3GPP TDocs (written contributions) at meeting
Meeting: S1-21 - 2003-07-07 to 2003-07-11, Sophia Antipolis
meeting id: S1-21 (click id for more info on this meeting)Click on the Tdoc to open its file.
| TDoc | Title | Source | Remarks |
|---|---|---|---|
| S1‑030573 | Draft Agenda Version C – 23/06/2003 | SA1 Chairman/MCC | - |
| S1‑030574 | - | - | - |
| S1‑030577 | Proposed Agenda for Priority SWG Meeting | Priority Service SWG Chairman | imported from 3GU |
| S1‑030578 | Proposed Priority Service Guide – May-2003 draft | Telcordia Technologies | imported from 3GU |
| S1‑030579 | Comments on Annex A of the Priority Service Guide | Telcordia Technologies | imported from 3GU |
| S1‑030580 | Signalling of Priority Indicators | Telcordia Technologies | imported from 3GU |
| S1‑030581 | Mapping of Priority Indicators | Telcordia Technologies | imported from 3GU |
| S1‑030582 | - | - | imported from 3GU |
| S1‑030583 | Proposed outline for Priority Multimedia Service feasibiity study TR | Nortel Networks | imported from 3GU |
| S1‑030584 | Priority Service Guide draft – Comments | Nortel Networks | imported from 3GU |
| S1‑030585 | Use Cases for Bearer Level Charging | Nortel Networks | imported from 3GU |
| S1‑030586 | Contribution to 22.800 - sections on 3GPP requirement summary | TeliaSonera AB | - |
| S1‑030587 | Contribution to 22.800 - section on conclusions | TeliaSonera AB | imported from 3GU |
| S1‑030588 | Enhancements to 22.800 | TeliaSonera AB | imported from 3GU |
| S1‑030589 | Editorial modifications to 22.800 | TeliaSonera AB | - |
| S1‑030590 | WLAN Network selection requirements | Research In Motion | imported from 3GU |
| S1‑030591 | Definition: "Privacy Information" | Lucent Technologies | imported from 3GU |
| S1‑030592 | Privacy: Text for 'Regulatory Framework' Clause 9 | Lucent Technologies | imported from 3GU |
| S1‑030593 | Aspects on Priority Service and eMLPP in public networks | Ericsson | imported from 3GU |
| S1‑030594 | Aspects on simultaneous offering of Priority Service and eMLPP | Ericsson | - |
| S1‑030595 | Proposed Conclusion on TR 22 800 | Telecom Italia | imported from 3GU |
| S1‑030596 | Revision TR 22 800 | Telecom Italia | imported from 3GU |
| S1‑030597 | Conclusion for Multiple Terminals scenario | Nokia | - |
| S1‑030598 | GUP Access over several Networks | Alcatel | imported from 3GU |
| S1‑030599 | LS on review of TR “Study into Applicability of GALILEO in LCS” | SA2 | imported from 3GU |
| S1‑030600 | RE: Request for Information Regarding WLAN Interworking Impacts to UICC applications | SA2 | imported from 3GU |
| S1‑030601 | - | - | imported from 3GU |
| S1‑030602 | - | - | imported from 3GU |
| S1‑030603 | Notes on the priority service compatibility with WPS and ISUP | Nokia | imported from 3GU |
| S1‑030604 | Title | Source | imported from 3GU |
| S1‑030605 | Agenda of SWG Messaging | SWG Messaging Chair, Paul Carpenter (Research in Motion) | imported from 3GU |
| S1‑030606 | AGENDA for 22.800 (IMS) Drafting SWG | Luisa Marchetto (AWS) - Acting Chairperson | - |
| S1‑030607 | - | - | imported from 3GU |
| S1‑030608 | Discussion of principles for drawing conclusions from TR 22.800 | NTT DoCoMo Inc. | imported from 3GU |
| S1‑030609 | Proposed changes to Chapter 4 of TR 22.800 | NTT DoCoMo Inc. | imported from 3GU |
| S1‑030610 | Clarification of the method for drawing conclusions from TR 22.800 | NTT DoCoMo Inc. | imported from 3GU |
| S1‑030611 | - | - | imported from 3GU |
| S1‑030612 | Meeting Report of IMS SWG/TR 22.800 Drafting | Luisa Marchetto / Acting Chair | imported from 3GU |
| S1‑030613 | Reserved for IMS SWG | Acting SWG Chairperson | - |
| S1‑030614 | Proposed Conclusion on TR 22 800 | 3,Rogers Wireless, Vodafone,Telecom Italia | imported from 3GU |
| S1‑030615 | - | - | imported from 3GU |
| S1‑030616 | Modified Contribution | IMS SWG Acting Chairperson | - |
| S1‑030617 | Consequences if ?[H16] | T-Mobile | imported from 3GU |
| S1‑030618 | - | - | imported from 3GU |
| S1‑030619 | Discussion of the Relationship Between 3GPP and OMA for Messaging | Openwave | - |
| S1‑030620 | - | - | - |
| S1‑030621 | Reply LS on review of TR “Study into Applicability of GALILEO in LCS” (S2-031577) | SA1 | - |
| S1‑030623 | Aspects on Priority Service and eMLPP in public networks | Ericsson | - |
| S1‑030624 | [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. | SA1 LCS SWG | - |
| S1‑030625 | Reply to Liaison Statement on “Emergency Services Routing Based on Interim Position” | SA1 | - |
| S1‑030627 | Interactions between the eMLPP and the Priority Service | Ericsson | - |
| S1‑030629 | Definition of Personal data | Ericsson | - |
| S1‑030630 | Definition: "Privacy Information" | Lucent Technologies | - |
| s1‑030631 | - | - | - |
| s1‑030632 | Report of SWG Privacy | SWG Privacy Chair, Liz Daniel, Lucent Technologies | - |
| S1‑030633 | [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. | O2 | - |
| S1‑030634 | LS on MMS Service Requirements | SA1 | - |
| S1‑030635 | Report of SWG Messaging | SWG Messaging Chair: Paul Carpenter, Research in Motion | - |
| S1‑030636 | Liaison Statement on MMS Requirements | SA1 | - |
| S1‑030637 | Consequences if ?[H16] | T-Mobile | - |
| S1‑030638 | [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. | O2 | - |
| S1‑030639 | Comments on S1-030578 Priority Service Guide | Ericsson | - |
| S1‑030640 | LS on MMS Service Requirements | SA1 | - |
| S1‑030641 | Report of SWG Priority from San Diego | SWG Priority Chair, Jim Garrahan (Telcordia Technologies) | - |
| S1‑030643 | Report of March 13th & 15th SWG WLAN in San Diego | SWG WLAN Chair Mark Younge, T-Mobile USA | - |
| S1‑030644 | [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. | SA1 | - |
| S1‑030645 | [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‑030646 | [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. | SA1 LCS SWG | - |
| S1‑030647 | Report of SWG Bearer Charging | Amar Deol / Acting Chair | - |
| S1‑030648 | Use Cases for Bearer Level Charging | Nortel Networks | - |
| S1‑030649 | Draft Reply to Liaison Statement on “MBMS Codec Requirements | Nortel Networks | - |
| S1‑030650 | [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. | SA1 LCS SWG | - |
| S1‑030651 | Report of SWG Messaging | SWG Messaging Chair: Paul Carpenter, Research in Motion | - |
| S1‑030652 | LS on Stage 3 work for Early UE handling | GERAN2 | - |
| S1‑030653 | LS on impact of ‘Early UE handling’ on the GERAN | TSG GERAN | - |
| S1‑030654 | [D1]LS on Protocols over the Mt interface | CN WG1 | - |
| S1‑030655 | LS on Network Sharing Requirements for Rel-6 | CN1 | - |
| S1‑030656 | Reply LS on R99 and later emergency calls when attached to data only network | CN1 | - |
| S1‑030657 | Reply LS on sending the SGSN’s MNC and MCC to the GGSN and service node | CN4 | - |
| S1‑030658 | LS on terminal MMS capability discovery prior MM notification | TSG CN WG4 | - |
| S1‑030659 | LS on MNP | CN | - |
| S1‑030660 | LS on Core Network Provision of separate flows for P2P and P2M radio Transmission and Minimum UE Capability Required for Supporting MBMS | RAN1 | - |
| S1‑030661 | LS on Review of the Speech Enabled Services part of the 3GPP work plan | [SA 2] | - |
| S1‑030662 | Reply to Liaison Statement on MBMS Codec Requirements | TSG SA WG2 | - |
| S1‑030663 | LS on UE actions for Emergency Services | SA WG2 | - |
| S1‑030664 | Liaison response On Minimum UE Capability Required for supporting MBMS | SA2 | - |
| S1‑030665 | Reply to Liaison Statement on “Emergency Services Routing Based on Interim Position” | SA2 | - |
| S1‑030666 | LS on Additional Questions from LS on Query, Cancel of activated location requests for the Target | SA2 | - |
| S1‑030667 | Definition of “IMS Speech Call” | SA2 | - |
| S1‑030668 | LS on Privacy and Security Requirements within GSM/UMTS Devices | 3GPP SA3 | - |
| S1‑030669 | Reliable Transport: Status Update and Clarification on Use Cases | TSG SA WG4 | - |
| S1‑030670 | LS on Implications of Content Cache Language in TS 22.233 | SA4 | - |
| S1‑030671 | LS on sending the SGSN’s MNC and MCC to the GGSN and service nodes | SA5 | - |
| S1‑030672 | LS on Roaming Awareness | SA5 | - |
| S1‑030673 | LS on Reporting Radio Resource Usage Information for MBMS from UTRAN/GERAN to Core Network and/or to OAM | SA5 | - |
| S1‑030674 | Title | Source | - |
| S1‑030675 | UICC Temperature Ranges | ETSI SCP | - |
| S1‑030676 | Title | Source | - |
| S1‑030677 | LS on MMS for Deferred Mode IMS Messaging | T2 | - |
| S1‑030678 | RE: LS on Cleanup of SAT/USAT requirements 3GPP TS 22.038 | 3GPP T3 | - |
| S1‑030679 | LS on support of GSM SIM files (and services) on the USIM | TSG-T3 | - |
| S1‑030680 | Re: LS on clarification of USIM-based access to IMS | 3GPP T3 | - |
| S1‑030681 | Response LS on (U)SIM Toolkit originated emergency calls | 3GPP T3 | - |
| S1‑030682 | - | - | - |
| S1‑030683 | - | - | - |
| S1‑030684 | LS on Use of E164 numbers for emerging mobile systems | TSG CN WG4 | - |
| S1‑030685 | LS on CAMEL interactions with SCUDIF | CN4 (from joint session with CN2 & CN3) | - |
| S1‑030686 | LS on Charging Requirements on MNP for Pre-paid Subscribers | CN4 | - |
| S1‑030687 | Response to LS on MBMS requirements | RAN WG2-RAN WG3 MBMS ad-hoc. | - |
| S1‑030688 | LS Response on Use of ISIM and USIM for IMS access | SA2 | - |
| S1‑030689 | LS on clarification of USIM-based access to IMS | SA 3 | - |
| S1‑030690 | LS on requirements on security for the Mt reference point | 3GPP SA3 | - |
| S1‑030691 | Reply LS on ‘Request for Information Regarding WLAN Interworking Impacts to UICC applications’ | SA3 | - |
| S1‑030692 | Liaison response On Minimum UE Capability Required for supporting MBMS | SA4 | - |
| S1‑030693 | Reply to “Reply to Liaison Statement on MBMS Codec Requirements” | SA4 | - |
| S1‑030694 | Response to LS on Minimum UE Capability Required for supporting MBMS | RAN WG2 | - |
| S1‑030695 | WID for Multimedia Broadcast/Multicast Service (MBMS) codecs and protocols | Nokia1 | - |
| S1‑030696 | LS on usage of GUP reference points | SA5 (SWGA) | - |
| S1‑030697 | LS on Correction of the definition of the term CDR in 21.905 "Vocabulary for 3GPP Specifications" and in 22.115 "Service Aspects Charging and billing" | SA5 (SWGB) | - |
| S1‑030698 | LS on Frames WI Description | EP SCP-WG3 | - |
| S1‑030699 | Re: LS on SMS/MMS Interworking from WLANs | T2 | - |
| S1‑030700 | LS on missing SMS transmission via MSC | T2 | - |
| S1‑030701 | Re: LS on terminal MMS capability discovery prior MM notification | T2 | - |
| S1‑030702 | LS on WLAN interworking | 3GPP T3 | - |
| S1‑030703 | LS on MMS capability of the card | T3 | - |
| S1‑030704 | LS on the addition of MMS support by the USIM Application Toolkit | TSG-T | - |
| S1‑030705 | - | - | imported from 3GU |
| S1‑030706 | Report of SWG Priority from San Diego (revised) | SWG Priority Chair, Jim Garrahan (Telcordia Technologies) | imported from 3GU |
| S1‑030707 | Proposed Agenda for Priority SWG Meeting | Priority Service SWG Chairman | imported from 3GU |
| S1‑030708 | Priority Service Guide – July-2003 draft | Telcordia Technologies | imported from 3GU |
| S1‑030709 | Proposed Text for TR 22.952, Clause 5 | Telcordia Technologies | imported from 3GU |
| S1‑030710 | Proposed Text for TR 22.952, Clause 6 | National Communications System | imported from 3GU |
| S1‑030711 | Distinguishing Priority Service users vs. eMLPP users | Nortel Networks | imported from 3GU |
| S1‑030712 | Use Cases for Bearer Level Charging | Nortel Networks | imported from 3GU |
| S1‑030713 | Draft Reply to Liaison Statement on “MBMS Codec Requirements | Nortel Networks | imported from 3GU |
| S1‑030714 | Report of SWG Bearer Charging | Amar Deol / Acting Chair | imported from 3GU |
| S1‑030715 | - | - | imported from 3GU |
| S1‑030716 | [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. | Gemplus, Schlumberger | imported from 3GU |
| S1‑030717 | Response to Liaison Statement on “Reliable transport” for PSS | Orange | imported from 3GU |
| S1‑030718 | PayTV model | Gemplus, Oberthur | imported from 3GU |
| S1‑030719 | List of liaison statements to SA1 in Sophia Antipolis and proposed disposition | Chairman/MCC | imported from 3GU |
| S1‑030720 | - | - | imported from 3GU |
| S1‑030721 | Contribution to 3.1 and 4.3 of the Privacy TR (Privacy related Information) | Siemens | imported from 3GU |
| S1‑030722 | Contribution to 5.2 of the Privacy TR (clarification of General Requirements) | Siemens | imported from 3GU |
| S1‑030723 | Contribution to 6 and 9 of the Privacy TR (Relation to the OMA RD document) | Siemens | imported from 3GU |
| S1‑030724 | Network Selection for WLAN interworking | Telecom Italia | imported from 3GU |
| S1‑030725 | Update of GUP Work Item Description | Nokia | imported from 3GU |
| S1‑030726 | [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‑030727 | [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‑030728 | Proposal to Withdraw WID on 'Feature Interactions' | AT&T Wireless Services | - |
| S1‑030729 | [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. | Vodafone UK | imported from 3GU |
| S1‑030730 | [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. | Vodafone UK | imported from 3GU |
| S1‑030731 | LS on Privacy and Security Requirements within GSM/UMTS Devices | 3GPP SA1 | imported from 3GU |
| S1‑030732 | [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. | Vodafone UK | imported from 3GU |
| S1‑030733 | [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. | Vodafone, Ericsson | imported from 3GU |
| S1‑030734 | UPDATE TO MBMS TELESERVICE WID | 3 | - |
| S1‑030735 | General Material for MBMS Teleservice TS | 3 | - |
| s1‑030736 | MBMS Teleservice Streaming Use Case | 3 | imported from 3GU |
| s1‑030737 | MBMS Teleservice Download Use Case | 3 | imported from 3GU |
| S1‑030738 | MBMS Discussion on need of Uplink requirement as raised by SA | 3 | - |
| S1‑030739 | Logical conclusions on 22.800 | 3, Telecom Italia | imported from 3GU |
| S1‑030740 | Clarification ton Multiple IMS scenarios | 3 | - |
| S1‑030741 | [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. | 3, Telecom Italia | imported from 3GU |
| s1‑030742 | Draft Meeting Agenda for the MBMS session at SA1#22 | 31 | imported from 3GU |
| S1‑030743 | [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 | imported from 3GU |
| S1‑030744 | - | - | imported from 3GU |
| S1‑030745 | The GUP access mechanism shall be capable to access synchronized copies of a GUP component. | Siemens | imported from 3GU |
| S1‑030746 | [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‑030747 | 5.It shall be possible for the supplier of data to render the data to be unreadable by any party not authorised to receive it. | Siemens | imported from 3GU |
| S1‑030748 | Discussion on "Support of emergency calls when attached to data only network" | Siemens | imported from 3GU |
| S1‑030749 | [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‑030750 | Discussion of requirements for CAMEL support with SCUDIF | NTT DoCoMo Inc. | imported from 3GU |
| S1‑030751 | MBMS Teleservice Use Cases | NTT DoCoMo Inc. | imported from 3GU |
| S1‑030752 | [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‑030753 | [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‑030754 | Aspects on Priority Service and eMLPP in public networks | Priority SWG | imported from 3GU |
| S1‑030755 | Comments on the SA2 LS on Additional Questions from LS on Query, Cancel of activated location requests for the Target | Huawei, China Mobile | imported from 3GU |
| S1‑030756 | Interactions between the eMLPP and the Priority Service | Priority SWG | imported from 3GU |
| S1‑030757 | Priority Service, interworking with MLPP/ISUP/BICC | Ericsson | imported from 3GU |
| S1‑030758 | [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‑030759 | Consequences if ?[H16] | Ericsson | imported from 3GU |
| S1‑030760 | Comments on the 'Study on a Generalised Privacy Capability' | Ericsson | - |
| S1‑030761 | [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‑030762 | [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‑030763 | [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. | WLAN SWG | imported from 3GU |
| S1‑030764 | [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‑030765 | [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. | Lucent | imported from 3GU |
| S1‑030766 | [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‑030767 | [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‑030768 | MBMS Teleservice Charging Requirements | T-Mobile | imported from 3GU |
| S1‑030769 | MBMS Teleservice Security Aspects | T-Mobile | imported from 3GU |
| S1‑030770 | MBMS Teleservice High Level Requirements | T-Mobile | imported from 3GU |
| S1‑030771 | Cell Broadcast Data Download support in UMTS networks | Celltick, SchlumbergerSema | imported from 3GU |
| S1‑030772 | This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification. | T-Mobile | imported from 3GU |
| S1‑030773 | [DRAFT][D1] Reply LS on emergency calls | SA1 | imported from 3GU |
| S1‑030774 | Privacy, Minor Revisions | Lucent Technologies | imported from 3GU |
| S1‑030775 | - | - | imported from 3GU |
| S1‑030776 | [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‑030777 | [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‑030778 | [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‑030779 | MBMS Service Scenarios | Nokia | imported from 3GU |
| S1‑030780 | Discussion about service scenarios for audio in PSS and MMS in 3GPP Rel-6 | Nokia | - |
| S1‑030781 | Minimum number of shared network domain identities in shared networks | Nokia | imported from 3GU |
| S1‑030782 | Minimum number core network operators in shared networks and their identification | Nokia | imported from 3GU |
| S1‑030783 | Text proposal for TR 22.xyz Study on a Generalised Privacy Capability | Nokia | imported from 3GU |
| S1‑030784 | LS on CAMEL interactions with SCUDIF | SA1 | imported from 3GU |
| S1‑030785 | [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‑030786 | [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‑030787 | CAMEL interactions with SCUDIF | Ericsson | - |
| S1‑030788 | CAMEL interactions with SCUDIF | Ericsson | - |
| S1‑030789 | CAMEL interactions with SCUDIF | Ericsson | - |
| S1‑030790 | Use of SIM/USIM emergency number lists | Nokia | imported from 3GU |
| S1‑030791 | [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‑030792 | Consequences if ?[H16] | Nokia | imported from 3GU |
| S1‑030793 | [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‑030794 | Default emergency numbers | Nokia | imported from 3GU |
| S1‑030795 | IMS Speech call definition | Nokia | - |
| S1‑030796 | Emergency calls in PS domain | Nokia | - |
| S1‑030797 | [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‑030798 | [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‑030799 | Contribution to 3.1 and 4.3 of the Privacy TR (Privacy related Information) | Siemens | imported from 3GU |
| S1‑030800 | [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‑030801 | [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‑030802 | WLAN network selection requirements | Research In Motion | imported from 3GU |
| S1‑030803 | [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 WLAN SWG | imported from 3GU |
| S1‑030804 | [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 WLAN SWG | imported from 3GU |
| S1‑030805 | [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 WLAN SWG | imported from 3GU |
| S1‑030806 | [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 WLAN SWG | imported from 3GU |
| S1‑030807 | Agenda of Privacy SWG, DRAFT 1 | Chair / Liz Daniel | imported from 3GU |
| S1‑030808 | TR22.800 Update of scenario descriptions', dealing with revision of scenarios, namely the multiple IMS and the operators integration of domains | Telecom Italia | - |
| S1‑030809 | TR22.800 Revision of conclusions | Telecom Italia | - |
| S1‑030810 | Agenda of IMS SWG, DRAFT 2 | Chair / Kokkola | - |
| S1‑030811 | [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. | SchlumbergerSema | - |
| S1‑030812 | [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. | SA1 | - |
| S1‑030813 | - | - | - |
| S1‑030814 | Revised Report of March 13th & 15th SWG WLAN in San Diego | SWG WLAN Chair Mark Younge, T-Mobile USA | - |
| S1‑030815 | SMS over WLAN | Orange | - |
| S1‑030816 | - | - | - |
| S1‑030817 | Proposed dates for SA1 meetings in 2004 | Chairman, MCC | - |
| S1‑030818 | Result of SA #20 | Chairman/MCC | - |
| S1‑030819 | Meeting Report of IMS SWG/TR 22.800 Drafting | Luisa Marchetto / Acting Chair | - |
| S1‑030820 | Additional Use Case for eMLPP subscriber in a Priority Service only network | Nokia | - |
| S1‑030821 | Proposed Text for TR 22.952, Clause 5 | Telcordia Technologies | - |
| S1‑030822 | - | - | - |
| S1‑030823 | [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‑030824 | [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‑030825 | [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‑030826 | - | - | - |
| S1‑030827 | - | - | - |
| S1‑030828 | - | - | - |
| S1‑030829 | Security issue with multiple PDP Contexts in GPRS | Vodafone UK | - |
| S1‑030830 | Page: 1 | Vodafone UK | - |
| S1‑030832 | Reply to Liaison Statement on “Emergency Services Routing Based on Interim Position” | SA1 | - |
| S1‑030833 | [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‑030834 | Response to Liaison Statement on “Reliable transport” for PSS | SA1 | - |
| S1‑030835 | LS on Implementability of MBMS Requirements and Architecture | TSG GERAN | - |
| S1‑030836 | LS on CAMEL interactions with SCUDIF | SA1 | - |
| S1‑030837 | Reply LS on Frames WI Description | SA1 | - |
| S1‑030839 | [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. | Vodafone and NTT DoCoMo | - |
| S1‑030840 | LS on CS interconnect charging for multi-media services (Video telephony) | 3GPP SA1 | - |
| S1‑030841 | - | - | - |
| S1‑030842 | Report of SWG GUP | SWG GUP Chair Joerg Swetina | - |
| S1‑030843 | - | - | - |
| S1‑030844 | Report of IMS SWG | Max de Groot | - |
| S1‑030845 | - | - | - |
| S1‑030846 | - | - | - |
| S1‑030847 | - | - | - |
| S1‑030848 | Report of SWG Messaging | SWG Messaging Chair: Paul Carpenter, Research In Motion | - |
| S1‑030849 | - | - | - |
| S1‑030850 | Report of SWG Priority from Sophia Antipolis | SWG Priority Chair, Jim Garrahan (Telcordia Technologies) | - |
| S1‑030851 | - | - | - |
| s1‑030852 | Report of SWG Privacy | SWG Privacy Chair, Liz Daniel, Lucent Technologies | - |
| S1‑030853 | - | - | - |
| S1‑030854 | Report of SWG WLAN | SWG WLAN Chair Mark Younge, T-Mobile USA | - |
| S1‑030855 | - | - | - |
| S1‑030856 | Report of SWG MBMS | SWG MBMS Chair Bill Szelazek | - |
| S1‑030857 | - | - | - |
| S1‑030858 | Draft Response LS on Network Sharing Requirements for Rel-6 | SA1 | - |
| S1‑030859 | Minimum number of Shared Network Domain Identities | SA1 | - |
| S1‑030860 | [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. | Vodafone UK | - |
| S1‑030861 | [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 | - |
| S1‑030862 | - | - | - |
| S1‑030863 | [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‑030864 | [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‑030865 | [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‑030866 | [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. | Vodafone UK | - |
| s1‑030867 | Draft Meeting Agenda for the MBMS session at SA1#21 | 31 | - |
| S1‑030868 | - | - | - |
| S1‑030870 | Reply to Liaison Statement on “MBMS Codec Requirements | SA1 | - |
| S1‑030873 | DRAFT LS on MBMS Teleservice Requirements | SA1 | - |
| S1‑030875 | - | - | - |
| S1‑030876 | DRAFT LS on MBMS Teleservice Requirements | SA1 | - |
| S1‑030879 | This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification. | T-Mobile | - |
| S1‑030880 | Agenda of SWG Messaging – Update B | SWG Messaging Chair, Paul Carpenter (Research in Motion) | - |
| S1‑030882 | LS on Delivery Reports | SA1 | - |
| S1‑030883 | -Screening of Messages | T-Mobile | - |
| S1‑030884 | Consequences if ?[H16] | Nokia | - |
| S1‑030885 | LS on MMS capability of the card | EP SCP WG1 | - |
| S1‑030886 | [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. | SchlumbergerSema, TIM | - |
| S1‑030887 | [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. | SchlumbergerSema, TIM | - |
| S1‑030888 | LS on MMS as a Bearer for USAT | SA1 | - |
| S1‑030889 | LS on MMS Service Requirements | SA1 | - |
| S1‑030890 | - | - | - |
| S1‑030891 | WID for Cell Broadcast Data Download in UMTS | - | - |
| S1‑030892 | LS on Cell Broadcast Data Download with UMTS | SA1 | - |
| S1‑030893 | It is an operator decision as to the level of interworking supported. This can be broadly grouped as: | RIM | - |
| S1‑030894 | [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. | SchlumbergerSema, TIM | - |
| S1‑030895 | [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. | SchlumbergerSema, TIM | - |
| S1‑030896 | Additional Use Case for eMLPP subscriber in a Priority Service only network | Nokia | - |
| S1‑030897 | Priority Service Guide – v0.6.0 – Request to send to TSG-SA for information | Priority SWG | - |
| S1‑030899 | [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. | WLAN SWG | - |
| S1‑030900 | RE: Re: LS on SMS/MMS Interworking from WLANs | SA1 | - |
| S1‑030901 | [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‑030902 | Reply LS on WLAN Interworking requirements for SIM and USIM | SA1 | - |
| S1‑030903 | Re: LS on SMS/MMS Interworking from WLANs | SA1 | - |
| S1‑030904 | [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‑030905 | LS on requirements on security for the Mt reference point | SA1 | - |
| S1‑030906 | Conference: An IP multimedia session with two or more participants. Each conference has a "conference focus". A conference can be uniquely identified by a user. An example for a conference could be a multimedia game, in which the conference focus is | SA1 (3, Telecom Italia) | - |
| S1‑030907 | - | - | - |
| S1‑030908 | [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. | SA1 (T-Mobile) | - |
| S1‑030910 | [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. | SA1 (T-Mobile) | - |
| S1‑030911 | [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‑030912 | LS on requirements on security for the Mt reference point | SA1 | - |
| S1‑030914 | Proposed modifications to S1-030854 WLAN report | RIM | - |
| S1‑030915 | [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. | WLAN SWG | - |
| S1‑030916 | Report of SWG WLAN | SWG WLAN Chair Mark Younge, T-Mobile USA | - |
| S1‑030917 | [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. | Vodafone UK | - |
| S1‑030918 | [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. | SA1 | - |
| S1‑030919 | Reply to LS on Additional Questions from LS on Query, Cancel of activated location requests for the Target | SA1 | - |
| S1‑030920 | Reply to LS on Additional Questions from LS on Query, Cancel of activated location requests for the Target | SA1 | - |
| S1‑030921 | Reply LS on Broadcast and PLMN selection for Shared RAN | GERAN | - |
| S1‑030922 | LS on MMS as a Bearer for USAT | SA1 | - |
| S1‑030923 | [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. | SchlumbergerSema, TIM | - |
| S1‑030924 | Consequences if ?[H16] | Orange, T-mobile, Telefonica | - |
| S1‑030925 | Consequences if ?[H16] | Orange, T-mobile, Telefonica | - |
| S1‑030927 | LS on usage of GUP reference points | SA2 | - |
| S1‑030928 | LS on Security issues regarding multiple PDP contexts in GPRS | SA2 | - |
| S1‑030929 | Update of GUP Work Item Description | SA1 | - |
| S1‑030930 | Text proposal for TR 22.xyz Study on a Generalised Privacy Capability | Nokia | - |
| S1‑030931 | Privacy, Minor Revisions | Lucent Technologies | - |
| s1‑030932 | - | - | - |
| S1‑030935 | LS on TR 22.952, Priority Service Guide – request for review and comment | SA1 | - |
| S1‑030936 | Contribution to 3.1 and 4.3 of the Privacy TR (Privacy related Information) | Siemens | - |
| S1‑030937 | Contribution to 5.2 of the Privacy TR (clarification of General Requirements) | Siemens | - |
| S1‑030938 | Contribution to 6 and 9 of the Privacy TR (Relation to the OMA RD document) | Siemens | - |
| S1‑030939 | [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. | Motorola | - |
| S1‑030940 | [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 (Ericsson, Motorola) | - |
| S1‑030942 | LS on Priority Service and eMLPP interworking | SA1 | - |
| S1‑030943 | [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‑030944 | [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‑030945 | [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‑030946 | [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. | Vodafone UK | - |
| S1‑030947 | [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. | SA1 | - |
| S1‑030948 | [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. | Vodafone UK | - |
| S1‑030949 | LS on MMS Service Requirements | SA1 | - |
| S1‑030950 | [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. | SchlumbergerSema, TIM | - |
| S1‑030951 | Reply LS on “Security issues regarding multiple PDP contexts in GPRS” | SA1 | - |
| S1‑030953 | [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‑030954 | Response LS on (U)SIM Toolkit originated emergency calls | 3GPP SA1 | - |
| S1‑030955 | Reply to Liaison Statement on Bearer Level Charging | SA1 | - |
| S1‑030956 | Alignment of stage 1 with stage 2 & stage 3 | - | - |
| S1‑030957 | Reply to LS on Implementability of MBMS Requirements and Architecture, (GP031730) | TSG SA1 | - |
| S1‑030958 | Reply LS on “Security issues regarding multiple PDP contexts in GPRS” | SA1 | - |
| S1‑030959 | [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. | Vodafone | - |
| S1‑030960 | - | - | - |
| S1‑030961 | [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. | Vodafone UK | - |
| S1‑030962 | [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‑030963 | [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‑030964 | LS on CAMEL interactions with SCUDIF | SA1 | - |
| S1‑030965 | 5.It shall be possible for the supplier of data to render the data to be unreadable by any party not authorised to receive it. | Siemens | - |
| S1‑030966 | Reply LS on WLAN Interworking requirements for SIM and USIM | SA1 | - |
| S1‑030967 | Re: LS on SMS/MMS Interworking from WLANs | SA1 | - |
| S1‑030968 | - | - | - |
| S1‑030969 | LS on Priority Service and eMLPP interworking | SA1 | - |
| S1‑030970 | [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. | SA5 | - |
| S1‑030971 | [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. | SA5 | - |
| S1‑030972 | Minimum number of Shared Network Domain Identities | SA1 | - |
| S1‑030973 | Response LS on (U)SIM Toolkit originated emergency calls | 3GPP SA1 | - |
| S1‑030974 | [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‑030975 | Default emergency numbers | SA1 | - |
| S1‑030976 | [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. | Vodafone | - |
| S1‑030977 | Response to LS on support of GSM SIM files (and services) on the USIM | SA1 | - |
| S1‑030978 | Reply LS on Frames WI Description | SA1 | - |
| S1‑030979 | LS on CS interconnect charging for multi-media services (Video telephony) | 3GPP SA1 | - |
page generated from database: 2024-04-13 13:51:47