id
stringlengths 5
12
| title
stringlengths 8
250
| type
stringclasses 2
values | version
stringclasses 222
values | working_group
stringclasses 30
values | url
stringlengths 67
81
| scope
stringlengths 0
65.7k
|
|---|---|---|---|---|---|---|
06.42
|
Voice Activity Detection (VAD) for Half Rate Speech Traffic Channels
|
TS
|
8.0.1
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/06_series/06.42/0642-801.zip
|
The present document specifies the Voice Activity Detector (VAD) to be used in the Discontinuous Transmission (DTX) as described in GSM 06.41 [4]. It also specifies the test methods to be used to verify that a VAD implementation complies with the present document.
The requirements are mandatory on any VAD to be used either in GSM Mobile Stations (MS)s or Base Station Systems (BSS)s that utilize the half‑rate GSM speech traffic channel.
|
06.51
|
GSM Enhanced full rate speech processing functions: General description
|
TS
|
8.2.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/06_series/06.51/0651-820.zip
|
The present document is an introduction to GSM 06.60 [6], GSM 06.61 [7], GSM 06.62 [8], GSM 06.81 [9] and GSM 06.82 [10] ENs dealing with the speech processing functions in the Enhanced Full Rate channel of the GSM system. A general overview of the speech processing functions is given, with reference to the ENs where each function is specified in detail.
|
06.53
|
ANSI-C code for the GSM Enhanced Full Rate (EFR) speech codec
|
TS
|
8.0.1
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/06_series/06.53/0653-801.zip
|
The present document contains an electronic copy of the ANSI‑C code for the GSM Enhanced Full Rate codec. The ANSI‑C code is necessary for a bit exact implementation of the Enhanced Full Rate speech transcoder (GSM 06.60 [3]), Voice Activity Detection (GSM 06.82 [7]), comfort noise (GSM 06.62 [5]), Discontinuous Transmission (GSM 06.81 [6]) and example solutions for substituting and muting of lost frames (GSM 06.61 [4]).
|
06.54
|
Test sequences for the GSM Enhanced Full Rate (EFR)
|
TS
|
8.2.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/06_series/06.54/0654-820.zip
|
The present document specifies the digital test sequences for the GSM enhanced full rate speech codec. These sequences test for a bit exact implementation of the enhanced full rate speech transcoder (GSM 06.60 [2]), Voice Activity Detection (GSM 06.82 [6]), comfort noise (GSM 06.62 [4]) and the discontinuous transmission (GSM 06.81 [5]).
|
06.55
|
Performance characterisation of the GSM EFR Speech Codec
|
TR
|
8.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/06_series/06.55/0655-800.zip
|
The present document gives background information on the performance of the GSM enhanced full rate speech codec. Experimental results from the Pre-selection and Verification tests carried out during the standardization process by the SEG (Speech Expert Group) are reported to give a more detailed picture of the behaviour of the GSM enhanced full rate speech codec under different conditions of operation.
|
06.60
|
Enhanced full rate speech transcoding
|
TS
|
8.0.1
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/06_series/06.60/0660-801.zip
|
The present document describes the detailed mapping between input blocks of 160 speech samples in 13‑bit uniform PCM format to encoded blocks of 244 bits and from encoded blocks of 244 bits to output blocks of 160 reconstructed speech samples. The sampling rate is 8 000 sample/s leading to a bit rate for the encoded bit stream of 12,2 kbit/s. The coding scheme is the so‑called Algebraic Code Excited Linear Prediction Coder, hereafter referred to as ACELP.
The present document also specifies the conversion between A‑law or -law (PCS 1900) PCM and 13‑bit uniform PCM. Performance requirements for the audio input and output parts are included only to the extent that they affect the transcoder performance. This part also describes the codec down to the bit level, thus enabling the verification of compliance to the part to a high degree of confidence by use of a set of digital test sequences. These test sequences are described in GSM 06.54 [7] and are available on disks.
In case of discrepancy between the requirements described in the present document and the fixed point computational description (ANSI‑C code) of these requirements contained in GSM 06.53 [6], the description in GSM 06.53 [6] will prevail.
The transcoding procedure specified in the present document is applicable for the enhanced full rate speech traffic channel (TCH) in the GSM system.
In GSM 06.51 [5], a reference configuration for the speech transmission chain of the GSM enhanced full rate (EFR) system is shown. According to this reference configuration, the speech encoder takes its input as a 13‑bit uniform PCM signal either from the audio part of the Mobile Station or on the network side, from the PSTN via an 8‑bit/A‑law or -law (PCS 1900) to 13‑bit uniform PCM conversion. The encoded speech at the output of the speech encoder is delivered to a channel encoder unit which is specified in GSM 05.03 [3]. In the receive direction, the inverse operations take place.
|
06.61
|
Substitution and muting of lost frames for encanced full rate speech traffic channels
|
TS
|
8.0.1
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/06_series/06.61/0661-801.zip
|
The present document defines a frame substitution and muting procedure which shall be used by the Receive (RX) Discontinuous Transmission (DTX) handler when one or more lost speech or Silence Descriptor (SID) frames are received from the Radio Sub System (RSS).
The requirements of the present document are mandatory for implementation in all GSM Base Station Systems (BSS)s and Mobile Stations (MS)s capable of supporting the enhanced Full Rate speech traffic channel. It is not mandatory to follow the bit exact implementation outlined in the present document and the corresponding C‑source code.
|
06.62
|
Comfort noise aspects for Enhanced Full Rate (EFR) speech traffic channels
|
TS
|
8.0.1
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/06_series/06.62/0662-801.zip
|
The present document gives the detailed requirements for the correct operation of the background acoustic noise evaluation, noise parameter encoding/decoding and comfort noise generation in Mobile Stations (MSs) and Base Station Systems (BSSs) during Discontinuous Transmission (DTX) on Enhanced Full Rate speech traffic channels.
The requirements described in the present document are mandatory for implementation in all GSM MSs capable of supporting the Enhanced Full Rate speech traffic channel.
The receiver requirements are mandatory for implementation in all GSM BSSs capable of supporting the Enhanced Full Rate speech traffic channel, the transmitter requirements only for those where downlink DTX will be used.
In case of discrepancy between the requirements described in the present document and the fixed point computational description of these requirements contained in GSM 06.53 [2], the description in GSM 06.53 [2] will prevail.
|
06.76
|
Adaptive Multi-Rate (AMR) speech codec; Study phase report
|
TR
|
8.0.1
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/06_series/06.76/0676-801.zip
|
The present document presents the outcome of the Study Phase initiated at SMG#20 on the concept of the Adaptive Multi-Rate (AMR) codec. The AMR concept represents a new approach to achieving consistent high quality speech combined with efficient spectrum usage. It was recognized at SMG#20 that this would require novel techniques whose feasibility should first be assessed before proceeding with a full development of the AMR system and its control.
Clauses 1 to 4 provide an overview and background to the AMR concept. Clause 5 provides a basic description of the AMR system functionality including working assumptions that have been agreed during the Study Phase. Feasibility aspects are considered in clause 6. The requirement specification, which will form the basis for the development phase, is contained in clause 7. Clause 8 gives an indication of the MS and network upgrades needed to support AMR. Clause 9 outlines how the AMR codec will be developed, tested and selected including the proposed time-plan. Clauses 10 and 11 conclude with a summary of the risks and recommendations.
|
06.77
|
Minimum Performance Requirements for Noise Suppresser Application to the AMR Speech Encoder
|
TS
|
8.1.1
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/06_series/06.77/0677-811.zip
|
The present document specifies recommended minimum performance requirements for noise suppression algorithms intended for application in conjunction with the AMR speech encoder. This specification is for guidance purposes. Noise Suppression is intended to enhance the speech signal corrupted by acoustic noise at the input to the AMR speech encoder.
The use of this recommended minimum performance requirements specification is not mandatory except for those solutions intended to be endorsed by SMG11.
It is the intention of SMG11 to perform analysis and validation of any AMR noise suppression solution which is voluntarily brought to the attention of SMG11 in the future, using the requirements set out in this specification to facilitate such an analysis. In order for SMG11 to endorse such a solution, SMG11 must confirm that all the recommended minimum performance requirements are met.
|
06.78
|
Results of the AMR noise suppression selection phase
|
TR
|
8.0.1
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/06_series/06.78/0678-801.zip
|
This technical report provides background information on the performance of the six candidates which were proposed as solutions for publication of an example noise suppression solution for application to the GSM Adaptive Multi-Rate (AMR) speech codec. Experimental test results from the speech quality related testing are reported to illustrate the behaviour of the candidate algorithms in multiple operational conditions. Additional information is also provided covering data not necessarily directly associated with speech quality (such as complexity, delay, effect on voice activity factor).
|
06.81
|
Discontinuous Transmission (DTX) for encanced full rate speech traffic channels
|
TS
|
8.0.1
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/06_series/06.81/0681-801.zip
|
The present document gives a description of the general baseband operation of Enhanced Full Rate speech traffic channels in the transmitter and in the receiver of GSM Mobile Stations (MS)s and Base Station Systems (BSS)s during Discontinuous Transmission (DTX).
For clarity, the description is structured according to the block diagrams in figures 1 and 4. Except in the case described next, this structure of distributing the various functions between system entities is not mandatory for implementation, as long as the operation on the air interface and on the speech decoder output remains the same.
In the case of BSSs where the speech transcoder is located remotely in the Base Station Controller (BSC), the implementation of the interfaces between the DTX handlers and the Radio Sub System (RSS) as described in the present document together with all their flags is mandatory, being part of the A‑bis interface as described in GSM 08.60 [13].
The DTX functions described in the present document are mandatory for implementation in the GSM MSs. The receiver requirements are mandatory for implementation in all GSM BSSs, the transmitter requirements only for those where downlink DTX will be used.
|
06.82
|
Voice Activity Detection (VAD) for enhanced full rate speech traffic channels
|
TS
|
8.0.1
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/06_series/06.82/0682-801.zip
|
The present document specifies the Voice Activity Detector (VAD) to be used in the Discontinuous Transmission (DTX) as described in GSM 06.81 [5] Discontinuous transmission (DTX) for Enhanced Full Rate (EFR) speech traffic channels.
The requirements are mandatory on any VAD to be used either in GSM Mobile Stations (MS)s or Base Station Systems (BSS)s that utilize the enhanced full-rate speech traffic channel.
|
06.85
|
Subjective tests on the interoperability of the HR/FR/EFR speech codecs; single, tandem and tandem free operation
|
TR
|
8.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/06_series/06.85/0685-800.zip
|
The present document contains the results obtained from an internationally co-ordinated subjective evaluation conducted by four laboratories to estimate the performance in mobile-to-mobile connections of the GSM half, full, and enhanced full rate speech codecs (including the expected advantages of the Tandem Free Operation), in case of inter-operability in the digital cellular telecommunications system. These (listening-only) tests did not include the effects of Voice Activity Detector, Comfort Noise Insertion and the Discontinuous Transmission.
|
08.01
|
General Aspects on the BSS-MSC Interface
|
TS
|
8.0.1
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/08_series/08.01/0801-801.zip
|
The present document is an introduction to the 3GPP TS 08.0x series of Technical Specifications and deals with the definition of the base station system (BSS) to mobile switching centre (MSC) (referred to as the A-interface) defined for the GSM system.
It also introduces Technical Specifications in the 3GPP TS 08.20 series, dealing with the support of data services on this interface.
The present document gives an overview of the content of the 3GPP TS 08.0x and 3GPP TS 08.20 series of Technical Specifications explaining how the detailed content of the Technical Specifications is partitioned and how the Technical Specifications can be used to support a full BSS-MSC interface.
|
08.02
|
Base Station System - Mobile Services Switching Centre (BSS-MSC) Interface - Interface Principles
|
TS
|
8.0.1
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/08_series/08.02/0802-801.zip
|
The present document gives the principles on which the detailed interface specifications in the rest of the 3GPP TS 08.0X series of Technical Specifications are based.
The set of fixed equipment accessed from the MSC through one particular instance of the interface will be later referred to as a Base Station System (BSS). A BSS ensures the coverage of n cells, where n can be 1 or more.
The function of a BSS may be further subdivided into a control function, performed by one Base Station Controller (BSC) and a transceiving function, performed by "n" Base Transceiver Station equipments (BTS), one for each cell. However, the study of such a split is outside the scope of the 08.0x series of Technical Specifications, where the BSS will be considered as a whole.
The BSS-MSC interface defined in the 3GPP TS 08 series of Technical Specifications is designed to support a wide range of possible architectures on both sides. Characteristics like the physical location of the transcoders/rate adaptation inside the BSS (either integrated into the transceivers or very near to the MSC) or the use of traffic or signalling concentration at either side are left to the operators choice. Annex A to the present document contains guidance information concerning the use of remote mobile switching units, which for the purposes of the present document are considered as part of the MSC.
Direct connection between two BSSs is not supported by this interface.
This interface is based on the use of 1 or more 2 048 kbit/s digital transmission system interfaces. Each 2 048 kbit/s interface provides 31*64 kbit/s channels which can be used for traffic or signalling as the operator requires.
The signalling is layered, terminology similar to that in the OSI reference model is used in this series, however the layers referred to are not identical to the equivalently named layer in the OSI model.
This interface is defined at the boundary of the MSC and has a per channel bit rate of 64 kbit/s, but the net radio path traffic channel is at a rate of less than 16 kbit/s. A transcoder or rate adapter function is thus needed for the rate conversion. The interface is designed such that the transcoding or rate adaptation function may be geographically situated at either the MSC site or the BSS site, however the transcoder is considered to be part of the BSS.
The interface has been designed around the aims of 3GPP TS 08.01 allowing each component and the system as a whole to evolve.
|
08.04
|
Base Station System - Mobile Services Switching Centre (BSS-MSC) Interface Layer 1 Specification
|
TS
|
8.0.1
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/08_series/08.04/0804-801.zip
|
The present document defines the structure of the physical layer (layer 1) of the BSS-MSC interface for supporting traffic channels. Use of the physical layer for supporting Signalling System No.7 signalling links is covered in Technical Specification 3GPP TS 08.06.
The physical layer is the lowest layer in the OSI Reference Model and it supports all functions required for transmission of bit streams on the physical medium.
For the present document only digital transmission will be considered, the use of analogue transmission is a national concern.
|
08.06
|
Signalling Transport Mechanism Specification for the Base Station System - Mobile Services Switching Centre (BSS-MSC) Interface
|
TS
|
8.0.1
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/08_series/08.06/0806-801.zip
|
The present document is split into two parts, clause 1-4 dealing with the MTP and clauses 5-7 dealing with the SCCP and its use.
The MTP provides a mechanism giving reliable transfer of signalling messages. Clauses 1-4 of the present document deal with the subset of the MTP that can be used between an BSS and an MSC, which is compatible with a full MTP.
The SCCP is used to provide a referencing mechanism to identify a particular transaction relating to for instance a particular call. Clauses 5-7 identify the SCCP subset that should be used between a BSS and an MSC. The SCCP can also be used to enhance the message routing for (for instance) operations and maintenance information.
|
08.08
|
Mobile-services Switching Centre - Base Station system (MSC-BSS) Interface Layer 3 Specification
|
TS
|
8.15.0
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/08_series/08.08/0808-8f0.zip
|
The present document specifies the layer 3 procedures used on the Base Station System (BSS) to Mobile-services Switching Centre (MSC) interface for control of GSM services.
For the purposes of call control and mobility management, messages are not interpreted at the Base Station System (BSS) which acts as a relay function. These messages and procedures are documented in 3GPP TS 04.08, the only relevant issues covering these messages in the present document are those concerned with error conditions at the interface, and the headers that are required for the correct addressing of the messages. This is specified in more detail in 3GPP TS 08.06.
The functional split between MSC and BSS is defined in 3GPP TS 08.02 and states that the BSS is responsible for local radio resource allocation and in order to support this the required procedures between BSS and MSC are defined in detail in the present document.
3GPP TS 08.02 also states that the BSS is responsible for the scheduling of all CCCH/BCCH messages and therefore some procedures for providing the BSS with the necessary information to be passed on these channels for individual calls (i.e. paging) are defined in the present document, but the scheduling is not discussed.
This interface and consequently these layer 3 procedures are designed to support BSSs providing one or more cells.
|
08.14
|
General Packet Radio Service (GPRS); Base Station System (BSS) - Serving GPRS Support Node (SGSN) interface; Gb Interface Layer 1
|
TS
|
8.0.1
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/08_series/08.14/0814-801.zip
|
The present document specifies the physical layer on the Base Station System (BSS) to Serving GPRS Support Node (SGSN) interface (Gb interface) and references layer 1 standards to be used on this interface.
The protocol stack on the Gb interface is defined in the stage 2 3GPP TS 03.60 [3].
|
08.16
|
General Packet Radio Service (GPRS); Base Station System (BSS) - Serving GPRS Support Node (SGSN) Interface; Network Service
|
TS
|
8.0.1
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/08_series/08.16/0816-801.zip
|
The present document specifies the Network Service used on the Base Station System (BSS) to Serving GPRS Support Node (SGSN) interface (Gb interface).
The protocol stack on the Gb interface is defined in the stage 2 Technical Specification 3GPP TS 03.60 [1].
The Network Service entity provides network services to the BSSGP entity specified in 3GPP TS 08.18 [2].
The layer 1 of the Gb interface is specified in 3GPP TS 08.14 [3].
In the present document, the communication between adjacent layers and the services provided by the layers are distributed by use of abstract service primitives. But only externally observable behaviour resulting from the description is normatively prescribed by the present document.
The service primitive model used in the present document is based on the concepts developed in CCITT Recommendation X.200 [4].
|
08.18
|
General Packet Radio Service (GPRS); Base Station System (BSS) - Serving GPRS Support Node (SGSN); BSS GPRS Protocol
|
TS
|
8.12.0
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/08_series/08.18/0818-8c0.zip
|
The present document specifies or references procedures used on the Base Station System (BSS) to Serving GPRS Support Node (SGSN) interface for control of GSM packet data services.
The functional split between BSS and SGSN is defined in 3GPP TS 03.60 [7] which states that a BSS is responsible for local radio resource allocation. The required procedures between BSS and SGSN are defined in detail in the present document.
|
08.20
|
Rate Adaptation on the Base Station System - Mobile Service Switching Centre (BSS-MSC) Interface
|
TS
|
8.4.1
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/08_series/08.20/0820-841.zip
|
The present document defines rate adaptation functions to be used in GSM PLMN Base Station Systems (BSS) transcoders and IWF for adapting radio interface data rates to the 64 kbit/s used at the A-interface in accordance with 3GPP TS 03.10.
The number of Base Station System - Mobile-services Switching Centre (BSS - MSC) traffic channels supporting data rate adaptation may be limited. In this case some channels may not support data rate adaptation. Those that do, shall conform to this specification.
NOTE: This specification should be considered together with 3GPP TS 04.21 to give a complete description of PLMN rate adaptation.
|
08.31
|
Location Services (LCS): Serving Mobile Location Centre - Serving Mobile Location Centre (SMLC - SMLC); SMLCPP specification
|
TS
|
8.1.1
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/08_series/08.31/0831-811.zip
|
The present document contains the definition of the SMLCPP protocol to be used between two Serving Mobile Location Centres (SMLC).
The LCS architecture is described in 03.71. The following aspects of it are relevant to the issue:
- each SMLC controls a number of LMUs, and a given LMU is under the direct control of a single SMLC;
- there is a direct communication path, independent of SMLCPP, between a LMU and the SMLC that controls it;
- deciphering keys are controlled by one SMLC in the location area and sent to other SMLCs in the same location area.
SMLCPP runs between two SMLC functions in the same PLMN. Transport is outside the scope of the present document. It assumes a transport service between these functions, as provided by BSSAP-LE. The present document assumes that the underlying transport (e.g., as described by BSSMAP-LE specifications) provides for transport and routing for any two pairs of SMLCs which need to run SMLCPP exchanges, whatever the implementation options for each of the SMLCs (BSS based or NSS based).
The main functions of SMLCPP are described in [5]. The key aspects are:
a) allowing an SMLC to ask for and obtain measurements on specific MSs performed by LMUs not under its direct control (e.g., for TOA);
b) allowing an SMLC to ask for and obtain information about Radio Interface Timing (RIT), as known from measurements done by LMUs not under its direct control;
c) allowing an SMLC, that controls deciphering keys in the location area, to sent them to other SMLCs in the same location area.
|
08.51
|
Base Station Controller - Base Tranceiver Station (BSC-BTS) Interface General Aspects
|
TS
|
8.0.1
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/08_series/08.51/0851-801.zip
|
The present document is an introduction to the 08.5x - 08.6x series of 3GPP Technical Specifications and deals with the definition of the base station controller (BSC) to base transceiver station (BTS) interface defined inside the base station system (BSS) for the GSM system. These Technical Specifications define the basic interface with some identified options requiring further elaboration. The BSC-BTS interface is mandatory within GSM only if the BSC and the BTS are not colocated.
|
08.52
|
Base Station Controller - Base Tranceiver Station (BSC-BTS) Interface - Interface Principles
|
TS
|
8.0.1
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/08_series/08.52/0852-801.zip
|
The use and general aspects of the A-bis interface are given in Technical Specification 3GPP TS 08.51.
The present document gives the principle basis for the rest of the specifications specifying the interface between the Base Station Controller, BSC, and the Base Transceiver Station, BTS, with its transceivers, TRX. These components together form the Base Station System, BSS. (The interface between MSC and the BSS is specified in Technical Specifications 3GPP TS 08.01 - 08.20).
The intention with this interface is to get a unified way of connecting remotely located BTSs/TRXs to a BSC allowing for the interconnection of BSCs and BTSs/TRXs from different manufacturers.
In order to keep the BTS as simple as possible, BTS contains only those functions which have to recide close to the radio interface.
|
08.54
|
BSC-BTS Layer 1; Structure of Physical Circuits
|
TS
|
8.0.1
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/08_series/08.54/0854-801.zip
|
The use and general aspects of the A-bis interface are given in Technical Specification 3GPP TS 08.51.
The present document defines the structure of the physical layer (layer 1) of the BSC - BTS/TRX interface for supporting traffic channels and control channels. Use of the physical layer for supporting link protocol is covered in Technical Specification 3GPP TS 08.56.
The physical layer is the lowest layer in the OSI Reference Model and it supports all functions required for transmission of bit streams on the physical medium.
For the present document only digital transmission will be considered, the use of analogue transmission is a national concern.
|
08.56
|
BSC-BTS Layer 2; Specification
|
TS
|
8.0.1
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/08_series/08.56/0856-801.zip
|
The present document specifies the link layer used for signalling on the A-bis interface between BSC and BTS. The use and general aspects of the A-bis interface are described in 3GPP TS 08.51 and the interface aspects in 3GPP TS 08.52.
The Link Access Procedure on the D-channel (LAPD) specification used on the A-bis interface in the GSM PLMN is a subset of the ETS 300 125 which in turn has less options than the CCITT Recommendation Q.921.
This description contains first the protocol definitions and second the services provided by the layer 2 to the layer 3.
|
08.58
|
Base Station Controler - Base Transceiver Station (BCS-BTS) Interface Layer 3 Specification
|
TS
|
8.6.0
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/08_series/08.58/0858-860.zip
|
The use and general aspects of the Base Station Controller (BSC) to Base Station Transceiver (BTS) interface (the A-bis interface) are given in 3GPP TS 08.51.
This Technical Specification (TS) specifies the general structure of layer 3 and traffic management procedures and messages used on the A-bis interface to support signalling procedures as defined in 3GPP TS 04.08. Support for Location Services (LCS) related signalling, as defined in 3GPP TS 03.71, is also included. 3GPP TS 03.71 identifies new A-bis signalling to support BTS-embedded Type B LMUs as well as standalone, Type B LMUs. The standalone Type B LMU supports the layer 1 and 2 signalling for the A-bis as well as the Location Service message defined in this specification.
Network management procedures and messages for the A-bis interface are defined in 3GPP TS 08.59.
The functional split between BSC and BTS is defined in 3GPP TS 08.52. The procedures and messages required to support this split are defined in detail in this TS.
|
08.60
|
In-band control of remote transcoders and rate adaptors for Enhanced Full Rate (EFR) and full rate traffic channels
|
TS
|
8.2.1
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/08_series/08.60/0860-821.zip
|
When 64 kbit/s traffic channels are used on the Abis interface, the speech shall be coded according to ITU-T Recommendation G.711 and the data rate adaptation shall be as specified in GSM 04.21 and GSM 08.20.
In the case where 16 kbit/s traffic channels are used for full rate speech, enhanced full rate speech, Adaptive Multi-Rate speech or full rate data service, then the present document shall apply for frame structure and for control of remote transcoders and additional rate adaptors.
For Adaptive Multi-Rate speech the present document specifies the 16 kBit/s submultiplexing, both for the full and the half rate traffic channels (TCH/AFS and TCH/AHS). The specification for 8 kBit/s submultiplexing is given in GSM 08.61, both for the full and the half rate traffic channels (TCH/AFS and TCH/AHS).
The use and general aspects of the Abis interface are given in GSM 08.51.
NOTE: The present document should be considered together with the GSM 06 series of specifications, GSM 04.21 (Rate Adaptation on the MS-BSS Interface) and GSM 08.20 (Rate Adaptation on the BS/MSC Interface).
|
08.61
|
In-band control of remote transcoders and rate adaptors for half rate traffic channels
|
TS
|
8.1.0
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/08_series/08.61/0861-810.zip
|
The present document describes the protocol between the Base Transceiver Station (BTS) and the remote Transcoder/Rate Adaption Unit (TRAU) for speech and data on half rate traffic channel (TCH/H).
For Half Rate speech and half rate data the protocol is specified for 8 kbit/s and 16 kbit/s submultiplexing scheme.
For Adaptive Multi-Rate speech the present document specifies the 8 kBit/s submultiplexing, both for the full and the half rate traffic channels (TCH/AFS and TCH/AHS). The specification for 16 kBit/s submultiplexing is given in Rec GSM 08.60, both for the full and the half rate traffic channels (TCH/AFS and TCH/AHS).
The present document should be considered together with the GSM 06 series, GSM 04.21 (Rate Adaption on the MS‑BSS Interface) and GSM 08.20 (Rate Adaption on the BTS/MSC Interface).
|
08.62
|
Inband Tandem Free Operation (TFO) of Speech Codecs; Service Description; Stage 3
|
TS
|
8.0.1
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/08_series/08.62/0862-801.zip
|
This service description document details the Inband Signalling Protocol between Transcoder/Rate Adaptor Units for speech traffic channels for the Tandem Free Operation (TFO) of Speech Codecs.
This service description should be considered together with GSM 08.60 (Inband control of remote transcoders and rate adaptors for Enhanced Full Rate and Full Rate traffic channels) and GSM 08.61 (Inband control of remote transcoders and rate adaptors for Half Rate traffic channels).
Annex A is mandatory and describes the general Inband Signalling (IS) Principle.
Annex B is informative and gives the rules for In Path Equipment (IPE).
Annex C is the formal SDL description of the TFO Protocol as given in clause 10. Clause 10 has precedence in case of ambiguities. A part of Annex C is in electronic format. Annex C is informative. It supports the formal verification of the TFO Protocol.
|
08.71
|
Location Services (LCS); Serving Mobile Location Centre - Base Station System (SMLC-BSS) interface; Layer 3
|
TS
|
8.6.0
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/08_series/08.71/0871-860.zip
|
The present document contains the coding of information necessary for support of location service operation on the SMLC-BSS interface layer 3.
Clause 2 gives the functional definitions and contents of messages for location service operations. Clause 3 gives the general format and coding for messages used for location service and the format and coding of information elements used for location service operations.
|
09.01
|
General Network Interworking Scenarios
|
TR
|
8.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/09_series/09.01/0901-800.zip
|
The present document serves as an introduction to the GSM 09.xx‑series.
In clause 4, the technical requirements for Public Land Mobile Network (PLMN) interworking are introduced, and in clause 5 there is a summary of the contents of the GSM 09.xx‑series.
|
09.08
|
Application of the Base Station System Application Part (BSSAP) on the E-Interface
|
TS
|
8.2.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/09_series/09.08/0908-820.zip
|
The present document describes the subset of Base Station System Application Part (BSSAP) messages and procedures, defined in 3GPP TS 08.06 and 3GPP TS 08.08, which is used on the E‑interface. A general description can be found in 3GPP TS 03.02 and 3GPP TS 03.09.
For the initiation and execution of handover between MSCs a subset of BSSMAP procedures are used. For the subsequent control of resources allocated to the Mobile Station (MS) BSSMAP procedures are used. DTAP is used for the transfer of connection management and mobility management messages between the MS and the controlling MSC.
|
09.31
|
Location Services (LCS); Base Station System Application Part LCS Extension (BSSAP-LE)
|
TS
|
8.7.1
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/09_series/09.31/0931-871.zip
|
The present document specifies procedures and information coding that are needed to define and support the BSSAP LCS Extension (BSSAP-LE). The BSSAP-LE message set is applicable to the following GSM interfaces defined in 3GPP TS 03.71:
Lb interface (BSC-SMLC).
Ls interface (MSC-SMLC).
Lp interface (SMLC-SMLC).
The present document defines message formats and encoding for BSSAP-LE and the particular subsets of it that are applicable to each of the above interfaces. The present document also defines the support for BSSAP-LE message transfer on each of these interfaces using CCITT and ANSI versions of SS7 MTP and SCCP. Additional requirements for the above interfaces that are applicable to BSSAP-LE are also defined – e.g. usage of BSSAP (as defined in 3GPP TS 04.08 and 08.08) on the Lb interface.
|
09.95
|
General Packet Radio Service (GPRS); Interworking between modified Public Land Mobile Network (PLMN) supporting GPRS and legacy GPRS mobiles
|
TR
|
8.0.0
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/09_series/09.95/0995-800.zip
|
This report describes issues relating to the GPRS specifications, which lead to the specifications being modified after the placement of GPRS compliant mobiles into the market place.
Where possible the present report clarifies any recommended measures which may be adopted by the GPRS infrastructure to enable interworking to be obtained between the GPRS infrastructure and legacy Mobile Station (MS) implementations of the GPRS specifications.
For each issue this report also defines the time after which all new GPRS mobiles are required to meet the modified specifications.
The lifetime of the herein described measures together with their potential impact on optimal network performance is out of the scope of the present document.
|
10.59
|
Project scheduling and open issues for EDGE
|
TR
|
8.0.0
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/10_series/10.59/1059-800.zip
| |
11.10-1
|
Mobile station (MS) conformance specification; Part 1: Conformance specification
|
TS
|
8.3.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/11_series/11.10-1/1110-1-830.zip
|
The present document describes the technical characteristics and methods of test for Mobile Stations (MS), for the Pan European digital cellular communications system and Personal Communication Systems (PCS) operating in the 400 MHz, 900 MHz and 1 800 MHz band (GSM 400, GSM 900 and DCS 1 800), standardized by ETSI Special Mobile Group (SMG).
The present document is valid for MS implemented according Phase2 or Phase2+ R96, or R97, or R98 or R99.
A subset of the tests is referenced in the GSM Common Technical Regulations (CTRs) and is used for regulatory conformance testing according to the EEC procedures for Telecommunications Terminal Equipment (TTE) type approval (EC Directive 91/263/EEC; also known as the "Terminal Directive" or "Second Phase Directive"). The remaining tests can be used to verify conformance with the GSM core technical specifications for those requirements that are not considered "essential" in the sense of the EC Directive 91/263/EEC (Article 4).
The present document covers the minimum characteristics considered necessary in order to provide sufficient performance for mobile equipment and to prevent interference to other services or to other users, and to the PLMNs.
It does not necessarily include all the characteristics which may be required by a user or subscriber, nor does it necessarily represent the optimum performance achievable.
It applies to the public land mobile radio service in the GSM 400, GSM 900 and DCS 1 800 systems, using constant envelope modulation and operating on radio frequencies in the 400, 900 and 1 800 MHz bands respectively with a channel separation of 200 kHz and carrying 8 full rate channels or 16 half rate channels per carrier according to the TDMA principle.
The present document is part of the GSM-series of technical specifications. This EN neither replaces any of the other GSM technical specifications or GSM related TSs, nor is it created to provide full understanding of (or parts of) the GSM 400, GSM 900 and DCS 1 800 systems. The present document lists the requirements, and provides the methods of test for testing a MS for conformance to the GSM standard.
For a full description of the system, reference should be made to all the GSM technical specifications. Clause 2 provides a complete list of the GSM technical specifications, GSM related TSs, and TRs, on which this conformance test specifications is based.
The present document applies to the unit which includes the hardware to establish a connection across the radio interface.
If there is a difference between this conformance test TS, and any other GSM technical specification, then the other GSM technical specification shall prevail.
|
11.10-4
|
Mobile Station (MS) conformance specification; Part 4: Subscriber Identity Module (SIM) application toolkit conformance test specification
|
TS
|
8.15.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/11_series/11.10-4/1110-4-8f0.zip
|
The present document describes the technical characteristics and methods of test for testing the SIM Application Toolkit implemented in Mobile Stations (MS) for the Pan European digital cellular communications system and Personal Communication Systems (PCS) operating in the 450 MHz, 480 MHz, 700 MHz, 750 MHz, 850 MHz, 900 MHz, 1 800 MHz and 1 900 MHz frequency band (GSM 400, GSM 700, GSM 750, GSM 850, GSM 900, DCS 1 800 and PCS 1 900) within the European digital cellular telecommunications system, in compliance with the relevant requirements, and in accordance with the relevant guidance given in ISO/IEC 9646‑7 [19] and ETS 300 406 [20].
The present document is valid for MS implemented according to GSM Phase2+ R96, or R97, or R98, or R99.
The present document covers the minimum characteristics considered necessary in order to provide sufficient performance for mobile equipment and to prevent interference to other services or to other users, and to the PLMNs.
It does not necessarily include all the characteristics which may be required by a user or subscriber, nor does it necessarily represent the optimum performance achievable.
The present document is part of the GSM-series of technical specifications. The present document neither replaces any of the other GSM technical specifications or GSM related ETSs or ENs, nor is it created to provide full understanding of (or parts of) the GSM 400, GSM 700, GSM 850, GSM 900, DCS1800 and PCS1900 systems . The present document lists the requirements, and provides the methods of test for testing the SIM Application Toolkit implemented in a MS for conformance to the GSM standard.
For a full description of the system, reference should be made to all the GSM technical specifications or GSM related ETSs or ENs. Clause 2 provides a complete list of the GSM technical specifications, GSM related ETSs, ENs, and ETRs, on which this conformance test specifications is based.
If there is a difference between this present conformance document, and any other GSM technical specification or GSM related ETS or EN, or 3GPP TS, then the other GSM technical specification or GSM related ETS or EN or 3GPP TS shall prevail.
|
11.11
|
Specification of the Subscriber Identity Module - Mobile Equipment (SIM-ME) Interface
|
TS
|
8.14.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/11_series/11.11/1111-8e0.zip
|
The present document defines the interface between the Subscriber Identity Module (SIM) and the Mobile Equipment (ME) for use during the network operation phase of GSM as well as those aspects of the internal organization of the SIM which are related to the network operation phase. This is to ensure interoperability between a SIM and an ME independently of the respective manufacturers and operators. The concept of a split of the Mobile Station (MS) into these elements as well as the distinction between the GSM network operation phase, which is also called GSM operations, and the administrative management phase are described in the TS 02.17 [6].
The present document defines:
‑ the requirements for the physical characteristics of the SIM, the electrical signals and the transmission protocols;
‑ the model which shall be used as a basis for the design of the logical structure of the SIM;
‑ the security features;
‑ the interface functions;
‑ the commands;
‑ the contents of the files required for the GSM application;
‑ the application protocol.
Unless otherwise stated, references to GSM also apply to DCS 1800 and PCS 1900.
The present document does not specify any aspects related to the administrative management phase. Any internal technical reallocation of either the SIM or the ME are only specified where these reflect over the interface. It does not specify any of the security algorithms which may be used.
The present document defines the SIM/ME interface for GSM Phase 2. While all attempts have been made to maintain phase compatibility, any issues that specifically relate to Phase 1 should be referenced from within the relevant Phase 1 specification.
|
11.13
|
Test specification for Subscriber Interface Module (SIM) Application Programme Interface (API) for Java card
|
TS
|
8.3.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/11_series/11.13/1113-830.zip
|
The present document covers the minimum characteristics considered necessary in order to provide compliance to GSM 03.19 [7].
The present document describes the technical characteristics and methods of test for testing the SIM API for Java CardTM [7] implemented in the subscriber identity modules (SIMs) for GSM. It specifies the following parts:
- test applicability;
- test environment description;
- tests format;
- test area reference;
- conformance requirements;
- test suite files;
- test procedure;
- test coverage; and
- a description of the associated testing tools that shall be used.
|
11.14
|
Specification of the SIM Application Toolkit (SAT) for the Subscriber Identity Module - Mobile Equipment (SIM-ME) interface
|
TS
|
8.18.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/11_series/11.14/1114-8i0.zip
|
The present document defines the interface between the Subscriber Identity Module (SIM) and the Mobile Equipment (ME), and mandatory ME procedures, specifically for "SIM Application Toolkit".
SIM Application Toolkit is a set of commands and procedures for use during the network operation phase of GSM, in addition to those defined in TS 11.11 [20].
Specifying the interface is to ensure interoperability between a SIM and an ME independently of the respective manufacturers and operators. The concept of a split of the Mobile Station (MS) into these elements as well as the distinction between the GSM network operation phase, which is also called GSM operations, and the administrative management phase are described in TS 02.17 [3].
The present document defines:
- the commands;
- the application protocol;
- the mandatory requirements on the SIM and ME for each procedure.
Unless otherwise stated, references to GSM also apply to DCS 1800.
The present document does not specify any aspects related to the administrative management phase. Any internal technical realization of either the SIM or the ME are only specified where these reflect over the interface. This standard does not specify any of the security algorithms which may be used.
The present document defines an enhancement for GSM Phase 2+ of the SIM/ME interface for GSM Phase 2. While all attempts have been made to maintain phase compatibility, any issues that specifically relate to Phase 1 should be referenced from within the relevant Phase 1 specification.
|
11.17
|
Subscriber Identity Module (SIM) test specification
|
TS
|
8.2.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/11_series/11.17/1117-820.zip
|
The present document provides the Conformance Test Specification for the Subscriber Identity Module defined in GSM 11.11 [1], GSM 11.12 [8] and GSM 11.18 [9].
|
11.21
|
Base Station System (BSS) equipment specification; Radio aspects
|
TS
|
8.11.0
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/11_series/11.21/1121-8b0.zip
|
The present document specifies the Radio Frequency (RF) test methods and conformance requirements for GSM 400, GSM 900 and DCS 1800, PCS 1900, GSM 850, MXM 850 and MXM 1900 Base Station Systems (BSS)s. These have been derived from, and are consistent with, the core GSM specifications specified in the requirements reference subclause of each test with the exception that requirements expressed as a reference to regulatory documents (e.g. FCC) have not been included in the present document.
The present document is applicable to BSS meeting the requirements of either GSM Phase 2 or GSM Phase 2+. Unless otherwise stated, all tests are applicable to BSS meeting Phase 2 and/or Phase 2+ GSM requirements, because the requirements of the Phase 2 and Phase 2+ core GSM specifications which are referenced in the test are consistent. Most differences between Phase 2 and Phase 2+ requirements represent Phase 2+ features which are optional for the BSS to support.
For each test, two conformance requirements are specified:
‑ essential conformance requirements;
‑ complete conformance requirements.
Essential conformance requirements are those which are required:
a) to ensure compatibility between the radio channels in the same cell;
b) to ensure compatibility between cells, both co‑ordinated and unco‑ordinated;
c) to ensure compatibility with existing systems in the same or adjacent frequency bands;
d) to verify the important aspects of the transmission quality of the system.
Essential conformance requirements are sufficient to verify the performance of the equipment for radio type approval purposes, in countries where this is applicable. For GSM 850, MXM 850, PCS 1900 and MXM 1900 only the complete conformance requirements are applicable.
Complete conformance requirements may be tested to verify all aspects of the performance of a BSS. These requirements are intended to be used by manufacturers and operators to allow conformance and acceptance testing to be performed in a consistent manner; the tests to be performed should be agreed between the parties.
In some tests there are separate requirements for micro‑BTS and BTS. If there is no separate requirement for a micro‑BTS, the requirements for the BTS apply to a micro‑BTS.
In the present document, the reference point for RF connections (except for the measurement of mean transmitted RF carrier power) is the antenna connector, as defined by the manufacturer. The present document does not apply to repeaters or RF devices which may be connected to an antenna connector of a BSS, except as specified in subclause 4.10.
NOTE: The present document contains both essential conformance requirements and complete conformance requirements. Essential conformance requirements are those requirements which may be deemed sufficient for radio type approval purposes, complete conformance requirements cover all conformance aspects.
|
11.26
|
Base Station System (BSS) equipment specification; Part 4: Repeaters
|
TS
|
8.0.2
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/11_series/11.26/1126-802.zip
|
The present document describes the Radio Frequency (RF) tests for GSM 450, GSM 480, GSM 900 and DCS 1800 repeaters which receive, amplify, and retransmit a received Mobile Station (MS) signal in the GSM MS transmit band and simultaneously receive, amplify and retransmit a received Base Transceiver Station (BTS) RF signal in the GSM BTS transmit band.
The present document is applicable to repeaters meeting the requirements of either GSM Phase 2 or GSM Phase 2+. Unless otherwise stated, all tests are applicable to repeaters meeting Phase 2 and/or Phase 2+ GSM requirements, because the requirements of the Phase 2 and Phase 2+ core GSM specifications which are referenced in the test are consistent. Most differences between Phase 2 and Phase 2+ requirements represent Phase 2+ features which are optional for the BSS to support.
|
12.03
|
Security Management
|
TS
|
8.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/12_series/12.03/1203-800.zip
|
The present document describes the management of the security related aspects in the GSM/DCS PLMN. The management of the relevant security services is addressed with respect to the following aspects:
Overview of the security features;
Description of the relevant management procedures;
Modeling using the object oriented paradigm.
The definitions and descriptions of the security features and mechanisms are contained in the specifications of the underlying procedures and are not defined in the present document. References to appropriate GSM/DCS specifications have been made throughout the present document where necessary. Issues relating to the security of management (e.g. file transfer security, database security, inter‑operator security, etc.) are not covered in the present document.
|
12.04
|
Performance data measurements
|
TS
|
8.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/12_series/12.04/1204-810.zip
|
The present document describes the requirements for the management of performance measurements and the collection of performance measurement data across a Public Land Mobile Network (PLMN). It defines the administration of measurement schedules, the generation of measurement results in the Network Elements (NEs) and the transfer of these results to the Operations System (OS). It also describes how the various requirements can be modelled as part of the generic PLMN information model.
A set of measurements available for collection by NEs are described in annex B, effort has been made to ensure consistency in the definition of measurements between different NEs.
The following is beyond the scope the present document:
- how the data, once accumulated and collected, could or should be processed, stored, or presented to an end user;
- the information which may be obtained through the collection and processing of call or event related records which have been produced by the NEs primarily for the purpose of raising bills and other charges.
The management requirements have been derived from existing telecommunications operations experience. The management definitions were then derived from other standardisation work so as to minimise the re-invention factor. References are given as appropriate.
The objective of the present document is: to normalise the description of each measurement; and to produce a common description of the management technique for result accumulation and transmission across a management interface. The normalisation is intended to result in comparability of measurement data produced in a multi-vendor PLMN.
As far as possible, existing standardisation in the area of performance management has been re-used and enhanced where particular requirements, peculiar to the mobile telephony environment, have been recognised.
Field of application
The present document considers all aspects of performance management for a PLMN and its NEs defined in the GSM core Technical Specifications. However, only those aspects, which are GSM specific and particular to PLMN operation are included in the present document. Other performance measurement aspects of described NEs and performance measurement aspects of NEs not described by the GSM core Technical Specifications are included for information purposes in annex E or may be found in referenced documents.
|
12.21
|
Network Management (NM) procedures and messages on the A-bis interface
|
TS
|
8.0.0
|
R6
|
https://www.3gpp.org/ftp/Specs/archive/12_series/12.21/1221-800.zip
|
The present document addresses the network management messages and procedures across the A-bis interface, which is defined as Qx in GSM. The information model included here defines the objects and how they are addressed for purposes of operations and maintenance activities.
There is a requirement for the A-bis interface to be open to allow interoperation between BTSs of different manufacturers working to the same BSC. The present document addresses this requirement from O&M point of view, which allows this interworking to take place. It shows the split of NM functions between BSC and BTS. The procedures and coding of the messages are specified in detail. In practice, in addition to the present document it is necessary that the content of manufacturer-dependent information fields be specified to fulfill the functionality.
It is essential for operation that a BSC can handle the functions used by all its BTSs. Therefore, all items in the present document are considered mandatory unless otherwise indicated in the present document.
|
12.71
|
Location Services (LCS); Location services management
|
TS
|
8.0.1
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/12_series/12.71/1271-801.zip
|
The present document addresses the network management architecture, functions, and protocol for LCS operations and maintenance. The information model included here defines the managed entities and how they are addressed for purposes of operations and maintenance activities.
There is a requirement for the network management interface to be open to allow interoperation between LMUs and GMLCs of different manufacturers working to the same SMLC. The present document addresses this requirement from an operations and maintenance point of view, which allows this interworking to take place. It shows the split of network management functions between GMLC, SMLC and LMU. The procedures and coding of the messages are specified in detail. In practice, in addition to the present document, it is necessary that the content of manufacturer-dependent information fields be specified to fulfil the functionality.
It is essential for operation that a SMLC can handle the functions used by all its LMUs. Therefore, all items in the present document are considered mandatory unless otherwise indicated in the present document.
NOTE: This version contains only the SMLC-LMU interface. Other work will be undertaken in the future.
|
21.904
|
User Equipment (UE) capability requirements
|
TR
|
3.5.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/21_series/21.904/21904-350.zip
|
The present document’s scope is the Release 99 of the 3GPP specifications to which it refers. This document is not currently planned to be kept updated beyond December 2000.
The present document defines a baseline set of capability requirements that enable all UEs to "register" with all applicable 3GPP networks (depending on the availability of a appropriate subscription). It describes all the functions that a UE has to perform in order to "exist" within a 3GPP network. These functions are used to derive requirements for all aspects of UE baseline capability. The present document also identifies different UE Service Capabilities and the functions that a UE must perform in order to access a service. The actual capabilities that a UE must posses to meet these requirements are identified in the report and in some instances listed in the Annexes to the present document, as well as being described in the referenced implementation specifications.
The present document introduces the concept of "service-less UE" which can exist in the network but provides no user service. Although this is not a marketable UE type it describes from the standardisation viewpoint a baseline set of capabilities to which specific service-related UE capabilities can then be added.
The present document should not be used as the sole basis for UE design, only as an informative indication of capabilities required to support a given functionality, and as a pointer to the location of text describing said functionality, in the core specifications.
UE capability requirements may include some regulatory requirements (mandatory requirements). However, it is not intended to identify them as such in this report. Some of the requirements identified in this document as essential, may therefore also be “mandatory” according to the definition of that term appearing herein.
|
21.910
|
Multi-mode UE issues; categories, principles and procedures
|
TR
|
3.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/21_series/21.910/21910-300.zip
|
This 3GPP Technical Report identifies multi-mode User Equipments categories. This technical report also describes the general principles and procedures for the multi-mode operation standardised in the 3GPP specifications. In particular, this TR is focused on a type 2 UE, as defined in Clause 4 in the present report. This type of UE can when utilising one mode, perform monitoring of another mode and report it utilising the current mode. This type of UE does not support simultaneous reception or transmission through different modes.
The scope of this TR is the type of terminal implemented with at least the following modes:
- UTRA FDD and/or TDD mode
- GSM mode
Regarding the GSM mode, it encompasses the capabilities offered by the GSM technical specifications, e.g, Circuit Switched and Packet Switched services using either GMSK or 8-PSK modulation in the frequency bands specified in the GSM specifications.
The present report is built on and references specifications/reports being produced in 3GPP or within other relevant foras e.g. ETSI SMG.
|
21.978
|
Feasibility Technical Report; CAMEL Control of VoIP Services
|
TR
|
3.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/21_series/21.978/21978-300.zip
|
The purpose of this Technical Report is to study the feasibility of a core network CAMEL server controlling voice services carried by VoIP within a GPRS PDP Context using:
1) An architecture based on ITU-T, H.323 family of recommendations.
2) An architecture based on IETF SIP specifications.
|
22.100
|
UMTS Phase 1
|
TS
|
3.7.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.100/22100-370.zip
|
The UMTS system will be defined in a phased approach. The present document specifies the requirements for Release '99 of UMTS. Some requirements which are necessary to ensure a smooth transition to later releases are also indicated. The present document should, however, be read in conjunction with the other 22.000 series documents which provide a complete description of the requirements for UMTS Release '99.
|
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.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.
|
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.
|
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.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.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.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.
|
25.833
|
Physical layer items not for inclusion in Release 99
|
TR
|
3.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.833/25833-300.zip
|
This Technical Report collects material on UTRA physical layer items which have already been in the specifications, but were decided not to be included in release ’99.
The items are described by text from the specifications or by text proposals which have been accepted by WG1.
|
25.925
|
Radio Interface for Broadcast/Multicast Services
|
TR
|
3.5.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.925/25925-350.zip
|
The present document shall provide a general overview on radio interface related aspects of broadcast/multicast services. This report covers stage 2 and stage 3 aspects of the radio interface.
This report is organised as follows: clause 4 gives an overview on the broadcast/multicast services and their requirements. Clause 5 provides a common model and describes aspects common to all point-to-multipoint services. Clause 6 is devoted to the Cell Broadcast Service describing the impacts on the interface functions and the protocol aspects. The present document covers only those items, which are in the scope of 3GPP TSG RAN WG 2. Information from Technical Specifications or other documents are provided when it is necessary to understand the requirements described.
Table 1.1: Schedule of the broadcast/multicast services onto the UMTS phases and annual releases
Release
Broadcast/multicast service
1999
Cell Broadcast Service CBS (GSM)
Cell Broadcast Service (ANSI-41)
NOTE: A decision to map the services to releases is required for all other broadcast/multicast services.
|
26.915
|
Echo Control For Speech and Multi-Media Services
|
TR
|
3.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.915/26915-300.zip
|
The present document specifies minimum performance requirements for the gateway echo control of 3G speech and multi-media services. The present document is applicable to any narrow band speech telephony or multimedia service.
|
29.198
|
Open Service Architecture (OSA) Application Programming Interface (API) - Part 1
|
TS
|
3.4.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.198/29198-340.zip
|
This document specifies the stage 3 of the Open Service Architecture (OSA) Application Programming Interface (API). The concepts and the functional architecture of the Open Service Architecture (API) are described by 3GPP TS 23.127 [2]. This document describes the stage 3 specification of the Open Service Architecture API.
The Open Service Architecture defines an architecture that enables service providers to make use of network functionality through an open standardised interface, i.e. the OSA API. The network functionality is describes as Service Capability Servers. Within the OSA concepts the following Service Capability Servers are identified:
CAMEL Service Environment (see in 3GPP TS 23.078 [4])
WAP execution platform (i.e. WAP Gateway & WAP Push Proxy, see in [13] )
Home Location Register (HLR)
The stage 3 documentation of the OSA R’99 API consists of two parts:
The API specification (Part 1).
This is a normative stage 3 specification of the capabilities of the OSA R’99 API and describes the OSA API interface classes, containing class diagrams (see section 6), state transition diagrams (see section 7), data type definitions (section 8), and the IDLs (see section 9).
- The Mapping specification of the OSA R’99 API and the network protocols (Part2).
This is an informative specification to provide an example how the OSA API can be mapped on the network protocols (i.e. MAP [7], CAP[8] and WAP[9]). It is an informative document, since this mapping is considered as implementation/vendor dependent. On the other hand this mapping will provide potential service designers with a better understanding of the relationship of the OSA API interface classes and the behavior of the network associated to these interface classes.
The OSA API Stage 3 activity is performed jointly with ETSI SPAN3’s Service Provider Access Requirements activity. The contents of this document is related to the jointly owned 3GPP & ETSI document referred as the API Master document, which contains the API interface descriptions that are common and differentiated between ETSI & 3GPP.
|
29.998
|
Open Services Architecture (OSA) Application Programming Interface (API) part 2
|
TR
|
3.2.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.998/29998-320.zip
|
The present document investigates how the OSA Interface Class methods can be mapped onto CAMEL Application Part operations and MAP Application Part operations. The mapping of the OSA API to the CAP and relevant MAP operations is considered informative, and not normative.
The Open Service Architecture (OSA) defines an architecture that enables operator and third party applications to make use of network functionality through an open standardized interface (the OSA Interface). OSA provides the glue between applications and service capabilities provided by the network. In this way applications become independent from the underlying network technology. The applications constitute the top level of the Open Service Architecture (OSA). This level is connected to the Service Capability Servers (SCSs) via the OSA interface. The SCSs map the OSA interface onto the underlying telecommunications specific protocols (e.g. MAP, CAP, etc.) and are therefore hiding the network complexity from the applications.
The specific Service Capability Server under consideration in this technical report is the CSE. In this case, the OSA API provides the operator or third party applications access to the CAMEL Application Part protocol operations, via the OSA Interface Class methods. On the gsmSCF, the OSA Interface Class methods need to be mapped, or translated, onto the relevant CAP and/or MAP operations. Only the non-framework Service Capability Features will be taken into account for the mapping. This document is not exhaustive in covering all the mappings that can be expected. It provides several examples, but it should be noted that several other possibilities exist. In particular, only general cases of normal operations are covered and exception scenarios are not within the scope of the document.
In addition to the configuration of SCS and CSE, this technical report contains some recommendations for a configuration consisting of SCS and HLR. On the HLR, the OSA Interface Class methods need to be mapped, or translated, onto the relevant MAP protocol operations. The mappings contained in this technical report for the SCS/HLR case are not intended to be exhaustive.
The OSA API to CAP and MAP mapping is part of Release99.
|
32.005
|
Telecommunications management; Charging management; 3G call and event data for the Circuit Switched (CS) domain
|
TS
|
3.7.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.005/32005-370.zip
|
The present document is concerned with the administration of subscriber related event and call data. This includes both the collection of call data from, and the distribution of tariff data to, the Network Elements.
The subscriber (IMSI) and mobile equipment (IMEI) related call and event data collected is employed by a number of management activities including billing & accounting, statistical analysis and customer care.
The tariff data in the Network Elements is required to support the supplementary service "Advice of Charge".
The aim of the present document is to describe both the network management functions required and the data involved.
|
32.015
|
Telecommunications management; Charging management; 3G call and event data for the Packet Switched (PS) domain
|
TS
|
3.12.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.015/32015-3c0.zip
|
The GSM and UMTS PLMN support a range of packet-based services in the same network. In order to enable operators the ability to provide a commercially viable service there is a need to provide charging functions. The present document describes the functionality of charging, which includes the General Packet Radio Service (GPRS) in GSM and UMTS, as defined in 3GPP TS 22.060 [3] and 3GPP TS 23.060 [8] (packet based services).
|
32.104
|
Telecommunication management; 3G Performance Management
|
TS
|
3.9.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.104/32104-390.zip
|
The present document describes the requirements for the management of performance measurements and the collection of performance measurement data across a 3G network. It defines the administration of measurement schedules by the Network Element Manager (EM), the generation of measurement results in the Network Elements (NEs) and the transfer of these results to one or more Operations Systems, i.e. EM(s) and/or Network Manager(s) (NM(s)).
The basic Performance Management concept that the present document is built upon is described in clause 4. The requirements how an EM administers the performance measurements and how the results can be collected are defined in detail in clause 5. Annex A specifies the file format for the bulk transfer of performance measurement results to the NM, while annex B discusses the file transfer procedure utilised on that interface. A set of measurements available for collection by NEs are described in annex C, effort has been made to ensure consistency in the definition of measurements between different NEs.
The following is beyond the scope of the present document, and therefore the present document does not describe:
- the formal definition of the interface that the EM uses to administer performance measurements in the NEs;
- the formal definition of the interface that the EM uses to collect measurement results from the NEs;
- how the data, once accumulated and collected, could or should be processed, stored, or presented to an end user;
- the information which may be obtained through the collection and processing of call or event related records which have been produced by the NEs primarily for the purpose of raising bills and other charges.
The management requirements have been derived from existing telecommunications operations experience. The management definitions were then derived from other standardisation work so as to minimise the re-invention factor. References are given as appropriate.
The objectives of this standardisation are:
- to provide the descriptions for a standard set of measurements;
- to produce a common description of the management technique for measurement administration and result accumulation; and
- to define a method for the bulk transmission of measurement results across a management interface.
The definition of the standard measurements is intended to result in comparability of measurement data produced in a multi-vendor 3G network, for those measurement types that can be standardised across all vendors' implementations.
As far as possible, existing standardisation in the area of Performance Management has been re-used and enhanced where particular requirements, peculiar to the mobile telephony environment, have been recognised.
The present document considers all the above aspects of Performance Management for a 3G network and its NEs defined in the 3G core Technical Specifications. However, only those aspects which are specific to a 3G system and particular to 3G-network operation are included in the present document.
|
32.106-1
|
Telecommunication management; Configuration Management (CM); Part 1: Concept and requirements
|
TS
|
3.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.106-1/32106-1-310.zip
|
The present document describes the Configuration Management (CM) aspects of managing a 3G network. This is described from the management perspective in 3G TS 32.101 [1] and 3G TS 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 (QOS), 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 NEs in the context of the described management environment. The context is described for both the management system (OS) and Network Element (NE) functionality.
Clause 7 contains the specific definitions for the standardised N interface, which are necessary to follow for compliance to this specification.
The Itf‑N for CM is built up by a number of Integration Reference Points (IRPs) and a related Name Convention, which realise the functional capabilities over this interface. The basic structure of the IRPs is defined in 3G TS 32.101 [1] and 3G TS 32.102 [2]. For CM, a number of IRPs (and the Name Convention) are defined herein, used by this as well as by other specifications for Telecom Management produced by 3GPP. All these are included in Parts 2 through 8 of the present document as follows:
Notification IRP Information Service Version 1: 32.106 Part 2
Notification IRP CORBA Solution Set Version 1:1: 32.106 Part 3
Notification IRP CMIP Solution Set Version 1:1: 32.106 Part 4
Basic Configuration Management IRP Information Model (including NRM) Version 1: 32.106 Part 5
Basic Configuration Management IRP CORBA Solution Set Version 1:1: 32.106 Part 6
Basic Configuration Management IRP CMIP Solution Set Version 1:1: 32.106 Part 7
Name Convention for Managed Objects: 32.106 Part 8
|
32.106-2
|
Telecommunication management; Configuration Management (CM); Part 2: Notification Integration Reference Point (IRP): Information Service (IS)
|
TS
|
3.3.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.106-2/32106-2-330.zip
|
Network Elements (NEs) under management generate events to inform event receivers about occurrences within the network that may be of interest to event receivers. There are a number of categories of events. Alarm, as specified in Alarm IRP: Information Service 3GPP TS 32.111-2 [1], is one member of this category.
The purpose of Notification IRP is to define an interface through which an IRPManager (typically a network management system) can subscribe to IRPAgent (typically an Element Manager (EM) or a NE) for receiving network events. It also specifies attributes carried in the network events. These attributes are common among all event categories. Attributes that are specific to a particular event category are not part of the present document. For example, perceivedSeverity is an attribute specific for alarm event category. This attribute is not defined the present document but in Alarm IRP 3GPP TS 32.111-2 [1].
|
32.106-3
|
Telecommunication management; Configuration Management (CM); Part 3: Notification Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS)
|
TS
|
3.3.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.106-3/32106-3-330.zip
|
The present document specifies the Common Object Request Broker Architecture (CORBA) Solution Set (SS) for the IRP whose semantics is specified in Notification IRP: Information Service (3GPP TS 32.106-2 [5]).
|
32.106-4
|
Telecommunication management; Configuration Management (CM); Part 4: Notification Integration Reference Point (IRP); Common Management Information Protocol (CMIP) Solution Set (SS)
|
TS
|
3.2.1
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.106-4/32106-4-321.zip
|
The present document specifies the Common Management Information Protocol (CMIP) Solution Set (SS) for the Notification Integration Reference Point (IRP): Information Service defined in 3GPP TS 32.106-2 [3]. In detail:
• Clause 4 contains an introduction to some concepts that are the base for some specific aspects of the CMIP interfaces.
• Clause 5 contains the GDMO definitions for the Alarm Management over the CMIP interfaces
• Clause 6 contains the ASN.1 definitions supporting the GDMO definitions provided in clause 5.
|
32.106-5
|
Telecommunication management; Configuration Management (CM); Part 5: Basic CM Integration Reference Point (IRP): Information model (including Network Resource Model (NRM)
|
TS
|
3.2.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.106-5/32106-5-320.zip
|
The present document (Basic Configuration Management (CM) IRP: Information Model) defines an Integration Reference Point (IRP) through which an 'IRPAgent' (typically an Element Manager or Network Element) can communicate basic Configuration Management related information to one or several 'IRPManagers' (typically Network Managers). This version of the IRP is mainly intended for “passive management” of high-level network configuration and status information as required by a Network Manager.
The present document is divided in three main parts:
1. specifies a generic IRP Information Service with operations and notifications to be used by an ‘IRPManager’ to retrieve information on managed objects maintained by an ‘IRPAgent’.
2. specifies a generic Network Resource Model, NRM (also referred to as a Management Information Model - MIM) with definitions of Managed Object Classes.
3. defines the UMTS management NRM by reusing this generic model either by direct reuse or sub-classing.
The Configuration Management (CM) area is very large. The intention is to split the specification of the related interfaces in several IRPs. In addition to the subject IRP, it is expected that IRPs will be defined for functional areas like Security management, Software management, Network & Service provisioning, etc. An important aspect of such a split is that the Network Resource Models (NRMs) defined in different IRPs are consistent. The Basic CM IRP here provides a base for all CM-related resource modelling.
To summarize, the Basic CM IRP has three main purposes:
(1) to define an interface for retrieval of Configuration Management information,
(2) to define a generic Network Resource Model that constitutes a base from which other (more specialized) resource models can inherit, and
(3) to define the applied UMTS management Network Resource Model.
|
32.106-6
|
Telecommunication management; Configuration Management (CM); Part 6: Basic CM Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)
|
TS
|
3.4.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.106-6/32106-6-340.zip
|
The purpose of this Basic Configuration Management (CM) IRP: Information Service CORBA Solution Set is to define the mapping of the IRP information model (see 3GPP TS 32.106-5 [4]) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
The present document does not describe any Network Resource Model (NRM) – this is described in 3GPP TS 32.106-5 [4]. Please note that 3GPP TS 32.106-5 [4] defines an IRP Information Model, which comprises both an IS and NRM definition.
|
32.106-7
|
Telecommunication management; Configuration Management (CM); Part 7: Basic CM Integration Reference Point (IRP): Common Management Information Protocol (CMIP) Solution Set (SS)
|
TS
|
3.3.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.106-7/32106-7-330.zip
|
The present document defines a CMIP Solution Set for the Basic CM IRP introduced in 3GPP TS 32.106-5 [15].
The version of this CMIP Solution Set is 1:1, where the first “1” means that it corresponds to the Information Model version 1, and the second “1” means that it is the first CMIP Solution Set corresponding to Information Model version 1.
Clause 4 maps the protocol- and technology-independent operations, parameters, notifications and the Network Resource Model specified in the Basic CM IRP Information Model (Chapter 6 of 3GPP 3GPP TS 32.106-5 [15]) onto the corresponding CMIP/CMISE equivalences. The important technical aspects specific to this CMIP Solution Set are also described there. The GDMO definitions are introduced in Clause5. Clause 6 contains the ASN.1 definitions related to the GDMO definitions provided in clause 5.
|
32.106-8
|
Telecommunication management; Configuration Management (CM); Part 8: Name convention for Managed Objects
|
TS
|
3.2.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.106-8/32106-8-320.zip
|
A more detailed background and introduction of the IRP concept is given in 3G TS 32.101 [11] and 3G TS 32.102 [12].
To perform network management tasks, co-operating applications require identical interpretation of names assigned to network resources under management. Such names are required to be unambiguous as well. The present document recommends one name convention for network resources under management in the IRP context.
To facilitate integration of network management information obtained via multiple IRPs of different technologies such as CMIP and CORBA, identical network resource name semantics must be conveyed in all IRPs. The present document specifies one such name convention.
|
34.901
|
Test Time Optimisation based on statistical approaches; Statistical theory applied and evaluation of statistical significance
|
TR
|
3.0.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/34_series/34.901/34901-300.zip
|
The present document describes the statistical theory and concepts applied in the conformance test of the user equipment (UE) so as to improve test speed.
|
34.907
|
Report on electrical safety requirements and regulations
|
TR
|
3.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/34_series/34.907/34907-300.zip
|
The present document, that will not be maintained, provides information describing the situation in March 1999.
The present document provides the information on electrical safety requirements for Information and Technical equipment including 3G mobile phone in each country and region.
[The main objective of the present document is to give an outline on electrical safety in each country and region, to people who are not familiar with this issue. Therefore, the information in the present document will not be kept updated with the latest information.] The present document summarizes the differences between international standards IEC60950 and national standards and also refers to regulations with regard to the conformity assessment because each country has standards, which are different from other countries.
Most information in the present document is quoted from IEC's publications. Therefore the present document neither defines any new electrical safety requirements nor contradicts IEC's policy.
|
34.925
|
Specific Absorption Rate (SAR) requirements and regulations in different regions
|
TR
|
3.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/34_series/34.925/34925-300.zip
|
The present document, that will not be maintained, provides information describing the situation in May 1999.
The present document provides information on Radio Frequency (RF) exposure limits and assessment methods for IMT-2000 terminals. It summarises international, regional and national recommendations, standards and regulations relevant to current and future mobile communication devices.
The present document cover only terminal devices that are normally operated close to the user, approximately within 20 cm of any part of the body. For other IMT-2000 RF transmitting equipment, for example base stations, other RF exposure standards, limits and assessment methods than those described in the present document may be applied.
The present document does not define any new RF exposure limits or assessment methods. It refers to recommendations, standards and regulations that already exist or are under development. Like other existing mobile communication terminals, IMT-2000 terminals will be recommended or requested to comply with these guidelines.
|
24.437
|
Digital asset, Spatial mapping and Spatial anchors server - Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification;
|
TS
|
0.1.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.437/24437-010.zip
|
The present document specifies the protocol aspects and APIs for the metaverse application over the 3GPP network for SAn-UU and SM-UU reference points. The APIs are specified as RESTful APIs except for custom operations wherever required.
The present document is applicable to the user equipment (UE) supporting the digital asset as described in 3GPP TS 23.438 [3], spatial mapping and spatial anchor client functionalities as described in 3GPP TS 23.437 [2], to the application server supporting the digital asset as described in 3GPP TS 23.438 [3], spatial mapping and spatial anchor server functionalities as described in 3GPP TS 23.437 [2] and to the application server supporting the vertical application server (VAL server) functionality as defined in specific vertical application service (VAL service) specification.
NOTE: The specification of the VAL server for a specific VAL service is out of scope of the present document.
|
35.237
|
Specification of the MILENAGE-256 algorithm set: An example set of 256-bit 3GPP Authentication and Key Generation functions f1, f1*, f2, f3, f4, f5, f5* and f5**; Document 4: Summary and Results of Design and Evaluation
|
TS
|
0.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/35_series/35.237/35237-010.zip
|
Editor's Note: This clause contains scope information from ETSI SAGE for selected option.
The present document …
|
33.742
|
5G Security Assurance Specification (SCAS); Split gNB product classes
|
TS
|
0.3.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.742/33742-030.zip
|
The present document contains objectives, requirements and test cases that are specific to the various split gNB network product classes. The gNB can be deployed as more than one entity by splitting the gNB into gNB-CU and gNB-DU(s) and possibly further splitting the gNB-CU into gNB-CU-CP and gNB-CU-UP(s) (see TS 38.401 [5]). Test cases for such deployments are provided. The present document refers to the Catalogue of General Security Assurance Requirements (see TS 33.117 [2]) and formulates specific adaptions of the requirements and test cases given there, as well as specifying requirements and test cases unique to the various split gNB network product class.
|
33.929
|
Lawful Interception (LI) implementation guidance
|
TR
|
0.0.21
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.929/33929-00l.zip
|
The present document provides architectural diagrams, conceptual scenarios, flow-diagrams, examples, and other background information which can be useful to implement the LI functions defined in TS 33.126 [2], TS 33.127 [3] and TS 33.128 [4].
|
28.544
|
Management and orchestration; Self-Organizing Networks (SON) for 5G networks; Network Resource Model (NRM)
|
TS
|
0.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.544/28544-000.zip
|
The present document …
|
25.902
|
Iub/Iur congestion control
|
TR
|
6.1.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.902/25902-610.zip
| |
36.276
|
Overall description of LTE-based 5G broadcast
|
TR
|
1.0.0
|
R1
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.276/36276-100.zip
|
The present document provides an overview and overall description of the LTE-based 5G terrestrial broadcast comprising:
- a service delivering Free To Air content [2];
- a radio network comprising only MBMS-dedicated cells or FeMBMS/Unicast-mixed cells [3] as transmitters; and
- Receive Only Mode (ROM) devices and UEs supporting FeMBMS [4] as receivers.
Details of the radio interface protocols and procedures are specified in companion specifications of the 36 series.
This document is a 'living' document, i.e. it is permanently updated and presented to TSG-RAN meetings.
|
38.173
|
TDD operating band in Band n48
|
TS
|
0.0.1
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.173/38173-001.zip
|
The present document is a technical report for the work item of TDD operating band in Band n48.
|
25.901
|
Network Assisted Cell Change (NACC) from UTRAN to GERAN; Network side aspects
|
TR
|
7.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.901/25901-700.zip
| |
22.969
|
Feasibility study on enhancements of Public Warning System (PWS)
|
TR
|
1.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.969/22969-100.zip
|
The present document describes new use cases and potential requirements applicable to Public Warning Services for
- UEs with diverse form-factors whose user interface is different from the conventional mobile phones; and
- UEs that are defined by applying 3GPP system to non-ICT industry businesses (e.g. vehicles or machines such as IoT devices or robots) and have the different UE role from what 3GPP has traditionally assumed.
In addition, it considers the improvement of the understandability of the PWS message e.g. displaying language independent or graphical content to users, especially foreigners who might not understand the language used in the text or people with physical disability who may be sight impaired and unable to read the text. So it deals with user interface related potential requirements to address the presentation of the warning message considering circumstances such as language being used (e.g. international roaming scenario where the user does not understand the local language) or users with disability (e.g. people with vision impairment).
The present document does not cover use cases or potential requirements for US WEA and Japan ETWS so the results of this document are not applicable for US and Japan. This document considers national variants of EU-Alert and KPAS related service scenarios and potential requirements.
|
24.568
|
WLAN connectivity for 5GS Management Object (MO)
|
TS
|
0.1.1
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.568/24568-011.zip
|
The present document defines WLAN connectivity for 5GS management objects used by the network and the UE.
The Management Objects consist of following relevant parameters for:
- WLAN access network discovery; and
- non-3GPP access node (e.g. N3IWF) selection;
that can be managed by the network.
Editor's note: The content of scope will have more information when related stage 2 is completed.
|
28.542
|
Management and orchestration of networks and network slicing; 5G Core Network (5GC) Network Resource Model (NRM); Stage 1
|
TS
|
1.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.542/28542-100.zip
|
The present document specifies the requirements for the Network Resource Model (NRM) definitions of 5G Core Network (5GC), to support the management of variety of 5GC network functions and features defined in 3GPP TS 23.501 [2].
|
28.543
|
Management and orchestration of networks and network slicing; 5G Core Network (5GC) Network Resource Model (NRM); Stage 2 and stage 3
|
TS
|
1.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.543/28543-110.zip
|
The present document specifies the Information Model definitions and Solution Set definitions for 5G Core Network (5GC) network resource model, to fulfil the requirements identified in 3GPP TS 28.542 [2].
The Information Model definitions define the semantics and behaviour of information object class attributes and relations visible on the management interfaces in a protocol and technology neutral way. And Solution Set definitions define one or more solution set(s) with specific protocol(s) according to the Information Model definitions
|
28.546
|
Management and orchestration of networks and network slicing; Fault Supervision (FS); Stage 2 and stage 3
|
TS
|
0.3.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.546/28546-030.zip
|
The present document …
|
28.551
|
Management and orchestration of networks and network slicing; Performance Management (PM); Stage 2 and stage 3
|
TS
|
0.3.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.551/28551-030.zip
| |
28.553
|
Management and orchestration of networks and network slicing; 5G Core Network (5GC) performance measurements and assurance data
|
TS
|
0.4.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.553/28553-040.zip
|
This document specifies the performance measurements and assurance data for 5GC Network Functions.
The performance measurements and assurance data are defined based on the measurement template as described in TS 32.404 [3].
|
29.516
|
5G System; Interworking between 5G Network and external Data Networks; Stage 3
|
TS
|
0.1.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.516/29516-010.zip
|
The present document defines the stage 3 interworking procedures for 5G Network interworking between:
a) PLMN and external DN; and
b) PLMN and PLMN.
The stage 2 requirements and procedures are contained in 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3].
For interworking between 5G PLMN and external DNs, the present document is valid for both 3GPP accesses and non-3GPP accesses.
|
32.159
|
TS template for stage 2 and stage 3 of management service definitions
|
TS
|
0.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.159/32159-000.zip
|
The present document contains the template to be used for the production of all Management Services stage 2 and stage 3 specifications.
|
36.934
|
LTE Extended 1.5 GHz SDL band (1427 – 1518 MHz)
|
TR
|
0.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.934/36934-010.zip
|
The present document is a technical report for the LTE Extended 1.5 GHz FDD supplemental downlink (SDL) band covering 1427 – 1518 MHz. It is intended to be specified for E-UTRA for operations at least in Europe with the possibility of other countries outside of Europe. As it is defined as SDL, the band is to be used in CA for E-UTRA. The LTE CA combination of Band 20 + FDD SDL Band 1427 – 1518 MHz has selected.
|
38.141
|
NR; Base Station (BS) conformance testing
|
TS
|
0.0.3
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/38_series/38.141/38141-003.zip
|
The present document specifies the Radio Frequency (RF) test methods and conformance requirements for NR Base Station (BS). These have been derived from, and are consistent with the NR BS specification defined in [2]. The technical specification is in 2 parts, part 1 covers conducted requirements and part 2 covers radiated requirements.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.