3GPP TDocs (written contributions) at meeting
Meeting: S1-53 - 2011-02-14 to 2011-02-18, Nashville
meeting id: S1-53 (click id for more info on this meeting)Click on the Tdoc to open its file.
TDoc | Title | Source | Remarks |
---|---|---|---|
S1‑110000 | Agenda for SA1#53 draft 1 | TB Chairman | imported from 3GU |
S1‑110001 | Agenda for SA1#53 draft 2 | TB Chairman | imported from 3GU |
S1‑110002 | Agenda for SA1#53 draft 3 | TB Chairman | imported from 3GU |
S1‑110003 | Agenda for SA1#53 | TB Chairman | imported from 3GU |
S1‑110004 | Draft Minutes of SA1#52 | ETSI Secretariat | imported from 3GU |
S1‑110005 | Minutes of SA1#52 | ETSI Secretariat | imported from 3GU |
S1‑110006 | SA1 extract of the Work Plan at the beginning of SA1#53 | ETSI Secretariat | imported from 3GU |
S1‑110007 | FS_INIPUI: update to TR22.894 | Rapporteur | imported from 3GU |
S1‑110008 | FS_INIPUI: Updates to the Scope | Vodafone | imported from 3GU |
S1‑110009 | FS_INIPUI: Proposed Definitions | Vodafone | imported from 3GU |
S1‑110010 | FS_INIPUI: Business Relationship between Entities | Vodafone | imported from 3GU |
S1‑110011 | FS_INIPUI: Proposed Updates for Service Scenarios | Vodafone | imported from 3GU |
S1‑110012 | FS_INIPUI: Proposed Text on Security | Vodafone | imported from 3GU |
S1‑110013 | FS_INIPUI: Charging Aspects | Vodafone | imported from 3GU |
S1‑110014 | FS_INIPUI: Potential Regulatory Requirements | Vodafone | imported from 3GU |
S1‑110015 | FS_INIPUI: INIPUI Registry architecture/organisation | Vodafone | imported from 3GU |
S1‑110016 | TR 22.809 FS_VINE Errata (editorial) | Rapporteur | imported from 3GU |
S1‑110017 | LS_in from SA5 to SA1, SA2 Reply on Use cases and suggested requirements for key issue 3 (QoS and gating based on spending limits) in TR 23.813 Study on Policy solutions and enhancements (S1-102396 / S5-102884) | S5-102935 | imported from 3GU |
S1‑110018 | LS_in from SA5 to SA1 (cc: SA2) on Network-provided local time information for IMS Charging | S5-102937 | imported from 3GU |
S1‑110019 | Clarification on applicability of EAB to GERAN only in rel-10 | Alcatel-lucent, Samsung | imported from 3GU |
S1‑110020 | Requirements on frequent small data exchange | China Telecommunications, ZTE, CATT | imported from 3GU |
S1‑110021 | Proposed new requirements for VINE | Vodafone | imported from 3GU |
S1‑110022 | RAT support for EU-Alert | Vodafone | imported from 3GU |
S1‑110023 | Draft LS to SA4 (Cc SA2, SA3) on Requirements and Architecture issues of PSS (S4-110166) | Ericsson | imported from 3GU |
S1‑110024 | TR 22.896 V0.0.0 (Skeleton) | NEC | imported from 3GU |
S1‑110025 | Use Case for Continuity of Data Sessions to Local Networks | NEC | imported from 3GU |
S1‑110026 | Multiple Service Sessions Use Case for FS_ MODAI | China Mobile | imported from 3GU |
S1‑110027 | Non-Web Service Access Use Cases for Section 9 of FS_SSO | China Mobile, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | imported from 3GU |
S1‑110028 | Clarification on the pre-conditions of Section 4 of FS_SSO | China Mobile, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | imported from 3GU |
S1‑110029 | Heterogeneous Network Access Use Cases for Section 9 of FS_SSO | China Mobile | imported from 3GU |
S1‑110030 | Business Model for Section 5 of FS_SSO | China Mobile, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | imported from 3GU |
S1‑110031 | VINE Requirements Clean-Up | Vodafone | imported from 3GU |
S1‑110032 | Draft Skeleton for TR 22.801 non-MTC Mobile Data Applications impacts | Huawei | imported from 3GU |
S1‑110033 | FS_MODAI: Proposed Text for Introduction in TR 22.801 | Huawei, China Mobile, China Telecommunications | imported from 3GU |
S1‑110034 | FS_MODAI: Proposed Text for Scope in TR 22.801 | Huawei, China Mobile, China Telecommunications | imported from 3GU |
S1‑110035 | FS_MODAI: Proposed Text for Background in TR 22.801 | Huawei, China Mobile, China Telecommunications | imported from 3GU |
S1‑110036 | FS_MODAI: Always online mobile data applications use case | China Mobile, Huawei | imported from 3GU |
S1‑110037 | FS_MODAI: User experience Improvement use case | China Telecom, Huawei, ZTE, CATT | imported from 3GU |
S1‑110038 | FS_MODAI: Transmission of small data packet use case | China Mobile, China Telecommunications, Huawei | imported from 3GU |
S1‑110039 | FS_MODAI: Controlling access to RAT use case | Huawei | imported from 3GU |
S1‑110040 | [Draft] Reply LS to "LS on Network-provided local time information for IMS Charging" | ZTE | imported from 3GU |
S1‑110041 | Addition of additional network provided time information for IMS charging | ZTE | imported from 3GU |
S1‑110042 | Addition of a Note to clarify the support for LIPA mobility in Rel-10 | ZTE | imported from 3GU |
S1‑110043 | Addition of a requirement for optimizing paging load for LIPA traffic in Rel-10 | ZTE | imported from 3GU |
S1‑110044 | Comments on Alternatives to E.164 | France Telecom | imported from 3GU |
S1‑110045 | Clarification on the usage of Extended Access Barring for AN & CN Overload | ZTE | imported from 3GU |
S1‑110046 | Clarification on how EAB is applied in Shared Network | ZTE | imported from 3GU |
S1‑110047 | Alignment with Stage2 on overload control and Time Tolerant MTC Feature for Rel-10 | ZTE | imported from 3GU |
S1‑110048 | Alignment with Stage2 on the configuration of MTC Device with low access priority | ZTE | imported from 3GU |
S1‑110049 | Alignment with LS from SA3/SA5 for Rel-10 | ZTE | imported from 3GU |
S1‑110050 | Clarification of MTC Device Triggering | ZTE | imported from 3GU |
S1‑110051 | Addition of security requirement for MTC Device Triggering | ZTE | imported from 3GU |
S1‑110052 | CR to 22.368: Additional security requirements | Panasonic, Intel | imported from 3GU |
S1‑110053 | CR to 22.368: Suppress MTC device triggering | Panasonic, ZTE, Intel | imported from 3GU |
S1‑110054 | PCR to 22.888: Potential service requirements for Communications via MTC Gateway Device | Panasonic, China Mobile, ITRI, ZTE | imported from 3GU |
S1‑110055 | Conclusion for VINE | Verizon Wireless | imported from 3GU |
S1‑110056 | New WID for Support of 3GPP Voice Interworking with Enterprise IP-PBX | Verizon Wireless | imported from 3GU |
S1‑110057 | Proposed Use Case for the TR 22.895 | Alcatel-Lucent | imported from 3GU |
S1‑110058 | 22.101 CR Introduction of NOVES requirements | RIM | imported from 3GU |
S1‑110059 | CR to 22.278: Proposed Annex for MOSAP interworking scenarios | Verizon Wireless | imported from 3GU |
S1‑110060 | CR to 22.278: New Requirements for MOSAP | Verizon Wireless | imported from 3GU |
S1‑110061 | PCR to TR 22.888 - Communication via MTC Gateway Device | Alcatel-Lucent | imported from 3GU |
S1‑110062 | Alignment of requirement with CT6 conclusions | Gemalto, G&D, T-Mobile, | imported from 3GU |
S1‑110063 | CR to Communication control capability | Gemalto | imported from 3GU |
S1‑110064 | Hosting Party Identity Module | Qualcomm, Incorporated | imported from 3GU |
S1‑110065 | Hosting Party Identity Module | Qualcomm, Incorporated | imported from 3GU |
S1‑110066 | CR to 22.220 Rel-9 Hosting Party Identity Module | Qualcomm Inc. | imported from 3GU |
S1‑110067 | VINE WB codec requirement derived from use cases | Qualcomm Inc. | imported from 3GU |
S1‑110068 | CR to 22.268 PWS in RAN sharing environment | Qualcomm Inc. | imported from 3GU |
S1‑110069 | Data from real networks on smartphone impacts | Qualcomm Inc. | imported from 3GU |
S1‑110070 | On the skeleton of TR 22.801 | Qualcomm Inc. | imported from 3GU |
S1‑110071 | Text Proposal for the Scope of TR 22.801 | Qualcomm Inc. | imported from 3GU |
S1‑110072 | On the mitigation of the impact of third party applications to 3GPP cellular networks | Qualcomm Inc. | imported from 3GU |
S1‑110073 | LS on Hosting Party application in UICC | Qualcomm Inc. | imported from 3GU |
S1‑110074 | Editorial change to figure 10.3 and 10.4 Clause 10.1 | Ericsson | imported from 3GU |
S1‑110075 | Clarifying PS to CS handover requirements for multimedia priority calls | Ericsson | imported from 3GU |
S1‑110076 | Discussion on PS to CS handover requirements for multimedia priority eMPS | Ericsson | imported from 3GU |
S1‑110077 | CR 22.228 - Inter-UE transfer/replication control by the content owner | Orange, Telecom Italia | imported from 3GU |
S1‑110078 | FS_U2e - TR 22.817 - editorial corrections | Rapporteur | imported from 3GU |
S1‑110079 | FS_U2e - TR 22.817 - ISO-USB migration considerations | Rapporteur | imported from 3GU |
S1‑110080 | FS_U2e - TR 22.817 - ISO-USB migration considerations | Rapporteur | imported from 3GU |
S1‑110081 | FS_U2e - TR 22.817 - potential requirements | Rapporteur | imported from 3GU |
S1‑110082 | Comments on Noves | Orange | imported from 3GU |
S1‑110083 | MTC Device to Server Communication (TR contribution) | Telefonica S.A. | imported from 3GU |
S1‑110084 | CR to TS22.368 - MTC-IMS Service Layer Capabilities | Telefonica S.A. | imported from 3GU |
S1‑110085 | Fixed Broadband Access Network Requirements for BBAI Building Block 3 - Convergent scenario | Huawei | imported from 3GU |
S1‑110086 | New Requirements for Enterprise Interworking scenario | Verizon Wireless, Cisco | imported from 3GU |
S1‑110087 | BBF requirements for BBAI Convergent scenario | Huawei | imported from 3GU |
S1‑110088 | Clarification on Service Continuity for SIPTO | Huawei | imported from 3GU |
S1‑110089 | Clarification on Policy for SIPTO for H(e)NB subsystem | Huawei | imported from 3GU |
S1‑110090 | NIMTC - SA2 Alignment for MTC Time Tolerant Feature | Sierra Wireless | imported from 3GU |
S1‑110091 | NIMTC - SA2 Alignment for Roaming and Steering | Sierra Wireless | imported from 3GU |
S1‑110092 | IMS emergency call requirements for additional media types | Alcatel-Lucent, AT&T | imported from 3GU |
S1‑110093 | Discussion Paper on BBF Stage-1 Requirements | Alcatel-Lucent | imported from 3GU |
S1‑110094 | NOVES use case caveats when sending independent media | Alcatel-Lucent | imported from 3GU |
S1‑110095 | FS_INIPUI: End to End Service Requirements | AT&T | imported from 3GU |
S1‑110096 | BBF Access Specific Requirements | Alcatel-Lucent | imported from 3GU |
S1‑110097 | Consideration for Extended Access Barring | NTT DOCOMO | imported from 3GU |
S1‑110098 | Supplementary services classification on II-NNI | Orange | imported from 3GU |
S1‑110099 | (draft) LS to RAN WG2, CT WG1 (SA WG2, RAN WG3, GERAN WG2) on RAN Sharing for H(e)NB Cells | Vodafone | imported from 3GU |
S1‑110100 | RAN Sharing for H(e)NB | Vodafone | imported from 3GU |
S1‑110101 | draft reply LS on Security Issues with Logged MDT | Vodafone | imported from 3GU |
S1‑110102 | Logged MDT User Privacy and Consent | Vodafone | imported from 3GU |
S1‑110103 | draft WID on IMS Network-Independent Public User Identities | Vodafone | imported from 3GU |
S1‑110104 | VINE requirements for CS interworking | Vodafone | imported from 3GU |
S1‑110105 | Discussion paper: H(e)NB RAN sharing request from Release 10 | Orange | imported from 3GU |
S1‑110106 | LS to SA WG5 (Cc GSMA CPWP, CT WG1, SA WG2) reply on service identification for charging purposes in case of IMS Roaming | Ericsson | imported from 3GU |
S1‑110107 | FS_INIPUI: Proposed Conclusions | Vodafone | imported from 3GU |
S1‑110108 | Response on LS to SA (Cc ITU-T SG2, GSMA, 3GPP2) on display of duplicated numbers in the phone book | Nokia | imported from 3GU |
S1‑110109 | Display of duplicated numbers in the phone book | Nokia | imported from 3GU |
S1‑110110 | MTC 'Offline' Ambiguity | Renesas Electronics Europe | imported from 3GU |
S1‑110111 | Withdrawn with ADN | - | imported from 3GU |
S1‑110112 | CR 22.368 Removal of ambiguity with MTC 'Offline' | Renesas Electronics Europe | imported from 3GU |
S1‑110113 | Mirror of overload control requirement with low access priority from Rel-10 | ZTE, KPN, Panasonic | imported from 3GU |
S1‑110114 | Mirror of the configuration requirement of MTC Device with low access priority from Rel-10 | ZTE, KPN, Panasonic | imported from 3GU |
S1‑110115 | Clean-up on VINE TR | Orange | imported from 3GU |
S1‑110116 | Reply LS for MDT | NTT DOCOMO | imported from 3GU |
S1‑110117 | Reply LS to RAN3 (Cc SA2/RAN2) on support of PWS in RAN Sharing Environment | Alcatel-Lucent | imported from 3GU |
S1‑110118 | Reply LS to Discussion on Cell Broadcast Service for MOCN Shared Network | Alcatel-Lucent | imported from 3GU |
S1‑110119 | Use cases for MOSAP | Intel | imported from 3GU |
S1‑110120 | MODAI | Intel | imported from 3GU |
S1‑110121 | Discussion on policy for SIPTO | Huawei | imported from 3GU |
S1‑110122 | Clarification for SIPTO policy | Huawei | imported from 3GU |
S1‑110123 | Discussion on MTC Feature priority | Huawei | imported from 3GU |
S1‑110124 | FS_MODAI: Use Case of Offloading Cellular Network Data to WiFi Networks | Motorola Mobility | imported from 3GU |
S1‑110125 | FS_MODAI: Use Case of Seamless Handover of Cellular Data Services to Trusted WiFi Networks | Motorola Mobility | imported from 3GU |
S1‑110126 | FS_SSO: Proposed texts for TR 22.895 Section 4 | Motorola Mobility | imported from 3GU |
S1‑110127 | FS_INIPUI: Updates to Potential Requirements | Telecom Italia | imported from 3GU |
S1‑110128 | FS_U2e: proposal of a new use case | Telecom Italia | imported from 3GU |
S1‑110129 | FS_U2e: proposal of a new use case | Telecom Italia | imported from 3GU |
S1‑110130 | Clarifications for Extended Access Barring | Huawei | imported from 3GU |
S1‑110131 | Discussion on SIMTC prioritization | KPN | imported from 3GU |
S1‑110132 | Reply LS to S3-101435 on MTC USIM requirements | KPN | imported from 3GU |
S1‑110133 | 22.368 Rel-10 alignment on MTC USIM requirements | KPN | imported from 3GU |
S1‑110134 | Reply LS to S5-110553 on MTC Charging requirements for Rel-10 | KPN | imported from 3GU |
S1‑110135 | 22.368 Rel-10 alignment on MTC Charging requirements | KPN | imported from 3GU |
S1‑110136 | MOSAP consent based charging | Samsung Electronics | imported from 3GU |
S1‑110137 | SIMTC Work Planning and Prioritization | Samsung Electronics | imported from 3GU |
S1‑110138 | NIMTC - CR Update Service User Definition | Sierra Wireless | imported from 3GU |
S1‑110139 | M2M specific optimizations for LTE | Vodafone | imported from 3GU |
S1‑110140 | Clarification of terminology and use cases | Alcatel-Lucent | imported from 3GU |
S1‑110141 | Conclusions on HES and business trunking | Alcatel-Lucent | imported from 3GU |
S1‑110142 | Need for E-AS to access subscriber data | Alcatel-Lucent | imported from 3GU |
S1‑110143 | Removal of Unified Communication Services terminology | Alcatel-Lucent | imported from 3GU |
S1‑110144 | Clarification to use case in clause 6.2.1 | Alcatel-Lucent | imported from 3GU |
S1‑110145 | Meeting report for SSO WG | Rapporteur | imported from 3GU |
S1‑110146 | 'Extended Access Barring' discussion paper | Qualcomm Inc. | imported from 3GU |
S1‑110147 | CR to 22.011 (Rel-10) related to Access Control | Qualcomm Inc. | imported from 3GU |
S1‑110148 | Response to GERAN 2 LS on Extended Access Barring | Qualcomm Inc. | imported from 3GU |
S1‑110149 | Response to SA LS on Extended Access Barring | Qualcomm Inc. | imported from 3GU |
S1‑110150 | Update of existing Use Case 4 with requirements for TR 22.895 | InterDigital Communications | imported from 3GU |
S1‑110151 | Update of existing Use Case 1 with requirements for TR 22.895 | InterDigital Communications | imported from 3GU |
S1‑110152 | Update of existing Use Case 2 with requirements for TR 22.895 | InterDigital Communications | imported from 3GU |
S1‑110153 | 22011 Network Sharing, Unbarring, and clean-up | Sierra Wireless | imported from 3GU |
S1‑110154 | Proposed VINE text for CS interworking | Tatara Systems | imported from 3GU |
S1‑110155 | Proposed VINE requirements for emergency services | Tatara Systems | imported from 3GU |
S1‑110156 | MTC 'Offline' Ambiguity | Renesas Electronics Europe | For M2M |
S1‑110157 | Supplementary services classification on II-NNI | Orange | For C-IMS |
S1‑110158 | CR to 22.228 on IUT Privacy | Huawei | Merged with S1-110077 into S1-110191 |
S1‑110159 | RAN Sharing for H(e)NB | Vodafone | Noted, see S1-110099 on the same topic. |
S1‑110160 | Discussion on policy for SIPTO | Huawei | See corresponding CR in S1-110122 |
S1‑110161 | VINE requirements for CS interworking | Vodafone | For VINE |
S1‑110162 | PWS in RAN sharing environment | Qualcomm Incorporated, Alcatel Lucent | Revised to S1-110171 |
S1‑110163 | LS to CT1 (Cc SA2, GERAN2, RAN3, CT) to Discussion on Cell Broadcast Service for MOCN Shared Network | Alcatel-Lucent/SA1 | Approved. |
S1‑110164 | TR 22.988 V0.2.0 on M2M E.164 | T-Mobile | Noted. v.0.3.0 in S1-110358. |
S1‑110165 | Use cases for the TR on M2M | T-Mobile | This is agreed but since it was agreed late, it could not be included in the latest version of the TR in S1-110358. It will be included in the next version. |
S1‑110166 | Hosting Party Identity Module | Qualcomm, Incorporated | Revised to S1-110183 |
S1‑110167 | Hosting Party Identity Module | Qualcomm Incorporated, Sagem Orga GmbH | Revised to S1-110184 |
S1‑110168 | Hosting Party Identity Module | Qualcomm Incorporated, Sagem Orga GmbH | Revised to S1-110185 |
S1‑110169 | LS on Hosting Party application in UICC | Qualcomm Inc. | Withdrawn |
S1‑110170 | LS to CT1 on keeping voice services handed to service restricted areas after successful handover | RIM | Approved. |
S1‑110171 | PWS in RAN sharing environment | Qualcomm Incorporated, Alcatel Lucent | Revised to S1-110180 |
S1‑110172 | Reply LS for MDT to RAN WG2, TSG SA WG3, TSG SA WG5 | NTT DOCOMO | Approved. |
S1‑110173 | Display of duplicated numbers in the phone book | Nokia | Replaced by S1-110405 |
S1‑110174 | Response on LS to SA (Cc ITU-T SG2, GSMA, 3GPP2) on display of duplicated numbers in the phone book | SA1 | Replaced by S1-110406 |
S1‑110175 | Draft LS to SA4, SA3 (Cc SA2) on Requirements and Architecture issues of PSS (S4-110166) | SA1 | Approved. |
S1‑110176 | Removal of the outdated reference to TS 21.133 | Ericsson | Agreed. |
S1‑110177 | Clarifying PS to CS handover requirements for multimedia priority calls | Ericsson | Revised to S1-110182 |
S1‑110178 | New Requirements for Enterprise Interworking scenario | Verizon Wireless, Cisco | Agreed. |
S1‑110179 | LS to SA WG5 (Cc GSMA CPWP, CT WG1, SA WG2) reply on service identification for charging purposes in case of IMS Roaming | SA1 | Revised to S1-110431 |
S1‑110180 | PWS in RAN sharing environment | Qualcomm Incorporated, Alcatel Lucent | Revised to S1-110186 |
S1‑110181 | Fixed Broadband Access Network Requirements for BBAI Building Block 3 - Convergent scenario | Huawei, Alcatel-Lucent, Verizon, NSN, Cisco, Vodafone | Agreed. |
S1‑110182 | Clarifying PS to CS handover requirements for multimedia priority calls | Ericsson | Agreed. |
S1‑110183 | Hosting Party Identity Module | Qualcomm, Incorporated | Agreed. |
S1‑110184 | Hosting Party Identity Module | Qualcomm Incorporated, Sagem Orga GmbH | Agreed. |
S1‑110185 | Hosting Party Identity Module | Qualcomm Incorporated, Sagem Orga GmbH | Agreed. |
S1‑110186 | PWS in RAN sharing environment | Qualcomm Incorporated, Alcatel Lucent | Revised to S1-110433 |
S1‑110187 | Reply LS to RAN3 (Cc SA2, RAN2 and CT1) on support of PWS in RAN Sharing Environment | SA1 | Revised to S1-110434 |
S1‑110188 | LS to SA3 (Cc SA2) on Security Issues for Machine Type Communications | M2M/SA1 | Noted. |
S1‑110189 | New requirements for MOSAP | Verizon Wireless, Deutsche Telekom, Cisco, Intel, Nokia Siemens Networks | Revised to S1-110404 |
S1‑110190 | New WID on Support for 3GPP Voice Interworking with Enterprise IP-PBX | VINE SWG | Revised to S1-110194 |
S1‑110191 | IUT Privacy considerations associated with remote end user and restricting copyrighted content. | Huawei, Orange, Telecom Italia, InterDigital | Revised to S1-110428 |
S1‑110192 | TR 22.809 V1.2.0 on Feasibility Study on Support for | Rapporteur | Agreed to be sent to SA for approval. |
S1‑110193 | Coverpage for TR 22.809 | Rapporteur | Agreed to be sent to SA for approval. |
S1‑110194 | New WID on Support for 3GPP Voice Interworking with Enterprise IP-PBX | VINE SWG | Agreed to be sent to SA for approval. |
S1‑110195 | LS to SA2 on answer to S2-105243 on network verification of UE provided location | SA1 | Agreed. |
S1‑110196 | Reply LS to SA WG2, SA5 (Cc CT1) to “LS on Network-provided local time information for IMS Charging” | SA1 | Agreed. |
S1‑110197 | Coverpage for TR 22.894 | Rapporteur | Agreed. |
S1‑110198 | Withdrawn | - | Withdrawn |
S1‑110199 | LS to SA, 3GPP SA WG2 on Response on a new 3GPP – BBF workshop proposal | BBAI SWG | Approved. |
S1‑110200 | LS on support of PWS in RAN Sharing Environment | R3-102507 | Noted, see related CR in S1-110162. |
S1‑110201 | LS on Work on second edition ECMA TR/92 | Ecma/TC32-TG17/2010/058 | Withdrawn, already treated at SA1#52 as S1-103180. |
S1‑110202 | LS Reply on Use cases and suggested requirements for key issue 3 (QoS and gating based on spending limits) in TR 23.813 Study on Policy solutions and enhancements (S1-102396 / S5-102884) | S5-102935 | Noted without presentation |
S1‑110203 | LS on Network-provided local time information for IMS Charging | S5-102937 | See related CR in S1-110041. |
S1‑110204 | Reply LS on MBR>GBR bearers in MTSI | S4-100880 | Noted without presentation |
S1‑110205 | LS on new Study Item on Core Network Overload issues | S3-101400 | Noted without presentation |
S1‑110206 | Reply LS on Simultaneous registration of a single private identity from different UEs | S3-101402 | Noted without presentation |
S1‑110207 | LS on review of MDT design and reply LS on Security Issues with Logged MDT | S3-101422 | See the two proposed answers in S1-110116 and S1-110102. |
S1‑110208 | LS to SA1 on Hosting Party application in UICC | C6-100634 | Noted. See S1-110232 and S1-110064 on the same topic. |
S1‑110209 | LS to RAN3 on Hosting Party Module for H(e)NB | C6-100633 | Noted without presentation. |
S1‑110210 | Reply LS on direct stage 3 work for NIMTC functionality | C3-101490 | Noted. |
S1‑110211 | Reply LS on RAN sharing for Home(e)NB cells | R2-106942 | Noted without presentation. |
S1‑110212 | Response LS on RAN sharing for Home(e)NB cells | R3-103742 | Noted without presentation. |
S1‑110213 | Reply LS on direct stage 3 work for NIMTC functionality | C4-103168 | Noted. |
S1‑110214 | Reply LS on the Usage of MBR and GBR bearers in MTSI | C3-101505 | Noted without presentation |
S1‑110215 | Reply LS on MTC USIM requirement for Rel-10 | C1-104852 | For M2M |
S1‑110216 | LS on keeping voice services handed to service restricted areas after successful handover | C1-105242 | Answer to be provided in S1-110170. |
S1‑110217 | LS on BBF interworking status | S2-106004 | Noted without presentation |
S1‑110218 | Second LS reply on Location Information for MDT | S2-105960 | Noted without presentation. |
S1‑110219 | LS on security issues about Machine Type Communication | S3-101441 | For M2M IMS. |
S1‑110220 | Reply LS to S1-103315-LS on MTC USIM requirements for Rel-10 | S3-101435 | For M2M |
S1‑110221 | LS on Extended Access Barring | GP-102072 | For M2M |
S1‑110222 | Response LS on MTC USIM requirements for Rel-10 (S1-103315) | C6-100585 | For M2M |
S1‑110223 | LS on Extended Access Barring | SP-100898 | For M2M |
S1‑110224 | LS on Display of duplicated numbers in the phone book | SP-100837 | See related CR in S1-110109. |
S1‑110225 | Response to LS on a new 3GPP – BBF workshop proposal | SP-100875 | For BBAI |
S1‑110226 | Liaison Statement on security issues of PSS service | S4-110175 | See related LSs. |
S1‑110227 | Liaison Statement on Requirements and Architecture issues of PSS service | S4-110166 | See related LSs. |
S1‑110228 | Reply LS to CT6 on Hosting Party Module for H(e)NB | R3-110336 | Noted without presentation |
S1‑110229 | Reply LS on RAN sharing for Home(e)NB cells | S2-110160 | Noted without presentation. |
S1‑110230 | LS on RAN Sharing for H(e)NB Cells | R2-110691 | Noted. |
S1‑110231 | LS on MDT user involvement | R2-110699 | Noted without presentation. |
S1‑110232 | reply LS to CT6 on LS on Hosting Party Module for H(e)NB (S3-110157 / C6-100634) | S3-110184 | Noted. See related CR in S1-110064. |
S1‑110233 | LS on Use Cases & Suggested Requirements for Non-Voice-Centric (NVC) Emergency | NENA 73-501 | Postponed to next meeting. |
S1‑110234 | Reply to LS on RAN Sharing for H(e)NB Cells | C1-110774 | Noted. |
S1‑110235 | LS on Cell Broadcast Service for MOCN Shared Network | C1-110777 | Noted, see proposed answer in S1-110163. |
S1‑110236 | Rely LS on Liaison Statement on security issues of PSS service | S3-110202 | Proposed answer to S1-110226, 227 and 236 in S1-110023. |
S1‑110237 | Reply LS on MDT user involvement | S3-110185 | Noted without presentation. |
S1‑110238 | LS on security for PWS | S3-110205 | Noted. |
S1‑110239 | LS reply on service identification for charging purposes in case of IMS Roaming | S5-110552 | See proposed answer in S1-110106. |
S1‑110240 | LS on MTC charging requirements for Rel-10 | S5-110553 | For M2M |
S1‑110241 | Liaison Statement on NOVES | EMTEL(11)0002r2 | For Noves SWG |
S1‑110242 | LS on network verification of UE provided location | S1-103160/ S2-105243 | Noted. See related LS in S1-110203. To be considered also in the IMS SWG. |
S1‑110243 | LS on addition of Transit IOI for IMS Interconnection Charging | S5-110497 | Noted without presentation |
S1‑110244 | Reply LS on review of MDT design and reply LS on Security Issues with Logged MDT | S5-110529 | Noted without presentation. |
S1‑110245 | LS on “Wide area sensor and/or actuator network (WASN) systems” | RT-110024 | Answered together with S1-110246 in S1-110248 |
S1‑110246 | LS on “Quality of Service requirements and objectives for wireless access systems” | RT-110025 | Answered together with S1-110245 in S1-110248 |
S1‑110247 | Reply LS on MDT user involvement (S5-110367 / R2-110699) | S5-110482 | Noted without presentation. |
S1‑110248 | LS to RAN ITU-R Ad Hoc (Cc SA2, SA4, RAN2, RAN3, CT1 on Response on LS on “Wide area sensor and/or actuator network (WASN) systems” (RT-110024) and on “Quality of Service requirements and objectives for wireless access systems” (RT-110025) | SA1 | Approved. |
S1‑110249 | Not allocated | - | Not used |
S1‑110250 | SWG presentation to SA1 plenary | SWG chair | Noted. |
S1‑110251 | SWG meeting report | SWG chair | Approved. |
S1‑110252 | Proposed Agenda for MODAI SWG SA1#53 | SWG Chair (Huawei) | For MODAI |
S1‑110253 | TR 22.801 V0.1.0 on Study on non-MTC Mobile Data Applications impacts | Rapporteur | Agreed as a basis for future contributions. |
S1‑110254 | TR 22.801 V0.0.0 on Study on non-MTC | Rapporteur | For MODAI |
S1‑110255 | Proposed Text for Introduction in TR 22.801 | Huawei, China Mobile, China Telecommunications | For MODAI |
S1‑110256 | Proposed Text for Scope in TR 22.801 | Huawei, China Mobile, China Telecommunications, Qualcomm | For MODAI |
S1‑110257 | Proposed Text for Background in TR 22.801 | Huawei, China Mobile, China Telecommunications, Intel | For MODAI |
S1‑110258 | Data from real UMTS networks on smartphone impacts | tilization, traffic, | For MODAI |
S1‑110259 | Transmission of small data packet use case | China Mobile, China Telecommunications, Huawei | For MODAI |
S1‑110260 | Use case: Status updates and keep-alive messages due to always on mobile | China Mobile, Huawei, Intel, China Telecomm | For MODAI |
S1‑110261 | Not allocated | - | For MODAI |
S1‑110262 | Not allocated | - | For MODAI |
S1‑110263 | Not allocated | - | For MODAI |
S1‑110264 | Not allocated | - | For MODAI |
S1‑110265 | SWG presentation to SA1 plenary | SWG chair | Noted. |
S1‑110266 | SWG meeting report | SWG chair | Approved. |
S1‑110267 | Not allocated | - | For CSN |
S1‑110268 | Use Case for Continuity of Data Sessions to Local Networks | NEC, Samsung, Alcatel Lucent, AT&T | For CSN |
S1‑110269 | Not allocated | - | For CSN |
S1‑110270 | SWG presentation to SA1 plenary | SWG chair | Noted. |
S1‑110271 | SWG meeting report | SWG chair | Approved. |
S1‑110272 | Agenda for SSO SWG | SWG Chair | For SSO |
S1‑110273 | Agenda for SSO SWG | SWG Chair | For SSO |
S1‑110274 | Clarification on the pre-conditions of Section 4 of FS_SSO | China Mobile, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | For SSO |
S1‑110275 | FS_SSO: Proposed texts for TR 22.895 Section 4 | Motorola Mobility | For SSO |
S1‑110276 | Common Pre-conditions for SSO Use Cases | China Mobile, Motorola Mobility | For SSO |
S1‑110277 | Non-Web Service Access Use Cases for Section 9 of FS_SSO | China Mobile, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | For SSO |
S1‑110278 | Proposed Use Case for the TR 22.895 | Alcatel-Lucent, Alcatel-Lucent Shanghai Bell, InterDigital | For SSO |
S1‑110279 | Update of Existing Use Case 1 with Requirements for TR 22.895 | InterDigital | Revised to S1-110425 |
S1‑110280 | Update of Existing Use Case 2 with Requirements for TR 22.895 | InterDigital, Inc. | For SSO |
S1‑110281 | Business Model for Section 5 of FS_SSO | China Mobile, Alcatel-Lucent, Alcatel-Lucent Shanghai Bell | For SSO |
S1‑110282 | Common Pre-conditions for SSO Use Cases | China Mobile, Motorola Mobility | For SSO |
S1‑110283 | TR 22.895 | Rapporteur | Not available. To be sent as soon as possible by the rapporteur. |
S1‑110284 | Not allocated | - | Not used |
S1‑110285 | SWG presentation to SA1 plenary | SWG chair | Noted. |
S1‑110286 | SWG meeting report | SWG chair | Approved. |
S1‑110287 | U2e SWG agenda | SWG Chairman | For U2 |
S1‑110288 | Editorial Corrections | Rapporteur | For U2 |
S1‑110289 | Editor´s notes | Rapporteur | For U2 |
S1‑110290 | ISO / USB migration | Rapporteur | For U2 |
S1‑110291 | UICC applications Partial Forward Compatibility | Rapporteur | For U2 |
S1‑110292 | Use Cases | Telecom Italia | For U2 |
S1‑110293 | Use case – USAT application download reducing network traffic overload | Telecom Italia | For U2 |
S1‑110294 | TR 22.817 v0.4.0 on Study on UICC/USIM enhancements | SWG Chairman | Agreed as a basis for future contributions. |
S1‑110295 | SWG presentation to SA1 plenary | SWG chair | Noted. |
S1‑110296 | SWG meeting report | SWG chair | Approved. |
S1‑110297 | Scenarios for Interworking between Mobile Operators and Application Providers | Verizon Wireless, Cisco, Intel | Agreed. |
S1‑110298 | Use cases for MOSAP | Intel, Verizon Wireless, Cisco, Motorola Mobility | For MOSAP |
S1‑110299 | Withdrawn | Samsung | Withdrawn. |
S1‑110300 | New requirements for MOSAP | Verizon Wireless, Deutsche Telekom, Cisco, Intel, Nokia Siemens Networks | Revised to S1-110189 |
S1‑110301 | Proposed Agenda for the MOSAP SWG | MOSAP SWG Chairman (Cisco Systems) | For MOSAP |
S1‑110302 | Use cases for MOSAP | Intel, Verizon Wireless, Cisco, Motorola Mobility | Agreed. |
S1‑110303 | Agenda for the MOSAP SWG | MOSAP SWG Chairman (Cisco Systems) | For MOSAP |
S1‑110304 | Not allocated | - | For MOSAP |
S1‑110305 | SWG presentation to SA1 plenary | SWG chair | Noted. |
S1‑110306 | SWG meeting report | SWG chair | Approved. |
S1‑110307 | Draft LS on Response on a new 3GPP – BBF workshop proposal | SWG | Revised to S1-110199. |
S1‑110308 | Fixed Broadband Access Network Requirements for BBAI Building Block 3 - Convergent scenario | Huawei, Alcatel-Lucent, Verizon | Revised to S1-110181 |
S1‑110309 | Not allocated | - | For BBAI |
S1‑110310 | SWG presentation to SA1 plenary | SWG chair | For Noves SWG |
S1‑110311 | SWG meeting report | SWG chair | For BBAI |
S1‑110312 | NOVES SWG Agenda | SWG Chair | For BBAI |
S1‑110313 | NOVES European aspects | NOVES SWG | Agreed. |
S1‑110314 | Draft LS to EMTEL on Reply to S1-110241 on NOVES from ETSI EMTEL | NOVES SWG | Revised to S1-110317 |
S1‑110315 | IMS emergency call requirements for additional media types | Alcatel-Lucent, AT&T | Revised to S1-110319 |
S1‑110316 | Comments on Noves | Orange – France Telecom | Agreed. |
S1‑110317 | LS to EMTEL on Reply to S1-110241 on NOVES from ETSI EMTEL | NOVES SWG | Revised to S1-110318 |
S1‑110318 | LS to EMTEL on Reply to S1-110241 on NOVES from ETSI EMTEL | SA1 | Agreed. |
S1‑110319 | IMS emergency call requirements for additional media types | Alcatel-Lucent, AT&T | Withdrawn |
S1‑110320 | SWG meeting report | SWG chair | Approved. |
S1‑110321 | SWG presentation to SA1 plenary | SWG chair | Noted. |
S1‑110322 | Draft Agenda for the C-IMS SWG | SWG Chair | For C-IMS |
S1‑110323 | Addition of additional network provided time information for IMS charging | ZTE, AT&T | For C-IMS |
S1‑110324 | LS to SA2 on network verification of UE provided location | 3GPP SA WG1 | For C-IMS |
S1‑110325 | Addition of additional network provided time information for IMS charging | ZTE, AT&T | Agreed. |
S1‑110326 | Reply LS to SA WG2, SA5 (Cc CT1) to “LS on Network-provided local time information for IMS Charging” | CIMS SWG/SA1 | Revised to S1-110196 |
S1‑110327 | FS_INIPUI: Proposed Definitions | Vodafone | For C-IMS |
S1‑110328 | FS_INIPUI: Business Relationship between Entities | Vodafone | For C-IMS |
S1‑110329 | FS_INIPUI: Updates to Potential Requirements | Telecom Italia, Vodafone | For C-IMS |
S1‑110330 | FS_INIPUI: End to End Service Requirements | AT&T | For C-IMS |
S1‑110331 | FS_INIPUI: Updates to the Scope | Vodafone, Telecom Italia | For C-IMS |
S1‑110332 | FS_INIPUI: Proposed Text on Security | Vodafone | For C-IMS |
S1‑110333 | FS_INIPUI: Charging Aspects | Vodafone, Telecom Italia | For C-IMS |
S1‑110334 | FS_INIPUI: INIPUI Registry architecture/organisation | Vodafone | For C-IMS |
S1‑110335 | FS_INIPUI: Proposed Conclusions | Vodafone | For C-IMS |
S1‑110336 | TR 22.894 V0.3.0 on Feasibility Study on IMS Network-Independent Public User Identities | Rapporteur | Agreed to be sent for information to SA. |
S1‑110337 | Coverpage for TR 22.894 | Rapporteur | Revised to S1-110197 |
S1‑110338 | LS to SA2 on answer to S2-105243 on network verification of UE provided location | CIMS SWG/SA1 | Revised to S1-110195 |
S1‑110339 | Supplementary services classification on II-NNI | France Telecom | Agreed. |
S1‑110340 | SWG presentation to SA1 plenary | SWG chair | Noted. |
S1‑110341 | SWG meeting report | SWG chair | Approved. |
S1‑110342 | Proposed Agenda for the VINE SWG | SWG Chairman (Tatara Systems) | For VINE |
S1‑110343 | Proposed Agenda for the VINE SWG | SWG Chairman (Tatara Systems) | For VINE |
S1‑110344 | Clean-up on VINE TR | Orange | For VINE |
S1‑110345 | Clarification of terminology and use cases | Alcatel-Lucent | For VINE |
S1‑110346 | VINE WB codec requirement derived from use cases | Qualcomm Inc | For VINE |
S1‑110347 | P-CR on TR 22.809 (FS_VINE) – requirements for emergency services | Tatara Systems, Verizon Wireless | For VINE |
S1‑110348 | Clean-up on VINE TR | Orange | For VINE |
S1‑110349 | Clarification of terminology and use cases | Alcatel-Lucent | For VINE |
S1‑110350 | VINE Requirements Clean-up | Vodafone | For VINE |
S1‑110351 | Conclusion for VINE | Verizon Wireless, Vodafone, Alcatel-Lucent, Cisco | For VINE |
S1‑110352 | Draft WID for VINE | SWG | Revised to S1-110190 |
S1‑110353 | TR 22.809 V1.1.0 on Feasibility Study on Support for | Rapporteur | Revised to S1-110192 |
S1‑110354 | Proposed Agenda for the VINE SWG | SWG Chairman (Tatara Systems) | For VINE |
S1‑110355 | SWG presentation to SA1 plenary | SWG chair | Noted. |
S1‑110356 | SWG meeting report | SWG chair | Revised to S1-110426 |
S1‑110357 | Agenda M2M SWG meeting | Chairman M2M SWG | For M2M |
S1‑110358 | TR 22.988 V0.3.0 on Study on Alternatives to E.164 for Machine-Type Communications (Release 10) | Rapporteur | This is the agreed output of the M2M SWG meeting. |
S1‑110359 | TR 22.888 V0.4.0 on Study on Enhancements for MTC (Rel-11). | Rapporteur | This is the agreed output of the M2M SWG meeting. |
S1‑110360 | MTC charging requirements in Rel-11 | KPN | For M2M |
S1‑110361 | DRAFT LS on MTC charging requirements for Release 10 | 3GPP SA WG1 | For M2M |
S1‑110362 | Allocated by M2M | ZTE | For M2M |
S1‑110363 | DRAFT LS to SA3, CT1, CT6 on MTC USIM requirements for Release 10 | M2M SWG/SA1 | Revised to S1-110422 |
S1‑110364 | SA2 Alignment for MTC Time Tolerant Feature | Sierra Wireless | Agreed. |
S1‑110365 | Consideration for Extended Access Barring | NTT DOCOMO | For M2M |
S1‑110366 | DRAFT LS on Security Issues for Machine Type Communications | M2M SWG chair | Revised offline to S1-110188 |
S1‑110367 | Clarifications for Extended Access Barring | Huawei | Revised to S1-110403 |
S1‑110368 | Clarification of EAB | Sierra Wireless | Revised to S1-110410 |
S1‑110369 | Removal of ambiguity with MTC 'Offline' | Renesas Electronics Europe, Nokia Corporation | Revised to S1-110415 |
S1‑110370 | Additional security for MTC Triggering requirements | Panasonic, Intel, KPN, ZTE | Revised to S1-110413 |
S1‑110371 | Discussion on SIMTC Prioritisation | KPN | For M2M |
S1‑110372 | Discussion on SIMTC Prioritisation | KPN | For M2M SWG |
S1‑110373 | DRAFT LS on MTC charging requirements for Release 10 | 3GPP SA WG1 | For M2M |
S1‑110374 | MTC charging requirements in Rel-10 | KPN | Agreed. |
S1‑110375 | Suppress MTC device triggering | Panasonic, ZTE, Intel, ITRI, KPN | Revised to S1-110414 |
S1‑110376 | MTC - IMS Service Layer Capabilities | Telefonica | Revised to S1-110408 |
S1‑110377 | MTC Device-to-Server Communication | Telefonica | For M2M |
S1‑110378 | TR 22.988 V0.2.0 on Study on Alternatives to E.164 for Machine-Type Communications | Rapporteur | For M2M |
S1‑110379 | DRAFT LS to SA5 on MTC charging requirements for Release 10 | M2M SWG | Revised to S1-110421 |
S1‑110380 | Informal Voting results and chairman proposal | Chair+MCC | Revised to S1-110407 |
S1‑110381 | LS to SA and SA2 on SIMTC work prioritization for Rel-11 | Chair/SA1 | Revised to S1-110419 |
S1‑110382 | Not allocated | - | For M2M |
S1‑110383 | Not allocated | - | For M2M |
S1‑110384 | Not allocated | - | For M2M |
S1‑110385 | Not allocated | - | For M2M |
S1‑110386 | Not allocated | - | For M2M |
S1‑110387 | Not allocated | - | For M2M |
S1‑110388 | Not allocated | - | For M2M |
S1‑110389 | Not allocated | - | For M2M |
S1‑110390 | Not allocated | - | For M2M |
S1‑110391 | Not allocated | - | For M2M |
S1‑110392 | Not allocated | - | For M2M |
S1‑110393 | Not allocated | - | For M2M |
S1‑110394 | Not allocated | - | For M2M |
S1‑110395 | Not allocated | - | For M2M |
S1‑110396 | Not allocated | - | For M2M |
S1‑110397 | Not allocated | - | For M2M |
S1‑110398 | Not allocated | - | For M2M |
S1‑110399 | Not allocated | - | For M2M |
S1‑110400 | TR 22.896 V0.0.1 on Study on Continuity of Data Sessions to Local Networks | Rapporteur | For CSN |
S1‑110401 | Use Case for Continuity of Data Sessions to Local Networks | NEC, Samsung, Alcatel Lucent, AT&T | For CSN |
S1‑110402 | TR 22.896 V0.1.0 on Study on Continuity of Data Sessions to Local Networks | Rapporteur | Agreed as a basis for future contributions. |
S1‑110403 | Clarifications for Extended Access Barring | Huawei | Revised to S1-110409 |
S1‑110404 | New requirements for MOSAP | Verizon Wireless, Deutsche Telekom, Cisco, Intel, Nokia Siemens Networks | Agreed. |
S1‑110405 | Display of duplicated numbers in the phone book | Nokia | Agreed. |
S1‑110406 | Response on LS to SA (Cc ITU-T SG2, GSMA, 3GPP2) on display of duplicated numbers in the phone book | SA1 | Agreed. |
S1‑110407 | Informal Voting results and chairman proposal | Chair+MCC | Agreed. |
S1‑110408 | MTC - IMS Service Layer Capabilities | Telefonica | Revised to S1-110420 |
S1‑110409 | Clarifications for Extended Access Barring | Huawei | Agreed. |
S1‑110410 | Clarification of EAB | Sierra Wireless | Agreed. |
S1‑110411 | Clarification of EAB | Sierra Wireless | Agreed. |
S1‑110412 | MTC charging requirements in Rel-11 | KPN | Revised to S1-110427 |
S1‑110413 | Additional security for MTC Triggering requirements | Panasonic, Intel, KPN, ZTE | Revised to S1-110429 |
S1‑110414 | Suppress MTC device triggering | Panasonic, ZTE, Intel, ITRI, KPN | Agreed. |
S1‑110415 | Removal of ambiguity with MTC 'Offline' | Renesas Electronics Europe, Nokia Corporation | Withdrawn. |
S1‑110416 | LS Response to GERAN 2 (Cc SA, RAN2, SA2 and CT1) on LS on Extended Access Barring | Qualcomm Inc. | Revised to S1-110423 |
S1‑110417 | Response to SA (Cc RAN2, GERAN2, SA2 and CT1) on Extended Access Barring | Qualcomm Inc. | Revised to S1-110424 |
S1‑110418 | Supplementary services classification on II-NNI | France Telecom | Revised to S1-110430 |
S1‑110419 | LS to SA and SA2 on SIMTC work prioritization for Rel-11 | SA1 | Agreed. |
S1‑110420 | MTC - IMS Service Layer Capabilities | Telefonica | Agreed. |
S1‑110421 | LS to SA5 on MTC charging requirements for Release 10 | SA1 | Agreed. |
S1‑110422 | LS to SA3, CT1, CT6 on MTC USIM requirements for Release 10 | SA1 | Agreed. |
S1‑110423 | LS Response to GERAN 2 (Cc SA, RAN2, SA2 and CT1) on LS on Extended Access Barring | Qualcomm Inc. | Revised to S1-110432 |
S1‑110424 | LS to SA (Cc RAN2, GERAN2, SA2 and CT1) on response on Extended Access Barring | SA1 | Agreed. |
S1‑110425 | Update of Existing Use Case 1 with Requirements for TR 22.895 | InterDigital | Agreed. |
S1‑110426 | SWG meeting report | SWG chair | Agreed. |
S1‑110427 | MTC charging requirements in Rel-11 | KPN | Agreed. |
S1‑110428 | IUT Privacy considerations associated with remote end user and restricting copyrighted content. | Huawei, Orange, Telecom Italia, InterDigital | Agreed. |
S1‑110429 | Additional security for MTC Triggering requirements | Panasonic, Intel, KPN, ZTE | Agreed. |
S1‑110430 | Supplementary services classification on II-NNI | France Telecom | Agreed. |
S1‑110431 | LS to SA WG5 (Cc GSMA CPWP, CT WG1, SA WG2) reply on service identification for charging purposes in case of IMS Roaming | SA1 | Agreed. |
S1‑110432 | LS Response to GERAN 2 (Cc SA, RAN2, SA2 and CT1) on LS on Extended Access Barring | Qualcomm Inc. | Agreed. |
S1‑110433 | PWS in RAN sharing environment | Qualcomm Incorporated, Alcatel Lucent | Agreed. |
S1‑110434 | Reply LS to RAN3 (Cc SA2, RAN2 and CT1) on support of PWS in RAN Sharing Environment | SA1 | Agreed. |
page generated from database: 2024-09-26 11:02:35