3GPP TDocs (written contributions) at meeting
Meeting: S2-127 - 2018-04-16 to 2018-04-20, Sanya
meeting id: S2-127 (click id for more info on this meeting)Click on the Tdoc to open its file.
| TDoc | Title | Source | Remarks |
|---|---|---|---|
| S2‑183049 | Draft Agenda for SA WG2#127 | SA WG2 Chairman | imported from 3GU |
| S2‑183050 | Draft Report of SA WG2 meeting #126 | SA WG2 Secretary | imported from 3GU |
| S2‑183051 | LS from SA WG6: LS on Integration of northbound APIs with CAPIF | SA WG6 | imported from 3GU |
| S2‑183052 | LS from GSMA Packet IoTTF: LS reply to SA WG2 on Differentiation of LTE-M (eMTC) traffic from other LTE data traffic | GSMA Packet IoTTF | imported from 3GU |
| S2‑183053 | LS from CT WG1: LS on service gap control with resume for non-supporting UE | CT WG1 | imported from 3GU |
| S2‑183054 | LS from CT WG3: LS on Resource Identifiers for T8 | CT WG3 | imported from 3GU |
| S2‑183055 | LS from CT WG3: LS on T8 Destination Address | CT WG3 | imported from 3GU |
| S2‑183056 | LS from RAN WG2: Reply LS on maximum idle mode DRX value | RAN WG2 | imported from 3GU |
| S2‑183057 | LS from RAN WG3: LS on Extending TAC for NR and NG-RAN | RAN WG3 | imported from 3GU |
| S2‑183058 | LS from SA WG6: Reply LS to SA WG2 on default values for 5GS QoS averaging window | SA WG6 | imported from 3GU |
| S2‑183059 | LS from SA WG4: LS on QoS for Live Uplink Streaming (FLUS) | SA WG4 | imported from 3GU |
| S2‑183060 | LS from CT WG3: LS on Questions on Events related to Service Data Flows in the Nsmf_EventExposure service | CT WG3 | imported from 3GU |
| S2‑183061 | LS from GSMA ESIM WI4: BIP for non-IP: MT communication | GSMA ESIM WI4 | imported from 3GU |
| S2‑183062 | LS from : NGMN Paper on 5G End-to-End Architecture Framework. | NGMN | imported from 3GU |
| S2‑183063 | LS from CT WG1: Reply LS on indication of preferred CIoT network behavior | CT WG1 | imported from 3GU |
| S2‑183064 | LS from CT WG1: LS on handling of EPS bearer context and PDU session context for interworking without N26 | CT WG1 | imported from 3GU |
| S2‑183065 | LS from CT WG1: LS on the IMS voice over PS session supported indication | CT WG1 | imported from 3GU |
| S2‑183066 | LS from CT WG1: LS on one step MO SMS procedure | CT WG1 | imported from 3GU |
| S2‑183067 | LS from CT WG1: LS on N3GPP TAI | CT WG1 | imported from 3GU |
| S2‑183068 | LS from CT WG1: LS on DRX parameters negotiation | CT WG1 | imported from 3GU |
| S2‑183069 | LS from CT WG1: LS on deactivation of MICO mode due to emergency service | CT WG1 | imported from 3GU |
| S2‑183070 | LS from CT WG1: LS on 5G-GUTI type | CT WG1 | imported from 3GU |
| S2‑183071 | LS from CT WG1: Reply LS on EPS fallback for voice | CT WG1 | imported from 3GU |
| S2‑183072 | LS from CT WG1: LS on TAI and forbidden TAI list for 5GS | CT WG1 | imported from 3GU |
| S2‑183073 | LS from CT WG1: LS on paging with IMSI/SUCI in 5GS | CT WG1 | imported from 3GU |
| S2‑183074 | LS from CT WG4: LS on the clarification of the UDR service name | CT WG4 | imported from 3GU |
| S2‑183075 | LS from RAN WG2: Response LS on optionality of the UE procedures related to RRC Inactive | RAN WG2 | imported from 3GU |
| S2‑183076 | LS from RAN WG2: LS on UE differentiation in NB-IoT | RAN WG2 | imported from 3GU |
| S2‑183077 | LS from RAN WG2: LS on clarification of NSSAI information exchange during Inactive to connected mode transition | RAN WG2 | imported from 3GU |
| S2‑183078 | LS from RAN WG3 Reply LS on Paging failures for CE Capable UEs | RAN WG3 | imported from 3GU |
| S2‑183079 | LS from RAN WG3: LS on data forwarding for intra-system handover | RAN WG3 | imported from 3GU |
| S2‑183080 | LS from RAN WG3: Reply LS on coexistence between RRC inactive and dual connectivity | RAN WG3 | imported from 3GU |
| S2‑183081 | LS from RAN WG3: LS on Applying Xn and NG HO procedure for Inter-RA Mobility | RAN WG3 | imported from 3GU |
| S2‑183082 | LS from RAN WG3 3: Reply LS on EDT procedures and AS NAS interaction | RAN WG3 3 | imported from 3GU |
| S2‑183083 | LS from RAN WG3: LS on Handling of end marker packets | RAN WG3 | imported from 3GU |
| S2‑183084 | LS from RAN WG4: Reply LS on NR interworking with GSM and UMTS | RAN WG4 | imported from 3GU |
| S2‑183085 | LS from TSG RAN: LS on secured Signalling-only connection | TSG RAN | imported from 3GU |
| S2‑183086 | LS from TSG RAN: LS on optimisation of UE capability signalling | TSG RAN | imported from 3GU |
| S2‑183087 | LS from SA WG3: LS on authentication related services provided by AUSF and UDM | SA WG3 | imported from 3GU |
| S2‑183088 | LS from SA WG3: LS on Support User Plane Encryption in UP security policy | SA WG3 | imported from 3GU |
| S2‑183089 | LS from SA WG3: LS on UP Security Policy | SA WG3 | imported from 3GU |
| S2‑183090 | LS from SA WG3: LS on Initial NAS message protection | SA WG3 | imported from 3GU |
| S2‑183091 | LS from SA WG3: LS on AS Security Context Setup | SA WG3 | imported from 3GU |
| S2‑183092 | LS from SA WG3: LS on SoR mechanism | SA WG3 | imported from 3GU |
| S2‑183093 | LS from RAN WG2: Reply LS on EDT procedures and AS NAS interaction | RAN WG2 | imported from 3GU |
| S2‑183094 | LS from RAN WG2: Reply LS on Data support for voice centric UE supporting CE mode B | RAN WG2 | imported from 3GU |
| S2‑183095 | LS from RAN WG2: Reply LS to Reply LS on UE differentiation for Rel-15 NB-IoT | RAN WG2 | imported from 3GU |
| S2‑183096 | LS from RAN WG2: Reply LS on Reliability for eV2X | RAN WG2 | imported from 3GU |
| S2‑183097 | LS from RAN WG2: Reply LS on Certification/License and Identification of Aerial Vehicles | RAN WG2 | imported from 3GU |
| S2‑183098 | LS from RAN WG2: LS on PC5 transmission mechanism selection | RAN WG2 | imported from 3GU |
| S2‑183099 | LS from RAN WG2: LS to SA WG2 and CT WG1 on enabling and disabling NG RAN Capabilities | RAN WG2 | imported from 3GU |
| S2‑183100 | LS from RAN WG2: LS regarding RAN support for NW slicing | RAN WG2 | imported from 3GU |
| S2‑183101 | LS from TSG SA: Reply LS on V1 and V2 reference points | TSG SA | imported from 3GU |
| S2‑183102 | LS from TSG SA: LS on Guidance on UE WiFi MAC Address inclusion in LTE Positioning Protocol | TSG SA | imported from 3GU |
| S2‑183103 | 5_16_6_Mission Critical Services - Reference Update | FirstNet, AT&T, Motorola Solutions, Airwave | imported from 3GU |
| S2‑183104 | 5_16_6_Mission Critical Services - Editorial Changes and Clarifications | FirstNet, AT&T, Motorola Solutions, Airwave | imported from 3GU |
| S2‑183105 | Xn handover and slice unavailability | Qualcomm Incorporated | imported from 3GU |
| S2‑183106 | [DRAFT] LS response on Applying Xn and NG HO procedure for Inter-RA Mobility | Qualcomm Finland RFFE Oy | imported from 3GU |
| S2‑183107 | Fixing Incorrect References to the Service Request Procedures | Convida Wireless LLC | imported from 3GU |
| S2‑183108 | Include support for eSRVCC in S8HR in 23.228 | Ericsson, Vodafone, Deutsche Telekom, NTT DoCoMo | imported from 3GU |
| S2‑183109 | Include support for eSRVCC in S8HR in 23.237 | Ericsson, Vodafone, Deutsche Telekom, NTT DoCoMo | imported from 3GU |
| S2‑183110 | Include support for eSRVCC in S8HR in 23.216 | Ericsson, Vodafone, Deutsche Telekom, NTT DoCoMo | imported from 3GU |
| S2‑183111 | Solution X for key issue 5 : Enabling SBA-based Cx | Ericsson | imported from 3GU |
| S2‑183112 | Solution X for key issue 6 : Enabling SBA-based Sh | Ericsson | imported from 3GU |
| S2‑183113 | Solution to Key issue #EPC-1 | Ericsson | imported from 3GU |
| S2‑183114 | Solution to Key issue #EPC-3 | Ericsson | imported from 3GU |
| S2‑183115 | Solution to Key issue IMS-1, IMS-2, and IMS-3 | Ericsson | imported from 3GU |
| S2‑183116 | Making the T8 Destination Address Mandatory for APIs that Create a Subscription | Convida Wireless LLC, Huawei | imported from 3GU |
| S2‑183117 | [DRAFT] Reply LS on T8 Destination Address | Convida Wireless LLC | imported from 3GU |
| S2‑183118 | [DRAFT] Reply LS on Resource Identifiers for T8 | Convida Wireless LLC | imported from 3GU |
| S2‑183119 | Fixing TTRI Usage in the MT NIDD Procedure | Convida Wireless LLC | imported from 3GU |
| S2‑183120 | Discussion on TLTRI and TTRI Usage | Convida Wireless LLC | imported from 3GU |
| S2‑183121 | TLTRI and TTRI Usage | Convida Wireless LLC, Huawei | imported from 3GU |
| S2‑183122 | [DRAFT] Reply LS on DRX Parameter Negotiation | Convida Wireless LLC | imported from 3GU |
| S2‑183123 | [DRAFT] Reply LS on paging with IMSI/SUCI in 5GS | Ericsson | imported from 3GU |
| S2‑183124 | SUPI based paging | Ericsson | imported from 3GU |
| S2‑183125 | Fetching UE Radio Capability and UE Radio Capability for Paging Information | Ericsson | imported from 3GU |
| S2‑183126 | Alignment with CT WG1/RAN on handling of S1AP CONNECTION ESTABLISHMENT INDICATION | Ericsson | imported from 3GU |
| S2‑183127 | Removing some ENs and update in Solution #4 | Ericsson | imported from 3GU |
| S2‑183128 | Solution to Key issue #IMS-4: Support of emergency services by UEs attached for RLOS | Ericsson | imported from 3GU |
| S2‑183129 | Solution to Key Issue #1 | Ericsson | imported from 3GU |
| S2‑183130 | S-NSSAI in EBI Allocation | Ericsson | imported from 3GU |
| S2‑183131 | Key Issue #5 Solution: MO Data Buffering | Convida Wireless LLC, NEC | imported from 3GU |
| S2‑183132 | Key Issue #9 Solution: SCEF+NEF Node | Convida Wireless LLC, AT&T | imported from 3GU |
| S2‑183133 | LS from BBF: Response to SA WG2 liaison on general status of work | BBF | imported from 3GU |
| S2‑183134 | Correction to Nnwdaf_EventsSubscription_Notify | KDDI, ETRI, Oracle | imported from 3GU |
| S2‑183135 | [DRAFT] LS response on LS on Support User Plane Encryption in UP security policy | Qualcomm Finland RFFE Oy | imported from 3GU |
| S2‑183136 | [DRAFT] LS response on LS on UP Security Policy | Qualcomm Finland RFFE Oy | imported from 3GU |
| S2‑183137 | Correction of description related to PFD management | KDDI, China Unicom | imported from 3GU |
| S2‑183138 | UE capability related to integrity protection of DRBs for signalling of the maximum supported data rate per UE for integrity protection | Qualcomm Finland RFFE Oy | imported from 3GU |
| S2‑183139 | UE capability related to integrity protection of DRBs for signalling of the maximum supported data rate per UE for integrity protection | Qualcomm Finland RFFE Oy | imported from 3GU |
| S2‑183140 | [DRAFT] LS OUT on UE capability related to integrity protection of DRBs | Qualcomm Finland RFFE Oy | imported from 3GU |
| S2‑183141 | Correction to URSP and UE preferences for NSSP and SSCMSP | Qualcomm Finland RFFE Oy | imported from 3GU |
| S2‑183142 | Mobile Terminated SMS over NAS: 5GS Access Selection | Qualcomm Finland RFFE Oy | imported from 3GU |
| S2‑183143 | Access Selection for Mobile Terminated SMS over NAS | Qualcomm Finland RFFE Oy | imported from 3GU |
| S2‑183144 | Discussion on Initial NAS message protection | Qualcomm Finland RFFE Oy | imported from 3GU |
| S2‑183145 | [DRAFT] LS response on Initial NAS message protection | Qualcomm Finland RFFE Oy | imported from 3GU |
| S2‑183146 | [DRAFT] LS response on N3GPP TAI | Qualcomm Finland RFFE Oy | imported from 3GU |
| S2‑183147 | Paging for delay tolerant applications in the UE | NEC | imported from 3GU |
| S2‑183148 | Clarifications on Non-3GPP TAI | Qualcomm Finland RFFE Oy | imported from 3GU |
| S2‑183149 | Discovery and Topology Hiding | Ericsson | imported from 3GU |
| S2‑183150 | Alignment of RAT Fallback to EPS Fallback call flow | Ericsson | imported from 3GU |
| S2‑183151 | Reliability for eV2X for LTE clarification | Ericsson | imported from 3GU |
| S2‑183152 | Subscription for Aerial UE in 3GPP system | Ericsson, NTT DoCoMo, Qualcomm Incorporated, Intel | imported from 3GU |
| S2‑183153 | Solutions for KI#5,KI#6 and KI#11 Service Authorisation | Ericsson | imported from 3GU |
| S2‑183154 | Solution for KI#12 V2X interworking | Ericsson | imported from 3GU |
| S2‑183155 | Clarification of using more than eight EPS bearers with EPS | Ericsson | imported from 3GU |
| S2‑183156 | Clarification on single outstanding Service Request | Intel, MediaTek Inc. | imported from 3GU |
| S2‑183157 | Temporary restriction of Reflective QoS | Intel, MediaTek Inc. | imported from 3GU |
| S2‑183158 | Temporary restriction of Reflective QoS | Intel, MediaTek Inc. | imported from 3GU |
| S2‑183159 | On UE capability handling based on UE capability ID | Intel | imported from 3GU |
| S2‑183160 | 5GS Temporary Identifiers and mapping - solution proposal | Ericsson | imported from 3GU |
| S2‑183161 | Changed length and mapping of 5GS Temporary Identifiers | Ericsson | imported from 3GU |
| S2‑183162 | Slice configuration change | Ericsson | imported from 3GU |
| S2‑183163 | Slice configuration change | Ericsson | imported from 3GU |
| S2‑183164 | SMSF - removal of MT SMS Domain Selection | Ericsson | imported from 3GU |
| S2‑183165 | Adding support for IMS to Npcf service | Ericsson | imported from 3GU |
| S2‑183166 | Defining NWDAF in 23.501 | Ericsson, AT&T, Huawei | imported from 3GU |
| S2‑183167 | UE Policies in a UE Policy Container | Ericsson | imported from 3GU |
| S2‑183168 | Default QoS rule | Ericsson | imported from 3GU |
| S2‑183169 | Corrections to PFD management | Ericsson | imported from 3GU |
| S2‑183170 | AMF UE area of interest reporting in RRC inactive state | Ericsson | imported from 3GU |
| S2‑183171 | Deregistration procedure correction | Ericsson | imported from 3GU |
| S2‑183172 | Updates to solution 11 | Ericsson | imported from 3GU |
| S2‑183173 | Updates to solution 2 for SMF selection | Ericsson | imported from 3GU |
| S2‑183174 | Updates to solution 1 | Ericsson | imported from 3GU |
| S2‑183175 | Corrections for handling UP security policy when interworking with EPC | Ericsson | imported from 3GU |
| S2‑183176 | Discussion on using PSI | OPPO | imported from 3GU |
| S2‑183177 | UE Presence in Area Of Interest | Samsung | imported from 3GU |
| S2‑183178 | Non-seamless offload indicator in URSP | Samsung | imported from 3GU |
| S2‑183179 | Clarification on NG-RAN location reporting procedure | Samsung | imported from 3GU |
| S2‑183180 | Key Issues considerations to support isolated and coexisted slices | ZTE Corporation, Telecom Italia, Oracle, China Telecom | imported from 3GU |
| S2‑183181 | Update on UE mobility event notification | Samsung | imported from 3GU |
| S2‑183182 | Solution for supporting the complete slice isolation in network slicing | ZTE Corporation, China Telecom | imported from 3GU |
| S2‑183183 | UE Policy delivery procedure | Samsung | imported from 3GU |
| S2‑183184 | Clarification on downlink data handling for LADN | Samsung | imported from 3GU |
| S2‑183185 | Identification and update of UE derived QoS rule | Samsung | imported from 3GU |
| S2‑183186 | Overriding user preference indication in URSP | Samsung | imported from 3GU |
| S2‑183187 | UE policy delivery corrections | Samsung | imported from 3GU |
| S2‑183188 | Clarification on multiple QoS rules with same QFI including QoS parameters | Samsung | imported from 3GU |
| S2‑183189 | Solution to key issue#6 | LG Electronics | imported from 3GU |
| S2‑183190 | Solution to key issue#8 | LG Electronics, NTT DOCOMO | imported from 3GU |
| S2‑183191 | Solution to key issue#10 for non-IP based V2X message transmission and reception over Uu | LG Electronics, NTT DOCOMO | imported from 3GU |
| S2‑183192 | TR 23.724: Enhanced MICO for power saving solution | Qualcomm Incorporated, Sony, Samsung, Convida Wireless LLC, BlackBerry UK Ltd | imported from 3GU |
| S2‑183193 | TR 23.724: NIDD aspects for small data transfer via NAS-SM | Qualcomm Incorporated | imported from 3GU |
| S2‑183194 | TR 23.724: Addressing open issues for Solution 1 | Qualcomm Incorporated | imported from 3GU |
| S2‑183195 | TS 23.502: Perform authentication before Context Acknowledgement during 5GS to EPS Idle mode mobility using N26 interface | Qualcomm Incorporated | imported from 3GU |
| S2‑183196 | Clarification of traffic steering in UPF + PGW-U | KDDI | imported from 3GU |
| S2‑183197 | New Study on Architecture aspects of using satellite access in 5G | THALES | imported from 3GU |
| S2‑183198 | UE capability handling based on UE capability ID | Intel | imported from 3GU |
| S2‑183199 | UE capability handling based on UE capability ID | Intel | imported from 3GU |
| S2‑183200 | New Key Issue: Optimal modularization of the system | Deutsche Telekom, AT&T, Telecom Italia, Sprint, China Mobile, KDDI, Interdigital Inc., SK Telecom, Telstra, Verizon | imported from 3GU |
| S2‑183201 | New Key Issue: SBA backward and forward compatibility | Deutsche Telekom, | imported from 3GU |
| S2‑183202 | NSSF uses NWDAF's Service to select network slice(s) | NEC Europe Ltd | imported from 3GU |
| S2‑183203 | Clarification on using PSI | OPPO | imported from 3GU |
| S2‑183204 | Clarification on UE configuration update procedure | OPPO, ZTE | imported from 3GU |
| S2‑183205 | Clarification on UE policy configuration -23.503 | OPPO | imported from 3GU |
| S2‑183206 | New Key Issue: Improvements to service framework related aspects | Deutsche Telekom | imported from 3GU |
| S2‑183207 | New Key Issue: Architectural support for highly reliable deployments | Deutsche Telekom | imported from 3GU |
| S2‑183208 | Clarification on UE policy configuration -23.502 | OPPO | imported from 3GU |
| S2‑183209 | Solution for UE assisted enrypted traffic detection | OPPO | imported from 3GU |
| S2‑183210 | Solution for NW triggered enrypted traffic detection | OPPO | imported from 3GU |
| S2‑183211 | 5G SRVCC architecture assumption | OPPO | imported from 3GU |
| S2‑183212 | Updates to System Enablers for Priority Mechanisms | Vencore Labs, OEC, AT&T, T-Mobile USA, Sprint | imported from 3GU |
| S2‑183213 | Use of Establishment Cause in PDU Session Establishment Procedurere | Vencore Labs, OEC, AT&T, T-Mobile USA, Sprint | imported from 3GU |
| S2‑183214 | KI 1: Adding DL data handling in solution 5 SDFP | Ericsson | imported from 3GU |
| S2‑183215 | KI 1 & 2: Extract NIMF as separate solution | Ericsson | imported from 3GU |
| S2‑183216 | KI 2: Adding RRC Inactive handling in solution 7 for frequent SD | Ericsson | imported from 3GU |
| S2‑183217 | KI 3: Solution for High latency communication | Ericsson | imported from 3GU |
| S2‑183218 | Alignment with CT WG1 for handling of Connection Resume Requests at Service Gap | Ericsson | imported from 3GU |
| S2‑183219 | [DRAFT] Reply LS on service gap control with resume for non-supporting UE | Ericsson | imported from 3GU |
| S2‑183220 | [DRAFT] Response LS on Resource Identifiers for T8 | Ericsson | imported from 3GU |
| S2‑183221 | Enhancement of network event reporting | Ericsson | imported from 3GU |
| S2‑183222 | Fixing Group NIDD | Ericsson | imported from 3GU |
| S2‑183223 | Description of 5GC LCS in 23.271 Rel-15. | Ericsson | imported from 3GU |
| S2‑183224 | LCS in 5GC | Ericsson | imported from 3GU |
| S2‑183225 | Solution for Location Service exposure | Ericsson | imported from 3GU |
| S2‑183226 | Solution for Location Service exposure to NG-RAN | Ericsson | imported from 3GU |
| S2‑183227 | Clarifications on Nudr interactions between PCF and UDR | Ericsson | imported from 3GU |
| S2‑183228 | PCRF trigger LLC Mobility clarifications on solution 3 | Ericsson | imported from 3GU |
| S2‑183229 | UE Radio Capability for paging | Ericsson | imported from 3GU |
| S2‑183230 | Editorial corrections to 23.502 | Ericsson | imported from 3GU |
| S2‑183231 | 3GPP SBA and ETSI NFV concepts | Ericsson | imported from 3GU |
| S2‑183232 | Requirements for 3GPP end user devices via 5G-RG/FN-RG | Ericsson | imported from 3GU |
| S2‑183233 | Support 3GPP UEs via 5G-RG/FN-RG for wireline access network using N3GPP solutions | Ericsson | imported from 3GU |
| S2‑183234 | PCR 23.724: Power Saving Mode | Ericsson | imported from 3GU |
| S2‑183235 | PCR 23.724: eDRX | Ericsson | imported from 3GU |
| S2‑183236 | Support of multiple PDU sessions to the same DNN but different S-NSSAIs for EPC-5GC interworking | Qualcomm Incorporated | imported from 3GU |
| S2‑183237 | TS 23.501: Clarifying SMF, UPF and PCF selection for 5GC-EPC interworking | Qualcomm Incorporated | imported from 3GU |
| S2‑183238 | TS 23.502: Taking UE subscription into account when transfering PDU sessions during 5GC-EPC mobility | Qualcomm Incorporated | imported from 3GU |
| S2‑183239 | AMF Selection aspects | Nokia, Nokia Shanghai Bell, NTT Docomo, Verizon, AT&T, Telicom Italia, SK Telecom | imported from 3GU |
| S2‑183240 | 23.501 EN resolution | Nokia, Nokia Shanghai Bell (Rapporteur) | imported from 3GU |
| S2‑183241 | AMF functionality clarification - to add SUCI | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183242 | AMF Context Retrieval upon relocation | Nokia, Nokia Shanghai Bell, NTT DoCoMo | imported from 3GU |
| S2‑183243 | Signalling only connection - AS security context | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183244 | [DRAFT] Reply LS on secured Signalling-only connection | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183245 | Service Request - AS Security Setup | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183246 | EPS to 5GS Mobility - Handling PDN connections that are not subject to service continuity | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183247 | EPS Interworking Principles - SR mode with N26 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183248 | EPS Interworking - Clarify SMF Registration | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183249 | P-GW-C+SMF Registration in the UDM for the purpose of EPS interworking | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183250 | EPS Bearer ID allocation for Home routed case | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183251 | Context retrieval for the purpose of EPS interworking | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183252 | Support for dual registration via the same RAT | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Verizon | imported from 3GU |
| S2‑183253 | Voice fallback during roaming scenarios | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183254 | NF Discovery via the NRF | Nokia, Nokia Shanghai Bell, Verizon, AT&T | imported from 3GU |
| S2‑183255 | NF Registration via the NRF | Nokia, Nokia Shanghai Bell, Verizon, AT&T | imported from 3GU |
| S2‑183256 | Nudm_UEAuthentication Service clarification | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183257 | UDM services - addition to Nudm_UEAuthentication | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183258 | UDM functionality support for SUCI | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183259 | MFBR Enforcement for GBR QoS flows | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183260 | [DRAFT] LS on URLLC Services | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183261 | NF Registration via the NRF | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183262 | Removing the limit on the number of slices | Huawei, HiSilicon | imported from 3GU |
| S2‑183263 | Architecture principles for eSBA | Huawei, HiSilicon | imported from 3GU |
| S2‑183264 | Key Issue: Support of system flexibility and service provisioning | Huawei, HiSilicon | imported from 3GU |
| S2‑183265 | Positioning procedures considering different LMF deployment scenarios | Huawei, HiSilicon | imported from 3GU |
| S2‑183266 | Correction to figure caption error in handover procedures | Huawei, Hisilicon | imported from 3GU |
| S2‑183267 | Discussion on TAI for N3GPP | Huawei, Hisilicon | imported from 3GU |
| S2‑183268 | Clarification on TAI for N3GPP | Huawei, Hisilicon | imported from 3GU |
| S2‑183269 | [DRAFT] LS Response on TAI for N3GPP | Huawei, Hisilicon | imported from 3GU |
| S2‑183270 | Clarification for Network Requested PDU Session Release via Untrusted non-3GPP access | Huawei, Hisilicon | imported from 3GU |
| S2‑183271 | Update of the Key issue 5: Multi-access PDU sessions (Un-trusted access) | Huawei, Hisilicon | imported from 3GU |
| S2‑183272 | Alignment to BBF result: KI5 handover solution | Huawei, Hisilicon | imported from 3GU |
| S2‑183273 | IPTV solution for WWC | Huawei, Hisilicon | imported from 3GU |
| S2‑183274 | Solution to mobile restriction and LADN support for WWC | Huawei, Hisilicon | imported from 3GU |
| S2‑183275 | KI#5: solution for RM state | Huawei, Hisilicon | imported from 3GU |
| S2‑183276 | KI#5: solution for CM state | Huawei, Hisilicon | imported from 3GU |
| S2‑183277 | Correction to NEF service | China Telecommunications | imported from 3GU |
| S2‑183278 | Abbreviations supplement | China Telecom Corporation Ltd. | imported from 3GU |
| S2‑183279 | Clarification on NSI selection and Configured NSSAI | China Telecom Corporation Ltd. | imported from 3GU |
| S2‑183280 | Consideration on Network Slice Priority | China Telecom Corporation Ltd. | imported from 3GU |
| S2‑183281 | FS_5G-SRVCC - Skeleton of TR 23.756 | China Unicom | imported from 3GU |
| S2‑183282 | FS_5G-SRVCC - Scope of TR 23.756 | China Unicom | imported from 3GU |
| S2‑183283 | Architectural assumptions and requirements of 5G SRVCC | China Unicom | imported from 3GU |
| S2‑183284 | Key issue of 5G SRVCC | China Unicom | imported from 3GU |
| S2‑183285 | New use case: NWDA-assisted load balancing/re-balancing of network function | KDDI | imported from 3GU |
| S2‑183286 | 3GPP PS Data Off Clarification | Intel, Telecom Italia, Deutsche Telekom, Nokia, Nokia Shanghai Bell, Huawei, Hisilicon, Qualcomm, ZTE, MediaTek Inc., CMCC, China Unicom, OPPO | imported from 3GU |
| S2‑183287 | 3GPP PS Data Off Clarification | Intel, Telecom Italia, Deutsche Telekom, Nokia, Nokia Shanghai Bell, Huawei, Hisilicon, Qualcomm, ZTE, MediaTek Inc., CMCC, China Unicom, OPPO | imported from 3GU |
| S2‑183288 | 3GPP PS Data Off Clarification | Intel, Telecom Italia, Deutsche Telekom, Nokia, Nokia Shanghai Bell, Huawei, Hisilicon, Qualcomm, ZTE, MediaTek Inc., CMCC, China Unicom, OPPO | imported from 3GU |
| S2‑183289 | 3GPP PS Data Off Clarification | Intel, Telecom Italia, Deutsche Telekom, Nokia, Nokia Shanghai Bell, Huawei, Hisilicon, Qualcomm, ZTE, MediaTek Inc., CMCC, China Unicom, OPPO | imported from 3GU |
| S2‑183290 | 3GPP PS Data Off Clarification | Intel, Telecom Italia, Deutsche Telekom, Nokia, Nokia Shanghai Bell, Huawei, Hisilicon, Qualcomm, ZTE, MediaTek Inc., CMCC, China Unicom, OPPO | imported from 3GU |
| S2‑183291 | Network Sharing and Interworking Clarification | Intel, ZTE | imported from 3GU |
| S2‑183292 | Clarify related description for Network Sharing and Interworking | Intel, ZTE | imported from 3GU |
| S2‑183293 | Clarification on UE behavior on receiving empty Allowed NSSAI | Intel | imported from 3GU |
| S2‑183294 | Clarification in LADN clause 5.6.5 | Intel, AT&T, KDDI, OPPO | imported from 3GU |
| S2‑183295 | Solution for key issue #5 | Intel, LG Electronics | imported from 3GU |
| S2‑183296 | Solution for key issue #6 | Intel | imported from 3GU |
| S2‑183297 | New key issue on NWDAF assisting traffic routing | Intel, AT&T | imported from 3GU |
| S2‑183298 | New solution on NWDAF influencing traffic routing | Intel, AT&T | imported from 3GU |
| S2‑183299 | SRVCC Architecture from NG-RAN to UTRAN CS | Intel, Huawei, Hisilicon | imported from 3GU |
| S2‑183300 | New key issue on enabling SRVCC from NG-RAN to UTRAN CS | Intel | imported from 3GU |
| S2‑183301 | New key issue on SRVCC HO Procedure from NG-RAN to UTRAN CS | Intel | imported from 3GU |
| S2‑183302 | New key issue on returning UE to NG-RAN from UTRAN CS | Intel | imported from 3GU |
| S2‑183303 | New solution on returning UE to NG-RAN from UTRAN CS | Intel | imported from 3GU |
| S2‑183304 | TR 23.715: Update to Architectural Assumptions for PARLOS | OTD | imported from 3GU |
| S2‑183305 | TR 23.715: Update to Architectural Assumptions for PARLOS | OTD | imported from 3GU |
| S2‑183306 | TR 23.731: Update to Privacy Check with UE Privacy Setting | OTD | imported from 3GU |
| S2‑183307 | TR 23.731: Update to Privacy Check with UE Privacy Setting | OTD | imported from 3GU |
| S2‑183308 | Missing requirements to trigger Notification Control | Ericsson | imported from 3GU |
| S2‑183309 | Removal of Allowed NSSAI indication to RAN | Ericsson | imported from 3GU |
| S2‑183310 | [DRAFT] LS reply to LS from SA WG4: LS on QoS for Live Uplink Streaming (FLUS) | Ericsson | imported from 3GU |
| S2‑183311 | Use of priority parameters in scheduling | Ericsson | imported from 3GU |
| S2‑183312 | Modifications for 6 bit QFI | Ericsson | imported from 3GU |
| S2‑183313 | Clarifications to Registration and UE triggered Service Request procedure | Ericsson | imported from 3GU |
| S2‑183314 | Clarification on Data Off reporting | Ericsson | imported from 3GU |
| S2‑183315 | Discussion for LS from RAN WG2 on PC5 transmission mechanism selection (S2-183098/ R2-1804090) | LG Electronics | imported from 3GU |
| S2‑183316 | [DRAFT] Reply LS on PC5 transmission mechanism selection | LG Electronics | imported from 3GU |
| S2‑183317 | Addition of PDU Session Type in Route Selection Descriptor | Huawei, HiSilicon | imported from 3GU |
| S2‑183318 | Correction on Policy Control Request Triggers | Huawei, HiSilicon | imported from 3GU |
| S2‑183319 | The interaction between PCF and AF | Huawei, HiSilicon | imported from 3GU |
| S2‑183320 | Clarification on different set of URSP rules | Huawei, HiSilicon | imported from 3GU |
| S2‑183321 | Discussion on way forward for MT SMS domain selection by SMSF | LG Electronics | imported from 3GU |
| S2‑183322 | Clarification on MT SMS domain selection by SMSF | LG Electronics | imported from 3GU |
| S2‑183323 | Key issue on QoS Monitoring for 5G URLLC SID | Huawei, Hisilicon | imported from 3GU |
| S2‑183324 | Clarification on MT SMS domain selection by SMSF | LG Electronics | imported from 3GU |
| S2‑183325 | Correction to CN-initiated selective deactivation of UP connection of an existing PDU Session | Huawei, HiSilicon | imported from 3GU |
| S2‑183326 | TS 23.501: Clean-up for UE Configuration Update procedure | Huawei, HiSilicon | imported from 3GU |
| S2‑183327 | Clarification of the mapping releation between PDU session ID and access type in the AMF. | Huawei, HiSilicon | imported from 3GU |
| S2‑183328 | TS 23.501: Clean-up for the parts of RRC Inactive | Huawei, HiSilicon | imported from 3GU |
| S2‑183329 | TS 23.502: Clean-up for the parts of RRC Inactive | Huawei, HiSilicon | imported from 3GU |
| S2‑183330 | UE DL Signalling handling in RRC Inactive State | Huawei, HiSilicon | imported from 3GU |
| S2‑183331 | [DRAFT] LS Reply on DRX parameters negotiation | Huawei, HiSilicon | imported from 3GU |
| S2‑183332 | Cleanup to PCF selection in AMF and SMF | Huawei, HiSilicon | imported from 3GU |
| S2‑183333 | Description for policy association | Huawei, HiSilicon | imported from 3GU |
| S2‑183334 | 503: UE Policy Delivery | Huawei, HiSilicon | imported from 3GU |
| S2‑183335 | TS 23.502 Wildcard DNN management | Huawei, HiSilicon | imported from 3GU |
| S2‑183336 | TS 23.501 Correction on Control Plane protocol stacks | Huawei, HiSilicon | imported from 3GU |
| S2‑183337 | Solutions of Reflective QoS Restriction in UE | Huawei, HiSilicon | imported from 3GU |
| S2‑183338 | TR Skeleton of 5G URLLC | Huawei, Hisilicon | imported from 3GU |
| S2‑183339 | TR Scope of 5G URLLC | Huawei, Hisilicon | imported from 3GU |
| S2‑183340 | Architecture assumption of 5G URLLC | Huawei, Hisilicon | imported from 3GU |
| S2‑183341 | Key issue of supporting high reliability for URLLC services | Huawei, Hisilicon | imported from 3GU |
| S2‑183342 | Key issue of supporting low latency and jitter during handover procedure | Huawei, Hisilicon | imported from 3GU |
| S2‑183343 | Key issue of supporting session continuity for URLLC services | Huawei, Hisilicon | imported from 3GU |
| S2‑183344 | Update of UE Configured NSSAI | Huawei, Hisilicon | imported from 3GU |
| S2‑183345 | Update of UE Configured NSSAI | Huawei, Hisilicon | imported from 3GU |
| S2‑183346 | PDU Session Address Lifetime for SSC mode3 | Huawei, Hisilicon | imported from 3GU |
| S2‑183347 | Clarification on HO procedure | Huawei, Hisilicon | imported from 3GU |
| S2‑183348 | Clarification of Data Notification in service request procedure | Huawei, Hisilicon | imported from 3GU |
| S2‑183349 | Additional PDU Session Type in Route Selection Descriptor | Huawei, Hisilicion | imported from 3GU |
| S2‑183350 | Discussion on enabling the URSP | Huawei, Hisilicion | imported from 3GU |
| S2‑183351 | Clarification on 'match all ' URSP rule | Huawei, Hisilicion | imported from 3GU |
| S2‑183352 | Correlation between EBI and QFI | Huawei, Hisilicion | imported from 3GU |
| S2‑183353 | Multiple PDU session for same DNN | Huawei, Hisilicion | imported from 3GU |
| S2‑183354 | [DRAFT] Response to LS on 5G-GUTI type | Huawei, Hisilicion | imported from 3GU |
| S2‑183355 | Clarification on NSSAI related functionality in 5G RAN | Qualcomm Finland RFFE Oy | imported from 3GU |
| S2‑183356 | Application detection report when PFDs are removed | Huawei, Hisilicon | imported from 3GU |
| S2‑183357 | Application detection report when PFDs are removed | Huawei, Hisilicon | imported from 3GU |
| S2‑183358 | TS 23.501 Clarification on Application data | Huawei, Hisilicon | imported from 3GU |
| S2‑183359 | TS 23.502 Clarification on Application data | Huawei, Hisilicon | imported from 3GU |
| S2‑183360 | Updates on Subscribe Service Operation | Huawei, Hisilicon | imported from 3GU |
| S2‑183361 | ATSSS Rule definition and TFCP procedure update | Huawei, Hisilicon | imported from 3GU |
| S2‑183362 | Encrypted traffic detection and verification | Huawei, Hisilicon | imported from 3GU |
| S2‑183363 | Solution for utilizing services provided by 5GC | Huawei, Hisilicon | imported from 3GU |
| S2‑183364 | Consideration on SBA-based Sh | Huawei, Hisilicon | imported from 3GU |
| S2‑183365 | Solution for KI on Discovery of Network Functions | Huawei, Hisilicon | imported from 3GU |
| S2‑183366 | Consideration on SBA-based Cx | Huawei, Hisilicon | imported from 3GU |
| S2‑183367 | Solutions for common IMS network through multiple 5GC network slices | Huawei, Hisilicon | imported from 3GU |
| S2‑183368 | Discussion on IMS Device Configuration in 5G | Huawei, Hisilicon | imported from 3GU |
| S2‑183369 | Solution for IMS device configuration in 5G | Huawei, Hisilicon | imported from 3GU |
| S2‑183370 | TS_23.502 CR Alignment on the IMS voice over PS session supported indication | Huawei, Hisilicon | imported from 3GU |
| S2‑183371 | Update of UE Configured NSSAI | Huawei, Hisilicon | imported from 3GU |
| S2‑183372 | PDU Session Address Lifetime for SSC mode3 | Huawei, Hisilicon | imported from 3GU |
| S2‑183373 | Clarification on RAT fallback | LG Electronics Inc. | imported from 3GU |
| S2‑183374 | Clarification on RAT fallback | LG Electronics Inc. | imported from 3GU |
| S2‑183375 | Clarification on support of simultaneous registration of both MME and AMF | LG Electronics Inc. | imported from 3GU |
| S2‑183376 | Capturing PDN connection handling for without N26 interworking | LG Electronics Inc. | imported from 3GU |
| S2‑183377 | Clarification on AMF deregistration by UDM in N26 based interworking from 5GS to EPS | LG Electronics | imported from 3GU |
| S2‑183378 | Handover type for eLTE connected both 5GC and EPC | LG Electronics Inc. | imported from 3GU |
| S2‑183379 | Clarification to CM state handling | LG Electronics Inc. | imported from 3GU |
| S2‑183380 | Solution proposal 'Adjustable periodic Registration Update' for UE power saving | LG Electronics, SK Telecom, LG Uplus | imported from 3GU |
| S2‑183381 | Clarification on Registration procedure for SMS over NAS | LG Electronics | imported from 3GU |
| S2‑183382 | Clarification on Registration procedure for SMS over NAS | LG Electronics | imported from 3GU |
| S2‑183383 | Clarification on Network-initiated Deregistration | LG Electronics | imported from 3GU |
| S2‑183384 | Clarification on notification message | LG Electronics | imported from 3GU |
| S2‑183385 | Selective deactivation of UP connection for non-3GPP PDU Session | LG Electronics | imported from 3GU |
| S2‑183386 | Solution for KI5: Delay UL transmission for MO case | OPPO | imported from 3GU |
| S2‑183387 | Solution for KI5: Delay Paging Response for MT case | OPPO | imported from 3GU |
| S2‑183388 | Traffic steering with ATSSS Policy | Motorola Mobility, Lenovo | imported from 3GU |
| S2‑183389 | Update of UE-Assisted Solution | Motorola Mobility, Lenovo | imported from 3GU |
| S2‑183390 | ATSSS procedure for TFCP solution | OPPO | imported from 3GU |
| S2‑183391 | Scope of FS_eNS TR 23.740 | Telecom Italia, ZTE | imported from 3GU |
| S2‑183392 | Skeleton of the TR 23.740 | Telecom Italia, ZTE | imported from 3GU |
| S2‑183393 | Network Slice isolation | Telecom Italia | imported from 3GU |
| S2‑183394 | Solution for Network Slice coexistence | Telecom Italia | imported from 3GU |
| S2‑183395 | Editorial correction in clause 5.9.2 Subscription Permanent Identifier | Telecom Italia | imported from 3GU |
| S2‑183396 | Correction to DNN subscription | Telecom Italia | imported from 3GU |
| S2‑183397 | 5GS support for network slicing | Telecom Italia | imported from 3GU |
| S2‑183398 | Lack of S-NSSAI or DNN in the PDU Session Establishment Request | Telecom Italia | imported from 3GU |
| S2‑183399 | On access stratum considerations for network slicing | Nokia, Nokia Shanghai Bell, NEC | imported from 3GU |
| S2‑183400 | On delivering Delay critical service consistently end to end | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183401 | Insufficient UE resources for signalled QoS rules | Intel | imported from 3GU |
| S2‑183402 | Clarification on the support of Delay Critical resource type | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183403 | Network Slicing clause cleanup | Nokia, Nokia Shanghai Bell, Mediatek, Telecom Italia | imported from 3GU |
| S2‑183404 | Alignment to BBF result: KI5 handover solution | Huawei, Hisilicon | imported from 3GU |
| S2‑183405 | Discussion on support of eCall and emergency services when E-UTRAN is connected to EPC and 5GC | NEC Europe Ltd | imported from 3GU |
| S2‑183406 | Support of eCall when E-UTRAN is connected to EPC and 5GC | NEC Europe Ltd | imported from 3GU |
| S2‑183407 | Support of emergency services when E-UTRAN is connected to EPC and 5GC | NEC Europe Ltd | imported from 3GU |
| S2‑183408 | [DRAFT] Reply LS on 5G-GUTI type | Qualcomm Incorporated | imported from 3GU |
| S2‑183409 | [DRAFT] Reply LS on clarification of NSSAI information exchange during Inactive to connected mode transition | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183410 | Solution for RLOS attach procedure | NEC Europe Ltd | imported from 3GU |
| S2‑183411 | IPv6 Multi-homing capability report | Spreadtrum Communications | imported from 3GU |
| S2‑183412 | Associated access type of PDU Session updating | Spreadtrum Communications | imported from 3GU |
| S2‑183413 | IMS T-ADS with dual registered UE | Spreadtrum Communications | imported from 3GU |
| S2‑183414 | Multi-user share the same IMS signaling bearer | Spreadtrum Communications | imported from 3GU |
| S2‑183415 | User preference has higher priority than NSSP in URSP when UE selects the S-NSSAI for PDU Session Establishment | Spreadtrum Communications | imported from 3GU |
| S2‑183416 | UE and network shall overide the Core Network type restriction for regulatory prioritized services | Spreadtrum Communications | imported from 3GU |
| S2‑183417 | Clarification to the usage of Internal-Group Identifiers | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183418 | Clarification to the usage of Internal-Group Identifiers | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183419 | Support of End Markers in 5GS: case of Dual Connectivity and of EPC IWK | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183420 | Different types of Ethernet services and N4 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183421 | Providing AF with information on the N6 User Plane tunelling information | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183422 | Interactions with the DN-AAA that are not for authentication | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183423 | SMF getting UE location from the AMF for NPLI when no QoS flow to create/Update/modify | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183424 | Update Solution 6 | Sony | imported from 3GU |
| S2‑183425 | Resolution of outstanding issue on eight S-NSSAIs restriction | MediaTek Inc., Qualcomm Incorporated, Intel, Huawei, HiSilicon | imported from 3GU |
| S2‑183426 | Removal of network restriction for eight concurrent S-NSSAIs when serving a UE | MediaTek Inc., Qualcomm Incorporated, Intel, Huawei, HiSilicon | imported from 3GU |
| S2‑183427 | Removal of duplicated requirements for Allowed/Configured NSSAI | MediaTek Inc. | imported from 3GU |
| S2‑183428 | Clarification to handling of packet filters at PDU Session Modification | MediaTek Inc. | imported from 3GU |
| S2‑183429 | N3GPP TAI | MediaTek Inc. | imported from 3GU |
| S2‑183430 | [DRAFT] LS on N3GPP TAI | MediaTek Inc. | imported from 3GU |
| S2‑183431 | Correction to AMF and S-NSSAI overload control | MediaTek Inc. | imported from 3GU |
| S2‑183432 | Handling of UE Capability ID | MediaTek Inc. | imported from 3GU |
| S2‑183433 | [DRAFT] LS on optimisation of UE capability signalling | MediaTek Inc. | imported from 3GU |
| S2‑183434 | LADN Signaling to SMF | Sony | imported from 3GU |
| S2‑183435 | Monitoring Event configuration removal for a group | Huawei, Hisilicon | imported from 3GU |
| S2‑183436 | Correction to the group message delivery | Huawei, Hisilicon | imported from 3GU |
| S2‑183437 | Deletion of Network Parameter Configuration | Huawei, Hisilicon | imported from 3GU |
| S2‑183438 | Corrections on UE configuration update procedure | Huawei, Hisilicon | imported from 3GU |
| S2‑183439 | Multiple PDU session per DNN | Huawei, Hisilicon | imported from 3GU |
| S2‑183440 | [DRAFT] ReplyLS on Paging with IMSI | Huawei, Hisilicon | imported from 3GU |
| S2‑183441 | AMF Name and AMF N2AP UE ID | Huawei, Hisilicon | imported from 3GU |
| S2‑183442 | Discussion on TAC for NG-RAN | Huawei, Hisilicon | imported from 3GU |
| S2‑183443 | [DRAFT] ReplyLS on Extending TAC for NR and NG-RA | Huawei, Hisilicon | imported from 3GU |
| S2‑183444 | [DRAFT] ReplyLS on TAI and forbidden TAI list for 5GS | Huawei, Hisilicon | imported from 3GU |
| S2‑183445 | Correction for support of the Ethernet Type PDU Session | Huawei, Hisilicon | imported from 3GU |
| S2‑183446 | How AMF provides LADN Information to UE | Huawei, HiSilicon | imported from 3GU |
| S2‑183447 | EBI allocation for HR roaming case | Huawei, Hisilicon | imported from 3GU |
| S2‑183448 | SMF registers to HSS/UDM | Huawei, Hisilicon | imported from 3GU |
| S2‑183449 | CN Tunnel establishment for interworking handover | Huawei, Hisilicon | imported from 3GU |
| S2‑183450 | Select the same SMF+UPF for PDU sessions of the same DNN | Huawei, HiSilicon | imported from 3GU |
| S2‑183451 | Subscription status notification for Event Exposure service | Huawei, Hisilicon | imported from 3GU |
| S2‑183452 | Subscription status notification for Event Exposure service | Huawei, Hisilicon | imported from 3GU |
| S2‑183453 | Solution for KI_ common north-bound APIs for EPC-5GC interworking | Huawei, Hisilicon | imported from 3GU |
| S2‑183454 | Service Area of SMF | Huawei, Hisilicon | imported from 3GU |
| S2‑183455 | Inter I-SMF mobility | Huawei, Hisilicon | imported from 3GU |
| S2‑183456 | ULCL relocation and release | Huawei, Hisilicon | imported from 3GU |
| S2‑183457 | Enhancement for IP allocation solution | Huawei, HiSilicon | imported from 3GU |
| S2‑183458 | Resource management of UPF shared by multiple SMFs during UPF relocation | Huawei, HiSilicon | imported from 3GU |
| S2‑183459 | Discussion on slice related congestion control handling at RAN node | NEC Europe Ltd | imported from 3GU |
| S2‑183460 | Correction of non-3GPP to E-UTRAN handovers | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183461 | Correction of non-3GPP to E-UTRAN handovers | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183462 | Removal of editor's notes in clause 4.12 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183463 | Determination of ePDG vs N3IWF function is a combined ePDG-N3IWF node | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183464 | Architecture framework with ATSSS rules and UP Access Agnostic Reporting Control Protocol | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183465 | Solution for localized routing based on OMR | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183466 | Solution: IMS procedures for RLOS | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183467 | Clarification on SMF selection | LG Electronics | imported from 3GU |
| S2‑183468 | Clarification on SMF selection | LG Electronics | imported from 3GU |
| S2‑183469 | Clarification on SMSF selection | LG Electronics | imported from 3GU |
| S2‑183470 | Clarification on policy provision in roaming case | LG Electronics | imported from 3GU |
| S2‑183471 | Clarification on policy provision in roaming case | LG Electronics | imported from 3GU |
| S2‑183472 | Clarification on the figures for the roaming aspects | LG Electronics | imported from 3GU |
| S2‑183473 | Clarification on PCF ID and PCF selection in the HO procedure | LG Electronics | imported from 3GU |
| S2‑183474 | Correction to identifiers in Registration procedure | Intel | imported from 3GU |
| S2‑183475 | Correction to identifiers in Registration procedure | Intel | imported from 3GU |
| S2‑183476 | Authentication Related Services | Ericsson | imported from 3GU |
| S2‑183477 | [DRAFT] Reply LS on authentication related services provided by AUSF and UDM | Ericsson | imported from 3GU |
| S2‑183478 | Alignment with the definition of PCF-AMF and PCF-SMF interfaces | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183479 | Clarification on DNAI and PRA mapping | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183480 | Clarification on DNAI and PRA mapping | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183481 | Remove Tracking Area from cell information for shared network | Ericsson Inc. | imported from 3GU |
| S2‑183482 | Update for providing policy requirements to multiple UEs | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183483 | Network slicing information as the service input parameter of BSF service operations | Nokia, Nokia Shanghai Bell, China Mobile? | imported from 3GU |
| S2‑183484 | Mobility Event initial report | Sony Corporation | imported from 3GU |
| S2‑183485 | Cleanups on the support of session binding for Ethernet PDU session Type | Nokia, Nokia Shanghai Bell, China Mobile? | imported from 3GU |
| S2‑183486 | Skeleton of AAI_LTE_NR TR | China Telecom | imported from 3GU |
| S2‑183487 | Scope of AAI_LTE_NR TR | China Telecom,AT&T | imported from 3GU |
| S2‑183488 | Architectural Assumptions for AAI_LTE_NR | China Telecom | imported from 3GU |
| S2‑183489 | New Key Issue: The criteria of making the decision and generating the assistant information provided to RAN | China Telecom | imported from 3GU |
| S2‑183490 | New Key Issue: Special aspect for scenario 2 | China Telecom | imported from 3GU |
| S2‑183491 | NEF and UDR in LBO architecture for AF influence on traffic routing | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183492 | Network slicing information for binding the AF request to the relevant PCF | Nokia, Nokia Shanghai Bell, China Mobile? | imported from 3GU |
| S2‑183493 | Enhancement to existing location service solution for commercial use cases | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183494 | Controlled support of (AF) session binding for Ethernet PDU Session Type | Nokia, Nokia Shanghai Bell, China Mobile? | imported from 3GU |
| S2‑183495 | Solution 2 Update: NW-Requested Establishment of MA-PDU session | Motorola Mobility, Lenovo | imported from 3GU |
| S2‑183496 | Study on system architecture for next generation real time communication services | China Mobile,AT&T?, CATR, CATT, China Telecom, China Unicom?, Deutsche Telekom, Huawei, Institute for Information Industry, OPPO, Telefonica, Verizon, ZTE | imported from 3GU |
| S2‑183497 | Update on AMF service operation to support query for terminating domain selection for IMS voice | China Mobile | imported from 3GU |
| S2‑183498 | Discussion on SMSF domain selecion | China Mobile | imported from 3GU |
| S2‑183499 | Update on architecture to support MT SMS domain selection | China Mobile | imported from 3GU |
| S2‑183500 | Update on SMSoNAS procedures to support MT SMS domain selection | China Mobile | imported from 3GU |
| S2‑183501 | Correction on Nsmsf_SMService_Activate service operation | China Mobile | imported from 3GU |
| S2‑183502 | Solution 1 on IMS supporting N5 and Rx simultaneously | China Mobile | imported from 3GU |
| S2‑183503 | Solution 2 on IMS supporting N5 and Rx simultaneously | China Mobile | imported from 3GU |
| S2‑183504 | Solution5 Update: Privacy Check procedure W.R.T. LMF based architecture | vivo | imported from 3GU |
| S2‑183505 | Discussion on issues for 5G to 3G SRVCC Initiation | vivo | imported from 3GU |
| S2‑183506 | Architectural Assumptions for 5G to 3G SRVCC | vivo | imported from 3GU |
| S2‑183507 | Registration for 5G to 3G SRVCC | vivo | imported from 3GU |
| S2‑183508 | How to return to 5G | vivo | imported from 3GU |
| S2‑183509 | Correction of Provision parameters flow | Ericsson Inc. | imported from 3GU |
| S2‑183510 | SMF assisted RAN information | Motorola Mobility, Lenovo | imported from 3GU |
| S2‑183511 | Removal of MO SMS using one step approach in CM-IDLE | Ericsson Inc. | imported from 3GU |
| S2‑183512 | Classification of external parameters to MM and SM parameters | Motorola Mobility, Lenovo | imported from 3GU |
| S2‑183513 | [DRAFT] Reply LS one step MO SMS procedure | Ericsson Inc. | imported from 3GU |
| S2‑183514 | Clarifying handling of reachability state | Ericsson Inc. | imported from 3GU |
| S2‑183515 | Optimizations for decision data pcc rule elements | Oracle Corporation | imported from 3GU |
| S2‑183516 | Solution for Key Issue #3: Access to 5GC from UEs that do not support NAS | Motorola Mobility, Lenovo | imported from 3GU |
| S2‑183517 | Dual Registration mode of operation from E-UTRA cell connecting to both EPC and 5GC | Intel | imported from 3GU |
| S2‑183518 | Solution 1 update | Deutsche Telekom | imported from 3GU |
| S2‑183519 | PLMN selection and radio access for RLOS | Motorola Mobility, Lenovo | imported from 3GU |
| S2‑183520 | Proposal of UE Policy for Background Data Transfer | KDDI | imported from 3GU |
| S2‑183521 | Addition of Broadcast of Assistance Data for E-UTRAN | Qualcomm Incorporated | imported from 3GU |
| S2‑183522 | Consolidation of UE Network Capabilities | Qualcomm Incorporated | imported from 3GU |
| S2‑183523 | Consolidation of UE Network Capabilities | Qualcomm Incorporated | imported from 3GU |
| S2‑183524 | MM Backoff timer for IMS emergency/HP calls | Qualcomm Incorporated | imported from 3GU |
| S2‑183525 | NAS level congestion control for emergency and high priority access | Qualcomm Incorporated | imported from 3GU |
| S2‑183526 | Coexistence of RRC Inactive and Dual Connectivity | Qualcomm Incorporated | imported from 3GU |
| S2‑183527 | [DRAFT] Reply LS on coexistence between RRC inactive and dual connectivity | Qualcomm Incorporated | imported from 3GU |
| S2‑183528 | Removal of one step SMS procedure | Qualcomm Incorporated | imported from 3GU |
| S2‑183529 | Mapped parameters in case of No N26 | Qualcomm Incorporated | imported from 3GU |
| S2‑183530 | [DRAFT] Reply LS on handling of EPS bearer context and PDU session context for interworking without N26 | Qualcomm Incorporated | imported from 3GU |
| S2‑183531 | Need for UE and Core Network Capability for increased number of bearers | Qualcomm Incorporated, Samsung, ZTE | imported from 3GU |
| S2‑183532 | UE Capability for supporting 15 EPS bearers | Qualcomm Incorporated, Samsung, ZTE | imported from 3GU |
| S2‑183533 | Network support for increased number of bearers | Qualcomm Incorporated, Samsung, ZTE | imported from 3GU |
| S2‑183534 | Preferred PLMN list for RLOS | Qualcomm Incorporated | imported from 3GU |
| S2‑183535 | Optimisation of UE radio capability signalling | Qualcomm Incorporated | imported from 3GU |
| S2‑183536 | Scope of eSBA TR | China Mobile | imported from 3GU |
| S2‑183537 | Propose Skeleton for eSBA TR 23.742 | China Mobile | imported from 3GU |
| S2‑183538 | Clarifications on Nudr interactions between PCF and UDR for Application Data | Ericsson Inc. | imported from 3GU |
| S2‑183539 | Discussion on UE Policy for Background Data Transfer | KDDI | imported from 3GU |
| S2‑183540 | Update UDR DM service for data subscription | China Mobile | imported from 3GU |
| S2‑183541 | Terminology cleanup | Ericsson Inc. | imported from 3GU |
| S2‑183542 | Editorial corrections on PCC related to SMF | Ericsson Inc. | imported from 3GU |
| S2‑183543 | Discussion on Architectural Assumptions | Ericsson Inc. | imported from 3GU |
| S2‑183544 | Correction to Nnwdaf_EventsSubscription_Notify (related to nw slice) | KDDI, ETRI, Oracle | imported from 3GU |
| S2‑183545 | Corrections to Service Request procedure | InterDigital Inc. | imported from 3GU |
| S2‑183546 | NAS Notification Response in NW triggered Service Request procedure | InterDigital Inc. | imported from 3GU |
| S2‑183547 | Clarification on the use of shared AMF Pointer value | Intel | imported from 3GU |
| S2‑183548 | UCU procedure and Access Type | InterDigital Communications | imported from 3GU |
| S2‑183549 | Clarification on the use of shared AMF Pointer value | Intel | imported from 3GU |
| S2‑183550 | UE Requested Multi-access PDU Session Establishment | InterDigital Communications | imported from 3GU |
| S2‑183551 | Network-controlled Traffic Steering for Multi-access PDU Session | InterDigital Communications | imported from 3GU |
| S2‑183552 | KI5 Solution Delay Tolerant PDU session | InterDigital Communications | imported from 3GU |
| S2‑183553 | KI2 Solution RRC Inactive for frequent small data transmission | InterDigital Communications | imported from 3GU |
| S2‑183554 | Clarification on NGAP UE-TNLA-binding per UE Release procedure | Intel | imported from 3GU |
| S2‑183555 | KI1 Solution Update Small data without PDU session | InterDigital Communications | imported from 3GU |
| S2‑183556 | SM_23.501_ReAuthentication by an external DN-AAA server | InterDigital Communications | imported from 3GU |
| S2‑183557 | SM_23.502_ReAuthentication by an external DN-AAA server | InterDigital Communications | imported from 3GU |
| S2‑183558 | Update to Solution #5 | Intel | imported from 3GU |
| S2‑183559 | 23.716 solutions: Support of IPTV | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183560 | 23.716 solutions: IPV6 address allocation mechanisms for RGW | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183561 | Updates to SMF Event Exposure | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183562 | DOCSIS solution for WWC | CableLabs | imported from 3GU |
| S2‑183563 | DOCSIS solution for WWC | CableLabs, Charter Communications, Comcast | imported from 3GU |
| S2‑183564 | Low Access Priority in 5G system | Qualcomm UK Ltd | imported from 3GU |
| S2‑183565 | Introducing low access priority to 5G system | Qualcomm UK Ltd | imported from 3GU |
| S2‑183566 | Solution for Key Issue 1: RRC Inactive with CM IDLE state | Qualcomm UK Ltd | imported from 3GU |
| S2‑183567 | Solution Key issue 3 (HLCom): Extended buffering at UPF of MT data for user plane | Qualcomm UK Ltd | imported from 3GU |
| S2‑183568 | Solution KI-14: QoS for Data over NAS | Qualcomm UK Ltd | imported from 3GU |
| S2‑183569 | Key Issue on Slice Interworking between 5GC and EPC | Qualcomm Finland RFFE Oy | imported from 3GU |
| S2‑183570 | Alternative UE-assisted ENTRADE solution | Qualcomm Finland RFFE Oy | imported from 3GU |
| S2‑183571 | Architectural assumptions | Qualcomm Finland RFFE Oy | imported from 3GU |
| S2‑183572 | Key Issue on Application-related RAT preferences | Qualcomm Finland RFFE Oy | imported from 3GU |
| S2‑183573 | IMS Partial Service Request | T-Mobile USA Inc. | imported from 3GU |
| S2‑183574 | Clarifications for solutions 1/2/3 for LADN and local area | T-Mobile USA Inc. | imported from 3GU |
| S2‑183575 | Solution #9 Evaluation | T-Mobile USA Inc. | imported from 3GU |
| S2‑183576 | Update to Solution #9 to resolve open EN | T-Mobile USA Inc. | imported from 3GU |
| S2‑183577 | PGW Allocation of Bearer IDs to accommodate non-ubiquitous 15 bearer support | T-Mobile USA | imported from 3GU |
| S2‑183578 | Solution for the key issue x: Single radio voice continuity from 5GS to 3G | Huawei, HiSilicon, China Unicom | imported from 3GU |
| S2‑183579 | ATSSS Solution – Update of Solution 2 | LG Electronics | imported from 3GU |
| S2‑183580 | ATSSS Solution - Differentiation of 3GPP RATs in ATSSS Rule | LG Electronics | imported from 3GU |
| S2‑183581 | URSP Rule and ATSSS Rule | LG Electronics | imported from 3GU |
| S2‑183582 | Clairifcation on PDU Session Establishment procedure | LG Electronics | imported from 3GU |
| S2‑183583 | LADN configuration of UE | LG Electronics | imported from 3GU |
| S2‑183584 | Removing support of MOBIKE | LG Electronics | imported from 3GU |
| S2‑183585 | Clarification on the QFI equals 5QI option | CATT, OPPO | imported from 3GU |
| S2‑183586 | Policy related update in the PDU Session Establishment procedure | CATT | imported from 3GU |
| S2‑183587 | Updates to Solution #2 | Cisco Systems | imported from 3GU |
| S2‑183588 | AF Control of Make-before-break PDN Connection | Cisco Systems | imported from 3GU |
| S2‑183589 | Not limiting the range of QFI to 64 | Cisco Systems, Verizon | imported from 3GU |
| S2‑183590 | [DRAFT] Reply LS on QoS | Cisco Systems, Verizon | imported from 3GU |
| S2‑183591 | Updates to Solution #5 | Cisco Systems | imported from 3GU |
| S2‑183592 | Remove PCF as the consumer of Namf_EventExposure and Nsmf_EventExposure services | CATT | imported from 3GU |
| S2‑183593 | Clarification on the Nx tunnel release in Solution 2 | CATT | imported from 3GU |
| S2‑183594 | Clarification on Infrequent small data transfer via NAS-SM | China Mobile | imported from 3GU |
| S2‑183595 | Optionality of SMF selection for small data solution 2 | China Mobile | imported from 3GU |
| S2‑183596 | Optional Duplidate Address Detection for V2X Communication over PC5 | Qualcomm Incorporated, LG Electronics, Intel | imported from 3GU |
| S2‑183597 | General Framework for 5G network automation | China Mobile | imported from 3GU |
| S2‑183598 | Optional Duplidate Address Detection for V2X Communication over PC5 | Qualcomm Incorporated, LG Electronics, Intel | imported from 3GU |
| S2‑183599 | RFSP selection proposal for Key Issue 1 | China Mobile | imported from 3GU |
| S2‑183600 | S-NSSAI Based Congestion Control | Qualcomm CDMA Technologies | imported from 3GU |
| S2‑183601 | Key issue on performance improvement and supervision of mIoT terminals | China Mobile | imported from 3GU |
| S2‑183602 | Add PPPR introduction to ProSe QoS descriptions | Qualcomm Incorporated, Ericsson, OPPO, Intel | imported from 3GU |
| S2‑183603 | Clarification of S-NSSAI based congestion control | Qualcomm CDMA Technologies | imported from 3GU |
| S2‑183604 | Solution for performance improvement and supervision of mIoT terminals | China Mobile | imported from 3GU |
| S2‑183605 | Clarification on the Data Reporting for Secondary RAT | NTT DOCOMO INC. | imported from 3GU |
| S2‑183606 | Discussion on the handling of new incompatible RAN Tx features for PC5 | Qualcomm Incorporated, LG Electronics | imported from 3GU |
| S2‑183607 | Indirect Data forwarding for N2 HO | Qualcomm CDMA Technologies | imported from 3GU |
| S2‑183608 | [DRAFT] Reply LS on data forwarding for intra-system handover | Qualcomm CDMA Technologies | imported from 3GU |
| S2‑183609 | Add inidcation of Notification Control to QoS rules sent to UE | Qualcomm Incorporated | imported from 3GU |
| S2‑183610 | Paging with IMSI/SUCI | Qualcomm CDMA Technologies | imported from 3GU |
| S2‑183611 | [DRAFT] Reply LS on paging with IMSI/SUCI in 5GS | Qualcomm CDMA Technologies | imported from 3GU |
| S2‑183612 | Discussion on MDBV enforcement | Qualcomm Incorporated | imported from 3GU |
| S2‑183613 | Solution of Direct SRVCC procedure | Qualcomm CDMA Technologies | imported from 3GU |
| S2‑183614 | Solution of Indirect SRVCC procedure | Qualcomm CDMA Technologies | imported from 3GU |
| S2‑183615 | Key Issue of Analysis PS HO support in SRVCC from 5G to 3G | Qualcomm CDMA Technologies | imported from 3GU |
| S2‑183616 | [DRAFT] LS on MDBV enforcement for delay critical QoS flows | Qualcomm Incorporated | imported from 3GU |
| S2‑183617 | Local deactivate MICO for emergency service | Qualcomm CDMA Technologies | imported from 3GU |
| S2‑183618 | Support use of DNN for URSP traffic descriptor | Qualcomm Incorporated, Intel | imported from 3GU |
| S2‑183619 | Mechanism to avoid UE re-registration due to UE configuration update under critical conditions | Apple | imported from 3GU |
| S2‑183620 | Unicast and multicast V2X communication support over PC5 | Qualcomm Incorporated | imported from 3GU |
| S2‑183621 | Key Issue on Support of Flexible and Efficient Periodic and Triggered Location | Qualcomm Incorporated | imported from 3GU |
| S2‑183622 | New solution: MPTCP proxy architecture | Apple | imported from 3GU |
| S2‑183623 | Low Power Periodic and Triggered Location for the LMF Based Solution | Qualcomm Incorporated | imported from 3GU |
| S2‑183624 | Simplify the LADN PDU Session handling | CATT | imported from 3GU |
| S2‑183625 | Solution on extended buffering | CATT | imported from 3GU |
| S2‑183626 | Solution on Service Authorization and Provisioning to UE | CATT | imported from 3GU |
| S2‑183627 | Solution on Service Authorization to NG-RAN | CATT | imported from 3GU |
| S2‑183628 | V2X message transmission profile selection | CATT | imported from 3GU |
| S2‑183629 | New SID on supporting Flexible Local Area Data Network | LG Electronics, SK Telecom, LG Uplus, KT Corp., Verizon UK LTD, Sprint, China Unicom, Telecom Italia, KPN, Samsung, ETRI, ITRI, Cisco, Oracle, Sony | imported from 3GU |
| S2‑183630 | Updates of Solution#5 for UE Registration via Trusted Non-3GPP Access | Intel | imported from 3GU |
| S2‑183631 | Update to solution#4 on Reliable Data Service Support | Intel | imported from 3GU |
| S2‑183632 | Update on Key Issue Description | Huawei, HiSilicon, AT&T | imported from 3GU |
| S2‑183633 | New Key Issue for Data Collection Framework | Huawei, HiSilicon, AT&T | imported from 3GU |
| S2‑183634 | Use Case: NWDA-assisting E2E QoS Assurance | Huawei, HiSilicon | imported from 3GU |
| S2‑183635 | Solution for QoS Provisioning and Adjustment | Huawei, HiSilicon, Intel | imported from 3GU |
| S2‑183636 | Solution for Data Collection Framework | Huawei, HiSilicon, Convida Wireless LLC | imported from 3GU |
| S2‑183637 | Key Issue and Solution for Future Background Data Transfer | Huawei, HiSilicon | imported from 3GU |
| S2‑183638 | Analytic Information Exposure to SMF for Traffic Handling | Huawei, HiSilicon,Convida Wireless LLC | imported from 3GU |
| S2‑183639 | Solution for KI#6 - Management for Enhanced Coverage | Intel | imported from 3GU |
| S2‑183640 | Solution for the differentiation of 3GPP RATs in ATSSS rule | Intel | imported from 3GU |
| S2‑183641 | Paging failure for CE-capable UEs after 2G/3G to 4G idle-mode mobility | Intel | imported from 3GU |
| S2‑183642 | Solution of Key Issues #2, #3, #4 for ATSSS rule | Intel | imported from 3GU |
| S2‑183643 | How SMF validates UE location for LADN | Samsung | imported from 3GU |
| S2‑183644 | Clarification for UE Registration Procedures for Network Slice instance selection in case of multi-access | ZTE Corporation | imported from 3GU |
| S2‑183645 | Trust Model and Architecture Assumption | Intel | imported from 3GU |
| S2‑183646 | Correction on dynamically assigned 5QI | Samsung | imported from 3GU |
| S2‑183647 | Updates of Solution#2 for Resolving Editor Notes | Intel | imported from 3GU |
| S2‑183648 | [DRAFT] LS reply to LS on Questions on Events related to Sevice Data Flows in the Nsmf_EventExposure service | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183649 | Solution of Encrypted Traffic Detection for key issue#2 | Intel | imported from 3GU |
| S2‑183650 | New Key Issue on UE Policy Driven 3GPP RATs Selection with Application Awareness | Intel | imported from 3GU |
| S2‑183651 | Solution of High latency communication and Power Saving Function | Intel | imported from 3GU |
| S2‑183652 | LADN discovery for non-subscription model | Samsung | imported from 3GU |
| S2‑183653 | Architectural Updates for ATSSS Solution 1 | BROADCOM CORPORATION, BT PIc | imported from 3GU |
| S2‑183654 | N4 modificaion inserted during PDU Session Modification | Samsung | imported from 3GU |
| S2‑183655 | Clarifications of Subscribed and Configured S-NSSAI update | ZTE Corporation | imported from 3GU |
| S2‑183656 | Clarifications of ANDSP Functionality | ZTE Corporation | imported from 3GU |
| S2‑183657 | AUSF clarification and alignment | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183658 | Nausf_UEAuthentication Service clarification | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183659 | Correction to references | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183660 | New key issue: Update of NWDA service for load balancing/re-balancing of network function | KDDI Corporation | imported from 3GU |
| S2‑183661 | Updates to Solution #4: Support of Trusted Non-3GPP Access | Motorola Mobility, Lenovo | imported from 3GU |
| S2‑183662 | LS from CableLabs: Include Support for DOCSIS in the 5WWC Study Item | CableLabs | imported from 3GU |
| S2‑183663 | Clarification on N3GPP TAI | Samsung | imported from 3GU |
| S2‑183664 | Correction on capability negotation on 'SMS over NAS' | Samsung | imported from 3GU |
| S2‑183665 | Alignment of the name of the network function | Samsung | imported from 3GU |
| S2‑183666 | Update of PDU Session Establishment Procedure | Samsung | imported from 3GU |
| S2‑183667 | Correction on capability negotation on 'SMS over NAS' | Samsung | imported from 3GU |
| S2‑183668 | Solution for position via user plane transmission | Huawei, HiSilicon | imported from 3GU |
| S2‑183669 | Solution for Slicing dependent location service | Huawei, HiSilicon | imported from 3GU |
| S2‑183670 | Solution for location service exposure | Huawei, HiSilicon | imported from 3GU |
| S2‑183671 | correction on Architectural assumption for emergency service | Samsung | imported from 3GU |
| S2‑183672 | Update to Attributes of a PDU Session Table | Samsung | imported from 3GU |
| S2‑183673 | RLOS service for the attached UE in limited state | Samsung | imported from 3GU |
| S2‑183674 | How to complete RLOS service | Samsung | imported from 3GU |
| S2‑183675 | MA-PDU session release operations | ITRI | imported from 3GU |
| S2‑183676 | Non-3GPP access related aspects for INOBEAR | Telstra Corporation Limited | imported from 3GU |
| S2‑183677 | Update separate establishment for a MA-PDU Session in Solution 2 | ITRI | imported from 3GU |
| S2‑183678 | Solution for TR 23.716: 3GPP UE connects to 5GS via 5G-RG | ITRI | imported from 3GU |
| S2‑183679 | Correction to N2 handover preparation | CATT | imported from 3GU |
| S2‑183680 | support of DRB level data forwarding | CATT | imported from 3GU |
| S2‑183681 | establishing user plane connections during the handover | CATT | imported from 3GU |
| S2‑183682 | Setting indirect data forwarding flag | CATT | imported from 3GU |
| S2‑183683 | Correction on NAS level congestion control | CATT | imported from 3GU |
| S2‑183684 | NWDAF assisted Handover decision | CATT | imported from 3GU |
| S2‑183685 | Optimizing connection management based on NWDAF output | CATT | imported from 3GU |
| S2‑183686 | Optimizing registration area management based on NWDAF output | CATT | imported from 3GU |
| S2‑183687 | Overload avoidance with the help of NWDAF output | CATT | imported from 3GU |
| S2‑183688 | Update to TR 23.716 4.2.2.3 Scenario 3 | ITRI | imported from 3GU |
| S2‑183689 | Updating 6.2 Solution 2 to add a procedure for Multi-Access PDU Session Release | ETRI | imported from 3GU |
| S2‑183690 | Updating 6.2 Solution 2 to support a Multi-Access PDU Session with a single PDU session Id | ETRI | imported from 3GU |
| S2‑183691 | LCS architecture enhancement addressing Key Issue #1 in TR 23.731 | Huawei, HiSilicon | imported from 3GU |
| S2‑183692 | Solution to new KI of supporting non-3GPP access | Huawei, HiSilicon | imported from 3GU |
| S2‑183693 | 23.502: Alignment of terminologies regarding PDU Session | Samsung | imported from 3GU |
| S2‑183694 | Handling of large UE radio capabilities at inter-RAT and SR-VCC handover | Vodafone | imported from 3GU |
| S2‑183695 | Radio efficient handling of large UE radio capabilities at inter-RAT and SRVCC handover | Vodafone | imported from 3GU |
| S2‑183696 | New KI #X: Positioning Access selection for LCS service | CATT | imported from 3GU |
| S2‑183697 | INOBEAR support for mobility procedure | ZTE | imported from 3GU |
| S2‑183698 | INOBEAR support in Session Management procedure | ZTE | imported from 3GU |
| S2‑183699 | TS23.501 Clarification on Internal Group ID | ZTE | imported from 3GU |
| S2‑183700 | TS23.502 Clarification on Internal Group ID | ZTE | imported from 3GU |
| S2‑183701 | TS23.502 Clarification on Access and mobility related policy | ZTE | imported from 3GU |
| S2‑183702 | TS23.503 Clarification on Access and mobility related policy | ZTE | imported from 3GU |
| S2‑183703 | TS 23.501 Clarification on AMF management | ZTE | imported from 3GU |
| S2‑183704 | TS23.502 Clarification on AMF Subscription Correlation ID | ZTE | imported from 3GU |
| S2‑183705 | TS23.503 Clarification on BSF | ZTE | imported from 3GU |
| S2‑183706 | TS23.502 Additional DataSet and Datakey | ZTE | imported from 3GU |
| S2‑183707 | TS23.503 ePDG/N3IWF selection information | ZTE | imported from 3GU |
| S2‑183708 | TS23.502 Nnef_TrafficInfluence service | ZTE | imported from 3GU |
| S2‑183709 | TS23.502 Remove access independent event trigger in Nsmf_EventExposure Service | ZTE | imported from 3GU |
| S2‑183710 | Addition last known RAN information in solution 5 | ZTE | imported from 3GU |
| S2‑183711 | Solution for AF influence on traffic routing | ZTE | imported from 3GU |
| S2‑183712 | QoS flow handling for Multi-Access PDU session | ZTE | imported from 3GU |
| S2‑183713 | Architecture requirement on dual registration and dual radio | ZTE | imported from 3GU |
| S2‑183714 | New Key Issue on Traffic Routing decision between E-UTRA and NR | ZTE | imported from 3GU |
| S2‑183715 | Update solution 6 of User Privacy Setting send via AMF | CATT | imported from 3GU |
| S2‑183716 | Handling of very large UE radio capabilities for the anticipated EN-DC UEs | Vodafone | imported from 3GU |
| S2‑183717 | New Key Issue: Extend Service Concept into User Plane | CATT | imported from 3GU |
| S2‑183718 | New KI #X: LCS support in Interworking Scenarios | CATT | imported from 3GU |
| S2‑183719 | New KI #X : Distribution Positioning Assistance Information | CATT | imported from 3GU |
| S2‑183720 | New Solution for KI#4 : User Privacy Setting send via LMF | CATT | imported from 3GU |
| S2‑183721 | 5GMBS Study Item proposal | Huawei, HiSilicon | imported from 3GU |
| S2‑183722 | Considerations on UE-specific information for UE differentiation for LSin S2-183095/R2-1803821 | Huawei, HiSilicon | imported from 3GU |
| S2‑183723 | Additional parameters for NB-IoT UE Uu operation optimisation | Huawei, HiSilicon | imported from 3GU |
| S2‑183724 | Additional parameters for NB-IoT UE Uu operation optimisation | Huawei, HiSilicon | imported from 3GU |
| S2‑183725 | Solution for Key Issue #4: MICO Mode Management for Expected Application Behaviour | Huawei, HiSilicon | imported from 3GU |
| S2‑183726 | Support QoS Differentiation for Unstructured PDU Session | Huawei, HiSilicon | imported from 3GU |
| S2‑183727 | Solution for Key Issue on Expected UE Behaviour | Huawei, HiSilicon, Convida, InterDigital, Samsung | imported from 3GU |
| S2‑183728 | Enhanced MICO mode for power saving function | Huawei, HiSilicon | imported from 3GU |
| S2‑183729 | Packet Aggregation for Small Data Delivery | Huawei, HiSilicon | imported from 3GU |
| S2‑183730 | Extended buffering solution in 5GS | Huawei, HiSilicon | imported from 3GU |
| S2‑183731 | Key issue on supporting CIoT UE access multiple Afs | Huawei, HiSilicon | imported from 3GU |
| S2‑183732 | Addressing open issues of solution 1 for infrequent small data transfer | Huawei, HiSilicon | imported from 3GU |
| S2‑183733 | NEF based infrequent small data transfer via NAS-SM | Huawei, HiSilicon | imported from 3GU |
| S2‑183734 | Solution for KI7: Reuse of EPS Overload Control Mechanims | Huawei, HiSilicon | imported from 3GU |
| S2‑183735 | Clarification on Key Issue: Network Slicing for eV2X | Huawei, HiSilicon | imported from 3GU |
| S2‑183736 | Solution for KI#8: NEF Selection for Mobility Support | Huawei, HiSilicon | imported from 3GU |
| S2‑183737 | Efficient Service Provisioning to UE for eV2X communications over PC5 and Uu reference point | Huawei, HiSilicon | imported from 3GU |
| S2‑183738 | Solution for eV2X QoS Support Key Issue: AF function impact on QoS | Huawei, HiSilicon | imported from 3GU |
| S2‑183739 | Support for MEC topology exposure for efficient DNAI selection | Huawei, HiSilicon | imported from 3GU |
| S2‑183740 | Network-controlled QoS for side link communication | Huawei, HiSilicon | imported from 3GU |
| S2‑183741 | Enhance Functionalities of NEF | Huawei, HiSilicon | imported from 3GU |
| S2‑183742 | 5G eV2X architecture proposal | Huawei, HiSilicon | imported from 3GU |
| S2‑183743 | Update to solution 8 – Routing media traffic via different 5GC network slices | Motorola Mobility, Lenovo | imported from 3GU |
| S2‑183744 | Infrequent Small Data Transmission: Using Resume and Suspend procedure | Samsung, SK Telecom | imported from 3GU |
| S2‑183745 | S-NSSAI check for activation of UP connection of PDU Session | CATT | imported from 3GU |
| S2‑183746 | Update to Key Issue #2 – Cell selection in case UE supports multiple V2X applications each operating on different PC5 RAT or carrier frequency | Motorola Mobility, Lenovo | imported from 3GU |
| S2‑183747 | S-NSSAI check in Network Triggered Service Request | CATT | imported from 3GU |
| S2‑183748 | APN Rate Control after PDN connection release/re-establishment | Huawei, HiSilicon | imported from 3GU |
| S2‑183749 | APN Rate Control after PDN connection release/re-establishment | Huawei, HiSilicon | imported from 3GU |
| S2‑183750 | APN Rate Control after PDN connection release/re-establishment | Huawei, HiSilicon | imported from 3GU |
| S2‑183751 | Architectural Assumptions and Requirement | China Telecom Corporation Ltd. | imported from 3GU |
| S2‑183752 | Correcting Registration Request parameters for EPS to 5GS Idle mode mobility with N26 | Qualcomm Incorporated | imported from 3GU |
| S2‑183753 | Support of isolated slice usage in the UE | Huawei, HiSilicon | imported from 3GU |
| S2‑183754 | New Key Issue: Identify scenarios when Network Slices cannot coexist within a single PLMN | Interdigital Asia LLC | imported from 3GU |
| S2‑183755 | Correction to the UE Policy section 6.1.2.2.1 | NEC | imported from 3GU |
| S2‑183756 | The interaction between PCF and AF | Huawei, HiSilicon | imported from 3GU |
| S2‑183757 | Correction to User Plane Security Enforcement | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183758 | Correction to handover procedures | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183759 | Location information as part of UPF Provisioning Information | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183760 | Corrections on namings of SMF Service Operations | Samsung | imported from 3GU |
| S2‑183761 | Corrections to the selective deactivation of UP connection | Motorola Mobility, Lenovo | imported from 3GU |
| S2‑183762 | Alignment on V-PCF behaviour to handle UE policy | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183763 | Discussion on Traffic Logical Status Awareness | China Telecom | imported from 3GU |
| S2‑183764 | Session handling for interworking without N26 | LG Electronics | imported from 3GU |
| S2‑183765 | Solution for Key Issue 5: AF Influence | NTT DOCOMO, | imported from 3GU |
| S2‑183766 | Session handling for interworking without N26 | LG Electronics | imported from 3GU |
| S2‑183767 | Study on Traffic Logical Status Awareness | China Telecom | imported from 3GU |
| S2‑183768 | Future proofing UE Radio Capability handling | Vodafone | imported from 3GU |
| S2‑183769 | Summary of 6-bit QFI discussions and proposed way forward | Samsung | imported from 3GU |
| S2‑183770 | Solution for key issue 3: Network Slicing and IMS | ZTE | imported from 3GU |
| S2‑183771 | Solution for key issue 7: How can IMS utilize services provided by Npcf | ZTE | imported from 3GU |
| S2‑183772 | Clarification on the enabling SRVCC during 5GS to EPS connected mode mobility | ZTE | imported from 3GU |
| S2‑183773 | Discussion and proposal on the Emergency service Fallback indicator per RAT | ZTE | imported from 3GU |
| S2‑183774 | Clarification on the Emergency service fallback indicator | ZTE | imported from 3GU |
| S2‑183775 | Clarification on the Emergency service fallback indicator | ZTE | imported from 3GU |
| S2‑183776 | Clarification on the CN control plane information for mobility from 5G to 4G with N26 | ZTE | imported from 3GU |
| S2‑183777 | Clarification on the EBI assignment, PDU session ID list in Registration and PDU session correlation. | ZTE | imported from 3GU |
| S2‑183778 | Mofification on SMF registration afer EPS to 5GS mobility | ZTE | imported from 3GU |
| S2‑183779 | Proposal on the EPS Qos parameters on N7 | ZTE | imported from 3GU |
| S2‑183780 | Solution on reusing the mechanism in EPS SRVCC to enable the 5G SRVCC | ZTE, Huawei, Qualcomm Incorporated | imported from 3GU |
| S2‑183781 | Discussion and proposal on indirect vs direct interface architecture | ZTE | imported from 3GU |
| S2‑183782 | Solution on the returning to EPS or 5GS after 5G SRVCC | ZTE | imported from 3GU |
| S2‑183783 | Clarifications required resulting from 6-bit QFI limit | Samsung | imported from 3GU |
| S2‑183784 | EV2X architecture reference model | Samsung, SK Telecom | imported from 3GU |
| S2‑183785 | Solution to Key Issue #2 - Cell selection when UE supports multiple V2X applications | Motorola Mobility, Lenovo | imported from 3GU |
| S2‑183786 | PC5 RAT selection for a V2X application | Samsung | imported from 3GU |
| S2‑183787 | Summary of offline discussions on INOBEAR | Samsung | imported from 3GU |
| S2‑183788 | Network Slicing for eV2X services | Samsung, SK Telecom | imported from 3GU |
| S2‑183789 | On the optionality of the INACTIVE state and CN impact | Samsung | imported from 3GU |
| S2‑183790 | NIDD service activation between NF and NEF | Samsung, SK Telecom | imported from 3GU |
| S2‑183791 | Missing 'redirection' to E-UTRA connected to 5GC | Intel | imported from 3GU |
| S2‑183792 | INOBEAR assumptions, key issues and way forward | Rapporteur (Samsung) | imported from 3GU |
| S2‑183793 | Subsuming 'handover attach' under UE MM Core Network Capability in the Registration procedure | Intel | imported from 3GU |
| S2‑183794 | [DRAFT] Reply LS on optimisation of UE capability signalling | Intel | imported from 3GU |
| S2‑183795 | Correction of security aspects in Registration and Service Request procedures | Huawei, Hisilicon | imported from 3GU |
| S2‑183796 | Discussion on Initial Message Protection | Huawei, Hisilicon | imported from 3GU |
| S2‑183797 | [DRAFT] Reply LS on Initial Message Protection | Huawei, Hisilicon | imported from 3GU |
| S2‑183798 | Correction to Nnwdaf_EventsSubscription_Notify (related to nw slice) | KDDI, ETRI, Oracle | imported from 3GU |
| S2‑183799 | Enhanced Power Saving Mode | OPPO | imported from 3GU |
| S2‑183800 | Updating Key Issue #8: Support of edge computing in mobility case | China Mobile | imported from 3GU |
| S2‑183801 | Subscription based information for Aerial UEs | Lenovo, Motorola Mobility | imported from 3GU |
| S2‑183802 | Update to the impacts and evaluation for Solution 3 'PCRF initiated S/PGW-U change based on detection of applications requiring low latency' | Vodafone | imported from 3GU |
| S2‑183803 | Update to the impacts and evaluation for Solution 1 'make-before-break PDN connection mobility initiated by MME' | Vodafone | imported from 3GU |
| S2‑183804 | Interim conclusion proposal | Intel | imported from 3GU |
| S2‑183805 | Subscription based information for Aerial UEs | Lenovo, Motorola Mobility | imported from 3GU |
| S2‑183806 | Tunnelling mechanism support indirect data forwarding between UPF and gNB for intra-system handover | Samsung Electronics | imported from 3GU |
| S2‑183807 | Clarification on Domain Selection for Emergency Service | OPPO | imported from 3GU |
| S2‑183808 | Solution for supporting LCS via non-3GPP access | Lenovo, Motorola Mobility | imported from 3GU |
| S2‑183809 | UE behavior clarification for Emergency Service | OPPO | imported from 3GU |
| S2‑183810 | Clarification on Nbsf_Management_Deregister service operation | China Mobile | imported from 3GU |
| S2‑183811 | Clarification on Nnwdaf_Analytics_Info service | China Mobile | imported from 3GU |
| S2‑183812 | Correction to indirect forwarding at intra 5GS N2 HO | Ericsson | imported from 3GU |
| S2‑183813 | Correction to forwarding at EPS to 5GS HO | Ericsson | imported from 3GU |
| S2‑183814 | Slice specific congestion handling | Ericsson | imported from 3GU |
| S2‑183815 | Solution for Key Issue 3: Optimization based on paging failure prediction from NWDAF | Lenovo, Motorola Mobility | imported from 3GU |
| S2‑183816 | User Plane Integrity Protection setting based UE capability | OPPO | imported from 3GU |
| S2‑183817 | MME request for UE Radio Capabilities | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183818 | New solution: Addition of SGW-U as uplink classifier instead of relocating S/PGW-U | Vodafone | imported from 3GU |
| S2‑183819 | AMF condition to send RRC Inactive Assistance Information | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183820 | TR 23.724: ConnectionLess (CL) data solution | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183821 | Local deactivation of MICO mode | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183822 | Local deactivation of MICO mode | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183823 | New Key Issue: Extend Service Concept into User Plane | CATT, China Mobile | imported from 3GU |
| S2‑183824 | Use cases introduction and guidelines | ORANGE | imported from 3GU |
| S2‑183825 | [DRAFT] Reply LS on Handling of end marker packets | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183826 | Draft Skeleton for TR 23.736 'Study on enhancement of systems using EPS for Ultra Reliability and Availability using commodity equipment' | Vodafone | imported from 3GU |
| S2‑183827 | PCC rules modification when UE is suspended | Huawei, Hisilicon | imported from 3GU |
| S2‑183828 | Clarification of Use Case 8 | ORANGE | imported from 3GU |
| S2‑183829 | Clarification of high priority access | KPN N.V. | imported from 3GU |
| S2‑183830 | Scope of FS_EPS_URACE TR 23.736 | Vodafone | imported from 3GU |
| S2‑183831 | Architectural assumptions for SRVCC handover to 3G | Motorola Mobility, Lenovo | imported from 3GU |
| S2‑183832 | ETSUN solution to key issue 5 | NEC | imported from 3GU |
| S2‑183833 | Dual registration interworking procedure | Samsung | imported from 3GU |
| S2‑183834 | Solution for SRVCC handover to 3G | Motorola Mobility, Lenovo | imported from 3GU |
| S2‑183835 | UE support for dual registration | Samsung | imported from 3GU |
| S2‑183836 | Indirect data forwarding for SRM interworking | Samsung | imported from 3GU |
| S2‑183837 | New use case: Prevention of various security attacks | ORANGE | imported from 3GU |
| S2‑183838 | AAI Key Issues | Samsung | imported from 3GU |
| S2‑183839 | AAI Architecture | Samsung | imported from 3GU |
| S2‑183840 | LS from ETSI TC CYBER: LS on inclusion of Middlebox Security Protocol profile option | ETSI TC CYBER | imported from 3GU |
| S2‑183841 | Dual registration interworking procedure | Samsung | imported from 3GU |
| S2‑183842 | New Key Issue: Isolation aspects in slicing interworking | NTT DOCOMO | imported from 3GU |
| S2‑183843 | New Key Issue for Data Collection Framework (additional content) | ORANGE | imported from 3GU |
| S2‑183844 | Adding a new use case on predictive network quality | China Mobile | imported from 3GU |
| S2‑183845 | Support for Mobility Attach indication | NTT DOCOMO | imported from 3GU |
| S2‑183846 | EBI allocation and slicing interworking with EPS | NTT DOCOMO | imported from 3GU |
| S2‑183847 | Dual Connectivity Support for Network Slicing | NTT DOCOMO | imported from 3GU |
| S2‑183848 | Dual connectivity support for network slices | NTT DOCOMO | imported from 3GU |
| S2‑183849 | [DRAFT] Reply LS on on N3GPP TAI | Nokia Belgium | imported from 3GU |
| S2‑183850 | Clarification on Mobility for UEs in single-registration mode | ORANGE | imported from 3GU |
| S2‑183851 | Tunnel Info reservation at the UPF for sessions interworked with EPC | NTT DOCOMO | imported from 3GU |
| S2‑183852 | SMF registration for PDN connections, discussion | NTT DOCOMO | imported from 3GU |
| S2‑183853 | SMF registration for PDN Connections | NTT DOCOMO | imported from 3GU |
| S2‑183854 | Support Ethernet PDU Session binding in BSF service | China Mobile | imported from 3GU |
| S2‑183855 | Solution proposal 'Indirect Service Interaction' to address key issue 'Improvements to service framework related aspects' | Deutsche Telekom | imported from 3GU |
| S2‑183856 | Update to Support of edge computing Key Issue #8 | InterDigital Inc. | imported from 3GU |
| S2‑183857 | Requirements and Key Issues related to the use of Duplicated Networks | Vodafone | imported from 3GU |
| S2‑183858 | 5GS V2X Architecture | InterDigital Inc. | imported from 3GU |
| S2‑183859 | Removal of leftover sentence regarding MTC-IWF architecture | ORANGE | imported from 3GU |
| S2‑183860 | Clarification to the NRF Roaming architecture | DeutscheTelekom | imported from 3GU |
| S2‑183861 | Slicing information and RFSP | Ericsson | imported from 3GU |
| S2‑183862 | LS from SA WG3LI: LS on SoR mechanism | SA WG3LI | imported from 3GU |
| S2‑183863 | LS from SA WG5: LS Reply to SA2 on Differentiation of LTE-M (eMTC) traffic from other LTE data traffic | SA WG5 | imported from 3GU |
| S2‑183864 | LS from SA WG5: LS reply from SA WG5 to SA WG2 on 5G Specification of PSy | SA WG5 | imported from 3GU |
| S2‑183865 | LS from SA WG5: LS on 5G Trace | SA WG5 | imported from 3GU |
| S2‑183866 | LS from SA WG4: LS on CAPIF4xMB | SA WG4 | imported from 3GU |
| S2‑183867 | LS from SA WG4: LS on FS_eVoLP | SA WG4 | imported from 3GU |
| S2‑183868 | LS from SA WG4: Reply LS on FEC and ROHC for mission critical services over MBMS | SA WG4 | imported from 3GU |
| S2‑183869 | New Study on Architecture aspects of using satellite access in 5G | Thales, TNO, CNES, Avanti, CCTC, ESA, Fraunhofer IIS, Hughes Network Systems, Nomor Research, Catapult, IAESI, SES, ICS, VTT, Alibaba | imported from 3GU |
| S2‑183870 | New SID on supporting Flexible Local Area Data Network | LG Electronics, SK Telecom, LG Uplus, KT Corp., Verizon UK LTD, Sprint, China Unicom, Telecom Italia, KPN, Samsung, ETRI, ITRI, Cisco, Oracle, Sony | imported from 3GU |
| S2‑183871 | Study on system architecture for next generation real time communication services | China Mobile, Deutsche Telekom, Verizon, China Telecom, Telefonica, China Unicom?, AT&T?, Huawei, ZTE, CATT, CATR | imported from 3GU |
| S2‑183872 | 5GMBS Study Item proposal | Huawei, HiSilicon | imported from 3GU |
| S2‑183873 | 5G eV2X architecture proposal | Huawei, HiSilicon | imported from 3GU |
| S2‑183874 | EV2X architecture reference model | Samsung, SK Telecom | imported from 3GU |
| S2‑183875 | Solutions for KI#5,KI#6 and KI#11 Service Authorisation | Ericsson | imported from 3GU |
| S2‑183876 | Solution for key issue #5 | Intel, LG Electronics | imported from 3GU |
| S2‑183877 | Efficient Service Provisioning to UE for eV2X communications over PC5 and Uu reference point | Huawei, HiSilicon | imported from 3GU |
| S2‑183878 | Solution to key issue#6 | LG Electronics | imported from 3GU |
| S2‑183879 | Network Slicing for eV2X services | Samsung, SK Telecom | imported from 3GU |
| S2‑183880 | Clarification on Key Issue: Network Slicing for eV2X | Huawei, HiSilicon | imported from 3GU |
| S2‑183881 | Solution to key issue#8 | LG Electronics, NTT DOCOMO | imported from 3GU |
| S2‑183882 | 5G eV2X architecture proposal | Huawei, HiSilicon, InterDigital | imported from 3GU |
| S2‑183883 | EV2X architecture reference model | Samsung, SK Telecom | imported from 3GU |
| S2‑183884 | Solution for key issue #5 | Intel, LG Electronics | imported from 3GU |
| S2‑183885 | Efficient Service Provisioning to UE for eV2X communications over PC5 and Uu reference point | Huawei, HiSilicon | imported from 3GU |
| S2‑183886 | Solution to key issue#6 | LG Electronics | imported from 3GU |
| S2‑183887 | Network Slicing for eV2X services | Samsung, SK Telecom | imported from 3GU |
| S2‑183888 | Solution to key issue#8 | LG Electronics, NTT DOCOMO | imported from 3GU |
| S2‑183889 | Clarification on Key Issue: Network Slicing for eV2X | Huawei, HiSilicon | imported from 3GU |
| S2‑183890 | Chairmans Notes of the meeting | SA WG2 Chairman (Huawei) | imported from 3GU |
| S2‑183891 | Chairmans Notes from Puneet Jain parallel sessions | SA WG2 Vice Chairman (Intel) | imported from 3GU |
| S2‑183892 | Chairmans Notes from Krisztian Kiss parallel sessions | SA WG2 Vice Chairman (Apple) | imported from 3GU |
| S2‑183893 | Chairmans Notes from LaeYoung Kim parallel sessions | Convenor (LG Electronics) | imported from 3GU |
| S2‑183894 | Chairmans Notes from Mirko Schramm parallel sessions | Convenor (Huawei) | imported from 3GU |
| S2‑183895 | Reserved for LaeYoungs parallel sessions | - | imported from 3GU |
| S2‑183896 | Reserved for LaeYoungs parallel sessions | - | imported from 3GU |
| S2‑183897 | Reserved for LaeYoungs parallel sessions | - | imported from 3GU |
| S2‑183898 | Reserved for LaeYoungs parallel sessions | - | imported from 3GU |
| S2‑183899 | Reserved for LaeYoungs parallel sessions | - | imported from 3GU |
| S2‑183900 | Reserved for LaeYoungs parallel sessions | - | imported from 3GU |
| S2‑183901 | Reserved for LaeYoungs parallel sessions | - | imported from 3GU |
| S2‑183902 | Reserved for LaeYoungs parallel sessions | - | imported from 3GU |
| S2‑183903 | Reserved for LaeYoungs parallel sessions | - | imported from 3GU |
| S2‑183904 | Reserved for LaeYoungs parallel sessions | - | imported from 3GU |
| S2‑183905 | Reserved for LaeYoungs parallel sessions | - | imported from 3GU |
| S2‑183906 | Reserved for LaeYoungs parallel sessions | - | imported from 3GU |
| S2‑183907 | Reserved for LaeYoungs parallel sessions | - | imported from 3GU |
| S2‑183908 | Reserved for LaeYoungs parallel sessions | - | imported from 3GU |
| S2‑183909 | Reserved for LaeYoungs parallel sessions | - | imported from 3GU |
| S2‑183910 | Reserved for LaeYoungs parallel sessions | - | imported from 3GU |
| S2‑183911 | Reserved for LaeYoungs parallel sessions | - | imported from 3GU |
| S2‑183912 | Reserved for LaeYoungs parallel sessions | - | imported from 3GU |
| S2‑183913 | Enhanced MICO mode for power saving function | Huawei, HiSilicon | imported from 3GU |
| S2‑183914 | TR 23.724: Enhanced MICO for power saving solution | Qualcomm Incorporated, Sony, Samsung, Convida Wireless LLC, BlackBerry UK Ltd | imported from 3GU |
| S2‑183915 | Enhanced Power Saving Mode | OPPO | imported from 3GU |
| S2‑183916 | Solution of High latency communication and Power Saving Function | Intel | imported from 3GU |
| S2‑183917 | PCR 23.724: eDRX | Ericsson | imported from 3GU |
| S2‑183918 | Solution proposal 'Adjustable periodic Registration Update' for UE power saving | LG Electronics, SK Telecom, LG Uplus | imported from 3GU |
| S2‑183919 | Solution for Key Issue #4: MICO Mode Management for Expected Application Behaviour | Huawei, HiSilicon | imported from 3GU |
| S2‑183920 | KI 3: Solution for High latency communication | Ericsson | imported from 3GU |
| S2‑183921 | Scope of FS_eNS TR 23.740 | Telecom Italia, ZTE | imported from 3GU |
| S2‑183922 | Skeleton of the TR 23.740 | Telecom Italia, ZTE | imported from 3GU |
| S2‑183923 | Key Issues considerations to support isolated and coexisted slices | ZTE, Telecom Italia, Oracle, China Telecom | imported from 3GU |
| S2‑183924 | Key Issue on Slice Interworking between 5GC and EPC | Qualcomm Incorporated | imported from 3GU |
| S2‑183925 | New Key Issue: Identify scenarios when Network Slices cannot coexist within a single PLMN | InterDigital Inc, ITRI | imported from 3GU |
| S2‑183926 | Support of isolated slice usage in the UE | Huawei, HiSilicon | imported from 3GU |
| S2‑183927 | TLTRI Assignment by the SCEF | Convida Wireless LLC, Huawei, Nokia | imported from 3GU |
| S2‑183928 | [DRAFT] Reply LS on Resource Identifiers for T8 | SA WG2 | imported from 3GU |
| S2‑183929 | Making the T8 Destination Address Mandatory for APIs that Create a Subscription | Convida Wireless LLC, Huawei | imported from 3GU |
| S2‑183930 | [DRAFT] Reply LS on T8 Destination Address | SA WG2 | imported from 3GU |
| S2‑183931 | Monitoring Event configuration removal for a group | Huawei, Hisilicon | imported from 3GU |
| S2‑183932 | Deletion of Network Parameter Configuration | Huawei, Hisilicon | imported from 3GU |
| S2‑183933 | Optional Duplidate Address Detection for V2X Communication over PC5 | Qualcomm Incorporated, LG Electronics, Intel | imported from 3GU |
| S2‑183934 | Optional Duplidate Address Detection for V2X Communication over PC5 | Qualcomm Incorporated, LG Electronics, Intel | imported from 3GU |
| S2‑183935 | Reliability for eV2X for LTE clarification | Ericsson, Qualcomm Inc., Oppo | imported from 3GU |
| S2‑183936 | [DRAFT] Reply LS on PC5 transmission mechanism selection | SA WG2 | imported from 3GU |
| S2‑183937 | Discussion on Architectural Assumptions | Ericsson | imported from 3GU |
| S2‑183938 | General Framework for 5G network automation | China Mobile | imported from 3GU |
| S2‑183939 | Use cases introduction and guidelines | ORANGE | imported from 3GU |
| S2‑183940 | NWDA-assisted load balancing/re-balancing of network function | KDDI | imported from 3GU |
| S2‑183941 | Use Case: NWDA-assisting E2E QoS Assurance | Huawei, HiSilicon | imported from 3GU |
| S2‑183942 | New use case: Prevention of various security attacks | ORANGE | imported from 3GU |
| S2‑183943 | Adding a new use case on predictive network quality | China Mobile | imported from 3GU |
| S2‑183944 | RFSP selection proposal for Key Issue 1 | China Mobile | imported from 3GU |
| S2‑183945 | Update on Key Issue Description | Huawei, HiSilicon, AT&T | imported from 3GU |
| S2‑183946 | New Key Issue for Data Collection Framework (additional content) | ORANGE | imported from 3GU |
| S2‑183947 | New key issue on NWDAF assisting traffic routing | Intel, AT&T | imported from 3GU |
| S2‑183948 | Key issue on performance improvement and supervision of mIoT terminals | China Mobile | imported from 3GU |
| S2‑183949 | Key Issue and Solution for Future Background Data Transfer | Huawei, HiSilicon | imported from 3GU |
| S2‑183950 | eLCS Drafting session report | Drafting group convenor | imported from 3GU |
| S2‑183951 | Solution5 Update: Privacy Check procedure W.R.T. LMF based architecture | vivo | imported from 3GU |
| S2‑183952 | New KI #X: LCS support in Interworking Scenarios | CATT | imported from 3GU |
| S2‑183953 | New KI #X : Distribution Positioning Assistance Information | CATT | imported from 3GU |
| S2‑183954 | Solution for position via user plane transmission | Huawei, HiSilicon | imported from 3GU |
| S2‑183955 | Solution for Slicing dependent location service | Huawei, HiSilicon | imported from 3GU |
| S2‑183956 | New Solution for KI#4 : User Privacy Setting send via LMF | CATT | imported from 3GU |
| S2‑183957 | TR 23.731: Update to Privacy Check with UE Privacy Setting | OTD | imported from 3GU |
| S2‑183958 | Update solution 6 of User Privacy Setting send via AMF | CATT | imported from 3GU |
| S2‑183959 | Solution for location service exposure | Huawei, HiSilicon | imported from 3GU |
| S2‑183960 | Solution for Location Service exposure | Ericsson | imported from 3GU |
| S2‑183961 | Solution for Location Service exposure to NG-RAN | Ericsson | imported from 3GU |
| S2‑183962 | Solution for supporting LCS via non-3GPP access | Lenovo, Motorola Mobility | imported from 3GU |
| S2‑183963 | Solution to new KI of supporting non-3GPP access | Huawei, HiSilicon | imported from 3GU |
| S2‑183964 | Enhancement to existing location service solution for commercial use cases | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183965 | LCS architecture enhancement addressing Key Issue #1 in TR 23.731 | Huawei, HiSilicon | imported from 3GU |
| S2‑183966 | Low Power Periodic and Triggered Location for the LMF Based Solution | Qualcomm Incorporated | imported from 3GU |
| S2‑183967 | Positioning procedures considering different LMF deployment scenarios | Huawei, HiSilicon | imported from 3GU |
| S2‑183968 | Reply LS on PC5 transmission mechanism selection | SA WG2 | imported from 3GU |
| S2‑183969 | Additional parameters for NB-IoT UE Uu operation optimisation | Huawei, HiSilicon | imported from 3GU |
| S2‑183970 | Additional parameters for NB-IoT UE Uu operation optimisation | Huawei, HiSilicon | imported from 3GU |
| S2‑183971 | Alignment with CT WG1 for handling of Connection Resume Requests at Service Gap | Ericsson | imported from 3GU |
| S2‑183972 | [DRAFT] Reply LS on service gap control with resume for non-supporting UE | Ericsson | imported from 3GU |
| S2‑183973 | Subscription for Aerial UE in 3GPP system | Ericsson, NTT DoCoMo, Qualcomm Incorporated, Intel | imported from 3GU |
| S2‑183974 | Handling of large UE radio capabilities at inter-RAT and SR-VCC handover | Vodafone | imported from 3GU |
| S2‑183975 | Radio efficient handling of large UE radio capabilities at inter-RAT and SRVCC handover | Vodafone | imported from 3GU |
| S2‑183976 | Handling of large UE radio capabilities at inter-RAT and SR-VCC handover | Vodafone | imported from 3GU |
| S2‑183977 | Handling of very large UE radio capabilities for the anticipated EN-DC UEs | Vodafone | imported from 3GU |
| S2‑183978 | Solution Key issue 3 (HLCom): Extended buffering at UPF of MT data for user plane | Qualcomm Incorporated | imported from 3GU |
| S2‑183979 | Extended buffering solution in 5GS | Huawei, HiSilicon | imported from 3GU |
| S2‑183980 | Solution for KI#6 - Management for Enhanced Coverage | Intel | imported from 3GU |
| S2‑183981 | Key Issue #9 Solution: SCEF+NEF Node | Convida Wireless LLC, AT&T | imported from 3GU |
| S2‑183982 | Solution for KI_ common north-bound APIs for EPC-5GC interworking | Huawei, Hisilicon | imported from 3GU |
| S2‑183983 | Solution for Key Issue on Expected UE Behaviour | Huawei, HiSilicon, Convida Wireless LLC, InterDigital, Samsung | imported from 3GU |
| S2‑183984 | Classification of external parameters to MM and SM parameters | Motorola Mobility, Lenovo | imported from 3GU |
| S2‑183985 | Solution for KI7: Reuse of EPS Overload Control Mechanims | Huawei, HiSilicon | imported from 3GU |
| S2‑183986 | Solution KI-14: QoS for Data over NAS | Qualcomm Incorporated | imported from 3GU |
| S2‑183987 | Support QoS Differentiation for Unstructured PDU Session | Huawei, HiSilicon | imported from 3GU |
| S2‑183988 | SMF assisted RAN information | Motorola Mobility, Lenovo | imported from 3GU |
| S2‑183989 | Infrequent Small Data Transmission: Using Resume and Suspend procedure | Samsung, SK Telecom | imported from 3GU |
| S2‑183990 | TR 23.724: ConnectionLess (CL) data solution | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183991 | TR 23.724: NIDD aspects for small data transfer via NAS-SM | Qualcomm Incorporated | imported from 3GU |
| S2‑183992 | NEF based infrequent small data transfer via NAS-SM | Huawei, HiSilicon | imported from 3GU |
| S2‑183993 | NIDD service activation between NF and NEF | Samsung, SK Telecom | imported from 3GU |
| S2‑183994 | TR 23.724: Addressing open issues for Solution 1 | Qualcomm Incorporated | imported from 3GU |
| S2‑183995 | Discovery and Topology Hiding | Ericsson | imported from 3GU |
| S2‑183996 | NF Registration via the NRF | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑183997 | NF Discovery via the NRF | Nokia, Nokia Shanghai Bell, Verizon, AT&T | imported from 3GU |
| S2‑183998 | Subscription status notification for Event Exposure service | Huawei, Hisilicon | imported from 3GU |
| S2‑183999 | Subscription status notification for Event Exposure service | Huawei, Hisilicon | imported from 3GU |
| S2‑184000 | Correction of Provision parameters flow | Ericsson | imported from 3GU |
| S2‑184001 | Update UDR DM service for data subscription | China Mobile | imported from 3GU |
| S2‑184002 | TS23.502 Clarification on AMF Subscription Correlation ID | ZTE | imported from 3GU |
| S2‑184003 | TS23.502 Additional DataSet and Datakey | ZTE | imported from 3GU |
| S2‑184004 | TS23.502 Nnef_TrafficInfluence service | ZTE | imported from 3GU |
| S2‑184005 | Clarifications on Nudr interactions between PCF and UDR for Application Data | Ericsson | imported from 3GU |
| S2‑184006 | Clarifications on Nudr interactions between PCF and UDR | Ericsson | imported from 3GU |
| S2‑184007 | [DRAFT] Reply LS on Nudr Structured Data for Exposure | SA WG2 | imported from 3GU |
| S2‑184008 | Trust Model and Architecture Assumption | Intel | imported from 3GU |
| S2‑184009 | Solution for UE assisted enrypted traffic detection | OPPO, China Unicom | imported from 3GU |
| S2‑184010 | Solution to Key Issue #1 | Ericsson, China Unicom | imported from 3GU |
| S2‑184011 | Encrypted traffic detection and verification | Huawei, Hisilicon | imported from 3GU |
| S2‑184012 | Solution for NW triggered enrypted traffic detection | OPPO | imported from 3GU |
| S2‑184013 | Alternative UE-assisted ENTRADE solution | Qualcomm Incorporated | imported from 3GU |
| S2‑184014 | Update of UE-Assisted Solution | Motorola Mobility, Lenovo | imported from 3GU |
| S2‑184015 | Updates of Solution#2 for Resolving Editor Notes | Intel | imported from 3GU |
| S2‑184016 | [DRAFT] Reply LS on INOBEAR | SA WG2 | imported from 3GU |
| S2‑184017 | INOBEAR assumptions, key issues and way forward | Rapporteur (Samsung) | imported from 3GU |
| S2‑184018 | UE Capability for supporting 15 EPS bearers | Qualcomm Incorporated, Samsung, ZTE | imported from 3GU |
| S2‑184019 | Network support for increased number of bearers | Qualcomm Incorporated, Samsung, ZTE | imported from 3GU |
| S2‑184020 | Clarification of using more than eight EPS bearers with EPS | Ericsson | imported from 3GU |
| S2‑184021 | TR 23.715: Update to Architectural Assumptions for PARLOS | OTD | imported from 3GU |
| S2‑184022 | Correction on Architectural assumption for emergency service | Samsung | imported from 3GU |
| S2‑184023 | Solution for RLOS attach procedure | NEC Corporation | imported from 3GU |
| S2‑184024 | Solution to Key issue #EPC-3 | Ericsson | imported from 3GU |
| S2‑184025 | Solution to Key issue IMS-1, IMS-2, and IMS-3 | Ericsson | imported from 3GU |
| S2‑184026 | Solution to Key issue #IMS-4: Support of emergency services by UEs attached for RLOS | Ericsson | imported from 3GU |
| S2‑184027 | Solution: IMS procedures for RLOS | Nokia, Nokia Shanghai Bell, Verizon | imported from 3GU |
| S2‑184028 | PLMN selection and radio access for RLOS | Motorola Mobility, Lenovo | imported from 3GU |
| S2‑184029 | Preferred PLMN list for RLOS | Qualcomm Incorporated | imported from 3GU |
| S2‑184030 | RLOS service for the attached UE in limited state | Samsung | imported from 3GU |
| S2‑184031 | Removing some ENs and update in Solution #4 | Ericsson | imported from 3GU |
| S2‑184032 | How to complete RLOS service | Samsung | imported from 3GU |
| S2‑184033 | Solution for position via user plane transmission | Huawei, HiSilicon | imported from 3GU |
| S2‑184034 | Solution for location service exposure | Huawei, HiSilicon | imported from 3GU |
| S2‑184035 | Solution for Location Service exposure to NG-RAN | Ericsson | imported from 3GU |
| S2‑184036 | LCS architecture enhancement addressing Key Issue #1 in TR 23.731 | Huawei, HiSilicon | imported from 3GU |
| S2‑184037 | Enhanced MICO mode for power saving function | Huawei, HiSilicon | imported from 3GU |
| S2‑184038 | Solution of High latency communication and Power Saving Function | Intel | imported from 3GU |
| S2‑184039 | PCR 23.724: eDRX | Ericsson | imported from 3GU |
| S2‑184040 | Solution proposal 'Adjustable periodic Registration Update' for UE power saving | LG Electronics, SK Telecom, LG Uplus | imported from 3GU |
| S2‑184041 | Solution for Key Issue #4: MICO Mode Management for Expected Application Behaviour | Huawei, HiSilicon | imported from 3GU |
| S2‑184042 | KI 3: Solution for High latency communication | Ericsson | imported from 3GU |
| S2‑184043 | Solution Key issue 3 (HLCom): Extended buffering at UPF of MT data for user plane | Qualcomm Incorporated | imported from 3GU |
| S2‑184044 | Support QoS Differentiation for Unstructured PDU Session | Huawei, HiSilicon | imported from 3GU |
| S2‑184045 | New Solution for KI#4 : User Privacy Setting send via LMF | CATT | imported from 3GU |
| S2‑184046 | Update solution 6 of User Privacy Setting send via AMF | CATT | imported from 3GU |
| S2‑184047 | Classification of external parameters to MM and SM parameters | Motorola Mobility, Lenovo | imported from 3GU |
| S2‑184048 | Addition of Broadcast of Assistance Data for E-UTRAN | Qualcomm Incorporated | imported from 3GU |
| S2‑184049 | Removal of leftover sentence regarding MTC-IWF architecture | ORANGE | imported from 3GU |
| S2‑184050 | UE Capability for supporting 15 EPS bearers | Qualcomm Incorporated, Samsung, ZTE | imported from 3GU |
| S2‑184051 | Network support for increased number of bearers | Qualcomm Incorporated, Samsung, ZTE | imported from 3GU |
| S2‑184052 | Clarification of using more than eight EPS bearers with EPS | Ericsson | imported from 3GU |
| S2‑184053 | [DRAFT] Reply LS on INOBEAR | SA WG2 | imported from 3GU |
| S2‑184054 | Reply LS on Deletion of Network Parameter Configuration | SA WG2 | imported from 3GU |
| S2‑184055 | Monitoring Event configuration removal for a group | Huawei, Hisilicon | imported from 3GU |
| S2‑184056 | Deletion of Network Parameter Configuration | Huawei, Hisilicon | imported from 3GU |
| S2‑184057 | Monitoring Event configuration removal for a group | Huawei, Hisilicon | imported from 3GU |
| S2‑184058 | Subscription for Aerial UE in 3GPP system | Ericsson, NTT DoCoMo, Qualcomm Incorporated, Intel | imported from 3GU |
| S2‑184059 | Reply LS on Deletion of Network Parameter Configuration | SA WG2 | imported from 3GU |
| S2‑184060 | Radio efficient handling of large UE radio capabilities at inter-RAT and SRVCC handover | Vodafone | imported from 3GU |
| S2‑184061 | [DRAT] LS on Aspects of handling large UE UE radio capabilities in EPC | SA WG2 | imported from 3GU |
| S2‑184062 | Handling of very large UE radio capabilities for the anticipated EN-DC UEs | Vodafone | imported from 3GU |
| S2‑184063 | Mapped parameters in case of No N26 | Qualcomm Incorporated | imported from 3GU |
| S2‑184064 | [DRAFT] Reply LS on handling of EPS bearer context and PDU session context for interworking without N26 | Qualcomm Incorporated | imported from 3GU |
| S2‑184065 | Clarification of traffic steering in UPF + PGW-U | KDDI | imported from 3GU |
| S2‑184066 | Proposal on the EPS Qos parameters on N7 | ZTE | imported from 3GU |
| S2‑184067 | [DRAFT] Reply LS on 5G-GUTI type | Qualcomm Incorporated | imported from 3GU |
| S2‑184068 | P-GW-C+SMF Registration in the UDM for the purpose of EPS interworking | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑184069 | Mofification on SMF registration afer EPS to 5GS mobility | ZTE | imported from 3GU |
| S2‑184070 | EPS to 5GS Mobility - Handling PDN connections that are not subject to service continuity | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑184071 | EPS Interworking Principles - SR mode with N26 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑184072 | Context retrieval for the purpose of EPS interworking | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑184073 | IPv6 Multi-homing capability report | Spreadtrum | imported from 3GU |
| S2‑184074 | Clarification on the EBI assignment, PDU session ID list in Registration and PDU session correlation. | ZTE | imported from 3GU |
| S2‑184075 | Indirect data forwarding for SRM interworking | Samsung | imported from 3GU |
| S2‑184076 | Cleanups on the support of session binding for Ethernet PDU session Type | Nokia, Nokia Shanghai Bell, China Mobile | imported from 3GU |
| S2‑184077 | Network slicing information as the service input parameter of BSF service operations | Nokia, Nokia Shanghai Bell, China Mobile | imported from 3GU |
| S2‑184078 | Network slicing information for binding the AF request to the relevant PCF | Nokia, Nokia Shanghai Bell, China Mobile | imported from 3GU |
| S2‑184079 | Controlled support of (AF) session binding for Ethernet PDU Session Type | Nokia, Nokia Shanghai Bell, China Mobile | imported from 3GU |
| S2‑184080 | TS23.503 Clarification on BSF | ZTE | imported from 3GU |
| S2‑184081 | Clarification on Nbsf_Management_Deregister service operation | China Mobile | imported from 3GU |
| S2‑184082 | TS 23.501 Clarification on Application data | Huawei, HiSilicon, China Mobile | imported from 3GU |
| S2‑184083 | Update for providing policy requirements to multiple UEs | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑184084 | NEF and UDR in LBO architecture for AF influence on traffic routing | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑184085 | [DRAFT] LS reply to LS on Questions on Events related to Sevice Data Flows in the Nsmf_EventExposure service | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑184086 | TS23.502 Remove access independent event trigger in Nsmf_EventExposure Service | ZTE | imported from 3GU |
| S2‑184087 | Service Area of SMF | Huawei, Hisilicon | imported from 3GU |
| S2‑184088 | Updates to solution 1 | Ericsson | imported from 3GU |
| S2‑184089 | Updates to solution 2 for SMF selection | Ericsson | imported from 3GU |
| S2‑184090 | Updates to Solution #5 | Cisco Systems | imported from 3GU |
| S2‑184091 | Inter I-SMF mobility | Huawei, Hisilicon | imported from 3GU |
| S2‑184092 | ULCL relocation and release | Huawei, Hisilicon | imported from 3GU |
| S2‑184093 | Update to Solution #9 to resolve open EN | T-Mobile USA INC | imported from 3GU |
| S2‑184094 | Enhancement for IP allocation solution | Huawei, HiSilicon | imported from 3GU |
| S2‑184095 | Updates to solution 11 | Ericsson | imported from 3GU |
| S2‑184096 | Resource management of UPF shared by multiple SMFs during UPF relocation | Huawei, HiSilicon | imported from 3GU |
| S2‑184097 | Solution for AF influence on traffic routing | ZTE | imported from 3GU |
| S2‑184098 | Solution for Key Issue 5: AF Influence | NTT DOCOMO, | imported from 3GU |
| S2‑184099 | ETSUN solution to key issue 5 | NEC | imported from 3GU |
| S2‑184100 | Correction of non-3GPP to E-UTRAN handovers | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑184101 | Correction of non-3GPP to E-UTRAN handovers | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑184102 | Clarification on N3GPP TAI | Samsung | imported from 3GU |
| S2‑184103 | [DRAFT] LS on N3GPP TAI | MediaTek Inc. | imported from 3GU |
| S2‑184104 | Clarification for Network Requested PDU Session Release via Untrusted non-3GPP access | Huawei, Hisilicon | imported from 3GU |
| S2‑184105 | Determination of ePDG vs N3IWF function is a combined ePDG-N3IWF node | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑184106 | Removal of editor's notes in clause 4.12 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑184107 | Clarification on notification message | LG Electronics | imported from 3GU |
| S2‑184108 | 3GPP PS Data Off Clarification | Intel, Telecom Italia, Deutsche Telekom, Nokia, Nokia Shanghai Bell, Huawei, HiSilicon, Qualcomm, ZTE, MediaTek Inc., CMCC, China Unicom, OPPO, CATT | imported from 3GU |
| S2‑184109 | 3GPP PS Data Off Clarification | Intel, Telecom Italia, Deutsche Telekom, Nokia, Nokia Shanghai Bell, Huawei, HiSilicon, Qualcomm, ZTE, MediaTek Inc., CMCC, China Unicom, OPPO, CATT | imported from 3GU |
| S2‑184110 | 3GPP PS Data Off Clarification | Intel, Telecom Italia, Deutsche Telekom, Nokia, Nokia Shanghai Bell, Huawei, HiSilicon, Qualcomm, ZTE, MediaTek Inc., CMCC, China Unicom, OPPO, CATT | imported from 3GU |
| S2‑184111 | 3GPP PS Data Off Clarification | Intel, Telecom Italia, Deutsche Telekom, Nokia, Nokia Shanghai Bell, Huawei, HiSilicon, Qualcomm, ZTE, MediaTek Inc., CMCC, China Unicom, OPPO, CATT | imported from 3GU |
| S2‑184112 | 3GPP PS Data Off Clarification | Intel, Telecom Italia, Deutsche Telekom, Nokia, Nokia Shanghai Bell, Huawei, HiSilicon, Qualcomm, ZTE, MediaTek Inc., CMCC, China Unicom, OPPO, CATT | imported from 3GU |
| S2‑184113 | Update of the Key issue 5: Multi-access PDU sessions (Un-trusted access) | Huawei, Hisilicon | imported from 3GU |
| S2‑184114 | Architectural Updates for ATSSS Solution 1 | BT Plc, Broadcom | imported from 3GU |
| S2‑184115 | New solution: MPTCP proxy architecture | Apple, Inc. | imported from 3GU |
| S2‑184116 | Architecture framework with ATSSS rules and UP Access Agnostic Reporting Control Protocol | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑184117 | Solution 2 Update: NW-Requested Establishment of MA-PDU session | Motorola Mobility, Lenovo | imported from 3GU |
| S2‑184118 | ATSSS Solution - Update of Solution 2 | LG Electronics, Motorola Mobility, Lenovo | imported from 3GU |
| S2‑184119 | MA-PDU session release operations | ITRI | imported from 3GU |
| S2‑184120 | Traffic steering with ATSSS Policy | Motorola Mobility, Lenovo | imported from 3GU |
| S2‑184121 | ATSSS Rule definition and TFCP procedure update | Huawei, Hisilicon | imported from 3GU |
| S2‑184122 | Solution for KI on Discovery of Network Functions | Huawei, Hisilicon | imported from 3GU |
| S2‑184123 | Solutions for common IMS network through multiple 5GC network slices | Huawei, Hisilicon | imported from 3GU |
| S2‑184124 | Update to solution 8 - Routing media traffic via different 5GC network slices | Motorola Mobility, Lenovo | imported from 3GU |
| S2‑184125 | Solution for key issue 3: Network Slicing and IMS | ZTE | imported from 3GU |
| S2‑184126 | Solution X for key issue 5 : Enabling SBA-based Cx | Ericsson | imported from 3GU |
| S2‑184127 | Consideration on SBA-based Cx | Huawei, Hisilicon | imported from 3GU |
| S2‑184128 | Solution X for key issue 6 : Enabling SBA-based Sh | Ericsson | imported from 3GU |
| S2‑184129 | Solution for utilizing services provided by 5GC | Huawei, Hisilicon | imported from 3GU |
| S2‑184130 | FS_5G-SRVCC - Scope of TR 23.756 | China Unicom | imported from 3GU |
| S2‑184131 | Architectural assumptions and requirements of 5G SRVCC | China Unicom | imported from 3GU |
| S2‑184132 | New key issue on enabling SRVCC from NG-RAN to UTRAN CS | Intel, Huawei, HiSilicon, ZTE, China Unicom | imported from 3GU |
| S2‑184133 | New key issue on SRVCC HO Procedure from NG-RAN to UTRAN CS | Intel, Huawei, HiSilicon, ZTE, China Unicom | imported from 3GU |
| S2‑184134 | New key issue on returning UE to NG-RAN from UTRAN CS | Intel, Huawei, HiSilicon, ZTE, China Unicom | imported from 3GU |
| S2‑184135 | [DRAFT] Return from UTRAN to NG-RAN for SRVCC from 5GS to UTRAN | SA WG2 | imported from 3GU |
| S2‑184136 | Key Issue of Analysis PS HO support in SRVCC from 5G to 3G | Qualcomm Incorporated | imported from 3GU |
| S2‑184137 | SRVCC Architecture from NG-RAN to UTRAN CS | Intel, Huawei, Hisilicon | imported from 3GU |
| S2‑184138 | Solution on reusing the mechanism in EPS SRVCC to enable the 5G SRVCC | ZTE, Huawei, Qualcomm Incorporated | imported from 3GU |
| S2‑184139 | EBI allocation and slicing interworking with EPS | NTT DOCOMO | imported from 3GU |
| S2‑184140 | Solution of Indirect SRVCC procedure | Qualcomm Incorporated | imported from 3GU |
| S2‑184141 | Tunnel Info reservation at the UPF for sessions interworked with EPC | NTT DOCOMO | imported from 3GU |
| S2‑184142 | Correlation between EBI and QFI | Huawei, HiSilicon | imported from 3GU |
| S2‑184143 | CN Tunnel establishment for interworking handover | Huawei, Hisilicon | imported from 3GU |
| S2‑184144 | Dual Registration mode of operation from E-UTRA cell connecting to both EPC and 5GC | Intel | imported from 3GU |
| S2‑184145 | Requirements for 3GPP end user devices via 5G-RG/FN-RG | Ericsson | imported from 3GU |
| S2‑184146 | Alignment to BBF result: KI5 handover solution | Huawei, Hisilicon | imported from 3GU |
| S2‑184147 | Solution 1 update | Deutsche Telekom | imported from 3GU |
| S2‑184148 | DOCSIS solution for WWC | CableLabs, Charter Communications, Comcast | imported from 3GU |
| S2‑184149 | 23.716 solutions: IPV6 address allocation mechanisms for RGW | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑184150 | KI#5: solution for RM state | Huawei, Hisilicon | imported from 3GU |
| S2‑184151 | KI#5: solution for CM state | Huawei, Hisilicon | imported from 3GU |
| S2‑184152 | 23.716 solutions: Support of IPTV | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑184153 | IPTV solution for WWC | Huawei, Hisilicon | imported from 3GU |
| S2‑184154 | Service Area of SMF | Huawei, Hisilicon | imported from 3GU |
| S2‑184155 | Updates to solution 2 for SMF selection | Ericsson | imported from 3GU |
| S2‑184156 | ULCL relocation and release | Huawei, Hisilicon | imported from 3GU |
| S2‑184157 | Resource management of UPF shared by multiple SMFs during UPF relocation | Huawei, HiSilicon | imported from 3GU |
| S2‑184158 | Solution for AF influence on traffic routing | ZTE | imported from 3GU |
| S2‑184159 | ETSUN solution to key issue 5 | NEC | imported from 3GU |
| S2‑184160 | Solution for AF influence on traffic routing | ZTE | imported from 3GU |
| S2‑184161 | ULCL relocation and release | Huawei, Hisilicon | imported from 3GU |
| S2‑184162 | Clarification of traffic steering in UPF + PGW-U | KDDI | imported from 3GU |
| S2‑184163 | Proposal on the EPS Qos parameters on N7 | ZTE | imported from 3GU |
| S2‑184164 | EBI allocation and slicing interworking with EPS | NTT DOCOMO | imported from 3GU |
| S2‑184165 | Tunnel Info reservation at the UPF for sessions interworked with EPC | NTT DOCOMO | imported from 3GU |
| S2‑184166 | Correlation between EBI and QFI | Huawei, HiSilicon | imported from 3GU |
| S2‑184167 | Dual Registration mode of operation from E-UTRA cell connecting to both EPC and 5GC | Intel | imported from 3GU |
| S2‑184168 | CN Tunnel establishment for interworking handover | Huawei, Hisilicon | imported from 3GU |
| S2‑184169 | [DRAFT] Reply LS on 5G-GUTI type | Qualcomm Incorporated | imported from 3GU |
| S2‑184170 | Mapped parameters in case of No N26 | Qualcomm Incorporated | imported from 3GU |
| S2‑184171 | The interaction between PCF and AF | Huawei, HiSilicon | imported from 3GU |
| S2‑184172 | Policy related update in the PDU Session Establishment procedure | CATT | imported from 3GU |
| S2‑184173 | Correction on Policy Control Request Triggers | Huawei, HiSilicon | imported from 3GU |
| S2‑184174 | Default QoS rule | Ericsson | imported from 3GU |
| S2‑184175 | Clarification on Nnwdaf_Analytics_Info service | China Mobile | imported from 3GU |
| S2‑184176 | Clarification on DNAI and PRA mapping | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑184177 | Correction of description related to PFD management | KDDI | imported from 3GU |
| S2‑184178 | Corrections to PFD management | Ericsson | imported from 3GU |
| S2‑184179 | Remove PCF as the consumer of Namf_EventExposure and Nsmf_EventExposure services | CATT | imported from 3GU |
| S2‑184180 | Solution for key issue 3: Network Slicing and IMS | ZTE | imported from 3GU |
| S2‑184181 | Solution for KI on Discovery of Network Functions | Huawei, Hisilicon | imported from 3GU |
| S2‑184182 | Solutions for common IMS network through multiple 5GC network slices | Huawei, Hisilicon | imported from 3GU |
| S2‑184183 | Clarify related description for Network Sharing and Interworking | Intel, ZTE | imported from 3GU |
| S2‑184184 | Support use of DNN for URSP traffic descriptor | Qualcomm Incorporated, Intel | imported from 3GU |
| S2‑184185 | Correction to URSP and UE preferences for NSSP and SSCMSP | Qualcomm Incorporated | imported from 3GU |
| S2‑184186 | Correction to the UE Policy section 6.1.2.2.1 | NEC | imported from 3GU |
| S2‑184187 | Clarification on UE policy configuration -23.503 | OPPO, China Unicom, China Telecom | imported from 3GU |
| S2‑184188 | Additional PDU Session Type in Route Selection Descriptor | Huawei, HiSilicon | imported from 3GU |
| S2‑184189 | Clarification on 'match all ' URSP rule | Huawei, HiSilicon | imported from 3GU |
| S2‑184190 | Application detection report when PFDs are removed | Huawei, Hisilicon | imported from 3GU |
| S2‑184191 | Application detection report when PFDs are removed | Huawei, Hisilicon | imported from 3GU |
| S2‑184192 | Clarification on using PSI | OPPO, China Unicom | imported from 3GU |
| S2‑184193 | UE policy delivery corrections | Samsung | imported from 3GU |
| S2‑184194 | Clarification on policy provision in roaming case | LG Electronics | imported from 3GU |
| S2‑184195 | Clarification on policy provision in roaming case | LG Electronics | imported from 3GU |
| S2‑184196 | TS23.502 Clarification on Access and mobility related policy | ZTE | imported from 3GU |
| S2‑184197 | TS23.503 Clarification on Access and mobility related policy | ZTE | imported from 3GU |
| S2‑184198 | Cleanup to PCF selection in AMF and SMF | Huawei, HiSilicon | imported from 3GU |
| S2‑184199 | Description for policy association | Huawei, HiSilicon | imported from 3GU |
| S2‑184200 | Alignment with the definition of PCF-AMF and PCF-SMF interfaces | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑184201 | TS23.503 ePDG/N3IWF selection information | ZTE | imported from 3GU |
| S2‑184202 | Clarification on UE policy configuration -23.503 | OPPO, China Unicom, China Telecom | imported from 3GU |
| S2‑184203 | Additional PDU Session Type in Route Selection Descriptor | Huawei, HiSilicon | imported from 3GU |
| S2‑184204 | Clarification on 'match all ' URSP rule | Huawei, HiSilicon | imported from 3GU |
| S2‑184205 | Correction to the UE Policy section 6.1.2.2.1 | NEC | imported from 3GU |
| S2‑184206 | UE policy delivery corrections | Samsung | imported from 3GU |
| S2‑184207 | Clarification on using PSI | OPPO, China Unicom | imported from 3GU |
| S2‑184208 | Clarification on policy provision in roaming case | LG Electronics | imported from 3GU |
| S2‑184209 | Clarification on policy provision in roaming case | LG Electronics | imported from 3GU |
| S2‑184210 | TS23.502 Clarification on Access and mobility related policy | ZTE | imported from 3GU |
| S2‑184211 | Cleanup to PCF selection in AMF and SMF | Huawei, HiSilicon | imported from 3GU |
| S2‑184212 | Alignment with the definition of PCF-AMF and PCF-SMF interfaces | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑184213 | TS23.503 ePDG/N3IWF selection information | ZTE | imported from 3GU |
| S2‑184214 | Consolidation of UE Network Capabilities | Qualcomm Incorporated | imported from 3GU |
| S2‑184215 | Consolidation of UE Network Capabilities | Qualcomm Incorporated | imported from 3GU |
| S2‑184216 | Dual connectivity support for network slices | NTT DOCOMO | imported from 3GU |
| S2‑184217 | Xn handover and slice unavailability | Qualcomm Incorporated | imported from 3GU |
| S2‑184218 | [DRAFT] LS response on Applying Xn and NG HO procedure for Inter-RA Mobility | Qualcomm Incorporated | imported from 3GU |
| S2‑184219 | Summary on NSSAI handling in AS | Drafting group (Nokia) | imported from 3GU |
| S2‑184220 | LS from CT WG3: LS on Nudr Structured Data for Exposure | CT WG3 | imported from 3GU |
| S2‑184221 | SUPI based paging | Ericsson | imported from 3GU |
| S2‑184222 | [DRAFT] Reply LS on paging with IMSI/SUCI in 5GS | Ericsson | imported from 3GU |
| S2‑184223 | AS security context Principles | Nokia, Nokia Shanghai Bell (Editor) | imported from 3GU |
| S2‑184224 | Clarifications to Registration and UE triggered Service Request procedure | Ericsson | imported from 3GU |
| S2‑184225 | LS response on LS on Support User Plane Encryption in UP security policy | SA WG2 | imported from 3GU |
| S2‑184226 | LS response on LS on UP Security Policy | SA WG2 | imported from 3GU |
| S2‑184227 | [DRAFT] LS response on Initial NAS message protection | SA WG2 | imported from 3GU |
| S2‑184228 | Authentication Related Services | Ericsson | imported from 3GU |
| S2‑184229 | Response LS on authentication related services provided by AUSF and UDM | SA WG2 | imported from 3GU |
| S2‑184230 | Corrections for handling UP security policy when interworking with EPC | Ericsson, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑184231 | UE capability related to integrity protection of DRBs for signalling of the maximum supported data rate per UE for integrity protection | Qualcomm Incorporated | imported from 3GU |
| S2‑184232 | Propose Skeleton for eSBA TR 23.742 | China Mobile | imported from 3GU |
| S2‑184233 | Scope of eSBA TR | China Mobile | imported from 3GU |
| S2‑184234 | New Key Issue: Optimal modularization of the system | Deutsche Telekom, AT&T, Telecom Italia, Sprint, China Mobile, KDDI, Interdigital Inc., SK Telecom, Telstra, Verizon, NTT DOCOMO | imported from 3GU |
| S2‑184235 | New Key Issue: Improvements to service framework related aspects | Deutsche Telekom, AT&T, Telekom Italia, Sprint, SK Telecom, Ericsson, China Mobile | imported from 3GU |
| S2‑184236 | New Key Issue: Architectural support for highly reliable deployments | Deutsche Telekom, Interdigital, Sprint, KDDI, NTT DOCOMO | imported from 3GU |
| S2‑184237 | New Key Issue: Extend Service Concept into User Plane | CATT, China Mobile | imported from 3GU |
| S2‑184238 | New Key Issue: SBA backward and forward compatibility | Deutsche Telekom | imported from 3GU |
| S2‑184239 | Key Issue: Support of system flexibility and service provisioning | Huawei, HiSilicon | imported from 3GU |
| S2‑184240 | Architecture principles for eSBA | Huawei, HiSilicon | imported from 3GU |
| S2‑184241 | 3GPP SBA and ETSI NFV concepts | Ericsson | imported from 3GU |
| S2‑184242 | LS from RAN WG2: Response LS on INOBEAR | RAN WG2 | imported from 3GU |
| S2‑184243 | Use of priority parameters in scheduling | Ericsson | imported from 3GU |
| S2‑184244 | [DRAFT] LS reply to LS from SA WG4: LS on QoS for Live Uplink Streaming (FLUS) | SA WG2 | imported from 3GU |
| S2‑184245 | Clarification on multiple QoS rules with same QFI including QoS parameters | Samsung | imported from 3GU |
| S2‑184246 | [DRAFT] Reply LS on QoS | SA WG2 | imported from 3GU |
| S2‑184247 | Clarifications required resulting from 6-bit QFI limit | Samsung | imported from 3GU |
| S2‑184248 | Correction on dynamically assigned 5QI | Samsung | imported from 3GU |
| S2‑184249 | Temporary restriction of Reflective QoS | Intel, MediaTek Inc. | imported from 3GU |
| S2‑184250 | Temporary restriction of Reflective QoS | Intel, MediaTek Inc. | imported from 3GU |
| S2‑184251 | Identification and update of UE derived QoS rule | Samsung | imported from 3GU |
| S2‑184252 | Insufficient UE resources for signalled QoS rules | Intel | imported from 3GU |
| S2‑184253 | [DRAFT] LS on optimisation of UE capability signalling | MediaTek Inc. | imported from 3GU |
| S2‑184254 | Interactions with the DN-AAA that are not for authentication | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑184255 | SM_23.501_ReAuthentication by an external DN-AAA server | InterDigital Inc. | imported from 3GU |
| S2‑184256 | SM_23.502_ReAuthentication by an external DN-AAA server | InterDigital Inc. | imported from 3GU |
| S2‑184257 | Providing AF with information on the N6 User Plane tunelling information | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑184258 | Correction to DNN subscription | Telecom Italia | imported from 3GU |
| S2‑184259 | Lack of S-NSSAI or DNN in the PDU Session Establishment Request | Telecom Italia | imported from 3GU |
| S2‑184260 | TS 23.502 Wildcard DNN management | Huawei, HiSilicon | imported from 3GU |
| S2‑184261 | Different types of Ethernet services and N4 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑184262 | Correction for support of the Ethernet Type PDU Session | Huawei, Hisilicon | imported from 3GU |
| S2‑184263 | Clarification to the usage of Internal-Group Identifiers | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑184264 | LS from CT WG1: Reply LS on INOBEAR | CT WG1 | imported from 3GU |
| S2‑184265 | LADN configuration of UE | LG Electronics | imported from 3GU |
| S2‑184266 | How AMF provides LADN Information to UE | Huawei, HiSilicon | imported from 3GU |
| S2‑184267 | Clarification in LADN clause 5.6.5 | Intel, AT&T, KDDI, OPPO | imported from 3GU |
| S2‑184268 | How SMF validates UE location for LADN | Samsung | imported from 3GU |
| S2‑184269 | Clarification on downlink data handling for LADN | Samsung | imported from 3GU |
| S2‑184270 | LADN Signaling to SMF | Sony, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Ericsson | imported from 3GU |
| S2‑184271 | SMF getting UE location from the AMF for NPLI when no QoS flow to create/Update/modify | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑184272 | Reply LS one step MO SMS procedure | SA WG2 | imported from 3GU |
| S2‑184273 | Clarification on RAT fallback | LG Electronics | imported from 3GU |
| S2‑184274 | Update on AMF service operation to support query for terminating domain selection for IMS voice | China Mobile | imported from 3GU |
| S2‑184275 | 5_16_6_Mission Critical Services - Reference Update | FirstNet, AT&T, Motorola Solutions, Airwave | imported from 3GU |
| S2‑184276 | 5_16_6_Mission Critical Services - Editorial Changes and Clarifications | FirstNet, AT&T, Motorola Solutions, Airwave | imported from 3GU |
| S2‑184277 | Correction on capability negotation on 'SMS over NAS' | Samsung | imported from 3GU |
| S2‑184278 | Correction on capability negotation on 'SMS over NAS' | Samsung | imported from 3GU |
| S2‑184279 | Clarification on MT SMS domain selection by SMSF | LG Electronics | imported from 3GU |
| S2‑184280 | Clarification on MT SMS domain selection by SMSF | LG Electronics | imported from 3GU |
| S2‑184281 | Mobile Terminated SMS over NAS: 5GS Access Selection | Qualcomm Incorporated | imported from 3GU |
| S2‑184282 | Access Selection for Mobile Terminated SMS over NAS | Qualcomm Incorporated | imported from 3GU |
| S2‑184283 | Clarification on SMSF selection | LG Electronics | imported from 3GU |
| S2‑184284 | Clarification on the enabling SRVCC during 5GS to EPS connected mode mobility | ZTE | imported from 3GU |
| S2‑184285 | Missing 'redirection' to E-UTRA connected to 5GC | Intel | imported from 3GU |
| S2‑184286 | Clarification on Domain Selection for Emergency Service | OPPO | imported from 3GU |
| S2‑184287 | LS one eCall Indicator | SA WG2 | imported from 3GU |
| S2‑184288 | [DRAFT] LS Reply on DRX parameters negotiation | SA WG2 | imported from 3GU |
| S2‑184289 | Corrections on UE configuration update procedure | Huawei, HiSilicon | imported from 3GU |
| S2‑184290 | UE and network shall overide the Core Network type restriction for regulatory prioritized services | Spreadtrum | imported from 3GU |
| S2‑184291 | NAS level congestion control for emergency and high priority access | Qualcomm Incorporated, Vencore Labs, KPN | imported from 3GU |
| S2‑184292 | Clarification of high priority access | KPN N.V. | imported from 3GU |
| S2‑184293 | LS from CT WG1: LS on UE capability related to integrity protection of DRBs | CT WG1 | imported from 3GU |
| S2‑184294 | LS from CT WG3: LS on Deletion of Network Parameter Configuration | CT WG3 | imported from 3GU |
| S2‑184295 | AMF Selection aspects | Nokia, Nokia Shanghai Bell, NTT Docomo, Verizon, AT&T, Telecom Italia, SK Telecom | imported from 3GU |
| S2‑184296 | Clarification on the use of shared AMF Pointer value | Intel | imported from 3GU |
| S2‑184297 | Clarification on the use of shared AMF Pointer value | Intel | imported from 3GU |
| S2‑184298 | Clarification on NGAP UE-TNLA-binding per UE Release procedure | Intel | imported from 3GU |
| S2‑184299 | TS 23.501 Clarification on AMF management | ZTE | imported from 3GU |
| S2‑184300 | Update on UE mobility event notification | Samsung | imported from 3GU |
| S2‑184301 | LS from RAN WG2: Reply LS on 5G-S-TMSI | RAN WG2 | imported from 3GU |
| S2‑184302 | LS from RAN WG2: Reply LS on Extending TAC for NR and NG-RAN | RAN WG2 | imported from 3GU |
| S2‑184303 | Clarification on UE configuration update procedure | OPPO, Telecom Italia, ZTE, China Mobile, China Unicom, China Telecom | imported from 3GU |
| S2‑184304 | UCU procedure and Access Type | InterDigital Inc. | imported from 3GU |
| S2‑184305 | Network Slicing clause cleanup | Nokia, Nokia Shanghai Bell, Mediatek, Telecom Italia | imported from 3GU |
| S2‑184306 | Slice configuration change | Ericsson | imported from 3GU |
| S2‑184307 | Update of UE Configured NSSAI | Huawei, Hisilicon | imported from 3GU |
| S2‑184308 | S-NSSAI check for activation of UP connection of PDU Session | CATT | imported from 3GU |
| S2‑184309 | [DRAFT] Reply LS on 5G-S-TMSI | SA WG2 | imported from 3GU |
| S2‑184310 | Correction to AMF and S-NSSAI overload control | MediaTek Inc. | imported from 3GU |
| S2‑184311 | Clarification of S-NSSAI based congestion control | Qualcomm Incorporated, MediaTek Inc. | imported from 3GU |
| S2‑184312 | LS from RAN WG3: Reply LS on INOBEAR | RAN WG3 | imported from 3GU |
| S2‑184313 | PCRF trigger LLC Mobility clarifications on solution 3 | Ericsson | imported from 3GU |
| S2‑184314 | Updates to Solution #2 | Cisco Systems | imported from 3GU |
| S2‑184315 | AF Control of Make-before-break PDN Connection | Cisco Systems | imported from 3GU |
| S2‑184316 | Update to the impacts and evaluation for Solution 3 'PCRF initiated S/PGW-U change based on detection of applications requiring low latency' | Vodafone | imported from 3GU |
| S2‑184317 | Update to the impacts and evaluation for Solution 1 'make-before-break PDN connection mobility initiated by MME' | Vodafone | imported from 3GU |
| S2‑184318 | New solution: Addition of SGW-U as uplink classifier instead of relocating S/PGW-U | Vodafone | imported from 3GU |
| S2‑184319 | Scope of FS_EPS_URACE TR 23.736 | Vodafone | imported from 3GU |
| S2‑184320 | Requirements and Key Issues related to the use of Duplicated Networks | Vodafone | imported from 3GU |
| S2‑184321 | LS from CT WG4: Reply LS on INOBEAR | CT WG4 | imported from 3GU |
| S2‑184322 | TR Scope of 5G URLLC | Huawei, Hisilicon | imported from 3GU |
| S2‑184323 | Key issue on QoS Monitoring for 5G URLLC SID | Huawei, Hisilicon | imported from 3GU |
| S2‑184324 | Key issue of supporting high reliability for URLLC services | Huawei, Hisilicon | imported from 3GU |
| S2‑184325 | Key issue of supporting low latency and jitter during handover procedure | Huawei, Hisilicon | imported from 3GU |
| S2‑184326 | Key issue of supporting session continuity for URLLC services | Huawei, Hisilicon | imported from 3GU |
| S2‑184327 | Architecture assumption of 5G URLLC | Huawei, Hisilicon | imported from 3GU |
| S2‑184328 | [DRAFT] LS OUT on UE capability related to integrity protection of DRBs | SA WG2 | imported from 3GU |
| S2‑184329 | UDM services - addition to Nudm_UEAuthentication | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑184330 | AUSF clarification and alignment | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑184331 | Correction to User Plane Security Enforcement | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑184332 | SUPI based paging | Ericsson | imported from 3GU |
| S2‑184333 | [DRAFT] Reply LS on secured Signalling-only connection | SA WG2 | imported from 3GU |
| S2‑184334 | Indirect Data forwarding for N2 HO | Qualcomm Incorporated | imported from 3GU |
| S2‑184335 | [DRAFT] Reply LS on data forwarding for intra-system handover | SA WG2 | imported from 3GU |
| S2‑184336 | Local deactivation of MICO mode | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑184337 | Correction to handover procedures | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑184338 | Clarification on NG-RAN location reporting procedure | Samsung | imported from 3GU |
| S2‑184339 | Clarifying handling of reachability state | Ericsson | imported from 3GU |
| S2‑184340 | Clarification on single outstanding Service Request | Intel, MediaTek Inc. | imported from 3GU |
| S2‑184341 | Clarification of Data Notification in service request procedure | Huawei, Hisilicon | imported from 3GU |
| S2‑184342 | Corrections to the selective deactivation of UP connection | Motorola Mobility, Lenovo | imported from 3GU |
| S2‑184343 | Coexistence of RRC Inactive and Dual Connectivity | Qualcomm Incorporated | imported from 3GU |
| S2‑184344 | [DRAFT] Reply LS on coexistence between RRC inactive and dual connectivity | SA WG2 | imported from 3GU |
| S2‑184345 | UE DL Signalling handling in RRC Inactive State | Huawei, HiSilicon | imported from 3GU |
| S2‑184346 | TS 23.501: Clean-up for the parts of RRC Inactive | Huawei, HiSilicon | imported from 3GU |
| S2‑184347 | TS 23.502: Clean-up for the parts of RRC Inactive | Huawei, HiSilicon | imported from 3GU |
| S2‑184348 | Local deactivate MICO for emergency service | Qualcomm Incorporated | imported from 3GU |
| S2‑184349 | [DRAFT] LS on MDBV enforcement for delay critical QoS flows | SA WG2 | imported from 3GU |
| S2‑184350 | Clarification on the support of Delay Critical resource type | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑184351 | Updates to System Enablers for Priority Mechanisms | Vencore Labs, OEC, AT&T, T-Mobile USA, Sprint | imported from 3GU |
| S2‑184352 | Use of Establishment Cause in PDU Session Establishment Procedure | Vencore Labs, OEC, AT&T, T-Mobile USA, Sprint | imported from 3GU |
| S2‑184353 | MFBR Enforcement for GBR QoS flows | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑184354 | Clarification to handling of packet filters at PDU Session Modification | MediaTek Inc. | imported from 3GU |
| S2‑184355 | Temporary restriction of Reflective QoS | Intel, MediaTek Inc. | imported from 3GU |
| S2‑184356 | [DRAFT] LS on number of packet filters | SA WG2 | imported from 3GU |
| S2‑184357 | Reply LS on QoS | SA WG2 | imported from 3GU |
| S2‑184358 | Clarifications required resulting from 6-bit QFI limit | Samsung, CATT, Ericsson | imported from 3GU |
| S2‑184359 | Reply LS on QoS | SA WG2 | imported from 3GU |
| S2‑184360 | Clarification of the mapping releation between PDU session ID and access type in the AMF. | Huawei, HiSilicon | imported from 3GU |
| S2‑184361 | PDU Session Address Lifetime for SSC mode3 | Huawei, Hisilicon | imported from 3GU |
| S2‑184362 | Correction to CN-initiated selective deactivation of UP connection of an existing PDU Session | Huawei, HiSilicon | imported from 3GU |
| S2‑184363 | N4 modificaion inserted during PDU Session Modification | Samsung | imported from 3GU |
| S2‑184364 | Updates to SMF Event Exposure | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑184365 | Clarification on SMF selection | LG Electronics | imported from 3GU |
| S2‑184366 | Location information as part of UPF Provisioning Information | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑184367 | Clarification in LADN clause 5.6.5 | Intel, AT&T, KDDI, OPPO | imported from 3GU |
| S2‑184368 | Correction to DNN subscription | Telecom Italia, Samsung | imported from 3GU |
| S2‑184369 | TS 23.502 Wildcard DNN management | Huawei, HiSilicon | imported from 3GU |
| S2‑184370 | Clarification in LADN clause 5.6.5 | Intel, AT&T, KDDI, OPPO | imported from 3GU |
| S2‑184371 | How SMF validates UE location for LADN | Samsung | imported from 3GU |
| S2‑184372 | Different types of Ethernet services and N4 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑184373 | Lack of S-NSSAI or DNN in the PDU Session Establishment Request | Telecom Italia | imported from 3GU |
| S2‑184374 | [DRAFT] Reply LS on clarification of NSSAI information exchange during Inactive to connected mode transition | SA WG2 | imported from 3GU |
| S2‑184375 | New Key Issue: The criteria of making the decision and generating the assistant information provided to RAN | China Telecom | imported from 3GU |
| S2‑184376 | New Key Issue: Special aspect for scenario 2 | China Telecom | imported from 3GU |
| S2‑184377 | New Key Issue on UE Policy Driven 3GPP RATs Selection with Application Awareness | Intel | imported from 3GU |
| S2‑184378 | Architectural Assumptions for AAI_LTE_NR | China Telecom | imported from 3GU |
| S2‑184379 | Architectural assumptions | Qualcomm Incorporated | imported from 3GU |
| S2‑184380 | Architecture requirement on dual registration and dual radio | ZTE | imported from 3GU |
| S2‑184381 | Network Slicing clause cleanup | Nokia, Nokia Shanghai Bell, Mediatek, Telecom Italia | imported from 3GU |
| S2‑184382 | [DRAFT] LS on inclusion of NSSAI in RRC connection establishment procedure | SA WG2 | imported from 3GU |
| S2‑184383 | AMF UE area of interest reporting in RRC inactive state | Ericsson | imported from 3GU |
| S2‑184384 | UE Presence in Area Of Interest | Samsung | imported from 3GU |
| S2‑184385 | UE Presence in Area Of Interest | Samsung | imported from 3GU |
| S2‑184386 | AMF Context Retrieval upon relocation | Nokia, Nokia Shanghai Bell, NTT DoCoMo | imported from 3GU |
| S2‑184387 | AMF functionality clarification - to add SUCI | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑184388 | Correction to identifiers in Registration procedure | Intel | imported from 3GU |
| S2‑184389 | Correction to identifiers in Registration procedure | Intel | imported from 3GU |
| S2‑184390 | [DRAFT] LS on Low Access Priority in 5G system | SA WG2 | imported from 3GU |
| S2‑184391 | Correction on NAS level congestion control | CATT | imported from 3GU |
| S2‑184392 | TS23.502 Clarification on Internal Group ID | ZTE | imported from 3GU |
| S2‑184393 | LS from RAN WG2: Response to LS on encrypting broadcasted positioning data and LS on provisioning of positioning assistance data via LPPa for broadcast | RAN WG2 | imported from 3GU |
| S2‑184394 | LS from RAN WG2: Reply LS to SA3 on encryption of broadcast positioning information | RAN WG2 | imported from 3GU |
| S2‑184395 | AMF Selection aspects | Nokia, Nokia Shanghai Bell, NTT Docomo, Verizon, AT&T, Telecom Italia, SK Telecom | imported from 3GU |
| S2‑184396 | Clarification on the use of shared AMF Pointer value | Intel | imported from 3GU |
| S2‑184397 | UCU procedure and Access Type | InterDigital Inc. | imported from 3GU |
| S2‑184398 | Correction on NAS level congestion control | CATT | imported from 3GU |
| S2‑184399 | Corrections on UE configuration update procedure | Huawei, HiSilicon | imported from 3GU |
| S2‑184400 | Correction on NAS level congestion control | CATT | imported from 3GU |
| S2‑184401 | Additional parameters for NB-IoT UE Uu operation optimisation | Huawei, HiSilicon | imported from 3GU |
| S2‑184402 | Additional parameters for NB-IoT UE Uu operation optimisation | Huawei, HiSilicon | imported from 3GU |
| S2‑184403 | [DRAFT] Reply LS on service gap control with resume for non-supporting UE | Ericsson | imported from 3GU |
| S2‑184404 | Monitoring Event configuration removal for a group | Huawei, Hisilicon | imported from 3GU |
| S2‑184405 | Removal of leftover sentence regarding MTC-IWF architecture | ORANGE | imported from 3GU |
| S2‑184406 | Handling of very large UE radio capabilities for the anticipated EN-DC UEs | Vodafone | imported from 3GU |
| S2‑184407 | Solution for Key Issue on Expected UE Behaviour | Huawei, HiSilicon, Convida Wireless LLC, InterDigital, Samsung | imported from 3GU |
| S2‑184408 | Classification of external parameters to MM and SM parameters | Motorola Mobility, Lenovo | imported from 3GU |
| S2‑184409 | Solution for KI7: Reuse of EPS Overload Control Mechanims | Huawei, HiSilicon | imported from 3GU |
| S2‑184410 | Solution KI-14: QoS for Data over NAS | Qualcomm Incorporated | imported from 3GU |
| S2‑184411 | Support QoS Differentiation for Unstructured PDU Session | Huawei, HiSilicon | imported from 3GU |
| S2‑184412 | SMF assisted RAN information | Motorola Mobility, Lenovo | imported from 3GU |
| S2‑184413 | Infrequent Small Data Transmission: Using Resume and Suspend procedure | Samsung, SK Telecom | imported from 3GU |
| S2‑184414 | TR 23.724: ConnectionLess (CL) data solution | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑184415 | NEF based infrequent small data transfer via NAS-SM | Huawei, HiSilicon | imported from 3GU |
| S2‑184416 | TR 23.724: Addressing open issues for Solution 1 | Qualcomm Incorporated | imported from 3GU |
| S2‑184417 | Enhanced MICO mode for power saving function | Huawei, HiSilicon | imported from 3GU |
| S2‑184418 | PCR 23.724: eDRX | Ericsson | imported from 3GU |
| S2‑184419 | Trust Model and Architecture Assumption | Intel | imported from 3GU |
| S2‑184420 | Solution for UE assisted enrypted traffic detection | OPPO, China Unicom | imported from 3GU |
| S2‑184421 | Providing AF with information on the N6 User Plane tunelling information | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑184422 | Correction to DNN subscription | Telecom Italia, Samsung | imported from 3GU |
| S2‑184423 | Different types of Ethernet services and N4 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑184424 | LADN configuration of UE | LG Electronics | imported from 3GU |
| S2‑184425 | Clarification of the mapping releation between PDU session ID and access type in the AMF. | Huawei, HiSilicon | imported from 3GU |
| S2‑184426 | Correction to CN-initiated selective deactivation of UP connection of an existing PDU Session | Huawei, HiSilicon | imported from 3GU |
| S2‑184427 | Lack of S-NSSAI or DNN in the PDU Session Establishment Request | Telecom Italia | imported from 3GU |
| S2‑184428 | Updates to SMF Event Exposure | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑184429 | Providing AF with information on the N6 User Plane tunelling information | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑184430 | Correction for support of the Ethernet Type PDU Session | Huawei, Hisilicon | imported from 3GU |
| S2‑184431 | How SMF validates UE location for LADN | Samsung | imported from 3GU |
| S2‑184432 | Clarification on downlink data handling for LADN | Samsung | imported from 3GU |
| S2‑184433 | SMF getting UE location from the AMF for NPLI when no QoS flow to create/Update/modify | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑184434 | LADN configuration of UE | LG Electronics | imported from 3GU |
| S2‑184435 | SMF getting UE location from the AMF for NPLI when no QoS flow to create/Update/modify | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑184436 | LADN configuration of UE | LG Electronics | imported from 3GU |
| S2‑184437 | SMF getting UE location from the AMF for NPLI when no QoS flow to create/Update/modify | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑184438 | LADN configuration of UE | LG Electronics | imported from 3GU |
| S2‑184439 | Clarification on NSSAI related functionality in 5G RAN | Qualcomm Incorporated | imported from 3GU |
| S2‑184440 | Clarification of the mapping releation between PDU session ID and access type in the AMF. | Huawei, HiSilicon | imported from 3GU |
| S2‑184441 | Way forward for interworking for PDU sessions with same DNN for different slices | Drafting group (Huawei) | imported from 3GU |
| S2‑184442 | Reply LS one step MO SMS procedure | SA WG2 | imported from 3GU |
| S2‑184443 | Update on AMF service operation to support query for terminating domain selection for IMS voice | China Mobile | imported from 3GU |
| S2‑184444 | Correction on capability negotation on 'SMS over NAS' | Samsung, LG Electronics | imported from 3GU |
| S2‑184445 | Correction on capability negotation on 'SMS over NAS' | Samsung, LG Electronics | imported from 3GU |
| S2‑184446 | Clarification on SMSF selection | LG Electronics | imported from 3GU |
| S2‑184447 | Clarification on Domain Selection for Emergency Service | OPPO | imported from 3GU |
| S2‑184448 | [DRAFT] LS on eCall broadcast indicator and Emergency services support broadcast indicator | SA WG2 | imported from 3GU |
| S2‑184449 | Mobile Terminated SMS over NAS: 5GS Access Selection | Qualcomm Incorporated | imported from 3GU |
| S2‑184450 | Correction on capability negotation on 'SMS over NAS' | Samsung, LG Electronics | imported from 3GU |
| S2‑184451 | Correction on capability negotation on 'SMS over NAS' | Samsung, LG Electronics | imported from 3GU |
| S2‑184452 | Correction on capability negotation on 'SMS over NAS' | Samsung, LG Electronics | imported from 3GU |
| S2‑184453 | [DRAFT] LS on eCall broadcast indicator and Emergency services support broadcast indicator | SA WG2 | imported from 3GU |
| S2‑184454 | Update on AMF service operation to support query for terminating domain selection for IMS voice | China Mobile | imported from 3GU |
| S2‑184455 | Correction on capability negotation on 'SMS over NAS' | Samsung, LG Electronics | imported from 3GU |
| S2‑184456 | S-NSSAI check in Network Triggered Service Request | CATT | imported from 3GU |
| S2‑184457 | Update to solution 8 - Routing media traffic via different 5GC network slices | Motorola Mobility, Lenovo | imported from 3GU |
| S2‑184458 | Solution X for key issue 5 : Enabling SBA-based Cx | Ericsson | imported from 3GU |
| S2‑184459 | Consideration on SBA-based Cx | Huawei, Hisilicon | imported from 3GU |
| S2‑184460 | Solution X for key issue 6 : Enabling SBA-based Sh | Ericsson | imported from 3GU |
| S2‑184461 | Solution for utilizing services provided by 5GC | Huawei, Hisilicon | imported from 3GU |
| S2‑184462 | Solution for key issue 3: Network Slicing and IMS | ZTE | imported from 3GU |
| S2‑184463 | Solution X for key issue 6 : Enabling SBA-based Sh | Ericsson | imported from 3GU |
| S2‑184464 | Solution for key issue 3: Network Slicing and IMS | ZTE | imported from 3GU |
| S2‑184465 | Solution for KI on Discovery of Network Functions | Huawei, Hisilicon | imported from 3GU |
| S2‑184466 | Clarification on N3GPP TAI | Samsung | imported from 3GU |
| S2‑184467 | Clarification for Network Requested PDU Session Release via Untrusted non-3GPP access | Huawei, Hisilicon | imported from 3GU |
| S2‑184468 | Clarification on N3GPP TAI | Samsung | imported from 3GU |
| S2‑184469 | Clarification for Network Requested PDU Session Release via Untrusted non-3GPP access | Huawei, Hisilicon | imported from 3GU |
| S2‑184470 | Architectural Updates for ATSSS Solution 1 | BT Plc, Broadcom | imported from 3GU |
| S2‑184471 | New solution: MPTCP proxy architecture | Apple, Inc. | imported from 3GU |
| S2‑184472 | Architecture framework with ATSSS rules and UP Access Agnostic Reporting Control Protocol | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑184473 | Solution 2 Update: NW-Requested Establishment of MA-PDU session | Motorola Mobility, Lenovo | imported from 3GU |
| S2‑184474 | ATSSS Solution - Update of Solution 2 | LG Electronics, Motorola Mobility, Lenovo, InterDigital | imported from 3GU |
| S2‑184475 | ATSSS Rule definition and TFCP procedure update | Huawei, Hisilicon | imported from 3GU |
| S2‑184476 | Architectural Updates for ATSSS Solution 1 | BT Plc, Broadcom | imported from 3GU |
| S2‑184477 | Alignment to BBF result: KI5 handover solution | Huawei, Hisilicon | imported from 3GU |
| S2‑184478 | 23.716 solutions: Support of IPTV | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑184479 | 23.716 solutions: IPV6 address allocation mechanisms for RGW | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑184480 | Architectural assumptions and requirements of 5G SRVCC | China Unicom | imported from 3GU |
| S2‑184481 | New key issue on enabling SRVCC from NG-RAN to UTRAN CS | Intel, Huawei, HiSilicon, ZTE, China Unicom | imported from 3GU |
| S2‑184482 | New key issue on returning UE to NG-RAN from UTRAN CS | Intel, Huawei, HiSilicon, ZTE, China Unicom | imported from 3GU |
| S2‑184483 | Return from UTRAN to NG-RAN for SRVCC from 5GS to UTRAN | SA WG2 | imported from 3GU |
| S2‑184484 | Key Issue of Analysis PS HO support in SRVCC from 5G to 3G | Qualcomm Incorporated | imported from 3GU |
| S2‑184485 | Solution on reusing the mechanism in EPS SRVCC to enable the 5G SRVCC | ZTE, Huawei, Qualcomm Incorporated | imported from 3GU |
| S2‑184486 | Solution of Indirect SRVCC procedure | Qualcomm Incorporated | imported from 3GU |
| S2‑184487 | S-NSSAI check in Network Triggered Service Request | CATT | imported from 3GU |
| S2‑184488 | Network Slicing clause cleanup | Nokia, Nokia Shanghai Bell, Mediatek, Telecom Italia | imported from 3GU |
| S2‑184489 | Reply LS on coexistence between RRC inactive and dual connectivity | SA WG2 | imported from 3GU |
| S2‑184490 | UE DL Signalling handling in RRC Inactive State | Huawei, HiSilicon | imported from 3GU |
| S2‑184491 | [DRAFT] Reply LS on secured Signalling-only connection | SA WG2 | imported from 3GU |
| S2‑184492 | Clarifying handling of reachability state | Ericsson | imported from 3GU |
| S2‑184493 | S-NSSAI check for activation of UP connection of PDU Session | CATT | imported from 3GU |
| S2‑184494 | Use of priority parameters in scheduling | Ericsson | imported from 3GU |
| S2‑184495 | Way forward for interworking for PDU sessions with same DNN for different slices | Drafting group (Huawei) | imported from 3GU |
| S2‑184496 | EBI allocation and slicing interworking with EPS | NTT DOCOMO | imported from 3GU |
| S2‑184497 | Clarification on NSSAI related functionality in 5G RAN | Qualcomm Incorporated | imported from 3GU |
| S2‑184498 | LS on clarification of NSSAI information exchange during Inactive to connected mode transition | SA WG2 | imported from 3GU |
| S2‑184499 | [DRAFT] LS on inclusion of NSSAI in RRC connection establishment procedure | SA WG2 | imported from 3GU |
| S2‑184500 | Xn handover and slice unavailability | Qualcomm Incorporated | imported from 3GU |
| S2‑184501 | Reply LS on 5G-S-TMSI | SA WG2 | imported from 3GU |
| S2‑184502 | New Study on Architecture aspects of using satellite access in 5G | Thales, TNO, CNES, Avanti, CCTC, ESA, Fraunhofer IIS, Hughes Network Systems, Nomor Research, Catapult, IAESI, SES, ICS, VTT, Alibaba | imported from 3GU |
| S2‑184503 | New SID on supporting Flexible Local Area Data Network | LG Electronics, SK Telecom, LG Uplus, KT Corp., Verizon UK LTD, Sprint, China Unicom, Telecom Italia, KPN, Samsung, ETRI, ITRI, Cisco, Oracle, Sony | imported from 3GU |
| S2‑184504 | Study on system architecture for next generation real time communication services | China Mobile, Deutsche Telekom, Verzion, China Telecom, Telefonica, China Unicom, AT&T, Huawei, ZTE, CATT, CATR, Institute for Information Industry, OPPO | imported from 3GU |
| S2‑184505 | 5GMBS Study Item proposal | Huawei, HiSilicon | imported from 3GU |
| S2‑184506 | Clarifications to Registration and UE triggered Service Request procedure | Ericsson | imported from 3GU |
| S2‑184507 | Reply LS on secured Signalling-only connection | SA WG2 | imported from 3GU |
| S2‑184508 | [DRAFT] LS response on Initial NAS message protection | SA WG2 | imported from 3GU |
| S2‑184509 | [DRAFT] LS OUT on UE capability related to integrity protection of DRBs | SA WG2 | imported from 3GU |
| S2‑184510 | LS response on Initial NAS message protection | SA WG2 | imported from 3GU |
| S2‑184511 | Reply LS on paging with IMSI/SUCI in 5GS | SA WG2 | imported from 3GU |
| S2‑184512 | Reply LS on paging with IMSI/SUCI in 5GS | SA WG2 | imported from 3GU |
| S2‑184513 | LS OUT on UE capability related to integrity protection of DRBs | SA WG2 | imported from 3GU |
| S2‑184514 | Consolidation of UE Network Capabilities | Qualcomm Incorporated, Spreadtrum Communications, Ericsson | imported from 3GU |
| S2‑184515 | Consolidation of UE Network Capabilities | Qualcomm Incorporated, Intel | imported from 3GU |
| S2‑184516 | Dual connectivity support for network slices | NTT DOCOMO | imported from 3GU |
| S2‑184517 | Encrypted traffic detection and verification | Huawei, Hisilicon | imported from 3GU |
| S2‑184518 | Alternative UE-assisted ENTRADE solution | Qualcomm Incorporated | imported from 3GU |
| S2‑184519 | Alternative UE-assisted ENTRADE solution | Qualcomm Incorporated | imported from 3GU |
| S2‑184520 | Solution to Key issue #EPC-3 | Ericsson | imported from 3GU |
| S2‑184521 | Solution to Key issue IMS-1, IMS-2, and IMS-3 | Ericsson | imported from 3GU |
| S2‑184522 | Solution to Key issue #IMS-4: Support of emergency services by UEs attached for RLOS | Ericsson | imported from 3GU |
| S2‑184523 | PLMN selection and radio access for RLOS | Motorola Mobility, Lenovo | imported from 3GU |
| S2‑184524 | Removing some ENs and update in Solution #4 | Ericsson | imported from 3GU |
| S2‑184525 | How to complete RLOS service | Samsung | imported from 3GU |
| S2‑184526 | Solution to Key issue #EPC-3 | Ericsson | imported from 3GU |
| S2‑184527 | Solution to Key issue IMS-1, IMS-2, and IMS-3 | Ericsson | imported from 3GU |
| S2‑184528 | Solution to Key issue #IMS-4: Support of emergency services by UEs attached for RLOS | Ericsson | imported from 3GU |
| S2‑184529 | Reserved for Puneet's parallel sessions | - | imported from 3GU |
| S2‑184530 | Reserved for Puneet's parallel sessions | - | imported from 3GU |
| S2‑184531 | Reserved for Puneet's parallel sessions | - | imported from 3GU |
| S2‑184532 | Reserved for Puneet's parallel sessions | - | imported from 3GU |
| S2‑184533 | Reserved for Puneet's parallel sessions | - | imported from 3GU |
| S2‑184534 | Reserved for Puneet's parallel sessions | - | imported from 3GU |
| S2‑184535 | Reserved for Puneet's parallel sessions | - | imported from 3GU |
| S2‑184536 | Reserved for Puneet's parallel sessions | - | imported from 3GU |
| S2‑184537 | Network Slicing clause cleanup | Nokia, Nokia Shanghai Bell, Mediatek, Telecom Italia | imported from 3GU |
| S2‑184538 | Slice configuration change | Ericsson | imported from 3GU |
| S2‑184539 | Clarify related description for Network Sharing and Interworking | Intel, ZTE, Ericsson | imported from 3GU |
| S2‑184540 | Remove Tracking Area from cell information for shared network | Ericsson | imported from 3GU |
| S2‑184541 | EBI allocation and slicing interworking with EPS | NTT DOCOMO, Ericsson | imported from 3GU |
| S2‑184542 | Dual connectivity support for network slices | NTT DOCOMO | imported from 3GU |
| S2‑184543 | Correction on dynamically assigned 5QI | Samsung | imported from 3GU |
| S2‑184544 | Temporary restriction of Reflective QoS | Intel, MediaTek Inc. | imported from 3GU |
| S2‑184545 | Clarification on the support of Delay Critical resource type | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑184546 | Updates to System Enablers for Priority Mechanisms | Vencore Labs, OEC, AT&T, T-Mobile USA, Sprint | imported from 3GU |
| S2‑184547 | MFBR Enforcement for GBR QoS flows | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑184548 | Use of priority parameters in scheduling | Ericsson | imported from 3GU |
| S2‑184549 | Add inidcation of Notification Control to QoS rules sent to UE | Qualcomm Incorporated | imported from 3GU |
| S2‑184550 | Clarifications required resulting from 6-bit QFI limit | Samsung, CATT, Ericsson | imported from 3GU |
| S2‑184551 | Reply LS on UE supported number of packet filters for signalled QoS rules | SA WG2 | imported from 3GU |
| S2‑184552 | EBI allocation and slicing interworking with EPS | NTT DOCOMO, Ericsson | imported from 3GU |
| S2‑184553 | New Key Issue: Optimal modularization of the system | Deutsche Telekom, AT&T, Telecom Italia, Sprint, China Mobile, KDDI, Interdigital Inc., SK Telecom, Telstra, Verizon, NTT DOCOMO | imported from 3GU |
| S2‑184554 | New Key Issue: Improvements to service framework related aspects | Deutsche Telekom, AT&T, Telekom Italia, Sprint, SK Telecom, Ericsson, China Mobile | imported from 3GU |
| S2‑184555 | New Key Issue: Architectural support for highly reliable deployments | Deutsche Telekom, Interdigital, Sprint, KDDI, NTT DOCOMO | imported from 3GU |
| S2‑184556 | New Key Issue: SBA backward and forward compatibility | Deutsche Telekom | imported from 3GU |
| S2‑184557 | UCU procedure and Access Type | InterDigital Inc. | imported from 3GU |
| S2‑184558 | LS on Delay Tolerant Access and Low Access Priority in 5GS | SA WG2 | imported from 3GU |
| S2‑184559 | EBI allocation and slicing interworking with EPS | NTT DOCOMO, Ericsson | imported from 3GU |
| S2‑184560 | Clarification on NGAP UE-TNLA-binding per UE Release procedure | Intel | imported from 3GU |
| S2‑184561 | TS23.502 Clarification on Internal Group ID | ZTE | imported from 3GU |
| S2‑184562 | UCU procedure and Access Type | InterDigital Inc. | imported from 3GU |
| S2‑184563 | EBI allocation and slicing interworking with EPS | NTT DOCOMO, Ericsson | imported from 3GU |
| S2‑184564 | New key issue on returning UE to NG-RAN from UTRAN CS | Intel, Huawei, HiSilicon, ZTE, China Unicom | imported from 3GU |
| S2‑184565 | Use of priority parameters in scheduling | Ericsson | imported from 3GU |
| S2‑184566 | TS 23.502 Clarification on Application data | Huawei, HiSilicon, China Mobile | imported from 3GU |
| S2‑184567 | Updates on Subscribe Service Operation | Huawei, Hisilicon | imported from 3GU |
| S2‑184568 | Update UDR DM service for data subscription | China Mobile | imported from 3GU |
| S2‑184569 | TS23.502 Nnef_TrafficInfluence service | ZTE | imported from 3GU |
| S2‑184570 | Clarifications on Nudr interactions between PCF and UDR | Ericsson | imported from 3GU |
| S2‑184571 | Application detection report when PFDs are removed | Huawei, Hisilicon | imported from 3GU |
| S2‑184572 | Use cases introduction and guidelines | ORANGE | imported from 3GU |
| S2‑184573 | New use case: Prevention of various security attacks | ORANGE | imported from 3GU |
| S2‑184574 | New Key Issue for Data Collection Framework (additional content) | ORANGE | imported from 3GU |
| S2‑184575 | Key issue on performance improvement and supervision of mIoT terminals | China Mobile | imported from 3GU |
| S2‑184576 | Update to the impacts and evaluation for Solution 1 'make-before-break PDN connection mobility initiated by MME' | Vodafone | imported from 3GU |
| S2‑184577 | New solution: Addition of SGW-U as uplink classifier instead of relocating S/PGW-U | Vodafone | imported from 3GU |
| S2‑184578 | Scope of FS_EPS_URACE TR 23.736 | Vodafone | imported from 3GU |
| S2‑184579 | New Key Issue: Improvements to service framework related aspects | Deutsche Telekom, AT&T, Telekom Italia, Sprint, SK Telecom, Ericsson, China Mobile | imported from 3GU |
| S2‑184580 | New Key Issue: Architectural support for highly reliable deployments | Deutsche Telekom, Interdigital, Sprint, KDDI, NTT DOCOMO | imported from 3GU |
| S2‑184581 | New Key Issue: Extend Service Concept into User Plane | CATT, China Mobile | imported from 3GU |
| S2‑184582 | Key Issue: Support of system flexibility and service provisioning | Huawei, HiSilicon | imported from 3GU |
| S2‑184583 | Architecture principles for eSBA | Huawei, HiSilicon | imported from 3GU |
| S2‑184584 | 3GPP SBA and ETSI NFV concepts | Ericsson | imported from 3GU |
| S2‑184585 | Controlled support of (AF) session binding for Ethernet PDU Session Type | Nokia, Nokia Shanghai Bell, China Mobile | imported from 3GU |
| S2‑184586 | TS23.503 Clarification on BSF | ZTE | imported from 3GU |
| S2‑184587 | TS 23.501 Clarification on Application data | Huawei, HiSilicon, China Mobile | imported from 3GU |
| S2‑184588 | TS23.502 Remove access independent event trigger in Nsmf_EventExposure Service | ZTE | imported from 3GU |
| S2‑184589 | Clarification on Nnwdaf_Analytics_Info service | China Mobile | imported from 3GU |
| S2‑184590 | Key issue of supporting high reliability for URLLC services | Huawei, Hisilicon | imported from 3GU |
| S2‑184591 | LADN configuration of UE | LG Electronics | imported from 3GU |
| S2‑184592 | Propose Skeleton for eSBA TR 23.742 | China Mobile | imported from 3GU |
| S2‑184593 | Key issue of supporting high reliability for URLLC services | Huawei, Hisilicon | imported from 3GU |
| S2‑184594 | Key Issue on Slice Interworking between 5GC and EPC | Qualcomm Incorporated | imported from 3GU |
| S2‑184595 | Support of isolated slice usage in the UE | Huawei, HiSilicon | imported from 3GU |
| S2‑184596 | Corrections to PFD management | Ericsson | imported from 3GU |
| S2‑184597 | New Key Issue: Special aspect for scenario 2 | China Telecom | imported from 3GU |
| S2‑184598 | Architectural Assumptions for AAI_LTE_NR | China Telecom | imported from 3GU |
| S2‑184599 | Clarification on NGAP UE-TNLA-binding per UE Release procedure | Intel | imported from 3GU |
| S2‑184600 | Different types of Ethernet services and N4 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑184601 | How SMF validates UE location for LADN | Samsung | imported from 3GU |
| S2‑184602 | Location information as part of UPF Provisioning Information | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑184603 | MFBR Enforcement for GBR QoS flows | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑184604 | Use of priority parameters in scheduling | Ericsson | imported from 3GU |
| S2‑184605 | LS on aspects of handling large UE radio capabilities in EPC | SA WG2 | imported from 3GU |
| S2‑184606 | Application detection report when PFDs are removed | Huawei, HiSilicon, Ericsson | imported from 3GU |
| S2‑184607 | Application detection report when PFDs are removed | Huawei, Hisilicon | imported from 3GU |
| S2‑184608 | LS on optimisation of UE capability signalling | SA WG2 | imported from 3GU |
| S2‑184609 | Defining NWDAF in 23.501 | Ericsson, AT&T, Huawei | imported from 3GU |
| S2‑184610 | Alignment of the name of the network function | Samsung | imported from 3GU |
| S2‑184611 | Update on UE mobility event notification | Samsung | imported from 3GU |
| S2‑184612 | Different types of Ethernet services and N4 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑184613 | LS on MDBV for delay critical QoS flows | SA WG2 | imported from 3GU |
| S2‑184614 | LS reply to LS on QoS for Live Uplink Streaming (FLUS) | SA WG2 | imported from 3GU |
| S2‑184615 | LS on UE supported number of packet filters for signalled QoS rules | SA WG2 | imported from 3GU |
| S2‑184616 | Clarification on using PSI | OPPO, China Unicom | imported from 3GU |
| S2‑184617 | LS reply to LS on Questions on Events related to Service Data Flows in the Nsmf_EventExposure service | SA WG2 | imported from 3GU |
| S2‑184618 | Corrections to PFD management | Ericsson | imported from 3GU |
| S2‑184619 | NEF and UDR in LBO architecture for AF influence on traffic routing | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑184620 | LS on eCall broadcast indicator and Emergency services support broadcast indicator | SA WG2 | imported from 3GU |
| S2‑184621 | Dual Registration mode of operation from E-UTRA cell connecting to both EPC and 5GC | Intel, Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑184622 | Mapped parameters in case of No N26 | Qualcomm Incorporated | imported from 3GU |
| S2‑184623 | TS23.502 Additional DataSet and Datakey | ZTE, Ericsson | imported from 3GU |
| S2‑184624 | Reply LS on Nudr Structured Data for Exposure | SA WG2 | imported from 3GU |
| S2‑184625 | Clarification on Key Issue: Network Slicing for eV2X | Huawei, HiSilicon | imported from 3GU |
| S2‑184626 | Efficient Service Provisioning to UE for eV2X communications over PC5 and Uu reference point | Huawei, HiSilicon | imported from 3GU |
| S2‑184627 | EV2X architecture reference model | Samsung, SK Telecom | imported from 3GU |
| S2‑184628 | KI 3: Solution for High latency communication | Ericsson, CATT | imported from 3GU |
| S2‑184629 | PCR 23.724: eDRX | Ericsson | imported from 3GU |
| S2‑184630 | New Key Issue for Data Collection Framework (additional content) | ORANGE, Huawei, HiSilicon, AT&T, KDDI | imported from 3GU |
| S2‑184631 | New use case: Prevention of various security attacks | ORANGE | imported from 3GU |
| S2‑184632 | Use Case: NWDA-assisting E2E QoS Assurance | Huawei, HiSilicon, China Mobile, AT&T, NTT DoCoMo, Intel, NEC | imported from 3GU |
| S2‑184633 | Updates to Solution #5 | Cisco Systems | imported from 3GU |
| S2‑184634 | LCS architecture enhancement addressing Key Issue #1 in TR 23.731 | Huawei, HiSilicon | imported from 3GU |
| S2‑184635 | Solution for position via user plane transmission | Huawei, HiSilicon | imported from 3GU |
| S2‑184636 | Solution to new KI of supporting non-3GPP access | Huawei, HiSilicon | imported from 3GU |
| S2‑184637 | Solutions for common IMS network through multiple 5GC network slices | Huawei, Hisilicon | imported from 3GU |
| S2‑184638 | Reply LS on INOBEAR | SA WG2 | imported from 3GU |
| S2‑184639 | Solution to Key issue #IMS-4: Support of emergency services by UEs attached for RLOS | Ericsson | imported from 3GU |
| S2‑184640 | AF Control of Make-before-break PDN Connection | Cisco Systems | imported from 3GU |
| S2‑184641 | Updates to Solution #2 | Cisco Systems | imported from 3GU |
| S2‑184642 | Requirements and Key Issues related to the use of Duplicated Networks | Vodafone | imported from 3GU |
| S2‑184643 | Key Issue: Support of system flexibility and service provisioning | Huawei, HiSilicon | imported from 3GU |
| S2‑184644 | New Key Issue: Extend Service Concept into User Plane | CATT, China Mobile | imported from 3GU |
| S2‑184645 | Propose Skeleton for eSBA TR 23.742 | China Mobile | imported from 3GU |
| S2‑184646 | Architectural assumptions and requirements of 5G SRVCC | China Unicom | imported from 3GU |
page generated from database: 2024-04-13 13:51:47