id stringlengths 5 12 | title stringlengths 8 250 | type stringclasses 2 values | version stringclasses 561 values | working_group stringclasses 30 values | url stringlengths 67 81 | scope stringlengths 0 65.7k |
|---|---|---|---|---|---|---|
23.073 | Support of Localised Service Area (SoLSA); Stage 2 | TS | 3.0.1 | N4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.073/23073-301.zip | The present document specifies the stage 2 description of the SoLSA service, which gives the network operator the basis to offer subscribers or group of subscribers different services, different tariffs and different access rights depending on the geographical location of the subscriber, according to GSM 02.43. |
23.920 | Evolution of the GSM platform towards UMTS | TS | 3.1.0 | - | https://www.3gpp.org/ftp/Specs/archive/23_series/23.920/23920-310.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.922 | Architecture for an All IP network | TR | 1.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.922/23922-100.zip | This technical report will propose an architecture that provisions an all-IP architecture option for release 00. The purpose of the technical report is to
• identify key issues and affected ongoing 3GPP work that need to be resolved and
• propose a high level work plan for completion of an all IP release 00 UMTS standard
in order to provide this architectural option within Release 2000. |
23.927 | VHE, Open Service Architecture (OSA) | TR | 0.1.0 | - | https://www.3gpp.org/ftp/Specs/archive/23_series/23.927/23927-010.zip | This ETSI Technical Specification (TS) describes the Open Service Architecture for the Universal Mobile Telecommunications System (UMTS).
The goal of standardisation in UMTS with respect to Virtual Home Environment (VHE) services is to provide a framework within which services can be created based on standardised service features. The Open Service Architecture described in thes document provides this framework for implementing services based on service features, which in turn are based on service capabilities. As an advanced option it is possible to implement services directly based on service capabilities. |
24.012 | Short Message Service Cell Broadcast (SMSCB) Support on the Mobile Radio Interface | TS | 3.0.0 | G2 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.012/24012-300.zip | This TS describes how the Short Message Service Cell Broadcast (SMSCB) (Teleservice 23 as specified in GSM 02.03) is supported over the mobile radio interface. |
24.065 | General Packet Radio Service (GPRS); Mobile Station (MS) - Serving GPRS Support Node (SGSN); Subnetwork Dependent Convergence Protocol (SNDCP) | TS | 3.1.0 | N1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.065/24065-310.zip | The present document provides the description of the Subnetwork Dependent Convergence Protocol (SNDCP) for the General Packet Radio Service (GPRS).
The user of the services provided by SNDCP is a packet data protocol (PDP) at the mobile Station (MS) or the Relay at the Serving GPRS Support Node (SGSN). Additionally, a control entity, e.g., AT command interpreter, may be an SNDCP user. SNDCP uses the services provided by the Logical Link Control (LLC) layer 4 and the Session Management (SM) sub-layer 2.
The main functions of SNDCP are:
- Multiplexing of several PDPs.
- Compression / decompression of user data.
- Compression / decompression of protocol control information.
- Segmentation of a network protocol data unit (N‑PDU) into Logical Link Control Protocol Data Units (LL‑PDUs) and re-assembly of LL‑PDUs into a N‑PDU.
GSM 04.65 is applicable to GPRS MS and SGSN. |
24.068 | Group Call Control (GCC) Protocol | TS | 3.1.0 | N1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.068/24068-310.zip | This TS specifies the Group Call Control (GCC) protocol used by the Voice Group Call Service (VGCS) on the radio interface. |
24.069 | Broadcast Call Control (BCC) protocol | TS | 3.1.0 | N1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.069/24069-310.zip | |
25.103 | RF parameters in support of RRM | TS | 2.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.103/25103-200.zip | This Technical Specification shall describe RF parameters and Requirements for the Radio Resource Management. |
25.231 | Physical layer - Measurements | TS | 0.3.0 | R1 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.231/25231-030.zip | |
25.831 | Study Items for future release | TR | 0.0.2 | R3 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.831/25831-002.zip | |
25.926 | UE Radio Access capabilities definition | TR | 3.3.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.926/25926-330.zip | The present document identifies the parameters of the access stratum part of the UE radio access capabilities. Furthermore, some reference configurations of these values are defined. The intention is that these configurations will be used for test specifications. |
25.990 | Vocabulary for UTRAN | TR | 3.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.990/25990-300.zip | This document is a collection of terms, definitions and abbreviations related to the baseline documents defining 3GPP objectives and systems framework. This document provides a tool for further work on 3GPP technical documentation and facilitates their understanding.
The terms, definitions and abbreviations as given in this document are either imported from existing documentation (ETSI, ITU or elsewhere) or newly created by 3GPP experts whenever the need for precise vocabulary was identified. |
26.075 | Performance characterization of the Adaptive Multi-Rate (AMR) speech codec | TS | 1.2.0 | - | https://www.3gpp.org/ftp/Specs/archive/26_series/26.075/26075-120.zip | This is the first version of the technical report providesing background information on the performances of the GSM Adaptive Multi-Rate (AMR) speech codec. Experimental test results from the Verification and Characterization phases of testing are reported to illustrate the behavior of the GSM AMR in multiple operational conditions. |
26.112 | Codec(s) for Circuit Switched Multimedia Telephony Service; Call Set-up Requirements | TS | 1.1.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.112/26112-110.zip | This technical specification describes the call-set-up requirements and related circuit switched call control procedures for ITU-T H.324 based multimedia service within GSM/3GPP networks and with external telecommunications networks. |
26.115 | Echo control for speech and multimedia services | TS | 0.0.1 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.115/26115-001.zip | |
26.913 | Quantitative performance evaluation of real-time packet switched multimedia services over 3G | TR | 0.0.1 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.913/26913-001.zip | |
28.062 | Inband Tandem Free Operation (TFO) of speech codecs; Service description; Stage 3 | TS | 3.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.062/28062-300.zip | |
29.004 | Interworking between the Public Land Mobile Network (PLMN) and the Circuit Switched Public Data Network (CSPDN) | TS | 3.0.0 | N3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.004/29004-300.zip | |
29.005 | Interworking between the Public Land Mobile Network (PLMN) and the Packet Switched Public Data Network (PSPDN) for Packet Assembly/Disassembly (PAD) facility access | TS | 3.0.0 | N3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.005/29005-300.zip | |
29.006 | Interworking between a PLMN and the ISDN or PSTN for support of Packet Switched data transmission services | TS | 3.0.0 | N3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.006/29006-300.zip | |
32.106 | Configuration Management | TS | 3.0.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.106/32106-301.zip | The present document describes the Configuration Management (CM) aspects of managing a 3G network. This is described from the management perspective outlined in the two 3GPP specifications 32.101 [1] and 32.102 [2].
The present document defines a set of controls to be employed to effect set-up and changes to a 3G network in such a way that operational capability and quality of service, network integrity and system inter working are ensured. In this way, the present document describes the interface definition and behaviour for the management of relevant 3G network NEs in the context of the described management environment. The context is described for both the management systems (OS) and NE functionality.
Clause 7 contains the specific definitions for the standardised N-interface, which are necessary to follow for compliance to this specification. |
32.111 | 3G Fault Management | TS | 3.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.111/32111-320.zip | The present document specifies the overall requirements for 3G Fault Management as it applies to the NE, EM and NM.
Clauses 4 and 5 define the fault management concept and functional requirements for the detection of faults and the generation, collection and presentation of alarms, operational state data and test results across 3G systems. These functions are described on a non-formal level since the formal standardisation of these functions across the different vendors' equipment is not required. The functional areas to be specified in this part of the document cover:
• fault surveillance and detection in the NEs;
• notification of alarms (including alarm cease) and operational state changes;
• retrieval of current alarms from the NEs;
• fault isolation and defence mechanisms in the NEs;
• alarm filtering;
• management of alarm severity levels;
• alarm and operational state data presentation and analysis at the OS;
• retention of alarm and operational state data in the NEs and the OS; and
• the management of tests.
Any (re)configuration activity exerted from the OMC as a consequence of faults will not be subject of the present document, these are described in [1].
Clauses 6 and 7 of the present document describe specific aspects of the Fault Management for the UTRAN and the CN, respectively, with particular emphasis on the exact fault definitions and alarm information to be generated. The definition of the test procedures and the relationship with the UTRAN resp. CN management architecture as defined in [3].
Finally, Clause 8 of the present document defines the functional requirements for the standard Itf-N, for the purpose of Fault Management of 3G networks, as seen from the Network Manager (NM). The Itf-N is fully standardised so as to connect systems of any vendor to the NM via this interface. |
33.900 | Guide to 3G security | TR | 1.2.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.900/33900-120.zip | |
33.909 | 3G Security; Report on the design and evaluation of the MILENAGE algorithm set; Deliverable 5: An example algorithm for the 3GPP authentication and key generation functions | TR | 3.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.909/33909-300.zip | This public report contains a detailed summary of the work performed during the design and evaluation of the 3GPP Authentication Functions denoted as the MILENAGE algorithm set. It contains all results and findings from this work and should be read as a supplement to the specifications of the algorithms in ref. [3] and the general project report, ref. [4]. |
35.205 | 3G Security; Specification of the MILENAGE algorithm set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1*, f2, f3, f4, f5 and f5*; Document 1: General | TS | 3.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.205/35205-300.zip | This report is a description of the work undertaken by an ETSI SAGE Task Force on the design of the Milenage Algorithm Set: an example set of 3GPP Authentication and Key Generation Functions.
The 3GPP Authentication and Key Generation Functions are not standardized. An example set of these algorithms has been produced on request from 3GPP with the intent that it shall be offered to the UMTS operators, to utilise instead of developing their own. An ETSI SAGE Task Force has carried out this work.
The requirement specification from 3GPP stated that operator personalisation of the example set shall be possible and that the basic kernel shall be possible to replace.
The example set is based on the block cipher Rijndael, which at the time was one of the AES candidates and the specification describes how the 7 algorithms used in 3GPP authentication and key generation are scheduled around this basic kernel. The specification and associated test data for the example algorithm set is documented in three documents:
- A formal specification of both the modes and the example kernel [3]
- A detailed test data document, covering modes and the example kernel [4]
- A "black box" test data document [5]
A detailed summary of the evaluation is provided in a public evaluation report [6]
This report gives an overview of the overall work by the task force. |
35.206 | 3G Security; Specification of the MILENAGE algorithm set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1*, f2, f3, f4, f5 and f5*; Document 2: Algorithm specification | TS | 3.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.206/35206-300.zip | |
35.207 | 3G Security; Specification of the MILENAGE algorithm set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1*, f2, f3, f4, f5 and f5*; Document 3: Implementors' test data | TS | 3.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.207/35207-300.zip | |
35.208 | 3G Security; Specification of the MILENAGE algorithm set: An example algorithm set for the 3GPP authentication and key generation functions f1, f1*, f2, f3, f4, f5 and f5*; Document 4: Design conformance test data | TS | 3.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/35_series/35.208/35208-300.zip |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.