|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 23.002 |
sa2 |
|
Network Architecture |
This TS offers an overview of the 3GPP PLMN and its architectures and configuration. The configuration and
the functional entities of the PLMN and the interfaces between them are described on a general level in order to cope
with possible implementations. These descriptions include interfaces between and within the core networks, the access
networks, the user equipment, different service platforms, different domains and subsystems, and functional entities
within domains and subsystems.
This document covers different architectural aspects with varying level of detail. In general, other specifications shall be
referred to for further details; these specifications enable the reader to acquire the full understanding of a system or
service feature.
|
|
|
V3.6 | |
V4.8 | |
V5.12 | |
V6.10 | |
V7.6 | |
V8.6 | |
V9.3 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 23.003 |
ct4 |
|
Numbering, Addressing and Identification |
This TS defines the principal purpose and use of International Mobile station Equipment Identities (IMEI)
within the digital cellular telecommunications system and the 3GPP system.
The present document defines:
|
| a) |
an identification plan for mobile subscribers in the GSM system;
| |
| b) |
principles of assigning telephone and ISDN numbers to MSs in the country of registration of the MS;
| |
| c) |
principles of assigning Mobile Station (MS) roaming numbers to visiting MSs;
| |
| d) |
an identification plan for location areas, routing areas, and base stations in the GSM system;
| |
| e) |
an identification plan for MSCs, SGSNs, GGSNs, and location registers in the GSM system;
| |
| f) |
principles of assigning international mobile equipment identities;
| |
| g) |
principles of assigning zones for regional subscription;
| |
| h) |
an identification plan for groups of subscribers to the Voice Group Call Service (VGCS) and to the Voice
Broadcast Service (VBS); and identification plan for voice group calls and voice broadcast calls; an
identification plan for group call areas;
| |
| i) |
principles for assigning Packet Data Protocol (PDP) addresses to mobile stations;
| |
| j) |
an identification plan for point-to-multipoint data transmission groups;
| |
| k) |
an identification plan for CN domain, RNC and service area in the UTRAN system;
| |
| l) |
an identification plan for mobile subscribers in the WLAN system;
| |
| m) |
addressing and identification for IMS Service Continuity;
| |
| n) |
an identification plan together with principles of assignment and mapping of identities for the Evolved Packet
System.
|
|
|
|
V3.15 | |
V4.9 | |
V5.11 | |
V6.16 | |
V7.9 | |
V8.9 | |
V9.3 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 23.007 |
ct4 |
|
Restoration procedures |
|
The data stored in location registers are automatically updated in normal operation; the main information stored in a
location register defines the location of each mobile station and the subscriber data required to handle traffic for each
mobile subscriber. The loss or corruption of these data will seriously degrade the service offered to mobile subscribers;
it is therefore necessary to define procedures to limit the effects of failure of a location register, and to restore the
location register data automatically. The present document defines the necessary procedures.
|
|
|
V3.6 | |
V4.2 | |
V5.1 | |
V6.2 | |
V7.0 | |
V8.8 | |
V9.4 | |
V10.0 | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 23.008 |
ct4 |
|
Organization of Subscriber Data |
This TS provides details concerning information to be stored in home subscriber servers, visitor location
registers, GPRS Support Nodes and Call Session Control Function (CSCF) concerning mobile subscriber.
Clause 2 contains all details concerning the definition of the parameters, often given by reference to other
specifications, and where the parameter is to be stored.
Table 1 in clause 3 gives a summary overview and clause 4 identifies the reference information required for accessing
the information.
|
|
|
V3.8 | |
V4.3 | |
V5.14 | |
V6.15 | |
V7.11 | |
V8.10 | |
V9.3 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 23.009 |
ct1 |
|
Handover procedures |
|
This TS contains a detailed description of the handover procedures to be used in PLMNs. The purpose of
the handover procedures, as described in the present document, are to ensure that the connection to the Mobile Station
(MS) or User Equipment (UE) is maintained as it moves from one cell or radio network to another. The document
defines the circuit switched handover functionality based on the service requirements in 3GPP TS 22.129. For the
circuit switched handover functionality related to SRVCC, it is based on the service requirements in
TS 23.216.
|
|
|
V3.14 | |
V4.9 | |
V5.12 | |
V6.5 | |
V7.1 | |
V8.2 | |
V9.1 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 23.011 |
ct4 |
|
Technical realization of Supplementary Services |
This TS describes the general aspects on how supplementary services in the 3GPP system are realised
from a technical point of view.
Description of technical realisation for specific supplementary services can be found in 3GPP TS 23.072, 3GPP TS 23.08x and
3GPP TS 23.09x-series technical specifications.
All supplementary services may require signalling on the radio path. Signalling procedures and messages used are
defined in the 3GPP TS 24.072, 3GPP TS 24.08x and 3GPP TS 24.09x-series of technical specifications.
For some supplementary services information needs to be transferred between the Home Location Register (HLR), the
Visitor Location Register (VLR), the Mobile services Switching Centre (MSC) and the Serving GPRS Support Node
(SGSN). Signalling procedures for such information transfer are defined in 3GPP TS 29.002.
Definitions and descriptions of supplementary services are given in the 3GPP TS 22.072, 3GPP TS 22.08x and 3GPP TS 22.09x-series of
technical specifications.
Definitions are given in 3GPP TS 22.004.
|
|
|
V3.1 | |
V4.0 | |
V5.0 | |
V6.0 | |
V7.0 | |
V8.0 | |
V9.0 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 23.012 |
ct4 |
|
Location management procedures |
This TS describes the location management procedures for the circuit switched domain, with respect to
the application level functional behaviour. This is to be distinguished from the corresponding protocol handling
behaviour, which is specified in 3GPP TS 29.002. The following location management procedures are included:
|
| - |
location updating;
| |
| - |
location cancellation;
| |
| - |
MS purging;
| |
| - |
IMSI attach/detach.
|
The procedures in the Mobile Station (MS) are described in TS 03.22. The procedures between MSC, VLR and HLR
utilise the Mobile Application Part (MAP) and details concerning the protocol handling are contained in 3GPP TS 29.002..
The present document excludes location management procedures for the packet switched domain, which are covered in
3GPP TS 23.060.
The descriptions herein depict a logical separation between the MSC and VLR. This logical separation, as well as the
messages transferred between the two logical entities are the basis of a model used to define the externally visible
behaviour of the MSC/VLR, which a may be a single physical entity. They do not impose any requirement except the
definition of the externally visible behaviour.
|
|
|
V3.3 | |
V4.0 | |
V5.2 | |
V6.4 | |
V7.3 | |
V8.2 | |
V9.0 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
V3.2 | |
V4.1 | |
V5.1 | |
V6.0 | |
V7.0 | |
V8.0 | |
V9.0 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 23.015 |
ct4 |
|
Technical realization of Operator Determined Barring (ODB) |
The network feature Operator Determined Barring (ODB) allows a network operator or service provider to regulate
access by subscribers to services (Circuit/Packet Oriented and Interworking WLAN), by the barring of certain
categories of incoming or outgoing calls/ Packet Oriented Services or of roaming. Operator Determined Barring applies
to all bearer services and teleservices except the Emergency Call teleservice; the teleservice Short Message Point-to-
Point is therefore subject to Operator Determined Barring in the same way as circuit-switched calls.
The application of specific categories of Operator Determined Barring to a subscription is controlled by the network
operator or service provider, using administrative interaction at the HLR; this interface is not standardised.
|
|
|
V3.1 | |
V4.0 | |
V5.0 | |
V6.0 | |
V7.0 | |
V8.1 | |
V9.0 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 23.016 |
ct4 |
|
Subscriber data management - Stage 2 |
This specification gives the stage 2 description of the subscriber data management handling between:
|
| - |
the Home Location Register (HLR) and the Visitor Location Register (VLR);
| |
| - |
the Home Location Register (HLR) and the Serving GPRS Support Node (SGSN).
|
A number of procedures require updating of subscriber information:
|
| - |
location updating;
| |
| - |
restoration;
| |
| - |
modification of data by the operator;
| |
| - |
modification of data by the subscriber via the Mobile Station (MS).
|
Updating of subscriber information from HLR to SGSN is required in the following situations:
|
| - |
GPRS location updating;
| |
| - |
modification of data by the operator.
|
Only the rules for the updating of subscriber data from the HLR to the VLR and from the HLR to the SGSN are
described in this specification. Public Land Mobile Network (PLMN) specific and Unstructured Supplementary Service
Data (USSD) subscriber data are out of scope of this specification. The GPRS context update from the SGSN to the
GGSN is out of scope of this specification.
|
|
|
V3.10 | |
V4.4 | |
V5.3 | |
V6.1 | |
V7.0 | |
V8.1 | |
V9.1 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 23.018 |
ct4 |
|
Basic Call Handling - Technical Realization |
This TS
specifies the technical realization of the handling of calls originated by a UMTS or GSM mobile subscriber and calls directed to a UMTS or GSM mobile subscriber, up to the point where the call is established. Normal release of the call after establishment is also specified. Trunk Originated call is also modelled.
In the present document, the term MS is used to denote a UMTS UE or GSM MS, as appropriate.
The details of the effects of UMTS or GSM supplementary services on the handling of a call are described in the relevant 3GPP TS 23.07x, 3GPP TS 23.08x and 3GPP TS 23.09x series of specifications.
The specification of the handling of a request from the HLR for subscriber information is not part of basic call handling, but is required for both CAMEL
(3GPP TS 23.078) and optimal routeing
(3GPP TS 23.079). The use of the Provide Subscriber Information message flow is shown in 3GPP TS 23.078 and 3GPP TS 23.079.
The logical separation of the MSC and VLR (shown in clauses 4, 5 and 7), and the messages transferred between them (described in clause 8) are the basis of a model used to define the externally visible behaviour of the MSC/VLR, which is a single physical entity. They do not impose any requirement except the definition of the externally visible behaviour.
|
|
|
V3.12 | |
V4.3 | |
V5.10 | |
V6.6 | |
V7.7 | |
V8.2 | |
V9.1 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 23.031 |
sa3 |
|
Fraud Information Gathering System (FIGS) - Service description - Stage 2 |
This TS specifies the stage 2 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.
Three levels of FIGS service are defined, levels 1 to 3.
Level 1 will use the facilities provided by Transferred Account Procedure (TAP).
Levels 2 and 3 will use facilities provided by Customised Applications for Mobile network Enhanced Logic (CAMEL),
in particular, the information flows between the GSM Service Switching Function (gsmSSF) and GSM Service Control
Function (gsmSCF). Phase 1 and Phase 2 CAMEL facilities will be used.
Connection-orientated services only are covered.
|
|
|
V3.0 | |
V4.0 | |
V5.0 | |
V6.0 | |
V7.0 | |
V8.0 | |
V9.0 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 23.032 |
sa2 |
|
Universal Geographical Area Description (GAD) |
This TS defines an intermediate universal Geographical Area Description which subscriber applications,
GSM or UMTS services can use and the network can convert into an equivalent radio coverage map.
For GSM or UMTS services which involve the use of an "area", it can be assumed that in the majority of cases the
Service Requester will be forbidden access to data on the radio coverage map of a particular PLMN and that the Service
Requester will not have direct access to network entities (e.g. BSC/BTS or RNC/Node B).
The interpretation by the PLMN operator of the geographical area in terms of cells actually used, cells that are partly
within the given area and all other technical and quality of service aspects are out of the scope of the present document.
This specification also provides a description of velocity that may be associated with a universal Geographical Area
Description when both are applied to a common entity at a common time.
|
|
|
V3.2 | |
V4.1 | |
V5.0 | |
V6.0 | |
V7.0 | |
V8.0 | |
V9.0 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 23.034 |
ct1 |
|
High Speed Circuit Switched Data (HSCSD) - Stage 2 |
This TS contains the stage 2 service description for a High Speed Circuit Switched Data (HSCSD) on
GSM/GERAN in A/Gb mode and Iu mode. HSCSD utilizes the multislot mechanism, i.e. using multiple traffic
channels (/bearers) for the communication.
Additionally, the present document specifies some HSCSD related requirements for multi system mobile stations
operating in UTRAN Iu mode. In UTRAN Iu mode one bearer can provide all needed data rates, and the multislot
mechanism is therefore not needed. However, for inter-system handover to GERAN, certain information has to be
provided by the mobile station during the service negotiation. The UTRAN Iu mode aspects concerning HSCSD are
described exclusively in clause 4.2.
Stage 2 identifies the functional capabilities and information flows needed to support the service as described in
3GPP TS 22.034. Furthermore, it identifies various possible physical locations for the functional capabilities. The
output of Stage 2, which is signalling system independent, is used as an input to Stage 3, the design of signalling system
and switching Recommendations.
|
|
|
V3.3 | |
V4.0 | |
V5.2 | |
V6.0 | |
V7.0 | |
V8.0 | |
V9.0 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 23.035 |
sa3 |
|
Immediate Service Termination (IST) |
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 message.
|
|
|
V3.1 | |
V4.1 | |
V5.1 | |
V6.0 | |
V7.0 | |
V8.0 | |
V9.0 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 23.038 |
ct1 |
|
Alphabets and language-specific information |
This TS defines the character sets, languages and message handling requirements for SMS, CBS and
USSD and may additionally be used for Man Machine Interface (MMI) (3GPP TS 22.030).
The specification for the Data Circuit terminating Equipment/Data Terminal Equipment (DCE/DTE) interface
(3GPP TS 27.005)
will also use the codes specified herein for the transfer of SMS data to an external terminal.
|
|
|
V3.3 | |
V4.5 | |
V5.1 | |
V6.1 | |
V7.0 | |
V8.3 | |
V9.1 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 23.040 |
ct1 |
|
Technical Realization of the Short Message Service (SMS) |
This TS describes the Short Message Service (SMS) for GSM/UMTS networks. It defines:
|
| - |
the services and service elements;
| |
| - |
the network architecture;
| |
| - |
the Service Centre functionality;
| |
| - |
the SMS Router functionality;
| |
| - |
the MSC functionality (with regard to the SMS);
| |
| - |
the SGSN functionality (with regard to the SMS);
| |
| - |
the routing requirements;
| |
| - |
the protocols and protocol layering;
|
for the Mobile Originated and Mobile Terminated SMS Teleservices, as specified in 3GPP TS 22.003 and 3GPP TS 22.105.
|
|
|
V3.11 | |
V4.10 | |
V5.9 | |
V6.9 | |
V7.2 | |
V8.6 | |
V9.2 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 23.041 |
ct1 |
|
Technical realization of Cell Broadcast Service (CBS) |
This TS describes the Cell Broadcast short message service (CBS) for GSM and UMTS.
For GSM it defines the primitives over the Cell Broadcast Centre - Base Station System (CBC-BSS) interface and the
message formats over the Base Station System - Mobile Station (BSS-MS) interface for Teleservice 23 as specified in
3GPP TS 22.003.
For UMTS it defines the interface requirements for the Cell Broadcast Center - UMTS Radio Network System (RNS)
interface and the radio interface requirements for UMTS Radio Acces Networks to support CBS as specified in
3GPP TS 22.003.
|
|
|
V3.5 | |
V4.4 | |
V5.2 | |
V6.2 | |
V7.0 | |
V8.6 | |
V9.4 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
V3.1 | |
V4.0 | |
V5.0 | |
V6.0 | |
V7.0 | |
V8.0 | |
V9.0 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 23.048 |
ct6 |
|
Security mechanisms for the (U)SIM application toolkit - Stage 2 |
This TS 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 TS 51.011 and allows remote management of files on the UICC in
conjunction with SMS and the Data Download to UICC feature of 3GPP TS 31.111.
For UICCs based on TS 43.019, 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. For UICCs 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 3G or GSM PLMN and
an entity in the UICC.
Secured Packets contain application messages to which certain mechanisms according to 3GPP TS 22.048 have been
applied. Application messages are commands or data exchanged between an application resident in or behind the 3G or
GSM PLMN and on the UICC. The Sending/Receiving Entity in the 3G or GSM PLMN and the UICC are responsible
for applying the security mechanisms to the application messages and thus turning them into Secured Packets.
|
|
|
- | |
V4.5 | |
V5.9 | |
- | |
- | |
- | |
- | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
- | |
V4.0 | |
V5.0 | |
V6.0 | |
V7.0 | |
V8.0 | |
V9.0 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 23.057 |
sa2 |
|
Mobile Execution Environment (MExE) - Functional description - Stage 2 |
This TS defines the stage 2 and stage 3 description of the Mobile Execution Environment (MExE).
Stage 2 identifies the functional capabilities and information flows needed to support the service described in stage 1.
The present document includes information applicable to network operators, service providers and terminal, switch and
database manufacturers.
The present document contains the core functions for a Mobile Execution Environment (MExE) which are sufficient to
provide a complete service.
MExE uses a number of technologies to realise the requirements of the stage 1 description (3GPP TS 22.057). The
present document describes how the service requirements are realised with the selected technologies. The TS is devised
into clauses each covering the aspects relating to particular MExE technologies, it is intended that this specification will
evolve along with the MExE technologies. A generic clause of the specification covers areas of MExE common to all
technologies.
|
|
|
V3.4 | |
V4.5 | |
V5.1 | |
V6.2 | |
V7.0 | |
V8.0 | |
V9.0 | |
- | |
- | |
- |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|