3GPP TDocs (written contributions) at meeting
Meeting: S2-128 - 2018-07-02 to 2018-07-06, Vilnius
meeting id: S2-128 (click id for more info on this meeting)Click on the Tdoc to open its file.
| TDoc | Title | Source | Remarks |
|---|---|---|---|
| S2‑186305 | Draft Agenda for SA WG2#128 | SA WG2 Chairman | imported from 3GU |
| S2‑186306 | Draft Report of SA WG2 meeting #127BIS | SA WG2 Secretary | imported from 3GU |
| S2‑186307 | LS from RAN WG3: LS on data forwarding for intra-system handover | RAN WG3 | imported from 3GU |
| S2‑186308 | LS from RAN WG3: LS on Handling of end marker packets | RAN WG3 | imported from 3GU |
| S2‑186309 | LS from SA WG3: LS on AS Security Context Setup | SA WG3 | imported from 3GU |
| S2‑186310 | LS from RAN WG2: LS to SA WG2 and CT WG1 on enabling and disabling NG RAN Capabilities | RAN WG2 | imported from 3GU |
| S2‑186311 | LS from CT WG1: LS on UE capability related to integrity protection of DRBs | CT WG1 | imported from 3GU |
| S2‑186312 | LS from CT WG1: LS on modification of solution for PLMN and RAT selection policies for roaming based on SA WG2 comments | CT WG1 | imported from 3GU |
| S2‑186313 | LS from CT WG1: Reply LS on 5G service request procedure | CT WG1 | imported from 3GU |
| S2‑186314 | LS from CT WG3: LS on the update of Nnef_PFDmanagement description | CT WG3 | imported from 3GU |
| S2‑186315 | LS from CT WG4: LS on Access Restriction Data for NR in EPC | CT WG4 | imported from 3GU |
| S2‑186316 | LS from RAN WG2: LS on GAD shape(s) for high accuracy positioning | RAN WG2 | imported from 3GU |
| S2‑186317 | LS from RAN WG3: Response to LS on encrypting broadcasted positioning data and LS on provisioning of positioning assistance data via LPPa for broadcast | RAN WG3 | imported from 3GU |
| S2‑186318 | LS from RAN WG3: Reply LS on TAI and forbidden TAI List for 5GS | RAN WG3 | imported from 3GU |
| S2‑186319 | LS from CT WG4: LS on Service Area Restrictions | CT WG4 | imported from 3GU |
| S2‑186320 | LS from SA WG1: Reply LS on Delay Tolerant Access and Low Access Priority in 5GS | SA WG1 | imported from 3GU |
| S2‑186321 | LS from SA WG3: Security solution for encryption of broadcast positioning information | SA WG3 | imported from 3GU |
| S2‑186322 | LS from SA WG3: Reply LS on UE capability related to integrity protection of DRBs | SA WG3 | imported from 3GU |
| S2‑186323 | LS from SA WG3: LS response on Initial NAS message protection | SA WG3 | imported from 3GU |
| S2‑186324 | LS from SA WG3: LS on TLS and inter PLMN routing | SA WG3 | imported from 3GU |
| S2‑186325 | LS from CT WG1: Reply LS on initial NAS message protection | CT WG1 | imported from 3GU |
| S2‑186326 | LS from CT WG1: LS on UE policy | CT WG1 | imported from 3GU |
| S2‑186327 | LS from CT WG4: LS OUT on N16 Communication Failure | CT WG4 | imported from 3GU |
| S2‑186328 | LS from CT WG4: LS on the use of PGW FQDN in the SMF Selection | CT WG4 | imported from 3GU |
| S2‑186329 | LS from CT WG4: Reply LS on AUSF/UDM instance selection and SUCI parameters | CT WG4 | imported from 3GU |
| S2‑186330 | LS from CT WG4: LS Reply on Overload Control of Service Based Interfaces | CT WG4 | imported from 3GU |
| S2‑186331 | LS from RAN WG3: LS on RAN initiated TNL Associations over NGAP | RAN WG3 | imported from 3GU |
| S2‑186332 | LS from RAN WG3: LS on signalling of dynamic 5QI values | RAN WG3 | imported from 3GU |
| S2‑186333 | LS from RAN WG3: LS on Location Reporting for Area of Interest | RAN WG3 | imported from 3GU |
| S2‑186334 | LS from RAN WG3: Reply LS on Allowed NSSAI indication to RAN | RAN WG3 | imported from 3GU |
| S2‑186335 | LS from RAN WG3: LS on Radio Capability Check for IMS Voice | RAN WG3 | imported from 3GU |
| S2‑186336 | LS from SA WG3: LS response on Initial NAS message protection | SA WG3 | imported from 3GU |
| S2‑186337 | LS from RAN WG2: LS on LMF determination that the UE is served by NR | RAN WG2 | imported from 3GU |
| S2‑186338 | LS from RAN WG2: Reply LS on Reply LS on coexistence between RRC inactive and dual connectivity | RAN WG2 | imported from 3GU |
| S2‑186339 | LS from RAN WG2: LS on Connection Control | RAN WG2 | imported from 3GU |
| S2‑186340 | LS from RAN WG2: Reply LS on inclusion of NSSAI information during Inactive to connected mode transition | RAN WG2 | imported from 3GU |
| S2‑186341 | LS from CT WG3: LS on clarification for spending limit control functionality | CT WG3 | imported from 3GU |
| S2‑186342 | Update to Solution 33 Delayed paging response | Sony, NEC | imported from 3GU |
| S2‑186343 | Evaluation of Solution 6 | Sony | imported from 3GU |
| S2‑186344 | New Key Issue: Recommendations produced by NWDAF | ORANGE | imported from 3GU |
| S2‑186345 | New Solution: Recommendations produced by NWDAF | ORANGE | imported from 3GU |
| S2‑186346 | New Solution to Key Issue #3: Data Collection by subscription to NFs/AFs | Orange | imported from 3GU |
| S2‑186347 | Solution 2 update: Content of Network Data Analytics Feedback | ORANGE | imported from 3GU |
| S2‑186348 | Essential correction and clarification about user preference for URSP | KDDI, Orange, Telecom Italia | imported from 3GU |
| S2‑186349 | Correction of SMF initiated Session Management Policy Modification for Background data transfer | KDDI | imported from 3GU |
| S2‑186350 | Missing TADs behaviour | BlackBerry UK Limited | imported from 3GU |
| S2‑186351 | Change OCS to CHF | KDDI | imported from 3GU |
| S2‑186352 | Periodic TAU/RAU Timer negotiation with PSM | ORANGE | imported from 3GU |
| S2‑186353 | Evaluation Criteria for ATSSS | Deutsche Telekom | imported from 3GU |
| S2‑186354 | Completing solution 33 | Qualcomm Incorporated | imported from 3GU |
| S2‑186355 | Definition of Primary PLMN ID | ORANGE | imported from 3GU |
| S2‑186356 | Update of Key Issue 10 | AT&T | imported from 3GU |
| S2‑186357 | NWDAF related corrections to TR 23.791 | AT&T | imported from 3GU |
| S2‑186358 | Negotiation of long periodic TAU timer value | ORANGE, Telecom Italia | imported from 3GU |
| S2‑186359 | Negotiation of long periodic RAU timer value | ORANGE, Telecom Italia | imported from 3GU |
| S2‑186360 | Enforcement of Mutually Exclusive Access to Network Slices | Telecom Italia | imported from 3GU |
| S2‑186361 | Correction to SMF registeration of PDU Session ID | Telecom Italia, KDDI, ZTE | imported from 3GU |
| S2‑186362 | Correction to handling of DNNs not supported by the network | Telecom Italia | imported from 3GU |
| S2‑186363 | Proposed skeleton for FS_UDICOM | Vodafone | imported from 3GU |
| S2‑186364 | LS from CT WG6: Reply LS on SoR mechanism | CT WG6 | imported from 3GU |
| S2‑186365 | LS from RAN WG1: Reply LS on PC5 transmission mechanism selection | RAN WG1 | imported from 3GU |
| S2‑186366 | LS from TSG SA: LS on Guidance on Way Forward for Steering of Roaming | TSG SA | imported from 3GU |
| S2‑186367 | Reserved for LS In | MCC | imported from 3GU |
| S2‑186368 | Reserved for LS In | MCC | imported from 3GU |
| S2‑186369 | Scope of FS_UDICOM, 23.732 | Vodafone | imported from 3GU |
| S2‑186370 | Enhancements to Dual Registration mode of operation | Intel | imported from 3GU |
| S2‑186371 | Enhancements to Dual Registration mode of operation | Intel | imported from 3GU |
| S2‑186372 | Enhancements to Dual Registration mode of operation | Intel | imported from 3GU |
| S2‑186373 | Enhancements to Dual Registration mode of operation | Intel | imported from 3GU |
| S2‑186374 | UE Radio Capability Update using TAU procedure | Intel | imported from 3GU |
| S2‑186375 | Further correction to identifiers in Registration procedure | Intel | imported from 3GU |
| S2‑186376 | Further correction to identifiers in Registration procedure | Intel | imported from 3GU |
| S2‑186377 | Reply LS on initial NAS message protection | Intel | imported from 3GU |
| S2‑186378 | Mandatory valid lifetime configuration for old IP prefix in multi-homing | Intel, InerDigital Inc. | imported from 3GU |
| S2‑186379 | MME handling of UE 5GMM capability | Intel | imported from 3GU |
| S2‑186380 | Key Issues on FS_RACS | Intel | imported from 3GU |
| S2‑186381 | Solution on key issues for FS_RACS | Intel | imported from 3GU |
| S2‑186382 | 5GS Temporary Identifier aspects | Ericsson | imported from 3GU |
| S2‑186383 | Temporary identifier coordination | Ericsson | imported from 3GU |
| S2‑186384 | Temporary identitier usage at interworking | Ericsson | imported from 3GU |
| S2‑186385 | Requested NSSAI in Network Initiated Change of Network slices. | Ericsson | imported from 3GU |
| S2‑186386 | Requested NSSAI in access stratum | Ericsson | imported from 3GU |
| S2‑186387 | Network Slicing Subscription Change Indication | Ericsson | imported from 3GU |
| S2‑186388 | Correcting handling of RAT restriction and Forbidden Areas | Ericsson | imported from 3GU |
| S2‑186389 | Triggers for Network Triggered Service Request and UE Activity procedure | Ericsson | imported from 3GU |
| S2‑186390 | KI1: Solution 19 improvement | Ericsson | imported from 3GU |
| S2‑186391 | KI3: MT signalling for power saving UE | Ericsson | imported from 3GU |
| S2‑186392 | KI3: Paging of power saving UEs | Ericsson | imported from 3GU |
| S2‑186393 | KI13: Update to KI#13 | Ericsson | imported from 3GU |
| S2‑186394 | KI13: Local RRM Policy UE Differentiation | Ericsson | imported from 3GU |
| S2‑186395 | Solution 7 improvement | Ericsson | imported from 3GU |
| S2‑186396 | Enhancement of network event reporting | Ericsson | imported from 3GU |
| S2‑186397 | AMF selection for 5WWC | Ericsson | imported from 3GU |
| S2‑186398 | SM procedures for 5WWC | Ericsson | imported from 3GU |
| S2‑186399 | MM procedures for 5WWC | Ericsson | imported from 3GU |
| S2‑186400 | Mobility Restrictions for 5WWC | Ericsson | imported from 3GU |
| S2‑186401 | Updates to solution #11 “Support 3GPP UEs via 5G-RG/FN-RG for wireline access network using N3GPP solutions” | Ericsson | imported from 3GU |
| S2‑186402 | Update to Solution 6 to Key issue #EPC-3 and #EPC-4 to enable VoLTE calls after initial attachment | Ericsson | imported from 3GU |
| S2‑186403 | Handling of IMS Registration for RLOS UEs | Ericsson | imported from 3GU |
| S2‑186404 | Introduction of SBI-based SMSGW in 5GC | Ericsson | imported from 3GU |
| S2‑186405 | Supported positioning methods | Ericsson | imported from 3GU |
| S2‑186406 | Solution to allow Authentication for RLOS attached UE and update to Solution #8 | Ericsson | imported from 3GU |
| S2‑186407 | LS on Authentication for RLOS EPS Attach | Ericsson | imported from 3GU |
| S2‑186408 | Solution to Key Issue #EPC-4 | Ericsson | imported from 3GU |
| S2‑186409 | Solution to Key issue #3 QoS Support for eV2X over Uu interface | Ericsson | imported from 3GU |
| S2‑186410 | 5GS to EPS Mobility without N26 | Ericsson | imported from 3GU |
| S2‑186411 | EPS to 5GS mobility with N26 | Ericsson | imported from 3GU |
| S2‑186412 | eSBA - Interoperability aspects in key issue 6 | Ericsson | imported from 3GU |
| S2‑186413 | Solution proposal “Flexible Service Framework” to address key issue “Improvements to service framework related aspects | Ericsson | imported from 3GU |
| S2‑186414 | Solution proposal “hierarchical service framework” to address key issue “Improvements to service framework related aspects” | Ericsson | imported from 3GU |
| S2‑186415 | Solution proposal “improvements to the service framework” to address key issue “Improvements to service framework related aspects | Ericsson | imported from 3GU |
| S2‑186416 | New issue on roaming | Ericsson | imported from 3GU |
| S2‑186417 | Service framework requirements | Ericsson | imported from 3GU |
| S2‑186418 | Update of the Service Instance Set solution | Ericsson | imported from 3GU |
| S2‑186419 | An overview of the IETF DetNet activity | Ericsson | imported from 3GU |
| S2‑186420 | Anchor change for Ethernet PDU Sessions | Ericsson | imported from 3GU |
| S2‑186421 | Updates to Solution #1 on Redundant user plane paths based on dual connectivity | Ericsson | imported from 3GU |
| S2‑186422 | Updates to solution #2 on Multiple UEs per device for user plane redundancy | Ericsson | imported from 3GU |
| S2‑186423 | Discovering SMF instance at EPS to 5GS interworking | Ericsson | imported from 3GU |
| S2‑186424 | [DRAFT] Reply LS on the use of PGW FQDN in the SMF Selection | Ericsson | imported from 3GU |
| S2‑186425 | User preference over Route Selection Descriptor | Samsung, Intel | imported from 3GU |
| S2‑186426 | Correction for UE requested LADN Information | Samsung, Intel | imported from 3GU |
| S2‑186427 | Clarification on LADN | Samsung | imported from 3GU |
| S2‑186428 | Clarification on a wildcard DNN | Samsung | imported from 3GU |
| S2‑186429 | Update of Solution 3.1 “Amendments to Service Interaction model” to address editors notes | Deutsche Telekom | imported from 3GU |
| S2‑186430 | Update of Solution 4.1 - SBA with stateless and unsticky services to address editors notes | Deutsche Telekom | imported from 3GU |
| S2‑186431 | Support for VLAN ID learning to enable IEEE 802.1CB (Frame Replication and Elimination for Reliability) combined with IEEE 802.1Q | Qualcomm Incorporated | imported from 3GU |
| S2‑186432 | Solution on UE radio capabilities signalling optimizations | Deutsche Telekom | imported from 3GU |
| S2‑186433 | Clarification of Network area information for BDT in order to align with TS23.203. | KDDI, TOYOTA ITC | imported from 3GU |
| S2‑186434 | Update to Solution 32: MO Data Buffering in the UE | NEC, Convida Wireless LLC | imported from 3GU |
| S2‑186435 | Combining RRC-INACTIVE and 5G UP optimization for efficient handling of bursty frequent small data | Qualcomm Incorporated | imported from 3GU |
| S2‑186436 | Solution 2: Update of Combined Establishment | Motorola Mobility, Lenovo | imported from 3GU |
| S2‑186437 | Update of Solution #11: Support 5GC-capable UEs via 5G-RG/FN-RG for wireline access network using N3GPP solutions | Motorola Mobility, Lenovo | imported from 3GU |
| S2‑186438 | Update of Solution #3: Access to 5GC from UEs without supporting NAS on non-3GPP access | Motorola Mobility, Lenovo | imported from 3GU |
| S2‑186439 | Consolidated ATSSS Solution | Motorola Mobility, Lenovo | imported from 3GU |
| S2‑186440 | An addition to Key Issue 2 | AT&T, Sprint | imported from 3GU |
| S2‑186441 | Clarifying RAI handling | Qualcomm Incorporated | imported from 3GU |
| S2‑186442 | Correcting use of identifiers during registration in equivalent PLMNs | Qualcomm Europe Inc.(France) | imported from 3GU |
| S2‑186443 | Correcting use of identifiers during registration in equivalent PLMNs | Qualcomm Incorporated | imported from 3GU |
| S2‑186444 | Architectural updates for ATSSS Solution 1 | BROADCOM CORPORATION | imported from 3GU |
| S2‑186445 | Clarification on the establishment procedure of proxyied MPTCP connections | Orange | imported from 3GU |
| S2‑186446 | New solution: NWDAF service to provide recommendation for NF instance selection | KDDI | imported from 3GU |
| S2‑186447 | Updates to Solution 5 | Cisco Systems Belgium | imported from 3GU |
| S2‑186448 | MO service correction | BlackBerry UK Limited | imported from 3GU |
| S2‑186449 | Reply LS on Access Restriction Data for NR in EPC | Cisco Systems Belgium | imported from 3GU |
| S2‑186450 | TR 23.740: eNS TR update on scope and references | ZTE Wistron | imported from 3GU |
| S2‑186451 | TR 23.740: Solution for supporting the mutually exclusive access slices via the extension of S-NSSAI | ZTE Wistron | imported from 3GU |
| S2‑186452 | TR 23.793: MPTCP Proxy Selection Policy and miscellaneous changes | ZTE Wistron | imported from 3GU |
| S2‑186453 | Handling of subscription restrictions for mobility from EPS to 5GS | Cisco Systems Belgium | imported from 3GU |
| S2‑186454 | Storage of structured proprietory data in UDSF | Deutsche Telekom | imported from 3GU |
| S2‑186455 | Update of parameter in call flow and service operation for NSI ID | KDDI, Telecom Italia, ZTE Wistron, ETRI | imported from 3GU |
| S2‑186456 | Update of UPF selection factor for network slice instance | KDDI, ETRI, ZTE Wistron | imported from 3GU |
| S2‑186457 | Update of UPF selection factor for network slice instance | KDDI | imported from 3GU |
| S2‑186458 | Solution Update-Update Solution 33 | OPPO | imported from 3GU |
| S2‑186459 | Solution for KI 5-Network controlled UL data transmission delay | OPPO | imported from 3GU |
| S2‑186460 | Solution Update-Update Solution 1 | OPPO | imported from 3GU |
| S2‑186461 | Update ATSSS procedure for TFCP solution | OPPO, Huawei | imported from 3GU |
| S2‑186462 | New Key Issue: Support Back-forward Compatibility | OPPO | imported from 3GU |
| S2‑186463 | New Key Issue: Support Multiple PLMNs and Network Sharing | OPPO | imported from 3GU |
| S2‑186464 | Solution to Key Issue 9 | Ericsson Inc. | imported from 3GU |
| S2‑186465 | PDU Session selection | InterDigital Inc. | imported from 3GU |
| S2‑186466 | Solution 2 Update: Modifying Multi-access PDU Session as single-access PDU | InterDigital Inc. | imported from 3GU |
| S2‑186467 | NAS based Solution for KI#15 | NTT DOCOMO | imported from 3GU |
| S2‑186468 | RRC based Solution for KI#15 | NTT DOCOMO | imported from 3GU |
| S2‑186469 | Clarification on UE context exchanged on N26 interface | NTT DOCOMO | imported from 3GU |
| S2‑186470 | TR Skeleton for study on architecture aspects for using satellite access in 5G | THALES | imported from 3GU |
| S2‑186471 | References for FS_5GSAT_ARCH TR | THALES | imported from 3GU |
| S2‑186472 | Scope of FS_5GSAT_ARCH TR | THALES | imported from 3GU |
| S2‑186473 | Satellite system characteristics to be included in FS_5GSAT_ARCH TR | THALES | imported from 3GU |
| S2‑186474 | Reference Satellite Integration Architectures for FS_5GSAT_ARCH TR | THALES | imported from 3GU |
| S2‑186475 | Architectural assumptions for Mutually Exclusive Access to Network Slices | Huawei, HiSilicon | imported from 3GU |
| S2‑186476 | Solutions for Mutually Exclusive Access to Network Slices | Huawei, HiSilicon | imported from 3GU |
| S2‑186477 | On terminology for SBA | Huawei, HiSilicon | imported from 3GU |
| S2‑186478 | Correction to AF influence on traffic routing | Huawei, HiSilicon | imported from 3GU |
| S2‑186479 | Corrections to AF influence on traffic routing | Huawei, HiSilicon | imported from 3GU |
| S2‑186480 | TS 23.502: updates for the UE Configured NSSAI update procedure | Huawei, HiSilicon | imported from 3GU |
| S2‑186481 | Clarification on UE Registration type with only PDU Session for Emergency Services | Huawei, HiSilicon | imported from 3GU |
| S2‑186482 | Solution for KI#3: AF Response to UP Path Management Event Notifications | Huawei, HiSilicon | imported from 3GU |
| S2‑186483 | Update of solution #3 and solution #4 | Huawei, HiSilicon | imported from 3GU |
| S2‑186484 | Update of solution #5 | Huawei, HiSilicon | imported from 3GU |
| S2‑186485 | [draft] LS reply to LS on clarification for spending limit control functionality | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186486 | [Draft] LS reply to LS on UE policy | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186487 | 23502 AMF-PCF Association termination | Huawei, HiSilicon | imported from 3GU |
| S2‑186488 | Discussion on AMF-PCF Association Termination | Huawei, HiSilicon | imported from 3GU |
| S2‑186489 | The resource type of QoS Flow associated with the default QoS rule | Huawei, HiSilicon | imported from 3GU |
| S2‑186490 | 23502 UE Policy Delivery in case of UE not reachable | Huawei, HiSilicon | imported from 3GU |
| S2‑186491 | 23503 UE Policy Delivery in case of UE not reachable | Huawei, HiSilicon | imported from 3GU |
| S2‑186492 | Updates for LMF selection criteria | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186493 | Support of tracing in 5GS signalling: overview | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186494 | Support of tracing in 5GS signalling: SM related signalling and data | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186495 | Support of tracing in 5GS signalling: SMSF related signalling and data | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186496 | User Location Information added in N2 UE Context Release Complete | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186497 | Update of Solution #1: Support of Trusted Non-3GPP Access | Motorola Mobility, Lenovo, Broadcom | imported from 3GU |
| S2‑186498 | Further clarification for distributed service framework | China Mobile | imported from 3GU |
| S2‑186499 | Support of tracing in 5GS signalling: PCF related signalling and data (SM part) | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186500 | UPF service introduced in SBA | China Mobile | imported from 3GU |
| S2‑186501 | Common Network Data Service | China Mobile | imported from 3GU |
| S2‑186502 | MCC implementation correction of 23.501 CR0255R7 | MCC | imported from 3GU |
| S2‑186503 | Correction of descriptions (OCS and Traffic filter for URSP) in TS 23.503 | KDDI | imported from 3GU |
| S2‑186504 | UPF selection factor | China Telecom | imported from 3GU |
| S2‑186505 | Clarification on the SSC mode be supported between 5GS and EPS IWK | China Telecom | imported from 3GU |
| S2‑186506 | Clarification to UE Configuration Update | LG Electronics | imported from 3GU |
| S2‑186507 | Clarification on CN-initiated selective deactivation of UP connection | LG Electronics | imported from 3GU |
| S2‑186508 | Clarification on LADN DNN(s) configured in AMF | LG Electronics | imported from 3GU |
| S2‑186509 | Documentation of IWK-NEF in TR 23.724 | Qualcomm Incorporated, Convida Wireless, AT&T | imported from 3GU |
| S2‑186510 | Optionality of SMF selection for small data solution 2 | China Mobile | imported from 3GU |
| S2‑186511 | Definitions, architectural assumptions and key issue related to network identification, selection and access control | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186512 | Clarification on UE policy configuration | OPPO | imported from 3GU |
| S2‑186513 | Discussion on UE policy configuration | OPPO | imported from 3GU |
| S2‑186514 | Clarification on User preference URSP | OPPO | imported from 3GU |
| S2‑186515 | The proposal for subscribed PTW length using Network Parameter Configuration procedure via SCEF | China Mobile | imported from 3GU |
| S2‑186516 | Updating for solution#5 in FS_URLLC | OPPO | imported from 3GU |
| S2‑186517 | 23.716 solutions: small update to Solution #9 - new IPV6 address allocation mechanisms | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186518 | 23.716 new solutions: Subscription control for the Support of a range of IP address/Prefixes in a PDU Session | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186519 | Clarification on UE configuration update procedure | OPPO | imported from 3GU |
| S2‑186520 | The proposal for subscribed PTW length | China Mobile | imported from 3GU |
| S2‑186521 | Selection of target AMF in EPS to 5GS handover procedure using N26 | China Mobile | imported from 3GU |
| S2‑186522 | Solution for infrequent small data transmission with temporary PDU session | China Mobile | imported from 3GU |
| S2‑186523 | TR 23.716: Updates to Architectural Requirements | OTD, Charter | imported from 3GU |
| S2‑186524 | TR 23.716: Updates to Architectural Requirements | OTD, Charter | imported from 3GU |
| S2‑186525 | Solution for Key Issue 5 | Sony | imported from 3GU |
| S2‑186526 | Corrections for ARP priority level | Huawei, HiSilicon | imported from 3GU |
| S2‑186527 | Corrections for low latency QCIs | Huawei, HiSilicon | imported from 3GU |
| S2‑186528 | 5QI priority level overwriting for nonGBR | Huawei, HiSilicon | imported from 3GU |
| S2‑186529 | Clarifications for 5QI priority level overwriting | Huawei, HiSilicon | imported from 3GU |
| S2‑186530 | 5QI-QCI alignment | Huawei, HiSilicon | imported from 3GU |
| S2‑186531 | Number of packet filters supported by UE | Huawei, HiSilicon | imported from 3GU |
| S2‑186532 | Number of packet filters supported by UE | Huawei, HiSilicon | imported from 3GU |
| S2‑186533 | Paging policy differentiation for RRC inactive | Huawei, HiSilicon | imported from 3GU |
| S2‑186534 | Way forward on UE differentiation | Qualcomm Incorporated, Nokia, Deutsche Telekom, Orange | imported from 3GU |
| S2‑186535 | RAN-modified CN assistance parameters | Qualcomm Incorporated, Nokia, Deutsche Telekom, Orange | imported from 3GU |
| S2‑186536 | Cleanup of Broadcast of Assistance Data for E-UTRAN | Qualcomm Incorporated, Ericsson | imported from 3GU |
| S2‑186537 | Storage of permanent identities for private networks | Qualcomm Incorporated | imported from 3GU |
| S2‑186538 | Introducing low access priority to 5G system | Qualcomm Incorporated | imported from 3GU |
| S2‑186539 | On signalling dynamic 5QI values | Qualcomm Incorporated | imported from 3GU |
| S2‑186540 | [DRAFT] Reply LS on signalling of dynamic 5QI values | Qualcomm Incorporated | imported from 3GU |
| S2‑186541 | Corrections in Reachability procedures | Qualcomm Incorporated | imported from 3GU |
| S2‑186542 | On congestion control for PaRLOS | Qualcomm Incorporated | imported from 3GU |
| S2‑186543 | Evaluation and conclusion for Key Issue EPC-1 | Qualcomm Incorporated | imported from 3GU |
| S2‑186544 | Evaluation and conclusion for Key Issue EPC-2 | Qualcomm Incorporated | imported from 3GU |
| S2‑186545 | TR 23.743 skeleton | Qualcomm Incorporated | imported from 3GU |
| S2‑186546 | Scope of the TR for the study on optimisations on UE radio capability signalling | Qualcomm Incorporated | imported from 3GU |
| S2‑186547 | Key issue to determine how are the UE capabilities identified | Qualcomm Incorporated, Mediatek, Intel | imported from 3GU |
| S2‑186548 | Key issue to determine where are the UE radio capabilities stored | Qualcomm Incorporated, Mediatek, Intel | imported from 3GU |
| S2‑186549 | Key issue to determine procedures for UE radio capabilities management | Qualcomm Incorporated, Mediatek, Intel | imported from 3GU |
| S2‑186550 | Solution for how are the UE radio capabilities identified | Qualcomm Incorporated | imported from 3GU |
| S2‑186551 | Solution for how are the UE radio capabilities managed and signalled | Qualcomm Incorporated | imported from 3GU |
| S2‑186552 | Application detection report when the PFDs are removed | Huawei, HiSilicon | imported from 3GU |
| S2‑186553 | Application detection report when the PFDs are removed | Huawei, HiSilicon | imported from 3GU |
| S2‑186554 | Application detection report when the PFDs are removed | Huawei, HiSilicon | imported from 3GU |
| S2‑186555 | Application detection report when the PFDs are removed | Huawei, HiSilicon | imported from 3GU |
| S2‑186556 | Correction to the procedure of PFD Retrieval by the SMF | Huawei, HiSilicon | imported from 3GU |
| S2‑186557 | Clarification on access network information during IMS call in 5G dual connectivity scenario | Huawei, HiSilicon | imported from 3GU |
| S2‑186558 | Deployment Option for NF Discovery and Selection | Huawei, HiSilicon | imported from 3GU |
| S2‑186559 | Alignment on the Namf_EventExposure_Subscribe service operation | Huawei, HiSilicon | imported from 3GU |
| S2‑186560 | PCF added as consumer of EventExposure service of AMF and SMF | Huawei, HiSilicon | imported from 3GU |
| S2‑186561 | Update of TFCP solution | Huawei, HiSilicon | imported from 3GU |
| S2‑186562 | Editorial correction for TFCP solution | Huawei, HiSilicon | imported from 3GU |
| S2‑186563 | ATSSS path performance measurement function | Huawei, HiSilicon | imported from 3GU |
| S2‑186564 | Fix the leftover FFS for Solution #4 | Vivo | imported from 3GU |
| S2‑186565 | Overall evaluation of solutions for Key Issue#3 | Vivo | imported from 3GU |
| S2‑186566 | Evaluation of Solution5: Privacy Check procedure | Vivo | imported from 3GU |
| S2‑186567 | Key issue: Architecture of vertical LAN | Vivo | imported from 3GU |
| S2‑186568 | Correction on mobility management back-off timer | vivo | imported from 3GU |
| S2‑186569 | Update of ATSSS solution #6 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186570 | Update of solution #4 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186571 | Update of solution #5 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186572 | Update of solution #10 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186573 | Evaluation of solutions and conclusions related to Key Issues # IMS-1, # IMS-2 and # IMS-3 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186574 | Update of Solution 23 - MICO Mode Management for Expected Application Behaviour | Huawei, HiSilicon, SK Telecom | imported from 3GU |
| S2‑186575 | The interaction between vPCF and vUDR | Huawei, HiSilicon | imported from 3GU |
| S2‑186576 | The interaction between vPCF and vUDR | Huawei, HiSilicon | imported from 3GU |
| S2‑186577 | Discussion on the interaction between vPCF and vUDR | Huawei, HiSilicon | imported from 3GU |
| S2‑186578 | Specific QoS & Policy control for URLLC services | Huawei, HiSilicon | imported from 3GU |
| S2‑186579 | Architectural Assumptions: RLOS access to authenticated UEs | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186580 | Correction on Connection Resume procedure | Huawei, HiSilicon | imported from 3GU |
| S2‑186581 | Correction on signalling message holding during HO | Huawei, HiSilicon | imported from 3GU |
| S2‑186582 | UE location report to the SMF by RAN in RRC Inactive State | Huawei, HiSilicon | imported from 3GU |
| S2‑186583 | Solution for KI2: Default GBR QoS Flow | Huawei, HiSilicon | imported from 3GU |
| S2‑186584 | Clarification on UE Capability Match Request procedure | LG Electronics | imported from 3GU |
| S2‑186585 | Fixing clause number | LG Electronics | imported from 3GU |
| S2‑186586 | Solution to key issue#10 for non-IP based V2X message transmission and reception over Uu | LG Electronics, NTT DOCOMO | imported from 3GU |
| S2‑186587 | Update of Solution#6 | LG Electronics | imported from 3GU |
| S2‑186588 | Correction to Configured NSSAI for the HPLMN | MediaTek Inc. | imported from 3GU |
| S2‑186589 | Correction to TAI list generation | MediaTek Inc. | imported from 3GU |
| S2‑186590 | Service Accept to complete Service Request | MediaTek Inc. | imported from 3GU |
| S2‑186591 | Clarification on PPD for RRC inactive state | ZTE | imported from 3GU |
| S2‑186592 | Clarifications on N2 based handover | ZTE | imported from 3GU |
| S2‑186593 | Clarifications on Xn based handover | ZTE | imported from 3GU |
| S2‑186594 | Network Function Repository Function | ZTE | imported from 3GU |
| S2‑186595 | Add missing event for Nsmf_EventExposure Service | ZTE | imported from 3GU |
| S2‑186596 | Removal PCC policy for Routing rules configuration | ZTE | imported from 3GU |
| S2‑186597 | Removal Internal group ID from the input parameter in Npcf_AMPolicyControl_Create service | ZTE | imported from 3GU |
| S2‑186598 | Clarification on AM Policy Association termination | ZTE | imported from 3GU |
| S2‑186599 | Correct the figure in clause 4.16.4 SM Policy Association Establishment | ZTE | imported from 3GU |
| S2‑186600 | QoS flow handling for Multi-Access PDU session | ZTE | imported from 3GU |
| S2‑186601 | Solution for Key issue#2: Enabling interworking for slicing between EPC and 5GC | ZTE | imported from 3GU |
| S2‑186602 | Update for Solution 5: Small Data Fast Path communication | ZTE | imported from 3GU |
| S2‑186603 | L-SMF clarification for solution 16: I-UPF insertion and L-SMF/L-UPF selection | ZTE | imported from 3GU |
| S2‑186604 | Adding charging aspects and other updates to solution 14 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186605 | Discussion on UE policy management and distribution | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186606 | Update to UE policy distribution | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186607 | Update for UE policy provision and update | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186608 | Network Exposure in Roaming Situations | Convida Wireless LLC, AT&T, Intel | imported from 3GU |
| S2‑186609 | Evaluation and conclusion for KI#1 and KI#2 | China Unicom, vivo, Huawei, CAICT, CATT, ZTE, OPPO, Intel, Qualcomm, Lenovo, Motorola Mobility, MediaTek Inc | imported from 3GU |
| S2‑186610 | KI on Slice Specific Authentication and Authorization using non 3GPP credentials | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186611 | Concluding Key Issue #9 | Convida Wireless LLC, AT&T, Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186612 | Mutual Exclusion among slices solution | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186613 | Slice Specific Authentication and Authorization using non 3GPP credentials - Solution | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186614 | Editorial Fixes to the UECM Text | Convida Wireless LLC | imported from 3GU |
| S2‑186615 | AMF to PCF interactions in the UE Configuration Update for UE policy delivery procedure | Ericsson | imported from 3GU |
| S2‑186616 | Policy Control Request triggers for updating the AM Policy Association | Ericsson | imported from 3GU |
| S2‑186617 | Termination of the AM Policy Association | Ericsson | imported from 3GU |
| S2‑186618 | Solution to KI#7: NWDAF assisting Future Background Data Transfer | Ericsson | imported from 3GU |
| S2‑186619 | Discussion on the BEST Protocol | Convida Wireless LLC | imported from 3GU |
| S2‑186620 | V2X reference architecture | Ericsson, CATT, Samsung | imported from 3GU |
| S2‑186621 | Update of solution #3 | Ericsson, Samsung | imported from 3GU |
| S2‑186622 | Unicast media delivery for 5WWC | Ericsson | imported from 3GU |
| S2‑186623 | [DRAFT] Reply LS on new BEST Service | Convida Wireless LLC | imported from 3GU |
| S2‑186624 | Discussion and New Key Issues for Objective 1 | Convida Wireless LLC, Qualcomm, AT&T, Intel, Verizon UK Ltd | imported from 3GU |
| S2‑186625 | Updated SID on User Data Interworking, Coexistence and Migration | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186626 | On the Configured NSSAI valid for all PLMNs | Nokia, Nokia Shanghai Bell, Telecom Italia, Mediatek, ZTE Wistron, Huawei, Intel | imported from 3GU |
| S2‑186627 | New solution for UL-CL/BP Insertion with UPF that is capable to flexibly interface any SMF | Ericsson | imported from 3GU |
| S2‑186628 | Handling of UP Security Policy when IWK with EPS | Ericsson | imported from 3GU |
| S2‑186629 | Removal of the Configured NSSAI valid for all PLMNs | Nokia, Nokia Shanghai Bell, Telecom Italia, Mediatek, ZTE Wistron, Huawei, Intel | imported from 3GU |
| S2‑186630 | Configured NSSAI update | Ericsson | imported from 3GU |
| S2‑186631 | Configured NSSAI update | Ericsson | imported from 3GU |
| S2‑186632 | Correction to AS security handling in registration procedure | Ericsson | imported from 3GU |
| S2‑186633 | Priority Level signalled with standardized 5QIs and QoS characteristics signalled with dynamically assigned 5QIs. | Vencore Labs, OEC, AT&T, T-Mobile USA, Sprint | imported from 3GU |
| S2‑186634 | N28 session termination | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186635 | Adding N28 session termination procedure and updates to CHF services | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186636 | Correction to Service Request QoS when changing between non-3GPP and 3GPP accesses | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186637 | Relationship between type-a networks and PLMNs | Qualcomm Incorporated | imported from 3GU |
| S2‑186638 | Update to Registration procedure with AMF relocation | InterDigital Inc. | imported from 3GU |
| S2‑186639 | An addition of a new Key Issue on Network Status | AT&T | imported from 3GU |
| S2‑186640 | Clarification on handling of Ethernet frames at UPF | Qualcomm Incorporated | imported from 3GU |
| S2‑186641 | Discussion on UE policy update and enforcement handling | Qualcomm Incorporated, | imported from 3GU |
| S2‑186642 | Impacts Update to Solution 32: MO Data Buffering in the UE | NEC, Convida Wireless LLC | imported from 3GU |
| S2‑186643 | URSP updates and Application to PDU session association re-evaluation | Qualcomm Incorporated | imported from 3GU |
| S2‑186644 | Key Issues for FS_5GSAT_ARCH TR | Thales | imported from 3GU |
| S2‑186645 | [DRAFT] Reply LS on UE policy | Qualcomm Incorporated | imported from 3GU |
| S2‑186646 | [DRAFT] Reply LS on LMF determination that the UE is served by NR | Qualcomm Incorporated | imported from 3GU |
| S2‑186647 | Update to solution for eV2X system migrations | Qualcomm Incorporated, Huawei, HiSilicon | imported from 3GU |
| S2‑186648 | EV2X QoS Support of PC5 communications | Qualcomm Incorporated, | imported from 3GU |
| S2‑186649 | Enhancements to Solution 2 | Qualcomm Incorporated | imported from 3GU |
| S2‑186650 | Key Issue on Coexistence with the Location Solution in Release 15 | Qualcomm Incorporated | imported from 3GU |
| S2‑186651 | Support for Key Issue on Coexistence with the Location Solution in Release 15 | Qualcomm Incorporated | imported from 3GU |
| S2‑186652 | Support of Low Power Periodic and Triggered Location for Solution 2 using EDT | Qualcomm Incorporated | imported from 3GU |
| S2‑186653 | Introduce Early Data Transmission option to Solution 1 | Qualcomm Incorporated | imported from 3GU |
| S2‑186654 | New solution: Early Data Transmission with Immediate RRC completion | Qualcomm Incorporated | imported from 3GU |
| S2‑186655 | Solution to KI15: UE CN selection using broadcast information | Qualcomm Incorporated | imported from 3GU |
| S2‑186656 | Solution 19 clarifications | Qualcomm Incorporated | imported from 3GU |
| S2‑186657 | Distributed service framework | Oracle, Verizon | imported from 3GU |
| S2‑186658 | Discussion on eSBA key issue 3 | Oracle Corporation, Verizon | imported from 3GU |
| S2‑186659 | Final conclusions on Configured NSSAI not associated to any PLMNs | Qualcomm Incorporated | imported from 3GU |
| S2‑186660 | Completion of description on Configured NSSAIs | Qualcomm | imported from 3GU |
| S2‑186661 | IP address allocation | BlackBerry UK Limited | imported from 3GU |
| S2‑186662 | Modifications to Registration Procedure for initial NAS security support | Qualcomm | imported from 3GU |
| S2‑186663 | [DRAFT] Reply LS on initial NAS message protect | Qualcomm Austria RFFE GmbH | imported from 3GU |
| S2‑186664 | [DRAFT] Reply LS on GSMA question on 5G network slices | Qualcomm Austria RFFE GmbH | imported from 3GU |
| S2‑186665 | Solution for key issue #2 'Enabling interworking for slicing between EPC and 5GC' | Qualcomm Incorporated | imported from 3GU |
| S2‑186666 | Discussion on NWDAF interactions with OAM | Huawei, HiSilicon, CATR, Convida Wireless LLC, China Unicom, China Mobile, NTT DoCoMo? | imported from 3GU |
| S2‑186667 | [DRAFT] LS on Issues of OAM consuming analytics from NWDAF | Huawei, HiSilicon | imported from 3GU |
| S2‑186668 | Use Case and KI for NWDAF exposing analytics to OAM | Huawei, HiSilicon | imported from 3GU |
| S2‑186669 | Solution for Key Issue 4: Interactions with OAM for Network Data Collection | Huawei, HiSilicon, Telecom Italia, Orange | imported from 3GU |
| S2‑186670 | Update Solution 3: How to define the service experience | Huawei, HiSilicon, Convida Wireless LLC, AT&T, Telecom Italia | imported from 3GU |
| S2‑186671 | Update Solution for Key Issue 5: NWDAF-Assisted QoS Profile Provisioning | Huawei, HiSilicon | imported from 3GU |
| S2‑186672 | Solution for Key Issue 7: NWDAF assisting Future Background Data Transfer | Huawei, HiSilicon | imported from 3GU |
| S2‑186673 | Analytic Information Exposure to SMF for Traffic Handling | Huawei, HiSilicon, Convida Wireless LLC | imported from 3GU |
| S2‑186674 | Solution for Slice Specific Authentication and Authorization using non 3GPP credentials | Qualcomm Incorporated | imported from 3GU |
| S2‑186675 | Updates to ATSSS Solution 1 | NICT | imported from 3GU |
| S2‑186676 | Solution to QoS Profile Provisioning and adjustment | China Telecommunications | imported from 3GU |
| S2‑186677 | Correction of UE configuration update procedure | Intel, Apple, OPPO | imported from 3GU |
| S2‑186678 | LADN Clarification | Intel, Huawei, Samsung | imported from 3GU |
| S2‑186679 | DNN Usage Clarification | Intel | imported from 3GU |
| S2‑186680 | DNN Usage Clarification | Intel | imported from 3GU |
| S2‑186681 | Clarification on UE policy graceful enforcement period | Intel, Nokia, OPPO, SAMSUNG, Orange, KDDI, China Unicom, Apple | imported from 3GU |
| S2‑186682 | Clarification on ANDSP support | Intel | imported from 3GU |
| S2‑186683 | Clarification on initial UE policy provisioning | Intel | imported from 3GU |
| S2‑186684 | UE triggered UE policy provisioning procedure | Intel | imported from 3GU |
| S2‑186685 | EV2X Solution #4 update addressing key issue #11 | Intel, LG Electronics | imported from 3GU |
| S2‑186686 | EV2X Solution addressing key issue #12 based on Architecture in A.2 | Intel, LG Electronics | imported from 3GU |
| S2‑186687 | New key issue: Support 5G deployment option #3 | Intel | imported from 3GU |
| S2‑186688 | EV2X Conclusion for key issue #7 | Intel, LG Electronics?, Qualcomm?, Ericsson? | imported from 3GU |
| S2‑186689 | New solution on NWDAF influencing traffic routing | Intel | imported from 3GU |
| S2‑186690 | Update of solution #3 on returning UE from UTRAN to NG-RAN or E-UTRAN | Intel, Huawei | imported from 3GU |
| S2‑186691 | New solution on returning UE from UTRAN to NG-RAN or E-UTRAN with MSC and UTRAN impact | Intel, Huawei | imported from 3GU |
| S2‑186692 | Evaluation and conclusion of Solutions for Key issue 3 | Intel, Huawei | imported from 3GU |
| S2‑186693 | Notification Control applicability | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186694 | Status, Plans related to Enable Location Service in Rel-16 | CATT | imported from 3GU |
| S2‑186695 | Revised SID: Study on Enhancement to Service Based Architecture for Location Services | CATT, Qualcomm Incorporated, China Telecom, China Mobile, CAICT, China Unicom, Huawei, HiSilicon, Verizon UK Ltd?, ZTE, T-Mobile USA?, AT&T?, Nokia?, Nokia Shanghai Bell?, Ericsson?, Comtech Telecommunications?, Intel? | imported from 3GU |
| S2‑186696 | New Solution for KI#15: Location continuity for Handovers between 5GS and EPS | CATT | imported from 3GU |
| S2‑186697 | One Solution for Key Issue #2: Extend Service Concept into User Plane | CATT | imported from 3GU |
| S2‑186698 | Use Case NWDA-assisted autonomous traffic steering | China Telecom | imported from 3GU |
| S2‑186699 | Clarification for pre-configured QoS rule | CATT | imported from 3GU |
| S2‑186700 | Clarification for QoS handling at UPF | CATT | imported from 3GU |
| S2‑186701 | Indirect data forwarding for interworking with N26 | Samsung | imported from 3GU |
| S2‑186702 | UE support for dual registration mode interworking | Samsung, Verizon, SK Telecom, LG Electronics | imported from 3GU |
| S2‑186703 | AppId defintion | Samsung | imported from 3GU |
| S2‑186704 | Interim conclusion for Key issue #6 | Intel | imported from 3GU |
| S2‑186705 | Solution update and interim conclusion for Key issue #11: Monitoring | Intel | imported from 3GU |
| S2‑186706 | Solution for Key Issue #15: Core Network selection for Cellular IoT | Intel | imported from 3GU |
| S2‑186707 | Delay Tolerant Access and Low Access Priority in 5GS | Intel | imported from 3GU |
| S2‑186708 | [DRAFT] Reply LS on Delay Tolerant Access and Low Access Priority in 5GS | Intel | imported from 3GU |
| S2‑186709 | 2 New Key Issues for HSS UDR Interactions | T-Mobile USA INC | imported from 3GU |
| S2‑186710 | New Key Issue for signalling optimization | T-Mobile USA INC | imported from 3GU |
| S2‑186711 | Solution for Key Issue 8: Performance improvement and supervision of mIoT terminals | China Mobile | imported from 3GU |
| S2‑186712 | Discussion on DL signalling handling for non-3GPP PDU Session | LG Electronics | imported from 3GU |
| S2‑186713 | DL signalling handling for non-3GPP PDU Session | LG Electronics | imported from 3GU |
| S2‑186714 | [DRAFT] Reply LS on 5G service request procedure | LG Electronics | imported from 3GU |
| S2‑186715 | Access type notification to SMF in Service Request | LG Electronics | imported from 3GU |
| S2‑186716 | Clarification on AN parameters in N3GPP procedures | LG Electronics | imported from 3GU |
| S2‑186717 | Default IPsec tunnel for a PDU Session | LG Electronics | imported from 3GU |
| S2‑186718 | Clarification on SSC Mode Selection Policy | LG Electronics | imported from 3GU |
| S2‑186719 | Update Solution 8 - resolving editor's notes | LG Electronics | imported from 3GU |
| S2‑186720 | QoS handling in MA-PDU Session | LG Electronics | imported from 3GU |
| S2‑186721 | Solution for establishing N3 and N9 tunnels for redundant transmission | Samsung | imported from 3GU |
| S2‑186722 | Update the solution #4 | Samsung | imported from 3GU |
| S2‑186723 | Update on Key Issue #1 and #2 for analytic information metadata exposure to 5GS NFs and AFs | Samsung | imported from 3GU |
| S2‑186724 | A solution to provide the available analytic information metadata | Samsung | imported from 3GU |
| S2‑186725 | Correction on Establishing a PDU Session in a Network Slice | Samsung | imported from 3GU |
| S2‑186726 | Update on Key Issue #1 and #2 to allow the registration of a new analytic information definition by 5G NF and AF | Samsung | imported from 3GU |
| S2‑186727 | Clarification on the delivery of EBI to UE | Huawei, HiSilicon | imported from 3GU |
| S2‑186728 | Clafication on cancel registration with N26 | Huawei, HiSilicon | imported from 3GU |
| S2‑186729 | Clafication on cancel registration with N26 | Huawei, HiSilicon | imported from 3GU |
| S2‑186730 | Detailed description on user preference | Huawei, HiSilicon | imported from 3GU |
| S2‑186731 | A solution to register a new definition of analytic information provided by NWDAF | Samsung | imported from 3GU |
| S2‑186732 | Solution for KI15: Core Network selection for Cellular IOT | Huawei, HiSilicon | imported from 3GU |
| S2‑186733 | Solution on KI16: Support of Group Communication and Messaging | Huawei, HiSilicon | imported from 3GU |
| S2‑186734 | Update of Solution 26: Expected UE Behaviour provisioning for CIoT | Huawei, HiSilicon | imported from 3GU |
| S2‑186735 | Solution for KI3: UE availability after DDN failure for multiple Afs | Huawei, HiSilicon | imported from 3GU |
| S2‑186736 | Solution for K1 and K2: Packet Aggregation for Small Data Delivery | Huawei, HiSilicon, Convida Wireless LLC | imported from 3GU |
| S2‑186737 | Solution for KI1: Small Data transmission based on independently suspended and resumed PDU sessions | Huawei, HiSilicon | imported from 3GU |
| S2‑186738 | Solution for KI8: Reliable Data Service support in the SMF | Huawei, HiSilicon | imported from 3GU |
| S2‑186739 | Update of Solution 27: Reuse of EPS Overload Control Mechanisms Editor's Notes | Huawei, HiSilicon, Intel | imported from 3GU |
| S2‑186740 | Update solution #37 for KI 11:Monitoring | Huawei, HiSilicon | imported from 3GU |
| S2‑186741 | Update to Solution 1 on Release assistance handling | Huawei, HiSilicon, SK Telecom | imported from 3GU |
| S2‑186742 | New solutions: Line Id Transfer to and usage within 5GC | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186743 | ENA: avoiding overlap with other WG | Nokia, Nokia Shanghai Bell, Ericsson | imported from 3GU |
| S2‑186744 | Revision of Study of enablers for Network Automation for 5G | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186745 | TR 23.791 scope update | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186746 | SMS subsciption Change | NEC | imported from 3GU |
| S2‑186747 | UE Context in SMSF data | Huawei, HiSilicon | imported from 3GU |
| S2‑186748 | UE context in SMF data | Huawei, HiSilicon | imported from 3GU |
| S2‑186749 | Emergency call and eCall support when a cell is connected to EPC and 5GC | NEC | imported from 3GU |
| S2‑186750 | Service Authorization and Provisioning to UE for eV2X communications over PC5 based on UE V2X capability | CATT | imported from 3GU |
| S2‑186751 | Update to Solution#6 | CATT | imported from 3GU |
| S2‑186752 | Update to solution 19 | CATT | imported from 3GU |
| S2‑186753 | Update to solution 30 | CATT | imported from 3GU |
| S2‑186754 | Access Node Selection for MT SMS | NEC | imported from 3GU |
| S2‑186755 | Mobility Restriction List clean up | Qualcomm Incorporated | imported from 3GU |
| S2‑186756 | Clarification to the UE's behavior of emergency registered UE | NEC | imported from 3GU |
| S2‑186757 | WLAN SSID as validity condition for WLAN offload in URSP rules | Motorola Mobility, Lenovo | imported from 3GU |
| S2‑186758 | TS 23.502: Mobility Restriction List Clean up | Qualcomm Incorporated | imported from 3GU |
| S2‑186759 | RRC-INACTIVE state and GUTI reallocation procedure over non-3GPP access | NEC | imported from 3GU |
| S2‑186760 | Solution to Key Issue #2 -Supporting multiple V2X applications requiring different operating carrier frequency (for V2X over PC5) or RAT type (for V2X over Uu) | Motorola Mobility, Lenovo | imported from 3GU |
| S2‑186761 | Solution of RG configuration and management | Huawei, HiSilicon | imported from 3GU |
| S2‑186762 | IPTV solution for WWC | Huawei, HiSilicon | imported from 3GU |
| S2‑186763 | Update of Registration Restriction solution | Huawei, HiSilicon | imported from 3GU |
| S2‑186764 | Service Control for Hybrid control | Huawei, HiSilicon | imported from 3GU |
| S2‑186765 | Solution for FWA | Huawei, HiSilicon | imported from 3GU |
| S2‑186766 | Hybrid Access definition and solution | Huawei, HiSilicon | imported from 3GU |
| S2‑186767 | UE relay: slice and QoS issues | Huawei, HiSilicon | imported from 3GU |
| S2‑186768 | Clarification for the handling for downlink signaling over Non-3GPP access | Huawei, HiSilicon | imported from 3GU |
| S2‑186769 | Handling of downlink NAS signalling for UE in CM-IDLE on Non-3GPP access | Huawei, HiSilicon | imported from 3GU |
| S2‑186770 | LS Response on downlink signalling handling for N3GPP | Huawei, HiSilicon | imported from 3GU |
| S2‑186771 | Clarification for the access type for downlink signalling | Huawei, HiSilicon | imported from 3GU |
| S2‑186772 | Clarification of the Service Request procedure | Huawei, HiSilicon | imported from 3GU |
| S2‑186773 | Clarification on EDT procedure | NTT DOCOMO INC. | imported from 3GU |
| S2‑186774 | Default S-NSSAI correction and NSSF service udpate | Huawei, HiSilicon | imported from 3GU |
| S2‑186775 | Multiple PDN session per DNN | Huawei, HiSilicon | imported from 3GU |
| S2‑186776 | Multiple PDN session per DNN | Huawei, HiSilicon | imported from 3GU |
| S2‑186777 | Clarification on priority service | Huawei, Hisillicon | imported from 3GU |
| S2‑186778 | 5G S-TMSI for the network sharing | Huawei, HiSilicon | imported from 3GU |
| S2‑186779 | Subscription of selecting the same SMF and UPF | Huawei, HiSilicon | imported from 3GU |
| S2‑186780 | Subscription of selecting the same SMF and UPF | Huawei, HiSilicon | imported from 3GU |
| S2‑186781 | N16 communication failure | Huawei, HiSilicon | imported from 3GU |
| S2‑186782 | Clarification on UPF tunnel change | Huawei, Hisillicon | imported from 3GU |
| S2‑186783 | Data handling in UPF during IRAT handover | Huawei, HiSilicon | imported from 3GU |
| S2‑186784 | Registration, PDU Session establishment, Xn handover Procedures for solution 6 | Huawei, HiSilicon | imported from 3GU |
| S2‑186785 | UL-CL insertion when ULCL is in different region comparing to A-SMF | Huawei, HiSilicon | imported from 3GU |
| S2‑186786 | Reduce latency to setup the user plane | Huawei, HiSilicon | imported from 3GU |
| S2‑186787 | Evaluation of solution #6 and conclusion proposal | Huawei, HiSilicon | imported from 3GU |
| S2‑186788 | Evaluation for the solution 10 | Huawei, HiSilicon | imported from 3GU |
| S2‑186789 | Group based solution for NF/NF service instance reliability | Huawei, HiSilicon, SK Telecom | imported from 3GU |
| S2‑186790 | Mobility from EPC to 5GC for slice support | Huawei, HiSilicon | imported from 3GU |
| S2‑186791 | [DRAFT] Reply LS on Service Area Restrictions | Qualcomm Tech. Netherlands B.V | imported from 3GU |
| S2‑186792 | Indirect data forwarding for N2 based HO Clean up | Qualcomm Incorporated | imported from 3GU |
| S2‑186793 | Evaluation of Solutions for Key issue 4 | Qualcomm Incorporated | imported from 3GU |
| S2‑186794 | Updating 6.2 Solution 2 to add a procedure for Multi-Access PDU Session Modification | ETRI | imported from 3GU |
| S2‑186795 | TR Skeleton for Study on 5GS Enhanced support of Vertical and LAN Services | Nokia, Nokia Shanghai Bell (Rapporteur) | imported from 3GU |
| S2‑186796 | TR Scope | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186797 | Key issue on accessing PLMN services via type-b network | Nokia, Nokia Shanghai Bell, Qualcomm | imported from 3GU |
| S2‑186798 | Key issue on support for TSN | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated | imported from 3GU |
| S2‑186799 | Key issue on support for Service Exposure for Vertical and LAN Services | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated | imported from 3GU |
| S2‑186800 | Key issue on support for type-a networks | Nokia, Nokia Shanghai Bell, Qualcomm | imported from 3GU |
| S2‑186801 | Enhancements to Services Framework | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186802 | Solution for 5G URLLC in 3GPP System | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186803 | 5GS to EPS Mobility | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186804 | Registration type for Nudm_UECM_Registration | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186805 | Correction to AS Security Context | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186806 | GUAMI Definition Correction | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186807 | NGAP-UE-TNLA-Binding re-creation when preferred TNL is unavailable | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186808 | NGAP-UE-TNLA-Binding re-creation when preferred TNL is unavailable | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186809 | Merging Network Slice with regular EPS Interworking | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186810 | No Dynamic 5QI signaling towards RAN - Align with RAN WG3 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186811 | Notification Control applicability | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186812 | Peer NF association of GUAMI with a given UE | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186813 | 5G AN Parameters sent during Service Request | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186814 | 5G AN Parameters sent during Service Request | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186815 | Key issue: Access and Mobility control for vertical LAN UE | Vivo | imported from 3GU |
| S2‑186816 | Key issue: Interworking between type-a networks and public networks | Vivo | imported from 3GU |
| S2‑186817 | Clarification on DNN based congestion control for System interworking w/o N26 | LG Electronics | imported from 3GU |
| S2‑186818 | Corrections in clause 4.3.3 PDU Session Modification and clause 4.3.4 PDU Session Release | ETRI | imported from 3GU |
| S2‑186819 | Update of Solution 4 'Positioning operations considering different LMF deployment scenarios' with the MR-LR case for solution 4A | Huawei, HiSilicon | imported from 3GU |
| S2‑186820 | Solution for the optimization for profile of NF/NF service instance | Huawei, HiSilicon | imported from 3GU |
| S2‑186821 | [DRAFT] Reply LS on TLS and inter PLMN routing | Huawei, HiSilicon | imported from 3GU |
| S2‑186822 | Solution for KI 11 Coordination of Positioning Signalling Transmitted via CP Path and UP Path | Huawei, HiSilicon | imported from 3GU |
| S2‑186823 | Correction on AMF and UDM service table | Huawei, HiSilicon | imported from 3GU |
| S2‑186824 | Key Issue Proposal on 5GLAN Group Management | Huawei, HiSilicon, KPN | imported from 3GU |
| S2‑186825 | Key Issue Proposal on Clock Synchronization | Huawei, HiSilicon | imported from 3GU |
| S2‑186826 | Key Issue Proposal on Control of Deterministic Packet Delivery | Huawei, HiSilicon | imported from 3GU |
| S2‑186827 | Key issue 8 update: session and service continuity requirement based edge computing for V2X | China Mobile | imported from 3GU |
| S2‑186828 | Home WLAN accessing solution | Huawei, HiSilicon | imported from 3GU |
| S2‑186829 | PDU session establishment. | Huawei, HiSilicon | imported from 3GU |
| S2‑186830 | Editorial corrections | Huawei, HiSilicon | imported from 3GU |
| S2‑186831 | Relationship between Traffic Profile and Release Assistance Information | Huawei, HiSilicon | imported from 3GU |
| S2‑186832 | Traffic Profile for for NB-IoT UE Uu operation optimisation | Huawei, HiSilicon | imported from 3GU |
| S2‑186833 | Correction to S1-U bearer(s) establishment procedure during data transport using CP CIoT Optimisation | Huawei, HiSilicon | imported from 3GU |
| S2‑186834 | Update of Solution 5: V2X parameters provisioning | Huawei, HiSilicon | imported from 3GU |
| S2‑186835 | Update of Solution 2: QoS Support for eV2X over Uu interface | Huawei, HiSilicon | imported from 3GU |
| S2‑186836 | Further considerations on slicing for eV2X services and update of Solution 7 | Huawei, HiSilicon | imported from 3GU |
| S2‑186837 | Procedure descriptions for Solution 16: QoS Enhancements for eV2X Services | Huawei, HiSilicon | imported from 3GU |
| S2‑186838 | New Solution for KI8 and KI extension: Support for MEC topology exposure for efficient UPF anchor selection | Huawei, HiSilicon | imported from 3GU |
| S2‑186839 | Update of Solution 15 to address ENs and provide missing procedures | Huawei, HiSilicon | imported from 3GU |
| S2‑186840 | New Solution for KI12: Interworking solution for architectual option B | Huawei, HiSilicon, InterDigital | imported from 3GU |
| S2‑186841 | New key issue for supporting broadcast for 5GS eV2X | Huawei, HiSilicon | imported from 3GU |
| S2‑186842 | Solution for broadcast KI | Huawei, HiSilicon | imported from 3GU |
| S2‑186843 | New key issue and solution for dynamic application adjustments | Huawei, HiSilicon | imported from 3GU |
| S2‑186844 | UE location report to the SMF by RAN in RRC Inactive State | Huawei, HiSilicon | imported from 3GU |
| S2‑186845 | Clarification on 5G-GUTI in use during Registration procedure | OPPO | imported from 3GU |
| S2‑186846 | Solution of 5GC Capable UE behind 5G-RG connected to 5GC via NG-RAN/W-5GAN | Intel | imported from 3GU |
| S2‑186847 | Solution Updates for Key Issue 13 | Intel | imported from 3GU |
| S2‑186848 | Update of Solution 5 | Apple (UK) Limited | imported from 3GU |
| S2‑186849 | Updates of Solution 1 with alternative UP Convergence Method and Evaluation Procedure | Intel | imported from 3GU |
| S2‑186850 | New Key Issues for Network Discovery & Selection and Access Control & Restriction | Intel | imported from 3GU |
| S2‑186851 | Key issues for 5G-LAN Service Discovery, Selection and Restriction | Intel | imported from 3GU |
| S2‑186852 | Null interworking with GERAN/UTRAN CS domain | Vodafone | imported from 3GU |
| S2‑186853 | Correction on UE policy delivery | OPPO | imported from 3GU |
| S2‑186854 | Key issues of Service and Session Management for 5G-LAN type Service | Intel | imported from 3GU |
| S2‑186855 | RRC Inactive to EPC mobility | Vodafone | imported from 3GU |
| S2‑186856 | Architecture requirements of data interworking | China Mobile | imported from 3GU |
| S2‑186857 | Correction on mobility management back-off timer | Vivo | imported from 3GU |
| S2‑186858 | Key issue: Clarification on procedures and required data for UDM/UDR and HSS interworking | China Mobile | imported from 3GU |
| S2‑186859 | Key issue: How to interwork between UDM/UDR and HSS | China Mobile | imported from 3GU |
| S2‑186860 | [DRAFT] LS on Service Authorization to NG-RAN for eV2X communications over PC5 | LG Electronics | imported from 3GU |
| S2‑186861 | Clarification on the target CN indication when Emergency Services Fallback | OPPO | imported from 3GU |
| S2‑186862 | 5G-TMSI should map to M-TMSI | Vodafone | imported from 3GU |
| S2‑186863 | 5WWC: Applicability of ATSSS for 5G-RG | Telstra | imported from 3GU |
| S2‑186864 | Homogeneous Support of IMS Voice over PS Sessions indication | LG Electronics | imported from 3GU |
| S2‑186865 | 5WWC: Update of Solution #13 | Telstra Corporation Limited | imported from 3GU |
| S2‑186866 | Discussions on RAN initiated TNL Associations over NGAP | Huawei | imported from 3GU |
| S2‑186867 | [DRAFT] LS Reply on RAN initiated TNL Associations over NGAP | Huawei | imported from 3GU |
| S2‑186868 | NG-RAN node support multiple TNL Endpoints | Huawei, HiSilicon | imported from 3GU |
| S2‑186869 | Clarification on Homogeneous Support of IMS Voice over PS Sessions indication | LG Electronics | imported from 3GU |
| S2‑186870 | Partial Solution to Key Issue #EPC-7 'level of security' | Vodafone | imported from 3GU |
| S2‑186871 | Clarification on the non-IP PDU session type for EPS to 5GS interworking | ZTE | imported from 3GU |
| S2‑186872 | Clarification on the PDU session handling in EPS to 5GS handover with N26 | ZTE, Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186873 | Clarification on the PDU session handling in EPS to 5GS handover with N26 | ZTE, Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186874 | Clarification on the target MME capability from AMF to SMF for 5GS to EPS mobility | ZTE | imported from 3GU |
| S2‑186875 | Update the Nsmf_PDUSession_CreateSMContext for EPS to 5GS mobility | ZTE | imported from 3GU |
| S2‑186876 | Solution on the mobility decision | ZTE | imported from 3GU |
| S2‑186877 | Solution on the UPF selection | ZTE | imported from 3GU |
| S2‑186878 | Returning UE from UTRAN to NR or E-UTRA with existing mechanism | ZTE | imported from 3GU |
| S2‑186879 | Update the impact to the solution 2 | ZTE | imported from 3GU |
| S2‑186880 | Handling LADN service area during handovers | NTT DOCOMO | imported from 3GU |
| S2‑186881 | Correction on Secondary RAT data usage report in RAU procedure | Huawei, HiSilicon | imported from 3GU |
| S2‑186882 | Clarification on N3IWF key delivery during registration procedure | Samsung | imported from 3GU |
| S2‑186883 | KI#15 - Solution discussion | NTT DOCOMO | imported from 3GU |
| S2‑186884 | Key issues on the maximum size of UE radio capabilities, and interface capabilities | Vodafone | imported from 3GU |
| S2‑186885 | Clarification on EPC Solution#4 | Samsung | imported from 3GU |
| S2‑186886 | Solution to access restriction on UE's attach for RLOS | Samsung | imported from 3GU |
| S2‑186887 | Solution update: NIDD service activation for AMF and SMF | Samsung | imported from 3GU |
| S2‑186888 | New solution: Aggregation of Data over NAS | Samsung | imported from 3GU |
| S2‑186889 | Solution 8 update: to resolve ENs | Samsung | imported from 3GU |
| S2‑186890 | Solution 19 update: to resolve ENs | Samsung | imported from 3GU |
| S2‑186891 | [DRAFT] Reply LS to S2-185503 Location reporting for AoI | Samsung | imported from 3GU |
| S2‑186892 | Clarification on representation of AoI for NG-RAN location reporting procedure | Samsung | imported from 3GU |
| S2‑186893 | MT SMS failure recovery | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186894 | Incorrect text implying slicing is optional | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186895 | Update of SMSF selection function | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186896 | Solution to Mutually exclusive access to Network Slices | China Telecommunications | imported from 3GU |
| S2‑186897 | Impact area of ConnectionLess solution | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186898 | Add monitoring event cancellation call flows | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186899 | Nudm_EventExposure subscription and cancellation | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186900 | Time stamp in Namf, Nsmf and Nnef EventExposure_Notify service operations | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186901 | Corrections to NF profile description | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186902 | Corrections to NRF services description | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186903 | Corrections to NF services names and references | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186904 | SBA friendly UE policy delivery | Samsung | imported from 3GU |
| S2‑186905 | Correction to handover from EPS to 5GS | CATT | imported from 3GU |
| S2‑186906 | Handling PDN connections with PGW not within the new PLMN | CATT | imported from 3GU |
| S2‑186907 | Correction on inter-PLMN mobility | CATT | imported from 3GU |
| S2‑186908 | Optimizing connection management based on NWDAF output | CATT | imported from 3GU |
| S2‑186909 | Overload avoidance with the help of NWDAF output | CATT | imported from 3GU |
| S2‑186910 | Solution for Connected mode mobility from EPC to 5GC | CATT | imported from 3GU |
| S2‑186911 | Solution on Delayed MT data transmission for power saving | CATT | imported from 3GU |
| S2‑186912 | Update to PDN connection establishment | CATT | imported from 3GU |
| S2‑186913 | UE behaviour when RLOS attached UE selects non-equivalent PLMN | NEC | imported from 3GU |
| S2‑186914 | Clarification on Nbsf_Management_Update service operation | China Mobile | imported from 3GU |
| S2‑186915 | Nudm service update to support protection of Steering of Roaming | Samsung, Ericsson, Intel, Nokia, Nokia Shanghai Bell, Qualcomm, T-Mobile USA | imported from 3GU |
| S2‑186916 | Update on AUSF service operation to support Steering of Roaming | Samsung, Ericsson, Intel, Nokia, Nokia Shanghai Bell, Qualcomm, T-Mobile USA | imported from 3GU |
| S2‑186917 | Architectural Assumptions in 23,732 | Vodafone | imported from 3GU |
| S2‑186918 | GMLC based Positioning Access selection for LCS service | CATT | imported from 3GU |
| S2‑186919 | Key Issue: UE-driven analytics sharing mechanisms to 5GC | Samsung | imported from 3GU |
| S2‑186920 | Evaluation of solutions and conclusion of Key Issue #14 | CATT | imported from 3GU |
| S2‑186921 | New Key Issue: UE driven analytics sharing | Lenovo, Motorola Mobility | imported from 3GU |
| S2‑186922 | Evaluation of solutions of Key Issue #4 | CATT | imported from 3GU |
| S2‑186923 | Traffic Profile for for NB-IoT UE Uu operation optimisation | Huawei, HiSilicon | imported from 3GU |
| S2‑186924 | Update solution 5 in TR 23.791 | Lenovo, Motorola Mobility | imported from 3GU |
| S2‑186925 | Update solution 12: LCS support for non-3GPP access | Lenovo, Motorola Mobility | imported from 3GU |
| S2‑186926 | Solution for KI 1#: Redundant Transmission in core network for URLLC service | Lenovo, Motorola Mobility | imported from 3GU |
| S2‑186927 | [DRAFT] LS on security handling when deploying UDSF | Ericsson | imported from 3GU |
| S2‑186928 | Introduction of local RRM policy specific UE differentiation | Vodafone, Ericsson | imported from 3GU |
| S2‑186929 | Update solution 6.12 | ITRI | imported from 3GU |
| S2‑186930 | Resolve EN in Release of a Multi-Access PDU Session | ITRI | imported from 3GU |
| S2‑186931 | Clarification on N1 data transfer for RRC-Inactive UE | China Mobile, Ericsson, China Telecom, China Unicom, CATT, Huawei, ZTE, Motorola Mobility, Lenovo, OPPO, LG Electronics | imported from 3GU |
| S2‑186932 | Update on Domain Selection Rules for emergency session attempts | Samsung | imported from 3GU |
| S2‑186933 | Solution for KI#2 / KI#12: PC5 resource control | Samsung | imported from 3GU |
| S2‑186934 | DP for clarification on N1 data transfer for RRC-Inactive UE | China Mobile Com. Corporation | imported from 3GU |
| S2‑186935 | Solution for KI#5 / KI#6 / KI#11: Service authorization based on S-NSSAI | Samsung | imported from 3GU |
| S2‑186936 | Requested NSSAI in non-roaming case | ETRI | imported from 3GU |
| S2‑186937 | Clafication on retrievial of the security context from old AMF | Huawei, HiSilicon | imported from 3GU |
| S2‑186938 | Update to Solution 9 to enhance the congestion control description | Motorola Mobility, Lenovo, Qualcomm, Charter Communications, Nokia, Nokia Shanghai Bell, Intel, Sprint | imported from 3GU |
| S2‑186939 | Update to Solution 15: External parameter provisioning | Motorola Mobility, Lenovo | imported from 3GU |
| S2‑186940 | [DRAFT] Reply LS on enabling and disabling NG RAN Capabilities | Motorola Mobility, Lenovo | imported from 3GU |
| S2‑186941 | Mutually exclusive access to Network Slices | InterDigital Inc. | imported from 3GU |
| S2‑186942 | New Key Issue: Routing in 5GLAN | InterDigital Inc. | imported from 3GU |
| S2‑186943 | Update to Illustrated Procedures: 'Delivery of Messages' | InterDigital Inc. | imported from 3GU |
| S2‑186944 | New Key Issue: Access to specific Network Slices authorized and authenticated through additional User Identifiers | InterDigital Inc. | imported from 3GU |
| S2‑186945 | Solution for QoS Monitoring Key Issue | Huawei, HiSilicon | imported from 3GU |
| S2‑186946 | New KI: support for 5GLAN communication service | Huawei, HiSilicon | imported from 3GU |
| S2‑186947 | Missing NEF services | ORANGE | imported from 3GU |
| S2‑186948 | Removal of Editor's note in Sol#15 | NEC | imported from 3GU |
| S2‑186949 | Update to Support of edge computing Key Issue #8 | InterDigital Inc. | imported from 3GU |
| S2‑186950 | Solution to KI#8:5GS V2X Edge Computing | InterDigital Inc. | imported from 3GU |
| S2‑186951 | Attempt to update Scenario 3 to clarify relationships between 'end UEs', 'RGs' and core network entities | Vodafone | imported from 3GU |
| S2‑186952 | [DRAFT] LS on Network Data Analytics | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186953 | Update to Solution#19: UP deactivation for UE in RRC inactive state | InterDigital Inc., | imported from 3GU |
| S2‑186954 | [DRAFT] Paging cause from RAN to UE | Intel | imported from 3GU |
| S2‑186955 | Solution for I-SMF selection during 4G to 5G IWK | Huawei, HiSilicon | imported from 3GU |
| S2‑186956 | Way forward for event exposure key issue conclusion | Huawei, HiSilicon | imported from 3GU |
| S2‑186957 | Architecture Principle for UPF Reporting | Huawei, HiSilicon, SKT | imported from 3GU |
| S2‑186958 | [DRAFT] LS Reply on LMF determination that the UE is served by NR | Huawei | imported from 3GU |
| S2‑186959 | [DRAFT] Reply LS on Connection Control | Qualcomm Incorporated | imported from 3GU |
| S2‑186960 | Potential way to achieve Mutually Exclusive access to Network Slices | ITRI | imported from 3GU |
| S2‑186961 | Correction to interworking with EPC with N3GPP PDU Sessions | MediaTek Inc. | imported from 3GU |
| S2‑186962 | UE radio capabilities - alignment with rSRVCC from GERAN | Vodafone | imported from 3GU |
| S2‑186963 | Solution #4.3 update | NTT DOCOMO | imported from 3GU |
| S2‑186964 | Emergency Services Support indicator for non-3GPP access | ORANGE | imported from 3GU |
| S2‑186965 | Clarification of the AMF Set definition | NTT DOCOMO | imported from 3GU |
| S2‑186966 | GUAMI Definition Correction | Nokia, Nokia Shanghai Bell, Orange | imported from 3GU |
| S2‑186967 | Handling of downlink NAS signalling for UE in CM-IDLE on Non-3GPP access | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186968 | Handling of downlink NAS signalling for UE in CM-IDLE on Non-3GPP access | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑186969 | LS from SA WG5: LS on Introduction of a new charging method for PCC Rule. | SA WG5 | imported from 3GU |
| S2‑186970 | LS from SA WG5: LS on Use of NRF framework by CHF for information | SA WG5 | imported from 3GU |
| S2‑186971 | Clarifications about MOBIKE and N3IWF certificate | Motorola Mobility, Lenovo | imported from 3GU |
| S2‑186972 | Discussion about NWDAF interactions with OAM | Huawei, HiSilicon, CATR, Convida Wireless LLC, China Unicom, China Mobile, Orange, Alibaba | - |
| S2‑186973 | New key issue: Support 5G deployment option #3 | Intel | - |
| S2‑186974 | Key issue 8 update: session and service continuity requirement based edge computing | China Mobile | - |
| S2‑186975 | Key Issue on Broadcast Support for eV2X | Huawei, HiSilicon | - |
| S2‑186976 | Solution for KI#3: QoS Support for eV2X over Uu interface | Ericsson, LG Electronics | - |
| S2‑186977 | Solution to key issue#10 for non-IP based V2X message transmission and reception over Uu | LG Electronics, NTT DOCOMO | - |
| S2‑186978 | Procedure descriptions for Solution 16 - QoS Enhancements for eV2X Services | Huawei, HiSilicon | - |
| S2‑186979 | EV2X QoS Support of PC5 communications | Qualcomm Incorporated, | - |
| S2‑186980 | Update of Solution#6 | LG Electronics, CATT, NTT DOCOMO, Motorola Mobility, Lenovo | - |
| S2‑186981 | Update of solution #3 | Ericsson, Samsung | - |
| S2‑186982 | Update on eV2X Solution #10 addressing key issue #12 based on Architecture in A.2 | Intel, LG Electronics, Blackberry | - |
| S2‑186983 | Procedures for the provision of Network-controlled QoS for PC5 communication | Huawei, HiSilicon | - |
| S2‑186984 | New key issue: Support 5G deployment option #3 | Intel | - |
| S2‑186985 | Key issue 8 update: session and service continuity requirement based edge computing | China Mobile | - |
| S2‑186986 | Key Issue on Broadcast Support for eV2X | Huawei, HiSilicon | - |
| S2‑186987 | Solution for KI#3: QoS Support for eV2X over Uu interface | Ericsson, LG Electronics | - |
| S2‑186988 | Solution to key issue#10 for non-IP based V2X message transmission and reception over Uu | LG Electronics, NTT DOCOMO | - |
| S2‑186989 | Procedure descriptions for Solution 16 - QoS Enhancements for eV2X Services | Huawei, HiSilicon | - |
| S2‑186990 | EV2X QoS Support of PC5 communications | Qualcomm Incorporated, LG Electronics, InterDigital Inc. | - |
| S2‑186991 | Update of solution #3 | Ericsson, Samsung | - |
| S2‑186992 | Reserved for LaeYoung's parallel sessions | - | imported from 3GU |
| S2‑186993 | Architectural Assumptions: RLOS access to authenticated UEs | Nokia, Nokia Shanghai Bell | - |
| S2‑186994 | On congestion control for PaRLOS | Qualcomm Incorporated | - |
| S2‑186995 | Update to Solution 9 to enhance the congestion control description | Motorola Mobility, Lenovo, Qualcomm, Charter Communications, Nokia, Nokia Shanghai Bell, Intel, Sprint | - |
| S2‑186996 | Update of solution #4 | Nokia, Nokia Shanghai Bell | - |
| S2‑186997 | Clarification on EPC Solution#4 | Samsung | - |
| S2‑186998 | Update of solution #5 | Nokia, Nokia Shanghai Bell | - |
| S2‑186999 | Update of solution #10 | Nokia, Nokia Shanghai Bell | - |
| S2‑187000 | New solution to allow Authentication for RLOS attached UE and update to Solution #8 | Ericsson | - |
| S2‑187001 | Partial Solution to Key Issue #EPC-7 'level of security' | Vodafone | - |
| S2‑187002 | Update of Solution #1: Support of Trusted Non-3GPP Access | Motorola Mobility, Lenovo, Broadcom | - |
| S2‑187003 | PDU session establishment procedure | Huawei, HiSilicon | - |
| S2‑187004 | Update of Solution #3: Access to 5GC from UEs without supporting NAS on non-3GPP access | Motorola Mobility, Lenovo, Broadcom | - |
| S2‑187005 | Editorial corrections | Huawei, HiSilicon | - |
| S2‑187006 | Solution for FWA | Huawei, HiSilicon | - |
| S2‑187007 | SM procedures for 5WWC | Ericsson | - |
| S2‑187008 | MM procedures for 5WWC | Ericsson | - |
| S2‑187009 | [DRAFT] LS Reply on LMF determination that the UE is served by NR | Huawei | - |
| S2‑187010 | Key Issue on Coexistence with the Location Solution in Release 15 | Qualcomm Incorporated | - |
| S2‑187011 | Support for Key Issue on Coexistence with the Location Solution in Release 15 | Qualcomm Incorporated | - |
| S2‑187012 | Enhancements to Solution 2 | Qualcomm Incorporated | - |
| S2‑187013 | Support of Low Power Periodic and Triggered Location for Solution 2 using EDT | Qualcomm Incorporated | - |
| S2‑187014 | Updates for LMF selection criteria | Nokia, Nokia Shanghai Bell | - |
| S2‑187015 | Adding charging aspects and other updates to solution 14 | Nokia, Nokia Shanghai Bell | - |
| S2‑187016 | Supported positioning methods | Ericsson | - |
| S2‑187017 | Updates to Solution 5 | Cisco, Softbank | - |
| S2‑187018 | Registration, PDU Session establishment, Xn handover Procedures for solution 6 | Huawei, HiSilicon | - |
| S2‑187019 | UL-CL insertion when ULCL is in different region comparing to A-SMF | Huawei, HiSilicon | - |
| S2‑187020 | Solution for I-SMF selection during 4G to 5G IWK | Huawei, HiSilicon | - |
| S2‑187021 | Removal of Editor's note in Sol#15 | NEC | - |
| S2‑187022 | L-SMF clarification for solution 16: I-UPF insertion and L-SMF/L-UPF selection | Qualcomm Incorporated, LG Electronics, InterDigital Inc. | - |
| S2‑187023 | New solution for UL-CL/BP Insertion with UPF that is capable to flexibly interface any SMF | Ericsson | - |
| S2‑187024 | Reduce latency to setup the user plane | Huawei, HiSilicon | - |
| S2‑187025 | Evaluation of solution #6 and conclusion proposal | Huawei, HiSilicon | - |
| S2‑187026 | Evaluation for the solution 10 | Huawei, HiSilicon | - |
| S2‑187027 | 23.716 new solution: Subscription control for the Support of ranges of IP address/Prefixes in a PDU Session | Nokia, Nokia Shanghai Bell | - |
| S2‑187028 | IPTV solution for WWC | Huawei, HiSilicon | - |
| S2‑187029 | Unicast media delivery for 5WWC | Ericsson | - |
| S2‑187030 | Mobility Restrictions for 5WWC | Ericsson | - |
| S2‑187031 | Update of Registration Restriction solution | Huawei, HiSilicon | - |
| S2‑187032 | Solution Updates for Key Issue 13 | Intel, Huawei | - |
| S2‑187033 | Solution for RG configuration and management | Huawei, HiSilicon | - |
| S2‑187034 | 5WWC: Applicability of ATSSS for 5G-RG | Telstra | - |
| S2‑187035 | TR 23.716: Updates to Architectural Requirements | OTD, Charter | - |
| S2‑187036 | Attempt to update Scenario 3 to clarify relationships between 'end UEs', 'RGs' and core network entities | Vodafone | - |
| S2‑187037 | Architectural Updates for ATSSS Solution 1 | Broadcom | - |
| S2‑187038 | Additional options for L4 convergence method in Solution 1 | Deutsche Telekom | - |
| S2‑187039 | Updates of Solution 1 with alternative UP Convergence Method and Evaluation Procedure | Intel | - |
| S2‑187040 | Solution 2: Update of Combined Establishment | Motorola Mobility, Lenovo | - |
| S2‑187041 | Solution 2 Update: Modifying Multi-access PDU Session as single-access PDU | InterDigital Inc. | - |
| S2‑187042 | Updating 6.2 Solution 2 to add a procedure for Multi-Access PDU Session Modification | ETRI | - |
| S2‑187043 | Resolve EN in Release of a Multi-Access PDU Session | ITRI | - |
| S2‑187044 | ATSSS execution procedure for TFCP solution | OPPO, Huawei | - |
| S2‑187045 | Update of TFCP solution | Huawei, HiSilicon | - |
| S2‑187046 | ATSSS path performance measurement function | Huawei, HiSilicon | - |
| S2‑187047 | 23.793: Update of Solution 5 | Apple (UK) Limited | - |
| S2‑187048 | TR 23.793: MPTCP Proxy Selection Policy and miscellaneous changes | ZTE Wistron | - |
| S2‑187049 | Correction to Service Request QoS when changing between non-3GPP and 3GPP accesses | Nokia, Nokia Shanghai Bell, LGE | - |
| S2‑187050 | Handling of downlink NAS signalling for UE in CM-IDLE on Non-3GPP access | Huawei, HiSilicon | imported from 3GU |
| S2‑187051 | DL signalling handling for non-3GPP PDU Session | LG Electronics | - |
| S2‑187052 | Handling of downlink NAS signalling for UE in CM-IDLE on Non-3GPP access | Nokia, Nokia Shanghai Bell | - |
| S2‑187053 | Clarification of the Service Request procedure | Huawei, HiSilicon | imported from 3GU |
| S2‑187054 | Corrections to NRF services description | Nokia, Nokia Shanghai Bell | - |
| S2‑187055 | Correction on AMF and UDM service table | Huawei, HiSilicon | - |
| S2‑187056 | Corrections to NF profile description | Nokia, Nokia Shanghai Bell | - |
| S2‑187057 | Corrections to NF services names and references | Nokia, Nokia Shanghai Bell | - |
| S2‑187058 | Add monitoring event cancelltion call flows | Nokia, Nokia Shanghai Bell | - |
| S2‑187059 | Nudm_EventExposure_Subscribe and unsubscribe service operation correction | Nokia, Nokia Shanghai Bell | - |
| S2‑187060 | Missing NEF services. | ORANGE | - |
| S2‑187061 | Fix the leftover FFS for Solution #4 | Vivo | - |
| S2‑187062 | Update of solution #3 on returning UE from UTRAN to NG-RAN or E-UTRAN | Intel, Huawei | - |
| S2‑187063 | New solution on returning UE from UTRAN to NG-RAN or E-UTRAN with MSC and UTRAN impact | Intel, Huawei | - |
| S2‑187064 | Returning UE from UTRAN to NR or E-UTRA with existing mechanism | ZTE | - |
| S2‑187065 | Evaluation and conclusion for KI#1 and KI#2 | China Unicom, vivo, Huawei, CAICT, CATT, ZTE, OPPO, Intel, Qualcomm, Lenovo, Motorola Mobility, MediaTek Inc | - |
| S2‑187066 | Evaluation of Solutions for Key issue 4 | Qualcomm Incorporated | - |
| S2‑187067 | [DRAFT] LS reply to LS on Use of NRF framework by CHF for information | SA WG2 | - |
| S2‑187068 | [DRAFT] LS reply to LS on UE policy | SA WG2 | - |
| S2‑187069 | N28 session termination | Nokia, Nokia Shanghai Bell | - |
| S2‑187070 | Adding N28 session termination procedure and updates to CHF services | Nokia, Nokia Shanghai Bell | - |
| S2‑187071 | [DRAFT] LS reply to LS on clarification for spending limit control functionality | SA WG2 | - |
| S2‑187072 | Update to UE policy distribution | Nokia, Nokia Shanghai Bell | - |
| S2‑187073 | Update to UE policy provision and update | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑187074 | SBI friendly UE policy delivery procedure | Samsung | - |
| S2‑187075 | Clarification on initial UE policy provisioning | Intel, Telecom Italia | - |
| S2‑187076 | UE triggered UE policy provisioning procedure | Intel, Qualcomm Inc, Samsung, Mediatek | - |
| S2‑187077 | URSP updates and Application to PDU session association re-evaluation | Qualcomm Incorporated | - |
| S2‑187078 | UE policy graceful enforcement time in URSP rule | Intel, Nokia, OPPO, SAMSUNG, Orange, KDDI, China Unicom, Apple | - |
| S2‑187079 | Essential correction and clarification about user preference for URSP | KDDI, Orange, Telecom Italia, AT&T, Vodafone, Sprint, Deutsche Telekom, T-Mobile USA, China Mobile, Verizon UK ltd, Telefonica, BT, KPN, SK Telecom, China Unicom, China Telecom | - |
| S2‑187080 | Clarification for the access type for downlink signalling | Huawei, HiSilicon | - |
| S2‑187081 | LS Response on downlink signalling handling for N3GPP | Huawei, HiSilicon | - |
| S2‑187082 | PDU session establishment procedure | Huawei, HiSilicon | - |
| S2‑187083 | Editorial corrections | Huawei, HiSilicon | - |
| S2‑187084 | Solution for FWA | Huawei, HiSilicon | - |
| S2‑187085 | IPTV solution for WWC | Huawei, HiSilicon | - |
| S2‑187086 | Solution Updates for Key Issue 13 | Intel, Huawei | - |
| S2‑187087 | 5WWC: Applicability of ATSSS for 5G-RG | Telstra | - |
| S2‑187088 | TR 23.716: Updates to Architectural Requirements | OTD, Charter | - |
| S2‑187089 | Attempt to update Scenario 3 to clarify relationships between 'end UEs', 'RGs' and core network entities | Vodafone | - |
| S2‑187090 | Architectural Updates for ATSSS Solution 1 | Broadcom | - |
| S2‑187091 | Additional options for L4 convergence method in Solution 1 | Deutsche Telekom | imported from 3GU |
| S2‑187092 | Updates of Solution 1 with alternative UP Convergence Method and Evaluation Procedure | Intel | - |
| S2‑187093 | Architectural Assumptions: RLOS access to authenticated UEs | Nokia, Nokia Shanghai Bell, Ericsson | - |
| S2‑187094 | Update of solution #4 | Nokia, Nokia Shanghai Bell, Ericsson | - |
| S2‑187095 | Clarification on EPC Solution#4 | Samsung | - |
| S2‑187096 | LS Reply on LMF determination that the UE is served by NR | SA WG2 | - |
| S2‑187097 | Enhancements to Solution 2 | Qualcomm Incorporated | - |
| S2‑187098 | Support of Low Power Periodic and Triggered Location for Solution 2 using EDT | Qualcomm Incorporated | - |
| S2‑187099 | Updates for LMF selection criteria | Nokia, Nokia Shanghai Bell | - |
| S2‑187100 | Adding charging aspects and other updates to solution 14 | Nokia, Nokia Shanghai Bell | - |
| S2‑187101 | New Solution for KI#15: Location continuity support for N26 based Handovers | CATT | - |
| S2‑187102 | TR 23.793: MPTCP Proxy Selection Policy and miscellaneous changes | ZTE Wistron | - |
| S2‑187103 | Solution 2 Update: Modifying Multi-access PDU Session as single-access PDU | InterDigital Inc. | - |
| S2‑187104 | Updating 6.2 Solution 2 to add a procedure for Multi-Access PDU Session Modification | ETRI, ITRI | - |
| S2‑187105 | ATSSS path performance measurement function | Huawei, HiSilicon | - |
| S2‑187106 | 23.793: Update of Solution 5 | Apple (UK) Limited | - |
| S2‑187107 | ATSSS path performance measurement function | Huawei, HiSilicon | - |
| S2‑187108 | Updating 6.2 Solution 2 to add a procedure for Multi-Access PDU Session Modification | ETRI, ITRI | - |
| S2‑187109 | PCF added as consumer of EventExposure service of AMF and SMF | Huawei, HiSilicon, Ericsson | - |
| S2‑187110 | Clarification on N3IWF key delivery during registration procedure | Samsung | - |
| S2‑187111 | L-SMF clarification for solution 16: I-UPF insertion and L-SMF/L-UPF selection | ZTE | - |
| S2‑187112 | L-SMF clarification for solution 16: I-UPF insertion and L-SMF/L-UPF selection | ZTE | - |
| S2‑187113 | Updates to Solution 5 | Cisco, Softbank | - |
| S2‑187114 | Registration, PDU Session establishment, Xn handover Procedures for solution 6 | Huawei, HiSilicon | - |
| S2‑187115 | Reduce latency to setup the user plane | Huawei, HiSilicon | - |
| S2‑187116 | Evaluation of solution #6 and conclusion proposal | Huawei, HiSilicon | - |
| S2‑187117 | Evaluation for the solution 10 | Huawei, HiSilicon | - |
| S2‑187118 | Update of solution #3 on returning UE from UTRAN to NG-RAN or E-UTRAN | Intel, Huawei | - |
| S2‑187119 | New solution on returning UE from UTRAN to NG-RAN or E-UTRAN with MSC and UTRAN impact | Intel, Huawei | - |
| S2‑187120 | Evaluation of Solutions for Key issue 4 | Qualcomm Incorporated | - |
| S2‑187121 | Evaluation for the solution 10 | Huawei, HiSilicon | - |
| S2‑187122 | Update of Solution #3: Access to 5GC from UEs without supporting NAS on non-3GPP access | Motorola Mobility, Lenovo, Broadcom | - |
| S2‑187123 | On congestion control for PaRLOS | Qualcomm Incorporated | - |
| S2‑187124 | Update of solution #5 | Nokia, Nokia Shanghai Bell | - |
| S2‑187125 | Update of solution #10 | Nokia, Nokia Shanghai Bell | - |
| S2‑187126 | Partial Solution to Key Issue #EPC-7 'level of security' | Vodafone | - |
| S2‑187127 | Update of solution #4 | Nokia, Nokia Shanghai Bell, Ericsson | - |
| S2‑187128 | Handling of downlink NAS signalling for UE in CM-IDLE on Non-3GPP access | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑187129 | Correction to Service Request QoS when changing between non-3GPP and 3GPP accesses | Nokia, Nokia Shanghai Bell, LGE | - |
| S2‑187130 | [DRAFT] Reply LS on 5G service request procedure | SA WG2 | - |
| S2‑187131 | Correction on AMF and UDM service table | Huawei, HiSilicon | - |
| S2‑187132 | Clarification on initial UE policy provisioning | Intel, Telecom Italia | - |
| S2‑187133 | URSP updates and Application to PDU session association re-evaluation | Qualcomm Incorporated | - |
| S2‑187134 | Essential correction and clarification about user preference for URSP | KDDI, Orange, Telecom Italia, AT&T, Vodafone, Sprint, Deutsche Telekom, T-Mobile USA, China Mobile, Verizon UK ltd, Telefonica, BT, KPN, SK Telecom, China Unicom, China Telecom | - |
| S2‑187135 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑187136 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑187137 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑187138 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑187139 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑187140 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑187141 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑187142 | Reserved for Krisztian's parallel sessions | - | imported from 3GU |
| S2‑187143 | Enhancement of network event reporting | Ericsson, Verizon, Nokia, Convida | - |
| S2‑187144 | Application detection report when the PFDs are removed | Huawei, HiSilicon | - |
| S2‑187145 | Application detection report when the PFDs are removed | Huawei, HiSilicon | - |
| S2‑187146 | [DRAFT] Reply LS on new BEST Service | Convida Wireless LLC | - |
| S2‑187147 | The proposal for subscribed PTW length | China Mobile | - |
| S2‑187148 | RAN-modified CN assistance parameters | Qualcomm Incorporated, Nokia, Deutsche Telekom, Orange | - |
| S2‑187149 | Introduction of local RRM policy specific UE differentiation | Vodafone, Ericsson | - |
| S2‑187150 | Traffic Profile for NB-IoT UE Uu operation optimisation | Huawei, HiSilicon | - |
| S2‑187151 | Negotiation of long periodic TAU timer value | ORANGE, Telecom Italia, Sprint | - |
| S2‑187152 | Negotiation of long periodic RAU timer value | ORANGE, Telecom Italia, Sprint | - |
| S2‑187153 | Clarification on EDT procedure | NTT DOCOMO INC. | - |
| S2‑187154 | 23.737: Reference Satellite Integration Architectures for FS_5GSAT_ARCH TR | THALES | - |
| S2‑187155 | TR 23.743 skeleton | Qualcomm Incorporated | - |
| S2‑187156 | Scope of the TR for the study on optimisations on UE radio capability signalling | Qualcomm Incorporated | - |
| S2‑187157 | Key issue to determine how are the UE capabilities identified | Qualcomm Incorporated, Mediatek, Intel | - |
| S2‑187158 | Key issue to determine where are the UE radio capabilities stored | Qualcomm Incorporated, Mediatek, Intel | - |
| S2‑187159 | Key issue to determine procedures for UE radio capabilities management | Qualcomm Incorporated, Mediatek, Intel | - |
| S2‑187160 | Solution on key issues for FS_RACS | Intel | - |
| S2‑187161 | Key issues on the maximum size of UE radio capabilities, and interface capabilities | Vodafone | - |
| S2‑187162 | [DRAFT] LS on maximum size of UE Radio Capabilities and maximum Information Element size on network interfaces | SA WG2 | - |
| S2‑187163 | [DRAFT] LS on Data Analytics in SA WG2/NWDAF | Huawei, HiSilicon | - |
| S2‑187164 | UPDATE to SID: Study of enablers for Network Automation for 5G | Nokia, Nokia Shanghai Bell | - |
| S2‑187165 | Use Case and KI for NWDAF exposing analytics to OAM | Huawei, HiSilicon | - |
| S2‑187166 | New Key Issue: Recommendations produced by NWDAF | ORANGE, Huawei | - |
| S2‑187167 | Update of Key Issue 10 | AT&T | - |
| S2‑187168 | An addition of a new Key Issue on Network Status | AT&T, KDDI, Convida Wireless LLC, Huawei | - |
| S2‑187169 | Update on Key Issue #1 and #2 for analytic information metadata exposure to 5GS NFs and AFs | Samsung | - |
| S2‑187170 | Update on Key Issue #1 and #2 to allow the registration of a new analytic information definition by 5G NF and AF | Samsung | imported from 3GU |
| S2‑187171 | Architectural assumptions for M.E.A.N.S | Huawei, HiSilicon | - |
| S2‑187172 | New Key Issue: Access to specific Network Slices authorized and authenticated through additional User Identifiers | InterDigital Inc. | - |
| S2‑187173 | Solutions for MEANS (Mutually Exclusive Access to Network Slices) | Huawei, HiSilicon | - |
| S2‑187174 | TR 23.740: Solution for Slicing Group support for mutually exclusive access to network slices | ZTE Wistron | - |
| S2‑187175 | Mutual Exclusion among slices solution | Nokia, Nokia Shanghai Bell | - |
| S2‑187176 | Solution to KI1: Mutually exclusive access to Network Slices | InterDigital Inc., ITRI | - |
| S2‑187177 | Solution for Key issue#2: Enabling interworking for slicing between EPC and 5GC | ZTE | - |
| S2‑187178 | Solution for key issue #2 'Enabling interworking for slicing between EPC and 5GC' | Qualcomm Incorporated | - |
| S2‑187179 | Mobility from EPC to 5GC for slice support | Huawei, HiSilicon | - |
| S2‑187180 | Solution for Connected mode mobility from EPC to 5GC | CATT | - |
| S2‑187181 | KI3: MT signalling for power saving UE | Ericsson | - |
| S2‑187182 | KI3: Paging of power saving UEs | Ericsson | - |
| S2‑187183 | Solution for KI3: UE availability after DDN failure for multiple AFs | Huawei, HiSilicon | - |
| S2‑187184 | PCR 23.724: Update to KI#13 | Ericsson | - |
| S2‑187185 | Local RRM Policy UE Differentiation for KI#13 | Ericsson | - |
| S2‑187186 | Update of Solution 26: Expected UE Behaviour provisioning for CIoT | Huawei, HiSilicon | - |
| S2‑187187 | KI1: Solution 19 improvement | Ericsson | - |
| S2‑187188 | Solution update: NIDD service activation for AMF and SMF | Samsung | - |
| S2‑187189 | New solution: Aggregation of Data over NAS | Samsung, Huawei, HiSilicon | - |
| S2‑187190 | eNA Drafting session Output | Huawei | - |
| S2‑187191 | New solution: NWDAF Influence on traffic routing | Intel, AT&T | - |
| S2‑187192 | New Key Issue: UE driven analytics sharing | Lenovo, Motorola Mobility, Samsung, China Mobile | - |
| S2‑187193 | Update Solution 3: How to define the service experience | Huawei, HiSilicon, Convida Wireless LLC, AT&T, Telecom Italia, China Mobile | - |
| S2‑187194 | Solution to Key Issue #3: Data Collection by subscription to NFs/AFs | ORANGE, Huawei | - |
| S2‑187195 | Solution 2 update: Content of Network Data Analytics Feedback | ORANGE | - |
| S2‑187196 | Solution to Key Issues 9 | Ericsson | - |
| S2‑187197 | Update Solution for Key Issue 5: NWDAF-Assisted QoS Profile Provisioning | Huawei, HiSilicon, China Telecom | - |
| S2‑187198 | Solution for Key Issue 8: Performance improvement and supervision of mIoT terminals | China Mobile, Lenovo, Motorola Mobility | - |
| S2‑187199 | TR Skeleton for study on architecture aspects for using satellite access in 5G | Thales | - |
| S2‑187200 | Scope of FS_5GSAT_ARCH TR | Thales | - |
| S2‑187201 | Satellite system characteristics to be included in FS_5GSAT_ARCH TR | Thales | - |
| S2‑187202 | 23.737: Reference Satellite Integration Architectures for FS_5GSAT_ARCH TR | THALES | - |
| S2‑187203 | Key Issues for FS_5GSAT_ARCH TR | Thales | imported from 3GU |
| S2‑187204 | Evaluation of Solution 6 | Sony | - |
| S2‑187205 | Clarifying RAI handling | Qualcomm Incorporated | - |
| S2‑187206 | Optionality of SMF selection for small data solution 2 | China Mobile | imported from 3GU |
| S2‑187207 | Solution for infrequent small data transmission with temporary PDU session | China Mobile | - |
| S2‑187208 | Update for Solution 5: Small Data Fast Path communication | ZTE | - |
| S2‑187209 | Update to Solution 30 | CATT | - |
| S2‑187210 | Solution 19 update: to resolve ENs | Samsung | - |
| S2‑187211 | Update to Solution#19: UP deactivation for UE in RRC inactive state | InterDigital Inc., | - |
| S2‑187212 | Solution for KI 1 and KI 2: Packet Aggregation for Small Data Delivery | Huawei, HiSilicon, Convida Wireless LLC | imported from 3GU |
| S2‑187213 | Solution 7 improvement | Ericsson | - |
| S2‑187214 | Combining RRC-INACTIVE and 5G UP optimization for efficient handling of bursty frequent small data | Qualcomm Incorporated | - |
| S2‑187215 | Update of Solution 27: Reuse of EPS Overload Control Mechanisms Editor's Notes | Huawei, HiSilicon, Intel | - |
| S2‑187216 | Concluding Key Issue #9 | Convida Wireless LLC, AT&T, Huawei, HiSilicon, Nokia, Nokia Shanghai Bell | - |
| S2‑187217 | Interim conclusion for Key issue #6 | Intel | - |
| S2‑187218 | Update solution #37 for KI 11:Monitoring | Huawei, HiSilicon | - |
| S2‑187219 | Solution update and interim conclusion for Key issue #11: Monitoring | Intel | - |
| S2‑187220 | RRC based Solution for KI#15 | NTT DOCOMO | - |
| S2‑187221 | NAS based Solution for KI#15 | NTT DOCOMO | - |
| S2‑187222 | UE Radio Capability Update using TAU procedure | Intel | - |
| S2‑187223 | [DRAFT] LS on E-UTRAN UE Radio Capability Update using TAU procedure | SA WG2 | - |
| S2‑187224 | Correction on Secondary RAT data usage report | Huawei, HiSilicon | - |
| S2‑187225 | Network Exposure in Roaming Situations | Convida Wireless LLC, AT&T, Intel, Ericsson | - |
| S2‑187226 | Reply LS on new BEST Service | SA WG2 | - |
| S2‑187227 | The proposal for subscribed PTW length | China Mobile | - |
| S2‑187228 | UE Radio Capability Update using TAU procedure | Intel | - |
| S2‑187229 | Solution to KI15: UE CN selection using broadcast information | Qualcomm Incorporated | - |
| S2‑187230 | Solution for KI15: Core Network selection for Cellular IOT | Huawei, HiSilicon | - |
| S2‑187231 | Update to Solution 33: Delayed paging response | Sony, NEC, OPPO | - |
| S2‑187232 | Completing solution 33 | Qualcomm Incorporated, Huawei, HiSilicon, Blackberry UK Ltd. | - |
| S2‑187233 | Update to Solution 32: MO Data Buffering in the UE | NEC, Convida Wireless LLC | - |
| S2‑187234 | Solution for KI 1 and KI 2: Packet Aggregation for Small Data Delivery | Huawei, HiSilicon, Convida Wireless LLC, Samsung | - |
| S2‑187235 | Scope of FS_5GSAT_ARCH TR | Thales | - |
| S2‑187236 | Satellite system characteristics to be included in FS_5GSAT_ARCH TR | Thales | - |
| S2‑187237 | 23.737: Reference Satellite Integration Architectures for FS_5GSAT_ARCH TR | THALES | - |
| S2‑187238 | Enhancement of network event reporting | Ericsson, Verizon, Nokia, Nokia Shanghai Bell, Convida | - |
| S2‑187239 | The proposal for subscribed PTW length | China Mobile | - |
| S2‑187240 | Traffic Profile for NB-IoT UE Uu operation optimisation | Huawei, HiSilicon | - |
| S2‑187241 | Traffic Profile for NB-IoT UE Uu operation optimisation | Huawei, HiSilicon | - |
| S2‑187242 | Traffic Profile for NB-IoT UE Uu operation optimisation | Huawei, HiSilicon | - |
| S2‑187243 | Clarification on EDT procedure | NTT DOCOMO INC. | - |
| S2‑187244 | Enhancement of network event reporting | Ericsson, Verizon, Nokia, Nokia Shanghai Bell, Convida | - |
| S2‑187245 | Scope of FS_5GSAT_ARCH TR | Thales | - |
| S2‑187246 | 23.737: Reference Satellite Integration Architectures for FS_5GSAT_ARCH TR | THALES | - |
| S2‑187247 | Architectural assumptions for M.E.A.N.S | Huawei, HiSilicon | - |
| S2‑187248 | New Key Issue: Access to specific Network Slices authorized and authenticated through additional User Identifiers | InterDigital Inc. | - |
| S2‑187249 | Solutions for MEANS (Mutually Exclusive Access to Network Slices) | Huawei, HiSilicon | - |
| S2‑187250 | TR 23.740: Solution for Slicing Group support for mutually exclusive access to network slices | ZTE Wistron | - |
| S2‑187251 | Mutual Exclusion among slices solution | Nokia, Nokia Shanghai Bell | - |
| S2‑187252 | Solution to KI1: Mutually exclusive access to Network Slices | InterDigital Inc., ITRI | - |
| S2‑187253 | Use Case and KI for NWDAF exposing analytics to OAM | Huawei, HiSilicon | - |
| S2‑187254 | UPDATE to SID: Study of enablers for Network Automation for 5G | Nokia, Nokia Shanghai Bell | - |
| S2‑187255 | New Key Issue: Recommendations produced by NWDAF | ORANGE, Huawei | - |
| S2‑187256 | New Key Issue: UE driven analytics sharing | Lenovo, Motorola Mobility, Samsung, China Mobile | - |
| S2‑187257 | Solution to Key Issue #3: Data Collection by subscription to NFs/AFs | ORANGE, Huawei | - |
| S2‑187258 | Solution 2 update: Content of Network Data Analytics Feedback | ORANGE | - |
| S2‑187259 | Solution to Key Issues 9 | Ericsson | - |
| S2‑187260 | Update Solution for Key Issue 5: NWDAF-Assisted QoS Profile Provisioning | Huawei, HiSilicon, China Telecom | - |
| S2‑187261 | Solution for Key Issue 8: Performance improvement and supervision of mIoT terminals | China Mobile, Lenovo, Motorola Mobility | - |
| S2‑187262 | [DRAFT] LS on Data Analytics in SA WG2/NWDAF | Huawei, HiSilicon | - |
| S2‑187263 | Use Case and KI for NWDAF exposing analytics to OAM | Huawei, HiSilicon | - |
| S2‑187264 | New Key Issue: UE driven analytics sharing | Lenovo, Motorola Mobility, Samsung, China Mobile | - |
| S2‑187265 | KI3: MT signalling for power saving UE | Ericsson | - |
| S2‑187266 | KI3: Paging of power saving UEs | Ericsson | - |
| S2‑187267 | Local RRM Policy UE Differentiation for KI#13 | Ericsson | - |
| S2‑187268 | Update of Solution 26: Expected UE Behaviour provisioning for CIoT | Huawei, HiSilicon, InterDigital Inc., Convida, Motorola Mobility, Lenovo | - |
| S2‑187269 | Evaluation of Solution 6 | Sony | - |
| S2‑187270 | Clarifying RAI handling | Qualcomm Incorporated | - |
| S2‑187271 | Solution for infrequent small data transmission with temporary PDU session | China Mobile | - |
| S2‑187272 | Update for Solution 5: Small Data Fast Path communication | ZTE | - |
| S2‑187273 | Update to Solution 30 | CATT | - |
| S2‑187274 | Update to Solution#19: UP deactivation for UE in RRC inactive state | InterDigital Inc., LG Electronics | - |
| S2‑187275 | Solution 19 update: to resolve ENs | Samsung | - |
| S2‑187276 | Combining RRC-INACTIVE and 5G UP optimization for efficient handling of bursty frequent small data | Qualcomm Incorporated | - |
| S2‑187277 | Update of Solution 27: Reuse of EPS Overload Control Mechanisms Editor's Notes | Huawei, HiSilicon, Intel | - |
| S2‑187278 | Solution update and interim conclusion for Key issue #11: Monitoring | Intel | - |
| S2‑187279 | NAS based Solution for KI#15 | NTT DOCOMO | - |
| S2‑187280 | RRC based Solution for KI#15 | NTT DOCOMO | - |
| S2‑187281 | Solution for KI15: Core Network selection for Cellular IOT | Huawei, HiSilicon, Intel | - |
| S2‑187282 | Solution 7 improvement | Ericsson | - |
| S2‑187283 | KI3: Paging of power saving UEs | Ericsson | - |
| S2‑187284 | Evaluation of Solution 6 | Sony | - |
| S2‑187285 | Solution for infrequent small data transmission with temporary PDU session | China Mobile | - |
| S2‑187286 | Update to Solution#19: UP deactivation for UE in RRC inactive state | InterDigital Inc., LG Electronics | - |
| S2‑187287 | Solution 7 improvement | Ericsson | - |
| S2‑187288 | TR 23.740: Solution for Slicing Group support for mutually exclusive access to network slices | ZTE Wistron | - |
| S2‑187289 | Solution to KI1: Mutually exclusive access to Network Slices | InterDigital Inc., ITRI | - |
| S2‑187290 | Completing solution 33 | Qualcomm Incorporated, Huawei, HiSilicon, Blackberry UK Ltd., NEC | - |
| S2‑187291 | Reserved for Puneet's parallel sessions | - | imported from 3GU |
| S2‑187292 | Reserved for Puneet's parallel sessions | - | imported from 3GU |
| S2‑187293 | Draft Report of SA WG2 meeting #127BIS | SA WG2 Secretary | - |
| S2‑187294 | [DRAFT] LS on potential enhancement of DR-mode of operation | SA WG2 | - |
| S2‑187295 | Introduction of SBI-based SMSGW in 5GC | Ericsson, China Mobile, LG Electronics, CATT | imported from 3GU |
| S2‑187296 | Revised SID: Study on Enhancement to Service Based Architecture for Location Services | CATT, Qualcomm Incorporated, China Telecom, China Mobile, CAICT, China Unicom, Huawei, HiSilicon, Verizon UK Ltd, ZTE, T-Mobile USA, AT&T, Nokia, Nokia Shanghai Bell, Ericsson, Comtech Telecommunications, Intel | - |
| S2‑187297 | Storage of structured proprietary data in UDSF | Deutsche Telekom | - |
| S2‑187298 | Storage of permanent identities for private networks | Qualcomm Incorporated, Ericsson, Intel | - |
| S2‑187299 | [DRAFT] Reply LS on GSMA question on 5G network slices | SA WG2 | - |
| S2‑187300 | Network Slicing Subscription Change Indication | Ericsson, Nokia, Nokia Shanghai Bell, Huawei | - |
| S2‑187301 | 23.501 CR0487: Correction to Configured NSSAI for the HPLMN | MediaTek Inc., Huawei, HiSilicon, Ericsson | - |
| S2‑187302 | Requested NSSAI in Network Initiated Change of Network slices | Ericsson, Nokia, Nokia Shanghai Bell, Telecom Italia, Motorola Mobility, Lenovo, InterDigital Inc. | - |
| S2‑187303 | Update of parameter in call flow and service operation for NSI ID | KDDI, Telecom Italia, ZTE Wistron, ETRI | - |
| S2‑187304 | Update of UPF selection factor for network slice instance | KDDI, ETRI, ZTE Wistron, China Telecom | - |
| S2‑187305 | Default S-NSSAI correction and NSSF service update | Huawei, HiSilicon | - |
| S2‑187306 | Multiple PDU session per DNN | Huawei, HiSilicon | - |
| S2‑187307 | Multiple PDU session per DNN | Huawei, HiSilicon | - |
| S2‑187308 | Incorrect text implying slicing is optional | Nokia, Nokia Shanghai Bell, Telecom Italia, Ericsson, Huawei | - |
| S2‑187309 | Support of tracing in 5GS signalling: overview | Nokia, Nokia Shanghai Bell | - |
| S2‑187310 | Support of tracing in 5GS signalling: SM related signalling and data | Nokia, Nokia Shanghai Bell | - |
| S2‑187311 | Support of tracing in 5GS signalling: SMSF related signalling and data | Nokia, Nokia Shanghai Bell | - |
| S2‑187312 | Support of tracing in 5GS signalling: PCF related signalling and data (SM part) | Nokia, Nokia Shanghai Bell | - |
| S2‑187313 | An overview of the IETF DetNet activity | Ericsson | - |
| S2‑187314 | Specific QoS & Policy control for URLLC services | Huawei, HiSilicon | - |
| S2‑187315 | Updates to Solution #1 on Redundant user plane paths based on dual connectivity | Ericsson | - |
| S2‑187316 | Updates to solution #2 on Multiple UEs per device for user plane redundancy | Ericsson | - |
| S2‑187317 | Support for VLAN ID learning to enable IEEE 802.1CB (Frame Replication and Elimination for Reliability) combined with IEEE 802.1Q | Qualcomm Incorporated | - |
| S2‑187318 | Update of solution#3 and solution#4 | Huawei, HiSilicon | - |
| S2‑187319 | Update the solution #4 | Samsung | - |
| S2‑187320 | Reply LS on Location Reporting for Area of Interest | SA WG2 | - |
| S2‑187321 | Clarification on representation of AoI for NG-RAN location reporting procedure | Samsung | - |
| S2‑187322 | Paging policy differentiation for RRC inactive | Huawei, HiSilicon | - |
| S2‑187323 | Corrections in Reachability procedures | Qualcomm Incorporated | - |
| S2‑187324 | Correction on Connection Resume procedure | Huawei, HiSilicon | - |
| S2‑187325 | Correction on signalling message holding during HO | Huawei, HiSilicon | - |
| S2‑187326 | TS23.502 Clarifications on Xn based handover | Ericsson | - |
| S2‑187327 | TS23.502 handover | ZTE | - |
| S2‑187328 | Clarification on N1 data transfer for RRC-Inactive UE | China Mobile, Ericsson, China Telecom, China Unicom, CATT, Huawei, ZTE, Motorola Mobility, Lenovo, OPPO, LG Electronics | - |
| S2‑187329 | Triggers for Network Triggered Service Request and UE Activity procedure | Ericsson | - |
| S2‑187330 | Clarification on UE Capability Match Request procedure | LG Electronics | - |
| S2‑187331 | Missing TADs behaviour | BlackBerry UK Limited | - |
| S2‑187332 | MO service correction | BlackBerry UK Limited | - |
| S2‑187333 | Clarification on UE Registration type with only PDU Session for Emergency Services | Huawei, HiSilicon | - |
| S2‑187334 | Clarification to the UE's behavior of emergency registered UE | NEC | - |
| S2‑187335 | Clarification on access network information during IMS call in 5G dual connectivity scenario | Huawei, HiSilicon | - |
| S2‑187336 | SMS subsciption Change | NEC | - |
| S2‑187337 | UE Context in SMSF data | Huawei, HiSilicon | - |
| S2‑187338 | Emergency call and eCall support when the ng-eNode is connected to EPC and 5GC | NEC | - |
| S2‑187339 | Homogeneous Support of IMS Voice over PS Sessions indication | LG Electronics | - |
| S2‑187340 | Clarification on Homogeneous Support of IMS Voice over PS Sessions indication | LG Electronics | - |
| S2‑187341 | MT SMS failure recovery | Nokia, Nokia Shanghai Bell | - |
| S2‑187342 | Update on Domain Selection Rules for emergency session attempts | Samsung | - |
| S2‑187343 | Emergency Services Support indicator for non-3GPP access | ORANGE | - |
| S2‑187344 | [DRAFT] Reply LS on signalling of dynamic 5QI values | SA WG2 | - |
| S2‑187345 | Priority Level signalled with standardized 5QIs and QoS characteristics signalled with dynamically assigned 5QIs. | Vencore Labs, OEC, AT&T, T-Mobile USA, Sprint, Verizon UK Ltd. | - |
| S2‑187346 | Clarification for pre-configured QoS rule | CATT | - |
| S2‑187347 | Clarification for QoS handling at UPF | CATT | - |
| S2‑187348 | Notification Control applicability | Nokia, Nokia Shanghai Bell | - |
| S2‑187349 | The resource type of QoS Flow associated with the default QoS rule | Huawei, HiSilicon | - |
| S2‑187350 | Clarifications for 5QI priority level overwriting | Huawei, HiSilicon | - |
| S2‑187351 | 5QI-QCI alignment | Huawei, HiSilicon | - |
| S2‑187352 | Number of packet filters supported by UE | Huawei, HiSilicon | - |
| S2‑187353 | Corrections for ARP priority level | Huawei, HiSilicon | - |
| S2‑187354 | Corrections for low latency QCIs | Huawei, HiSilicon | - |
| S2‑187355 | Reply LS on signalling of dynamic 5QI values | SA WG2 | - |
| S2‑187356 | Notification Control applicability | Nokia, Nokia Shanghai Bell | - |
| S2‑187357 | Discovering SMF instance at EPS to 5GS interworking | Ericsson | - |
| S2‑187358 | [DRAFT] Reply LS on the use of PGW FQDN in the SMF Selection | Ericsson | - |
| S2‑187359 | Handling of subscription restrictions for mobility from EPS to 5GS | Cisco Systems, Ericsson? | - |
| S2‑187360 | [DRAFT] Reply LS on Access Restriction Data for NR in EPC | Cisco Systems Belgium | - |
| S2‑187361 | Merging Network Slice with regular EPS Interworking | Nokia, Nokia Shanghai Bell | - |
| S2‑187362 | Temporary identitier usage at interworking | Ericsson | - |
| S2‑187363 | Clarification on the SSC mode be supported between 5GS and EPS IWK | China Telecom | imported from 3GU |
| S2‑187364 | Clarification on cancel registration with N26 | Huawei, HiSilicon | imported from 3GU |
| S2‑187365 | 5GS to EPS Mobility | Nokia, Nokia Shanghai Bell | - |
| S2‑187366 | Clarification on the target MME capability from AMF to SMF for 5GS to EPS mobility | ZTE | - |
| S2‑187367 | Clafication on retrievial of the security context from old AMF | Huawei, HiSilicon | - |
| S2‑187368 | EPS to 5GS mobility with N26 | Ericsson, ZTE | - |
| S2‑187369 | Clarification on the PDU session handling in EPS to 5GS handover with N26 | ZTE, Nokia, Nokia Shanghai Bell | - |
| S2‑187370 | Clarification on the PDU session handling in EPS to 5GS handover with N26 | ZTE, Nokia, Nokia Shanghai Bell | - |
| S2‑187371 | Indirect data forwarding for interworking with N26 | Samsung | - |
| S2‑187372 | Registration type for Nudm_UECM_Registration | Nokia, Nokia Shanghai Bell | - |
| S2‑187373 | Clarification on the non-IP PDU session type for EPS to 5GS interworking | ZTE | - |
| S2‑187374 | Correction to handover from 5GS to EPS | CATT | - |
| S2‑187375 | Update to PDN connection establishment | CATT | - |
| S2‑187376 | RRC Inactive to EPC mobility | Vodafone | - |
| S2‑187377 | Discovering SMF instance at EPS to 5GS interworking | Ericsson | - |
| S2‑187378 | Reply LS on the use of PGW FQDN in the SMF Selection | SA WG2 | - |
| S2‑187379 | Handling of subscription restrictions for mobility from EPS to 5GS | Cisco Systems, Ericsson | - |
| S2‑187380 | Reply LS on Access Restriction Data for NR in EPC | SA WG2 | - |
| S2‑187381 | Clafication on retrievial of the security context from old AMF | Huawei, HiSilicon | - |
| S2‑187382 | Clarification on the PDU session handling in EPS to 5GS handover with N26 | ZTE, Nokia, Nokia Shanghai Bell | - |
| S2‑187383 | Clarification on the PDU session handling in EPS to 5GS handover with N26 | ZTE, Nokia, Nokia Shanghai Bell | - |
| S2‑187384 | Clarification on the non-IP PDU session type for EPS to 5GS interworking | ZTE | - |
| S2‑187385 | Reserved for Irfan's parallel sessions | - | imported from 3GU |
| S2‑187386 | Reserved for Irfan's parallel sessions | - | imported from 3GU |
| S2‑187387 | Solution for 5G URLLC in 5G System | Nokia, Nokia Shanghai Bell | - |
| S2‑187388 | Solution for establishing N3 and N9 tunnels for redundant transmission | Samsung, Huawei, HiSilicon, Lenovo, Motorola Mobility | - |
| S2‑187389 | Updating for solution#5 in FS_URLLC | OPPO | - |
| S2‑187390 | Solution for Key Issue 5 | Sony, Interdigital | - |
| S2‑187391 | Updated SID on User Data Interworking, Coexistence and Migration | Nokia, Nokia Shanghai Bell | - |
| S2‑187392 | Proposed scope for FS_UDICOM, 23.732 | Vodafone | - |
| S2‑187393 | Architectural assumptions for 23.732 | Vodafone | - |
| S2‑187394 | Architecture requirements of data interworking | China Mobile | imported from 3GU |
| S2‑187395 | 2 New Key Issues for HSS UDR Interactions | T-Mobile USA INC | - |
| S2‑187396 | Key issue: Clarification on procedures and required data for UDM/UDR and HSS interworking | China Mobile | imported from 3GU |
| S2‑187397 | Key issue: How to interwork between UDM/UDR and HSS | China Mobile, Verizon | - |
| S2‑187398 | Solution for QoS Monitoring for URLLC Services | Huawei, HiSilicon | - |
| S2‑187399 | Correction to AS Security Context | Nokia, Nokia Shanghai Bell, Ericsson | - |
| S2‑187400 | Reply LS on initial NAS message protection | SA WG2 | - |
| S2‑187401 | [DRAFT] Reply LS on TLS and inter PLMN routing | SA WG2 | - |
| S2‑187402 | MME handling of UE 5GMM capability | Intel | imported from 3GU |
| S2‑187403 | Handling of UP Security Policy when IWK with EPS | Ericsson | - |
| S2‑187404 | [DRAFT] LS on security handling when deploying UDSF | SA WG2 | - |
| S2‑187405 | [DRAFT] Reply LS on initial NAS message protection | SA WG2 | - |
| S2‑187406 | ESBA - Interoperability aspects in key issue 6 | Ericsson | - |
| S2‑187407 | An addition to Key Issue 2 | AT&T, Sprint | - |
| S2‑187408 | New issue on roaming | Ericsson | - |
| S2‑187409 | Service framework requirements | Ericsson | - |
| S2‑187410 | Update of Solution 3.1 'Amendments to Service Interaction model' to address editors notes | Deutsche Telekom | - |
| S2‑187411 | Update to Illustrated Procedures: 'Delivery of Messages' | InterDigital Inc. | - |
| S2‑187412 | N16 communication failure | Huawei, HiSilicon | - |
| S2‑187413 | Correction to SMF registration of PDU Session ID | Telecom Italia, KDDI, ZTE Wistron | - |
| S2‑187414 | PDU Session selection | InterDigital Inc. | - |
| S2‑187415 | Correction to AF influence on traffic routing | Huawei, HiSillicon | - |
| S2‑187416 | User Location Information added in N2 UE Context Release Complete | Nokia, Nokia Shanghai Bell | - |
| S2‑187417 | Application detection report when the PFDs are removed | Huawei, HiSilicon | - |
| S2‑187418 | Clarification on handling of Ethernet frames at UPF | Qualcomm Incorporated | - |
| S2‑187419 | Clarification on SSC Mode Selection Policy | LG Electronics | imported from 3GU |
| S2‑187420 | UE context in SMF data | Huawei, HiSilicon | - |
| S2‑187421 | Subscription of selecting the same SMF and UPF | Huawei, HiSilicon | - |
| S2‑187422 | Subscription of selecting the same SMF and UPF | Huawei, HiSilicon | - |
| S2‑187423 | Clarification on UPF tunnel change | Huawei, Hisillicon | - |
| S2‑187424 | Corrections in clause 4.3.3 PDU Session Modification and clause 4.3.4 PDU Session Release | ETRI | imported from 3GU |
| S2‑187425 | Clarification on a wildcard DNN | Samsung | - |
| S2‑187426 | DNN Usage Clarification | Intel | - |
| S2‑187427 | Correction for UE requested LADN Information | Samsung, Intel, Huawei, LG Electronics | - |
| S2‑187428 | Clarification on LADN | Samsung, Huawei, LG Electronics | - |
| S2‑187429 | [DRAFT] Reply LS on enabling and disabling NG RAN Capabilities | SA WG2 | - |
| S2‑187430 | [DRAFT] Reply LS on Service Area Restrictions | SA WG2 | - |
| S2‑187431 | LS Reply on RAN initiated TNL Associations over NGAP | SA WG2 | - |
| S2‑187432 | [DRAFT] Reply LS on Connection Control | SA WG2 | - |
| S2‑187433 | Correcting use of identifiers during registration in equivalent PLMNs | Qualcomm Incorporated | - |
| S2‑187434 | Clarification on UE context exchanged on N26 interface | NTT DOCOMO | - |
| S2‑187435 | Further corrections to identifiers in Registration procedure | Intel | imported from 3GU |
| S2‑187436 | 5GS Temporary Identifier aspects | Ericsson | - |
| S2‑187437 | 23.501 CR0488: Correction to TAI list generation | MediaTek Inc. | - |
| S2‑187438 | 23.501: 5G AN Parameters sent during Service Request | Nokia, Nokia Shanghai Bell, Ericsson | - |
| S2‑187439 | 23.502: 5G AN Parameters sent during Service Request | Nokia, Nokia Shanghai Bell, Ericsson | - |
| S2‑187440 | Mobility Restriction List clean up | Qualcomm Incorporated | - |
| S2‑187441 | Clarification on priority service | Huawei, Hisillicon | - |
| S2‑187442 | Service Accept to complete Service Request | MediaTek Inc. | - |
| S2‑187443 | Further clarification for distributed service framework | China Mobile | - |
| S2‑187444 | Distributed service framework | Oracle, Verizon, Cisco. | - |
| S2‑187445 | Solution proposal 'Flexible Service Framework' to address key issue 'Improvements to service framework related aspects' | Ericsson | - |
| S2‑187446 | 23.742: Enhancements to Services Framework | Nokia, Nokia Shanghai Bell | - |
| S2‑187447 | Solution #4.3 update | NTT DOCOMO | - |
| S2‑187448 | One Solution for Key Issue #2: Extend Service Concept into User Plane | CATT | - |
| S2‑187449 | Update of Solution 4.1SBA with stateless and unsticky services to address editors notes | Deutsche Telekom | - |
| S2‑187450 | Common Network Data Service | China Mobile | - |
| S2‑187451 | Group based solution for NF/NF service instance reliability | Huawei, HiSilicon, SK Telecom | - |
| S2‑187452 | Correction of UE configuration update procedure | Intel, Apple, OPPO | - |
| S2‑187453 | Clarification to UE Configuration Update | LG Electronics | - |
| S2‑187454 | Clarification on UE configuration update procedure | OPPO | - |
| S2‑187455 | Correction of UE configuration update procedure | Intel, Apple, OPPO | - |
| S2‑187456 | Unified Access Control for UE configured for EAB | Intel, Ericsson, Nokia, Nokia Shanghai Bell, NEC, LG Electronics | - |
| S2‑187457 | [DRAFT] Reply LS on Delay Tolerant Access and Low Access Priority in 5GS | SA WG2 | - |
| S2‑187458 | GUAMI Definition Correction | Nokia, Nokia Shanghai Bell, Orange | - |
| S2‑187459 | Clarification of the AMF Set definition | NTT DOCOMO | - |
| S2‑187460 | Peer NF association of GUAMI with a given UE | Nokia, Nokia Shanghai Bell | - |
| S2‑187461 | Clarification on DNN based congestion control for System interworking w/o N26 | LG Electronics | imported from 3GU |
| S2‑187462 | Correction on inter-PLMN mobility | CATT | - |
| S2‑187463 | Definitions, architectural assumptions and key issue related to network identification, selection and access control | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell | - |
| S2‑187464 | Key Issue Proposal on 5GLAN Group Management | Huawei, HiSilicon, KPN | - |
| S2‑187465 | New Key Issues for Network Discovery & Selection and Access Control & Restriction | Intel, Qualcomm Incorporated | - |
| S2‑187466 | Key issues for 5G-LAN Service Discovery, Selection and Restriction | Intel | - |
| S2‑187467 | Key Issue Proposal on Clock Synchronization | Huawei, HiSilicon | - |
| S2‑187468 | Key issue on support for TSN | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated | - |
| S2‑187469 | Support for 5GLAN communication service key issue | Huawei, HiSilicon, Intel, InterDigital Inc. | - |
| S2‑187470 | Key issue on support for Service Exposure for Vertical and LAN Services | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Convida Wireless | - |
| S2‑187471 | Solution for 5G URLLC in 5G System | Nokia, Nokia Shanghai Bell | - |
| S2‑187472 | Updates to Solution #1 on Redundant user plane paths based on dual connectivity | Ericsson | - |
| S2‑187473 | Update of solution#3 and solution#4 | Huawei, HiSilicon | - |
| S2‑187474 | An overview of the IETF DetNet activity | Ericsson | - |
| S2‑187475 | Specific QoS & Policy control for URLLC services | Huawei, HiSilicon | - |
| S2‑187476 | Updating for solution#5 in FS_URLLC | OPPO | - |
| S2‑187477 | Solution for QoS Monitoring for URLLC Services | Huawei, HiSilicon | - |
| S2‑187478 | Solution for Key Issue 5 | Sony, Interdigital | - |
| S2‑187479 | Proposed scope for FS_UDICOM, 23.732 | Vodafone | - |
| S2‑187480 | Updated SID on User Data Interworking, Coexistence and Migration | Nokia, Nokia Shanghai Bell | - |
| S2‑187481 | Architectural assumptions for 23.732 | Vodafone | - |
| S2‑187482 | 2 New Key Issues for HSS UDR Interactions | T-Mobile USA INC | - |
| S2‑187483 | Key issue: How to interwork between UDM/UDR and HSS | China Mobile, Verizon | - |
| S2‑187484 | 2 New Key Issues for HSS UDR Interactions | T-Mobile USA INC | - |
| S2‑187485 | 23.501 CR0487: Correction to Configured NSSAI for the HPLMN | MediaTek Inc., Huawei, HiSilicon, Ericsson, Intel | - |
| S2‑187486 | Default S-NSSAI correction and NSSF service update | Huawei, HiSilicon | - |
| S2‑187487 | Multiple PDU session per DNN | Huawei, HiSilicon | imported from 3GU |
| S2‑187488 | Multiple PDU session per DNN | Huawei, HiSilicon | imported from 3GU |
| S2‑187489 | Support of tracing in 5GS signalling: overview | Nokia, Nokia Shanghai Bell | - |
| S2‑187490 | Support of tracing in 5GS signalling: SM related signalling and data | Nokia, Nokia Shanghai Bell | - |
| S2‑187491 | Support of tracing in 5GS signalling: SMSF related signalling and data | Nokia, Nokia Shanghai Bell | - |
| S2‑187492 | Support of tracing in 5GS signalling: PCF related signalling and data (SM part) | Nokia, Nokia Shanghai Bell | - |
| S2‑187493 | Storage of structured proprietary data in UDSF | Deutsche Telekom | - |
| S2‑187494 | Storage of permanent identities for private networks | Qualcomm Incorporated, Ericsson, Intel | - |
| S2‑187495 | [DRAFT] Reply LS on GSMA question on 5G network slices | SA WG2 | - |
| S2‑187496 | Question for decision on Configured NSSAI valid for all PLMNs | Qualcomm | - |
| S2‑187497 | Missing TADs behaviour | BlackBerry UK Limited | - |
| S2‑187498 | Clarification on UE Registration type with only PDU Session for Emergency Services | Huawei, Hisilicon, NEC | - |
| S2‑187499 | UE Context in SMSF data | Huawei, HiSilicon | - |
| S2‑187500 | Emergency call and eCall support when the ng-eNode is connected to EPC and 5GC | NEC | - |
| S2‑187501 | MT SMS failure recovery | Nokia, Nokia Shanghai Bell | - |
| S2‑187502 | The resource type of QoS Flow associated with the default QoS rule | Huawei, HiSilicon | - |
| S2‑187503 | Clarifications for 5QI priority level overwriting | Huawei, HiSilicon | imported from 3GU |
| S2‑187504 | Number of packet filters supported by UE | Huawei, HiSilicon | - |
| S2‑187505 | Reply LS on initial NAS message protection | SA WG2 | - |
| S2‑187506 | LS on security handling when deploying UDSF | SA WG2 | - |
| S2‑187507 | The resource type of QoS Flow associated with the default QoS rule | Huawei, HiSilicon | - |
| S2‑187508 | TS23.502 Clarifications on Xn based handover | ZTE | - |
| S2‑187509 | Update of the Service Instance Set solution | Ericsson, Vodafone | - |
| S2‑187510 | Common Network Data Service | China Mobile | - |
| S2‑187511 | An addition to Key Issue 2 | AT&T, Sprint | - |
| S2‑187512 | New issue on roaming | Ericsson | - |
| S2‑187513 | Service framework requirements | Ericsson | - |
| S2‑187514 | Update of Solution 3.1 'Amendments to Service Interaction model' to address editors notes | Deutsche Telekom | - |
| S2‑187515 | Handling LADN service area during handovers | NTT DOCOMO | - |
| S2‑187516 | Update to Illustrated Procedures: 'Delivery of Messages' | InterDigital Inc. | imported from 3GU |
| S2‑187517 | Further clarification for distributed service framework | China Mobile | - |
| S2‑187518 | Distributed service framework | Oracle, Verizon, Cisco. | - |
| S2‑187519 | Solution proposal 'Flexible Service Framework' to address key issue 'Improvements to service framework related aspects' | Ericsson | - |
| S2‑187520 | 23.742: Enhancements to Services Framework | Nokia, Nokia Shanghai Bell | - |
| S2‑187521 | One Solution for Key Issue #2: Extend Service Concept into User Plane | CATT | - |
| S2‑187522 | Reserved for LaeYoung's parallel sessions | - | imported from 3GU |
| S2‑187523 | Reserved for LaeYoung's parallel sessions | - | imported from 3GU |
| S2‑187524 | Reserved for LaeYoung's parallel sessions | - | imported from 3GU |
| S2‑187525 | Reserved for LaeYoung's parallel sessions | - | imported from 3GU |
| S2‑187526 | Reserved for LaeYoung's parallel sessions | - | imported from 3GU |
| S2‑187527 | Update of UPF selection factor for network slice instance | KDDI, ETRI, ZTE Wistron, China Telecom | - |
| S2‑187528 | Application detection report when the PFDs are removed | Huawei, HiSilicon | - |
| S2‑187529 | Clarification on handling of Ethernet frames at UPF | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell | - |
| S2‑187530 | Subscription of selecting the same SMF and UPF | Huawei, HiSilicon | - |
| S2‑187531 | Clarification on a wildcard DNN | Samsung | - |
| S2‑187532 | Clarification on LADN | Samsung, Huawei, LG Electronics | - |
| S2‑187533 | N16 communication failure | Huawei, HiSilicon | - |
| S2‑187534 | Clarification on a wildcard DNN | Samsung | - |
| S2‑187535 | Correction for UE requested LADN Information | Samsung, Intel, Huawei, LG Electronics | - |
| S2‑187536 | Clarification on LADN | Samsung, Huawei, LG Electronics | - |
| S2‑187537 | 5QI-QCI alignment | Huawei, HiSilicon | - |
| S2‑187538 | UE location report to the SMF by RAN in RRC Inactive State | Huawei, HiSilicon | - |
| S2‑187539 | Reply LS on enabling and disabling NG RAN Capabilities | SA WG2 | - |
| S2‑187540 | Reply LS on Service Area Restrictions | SA WG2 | - |
| S2‑187541 | Unified Access Control for UE configured for EAB | Intel, Ericsson, Nokia, Nokia Shanghai Bell, NEC, LG Electronics | - |
| S2‑187542 | Introducing low access priority to 5G system | Qualcomm Incorporated | - |
| S2‑187543 | Reply LS on Connection Control | SA WG2 | - |
| S2‑187544 | Clarification on priority service | Huawei, Hisillicon | - |
| S2‑187545 | GUAMI Definition Correction | Nokia, Nokia Shanghai Bell, Orange | - |
| S2‑187546 | Correction on inter-PLMN mobility | CATT | - |
| S2‑187547 | New Key Issues for Network Discovery & Selection and Access Control & Restriction | Intel, Qualcomm Incorporated, Deutsche Telekom AG | - |
| S2‑187548 | Definitions, architectural assumptions and key issue related to network identification, selection and access control | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Deutsche Telekom, vivo, Intel | - |
| S2‑187549 | Definitions, architectural assumptions and key issue related to network identification, selection and access control (solution) | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell | - |
| S2‑187550 | Key Issue Proposal on 5GLAN Group Management | Huawei, HiSilicon, KPN, Intel | - |
| S2‑187551 | Key issues for 5G-LAN Service Discovery, Selection and Restriction | Intel | - |
| S2‑187552 | Key Issue Proposal on Clock Synchronization | Huawei, HiSilicon | - |
| S2‑187553 | Key issue on support for TSN | Nokia, Nokia Shanghai Bell, Qualcomm Incorporated | - |
| S2‑187554 | Support for 5GLAN communication service key issue | Huawei, HiSilicon, Intel, InterDigital Inc. | - |
| S2‑187555 | Reserved for Irfan's parallel sessions | - | imported from 3GU |
| S2‑187556 | Reserved for Irfan's parallel sessions | - | imported from 3GU |
| S2‑187557 | Reserved for Irfan's parallel sessions | - | imported from 3GU |
| S2‑187558 | Reserved for Irfan's parallel sessions | - | imported from 3GU |
| S2‑187559 | Reserved for Irfan's parallel sessions | - | imported from 3GU |
| S2‑187560 | Update of parameter in call flow and service operation for NSI ID | KDDI, Telecom Italia, ZTE Wistron, ETRI | - |
| S2‑187561 | Default S-NSSAI correction and NSSF service update | Huawei, HiSilicon | - |
| S2‑187562 | [DRAFT] Reply LS on GSMA question on 5G network slices | SA WG2 | - |
| S2‑187563 | Reply LS on Location Reporting for Area of Interest | SA WG2 | - |
| S2‑187564 | Triggers for Network Triggered Service Request and UE Activity procedure | Ericsson | - |
| S2‑187565 | Corrections in Reachability procedures | Qualcomm Incorporated | - |
| S2‑187566 | Correction on Connection Resume procedure | Huawei, HiSilicon | - |
| S2‑187567 | TS23.502 Clarifications on Xn based handover | ZTE | - |
| S2‑187568 | TS23.502 handover | ZTE | - |
| S2‑187569 | UE location report to the SMF by RAN in RRC Inactive State | Huawei, HiSilicon | imported from 3GU |
| S2‑187570 | TS23.502 Clarifications on Xn based handover | ZTE | - |
| S2‑187571 | IPTV solution for WWC | Huawei, HiSilicon | - |
| S2‑187572 | N28 session termination | Nokia, Nokia Shanghai Bell | - |
| S2‑187573 | Adding N28 session termination procedure and updates to CHF services | Nokia, Nokia Shanghai Bell | - |
| S2‑187574 | Key issues on the maximum size of UE radio capabilities, and interface capabilities | Vodafone | - |
| S2‑187575 | LS on maximum size of UE Radio Capabilities and maximum Information Element size on network interfaces | SA WG2 | - |
| S2‑187576 | Solution on key issues for FS_RACS | Intel | - |
| S2‑187577 | LS reply to LS on Use of NRF framework by CHF for information | SA WG2 | - |
| S2‑187578 | LS reply to LS on UE policy | SA WG2 | - |
| S2‑187579 | LS reply to LS on clarification for spending limit control functionality | SA WG2 | - |
| S2‑187580 | Clarification on initial UE policy provisioning | Intel, Telecom Italia | - |
| S2‑187581 | SBI friendly UE policy delivery procedure | Samsung | - |
| S2‑187582 | UE Policy Delivery in case of UE not reachable | Huawei, HiSilicon | imported from 3GU |
| S2‑187583 | UE Policy Delivery in case of UE not reachable | Huawei, HiSilicon | - |
| S2‑187584 | PCF added as consumer of EventExposure service of AMF and SMF | Huawei, HiSilicon, Ericsson, Nokia, Nokia Shanghai Bell | - |
| S2‑187585 | [DRAFT] Reply LS on 5G service request procedure | SA WG2 | - |
| S2‑187586 | Correction to Service Request QoS when changing between non-3GPP and 3GPP accesses | Nokia, Nokia Shanghai Bell, LGE | - |
| S2‑187587 | Missing NEF services. | ORANGE | - |
| S2‑187588 | Solution for RG configuration and management | Huawei, HiSilicon | - |
| S2‑187589 | TR 23.716: Updates to Architectural Requirements | OTD, Charter | - |
| S2‑187590 | Update of solution #5 | Nokia, Nokia Shanghai Bell | - |
| S2‑187591 | Application detection report when the PFDs are removed | Huawei, HiSilicon | - |
| S2‑187592 | Application detection report when the PFDs are removed | Huawei, HiSilicon | - |
| S2‑187593 | Traffic Profile for NB-IoT UE Uu operation optimisation | Huawei, HiSilicon | - |
| S2‑187594 | Traffic Profile for NB-IoT UE Uu operation optimisation | Huawei, HiSilicon | - |
| S2‑187595 | Clarification on EDT procedure | NTT DOCOMO INC. | - |
| S2‑187596 | UE Radio Capability Update using TAU procedure | Intel | - |
| S2‑187597 | TS23.502 handover | ZTE | - |
| S2‑187598 | Updates to Solution 5 | Cisco, Softbank | - |
| S2‑187599 | Reply LS on GSMA question on 5G network slices | SA WG2 | - |
| S2‑187600 | Reply LS on Delay Tolerant Access and Low Access Priority in 5GS | SA WG2 | - |
| S2‑187601 | Application detection report when the PFDs are removed | Huawei, HiSilicon | - |
| S2‑187602 | 5QI-QCI alignment | Huawei, HiSilicon | - |
| S2‑187603 | Paging policy differentiation for RRC inactive | Huawei, HiSilicon, Ericsson | - |
| S2‑187604 | Missing TADs behaviour | BlackBerry UK Limited | - |
| S2‑187605 | Emergency Services Support indicator for non-3GPP access | ORANGE | - |
| S2‑187606 | [DRAFT] LS on potential enhancement of DR-mode of operation | SA WG2 | - |
| S2‑187607 | The proposal for subscribed PTW length | China Mobile | imported from 3GU |
| S2‑187608 | Application detection report when the PFDs are removed | Huawei, HiSilicon | imported from 3GU |
| S2‑187609 | SBI friendly UE policy delivery procedure | Samsung | imported from 3GU |
| S2‑187610 | Emergency Services Support indicator for non-3GPP access | ORANGE | imported from 3GU |
| S2‑187611 | Clarification on the non-IP PDU session type for EPS to 5GS interworking | ZTE | imported from 3GU |
| S2‑187612 | TR 23.716: Updates to Architectural Requirements | OTD, Charter | imported from 3GU |
| S2‑187613 | Solution 7 improvement | Ericsson | imported from 3GU |
| S2‑187614 | Solution for KI15: Core Network selection for Cellular IOT | Huawei, HiSilicon, Intel | imported from 3GU |
| S2‑187615 | Solution for KI5: Network controlled UL data transmission delay | OPPO | imported from 3GU |
| S2‑187616 | UPDATE to SID: Study of enablers for Network Automation for 5G | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑187617 | LS on Data Analytics in SA WG2/NWDAF | SA WG2 | imported from 3GU |
| S2‑187618 | New Key Issue: Recommendations produced by NWDAF | ORANGE, Huawei | imported from 3GU |
| S2‑187619 | Solution 2 update: Content of Network Data Analytics Feedback | ORANGE | imported from 3GU |
| S2‑187620 | Definitions, architectural assumptions and key issue related to network identification, selection and access control (solution) | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑187621 | Key Issue Proposal on 5GLAN Group Management | Huawei, HiSilicon, KPN, Intel | imported from 3GU |
| S2‑187622 | Key issues for 5G-LAN Service Discovery, Selection and Restriction | Intel | imported from 3GU |
| S2‑187623 | Key Issue Proposal on Clock Synchronization | Huawei, HiSilicon | imported from 3GU |
| S2‑187624 | Support for 5GLAN communication key issue | Huawei, HiSilicon, Intel, InterDigital Inc. | imported from 3GU |
| S2‑187625 | Update of solution #5 | Nokia, Nokia Shanghai Bell | imported from 3GU |
| S2‑187626 | Service framework requirements | Ericsson | imported from 3GU |
| S2‑187627 | Distributed service framework | Oracle, Verizon, Cisco. | imported from 3GU |
| S2‑187628 | Updating for solution#5 in FS_URLLC | OPPO | imported from 3GU |
| S2‑187629 | LS on potential enhancement of DR-mode of operation | SA WG2 | imported from 3GU |
page generated from database: 2024-04-22 07:58:53