id stringlengths 5 12 | title stringlengths 8 250 | type stringclasses 2
values | version stringclasses 560
values | working_group stringclasses 30
values | url stringlengths 67 81 | scope stringlengths 0 65.7k |
|---|---|---|---|---|---|---|
22.115 | Service aspects; Charging and billing | TS | 3.4.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.115/22115-340.zip | The present document describes the Service Aspects of charging and billing of the 3GPP System.
The present document is not intended to duplicate existing standards or standards being developed by other groups on these topics, and will reference these where appropriate. The present document will elaborate on the charging requirements described in the Charging Principles in 3GPP TS 22.101 Service Principles. It will allow the generation of accurate charging information to be used in the commercial and contractual relationships between the parties concerned. |
22.121 | Service aspects; The Virtual Home Environment (VHE); Stage 1 | TR | 3.3.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.121/22121-331.zip | The present document specifies the content of the Stage 1 requirement for realisation of VHE.
Virtual Home Environment (VHE) is defined as a concept for Personal Service Environment (PSE) portability across network boundaries and between terminals. The concept of VHE is such that users are consistently presented with the same personalised features, User Interface customisation and services in whatever network and whatever terminal (within the capabilities of the terminal and the network), wherever the user may be located. |
22.135 | Multicall; Service description; Stage 1 | TS | 3.4.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.135/22135-340.zip | |
22.129 | Service aspects; Handover requirements between UTRAN and GERAN or other radio systems | TS | 3.6.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.129/22129-360.zip | |
22.945 | Study of provision of fax service in GSM and UMTS | TR | 3.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.945/22945-300.zip | |
22.140 | Multimedia Messaging Service (MMS); Stage 1 | TS | 3.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.140/22140-310.zip | |
22.975 | Advanced addressing | TR | 3.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.975/22975-310.zip | This document defines the requirements for numbering and addressing for UMTS. This technical report is aimed at generating discussion and should agreed with ETSI WG NA2. The responsibility for developing of Numbering and Addressing schemes for all networks being in ETSI NA2. |
22.971 | Automatic establishment of roaming relationships | TR | 3.1.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.971/22971-311.zip | This document outlines a proposed framework for commercial and technical interworking between UMTS Home Environments and Serving Networks who have no direct prior commercial agreements with each other.
This document is applicable to UMTS standardisation within ETSI, and is produced with the intent to clarify the concepts involved, and identify those areas which require standardisation. |
23.002 | Network architecture | TS | 3.6.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.002/23002-360.zip | |
23.003 | Numbering, addressing and identification | TS | 3.15.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.003/23003-3f0.zip | |
23.007 | Restoration procedures | TS | 3.6.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.007/23007-360.zip | The data stored in location registers are automatically updated in normal operation; the main information stored in a location register defines the location of each mobile station and the subscriber data required to handle traffic for each mobile subscriber. The loss or corruption of these data will seriously degrade the service offered to mobile subscribers; it is therefore necessary to define procedures to limit the effects of failure of a location register, and to restore the location register data automatically. The present document defines the necessary procedures.
The basic principle is that restoration should be based on radio contact to avoid faulty data being spread in the system.
Subscriber data for supplementary services must also be correctly restored, although the impact on service of corruption of supplementary service data is less severe.
Procedures for supporting these functions are defined in 3GPP TS 29.002 [6] and 3GPP TS 29.060 [8].
The MAP operation "IMSI Attach" is used only in MAP version 1; in MAP version 2 the same function is performed by the MAP operation "Update Location Area". References in this specification to IMSI attach apply only to MAP version 1 network entities.
If the restoration of subscriber data in the VLR is triggered by Location Updating or IMSI Attach, the VLR retrieves subscriber data from the HLR by sending an "Update Location" request, which triggers one or more "Insert Subscriber Data" operations from the HLR. The "Update Location" request may also be used to send the LMSI to the HLR.
If the restoration of subscriber data in the VLR is triggered by a "Provide Roaming Number" request, the behaviour of the VLR depends on whether it is implemented according to MAP version 1 or MAP version 2. For MAP version 2, the VLR retrieves subscriber data from the HLR by sending a "Restore Data" request, which triggers one or more "Insert Subscriber Data" operations from the HLR. The "Restore Data" request is also used to send the LMSI to the HLR. For MAP version 1, the VLR retrieves subscriber data from the HLR by sending a "Send Parameters" request with parameter type "Subscriber Data", which cannot be used to send the LMSI to the HLR.
The VLR number and MSC number in the subscriber data in the HLR are updated by the "Update Location" procedure.
The GGSN (Gateway GPRS Support Node) is the point of PDN interconnection with the GSM PLMN supporting GPRS. The GGSN contains routing information for GPRS users with a PDP context active. The necessary procedures needed to restore GGSN data information after a restart are described in this document.
The SGSN (Serving GPRS Support Node) is the node that is serving the MS. The SGSN stores information regarding e.g. mobility management, routing and security. The necessary procedures needed to restore this SGSN information after a restart are described in this document.
The MME (Mobility Management Entity) is the node that is serving the UE when attached to E-UTRAN. The MME stores information regarding e.g. mobility management, routing and security. The necessary procedures needed to restore this MME information after a restart are described in this document.
A Type A LMU (Location Measurement Unit) is a network node, accessed over the GSM air interface, that is functionally similar to an MS. All requirements associated with a non-GPRS MS in this specification apply also to a Type A LMU except where specified otherwise. |
23.009 | Handover procedures | TS | 3.14.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.009/23009-3e0.zip | |
23.008 | Organization of subscriber data | TS | 3.8.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.008/23008-380.zip | The present document provides details concerning information to be stored in the different entities storing data within a 3GPP network concerning mobile subscriber. A list of entities storing subscriber data is provided in clause 1.
Clause 2 contains all details concerning the definition of the parameters, often given by reference to other specifications, and where the parameter is to be stored.
Table 1 in clause 3 gives a summary overview and clause 4 identifies the reference information required for accessing the information.
In this specification, if there is no specific indication, the following principles apply:
- "SGSN" refers to an SGSN which may support the Gn and Gp interfaces or the S4 interface or both.
- "S4-SGSN" refers to an SGSN which only supports the S4 interface.
- "Gn/Gp-SGSN" refers to an SGSN which only supports the Gn and Gp interfaces. |
23.012 | Location management procedures | TS | 3.3.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.012/23012-330.zip | |
23.014 | Support of Dual Tone Multi-Frequency (DTMF) signalling | TS | 3.2.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.014/23014-320.zip | |
23.011 | Technical realization of Supplementary Services | TS | 3.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.011/23011-310.zip | |
23.015 | Technical realization of Operator Determined Barring (ODB) | TS | 3.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.015/23015-310.zip | The network feature Operator Determined Barring (ODB) allows a network operator or service provider to regulate access by subscribers to services (Circuit/Packet Oriented and Interworking WLAN), by the barring of certain categories of incoming or outgoing calls/ Packet Oriented Services or of roaming. Operator Determined Barring applies to all bearer services and teleservices except the Emergency Call teleservice and Emergency Bearer Services; the teleservice Short Message Point-to-Point is therefore subject to Operator Determined Barring in the same way as circuit-switched calls.
The application of specific categories of Operator Determined Barring to a subscription is controlled by the network operator or service provider, using administrative interaction at the HLR; this interface is not standardised. |
23.018 | Basic call handling; Technical realization | TS | 3.12.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.018/23018-3c0.zip | |
23.031 | 3G Security; Fraud Information Gathering System (FIGS); Technical realization; Stage 2 | TS | 3.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.031/23031-300.zip | |
23.016 | Subscriber data management; Stage 2 | TS | 3.10.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.016/23016-3a0.zip | |
23.034 | High Speed Circuit Switched Data (HSCSD); Stage 2 | TS | 3.3.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.034/23034-330.zip | |
23.032 | Universal Geographical Area Description (GAD) | TS | 3.2.1 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.032/23032-321.zip | |
23.035 | Immediate Service Termination (IST); Stage 2 | TS | 3.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.035/23035-310.zip | |
23.039 | Interface Protocols for the connection of Short Message Service Centers (SMSCs) to Short Message Entities (SMEs) | TR | 3.2.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.039/23039-320.zip | The present document describes a range of alternative interfaces which may be utilised by Short Message Service Centre (SMSC), and Short Message Entity (SME), developers for the connection of SMEs to SMSCs.
The purpose of the present document is to provide a single document within which the various proprietary SMSC to SME interface standards may be accommodated as optional implementations.
As stated in 3GPP TS 23.040 [1], the functionality of the SMSC is outside of the scope of the 3GPP Technical Specifications. As a result, no standardised interfaces have been specified for the connection of SMEs to the SMSC. In the absence of a prevailing standard, SC (Service Centre), developers have devised their own protocols which have not necessarily been based on any existing standards and are therefore largely incompatible with one another.
This document by referring to the various de-facto protocols will limit the further proliferation of proprietary standards and will benefit new SC/SME developers who may then adopt one or more of the existing protocols outlined in the present document.
This document does not provide recommendations, as to the preferred protocol implementation as all are regarded as being of equal merit. SC/SME implementors should therefore adopt the protocol most suited to their particular implementation, application or market. |
23.040 | Technical realization of the Short Message Service (SMS) | TS | 3.11.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.040/23040-3b0.zip | |
23.038 | Alphabets and language-specific information | TS | 3.3.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.038/23038-330.zip | |
23.042 | Compression algorithm for text messaging services | TS | 3.1.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.042/23042-310.zip | |
23.057 | Mobile Execution Environment (MExE); Functional description; Stage 2 | TS | 3.4.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.057/23057-340.zip | |
23.041 | Technical realization of Cell Broadcast Service (CBS) | TS | 3.5.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.041/23041-350.zip | |
23.066 | Support of Mobile Number Portability (MNP); Technical realization; Stage 2 | TS | 3.3.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.066/23066-330.zip | |
23.060 | General Packet Radio Service (GPRS); Service description; Stage 2 | TS | 3.17.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.060/23060-3h0.zip | |
23.067 | enhanced Multi-Level Precedence and Pre-emption Service (eMLPP); Stage 2 | TS | 3.3.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.067/23067-330.zip | |
23.072 | Call Deflection (CD) supplementary service; Stage 2 | TS | 3.3.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.072/23072-330.zip | |
23.078 | Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 4; Stage 2 | TS | 3.19.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.078/23078-3j0.zip | |
23.079 | Support of Optimal Routeing (SOR); Technical realization | TS | 3.8.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.079/23079-380.zip | |
23.081 | Line Identification supplementary services; Stage 2 | TS | 3.2.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.081/23081-320.zip | |
23.082 | Call Forwarding (CF) supplementary services; Stage 2 | TS | 3.7.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.082/23082-370.zip | |
23.083 | Call Waiting (CW) and Call Hold (HOLD) supplementary services; Stage 2 | TS | 3.2.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.083/23083-320.zip | |
23.084 | Multi Party (MPTY) supplementary service; Stage 2 | TS | 3.2.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.084/23084-320.zip | |
23.085 | Closed User Group (CUG) supplementary service; Stage 2 | TS | 3.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.085/23085-310.zip | |
23.087 | User-to-User Signalling (UUS) supplementary service; Stage 2 | TS | 3.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.087/23087-310.zip | |
23.086 | Advice of Charge (AoC) supplementary services; Stage 2 | TS | 3.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.086/23086-310.zip | |
23.088 | Call Barring (CB) Supplementary Services; Stage 2 | TS | 3.2.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.088/23088-320.zip | |
23.091 | Explicit Call Transfer (ECT) supplementary service; Stage 2 | TS | 3.2.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.091/23091-320.zip | |
23.090 | Unstructured Supplementary Service Data (USSD); Stage 2 | TS | 3.2.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.090/23090-320.zip | |
23.093 | Technical realization of Completion of Calls to Busy Subscriber (CCBS); Stage 2 | TS | 3.2.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.093/23093-320.zip | |
23.096 | Name identification supplementary services; Stage 2 | TS | 3.0.1 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.096/23096-301.zip | |
23.097 | Multiple Subscriber Profile (MSP) (Phase 2); Stage 2 | TS | 3.1.1 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.097/23097-311.zip | |
23.101 | General Universal Mobile Telecommunications System (UMTS) architecture | TS | 3.1.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.101/23101-310.zip | |
23.094 | Follow-Me (FM); Stage 2 | TS | 3.2.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.094/23094-320.zip | |
23.108 | Mobile radio interface layer 3 specification, core network protocols; Stage 2 | TS | 3.2.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.108/23108-320.zip | |
23.107 | Quality of Service (QoS) concept and architecture | TS | 3.9.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.107/23107-390.zip | |
23.116 | Super-Charger technical realization; Stage 2 | TS | 3.2.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.116/23116-320.zip | |
23.119 | Gateway Location Register (GLR); Stage 2 | TS | 3.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.119/23119-300.zip | |
23.110 | Universal Mobile Telecommunications System (UMTS) access stratum; Services and functions | TS | 3.4.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.110/23110-340.zip | |
23.121 | Architectural requirements for Release 1999 | TS | 3.6.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.121/23121-360.zip | The present document covers issues related to the evolution of the GSM platform towards UMTS with the overall goal of fulfilling the UMTS service requirements, the support of the UMTS role model, support of roaming and support of new functionality, signalling systems and interfaces. |
23.122 | Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode | TS | 3.10.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.122/23122-3a0.zip | |
23.127 | Virtual Home Environment (VHE) / Open Service Access (OSA) | TS | 3.4.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.127/23127-340.zip | The present document specifies the stage 2 of the Virtual Home Environment.
Virtual Home Environment (VHE) is defined as a concept for Personal Service Environment (PSE) portability across network boundaries and between terminals. The concept of VHE is such that users are consistently presented with the same personalised features, User Interface customisation and services in whatever network and whatever terminal (within the capabilities of the terminal and the network), wherever the user may be located.
For Release 5, e.g. CAMEL, MExE, OSA and USAT are considered the mechanisms supporting the VHE concept.
Stage 2 specifications for CAMEL, MExE and USAT are addressed in other documents [1], [2], [3]. However, there is no separate stage 2 specification document for OSA. Therefore, the present document addresses stage 2 aspects for OSA. |
23.135 | Multicall supplementary service; Stage 2 | TS | 3.2.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.135/23135-320.zip | |
23.171 | Location Services (LCS); Functional description; Stage 2 (UMTS) | TS | 3.11.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.171/23171-3b0.zip | The present document specifies the stage 2 of the LoCation Services (LCS) feature in UMTS, which provides the mechanisms to support mobile location services for operators, subscribers and third party service providers.
Location Services may be considered as a network provided enabling technology consisting of standardised service capabilities, which enable the provision of location applications. The application(s) may be service provider specific. The description of the numerous and varied possible location applications which are enabled by this technology are outside the scope of the present document. However, clarifying examples of how the functionality being described may be used to provide specific location services may be included.
This stage 2 service description covers the LCS system functional model for the whole system, the LCS system architecture, state descriptions, message flows, etc. |
23.908 | Technical report on Pre-Paging | TR | 3.0.1 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.908/23908-301.zip | The purpose of the present document is to study:
1. The potential applications of Pre-paging in GSM/UMTS networks.
2. The impact of Pre-paging on the GSM/UMTS specifications.
3. The interaction of Pre-paging with the work carried out by SMG2 and SMG3 on Classmarks for UMTS (i.e. Service Classmark and Terminal classmark).
It is a requirement of the report that the Pre-paging mechanism does not require an upgrade of the MAP application context version. |
23.909 | Technical report on the Gateway Location Register | TR | 3.0.1 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.909/23909-301.zip | The present document describes the use of a Gateway Location Register within the UMTS Core Network as a means of reducing the amount of MAP signalling traffic associated with location management carried over inter-PLMN links for roaming users.
One of the requirements of the present document is to describe a network architecture where the presence of a GLR within a UMTS PLMN is not visible to either a second generation PLMN (i.e. GSM release 98 or earlier) or a 3G PLMN (i.e. GSM Release 99 or later). So the objective of this report is that changes to GSM specified interfaces or procedures will not be needed in order to:
- integrate a GLR into a UMTS PLMN;
- allow interworking between a GLR-enabled UMTS network and a GSM or UMTS network without a GLR.
The present document will be restricted to the study of the case where the GLR supports one VPLMN only. A separate TR will be required if support of multiple VPLMNs by the GLR is to be studied.
The present document will study support of multiple HPLMNs by the GLR. |
23.910 | Circuit switched data bearer services | TR | 3.6.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.910/23910-360.zip | The present document provides an overview of the architecture and issues related to the provision of Circuit Switched Bearer Services in a 3G mobile network (UMTS) operating in UTRAN or GERAN Iu mode. Handover to GERAN A/Gb mode is also considered.
NOTE: The Gb interface does not play any role in the scope of the present document although the term "A/Gb mode" is used. |
23.911 | Technical report on Out-of-band transcoder control | TR | 3.0.1 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.911/23911-301.zip | The purpose of the present document is to study:
1. The feasibility of out-of-band transcoder control in UMTS/IMT-2000 networks.
2. The impact of out-of-band transcoder control on the UMTS/IMT-2000 specifications.
The present document introduces one enhanced in-band transcoder control procedure and four out‑of‑band transcoder control procedures that might be adaptable for transcoder control in UMTS/IMT-2000 networks. Then compare each procedure from various point of views to seek the most feasible procedure. |
23.912 | Technical report on Super-Charger | TR | 3.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.912/23912-310.zip | The present document describes the use of Super-Charger mechanism within UMTS to reduce the signalling traffic associated with mobility. This document provides a technical proposal and example uses of the Super-Charger concept but also identifies issues that require further study. Finally, this document highlights the advantages and disadvantages, and identifies the UMTS Technical Specifications that would require enhancing to support this functionality. |
23.923 | Combined GSM and Mobile IP mobility handling in UMTS IP CN | TR | 3.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.923/23923-300.zip | The present document contains a feasibility study on using Mobile IP+ as a tunnelling and mobility management protocol in combination with GSM/UMTS mobility management in the packet domain of UMTS CN. A target architecture will be described and evaluated and the migration path from the current GPRS architecture towards the target architecture will be defined. It shall also describe the driving forces for moving from GTP towards Mobile IP+ as well as the benefits and disadvantages of the target architecture. A time schedule, i.e. UMTS releases, for the standardisation of such an architecture shall be proposed. Work on Mobile IP+ in the IETF should be taken into account.
This report will also contain a study on how to offer Mobile IP+ as an overlay to GPRS. This would allow an end user device, which is connected to the Internet (or intranet etc.) via LAN, to be reconnected during an active session via GPRS/UMTS or visa versa, without the need for any re-configuration or re-start of applications. The outcome of this part shall be part of UMTS release 99. Proposed solutions need to be balanced between the requirement to minimise the impact on the current GPRS standards and the requirements generated by further development of using Mobile IP+ within the CN in an efficient way. The output of this study is a description of the system and a set of CR's for those standards handled by 3GPP-TSG SA-WG2. |
23.930 | Iu principles | TR | 3.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.930/23930-300.zip | This report identifies the requirements on the Iu and studies relevant principles to guide further standardisation of the related interface(s).
The different instances of the UMTS radio access currently identified are the following:
UMTS radio access network (URAN)
UMTS Terrestrial Radio Access Network (UTRAN)
Broadband Radio Access Network (BRAN)
UMTS satellite radio access network |
23.972 | Circuit switched multimedia telephony | TR | 3.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.972/23972-300.zip | This document collects the requirements and working assumptions for multimedia for release 99. The description is at a level of detail, which is required in the detailed procedure design in N1 and N3.
The target release for the Multimedia specifications is (in general) R99, and the specifications apply to UMTS as well as GSM. |
24.002 | GSM - UMTS Public Land Mobile Network (PLMN) Access Reference Configuration | TS | 3.1.1 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.002/24002-311.zip | |
23.140 | Multimedia Messaging Service (MMS); Functional description; Stage 2 | TS | 3.1.0 | CP | https://www.3gpp.org/ftp/Specs/archive/23_series/23.140/23140-310.zip | The present document defines the stage 2 and stage 3 description of the non-realtime Multimedia Messaging Service, MMS. Stage 2 identifies the functional capabilities and information flows needed to support the service described in stage 1.
The present document includes information applicable to network operators, service providers and terminal, switch and database manufacturers.
The present document contains the core functions for a non realtime Multimedia Messaging Service, MMS, which are sufficient to provide a basic service.
MMS uses a number of technologies to realise the requirements of the stage 1 description (3G TS 22.140) [1]. The present document describes how the service requirements are realised with the selected technologies. As far as possible existing protocols (e.g. WAP, SMTP, ESMTP as transfer protocols; lower layers to provide push, pull, notification) and existing message formats (e.g. SMIL, MIME) shall be used for the realisation of the Multimedia Messaging Service.
The present document serves as a foundation for the development of MMS. It describes a new service which has no direct equivalent in the previous ETSI/GSM world or in the fixed network world. In consequence readers may find that certain aspects are not clearly defined or open to misinterpretation. Where any such case is encountered it is essential that the issue is brought to the 3GPP TSG T2 standards body (see page 2 for contact information) for discussion and resolution in order to provide interoperable implementations. |
24.007 | Mobile radio interface signalling layer 3; General Aspects | TS | 3.10.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.007/24007-3a0.zip | |
24.010 | Mobile radio interface layer 3; Supplementary services specification; General aspects | TS | 3.2.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.010/24010-320.zip | |
24.011 | Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface | TS | 3.6.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.011/24011-360.zip | |
24.022 | Radio Link Protocol (RLP) for circuit switched bearer and teleservices | TS | 3.5.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.022/24022-350.zip | |
24.030 | Location Services (LCS); Supplementary service operations; Stage 3 | TS | 3.3.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.030/24030-330.zip | |
24.067 | Enhanced Multi-Level Precedence and Pre-emption service (eMLPP); Stage 3 | TS | 3.2.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.067/24067-320.zip | |
24.072 | Call Deflection (CD) supplementary service; Stage 3 | TS | 3.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.072/24072-300.zip | |
24.081 | Line Identification supplementary services; Stage 3 | TS | 3.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.081/24081-310.zip | |
24.082 | Call Forwarding (CF) supplementary services; Stage 3 | TS | 3.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.082/24082-300.zip | |
24.083 | Call Waiting (CW) and Call Hold (HOLD) supplementary services; Stage 3 | TS | 3.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.083/24083-300.zip | |
24.084 | Multi Party (MPTY) supplementary service; Stage 3 | TS | 3.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.084/24084-300.zip | |
24.085 | Closed User Group (CUG) supplementary service; Stage 3 | TS | 3.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.085/24085-300.zip | |
24.086 | Advice of Charge (AoC) supplementary services; Stage 3 | TS | 3.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.086/24086-300.zip | |
24.087 | User-to-User Signalling (UUS) Supplementary Service; Stage 3 | TS | 3.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.087/24087-300.zip | |
24.088 | Call Barring (CB) supplementary service; Stage 3 | TS | 3.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.088/24088-300.zip | |
24.090 | Unstructured Supplementary Service Data (USSD); Stage 3 | TS | 3.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.090/24090-300.zip | |
24.091 | Explicit Call Transfer (ECT) supplementary service; Stage 3 | TS | 3.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.091/24091-300.zip | |
24.093 | Completion of Calls to Busy Subscriber (CCBS); Stage 3 | TS | 3.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.093/24093-300.zip | |
24.096 | Name Identification supplementary services; Stage 3 | TS | 3.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.096/24096-300.zip | |
24.135 | Multicall supplementary service; Stage 3 | TS | 3.2.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.135/24135-320.zip | |
25.101 | User Equipment (UE) radio transmission and reception (FDD) | TS | 3.19.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.101/25101-3j0.zip | |
25.104 | Base Station (BS) radio transmission and reception (FDD) | TS | 3.14.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.104/25104-3e0.zip | |
25.105 | Base Station (BS) radio transmission and reception (TDD) | TS | 3.16.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.105/25105-3g0.zip | |
25.113 | Base station (BS) and repeater electromagnetic compatibility (EMC) | TS | 3.5.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.113/25113-350.zip | |
25.141 | Base Station (BS) conformance testing (FDD) | TS | 3.15.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.141/25141-3f0.zip | |
25.142 | Base Station (BS) conformance testing (TDD) | TS | 3.15.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.142/25142-3f0.zip | |
25.201 | Physical layer - general description | TS | 3.4.0 | RP | https://www.3gpp.org/ftp/Specs/archive/25_series/25.201/25201-340.zip | |
25.211 | Physical channels and mapping of transport channels onto physical channels (FDD) | TS | 3.12.0 | RP | https://www.3gpp.org/ftp/Specs/archive/25_series/25.211/25211-3c0.zip | |
24.080 | Mobile radio interface layer 3 supplementary services specification; Formats and coding | TS | 3.7.1 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.080/24080-371.zip | The present document contains the coding of information necessary for support of supplementary service operation on the mobile radio interface layer 3.
Clause 2 gives the functional definitions and contents of messages for call independent supplementary service operations. Messages necessary for support of call related supplementary service operations are defined in TS 24.008.
Clause 3 gives the general format and coding for messages used for call independent supplementary service and the format and coding of information elements used for both call related and call independent supplementary service operations.
Clause 4 gives the specification of the call related and call independent supplementary service operations. |
25.212 | Multiplexing and channel coding (FDD) | TS | 3.11.0 | RP | https://www.3gpp.org/ftp/Specs/archive/25_series/25.212/25212-3b0.zip |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.