TDoc | Title | Source |
---|---|---|
S2-2504483 | SA2#169 meeting Agenda | SA WG2 Chair |
S2-2504484 | SA WG2#169 session plan | SA WG2 Chair |
S2-2504730 | SA WG2#169 Plan for the meeting | SA WG2 Chair |
TDoc | Title | Source |
---|---|---|
S2-2504485 | Draft Report of SA WG2 meeting #168 | SA WG2 Secretary |
TDoc | Title | Source |
---|---|---|
S2-2504571 | LS from CEN TC 278 WG 15: LS on Next Generation eCall | CEN TC 278 WG 15 |
S2-2504632 | LS from IETF IPv6 Maintenance (6MAN): LS on draft-ietf-6man-deprecate-router-alert, 'Deprecation of the IPv6 Router Alert Option for New Protocols' | IETF IPv6 Maintenance (6MAN) |
S2-2504633 | LS from IETF GREEN WG: LS on the creation of the Getting Ready for Energy-Efficient Networking Working Group in the IETF | IETF GREEN WG |
S2-2504755 | [DRAFT] LS reply on Handling of UE Radio Capability for Paging | Huawei, HiSilicon |
S2-2504756 | Alignment on Handling of UE Radio Capability for Paging | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
S2-2504806 | Misleading message flow in network triggered SR procedure | Nokia |
TDoc | Title | Source |
---|---|---|
S2-2504925 | Synchronizing status of QoS Flow(s) between H-SMF or anchor SMF and UE | Ericsson |
TDoc | Title | Source |
---|---|---|
S2-2504636 | BSF subscription validity time | Oracle, Verizon |
S2-2504680 | BSF subscription validity time | Oracle, Verizon |
S2-2505101 | Update of definitions clause | Huawei, HiSilicon |
S2-2505102 | Update of definitions clause | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
S2-2504518 | LS from RAN WG3: LS on Handling of UE Radio Capability for Paging | RAN WG3 |
S2-2504920 | [DRAFT] Reply LS on Handling of UE Radio Capability for Paging | Ericsson |
S2-2504921 | UE radio capability for paging handling | Ericsson |
S2-2504922 | UE radio capability for paging handling | Ericsson |
S2-2504923 | UE radio capability for paging handling | Ericsson |
S2-2505001 | [DRAFT] Response LS on Handling of UE Radio Capability for Paging | ZTE |
S2-2505376 | [DRAFT] Response LS on Handling of UE Radio Capability for Paging | Vodafone |
S2-2505420 | UE radio capability for paging handling | Ericsson |
S2-2505422 | UE radio capability for paging handling | Ericsson |
S2-2505423 | UE radio capability for paging handling | Ericsson |
TDoc | Title | Source |
---|---|---|
S2-2504618 | 5GS common time reference traceable to UTC | Nokia |
S2-2504619 | 5GS common time reference traceable to UTC | Nokia |
S2-2504620 | 5GS common time reference traceable to UTC | Nokia |
S2-2504621 | 5GS common time reference traceable to UTC | Nokia |
S2-2504623 | 5GS common time reference traceable to UTC | Nokia |
S2-2505426 | 5GS common time reference traceable to UTC | Nokia, ZTE |
S2-2505427 | 5GS common time reference traceable to UTC | Nokia, ZTE |
TDoc | Title | Source |
---|---|---|
S2-2504795 | Reference correction for NR RRC in clause 5.4.4.1 | Nokia |
TDoc | Title | Source |
---|---|---|
S2-2505301 | NSSRG clarification | Samsung |
TDoc | Title | Source |
---|---|---|
S2-2504572 | LS from CT WG1: LS on stage 1 requirements for the support for PWS over satellite NGRAN in Rel-17 | CT WG1 |
S2-2505396 | PWS support | Samsung |
S2-2505404 | [DRAFT] Reply LS on stage 1 requirements for the support for PWS over satellite NGRAN in Rel-17 | Samsung |
TDoc | Title | Source |
---|---|---|
S2-2504946 | Supporting multiple LCS-UPP connections per UE | Ericsson, Huawei, ZTE |
S2-2505353 | Discussion on routing ID and LCS-UP connection mapping for multiple LCS-UP connections. | OPPO |
S2-2505354 | Clarification and correction on modification of UP connection between UE and LMF | [Huawei, HiSilicon], OPPO |
S2-2505355 | User plane positioning update for correlation ID and LCS-UP connection mapping | OPPO |
S2-2505434 | Clarification and correction on modification of UP connection between UE and LMF | Nokia, Nokia Shanghai Bell |
TDoc | Title | Source |
---|---|---|
S2-2504807 | Clarification on always-on PDU Session | Nokia,[ZTE] |
S2-2504808 | Clarification on always-on PDU Session | ZTE |
S2-2505000 | Clarification on Configured NSSAI mismatch when a network performs slice replacement for on demand slices | LG Electronics |
TDoc | Title | Source |
---|---|---|
S2-2504520 | LS from RAN WG3: LS on Average Window for Alternative QoS | RAN WG3 |
S2-2504539 | Alignment of PDU set information | ZTE |
S2-2504540 | Alignment of PDU set information | ZTE |
S2-2504865 | Removal of Averaging Window from the AQP | Ericsson |
S2-2504866 | Removal of Averaging Window from the AQP | Ericsson |
S2-2504867 | [DRAFT] LS Reply on Average Window for Alternative QoS | Ericsson |
S2-2504939 | [DRAFT] LS on Average Window for Alternative QoS | CATT |
S2-2504968 | [DRAFT] Reply LS on Average Window for Alternative QoS | ZTE |
S2-2505103 | Clarifications for multi-modal services | Huawei, HiSilicon, Nokia |
S2-2505104 | Clarifications for multi-modal services | Huawei, HiSilicon, Nokia |
S2-2505105 | Clarifications for multi-modal services | Huawei, HiSilicon |
S2-2505106 | Clarifications for multi-modal services | Huawei, HiSilicon |
S2-2505107 | Clarifications and corrections for ECN marking for L4S and congestion monitoring | Huawei, HiSilicon |
S2-2505108 | Clarifications and corrections for ECN marking for L4S and congestion monitoring | Huawei, HiSilicon |
S2-2505155 | [DRAFT] LS Reply on Average Window for Alternative QoS | SAMSUNG |
TDoc | Title | Source |
---|---|---|
S2-2504507 | LS from CT WG4: Reply LS on request for IMS Data Channel related clarifications | CT WG4 |
S2-2505208 | Adding event for session establishment cancellation | China Mobile |
S2-2505209 | Adding event for session establishment cancellation | China Mobile |
TDoc | Title | Source |
---|---|---|
S2-2504691 | HR SBO request indication in inter PLMN mobility case | Samsung |
S2-2504692 | HR SBO request indication in inter PLMN mobility case | Samsung |
S2-2504693 | HR SBO request indication in inter PLMN mobility case | Samsung |
S2-2504694 | HR SBO request indication in inter PLMN mobility case | Samsung |
S2-2505126 | Failure notification to AF on simultaneous connectivity | Huawei, Hisilicom |
S2-2505254 | Simultaneous connectivity failure notification | Samsung |
TDoc | Title | Source |
---|---|---|
S2-2504529 | LS from SA WG3: LS reply on Issues related to Analytics context transfer between AnLF(s) | SA WG3 |
S2-2504536 | Clarifications on the definition of accuracy | ZTE |
S2-2504537 | Clarifications on accuracy monitoring procedure | ZTE |
S2-2504538 | Clarifications on accuracy monitoring procedure | ZTE |
S2-2504786 | Correction on ML Model accuracy related information | Vivo |
S2-2504787 | Correction on ML Model accuracy related information | Vivo |
S2-2504879 | Alignment to reflect the SA WG2 status according to LS reply from SA WG3 | Ericsson |
S2-2504880 | Alignment to reflect the SA WG2 status according to LS reply from SA WG3 | Ericsson |
S2-2504989 | Optional Addition of last known UE Location | Verizon, AT&T, Charter Communications, China Mobile, China Telecom, Deutsche Telekom , Ericsson, Nokia, Oracle, Rakuten Mobile, Samsung, SK Telecom, Vodafone |
S2-2504996 | Addition of QoS Flow Maintainability KPI | Verizon, Oracle |
S2-2504998 | [DRAFT] LS for a new KPI related to the maintainability of a QoS flow | Verizon Switzerland AG, Oracle |
S2-2505411 | Discussion on QoS Flow Sustainability. | Verizon, Oracle |
S2-2505424 | Alignment to reflect the SA WG2 status according to LS reply from SA WG3 | Ericsson |
TDoc | Title | Source |
---|---|---|
S2-2504506 | LS from CT WG4: Reply LS on maximum warning message size | CT WG4 |
S2-2504578 | LS from RAN WG3: Reply LS on OAM requirements to support regenerative payload transport links | RAN WG3 |
S2-2504580 | LS from SA WG5: Reply LS to LS on reply to LS on OAM requirements to support regenerative payload | SA WG5 |
S2-2504656 | Support of NG connection interruption due to hard feeder link switch over | China Telecom |
S2-2504683 | Update on early media handling in UE-Satellite-UE scenario | Vivo |
S2-2504722 | Removal of Rx-Related Note for UE-SAT-UE | ZTE, CATT |
S2-2504723 | Input Parameter Alignment for UP Path Change Subscription in TS 23.502 | ZTE |
S2-2504724 | Input Parameter Alignment for UP Path Change Subscription in TS 23. 228 | ZTE |
S2-2504725 | Enhancement of SM Policy Control to Support Implicit Subscription Handling | ZTE |
S2-2504726 | Clarification of DNAI Handling for UE-SAT-UE Communication | ZTE |
S2-2504727 | Refinement of UE behavior and S&F wait timer handling | ZTE |
S2-2504777 | Update to Initial Call setup and functional support for UE-Satellite-UE communication in IMS | Ericsson |
S2-2504778 | Update to Mobility procedures for UE-Satellite-UE communication | Ericsson |
S2-2504790 | Clarification on S&F Wait Timer | Nokia, Huawei, HiSilicon |
S2-2504882 | On TAI configuration in AMF via OAM. | Qualcomm Incorporated, Vodafone |
S2-2504905 | Clarify S1-U not supported by split MME | Ericsson, AT&T |
S2-2504906 | Clarify PDN connection handling for split MME | Ericsson, AT&T |
S2-2504907 | Clarify the S&F event is sent from SCEF to SCS/AS | Ericsson, AT&T |
S2-2504909 | TAI handling for regenerative access . | Ericsson |
S2-2504911 | [DRAFT] Reply LS on OAM requirements to support regenerative payload transport links | Qualcomm, Vodafone |
S2-2504977 | Transition to S&F satellite for legacy UE | Qualcomm Incorporated |
S2-2504994 | UE procedures for handling S&F Wait Timer | Qualcomm Incorporated |
S2-2505050 | Transitioning between operation in S&F mode and normal mode | LG Electronics |
S2-2505051 | Procedure updates for S&F operation | LG Electronics |
S2-2505053 | Updates to S&F mode transition | Vivo |
S2-2505054 | Procedure updates for S&F | Vivo |
S2-2505055 | TAIs configured by OAM | Vivo |
S2-2505056 | TAIs configured by OAM | Vivo |
S2-2505057 | [DRAFT] Reply LS on OAM requirements to support regenerative payload transport links | vivo |
S2-2505093 | Update on change of BP/ULCL and UP notification procedures for UE-Satellite-UE communication | ETRI |
S2-2505100 | Clarification that a UE may not be necessarily served by all the satellites in S&F mode in a PLMN but by a subset of satellites | Sateliot, Thales, Novamint |
S2-2505149 | Clarification on UP path event subscription for UE-satellite-UE communication | Huawei, HiSilicon |
S2-2505150 | Clarification and correction on UP path event report for UE-satellite-UE communication | Huawei, HiSilicon |
S2-2505151 | Update Support of Attach with PDN connection for split MME architecture | Huawei, HiSilicon |
S2-2505152 | Removing UE S&F Term | Huawei, HiSilicon |
S2-2505201 | Detach related procedures update to support S&F operation | Xiaomi |
S2-2505223 | Avoid congestion caused by S&F timer | MediaTek Inc. |
S2-2505232 | Update to the GUTI Reallocation procedure | ZTE |
S2-2505233 | N2 interface enhancement for downlink data suspension/resumption | ZTE |
S2-2505236 | Discussion on OAM based solution to support NTN regenerative payload. | CATT, CSCN, ZTE, vivo |
S2-2505237 | [DRAFT] Reply LS on OAM requirements to support regenerative payload transport links | CATT |
S2-2505238 | Configuration of TAI list for regenerative satellite payload | CATT, CSCN |
S2-2505239 | Clarification on UE-SAT-UE communication when serving satellite changes | CATT |
S2-2505240 | Clarification on UE-Satellite-UE communication procedures | CATT |
S2-2505261 | [DRAFT] Reply LS on OAM requirements to support regenerative payload transport links | CATT |
S2-2505389 | Align the terms. | Samsung |
S2-2505395 | Handling S&F not allowed. | Samsung |
S2-2505407 | Supported TAIs information | Samsung |
S2-2505408 | [DRAFT] Reply LS on OAM requirements to support regenerative payload transport links | Samsung |
TDoc | Title | Source |
---|---|---|
S2-2504581 | LS from GSMA TSG IMSDCAS: LS to SA WG2 About Requirements Concerning Automatic Resume Where You have Left Off | GSMA TSG IMSDCAS |
S2-2504634 | LS from SA WG4: LS on Advanced MF capability registration and discovery | SA WG4 |
S2-2504638 | Clarification of the NG_RTC_Ph2 KI#4 procedure description | Nokia |
S2-2504639 | Aligning MF selection criteria with 23.228 | Nokia |
S2-2504640 | [DRAFT] LS on Advanced MF capability registration and discovery | Nokia |
S2-2504770 | KI#8: Updates to services and operations | Ericsson |
S2-2504771 | KI#8: Corrections to Avatar procedures | Ericsson |
S2-2504772 | KI#3: Update to DC interworking with MTSI UE | Ericsson |
S2-2504773 | KI#2: Correcting Information Retrieval | Ericsson |
S2-2504774 | KI#2: Corrections to DC AS initiated Session Update to add BDC to an existing IMS session | Ericsson |
S2-2504775 | KI#2: Corrections to DC AS initiated Standalone ADC Session Creation | Ericsson |
S2-2504776 | KI#2: Corrections to DC AS initiated IMS Session Update Procedures | Ericsson |
S2-2505032 | De-multiplexing ADC to avoid multiplexing ADCs with same stream ID | Vivo |
S2-2505033 | Adding more event filters for ADC media type | Vivo |
S2-2505034 | Update on support of DC interworking | Vivo |
S2-2505035 | Modification on general description for standalone IMS DC session | Vivo |
S2-2505044 | MDC2 endpoint indication for Avatar Represenation downloading | Qualcomm Incorporated, Ericsson |
S2-2505045 | Generlization of MF capabilities registration and discovery | Qualcomm Incorporated |
S2-2505082 | Update IMS SBA description to align with other specifications | Huawei, HiSilicon |
S2-2505083 | Correction on standalone data channel description | Huawei, HiSilicon |
S2-2505084 | Update network centric call flow for Avatar Communication | Huawei, HiSilicon |
S2-2505085 | [DRAFT] Reply LS on MF Capabilities from SA WG4 | Huawei, HiSilicon |
S2-2505177 | Adding BDC Procedure Update | ZTE |
S2-2505178 | Clarification on Standalone DC Procedure | ZTE |
S2-2505179 | Clarification on NRF Service Related to MF | ZTE |
S2-2505180 | Add DC Application Server Description | ZTE |
S2-2505181 | Clarification on MF Profile | ZTE |
S2-2505182 | [DRAFT] Reply LS on Advanced MF capability registration and discovery | ZTE |
S2-2505183 | KI#1: Corrections to IMS Subscribe/Notify Framework Architecture | [Ericsson, Nokia,] ZTE, [Huawei] |
S2-2505203 | Updates on procedure and service of DC interworking via DC AS | China Mobile, Huawei, Hisilicon |
S2-2505204 | Clarification on PSI configuration on UE | China Mobile, Huawei, Hisilicon |
S2-2505205 | Clarification on usage of Avatar ID | China Mobile, Huawei, Hisilicon |
S2-2505206 | Updates on HSS Nhss_ImsEventExposure service | China Mobile, Huawei, Hisilicon |
S2-2505207 | Correction to 3GPP PS Data Off Exempted Services for DC interworking | China Mobile, Huawei, Hisilicon |
S2-2505259 | KI#3: Updates on the ADC Interworking via DC AS procedure | Samsung |
S2-2505260 | MMTel media removal clarification | Samsung |
S2-2505262 | KI#1: Corrections to IMS Subscribe/Notify Framework Architecture | [Samsung], Ericsson, Nokia, ZTE, Huawei |
S2-2505264 | Clarification on DC AS URL for downloading Avatar ID List | Samsung |
S2-2505265 | KI#3: Updates on interworking with MTSI UE procedures | Samsung |
S2-2505266 | [DRAFT] Reply to LS on Automatic Resumption in IMS data channel | Samsung |
TDoc | Title | Source |
---|---|---|
S2-2504508 | LS from CT WG4: LS on Encoding of (S)RTP Multiplexed Media Identification Information | CT WG4 |
S2-2504524 | LS from RAN WG3: Reply LS on uplink rate control | RAN WG3 |
S2-2504535 | LS from SA WG4: Reply LS on Encoding of (S)RTP Multiplexed Media Identification Information | SA WG4 |
S2-2504563 | LS from SA WG4: LS on the accuracy of PDU Set size and data burst size indication | SA WG4 |
S2-2504564 | LS from SA WG4: LS on Indicating Time to the Next Data Burst (TTNB) | SA WG4 |
S2-2504565 | LS from SA WG4: LS to SA WG2 and CT WG4 on N6-Unmarked PDUs | SA WG4 |
S2-2504566 | LS from SA WG4: LS on RTP retransmission | SA WG4 |
S2-2504574 | LS from CT WG4: LS on Transport Level Marking on N3/N9 | CT WG4 |
S2-2504612 | Clarification on provisioning Multi-modal Service ID to NG-RAN | China Mobile |
S2-2504613 | Support of providing MMSID from 5GC to NG-RAN | China Mobile |
S2-2504614 | Clarification of providing MMSID from 5GC to NG-RAN | China Mobile |
S2-2504615 | Clarifications and corrections on usage of MoQ for encrypted media flows | China Mobile |
S2-2504637 | Correction on the Support of MoQ | Nokia |
S2-2504681 | [DRAFT] Reply LS on RTP retransmission | InterDigital, Inc. |
S2-2504697 | Addressing default PDU-set importance | Lenovo, |
S2-2504714 | [DRAFT] Reply LS on RTP Retransmission | China Mobile |
S2-2504717 | KI#4: Resolve the incorrect multiplex support in NOTE | China Mobile |
S2-2504733 | [DRAFT] LS Reply on RTP retransmission | vivo |
S2-2504734 | [DRAFT] LS reply on uplink rate control | vivo |
S2-2504766 | Removal of Editor s Note as CT WG3 is working on UDP options kind value | Nokia |
S2-2504813 | Clarifications on ECN marking for L4S | Apple, Ericsson, T-Mobile USA, Charter Communications |
S2-2504859 | MoQ missing from the Protocol Description | Ericsson |
S2-2504860 | Triggering of Transport Level Marking based on PDU Set Importance in I-SMF | Ericsson |
S2-2504861 | [DRAFT] LS Reply on Transport Level Marking on N3/N9 | Ericsson |
S2-2504862 | Indication of Rate-Adaptable QoS Flows to NG-RAN | Ericsson |
S2-2504863 | Indication of Rate-Adaptable QoS Flows to NG-RAN | Ericsson |
S2-2504864 | Indication of Rate-Adaptable QoS Flows to NG-RAN | Ericsson |
S2-2504937 | [DRAFT] Reply LS on N6-Unmarked PDUs | CATT |
S2-2504938 | [DRAFT] Reply LS on RTP retransmission | CATT |
S2-2504940 | QoS Notification Control of PDU Set QoS with only one direction | CATT, [Huawei, Nokia] |
S2-2504958 | [DRAFT] Reply LS on Transport Level Marking on N3/N9 | Tencent,Tencent Cloud |
S2-2504974 | Alignment of PDU Set based Handling description | Tencent, Tencent Cloud |
S2-2504975 | Clarifications for rate limitation exposure | [Huawei, HiSilicon],Tencent, Tencent Cloud |
S2-2504976 | Clarifications on Expedited Data Transfer | Tencent, Tencent Cloud, Lenovo |
S2-2504985 | Dynamic detection of L4S traffic and enabling of ECN marking for L4S. | Apple, Ericsson |
S2-2505076 | Update on PDU session establishment procedure for MoQ | Huawei, HiSilicon |
S2-2505077 | 23.501 Support of uplink rate control for QoS flows at RAN | Lenovo, ZTE, China Telecom |
S2-2505078 | 23.502 Support of uplink rate control for QoS flows at RAN | Lenovo, ZTE, China Telecom |
S2-2505079 | 23.503 Support of uplink rate control for QoS flows at RAN | Lenovo, ZTE, China Telecom |
S2-2505080 | [DRAFT] Reply LS on Uplink Rate Control | Lenovo |
S2-2505091 | [DRAFT] Reply LS on Transport Level Marking on N3/N9 | LG Electronics |
S2-2505094 | Clarification for the Transport Level Marking on N3/N9 | LG Electronics |
S2-2505095 | [DRAFT] LS Reply on N6-Unmarked PDUs | LG Electronics |
S2-2505096 | Support identification and marking for the N6-unmarked PDUs | LG Electronics |
S2-2505109 | Clarifications for multiplexed media traffic | Huawei, HiSilicon |
S2-2505110 | Clarifications for multiplexed media traffic | Huawei, HiSilicon |
S2-2505111 | Clarifications for control of expedited data transfer | Huawei, HiSilicon |
S2-2505112 | Clarifications for rate limitation exposure | Huawei, HiSilicon |
S2-2505113 | QoS Notification Control of PDU Set QoS with only one direction | [CATT,] Huawei [, Nokia] |
S2-2505114 | Clarifications for PDU Set QoS information based DSCP marking | Huawei, HiSilicon |
S2-2505138 | [DRAFT] LS to SA WG4 on RTP retransmission | Lenovo |
S2-2505144 | Alternative QoS profile handling considering PDU Set QoS parameters | Samsung |
S2-2505145 | [DRAFT] Reply LS on Transport Level Marking on N3/N9 | Lenovo |
S2-2505146 | Discussion: Way forward for Transport Level Marking at I-UPF. | Lenovo, Nokia |
S2-2505147 | Corrections for 23.501 Transport Level Marking on N3/N9 at I-UPF | Lenovo, Nokia |
S2-2505148 | Connect-UDP client functionality of UPF | Samsung |
S2-2505156 | [DRAFT] LS Reply on N6-Unmarked PDUs | SAMSUNG |
S2-2505157 | [DRAFT] LS Reply on RTP retransmission | SAMSUNG |
S2-2505184 | Update the procedures with Multi-modal service ID | Vivo |
S2-2505195 | Correcting references to TS 23.501 clauses | Nokia |
S2-2505197 | Available Bitrate Reporting when the Serving RAN Node Changes | [InterDigital Inc.], Nokia |
S2-2505242 | PDU Set Importance support for N6-unmarked PDUs | Nokia |
S2-2505243 | [DRAFT] Reply LS on N6-Unmarked PDUs | Nokia |
S2-2505244 | Discussion on prioritization of RTP retransmissions in 5GS. | Nokia |
S2-2505245 | [DRAFT] Reply LS on network awareness and QoS handling of RTP retransmissions | Nokia |
S2-2505268 | [DRAFT] Reply LS on RTP retransmission | OPPO |
S2-2505269 | [DRAFT] Reply LS on N6-Unmarked PDUs | OPPO |
S2-2505270 | PDU Set Importance determination for the N6-unmarked PDUs | OPPO |
S2-2505390 | XRM_Ph2_KI1 Update of PDU Set Information Marking witout DL Set QoS | Xiaomi |
S2-2505391 | Discussion on Rate Control . | Xiaomi |
S2-2505392 | XRM_Ph2_Clarification on the DL Protocol Description | Xiaomi |
S2-2505418 | Clarification on Protocol Description for UDP-Option |
TDoc | Title | Source |
---|---|---|
S2-2504522 | LS from RAN WG3: Reply LS on energy saving indication from CN to RAN | RAN WG3 |
S2-2504627 | Removal of Energy Saving indicator from AMF to NG-RAN | LG Electronics |
S2-2504628 | Removal of Energy Saving indicator from AMF to NG-RAN | LG Electronics |
S2-2504629 | [DRAFT] Reply LS on energy saving indication from CN to RAN | LG Electronics |
S2-2504709 | Alignment of Energy indicator in BDT policy | China Mobile |
S2-2504710 | On the report of SMF to EIF for user-plane energy consumption calculation | [Huawei, HiSilicon, NEC], China Mobile, ETRI |
S2-2504711 | Energy consumption information for access type | [Samsung, NTT DOCOMO], China Mobile, ETRI |
S2-2504712 | [DRAFT] Reply LS on energy saving indication from CN to RAN | China Mobile |
S2-2504713 | Removing EN on Energy Saving Indicator provision | China Mobile |
S2-2504812 | Clean up the consumer NF of energy consumption information exposure | Qualcomm Incorporated |
S2-2504814 | Discussion on overlapping PDRs. | Nokia |
S2-2504816 | Clarification on the EventExposure service operation of SMF | Nokia, [Huawei, HiSilicon] |
S2-2504835 | Negotiation for future background data transfer considering energy | NTT DOCOMO, Toyota, KDDI |
S2-2504846 | Discussion on the incoming Reply LS on energy saving indication from CN to RAN. | Nokia, Huawei |
S2-2504847 | [DRAFT] Reply LS on energy saving indication from CN to RAN | Nokia |
S2-2504848 | Removal of ESI to NG-RAN | Nokia, Huawei |
S2-2504852 | Removal of ESI to NG-RAN | Nokia, Huawei |
S2-2504854 | EIF exposure service definition clarification | Nokia |
S2-2504893 | Energy Consumption information collection from SMF. | Ericsson |
S2-2504894 | Use of UPF EventExposure for Energysys | Ericsson |
S2-2504895 | Use of SMF and UPF EventExposure for Energysys | Ericsson |
S2-2504959 | Discussion paper on the Energy saving indicator from CN to RAN according to the RAN WG3 LS response. | ZTE |
S2-2504960 | [DRAFT] Reply LS on energy saving indication from CN to RAN | ZTE |
S2-2504961 | Resolving the EN on the energy saving indicator according to RAN WG feedback | ZTE |
S2-2504962 | Resolving the EN on the energy saving indicator according to RAN WG feedback | ZTE |
S2-2504963 | Adding Energy indication to BDT procedure and service operation | ZTE |
S2-2504964 | Clarification on the BDT policy decision | ZTE |
S2-2504965 | Clarification on retrieving information from OAM | ZTE |
S2-2504966 | Clarification on the UPF Energy Consumption information collection | ZTE |
S2-2504967 | Clarification on the UPF Energy Consumption information collection | ZTE |
S2-2505003 | Clarification on PLMN | LG Electronics |
S2-2505117 | Update the procedure for BDT policy decisions | Vivo |
S2-2505123 | On the report of SMF to EIF for user-plane energy consumption calculation | [Huawei, HiSilicon, NEC], vivo |
S2-2505125 | Energy consumption information for access type | [Samsung, NTT DOCOMO], vivo |
S2-2505130 | EIF exposure service definition clarification | [Nokia],vivo |
S2-2505160 | Clarification on the EventExposure service operation of SMF | Huawei, HiSilicon |
S2-2505161 | Energy consumption information for access type | [Samsung, NTT DOCOMO], Huawei, HiSilicon |
S2-2505162 | Report of SMF to EIF for user-plane energy consumption calculation | Huawei, HiSilicon |
S2-2505163 | Clarification of the lack of supporting EC when DC is used | Huawei, HiSilicon |
S2-2505164 | Energy Consumption information collection procedure | [Nokia, CMCC], Huawei, [Samsung] |
S2-2505247 | Energy consumption information for access type | [Samsung, NTT DOCOMO], vivo |
S2-2505285 | Resolve the EN on Energy Saving Indicator | CATT |
S2-2505286 | Resolve the EN on Energy Saving Indicator | CATT |
S2-2505289 | EIF discvoery and selection | Samsung |
S2-2505290 | EIF discvoery and selection | Samsung |
S2-2505291 | Support of EIF subscription termination | Samsung |
S2-2505293 | On the report of SMF to EIF for user-plane energy consumption calculation | [Huawei, HiSilicon, NEC], Samsung |
S2-2505295 | Corrections for energy saving related AF input on BDT policy negotiation | Huawei, HiSilicon, NTT DOCOMO, KDDI |
S2-2505303 | Update on Energy Saving Indicator handling | Vivo |
S2-2505304 | Update on Energy Saving Indicator handling | Vivo |
S2-2505405 | BDT Energy Negotiation Procedures | Motorola Mobile Com Technology |
TDoc | Title | Source |
---|---|---|
S2-2504515 | LS from RAN WG2: LS on paging ID length | RAN WG2 |
S2-2504516 | LS from RAN WG2: LS on byte-alignment of upper layer data SDU | RAN WG2 |
S2-2504517 | LS from RAN WG2: LS on D2R message size for inventory response | RAN WG2 |
S2-2504523 | LS from RAN WG3: LS on Ambient IoT further progress of RAN WG3 | RAN WG3 |
S2-2504645 | Command Procedure Update. | Ofinno |
S2-2504646 | [DRAFT] Reply LS on Paging ID Length | Ofinno, LLC |
S2-2504647 | Discussion on Paging ID. | Ofinno |
S2-2504718 | AIoT Scope and Architecture General concept clarifications. | NEC |
S2-2504719 | AIoT priority information. | NEC, Futurewei, Lenovo |
S2-2504720 | [DRAFT] LS on Ambient IoT Priority information | NEC |
S2-2504735 | [DRAFT] Reply LS on D2R message size for inventory response | InterDigital Inc. |
S2-2504736 | AMF selection and non-operation Related Procedure . | Vivo |
S2-2504737 | Fix the ENs for AIoT data. | Vivo |
S2-2504738 | Update to NF Services. | Vivo |
S2-2504739 | Update to inventory procedure. | Vivo |
S2-2504740 | Update to command procedure. | Vivo |
S2-2504741 | Update to procedure between AIOTF and NG-RAN for indirect connectivity to align RAN agreement. | Vivo |
S2-2504742 | Update to Filtering Information. | Vivo |
S2-2504743 | ADM related clause update. | Vivo |
S2-2504744 | Update to Protocol Stacks. | Vivo |
S2-2504745 | Update to Network Functions. | Vivo |
S2-2504796 | AIoT assistance information update. | Nokia |
S2-2504797 | AIoT Inventory procedure update. | Nokia |
S2-2504798 | NG-RAN description . | Nokia |
S2-2504803 | Resolution of the follow-on command indication. | Sony |
S2-2504857 | Text on AIoT Device capabilities. | NTT DOCOMO |
S2-2504858 | Text on assistance information to support command procedure. | NTT DOCOMO |
S2-2504870 | Discussion on structure of AIoT data for read/write/disable. | NTT DOCOMO |
S2-2504881 | Text on bank pointer in command. | NTT DOCOMO |
S2-2504884 | Clause 5.3.2: Update on ADM Discovery and Selection. | Ericsson, Nokia |
S2-2504885 | AIoT Data and Approximate D2R Message Size. | Ericsson |
S2-2504886 | Clause 6.2.3: Update on Command Procedure. | Ericsson |
S2-2504887 | Clause 6.2.4 & 7.3.2 & 7.3.3: Update to Align with RAN WG3 on Correlation ID. | Ericsson |
S2-2504888 | Support of Device Location in Ambient IoT. | Ericsson, LG Electronics, Nokia |
S2-2504889 | Clause 5.7.2: Update on AIoT Device Permanent Identifier. | Ericsson |
S2-2504890 | Clause 4.5.6: Update on NRF for ADM. | Ericsson |
S2-2504891 | Clause 4.6: Update on Protocol Stack. | Ericsson |
S2-2504933 | Update for Functional Entities. | China Mobile |
S2-2504934 | Inventory Procedure -- RAN reader(s) abnormal status and follow on command indication . | China Mobile |
S2-2504935 | NG-RAN Node and RAN Reader Selection the NEF performs the location conversion. | China Mobile |
S2-2505004 | Update on Device Permanent Identifier and Filtering Information. | CATT |
S2-2505005 | [Draft] Reply LS on paging ID length . | SA WG2 |
S2-2505006 | Update on Reader Selection. | CATT |
S2-2505007 | Update on Command procedure. | CATT |
S2-2505008 | Update on assistance information. | CATT |
S2-2505009 | [Draft] Reply LS on D2R message size for inventory response . | SA WG2 |
S2-2505010 | Clarification on interaction between NEF and AF. | LG Electronics |
S2-2505011 | Removal of general sub-clause under clause 7. | LG Electronics |
S2-2505014 | EN resolution on AIoT data. | OPPO |
S2-2505015 | RAN Reader Selection Information in AIOTF. | OPPO |
S2-2505016 | Update on Description for Protocol Stack. | OPPO |
S2-2505017 | Update on Assistance information. | OPPO |
S2-2505018 | Update on Inventory procedure. | OPPO |
S2-2505019 | Update on Command procedure. | OPPO |
S2-2505020 | Update on NF description. | OPPO |
S2-2505041 | Enhancements to A-IoT Command Procedure. | Tejas Networks Limited |
S2-2505042 | Enhancements to A-IoT Inventory Service. | Tejas Networks Limited |
S2-2505060 | Architecture Updates for Service Based Interface. | Samsung |
S2-2505061 | AIoT Readers. | Samsung |
S2-2505062 | AIOTF Service Update. | Samsung |
S2-2505063 | Command Type AIoT data Update. | Samsung |
S2-2505064 | NEF Service Update. | Samsung |
S2-2505065 | AIoT Device. | Samsung |
S2-2505066 | AMF Service Update. | Samsung |
S2-2505067 | Protocol Stack Update. | Samsung |
S2-2505072 | Command Procedure Update. | Samsung |
S2-2505075 | Inventory Procedure Update. | Samsung |
S2-2505097 | Update to the AIOTF functionality for inventory procedure. | Lenovo |
S2-2505169 | PCR to TS 23.369: AIoT Service Operation Result Aggregation. | ZTE, Futurewei, Nokia, LG Electronics, Lenovo, InterDigital Inc., CATT, China Mobile |
S2-2505170 | PCR to TS 23.369: Update Protocol Stacks. | ZTE, Nokia, CATT, China Mobile |
S2-2505171 | PCR to TS 23.369: Update Procedures for Follow-on Command. | ZTE |
S2-2505172 | PCR to TS 23.369: Clarification on NG-RAN Node and RAN Reader Selection. | ZTE |
S2-2505173 | PCR to TS 23.369: Clarification on D2R Message Size for Inventory Response. | ZTE |
S2-2505174 | PCR to TS 23.369: AIOTF and NEF Service Definition Update. | ZTE |
S2-2505175 | PCR to TS 23.369: Add Device ID Length Information for Inventory Request. | ZTE |
S2-2505176 | [DRAFT] Reply LS on paging ID length | ZTE |
S2-2505211 | Update on Functional Entities. | China Mobile |
S2-2505212 | Update on AIOTF selection. | China Mobile |
S2-2505213 | Update on NRF services to support AIOTF discovery | China Mobile |
S2-2505214 | Procedure updates with RAN reader(s) abnormal status and follow-on command indication . | China Mobile |
S2-2505225 | Update on ADM Discovery and Selection. | NTT DOCOMO |
S2-2505231 | Update on ADM function. | NTT DOCOMO |
S2-2505298 | Ensuring an inter-operable Ambient IoT system. | Qualcomm Incorporated |
S2-2505300 | Support implementation-specific Read and Write operation through generic AIoT Device specific command. | Qualcomm Incorporated |
S2-2505305 | Update on inventory procedure. | HONOR |
S2-2505311 | D2R message size for inventory response. | InterDigital Inc. |
S2-2505313 | Correction on device filtering information. | InterDigital Inc. |
S2-2505314 | [DRAFT] Reply LS on Paging ID Length | Ericsson |
S2-2505315 | Discussion Paper on Paging ID Length . | Ericsson |
S2-2505320 | AIoT Device Information Configure Service. | InterDigital Inc., Lenovo |
S2-2505322 | Paging re-attempt configuration. | InterDigital Inc. |
S2-2505335 | Protocol Stack Update. | Huawei, HiSilicon |
S2-2505336 | AIOTF and Reader Selection Updates. | Huawei, HiSilicon |
S2-2505337 | NF Selection Update. | Huawei, HiSilicon |
S2-2505338 | Clause 5.4 Assistance Information Update. | Huawei, HiSilicon |
S2-2505339 | Clause 5.7 Identifier Update. | Huawei, HiSilicon |
S2-2505340 | Inventory Procedure Update. | Huawei, HiSilicon |
S2-2505341 | Command Procedure Update. | Huawei, HiSilicon |
S2-2505342 | Update of Procedures between AIOTF and NG-RAN for Indirect Connectivity. | Huawei, HiSilicon |
S2-2505343 | Support of AIoT Device Memory and Associated Commands. | Huawei, HiSilicon |
S2-2505344 | AIoT Device Memory and Associated Commands. | Huawei, HiSilicon, Qualcomm Incorporated |
S2-2505345 | Improve AIoT NF Services. | Huawei, HiSilicon |
S2-2505346 | Support of AIoT device context management. | Huawei, HiSilicon |
S2-2505347 | Support of AIoT Device Temporary ID. | Huawei, HiSilicon |
S2-2505352 | Update to clause 5.7 Identifiers. | HONOR |
S2-2505357 | Update to the Protocol Stack Figures. | Lenovo |
S2-2505358 | Update to the Nnef_AIoT services. | Lenovo |
S2-2505360 | Introduce text to clause 5.7.1 General . | Lenovo |
S2-2505393 | [DRAFT] LS Reply on D2R message size for inventory response | Xiaomi |
S2-2505394 | AIoT_Inventory Response Message Size. | Xiaomi |
TDoc | Title | Source |
---|---|---|
S2-2504929 | NF discovery for signaling data collection related to signaling storm analytics | China Mobile |
TDoc | Title | Source |
---|---|---|
S2-2504505 | LS from CT WG3: LS on AIML_CN issues | CT WG3 |
S2-2504509 | LS from CT WG4: LS on Clarification on SCP data collection | CT WG4 |
S2-2504530 | LS from SA WG3: Reply LS on User Privacy Aspects of LMF-based AI/ML positioning | SA WG3 |
S2-2504541 | LMF re-selection based on AI capability | ZTE |
S2-2504542 | Clarifications on the time interval supporting VFL | ZTE |
S2-2504543 | Clarifications on VFL inference | ZTE |
S2-2504544 | General maintenance of KI#1 | ZTE |
S2-2504545 | General maintenance of KI#4 | ZTE |
S2-2504546 | Output parameters clarifications in KI#3 | ZTE |
S2-2504547 | VFL clients removal during VFL training | ZTE |
S2-2504548 | VFL high level description refinements | ZTE |
S2-2504549 | LMF re-selection based on AI capability | ZTE |
S2-2504550 | VFL client aggregation capability | ZTE |
S2-2504551 | LMF re-selection based on AI capability | ZTE |
S2-2504552 | VFL client aggregation capability | ZTE |
S2-2504553 | Optimization of VFL triggers | ZTE, [Huawei, Hisilicon, vivo, OPPO, Nokia, Futurewei, Samsung, China Mobile, Interdigital] |
S2-2504559 | User consent check amd LCS privacy check for LMF models | Nokia |
S2-2504560 | Parameters for vertical federated learning inference procedure | Nokia |
S2-2504561 | KI#2: VFL services | Nokia |
S2-2504567 | [DRAFT] Reply LS on Questions on stage 2 requirements for AIML_CN | Nokia |
S2-2504575 | LS from CT WG4: LS on Questions on stage 2 requirements for AIML_CN | CT WG4 |
S2-2504577 | LS from RAN WG3: Reply LS on LMF-based AI/ML Positioning for case 3b | RAN WG3 |
S2-2504579 | LS from SA WG5: Reply LS on AI/ML UE sided data collection | SA WG5 |
S2-2504583 | AIML_CN KI#4 Resolve issues for event exposure | Nokia |
S2-2504584 | AIML_CN KI#4 Resolve issues for event exposure and for SCP mitigation actions | Nokia |
S2-2504586 | [DRAFT] Reply to CT WG4 on stage 2 requirements for AIML_CN | Oracle |
S2-2504587 | KI#4: NRF Event Exposure to detect signaling storm | Oracle |
S2-2504598 | [DRAFT] Reply LS on LMF-based AI/ML Positioning for case 3b | Samsung |
S2-2504655 | [DRAFT] LS on clarification on the purpose of user consent | LG Electronics |
S2-2504660 | Clarification on User consent | LG Electronics |
S2-2504661 | Clarification on User consent | LG Electronics |
S2-2504665 | Typo correction in clause 6.2E.4 in TS 23.288 | IPLOOK |
S2-2504667 | Discussion on potential SoH for user consent and privacy in AI/ML-based positioning | Apple |
S2-2504675 | [DRAFT] Reply LS on clarification of SCP data collection from CT WG4 (S2-2504509_C4-251477) | Oracle |
S2-2504696 | Optimization of VFL triggers | [ZTE, Huawei, Hisilicon, vivo, OPPO, Nokia, Futurewei, Samsung, China Mobile, Interdigital], Lenovo |
S2-2504698 | Clarifications for Signalling Storm Analytics | Lenovo |
S2-2504746 | Adding SCP as data source for NWDAF data collection | Huawei, HiSilicon |
S2-2504747 | [DRAFT] Reply LS on Clarification of SCP data collection from CT WG4 | Huawei, HiSilicon |
S2-2504748 | Clarification on data collection from SCP | Huawei, HiSilicon |
S2-2504758 | Correction on Feature ID used in NRF | Huawei, HiSilicon, ZTE |
S2-2504759 | Correction on VFL model retraining | Huawei, HiSilicon |
S2-2504760 | Update to VFL preparation procedure | Huawei, HiSilicon |
S2-2504761 | [DRAFT] LS reply on AIML_CN issues | Huawei, HiSilicon |
S2-2504762 | Correction on AIML_CN issues | Huawei, HiSilicon |
S2-2504763 | Correction on AIML_CN issues | Huawei, HiSilicon |
S2-2504779 | Removal of requirements related to case 2b | Vivo |
S2-2504780 | Removal of requirements related to case 2b | Vivo, [Xiaomi, ZTE, OPPO, Mediatek Inc., Samsung, Nokia, CATT, Ericsson, Qualcomm Incorporated, Huawei, HiSilicon, ERTI] |
S2-2504781 | Clarification on VFL Server registration & discovery | Vivo |
S2-2504782 | Alignment for VFL service operation | Vivo |
S2-2504783 | [DRAFT] Reply LS on Questions on stage 2 requirements for AIML_CN | vivo |
S2-2504784 | CR for 23.501 AIML_CN NRF services expsoure | Vivo |
S2-2504785 | CR for 23.501 AIML_CN SCP related alignment | Vivo |
S2-2504815 | UE LCS privacy check for AI/ML based positioning | Qualcomm Incorporated |
S2-2504829 | ML Model provisioning by OAM for LMF-based AI/ML Positioning | NTT DOCOMO, Ericsson, Nokia, Huawei, HiSilicon, ZTE, Intel |
S2-2504830 | Updates to UE LCS privacy profile | Apple |
S2-2504831 | User Consent vs. LCS Privacy Profile for LMF-based AI/ML Positioning | NTT DOCOMO |
S2-2504832 | Correction of SMF events for QoS and Policy Assistance information | NTT DOCOMO |
S2-2504833 | Exposure of control plane signalling information from NFs | NTT DOCOMO |
S2-2504834 | Correction of NF Signalling Information for Signalling Storm Analytics | NTT DOCOMO |
S2-2504843 | Clarify UE Positioning Capability in data collection from NG-RAN procedure | Qualcomm Incorporated |
S2-2504849 | Resolve ENs on input data for LMF based AI/ML positioning | [CATT, Ericsson, vivo,] Huawei, HiSilicon |
S2-2504850 | Updates of NWDAF discovery and ML model provisioning for LMF-based AI/ML Positioning | Huawei, HiSilicon |
S2-2504851 | Corrections of LMF-based AI/ML positioning indication | Huawei, HiSilicon |
S2-2504853 | Parameters for vertical federated learning inference procedure | [Nokia, Vivo,] Huawei, [Oppo, Samsung] |
S2-2504873 | LMF checking LCS privacy profile before collecting input data and ground truth | Ericsson, AT&T, Lenovo, Intel |
S2-2504878 | Update triggering Case A and some corrections and Resolving ENs for VFL | Ericsson, China Telecom, ZTE |
S2-2504984 | Parameters for PCF event exposure related to signalling load analytics | Nokia |
S2-2504991 | UE LCS privacy check for ground truth data collection and input data storage for ML model training for AI/ML positioning | Intel |
S2-2504992 | UE LCS privacy check for ground truth data collection | Intel |
S2-2504993 | Update ADRF service consumer to include LMF | Intel |
S2-2505013 | LCS privacy profile and user consent | Samsung |
S2-2505030 | Clarification on privacy check for data collection | Xiaomi |
S2-2505052 | Clarification on Signalling Storm Analytics | LG Electronics |
S2-2505249 | Update event exposure service of PCF | China Telecom |
S2-2505250 | Remove misleading content and update consumers in Signalling Storm Analytics | China Telecom |
S2-2505251 | Update triggering Case A and some corrections and Resolving ENs for VFL | [Ericsson], China Telecom, [ZTE] |
S2-2505253 | [DRAFT] LS Reply on LS on AIML_CN issues | LG Electronics |
S2-2505255 | Clarification on the consumer of the DCCF and the MFAF | LG Electronics |
S2-2505256 | DDCF as the consumer of the Nlmf_DataExposure service | LG Electronics |
S2-2505258 | QoS Profile exposed by SMF event exposure | LG Electronics |
S2-2505274 | Update triggering Case A and some corrections and Resolving ENs for VFL | [Ericsson, China Telecom, ZTE], Lenovo |
S2-2505281 | Resolve ENs on input data for LMF based AI/ML positioning | CATT, [Ericsson, vivo, Huawei, HiSilicon] |
S2-2505328 | AIML_CN KI#1 Add DCCF as Client for Nlmf_DataExposure service | Nokia |
S2-2505370 | UE LCS privacy check for ground truth data collection for UE positioning ML model training in NWDAF containing MTLF | Intel |
S2-2505417 | Optimization of VFL triggers | ZTE, Huawei, Hisilicon, vivo, OPPO, Nokia, Futurewei, Samsung, China Mobile, Interdigital |
TDoc | Title | Source |
---|---|---|
S2-2504670 | Correction to implementation of 23.167_CR0377R2 | MCC |
S2-2504674 | Clarifying port ranges and removing EN | Ericsson |
S2-2504794 | Clarification on EHPLMN deployment requirement for Indirect Network Sharing | China Unicom |
S2-2504924 | Inter PLMN GMLC communication via NEF removal | Ericsson, Nokia |
TDoc | Title | Source |
---|---|---|
S2-2504501 | LS from CT WG1: LS on the conclusion of FS_MINT_Ph2 | CT WG1 |
S2-2504502 | LS from CT WG1: LS on clarification for multi-hop UE-to-UE relay discovery using model B | CT WG1 |
S2-2504503 | LS from CT WG3: LS Reply on Optimizations to UPF event subscriptions and reporting | CT WG3 |
S2-2504510 | LS from CT WG4: LS on feedback for IMS resiliency study | CT WG4 |
S2-2504512 | LS from RAN WG2: Reply LS on signalling feasibility of dataset and parameter sharing | RAN WG2 |
S2-2504519 | LS from RAN WG3: Reply LS on NR Femto node shared by PLMN and PNI-NPN | RAN WG3 |
S2-2504521 | LS from RAN WG3: Reply LS on emergency call back and paging | RAN WG3 |
S2-2504525 | LS from RAN WG3: LS on AI/ML Positioning Case 3a | RAN WG3 |
S2-2504526 | LS from SA WG3: LS reply to LS on Security related protocol-specific parameters for N6 delay measurement | SA WG3 |
S2-2504527 | LS from SA WG3: Reply LS on security verification related to NR Femtos | SA WG3 |
S2-2504528 | LS from SA WG3: LS reply on use of 3gpp-Sbi-Originating-Network-Id for Indirect Network Sharing case | SA WG3 |
S2-2504531 | LS from SA WG3: Reply LS on OSAppID usage by App Token use case | SA WG3 |
S2-2504532 | LS from SA WG5: Reply LS on Ambient IoT progress of RAN WG3 | SA WG5 |
S2-2504533 | LS from SA WG4: Remove time service endpoints from MBSTF scope | SA WG4 |
S2-2504534 | LS from SA WG4: LS on Avatar Security Aspects | SA WG4 |
S2-2504562 | [DRAFT] Reply LS on AI/ML Positioning Case 3a | Nokia |
S2-2504568 | 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-2504569 | LS from RAN WG1: LS on signalling feasibility of dataset and parameter sharing | RAN WG1 |
S2-2504573 | LS from CT WG4: LS on Ethernet MA PDU session using MPQUIC-E steering | CT WG4 |
S2-2504594 | [DRAFT] Further Reply LS on signalling feasibility of dataset and parameter sharing | Qualcomm Technologies |
S2-2504597 | [DRAFT] Reply LS on signalling feasibility of dataset and parameter sharing | Samsung |
S2-2504608 | [DRAFT] Reply LS on signalling feasibility of dataset and parameter sharing | Apple |
S2-2504624 | [DRAFT] LS Reply to RAN WG3 on AI/ML Positioning Case 3a | CEWiT |
S2-2504625 | Discussion Paper for LS-Reply on AI/ML Positioning Case 3a from RAN WG3 | CEWiT |
S2-2504635 | LS from SA WG3-LI: LS on LI requirements on IMS Data Channel | SA WG3-LI |
S2-2504654 | [DRAFT] Reply LS on signalling feasibility of dataset and parameter sharing | LG Electronics |
S2-2504666 | [DRAFT] Reply LS on signalling feasibility of dataset and parameter sharing | ZTE |
S2-2504749 | [DRAFT] Reply LS on AI/ML Positioning Case 3a | Huawei, HiSilicon |
S2-2504767 | [DRAFT] Reply LS on emergency call back and paging | Qualcomm |
S2-2504792 | [DRAFT] Response to LS on the conclusion of FS_MINT_Ph2 | China Telecom |
S2-2504793 | SA WG2 specification impact on FS_MINT_Ph2. | China Telecom |
S2-2504877 | [DRAFT] LS Reply on signalling feasibility of dataset and parameter sharing | Ericsson |
S2-2504900 | MPQUIC-E and Ethernet Header Compression . | Ericsson |
S2-2504901 | Handling of MPQUIC-E with EPS interworking | Ericsson, LG Electronics |
S2-2504902 | Handling of MPQUIC-E with EPS interworking | Ericsson |
S2-2504903 | Handling of MPQUIC-E in roaming cases | Ericsson |
S2-2504904 | [DRAFT] Reply LS on Ethernet MA PDU session using MPQUIC-E steering | Ericsson |
S2-2504919 | [DRAFT] Reply LS on the conclusion of FS_MINT_Ph2 | Ericsson |
S2-2504941 | [DRAFT] Reply LS on Ethernet MA PDU session using MPQUIC-E steering | CATT |
S2-2504942 | How to support Ethernet MA PDU Session using MPQUIC-E with one EPS leg and V-SMF. | CATT |
S2-2504943 | Support Ethernet MA PDU Session using MPQUIC-E with 'ethernet' indication to NG-RAN | CATT |
S2-2504944 | Support Ethernet MA PDU Session using MPQUIC-E with 'ethernet' indication to NG-RAN | CATT |
S2-2504947 | [DRAFT] Reply LS on AI/ML Positioning Case 3a | Ericsson |
S2-2504948 | Discussion on Introducing RI-LR. | Ericsson |
S2-2504969 | Clarification on the Averaging Window | ZTE |
S2-2504970 | Clarification on the Averaging Window | ZTE |
S2-2504971 | Clarifying the Femto cell sharing the access control. | ZTE |
S2-2504972 | [DRAFT] Reply LS on AI ML Positioning Case 3a. | ZTE |
S2-2504995 | [DRAFT] Reply LS on the conclusion of FS_MINT_Ph2 | LG Electronics |
S2-2504997 | [DRAFT] Reply LS on Ethernet MA PDU session using MPQUIC-E steering | LG Electronics |
S2-2505025 | Discussion on signalling feasibility of dataset and parameter sharing. | Xiaomi |
S2-2505026 | [DRAFT] LS reply on signalling feasibility of dataset and parameter sharing | Xiaomi |
S2-2505028 | [DRAFT] LS reply on AIML Positioning Case 3a | Xiaomi |
S2-2505058 | [DRAFT] LS Reply on signalling feasibility of dataset and parameter sharing | NTT DOCOMO |
S2-2505088 | [DRAFT] Reply LS on Ethernet MA PDU session using MPQUIC-E steering | Samsung |
S2-2505089 | Clarifications to HR roaming scenarios for supporting MPQUIC-E | Samsung |
S2-2505118 | [DRAFT] Reply LS on signaling feasibility of dataset and parameter sharing | MediaTek Inc. |
S2-2505119 | Clarification on MPQUIC-E functionality in roaming and EPS scenarios | Huawei, HiSilicon |
S2-2505120 | Clarification on MPQUIC-E functionality in roaming and EPS scenarios | Huawei, HiSilicon |
S2-2505121 | [DRAFT] Reply LS on Ethernet MA PDU session using MPQUIC-E functionality | Huawei, HiSilicon |
S2-2505140 | NR Femto cell shared by PLMN and PNI-NPN | Samsung |
S2-2505186 | MA PDU Session with Ethernet type using MPQUIC-E for interworking | MediaTek Inc. |
S2-2505279 | [DRAFT] Reply LS on signalling feasibility of dataset and parameter sharing | CATT |
S2-2505280 | [DRAFT] Reply LS on AI/ML Positioning Case 3a | CATT |
S2-2505308 | Correction for MA PDU Session of type Ethernet with MPQUIC-E steering functionality for Roaming scenarios | Nokia, LGE |
S2-2505309 | [DRAFT] Reply LS on Ethernet MA PDU session using MPQUIC-E steering | Nokia |
S2-2505351 | Corrections for multi-hop UE-to-UE relay discovery using model B | Qualcomm Incorporated |
S2-2505359 | [DRAFT] Reply LS on clarification for multi-hop UE-to-UE relay discovery using model B | Qualcomm Incorporated |
S2-2505362 | Clarifications on other protocols used for N6 delay measurements | Nokia |
S2-2505381 | [DRAFT] Reply LS on signalling feasibility of dataset and parameter sharing | Nokia |
S2-2505382 | PSAP emergency callback interaction with PSM | Vodafone |
TDoc | Title | Source |
---|---|---|
S2-2504504 | LS from CT WG3: LS on Extending Charging Support in 5GC | CT WG3 |
S2-2504513 | LS from RAN WG2: Reply LS on paging capability loss issue | RAN WG2 |
S2-2504514 | LS from RAN WG2: LS on LP-WUS subgrouping progress | RAN WG2 |
S2-2504576 | LS from RAN WG2: Reply LS on LP-WUS subgrouping | RAN WG2 |
S2-2504687 | [DRAFT] Reply LS on Extending Charging Support in 5GC | Nokia |
S2-2504688 | Clarification of Note related to CHF Group ID and CHF Set ID | Nokia |
S2-2504757 | [DRAFT] LS Reply on Extending Charging Support in 5GC | Huawei, HiSilicon |
S2-2504868 | [DRAFT] LS reply on Extending Charging Support in 5GC | Ericsson |
S2-2504869 | CHF group ID corrections | Ericsson, Verizon |
S2-2504913 | Clarification of eDRX application with emergency service | Ericsson, AT&T, Qualcomm Incorporated |
S2-2504914 | Clarification of eDRX application with emergency service | Ericsson, AT&T, Qualcomm Incorporated |
S2-2504915 | Clarification of eDRX application with emergency service | Ericsson, AT&T, Qualcomm Incorporated |
S2-2504916 | Clarification on emergency PDU session release | Ericsson, AT&T, Qualcomm Incorporated, MediaTek Inc |
S2-2504917 | Clarification on emergency PDU session release | Ericsson, AT&T, Qualcomm Incorporated, MediaTek Inc |
S2-2504918 | Clarification on emergency PDU session release | Ericsson, AT&T, Qualcomm Incorporated, MediaTek Inc |
S2-2505027 | Discussion on AIML Positioning Case 3a. | Xiaomi |
S2-2505029 | Procedures of data collection for NG RAN-sided models | Xiaomi |
S2-2505127 | EDRX for UE in RRC Inactive with emergency PDU Session | Huawei, HiSilicon |
S2-2505128 | EDRX for UE in RRC Inactive with emergency PDU Session | Huawei, HiSilicon |
S2-2505129 | EDRX for UE in RRC Inactive with emergency PDU Session | Huawei, HiSilicon |
S2-2505143 | Procedures for Positioning Information Collection for NG-RAN | CEWiT |
S2-2505241 | Clarification on MBS broadcast service area | CATT |
S2-2505361 | Multi-RAN-vendor support for paging of LP-WUS UEs | Vodafone |
S2-2505379 | [DRAFT] Response to Reply LS on paging capability loss issue | Vodafone |
S2-2505419 | CHF group ID corrections | Ericsson, Verizon |
TDoc | Title | Source |
---|---|---|
S2-2504588 | WT1: Solution for providing IMS voice over GEO via Control Plane. | Qualcomm Incorporated |
S2-2504589 | WT1: Solution for providing IMS voice over GEO via User Plane. | Qualcomm Incorporated |
S2-2504591 | WT1: Solution for IMS signaling performance optimization to support voice over GEO . | Qualcomm Incorporated |
S2-2504596 | FS_5GSAT_Ph4_ARC New Sol: Support of IMS Voice Call over NB-IoT NTN | Skylo Technologies |
S2-2504605 | LS from ITU-T SG17: LS on establishment of a new work item Technical Report ITU-T TR.FMSC-IMT2030 'Security technologies of fixed, mobile and satellite convergence for IMT-2030 networks' | ITU-T SG17 |
S2-2504651 | KI#X: New Solution: SDP negotiation with 100 trying for IMS NB-IoT GEO Access. | CSCN |
S2-2504652 | New solution: IMS call setup procedure without pre-condition for voice over GEO satellite. | OPPO, MediaTek Inc., vivo |
S2-2504659 | 23.700-19: New solution of combined CP/UP in a PDN connection for KI#1. | China Telecom |
S2-2504662 | 23.700-19: New solution of setup UP bearer for vioce for KI#1. | China Telecom |
S2-2504663 | 23.700-19: Discussion and Interim conclusion for UE-SAT-UE communication for non-IMS services. | China Telecom, Thales, TNO, Eutelsat, Novamint |
S2-2504664 | 23.700-19: New solution to support ground fallback of UE-Satellite-UE communication. | China Telecom |
S2-2504669 | New solution for KI#2: IMS procedure optimization for IMS voice over GEO satellite. | IPLOOK |
S2-2504678 | RoHC Issues | Qualcomm |
S2-2504679 | [DRAFT] LS on Issues related to RoHC for support of IMS voice over NB-IoT NTN connected to EPC | Qualcomm |
S2-2504682 | Solution for IMS optimization to reduce call setup time. | Vivo, MediaTek Inc., ZTE, OPPO |
S2-2504791 | KI #1: New Sol: U-plane-based IMS service via NB-IoT access. | Nokia |
S2-2504801 | Key issue for WT#2: UE-SAT-UE communication enhancement for NR NTN NGSO constellation with feeder link available. | Transsion Holdings |
S2-2504908 | New Sol: Reuse existing LTE solution to establish IP-CAN for IMS voice over NB-IoT (GEO) . | Ericsson |
S2-2504932 | Solution for IMS signaling performance optimization to support voice over GEO. | China Mobile |
S2-2504979 | KI#3: Support for emergency calls over NB-IoT NTN. | Qualcomm Incorporated |
S2-2505023 | KI#2.2 Solution: UE-Sat-UE communication for non-IMS service via Onboard I-UPFs. | China Mobile |
S2-2505036 | Discussion on call setup estimation | vivo |
S2-2505037 | Methodology of call setup time estimation for GEO voice call. | Vivo |
S2-2505038 | Solution for call setup based on I1. | Vivo |
S2-2505046 | KI#4: Support for location information for emergency calls over NB-IoT NTN. | Qualcomm Incorporated |
S2-2505049 | KI#1: New Sol: Optimisation of IMS voice call initiation over NB-IoT (GEO) when the UE is in Idle. | LG Electronics |
S2-2505068 | Discussion paper on CP/UP options and checkpoint | vivo |
S2-2505071 | Solution for Location service for IMS emergency call. | Vivo |
S2-2505073 | Solution for UP-based NB-IoT (GEO) supporting IMS voice. | Vivo, MediaTek Inc, Spreadtrum |
S2-2505074 | Solution for CP-based NB-IoT (GEO) supporting IMS voice. | Vivo |
S2-2505081 | Solution for Pre-established Dual DRB Support for IMS Voice over NB-IoT via GEO Satellite. | ZTE, MediaTek Inc |
S2-2505086 | IMS Enhancement Solution for GEO NB-IoT NTN Access with Rate and Call Setup Time Constraints. | ZTE, vivo |
S2-2505087 | KI#1: New Sol: IMS PDN connection with both IP EPS bearer and non-IP EPS bearer. | MediaTek Inc |
S2-2505090 | KI#2: New Sol: CST reduction by pre-configuring SDP parameters. | MediaTek Inc., vivo, OPPO |
S2-2505092 | KI#2: New Sol: IMS call optimization for NB-IoT (GEO). | Mediatek Inc. |
S2-2505115 | Interim conclusion for KI#2 UE-SAT-UE communication via UPF only onboard satellite for non-IMS services. | Nokia |
S2-2505116 | 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-2505122 | KI#1: New Sol: Support of IMS voice over GEO via NB-IoT NTN connected to EPC using single PDN connection with hybrid CP and UP bearers. | MediaTek Inc |
S2-2505153 | New solution - SIP procedure optimization for IMS voice call via NB-IoT GEO Source: Huawei, HiSilicon. | New solution - SIP procedure optimization for IMS voice call via NB-IoT GEO Source: Huawei, HiSilicon |
S2-2505154 | [New Sol] Connection setup for NB-IoT IMS call over GEO. | Huawei, HiSilicon |
S2-2505158 | KI #1: New Sol for UP based IMS voice call over NB-IoT(Geo). | Samsung |
S2-2505159 | KI #1: New Sol for CP based IMS voice call over NB-IoT(Geo). | Samsung |
S2-2505188 | 23.700-19: Key issue for WT#2.2: UE-SAT-UE communication via UPF onboard satellite for non-IMS services. | ETRI |
S2-2505189 | 23.700-19: New Solution for WT#2.2: UE-SAT-UE communication via UPF onboard satellite for non-IMS services. | ETRI |
S2-2505198 | KI#1: New Sol: CP based solution for supporting IMS voice over NB-IoT via GEO. | Xiaomi |
S2-2505199 | KI#3: New Sol: Supporting of IMS emergency call over NB-IoT GEO. | Xiaomi |
S2-2505200 | KI#4: New Sol: Location Provision for IMS emergency call over NB-IoT via GEO. | Xiaomi |
S2-2505226 | KI #1: Support of IMS voice over NB-IoT NTN via GEO connecting to EPC using user plane. | CATT |
S2-2505227 | New solution of optimized IMS call procedure for GEO NB-IoT access. | CATT |
S2-2505228 | KI #3, New Sol: IMS emergency service for NB-IoT device using GEO satellite access to EPC. | CATT |
S2-2505229 | KI #4, New Sol: EPC-NI-LR based location service for emergency situation. | CATT |
S2-2505230 | New Solution for UE-SAT-UE communication via 5G-LAN. | CATT |
S2-2505267 | New solution: Emergency QoS awareness at eNB for IMS Emergency Call via Control Plane. | OPPO |
S2-2505310 | Analysis on Call Setup Time for IMS Voice over GEO Satellite | Samsung Electronics GmbH |
S2-2505318 | Protocol Overhead for IMS voice transmission | Samsung |
S2-2505319 | KI #2: New Sol: Signaling optimizations for voice over GEO sessions. | Nokia |
S2-2505334 | KI#1 New Solution: QoS Mapping for IMS voice service over GEO satellite. | NTT DOCOMO |
S2-2505367 | KI#1: New Sol: Support of CP/UP combination and QoS for IMS voice service over GEO satellite. | NTT DOCOMO |
S2-2505368 | KI#1: New Sol: Support of capability exchange and NAS timer adjustment for IMS voice service over GEO satellite. | NTT DOCOMO |
S2-2505369 | KI#1: New Sol: Support of PDN connection where packets are transported as Non-IP over the GEO satellite and seen as IP by IMS nodes. | NTT DOCOMO |
TDoc | Title | Source |
---|---|---|
S2-2504592 | TR 23.700-14: FS_Sensing_ARC new solutions on sensing service operations | Qualcomm Incorporated |
S2-2504600 | Terminology Update | OPPO |
S2-2504601 | New Solution for KI#1: Sensing Function distribution in the general architecture | OPPO |
S2-2504602 | Key issue for WT#2: Sensing Entity Authorization | OPPO |
S2-2504603 | New Solution for KI#4: Data Collection from multiple sources | OPPO |
S2-2504604 | New Solution for KI#5: Sensing result delivery to the consumer | OPPO |
S2-2504606 | LS from ITU-T SG17: LS on the establishment of a new work item ITU-T X.s-isac 'Security guidelines for integrated sensing and communication in IMT-2020 networks and beyond' | ITU-T SG17 |
S2-2504609 | New Solution Key Issue #1: System Architecture to Support Sensing | Rakuten Mobile, NIST |
S2-2504610 | Requirements for storage and differentiation of sensing data | AT&T Services, Inc. |
S2-2504671 | New solution to KI#4 on sensing data and the associated information transport. | OPPO |
S2-2504672 | New solution to KI#3 on Sensing Entity discovery and selection. | OPPO |
S2-2504673 | 23.700-14: Update to KI#2 on Sensing area authorization. | OPPO |
S2-2504768 | New Solution on Sensing Request and Exposure Procedure. | Apple |
S2-2504820 | KI#4 New Sol: Sensing Data and the Associated Information Collection and Transport . | Samsung |
S2-2504821 | New solution for KI#1-6_Enable 5GS to support sensing services. | Vivo |
S2-2504822 | New solution for KI#3_Sensing function and entity discovery and selection. | Vivo |
S2-2504823 | New solution for KI#2_Service authorization and revocation. | Vivo |
S2-2504826 | Revised TR Skeleton for FS_Sensing_ARC | Apple, Xiaomi |
S2-2504839 | New Sol: General procedure to enable sensing service. | China Telecom |
S2-2504840 | KI#3, New Sol: Sensing Entity and Sensing Function Discovery and (Re-)Selection. | China Telecom |
S2-2504841 | Terminology Update. | China Telecom |
S2-2504883 | Term update for Sensing Function. | China Mobile |
S2-2504892 | New solution for KI#2 Service authorization and revocation. | China Mobile |
S2-2504898 | New Solution for KI#3 Discovery and selection of sensing entities. | China Mobile |
S2-2504899 | New solution for KI#4 Sensing Data Collection and Transportation. | China Mobile |
S2-2504910 | New solution for KI#5: Support sensing result exposure to AF. | China Mobile |
S2-2504912 | New Solution for KI#6 Configuration Parameter Provisioning of Sensing Entities. | China Mobile |
S2-2504927 | KI#3, New Sol: Sensing Function Registration, Discovery and Selection. | Futurewei |
S2-2504936 | New solution for KI#3 and #6. | Sony |
S2-2504945 | KI#5, a new solution: Baseline for exposing sensing results to an AF. | Ericsson |
S2-2504949 | Update the definition and Architectural Requirements. | ZTE |
S2-2504950 | New solution for KI#1, the Architecture and high level procedure. | ZTE |
S2-2504951 | KI#4, a new solution for the sensing data collection and transport. | ZTE |
S2-2504952 | KI#3, a new solution for Sensing Entity and Sensing Function Discovery and (Re-)Selection. | ZTE |
S2-2504953 | KI#2, a new solution for the sensing service authorization. | ZTE |
S2-2505039 | Solution for KI#1: System Architecture to support sensing . | Tejas Networks Limited |
S2-2505040 | Solution for KI#2: Authorization and Revocation to Support Sensing Service . | Tejas Networks Limited |
S2-2505043 | KI#1&2, NewSol: Authorization to support sensing service request from UE and sensing result exposure to UE. | LG Electronics |
S2-2505098 | Solution for KI#3: Sensing Entity discovery and selection. | Lenovo |
S2-2505131 | Solution for KI#3: Sensing Entity and Sensing Function Discovery. | CEWiT |
S2-2505134 | Solution for KI#5: Exposure of Sensing Results. | CEWiT |
S2-2505135 | Solution for KI#1: System Architecture to support sensing . | Lenovo, China Telecom |
S2-2505136 | Solution for KI#3: Sensing Function discovery and selection . | Lenovo |
S2-2505137 | Solution for KI#2: Authorization and Revocation of sensing service request. | Lenovo |
S2-2505190 | High-level Procedure and Architecture of the Sensing service. | Huawei, HiSilicon, CAICT |
S2-2505191 | KI#2, New Sol: Authorization and Revocation to Support Sensing Service. | Huawei, HiSilicon, CAICT |
S2-2505192 | KI#3, New Sol: Sensing Entity and Sensing Function Discovery and (Re-)Selection . | Huawei, HiSilicon, CAICT |
S2-2505193 | KI#5, New Sol: Sensing Result Exposure. | Huawei, HiSilicon |
S2-2505194 | 23.700-14: New Solution for Key Issue#5: Sensing Result Exposure. | ETRI |
S2-2505215 | 23.700-14: KI#1_New Solution_System Architecture to Support Sensing. | Samsung |
S2-2505217 | 23.700-14: KI#2_New Solution_ Authorization and Revocation to Support Sensing Service. | Samsung |
S2-2505219 | 23.700-14: KI#3_New Solution_ Sensing Entity and Sensing Function Discovery and (Re-)Selection. | Samsung |
S2-2505221 | 23.700-14: KI#5_New Solution_ Sensing Result Exposure. | Samsung |
S2-2505222 | 23.700-14: KI#6_New Solution_Configuration Parameter Provisioning of Sensing Entities. | Samsung |
S2-2505263 | KI#2, New Sol: Authorization Information Update by UE. | Toyota Motor Corporation, BUPT |
S2-2505271 | New solution for KI#1: New sensing NFs and functionalities. | ETRI |
S2-2505272 | New solution for KI#3: Discovery and selection of sensing entities and functions. | ETRI |
S2-2505273 | New solution for KI#4: Sensing data collection, transport, and processing. | ETRI |
S2-2505276 | Sensing result exposure towards sensing service consumer . | Lenovo |
S2-2505288 | KI#1 New Solution: AMF-Inclusive Framework for 5GC Sensing. | NTT DOCOMO |
S2-2505312 | KI#2, New Sol: Authorization Information Update by AF. | Toyota Motor Corporation, BUPT |
S2-2505323 | KI#2, New Sol: Authorization of Sensing Service Requests. | Toyota Motor Corporation, BUPT |
S2-2505325 | KI#4, New Sol: Collection of Sensing data and its transport over the control plane. | Toyota Motor Corporation, BUPT |
S2-2505326 | KI#1, New Sol: architecture for sensing service enablement per sensing service area. | Interdigital |
S2-2505327 | KI#2, New Sol: UE initiated sensing service request. | Interdigital |
S2-2505329 | KI#5, New Sol: Procedures for periodic sensing request with target service area or target UE. | Interdigital |
S2-2505380 | 5GS Architecture Enhancements for Integrated Sensing. | Intel |
S2-2505397 | KI #1, New Sol: Sensing Architecture. | CATT |
S2-2505398 | KI #3, New Sol: Discovery and (Re-)selection of SF and Sensing Entity. | CATT |
S2-2505399 | KI#4, New Sol: Sensing Data Collection and Transport | CATT |
S2-2505400 | KI #5, New Sol: One time and event triggered sensing result exposure. | CATT |
S2-2505412 | Editorial corrections for TR 23.700-14 . | Xiaomi, |
S2-2505413 | New solution for KI#2 Authorization and revocation based on sensing service conditions . | Xiaomi |
S2-2505414 | New solution for 3rd party initiates the Sensing Service. | Xiaomi |
S2-2505415 | New solution for KI#2 Revocation of an ongoing Sensing Service . | Xiaomi |
S2-2505429 | Authorization and Parameter Configuration of ISAC. | Nokia, Nokia Shanghai Bell |
S2-2505430 | NRF Solution to Key Issue #3. | Nokia, Nokia Shanghai Bell |
S2-2505431 | Solutio to KI #1 New Sol ISAC System Architecture. | Nokia, Nokia Shanghai Bell |
S2-2505432 | Solution to KI#5 Sensing Service Exposure. | Nokia, Nokia Shanghai Bell |
TDoc | Title | Source |
---|---|---|
S2-2504511 | LS from RAN WG2: LS on AI/ML UE sided data collection | RAN WG2 |
S2-2504554 | UE policy enhancement to support data collection from UE. | ZTE |
S2-2504555 | NF selection and triggers for UE data collection. | ZTE |
S2-2504558 | New Solution for KI#1: Establish the UP connection between UE and 5GC to support the standardized UE data collection. | OPPO |
S2-2504570 | LS from TSG RAN: LS on AI/ML UE sided data collection | TSG RAN |
S2-2504585 | Solution proposal for Key Issue #2 | Nokia |
S2-2504593 | New Solution for KI#1: UP based UE data collection solution for AI/ML NR air interface operation. | Qualcomm Incorporated |
S2-2504599 | New Solution for KI#1: Discovery, selection and authorization of data collection UE | OPPO |
S2-2504607 | [DRAFT] Reply LS on AI/ML UE sided data collection | Apple |
S2-2504649 | New Solution for KI#1: UE sided data collection and transfer over UP. | |
S2-2504653 | KI#1, Solution#2 Update: resolving some editor s notes . | LG Electronics |
S2-2504668 | New Solution for KI#2: AI/ML-assisted UP traffic pattern and behaviour analysis. | SK Telecom, Boost Mobile Network, China Mobile, Deutsche Telekom, KDDI, KPN N.V., NTT DOCOMO, Rakuten Mobile, Verizon |
S2-2504700 | KI#1, New Sol: AF provisioning of UE data collection requirements with NEF support. | Apple |
S2-2504701 | Updates of Architectural Assumptions and Requirements for FS_AIML_CN_Ph2. | Vivo |
S2-2504702 | KI#1: Update Solution#1. | Vivo |
S2-2504703 | KI#2: New Solution Collocation of UPF and NWDAF containing AnLF to support efficient performance of User Plane. | Vivo |
S2-2504704 | [DRAFT] Reply LS on AI/ML UE sided data collection | Vivo(rapporteur), Samsung(rapporteur) |
S2-2504721 | PCR to TR 23.700-04: KI#1 High-level UE data collection procedure and interim agreements. | Nokia |
S2-2504750 | KI#1, New Solution: CN triggers UE Data Collection and Transfer. | Huawei, HiSilicon |
S2-2504751 | KI#1, New Solution: RAN Assisted UE Data Collection. | Huawei, HiSilicon |
S2-2504764 | KI#2: New solution for AIML assisted user plane performance enhancement for normal traffic. | Huawei, HiSilicon |
S2-2504765 | KI#2, New Solution: Traffic Pattern Analytics Supporting Efficient Performance of UP . | Huawei, HiSilicon |
S2-2504800 | KI#1: New Solution UE-side model training data collection via DCCF and ADRF in CN over UP. | Transsion Holdings |
S2-2504804 | [DRAFT] Reply LS on AI/ML UE sided data collection | OPPO |
S2-2504817 | KI#2: Solution for user plane analytics via efficient UP data collection. | NTT DOCOMO |
S2-2504825 | KI#2 New Sol: Support of user plane management analytics . | Samsung |
S2-2504836 | KI#1: New Sol: UP-based UE data collection. | NTT DOCOMO |
S2-2504842 | TR skeleton update. | Samsung (rapporteur), vivo (rapporteur) |
S2-2504844 | KI#1 Update of Solution #3: Addressing Editor s Notes. | Lenovo |
S2-2504871 | [DRAFT] Reply LS on AI/ML UE sided data collection | Ericsson |
S2-2504872 | KI#1 solution using the generic architecture for collecting and exposing the collected UE data. | Ericsson |
S2-2504874 | Discussion paper on UE data collection solution between UE and 5GC. | Ericsson |
S2-2504875 | (KI#2) Solution based on analysis of abnormal user plane traffic. | Ericsson |
S2-2504876 | (KI#2) Solution based on analysis of user plane traffic towards malicious and/or forbidden sites. | Ericsson |
S2-2504926 | New Solution for KI#1 on 5GC Support for UE Data Collection over the User Plane . | China Mobile |
S2-2504928 | New Solution for KI#2 on user plane traffic pattern and behavior analysis . | China Mobile |
S2-2504978 | KI #1, New Sol #X: UE data transfer over UP based on guidance for URSP. | MediaTek Inc. |
S2-2504980 | KI#2, New Sol: NWDAF-assisted Analytics for Efficient User Plane Performance. | ETRI |
S2-2504990 | KI#1 New Sol: Support of AIML data transfer via UP with AMF involvement. | Samsung |
S2-2504999 | New Solution for KI#1: Data transfer over UP connection for UE data collection. | China Telecom |
S2-2505002 | New Solution to KI#1: General Framework for UE Data Collection over UP. | ETRI |
S2-2505022 | KI#1, New Sol #X: Data collections for UE-side model training via user plane. | Tencent, Tencent Cloud |
S2-2505031 | Solution for WT#1 Standardized transfer of standardized data over UP for UE data collection. | Xiaomi |
S2-2505047 | [DRAFT] Reply LS on AI/ML UE sided data collection | InterDigital France R&D, SAS |
S2-2505048 | New Solution for UE-side Data Collection and Transfer over UP. | InterDigital Inc |
S2-2505059 | Pseudo-CR on New Solution Key Issue #2/Use Case #1: AI/ML-assisted user plane traffic pattern and behaviour analysis to support efficient performance of User Plane . | Rakuten Mobile, NIST |
S2-2505141 | KI#2_new solution of user plane traffic pattern and behaviour detection and policy update based on NWDAF analysis. | CATT |
S2-2505248 | New Solution of KI#2: a new Analytics ID to improve user plane performance. | China Telecom |
S2-2505277 | KI#1 new solution for UE data collection and transfer. | CATT |
S2-2505278 | [DRAFT] Reply LS on AI/ML UE sided data collection | CATT |
S2-2505416 | [DRAFT] Reply LS on AI/ML UE sided data collection |
TDoc | Title | Source |
---|---|---|
S2-2504630 | KI#1 new solution: Consumption energy source exposure | NEC |
S2-2504631 | KI#2 new solution: UE energy saving service in low UE battery | NEC |
S2-2504695 | KI#1, new solution: Energy consumption calculation enhancements. | Vivo |
S2-2504706 | New solution for key issue #3: UPF (re)selection based on energy related information. | China Mobile |
S2-2504707 | Energy Consumption information assisted Policy Update. | China Mobile |
S2-2504708 | [DRAFT] LS on static energy consumption estimation | China Mobile |
S2-2504788 | KI #3, New Sol: AMF (re-)selection based on energy related information. | Vivo |
S2-2504789 | KI#2 new solution for URSP generation/update considering the energy related information. | Vivo |
S2-2504818 | KI#2, Sol#6: Addressing ENs on policy control. | Apple |
S2-2504837 | KI#1: New Sol: Energy Consumption estimation considering idle energy consumption. | NTT DOCOMO |
S2-2504838 | KI#3: New Sol: UP path adjustment based on energy objective. | NTT DOCOMO |
S2-2504856 | KI#3 new solution: Energy-aware NF and path selection. | Nokia |
S2-2504896 | KI #3, New Solution: Report current and anticipated energy related information in the NF profile. | Ericsson |
S2-2504897 | New Solution for Differentiated Charging when Network Performs Service Adjustment. | Ericsson |
S2-2504954 | KI#1, a new solution for renewable energy information collection and exposure. | ZTE |
S2-2504955 | KI#2, a new solution for Qos adjustment. | ZTE |
S2-2504956 | KI#3, new solution for NF selection. | ZTE |
S2-2504957 | KI#3, new solution for the UP adjustment. | ZTE |
S2-2505012 | KI#1, NewSol: Enhancement of energy related information exposure. | LG Electronics |
S2-2505024 | KI#1: discussion paper for the energy consumption calculation. | Vivo, Lenovo |
S2-2505124 | Skeleton update for Clause 7 according to new template. | China Telecom, Lenovo |
S2-2505166 | KI#1, New Sol: Renewable energy per UE, PDU session and SDF. | Huawei, HiSilicon |
S2-2505167 | KI#3, New Sol: NF selection profile. | Huawei, HiSilicon |
S2-2505168 | WT#3: NF selection profile. | Huawei, HiSilicon |
S2-2505185 | KI3 new solution: UPF discovery based on energy related information. | NEC |
S2-2505187 | KI3 New solution: UP path adjustment based on energy related information. | NEC |
S2-2505202 | Solve ENs in solution 4 . | MediaTek Inc. |
S2-2505234 | KI#2: New Solution on Session control based on EIF notification. | Samsung |
S2-2505246 | KI#2: New Solution on access control based on EIF notification. | Samsung |
S2-2505275 | KI#2: proposed agreement of principles. | Nokia |
S2-2505282 | KI#1#2 new solution to improve energy consumption calculation and energy saving control. | CATT |
S2-2505283 | KI#2 solution update for policy control based on notifications from the EIF. | CATT |
S2-2505284 | KI#3 new solution for UP path adjustment based on energy related information. | CATT, KDDI, Toyota |
S2-2505287 | Solution for KI#2: Support of policy adjustments. | MediaTek Inc. |
S2-2505294 | Solution for KI#3: Support of UP path adjustments for the UE. | MediaTek Inc. |
S2-2505296 | KI#2: New Solution on Energy Control for Network Slice. | Samsung |
S2-2505299 | KI#3: New solution on Energy-aware NF discovery/selection mechanism. | Samsung |
S2-2505306 | KI#2, sol#5 update: Service adjustments for network energy saving based on AF request and energy information. | Vivo |
S2-2505321 | KI#2 new solution Dynamic service adjustments based on review of EC Events from EIF. | Nokia |
S2-2505324 | KI#2 new solution Dynamic service adjustments based on Energy Behaviour Analytics. | Nokia |
S2-2505428 | Key Issue #3 New Solution: UP path adjustment based on energy consumption information. | InterDigital Inc. |
TDoc | Title | Source |
---|---|---|
S2-2504556 | New WID on Model Evaluation Metrics Enhancement. | ZTE |
S2-2504557 | Model Evaluation Metrics Enhancement. | ZTE |
S2-2504611 | WID: TEI20_DAMUP - Deferred AM and UE Policies in the 5GC | Oracle, Verizon |
S2-2504641 | New WID on New Exposable Event: reporting changes on the GPSI-SUPI associations. | Nokia, NTT DOCOMO |
S2-2504642 | New Exposable Event: reporting changes on the GPSI-SUPI associations | Nokia, NTT DOCOMO |
S2-2504643 | New WID on Documenting tools to support Fixed Wireless Access (FWA). | Nokia, |
S2-2504644 | Documenting tools to support Fixed Wireless Access (FWA) | Nokia |
S2-2504677 | TEI20: Resolving suboptimal user QoE with IETF s SCONE in UPF. | META |
S2-2504752 | New WID: TEI20_5IOPS Isolated Operation for Public Safety in 5G System (5IOPS). | Huawei, HiSilicon |
S2-2504753 | Implementation and deployment guildlines of the Isolated Operation for Public Safety in 5GS (5IOPS) | Huawei, Hisilicon |
S2-2504754 | Procedures of the Isolated Operation for Public Safety in 5GS (5IOPS) | Huawei, Hisilicon |
S2-2504809 | TEI20 Support of NSSAA in EPS | Nokia, T-Mobile USA, Oracle, Orange |
S2-2504810 | DRAFT CR on introducing NSSAA over EPC | Nokia, T-Mobile USA, Oracle, Orange |
S2-2504811 | New WID on Support of NSSAA in EPS . | Nokia, T-Mobile USA, Oracle, Orange . |
S2-2504819 | New WID: ECN marking for L4S in the UE . | Apple |
S2-2504824 | New WID on eRG without USIM. | China Unicom |
S2-2504827 | Clarifying the support of Non-USIM eRG accessing 5GC/EPC via ePDG | China Unicom, Huawei, Hisilicon |
S2-2504845 | New TEI20 proposal on support of distributed inference for VFL. | Lenovo |
S2-2504930 | Discussion for TEI20 WID proposal on Dynamic Network Identity. | China Mobile |
S2-2504931 | Dynamic Network Identity. | China Mobile |
S2-2504973 | TEI 20 - VFL Distributed Inference Motivation | Lenovo |
S2-2504981 | New WID: TEI20_5MBS_Roam; Adding support for Roaming UEs to receive 5MBS. | Nokia |
S2-2504982 | MBS Roaming | Nokia |
S2-2504983 | MBS Roaming | Nokia |
S2-2505099 | Enhancement of Non-3GPP Device Identifiers | Huawei, HiSilicon |
S2-2505139 | New SID on MANET Multicast for 5G ProSe Multi-Hop UE-to-UE Relay. | KPN N.V. |
S2-2505235 | New WID on providing per-subscriber Allowed MAC addresses from UDM. | Samsung |
S2-2505252 | Support of allowed MAC addresses in SM subscription data in UDM | Samsung |
S2-2505257 | Support of VLAN handling instructions in SM subscription data | Samsung |
S2-2505297 | New WID: TEI20_NEMO on NR to LTE mobility restriction | NTT DOCOMO, Nokia |
S2-2505333 | New WID on support for Ethernet PDU session for backhauling of MWAB . | Qualcomm Incorporated |
S2-2505349 | Support of Ethernet type of BH PDU Session for MWAB | Qualcomm Incorporated |
S2-2505350 | Support of Ethernet BH PDU Sessions for MWAB | Qualcomm Incorporated |
S2-2505356 | New WID: TEI20_5IOPS Isolated Operation for Public Safety in 5G System (5IOPS). | Huawei, HiSilicon |
S2-2505363 | TEI-20 on Enhanced EAS/ECS Option Selection . | Nokia |
S2-2505364 | Exposure of N6 delay measurements | Nokia |
S2-2505365 | Utilizing existing information to create/update DNS message handling rule | Nokia |
S2-2505366 | Updating Service Experience and DN performance analytics with N6 delay measurements | Nokia |
S2-2505386 | TEI20 Support of User Control of Inter-PLMN Handover | Deutsche Telekom |
S2-2505388 | New WID: TEI20_5MBS_Roam; Adding support for Roaming UEs to receive 5MBS. | Nokia |
S2-2505401 | Discussion on TEI20 WID of QoS Enhancement for MWAB. | CATT |
S2-2505402 | New WID on QoS Enhancement for MWAB. | CATT |
S2-2505403 | QoS Enhancement for MWAB | CATT |
S2-2505435 | New WID: IMS Multimedia Telephony enhancements | Apple |
TDoc | Title | Source |
---|---|---|
S2-2504648 | Discussion on Rel-20 Ambient IoT study. | Ofinno |
S2-2504676 | New SID on Enhancements for ePDG based access to 5GC. | Qualcomm Incorporated as moderator |
S2-2504699 | New WT for AIML_CN_Ph2 work. | Lenovo |
S2-2504799 | New WID on Indirect Network Sharing phase2. | China Unicom |
S2-2504802 | New WID on Indirect Network Sharing phase2. | China Unicom (Moderator) |
S2-2504828 | Rel-20 Sensing Work Organisation in SA WG2 . | Apple, Deutsche Telekom |
S2-2504986 | NWM summary report on Mission Critical Services, Multimedia Priority Services | Peraton Labs (moderator) |
S2-2504987 | New SID on MPS Enhancements for IoT. | Peraton Labs (moderator) |
S2-2504988 | New SID on MPS Enhancements for IoT. | Peraton Labs |
S2-2505142 | ProSe_Ph4 Way Forward | KPN N.V. |
S2-2505196 | Study on Extended Reality and Media Service (XRM) Phase 3. | Nokia |
S2-2505316 | Summary outcome of offline discussion on SI Industrial networks_enhancements | Ericsson (Moderator) |
S2-2505317 | New SID on Study on Industrial Networks enhancements. | Ericsson (Moderator) |
S2-2505330 | New Study on User Identities and Authentication Architecture Phase 2. | InterDigital Inc. |
S2-2505331 | New Study on Identifying non-3GPP Devices Connecting behind a UE or 5G-RG Phase 2. | InterDigital Inc. |
S2-2505332 | Summary the Email Discussion on a Way Forward for UIA_ARC in Rel-20. | InterDigital Inc. (Moderator) |
S2-2505348 | Discussion on Rel-20 FS_XRM Ph3. | Huawei, HiSilicon |
S2-2505371 | Discussion on Rel-20 Indirect Network Sharing phase2. | CableLabs |
S2-2505373 | NEW SID on Architecture support of Ambient power-enabled Internet of Things-Phase 2. | Huawei (Moderator) |
S2-2505374 | Rel-20 SA WG2 Ambient IoT Proposal | Huawei, HiSilicon |
S2-2505375 | Moderator report on: Moderated discussion for R20 SA WG2 Ambient IoT Phase 2 | Huawei (moderator) |
S2-2505377 | New WID on Indirect Network Sharing phase2. | CableLabs |
S2-2505383 | Support of simultaneous support for 3GPP access and non-3GPP access without UE impact in Rel-20. | NEC |
S2-2505384 | Summary of NWM discussion on 'Short Message Service to Emergency Response Centre' study objectives and WTs | Apple (Moderator) |
S2-2505385 | New SID on Short Message Service to Emergency Response Centre. | Apple (Moderator) |
S2-2505387 | Update to new WID on Indirect Network Sharing phase2. | NEC |
S2-2505409 | Revised SID on Study on Stage 2 for Integrated Sensing and Communication | Xiaomi, Apple (Rapporteurs) |
TDoc | Title | Source |
---|---|---|
S2-2504684 | NWM discussion on 6G work area | ZTE(moderator) |
S2-2504685 | Summary of NWM discussion on 6G work areas. | ZTE(moderator) |
S2-2504686 | New Study on Architecture for 6G System. | ZTE (Moderator) |
S2-2504769 | 6G Architecture support cloud-Native features . | Boost Mobile Network, EchoStar, AT&T, SK Telecom, KPN N.V., TNO, Deutsche Telekom AG, Telecom Italia S.p.A., Rakuten Mobile |
S2-2504855 | 6G-NTN use cases for 6G Study Item WA#8 . | EchoStar, Boost Mobile Network, TNO, Novamint, Thales, Airbus |
S2-2505224 | Vivo views on 6G energy saving and energy efficiency | vivo |
S2-2505292 | New Study on 6G System architecture. | Huawei, HiSilicon |
S2-2505302 | Structure of the 6G study item. | Qualcomm Incorporated, Ericsson |
S2-2505307 | Suggestions on 6G Architecture Study Motivation and Scope . | China Mobile, CATT, |
S2-2505372 | MediaTek View - 6G SI | MediaTek Inc. |
S2-2505378 | Apple comments on 6G SID proposal (S2-2504686). | Apple |
S2-2505410 | Discussion on 5G-A and 6G Sensing | xiaomi, Apple |
S2-2505421 | 6G Study time plan | Nokia |
TDoc | Title | Source |
---|---|---|
S2-2504728 | SA WG2#169 Work Planning slides | SA WG2 Chair |
S2-2504729 | SA WG2#169 Work planning spreadsheet | SA WG2 Chair |
S2-2504731 | Rel-20 5GA and 6G TU budget split | SA WG2 Chair |
S2-2504732 | Plan for 6G study | SA WG2 Chair |
S2-2505132 | 2027 meeting calendar | SA WG2 Chair |
TDoc | Title | Source |
---|---|---|
S2-2505133 | New template for SI/WI status reports | SA WG2 Chair |
TDoc | Title | Source |
---|---|---|
S2-2504582 | LS from SA WG3: LS on UIA Rel-20 in response to SA guidance from SA#107 | SA WG3 |
S2-2505021 | Cover sheet for presentation of TS 23.369 to TSG SA for Approval | OPPO |
S2-2505210 | New SID: Study on system architecture for next generation real time communication services phase 3. | China Mobile, Huawei |
TDoc | Title | Source |
---|---|---|
S2-2504486 | Incoming LS mis-numbered and withdrawn | MCC |
S2-2504487 | Incoming LS mis-numbered and withdrawn | MCC |
S2-2504488 | Incoming LS mis-numbered and withdrawn | MCC |
S2-2504489 | Incoming LS mis-numbered and withdrawn | MCC |
S2-2504490 | Incoming LS mis-numbered and withdrawn | MCC |
S2-2504491 | Incoming LS mis-numbered and withdrawn | MCC |
S2-2504492 | Incoming LS mis-numbered and withdrawn | MCC |
S2-2504493 | Incoming LS mis-numbered and withdrawn | MCC |
S2-2504494 | Incoming LS mis-numbered and withdrawn | MCC |
S2-2504495 | Incoming LS mis-numbered and withdrawn | MCC |
S2-2504496 | Incoming LS mis-numbered and withdrawn | MCC |
S2-2504497 | Incoming LS mis-numbered and withdrawn | MCC |
S2-2504498 | Incoming LS mis-numbered and withdrawn | MCC |
S2-2504499 | Incoming LS mis-numbered and withdrawn | MCC |
S2-2504500 | Incoming LS mis-numbered and withdrawn | MCC |
S2-2504590 | WT1:Architecture assumptions for normal IMS voice call over GEO via NB-IoT NTN connecting to EPC. | Qualcomm Incorporated |
S2-2504595 | TR 23.700-67: KI#3: new solution for UP path adjustment | Qualcomm Technologies |
S2-2504616 | Correction to NTZ | Ofinno |
S2-2504617 | Conditions for Network Slice Replacement notification | Oracle, Verizon |
S2-2504622 | 5GS common time reference traceable to UTC | Nokia |
S2-2504626 | AIML_CN KI#1 Add DCCF as Client for Nlmf_DataExposure service | Nokia |
S2-2504650 | New Solution: IMS voice OptimizeSDP negotiation with 100 trying for IMS NB-IoT GEO Access | CSCN |
S2-2504657 | New solution of combined CP/UP in a PDN connection for KI#1 | China Telecom Corporation Ltd. |
S2-2504658 | New solution of combined CP/UP in a PDN connection for KI#1 | China Telecom Corporation Ltd. |
S2-2504689 | CHF discovery and selection based on CHF Group ID | Nokia |
S2-2504690 | CHF Group ID in Access and Mobility, Session Management and SMS Management Subscription Data | Nokia |
S2-2504705 | Energy Consumption information assisted Policy Update. | China Mobile |
S2-2504715 | [DRAFT] Reply LS on the accuracy of PDU Set size and data burst size indication | China Mobile |
S2-2504716 | KI#4: Resolve the incorrect multiplex support in NOTE | China Mobile |
S2-2504805 | Misleading message flow in network triggered SR procedure | Nokia |
S2-2505069 | FS_5GSAT_Ph4_23700-19_KI#1_NB-IoT UP-based IMS voice using GEO satellite | vivo, MediaTek Inc. |
S2-2505070 | FS_5GSAT_Ph4_23700-19_KI#1_NB-IoT CP-based IMS voice using GEO satellite | vivo |
S2-2505165 | Corrections for energy saving related AF input on BDT policy negotiation | Huawei, HiSilicon |
S2-2505216 | KI#2, New Sol: Authorization Information Update by AF | TOYOTA MOTOR CORPORATION |
S2-2505218 | KI#2, New Sol: Authorization of Sensing Service Requests | Toyota Motor Corporation, Beijing University of Posts and Telecommunications |
S2-2505220 | KI#4, New Sol: Sensing data collection and transport over Control Plane | Toyota Motor Corporation, Beijing University of Posts and Telecommunications |
S2-2505406 | Supported TAIs information | Samsung |
S2-2505425 | Clarification and correction on modification of UP connection between UE and LMF | Nokia, Nokia Shanghai Bell |
S2-2505433 | Clarification and correction on modification of UP connection between UE and LMF | Huawei, HiSilicon |