TDoc | Title | Source |
---|---|---|
C1-253000 | 3GPP TSG CT1#155 – agenda for Tdoc allocation | CT1 Chair |
C1-253001 | 3GPP TSG CT1#155 – agenda after Tdoc allocation deadline | CT1 Chair |
C1-253002 | 3GPP TSG CT1#155 – agenda with proposed LS-actions | CT1 Chair |
C1-253003 | 3GPP TSG CT1#155 – agenda at start of meeting | CT1 Chair |
C1-253004 | 3GPP TSG CT1#155– agenda Thursday evening | CT1 Chair |
C1-253005 | 3GPP TSG CT1#155 – agenda at end of meeting | CT1 Chair |
C1-253006 | Initial time schedule for CT1#155 | CT1 Chair |
TDoc | Title | Source |
---|---|---|
C1-253007 | Draft CT1#154 meeting report for approval | MCC |
TDoc | Title | Source |
---|---|---|
C1-253019 | LS on Next Generation eCall | CEN/TC 278/WG 15 “eSafety” |
C1-253020 | LS on SL Ranging and Short-range based positioning management procedures | CT3 |
C1-253021 | Reply LS on maximum warning message size | CT4 |
C1-253022 | Reply LS on request for IMS Data Channel related clarifications | CT4 |
C1-253023 | LS on Encoding of (S)RTP Multiplexed Media Identification Information | CT4 |
C1-253024 | LS on feedback for IMS resiliency study | CT4 |
C1-253025 | LS to CT1 and CT4 on maximum warning message size | RAN2 |
C1-253026 | Reply LS on paging capability loss issue | RAN2 |
C1-253027 | Reply LS on emergency call back and paging | RAN3 |
C1-253028 | Reply LS on Privacy and security aspects regarding DC management by the network | SA2 |
C1-253029 | Reply LS on multiplexing capability negotiation | SA2 |
C1-253030 | LS on AIoT device identifier length | SA2 |
C1-253031 | LS reply on support for multiple non-3GPP device identifiers | SA2 |
C1-253032 | Reply LS on PWS enhancement for MWAB and MBSR | SA2 |
C1-253033 | LS on S&F mode indications to NAS | RAN2 |
C1-253034 | LS on byte-alignment of upper layer data SDU | RAN2 |
C1-253556 | LS on draft-ietf-6man-deprecate-router-alert, “Deprecation of the IPv6 Router Alert Option for New Protocols” | IETF IPv6 Maintenance (6MAN) |
C1-253557 | LS on the creation of the Getting Ready for Energy-Efficient Networking Working Group in the IETF | IETF Getting Ready for Energy-Efficient Networking Working Group (GREEN) |
C1-253558 | Reply LS on Encoding of (S)RTP Multiplexed Media Identification Information | SA4 |
C1-253559 | LS on LI requirements on IMS Data Channel | SA3-LI |
C1-253562 | LS to 3GPP CT1 on SOR-CMCI | GSMA |
TDoc | Title | Source |
---|---|---|
C1-253049 | LS on UE parameters update header security | Nokia |
C1-253095 | LS on AIoT protocol naming | Huawei, HiSilicon / Mikael |
C1-253192 | Reply LS on Next Generation eCall | Qualcomm Incorporated |
C1-253208 | Reply LS to RAN2 on maximum size of the PWS warning message content | Qualcomm Incorporated / Amer |
C1-253209 | Reply LS on S&F mode indications to NAS | Qualcomm Incorporated / Amer |
C1-253212 | Reply LS on S&F mode indications to NAS | Qualcomm Incorporated / Amer |
C1-253288 | Reply LS on S&F mode indications. | vivo/Hui |
C1-253324 | Reply LS to CT4 on encoding alignment of (S)RTP Multiplexed Media Identification information | Nokia |
C1-253342 | Reply LS on on byte-alignment of upper layer data SDU | ZTE / Joy |
C1-253350 | LS on the path information in 5G ProSe multi-hop UE-to-UE relay discovery of non-IP PDU type | ZTE / Joy |
C1-253370 | Discussion paper on Satellite Coverage Availability Information | QUALCOMM Europe Inc. - Spain |
C1-253371 | LS on Satellite Coverage Availability Information | QUALCOMM Europe Inc. - Spain |
C1-253402 | Reply LS on maximum warning message size | Google / SangMin |
C1-253403 | Reply LS on S&F mode indications to NAS | Google / SangMin |
C1-253414 | Reply LS on Geofencing in ETWS for NR and NB-IoT NTN | Ericsson / Neda |
C1-253470 | Reply LS on S&F mode indications to NAS | CATT/Xiaoxue |
C1-253472 | Reply LS on Encoding of (S)RTP Multiplexed Media Identification Information | vivo |
C1-253536 | LS on broadcasting the information on disaster condition of a PLMN from E-UTRAN in case of Disaster Condition | LG Electronics |
C1-253543 | Reply LS on S&F mode indication to NAS | LG Electronics /Stella |
TDoc | Title | Source |
---|---|---|
C1-253008 | Latest version of the Work Plan | MCC |
C1-253010 | CT1#155 guidance | CT1 Chair |
C1-253011 | Guidance for handling of specifications | CT1 Chair |
C1-253045 | Guidance for handling of presentation sheets | CT1 Chair |
C1-253560 | Guidance for handling of specifications | CT1 Chair |
TDoc | Title | Source |
---|---|---|
C1-253036 | Addition of abnormal case handling for UE requested MA PDU session with invalid capabilities | Lenovo |
C1-253037 | Addition of abnormal case handling for UE requested MA PDU session with invalid capabilities | Lenovo |
C1-253038 | Addition of abnormal case handling for UE requested MA PDU session with invalid capabilities | Lenovo |
C1-253039 | Addition of abnormal case handling for UE requested MA PDU session with invalid capabilities | Lenovo |
C1-253078 | Updating the +CSODCP and +CRTDCP AT Command descriptions to account for the Control Plane CIoT 5GS Optimisation | InterDigital, Huawei, HiSilicon |
C1-253079 | Updating the +CSODCP and +CRTDCP AT Command descriptions to account for the Control Plane CIoT 5GS Optimisation | InterDigital, Huawei, HiSilicon |
C1-253080 | Updating the +CSODCP and +CRTDCP AT Command descriptions to account for the Control Plane CIoT 5GS Optimisation | InterDigital, Huawei, HiSilicon |
C1-253130 | Correction to the XML schema on |
Huawei, HiSilicon |
C1-253131 | Correction to the XML schema on |
Huawei, HiSilicon |
C1-253132 | Correction to the XML schema on |
Huawei, HiSilicon |
C1-253133 | Correction to the |
Huawei, HiSilicon |
C1-253134 | Correction to the XML schema on |
Huawei, HiSilicon |
C1-253135 | Correction to the XML schema on |
Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
C1-253451 | Compromised update for SOR-CMCI. | Huawei, HiSilicon, [NTT DOCOMO] |
C1-253503 | Compromised update for SOR-CMCI. | Huawei, HiSilicon, [NTT DOCOMO] |
C1-253511 | Compromised update for SOR-CMCI. | Huawei, HiSilicon / Vishnu |
C1-253513 | Compromised update for SOR-CMCI. | Huawei, HiSilicon / Vishnu |
C1-253526 | Compromised update for SOR-CMCI. | Huawei, HiSilicon, [NTT DOCOMO] |
C1-253527 | Compromised update for SOR-CMCI. | Huawei, HiSilicon / Vishnu |
TDoc | Title | Source |
---|---|---|
C1-253399 | Correction to ACR Determine and Service Provisioning. | Samsung |
C1-253408 | Correction to ACR Determine and Service Provisioning. | Samsung |
C1-253413 | Correction to ACR Determine and Service Provisioning. | Samsung |
C1-253478 | Corrections on the EAS dynamic information | Huawei, HiSilicon |
C1-253479 | Corrections on the EAS dynamic information | Huawei, HiSilicon |
C1-253480 | Corrections on the EAS dynamic information | Huawei, HiSilicon |
C1-253481 | Corrections on the EEC context relocation information | Huawei, HiSilicon |
C1-253482 | Corrections on the EEC context relocation information | Huawei, HiSilicon |
C1-253483 | Corrections on the EEC context relocation information | Huawei, HiSilicon |
C1-253484 | Corrections on the Target Information | Huawei, HiSilicon |
C1-253485 | Corrections on the Target Information | Huawei, HiSilicon |
C1-253486 | Corrections on the Target Information | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
C1-253170 | Correction to the event-triggered location reporting procedure and the client-triggered or VAL server-triggered location reporting procedure for CoAP | Huawei, HiSilicon |
C1-253171 | Correction to the event-triggered location reporting procedure and the client-triggered or VAL server-triggered location reporting procedure for CoAP | Huawei, HiSilicon |
C1-253172 | Correction to the event-triggered location reporting procedure and the client-triggered or VAL server-triggered location reporting procedure for CoAP | Huawei, HiSilicon |
C1-253173 | Correction to off-network location management protocol | Huawei, HiSilicon |
C1-253174 | Correction to off-network location management protocol | Huawei, HiSilicon |
C1-253175 | Correction to off-network location management protocol | Huawei, HiSilicon |
C1-253176 | Correction to include timestamp for location report information for HTTP | Huawei, HiSilicon |
C1-253177 | Correction to include timestamp for location report information for HTTP | Huawei, HiSilicon |
C1-253178 | Correction to include timestamp for location report information for HTTP | Huawei, HiSilicon |
C1-253180 | Correction to include timestamp for location report information for CoAP | Huawei, HiSilicon |
C1-253181 | Correction to include timestamp for location report information for CoAP | Huawei, HiSilicon |
C1-253182 | Correction to include timestamp for location report information for CoAP | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
C1-253487 | Corrections on the ACR parameters | Huawei, HiSilicon |
C1-253488 | Corrections on the ACR parameters | Huawei, HiSilicon |
C1-253489 | Corrections on the EAS bundles | Huawei, HiSilicon |
C1-253490 | Corrections on the EAS bundles | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
C1-253218 | Clarification on LCS user plane connection handling | Qualcomm Incorporated |
C1-253259 | Maximum number of LCS secured user plane connections per UE | Nokia |
C1-253261 | UP connection trasfer during LMF relocation | OPPO |
C1-253262 | UP connection trasfer during LMF relocation | OPPO |
C1-253272 | Clarification on maximum number of LCS secured user plane connection per UE | ZTE |
C1-253273 | Clarification on maximum number of LCS secured user plane connection per UE | ZTE |
C1-253468 | Clarification on the failure of the user plane connection establishment | CATT |
C1-253469 | Clarification on the failure of the user plane connection establishment | CATT |
C1-253510 | Maximum one user plane connection per UE | Ericsson |
TDoc | Title | Source |
---|---|---|
C1-253153 | Correction to the LocationReportConfiguration data type and related CDDL documents | Huawei, HiSilicon |
C1-253154 | Correction to the LocationReportConfiguration data type and related CDDL documents | Huawei, HiSilicon |
C1-253155 | Correction to new type of data type for positioning method | Huawei, HiSilicon |
C1-253168 | Correction to new type of data type for positioning method | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
C1-253059 | Update the interaction of DC with CFNR and support the requirement | China Mobile |
C1-253060 | Update the interaction of DC with CFNR and support the requirement | China Mobile |
C1-253061 | Notify the redirected-to party identity to the DCSF in the case of CDIV | China Mobile |
C1-253062 | Notify the redirected-to party identity to the DCSF in the case of CDIV | China Mobile |
TDoc | Title | Source |
---|---|---|
C1-253508 | Correction on usage of terms in communication with Application Client | China Mobile |
C1-253509 | Correction on usage of terms in communication with Application Client | China Mobile |
TDoc | Title | Source |
---|---|---|
C1-253373 | User plane resource request PDU associated with S-NSSAI not in the allowed S-NSSAI for the current TA | Samsung |
C1-253374 | User plane resource request PDU associated with S-NSSAI not in the allowed S-NSSAI for the current TA | Samsung |
TDoc | Title | Source |
---|---|---|
C1-253125 | Correction related to the depreciation of the ATSSS-ST field | Nokia |
TDoc | Title | Source |
---|---|---|
C1-253417 | Supported AIoT NAS procedures | Nokia |
C1-253534 | CT aspects of MINT support in EPS for 5G-only national roaming UE | China Telecommunications |
TDoc | Title | Source |
---|---|---|
C1-253050 | Revised WID on CT aspects of Multi-Access (ATSSS_Ph4) | Apple |
C1-253120 | Revised WID on CT aspects of Core Network Enhanced Support for Artificial Intelligence (AI) and Machine Learning (ML) | vivo |
C1-253191 | Revised WID on Alignment of eCall over IMS with CEN | CT1 |
C1-253203 | revised WID on MPS4msg | Peraton Labs, CISA ECD, AT&T |
C1-253298 | revised WID on MPS4msg | Peraton Labs, CISA ECD, AT&T |
C1-253303 | Revised WID on CT aspects for application enablement for mobile metaverse services | Samsung, Nokia |
C1-253504 | Revised WID on CT aspects for enabling MSGin5G Service phase 3 | China Mobile Com. Corporation |
TDoc | Title | Source |
---|---|---|
C1-253127 | Corrections related to the encoding of the network steering functionalities information | Nokia |
C1-253128 | Correcting wrong references and other miscellaneous corrections | Nokia |
C1-253137 | Reference to obsolete IETF RFC3810 and RFC3376 | Huawei, HiSilicon |
C1-253190 | Abnormal case handling of Tsor timer expiry. | Huawei, HiSilicon / Vishnu |
C1-253198 | VPLMN controlled D2C configuration | Apple |
C1-253199 | VPLMN controlled D2C configuration | Apple |
C1-253225 | Correction to abnormal cases in the network | ZTE |
C1-253226 | Clarification on discovery of the UE UDP port of the PMF | ZTE |
C1-253231 | New AT Command +CLOGSIMAPDU for nrUSIM logging | Apple |
C1-253239 | Corrections to the handling of positioning capabilities | Ericsson / Yumei |
C1-253240 | Default handling for the spare values | Ericsson |
C1-253260 | IEI handling | OPPO |
C1-253263 | IEI handling | OPPO |
C1-253281 | Corrections on PLMN selection in satellite access technology | ZTE |
C1-253326 | UE behaviour on prolonged SR failures in 5G | Samsung, AT&T |
C1-253327 | PLMN selection in case of emergency call in limited service state | NTT DOCOMO |
C1-253329 | UE behaviour on prolonged SR failures other than 5G | Samsung Electronics France SA |
C1-253339 | Clarification to the AT command CGATT | Huawei, HiSilicon / Vishnu |
C1-253352 | Abnormal case handling for Tsor timer expiry when MRU ongoing | Huawei, HiSilicon |
C1-253366 | AT command for real-time text | Vodafone |
C1-253379 | Eees_EASInformationProvisioning API: cardinality of arrays | Ericsson |
C1-253405 | Handling of RLF recovery while RAI bits are set | |
C1-253409 | 5GSM sublayer operation upon receiving an indication that the CIoT user data was not forwarded due to congestion control and a timer value from the 5GMM sublayer | Nokia |
C1-253427 | Multiple LCS-UPP connections per UE | Ericsson / Yumei |
C1-253428 | Multiple LCS-UPP connections per UE | Ericsson / Yumei |
C1-253432 | Capability for multiple user plane connections per UE | Ericsson / Yumei |
C1-253446 | LMF relocation on new user plane connection | Ericsson / Yumei |
C1-253447 | Alt1 - Modify LCS-UPP connection for LMF relocation via CP | Ericsson / Yumei |
C1-253449 | Alt2 - Modify LCS-UPP connection for LMF relocation via UP | Ericsson |
C1-253512 | VPLMN controlled D2C configuration | Apple |
C1-253519 | Inactive EPS bearer context in ESM DATA TRANSPORT | MediaTek Inc. |
C1-253520 | Inactive PDU session in UL NAS DATA TRANSPORT | MediaTek Inc. |
C1-253521 | Correction to T3440 timer handling with control plane data back-off timer T3448 | MediaTek Inc. |
C1-253522 | Correction to T3540 timer handling with control plane data back-off timer T3448 | MediaTek Inc. |
C1-253542 | VPLMN controlled D2C configuration | Apple |
C1-253546 | Correction to T3540 timer handling with control plane data back-off timer T3448 | MediaTek Inc. |
C1-253549 | UE behaviour on prolonged SR failures in 5G | Samsung, AT&T |
TDoc | Title | Source |
---|---|---|
C1-253084 | Introducing and adding the information elements of NTZ configuration procedure | Apple |
C1-253310 | Update data structure to support NTZ enforcement procedures | InterDigital |
C1-253311 | Update data semantics to support NTZ enforcement procedures | InterDigital |
C1-253313 | Update XML schema to support NTZ enforcement procedures | InterDigital |
C1-253316 | Workplan for the CT1 part of UASAPP_Ph3 | InterDigital |
TDoc | Title | Source |
---|---|---|
C1-253380 | Support of EAS Information provisioning request from leading EES to partner EES | Ericsson |
C1-253423 | Traffic influence indication in EAS discovery procedure. | Samsung |
C1-253425 | Correction to UE Identifier in ACR Initiation request | Samsung |
TDoc | Title | Source |
---|---|---|
C1-253070 | Work plan for the CT1 part of NBI19 | Huawei, HiSilicon /Christian |
C1-253493 | Corrections on the Eecs_ServiceProvisioning service | Huawei, HiSilicon |
C1-253494 | Corrections on the Eees_ACREvents service | Huawei, HiSilicon |
C1-253495 | Corrections on the Eees_EASDiscovery service | Huawei, HiSilicon |
C1-253496 | Corrections on the Eees_EASInformationProvisioning service | Huawei, HiSilicon |
C1-253497 | Corrections on the Eees_EECRegistration service | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
C1-253163 | Addition to floor control release message | Ericsson |
C1-253164 | Addition of Idm client id MO | Ericsson, Motorola Solutions |
C1-253165 | Addition of Idm client id | Ericsson |
C1-253179 | Corrections for handling of sending a SIP BYE request on receipt of a SIP REFER request | Kontron Transportation France |
C1-253186 | Clarifications on MCPTT private call transfer | Kontron Transportation France |
C1-253188 | Corrections related to "P-Asserted-Service” header | Kontron Transportation France |
C1-253200 | Reference to obsoleted IETF RFC 7231 | Ericsson |
C1-253491 | Reference to obsoleted IETF RFC 4122 | Huawei, HiSilicon |
C1-253492 | Reference to obsoleted IETF RFC 4122 | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
C1-253043 | ECRATU list handling when RPLMN is not part of EPLMN | Apple, China Mobile, InterDigital |
C1-253044 | ECRATU list handling when RPLMN is not part of EPLMN | Apple, China Mobile, InterDigital, Vodafone, Ericsson |
C1-253052 | Definition of access technologies for satellite access | Apple |
C1-253270 | Deleting access technology utilization control information | Samsung |
C1-253271 | Deleting access technology utilization control information | Samsung |
C1-253282 | Clarification on the type of access technology utilization control in EPS | vivo |
C1-253283 | Clarification on the type of access technology utilization control in 5GS | vivo |
C1-253284 | Correction on type of access technology utilization control in detach procedure | vivo |
C1-253285 | Correction on type of access technology utilization control in degistration procedure | vivo |
C1-253286 | Remove limitation on access technology utilization control only in 3GPP access | vivo |
C1-253334 | terminology corrections | SAMSUNG/Danish |
C1-253335 | Correction in the terminology | Samsung |
C1-253340 | Forbidden TA handling during RAT utilization control | Nokia |
C1-253341 | Forbidden TA handling during RAT utilization control | Nokia |
C1-253351 | Discussion on 2G/3G handling in RAT utilization control | Nokia |
C1-253353 | 2G and 3G handling for RAT utilization control | Nokia |
C1-253354 | Clarification that the PLMN with RAT restriction will be indicated as available for manual selection. | Huawei, HiSilicon / Vishnu |
C1-253372 | 2G and 3G handling for RAT utilization control | Nokia |
C1-253433 | Clarify NW requirement in applying access technology utilization control | NTT DOCOMO |
C1-253434 | Clarify NW requirement in applying access technology utilization control - registration | NTT DOCOMO |
C1-253435 | Clarify NW requirement in applying access technology utilization control - UCU | NTT DOCOMO |
C1-253436 | Clarify NW requirement in applying access technology utilization control - deregi | NTT DOCOMO |
C1-253437 | Clarify NW requirement in applying access technology utilization control - service request | NTT DOCOMO |
C1-253438 | Clarify AMF requirement in applying access technology utilization control | NTT DOCOMO |
C1-253439 | Clarify NW requirement in applying access technology utilization control - attach | NTT DOCOMO |
C1-253440 | Clarify NW requirement in applying access technology utilization control - detach | NTT DOCOMO |
C1-253441 | Clarify NW requirement in applying access technology utilization control - service request | NTT DOCOMO |
C1-253442 | Handling of received access technology utilization control information based on UE configuration | NTT DOCOMO |
C1-253443 | Handling of received access technology utilization control information based on UE configuration | NTT DOCOMO |
C1-253444 | Addition of configuration parameter for ECRATU | NTT DOCOMO |
C1-253528 | ECRATU list handling when RPLMN is not part of EPLMN | Apple, China Mobile, InterDigital |
TDoc | Title | Source |
---|---|---|
C1-253087 | Large scale deployment issues for LMS and proposed solution. | Motorola Solutions Germany |
C1-253121 | pCR on LMS services reorganization Clause 6 | Airbus |
C1-253122 | pCR on LMS services reorganization Clause 7 | Airbus |
C1-253123 | pCR on LMS services reorganization Annex A | Airbus |
C1-253124 | pCR on LMS authorizations | Airbus |
C1-253156 | MCLoc LMC in network entities | Ericsson / Magnus |
C1-253157 | MCLoc HTTP/2 support in identity management specification | Ericsson |
C1-253158 | MCLoc cleanup | Ericsson / Magnus |
C1-253159 | MCLoc obsolete RFC4122 | Ericsson / Magnus |
C1-253160 | MCLoc Enhancements for Subscription APIs | Ericsson / Magnus |
C1-253161 | MCLoc Additional attributes in LMS Registration | Ericsson / Magnus |
C1-253162 | Location user profile configuration data | Ericsson |
C1-253166 | MCLoc workplan | Ericsson / Magnus |
C1-253167 | MCLoc SIP/HTTP/NAT handling discussion paper | Ericsson / Magnus |
TDoc | Title | Source |
---|---|---|
C1-253009 | Additional Background Traffic Condition for Delay Tolerant Access Category | SK Telecom, LG Electronics, LG Uplus, China Unicom |
C1-253012 | Discussion on Access Category for Background Traffic | SK Telecom, LG Electronics, LG Uplus, China Unicom, vivo, Huawei, HiSilicon |
C1-253042 | New Access Category for Background Traffic | SK Telecom, LG Electronics, LG Uplus, China Unicom, vivo, Huawei, HiSilicon |
C1-253047 | UE parameters update header security | Nokia, Lenovo |
C1-253048 | DREI capability indication | Nokia |
C1-253072 | SUCI calculation failure handling | Apple |
C1-253136 | Reference to obsolete IETF RFC4122 and RFC7049 | Huawei, HiSilicon |
C1-253144 | Added UE behavior when MRU is ongoing and an ESFB request is pending | Huawei, HiSilicon / Vishnu |
C1-253237 | Corrections to the NW handling of positioning capabilities | Ericsson |
C1-253265 | Correction related to UAS | SHARP |
C1-253266 | Correction of the term regarding end of unavailability period report | SHARP |
C1-253274 | UE indication support of multiple LCS secured user plane connections | ZTE |
C1-253278 | No allowed NSSAI after de-registration with cause #62 | ZTE |
C1-253279 | Use standard value for S-NSSAI applicable to equivalent PLMNs | ZTE |
C1-253280 | No definition of camped PLMN | ZTE |
C1-253293 | Remove emergency restriction for WUS assistance in 5GS | vivo |
C1-253294 | Remove emergency restriction for WUS assistance in EPS | vivo |
C1-253299 | Editorial correction in service reject | NTT DOCOMO |
C1-253336 | T3525 handling on access change | Samsung |
C1-253355 | Requested NSSAI includeds S-NSSAI from partially allowed NSSAI | Samsung |
C1-253362 | LP-WUSPS paging subgroup ID values | Ericsson |
C1-253363 | Additional corrections to WUS, PEIPS and LP-WUSPS assistance information | Ericsson |
C1-253368 | S-NSSAI to be removed is the only S-NSSAI in the configured NSSAI, allowed NSSAI and partially allowed NSSAI | Samsung |
C1-253369 | Name correction for Disaster roaming information update data | SAMSUNG/Danish |
C1-253375 | PLMN-specific counter reset when the UE is registered for disaster roaming services | Samsung |
C1-253376 | Miscellaneous corrections | Ericsson |
C1-253410 | Stopping 5GS timers for CIoT upon congestion control being resolved | Nokia |
C1-253416 | Handling of PEIPS when an Emergency PDU session is established | Huawei, HiSilicon / Vishnu |
C1-253418 | PEIPS and emergency | Ericsson |
C1-253421 | Discussion on the backward compatability issue for using PEIPS during emergency PDU session. | Huawei, HiSilicon / Vishnu |
C1-253477 | Reference to obsoleted IETF RFC 4122 | Huawei, HiSilicon |
C1-253514 | Enabling satellite NG-RAN capability | MediaTek Inc. |
C1-253515 | Exemptions where service area restriction applies | MediaTek Inc. |
C1-253516 | MO exception reporting while T3447 or T3346 running | MediaTek Inc. |
C1-253517 | Unexpected MM cause for CIOT user data container | MediaTek Inc. |
C1-253518 | Corrections when UE in 5GMM-CONNECTED mode with RRC inactive indication | MediaTek Inc. |
TDoc | Title | Source |
---|---|---|
C1-253169 | Clarification to MM state | Huawei, HiSilicon / Vishnu |
C1-253238 | Correction to the WUS assistance information | Ericsson / Yumei |
C1-253322 | Stopping T3448 on ESM DATA TRANSPORT | Samsung Electronics France SA |
C1-253323 | Editorial correction in texts | Samsung |
C1-253333 | Using CustomLLFailureRetry leaf in an equivalent PLMN | NTT DOCOMO |
C1-253412 | Stopping GPRS timers for CIoT upon congestion control being resolved | Nokia |
C1-253498 | Reference to obsoleted IETF RFC 4282 | Huawei, HiSilicon |
C1-253555 | Stopping T3448 on ESM DATA TRANSPORT | Samsung Electronics France SA |
TDoc | Title | Source |
---|---|---|
C1-253365 | Slicing corrections | Ericsson |
TDoc | Title | Source |
---|---|---|
C1-253035 | FRMCS_Ph5 work plan | Nokia |
C1-253046 | Modifying the criteria for determining the participants during an ongoing ad hoc group emergency alert | Nokia, Kontron Transportation France, UIC |
C1-253053 | Audio mixing is performed in the UE or in the network to support multi-talker control | Nokia |
C1-253183 | Adding option to apply automatic commencement for adhoc group calls | Kontron Transportation France, Nokia |
C1-253184 | Adhoc group call release by an authorized user (MCPTT) | Kontron Transportation France, Nokia |
C1-253185 | Interworking of adhoc group call | Kontron Transportation France, Nokia |
C1-253227 | Modifying the criteria for determining the participants during an ongoing ad hoc group emergency alert | Nokia |
C1-253228 | Modifying the criteria for determining the participants during an ongoing ad hoc group emergency alert | Nokia |
C1-253229 | Ad hoc group standalone SDS using signalling CP – AHG determination | Nokia, UIC |
TDoc | Title | Source |
---|---|---|
C1-253201 | Corrections for MPS in restricted area | Peraton Labs, CISA ECD, AT&T |
C1-253202 | MPS for Messaging Paging Priority | Peraton Labs, CISA ECD, AT&T |
C1-253296 | Corrections for MPS in restricted area | Peraton Labs, CISA ECD, AT&T |
C1-253297 | MPS for Messaging Paging Priority | Peraton Labs, CISA ECD, AT&T |
TDoc | Title | Source |
---|---|---|
C1-253057 | Work plan for UIA_ARC | InterDigital |
C1-253102 | Multiple Non-3GPP device identifiers for QoS differentiation per PDU session modification procedure | Huawei, HiSilicon |
C1-253193 | Support for multiple non-3GPP device identifiers per PDU session modification procedure | InterDigital |
C1-253194 | Clarification on PDU session selection for QoS differentiation | InterDigital |
C1-253195 | PDU Modification exclusively for QoS differentiation | InterDigital, Apple |
C1-253196 | QoS Differentiation not available | InterDigital, Apple |
C1-253197 | PDU session modification reject with QoS Differentiation not available | InterDigital |
C1-253230 | Handling multiple non-3GPP device identifiers | Apple |
C1-253244 | Non-3GPP device identifier rejection | Ericsson / Yumei |
C1-253245 | Non-3GPP device identifier support | Ericsson / Yumei |
C1-253246 | Non-3GPP device identifier rejection | Ericsson / Yumei |
C1-253247 | Reply LS on LS reply on support for multiple non-3GPP device identifiers | Ericsson / Yumei |
C1-253275 | Support multiple non-3GPP devices per PDU session modification procedure | ZTE |
C1-253276 | PDU session modification request only for non-3GPP device(s) | ZTE |
C1-253277 | New 5GSM cause value for non-3GPP device identifier(s) not available | ZTE |
C1-253325 | Differentiated QoS for non-3GPP device identifiers connected through the UE | Nokia |
C1-253328 | Handling of unavailability of non-3GPP device identifier by the network | Nokia |
C1-253330 | Runtime handling of unavailability of non-3GPP devices by the network | Nokia |
C1-253499 | Clarifications on the PDU session modification for non-3GPP device | Huawei, HiSilicon |
C1-253500 | Support of multiple Non-3GPP device identifiers for QoS differentiation | Huawei, HiSilicon |
C1-253501 | Support of reject QoS differentiation for non-3GPP device identifier(s) | Huawei, HiSilicon |
C1-253502 | Support of reject QoS differentiation for VLAN tag not allowed | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
C1-253129 | Work Plan: CT Aspects of Phase3 for UAS, UAV and UAM | LG Electronics Inc. |
TDoc | Title | Source |
---|---|---|
C1-253147 | Correction to wrong element name, data semantics, and table numbering | Huawei, HiSilicon |
C1-253148 | Introduction of new location positioning configuration procedure for HTTP | Huawei, HiSilicon |
C1-253149 | Introduction of new location positioning configuration procedure for CoAP | Huawei, HiSilicon |
C1-253150 | Introduction of new history location result report procedure for HTTP | Huawei, HiSilicon |
C1-253151 | Introduction of new history location result report procedure for CoAP | Huawei, HiSilicon |
C1-253152 | Correction to velocity information | Huawei, HiSilicon |
C1-253187 | Introduction of new data type for location positioning configuration procedure for CoAP | Huawei, HiSilicon /Christian |
C1-253464 | eLSAPP CT1 Work plan | CATT/Xiaoxue |
C1-253465 | Add the confirm location verification procedure | CATT |
TDoc | Title | Source |
---|---|---|
C1-253071 | Work plan for the CT1 part of SEALDD_Ph2 | Huawei, HiSilicon /Christian |
C1-253138 | Correction to the |
Huawei, HiSilicon |
C1-253139 | Correction to the |
Huawei, HiSilicon |
C1-253140 | void | void |
C1-253141 | Update to CR0059r1 on "Implementation of CRs 0014 and 0031" | Huawei, HiSilicon |
C1-253142 | Correction to the use of "and/or" term | Huawei, HiSilicon |
C1-253143 | Resolution of editor's note under clause A.3.1.5.2 introduced by CR#0037 | Huawei, HiSilicon |
C1-253145 | Resolution of editor's note under clause 8.4.2 introduced by CR#0030 | Huawei, HiSilicon |
C1-253146 | Resolution of editor's note under clause 8.4.2 introduced by CR#0023 | Huawei, HiSilicon |
C1-253381 | Correction to SEALDD regular transmission connection establishment | Ericsson / Nevenka |
C1-253505 | Correction to the Sdd_RegularTransmissionConnection API provided by the SDDM-S | Huawei, HiSilicon |
TDoc | Title | Source |
---|---|---|
C1-253100 | T3451 applicability at procedure accept | Huawei, HiSilicon |
C1-253101 | T3451 normal stop conditions | Huawei, HiSilicon |
C1-253210 | Handling of S&F mode indications from the lower layers | Qualcomm Incorporated / Amer |
C1-253211 | UE handling of ETWS geofencing | Qualcomm Incorporated |
C1-253213 | UE handling of ETWS geofencing | Qualcomm Incorporated |
C1-253214 | Handling of S&F mode indications from the lower layers | Qualcomm Incorporated |
C1-253248 | Resolving the EN on S&F wait timer in the attach procedure | Nokia |
C1-253249 | Resolving the EN on S&F wait timer in the service request procedure | Nokia |
C1-253250 | Corrections to stop conditions for timer T3451-option 1 | Nokia |
C1-253251 | Corrections to stop conditions for timer T3451-option 2 | Nokia |
C1-253252 | S&F satellite operation parameters in non-integrity protected reject messages-option1 | Nokia, MediaTek Inc. |
C1-253253 | S&F satellite operation parameters in non-integrity protected reject messages-option2 | Nokia, MediaTek Inc. |
C1-253254 | Aligning attach and service request procedures with the term “S&F satellite E-UTRA cell” | Nokia |
C1-253255 | TAU procedure triggered by the UE being out of the TAI list overrides timer T3451 - attach procedure | Nokia |
C1-253256 | TAU procedure triggered by the UE being out of the TAI list overrides timer T3451 - service request procedure | Nokia |
C1-253257 | Triggering TAU procedure for “case a” (due to UE moving out of TAI list) overrides timer T3451 | Nokia |
C1-253258 | Additional condition for stopping timer T3451 | Nokia |
C1-253287 | Discussion on the transition time information between S&F mode and normal mode | vivo/Hui |
C1-253289 | The handling on the transition from normal mode to S&F mode | vivo |
C1-253290 | The UE behaviour on S&F wait timer received in NAS accept message | vivo |
C1-253291 | Clarification on S&F wait timer in NAS reject message | vivo/Hui |
C1-253302 | The handling on the transition time information between S&F mode and normal mode | vivo |
C1-253309 | Discussion on handling of timer T3451 in UE | Samsung Electronics France SA |
C1-253312 | T3451 handling in the UE | Samsung Electronics France SA |
C1-253314 | S&F monitoring list deletion due to number of satellites 0 | Samsung |
C1-253317 | Periodic timer and DRX parameter due to S&F satellite operation | Samsung |
C1-253319 | Determination of mobile reachable timer, periodic timer or the implicit detach timer | Samsung |
C1-253321 | NAS signalling connection release after EMM cause 83 | Samsung |
C1-253394 | Handling of S&F timer when PSM is activated | Huawei, HiSilicon / Vishnu |
C1-253398 | Correction to general clause for Store and Forward (S&F) Satellite operation | Huawei, HiSilicon / Vishnu |
C1-253400 | Specifying handling of transition time indication for S&F | Ericsson |
C1-253404 | S&F transition time information from lower layers | |
C1-253426 | Support of Store and Forward (S&F) satellite operation – tracking area update procedure | Ericsson, Huawei, HiSilicon, CATT, Samsung, Nokia, LG Electronics |
C1-253429 | Alignments in S&F in Satellite | Ericsson, LG Electronics, CATT |
C1-253431 | General clause for Store and Forward (S&F) Satellite operation | Ericsson, LG Electronics, CATT |
C1-253445 | Resolving EN on UE action on expiry of S&F wait timer in S&F mode | Ericsson, LG Electronics, CATT |
C1-253456 | 5GSAT_Ph3_ARCH CT1 Work plan | CATT/Xiaoxue |
C1-253457 | Enhance detach procedure for S&F satellite operation | CATT, SHARP, ZTE, Nokia, vivo, MediaTek Inc., Samsung, Huawei, HiSilicon |
C1-253466 | Support for sidelink positioning management | CATT |
C1-253467 | Add the short-Range based positioning information procedure | CATT |
C1-253523 | Handling ATTACH REJECT and SERVICE REJECT with no S&F wait timer | MediaTek Inc. |
C1-253524 | PLMN selection when not supporting S&F operation | MediaTek Inc. |
C1-253525 | S&F information as trigger for service accept | MediaTek Inc. |
C1-253533 | Discussion on RAN2 LS on S&F mode indications to NAS | LG Electronics /Stella |
C1-253539 | (Opt.1) Reusing T3451 considering transition time indication from lower layers | LG Electronics |
C1-253541 | (Opt.2) Introducing T3451A to handle transition time indication from lower layers | LG Electronics |
C1-253544 | T3451 handling in the UE | Samsung Electronics France SA |
C1-253548 | Encoding of | Nokia |
TDoc | Title | Source |
---|---|---|
C1-253269 | Support of SNPN in the 5G ProSe additional parameters announcement procedure | SHARP |
C1-253535 | CT aspects of ProSe support in NPN | China Telecommunications |
TDoc | Title | Source |
---|---|---|
C1-253085 | Clarification on IP Address allocation in 5G ProSe multi-hop UE to Network relay procedure | Apple Inc |
C1-253086 | Editorial correction for ProSe multi-hop U2N relay | Apple |
C1-253103 | Introducing the configuration parameters of the 5G ProSe multi-hop layer-2 UE-to-network relay UE – the procedural part | Nokia |
C1-253104 | Introducing the configuration parameters of the 5G ProSe multi-hop layer-2 UE-to-network relay UE – the encoding part | Nokia |
C1-253105 | Adding the PC5 QoS flow in the List of multi-hop remote UE parameters | Nokia |
C1-253106 | Introducing the 5G ProSe additional parameters announcement procedure for multi-hop UE-to-network relay | Nokia |
C1-253107 | Updating the ProSe additional parameters announcement request message for multi-hop UE-to-network relay | Nokia |
C1-253108 | Corrections for the identifiers used in 5G ProSe multi-hop UE-to-UE relay discovery for IP data unit type with model B | Nokia |
C1-253109 | Corrections related to the Root relay info in the PC5 discovery procedures | Nokia |
C1-253110 | Adding the path information in the direct link establishment request/Accept messages for the multi-hop UE-to-UE relay for Ethernet and Unstructured data unit type | Nokia |
C1-253111 | Adding the path information in the direct link modification request/Accept messages for the multi-hop UE-to-UE relay for Ethernet and Unstructured data unit type | Nokia |
C1-253112 | Resolving the ENs related to the List of multi-hop remote UE parameters | Nokia |
C1-253113 | Updating the MH discovery additional information procedure to consider the Announcer info of the intermediate relay UE connected to the U2N relay UE | Nokia |
C1-253114 | Correction for the encoding of the configuration parameters of 5G ProSe intermediate U2N relay UE related to the indication of PDU session parameters | Nokia |
C1-253115 | Routing information for 5G ProSe multi-hop end UE | Nokia |
C1-253116 | Specifying security procedures over PC3a interface for multi-hop UE-to-network relay | Nokia |
C1-253117 | Specifying security procedures over PC3a interface for multi-hop UE-to-UE relay | Nokia |
C1-253118 | Adding the Hop limit in the PC5 signalling messages for multi-hop UE-to-UE relay communication | Nokia |
C1-253215 | Support PWS via Multi-hop U2N relay | Qualcomm Incorporated |
C1-253216 | Hop count and Hop limit for MH U2N relay discovery model A | Qualcomm Incorporated |
C1-253217 | Introducing the 5G ProSe additional parameters announcement procedure for multi-hop UE-to-network relay | Qualcomm Incorporated, LG Electronics |
C1-253267 | Corrections for multi-hop UE-to-network relay discovery additional information | SHARP |
C1-253268 | Adding Hop limit IE to ProSe direct link establishment request message | SHARP |
C1-253343 | Resolve EN on PROSE PC5 DISCOVERY message for multi-hop L3 U2U relay discovery | ZTE |
C1-253344 | Correction to PROSE PC5 DISCOVERY message for multi-hop U2U relay discovery response | ZTE |
C1-253345 | Clarification on multi-hop L3 U2U relay discovery for IP data unit type with model A | ZTE |
C1-253346 | Resolve EN on signal strength measurement and related timer in multi-hop U2U relay discovery | ZTE |
C1-253347 | Definition on ROSE PC5 DISCOVERY messages for multi-hop U2U relay discovery for non-IP | ZTE |
C1-253348 | Resolve EN on updating the parameters in the procedure of multi-hop L3 U2U relay discovery for non-IP with model A | ZTE |
C1-253349 | Complete the defnition on List of multi-hop UE-to-UE relay paths IE | ZTE |
C1-253452 | 5G_ProSe_Ph3 work plan | CATT/Xiaoxue |
C1-253453 | Update multi-hop U2N relay selection procedure | CATT, InterDigital, NIST |
C1-253454 | Add multi-hop U2N relay reselection procedure | CATT/Xiaoxue |
C1-253455 | Update 5GMM capability for IM relay | CATT/Xiaoxue |
C1-253530 | Add multi-hop U2N relay reselection procedure | CATT, InterDigital, NIST |
C1-253537 | Update 5GMM capability for IM relay | CATT |
C1-253561 | Policy/Parameter provisioning to support PWS for 5G ProSe multi-hop U2N Relay | OPPO |
TDoc | Title | Source |
---|---|---|
C1-253063 | Work plan for NG_RTC_Ph2 | China Mobile |
C1-253064 | Support of DC multiplexing capability negotiation and indication in IMS network | China Mobile, Huawei, HiSilicon |
C1-253065 | DC setup configuration is inapplicable for standalone DC session | China Mobile |
C1-253066 | Update the IMS AS support of standalone DC session procedures | China Mobile |
C1-253067 | The requirement of the UE related to DC application in 8.1 | China Mobile |
C1-253068 | Additional information to indicate DC is initiated by the DC AS | China Mobile |
C1-253069 | Additional requirement of the IMS AS in KI#2 | China Mobile |
C1-253232 | The interaction of standalone DC with OIP | China Mobile |
C1-253264 | The interaction for network initiated data channel setup | Huawei, HiSilicon |
C1-253356 | Procedures for signing and verification of third-party user identity | Samsung |
C1-253367 | RCD info and role of S-CSCF | Samsung |
C1-253382 | Reference update: draft-ietf-sipcore-callinfo-rcd | Ericsson |
C1-253383 | Removal of EN on the resource structure for signing and verification of RCD info | Ericsson |
C1-253384 | HTTP signing requests with RCD info | Ericsson |
TDoc | Title | Source |
---|---|---|
C1-253204 | Work Plan for AIML_App | Lenovo |
C1-253304 | ML model retrieval service API | InterDigital |
C1-253305 | Split AIML operation pipeline API | InterDigital |
C1-253385 | Aimles_AIMLEClientRegistration API: DataSetAvailability definition | Ericsson / Nevenka |
C1-253386 | OpenAPI file for Aimles_AIMLEClientRegistration API | Ericsson / Nevenka |
C1-253387 | OpenAPI file for Aimlec_AIMLEClientServiceOperations API | Ericsson / Nevenka |
C1-253388 | Aimlec_AimlTaskTransfer API: support of 204 response | Ericsson / Nevenka |
C1-253389 | OpenAPI file for Aimlec_AimlTaskTransfer API | Ericsson / Nevenka |
C1-253390 | OpenAPI file for Aimles_AimlTaskTransfer API | Ericsson / Nevenka |
C1-253391 | OpenAPI file for Aimlec_MLModelTrainingCapabilityEva API | Ericsson / Nevenka |
C1-253392 | AimlModelInfo data type not listed in data model introduction | Ericsson / Nevenka |
C1-253393 | Update of OpenAPI file for Aimlec_FLGroupIndication API | Ericsson / Nevenka |
C1-253395 | FL group deletion flag in Aimlec_FLGroupIndication API | Ericsson / Sree |
TDoc | Title | Source |
---|---|---|
C1-253073 | Data source registration service operation | Samsung |
C1-253074 | Data source registration update service operation | Samsung |
C1-253075 | Data source deregistration service operation | Samsung |
C1-253076 | API and data model for data source registration management | Samsung |
C1-253077 | Work plan for the CT1 part of Metaverse_APP | Samsung |
C1-253306 | Updating the spatial anchor subscribe service operation | InterDigital |
C1-253307 | Updating the spatial anchor subscription update service operation | InterDigital |
C1-253308 | Updating the spatial anchor unsubscribe service operation | InterDigital |
C1-253331 | Digital asset profile management service operation definition | Nokia |
C1-253332 | Digital asset profile create service | Nokia |
C1-253337 | Digital asset profile UPDATE service | Nokia |
C1-253338 | Digital asset profile DELETE service | Nokia |
TDoc | Title | Source |
---|---|---|
C1-253189 | Clarifications to eCall setup, in-band MSD transmission and retry | Qualcomm Incorporated |
TDoc | Title | Source |
---|---|---|
C1-253040 | MPQUIC-IP without ATSSS-LL in 5GS | Lenovo |
C1-253041 | MPQUIC-IP without ATSSS-LL in EPS | Lenovo |
C1-253051 | Work Plan for MASSS | Apple |
C1-253058 | IP address versions for "link-specific multipath" IP addresses and proxy information when MPQUIC-E functionality is enabled | Nokia |
C1-253219 | Discussion on handling of multi-access PDU connectivity service failure | ZTE / Joy |
C1-253220 | Handling of multi-access PDU connectivity service failure | ZTE |
C1-253221 | Inclusion of ATSSS status in related session management messages | ZTE |
C1-253377 | Correction on the steering functionality included in ATSSS rule | Ericsson |
C1-253378 | Adding only MPQUIC-IP functionality case in PDU session establishment and modification procedures | Ericsson |
C1-253420 | Specifying cause of rejection due to incompatible ATSSS capabilities | Ericsson |
C1-253424 | Handling of incompatible ATSSS capabilities for EPC and non-3GPP | Ericsson |
C1-253430 | Specifying cause of rejection due to incompatible ATSSS capabilities in EPC | Ericsson / Neda |
C1-253529 | Correction to PDU session modification on mobility to 5GS –Alternative 1 | Samsung |
C1-253532 | Correction to PDU session modification on mobility to 5GS –Alternative 2 | Samsung |
TDoc | Title | Source |
---|---|---|
C1-253241 | Encoding of (S)RTP multiplexed media identification information component | Ericsson / Yumei |
C1-253242 | Correction to MID in (S)RTP multiplexed media identification information component | Ericsson |
C1-253243 | Reply LS on Encoding of (S)RTP Multiplexed Media Identification Information | Ericsson / Yumei |
C1-253320 | Alignment of (S)RTP multiplexed media identification information | Nokia |
C1-253473 | Discussion on coding of (S)RTP Multiplexed Media Identification Information | vivo |
C1-253474 | Correction on the coding of (S)RTP multiplexed media identification information and introducing the identification tag | vivo |
TDoc | Title | Source |
---|---|---|
C1-253458 | Clarification on the satellite identifier in optimized media routing | CATT |
C1-253459 | Additional of HTTP procedures for satellite coverage information provisioning | CATT |
C1-253460 | Additional of HTTP procedures for UE requesting the SCAI | CATT |
C1-253461 | Encoding UE satellite information | CATT |
C1-253462 | NRM Server exposing the S&F events to the VAL server procedure | CATT |
C1-253463 | VAL UE reports the UE satellite information procedure | CATT |
TDoc | Title | Source |
---|---|---|
C1-253396 | SEALDD enabled XR data transmission establishment service for XR application-HTTP | Ericsson |
C1-253397 | SEALDD enabled XR data transmission establishment for XR application-CoAP | Ericsson |
TDoc | Title | Source |
---|---|---|
C1-253300 | Clarify the behavior of the MSGin5G Server for deferred message | ZTE |
C1-253301 | Clarify the interaction between the SEAL Clients on constrained UEs and unconstrained UE | ZTE |
TDoc | Title | Source |
---|---|---|
C1-253126 | Work plan for the CT1 impact of the WID Non3GPPMob_Sec | Nokia |
TDoc | Title | Source |
---|---|---|
C1-253013 | Discussion paper: Optimization of message definitions for "Control plane CIoT EPS optimization" | Apple |
C1-253014 | Optimization of message definitions for "Control plane CIoT EPS optimization", message definition | Apple |
C1-253015 | Optimization of message definitions for "Control plane CIoT EPS optimization", EPD definition | Apple |
C1-253016 | Optimization of message definitions for "Control plane CIoT EPS optimization", procedure definition | Apple |
C1-253017 | New message for transferring data over NAS – Part 1: message format | Qualcomm Incorporated, European Space Agency, Eutelsat Group, Inmarsat, Viasat, Novamint, Sateliot, EchoStar, Deutsche Telekom, T-Mobile USA, Vodafone, CATT, Thales, Skylo |
C1-253018 | New message for transferring data over NAS – Part 2: procedures | Qualcomm Incorporated, European Space Agency, Eutelsat Group, Inmarsat, Viasat, Novamint, Sateliot, EchoStar, Deutsche Telekom, T-Mobile USA, Vodafone, CATT, Skylo |
C1-253081 | New message for transferring data over NAS – Part 1: message format | Qualcomm Incorporated, European Space Agency, Eutelsat Group, Inmarsat, Viasat, Novamint, Sateliot, EchoStar, Deutsche Telekom, T-Mobile USA, Vodafone, CATT, Thales, Skylo |
C1-253082 | New message for transferring data over NAS – Part 2: procedures | Qualcomm Incorporated, European Space Agency, Eutelsat Group, Inmarsat, Viasat, Novamint, Sateliot, EchoStar, Deutsche Telekom, T-Mobile USA, Vodafone, CATT, Skylo |
C1-253083 | Addition of protocol discriminator for transferring data over control plane | Qualcomm Incorporated, European Space Agency, Eutelsat Group, Immarsat, Viasat, Novamint, Sateliot, EchoStar, Deutsche Telekom, T-Mobile USA, Vodafone, vivo, CATT, Skylo |
C1-253096 | NAS overhead reduction for CP CIoT data transport, message format | Huawei, HiSilicon, MediaTek Inc. |
C1-253097 | NAS overhead reduction for CP CIoT data transport, procedure | Huawei, HiSilicon, MediaTek Inc. |
C1-253098 | NAS overhead reduction for CP CIoT data transport, message format | Huawei, HiSilicon |
C1-253099 | NAS overhead reduction for CP CIoT data transport, procedure | Huawei, HiSilicon |
C1-253292 | The handling on S&F wait timer in non-integrity protected reject messages | vivo/Hui |
C1-253295 | The message format on NAS overhead reduction for CP CIoT data transfer | vivo |
C1-253357 | Discussion to message format for control plane CIoT EPS optimization with optimized header | Ericsson / Ivo |
C1-253358 | Alternative-1 for control plane CIoT EPS optimization with optimized header - message definition | Ericsson |
C1-253359 | Alternative-1 for control plane CIoT EPS optimization with optimized header - EPD definition | Ericsson |
C1-253360 | Alternative-2 for control plane CIoT EPS optimization with optimized header - message definition | Ericsson |
C1-253361 | Control plane CIoT EPS optimization with optimized header - procedures | Ericsson / Ivo |
TDoc | Title | Source |
---|---|---|
C1-253205 | Discussion on the maximum size of the PWS warning message content | Qualcomm Incorporated / Amer |
C1-253206 | Clarification on the maximum warning message content size for PWS | Qualcomm Incorporated |
C1-253207 | UE handling of ETWS geofencing | Qualcomm Incorporated |
C1-253401 | Discussion on maximum warning message size in NB-IoT | Ericsson / Neda |
C1-253406 | void | void |
C1-253407 | Adding support for geofencing to ETWS primary notification | Ericsson, SyncTechno Inc., NTT DOCOMO |
C1-253411 | Discussion on geofencing in ETWS | Ericsson / Neda |
TDoc | Title | Source |
---|---|---|
C1-253506 | pCR on 6.2.1.2 Update and Code Additions | China Mobile Com. Corporation |
C1-253507 | pCR on MMTel Enabler Client request DC application profiles based on notification | China Mobile Com. Corporation |
TDoc | Title | Source |
---|---|---|
C1-253054 | AIoT protocol design principles | OPPO |
C1-253055 | Encoding of AIoT protocol | OPPO |
C1-253056 | AIoT protocol - error handling | OPPO |
C1-253088 | Discussion on AIoT device to AIOTF protocol design | Huawei, HiSilicon / Mikael |
C1-253089 | Pseudo-CR on naming of AIoT device to AIOTF protocol | Huawei, HiSilicon / Mikael |
C1-253090 | Pseudo-CR on AIoT-SP framework | Huawei, HiSilicon / Mikael |
C1-253091 | Addition of AIoT-SP as L3 protocol | Huawei, HiSilicon / Mikael |
C1-253092 | Pseudo-CR on AIoT-SP overview clause | Huawei, HiSilicon / Mikael |
C1-253093 | Pseudo-CR on AIoT-SP elementary procedures, general clause | Huawei, HiSilicon / Mikael |
C1-253094 | Pseudo-CR on AIoT-SP messages header information | Huawei, HiSilicon / Mikael |
C1-253119 | Pseudo-CR on AIoT-SP handling of unknown, unforeseen and erroneous protocol data | Huawei, HiSilicon / Mikael |
C1-253222 | Pseudo-CR on command procedures | ZTE / Joy |
C1-253223 | Pseudo-CR on definition of command messages | ZTE / Joy |
C1-253224 | Pseudo-CR on timers for command procedures | ZTE / Joy |
C1-253233 | Procedure on read command | China Mobile |
C1-253234 | Procedure on write command | China Mobile |
C1-253235 | Procedure on disable command | China Mobile |
C1-253236 | Cause value used in the procedures | China Mobile |
C1-253415 | General NAS protocol concepts for AIoT devices | Nokia |
C1-253448 | Pseudo-CR on AIoT clause 2 References | Lenovo / Thomas |
C1-253450 | Pseudo-CR on AIoT clause 5.1 | Lenovo / Thomas |
C1-253471 | Pseudo-CR on AIoT adding clause 6 | Lenovo / Thomas |
C1-253475 | Inventory procedure | vivo |
C1-253476 | General for system parameters | vivo |
C1-253545 | elemetary procedures for AIoT NAS protocol | Samsung |
C1-253547 | inventory procedure initiated by network | Samsung |
C1-253550 | Command procedure initiated by network | Samsung |
C1-253551 | inventory procedure accepted by AIoT device | Samsung |
C1-253552 | command procedure accepted by AIoT device | Samsung |
C1-253553 | Inventory procedure not accepted by AIoT device | Samsung |
C1-253554 | Command procedure not accepted by AIoT device | Samsung |
TDoc | Title | Source |
---|---|---|
C1-253315 | Update of conclusion for KI#1 | Nokia |
C1-253318 | Update of solution and conclusion for KI#2 | Nokia |
C1-253364 | Additional way to determine that disaster condition has ended | Ericsson |
C1-253419 | Solution #X: Solving the service discontinuity under mobility in disaster conditions | Nokia |
C1-253422 | Access Technology Control for Disaster Roaming Stability | LG Electronics |
C1-253531 | Update on the NOTE of solution #1 | China Telecommunications Corp. |
C1-253538 | Revised SID on MINT support in EPS for 5G-only national roaming UE | LG Electronics Deutschland |
C1-253540 | Update on the NOTE of solution #1 | China Telecom, LG Electronics |