3GPP TDocs (written contributions) at meeting
Meeting: S1-83 - 2018-08-20 to 2018-08-24, West Palm Beach, Florida
meeting id: S1-83 (click id for more info on this meeting)Click on the Tdoc to open its file.
TDoc | Title | Source | Remarks |
---|---|---|---|
S1‑182000 | Draft Agenda for SA1#83 | Chairman | imported from 3GU |
S1‑182001 | 2nd Draft agenda for SA1#83 | Chairman | imported from 3GU |
S1‑182002 | Final Schedule and Agenda with document allocation for SA1#83 | Chairman | imported from 3GU |
S1‑182003 | Report of SA1 topics at SA#81 | Chairman | imported from 3GU |
S1‑182004 | Draft minutes of SA1#82 | ETSI MCC | imported from 3GU |
S1‑182005 | Final minutes of SA1#82 | ETSI MCC | imported from 3GU |
S1‑182006 | Extract of the 3GPP Work Plan for SA1#83 | ETSI MCC | imported from 3GU |
S1‑182007 | Draft response LS to CT1 on validity of extended local emergency number list (C1-184943) | BlackBerry UK Limited | imported from 3GU |
S1‑182008 | Extended local emergency number list | BlackBerry UK Limited | imported from 3GU |
S1‑182009 | Performance requirements for 5G satellite access | THALES | imported from 3GU |
S1‑182010 | Mutiple access requirements related to 5G satellite access | THALES | imported from 3GU |
S1‑182011 | Mutiple access requirements related to 5G satellite access | THALES | imported from 3GU |
S1‑182012 | Connectivity aspects of 5G satellite access | THALES | imported from 3GU |
S1‑182013 | Efficient delivery of content using 5G satellite access network | THALES | imported from 3GU |
S1‑182014 | Efficient user plane aspects of 5G satellite access | THALES | imported from 3GU |
S1‑182015 | Mobility management related requirements for 5G satellite access | THALES | imported from 3GU |
S1‑182016 | NG-RAN sharing for 5G satellite access network | THALES | imported from 3GU |
S1‑182017 | QoS control aspects of 5G satellite access | THALES | imported from 3GU |
S1‑182018 | Regulatory and charging aspects related to 5G satellite access | THALES | imported from 3GU |
S1‑182019 | Satellite links between radio access network and core network | THALES | imported from 3GU |
S1‑182020 | Broadcast and multicast via satellite access networks | THALES | imported from 3GU |
S1‑182021 | Discussion paper on out of coverage communications | MINISTERE DE L'INTERIEUR | imported from 3GU |
S1‑182022 | Introduction to a SID proposal targeting Wireless Operating Rooms | B-Com | imported from 3GU |
S1‑182023 | New Feasibility Study on Wireless Operating Rooms (FS_WOR) | B-Com | imported from 3GU |
S1‑182024 | New SID on Smart Community and City Services over 3GPP Systems | OMESH Technologies Co. Ltd. | imported from 3GU |
S1‑182025 | Skeleton TR of Smart Community and City Services over 3GPP Systems | OMESH Technologies Co. Ltd. | imported from 3GU |
S1‑182026 | New SID on Smart Community and City Services over 3GPP Systems | OMESH Technologies Co. Ltd. | imported from 3GU |
S1‑182027 | Skeleton TR of Smart Community and City Services over 3GPP Systems | OMESH Technologies Co. Ltd. | imported from 3GU |
S1‑182028 | New SID on Smart Community and City Services over 3GPP Systems | OMESH Technologies Co. Ltd. | imported from 3GU |
S1‑182029 | Skeleton TR of Smart Community and City Services over 3GPP Systems | OMESH Technologies Co. Ltd. | imported from 3GU |
S1‑182030 | FS_SCC: Use case on Urban Infrastructure Management | OMESH Technologies Co. Ltd. | imported from 3GU |
S1‑182031 | FS_SCC: Use case on Urban Infrastructure Management | OMESH Technologies Co. Ltd. | imported from 3GU |
S1‑182032 | FS_SCC: Annex_Vertical_Requirements | OMESH Technologies Co. Ltd. | imported from 3GU |
S1‑182033 | FS_SCC: Annex_Vertical_Requirements | OMESH Technologies Co. Ltd. | imported from 3GU |
S1‑182034 | FS_SCC: Use case on Micro-environment services | OMESH Technologies Co. Ltd. | imported from 3GU |
S1‑182035 | FS_SCC: Use case on Micro-environment services | OMESH Technologies Co. Ltd. | imported from 3GU |
S1‑182036 | FS_SCC: Annex_Business_Model | OMESH Technologies Co. Ltd. | imported from 3GU |
S1‑182037 | FS_SCC: Annex_Business_Model | OMESH Technologies Co. Ltd. | imported from 3GU |
S1‑182038 | TBD | OMESH Technologies Co. Ltd. | imported from 3GU |
S1‑182039 | TBD | OMESH Technologies Co. Ltd. | imported from 3GU |
S1‑182040 | BroadWay procuring and testing 3GPP Mission Critical solutions | Public Safety Communication Europe (PSCE) Forum | imported from 3GU |
S1‑182041 | Alignment of REAR requirements | LG Electronics France | imported from 3GU |
S1‑182042 | Alignment of REAR requirements | LG Electronics France | imported from 3GU |
S1‑182043 | Alignment of REAR requirements | LG Electronics France | imported from 3GU |
S1‑182044 | Alignment of indirect communication requirements | LG Electronics France | imported from 3GU |
S1‑182045 | Alignment of REAR requirements | LG Electronics France | imported from 3GU |
S1‑182046 | FS_V2XIMP Consolidation of Requirements Set #1 - DP | LG Electronics France | imported from 3GU |
S1‑182047 | Consolidated Requirements Set#1 | LG Electronics France | imported from 3GU |
S1‑182048 | Correction to use cases | LG Electronics France | imported from 3GU |
S1‑182049 | Different QoS prediction for different V2X users | ZTE Corporation | imported from 3GU |
S1‑182050 | QoS aspect for extended sensor | ZTE Corporation | imported from 3GU |
S1‑182051 | Delaying periodic higher priority PLMN searches and reselection attempts when receiving eMBMS service in idle mode | Qualcomm Incorporated | imported from 3GU |
S1‑182052 | FS_ID_UAS: overview | Qualcomm Incorporated | imported from 3GU |
S1‑182053 | FS_ID_UAS: potential requirements for live data acquisition by UTM | Qualcomm Incorporated | imported from 3GU |
S1‑182054 | FS_ID_UAS: use case for distributed close-field separation service | Qualcomm Incorporated | imported from 3GU |
S1‑182055 | FS_ID_UAS: use case for local broadcast of UAS identity | Qualcomm Incorporated | imported from 3GU |
S1‑182056 | FS_ID_UAS: consolidated potential requirements | Qualcomm Incorporated | imported from 3GU |
S1‑182057 | FS_ID_UAS: conclusion and recommendation | Qualcomm Incorporated | imported from 3GU |
S1‑182058 | New WID on Remote Identification of Unmanned Aerial Systems | Qualcomm Incorporated | imported from 3GU |
S1‑182059 | Reply LS on Applicability of 3GPP PS Data off to Ethernet and Unstructured PDU Session Type | Qualcomm Incorporated | imported from 3GU |
S1‑182060 | FS_ID_UAS: considerations on ID value | Qualcomm UK Ltd | imported from 3GU |
S1‑182061 | Dynamic Group Participation | FirstNet | imported from 3GU |
S1‑182062 | LS on ESOA (EMEA Satellite Operators Association) - 5G for Satellite Systems | HUGHES Network Systems Ltd | imported from 3GU |
S1‑182063 | CR 22.819 Addition of requirements on positioning for the indoor commmunication inside a vessel | SyncTechno Inc., Korean Register of shipping | imported from 3GU |
S1‑182064 | TS Skeleton for 22.119 v16.0.0 | SyncTechno Inc. (Rapporteur) | imported from 3GU |
S1‑182065 | Scope | SyncTechno Inc. (Rapporteur) | imported from 3GU |
S1‑182066 | Overview | SyncTechno Inc. (Rapporteur) | imported from 3GU |
S1‑182067 | General Requirements | SyncTechno Inc., Korean Register of shipping | imported from 3GU |
S1‑182068 | Requirements of basic capabilities | SyncTechno Inc., Korean Register of shipping | imported from 3GU |
S1‑182069 | Requirements of multi-access and seamless mobility | SyncTechno Inc., Korean Register of shipping | imported from 3GU |
S1‑182070 | Requirements of warning notification and emergency request for maritime safety | SyncTechno Inc., Korean Register of shipping | imported from 3GU |
S1‑182071 | Requirements of MC Services applicable to maritime usage | SyncTechno Inc., Korean Register of shipping | imported from 3GU |
S1‑182072 | CR 22.179 Application of MCPTT to maritime usage | SyncTechno Inc., Korean Register of shipping | imported from 3GU |
S1‑182073 | CR 22.280 Application of MCX Services to maritime usage | SyncTechno Inc. | imported from 3GU |
S1‑182074 | CR 22.281 Application of MCVideo to maritime usage | SyncTechno Inc., Korean Register of shipping | imported from 3GU |
S1‑182075 | CR 22.282 Application of MCData to maritime usage | SyncTechno Inc., Korean Register of shipping | imported from 3GU |
S1‑182076 | Draft LS to IALA on maritime works in 3GPP | SyncTechno Inc. (Rapporteur) | imported from 3GU |
S1‑182077 | Presentation of Spec 22.119 to TSG for information | SyncTechno Inc. (Rapporteur) | imported from 3GU |
S1‑182078 | Draft TR 22.827 Skeleton Study on Audio-Visual Service Production | EBU | imported from 3GU |
S1‑182079 | Draft TR 22.827 Section 4 Overview | EBU | imported from 3GU |
S1‑182080 | Draft TR 22.827 Section 1 Scope | EBU | imported from 3GU |
S1‑182081 | FS_LUCIA: Consolidation of potential requirements | Deutsche Telekom AG | imported from 3GU |
S1‑182082 | FS_LUCIA: CR on Consolidation of potential requirements | Deutsche Telekom AG | imported from 3GU |
S1‑182083 | UIA Service Requirements | Deutsche Telekom AG | imported from 3GU |
S1‑182084 | UIA Charging Requirements | Deutsche Telekom AG | imported from 3GU |
S1‑182085 | Same operator for all MUD identities | Ericsson LM | imported from 3GU |
S1‑182086 | Reply LS to LS on Multi-identity and multi-device requirements | Ericsson LM | imported from 3GU |
S1‑182087 | Enhancements for authorisation to invoke automatic user regrouping | Kapsch CarrierCom | imported from 3GU |
S1‑182088 | Enhancement for interworking of group communication between FRMCS and GSM-R | Kapsch CarrierCom | imported from 3GU |
S1‑182089 | Update for gap analysis in TR 22.889 | Kapsch CarrierCom | imported from 3GU |
S1‑182090 | Comment on the use case 5.1 for Initial authorisation to operate | Orange | imported from 3GU |
S1‑182091 | Comment on the use case 5.2 for live data acquisition by UTM | Orange | imported from 3GU |
S1‑182092 | New use case for detection and management of a rogue UAS | Orange | imported from 3GU |
S1‑182093 | Support to accurate and reliable handling of containers | Orange | imported from 3GU |
S1‑182094 | Support to accurate and reliable handling of containers | Orange | imported from 3GU |
S1‑182095 | Clarification on Delay Tolerant | LG Electronics France | imported from 3GU |
S1‑182096 | Clarification on Delay Tolerant | LG Electronics France | imported from 3GU |
S1‑182097 | Clarification on Delay Tolerant | LG Electronics France | imported from 3GU |
S1‑182098 | Clarification to Delay Tolerant | LG Electronics France | imported from 3GU |
S1‑182099 | Cloud-based NLOS UAV operation | LG Electronics France | imported from 3GU |
S1‑182100 | Ethernet support requirements from CAV to CyberCAV | Qualcomm Incorporated | imported from 3GU |
S1‑182101 | Ethernet support in SMARTER vs CyberCAV | Qualcomm Incorporated | imported from 3GU |
S1‑182102 | Comments on CyberCAV requirements | Qualcomm Incorporated | imported from 3GU |
S1‑182103 | CyberCAV network name requirement | Qualcomm Incorporated | imported from 3GU |
S1‑182104 | Comments on CyberCAV definitions | Qualcomm Incorporated | imported from 3GU |
S1‑182105 | FS_5GMSG Consolidated potential requirements | China Mobile (Hangzhou) Inf. | imported from 3GU |
S1‑182106 | FS_5GMSG Gap analysis | China Mobile (Hangzhou) Inf. | imported from 3GU |
S1‑182107 | FS_5GMSG Conclusion and recommendations | China Mobile (Hangzhou) Inf. | imported from 3GU |
S1‑182108 | TR22.824 clean up | China Mobile (Hangzhou) Inf. | imported from 3GU |
S1‑182109 | TR 22.824 V1.1.0 | China Mobile (Hangzhou) Inf. | imported from 3GU |
S1‑182110 | Presentation of Report to TSG: TR 22.824, Version 1.1.0 | China Mobile (Hangzhou) Inf. | imported from 3GU |
S1‑182111 | Add reqs to TS 22.228 for IMS slicing | China Mobile Com. Corporation | imported from 3GU |
S1‑182112 | New SID on Assets Tracking Use cases | NOVAMINT | imported from 3GU |
S1‑182113 | Motivation to study Assets Tracking use cases | NOVAMINT | imported from 3GU |
S1‑182114 | CR 22.268 Additional requirements in KPAS (Rel-15) | SyncTechno Inc. | imported from 3GU |
S1‑182115 | CR 22.268 Additional requirements in KPAS (Rel-16) | SyncTechno Inc. | imported from 3GU |
S1‑182116 | Way forward for normative phase of FS_V2XIMP | LG Electronics France | imported from 3GU |
S1‑182117 | Discussion on Use Case for Interactive Service, Cloud Rendering for Games | Tencent, China Mobile, China Telecom, China Unicom | imported from 3GU |
S1‑182118 | KPIs for horizontal and vertical positioning service levels | ESA | imported from 3GU |
S1‑182119 | Other KPIS for 5G positioning services | ESA | imported from 3GU |
S1‑182120 | Security requirements for 5G positioning services | ESA | imported from 3GU |
S1‑182121 | Update description (clause 7.3.1) of 5G positioning services | ESA | imported from 3GU |
S1‑182122 | Additional consideration (clause 6.3) to support the consolidated requirements | ESA | imported from 3GU |
S1‑182123 | Corrections to annex A | ESA | imported from 3GU |
S1‑182124 | TR 22.842 Skeleton for NCIS | OPPO | imported from 3GU |
S1‑182125 | Proposal for absolute high but relative low speed use case for NCIS | OPPO | imported from 3GU |
S1‑182126 | Proposal for interactive service use case for NCIS | OPPO | imported from 3GU |
S1‑182127 | Proposal for Users from multiple PLMN joining the same group | OPPO | imported from 3GU |
S1‑182128 | Proposal for Interactive Service in Proximity | OPPO | imported from 3GU |
S1‑182129 | Proposal for Interactive Service in non-Proximity | OPPO | imported from 3GU |
S1‑182130 | Proposal for User in proximity joining or leaving a group | OPPO | imported from 3GU |
S1‑182131 | Proposal for User in non-proximity joining or leaving a group | OPPO | imported from 3GU |
S1‑182132 | Clarification for Inter-RAT Mobility requirement for realtime service | OPPO, China Mobile, China Telecom, Tencent, CATT | imported from 3GU |
S1‑182133 | New WID on the 5GMSG Service requirements | China Mobile (Hangzhou) Inf. | imported from 3GU |
S1‑182134 | MEC Support for V2X Use Cases | Tencent, China Telecom, China Mobile, OPPO | imported from 3GU |
S1‑182135 | Draft Reply LS on validity of extended local emergency number list | Deutsche Telekom AG | imported from 3GU |
S1‑182136 | Emergency Call Type alignment and clarification | Deutsche Telekom AG | imported from 3GU |
S1‑182137 | 5GMSG: alignment of gap and unified control case | China Unicom | imported from 3GU |
S1‑182138 | 5GMSG: message size of remote control | China Unicom | imported from 3GU |
S1‑182139 | FS_BMNS terminology alignment | Nokia, Nokia Shanghai Bell | imported from 3GU |
S1‑182140 | FS_BMNS editor’s note | Nokia, Nokia Shanghai Bell | imported from 3GU |
S1‑182141 | FS_BMNS considerations | Nokia, Nokia Shanghai Bell, NTT DoCoMo | imported from 3GU |
S1‑182142 | FS_BMNS consolidated potential requirements | Nokia, Nokia Shanghai Bell, NTT DoCoMo | imported from 3GU |
S1‑182143 | FS_BMNS conclusion | Nokia, Nokia Shanghai Bell | imported from 3GU |
S1‑182144 | 5GLAN discussion of editorials on security and charging requirements | Nokia, Nokia Shanghai Bell | imported from 3GU |
S1‑182145 | 5GLAN security requirements | Nokia, Nokia Shanghai Bell | imported from 3GU |
S1‑182146 | 5GLAN charging requirements | Nokia, Nokia Shanghai Bell | imported from 3GU |
S1‑182147 | Affiliation and de-affiliation conditions in correspondence with Functional Alias | Nokia, Nokia Shanghai Bell, UIC | imported from 3GU |
S1‑182148 | Adding gap analysis information for 6.2 "Multi-train voice communication for Drivers and Ground FRMCS User(s) communication" | Nokia, Nokia Shanghai Bell | imported from 3GU |
S1‑182149 | Adding gap analysis information for 6.3 "On-train outgoing voice communication from the Driver towards the Controller(s) of the train" | Nokia, Nokia Shanghai Bell | imported from 3GU |
S1‑182150 | Adding gap analysis information for 6.4 "Railway emergency communication" | Nokia, Nokia Shanghai Bell | imported from 3GU |
S1‑182151 | Adding gap analysis information for 6.9 "Data communication for possession management" | Nokia, Nokia Shanghai Bell | imported from 3GU |
S1‑182152 | Adding gap analysis information for 6.10 "Recording of communication" | Nokia, Nokia Shanghai Bell | imported from 3GU |
S1‑182153 | Adding gap analysis information for 6.15 "On-train incoming voice or video communication from the Controller(s) of the train towards the drivers" | Nokia, Nokia Shanghai Bell | imported from 3GU |
S1‑182154 | Clarification BMNS study – business models | KPN | imported from 3GU |
S1‑182155 | Explanation CR_5GLAN | KPN | imported from 3GU |
S1‑182156 | CR - 5GLAN Requirements | KPN | imported from 3GU |
S1‑182157 | Study on MUltihop RElays | KPN | imported from 3GU |
S1‑182158 | New Feasibility Study on Communication Services for Critical Medical Applications (FS_CMED) | B-Com | imported from 3GU |
S1‑182159 | Requirement for Operator controlled Caching service delivery | China Telecom,CATT,ZTE | imported from 3GU |
S1‑182160 | Charging Requirement for Operator controlled Caching service delivery | CATT, China Telecom,ZTE | imported from 3GU |
S1‑182161 | New SID proposal for Access Control for Secondary Access | LG Electronics France | imported from 3GU |
S1‑182162 | Access control for secondary access | LG Electronics France | imported from 3GU |
S1‑182163 | Access control for secondary access | LG Electronics France | imported from 3GU |
S1‑182164 | Revised WID on multi-device and multi-identity (MuD) | ETRI | imported from 3GU |
S1‑182165 | Adding a new requirement about default identity | ETRI | imported from 3GU |
S1‑182166 | Discussion on the type-a / type-b network requirements | Vodafone Group Plc | imported from 3GU |
S1‑182167 | Type-a and type-b network requirements | Vodafone Group Plc | imported from 3GU |
S1‑182168 | Discussion on the network service exposure requirements | Vodafone Group Plc | imported from 3GU |
S1‑182169 | Network service exposure requirements | Vodafone Group Plc | imported from 3GU |
S1‑182170 | Inclusion of the CIoT requirements | Vodafone Group Plc | imported from 3GU |
S1‑182171 | Inclusion of the CIoT requirements | Vodafone Group Plc | imported from 3GU |
S1‑182172 | Inclusion of the CIoT requirements | Vodafone Group Plc | imported from 3GU |
S1‑182173 | Discussion paper for potential LS reply on AIOTI 5G paper | FUJITSU Laboratories of Europe | imported from 3GU |
S1‑182174 | Inclusion of the 5G requirements -- Service continuity | Vodafone Group Plc | imported from 3GU |
S1‑182175 | Inclusion of the 5G requirements -- positioning requirements | Vodafone Group Plc | imported from 3GU |
S1‑182176 | Inclusion of the 5G requirements – efficient use plane | Vodafone Group Plc | imported from 3GU |
S1‑182177 | Inclusion of the 5G requirements -- Efficient content delivery | Vodafone Group Plc | imported from 3GU |
S1‑182178 | Inclusion of the 5G requirements -- Context aware network | Vodafone Group Plc | imported from 3GU |
S1‑182179 | Emergency Call Type alignment and clarification | Deutsche Telekom AG | imported from 3GU |
S1‑182180 | New SID Proposal: Study on 5G enhancement for UAVs with fixed routing | China Unicom | imported from 3GU |
S1‑182181 | Study on Enhanced 3GPP support for Mobile Edge Services | KT Corp. | imported from 3GU |
S1‑182182 | Discussion on Study on Enhanced 3GPP support for Mobile Edge Services | KT Corp. | imported from 3GU |
S1‑182183 | Audio Streaming in professional live performances | Sennheiser Electronic GmbH | imported from 3GU |
S1‑182184 | On-Site Live Audio Presentation | Sennheiser Electronic GmbH | imported from 3GU |
S1‑182185 | Draft LS reply SA1 to SA6 on last MCX User having registered a specific functional alias is leaving | Union Inter. Chemins de Fer | imported from 3GU |
S1‑182186 | MCData periodical and non-periodical communication | Union Inter. Chemins de Fer | imported from 3GU |
S1‑182187 | MCCore dynamic prioritization | Union Inter. Chemins de Fer | imported from 3GU |
S1‑182188 | Definitions for TR 22.287 | Sennheiser Electronic GmbH | imported from 3GU |
S1‑182189 | CR_subclause 12.19_allocation and isolation of communication resources | Union Inter. Chemins de Fer | imported from 3GU |
S1‑182190 | CR_AutomaticTrain Control | Union Inter. Chemins de Fer | imported from 3GU |
S1‑182191 | CR_FRMCS Equipment capabilities for multiple FRMCS Users | Union Inter. Chemins de Fer | imported from 3GU |
S1‑182192 | CR_subclause 7.3.5_voice_comm_train_staff_to_ground | Union Inter. Chemins de Fer | imported from 3GU |
S1‑182193 | Addition of inter-site Ethernet transport service | NTT DOCOMO INC. | imported from 3GU |
S1‑182194 | CR_12.9.5_Potential_ requirements_ and_ gap_analysis_ bearer flexibility | Union Inter. Chemins de Fer | imported from 3GU |
S1‑182195 | Addition of inter-site Ethernet transport service to TS 22.261 | NTT DOCOMO INC. | imported from 3GU |
S1‑182196 | Adding the post-conditions of Millisecond-Level Precise Load Control | China Telecomunication Corp. | imported from 3GU |
S1‑182197 | FS_BMNS: Figure to illustrate clause 5.5 | Sennheiser Electronic GmbH | imported from 3GU |
S1‑182198 | FRMCS System/User - Roaming capabilities | Union Inter. Chemins de Fer | imported from 3GU |
S1‑182199 | enhancement on initial UAV authorization operation | HuaWei Technologies Co., Ltd | imported from 3GU |
S1‑182200 | CR_Chapter 12.10 - QoS in a railway environment | Union Inter. Chemins de Fer | imported from 3GU |
S1‑182201 | Discussion on 5G network enhancement with application service assistance in Rel-17 | Huawei, Hisilicon | imported from 3GU |
S1‑182202 | New use case on voice communication transfer and forwarding | Union Inter. Chemins de Fer | imported from 3GU |
S1‑182203 | additional consideration for security | HuaWei Technologies Co., Ltd | imported from 3GU |
S1‑182204 | Changes to subclause 9.16 - Arbitration | Union Inter. Chemins de Fer | imported from 3GU |
S1‑182205 | Use case of UAV type identification | HuaWei Technologies Co., Ltd | imported from 3GU |
S1‑182206 | Adding GSM-R interworking requirmenst for Assured Voice Communication (AVC) | Union Inter. Chemins de Fer | imported from 3GU |
S1‑182207 | Use case of UAV fly range restriction | HuaWei Technologies Co., Ltd | imported from 3GU |
S1‑182208 | off-network UAV identification | HuaWei Technologies Co., Ltd | imported from 3GU |
S1‑182209 | Clock Synchronization Service Performance | HuaWei Technologies Co., Ltd | imported from 3GU |
S1‑182210 | Annex: timeliness attribute for time accuracy | HuaWei Technologies Co., Ltd | imported from 3GU |
S1‑182211 | New text on Management role models | ETRI | imported from 3GU |
S1‑182212 | Private slice management in role model scenarios | ETRI | imported from 3GU |
S1‑182213 | Annex: communication service availability and reliability vs PER | HuaWei Technologies Co., Ltd | imported from 3GU |
S1‑182214 | New SID on Smart Community and City Services over 3GPP Systems | OMESH Technologies Co. Ltd. | imported from 3GU |
S1‑182215 | Skeleton TR of Smart Community and City Services over 3GPP Systems | OMESH Technologies Co. Ltd. | imported from 3GU |
S1‑182216 | Discussion on the Future Services of Smart Community and City over 3GPP Systems | OMESH Technologies Co. Ltd. | imported from 3GU |
S1‑182217 | Comments on the enIMS use case Remote camera control | Sony Mobile Communications | imported from 3GU |
S1‑182218 | Discussion on VN and network operator for 5GLAN normative | Huawei Technologies France | imported from 3GU |
S1‑182219 | QoS list to support V2X critical applications | Huawei Technologies France | imported from 3GU |
S1‑182220 | TR 22.804 – adding CRC and FIFO to list of abbreviations | Siemens AG | imported from 3GU |
S1‑182221 | QoS list to support V2X critical applications | Huawei Technologies France | imported from 3GU |
S1‑182222 | Application originated messages for stationary IoT sensors | Sony Mobile Communications | imported from 3GU |
S1‑182223 | Application originated messages for IoT sensors | Sony Mobile Communications | imported from 3GU |
S1‑182224 | TR 22.804 – attending orphaned annexes | Siemens AG | imported from 3GU |
S1‑182225 | Addition of requirements for Group Communication System Enabler | Huawei Technologies Co. Ltd. | imported from 3GU |
S1‑182226 | TR 22.804 - editorial cleanup of annexe B | Siemens AG | imported from 3GU |
S1‑182227 | Addition of requirement for VR Telepresence | Huawei Technologies Co. Ltd. | imported from 3GU |
S1‑182228 | TR 22.804 – annexe F – correction of entries for use cases 5.6.2 and 5.6.3 | Siemens AG; Ericsson | imported from 3GU |
S1‑182229 | Interworking with ONVIF cameras | Huawei Technologies Co. Ltd. | imported from 3GU |
S1‑182230 | Correction of positioning service performance requirements | Fraunhofer IIS | imported from 3GU |
S1‑182231 | Support for services using Artificial Intelligent | Huawei Technologies Co. Ltd. | imported from 3GU |
S1‑182232 | Updates to QoS Monitoring Description | Huawei Technologies Co. Ltd. | imported from 3GU |
S1‑182233 | Accurate Positioning for the Factories of the Future | Fraunhofer IIS | imported from 3GU |
S1‑182234 | CyberCAV- Positioning Service Performance Requirements | Fraunhofer IIS | imported from 3GU |
S1‑182235 | EU-alert applicability for 5G | KPN N.V. | imported from 3GU |
S1‑182236 | WID on Business Role Models for Network Slicing (BRMNS) | Nokia, Nokia Shanghai Bell | imported from 3GU |
S1‑182237 | Addition of a new UAC Access Category for RRC level MO signalling | Ericsson | imported from 3GU |
S1‑182238 | Enhanced network slice requirements based on business role models | Nokia, Nokia Shanghai Bell | imported from 3GU |
S1‑182239 | cyberCAV – 22.104 – clause 1 (introduction) | Siemens AG | imported from 3GU |
S1‑182240 | cyberCAV – 22.104 – order of annexes | Siemens AG | imported from 3GU |
S1‑182241 | Addition of new Access category for “MO signalling on RRC level resulting from other than paging” | Ericsson | imported from 3GU |
S1‑182242 | Presentation of Specification to TSG SA#81: TS 22.104, Version 1.0.0 | Siemens AG | imported from 3GU |
S1‑182243 | Addition of new Access category for “MO signalling on RRC level resulting from other than paging”- Mirror CR | Ericsson | imported from 3GU |
S1‑182244 | cyberCAV – TS 22.104 – clause 1 (scope) | Siemens AG | imported from 3GU |
S1‑182245 | UAC Alignment CR removing editor’s note | Ericsson | imported from 3GU |
S1‑182246 | UAC Alignment CR removing editors note – mirror CR | Ericsson | imported from 3GU |
S1‑182247 | TR 22.804 - editorial cleanup of “private” | Siemens AG | imported from 3GU |
S1‑182248 | 22.804 – cleanup of “private” | Siemens AG | imported from 3GU |
S1‑182249 | TR 22.804 – seamless service continuity for wind farms | Siemens AG | imported from 3GU |
S1‑182250 | Discussion paper on type-a/type-b network definitions | Ericsson | imported from 3GU |
S1‑182251 | Private network requirements | Ericsson | imported from 3GU |
S1‑182252 | Correction to EAB | Vencore Labs | imported from 3GU |
S1‑182253 | Correction to EAB | Vencore Labs, OEC, AT&T | imported from 3GU |
S1‑182254 | Correction to EAB | Vencore Labs, OEC, AT&T | imported from 3GU |
S1‑182255 | Public emergency calls | Ericsson LM, Kapsch CarrierCom | imported from 3GU |
S1‑182256 | Proposed priorities for 5G_HYPOS normative work in SA1#83 | ESA | imported from 3GU |
S1‑182257 | Explanation on CR KPI for Horizontal and Vertical positioning services | ESA | imported from 3GU |
S1‑182258 | Update of 6.4.2 | ESA | imported from 3GU |
S1‑182259 | TR 22.854 Outline Changes to Include MPS Voice | Vencore Labs, OEC, AT&T | imported from 3GU |
S1‑182260 | ID_UAS – enhancement on use case for initial authorization to operate | T-Mobile Austria GmbH | imported from 3GU |
S1‑182261 | MPS Voice during International Roaming | Vencore Labs, OEC, AT&T | imported from 3GU |
S1‑182262 | DTS Invoked during International Roaming | Vencore Labs, OEC. AT&T | imported from 3GU |
S1‑182263 | Data Transport Service (DTS) Invoked from a Public UE | Vencore Labs, OEC, AT&T | imported from 3GU |
S1‑182264 | Data Transport Service (DTS) Invoked from an IoT device | Vencore Labs, OEC, AT&T | imported from 3GU |
S1‑182265 | MPS Capable Enterprise Network Activation of DTS for MPS Subscribed IoT Devices | Vencore Labs | imported from 3GU |
S1‑182266 | MPS for DTS QoS and Media Encryption Modifications | Vencore Labs, OEC, AT&T | imported from 3GU |
S1‑182267 | Modification of multi-identity scope | Orange Romania | imported from 3GU |
S1‑182268 | Gap analysis of [R-12.13-0004] LMR interworking | Hansung University, ETRI | imported from 3GU |
S1‑182269 | Clarify the method of configuring the UE to use Access Identity 1 | Vencore Labs, OEC, AT&T, T-Mobile USA, Verizon, Sprint | imported from 3GU |
S1‑182270 | Proposal for normative cyberCAV requirements | Nokia, Nokia Shanghai Bell | imported from 3GU |
S1‑182271 | Gap analysis of [R-12.13-0003] LMR interworking | Hansung University, ETRI | imported from 3GU |
S1‑182272 | Support for use of licensed and unlicensed bands | Nokia, Nokia Shanghai Bell | imported from 3GU |
S1‑182273 | Clarify the method of configuring the UE to use Access Identity 1 | Vencore Labs | imported from 3GU |
S1‑182274 | Support for networks for non-public use | Nokia, Nokia Shanghai Bell | imported from 3GU |
S1‑182275 | Support for security requirements based on FS_CAV | Nokia, Nokia Shanghai Bell | imported from 3GU |
S1‑182276 | Addition of Informative Annex for QoS Monitoring | Siemens AG | imported from 3GU |
S1‑182277 | Reply LS on Multi-identity and multi-device requirements | Orange Romania | imported from 3GU |
S1‑182278 | BMNS – Management of network selection information | Siemens AG | imported from 3GU |
S1‑182279 | A NOTE for clarifying the general scope of Emergency Responder use case | LG Electronics Mobile Research | imported from 3GU |
S1‑182280 | SAE International’s Levels of Automation reference link | LG Electronics Mobile Research | imported from 3GU |
S1‑182281 | SAE International’s Levels of Automation reference link | LG Electronics Mobile Research | imported from 3GU |
S1‑182282 | SAE International’s Levels of Automation reference link | LG Electronics Mobile Research | imported from 3GU |
S1‑182283 | cyberCAV – 22.104 – summary of service performance requirements | Siemens AG | imported from 3GU |
S1‑182284 | SAE International’s Levels of Automation reference link | LG Electronics Mobile Research | imported from 3GU |
S1‑182285 | cyberCAV – 22.104 – annexe – communication errors | Siemens AG | imported from 3GU |
S1‑182286 | Gap analysis of [R-12.13-0001] LMR interworking | Hansung University, ETRI | imported from 3GU |
S1‑182287 | Clarification on consolidated potential requirements appliable to V2X | LG Electronics Mobile Research | imported from 3GU |
S1‑182288 | cyberCAV - Deployment option of type-a networks | Siemens AG | imported from 3GU |
S1‑182289 | Draft Use case on Container Tracking | NOVAMINT | imported from 3GU |
S1‑182290 | CyberCAV definitions, requirements and slicing | T-Mobile Austria GmbH | imported from 3GU |
S1‑182291 | 5G positioning requirements also appliable to V2X scenarios | LG Electronics Mobile Research | imported from 3GU |
S1‑182292 | Gap analysis of [R-12.11.5-0001] and [R-12.11.5-0002] | Hansung University, ETRI | imported from 3GU |
S1‑182293 | Motivation to study Assets Tracking use cases | NOVAMINT | imported from 3GU |
S1‑182294 | Gap analysis of [R-12.11.5-0003] | Hansung University | imported from 3GU |
S1‑182295 | Gap analysis of [R-12.11.5-0005] | Hansung University, ETRI | imported from 3GU |
S1‑182296 | cyberCAV – 22.104 – annexe – characteristic parameters and influence quantities | Siemens AG | imported from 3GU |
S1‑182297 | Clarification on the PLMN selection mode for RLOS | Intel | imported from 3GU |
S1‑182298 | FS_ID_UAS: Update Definition and Use case 5.1 | Intel | imported from 3GU |
S1‑182299 | FS_ID_UAS: Use case for UAS Discovery | Intel | imported from 3GU |
S1‑182300 | FS_ID_UAS: Use case of UAS Based Remote Inspection | Intel | imported from 3GU |
S1‑182301 | FS_ID_UAS: Use case of UAS Identification via UAV Controller | Intel | imported from 3GU |
S1‑182302 | pCR to 22.825 on enhancement on initial UAV authorization operation | Huawei | imported from 3GU |
S1‑182303 | pCR to 22.825 on additional consideration for security | Huawei | imported from 3GU |
S1‑182304 | pCR to 22.825 on Use case of UAV type identification | Huawei | imported from 3GU |
S1‑182305 | pCR to 22.825 on Use case of UAV fly range restriction | Huawei | imported from 3GU |
S1‑182306 | pCR to 22.825 on off-network UAV identification | Huawei | imported from 3GU |
S1‑182307 | pCR to 22.104 on Clock Synchronization Service Performance | Huawei | imported from 3GU |
S1‑182308 | pCR to 22.104 on Annex: timeliness attribute for time accuracy | Huawei | imported from 3GU |
S1‑182309 | pCR to 22.104 on Annex: communication service availability and reliability vs PER | Huawei | imported from 3GU |
S1‑182310 | Reply LS on Change default exempt status for BIP with respect to 3GPP PS Data Off feature | C1-183728 | imported from 3GU |
S1‑182311 | LS on Applicability of 3GPP PS Data off to Ethernet and Unstructured PDU Session Type | C1-183851 | imported from 3GU |
S1‑182312 | LS on Multi-identity and multi-device requirements | C1-184818 | imported from 3GU |
S1‑182313 | LS on the applicability of service area restriction and NSSAIs to EPLMNs. | C1-184906 | imported from 3GU |
S1‑182314 | LS on validity of extended local emergency number list | C1-184943 | imported from 3GU |
S1‑182315 | Reply LS on SoR mechanism | C6-180250 | imported from 3GU |
S1‑182316 | LS on the start of ETSI STF555 - "Study of use cases and communications involving IoT devices in emergency situations" | ETSI EMTEL(18)000026 | imported from 3GU |
S1‑182317 | Liaison ESOA (EMEA Satellite Operators Association) on 5G for Satellite Systems | ESOA-LS-2018-1 | imported from 3GU |
S1‑182318 | LS on new ITU-T Recommendations related to Immersive Live Experience (ILE) | ITU SG16-LS110 | imported from 3GU |
S1‑182319 | Publication of new paper on network slicing and future plans | GSMA NEST_35_00x | imported from 3GU |
S1‑182320 | Reply LS on the transmission of video over PC5 interface | R1-1807870 | imported from 3GU |
S1‑182321 | LS on Addition of access/load control for CE | R2-1808898 | imported from 3GU |
S1‑182322 | LS on Slice based Wait timer in NR RRC release | R2-1810964 | imported from 3GU |
S1‑182323 | LS on PS Data Off for non-IP services | S2-185611 | imported from 3GU |
S1‑182324 | LS OUT on Location Service exposure to NG-RAN | S2-185792 | imported from 3GU |
S1‑182325 | Reply LS on LS to 3GPP on QoS Prediction | S2-185846 | imported from 3GU |
S1‑182326 | Reply LS on Delay Tolerant Access and Low Access Priority in 5GS | S2-187600 | imported from 3GU |
S1‑182327 | Reply LS on Removal of LTE specific terminology from Group Communication System Enablers TS 22.468 | S3-182031 | imported from 3GU |
S1‑182328 | LS Out for 5G slices roaming | S3i180376 | imported from 3GU |
S1‑182329 | LS on the transmission of video over PC5 interface | S4-180980 | imported from 3GU |
S1‑182330 | Reply LS to 5GAA on QoS Prediction | S5-183631 | imported from 3GU |
S1‑182331 | LS on last MCX User having registered a specific functional alias is leaving | S6-180966 | imported from 3GU |
S1‑182332 | Reply to LS on MCVideo capability information sharing | S6-181282 | imported from 3GU |
S1‑182333 | LS on use of ITS dedicated spectrum within V2X UE | S6-181288 | imported from 3GU |
S1‑182334 | Additional Reply LS on eV2X evaluation methodology | SAE C-V2X | imported from 3GU |
S1‑182335 | LS on consent of draft Recommendation Y.3103 (formerly Y.IMT2020-BM) | ITU SG13-LS63 | imported from 3GU |
S1‑182336 | Reply LS to “5G for Industrial Communication” | SP-180608 | imported from 3GU |
S1‑182337 | Reply-LS on secure storage and processing of subscription credentials | S3-180851 | imported from 3GU |
S1‑182338 | Railway drafting agenda | Rapporteur / Session Chair | imported from 3GU |
S1‑182339 | Railway drafting report | Rapporteur / Session Chair | imported from 3GU |
S1‑182340 | enIMS+FS_MPS2+FS_AVPROD+FS_NCIS drafting agenda | Rapporteur / Session Chair | imported from 3GU |
S1‑182341 | enIMS++FS_MPS2+FS_AVPROD+FS_NCIS drafting report | Rapporteur / Session Chair | imported from 3GU |
S1‑182342 | 5GLAN+UIA+FS_LUCIA+FS_5GMSG+FS_BMNS drafting agenda | Rapporteur / Session Chair | imported from 3GU |
S1‑182343 | 5GLAN+UIA+FS_LUCIA+FS_5GMSG+FS_BMNS drafting report | Rapporteur / Session Chair | imported from 3GU |
S1‑182344 | TS22.104v1.0.0 to include agreements at this meeting | Rapporteur (Siemens) | imported from 3GU |
S1‑182345 | cyberCAV drafting agenda | Rapporteur / Session Chair | imported from 3GU |
S1‑182346 | cyberCAV drafting report | Rapporteur / Session Chair | imported from 3GU |
S1‑182347 | 5GSAT+MARCOM+FS_MARCOM+5G_HYPOS+FS_5G_HYPOS drafting agenda | Rapporteur / Session Chair | imported from 3GU |
S1‑182348 | 5GSAT+MARCOM+FS_MARCOM+5G_HYPOS+FS_5G_HYPOS drafting report | Rapporteur / Session Chair | imported from 3GU |
S1‑182349 | TS22.119v1.0.0 to include agreements at this meeting | Rapporteur (SyncTechno Inc.) | imported from 3GU |
S1‑182350 | TR22.830v1.1.0 to include agreements at this meeting | Rapporteur (Nokia) | imported from 3GU |
S1‑182351 | Cover page for presentation of TR22.830v1.1.0 | Rapporteur (Nokia) | imported from 3GU |
S1‑182352 | TS22.854v0.4.0 to include agreements at this meeting | Rapporteur (Vencore Labs) | imported from 3GU |
S1‑182353 | FS_ID_UAS+FS_V2XIMP drafting agenda | Rapporteur / Session Chair | imported from 3GU |
S1‑182354 | FS_ID_UAS+FS_V2XIMP drafting report | Rapporteur / Session Chair | imported from 3GU |
S1‑182355 | TR22.825v1.0.0 to include agreements at this meeting | Rapporteur (Qualcomm) | imported from 3GU |
S1‑182356 | Cover page for presentation of TR22.825v1.0.0 | Rapporteur (Qualcomm) | imported from 3GU |
S1‑182357 | TS22.827v0.1.0 to include agreements at this meeting | Rapporteur (EBU) | imported from 3GU |
S1‑182358 | TS22.842v0.1.0 to include agreements at this meeting | Rapporteur (OPPO) | imported from 3GU |
S1‑182359 | MONASTERY2 – Status report | Nokia | imported from 3GU |
S1‑182360 | FS_FRMCS2 – Status report | Nokia | imported from 3GU |
S1‑182361 | enIMS – Status report | China Mobile | imported from 3GU |
S1‑182362 | SMARTER Ph2 – Status report | Vodafone | imported from 3GU |
S1‑182363 | QoS_MON – Status report | Huawei | imported from 3GU |
S1‑182364 | MuD – Status report | Ericsson | imported from 3GU |
S1‑182365 | MOBRT – Status report | OPPO | imported from 3GU |
S1‑182366 | 5GLAN – Status report | KPN | imported from 3GU |
S1‑182367 | cyberCAV – Status report | Siemens | imported from 3GU |
S1‑182368 | eLSTR – Status report | China Telecom | imported from 3GU |
S1‑182369 | 5GSAT – Status report | THALES | imported from 3GU |
S1‑182370 | MARCOM – Status report | SyncTechno | imported from 3GU |
S1‑182371 | FS_MARCOM – Status report | SyncTechno | imported from 3GU |
S1‑182372 | UIA – Status report | Deutsche Telekom | imported from 3GU |
S1‑182373 | FS_LUCIA – Status report | Deutsche Telekom | imported from 3GU |
S1‑182374 | 5G_HYPOS – Status report | ESA | imported from 3GU |
S1‑182375 | FS_5G_HYPOS – Status report | ESA | imported from 3GU |
S1‑182376 | FS_5GMSG – Status report | China Mobile | imported from 3GU |
S1‑182377 | FS_BMNS – Status report | Nokia | imported from 3GU |
S1‑182378 | FS_MPS2 – Status report | Vencore Labs | imported from 3GU |
S1‑182379 | FS_ID_UAS – Status report | Qualcomm | imported from 3GU |
S1‑182380 | FS_V2XIMP – Status report | LGE | imported from 3GU |
S1‑182381 | FS_AVPROD – Status report | EBU | imported from 3GU |
S1‑182382 | FS_NCIS – Status report | OPPO | imported from 3GU |
S1‑182383 | LS on Announcing the release of the “IoT Relation and Impact on 5G” | AIOTI WG03 | imported from 3GU |
S1‑182384 | Improvement of quality control | Chair | imported from 3GU |
S1‑182385 | Satellite links between radio access network and core network | Thales, TNO, SyncTechno Inc., Novamint, ESA, CTTC, VT iDirect, KT Corporation | imported from 3GU |
S1‑182386 | Not used | Chair | imported from 3GU |
S1‑182387 | Not used | Chair | imported from 3GU |
S1‑182388 | Not used | Chair | imported from 3GU |
S1‑182389 | Not used | Chair | imported from 3GU |
S1‑182390 | Not used | Chair | imported from 3GU |
S1‑182391 | Not used | Chair | imported from 3GU |
S1‑182392 | Not used | Chair | imported from 3GU |
S1‑182393 | Not used | Chair | imported from 3GU |
S1‑182394 | 5G LAN- new CR explanation | KPN | imported from 3GU |
S1‑182395 | 5GLAN Requirements | KPN, Nokia, Huawei, Interdigital | imported from 3GU |
S1‑182396 | Correction of Ethernet transport service requirements | ETRI | imported from 3GU |
S1‑182397 | Clock synchronisation communication service requirements | ETRI | imported from 3GU |
S1‑182398 | LS on Requirements to enable Predictive QoS for Automotive industry | 5GAA A-180265 | imported from 3GU |
S1‑182399 | Network service exposure requirements | Vodafone, Huawei, Nokia | imported from 3GU |
S1‑182400 | TR 21.915 v.0.2.0 on ^^Release description; Release 15 | MCC | imported from 3GU |
S1‑182401 | Very accurate positioning in support of precision agriculture | Novamint | imported from 3GU |
S1‑182402 | LS on Prioritised Use Cases and Requirements for consideration in Rel-16 NR-V2X | 5GAA1 T-180181 | imported from 3GU |
S1‑182403 | cyberCAV – 22.104 – summary of service performance requirements | Siemens AG | imported from 3GU |
S1‑182404 | Additional requirements in KPAS | SyncTechno Inc., KT, LG Uplus, Samsung Electronics | imported from 3GU |
S1‑182405 | Additional requirements in KPAS | SyncTechno Inc., KT, LG Uplus, Samsung Electronics | imported from 3GU |
S1‑182406 | cyberCAV – 22.104 – annexe – characteristic parameters and influence quantities | Siemens AG | imported from 3GU |
S1‑182407 | Summary for MONASTERY | Nokia (Rapporteur) | imported from 3GU |
S1‑182408 | Alignment of emergency call types defined by CT1 | BlackBerry, ... | imported from 3GU |
S1‑182409 | Emergency Call Type alignment and clarification | Deutsche Telekom AG | imported from 3GU |
S1‑182410 | LS on Interworking of DECT technology with 3GPP networks | DECT(18)000106 | imported from 3GU |
S1‑182411 | Reply LS to Ct1 (cc SA2) on Reply LS on Applicability of 3GPP PS Data off to Ethernet and Unstructured PDU Session Type | Qualcomm Incorporated | imported from 3GU |
S1‑182412 | Draft Reply LS to ESOA on 5G for Satellite Systems | Thales | imported from 3GU |
S1‑182413 | Study on MUltihop Relays | KPN | imported from 3GU |
S1‑182414 | LS on new access category | RAN2 R2-1813228 | imported from 3GU |
S1‑182415 | Same operator for all MUD identities | Ericsson, Orange, ETRI, Huawei, China Unicom | imported from 3GU |
S1‑182416 | Draft LS to ETSI AIOTI WG03 reply on IoT Relation and impact on 5G | FUJITSU Laboratories of Europe | imported from 3GU |
S1‑182417 | Clarification to Delay Tolerant | LG Electronics, Ericsson | imported from 3GU |
S1‑182418 | Clarification to Delay Tolerant | LG Electronics, Ericsson | imported from 3GU |
S1‑182419 | Draft LS on Publication of new paper on network slicing and future plans | Deutsche Telekom | imported from 3GU |
S1‑182420 | Reply to LS on MCVideo capability information sharing | The Police of the Netherlands | imported from 3GU |
S1‑182421 | Draft LS answer on Requirements to enable Predictive QoS for Automotive industry | Huawei | imported from 3GU |
S1‑182422 | New SID on Assets Tracking Use cases | NOVAMINT | imported from 3GU |
S1‑182423 | Draft Use case on Container Tracking | NOVAMINT | imported from 3GU |
S1‑182424 | New SID on Smart Community and City Services over 3GPP Systems | OMESH Technologies Co. Ltd. | imported from 3GU |
S1‑182425 | New SID on Assets Tracking Use cases | NOVAMINT | imported from 3GU |
S1‑182426 | Way forward for normative phase of FS_V2XIMP | LG Electronics France | imported from 3GU |
S1‑182427 | FS_V2XIMP Consolidation of Requirements Set #1 - DP | LG Electronics France | imported from 3GU |
S1‑182428 | Consolidated requirements for FS_V2XIMP | LG Electronics | imported from 3GU |
S1‑182429 | Study on MUltihop Relays | KPN | imported from 3GU |
S1‑182430 | Connectivity aspects of 5G satellite access | Thales, TNO, SyncTechno Inc., Novamint, ESA, CTTC, VT iDirect, KT Corporation | imported from 3GU |
S1‑182431 | Efficient user plane aspects of 5G satellite access | Thales, TNO, SyncTechno Inc., Novamint, ESA, CTTC, VT iDirect, KT Corporation | imported from 3GU |
S1‑182432 | Mobility management related requirements for 5G satellite access | Thales, TNO, SyncTechno Inc., Novamint, ESA, CTTC, VT iDirect, KT Corporation | imported from 3GU |
S1‑182433 | Regulatory and charging aspects related to 5G satellite access | Thales, TNO, SyncTechno Inc., Novamint, ESA, CTTC, VT iDirect, KT Corporation | imported from 3GU |
S1‑182434 | New SID proposal for Access Control for Secondary Access | LG Electronics France | imported from 3GU |
S1‑182435 | Access control for secondary access | LG Electronics France | imported from 3GU |
S1‑182436 | New SID Proposal: Study on 5G enhancement for UAVs with fixed routing | China Unicom | imported from 3GU |
S1‑182437 | Addition of new Access category for 'MO signalling on RRC level resulting from other than paging' | Ericsson | imported from 3GU |
S1‑182438 | Addition of new Access category for 'MO signalling on RRC level resulting from other than paging'- Mirror CR | Ericsson | imported from 3GU |
S1‑182439 | Additional requirements in KPAS | SyncTechno Inc., KT, LG Uplus, Samsung | imported from 3GU |
S1‑182440 | Additional requirements in KPAS | SyncTechno Inc., KT, LG Uplus, Samsung | imported from 3GU |
S1‑182441 | Discussion paper on type-a/type-b network definitions | Ericsson | imported from 3GU |
S1‑182442 | Non-public network requirements | Ericsson, Qualcomm, Vodafone | imported from 3GU |
S1‑182443 | cyberCAV - Deployment option of type-a networks | Siemens AG | imported from 3GU |
S1‑182444 | Network service exposure requirements | Vodafone, Huawei, Nokia | imported from 3GU |
S1‑182445 | Support for security requirements based on FS_CAV | Nokia, Nokia Shanghai Bell | imported from 3GU |
S1‑182446 | cyberCAV – 22.104 – clause 1 (introduction) | Siemens AG | imported from 3GU |
S1‑182447 | cyberCAV – TS 22.104 – clause 1 (scope) | Siemens AG | imported from 3GU |
S1‑182448 | Clock Synchronization Service Performance | HuaWei Technologies Co., Ltd | imported from 3GU |
S1‑182449 | CyberCAV- Positioning Service Performance Requirements | Fraunhofer IIS | imported from 3GU |
S1‑182450 | 5G LAN- new CR explanation | KPN | imported from 3GU |
S1‑182451 | 5GLAN discussion of editorials on security and charging requirements | Nokia, Nokia Shanghai Bell | imported from 3GU |
S1‑182452 | 5GLAN security requirements | Nokia, Nokia Shanghai Bell | imported from 3GU |
S1‑182453 | 5GLAN charging requirements | Nokia, Nokia Shanghai Bell | imported from 3GU |
S1‑182454 | FS_LUCIA: Consolidation of potential requirements | Deutsche Telekom AG | imported from 3GU |
S1‑182455 | Consolidation of potential requirements | Deutsche Telekom, Huawei, Interdigital, NEC, Telecom Italia | imported from 3GU |
S1‑182456 | UIA Service Requirements | Deutsche Telekom, NEC, Telecom Italia, Huawei | imported from 3GU |
S1‑182457 | FS_BMNS terminology alignment | Nokia, Nokia Shanghai Bell | imported from 3GU |
S1‑182458 | FS_BMNS editor’s note | Nokia, Nokia Shanghai Bell | imported from 3GU |
S1‑182459 | Clarification BMNS study – business models | KPN | imported from 3GU |
S1‑182460 | New text on Management role models | ETRI | imported from 3GU |
S1‑182461 | Private slice management in role model scenarios | ETRI | imported from 3GU |
S1‑182462 | Proposal on finalising cyberCAV terminology | Vodafone | imported from 3GU |
S1‑182463 | FS_BMNS: Figures to illustrate clause 5.5 | Sennheiser electronic GmbH & Co KG | imported from 3GU |
S1‑182464 | BMNS – Management of network selection information | Siemens AG | imported from 3GU |
S1‑182465 | FS_BMNS considerations | Nokia, Nokia Shanghai Bell, NTT DoCoMo | imported from 3GU |
S1‑182466 | FS_BMNS consolidated potential requirements | Nokia, Nokia Shanghai Bell, NTT DoCoMo | imported from 3GU |
S1‑182467 | 5GMSG: message size of remote control | China Unicom | imported from 3GU |
S1‑182468 | WID on Business Role Models for Network Slicing (BRMNS) | Nokia, Nokia Shanghai Bell | imported from 3GU |
S1‑182469 | Enhanced network slice requirements based on business role models | Nokia, Nokia Shanghai Bell | imported from 3GU |
S1‑182470 | FS_BMNS: Figure to illustrate clause 5.5 | Sennheiser Electronic GmbH | imported from 3GU |
S1‑182471 | Application originated messages for stationary IoT sensors | Sony Mobile Communications | imported from 3GU |
S1‑182472 | Application originated messages for IoT sensors | Sony Mobile Communications | imported from 3GU |
S1‑182473 | FS_5GMSG Consolidated potential requirements | China Mobile (Hangzhou) Inf. | imported from 3GU |
S1‑182474 | FS_5GMSG Conclusion and recommendations | China Mobile (Hangzhou) Inf. | imported from 3GU |
S1‑182475 | New WID on the 5GMSG Service requirements (5GMSG) | China Mobile (Hangzhou) Inf. | imported from 3GU |
S1‑182476 | Ethernet support in TS 22.261 | Qualcomm Incorporated | imported from 3GU |
S1‑182477 | Ethernet support in SMARTER vs CyberCAV | Qualcomm Incorporated | imported from 3GU |
S1‑182478 | CyberCAV network name requirement | Qualcomm Incorporated | imported from 3GU |
S1‑182479 | cyberCAV – 22.104 – annexe – characteristic parameters and influence quantities | Siemens AG | imported from 3GU |
S1‑182480 | Addition of inter-site Ethernet transport service | NTT DOCOMO INC. | imported from 3GU |
S1‑182481 | FS_BMNS terminology alignment | Nokia, Nokia Shanghai Bell | imported from 3GU |
S1‑182482 | Support for use of licensed and unlicensed bands | Nokia, Nokia Shanghai Bell | imported from 3GU |
S1‑182483 | Addition of inter-site Ethernet transport service to TS 22.261 | NTT DOCOMO INC. | imported from 3GU |
S1‑182484 | FS_BMNS consolidated potential requirements | Nokia, Nokia Shanghai Bell, NTT DoCoMo | imported from 3GU |
S1‑182485 | Accurate Positioning for the Factories of the Future | Fraunhofer IIS | imported from 3GU |
S1‑182486 | Correction of positioning service performance requirements | Fraunhofer IIS, Huawei, Vodafone, Sony, Volkswagen AG, Siemens, Harting, Deutsche Telekom | imported from 3GU |
S1‑182487 | Add the post-conditions of Millisecond-Level Precise Load Control | China Telecom, Huawei | imported from 3GU |
S1‑182488 | TR 22.804 - attending orphaned annexes | Siemens AG | imported from 3GU |
S1‑182489 | Support for security requirements based on FS_CAV | Nokia, Nokia Shanghai Bell | imported from 3GU |
S1‑182490 | Not used | Reserved Ki-Dong | imported from 3GU |
S1‑182491 | Not used | Reserved Ki-Dong | imported from 3GU |
S1‑182492 | Not used | Reserved Ki-Dong | imported from 3GU |
S1‑182493 | Not used | Reserved Ki-Dong | imported from 3GU |
S1‑182494 | Not used | Reserved Ki-Dong | imported from 3GU |
S1‑182495 | Not used | Reserved Ki-Dong | imported from 3GU |
S1‑182496 | Not used | Reserved Ki-Dong | imported from 3GU |
S1‑182497 | Not used | Reserved Ki-Dong | imported from 3GU |
S1‑182498 | Not used | Reserved Ki-Dong | imported from 3GU |
S1‑182499 | Not used | Reserved Ki-Dong | imported from 3GU |
S1‑182500 | Not used | Reserved Ki-Dong | imported from 3GU |
S1‑182501 | QoS list to support V2X critical applications | Huawei | imported from 3GU |
S1‑182502 | FS_ID_UAS: overview | Qualcomm Incorporated | imported from 3GU |
S1‑182503 | Comment on the use case 5.1 for Initial authorisation to operate | Orange | imported from 3GU |
S1‑182504 | enhancement on initial UAV authorization operation | HuaWei Technologies Co., Ltd | imported from 3GU |
S1‑182505 | ID_UAS – enhancement on use case for initial authorization to operate | T-Mobile Austria GmbH | imported from 3GU |
S1‑182506 | FS_ID_UAS: Update Definition and Use case 5.1 | Intel | imported from 3GU |
S1‑182507 | Use case of UAV fly range restriction | Huawei, Orange, China Unicom | imported from 3GU |
S1‑182508 | FS_ID_UAS: potential requirements for live data acquisition by UTM | Qualcomm Incorporated | imported from 3GU |
S1‑182509 | off-network UAV identification | HuaWei Technologies Co., Ltd | imported from 3GU |
S1‑182510 | Way forward for normative phase of FS_V2XIMP | LG Electronics France | imported from 3GU |
S1‑182511 | Correction to use cases | LG Electronics | imported from 3GU |
S1‑182512 | Different QoS prediction for different V2X users | ZTE Corporation | imported from 3GU |
S1‑182513 | QoS aspect for extended sensor | ZTE Corporation | imported from 3GU |
S1‑182514 | MEC Support for V2X Use Cases | Tencent, China Telecom, China Mobile, OPPO, China Unicom, ZTE | imported from 3GU |
S1‑182515 | Not used | Reserved Greg | imported from 3GU |
S1‑182516 | MPS Voice during International Roaming | Vencore Labs, OEC, AT&T | imported from 3GU |
S1‑182517 | DTS Invoked during International Roaming | Vencore Labs, OEC. AT&T | imported from 3GU |
S1‑182518 | Data Transport Service (DTS) Invoked from a Public UE | Vencore Labs, OEC, AT&T | imported from 3GU |
S1‑182519 | MPS Capable Enterprise Network Activation of DTS for MPS Subscribed IoT Devices | Vencore Labs | imported from 3GU |
S1‑182520 | MPS for DTS QoS and Media Encryption Modifications | Vencore Labs, OEC, AT&T | imported from 3GU |
S1‑182521 | Add reqs for IMS to support IMS slicing | China Mobile, Huawei, Deutsche Telekom | imported from 3GU |
S1‑182522 | Interworking with ONVIF cameras | Huawei, China Mobile | imported from 3GU |
S1‑182523 | Addition of requirement for VR Telepresence | Huawei, China Mobile, KPN | imported from 3GU |
S1‑182524 | Draft TR 22.827 Section 4 Overview | EBU | imported from 3GU |
S1‑182525 | Draft TR 22.827 Section 1 Scope | EBU | imported from 3GU |
S1‑182526 | Audio Streaming in professional live performances | Sennheiser Electronic GmbH | imported from 3GU |
S1‑182527 | On-Site Live Audio Presentation | Sennheiser Electronic GmbH | imported from 3GU |
S1‑182528 | Discussion on Use Case for Interactive Service, Cloud Rendering for Games | Tencent, China Mobile, China Telecom, China Unicom | imported from 3GU |
S1‑182529 | TR 22.842 Skeleton for NCIS | OPPO | imported from 3GU |
S1‑182530 | Proposal for absolute high but relative low speed use case for NCIS | OPPO | imported from 3GU |
S1‑182531 | Proposal for interactive service use case for NCIS | OPPO | imported from 3GU |
S1‑182532 | Proposal for Users from multiple PLMN joining the same group | OPPO | imported from 3GU |
S1‑182533 | Not used | Reserved Greg | imported from 3GU |
S1‑182534 | Not used | Reserved Greg | imported from 3GU |
S1‑182535 | FS_ID_UAS: use case for local broadcast of UAS identity | Qualcomm Incorporated | imported from 3GU |
S1‑182536 | New use case for detection and management of a rogue UAS | Huawei, Orange, China Unicom | imported from 3GU |
S1‑182537 | Cloud-based NLOS UAV operation | LG Electronics France | imported from 3GU |
S1‑182538 | FS_ID_UAS: Use case of UAS Based Remote Inspection | Intel | imported from 3GU |
S1‑182539 | additional consideration for security | HuaWei Technologies Co., Ltd | imported from 3GU |
S1‑182540 | FS_ID_UAS: consolidated potential requirements | Qualcomm Incorporated | imported from 3GU |
S1‑182541 | FS_ID_UAS: conclusion and recommendation | Qualcomm Incorporated | imported from 3GU |
S1‑182542 | New WID on Remote Identification of Unmanned Aerial Systems | Qualcomm Incorporated | imported from 3GU |
S1‑182543 | Skeleton TS on Unmanned Aerial System (UAS) support in 3GPP | Rapporteur | imported from 3GU |
S1‑182544 | Consolidated requirements for FS_V2XIMP | LG Electronics | imported from 3GU |
S1‑182545 | Addition of requirements for Group Communication System Enabler | Huawei, China Mobile | imported from 3GU |
S1‑182546 | Support for services using Artificial Intelligent | Huawei, China Mobile | imported from 3GU |
S1‑182547 | Add reqs for IMS to support IMS slicing | China Mobile, Huawei, Deutsche Telekom | imported from 3GU |
S1‑182548 | MPS for DTS QoS and Media Encryption Modifications | Vencore Labs, OEC, AT&T | imported from 3GU |
S1‑182549 | Draft TR 22.827 Section 1 Scope | EBU, BMWi, Sennheiser Electronic GmbH | imported from 3GU |
S1‑182550 | Discussion on Use Case for Interactive Service, Cloud Rendering for Games | Tencent, China Mobile, China Telecom, China Unicom | imported from 3GU |
S1‑182551 | NCIS use case – VR Based Interactive Service | OPPO | imported from 3GU |
S1‑182552 | Not used | Reserved Greg | imported from 3GU |
S1‑182553 | Not used | Reserved Greg | imported from 3GU |
S1‑182554 | Not used | Reserved Greg | imported from 3GU |
S1‑182555 | Not used | Reserved Greg | imported from 3GU |
S1‑182556 | Not used | Reserved Greg | imported from 3GU |
S1‑182557 | Not used | Reserved Greg | imported from 3GU |
S1‑182558 | Not used | Reserved Greg | imported from 3GU |
S1‑182559 | Not used | Reserved Greg | imported from 3GU |
S1‑182560 | Not used | Reserved Greg | imported from 3GU |
S1‑182561 | Dynamic Group Participation | FirstNet, Nokia, Nokia Shanghai Bell, UIC, Kapsch CarrierCom | imported from 3GU |
S1‑182562 | Clarification of requirement R-6.4.9-001 | The Police of the Netherlands | imported from 3GU |
S1‑182563 | Draft LS reply SA1 to SA6 on last MCX User having registered a specific functional alias is leaving | Union Inter. Chemins de Fer | imported from 3GU |
S1‑182564 | Selection of Application Layer Priorities by the MCX Service user | UIC, Nokia, Nokia Shanghai Bell | imported from 3GU |
S1‑182565 | Enhancement for interworking of group communication between FRMCS and GSM-R | Kapsch CarrierCom, Nokia, Nokia Shanghai Bell | imported from 3GU |
S1‑182566 | IP connectivity for MCData users. | UIC | imported from 3GU |
S1‑182567 | Update for gap analysis in TR 22.889 | Kapsch CarrierCom, Nokia, Nokia Shanghai Bell | imported from 3GU |
S1‑182568 | Adding gap analysis information for 6.2 'Multi-train voice communication for Drivers and Ground FRMCS User(s) communication' | Nokia, Nokia Shanghai Bell | imported from 3GU |
S1‑182569 | Adding gap analysis information for 6.3 'On-train outgoing voice communication from the Driver towards the Controller(s) of the train' | Nokia, Nokia Shanghai Bell | imported from 3GU |
S1‑182570 | Gap analysis of [R-12.13-0003] LMR interworking | Hansung University, ETRI | imported from 3GU |
S1‑182571 | Gap analysis of [R-12.13-0001] LMR interworking | Hansung University, ETRI | imported from 3GU |
S1‑182572 | Adding GSM-R interworking requirmenst for Assured Voice Communication (AVC) | Union Inter. Chemins de Fer | imported from 3GU |
S1‑182573 | Chapter 12.10 - QoS in a railway environment | UIC | imported from 3GU |
S1‑182574 | Automatic Train Control data communication | UIC, Nokia, Ericsson, Kapsch Carrier Com, Huawei | imported from 3GU |
S1‑182575 | Voice communication transfer related use cases | UIC | imported from 3GU |
S1‑182576 | FRMCS Equipment capabilities for multiple FRMCS Users | UIC, Hansung University | imported from 3GU |
S1‑182577 | FRMCS System/User - Roaming capabilities | UIC | imported from 3GU |
S1‑182578 | IP connectivity for MCData users. | UIC | imported from 3GU |
S1‑182579 | Voice communication transfer related use cases | UIC | imported from 3GU |
S1‑182580 | Clarification of requirement R-6.4.9-001 | The Police of the Netherlands | imported from 3GU |
S1‑182581 | Selection of Application Layer Priorities by the MCX Service user | UIC, Nokia, Nokia Shanghai Bell | imported from 3GU |
S1‑182582 | Additional consideration (clause 6.3) to support the consolidated requirements | ESA | imported from 3GU |
S1‑182583 | Corrections to annex A | ESA | imported from 3GU |
S1‑182584 | Update to clause 6.2.4 Accuracy and availability | ESA | imported from 3GU |
S1‑182585 | KPIs for horizontal and vertical positioning service levels in clause 7.3.2 | ESA, LG Electronics Mobile Research | imported from 3GU |
S1‑182586 | Other KPIS for 5G positioning services | ESA | imported from 3GU |
S1‑182587 | Security requirements for 5G positioning services | ESA | imported from 3GU |
S1‑182588 | Update description (clause 7.3.1) of 5G positioning services | ESA, LG Electronics Mobile Research | imported from 3GU |
S1‑182589 | A NOTE for clarifying the general scope of Emergency Responder use case | LG Electronics Mobile Research | imported from 3GU |
S1‑182590 | Regulatory and charging aspects related to 5G satellite access | Thales, TNO, SyncTechno Inc., Novamint, ESA, CTTC, VT iDirect, KT Corporation | imported from 3GU |
S1‑182591 | Proposed priorities for 5G_HYPOS normative work in SA1#83 | ESA | imported from 3GU |
S1‑182592 | Explanation on CR KPI for Horizontal and Vertical positioning services | ESA | imported from 3GU |
S1‑182593 | KPIs for horizontal and vertical positioning service levels in clause 7.3.2 | ESA | imported from 3GU |
S1‑182594 | Other KPIS for 5G positioning services | ESA | imported from 3GU |
S1‑182595 | Security requirements for 5G positioning services | ESA | imported from 3GU |
S1‑182596 | Update description (clause 7.3.1) of 5G positioning services | ESA | imported from 3GU |
S1‑182597 | Additional consideration (clause 6.3) to support the consolidated requirements | ESA | imported from 3GU |
S1‑182598 | Additional consideration (clause 6.3) to support the consolidated requirements | ESA | imported from 3GU |
S1‑182599 | Update to clause 6.2.4 Accuracy and availability | ESA | imported from 3GU |
S1‑182600 | A NOTE for clarifying the general scope of Emergency Responder use case | LG Electronics Mobile Research | imported from 3GU |
S1‑182601 | Clarification on consolidated potential requirements appliable to V2X | LG Electronics Mobile Research | imported from 3GU |
S1‑182602 | Multiple access requirements related to 5G satellite access | Thales, TNO, SyncTechno Inc., Novamint, ESA, CTTC, VT iDirect, KT Corporation | imported from 3GU |
S1‑182603 | Connectivity aspects of 5G satellite access | Thales, TNO, SyncTechno Inc., Novamint, ESA, CTTC, VT iDirect, KT Corporation | imported from 3GU |
S1‑182604 | Efficient delivery of content using 5G satellite access network | Thales, TNO, SyncTechno Inc., Novamint, ESA, CTTC, VT iDirect, KT Corporation | imported from 3GU |
S1‑182605 | Efficient user plane aspects of 5G satellite access | Thales, TNO, SyncTechno Inc., Novamint, ESA, CTTC, VT iDirect, KT Corporation | imported from 3GU |
S1‑182606 | Mobility management related requirements for 5G satellite access | Thales, TNO, SyncTechno Inc., Novamint, ESA, CTTC, VT iDirect, KT Corporation | imported from 3GU |
S1‑182607 | QoS control aspects of 5G satellite access | Thales, TNO, SyncTechno Inc., Novamint, ESA, CTTC, VT iDirect, KT Corporation | imported from 3GU |
S1‑182608 | TS Skeleton for 22.119 v16.0.0 | SyncTechno Inc. (Rapporteur) | imported from 3GU |
S1‑182609 | Scope | SyncTechno Inc. (Rapporteur) | imported from 3GU |
S1‑182610 | Overview | SyncTechno Inc. (Rapporteur) | imported from 3GU |
S1‑182611 | Requirements of basic capabilities | SyncTechno Inc., Korean Register of shipping | imported from 3GU |
S1‑182612 | Requirements of warning notification and emergency request for maritime safety | SyncTechno Inc., Korean Register of shipping | imported from 3GU |
S1‑182613 | Application of MCPTT to maritime usage | SyncTechno Inc., Korean Register of shipping, VTT | imported from 3GU |
S1‑182614 | Application of MCX Services to maritime usage | SyncTechno Inc., Korean Register of shipping, VTT | imported from 3GU |
S1‑182615 | Application of MCData to maritime usage | SyncTechno Inc., Korean Register of shipping, VTT | imported from 3GU |
S1‑182616 | Support to accurate and reliable handling of containers | Orange | imported from 3GU |
S1‑182617 | Draft LS to IALA on maritime works in 3GPP | SyncTechno Inc. (Rapporteur) | imported from 3GU |
S1‑182618 | Addition of requirements on positioning for the indoor commmunication inside a vessel | SyncTechno Inc., Korean Register of shipping, VTT | imported from 3GU |
S1‑182619 | Broadcast and multicast via satellite access networks | Thales, TNO, SyncTechno Inc., Novamint, ESA, CTTC, VT iDirect, KT Corporation, one2many | imported from 3GU |
S1‑182620 | Corrections to annex A | ESA | imported from 3GU |
S1‑182621 | Clarify the method of configuring the UE to use Access Identity 1 | Vencore Labs, OEC, AT&T, T-Mobile USA, Verizon, Sprint, FirstNet | imported from 3GU |
S1‑182622 | Clarify the method of configuring the UE to use Access Identity 1 | Vencore Labs, OEC, AT&T, T-Mobile USA, Verizon, Sprint | imported from 3GU |
S1‑182623 | SAE International's Levels of Automation reference link | LG Electronics Mobile Research | imported from 3GU |
S1‑182624 | SAE International's Levels of Automation reference link | LG Electronics Mobile Research | imported from 3GU |
S1‑182625 | SAE International's Levels of Automation reference link | LG Electronics Mobile Research | imported from 3GU |
S1‑182626 | SAE International's Levels of Automation reference link | LG Electronics Mobile Research | imported from 3GU |
S1‑182627 | QoS list to support V2X critical applications | Huawei Technologies France | imported from 3GU |
S1‑182628 | Inclusion of the CIoT requirements | Vodafone | imported from 3GU |
S1‑182629 | Inclusion of the CIoT requirements | Vodafone | imported from 3GU |
S1‑182630 | Inclusion of the CIoT requirements | Vodafone | imported from 3GU |
S1‑182631 | Inclusion of the CIoT requirements | Vodafone | imported from 3GU |
S1‑182632 | Correction to EAB | Vencore Labs, OEC, AT&T | imported from 3GU |
S1‑182633 | Delaying periodic higher priority PLMN searches and reselection attempts when receiving eMBMS service in idle mode | Qualcomm Incorporated | imported from 3GU |
S1‑182634 | Audio Streaming in professional live performances | Sennheiser Electronic GmbH | imported from 3GU |
S1‑182635 | On-Site Live Audio Presentation | Sennheiser Electronic GmbH | imported from 3GU |
S1‑182636 | Definitions for TR 22.287 | Sennheiser Electronic GmbH | imported from 3GU |
S1‑182637 | Clarification on the PLMN selection mode for RLOS | Intel | imported from 3GU |
S1‑182638 | Inclusion of the 5G requirements -- Service continuity | Vodafone, Telecom Italia | imported from 3GU |
S1‑182639 | Inclusion of the 5G requirements – efficient use plane | Vodafone Group Plc | imported from 3GU |
S1‑182640 | Inclusion of the 5G requirements -- Efficient content delivery | Vodafone Group Plc | imported from 3GU |
S1‑182641 | Inclusion of the 5G requirements -- Context aware network | Vodafone, Telecom Italia | imported from 3GU |
S1‑182642 | Updates to QoS Monitoring Description | Huawei, Siemens, China Mobile, KDDI | imported from 3GU |
S1‑182643 | Addition of Informative Annex for QoS Monitoring | Siemens, Huawei | imported from 3GU |
S1‑182644 | Different QoS prediction for different V2X users | ZTE Corporation, China Unicom, China Mobile | imported from 3GU |
S1‑182645 | Adding a new requirement about default identity | ETRI | imported from 3GU |
S1‑182646 | New Feasibility Study on Communication Services for Critical Medical Applications (FS_CMED) | B-Com | imported from 3GU |
S1‑182647 | Addition of Informative Annex for QoS Monitoring | Siemens, Huawei | imported from 3GU |
S1‑182648 | Clarification for Inter-RAT Mobility requirement for realtime service | OPPO, China Mobile, China Telecom, Tencent, CATT | imported from 3GU |
S1‑182649 | Requirement for Operator controlled Caching service delivery | China Telecom,CATT ,ZTE, CATR | imported from 3GU |
S1‑182650 | Charging Requirement for Operator controlled Caching service delivery | CATT, China Telecom, ZTE,CATR | imported from 3GU |
S1‑182651 | Clarification of requirement R-6.4.9-001 | The Police of the Netherlands | imported from 3GU |
S1‑182652 | Local emergency numbers and emergency call types for use in the IM CN subsystem handling | BlackBerry, Intel Corporation, NTT DOCOMO | imported from 3GU |
S1‑182653 | PS Data Off handling of non-IP PDN types | Qualcomm Incorporated | imported from 3GU |
S1‑182654 | PS Data Off handling of non-IP PDN types | Qualcomm Incorporated | imported from 3GU |
S1‑182655 | PS Data Off handling of non-IP PDN types | Qualcomm Incorporated | imported from 3GU |
S1‑182656 | LS to ESOA on 5G for Satellite Systems | SA1 | imported from 3GU |
S1‑182657 | Update to MUD identities | Ericsson, Orange, ETRI, Huawei, China Unicom | imported from 3GU |
S1‑182658 | Reply LS to SA5 (cc CT1) on Multi-identity and multi-device requirements | Ericsson LM | imported from 3GU |
S1‑182659 | LS reply to AIOTI WG03 on IoT Relation and impact on 5G | SA1 | imported from 3GU |
S1‑182660 | TR 22.804 - editorial cleanup of 'private' | Siemens AG | imported from 3GU |
S1‑182661 | Clarification to Delay Tolerant | LG Electronics, Ericsson | imported from 3GU |
S1‑182662 | Clarification to Delay Tolerant | LG Electronics, Ericsson | imported from 3GU |
S1‑182663 | Draft LS to GSMA on Publication of new paper on network slicing and future plans | Deutsche Telekom | imported from 3GU |
S1‑182664 | TR 22.804 - service continuity for wind farms | Siemens AG | imported from 3GU |
S1‑182665 | LS to SA6 (cc CT1) on MCVideo capabilities | SA1 | imported from 3GU |
S1‑182666 | Draft LS answer to 5GAA Liaison, 5GAA WG2 Chair, 3GPP TSG SA WG2 on Requirements to enable Predictive QoS for Automotive industry | Huawei | imported from 3GU |
S1‑182667 | New SID on Assets Tracking Use cases | NOVAMINT, b<>com, Siemens, NEC, Phillips | imported from 3GU |
S1‑182668 | New Feasibility Study on Communication Services for Critical Medical Applications (FS_CMED) | B-Com | imported from 3GU |
S1‑182669 | New SID on Smart Community and City Services over 3GPP Systems | OMESH Technologies Co. Ltd. | imported from 3GU |
S1‑182670 | Study on enhanced Relays for Energy eFficiency and Extensive Coverage (FS_REFEC) | KPN | imported from 3GU |
S1‑182671 | Adding a new requirement about default identity | ETRI | imported from 3GU |
S1‑182672 | New Study on 5G enhancement for UAVs (FS_5GEAV) | China Unicom | imported from 3GU |
S1‑182673 | Clarify the method of configuring the UE to use Access Identity 1 and Access Identity 2 | Vencore Labs, OEC, AT&T, T-Mobile USA, Verizon, Sprint, FirstNet | imported from 3GU |
S1‑182674 | Clarify the method of configuring the UE to use Access Identity 1 and Access Identity 2 | Vencore Labs, OEC, AT&T, T-Mobile USA, Verizon, Sprint, FirstNet | imported from 3GU |
S1‑182675 | Non-public network requirements | Ericsson, Qualcomm, Vodafone | imported from 3GU |
S1‑182676 | Deployment options for non-public networks | Siemens AG, Intel, Sennheiser | imported from 3GU |
S1‑182677 | Network service exposure requirements | Vodafone, Huawei, Nokia | imported from 3GU |
S1‑182678 | Support for use of licensed and unlicensed bands | Nokia, Nokia Shanghai Bell | imported from 3GU |
S1‑182679 | Support for use of licensed and unlicensed bands | Nokia, Nokia Shanghai Bell | imported from 3GU |
S1‑182680 | Clarification on the PLMN selection mode for RLOS | Intel | imported from 3GU |
S1‑182681 | Support for security requirements based on FS_CAV | Nokia, Nokia Shanghai Bell | imported from 3GU |
S1‑182682 | Editorial cleanup of 'private' | Siemens AG | imported from 3GU |
S1‑182683 | Add the post-conditions of Millisecond-Level Precise Load Control | China Telecom, Huawei | imported from 3GU |
S1‑182684 | Clock Synchronization Service Performance | HuaWei Technologies Co., Ltd | imported from 3GU |
S1‑182685 | Ethernet support in TS 22.261 | Qualcomm Incorporated | imported from 3GU |
S1‑182686 | cyberCAV – 22.104 – annexe – characteristic parameters and influence quantities | Siemens AG | imported from 3GU |
S1‑182687 | Local emergency numbers and emergency call types for use in the IM CN subsystem handling | BlackBerry, Intel Corporation, NTT DOCOMO | imported from 3GU |
S1‑182688 | Inclusion of the 5G requirements -- Service continuity | Vodafone, Telecom Italia | imported from 3GU |
S1‑182689 | Inclusion of the 5G requirements -- Context aware network | Vodafone, Telecom Italia | imported from 3GU |
S1‑182690 | Updates to QoS Monitoring Description | Huawei, Siemens, China Mobile, KDDI | imported from 3GU |
S1‑182691 | Addition of Informative Annex for QoS Monitoring | Siemens, Huawei | imported from 3GU |
S1‑182692 | Different QoS estimation for different V2X applications | ZTE Corporation, China Unicom, China Mobile | imported from 3GU |
S1‑182693 | QoS aspect for extended sensor | ZTE Corporation | imported from 3GU |
S1‑182694 | FS_ID_UAS+FS_V2XIMP drafting report | Rapporteur / Session Chair | imported from 3GU |
S1‑182695 | QoS list to support V2X critical applications | Huawei | imported from 3GU |
S1‑182696 | Clarification for Inter-RAT Mobility requirement for realtime service | OPPO, China Mobile, China Telecom, Tencent, CATT | imported from 3GU |
S1‑182697 | Requirement for Operator controlled Caching service delivery | China Telecom,CATT ,ZTE, CATR | imported from 3GU |
S1‑182698 | New WID on the 5GMSG Service requirements (5GMSG) | China Mobile, China Unicom, ZTE, CATR | imported from 3GU |
S1‑182699 | WID on Business Role Models for Network Slicing (BRMNS) | Nokia, Nokia Shanghai Bell | imported from 3GU |
S1‑182700 | 5G LAN- new CR explanation | KPN, Huawei, Interdigital | imported from 3GU |
S1‑182701 | 5GLAN discussion of editorials on security and charging requirements | Nokia, Nokia Shanghai Bell | imported from 3GU |
S1‑182702 | 5GLAN charging requirements | Nokia, Nokia Shanghai Bell | imported from 3GU |
S1‑182703 | Consolidation of potential requirements | Deutsche Telekom, Huawei, Interdigital, NEC, Telecom Italia | imported from 3GU |
S1‑182704 | UIA Service Requirements | Deutsche Telekom, NEC, Telecom Italia, Huawei | imported from 3GU |
S1‑182705 | BRMNS WI status report | Rapporteur (Nokia) | imported from 3GU |
S1‑182706 | FS_5GMSG Consolidated potential requirements | China Mobile (Hangzhou) Inf. | imported from 3GU |
S1‑182707 | Clarification BMNS study – business models | KPN | imported from 3GU |
S1‑182708 | New text on Management role models | ETRI | imported from 3GU |
S1‑182709 | FS_BMNS: Figure to illustrate clause 5.5 | Sennheiser Electronic GmbH | imported from 3GU |
S1‑182710 | Private slice management in role model scenarios | ETRI | imported from 3GU |
S1‑182711 | BMNS – Management of network selection information | Siemens AG | imported from 3GU |
S1‑182712 | Draft LS reply to SA WG6 on last MCX User having registered a specific functional alias is leaving | Union Inter. Chemins de Fer | imported from 3GU |
S1‑182713 | FS_BMNS considerations | Nokia, Nokia Shanghai Bell, NTT DoCoMo | imported from 3GU |
S1‑182714 | FS_BMNS consolidated potential requirements | Nokia, Nokia Shanghai Bell, NTT DoCoMo | imported from 3GU |
S1‑182715 | LS reply to SA6 on last MCX User having registered a specific functional alias is leaving | SA1 | imported from 3GU |
S1‑182716 | Add reqs for IMS to support IMS partitioning | China Mobile, Huawei, Deutsche Telekom | imported from 3GU |
S1‑182717 | Addition of requirements for Group Communication System Enabler | Huawei, China Mobile | imported from 3GU |
S1‑182718 | Addition of requirement for VR Telepresence | Huawei, China Mobile, KPN | imported from 3GU |
S1‑182719 | Revised FS_AVPROD WID | Rapporteur | imported from 3GU |
S1‑182720 | Efficient delivery of content using 5G satellite access network | Thales, TNO, SyncTechno Inc., Novamint, ESA, CTTC, VT iDirect, KT Corporation | imported from 3GU |
S1‑182721 | Discussion on Use Case for Interactive Service, Cloud Rendering for Games | Tencent, China Mobile, China Telecom, China Unicom | imported from 3GU |
S1‑182722 | NCIS use case – VR Based Interactive Service | OPPO | imported from 3GU |
S1‑182723 | Proposal for Users from multiple PLMN joining the same group | OPPO | imported from 3GU |
S1‑182724 | Proposal for absolute high but relative low speed use case for NCIS | OPPO | imported from 3GU |
S1‑182725 | Connectivity aspects of 5G satellite access | Thales, TNO, SyncTechno Inc., Novamint, ESA, CTTC, VT iDirect, KT Corporation, KRRI | imported from 3GU |
S1‑182726 | Requirements of warning notification and emergency request for maritime safety | SyncTechno Inc., Korean Register of shipping, VTT | imported from 3GU |
S1‑182727 | [DRAFT] LS to IALA (cc SA) on the information of the 3GPP standardization applicable to maritime usage and the request of the additional maritime related information | SyncTechno Inc. (Rapporteur) | imported from 3GU |
S1‑182728 | FS_ID_UAS: potential requirements for live data acquisition by UTM | Qualcomm Incorporated | imported from 3GU |
S1‑182729 | off-network UAV identification | HuaWei Technologies Co., Ltd | imported from 3GU |
S1‑182730 | FS_ID_UAS: use case for local broadcast of UAS identity | Qualcomm Incorporated | imported from 3GU |
S1‑182731 | 5GLAN security requirements | Nokia, Nokia Shanghai Bell | imported from 3GU |
S1‑182732 | New use case for detection and management of a rogue UAS | Huawei, Orange, China Unicom | imported from 3GU |
S1‑182733 | Use case of UAV fly range restriction | Huawei, Orange, China Unicom | imported from 3GU |
S1‑182734 | Consolidated requirements for FS_V2XIMP | LG Electronics, Huawei | imported from 3GU |
S1‑182735 | Different QoS estimation for different V2X applications | ZTE Corporation, China Unicom, China Mobile | imported from 3GU |
S1‑182736 | QoS aspect for extended sensor | ZTE Corporation | imported from 3GU |
S1‑182737 | Requirement for Operator controlled Caching service delivery | China Telecom,CATT ,ZTE, CATR | imported from 3GU |
S1‑182738 | Terminology clarification | Tencent, China Telecom, China Mobile, OPPO, China Unicom, ZTE, Ericsson | imported from 3GU |
S1‑182739 | New Feasibility Study on Communication Services for Critical Medical Applications (FS_CMED) | B-Com | imported from 3GU |
S1‑182740 | New WID on Remote Identification of Unmanned Aerial Systems | Qualcomm Incorporated | imported from 3GU |
S1‑182741 | Reply LS to CT1 on validity of extended local emergency number list | SA1 | imported from 3GU |
S1‑182742 | PS Data Off handling of non-IP PDN types | Qualcomm Incorporated | imported from 3GU |
S1‑182743 | Reply LS to CT1 (cc SA2) on Applicability of 3GPP PS Data off to Ethernet and Unstructured PDU Session Type | SA1 | imported from 3GU |
S1‑182744 | LS to SA5 (cc CT1) on Multi-identity and multi-device requirements | SA1 | imported from 3GU |
S1‑182745 | New Feasibility Study on Communication Services for Critical Medical Applications (FS_CMED) | B-Com | imported from 3GU |
S1‑182746 | Report on Communication Services for Critical Medical Applications (FS_CMED) | B-Com | imported from 3GU |
S1‑182747 | New SID on Asset Tracking Use cases (FS_5G_ATRAC) | NOVAMINT, b<>com, Siemens, NEC, Phillips | imported from 3GU |
S1‑182748 | Study on enhanced Relays for Energy eFficiency and Extensive Coverage (FS_REFEC) | KPN | imported from 3GU |
S1‑182749 | New Study on Enhancement for UAVs (FS_EAV) | China Unicom | imported from 3GU |
S1‑182750 | New WID on the 5GMSG Service requirements (5GMSG) | China Mobile, China Unicom, ZTE, CATR | imported from 3GU |
S1‑182751 | Report on Asset Tracking Use cases (FS_5G_ATRAC ) | NOVAMINT, b<>com, Siemens, NEC, Phillips | imported from 3GU |
S1‑182752 | Report on enhanced Relays for Energy eFficiency and Extensive Coverage (FS_REFEC) | KPN | imported from 3GU |
S1‑182753 | New Study on Enhancement for UAVs (FS_EAV) | China Unicom | imported from 3GU |
S1‑182754 | Report on Remote Identification of Unmanned Aerial Systems | Qualcomm Incorporated | imported from 3GU |
S1‑182755 | 5GLAN security requirements | Nokia, Nokia Shanghai Bell | imported from 3GU |
S1‑182756 | Non-public network requirements | Ericsson, Qualcomm, Vodafone | imported from 3GU |
S1‑182757 | Support for use of licensed and unlicensed bands | Nokia, Nokia Shanghai Bell | imported from 3GU |
S1‑182758 | Support for use of licensed and unlicensed bands | Nokia, Nokia Shanghai Bell | imported from 3GU |
S1‑182759 | Requirement for Operator controlled Caching service delivery | China Telecom,CATT ,ZTE, CATR | imported from 3GU |
S1‑182760 | LS to IALA (cc SA) on the information of the 3GPP standardization applicable to maritime usage and the request of the additional maritime related information | SA1 | imported from 3GU |
S1‑182761 | Clarification BMNS study – business models | KPN | imported from 3GU |
S1‑182762 | BMNS – Management of network selection information | Siemens AG | imported from 3GU |
S1‑182763 | Discussion on Use Case for Interactive Service, Cloud Rendering for Games | Tencent, China Mobile, China Telecom, China Unicom | imported from 3GU |
S1‑182764 | LS to SA2, 5GAA, 5GAA WG2 on Requirements to enable Predictive QoS for Automotive industry | SA1 | imported from 3GU |
S1‑182765 | Report on the 5GMSG Service requirements (5GMSG) | China Mobile | imported from 3GU |
S1‑182766 | Skeleton TS on Unmanned Aerial System (UAS) v.0.1.0 support in 3GPP | Rapporteur | imported from 3GU |
S1‑182767 | Addition of requirement for VR Telepresence | Huawei, China Mobile, KPN | imported from 3GU |
S1‑182768 | Clarification on the PLMN selection mode for RLOS | Intel | imported from 3GU |
S1‑182769 | Clarification for Inter-RAT Mobility requirement for realtime service | OPPO, China Mobile, China Telecom, Tencent, CATT | imported from 3GU |
S1‑182770 | Cover page for presentation of TR22.830v1.1.0 | Rapporteur (Nokia) | imported from 3GU |
S1‑182771 | Enhanced network slice requirements based on business role models | Nokia, Nokia Shanghai Bell | imported from 3GU |
page generated from database: 2024-10-07 07:52:06