| TDoc | Title | Source |
|---|---|---|
| S2-2502789 | SA2#168 meeting Agenda | SA WG2 Chair |
| S2-2502790 | SA WG2#168 meeting schedule | SA WG2 Chair |
| S2-2503115 | Plan for the meeting | SA WG2 Chair |
| S2-2504482 | SA WG2#168 meeting schedule | SA WG2 Chair |
| TDoc | Title | Source |
|---|---|---|
| S2-2502791 | Draft Report of SA WG2 meeting #167 | SA WG2 Secretary |
| TDoc | Title | Source |
|---|---|---|
| S2-2502797 | LS from GSMA TSGNS: OSAppID usage by AppToken use case | GSMA TSGNS |
| S2-2502798 | LS from CEN TC 278 WG 15: LS on Next Generation eCall | CEN TC 278 WG 15 |
| S2-2502801 | LS from RAN WG2: Reply LS on Time Synchronization for MBS | RAN WG2 |
| S2-2502809 | LS from CT WG3: LS reply on FS_IMS_RES outcome and future work plan | CT WG3 |
| S2-2502823 | LS from RAN WG2: Inclusion of NTN intended service area in the Service Announcement | RAN WG2 |
| S2-2502838 | LS from SA WG4: LS on Advanced Media Delivery | SA WG4 |
| S2-2502845 | LS from SA WG6: LS on Generation of AF specific UE ID | SA WG6 |
| S2-2502846 | LS from TSG SA: Reply LS on support of multiple access technologies based on the IMS service type | TSG SA |
| S2-2502848 | LS from ETSI ISG NFV: Publication of ETSI NFV group report on architectural support for NFV evolution | ETSI ISG NFV |
| S2-2502849 | LS from CT WG4: LS on Optimizations to UPF event subscriptions and reporting | CT WG4 |
| S2-2502870 | Generation of AF specific UE Identifier . | Apple |
| S2-2502871 | [DRAFT] Reply LS on generation of AF specific UE ID | Apple |
| S2-2502898 | [DRAFT] Reply LS on Inclusion of NTN intended service area in the Service Announcement | Nokia |
| S2-2502924 | [DRAFT] Reply LS on generation of AF specific UE ID | Samsung |
| S2-2502926 | [DRAFT] Reply LS on OSAppID usage by AppToken use case | Telefonica Germany GmbH |
| S2-2502927 | Discussion paper on GSMA TSGNS AppToken use case. | Telefonica S.A., Verizon, Deutsche Telekom, KDDI, Ericsson, Nokia |
| S2-2502951 | [DRAFT] LS Reply on Generation of AF specific UE ID | Ericsson |
| S2-2502953 | Handling of AF Specific UE IDs | Ericsson, AT&T, Nokia, Deutsche Telekom, KPN, NTT DOCOMO |
| S2-2503024 | AF specific UE ID generation | Samsung |
| S2-2503025 | AF specific UE ID generation | Samsung |
| S2-2503091 | [DRAFT] LS on Generation of AF specific UE ID | Nokia |
| S2-2503092 | Generation of AF specific UE ID | Nokia, AT&T, KPN, NTT DOCOMO, Deutsche Telekom |
| S2-2503095 | [DRAFT] LS on Optimizations to UPF event subscriptions and reporting | Nokia |
| S2-2503424 | [DRAFT] Reply LS to 'OSAppID usage by AppToken use case' | Apple |
| S2-2503617 | [DRAFT] Reply LS for OSAppID usage by AppToken use case | ZTE |
| S2-2503620 | [DRAFT] LS Response on Generation of AF specific UE ID | ZTE |
| S2-2503739 | [DRAFT] LS Reply on Optimizations to UPF event subscriptions and reporting | Ericsson |
| S2-2503747 | [DRAFT] Reply LS on OSAppID usage by AppToken use case | Samsung |
| S2-2503769 | [DRAFT] Reply LS on Optimizations to UPF event subscriptions and reporting | China Mobile |
| S2-2503855 | [DRAFT] Reply LS on OSAppID usage by AppToken use case | Google Korea LLC |
| S2-2503877 | 6G specification format modernization: towards Automation-Native. | Nokia |
| S2-2504094 | [DRAFT] Reply LS on OSAppID usage by AppToken use case | Telefonica Germany GmbH |
| S2-2504095 | [DRAFT] Reply LS on generation of AF specific UE ID | Apple |
| S2-2504096 | Handling of AF Specific UE IDs | Ericsson, AT&T, Nokia, Deutsche Telekom, KPN, NTT DOCOMO, Apple, Samsung |
| S2-2504097 | Generation of AF specific UE ID | Nokia, AT&T, KPN, NTT DOCOMO, Deutsche Telekom |
| S2-2504098 | [DRAFT] LS on Optimizations to UPF event subscriptions and reporting | Nokia |
| S2-2504393 | [DRAFT] Reply LS on OSAppID usage by AppToken use case | Telefonica Germany GmbH |
| S2-2504394 | Handling of AF Specific UE IDs | Ericsson, AT&T, Nokia, Deutsche Telekom, KPN, NTT DOCOMO, Apple, Samsung |
| S2-2504395 | Generation of AF specific UE ID | Nokia, AT&T, KPN, NTT DOCOMO, Deutsche Telekom, Ericsson, Samsung |
| S2-2504396 | Reply LS on generation of AF specific UE ID | SA WG2 |
| S2-2504397 | [DRAFT] LS on Optimizations to UPF event subscriptions and reporting | Nokia |
| S2-2504468 | Reply LS on OSAppID usage by AppToken use case | SA WG2 |
| S2-2504469 | LS on Optimizations to UPF event subscriptions and reporting | SA WG2 |
| TDoc | Title | Source |
|---|---|---|
| S2-2503084 | AMF reselection via NAS reroute based on Routing Indicator | Jio Platforms Ltd (JPL) |
| S2-2503401 | Registration handling during the mobility from non-3GPP access to 3GPP access | Huawei, Hisilicon |
| S2-2503402 | Registration handling during the mobility from non-3GPP access to 3GPP access | Huawei, Hisilicon |
| S2-2503729 | Radio capability assignment in case of equivalent PLMNs. | NEC |
| S2-2504363 | Registration handling during the mobility from non-3GPP access to 3GPP access | Huawei, Hisilicom |
| S2-2504364 | Registration handling during the mobility from non-3GPP access to 3GPP access | Huawei, Hisilicom |
| S2-2504410 | Registration handling during the mobility from non-3GPP access to 3GPP access | Huawei, Hisilicom |
| S2-2504411 | Registration handling during the mobility from non-3GPP access to 3GPP access | Huawei, Hisilicom |
| S2-2504472 | Registration handling during the mobility from non-3GPP access to 3GPP access | Huawei, Hisilicom |
| S2-2504473 | Registration handling during the mobility from non-3GPP access to 3GPP access | Huawei, Hisilicom |
| TDoc | Title | Source |
|---|---|---|
| S2-2502983 | Synchronizing status of QoS Flow(s) between H-SMF or anchor SMF and UE | Ericsson |
| S2-2504365 | Synchronizing status of QoS Flow(s) between H-SMF or anchor SMF and UE | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| S2-2503085 | Rel-16 CR TS 23.502 Type Allocation Code (TAC) based AMF local configuration for establishment of UE policy association. | Jio Platform Limited (JPL) |
| S2-2503506 | Simplification of clause 6.2.1.2 | Huawei, HiSilicon |
| TDoc | Title | Source |
|---|---|---|
| S2-2503719 | Discussion on the epoch issue for 5G Residence time calculation | ZTE |
| S2-2503720 | Epoch for 5G Residence time calculation | ZTE |
| S2-2503721 | Epoch for 5G Residence time calculation | ZTE |
| S2-2503722 | Epoch for 5G Residence time calculation | ZTE |
| S2-2503723 | Epoch for 5G Residence time calculation | ZTE |
| S2-2503746 | Ensuring the same epoch for timestamping for gPTP | Qualcomm |
| S2-2503862 | 5GS common time reference traceable to UTC | Nokia |
| S2-2503863 | 5GS common time reference traceable to UTC | Nokia |
| S2-2504366 | 5GS common time reference traceable to UTC | Nokia |
| S2-2504367 | 5GS common time reference traceable to UTC | Nokia |
| TDoc | Title | Source |
|---|---|---|
| S2-2503088 | Service restoration by IMS when the UE is unresponsive but reachable | Jio Platforms Ltd (JPL) |
| TDoc | Title | Source |
|---|---|---|
| S2-2503350 | Correlate the Slice Load to an AOI when location is provided | Verizon, Oracle, CATT |
| S2-2503361 | Attribute Level Change | Verizon, Oracle, CATT |
| S2-2504368 | Correlate the Slice Load to an AOI when location is provided | Verizon, Oracle, CATT, Ericsson |
| S2-2504369 | Attribute Level Change | Verizon, Oracle, CATT |
| TDoc | Title | Source |
|---|---|---|
| S2-2502803 | LS from CT WG1: LS on stage 1 requirements for the support for PWS over satellite NGRAN in Rel-17 | CT WG1 |
| TDoc | Title | Source |
|---|---|---|
| S2-2502813 | LS from CT WG4: LS on New port number for LCS-UPP | CT WG4 |
| TDoc | Title | Source |
|---|---|---|
| S2-2502961 | Solving UE shall have maximum one LCS-UPP | Ericsson |
| S2-2502962 | Supporting multiple LCS-UPP connections per UE | Ericsson |
| S2-2503171 | Discussion on single LCS-UPP connection maintenance. | OPPO |
| S2-2503172 | User plane positioning update for LCS-UPP context synchronization | OPPO |
| S2-2503173 | Update on single LCS-UPP connection maintenance | OPPO |
| S2-2503492 | Clarification and correction on modification of UP connection between UE and LMF | Huawei, HiSilicon |
| S2-2503493 | Clarification and correction on modification of UP connection between UE and LMF | Huawei, HiSilicon |
| S2-2503647 | Solve the failure of the user plane connection establishment | CATT |
| S2-2503648 | Solve the failure of the user plane connection establishment | CATT |
| S2-2503724 | Correction on the Modification of User Plane Connection between UE and LMF | ZTE |
| S2-2503725 | Correction on the Modification of User Plane Connection between UE and LMF | ZTE |
| S2-2503726 | Clarification on the maximum one LCS-UPP connection restriction | ZTE |
| S2-2504042 | Solving UE shall have maximum one LCS-UPP | Ericsson, ZTE |
| S2-2504043 | Clarification and correction on modification of UP connection between UE and LMF | Huawei, HiSilicon |
| S2-2504044 | Supporting multiple LCS-UPP connections per UE | Ericsson |
| S2-2504045 | Solve the failure of the user plane connection establishment | CATT |
| S2-2504046 | Solve the failure of the user plane connection establishment | CATT |
| S2-2504086 | Clarification and correction on modification of UP connection between UE and LMF | Huawei, HiSilicon |
| S2-2504087 | Solving UE shall have maximum one LCS-UPP | Ericsson, ZTE, CATT |
| S2-2504088 | Supporting multiple LCS-UPP connections per UE | Ericsson, Huawei |
| S2-2504089 | Solve the failure of the user plane connection establishment | CATT, Ericsson |
| S2-2504090 | Solve the failure of the user plane connection establishment | CATT, Ericsson |
| S2-2504349 | Solve the failure of the user plane connection establishment | CATT, Ericsson |
| S2-2504350 | Solve the failure of the user plane connection establishment | CATT, Ericsson |
| TDoc | Title | Source |
|---|---|---|
| S2-2502874 | Update network slice replacement PCRT | Oracle, Verizon |
| S2-2502875 | Update network slice replacement PCRT | Oracle, Verizon |
| S2-2502889 | Clarification on the removal of S-NSSAI from the Configured NSSAI | Nokia, ZTE |
| S2-2502890 | Clarification on the removal of S-NSSAI from the Configured NSSAI | Nokia, ZTE |
| S2-2503298 | Configured NSSAI exchange between AMFs for Network Slice Replacement | LG Electronics |
| S2-2503299 | Configured NSSAI exchange between AMFs for Network Slice Replacement | LG Electronics |
| S2-2503300 | Update on UE Context in AMF to support Network Slice Replacement | LG Electronics |
| S2-2503301 | Update on UE Context in AMF to support Network Slice Replacement | LG Electronics |
| S2-2503546 | Discussion on always-on PDU sessions for network slices subject to area restrictions. | NTT Docomo, Nokia |
| S2-2503548 | Handling of always-on PDU sessions for network slices subject to area control | NTT DOCOMO, Nokia |
| S2-2503550 | Handling of always-on PDU sessions for network slices subject to area restrictions | NTT DOCOMO, Nokia |
| S2-2503551 | Handling of always-on PDU sessions for network slices subject to area restrictions | NTT DOCOMO, Nokia. |
| S2-2503558 | Handling of always-on PDU sessions for network slices subject to area control | Nokia |
| S2-2503559 | Handling of always-on PDU sessions for network slices subject to area control- option B | Nokia, NTT DOCOMO |
| S2-2503573 | Handling of always-on PDU sessions for network slices subject to area control- option B | Nokia, NTT DOCOMO |
| S2-2503615 | Clarification on always-on PDU Session | ZTE |
| S2-2503616 | Clarification on always-on PDU Session | ZTE |
| S2-2503664 | Clarification on Configured NSSAI for temporary slice | Samsung |
| S2-2503666 | Clarification on Configured NSSAI for temporary slice | Samsung |
| S2-2503821 | Discussion on always-on PDU sessions for network slices subject to area restrictions. | NTT Docomo, Nokia |
| S2-2504141 | Update network slice replacement PCRT | Oracle, Verizon |
| S2-2504142 | Update network slice replacement PCRT | Oracle, Verizon |
| S2-2504143 | Configured NSSAI exchange between AMFs for Network Slice Replacement | LG Electronics |
| S2-2504144 | Clarification on always-on PDU Session | ZTE |
| S2-2504145 | Clarification on always-on PDU Session | ZTE |
| S2-2504401 | Clarification on the removal of S-NSSAI from the Configured NSSAI | Nokia, ZTE, Verizon, Qualcomm |
| TDoc | Title | Source |
|---|---|---|
| S2-2502891 | Clarifications on ECN marking for L4S | Apple |
| S2-2502892 | Clarifications on ECN marking for L4S | Apple |
| S2-2502893 | Dynamic detection of L4S traffic and enabling of ECN marking for L4S. | Apple, Ericsson |
| S2-2503324 | Fix PDU Set based Handling description | Samsung |
| S2-2503325 | Fix PDU Set based Handling description | Samsung |
| S2-2503326 | N2 SM information to NG-RAN | Samsung |
| S2-2503327 | N2 SM information to NG-RAN | Samsung |
| S2-2503507 | Clarifications for multi-modal services | Huawei, HiSilicon, Nokia |
| S2-2503508 | Clarifications for multi-modal services | Huawei, HiSilicon, Nokia |
| S2-2503509 | Clarifications for multi-modal services | Huawei, HiSilicon, Nokia, ZTE |
| S2-2503510 | Clarifications for multi-modal services | Huawei, HiSilicon, Nokia |
| S2-2503513 | Clarifications and corrections for ECN marking for L4S and congestion monitoring | Huawei, HiSilicon |
| S2-2503514 | Clarifications and corrections for ECN marking for L4S and congestion monitoring | Huawei, HiSilicon |
| S2-2503515 | Clarifications and corrections for ECN marking for L4S and congestion monitoring | Huawei, HiSilicon |
| S2-2503516 | Clarifications and corrections for ECN marking for L4S and congestion monitoring | Huawei, HiSilicon |
| S2-2503585 | Clarifications for multi-modal services | Huawei, HiSilicon |
| S2-2503587 | Clarifications for multi-modal services | Huawei, HiSilicon |
| S2-2503591 | Activation of QoS monitoring for the GBR service data flow | CATT |
| S2-2503894 | Clarifications on ECN marking for L4S | Apple |
| S2-2503895 | Clarifications on ECN marking for L4S | Apple |
| S2-2503896 | Clarifications for multi-modal services | Huawei, HiSilicon, Nokia |
| S2-2503897 | Clarifications for multi-modal services | Huawei, HiSilicon, Nokia |
| S2-2503898 | Clarifications for multi-modal services | Huawei, HiSilicon, Nokia, ZTE |
| S2-2503899 | Clarifications for multi-modal services | Huawei, HiSilicon, Nokia |
| S2-2503900 | Clarifications for multi-modal services | Huawei, HiSilicon |
| S2-2503901 | Clarifications for multi-modal services | Huawei, HiSilicon |
| S2-2503902 | Fix PDU Set based Handling description | Samsung |
| S2-2503903 | Fix PDU Set based Handling description | Samsung |
| S2-2503904 | N2 SM information to NG-RAN | Samsung |
| S2-2503905 | N2 SM information to NG-RAN | Samsung |
| S2-2503906 | Activation of QoS monitoring for the GBR service data flow | CATT |
| S2-2503992 | Clarifications on ECN marking for L4S | Apple |
| S2-2503993 | Clarifications and corrections for ECN marking for L4S and congestion monitoring | Huawei, HiSilicon |
| S2-2504153 | Clarifications and corrections for ECN marking for L4S and congestion monitoring | Huawei, HiSilicon |
| S2-2504154 | Clarifications and corrections for ECN marking for L4S and congestion monitoring | Huawei, HiSilicon |
| S2-2504155 | Clarifications and corrections for ECN marking for L4S and congestion monitoring | Huawei, HiSilicon |
| S2-2504156 | Clarifications for multi-modal services | Huawei, HiSilicon, Nokia |
| S2-2504157 | Fix PDU Set based Handling description | Samsung |
| S2-2504158 | Fix PDU Set based Handling description | Samsung |
| S2-2504159 | N2 SM information to NG-RAN | Samsung |
| S2-2504160 | N2 SM information to NG-RAN | Samsung |
| S2-2504161 | Activation of QoS monitoring for the GBR service data flow | CATT, Huawei |
| S2-2504189 | N2 SM information to NG-RAN | Samsung |
| S2-2504190 | N2 SM information to NG-RAN | Samsung |
| S2-2504226 | Clarifications and corrections for ECN marking for L4S and congestion monitoring | Huawei, HiSilicon |
| S2-2504227 | Clarifications for multi-modal services | Huawei, HiSilicon, Nokia |
| S2-2504228 | Clarifications for multi-modal services | Huawei, HiSilicon, Nokia, ZTE |
| S2-2504249 | Clarifications and corrections for ECN marking for L4S and congestion monitoring | Huawei, HiSilicon |
| S2-2504250 | Clarifications for multi-modal services | Huawei, HiSilicon, Nokia |
| S2-2504251 | Clarifications for multi-modal services | Huawei, HiSilicon, Nokia |
| S2-2504480 | Clarifications for multi-modal services | Huawei, HiSilicon, Nokia |
| TDoc | Title | Source |
|---|---|---|
| S2-2502804 | LS from CT WG1: Reply LS on request for IMS Data Channel related clarifications | CT WG1 |
| S2-2503759 | Adding event for session establishment cancellation | China Mobile |
| S2-2503760 | Adding event for session establishment cancellation | China Mobile |
| S2-2503761 | Correction on bootstrap DC removal | China Mobile |
| S2-2503762 | Correction on bootstrap DC removal | China Mobile |
| S2-2503978 | Adding event for session establishment cancellation | China Mobile |
| S2-2503979 | Adding event for session establishment cancellation | China Mobile |
| S2-2503980 | Correction on bootstrap DC removal | China Mobile, Nokia |
| S2-2503981 | Correction on bootstrap DC removal | China Mobile, Nokia |
| S2-2504204 | Correction on bootstrap DC removal | China Mobile, Nokia, Huawei, Ericsson |
| S2-2504205 | Correction on bootstrap DC removal | China Mobile, Nokia, Huawei, Ericsson |
| TDoc | Title | Source |
|---|---|---|
| S2-2503890 | Alignment with ATSSS Capability IE | Apple |
| S2-2503891 | Alignment with ATSSS Capability IE | Apple |
| S2-2504134 | Alignment with ATSSS Capability IE | Apple |
| S2-2504386 | Alignment with ATSSS Capability IE | Apple |
| TDoc | Title | Source |
|---|---|---|
| S2-2503852 | SMF event on simultaneous connectivity failure | Nokia |
| S2-2503919 | SMF event on simultaneous connectivity failure | Nokia |
| S2-2504173 | SMF event on simultaneous connectivity failure | Nokia |
| TDoc | Title | Source |
|---|---|---|
| S2-2502853 | Clarifications on the definition of accuracy | ZTE |
| S2-2502854 | Clarifications on the definition of accuracy | ZTE |
| S2-2502855 | Clarifications on the file address related to ADRF | ZTE |
| S2-2502856 | Clarifications on the file address related to ADRF | ZTE |
| S2-2503539 | Correction on analytics feedback information | Vivo |
| S2-2503540 | Correction on analytics feedback information | Vivo |
| S2-2504125 | Clarifications on the definition of accuracy | ZTE |
| S2-2504126 | Clarifications on the file address related to ADRF | ZTE |
| S2-2504127 | Correction on analytics feedback information | Vivo |
| TDoc | Title | Source |
|---|---|---|
| S2-2502876 | Correction for BSF invocation in URSP Rule Enforcement Information procedure | Oracle, Verizon |
| S2-2502877 | Correction for BSF invocation in URSP Rule Enforcement Information procedure | Oracle, Verizon |
| S2-2503778 | Correction for BSF invocation in URSP Rule Enforcement Information procedure | Oracle, Verizon, Ericsson |
| S2-2503779 | Correction for BSF invocation in URSP Rule Enforcement Information procedure | Oracle, Verizon, Ericsson |
| S2-2504114 | Correction for BSF invocation in URSP Rule Enforcement Information procedure | Oracle, Verizon, Ericsson |
| S2-2504115 | Correction for BSF invocation in URSP Rule Enforcement Information procedure | Oracle, Verizon, Ericsson |
| TDoc | Title | Source |
|---|---|---|
| S2-2502822 | LS from RAN WG2: Geofencing in ETWS for NR and NB-IoT NTN | RAN WG2 |
| S2-2502824 | LS from RAN WG2: LS to CT1 and CT4 on maximum warning message size | RAN WG2 |
| S2-2502825 | LS from RAN WG3: Reply LS on UE Location Information for NB-IoT NTN | RAN WG3 |
| S2-2502829 | LS from RAN WG3: Reply LS on OAM requirements to support regenerative payload transport links | RAN WG3 |
| S2-2502842 | LS from SA WG5: Reply LS to LS on reply to LS on OAM requirements to support regenerative payload | SA WG5 |
| S2-2502879 | Refinement of UE behavior and S&F wait timer handling | ZTE |
| S2-2502880 | Clarify the conditions for MME to provide S&F parameters in NAS procedure | ZTE |
| S2-2502881 | Enhancement of S&F Monitoring List update | ZTE |
| S2-2502882 | Align the condition for UE to indicate the S&F capability | ZTE |
| S2-2502883 | Update to the GUTI Reallocation procedure | ZTE |
| S2-2502917 | Update to Initial Call setup and functional support for UE-Satellite-UE communication in IMS | Ericsson |
| S2-2502918 | Update to Mobility procedures for UE-Satellite-UE communication | Ericsson |
| S2-2502928 | Update of target satellite ID notification | ZTE |
| S2-2502929 | [DRAFT] Reply LS on OAM requirements to support regenerative payload | ZTE Corporation |
| S2-2502930 | [DRAFT] Reply LS on OAM requirements to support regenerative payload | ZTE Corporation |
| S2-2503070 | TAU and Service Request procedure correction for S&F | Nokia |
| S2-2503071 | Clarification on S&F Wait Timer | Nokia |
| S2-2503224 | On TAI configuration in AMF via OAM. | Qualcomm Incorporated, Vodafone |
| S2-2503231 | [DRAFT] Reply LS on OAM requirements to support regenerative payload transport links | Qualcomm, Vodafone |
| S2-2503265 | Clarifications to UE S&F capability and procedures that can include S&F Monitoring list | Ericsson |
| S2-2503266 | Clarify S1-U not supported by split MME | Ericsson |
| S2-2503267 | Clarify PDN connection handling for split MME | Ericsson |
| S2-2503268 | Tracking Area handling for regenerative satellite access. | Ericsson |
| S2-2503275 | Clarification on usage of S&F Wait Timer in UE | China Telecom |
| S2-2503276 | Clarification on Attach reject | China Telecom |
| S2-2503363 | Transitioning between operation in S&F mode and normal mode | LG Electronics |
| S2-2503414 | Updates to S&F mode transition | Vivo |
| S2-2503415 | Procedure updates for S&F | Vivo |
| S2-2503416 | TAIs configured by OAM | Vivo |
| S2-2503417 | TAIs configured by OAM | Vivo |
| S2-2503467 | Update on change of BP/ULCL and UP notification procedures for UE-Satellite-UE communication | ETRI |
| S2-2503494 | No Necessity to define UE in S&F mode | MediaTek Inc., Qualcomm Incorporated |
| S2-2503495 | Avoid congestion caused by S&F timer | MediaTek Inc. |
| S2-2503533 | MT data transport in CP CIoT EPS Optimisation update for S&F operation | Xiaomi |
| S2-2503583 | Update on early media handling in UE-Satellite-UE scenario | Vivo |
| S2-2503652 | Clarification on UP path event subscription for UE-satellite-UE communication | Huawei, HiSilicon |
| S2-2503653 | Clarification and correction on UP path event report for UE-satellite-UE communication | Huawei, HiSilicon |
| S2-2503654 | Update Support of Attach with PDN connection for split MME architecture | Huawei, HiSilicon |
| S2-2503655 | Clarification on S&F timer in NAS Accept and NAS Reject messages | Huawei, HiSilicon |
| S2-2503656 | Corrections for S&F Support and operation | Huawei, HiSilicon |
| S2-2503662 | Avoid congestion caused by S&F timer | MediaTek Inc. |
| S2-2503706 | [DRAFT] Reply LS on OAM requirements to support regenerative payload transport links | CATT |
| S2-2503707 | Configuration of TAI list for regenerative satellite payload | CATT |
| S2-2503708 | Clarification on the deletion of the previous S&F Monitoring List | CATT |
| S2-2503709 | Clarification on UE-SAT-UE communication when serving satellite changes | CATT |
| S2-2503710 | Clarification on 5QI for satellite access | CATT |
| S2-2503711 | Clarification on QCI for satellite access | CATT |
| S2-2503712 | Clarification on UE-Satellite-UE communication procedures | CATT |
| S2-2503750 | Procedure updates for S&F operation | LG Electronics |
| S2-2503753 | Clarify the S&F event is sent from SCEF to SCS/AS | Ericsson |
| S2-2503764 | Correction on UE-sat-UE communication procedures | China Mobile |
| S2-2503880 | Handling S&F wait timer. | Samsung |
| S2-2503881 | Handling S&F not allowed. | Samsung |
| S2-2503886 | Editorial fixes and handling when S&F is not enabled by UE. | Samsung |
| S2-2503887 | Align the terms. | Samsung |
| S2-2503911 | TAIs configured by OAM | vivo |
| S2-2503912 | TAIs configured by OAM | vivo |
| S2-2503913 | Clarification on 5QI for satellite access | CATT |
| S2-2503914 | Clarification on QCI for satellite access | CATT |
| S2-2503915 | Clarification on S&F Wait Timer | Nokia |
| S2-2503916 | Editorial fixes | Samsung |
| S2-2503917 | Corrections for S&F Support and operation | Huawei, HiSilicon |
| S2-2503918 | Update Support of Attach with PDN connection for split MME architecture | Huawei, HiSilicon |
| S2-2504182 | Corrections for S&F Support and operation | Huawei, HiSilicon, Nokia |
| S2-2504183 | Editorial fixes | Samsung |
| S2-2504184 | Update Support of Attach with PDN connection for split MME architecture | Huawei, HiSilicon |
| S2-2504244 | Corrections for S&F Support and operation | Huawei, HiSilicon, Nokia, Ericsson |
| TDoc | Title | Source |
|---|---|---|
| S2-2502796 | LS from SA WG4: Reply LS on Clarification of DC Binding Information | SA WG4 |
| S2-2502807 | LS from CT WG1: LS on multiplexing capability negotiation | CT WG1 |
| S2-2502836 | LS from SA WG3: LS on Privacy and security aspects regarding DC management by the network | SA WG3 |
| S2-2502847 | LS from GSMA TSG IMSDCAS: LS to SA WG2 About Requirements Concerning Automatic Resume Where You have Left Off | GSMA TSG IMSDCAS |
| S2-2502909 | KI#1: Corrections to IMS Subscribe/Notify Framework Architecture | Ericsson |
| S2-2502910 | KI#8: Updates to services and operations | Ericsson |
| S2-2502911 | KI#8: Corrections to Avatar procedures | Ericsson |
| S2-2502912 | KI#3: Update to DC interworking with MTSI UE | Ericsson |
| S2-2502913 | KI#2: Generalizing Information Retrieval | Ericsson |
| S2-2502914 | KI#2: Corrections to DC AS initiated Session Update to add BDC to an existing IMS session | Ericsson |
| S2-2502915 | KI#2: Corrections to DC AS initiated Standalone ADC Session Creation | Ericsson |
| S2-2502916 | KI#2: Corrections to DC AS initiated IMS Session Update Procedures | Ericsson |
| S2-2502919 | KI#1: Immediate Reporting | Ericsson |
| S2-2502920 | KI#1: Event Status Retrieval Procedure | Ericsson |
| S2-2502921 | KI#1: Event Status Retrieval Procedure | Ericsson |
| S2-2503097 | NG_RTC_Ph2 KI#1: Subscribe/Notify Procedure correction | Nokia |
| S2-2503098 | KI#2: Correction of procedures in clause AG | Nokia |
| S2-2503099 | Clarification of the NG_RTC_Ph2 KI#4 procedure description | Nokia |
| S2-2503100 | Aligning MF selection criteria with 23.228 | Nokia |
| S2-2503167 | KI#3: Updates on the ADC Interworking via DC AS procedure | Samsung |
| S2-2503169 | KI#3: Updates on interworking with MTSI UE procedures | Samsung |
| S2-2503170 | [DRAFT] Reply to LS on Automatic Resumption in IMS data channel | Samsung |
| S2-2503178 | Clarification on DC AS URL for downloading Avatar ID List | Samsung |
| S2-2503180 | Clarification on Nhss_ImsUECM_AsInfoGet | Samsung |
| S2-2503289 | MDC2 endpoint indication for Avatar Represenation downloading | Qualcomm Incorporated, Ericsson |
| S2-2503295 | Correction on DC multiplexing capability negotiation | Qualcomm Incorporated |
| S2-2503308 | Indication of DC initiator for DC create/update/termination | Qualcomm Incorporated |
| S2-2503310 | Generlization of MF capabilities registration and discovery | Qualcomm Incorporated |
| S2-2503314 | [DRAFT] Reply LS on Privacy and security aspects regarding DC management by the network | Qualcomm Incorporated |
| S2-2503552 | Clarification on Nhss_ImsEE_Subscribe Immediate reporting | Huawei, HiSilicon |
| S2-2503553 | Update IMS SBA description to align with other specifications | Huawei, HiSilicon |
| S2-2503554 | Update IMS DC capability exposure procedure with detailed description | Huawei, HiSilicon |
| S2-2503555 | Correction on standalone data channel description | Huawei, HiSilicon |
| S2-2503556 | Update network centric call flow for Avatar Communication | Huawei, HiSilicon |
| S2-2503578 | De-multiplexing ADC to avoid multiplexing ADCs with same stream ID | Vivo |
| S2-2503579 | Abbreviations of ADC and BDC | Vivo |
| S2-2503580 | Adding more event filters for ADC media type | Vivo |
| S2-2503581 | Update on support of DC interworking | Vivo |
| S2-2503582 | Modification on general description for standalone IMS DC session | Vivo |
| S2-2503678 | Clarification on Adding BDC Procedure | ZTE |
| S2-2503679 | Clarification on Establishing IMS Session with Standalone BDC Procedure | ZTE |
| S2-2503680 | Clarification on Establishing IMS Session with Standalone A2P ADC Procedure | ZTE |
| S2-2503681 | Correction on IMS Service Definition | ZTE |
| S2-2503682 | Clarification on NRF Service Related to MF | ZTE |
| S2-2503683 | Clarification on DC Application Server | ZTE |
| S2-2503684 | Additional Information in Adding P2P ADC Procedure | ZTE |
| S2-2503685 | [DRAFT] Reply LS on Privacy and security aspects regarding DC management by the network | ZTE |
| S2-2503695 | Discussion on AsInfoGet service operation. | Samsung |
| S2-2503697 | MMTel media removal clarification | Samsung |
| S2-2503701 | HSS handling for subscription with IMS | Samsung |
| S2-2503748 | [DRAFT] Reply LS on multiplexing capability negotiation | Qualcomm Incorporated |
| S2-2503754 | Correction of detection criteria for event exposure | China Mobile |
| S2-2503755 | Updates on procedure and service of DC interworking via DC AS | China Mobile |
| S2-2503756 | Clarification on PSI configuration on UE | China Mobile |
| S2-2503757 | Clarification on usage of Avatar ID | China Mobile |
| S2-2503758 | Updates on HSS Nhss_ImsEventExposure service | China Mobile |
| S2-2503763 | [DRAFT] Reply LS on multiplexing capability negotiation | China Mobile |
| S2-2503982 | Additional Information in Adding P2P ADC Procedure | ZTE |
| S2-2503983 | [DRAFT] Reply LS on Privacy and security aspects regarding DC management by the network | ZTE |
| S2-2503984 | Correction on DC multiplexing capability negotiation | Qualcomm Incorporated |
| S2-2503985 | [DRAFT] Reply LS on multiplexing capability negotiation | Qualcomm Incorporated |
| S2-2503986 | KI#1: Corrections to IMS Subscribe/Notify Framework Architecture | Ericsson |
| S2-2503987 | Correction on IMS Service Definition | ZTE |
| S2-2503988 | KI#1: Immediate Reporting | Ericsson |
| S2-2503989 | HSS handling for subscription with IMS | Samsung |
| S2-2503990 | KI#2: Generalizing Information Retrieval | Ericsson |
| S2-2503991 | KI#2: Correction of procedures in clause AG | Nokia, ZTE, Huawei, HiSilicon |
| S2-2504206 | Additional Information in Adding P2P ADC Procedure | ZTE |
| S2-2504207 | Reply LS on Privacy and security aspects regarding DC management by the network | SA WG2 |
| S2-2504208 | Correction on DC multiplexing capability negotiation | Qualcomm Incorporated |
| S2-2504209 | Reply LS on multiplexing capability negotiation | SA WG2 |
| S2-2504210 | KI#1: Corrections to IMS Subscribe/Notify Framework Architecture | Ericsson, Nokia, ZTE, Huawei |
| S2-2504211 | Correction on IMS Service Definition | ZTE |
| S2-2504212 | KI#2: Generalizing Information Retrieval | Ericsson |
| S2-2504213 | KI#2: Correction of procedures in clause AG | Nokia, ZTE, Huawei, HiSilicon |
| S2-2504214 | Additional Information in Adding P2P ADC Procedure | ZTE, Qualcomm Incorporated |
| S2-2504247 | KI#2: Generalizing Information Retrieval | Ericsson |
| S2-2504248 | KI#2: Correction of procedures in clause AG | Nokia, ZTE, Huawei, HiSilicon |
| TDoc | Title | Source |
|---|---|---|
| S2-2502794 | LS from RAN WG2: Reply LS on Application-Layer FEC Awareness at RAN | RAN WG2 |
| S2-2502800 | LS from RAN WG3: Reply LS on FS_XRM Ph2 for available data rate report | RAN WG3 |
| S2-2502814 | LS from CT WG4: LS on MoQ Relay Address in UPF Profile | CT WG4 |
| S2-2502815 | LS from CT WG4: LS on Transport Level Marking on N3/N9 | CT WG4 |
| S2-2502820 | LS from RAN WG2: LS on uplink rate control | RAN WG2 |
| S2-2503005 | 23.501 Support of uplink rate control for QoS flows at RAN | Lenovo |
| S2-2503006 | 23.502 Support of uplink rate control for QoS flows at RAN | Lenovo |
| S2-2503007 | 23.503 Support of uplink rate control for QoS flows at RAN | Lenovo |
| S2-2503008 | [DRAFT] LS reply on uplink rate control for XR service | Lenovo |
| S2-2503093 | [DRAFT] LS on on MoQ Relay Address in UPF Profile | Nokia |
| S2-2503094 | Removal of the MoQ Relay Address in UPF Profile | Nokia |
| S2-2503096 | Correction on the Support of MoQ | Nokia |
| S2-2503147 | KI#1, Update to Notification Control and Alternative QoS profile with PDU Set QoS | Vivo, Nokia |
| S2-2503148 | [DRAFT] LS reply on uplink rate control | vivo |
| S2-2503206 | Correction concerning presence of PDU Set Control information without a Protocol Description | Ericsson |
| S2-2503207 | MoQ missing from the Protocol Description | Ericsson |
| S2-2503208 | Triggering of Transport Level Marking based on PDU Set Importance in I-SMF | Ericsson |
| S2-2503209 | [DRAFT] LS Reply on Transport Level Marking on N3/N9 | Ericsson |
| S2-2503210 | Indication of Rate-Adaptable QoS Flows to NG-RAN | Ericsson |
| S2-2503211 | Indication of Rate-Adaptable QoS Flows to NG-RAN | Ericsson |
| S2-2503212 | Indication of Rate-Adaptable QoS Flows to NG-RAN | Ericsson |
| S2-2503213 | [DRAFT] LS Reply on uplink rate control | Ericsson |
| S2-2503226 | KI#3: Align the mapping of PSI value to DSPC Drop Precedence setting | China Mobile |
| S2-2503228 | KI#4: Resolve the incorrect multiplex support in NOTE | China Mobile |
| S2-2503328 | Alternative QoS profile handling considering PDU Set QoS parameters | Samsung |
| S2-2503329 | Notification control on use of PDU Set QoS parameters | Samsung |
| S2-2503334 | PDU Set based handling without PDU Set QoS parameters | Samsung |
| S2-2503335 | [DRAFT] LS Reply on uplink rate control | SAMSUNG |
| S2-2503336 | Transport level packet marking operation at I-SMF/I-UPF | Samsung |
| S2-2503339 | [DRAFT] LS Reply on Transport Level Marking on N3/N9 | SAMSUNG |
| S2-2503393 | [DRAFT] LS reply on uplink rate control | OPPO |
| S2-2503433 | Support Alternative QoS profile with PDU Set QoS and Notification Control with explicit NG-RAN indication Alt-1 | Nokia |
| S2-2503434 | Support Alternative QoS profile with PDU Set QoS and Notification Control with explicit SMF indication Alt-2 | Nokia |
| S2-2503435 | Indication of PDU Set QoS in Notification Control | Nokia |
| S2-2503436 | Discussion on PDU set QoS explicit indication by NG-RAN or SMF. | Nokia |
| S2-2503437 | Discussion on PDU set based DSCP marking. | Nokia |
| S2-2503438 | [DRAFT] Reply LS on Transport Level Marking based on PDU Set Importance | Nokia |
| S2-2503439 | Correction on PDU set based DSCP marking | Nokia |
| S2-2503470 | Update on PDU session establishment procedure for MoQ | Huawei, HiSilicon |
| S2-2503517 | Clarifications for multiplexed media traffic | Huawei, HiSilicon |
| S2-2503518 | Clarifications for multiplexed media traffic | Huawei, HiSilicon |
| S2-2503519 | Clarifications for available bitrate exposure | Huawei, HiSilicon |
| S2-2503520 | Clarifications for available bitrate exposure | Huawei, HiSilicon |
| S2-2503521 | Clarifications for control of expedited data transfer | Huawei, HiSilicon |
| S2-2503522 | Clarifications for rate limitation exposure | Huawei, HiSilicon |
| S2-2503523 | Clarifications for rate limitation exposure | Huawei, HiSilicon |
| S2-2503524 | Clarifications for QoS Notification Control with direction information | Huawei, HiSilicon |
| S2-2503525 | Clarifications for QoS Notification Control with direction information | Huawei, HiSilicon |
| S2-2503526 | Clarifications for PDU Set QoS information based DSCP marking | Huawei, HiSilicon |
| S2-2503545 | Corrections for 23.501 Transport Level Marking on N3/N9 | Lenovo |
| S2-2503547 | [DRAFT] LS out CT WG4 on Transport Level Marking on N3/N9 | Lenovo |
| S2-2503560 | Update the procedures with Multi-modal service ID | Vivo |
| S2-2503589 | QoS Notification Control of PDU Set QoS with only one direction | CATT |
| S2-2503590 | Policy Control on QoS Notification Control of PDU Set QoS with only one direction | CATT |
| S2-2503732 | Available Bitrate Reporting when the Serving RAN Node Changes | InterDigital Inc. |
| S2-2503734 | [DRAFT] LS on Available Bitrate Monitoring | InterDigital Inc. |
| S2-2503782 | [DRAFT] LS Reply to CT WG4 on MoQ Relay Address in UPF Profile | China Mobile |
| S2-2503783 | Clarification on provisioning Multi-modal Service ID to NG-RAN | China Mobile |
| S2-2503785 | Support of providing MMSID from 5GC to NG-RAN | China Mobile |
| S2-2503786 | Clarification of providing MMSID from 5GC to NG-RAN | China Mobile |
| S2-2503804 | Add missing XRM condition on PDU Set QoS Notification control | Nokia |
| S2-2503825 | Correcting references to TS 23.501 clauses | Nokia |
| S2-2503882 | XRM_Ph2_KI1 Update of PDU Set Information Marking witout DL Set QoS | Xiaomi |
| S2-2503883 | XRM_Ph2_KI3 Update of PSI based DSCP Marking | Xiaomi |
| S2-2503884 | XRM_Ph2_Clarification on the DL Protocol Description | Xiaomi |
| S2-2503885 | [DRAFT] LS Reply on Transport Level Marking on N3N9 | Xiaomi |
| S2-2503888 | Ph2_KI1 Update of QNC with AQP including PDU Set QoS | Xiaomi |
| S2-2503907 | Removal of the MoQ Relay Address in UPF Profile | Nokia, China Mobile |
| S2-2503908 | LS Reply to CT WG4 on MoQ Relay Address in UPF Profile | SA WG2 |
| S2-2503909 | Triggering of Transport Level Marking based on PDU Set Importance in I-SMF | Ericsson |
| S2-2503910 | [DRAFT] LS out CT WG4 on Transport Level Marking on N3/N9 | Lenovo |
| S2-2503931 | [DRAFT] LS reply on uplink rate control | vivo |
| S2-2503932 | 23.501 Support of uplink rate control for QoS flows at RAN | Lenovo |
| S2-2503933 | Available Bitrate Reporting when the Serving RAN Node Changes | InterDigital Inc. |
| S2-2503934 | [DRAFT] LS on Available Bitrate Monitoring | InterDigital Inc. |
| S2-2503935 | Clarifications for available bitrate exposure | Huawei, HiSilicon |
| S2-2503936 | Clarifications for rate limitation exposure | Huawei, HiSilicon |
| S2-2503937 | Support Alternative QoS profile with PDU Set QoS and Notification Control with explicit NG-RAN indication Alt-1 | Nokia |
| S2-2503938 | Indication of PDU Set QoS in Notification Control | Nokia |
| S2-2503939 | Correction concerning presence of PDU Set Control information without a Protocol Description | Ericsson |
| S2-2503940 | PDU Set based handling without PDU Set QoS parameters | Samsung |
| S2-2503941 | QoS Notification Control of PDU Set QoS with only one direction | CATT |
| S2-2503942 | Clarifications for QoS Notification Control with direction information | Huawei, HiSilicon |
| S2-2504162 | [DRAFT] LS out CT WG4 on Transport Level Marking on N3/N9 | Lenovo |
| S2-2504163 | [DRAFT] LS reply on uplink rate control | vivo |
| S2-2504164 | Available Bitrate Reporting when the Serving RAN Node Changes | InterDigital Inc. |
| S2-2504165 | Clarifications for rate limitation exposure | Huawei, HiSilicon |
| S2-2504166 | Clarifications for rate limitation exposure | Huawei, HiSilicon |
| S2-2504167 | Correction concerning presence of PDU Set Control information without a Protocol Description | Ericsson |
| S2-2504168 | PDU Set based handling without PDU Set QoS parameters | Samsung |
| S2-2504169 | Clarifications for QoS Notification Control with direction information | Huawei, HiSilicon |
| S2-2504170 | QoS Notification Control of PDU Set QoS with only one direction | CATT, Huawei, Nokia |
| S2-2504171 | Ph2_KI1 Update of QNC with AQP including PDU Set QoS | Xiaomi |
| S2-2504229 | Triggering of Transport Level Marking based on PDU Set Importance in I-SMF | Ericsson |
| S2-2504230 | [DRAFT] LS out CT WG4 on Transport Level Marking on N3/N9 | Lenovo |
| S2-2504231 | Available Bitrate Reporting when the Serving RAN Node Changes | InterDigital Inc. |
| S2-2504232 | Available Bitrate Reporting when the Serving RAN Node Changes | InterDigital Inc. |
| S2-2504252 | LS reply on uplink rate control | SA WG2 |
| S2-2504417 | Available Bitrate Reporting when the Serving RAN Node Changes | InterDigital Inc. |
| S2-2504418 | Clarifications for rate limitation exposure | Huawei, HiSilicon |
| S2-2504419 | QoS Notification Control of PDU Set QoS with only one direction | CATT, Huawei, Nokia |
| S2-2504420 | Clarifications for QoS Notification Control with direction information | Huawei, HiSilicon, Nokia |
| S2-2504481 | Clarifications for rate limitation exposure | Huawei, HiSilicon |
| TDoc | Title | Source |
|---|---|---|
| S2-2502817 | LS from TSG CT: LS reply to LS on energy information collection from OAM to EIF | TSG CT |
| S2-2502843 | LS from SA WG5: LS reply to LS on energy information collection from OAM to EIF | SA WG5 |
| S2-2503054 | Update on Energy Consumption information collection procedure | ETRI |
| S2-2503055 | Update on SMF event exposure to support Energy Consumption information | ETRI |
| S2-2503056 | Editorial update on Energy Consumption information collection and exposure | ETRI |
| S2-2503121 | Discussion on Energy Consumption model. | NTT DOCOMO |
| S2-2503122 | Correction of Energy Consumption Model | NTT DOCOMO |
| S2-2503124 | Clarification on the reporting period of energy-related information | NTT DOCOMO |
| S2-2503125 | Negotiation for future background data transfer considering energy | NTT DOCOMO, Toyota, KDDI |
| S2-2503455 | Adding Energy indication to BDT procedure and service operation | ZTE |
| S2-2503456 | Clarification on the BDT policy decision | ZTE |
| S2-2503457 | Correction on the granularity description and clause reference | ZTE |
| S2-2503458 | Procedure Correction on the Energy Consumption information collection | ZTE |
| S2-2503459 | Clarification on the OAM input | ZTE |
| S2-2503460 | Resolve the EN in the EIF service | ZTE |
| S2-2503572 | Correction on energy consumption information collection and exposure | CATT |
| S2-2503586 | Discussion on the collection and exposure of data usage. | Nokia |
| S2-2503588 | Energy Consumption information collection procedure clarification | Nokia |
| S2-2503593 | SMF exposure service clarification for Energy Consumption information collection | Nokia |
| S2-2503595 | EIF exposure serice definition clarification | Nokia |
| S2-2503601 | EIF exposure service definition clarification | Nokia |
| S2-2503621 | Update the procedure and EIF service | Vivo |
| S2-2503627 | Corrections for energy saving related AF input on BDT policy negotiation | Huawei, HiSilicon, NTT DOCOMO, KDDI |
| S2-2503628 | Report of SMF to EIF for user-plane energy consumption calculation | Huawei, HiSilicon |
| S2-2503629 | On the report of SMF to EIF for user-plane energy consumption calculation | Huawei, HiSilicon |
| S2-2503630 | Update on EC collection upon PDU Session management | Huawei, HiSilicon |
| S2-2503631 | On the report of SMF to EIF for user-plane energy consumption calculation | Huawei, HiSilicon |
| S2-2503632 | Clarification on the EventExposure service operation of SMF | Huawei, HiSilicon |
| S2-2503633 | Clarification on the EventExposure service operation of SMF | Huawei, HiSilicon |
| S2-2503637 | Update the procedure for BDT policy decisions | Vivo |
| S2-2503639 | Solve the editor s note about the renewable energy information | Vivo |
| S2-2503650 | Update on SMF services | Vivo |
| S2-2503651 | Update on the energy consumption information exposure | Vivo |
| S2-2503731 | EIF discvoery and selection | Samsung |
| S2-2503735 | EIF discvoery and selection | Samsung |
| S2-2503736 | Clarifications on SMF event for information for energy consumption calculation | Samsung |
| S2-2503737 | Energy consumption information for access type | Samsung |
| S2-2503740 | Energy consumption information for access type | Samsung |
| S2-2503780 | Alignment of Energy indicator in BDT policy | China Mobile |
| S2-2503781 | Energy subscription termination and event exposure in SMF | China Mobile |
| S2-2503805 | Energy consumption information collection for new PDU Session | Samsung |
| S2-2503806 | Support of renewable energy information | Samsung |
| S2-2503807 | Update on the energy consumption information collection | Vivo |
| S2-2503809 | Collection of energy consumption information for new PDU session | Samsung |
| S2-2503994 | Solve the editor’s note about the renewable energy information | vivo, ZTE |
| S2-2503995 | Clarification on the OAM input | ZTE |
| S2-2503996 | Energy Consumption information collection procedure clarification | Nokia |
| S2-2503997 | On the report of SMF to EIF for user-plane energy consumption calculation | Huawei, HiSilicon |
| S2-2503998 | Clarification on the EventExposure service operation of SMF | Huawei, HiSilicon |
| S2-2503999 | Correction on the granularity description and clause reference | ZTE |
| S2-2504000 | Correction on energy consumption information collection and exposure | CATT, ZTE, vivo, ETRI |
| S2-2504001 | Energy consumption information collection for new PDU Session | Samsung |
| S2-2504002 | Update on the energy consumption information collection | vivo |
| S2-2504003 | On the report of SMF to EIF for user-plane energy consumption calculation | Huawei, HiSilicon |
| S2-2504004 | Energy consumption information for access type | Samsung |
| S2-2504005 | Energy consumption information for access type | Samsung |
| S2-2504006 | SMF exposure service clarification for Energy Consumption information collection | Nokia |
| S2-2504007 | Update on the energy consumption information exposure | vivo |
| S2-2504008 | EIF exposure serice definition clarification | Nokia |
| S2-2504009 | EIF exposure service definition clarification | Nokia |
| S2-2504010 | Resolve the EN in the EIF service | ZTE |
| S2-2504080 | Energy Consumption information collection procedure clarification | Nokia |
| S2-2504091 | SMF exposure service clarification for Energy Consumption information collection | Nokia |
| S2-2504297 | Energy Consumption information collection procedure clarification | Nokia, CMCC, Huawei, Samsung |
| S2-2504298 | On the report of SMF to EIF for user-plane energy consumption calculation | Huawei, HiSilicon, NEC |
| S2-2504299 | Clarification on the EventExposure service operation of SMF | Huawei, HiSilicon |
| S2-2504300 | Correction on the granularity description and clause reference | ZTE |
| S2-2504301 | Correction on energy consumption information collection and exposure | CATT, ZTE, vivo, ETRI |
| S2-2504302 | Clarification on the OAM input | ZTE, Huawei |
| S2-2504303 | Energy consumption information collection for new PDU Session | Samsung |
| S2-2504304 | Update on the energy consumption information collection | Vivo |
| S2-2504305 | On the report of SMF to EIF for user-plane energy consumption calculation | Huawei, HiSilicon |
| S2-2504306 | Energy consumption information for access type | Samsung |
| S2-2504307 | SMF exposure service clarification for Energy Consumption information collection | Nokia, Huawei, CMCC |
| S2-2504317 | Energy consumption information for access type | Samsung |
| S2-2504338 | EIF exposure serice definition clarification | Nokia |
| S2-2504339 | Clarification on the OAM input | ZTE, Huawei |
| S2-2504340 | Energy consumption information for access type | Samsung, NTT DOCOMO |
| S2-2504341 | Energy consumption information for access type | Samsung, NTT DOCOMO |
| S2-2504348 | Clarification on the OAM input | ZTE, Huawei |
| TDoc | Title | Source |
|---|---|---|
| S2-2502805 | LS from CT WG1: LS on PWS enhancements for MWAB and MBSR | CT WG1 |
| S2-2502830 | LS from RAN WG3: Reply LS on FS_VMR_Ph2 solution impacts to RAN (Additional ULI) | RAN WG3 |
| S2-2502831 | LS from RAN WG3: Reply LS on Support of Location Service Involving WAB-Nodes | RAN WG3 |
| S2-2502844 | LS from SA WG5: LS on MWAB-gNB Configurations | SA WG5 |
| S2-2502975 | [DRAFT] Reply LS on MWAB-gNB Configuration | Ericsson |
| S2-2502976 | [DRAFT] Reply LS on PWS enhancement for MWAB and MBSR | Ericsson |
| S2-2502977 | PWS handling with Additional ULI | Ericsson, Qualcomm Incorporated |
| S2-2502978 | PWS handling update for VMR | Ericsson, Qualcomm Incorporated |
| S2-2502979 | MWAB-gNB indication to AMF | Ericsson |
| S2-2502980 | MWAB-gNB authorization handling update | Ericsson |
| S2-2502981 | PWS handling with Additional ULI | Ericsson, Qualcomm Incorporated |
| S2-2502982 | PWS handling update for VMR | Ericsson, Qualcomm Incorporated |
| S2-2503018 | Clarification on MWAB-UE aspect | LG Electronics |
| S2-2503168 | Clarification of mobility clause | Nokia |
| S2-2503177 | Clarification of the network slicing clause | Nokia, China Telecom |
| S2-2503181 | Handling of BH PDU session in the network | Nokia |
| S2-2503183 | Add MWAB indication to NEF monitoring events | Nokia |
| S2-2503184 | Removal of text for PWS | Nokia |
| S2-2503185 | Removal of text for PWS | Nokia |
| S2-2503351 | [DRAFT] Reply LS on PWS enhancements for MWAB and MBSR | Huawei, HiSilicon |
| S2-2503352 | MWAB-UE authorization | Huawei, HiSilicon |
| S2-2503353 | Backhaul PDU Session handling for MWAB | Huawei, HiSilicon |
| S2-2503354 | PWS enhancements for MBSR | Huawei, HiSilicon |
| S2-2503355 | PWS enhancements for MBSR and MWAB | Huawei, HiSilicon |
| S2-2503356 | PWS enhancements for MBSR | Huawei, HiSilicon |
| S2-2503357 | PWS enhancements for MBSR and MWAB | Huawei, HiSilicon |
| S2-2503440 | PWS enhancements for MWAB and MBSR | Samsung |
| S2-2503443 | PWS enhancements for MWAB and MBSR | Samsung |
| S2-2503645 | Additional ULI Update | CATT |
| S2-2503646 | [DRAFT] Reply LS on FS_VMR_Ph2 solution impacts to RAN (Additional ULI) | CATT |
| S2-2503813 | Correction of the Additional ULI mapping conditions for MWAB | Qualcomm Incorporated, Ericsson, Nokia, Huawei, HiSilicon, LG Electronics |
| S2-2503816 | [DRAFT] Reply LS on FS_VMR_Ph2 solution impacts to RAN (Additional ULI) | Qualcomm Incorporated |
| S2-2503817 | [DRAFT] Reply LS on MWAB-gNB Configurations | Qualcomm Incorporated |
| S2-2503818 | Correction of the 5GC-MT-LR procedure involving MWAB | Qualcomm Incorporated, Nokia |
| S2-2503872 | Clarification on MWAB URSP processing | Samsung |
| S2-2503873 | [DRAFT] Reply LS on MWAB-gNB Configurations | Samsung |
| S2-2504101 | [DRAFT] Reply LS on MWAB-gNB Configurations | Qualcomm Incorporated |
| S2-2504102 | Clarification on MWAB URSP processing | Samsung |
| S2-2504103 | Backhaul PDU Session handling for MWAB | Huawei, HiSilicon, Samsung |
| S2-2504104 | PWS enhancements for MBSR | Huawei, HiSilicon, Ericsson |
| S2-2504105 | PWS handling | Ericsson, Qualcomm Incorporated |
| S2-2504106 | Removal of text for PWS | Nokia |
| S2-2504107 | PWS enhancements for MWAB and MBSR | Samsung, Nokia, Ericsson |
| S2-2504108 | MWAB-gNB indication to AMF | Ericsson, Huawei, HiSilicon |
| S2-2504109 | Reply LS on PWS enhancement for MWAB and MBSR | SA WG2 |
| S2-2504110 | Reply LS on FS_VMR_Ph2 solution impacts to RAN (Additional ULI) | SA WG2 |
| S2-2504111 | Add MWAB indication to NEF monitoring events | Nokia |
| S2-2504379 | Clarification on MWAB URSP processing | Samsung |
| S2-2504380 | Reply LS on MWAB-gNB Configurations | SA WG2 |
| S2-2504381 | PWS enhancements for MBSR | Huawei, HiSilicon, Ericsson |
| S2-2504382 | PWS handling | Ericsson, Qualcomm Incorporated, Huawei, HiSilicon, Samsung |
| S2-2504383 | Reply LS on PWS enhancement for MWAB and MBSR | SA WG2 |
| S2-2504384 | MWAB-gNB indication to AMF | Ericsson, Huawei, HiSilicon, Nokia |
| S2-2504385 | Backhaul PDU Session handling for MWAB | Huawei, HiSilicon, Samsung |
| TDoc | Title | Source |
|---|---|---|
| S2-2502885 | Removing QoS EN | KPN N.V. |
| S2-2502886 | Editorial corrections | KPN N.V. |
| S2-2502968 | Updates to Common identifiers for 5G ProSe UE-to-Network Relay | Ericsson, AT&T |
| S2-2503015 | Introduction of Multi-hop Layer-2 UE-to-Network relaying | CATT |
| S2-2503052 | Policy/Parameter provisioning to support PWS for 5G ProSe multi-hop U2N Relay | OPPO |
| S2-2503141 | Clarification on Multi-hop U2N and U2U Discovery | Huawei, HiSilicon |
| S2-2503142 | Clarification on Relay reselection for 5G ProSe Remote UE with 5G ProSe Multi-hop UE-to-Network Relays | Huawei, HiSilicon |
| S2-2503203 | Updates to the 5G ProSe Multi-hop UE-to-UE Relay Discovery procedure | Ericsson, AT&T, FirstNet, Qualcomm |
| S2-2503279 | Editorial correction on Multi-hop UE-to-UE Relay | China Telecom |
| S2-2503374 | Adding Layer-2 Multi-hop U2N relaying aspects to UE Subscription data | LG Electronics |
| S2-2503824 | End UE RSC-Bounded Routing | Nokia, Nokia Shanghai Bell |
| S2-2504116 | Removing QoS EN | KPN N.V. |
| S2-2504117 | Updates to Common identifiers for 5G ProSe UE-to-Network Relay | Ericsson, AT&T |
| S2-2504118 | Policy/Parameter provisioning to support PWS for 5G ProSe multi-hop U2N Relay | OPPO |
| S2-2504119 | Clarification on Multi-hop U2N and U2U Discovery | Huawei, HiSilicon |
| S2-2504120 | Clarification on Relay reselection for 5G ProSe Remote UE with 5G ProSe Multi-hop UE-to-Network Relays | Huawei, HiSilicon, Samsung |
| S2-2504121 | Updates to the 5G ProSe Multi-hop UE-to-UE Relay Discovery procedure | Ericsson, AT&T, FirstNet, Qualcomm, Samsung |
| S2-2504122 | End UE RSC-Bounded Routing | Nokia, Nokia Shanghai Bell |
| S2-2504123 | Introduction of Multi-hop Layer-2 UE-to-Network relaying | CATT, LG Electronics |
| S2-2504124 | Editorial correction on Multi-hop UE-to-UE Relay | China Telecom |
| S2-2504390 | Clarification on Multi-hop U2N and U2U Discovery | Huawei, HiSilicon, Samsung |
| S2-2504391 | Clarification on Relay reselection for 5G ProSe Remote UE with 5G ProSe Multi-hop UE-to-Network Relays | Huawei, HiSilicon |
| S2-2504392 | Editorial correction on Multi-hop UE-to-UE Relay | China Telecom |
| TDoc | Title | Source |
|---|---|---|
| S2-2502806 | LS from CT WG1: LS on support for multiple non-3GPP device identifiers | CT WG1 |
| S2-2502872 | [DRAFT] Reply LS on support for multiple non-3GPP device identifiers | Nokia |
| S2-2502894 | Clarification on AF-5GC interaction for provisioning non-3GPP device identifiers | Apple, Charter Communications |
| S2-2502900 | PCF and SMF selection for QoS differentiation for non-3GPP devices | Ericsson |
| S2-2502901 | Selection mechanisms for SMF and PCF for non-3GPP devices QoS differentiation | Ericsson |
| S2-2502902 | QoS differention for multiple Non-3GPP devices | Ericsson, AT&T |
| S2-2502903 | Results of QoS differention for multiple Non-3GPP devices | Ericsson, AT&T |
| S2-2502904 | Removing Non-3GPP Device Connection Information from SM policy control create | Ericsson |
| S2-2502905 | Handling removal of Non-3GPP Device Identifiers from UDR | Ericsson, AT&T |
| S2-2502906 | Clarifying port ranges and removing EN | Ericsson |
| S2-2502907 | [DRAFT] LS reply on support for multiple non-3GPP device identifiers | Ericsson will be SA2 |
| S2-2502985 | [DRAFT] Reply LS on support for multiple non-3GPP device identifiers | Google Korea LLC |
| S2-2502986 | Providing device identifier information in PDU session modification request | |
| S2-2502987 | Providing device identifier information in PDU session modification request | |
| S2-2502988 | Providing device identifier information in PDU session modification request | |
| S2-2503000 | Adding a Reference to the Home Routed Roaming PDU Session Modification Procedure | InterDigital Inc., LG Electronics, Samsung, Nokia |
| S2-2503001 | Updating the Nsmf_PDUSession_Update service description to account for non-3GPP device connection information | InterDigital Inc., LG Electronics, Samsung, Nokia |
| S2-2503031 | Clarifications to Session Management aspects for handling Non-3GPP Device Identifiers | Samsung |
| S2-2503053 | [DRAFT] Reply to LS on support for multiple non-3GPP device identifiers | Samsung TO BE SA2 |
| S2-2503074 | Clarifications on SM signalling including non-3GPP device identifiers for QoS differentiation | Apple |
| S2-2503075 | Clarifications for SM signalling including non-3GPP device identifiers for QoS differentiation | Apple |
| S2-2503306 | Clarification on PDU Session for non-3GPP device | LG Electronics |
| S2-2503330 | Inclusion of several Non-3GPP Device Identifiers | Nokia, InterDigital Inc., LG Electronics |
| S2-2503331 | Inclusion of several Non-3GPP Device Identifiers | Nokia, InterDigital Inc., LG Electronics |
| S2-2503332 | Inclusion of several Non-3GPP Device Identifiers | Nokia, InterDigital Inc., LG Electronics |
| S2-2503337 | Support of SMF selection considering the Non-3GPP Device Identifier | Huawei, HiSilicon |
| S2-2503338 | Support of SMF selection for Non-3GPP Device Identifer | Huawei, HiSilicon |
| S2-2503461 | [DRAFT] Reply LS on support for multiple non-3GPP device identifiers | ZTE |
| S2-2503462 | Clarification on the non-3gpp device identifier activation and removal | ZTE, Xiaomi |
| S2-2503463 | Clarification on the non-3gpp device identifier activation and removal | ZTE, Xiaomi |
| S2-2503464 | Clarification on the non-3gpp device identifier activation and removal | ZTE, Xiaomi |
| S2-2503465 | Clarification on the subscription to UDR | ZTE |
| S2-2503596 | Update on Non-3GPP Device Identifier(s) Information provisioning and policy control | Xiaomi |
| S2-2503597 | Update definition of non-3GPP device connection information | Xiaomi |
| S2-2503604 | [DRAFT] UIA LSout on support for multiple non-3GPP device identifiers | Huawei, HiSilicon |
| S2-2503605 | Clarificaiton on supporting multiple non-3GPP device identifiers | Huawei, HiSilicon |
| S2-2503606 | Clarificaiton on supporting multiple non-3GPP device identifiers | Huawei, HiSilicon |
| S2-2503607 | Clarificaiton on supporting multiple non-3GPP device identifiers | Huawei, HiSilicon |
| S2-2503677 | Correction about the Non-3GPP Device Connection Information | China Mobile |
| S2-2503858 | [DRAFT] Reply LS on support for multiple non-3GPP device identifiers | CSCN |
| S2-2503864 | [DRAFT] LS Reply on support for multiple non-3GPP device identifiers | Intel |
| S2-2504022 | Inclusion of several Non-3GPP Device Identifiers | Nokia, InterDigital Inc., LG Electronics, Samsung |
| S2-2504023 | QoS differention for multiple Non-3GPP devices | Ericsson |
| S2-2504024 | Clarificaiton on supporting multiple non-3GPP device identifiers | Huawei, HiSilicon |
| S2-2504025 | Handling removal of Non-3GPP Device Identifiers from UDR | Ericsson |
| S2-2504026 | [DRAFT] LS reply on support for multiple non-3GPP device identifiers | Ericsson will be SA2 |
| S2-2504027 | Clarifications on SM signalling including non-3GPP device identifiers for QoS differentiation | Apple |
| S2-2504028 | Update on Non-3GPP Device Identifier(s) Information provisioning and policy control | Xiaomi |
| S2-2504029 | Updating the Nsmf_PDUSession_Update service description to account for non-3GPP device connection information | InterDigital Inc., LG Electronics, Samsung, Nokia |
| S2-2504030 | Clarification on the subscription to UDR | ZTE, Nokia |
| S2-2504031 | Correction about the Non-3GPP Device Connection Information | China Mobile |
| S2-2504032 | Clarifying port ranges and removing EN | Ericsson |
| S2-2504033 | Clarifications to Session Management aspects for handling Non-3GPP Device Identifiers | Samsung |
| S2-2504034 | Clarification on PDU Session for non-3GPP device | LG Electronics |
| S2-2504035 | PCF and SMF selection for QoS differentiation for non-3GPP devices | Ericsson, Huawei? |
| S2-2504036 | Support of SMF selection for Non-3GPP Device Identifer | Huawei, HiSilicon |
| S2-2504253 | Inclusion of several Non-3GPP Device Identifiers | Nokia, InterDigital Inc., LG Electronics, Samsung, ZTE, Xiaomi |
| S2-2504254 | QoS differention for multiple Non-3GPP devices | Ericsson, AT&T, Xiaomi |
| S2-2504255 | Clarificaiton on supporting multiple non-3GPP device identifiers | Huawei, HiSilicon, Samsung |
| S2-2504256 | [DRAFT] LS reply on support for multiple non-3GPP device identifiers | Ericsson will be SA2 |
| S2-2504257 | Clarifications on SM signalling including non-3GPP device identifiers for QoS differentiation | Apple |
| S2-2504258 | Clarifications to Session Management aspects for handling Non-3GPP Device Identifiers | Samsung |
| S2-2504259 | Clarification on the subscription to UDR | ZTE, Nokia, NEC, Xiaomi |
| S2-2504260 | Clarification on PDU Session for non-3GPP device | LG Electronics |
| S2-2504332 | QoS differention for multiple Non-3GPP devices | Ericsson, AT&T, Xiaomi, Nokia, CableLabs |
| S2-2504333 | Clarificaiton on supporting multiple non-3GPP device identifiers | Huawei, HiSilicon, Samsung, Deutsche Telekom, Nokia, LGE, Charter, ZTE |
| S2-2504334 | Clarifications on SM signalling including non-3GPP device identifiers for QoS differentiation | Apple, Charter Communications, Nokia |
| S2-2504335 | Clarifications to Session Management aspects for handling Non-3GPP Device Identifiers | Samsung |
| S2-2504336 | QoS differention for multiple Non-3GPP devices | Ericsson, AT&T, Xiaomi, Nokia, CableLabs, ZTE |
| S2-2504337 | LS reply on support for multiple non-3GPP device identifiers | SA WG2 |
| S2-2504477 | Clarificaiton on supporting multiple non-3GPP device identifiers | Huawei, HiSilicon, Samsung, Deutsche Telekom, Nokia, LGE, Charter Communications, ZTE |
| TDoc | Title | Source |
|---|---|---|
| S2-2502812 | LS from CT WG4: LS on Security related protocol-specific parameters for N6 delay measurement | CT WG4 |
| S2-2502895 | Clarification on SMF triggered I-SMF insertion or removal for Local Offloading Management | Nokia |
| S2-2503259 | KI#1 Clarification on EAS Discovery using IP replacement to support Local Offloading Management | OPPO |
| S2-2503391 | Clarification on the Local Offloading Management and SMF Service Area | LG Electronics |
| S2-2503395 | Clarification on the Local Offloading Management Service Area | LG Electronics |
| S2-2503397 | Clarification on the AF trafficInfluence information from SMF to I-SMF | LG Electronics |
| S2-2503399 | Clarification on the AF trafficInfluence information from SMF to I-SMF | LG Electronics |
| S2-2503403 | Clarification of the selected I-SMF for Local offloading traffic handling . | Huawei, HiSilicon |
| S2-2503404 | KI#1: Clarfication on the I-SMF selected for local offloading managment | Huawei, HiSilicon, Samsung |
| S2-2503405 | KI#1: Clarfication on the I-SMF selected for local offloading managment | Huawei, HiSilicon, Samsung |
| S2-2503406 | KI#1: Clarfication on the I-SMF selected for local offloading managment | Huawei, HiSilicon, Samsung |
| S2-2503407 | Interaction between the I-SMF and SMF . | Huawei, HiSilicon |
| S2-2503408 | Interaction between SMF and I-SMF | Huawei, Hisilicon |
| S2-2503409 | Interaction between SMF and I-SMF | Huawei, Hisilicon |
| S2-2503498 | SMF profile enhancement | China Mobile |
| S2-2503499 | Correction of local offloading management | China Mobile |
| S2-2503500 | UE mobility for local offloading management | China Mobile |
| S2-2503614 | Clarification for Local offloading management policy | ZTE |
| S2-2503698 | 23.501 CR6249: Clarification on Local Offloading Management with URSP | Samsung |
| S2-2503699 | Clarification on handling application not matched with LOM policy | Samsung |
| S2-2503700 | Clarification on I-SMF operation for N6 Delay Measurement | Samsung |
| S2-2503850 | Clarifications on I-SMF insertion for PDU Session Mobility | Nokia |
| S2-2503851 | Corrections on Local Offloading Management related indications | Nokia |
| S2-2503920 | Clarification on I-SMF operation for N6 Delay Measurement | Samsung |
| S2-2503921 | KI#1: Clarfication on the I-SMF selected for local offloading managment | Huawei, HiSilicon, Samsung |
| S2-2503922 | Clarification for Local offloading management policy | ZTE |
| S2-2503923 | SMF profile enhancement | China Mobile |
| S2-2503924 | Correction of local offloading management | China Mobile |
| S2-2503925 | UE mobility for local offloading management | China Mobile |
| S2-2503926 | Clarification on Local Offloading Management with URSP | Samsung |
| S2-2503927 | Clarification on handling application not matched with LOM policy | Samsung |
| S2-2503928 | Clarifications on I-SMF insertion for PDU Session Mobility | Nokia |
| S2-2503929 | Interaction between SMF and I-SMF | Huawei, Hisilicon |
| S2-2503930 | Interaction between SMF and I-SMF | Huawei, Hisilicon |
| S2-2504174 | Clarification for Local offloading management policy | ZTE |
| S2-2504175 | Correction of local offloading management | China Mobile |
| S2-2504176 | UE mobility for local offloading management | China Mobile |
| S2-2504177 | Clarification on handling application not matched with LOM policy | Samsung |
| S2-2504178 | Corrections on Local Offloading Management related indications | Nokia |
| S2-2504179 | Interaction between SMF and I-SMF | Huawei, Hisilicon |
| S2-2504180 | Interaction between SMF and I-SMF | Huawei, Hisilicon |
| S2-2504181 | UE mobility for local offloading management | China Mobile |
| S2-2504233 | Clarification for Local offloading management policy | ZTE |
| S2-2504246 | Clarification for Local offloading management policy | ZTE |
| TDoc | Title | Source |
|---|---|---|
| S2-2502810 | LS from CT WG3: Reply LS on Nnef_RetrieveInfoUAVFlight_Get service operation | CT WG3 |
| S2-2502828 | LS from RAN WG3: LS on UAV regulation from RAN3 | RAN WG3 |
| S2-2502937 | Clarification on procedure for instructing aerial UEs for altitude reporting | LG Electronics |
| S2-2502938 | [DRAFT] Reply LS on UAV regulation from RAN WG3 | LG Electronics |
| S2-2502963 | [DRAFT] Reply LS on UAV regulation from RAN WG3 | Ericsson |
| S2-2502964 | Assigned trajectory event for in-flight monitoring | Ericsson |
| S2-2502965 | Updates to Assigned Trajectory Parameters | Ericsson |
| S2-2502966 | Instructing a UAV to stop the altitude reporting | Ericsson |
| S2-2503179 | Altitude reporting update | CATT |
| S2-2503182 | Procedures update | CATT |
| S2-2503441 | [DRAFT] Reply LS on UAV regulation from RAN WG3 | China Mobile Com. Corporation |
| S2-2503643 | Altitude reporting cancellation | CATT |
| S2-2503644 | [DRAFT] Reply LS on UAV regulation from RAN WG3 | CATT |
| S2-2503673 | The indication on altitude thresholds and reporting periodicity for the aerial UE's altitude reporting | China Mobile |
| S2-2504128 | The indication on altitude thresholds and reporting periodicity for the aerial UE's altitude reporting | China Mobile |
| S2-2504129 | Instructing a UAV to stop the altitude reporting | Ericsson, CATT |
| S2-2504130 | Altitude reporting cancellation | CATT, Ericsson |
| S2-2504131 | [DRAFT] Reply LS on UAV regulation from RAN WG3 | China Mobile Com. Corporation |
| S2-2504132 | Assigned trajectory event for in-flight monitoring | Ericsson |
| S2-2504133 | Updates to Assigned Trajectory Parameters | Ericsson |
| S2-2504375 | Instructing a UAV to stop the altitude reporting | Ericsson, CATT |
| S2-2504376 | Altitude reporting cancellation | CATT, Ericsson |
| S2-2504377 | The indication on altitude thresholds and reporting periodicity for the aerial UE's altitude reporting | China Mobile, LG Electronics |
| S2-2504378 | [DRAFT] Reply LS on UAV regulation from RAN WG3 | China Mobile Com. Corporation |
| S2-2504470 | The indication on altitude thresholds and reporting periodicity for the aerial UE's altitude reporting | China Mobile, LG Electronics |
| S2-2504471 | Reply LS on UAV regulation from RAN WG3 | SA WG2 |
| TDoc | Title | Source |
|---|---|---|
| S2-2502955 | Corrections on UPF Event Exposure | Ericsson |
| S2-2503032 | Clarification to usage of operator configurable UPF capabilities in LBO roaming scenarios | Samsung |
| S2-2503034 | Clarification to UPF selection based on specific UPF functionalities | Samsung |
| S2-2503036 | Clarifications to Direct subscription to UPF Events in case of session release or UPF relocation | Samsung |
| S2-2503037 | Correction to direct subscription of UPF event expsoure using UE IP address | Samsung |
| S2-2503822 | An optimized method for AF to obtain the DN-facing UE IP address | CEWiT |
| S2-2504037 | Corrections on UPF Event Exposure | Ericsson |
| S2-2504038 | Clarification to UPF selection based on specific UPF functionalities | Samsung |
| S2-2504039 | Clarifications to Direct subscription to UPF Events in case of session release or UPF relocation | Samsung |
| S2-2504040 | Correction to direct subscription of UPF event expsoure using UE IP address | Samsung |
| S2-2504041 | Clarification to operator configurable UPF capabilities in LBO roaming scenarios | Samsung |
| S2-2504081 | Clarification to UPF selection based on specific UPF functionalities | Samsung |
| S2-2504082 | Correction to direct subscription of UPF event expsoure using UE IP address | Samsung |
| S2-2504083 | Clarifications to Direct subscription to UPF Events in case of session release or UPF relocation | Samsung |
| S2-2504084 | Clarification to operator configurable UPF capabilities in LBO roaming scenarios | Samsung |
| S2-2504085 | Clarification to UPF selection based on specific UPF functionalities | Samsung |
| TDoc | Title | Source |
|---|---|---|
| S2-2502827 | LS from RAN WG3: LS on security verification related to NR Femtos | RAN WG3 |
| S2-2503302 | Clarification on CAG Information Provisioning | LG Electronics |
| S2-2503360 | Removal of event subscription for CAG information provisioning | Samsung |
| S2-2503367 | UDM functional description update for CAG information provisioning | Samsung |
| S2-2503853 | Clarifications on NR Femto node deployments | Nokia |
| S2-2504136 | Clarification on CAG Information Provisioning | LG Electronics |
| S2-2504137 | Removal of event subscription for CAG information provisioning | Samsung |
| S2-2504138 | UDM functional description update for CAG information provisioning | Samsung |
| S2-2504398 | Clarification on CAG Information Provisioning | LG Electronics |
| S2-2504399 | Clarifications on NR Femto node deployments | Nokia |
| TDoc | Title | Source |
|---|---|---|
| S2-2502811 | LS from CT WG4: LS on Ethernet MA PDU session using MPQUIC-E steering | CT WG4 |
| S2-2503020 | Correction for MA PDU Session of type Ethernet with MPQUIC-E steering functionality for Roaming scenarios | Nokia |
| S2-2503021 | LS on Next Generation eCall. | CEN/TC 278/WG 15 eSafety |
| S2-2503022 | [DRAFT] Reply LS on Ethernet MA PDU session using MPQUIC-E steering | Nokia |
| S2-2503038 | Corrections to PDU Session Modification on mobility to 5GS for Ethernet MA PDU Session | Samsung |
| S2-2503039 | [DRAFT] Reply LS on Ethernet MA PDU session using MPQUIC-E steering | Samsung |
| S2-2503040 | Clarification to HR-SBO scenarios for supporting MPQUIC-E | Samsung |
| S2-2503041 | Correct Handling of IP version when MPQUIC-E is enabled | Samsung |
| S2-2503042 | Correct Handling of IP version when MPQUIC-E is enabled | Samsung |
| S2-2503076 | Correction to EPS interworking for MA PDU Session of type Ethernet with MPQUIC-E steering functionality | Nokia |
| S2-2503249 | Discussion on the consideration of IP version of the two MPQUIC link-specific multipath addresses . | China Mobile |
| S2-2503257 | MPQUIC IP-allocation considerations & Some corrections | China Mobile |
| S2-2503258 | MPQUIC IP-allocation considerations & Some corrections | China Mobile |
| S2-2503261 | Handling of MPQUIC-E with EPS interworking | Ericsson |
| S2-2503262 | Handling of MPQUIC-E with EPS interworking | Ericsson |
| S2-2503263 | Handling of MPQUIC-E in roaming cases | Ericsson |
| S2-2503264 | [DRAFT] Reply LS on Ethernet MA PDU session using MPQUIC-E steering | Ericsson |
| S2-2503278 | Clarification on MPQUIC proxy | China Telecom |
| S2-2503297 | Clarification on IP version used for MPQUIC-E | MediaTek Inc. |
| S2-2503303 | Clarification on IP version used for MPQUIC-E | LG Electronics, CableLabs, Apple |
| S2-2503304 | [DRAFT] Reply LS on Ethernet MA PDU session using MPQUIC-E steering | LG Electronics |
| S2-2503305 | Clarification on PDU Session Type setting in case of V/I-SMF | LG Electronics |
| S2-2503307 | Clarification on IP version used for MPQUIC-E | MediaTek Inc. |
| S2-2503309 | Clarification on IP version used for MPQUIC-E in procedure | LG Electronics |
| S2-2503429 | Terminology alignment for steering functionality(ies) | Huawei, HiSilicon |
| S2-2503430 | Clarification on MPQUIC functionality | Huawei, HiSilicon |
| S2-2503431 | Terminology alignment for steering functionality(ies) | Huawei, HiSilicon |
| S2-2503432 | [DRAFT] LS on Ethernet MA PDU session using MPQUIC-E functionality | Huawei, HiSilicon |
| S2-2503738 | Clarification on IP version used for MPQUIC-E | LG Electronics, CableLabs, Apple |
| S2-2503751 | IP version used for MPQUIC-E | Ericsson |
| S2-2503752 | IP version used for MPQUIC-E | Ericsson |
| S2-2503889 | Alignment with ATSSS Capability IE | Apple |
| S2-2504353 | Correction for MA PDU Session of type Ethernet with MPQUIC-E steering functionality for Roaming scenarios | Nokia |
| S2-2504354 | Handling of MPQUIC-E with EPS interworking | Ericsson |
| S2-2504355 | Handling of MPQUIC-E with EPS interworking | Ericsson |
| S2-2504356 | [DRAFT] Reply LS on Ethernet MA PDU session using MPQUIC-E steering | Nokia |
| S2-2504357 | Terminology alignment for steering functionality(ies) | Huawei, HiSilicon, ETRI, China Telecom |
| S2-2504358 | Terminology alignment for steering functionality(ies) | Huawei, HiSilicon |
| S2-2504359 | Alignment with ATSSS Capability IE | Apple |
| S2-2504360 | Corrections to PDU Session Modification on mobility to 5GS for Ethernet MA PDU Session | Samsung |
| S2-2504361 | IP version used for MPQUIC-E | Ericsson, LG Electronics, CableLabs, Mediatek |
| S2-2504362 | MPQUIC IP-allocation considerations & Some corrections | China Mobile |
| S2-2504387 | IP version used for MPQUIC-E | Ericsson |
| S2-2504406 | IP version used for MPQUIC-E | Ericsson, LG Electronics, CableLabs, MediaTek Inc., Apple, China Mobile, Nokia, CATT, Samsung, Deutsche Telekom |
| S2-2504407 | IP version used for MPQUIC-E | Ericsson, LGE, CATT, Mediatek?, China Mobile, Nokia, Apple |
| S2-2504408 | IP version used for MPQUIC-E | Ericsson, LG Electronics, CATT, MediaTek Inc., China Mobile, Nokia, Apple, Samsung, CableLabs, Deutsche Telekom |
| S2-2504409 | MPQUIC IP-allocation considerations & Some corrections | China Mobile |
| TDoc | Title | Source |
|---|---|---|
| S2-2502799 | LS from SA WG3: Reply LS on security aspects of Ambient IoT | SA WG3 |
| S2-2502832 | LS from RAN WG3: LS on Ambient IoT progress of RAN WG3 | RAN WG3 |
| S2-2502835 | LS from SA WG3: Reply LS on Device Subscription Data | SA WG3 |
| S2-2502839 | LS from SA WG5: Reply to LS on A-IoT Conclusions in SA WG2 | SA WG5 |
| S2-2502939 | Clause 5.4 updates. | LG Electronics |
| S2-2503002 | Addressing EN: AF authorization for Ambient IoT. | Lenovo |
| S2-2503003 | NF descriptions update for AIOTF and NRF. | Lenovo, China Telecom |
| S2-2503004 | Update for Command Procedure: Command failure handling. | Lenovo, China Telecom |
| S2-2503009 | Update on Inventory procedure. | CATT |
| S2-2503010 | Update on Command procedure. | CATT |
| S2-2503011 | AIOTF selection and AMF selection. | CATT |
| S2-2503012 | AIoT Reader Selection update. | CATT |
| S2-2503013 | Resolve EN on AF authorization. | CATT |
| S2-2503043 | Structure for documenting indirect path and Direct path. | OPPO |
| S2-2503044 | Update on NF description. | OPPO |
| S2-2503045 | Update on the Aggregation in the Inventory and Command procedure. | OPPO |
| S2-2503046 | Update on AIoT Device ID information. | OPPO |
| S2-2503047 | EN resolution on AIoT data. | OPPO |
| S2-2503048 | EN Resolution and Clarification in Inventory Procedure. | OPPO |
| S2-2503049 | Resolving the EN on AIoT RAN Reader and AMF selection. | OPPO |
| S2-2503050 | Update on Description for Protocol Stack. | OPPO |
| S2-2503106 | [DRAFT] LS Reply on Ambient IoT progress of RAN WG3 | NEC |
| S2-2503108 | AIoT device priority as AIoT Assistance information. | NEC |
| S2-2503109 | AIoT Scope and Architecture General concept clarifications. | NEC |
| S2-2503149 | Update AIoT Inventory procedure for Command . | Ofinno |
| S2-2503150 | [DRAFT] LS on Ambient IoT | vivo |
| S2-2503151 | Non-Operation Related Procedure . | Vivo |
| S2-2503152 | PCR to TS 23.xyz: Filtering Information. | Vivo |
| S2-2503153 | AIOTF/AMF selection and NF profile. | Vivo |
| S2-2503154 | Update to inventory procedure. | Vivo |
| S2-2503155 | Update to command procedure. | Vivo |
| S2-2503156 | Update to NF Services. | Vivo |
| S2-2503157 | Update to Network Functions. | Vivo |
| S2-2503161 | Update Assistance information for Inventory procedure . | Ofinno |
| S2-2503163 | [DRAFT] LS on Assistance information for follow-up Command procedure | Ofinno, LLC |
| S2-2503195 | Clause 5.X: ADM Discovery and Selection. | Ericsson |
| S2-2503196 | Clause 5.6 & 6.2.2 & 6.2.3: Resolve EN on AF Authorization. | Ericsson |
| S2-2503197 | Clause 5.X & 6.2.2 & 6.2.3: AIOTF Discovery and Selection. | Ericsson |
| S2-2503198 | Clause 4.6: Protocol Stack Update. | Ericsson |
| S2-2503199 | Clause 4.2.2 & 4.3: Reference Point Definition. | Ericsson |
| S2-2503200 | Terminology Alignment. | Ericsson, Huawei, HiSilicon |
| S2-2503201 | [DRAFT] LS on Assistance Information for Subsequent Command | Ericsson |
| S2-2503378 | AIoT RAN Connectivity. | Samsung |
| S2-2503379 | AIoT Device. | Samsung |
| S2-2503380 | Command Type AIoT data. | Samsung |
| S2-2503381 | Assistance Information. | Samsung |
| S2-2503382 | Command Procedure Update. | Samsung |
| S2-2503384 | AIoT Readers. | Samsung |
| S2-2503385 | AIoT Reader Selection. | Samsung |
| S2-2503387 | Inventory Procedure Update. | Samsung |
| S2-2503388 | AF Authorization. | Samsung |
| S2-2503390 | Reference Points. | Samsung |
| S2-2503394 | Reference Points and SBIs for Ambient IoT | Samsung |
| S2-2503442 | Discussion on assistance information to support command. | NTT DOCOMO, T-Mobile USA |
| S2-2503466 | Text on assistance information to support command procedure. | NTT DOCOMO, T-Mobile USA |
| S2-2503469 | Updates to call flows to support command. | NTT DOCOMO, T-Mobile USA |
| S2-2503471 | Update Inventory Procedure. | Sony |
| S2-2503472 | Update Command Procedure. | Sony |
| S2-2503473 | Text on AIoT Device capabilities. | NTT DOCOMO |
| S2-2503475 | PCR for TS 23.369: AIoT Reader Selection. | China Mobile |
| S2-2503476 | AIoT Reader Selection discussion | China Mobile Com. Corporation |
| S2-2503477 | PCR for TS 23.369: update on Assistance information provided to AIoT RAN Node. | China Mobile |
| S2-2503496 | [DRAFT] LS Reply on Ambient IoT progress of RAN WG3 | China Mobile Com. Corporation |
| S2-2503502 | PCR to TS 23.369 on aggregation aspects. | NTT DOCOMO |
| S2-2503527 | Updates on AF authorization . | Nokia |
| S2-2503549 | Updates on aggregation . | Nokia |
| S2-2503609 | Update to clause 5.7 Identifiers. | HONOR |
| S2-2503649 | Discussion on Nx reference point interface between AIOTF and AIoT RAN. | Tejas Networks |
| S2-2503670 | ADM selection and related update. | Vivo |
| S2-2503686 | PCR to TS 23.369: AIoT Service Operation Result Aggregation. | ZTE |
| S2-2503687 | PCR to TS 23.369: Clarification on AIoT Device Profile Data. | ZTE |
| S2-2503688 | PCR to TS 23.369: Address EN for AIoT Reader Control Transportation. | ZTE |
| S2-2503689 | PCR to TS 23.369: Clarification on AIoT Procedure. | ZTE |
| S2-2503690 | PCR to TS 23.369: AIOTF and NEF Service Definition Update. | ZTE |
| S2-2503691 | [DRAFT] LS on Command Indication in Inventory Request | ZTE |
| S2-2503692 | PCR to TS 23.369: Address EN for AIoT Reader Selection. | ZTE |
| S2-2503696 | Update for AIoT Service Procedures. | China Mobile |
| S2-2503703 | Update for Functional Entities. | China Mobile |
| S2-2503791 | AIoT Device Information Configure Service. | InterDigital Inc., Lenovo |
| S2-2503792 | Update to Inventory procedure regarding AIOTF selection . | InterDigital Inc. |
| S2-2503793 | Update to Command procedure. | InterDigital Inc. |
| S2-2503794 | [DRAFT] LS on the need of indication of follow-up Command procedure in Inventory request | InterDigital Inc. |
| S2-2503833 | PCR for TS 23.369: Clarification on Assistance Information. | Huawei, HiSilicon |
| S2-2503834 | PCR for TS 23.369: Update Inventory Procedure. | Huawei, HiSilicon |
| S2-2503835 | PCR for TS 23.369: Update Command Procedure. | Huawei, HiSilicon |
| S2-2503836 | PCR for TS 23.369: Improve AIoT NF Services. | Huawei, HiSilicon |
| S2-2503837 | PCR for TS 23.369: Support of AIoT Device Context Management. | Huawei, HiSilicon |
| S2-2503838 | PCR for TS 23.369: AIoT Reader Selection. | Huawei, HiSilicon |
| S2-2503839 | PCR for TS 23.369: Protocol Stack Update. | Huawei, HiSilicon |
| S2-2503840 | PCR for TS 23.369: Address ENs for AF authorization. | Huawei, HiSilicon |
| S2-2503841 | PCR for TS 23.369: Improve AIoT Device Profile Management. | Huawei, HiSilicon |
| S2-2503842 | Ambient IoT interfaces and reference points | Huawei, HiSilicon |
| S2-2503843 | Discussion on RAN Procedure Interactions. | Huawei, HiSilicon |
| S2-2503845 | PCR for TS 23.369: Update of Device ID for NID. | Huawei, HiSilicon |
| S2-2503846 | PCR for TS 23.369: Procedure for AIOTF and AIoT Reader Communication. | Huawei, HiSilicon |
| S2-2503847 | PCR for TS 23.369: Support of AIoT Device Temporary ID. | Huawei, HiSilicon |
| S2-2503848 | PCR for TS 23.369: AIoT Reference Point Naming . | Huawei, HiSilicon |
| S2-2503849 | [DRAFT] LS on AIoT device identifier length | Huawei, HiSilicon |
| S2-2503857 | PCR to TS 23.369: AIoT Reader selection . | Lenovo |
| S2-2503874 | AIOTF selection. | Samsung |
| S2-2504011 | Terminology Alignment. | Ericsson, Huawei, HiSilicon, OPPO |
| S2-2504012 | PCR for TS 23.369: AIoT Reference Point Naming . | Huawei, HiSilicon, Ericsson |
| S2-2504013 | Clause 4.2.2 & 4.3: Reference Point Definition. | Ericsson, Tejas Networks, CEWiT, Samsung |
| S2-2504014 | Reference Points and SBIs for Ambient IoT | Samsung, Huawei |
| S2-2504015 | PCR for TS 23.369: AIoT Reader Selection. | China Mobile, ZTE, Futurewei |
| S2-2504016 | AIOTF selection. | CATT |
| S2-2504017 | AMF selection. | Vivo |
| S2-2504018 | Update to Inventory procedure regarding AIOTF selection . | InterDigital Inc. |
| S2-2504019 | Clause 5.X: ADM Discovery and Selection. | Ericsson |
| S2-2504020 | Clause 5.4 updates. | LG Electronics, Futurewei, NTT DOCOMO, InterDigital, Ericsson, ZTE, Lenovo, OPPO, CATT, Huawei, Nokia, MediaTek Inc. |
| S2-2504021 | [DRAFT] LS on the need of indication of follow-up Command procedure in Inventory request | InterDigital Inc. |
| S2-2504058 | PCR for TS 23.369: Improve AIoT Device Profile Management. | Huawei, HiSilicon, Samsung |
| S2-2504059 | Clause 5.6 & 6.2.2 & 6.2.3: Resolve EN on AF Authorization. | Ericsson |
| S2-2504060 | PCR for TS 23.369: Update of Device ID for NID. | Huawei, HiSilicon |
| S2-2504061 | [DRAFT] LS on AIoT device identifier length | Huawei, HiSilicon |
| S2-2504062 | PCR to TS 23.xyz: Filtering Information. | Vivo, Futurewei |
| S2-2504063 | Structure for documenting indirect path and Direct path. | OPPO |
| S2-2504064 | PCR for TS 23.369: Update Inventory Procedure. | Huawei, HiSilicon |
| S2-2504065 | Command Type AIoT data. | Samsung, Futurewei |
| S2-2504066 | Update on Command procedure. | CATT, Lenovo?, vivo?, Samsung, NTT DOCOMO INC.? Sony? Huawei?, InterDigital Inc., OPPO |
| S2-2504067 | NF descriptions update for AIOTF and NRF. | Lenovo, China Telecom, NTT DOCOMO, Futurewei, Nokia |
| S2-2504270 | PCR for TS 23.369: AIoT Reader Selection. | China Mobile, ZTE, Futurewei, Samsung |
| S2-2504271 | [DRAFT] LS Reply on Ambient IoT progress of RAN WG3 | NEC |
| S2-2504272 | AMF selection. | Vivo, Samsung |
| S2-2504273 | [DRAFT] LS Reply on Ambient IoT progress of RAN WG3 | NEC |
| S2-2504274 | AIOTF selection. | CATT, Samsung |
| S2-2504275 | Clause 5.X: ADM Discovery and Selection. | Ericsson, Vivo |
| S2-2504276 | Update to Inventory procedure regarding AIOTF selection . | InterDigital Inc. |
| S2-2504277 | Clause 5.4 updates. | LG Electronics, Futurewei, NTT DOCOMO, InterDigital, Ericsson, ZTE, Lenovo, OPPO, CATT, Huawei, Nokia, MediaTek Inc., vivo, Samsung, CEWiT, NEC |
| S2-2504278 | [DRAFT] LS on the need of indication of follow-up Command procedure in Inventory request | InterDigital Inc. |
| S2-2504279 | PCR for TS 23.369: Improve AIoT Device Profile Management. | Huawei, HiSilicon, Samsung |
| S2-2504280 | Clause 5.6 & 6.2.2 & 6.2.3: Resolve EN on AF Authorization. | Ericsson, Huawei, HiSilicon |
| S2-2504281 | PCR for TS 23.369: Update of Device ID for NID. | Huawei, HiSilicon |
| S2-2504282 | [DRAFT] LS on AIoT device identifier length | Huawei, HiSilicon |
| S2-2504283 | PCR to TS 23.xyz: Filtering Information. | Vivo, Futurewei |
| S2-2504284 | PCR for TS 23.369: Update Inventory Procedure. | Huawei, HiSilicon |
| S2-2504285 | Command Type AIoT data. | Samsung, Futurewei |
| S2-2504286 | Update on Command procedure. | CATT, Lenovo, vivo, Samsung, NTT DOCOMO INC., Sony, Huawei, InterDigital Inc., OPPO |
| S2-2504287 | NF descriptions update for AIOTF and NRF. | Lenovo, China Telecom, NTT DOCOMO, Futurewei, Nokia |
| S2-2504288 | LS Reply on Ambient IoT progress of RAN WG3 | SA WG2 |
| S2-2504289 | PCR for TS 23.369: AIoT Reader Selection. | China Mobile, ZTE, Futurewei, Samsung, Lenovo, Interdigital, CATT, NEC |
| S2-2504290 | AMF selection. | Vivo, Samsung |
| S2-2504291 | AIOTF selection. | CATT, Samsung, Ericsson, Lenovo, vivo |
| S2-2504292 | Update to Inventory procedure regarding AIOTF selection . | InterDigital Inc. |
| S2-2504293 | Clause 5.4 updates. | LG Electronics, Futurewei, NTT DOCOMO, InterDigital, Ericsson, ZTE, Lenovo, OPPO, CATT, Huawei, Nokia, MediaTek Inc., vivo, Samsung, CEWiT, NEC |
| S2-2504294 | LS on the need of indication of follow-up Command procedure in Inventory request | SA WG2 |
| S2-2504295 | PCR for TS 23.369: Improve AIoT Device Profile Management. | Huawei, HiSilicon, Samsung |
| S2-2504296 | LS on AIoT device identifier length | SA WG2 |
| S2-2504318 | PCR for TS 23.369: Update Inventory Procedure. | Huawei, HiSilicon, CATT, OPPO |
| S2-2504319 | Terminology Alignment. | Ericsson, Huawei, HiSilicon, OPPO, Deutsche Telekom |
| S2-2504320 | Clause 5.4 updates. | LG Electronics, Futurewei, NTT DOCOMO, InterDigital, Ericsson, ZTE, Lenovo, OPPO, CATT, Huawei, Nokia, MediaTek Inc., vivo, Samsung, CEWiT, NEC, China Mobile |
| S2-2504321 | PCR for TS 23.369: Improve AIoT Device Profile Management. | Huawei, HiSilicon, Samsung |
| TDoc | Title | Source |
|---|---|---|
| S2-2502792 | 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 |
| S2-2502793 | LS from RAN WG1: LS on signalling feasibility of dataset and parameter sharing | RAN WG1 |
| S2-2502802 | LS from RAN WG2: Reply LS to SA WG2 on LMF-based AI/ML Positioning for Case 2b | RAN WG2 |
| S2-2502816 | LS from CT WG4: LS on Questions on stage 2 requirements for AIML_CN | CT WG4 |
| S2-2502818 | LS from RAN WG1: Reply LS on LMF-based AI/ML Positioning for Case 2b | RAN WG1 |
| S2-2502819 | LS from RAN WG1: Reply LS on LMF-based AI/ML Positioning for Case 3b | RAN WG1 |
| S2-2502826 | LS from RAN WG3: Reply LS on LMF-based AI/ML Positioning for case 3b | RAN WG3 |
| S2-2502840 | LS from SA WG5: Reply LS on ML Model provisioning by OAM to LMF for UE positioning | SA WG5 |
| S2-2502841 | LS from SA WG5: Reply LS on AI/ML UE sided data collection | SA WG5 |
| S2-2502857 | [DRAFT] Reply LS on ML Model provisioning by OAM to LMF for UE positioning | ZTE |
| S2-2502858 | LMF re-selection based on AI capability | ZTE |
| S2-2502859 | Clarifications on the time interval supporting VFL | ZTE |
| S2-2502860 | Clarifications on VFL inference | ZTE |
| S2-2502861 | General maintenance of KI#1 | ZTE |
| S2-2502862 | General maintenance of KI#4 | ZTE |
| S2-2502863 | Optimization of VFL triggers | ZTE, Huawei, Hisilicon, vivo, OPPO |
| S2-2502864 | Output parameters clarifications in KI#3 | ZTE |
| S2-2502865 | VFL clients removal during VFL training | ZTE |
| S2-2502866 | VFL high level description refinements | ZTE |
| S2-2502867 | LMF re-selection based on AI capability | ZTE |
| S2-2502868 | LMF re-selection based on AI capability | ZTE |
| S2-2502899 | KI#1: Considering RAN load when collecting data to train model for positioning | Nokia |
| S2-2502931 | Removal of requirements related to case 2b | Vivo |
| S2-2502932 | Removal of requirements related to case 2b | Vivo, Xiaomi, ZTE, OPPO, Mediatek Inc., Samsung, Nokia |
| S2-2502933 | Update on input data collection by NWDAF for LMF-based AIML positioning | ETRI |
| S2-2502934 | Corrections on input data for QoS and policy assistance analytics | ETRI |
| S2-2502947 | Changes on user consent and privacy for AIML-based positioning | Apple |
| S2-2502948 | Remaining aspects on user consent and privacy for AI/ML-based positioning . | Apple |
| S2-2503030 | Remove EN on LMF's consideration of RAN load | Samsung |
| S2-2503110 | ML Model provisioning by OAM for LMF-based AI/ML Positioning | NTT DOCOMO, Ericsson |
| S2-2503111 | Exposure of control plane signalling information from NFs | NTT DOCOMO |
| S2-2503119 | Correction of NF Signalling Information for Signalling Storm Analytics | NTT DOCOMO |
| S2-2503130 | Alignment of existing mechanisms for accuracy generation impacted by VFL procedures | Huawei, HiSilicon, ZTE |
| S2-2503131 | Clarification on registration and discovery for VFL | Huawei, HiSilicon |
| S2-2503134 | Correction on usage of signalling storm analytics for reliability of NF services | Huawei, HiSilicon |
| S2-2503135 | Clarifying Signalling Storm Analytics | Huawei, HiSilicon |
| S2-2503136 | Adding SCP as data source for NWDAF data collection | Huawei, HiSilicon |
| S2-2503190 | LMF checking LCS privacy profile before collecting input data and ground truth | Ericsson, AT&T |
| S2-2503191 | Resolution of Editor s Note based on RAN WG1 and RAN 3 LS replies. | Ericsson |
| S2-2503193 | Update triggering Case A and some corrections and Resolving ENs for VFL | Ericsson, China Telecom |
| S2-2503194 | Selection of aggregating client in VFL | Ericsson |
| S2-2503215 | Discussion on UE LCS privacy check for ground truth data collection and input data storage for ML model training for AI/ML positioning . | Intel |
| S2-2503216 | UE LCS privacy check for ground truth data collection and input data storage for ML model training for AI/ML positioning | Intel |
| S2-2503217 | UE LCS privacy check for ground truth data collection | Intel |
| S2-2503218 | Input data storage in ADRF for ML model training for AI/ML positioning | Intel |
| S2-2503219 | Update ADRF service consumer to include LMF | Intel |
| S2-2503227 | [DRAFT] Reply LS on ML Model provisioning by OAM to LMF for UE positioning | Nokia |
| S2-2503229 | KI#1: ML Model training by OAM for LMF models for UE positioning | Nokia |
| S2-2503233 | Parameters from Analytics Request also required for VFL inference | Nokia |
| S2-2503234 | Parameters for vertical federated learning inference procedure | Nokia |
| S2-2503235 | Parameters for vertical federated learning inference procedure | Nokia |
| S2-2503237 | Correcting triggers for VFL training | Nokia |
| S2-2503240 | Correcting procedures for Exchanging intermediate results between VFL clients | Nokia |
| S2-2503242 | KI#2: VFL services | Nokia |
| S2-2503248 | [DRAFT] Reply LS on Questions on stage 2 requirements for AIML_CN | Nokia |
| S2-2503250 | Updates on VFL inference | Interdigital |
| S2-2503251 | Update on VFL training | Interdigital |
| S2-2503252 | Updates on VFL preparation | Interdigital |
| S2-2503253 | AIML_CN KI#4 Resolve issues for event exposure and for SCP mitigation actions | Nokia |
| S2-2503255 | AIML_CN KI#4 Resolve issues for event exposure | Nokia |
| S2-2503282 | CR for 23.501 AIML_CN SCP related alignment | Vivo |
| S2-2503283 | [DRAFT] Reply LS on Questions on stage 2 requirements for AIML_CN | vivo |
| S2-2503319 | Editor s Note clean up for the VFL | OPPO |
| S2-2503340 | [DRAFT] Reply LS on ML Model provisioning by OAM to LMF for UE positioning | Huawei, HiSilicon |
| S2-2503341 | Update of ML model retrieval from OAM | Huawei, HiSilicon |
| S2-2503342 | Update of input data and procedure for LMF-based AIML positioning | Huawei, HiSilicon |
| S2-2503343 | Update the procedure of data collection from NG-RAN | Huawei, HiSilicon |
| S2-2503344 | Updates of NWDAF discovery and ML model provisioning for LMF-based AI/ML Positioning | Huawei, HiSilicon |
| S2-2503345 | Corrections of LMF-based AI/ML positioning indication | Huawei, HiSilicon |
| S2-2503347 | Correction on VFL correlation ID handling | Huawei, HiSilicon |
| S2-2503348 | Update to VFL preparation procedure | Huawei, HiSilicon |
| S2-2503349 | Update the inference service for VFL | Huawei, HiSilicon |
| S2-2503365 | Update and Resolve ENs for VFL Training Procedure | LG Electronics |
| S2-2503366 | Clarification on Aggregator NWDAF Client Selection | LG Electronics |
| S2-2503368 | Clarification on Signalling Storm Analytics | LG Electronics |
| S2-2503410 | Enhancements on the input and output of QoS and Policy Assistance Analytics | China Mobile |
| S2-2503411 | NF discovery for signaling data collection related to signaling storm analytics | China Mobile |
| S2-2503535 | Address ENs for AI positioning case 3b | Vivo |
| S2-2503536 | Clarification on VFL Server registration & discovery | Vivo |
| S2-2503537 | Clarification on VFL inference | Vivo |
| S2-2503538 | Clarification on VFL training | Vivo |
| S2-2503564 | Resolve ENs on input data for LMF based AI/ML positioning | CATT |
| S2-2503565 | Further corrections on QoS and policy assistance analytics | CATT |
| S2-2503577 | Addition of NOTE to user consent purpose | Apple |
| S2-2503598 | Clarification on privacy check for data collection | Xiaomi |
| S2-2503663 | Discussion of the user consent and UE LCS privacy check for AI/ML based positioning. | Qualcomm Incorporated, Xiaomi |
| S2-2503665 | UE LCS privacy check for AI/ML based positioning | Qualcomm Incorporated |
| S2-2503668 | UE LCS privacy check for AI/ML based positioning | Qualcomm Incorporated |
| S2-2503674 | Removal the AI/ML based positioning for case 2b | Qualcomm Incorporated |
| S2-2503693 | Removal the EN about LMF taking into account RAN load | Qualcomm Incorporated |
| S2-2503718 | Maintenance of VFL model training and inference with client intermediate results sharing between VFL clients | Samsung |
| S2-2503963 | [DRAFT] Reply LS on ML Model provisioning by OAM to LMF for UE positioning | ZTE |
| S2-2503964 | ML Model provisioning by OAM for LMF-based AI/ML Positioning | NTT DOCOMO, Ericsson, Nokia, Huawei, HiSilicon |
| S2-2503965 | Changes on user consent and privacy for AIML-based positioning | Apple, Xiaomi |
| S2-2503966 | UE LCS privacy check for AI/ML based positioning | Qualcomm Incorporated |
| S2-2503967 | Removal of requirements related to case 2b | Vivo, Xiaomi, ZTE, OPPO, Mediatek Inc., Samsung, Nokia, CATT |
| S2-2503968 | Resolve ENs on input data for LMF based AI/ML positioning | CATT, Ericsson, vivo |
| S2-2503969 | Editor s Note clean up for the VFL | OPPO |
| S2-2503970 | Optimization of VFL triggers | ZTE, Huawei, Hisilicon, vivo, OPPO, Nokia, Futurewei, Samsung, China Mobile, Interdigital |
| S2-2503971 | Update triggering Case A and some corrections and Resolving ENs for VFL | Ericsson, China Telecom, ZTE |
| S2-2503972 | Alignment of existing mechanisms for accuracy generation impacted by VFL procedures | Huawei, HiSilicon, ZTE |
| S2-2503973 | Parameters for vertical federated learning inference procedure | Nokia, Vivo, Huawei |
| S2-2503974 | Updates on VFL inference | Interdigital, Samsung |
| S2-2503975 | Clarification on Aggregator NWDAF Client Selection | LG Electronics |
| S2-2503976 | Maintenance of VFL model training and inference with client intermediate results sharing between VFL clients | Samsung, ZTE, Nokia, OPPO, LG Electronics, Ericsson |
| S2-2503977 | Enhancements on the input and output of QoS and Policy Assistance Analytics | China Mobile, ETRI |
| S2-2504172 | UE LCS privacy check for ground truth data collection and input data storage for ML model training for AI/ML positioning | Intel |
| S2-2504197 | Reply LS on ML Model provisioning by OAM to LMF for UE positioning | SA WG2 |
| S2-2504198 | ML Model provisioning by OAM for LMF-based AI/ML Positioning | NTT DOCOMO, Ericsson, Nokia, Huawei, HiSilicon |
| S2-2504199 | AIML_CN KI#1: Status and proposal on user consent and privacy profile | Apple |
| S2-2504200 | Removal of requirements related to case 2b | Vivo, Xiaomi, ZTE, OPPO, Mediatek Inc., Samsung, Nokia, CATT, Ericsson, Qualcomm Incorporated, Huawei, HiSilicon, ERTI |
| S2-2504201 | Resolve ENs on input data for LMF based AI/ML positioning | CATT, Ericsson, vivo, Huawei, HiSilicon |
| S2-2504202 | Editor s Note clean up for the VFL | OPPO, Nokia |
| S2-2504215 | Optimization of VFL triggers | ZTE, Huawei, Hisilicon, vivo, OPPO, Nokia, Futurewei, Samsung, China Mobile, Interdigital |
| S2-2504216 | Parameters for vertical federated learning inference procedure | Nokia, Vivo, Huawei, Oppo, Samsung |
| S2-2504217 | Updates on VFL inference | Interdigital, Samsung |
| S2-2504218 | Maintenance of VFL model training and inference with client intermediate results sharing between VFL clients | Samsung, ZTE, Nokia, OPPO, LG Electronics, Ericsson |
| S2-2504219 | Enhancements on the input and output of QoS and Policy Assistance Analytics | China Mobile, ETRI, Samsung, Huawei |
| S2-2504220 | Update triggering Case A and some corrections and Resolving ENs for VFL | Ericsson, China Telecom, ZTE |
| S2-2504221 | Optimization of VFL triggers | ZTE, Huawei, Hisilicon, vivo, OPPO, Nokia, Futurewei, Samsung, China Mobile, Interdigital |
| S2-2504243 | Inclusion of several Non-3GPP Device Identifiers | Nokia, InterDigital Inc., LG Electronics, Samsung, ZTE, Xiaomi |
| S2-2504476 | Updates on VFL inference | Interdigital, Samsung |
| TDoc | Title | Source |
|---|---|---|
| S2-2503057 | Clarification on Indirect Network Sharing | China Unicom |
| S2-2503876 | Missing PLMN ID definition in GUAMI. | Samsung |
| S2-2504135 | Missing PLMN ID definition in GUAMI. | Samsung |
| S2-2504400 | Missing PLMN ID definition in GUAMI. | Samsung |
| TDoc | Title | Source |
|---|---|---|
| S2-2502808 | LS from CT WG3: LS on AF requested network slice replacement | CT WG3 |
| S2-2502922 | Support for Network initiated Slice Replacement Termination | Ericsson |
| S2-2503126 | [DRAFT] LS reply on AF requested network slice replacement | Huawei, HiSilicon |
| S2-2503127 | Clarification on AF requested network slice replacement | Huawei, HiSilicon |
| S2-2503128 | Clarification on AF requested network slice replacement | Huawei, HiSilicon |
| S2-2503187 | Removal of EN about Configured NSSAI | Nokia |
| S2-2503202 | Feature interaction resolution | Nokia |
| S2-2503204 | On the termination of slice replacement | Nokia |
| S2-2503205 | Clarification of Nnef_AMFInfluence based approach to AF requested network slice replacement | Nokia |
| S2-2503618 | Clarification on notifying the outcome of network slice replacement to AF | ZTE |
| S2-2503619 | [DRAFT] LS Response on AF requested network slice replacement | ZTE |
| S2-2503672 | [DRAFT] Reply LS on AF requested network slice replacement | Samsung |
| S2-2503676 | Discussion on removal of Replaced S-NSSAI from Configured NSSAI for AF triggered slice replacement. | Samsung |
| S2-2503694 | Addressing EN for AF requested slice selection | Samsung, LG Electronics |
| S2-2504146 | Clarification on notifying the outcome of network slice replacement to AF | ZTE |
| S2-2504147 | LS Response on AF requested network slice replacement | SA WG2 |
| S2-2504148 | Support for Network initiated Slice Replacement Termination | Ericsson |
| S2-2504149 | On the termination of slice replacement | Nokia |
| S2-2504150 | Clarification of Nnef_AMFInfluence based approach to AF requested network slice replacement | Nokia |
| S2-2504151 | Clarification on AF requested network slice replacement | Huawei, HiSilicon |
| S2-2504152 | Feature interaction resolution | Nokia |
| S2-2504370 | Clarification on AF requested network slice replacement | Huawei, HiSilicon |
| S2-2504402 | On the termination of slice replacement | Nokia |
| S2-2504403 | Clarification of Nnef_AMFInfluence based approach to AF requested network slice replacement | Nokia |
| S2-2504404 | Clarification on AF requested network slice replacement | Huawei, HiSilicon |
| S2-2504405 | Feature interaction resolution | Nokia |
| S2-2504467 | On the termination of slice replacement | Nokia |
| S2-2504478 | Clarification on AF requested network slice replacement | Huawei, HiSilicon |
| TDoc | Title | Source |
|---|---|---|
| S2-2502821 | LS from RAN WG2: Reply LS on LP-WUS subgrouping | RAN WG2 |
| S2-2502969 | Clarification of eDRX application with emergency service | Ericsson, AT&T, Qualcomm Incorporated |
| S2-2502970 | Clarification of eDRX application with emergency service | Ericsson, AT&T, Qualcomm Incorporated |
| S2-2502971 | Clarification of eDRX application with emergency service | Ericsson, AT&T, Qualcomm Incorporated |
| S2-2502972 | Clarification on emergency PDU session release | Ericsson, AT&T, Qualcomm Incorporated, MediaTek Inc |
| S2-2502973 | Clarification on emergency PDU session release | Ericsson, AT&T, Qualcomm Incorporated, MediaTek Inc |
| S2-2502974 | Clarification on emergency PDU session release | Ericsson, AT&T, Qualcomm Incorporated, MediaTek Inc |
| S2-2503333 | CHF Group ID in the needed contexts | Nokia |
| S2-2503667 | Multi-RAN-vendor support for paging of LP-WUS UEs | Vodafone |
| S2-2503831 | PSAP emergency callback interaction with PSM | Vodafone |
| S2-2503854 | Correction of PSAP call-back terminology | Vodafone |
| S2-2504099 | Clarification of eDRX application with emergency service | Ericsson, AT&T, Qualcomm Incorporated |
| S2-2504100 | Clarification on emergency PDU session release | Ericsson, AT&T, Qualcomm Incorporated, MediaTek Inc |
| S2-2504112 | Correction of PSAP call-back terminology | Vodafone |
| S2-2504113 | CHF Group ID in the needed contexts | Nokia |
| S2-2504412 | PSAP emergency callback interaction with PSM | Vodafone |
| S2-2504413 | CHF Group ID in the needed contexts | Nokia |
| TDoc | Title | Source |
|---|---|---|
| S2-2503019 | New solution of IMS call setup procedure simplification for WT#1 GEO voice support. | OPPO |
| S2-2503077 | FS_5GSAT_Ph4_ARC Key issues for WT#1: Support of IMS voice over GEO NB-IoT NTN connecting to EPC. | Nokia |
| S2-2503078 | FS_5GSAT_Ph4_ARC Key issue for WT#2: UE-SAT-UE communication enhancement for NR NTN NGSO constellation with feeder link available. | Nokia |
| S2-2503080 | FS_5GSAT_Ph4_ARC Architecture Assumptions. | Nokia |
| S2-2503165 | Key issue for WT#1: Support of IMS voice over GEO NB-IoT NTN connecting to EPC. | Samsung |
| S2-2503166 | Key issue for WT#2: UE-SAT-UE communication enhancement for NR NTN NGSO constellation with feeder link available. | Samsung |
| S2-2503220 | WT1: Solution for providing IMS voice over GEO via Control Plane. | Qualcomm Incorporated |
| S2-2503221 | WT1: Solution for providing IMS voice over GEO via User Plane. | Qualcomm Incorporated |
| S2-2503232 | WT1:Architecture assumptions for normal IMS voice call over GEO via NB-IoT NTN connecting to EPC. | Qualcomm Incorporated |
| S2-2503269 | Architecture assumptions for IMS voice call over NB-IoT (GEO). | Ericsson |
| S2-2503277 | 23.700-19: Key issues for UE-SAT-UE communication for non-IMS services. | China Telecom |
| S2-2503311 | WT1: Solution for IMS signaling performance optimization to support voice over GEO . | Qualcomm Incorporated |
| S2-2503320 | FS_5GSAT_Ph4_ARC New Key Issue: QoS Support for IMS voice service over GEO satellite. | OPPO |
| S2-2503321 | FS_5GSAT_Ph4_ARC New Key Issue: IMS procedure enhancement and potential optimization for IMS voice over GEO satellite. | OPPO |
| S2-2503346 | KI #1: New Sol: U-plane-based IMS service via NB-IoT access. | Nokia |
| S2-2503362 | Architectural Assumptions. | LG Electronics |
| S2-2503389 | 23.700-19: Key issues for QoS aspect of GEO call. | China Telecom |
| S2-2503468 | 23.700-19: Key issue for WT#2.2: UE-SAT-UE communication via UPF only onboard satellite for non-IMS services. | ETRI |
| S2-2503486 | Discussion paper on CP/UP-based solutions | vivo |
| S2-2503487 | 23.700-19: Architecture principles and assumptions . | Vivo |
| S2-2503488 | FS_5GSAT_Ph4-ARC Key issue on Support of IMS voice over NB-IoT (GEO) satellite access to EPC. | Vivo, MediaTek Inc. |
| S2-2503489 | Solution for UP-based NB-IoT (GEO) supporting IMS voice. | Vivo |
| S2-2503490 | Solution for CP-based NB-IoT (GEO) supporting IMS voice. | Vivo |
| S2-2503491 | Key issue for WT#2.2. | China Mobile |
| S2-2503497 | Emergency Call Optimization and IMS Registration optimization needs to be included in the scope for voice using GEO. | MediaTek Inc. |
| S2-2503501 | KI #X: New Solution: CST reduction by pre-negotiate SDP parameters during SIP registration. | MediaTek Inc. |
| S2-2503504 | KI #X: New Solution: IMS PDN Activation with both default and dedicated EPS bearer contexts. | MediaTek Inc. |
| S2-2503505 | KI #X: New Solution: IMS PDN as first PDN connection. | MediaTek Inc. |
| S2-2503528 | Key issues for WT#1: Support of IMS voice over GEO via NB-IoT NTN connecting to EPC. | Xiaomi |
| S2-2503529 | Architectural Assumptions and Principles for Supporting of IMS voice over GEO NB-IoT NTN connecting to EPC. | Xiaomi |
| S2-2503530 | Key issues for WT#2: Support of UE-SAT-UE communication enhancment. | Xiaomi |
| S2-2503531 | Architectural Assumptions and Principles for UE-SAT-UE communication enhancement. | Xiaomi |
| S2-2503532 | KI#X: New Sol: Support QoS differentiation for CP based IMS voice service over NB-IoT NTN. | Xiaomi |
| S2-2503575 | KI#1: New Sol: Support of CP/UP combination and QoS for IMS voice service over GEO satellite. | NTT DOCOMO |
| S2-2503576 | KI#1: New Sol: Support of capability exchange and NAS timer adjustment for IMS voice service over GEO satellite. | NTT DOCOMO |
| S2-2503584 | 23.700-19: Key Issue on support of 5G-LAN with satellite access. | Vivo |
| S2-2503638 | KI #X: New Solution: CST reduction by pre-negotiate SDP parameters with an early SIP INVITE. | MediaTek Inc. |
| S2-2503657 | [AA] Architecture assumptions. | Huawei, HiSilicon |
| S2-2503658 | [WT1] WT1 Key Issues. | Huawei, HiSilicon |
| S2-2503659 | [WT2] WT2 Key Issues. | Huawei, HiSilicon |
| S2-2503660 | [New Sol] Connection setup for NB-IoT IMS call over GEO. | Huawei, HiSilicon |
| S2-2503741 | FS_5GSAT_Ph4_ARC TR Skeleton. | CATT |
| S2-2503742 | FS_5GSAT_Ph4_ARC TR Scope. | CATT |
| S2-2503743 | FS_5GSAT_Ph4_ARC Architecture Assumptions. | CATT, CSCN |
| S2-2503744 | FS_5GSAT_Ph4_ARC Key issues for WT#1. | CATT, vivo |
| S2-2503745 | FS_5GSAT_Ph4_ARC Key issues for WT#2_2. | CATT, CSCN |
| S2-2503765 | New KI: IMS enhancements and optimizations to support NB-IoT as IP-CAN. | China Mobile |
| S2-2503766 | New KI: Support of UE-SAT-UE communication for roaming case. | China Mobile |
| S2-2503860 | Architectural assumptions and principles for 23.700-19. | TNO |
| S2-2503861 | 23.700-19 Key Issues: UE-SAT-UE communication for non-IMS services. | TNO |
| S2-2503878 | Architectural Assumptions and Principles. | Samsung |
| S2-2503943 | FS_5GSAT_Ph4_ARC TR Skeleton. | CATT |
| S2-2503944 | FS_5GSAT_Ph4_ARC TR Scope. | CATT |
| S2-2503945 | 23.700-19: Architecture principles and assumptions for WT-1 . | Vivo, Qualcomm?, CATT?, CSCN?, Xiaomi?, Ericsson?, Huawei?, HiSilicon?, Nokia?, LG Electronics?, TNO?, Samsung?, Xiaomi? |
| S2-2503946 | [AA] Architecture assumptions. | Huawei, HiSilicon |
| S2-2503947 | 23.700-19: Architecture principles and assumptions for WT-1 . | Vivo, Qualcomm?, CATT?, CSCN?, Xiaomi?, Ericsson?, Huawei?, HiSilicon?, Nokia?, LG Electronics?, TNO?, Samsung?, Xiaomi? |
| S2-2503948 | [AA] Architecture assumptions. | Huawei, HiSilicon |
| S2-2503949 | FS_5GSAT_Ph4_ARC Key issues for WT#1. | CATT, vivo |
| S2-2503950 | Key issue for WT#2: UE-SAT-UE communication enhancement for NR NTN NGSO constellation with feeder link available. | Samsung, ETRI |
| S2-2503951 | New solution of IMS call setup procedure simplification for WT#1 GEO voice support. | OPPO |
| S2-2504185 | FS_5GSAT_Ph4_ARC TR Skeleton. | CATT |
| S2-2504186 | FS_5GSAT_Ph4_ARC TR Scope. | CATT |
| S2-2504187 | 23.700-19: Architecture principles and assumptions for WT-1 . | Vivo, Qualcomm, CATT, CSCN, Xiaomi, Ericsson, Huawei, HiSilicon, Nokia, LG Electronics, TNO, Samsung, OPPO, NTT DOCOMO, China Telecom, |
| S2-2504188 | [AA] Architecture assumptions. | Huawei, HiSilicon, TNO, Samsung |
| S2-2504191 | FS_5GSAT_Ph4_ARC Key issues for WT#1. | CATT, vivo, SAMSUNG |
| S2-2504223 | FS_5GSAT_Ph4_ARC Key issues for WT#1. | CATT, vivo, SAMSUNG, TNO |
| S2-2504224 | Key issue for WT#2: UE-SAT-UE communication enhancement for NR NTN NGSO constellation with feeder link available. | Samsung |
| S2-2504225 | New solution of IMS call setup procedure simplification for WT#1 GEO voice support. | OPPO |
| S2-2504245 | Key issue for WT#2: UE-SAT-UE communication enhancement for NR NTN NGSO constellation with feeder link available. | Samsung, ETRI |
| TDoc | Title | Source |
|---|---|---|
| S2-2502936 | Key issue for WT#5: Sensing Result Exposure. | OPPO |
| S2-2502942 | 23.700-14: Key issue X: Sensing data and the associated information collection and transport. | OPPO |
| S2-2502943 | TR Skeleton for FS_Sensing_ARC | Apple, Xiaomi |
| S2-2502944 | TR Scope for FS_Sensing_ARC . | Apple, Xiaomi |
| S2-2502960 | Adding Architecture assumptions and requirements. | Ericsson |
| S2-2503028 | Architectural Assumptions and Requirements. | LG Electronics |
| S2-2503061 | Key issue for WT#1: Architecture support for Integrated Sensing and Communication. | Vivo |
| S2-2503062 | Key issue for WT#2 Service authorization and revocation. | Vivo |
| S2-2503063 | Key issue for WT#3 Sensing entities discovery and selection. | Vivo |
| S2-2503064 | Architectural Assumptions and Requirements for ISAC. | Vivo |
| S2-2503065 | New solution: Enable the 5GS to support sensing services. | Vivo |
| S2-2503079 | New Key Issue on Sensing Architecture . | Apple |
| S2-2503089 | Key issue for WT#2: Sensing service authurization and revocation. | OPPO |
| S2-2503090 | Key issue for WT#6: Configuration parameters/policy provisioning. | OPPO |
| S2-2503101 | Architecture assumptions and requirements. | OPPO |
| S2-2503143 | Key Issue for WT#3 Discovery and selection . | Sony |
| S2-2503145 | Architectural Assumptions for Sensing. | Ofinno |
| S2-2503146 | Key Issue for WT#6 Configuration parameter provisioning . | Sony |
| S2-2503174 | 23.700-14: Key issue X: Discovery and Selection of Sensing Function. | OPPO |
| S2-2503175 | 23.700-14: Key issue X: Discovery and selection of sensing transmitter and receiver. | OPPO |
| S2-2503176 | 23.700-14: Key issue X: Sensing area authorization. | OPPO |
| S2-2503222 | Architectural Assumptions and Requirements for FS_Sensing. | |
| S2-2503230 | WT-4: KI#X-UE data collection for sensing service. | |
| S2-2503236 | Architectural Assumptions and Principles for ISAC . | InterDigital Inc. |
| S2-2503238 | New KI: KI for WT#1 for architecture support . | InterDigital Inc. |
| S2-2503239 | New KI: KI for WT#2 and WT#5 Service exposure for ISAC . | InterDigital Inc. |
| S2-2503271 | Analysis of issues to be considered for end-to-end sensing service. | China Telecom |
| S2-2503272 | Architectural Assumptions and Requirements for sensing service. | China Telecom |
| S2-2503273 | TR 23.700-14: Key Issue on sensing configuration, authorization and revocation. | China Telecom |
| S2-2503274 | TR 23.700-14: Key Issue on the discovery and selection of sensing entities. | China Telecom |
| S2-2503312 | Key issue for WT#1: Sensing Architecture. | OPPO |
| S2-2503369 | Key issue for WT-1: Architecture and function enhancements to support sensing. | Samsung |
| S2-2503370 | Key issue for WT-2: Service authorization and revocation. | Samsung |
| S2-2503371 | Key issue for WT-3: Discovery and selection of sensing entities . | Samsung |
| S2-2503372 | Key issue for WT-4: Sensing and associated data collection and derive sensing result . | Samsung |
| S2-2503373 | Key issue for WT-5: Mechanisms for providing sensing information and result . | Samsung |
| S2-2503376 | Key issue for WT-6: Configuration parameters/policy provisioning for the support of ISAC services. | Samsung |
| S2-2503413 | Discussion on Architecture Assumption for ISAC study. | China Mobile |
| S2-2503420 | Architectural assumptions and Architectural Requirements. | China Mobile |
| S2-2503421 | Key Issue 1: Architecture and function enhancements. | China Mobile |
| S2-2503422 | Key Issue 4: Sensing data collection and transport. | China Mobile |
| S2-2503423 | Key Issue 5: Sensing result exposure. | China Mobile |
| S2-2503425 | Key Issue 6: Configuration parameters and policy provisioning. | China Mobile |
| S2-2503426 | Key Issue 2: Service authorization and revocation. | China Mobile |
| S2-2503427 | Key Issue 3: Discovery and selection of sensing entities. | China Mobile |
| S2-2503444 | ISAC Architectural Assumptions and Requirements. | ZTE |
| S2-2503445 | Adding Definitions and terminologies. | ZTE |
| S2-2503446 | Key issue#1, Architecture enhancement to support ISAC. | ZTE |
| S2-2503447 | Key issue#2, Sensing Service authorization and parameter/policy provisioning. | ZTE |
| S2-2503448 | Key issue#3, Discovery and selection of sensing entities. | ZTE |
| S2-2503449 | Key issue#4, Sensing data collection and transport. | ZTE |
| S2-2503450 | Key issue#5, Sensing result exposure. | ZTE |
| S2-2503542 | New KI: service authorization and revocation for sensing services . | Lenovo |
| S2-2503543 | New KI: sensing data and associated information collection and transmission. | Lenovo |
| S2-2503544 | New KI: sensing result exposure. | Lenovo |
| S2-2503574 | New Key Issue on Supported Sensing Modes . | Apple |
| S2-2503622 | TR 23.700-14: New key issue for WT-1 Architecture and function enhancements. | ETRI |
| S2-2503623 | TR 23.700-14: New key issue for WT-2 Service authorization and revocation. | ETRI |
| S2-2503624 | TR 23.700-14: New key issue for WT-3 Discovery and selection of sensing entities. | ETRI |
| S2-2503625 | TR 23.700-14: New key issue for WT-4 Sensing data collection and transport. | ETRI |
| S2-2503626 | TR 23.700-14: New key issue for WT-5 Sensing result exposure. | ETRI |
| S2-2503640 | 23.700-14: New KI for FS_Sensing_ARC WT#1. | CATT |
| S2-2503641 | 23.700-14: New KI for FS_Sensing_ARC WT#4. | CATT |
| S2-2503642 | 23.700-14: New KI for FS_Sensing_ARC WT#5. | CATT |
| S2-2503704 | Architectural assumptions for the 5GS sensing architecture. | Lenovo |
| S2-2503705 | Terms for the 5GS sensing architecture. | Lenovo |
| S2-2503770 | Architectural Assumptions of ISAC. | Nokia, Nokia Shanghai Bell |
| S2-2503771 | Architectural Requirements of ISAC. | Nokia, Nokia Shanghai Bell |
| S2-2503772 | KI#1 Architecture and function enhancements to support sensing. | Nokia, Nokia Shanghai Bell |
| S2-2503773 | KI#2 Service authorization and revocation. | Nokia, Nokia Shanghai Bell |
| S2-2503774 | KI#3 Discovery and selection of sensing entities. | Nokia, Nokia Shanghai Bell |
| S2-2503775 | KI#4 Sensing data and the associated information collection and transport. | Nokia, Nokia Shanghai Bell |
| S2-2503776 | KI#5 sensing associated information and result exposure. | Nokia, Nokia Shanghai Bell |
| S2-2503777 | KI#6 Configuration parameters policy provisioning. | Nokia, Nokia Shanghai Bell |
| S2-2503798 | Terms of Sensing study. | Huawei, HiSilicon |
| S2-2503799 | Architecture assumptions of Sensing study. | Huawei, HiSilicon |
| S2-2503800 | Call flow of the sensing study. | Huawei, HiSilicon |
| S2-2503801 | KI#2, New Sol: Service authorisation and revocation. | Huawei, HiSilicon |
| S2-2503802 | KI#3, New Sol: Discovery and selection of sensing entities. | Huawei, HiSilicon |
| S2-2503803 | KI#5, New Sol: Providing Sensing result and other related information. | Huawei, HiSilicon |
| S2-2503814 | New KI: KI for WT#3 for discovery and selection of sensing entities . | InterDigital Inc. |
| S2-2503815 | Key Issue for WT2, WT#3 & WT#4: QoS Mechanism. | OPPO |
| S2-2503819 | TR 23.700-14: FS_Sensing-ARC architecture requirements and assumptions . | Qualcomm Incorporated |
| S2-2503820 | TR 23.700-14: FS_Sensing-ARC new key issues. | Qualcomm Incorporated |
| S2-2503865 | Terms for FS_Sensing_ARC . | Xiaomi |
| S2-2503866 | New KI#1 architecture and function enhancement to support ISAC service . | Xiaomi |
| S2-2503867 | New KI#2 ISAC Service authorization and revocation . | Xiaomi |
| S2-2503868 | New KI#3 Discovery and selection of sensing entities . | Xiaomi |
| S2-2503869 | New KI#4 Sensing data and associated data collection and result calculation . | Xiaomi |
| S2-2503870 | New KI#5 Sensing associated information and result exposure . | Xiaomi |
| S2-2504047 | TR Skeleton for FS_Sensing_ARC | Apple, Xiaomi |
| S2-2504048 | TR Scope for FS_Sensing_ARC . | Apple, Xiaomi |
| S2-2504049 | Terms of Sensing study. | Huawei, HiSilicon |
| S2-2504050 | Key Issue for WT#6 Configuration parameter provisioning . | Sony |
| S2-2504051 | New Key Issue on Sensing Architecture . | Apple |
| S2-2504052 | TR 23.700-14: FS_Sensing-ARC new key issues. | Qualcomm Incorporated, Futurewei |
| S2-2504053 | Key issue for WT#3 Sensing entities discovery and selection. | Vivo |
| S2-2504054 | 23.700-14: Key issue X: Sensing data and the associated information collection and transport. | OPPO |
| S2-2504055 | Key Issue 5: Sensing result exposure. | China Mobile |
| S2-2504056 | Architectural Assumptions for sensing service. | China Telecom |
| S2-2504057 | Adding Architecture assumptions and requirements. | Ericsson |
| S2-2504261 | Terms of Sensing study. | Huawei, HiSilicon |
| S2-2504262 | Adding Architecture requirements. | Ericsson, NTT DOCOMO |
| S2-2504263 | Architectural Assumptions for sensing service. | China Telecom, LG, Huawei, ZTE, Ericsson, OPPO, China Mobile, Xiaomi, Samsung, Nokia, Nokia Shanghai Bell |
| S2-2504264 | New Key Issue on Sensing Architecture . | Apple, LG Electronics, Xiaomi, NTT DOCOMO |
| S2-2504265 | TR 23.700-14: FS_Sensing-ARC new key issues. | Qualcomm Incorporated, Futurewei, China Telecom, Xiaomi, vivo, Apple |
| S2-2504266 | Key issue for WT#3 Sensing entities discovery and selection. | Vivo, Xiaomi, Sony, OPPO, Qualcomm Incorporated, China Telecom, ZTE, ETRI, Nokia, Nokia Shanghai Bell, InterDigital Inc |
| S2-2504267 | Key Issue 5: Sensing result exposure. | China Mobile, CATT |
| S2-2504268 | Key Issue for WT#6 Configuration parameter provisioning . | Sony, OPPO, Samsung, China Mobile Com. Corporation, Nokia, Nokia Shanghai Bell |
| S2-2504269 | 23.700-14: Key issue X: Sensing data and the associated information collection and transport. | OPPO |
| S2-2504322 | Adding Architecture requirements. | Ericsson, NTT DOCOMO, Samsung, Nokia, Nokia Shanghai Bell, LG Electronics, ZTE, Xiaomi, Google, Ofinno, CEWiT, InterDigital Inc., Apple, CATT |
| S2-2504323 | Architectural Assumptions for sensing service. | China Telecom, LG Electronics, Huawei, ZTE, Ericsson, OPPO, China Mobile, Xiaomi, Samsung, Nokia, Nokia Shanghai Bell, Ofinno, CATT, Deutsche Telekom, Futurewei, NTT DOCOMO, Lenovo, vivo, Apple, CEWiT, MTK |
| S2-2504324 | Terms of Sensing study. | Huawei, HiSilicon, Offino, Lenovo, Deutsche Telekom |
| S2-2504325 | New Key Issue on Sensing Architecture . | Apple, LG Electronics, Xiaomi, NTT DOCOMO, Nokia, Nokia Shanghai Bell, ZTE, CeWIT |
| S2-2504326 | TR 23.700-14: FS_Sensing-ARC new key issues. | Qualcomm Incorporated, Futurewei, China Telecom, Xiaomi, vivo, Apple, Samsung, NTT DOCOMO, ETRI, ZTE, InterDigital, Nokia, Nokia Shanghai Bell. Huawei, HiSilicon, CEWiT |
| S2-2504327 | Key issue for WT#3 Sensing entities discovery and selection. | Vivo, China Mobile, Xiaomi, Sony, OPPO, Qualcomm Incorporated, China Telecom, Huawei, HiSilicon, ZTE, ETRI, Nokia, Nokia Shanghai Bell, InterDigital Inc, Apple, Futurewei, NTT DOCOMO, Ofinno, CEWiT |
| S2-2504328 | 23.700-14: Key issue X: Sensing data and the associated information collection and transport. | OPPO, ZTE, Xiaomi, ETRI, Lenovo, Intel, NTT Docomo, Futurewei, Nokia, Nokia Shanghai Bell, CATT, Huawei, HiSilicon, CEWiT |
| S2-2504329 | Key Issue 5: Sensing result exposure. | China Mobile, CATT, Apple, Nokia, Nokia Shanghai Bell, Huawei, HiSilicon, Samsung, ZTE, vivo, InterDigital, ETRI, NTT DOCOMO, Futurewei, CEWiT, Xiaomi, Lenovo |
| S2-2504330 | Key Issue for WT#6 Configuration parameter provisioning . | Sony, OPPO, Samsung, China Mobile Com. Corporation, Nokia, Nokia Shanghai Bell, NTT DOCOMO, CEWiT, Futurewei, DT |
| S2-2504331 | Terms of Sensing study. | Huawei, HiSilicon, Ofinno, Lenovo, Deutsche Telekom, Apple, Nokia, Nokia Shanghai Bell, CEWiT, NTT DOCOMO |
| TDoc | Title | Source |
|---|---|---|
| S2-2502795 | LS from TSG RAN: LS on AI/ML UE sided data collection | TSG RAN |
| S2-2502923 | DP for R20 AIML WT#2 UC | SK Telecom |
| S2-2502940 | Key issue for WT#1: Standardized UE data collection based on UP connection between UE and 5GC. | OPPO |
| S2-2502949 | New KI: 5GC Support for UE Data Collection over the User Plane . | Apple |
| S2-2502950 | PCR to TR 23.700-04: Requirements. | Nokia |
| S2-2502992 | 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 |
| S2-2502993 | 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 |
| S2-2502994 | 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 |
| S2-2502995 | 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 |
| S2-2502996 | Key issues for WT#1. | ZTE |
| S2-2502997 | Architecture requirement and assumption. | ZTE |
| S2-2503016 | UP building for UE training data collection. | ZTE |
| S2-2503017 | Architectural Assumptions and Requirements. | LG Electronics |
| S2-2503023 | KI#1, New Sol#X: Generalized UE data collection over user plane . | LG Electronics |
| S2-2503026 | TR Skeleton for FS_AIML_CN_Ph2 | Samsung, vivo |
| S2-2503027 | Scope for FS_AIML_CN_Ph2. | Samsung (rapporteur), vivo (rapporteur) |
| S2-2503068 | Solution for WT 1 General Framework for data collection from the UE. | Lenovo |
| S2-2503072 | New Use case for Work Task #2 (Whether and how to enhance the 5GC analytics to support efficient performance user plane). | Rakuten Mobile, NIST |
| S2-2503102 | Key issue for WT#1: Data collection UE authorization and availability verification. | OPPO |
| S2-2503103 | Key issue for WT#1: Discovery and selection of data collection UE. | OPPO |
| S2-2503104 | Key issue for WT#1: Tiggering of UE data collection over UP. | OPPO |
| S2-2503129 | New use case for WT2: user plane performance optimization with assistance of NWDAF. | Huawei, HiSilicon, CMCC |
| S2-2503132 | KI#1: New Sol: CP-instructed UP-based UE data collection. | NTT DOCOMO |
| S2-2503133 | WT#2: Key Issue description for user plane analytics. | NTT DOCOMO |
| S2-2503137 | New Key Issue: 5GC Analytics Enhancement to Support Efficient Performance of User Plane. | Huawei, HiSilicon |
| S2-2503138 | New Key Issue: How to support UE data collection and transfer over User Plane for UE-side model training. | Huawei, HiSilicon |
| S2-2503139 | New solution to support UE data collection and transfer for AI based positioning . | Huawei, HiSilicon |
| S2-2503140 | New Solution for UE Data Collection and Transfer over User Plane. | Huawei, HiSilicon |
| S2-2503188 | Architectural Assumptions and Requirements for FS_AIML_CN_Ph2. | |
| S2-2503189 | KI#1 solution using the generic architecture for collecting and exposing the collected UE data. | Ericsson |
| S2-2503192 | KI#2 description. | Ericsson |
| S2-2503223 | WT#1: KI#X-UE data collection over UP. | |
| S2-2503241 | New Key Issue for WT#1: UE-side Data Collection over User Plane. | InterDigital Inc |
| S2-2503247 | New Solution for UE-side Data Collection and Transfer over UP. | InterDigital Inc |
| S2-2503254 | WT#1: KI#X for UE policy of UE data collection. | |
| S2-2503280 | FS_AIML_CN_Ph2 Use case for WT#2. | ZTE |
| S2-2503281 | FS_AIML_CN_Ph2 Key issue for WT#2. | ZTE |
| S2-2503284 | Key issue for WT#1 UE data collection for AI/ML for NR air interface operation. | CATT |
| S2-2503285 | Key issue for WT#2 Network analytics enhancement for user plane performance improvement. | CATT |
| S2-2503290 | New Key Issue for transfer of data over UP for UE data collection. | Vivo(rapporteur), Samsung(rapporteur) |
| S2-2503291 | Architectural Assumptions and Requirements for FS_AIML_CN_Ph2. | Vivo(rapporteur), Samsung(rapporteur) |
| S2-2503292 | KI#1: New Solution UE data collection via DCCF in CN over UP. | Vivo |
| S2-2503315 | Architectural Assumptions and Requirements for FS_AIML_CN_Ph2. | OPPO |
| S2-2503316 | Key issue for WT#1: Architecture enhancement to support UE data collection. | OPPO |
| S2-2503317 | Key issue for WT#1: User consent and privacy for the standardized UE data collection. | OPPO |
| S2-2503318 | New Solution for KI#X: Establish the UP connection between UE and 5GC to support the standardized UE data collection. | OPPO |
| S2-2503322 | UE policy enhancement to support data collection from UE. | ZTE |
| S2-2503323 | NF selection and triggers for UE data collection. | ZTE |
| S2-2503396 | FS_AIML_CN_Ph2 New Key Issue for Work Task #1. | China Mobile |
| S2-2503398 | FS_AIML_CN_Ph2 New Key Issue for Work Task #2. | China Mobile, SK Telecom |
| S2-2503400 | Architecture Assumption of TR 23.700-04. | China Mobile |
| S2-2503478 | Architectural Assumptions and Requirements for WT#1. | ETRI |
| S2-2503479 | Key issue for WT#1. | ETRI |
| S2-2503481 | New Solution to KI#1: Policy enhancement for UE-side data collection over UP. | ETRI |
| S2-2503561 | Architectural Assumptions and Requirements for FS_AIML_CN_Ph2. | CATT |
| S2-2503562 | Use case for WT#1 UE data collection. | CATT |
| S2-2503563 | [DRAFT] Reply LS on AI/ML UE sided data collection | CATT |
| S2-2503599 | Architectural Assumptions for FS_AIML_CN_Ph2. | Xiaomi |
| S2-2503600 | Key issue for WT#1 UE data transfer via UP for UE-side model training for AIML NR air interface operation. | Xiaomi |
| S2-2503702 | New Solution for KI#1: UP based UE data collection solution for AI/ML NR air interface operation. | Qualcomm Incorporated |
| S2-2503714 | Evaluation criteria for WT#1. | Samsung |
| S2-2503728 | KI#1 New Sol: Support of AIML data transfer via UP with AMF involvement. | Samsung |
| S2-2503789 | TR Skeleton for FS_AIML_CN_Ph2 | Samsung, vivo |
| S2-2503795 | WT#2 use case: Prevention of unexpected service experience degradation. | Samsung |
| S2-2503796 | WT#2 use case: Enhancement of analytics for user plane traffic pattern and characteristic. | Samsung |
| S2-2503811 | 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. |
| S2-2503952 | Scope for FS_AIML_CN_Ph2. | Samsung (rapporteur), vivo (rapporteur) |
| S2-2503953 | TR Skeleton for FS_AIML_CN_Ph2 | Samsung, vivo |
| S2-2503954 | Architectural Assumptions and Requirements for FS_AIML_CN_Ph2. | Vivo(rapporteur), Samsung(rapporteur) |
| S2-2503955 | New Key Issue for transfer of data over UP for UE data collection. | Vivo(rapporteur), Samsung(rapporteur) |
| S2-2503956 | KI#1: New Solution UE data collection via DCCF in CN over UP. | Vivo |
| S2-2503957 | UP building for UE training data collection. | ZTE |
| S2-2503958 | KI#1, New Sol#X: Generalized UE data collection over user plane . | LG Electronics |
| S2-2503959 | Solution for WT 1 General Framework for data collection from the UE. | Lenovo |
| S2-2503960 | WT#2 use case AI/ML-assisted user plane traffic pattern and behaviour analysis to support efficient performance of User Plane. | SK Telecom, China Mobile, China Telecom, Deutsche Telekom, KPN N.V., LG Uplus, Verizon, Rakuten Mobile |
| S2-2503961 | New use case for WT2: user plane performance optimization with assistance of NWDAF. | Huawei, HiSilicon, CMCC, SK Telecom, ZTE |
| S2-2503962 | WT#2 Key Issue AI/ML-assisted user plane traffic pattern and behaviour analysis to support efficient performance of User Plane. | SK Telecom, China Mobile, China Telecom, Deutsche Telekom, KPN N.V., LG Uplus, Verizon, Rakuten Mobile |
| S2-2504192 | TR Skeleton for FS_AIML_CN_Ph2 | Samsung, vivo |
| S2-2504193 | Scope for FS_AIML_CN_Ph2. | Samsung (rapporteur), vivo (rapporteur) |
| S2-2504194 | New Key Issue for transfer of data over UP for UE data collection. | Vivo(rapporteur), Samsung(rapporteur) |
| S2-2504195 | Architectural Assumptions and Requirements for FS_AIML_CN_Ph2. | Vivo(rapporteur), Samsung(rapporteur) |
| S2-2504196 | WT#2 use case AI/ML-assisted user plane traffic pattern and behaviour analysis to support efficient performance of User Plane. | SK Telecom, China Mobile, China Telecom, Deutsche Telekom, KPN N.V., LG Uplus, Verizon, Rakuten Mobile, NTT DOCOMO, ETRI, ZTE, Huawei, Nokia, Samsung, Ericsson |
| S2-2504203 | WT#2 Key Issue AI/ML-assisted user plane traffic pattern and behaviour analysis to support efficient performance of User Plane. | SK Telecom, China Mobile, China Telecom, Deutsche Telekom, KPN N.V., LG Uplus, Verizon, Rakuten Mobile, NTT DOCOMO, ETRI, ZTE, Huawei, Nokia, Samsung, Ericsson |
| S2-2504222 | [DRAFT] LS on use case for NWDAF based UP performance optimization | Huawei |
| S2-2504234 | UP building for UE training data collection. | ZTE |
| S2-2504235 | New Key Issue for transfer of data over UP for UE data collection. | Vivo(rapporteur), Samsung(rapporteur) |
| S2-2504236 | WT#2 use case AI/ML-assisted user plane traffic pattern and behaviour analysis to support efficient performance of User Plane. | SK Telecom, China Mobile, China Telecom, Deutsche Telekom, KPN N.V., LG Uplus, Verizon, Rakuten Mobile, NTT DOCOMO, ETRI, ZTE, Huawei, Nokia, Samsung, Ericsson |
| S2-2504237 | New use case for WT2: user plane performance optimization with assistance of NWDAF. | Huawei, HiSilicon, CMCC, SK Telecom, ZTE |
| S2-2504238 | KI#1: New Solution UE data collection via DCCF in CN over UP. | Vivo, Samsung |
| S2-2504239 | New use case for WT2: user plane performance optimization with assistance of NWDAF. | Huawei, HiSilicon, CMCC, SK Telecom, ZTE |
| S2-2504240 | UP building for UE training data collection. | ZTE |
| S2-2504241 | KI#1, New Sol#X: Generalized UE data collection over user plane . | LG Electronics |
| S2-2504242 | Solution for WT 1 General Framework for data collection from the UE. | Lenovo |
| S2-2504421 | New use case for WT2: user plane performance optimization with assistance of NWDAF. | Huawei, HiSilicon, CMCC, SK Telecom, ZTE |
| S2-2504422 | UP building for UE training data collection. | ZTE |
| TDoc | Title | Source |
|---|---|---|
| S2-2502952 | Energy Optimization Trigger for PCF based Policy Control. | Ericsson |
| S2-2502956 | Architecture assumptions. | Vivo |
| S2-2502957 | New key issue for WT#1: Enhancements to the energy related information collection, determination, and exposure. | Vivo |
| S2-2502958 | New key issue for WT#2: Service adjustments for network energy saving. | Vivo |
| S2-2503073 | Key issue for WT#1: Whether and how to enhance the collection, determination and exposure of energy related information in the 5GS. | Rakuten Mobile |
| S2-2503120 | TR 23.700-67 Skeleton for FS_EnergySys_Ph2 | China Telecom, Lenovo (Rapporteur) |
| S2-2503123 | FS_EnergySys_Ph2 TR23.700-67 Scope. | China Telecom, Lenovo (Rapporteur) |
| S2-2503144 | KI#2: New Sol: Energy-aware data transfer policy negotiation. | NTT DOCOMO |
| S2-2503158 | Key issue for WT#1: Energy related information collection, determination, and exposure. | Samsung |
| S2-2503159 | Key issue for WT#2: Support of service adjustments for the UE. | Samsung |
| S2-2503160 | Key issue for WT#3: Enhancements based on energy related information. | Samsung |
| S2-2503287 | Key issue for WT#2: Support of service adjustments for the UE. | MediaTek Inc. |
| S2-2503288 | Solution for WT#2: Support of QoS adjustments. | MediaTek Inc. |
| S2-2503294 | Solution for WT#2: Support of policy adjustments. | MediaTek Inc. |
| S2-2503313 | Solution for WT#3: Support of UP path adjustments for the UE. | MediaTek Inc. |
| S2-2503383 | Key Issue for WT#1: Enhancements in collection, determination and exposure of energy related information. | NEC |
| S2-2503386 | Key issue for WT3: NF (re)selection and/or UP path adjustment based on energy related information. | NEC |
| S2-2503392 | KI#2, new sol: Service adjustments for network energy saving based on AF request and energy information. | Vivo |
| S2-2503418 | New KI for WT#3: NF (re)selection and UP path adjustment based on energy related information. | Vivo |
| S2-2503419 | KI #3, New Sol: AMF (re-)selection based on energy related information. | Vivo |
| S2-2503451 | Proposal on the architecture assumptions and requirement. | ZTE |
| S2-2503452 | Adding new KI on the collection, determination and exposure of energy related information. | ZTE |
| S2-2503453 | Adding new KI on supporting service adjustments for the UE to enable energy saving. | ZTE |
| S2-2503454 | Adding new KI on support of NF (re)selection and/or UP path adjustment based on energy related information. | ZTE |
| S2-2503482 | New Key Issue: Enhancement for energy related information collection, determination, and exposure. | China Mobile |
| S2-2503483 | New Key Issue: Network service adjustment with considering the energy consumption information. | China Mobile |
| S2-2503484 | New Key Issue: NF (re)selection and/or UP path adjustment based on energy related information. | China Mobile, Lenovo, China Telecom |
| S2-2503485 | Architectural Assumptions and Principles for Energy Efficiency and Energy Saving. | China Mobile, Lenovo, China Telecom |
| S2-2503566 | Architectural Assumptions and Requirements for FS_EnergySys_Ph2. | CATT |
| S2-2503567 | Key issue for WT#1 - Enhancements on energy related information collection and exposure. | CATT |
| S2-2503568 | Key issue for WT#2 - Service adjustments for the UE to enable energy saving. | CATT |
| S2-2503569 | Key issue for WT#3 - NF (re)selection and UP path adjustment for energy saving. | CATT |
| S2-2503570 | KI#2 new solution for policy control based on interactions with the EIF. | CATT |
| S2-2503571 | KI#3 new solution for UP path adjustment based on energy related information. | CATT |
| S2-2503603 | New Key issue for WT#1 On Enhancements of Energy-related information exposure. | Nokia |
| S2-2503608 | New Key issue for WT#2 - Service adjustments for the UE to enable energy saving. | Nokia |
| S2-2503610 | New Key issue for WT#3 - On the support NF (re-)selection and/or UP path adjustment based on energy related information . | Nokia |
| S2-2503612 | KI#1:new solution: P-CR on exposure of UE scoring data. | Nokia |
| S2-2503634 | WT#1: EC improvement for Passive and dynamic EC. | Huawei, HiSilicon |
| S2-2503635 | WT#1: Renewable energy per UE, PDU session and SDF. | Huawei, HiSilicon |
| S2-2503636 | WT#3: NF selection profile and UPF selection. | Huawei, HiSilicon |
| S2-2503713 | New Solution to WT#2: Enabling dynamic QoS handling for energy efficiency lterby use of Energy Saving QoS Profiles . | Qualcomm Incorporated |
| S2-2503717 | New KI: Enhancing collection, determination and exposure of energy related information. | NTT DOCOMO |
| S2-2503727 | New KI: Service adjustment for energy saving. | NTT DOCOMO |
| S2-2503730 | New KI: Enhancing 5GC energy efficiency . | NTT DOCOMO |
| S2-2503787 | Energy Consumption information assisted Policy Update. | China Mobile |
| S2-2503788 | KI#2: New Solution on SM policy control based on EIF notification. | Samsung |
| S2-2503790 | KI#2: New Solution on AM policy control based on EIF notification. | Samsung |
| S2-2503832 | KI#2: New Solution on policy control based on Energy Consumption Information for Network Slice. | Samsung |
| S2-2503856 | KI#3: New solution on NF selection mechanism based on energy related information. | Samsung |
| S2-2503879 | KI#1 - Enhancements on energy related information collection, determination and exposure. | Lenovo |
| S2-2504068 | TR 23.700-67 Skeleton for FS_EnergySys_Ph2 | China Telecom, Lenovo (Rapporteur) |
| S2-2504069 | Architectural Assumptions and Principles for Energy Efficiency and Energy Saving. | China Mobile, Lenovo, China Telecom |
| S2-2504070 | New Key issue for WT#1 On Enhancements of Energy-related information exposure. | Nokia |
| S2-2504071 | Key issue for WT#2: Support of service adjustments for the UE. | MediaTek Inc., Samsung, vivo |
| S2-2504072 | New Key Issue: NF (re)selection and/or UP path adjustment based on energy related information. | China Mobile, Lenovo, China Telecom, NTT DOCOMO, InterDigital |
| S2-2504073 | KI#1:new solution: P-CR on exposure of UE scoring data. | Nokia |
| S2-2504074 | Energy Optimization Trigger for PCF based Policy Control. | Ericsson |
| S2-2504075 | KI#2: New Sol: Energy-aware data transfer policy negotiation. | NTT DOCOMO |
| S2-2504076 | New Solution to WT#2: Enabling dynamic QoS handling for energy efficiency lterby use of Energy Saving QoS Profiles . | Qualcomm Incorporated |
| S2-2504077 | Solution for WT#2: Support of QoS adjustments. | MediaTek Inc., vivo |
| S2-2504078 | KI#2, new sol: Service adjustments for network energy saving based on AF request and energy information. | Vivo |
| S2-2504079 | KI#2 new solution for policy control based on interactions with the EIF. | CATT |
| S2-2504308 | Architectural Assumptions and Principles for Energy Efficiency and Energy Saving. | China Mobile, Lenovo, China Telecom |
| S2-2504309 | KI#1: new solution: P-CR on exposure of UE scoring data. | Nokia |
| S2-2504310 | Energy Optimization Trigger for PCF based Policy Control. | Ericsson |
| S2-2504311 | KI#2: New Sol: Energy-aware data transfer policy negotiation. | NTT DOCOMO |
| S2-2504312 | Solution for WT#2: Support of QoS adjustments. | MediaTek Inc., vivo |
| S2-2504313 | KI#2, new sol: Service adjustments for network energy saving based on AF request and energy information. | Vivo |
| S2-2504314 | KI#2 new solution for policy control based on interactions with the EIF. | CATT |
| S2-2504315 | New Solution to WT#2: Enabling dynamic QoS handling for energy efficiency lterby use of Energy Saving QoS Profiles . | Qualcomm Incorporated, vivo |
| S2-2504316 | FS_EnergySys_Ph2 TR23700-67 Skeleton. | China Telecom, Lenovo (Rapporteur) |
| S2-2504342 | KI#1: new solution: P-CR on exposure of UE scoring data. | Nokia |
| S2-2504343 | Energy Optimization Trigger for PCF based Policy Control. | Ericsson |
| S2-2504344 | Solution for WT#2: Support of QoS adjustments. | MediaTek Inc., vivo |
| S2-2504345 | KI#2, new sol: Service adjustments for network energy saving based on AF request and energy information. | Vivo |
| S2-2504346 | KI#2: New Sol: Energy-aware data transfer policy negotiation. | NTT DOCOMO |
| S2-2504347 | New Solution to WT#2: Enabling dynamic QoS handling for energy efficiency lterby use of Energy Saving QoS Profiles . | Qualcomm Incorporated, vivo |
| S2-2504479 | Energy Optimization Trigger for PCF based Policy Control. | Ericsson |
| TDoc | Title | Source |
|---|---|---|
| S2-2504423 | WI Status Report for Integration of satellite components in the 5G architecture Phase 3 (5GSAT_Ph3-ARC) | Rapporteur (CATT) |
| S2-2504424 | WI Status Report for System architecture for next generation real time communication services phase 2 (NG_RTC_Ph2) | Rapporteur (China Mobile) |
| S2-2504425 | WI Status Report for Extended Reality and Media service (XRM) Phase 2 (XRM_Ph2) | Rapporteur (Nokia) |
| S2-2504426 | WI Status Report for 5GS Enhancement for Energy Efficiency and Energy Saving (EnergySys) | Rapporteur (Samsung) |
| S2-2504427 | WI Status Report for MPS for IMS Messaging and SMS services (MPS4msg) | Rapporteur (Peraton Labs) |
| S2-2504428 | WI Status Report for Architecture Enhancements for Vehicle Mounted Relays Phase 2 (VMR_Ph2) | Rapporteur (Qualcomm) |
| S2-2504429 | WI Status Report for System Enhancement for Proximity-based Services in 5GS - Phase 3 (5G_ProSe_Ph3) | Rapporteur (TNO) |
| S2-2504430 | WI Status Report for Identifying non-3GPP Devices Connecting behind a UE or 5G-RG (UIA_ARC) | Rapporteur (Interdigital) |
| S2-2504431 | WI Status Report for Enhancement of support for Edge Computing in 5G Core network - Phase 3 (eEDGE_5GC_Ph3) | Rapporteur (Intel) |
| S2-2504432 | WI Status Report for Phase 3 for UAS, UAV and UAM (UAS_Ph3) | Rapporteur (LGE) |
| S2-2504433 | WI Status Report for UPF enhancement for Exposure And SBA Phase 2 (UPEAS_Ph2) | Rapporteur (ZTE) |
| S2-2504434 | WI Status Report for System aspects of 5G NR Femto (5G_Femto) | Rapporteur (DOCOMO) |
| S2-2504435 | WI Status Report for Multi-Access (ATSSS_Ph4) (MASSS) | Rapporteur (Apple) |
| S2-2504436 | WI Status Report for Architecture support of Ambient power-enabled Internet of Things (AmbientIoT-ARC) | Rapporteur (Huawei) |
| S2-2504437 | WI Status Report for Core Network Enhanced Support for Artificial Intelligence (AI)/Machine Learning (ML) (AIML_CN) | Rapporteur (vivo) |
| S2-2504438 | WI Status Report for Study on Integration of satellite components in the 5G architecture Phase 4 (FS_5GSAT_Ph4_ARC) | Rapporteur (CATT) |
| S2-2504439 | WI Status Report for Study on Architecture Enhancement to support Integrated Sensing and Communication (FS_Sensing_ARC) | Rapporteur (Xiaomi) |
| S2-2504440 | WI Status Report for Study on Core Network Enhanced Support for Artificial Intelligence (AI)/Machine Learning (ML)_Ph2 (FS_AIML_CN_Ph2) | Rapporteur (vivo) |
| S2-2504441 | WI Status Report for Study on Energy Efficiency and Energy Saving Phase2 (FS_EnergySys_Ph2) | Rapporteur (Lenovo) |
| TDoc | Title | Source |
|---|---|---|
| S2-2503112 | TU budget for Rel-20 | SA WG2 Chair |
| S2-2503113 | Work Planning slides | SA WG2 Chair |
| S2-2503114 | Work planning spreadsheet | SA WG2 Chair |
| S2-2503116 | Best practice for SA WG2 studies | SA WG2 Chair |
| S2-2503117 | Guidance for SA WG2 Rel-20 preparation in Q2 2025. | SA WG2 Chair |
| S2-2504388 | Work Planning slides | SA WG2 Chair |
| S2-2504389 | Best practice for SA WG2 studies. | SA WG2 Chair |
| S2-2504416 | Best practice for SA WG2 studies. | SA WG2 Chair |
| S2-2504475 | Plan for SA2#168 Friday Plenary | SA WG2 Chair |
| TDoc | Title | Source |
|---|---|---|
| S2-2502850 | LS from SA WG3: LS on UIA Rel-20 in response to SA guidance from SA#107 | SA WG3 |
| S2-2502888 | Discussion on Ambient IoT Phase 2. | KPN N.V. |
| S2-2502897 | New SID on System Enhancement for Proximity-based Services in 5GS - Phase 4. | KPN N.V. |
| S2-2502946 | Ambient IoT scope for Rel-20. | Qualcomm |
| S2-2502984 | Discussion for WT-3 Resilient Notification. | EchoStar, Boost Mobile |
| S2-2503014 | Discussion on Rel-20 Ambient IoT Scope. | CATT |
| S2-2503029 | LGE View on Rel-20 Ambient IoT study | LG Electronics |
| S2-2503051 | Proposed scope of AmbientIoT-ARC Phase 2. | OPPO |
| S2-2503059 | Moderator summary and proposal on: Moderated discussion for Indirect Network Sharing phase2. | China Unicom (Moderator) |
| S2-2503060 | New SID on Study on Indirect Network Sharing phase2. | China Unicom (Moderator) |
| S2-2503066 | New SID on Study on Indirect Network Sharing phase2. | China Unicom |
| S2-2503069 | Indirect Network Sharing phase 2 | China Unicom |
| S2-2503105 | Discussion on IMS resiliency study. | KDDI, SK Telecom |
| S2-2503107 | Discussion on Rel-20 AIoT. | NEC |
| S2-2503118 | TSG SA Guidance to SA WG2 on 5GA studies | SA WG2 Chair |
| S2-2503164 | Discussion on Rel-20 Ambient IoT study. | Ofinno |
| S2-2503214 | Extension for XRM on-path signalling Connect-UDP Forwarded Mode. . | Ericsson |
| S2-2503243 | NWM summary report on Mission Critical Services, Multimedia Priority Services | Peraton Labs (moderator) |
| S2-2503244 | New SID on MPS Enhancements for IoT. | Peraton Labs (moderator) |
| S2-2503245 | New SID on MPS Enhancements for IoT. | Peraton Labs |
| S2-2503246 | New SID on System Enhancement for Proximity-based Services in 5GS - Phase 4. | Peraton Labs (moderator) |
| S2-2503480 | Discussion on Release 20 Ambient IoT SID scope. | NTT DOCOMO |
| S2-2503503 | Discussion on R20 Ambient IoT SID scope | Nokia Korea |
| S2-2503534 | Overall View on 5G-A Rel-20 AIoT | China Mobile Com. Corporation |
| S2-2503557 | Discussion on enhancement to IMS network capability exposure. | Huawei, HiSilicon |
| S2-2503592 | New SID on 5GS XRM Ph3. | CATT |
| S2-2503661 | Discussion paper for information on Loop prevention and Multi Domain Support in the study on Industrial Networks Enhancements. | Nokia |
| S2-2503671 | New SID: Study on Architecture support of Ambient power-enabled Internet of Things Phase2. | Vivo |
| S2-2503715 | New SID on Study on Indirect Network Sharing phase2. | NEC |
| S2-2503767 | New SID: Study on system architecture for next generation real time communication services phase 3. | China Mobile |
| S2-2503768 | Moderator report: Moderated discussion on NG_RTC continuation | China Mobile |
| S2-2503797 | Resilient Notification. | EchoStar, Boost Mobile |
| S2-2503826 | Study on Extended Reality and Media Service (XRM) Phase 3. | Nokia |
| S2-2503827 | NWM Discussion Report on R20 5GA XRM_Ph3 | Nokia |
| S2-2503829 | Discussion on Rel-20 FS_XRM Ph3. | Huawei, HiSilicon, China Mobile, SK Telecom, |
| S2-2503830 | New SID on Study on Indirect Network Sharing phase2. | CableLabs |
| S2-2503844 | Rel-20 SA WG2 Ambient IoT Proposal | Huawei, HiSilicon |
| S2-2503893 | Discussion on Rel-20 FS_XRM Ph3. | Huawei, HiSilicon, China Mobile, SK Telecom |
| S2-2504371 | New SID on Study on Indirect Network Sharing phase2. | China Unicom (Moderator) |
| S2-2504372 | Study on Extended Reality and Media Service (XRM) Phase 3. | Nokia |
| S2-2504373 | New SID: Study on system architecture for next generation real time communication services phase 3. | China Mobile |
| S2-2504374 | New SID on System Enhancement for Proximity-based Services in 5GS - Phase 4. | KPN N.V. |
| S2-2504415 | New WID on Indirect Network Sharing phase2. | China Unicom (Moderator) |
| S2-2504474 | New WID on Indirect Network Sharing phase2. | China Unicom (Moderator) |
| TDoc | Title | Source |
|---|---|---|
| S2-2502869 | NTT DOCOMO's views on 6G study | NTT DOCOMO |
| S2-2502873 | AT&T views on 6G study in SA WG2 | AT&T Services, Inc. |
| S2-2502878 | Verizons views on 6G study in SA WG2 | Verizon Spain |
| S2-2502884 | China Mobile views about 6G Architecture | China Mobile |
| S2-2502887 | KPN N.V. views on 6G Architecture | KPN N.V. |
| S2-2502896 | Intel views on 6G study | Intel |
| S2-2502935 | Some fundamental principles on 6G Architecture. | China Mobile, China Telecom, China Unicom, CATT, OPPO, Vivo, Xiaomi, ZTE |
| S2-2502941 | Lenovo views on 6G study | Lenovo |
| S2-2502945 | Proposed scope for 6G study item | Qualcomm |
| S2-2502959 | Boost Mobile views on 6G study | Boost Mobile Network |
| S2-2502989 | SK Telecom views on 6G study | SK Telecom |
| S2-2502991 | Focus Areas and Priorities in the 6G Study | ETRI, SK Telecom, KT, LG Uplus |
| S2-2503058 | China Unicom view on SA WG2 R20 6G SID | China Unicom |
| S2-2503067 | Rakuten_Mobile_6G_Priorities_Presentation | Rakuten Mobile, Inc |
| S2-2503162 | Huawei view on 6G Core SID scope | Huawei, HiSilicon |
| S2-2503186 | Google's views on 6G study | |
| S2-2503225 | Futurewei Views on 6G Study | Futurewei Technologies |
| S2-2503256 | 6G System Scope, Technical areas | Nokia |
| S2-2503260 | OPPO View on 6G SID WTs | OPPO |
| S2-2503270 | Ericsson view on 6G SID Scope Content | Ericsson |
| S2-2503286 | China Telecom's View on First 6G Service and Architecture | China Telecom |
| S2-2503293 | Vivo view on 6G system architecture | vivo |
| S2-2503375 | Areas of NEC interests in 6G architecture | NEC Corporation |
| S2-2503377 | Discussion for 6G Study on Interworking and Migration | Samsung |
| S2-2503412 | Apple's View on 6G SID Scope | Apple |
| S2-2503541 | UE and network Coordinated Computing | OPPO, China Unicom, LG Electronics, CATT, CMCC, vivo, SKT, China Telecom |
| S2-2503594 | Vivo view on 6G AIML | vivo |
| S2-2503602 | Samsung view on 6G Architecture | Samsung |
| S2-2503611 | Topics for SA WG2 6G Study | Vodafone |
| S2-2503613 | ZTE view on 6G scope for Architecture | ZTE |
| S2-2503669 | Discussion for 6G Study on Service Plane | Samsung |
| S2-2503675 | CATT views on SA WG2 6G SID | CATT |
| S2-2503716 | Discussion for 6G study on Native AI | Samsung |
| S2-2503733 | Discussion for 6G Study on Network Resilience | Samsung |
| S2-2503749 | Discussion for 6G Study on compact and simple network architecture | Samsung Electronics France SA |
| S2-2503810 | Thoughts on SA WG2 6G Study Scope | MediaTek Inc. |
| S2-2503823 | Interdigital's views on SA WG2 6G Study item | InterDigital Canada |
| S2-2503828 | MSO View on 6G SID Scope | CableLabs, Charter Communications, Comcast |
| S2-2503859 | Charter Communications - 6G System Architecture and Services Priorities | Charter Communications, Inc |
| S2-2503871 | Xiaomi's view on the key areas of 6GC study | Xiaomi |
| S2-2503875 | Views on Priority Topics for 6G System Architecture SID | Deutsche Telekom AG |
| S2-2503892 | LGE view on 6G study | LG Electronics |
| S2-2504139 | Discussion on work areas of 6G SA WG2 study. | Moderator (ZTE) |
| S2-2504140 | Discussion on work areas of 6G SA WG2 study. | Moderator |
| S2-2504414 | Discussion on work areas of 6G SA WG2 study. | Moderator |
| TDoc | Title | Source |
|---|---|---|
| S2-2502833 | LS from TSG RAN: LS on AI/ML UE sided data collection | TSG RAN |
| S2-2502834 | LS from SA WG3: Reply LS on security aspects of Ambient IoT | SA WG3 |
| S2-2502837 | LS from SA WG4: Reply LS on Clarification of DC Binding Information | SA WG4 |
| S2-2502851 | WITHDRAWN: Reserved for incoming LS | MCC |
| S2-2502852 | WITHDRAWN: Reserved for incoming LS | MCC |
| S2-2502908 | Corrections on UPF Event Exposure | Ericsson |
| S2-2502925 | Discussion on AF specific UE ID generation | Samsung |
| S2-2502954 | Handling of AF Specific UE IDs | Ericsson |
| S2-2502967 | Update to Nnef_UAVFlightAssistance_Notify service operation | Ericsson |
| S2-2502990 | FS_AIML_CN_Ph2 WT#2 UC | SK Telecom |
| S2-2502998 | KI#1 Solution_UE policy enhancement to support data collection from UE | ZTE |
| S2-2502999 | KI#1 Solution_NF selection and triggers for UE data collection | ZTE |
| S2-2503033 | 23.502 Clarifications to Session Management aspects for handling multiple Non-3GPP Device Identifiers | Samsung |
| S2-2503035 | 23.501 Clarification to usage of Operator configurable UPF capabilties in roaming scenarios | Samsung |
| S2-2503081 | [DRAFT] Reply LS on OSAppID usage by AppToken use case | Nokia |
| S2-2503082 | AMF reselection via NAS reroute based on Routing Indicator | Jio Platforms Ltd (JPL) |
| S2-2503083 | Service restoration by IMS when the UE is unresponsive but reachable | Jio |
| S2-2503086 | Service restoration by IMS when the UE is unresponsive but reachable | Jio Platforms Ltd (JPL) |
| S2-2503087 | Service restoration by IMS when the UE is unresponsive but reachable | Jio Platforms Ltd (JPL) |
| S2-2503296 | [DRAFT] Reply LS on multiplexing capability negotiation | Qualcomm Incorporated |
| S2-2503358 | UDM functional description update for CAG information provisioning | SAMSUNG |
| S2-2503359 | Removal of event subscription for CAG information provisioning | SAMSUNG |
| S2-2503364 | Procedure updates for S&F operation | LG Electronics |
| S2-2503428 | PCR to TS 23.369 on aggregation aspects. | NTT DOCOMO |
| S2-2503474 | Discussion on Release 20 Ambient IoT SID scope | NTT DOCOMO INC.. |
| S2-2503511 | Clarifications for multi-modal services | Huawei, HiSilicon |
| S2-2503512 | Clarifications for multi-modal services | Huawei, HiSilicon |
| S2-2503784 | Clarifications and corrections on usage of MoQ for encrypted media flows | China Mobile |
| S2-2503808 | Collection of energy consumption information for new PDU session | Samsung |
| S2-2503812 | End UE RSC Bounded Routing | Nokia, Nokia Shanghai Bell |
| S2-2504092 | Reserved for Wanqiang's sessions | - |
| S2-2504093 | Reserved for Wanqiang's sessions | - |
| S2-2504351 | Reserved for Wanqiang's sessions | - |
| S2-2504352 | Reserved for Wanqiang's sessions | - |
| S2-2504442 | Reserved for Dario's sessions | - |
| S2-2504443 | Reserved for Dario's sessions | - |
| S2-2504444 | Reserved for Dario's sessions | - |
| S2-2504445 | Reserved for Dario's sessions | - |
| S2-2504446 | Reserved for Dario's sessions | - |
| S2-2504447 | Reserved for Dario's sessions | - |
| S2-2504448 | Reserved for Dario's sessions | - |
| S2-2504449 | Reserved for Dario's sessions | - |
| S2-2504450 | Reserved for Dario's sessions | - |
| S2-2504451 | Reserved for Dario's sessions | - |
| S2-2504452 | Reserved for Dario's sessions | - |
| S2-2504453 | Reserved for Dario's sessions | - |
| S2-2504454 | Reserved for Dario's sessions | - |
| S2-2504455 | Reserved for Dario's sessions | - |
| S2-2504456 | Reserved for Dario's sessions | - |
| S2-2504457 | Reserved for Dario's sessions | - |
| S2-2504458 | Reserved for Dario's sessions | - |
| S2-2504459 | Reserved for Dario's sessions | - |
| S2-2504460 | Reserved for Dario's sessions | - |
| S2-2504461 | Reserved for Dario's sessions | - |
| S2-2504462 | Reserved for Dario's sessions | - |
| S2-2504463 | Reserved for Dario's sessions | - |
| S2-2504464 | Reserved for Dario's sessions | - |
| S2-2504465 | Reserved for Dario's sessions | - |
| S2-2504466 | Reserved for Dario's sessions | - |