3GPP TDocs (written contributions) at meeting
Meeting: S1-75 - 2016-08-22 to 2016-08-26, San Francisco
meeting id: S1-75 (click id for more info on this meeting)Click on the Tdoc to open its file.
TDoc | Title | Source | Remarks |
---|---|---|---|
S1‑162000 | Draft agenda for SA1#75 | Chair | imported from 3GU |
S1‑162001 | Draft agenda for SA1#75 | Chair | imported from 3GU |
S1‑162002 | Final Schedule and Agenda with document allocation for SA1#75 | Chair | imported from 3GU |
S1‑162003 | SA1-related topics at SA#72 | Chair | imported from 3GU |
S1‑162004 | Draft minutes of SA1#74 | MCC | imported from 3GU |
S1‑162005 | Minutes of SA1#74 | MCC | imported from 3GU |
S1‑162006 | Extract of the 3GPP Work Plan for SA1#75 | MCC | imported from 3GU |
S1‑162007 | Audio Cut-in Regroup requirement | HOME OFFICE | imported from 3GU |
S1‑162008 | Corrections to referenced sub-clauses in Annex B and Annex C | HOME OFFICE | imported from 3GU |
S1‑162009 | Change of MCPTT functionality between Rel-13 and Rel-14 due to removing distinction of with and without floor control for priority when interrupted by emergency calls | HOME OFFICE | imported from 3GU |
S1‑162010 | Video requirement clarifications | HOME OFFICE | imported from 3GU |
S1‑162011 | Add an Informative Annex table in MCCoRe TS 22.280 with a List of Variables used | U.S. Department of Commerce | imported from 3GU |
S1‑162012 | Add definitions for participant and participant type to MCCoRe TS 22.280 sub-clause 3.1. | U.S. Department of Commerce | imported from 3GU |
S1‑162013 | Remove definitions for participant and participant type in MCPTT TS 22.179 that are being added to MCCoRe TS 22.280. | U.S. Department of Commerce | imported from 3GU |
S1‑162014 | Add Service description in sub-clause 5.4.1.1 for MCVideo Device and Camera moving at high speed. | U.S. Department of Commerce | imported from 3GU |
S1‑162015 | Remove requirement in MCData TS 22.282 that has been added to MCCoRe TS 22.280. | U.S. Department of Commerce | imported from 3GU |
S1‑162016 | Editoral changes to several clauses and sub-clauses in MCData TS 22.282 for consistency and to improve understanding and readability. | U.S. Department of Commerce | imported from 3GU |
S1‑162017 | Editoral changes to several sub-clauses in MCVideo TS 22.281 for consistency and to improve understanding and readability. | U.S. Department of Commerce | imported from 3GU |
S1‑162018 | Add References and Abbreviations to MCVideo TS 22.281. | U.S. Department of Commerce | imported from 3GU |
S1‑162019 | Editorial changes to MCCoRe TS 22.280 Informative Annex D sub-clause D.1 | U.S. Department of Commerce | imported from 3GU |
S1‑162020 | In MCCoRe TS 22.280 provide changes to References 1, 2, and 3 in clause 2. | U.S. Department of Commerce | imported from 3GU |
S1‑162021 | Add remotely to the requirements in sub-clause 5.1.3.3.2 in MCVideo TS 22.281 to provide clarification | U.S. Department of Commerce | imported from 3GU |
S1‑162022 | Provide editorial changes to several sub-clauses in MCCoRe TS 22.280 for consistency and to improve understanding and readability. | U.S. Department of Commerce | imported from 3GU |
S1‑162023 | In MCData TS 22.282 Add requirements to empty sub-clause 6.3 MCData Services requirements specific to off-network use. | U.S. Department of Commerce | imported from 3GU |
S1‑162024 | In MCVideo TS 22.281 add a definition for robot and provide changes to sub-clause 5.1.5 Robots video remote control. | U.S. Department of Commerce | imported from 3GU |
S1‑162025 | In MCData TS 22.282 Provide changes to sub-clause 6.1.2 Robots, to improve understanding and readability. | U.S. Department of Commerce | imported from 3GU |
S1‑162026 | In MCData TS 22.282 Modify the title of clause 5 MCData generic capability requirements and add a sentence to the introduction sub-clause 5.1 | U.S. Department of Commerce | imported from 3GU |
S1‑162027 | In MCPTT TS 22.179 Provide editorial changes to sub-clause 6.6.2.2 and Informative Annex A1 for consistency and readability. | U.S. Department of Commerce | imported from 3GU |
S1‑162028 | Remove data streaming from MCData TS 22.282 sub-clause 6.1.1.1 Service description 1st paragraph, 3rd sentence | U.S. Department of Commerce | imported from 3GU |
S1‑162029 | In MCCoRe TS 22.280 provide editorial changes to the service description in sub-clause 6.19.1 Call rejection and queuing. | U.S. Department of Commerce | imported from 3GU |
S1‑162030 | In MCData TS 22.282 change group to users in sub-clause 5.2.2 requirement 3. | U.S. Department of Commerce | imported from 3GU |
S1‑162031 | Updated reference for Education use cases | VODAFONE Group Plc | imported from 3GU |
S1‑162032 | Addition of reference for Education use cases | VODAFONE Group Plc | imported from 3GU |
S1‑162033 | Change may to shall in MCData TS 22.282 sub-clause 6.2.3 requirement 10. | U.S. Department of Commerce | imported from 3GU |
S1‑162034 | In MCVideo TS 22.281 modify sub-clause 5.3.2.2 requirement 3 and remove variable N9. | U.S. Department of Commerce | imported from 3GU |
S1‑162035 | CR EMBB TR 22.863 - Extreme coverage in low density areas | ORANGE | imported from 3GU |
S1‑162036 | In MCCoRe TS 22.280 Add a requirement in sub-clause 8.4.2 Requirements for a single group with multiple MCX Services. | U.S. Department of Commerce | imported from 3GU |
S1‑162037 | In MCVideo TS 22.281 add a requirement in sub-clause 5.1.2.2.2 Requirements for video capabilities information management. | U.S. Department of Commerce | imported from 3GU |
S1‑162038 | In MCVideo TS 22.281 Modify title of sub-clause 5.4 to indicate that the performance and quality requirements are specific to on-network. | U.S. Department of Commerce | imported from 3GU |
S1‑162039 | Remove definition for Mission Critical Organization in MCPTT TS 22.179 that was added to MCCoRe TS 22.280 as a common definition. | U.S. Department of Commerce | imported from 3GU |
S1‑162040 | Traffic efficiency improvement by V2X communications | China Mobile Com. Corporation | imported from 3GU |
S1‑162041 | In MCCoRe TS 22.280 Add sub-clause 7.4 requirements to normative Annex C MCCoRe Requirements for MCData. | U.S. Department of Commerce | imported from 3GU |
S1‑162042 | Clarification on Access control for REAR | LG Electronics Inc | imported from 3GU |
S1‑162043 | Discussion on unified access control | LG Electronics Inc | imported from 3GU |
S1‑162044 | text proposal for overview for eV2X TR | Rapporteur (LG Electronics Inc) | imported from 3GU |
S1‑162045 | Text proposal for TBD values in eV2X | Rapporteur (LG Electronics Inc) | imported from 3GU |
S1‑162046 | Text proposal for consideration section for eV2X | Rapporteur (LG Electronics Inc) | imported from 3GU |
S1‑162047 | Text proposal for conclusion section for eV2X | Rapporteur (LG Electronics Inc) | imported from 3GU |
S1‑162048 | draft LS on Study on Enhancement of 3GPP support for V2X services | Rapporteur (LG Electronics Inc) | imported from 3GU |
S1‑162049 | Information delivery through 3GPP infrastructure | LG Electronics Inc | imported from 3GU |
S1‑162050 | Use case on 3GPP and Non3GPP eV2X interworking | LG Electronics Inc | imported from 3GU |
S1‑162051 | Use case on NR and LTE interworking | LG Electronics Inc | imported from 3GU |
S1‑162052 | Use case on Communication Status reporting in eV2 | LG Electronics Inc | imported from 3GU |
S1‑162053 | Text proposal for abbreviation and definition section | Rapporteur (LG Electronics Inc) | imported from 3GU |
S1‑162054 | Value update for the eV2X use case | LG Electronics Inc | imported from 3GU |
S1‑162055 | CR0002R3 to 22 185 correction on V2X privacy | LG Electronics Inc | imported from 3GU |
S1‑162056 | Draft reply LS to S3-160789 | LG Electronics Inc | imported from 3GU |
S1‑162057 | Correction to 22.278 R13 on Scope update | LG Electronics, KPN | imported from 3GU |
S1‑162058 | Correction to 22.278 R14 on Scope update | LG Electronics, KPN | imported from 3GU |
S1‑162059 | Intersection Safety Information Provisioning for Urban Driving | ETRI | imported from 3GU |
S1‑162060 | C-ITS and LTE Interworking for Seamless Service | ETRI | imported from 3GU |
S1‑162061 | Service Classification for FRMCS Requirements | ETRI | imported from 3GU |
S1‑162062 | Skeleton of Study on Future Railway Mobile Communication System | Nokia, Alcatel-Lucent Shanghai Bell, Ericsson, UIC, Kapsch CarrierCom | imported from 3GU |
S1‑162063 | Proposed scope section for FS_FRMCS TR | Nokia, Alcatel Lucent Shanghai Bell, Ericsson, UIC, Kapsch CarrierCom | imported from 3GU |
S1‑162064 | Proposed text for the Overview section of FS_FRMCS TR | Nokia, Alcatel Lucent Shanghai Bell, Ericsson, UIC, Kapsch CarrierCom | imported from 3GU |
S1‑162065 | FRMCS-user communication handling related use cases | Nokia, Alcatel-Lucent Shanghai Bell, Ericsson, UIC, Kapsch CarrierCom | imported from 3GU |
S1‑162066 | Initialisation and shut-down related use cases | Nokia, Alcatel-Lucent Shanghai Bell, Ericsson, UIC, Kapsch CarrierCom | imported from 3GU |
S1‑162067 | Secured voice communication | Nokia, Alcatel-Lucent Shanghai Bell, Ericsson, UIC, Kapsch CarrierCom | imported from 3GU |
S1‑162068 | Role management and presence related use cases | Nokia, Alcatel-Lucent Shanghai Bell, Ericsson, UIC, Kapsch CarrierCom | imported from 3GU |
S1‑162069 | Location services related use cases | Nokia, Alcatel-Lucent Shanghai Bell, Ericsson, UIC, Kapsch CarrierCom | imported from 3GU |
S1‑162070 | Examples of role management | Nokia, Alcatel-Lucent Shanghai Bell, Ericsson, UIC, Kapsch CarrierCom | imported from 3GU |
S1‑162071 | Consolidation of PRs - eV2X 5G Aspects | LG Electronics Inc. | imported from 3GU |
S1‑162072 | Update the requirements of “Information change within platoon” in eV2X TR | China Mobile Com. Corporation | imported from 3GU |
S1‑162073 | Adding new V2X Privacy requirement | China Mobile Com. Corporation | imported from 3GU |
S1‑162074 | Revision on V2X Privacy | China Mobile Com. Corporation | imported from 3GU |
S1‑162075 | V2X Privacy Discussion | China Mobile Com. Corporation | imported from 3GU |
S1‑162076 | Replace “Vehicle” by “UE” in 5.5.2 potential requirements | HUAWEI | imported from 3GU |
S1‑162077 | Use case to support Emergency Trajectory Alignment | HUAWEI | imported from 3GU |
S1‑162078 | Video data sharing for assisted and improved automated Driving | HUAWEI | imported from 3GU |
S1‑162079 | eV2X use case for Teleoperated Support | HUAWEI | imported from 3GU |
S1‑162080 | Cooperative Collision Avoidance (CoCA) of connected automated vehicles | HUAWEI | imported from 3GU |
S1‑162081 | Clarification split of eV2X requirements between LTE and NR | HUAWEI | imported from 3GU |
S1‑162082 | Sevice continuity for SMARTER_MIoT TR | Huawei Device Co., Ltd | imported from 3GU |
S1‑162083 | Add set I requirements for platooning use case | HUAWEI | imported from 3GU |
S1‑162084 | Enhancement of Public Warning System | SyncTechno Inc. | imported from 3GU |
S1‑162085 | [Draft] New WID for study on enhancements of Public Warning System | SyncTechno Inc. | imported from 3GU |
S1‑162086 | Maritime e-Navigation Services over 3GPP system | SyncTechno Inc. | imported from 3GU |
S1‑162087 | [Draft] New WID for Study on Maritime e-Navigation Services over 3GPP system | SyncTechno Inc. | imported from 3GU |
S1‑162088 | TR Skeleton for feasibility study on maritime e-Navigation services | SyncTechno Inc. | imported from 3GU |
S1‑162089 | SMARTER - Introduction | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
S1‑162090 | SMARTER - Scope | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
S1‑162091 | SMARTER - Definitions | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
S1‑162092 | SMARTER – UE update | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
S1‑162093 | SMARTER – Mobility support | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
S1‑162094 | SMARTER – Multi access technologies | Nokia Alcatel-Lucent Shanghai Bell | imported from 3GU |
S1‑162095 | SMARTER - Migration | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
S1‑162096 | SMARTER – descriptive text | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
S1‑162097 | SMARTER – Resource Efficiency | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
S1‑162098 | SMARTER - Security | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
S1‑162099 | SMARTER - Charging | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
S1‑162100 | New SID proposal for Provision of Local Operator Services | Nokia, Verizon | imported from 3GU |
S1‑162101 | FS_PLeaSe skeleton | Nokia | imported from 3GU |
S1‑162102 | Clarification split of eV2X requirements between LTE and NR | HUAWEI | imported from 3GU |
S1‑162103 | Work Plan for SMARTER WI | Rapporteur (VODAFONE Group Plc) | imported from 3GU |
S1‑162104 | Draft LS on 5G work alignment | VODAFONE Group Plc | imported from 3GU |
S1‑162105 | Some considerations on SMARTER WI | Rapporteur (VODAFONE Group Plc) | imported from 3GU |
S1‑162106 | User Controlled Spoofed Call Treatment | SPRINT Corporation | imported from 3GU |
S1‑162107 | Presentation of the results of spoofed call detection to the terminating user. | SPRINT Corporation | imported from 3GU |
S1‑162108 | Addition of spoofed callerid as a criteria for call diversion and call blocking features | SPRINT Corporation | imported from 3GU |
S1‑162109 | SMARTER - some network slicing requirements | Deutsche Telekom | imported from 3GU |
S1‑162110 | Dynamic Control of Quality of Service, Priority, and Pre-emption | U.S. Department of Commerce | imported from 3GU |
S1‑162111 | Normative requirements for eMBB | HUAWEI | imported from 3GU |
S1‑162112 | FS_eV2X RAT selection based on KPIs | Intel Corporation (UK) Ltd | imported from 3GU |
S1‑162113 | FS_eV2X Out of RAT Coverage | Intel Corporation (UK) Ltd | imported from 3GU |
S1‑162114 | FS_eV2X 802.11p-based RSU Measurements | Intel Corporation (UK) Ltd | imported from 3GU |
S1‑162115 | FS_eV2X RAT selection based on KPIs | Intel Corporation (UK) Ltd | imported from 3GU |
S1‑162116 | FS_eV2X Out of RAT Coverage | Intel Corporation (UK) Ltd | imported from 3GU |
S1‑162117 | SMARTER Mobility management and service continuity aspects | Intel Corporation (UK) Ltd | imported from 3GU |
S1‑162118 | SMARTER Subscription aspects | Intel Corporation (UK) Ltd | imported from 3GU |
S1‑162119 | Correction on mobility support requirements | Intel Corporation (UK) Ltd | imported from 3GU |
S1‑162120 | Correction of ambiguous term, "and/or" | U.S. Department of Commerce | imported from 3GU |
S1‑162121 | Missing requirements from Consolidation | Intel Corporation (UK) Ltd | imported from 3GU |
S1‑162122 | Insertion of new clause 5.5.2 with requirement [R-5.1.8-002] from clause 5.1.8 | U.S. Department of Commerce | imported from 3GU |
S1‑162123 | Corrections to Clause 4.2 | U.S. Department of Commerce | imported from 3GU |
S1‑162124 | Correction of inconsistency between header 6.7 and overview text 6.7.1 | U.S. Department of Commerce | imported from 3GU |
S1‑162125 | Correction to clause 5.1.1 requirement [R-5.1.1-005] | U.S. Department of Commerce | imported from 3GU |
S1‑162126 | Clarification of text in clause 5.4.1 | U.S. Department of Commerce | imported from 3GU |
S1‑162127 | Clarification of text in clause 5.6.1 | U.S. Department of Commerce | imported from 3GU |
S1‑162128 | Moving of informative text within requirements to NOTEs | U.S. Department of Commerce | imported from 3GU |
S1‑162129 | Correction [R-7.12.3-003] | U.S. Department of Commerce | imported from 3GU |
S1‑162130 | Correction of the entity that affiliates | U.S. Department of Commerce | imported from 3GU |
S1‑162131 | Singe requirement label [R-5.6.2.4.1-004] with two requirements | U.S. Department of Commerce | imported from 3GU |
S1‑162132 | Corrections to definitions | U.S. Department of Commerce | imported from 3GU |
S1‑162133 | Clarifications and corrections to audio-cut-in | U.S. Department of Commerce | imported from 3GU |
S1‑162134 | Corrections to 22.281 | U.S. Department of Commerce | imported from 3GU |
S1‑162135 | Corrections to 22.282 | U.S. Department of Commerce | imported from 3GU |
S1‑162136 | Draft Reply LS on alternative authentication methods | ORANGE | imported from 3GU |
S1‑162137 | Priority, QoS and Policy Control Requirements | HUAWEI TECHNOLOGIES Co. Ltd. | imported from 3GU |
S1‑162138 | Priority, QoS and Policy Control Description | HUAWEI TECHNOLOGIES Co. Ltd. | imported from 3GU |
S1‑162139 | Add Connectivity models and requirements (wearable) in SMARTER TS | Huawei Device Co., Ltd | imported from 3GU |
S1‑162140 | Use case for eV2X: information sharing for limited/full automated driving | NTT DOCOMO INC. | imported from 3GU |
S1‑162141 | Use case for eV2X: information sharing for limited/full automated platooning | NTT DOCOMO INC. | imported from 3GU |
S1‑162142 | Consideration for eV2X on multi PLMN environment | NTT DOCOMO INC. | imported from 3GU |
S1‑162143 | Consideration for eV2X on interoperability with other V2X schemes | NTT DOCOMO INC. | imported from 3GU |
S1‑162144 | Consideration for eV2X on security aspects | NTT DOCOMO INC. | imported from 3GU |
S1‑162145 | FRMCS use cases for interworking with GSMR | Huawei Tech.(UK) Co., Ltd | imported from 3GU |
S1‑162146 | improvement of 3GPP MCX Service to support FRMCS URS | Huawei Tech.(UK) Co., Ltd | imported from 3GU |
S1‑162147 | Text proposal on “Efficient Content delivery” | China Mobile | imported from 3GU |
S1‑162148 | Text proposal on “Efficient User Plane” | China Mobile | imported from 3GU |
S1‑162149 | New WID on Enhancements of LTE for affordable Video/HD | China Telecommunications | imported from 3GU |
S1‑162150 | Corrections for Use Case Regarding Collective Perception of Environment | KRRI | imported from 3GU |
S1‑162151 | Corrections for Use Case Regarding Collective Perception of Environment | KRRI | imported from 3GU |
S1‑162152 | Use Case for Changing Driving-Mode | KRRI | imported from 3GU |
S1‑162153 | Corrections for Use Case Regarding Vehicle Platooning | KRRI | imported from 3GU |
S1‑162154 | A vehicle information sharing requirement for eV2X interoperability with other V2X schemes | ITRI | imported from 3GU |
S1‑162155 | Interworking between 5G and non-3GPP access | China Telecommunications | imported from 3GU |
S1‑162156 | Consideration on loose interworking between 5G and UTRAN/GERAN access | China Telecommunications | imported from 3GU |
S1‑162157 | Proposed definition and description of, and requirements for network slicing to TS 22.xxx | Nokia, Alcatel-Lucent Shanghai Bell, Deutsche Telekom, Vodafone | imported from 3GU |
S1‑162158 | Proposed performance requirements for services requiring a low latency or a high reliability | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
S1‑162159 | Proposed performance requirements for scenarios requiring high bit rates or high traffic densities | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
S1‑162160 | Clean-up of TR 22.862 on CriC | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
S1‑162161 | Clean-up of TR 22.863 on eMBB | Nokia, Alcatel-Lucent Shanghai Bell | imported from 3GU |
S1‑162162 | Enhanced Calling Name Service | Ericsson Inc. | imported from 3GU |
S1‑162163 | Enhanced Calling Name | Ericsson Inc. | imported from 3GU |
S1‑162164 | Clarification of use case 5.6 in eV2X TR | Ericsson LM | imported from 3GU |
S1‑162165 | Correction of speed parameter values | ETRI | imported from 3GU |
S1‑162166 | Correction of speed parameter values | ETRI | imported from 3GU |
S1‑162167 | SMARTER efficient user plane | Huawei Tech.(UK) Co., Ltd | imported from 3GU |
S1‑162168 | SMARTER context aware network | Huawei Tech.(UK) Co., Ltd | imported from 3GU |
S1‑162169 | SMARTER self backhaul | Huawei Tech.(UK) Co., Ltd | imported from 3GU |
S1‑162170 | SMARTER Efficient content delivery | Huawei Tech.(UK) Co., Ltd | imported from 3GU |
S1‑162171 | SMARTER flexbile broadcast service | Huawei Tech.(UK) Co., Ltd | imported from 3GU |
S1‑162172 | SMARTER network capability exposure | Huawei Tech.(UK) Co., Ltd | imported from 3GU |
S1‑162173 | SMARTER mobility support | Huawei Tech.(UK) Co., Ltd | imported from 3GU |
S1‑162174 | The impact of a new flexible mobile RAT operating in frequency bands 6-100 GHz on 5G use cases: the vision of the mmMAGIC project | Intel Corporation (UK) Ltd | imported from 3GU |
S1‑162175 | network capability exposure for NEO TR | Huawei Tech.(UK) Co., Ltd | imported from 3GU |
S1‑162176 | Clarification on eV2X requirements for UE privacy | Qualcomm Incorporated | imported from 3GU |
S1‑162177 | Update to UE privacy requirements | Qualcomm Incorporated | imported from 3GU |
S1‑162178 | eV2X Use Case: Tethering via Vehicle | Qualcomm Incorporated | imported from 3GU |
S1‑162179 | eV2X Use Case: Automated Parking Reservation System | Qualcomm Incorporated | imported from 3GU |
S1‑162180 | eV2X Use Case: Dynamic Ride Sharing | Qualcomm Incorporated | imported from 3GU |
S1‑162181 | eV2X Use Case: Hazardous Road Condition Warning | Qualcomm Incorporated | imported from 3GU |
S1‑162182 | eV2X Platooning operations and requirements consolidation | Qualcomm Incorporated | imported from 3GU |
S1‑162183 | eV2X requirement allocation between LTE and SMARTER | Qualcomm Incorporated | imported from 3GU |
S1‑162184 | Update to eV2X use case “Automated Cooperative Driving for Short distance Grouping” | Qualcomm Incorporated | imported from 3GU |
S1‑162185 | Creating stub version of TS 22.234 | Qualcomm Incorporated | imported from 3GU |
S1‑162186 | MIoT relays | Qualcomm Incorporated | imported from 3GU |
S1‑162187 | NEO cleanup comments | Qualcomm Incorporated | imported from 3GU |
S1‑162188 | Service Slicing | Qualcomm Incorporated | imported from 3GU |
S1‑162189 | NEO: LTE service support in 5G | Qualcomm Incorporated | imported from 3GU |
S1‑162190 | Reply LS on alternative authentication methods and different types of credentials considerations for NextGen network | Qualcomm Incorporated | imported from 3GU |
S1‑162191 | Reply LS on normal emergency call for UE in eCall only mode | Qualcomm Incorporated | imported from 3GU |
S1‑162192 | Distribution of V2X messages to locally relevant V2X application server | KPN, LG | imported from 3GU |
S1‑162193 | Introducing service roaming requirements from GSMA liaison | KPN | imported from 3GU |
S1‑162194 | Low-delay speech, audio and video Requirements | HUAWEI TECHNOLOGIES Co. Ltd. | imported from 3GU |
S1‑162195 | Corrections to Group Regroup triggered by the need to support of Audio Cut-in capability | Motorola Solutions, Airwave | imported from 3GU |
S1‑162196 | Reply LS on Questions on alternative authentication methods and different types of credentials considerations for NextGen network | Nokia | imported from 3GU |
S1‑162197 | SMARTER Traffic Offloading | Intel Corporation (UK) Ltd | imported from 3GU |
S1‑162198 | Clarification of latency requirement for virtual meeting | Sony Europe Limited | imported from 3GU |
S1‑162199 | [DRAFT] Reply LS to SA4 on Codec for MCVideo | Motorola Solutions | imported from 3GU |
s1‑162200 | Correcting the Virtual meeting Requirement | Sony Mobile Communications AB | - |
S1‑162201 | Correction of speed paramenter values | ETRI, KTL | - |
S1‑162202 | Intersection Safety Information Provisioning for Urban Driving | ETRI | - |
S1‑162203 | LS on Comparison of TETRA, MCPTT, and North American LMR Terminology | ATIS LMR/LTE Interworking Ad hoc | - |
S1‑162204 | Reply LS Regarding LTE support for V2X services | SP-160150 | - |
S1‑162205 | Reply LS on "Next Generation" Security Requirements | S3-161182 | - |
S1‑162206 | LS on Questions on alternative authentication methods and different types of credentials considerations for NextGen network | S3-161159 | - |
S1‑162207 | LS to SA6 and SA1 on discreet listening and recording for MCPTT | S3-161230 | - |
S1‑162208 | LS on normal emergency call for UE in eCall only mode | C1-163875 | - |
S1‑162209 | LS response to SA4 on progress of FS_xMBMS study item | C3-162236 | - |
S1‑162210 | Response Liaison Statement on 5G Capabilities and Requirements | S3-161154 | - |
S1‑162211 | LS on "Next Generation" Security Requirements | S2-164280 | - |
S1‑162212 | LS on Key capabilities and issues to be addressed for 5G | NGMN Alliance | - |
S1‑162213 | LS on progress of FS_xMBMS study item | S4-160837 | - |
S1‑162214 | LS on the Codec for MCVideo | S4-160843 | - |
S1‑162215 | Liaison Statement on 5G Capabilities and Requirements | GSMA N2020_001 | - |
S1‑162216 | LS on I-WLAN handling and specification withdrawal | SP-160508 | - |
S1‑162217 | Vertical industry application perspectives and implications for 5G | NGMN Alliance | - |
S1‑162218 | Reply LS on "Next Generation" Security Requirements for RAN | S3-160833 | - |
S1‑162219 | LS on V2V Authorization | R3-161540 | - |
S1‑162220 | Reply LS on IMS Network Requirements regarding the provision of call progress indications | C1-163118 | - |
S1‑162221 | LS on eCall over IMS questions | C1-162773 | - |
S1‑162222 | Reply LS on EPC procedures for providing eNB with V2X authorization information | R2-164498 | - |
S1‑162223 | LS on Password based service activation for IMS Multimedia Telephony service (PWDIMS-CT) | S3-160776 | - |
S1‑162224 | Reply LS on V2X message characteristics | S3-160777 | - |
S1‑162225 | LS on Clarification to privacy requirements | S3-160789/S1-161574 | - |
S1‑162226 | Rapporteur (KPN) | MCImp Agenda | - |
S1‑162227 | Rapporteur (KPN) | MCImp Report | - |
S1‑162228 | Rapporteur (T-Mobile) | SMARTER Agenda | - |
S1‑162229 | Rapporteur (T-Mobile) | SMARTER Report | - |
S1‑162230 | Rapporteur | Draft TS 22.261 on SMARTER | - |
S1‑162231 | Rapporteur (LG) | V2X Agenda | - |
S1‑162232 | Rapporteur (LG) | V2X Report | - |
S1‑162233 | Rapporteur | TR 22.886 on eV2X | - |
S1‑162234 | Rapporteur (LGE) | Cover page for eV2X | - |
S1‑162235 | Rapporteur (Nokia) | TR 22.989 on FRMCS | - |
S1‑162236 | Rapporteur (Huawei) | REAR status report | - |
S1‑162237 | Rapporteur (China Mobile) | FS_SMARTER-NEO Status Report | - |
S1‑162238 | Rapporteur (Vodafone) | SMARTER Status Report | - |
S1‑162239 | Rapporteur (LGE) | FS_eV2X Status Report | - |
S1‑162240 | Rapporteur (Nokia) | FS_FRMCS Status Report | - |
S1‑162241 | Dynamic Control of Quality of Service, Priority, and Pre-emption | U.S. Department of Commerce | - |
S1‑162242 | Maritime e-Navigation Services over 3GPP system | SyncTechno Inc. | - |
S1‑162243 | [Draft] New WID for Study on Maritime e-Navigation Services over 3GPP system | SyncTechno Inc. | - |
S1‑162244 | Use case for eV2X: information sharing for limited/full automated driving | NTT DOCOMO INC. | - |
S1‑162245 | Use case for eV2X: information sharing for limited/full automated platooning | NTT DOCOMO INC. | - |
S1‑162246 | CR0002R3 to 22 185 correction on V2X privacy | LG Electronics Inc | - |
S1‑162247 | Clarification on Access control for REAR | LG Electronics | - |
S1‑162248 | Reply LS to SA3 on alternative authentication methods and different types of credentials considerations for NextGen network | Qualcomm Incorporated | - |
S1‑162249 | [DRAFT] LS on Response Liaison Statement to GSMA on 5G Capabilities and Requirements | SA1 | - |
S1‑162250 | New SID proposal for Provision of Local Operator Services (FS_PLeaSe) | Nokia, Verizon | - |
S1‑162251 | SMARTER - Security | Nokia, Alcatel-Lucent Shanghai Bell | - |
S1‑162252 | Reply LS to TTC (cc ARIB, SA) regarding LTE support for V2X services/SP-160150/f S1-161257 | SA1 | - |
S1‑162253 | The impact of a new flexible mobile RAT operating in frequency bands 6-100 GHz on 5G use cases: the vision of the mmMAGIC project | Intel Corporation (UK) Ltd | - |
S1‑162254 | SMARTER Traffic Offloading | Intel Corporation (UK) Ltd | - |
S1‑162255 | Missing requirements from NEO Consolidation | Intel Corporation | - |
S1‑162256 | Correction on mobility support requirements | Intel Corporation | - |
S1‑162257 | Creating stub version of TS 22.234 | Qualcomm Incorporated | - |
S1‑162258 | CR0002R3 to 22 185 correction on V2X privacy | LG Electronics Inc | - |
S1‑162259 | LS on MCPTT over LTE feature addition through modification of TS 22.280 requirements | SP-160469 | - |
S1‑162260 | Clarification of mobility management procedures for UEs in eCall mode | Deutsche Telekom | - |
S1‑162261 | Reply LS to CT1 (cc SA2) on normal emergency call for UE in eCall only mode | SA1/t-mobile | - |
S1‑162262 | [DRAFT] Reply LS to SA4 (cc SA6) on Codec for MCVideo | Motorola Solutions | - |
S1‑162263 | Add Connectivity models and requirements (wearable) in SMARTER TS | Huawei Device Co., Ltd | - |
S1‑162264 | Reply LS to SA3 on questions on discreet listening and recording for MCPTT | SA1 | - |
S1‑162265 | [DRAFT] LS to SA4 (cc SA2, SA3, SA6, CT3) on progress of FS_xMBMS study item | SA1/NEC | - |
S1‑162266 | In MCCoRe TS 22.280 Add sub-clause 7.4 requirements to normative Annex C MCCoRe Requirements for MCData. | US Department of Commerce | - |
S1‑162267 | [Draft] New WID for study on enhancements of Public Warning System | SyncTechno Inc., NEC, one2many, KRRI, MTCC, ETRI, Korea Testing Laboratory | - |
S1‑162268 | Study on Maritime Communication Services over 3GPP system (FS_MARCOM) | SyncTechno Inc. | - |
S1‑162269 | LS on Clarification to privacy requirements | S3-160789/S1-161574 | - |
S1‑162270 | New SID proposal for Provision of Local Operator Services (FS_PLeaSe) | Nokia, Verizon | - |
S1‑162271 | User Controlled Spoofed Call Treatment (SPECTRE) | SPRINT Corporation | - |
S1‑162272 | Presentation of the results of spoofed call detection to the terminating user. | Sprint, AT&T, Qualcomm, Nokia, Verizon, T-Mobile USA, Ericsson, LGE | - |
S1‑162273 | Addition of spoofed callerid as a criteria for call diversion and call blocking features | Sprint, AT&T, Qualcomm, Nokia, Verizon, T-Mobile USA, Ericsson, LGE | - |
S1‑162274 | Enhanced Calling Name Service (eCNAM) | Ericsson Inc. | - |
S1‑162275 | Clarification on Access control for REAR | LG Electronics | - |
S1‑162276 | SMARTER - Multi access technologies | Nokia Alcatel-Lucent Shanghai Bell | - |
S1‑162277 | SMARTER - Resource Efficiency | Nokia, Alcatel-Lucent Shanghai Bell | - |
S1‑162278 | New WID on Enhancements of LTE for affordable Video/HD (FS_eLAV) | China Telecommunications | - |
S1‑162279 | Removal of incorrect reference in scope | LG Electronics, KPN | - |
S1‑162280 | Clarification on Access control for REAR | LG Electronics | - |
S1‑162281 | Proposed scope section for FS_FRMCS TR | Nokia, Alcatel Lucent Shanghai Bell, Ericsson, UIC, Kapsch CarrierCom | - |
S1‑162282 | Proposed text for the Overview section of FS_FRMCS TR | Nokia, Alcatel Lucent Shanghai Bell, Ericsson, UIC, Kapsch CarrierCom, Huawei | - |
S1‑162283 | FRMCS-user communication handling related use cases | Nokia, Alcatel-Lucent Shanghai Bell, Ericsson, UIC, Kapsch CarrierCom, Huawei | - |
S1‑162284 | Initialisation and shut-down related use cases | Nokia, Alcatel-Lucent Shanghai Bell, Ericsson, UIC, Kapsch CarrierCom, Huawei | - |
S1‑162285 | Secured voice communication | Nokia, Alcatel-Lucent Shanghai Bell, Ericsson, UIC, Kapsch CarrierCom, Huawei | - |
S1‑162286 | Role management and presence related use cases | Nokia, Alcatel-Lucent Shanghai Bell, Ericsson, UIC, Kapsch CarrierCom, Huawei | - |
S1‑162287 | Location services related use cases | Nokia, Alcatel-Lucent Shanghai Bell, Ericsson, UIC, Kapsch CarrierCom, Huawei | - |
S1‑162288 | Examples of role management | Nokia, Alcatel-Lucent Shanghai Bell, Ericsson, UIC, Kapsch CarrierCom, Huawei | - |
S1‑162289 | FRMCS use cases for interworking with GSMR | Huawei Tech.(UK) Co., Ltd | - |
S1‑162290 | Sevice continuity for SMARTER_MIoT TR | Huawei, Huawei Device, Hisilicon, Vodafone, KPN, LGE | - |
S1‑162291 | Clean-up of TR 22.862 on CriC | Nokia, Alcatel-Lucent Shanghai Bell | - |
S1‑162292 | Clean-up of TR 22.863 on eMBB | Nokia, Alcatel-Lucent Shanghai Bell | - |
s1‑162293 | Correcting the Virtual meeting Requirement | Sony Mobile Communications AB | - |
S1‑162294 | FRMCS-user communication handling related use cases | Nokia, Alcatel-Lucent Shanghai Bell, Ericsson, UIC, Kapsch CarrierCom | - |
S1‑162295 | Secured voice communication | Nokia, Alcatel-Lucent Shanghai Bell, Ericsson, UIC, Kapsch CarrierCom | - |
S1‑162296 | Not used | MCC | imported from 3GU |
S1‑162297 | Not used | MCC | imported from 3GU |
S1‑162298 | Not used | MCC | imported from 3GU |
S1‑162299 | Not used | MCC | imported from 3GU |
S1‑162300 | Priority, QoS and Policy Control Requirements | HUAWEI TECHNOLOGIES Co. Ltd. | - |
S1‑162301 | Priority, QoS and Policy Control Description | HUAWEI TECHNOLOGIES Co. Ltd. | - |
S1‑162302 | Work Plan for SMARTER WI | Rapporteur (VODAFONE Group Plc) | - |
S1‑162303 | Draft LS to RAN, SA2 on 5G work alignment | VODAFONE Group Plc | - |
S1‑162304 | SMARTER - Introduction | Nokia, Alcatel-Lucent Shanghai Bell | - |
S1‑162305 | SMARTER - Scope | Nokia, Alcatel-Lucent Shanghai Bell | - |
S1‑162306 | NEO: LTE service support in 5G | Qualcomm Incorporated | - |
S1‑162307 | SMARTER - Definitions | Nokia, Alcatel-Lucent Shanghai Bell | - |
S1‑162308 | SMARTER - UE update | Nokia, Alcatel-Lucent Shanghai Bell | - |
S1‑162309 | SMARTER - descriptive text | Nokia, Alcatel-Lucent Shanghai Bell | - |
S1‑162310 | SMARTER - Migration | Nokia, Alcatel-Lucent Shanghai Bell | - |
S1‑162311 | SMARTER - Mobility support | Nokia, Alcatel-Lucent Shanghai Bell | - |
S1‑162312 | Normative requirements for eMBB | HUAWEI | - |
S1‑162313 | SMARTER - Multi access technologies | Nokia Alcatel-Lucent Shanghai Bell | - |
S1‑162314 | SMARTER - Resource Efficiency | Nokia, Alcatel-Lucent Shanghai Bell | - |
S1‑162315 | SMARTER Efficient content delivery | Huawei Tech.(UK) Co., Ltd | - |
S1‑162316 | SMARTER flexbile broadcast service | Huawei Tech.(UK) Co., Ltd | - |
S1‑162317 | Text proposal on "Efficient User Plane" | China Mobile | - |
S1‑162318 | SMARTER - Resource Efficiency | Nokia, Alcatel-Lucent Shanghai Bell | - |
S1‑162319 | Text proposal on "Efficient User Plane" | China Mobile | - |
S1‑162320 | SMARTER Efficient content delivery | Huawei Tech.(UK) Co., Ltd | - |
S1‑162321 | Add Connectivity models and requirements (wearable) in SMARTER TS | Huawei Device Co., Intel, KPN | - |
S1‑162322 | Priority, QoS and Policy Control Requirements | HUAWEI TECHNOLOGIES Co. Ltd. | - |
S1‑162323 | Priority, QoS and Policy Control Description | HUAWEI TECHNOLOGIES Co. Ltd. | - |
S1‑162324 | Dynamic Control of Quality of Service, Priority, and Pre-emption | U.S. Department of Commerce | - |
S1‑162325 | Proposed definition and description of, and requirements for network slicing to TS 22.xxx | Nokia, Alcatel-Lucent Shanghai Bell, Deutsche Telekom, Vodafone | - |
S1‑162326 | SMARTER - some network slicing requirements | Deutsche Telekom | - |
S1‑162327 | SMARTER network capability exposure | Huawei Tech.(UK) Co., Ltd | - |
S1‑162328 | SMARTER context aware network | Huawei Tech.(UK) Co., Ltd | - |
S1‑162329 | SMARTER Subscription aspects | Intel Corporation (UK) Ltd | - |
S1‑162330 | SMARTER self backhaul | Huawei Tech.(UK) Co., Ltd | - |
S1‑162331 | SMARTER flexbile broadcast service | Huawei Tech.(UK) Co., Ltd | - |
S1‑162332 | Proposed performance requirements for scenarios requiring high bit rates or high traffic densities | Nokia, Alcatel-Lucent Shanghai Bell | - |
S1‑162333 | Proposed performance requirements for scenarios requiring high bit rates or high traffic densities | Nokia, Alcatel-Lucent Shanghai Bell, Huawei | - |
S1‑162334 | SMARTER - Security | Nokia, Alcatel-Lucent Shanghai Bell | - |
S1‑162335 | SMARTER - Charging | Nokia, Alcatel-Lucent Shanghai Bell | - |
S1‑162336 | Correction on mobility support requirements | Intel Corporation | - |
S1‑162337 | Missing requirements from NEO Consolidation | Intel Corporation | - |
S1‑162338 | Introducing service roaming requirements from GSMA Liaison | KPN | - |
S1‑162339 | network capability exposure for NEO TR | Huawei Technologies | - |
S1‑162340 | NEO cleanup comments | Qualcomm Incorporated | - |
S1‑162341 | 3rd party service authorization | Qualcomm Incorporated | - |
S1‑162342 | SMARTER - Introduction | Nokia, Alcatel-Lucent Shanghai Bell | - |
S1‑162343 | SMARTER - Definitions | Nokia, Alcatel-Lucent Shanghai Bell | - |
S1‑162344 | SMARTER - UE update | Nokia, Alcatel-Lucent Shanghai Bell | - |
S1‑162345 | SMARTER - descriptive text | Nokia, Alcatel-Lucent Shanghai Bell | - |
S1‑162346 | SMARTER - Migration | Nokia, Alcatel-Lucent Shanghai Bell | - |
S1‑162347 | SMARTER - Resource Efficiency | Nokia, Alcatel-Lucent Shanghai Bell | - |
S1‑162348 | Text proposal on "Efficient User Plane" | China Mobile | - |
S1‑162349 | SMARTER Efficient content delivery | Huawei Tech.(UK) Co., Ltd | - |
S1‑162350 | Update the requirements of "Information change within platoon" in eV2X TR | China Mobile Com. Corporation | - |
S1‑162351 | Clarification split of eV2X requirements between LTE and NR | HUAWEI | - |
S1‑162352 | FS_eV2X Out of RAT Coverage | Intel Corporation (UK) Ltd | - |
S1‑162353 | Use Case for Changing Driving-Mode | KRRI | - |
S1‑162354 | FS_eV2X 802.11p-based RSU Measurements | Intel Corporation (UK) Ltd | - |
S1‑162355 | FS_eV2X RAT selection based on KPIs | Intel Corporation (UK) Ltd | - |
S1‑162356 | Use case on 3GPP and Non3GPP eV2X interworking | LG Electronics Inc | - |
S1‑162357 | Consideration for eV2X on interoperability with other V2X schemes | NTT DOCOMO INC. | - |
S1‑162358 | Use case on NR and LTE interworking | LG Electronics Inc | - |
S1‑162359 | Use case on Communication Status Reporting in eV2X TR | LG Electronics Inc | - |
S1‑162360 | Consideration for eV2X on multi PLMN environment | NTT DOCOMO INC. | - |
S1‑162361 | Consideration for eV2X on security aspects | NTT DOCOMO INC. | - |
S1‑162362 | Intersection Safety Information Provisioning for Urban Driving | ETRI | - |
S1‑162363 | Use case to support Emergency Trajectory Alignment | HUAWEI | - |
S1‑162364 | eV2X Use Case: Tethering via Vehicle | Qualcomm Incorporated | - |
S1‑162365 | Update the requirements of "Information change within platoon" in eV2X TR | China Mobile Com. Corporation | - |
S1‑162366 | Replace "Vehicle" by "UE" in 5.5.2 potential requirements | HUAWEI | - |
S1‑162367 | Corrections for Use Case Regarding Collective Perception of Environment | KRRI | - |
S1‑162368 | Corrections for Use Case Regarding Vehicle Platooning | KRRI | - |
S1‑162369 | Update to eV2X use case "Automated Cooperative Driving for Short distance Grouping" | Qualcomm Incorporated | - |
S1‑162370 | Video data sharing for assisted and improved automated Driving | HUAWEI | - |
S1‑162371 | eV2X use case for Teleoperated Support | HUAWEI | - |
S1‑162372 | eV2X Use Case: Dynamic Ride Sharing | Qualcomm Incorporated | - |
S1‑162373 | Text proposal for consideration section for eV2X | Rapporteur (LG Electronics Inc) | - |
S1‑162374 | Text proposal for abbreviation and definition section | Rapporteur (LG Electronics Inc) | - |
S1‑162375 | Text proposal for conclusion section for eV2X | Rapporteur (LG Electronics Inc) | - |
S1‑162376 | S1-162140 | HUAWEI | - |
S1‑162377 | Use case for eV2X: information sharing for limited/full automated driving | NTT DOCOMO INC. | - |
S1‑162378 | Use case for eV2X: information sharing for limited/full automated platooning | NTT DOCOMO INC. | - |
S1‑162379 | Update to eV2X use case "Automated Cooperative Driving for Short distance Grouping" | Qualcomm Incorporated, Huawei | - |
S1‑162380 | eV2X Use Case: Hazardous Road Condition Warning | Qualcomm Incorporated | - |
S1‑162381 | Correction of speed parameter values | ETRI, KTL | - |
S1‑162382 | CR0002R3 to 22 185 correction on V2X privacy | LG Electronics Inc | - |
S1‑162383 | Consolidation of PRs - eV2X 5G Aspects | LG Electronics Inc. | - |
S1‑162384 | Clarification split of eV2X requirements between LTE and NR | HUAWEI | - |
S1‑162385 | draft LS to ETSI ITS WG1 on Study on Enhancement of 3GPP support for V2X services | Rapporteur (LG Electronics Inc) | - |
S1‑162386 | Add set I requirements for platooning use case | HUAWEI | - |
S1‑162387 | Use Case for Changing Driving-Mode | KRRI | - |
S1‑162388 | Clarification of use case 5.6 in eV2X TR | Ericsson LM | - |
S1‑162389 | FS_eV2X RAT selection based on KPIs | Intel Corporation (UK) Ltd | - |
S1‑162390 | Use case for eV2X: information sharing for limited/full automated driving | NTT DOCOMO INC. | - |
S1‑162391 | Use case to support Emergency Trajectory Alignment | HUAWEI | - |
S1‑162392 | Video data sharing for assisted and improved automated Driving | HUAWEI | - |
S1‑162393 | eV2X use case for Teleoperated Support | HUAWEI | - |
S1‑162394 | FS_eV2X 802.11p-based RSU Measurements | Intel Corporation (UK) Ltd | imported from 3GU |
S1‑162395 | Use case on Communication Status Reporting in eV2X TR | LG Electronics Inc | - |
S1‑162396 | Intersection Safety Information Provisioning for Urban Driving | ETRI | - |
S1‑162397 | Distribution of V2X messages to locally relevant V2X application servers | KPN, LG | - |
S1‑162398 | Use case for eV2X: information sharing for limited/full automated platooning | NTT DOCOMO INC. | - |
S1‑162399 | Corrections for Use Case Regarding Collective Perception of Environment | KRRI | - |
S1‑162400 | Clarifications and corrections to audio cut-in | US Department of Commerce | - |
S1‑162401 | Corrections to Group Regroup triggered by the need to support of Audio Cut-in capability | Motorola Solutions, Airwave, Home Office | - |
S1‑162402 | Remove definitions for participant and participant type in MCPTT TS 22.179 that are being added to MCCoRe TS 22.280. | US Department of Commerce | - |
S1‑162403 | Add definitions for participant and participant type to MCCoRe TS 22.280 sub-clause 3.1. | US Department of Commerce | - |
S1‑162404 | In MCPTT TS 22.179 Provide editorial changes to sub-clause 6.6.2.2. | US Department of Commerce | - |
S1‑162405 | Remove definition for Mission Critical Organization in MCPTT TS 22.179 that was added to MCCoRe TS 22.280 as a common definition. | US Department of Commerce | - |
S1‑162406 | Corrections to referenced sub-clauses in Annex B and Annex C | Home Office | - |
S1‑162407 | Add an Informative Annex table in MCCoRe TS 22.280 with a List of Variables used | US Department of Commerce | - |
S1‑162408 | Provide editorial changes to several sub-clauses in MCCoRe TS 22.280 for consistency and to improve understanding and readability. | US Department of Commerce | - |
S1‑162409 | In MCCoRe TS 22.280 provide editorial changes to the service description in sub-clause 6.19.1 Call rejection and queuing. | US Department of Commerce | - |
S1‑162410 | Insertion of new clause 5.5.2 with requirement [R-5.1.8-002] from clause 5.1.8 | US Department of Commerce | - |
S1‑162411 | Corrections to Clause 4.2 | US Department of Commerce | - |
S1‑162412 | Clarification of text in clause 5.4.1 | US Department of Commerce | - |
S1‑162413 | Moving of informative text within requirements to NOTEs | US Department of Commerce | - |
S1‑162414 | Correction [R-7.12.3-003] | US Department of Commerce | - |
S1‑162415 | Correction of the entity that affiliates | US Department of Commerce | - |
S1‑162416 | Single requirement label [R-5.6.2.4.1-004] with two requirements | US Department of Commerce | - |
S1‑162417 | Video requirements clarifications | Home Office | - |
S1‑162418 | Add Service description in sub-clause 5.4.1.1 for MCVideo Device and Camera moving at high speed. | US Department of Commerce | - |
S1‑162419 | Add References to clause 2 and Abbreviations to sub-clause 3.2 in MCVideo TS 22.281. | US Department of Commerce | - |
S1‑162420 | In MCVideo TS 22.281 add a definition for robot in sub-clause 3.1 and provide changes to sub-clause 5.1.5 Robots video remote control to improve understanding and readability. | US Department of Commerce | - |
S1‑162421 | In MCVideo TS 22.281 add a requirement in sub-clause 5.1.2.2.2 Requirements for video capabilities information management. | US Department of Commerce | - |
S1‑162422 | In MCVideo TS 22.281 Modify title of sub-clause 5.4 to indicate that the performance and quality requirements are for on-network and off-network. | US Department of Commerce | - |
S1‑162423 | Corrections to 22.281 | US Department of Commerce | - |
S1‑162424 | Editoral changes to several clauses and sub-clauses in MCData TS 22.282 for consistency and to improve understanding and readability. | US Department of Commerce | - |
S1‑162425 | In MCData TS 22.282 Add requirements to empty sub-clause 6.3 MCData Services requirements specific to off-network use. | US Department of Commerce | - |
S1‑162426 | In MCData TS 22.282 Provide changes to sub-clause 6.1.2 Robots, to improve understanding and readability. | US Department of Commerce | - |
S1‑162427 | Remove data streaming from MCData TS 22.282 sub-clause 6.1.1.1 Service description 1st paragraph, 3rd sentence. | US Department of Commerce | - |
S1‑162428 | Change may to shall in MCData TS 22.282 sub-clause 6.2.3 requirement 10. | US Department of Commerce | - |
S1‑162429 | Corrections to 22.282 | US Department of Commerce | - |
S1‑162430 | Video requirements clarifications | Home Office | - |
S1‑162431 | Not used | MCC | imported from 3GU |
S1‑162432 | Not used | MCC | imported from 3GU |
S1‑162433 | Not used | MCC | imported from 3GU |
S1‑162434 | Not used | MCC | imported from 3GU |
S1‑162435 | Not used | MCC | imported from 3GU |
S1‑162436 | Not used | MCC | imported from 3GU |
S1‑162437 | Not used | MCC | imported from 3GU |
S1‑162438 | Not used | MCC | imported from 3GU |
S1‑162439 | Not used | MCC | imported from 3GU |
S1‑162440 | Not used | MCC | imported from 3GU |
S1‑162441 | Not used | MCC | imported from 3GU |
S1‑162442 | Not used | MCC | imported from 3GU |
S1‑162443 | Not used | MCC | imported from 3GU |
S1‑162444 | Not used | MCC | imported from 3GU |
S1‑162445 | Not used | MCC | imported from 3GU |
S1‑162446 | Not used | MCC | imported from 3GU |
S1‑162447 | Not used | MCC | imported from 3GU |
S1‑162448 | Not used | MCC | imported from 3GU |
S1‑162449 | Not used | MCC | imported from 3GU |
S1‑162450 | Dynamic Control of Quality of Service, Priority, and Pre-emption | U.S. Department of Commerce | - |
S1‑162451 | Proposed definition and description of, and requirements for network slicing to TS 22.xxx | Nokia, Alcatel-Lucent Shanghai Bell, Deutsche Telekom, Vodafone | - |
S1‑162452 | Consideration for eV2X on security aspects | NTT DOCOMO INC. | - |
S1‑162453 | eV2X Use Case: Hazardous Road Condition Warning | Qualcomm Incorporated | - |
S1‑162454 | eV2X Use Case: Dynamic Ride Sharing | Qualcomm Incorporated | - |
S1‑162455 | Use case to support Emergency Trajectory Alignment | HUAWEI | - |
S1‑162456 | Not used | MCC | imported from 3GU |
S1‑162457 | Not used | MCC | imported from 3GU |
S1‑162458 | Not used | MCC | imported from 3GU |
S1‑162459 | Not used | MCC | imported from 3GU |
S1‑162460 | Not used | MCC | imported from 3GU |
S1‑162461 | Not used | MCC | imported from 3GU |
S1‑162462 | Not used | MCC | imported from 3GU |
S1‑162463 | Not used | MCC | imported from 3GU |
S1‑162464 | Not used | MCC | imported from 3GU |
S1‑162465 | Not used | MCC | imported from 3GU |
S1‑162466 | Not used | MCC | imported from 3GU |
S1‑162467 | Not used | MCC | imported from 3GU |
S1‑162468 | Not used | MCC | imported from 3GU |
S1‑162469 | Not used | MCC | imported from 3GU |
S1‑162470 | Extreme coverage in low population density areas requirements | Orange, MoI France | - |
S1‑162471 | SMARTER - Mobility support | Nokia, Alcatel-Lucent Shanghai Bell | - |
S1‑162472 | FRMCS use cases for interworking with GSMR | Huawei Tech.(UK) Co., Ltd | - |
S1‑162473 | Extreme coverage in low population density areas requirements | Orange, MoI France, Gemalto | - |
S1‑162474 | eV2X use case for Teleoperated Support | HUAWEI | - |
S1‑162475 | Missing requirements from NEO Consolidation | Intel Corporation | - |
S1‑162476 | Introducing service roaming requirements from GSMA Liaison | KPN | - |
S1‑162477 | network capability exposure for NEO TR | Huawei Technologies | - |
S1‑162478 | 3rd party service authorization | Qualcomm Incorporated | - |
S1‑162479 | Draft LS to RAN, SA2 (cc SA, SA3) on 5G work alignment | VODAFONE Group Plc | - |
S1‑162480 | SMARTER - Definitions | Nokia, Alcatel-Lucent Shanghai Bell | - |
S1‑162481 | SMARTER - Migration | Nokia, Alcatel-Lucent Shanghai Bell | - |
S1‑162482 | SMARTER network capability exposure | Huawei Technologies,China Mobile, China Telecom,Intel | - |
S1‑162483 | SMARTER context aware network | Huawei Technologies,NEC,China Telecom | - |
S1‑162484 | SMARTER self backhaul | Huawei Tech.(UK) Co., Ltd | - |
S1‑162485 | SMARTER flexbile broadcast service | Huawei Tech.(UK) Co., Ltd | - |
S1‑162486 | Text proposal on "Efficient User Plane" | China Mobile | - |
S1‑162487 | CR0002R3 to 22 185 correction on V2X privacy | LG Electronics Inc | - |
S1‑162488 | Proposed definition and description of, and requirements for network slicing to TS 22.xxx | Nokia, Alcatel-Lucent Shanghai Bell, Deutsche Telekom, Vodafone | - |
S1‑162489 | SMARTER - some network slicing requirements | Deutsche Telekom, Telecom Italia, NEC, Huawei | - |
S1‑162490 | SMARTER network capability exposure | Huawei Technologies,China Mobile, China Telecom,Intel,NEC,China Unicom | - |
S1‑162491 | FS_eV2X Out of RAT Coverage | Intel Corporation (UK) Ltd | - |
S1‑162492 | SMARTER context aware network | Huawei Technologies,NEC,China Telecom | - |
S1‑162493 | SMARTER Subscription aspects | Intel Corporation (UK) Ltd | - |
S1‑162494 | Add Service description in sub-clause 5.4.1.1 for MCVideo Device and Camera moving at high speed. | US Department of Commerce | - |
S1‑162495 | In MCVideo TS 22.281 Modify title of sub-clause 5.4 to indicate that the performance and quality requirements are for on-network and off-network. | US Department of Commerce | - |
S1‑162496 | Remove data streaming from MCData TS 22.282 sub-clause 6.1.1.1 Service description 1st paragraph, 3rd sentence. | US Department of Commerce | - |
S1‑162497 | In MCCoRe TS 22.280 provide editorial changes to the service description in sub-clause 6.19.1 Call rejection and queuing. | US Department of Commerce | - |
S1‑162498 | In MCVideo TS 22.281 add a definition for robot in sub-clause 3.1 and provide changes to sub-clause 5.1.5 Robots video remote control to improve understanding and readability. | US Department of Commerce | - |
S1‑162499 | Corrections to 22.281 | US Department of Commerce | - |
S1‑162500 | In MCData TS 22.282 Add requirements to empty sub-clause 6.3 MCData Services requirements specific to off-network use. | US Department of Commerce | - |
S1‑162501 | Annex A Examples of role management | Nokia, Alcatel-Lucent Shanghai Bell, Ericsson, UIC, Kapsch CarrierCom, Hansung University, ETRI, Huawei | - |
S1‑162502 | Consolidation of PRs - eV2X 5G Aspects | LG Electronics Inc. | - |
S1‑162503 | Correction of speed parameter values | ETRI, KTL | - |
S1‑162504 | Distribution of V2X messages to locally relevant V2X application servers | KPN, LG | - |
S1‑162505 | SMARTER - Charging | Nokia, Alcatel-Lucent Shanghai Bell | - |
S1‑162506 | FS_eV2X RAT selection based on KPIs | Intel Corporation (UK) Ltd | - |
S1‑162507 | Correction on V2X privacy | LG Electronics Inc | - |
S1‑162508 | FS_eV2X Out of RAT Coverage | Intel Corporation (UK) Ltd | - |
S1‑162509 | Intersection Safety Information Provisioning for Urban Driving | ETRI | - |
S1‑162510 | Use case to support Emergency Trajectory Alignment | HUAWEI | - |
S1‑162511 | Video data sharing for assisted and improved automated Driving | HUAWEI | - |
S1‑162512 | Use Case for Changing Driving-Mode | KRRI | - |
S1‑162513 | eV2X Use Case: Tethering via Vehicle | Qualcomm Incorporated | - |
S1‑162514 | Add set I requirements for platooning use case | HUAWEI | - |
S1‑162515 | Missing requirements from NEO Consolidation | Intel Corporation | - |
S1‑162516 | SMARTER - Security | Nokia, Alcatel-Lucent Shanghai Bell | - |
S1‑162517 | Proposed performance requirements for scenarios requiring high bit rates or high traffic densities | Nokia, Alcatel-Lucent Shanghai Bell | - |
S1‑162518 | New SID proposal for Provision of Local Operator Services (FS_PLeaSe) | Nokia, Verizon | - |
S1‑162519 | WID on Enhanced Calling Name Service (eCNAM) | Ericsson Inc. | - |
S1‑162520 | SMARTER self backhaul | Huawei Tech.(UK) Co., Ltd | - |
S1‑162521 | [Draft] New WID for study on enhancements of Public Warning System | SyncTechno Inc., NEC, one2many, KRRI, MTCC, ETRI, Korea Testing Laboratory | - |
S1‑162522 | Study on Maritime Communication Services over 3GPP system (FS_MARCOM) | SyncTechno Inc. | - |
S1‑162523 | TR Skeleton for feasibility study on maritime e-Navigation services | SyncTechno Inc. | - |
S1‑162524 | WID on Enhanced Calling Name Service (eCNAM) | Ericsson Inc. | - |
S1‑162525 | New WID on Feasible Study on Enhancement of LTE for Efficient delivery Video/High Definition | China Telecommunications | - |
S1‑162526 | Reply LS to SA3 on alternative authentication methods and different types of credentials considerations for NextGen network | Qualcomm Incorporated | - |
S1‑162527 | LS on Response Liaison Statement to GSMA on 5G Capabilities and Requirements | SA1 | - |
S1‑162528 | [DRAFT] Reply LS to SA3 (cc SA2) on Clarification to privacy requirements | LG Electronics Inc | - |
S1‑162529 | Reply LS to TTC (cc ARIB, SA) regarding LTE support for V2X services/SP-160150/f S1-161257 | SA1 | - |
S1‑162530 | Consolidation of PRs - eV2X 5G Aspects | LG Electronics Inc. | - |
S1‑162531 | Reply LS to SA3 (cc SA2) on Clarification to privacy requirements | SA1/LG Electronics Inc | - |
S1‑162532 | Clarification of mobility management procedures for UEs in eCall mode | Deutsche Telekom | - |
S1‑162533 | Reply LS to CT1 (cc SA2) on normal emergency call for UE in eCall only mode | SA1/t-mobile | - |
S1‑162534 | Reply LS to SA4 (cc SA6) on Codec for MCVideo | SA1/Motorola Solutions | - |
S1‑162535 | LS to SA4 (cc SA2, SA3, SA6, CT3) on progress of FS_xMBMS study item | SA1/NEC | - |
S1‑162536 | Creating stub version of TS 22.234 | Qualcomm Incorporated | - |
S1‑162537 | Intersection Safety Information Provisioning for Urban Driving | ETRI | - |
S1‑162538 | Annex A Examples of role management | Nokia, Alcatel-Lucent Shanghai Bell, Ericsson, UIC, Kapsch CarrierCom, Hansung University, ETRI, Huawei | - |
S1‑162539 | FS_eV2X Out of RAT Coverage | Intel Corporation (UK) Ltd | - |
S1‑162540 | Intersection Safety Information Provisioning for Urban Driving | ETRI | - |
S1‑162541 | Use case to support Emergency Trajectory Alignment | HUAWEI | - |
S1‑162542 | draft LS to ETSI ITS WG1 on Study on Enhancement of 3GPP support for V2X services | Rapporteur (LG Electronics Inc) | - |
S1‑162543 | LS to RAN, SA2 (cc SA, SA3) on 5G work alignment | SA1/VODAFONE Group Plc | - |
S1‑162544 | LS to RAN, SA2 (cc SA, SA3) on 5G work alignment | SA1/VODAFONE Group Plc | - |
S1‑162545 | 3rd party service authorization | Qualcomm Incorporated | - |
S1‑162546 | Add Connectivity models and requirements (wearable) in SMARTER TS | Huawei Device Co., Intel, KPN | - |
S1‑162547 | Proposed definition and description of, and requirements for network slicing to TS 22.xxx | Nokia, Alcatel-Lucent Shanghai Bell, Deutsche Telekom, Vodafone | - |
S1‑162548 | SMARTER - some network slicing requirements | Deutsche Telekom, Telecom Italia, NEC, Huawei | - |
S1‑162549 | SMARTER network capability exposure | Huawei Technologies,China Mobile, China Telecom,Intel,NEC,China Unicom | - |
S1‑162550 | SMARTER Subscription aspects | Intel Corporation (UK) Ltd | - |
S1‑162551 | SMARTER - Security | Nokia, Alcatel-Lucent Shanghai Bell | - |
S1‑162552 | Intersection Safety Information Provisioning for Urban Driving | ETRI | imported from 3GU |
S1‑162553 | draft LS to ETSI ITS WG1 on Study on Enhancement of 3GPP support for V2X services | Rapporteur (LG Electronics Inc) | - |
S1‑162554 | LS to ETSI ITS WG1 on Study on Enhancement of 3GPP support for V2X services | Rapporteur (LG Electronics Inc) | - |
S1‑162555 | Reply LS to SA3 on alternative authentication methods and different types of credentials considerations for NextGen network | SA1/Qualcomm Incorporated | - |
S1‑162556 | Study on Maritime Communication Services over 3GPP system (FS_MARCOM) | SyncTechno Inc. | - |
S1‑162557 | Rapporteur (LGE) | Cover page for eV2X | - |
S1‑162558 | Rapporteur (LGE) | FS_eV2X Status Report | - |
S1‑162559 | Reply LS to SA3 on alternative authentication methods and different types of credentials considerations for NextGen network | SA1/Qualcomm Incorporated | - |
page generated from database: 2024-07-20 12:15:34