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 |
|---|---|---|---|---|---|---|
04.63 | Packet Data on Signalling channels Service (PDS) Service Description, Stage 3 | TS | 8.0.1 | C1 | https://www.3gpp.org/ftp/Specs/archive/04_series/04.63/0463-801.zip | The present document specifies the protocols for connection management of packet data on signalling channels which is applied on the air interface, the PDSS1 protocol and the PDSS2 protocol. |
07.01 | General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS) | TS | 8.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/07_series/07.01/0701-800.zip | This TS is based on the principles of terminal adaptor functions presented in the CCITT I-series of recommendations (I.460 - I.463).
The GSM PLMN supports a wide range of voice and non-voice services in the same network. In order to enable non-voice traffic in the GSM PLMN there is a need to connect various kinds of terminal equipments to the Mobile Termination (MT). The target of this ETS is to outline the functions needed for the terminal adaptation.
In the GSM 02.02 (ETS 300 904) the bearer services are described. The general network configuration is described in GSM 03.02 and the GSM PLMN access reference configuration is defined in GSM 04.02. The various connection types used in the GSM PLMN are presented in GSM 03.10. Terminology used in this ETS is presented in GSM 01.04 (ETR 350). For support of data services between GSM PLMN and other networks see GSM 09-series of Specifications. |
07.02 | Terminal Adaptation Functions (TAF) for Services Using Asynchronous Bearer Capabilities | TS | 8.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/07_series/07.02/0702-800.zip | |
07.03 | Terminal Adaptation Functions (TAF) for Services Using Synchronous Bearer Capabilities | TS | 8.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/07_series/07.03/0703-800.zip | This Technical Specification (TS) defines Terminal Adaptation Functions (TAF) which are integrated in a Mobile Termination (MT) and which enable the attachment of Synchronous Terminals to an MT (see GSM 04.02 [4]). The general aspects of Terminal Adaptation Functions are contained in specification GSM 07.01 [8]. This ETS covers support of synchronous data services (see GSM 02.02 [2]) for the following interfaces and procedures:
‑ V.22 DTE/DCE Interface
‑ V.22 bis DTE/DCE Interface
‑ V.26 ter DTE/DCE Interface
‑ V.32 DTE/DCE Interface
‑ X.21 DTE/DCE Interface
‑ X.21 bis DTE/DCE Interface
‑ X.25 Procedure
‑ X.32 Procedure
‑ V.25 bis Procedure
‑ I.420 Interface (S)
LAPB is the only synchronous non‑transparent protocol which is considered here. |
07.08 | GSM Application Programming Interface | TS | 8.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/07_series/07.08/0708-800.zip | This European Telecommunication Standard (ETS) defines the GSM Application Programming Interface (GSM‑API) in two parts.
The first part describes, how compatibility to existing application interface ETS 300 838 [14] is covered for the GSM network. So existing PCI applications are able to be used in a GSM environment. For these applications the necessary mapping and local knowledge between application interface and network is described. The only modifications needed in ETS 300 838 [14] to fulfil this requirements are covered by changes of the parameter description. These changes of parameters are defined in clauses 4 and 5 of this ETS.
An application compliant with this ETS shall not imply compliance with ETS 300 838 (HPCI).
Clause 4 is meant to replace subclause 5.7 message parameters of ETS 300 838 [14]. which defines the parameters of the profile A of the HPCI.
NOTE 1: Clause 4is for further study.
Clause 5 replaces subclause 6.8 parameter description of ETS 300 838, which defines the parameters of the profile B of the HPCI.
The second part defines GSM specific features. New GSM‑API applications need extensions to ETS 300 838 [14] which are defined in section 6 and 7of this ETS.
These sections are meant as an addition to ETS 300 838 [14]. They do not replace any clause of ETS 300 838 [14].
Clause 6 defines the extensions according to the profile A of ETS 300 838 [14].
NOTE 2: Clause 6 is for further study.
Clause 7 defines the extensions according to the profile B of ETS 300 838 [14] (bit compatible to COMMON ISDN API).
The messages and the operating system dependent part of ETS 300 838 [14] will not be changed for GSM‑API. |
09.07 | General Requirements on Interworking between the Public Land Mobile Network (PLMN) and the Intergrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN) | TS | 8.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/09_series/09.07/0907-800.zip | This TS identifies the Mobile‑services Switching Centre/Interworking Functions (MSC/IWFs) and requirements to support interworking between:
a) PLMN and PSTN
b) PLMN and ISDN
It is not possible to treat ISDN and PSTN as one type of network, even when both ISDN and PSTN subscribers are served by the same exchange because of the limitations of the PSTN subscribers access i.e. analogue connection without D‑channel signalling.
Within this TS, the requirements for voice and non‑voice (data) calls are considered separately. |
09.14 | Application of ISDN User Part (ISUP) Version 3 for the Integrated Services Digital Network (ISDN) - Public Land Mobile Network (PLMN) signalling interface; Part 1: Protocol specification | TS | 8.0.0 | - | https://www.3gpp.org/ftp/Specs/archive/09_series/09.14/0914-800.zip | The present document specifies the third version of the Integrated Services Digital Network (ISDN) - Global System for Mobile communications (GSM) Public Land Mobile Network (PLMN) signalling interface. The present document is applicable to the interconnection of PLMN and ISDN.
The ISUP interface defined is the trunk signalling interface between the PLMN and the ISDN. It is assumed that the interface between PLMN and ISDN can occur at any point in a national network, provided that the exchange in the national network has this ISDN-PLMN signalling interface.
This signalling interface is based on ISUP version 3 (as given in EN 300 356-1 [1] to EN 300 356-20 [19]). The functionality in the GSM system is based on GSM Phase 2+ Release 1998.
NOTE 1: Support of new functionality in the GSM system applicable for this interface may be included in subsequent versions of the present document or may be published as a new EN.
Connection types:
The following ISUP version 3 connection types can be supported:
- speech;
- 3,1 kHz audio;
- 64 kbit/s unrestricted;
- 64 kbit/s unrestricted preferred;
- 2 64 kbit/s unrestricted;
- 384 kbit/s unrestricted;
- 1 536 kbit/s unrestricted;
- 1 920 kbit/s unrestricted.
NOTE 2: 2 64 kbit/s, 384 kbit/s, 1 536 kbit/s, 1 920 kbit/s unrestricted and 64 kbit/s unrestricted preferred connection types are not supported by the GSM access, however the connection types may be used in order to support other access methods via the GSM network.
Supplementary services:
The following ISUP version 3 supplementary services can be supported:
- Calling Line Identification Presentation (CLIP)/
Calling Line Identification Restriction (CLIR);
- Connected Line Identification Presentation (COLP)/
Connected Line Identification Restriction (COLR);
- Terminal portability (TP);
- User-to-User Signalling (UUS);
- Closed User Group (CUG);
- Subaddressing (SUB);
- Malicious Call Identification (MCID);
- Conference call, add-on (CONF);
- Explicit Call Transfer (ECT);
- Call Forwarding Unconditional (CFU)/
Call Forwarding on Busy (CFB)/
Call Forwarding on No Reply (CFNR);
- Call Deflection (CD);
- Call Hold (HOLD);
- Call Waiting (CW);
- Completion of Calls to Busy Subscriber (CCBS);
- Completion of Calls on No Reply (CCNR);
- Three party (3PTY).
The support of supplementary services on this interface does not necessarily imply that the supplementary services are supported in one or the other of the networks interconnected.
The Direct Dialling In (DDI) supplementary service and Multiple Subscriber Number (MSN) supplementary service have no impact on this interface.
This interface can be used within national networks, however messages and parameters that are marked for national use in EN 300 356-1 [1] are not described in the present document. |
09.18 | General Packet Radio Service (GPRS); Serving GPRS Support Node (SGSN) - Visitors Location Register (VLR); Gs interface layer 3 specification | TS | 8.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/09_series/09.18/0918-800.zip | The present document specifies or references procedures used on the Serving GPRS Support Node (SGSN) to Visitors Location Register (VLR) interface for interoperability between GSM circuit switched services and GSM packet data services.
The present document specifies the layer 3 messages and procedures on the Gs interface to allow coordination between databases and to relay certain messages related to GSM circuit switched services over the GPRS subsystem.
The functional split between VLR and SGSN is defined in GSM 03.60. The required procedures between VLR and SGSN are defined in detail in the present document. |
10.57 | Project scheduling and open issues: Mobile Station Execution Environment (MExE) | TR | 8.0.0 | T2 | https://www.3gpp.org/ftp/Specs/archive/10_series/10.57/1057-800.zip | The purpose of this document is to describe the project plan for the Mobile Station Execution Environment (MEXE) work item standardisation.
This document is a ‘living document’ and permanently updated by PT SMG. Proposals for change shall be forwarded to PT SMG, where the latest version can be obtained any time. The MEXE specification rapporteurs should make sure that this document can always reflects the latest status of work. |
10.76 | Noise suppression for the AMR codec; Project scheduling and open issues | TR | 1.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/10_series/10.76/1076-100.zip | The purpose of this document is to describe the schedule of the standardisation process for the Noise Suppression feature for the Adaptive Multi Rate Codec and to define open issues that are still under discussion. It also lists the new standards and necessary amendments to the GSM/DCS phase 2+ specifications for the technical realisation of the function.
The new standards and Change Requests (CR) necessary for this feature are listed in clause 9. |
11.10-2 | Mobile station (MS) conformance specification; Part 2: Protocol Implementation Conformance Statement (PICS) proforma specification | TS | 8.0.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/11_series/11.10-2/1110-2-800.zip | The present document provides the Protocol Implementation Conformance Statement (PICS) proforma for Global System for Mobile Stations (MSs), operating in the 900 MHz and 1 800 MHz frequency band (GSM 900 and DCS 1 800) within the European digital cellular telecommunications system (Phase 2), in compliance with the relevant requirements, and in accordance with the relevant guidance given in ISO/IEC 9646‑7 [3] and ETS 300 406 [1]. |
11.10-3 | Mobile Station (MS) conformance specification; Part 3: Layer3 (L3) Abstract Test Suite (ATS) | TS | 8.0.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/11_series/11.10-3/1110-3-800.zip | The present document specifies the Abstract Test Suites (ATS) and partial IXIT proforma for the Network Layer (Layer 3) at the mobile radio interface of the GSM or DCS (Phase 2+) mobile stations (MS) conforming to the ENs for Layer 3, cell selection, Enhanced Full Rate Speech, Multi-band, GSM-R band (R-GSM) and ASCI ( the voice group call service (VGCS), voice broadcast service (VBS), enhanced Multi-Level Precedence and Pre-emption service (eMLPP), User-to-user Signalling (UUS) service and the Follow Me service) for the digital cellular telecommunications systems.
This EN is valid for MS implemented according Phase2 or Phase2+ R96, or R97, or R98, or R99, or R00.
The ISO standards for the methodology of conformance testing and the TTCN language are used as the basis for the test specifications. |
11.18 | Specification of the 1.8 Volt Subscriber Identity Module - Mobile Equipment (SIM - ME) Interface | TS | 8.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/11_series/11.18/1118-800.zip | The present document defines the aspects of the Subscriber Identity Module - Mobile Equipment (SIM - ME) interface which are based on 1.8V technology to be used in the Mobile Station (MS). It specifies the electrical and logical requirements necessary for the operation of the 1.8V SIM - ME interface where it differs from GSM 11.11 [1]. For all aspects of the SIM - ME interface which are not covered by the present document, GSM 11.11 [1] applies. |
21.810 | Report on multi-mode UE issues; ongoing work and identified additional work | TR | 3.0.0 | T2 | https://www.3gpp.org/ftp/Specs/archive/21_series/21.810/21810-300.zip | This 3GPP Technical Report identifies the work done in other working groups within 3GPP and SMG concerning Multi-mode UEs. The report is related to TR 21.910 [38] which identifies multi-mode User Equipments categories and also describes the general principles and procedures for the multi-mode operation standardised in the 3GPP specifications.
The present report describes the status of the work as of February 2000. |
22.043 | Support of Localized Service Area (SoLSA); Service description; Stage 1 | TS | 3.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.043/22043-310.zip | This technical specification, specifies a mechanism, which can be used as a platform for providing special tariffs and/or special set of service features for certain subscribers within a regionally restricted area or areas.
The motivation for this concept is to create means for network operators to build new service and tariff packages, which take into account subscriber groups and their needs.
The localised service area is both an optional network feature and an optional UE feature. Usage and implementation of the different SoLSA service features may vary according to operator's service packages.
This feature is not intended to replace the existing method of cell selection, cell indication and handover.
“Support of Localised service area (SoLSA)” is renamed Phase 2+ item “Support of Home Area Priority”
Note: The present document covers description for GERAN support only. UTRAN support will be added in latter releases. |
22.053 | Tandem Free Operation (TFO); Service description; Stage 1 | TS | 3.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.053/22053-300.zip | |
22.907 | Terminal concepts | TR | 3.1.3 | - | https://www.3gpp.org/ftp/Specs/archive/22_series/22.907/22907-313.zip | This document is informative and applicable to standardisation work within ETSI SMG for UMTS. It discusses the issues related to terminal and smart card concepts in the UMTS environment. The report will provide guidance and input to the SMG specification work in the area of UMTS terminals and IC cards used for containing UMTS information and accessing UMTS services. It presents various options on the roles relating to IC cards and terminals as well as discussing their relationship in UMTS. |
22.924 | Charging and accounting mechanisms | TR | 3.1.1 | - | https://www.3gpp.org/ftp/Specs/archive/22_series/22.924/22924-311.zip | This document outlines the requirements and proposed new mechanisms to be used for billing and charging in UMTS. This document is a basis for discussion during the standardisation work within ETSI SMG for UMTS. |
22.925 | Quality of Service (QoS) and network performance | TR | 3.1.1 | - | https://www.3gpp.org/ftp/Specs/archive/22_series/22.925/22925-311.zip | This TR identifies the parameters and parameter values which are to be used as targets when producing UMTS standards and which are to serve as guidelines to operators and service providers for network design and service provision. |
22.960 | Mobile multimedia services | TR | 3.0.1 | - | https://www.3gpp.org/ftp/Specs/archive/22_series/22.960/22960-301.zip | This document discusses the issues related to mobile multimedia in UMTS environment. Specifically the foreseen mobile multimedia applications and their special requirements are referred briefly. The major technical challenges faced in the provision of multimedia services and Internet and Intranet access are discussed and highlighted in order to give guidance for UMTS system standardisation.
This document contains various views into these future topics and cannot be regarded as complete. |
22.970 | Virtual Home Environment (VHE) Report | TR | 3.0.1 | - | https://www.3gpp.org/ftp/Specs/archive/22_series/22.970/22970-301.zip | This document describes the Virtual Home Environment (VHE) concept and its constituent parts. It aims to identify how VHE will be realised.
A concept called Service Environment is introduced to describe how VHE services will be made available on demand to a user travelling with her terminal in any location.
The concept of Virtual Terminal is discussed to describe how VHE can be made available in any terminal. |
22.972 | Circuit-switched multimedia | TR | 0.0.0 | - | https://www.3gpp.org/ftp/Specs/archive/22_series/22.972/22972-000.zip | This TR describes how to realise the SMG1 requirements for real time multimedia services in UMTS (Ref 22.60). Specifically the TR covers
1) the extent of standardization required for multimedia in UMTS;
2) the functional distribution in the UMTS network and associated applications;
3) impact of the functional distribution on user terminals (for instance, hand-held, phone with a PC, and others);
4) impact of the functional distribution on Core and Access network. |
23.010 | GSM Public Land Mobile Network (PLMN) Connection Types | TS | 3.0.0 | - | https://www.3gpp.org/ftp/Specs/archive/23_series/23.010/23010-300.zip | |
23.022 | Functions related to Mobile Station (MS) in idle mode and group receive mode | TS | 3.1.0 | - | https://www.3gpp.org/ftp/Specs/archive/23_series/23.022/23022-310.zip | This TS gives an overview of the tasks undertaken by a GSM Mobile Station (MS) when in idle mode, that is, switched on but not having a dedicated channel allocated, e.g. not making or receiving a call, or when in group receive mode, that is, receiving a group call or broadcast call but not having a dedicated connection. It also describes the corresponding network functions. The idle mode functions are also performed by a GPRS MS as long as no dedicated channel is allocated to the MS. The idle mode functions are also performed by a CTS MS as long as the CTS MS is in manual mode GSM only or in automatic mode under PLMN coverage.
NOTE: The term GSM MS is used for any type of MS supporting one, or combinations, of the frequency bands specified in GSM 05.05.
This ETS outlines how the requirements of the GSM 02 series Technical Specifications (especially GSM 02.11) on idle mode operation shall be implemented. Further details are given in GSM 04.08 and GSM 05.08.
Clause 2 of this TS gives a general description of the idle mode process. Clause 3 outlines the main requirements and technical solutions of those requirements. Clause 4 describes the processes used in idle mode. There is inevitably some overlap between these clauses. Clause 5 describes the cell change procedures for a MS in group receive mode. |
23.043 | Support of Videotex | TS | 3.0.0 | - | https://www.3gpp.org/ftp/Specs/archive/23_series/23.043/23043-300.zip | |
23.044 | Support of Teletex | TS | 3.0.0 | - | https://www.3gpp.org/ftp/Specs/archive/23_series/23.044/23044-300.zip | |
23.045 | Technical Realization of Facsimile Group 3 Service - transparent | TS | 3.0.0 | N3 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.045/23045-300.zip | |
23.046 | Technical realisation of facsimile Group 3 service - non-transparent | TS | 3.0.0 | - | https://www.3gpp.org/ftp/Specs/archive/23_series/23.046/23046-300.zip | |
23.054 | Shared Interworking Functions (SIWF); Stage 2 | TS | 3.0.0 | N3 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.054/23054-300.zip | |
23.069 | Voice Broadcast service (VBS); Stage 2 | TS | 3.0.0 | N1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.069/23069-300.zip | |
23.070 | Routeing of calls to/from Public Data Networks (PDN) and the GSM Public Land Mobile Network (PLMN) | TS | 3.0.0 | - | https://www.3gpp.org/ftp/Specs/archive/23_series/23.070/23070-300.zip | |
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 | |
26.955 | 5G Video Codec Characteristics | TR | 19.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.955/26955-j00.zip | |
25.101 | User Equipment (UE) radio transmission and reception (FDD) | TS | 19.0.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/25_series/25.101/25101-j00.zip | |
38.104 | NR; Base Station (BS) radio transmission and reception | TS | 19.3.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/38_series/38.104/38104-j30.zip | |
31.124 | Mobile Equipment (ME) conformance test specification; Universal Subscriber Identity Module Application Toolkit (USAT) conformance test specification | TS | 18.5.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.124/31124-i50.zip | |
23.700-15 | Study on Use of sensing results for Vertical Applications | TR | 1.0.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-15/23700-15-100.zip | |
23.700-26 | Study on application enablement for Ambient IoT services | TR | 1.0.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-26/23700-26-100.zip | |
23.700-43 | Study on CAPIF Phase 4 | TR | 1.0.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-43/23700-43-100.zip | |
23.700-44 | Study on application enablement to support energy saving | TR | 1.0.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-44/23700-44-100.zip | |
23.700-57 | Study on Stage 2 for MMTel Phase 2 | TR | 1.0.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-57/23700-57-100.zip | |
23.947 | Guidelines for 3GPP Application Enablement usage | TR | 1.0.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.947/23947-100.zip | |
36.719-01-01 | LTE REL-19 CA for x bands (1<=x<=6)DL with y bands (y=1,2) UL | TR | 0.7.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/36_series/36.719-01-01/36719-01-01-070.zip | The present document is a technical report on intra-band CA and inter-band CA for x bands DL (1≤x≤6) with y bands UL (y=1,2) under Rel-19 timeframe.
The purpose is to gather the relevant background information and studies, in order to address Rel-19 band combinations that are related to x bands (1≤x≤6) DL with y bands UL (y=1,2) bands UL CA requirements. The band combinations are requested in the Excel file of the WID [2] or its revisions. |
33.900 | Guide to 3G security | TR | 0.4.1 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.900/33900-041.zip |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.