3GPP IMS and UMTS Specifications -- 23 Series:
Technical Realization - Stage 2
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 23.002 |
SA2 |
|
Network Architecture |
This TS offers an overview of the 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.
|
| - |
Clause 4a7 contains the description of the IMS entities of the PLMN.
| |
| - |
Clause 6a7 describes the IMS specific interfaces and reference points.
|
|
|
|
| |
| Up |
Rapporteur: Alexander Milinski |
|
|
|
|
|
|
|
|
| | |
|
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.
|
| - |
Clause 13 describes the format of the parameters needed to access the IP multimedia core network subsystem.
|
|
|
|
| |
| Up |
Rapporteur: Nick Russell |
|
|
|
|
|
|
|
|
| | |
|
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.
|
|
|
| |
| Up |
Rapporteur: Peter Schmitt |
|
|
|
|
|
|
|
|
| | |
|
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.
|
|
|
| |
| Up |
Rapporteur: Nick Russell |
|
|
|
|
|
|
|
|
| | |
|
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.
|
|
|
| |
| Up |
Rapporteur: Ian Harris |
|
|
|
|
|
|
|
|
|
|
| |
| Up |
Rapporteur: Apostolis Salkintzis |
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 23.078 |
CT4 |
|
CAMEL Phase X - Stage 2 |
This Technical Specifications specify the stage 2 description for the third and fourth phases (see
3GPP TS 22.078)
of the Customized Applications for Mobile network Enhanced Logic (CAMEL) feature which provides
the mechanisms to support services of operators which are not covered by standardized services
even when roaming outside the Home PLMN.
|
|
In the third phase (Release 3 and 4) the CAMEL feature supports:
|
|
| - |
Mobile originated and forwarded calls;
| |
| - |
Mobile terminating calls;
| |
| - |
Any time interrogation;
| |
| - |
Active location information retrieval;
| |
| - |
Suppression of announcements;
| |
| - |
Announcements, in band user interaction;
| |
| - |
Charging features;
| |
| - |
Supplementary service invocation notifications;
| |
| - |
USSD interaction with the gsmSCF;
| |
| - |
Mobility Management event notifications;
| |
| - |
Change of Calling Line Identification Presentation Indicator for an MO call to restricted;
| |
| - |
SoLSA;
| |
| - |
Serving network dialled services;
| |
| - |
MO SMS;
| |
| - |
GPRS data transmission;
| |
| - |
Mobility management;
| |
| - |
Notification to CSE of change of subscriber data;
| |
| - |
Any Time Modification;
| |
| - |
Any Time Interrogation of subscription Information;
| |
| - |
T-BCSM in the VMSC and terminating AoC;
| |
| - |
Interworking with Location Services;
| |
| - |
Multiple Subscriber Profile;
| |
| - |
Active Location Retrieval;
| |
| - |
Call Gapping.
|
A functional entity (VMSC, GMSC or SGSN) may support the complete CAMEL phase 4 functionality or, as a network option, it may support the complete CAMEL phase 3 functionality and a partial implementation of CAMEL phase 4.
The fourth phase of the CAMEL feature supports, in addition to the third phase of the CAMEL:
|
| - |
Interactions with Optimal Routing;
| |
| - |
Call Party Handling;
| |
| - |
DTMF Mid call procedure for Mobile Originated and Mobile Terminating calls;
| |
| - |
Provision of location information of called subscriber;
| |
| - |
Provide location information during ongoing call;
| |
| - |
CAMEL control over MT SMS;
| |
| - |
Notification of GPRS mobility management to CSE;
| |
| - |
Inclusion of ODB data in Any Time Modification;
| |
| - |
Enhancement of Any Time Interrogation and Provide Subscriber Information for PS Domain;
| |
| - |
Mobile Number Portability database interrogation.
|
|
| - |
Criteria for the provision of location information during ongoing call;
| |
| - |
Enhanced Dialled Services;
| |
| - |
Enhancement to Establish Temporary Connection;
|
|
| - |
CAMEL control of trunk originated calls.
|
CAMEL applicability to IP-based multimedia services is introduced in the fourth phase of the CAMEL.
It is specified in
3GPP TS 23.278.
|
|
|
| |
| Up |
Rapporteur: Christian Homann |
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 23.107 |
SA2 |
|
Quality of Service (QoS)
Concept and Architecture |
|
This TS provides the framework for Quality of Service within the 3GPP system.
The main purpose is to specify the list of attributes applicable to the UMTS Bearer Service
and the Radio Access Bearer Service, as well as describe the Quality of Service architecture
to be used in the 3GPP system.
|
|
|
| |
| Up |
Rapporteur: Janne Rinne |
|
|
|
|
|
|
|
|
|
|
| |
| Up |
Rapporteur: Krister Boman |
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 23.140 |
CT |
|
Multimedia Messaging Service (MMS) - Functional description - Stage 2 |
This TS
defines the stage 2 and stage 3 description of the non-realtime Multimedia Messaging Service, MMS. 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 non realtime Multimedia Messaging Service, MMS, which are sufficient to provide a basic service.
MMS uses a number of technologies to realise the requirements of the stage 1 description
(3GPP TS 22.140). The present document describes how the service requirements are realised with the selected technologies. As far as possible existing protocols (e.g. WAP, SMTP, ESMTP as transfer protocols; lower layers to provide push, pull, notification) and existing message formats (e.g. SMIL, MIME) shall be used for the realisation of the Multimedia Messaging Service.
|
|
|
| |
| Up |
Rapporteur: Matthias Roebke |
|
|
|
|
|
|
|
|
|
|
| |
| Up |
Rapporteur: Balazs Bertenyi |
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 23.167 |
SA2 |
|
IP Multimedia Subsystem (IMS) Emergency Sessions |
|
This TS defines the stage-2 service description for emergency services in the IP Multimedia Core Network
Subsystem (IMS), including the elements necessary to support IP Multimedia (IM) emergency services.
This document covers also the Access Network aspects that are crucial for the provisioning of
IMS emergency services.
|
|
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 23.198 |
CT5 |
|
Open Service Access (OSA) - Stage 2 |
The Open Service Access (OSA) defines an architecture that enables service application developers to make
use of network functionality through open standardized interface, i.e. the OSA APIs and Parlay X Web Services.
The network functionality is describes as Service Capability Features (SCFs) or Services.
The OSA Framework is a general component in support of Services (Service Capabilities) and Applications.
The concepts and the functional architecture for the OSA are contained in the present document.
The requirements for OSA are contained in
3GPP TS 22.127.
NOTE: The terms "Service" and "Service Capability Feature" are used as alternatives for the same concept
in the present document. In the OSA Application Programming Interface (API) itself, the SCFs as
identified in the 3GPP requirements and architecture are reflected as "service",
in terms like service instance lifecycle manager, service Discovery.
|
|
|
| |
| Up |
Rapporteur: Salim Mounir Alaoui |
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 23.203 |
SA2 |
|
Policy and Charging Control Architecture |
This TS specifies the overall stage 2 level functionality for Policy and Charging Control that encompasses the following high level functions for IP-CANs (e.g. GPRS, I-WLAN, Fixed Broadband, etc.):
|
| - |
Flow Based Charging, including charging control and online credit control;
| |
| - |
Policy control (e.g. gating control, QoS control, etc.).
|
|
|
|
| |
| Up |
Rapporteur: Balazs Bertenyi |
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 23.204 |
SA2 |
|
Support of SMS over generic 3GPP IP access - Stage 2 |
This TS specifies the new capabilities and enhancements needed to support SMS over a generic IP Connectivity Access Network (IP-CAN) using IMS capabilities. These include (but are not limited to):
|
| - |
Enhancements to the HSS;
| |
| - |
Communication between the SMS-GMSC/SMS-IWMSC and the HSS;
| |
| - |
Authentication of service usage and registration;
| |
| - |
Transfer of Mobile Terminated SMS, Mobile Originated SMS, and Delivery reports;
| |
| - |
Mechanisms to handle SMS when there is more than one IP connection active with the mobile, etc.
|
|
|
|
| |
| Up |
Rapporteur: Wenlin Zhang |
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 23.205 |
CT4 |
|
Bearer-Independent Circuit-Switched Core Network -
Stage 2 |
|
This TS defines the stage 2 description for the bearer independent CS core network. The stage 2 shall cover the information flow between the GMSC server, MSC server and media gateways. Note that nothing in the present document shall preclude an implementation of a combined MSC Server and MGW.
The present document shall show the CS core network termination of the Iu interface in order to cover the information flow stimulus to the core network and describe the interaction with the supplementary and value added services and capabilities.
For the purposes of the present document, the protocol used over the Nc interface is an enhanced call control protocol supporting call bearer separation such as BICC (which is specified in
3GPP TS 29.205).
The protocol used over the Mc interface is H.248. Existing specifications and recommendations shall not be repeated, as such the relevant specification shall be referred to.
The present document is applicable only for ATM or IP transport in the CS core network.
|
|
|
| |
| Up |
Rapporteur: Phil Hodges |
|
|
|
|
|
|
|
|
|
|
| |
| Up |
Rapporteur: Andy Bennett |
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 23.207 |
SA2 |
|
End-to-end Quality of Service (QoS)
Concept and Architecture |
|
This TS provides the framework for end-to-end Quality of Service involving GPRS and complements
3GPP TS 23.107
which describes the framework for Quality of Service within UMTS.
The document describes the interaction between the TE/MT Local Bearer Service, the GPRS
Bearer Service, and the External Bearer Service, and how these together provide
Quality of Service for the End-to-End Service. In contrast to the
3GPP TS 23.107, the present document
is only applicable to GPRS packet switched access services, and
includes aspects of interworking to the IM subsystem as well as PSTN and other networks.
|
|
|
| |
| Up |
Rapporteur: Johnson Oyama |
|
|
|
|
|
|
|
|
|
|
| |
| Up |
Rapporteur: Keith Drage |
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 23.221 |
SA2 |
|
Architectural Requirements |
|
This TS covers the architectural requirements for the GSM in Iu mode and UMTS systems. In particular it
details the high level requirements for the Circuit Switched (CS) Domain and the stage 2 procedures that span more
than one domain/subsystem within UMTS and GSM. The reference model to which these procedures apply can be
found within
3GPP TS 23.002.
In addition, A mode to Iu mode handover for CS services is addressed. Detailed
architectural requirements within the subsystems are contained within the remainder of the 23 series of specifications
e.g. the requirements for the Packet Switched (PS) domain are contained within
3GPP TS 23.060
and the requirements
for the Bearer Independent CS Core Network are contained in
3GPP TS 23.205.
|
|
|
| |
| Up |
Rapporteur: Elizabeth Daniel |
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 23.228 |
SA2 |
|
IP Multimedia Subsystem (IMS) - Stage 2 |
This TS describes
the IMS concepts related to services, naming and addressing, signaling, mobility,
the roles of session control functions, as well as security and charging.
Section 5 documents the main procedures that are used for the provision of services
in the IP multimedia subsystem.
These procedures are described using text description as well as information flow diagrams.
The procedures described in this document are meant to provide a high level description and
are not intended to be exhaustive. Additional procedures and details are provided in
3GPP TS 24.228.
|
|
|
| |
| Up |
Rapporteur: Thomas Towle |
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 23.234 |
SA2 |
|
3GPP System to WLAN Interworking -
System Description |
This TS specifies system description for interworking between 3GPP systems and Wireless Local Area Networks
(WLANs). This specification is not limited to WLAN technologies.
It is also valid for other IP based Access Networks that support the same capabilities towards the
interworking system as WLAN does. The intent of 3GPP-WLAN Interworking is to extend 3GPP services and
functionality to the WLAN access environment. The 3GPP-WLAN Interworking System provides bearer services
allowing a 3GPP subscriber to use a WLAN to access 3GPP PS based services.
This specification defines a 3GPP system architecture and procedures to do the following:
|
| 1. |
Provide Access, Authentication and Authorisation (AAA) services to the 3GPP-WLAN Interworking System
based on subscription.
| |
| 2. |
Provide access to the locally connected IP network (e.g. the Internet) if allowed by subscription.
| |
| 3. |
Provide WLAN UEs with IP bearer capability to the operator's network and PS Services,
if allowed by subscription.
| |
| 4. |
Provide WLAN UEs with IP bearer capability to access IMS Emergency calls for both UICC and UICC-less cases.
|
|
|
|
| |
| Up |
Rapporteur: Nicolas Martiquet |
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 23.246 |
SA2 |
|
Multimedia Broadcast/Multicast Service (MBMS) -
Architecture and Functional Description |
This TS
describes the stage 2 description (architectural solution and functionalities) for the MBMS Bearer Service, which includes, together with MBMS User Services defined in
3GPP TS 26.346,
all the elements necessary to realise the stage 1 requirements in
3GPP TS 22.146 and
3GPP TS 22.246.
The present document also includes considerations on the manner in which User Services should make use of the MBMS Bearer Service described herein. It should be noted that the specification of MBMS User Services in
3GPP TS 26.346
takes precedence over User Service aspects described in this document.
The present document includes information applicable to network operators, service providers and manufacturers.
|
|
|
| |
| Up |
Rapporteur: Andre Jarvis |
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 23.271 |
SA2 |
|
Functional Stage 2 Description of Location Services (LCS) |
This TS specifies the stage 2 of the LoCation Services (LCS) feature in UMTS and GSM, which provides
the mechanisms to support mobile location services for operators, subscribers and third party service providers.
Location Services may be considered as a network provided enabling technology consisting of standardised
service capabilities, which enable the provision of location applications. The application(s) may be
service provider specific. The description of the numerous and varied possible location applications
which are enabled by this technology are outside the scope of the present document.
However, clarifying examples of how the functionality being described may be used to provide specific
location services may be included.
This stage 2 service description covers the LCS system functional model for the whole system,
the LCS system architecture, state descriptions, message flows, etc.
|
|
|
| |
| Up |
Rapporteur: Gavin Wong |
|
|
|
|
|
|
|
|
|
|
| |
| Up |
Rapporteur: Nigel H. Berry |
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 23.279 |
SA2 |
|
Combining Circuit Switched (CS) and
IMS Services - Stage 2 |
|
This TS provides architectural details to combine CS services and IMS services for using them in parallel
between the same two users in a peer-to-peer context. The document provides a detailed description of how capabilities
and identities are exchanged to enable the combination of CS and IMS services between the same two UEs.
|
|
|
| |
| Up |
Rapporteur: Yun Chao Hu |
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 23.333 |
CT4 |
|
MRFC-MRFP Mp Interface - Procedures Descriptions |
This TS
describes the functional requirements and information flows that generate procedures between the Multimedia Resource Function Controller (MRFC) and the Multimedia Resource Function Processor (MRFP), the Mp Interface.
This specification is limited to information flows relevant to the Mp Interface; in order to define these procedures and make the functional requirements clear some triggers from an external interface may be described; these may be specified within the Mr interface for example or within an AS in which the MRFC function resides. However for the overall stage 2 procedures of IMS see
3GPP TS 23.228.
The protocol on the Mp interface is defined to comply with ITU-T H.248.1 Gateway Control Protocol. The goal of this specification is to provide the input to defining a formal Profile within the H.248 protocol toolbox specifically for the Mp application.
|
|
|
| |
| Up |
Rapporteur: Emmanuel Gay |
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 23.401 |
SA2 |
|
GPRS enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access |
This TS
defines the Stage 2 service description for the Evolved 3GPP Packet Switched Domain - also known as the Evolved Packet System (EPS) in this document. The Evolved 3GPP Packet Switched Domain provides IP connectivity using the Evolved Universal Terrestrial Radio Access Network (E-UTRAN).
The specification covers both roaming and non-roaming scenarios and covers all aspects, including mobility between E-UTRAN and pre-E-UTRAN 3GPP radio access technologies, policy control and charging, and authentication.
The Radio Access Network functionality is documented only to the extent necessary to describe the overall system. TS 36.300 contains the overall description of the Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN).
ITU-T Recommendation I.130 describes a three-stage method for characterisation of telecommunication services, and ITU-T Recommendation Q.65 defines Stage 2 of the method.
TS 23.402 is a companion specification to this specification.
|
|
|
| |
| Up |
Rapporteur: Chris Pudney |
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 23.402 |
SA2 |
|
Architecture enhancements for non-3GPP accesses |
This TS
specifies the stage 2 service description for providing IP connectivity using non-3GPP accesses to the Evolved 3GPP Packet Switched domain. In addition, for E-UTRAN and non-3GPP accesses, the specification describes the Evolved 3GPP PS Domain where the protocols between its Core Network elements are IETF-based.
ITU-T Recommendation I.130 describes a three-stage method for characterisation of telecommunication services, and ITU-T Recommendation Q.65 defines stage 2 of the method.
The specification covers both roaming and non-roaming scenarios and covers all aspects, including mobility between 3GPP and non 3GPP accesses, policy control and charging, and authentication, related to the usage of non-3GPP accesses.
TS 23.401 covers architecture aspects common to the Evolved 3GPP Packet Switched domain.
|
|
|
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 23.406 |
SA2 |
|
Protocols for Advanced Networking (TISPAN);
IMS; Stage 2 description
|
This TS
describes the IP Multimedia Subsystem (IMS) core component of the TISPAN NGN functional architecture and its relationships to other subsystems and components.
Use of IMS functional entities in support of transit scenarios is incompletely described. Completion of this description is dependent on ongoing work in 3GPP.
NOTE: 3GPP SA2 is working on a solution for IMS transit, according to an agreement between TISPAN and 3GPP. When ready, that solution will replace any solution documented by TISPAN in case of discrepancy. The affected IMS functional entities, and the way they perform transit routing, may also be different in the SA2 solution than what is documented in the present document. The SA2 solution will be added to the TISPAN Release-1 documentation.
|
|
|
| |
| Up |
Rapporteur: Balazs Bertenyi |
|
|
|
|
|
|
|
|
|
|
| |
| Up |
Rapporteur: Balazs Bertenyi |
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 23.506 |
SA2 |
|
Protocols for Advanced Networking (TISPAN);
IMS; Stage 2 description
|
This TS
provides the ETSI endorsement of the 3GPP TS 23.228 "IP Multimedia Subsystem; Stage 2,
Release 7".
The present document provides the necessary adaptions to the 3GPP IP Multimedia Core Network Subsystem (IMS), in
order to support the Access Networks and terminals in the scope of the present NGN Release. The present document
also includes certain elements from 3GPP Release 8 (TS 23.228 v8.2.0)
|
|
|
| |
| Up |
Rapporteur: Balazs Bertenyi |
|
|
|
|
|
|
|
|
| | |
|
3GPP TS 23.507 |
SA2 |
|
TISPAN;
Voice Call Continuity (VCC); Stage 2
|
This TS
provides the ETSI TISPAN endorsement of 3GPP TS.23.206 "Voice Call Continuity (VCC)
between Circuit Switched (CS) and IP Multimedia Subsystem (IMS); Stage 2: Release 7".
The current VCC solution explained in the TS.23.206 is essentially defined for a core IMS provider that is a mobile
operator (that has also CS domain). In Informative Annex ZA theres is a possible scenario how the solution can be
extended to a generic IMS operator (e.g. when fixed network operator and CS mobile network operator are separate
organisations).
|
|
|
| |
| Up |
Rapporteur: Balazs Bertenyi |
|
|
|
|
|
|
|
|
|
|
| |
| Up |
Rapporteur: Balazs Bertenyi |
|
|
|
|
|
|
|
|
|
|
| |
| Up |
Rapporteur: Balazs Bertenyi |
|
|
|
|
|
|
|
|
|
|
