3GPP TDocs (written contributions) at meeting
Meeting: S1-22 - 2003-10-27 to 2003-10-31, Bangkok
meeting id: S1-22 (click id for more info on this meeting)Click on the Tdoc to open its file.
| TDoc | Title | Source | Remarks |
|---|---|---|---|
| S1‑030980 | Draft Agenda Version A – 07/10/2003 | SA1 Chairman/MCC | - |
| S1‑030982 | - | - | - |
| S1‑030983 | - | - | - |
| S1‑030984 | Introduction Text for TS | 31 | - |
| S1‑030985 | Comparisons of data rates and durations | 31 | - |
| S1‑030986 | - | - | - |
| S1‑030987 | Requirements for TS to be presented for information to SA#21 | SA1 MBMS SWG Chair (3)1 | - |
| S1‑030988 | - | - | - |
| S1‑030989 | - | - | - |
| S1‑030990 | Tdoc List for the SA1 MBMS ad-hoc meeting | SA1 MBMS SWG Chair1 | - |
| S1‑030991 | Use case data | 31 | - |
| S1‑030993 | Service Profile Characteristics | Bamboo MediaCasting | - |
| S1‑030994 | - | - | - |
| S1‑030997 | Reply LS on clarification of MBMS charging issues | SA 1 | - |
| S1‑031000 | Report of MBMS SWG adhoc meeting 6-8 August 2003 | SA1 MBMS SWG Chair (3)1 | - |
| S1‑031001 | - | - | - |
| S1‑031002 | LS regarding progress of work for MBMS User Services | SA1 | - |
| S1‑031003 | - | - | - |
| S1‑031006 | Minimum requirement for simultaneous MBMS bearers | Orange PCS | - |
| S1‑031007 | [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. | Orange PCS | - |
| S1‑031008 | MBMS User Services, transport services and sessions | Bamboo, Siemens AG | - |
| S1‑031009 | - | - | - |
| S1‑031010 | Alignment of MBMS use cases and bit rates | - | - |
| S1‑031011 | Title | Source | - |
| S1‑031012 | LS on MMS for Deferred Mode IMS Messaging and SMS/MMS Interworking from WLANs. | SA2 | - |
| S1‑031013 | LS on modification of the LDR event types | TSG SA2 | - |
| S1‑031014 | Response to LS on clarification of USIM-based access to IMS | SA 2 | - |
| S1‑031015 | Liaison on Security Solutions for the Ut Reference Point | SA2 | - |
| S1‑031016 | - | - | - |
| S1‑031017 | Response to LS on clarification of USIM-based access to IMS | SA3 | - |
| S1‑031018 | LS on Profiling of RFC3325 for IMS | SA3 | - |
| S1‑031019 | LS on clarification of MBMS charging issues | SA 3 | - |
| S1‑031020 | Liaison response on LS on Protocols, Codecs and Media formats for MBMS | TSG SA WG4 | - |
| S1‑031021 | Reply to LS on Core Network Provision of separate flows for P2P and P2M radio Transmission | SA WG4 | - |
| S1‑031022 | LS on possible re-organisation of 3GPP charging specification work | SA5 | - |
| S1‑031023 | LS reply for R99 and following on video telephony | 3GPP SA5 | - |
| S1‑031024 | LS reply on sending the SGSNs MNC and MCC to the GGSN and service node | SA5 | - |
| S1‑031025 | Agenda Emergency Calls ad hoc | Ad Hoc Chair, | - |
| S1‑031026 | [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. | Siemens AG | - |
| S1‑031027 | [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. | Motorola | - |
| S1‑031028 | [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. | Motorola | - |
| S1‑031029 | [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. | Motorola | - |
| S1‑031030 | [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. | Motorola | - |
| S1‑031031 | [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‑031032 | [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‑031033 | [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‑031034 | [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‑031035 | [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‑031036 | - | - | - |
| S1‑031037 | [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‑031038 | Table of emergency call numbers | Ericsson | - |
| S1‑031039 | [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‑031040 | [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‑031041 | [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‑031042 | Table of emergency call numbers | Ericsson | - |
| S1‑031043 | Agenda Emergency Calls Ad Hoc | Ad Hoc Chair, Luisa Marchetto (AWS) | - |
| S1‑031044 | Modification of emergency number identification rules in 22.101 R99 | - | - |
| S1‑031045 | Modification of emergency number identification rules in 22.101 Rel-4 | - | - |
| S1‑031046 | Modification of emergency number identification rules in 22.101 Rel-5 | - | - |
| S1‑031047 | Table of emergency call numbers | Ericsson | - |
| S1‑031048 | - | - | - |
| S1‑031049 | Cleanup and modifications on identification of emergency numbers in 22.101 Rel-6 | - | - |
| S1‑031050 | [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. | Siemens AG | - |
| S1‑031051 | [DRAFT][D1] Reply LS on emergency calls | SA1 | - |
| S1‑031052 | Agenda for Emergency Calls Ad Hoc | Ad Hoc Chair, Luisa Marchetto (AWS) | - |
| S1‑031053 | 22.934 WLAN Interworking Feasibility Study Comments | SBC Communications | - |
| S1‑031055 | Consequences if ?[H16] | Orange, T-mobile, Telefonica, Vodafone | - |
| S1‑031056 | [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. | Schlumberger, TIM | - |
| S1‑031057 | [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. | MmO2, Schlumberger, TIM | - |
| S1‑031058 | Page: 1 | Lucent Technologies, Siemens, Nokia | - |
| S1‑031059 | Updated WI for GUP | SA | - |
| S1‑031060 | [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. | mmO2, T-Mobile, Vodafone, Cingular, Swisscom, KPN | - |
| S1‑031061 | [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. | mmO2 | - |
| S1‑031062 | [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. | Siemens | - |
| S1‑031063 | [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. | Siemens | - |
| S1‑031064 | Liaison Statement on EC Requirements on Emergency Telecommunications | OCG EMTEL | - |
| S1‑031065 | Reply LS on Network Sharing in GERAN | GERAN (WG2) | - |
| S1‑031066 | Liason statement on Profiling of RFC3325 for IMS | CN1 | - |
| S1‑031067 | LS on ‘updated WID for emergency call enhancements for IP & PS based calls’ | CN1 | - |
| S1‑031068 | LS on the Criteria for "change of position" procedures | CN2 | - |
| S1‑031069 | LS on sending the SGSNs MNC and MCC to the GGSN and service node | CN4 | - |
| S1‑031070 | LS to SA1 on GUP work in CN4 | CN4 | - |
| S1‑031071 | Reply to LS on Emergency Services Routing Based on Interim Position | CN4 | - |
| S1‑031072 | LS on Clarification on Presence Service Matters | CN4 | - |
| S1‑031073 | - | - | - |
| S1‑031074 | Reply LS on further guidance for Network Sharing in Rel-6 | RAN WG2 | - |
| S1‑031075 | LS on Base station definition in TR21.905 | TSG RAN WG4 | - |
| S1‑031076 | LS on update of Generic User Profile WID | SA2 | - |
| S1‑031077 | LS on MBMS Volume/Time Based Charging | SA2 | - |
| S1‑031078 | Response to RAN assumptions on MBMS | SA2 | - |
| S1‑031079 | Reply LS on Implementability of MBMS Requirements and Architecture | SA2 | - |
| S1‑031080 | Response LS on SMS/MMS Interworking from WLANs | SA2 | - |
| S1‑031081 | Reply to Liaison Statement on “Emergency Services Routing Based on Interim Position” | SA2 | - |
| S1‑031082 | LS on developing interworking with GIS (geographical information system) | 3GPP SA2 | - |
| S1‑031083 | Reply LS on possible re-organisation of 3GPP charging specification work | SA2 | - |
| S1‑031084 | Reply LS on "Broadcast and PLMN selection for shared RAN" | SA2 | - |
| S1‑031085 | LS on further guidance for Network Sharing in Rel-6 | SA2 | - |
| S1‑031086 | LS Response on User Data Management architecture requirements | SA2 | - |
| S1‑031087 | Response LS on MMS support by USAT | SA2 | - |
| S1‑031088 | LS on “Update of WID on MBMS" | SA4 | - |
| S1‑031089 | Response to Liaison Statement on “Reliable transport” for PSS | SA4 | - |
| S1‑031090 | LS reply on sending the SGSN’s MNC and MCC to the GGSN | SA5 SWGB | - |
| S1‑031091 | LS on Temperature Range in ETSI TS 102 221 | EP SCP | - |
| S1‑031092 | LS to report on Advanced UICC Communication | EP SCP | - |
| S1‑031093 | - | - | - |
| S1‑031094 | LS on principles for overlapping issues with OMA regarding PoC | 3GPP TSG-SA | - |
| S1‑031095 | LS – Emergency services using SMS / MMS | T2 | - |
| S1‑031096 | LS on addition of MMS support by the USIM Application Toolkit | T2 | - |
| S1‑031097 | Reply-LS on Application-ID in MMS | T2 | - |
| S1‑031098 | Progress in TSG T2 on the CBS | T2 | - |
| S1‑031099 | LS response on usage of GUP reference points | T2 | - |
| S1‑031100 | Reply-LS on Enhancements to DRM Support in MMS | T2 | - |
| S1‑031101 | LS on identifying MMS Enabled devices and MMS Capabilities of those devices. | T2 | - |
| S1‑031102 | Response to LS on support of GSM SIM files (and services) on the USIM | T3 | - |
| S1‑031103 | LS on 3GPP Smart Card Application Provisioning Parameters | 3GPP TSG–T3 | - |
| S1‑031104 | LS on potential USIM impact of the MBMS security framework | 3GPP TSG T WG3 | - |
| S1‑031105 | - | - | - |
| S1‑031106 | LS on the use of MMS as a bearer for USAT | 3GPP TSG-T | - |
| S1‑031107 | LS on TR 22.952, Priority Service Guide | 3GPP TSG-T | - |
| S1‑031108 | A GUP data store holding a synchronized copy of a GUP component may provide a GUP functionality to let data consumers access that synchronized copy | Siemens, Nokia | imported from 3GU |
| S1‑031109 | [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‑031110 | [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 | imported from 3GU |
| S1‑031111 | Actions on SA1 resulting from TSG SA#21 | Chairman | imported from 3GU |
| S1‑031112 | Proposed predisposition of liaison statements to SA1 | MCC | imported from 3GU |
| S1‑031113 | Proposed Agenda for Priority SWG Meeting | Priority Service SWG Chairman | imported from 3GU |
| S1‑031114 | Proposed Disposition of Editor's Notes for TR 22.952 | Telcordia Technologies | imported from 3GU |
| S1‑031115 | Proposed Text for Clause 4.4.2 for TR 22.952 | Telcordia Technologies | imported from 3GU |
| S1‑031116 | Proposed Text for Clause 4.6 for TR 22.952 | Telcordia Technologies | imported from 3GU |
| S1‑031117 | Proposed Modifications to TR 22.952 | Telcordia Technologies | imported from 3GU |
| S1‑031118 | [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‑031119 | Proposed Text Changes for TR 22.952 | National Communications System | imported from 3GU |
| S1‑031120 | Proposed New Text for TR 22.952 | National Communications System | imported from 3GU |
| S1‑031121 | - | - | imported from 3GU |
| S1‑031122 | [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‑031123 | [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 | imported from 3GU |
| S1‑031124 | [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 | imported from 3GU |
| S1‑031125 | [DRAFT] LS response on Presence Service Matters | SA1 | imported from 3GU |
| S1‑031126 | - | - | imported from 3GU |
| S1‑031127 | Enhancements to TS 22.246 (MBMS User Services) | Siemens AG | imported from 3GU |
| S1‑031128 | [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‑031129 | [H1] Document numbers are allocated by the Working Group Secretary. | Nortel Networks, AWS, T-Mobile USA | imported from 3GU |
| S1‑031130 | [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. | Schlumberger | imported from 3GU |
| S1‑031131 | [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. | Schlumberger | imported from 3GU |
| S1‑031132 | [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. | Schlumberger | imported from 3GU |
| S1‑031133 | [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. | Schlumberger | imported from 3GU |
| S1‑031134 | [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. | Schlumberger | imported from 3GU |
| S1‑031135 | [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 | imported from 3GU |
| S1‑031136 | [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 International | imported from 3GU |
| S1‑031137 | [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 International | imported from 3GU |
| S1‑031138 | [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 | imported from 3GU |
| S1‑031139 | DRAFT Information re OMA PoC Development Status | Cingular Wireless | imported from 3GU |
| S1‑031140 | Reply LS to 3GPP on principles for overlapping issues with OMA regarding PoC | OMA Req WG (with input from OMA PoC WG) | imported from 3GU |
| S1‑031141 | CBDD in UMTS Use Cases | Celltick. | imported from 3GU |
| S1‑031142 | [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. | Celltick Technologies | imported from 3GU |
| S1‑031143 | [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. | Nortel Networks. | imported from 3GU |
| S1‑031144 | [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‑031145 | Terminology addtions for IP-CAN and IP-CAN bearer | - | imported from 3GU |
| S1‑031146 | "Advanced Geographic Description" for Location based Services | SIEMENS | imported from 3GU |
| S1‑031147 | [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, Vodafone, Huawei | imported from 3GU |
| S1‑031148 | 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 | Schlumberger | imported from 3GU |
| S1‑031149 | - | - | imported from 3GU |
| S1‑031150 | Removal of Visited Network capabilities | - | imported from 3GU |
| S1‑031151 | [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‑031152 | Additional material for the join CAMEL session in SA1#22 | NOKIA | imported from 3GU |
| S1‑031153 | Proposal for GUP WID update | Nokia | imported from 3GU |
| S1‑031154 | Discussion of Presence dependency upon CAMEL (Phase 4) | NTT DoCoMo Inc. | imported from 3GU |
| S1‑031155 | [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‑031156 | Media Types for MBMS User Services | NTT DoCoMo Inc. | imported from 3GU |
| S1‑031157 | - | - | imported from 3GU |
| S1‑031158 | Status update for WI EMC1-PS | Ericsson | imported from 3GU |
| S1‑031159 | MBMS User Service Priorities | Bamboo MediaCasting Ltd. | imported from 3GU |
| S1‑031160 | - | - | imported from 3GU |
| S1‑031161 | Agenda of SWG Messaging | SWG Messaging Chair, Paul Carpenter (Research in Motion) | imported from 3GU |
| S1‑031162 | Clarification of 3G PS based service over WLAN | Samsung, | imported from 3GU |
| S1‑031163 | Automatic Device Detection (ADD) – General information and background | Ericsson | imported from 3GU |
| S1‑031164 | [H1] Enter the specification number in this box. For example, 04.08 or 31.102. Do not prefix the number with anything . i.e. do not use "TS", "GSM" or "3GPP" etc. | Ericsson | imported from 3GU |
| S1‑031165 | Changes to TR 22.952 on Roaming between eMLPP and Priority Service networks | Ericsson | imported from 3GU |
| S1‑031166 | Changes to TR 22.952 on North American regional requirements | Ericsson | imported from 3GU |
| S1‑031167 | MBMS Application bit-rates Clarification | Nortel Networks | imported from 3GU |
| S1‑031168 | [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‑031169 | Need for Point to Point repair for MBMS downloaded files | Vodafone Group | imported from 3GU |
| S1‑031170 | Administrative restriction of subscribers’ access – Background and general information | Ericsson | imported from 3GU |
| S1‑031171 | [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‑031172 | High Availability for OSA | AePONA (Eamonn Murray, Alan Taylor) | imported from 3GU |
| S1‑031173 | - | - | imported from 3GU |
| S1‑031174 | Old | AePONA, Ericsson, IBM | imported from 3GU |
| S1‑031175 | Draft reply to SA3 on UE Privacy and Security Framework | Vodafone Group | imported from 3GU |
| S1‑031176 | [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‑031177 | - | - | imported from 3GU |
| S1‑031178 | Priority call to an eMLPP subscriber | Nortel Networks | imported from 3GU |
| S1‑031179 | - | - | imported from 3GU |
| S1‑031180 | Proposed Changes to TR 22.952 – Priority Service Guide | Nortel Networks | imported from 3GU |
| S1‑031181 | - | - | imported from 3GU |
| S1‑031182 | [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, Fujitsu | imported from 3GU |
| S1‑031183 | - | - | imported from 3GU |
| S1‑031184 | MBMS User Services | NTT DoCoMo Inc. | imported from 3GU |
| S1‑031185 | [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‑031186 | [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‑031187 | Draft Report of the MBMS Joint Meeting | MBMS SA1/SA2/SA4/RAN1/RAN2/RAN3/RAN4/GERAN1/GERAN2 Joint Meeting Secretary1 | imported from 3GU |
| S1‑031188 | Charging Requirements for MBMS | 31, | imported from 3GU |
| S1‑031189 | Emergency Call Requirements | mmO2 | imported from 3GU |
| S1‑031190 | [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. | mmO2 | imported from 3GU |
| S1‑031191 | [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‑031192 | Agenda of IMS SWG | Chair / Kokkola | - |
| S1‑031193 | [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. | mmO2 | - |
| S1‑031194 | Add criteria "inter-MSC handover" for change of position procedures | - | - |
| S1‑031195 | [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. | SBC | - |
| S1‑031196 | Clarification of 3G PS based service over WLAN | Samsung, | - |
| S1‑031197 | - | - | - |
| S1‑031198 | - | - | - |
| S1‑031199 | LS on Layer1 Performance for MBMS | RAN1 | - |
| S1‑031200 | LS on Local Multicast area concept for MBMS | RAN3 | - |
| S1‑031201 | Liaison on “Comments on Priority Service Guide” | TSG RAN3 | - |
| S1‑031202 | LS on ‘USIM changes for key management of Voice Group Call Services’. | SA3 | - |
| S1‑031203 | The requirement and feasibility of IMS watcher authentication | SA3 | - |
| S1‑031204 | LS Reply on charging aspects of Priority Service (draft TR 22.952) | SA5 | - |
| S1‑031205 | MBMS SWG Agenda for SA#22 | MBMS SWG Chair1, | - |
| S1‑031206 | MBMS SA1/SA2/SA4/RAN1/RAN2/RAN3/RAN4/GERAN1/GERAN2 Meeting Report & Impacts on SA1 MBMS Work | MBMS SWG Chair1, | - |
| S1‑031207 | [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 International | - |
| S1‑031208 | Response LS on support of GSM SIM files (and services) on the USIM, and USIM changes for key management of Voice Group Call Services | SA1 | - |
| S1‑031209 | - | - | - |
| S1‑031210 | Reply on the requirement and feasibility of IMS watcher authentication | SA1 | - |
| S1‑031211 | - | - | - |
| S1‑031212 | Reply to STF228 User Interoperability Criteria | SA1 | - |
| S1‑031213 | - | - | - |
| S1‑031214 | - | - | - |
| S1‑031215 | - | - | - |
| S1‑031216 | - | - | - |
| S1‑031217 | LS on Status of 3GPP Service Definition and Service Creation work | S1 | - |
| S1‑031218 | LS on Priority Service and eMLPP interworking | S1 | - |
| S1‑031219 | Notify of forced erasure to initiating subscriber A | - | - |
| S1‑031220 | Interaction between ME and USAT applications | - | - |
| S1‑031221 | - | - | - |
| S1‑031222 | - | - | - |
| S1‑031223 | - | - | - |
| S1‑031224 | - | - | - |
| S1‑031225 | - | - | - |
| S1‑031226 | - | - | - |
| S1‑031227 | - | - | - |
| S1‑031228 | - | - | - |
| S1‑031229 | - | - | - |
| S1‑031230 | - | - | - |
| S1‑031231 | - | - | - |
| S1‑031232 | Introduce High Availability requirement for OSA | - | - |
| S1‑031233 | - | - | - |
| S1‑031234 | Administrative restriction of subscribers’ access | - | - |
| S1‑031235 | - | - | - |
| S1‑031236 | - | - | - |
| S1‑031237 | - | - | - |
| S1‑031238 | - | - | - |
| S1‑031239 | - | - | - |
| S1‑031240 | MMS targetting UE elements | - | - |
| S1‑031241 | - | - | - |
| S1‑031242 | - | - | - |
| S1‑031243 | - | - | - |
| S1‑031244 | - | - | - |
| S1‑031245 | - | - | - |
| S1‑031246 | - | - | - |
| S1‑031247 | - | - | - |
| S1‑031248 | - | - | - |
| S1‑031249 | - | - | - |
| S1‑031250 | - | - | - |
| S1‑031251 | - | - | - |
| S1‑031252 | - | - | - |
| S1‑031253 | - | - | - |
| S1‑031254 | - | - | - |
| S1‑031255 | - | - | - |
| S1‑031256 | Clarifications on general service requirements and data description requirements | - | - |
| S1‑031257 | Clarifications GUP data access and administration | - | - |
| S1‑031258 | Clarifications on GUP synchronisation | - | - |
| S1‑031259 | LS on updated WID for GUP | S1 | - |
| S1‑031260 | - | - | - |
| S1‑031261 | - | - | - |
| S1‑031262 | - | - | - |
| S1‑031263 | - | - | - |
| S1‑031264 | - | - | - |
| S1‑031265 | - | - | - |
| S1‑031266 | - | - | - |
| S1‑031267 | - | - | - |
| S1‑031268 | - | - | - |
| S1‑031269 | Support of "Advanced Geographic Description" (AGD) information | - | - |
| S1‑031270 | - | - | - |
| S1‑031271 | - | - | - |
| S1‑031272 | Correction of "velocity" requirements | - | - |
| S1‑031273 | - | - | - |
| S1‑031274 | Removal of change of area event | - | - |
| S1‑031275 | LS on modification of the LDR event types (reply to S2-032722) | S1 | - |
| S1‑031276 | - | - | - |
| S1‑031277 | - | - | - |
| S1‑031278 | LS on clarified requirements on synchronization for GUP | S1 | - |
| S1‑031279 | LS Reply on charging aspects of Priority Service Guide (draft TR 22.952) | S1 | - |
| S1‑031280 | - | - | - |
| S1‑031281 | - | - | - |
| S1‑031282 | - | - | - |
| S1‑031283 | - | - | - |
| S1‑031284 | - | - | - |
| S1‑031285 | LS on MMS targeting UE elements | S1 | - |
| S1‑031286 | LS on high bandwidth communication capability for USAT | S1 | - |
| S1‑031287 | - | - | - |
| S1‑031288 | - | - | - |
| S1‑031289 | - | - | - |
| S1‑031290 | - | - | - |
| S1‑031291 | - | - | - |
| S1‑031292 | - | - | - |
| S1‑031293 | - | - | - |
| S1‑031294 | LS on Clarification of the USSD message transfer to SIM/USIM requirement | S1 | - |
| S1‑031295 | - | - | - |
| S1‑031296 | CS interconnection – correction of an improper statement on the requirement for the identification of user data rate and user protocol at the interconnection point e.g. for inter-network | - | - |
| S1‑031297 | CS interconnection - requirements for the identification of user data rate and user protocol at the interconnection point e.g. for inter-network accounting purposes | - | - |
| S1‑031298 | CS interconnection - requirements for the identification of user data rate and user protocol at the interconnection point for inter-network accounting purposes | - | - |
| S1‑031299 | CS interconnection - requirements for the identification of user data rate and user protocol at the interconnection point for e.g. inter-network accounting purposes | - | - |
| S1‑031300 | Service based handover/assignment | - | - |
| S1‑031301 | - | - | - |
| S1‑031302 | LS on Equivalent PLMNs and Network Sharing | S1 | - |
| S1‑031303 | LS on CS interconnect accounting for multi-media services e.g. videotelephony | S1 | - |
| S1‑031304 | - | - | - |
| S1‑031305 | - | - | - |
| S1‑031306 | - | - | - |
| S1‑031307 | - | - | - |
| S1‑031308 | CLIR/CLIP interaction with CSE initiated calls | - | - |
| S1‑031309 | - | - | - |
| S1‑031310 | - | - | - |
| S1‑031311 | Modified base station definition | - | - |
| S1‑031312 | LS on Privacy and Security Requirements within GSM/UMTS Devices | S1 | - |
| S1‑031313 | Reply to LS on Clarification on Presence Service Matters (S1-031072;N4-031062) | S1 | - |
| S1‑031314 | Multi terminal requirement in 22.228 | - | - |
| S1‑031315 | CLIR/CLIP interaction with CSE initiated calls | - | - |
| S1‑031316 | Allowing CSE to suppress terminating CAMEL handling on new leg in existing call | - | - |
| S1‑031317 | Allowing CSE to suppress terminating CAMEL handling on new leg in existing call | - | - |
| S1‑031318 | CAMEL4 prepay interworking with SCUDIF | - | - |
| S1‑031319 | Align TS 22.038 with the T3 specifications TS 11.14 and TS 31.111 | - | - |
| S1‑031320 | Align TS 22.038 with the T3 specifications TS 11.14 and TS 31.111 | - | - |
| S1‑031321 | Align TS 22.038 with the T3 specifications TS 11.14 and TS 31.111 | - | - |
| S1‑031322 | Align TS 22.038 with the T3 specifications TS 11.14 and TS 31.111 | - | - |
| S1‑031323 | - | - | - |
| S1‑031325 | - | - | - |
| S1‑031326 | LS on developing interworking with GIS (reply to S2-033226) | S1 | - |
| S1‑031327 | Removal of misleading and obsolete text | - | - |
| S1‑031328 | Removal of misleading and obsolete text | - | - |
| S1‑031329 | Cell ID | - | - |
| S1‑031330 | MMS as an additional data exchange capability for USAT | - | - |
| S1‑031332 | Reply to LS on MBMS Volume/Time Based Charging (S1-031077;S2-033169) | S1 | - |
| S1‑031333 | Reply to LS on Layer1 Performance for MBMS (S1-031199;R1-031138) | S1 | - |
| S1‑031334 | Reply to LS on potential USIM impact of the MBMS security framework S1-031104; T3-030697) | S1 | - |
| S1‑031335 | Enable Cell Broadcast Bearer for USAT application while connected to UTRAN networks | - | - |
| S1‑031336 | Enable Cell Broadcast Bearer for USAT application while connected to UTRAN networks | - | - |
| S1‑031337 | - | - | - |
| S1‑031338 | UICC interaction with MMS clients | - | - |
| S1‑031339 | Automatic Device Detection | - | - |
| S1‑031340 | LS on CBDD to the USAT in UMTS | S1 | - |
| S1‑031341 | - | - | - |
| S1‑031342 | Correction of Core Network emergency call requirements | - | - |
| S1‑031343 | - | - | - |
| S1‑031344 | Clarification of emergency call requirements | - | - |
page generated from database: 2024-04-13 13:51:47