3GPP TDocs (written contributions) at meeting
Meeting: S1-54 - 2011-05-09 to 2011-05-13, Xian
meeting id: S1-54 (click id for more info on this meeting)Click on the Tdoc to open its file.
TDoc | Title | Source | Remarks |
---|---|---|---|
S1‑111000 | SA1#54 agenda draft 1 | TB Chairman | imported from 3GU |
S1‑111001 | SA1#54 Agenda Draft 2 | TB Chairman | imported from 3GU |
S1‑111002 | SA1#54 Agenda Draft 3 | TB Chairman | imported from 3GU |
S1‑111003 | SA1#54 Agenda | TB Chairman | imported from 3GU |
S1‑111004 | Draft Minutes of SA1#53 | ETSI Secretariat | imported from 3GU |
S1‑111005 | Minutes of SA1#53 | ETSI Secretariat | imported from 3GU |
S1‑111006 | SA1 extract of the Work Plan at the beginning of SA1#54 | ETSI Secretariat | imported from 3GU |
S1‑111007 | TR 22.988 Baseline Version 0.4.0 | Rapporteur | imported from 3GU |
S1‑111008 | Additional Use Case for TR 22.988 | Rapporteur | imported from 3GU |
S1‑111009 | Requirements and Conclusion for TR 22.988 | Rapporteur | imported from 3GU |
S1‑111010 | Editorial updates to TR22.894 | Rapporteur | imported from 3GU |
S1‑111011 | FS_INIPUI: Updates to Definitions | Vodafone | imported from 3GU |
S1‑111012 | FS_INIPUI: Further Clarification of the Business Relationships | Vodafone | imported from 3GU |
S1‑111013 | FS_INIPUI: Updates to Potential Requirements | Vodafone | imported from 3GU |
S1‑111014 | FS_INIPUI: Authoritative Provisioning Aspects | Vodafone | imported from 3GU |
S1‑111015 | FS_INIPUI: Discussion of inter-operator settlement | Vodafone | imported from 3GU |
S1‑111016 | FS_INIPUI: Proposed Conclusions | Vodafone | imported from 3GU |
S1‑111017 | Draft Work Item for IMS Network-Independent Public User Identities | Vodafone | imported from 3GU |
S1‑111018 | CR to 22.228 on IMS Network-Independent Public User Identities | Vodafone | imported from 3GU |
S1‑111019 | CR to 21.905 on Addition of new terms | Vodafone | imported from 3GU |
S1‑111020 | Introduction of Non-Voice Emergency Services (NOVES) | AT&T, Alcatel-Lucent | imported from 3GU |
S1‑111021 | Reply to SA2 LS on MTC Service Requirements | KPN | imported from 3GU |
S1‑111022 | CR on 22.368 on Clarification of triggering when offline | KPN | imported from 3GU |
S1‑111023 | Removal of PBX integration requirements | Deutsche Telekom, Vodafone | imported from 3GU |
S1‑111024 | Removal of PBX integration requirements | Deutsche Telekom, Vodafone | imported from 3GU |
S1‑111025 | Removal of Rel-10 MTC charging requirements | KPN | imported from 3GU |
S1‑111026 | Correction of charging requirements | Rapporteur (KPN) | imported from 3GU |
S1‑111027 | FS_RESUM WID - Study on Remote Subscription Management | FS_RESUM Rapporteur | imported from 3GU |
S1‑111028 | RESUM Skeleton TR22.8xx v0.0.1 | FS_RESUM Rapporteur | imported from 3GU |
S1‑111029 | Proposed scope for RESUM TR22.8xx | Qualcomm Incorporated, Clearwire, Sprint, KDDI | imported from 3GU |
S1‑111030 | Proposed general use case for RESUM TR22.8xx | Qualcomm Incorporated | imported from 3GU |
S1‑111031 | Proposed use case for RESUM TR22.8xx | Qualcomm Incorporated | imported from 3GU |
S1‑111032 | FS_RESUM: Use Case for RESUM | Motorola Mobility, Samsung | imported from 3GU |
S1‑111033 | Proposal for Study: Simultaneous Connectivity, Flow-Splitting and Dynamic Policy Control: Aggregation | InterDigital Communications | imported from 3GU |
S1‑111034 | Priority treatment for Network Management functions | Telcordia Technologies, National Communications System, AT&T | imported from 3GU |
S1‑111035 | Clarification of Priority Information | Telcordia Technologies, National Communications System | imported from 3GU |
S1‑111036 | MTC - IMS Service Layer Capabilities | Telefonica | imported from 3GU |
S1‑111037 | Amended Text to section 4.3 of TR22.888 MTC Device to Server Communication | Telefonica S.A. | imported from 3GU |
S1‑111038 | Input contribution to INIPUI TR22.894 | Telefonica S.A. | imported from 3GU |
S1‑111039 | FS_SSO_int: Use case for SSO and some editorial changes of SSO TR | Motorola Mobility | imported from 3GU |
S1‑111040 | FS_SSO_int: On Common Pre-conditions in Section 4.1 | Motorola Mobility, China Mobile | imported from 3GU |
S1‑111041 | Use case for high frequency of initiating applications | Rapporteur | imported from 3GU |
S1‑111042 | Use case for high frequency of initiating applications | Rapporteur | imported from 3GU |
S1‑111043 | Use case for high frequency of initiating applications | China Unicom | imported from 3GU |
S1‑111044 | Use case for high frequency of initiating applications | China Unicom | imported from 3GU |
S1‑111045 | PCR to 33.895 | Alcatel-Lucent, AT&T | imported from 3GU |
S1‑111046 | Clarification on MTC User Definition of TS 22.368 | China Mobile | imported from 3GU |
S1‑111047 | Clarification on MTC Communication Scenarios of TS 22.368 | China Mobile | imported from 3GU |
S1‑111048 | New Requirements for MTC Monitoring Feature | China Mobile | imported from 3GU |
S1‑111049 | Addition of SSO Provider Definition | China Mobile | imported from 3GU |
S1‑111050 | Pre-conditions alignment for use cases of TR 22.895 | China Mobile | imported from 3GU |
S1‑111051 | Update of Non-Web Service Access Use Case of TR 22.895 | China Mobile | imported from 3GU |
S1‑111052 | Service experience correction for level of interruption of IP connectivity to the residential/enterprise IP network | RIM | imported from 3GU |
S1‑111053 | Removal of Requirement for UDC Data Model | NSN | imported from 3GU |
S1‑111054 | Clarification on how EAB is applied in Shared Network | ZTE, Panasonic, SierraWireless | imported from 3GU |
S1‑111055 | Clarification on how to control access attempts from UEs configured for EAB(R10) | ZTE | imported from 3GU |
S1‑111056 | Clarification on how to control access attempts from UEs configured for EAB(R11) | ZTE | imported from 3GU |
S1‑111057 | Discussion on offline status and MTC Device trigger | ZTE | imported from 3GU |
S1‑111058 | Not used | - | imported from 3GU |
S1‑111059 | Not used | - | imported from 3GU |
S1‑111060 | Clarificaion of "Offline" in MTC Device Trigger | ZTE | imported from 3GU |
S1‑111061 | Clarification of Time Controlled MTC Feature | ZTE | imported from 3GU |
S1‑111062 | MTC Device Drigger and Time Controlled MTC Feature | ZTE | imported from 3GU |
S1‑111063 | WID for study on usage monitoring control enhancement | ZTE | imported from 3GU |
S1‑111064 | Discussion on MTC Offline and Triggering | Renesas Mobile Europe Ltd | imported from 3GU |
S1‑111065 | CR 22.368-0061 rev 2: Removal of ambiguity with MTC 'Offline' | Renesas Mobile Europe Ltd | imported from 3GU |
S1‑111066 | CR to 22.228 info of called party for INIPUI | Deutsche Telekom | imported from 3GU |
S1‑111067 | Charging clarifications for INIPUI | Deutsche Telekom | imported from 3GU |
S1‑111068 | Correction to the admission control for the H(e)NB | ZTE | imported from 3GU |
S1‑111069 | Correction to the admission control for the H(e)NB | ZTE | imported from 3GU |
S1‑111070 | Correction to the admission control for the H(e)NB | ZTE | imported from 3GU |
S1‑111071 | Discussion on route optimization for SIPTO | ZTE, China Mobile | imported from 3GU |
S1‑111072 | Route optimization for SIPTO | ZTE, China Mobile | imported from 3GU |
S1‑111073 | Draft LS to SA2 on route optimization for SIPTO | ZTE, China Mobile | imported from 3GU |
S1‑111074 | Clarification on the requirement for MRA activation | ZTE | imported from 3GU |
S1‑111075 | Clarification on continuity of a MRA session between (e)NBs | ZTE | imported from 3GU |
S1‑111076 | Discussion on Additional MRA Scenarios | ZTE | imported from 3GU |
S1‑111077 | Discussion on Reverse Charging for Multimedia Streams | ZTE | imported from 3GU |
S1‑111078 | Enhancement of reverse charging to specific multimedia streams | ZTE | imported from 3GU |
S1‑111079 | Non-collaboration requirements for MOSAP | Samsung Electronics | imported from 3GU |
S1‑111080 | User consent-based charging use case for MOSAP | Samsung Electronics | imported from 3GU |
S1‑111081 | UE initiated ASP requested priority traffic handling for MOSAP | Samsung Electronics | imported from 3GU |
S1‑111082 | Clarifying requirements for MTC | Samsung Electronics | imported from 3GU |
S1‑111083 | Clarification of requirements for MTC (CR) | Samsung Electronics | imported from 3GU |
S1‑111084 | Changes to description of existing use cases to include non-browser applications | InterDigital, Inc. | imported from 3GU |
S1‑111085 | New Use Case for User Authentication | InterDigital Communications, Inc. | imported from 3GU |
S1‑111086 | New use case for selection and indication of SSOauthentication mechanism | InterDigital, Communications, Inc. | imported from 3GU |
S1‑111087 | Seamless service detection, redirection and supply of credentials by a UE | InterDigital Communication, Inc. | imported from 3GU |
S1‑111088 | New use case for enabling 'Affliated Service' by subscription of the application and identity provideer services to an Operators SSO system | InterDigital Commnuications, Inc. | imported from 3GU |
S1‑111089 | CR to TR22.809: Additional Potential Requirements | Verizon Wireless | imported from 3GU |
S1‑111090 | CR to TR 22.809: Supplementary Services for Support of IP-PBX | Verizon Wireless | imported from 3GU |
S1‑111091 | IMS emergency call domain selection clarification | Alcatel-Lucent, Verizon, AT&T | imported from 3GU |
S1‑111092 | IMS emergency call domain selection clarification | Alcatel-Lucent, Verizon, AT&T | imported from 3GU |
S1‑111093 | IMS emergency call domain selection clarification | Alcatel-Lucent, Verizon, AT&T | imported from 3GU |
S1‑111094 | draft LS response to R2-112589 on LTE UE IMS emergency call support | Alcatel-Lucent | imported from 3GU |
S1‑111095 | IMS emergency call requirements for additional media types | Alcatel-Lucent, AT&T, Nokia Siemens Networks, ZTE, TeleCommunication Systems, Qualcomm, Cisco, Ericsson, Huawei, Verizon | imported from 3GU |
S1‑111096 | Introduction of new scenarios for IP addressing | Alcatel-Lucent, Nokia Siemens Networks | imported from 3GU |
S1‑111097 | Characteristics of offline triggering | Alcatel-Lucent | imported from 3GU |
S1‑111098 | Discussion Paper for Study on Smart Mobile Content Delivery in 3GPP Networks | Huawei | imported from 3GU |
S1‑111099 | Defining an offline MTC device | Alcatel-Lucent | imported from 3GU |
S1‑111100 | Study on Smart Mobile Content Delivery in 3GPP Networks | Huawei | imported from 3GU |
S1‑111101 | Proposed Use Case for the TR 22.895 | Intel | imported from 3GU |
S1‑111102 | Contribution to TR 22.817 v0.4.0 UICC/USIM enhancements Study UICC Application upgrade - Section 5 | Intel | imported from 3GU |
S1‑111103 | MODAI Use Case: Load Condition and UE Type Distinction | Qualcomm Inc. | imported from 3GU |
S1‑111104 | Data application impact on real UMTS networks | Qualcomm Inc. | imported from 3GU |
S1‑111105 | discussion on FW traversal in IMS | China Mobile | imported from 3GU |
S1‑111106 | CR for FW traversal in IMS | China Mobile | imported from 3GU |
S1‑111107 | Comments on alternatives to E.164 | Orange | imported from 3GU |
S1‑111108 | Potential Requirements for "Always online" mobile data applications | China Mobile | imported from 3GU |
S1‑111109 | Potential Requirements for the Transmission of small data packet use case | China Mobile | imported from 3GU |
S1‑111110 | Potential Requirements of the collaboration between the radio access network and the core network | China Mobile | imported from 3GU |
S1‑111111 | CR to TS22.368 - Addressing | Orange | imported from 3GU |
S1‑111112 | Proposed Reply LS on Remote Party Restrictions for IUT | Orange | imported from 3GU |
S1‑111113 | Clarifications on Requirements to Fixed Mobile Convergence Building Block 3 | Orange | imported from 3GU |
S1‑111114 | One number and Unified Voice Mail use cases to add to IMS use cases | Orange | imported from 3GU |
S1‑111115 | Additional use cases for H(e)NB RAN Sharing scenario | Orange | imported from 3GU |
S1‑111116 | PCR to 22.888: Potential requirements for Communications via MTC Gateway Device | Panasonic, ITRI, ZTE, China Mobile | imported from 3GU |
S1‑111117 | PCR to 22.888: Monitoring via MTC Gateway Device | ITRI | imported from 3GU |
S1‑111118 | Clarification on applicability of EAB | Vodafone | imported from 3GU |
S1‑111119 | Way forward on INIPUI | Ericsson, Vodafone | imported from 3GU |
S1‑111120 | Alignment of the Transparent end-to-end packet-switched streaming service | Ericsson | imported from 3GU |
S1‑111121 | Alignment of the Transparent end-to-end packet-switched streaming service stage 1 specification with stage 3 implementations | Ericsson | imported from 3GU |
S1‑111122 | Addition of Anonymous Call Rejection as a SS | Alcatel-Lucent | imported from 3GU |
S1‑111123 | Addition of Anonymous Call Rejection to 22.004 as a SS | Alcatel-Lucent | imported from 3GU |
S1‑111124 | Clarification on MTC Feature and subscription | Huawei | imported from 3GU |
S1‑111125 | Alignment for UICC Low priority information | Huawei | imported from 3GU |
S1‑111126 | Clarification for SIPTO policy | Huawei | imported from 3GU |
S1‑111127 | Update of sections 2 and 3 of TR 22.896 | NEC | imported from 3GU |
S1‑111128 | Use case for TR 22.896 on MRA - LIPA mobility | NEC | imported from 3GU |
S1‑111129 | Proposal for section 4 (General Description) of TR 22.896 | NEC | imported from 3GU |
S1‑111130 | Proposal for section 7 (Conclusion) of TR 22.896 | NEC | imported from 3GU |
S1‑111131 | Continuity of Data Sessions to Local Networks | NEC | imported from 3GU |
S1‑111132 | Clarifications on SIPTO offload | NEC | imported from 3GU |
S1‑111133 | CR to TS 22.228: VINE Requirements | Vodafone | imported from 3GU |
S1‑111134 | CR to TR 22.809: VINE requirements update | Vodafone | imported from 3GU |
S1‑111135 | CR to TS 22.228: New annex for VINE reference model | Tatara Systems | imported from 3GU |
S1‑111136 | CR to TS 22.228: New annex for VINE use cases | Tatara Systems | imported from 3GU |
S1‑111137 | Discussion on MTC device identifier | Neustar | imported from 3GU |
S1‑111138 | Potential Requirements for Always online mobile data applications | Huwei, China Mobile, Intel | imported from 3GU |
S1‑111139 | Potential Requirements for the Transmission of small data packet use case | Huawei, China Mobile, Intel, China Telecom | imported from 3GU |
S1‑111140 | Adding several MTC features applicable in general for all communication scenario to 22.101 | Nokia Siemens Networks | imported from 3GU |
S1‑111141 | Frequent network access attempts from mobile data applications after failure | Huawei | imported from 3GU |
S1‑111142 | Removing MTC features generally applicable from 22.368 | Nokia Siemens Networks | imported from 3GU |
S1‑111143 | Identifying change in behaviour of mobile data applications | Huawei | imported from 3GU |
S1‑111144 | Discussion of applicability of Rel-11 22.368 MTC Features | Nokia Siemens Networks | imported from 3GU |
S1‑111145 | draft Reply LS on remote party restrictions for IUT | Huawei | imported from 3GU |
S1‑111146 | user identity acknowledge for SSO usage | Huawei | imported from 3GU |
S1‑111147 | Use case for MODAI | Intel | imported from 3GU |
S1‑111148 | Use case for MODAI | Intel | imported from 3GU |
S1‑111149 | Data relating to the presence of small packets over 3GPP access | Intel | imported from 3GU |
S1‑111150 | Study item on converged mobile broadcast support for LTE | Intel | imported from 3GU |
S1‑111151 | Toward Convergence of 3GPP eMBMS and Mobile Broadcasting Standards | Intel | imported from 3GU |
S1‑111152 | Discussion of EAB in MTC | Intel | imported from 3GU |
S1‑111153 | clarification for MTC identifier | Intel | imported from 3GU |
S1‑111154 | Restriction of the use of a USIM to specific MEs/MTC Devices | Ericsson, ST-Ericsson | imported from 3GU |
S1‑111155 | Service experience correction for level of interruption of IP connectivity to the residential/enterprise IP network | RIM | Revised to S1-111216 |
S1‑111156 | Discussion Paper H(e)NB : Additional use cases for H(e)NB RAN Sharing scenario | Orange | Withdrawn |
S1‑111157 | LS out : Proposed reply LS to ETSI SCP | Orange | Withdrawn, uploaded as 294 |
S1‑111158 | One number and Unified Voice Mail use cases to add to IMS use cases | Orange | Revised to S1-111392 |
S1‑111159 | Discussion on MTC Offline and Triggering | Renesas Mobile Europe Ltd, Samsung Electronics | Handled by M2M |
S1‑111160 | LS on PWS security | C1-111150 | Noted without presentation. |
S1‑111161 | LS on MTC USIM requirements for Release 10 | C1-111155 | See also SA3's LS in S1-111183. |
S1‑111162 | Reply LS on LS reply on service identification for charging purposes in case of IMS Roaming (S1-110431) | C1-111530 | Noted without presentation. |
S1‑111163 | LS Response to LS on eCall AT command | GP-110011 | Noted without presentation. |
S1‑111164 | LS on Release 10 NIMTC Work | GP-110382 | Noted. |
S1‑111165 | Reply LS on Cell Broadcast Service for MOCN Shared Network | GP-110501 | Noted without presentation |
S1‑111166 | LS on Management of MOCN supporting MSs/UEs in GERAN | GP-110518 | Noted without presentation |
S1‑111167 | LS on MDT configuration with user consent | R2-111714 | Noted. |
S1‑111168 | Reply to C1-110757 on Provision of the RRC establishment cause "Delay tolerant" | R2-111726 | Noted. |
S1‑111169 | Reply LS on LTE UE IMS emergency call support in Rel-9 and later | R2-112589 | Handled by CIMS |
S1‑111170 | Reply LS on Cell Broadcast Service for MOCN Shared Network | R3-111010 | Noted without presentation |
S1‑111171 | LS on partial success of Write Replace Warning Request for ETWS | R3-111084 | Noted without presentation |
S1‑111172 | LS on LTE UE IMS emergency call support in Rel-9 and later | R5-110716 | Handled by CIMS |
S1‑111173 | Reply LS on Requirements and Architecture issues of PSS service | S2-110943 | Noted without presentation. |
S1‑111174 | Reply LS on Simultaneous registration of a single private identity from different UEs | S2-111153 | Handled by CIMS |
S1‑111175 | LS on MTC SIMTC Planning and Prioritization | S2-111219 | Noted, this is superseded by S1-111192. |
S1‑111176 | Reply LS on “Quality of Service requirements and objectives for wireless access systems” | S2-111261 | Noted without presentation |
S1‑111177 | LS on MTC Service Requirements | S2-111263 | Handled by M2M |
S1‑111178 | LS response on F2F BBF and 3GPP joint meeting | S2-111265 | Obsolete, superseded by S1-111194. |
S1‑111179 | Reply LS on Cell Broadcast Service for MOCN Shared Network | S2-111272 | Noted without presentation |
S1‑111180 | LS on HPLMN aspects VPLMN Autonomous CSG Roaming | S2-112180 | Draft answer to be provided by Telecom Italia in S1-111211. |
S1‑111181 | Reply LS on Network Sharing | S2-112197 | Noted without presentation |
S1‑111182 | LS on remote party restrictions for IUT | S2-112212 | Postponed to next meeting. |
S1‑111183 | Reply LS on MTC USIM requirements for Release 10 | S3-110556 | To be handled in the MTC SWG. |
S1‑111184 | LS on potential co-operation between 3GPP work on MTC security and ETSI M2M | S3-110558 | Noted. |
S1‑111185 | Reply LS on Requirements and Architecture issues of PSS service | S3-110572 | Noted without presentation. |
S1‑111186 | Reply LS on Liaison Statement on security issues of PSS service | S4-110335 | Noted without presentation. |
S1‑111187 | Reply LS on Requirements and Architecture issues of PSS service | S4 -110498 | Noted without presentation. |
S1‑111188 | LS on PSS HTTP-based Download and Streaming and 3GP-DASH QoS management | S4-110551 | Noted without presentation. |
S1‑111189 | LS on MTC charging requirements for Release 10 | S5-111360 | Noted, no impact foreseen in MTC SWG. |
S1‑111190 | LS on MDT User consent handling | S5-111525 | See S1-111167. |
S1‑111191 | Liaison Statement on new Work Item for eUICC | SCP(11)0147r1 | More discussions to take place at the ad-hoc group. |
S1‑111192 | Reply LS on MTC Planning and Prioritization | SP-110218 | Agreed, to be followed in the MTC SWG. |
S1‑111193 | LS on Non-Access Stratum (NAS) configuration parameters for NIMTC | SP-110220 | To be handled in the MTC SWG. |
S1‑111194 | LS on agenda and dates for F2F BBF and 3GPP workshop | SP-110231 | Noted. |
S1‑111195 | LS on Network Sharing | SP-110234 | Noted. |
S1‑111196 | CR 22.368-0061 rev 2: Removal of ambiguity with MTC 'Offline' | Renesas Mobile Europe Ltd, Samsung Electronics | Handled by M2M |
S1‑111197 | Correction of NIMTC requirements to define the precedence for NAS configuration parameters in case they are defined in the device and in the USIM+ | Safran Morpho | Handled by M2M |
S1‑111198 | Scenarios for Inter-UE transfer remote party privacy | InterDigital | Handled by CIMS |
S1‑111199 | Discussion on route optimization for SIPTO | ZTE, China Mobile | See related CR in S1-111200. |
S1‑111200 | Avoiding deterioration of user experience for SIPTO | ZTE, China Mobile | Noted. |
S1‑111201 | Draft LS to SA2 on route optimization for SIPTO | ZTE, China Mobile | Noted. |
S1‑111202 | IMS emergency call requirements for additional media types | Alcatel-Lucent, AT&T, Nokia Siemens Networks, ZTE, TeleCommunication Systems, Qualcomm, Cisco, Ericsson, Huawei, Verizon, Sprint | Revised to S1-111206 |
S1‑111203 | Introduction of new scenarios for IP addressing | Alcatel-Lucent, Nokia Siemens Networks | Handled by M2M |
S1‑111204 | Various ways to access the Local Network from Macro Cellular | Alcatel-Lucent, AT&T | Handled by CSN |
S1‑111205 | Additional Potential VINE requirements | Alcatel-Lucent | Handled by VINE |
S1‑111206 | IMS emergency call requirements for additional media types | Alcatel-Lucent, AT&T, Nokia Siemens Networks, ZTE, TeleCommunication Systems, Qualcomm, Cisco, Ericsson, Huawei, Verizon, Sprint | Revised to S1-111410 |
S1‑111207 | Introduction of Non-Voice Emergency Services (NOVES) | AT&T, Alcatel-Lucent | Revised to S1-111428 |
S1‑111208 | Removal of Requirement for UDC Data Model | NSN | Agreed. |
S1‑111209 | Removal of Requirement for UDC Data Model | NSN | Agreed. |
S1‑111210 | Study item on converged mobile broadcast support for LTE | Intel | Noted. |
S1‑111211 | Draft answer to LS in S1-111180. | Telecom Italia | Revised to S1-111420 |
S1‑111212 | LS on Clarification of type(s) of operator-controlled SSO credentials | S3-110579 | Handled by SSO |
S1‑111213 | LS on 3GPP eUICC requirements scope | C6-110260 | Handled by M2M |
S1‑111214 | WID for study on usage monitoring control enhancement | ZTE | Agreed. |
S1‑111215 | Discussion Paper for Study on Smart Mobile Content Delivery in 3GPP Networks | Huawei | See related WID in S1-111100. |
S1‑111216 | Alignment of requirement for level of interruption of IP connectivity to the residential/enterprise IP network | Research In Motion, Verizon Wireless | Withdrawn. |
S1‑111217 | Reply LS on MTC USIM requirements for Release 10 | C6-110254 | Noted. |
S1‑111218 | Study on Smart Mobile Content Delivery in 3GPP Networks | Huawei | Withdrawn. |
S1‑111219 | Addition of Anonymous Call Rejection as a SS | Alcatel-Lucent, Ericsson | Revised to S1-111405 |
S1‑111220 | MOSAP Presentation | MOSAP SWG Chair (Vojislav Vucetic, Cisco Systems) | Noted. |
S1‑111221 | MOSAP Report | MOSAP SWG Chair | Approved. |
S1‑111222 | MOSAP Agenda | MOSAP SWG Chair | Handled by MOSAP |
S1‑111223 | User consent-based charging use case for MOSAP | Samsung | Agreed. |
S1‑111224 | Non-collaboration requirements for MOSAP | Samsung | Revised to S1-111412 |
S1‑111225 | - | MOSAP SWG | Withdrawn |
S1‑111226 | CDN requirements for MOSAP | Huawei | Handled by MOSAP |
S1‑111227 | CDN requirements for MOSAP | Huawei | Revised to S1-111426 |
S1‑111228 | Withdrawn | - | Withdrawn |
S1‑111229 | Withdrawn | - | Withdrawn |
S1‑111230 | LS to SA3 on Operator credentials | SSO SWG | Revised to S1-111231. |
S1‑111231 | LS to SA3 on Operator credentials | SSO SWG | Revised to S1-111232 |
S1‑111232 | LS to SA3 on Operator credentials | SSO SWG | Agreed. |
S1‑111233 | Not used | - | Not used |
S1‑111234 | Not used | - | Not used |
S1‑111235 | Not used | - | Not used |
S1‑111236 | Not used | - | Not used |
S1‑111237 | Not used | - | Not used |
S1‑111238 | Not used | - | Not used |
S1‑111239 | Not used | - | Not used |
S1‑111240 | SSO Presentation | SSO SWG Chair (Chris Wallace, InterDigital Communications) | Noted. |
S1‑111241 | SSO Report | SSO SWG Chair | Handled by SSO |
S1‑111242 | SSO Agenda | SSO SWG Chair | Handled by SSO |
S1‑111243 | TR 22.895 V0.1.0 on Study on Service aspects of integration of Single Sign-On (SSO) frameworks with 3GPP operator-controlled resources and mechanisms | Rapporteur | Revised to S1-111258 |
S1‑111244 | Addition of SSO Provider Definition | China Mobile, InterDigital | Handled by SSO |
S1‑111245 | Editorial fix for the TR 22.895 | Alcatel-Lucent, AT&T | Handled by SSO |
S1‑111246 | Update of Non-Web Service Access Use Case of TR 22.895 | China Mobile, Motorola Mobility | Handled by SSO |
S1‑111247 | New Use Case for User Authentication | InterDigital, Inc., Sagem-Orga | Handled by SSO |
S1‑111248 | New Use Case for Selection and Indication of SSO Authentication Mechanism | InterDigital, Inc., Sagem-Orga | Handled by SSO |
S1‑111249 | Seamless Service Detection, Redirection and Supply of Credentials by a UE | InterDigital, Inc. | Handled by SSO |
S1‑111250 | Proposed Use Case for the TR 22.895 | Intel Corporation (UK) Ldt. | Handled by SSO |
S1‑111251 | Addition of SSO Provider Definition | China Mobile, InterDigital | Handled by SSO |
S1‑111252 | FS_SSO_int: Use case for SSO and some editorial changes of SSO TR | Motorola Mobility | Handled by SSO |
S1‑111253 | Changes to description of existing use cases to include non-browser | InterDigital, Inc., Sagem-Orga | Handled by SSO |
S1‑111254 | user identity acknowledge for SSO usage | Huawei | Handled by SSO |
S1‑111255 | Seamless Service Detection, Redirection and Supply of Credentials by a UE | InterDigital, Inc. | Handled by SSO |
S1‑111256 | Proposed Use Case for the TR 22.895 | Intel Corporation (UK) Ldt. | Handled by SSO |
S1‑111257 | LS to SA3 on Operator credentials | SSO SWG | Revised to S1-111259 |
S1‑111258 | TR 22.895 V0.2.0 on Study on Service aspects of integration of Single Sign-On (SSO) frameworks with 3GPP operator-controlled resources and mechanisms | Rapporteur | Revised to S1-111218 |
S1‑111259 | LS to SA3 on Operator credentials | SSO SWG | Revised to S1-111230 |
S1‑111260 | Presentation of CSN | CSN SWG Chair (Joerg Swetina, NEC) | Noted. |
S1‑111261 | CSN Report | CSN Chair | Approved. |
S1‑111262 | CSN Agenda | - | Handled by CSN |
S1‑111263 | Proposal for section 4 (General Description) of TR 22.896 | NEC | Handled by CSN |
S1‑111264 | Use case for TR 22.896 on MRA – LIPA mobility | NEC | Handled by CSN |
S1‑111265 | Discussion on Additional MRA Scenarios | ZTE | Handled by CSN |
S1‑111266 | Proposal for section 7 (Conclusion) of TR 22.896 | NEC | Handled by CSN |
S1‑111267 | LS to SA2 on Continuity of Data Sessions to Local Networks | CSN SWG | Agreed. |
S1‑111268 | Not used | - | Not used |
S1‑111269 | Not used | - | Not used |
S1‑111270 | Not used | - | Not used |
S1‑111271 | Not used | - | Not used |
S1‑111272 | Cover page for TR on CSN | - | Noted, no need since the TR is not submitted to SA anymore. |
S1‑111273 | LS to SA2 (Cc SA) on Continuity of Data Sessions to Local Networks | CSN SWG | Revised to S1-111267 |
S1‑111274 | TR 22.896 V0.2.0 on Study on Continuity of Data Sessions to Local Networks | Rapporteur | Revised to S1-111416 |
S1‑111275 | MODAI Presentation | MODAI SWG Chair (Amar Deol, Huawei) | Noted, |
S1‑111276 | MODAI Report | MODAI Chair | Approved. |
S1‑111277 | MODAI Agenda | Modai Chair | Handled by MODAI |
S1‑111278 | Data relating to the presence of small packets over 3GPP access | Intel | Handled by MODAI |
S1‑111279 | Potential Requirements for “Always online” mobile data applications | China Mobile, Huawei, Intel | Handled by MODAI |
S1‑111280 | Not used? | - | Handled by MODAI |
S1‑111281 | Potential Requirements for the Transmission of small data packet use case | China Mobile, China Telecommunications, Huawei, Intel | Handled by MODAI |
S1‑111282 | Use case for high frequency t start of initiating applicationsservice | China Unicom | Handled by MODAI |
S1‑111283 | MODAI use case: Mobile Data Application Distributed Denial of Service (DDoS) Attacks | Intel | Handled by MODAI |
S1‑111284 | MODAI use case: Overload issues caused by live content streaming from the Internet. | Intel | Handled by MODAI |
S1‑111285 | MODAI use case: Mobile Data Application Distributed Denial of Service (DDoS) Attacks | Intel | Handled by MODAI |
S1‑111286 | Use case for frequent start of service | China Unicom | Handled by MODAI |
S1‑111287 | Potential Requirements for “Always online” mobile data applications | China Mobile, Huawei, Intel | Handled by MODAI |
S1‑111288 | TR 22.801 V0.2.0 on Study on non-MTC Mobile Data Applications impacts (Release 11) | Rapporteur | Agreed as a basis for future contribution. |
S1‑111289 | Not used | - | Handled by RESUM |
S1‑111290 | RESUM Presentation | RESUM Ad-hoc Chair (Enrico Scarrone, Telecom Italia) | Revised to S1-111435 |
S1‑111291 | Not used | - | Handled by RESUM |
S1‑111292 | Withdrawn, corrupted file | - | Withdrawn, corrupted file |
S1‑111293 | Withdrawn, corrupted file | - | Withdrawn, corrupted file |
S1‑111294 | Not used | - | Not used |
S1‑111295 | LS on Clarification to eUICC uses cases and Requirements | 3GPP SA WG1 | Handled by RESUM |
S1‑111296 | Not used | - | Handled by RESUM |
S1‑111297 | Not used | - | Withdrawn, corrupted file |
S1‑111298 | LS to GSMA Embedded SIM Task Force (ETSI SCP, ETSI SCP REQ, SA, CT6, SA3, 3GPP2 TSG-S and 3GPP2 TSG-C) on Clarification to eUICC uses cases and Requirements | 3GPP SA WG1 | Approved. |
S1‑111299 | Not used | - | Handled by RESUM |
S1‑111300 | SIMTC Presentation | M2M SWG Chair (Toon Norp, KPN) | Noted. |
S1‑111301 | SIMTC Report | M2M SWG Chair | Approved. |
S1‑111302 | SIMTC Agenda | M2M SWG Chair | Handled by SIMTC |
S1‑111303 | Clarification of requirements for MTC | Samsung Electronics | Revised to S1-111377 |
S1‑111304 | Clarification of MTC Device management requirement | Samsung Electronics | Agreed. |
S1‑111305 | Draft LS on MTC Service Requirements | 3GPP SA WG1 | Handled by SIMTC |
S1‑111306 | Removal of Rel-10 MTC Charging requirements | Rapporteur (KPN) | Agreed. |
S1‑111307 | Correction of NIMTC requirements to define the precedence for NAS configuration parameters in case they are defined in the device and in the USIM | Sagem Orga GmbH (Morpho) | Revised to S1-111372 |
S1‑111308 | Correction of SIMTC requirements to define the precedence for NAS configuration parameters in case they are defined in the device and in the USIM | Sagem Orga GmbH (Morpho) | Revised to S1-111373 |
S1‑111309 | Deletion of requirement on MTC USIM for Release 10 | Rapporteur (KPN) | Agreed. |
S1‑111310 | Clarification on how EAB is applied in Shared Network | ZTE, Panasonic, SierraWireless | Revised to S1-111376 |
S1‑111311 | Withdrawn | - | Withdrawn |
S1‑111312 | Withdrawn | - | Withdrawn |
S1‑111313 | Adding a definition of “Offline MTC Device” and requirements for offline MTC Device Trigger | ZTE, Panasonic, KPN, Huawei, Alcatel-Lucent, Sierra Wireless, Hisilicon | Revised to S1-111417 |
S1‑111314 | Communications via MTC Gateway Device | Panasonic, ITRI, ZTE, China Mobile | Handled by SIMTC |
S1‑111315 | Additional Use Case for TR 22.988 | T-Mobile USA | Handled by SIMTC |
S1‑111316 | Additional Use Case for TR 22.988 | T-Mobile USA | Handled by SIMTC |
S1‑111317 | Requirements and Conclusion for TR 22.988 | T-Mobile USA | Handled by SIMTC |
S1‑111318 | TR 22.988 V0.5.0 on Study on Alternatives to E.164 for Machine-Type Communications (Release 10) | Rapporteur | Revised to S1-111380 |
S1‑111319 | 22.888 V0.5.0 on Study on Enhancements for MTC; | Rapporteur | Agreed as a basis for future contributions. |
S1‑111320 | Clarification on MTC User Definition | China Mobile | Handled by SIMTC |
S1‑111321 | Clarification on MTC Communication Scenarios of TS 22.368 | China Mobile | Handled by SIMTC |
S1‑111322 | New Requirements for MTC Monitoring Feature | China Mobile | Handled by SIMTC |
S1‑111323 | Discussion on MTC Offline and Triggering | Renesas Mobile Europe Ltd, Telefon LM AB Ericsson, ST-Ericsson SA, | Revised to S1-111419 |
S1‑111324 | Consolidation of M2M Requirements | NSN | Noted. E-mail discussions are encouraged. |
S1‑111325 | MTC Device Trigger and Time Controlled MTC Feature | ZTE, Panasonic | Revised to S1-111374 |
S1‑111326 | Introduction of new scenarios for IP addressing | Alcatel-Lucent, Nokia Siemens Networks, Ericsson, ST-Ericsson | Revised to S1-111379 |
S1‑111327 | Clarification on MTC User | China Mobile | Revised to S1-111375 |
S1‑111328 | Clarification of MTC identifier to aligning it with MTC Group feature | Intel | Agreed. |
S1‑111329 | New Requirements for MTC Monitoring Feature | China Mobile | Agreed. |
S1‑111330 | CIMS Report | C-IMS SWG Chair (Betsy Covell, Alcatel-Lucent) | Approved. |
S1‑111331 | CIMS Presentation | C-IMS SWG Chair (Betsy Covell, Alcatel-Lucent) | Noted. |
S1‑111332 | CIMS Agenda | - | Handled by CIMS |
S1‑111333 | FW traversal support in Common IMS | China Mobile, Huawei, ZTE, AcmePacket | Revised to S1-111354 |
S1‑111334 | LS to SA2 (Cc SA3, CT1) on Simultaneous registration of a single private identity from different UEs | CIMS SWG | Agreed. |
S1‑111335 | [Draft] LS on remote party restrictions for IUT | 3GPP SA WG1 | Revised to S1-111437 |
S1‑111336 | IMS emergency call clarifications | Alcatel-Lucent, Verizon, AT&T | Handled by CIMS |
S1‑111337 | IMS emergency call clarifications | Alcatel-Lucent, Verizon, AT&T | Revised to S1-111352 |
S1‑111338 | IMS emergency call clarifications | Alcatel-Lucent, Verizon, AT&T | Revised to S1-111353 |
S1‑111339 | draft LS on Reply LS on LTE UE IMS emergency call support in Rel-9 and later | 3GPP SA WG1 | Handled by CIMS |
S1‑111340 | TR 22.894 V1.2.0 on Feasibility Study on IMS Network-Independent Public User Identities | Rapporteur | Revised to S1-111422 |
S1‑111341 | FS_INIPUI: Further Clarification of the Business Relationships | Vodafone | Handled by CIMS |
S1‑111342 | FS_INIPUI: Updates to Potential Requirements | Vodafone | Handled by CIMS |
S1‑111343 | Cover page for TR 22.894 | Rapporteur | Revised to S1-111423 |
S1‑111344 | LS on “IMS Network-Independent Public User Identities” | 3GPP SA WG1 | Handled by CIMS |
S1‑111345 | Draft Work Item for IMS Network-Independent Public User Identities | Vodafone | Revised to S1-111411 |
S1‑111346 | IMS Network-Independent Public User Identities | Vodafone | Agreed. |
S1‑111347 | Withdrawn | - | Handled by CIMS |
S1‑111348 | IMS emergency call clarifications | Alcatel-Lucent, Verizon, AT&T | Revised to S1-111351 |
S1‑111349 | LS on Reply LS on LTE UE IMS emergency call support in Rel-9 and later | 3GPP SA WG1 | Noted. |
S1‑111350 | LS to GSMA IWG, IREG RiLTE (Cc SA2) on “IMS Network-Independent Public User Identities” | CIMS SWG | Revised to S1-111425 |
S1‑111351 | IMS emergency call clarifications | Alcatel-Lucent, Verizon, AT&T | Noted. |
S1‑111352 | IMS emergency call clarifications | Alcatel-Lucent, Verizon, AT&T | Noted. |
S1‑111353 | IMS emergency call clarifications | Alcatel-Lucent, Verizon, AT&T | Noted. |
S1‑111354 | FW traversal support in Common IMS | China Mobile, Huawei, ZTE, AcmePacket | Agreed. |
S1‑111355 | VINE Presentation | VINE SWG Chair (Phil Brown, Tatara Systems) | Noted. |
S1‑111356 | VINE Report | VINE SWG Chair (Phil Brown, Tatara Systems) | Approved. |
S1‑111357 | VINE SWG Agenda | SWG Chair | Handled by VINE |
S1‑111358 | Revised 1357 | SWG Chair | Handled by VINE |
S1‑111359 | Revised 1089 | Verizon, Vodafone, Cisco, NSN, ALU | Handled by VINE |
S1‑111360 | Revised 1090 | Verizon, Cisco | Handled by VINE |
S1‑111361 | Revised 1134 | Vodafone | Handled by VINE |
S1‑111362 | Revised 1218 | Orange | Handled by VINE |
S1‑111363 | Revised 1133 | Vodafone | Handled by VINE |
S1‑111364 | VINE SWG Agenda (final) | SWG Chair | Handled by VINE |
S1‑111365 | Additional Potential Requirements | Verizon Wireless, Vodafone, Cisco, Nokia Siemens Networks, Alcatel Lucent | Revised to S1-111395 |
S1‑111366 | Supplementary Services for Support of Enterprise IP-PBX | Verizon Wireless, Cisco | Revised to S1-111393 |
S1‑111367 | Clarification of VINE requirements | Vodafone | Agreed. |
S1‑111368 | VINE | - | Handled by VINE |
S1‑111369 | VINE | - | Handled by VINE |
S1‑111370 | Draft LS to SA2 on MTC Service Requirements | KPN/SA1 | Revised to S1-111378 |
S1‑111371 | Use case and business arguments for Offline Triggering | KPN, Vodafone, China Mobile, Verizon, Telecom Italia, Sierra Wireless | Revised to S1-111383 |
S1‑111372 | Correction of NIMTC requirements to define the precedence for NAS configuration parameters in case they are defined in the device and in the USIM | Sagem Orga GmbH (Morpho) | Agreed. |
S1‑111373 | Correction of SIMTC requirements to define the precedence for NAS configuration parameters in case they are defined in the device and in the USIM | Sagem Orga GmbH (Morpho) | Agreed. |
S1‑111374 | MTC Device Trigger and Time Controlled MTC Feature | ZTE, Panasonic | Agreed. |
S1‑111375 | Clarification on MTC User | China Mobile | Agreed. |
S1‑111376 | Clarification on how EAB is applied in Shared Network | ZTE, Panasonic, SierraWireless | Agreed. |
S1‑111377 | Clarification of requirements for MTC | Samsung Electronics | Agreed. |
S1‑111378 | Draft LS to SA2 on MTC Service Requirements | KPN/SA1 | Revised to S1-111382 |
S1‑111379 | Introduction of new scenarios for IP addressing | Alcatel-Lucent, Nokia Siemens Networks, Ericsson, ST-Ericsson | Agreed. |
S1‑111380 | TR 22.988 V0.5.0 on Study on Alternatives to E.164 for Machine-Type Communications (Release 10) | Rapporteur | Agreed as a basis for future contributions. |
S1‑111381 | Proposed response to Q.4 of SA2's LS in S1-111177. | KDDI | Noted. |
S1‑111382 | Draft LS to SA2 on MTC Service Requirements | KPN/SA1 | Revised to S1-111384 |
S1‑111383 | Use case and business arguments for Offline Triggering (Q4) | KPN, Vodafone, China Mobile, Verizon, Telecom Italia, Sierra Wireless | Agreed to be attached to the LS in zx382. |
S1‑111384 | Draft LS to SA2 on MTC Service Requirements | KPN/SA1 | Agreed. |
S1‑111385 | Not used | - | Not used |
S1‑111386 | Not used | - | Not used |
S1‑111387 | Not used | - | Not used |
S1‑111388 | Not used | - | Not used |
S1‑111389 | Not used | - | Not used |
S1‑111390 | New annex for VINE reference model | Tatara Systems, Verizon Wireless | Agreed. |
S1‑111391 | Voice Interworking with Enterprise IP-PBX (VINE) Requirements | Vodafone, Verizon Wireless, Cisco, Nokia Siemens Networks, Alcatel Lucent, Tatara Systems | Revised to S1-111396 |
S1‑111392 | One number and Unified Voice Mail use cases to add to IMS use in VINE TR | Orange | Revised to S1-111394 |
S1‑111393 | Supplementary Services for Support of Enterprise IP-PBX | Verizon Wireless, Cisco | Agreed. |
S1‑111394 | One number and Unified Voice Mail use cases to add to IMS use in VINE TR | Orange | Agreed. |
S1‑111395 | Additional Potential Requirements | Verizon Wireless, Vodafone, Cisco, Nokia Siemens Networks, Alcatel Lucent | Agreed. |
S1‑111396 | Voice Interworking with Enterprise IP-PBX (VINE) Requirements | Vodafone, Verizon Wireless, Cisco, Nokia Siemens Networks, Alcatel Lucent, Tatara Systems | Agreed. |
S1‑111397 | VINE | - | Not used |
S1‑111398 | VINE | - | Not used |
S1‑111399 | VINE | - | Not used |
S1‑111400 | Toward Convergence of 3GPP eMBMS and Mobile Broadcasting Standards | Intel | Noted |
S1‑111401 | Correction to the admission control for the H(e)NB | ZTE | Agreed. |
S1‑111402 | Correction to the admission control for the H(e)NB | ZTE | Agreed. |
S1‑111403 | Correction to the admission control for the H(e)NB | ZTE | Agreed. |
S1‑111404 | Alignment of the Transparent end-to-end packet-switched streaming service | Ericsson | Agreed. |
S1‑111405 | Addition of Anonymous Call Rejection as a SS | Alcatel-Lucent, Ericsson | Revised to S1-111429 |
S1‑111406 | Addition of Anonymous Call Rejection as a SS | Alcatel-Lucent, Ericsson | Withdrawn, covered in Rel-11 by S1-111418. |
S1‑111407 | Addition of Anonymous Call Rejection as a SS | Ericsson, Alcatel-Lucent | Agreed. |
S1‑111408 | Addition of Anonymous Call Rejection as a SS | Ericsson, Alcatel-Lucent | Agreed. |
S1‑111409 | Clarifications on Requirements to Fixed Mobile Convergence -Building Block 3 | Orange | Revised to S1-111421 |
S1‑111410 | IMS emergency call requirements for additional media types | Alcatel-Lucent, AT&T, Nokia Siemens Networks, ZTE, TeleCommunication Systems, Qualcomm, Cisco, Ericsson, Huawei, Verizon, Sprint | Agreed. |
S1‑111411 | WID on IMS Network-Independent Public User Identities | Vodafone | Revised to S1-111424 |
S1‑111412 | Non-collaboration requirements for MOSAP | Samsung | Agreed. |
S1‑111413 | Priority treatment for Network Management functions | Telcordia Technologies, National Communications System, AT&T | Agreed. |
S1‑111414 | Clarification of Priority Information | Telcordia Technologies, National Communications System | Agreed. |
S1‑111415 | Clarifications on SIPTO offload | NEC | Revised to S1-111431 |
S1‑111416 | TR 22.896 V0.2.1 on Study on Continuity of Data Sessions to Local Networks | Rapporteur | Revised to S1-111430 |
S1‑111417 | Adding a definition of “Offline MTC Device” and requirements for offline MTC Device Trigger | ZTE, Panasonic, KPN, Alcatel-Lucent, Sierra Wireless, China Mobile | Noted. |
S1‑111418 | Addition of Anonymous Call Rejection as a SS | Ericsson, Alcatel-Lucent | Revised to S1-111433 |
S1‑111419 | Discussion on MTC Offline and Triggering | Renesas ,Ericsson, ST-Ericsson, Samsung Hitachi ,InterDigital RIM, Telefónica., KDDI, NTT DOCOMO, Nokia Siemens Networks, Nokia ,Sprint, Fujitsu, China Unicom | Noted. |
S1‑111420 | LS to SA2 on HPLMN aspects VPLMN Autonomous CSG Roaming | SA1/Telecom Italia | Agreed. |
S1‑111421 | Clarifications on Requirements to Fixed Mobile Convergence -Building Block 3 | Orange | Withdrawn after off-line discussions. |
S1‑111422 | TR 22.894 V1.2.0 on Feasibility Study on IMS Network-Independent Public User Identities | Rapporteur | Agreed to be sent to SA for approval. |
S1‑111423 | Cover page for TR 22.894 | Rapporteur | Agreed. |
S1‑111424 | WID on IMS Network-Independent Public User Identities | Vodafone | Agreed. |
S1‑111425 | LS to GSMA IWG, GSMA IREG RILTE (Cc SA2) on “IMS Network-Independent Public User Identities” | SA1 | Agreed. |
S1‑111426 | CDN requirements for MOSAP | Huawei | Noted/postponed to next meeting. |
S1‑111427 | TR 22.895 V0.2.0 on Study on Service aspects of integration of Single Sign-On (SSO) frameworks with 3GPP operator-controlled resources and mechanisms | Rapporteur | Agreed as a basis for future contributions. |
S1‑111428 | Introduction of Non-Voice Emergency Services (NOVES) | AT&T, Alcatel-Lucent | Agreed. |
S1‑111429 | Addition of Anonymous Call Rejection as a SS | Alcatel-Lucent, Ericsson | Revised to S1-111434 |
S1‑111430 | TR 22.896 V0.2.2 on Study on Continuity of Data Sessions to Local Networks | Rapporteur | Agreed as a basis for future contributions. |
S1‑111431 | Clarifications on SIPTO offload | NEC | Noted, no consensus in SA1. |
S1‑111432 | Removal of PBX integration requirements | Deutsche Telekom, Vodafone | Agreed. |
S1‑111433 | Addition of Anonymous Call Rejection as a SS | Ericsson, Alcatel-Lucent | Agreed. |
S1‑111434 | Addition of Anonymous Call Rejection as a SS | Alcatel-Lucent, Ericsson | Agreed. |
S1‑111435 | RESUM Presentation | RESUM Ad-hoc Chair (Enrico Scarrone, Telecom Italia) | Noted. |
S1‑111436 | Proposed Update to the MOSAP WID for CDN | MOSAP | Noted, comments invited between now and the next meeting. |
S1‑111437 | [Draft] LS on remote party restrictions for IUT | 3GPP SA WG1 | Revised to S1-111438 |
S1‑111438 | Draft LS to SA2 on remote party restrictions for IUT | 3GPP SA WG1 | Noted. |
page generated from database: 2024-07-20 12:15:34