3GPP TDocs (written contributions) at meeting
Meeting: S1-19 - 2003-01-20 to 2003-01-24, San Francisco
meeting id: S1-19 (click id for more info on this meeting)Click on the Tdoc to open its file.
| TDoc | Title | Source | Remarks |
|---|---|---|---|
| S1‑022390 | - | - | - |
| S1‑030001 | Draft Agenda Version A – 06/01/2003 | SA1 Chairman/MCC | - |
| S1‑030002 | - | - | - |
| S1‑030003 | TITLE | SOURCE | imported from 3GU |
| S1‑030004 | LS on MBMS requirements | TSG GERAN (WG2) | imported from 3GU |
| S1‑030005 | LS on Use of E164 numbers for emerging mobile systems | CN WG4 | imported from 3GU |
| S1‑030006 | LS on clarification of User Data Management requirements | CN5 | imported from 3GU |
| S1‑030007 | LS on SS barring for SMS transfer over GPRS | TSG CN | imported from 3GU |
| S1‑030008 | Reply on Reply on Requirement for standardizing a Transcoding interface | SA2 | imported from 3GU |
| S1‑030009 | LS on management and regulatory requirements for Presence service | SA2 | imported from 3GU |
| S1‑030010 | LS on priorities for the support of PS based services | SA2 | imported from 3GU |
| S1‑030011 | Requirement to Allow Access to IMS by Means of SIM in 3G UEs | SA2 | imported from 3GU |
| S1‑030012 | Final response to LS on "Procedure for specifying UMTS QoS parameters per application" | SA4 | imported from 3GU |
| S1‑030013 | Liaison Statement on Additional Tags for MMS SMIL | SA4 | imported from 3GU |
| S1‑030014 | LS on “Work Item Description PSS Rel-6” | SA4 | imported from 3GU |
| S1‑030015 | Liaison Statement on Entities of the mobile system | SA5 | imported from 3GU |
| S1‑030016 | Reply LS on ‘New requirements about functionality to make subscription to different domains independent or linked based on operator decision’ | SA5 | imported from 3GU |
| S1‑030017 | [D1]LS on Preservation of PDP Context | SA5 | imported from 3GU |
| S1‑030018 | Reply LS on Indication of call termination as a result of IST operation | SA5 | imported from 3GU |
| S1‑030019 | LS – Identification of a Directory Number in MMS | T2 | imported from 3GU |
| S1‑030020 | LS on MM7 functionality enhancements requested by GSMA SERG | T2 | imported from 3GU |
| S1‑030021 | Re: LS on OSA support for MMS | T2 | imported from 3GU |
| S1‑030022 | LS on MMS parameter storage on the (U)SIM, and the Stage 1 Rel-4 specifications | T2 | imported from 3GU |
| S1‑030023 | LS on T2 proposal for GUP requirements- UE Data access and Backwards Compatibility | T2 | imported from 3GU |
| S1‑030024 | LS on T2 proposed changes to TS22.240 v1.0.0, Stage1 Service Requirements for GUP | T2 | imported from 3GU |
| S1‑030025 | ITU-T SG 11 and SSG Activities Concerning Priority Services | National Communications System | imported from 3GU |
| S1‑030026 | Contribution on Terminology for TR 22.800 | Telia AB | imported from 3GU |
| S1‑030027 | Clean-up of Section on Access Independence in TR 22.800 | Telia AB | imported from 3GU |
| S1‑030028 | Contribution to TR22.800 - 'Non-3GPP Access Scenario' | Telia AB | imported from 3GU |
| S1‑030029 | Contribution to TR22.800 - 'multiple IMS scenario (part one)' | Telia AB | imported from 3GU |
| S1‑030030 | Contribution to TR22.800 - 'multiple IMS scenario (part two)' | Telia AB | imported from 3GU |
| S1‑030031 | Contribution to TR22.800 - ''Interoperability scenario' | Telia AB | imported from 3GU |
| S1‑030034 | - | - | imported from 3GU |
| S1‑030035 | Source | Document for:Approval | imported from 3GU |
| S1‑030036 | Agenda of IMS SWG | Chair / Kokkola | imported from 3GU |
| S1‑030037 | New scenario input to TR22.800 – Stand Alone IMS Operator | Telia AB | imported from 3GU |
| S1‑030040 | Proposed Agenda for Priority SWG | Priority Service Feasibility Study SWG Rapporteur | imported from 3GU |
| S1‑030041 | Proposed Priority Service Guide - outline | Telcordia Technologies, National Communications System, Nortel Networks | imported from 3GU |
| S1‑030042 | Proposed Priority Service Guide - introduction | Telcordia Technologies | imported from 3GU |
| S1‑030043 | Proposed Priority Service Guide - introduction | Telcordia Technologies | imported from 3GU |
| S1‑030044 | Contribution to TR 22.800 'traditional role scenario' and 'non 3gpp access scenario' | Telecom Italia | imported from 3GU |
| S1‑030045 | Introduction of the protective mechanism of the Registration, Erasure, Activation, Deactivation and Interrogation of the Target UE. | Huawei, China Mobile | imported from 3GU |
| S1‑030046 | ·Periodic location reporting within specified period and reporting triggered by a specific event | Huawei, China Mobile | imported from 3GU |
| S1‑030047 | Introduction of the method of codeword distribution and verification procedure focused on LCS server. | Huawei, China Mobile | imported from 3GU |
| S1‑030048 | [H10] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Huawei, China Mobile | imported from 3GU |
| S1‑030049 | [H10] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Source:?[H10] | imported from 3GU |
| S1‑030050 | -Message qualification | Source:?[H10] | imported from 3GU |
| S1‑030051 | Introduction of application IMS group management in MMS | Huawei | imported from 3GU |
| S1‑030052 | Proposal for the update of GUP Work Item Description | Nokia | imported from 3GU |
| S1‑030053 | Replacement of DDF in GUP stage 1 specification | Nokia | imported from 3GU |
| S1‑030054 | Title : 3GPP GUP Component Master Concept | ALCATEL/Lucent | imported from 3GU |
| S1‑030055 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Research in Motion | imported from 3GU |
| S1‑030056 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Research in Motion | imported from 3GU |
| S1‑030057 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Research in Motion | imported from 3GU |
| S1‑030058 | Proposed Liaison Statement on Network Selection principles in 3GPP system to WLAN Interworking | SA2 | imported from 3GU |
| S1‑030059 | * The push server shall not change the push data (contents). Any transformations that the Push Server provides shall be compliant with user privacy requirements as defined in the push subscriber profile. | Research in Motion, NTT DoCoMo Inc. | imported from 3GU |
| S1‑030060 | * The push mechanism shall be efficient in the use of network resources and terminal resources. | Research in Motion, NTT DoCoMo Inc. | imported from 3GU |
| S1‑030061 | Network Selection for WLAN Interworking – requirement allocation and phasing | Motorola | imported from 3GU |
| S1‑030062 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Research in Motion, NTT DoCoMo Inc. | imported from 3GU |
| S1‑030063 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Research in Motion, NTT DoCoMo Inc. | imported from 3GU |
| S1‑030064 | - | - | imported from 3GU |
| S1‑030065 | Draft Work Item Description for Emergency Telecommunications Service feasibility study | SBC Communications | imported from 3GU |
| S1‑030066 | The format and values of this attribute shall be standardised. | NTT DoCoMo Inc. | imported from 3GU |
| S1‑030067 | Alignment of terminology used within TR 22.800 ‘IMS Subscription & Access Scenarios’ | NTT DoCoMo Inc. | imported from 3GU |
| S1‑030068 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | NTT DoCoMo | imported from 3GU |
| S1‑030069 | Synthetic Video Applications | EMC2, IAEI (represented by Vimatix) | imported from 3GU |
| S1‑030070 | [H10] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Huawei Technologies | imported from 3GU |
| S1‑030071 | [H8] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Ericsson | imported from 3GU |
| S1‑030073 | GUP Tidy-up of TS 22.240 v1.2.0 | Siemens | imported from 3GU |
| S1‑030074 | Clarification of centralised and de-centralised model | Siemens | imported from 3GU |
| S1‑030075 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Lucent Technologies | imported from 3GU |
| S1‑030076 | - | - | imported from 3GU |
| S1‑030077 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Lucent Technologies | imported from 3GU |
| S1‑030078 | Rel 99 and later Emergency calls in case on UE attached to data only network | Nokia | imported from 3GU |
| S1‑030079 | Updated scenario on Multiple terminals to TR 22.800 | Nokia | imported from 3GU |
| S1‑030080 | Note:Rejecting a request to access the UE MMI input/output capabilities by an application does not necessarily mean that it is terminated, but only that the access to the UE MMI input/output capabilities are not granted to this application. Handlin | Nokia | imported from 3GU |
| S1‑030081 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | NOKIA | imported from 3GU |
| S1‑030082 | IMS to GSM service continuity | Alcatel, Telefonica Moviles, KPN, Fujitsu, Huawei | imported from 3GU |
| S1‑030083 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Alcatel, Telefonica Moviles, KPN, Fujitsu, Huawei | imported from 3GU |
| S1‑030084 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | T-Mobile | imported from 3GU |
| S1‑030085 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | T-Mobile | imported from 3GU |
| S1‑030086 | Update to Scenario 8 of TR 22.800 v0.2.0 | T-Mobile | imported from 3GU |
| S1‑030087 | - | - | imported from 3GU |
| S1‑030088 | - | - | imported from 3GU |
| S1‑030089 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | T-Mobile | imported from 3GU |
| S1‑030090 | - | - | imported from 3GU |
| S1‑030091 | Scope of the Open Service Access Release 6 | SA1 SWG OSA | imported from 3GU |
| S1‑030092 | New scenarios for TR 22.800 about subscription relationships | Telecom Italia | imported from 3GU |
| S1‑030093 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Telia AB | imported from 3GU |
| S1‑030094 | 2.3National roaming | Telia AB | imported from 3GU |
| S1‑030095 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Telia AB | imported from 3GU |
| S1‑030097 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Telia AB | imported from 3GU |
| S1‑030098 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Telia AB | imported from 3GU |
| S1‑030099 | Contributions to the Revision of TR 22.800 scenarios | Telecom Italia | imported from 3GU |
| S1‑030100 | Proposed structure for section Summary of all scenarios of T | Telecom Italia | imported from 3GU |
| S1‑030101 | Initial conclusion on TR 22 800 | Telecom Italia | imported from 3GU |
| S1‑030103 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | SIEMENS | imported from 3GU |
| S1‑030104 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | SIEMENS | imported from 3GU |
| S1‑030105 | Some first contribution to a study on a "Generalised Privacy Capability" | Siemens AG. | imported from 3GU |
| S1‑030106 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Telia AB | imported from 3GU |
| S1‑030107 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Telia AB | imported from 3GU |
| S1‑030108 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Siemens AG | imported from 3GU |
| S1‑030110 | Contribution to the Feature Interaction TR | Siemens AG | imported from 3GU |
| S1‑030112 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Ericsson | imported from 3GU |
| S1‑030113 | Distinguishing Priority Service users vs. eMLPP users | Nortel Networks | imported from 3GU |
| S1‑030114 | R6 Service Based Local Policy : Background and rationalle | Nortel Networks | imported from 3GU |
| S1‑030115 | R6 Service Based Local Policy : Possible implementations | Nortel Networks | imported from 3GU |
| S1‑030116 | R6 Service Based Local Policy : Analysis | Nortel Networks | imported from 3GU |
| S1‑030117 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | RIM, AT&T Wireless Services | imported from 3GU |
| S1‑030118 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Siemens AG | imported from 3GU |
| S1‑030119 | - | - | imported from 3GU |
| S1‑030120 | IM CN subsystem: (IP Multimedia CN subsystem) comprises of all CN elements for the provision of IP multimedia applications over IP multimedia sessions | Nokia | imported from 3GU |
| S1‑030121 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Research In Motion | imported from 3GU |
| S1‑030122 | Proposal for Incorporating a Subset of SVG-Tiny into the MMS Specification | Research in Motion | imported from 3GU |
| S1‑030123 | It is an operator decision as to the level of interworking supported. This can be broadly grouped as: | Lucent Technologies | - |
| S1‑030124 | Additional Release 5 work needed for Policy Control and Subscription Control of Media | TSG SA | - |
| S1‑030125 | Title | Source | - |
| S1‑030126 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Telia AB | - |
| s1‑030127 | Outline for the TR on Generalised Privacy Capability | Lucent Technologies | - |
| s1‑030128 | Scope and Introduction for the Generalised Privacy Service TR | Lucent Technologies | - |
| S1‑030129 | Work Item Description for Multimedia Priority Services Feasibility Study | SBC Communications | - |
| S1‑030130 | - | - | - |
| S1‑030131 | Examples of Plazmic Media Engine | Research In Motion | - |
| S1‑030132 | - | - | - |
| S1‑030133 | Third Form Factor work status and request for additional requirements | EP SCP | - |
| S1‑030135 | Version x.y.z | Lucent Technologies | - |
| S1‑030136 | Version x.y.z | Lucent Technologies | - |
| S1‑030137 | LS on Use of E164 numbers for emerging mobile systems | SA1 | - |
| S1‑030138 | LS on control of SS barring for SMS transfer over GPRS | SA WG1 | - |
| S1‑030139 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | SA1 | - |
| S1‑030140 | DRAFT LS on Preservation of PDP context | SA1 | - |
| s1‑030141 | Proposed Response LS on Indication of call termination as a result of IST operation | SA1 | - |
| S1‑030142 | Information about the Liberty Alliance Project | Nokia, Siemens, Vodafone | - |
| S1‑030143 | - | - | - |
| S1‑030144 | LS on SIM Temperature Ranges | SA1 | - |
| S1‑030145 | Response to S1-030133 Third Form Factor work status and request for additional requirements | 3GPP TSG-SA1 | - |
| S1‑030146 | [H10] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Huawei, China Mobile | - |
| S1‑030147 | Unclear PUSH service requirements To Paul from Tommi with Love | Nokia | - |
| S1‑030148 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | NTT DoCoMo | - |
| S1‑030149 | [H10] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Huawei Technologies | - |
| S1‑030150 | LS on Rel 99 and later Emergency calls in case on UE attached to data only network | SA1 | - |
| S1‑030151 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | NOKIA | - |
| S1‑030152 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | SA1 | - |
| S1‑030153 | Agenda for the Joint S1 – T2 Meeting on MMS Rel-6 issues | Meeting convenor | - |
| S1‑030154 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Telia AB | - |
| S1‑030157 | Report of SWG GUP | SWG GUP Chair Michel Grech, Lucent Technologies | - |
| S1‑030158 | - | - | - |
| S1‑030159 | Minutes of IMS SWG | IMS SWG Chair, Tommi Kokkola | - |
| S1‑030160 | - | - | - |
| S1‑030161 | - | - | - |
| S1‑030162 | - | - | - |
| S1‑030163 | - | - | - |
| S1‑030164 | - | - | - |
| S1‑030165 | Report of SWG OSA meeting #17 | SWG OSA - Chair: Christelle Faure - Fujitsu | - |
| S1‑030166 | - | - | - |
| S1‑030167 | Report of SWG Priority | SWG Priority Chair, Jim Garrahan (Telcordia Technologies) | - |
| S1‑030168 | - | - | - |
| s1‑030169 | Report of SWG QoS | SWG WLAN Chair (Acting) Liz Daniel, Lucent Technologies | - |
| S1‑030170 | - | - | - |
| S1‑030171 | Report of SWG WLAN | SWG WLAN Chair (Acting) Mark Younge, T-Mobile USA | - |
| S1‑030172 | - | - | - |
| S1‑030174 | SWG WLAN agenda | SWG WLAN Chair | - |
| S1‑030175 | - | - | - |
| S1‑030176 | Discussion of the CR “Clarification of the charging entity WLAN in TS22.115” | Telia | - |
| s1‑030177 | Proposed Response LS on Priorities for the support of PS based services | SA1 | - |
| S1‑030178 | Scope of the Open Service Access Release 6 | SA1 SWG OSA | - |
| S1‑030180 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | T-Mobile | - |
| S1‑030181 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | T-Mobile | - |
| S1‑030182 | IM CN subsystem: (IP Multimedia CN subsystem) comprises of all CN elements for the provision of IP multimedia applications over IP multimedia sessions | Nokia | - |
| S1‑030183 | Page: 1 | Alcatel, Telefonica Moviles, KPN, Fujitsu, Huawei | - |
| S1‑030184 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Telia AB | - |
| S1‑030185 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Ericsson | - |
| S1‑030188 | Codings for storing melodies in the USIM (Release 6) | T2 | - |
| s1‑030189 | Response LS on Network Selection principles in 3GPP system to WLAN Interworking | SA1 | - |
| S1‑030190 | - | - | - |
| S1‑030191 | Update to Scenario 8 of TR 22.800 v0.2.0 | T-Mobile | - |
| S1‑030194 | New scenario for TR 22.800 | Telecom Italia | - |
| S1‑030195 | - | - | - |
| S1‑030196 | RE: LS on MM7 functionality enhancements requested by GSMA SERG | SA1 | - |
| S1‑030197 | [H10] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | T-Mobile | - |
| S1‑030198 | Liaison statement to LS on GSMA CPWP proposed additional charging requirement to be added in TS 22.115 | SA1 | - |
| S1‑030199 | Report of Joint S1-T2 SWG3 meeting on MMS Rel 6 issues | Chairman Michele Zarri | - |
| S1‑030200 | -Streaming | Telefónica Móviles, Orange, T-Mobile | - |
| S1‑030201 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Telia AB | - |
| S1‑030202 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Telia AB | - |
| S1‑030203 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Telia AB | - |
| S1‑030204 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Telia AB | - |
| S1‑030205 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Telia AB | - |
| S1‑030206 | Proposal for the update of GUP Work Item Description, revised | Nokia | - |
| S1‑030207 | Replacement of DDF in GUP stage 1 specification, revised | Nokia | - |
| S1‑030208 | - | - | - |
| S1‑030209 | - | - | - |
| S1‑030210 | LS on Update of SA2 Schedule in GUP Work Item Description | SA2 | - |
| S1‑030211 | Answer to LS on T2 proposal for GUP requirements- UE Data access and Backwards Compatibility | S1 | - |
| S1‑030212 | LS on Response to LS on T2 proposed changes to TS22.240 v1.0.0, Stage1 Service Requirements for GUP | SA1 | - |
| S1‑030213 | 3GPP GUP synchronization model | ALCATEL/Lucent | - |
| S1‑030214 | Prioritisation of work within SA2 WLAN | WLAN drafting group | - |
| s1‑030215 | It is an operator decision as to the level of interworking supported. This can be broadly grouped as: | SA1 WLAN SWG | - |
| S1‑030217 | GUP Tidy-up of TS 22.240 v1.2.0 | Siemens | - |
| S1‑030218 | LS on T2 proposal for GUP requirements- UE Data access and Backwards Compatibility | SA1 | - |
| S1‑030219 | Multimedia Priority Services WID modifications | SBC Communications | - |
| S1‑030220 | Page: 1 | Alcatel, Telefonica Moviles, KPN, Fujitsu, Huawei | - |
| S1‑030221 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | T-Mobile | - |
| S1‑030222 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | T-Mobile | - |
| S1‑030223 | - | - | - |
| S1‑030225 | Response to LS on Synthetic Video media type | SA1 | - |
| S1‑030226 | Clarification of centralised and de-centralised model | Siemens | - |
| S1‑030227 | 3GPP GUP synchronization model | ALCATEL/Lucent | - |
| S1‑030228 | Issues on the SA1 specification set | MCC | - |
| S1‑030229 | Clarification of centralised and de-centralised model | Siemens | - |
| S1‑030230 | LS on MBMS requirements | SA WG1 | - |
| S1‑030231 | UTRAN will only support Class A mode of operation | SIEMENS | - |
| S1‑030232 | UTRAN will only support Class A mode of operation | SIEMENS | - |
| S1‑030233 | - | - | - |
| S1‑030234 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Telia AB | - |
| S1‑030235 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | T-Mobile | - |
| S1‑030236 | 2.3National roaming | Telia AB | - |
| S1‑030237 | UTRAN will only support Class A mode of operation | SIEMENS | - |
| S1‑030238 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | SA1 | - |
| S1‑030239 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | SA1 | - |
| s1‑030240 | Response LS on Indication of call termination as a result of IST operation | SA1 | - |
| S1‑030241 | LS on control of SS barring for SMS transfer over GPRS | SA WG1 | - |
| S1‑030242 | LS on Use of E164 numbers for emerging mobile systems | SA1 | - |
| S1‑030244 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | NTT DoCoMo | - |
| S1‑030245 | [H10] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Huawei Technologies | - |
| S1‑030246 | LS on MBMS requirements | SA WG1 | - |
| S1‑030247 | LS on Rel 99 and later Emergency calls in case on UE attached to data only network | SA1 | - |
| S1‑030248 | [H10] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | NOKIA | - |
| S1‑030249 | * The push mechanism shall be efficient in the use of network resources and terminal resources. | Research in Motion, NTT DoCoMo Inc. | - |
| S1‑030250 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Research in Motion, NTT DoCoMo Inc. | - |
| S1‑030251 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Research in Motion | - |
| S1‑030252 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Research in Motion | - |
| S1‑030254 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Lucent Technologies | - |
| S1‑030255 | -Streaming | Ericsson | - |
| S1‑030256 | Note:Rejecting a request to access the UE MMI input/output capabilities by an application does not necessarily mean that it is terminated, but only that the access to the UE MMI input/output capabilities are not granted to this application. Handlin | Nokia | - |
| S1‑030257 | Note:Rejecting a request to access the UE MMI input/output capabilities by an application does not necessarily mean that it is terminated, but only that the access to the UE MMI input/output capabilities are not granted to this application. Handlin | Nokia | - |
| S1‑030259 | Response to S1-030133 Third Form Factor work status and request for additional requirements | 3GPP TSG-SA1 | - |
| S1‑030260 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | T-Mobile | - |
| S1‑030261 | LS on 3GPPs activities on a "Generalised Privacy Capability" | SA WG1 | - |
| S1‑030262 | - | - | - |
| S1‑030263 | -Screening of Messages | Openwave | - |
| s1‑030264 | Response LS on Priorities for the support of PS based services | SA1 | - |
| s1‑030265 | Response LS on Network Selection principles in 3GPP system to WLAN Interworking | SA1 | - |
| S1‑030267 | -Screening of Messages | Openwave | - |
| S1‑030268 | RE: LS on MM7 functionality enhancements requested by GSMA SERG | SA1 | - |
| S1‑030269 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Telia AB | - |
| S1‑030270 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Telia AB | - |
| S1‑030271 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Telia AB | - |
| S1‑030272 | Response to S1-030133 Third Form Factor work status and request for additional requirements | 3GPP TSG-SA1 | - |
| S1‑030273 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Siemens AG | - |
| S1‑030274 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | Siemens AG | - |
| S1‑030275 | LS on 3GPPs activities on a "Generalised Privacy Capability" | SA WG1 | - |
| S1‑030276 | LS on Use of E164 numbers for emerging mobile systems | SA1 | - |
| S1‑030277 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | NTT DoCoMo | - |
| S1‑030278 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | SIEMENS, NOKIA | - |
| S1‑030279 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | T-Mobile | - |
| S1‑030280 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | T-Mobile | - |
| S1‑030281 | * The push mechanism shall be efficient in the use of network resources and terminal resources. | Research in Motion, NTT DoCoMo Inc. | - |
| S1‑030282 | [H9] Enter the source of the CR. This is either (a) one or several companies or, (b) if a (sub)working group has already reviewed and agreed the CR, then list the group as the source. | T-Mobile | - |
| S1‑030283 | - | - | - |
page generated from database: 2024-04-13 13:51:47