id
stringlengths 5
12
| title
stringlengths 8
250
| type
stringclasses 2
values | version
stringclasses 212
values | working_group
stringclasses 30
values | url
stringlengths 67
81
| scope
stringlengths 0
65.7k
|
|---|---|---|---|---|---|---|
23.073
|
Support of Localised Service Area (SoLSA); Stage 2
|
TS
|
4.0.0
|
N4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.073/23073-400.zip
|
The present document specifies the stage 2 description of the SoLSA service, which gives the network operator the basis to offer subscribers or group of subscribers different services, different tariffs and different access rights depending on the geographical location of the subscriber, according to GSM 02.43.
|
23.821
|
Architecture Principles for Reelase 2000
|
TR
|
1.0.1
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.821/23821-101.zip
|
The scope of this Technical Report is to list architectural requirements, features, functions and solutions of UMTS inside the scope of UMTS Release 00. These are working assumptions agreed by TSG SA WG2. The TR focuses on
- new/modified functionality as compared to Release 99
- technical description of the features, functions and solutions of R00.
It is expected that this TR will act as a basis for the detailed Stage 2 specification work.
This TR has been created to ease the development of R00 work prior to the finalization of the R99 specifications. In conjunction with when R99 is finalized, work on the TR will cease and the relevant CRs will be produced to incorporate the contents of this TR within the R00 version of the specifications."
|
23.874
|
Feasibility study of architecture for network requested PDP context activation with User-ID
|
TR
|
1.3.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.874/23874-130.zip
|
The purpose of this technical report is to study the feasibility of architecture for push services over Packet Switched Networks.
In the present document, the architecture for the delivery network is examined and the architectures for the user terminal and the application server are out of scope.
|
23.907
|
Quality of Service (QoS) concept
|
TR
|
1.2.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.907/23907-120.zip
|
Scope of this document is to provide the framework for Quality of Service in UMTS. The document shall be used as a living document which will cover all issues related Quality of Service in UMTS.
|
23.913
|
UMTS Turbo-Charger
|
TR
|
1.0.0
|
-
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.913/23913-100.zip
| |
23.922
|
Architecture for an All IP network
|
TR
|
4.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.922/23922-400.zip
|
This technical report will propose an architecture that provisions an all-IP architecture option for release 00. The purpose of the technical report is to
• identify key issues and affected ongoing 3GPP work that need to be resolved and
• propose a high level work plan for completion of an all IP release 00 UMTS standard
in order to provide this architectural option within Release 2000.
|
25.835
|
Report on hybrid ARQ type II/III
|
TR
|
1.0.0
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.835/25835-100.zip
|
This technical report captures the results of the work on the work item “Hybrid ARQ Type II/III”. This includes technical solutions and their comparison. The report covers impacts on all RAN WGs.
|
25.837
|
Hybrid ARQ Type II/III (Iub/Iur aspects)
|
TR
|
0.1.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.837/25837-010.zip
|
The purpose of the present document is to gather all information concerning the impacts of Hybrid ARQ Type II/III on RAN WG3.
|
25.845
|
FDD RACH and AICH performance requirements
|
TR
|
0.0.3
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.845/25845-003.zip
|
This document is a Technical Report concerning the WG4 work item “Performance specification of demodulation of common channels”. In this report FDD RACH and AICH receptions are considered.
|
25.924
|
Opportunity Driven Multiple Access (ODMA)
|
TR
|
1.0.0
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.924/25924-100.zip
|
The present document provides a description of Opportunity Driven Multiple Access (ODMA).
ODMA is a relay transmission protocol to be applied to UMTS TDD. ODMA will provide the ability to maintain high data rates within a TDD towards the edges of traditional TDD coverage. The main purpose of ODMA is:
- Increase the high data rate coverage within a cell.
- Increase the capacity of TDD.
- Provide distributed network architecture for spot coverage and traffic hotspots.
|
25.938
|
Terminal power saving features
|
TR
|
2.0.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.938/25938-200.zip
|
The pupose of the present document is to help the TSG RAN WG3 group to specify the changes to existing specifications, needed for the introduction of the “Terminal Power Saving Features” option for Release 2000.
WG1 is the leading working group of this Work Item (WI) and has its own TR. The purpose of this TR is not to replace the TR or any decisions made in the leading WG. Rather, it is intended to gather all the information in order to trace the history and the status of the Work Task in other RAN WGs, and discuss issues that WG3 has impact on.
It is not intended to replace contributions and Change Requests, but only to list conclusions and make references to agreed contributions and CRs. When solutions are sufficiently stable, the CRs can be issued.
It describes agreed requirements related to the Work Task.
It identifies the affected specifications with related Change Requests.
It also describes the schedule of the Work Task.
This document is a ‘living’ document, i.e. it is permanently updated and presented to all TSG-RAN meetings
|
26.920
|
Architectural Model for the 3G Transcoders
|
TR
|
0.1.1
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.920/26920-011.zip
|
The present document is a description of the transcoder in the UMTS networksl. The initial aim of this document is to have a reference model for the standardization work carried out by the 3GPP Technical Specification Groups.
|
30.504
|
Work Plan and Study Items - RAN WG4
|
TR
|
2.2.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/30_series/30.504/30504-220.zip
| |
30.801
|
Overall Project Plan
|
TR
|
1.1.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/30_series/30.801/30801-110.zip
| |
30.802
|
Project plan on Bearer Services and QoS
|
TR
|
4.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/30_series/30.802/30802-400.zip
|
After completion of MAP version 2 the introduction of new or modification of existing features and services in phase 2+ and UMTS requires changes to the Mobile Application Part (MAP) specification (see [1]). This handbook gives some guidelines on how to introduce changes into the MAP. Protocol as well as application aspects.
|
32.105
|
3G charging and billing; Stage 2 description
|
TS
|
0.0.4
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.105/32105-004.zip
|
This Technical Specification describes the Architecture, Principals and Call Event specifications of charging and billing for the provision of service and services by a 3G system.
This standard is not intended to duplicate existing standards or standards being developed by other groups on these topics, and will reference these where appropriate. This standard will elaborate on the charging requirements described in the Charging Principles in UMTS 22.01 Service Principles. It will allow the generation of accurate charging information to be used in the commercial and contractual relationships between the parties concerned.
The call and event data generated by the network elements of the 3G network, is required for a number of telecom management activities including, but not limited to, the following:
• the billing of home subscribers, either directly or via service providers, for network utilisation charges;
- the settlement of accounts for traffic carried or services performed by fixed network and other operators;
- the settlement of accounts with other PLMNs for roaming traffic via the transferred account procedure;
- statistical analysis of service usage;
- as historical evidence in dealing with customer service and billing complaints;
In addition to the information collected from these network elements, network management functions are required for the administration of charging data.
For the purpose of the present document, the call and event data is considered to be collected, in real-time, by network element function (NEF) blocks located within the recording entities.
The data collected by the NEFs is sent to, or collected by, the appropriate Operations System Function (OSF) blocks for storage and further processing.
The location of the OSF is implementation specific and may, for example, be provided either by an Administration Centre (ADC) or integrated within the network elements themselves.
The following is beyond the scope of this TS, and therefore this TS does not describe:
-
The objectives of this standardisation are:
• to provide the descriptions of events and triggers for the generation of Call detail records;
- to provide the descriptions for Call and event Call detail records;
- to produce a description of the collection techniques for accounting administration and CDR generation;
and
- to define a method for the transmission of CDRs over an open interface.
|
32.111
|
3G Fault Management
|
TS
|
4.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.111/32111-400.zip
|
The present document specifies the overall requirements for 3G Fault Management as it applies to the NE, EM and NM.
Clauses 4 and 5 define the fault management concept and functional requirements for the detection of faults and the generation, collection and presentation of alarms, operational state data and test results across 3G systems. These functions are described on a non-formal level since the formal standardisation of these functions across the different vendors' equipment is not required. The functional areas to be specified in this part of the document cover:
• fault surveillance and detection in the NEs;
• notification of alarms (including alarm cease) and operational state changes;
• retrieval of current alarms from the NEs;
• fault isolation and defence mechanisms in the NEs;
• alarm filtering;
• management of alarm severity levels;
• alarm and operational state data presentation and analysis at the OS;
• retention of alarm and operational state data in the NEs and the OS; and
• the management of tests.
Any (re)configuration activity exerted from the OMC as a consequence of faults will not be subject of the present document, these are described in [1].
Clauses 6 and 7 of the present document describe specific aspects of the Fault Management for the UTRAN and the CN, respectively, with particular emphasis on the exact fault definitions and alarm information to be generated. The definition of the test procedures and the relationship with the UTRAN resp. CN management architecture as defined in [3].
Finally, Clause 8 of the present document defines the functional requirements for the standard Itf-N, for the purpose of Fault Management of 3G networks, as seen from the Network Manager (NM). The Itf-N is fully standardised so as to connect systems of any vendor to the NM via this interface.
|
32.301-3
|
Telecommunication management; Configuration Management (CM); Part 3: Notification Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) solution set
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.301-3/32301-3-200.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 [5].
|
32.301-4
|
Telecommunication management; Configuration Management (CM); Part 4: Notification Integration Reference Point: Common Management Information Protocol (CMIP) solution
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.301-4/32301-4-200.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 3G TS 32.301-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 Notification Management over the CMIP interfaces
• Clause 6 contains the ASN.1 definitions supporting the GDMO definitions provided in clause 5.
|
32.402
|
Telecommunication management; Performance Management (PM); Performance measurements - GSM
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.402/32402-200.zip
|
The present document describes the TMN model for the administration of measurements and the collection of measurement result data in a GSM system. It also includes the measurement definitions for GSM. The concept and functional requirements for performance management in wireless GSM and UMTS systems is set out in TS 32.401 [31], while the measurements for UMTS and combined UMTS/GSM systems are specified in TS 32.403 [32].
|
32.601-1
|
Telecommunication management; Configuration Management (CM); Part 1: Basic CM Integration Reference Point (IRP): requirements
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.601-1/32601-1-200.zip
|
The present document defines , in addition to the requirements defined in [1], [2] and [3], the requirements for the present IRP: Basic Configuration Management IRP.
|
32.601-2
|
Telecommunication management; Configuration Management (CM); Part 2: Basic CM Integration Reference Point (IRP) information model
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.601-2/32601-2-200.zip
|
The present document defines a component of 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 Configuration Management (CM) area is very large. The intention is to split the specification of the related interfaces in several IRPs – as described in the Introduction clause above. An important aspect of such a split is that the Network Resource Models (NRMs) defined in different IRPs containing NRMs are consistent, and that NRMs supported by an IRPAgent implementation can be accessed as one coherent model through one IRP Information Service. The Basic CM IRP: IS defined herein provides one such Information Service.
Thus, to summarize, the Basic CM IRP: IS defined in the present document has the following main purpose: to define an interface for retrieval of Configuration Management information.
(1)
|
32.601-3
|
Telecommunication management; Configuration Management (CM); Part 3: Basic CM Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) solution set
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.601-3/32601-3-200.zip
|
The purpose of this Basic Configuration Management (CM) IRP: CORBA Solution Set is to define the mapping of the Basic CM IRP: IS (see 3GPP TS 32.601-2 [4]) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
This document defines NRM independent data types, methods and notifications.
|
32.601-4
|
Telecommunication management; Configuration Management (CM); Part 4: Basic CM Integration Reference Point (IRP): Common Management Information Protocol (CMIP) solution set
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.601-4/32601-4-200.zip
|
The present document specifies the Common Management Information Protocol (CMIP) Solution Set (SS) for the Basic CM Integration Reference Point (IRP): Information Service defined in 3GPP TS 32.601-2. 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.602-1
|
Telecommunication management; Configuration Management (CM); CMt: Bulk CM Integration Reference Point (IRP) requirements
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.602-1/32602-1-200.zip
|
The present document describes the Bulk Configuration Management (CM) requirements for managing a 3G network. This is described from the management perspective in 3G TS 32.101 [1] and 3G TS 32.102 [2].
The Itf‑N for CM is built up by a number of Integration Reference Points (IRPs) and a related Name Convention 3G TS 32.300 [3], 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 a Name Convention) are defined, used by this as well as by other specifications for Telecom Management produced by 3GPP. These IRPs are defined in separate 3GPP specifications, and listed in the table in the Introduction clause above. This document defines the requirements for the Bulk CM IRP.
|
32.602-2
|
Telecommunication management; Configuration Management (CM); CMt: Bulk Configuration Management Integration Reference Point (IRP): Information service
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.602-2/32602-2-200.zip
| |
32.602-3
|
Telecommunication management; Configuration Management (CM); CM: Bulk Configuration Management Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) solution set
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.602-3/32602-3-200.zip
|
The purpose of this Bulk CM IRP: CORBA Solution Set is to define the mapping of the IRP information service (see 3GPP TS 32.602-2 [3]) 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) – they are described in Generic Network Resources IRP: NRM 3GPP TS 32.620-2 [4], UTRAN Network Resources IRP: NRM 3GPP TS 32.622-2 [11], GERAN Network Resources IRP: NRM 3GPP TS 32.623-2 [12].
|
32.602-4
|
Telecommunication management; Configuration Management (CM); CM: Bulk Configuration Management Integration Reference Point (IRP): Common Management Information Protocol (CMIP) solution set
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.602-4/32602-4-200.zip
|
The present document specifies the Common Management Information Protocol (CMIP) Solution Set (SS) for the Bulk CM Integration Reference Point (IRP): Information Service defined in 3GPP TS 32.602-2. 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.602-5
|
Telecommunication management; Configuration Management (CM); CM: Bulk Configuration Management Integration Reference Point (IRP): XML file format definition
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.602-5/32602-5-200.zip
|
The present document defines the XML file formats for the configuration data files and session log files of Bulk CM IRP IS [1].
Those file formats are based on XML [2], XML Schema [3] [4] [5] and XML Namespace [6] standards.
|
32.620-1
|
Telecommunication management; Configuration Management (CM); Part 1: Generic network resources Integration Reference Point (IRP): requirements
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.620-1/32620-1-200.zip
|
The present document defines , in addition to the requirements defined in [1], [2] and [3], the requirements for the present IRP: Generic Network Resources IRP.
|
32.620-2
|
Telecommunication management; Configuration Management (CM); Part 2: Generic network resources Integration Reference Point (IRP): Network Resource Model (NRM)
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.620-2/32620-2-200.zip
|
The present document (Generic Network Resources IRP: Network Resource Model) defines an Integration Reference Point (IRP) through which an 'IRPAgent' (typically an Element Manager or Network Element) can communicate Network Management related information to one or several 'IRPManagers' (typically Network Managers).
The present document specifies a generic Network Resource Model, NRM (also referred to as a Management Information Model - MIM) with definitions of Managed Object Classes.
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 Generic Network Resources IRP here provides a base for all resource modelling.
To summarize, the Generic Network Resources IRP main purpose is to define a generic Network Resource Model that constitutes a base from which other (more specialized) resource models can inherit or have associations with.
|
32.620-3
|
Telecommunication management; Configuration Management (CM); Part 3: Generic network resources Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) solution set
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.620-3/32620-3-200.zip
|
The TS 32.620 series (Generic Network Resources IRP) defines an Integration Reference Point (IRP) through which an 'IRPAgent' (typically an Element Manager or Network Element) can communicate Network Management related information to one or several 'IRPManagers' (typically Network Managers).
This series of documents specifies a generic Network Resource Model, NRM (also referred to as a Management Information Model - MIM) with definitions of Information Object Classes and Managed Object Classes.
The present document specifies the Corba Solution set.
|
32.620-4
|
Telecommunication management; Configuration Management (CM); Part 4: Generic network resources: Integration Reference Point (IRP) Common Management Information Protocol (CMIP) solution set
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.620-4/32620-4-200.zip
|
The present document specifies the Common Management Information Protocol (CMIP) Solution Set (SS) for the Generic Network Resource Integration Reference Point (IRP): Network Resource Model defined in 3GPP TS 32.620-2. 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.621-1
|
Telecommunication management; Configuration Management (CM); Part 1: Core network resources Integration Reference Point (IRP): requirements
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.621-1/32621-1-200.zip
|
The present document defines , in addition to the requirements defined in [1], [2] and [3], the requirements for the present IRP: Core Network Resources IRP.
|
32.621-2
|
Telecommunication management; Configuration Management (CM); Core Network Resources Integration Reference Point (IRP): Network Resource Model (NRM)
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.621-2/32621-2-200.zip
|
The present document is part of an Integration Reference Point (IRP) named “Core Network Resources IRP”, through which an 'IRPAgent' (typically an Element Manager or Network Element) can communicate Configuration Management information to one or several 'IRPManagers' (typically Network Managers) concerning CN resources. 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 “Core Network Resources IRP” comprises a set of specifications defining Requirements, a protocol neutral Network Resource Model (NRM) and corresponding Solution Set(s).
The present document specifies the protocol neutral Core Network Resources IRP: Network Resource Model. It reuses relevant parts of the generic NRM in [16], either by direct reuse or sub-classing, and in addition to that defines CN specific Managed Object Classes.
The Configuration Management (CM) area is very large. The intention is to split the specification of the related interfaces in several IRPs – as described in the Introduction clause above. An important aspect of such a split is that the Network Resource Models (NRMs) defined in different IRPs containing NRMs are consistent, and that NRMs supported by an IRPAgent implementation can be accessed as one coherent model through one IRP Information Service.
To summarize, the present document has the following main purpose: to define the applied CN specific Network Resource Model, based on the generic NRM in [16].
Finally, in order to access the information defined by this NRM, an IRP Information Service (IS) is needed, such as the Basic CM IRP: IS [17]. However, which Information Service that is applicable is outside the scope of this document.
|
32.621-3
|
Telecommunication management; Configuration Management (CM); Part 3: Core network resources Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) solution set
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.621-3/32621-3-200.zip
|
The purpose of this Core Network Resources IRP: CORBA Solution Set is to define the mapping of the IRP information model (see 3GPP TS 32.621-2 [3]) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
|
32.621-4
|
Telecommunication management; Configuration Management (CM); Part 4: Core network resources Integration Reference Point (IRP): Common Management Information Protocol (CMIP) solution set
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.621-4/32621-4-200.zip
|
The present document specifies the Common Management Information Protocol (CMIP) Solution Set (SS) for the CN Network Resource Integration Reference Point (IRP): Network Resource Model defined in 3GPP TS 32.621-2. 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.622-1
|
Telecommunication management; Configuration Management (CM); Part 1: UTRAN network resources Integration Reference Point (IRP): requirements
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.622-1/32622-1-200.zip
|
The present document defines , in addition to the requirements defined in [1], [2] and [3], the requirements for the present IRP: UTRAN Network Resources IRP.
|
32.622-2
|
Telecommunication management; Configuration Management (CM); Part 2: UTRAN network resources Integration Reference Point (IRP): Network Resource Model (NRM)
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.622-2/32622-2-200.zip
|
The present document is part of an Integration Reference Point (IRP) named “UTRAN Network Resources IRP”, through which an 'IRPAgent' (typically an Element Manager or Network Element) can communicate Configuration Management information to one or several 'IRPManagers' (typically Network Managers) concerning UTRAN resources. The “UTRAN Network Resources IRP” comprises a set of specifications defining Requirements, a protocol neutral Network Resource Model (NRM) and corresponding Solution Set(s).
The present document
1. specifies the protocol neutral UTRAN Network Resources IRP: Network Resource Model. It reuses relevant parts of the generic NRM in [16], either by direct reuse or sub-classing, and in addition to that defines UTRAN specific Managed Object Classes.
The Configuration Management (CM) area is very large. The intention is to split the specification of the related interfaces in several IRPs – as described in the Introduction clause above. An important aspect of such a split is that the Network Resource Models (NRMs) defined in different IRPs containing NRMs are consistent, and that NRMs supported by an IRPAgent implementation can be accessed as one coherent model through one IRP Information Service.
To summarize, the present document has the following main purpose:
(1) to define the applied UTRAN specific Network Resource Model, based on the generic NRM in [16].
Finally, in order to access the information defined by this NRM, an IRP Information Service (IS) is needed, such as the Basic CM IRP: IS [17] or the Bulk CM IRP: IS [18]. However, which Information Service that is applicable is outside the scope of this document.
|
32.622-3
|
Telecommunication management; Configuration Management (CM); Part 3: UTRAN network resources Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) solution set
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.622-3/32622-3-200.zip
|
The purpose of this UTRAN Network Resources IRP: CORBA Solution Set is to define the mapping of the IRP information model (see 3GPP TS 32.622-2 [4]) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
|
32.622-4
|
Telecommunication management; Configuration Management (CM); Part 4: UTRAN network resources Integration Reference Point (IRP): Common Management Information Protocol (CMIP) solution set
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.622-4/32622-4-200.zip
|
The present document specifies the Common Management Information Protocol (CMIP) Solution Set (SS) for the UTRAN Network Resource Integration Reference Point (IRP): Network Resource Model defined in 3GPP TS 32.622-2. 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.623-1
|
Telecommunication management; Configuration Management (CM); Part 1: GERAN network resources Integration Reference Point (IRP): requirements
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.623-1/32623-1-200.zip
|
The present document defines , in addition to the requirements defined in [1], [2] and [3], the requirements for the present IRP: GERAN Network Resources IRP.
|
32.623-2
|
Telecommunication management; Configuration Management (CM); Part 2: GERAN network resources Integration Reference Point (IRP): Network Resource Model (NRM)
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.623-2/32623-2-200.zip
|
The present document is part of an Integration Reference Point (IRP) named “GERAN Network Resources IRP”, through which an 'IRPAgent' (typically an Element Manager or Network Element) can communicate Configuration Management information to one or several 'IRPManagers' (typically Network Managers) concerning GERAN resources. The “GERAN Network Resources IRP” comprises a set of specifications defining Requirements, a protocol neutral Network Resource Model (NRM) and corresponding Solution Set(s).
The present document specifies the protocol neutral GERAN Network Resources IRP: Network Resource Model. It reuses relevant parts of the generic NRM in [16], either by direct reuse or sub-classing, and in addition to that defines GERAN specific Managed Object Classes.
The Configuration Management (CM) area is very large. The intention is to split the specification of the related interfaces in several IRPs – as described in the Introduction clause above. An important aspect of such a split is that the Network Resource Models (NRMs) defined in different IRPs containing NRMs are consistent, and that NRMs supported by an IRPAgent implementation can be accessed as one coherent model through one IRP Information Service.
To summarize, the present document has following main purpose: to define the applied GERAN specific Network Resource Model, based on the generic NRM in [16].
Finally, in order to access the information defined by this NRM, an IRP Information Service (IS) is needed, such as the Basic CM IRP: IS [17] or the Bulk CM IRP: IS [18]. However, which Information Service that is applicable is outside the scope of this document.
|
32.623-3
|
Telecommunication management; Configuration Management (CM); Part 3: GERAN network resources Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) solution set
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.623-3/32623-3-200.zip
|
The purpose of this GERAN Network Resources IRP: CORBA Solution Set is to define the mapping of the IRP information model (see 3GPP TS 32.623-2 [4]) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
|
32.623-4
|
Telecommunication management; Configuration Management (CM); Part 4: GERAN network resources Integration Reference Point (IRP): Common Management Information Protocol (CMIP) solution set
|
TS
|
2.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.623-4/32623-4-200.zip
|
The present document specifies the Common Management Information Protocol (CMIP) Solution Set (SS) for the GERAN Network Resource Integration Reference Point (IRP): Network Resource Model defined in 3GPP TS 32.623-2. 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.
|
34.910
|
Identification of test requirements for regulatory purposes in different regions/countries
|
TR
|
1.0.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/34_series/34.910/34910-100.zip
|
The present document contains a collection of test requirements identified for regulatory purposes in different regions/countries.
The actual test case descriptions will be contained in other documents.
|
41.102
|
GSM Release 4 specifications
|
TS
|
4.9.0
|
SP
|
https://www.3gpp.org/ftp/Specs/archive/41_series/41.102/41102-490.zip
|
The present document identifies the GSM system specifications for GSM Release 4.
|
42.032
|
Immediate Service Termination (IST); Service description; Stage 1
|
TS
|
4.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/42_series/42.032/42032-400.zip
|
This Technical Specification specifies the stage 1 description of the Immediate Service Termination (IST) service which provides the means for the HPLMN to terminate all the activities of an HPLMN subscriber in a VPLMN.
The purpose of this network feature is to enable the HPLMN to control the activities of its subscribers, particularly while they are roaming. If the HPLMN decides (based upon information received via Fraud Information Gathering System (FIGS) or other systems) that a roaming subscriber is behaving in a fraudulent or suspicious manner, the HPLMN can terminate all activities of the subscriber, including calls (including transferred and diverted calls) that are in progress.
This procedure can also be used to terminate all the activities of a subscriber when the subscription has ended.
The primary aim is to enable service providers/network operators to use IST to reduce the amount of money that they lose because of roaming fraud.
|
42.048
|
Security mechanisms for the SIM Application Toolkit; Stage 1
|
TS
|
4.0.0
|
T3
|
https://www.3gpp.org/ftp/Specs/archive/42_series/42.048/42048-400.zip
|
The present document provides standardised security mechanisms in conjunction with the SIM Application Toolkit for the interface between a GSM PLMN Entity and a SIM.
The security mechanisms which are specified are independent of applications.
The present document describes the functional requirements of the security mechanisms with the implementation detail of these mechanisms being described in the stage 2 specification (GSM 03.48).
The present document is the result of a feasibility study carried out on this topic, contained in GSM 11.15.
|
43.035
|
Immediate Service Termination (IST); Stage 2
|
TS
|
4.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/43_series/43.035/43035-410.zip
|
This TS specifies the stage 2 description of the Immediate Service Termination (IST) service which provides the means for the HPLMN to terminate all the activities of an HPLMN subscriber in a VPLMN.
Two implementations of IST are described: an implementation based on CAMEL, and an implementation based on a new MAP command.
|
43.046
|
Technical Realization of Facsimile Group 3 Service - non transparent
|
TS
|
4.0.0
|
N3
|
https://www.3gpp.org/ftp/Specs/archive/43_series/43.046/43046-400.zip
|
The present document deals with the procedures allowing the technical realization of the real time end to end facsimile group 3 service within the GSM PLMN using nontransparent network support according to the definition of the Teleservices 61 and 62 specified in GSM 22.003. Within the present document particular attention is given to Teleservice "Alternate speech/facsimile group 3" (Teleservice 61). However, the definitions apply also to Teleservice "Automatic facsimile group 3" (Teleservice 62) with the exception of all actions concerned with the speech phase. Consequently, in the following descriptions the term "Teleservice" denotes both Teleservice 61 and Teleservice 62 as appropriate.
NOTE: Some facilities associated with alternate speech/ facsimile group 3 may not be available with version 1 of MAP. In particular, the incall modification procedure following an inter MSC handover is not supported by this version. This imposes the limitation that for all calls it will not be possible to change between speech and facsimile following an inter MSC handover.
|
43.048
|
Security Mechanisms for SIM Toolkit Application; Stage 2
|
TS
|
4.0.0
|
T3
|
https://www.3gpp.org/ftp/Specs/archive/43_series/43.048/43048-400.zip
|
The present document specifies the structure of the Secured Packets in a general format and in implementations using Short Message Service Point to Point (SMS-PP) and Short Message Service Cell Broadcast (SMS-CB).
Furthermore, the coding is specified for a set of common application commands within the secured packets. This set is a subset of commands specified in GSM 11.11 [5] and allows remote management of files on the Subscriber Identity Module (SIM) in conjunction with SMS and the SIM Data Download feature of GSM 11.14 [6].
For SIM cards based on GSM 03.19 [15], the set of commands used in the remote applet management is defined in the present document. This is based on the Open Platform card management specification [14]. For SIM cards based on other technologies, other loading mechanisms may be used.
The present document is applicable to the exchange of secured packets between an entity in a GSM PLMN and an entity in the SIM.
Secured Packets contain application messages to which certain mechanisms according to GSM 02.48 [2] have been applied. Application messages are commands or data exchanged between an application resident in or behind the GSM PLMN and on the SIM. The Sending/Receiving Entity in the GSM PLMN and the SIM are responsible for applying the security mechanisms to the application messages and thus turning them into Secured Packets.
|
43.063
|
Packet Data on Signalling channels service (PDS) Service description, Stage 2
|
TS
|
4.0.0
|
N1
|
https://www.3gpp.org/ftp/Specs/archive/43_series/43.063/43063-400.zip
|
The present document specifies stage two of the Packet Data on Signalling channels service (PDS) which allows packet data transmission in GSM networks on dedicated channels.
|
44.008
|
Mobile radio interface layer 3 specification
|
TS
|
4.0.0
|
N1
|
https://www.3gpp.org/ftp/Specs/archive/44_series/44.008/44008-400.zip
|
This EN specifies the procedures used at the radio interface (Reference Point Um, see GSM 04.02) for Call Control (CC), Mobility Management (MM), Radio Resource (RR) management and Session Management (SM). The detailed descriptions of the protocols and the related procedures are described in GSM 04.18, TS 23.108 and TS 24.008.
When the notations for "further study" or "FS" or "FFS" are present in this ETS they mean that the indicated text is not a normative portion of this standard.
These procedures are defined in terms of messages exchanged over the control channels of the radio interface. The control channels are described in GSM 04.03.
The structured functions and procedures of this protocol and the relationship with other layers and entities are described in general terms in GSM 04.07.
|
44.063
|
Packet Data on Signalling channels Service (PDS) Service Description, Stage 3
|
TS
|
4.0.0
|
N1
|
https://www.3gpp.org/ftp/Specs/archive/44_series/44.063/44063-400.zip
|
The present document specifies the protocols for connection management of packet data on signalling channels which is applied on the air interface, the PDSS1 protocol and the PDSS2 protocol.
|
52.071
|
Location Services (LCS); Location services (LCS) management
|
TS
|
4.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/52_series/52.071/52071-410.zip
|
The present document describes the network management for LCS O&M within the digital cellular telecommunications system.
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.
|
01.00
|
Working Procedures for SMG and PT SMG
|
TR
|
8.0.0
|
SP
|
https://www.3gpp.org/ftp/Specs/archive/01_series/01.00/0100-800.zip
|
This document outlines the working methods [to be] used by SMG and its sub-groups and by PT SMG in relation to document management, i.e. handling of specifications, updating procedures, change request procedures, version control mechanisms, specifications status information etc. It complements the rules and procedures defined in ETSI. This document does not stipulate the details of the internal working of the TB sub-groups. From the Technical Specification Group point of view, a task and responsibility is given to a Working Group (WG) directly answering to SMG. In practice, the work/task may be carried out in a subgroup of that WG.
|
01.56
|
GSM Cordless Telephony System (CTS) (Phase 1); CTS Authentication and Key Generation Algorithms Requirements
|
TS
|
8.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/01_series/01.56/0156-800.zip
|
This specification constitutes a requirement specification for a set of associated cryptographic algorithms which is used for Cordless Telephony System (CTS) Radio Interface authentication and key management in the GSM Cordless Telephony System.
This specification is intended to provide ETSI SAGE with the information it requires in order to design and deliver a technical specification for such an algorithm set.
This specification covers the intended use of the algorithm set and use of the algorithm set specification, technical requirements on the algorithm set, requirements on the algorithm set specification and test data, and quality assurance requirements on both the algorithm set and its documentation. The document also outlines the background to the production of this specification.
|
02.01
|
Principles of telecommunication services supported by a GSM Public Land Mobile Network(PLMN)
|
TS
|
8.2.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/02_series/02.01/0201-821.zip
|
The present document coversthe definition of the telecommunication services supported by a GSM PLMN. The purpose of the present document is to provide a method for the characterization and the description of these telecommunication services.
|
02.02
|
Bearer Services (BS) Supported by a GSM Public Land Mobile Network (PLMN)
|
TS
|
8.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/02_series/02.02/0202-800.zip
|
This European Telecommunication Standard (ETS) defines a set of Bearer Services to be provided to GSM PLMN subscribers by a GSM PLMN itself and in connection with other networks. This ETS should also be used as a reference for defining the corresponding required mobile network capabilities which are specified by means of the "GSM PLMN connection type" concept, defined in GSM 03.10 [4].
The recommended provision of the Bearer Services is under the control of the GSM MoU and is out of the scope of ETSI TC-SMG.
Bearer Services not included in this ETS that require modifications to the GSM signalling specifications should not be introduced unilaterally by a mobile network operator.
|
02.03
|
Teleservices Supported by a GSM Public Land Mobile Network (PLMN)
|
TS
|
8.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/02_series/02.03/0203-800.zip
|
The present document describes and defines a recommended set of Teleservices to be supported by a GSM PLMN in connection with other networks as a basis for defining the network capabilities required.
Teleservices not included in the present document should not be introduced unilaterally by a mobile network operator, if the provision of this service requires that the GSM signalling specifications are modified.
|
02.04
|
General on Supplementary Services
|
TS
|
8.1.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/02_series/02.04/0204-810.zip
|
The purpose of this Technical Specification (TS) is to define a recommended set of supplementary services to the Teleservices and Bearer services which will be supported by a GSM PLMN in connection with other networks as a basis for the definition of the network capabilities required.
The descriptions of the different supplementary services are contained in the GSM 02.80 series.
Supplementary services not covered in GSM 02.04 or GSM 02.80 series cannot be introduced unilaterally in any GSM PLMN if they require modification of the GSM signalling Specifications.
Technical realization of supplementary services is described in GSM 03.11 and 04.10.
|
02.07
|
Mobile Station (MS) Features
|
TS
|
8.1.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/02_series/02.07/0207-810.zip
|
This TS defines Mobile Station (MS) features and to classifies them according to their type and whether they are mandatory or optional. The MS features detailed in this TS do not represent an exhaustive list. Those MS features which are subject to Type Approval are described in GSM 11.10 [13].
|
02.31
|
Fraud Information Gathering System (FIGS); Service description; Stage 1
|
TS
|
8.0.1
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/02_series/02.31/0231-801.zip
|
The present document specifies the stage 1 description of the Fraud Information Gathering System (FIGS) feature which provides the means for the HPLMN to monitor the activities of its subscribers in a VPLMN.
The purpose of this network feature is to enable the HPLMN to monitor the activities of its subscribers while they are roaming. The VPLMN collects information about a defined set of activities on monitored subscribers and sends this information back to the HPLMN. This enables the HPLMN to clear certain types of calls and so stop fraudulent use of the GSM system.
The present document enables service providers/ network operators to use FIGS, and service limitation controls such as Operator Determined Barring (ODB) and Immediate Service Termination (IST), to limit their financial exposure to subscribers producing large unpaid bills.
HPLMNs may also choose to monitor the activities of its subscribers within the HPLMN.
|
02.32
|
Immediate Service Termination (IST); Service description; Stage 1
|
TS
|
8.0.1
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/02_series/02.32/0232-801.zip
|
The present document specifies the stage 1 description of the Immediate Service Termination (IST) service which provides the means for the HPLMN to terminate all the activities of an HPLMN subscriber in a VPLMN.
The purpose of this network feature is to enable the HPLMN to control the activities of its subscribers, particularly while they are roaming. If the HPLMN decides (based upon information received via Fraud Information Gathering System (FIGS) or other systems) that a roaming subscriber is behaving in a fraudulent or suspicious manner, the HPLMN can terminate all activities of the subscriber, including calls (including transferred and diverted calls) that are in progress.
This procedure can also be used to terminate all the activities of a subscriber when the subscription has ended.
The primary aim is to enable service providers/network operators to use IST to reduce the amount of money that they lose because of roaming fraud.
|
02.34
|
High Speed Circuit Switched Data (HSCSD); Stage 1
|
TS
|
8.1.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/02_series/02.34/0234-810.zip
|
This Technical Specification (TS) specifies the Stage 1 description of High Speed Circuit Switched Data (HSCSD). HSCSD is a feature that allows users subscribing to the General Bearer Services to access user rates that can be achieved with one or more TCH/F. HSCSD also defines a flexible use of air interface resources which makes efficient and flexible use of higher user rates feasible.
|
02.40
|
Procedures for call progress Indications
|
TS
|
8.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/02_series/02.40/0240-800.zip
|
The present document defines requirements for call progress and related information to be provided to users of the GSM system.
|
02.42
|
Network Identity and Timezone (NITZ); Service Description, Stage 1
|
TS
|
8.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/02_series/02.42/0242-800.zip
|
The present document describes the feature Network Identity and Timezone (NITZ).
This feature provides the means for serving PLMNs to transfer current identity, time, Daylight Saving Time and the local timezone to Mobile Stations (MS)s, and for the MSs to store and use this information. This enhances roaming by permitting accurate indication of PLMN identities that are either newer than the Mobile Equipment (ME) or have changed their name since the ME was sold. Additionally time, Daylight Saving Time and timezone information can be utilised by MEs as desired.
|
02.57
|
Mobile Station Application Execution Environment (MExE) Service description Stage 1
|
TS
|
8.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/02_series/02.57/0257-800.zip
|
This ETSI Technical Specification defines the stage one description of the Mobile Station Application Execution Environment (MExE). Stage one is an overall service description, primarily from the subscriber’s and service providers’ points of view, and does not deal with the details of the human interface itself.
This TS includes information applicable to network operators, service providers and terminal, switch and database manufacturers.
This TS contains the core requirements for a Mobile Station Application Execution Environment (MExE) which are sufficient to provide a complete service.
It is highly desirable however, that technical solutions for a Mobile Station Application Execution Environment (MExE) should be sufficiently flexible to allow for possible enhancements. Additional functionalities not documented in this TS may implement requirements which are considered outside the scope of this TS. This additional functionality may be on a network-wide basis, nation-wide basis or particular to a group of users. Such additional functionality shall not compromise conformance to the core requirements of the service.
Figure 1: Scope of this TS
As indicated in Figure 1, the scope of this TS encompasses the MExE functionality in the MS, interaction with the MExE service environment. The MExE service environment is not necessarily restricted to the PLMN, and nodes providing MExE services (i.e. MExE servers) may also exist outside the PLMN. Aspects of the support provided by MExE servers within the MExE service environment (such as charging aspects, security level classification etc.) are covered by this specification, but not the MExE servers themselves.
MExE requirements are considered to be applicable to both GSM and UMTS systems.
|
02.60
|
General Packet Radio Service Stage 1 Description
|
TS
|
8.1.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/02_series/02.60/0260-810.zip
|
This ETSI Technical Specification defines the stage one description of the General Packet Radio Service (GPRS) on Global System for Mobile communications (GSM) networks. Stage one is an overall service description, primarily from the service subscriber's and user's points of view, but does not deal with the details of the human interface itself. This TS includes information applicable to network operators, service providers and terminal, switch and data base manufacturers.
This TS contains the core requirements for the GPRS and EGPRS on GSM, which are sufficient to provide a complete service.
This TS also documents some additional requirements which may be implemented (but do not have to be implemented).
In addition, additional functionality's not documented in this TS may be implemented. The requirements of which are considered outside the scope of this TS and consequently outside the scope of the corresponding stage 2 and stage 3 TSs. This additional functionality may be on a network-wide basis, or particular to one or a group of users. Such additional functionality shall not compromise conformance to the core requirements of the service.
The interface between the Mobile Station (MS) and any external applications are outside the scope of this TS.
Charging principles are outside the scope of this TS, unless specific service requirements are stated. These requirements deal with the allocation of certain call charges to particular users.
A later phase of GPRS may include interworking with circuit switched networks (e.g. PSTN, ISDN) and may emulate certain circuit switched services. These aspects are outside the scope of this version of this TS.
|
02.78
|
Customized Applications for Mobile network Enhanced Logic (CAMEL); Service definition (Stage 1)
|
TS
|
8.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/02_series/02.78/0278-800.zip
|
This standard specifies the stage 1 description for CAMEL feature (Customised Applications for Mobile network Enhanced Logic) which provides the mechanisms to support services consistently independently of the serving network. The CAMEL features shall facilitate service control of operator specific services external from the serving PLMN. The CAMEL feature is a network feature and not a supplementary service. It is a tool to help the network operator to provide the subscribers with the operator specific services even when roaming outside the HPLMN.
CAMEL is developed in phases. The following phases exist:
- CAMEL phase 1. This is the default phase in this specification. Text that are only applicable to phase 1 are characterised with the formal designator - $(CAMEL1$)
- CAMEL phase 2. It is characterised where necessary with the formal designation - $(CAMEL2$) and sometimes with an indication of CAMEL phase 2. - $(CAMEL2$)
- CAMEL phase 3. It is characterised where necessary with the formal designation - $(CAMEL3$) and sometimes with an indication of CAMEL phase 2. - $(CAMEL3$)
The CAMEL feature is applicable
- to mobile originated and mobile terminated call related activities;
- as a CAMEL phase 2 function, to supplementary service invocations - $(CAMEL2$);
- as a CAMEL Phase 3 function, to SMS MO, to GPRS sessions, to the control of HLR subscriber data, to control different call party connections, to the control of network signalling load and, - $(CAMEL3$);
- as a CAMEL Phase 3 function, to CSE created calls - $(CAMEL3$).
The mechanism described addresses especially the need for information exchange among the VPLMN, HPLMN and the CAMEL Service Environment (CSE) for support of such operator specific services. Any user procedures for operator specific services are outside the scope of this standard.
This specification describes the interactions between the functions of the VPLMN, HPLMN, IPLMN and the CSE.
The second phase of CAMEL enhance the capabilities of phase 1 and are included in this standard. Following capabilities are added:
- Additional event detection points.
- Interaction between a user and service using announcements, voice prompting and information collection via in band interaction or USSD interaction.
- Control of call duration and transfer of Advice of Charge Information to the mobile station.
- The CSE can be informed about the invocation of GSM supplementary services (ECT, CD, MPTY).
- For easy postprocessing, charging information from a serving node can be integrated in normal call records.
The third phase of CAMEL enhances the capabilities of phase 2. Following capabilities are added :
- Capabilities for enhanced handling of call party connections, together with the ability to handle more than 2 parties in a call
- Support of facilities to avoid overload situations.
- Capabilities to support Dialled Services.
- Capabilities to handle mobility events, such as (Not-)reachability and roaming.
- Control of GPRS sessions.
- Control of mobile originating SMS.
- Support of SoLSA. Support of Localised Service Area interworking is an optional feature. The support for interworking with mobile terminating calls is a requirement, however the specific details of how this will be realised is for further study - $(CAMEL3$)
Detailed information can be found in the respective sections.
|
02.82
|
Call Forwarding (CF) Supplementary Services; Stage 1
|
TS
|
8.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/02_series/02.82/0282-800.zip
| |
02.90
|
Unstructured Supplementary Service Data (USSD); Stage 1
|
TS
|
8.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/02_series/02.90/0290-800.zip
| |
02.94
|
Follow Me Service description; Stage 1
|
TS
|
8.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/02_series/02.94/0294-800.zip
|
The present document specifies the stage 1 description for the Follow Me feature.
The Follow Me feature enables a mobile subscriber A to manipulate the Follow Me data of a party B in such a way that - under certain conditions - subsequent calls directed to party B will be forwarded to subscriber A.
The feature is described from the service subscriber's and user's point of view, in particular:
‑ the procedure for normal operation with successful outcome;
‑ the action to be taken in exceptional circumstances;
‑ the interaction with other GSM services and features.
This TS does not deal with the Man‑Machine Interface (MMI) requirements, but makes reference to the appropriate specifications.
Any interaction with other services and/or networks not dealt with in this specification are outside the scope of this TS.
|
03.01
|
Network Functions
|
TS
|
8.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/03_series/03.01/0301-800.zip
|
The present document defines network functions which are necessary to support services and facilities provided by PLMNs. A summary of the network functions is given in Table 1, where also an indication is given whether the network must support the function. The table also indicates whether or not a function requires internetworking signalling between PLMNs (i.e. use of Mobile Application Part, Technical Specification GSM 09.02).
All functions require signalling on the radio path as specified in Technical Specification GSM 04.08.
|
03.31
|
Fraud Information Gathering System (FIGS); Service description; Stage 2
|
TS
|
8.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/03_series/03.31/0331-800.zip
| |
03.35
|
Immediate Service Termination (IST); Stage 2
|
TS
|
8.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/03_series/03.35/0335-810.zip
|
This GSM Technical Specification specifies the stage 2 description of the Immediate Service Termination (IST) service which provides the means for the HPLMN to terminate all the activities of an HPLMN subscriber in a VPLMN.
Two implementations of IST are described: an implementation based on CAMEL, and an implementation based on a new MAP command.
|
03.43
|
Support of Videotex
|
TR
|
8.0.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/03_series/03.43/0343-800.zip
|
The present document describes the support of Videotex service within the GSM PLMN network, taking into account the service definition as per CCITT Recommendation F.300 and Bearer Services specified in GSM 02.02 for a GSM PLMN.
|
03.44
|
Support of Teletex in a GSM Public Land Mobile Network (PLMN)
|
TR
|
8.0.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/03_series/03.44/0344-800.zip
|
The present document describes the support of the teletex service by a GSM Public Land Mobile Network (PLMN).
|
03.47
|
Example Protocol Stacks for Interconnecting Service Centre(s) (SC) and Mobile Services Switching Centre(s) (MSC)
|
TR
|
8.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/03_series/03.47/0347-800.zip
|
No mandatory protocol between the Service Centre (SC) and the Mobile Switching Centre (MSC) below the transfer layer is specified by GSM; this is a matter of agreement between SC and PLMN operators.
The present document specifies three approaches to the specification of protocol stacks of communication protocols for the purpose of relaying short messages and alerts between Short Message Service Centres and Gateway/Interworking MSCs (GMSC) for the Short Message Service (SMS). One approach is based upon use of the complete OSI reference model (see X.200), another approach is based upon the use of only the lower three OSI layers, and another approach is based upon the use of CCITT Signalling System No. 7 (see Q.700).
Alternative protocol stacks are specified via ASN.1 encoding rules (see X.208 and X.209). These alternative protocol stacks are examples for the implementation of the Short Message Relay Layer (SM‑RL). The requirements placed upon the Short Message Relay Layer are briefly described in clause 9 of GSM 03.40.
Specifications are based upon individual contributions. Any judgement concerning functionality, completeness and advantages/disadvantages of implementation is intentionally omitted.
|
03.49
|
Example protocol stacks for interconnecting Cell Broadcast Centre (CBC) and Base Station Controler (BSC)
|
TR
|
8.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/03_series/03.49/0349-800.zip
|
No mandatory protocol between the Cell Broadcast Centre (CBC) and the Base Station Controller (BSC) is specified by GSM; this is a matter of agreement between CBC and PLMN operators.
The present document specifies three alternative approaches to the specification of protocol stacks of communication protocols for the purpose of fulfilling the service requirements of the primitives specified for the CBC - BSC interface in GSM 03.41.
One approach is based upon the use of the complete OSI reference model (see X.200), another approach is based upon the use of only the lower 3 OSI layers, and another approach is based upon the use of CCITT Signalling System No. 7 (see Q.700).
Specifications are based upon individual contributions. Any judgement concerning functionality, completeness and advantages/disadvantages of implementation is intentionally omitted.
|
03.56
|
GSM Cordless Telephony System (CTS), Phase 1; CTS Architecture Description; Stage 2
|
TS
|
8.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/03_series/03.56/0356-800.zip
|
The present document defines the stage 2 description for the Cordless Telephony System (CTS) based on GSM radio. As the second stage of a three-level structure, it is derived from the stage 1 service description.
As mentioned already in the stage 1 description, a phased approach is indispensable to have an early first specification ready for market needs. The first phase focuses on the requirements necessary to elaborate the radio interface and the security aspects for an application supporting the speech tele-service (including DTMF support) in a residential single cell environment.
The standardisation of the physical layers of the GSM-CTS fixed network interface is not in the scope of the present document.
|
03.63
|
Packet Data on Signalling channels service (PDS) Service description, Stage 2
|
TS
|
8.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/03_series/03.63/0363-800.zip
| |
03.82
|
Call Forwarding (CF) Supplementary Services; Stage 2
|
TS
|
8.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/03_series/03.82/0382-800.zip
| |
04.22
|
Radio Link Protocol (RLP) for data and telematic services on the Mobile Station - Base Station System (MS - BSS) interface and the Base Station System - Mobile-services Switching Centre (BSS - MSC) interface
|
TS
|
8.0.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/04_series/04.22/0422-800.zip
| |
04.63
|
Packet Data on Signalling channels Service (PDS) Service Description, Stage 3
|
TS
|
8.0.1
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/04_series/04.63/0463-801.zip
|
The present document specifies the protocols for connection management of packet data on signalling channels which is applied on the air interface, the PDSS1 protocol and the PDSS2 protocol.
|
07.01
|
General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS)
|
TS
|
8.0.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/07_series/07.01/0701-800.zip
|
This TS is based on the principles of terminal adaptor functions presented in the CCITT I-series of recommendations (I.460 - I.463).
The GSM PLMN supports a wide range of voice and non-voice services in the same network. In order to enable non-voice traffic in the GSM PLMN there is a need to connect various kinds of terminal equipments to the Mobile Termination (MT). The target of this ETS is to outline the functions needed for the terminal adaptation.
In the GSM 02.02 (ETS 300 904) the bearer services are described. The general network configuration is described in GSM 03.02 and the GSM PLMN access reference configuration is defined in GSM 04.02. The various connection types used in the GSM PLMN are presented in GSM 03.10. Terminology used in this ETS is presented in GSM 01.04 (ETR 350). For support of data services between GSM PLMN and other networks see GSM 09-series of Specifications.
|
07.02
|
Terminal Adaptation Functions (TAF) for Services Using Asynchronous Bearer Capabilities
|
TS
|
8.0.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/07_series/07.02/0702-800.zip
| |
07.03
|
Terminal Adaptation Functions (TAF) for Services Using Synchronous Bearer Capabilities
|
TS
|
8.0.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/07_series/07.03/0703-800.zip
|
This Technical Specification (TS) defines Terminal Adaptation Functions (TAF) which are integrated in a Mobile Termination (MT) and which enable the attachment of Synchronous Terminals to an MT (see GSM 04.02 [4]). The general aspects of Terminal Adaptation Functions are contained in specification GSM 07.01 [8]. This ETS covers support of synchronous data services (see GSM 02.02 [2]) for the following interfaces and procedures:
‑ V.22 DTE/DCE Interface
‑ V.22 bis DTE/DCE Interface
‑ V.26 ter DTE/DCE Interface
‑ V.32 DTE/DCE Interface
‑ X.21 DTE/DCE Interface
‑ X.21 bis DTE/DCE Interface
‑ X.25 Procedure
‑ X.32 Procedure
‑ V.25 bis Procedure
‑ I.420 Interface (S)
LAPB is the only synchronous non‑transparent protocol which is considered here.
|
07.08
|
GSM Application Programming Interface
|
TS
|
8.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/07_series/07.08/0708-800.zip
|
This European Telecommunication Standard (ETS) defines the GSM Application Programming Interface (GSM‑API) in two parts.
The first part describes, how compatibility to existing application interface ETS 300 838 [14] is covered for the GSM network. So existing PCI applications are able to be used in a GSM environment. For these applications the necessary mapping and local knowledge between application interface and network is described. The only modifications needed in ETS 300 838 [14] to fulfil this requirements are covered by changes of the parameter description. These changes of parameters are defined in clauses 4 and 5 of this ETS.
An application compliant with this ETS shall not imply compliance with ETS 300 838 (HPCI).
Clause 4 is meant to replace subclause 5.7 message parameters of ETS 300 838 [14]. which defines the parameters of the profile A of the HPCI.
NOTE 1: Clause 4is for further study.
Clause 5 replaces subclause 6.8 parameter description of ETS 300 838, which defines the parameters of the profile B of the HPCI.
The second part defines GSM specific features. New GSM‑API applications need extensions to ETS 300 838 [14] which are defined in section 6 and 7of this ETS.
These sections are meant as an addition to ETS 300 838 [14]. They do not replace any clause of ETS 300 838 [14].
Clause 6 defines the extensions according to the profile A of ETS 300 838 [14].
NOTE 2: Clause 6 is for further study.
Clause 7 defines the extensions according to the profile B of ETS 300 838 [14] (bit compatible to COMMON ISDN API).
The messages and the operating system dependent part of ETS 300 838 [14] will not be changed for GSM‑API.
|
09.07
|
General Requirements on Interworking between the Public Land Mobile Network (PLMN) and the Intergrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN)
|
TS
|
8.0.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/09_series/09.07/0907-800.zip
|
This TS identifies the Mobile‑services Switching Centre/Interworking Functions (MSC/IWFs) and requirements to support interworking between:
a) PLMN and PSTN
b) PLMN and ISDN
It is not possible to treat ISDN and PSTN as one type of network, even when both ISDN and PSTN subscribers are served by the same exchange because of the limitations of the PSTN subscribers access i.e. analogue connection without D‑channel signalling.
Within this TS, the requirements for voice and non‑voice (data) calls are considered separately.
|
09.14
|
Application of ISDN User Part (ISUP) Version 3 for the Integrated Services Digital Network (ISDN) - Public Land Mobile Network (PLMN) signalling interface; Part 1: Protocol specification
|
TS
|
8.0.0
|
-
|
https://www.3gpp.org/ftp/Specs/archive/09_series/09.14/0914-800.zip
|
The present document specifies the third version of the Integrated Services Digital Network (ISDN) - Global System for Mobile communications (GSM) Public Land Mobile Network (PLMN) signalling interface. The present document is applicable to the interconnection of PLMN and ISDN.
The ISUP interface defined is the trunk signalling interface between the PLMN and the ISDN. It is assumed that the interface between PLMN and ISDN can occur at any point in a national network, provided that the exchange in the national network has this ISDN-PLMN signalling interface.
This signalling interface is based on ISUP version 3 (as given in EN 300 356-1 [1] to EN 300 356-20 [19]). The functionality in the GSM system is based on GSM Phase 2+ Release 1998.
NOTE 1: Support of new functionality in the GSM system applicable for this interface may be included in subsequent versions of the present document or may be published as a new EN.
Connection types:
The following ISUP version 3 connection types can be supported:
- speech;
- 3,1 kHz audio;
- 64 kbit/s unrestricted;
- 64 kbit/s unrestricted preferred;
- 2 64 kbit/s unrestricted;
- 384 kbit/s unrestricted;
- 1 536 kbit/s unrestricted;
- 1 920 kbit/s unrestricted.
NOTE 2: 2 64 kbit/s, 384 kbit/s, 1 536 kbit/s, 1 920 kbit/s unrestricted and 64 kbit/s unrestricted preferred connection types are not supported by the GSM access, however the connection types may be used in order to support other access methods via the GSM network.
Supplementary services:
The following ISUP version 3 supplementary services can be supported:
- Calling Line Identification Presentation (CLIP)/
Calling Line Identification Restriction (CLIR);
- Connected Line Identification Presentation (COLP)/
Connected Line Identification Restriction (COLR);
- Terminal portability (TP);
- User-to-User Signalling (UUS);
- Closed User Group (CUG);
- Subaddressing (SUB);
- Malicious Call Identification (MCID);
- Conference call, add-on (CONF);
- Explicit Call Transfer (ECT);
- Call Forwarding Unconditional (CFU)/
Call Forwarding on Busy (CFB)/
Call Forwarding on No Reply (CFNR);
- Call Deflection (CD);
- Call Hold (HOLD);
- Call Waiting (CW);
- Completion of Calls to Busy Subscriber (CCBS);
- Completion of Calls on No Reply (CCNR);
- Three party (3PTY).
The support of supplementary services on this interface does not necessarily imply that the supplementary services are supported in one or the other of the networks interconnected.
The Direct Dialling In (DDI) supplementary service and Multiple Subscriber Number (MSN) supplementary service have no impact on this interface.
This interface can be used within national networks, however messages and parameters that are marked for national use in EN 300 356-1 [1] are not described in the present document.
|
09.18
|
General Packet Radio Service (GPRS); Serving GPRS Support Node (SGSN) - Visitors Location Register (VLR); Gs interface layer 3 specification
|
TS
|
8.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/09_series/09.18/0918-800.zip
|
The present document specifies or references procedures used on the Serving GPRS Support Node (SGSN) to Visitors Location Register (VLR) interface for interoperability between GSM circuit switched services and GSM packet data services.
The present document specifies the layer 3 messages and procedures on the Gs interface to allow coordination between databases and to relay certain messages related to GSM circuit switched services over the GPRS subsystem.
The functional split between VLR and SGSN is defined in GSM 03.60. The required procedures between VLR and SGSN are defined in detail in the present document.
|
10.57
|
Project scheduling and open issues: Mobile Station Execution Environment (MExE)
|
TR
|
8.0.0
|
T2
|
https://www.3gpp.org/ftp/Specs/archive/10_series/10.57/1057-800.zip
|
The purpose of this document is to describe the project plan for the Mobile Station Execution Environment (MEXE) work item standardisation.
This document is a ‘living document’ and permanently updated by PT SMG. Proposals for change shall be forwarded to PT SMG, where the latest version can be obtained any time. The MEXE specification rapporteurs should make sure that this document can always reflects the latest status of work.
|
10.76
|
Noise suppression for the AMR codec; Project scheduling and open issues
|
TR
|
1.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/10_series/10.76/1076-100.zip
|
The purpose of this document is to describe the schedule of the standardisation process for the Noise Suppression feature for the Adaptive Multi Rate Codec and to define open issues that are still under discussion. It also lists the new standards and necessary amendments to the GSM/DCS phase 2+ specifications for the technical realisation of the function.
The new standards and Change Requests (CR) necessary for this feature are listed in clause 9.
|
11.10-2
|
Mobile station (MS) conformance specification; Part 2: Protocol Implementation Conformance Statement (PICS) proforma specification
|
TS
|
8.0.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/11_series/11.10-2/1110-2-800.zip
|
The present document provides the Protocol Implementation Conformance Statement (PICS) proforma for Global System for Mobile Stations (MSs), operating in the 900 MHz and 1 800 MHz frequency band (GSM 900 and DCS 1 800) within the European digital cellular telecommunications system (Phase 2), in compliance with the relevant requirements, and in accordance with the relevant guidance given in ISO/IEC 9646‑7 [3] and ETS 300 406 [1].
|
11.10-3
|
Mobile Station (MS) conformance specification; Part 3: Layer3 (L3) Abstract Test Suite (ATS)
|
TS
|
8.0.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/11_series/11.10-3/1110-3-800.zip
|
The present document specifies the Abstract Test Suites (ATS) and partial IXIT proforma for the Network Layer (Layer 3) at the mobile radio interface of the GSM or DCS (Phase 2+) mobile stations (MS) conforming to the ENs for Layer 3, cell selection, Enhanced Full Rate Speech, Multi-band, GSM-R band (R-GSM) and ASCI ( the voice group call service (VGCS), voice broadcast service (VBS), enhanced Multi-Level Precedence and Pre-emption service (eMLPP), User-to-user Signalling (UUS) service and the Follow Me service) for the digital cellular telecommunications systems.
This EN is valid for MS implemented according Phase2 or Phase2+ R96, or R97, or R98, or R99, or R00.
The ISO standards for the methodology of conformance testing and the TTCN language are used as the basis for the test specifications.
|
11.18
|
Specification of the 1.8 Volt Subscriber Identity Module - Mobile Equipment (SIM - ME) Interface
|
TS
|
8.0.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/11_series/11.18/1118-800.zip
|
The present document defines the aspects of the Subscriber Identity Module - Mobile Equipment (SIM - ME) interface which are based on 1.8V technology to be used in the Mobile Station (MS). It specifies the electrical and logical requirements necessary for the operation of the 1.8V SIM - ME interface where it differs from GSM 11.11 [1]. For all aspects of the SIM - ME interface which are not covered by the present document, GSM 11.11 [1] applies.
|
21.810
|
Report on multi-mode UE issues; ongoing work and identified additional work
|
TR
|
3.0.0
|
T2
|
https://www.3gpp.org/ftp/Specs/archive/21_series/21.810/21810-300.zip
|
This 3GPP Technical Report identifies the work done in other working groups within 3GPP and SMG concerning Multi-mode UEs. The report is related to TR 21.910 [38] which identifies multi-mode User Equipments categories and also describes the general principles and procedures for the multi-mode operation standardised in the 3GPP specifications.
The present report describes the status of the work as of February 2000.
|
22.043
|
Support of Localized Service Area (SoLSA); Service description; Stage 1
|
TS
|
3.1.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.043/22043-310.zip
|
This technical specification, specifies a mechanism, which can be used as a platform for providing special tariffs and/or special set of service features for certain subscribers within a regionally restricted area or areas.
The motivation for this concept is to create means for network operators to build new service and tariff packages, which take into account subscriber groups and their needs.
The localised service area is both an optional network feature and an optional UE feature. Usage and implementation of the different SoLSA service features may vary according to operator's service packages.
This feature is not intended to replace the existing method of cell selection, cell indication and handover.
“Support of Localised service area (SoLSA)” is renamed Phase 2+ item “Support of Home Area Priority”
Note: The present document covers description for GERAN support only. UTRAN support will be added in latter releases.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.