id
stringlengths 4
12
| title
stringlengths 8
250
| type
stringclasses 2
values | version
stringclasses 612
values | working_group
stringclasses 30
values | url
stringlengths 65
81
| scope
stringlengths 0
65.7k
|
|---|---|---|---|---|---|---|
22.979 | Feasibility study on combined Circuit Switched (CS) calls and IP Multimedia Subsystem (IMS) sessions | TR | 18.0.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.979/22979-i01.zip | This document studies the service requirements associated with a multimedia service combining a CS call with one or more IMS services (or vice versa), while appearing as a single service to both end-users. The feasibility study addresses the high-level requirements and use cases such for combinational service including charging and user experience. |
22.980 | Network composition feasibility study | TR | 18.0.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.980/22980-i01.zip | The present document explores the feasibility of a uniform procedure for the integration of, and the interworking with, a large variety of heterogeneous network types. This uniform procedure is called Network Composition. It focuses on ad-hoc networks, PANs, moving networks etc., but also includes access systems. The goal is to avoid the need for defining a new procedure for integration / interworking with each newly emerging network type and to explore the feasibility of making the Network Composition procedure dynamic and to minimize human intervention ("plug and play"). Of course, the high security (authentication, authorization) standards of 3GPP must thereby be maintained. Finally, it is desirable for the Network Composition procedure to be flexible regarding what functionality is assumed in the composing network.
It is conceivable that roaming within a pre-set commercial and technological environment could be established dynamically using the same procedure.
This Feasibility Study covers the following aspects:
- Description of purpose and benefits of composition
- Composition use cases highlighting uniformity, dynamicity, security, manageability, scalability, flexibility, as well as business aspects
- Study of potential composition requirements
- Description of the composition process
- Definition of traits and/or implications of introducing this functionality into the 3GPP system, covering subjects such as management, multi-link radio access, mobility, context & policy awareness, security, and media transcoding & adaptation capabilities. |
22.982 | Study of Customised Alerting Tone (CAT) requirements | TR | 18.0.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.982/22982-i01.zip | The objective of this study item is to study requirements and potential new capabilities in 3GPP that need to be standardized for the CAT service, especially additional features for roaming and interoperability support.
The present document specifies the requirements and technical implements for Customized Alerting Tone (CAT) service in CS domain and the developments in PS domain.
Basically this TR is considering voice services, though interaction with MITe [2] services will be studied. Also Multi-media CAT will be taken into consideration, so the CAT user may experience favourable songs, multi-media clips or other customized alerting tones. |
22.983 | Services alignment and migration | TR | 18.0.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.983/22983-i01.zip | This document studies how services to the end user should be delivered and managed regardless of how the user accesses the services (e.g. using CS or IMS) and to ensure a consistent user experience.
The services in scope include but are not restricted to:
• Conversational voice and video services
• Messaging services
• Supplementary Services as applied to the above.
For each of the above types, the service features that should be supported when accessing the service via CS or IMS using any appropriate access type are described. Also, how each service will behave when transferring between domains is described.
The work will also consider how to support existing ("traditional") services while allowing new, innovative services to be provided to the end user using the enhanced capabilities of the IMS. It will cover possible migration paths from where services are provided on both CS and IMS to IMS Call and Service Control. Also, this work will consider roaming and call handling, interaction with legacy terminals, and the provision of user state and location for services accessed via CS or IMS and for services transferred between them. |
22.985 | Service requirements for the User Data Convergence (UDC) | TR | 18.0.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.985/22985-i01.zip | The present document describes the concept of the 3GPP User Data Convergence (UDC). It furthermore collects some architectural requirements and should be taken as guideline in stage 2 and 3 work.
The UDC will simplify the overall network topology and interfaces, avoid data duplication and inconsistency and simplify creation of new services by providing easy access to the user data.
Special consideration is put on the following areas:
- Categorization of the user data of services which would be converged in UDC
- Identification of the requirements on the common data model framework with focus on extensibility
- Identification of the requirements on the UDC for the support of new services including their provisioning |
22.986 | Study on Service Specific Access Control | TR | 18.0.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.986/22986-i01.zip | This Technical Report (TR) presents the results of the Study on Service Specific Access Control (SSAC). The intent of this Study is to assess the ability of 3GPP specifications to meet requirements identified for Services Specific Access Control. This Study considers the following aspects:
• Study use cases and clarify issues in SSAC in EPS.
• Describe the considerations and the problems with existing access control, which are identified in the use cases
• Identify candidate requirements and aspects for providing SSAC in EPS. |
22.987 | Study of haptic services requirements | TR | 18.0.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.987/22987-i01.zip | This Technical Report aims to present use cases in telecommunication services that are developed by applying haptic technology. It also justifies accepting haptic technology in telecommunication services by investigating readiness for its use in the telecommunication system and the level of benefit for the user experience.
For such purpose this document investigates following questions:
- Provide the overview of current haptic technology which might be deployed in telecommunication
- Identify any adaption required for existing services enhanced by supporting the delivery of haptic sense
- Identify key aspects of new services built on capabilities provided by haptic technology
- Identify and specify general requirements for delivery of haptic sense in telecommunication networks
- Identify the scope and roles of 3GPP for mobile haptic services and consult with OMA to coordinate on the development of mobile haptic services
Note that this Technical Report considers all types of telecommunication networks within the scope of 3GPP, including mobile networks and IMS-based fixed networks, etc. |
22.988 | Study on alternatives to E.164 for Machine-Type Communications (MTC) | TR | 18.0.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.988/22988-i01.zip | This document seeks to study and highlight the challenge of using the existing public numbering resources to support Machine Type Communication (MTC) services and proposes that 3GPP develop an alternative to using public numbering resources for MTC communications. |
22.989 | Study on Future Railway Mobile Communication System | TR | 18.5.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.989/22989-i50.zip | |
22.990 | Study on off-network for rail | TR | 18.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.990/22990-i00.zip | The present document analyses Rail Off-Network use cases in order to derive potential requirements and investigate if normative adjustments are feasible or not. |
23.002 | Network architecture | TS | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.002/23002-i00.zip | This document 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.
Note that this document does not cover, or even list, all features of PLMNs. |
23.003 | Numbering, addressing and identification | TS | 18.7.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.003/23003-i70.zip | |
23.007 | Restoration procedures | TS | 18.5.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.007/23007-i50.zip | |
23.008 | Organization of subscriber data | TS | 18.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.008/23008-i10.zip | |
23.009 | Handover procedures | TS | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.009/23009-i00.zip | The present document 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 [9]. For the circuit switched handover functionality related to SRVCC and vSRVCC, it is based on the service requirements in 3GPP TS 23.216 [26].
The present document considers the following five handover cases:
i) handover between Base Station Subsystems (BSS) connected to the same MSC, this is termed an Intra-MSC handover;
ii) handover between Radio Network Subsystems (RNS) connected to the same 3G_MSC, this is termed an Intra-3G_MSC handover/relocation. This case also includes inter-system handover between RNS and BSS if the 3G_MSC supports the A-interface. In the context of this specification the term RNS refers also to a BSS when serving a mobile station in Iu mode. Furthermore, this case includes Intra-3G_MSC enhanced SRNS relocation between two RNSs;
iii) handover between Base Station Subsystems connected to different MSCs, this is termed an Inter-MSC handover. This category can be sub-divided into three further procedures:
a) the Basic Inter-MSC Handover procedure, where the MS is handed over from a controlling MSC (MSC‑A) to another MSC (MSC‑B);
b) the Subsequent Inter-MSC Handover procedure, where the MS is handed over from MSC‑B to a third MSC (MSC‑B');
c) the Subsequent Inter-MSC handback, where the MS is handed back from MSC‑B to MSC‑A.
iv) handover between Radio Network Subsystems connected to different 3G_MSCs, this is termed an Inter-3G_MSC handover/relocation. In the context of this specification the term RNS also refers to a BSS when serving a mobile station in Iu mode. This category can be divided into three further sub-procedures:
a) the Inter-3G_MSC Handover procedure from UMTS to GSM, where the UE/MS is handed over from a controlling 3G_MSC (3G_MSC‑A) to an MSC (MSC‑B);
b) the Inter-3G_MSC Handover procedure from GSM to UMTS, where the UE/MS is handed over from a controlling MSC (MSC‑A) to a 3G_MSC (3G_MSC‑B);
c) the Inter-3G_MSC Relocation procedure, where the UE is relocated from 3G_MSC‑A to 3G_MSC‑B. This procedure can also be combined with a hard change of radio resources (Hard Handover with switch in the core network).
The MSC in items a) and b) this category can optionally be a 3G_MSC supporting the A-interface. The three sub-procedures also cover subsequent handover/relocation to a third MSC‑B' or 3G_MSC‑B' and subsequent handover/relocation back to MSC‑A or 3G_MSC‑A.
v) handover within one BSS connected via AoIP, supported by the same MSC, this is termed "BSS Internal Handover with MSC Support". It is in fact a kind of external handover from MSC perspective and therefore a subset of i) but described in detail in separate clause 6.3 for clarity. The MSC in this category can be any of MSC-A, MSC-B, 3G_MSC-A or 3G_MSC-B.
In both cases i) and iii) the same procedures as defined in the 3GPP TS 48.008 [5] and the 3GPP TS 24.008 [10] shall be used on the A‑interface and on the Radio Interface, respectively.
In case ii) the same procedures as defined in the 3GPP TS 25.413 [11] and the 3GPP TS 24.008 [10] shall be used on the Iu‑interface. If the 3G_MSC in case ii) also supports the A-interface, the 3GPP TS 48.008 [5] and the 3GPP TS 24.008 [10] shall be used on the A‑interface.
In case iii) the handover procedures shall transport the A-interface messages between MSC‑A and MSC‑B described in the Mobile Application Part (MAP), 3GPP TS 29.002 [12].
In case iv) the handover procedures shall transport the A-interface messages between 3G_MSC and MSC described in the Mobile Application Part (MAP), 3GPP TS 29.002 [12].
In case iv) the relocation procedure shall transport the Iu-interface messages between 3G_MSC‑A and 3G_MSC‑B described in the Mobile Application Part (MAP), 3GPP TS 29.002 [12].
The interworking between the 3GPP TS 29.002 [12] protocol and the 3GPP TS 48.008 [5] protocol is described in the 3GPP TS 29.010 [8].
Multicall supplementary service is not applicable in GERAN Iu mode and relocation of Multicalls is therefore only possible within UTRAN.
Enhanced SRNS relocation is possible only within UTRAN between two RNSs conntected to the same 3G_MSC, i.e. in case ii).
Handovers, which take place on the same MSC are termed Intra-MSC handovers; this includes both Inter-BSS and Intra‑BSS handovers.
Handovers, which take place on the same 3G_MSC are termed Intra-3G_MSC handovers; this includes Inter-RNS handovers and optionally RNS to BSS and BSS to RNS handovers.
In the context of this specification the term InterSystem handover can also refer to a handover which takes place between a Base Station serving a mobile station in Iu mode and a Base Station serving a mobile in A/Gb mode.
"Flexible Iu interface for handover/relocation" Option (see 3GPP TS 23.221 [19], clause 4.2.1): Up to release 99 an RNS can be connected only to one 3G_MSC. From release 4 onwards, as a network option, an RNS can have Iu interfaces to more than one MSC. Such an additional Iu interface may be selected by an MSC during an intra-PLMN relocation or intra-PLMN BSS to RNS handover procedure. This allows the MSC to use an Intra-3G_MSC handover procedure according to case ii) instead of an Inter-3G_MSC handover procedure according to case iv). The decision whether to use the Intra-3G_MSC handover procedure is implementation and configuration dependent. In a network implementing this option, a global title based on the Global RNC-Id may optionally be used for the addressing of the Iu interface messages.
"Intra Domain Connection of RAN Nodes to Multiple CN Nodes" Option (see 3GPP TS 23.236 [18]): when applied, a BSS or an RNS can be connected to more than one MSC.
The present document also covers the requirements for handover in ongoing GSM voice group calls, directed retry and handover without a circuit connection between (U)MSCs. The present document does not consider the case of handovers between radio channels on the same BSS (Intra-BSS handover) or the handover of packet radio services except for case v), the "BSS Internal Handover with MSC Support" for Intra-BSS handover in AoIP, involving the MSC as described in clause 6.3. The Inter-RNS handover case that results in a relocation is covered by the present document, but not other Inter-RNS or Intra-RNS handover cases.
For voice broadcast calls in GSM, the speaker uses normal point-to-point handover procedures, whilst the listeners use idle mode cell reselection procedures, as for the voice group call listeners.
Voice group calls is only applicable to GSM and handover of voice group calls is therefore only possible in GSM.
Inter-MSC hand-over imposes a few limitations on the system. After inter-MSC hand-over:
- call re-establishment is not supported.
The list of 3GPP TS 48.008 [5] features supported during and after Inter-MSC handover is given in 3GPP TS 49.008 [7].
In the Inter-MSC handover case, the interworking between a Phase 1 BSSMAP protocol possibly used by one MSC and the Phase 2 BSSMAP protocol used in the Phase 2 MAP protocol on the E-interface is performed by this MSC.
This specification assumes TDM based Core Network and therefore PCM, ITU-T G.711 [16] encoded, voice channel for speech calls between MSC-A and MSC-B and toward the other party. For bearer independent CS Core Network architecture implementations see 3GPP TS 23.205 [23] and 3GPP TS 23.231 [24]. For handover including Out-Of-Band transcoder control and transcoder free operation see 3GPP TS 23.153 [25]. For handover with Local Call Local Switch (LCLS) see 3GPP TS 23.284 [29].
NOTE 1: The message primitive names used in the SDL diagrams and message flows in the present document do not represent the actual messages specified in the GSM or 3GPP stage 3 technical specifications. The primitive names are only intended to be indicative of their use in the present document.
The MSC server enhanced for SRVCC and the MSC server enhanced for vSRVCC as specified in 3GPP TS 23.216 [26] follows the procedures defined for 3G_MSC-A in the present specification with the exceptions and additions as specified in clause 4.5. |
23.011 | Technical realization of Supplementary Services | TS | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.011/23011-i00.zip | The present document 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, 230.8x and 230.9x‑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, 24.08x and 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, 22.08x and 22.09x‑series of technical specifications.
Definitions are given in 3GPP TS 22.004..
NOTE: The technical specifications on the technical realisation of supplementary services do not distinguish between subscriber, user and customer, since all three do not fully cover the textual needs. Generally the term "subscriber" is used, even if this person is not having the subscription. |
23.012 | Location management procedures | TS | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.012/23012-i00.zip | The present document 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 [8]. 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 3GPP TS 23.022 [6]. 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 [8].
The present document excludes location management procedures for the packet switched domain, which are covered in 3GPP TS 23.060 [20].
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. |
23.014 | Support of Dual Tone Multi-Frequency (DTMF) signalling | TS | 18.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.014/23014-i00.zip | The present document describes how Dual Tone Multi Frequency (DTMF) signals are supported in the 3GPP system. |
23.015 | Technical realization of Operator Determined Barring (ODB) | TS | 18.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.015/23015-i10.zip | |
23.016 | Subscriber data management; Stage 2 | TS | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.016/23016-i00.zip | 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/HSS) 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/HSS to SGSN is required in the following situations:
- GPRS location updating;
- EPS location updat ing;
- 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/HSS to the SGSN are described in this specification; these rules only apply when the MAP protocol is used for subscriber data updating (see 3GPP TS 29.002 [23]). 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 and the EPC bearer context update from the SGSN to the P-GW via S-GW are out of scope of this specification.
NOTE: The term 'HLR' should be read 'HLR/HSS' throughout the document. |
23.018 | Basic call handling; Technical realization | TS | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.018/23018-i00.zip | The present document 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 handling of DTMF signalling and Off-Air Call set-up (OACSU) are not described in the present document.
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 [12]) and optimal routeing (3GPP TS 23.079 [13]). The use of the Provide Subscriber Information message flow is shown in 3GPP TS 23.078 [12] and 3GPP TS 23.079 [13].
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.
If there is any conflict between the present document and the corresponding stage 3 specifications (3GPP TS 24.008 [26], 3GPP TS 25.413 [27], 3GPP TS 48.008 [2] and 3GPP TS 29.002 [29]), the stage 3 specification shall prevail. |
23.031 | 3G Security; Fraud Information Gathering System (FIGS); Technical realization; Stage 2 | TS | 18.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.031/23031-i00.zip | This Technical Specification 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. |
23.032 | Universal Geographical Area Description (GAD) | TS | 18.3.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.032/23032-i30.zip | The present document defines an intermediate universal Geographical Area Description which subscriber applications, GSM, UMTS, EPS or 5GS services can use and the network can convert into an equivalent radio coverage map.
For GSM, UMTS, EPS or 5GS 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, RNC/Node B, eNB or gNB).
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.
The specification further provides a description of range and direction, relative location and relative velocity for a pair of devices such as 2 UEs. |
23.034 | High Speed Circuit Switched Data (HSCSD); Stage 2 | TS | 18.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.034/23034-i00.zip | The present document 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.
In analogy with ITU-T Recommendation I.130 [6] (refer to annex A) and with reference of ITU-T Recommendation Q.65 [7] VI.1 (Stage 2 of the method for characterization of services supported by an ISDN), the second stage of the HSCSD is defined as follows.
Stage 2 identifies the functional capabilities and information flows needed to support the service as described in 3GPP TS 22.034 [9]. 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.
The present document specifies functions, procedures and information which apply to GERAN Iu mode. However, functionality related to GERAN Iu mode is neither maintained nor enhanced. |
23.035 | Immediate Service Termination (IST); Stage 2 | TS | 18.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.035/23035-i00.zip | This 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 message. |
23.038 | Alphabets and language-specific information | TS | 18.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.038/23038-i00.zip | The present document 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 [2]).
The specification for the Data Circuit terminating Equipment/Data Terminal Equipment (DCE/DTE) interface (3GPP TS 27.005 [8]) will also use the codes specified herein for the transfer of SMS data to an external terminal. |
23.040 | Technical realization of the Short Message Service (SMS) | TS | 18.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.040/23040-i00.zip | The present document describes the Short Message Service (SMS) for GSM/UMTS/EPS/5GS 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 MME functionality (with regard to the SMS);
- the SMSF functionality;
- the routing requirements;
- the protocols and protocol layering;
for the Mobile Originated and Mobile Terminated Short Message Service Teleservices, as specified in 3GPP TS 22.003 [2] and 3GPP TS 22.105 [32].
The use of radio resources for the transfer of short messages between the MS and the MSC or the SGSN or the MME is described in 3GPP TS 24.011 [13].
The present document also describes the Short Message Service (SMS) for EPS networks supported via "SMS in MME" (see 3GPP TS.23.272 [45], annex C).
The present document also describes the SGSN supporting Diameter based protocol for SMS between the SGSN and the central SMS functions (SMS-GMSC, SMS-IWMSC, SMS-Router) in annex J.
The present document also describes SMS for 5GS networks (see 3GPP TS 23.501 [51] and 3GPP TS 23.502 [52]).
The network aspects of Short Message Service provision are outside the scope of the present document (i.e. the provision of network connectivity between the PLMN subsystems). There is no technical restriction within the present document for the transfer of short messages between different PLMNs. Any such restriction is likely to be subject to commercial arrangements and PLMN operators must make their own provision for interworking or for preventing interworking with other PLMNs as they see fit.
The required and assumed network service offered to the higher layers is defined in the present document. |
23.041 | Technical realization of Cell Broadcast Service (CBS) | TS | 18.6.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.041/23041-i60.zip | |
23.042 | Compression algorithm for text messaging services | TS | 18.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.042/23042-i00.zip | The present document introduces the concepts and mechanisms involved in the compression and decompression of a stream of data. |
23.053 | Tandem Free Operation (TFO); Service description; Stage 2 | TS | 18.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.053/23053-i00.zip | The present document defines the stage 2 service description for Tandem Free Operation (TFO) in and between GSM and UMTS. Tandem Free Operation applies only to speech calls.
NOTE: The TFO principles are built so that they could be used as well by other systems other than GSM and UMTS.
In analogy with ITU-T Recommendations I.130 [2] and with reference to ITU-T Recommendations Q.65 VI.1 (Stage 2 of the method for the characterisation of services supported by an ISDN), the second stage of the following three-level structure is derived from a stage 1 service description.
- Stage 1 is an overall service description, from the service subscriber's and user's standpoints, that views the network as a single entity which provides services to the user.
- Stage 2 identifies the functional capabilities and information flows needed to support the service described in stage 1. 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.
- Stage 3 defines the signalling system protocols and switching functions needed to implement the service described in stage 2. |
23.057 | Mobile Execution Environment (MExE); Functional description; Stage 2 | TS | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.057/23057-i00.zip | The present document 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 (TS 22.057 [2]). 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.
Implementation of this specification outside the UE (User Equipment) is outside the scope of this specification. |
23.060 | General Packet Radio Service (GPRS); Service description; Stage 2 | TS | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.060/23060-i00.zip | The present document defines the stage‑2 service description for the General Packet Radio Service (GPRS) which is a packet bearer service and a main part of the packet domain. ITU-T Recommendation I.130 [29] describes a three-stage method for characterisation of telecommunication services, and ITU-T Recommendation Q.65 [31] defines stage 2 of the method. The GPRS described in the present document is also the description of the GERAN and UTRAN related functionality of the Evolved Packet System (EPS) according to TS 23.401 [89].
The present document does not cover the Radio Access Network functionality. TS 43.064 [11] contains an overall description of the GSM EDGE Radio Access Network (GERAN). TS 25.401 [53] contains an overall description of the Universal Terrestrial Radio Access Network (UTRAN). TS 43.051 [74] contains an overall description of GSM/EDGE Radio Access Network.
The present document does not cover the functionality of the GPRS enhancements for the Evolved Universal Terrestrial Radio Access Network (E‑UTRAN). This functionality and also the interoperation functionality between E‑UTRAN and GERAN/UTRAN accesses are described in TS 23.401 [89].
The present document specifies functions, procedures and information which apply to GERAN Iu mode. However, functionality related to GERAN Iu mode is neither maintained nor enhanced since Rel‑9. |
23.066 | Support of Mobile Number Portability (MNP); Technical realization; Stage 2 | TS | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.066/23066-i00.zip | The present document describes several alternatives for the realisation of Mobile Number Portability.
The present document includes information applicable to network operators, service providers, switch and database manufacturers and national regulators.
It is left to operator and implementation decisions which option, or combination of options, is used, taking into account the regulatory and architectural constraints that may prevail. The possible implications of these options on internal node functions and on signalling performance are not covered in the present document.
Normative Annex A of the present document describes the technical realisation of the handling of calls to ported UMTS or GSM mobile subscribers using IN technology.
Normative Annex C of the present document describes the technical realisation of the handling of calls to ported UMTS or GSM mobile subscribers using Signalling Relay technology.
Normative Annex A and Normative Annex C describe alternative solutions. The network operator may choose the solution to be used in his network.
Normative Annex B of the present document describes the technical realisation of the handling of non-call related SCCP signalling for ported UMTS or GSM mobile subscribers using Signalling Relay technology.
The present document does not specify the porting process. |
23.067 | enhanced Multi-Level Precedence and Pre-emption Service (eMLPP); Stage 2 | TS | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.067/23067-i00.zip | The present document specifies the stage 2 description of the enhanced Multi-Level Precedence and Pre-emption Service (eMLPP) which provides different call priorities in combination with fast call set-up and pre-emption for different applications according to 3GPP TS 22.067. |
23.072 | Call Deflection (CD) supplementary service; Stage 2 | TS | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.072/23072-i00.zip | This Technical Specification gives the stage 2 description of the Call Deflection supplementary service. |
23.078 | Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 4; Stage 2 | TS | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.078/23078-i00.zip | The present document specifies the stage 2 description for the fourth phase (see 3GPP TS 22.078 [6]) 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 HPLMN.
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.
In the present document, the GSM Service Control Function (gsmSCF) is treated as being part of the HPLMN. The regulatory environment in some countries may require the possibility that the gsmSCF and the HPLMN are controlled by different operators, and the gsmSCF and the HPLMN are therefore distinct entities.
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;
- Inclusion of flexible tone injection;
- 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 [29].
CAMEL is not applicable to Emergency Setup (TS 12), i.e. if an Emergency call is requested, then the gsmSSF shall not be invoked.
The mechanism described in the present document addresses especially the need for information exchange between the VPLMN or IPLMN and the HPLMN for support of operator specific services. Any user procedures for the control of operator specific services are outside the scope of the present document. Subscribers who have subscribed to operator specific services and therefore need the functional support of the CAMEL feature shall be marked in the HPLMN and VPLMN. In case a subscriber is marked to need CAMEL support, the appropriate procedures which provide the necessary information to the VPLMN or the HPLMN are invoked. It is possible for the HPLMN to instruct the VPLMN or IPLMN to interact with a gsmSCF which is controlled by the HPLMN.
The specification of operator specific services is outside the scope of the present document. |
23.079 | Support of Optimal Routeing (SOR); Technical realization | TS | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.079/23079-i00.zip | The present document specifies the technical realisation of the first phase of the network feature Support of Optimal Routeing (SOR). The first phase of SOR provides:
- as a network operator option, a method to route a call from one mobile subscriber directly to another mobile subscriber who is in the same country as the calling mobile subscriber or in the called mobile subscriber's home country, without needing to connect the call via the HPLMN of the called subscriber, even though the called mobile subscriber has roamed outside his HPLMN;
- a method to forward calls when a called mobile subscriber who has roamed outside his home country is busy, or is not reachable, or does not reply, to a forwarded-to destination in the HPLMN country of the called subscriber or the VPLMN country of the called subscriber, without needing to connect the forwarded call via the VPLMN of the called subscriber;
- a method to combine the optimal routeing described in the first bullet point above with the optimal routeing described in the second bullet point above.
OR of a call is permitted only if all entities involved in handling the call support OR.
Other cases of optimal routeing (e.g. calls where the calling and called subscribers are in different countries, forwarding to a mobile subscriber or multiple forwarding) will be considered for inclusion in later phases. |
23.081 | Line Identification supplementary services; Stage 2 | TS | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.081/23081-i00.zip | The present document gives the stage 2 description of the call identification supplementary services.
The group line identification supplementary services are divided into the following four supplementary services:
‑ Calling line identification presentation CLIP (clause 1);
‑ Calling line identification restriction CLIR (clause 2);
‑ Connected line identification presentation COLP (clause 3);
‑ Connected line identification restriction COLR (clause 4). |
23.082 | Call Forwarding (CF) supplementary services; Stage 2 | TS | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.082/23082-i00.zip | The present document gives the stage 2 description of the call forwarding supplementary services.
The group of supplementary services call offering supplementary services is divided into 4 different supplementary services:
- Call forwarding unconditional (CFU) (clause 1);
- Call forwarding on mobile subscriber busy (CFB) (clause 2);
- Call forwarding on no reply (CFNRy) (clause 3);
- Call forwarding on mobile subscriber not reachable (CFNRc) (clause 4). |
23.083 | Call Waiting (CW) and Call Hold (HOLD) supplementary services; Stage 2 | TS | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.083/23083-i00.zip | The present document gives the stage 2 description of the call completion supplementary services.
The group of call completion supplementary services is divided into the following two supplementary services:
- Call waiting (CW) (clause 1);
- Call hold (HOLD) (clause 2). |
23.084 | Multi Party (MPTY) supplementary service; Stage 2 | TS | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.084/23084-i00.zip | The present document gives the stage 2 description of the multi party supplementary services.
Only one multi party supplementary service has been defined, this is the Multi Party (MPTY) service, and is described in clause 1. |
23.085 | Closed User Group (CUG) supplementary service; Stage 2 | TS | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.085/23085-i00.zip | The present document gives the stage 2 description of the closed user group supplementary service.
The community of interest supplementary service defined is:
- closed user group (CUG) (see clause 1). |
23.086 | Advice of Charge (AoC) supplementary services; Stage 2 | TS | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.086/23086-i00.zip | The present document gives the stage 2 description of the Advice of Charge (AoC) supplementary services.
The charging supplementary services currently defined are:
- Advice of Charge (Information) (AoCI) (clause 1);
- Advice of Charge (Charging) (AoCC) (clause 2). |
23.087 | User-to-User Signalling (UUS) supplementary service; Stage 2 | TS | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.087/23087-i00.zip | The present document gives the stage 2 description of the User-to-User signalling supplementary services.
The User-to-user supplementary service is divided into 3 different services:
- Service 1 (UUS1)
- Service 2 (UUS2)
- Service 3 (UUS3) |
23.088 | Call Barring (CB) Supplementary Services; Stage 2 | TS | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.088/23088-i00.zip | The present document gives the stage 2 description of the call barring services.
The possibility for a mobile subscriber to have certain categories of calls barred originated from or terminated at his access:
Barring of outgoing calls (clause 1):
- Barring of all outgoing calls (BAOC) (Barring program 1);
- Barring of outgoing international calls (BOIC) (Barring program 2);
- Barring of outgoing international calls EXCEPT those directed to the home PLMN country
(BOIC-exHC) (Barring program 3).
Barring of incoming calls (clause 2):
- Barring of all incoming calls (BAIC) (Barring program 1);
- Barring of incoming calls when roaming outside the home PLMN country
(BIC-Roam) (Barring program 2);
- Anonymous Call Rejection (ACR) (Barring program 3).
NOTE: The call barring program "incoming calls when roaming outside the home PLMN country" (clause 2) is only relevant if as a general rule the called mobile subscriber pays the charges for the forwarded part of the call from his home PLMN country to any other country. |
23.090 | Unstructured Supplementary Service Data (USSD); Stage 2 | TS | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.090/23090-i00.zip | The present document gives the stage 2 description of Unstructured Supplementary Service Data (USSD).
The unstructured supplementary service data (USSD) mechanism allows the Mobile Station (MS) user and a PLMN operator defined application to communicate in a way which is transparent to the MS and to intermediate network entities. The mechanism allows development of PLMN specific supplementary services. The following diagram shows how handling of USSD is carried out, independently of the applications.
Figure 1.1: Handling of USSD
The present document defines the requirements for handling USSD at the MS and network entities. It does not include specification of particular applications, nor does it specify how a particular application is selected. Where more than one application exists at a network entity, routing of messages to the correct application is carried out by the USSD handler. The MMI for USSD is specified in TS 22.030 and TS 22.090. The alphabet indicator and the data coding scheme are defined in TS 23.038.
USSD may be initiated by the MS user, or by the network in the following ways:
- Network initiated USSD (clause 1);
- Mobile initiated USSD (clause 2). |
23.091 | Explicit Call Transfer (ECT) supplementary service; Stage 2 | TS | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.091/23091-i00.zip | The present document gives the stage 2 description of the call transfer supplementary services.
Only one call transfer supplementary service has been defined, this is the Explicit Call Transfer (ECT) supplementary service, and is described in the present document. |
23.093 | Technical realization of Completion of Calls to Busy Subscriber (CCBS); Stage 2 | TS | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.093/23093-i00.zip | This Technical Specification gives the stage 2 description of the Completion of Calls to Busy Subscriber (CCBS) supplementary service. |
23.094 | Follow-Me (FM); Stage 2 | TS | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.094/23094-i00.zip | The present document specifies the stage 2 description for the Follow Me feature.
The Follow Me feature enables a mobile subscriber A to manipulate the Follow Me data of a remote party B in such a way that subsequent calls directed to remote party B will be forwarded to subscriber A. |
23.096 | Name identification supplementary services; Stage 2 | TS | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.096/23096-i00.zip | The present document gives the stage 2 description of the Name Identification Supplementary Services.
The group of Name Identification Supplementary Services contains the following Supplementary Service:
CNAP - Calling name presentation (clause 4). |
23.097 | Multiple Subscriber Profile (MSP) (Phase 2); Stage 2 | TS | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.097/23097-i00.zip | The present document specifies the stage 2 description of the Multiple Subscriber Profile (MSP) Supplementary Service Phase 2. MSP Phase 2 is implemented using CAMEL Phase 3. |
23.101 | General Universal Mobile Telecommunications System (UMTS) architecture | TS | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.101/23101-i00.zip | This TS defines the basic physical and functional separation of UMTS. The contents of this specification is limited to those features that are common to all UMTS networks independent of their origin. It identifies and names the reference points and functional groupings appearing at this level. |
23.107 | Quality of Service (QoS) concept and architecture | TS | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.107/23107-i00.zip | The present document 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. |
23.108 | Mobile radio interface layer 3 specification, core network protocols; Stage 2 | TS | 18.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.108/23108-i00.zip | The present document specifies the procedures used at the radio interface (Reference Point Um, see 3GPP TS 24.002 [15]) for Call Control (CC), Mobility Management (MM), and Session Management (SM).
When the notations for "further study" or "FS" or "FFS" are present in the present document 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 3GPP TS 44.003 [16].
The structured functions and procedures of this protocol and the relationship with other layers and entities are described in general terms in 3GPP TS 24.007 [20]. |
23.110 | Universal Mobile Telecommunications System (UMTS) access stratum; Services and functions | TS | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.110/23110-i00.zip | The present document specifies the services provided by the Access Stratum to the rest of the system. The adopted architecture is given by TS 23.101 [2].
The present document describes the main functions visible at the boundary between the Access Stratum and the rest of the system, it describes in general terms the information flows, both control and user data, over this boundary and relevant for the Access Stratum.
The present document is the basis of the detailed specifications of the protocols which rule the information flows, both control and user data, between the Access Stratum and the parts of UMTS outside the Access Stratum, and of the detailed specifications of the UTRAN. These detailed specifications are to be found in other Technical Specifications. |
23.116 | Super-Charger technical realization; Stage 2 | TS | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.116/23116-i00.zip | The present document specifies the stage 2 description of the Super-Charger that provides a mechanism to reduce the signalling traffic associated with mobility. |
23.119 | Gateway Location Register (GLR); Stage 2 | TS | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.119/23119-i00.zip | The present document gives the stage 2 description of the Gateway Location Register (GLR) within the UMTS Core Network as a means of reducing the amount of MAP signalling traffic associated with location management carried over inter-PLMN links for roaming users.
The present document will be restricted of the case where the GLR supports one VPLMN only. |
23.122 | Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode | TS | 18.11.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.122/23122-ib0.zip | |
23.135 | Multicall supplementary service; Stage 2 | TS | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.135/23135-i00.zip | The present document gives the stage 2 description of the Multicall supplementary service. |
23.139 | 3GPP system - fixed broadband access network interworking; Stage 2 | TS | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.139/23139-i00.zip | This document specifies the Stage 2 system description for the interworking between a 3GPP system and a Fixed Broadband Access network defined by Broadband Forum to provide the IP connectivity to a 3GPP UE using a WLAN and a H(e)NB connected to a Fixed Broadband Access network.
The specification covers the system description mobility, Policy, QoS aspects between 3GPP and a Fixed Broadband Access network as well as the respective interactions with the PCC frameworks. This document specifies the detailed extension to EPC defined in TS 23.401 [2] and TS 23 402 [3] for supporting Fixed Broadband Access Network. The extension to PCC framework are specified in TS 23.203 [4]. |
23.153 | Out of band transcoder control; Stage 2 | TS | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.153/23153-i00.zip | The present document specifies the stage 2 description of the Out-of-Band Transcoder Control for speech services. It describes the principles and procedures to support Transcoder Free Operation, Tandem Free Operation and the interworking between TrFO and TFO. Transcoder at the edge is also part of the present document.
The present document specifies functions, procedures and information which apply to GERAN Iu mode. However, functionality related to GERAN Iu mode is neither maintained nor enhanced. |
23.142 | Value-added Services for SMS (VAS4SMS); Interface and signalling flow | TS | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.142/23142-i00.zip | The present document describes the stage 2 of the VAS4SMS (Value Added Service for SMS). It includes:
- The logic architecture;
- The logic elements functionality;
- The signaling flows;
- The interaction with other features.
The service requirements of VAS4SMS are specified in 3GPP TS 22.142 [2].
The functionality and mechanism of SMS Service is defined in 3GPP TS 23.040 [4]. |
23.146 | Technical realization of facsimile Group 3 non-transparent | TS | 18.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.146/23146-i00.zip | The present document describes the procedures allowing the technical realization of the real time end‑to‑end facsimile group 3 service within the UMTS PLMN using non‑transparent network support according to the definition of the Teleservices 61 and 62 specified in 3GPP TS 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: V.25bis is outdated. References to V.25bis procedures need to be replaced by corresponding procedures based on V.250 and 3GPP TS 27.007. |
23.161 | Network-Based IP Flow Mobility (NBIFOM); Stage 2 | TS | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.161/23161-i00.zip | The scope of this document is to specify the support of NBIFOM (Network based IP Flow Mobility) i.e. IP flow mobility based on network mobility protocols. This feature supports PDN connections that are simultaneously connected over 3GPP access (i.e. S5/S8 connection to a PDN GW) and a WLAN access (i.e. S2a or S2b connection to the same PDN GW). |
23.141 | Presence service; Architecture and functional description | TS | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.141/23141-i00.zip | The present document describes the stage 2 description (architectural solution and functionalities) for the Presence Service, which includes the elements necessary to realise the stage 1 requirements in TS 22.141 [2].
The present document includes information applicable to network operators, service providers and manufacturers. |
23.167 | IP Multimedia Subsystem (IMS) emergency sessions | TS | 18.2.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.167/23167-i20.zip | |
23.172 | Technical realization of Circuit Switched (CS) multimedia service UDI/RDI fallback and service modification; Stage 2 | TS | 18.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.172/23172-i00.zip | The present document describes the Service Change and UDI Fallback (SCUDIF) feature. This service is available to UDI/RDI multimedia calls and allows users to achieve successful call establishment when end to end circuit-switched (CS) multimedia is not possible (fallback to speech) or when signalling of the feature is not possible in the network (fallback to preferred service or speech). Furthermore, it allows the users to swap between a multimedia service and basic speech during an established call.
NOTE: In the present document, the term "multimedia" refers to UDI/RDI multimedia unless specifically stated. |
23.180 | Mission critical services support in the Isolated Operation for Public Safety (IOPS) mode of operation | TS | 18.0.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.180/23180-i00.zip | |
23.202 | Circuit switched data bearer services | TS | 18.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.202/23202-i00.zip | The present document provides an overview of the architecture and issues related to the provision of Circuit Switched Bearer Services in a 3G mobile network (UMTS) operating in UTRAN or GERAN Iu mode. Handover to GERAN A/Gb mode is also considered.
NOTE: The Gb interface does not play any role in the scope of the present document although the term "A/Gb mode" is used. |
23.203 | Policy and charging control architecture | TS | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.203/23203-i00.zip | |
23.204 | Support of Short Message Service (SMS) over generic 3GPP Internet Protocol (IP) access; Stage 2 | TS | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.204/23204-i00.zip | |
23.205 | Bearer-independent circuit-switched core network; Stage 2 | TS | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.205/23205-i00.zip | The present document 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 [22]). The protocol used over the Mc interface is H.248 (which is specified in 3GPP TS 29.232 [6]). Existing specifications and recommendations shall not be repeated, as such the relevant specification shall be referred to.
SIP-I based CS core network is further specified in 3GPP TS 23.231 [42].
Local Call Local Switch (LCLS) functionality is further specified in 3GPP TS 23.284 [45].
The present document is applicable only for ATM or IP transport in the CS core network.
Figure 1: CS core network logical architecture
The CAP interfaces and the interfaces towards the HLR are outside the scope of the present document.
Details of Transcoder-Free Operation are outside the scope of the present document. Please see 3GPPTS 23.153 [3] for more information.
The present document specifies functions, procedures and information which apply to GERAN Iu mode. However, functionality related to GERAN Iu mode is neither maintained nor enhanced. |
23.207 | End-to-end Quality of Service (QoS) concept and architecture | TS | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.207/23207-i00.zip | The present document provides the framework for end-to-end Quality of Service involving GPRS and complements TS 23.107 [3] which describes the framework for Quality of Service within UMTS. The end-to-end QoS architecture is provided in Figure 1. 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. The document also describes IP level mechanisms necessary in providing end-to-end Quality of Service involving GPRS networks, including possible interaction between the IP level and the GPRS level, as well as the application level and the IP level.
This document covers different architectural aspects of the end-to-end Quality of Service concept and architecture with varying level of detail. In general, other specifications shall be referred to for further details; these other specifications enable the reader to acquire the full understanding of the end-to-end Quality of Service concept and architecture. In particular, the stage 2 specification for the PCC architecture is specified in TS 23.203 [21]. The present document does not contain any requirements for the PCC architecture.
In contrast to the TS 23.107 [3], 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. The document does not cover the circuit switched access services.
Figure 1: End-to-End QoS Architecture |
23.214 | Architecture enhancements for control and user plane separation of EPC nodes | TS | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.214/23214-i00.zip | The present document specifies the overall stage 2 level functionality for control and user plane separation of EPC's SGW, PGW and TDF. This enables a flexible placement of the separated control plane and user plane functions for supporting diverse deployment scenarios (e.g. central or distributed user plane function) without affecting the overall functionality provided by these EPC entities. |
23.216 | Single Radio Voice Call Continuity (SRVCC); Stage 2 | TS | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.216/23216-i00.zip | This document specifies the architecture enhancements for Single Radio Voice Call Continuity (SRVCC) between the following access systems for voice calls that are anchored in the IMS:
- from E‑UTRAN to 3GPP2 1xCS;
- from E‑UTRAN to UTRAN/GERAN;
- from UTRAN (HSPA) to UTRAN/GERAN.
- from UTRAN/GERAN to E-UTRAN.
- from GERAN to UTRAN (HSPA).
- from NG-RAN to UTRAN.
This document will not describe 3GPP2 functional entities. However, interfaces between both 3GPP and 3GPP2 functional entities are described in this specification.
SRVCC from E‑UTRAN access to 3GPP2 1xCS is covered in this specification, including the handling of IMS emergency call continuity. Handling of non‑voice component and SRVCC from 3GPP2 1xCS to E‑UTRAN direction is not specified in this release.
SRVCC from NG-RAN/E‑UTRAN/UTRAN (HSPA) access and 3GPP UTRAN/GERAN CS accesses for voice calls that are anchored in the IMS, as well as the coordination between the SRVCC for voice call and the handover of non‑voice PS bearers are covered in this specification. SRVCC with IMS emergency call continuity from E-UTRAN/UTRAN (HSPA) to 3GPP UTRAN/GERAN CS accesses and from NG-RAN to UTRAN for voice calls is covered in this specification. SRVCC with eCall over IMS continuity from E-UTRAN/UTRAN (HSPA) to 3GPP UTRAN/GERAN CS accesses is covered in this specification. SRVCC with priority handling from E-UTRAN to 3GPP UTRAN/GERAN CS accesses for voice or voice and video calls is also covered in this specification. The handover of non‑voice PS bearer from E-UTRAN is specified by the procedures defined in TS 23.401 [2], TS 23.060 [10], TS 25.413 [11] and TS 43.129 [12]. The handover of non-voice PS bearer from UTRAN (HSPA) is specified by the procedures defined in TS 23.060 [10], TS 25.413 [11] and TS 43.129 [12]. The handover of non-voice PS bearer from NG-RAN to UTRAN is not supported.
This document specifies the architecture enhancements for Single Radio Video Call Continuity (vSRVCC) from E-UTRAN to UTRAN-CS access for Video Calls that are anchored in the IMS. |
23.218 | IP Multimedia (IM) session handling; IM call model; Stage 2 | TS | 18.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.218/23218-i00.zip | The present document specifies the IP Multimedia (IM) Call Model for handling of an IP multimedia session origination and termination for an IP Multimedia subscriber.
The present document includes interactions between an Application Server and IP multimedia sessions.
The IP Multimedia (IM) Subsystem stage 2 is specified in 3GPP TS 23.228 [3]. |
23.221 | Architectural requirements | TS | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.221/23221-i00.zip | This document covers the architectural requirements for 3GPP systems based on UTRAN, E-UTRAN and Iu mode GERAN. 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. The reference model to which these procedures apply can be found within TS 23.002 [1]. 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 TS 23.060 [2], TS 23.401 [27] and the requirements for the Bearer Independent CS Core Network are contained in TS 23.205[14]. |
23.222 | Common API Framework for 3GPP Northbound APIs | TS | 18.8.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.222/23222-i80.zip | |
23.226 | Global text telephony (GTT); Stage 2 | TS | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.226/23226-i00.zip | This 3GPP Technical Specification defines the stage 2 description of the real time Text Conversation Feature called Global Text Telephony, GTT. GTT Stage 2 identifies the functional capabilities needed to support the service described in GTT Stage 1.
This TS contains the core functions for a real time Text Conversation Feature GTT, to be used in combination with other media in conversational services.
GTT offers real time conversation in text, to be used alone or in combination with other conversational media, and interworking with current and emerging text conversation features in the fixed networks and other mobile networks.
GTT uses a number of functional entities to realise the requirements of the stage 1 description (TS 22.226 [3]). This TS describes how the service requirements are realised with these functional entities. As far as possible existing protocols shall be used for the realisation of the Global Text Telephony Feature. This may include e.g. , SIP, 3G.324, or Circuit Switched Voice service as protocol environments, and CTM, AL1 and RTP/text as transmission protocols. It also means usage of existing text presentation format ITU‑T Recommendation T.140 [5], common to all GTT text conversation environments. |
23.228 | IP Multimedia Subsystem (IMS); Stage 2 | TS | 18.10.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.228/23228-ia0.zip | |
23.231 | SIP-I based circuit-switched core network; Stage 2 | TS | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.231/23231-i00.zip | The present document defines the stage 2 description for the SIP-I based CS core network. The logical architecture for the SIP-I based CS core network is defined in 3GPP TS 23.205 [7].
This stage 2 shall cover the information flows between the GMSC server, MSC server and media gateways that are required to support a SIP-I based Nc interface. 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 and A interfaces 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 Nc interface profile is based on ITU-T Q.1912.5 [9] SIP-I profile C and is specified in 3GPP TS 29.231 [4]. The Mc interface profile is based on ITU-T H.248.1 [5] and is specified in 3GPP TS 29.232 [8].
Local Call Local Switch (LCLS) functionality is further specified in 3GPP TS 23.284 [31].
The present document is applicable only for IP transport in the CS core network.
Details of Transcoder-Free Operation/Out of Band Transcoder Control are outside the scope of the present document. See 3GPP TS 23.153 [3] for more information.
The present document specifies functions, procedures and information which apply to GERAN Iu mode. However, functionality related to GERAN Iu mode is neither maintained nor enhanced. |
23.236 | Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes | TS | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.236/23236-i00.zip | This document covers the details for the Intra Domain Connection of RAN Nodes to Multiple CN Nodes for GERAN and UTRAN based systems. In particular, it details the impacts to GSM and UMTS systems and the stage 2 procedures for the support of connecting a RNC or BSC to multiple MSC servers or SGSNs. The overall solution is described, and the detailed impacts on the existing specifications are identified. The description of a broadly similar concept for E-UTRAN based systems is not described in the document: instead, it is described in TS 23.401 [22].
NOTE: The specified solution impacts RAN nodes. In case an upgrade of radio networks is not performed, the solutions for deploying NNSF functionality above RAN nodes described in TR 23.924 [23] may be used as a guideline for connecting RAN nodes to multiple MSC servers.
The reference model to which these procedures apply can be found within TS 23.002 [1]. 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 TS 23.060 [2] and the requirements for the Bearer Independent CS Core Network are contained in TS 23.205 [14]. |
23.237 | IP Multimedia Subsystem (IMS) Service Continuity; Stage 2 | TS | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.237/23237-i00.zip | The present document specifies the architectural requirements and procedures for delivery of IMS Service Continuity.
TS 23.206 [3] is migrated to this specification.
The scope of the specification includes:
- Access Transfer related functionality:
- PS-CS Access Transfer;
- PS-PS Access Transfer;
- PS-PS Access Transfer in conjunction with PS-CS Access Transfer;
- Adding and/or removing media flows to support service;
. MSC Server assisted mid-call feature;
- SRVCC session transfer of IMS emergency session;
- DRVCC session transfer of IMS emergency session.
- Inter‑UE Transfer related functionality:
- Establishment and release of a Collaborative Session;
- Addition of media flows to, modification of media flows in, and release of media flows from a Collaborative Session;
- Transfer of media flows from one UE to another;
- Transfer of the Collaborative Session Control with or without transfer of media flows;
- Transfer of all media flows to a target UE without establishing a Collaborative Session;
- Session discovery;
- Inter-UE Transfer initiated by the target UE or by the SCC AS;
- Replication of media flows by means of Inter-UE Transfer procedures;
- Authorization and other aspects to support Inter-UE Transfer across multiple IMS subscriptions.
The solution is restricted to service continuity using IMS procedures, i.e. mobility mechanisms on the IP-CAN level are not within the scope of this specification. |
23.240 | 3GPP Generic User Profile (GUP); Architecture (Stage 2) | TS | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.240/23240-i00.zip | The present document defines the stage 2 architecture description to the 3GPP Generic User Profile (GUP), which includes the elements necessary to realise the stage 1 requirements in TS 22.240 [1].
The present document includes the GUP reference architecture with descriptions of functional entities, and their interfaces and procedures, as well as the high-level information model for the GUP data. |
23.246 | Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional description | TS | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.246/23246-i00.zip | The present document describes the stage 2 description (architectural solution and functionalities) for the MBMS Bearer Service, which includes, together with MBMS User Services defined in TS 26.346 [7], all the elements necessary to realise the stage 1 requirements in TS 22.146 [2] and TS 22.246 [6]. This document encompasses both GPRS and EPS.
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 TS 26.346 [7] takes precedence over User Service aspects described in this document.
The present document includes information applicable to network operators, service providers and manufacturers. |
23.247 | Architectural enhancements for 5G multicast-broadcast services | TS | 18.8.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.247/23247-i80.zip | |
23.251 | Network sharing; Architecture and functional description | TS | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.251/23251-i00.zip | The present document covers the details of Network Sharing for GERAN, UTRAN and E-UTRAN. It shows how several core network operators can share one radio access network and details the impacts on the network architecture. All UEs shall comply with existing requirements, among them PLMN selection and system information reception. The present document also defines requirements for network-sharing supporting UEs. |
23.255 | Application layer support for Uncrewed Aerial System (UAS); Functional architecture and information flows; | TS | 18.2.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.255/23255-i20.zip | |
23.256 | Support of Uncrewed Aerial Systems (UAS) connectivity, identification and tracking; Stage 2 | TS | 18.4.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.256/23256-i40.zip | |
23.259 | Personal Network Management (PNM); Procedures and information flows; Stage 2 | TS | 18.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.259/23259-i00.zip | The present document provides the procedure details and the information flows for support of Personal Network Management and Personal Area Network, including the PN redirection and PN access control applications enabled by Personal Network Management (PNM). |
23.261 | IP flow mobility and seamless Wireless Local Area Network (WLAN) offload; Stage 2 | TS | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.261/23261-i00.zip | This document specifies the Stage 2 system description for IP flow mobility between a 3GPP and a WLAN. The technical solution is based on the working principles of DSMIPv6 [2] and it is applicable to both the Evolved Packet System and the I-WLAN mobility architecture.
The specification covers the system description of seamless WLAN offload and IP flow mobility between 3GPP and WLAN as well as the respective interactions with the PCC and ANDSF frameworks. The system description for non seamless WLAN offload is covered in 3GPP TS 23.402 [3].
This document specifies also the detailed extensions to S2c [3] and H1 [4] reference points for IP flow mobility. The extensions to the PCC and to the ANDSF framework are specified respectively in 3GPP TS 23.203 [5] and in 3GPP TS 23.402 [3]. |
23.271 | Functional stage 2 description of Location Services (LCS) | TS | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.271/23271-i00.zip | The present document specifies the stage 2 of the LoCation Services (LCS) feature in UMTS, GSM and EPS (for E-UTRAN), which provides the mechanisms to support mobile location services for operators, subscribers and third party service providers.
Location Services in 5GC are restricted to regulatory services and are specified in TS 23.501 [54] and TS 23.502 [55] in this release of the specification. The architecture and signalling procedures in NG-RAN are defined in TS 38.305 [56].
The present document replaces the specifications TS 23.171 (Release 1999) and the system and core network parts of GSM 03.71 (Release 1999). TS 43.059 [16] replaces the radio access network parts of GSM 03.71 (Release 1999).
Location Services may be considered as a network provided enabling technology consisting of standardised service capabilities, which enable the provision of location applications. The application(s) may be service provider specific. The description of the numerous and varied possible location applications which are enabled by this technology are outside the scope of the present document. However, clarifying examples of how the functionality being described may be used to provide specific location services may be included.
This stage 2 service description covers the LCS system functional model for the whole system, the LCS system architecture, state descriptions, message flows, etc. |
23.272 | Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2 | TS | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.272/23272-i00.zip | |
23.273 | 5G System (5GS) Location Services (LCS); Stage 2 | TS | 18.10.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.273/23273-ia0.zip | |
23.278 | Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 4; Stage 2; IM CN Interworking | TS | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.278/23278-i00.zip | The present document specifies the stage 2 description for the Customized Applications for Mobile network Enhanced Logic (CAMEL) feature which provides the mechanisms to support services for the IP Multimedia Core Network (IM CN) Subsystem. |
23.279 | Combining Circuit Switched (CS) and IP Multimedia Subsystem (IMS) services; Stage 2 | TS | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.279/23279-i00.zip | The present document 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.
The present document includes the following capabilities that enable the combination of CS and IMS services:
- Radio capability exchange.
- SIP based UE terminal capability exchange.
- MSISDN number exchange in SIP.
- Establishing an IMS session in parallel to an ongoing CS call between the same two UEs.
- Establishing a CS call in parallel to an ongoing IMS session between the same two users UEs.
- Network support for establishing multimedia sessions between a UE that uses IMS origination and a UE that uses CSI termination.
The individual CS call or IMS service that are combined are described in their respective specifications. |
23.280 | Common functional architecture to support mission critical services; Stage 2 | TS | 18.12.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.280/23280-ic0.zip | |
23.281 | Functional architecture and information flows to support Mission Critical Video (MCVideo); Stage 2 | TS | 18.10.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.281/23281-ia0.zip | |
23.282 | Functional architecture and information flows to support Mission Critical Data (MCData); Stage 2 | TS | 18.11.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.282/23282-ib0.zip | |
23.283 | Mission Critical Communication Interworking with Land Mobile Radio Systems | TS | 18.3.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.283/23283-i30.zip |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.