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 | Work Item | Comments | Result |
| 0 | - | - | - | All Agenda Items | - | - | S2-168 | Docs:=0 | - |
| 1.1 | - | - | - | Opening of the meeting | - | - | Andy | Docs:=0 | - |
| 2 | - | - | - | Agenda | - | - | Andy | Docs:=3 | - |
| 2 | S2-2502789 | AGENDA | Approval | SA2#168 meeting Agenda | SA WG2 Chair | ||||
| 2 | S2-2502790 | AGENDA | Information | SA WG2#168 meeting schedule | SA WG2 Chair | ||||
| 2 | S2-2503115 | AGENDA | Endorsement | Plan for the meeting | SA WG2 Chair | ||||
| 2.1 | - | - | - | IPR Call and Antitrust Reminder | - | - | Andy | Docs:=0 | - |
| 3 | - | - | - | SA2#167 Meeting report | - | - | Andy | Docs:=1 | - |
| 3 | S2-2502791 | REPORT | Approval | Draft Report of SA WG2 meeting #167 | SA WG2 Secretary | ||||
| 4 | - | - | - | General | - | - | Andy | Docs:=0 | - |
| 4.1 | - | - | - | Common issues and Incoming LSs | - | - | Andy | Docs:=31 | - |
| 4.1 | - | - | - | Incoming LSs with no actions - proposed to note | - | - | - | Docs:=6 | - |
| 4.1 | S2-2502823 | LS In | Information | LS from RAN WG2: Inclusion of NTN intended service area in the Service Announcement | RAN WG2 (R2-2501583) | NR_NTN_Ph3-Core | Response drafted in S2-2502898 | ||
| 4.1 | S2-2502898 | LS OUT | Approval | [DRAFT] Reply LS on Inclusion of NTN intended service area in the Service Announcement | Nokia | Rel-19 | NR_NTN_Ph3-Core | Response to S2-2502823 | |
| 4.1 | S2-2502809 | LS In | Information | LS from CT WG3: LS reply on FS_IMS_RES outcome and future work plan | CT WG3 (C3-250657) | FS_IMS_RES | Reply to C4-244485 (S2-2411293 @ SA2#166) | ||
| 4.1 | S2-2502846 | LS In | Information | LS from TSG SA: Reply LS on support of multiple access technologies based on the IMS service type | TSG SA (SP-250329) | TSG SA Reply to GSMA (related to S2-2501277) | |||
| 4.1 | S2-2502838 | LS In | Information | LS from SA WG4: LS on Advanced Media Delivery | SA WG4 (S4-250412) | AMD-ARCH-MED, AMD_PRO-MED | |||
| 4.1 | S2-2502848 | LS In | Action | LS from ETSI ISG NFV: Publication of ETSI NFV group report on architectural support for NFV evolution | ETSI ISG NFV (NFV(25)000019r2) | ||||
| 4.1 | - | - | - | Next Generation eCall | - | - | - | Docs:=1 | - |
| 4.1 | S2-2502798 | LS In | Action | LS from CEN TC 278 WG 15: LS on Next Generation eCall | CEN TC 278 WG 15 (3GPP_LS_reply_2025-02-05) | Revision of S2-2501381 | |||
| 4.1 | - | - | - | OSAppID usage by AppToken use case | - | - | - | Docs:=7 | - |
| 4.1 | S2-2502797 | LS In | Information | LS from GSMA TSGNS: OSAppID usage by AppToken use case | GSMA TSGNS (TSGNS44_003v6) | Revision of S2-2501377. Responses drafted in S2-2502926, S2-2503081, S2-2503424, S2-2503617, S2-2503747, S2-2503855 | |||
| 4.1 | S2-2502927 | DISCUSSION | Discussion | Discussion paper on GSMA TSGNS AppToken use case. | Telefonica S.A., Verizon, Deutsche Telekom, KDDI, Ericsson, Nokia | Rel-19 | |||
| 4.1 | S2-2502926 | LS OUT | Approval | [DRAFT] Reply LS on OSAppID usage by AppToken use case | Telefonica Germany GmbH | Rel-19 | Response to S2-2502797 | ||
| 4.1 | S2-2503424 | LS OUT | Approval | [DRAFT] Reply LS to 'OSAppID usage by AppToken use case' | Apple | Rel-19 | Revision of (Unhandled) S2-2502143. Response to S2-2502797 | ||
| 4.1 | S2-2503617 | LS OUT | Approval | [DRAFT] Reply LS for OSAppID usage by AppToken use case | ZTE | Rel-19 | TEI19 | Response to S2-2502797 | |
| 4.1 | S2-2503747 | LS OUT | Approval | [DRAFT] Reply LS on OSAppID usage by AppToken use case | Samsung | Rel-19 | Response to S2-2502797 | ||
| 4.1 | S2-2503855 | LS OUT | Approval | [DRAFT] Reply LS on OSAppID usage by AppToken use case | Google Korea LLC | Rel-19 | Response to S2-2502797 | ||
| 4.1 | - | - | - | Generation of AF specific UE ID | - | - | - | Docs:=7 | - |
| 4.1 | S2-2502845 | LS In | Action | LS from SA WG6: LS on Generation of AF specific UE ID | SA WG6 (S6-250286) | EDGEAPP | Responses drafted in S2-2502871, S2-2502924, S2-2502951, S2-2503091, S2-2503620 | ||
| 4.1 | S2-2502870 | DISCUSSION | Discussion | Generation of AF specific UE Identifier . | Apple | ||||
| 4.1 | S2-2502871 | LS OUT | Approval | [DRAFT] Reply LS on generation of AF specific UE ID | Apple | Response to S2-2502845 | |||
| 4.1 | S2-2502924 | LS OUT | Approval | [DRAFT] Reply LS on generation of AF specific UE ID | Samsung | Response to S2-2502845 | |||
| 4.1 | S2-2503091 | LS OUT | Approval | [DRAFT] LS on Generation of AF specific UE ID | Nokia | Rel-19 | EDGEAPP | Response to S2-2502845 | |
| 4.1 | S2-2503620 | LS OUT | Approval | [DRAFT] LS Response on Generation of AF specific UE ID | ZTE | Rel-19 | EDGEAPP | Response to S2-2502845 | |
| 4.1 | S2-2502951 | LS OUT | Approval | [DRAFT] LS Reply on Generation of AF specific UE ID | Ericsson | Rel-19 | EDGEAPP | Response to S2-2502845 | |
| 4.1 | - | - | - | Optimizations to UPF event subscriptions and reporting | - | - | - | Docs:=8 | - |
| 4.1 | S2-2502849 | LS In | Action | LS from CT WG4: LS on Optimizations to UPF event subscriptions and reporting | CT WG4 (C4-250455) | Rel-19 | FS_PAIDC-UPF | Responses drafted in S2-2503095, S2-2503739, S2-2503769 | |
| 4.1 | S2-2503095 | LS OUT | Approval | [DRAFT] LS on Optimizations to UPF event subscriptions and reporting | Nokia | Rel-19 | FS_PAIDC_UPF | Response to S2-2502849 | |
| 4.1 | S2-2503739 | LS OUT | Approval | [DRAFT] LS Reply on Optimizations to UPF event subscriptions and reporting | Ericsson | Rel-19 | FS_PAIDC_UPF | Response to S2-2502849 | |
| 4.1 | S2-2503769 | LS OUT | Approval | [DRAFT] Reply LS on Optimizations to UPF event subscriptions and reporting | China Mobile | Rel-19 | FS_PAIDC_UPF | Response to S2-2502849 | |
| 4.1 | S2-2502953 | CR | Approval | 23.501 CR6168 (Rel-19, 'C'): Handling of AF Specific UE IDs | Ericsson, AT&T, Nokia, Deutsche Telekom, KPN, NTT DOCOMO | Rel-19 | EDGEAPP | ||
| 4.1 | S2-2503024 | CR | Approval | 23.501 CR6174 (Rel-19, 'C'): AF specific UE ID generation | Samsung | Rel-19 | EDGEAPP | ||
| 4.1 | S2-2503025 | CR | Approval | 23.502 CR5398 (Rel-19, 'C'): AF specific UE ID generation | Samsung | Rel-19 | EDGEAPP | ||
| 4.1 | S2-2503092 | CR | Approval | 23.502 CR5413 (Rel-19, 'F'): Generation of AF specific UE ID | Nokia, AT&T, KPN, NTT DOCOMO, Deutsche Telekom | Rel-19 | EDGEAPP | ||
| 4.1 | - | - | - | Inclusion of NTN intended service area in the Service Announcement | - | - | - | Docs:=2 | - |
| 4.1 | - | - | - | Time Synchronization for MBS | - | - | - | Docs:=1 | - |
| 4.1 | S2-2502801 | LS In | Action | LS from RAN WG2: Reply LS on Time Synchronization for MBS | RAN WG2 (R2-2501509) | Rel-19 | FS_AMD | Reply to S2-2501327 Revision of S2-2501386 | |
| 4.1 | - | - | - | ETSI NFV group report on architectural support for NFV evolution | - | - | - | Docs:=0 | - |
| 4.1 | - | - | - | Other | - | - | - | Docs:=1 | - |
| 4.1 | S2-2503877 | DISCUSSION | Information | 6G specification format modernization: towards Automation-Native. | Nokia | ||||
| 4.2 | - | - | - | P-CRs/CRs related to use of inclusive language in 3GPP | - | - | Andy | Docs:=0 | - |
| 5 | - | - | - | Pre-Rel-17 Maintenance (excluding all 5G topics) | - | - | Andy | Docs:=0 | - |
| 5.1 | - | - | - | 3GPP Packet Access Maintenance | - | - | (No documents) | Docs:=0 | - |
| 5.2 | - | - | - | QoS and PCC Maintenance | - | - | (No documents) | Docs:=0 | - |
| 5.3 | - | - | - | Non-3GPP Access Maintenance | - | - | (No documents) | Docs:=0 | - |
| 5.4 | - | - | - | IMS and IMS-Related Maintenance | - | - | (No documents) | Docs:=0 | - |
| 6 | - | - | - | Rel-15/Rel-16 Maintenance for 5G (only related to 5GS_Ph1 Work Item) | - | - | Andy | Docs:=0 | - |
| 6.1 | - | - | - | General aspects, concepts and reference models | - | - | (No documents) | Docs:=0 | - |
| 6.2 | - | - | - | Common Access Control, RM and CM functions and procedure flows | - | - | Andy | Docs:=4 | - |
| 6.2 | S2-2503084 | CR | Approval | 23.502 CR5411 (Rel-16, 'C'): AMF reselection via NAS reroute based on Routing Indicator | Jio Platforms Ltd (JPL) | Rel-16 | 5GS_Ph1 | ||
| 6.2 | S2-2503401 | CR | Approval | 23.502 CR5440 (Rel-18, 'F'): Registration handling during the mobility from non-3GPP access to 3GPP access | Huawei, Hisilicom | Rel-18 | TEI18, 5GS_Ph1 | ||
| 6.2 | S2-2503402 | CR | Approval | 23.502 CR5441 (Rel-19, 'F'): Registration handling during the mobility from non-3GPP access to 3GPP access | Huawei, Hisilicom | Rel-19 | 5GS_Ph1, TEI19_NetShare | ||
| 6.2 | S2-2503729 | CR | Approval | 23.501 CR6253 (Rel-19, 'C'): Radio capability assignment in case of equivalent PLMNs. | NEC | Rel-19 | TEI19 | ||
| 6.3 | - | - | - | Session management and continuity functions and flows | - | - | Andy | Docs:=1 | - |
| 6.3 | S2-2502983 | CR | Approval | 23.502 CR4501R1 (Rel-19, 'F'): Synchronizing status of QoS Flow(s) between H-SMF or anchor SMF and UE | Ericsson | Rel-19 | 5GS_Ph1, TEI19 | Revision of (Unhandled) S2-2310691 from SA2#159 | |
| 6.4 | - | - | - | Security related functions and flows | - | - | (No documents) | Docs:=0 | - |
| 6.5 | - | - | - | QoS concept and functionality | - | - | (No documents) | Docs:=0 | - |
| 6.6 | - | - | - | Policy and charging control | - | - | Andy | Docs:=2 | - |
| 6.6 | S2-2503085 | CR | Approval | 23.502 CR5412 (Rel-16, 'C'): Rel-16 CR TS 23.502 Type Allocation Code (TAC) based AMF local configuration for establishment of UE policy association. | Jio Platform Limited (JPL) | Rel-16 | 5GS_Ph1 | ||
| 6.6 | S2-2503506 | CR | Approval | 23.503 CR1541 (Rel-19, 'D'): Simplification of clause 6.2.1.2 | Huawei, HiSilicon | Rel-19 | 5GS_Ph1, TEI19 | ||
| 6.7 | - | - | - | 3GPP access specific functionality and flows | - | - | (No documents) | Docs:=0 | - |
| 6.8 | - | - | - | Specific services support | - | - | (No documents) | Docs:=0 | - |
| 6.9 | - | - | - | Interworking and Migration | - | - | (No documents) | Docs:=0 | - |
| 6.10 | - | - | - | Non-3GPP access specific functionality and flows | - | - | (No documents) | Docs:=0 | - |
| 6.11 | - | - | - | Framework functions | - | - | (No documents) | Docs:=0 | - |
| 7 | - | - | - | Rel-16 Maintenance for 5G (excluding 5GS_Ph1) | - | - | Andy | Docs:=0 | - |
| 7.1 | - | - | - | Architecture enhancements for 3GPP support of advanced V2X services (eV2XARC) | - | - | (No documents) | Docs:=0 | - |
| 7.2 | - | - | - | Wireless and Wireline Convergence for the 5G system architecture (5WWC) | - | - | (No documents) | Docs:=0 | - |
| 7.3 | - | - | - | Access Traffic Steering, Switch and Splitting support in the 5G system architecture (ATSSS) | - | - | (No documents) | Docs:=0 | - |
| 7.4 | - | - | - | Cellular IoT support and evolution for the 5G System (5G_CIoT) | - | - | (No documents) | Docs:=0 | - |
| 7.5 | - | - | - | Enablers for Network Automation for 5G (eNA) | - | - | (No documents) | Docs:=0 | - |
| 7.6 | - | - | - | Enhancement to the 5GC Location Services (5G_eLCS) | - | - | (No documents) | Docs:=0 | - |
| 7.7 | - | - | - | 5GS Enhanced support of Vertical and LAN Services (Vertical_LAN) | - | - | Andy | Docs:=8 | - |
| 7.7 | S2-2503719 | DISCUSSION | Discussion | Discussion on the epoch issue for 5G Residence time calculation | ZTE | Vertical_LAN | |||
| 7.7 | S2-2503746 | DISCUSSION | Agreement | Ensuring the same epoch for timestamping for gPTP | Qualcomm | Vertical_LAN | |||
| 7.7 | S2-2503720 | CR | Approval | 23.501 CR6104R1 (Rel-16, 'F'): Epoch for 5G Residence time calculation | ZTE | Rel-16 | Vertical_LAN | Revision of (Postponed) S2-2501749 | |
| 7.7 | S2-2503721 | CR | Approval | 23.501 CR6105R1 (Rel-17, 'F'): Epoch for 5G Residence time calculation | ZTE | Rel-17 | Vertical_LAN | Revision of (Postponed) S2-2501750 | |
| 7.7 | S2-2503722 | CR | Approval | 23.501 CR6106R1 (Rel-18, 'F'): Epoch for 5G Residence time calculation | ZTE | Rel-18 | Vertical_LAN | Revision of (Postponed) S2-2501751 | |
| 7.7 | S2-2503723 | CR | Approval | 23.501 CR6107R1 (Rel-19, 'A'): Epoch for 5G Residence time calculation | ZTE | Rel-19 | Vertical_LAN | Revision of (Postponed) S2-2501752 | |
| 7.7 | S2-2503862 | CR | Approval | 23.501 CR6268 (Rel-18, 'F'): 5GS common time reference traceable to UTC | Nokia | Rel-18 | IIoT, Vertical_LAN | Check Acronym. Vertical_LAN is Rel-16, IIoT is Rel-17! | |
| 7.7 | S2-2503863 | CR | Approval | 23.501 CR6269 (Rel-19, 'A'): 5GS common time reference traceable to UTC | Nokia | Rel-19 | IIoT, Vertical_LAN | Check Acronym. Vertical_LAN is Rel-16, IIoT is Rel-17! | |
| 7.8 | - | - | - | Enhancements to the Service-Based 5G System Architecture (5G_eSBA) | - | - | (No documents) | Docs:=0 | - |
| 7.9 | - | - | - | Architecture enhancements for the support of Integrated access and backhaul (IABARC) | - | - | (No documents) | Docs:=0 | - |
| 7.10 | - | - | - | Enhancement of URLLC supporting in 5GC (5G_URLLC) | - | - | (No documents) | Docs:=0 | - |
| 7.11 | - | - | - | Enhancement of Network Slicing (eNS) | - | - | (No documents) | Docs:=0 | - |
| 7.12 | - | - | - | Optimisations on UE radio capability signalling (RACS) | - | - | (No documents) | Docs:=0 | - |
| 7.13 | - | - | - | Enhanced IMS to 5GC Integration (eIMS5G_SBA) | - | - | Andy | Docs:=1 | - |
| 7.13 | S2-2503088 | CR | Approval | 23.228 CR1615 (Rel-16, 'B'): Service restoration by IMS when the UE is unresponsive but reachable | Jio Platforms Ltd (JPL) | Rel-16 | eIMS5G_SBA | ||
| 7.14 | - | - | - | User Data Interworking and Coexistence (UDICoM) | - | - | (No documents) | Docs:=0 | - |
| 7.15 | - | - | - | Enhancing Topology of SMF and UPF in 5G Networks (ETSUN) | - | - | (No documents) | Docs:=0 | - |
| 7.16 | - | - | - | 5GS Transfer of Policies for Background Data Transfer (xBDT) | - | - | (No documents) | Docs:=0 | - |
| 7.17 | - | - | - | Single radio voice continuity from 5GS to 3G (5G_SRVCC) | - | - | (No documents) | Docs:=0 | - |
| 8 | - | - | - | Rel-17 Maintenance | - | - | Andy | Docs:=0 | - |
| 8.1 | - | - | - | Enablers for Network Automation for 5G - phase 2 (eNA_Ph2) | - | - | Andy | Docs:=2 | - |
| 8.1 | S2-2503350 | CR | Approval | 23.288 CR1438 (Rel-18, 'F'): Correlate the Slice Load to an AOI when location is provided | Verizon, Oracle, CATT | Rel-18 | TEI18, eNA_Ph3 | ||
| 8.1 | S2-2503361 | CR | Approval | 23.288 CR1439 (Rel-19, 'F'): Attribute Level Change | Verizon, Oracle, CATT | Rel-19 | TEI19, AIML_CN | ||
| 8.2 | - | - | - | Enhanced support of Non-Public Networks (eNPN) | - | - | (No documents) | Docs:=0 | - |
| 8.3 | - | - | - | Enhancement of support for Edge Computing in 5GC (eEDGE_5GC) | - | - | (No documents) | Docs:=0 | - |
| 8.4 | - | - | - | Enhancement of Network Slicing Phase 2 (eNS_Ph2) | - | - | (No documents) | Docs:=0 | - |
| 8.5 | - | - | - | Enhanced support of Industrial IoT - TSC/URLLC enhancements (IIoT) | - | - | (No documents) | Docs:=0 | - |
| 8.6 | - | - | - | Access Traffic Steering, Switch and Splitting support in the 5G system architecture Phase 2 (ATSSS_Ph2) | - | - | (No documents) | Docs:=0 | - |
| 8.7 | - | - | - | Support of Aerial Systems Connectivity, Identification, and Tracking (ID_UAS) | - | - | (No documents) | Docs:=0 | - |
| 8.8 | - | - | - | System enhancement for Proximity based Services in 5GS (5G_ProSe) | - | - | (No documents) | Docs:=0 | - |
| 8.9 | - | - | - | Architectural enhancements for 5G multicast-broadcast services (5MBS) | - | - | (No documents) | Docs:=0 | - |
| 8.10 | - | - | - | System enablers for multi-USIM devices (MUSIM) | - | - | (No documents) | Docs:=0 | - |
| 8.11 | - | - | - | Architecture aspects for using satellite access in 5G (5GSAT_ARCH) | - | - | Andy | Docs:=1 | - |
| 8.11 | S2-2502803 | LS In | Information | LS from CT WG1: LS on stage 1 requirements for the support for PWS over satellite NGRAN in Rel-17 | CT WG1 (C1-250715) | 5GSAT | |||
| 8.12 | - | - | - | Architecture enhancements for 3GPP support of advanced V2X services - Phase 2 (eV2XARC_Ph2) | - | - | (No documents) | Docs:=0 | - |
| 8.13 | - | - | - | 5G System Enhancement for Advanced Interactive Services (5G_AIS) | - | - | (No documents) | Docs:=0 | - |
| 8.14 | - | - | - | Enhancement to the 5GC LoCation Services-Phase 2 (5G_eLCS_Ph2) | - | - | Andy | Docs:=1 | - |
| 8.14 | S2-2502813 | LS In | Information | LS from CT WG4: LS on New port number for LCS-UPP | CT WG4 (C4-250590) | 5G_eLCS_Ph3 | |||
| 8.15 | - | - | - | Multimedia Priority Service (MPS) Phase 2 (MPS2) | - | - | (No documents) | Docs:=0 | - |
| 8.16 | - | - | - | Dynamic management of group-based event monitoring (TEI17_GEM) | - | - | (No documents) | Docs:=0 | - |
| 8.17 | - | - | - | N7/N40 Interfaces Enhancements to Support GERAN and UTRAN (TEI17_NIESGU) | - | - | (No documents) | Docs:=0 | - |
| 8.18 | - | - | - | System enhancement for Redundant PDU Session (TEI17_SE_RPS) | - | - | (No documents) | Docs:=0 | - |
| 8.19 | - | - | - | IMS Optimization for HSS Group ID in an SBA environment (TEI17_IMSGID) | - | - | (No documents) | Docs:=0 | - |
| 8.20 | - | - | - | Support for Signed Attestation for Priority and Emergency Sessions (TEI17_SAPES) | - | - | (No documents) | Docs:=0 | - |
| 8.21 | - | - | - | Dynamically Changing AM Policies in the 5GC (TEI17_DCAMP) | - | - | (No documents) | Docs:=0 | - |
| 8.22 | - | - | - | IP address pool information from UDM (TEI17_IPU) | - | - | (No documents) | Docs:=0 | - |
| 8.23 | - | - | - | Same PCF selection for AMF and SMF (TEI17-SPSFAS) | - | - | (No documents) | Docs:=0 | - |
| 8.24 | - | - | - | Support of different slices over different Non-3GPP access (TEI17_N3SLICE) | - | - | (No documents) | Docs:=0 | - |
| 8.25 | - | - | - | Minimization of Service Interruption (MINT) | - | - | (No documents) | Docs:=0 | - |
| 8.26 | - | - | - | Architecture Enhancement for NR Reduced Capability Devices (ARCH_NR_REDCAP) | - | - | (No documents) | Docs:=0 | - |
| 8.27 | - | - | - | Architecture support for NB-IoT/eMTC Non-Terrestrial Networks in EPS (IoT_SAT_ARCH_EPS) | - | - | (No documents) | Docs:=0 | - |
| 8.28 | - | - | - | Rel-17 CAT B/C alignment CR(s) due to the work led by other 3GPP Working Groups | - | - | (No documents) | Docs:=0 | - |
| 9 | - | - | - | Rel-18 WIDs | - | - | Andy | Docs:=0 | - |
| 9.1.2 | - | - | - | 5G System with Satellite Backhaul (5GSATB) | - | - | (No documents) | Docs:=0 | - |
| 9.2.2 | - | - | - | Satellite access Phase 2 (5GSAT_Ph2) | - | - | (No documents) | Docs:=0 | - |
| 9.3.2 | - | - | - | Personal IoT Networks (5G_PIN) | - | - | (No documents) | Docs:=0 | - |
| 9.4.2 | - | - | - | Phase 2 for UAS, UAV and UAM (UAS_Ph2) | - | - | (No documents) | Docs:=0 | - |
| 9.5.2 | - | - | - | Ranging based services and sidelink positioning (Ranging_SL) | - | - | (No documents) | Docs:=0 | - |
| 9.6.2 | - | - | - | 5GC LoCation Services Phase 3 (eLCS_Ph3) | - | - | Wanqiang | Docs:=12 | - |
| 9.6.2 | - | - | - | Change Sequence of a Procedure | - | - | - | Docs:=2 | - |
| 9.6.2 | S2-2503492 | CR | Approval | 23.273 CR0717 (Rel-18, 'F'): Clarification and correction on modification of UP connection between UE and LMF | Huawei, HiSilicon | Rel-18 | 5G_eLCS_Ph3 | ||
| 9.6.2 | S2-2503493 | CR | Approval | 23.273 CR0718 (Rel-19, 'A'): Clarification and correction on modification of UP connection between UE and LMF | Huawei, HiSilicon | Rel-19 | 5G_eLCS_Ph3 | ||
| 9.6.2 | - | - | - | Number of User plane connections: One in Rel-18 | - | - | - | Docs:=4 | - |
| 9.6.2 | S2-2503171 | DISCUSSION | Agreement | Discussion on single LCS-UPP connection maintenance. | OPPO | Rel-18 | 5G_eLCS_Ph3 | ||
| 9.6.2 | S2-2502961 | CR | Approval | 23.273 CR0703 (Rel-18, 'F'): Solving UE shall have maximum one LCS-UPP | Ericsson | Rel-18 | 5G_eLCS_Ph3 | ||
| 9.6.2 | S2-2503173 | CR | Approval | 23.273 CR0707 (Rel-18, 'F'): Update on single LCS-UPP connection maintenance | OPPO | Rel-18 | 5G_eLCS_Ph3 | ||
| 9.6.2 | S2-2503726 | CR | Approval | 23.273 CR0729 (Rel-18, 'F'): Clarification on the maximum one LCS-UPP connection restriction | ZTE | Rel-18 | 5G_eLCS_Ph3 | ||
| 9.6.2 | - | - | - | Number of User plane connections: Multiple in Rel-19 | - | - | - | Docs:=1 | - |
| 9.6.2 | S2-2502962 | CR | Approval | 23.273 CR0646R3 (Rel-19, 'C'): Supporting multiple LCS-UPP connections per UE | Ericsson | Rel-19 | 5G_eLCS_Ph3, TEI19 | Revision of (Postponed) S2-2502330 | |
| 9.6.2 | - | - | - | Fall back to CP when UP fails | - | - | - | Docs:=2 | - |
| 9.6.2 | S2-2503647 | CR | Approval | 23.273 CR0722 (Rel-18, 'F'): Solve the failure of the user plane connection establishment | CATT | Rel-18 | 5G_eLCS_Ph3 | ||
| 9.6.2 | S2-2503648 | CR | Approval | 23.273 CR0723 (Rel-19, 'A'): Solve the failure of the user plane connection establishment | CATT | Rel-19 | 5G_eLCS_Ph3 | ||
| 9.6.2 | - | - | - | Context Sync between UE and NW | - | - | - | Docs:=3 | - |
| 9.6.2 | S2-2503172 | CR | Approval | 23.273 CR0706 (Rel-18, 'F'): User plane positioning update for LCS-UPP context synchronization | OPPO | Rel-18 | 5G_eLCS_Ph3 | ||
| 9.6.2 | S2-2503724 | CR | Approval | 23.273 CR0727 (Rel-18, 'F'): Correction on the Modification of User Plane Connection between UE and LMF | ZTE | Rel-18 | 5G_eLCS_Ph3 | ||
| 9.6.2 | S2-2503725 | CR | Approval | 23.273 CR0728 (Rel-19, 'A'): Correction on the Modification of User Plane Connection between UE and LMF | ZTE | Rel-19 | 5G_eLCS_Ph3 | ||
| 9.7.2 | - | - | - | Proximity-based Services in 5GS Phase 2 (5G_ProSe_Ph2) | - | - | (No documents) | Docs:=0 | - |
| 9.8.2 | - | - | - | Generic group management, exposure and communication enhancements (GMEC) | - | - | (No documents) | Docs:=0 | - |
| 9.9.2 | - | - | - | System Support for AI/ML-based Services (AIMLsys) | - | - | (No documents) | Docs:=0 | - |
| 9.10.2 | - | - | - | 5G multicast-broadcast services Phase 2 (5MBS_Ph2) | - | - | (No documents) | Docs:=0 | - |
| 9.11.2 | - | - | - | Network Slicing Phase 3 (eNS_Ph3) | - | - | Andy | Docs:=20 | - |
| 9.11.2 | S2-2502874 | CR | Approval | 23.503 CR1526 (Rel-18, 'F'): Update network slice replacement PCRT | Oracle, Verizon | Rel-18 | eNS_Ph3, TEI18 | ||
| 9.11.2 | S2-2502875 | CR | Approval | 23.503 CR1527 (Rel-19, 'A'): Update network slice replacement PCRT | Oracle, Verizon | Rel-19 | eNS_Ph3, TEI19 | ||
| 9.11.2 | - | - | - | Configured NSSAI | - | - | - | Docs:=8 | - |
| 9.11.2 | S2-2502889 | CR | Approval | 23.501 CR6018R2 (Rel-18, 'F'): Clarification on the removal of S-NSSAI from the Configured NSSAI | Nokia, ZTE | Rel-18 | eNS_Ph3 | Revision of (Postponed) S2-2501937 | |
| 9.11.2 | S2-2502890 | CR | Approval | 23.501 CR6019R2 (Rel-19, 'A'): Clarification on the removal of S-NSSAI from the Configured NSSAI | Nokia, ZTE | Rel-19 | eNS_Ph3 | Revision of (Unhandled) S2-2501938 | |
| 9.11.2 | S2-2503298 | CR | Approval | 23.501 CR6200 (Rel-18, 'F'): Configured NSSAI exchange between AMFs for Network Slice Replacement | LG Electronics | Rel-18 | eNS_Ph3 | ||
| 9.11.2 | S2-2503299 | CR | Approval | 23.501 CR6201 (Rel-19, 'A'): Configured NSSAI exchange between AMFs for Network Slice Replacement | LG Electronics | Rel-19 | eNS_Ph3 | ||
| 9.11.2 | S2-2503300 | CR | Approval | 23.502 CR5423 (Rel-18, 'F'): Update on UE Context in AMF to support Network Slice Replacement | LG Electronics | Rel-18 | eNS_Ph3 | ||
| 9.11.2 | S2-2503301 | CR | Approval | 23.502 CR5424 (Rel-19, 'A'): Update on UE Context in AMF to support Network Slice Replacement | LG Electronics | Rel-19 | eNS_Ph3 | ||
| 9.11.2 | S2-2503664 | CR | Approval | 23.501 CR6153R1 (Rel-18, 'F'): Clarification on Configured NSSAI for temporary slice | Samsung | Rel-18 | eNS_Ph3 | Revision of (Postponed) S2-2502125 | |
| 9.11.2 | S2-2503666 | CR | Approval | 23.501 CR6154R1 (Rel-19, 'A'): Clarification on Configured NSSAI for temporary slice | Samsung | Rel-19 | eNS_Ph3 | Revision of (Unhandled) S2-2502126 | |
| 9.11.2 | - | - | - | Always on PDU Session | - | - | - | Docs:=10 | - |
| 9.11.2 | S2-2503546 | DISCUSSION | Endorsement | Discussion on always-on PDU sessions for network slices subject to area restrictions. | NTT Docomo, Nokia | Rel-18 | eNS_Ph3 | Revision of (Noted) S2-2501575. Revised to S2-2503821 | Revised |
| 9.11.2 | S2-2503821 | DISCUSSION | Endorsement | Discussion on always-on PDU sessions for network slices subject to area restrictions. | NTT Docomo, Nokia | Rel-18 | eNS_Ph3 | Revision of S2-2503546 | |
| 9.11.2 | S2-2503548 | CR | Approval | 23.501 CR5987R2 (Rel-18, 'F'): Handling of always-on PDU sessions for network slices subject to area control | NTT DOCOMO, Nokia | Rel-18 | eNS_Ph3 | Revision of (Postponed) S2-2501577 | |
| 9.11.2 | S2-2503550 | CR | Approval | 23.501 CR5988R2 (Rel-19, 'A'): Handling of always-on PDU sessions for network slices subject to area restrictions | NTT DOCOMO, Nokia | Rel-19 | eNS_Ph3 | Revision of (Unhandled) S2-2501578 | |
| 9.11.2 | S2-2503551 | CR | Approval | 23.502 CR5273R2 (Rel-18, 'F'): Handling of always-on PDU sessions for network slices subject to area restrictions | NTT DOCOMO, Nokia. | Rel-18 | eNS_Ph3 | Revision of (Unhandled) S2-2501579 | |
| 9.11.2 | S2-2503558 | CR | Approval | 23.502 CR5274R2 (Rel-19, 'A'): Handling of always-on PDU sessions for network slices subject to area control | Nokia | Rel-19 | eNS_Ph3 | Revision of (Unhandled) S2-2501580. Confirm Spec version used - CR states 19.2.0! | |
| 9.11.2 | S2-2503559 | CR | Approval | 23.501 CR6231 (Rel-18, 'F'): Handling of always-on PDU sessions for network slices subject to area control- option B | Nokia, NTT DOCOMO | Rel-18 | eNS_Ph3 | ||
| 9.11.2 | S2-2503573 | CR | Approval | 23.501 CR6232 (Rel-19, 'A'): Handling of always-on PDU sessions for network slices subject to area control- option B | Nokia, NTT DOCOMO | Rel-19 | eNS_Ph3 | ||
| 9.11.2 | S2-2503615 | CR | Approval | 23.501 CR6237 (Rel-18, 'F'): Clarification on always-on PDU Session | ZTE | Rel-18 | eNS_Ph3 | ||
| 9.11.2 | S2-2503616 | CR | Approval | 23.501 CR6238 (Rel-19, 'A'): Clarification on always-on PDU Session | ZTE | Rel-19 | eNS_Ph3 | ||
| 9.12.2 | - | - | - | XR (Extended Reality) and media services (XRM) | - | - | Dario | Docs:=18 | - |
| 9.12.2 | - | - | - | L4S related | - | - | - | Docs:=7 | - |
| 9.12.2 | S2-2502893 | DISCUSSION | Discussion | Dynamic detection of L4S traffic and enabling of ECN marking for L4S. | Apple, Ericsson | ||||
| 9.12.2 | S2-2502891 | CR | Approval | 23.501 CR6069R2 (Rel-18, 'F'): Clarifications on ECN marking for L4S | Apple | Rel-18 | XRM | Revision of (Postponed) S2-2502406 | |
| 9.12.2 | S2-2502892 | CR | Approval | 23.501 CR6070R2 (Rel-19, 'A'): Clarifications on ECN marking for L4S | Apple | Rel-19 | XRM | Revision of (Postponed) S2-2501446 | |
| 9.12.2 | S2-2503513 | CR | Approval | 23.501 CR6135R1 (Rel-18, 'F'): Clarifications and corrections for ECN marking for L4S and congestion monitoring | Huawei, HiSilicon | Rel-18 | XRM | Revision of (Postponed) S2-2501907 | |
| 9.12.2 | S2-2503514 | CR | Approval | 23.501 CR6136R1 (Rel-19, 'A'): Clarifications and corrections for ECN marking for L4S and congestion monitoring | Huawei, HiSilicon | Rel-19 | XRM | Revision of (Unhandled) S2-2501908 | |
| 9.12.2 | S2-2503515 | CR | Approval | 23.503 CR1515R1 (Rel-18, 'F'): Clarifications and corrections for ECN marking for L4S and congestion monitoring | Huawei, HiSilicon | Rel-18 | XRM | Revision of (Unhandled) S2-2501909 | |
| 9.12.2 | S2-2503516 | CR | Approval | 23.503 CR1516R1 (Rel-19, 'A'): Clarifications and corrections for ECN marking for L4S and congestion monitoring | Huawei, HiSilicon | Rel-19 | XRM | Revision of (Unhandled) S2-2501910 | |
| 9.12.2 | - | - | - | Multi-modality services related | - | - | - | Docs:=6 | - |
| 9.12.2 | S2-2503507 | CR | Approval | 23.501 CR5255R7 (Rel-18, 'F'): Clarifications for multi-modal services | Huawei, HiSilicon, Nokia | Rel-18 | XRM | Revision of (Noted) S2-2410783 | |
| 9.12.2 | S2-2503508 | CR | Approval | 23.501 CR5568R3 (Rel-19, 'A'): Clarifications for multi-modal services | Huawei, HiSilicon, Nokia | Rel-19 | XRM | Revision of (withdrawn at S2#165) S2-2410331 | |
| 9.12.2 | S2-2503509 | CR | Approval | 23.503 CR1251R7 (Rel-18, 'F'): Clarifications for multi-modal services | Huawei, HiSilicon, Nokia, ZTE | Rel-18 | XRM | Revision of (Postponed at S2#165) S2-2410785 | |
| 9.12.2 | S2-2503510 | CR | Approval | 23.503 CR1357R3 (Rel-19, 'A'): Clarifications for multi-modal services | Huawei, HiSilicon, Nokia | Rel-19 | XRM | Revision of (Withdrawn at S2#165) S2-2410327 | |
| 9.12.2 | S2-2503585 | CR | Approval | 23.502 CR4702R7 (Rel-18, 'F'): Clarifications for multi-modal services | Huawei, HiSilicon | Rel-18 | XRM | Revision of (Postponed at S2#165) S2-2410784 | |
| 9.12.2 | S2-2503587 | CR | Approval | 23.502 CR4956R3 (Rel-19, 'A'): Clarifications for multi-modal services | Huawei, HiSilicon | Rel-19 | XRM | Revision of (Withdrawn at S2#165) S2-2410329 | |
| 9.12.2 | - | - | - | Others | - | - | - | Docs:=5 | - |
| 9.12.2 | S2-2503324 | CR | Approval | 23.501 CR6204 (Rel-18, 'F'): Fix PDU Set based Handling description | Samsung | Rel-18 | XRM | ||
| 9.12.2 | S2-2503325 | CR | Approval | 23.501 CR6205 (Rel-19, 'A'): Fix PDU Set based Handling description | Samsung | Rel-19 | XRM | ||
| 9.12.2 | S2-2503326 | CR | Approval | 23.502 CR5430 (Rel-18, 'F'): N2 SM information to NG-RAN | Samsung | Rel-18 | XRM | ||
| 9.12.2 | S2-2503327 | CR | Approval | 23.502 CR5431 (Rel-19, 'A'): N2 SM information to NG-RAN | Samsung | Rel-19 | XRM | ||
| 9.12.2 | S2-2503591 | CR | Approval | 23.503 CR1550 (Rel-19, 'F'): Activation of QoS monitoring for the GBR service data flow | CATT | Rel-19 | TEI19, XRM | ||
| 9.13.2 | - | - | - | RedCap Phase 2 (NR_RedCAP_Ph2) | - | - | (No documents) | Docs:=0 | - |
| 9.14.2 | - | - | - | Evolution of IMS multimedia telephony service (NG_RTC) | - | - | Dario | Docs:=5 | - |
| 9.14.2 | S2-2502804 | LS In | Information | LS from CT WG1: Reply LS on request for IMS Data Channel related clarifications | CT WG1 (C1-250819) | NG_RTC | |||
| 9.14.2 | S2-2503759 | CR | Approval | 23.228 CR1639 (Rel-19, 'F'): Adding event for session establishment cancellation | China Mobile | Rel-19 | NG_RTC | Rel-19 reserved, Rel-18 CR provided! | |
| 9.14.2 | S2-2503760 | CR | Approval | 23.228 CR1640 (Rel-19, 'A'): Adding event for session establishment cancellation | China Mobile | Rel-19 | NG_RTC | ||
| 9.14.2 | S2-2503761 | CR | Approval | 23.228 CR1641 (Rel-18, 'F'): Correction on bootstrap DC removal | China Mobile | Rel-18 | NG_RTC | Confirm Spec version used - CR states 18.8.0! | |
| 9.14.2 | S2-2503762 | CR | Approval | 23.228 CR1642 (Rel-19, 'A'): Correction on bootstrap DC removal | China Mobile | Rel-19 | NG_RTC | ||
| 9.15.2 | - | - | - | Access Traffic Steering, Switching and Splitting support in the 5GS; Phase 3 (ATSSS_Ph3) | - | - | Andy | Docs:=6 | - |
| 9.15.2 | S2-2503890 | CR | Approval | 23.501 CR6276 (Rel-18, 'F'): Alignment with ATSSS Capability IE | Apple | Rel-18 | MASSS | Revised to S2-2503891. Check WI Code -> MASSS is Rel-19 | Revised |
| 9.15.2 | S2-2503891 | CR | Approval | 23.501 CR6276R1 (Rel-18, 'F'): Alignment with ATSSS Capability IE | Apple | Rel-18 | ATSSS_Ph3 | Revision of S2-2503890 | |
| 9.16.2 | - | - | - | UPF enhancement for Exposure And SBA (UPEAS) | - | - | (No documents) | Docs:=0 | - |
| 9.17.2 | - | - | - | Edge Computing Phase 2 (EDGE_Ph2) | - | - | Dario | Docs:=1 | - |
| 9.17.2 | S2-2503852 | CR | Approval | 23.502 CR5478 (Rel-19, 'F'): SMF event on simultaneous connectivity failure | Nokia | Rel-19 | EDGE_Ph2 | ||
| 9.18.2 | - | - | - | 5G Timing Resiliency and TSC & URLLC enhancements (TRS_URLLC) | - | - | (No documents) | Docs:=0 | - |
| 9.19.2 | - | - | - | Vehicle Mounted Relays (VMR) | - | - | Andy | Docs:=0 | - |
| 9.20.2 | - | - | - | Support for 5WWC Phase 3 (5WWC_Ph2) | - | - | (No documents) | Docs:=0 | - |
| 9.21 | - | - | - | Stage 2 of MPS_WLAN (MPS_WLAN) | - | - | (No documents) | Docs:=0 | - |
| 9.22.2 | - | - | - | 5G AM Policy (AMP) | - | - | (No documents) | Docs:=0 | - |
| 9.23.2 | - | - | - | Enablers for Network Automation for 5G - Phase 3 (eNA_Ph3) | - | - | Andy | Docs:=6 | - |
| 9.23.2 | S2-2502853 | CR | Approval | 23.288 CR1402 (Rel-18, 'F'): Clarifications on the definition of accuracy | ZTE | Rel-18 | eNA_Ph3 | ||
| 9.23.2 | S2-2502854 | CR | Approval | 23.288 CR1403 (Rel-19, 'A'): Clarifications on the definition of accuracy | ZTE | Rel-19 | eNA_Ph3 | ||
| 9.23.2 | S2-2502855 | CR | Approval | 23.288 CR1404 (Rel-18, 'F'): Clarifications on the file address related to ADRF | ZTE | Rel-18 | eNA_Ph3 | ||
| 9.23.2 | S2-2502856 | CR | Approval | 23.288 CR1405 (Rel-19, 'A'): Clarifications on the file address related to ADRF | ZTE | Rel-19 | eNA_Ph3 | ||
| 9.23.2 | S2-2503539 | CR | Approval | 23.288 CR1446 (Rel-18, 'F'): Correction on analytics feedback information | Vivo | Rel-18 | eNA_Ph3 | ||
| 9.23.2 | S2-2503540 | CR | Approval | 23.288 CR1447 (Rel-19, 'F'): Correction on analytics feedback information | Vivo | Rel-19 | eNA_Ph3 | ||
| 9.24.2 | - | - | - | Enhanced support of Non-Public Networks phase 2 (eNPN_Ph2) | - | - | (No documents) | Docs:=0 | - |
| 9.25.2 | - | - | - | Enhancement of 5G UE Policy (eUEPO) | - | - | Andy | Docs:=4 | - |
| 9.25.2 | S2-2502876 | CR | Approval | 23.502 CR5380 (Rel-18, 'F'): Correction for BSF invocation in URSP Rule Enforcement Information procedure | Oracle, Verizon | Rel-18 | TEI18, eUEPO | Revised to S2-2503778 | Revised |
| 9.25.2 | S2-2503778 | CR | Approval | 23.502 CR5380R1 (Rel-18, 'F'): Correction for BSF invocation in URSP Rule Enforcement Information procedure | Oracle, Verizon, Ericsson | Rel-18 | TEI18, eUEPO | Revision of S2-2502876 | |
| 9.25.2 | S2-2502877 | CR | Approval | 23.502 CR5381 (Rel-19, 'A'): Correction for BSF invocation in URSP Rule Enforcement Information procedure | Oracle, Verizon | Rel-19 | eUEPO, TEI19 | Revised to S2-2503779 | Revised |
| 9.25.2 | S2-2503779 | CR | Approval | 23.502 CR5381R1 (Rel-19, 'A'): Correction for BSF invocation in URSP Rule Enforcement Information procedure | Oracle, Verizon, Ericsson | Rel-19 | eUEPO, TEI19 | Revision of S2-2502877 | |
| 9.26.2 | - | - | - | System Enabler for Service Function Chaining (SFC) | - | - | (No documents) | Docs:=0 | - |
| 9.27.2 | - | - | - | Extensions to the TSC Framework to support DetNet (DetNet) | - | - | (No documents) | Docs:=0 | - |
| 9.28.2 | - | - | - | Seamless UE context recovery (SUECR) | - | - | (No documents) | Docs:=0 | - |
| 9.29 | - | - | - | Multiple location report for MT-LR Immediate Location Request for regulatory services (TEI17_MLR) | - | - | (No documents) | Docs:=0 | - |
| 9.30 | - | - | - | Secondary DN Authentication and authorization in EPC IWK cases (TEI17_SDNAEPC) | - | - | (No documents) | Docs:=0 | - |
| 9.31 | - | - | - | MBS support for V2X services (TEI17_MBS4V2X) | - | - | (No documents) | Docs:=0 | - |
| 9.32 | - | - | - | Spending Limits for AM and UE Policies in the 5GC (TEI17_SLAMUP) | - | - | (No documents) | Docs:=0 | - |
| 9.33 | - | - | - | Enhancement of application detection event exposure (TEI17_ADEE) | - | - | (No documents) | Docs:=0 | - |
| 9.34 | - | - | - | General Support of IPv6 Prefix Delegation (TEI17_IPv6PD) | - | - | (No documents) | Docs:=0 | - |
| 9.35 | - | - | - | New WID on Dynamically Changing AM Policies in the 5GC Phase 2 (TEI17_DCAMP_Ph2) | - | - | (No documents) | Docs:=0 | - |
| 9.36 | - | - | - | Enhancement of NSAC for maximum number of UEs with at least one PDU session/PDN connection (eNSAC) | - | - | (No documents) | Docs:=0 | - |
| 9.37 | - | - | - | Generic Rel-18 LSs | - | - | _Not_on_Agenda | Docs:=0 | - |
| 9.38 | - | - | - | Rel-18 CAT B/C alignment CR(s) due to the work led by other 3GPP Working Groups | - | - | (No documents) | Docs:=0 | - |
| 19 | - | - | - | Rel-19 SIDs and WIDs | - | - | Andy | Docs:=0 | - |
| 19.1.1 | - | - | - | Study on Integration of satellite components in the 5G architecture Phase 3 (FS_5GSAT_Ph3_ARC) | - | - | _Not_on_Agenda | Docs:=0 | - |
| 19.1.2 | - | - | - | Integration of satellite components in the 5G architecture Phase 3 (5GSAT_Ph3_ARC) | - | - | Dario | Docs:=55 | - |
| 19.1.2 | - | - | - | Liaisons unrelated to specific key issues | - | - | - | Docs:=2 | - |
| 19.1.2 | S2-2502822 | LS In | Information | LS from RAN WG2: Geofencing in ETWS for NR and NB-IoT NTN | RAN WG2 (R2-2501581) | NR_NTN_Ph3-Core, IoT_NTN_Ph3-Core | |||
| 19.1.2 | S2-2502824 | LS In | Information | LS from RAN WG2: LS to CT1 and CT4 on maximum warning message size | RAN WG2 (R2-2501586) | IoT_NTN_Ph3-Core | |||
| 19.1.2 | - | - | - | KI#1 Regenerative payload satellite access | - | - | - | Docs:=13 | - |
| 19.1.2 | S2-2502829 | LS In | Action | LS from RAN WG3: Reply LS on OAM requirements to support regenerative payload transport links | RAN WG3 (R3-250895) | NR_NTN_Ph3-Core | Reply to S2-2413030 Responses drafted in S2-2502929, S2-2502930, S2-2503231, S2-2503706 | ||
| 19.1.2 | S2-2502842 | LS In | Action | LS from SA WG5: Reply LS to LS on reply to LS on OAM requirements to support regenerative payload | SA WG5 (S5-250842) | NTN_OAM_Ph2 | Reply to S2-2413030 Responses drafted in S2-2503231, S2-2503706 | ||
| 19.1.2 | S2-2503268 | DISCUSSION | Discussion | Tracking Area handling for regenerative satellite access. | Ericsson | Rel-19 | 5GSAT_Ph3-ARC | Handle | |
| 19.1.2 | S2-2503224 | DISCUSSION | Approval | On TAI configuration in AMF via OAM. | Qualcomm Incorporated, Vodafone | Rel-19 | 5GSAT_Ph3-ARC | Handle | |
| 19.1.2 | S2-2503706 | LS OUT | Approval | [DRAFT] Reply LS on OAM requirements to support regenerative payload transport links | CATT | Rel-19 | 5GSAT_Ph3-ARC | Handle -baseline Response to S2-2502829 and S2-2502842 | |
| 19.1.2 | S2-2502929 | LS OUT | Approval | [DRAFT] Reply LS on OAM requirements to support regenerative payload | ZTE Corporation | Rel-19 | 5GSAT_Ph3-ARC | Merge into S2-2503706 Response to S2-2502829 | |
| 19.1.2 | S2-2502930 | LS OUT | Approval | [DRAFT] Reply LS on OAM requirements to support regenerative payload | ZTE Corporation | Rel-19 | 5GSAT_Ph3-ARC | Duplicated: note? Response to S2-2502829 | |
| 19.1.2 | S2-2503231 | LS OUT | Approval | [DRAFT] Reply LS on OAM requirements to support regenerative payload transport links | Qualcomm, Vodafone | Rel-19 | NR_NTN_Ph3-Core | Handle Response to S2-2502829 and S2-2502842 | |
| 19.1.2 | S2-2503416 | CR | Approval | 23.501 CR6217 (Rel-19, 'F'): TAIs configured by OAM | Vivo | Rel-19 | 5GSAT_Ph3-ARC | Handle - baseline | |
| 19.1.2 | S2-2503707 | CR | Approval | 23.501 CR6250 (Rel-19, 'F'): Configuration of TAI list for regenerative satellite payload | CATT | Rel-19 | 5GSAT_Ph3-ARC | Merge into S2-2503416? | |
| 19.1.2 | S2-2503417 | CR | Approval | 23.502 CR5443 (Rel-19, 'F'): TAIs configured by OAM | Vivo | Rel-19 | 5GSAT_Ph3-ARC | Handle | |
| 19.1.2 | S2-2503710 | CR | Approval | 23.501 CR6252 (Rel-19, 'F'): Clarification on 5QI for satellite access | CATT | Rel-19 | 5GSAT_Ph3-ARC | Handle | |
| 19.1.2 | S2-2503711 | CR | Approval | 23.203 CR1142 (Rel-19, 'F'): Clarification on QCI for satellite access | CATT | Rel-19 | 5GSAT_Ph3-ARC | Handle | |
| 19.1.2 | - | - | - | KI#2 Store and forward satellite operation | - | - | - | Docs:=56 | - |
| 19.1.2 | - | - | - | KI#2: Liaisons | - | - | - | Docs:=1 | - |
| 19.1.2 | S2-2502825 | LS In | Action | LS from RAN WG3: Reply LS on UE Location Information for NB-IoT NTN | RAN WG3 (R3-250761) | IoT_NTN_enh-Core | Reply to S2-2412665 | ||
| 19.1.2 | - | - | - | KI#2: S&F wait timer related | - | - | - | Docs:=5 | - |
| 19.1.2 | S2-2503071 | CR | Approval | 23.401 CR3905 (Rel-19, 'F'): Clarification on S&F Wait Timer | Nokia | Rel-19 | 5GSAT_Ph3-ARC | Handle - baseline | |
| 19.1.2 | S2-2503275 | CR | Approval | 23.401 CR3909 (Rel-19, 'F'): Clarification on usage of S&F Wait Timer in UE | China Telecom | Rel-19 | 5GSAT_Ph3-ARC | Partially merge into S2-2503071 Focus on when UE starts timer | |
| 19.1.2 | S2-2502879 | CR | Approval | 23.401 CR3899 (Rel-19, 'F'): Refinement of UE behavior and S&F wait timer handling | ZTE | Rel-19 | 5GSAT_Ph3-ARC | Partially merge into S2-2503071 Focus on when UE starts timer | |
| 19.1.2 | S2-2503655 | CR | Approval | 23.401 CR3918 (Rel-19, 'F'): Clarification on S&F timer in NAS Accept and NAS Reject messages | Huawei, HiSilicon | Rel-19 | 5GSAT_Ph3-ARC | Partially merge into S2-2503071 Focus on when UE starts timer | |
| 19.1.2 | S2-2503880 | CR | Approval | 23.401 CR3922 (Rel-19, 'F'): Handling S&F wait timer. | Samsung | Rel-19 | 5GSAT_Ph3-ARC | Partially merge into S2-2503071 Focus on when UE stops timer | |
| 19.1.2 | - | - | - | KI#2: Other clarifications | - | - | - | Docs:=24 | - |
| 19.1.2 | S2-2503886 | CR | Approval | 23.401 CR3924 (Rel-19, 'F'): Editorial fixes and handling when S&F is not enabled by UE. | Samsung | Rel-19 | 5GSAT_Ph3-ARC | Handle | |
| 19.1.2 | S2-2503656 | CR | Approval | 23.401 CR3919 (Rel-19, 'F'): Corrections for S&F Support and operation | Huawei, HiSilicon | Rel-19 | 5GSAT_Ph3-ARC | Handle - baseline | |
| 19.1.2 | S2-2503070 | CR | Approval | 23.401 CR3904 (Rel-19, 'F'): TAU and Service Request procedure correction for S&F | Nokia | Rel-19 | 5GSAT_Ph3-ARC | Merged into S2-2503656? | |
| 19.1.2 | S2-2503265 | CR | Approval | 23.401 CR3906 (Rel-19, 'F'): Clarifications to UE S&F capability and procedures that can include S&F Monitoring list | Ericsson | Rel-19 | 5GSAT_Ph3-ARC | Handle | |
| 19.1.2 | S2-2502880 | CR | Approval | 23.401 CR3900 (Rel-19, 'F'): Clarify the conditions for MME to provide S&F parameters in NAS procedure | ZTE | Rel-19 | 5GSAT_Ph3-ARC | Handle | |
| 19.1.2 | S2-2502882 | CR | Approval | 23.401 CR3902 (Rel-19, 'F'): Align the condition for UE to indicate the S&F capability | ZTE | Rel-19 | 5GSAT_Ph3-ARC | Handle | |
| 19.1.2 | S2-2503415 | CR | Approval | 23.401 CR3914 (Rel-19, 'F'): Procedure updates for S&F | Vivo | Rel-19 | 5GSAT_Ph3-ARC | Handle | |
| 19.1.2 | S2-2503533 | CR | Approval | 23.401 CR3916 (Rel-19, 'F'): MT data transport in CP CIoT EPS Optimisation update for S&F operation | Xiaomi | Rel-19 | 5GSAT_Ph3-ARC | Handle | |
| 19.1.2 | S2-2502883 | CR | Approval | 23.401 CR3903 (Rel-19, 'F'): Update to the GUTI Reallocation procedure | ZTE | Rel-19 | 5GSAT_Ph3-ARC | Handle | |
| 19.1.2 | S2-2503708 | CR | Approval | 23.401 CR3920 (Rel-19, 'F'): Clarification on the deletion of the previous S&F Monitoring List | CATT | Rel-19 | 5GSAT_Ph3-ARC | Handle - baseline | |
| 19.1.2 | S2-2502881 | CR | Approval | 23.401 CR3901 (Rel-19, 'F'): Enhancement of S&F Monitoring List update | ZTE | Rel-19 | 5GSAT_Ph3-ARC | Merge into S2-2503708? | |
| 19.1.2 | S2-2503276 | CR | Approval | 23.401 CR3910 (Rel-19, 'F'): Clarification on Attach reject | China Telecom | Rel-19 | 5GSAT_Ph3-ARC | Handle | |
| 19.1.2 | S2-2503494 | CR | Approval | 23.401 CR3848R3 (Rel-19, 'F'): No Necessity to define UE in S&F mode | MediaTek Inc., Qualcomm Incorporated | Rel-19 | 5GSAT_Ph3-ARC | Handle Revision of (Noted) S2-2502190 | |
| 19.1.2 | S2-2503654 | CR | Approval | 23.401 CR3917 (Rel-19, 'F'): Update Support of Attach with PDN connection for split MME architecture | Huawei, HiSilicon | Rel-19 | 5GSAT_Ph3-ARC | Handle | |
| 19.1.2 | S2-2503753 | CR | Approval | 23.682 CR0498 (Rel-19, 'F'): Clarify the S&F event is sent from SCEF to SCS/AS | Ericsson | Rel-19 | 5GSAT_Ph3-ARC | Handle | |
| 19.1.2 | S2-2503887 | CR | Approval | 23.682 CR0499 (Rel-19, 'F'): Align the terms. | Samsung | Rel-19 | 5GSAT_Ph3-ARC | Handle | |
| 19.1.2 | S2-2503495 | CR | Approval | 23.401 CR3915 (Rel-19, 'F'): Avoid congestion caused by S&F timer | MediaTek Inc. | Rel-19 | FS_5GSAT_Ph3_ARCH | Revised to S2-2503662 | Revised |
| 19.1.2 | S2-2503662 | CR | Approval | 23.401 CR3915R1 (Rel-19, 'F'): Avoid congestion caused by S&F timer | MediaTek Inc. | Rel-19 | 5GSAT_Ph3-ARC | Handle Revision of S2-2503495 | |
| 19.1.2 | S2-2503750 | CR | Approval | 23.401 CR3921 (Rel-19, 'F'): Procedure updates for S&F operation | LG Electronics | Rel-19 | 5GSAT_Ph3-ARC | Handle | |
| 19.1.2 | S2-2503414 | CR | Approval | 23.401 CR3913 (Rel-19, 'F'): Updates to S&F mode transition | Vivo | Rel-19 | 5GSAT_Ph3-ARC | Handle | |
| 19.1.2 | S2-2503363 | CR | Approval | 23.401 CR3911 (Rel-19, 'F'): Transitioning between operation in S&F mode and normal mode | LG Electronics | Rel-19 | 5GSAT_Ph3-ARC | Handle | |
| 19.1.2 | S2-2503881 | CR | Approval | 23.401 CR3923 (Rel-19, 'F'): Handling S&F not allowed. | Samsung | Rel-19 | 5GSAT_Ph3-ARC | Handle | |
| 19.1.2 | S2-2503266 | CR | Approval | 23.401 CR3907 (Rel-19, 'F'): Clarify S1-U not supported by split MME | Ericsson | Rel-19 | 5GSAT_Ph3-ARC | Handle | |
| 19.1.2 | S2-2503267 | CR | Approval | 23.401 CR3908 (Rel-19, 'F'): Clarify PDN connection handling for split MME | Ericsson | Rel-19 | 5GSAT_Ph3-ARC | Handle | |
| 19.1.2 | - | - | - | KI#3 Support of UE-satellite-UE communication | - | - | - | Docs:=10 | - |
| 19.1.2 | S2-2503467 | CR | Approval | 23.502 CR5452 (Rel-19, 'F'): Update on change of BP/ULCL and UP notification procedures for UE-Satellite-UE communication | ETRI | Rel-19 | 5GSAT_Ph3-ARC | Handle | |
| 19.1.2 | S2-2503653 | CR | Approval | 23.501 CR6246 (Rel-19, 'F'): Clarification and correction on UP path event report for UE-satellite-UE communication | Huawei, HiSilicon | Rel-19 | 5GSAT_Ph3-ARC | Handle | |
| 19.1.2 | S2-2503709 | CR | Approval | 23.501 CR6251 (Rel-19, 'F'): Clarification on UE-SAT-UE communication when serving satellite changes | CATT | Rel-19 | 5GSAT_Ph3-ARC | Handle | |
| 19.1.2 | S2-2502917 | CR | Approval | 23.228 CR1608 (Rel-19, 'F'): Update to Initial Call setup and functional support for UE-Satellite-UE communication in IMS | Ericsson | Rel-19 | 5GSAT_Ph3-ARC | Handle | |
| 19.1.2 | S2-2503712 | CR | Approval | 23.228 CR1636 (Rel-19, 'F'): Clarification on UE-Satellite-UE communication procedures | CATT | Rel-19 | 5GSAT_Ph3-ARC | Handle | |
| 19.1.2 | S2-2503583 | CR | Approval | 23.228 CR1629 (Rel-19, 'F'): Update on early media handling in UE-Satellite-UE scenario | Vivo | Rel-19 | 5GSAT_Ph3-ARC | Handle | |
| 19.1.2 | S2-2503652 | CR | Approval | 23.228 CR1630 (Rel-19, 'F'): Clarification on UP path event subscription for UE-satellite-UE communication | Huawei, HiSilicon | Rel-19 | 5GSAT_Ph3-ARC | Handle | |
| 19.1.2 | S2-2503764 | CR | Approval | 23.228 CR1643 (Rel-19, 'F'): Correction on UE-sat-UE communication procedures | China Mobile | Rel-19 | 5GSAT_Ph3-ARC | Handle | |
| 19.1.2 | S2-2502918 | CR | Approval | 23.228 CR1609 (Rel-19, 'F'): Update to Mobility procedures for UE-Satellite-UE communication | Ericsson | Rel-19 | 5GSAT_Ph3-ARC | Handle | |
| 19.1.2 | S2-2502928 | CR | Approval | 23.228 CR1611 (Rel-19, 'F'): Update of target satellite ID notification | ZTE | Rel-19 | 5GSAT_Ph3-ARC | Handle | |
| 19.2.1 | - | - | - | Study on system architecture for next generation real time communication services phase 2 (FS_NG_RTC_Ph2) | - | - | _Not_on_Agenda | Docs:=0 | - |
| 19.2.2 | - | - | - | System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2) | - | - | Dario | Docs:=57 | - |
| 19.2.2 | - | - | - | Liaisons | - | - | - | Docs:=12 | - |
| 19.2.2 | S2-2502847 | LS In | Action | LS from GSMA TSG IMSDCAS: LS to SA WG2 About Requirements Concerning Automatic Resume Where You have Left Off | GSMA TSG IMSDCAS (IMSDCAS022_005v5) | Response drafted in S2-2503170 | |||
| 19.2.2 | S2-2503170 | LS OUT | Approval | [DRAFT] Reply to LS on Automatic Resumption in IMS data channel | Samsung | Rel-19 | NG_RTC_Ph2 | Response to S2-2502847 | |
| 19.2.2 | S2-2502836 | LS In | Action | LS from SA WG3: LS on Privacy and security aspects regarding DC management by the network | SA WG3 (S3-251144) | FS_NG_RTC_SEC_Ph2 | Postpone to next meeting for further spec updating? Responses drafted in S2-2503314, S2-2503685 | ||
| 19.2.2 | S2-2503314 | LS OUT | Approval | [DRAFT] Reply LS on Privacy and security aspects regarding DC management by the network | Qualcomm Incorporated | Rel-19 | NG_RTC_Ph2 | Response to S2-2502836 | |
| 19.2.2 | S2-2503308 | CR | Approval | 23.228 CR1623 (Rel-19, 'F'): Indication of DC initiator for DC create/update/termination | Qualcomm Incorporated | Rel-19 | NG_RTC_Ph2 | ||
| 19.2.2 | S2-2503685 | LS OUT | Approval | [DRAFT] Reply LS on Privacy and security aspects regarding DC management by the network | ZTE | Rel-19 | NG_RTC_Ph2 | Response to S2-2502836 | |
| 19.2.2 | S2-2503684 | CR | Approval | 23.228 CR1635 (Rel-19, 'F'): Additional Information in Adding P2P ADC Procedure | ZTE | Rel-19 | NG_RTC_Ph2 | ||
| 19.2.2 | S2-2502807 | LS In | Action | LS from CT WG1: LS on multiplexing capability negotiation | CT WG1 (C1-250885) | NG_RTC_Ph2 | Handle Responses drafted in S2-2503748, S2-2503763 | ||
| 19.2.2 | S2-2503748 | LS OUT | Approval | [DRAFT] Reply LS on multiplexing capability negotiation | Qualcomm Incorporated | Rel-19 | NG_RTC_Ph2 | Handle Response to S2-2502807 | |
| 19.2.2 | S2-2503763 | LS OUT | Approval | [DRAFT] Reply LS on multiplexing capability negotiation | China Mobile | NG_RTC_Ph2 | Handle Response to S2-2502807 | ||
| 19.2.2 | S2-2503295 | CR | Approval | 23.228 CR1622 (Rel-19, 'F'): Correction on DC multiplexing capability negotiation | Qualcomm Incorporated | Rel-19 | NG_RTC_Ph2 | Handle | |
| 19.2.2 | S2-2502796 | LS In | Action | LS from SA WG4: Reply LS on Clarification of DC Binding Information | SA WG4 (S4-242111) | Reply to S2-2405602. Note Revision of S2-2501374 | |||
| 19.2.2 | - | - | - | KI#1: IMS events for DC communication | - | - | - | Docs:=11 | - |
| 19.2.2 | S2-2502909 | CR | Approval | 23.228 CR1601 (Rel-19, 'F'): KI#1: Corrections to IMS Subscribe/Notify Framework Architecture | Ericsson | Rel-19 | NG_RTC_Ph2 | Handle | |
| 19.2.2 | S2-2503097 | CR | Approval | 23.228 CR1616 (Rel-19, 'F'): NG_RTC_Ph2 KI#1: Subscribe/Notify Procedure correction | Nokia | Rel-19 | NG_RTC_Ph2 | Merge into S2-2502909? | |
| 19.2.2 | S2-2503681 | CR | Approval | 23.228 CR1634 (Rel-19, 'D'): Correction on IMS Service Definition | ZTE | Rel-19 | NG_RTC_Ph2 | Merge into S2-2502909? | |
| 19.2.2 | S2-2502919 | CR | Approval | 23.502 CR5387 (Rel-19, 'F'): KI#1: Immediate Reporting | Ericsson | Rel-19 | NG_RTC_Ph2 | Handle | |
| 19.2.2 | S2-2503552 | CR | Approval | 23.228 CR1624 (Rel-19, 'F'): Clarification on Nhss_ImsEE_Subscribe Immediate reporting | Huawei, HiSilicon | Rel-19 | NG_RTC_Ph2 | Merge into S2-2502919? Check WI Code Capitalization! | |
| 19.2.2 | S2-2502920 | CR | Approval | 23.228 CR1610 (Rel-19, 'F'): KI#1: Event Status Retrieval Procedure | Ericsson | Rel-19 | NG_RTC_Ph2 | Handle | |
| 19.2.2 | S2-2502921 | CR | Approval | 23.502 CR5388 (Rel-19, 'F'): KI#1: Event Status Retrieval Procedure | Ericsson | Rel-19 | NG_RTC_Ph2 | Handle | |
| 19.2.2 | S2-2503758 | CR | Approval | 23.228 CR1588R1 (Rel-19, 'F'): Updates on HSS Nhss_ImsEventExposure service | China Mobile | Rel-19 | NG_RTC_Ph2 | Handle Revision of (Unhandled) S2-2501738 | |
| 19.2.2 | S2-2503580 | CR | Approval | 23.228 CR1544R2 (Rel-19, 'F'): Adding more event filters for ADC media type | Vivo | Rel-19 | NG_RTC_Ph2 | Revision of (Unhandled) S2-2501663 | |
| 19.2.2 | S2-2503701 | CR | Approval | 23.228 CR1576R3 (Rel-19, 'F'): HSS handling for subscription with IMS | Samsung | Rel-19 | NG_RTC_Ph2 | Handle Revision of (Postponed) S2-2502274 | |
| 19.2.2 | S2-2503754 | CR | Approval | 23.228 CR1548R2 (Rel-19, 'F'): Correction of detection criteria for event exposure | China Mobile | Rel-19 | NG_RTC_Ph2 | Revision of (Unhandled) S2-2501731 | |
| 19.2.2 | - | - | - | KI#2: IMS capability exposure for DC session | - | - | - | Docs:=11 | - |
| 19.2.2 | S2-2502913 | CR | Approval | 23.228 CR1604 (Rel-19, 'F'): KI#2: Generalizing Information Retrieval | Ericsson | Rel-19 | NG_RTC_Ph2 | Handle | |
| 19.2.2 | S2-2503695 | DISCUSSION | Information | Discussion on AsInfoGet service operation. | Samsung | Rel-19 | Handle | ||
| 19.2.2 | S2-2503180 | CR | Approval | 23.228 CR1620 (Rel-19, 'F'): Clarification on Nhss_ImsUECM_AsInfoGet | Samsung | Rel-19 | NG_RTC_Ph2 | Merge into S2-2502913? | |
| 19.2.2 | S2-2502914 | CR | Approval | 23.228 CR1605 (Rel-19, 'F'): KI#2: Corrections to DC AS initiated Session Update to add BDC to an existing IMS session | Ericsson | Rel-19 | NG_RTC_Ph2 | Merge into S2-2503098? | |
| 19.2.2 | S2-2503678 | CR | Approval | 23.228 CR1631 (Rel-19, 'F'): Clarification on Adding BDC Procedure | ZTE | Rel-19 | NG_RTC_Ph2 | Merge into S2-2503098? | |
| 19.2.2 | S2-2502915 | CR | Approval | 23.228 CR1606 (Rel-19, 'F'): KI#2: Corrections to DC AS initiated Standalone ADC Session Creation | Ericsson | Rel-19 | NG_RTC_Ph2 | Merge into S2-2503098? | |
| 19.2.2 | S2-2502916 | CR | Approval | 23.228 CR1607 (Rel-19, 'F'): KI#2: Corrections to DC AS initiated IMS Session Update Procedures | Ericsson | Rel-19 | NG_RTC_Ph2 | Merge into S2-2503098? | |
| 19.2.2 | S2-2503098 | CR | Approval | 23.228 CR1617 (Rel-19, 'F'): KI#2: Correction of procedures in clause AG | Nokia | Rel-19 | NG_RTC_Ph2 | Handle | |
| 19.2.2 | S2-2503554 | CR | Approval | 23.228 CR1626 (Rel-19, 'F'): Update IMS DC capability exposure procedure with detailed description | Huawei, HiSilicon | Rel-19 | NG_RTC_Ph2 | Merge into S2-2503098? | |
| 19.2.2 | S2-2503679 | CR | Approval | 23.228 CR1632 (Rel-19, 'F'): Clarification on Establishing IMS Session with Standalone BDC Procedure | ZTE | Rel-19 | NG_RTC_Ph2 | Merge into S2-2503098? | |
| 19.2.2 | S2-2503680 | CR | Approval | 23.228 CR1633 (Rel-19, 'F'): Clarification on Establishing IMS Session with Standalone A2P ADC Procedure | ZTE | Rel-19 | NG_RTC_Ph2 | Merge into S2-2503098? | |
| 19.2.2 | - | - | - | KI#3: DC interworking with MTSI UE | - | - | - | Docs:=5 | - |
| 19.2.2 | S2-2502912 | CR | Approval | 23.228 CR1539R2 (Rel-19, 'F'): KI#3: Update to DC interworking with MTSI UE | Ericsson | Rel-19 | NG_RTC_Ph2 | Revision of (Unhandled) S2-2501504 | |
| 19.2.2 | S2-2503167 | CR | Approval | 23.228 CR1598R1 (Rel-19, 'F'): KI#3: Updates on the ADC Interworking via DC AS procedure | Samsung | Rel-19 | NG_RTC_Ph2 | Handle Revision of (Unhandled) S2-2502136 | |
| 19.2.2 | S2-2503755 | CR | Approval | 23.228 CR1551R2 (Rel-19, 'F'): Updates on procedure and service of DC interworking via DC AS | China Mobile | Rel-19 | NG_RTC_Ph2 | Handle Revision of (Unhandled) S2-2501732 | |
| 19.2.2 | S2-2503169 | CR | Approval | 23.228 CR1600R1 (Rel-19, 'F'): KI#3: Updates on interworking with MTSI UE procedures | Samsung | Rel-19 | NG_RTC_Ph2 | Handle Revision of (Unhandled) S2-2502138 | |
| 19.2.2 | S2-2503581 | CR | Approval | 23.228 CR1465R4 (Rel-19, 'F'): Update on support of DC interworking | Vivo | Rel-19 | NG_RTC_Ph2 | Handle Revision of (Unhandled) S2-2501664 | |
| 19.2.2 | - | - | - | KI#6: Standalone IMS DC Sessions | - | - | - | Docs:=4 | - |
| 19.2.2 | S2-2503555 | CR | Approval | 23.228 CR1627 (Rel-19, 'F'): Correction on standalone data channel description | Huawei, HiSilicon | Rel-19 | NG_RTC_Ph2 | Handle | |
| 19.2.2 | S2-2503582 | CR | Approval | 23.228 CR1546R2 (Rel-19, 'D'): Modification on general description for standalone IMS DC session | Vivo | Rel-19 | NG_RTC_Ph2 | Handle Revision of (Unhandled) S2-2501665 | |
| 19.2.2 | S2-2503697 | CR | Approval | 23.228 CR1577R2 (Rel-19, 'F'): MMTel media removal clarification | Samsung | Rel-19 | NG_RTC_Ph2 | Handle Revision of Unhandled) S2-2502096 | |
| 19.2.2 | S2-2503756 | CR | Approval | 23.228 CR1637 (Rel-19, 'F'): Clarification on PSI configuration on UE | China Mobile | Rel-19 | NG_RTC_Ph2 | Handle | |
| 19.2.2 | - | - | - | KI#8: IMS Avatar Communication | - | - | - | Docs:=9 | - |
| 19.2.2 | S2-2502910 | CR | Approval | 23.228 CR1602 (Rel-19, 'F'): KI#8: Updates to services and operations | Ericsson | Rel-19 | NG_RTC_Ph2 | ||
| 19.2.2 | S2-2502911 | CR | Approval | 23.228 CR1603 (Rel-19, 'F'): KI#8: Corrections to Avatar procedures | Ericsson | Rel-19 | NG_RTC_Ph2 | ||
| 19.2.2 | S2-2503100 | CR | Approval | 23.502 CR5414 (Rel-19, 'F'): Aligning MF selection criteria with 23.228 | Nokia | Rel-19 | NG_RTC_Ph2 | Merge into S2-2503682? | |
| 19.2.2 | S2-2503310 | CR | Approval | 23.502 CR5429 (Rel-19, 'F'): Generlization of MF capabilities registration and discovery | Qualcomm Incorporated | Rel-19 | NG_RTC_Ph2 | Merge into S2-2503682? | |
| 19.2.2 | S2-2503682 | CR | Approval | 23.502 CR5467 (Rel-19, 'F'): Clarification on NRF Service Related to MF | ZTE | Rel-19 | NG_RTC_Ph2 | Handle as baseline? | |
| 19.2.2 | S2-2503178 | CR | Approval | 23.228 CR1619 (Rel-19, 'F'): Clarification on DC AS URL for downloading Avatar ID List | Samsung | Rel-19 | NG_RTC_Ph2 | ||
| 19.2.2 | S2-2503289 | CR | Approval | 23.228 CR1621 (Rel-19, 'F'): MDC2 endpoint indication for Avatar Represenation downloading | Qualcomm Incorporated, Ericsson | Rel-19 | NG_RTC_Ph2 | Handle | |
| 19.2.2 | S2-2503556 | CR | Approval | 23.228 CR1628 (Rel-19, 'F'): Update network centric call flow for Avatar Communication | Huawei, HiSilicon | Rel-19 | NG_RTC_Ph2 | ||
| 19.2.2 | S2-2503757 | CR | Approval | 23.228 CR1638 (Rel-19, 'F'): Clarification on usage of Avatar ID | China Mobile | Rel-19 | NG_RTC_Ph2 | Handle | |
| 19.2.2 | - | - | - | KI#4: Authorization and authentication of third-party identities in IMS sessions | - | - | - | Docs:=1 | - |
| 19.2.2 | S2-2503099 | CR | Approval | 23.228 CR1618 (Rel-19, 'F'): Clarification of the NG_RTC_Ph2 KI#4 procedure description | Nokia | Rel-19 | NG_RTC_Ph2 | ||
| 19.2.2 | - | - | - | KI#7: Multiplexing multiple DC applications over single SCTP connection | - | - | - | Docs:=1 | - |
| 19.2.2 | S2-2503578 | CR | Approval | 23.228 CR1584R1 (Rel-19, 'F'): De-multiplexing ADC to avoid multiplexing ADCs with same stream ID | Vivo | Rel-19 | NG_RTC_Ph2 | Revision of (Unhandled) S2-2501661 | |
| 19.2.2 | - | - | - | General | - | - | - | Docs:=3 | - |
| 19.2.2 | S2-2503553 | CR | Approval | 23.228 CR1625 (Rel-19, 'F'): Update IMS SBA description to align with other specifications | Huawei, HiSilicon | Rel-19 | NG_RTC_Ph2 | ||
| 19.2.2 | S2-2503579 | CR | Approval | 23.228 CR1543R2 (Rel-19, 'D'): Abbreviations of ADC and BDC | Vivo | Rel-19 | NG_RTC_Ph2 | Revision of (Unhandled) S2-2501662 | |
| 19.2.2 | S2-2503683 | CR | Approval | 23.228 CR1557R2 (Rel-19, 'B'): Clarification on DC Application Server | ZTE | Rel-19 | NG_RTC_Ph2 | Revision of (Unhandled) S2-2501950 | |
| 19.3.1 | - | - | - | Extended Reality and Media service (XRM) Phase 2 (FS_XRM_Ph2) | - | - | _Not_on_Agenda | Docs:=0 | - |
| 19.3.2 | - | - | - | Extended Reality and Media service (XRM) Phase 2 (XRM_Ph2) | - | - | Dario | Docs:=67 | - |
| 19.3.2 | - | - | - | Liaisons | - | - | - | Docs:=30 | - |
| 19.3.2 | S2-2502814 | LS In | Action | LS from CT WG4: LS on MoQ Relay Address in UPF Profile | CT WG4 (C4-250627) | XRM_Ph2 | Responses drafted in S2-2503093, S2-2503782 | ||
| 19.3.2 | S2-2503093 | LS OUT | Approval | [DRAFT] LS on on MoQ Relay Address in UPF Profile | Nokia | Rel-19 | XRM_Ph2 | Response to S2-2502814 | |
| 19.3.2 | S2-2503782 | LS OUT | Approval | [DRAFT] LS Reply to CT WG4 on MoQ Relay Address in UPF Profile | China Mobile | Rel-19 | XRM_Ph2 | Handle Response to S2-2502814 | |
| 19.3.2 | S2-2503094 | CR | Approval | 23.501 CR6181 (Rel-19, 'F'): Removal of the MoQ Relay Address in UPF Profile | Nokia | Rel-19 | XRM_Ph2 | Handle | |
| 19.3.2 | S2-2502815 | LS In | Action | LS from CT WG4: LS on Transport Level Marking on N3/N9 | CT WG4 (C4-250629) | XRM_Ph2 | Responses drafted in S2-2503209, S2-2503339, S2-2503438, S2-2503547, S2-2503885 | ||
| 19.3.2 | S2-2503437 | DISCUSSION | Discussion | Discussion on PDU set based DSCP marking. | Nokia | Rel-19 | XRM_Ph2 | Handle | |
| 19.3.2 | S2-2503209 | LS OUT | Approval | [DRAFT] LS Reply on Transport Level Marking on N3/N9 | Ericsson | XRM_Ph2 | Response to S2-2502815 | ||
| 19.3.2 | S2-2503339 | LS OUT | Approval | [DRAFT] LS Reply on Transport Level Marking on N3/N9 | SAMSUNG | Rel-19 | XRM_Ph2 | Response to S2-2502815 | |
| 19.3.2 | S2-2503438 | LS OUT | Approval | [DRAFT] Reply LS on Transport Level Marking based on PDU Set Importance | Nokia | Rel-19 | XRM_Ph2 | Response to S2-2502815 | |
| 19.3.2 | S2-2503547 | LS OUT | Approval | [DRAFT] LS out CT WG4 on Transport Level Marking on N3/N9 | Lenovo | Rel-19 | Handle - use as baseline. . Content to be adapted to agreement Response to S2-2502815 | ||
| 19.3.2 | S2-2503885 | LS OUT | Approval | [DRAFT] LS Reply on Transport Level Marking on N3N9 | Xiaomi | Rel-19 | XRM_Ph2 | Response to S2-2502815 | |
| 19.3.2 | S2-2503208 | CR | Approval | 23.501 CR6193 (Rel-19, 'F'): Triggering of Transport Level Marking based on PDU Set Importance in I-SMF | Ericsson | Rel-19 | XRM_Ph2 | Handle - use as baseline. . Content to be adapted to agreement | |
| 19.3.2 | S2-2503336 | CR | Approval | 23.501 CR6210 (Rel-19, 'F'): Transport level packet marking operation at I-SMF/I-UPF | Samsung | Rel-19 | XRM_Ph2 | ||
| 19.3.2 | S2-2503439 | CR | Approval | 23.501 CR6221 (Rel-19, 'F'): Correction on PDU set based DSCP marking | Nokia | Rel-19 | XRM_Ph2 | ||
| 19.3.2 | S2-2503545 | CR | Approval | 23.501 CR6230 (Rel-19, 'F'): Corrections for 23.501 Transport Level Marking on N3/N9 | Lenovo | Rel-19 | XRM_Ph2 | ||
| 19.3.2 | S2-2503883 | CR | Approval | 23.501 CR6273 (Rel-19, 'F'): XRM_Ph2_KI3 Update of PSI based DSCP Marking | Xiaomi | Rel-19 | XRM_Ph2 | ||
| 19.3.2 | S2-2502820 | LS In | Action | LS from RAN WG2: LS on uplink rate control | RAN WG2 (R2-2501347) | NR_XR_Ph3-Core | Response drafted in S2-2503008, S2-2503148, S2-2503213, S2-2503335, S2-2503393 | ||
| 19.3.2 | S2-2503008 | LS OUT | Approval | [DRAFT] LS reply on uplink rate control for XR service | Lenovo | Rel-19 | Response to S2-2502820 | ||
| 19.3.2 | S2-2503148 | LS OUT | Approval | [DRAFT] LS reply on uplink rate control | vivo | Rel-19 | XRM_Ph2 | Handle - use as baseline. . Content to be adapted to agreement Response to S2-2502820 | |
| 19.3.2 | S2-2503213 | LS OUT | Approval | [DRAFT] LS Reply on uplink rate control | Ericsson | Rel-19 | NR_XR_Ph3-Core | Response to S2-2502820 | |
| 19.3.2 | S2-2503335 | LS OUT | Approval | [DRAFT] LS Reply on uplink rate control | SAMSUNG | Rel-19 | XRM_Ph2 | Response to S2-2502820 | |
| 19.3.2 | S2-2503393 | LS OUT | Approval | [DRAFT] LS reply on uplink rate control | OPPO | Rel-19 | XRM_Ph2 | Response to S2-2502820 | |
| 19.3.2 | S2-2503005 | CR | Approval | 23.501 CR6173 (Rel-19, 'B'): 23.501 Support of uplink rate control for QoS flows at RAN | Lenovo | Rel-19 | XRM_Ph2 | Handle - use as baseline. . Content to be adapted to agreement | |
| 19.3.2 | S2-2503006 | CR | Approval | 23.502 CR5395 (Rel-19, 'B'): 23.502 Support of uplink rate control for QoS flows at RAN | Lenovo | Rel-19 | XRM_Ph2 | ||
| 19.3.2 | S2-2503007 | CR | Approval | 23.503 CR1531 (Rel-19, 'B'): 23.503 Support of uplink rate control for QoS flows at RAN | Lenovo | Rel-19 | XRM_Ph2 | Handle - use as baseline. . Content to be adapted to agreement | |
| 19.3.2 | S2-2503210 | CR | Approval | 23.501 CR6194 (Rel-19, 'C'): Indication of Rate-Adaptable QoS Flows to NG-RAN | Ericsson | Rel-19 | NR_XR_Ph3-Core | ||
| 19.3.2 | S2-2503211 | CR | Approval | 23.503 CR1535 (Rel-19, 'C'): Indication of Rate-Adaptable QoS Flows to NG-RAN | Ericsson | Rel-19 | NR_XR_Ph3-Core | ||
| 19.3.2 | S2-2503212 | CR | Approval | 23.502 CR5419 (Rel-19, 'C'): Indication of Rate-Adaptable QoS Flows to NG-RAN | Ericsson | Rel-19 | NR_XR_Ph3-Core | Handle - use as baseline. . Content to be adapted to agreement | |
| 19.3.2 | S2-2502794 | LS In | Action | LS from RAN WG2: Reply LS on Application-Layer FEC Awareness at RAN | RAN WG2 (R2-2411002) | Reply to S2-2410999 Revision of S2-2501366 | |||
| 19.3.2 | S2-2502800 | LS In | Action | LS from RAN WG3: Reply LS on FS_XRM Ph2 for available data rate report | RAN WG3 (R3-250806) | Rel-19 | XRM_Ph2, NR_XR_Ph3-Core | Reply to S2-2412720 Revision of S2-2501385 | |
| 19.3.2 | - | - | - | KI#9: XR related network information exposure enhancements | - | - | - | Docs:=6 | - |
| 19.3.2 | S2-2503734 | LS OUT | Approval | [DRAFT] LS on Available Bitrate Monitoring | InterDigital Inc. | Rel-19 | XRM_Ph2 | Handle | |
| 19.3.2 | S2-2503732 | CR | Approval | 23.501 CR6255 (Rel-19, 'F'): Available Bitrate Reporting when the Serving RAN Node Changes | InterDigital Inc. | Rel-19 | XRM_Ph2 | Handle | |
| 19.3.2 | S2-2503519 | CR | Approval | 23.501 CR6226 (Rel-19, 'F'): Clarifications for available bitrate exposure | Huawei, HiSilicon | Rel-19 | XRM_Ph2 | Merge into S2-2503732? | |
| 19.3.2 | S2-2503520 | CR | Approval | 23.503 CR1545 (Rel-19, 'F'): Clarifications for available bitrate exposure | Huawei, HiSilicon | Rel-19 | XRM_Ph2 | Handle | |
| 19.3.2 | S2-2503522 | CR | Approval | 23.501 CR6227 (Rel-19, 'F'): Clarifications for rate limitation exposure | Huawei, HiSilicon | Rel-19 | XRM_Ph2 | Handle | |
| 19.3.2 | S2-2503523 | CR | Approval | 23.503 CR1547 (Rel-19, 'F'): Clarifications for rate limitation exposure | Huawei, HiSilicon | Rel-19 | XRM_Ph2 | Handle | |
| 19.3.2 | - | - | - | KI#1: PDU set based QoS handling enhancement | - | - | - | Docs:=16 | - |
| 19.3.2 | S2-2503436 | DISCUSSION | Discussion | Discussion on PDU set QoS explicit indication by NG-RAN or SMF. | Nokia | Rel-19 | XRM_Ph2 | Handle | |
| 19.3.2 | S2-2503433 | CR | Approval | 23.501 CR6219 (Rel-19, 'F'): Support Alternative QoS profile with PDU Set QoS and Notification Control with explicit NG-RAN indication Alt-1 | Nokia | Rel-19 | XRM_Ph2 | Handle - either S2-2503433 or S2-2503434 | |
| 19.3.2 | S2-2503434 | CR | Approval | 23.501 CR6220 (Rel-19, 'F'): Support Alternative QoS profile with PDU Set QoS and Notification Control with explicit SMF indication Alt-2 | Nokia | Rel-19 | XRM_Ph2 | Handle - either S2-2503433 or S2-2503434 | |
| 19.3.2 | S2-2503435 | CR | Approval | 23.503 CR1538 (Rel-19, 'F'): Indication of PDU Set QoS in Notification Control | Nokia | Rel-19 | XRM_Ph2 | Handle | |
| 19.3.2 | S2-2503147 | CR | Approval | 23.501 CR6185 (Rel-19, 'F'): KI#1, Update to Notification Control and Alternative QoS profile with PDU Set QoS | Vivo, Nokia | Rel-19 | XRM_Ph2 | Merge into S2-2503589? | |
| 19.3.2 | S2-2503206 | CR | Approval | 23.503 CR1533 (Rel-19, 'F'): Correction concerning presence of PDU Set Control information without a Protocol Description | Ericsson | Rel-19 | XRM_Ph2 | Handle | |
| 19.3.2 | S2-2503328 | CR | Approval | 23.501 CR6206 (Rel-19, 'F'): Alternative QoS profile handling considering PDU Set QoS parameters | Samsung | Rel-19 | XRM_Ph2 | Merge into S2-2503589? | |
| 19.3.2 | S2-2503329 | CR | Approval | 23.501 CR6207 (Rel-19, 'F'): Notification control on use of PDU Set QoS parameters | Samsung | Rel-19 | XRM_Ph2 | Merge into S2-2503433/4? | |
| 19.3.2 | S2-2503334 | CR | Approval | 23.501 CR6209 (Rel-19, 'F'): PDU Set based handling without PDU Set QoS parameters | Samsung | Rel-19 | XRM_Ph2 | Handle | |
| 19.3.2 | S2-2503524 | CR | Approval | 23.501 CR6228 (Rel-19, 'F'): Clarifications for QoS Notification Control with direction information | Huawei, HiSilicon | Rel-19 | XRM_Ph2 | Merge into S2-2503589? | |
| 19.3.2 | S2-2503525 | CR | Approval | 23.503 CR1548 (Rel-19, 'F'): Clarifications for QoS Notification Control with direction information | Huawei, HiSilicon | Rel-19 | XRM_Ph2 | Handle | |
| 19.3.2 | S2-2503589 | CR | Approval | 23.501 CR6233 (Rel-19, 'F'): QoS Notification Control of PDU Set QoS with only one direction | CATT | Rel-19 | XRM_Ph2 | Handle - use as baseline | |
| 19.3.2 | S2-2503590 | CR | Approval | 23.503 CR1549 (Rel-19, 'F'): Policy Control on QoS Notification Control of PDU Set QoS with only one direction | CATT | Rel-19 | XRM_Ph2 | Merge into S2-2503525? | |
| 19.3.2 | S2-2503804 | CR | Approval | 23.501 CR6259 (Rel-19, 'F'): Add missing XRM condition on PDU Set QoS Notification control | Nokia | Rel-19 | XRM_Ph2 | Merge into S2-2503589? | |
| 19.3.2 | S2-2503882 | CR | Approval | 23.501 CR6272 (Rel-19, 'F'): XRM_Ph2_KI1 Update of PDU Set Information Marking witout DL Set QoS | Xiaomi | Rel-19 | XRM_Ph2 | Handle | |
| 19.3.2 | S2-2503888 | CR | Approval | 23.501 CR6274 (Rel-19, 'F'): Ph2_KI1 Update of QNC with AQP including PDU Set QoS | Xiaomi | Rel-19 | XRM_Ph2 | Merge into S2-2503589? | |
| 19.3.2 | - | - | - | KI#2: PDU Set information identification for end-to-end encrypted XRM traffic | - | - | - | Docs:=3 | - |
| 19.3.2 | S2-2503096 | CR | Approval | 23.501 CR6072R1 (Rel-19, 'F'): Correction on the Support of MoQ | Nokia | Rel-19 | XRM_Ph2 | Handle Revision of (Unhandled) S2-2501470 | |
| 19.3.2 | S2-2503207 | CR | Approval | 23.503 CR1534 (Rel-19, 'F'): MoQ missing from the Protocol Description | Ericsson | Rel-19 | XRM_Ph2 | Handle | |
| 19.3.2 | S2-2503470 | CR | Approval | 23.502 CR5453 (Rel-19, 'F'): Update on PDU session establishment procedure for MoQ | Huawei, HiSilicon | Rel-19 | XRM_Ph2 | Handle | |
| 19.3.2 | - | - | - | KI#3: Leverage PDU Set QoS information for DSCP marking over N3/N9 in the transport network | - | - | - | Docs:=2 | - |
| 19.3.2 | S2-2503226 | CR | Approval | 23.501 CR6091R1 (Rel-19, 'F'): KI#3: Align the mapping of PSI value to DSPC Drop Precedence setting | China Mobile | Rel-19 | XRM_Ph2 | Merge into S2-2503526 Revision of (Unhandled) S2-2501632 | |
| 19.3.2 | S2-2503526 | CR | Approval | 23.501 CR6229 (Rel-19, 'F'): Clarifications for PDU Set QoS information based DSCP marking | Huawei, HiSilicon | Rel-19 | XRM_Ph2 | Handle | |
| 19.3.2 | - | - | - | KI#4: Traffic detection and QoS flow mapping for multiplexed data flows | - | - | - | Docs:=3 | - |
| 19.3.2 | S2-2503228 | CR | Approval | 23.501 CR6095R1 (Rel-19, 'F'): KI#4: Resolve the incorrect multiplex support in NOTE | China Mobile | Rel-19 | XRM_Ph2 | Handle Revision of (Unhandled) S2-2501641 | |
| 19.3.2 | S2-2503517 | CR | Approval | 23.503 CR1544 (Rel-19, 'F'): Clarifications for multiplexed media traffic | Huawei, HiSilicon | Rel-19 | XRM_Ph2 | Handle | |
| 19.3.2 | S2-2503518 | CR | Approval | 23.502 CR5454 (Rel-19, 'F'): Clarifications for multiplexed media traffic | Huawei, HiSilicon | Rel-19 | XRM_Ph2 | Handle | |
| 19.3.2 | - | - | - | KI#5: QoS Handling for Dynamic Traffic Characteristics (Data Boost, etc.) | - | - | - | Docs:=3 | - |
| 19.3.2 | S2-2503521 | CR | Approval | 23.503 CR1546 (Rel-19, 'F'): Clarifications for control of expedited data transfer | Huawei, HiSilicon | Rel-19 | XRM_Ph2 | Handle | |
| 19.3.2 | S2-2503825 | CR | Approval | 23.502 CR5476 (Rel-19, 'F'): Correcting references to TS 23.501 clauses | Nokia | Rel-19 | XRM_Ph2 | Handle | |
| 19.3.2 | S2-2503884 | CR | Approval | 23.503 CR1554 (Rel-19, 'F'): XRM_Ph2_Clarification on the DL Protocol Description | Xiaomi | Rel-19 | XRM_Ph2 | Handle Add Affected Clauses! | |
| 19.3.2 | - | - | - | Multi Modal Awareness at RAN | - | - | - | Docs:=4 | - |
| 19.3.2 | S2-2503560 | CR | Approval | 23.502 CR5455 (Rel-19, 'F'): Update the procedures with Multi-modal service ID | Vivo | Rel-19 | XRM_Ph2 | Merge into S2-2503785? | |
| 19.3.2 | S2-2503783 | CR | Approval | 23.501 CR6258 (Rel-19, 'F'): Clarification on provisioning Multi-modal Service ID to NG-RAN | China Mobile | Rel-19 | XRM_Ph2 | Handle | |
| 19.3.2 | S2-2503785 | CR | Approval | 23.502 CR5474 (Rel-19, 'F'): Support of providing MMSID from 5GC to NG-RAN | China Mobile | Rel-19 | XRM_Ph2 | Handle - use as baseline | |
| 19.3.2 | S2-2503786 | CR | Approval | 23.503 CR1553 (Rel-19, 'F'): Clarification of providing MMSID from 5GC to NG-RAN | China Mobile | Rel-19 | XRM_Ph2 | Handle | |
| 19.4.1 | - | - | - | Feasibility Study on 5GS Enhancement for Energy Efficiency and Energy Saving (FS_EnergySys) | - | - | _Not_on_Agenda | Docs:=0 | - |
| 19.4.2 | - | - | - | 5GS Enhancement for Energy Efficiency and Energy Saving (EnergySys) | - | - | Wanqiang | Docs:=44 | - |
| 19.4.2 | - | - | - | LS In/Out - Renewable energy | - | - | - | Docs:=4 | - |
| 19.4.2 | S2-2502843 | LS In | Action | LS from SA WG5: LS reply to LS on energy information collection from OAM to EIF | SA WG5 (S5-250843) | Energy_OAM_Ph3 | |||
| 19.4.2 | S2-2502817 | LS In | Information | LS from TSG CT: LS reply to LS on energy information collection from OAM to EIF | TSG CT (CP-250253) | Energy_OAM_Ph3, EnergySys | |||
| 19.4.2 | S2-2503639 | CR | Approval | 23.501 CR6243 (Rel-19, 'F'): Solve the editor s note about the renewable energy information | Vivo | Rel-19 | EnergySys | ||
| 19.4.2 | S2-2503806 | CR | Approval | 23.501 CR6261 (Rel-19, 'F'): Support of renewable energy information | Samsung | Rel-19 | EnergySys | ||
| 19.4.2 | - | - | - | Energy Information Collection | - | - | - | Docs:=12 | - |
| 19.4.2 | S2-2503054 | CR | Approval | 23.502 CR5406 (Rel-19, 'F'): Update on Energy Consumption information collection procedure | ETRI | Rel-19 | EnergySys | Handle (Alt.#1) | |
| 19.4.2 | S2-2503586 | DISCUSSION | Agreement | Discussion on the collection and exposure of data usage. | Nokia | Rel-19 | EnergySys | ||
| 19.4.2 | S2-2503588 | CR | Approval | 23.502 CR5458 (Rel-19, 'F'): Energy Consumption information collection procedure clarification | Nokia | Rel-19 | EnergySys | Handle (Alt.#2) | |
| 19.4.2 | S2-2503629 | CR | Approval | 23.501 CR6240 (Rel-19, 'F'): On the report of SMF to EIF for user-plane energy consumption calculation | Huawei, HiSilicon | Rel-19 | EnergySys | Handle (Periodical reporting) Confirm Specification Number - CR states 23.502! | |
| 19.4.2 | S2-2503632 | CR | Approval | 23.501 CR6242 (Rel-19, 'F'): Clarification on the EventExposure service operation of SMF | Huawei, HiSilicon | Rel-19 | EnergySys | Handle as baseline | |
| 19.4.2 | S2-2503628 | CR | Approval | 23.501 CR6239 (Rel-19, 'F'): Report of SMF to EIF for user-plane energy consumption calculation | Huawei, HiSilicon | Rel-19 | EnergySys | Merge into S2-2503632 | |
| 19.4.2 | S2-2503457 | CR | Approval | 23.501 CR6222 (Rel-19, 'F'): Correction on the granularity description and clause reference | ZTE | Rel-19 | EnergySys | ||
| 19.4.2 | S2-2503572 | CR | Approval | 23.502 CR5456 (Rel-19, 'F'): Correction on energy consumption information collection and exposure | CATT | Rel-19 | EnergySys | Handle as baseline | |
| 19.4.2 | S2-2503056 | CR | Approval | 23.502 CR5408 (Rel-19, 'D'): Editorial update on Energy Consumption information collection and exposure | ETRI | Rel-19 | EnergySys | Merge into S2-2503572 | |
| 19.4.2 | S2-2503458 | CR | Approval | 23.502 CR5448 (Rel-19, 'F'): Procedure Correction on the Energy Consumption information collection | ZTE | Rel-19 | EnergySys | Merge into S2-2503572 | |
| 19.4.2 | S2-2503621 | CR | Approval | 23.502 CR5463 (Rel-19, 'F'): Update the procedure and EIF service | Vivo | Rel-19 | EnergySys | Merge into S2-2503572 | |
| 19.4.2 | S2-2503459 | CR | Approval | 23.501 CR6223 (Rel-19, 'F'): Clarification on the OAM input | ZTE | Rel-19 | EnergySys | ||
| 19.4.2 | - | - | - | SMF/gNB change, etc. | - | - | - | Docs:=8 | - |
| 19.4.2 | S2-2503805 | CR | Approval | 23.501 CR6260 (Rel-19, 'F'): Energy consumption information collection for new PDU Session | Samsung | Rel-19 | EnergySys | Handle as baseline | |
| 19.4.2 | S2-2503630 | CR | Approval | 23.501 CR6241 (Rel-19, 'F'): Update on EC collection upon PDU Session management | Huawei, HiSilicon | Rel-19 | EnergySys | Merge into S2-2503805 | |
| 19.4.2 | S2-2503807 | CR | Approval | 23.501 CR6262 (Rel-19, 'F'): Update on the energy consumption information collection | Vivo | Rel-19 | EnergySys | gNB change | |
| 19.4.2 | S2-2503631 | CR | Approval | 23.502 CR5464 (Rel-19, 'F'): On the report of SMF to EIF for user-plane energy consumption calculation | Huawei, HiSilicon | Rel-19 | EnergySys | Handle as baseline | |
| 19.4.2 | S2-2503781 | CR | Approval | 23.502 CR5473 (Rel-19, 'F'): Energy subscription termination and event exposure in SMF | China Mobile | Rel-19 | EnergySys | Merge into S2-2503631 | |
| 19.4.2 | S2-2503809 | CR | Approval | 23.502 CR5475 (Rel-19, 'F'): Collection of energy consumption information for new PDU session | Samsung | Rel-19 | EnergySys | Merge into S2-2503631 | |
| 19.4.2 | S2-2503737 | CR | Approval | 23.501 CR6256 (Rel-19, 'F'): Energy consumption information for access type | Samsung | Rel-19 | EnergySys | ||
| 19.4.2 | S2-2503740 | CR | Approval | 23.502 CR5470 (Rel-19, 'F'): Energy consumption information for access type | Samsung | Rel-19 | EnergySys | ||
| 19.4.2 | - | - | - | Nsmf_EventExposure | - | - | - | Docs:=5 | - |
| 19.4.2 | S2-2503593 | CR | Approval | 23.502 CR5459 (Rel-19, 'F'): SMF exposure service clarification for Energy Consumption information collection | Nokia | Rel-19 | EnergySys | Handle as baseline | |
| 19.4.2 | S2-2503055 | CR | Approval | 23.502 CR5407 (Rel-19, 'F'): Update on SMF event exposure to support Energy Consumption information | ETRI | Rel-19 | EnergySys | Merge into S2-2503593 | |
| 19.4.2 | S2-2503633 | CR | Approval | 23.502 CR5288R2 (Rel-19, 'F'): Clarification on the EventExposure service operation of SMF | Huawei, HiSilicon | Rel-19 | EnergySys | Merge into S2-2503593 Revision of (Unhandled) S2-2501563 | |
| 19.4.2 | S2-2503650 | CR | Approval | 23.502 CR5352R1 (Rel-19, 'F'): Update on SMF services | Vivo | Rel-19 | EnergySys | Merge into S2-2503593 Revision of (Noted) S2-2501716 | |
| 19.4.2 | S2-2503736 | CR | Approval | 23.502 CR5469 (Rel-19, 'F'): Clarifications on SMF event for information for energy consumption calculation | Samsung | Rel-19 | EnergySys | Merge into S2-2503593 | |
| 19.4.2 | - | - | - | Energy Consumption calculation | - | - | - | Docs:=2 | - |
| 19.4.2 | S2-2503121 | DISCUSSION | Discussion | Discussion on Energy Consumption model. | NTT DOCOMO | Rel-19 | EnergySys | ||
| 19.4.2 | S2-2503122 | CR | Approval | 23.501 CR6182 (Rel-19, 'F'): Correction of Energy Consumption Model | NTT DOCOMO | Rel-19 | EnergySys | ||
| 19.4.2 | - | - | - | Energy Information Exposure | - | - | - | Docs:=7 | - |
| 19.4.2 | S2-2503124 | CR | Approval | 23.501 CR6183 (Rel-19, 'F'): Clarification on the reporting period of energy-related information | NTT DOCOMO | Rel-19 | EnergySys | ||
| 19.4.2 | S2-2503651 | CR | Approval | 23.501 CR6245 (Rel-19, 'F'): Update on the energy consumption information exposure | Vivo | Rel-19 | EnergySys | ||
| 19.4.2 | S2-2503595 | CR | Approval | 23.501 CR6234 (Rel-19, 'F'): EIF exposure serice definition clarification | Nokia | Rel-19 | EnergySys | ||
| 19.4.2 | S2-2503601 | CR | Approval | 23.502 CR5461 (Rel-19, 'F'): EIF exposure service definition clarification | Nokia | Rel-19 | EnergySys | ||
| 19.4.2 | S2-2503460 | CR | Approval | 23.502 CR5449 (Rel-19, 'F'): Resolve the EN in the EIF service | ZTE | Rel-19 | EnergySys | ||
| 19.4.2 | S2-2503731 | CR | Approval | 23.501 CR6254 (Rel-19, 'F'): EIF discvoery and selection | Samsung | Rel-19 | EnergySys | ||
| 19.4.2 | S2-2503735 | CR | Approval | 23.502 CR5468 (Rel-19, 'F'): EIF discvoery and selection | Samsung | Rel-19 | EnergySys | ||
| 19.4.2 | - | - | - | BDT | - | - | - | Docs:=6 | - |
| 19.4.2 | S2-2503456 | CR | Approval | 23.503 CR1539 (Rel-19, 'F'): Clarification on the BDT policy decision | ZTE | Rel-19 | EnergySys | Handle (Alt.#1) | |
| 19.4.2 | S2-2503627 | CR | Approval | 23.503 CR1492R4 (Rel-19, 'F'): Corrections for energy saving related AF input on BDT policy negotiation | Huawei, HiSilicon, NTT DOCOMO, KDDI | Rel-19 | EnergySys | Handle (Alt.#2) Revision of (Unhandled) S2-2501566 | |
| 19.4.2 | S2-2503780 | CR | Approval | 23.502 CR5472 (Rel-19, 'F'): Alignment of Energy indicator in BDT policy | China Mobile | Rel-19 | EnergySys | Handle as baseline | |
| 19.4.2 | S2-2503455 | CR | Approval | 23.502 CR5447 (Rel-19, 'F'): Adding Energy indication to BDT procedure and service operation | ZTE | Rel-19 | EnergySys | Merge into S2-2503780 | |
| 19.4.2 | S2-2503637 | CR | Approval | 23.502 CR5465 (Rel-19, 'F'): Update the procedure for BDT policy decisions | Vivo | Rel-19 | EnergySys | Merge into S2-2503780 | |
| 19.4.2 | S2-2503125 | CR | Approval | 23.502 CR5240R2 (Rel-19, 'F'): Negotiation for future background data transfer considering energy | NTT DOCOMO, Toyota, KDDI | Rel-19 | EnergySys | Revision of (Merged and Postponed) S2-2502001 | |
| 19.5.1 | - | - | - | Study on MPS for IMS Messaging and SMS services (FS_MPS4msg) | - | - | _Not_on_Agenda | Docs:=0 | - |
| 19.5.2 | - | - | - | MPS for IMS Messaging and SMS services (MPS4msg) | - | - | (No documents) | Docs:=0 | - |
| 19.6.1 | - | - | - | Study on Architecture Enhancements for Vehicle Mounted Relays Phase 2 (FS_VMR_Ph2) | - | - | _Not_on_Agenda | Docs:=0 | - |
| 19.6.2 | - | - | - | Architecture Enhancements for Vehicle Mounted Relays Phase 2 (VMR_Ph2) | - | - | Andy | Docs:=36 | - |
| 19.6.2 | - | - | - | LS from SA WG5 on MWAB-gNB configuration | - | - | - | Docs:=5 | - |
| 19.6.2 | S2-2502844 | LS In | Action | LS from SA WG5: LS on MWAB-gNB Configurations | SA WG5 (S5-251090) | AdNRM_Ph3 | Replied in S2-2503817 Responses drafted in S2-2502975, S2-2503817, S2-2503873 | ||
| 19.6.2 | S2-2502975 | LS OUT | Approval | [DRAFT] Reply LS on MWAB-gNB Configuration | Ericsson | Rel-19 | VMR_Ph2 | Merge into S2-2503817? Response to S2-2502844 | |
| 19.6.2 | S2-2503817 | LS OUT | Approval | [DRAFT] Reply LS on MWAB-gNB Configurations | Qualcomm Incorporated | Rel-19 | VMR_Ph2 | HANDLE. Use as the baseline. Response to S2-2502844 | |
| 19.6.2 | S2-2503873 | LS OUT | Approval | [DRAFT] Reply LS on MWAB-gNB Configurations | Samsung | Rel-19 | Merge into S2-2503817? Response to S2-2502844 | ||
| 19.6.2 | S2-2503872 | CR | Approval | 23.501 CR6270 (Rel-19, 'F'): Clarification on MWAB URSP processing | Samsung | Rel-19 | VMR_Ph2 | HANDLE | |
| 19.6.2 | - | - | - | LS from CT WG1 on PWS support | - | - | - | Docs:=16 | - |
| 19.6.2 | S2-2502805 | LS In | Action | LS from CT WG1: LS on PWS enhancements for MWAB and MBSR | CT WG1 (C1-250820) | VMR_Ph2, VMR | Responses drafted in S2-2502976, S2-2503351 | ||
| 19.6.2 | S2-2502976 | LS OUT | Approval | [DRAFT] Reply LS on PWS enhancement for MWAB and MBSR | Ericsson | Rel-19 | VMR_Ph2, VMR | HANDLE. Use as the baseline. Response to S2-2502805 | |
| 19.6.2 | S2-2503351 | LS OUT | Approval | [DRAFT] Reply LS on PWS enhancements for MWAB and MBSR | Huawei, HiSilicon | Rel-19 | VMR_Ph2, VMR | Merge into S2-2502976? Response to S2-2502805 | |
| 19.6.2 | S2-2502981 | CR | Approval | 23.501 CR6171 (Rel-18, 'F'): PWS handling with Additional ULI | Ericsson, Qualcomm Incorporated | Rel-18 | VMR | Moved to 19.6.2. Merge into S2-2503356? | |
| 19.6.2 | S2-2503356 | CR | Approval | 23.501 CR6211 (Rel-18, 'F'): PWS enhancements for MBSR | Huawei, HiSilicon | Rel-18 | VMR | HANDLE. Baseline for Rel-18 TS 23.501. | |
| 19.6.2 | S2-2502977 | CR | Approval | 23.501 CR6087R1 (Rel-19, 'F'): PWS handling with Additional ULI | Ericsson, Qualcomm Incorporated | Rel-19 | VMR_Ph2, VMR | HANDLE. Baseline for Rel-19 TS 23.501. Revision of (Postponed) S2-2501597 | |
| 19.6.2 | S2-2503357 | CR | Approval | 23.501 CR6212 (Rel-19, 'F'): PWS enhancements for MBSR and MWAB | Huawei, HiSilicon | Rel-19 | VMR_Ph2 | Merge into S2-2502977? | |
| 19.6.2 | S2-2502978 | CR | Approval | 23.502 CR5341R1 (Rel-19, 'F'): PWS handling update for VMR | Ericsson, Qualcomm Incorporated | Rel-19 | VMR_Ph2, VMR | Merge into S2-2503443? Revision of (Postponed) S2-2501598 | |
| 19.6.2 | S2-2502982 | CR | Approval | 23.502 CR5392 (Rel-18, 'F'): PWS handling update for VMR | Ericsson, Qualcomm Incorporated | Rel-18 | VMR | Moved to 19.6.2. Merge into S2-2503184? | |
| 19.6.2 | S2-2503184 | CR | Approval | 23.502 CR5416 (Rel-18, 'F'): Removal of text for PWS | Nokia | Rel-18 | VMR | HANDLE. Baseline for Rel-18 TS 23.502 | |
| 19.6.2 | S2-2503185 | CR | Approval | 23.502 CR5417 (Rel-19, 'F'): Removal of text for PWS | Nokia | Rel-19 | VMR, VMR_Ph2 | Merge into S2-2503443? | |
| 19.6.2 | S2-2503354 | CR | Approval | 23.502 CR5434 (Rel-18, 'F'): PWS enhancements for MBSR | Huawei, HiSilicon | Rel-18 | VMR | Merge into S2-2503184? | |
| 19.6.2 | S2-2503355 | CR | Approval | 23.502 CR5435 (Rel-19, 'F'): PWS enhancements for MBSR and MWAB | Huawei, HiSilicon | Rel-19 | VMR_Ph2 | Merge into S2-2503443? | |
| 19.6.2 | S2-2503440 | CR | Approval | 23.502 CR5445 (Rel-18, 'F'): PWS enhancements for MWAB and MBSR | Samsung | Rel-18 | VMR_Ph2 | Merge into S2-2503184? | |
| 19.6.2 | S2-2503443 | CR | Approval | 23.502 CR5446 (Rel-19, 'F'): PWS enhancements for MWAB and MBSR | Samsung | Rel-19 | VMR_Ph2 | HANDLE. Baseline for Rel-19 TS 23.502 | |
| 19.6.2 | S2-2502979 | CR | Approval | 23.501 CR6169 (Rel-19, 'F'): MWAB-gNB indication to AMF | Ericsson | Rel-19 | VMR_Ph2 | HANDLE | |
| 19.6.2 | - | - | - | LS from RAN WG3 on Additional ULI | - | - | - | Docs:=5 | - |
| 19.6.2 | S2-2502830 | LS In | Action | LS from RAN WG3: Reply LS on FS_VMR_Ph2 solution impacts to RAN (Additional ULI) | RAN WG3 (R3-250901) | FS_VMR_Ph2, NR_WAB_5GFemto-Core | Replied in S2-2503816 Responses drafted in S2-2503646, S2-2503816 | ||
| 19.6.2 | S2-2503646 | LS OUT | Approval | [DRAFT] Reply LS on FS_VMR_Ph2 solution impacts to RAN (Additional ULI) | CATT | Rel-19 | VMR_Ph2 | Merge into S2-2503816? Response to S2-2502830 | |
| 19.6.2 | S2-2503816 | LS OUT | Approval | [DRAFT] Reply LS on FS_VMR_Ph2 solution impacts to RAN (Additional ULI) | Qualcomm Incorporated | Rel-19 | VMR_Ph2 | HANDLE. Baseline for LS Out Response to S2-2502830 | |
| 19.6.2 | S2-2503645 | CR | Approval | 23.501 CR6244 (Rel-19, 'F'): Additional ULI Update | CATT | Rel-19 | VMR_Ph2 | Merge into S2-2503813? | |
| 19.6.2 | S2-2503813 | CR | Approval | 23.501 CR6264 (Rel-19, 'F'): Correction of the Additional ULI mapping conditions for MWAB | Qualcomm Incorporated, Ericsson, Nokia, Huawei, HiSilicon, LG Electronics | Rel-19 | VMR_Ph2 | HANDLE. Baseline for CR. | |
| 19.6.2 | - | - | - | LS from RAN WG3 on Location Service support | - | - | - | Docs:=1 | - |
| 19.6.2 | S2-2502831 | LS In | Action | LS from RAN WG3: Reply LS on Support of Location Service Involving WAB-Nodes | RAN WG3 (R3-250902) | VMR_Ph2, NR_WAB_5GFemto-Core | Reply to S2-2412625. To be NOTED | ||
| 19.6.2 | - | - | - | Misc. corrections | - | - | - | Docs:=9 | - |
| 19.6.2 | S2-2503183 | CR | Approval | 23.501 CR6189 (Rel-19, 'F'): Add MWAB indication to NEF monitoring events | Nokia | Rel-19 | VMR_Ph2 | HANDLE Confirm Specification Number - CR states 23.502! | |
| 19.6.2 | S2-2503177 | CR | Approval | 23.501 CR6187 (Rel-19, 'F'): Clarification of the network slicing clause | Nokia, China Telecom | Rel-19 | VMR_Ph2 | HANDLE | |
| 19.6.2 | S2-2503818 | CR | Approval | 23.273 CR0730 (Rel-19, 'F'): Correction of the 5GC-MT-LR procedure involving MWAB | Qualcomm Incorporated, Nokia | Rel-19 | VMR_Ph2 | HANDLE | |
| 19.6.2 | S2-2502980 | CR | Approval | 23.501 CR6170 (Rel-19, 'F'): MWAB-gNB authorization handling update | Ericsson | Rel-19 | VMR_Ph2 | HANDLE | |
| 19.6.2 | S2-2503018 | CR | Approval | 23.501 CR6099R1 (Rel-19, 'F'): Clarification on MWAB-UE aspect | LG Electronics | Rel-19 | VMR_Ph2 | HANDLE Revision of (Unhandled) S2-2501694 | |
| 19.6.2 | S2-2503168 | CR | Approval | 23.501 CR6186 (Rel-19, 'F'): Clarification of mobility clause | Nokia | Rel-19 | VMR_Ph2 | HANDLE | |
| 19.6.2 | S2-2503181 | CR | Approval | 23.501 CR6188 (Rel-19, 'F'): Handling of BH PDU session in the network | Nokia | Rel-19 | VMR_Ph2 | HANDLE Confirm CR Number - CR states xxxx! | |
| 19.6.2 | S2-2503352 | CR | Approval | 23.501 CR6128R1 (Rel-19, 'F'): MWAB-UE authorization | Huawei, HiSilicon | Rel-19 | VMR_Ph2 | HANDLE Revision of (Unhandled) S2-2501871 | |
| 19.6.2 | S2-2503353 | CR | Approval | 23.501 CR6127R1 (Rel-19, 'F'): Backhaul PDU Session handling for MWAB | Huawei, HiSilicon | Rel-19 | VMR_Ph2 | HANDLE Revision of (Unhandled) S2-2501870 | |
| 19.7.1 | - | - | - | Study on System Enhancement for Proximity-based Services in 5GS – Phase 3 (FS_5G_ProSe_Ph3) | - | - | _Not_on_Agenda | Docs:=0 | - |
| 19.7.2 | - | - | - | System Enhancement for Proximity-based Services in 5GS – Phase 3 (5G_ProSe_Ph3) | - | - | Andy | Docs:=11 | - |
| 19.7.2 | - | - | - | General Corrections | - | - | - | Docs:=7 | - |
| 19.7.2 | S2-2502885 | CR | Approval | 23.304 CR0543 (Rel-19, 'F'): Removing QoS EN | KPN N.V. | Rel-19 | 5G_ProSe_Ph3 | Handle | |
| 19.7.2 | S2-2502968 | CR | Approval | 23.304 CR0545 (Rel-19, 'F'): Updates to Common identifiers for 5G ProSe UE-to-Network Relay | Ericsson, AT&T | Rel-19 | 5G_ProSe_Ph3 | Handle | |
| 19.7.2 | S2-2503052 | CR | Approval | 23.304 CR0547 (Rel-19, 'F'): Policy/Parameter provisioning to support PWS for 5G ProSe multi-hop U2N Relay | OPPO | Rel-19 | 5G_ProSe_Ph3 | Handle | |
| 19.7.2 | S2-2503141 | CR | Approval | 23.304 CR0548 (Rel-19, 'F'): Clarification on Multi-hop U2N and U2U Discovery | Huawei, HiSilicon | Rel-19 | 5G_ProSe_Ph3 | Handle | |
| 19.7.2 | S2-2503142 | CR | Approval | 23.304 CR0549 (Rel-19, 'F'): Clarification on Relay reselection for 5G ProSe Remote UE with 5G ProSe Multi-hop UE-to-Network Relays | Huawei, HiSilicon | Rel-19 | 5G_ProSe_Ph3 | Handle Check Affected Clauses (in other comments)! | |
| 19.7.2 | S2-2503203 | CR | Approval | 23.304 CR0550 (Rel-19, 'F'): Updates to the 5G ProSe Multi-hop UE-to-UE Relay Discovery procedure | Ericsson, AT&T, FirstNet, Qualcomm | Rel-19 | 5G_ProSe_Ph3 | Handle | |
| 19.7.2 | S2-2503824 | CR | Approval | 23.304 CR0553 (Rel-19, 'F'): End UE RSC-Bounded Routing | Nokia, Nokia Shanghai Bell | Rel-19 | 5G_ProSe_Ph3 | Handle | |
| 19.7.2 | - | - | - | Layer 2 | - | - | - | Docs:=2 | - |
| 19.7.2 | S2-2503015 | CR | Approval | 23.304 CR0546 (Rel-19, 'F'): Introduction of Multi-hop Layer-2 UE-to-Network relaying | CATT | Rel-19 | 5G_ProSe_Ph3 | Handle | |
| 19.7.2 | S2-2503374 | CR | Approval | 23.502 CR5438 (Rel-19, 'F'): Adding Layer-2 Multi-hop U2N relaying aspects to UE Subscription data | LG Electronics | Rel-19 | 5G_ProSe_Ph3 | Handle | |
| 19.7.2 | - | - | - | Editorial corrections | - | - | - | Docs:=2 | - |
| 19.7.2 | S2-2502886 | CR | Approval | 23.304 CR0544 (Rel-19, 'D'): Editorial corrections | KPN N.V. | Rel-19 | FS_5G_ProSe_Ph2 | Handle | |
| 19.7.2 | S2-2503279 | CR | Approval | 23.304 CR0551 (Rel-19, 'D'): Editorial correction on Multi-hop UE-to-UE Relay | China Telecom | Rel-19 | 5G_ProSe_Ph3 | Handle | |
| 19.8.1 | - | - | - | Study on User Identities and Authentication Architecture (FS_UIA_ARC) | - | - | _Not_on_Agenda | Docs:=0 | - |
| 19.8.2 | - | - | - | Identifying non-3GPP Devices Connecting behind a UE or 5G-RG (UIA_ARC) | - | - | Wanqiang | Docs:=41 | - |
| 19.8.2 | - | - | - | LS From CT WG1 and Draft Replies | - | - | - | Docs:=9 | - |
| 19.8.2 | S2-2502806 | LS In | Action | LS from CT WG1: LS on support for multiple non-3GPP device identifiers | CT WG1 (C1-250822) | UIA_ARC | Handle Responses drafted in S2-2502872, S2-2502907, S2-2502985, S2-2503053, S2-2503461, S2-2503604, S2-2503858, S2-2503864 | ||
| 19.8.2 | S2-2502872 | LS OUT | Approval | [DRAFT] Reply LS on support for multiple non-3GPP device identifiers | Nokia | Rel-19 | UIA_ARC | Response to S2-2502806 | |
| 19.8.2 | S2-2502907 | LS OUT | Approval | [DRAFT] LS reply on support for multiple non-3GPP device identifiers | Ericsson will be SA2 | Rel-19 | UIA_ARC | Handle - LS Reply Baseline Response to S2-2502806 | |
| 19.8.2 | S2-2502985 | LS OUT | Approval | [DRAFT] Reply LS on support for multiple non-3GPP device identifiers | Google Korea LLC | Rel-19 | UIA_ARC | Response to S2-2502806 | |
| 19.8.2 | S2-2503053 | LS OUT | Approval | [DRAFT] Reply to LS on support for multiple non-3GPP device identifiers | Samsung TO BE SA2 | Rel-19 | Response to S2-2502806 | ||
| 19.8.2 | S2-2503461 | LS OUT | Approval | [DRAFT] Reply LS on support for multiple non-3GPP device identifiers | ZTE | Rel-19 | UIA_ARC | Response to S2-2502806 | |
| 19.8.2 | S2-2503604 | LS OUT | Approval | [DRAFT] UIA LSout on support for multiple non-3GPP device identifiers | Huawei, HiSilicon | Rel-19 | UIA_ARC | Response to S2-2502806 | |
| 19.8.2 | S2-2503858 | LS OUT | Approval | [DRAFT] Reply LS on support for multiple non-3GPP device identifiers | CSCN | Rel-19 | UIA_ARC | Response to S2-2502806 | |
| 19.8.2 | S2-2503864 | LS OUT | Approval | [DRAFT] LS Reply on support for multiple non-3GPP device identifiers | Intel | Response to S2-2502806 | |||
| 19.8.2 | - | - | - | Addressing the CT WG1 LS - 23.501 | - | - | - | Docs:=4 | - |
| 19.8.2 | S2-2503330 | CR | Approval | 23.501 CR6208 (Rel-19, 'F'): Inclusion of several Non-3GPP Device Identifiers | Nokia, InterDigital Inc., LG Electronics | Rel-19 | UIA_ARC | Handle - 23.501 Baseline | |
| 19.8.2 | S2-2503605 | CR | Approval | 23.501 CR6236 (Rel-19, 'F'): Clarificaiton on supporting multiple non-3GPP device identifiers | Huawei, HiSilicon | Rel-19 | UIA_ARC | ||
| 19.8.2 | S2-2502986 | CR | Approval | 23.501 CR6172 (Rel-19, 'F'): Providing device identifier information in PDU session modification request | Rel-19 | UIA_ARC | |||
| 19.8.2 | S2-2503462 | CR | Approval | 23.501 CR6224 (Rel-19, 'F'): Clarification on the non-3gpp device identifier activation and removal | ZTE, Xiaomi | Rel-19 | UIA_ARC | ||
| 19.8.2 | - | - | - | Addressing the CT WG1 LS - 23.502 | - | - | - | Docs:=5 | - |
| 19.8.2 | S2-2502902 | CR | Approval | 23.502 CR5383 (Rel-19, 'F'): QoS differention for multiple Non-3GPP devices | Ericsson, AT&T | Rel-19 | UIA_ARC | Handle - 23.501 Baseline | |
| 19.8.2 | S2-2503331 | CR | Approval | 23.502 CR5432 (Rel-19, 'F'): Inclusion of several Non-3GPP Device Identifiers | Nokia, InterDigital Inc., LG Electronics | Rel-19 | UIA_ARC | ||
| 19.8.2 | S2-2503606 | CR | Approval | 23.502 CR5462 (Rel-19, 'F'): Clarificaiton on supporting multiple non-3GPP device identifiers | Huawei, HiSilicon | Rel-19 | UIA_ARC | ||
| 19.8.2 | S2-2502987 | CR | Approval | 23.502 CR5393 (Rel-19, 'F'): Providing device identifier information in PDU session modification request | Rel-19 | UIA_ARC | |||
| 19.8.2 | S2-2503463 | CR | Approval | 23.502 CR5450 (Rel-19, 'F'): Clarification on the non-3gpp device identifier activation and removal | ZTE, Xiaomi | Rel-19 | UIA_ARC | ||
| 19.8.2 | - | - | - | Addressing the CT WG1 LS - 23.503 | - | - | - | Docs:=4 | - |
| 19.8.2 | S2-2503607 | CR | Approval | 23.503 CR1551 (Rel-19, 'F'): Clarificaiton on supporting multiple non-3GPP device identifiers | Huawei, HiSilicon | Rel-19 | UIA_ARC | Handle - 23.503 Baseline | |
| 19.8.2 | S2-2502903 | CR | Approval | 23.503 CR1528 (Rel-19, 'F'): Results of QoS differention for multiple Non-3GPP devices | Ericsson, AT&T | Rel-19 | UIA_ARC | Missing Affected Clauses! | |
| 19.8.2 | S2-2503332 | CR | Approval | 23.503 CR1536 (Rel-19, 'F'): Inclusion of several Non-3GPP Device Identifiers | Nokia, InterDigital Inc., LG Electronics | Rel-19 | UIA_ARC | ||
| 19.8.2 | S2-2502988 | CR | Approval | 23.503 CR1529 (Rel-19, 'F'): Providing device identifier information in PDU session modification request | Rel-19 | UIA_ARC | |||
| 19.8.2 | - | - | - | Addressing the CT WG1 LS - Removal from Subscription Only | - | - | - | Docs:=2 | - |
| 19.8.2 | S2-2502905 | CR | Approval | 23.502 CR5385 (Rel-19, 'F'): Handling removal of Non-3GPP Device Identifiers from UDR | Ericsson, AT&T | Rel-19 | UIA_ARC | Handle Missing Affected Clauses! | |
| 19.8.2 | S2-2503464 | CR | Approval | 23.503 CR1540 (Rel-19, 'F'): Clarification on the non-3gpp device identifier activation and removal | ZTE, Xiaomi | Rel-19 | UIA_ARC | ||
| 19.8.2 | - | - | - | How the UE Stops QoS Differentiation for a Device | - | - | - | Docs:=2 | - |
| 19.8.2 | S2-2503074 | CR | Approval | 23.501 CR6180 (Rel-19, 'F'): Clarifications on SM signalling including non-3GPP device identifiers for QoS differentiation | Apple | Rel-19 | UIA_ARC | Handle | |
| 19.8.2 | S2-2503075 | CR | Approval | 23.502 CR5409 (Rel-19, 'F'): Clarifications for SM signalling including non-3GPP device identifiers for QoS differentiation | Apple | Rel-19 | UIA_ARC | ||
| 19.8.2 | - | - | - | HR Roaming | - | - | - | Docs:=2 | - |
| 19.8.2 | S2-2503000 | CR | Approval | 23.503 CR1530 (Rel-19, 'F'): Adding a Reference to the Home Routed Roaming PDU Session Modification Procedure | InterDigital Inc., LG Electronics, Samsung, Nokia | Rel-19 | UIA_ARC | Handle | |
| 19.8.2 | S2-2503001 | CR | Approval | 23.502 CR5394 (Rel-19, 'F'): Updating the Nsmf_PDUSession_Update service description to account for non-3GPP device connection information | InterDigital Inc., LG Electronics, Samsung, Nokia | Rel-19 | UIA_ARC | Handle | |
| 19.8.2 | - | - | - | Npcf_SMPolicyControl_Create service operation correction. | - | - | - | Docs:=2 | - |
| 19.8.2 | S2-2503596 | CR | Approval | 23.502 CR5460 (Rel-19, 'F'): Update on Non-3GPP Device Identifier(s) Information provisioning and policy control | Xiaomi | Rel-19 | UIA_ARC | Handle Baseline | |
| 19.8.2 | S2-2502904 | CR | Approval | 23.502 CR5384 (Rel-19, 'F'): Removing Non-3GPP Device Connection Information from SM policy control create | Ericsson | Rel-19 | UIA_ARC | Merge into S2-2503596? | |
| 19.8.2 | - | - | - | Others | - | - | - | Docs:=7 | - |
| 19.8.2 | S2-2503465 | CR | Approval | 23.502 CR5451 (Rel-19, 'F'): Clarification on the subscription to UDR | ZTE | Rel-19 | UIA_ARC | Handle | |
| 19.8.2 | S2-2503677 | CR | Approval | 23.502 CR5466 (Rel-19, 'F'): Correction about the Non-3GPP Device Connection Information | China Mobile | Rel-19 | UIA_ARC | Handle | |
| 19.8.2 | S2-2502906 | CR | Approval | 23.502 CR5386 (Rel-19, 'F'): Clarifying port ranges and removing EN | Ericsson | Rel-19 | UIA_ARC | Handle Missing Affected Clauses! | |
| 19.8.2 | S2-2503031 | CR | Approval | 23.501 CR6175 (Rel-19, 'F'): Clarifications to Session Management aspects for handling Non-3GPP Device Identifiers | Samsung | Rel-19 | UIA_ARC | Handle | |
| 19.8.2 | S2-2503306 | CR | Approval | 23.501 CR6203 (Rel-19, 'F'): Clarification on PDU Session for non-3GPP device | LG Electronics | Rel-19 | UIA_ARC | Handle | |
| 19.8.2 | S2-2502894 | CR | Approval | 23.316 CR2142R1 (Rel-19, 'F'): Clarification on AF-5GC interaction for provisioning non-3GPP device identifiers | Apple, Charter Communications | Rel-19 | UIA_ARC | Handle Revision of (Noted) S2-2500462 | |
| 19.8.2 | S2-2503597 | CR | Approval | 23.501 CR6235 (Rel-19, 'F'): Update definition of non-3GPP device connection information | Xiaomi | Rel-19 | UIA_ARC | Handle | |
| 19.8.2 | - | - | - | SMF Selection | - | - | - | Docs:=4 | - |
| 19.8.2 | S2-2502900 | CR | Approval | 23.501 CR6165 (Rel-19, 'F'): PCF and SMF selection for QoS differentiation for non-3GPP devices | Ericsson | Rel-19 | UIA_ARC | Handle | |
| 19.8.2 | S2-2502901 | CR | Approval | 23.502 CR5382 (Rel-19, 'F'): Selection mechanisms for SMF and PCF for non-3GPP devices QoS differentiation | Ericsson | Rel-19 | UIA_ARC | Handle | |
| 19.8.2 | S2-2503337 | CR | Approval | 23.501 CR5976R1 (Rel-19, 'F'): Support of SMF selection considering the Non-3GPP Device Identifier | Huawei, HiSilicon | Rel-19 | UIA_ARC | Handle Revision of (Noted) S2-2500558 | |
| 19.8.2 | S2-2503338 | CR | Approval | 23.502 CR5275R1 (Rel-19, 'F'): Support of SMF selection for Non-3GPP Device Identifer | Huawei, HiSilicon | Rel-19 | UIA_ARC | Handle Revision of (Unhandled) S2-2500709 | |
| 19.9.1 | - | - | - | Study on Enhancement of support for Edge Computing in 5G Core network - Phase 3 (FS_eEDGE_5GC_Ph3) | - | - | _Not_on_Agenda | Docs:=0 | - |
| 19.9.2 | - | - | - | Enhancement of support for Edge Computing in 5G Core network - Phase 3 (eEDGE_5GC_Ph3) | - | - | Dario | Docs:=23 | - |
| 19.9.2 | - | - | - | KI#2: Supporting N6 delay measurement | - | - | - | Docs:=0 | - |
| 19.9.2 | - | - | - | LS | - | - | - | Docs:=1 | - |
| 19.9.2 | S2-2502812 | LS In | Information | LS from CT WG4: LS on Security related protocol-specific parameters for N6 delay measurement | CT WG4 (C4-250555) | eEDGE_5GC_Ph3 | |||
| 19.9.2 | - | - | - | KI#2: I-SMF supporting N6 delay measurement - 548 CR | - | - | - | Docs:=1 | - |
| 19.9.2 | S2-2503700 | CR | Approval | 23.548 CR0310 (Rel-19, 'F'): Clarification on I-SMF operation for N6 Delay Measurement | Samsung | Rel-19 | eEDGE_5GC_Ph3 | ||
| 19.9.2 | - | - | - | KI#1: Offloading from central SMF | - | - | - | Docs:=5 | - |
| 19.9.2 | - | - | - | Support of I-SMF Selection - Discussion papers | - | - | - | Docs:=1 | - |
| 19.9.2 | S2-2503403 | DISCUSSION | Approval | Clarification of the selected I-SMF for Local offloading traffic handling . | Huawei, HiSilicon | Rel-19 | |||
| 19.9.2 | - | - | - | Support of I-SMF Selection - 548 CRs | - | - | - | Docs:=4 | - |
| 19.9.2 | S2-2503404 | CR | Approval | 23.548 CR0288R1 (Rel-19, 'F'): KI#1: Clarfication on the I-SMF selected for local offloading managment | Huawei, HiSilicon, Samsung | Rel-19 | eEDGE_5GC_Ph3 | Competing CR with S2-2502895 Revision of (Postponed) S2-2500611. Check WI Code Capitalization! | |
| 19.9.2 | S2-2502895 | CR | Approval | 23.548 CR0297R1 (Rel-19, 'F'): Clarification on SMF triggered I-SMF insertion or removal for Local Offloading Management | Nokia | Rel-19 | eEDGE_5GC_Ph3 | Competing CR with S2-2503404 Revision of (Postponed) S2-2501062 | |
| 19.9.2 | S2-2503405 | CR | Approval | 23.501 CR5981R1 (Rel-19, 'F'): KI#1: Clarfication on the I-SMF selected for local offloading managment | Huawei, HiSilicon, Samsung | Rel-19 | eEDGE_5GC_Ph3 | 501 CR. Depends on decision on S2-2502895 Revision of (Postponed) S2-2500612 | |
| 19.9.2 | S2-2503406 | CR | Approval | 23.502 CR5265R1 (Rel-19, 'F'): KI#1: Clarfication on the I-SMF selected for local offloading managment | Huawei, HiSilicon, Samsung | Rel-19 | eEDGE_5GC_Ph3 | 502 CR. Depends on decision on S2-2502895 Revision of (Postponed) S2-2500613 | |
| 19.9.2 | - | - | - | KI#1: LOM Policy | - | - | - | Docs:=1 | - |
| 19.9.2 | S2-2503614 | CR | Approval | 23.548 CR0308 (Rel-19, 'F'): Clarification for Local offloading management policy | ZTE | Rel-19 | eEDGE_5GC_Ph3 | ||
| 19.9.2 | - | - | - | KI#1: EAS Discovery using IP replacement | - | - | - | Docs:=1 | - |
| 19.9.2 | S2-2503259 | CR | Approval | 23.548 CR0302 (Rel-19, 'F'): KI#1 Clarification on EAS Discovery using IP replacement to support Local Offloading Management | OPPO | Rel-19 | eEDGE_5GC_Ph3 | Check WI Code Capitalization! | |
| 19.9.2 | - | - | - | KI#1: NF Profile and AMF configuration | - | - | - | Docs:=3 | - |
| 19.9.2 | S2-2503498 | CR | Approval | 23.501 CR6225 (Rel-19, 'F'): SMF profile enhancement | China Mobile | Rel-19 | eEDGE_5GC_Ph3 | ||
| 19.9.2 | S2-2503391 | CR | Approval | 23.501 CR6215 (Rel-19, 'F'): Clarification on the Local Offloading Management and SMF Service Area | LG Electronics | Rel-19 | eEDGE_5GC_Ph3 | ||
| 19.9.2 | S2-2503395 | CR | Approval | 23.548 CR0303 (Rel-19, 'F'): Clarification on the Local Offloading Management Service Area | LG Electronics | Rel-19 | eEDGE_5GC_Ph3 | ||
| 19.9.2 | - | - | - | KI#1: Other correction CRs | - | - | - | Docs:=5 | - |
| 19.9.2 | S2-2503499 | CR | Approval | 23.548 CR0306 (Rel-19, 'F'): Correction of local offloading management | China Mobile | Rel-19 | eEDGE_5GC_Ph3 | ||
| 19.9.2 | S2-2503500 | CR | Approval | 23.548 CR0307 (Rel-19, 'F'): UE mobility for local offloading management | China Mobile | Rel-19 | eEDGE_5GC_Ph3 | ||
| 19.9.2 | S2-2503698 | CR | Approval | 23.501 CR6249 (Rel-19, 'F'): 23.501 CR6249: Clarification on Local Offloading Management with URSP | Samsung | Rel-19 | AIML_CN | Wrong WI Code: (FS_) AIML_CN_Ph2 is a FS | |
| 19.9.2 | S2-2503699 | CR | Approval | 23.548 CR0309 (Rel-19, 'F'): Clarification on handling application not matched with LOM policy | Samsung | Rel-19 | eEDGE_5GC_Ph3 | ||
| 19.9.2 | S2-2503850 | CR | Approval | 23.502 CR5477 (Rel-19, 'F'): Clarifications on I-SMF insertion for PDU Session Mobility | Nokia | Rel-19 | eEDGE_5GC_Ph3 | ||
| 19.9.2 | - | - | - | KI#1: N4 Rule generation and LOM Indication | - | - | - | Docs:=4 | - |
| 19.9.2 | S2-2503851 | CR | Approval | 23.548 CR0311 (Rel-19, 'F'): Corrections on Local Offloading Management related indications | Nokia | Rel-19 | eEDGE_5GC_Ph3 | LOM indication | |
| 19.9.2 | S2-2503407 | DISCUSSION | Approval | Interaction between the I-SMF and SMF . | Huawei, HiSilicon | Rel-19 | |||
| 19.9.2 | S2-2503408 | CR | Approval | 23.548 CR0305 (Rel-19, 'F'): Interaction between SMF and I-SMF | Huawei, Hisilicon | Rel-19 | eEDGE_5GC_Ph3 | SDF/N4 rule discussed in the past. Focus on LOM allowed vs. support ind. | |
| 19.9.2 | S2-2503409 | CR | Approval | 23.502 CR5442 (Rel-19, 'F'): Interaction between SMF and I-SMF | Huawei, Hisilicon | Rel-19 | eEDGE_5GC_Ph3 | See S2-2503408 | |
| 19.9.2 | - | - | - | KI#1: Concluded issue - AF Traffic Influence | - | - | - | Docs:=2 | - |
| 19.9.2 | S2-2503397 | CR | Approval | 23.548 CR0304 (Rel-19, 'F'): Clarification on the AF trafficInfluence information from SMF to I-SMF | LG Electronics | Rel-19 | eEDGE_5GC_Ph3 | AF Traffic infl. discussed in the past. | |
| 19.9.2 | S2-2503399 | CR | Approval | 23.502 CR5439 (Rel-19, 'F'): Clarification on the AF trafficInfluence information from SMF to I-SMF | LG Electronics | Rel-19 | eEDGE_5GC_Ph3 | See S2-2503397 | |
| 19.10.1 | - | - | - | Study on Phase 3 for UAS, UAV and UAM (FS_UAS_Ph3) | - | - | _Not_on_Agenda | Docs:=0 | - |
| 19.10.2 | - | - | - | Phase 3 for UAS, UAV and UAM (UAS_Ph3) | - | - | Andy | Docs:=14 | - |
| 19.10.2 | - | - | - | Incoming LS - proposed to note | - | - | - | Docs:=1 | - |
| 19.10.2 | S2-2502810 | LS In | Action | LS from CT WG3: Reply LS on Nnef_RetrieveInfoUAVFlight_Get service operation | CT WG3 (C3-250661) | UAS_Ph3 | Reply to S2-2412757 | ||
| 19.10.2 | - | - | - | Incoming LS which needs Reply LS and CRs | - | - | - | Docs:=9 | - |
| 19.10.2 | S2-2502828 | LS In | Action | LS from RAN WG3: LS on UAV regulation from RAN3 | RAN WG3 (R3-250876) | TEI19 | Responses drafted in S2-2502938, S2-2502963, S2-2503441, S2-2503644 | ||
| 19.10.2 | S2-2502938 | LS OUT | Approval | [DRAFT] Reply LS on UAV regulation from RAN WG3 | LG Electronics | Rel-19 | TEI19, UAS_Ph3 | Response to S2-2502828 | |
| 19.10.2 | S2-2502963 | LS OUT | Approval | [DRAFT] Reply LS on UAV regulation from RAN WG3 | Ericsson | Rel-19 | TEI19, UAS_Ph3 | Response to S2-2502828 | |
| 19.10.2 | S2-2503441 | LS OUT | Approval | [DRAFT] Reply LS on UAV regulation from RAN WG3 | China Mobile Com. Corporation | Rel-19 | Response to S2-2502828 | ||
| 19.10.2 | S2-2503644 | LS OUT | Approval | [DRAFT] Reply LS on UAV regulation from RAN WG3 | CATT | Rel-19 | UAS_Ph3 | Response to S2-2502828 | |
| 19.10.2 | S2-2502937 | CR | Approval | 23.256 CR0192 (Rel-19, 'F'): Clarification on procedure for instructing aerial UEs for altitude reporting | LG Electronics | Rel-19 | TEI19, UAS_Ph3 | 5.16.2. Proposed to attach in Reply LS | |
| 19.10.2 | S2-2503673 | CR | Approval | 23.256 CR0199 (Rel-19, 'F'): The indication on altitude thresholds and reporting periodicity for the aerial UE's altitude reporting | China Mobile | Rel-19 | UAS_Ph3 | 5.16.2, 5.16.3. Referred by Reply LS | |
| 19.10.2 | S2-2502966 | CR | Approval | 23.256 CR0194 (Rel-19, 'C'): Instructing a UAV to stop the altitude reporting | Ericsson | Rel-19 | UAS_Ph3, TEI19 | 5.16.X (new). Proposed to attach in Reply LS | |
| 19.10.2 | S2-2503643 | CR | Approval | 23.256 CR0198 (Rel-19, 'C'): Altitude reporting cancellation | CATT | Rel-19 | UAS_Ph3 | 4.4.1.1.3.1, 4.4.1.1.3.3, 4.4.1.1.3.5, 5.16.1, 5.16.x. Proposed to attach in Reply LS | |
| 19.10.2 | - | - | - | Clarifications | - | - | - | Docs:=4 | - |
| 19.10.2 | S2-2502964 | CR | Approval | 23.256 CR0193 (Rel-19, 'F'): Assigned trajectory event for in-flight monitoring | Ericsson | Rel-19 | UAS_Ph3 | 5.12.3, 5.16.2 | |
| 19.10.2 | S2-2502965 | CR | Approval | 23.502 CR5391 (Rel-19, 'F'): Updates to Assigned Trajectory Parameters | Ericsson | Rel-19 | UAS_Ph3 | ||
| 19.10.2 | S2-2503179 | CR | Approval | 23.256 CR0196 (Rel-19, 'F'): Altitude reporting update | CATT | Rel-19 | UAS_Ph3 | 4.1, 4.4.1.1.3.3 | |
| 19.10.2 | S2-2503182 | CR | Approval | 23.256 CR0197 (Rel-19, 'F'): Procedures update | CATT | Rel-19 | UAS_Ph3 | 5.12.3, 5.13.2 | |
| 19.11.1 | - | - | - | Study on UPF enhancement for Exposure And SBA Phase 2 (FS_UPEAS_Ph2) | - | - | _Not_on_Agenda | Docs:=0 | - |
| 19.11.2 | - | - | - | UPF enhancement for Exposure And SBA Phase 2 (UPEAS_Ph2) | - | - | Wanqiang | Docs:=6 | - |
| 19.11.2 | S2-2503822 | CR | Approval | 23.288 CR1451 (Rel-19, 'B'): An optimized method for AF to obtain the DN-facing UE IP address | CEWiT | Rel-19 | UPEAS_Ph2 | ||
| 19.11.2 | S2-2502955 | CR | Approval | 23.502 CR5390 (Rel-19, 'F'): Corrections on UPF Event Exposure | Ericsson | Rel-19 | UPEAS_Ph2 | ||
| 19.11.2 | S2-2503034 | CR | Approval | 23.501 CR6177 (Rel-19, 'F'): Clarification to UPF selection based on specific UPF functionalities | Samsung | Rel-19 | UPEAS_Ph2 | Check WI Code Capitalization! | |
| 19.11.2 | S2-2503036 | CR | Approval | 23.502 CR5401 (Rel-19, 'F'): Clarifications to Direct subscription to UPF Events in case of session release or UPF relocation | Samsung | Rel-19 | UPEAS_Ph2 | Check WI Code Capitalization! | |
| 19.11.2 | S2-2503037 | CR | Approval | 23.502 CR5402 (Rel-19, 'F'): Correction to direct subscription of UPF event expsoure using UE IP address | Samsung | Rel-19 | UPEAS_Ph2 | Check WI Code Capitalization! | |
| 19.11.2 | S2-2503032 | CR | Approval | 23.501 CR6176 (Rel-19, 'F'): Clarification to usage of operator configurable UPF capabilities in LBO roaming scenarios | Samsung | Rel-19 | UPEAS_Ph2 | Check WI Code Capitalization! | |
| 19.12.1 | - | - | - | Study on System aspects of 5G NR Femto (FS_5G_Femto) | - | - | _Not_on_Agenda | Docs:=0 | - |
| 19.12.2 | - | - | - | System aspects of 5G NR Femto (5G_Femto) | - | - | Andy | Docs:=5 | - |
| 19.12.2 | S2-2502827 | LS In | Information | LS from RAN WG3: LS on security verification related to NR Femtos | RAN WG3 (R3-250822) | NR_WAB_5GFemto-Core | |||
| 19.12.2 | S2-2503302 | CR | Approval | 23.502 CR5425 (Rel-19, 'F'): Clarification on CAG Information Provisioning | LG Electronics | Rel-19 | 5G_Femto | ||
| 19.12.2 | S2-2503360 | CR | Approval | 23.502 CR5437 (Rel-19, 'F'): Removal of event subscription for CAG information provisioning | Samsung | Rel-19 | 5G_Femto | ||
| 19.12.2 | S2-2503367 | CR | Approval | 23.501 CR6214 (Rel-19, 'F'): UDM functional description update for CAG information provisioning | Samsung | Rel-19 | 5G_Femto | ||
| 19.12.2 | S2-2503853 | CR | Approval | 23.501 CR6266 (Rel-19, 'F'): Clarifications on NR Femto node deployments | Nokia | Rel-19 | 5G_Femto | ||
| 19.13.1 | - | - | - | Study on Multi-Access (DualSteer and ATSSS_Ph4) (FS_MASSS) | - | - | _Not_on_Agenda | Docs:=0 | - |
| 19.13.2 | - | - | - | Multi-Access (ATSSS_Ph4) (MASSS) | - | - | Andy | Docs:=32 | - |
| 19.13.2 | - | - | - | CT4 LS on Ethernet MA PDU session using MPQUIC-E steering | - | - | - | Docs:=15 | - |
| 19.13.2 | S2-2502811 | LS In | Action | LS from CT WG4: LS on Ethernet MA PDU session using MPQUIC-E steering | CT WG4 (C4-250554) | MASSS | Responses drafted in S2-2503022, S2-2503039, S2-2503304, S2-2503432 | ||
| 19.13.2 | S2-2503020 | CR | Approval | 23.502 CR5396 (Rel-19, 'F'): Correction for MA PDU Session of type Ethernet with MPQUIC-E steering functionality for Roaming scenarios | Nokia | Rel-19 | MASSS | Handle - use as baseline | |
| 19.13.2 | S2-2503021 | CR | Approval | 23.502 CR5397 (Rel-19, 'F'): LS on Next Generation eCall. | CEN/TC 278/WG 15 eSafety | Rel-19 | MASSS | Wrong document uploaded. Revised to S2-2503076 | Revised |
| 19.13.2 | S2-2503076 | CR | Approval | 23.502 CR5397R1 (Rel-19, 'F'): Correction to EPS interworking for MA PDU Session of type Ethernet with MPQUIC-E steering functionality | Nokia | Rel-19 | MASSS | Handle - use as baseline Revision of S2-2503021 | |
| 19.13.2 | S2-2503022 | LS OUT | Approval | [DRAFT] Reply LS on Ethernet MA PDU session using MPQUIC-E steering | Nokia | Rel-19 | MASSS | Handle - use as baseline Response to S2-2502811 | |
| 19.13.2 | S2-2503040 | CR | Approval | 23.502 CR5404 (Rel-19, 'F'): Clarification to HR-SBO scenarios for supporting MPQUIC-E | Samsung | Rel-19 | MASSS | Merged into S2-2503020? | |
| 19.13.2 | S2-2503039 | LS OUT | Approval | [DRAFT] Reply LS on Ethernet MA PDU session using MPQUIC-E steering | Samsung | Merged into S2-2503022? Response to S2-2502811 | |||
| 19.13.2 | S2-2503305 | CR | Approval | 23.502 CR5426 (Rel-19, 'F'): Clarification on PDU Session Type setting in case of V/I-SMF | LG Electronics | Rel-19 | MASSS | Merged into S2-2503020? | |
| 19.13.2 | S2-2503304 | LS OUT | Approval | [DRAFT] Reply LS on Ethernet MA PDU session using MPQUIC-E steering | LG Electronics | Rel-19 | MASSS | Merged into S2-2503022? Response to S2-2502811 | |
| 19.13.2 | S2-2503430 | CR | Approval | 23.502 CR5444 (Rel-19, 'F'): Clarification on MPQUIC functionality | Huawei, HiSilicon | Rel-19 | MASSS | Merged into S2-2503076? | |
| 19.13.2 | S2-2503432 | LS OUT | Approval | [DRAFT] LS on Ethernet MA PDU session using MPQUIC-E functionality | Huawei, HiSilicon | Rel-19 | MASSS | Merged into S2-2503022? Response to S2-2502811 | |
| 19.13.2 | S2-2503261 | CR | Approval | 23.501 CR6197 (Rel-19, 'F'): Handling of MPQUIC-E with EPS interworking | Ericsson | Rel-19 | MASSS | Handle | |
| 19.13.2 | S2-2503262 | CR | Approval | 23.502 CR5421 (Rel-19, 'F'): Handling of MPQUIC-E with EPS interworking | Ericsson | Rel-19 | MASSS | Merged into S2-2503076? | |
| 19.13.2 | S2-2503263 | CR | Approval | 23.502 CR5422 (Rel-19, 'F'): Handling of MPQUIC-E in roaming cases | Ericsson | Rel-19 | MASSS | Merged into S2-2503020? | |
| 19.13.2 | S2-2503264 | LS OUT | Approval | [DRAFT] Reply LS on Ethernet MA PDU session using MPQUIC-E steering | Ericsson | Rel-19 | MASSS | Merged into S2-2503022? Response to S2-2502811 | |
| 19.13.2 | - | - | - | Alignments | - | - | - | Docs:=5 | - |
| 19.13.2 | S2-2503429 | CR | Approval | 23.501 CR6218 (Rel-19, 'D'): Terminology alignment for steering functionality(ies) | Huawei, HiSilicon | Rel-19 | MASSS | Handle | |
| 19.13.2 | S2-2503431 | CR | Approval | 23.503 CR1537 (Rel-19, 'D'): Terminology alignment for steering functionality(ies) | Huawei, HiSilicon | Rel-19 | MASSS | Handle | |
| 19.13.2 | S2-2503889 | CR | Approval | 23.501 CR6275 (Rel-19, 'F'): Alignment with ATSSS Capability IE | Apple | Rel-19 | MASSS | Handle Should this be a mirror CR for S2-2503891?)! | |
| 19.13.2 | S2-2503038 | CR | Approval | 23.502 CR5403 (Rel-19, 'F'): Corrections to PDU Session Modification on mobility to 5GS for Ethernet MA PDU Session | Samsung | Rel-19 | MASSS | Handle | |
| 19.13.2 | S2-2503278 | CR | Approval | 23.501 CR6198 (Rel-19, 'F'): Clarification on MPQUIC proxy | China Telecom | Rel-19 | MASSS | Handle | |
| 19.13.2 | - | - | - | IP version used for MPQUIC-E | - | - | - | Docs:=9 | - |
| 19.13.2 | S2-2503303 | CR | Approval | 23.501 CR6202 (Rel-19, 'F'): Clarification on IP version used for MPQUIC-E | LG Electronics, CableLabs, Apple | Rel-19 | MASSS | Revised to S2-2503738 | Revised |
| 19.13.2 | S2-2503738 | CR | Approval | 23.501 CR6202R1 (Rel-19, 'F'): Clarification on IP version used for MPQUIC-E | LG Electronics, CableLabs, Apple | Rel-19 | MASSS | Handle Revision of S2-2503303 | |
| 19.13.2 | S2-2503309 | CR | Approval | 23.502 CR5428 (Rel-19, 'F'): Clarification on IP version used for MPQUIC-E in procedure | LG Electronics | Rel-19 | MASSS | Handle | |
| 19.13.2 | S2-2503751 | CR | Approval | 23.501 CR6257 (Rel-19, 'F'): IP version used for MPQUIC-E | Ericsson | Rel-19 | MASSS | Handle | |
| 19.13.2 | S2-2503752 | CR | Approval | 23.502 CR5471 (Rel-19, 'F'): IP version used for MPQUIC-E | Ericsson | Rel-19 | MASSS | Handle | |
| 19.13.2 | S2-2503297 | CR | Approval | 23.501 CR6199 (Rel-19, 'F'): Clarification on IP version used for MPQUIC-E | MediaTek Inc. | Rel-19 | MASSS | Merged into S2-2503751? | |
| 19.13.2 | S2-2503307 | CR | Approval | 23.502 CR5427 (Rel-19, 'F'): Clarification on IP version used for MPQUIC-E | MediaTek Inc. | Rel-19 | MASSS | Merged into S2-2503752? | |
| 19.13.2 | S2-2503041 | CR | Approval | 23.501 CR6178 (Rel-19, 'F'): Correct Handling of IP version when MPQUIC-E is enabled | Samsung | Rel-19 | MASSS | Handle | |
| 19.13.2 | S2-2503042 | CR | Approval | 23.502 CR5405 (Rel-19, 'F'): Correct Handling of IP version when MPQUIC-E is enabled | Samsung | Rel-19 | MASSS | Handle | |
| 19.13.2 | - | - | - | IP version of the two MPQUIC link-specific multipath addresses | - | - | - | Docs:=3 | - |
| 19.13.2 | S2-2503249 | DISCUSSION | Discussion | Discussion on the consideration of IP version of the two MPQUIC link-specific multipath addresses . | China Mobile | Rel-19 | MASSS | Handle | |
| 19.13.2 | S2-2503257 | CR | Approval | 23.501 CR6195 (Rel-19, 'F'): MPQUIC IP-allocation considerations & Some corrections | China Mobile | Rel-19 | MASSS | Handle | |
| 19.13.2 | S2-2503258 | CR | Approval | 23.501 CR6196 (Rel-18, 'A'): MPQUIC IP-allocation considerations & Some corrections | China Mobile | Rel-18 | MASSS | Handle | |
| 19.14.1 | - | - | - | Study on Architecture support of Ambient power-enabled Internet of Things (FS_AmbientIoT) | - | - | _Not_on_Agenda | Docs:=0 | - |
| 19.14.2 | - | - | - | Architecture support of Ambient power-enabled Internet of Things (AmbientIoT-ARC) | - | - | Wanqiang | Docs:=100 | - |
| 19.14.2 | - | - | - | LS in | - | - | - | Docs:=3 | - |
| 19.14.2 | S2-2502799 | LS In | Action | LS from SA WG3: Reply LS on security aspects of Ambient IoT | SA WG3 (S3-251055) | Rel-19 | FS_AmbientIoT | Reply to S2-2411049. No reply LS, propose to NOTE Revision of S2-2501384 | |
| 19.14.2 | S2-2502835 | LS In | Action | LS from SA WG3: Reply LS on Device Subscription Data | SA WG3 (S3-251102) | FS_AmbientIoT | Reply to S2-2501242. No reply LS, propose to NOTE | ||
| 19.14.2 | S2-2502839 | LS In | Action | LS from SA WG5: Reply to LS on A-IoT Conclusions in SA WG2 | SA WG5 (S5-250680) | Reply to S2-2413035. No reply LS, propose to NOTE | |||
| 19.14.2 | - | - | - | Rederence point (clause 4.2, 4.3 and 4.4) | - | - | - | Docs:=8 | - |
| 19.14.2 | S2-2503200 | P-CR | Approval | 23.369: Terminology Alignment. | Ericsson, Huawei, HiSilicon | Rel-19 | AmbientIoT-ARC | Handle | |
| 19.14.2 | S2-2503848 | P-CR | Approval | 23.369: PCR for TS 23.369: AIoT Reference Point Naming . | Huawei, HiSilicon | Rel-19 | AmbientIoT-ARC | Handle. Reference point naming | |
| 19.14.2 | S2-2503199 | P-CR | Approval | 23.369: Clause 4.2.2 & 4.3: Reference Point Definition. | Ericsson | Rel-19 | AmbientIoT-ARC | Focus on FFS on Ny interaface. Change on clause 4.3 merge into S2-2503848? | |
| 19.14.2 | S2-2503394 | CR | Approval | 23.501 CR6216 (Rel-19, 'F'): Reference Points and SBIs for Ambient IoT | Samsung | Rel-19 | AmbientIoT-ARC | Handle, update to 23.501 | |
| 19.14.2 | S2-2503390 | P-CR | Approval | 23.369: Reference Points. | Samsung | Rel-19 | AmbientIoT-ARC | Merge into S2-2503848? | |
| 19.14.2 | S2-2503842 | CR | Approval | 23.501 CR6265 (Rel-19, 'B'): Ambient IoT interfaces and reference points | Huawei, HiSilicon | Rel-19 | AmbientIoT-ARC | Merge into S2-2503394? | |
| 19.14.2 | S2-2503378 | P-CR | Approval | 23.369: AIoT RAN Connectivity. | Samsung | Rel-19 | AmbientIoT-ARC | Merge into S2-2503199? | |
| 19.14.2 | S2-2503649 | P-CR | Approval | 23.369: Discussion on Nx reference point interface between AIOTF and AIoT RAN. | Tejas Networks | Rel-19 | AmbientIoT-ARC | Merge into S2-2503199? | |
| 19.14.2 | - | - | - | LS from RAN WG3 on reader selection | - | - | - | Docs:=3 | - |
| 19.14.2 | S2-2502832 | LS In | Action | LS from RAN WG3: LS on Ambient IoT progress of RAN WG3 | RAN WG3 (R3-250905) | Ambient_IoT_Solutions-Core | Responses drafted in S2-2503106, S2-2503496 | ||
| 19.14.2 | S2-2503106 | LS OUT | Approval | [DRAFT] LS Reply on Ambient IoT progress of RAN WG3 | NEC | Rel-19 | Handle Response to S2-2502832 | ||
| 19.14.2 | S2-2503496 | LS OUT | Approval | [DRAFT] LS Reply on Ambient IoT progress of RAN WG3 | China Mobile Com. Corporation | Rel-19 | Merge into S2-2503106? Response to S2-2502832 | ||
| 19.14.2 | - | - | - | NG-RAN and Reader selection (5.3) | - | - | - | Docs:=8 | - |
| 19.14.2 | S2-2503475 | P-CR | Approval | 23.369: PCR for TS 23.369: AIoT Reader Selection. | China Mobile | Rel-19 | AmbientIoT-ARC | Handle | |
| 19.14.2 | S2-2503012 | P-CR | Approval | 23.369: AIoT Reader Selection update. | CATT | Rel-19 | AmbientIoT-ARC | Merge into S2-2503475? | |
| 19.14.2 | S2-2503049 | P-CR | Approval | 23.369: Resolving the EN on AIoT RAN Reader and AMF selection. | OPPO | Rel-19 | AmbientIoT-ARC | Merge into S2-2503475? | |
| 19.14.2 | S2-2503385 | P-CR | Approval | 23.369: AIoT Reader Selection. | Samsung | Rel-19 | AmbientIoT-ARC | Merge into S2-2503475? | |
| 19.14.2 | S2-2503857 | P-CR | Approval | 23.369: PCR to TS 23.369: AIoT Reader selection . | Lenovo | Rel-19 | AmbientIoT-ARC | Merge into S2-2503475? | |
| 19.14.2 | S2-2503692 | P-CR | Approval | 23.369: PCR to TS 23.369: Address EN for AIoT Reader Selection. | ZTE | Rel-19 | AmbientIoT-ARC | Merge into S2-2503475? | |
| 19.14.2 | S2-2503838 | P-CR | Approval | 23.369: PCR for TS 23.369: AIoT Reader Selection. | Huawei, HiSilicon | Rel-19 | AmbientIoT-ARC | Merge into S2-2503475? | |
| 19.14.2 | S2-2503476 | DISCUSSION | Information | AIoT Reader Selection discussion | China Mobile Com. Corporation | Rel-19 | AmbientIoT-ARC | Noted? | |
| 19.14.2 | - | - | - | NF discovery and selection | - | - | - | Docs:=7 | - |
| 19.14.2 | S2-2503153 | P-CR | Approval | 23.369: AIOTF/AMF selection and NF profile. | Vivo | Rel-19 | AmbientIoT-ARC | Handle. Focus on AMF selection | |
| 19.14.2 | S2-2503011 | P-CR | Approval | 23.369: AIOTF selection and AMF selection. | CATT | Rel-19 | AmbientIoT-ARC | Handle. Focus on AIOTF selection | |
| 19.14.2 | S2-2503792 | P-CR | Approval | 23.369: Update to Inventory procedure regarding AIOTF selection . | InterDigital Inc. | Rel-19 | AmbientIoT-ARC | Handle. Focus on EN on AIOTF selection | |
| 19.14.2 | S2-2503197 | P-CR | Approval | 23.369: Clause 5.X & 6.2.2 & 6.2.3: AIOTF Discovery and Selection. | Ericsson | Rel-19 | AmbientIoT-ARC | Merge into S2-2503011? | |
| 19.14.2 | S2-2503874 | P-CR | Approval | 23.369: AIOTF selection. | Samsung | Rel-19 | AmbientIoT-ARC | Merge into S2-2503011? | |
| 19.14.2 | S2-2503195 | P-CR | Approval | 23.369: Clause 5.X: ADM Discovery and Selection. | Ericsson | Rel-19 | AmbientIoT-ARC | Handle. ADM selection | |
| 19.14.2 | S2-2503670 | P-CR | Approval | 23.369: ADM selection and related update. | Vivo | Rel-19 | AmbientIoT-ARC | Merge into S2-2503196? | |
| 19.14.2 | - | - | - | Assistance information (5.4) | - | - | - | Docs:=11 | - |
| 19.14.2 | S2-2502939 | P-CR | Approval | 23.369: Clause 5.4 updates. | LG Electronics | Rel-19 | AmbientIoT-ARC | Handle | |
| 19.14.2 | S2-2503833 | P-CR | Approval | 23.369: PCR for TS 23.369: Clarification on Assistance Information. | Huawei, HiSilicon | Rel-19 | AmbientIoT-ARC | Merge into S2-2502939? | |
| 19.14.2 | S2-2503477 | P-CR | Approval | 23.369: PCR for TS 23.369: update on Assistance information provided to AIoT RAN Node. | China Mobile | Rel-19 | AmbientIoT-ARC | Merge into S2-2502939? | |
| 19.14.2 | S2-2503381 | P-CR | Approval | 23.369: Assistance Information. | Samsung | Rel-19 | AmbientIoT-ARC | Merge into S2-2503196? | |
| 19.14.2 | S2-2503466 | P-CR | Approval | 23.369: Text on assistance information to support command procedure. | NTT DOCOMO, T-Mobile USA | Rel-19 | AmbientIoT-ARC | Handle | |
| 19.14.2 | S2-2503442 | DISCUSSION | Discussion | Discussion on assistance information to support command. | NTT DOCOMO, T-Mobile USA | Rel-19 | AmbientIoT-ARC | Noted? | |
| 19.14.2 | S2-2503161 | P-CR | Approval | 23.369: Update Assistance information for Inventory procedure . | Ofinno | Rel-19 | AmbientIoT-ARC | Merge into S2-2503466? | |
| 19.14.2 | S2-2503794 | LS OUT | Approval | [DRAFT] LS on the need of indication of follow-up Command procedure in Inventory request | InterDigital Inc. | Rel-19 | AmbientIoT-ARC | Handle | |
| 19.14.2 | S2-2503201 | LS OUT | Approval | [DRAFT] LS on Assistance Information for Subsequent Command | Ericsson | Rel-19 | AmbientIoT-ARC | Merge into S2-2503794? | |
| 19.14.2 | S2-2503691 | LS OUT | Approval | [DRAFT] LS on Command Indication in Inventory Request | ZTE | Rel-19 | AmbientIoT-ARC | Merge into S2-2503794? | |
| 19.14.2 | S2-2503163 | LS OUT | Approval | [DRAFT] LS on Assistance information for follow-up Command procedure | Ofinno, LLC | Rel-19 | Merge into S2-2503794? | ||
| 19.14.2 | - | - | - | AIoT device data profile management (5.5) | - | - | - | Docs:=1 | - |
| 19.14.2 | S2-2503841 | P-CR | Approval | 23.369: PCR for TS 23.369: Improve AIoT Device Profile Management. | Huawei, HiSilicon | Rel-19 | AmbientIoT-ARC | ||
| 19.14.2 | - | - | - | AF authorization (5.6) | - | - | - | Docs:=6 | - |
| 19.14.2 | S2-2503196 | P-CR | Approval | 23.369: Clause 5.6 & 6.2.2 & 6.2.3: Resolve EN on AF Authorization. | Ericsson | Rel-19 | AmbientIoT-ARC | Handle | |
| 19.14.2 | S2-2503002 | P-CR | Approval | 23.369: Addressing EN: AF authorization for Ambient IoT. | Lenovo | Rel-19 | AmbientIoT-ARC | Merge into S2-2503196? | |
| 19.14.2 | S2-2503013 | P-CR | Approval | 23.369: Resolve EN on AF authorization. | CATT | Rel-19 | AmbientIoT-ARC | Merge into S2-2503196? | |
| 19.14.2 | S2-2503388 | P-CR | Approval | 23.369: AF Authorization. | Samsung | Rel-19 | AmbientIoT-ARC | Merge into S2-2503196? | |
| 19.14.2 | S2-2503527 | P-CR | Approval | 23.369: Updates on AF authorization . | Nokia | Rel-19 | AmbientIoT-ARC | Merge into S2-2503196? | |
| 19.14.2 | S2-2503840 | P-CR | Approval | 23.369: PCR for TS 23.369: Address ENs for AF authorization. | Huawei, HiSilicon | Rel-19 | AmbientIoT-ARC | Merge into S2-2503196? | |
| 19.14.2 | - | - | - | AIoT device ID (5.7) | - | - | - | Docs:=4 | - |
| 19.14.2 | S2-2503845 | P-CR | Approval | 23.369: PCR for TS 23.369: Update of Device ID for NID. | Huawei, HiSilicon | Rel-19 | AmbientIoT-ARC | Handle | |
| 19.14.2 | S2-2503849 | LS OUT | Approval | [DRAFT] LS on AIoT device identifier length | Huawei, HiSilicon | Rel-19 | AmbientIoT-ARC | Handle | |
| 19.14.2 | S2-2503152 | P-CR | Approval | 23.369: PCR to TS 23.xyz: Filtering Information. | Vivo | Rel-19 | AmbientIoT-ARC | Focus on 5.X | |
| 19.14.2 | S2-2503046 | P-CR | Approval | 23.369: Update on AIoT Device ID information. | OPPO | Rel-19 | AmbientIoT-ARC | Merged into S2-2503152? Focus on clause 5.7.3 | |
| 19.14.2 | - | - | - | Clasue 6: AIoT service procedure | - | - | - | Docs:=0 | - |
| 19.14.2 | - | - | - | Inventory and command procedure documentation | - | - | - | Docs:=2 | - |
| 19.14.2 | S2-2503043 | P-CR | Approval | 23.369: Structure for documenting indirect path and Direct path. | OPPO | Rel-19 | AmbientIoT-ARC | Handle. Topic for drafting session | |
| 19.14.2 | S2-2503846 | P-CR | Approval | 23.369: PCR for TS 23.369: Procedure for AIOTF and AIoT Reader Communication. | Huawei, HiSilicon | Rel-19 | AmbientIoT-ARC | Handle. Topic for drafting session | |
| 19.14.2 | - | - | - | Inventory procedure update | - | - | - | Docs:=11 | - |
| 19.14.2 | S2-2503834 | P-CR | Approval | 23.369: PCR for TS 23.369: Update Inventory Procedure. | Huawei, HiSilicon | Rel-19 | AmbientIoT-ARC | Handle | |
| 19.14.2 | S2-2503009 | P-CR | Approval | 23.369: Update on Inventory procedure. | CATT | Rel-19 | AmbientIoT-ARC | Merge into S2-2503834? | |
| 19.14.2 | S2-2503048 | P-CR | Approval | 23.369: EN Resolution and Clarification in Inventory Procedure. | OPPO | Rel-19 | AmbientIoT-ARC | Merge into S2-2503834? | |
| 19.14.2 | S2-2503149 | P-CR | Approval | 23.369: Update AIoT Inventory procedure for Command . | Ofinno | Rel-19 | AmbientIoT-ARC | Merge into S2-2503834? | |
| 19.14.2 | S2-2503154 | P-CR | Approval | 23.369: Update to inventory procedure. | Vivo | Rel-19 | AmbientIoT-ARC | Merge into S2-2503834? | |
| 19.14.2 | S2-2503387 | P-CR | Approval | 23.369: Inventory Procedure Update. | Samsung | Rel-19 | AmbientIoT-ARC | Merge into S2-2503834? | |
| 19.14.2 | S2-2503471 | P-CR | Approval | 23.369: Update Inventory Procedure. | Sony | Rel-19 | AmbientIoT-ARC | Merge into S2-2503834? | |
| 19.14.2 | S2-2503689 | P-CR | Approval | 23.369: PCR to TS 23.369: Clarification on AIoT Procedure. | ZTE | Rel-19 | AmbientIoT-ARC | Merge into S2-2503834? | |
| 19.14.2 | S2-2503696 | P-CR | Approval | 23.369: Update for AIoT Service Procedures. | China Mobile | Rel-19 | AmbientIoT-ARC | Merge into S2-2503834? | |
| 19.14.2 | S2-2503045 | P-CR | Approval | 23.369: Update on the Aggregation in the Inventory and Command procedure. | OPPO | Rel-19 | AmbientIoT-ARC | Merge into S2-2503834? | |
| 19.14.2 | S2-2503843 | DISCUSSION | Discussion | Discussion on RAN Procedure Interactions. | Huawei, HiSilicon | Rel-19 | AmbientIoT-ARC | NOTED? | |
| 19.14.2 | - | - | - | Command procedure - AIoT data structure | - | - | - | Docs:=2 | - |
| 19.14.2 | S2-2503047 | P-CR | Approval | 23.369: EN resolution on AIoT data. | OPPO | Rel-19 | AmbientIoT-ARC | Focus on EN related to AIoT data structure | |
| 19.14.2 | S2-2503380 | P-CR | Approval | 23.369: Command Type AIoT data. | Samsung | Rel-19 | AmbientIoT-ARC | Merge into S2-2503047? | |
| 19.14.2 | - | - | - | Command procedure update - overall | - | - | - | Docs:=8 | - |
| 19.14.2 | S2-2503010 | P-CR | Approval | 23.369: Update on Command procedure. | CATT | Rel-19 | AmbientIoT-ARC | Handle | |
| 19.14.2 | S2-2503004 | P-CR | Approval | 23.369: Update for Command Procedure: Command failure handling. | Lenovo, China Telecom | Rel-19 | AmbientIoT-ARC | Merge into S2-2503010? | |
| 19.14.2 | S2-2503155 | P-CR | Approval | 23.369: Update to command procedure. | Vivo | Rel-19 | AmbientIoT-ARC | Merge into S2-2503010? | |
| 19.14.2 | S2-2503382 | P-CR | Approval | 23.369: Command Procedure Update. | Samsung | Rel-19 | AmbientIoT-ARC | Merge into S2-2503010? | |
| 19.14.2 | S2-2503469 | P-CR | Approval | 23.369: Updates to call flows to support command. | NTT DOCOMO, T-Mobile USA | Rel-19 | AmbientIoT-ARC | Merge into S2-2503010? | |
| 19.14.2 | S2-2503472 | P-CR | Approval | 23.369: Update Command Procedure. | Sony | Rel-19 | AmbientIoT-ARC | Merge into S2-2503010? | |
| 19.14.2 | S2-2503835 | P-CR | Approval | 23.369: PCR for TS 23.369: Update Command Procedure. | Huawei, HiSilicon | Rel-19 | AmbientIoT-ARC | Merge into S2-2503010? | |
| 19.14.2 | S2-2503793 | P-CR | Approval | 23.369: Update to Command procedure. | InterDigital Inc. | Rel-19 | AmbientIoT-ARC | Merge into S2-2503010? | |
| 19.14.2 | - | - | - | NF description update (clause 4.5) | - | - | - | Docs:=9 | - |
| 19.14.2 | S2-2503003 | P-CR | Approval | 23.369: NF descriptions update for AIOTF and NRF. | Lenovo, China Telecom | Rel-19 | AmbientIoT-ARC | Handle. for AIOTF and NRF part | |
| 19.14.2 | S2-2503044 | P-CR | Approval | 23.369: Update on NF description. | OPPO | Rel-19 | AmbientIoT-ARC | Handle. for AIoT device, and AMF part | |
| 19.14.2 | S2-2503549 | P-CR | Approval | 23.369: Updates on aggregation . | Nokia | Rel-19 | AmbientIoT-ARC | Handle. For NG-RAN part | |
| 19.14.2 | S2-2503157 | P-CR | Approval | 23.369: Update to Network Functions. | Vivo | Rel-19 | AmbientIoT-ARC | Merge into S2-2503003? | |
| 19.14.2 | S2-2503502 | P-CR | Approval | 23.369: PCR to TS 23.369 on aggregation aspects. | NTT DOCOMO | Rel-19 | AmbientIoT-ARC | Merge into S2-2503003? | |
| 19.14.2 | S2-2503379 | P-CR | Approval | 23.369: AIoT Device. | Samsung | Rel-19 | AmbientIoT-ARC | Merge into S2-2503044? | |
| 19.14.2 | S2-2503384 | P-CR | Approval | 23.369: AIoT Readers. | Samsung | Rel-19 | AmbientIoT-ARC | Merge into S2-2503549? | |
| 19.14.2 | S2-2503473 | P-CR | Approval | 23.369: Text on AIoT Device capabilities. | NTT DOCOMO | Rel-19 | AmbientIoT-ARC | Merge into S2-2503044? | |
| 19.14.2 | S2-2503703 | P-CR | Approval | 23.369: Update for Functional Entities. | China Mobile | Rel-19 | AmbientIoT-ARC | Postponed, requesed by author | |
| 19.14.2 | - | - | - | NF sevices update (7.X) | - | - | - | Docs:=3 | - |
| 19.14.2 | S2-2503836 | P-CR | Approval | 23.369: PCR for TS 23.369: Improve AIoT NF Services. | Huawei, HiSilicon | Rel-19 | AmbientIoT-ARC | Handle | |
| 19.14.2 | S2-2503156 | P-CR | Approval | 23.369: Update to NF Services. | Vivo | Rel-19 | AmbientIoT-ARC | Handle | |
| 19.14.2 | S2-2503690 | P-CR | Approval | 23.369: PCR to TS 23.369: AIOTF and NEF Service Definition Update. | ZTE | Rel-19 | AmbientIoT-ARC | Merge into S2-2503836? | |
| 19.14.2 | - | - | - | Protocol stack (4.6) | - | - | - | Docs:=4 | - |
| 19.14.2 | S2-2503050 | P-CR | Approval | 23.369: Update on Description for Protocol Stack. | OPPO | Rel-19 | AmbientIoT-ARC | Handle. Focus on clause 4.6.2.1 | |
| 19.14.2 | S2-2503688 | P-CR | Approval | 23.369: PCR to TS 23.369: Address EN for AIoT Reader Control Transportation. | ZTE | Rel-19 | AmbientIoT-ARC | Handle. Focus on clause 4.6.2.2 and 4.6.2.3 | |
| 19.14.2 | S2-2503198 | P-CR | Approval | 23.369: Clause 4.6: Protocol Stack Update. | Ericsson | Rel-19 | AmbientIoT-ARC | Merge into S2-2503688? | |
| 19.14.2 | S2-2503839 | P-CR | Approval | 23.369: PCR for TS 23.369: Protocol Stack Update. | Huawei, HiSilicon | Rel-19 | AmbientIoT-ARC | Handle. Focus on clasue 4.6.1 | |
| 19.14.2 | - | - | - | Others | - | - | - | Docs:=8 | - |
| 19.14.2 | S2-2503609 | P-CR | Approval | 23.369: Update to clause 5.7 Identifiers. | HONOR | Rel-19 | AmbientIoT-ARC | Device temporay ID | |
| 19.14.2 | S2-2503847 | P-CR | Approval | 23.369: PCR for TS 23.369: Support of AIoT Device Temporary ID. | Huawei, HiSilicon | Rel-19 | AmbientIoT-ARC | Device temporay ID | |
| 19.14.2 | S2-2503687 | P-CR | Approval | 23.369: PCR to TS 23.369: Clarification on AIoT Device Profile Data. | ZTE | Rel-19 | AmbientIoT-ARC | Device temporay ID | |
| 19.14.2 | S2-2503837 | P-CR | Approval | 23.369: PCR for TS 23.369: Support of AIoT Device Context Management. | Huawei, HiSilicon | Rel-19 | AmbientIoT-ARC | AIoT device context management | |
| 19.14.2 | S2-2503151 | P-CR | Approval | 23.369: Non-Operation Related Procedure . | Vivo | Rel-19 | AmbientIoT-ARC | Procedure for AIOT association | |
| 19.14.2 | S2-2503108 | P-CR | Approval | 23.369: AIoT device priority as AIoT Assistance information. | NEC | Rel-19 | AmbientIoT-ARC | AIoT device priority | |
| 19.14.2 | S2-2503686 | P-CR | Approval | 23.369: PCR to TS 23.369: AIoT Service Operation Result Aggregation. | ZTE | Rel-19 | AmbientIoT-ARC | Aggregation | |
| 19.14.2 | S2-2503791 | P-CR | Approval | 23.369: AIoT Device Information Configure Service. | InterDigital Inc., Lenovo | Rel-19 | AmbientIoT-ARC | NEF Configure Service | |
| 19.14.2 | - | - | - | LS out | - | - | - | Docs:=1 | - |
| 19.14.2 | S2-2503150 | LS OUT | Approval | [DRAFT] LS on Ambient IoT | vivo | AmbientIoT-ARC | |||
| 19.14.2 | - | - | - | Scope update | - | - | - | Docs:=1 | - |
| 19.14.2 | S2-2503109 | P-CR | Approval | 23.369: AIoT Scope and Architecture General concept clarifications. | NEC | Rel-19 | AmbientIoT-ARC | ||
| 19.15.1 | - | - | - | Core Network Enhanced Support for Artificial Intelligence (AI)/Machine Learning (ML) (FS_AIML_CN) | - | - | _Not_on_Agenda | Docs:=0 | - |
| 19.15.2 | - | - | - | Core Network Enhanced Support for Artificial Intelligence (AI)/Machine Learning (ML) (AIML_CN) | - | - | Dario | Docs:=87 | - |
| 19.15.2 | - | - | - | 1st Round | - | - | - | Docs:=0 | - |
| 19.15.2 | - | - | - | KI#1 - AIML support for LMF positioning | - | - | - | Docs:=6 | - |
| 19.15.2 | - | - | - | KI#1: ML Model provisioning by OAM | - | - | - | Docs:=5 | - |
| 19.15.2 | S2-2502840 | LS In | Action | LS from SA WG5: Reply LS on ML Model provisioning by OAM to LMF for UE positioning | SA WG5 (S5-250826) | AIML_MGT_Ph2 | Reply to S2-2412890 Responses drafted in S2-2502857, S2-2503227, S2-2503340 | ||
| 19.15.2 | S2-2502857 | LS OUT | Approval | [DRAFT] Reply LS on ML Model provisioning by OAM to LMF for UE positioning | ZTE | Rel-19 | AIML_CN | Response to S2-2502840 | |
| 19.15.2 | S2-2503227 | LS OUT | Approval | [DRAFT] Reply LS on ML Model provisioning by OAM to LMF for UE positioning | Nokia | Rel-19 | Response to S2-2502840 | ||
| 19.15.2 | S2-2503340 | LS OUT | Approval | [DRAFT] Reply LS on ML Model provisioning by OAM to LMF for UE positioning | Huawei, HiSilicon | Rel-19 | AIML_CN | Response to S2-2502840 | |
| 19.15.2 | S2-2503110 | CR | Approval | 23.273 CR0705 (Rel-19, 'F'): ML Model provisioning by OAM for LMF-based AI/ML Positioning | NTT DOCOMO, Ericsson | Rel-19 | AIML_CN | ||
| 19.15.2 | - | - | - | KI#1: LCS privacy & User consent | - | - | - | Docs:=4 | - |
| 19.15.2 | S2-2502947 | CR | Approval | 23.273 CR0702 (Rel-19, 'F'): Changes on user consent and privacy for AIML-based positioning | Apple | Rel-19 | AIML_CN | ||
| 19.15.2 | S2-2503216 | CR | Approval | 23.273 CR0710 (Rel-19, 'F'): UE LCS privacy check for ground truth data collection and input data storage for ML model training for AI/ML positioning | Intel | Rel-19 | AIML_CN | ||
| 19.15.2 | S2-2503598 | CR | Approval | 23.273 CR0721 (Rel-19, 'F'): Clarification on privacy check for data collection | Xiaomi | Rel-19 | AIML_CN | ||
| 19.15.2 | S2-2503668 | CR | Approval | 23.288 CR1449 (Rel-19, 'F'): UE LCS privacy check for AI/ML based positioning | Qualcomm Incorporated | Rel-19 | AIML_CN | ||
| 19.15.2 | - | - | - | KI#1: TS 23.273 clause 6.22.2 - case 2b | - | - | - | Docs:=3 | - |
| 19.15.2 | S2-2502802 | LS In | Action | LS from RAN WG2: Reply LS to SA WG2 on LMF-based AI/ML Positioning for Case 2b | RAN WG2 (R2-2501507) | Rel-19 | NR_AIML_air-Core | Reply to S2-2501133 Revision of S2-2501387 | |
| 19.15.2 | S2-2502818 | LS In | Action | LS from RAN WG1: Reply LS on LMF-based AI/ML Positioning for Case 2b | RAN WG1 (R1-2501523) | AIML_CN | Reply to S2-2501133 | ||
| 19.15.2 | S2-2502932 | CR | Approval | 23.273 CR0700 (Rel-19, 'C'): Removal of requirements related to case 2b | Vivo, Xiaomi, ZTE, OPPO, Mediatek Inc., Samsung, Nokia | Rel-19 | AIML_CN | ||
| 19.15.2 | - | - | - | KI#1: TS 23.273 clause 6.22.3 - case 3b | - | - | - | Docs:=3 | - |
| 19.15.2 | S2-2502819 | LS In | Action | LS from RAN WG1: Reply LS on LMF-based AI/ML Positioning for Case 3b | RAN WG1 (R1-2500389) | AIML_CN | Reply to S2-2501341 | ||
| 19.15.2 | S2-2502826 | LS In | Action | LS from RAN WG3: Reply LS on LMF-based AI/ML Positioning for case 3b | RAN WG3 (R3-250796) | AIML_CN, NR_AIML_air, NR_AIML_air-Core | Reply to S2-2501341) | ||
| 19.15.2 | S2-2503564 | CR | Approval | 23.273 CR0720 (Rel-19, 'F'): Resolve ENs on input data for LMF based AI/ML positioning | CATT | Rel-19 | AIML_CN | ||
| 19.15.2 | - | - | - | KI#1: TS 23.273, 6.22.4 - data collection by NWDAF | - | - | - | Docs:=1 | - |
| 19.15.2 | S2-2502933 | CR | Approval | 23.273 CR0701 (Rel-19, 'F'): Update on input data collection by NWDAF for LMF-based AIML positioning | ETRI | Rel-19 | AIML_CN | ||
| 19.15.2 | - | - | - | KI#2 - Vertical Federated Learning | - | - | - | Docs:=11 | - |
| 19.15.2 | - | - | - | KI#2: General | - | - | - | Docs:=1 | - |
| 19.15.2 | S2-2503319 | CR | Approval | 23.288 CR1433 (Rel-19, 'F'): Editor s Note clean up for the VFL | OPPO | Rel-19 | AIML_CN | ||
| 19.15.2 | - | - | - | KI#2: VFL training (triggering of training, sample update, accuracy monitoring, etc.) | - | - | - | Docs:=3 | - |
| 19.15.2 | S2-2502863 | CR | Approval | 23.288 CR1411 (Rel-19, 'F'): Optimization of VFL triggers | ZTE, Huawei, Hisilicon, vivo, OPPO | Rel-19 | AIML_CN | ||
| 19.15.2 | S2-2503193 | CR | Approval | 23.288 CR1421 (Rel-19, 'F'): Update triggering Case A and some corrections and Resolving ENs for VFL | Ericsson, China Telecom | Rel-19 | AIML_CN | ||
| 19.15.2 | S2-2503130 | CR | Approval | 23.288 CR1417 (Rel-19, 'F'): Alignment of existing mechanisms for accuracy generation impacted by VFL procedures | Huawei, HiSilicon, ZTE | Rel-19 | AIML_CN | ||
| 19.15.2 | - | - | - | KI#2: VFL inference | - | - | - | Docs:=2 | - |
| 19.15.2 | S2-2503234 | CR | Approval | 23.288 CR1425 (Rel-19, 'F'): Parameters for vertical federated learning inference procedure | Nokia | Rel-19 | AIML_CN | ||
| 19.15.2 | S2-2503250 | CR | Approval | 23.288 CR1429 (Rel-19, 'F'): Updates on VFL inference | Interdigital | Rel-19 | AIML_CN | ||
| 19.15.2 | - | - | - | KI#2: Intermediate results sharing b/w VFL clients | - | - | - | Docs:=2 | - |
| 19.15.2 | S2-2503366 | CR | Approval | 23.288 CR1441 (Rel-19, 'F'): Clarification on Aggregator NWDAF Client Selection | LG Electronics | Rel-19 | AIML_CN | ||
| 19.15.2 | S2-2503718 | CR | Approval | 23.288 CR1450 (Rel-19, 'F'): Maintenance of VFL model training and inference with client intermediate results sharing between VFL clients | Samsung | Rel-19 | AIML_CN | ||
| 19.15.2 | - | - | - | KI#3 - NWDAF-assisted policy control and QoS enhancement | - | - | - | Docs:=1 | - |
| 19.15.2 | S2-2503410 | CR | Approval | 23.288 CR1386R1 (Rel-19, 'F'): Enhancements on the input and output of QoS and Policy Assistance Analytics | China Mobile | Rel-19 | AIML_CN | Revision of (Unhandled) S2-2501699 | |
| 19.15.2 | - | - | - | 2nd Round (only if time allows) | - | - | - | Docs:=0 | - |
| 19.15.2 | - | - | - | KI#4 - Signalling storm mitigation (related to CT4 LS) | - | - | - | Docs:=5 | - |
| 19.15.2 | S2-2502816 | LS In | Action | LS from CT WG4: LS on Questions on stage 2 requirements for AIML_CN | CT WG4 (C4-250630) | AIML_CN | Responses drafted in S2-2503248, S2-2503283 | ||
| 19.15.2 | S2-2503248 | LS OUT | Approval | [DRAFT] Reply LS on Questions on stage 2 requirements for AIML_CN | Nokia | Rel-19 | Response to S2-2502816 | ||
| 19.15.2 | S2-2503283 | LS OUT | Approval | [DRAFT] Reply LS on Questions on stage 2 requirements for AIML_CN | vivo | Rel-19 | AIML_CN | Response to S2-2502816 | |
| 19.15.2 | S2-2503255 | CR | Approval | 23.288 CR1432 (Rel-19, 'B'): AIML_CN KI#4 Resolve issues for event exposure | Nokia | Rel-19 | AIML_CN | ||
| 19.15.2 | S2-2503253 | CR | Approval | 23.502 CR5420 (Rel-19, 'B'): AIML_CN KI#4 Resolve issues for event exposure and for SCP mitigation actions | Nokia | Rel-19 | AIML_CN | ||
| 19.15.2 | - | - | - | General: incoming LS | - | - | - | Docs:=2 | - |
| 19.15.2 | S2-2502793 | LS In | Information | LS from RAN WG1: LS on signalling feasibility of dataset and parameter sharing | RAN WG1 (R1-2410922) | Revision of S2-2501364 | |||
| 19.15.2 | S2-2502841 | LS In | Information | LS from SA WG5: Reply LS on AI/ML UE sided data collection | SA WG5 (S5-250828) | AIML_MGT_Ph2 | Reply to RP-243316 (S2-2502795) | ||
| 19.15.2 | - | - | - | KI#1 - AIML support for LMF positioning | - | - | - | Docs:=7 | - |
| 19.15.2 | - | - | - | KI#1: Incoming LS | - | - | - | Docs:=1 | - |
| 19.15.2 | S2-2502792 | 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) | Reply to S2-2405833 Revision of S2-2501357 | |||
| 19.15.2 | - | - | - | KI#1: ML Model provisioning by OAM | - | - | - | Docs:=2 | - |
| 19.15.2 | S2-2503229 | CR | Approval | 23.273 CR0712 (Rel-19, 'F'): KI#1: ML Model training by OAM for LMF models for UE positioning | Nokia | Rel-19 | AIML_CN | ||
| 19.15.2 | S2-2503341 | CR | Approval | 23.273 CR0713 (Rel-19, 'F'): Update of ML model retrieval from OAM | Huawei, HiSilicon | Rel-19 | AIML_CN | ||
| 19.15.2 | - | - | - | KI#1: LCS privacy & User consent | - | - | - | Docs:=8 | - |
| 19.15.2 | S2-2502948 | DISCUSSION | Decision | Remaining aspects on user consent and privacy for AI/ML-based positioning . | Apple | Rel-19 | AIML_CN | ||
| 19.15.2 | S2-2503190 | CR | Approval | 23.273 CR0708 (Rel-19, 'F'): LMF checking LCS privacy profile before collecting input data and ground truth | Ericsson, AT&T | Rel-19 | AIML_CN | ||
| 19.15.2 | S2-2503215 | DISCUSSION | Discussion | Discussion on UE LCS privacy check for ground truth data collection and input data storage for ML model training for AI/ML positioning . | Intel | Rel-19 | AIML_CN | ||
| 19.15.2 | S2-2503217 | CR | Approval | 23.288 CR1423 (Rel-19, 'F'): UE LCS privacy check for ground truth data collection | Intel | Rel-19 | AIML_CN | ||
| 19.15.2 | S2-2503218 | CR | Approval | 23.273 CR0711 (Rel-19, 'F'): Input data storage in ADRF for ML model training for AI/ML positioning | Intel | Rel-19 | AIML_CN | ||
| 19.15.2 | S2-2503663 | DISCUSSION | Information | Discussion of the user consent and UE LCS privacy check for AI/ML based positioning. | Qualcomm Incorporated, Xiaomi | Rel-19 | AIML_CN | ||
| 19.15.2 | S2-2503665 | CR | Approval | 23.273 CR0724 (Rel-19, 'F'): UE LCS privacy check for AI/ML based positioning | Qualcomm Incorporated | Rel-19 | AIML_CN | ||
| 19.15.2 | S2-2503345 | CR | Approval | 23.273 CR0716 (Rel-19, 'F'): Corrections of LMF-based AI/ML positioning indication | Huawei, HiSilicon | Rel-19 | AIML_CN | ||
| 19.15.2 | - | - | - | KI#1: TS 23.273 clause 6.22.2- case 2b | - | - | - | Docs:=2 | - |
| 19.15.2 | S2-2503674 | CR | Approval | 23.273 CR0725 (Rel-19, 'F'): Removal the AI/ML based positioning for case 2b | Qualcomm Incorporated | Rel-19 | AIML_CN | ||
| 19.15.2 | S2-2503342 | CR | Approval | 23.273 CR0714 (Rel-19, 'F'): Update of input data and procedure for LMF-based AIML positioning | Huawei, HiSilicon | Rel-19 | AIML_CN | ||
| 19.15.2 | - | - | - | KI#1: TS 23.273 clause 6.22.3- case 3b | - | - | - | Docs:=5 | - |
| 19.15.2 | S2-2502899 | CR | Approval | 23.273 CR0637R2 (Rel-19, 'F'): KI#1: Considering RAN load when collecting data to train model for positioning | Nokia | Rel-19 | AIML_CN | Revision of (Unhandled) S2-2501476 | |
| 19.15.2 | S2-2503030 | CR | Approval | 23.273 CR0704 (Rel-19, 'F'): Remove EN on LMF's consideration of RAN load | Samsung | Rel-19 | AIML_CN | Wrong WI code AIML_CN_Ph2 (should be AIML_CN)! | |
| 19.15.2 | S2-2503191 | CR | Approval | 23.273 CR0709 (Rel-19, 'F'): Resolution of Editor s Note based on RAN WG1 and RAN 3 LS replies. | Ericsson | Rel-19 | AIML_CN | ||
| 19.15.2 | S2-2503343 | CR | Approval | 23.273 CR0715 (Rel-19, 'F'): Update the procedure of data collection from NG-RAN | Huawei, HiSilicon | Rel-19 | AIML_CN | ||
| 19.15.2 | S2-2503693 | CR | Approval | 23.273 CR0726 (Rel-19, 'F'): Removal the EN about LMF taking into account RAN load | Qualcomm Incorporated | Rel-19 | AIML_CN | ||
| 19.15.2 | - | - | - | KI#1: TS 23.288 | - | - | - | Docs:=5 | - |
| 19.15.2 | S2-2502858 | CR | Approval | 23.288 CR1406 (Rel-19, 'F'): LMF re-selection based on AI capability | ZTE | Rel-19 | AIML_CN | Confirm Specification Number - CR states 23.273! | |
| 19.15.2 | S2-2502861 | CR | Approval | 23.288 CR1409 (Rel-19, 'F'): General maintenance of KI#1 | ZTE | Rel-19 | AIML_CN | ||
| 19.15.2 | S2-2502931 | CR | Approval | 23.288 CR1415 (Rel-19, 'C'): Removal of requirements related to case 2b | Vivo | Rel-19 | AIML_CN | ||
| 19.15.2 | S2-2503219 | CR | Approval | 23.288 CR1424 (Rel-19, 'F'): Update ADRF service consumer to include LMF | Intel | Rel-19 | AIML_CN, AIML_CN | ||
| 19.15.2 | S2-2503344 | CR | Approval | 23.288 CR1434 (Rel-19, 'F'): Updates of NWDAF discovery and ML model provisioning for LMF-based AI/ML Positioning | Huawei, HiSilicon | Rel-19 | AIML_CN | ||
| 19.15.2 | - | - | - | KI#1: TS 23.501 and TS 23.502 | - | - | - | Docs:=3 | - |
| 19.15.2 | S2-2502867 | CR | Approval | 23.501 CR6164 (Rel-19, 'F'): LMF re-selection based on AI capability | ZTE | Rel-19 | AIML_CN | ||
| 19.15.2 | S2-2502868 | CR | Approval | 23.502 CR5379 (Rel-19, 'F'): LMF re-selection based on AI capability | ZTE | Rel-19 | AIML_CN | ||
| 19.15.2 | S2-2503577 | CR | Approval | 23.502 CR5457 (Rel-19, 'F'): Addition of NOTE to user consent purpose | Apple | Rel-19 | AIML_CN | ||
| 19.15.2 | - | - | - | KI#2 - Vertical Federated Learning | - | - | - | Docs:=4 | - |
| 19.15.2 | - | - | - | KI#2: General | - | - | - | Docs:=3 | - |
| 19.15.2 | S2-2502859 | CR | Approval | 23.288 CR1407 (Rel-19, 'F'): Clarifications on the time interval supporting VFL | ZTE | Rel-19 | AIML_CN | ||
| 19.15.2 | S2-2502866 | CR | Approval | 23.288 CR1414 (Rel-19, 'F'): VFL high level description refinements | ZTE | Rel-19 | AIML_CN | ||
| 19.15.2 | S2-2503347 | CR | Approval | 23.288 CR1435 (Rel-19, 'F'): Correction on VFL correlation ID handling | Huawei, HiSilicon | Rel-19 | AIML_CN | ||
| 19.15.2 | - | - | - | KI#2: Registration and discovery | - | - | - | Docs:=2 | - |
| 19.15.2 | S2-2503131 | CR | Approval | 23.288 CR1418 (Rel-19, 'F'): Clarification on registration and discovery for VFL | Huawei, HiSilicon | Rel-19 | AIML_CN | ||
| 19.15.2 | S2-2503194 | CR | Approval | 23.288 CR1422 (Rel-19, 'F'): Selection of aggregating client in VFL | Ericsson | Rel-19 | AIML_CN | ||
| 19.15.2 | - | - | - | KI#2: VFL preparation | - | - | - | Docs:=2 | - |
| 19.15.2 | S2-2503252 | CR | Approval | 23.288 CR1431 (Rel-19, 'F'): Updates on VFL preparation | Interdigital | Rel-19 | AIML_CN | ||
| 19.15.2 | S2-2503348 | CR | Approval | 23.288 CR1436 (Rel-19, 'F'): Update to VFL preparation procedure | Huawei, HiSilicon | Rel-19 | AIML_CN | ||
| 19.15.2 | - | - | - | KI#2: VFL training (triggering training, sample update, accuracy monitoring) | - | - | - | Docs:=4 | - |
| 19.15.2 | S2-2502865 | CR | Approval | 23.288 CR1413 (Rel-19, 'F'): VFL clients removal during VFL training | ZTE | Rel-19 | AIML_CN | ||
| 19.15.2 | S2-2503237 | CR | Approval | 23.288 CR1427 (Rel-19, 'F'): Correcting triggers for VFL training | Nokia | Rel-19 | AIML_CN | ||
| 19.15.2 | S2-2503251 | CR | Approval | 23.288 CR1430 (Rel-19, 'F'): Update on VFL training | Interdigital | Rel-19 | AIML_CN | ||
| 19.15.2 | S2-2503365 | CR | Approval | 23.288 CR1440 (Rel-19, 'F'): Update and Resolve ENs for VFL Training Procedure | LG Electronics | Rel-19 | AIML_CN | ||
| 19.15.2 | - | - | - | KI#2: VFL inference | - | - | - | Docs:=4 | - |
| 19.15.2 | S2-2502860 | CR | Approval | 23.288 CR1408 (Rel-19, 'F'): Clarifications on VFL inference | ZTE | Rel-19 | AIML_CN | ||
| 19.15.2 | S2-2503233 | DISCUSSION | Discussion | Parameters from Analytics Request also required for VFL inference | Nokia | Rel-19 | |||
| 19.15.2 | S2-2503235 | CR | Approval | 23.288 CR1426 (Rel-19, 'F'): Parameters for vertical federated learning inference procedure | Nokia | Rel-19 | AIML_CN | ||
| 19.15.2 | S2-2503349 | CR | Approval | 23.288 CR1437 (Rel-19, 'F'): Update the inference service for VFL | Huawei, HiSilicon | Rel-19 | AIML_CN | ||
| 19.15.2 | - | - | - | KI#2: Intermediate results sharing b/w VFL clients | - | - | - | Docs:=1 | - |
| 19.15.2 | S2-2503240 | CR | Approval | 23.288 CR1428 (Rel-19, 'F'): Correcting procedures for Exchanging intermediate results between VFL clients | Nokia | Rel-19 | AIML_CN | ||
| 19.15.2 | - | - | - | KI#2: VFL services | - | - | - | Docs:=1 | - |
| 19.15.2 | S2-2503242 | CR | Approval | 23.501 CR5676R4 (Rel-19, 'F'): KI#2: VFL services | Nokia | Rel-19 | AIML_CN | Revision of (Unhandled) S2-2501499 | |
| 19.15.2 | - | - | - | KI#3 - NWDAF-assisted policy control and QoS enhancement) | - | - | - | Docs:=3 | - |
| 19.15.2 | S2-2502864 | CR | Approval | 23.288 CR1412 (Rel-19, 'F'): Output parameters clarifications in KI#3 | ZTE | Rel-19 | AIML_CN | ||
| 19.15.2 | S2-2502934 | CR | Approval | 23.288 CR1416 (Rel-19, 'F'): Corrections on input data for QoS and policy assistance analytics | ETRI | Rel-19 | AIML_CN | Merge into S2-2503410 | |
| 19.15.2 | S2-2503565 | CR | Approval | 23.288 CR1448 (Rel-19, 'F'): Further corrections on QoS and policy assistance analytics | CATT | Rel-19 | AIML_CN | ||
| 19.15.2 | - | - | - | KI#4 - Signalling storm mitigation | - | - | - | Docs:=4 | - |
| 19.15.2 | - | - | - | KI#4: TS 23.288 | - | - | - | Docs:=5 | - |
| 19.15.2 | S2-2502862 | CR | Approval | 23.288 CR1410 (Rel-19, 'F'): General maintenance of KI#4 | ZTE | Rel-19 | AIML_CN | ||
| 19.15.2 | S2-2503119 | CR | Approval | 23.288 CR1400R1 (Rel-19, 'F'): Correction of NF Signalling Information for Signalling Storm Analytics | NTT DOCOMO | Rel-19 | AIML_CN | Revision of (Unhandled) S2-2501996 | |
| 19.15.2 | S2-2503135 | CR | Approval | 23.288 CR1419 (Rel-19, 'F'): Clarifying Signalling Storm Analytics | Huawei, HiSilicon | Rel-19 | AIML_CN | ||
| 19.15.2 | S2-2503136 | CR | Approval | 23.288 CR1420 (Rel-19, 'F'): Adding SCP as data source for NWDAF data collection | Huawei, HiSilicon | Rel-19 | AIML_CN | ||
| 19.15.2 | S2-2503368 | CR | Approval | 23.288 CR1442 (Rel-19, 'F'): Clarification on Signalling Storm Analytics | LG Electronics | Rel-19 | AIML_CN | ||
| 19.15.2 | - | - | - | KI#4: TS 23.501 | - | - | - | Docs:=2 | - |
| 19.15.2 | S2-2503134 | CR | Approval | 23.501 CR6184 (Rel-19, 'F'): Correction on usage of signalling storm analytics for reliability of NF services | Huawei, HiSilicon | Rel-19 | AIML_CN | ||
| 19.15.2 | S2-2503282 | CR | Approval | 23.501 CR6108R1 (Rel-19, 'F'): CR for 23.501 AIML_CN SCP related alignment | Vivo | Rel-19 | AIML_CN | Revision of (Unhandled) S2-2501761 | |
| 19.15.2 | - | - | - | KI#4: TS 23.502 | - | - | - | Docs:=2 | - |
| 19.15.2 | S2-2503111 | CR | Approval | 23.502 CR5238R2 (Rel-19, 'F'): Exposure of control plane signalling information from NFs | NTT DOCOMO | Rel-19 | AIML_CN | Revision of (Unhandled) S2-2501995 | |
| 19.15.2 | S2-2503411 | CR | Approval | 23.502 CR5350R1 (Rel-19, 'F'): NF discovery for signaling data collection related to signaling storm analytics | China Mobile | Rel-19 | AIML_CN | Revision of (Unhandled) S2-2501703 | |
| 19.16 | - | - | - | Indirect Network Sharing (TEI19_NetShare) | - | - | Andy | Docs:=2 | - |
| 19.16 | S2-2503057 | CR | Approval | 23.501 CR6179 (Rel-19, 'F'): Clarification on Indirect Network Sharing | China Unicom | Rel-19 | TEI19_NetShare | ||
| 19.16 | S2-2503876 | CR | Approval | 23.501 CR6271 (Rel-19, 'F'): Missing PLMN ID definition in GUAMI. | Samsung | Rel-19 | TEI19_NetShare | ||
| 19.17 | - | - | - | Architecture support of roaming value-added services (TEI19_RVAS) | - | - | Andy | Docs:=0 | - |
| 19.18 | - | - | - | Minimize the Number of Policy Associations (TEI19_MINPA) | - | - | Andy | Docs:=0 | - |
| 19.19 | - | - | - | Deferred 5GC-MT-LR Procedure for Periodic Location Events based NRPPa Periodic Measurement Reports (TEI19_DLPMR) | - | - | Andy | Docs:=0 | - |
| 19.20 | - | - | - | Providing per-subscriber VLAN instructions from UDM (TEI19_VLANSUB) | - | - | Andy | Docs:=0 | - |
| 19.21 | - | - | - | Enhancing Parameter Provisioning with static UE IP address and UP security policy (TEI19_IP_SP_EXP) | - | - | Andy | Docs:=0 | - |
| 19.22 | - | - | - | Spending Limits for UE Policies in Roaming scenario (TEI19_SLUPiR) | - | - | Andy | Docs:=0 | - |
| 19.23 | - | - | - | Subscription control for reference time distribution in EPS (TEI19_TIME_SUB_EPS) | - | - | Andy | Docs:=0 | - |
| 19.24 | - | - | - | On-demand broadcast of GNSS assistance data (TEI19_OBGAD) | - | - | Andy | Docs:=0 | - |
| 19.25 | - | - | - | QoS monitoring (TEI19_QME) | - | - | Andy | Docs:=0 | - |
| 19.26 | - | - | - | NF discovery and selection by target PLMN (TEI19_NFsel_by_tPLMN) | - | - | Andy | Docs:=0 | - |
| 19.27 | - | - | - | Roaming traffic offloading via session breakout in HPLMN (TEI19_HSBO) | - | - | Andy | Docs:=0 | - |
| 19.28 | - | - | - | Multiple Location Procedure for Emergency LCS Routing (TEI19_MLR4RTR) | - | - | Andy | Docs:=0 | - |
| 19.29 | - | - | - | Support for ProSe services in NPNs (TEI19_ProSe_NPN) | - | - | Andy | Docs:=0 | - |
| 19.30 | - | - | - | MSISDN verification operation support to Nnef_UEId Service (TEI19_MVOSNS) | - | - | Andy | Docs:=0 | - |
| 19.31 | - | - | - | ATSSS Rule Provisioning via 3GPP access connected to EPC (TEI19_ARP3E) | - | - | Andy | Docs:=0 | - |
| 19.32 | - | - | - | Network Controlled Network Slice Selection (TEI19_SliceSel) | - | - | Andy | Docs:=14 | - |
| 19.32 | - | - | - | LS in | - | - | - | Docs:=6 | - |
| 19.32 | S2-2502808 | LS In | Action | LS from CT WG3: LS on AF requested network slice replacement | CT WG3 (C3-250572) | TEI19_SliceSel | Responses drafted in S2-2503126, S2-2503619, S2-2503672 | ||
| 19.32 | S2-2503126 | LS OUT | Approval | [DRAFT] LS reply on AF requested network slice replacement | Huawei, HiSilicon | TEI19_SliceSel | Response to S2-2502808 | ||
| 19.32 | S2-2503619 | LS OUT | Approval | [DRAFT] LS Response on AF requested network slice replacement | ZTE | Rel-19 | TEI19_SliceSel | Response to S2-2502808 | |
| 19.32 | S2-2503672 | LS OUT | Approval | [DRAFT] Reply LS on AF requested network slice replacement | Samsung | Rel-19 | Response to S2-2502808 | ||
| 19.32 | S2-2503128 | CR | Approval | 23.502 CR5415 (Rel-19, 'F'): Clarification on AF requested network slice replacement | Huawei, HiSilicon | Rel-19 | TEI19_SliceSel | Confirm Spec version used - CR states 19.2.0! | |
| 19.32 | S2-2503618 | CR | Approval | 23.503 CR1552 (Rel-19, 'F'): Clarification on notifying the outcome of network slice replacement to AF | ZTE | Rel-19 | TEI19_SliceSel | ||
| 19.32 | - | - | - | Configured NSSAI | - | - | - | Docs:=3 | - |
| 19.32 | S2-2503676 | DISCUSSION | Information | Discussion on removal of Replaced S-NSSAI from Configured NSSAI for AF triggered slice replacement. | Samsung | Rel-19 | |||
| 19.32 | S2-2503694 | CR | Approval | 23.501 CR6248 (Rel-19, 'F'): Addressing EN for AF requested slice selection | Samsung, LG Electronics | Rel-19 | TEI19_SliceSel | ||
| 19.32 | S2-2503187 | CR | Approval | 23.501 CR6190 (Rel-19, 'F'): Removal of EN about Configured NSSAI | Nokia | Rel-19 | TEI19_SliceSel | ||
| 19.32 | - | - | - | Slice replacement termination | - | - | - | Docs:=4 | - |
| 19.32 | S2-2502922 | CR | Approval | 23.501 CR6167 (Rel-19, 'F'): Support for Network initiated Slice Replacement Termination | Ericsson | Rel-19 | TEI19_SliceSel | ||
| 19.32 | S2-2503204 | CR | Approval | 23.501 CR6192 (Rel-19, 'F'): On the termination of slice replacement | Nokia | Rel-19 | TEI19_SliceSel | ||
| 19.32 | S2-2503205 | CR | Approval | 23.502 CR5418 (Rel-19, 'F'): Clarification of Nnef_AMFInfluence based approach to AF requested network slice replacement | Nokia | Rel-19 | TEI19_SliceSel | ||
| 19.32 | S2-2503127 | CR | Approval | 23.503 CR1532 (Rel-19, 'F'): Clarification on AF requested network slice replacement | Huawei, HiSilicon | Rel-19 | TEI19_SliceSel | Confirm Spec version used - CR states 19.2.0! | |
| 19.32 | - | - | - | Other aspects | - | - | - | Docs:=1 | - |
| 19.32 | S2-2503202 | CR | Approval | 23.501 CR6191 (Rel-19, 'F'): Feature interaction resolution | Nokia | Rel-19 | TEI19_SliceSel | ||
| 19.33 | - | - | - | PRU Usage Extension supported by Core Network (TEI19_PRUE) | - | - | Andy | Docs:=0 | - |
| 19.48 | - | - | - | Generic Rel-19 CRs | - | - | _Not_on_Agenda | Docs:=0 | - |
| 19.49 | - | - | - | Generic Rel-19 LSs | - | - | _Not_on_Agenda | Docs:=0 | - |
| 19.50 | - | - | - | Rel-19 CAT B/C alignment CR(s) due to the work led by other 3GPP Working Groups | - | - | Andy | Docs:=11 | - |
| 19.50 | - | - | - | eDRX and emergency | - | - | - | Docs:=6 | - |
| 19.50 | S2-2502969 | CR | Approval | 23.501 CR6084R1 (Rel-17, 'F'): Clarification of eDRX application with emergency service | Ericsson, AT&T, Qualcomm Incorporated | Rel-17 | NR_newRAT-Core, NR_redcap-Core, 5G_CIoT, TEI17 | Revision of (Unhandled) S2-2501587. Check WI Code Capitalization (NR_redCap-Core)! | |
| 19.50 | S2-2502970 | CR | Approval | 23.501 CR6085R1 (Rel-18, 'A'): Clarification of eDRX application with emergency service | Ericsson, AT&T, Qualcomm Incorporated | Rel-18 | NR_newRAT-Core, NR_redcap-Core, 5G_CIoT, TEI17 | Revision of (Unhandled) S2-2501588. Check WI Code Capitalization (NR_redCap-Core)! | |
| 19.50 | S2-2502971 | CR | Approval | 23.501 CR6086R1 (Rel-19, 'A'): Clarification of eDRX application with emergency service | Ericsson, AT&T, Qualcomm Incorporated | Rel-19 | NR_newRAT-Core, NR_redcap-Core, 5G_CIoT, TEI17 | Revision of (Unhandled) S2-2501589. Check WI Code Capitalization (NR_redCap-Core)! | |
| 19.50 | S2-2502972 | CR | Approval | 23.502 CR5338R1 (Rel-17, 'F'): Clarification on emergency PDU session release | Ericsson, AT&T, Qualcomm Incorporated, MediaTek Inc | Rel-17 | NR_newRAT-Core, NR_redcap-Core, 5G_CIoT, TEI17 | Revision of (Unhandled) S2-2501590. Check WI Code Capitalization (NR_redCap-Core)! | |
| 19.50 | S2-2502973 | CR | Approval | 23.502 CR5339R1 (Rel-18, 'A'): Clarification on emergency PDU session release | Ericsson, AT&T, Qualcomm Incorporated, MediaTek Inc | Rel-18 | NR_newRAT-Core, NR_redcap-Core, 5G_CIoT, TEI17 | Revision of (Unhandled) S2-2501591. Check WI Code Capitalization (NR_redCap-Core)! | |
| 19.50 | S2-2502974 | CR | Approval | 23.502 CR5340R1 (Rel-19, 'A'): Clarification on emergency PDU session release | Ericsson, AT&T, Qualcomm Incorporated, MediaTek Inc | Rel-19 | NR_newRAT-Core, NR_redcap-Core, 5G_CIoT, TEI17 | Revision of (Unhandled) S2-2501592. Check WI Code Capitalization (NR_redCap-Core)! | |
| 19.50 | - | - | - | PSAP emergency callback | - | - | - | Docs:=2 | - |
| 19.50 | S2-2503831 | CR | Approval | 23.401 CR3898R1 (Rel-19, 'F'): PSAP emergency callback interaction with PSM | Vodafone | Rel-19 | EMC1, SIMTC, TEI19 | Revision of S2-2502147 | |
| 19.50 | S2-2503854 | CR | Approval | 23.501 CR6267 (Rel-19, 'F'): Correction of PSAP call-back terminology | Vodafone | Rel-19 | TEI19 | ||
| 19.50 | - | - | - | LP-WUS subgrouping | - | - | - | Docs:=2 | - |
| 19.50 | S2-2502821 | LS In | Action | LS from RAN WG2: Reply LS on LP-WUS subgrouping | RAN WG2 (R2-2501388) | NR_LPWUS-Core | Reply to S2-2412876 | ||
| 19.50 | S2-2503667 | CR | Approval | 23.501 CR6247 (Rel-19, 'F'): Multi-RAN-vendor support for paging of LP-WUS UEs | Vodafone | Rel-19 | NR_LPWUS | ||
| 19.50 | - | - | - | CHF Group ID | - | - | - | Docs:=1 | - |
| 19.50 | S2-2503333 | CR | Approval | 23.502 CR5433 (Rel-19, 'F'): CHF Group ID in the needed contexts | Nokia | Rel-19 | CHFSeg, TEI19 | ||
| 19.50 | - | - | - | Other | - | - | - | Docs:=19 | - |
| 20 | - | - | - | Rel-20 SIDs and WIDs | - | - | Andy | Docs:=0 | - |
| 20.1.1 | - | - | - | Study on Integration of satellite components in the 5G architecture Phase 4 (FS_5GSAT_Ph4_ARC) | - | - | Dario | Docs:=51 | - |
| 20.1.1 | - | - | - | TR Skeleton and TR Scope | - | - | - | Docs:=2 | - |
| 20.1.1 | S2-2503741 | P-CR | Approval | 23.700-19: FS_5GSAT_Ph4_ARC TR Skeleton. | CATT | Rel-20 | FS_5GSAT_Ph4_ARC | Handle | |
| 20.1.1 | S2-2503742 | P-CR | Approval | 23.700-19: FS_5GSAT_Ph4_ARC TR Scope. | CATT | Rel-20 | FS_5GSAT_Ph4_ARC | Handle | |
| 20.1.1 | - | - | - | Architectural assumptions | - | - | - | Docs:=11 | - |
| 20.1.1 | S2-2503487 | P-CR | Approval | 23.700-19: 23.700-19: Architecture principles and assumptions . | Vivo | Rel-20 | FS_5GSAT_Ph4_ARC | Handle baseline for WT-1 | |
| 20.1.1 | S2-2503232 | P-CR | Approval | 23.700-19: WT1:Architecture assumptions for normal IMS voice call over GEO via NB-IoT NTN connecting to EPC. | Qualcomm Incorporated | Rel-20 | FS_5GSAT_Ph4_ARC | Merge into S2-2503487? | |
| 20.1.1 | S2-2503743 | P-CR | Approval | 23.700-19: FS_5GSAT_Ph4_ARC Architecture Assumptions. | CATT, CSCN | Rel-20 | FS_5GSAT_Ph4_ARC | Merge into S2-2503487? | |
| 20.1.1 | S2-2503529 | P-CR | Approval | 23.700-19: Architectural Assumptions and Principles for Supporting of IMS voice over GEO NB-IoT NTN connecting to EPC. | Xiaomi | Rel-20 | FS_5GSAT_Ph4_ARC | Merge into S2-2503487? | |
| 20.1.1 | S2-2503269 | P-CR | Approval | 23.700-19: Architecture assumptions for IMS voice call over NB-IoT (GEO). | Ericsson | Rel-20 | FS_5GSAT_Ph4_ARC | Merge into S2-2503487? | |
| 20.1.1 | S2-2503657 | P-CR | Approval | 23.700-19: [AA] Architecture assumptions. | Huawei, HiSilicon | Rel-20 | FS_5GSAT_Ph4_ARC | Handle baseline for WT-2. Merge WT-1 part into S2-2503487? | |
| 20.1.1 | S2-2503080 | P-CR | Approval | 23.700-19: FS_5GSAT_Ph4_ARC Architecture Assumptions. | Nokia | Rel-20 | FS_5GSAT_Ph4_ARC | Merge into S2-2503487 and S2-2503657? | |
| 20.1.1 | S2-2503362 | P-CR | Approval | 23.700-19: Architectural Assumptions. | LG Electronics | Rel-20 | FS_5GSAT_Ph4_ARC | Merge into S2-2503487 and S2-2503657? | |
| 20.1.1 | S2-2503860 | P-CR | Approval | 23.700-19: Architectural assumptions and principles for 23.700-19. | TNO | Rel-20 | FS_5GSAT_Ph4_ARC | Merge into S2-2503487 and S2-2503657? | |
| 20.1.1 | S2-2503878 | P-CR | Approval | 23.700-19: Architectural Assumptions and Principles. | Samsung | Rel-20 | FS_5GSAT_Ph4_ARC | Merge into S2-2503487 and S2-2503657? | |
| 20.1.1 | S2-2503531 | P-CR | Approval | 23.700-19: Architectural Assumptions and Principles for UE-SAT-UE communication enhancement. | Xiaomi | Rel-20 | FS_5GSAT_Ph4_ARC | Merge into S2-2503657? | |
| 20.1.1 | - | - | - | KI for WT1 (IMS voice call over GEO via NB-IoT NTN connecting to EPC) | - | - | - | Docs:=12 | - |
| 20.1.1 | S2-2503486 | DISCUSSION | Discussion | Discussion paper on CP/UP-based solutions | vivo | Rel-20 | FS_5GSAT_Ph4_ARC | Handle | |
| 20.1.1 | S2-2503497 | DISCUSSION | Discussion | Emergency Call Optimization and IMS Registration optimization needs to be included in the scope for voice using GEO. | MediaTek Inc. | Rel-20 | FS_5GSAT_Ph4_ARC | Handle | |
| 20.1.1 | S2-2503744 | P-CR | Approval | 23.700-19: FS_5GSAT_Ph4_ARC Key issues for WT#1. | CATT, vivo | Rel-20 | FS_5GSAT_Ph4_ARC | Handle - baseline | |
| 20.1.1 | S2-2503488 | P-CR | Approval | 23.700-19: FS_5GSAT_Ph4-ARC Key issue on Support of IMS voice over NB-IoT (GEO) satellite access to EPC. | Vivo, MediaTek Inc. | Rel-20 | FS_5GSAT_Ph4_ARC | Merge into S2-2503744? | |
| 20.1.1 | S2-2503077 | P-CR | Approval | 23.700-19: FS_5GSAT_Ph4_ARC Key issues for WT#1: Support of IMS voice over GEO NB-IoT NTN connecting to EPC. | Nokia | Rel-20 | FS_5GSAT_Ph4_ARC | Merge into S2-2503744? | |
| 20.1.1 | S2-2503389 | P-CR | Approval | 23.700-19: 23.700-19: Key issues for QoS aspect of GEO call. | China Telecom | Rel-20 | FS_5GSAT_Ph4_ARC | Merge into S2-2503744? | |
| 20.1.1 | S2-2503528 | P-CR | Approval | 23.700-19: Key issues for WT#1: Support of IMS voice over GEO via NB-IoT NTN connecting to EPC. | Xiaomi | Rel-20 | FS_5GSAT_Ph4_ARC | Merge into S2-2503744? | |
| 20.1.1 | S2-2503658 | P-CR | Approval | 23.700-19: [WT1] WT1 Key Issues. | Huawei, HiSilicon | Rel-20 | FS_5GSAT_Ph4_ARC | Merge into S2-2503744? | |
| 20.1.1 | S2-2503765 | P-CR | Approval | 23.700-19: New KI: IMS enhancements and optimizations to support NB-IoT as IP-CAN. | China Mobile | Rel-20 | FS_5GSAT_Ph4_ARC | Merge into S2-2503744? | |
| 20.1.1 | S2-2503165 | P-CR | Approval | 23.700-19: Key issue for WT#1: Support of IMS voice over GEO NB-IoT NTN connecting to EPC. | Samsung | Rel-20 | FS_5GSAT_Ph4_ARC | Merge into S2-2503744? | |
| 20.1.1 | S2-2503320 | P-CR | Approval | 23.700-19: FS_5GSAT_Ph4_ARC New Key Issue: QoS Support for IMS voice service over GEO satellite. | OPPO | Rel-20 | FS_5GSAT_Ph4_ARC | Merge into S2-2503744? | |
| 20.1.1 | S2-2503321 | P-CR | Approval | 23.700-19: FS_5GSAT_Ph4_ARC New Key Issue: IMS procedure enhancement and potential optimization for IMS voice over GEO satellite. | OPPO | Rel-20 | FS_5GSAT_Ph4_ARC | Merge into S2-2503744? | |
| 20.1.1 | - | - | - | KI for WT2 (UE-SAT-UE comm. enh. for 5GS under NR NTN NGSO const. w/ feeder link available) | - | - | - | Docs:=11 | - |
| 20.1.1 | S2-2503166 | P-CR | Approval | 23.700-19: Key issue for WT#2: UE-SAT-UE communication enhancement for NR NTN NGSO constellation with feeder link available. | Samsung | Rel-20 | FS_5GSAT_Ph4_ARC | Handle - baseline (presented in CC) | |
| 20.1.1 | S2-2503861 | P-CR | Approval | 23.700-19: 23.700-19 Key Issues: UE-SAT-UE communication for non-IMS services. | TNO | Rel-20 | FS_5GSAT_Ph4_ARC | Merge into S2-2503166 | |
| 20.1.1 | S2-2503277 | P-CR | Approval | 23.700-19: 23.700-19: Key issues for UE-SAT-UE communication for non-IMS services. | China Telecom | Rel-20 | FS_5GSAT_Ph4_ARC | Merge into S2-2503166 | |
| 20.1.1 | S2-2503584 | P-CR | Approval | 23.700-19: 23.700-19: Key Issue on support of 5G-LAN with satellite access. | Vivo | Rel-20 | FS_5GSAT_Ph4_ARC | Merge into S2-2503166 | |
| 20.1.1 | S2-2503468 | P-CR | Approval | 23.700-19: 23.700-19: Key issue for WT#2.2: UE-SAT-UE communication via UPF only onboard satellite for non-IMS services. | ETRI | Rel-20 | FS_5GSAT_Ph4_ARC | Merge into S2-2503166 | |
| 20.1.1 | S2-2503530 | P-CR | Approval | 23.700-19: Key issues for WT#2: Support of UE-SAT-UE communication enhancment. | Xiaomi | Rel-20 | FS_5GSAT_Ph4_ARC | Merge into S2-2503166 | |
| 20.1.1 | S2-2503491 | P-CR | Approval | 23.700-19: Key issue for WT#2.2. | China Mobile | Rel-20 | FS_5GSAT_Ph4_ARC | ||
| 20.1.1 | S2-2503745 | P-CR | Approval | 23.700-19: FS_5GSAT_Ph4_ARC Key issues for WT#2_2. | CATT, CSCN | Rel-20 | FS_5GSAT_Ph4_ARC | Merge into S2-2503166 | |
| 20.1.1 | S2-2503659 | P-CR | Approval | 23.700-19: [WT2] WT2 Key Issues. | Huawei, HiSilicon | Rel-20 | FS_5GSAT_Ph4_ARC | Merge into S2-2503166 | |
| 20.1.1 | S2-2503078 | P-CR | Approval | 23.700-19: FS_5GSAT_Ph4_ARC Key issue for WT#2: UE-SAT-UE communication enhancement for NR NTN NGSO constellation with feeder link available. | Nokia | Rel-20 | FS_5GSAT_Ph4_ARC | Merge into S2-2503166 | |
| 20.1.1 | S2-2503766 | P-CR | Approval | 23.700-19: New KI: Support of UE-SAT-UE communication for roaming case. | China Mobile | Rel-20 | FS_5GSAT_Ph4_ARC | Postponed? | |
| 20.1.1 | - | - | - | Solution for WT1 (Max 2 rounds; Max 1 paper per company per round) | - | - | - | Docs:=15 | - |
| 20.1.1 | S2-2503019 | P-CR | Approval | 23.700-19: New solution of IMS call setup procedure simplification for WT#1 GEO voice support. | OPPO | Rel-20 | FS_5GSAT_Ph4_ARC | Handle if time allows | |
| 20.1.1 | S2-2503220 | P-CR | Approval | 23.700-19: WT1: Solution for providing IMS voice over GEO via Control Plane. | Qualcomm Incorporated | Rel-20 | FS_5GSAT_Ph4_ARC | Handle if time allows | |
| 20.1.1 | S2-2503221 | P-CR | Approval | 23.700-19: WT1: Solution for providing IMS voice over GEO via User Plane. | Qualcomm Incorporated | Rel-20 | FS_5GSAT_Ph4_ARC | Handle if time allows | |
| 20.1.1 | S2-2503311 | P-CR | Approval | 23.700-19: WT1: Solution for IMS signaling performance optimization to support voice over GEO . | Qualcomm Incorporated | Rel-20 | FS_5GSAT_Ph4_ARC | ||
| 20.1.1 | S2-2503346 | P-CR | Approval | 23.700-19: KI #1: New Sol: U-plane-based IMS service via NB-IoT access. | Nokia | Rel-20 | FS_5GSAT_Ph4_ARC | Handle if time allows | |
| 20.1.1 | S2-2503489 | P-CR | Approval | 23.700-19: Solution for UP-based NB-IoT (GEO) supporting IMS voice. | Vivo | Rel-20 | FS_5GSAT_Ph4_ARC | Handle if time allows | |
| 20.1.1 | S2-2503490 | P-CR | Approval | 23.700-19: Solution for CP-based NB-IoT (GEO) supporting IMS voice. | Vivo | Rel-20 | FS_5GSAT_Ph4_ARC | Handle if time allows | |
| 20.1.1 | S2-2503501 | P-CR | Approval | 23.700-19: KI #X: New Solution: CST reduction by pre-negotiate SDP parameters during SIP registration. | MediaTek Inc. | Rel-20 | FS_5GSAT_Ph4_ARC | ||
| 20.1.1 | S2-2503504 | P-CR | Approval | 23.700-19: KI #X: New Solution: IMS PDN Activation with both default and dedicated EPS bearer contexts. | MediaTek Inc. | Rel-20 | FS_5GSAT_Ph4_ARC | Handle if time allows | |
| 20.1.1 | S2-2503505 | P-CR | Approval | 23.700-19: KI #X: New Solution: IMS PDN as first PDN connection. | MediaTek Inc. | Rel-20 | FS_5GSAT_Ph4_ARC | Handle if time allows | |
| 20.1.1 | S2-2503532 | P-CR | Approval | 23.700-19: KI#X: New Sol: Support QoS differentiation for CP based IMS voice service over NB-IoT NTN. | Xiaomi | Rel-20 | FS_5GSAT_Ph4_ARC | Handle if time allows | |
| 20.1.1 | S2-2503575 | P-CR | Approval | 23.700-19: KI#1: New Sol: Support of CP/UP combination and QoS for IMS voice service over GEO satellite. | NTT DOCOMO | Rel-20 | FS_5GSAT_Ph4_ARC | Handle if time allows | |
| 20.1.1 | S2-2503576 | P-CR | Approval | 23.700-19: KI#1: New Sol: Support of capability exchange and NAS timer adjustment for IMS voice service over GEO satellite. | NTT DOCOMO | Rel-20 | FS_5GSAT_Ph4_ARC | ||
| 20.1.1 | S2-2503638 | P-CR | Approval | 23.700-19: KI #X: New Solution: CST reduction by pre-negotiate SDP parameters with an early SIP INVITE. | MediaTek Inc. | Rel-20 | FS_5GSAT_Ph4_ARC | ||
| 20.1.1 | S2-2503660 | P-CR | Approval | 23.700-19: [New Sol] Connection setup for NB-IoT IMS call over GEO. | Huawei, HiSilicon | Rel-20 | FS_5GSAT_Ph4_ARC | Handle if time allows | |
| 20.1.1 | - | - | - | Not in the scope of SID | - | - | - | Docs:=0 | - |
| 20.2.1 | - | - | - | Study on Architecture Enhancement to support Integrated Sensing and Communication (FS_Sensing_ARC) | - | - | Wanqiang | Docs:=90 | - |
| 20.2.1 | - | - | - | TR skeleton and scope | - | - | - | Docs:=2 | - |
| 20.2.1 | S2-2502943 | P-CR | Approval | 23.700-14: TR Skeleton for FS_Sensing_ARC | Apple, Xiaomi | Rel-20 | FS_Sensing_ARC | Handle Skeleton TR | |
| 20.2.1 | S2-2502944 | P-CR | Approval | 23.700-14: TR Scope for FS_Sensing_ARC . | Apple, Xiaomi | Rel-20 | FS_Sensing_ARC | Handle | |
| 20.2.1 | - | - | - | Terms and Definitions | - | - | - | Docs:=4 | - |
| 20.2.1 | S2-2503798 | P-CR | Approval | 23.700-14: Terms of Sensing study. | Huawei, HiSilicon | Rel-20 | FS_Sensing_ARC | Handle - use as baseline | |
| 20.2.1 | S2-2503445 | P-CR | Approval | 23.700-14: Adding Definitions and terminologies. | ZTE | Rel-20 | FS_Sensing_ARC | Merge into S2-2503798 | |
| 20.2.1 | S2-2503705 | P-CR | Approval | 23.700-14: Terms for the 5GS sensing architecture. | Lenovo | Rel-20 | FS_Sensing_ARC | Merge into S2-2503798 | |
| 20.2.1 | S2-2503865 | P-CR | Approval | 23.700-14: Terms for FS_Sensing_ARC . | Xiaomi | Rel-20 | FS_Sensing_ARC | Merge into S2-2503798 | |
| 20.2.1 | - | - | - | Architectural assumptions and requirements | - | - | - | Docs:=16 | - |
| 20.2.1 | S2-2502960 | P-CR | Approval | 23.700-14: Adding Architecture assumptions and requirements. | Ericsson | Rel-20 | FS_Sensing_ARC | Handle - use as baseline for architectural requirement | |
| 20.2.1 | S2-2503272 | P-CR | Approval | 23.700-14: Architectural Assumptions and Requirements for sensing service. | China Telecom | Rel-20 | FS_Sensing_ARC | Handle - use as baseline for architectural assumption | |
| 20.2.1 | S2-2503771 | P-CR | Approval | 23.700-14: Architectural Requirements of ISAC. | Nokia, Nokia Shanghai Bell | Rel-20 | FS_Sensing_ARC | Handle | |
| 20.2.1 | S2-2503704 | P-CR | Approval | 23.700-14: Architectural assumptions for the 5GS sensing architecture. | Lenovo | Rel-20 | FS_Sensing_ARC | Handle | |
| 20.2.1 | S2-2503028 | P-CR | Approval | 23.700-14: Architectural Assumptions and Requirements. | LG Electronics | Rel-20 | FS_Sensing_ARC | Merge architectural assumption into S2-2503272, architectural requirement part into S2-2502960 | |
| 20.2.1 | S2-2503064 | P-CR | Approval | 23.700-14: Architectural Assumptions and Requirements for ISAC. | Vivo | Rel-20 | FS_Sensing_ARC | Merge architectural assumption into S2-2503272, architectural requirement part into S2-2502960 | |
| 20.2.1 | S2-2503101 | P-CR | Approval | 23.700-14: Architecture assumptions and requirements. | OPPO | Rel-20 | FS_Sensing_ARC | Merge architectural assumption into S2-2503272, architectural requirement part into S2-2502960 | |
| 20.2.1 | S2-2503145 | P-CR | Approval | 23.700-14: Architectural Assumptions for Sensing. | Ofinno | Rel-20 | FS_Sensing_ARC | Merge architectural assumption into S2-2503272, architectural requirement part into S2-2502960, Key issue part merge into S2-2503079 | |
| 20.2.1 | S2-2503222 | P-CR | Approval | 23.700-14: Architectural Assumptions and Requirements for FS_Sensing. | Rel-20 | FS_Sensing_ARC | Merge architectural assumption into S2-2503272, architectural requirement part into S2-2502960 | ||
| 20.2.1 | S2-2503236 | P-CR | Approval | 23.700-14: Architectural Assumptions and Principles for ISAC . | InterDigital Inc. | Rel-20 | FS_Sensing_ARC | Merge architectural assumption into S2-2503272, architectural requirement part into S2-2502960 | |
| 20.2.1 | S2-2503413 | DISCUSSION | Discussion | Discussion on Architecture Assumption for ISAC study. | China Mobile | Not handle | |||
| 20.2.1 | S2-2503420 | P-CR | Approval | 23.700-14: Architectural assumptions and Architectural Requirements. | China Mobile | Rel-20 | FS_Sensing_ARC | Merge architectural assumption into S2-2503272, architectural requirement part into S2-2502960 | |
| 20.2.1 | S2-2503444 | P-CR | Approval | 23.700-14: ISAC Architectural Assumptions and Requirements. | ZTE | Rel-20 | FS_Sensing_ARC | Merge architectural assumption into S2-2503272, architectural requirement part into S2-2502960 | |
| 20.2.1 | S2-2503770 | P-CR | Approval | 23.700-14: Architectural Assumptions of ISAC. | Nokia, Nokia Shanghai Bell | Rel-20 | FS_Sensing_ARC | Merge architectural assumption into S2-2503272 | |
| 20.2.1 | S2-2503799 | P-CR | Approval | 23.700-14: Architecture assumptions of Sensing study. | Huawei, HiSilicon | Rel-20 | FS_Sensing_ARC | Merge architectural assumption into S2-2503272, architectural requirement part into S2-2502960 | |
| 20.2.1 | S2-2503819 | P-CR | Approval | 23.700-14: TR 23.700-14: FS_Sensing-ARC architecture requirements and assumptions . | Qualcomm Incorporated | Rel-20 | FS_Sensing_ARC | Merge architectural assumption into S2-2503272, architectural requirement part into S2-2502960 | |
| 20.2.1 | - | - | - | Key issues related WT#1 | - | - | - | Docs:=12 | - |
| 20.2.1 | S2-2503079 | P-CR | Approval | 23.700-14: New Key Issue on Sensing Architecture . | Apple | Rel-20 | FS_Sensing_ARC | Handle - use as baseline | |
| 20.2.1 | S2-2503446 | P-CR | Approval | 23.700-14: Key issue#1, Architecture enhancement to support ISAC. | ZTE | Rel-20 | FS_Sensing_ARC | Handle | |
| 20.2.1 | S2-2503061 | P-CR | Approval | 23.700-14: Key issue for WT#1: Architecture support for Integrated Sensing and Communication. | Vivo | Rel-20 | FS_Sensing_ARC | Merge into S2-2503079 | |
| 20.2.1 | S2-2503238 | P-CR | Approval | 23.700-14: New KI: KI for WT#1 for architecture support . | InterDigital Inc. | Rel-20 | FS_Sensing_ARC | Merge into S2-2503079 | |
| 20.2.1 | S2-2503312 | P-CR | Approval | 23.700-14: Key issue for WT#1: Sensing Architecture. | OPPO | Rel-20 | FS_Sensing_ARC | Merge into S2-2503079 | |
| 20.2.1 | S2-2503369 | P-CR | Approval | 23.700-14: Key issue for WT-1: Architecture and function enhancements to support sensing. | Samsung | Rel-20 | FS_Sensing_ARC | Merge into S2-2503079 | |
| 20.2.1 | S2-2503421 | P-CR | Approval | 23.700-14: Key Issue 1: Architecture and function enhancements. | China Mobile | Rel-20 | FS_Sensing_ARC | Merge into S2-2503079 | |
| 20.2.1 | S2-2503574 | P-CR | Approval | 23.700-14: New Key Issue on Supported Sensing Modes . | Apple | Rel-20 | FS_Sensing_ARC | Merge into S2-2503079 | |
| 20.2.1 | S2-2503622 | P-CR | Approval | 23.700-14: TR 23.700-14: New key issue for WT-1 Architecture and function enhancements. | ETRI | Rel-20 | FS_Sensing_ARC | Merge into S2-2503079 | |
| 20.2.1 | S2-2503640 | P-CR | Approval | 23.700-14: 23.700-14: New KI for FS_Sensing_ARC WT#1. | CATT | Rel-20 | FS_Sensing_ARC | Merge into S2-2503079 | |
| 20.2.1 | S2-2503772 | P-CR | Approval | 23.700-14: KI#1 Architecture and function enhancements to support sensing. | Nokia, Nokia Shanghai Bell | Rel-20 | FS_Sensing_ARC | Merge into S2-2503079 | |
| 20.2.1 | S2-2503866 | P-CR | Approval | 23.700-14: New KI#1 architecture and function enhancement to support ISAC service . | Xiaomi | Rel-20 | FS_Sensing_ARC | Merge into S2-2503079 | |
| 20.2.1 | - | - | - | Key issues related WT#2 | - | - | - | Docs:=15 | - |
| 20.2.1 | S2-2503820 | P-CR | Approval | 23.700-14: TR 23.700-14: FS_Sensing-ARC new key issues. | Qualcomm Incorporated | Rel-20 | FS_Sensing_ARC | Handle - use as baseline? | |
| 20.2.1 | S2-2503370 | P-CR | Approval | 23.700-14: Key issue for WT-2: Service authorization and revocation. | Samsung | Rel-20 | FS_Sensing_ARC | Handle | |
| 20.2.1 | S2-2503062 | P-CR | Approval | 23.700-14: Key issue for WT#2 Service authorization and revocation. | Vivo | Rel-20 | FS_Sensing_ARC | Merge into S2-2503820 | |
| 20.2.1 | S2-2503089 | P-CR | Approval | 23.700-14: Key issue for WT#2: Sensing service authurization and revocation. | OPPO | Rel-20 | FS_Sensing_ARC | Merge into S2-2503820 | |
| 20.2.1 | S2-2503176 | P-CR | Approval | 23.700-14: 23.700-14: Key issue X: Sensing area authorization. | OPPO | Rel-20 | FS_Sensing_ARC | Merge into S2-2503820 | |
| 20.2.1 | S2-2503239 | P-CR | Approval | 23.700-14: New KI: KI for WT#2 and WT#5 Service exposure for ISAC . | InterDigital Inc. | Rel-20 | FS_Sensing_ARC | Merge KI related WT#2 into S2-2503820 and KI related WT#5 into into S2-2503423 | |
| 20.2.1 | S2-2503271 | DISCUSSION | Discussion | Analysis of issues to be considered for end-to-end sensing service. | China Telecom | Rel-20 | FS_Sensing_ARC | Not handle | |
| 20.2.1 | S2-2503273 | P-CR | Approval | 23.700-14: TR 23.700-14: Key Issue on sensing configuration, authorization and revocation. | China Telecom | Rel-20 | FS_Sensing_ARC | Merge authorization/revocation part into S2-2503820, and configuration part into S2-2503146 | |
| 20.2.1 | S2-2503426 | P-CR | Approval | 23.700-14: Key Issue 2: Service authorization and revocation. | China Mobile | Rel-20 | FS_Sensing_ARC | Merge into S2-2503820 | |
| 20.2.1 | S2-2503447 | P-CR | Approval | 23.700-14: Key issue#2, Sensing Service authorization and parameter/policy provisioning. | ZTE | Rel-20 | FS_Sensing_ARC | Merge into S2-2503820 | |
| 20.2.1 | S2-2503542 | P-CR | Approval | 23.700-14: New KI: service authorization and revocation for sensing services . | Lenovo | Rel-20 | FS_Sensing_ARC | Merge into S2-2503820 | |
| 20.2.1 | S2-2503623 | P-CR | Approval | 23.700-14: TR 23.700-14: New key issue for WT-2 Service authorization and revocation. | ETRI | Rel-20 | FS_Sensing_ARC | Merge into S2-2503820 | |
| 20.2.1 | S2-2503773 | P-CR | Approval | 23.700-14: KI#2 Service authorization and revocation. | Nokia, Nokia Shanghai Bell | Rel-20 | FS_Sensing_ARC | Merge into S2-2503820 | |
| 20.2.1 | S2-2503815 | P-CR | Approval | 23.700-14: Key Issue for WT2, WT#3 & WT#4: QoS Mechanism. | OPPO | Rel-20 | FS_Sensing_ARC | Merge WT#2 part into S2-2503820, WT#3 part into S2-2503063, WT#4 into S2-2502942 | |
| 20.2.1 | S2-2503867 | P-CR | Approval | 23.700-14: New KI#2 ISAC Service authorization and revocation . | Xiaomi | Rel-20 | FS_Sensing_ARC | Merge into S2-2503820 | |
| 20.2.1 | - | - | - | Key issues related WT#3 | - | - | - | Docs:=12 | - |
| 20.2.1 | S2-2503063 | P-CR | Approval | 23.700-14: Key issue for WT#3 Sensing entities discovery and selection. | Vivo | Rel-20 | FS_Sensing_ARC | Handle - use as baseline | |
| 20.2.1 | S2-2503868 | P-CR | Approval | 23.700-14: New KI#3 Discovery and selection of sensing entities . | Xiaomi | Rel-20 | FS_Sensing_ARC | Handle | |
| 20.2.1 | S2-2503143 | P-CR | Approval | 23.700-14: Key Issue for WT#3 Discovery and selection . | Sony | Rel-20 | FS_Sensing_ARC | Merge into S2-2503063 | |
| 20.2.1 | S2-2503174 | P-CR | Approval | 23.700-14: 23.700-14: Key issue X: Discovery and Selection of Sensing Function. | OPPO | Rel-20 | FS_Sensing_ARC | Merge into S2-2503063 | |
| 20.2.1 | S2-2503175 | P-CR | Approval | 23.700-14: 23.700-14: Key issue X: Discovery and selection of sensing transmitter and receiver. | OPPO | Rel-20 | FS_Sensing_ARC | Merge into S2-2503063 | |
| 20.2.1 | S2-2503274 | P-CR | Approval | 23.700-14: TR 23.700-14: Key Issue on the discovery and selection of sensing entities. | China Telecom | Rel-20 | FS_Sensing_ARC | Merge into S2-2503063 | |
| 20.2.1 | S2-2503371 | P-CR | Approval | 23.700-14: Key issue for WT-3: Discovery and selection of sensing entities . | Samsung | Rel-20 | FS_Sensing_ARC | Merge into S2-2503063 | |
| 20.2.1 | S2-2503427 | P-CR | Approval | 23.700-14: Key Issue 3: Discovery and selection of sensing entities. | China Mobile | Rel-20 | FS_Sensing_ARC | Merge into S2-2503063 | |
| 20.2.1 | S2-2503448 | P-CR | Approval | 23.700-14: Key issue#3, Discovery and selection of sensing entities. | ZTE | Rel-20 | FS_Sensing_ARC | Merge into S2-2503063 | |
| 20.2.1 | S2-2503624 | P-CR | Approval | 23.700-14: TR 23.700-14: New key issue for WT-3 Discovery and selection of sensing entities. | ETRI | Rel-20 | FS_Sensing_ARC | Merge into S2-2503063 | |
| 20.2.1 | S2-2503774 | P-CR | Approval | 23.700-14: KI#3 Discovery and selection of sensing entities. | Nokia, Nokia Shanghai Bell | Rel-20 | FS_Sensing_ARC | Merge into S2-2503063 | |
| 20.2.1 | S2-2503814 | P-CR | Approval | 23.700-14: New KI: KI for WT#3 for discovery and selection of sensing entities . | InterDigital Inc. | Rel-20 | FS_Sensing_ARC | Merge into S2-2503063 | |
| 20.2.1 | - | - | - | Key issues related WT#4 | - | - | - | Docs:=10 | - |
| 20.2.1 | S2-2502942 | P-CR | Approval | 23.700-14: 23.700-14: Key issue X: Sensing data and the associated information collection and transport. | OPPO | Rel-20 | FS_Sensing_ARC | Handle - use as baseline | |
| 20.2.1 | S2-2503625 | P-CR | Approval | 23.700-14: TR 23.700-14: New key issue for WT-4 Sensing data collection and transport. | ETRI | Rel-20 | FS_Sensing_ARC | Handle | |
| 20.2.1 | S2-2503230 | P-CR | Approval | 23.700-14: WT-4: KI#X-UE data collection for sensing service. | Rel-20 | FS_Sensing_ARC | Merge into S2-2502942 | ||
| 20.2.1 | S2-2503372 | P-CR | Approval | 23.700-14: Key issue for WT-4: Sensing and associated data collection and derive sensing result . | Samsung | Rel-20 | FS_Sensing_ARC | Merge into S2-2502942 | |
| 20.2.1 | S2-2503422 | P-CR | Approval | 23.700-14: Key Issue 4: Sensing data collection and transport. | China Mobile | Rel-20 | FS_Sensing_ARC | Merge into S2-2502942 | |
| 20.2.1 | S2-2503449 | P-CR | Approval | 23.700-14: Key issue#4, Sensing data collection and transport. | ZTE | Rel-20 | FS_Sensing_ARC | Merge into S2-2502942 | |
| 20.2.1 | S2-2503543 | P-CR | Approval | 23.700-14: New KI: sensing data and associated information collection and transmission. | Lenovo | Rel-20 | FS_Sensing_ARC | Merge into S2-2503063 | |
| 20.2.1 | S2-2503641 | P-CR | Approval | 23.700-14: 23.700-14: New KI for FS_Sensing_ARC WT#4. | CATT | Rel-20 | FS_Sensing_ARC | Merge into S2-2502942 | |
| 20.2.1 | S2-2503775 | P-CR | Approval | 23.700-14: KI#4 Sensing data and the associated information collection and transport. | Nokia, Nokia Shanghai Bell | Rel-20 | FS_Sensing_ARC | Merge into S2-2502942 | |
| 20.2.1 | S2-2503869 | P-CR | Approval | 23.700-14: New KI#4 Sensing data and associated data collection and result calculation . | Xiaomi | Rel-20 | FS_Sensing_ARC | Merge into S2-2502942 | |
| 20.2.1 | - | - | - | Key issues related WT#5 | - | - | - | Docs:=9 | - |
| 20.2.1 | S2-2503423 | P-CR | Approval | 23.700-14: Key Issue 5: Sensing result exposure. | China Mobile | Rel-20 | FS_Sensing_ARC | Handle - use as baseline | |
| 20.2.1 | S2-2503642 | P-CR | Approval | 23.700-14: 23.700-14: New KI for FS_Sensing_ARC WT#5. | CATT | Rel-20 | FS_Sensing_ARC | Handle | |
| 20.2.1 | S2-2502936 | P-CR | Approval | 23.700-14: Key issue for WT#5: Sensing Result Exposure. | OPPO | Rel-20 | FS_Sensing_ARC | Merge into S2-2503423 | |
| 20.2.1 | S2-2503373 | P-CR | Approval | 23.700-14: Key issue for WT-5: Mechanisms for providing sensing information and result . | Samsung | Rel-20 | FS_Sensing_ARC | Merge into S2-2503423 | |
| 20.2.1 | S2-2503450 | P-CR | Approval | 23.700-14: Key issue#5, Sensing result exposure. | ZTE | Rel-20 | FS_Sensing_ARC | Merge into S2-2503423 | |
| 20.2.1 | S2-2503544 | P-CR | Approval | 23.700-14: New KI: sensing result exposure. | Lenovo | Rel-20 | FS_Sensing_ARC | Merge into S2-2503423 | |
| 20.2.1 | S2-2503626 | P-CR | Approval | 23.700-14: TR 23.700-14: New key issue for WT-5 Sensing result exposure. | ETRI | Rel-20 | FS_Sensing_ARC | Merge into S2-2503423 | |
| 20.2.1 | S2-2503776 | P-CR | Approval | 23.700-14: KI#5 sensing associated information and result exposure. | Nokia, Nokia Shanghai Bell | Rel-20 | FS_Sensing_ARC | Merge into S2-2503423 | |
| 20.2.1 | S2-2503870 | P-CR | Approval | 23.700-14: New KI#5 Sensing associated information and result exposure . | Xiaomi | Rel-20 | FS_Sensing_ARC | Merge into S2-2503423 | |
| 20.2.1 | - | - | - | Key issues related WT#6 | - | - | - | Docs:=5 | - |
| 20.2.1 | S2-2503146 | P-CR | Approval | 23.700-14: Key Issue for WT#6 Configuration parameter provisioning . | Sony | Rel-20 | FS_Sensing_ARC | Handle - use as baseline | |
| 20.2.1 | S2-2503090 | P-CR | Approval | 23.700-14: Key issue for WT#6: Configuration parameters/policy provisioning. | OPPO | Rel-20 | FS_Sensing_ARC | Merge into S2-2503146 | |
| 20.2.1 | S2-2503376 | P-CR | Approval | 23.700-14: Key issue for WT-6: Configuration parameters/policy provisioning for the support of ISAC services. | Samsung | Rel-20 | FS_Sensing_ARC | Merge into S2-2503146 | |
| 20.2.1 | S2-2503425 | P-CR | Approval | 23.700-14: Key Issue 6: Configuration parameters and policy provisioning. | China Mobile | Rel-20 | FS_Sensing_ARC | Merge into S2-2503146 | |
| 20.2.1 | S2-2503777 | P-CR | Approval | 23.700-14: KI#6 Configuration parameters policy provisioning. | Nokia, Nokia Shanghai Bell | Rel-20 | FS_Sensing_ARC | Merge into S2-2503146 | |
| 20.2.1 | - | - | - | Solutions | - | - | - | Docs:=5 | - |
| 20.2.1 | S2-2503065 | P-CR | Approval | 23.700-14: New solution: Enable the 5GS to support sensing services. | Vivo | Rel-20 | FS_Sensing_ARC | Not handle | |
| 20.2.1 | S2-2503800 | P-CR | Approval | 23.700-14: Call flow of the sensing study. | Huawei, HiSilicon | Rel-20 | FS_Sensing_ARC | Not handle | |
| 20.2.1 | S2-2503801 | P-CR | Approval | 23.700-14: KI#2, New Sol: Service authorisation and revocation. | Huawei, HiSilicon | Rel-20 | FS_Sensing_ARC | Not handle | |
| 20.2.1 | S2-2503802 | P-CR | Approval | 23.700-14: KI#3, New Sol: Discovery and selection of sensing entities. | Huawei, HiSilicon | Rel-20 | FS_Sensing_ARC | Not handle | |
| 20.2.1 | S2-2503803 | P-CR | Approval | 23.700-14: KI#5, New Sol: Providing Sensing result and other related information. | Huawei, HiSilicon | Rel-20 | FS_Sensing_ARC | Not handle | |
| 20.3.1 | - | - | - | Study on Core Network Enhanced Support for Artificial Intelligence (AI)/Machine Learning (ML)_Ph2 (FS_AIML_CN_Ph2) | - | - | Dario | Docs:=66 | - |
| 20.3.1 | - | - | - | General | - | - | - | Docs:=5 | - |
| 20.3.1 | S2-2502795 | LS In | Action | LS from TSG RAN: LS on AI/ML UE sided data collection | TSG RAN (RP-243316) | Revision of S2-2501372. Response drafted in S2-2503563 | |||
| 20.3.1 | S2-2503563 | LS OUT | Approval | [DRAFT] Reply LS on AI/ML UE sided data collection | CATT | Rel-20 | FS_AIML_CN_Ph2 | Postpone? Response to S2-2502795 | |
| 20.3.1 | S2-2503026 | P-CR | Approval | 23.700-04: TR Skeleton for FS_AIML_CN_Ph2 | Samsung, vivo | Rel-20 | FS_AIML_CN_Ph2 | Revised Skeleton TR. Revised to S2-2503789 | Revised |
| 20.3.1 | S2-2503789 | P-CR | Approval | 23.700-04: TR Skeleton for FS_AIML_CN_Ph2 | Samsung, vivo | Rel-20 | FS_AIML_CN_Ph2 | Handle Revision of S2-2503026. Skeleton TR | |
| 20.3.1 | S2-2503027 | P-CR | Approval | 23.700-04: Scope for FS_AIML_CN_Ph2. | Samsung (rapporteur), vivo (rapporteur) | Rel-20 | FS_AIML_CN_Ph2 | Handle | |
| 20.3.1 | - | - | - | Architectural Assumptions and Requirements | - | - | - | Docs:=10 | - |
| 20.3.1 | S2-2503291 | P-CR | Approval | 23.700-04: Architectural Assumptions and Requirements for FS_AIML_CN_Ph2. | Vivo(rapporteur), Samsung(rapporteur) | Rel-20 | FS_AIML_CN_Ph2 | Baseline | |
| 20.3.1 | S2-2502950 | P-CR | Approval | 23.700-04: PCR to TR 23.700-04: Requirements. | Nokia | Rel-20 | FS_AIML_CN_Ph2 | ||
| 20.3.1 | S2-2502997 | P-CR | Approval | 23.700-04: Architecture requirement and assumption. | ZTE | Rel-20 | FS_AIML_CN_Ph2 | ||
| 20.3.1 | S2-2503017 | P-CR | Approval | 23.700-04: Architectural Assumptions and Requirements. | LG Electronics | Rel-20 | FS_AIML_CN_Ph2 | Open | |
| 20.3.1 | S2-2503188 | P-CR | Approval | 23.700-04: Architectural Assumptions and Requirements for FS_AIML_CN_Ph2. | Rel-20 | FS_AIML_CN_Ph2 | |||
| 20.3.1 | S2-2503315 | P-CR | Approval | 23.700-04: Architectural Assumptions and Requirements for FS_AIML_CN_Ph2. | OPPO | Rel-20 | FS_AIML_CN_Ph2 | ||
| 20.3.1 | S2-2503400 | P-CR | Approval | 23.700-04: Architecture Assumption of TR 23.700-04. | China Mobile | Rel-20 | FS_AIML_CN_Ph2 | ||
| 20.3.1 | S2-2503478 | P-CR | Approval | 23.700-04: Architectural Assumptions and Requirements for WT#1. | ETRI | Rel-20 | FS_AIML_CN_Ph2 | ||
| 20.3.1 | S2-2503561 | P-CR | Approval | 23.700-04: Architectural Assumptions and Requirements for FS_AIML_CN_Ph2. | CATT | Rel-20 | FS_AIML_CN_Ph2 | ||
| 20.3.1 | S2-2503599 | P-CR | Approval | 23.700-04: Architectural Assumptions for FS_AIML_CN_Ph2. | Xiaomi | Rel-20 | FS_AIML_CN_Ph2 | ||
| 20.3.1 | - | - | - | WT#1 Key Issues | - | - | - | Docs:=17 | - |
| 20.3.1 | S2-2503290 | P-CR | Approval | 23.700-04: New Key Issue for transfer of data over UP for UE data collection. | Vivo(rapporteur), Samsung(rapporteur) | Rel-20 | FS_AIML_CN_Ph2 | Baseline | |
| 20.3.1 | S2-2502949 | P-CR | Approval | 23.700-04: New KI: 5GC Support for UE Data Collection over the User Plane . | Apple | Rel-20 | FS_AIML_CN_Ph2 | Open | |
| 20.3.1 | S2-2502940 | P-CR | Approval | 23.700-04: Key issue for WT#1: Standardized UE data collection based on UP connection between UE and 5GC. | OPPO | Rel-20 | FS_AIML_CN_Ph2 | ||
| 20.3.1 | S2-2502996 | P-CR | Approval | 23.700-04: Key issues for WT#1. | ZTE | Rel-20 | FS_AIML_CN_Ph2 | ||
| 20.3.1 | S2-2503102 | P-CR | Approval | 23.700-04: Key issue for WT#1: Data collection UE authorization and availability verification. | OPPO | Rel-20 | FS_AIML_CN_Ph2 | ||
| 20.3.1 | S2-2503103 | P-CR | Approval | 23.700-04: Key issue for WT#1: Discovery and selection of data collection UE. | OPPO | Rel-20 | FS_AIML_CN_Ph2 | ||
| 20.3.1 | S2-2503104 | P-CR | Approval | 23.700-04: Key issue for WT#1: Tiggering of UE data collection over UP. | OPPO | Rel-20 | FS_AIML_CN_Ph2 | ||
| 20.3.1 | S2-2503138 | P-CR | Approval | 23.700-04: New Key Issue: How to support UE data collection and transfer over User Plane for UE-side model training. | Huawei, HiSilicon | Rel-20 | FS_AIML_CN_Ph2 | Open | |
| 20.3.1 | S2-2503223 | P-CR | Approval | 23.700-04: WT#1: KI#X-UE data collection over UP. | Rel-20 | FS_AIML_CN_Ph2 | |||
| 20.3.1 | S2-2503241 | P-CR | Approval | 23.700-04: New Key Issue for WT#1: UE-side Data Collection over User Plane. | InterDigital Inc | Rel-20 | FS_AIML_CN_Ph2 | ||
| 20.3.1 | S2-2503254 | P-CR | Approval | 23.700-04: WT#1: KI#X for UE policy of UE data collection. | Rel-20 | FS_AIML_CN_Ph2 | |||
| 20.3.1 | S2-2503284 | P-CR | Approval | 23.700-04: Key issue for WT#1 UE data collection for AI/ML for NR air interface operation. | CATT | Rel-20 | FS_AIML_CN_Ph2 | ||
| 20.3.1 | S2-2503316 | P-CR | Approval | 23.700-04: Key issue for WT#1: Architecture enhancement to support UE data collection. | OPPO | Rel-20 | FS_AIML_CN_Ph2 | ||
| 20.3.1 | S2-2503317 | P-CR | Approval | 23.700-04: Key issue for WT#1: User consent and privacy for the standardized UE data collection. | OPPO | Rel-20 | FS_AIML_CN_Ph2 | ||
| 20.3.1 | S2-2503396 | P-CR | Approval | 23.700-04: FS_AIML_CN_Ph2 New Key Issue for Work Task #1. | China Mobile | Rel-20 | FS_AIML_CN_Ph2 | ||
| 20.3.1 | S2-2503479 | P-CR | Approval | 23.700-04: Key issue for WT#1. | ETRI | Rel-20 | FS_AIML_CN_Ph2 | ||
| 20.3.1 | S2-2503600 | P-CR | Approval | 23.700-04: Key issue for WT#1 UE data transfer via UP for UE-side model training for AIML NR air interface operation. | Xiaomi | Rel-20 | FS_AIML_CN_Ph2 | ||
| 20.3.1 | - | - | - | WT#1 Use Cases | - | - | - | Docs:=1 | - |
| 20.3.1 | S2-2503562 | P-CR | Approval | 23.700-04: Use case for WT#1 UE data collection. | CATT | Rel-20 | FS_AIML_CN_Ph2 | ||
| 20.3.1 | - | - | - | WT#1 Solutions (Handle following order below. One paper per company. Merged paper(s) get priority) | - | - | - | Docs:=16 | - |
| 20.3.1 | S2-2503016 | P-CR | Approval | 23.700-04: UP building for UE training data collection. | ZTE | Rel-20 | FS_AIML_CN_Ph2 | ||
| 20.3.1 | S2-2503023 | P-CR | Approval | 23.700-04: KI#1, New Sol#X: Generalized UE data collection over user plane . | LG Electronics | Rel-20 | FS_AIML_CN_Ph2 | ||
| 20.3.1 | S2-2503068 | P-CR | Approval | 23.700-04: Solution for WT 1 General Framework for data collection from the UE. | Lenovo | Rel-20 | FS_AIML_CN_Ph2 | ||
| 20.3.1 | S2-2503132 | P-CR | Approval | 23.700-04: KI#1: New Sol: CP-instructed UP-based UE data collection. | NTT DOCOMO | Rel-20 | FS_AIML_CN_Ph2 | ||
| 20.3.1 | S2-2503139 | P-CR | Approval | 23.700-04: New solution to support UE data collection and transfer for AI based positioning . | Huawei, HiSilicon | Rel-20 | FS_AIML_CN_Ph2 | ||
| 20.3.1 | S2-2503140 | P-CR | Approval | 23.700-04: New Solution for UE Data Collection and Transfer over User Plane. | Huawei, HiSilicon | Rel-20 | FS_AIML_CN_Ph2 | ||
| 20.3.1 | S2-2503189 | P-CR | Approval | 23.700-04: KI#1 solution using the generic architecture for collecting and exposing the collected UE data. | Ericsson | Rel-20 | FS_AIML_CN_Ph2 | ||
| 20.3.1 | S2-2503247 | P-CR | Approval | 23.700-04: New Solution for UE-side Data Collection and Transfer over UP. | InterDigital Inc | Rel-20 | FS_AIML_CN_Ph2 | ||
| 20.3.1 | S2-2503292 | P-CR | Approval | 23.700-04: KI#1: New Solution UE data collection via DCCF in CN over UP. | Vivo | Rel-20 | FS_AIML_CN_Ph2 | ||
| 20.3.1 | S2-2503318 | P-CR | Approval | 23.700-04: New Solution for KI#X: Establish the UP connection between UE and 5GC to support the standardized UE data collection. | OPPO | Rel-20 | FS_AIML_CN_Ph2 | ||
| 20.3.1 | S2-2503322 | P-CR | Approval | 23.700-04: UE policy enhancement to support data collection from UE. | ZTE | Rel-20 | FS_AIML_CN_Ph2 | ||
| 20.3.1 | S2-2503323 | P-CR | Approval | 23.700-04: NF selection and triggers for UE data collection. | ZTE | Rel-20 | FS_AIML_CN_Ph2 | ||
| 20.3.1 | S2-2503481 | P-CR | Approval | 23.700-04: New Solution to KI#1: Policy enhancement for UE-side data collection over UP. | ETRI | Rel-20 | FS_AIML_CN_Ph2 | ||
| 20.3.1 | S2-2503702 | P-CR | Approval | 23.700-04: New Solution for KI#1: UP based UE data collection solution for AI/ML NR air interface operation. | Qualcomm Incorporated | Rel-20 | FS_AIML_CN_Ph2 | ||
| 20.3.1 | S2-2503728 | P-CR | Approval | 23.700-04: KI#1 New Sol: Support of AIML data transfer via UP with AMF involvement. | Samsung | Rel-20 | FS_AIML_CN_Ph2 | ||
| 20.3.1 | S2-2503811 | P-CR | Approval | 23.700-04: New KI #Y, New Sol #X: Standardized transfer of data over UP for UE data collection as part of UE-side model Training. | MediaTek Inc. | Rel-20 | FS_AIML_CN_Ph2 | KI part to be merged into S2-2503290 | |
| 20.3.1 | - | - | - | WT#1 Others | - | - | - | Docs:=1 | - |
| 20.3.1 | S2-2503714 | P-CR | Approval | 23.700-04: Evaluation criteria for WT#1. | Samsung | Rel-20 | FS_AIML_CN_Ph2 | ||
| 20.3.1 | - | - | - | WT#2 Use Cases | - | - | - | Docs:=8 | - |
| 20.3.1 | S2-2502923 | DISCUSSION | Discussion | DP for R20 AIML WT#2 UC | SK Telecom | Rel-20 | |||
| 20.3.1 | S2-2502992 | P-CR | Approval | 23.700-04: WT#2 use case AI/ML-assisted UPF traffic pattern and behaviour analytics to support efficient performance of User Plane. | SK Telecom, China Mobile, China Telecom, Deutsche Telekom, KPN N.V., LG Uplus, Verizon | Rel-20 | FS_AIML_CN_Ph2 | Handle | |
| 20.3.1 | S2-2502993 | P-CR | Approval | 23.700-04: WT#2 use case: Analytics of detection and control of UPF traffic bursts to support efficient performance of User Plane. | SK Telecom, China Mobile, China Telecom, Deutsche Telekom, KPN N.V., LG Uplus, Verizon | Rel-20 | FS_AIML_CN_Ph2 | Handle | |
| 20.3.1 | S2-2503072 | P-CR | Approval | 23.700-04: New Use case for Work Task #2 (Whether and how to enhance the 5GC analytics to support efficient performance user plane). | Rakuten Mobile, NIST | Rel-20 | FS_AIML_CN_Ph2 | Merge into S2-2502993? | |
| 20.3.1 | S2-2503129 | P-CR | Approval | 23.700-04: New use case for WT2: user plane performance optimization with assistance of NWDAF. | Huawei, HiSilicon, CMCC | Rel-20 | FS_AIML_CN_Ph2 | Merge into S2-2502993? | |
| 20.3.1 | S2-2503280 | P-CR | Approval | 23.700-04: FS_AIML_CN_Ph2 Use case for WT#2. | ZTE | Rel-20 | FS_AIML_CN_Ph2 | Merge into S2-2502992? | |
| 20.3.1 | S2-2503795 | P-CR | Approval | 23.700-04: WT#2 use case: Prevention of unexpected service experience degradation. | Samsung | Rel-20 | FS_AIML_CN_Ph2 | Handle | |
| 20.3.1 | S2-2503796 | P-CR | Approval | 23.700-04: WT#2 use case: Enhancement of analytics for user plane traffic pattern and characteristic. | Samsung | Rel-20 | FS_AIML_CN_Ph2 | Handle | |
| 20.3.1 | - | - | - | WT#2 Key Issues (If use case discussion converges, then open one KI paper as baseline) | - | - | - | Docs:=8 | - |
| 20.3.1 | S2-2502994 | P-CR | Approval | 23.700-04: WT#2 Key Issue AI/ML-assisted UPF traffic pattern and behaviour analytics to support efficient performance of User Plane. | SK Telecom, China Mobile, China Telecom, Deutsche Telekom, KPN N.V., LG Uplus, Verizon | Rel-20 | FS_AIML_CN_Ph2 | ||
| 20.3.1 | S2-2502995 | P-CR | Approval | 23.700-04: WT#2 Key Issue: Analytics of detection and control of UPF traffic bursts to support efficient performance of User Plane. | SK Telecom, China Mobile, China Telecom, Deutsche Telekom, KPN N.V., LG Uplus, Verizon | Rel-20 | FS_AIML_CN_Ph2 | ||
| 20.3.1 | S2-2503133 | P-CR | Approval | 23.700-04: WT#2: Key Issue description for user plane analytics. | NTT DOCOMO | Rel-20 | FS_AIML_CN_Ph2 | ||
| 20.3.1 | S2-2503137 | P-CR | Approval | 23.700-04: New Key Issue: 5GC Analytics Enhancement to Support Efficient Performance of User Plane. | Huawei, HiSilicon | Rel-20 | FS_AIML_CN_Ph2 | ||
| 20.3.1 | S2-2503192 | P-CR | Approval | 23.700-04: KI#2 description. | Ericsson | Rel-20 | FS_AIML_CN_Ph2 | ||
| 20.3.1 | S2-2503281 | P-CR | Approval | 23.700-04: FS_AIML_CN_Ph2 Key issue for WT#2. | ZTE | Rel-20 | FS_AIML_CN_Ph2 | ||
| 20.3.1 | S2-2503285 | P-CR | Approval | 23.700-04: Key issue for WT#2 Network analytics enhancement for user plane performance improvement. | CATT | Rel-20 | FS_AIML_CN_Ph2 | ||
| 20.3.1 | S2-2503398 | P-CR | Approval | 23.700-04: FS_AIML_CN_Ph2 New Key Issue for Work Task #2. | China Mobile, SK Telecom | Rel-20 | FS_AIML_CN_Ph2 | ||
| 20.4.1 | - | - | - | Study on Energy Efficiency and Energy Saving Phase2 (FS_EnergySys_Ph2) | - | - | Wanqiang | Docs:=51 | - |
| 20.4.1 | - | - | - | TR Skeleton and TR Scope | - | - | - | Docs:=2 | - |
| 20.4.1 | S2-2503120 | P-CR | Approval | 23.700-67: TR 23.700-67 Skeleton for FS_EnergySys_Ph2 | China Telecom, Lenovo (Rapporteur) | Rel-20 | FS_EnergySys_Ph2 | Handle Skeleton TR | |
| 20.4.1 | S2-2503123 | P-CR | Approval | 23.700-67: FS_EnergySys_Ph2 TR23.700-67 Scope. | China Telecom, Lenovo (Rapporteur) | Rel-20 | FS_EnergySys_Ph2 | Handle | |
| 20.4.1 | - | - | - | Architectural Assumptions and Requirement | - | - | - | Docs:=4 | - |
| 20.4.1 | S2-2502956 | P-CR | Approval | 23.700-67: Architecture assumptions. | Vivo | Rel-20 | FS_EnergySys_Ph2 | Merge into S2-2503485? | |
| 20.4.1 | S2-2503451 | P-CR | Approval | 23.700-67: Proposal on the architecture assumptions and requirement. | ZTE | Rel-20 | FS_EnergySys_Ph2 | Merge into S2-2503485? | |
| 20.4.1 | S2-2503485 | P-CR | Approval | 23.700-67: Architectural Assumptions and Principles for Energy Efficiency and Energy Saving. | China Mobile, Lenovo, China Telecom | Rel-20 | FS_EnergySys_Ph2 | Handle, as baseline | |
| 20.4.1 | S2-2503566 | P-CR | Approval | 23.700-67: Architectural Assumptions and Requirements for FS_EnergySys_Ph2. | CATT | Rel-20 | FS_EnergySys_Ph2 | Merge into S2-2503485? | |
| 20.4.1 | - | - | - | KI Description for WT#1 (enhance the collection, determination and exposure) | - | - | - | Docs:=10 | - |
| 20.4.1 | S2-2502957 | P-CR | Approval | 23.700-67: New key issue for WT#1: Enhancements to the energy related information collection, determination, and exposure. | Vivo | Rel-20 | FS_EnergySys_Ph2 | Merge into S2-2503567? | |
| 20.4.1 | S2-2503073 | P-CR | Approval | 23.700-67: Key issue for WT#1: Whether and how to enhance the collection, determination and exposure of energy related information in the 5GS. | Rakuten Mobile | Rel-20 | FS_EnergySys_Ph2 | Merge into S2-2503567? | |
| 20.4.1 | S2-2503158 | P-CR | Approval | 23.700-67: Key issue for WT#1: Energy related information collection, determination, and exposure. | Samsung | Rel-20 | FS_EnergySys_Ph2 | Merge into S2-2503567? | |
| 20.4.1 | S2-2503383 | P-CR | Approval | 23.700-67: Key Issue for WT#1: Enhancements in collection, determination and exposure of energy related information. | NEC | Rel-20 | FS_EnergySys_Ph2 | Merge into S2-2503567? | |
| 20.4.1 | S2-2503452 | P-CR | Approval | 23.700-67: Adding new KI on the collection, determination and exposure of energy related information. | ZTE | Rel-20 | FS_EnergySys_Ph2 | Merge into S2-2503567? | |
| 20.4.1 | S2-2503482 | P-CR | Approval | 23.700-67: New Key Issue: Enhancement for energy related information collection, determination, and exposure. | China Mobile | Rel-20 | FS_EnergySys_Ph2 | Merge into S2-2503567? | |
| 20.4.1 | S2-2503567 | P-CR | Approval | 23.700-67: Key issue for WT#1 - Enhancements on energy related information collection and exposure. | CATT | Rel-20 | FS_EnergySys_Ph2 | Handle, as baseline | |
| 20.4.1 | S2-2503603 | P-CR | Approval | 23.700-67: New Key issue for WT#1 On Enhancements of Energy-related information exposure. | Nokia | Rel-20 | FS_EnergySys_Ph2 | Merge into S2-2503567? | |
| 20.4.1 | S2-2503717 | P-CR | Approval | 23.700-67: New KI: Enhancing collection, determination and exposure of energy related information. | NTT DOCOMO | Rel-20 | FS_EnergySys_Ph2 | Merge into S2-2503567? | |
| 20.4.1 | S2-2503879 | P-CR | Approval | 23.700-67: KI#1 - Enhancements on energy related information collection, determination and exposure. | Lenovo | Rel-20 | FS_EnergySys_Ph2 | Merge into S2-2503567? | |
| 20.4.1 | - | - | - | KI Description for WT#2 (service adjustments for the UE) | - | - | - | Docs:=8 | - |
| 20.4.1 | S2-2502958 | P-CR | Approval | 23.700-67: New key issue for WT#2: Service adjustments for network energy saving. | Vivo | Rel-20 | FS_EnergySys_Ph2 | Merge into S2-2503287? | |
| 20.4.1 | S2-2503159 | P-CR | Approval | 23.700-67: Key issue for WT#2: Support of service adjustments for the UE. | Samsung | Rel-20 | FS_EnergySys_Ph2 | Merge into S2-2503287? | |
| 20.4.1 | S2-2503287 | P-CR | Approval | 23.700-67: Key issue for WT#2: Support of service adjustments for the UE. | MediaTek Inc. | Rel-20 | FS_EnergySys_Ph2 | Handle, as baseline | |
| 20.4.1 | S2-2503453 | P-CR | Approval | 23.700-67: Adding new KI on supporting service adjustments for the UE to enable energy saving. | ZTE | Rel-20 | FS_EnergySys_Ph2 | Merge into S2-2503287? | |
| 20.4.1 | S2-2503483 | P-CR | Approval | 23.700-67: New Key Issue: Network service adjustment with considering the energy consumption information. | China Mobile | Rel-20 | FS_EnergySys_Ph2 | Merge into S2-2503287? | |
| 20.4.1 | S2-2503568 | P-CR | Approval | 23.700-67: Key issue for WT#2 - Service adjustments for the UE to enable energy saving. | CATT | Rel-20 | FS_EnergySys_Ph2 | Merge into S2-2503287? | |
| 20.4.1 | S2-2503608 | P-CR | Approval | 23.700-67: New Key issue for WT#2 - Service adjustments for the UE to enable energy saving. | Nokia | Rel-20 | FS_EnergySys_Ph2 | Merge into S2-2503287? | |
| 20.4.1 | S2-2503727 | P-CR | Approval | 23.700-67: New KI: Service adjustment for energy saving. | NTT DOCOMO | Rel-20 | FS_EnergySys_Ph2 | Merge into S2-2503287? | |
| 20.4.1 | - | - | - | KI Description for WT#3 (NF (re)selection and/or UP path adjustment) | - | - | - | Docs:=8 | - |
| 20.4.1 | S2-2503160 | P-CR | Approval | 23.700-67: Key issue for WT#3: Enhancements based on energy related information. | Samsung | Rel-20 | FS_EnergySys_Ph2 | Merge into S2-2503484? | |
| 20.4.1 | S2-2503386 | P-CR | Approval | 23.700-67: Key issue for WT3: NF (re)selection and/or UP path adjustment based on energy related information. | NEC | Rel-20 | FS_EnergySys_Ph2 | Merge into S2-2503484? | |
| 20.4.1 | S2-2503418 | P-CR | Approval | 23.700-67: New KI for WT#3: NF (re)selection and UP path adjustment based on energy related information. | Vivo | Rel-20 | FS_EnergySys_Ph2 | Merge into S2-2503484? | |
| 20.4.1 | S2-2503454 | P-CR | Approval | 23.700-67: Adding new KI on support of NF (re)selection and/or UP path adjustment based on energy related information. | ZTE | Rel-20 | FS_EnergySys_Ph2 | Merge into S2-2503484? | |
| 20.4.1 | S2-2503484 | P-CR | Approval | 23.700-67: New Key Issue: NF (re)selection and/or UP path adjustment based on energy related information. | China Mobile, Lenovo, China Telecom | Rel-20 | FS_EnergySys_Ph2 | Handle, as baseline | |
| 20.4.1 | S2-2503569 | P-CR | Approval | 23.700-67: Key issue for WT#3 - NF (re)selection and UP path adjustment for energy saving. | CATT | Rel-20 | FS_EnergySys_Ph2 | Merge into S2-2503484? | |
| 20.4.1 | S2-2503610 | P-CR | Approval | 23.700-67: New Key issue for WT#3 - On the support NF (re-)selection and/or UP path adjustment based on energy related information . | Nokia | Rel-20 | FS_EnergySys_Ph2 | Merge into S2-2503484? | |
| 20.4.1 | S2-2503730 | P-CR | Approval | 23.700-67: New KI: Enhancing 5GC energy efficiency . | NTT DOCOMO | Rel-20 | FS_EnergySys_Ph2 | Merge into S2-2503484? | |
| 20.4.1 | - | - | - | Solutions for WT#1 (enhance the collection, determination and exposure) | - | - | - | Docs:=3 | - |
| 20.4.1 | S2-2503612 | P-CR | Approval | 23.700-67: KI#1:new solution: P-CR on exposure of UE scoring data. | Nokia | Rel-20 | FS_EnergySys_Ph2 | Handle | |
| 20.4.1 | S2-2503634 | P-CR | Approval | 23.700-67: WT#1: EC improvement for Passive and dynamic EC. | Huawei, HiSilicon | Rel-20 | FS_EnergySys_Ph2 | Handle 2nd round if time permits | |
| 20.4.1 | S2-2503635 | P-CR | Approval | 23.700-67: WT#1: Renewable energy per UE, PDU session and SDF. | Huawei, HiSilicon | Rel-20 | FS_EnergySys_Ph2 | Handle 2nd round if time permits | |
| 20.4.1 | - | - | - | Solutions for WT#2 (service adjustments for the UE) | - | - | - | Docs:=11 | - |
| 20.4.1 | S2-2502952 | P-CR | Approval | 23.700-67: Energy Optimization Trigger for PCF based Policy Control. | Ericsson | Rel-20 | FS_EnergySys_Ph2 | Handle | |
| 20.4.1 | S2-2503144 | P-CR | Approval | 23.700-67: KI#2: New Sol: Energy-aware data transfer policy negotiation. | NTT DOCOMO | Rel-20 | FS_EnergySys_Ph2 | Handle | |
| 20.4.1 | S2-2503288 | P-CR | Approval | 23.700-67: Solution for WT#2: Support of QoS adjustments. | MediaTek Inc. | Rel-20 | FS_EnergySys_Ph2 | Handle | |
| 20.4.1 | S2-2503294 | P-CR | Approval | 23.700-67: Solution for WT#2: Support of policy adjustments. | MediaTek Inc. | Rel-20 | FS_EnergySys_Ph2 | ||
| 20.4.1 | S2-2503392 | P-CR | Approval | 23.700-67: KI#2, new sol: Service adjustments for network energy saving based on AF request and energy information. | Vivo | Rel-20 | FS_EnergySys_Ph2 | Handle | |
| 20.4.1 | S2-2503570 | P-CR | Approval | 23.700-67: KI#2 new solution for policy control based on interactions with the EIF. | CATT | Rel-20 | FS_EnergySys_Ph2 | Handle | |
| 20.4.1 | S2-2503713 | P-CR | Approval | 23.700-67: New Solution to WT#2: Enabling dynamic QoS handling for energy efficiency lterby use of Energy Saving QoS Profiles . | Qualcomm Incorporated | Rel-20 | FS_EnergySys_Ph2 | Handle | |
| 20.4.1 | S2-2503788 | P-CR | Approval | 23.700-67: KI#2: New Solution on SM policy control based on EIF notification. | Samsung | Rel-20 | FS_EnergySys_Ph2 | Handle | |
| 20.4.1 | S2-2503790 | P-CR | Approval | 23.700-67: KI#2: New Solution on AM policy control based on EIF notification. | Samsung | Rel-20 | FS_EnergySys_Ph2 | ||
| 20.4.1 | S2-2503832 | P-CR | Approval | 23.700-67: KI#2: New Solution on policy control based on Energy Consumption Information for Network Slice. | Samsung | Rel-20 | FS_EnergySys_Ph2 | ||
| 20.4.1 | S2-2503787 | P-CR | Approval | 23.700-67: Energy Consumption information assisted Policy Update. | China Mobile | Rel-20 | FS_EnergySys_Ph2 | Handle LATE DOC. | |
| 20.4.1 | - | - | - | Solutions for WT#3 (NF (re)selection and/or UP path adjustment) | - | - | - | Docs:=5 | - |
| 20.4.1 | S2-2503313 | P-CR | Approval | 23.700-67: Solution for WT#3: Support of UP path adjustments for the UE. | MediaTek Inc. | Rel-20 | FS_EnergySys_Ph2 | ||
| 20.4.1 | S2-2503419 | P-CR | Approval | 23.700-67: KI #3, New Sol: AMF (re-)selection based on energy related information. | Vivo | Rel-20 | FS_EnergySys_Ph2 | ||
| 20.4.1 | S2-2503571 | P-CR | Approval | 23.700-67: KI#3 new solution for UP path adjustment based on energy related information. | CATT | Rel-20 | FS_EnergySys_Ph2 | ||
| 20.4.1 | S2-2503636 | P-CR | Approval | 23.700-67: WT#3: NF selection profile and UPF selection. | Huawei, HiSilicon | Rel-20 | FS_EnergySys_Ph2 | Handle | |
| 20.4.1 | S2-2503856 | P-CR | Approval | 23.700-67: KI#3: New solution on NF selection mechanism based on energy related information. | Samsung | Rel-20 | FS_EnergySys_Ph2 | Handle 2nd round if time permits | |
| 30 | - | - | - | Project Planning and Management | - | - | Andy | Docs:=0 | - |
| 30.1 | - | - | - | New and Revised Study/Work Items | - | - | Andy | Docs:=0 | - |
| 30.2 | - | - | - | Submissions for TEI20 | - | - | _Not_on_Agenda | Docs:=0 | - |
| 30.3 | - | - | - | TR and TS Cover sheets | - | - | Andy | Docs:=0 | - |
| 30.4 | - | - | - | SI/WI Status Reports | - | - | Andy | Docs:=0 | - |
| 30.5 | - | - | - | Review of the Work Plan and planning future meetings | - | - | Andy | Docs:=5 | - |
| 30.5 | S2-2503112 | WORK PLAN | Endorsement | TU budget for Rel-20 | SA WG2 Chair | ||||
| 30.5 | S2-2503113 | WORK PLAN | Endorsement | Work Planning slides | SA WG2 Chair | ||||
| 30.5 | S2-2503114 | WORK PLAN | Endorsement | Work planning spreadsheet | SA WG2 Chair | ||||
| 30.5 | S2-2503116 | OTHER | Endorsement | Way of working guidance proposal | SA WG2 Chair | ||||
| 30.5 | S2-2503117 | OTHER | Endorsement | Guidance for SA WG2 Rel-20 preparation in Q2 2025. | SA WG2 Chair | ||||
| 30.6 | - | - | - | Proposals for Rel-20 5G Advanced Study/Work items | - | - | Andy | Docs:=37 | - |
| 30.6 | - | - | - | General | - | - | - | Docs:=1 | - |
| 30.6 | S2-2503118 | OTHER | Information | TSG SA Guidance to SA WG2 on 5GA studies | SA WG2 Chair | ||||
| 30.6 | - | - | - | Indirect Network Sharing phase2 | - | - | - | Docs:=6 | - |
| 30.6 | S2-2503060 | SID NEW | Approval | New SID on Study on Indirect Network Sharing phase2. | China Unicom (Moderator) | Rel-20 | Bad Acronym, Consider FS_NetShare_Ph2_ARC | ||
| 30.6 | S2-2503066 | SID NEW | Approval | New SID on Study on Indirect Network Sharing phase2. | China Unicom | Rel-20 | Bad Acronym, Consider FS_NetShare_Ph2_ARC. Alternative to S2-2503060? | ||
| 30.6 | S2-2503715 | SID NEW | Approval | New SID on Study on Indirect Network Sharing phase2. | NEC | Rel-20 | Bad Acronym, Consider FS_NetShare_Ph2_ARC. Alternative to S2-2503060? | ||
| 30.6 | S2-2503830 | SID NEW | Approval | New SID on Study on Indirect Network Sharing phase2. | CableLabs | Rel-20 | Bad Acronym, Consider FS_NetShare_Ph2_ARC. Alternative to S2-2503060? | ||
| 30.6 | S2-2503059 | DISCUSSION | Decision | Moderator summary and proposal on: Moderated discussion for Indirect Network Sharing phase2. | China Unicom (Moderator) | Rel-20 | |||
| 30.6 | S2-2503069 | DISCUSSION | Discussion | Indirect Network Sharing phase 2 | China Unicom | Rel-20 | |||
| 30.6 | - | - | - | XRM Ph3 | - | - | - | Docs:=6 | - |
| 30.6 | S2-2503826 | SID NEW | Approval | Study on Extended Reality and Media Service (XRM) Phase 3. | Nokia | Rel-20 | Consider Acronym: FS_XRM_Ph3_ARC. Alternative to S2-2503592? | ||
| 30.6 | S2-2503592 | SID NEW | Approval | New SID on 5GS XRM Ph3. | CATT | Bad Acronym, Consider FS_XRM_Ph3_ARC | |||
| 30.6 | S2-2503214 | DISCUSSION | Agreement | Extension for XRM on-path signalling Connect-UDP Forwarded Mode. . | Ericsson | ||||
| 30.6 | S2-2503829 | DISCUSSION | Discussion | Discussion on Rel-20 FS_XRM Ph3. | Huawei, HiSilicon, China Mobile, SK Telecom, | Rel-20 | Revised to S2-2503893 | Revised | |
| 30.6 | S2-2503893 | DISCUSSION | Discussion | Discussion on Rel-20 FS_XRM Ph3. | Huawei, HiSilicon, China Mobile, SK Telecom | Rel-20 | Revision of S2-2503829. LATE DOC. | ||
| 30.6 | S2-2503827 | REPORT | Information | NWM Discussion Report on R20 5GA XRM_Ph3 | Nokia | Rel-20 | |||
| 30.6 | - | - | - | NG_RTC continuation | - | - | - | Docs:=2 | - |
| 30.6 | S2-2503767 | SID NEW | Discussion | New SID: Study on system architecture for next generation real time communication services phase 3. | China Mobile | Rel-20 | Consider Acronym: FS_NG_RTC_Ph3_ARC | ||
| 30.6 | S2-2503768 | REPORT | Information | Moderator report: Moderated discussion on NG_RTC continuation | China Mobile | Rel-20 | |||
| 30.6 | - | - | - | Mission Critical Services, Multimedia Priority Services | - | - | - | Docs:=5 | - |
| 30.6 | S2-2503243 | REPORT | Discussion | NWM summary report on Mission Critical Services, Multimedia Priority Services | Peraton Labs (moderator) | Rel-20 | |||
| 30.6 | S2-2503244 | SID NEW | Approval | New SID on MPS Enhancements for IoT. | Peraton Labs (moderator) | Rel-20 | Consider Acronym FS_MPS_IOT_ARC | ||
| 30.6 | S2-2503245 | SID NEW | Approval | New SID on MPS Enhancements for IoT. | Peraton Labs | Rel-20 | Consider Acronym FS_MPS_IOT_ARC. Alternative to S2-2503244? | ||
| 30.6 | S2-2503246 | SID NEW | Approval | New SID on System Enhancement for Proximity-based Services in 5GS - Phase 4. | Peraton Labs (moderator) | Rel-20 | Consider Acronym FS_5G_ProSe_Ph4_ARC. Alternative to S2-2502897? | ||
| 30.6 | S2-2502897 | SID NEW | Approval | New SID on System Enhancement for Proximity-based Services in 5GS - Phase 4. | KPN N.V. | Rel-20 | Revision of (Noted) S2-2500543. Consider Acronym: FS_5G_ProSe_Ph4_ARC | ||
| 30.6 | - | - | - | Ambient IoT Phase 2 | - | - | - | Docs:=12 | - |
| 30.6 | S2-2502888 | DISCUSSION | Discussion | Discussion on Ambient IoT Phase 2. | KPN N.V. | Rel-20 | |||
| 30.6 | S2-2502946 | DISCUSSION | Discussion | Ambient IoT scope for Rel-20. | Qualcomm | Rel-20 | |||
| 30.6 | S2-2503014 | DISCUSSION | Discussion | Discussion on Rel-20 Ambient IoT Scope. | CATT | Rel-20 | |||
| 30.6 | S2-2503029 | DISCUSSION | Discussion | LGE View on Rel-20 Ambient IoT study | LG Electronics | Rel-20 | |||
| 30.6 | S2-2503051 | DISCUSSION | Discussion | Proposed scope of AmbientIoT-ARC Phase 2. | OPPO | ||||
| 30.6 | S2-2503107 | DISCUSSION | Discussion | Discussion on Rel-20 AIoT. | NEC | Rel-20 | |||
| 30.6 | S2-2503164 | DISCUSSION | Decision | Discussion on Rel-20 Ambient IoT study. | Ofinno | Rel-20 | |||
| 30.6 | S2-2503480 | DISCUSSION | Discussion | Discussion on Release 20 Ambient IoT SID scope. | NTT DOCOMO | Rel-20 | |||
| 30.6 | S2-2503503 | DISCUSSION | Discussion | Discussion on R20 Ambient IoT SID scope | Nokia Korea | ||||
| 30.6 | S2-2503534 | DISCUSSION | Information | Overall View on 5G-A Rel-20 AIoT | China Mobile Com. Corporation | Rel-20 | |||
| 30.6 | S2-2503671 | SID NEW | Approval | New SID: Study on Architecture support of Ambient power-enabled Internet of Things Phase2. | Vivo | Rel-20 | Consider Acronym: FS_AmbientIoT_Ph2_ARC | ||
| 30.6 | S2-2503844 | DISCUSSION | Discussion | Rel-20 SA WG2 Ambient IoT Proposal | Huawei, HiSilicon | Rel-20 | |||
| 30.6 | - | - | - | IMS resiliency | - | - | - | Docs:=3 | - |
| 30.6 | S2-2503105 | DISCUSSION | Discussion | Discussion on IMS resiliency study. | KDDI, SK Telecom | Rel-20 | |||
| 30.6 | S2-2503797 | SID NEW | Approval | Resilient Notification. | EchoStar, Boost Mobile | Rel-20 | Moved to 30.6 Space in Acronym. Consider Acronym FS_5GSAT_Ph4_RN_ARC? | ||
| 30.6 | S2-2502984 | DISCUSSION | Agreement | Discussion for WT-3 Resilient Notification. | EchoStar, Boost Mobile | Rel-20 | Moved to AI 30.6 | ||
| 30.6 | - | - | - | Other | - | - | - | Docs:=2 | - |
| 30.6 | S2-2503557 | DISCUSSION | Information | Discussion on enhancement to IMS network capability exposure. | Huawei, HiSilicon | Rel-20 | |||
| 30.6 | S2-2503661 | DISCUSSION | Information | Discussion paper for information on Loop prevention and Multi Domain Support in the study on Industrial Networks Enhancements. | Nokia | Rel-20 | |||
| 30.7 | - | - | - | 6G Study Item discussion papers | - | - | Andy | Docs:=42 | - |
| 30.7 | S2-2502869 | DISCUSSION | Discussion | NTT DOCOMO's views on 6G study | NTT DOCOMO | Rel-20 | |||
| 30.7 | S2-2502873 | DISCUSSION | Discussion | AT&T views on 6G study in SA WG2 | AT&T Services, Inc. | Rel-20 | |||
| 30.7 | S2-2502878 | DISCUSSION | Discussion | Verizons views on 6G study in SA WG2 | Verizon Spain | ||||
| 30.7 | S2-2502884 | DISCUSSION | Information | China Mobile views about 6G Architecture | China Mobile | Rel-20 | |||
| 30.7 | S2-2502887 | DISCUSSION | Discussion | KPN N.V. views on 6G Architecture | KPN N.V. | Rel-20 | |||
| 30.7 | S2-2502896 | DISCUSSION | Information | Intel views on 6G study | Intel | ||||
| 30.7 | S2-2502935 | DISCUSSION | Approval | Some fundamental principles on 6G Architecture. | China Mobile, China Telecom, China Unicom, CATT, OPPO, Vivo, Xiaomi, ZTE | Rel-20 | |||
| 30.7 | S2-2502941 | DISCUSSION | Discussion | Lenovo views on 6G study | Lenovo | Rel-20 | |||
| 30.7 | S2-2502945 | DISCUSSION | Discussion | Proposed scope for 6G study item | Qualcomm | Rel-20 | |||
| 30.7 | S2-2502959 | DISCUSSION | Discussion | Boost Mobile views on 6G study | Boost Mobile Network | Rel-20 | |||
| 30.7 | S2-2502989 | DISCUSSION | Discussion | SK Telecom views on 6G study | SK Telecom | ||||
| 30.7 | S2-2502991 | DISCUSSION | Discussion | Focus Areas and Priorities in the 6G Study | ETRI, SK Telecom, KT, LG Uplus | Rel-20 | |||
| 30.7 | S2-2503058 | DISCUSSION | Discussion | China Unicom view on SA WG2 R20 6G SID | China Unicom | Rel-20 | |||
| 30.7 | S2-2503067 | DISCUSSION | Discussion | Rakuten_Mobile_6G_Priorities_Presentation | Rakuten Mobile, Inc | Rel-20 | |||
| 30.7 | S2-2503162 | DISCUSSION | Approval | Huawei view on 6G Core SID scope | Huawei, HiSilicon | Rel-20 | |||
| 30.7 | S2-2503186 | DISCUSSION | Discussion | Google's views on 6G study | Rel-20 | ||||
| 30.7 | S2-2503225 | DISCUSSION | Discussion | Futurewei Views on 6G Study | Futurewei Technologies | Rel-20 | |||
| 30.7 | S2-2503256 | DISCUSSION | Discussion | 6G System Scope, Technical areas | Nokia | Rel-20 | |||
| 30.7 | S2-2503260 | DISCUSSION | Discussion | OPPO View on 6G SID WTs | OPPO | ||||
| 30.7 | S2-2503270 | DISCUSSION | Discussion | Ericsson view on 6G SID Scope Content | Ericsson | ||||
| 30.7 | S2-2503286 | DISCUSSION | Discussion | China Telecom's View on First 6G Service and Architecture | China Telecom | Rel-20 | |||
| 30.7 | S2-2503293 | DISCUSSION | Information | Vivo view on 6G system architecture | vivo | ||||
| 30.7 | S2-2503375 | DISCUSSION | Discussion | Areas of NEC interests in 6G architecture | NEC Corporation | Rel-20 | |||
| 30.7 | S2-2503377 | DISCUSSION | Decision | Discussion for 6G Study on Interworking and Migration | Samsung | ||||
| 30.7 | S2-2503412 | DISCUSSION | Discussion | Apple's View on 6G SID Scope | Apple | Rel-20 | |||
| 30.7 | S2-2503541 | DISCUSSION | Discussion | UE and network Coordinated Computing | OPPO, China Unicom, LG Electronics, CATT, CMCC, vivo, SKT, China Telecom | ||||
| 30.7 | S2-2503594 | DISCUSSION | Information | Vivo view on 6G AIML | vivo | ||||
| 30.7 | S2-2503602 | DISCUSSION | Presentation | Samsung view on 6G Architecture | Samsung | Rel-20 | |||
| 30.7 | S2-2503611 | DISCUSSION | Agreement | Topics for SA WG2 6G Study | Vodafone | Rel-20 | |||
| 30.7 | S2-2503613 | DISCUSSION | Information | ZTE view on 6G scope for Architecture | ZTE | ||||
| 30.7 | S2-2503669 | DISCUSSION | Discussion | Discussion for 6G Study on Service Plane | Samsung | Rel-20 | |||
| 30.7 | S2-2503675 | DISCUSSION | Discussion | CATT views on SA WG2 6G SID | CATT | Rel-20 | |||
| 30.7 | S2-2503716 | DISCUSSION | Information | Discussion for 6G study on Native AI | Samsung | Rel-20 | |||
| 30.7 | S2-2503733 | DISCUSSION | Discussion | Discussion for 6G Study on Network Resilience | Samsung | Rel-20 | |||
| 30.7 | S2-2503749 | DISCUSSION | Discussion | Discussion for 6G Study on compact and simple network architecture | Samsung Electronics France SA | Rel-20 | |||
| 30.7 | S2-2503810 | DISCUSSION | Discussion | Thoughts on SA WG2 6G Study Scope | MediaTek Inc. | Rel-20 | |||
| 30.7 | S2-2503823 | DISCUSSION | Discussion | Interdigital's views on SA WG2 6G Study item | InterDigital Canada | Rel-20 | |||
| 30.7 | S2-2503828 | DISCUSSION | Presentation | MSO View on 6G SID Scope | CableLabs, Charter Communications, Comcast | Rel-20 | |||
| 30.7 | S2-2503859 | DISCUSSION | Discussion | Charter Communications - 6G System Architecture and Services Priorities | Charter Communications, Inc | Rel-20 | |||
| 30.7 | S2-2503871 | DISCUSSION | Information | Xiaomi's view on the key areas of 6GC study | Xiaomi | Rel-20 | |||
| 30.7 | S2-2503875 | DISCUSSION | Discussion | Views on Priority Topics for 6G System Architecture SID | Deutsche Telekom AG | Rel-20 | |||
| 30.7 | S2-2503892 | DISCUSSION | Discussion | LGE view on 6G study | LG Electronics | Rel-20 | |||
| 30.9 | - | - | - | Exception sheets for work items | - | - | Andy | Docs:=0 | - |
| 31 | - | - | - | Close of meeting | - | - | Andy | Docs:=0 | - |
| 99 | - | - | - | Withdrawn and Reserved documents | - | - | Withdrawn | Docs:=31 | - |
| 99 | S2-2503081 | LS OUT | Approval | [DRAFT] Reply LS on OSAppID usage by AppToken use case | Nokia | Rel-19 | TEI19 | Revision of (Postponed) S2-2502775. Response to S2-2502797. WITHDRAWN | Withdrawn |
| 99 | S2-2502852 | OTHER | Information | Reserved for incoming LS | MCC | WITHDRAWN | Withdrawn | ||
| 99 | S2-2502851 | OTHER | Information | Reserved for incoming LS | MCC | WITHDRAWN | Withdrawn | ||
| 99 | S2-2502850 | OTHER | Information | Reserved for incoming LS | MCC | WITHDRAWN | Withdrawn | ||
| 99 | S2-2503808 | CR | Approval | 23.501 CR6263 (Rel-19, 'F'): Collection of energy consumption information for new PDU session | Samsung | Rel-19 | EnergySys | WITHDRAWN | Withdrawn |
| 99 | S2-2503812 | CR | Approval | 23.304 CR0552 (Rel-19, 'F'): End UE RSC Bounded Routing | Nokia, Nokia Shanghai Bell | Rel-19 | 5G_ProSe_Ph3 | WITHDRAWN | Withdrawn |
| 99 | S2-2502954 | CR | Approval | 23.502 CR5389 (Rel-19, 'C'): Handling of AF Specific UE IDs | Ericsson | Rel-19 | EDGEAPP | WITHDRAWN | Withdrawn |
| 99 | S2-2503033 | CR | Approval | 23.502 CR5399 (Rel-19, 'F'): 23.502 Clarifications to Session Management aspects for handling multiple Non-3GPP Device Identifiers | Samsung | Rel-19 | UIA_ARC | WITHDRAWN | Withdrawn |
| 99 | S2-2503035 | CR | Approval | 23.502 CR5400 (Rel-19, 'F'): 23.501 Clarification to usage of Operator configurable UPF capabilties in roaming scenarios | Samsung | Rel-19 | UPEAS_Ph2 | WITHDRAWN | Withdrawn |
| 99 | S2-2502925 | DISCUSSION | Discussion | Discussion on AF specific UE ID generation | Samsung | WITHDRAWN | Withdrawn | ||
| 99 | S2-2503364 | CR | Approval | 23.401 CR3912 (Rel-19, 'F'): Procedure updates for S&F operation | LG Electronics | Rel-19 | FS_5GSAT_Ph3_ARCH | WITHDRAWN | Withdrawn |
| 99 | S2-2503296 | LS OUT | Approval | [DRAFT] Reply LS on multiplexing capability negotiation | Qualcomm Incorporated | Rel-19 | NG_RTC_Ph2 | Response to S2-2502807. WITHDRAWN | Withdrawn |
| 99 | S2-2503511 | CR | Approval | 23.503 CR1542 (Rel-18, 'F'): Clarifications for multi-modal services | Huawei, HiSilicon | Rel-18 | XRM | Revision of (Postponed at S2#165) S2-2410784. WITHDRAWN | Withdrawn |
| 99 | S2-2503512 | CR | Approval | 23.503 CR1543 (Rel-19, 'A'): Clarifications for multi-modal services | Huawei, HiSilicon | Rel-19 | XRM | Revision of (Withdrawn at S2#165) S2-2410329. WITHDRAWN | Withdrawn |
| 99 | S2-2502967 | CR | Approval | 23.256 CR0195 (Rel-19, 'F'): Update to Nnef_UAVFlightAssistance_Notify service operation | Ericsson | Rel-19 | UAS_Ph3 | WITHDRAWN | Withdrawn |
| 99 | S2-2503428 | P-CR | Approval | 23.369: PCR to TS 23.369 on aggregation aspects. | NTT DOCOMO | Rel-19 | eCSFB, AmbientIoT-ARC | WITHDRAWN | Withdrawn |
| 99 | S2-2503474 | DISCUSSION | Discussion | Discussion on Release 20 Ambient IoT SID scope | NTT DOCOMO INC.. | Rel-20 | WITHDRAWN | Withdrawn | |
| 99 | S2-2503358 | CR | Approval | 23.501 CR6213 (Rel-19, 'F'): UDM functional description update for CAG information provisioning | SAMSUNG | Rel-19 | 5G_Femto | WITHDRAWN | Withdrawn |
| 99 | S2-2502998 | P-CR | Approval | 23.700-04: KI#1 Solution_UE policy enhancement to support data collection from UE | ZTE | Rel-20 | FS_AIML_CN_Ph2 | WITHDRAWN | Withdrawn |
| 99 | S2-2502999 | P-CR | Approval | 23.700-04: KI#1 Solution_NF selection and triggers for UE data collection | ZTE | Rel-20 | FS_AIML_CN_Ph2 | WITHDRAWN | Withdrawn |
| 99 | S2-2503083 | CR | Approval | 23.228 CR1612 (Rel-17, 'B'): Service restoration by IMS when the UE is unresponsive but reachable | Jio | Rel-17 | FS_eIMS5G | WITHDRAWN | Withdrawn |
| 99 | S2-2503082 | CR | Approval | 23.502 CR5410 (Rel-16, 'C'): AMF reselection via NAS reroute based on Routing Indicator | Jio Platforms Ltd (JPL) | Rel-16 | 5GS_Ph1 | WITHDRAWN | Withdrawn |
| 99 | S2-2503086 | CR | Approval | 23.228 CR1613 (Rel-16, 'B'): Service restoration by IMS when the UE is unresponsive but reachable | Jio Platforms Ltd (JPL) | Rel-16 | FS_eIMS5G | WITHDRAWN | Withdrawn |
| 99 | S2-2503087 | CR | Approval | 23.228 CR1614 (Rel-16, 'B'): Service restoration by IMS when the UE is unresponsive but reachable | Jio Platforms Ltd (JPL) | Rel-16 | eIMS5G_SBA | WITHDRAWN | Withdrawn |
| 99 | S2-2502833 | LS In | Action | LS from TSG RAN: LS on AI/ML UE sided data collection | TSG RAN (RP-243316) | NR_AIML_air | Already added in S2-2502795. WITHDRAWN | Withdrawn | |
| 99 | S2-2502834 | LS In | Action | LS from SA WG3: Reply LS on security aspects of Ambient IoT | SA WG3 (S3-251055) | FS_AmbientIoT | Already added in S2-2502799. WITHDRAWN | Withdrawn | |
| 99 | S2-2502837 | LS In | Action | LS from SA WG4: Reply LS on Clarification of DC Binding Information | SA WG4 (S4-242111) | FS_NG_RTC_Ph2 | Already added in S2-2502796. WITHDRAWN | Withdrawn | |
| 99 | S2-2502908 | CR | Approval | 23.501 CR6166 (Rel-19, 'F'): Corrections on UPF Event Exposure | Ericsson | Rel-19 | UPEAS_Ph2 | WITHDRAWN | Withdrawn |
| 99 | S2-2502990 | P-CR | Discussion | 23.700-04: FS_AIML_CN_Ph2 WT#2 UC | SK Telecom | Rel-20 | FS_AIML_CN_Ph2 | WITHDRAWN | Withdrawn |
| 99 | S2-2503359 | CR | Approval | 23.502 CR5436 (Rel-19, 'F'): Removal of event subscription for CAG information provisioning | SAMSUNG | Rel-19 | 5G_Femto | Revision of S2-2503358. WITHDRAWN | Withdrawn |