id
stringlengths 5
12
| title
stringlengths 8
250
| type
stringclasses 2
values | version
stringclasses 222
values | working_group
stringclasses 30
values | url
stringlengths 67
81
| scope
stringlengths 0
65.7k
|
|---|---|---|---|---|---|---|
22.084
|
MultiParty (MPTY) supplementary service; Stage 1
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.084/22084-i01.zip
|
The present document describes the Supplementary Services belonging to the group MultiParty Supplementary Services.
The general aspects, including definitions and recommended provision, of the description of the Supplementary Services are given in TS 22.004.
The group of Supplementary Services MultiParty Supplementary Services consists of one Supplementary Service:
- MultiParty service (Clause 1).
|
22.085
|
Closed User Group (CUG) supplementary services; Stage 1
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.085/22085-i01.zip
|
The present document describes the Supplementary Services belonging to the group Community Of Interest Supplementary Services.
The general aspects, including definitions and recommended provision, of the description of the Supplementary Services are given in TS 22.004.
The group of Community Of Interest Supplementary Services includes one Supplementary Service:
- Closed user group (clause 1).
|
22.086
|
Advice of Charge (AoC) supplementary services; Stage 1
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.086/22086-i01.zip
|
The present document describes the supplementary services belonging to the group Charging Supplementary Services.
The general aspects, including definitions and recommended provision, of the description of the supplementary services are given in TS 22.004 [2].
Charging services are the supplementary services associated with charging aspects. The group of supplementary services Charging Supplementary Services comprises two services:
- Advice of Charge (Information) - clause 1;
- Advice of Charge (Charging) - clause 2.
Advice of Charge (AoC) supplementary services will use the Charge Advice Information described in 22.024 [3].
In principle, the same type of Mobile Station (MS) can be used for both services of Advice of Charge (AoC), except where the application demands special features - e.g. the payment mechanism in a payphone.
Only one of these services may be subscribed to at any one time.
|
22.087
|
User-to-User Signalling (UUS); Service description; Stage 1
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.087/22087-i01.zip
|
The User-to-User Signalling (UUS) supplementary service allows a mobile subscriber to send/receive a limited amount of information to/from another PLMN or ISDN subscriber over the signalling channel in association with a call to the other subscriber.
|
22.088
|
Call Barring (CB) supplementary services; Stage 1
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.088/22088-i01.zip
|
The present document describes the supplementary services belonging to the group Call Restriction Supplementary Services.
The general aspects - including definitions and recommended provision - of the description of the supplementary services are given in 3GPP TS 22.004 [2].
The Call Restriction supplementary services allow the possibility for a mobile subscriber to have barring of certain categories of outgoing or incoming calls at the mobile subscribers access.
The group of Call Restriction Services includes two supplementary services:
- barring of outgoing calls;
- barring of incoming calls.
By use of subscription options, the mobile subscriber can at provision time select a set of one or more barring programs to determine the categories of calls to be barred. The following categories are defined:
- all outgoing calls;
- outgoing international calls;
- outgoing international calls except those directed to the home PLMN country;
- all incoming calls;
- incoming calls when roaming outside the home PLMN country.
NOTE 1: Each category (barring program) is handled as a single supplementary service.
NOTE 2: The call barring program "incoming calls when roaming outside the home PLMN country" 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.
The barring services can be offered to a mobile subscriber with a password option allowing the activation and deactivation by the subscriber. One password per mobile subscriber is supported by the network for all barring services. For the definition of the password, the description of its use and its management, see 3GPP TS 22.004 [2].
|
22.090
|
Unstructured Supplementary Service Data (USSD); Stage 1
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.090/22090-i01.zip
|
The present document defines the stage 1 description of Unstructured Supplementary Service Data (USSD) for use in one or a number of Public Land Mobile Networks (PLMNs).
|
22.091
|
Explicit Call Transfer (ECT) supplementary service; Stage 1
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.091/22091-i01.zip
|
The present document specifies the stage 1 description of Explicit Call Transfer (ECT) from the service subscriber's and user's points of view, in particular:
- the procedures for normal operation with successful outcome;
- the action to be taken in exceptional circumstances;
- the interaction with other supplementary services.
The present document does not deal with the Man-Machine Interface (MMI) requirements, but makes reference to the appropriate Technical Specifications.
The charging principles applied to ECT are established in the present document in terms of the charging information required to be collected. Any subsequent charging implications are outside of the scope of the present document.
Any interactions with other networks not dealt with in Clause 9 are outside the scope of the present document.
|
22.093
|
Completion of Calls to Busy Subscriber (CCBS); Service description, Stage 1
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.093/22093-i01.zip
|
The present document specifies the stage 1 description of Completion of Calls to Busy Subscriber (CCBS) from the subscriber's and user's points of view; in particular:
- the procedures for normal operation with successful outcome;
- the action to be taken in exceptional circumstances;
- the interaction with other supplementary services;
The present document does not deal with the Man-Machine Interface (MMI) requirements, but makes reference to the appropriate specifications.
The charging principles applied to CCBS are outside of the scope of this specifcation.
Any interactions with other networks not dealt with in the present document are outside the scope of the present document.
|
22.094
|
Follow Me service description; Stage 1
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.094/22094-i01.zip
|
The present document specifies the stage 1 description for the Follow Me feature.
The Follow Me feature enables a mobile subscriber A to manipulate the Follow Me data of a party B in such a way that - under certain conditions - subsequent calls directed to party B will be forwarded to subscriber A.
The feature is described from the service subscriber's and user's point of view, in particular:
‑ the procedure for normal operation with successful outcome;
‑ the action to be taken in exceptional circumstances;
‑ the interaction with other GSM services and features.
This TS does not deal with the Man‑Machine Interface (MMI) requirements, but makes reference to the appropriate specifications.
Any interaction with other services and/or networks not dealt with in this specification are outside the scope of this TS.
|
22.096
|
Name identification supplementary services; Stage 1
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.096/22096-i01.zip
|
The present document describes the supplementary services belonging to the group Name Identification supplementary services.
The general aspects, including definitions and recommended provision, of the description of the supplementary services are given in TS 22.004 [2].
The group of Name Identification supplementary services is divided into the following supplementary services:
CNAP Calling Name Presentation (clause 4).
|
22.097
|
Multiple Subscriber Profile (MSP) Phase 2; Service description; Stage 1
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.097/22097-i01.zip
|
The present document gives an overall view of how this service shall operate both in the PLMN and within the Mobile Station (MS). This TS defines functionality and is not intended to constrain implementation.
|
22.105
|
Services and service capabilities
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.105/22105-i01.zip
|
Existing systems have largely standardised the complete sets of bearer services, teleservices and supplementary services which they provide. 3GPP specifications specify service capabilities rather than services, allowing service differentiation and system continuity. This Technical Specification (TS) describes how and what kind of services the user has access to.
|
22.119
|
Maritime communication services over 3GPP system
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.119/22119-i01.zip
|
The present document describes service requirements to enable maritime communication services to be supported over a 3GPP system. Requirements for MC services applicable to general maritime usage are specified in 3GPP Technical Specifications dedicated to MC services [2], [3], [4], [5].
Requirements in the present document are specific to maritime usage.
|
22.129
|
Service aspects; Handover requirements between UTRAN and GERAN or other radio systems
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.129/22129-i01.zip
|
The scope of this document includes service requirements for handover maintaining continuity of service to a wireless terminal as it moves between the radio coverage area, or "cells", associated with different base station sites. This functionality is called "handover". Handover can also occur due to change of radio resource providing a service without necessarily any change of the base stations involved. In particular, when the radio resources providing a service change from one of the UTRA radio access modes to the other (UTRA-FDD and UTRA-TDD), this is regarded as handover. Particular emphasis has been placed on the description of requirements for service continuity within UTRAN and between UTRAN and GERAN.
It is a key requirement to allow for dual or multi-mode terminals to handover traffic from UTRAN to GERAN and vice versa. This document describes the service requirements for intra- and inter- system handover.
The following subject areas are within the scope of these service requirements:
- User perceived performance that may be influenced by handover;
- Operational requirements relating to handover;
- Security requirements.
The requirements set forth in this document are service requirements, in that they fulfil the following:
- The requirements are independent of the implementation of the UTRAN;
- The extent to which the requirements are met are in principle verifiable using observables that are not internal to the UTRAN.
|
22.135
|
Multicall; Service description; Stage 1
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.135/22135-i01.zip
|
The present document presents describes Multicall supplementary service.
The general aspects, including definitions and recommended provision, of the description of the 3GPP Supplementary Services are given in 3GPP TS 22.004.
|
22.140
|
Multimedia Messaging Service (MMS); Stage 1
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.140/22140-i01.zip
|
This Technical Specification defines the stage one description of the non real-time Multimedia Messaging Service, MMS. Stage one is the set of requirements which shall be supported for the provision of non real-time multimedia messaging service, seen primarily from the subscriber’s and service providers’ points of view.
This TS includes information applicable to network operators, service providers, terminal and network manufacturers.
This TS contains the core requirements for the Multimedia Messaging Service, which are sufficient to provide a complete service.
This TS defines the requirements for MMS to be understood as a framework to enable non real-time transmissions for different types of media including such functionality as:
- multiple media elements per single message
- individual handling of message elements
- different delivery methods for each message element
- negotiate different terminal and network MM capabilities
- notification and acknowledgement of MM related events (e.g. delivery, deletion, ...)
- handling of undeliverable MM
- personalised MMS configuration
- flexible charging
The above list is not exhaustive.
Thus the MMS enables a unified application which integrates the composition, storage, access, and delivery of different kinds of media, e.g. text, voice, image or video in combination with additional mobile requirements.
|
22.141
|
Presence service; Stage 1
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.141/22141-i01.zip
|
This TS defines the stage one description for the presence service. Stage one is the set of requirements which shall be supported to enable the exploitation of the presence service, seen primarily from the users' and home environments’ points of view.
This TS includes information applicable to the home environment, device and network manufacturers which are sufficient to provide complete support of the presence service.
Additional functionalities not documented in this TS are considered outside the scope of this TS. Such additional functionality may be on a network-wide basis, nation-wide basis or particular to a group of users. Such additional functionality shall not compromise conformance to the requirements of the presence service defined in this specification.
|
22.142
|
Value Added Services (VAS) for Short Message Service (SMS) requirements
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.142/22142-i01.zip
|
The present document specifies the service requirements associated with series of value-added features for short message service (SMS). Specifically, the objective of this document is to specify potential new value-added services for SMS in 3GPP that need to be standardized.
|
22.146
|
Multimedia Broadcast/Multicast Service (MBMS); Stage 1
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.146/22146-i01.zip
|
This Technical specification defines the stage one description of the Broadcast and Multicast Services for the 3GPP System. Stage one is the set of requirements which shall be supported for the provision of Broadcast and Multicast services, seen primarily from the subscriber’s and service providers’ points of view.
Note: Non-3GPP access systems may provide MBMS transport service, but this is not in the scope of this specification.
This TS includes information applicable to network operators, content providers, and terminal and network manufacturers.
This TS contains the core requirements for Multicast and Broadcast Services, which are sufficient to provide a complete service.
|
22.173
|
IP Multimedia Core Network Subsystem (IMS) Multimedia Telephony Service and supplementary services; Stage 1
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.173/22173-i01.zip
|
The present document define the IMS Multimedia Telephony service and the minimum set of capabilities required to secure multi-vendor and multi-operator inter-operability for Multimedia Telephony and related Supplementary Services.
|
22.174
|
Push Service; Service aspects; Stage 1
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.174/22174-i01.zip
|
This Technical Specification defines the Stage 1 description of the Push Service and is the set of requirements that shall be supported for the provision of push, seen primarily from the subscriber’s, service providers’ and delivery network points of view.
This TS includes information applicable to network operators, service providers, terminal and network manufacturers. It is of use to manufacturers and organisations which have devices or machines benefiting by availability of push service.
This TS contains the core requirements for the Push Service, for operator and external Push Initiators, which are sufficient to provide a complete service capability and service capability feature.
This TS defines the requirements for the Push Service to enable delivery of push data, including such functionality as:
• Transfer of push data from a Push Initiator to a Push Recipient
• Latency and Priority classes,
• Definition of handling of undeliverable push data.
|
22.182
|
Customized Alerting Tones (CAT) requirements; Stage 1
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.182/22182-i01.zip
|
The present document specifies the requirements and technical considerations for Customized Alerting Tone (CAT) service in both CS and PS domains, especially additional features for roaming and interoperability support.
This document considers voice and multi-media CAT, so the CAT user may experience favourable songs, multi-media clips or other customized alerting tones.
|
22.183
|
Customized Ringing Signal (CRS) requirements; Stage 1
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.183/22183-i01.zip
|
The document specifies the requirements and technical considerations for Customized Ringing Signal (CRS) service in the PS and CS domains, especially additional features for roaming and interoperability support.
This document considers voice and multi-media CRS, so the CRS user may experience favourable songs, multi-media clips or other customized CRS.
This document specifies the CRS filtering service requirements that allow the user to filter the CRS.
|
22.185
|
Service requirements for V2X services
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.185/22185-i01.zip
|
The present document provides 3GPP support for V2X service requirements to be supported by LTE transport. These requirements are identified by taking into account the V2X service requirements defined in other SDOs, e.g. ETSI ITS, US SAE. The specification includes requirements of safety and non-safety aspects.
|
22.186
|
Service requirements for enhanced V2X scenarios
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.186/22186-i01.zip
|
The present document specifies service requirements to enhance 3GPP support for V2X scenarios in the 3GPP systems (i.e. EPS, 5G).
It includes transport layer support for both safety and non-safety V2X scenarios:
- Safety-related V2X scenarios: e.g. automated driving, vehicle platooning
- Non-safety-related V2X scenarios: e.g., mobile high data rate entertainment, mobile hotspot/office/home, dynamic digital map update
|
22.220
|
Service requirements for Home Node B (HNB) and Home eNode B (HeNB)
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.220/22220-i01.zip
|
This specification defines the service requirements for the basic functionalities for the support of Home NodeB (HNB) and Home eNodeB (HeNB) – jointly referred to as H(e)NB – and the further functionalities that will enable the mobile operators to provide more advanced services as well as improving the user experience.
|
22.226
|
Global Text Telephony (GTT); Stage 1
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.226/22226-i01.zip
|
This Technical Specification defines the stage one description of the Global Text Telephone Feature, GTT.. Stage one is the set of requirements which shall be supported for the provision of the real-time text conversation feature, seen primarily from the subscriber’s and service providers’ points of view.
This TS includes information applicable to network operators, service providers, terminal and network manufacturers.
This TS contains the core requirements for the Global Text Telephony feature, which are sufficient to provide a complete feature to incorporate in conversational services.
This TS defines the requirements for GTT to be understood as a framework to enable real-time transmission of text, for the purpose of a text based or text supported conversation between users. Text may be transported alone or in combination with other media in the session, especially video and voice.
Thus the GTT enables text conversation to be included in any mobile conversational service.
Interworking with existing text telephony in PSTN as well as emerging forms of standardised text conversation in all networks is within the scope of this document. Interoperation with Multimedia Messaging Services is also within scope of this feature.
Note: The Global Text Telephony feature may be enhanced due to e.g. operator's or regulator's requirements, however such additional functionality shall not compromise conformance to the core requirements documented in this TS.
|
22.228
|
Service requirements for the Internet Protocol (IP) multimedia core network subsystem (IMS); Stage 1
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.228/22228-i01.zip
|
This TS defines the service requirements from users’ and operators’ perspective for the support of IP multimedia applications through the IMS.
IP multimedia applications are supported by IP multimedia sessions in the IM CN Subsystem. IP multimedia sessions use IP connectivity bearers (e.g. GPRS as a bearer). Examples of IP multimedia applications include speech communication, real time multimedia applications, shared online whiteboards etc.
This TS, in general, does not standardise usage of IP multimedia applications, but instead identifies the requirements to enable their support.
In order to align IP multimedia applications wherever possible with non-3GPP IP applications, the general approach is to adopt non-3GPP IP based solutions.
The existing legacy tele- and supplementary services shall not be re-standardised as IP multimedia applications, and multimedia equivalent applications may be created with toolkits.
|
22.233
|
Transparent end-to-end packet-switched streaming service; Stage 1
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.233/22233-i01.zip
|
This Technical Specification defines the stage one description of the Packet-switched Streaming Service (PSS). Stage one is the set of requirements that shall be supported for the provision of a streaming service, seen primarily from the user’s and service providers’ points of view but also includes the service capabilities of the PSS itself
This TS includes information applicable to network operators, service providers, terminal and network manufacturers.
This TS contains the core requirements for the Packet-switched Streaming Service (PSS), which are sufficient to enable a range of services.
|
22.240
|
Service requirements for 3GPP Generic User Profile (GUP); Stage 1
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.240/22240-i01.zip
| |
22.242
|
Digital Rights Management (DRM); Stage 1
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.242/22242-i01.zip
| |
22.243
|
Speech recognition framework for automated voice services; Stage 1
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.243/22243-i01.zip
|
The present document defines the stage one description of the Speech Recognition Framework for Automated Voice Services. Stage One is the set of requirements for data seen primarily from the user’s and service providers’ points of view.
This Technical Specification includes information applicable to network operators, service providers, terminal and network manufacturers.
This Technical Specification contains the core requirements for the Speech Recognition Framework for automated voice services.
The scope of this Stage 1 is to identify the requirements for 3G networks to support the deployments of a speech recognition framework - based automated voice services and therefore to introduce a 3GPP speech recognition framework as part of speech-enabled services. The Speech Recognition Framework for automated voice services is an optional feature in a 3GPP system.
Figure 1 positions the Speech recognition Framework (SRF) with respect to other speech-enabled services as discussed in [6]. As illustrated, SRF is designed to support server-side speech recognition over packet switched network (e.g. IMS). As such SRF also enable configurations of multimodal and multi-device services that include distribute the speech engines.
Note that it is possible to design speech-enabled services that alternate or combine the use of client-side only engines and SRF.
Figure 1 - Positions the scope of the speech recognition framework as part of general speech enabled services.
|
22.246
|
Multimedia Broadcast/Multicast Service (MBMS) user services; Stage 1
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.246/22246-i01.zip
|
The present document describes MBMS User Services that use the capabilities of MBMS. Application scenarios including charging, QoS aspects and related service requirements derived from them are described. These scenarios and service requirements can be used as guidance for the design of codecs and bearers.
|
22.250
|
IP Multimedia Subsystem (IMS) Group Management; Stage 1
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.250/22250-i01.zip
|
The present document defines the stage one description of the IMS group management. Stage one is the set of requirements which shall be supported for the provision of IMS group management, seen primarily from the subscribers' and service providers' points of view.
The TS includes information applicable to network operator, service provider, terminal and network manufacturer.
Additional functionalities not documented in the TS are considered outside the scope of this TS. Such additional functionality may be on a network-wide basis, nation-wide basis or particular to a group of users. Such additional functionality shall not compromise conformance to the requirements of the IMS group management defined in this specification.
|
22.259
|
Service requirements for Personal Network Management (PNM); Stage 1
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.259/22259-i01.zip
|
The present document describes the service requirements for the Personal Network Management (PNM). Aspects of data synchronisation and management of user data are out of scope.
|
22.262
|
Message service within the 5G System (5GS); Stage 1
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.262/22262-i01.zip
|
The present document provides the service requirements for operation of the MSGin5G Service. The MSGin5G Service provides point-to-point, application-to-point, group and broadcast message delivery for person-to-thing communication and thing-to-thing communication.
|
22.263
|
Service requirements for Video, Imaging and Audio for Professional Applications (VIAPA)
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.263/22263-i01.zip
|
This document describes the service and performance requirements for the operation of professional video, audio and imaging via a 5G system, including a UE, NG-RAN and 5G Core network.
The aspects addressed in this document include:
- Network service requirements specific for the operation of professional video, imaging and audio for PLMN and non-public networks (NPN)
- New key performance indicators (KPIs) for PLMN and NPN
- KPIs for Multicast and Broadcast Services
- Network Exposure Requirements
- Clock synchronisation
- Application Specific Requirements for video, imaging and audio
- Mobile and airborne base stations for NPNs
- Service continuity
|
22.278
|
Service requirements for the Evolved Packet System (EPS)
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.278/22278-i01.zip
|
The present document describes the service requirements for the Evolved Packet System. Requirements for 5G E-UTRA-NR Dual Connectivity in E-UTRAN connected to EPC, are included in this document.
|
22.279
|
Combined Circuit Switched (CS) and IP Multimedia Subsystem (IMS) sessions; Stage 1
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.279/22279-i01.zip
|
The present document specifies service requirements for Combining CS and IMS services using a CS speech or CS multimedia call in association with an IMS session. The IMS session may consist of one or more IMS services.
Requirements for the following capabilities are included:
- Radio capability exchange.
- Terminal capability exchange.
- E.164 number exchange.
- Adding IMS session to an ongoing CS call.
- Adding a CS call to an ongoing IMS session.
- Supplementary services as they relate to CSICS.
It is intended that the capabilities defined herein for CSICS shall support interoperability between different operator networks, and roaming.
|
22.281
|
Mission Critical (MC) video
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.281/22281-i01.zip
|
The present document provides the service requirements for operation of the MCVideo service. MCVideo makes use of capabilities included in Group Communication System Enablers, Proximity Services, Isolated E‑UTRAN operation for Public Safety and Mission Critical Services Common Requirements with additional requirements specific to the MCVideo Service. The MCVideo Service can be used for public safety applications and maritime safety applications and also for general commercial applications (e.g. utility companies, railways and maritime usage). The requirements in this specifications do not apply to GSM or UMTS.
|
22.282
|
Mission Critical (MC) data
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.282/22282-i01.zip
|
The present document provides the service requirements for operation of the MCData service. MCData makes use of capabilities included in Group Communication System Enablers, Proximity Services, Isolated E-UTRAN operation for Public Safety and Mission Critical Services Common Requirements with additional requirements specific to the MCData Service. The MCData Service can be used for public safety applications and maritime safety applications and also for general commercial applications (e.g., utility companies, railways and maritime usage). The requirements in this specifications do not apply to GSM or UMTS.
|
22.289
|
Mobile communication system for railways
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.289/22289-i01.zip
|
The present document provides rail communication Stage 1 normative service requirements for 5G system. Rail communication includes main line and rail-bound mass transit. Communication for main line is based on the set of Mission Critical specification [1], [2], [3], [4]. Several service requirements for rail-bound mass transit are based on the methodology of cyber-physical control applications [7]. Requirements which are not in the scope of those specifications are provided in this Technical Specification.
|
22.340
|
IP Multimedia Subsystem (IMS) messaging; Stage 1
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.340/22340-i01.zip
|
The present document specifies the stage one description of the IMS Messaging services. Stage one is an overall service description and defines service requirements, primarily from the subscriber's and service providers' points of view, and does not deal with the details of the human interface itself.
The present TS includes information applicable to network operators, service providers and terminal, switch and database manufacturers.
The present TS contains the requirements for IMS Messaging services, which are sufficient to provide a complete service. The messaging types identified in this document are: immediate messaging and session based messaging.
It is highly desirable that technical solutions for IMS Messaging services should be sufficiently flexible to allow for possible enhancements. Additional functionalities not documented in this 3GPP TS may implement requirements which are considered outside the scope of this 3GPP TS. Such additional functionality shall not compromise conformance to the core requirements of the service.
|
22.346
|
Isolated Evolved Universal Terrestrial Radio Access Network (E-UTRAN) operation for public safety; Stage 1
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.346/22346-i01.zip
|
The present document specifies the service requirements for Isolated E-UTRAN Operation in support of mission critical network operation for Public Safety. In particular, requirements are specified for:
- Initiation of Isolated E-UTRAN operation.
- Ongoing Isolated E-UTRAN operation.
- Termination of Isolated E-UTRAN operation.
- Security aspects of Isolated E-UTRAN operation.
|
22.368
|
Service requirements for Machine-Type Communications (MTC); Stage 1
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.368/22368-i01.zip
|
The present document specifies the service requirements for Network Improvements for Machine Type Communications. In particular it will:
- identify and specify general requirements for machine type communications;
- identify service aspects where network improvements (compared to the current human-to-human oriented services) are needed to cater for the specific nature of machine-type communications;
- specify machine type communication requirements for these service aspects where network improvements are needed for machine type communication.
|
22.468
|
Group Communication System Enablers (GCSE)
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.468/22468-i01.zip
|
The present document collects the requirements as relevant to improve the 3GPP system to support Group Communication for Public Safety and Critical Communication and other services.
For Public Safety and Critical Communication Services, US requirements as specified in NPSTC (Mission Critical Voice Requirements) [2], [3], [4], the TETRA + Critical Communications Association (TCCA) [8] and ITU [6], [7] inputs are taken as starting point.
Other regional requirements may also be reflected in the work. The requirements are worded in a way to easily accommodate future requirements from other regions or stakeholders.
Other services have corresponding regulatory and service justification.
|
22.519
|
Business communication requirements
|
TS
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.519/22519-i01.zip
|
The present document specifies network requirements:
- to support connection and interoperation of business communication capabilities (either hosted in NGCN or NGN) to the NGN; and
- to support connection and interoperation of business communication capabilities to other business communication capabilities (either hosted in NGCN or NGN); and
- to support connection and interoperation of business communication capabilities to other business communication capabilities located in or connected to the ISDN and PSTN; and
- to support PABX functionality (hosted enterprise services) in an NGN.
NOTE 1: Network requirements to support connection of NGCN directly connected to an NGN are specified.
NOTE 2: Attachment of legacy PBX functionality to the NGN is not specified in the present document. It is assumed that existing legacy service requirements apply in this case.
The present document also specifies network requirements for communication between NGCN capabilities (including user equipment) to other NGCN capabilities of the same enterprise through the NGN (e.g. geographically separated).
The present document does not specify NGCN services, nor does it specify network based application services provided to a user of an NGCN.
|
22.835
|
Study on enhanced access to and support of network slices
|
TR
|
18.2.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.835/22835-i20.zip
|
The present document studies various use cases and scenarios using network slices, in order to identify potential service requirements for the 5G system, e.g.:
- when there is a restriction of network slice to e.g., certain frequency bands/sub bands, RATs, geographical areas, networks and applications,
- when a UE has a subscription to multiple network slices and these network slices are deployed for e.g., different frequency bands/sub bands, RATs, geographical area and applications,
- when there is a preference or prioritization for a network slice over other network slices e.g. when there are conflicting constraints on network slice availability.
The present document also includes a gap analysis of its derived potential requirements versus existing 3GPP requirements.
|
22.839
|
Study on vehicle-mounted relays
|
TR
|
18.1.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.839/22839-i10.zip
|
The present document is the outcome of the study on use cases and potential new requirements for 5GS support of mobile base station relays mounted on vehicles, using 5G NR over the radio links toward UEs and macro RAN (connected to 5GC). This study covers aspects related to:
• Vehicle base station relays providing service to UEs inside the vehicle or in the vicinity of the vehicle;
• End-to-end service continuity during mobility scenarios (including mobility of the relays);
• Provisioning, policies and control, e.g. for
◦ Provisioning of spectrum used by the relays, geographic area restrictions;
◦ Control of relay operation, UEs access and connectivity via relays.
• Aspects related to roaming of relays, security, regulatory requirements (e.g. for emergency services), charging, spectrum interference.
• Gap analysis between the identified requirements and existing 5GS requirements or functionalities.
|
22.844
|
Study on 5G Networks Providing Access to Localized Services
|
TR
|
18.2.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.844/22844-i20.zip
|
The present document intends to capture the outcome of the study on use cases and potential new requirements for 5G networks providing access to localized services. The study aims to cover:
• use cases for enhanced 5G system support of a hosting network providing users/devices access to specific services, offered by the hosting network operator, other mobile operator(s) or 3rd party provider(s). Including scenarios where:
◦ Access to services through the hosting network could be on demand, temporary and/or cover specific location(s);
◦ The operator of the hosting network, or other mobile operator offering services to users, can be a PLMN or NPN operator;
◦ Different RATs (3GPP or non-3GPP) and spectrum (licensed or unlicensed) could be considered;
◦ The hosting network can also provide specific network services, e.g., location-based service, time synchronization etc.
• Investigate potential new service requirements, including:
◦ Enabling users/UEs to discover availability of specific target networks and specific services through a hosting network;
◦ Network functionalities to negotiate and configure access and requirements for a specific service (e.g., QoS, network slicing, charging, onboarding etc.);
▪ Can include policy management, service/QoS monitoring, and interaction between the hosting network and other mobile operator or 3rd party (offering the service) e.g., via API or other standard mechanisms
◦ Enabling users/UEs to concurrently use specific target services offered through a hosting network and the regular services offered by the HPLMN of the user/UE;
◦ Enabling access to the hosting network and specific services for users/UEs without previous relationship with the hosting network;
◦ Consideration of regulatory and security aspects.
• Gap analysis between potential new requirements and existing requirements and functionalities supported by 3GPP, e.g., VIAPA, NPN, slicing, QoS, etc.
|
22.847
|
Study on supporting tactile and multi-modality communication services
|
TR
|
18.2.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.847/22847-i20.zip
|
This present document provides stage 1 use cases and potential 5G requirements on supporting tactile and multi-modal communication services. In the context of the present document, the aspects addressed include:
1) Study new scenarios and identify use cases and potential requirements for immersive real time experience involving tactile and multi-modal interactions, including:
a) Network assistance for coordinated transmission of multiple modal representations associated with the same session,
b) aspects of charging, security and privacy, and
c) KPIs (including network reliability and availability).
2) Gap analysis with existing requirements and functionalities on supporting tactile and multi-modal communication services.
|
22.855
|
Study on ranging-based services
|
TR
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.855/22855-i01.zip
|
The present document provides Stage 1 potential 5G service requirements for ranging based services. In the context of the present document, Ranging-based services are to be understood as the applications utilizing the distance between two UEs and/or the direction of one UE from the other one.
The aspects addressed in the present document include:
- Identify Use cases and potential requirements of ranging-based services directly between two or more UEs, e.g. accuracy of distance and direction, maximum range distance, ranging latency, energy/battery consumption.
- Gap analysis with existing mechanisms to enable ranging-based services.
NOTE: the study does not intend to address V2X specific use cases and requirements.
|
22.858
|
Study on enhancements for residential 5G
|
TR
|
18.2.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.858/22858-i20.zip
|
The present document examines use cases and traffic scenarios in residential environments (e.g. homes and small offices) and identifies related new potential functional requirements and potential key performance requirements in the following three areas:
- Enhancements for wireline wireless convergence,
- Enhancements for fixed LAN - 5GLAN integration, and
- Enhancements for indoor small base stations
|
22.859
|
Study on Personal Internet of Things (PIoT) networks
|
TR
|
18.2.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.859/22859-i20.zip
|
The present document is aiming at documenting potential new use cases and service requirements to enhance 5GS for the support of Personal IoT networks (PINs), including when the PIN is connected to 5GC.
|
22.867
|
Study on 5G smart energy and infrastructure
|
TR
|
18.2.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.867/22867-i20.zip
|
The present document is to address study use cases, potential new service requirements for 5G system to support Smart Grid including the following topics:
• Smart Grid services, e.g. IEC standards, and their communications requirements including capacity, latency, availability, end-to-end QoS, resilience/redundancy and security.
• Deployment requirements when considering constraints e.g. service lifetime, coverage (ubiquity), electromagnetic applicability (e.g. penetration, ability to operate in high EM environments,) etc.
• Additional requirements due to operational manageability – e.g. the ability to configure and monitor the real (achieved & up to date) availability of virtual network topologies
• New Smart Grid use cases and potential service function requirements: e.g. on-demand power supply, distributed power supply system, distribution automation, higher accuracy power load measurement and control, meter automation, etc.
• Communication KPI and service requirements for enabling microgrids, DER and specifically distributed generation (DG) that require 5G wireless communication (e.g. wind and solar energy generation, including scenarios at or near residential / consumer premises, etc.)
|
22.873
|
Study on evolution of the IP Multimedia Subsystem (IMS) multimedia telephony service
|
TR
|
18.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.873/22873-i00.zip
|
The present document studies new scenarios (e.g. AR/VR communication) for IMS Multimedia Telephony service, identifies potential service requirements, and identifies additional potential requirements on 5G system.
This document also does a gap analysis to existing requirements in 3GPP to identify potential requirements for introduction into 3GPP.
NOTE: Use cases in this document have references to those already specified in 3GPP TR26.918 [2] and TR26.928[3]. This allows an easier breakdown of these use cases to existing features and potential new requirements as well as relevant performance figures. New use cases in this TR are highlighted if they are not covered in 3GPP SA4 work.
|
22.874
|
5G System (5GS); Study on traffic characteristics and performance requirements for AI/ML model transfer
|
TR
|
18.2.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.874/22874-i20.zip
|
This report captures the study of the use cases and the potential performance requirements for 5G system support of Artificial Intelligence (AI)/Machine Learning (ML) model distribution and transfer (download, upload, updates, etc.), and identifies traffic characteristics of AI/ML model distribution, transfer and training for various applications, e.g. video/speech recognition, robot control, automotive, other verticals.
The aspects addressed include:
• AI/ML operation splitting between AI/ML endpoints;
• AI/ML model/data distribution and sharing over 5G system;
• Distributed/Federated Learning over 5G system.
Study of the AI/ML models themselves are not in the scope of the TR.
|
22.878
|
Study on 5G timing resiliency system
|
TR
|
18.2.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.878/22878-i20.zip
|
The present document identifies additional potential requirements on the 5G system to support time-synchronization services in public and vertical domains, including both the ability to improve resiliency of timing services involving technologies supported by 5G and the ability to the ability to act as a backup for GNSS timing services.
The use cases address:
• the use of 5G system in concert with other timing technologies as a resilient timing source for end-users in complement/back-up/alternate to GNSS, and
• enhancement to the 5G system to enable time synchronization resiliency if GNSS or other timing services are compromised.
|
22.881
|
Study on sharing administrative configuration information between interconnected Mission Critical (MCX) service systems
|
TR
|
18.1.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.881/22881-i10.zip
|
The present document studies use cases that assess under which circumstances interconnected MCX Service Systems exchange administrative and security relevant data and information.
Its objective is to identify new potential requirements related to the use cases and new high-level security requirements related to interconnection of MCX Service Systems and migration of MCX Users and MCX Service Groups.
|
22.903
|
Study on Videotelephony teleservice
|
TR
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.903/22903-i01.zip
|
The present document intends to analyse the introduction of additional functionalities for the videotelephony service in addition to what is provided in the 3GPP specifications up to Release 6. The functionalities will include but are not limited to codec negotiation, charging principles, supplementary services support. The approach followed is to evaluate how functionalities which are applicable to existing teleservices can be replicated for videotelephony.
The document will analyse how the new functionalities will impact the backwards compatibility with the existing CS multimedia service and will whether it is beneficial to create a videotelephony teleservice.
|
22.904
|
Study on user-centric identifiers and authentication
|
TR
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.904/22904-i01.zip
|
The present document aims to study the introduction of an optional, user-centric authentication layer on top of the existing subscription authentication, supporting various authentication mechanisms and interactions with external authentication systems as well as a degree of confidence (i.e. a value that allows differentiated service policies depending on the reliability of the User Identifier).
The new authentication layer shall not replace existing subscription credentials. The security and privacy of subscriber or end user data shall not be compromised.
Use cases are developed and potential requirements derived how to use the new User Identifier within the 3GPP system e.g. to provide customized services and enhanced charging and how to provide this identifier to external entities to enable authentication for systems and services outside 3GPP.
Use cases for use within 3GPP include
- providing different users using the same UE with customized services
- identifying users of devices behind a gateway with a 3GPP subscription, but without the devices having a dedicated 3GPP subscription
- using a User Identifier being linked to a subscription to access 3GPP services via non-3GPP access
- using a User Identifier for slice authorization.
|
22.906
|
Study on IMS based peer-to-peer content distribution services
|
TR
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.906/22906-i01.zip
|
This Technical Report presents the overview, use cases and other aspects (e.g. Mobility, Charging, Security and etc.) of IMS based Peer-to-Peer Content Distribution Services. And the potential service requirements will be identified. The objectives are to study IMS based content distribution services with the following aspects:
• Identifying the user cases to describe how users, operators and service providers will may benefit by using/deploying IMS based content distribution services in fixed and mobile convergence networks with Peer-to-Peer technology;
• Identifying service aspects where IMS network improvements are needed to cater for content distributed services for above accesses;
• Identifying mobility, charging and security related requirements in the case of content distribution services on IMS;
• Identifying potential copyright issues;
|
22.908
|
Study on Paging Permission with Access Control (PPAC)
|
TR
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.908/22908-i01.zip
|
This Technical Report (TR) presents the results of the Study on Paging Permission with Access Control. The intent of this Study is to assess the ability of 3GPP specifications to meet requirements identified for Paging Permission with Access Control. This Study considers the following aspects:
- Identify requirements and aspects for Paging Permission with Access Control.
- Perform a Gap Analysis to assess the ability of existing 3GPP specifications to meet the requirements and aspects.
Regarding use-cases, followings should be studied in order to identify issues which are caused by the existing access control mechanism which does not allow UEs applied the access class restriction to establish terminating calls (non-exhaustive list):
• Priority Service.
• Emergency Service.
• Communication between UEs in the same area where access control is performed
This study should focus on providing this service using the CS/PS domain. This study includes the aspect of originating call and terminating call.
|
22.912
|
Study into network selection requirements for non-3GPP access
|
TR
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.912/22912-i01.zip
|
The present document considers the network selection procedures requirements for non-3GPP access types. The network selection principles covered include both automatic and manual selection. Also considered is the operator management of network preferences for non-3GPP access types and how the device accesses networks offered through non-3GPP access.
Non-3GPP access includes any method by which the UE is connected either to a core network or to a server other than by using the radio bearers standardised by 3GPP. Examples are: BlueTooth, WLAN and fixed (wired connections).
UEs considered in this study are UEs able to connect to a non-3GPP network in addition to its 3GPP capabilities (i.e. dual mode, multi-mode UEs).
This work in this TR is applicable to GSM and UMTS and there are no additional considerations of EPS (Evolved Packet System).
Roaming and handover conditions between 3GPP and non-3GPP networks is not under the scope of this document and will not be treated here. They may be referred to, however, for the consistency of use cases and access description consistency.
Connection to a 3GPP operator's core network by WLAN is out of scope where this is I-WLAN. This is covered in [2].
Use of the Generic Access Network is out of scope.
Considerations of tariffing are out of scope.
|
22.926
|
Guidelines for extraterritorial 5G Systems (5GS)
|
TR
|
18.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.926/22926-i00.zip
|
The present document identifies use cases and associated guidelines for the provision of services when a 5G public network has an extraterritoriality access component.
This Technical Report (TR) addresses:
- Use cases and associated conditions generating extraterritoriality of public 5G systems (e.g. HAPS covering multiple countries, satellite access covering international waters, aeronautical networks),
- 3GPP features (e.g. emergency calls, PWS, LI, charging) and technical aspects (e.g. MCC/MNC, location of UE/NW) for which extraterritoriality may be relevant, and types of regulations that may be applicable.
- Guidelines on the fulfilment of relevant regulatory requirements (e.g. routing to a core network in a specific country, use of MCC).
This 900 series TR is meant to serve as the basis for technical work in other 3GPP Working Groups when considering the above topics. This TR is not normative. It has been developed by SA1 to capture relevant high-level considerations associated with of the provision of 5G public network and access services in extraterritorial contexts, and provide corresponding guidelines.
|
22.936
|
Multi-system terminals
|
TR
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.936/22936-i01.zip
|
The present document studies the behaviour of a multi system terminal that supports both 3GPP and non-3GPP systems. Particular issues handled include, but are not restricted to:
• Whether the system selection or PLMN selection should take higher priority in a multi system terminal.
• Criteria for system change.
• Interaction between the user's and the operator's preferences.
• Support of automatic and manual system selection mode.
• Different methods of system selection and their impact on 3GPP specifications.
• Some areas for possible standardization, to ensure 3GPP compliance and protection of 3GPP networks.
The present document treats non-3GPP networks in a generic way but it applies mainly to the case of 3GPP2/3GPP compliant terminals.
|
22.940
|
IP Multimedia Subsystem (IMS) messaging
|
TR
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.940/22940-i01.zip
|
The objective of this Technical Report is to:
a) Describe use cases that illustrate the service requirements for IMS messaging.
b) Derive the broad 3GPP requirements for IMS messaging services.
c) Investigate the possible requirements for interworking with networks outside the 3GPP domain
d) Develop an analysis of the possible interaction between IMS messaging services and existing 3GPP messaging services (SMS, EMS and MMS) as well as other relevant 3GPP services such as presence IMS group management and so on.
e) Identify possible routes to standardization by:
1) Adopting existing and emerging standards, e.g. OMA, IETF.
2) Modifying and enhancing existing and emerging standards.
3) Developing of new standards.
|
22.942
|
Study on Value Added Services (VAS) for Short Message Service (SMS)
|
TR
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.942/22942-i01.zip
|
The present document studies the service requirements associated with series of value-added features for short message service (SMS). Specifically, the objective of this document is to study potential new value-added services for SMS in 3GPP that need to be standardized.
|
22.944
|
Report on service requirements for UE functionality split
|
TR
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.944/22944-i01.zip
|
This report identifies scenarios and requirements for UEs with functionality split over multiple devices. Scenarios that are required to be supported in the standard are defined in detail. The requirements in this report should enable interoperability between user equipment components from different vendors. This report is not intended to identify all possible or permitted functionality splits. Certain splits of functionality may be prohibited for security or other reasons. This report does not identify all prohibited scenarios.
|
22.947
|
Study on Personal Broadcast Service (PBS)
|
TR
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.947/22947-i01.zip
|
This Technical Report presents potential use cases of Personal Broadcast Service. It aims to take account of service and system aspect of PBS. The minimum set of service requirements associated with each use case will be identified.
|
22.948
|
Study of requirements of IP-Multimedia Subsystem (IMS) convergent multimedia conferencing
|
TR
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.948/22948-i01.zip
|
The present document studies the requirements for IP-Multimedia Subsystem (IMS) Convergent Multimedia Conferencing (CMMC) service in IMS. Specifically, the objective of this study item is to:
a) Identify features of IMS multimedia conferencing, and describe potential service requirements for IMS multimedia conferencing.
b) Identify the IMS requirements for multimedia conferencing services:
1) the conference framework
2) data sharing session establishment/termination/management in a conference
3) media control for audio, video and data
4) floor control for audio, video and data
5) conference policy
c) Identify possible routes to standardization by:
1) Adopting existing and emerging standards, e.g. OMA, IETF, W3C.
2) Modifying and enhancing existing and emerging standards.
3) Developing of new standards.
|
22.949
|
Study on a generalized privacy capability
|
TR
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.949/22949-i01.zip
|
The present document aims to investigate and summarise the existing service requirements on privacy for 3GPP services. In order to ensure that these services and future 3GPP services will have a consistent set of rules that control the availability and usage of confidential information, it is the intention to identify a common way to handle privacy related information in the network.
Generic privacy requirements for the mobile industry are also being defined in [3] by the Open Mobile Alliance and it is the intention of this document to present the existing requirements and any alternatives to achieving the required functionality within 3GPP networks.
The scope of this study is to:
- Identify privacy related information that is used in the 3GPP system;
- Identify the existing 3GPP services that handle privacy related information;
- Identify the various stakeholders that handle, control or consume personal data, and to define their relationships;
- Document the definitions of the various functions, stakeholders and functions involved in a privacy capability;
- Identify the work being done by other organizations and the additional work to be done by 3GPP.
The types of data subject to privacy rules within the scope of this study include
- Privacy related information specific to an individual user;
- Privacy related information relating to entities such as corporations;
- Network data such as serving cell and broadcast area, e.g. data that relates to the user's location or presence in the network, and which could be used by applications to track the user.
|
22.950
|
Priority service feasibility study
|
TR
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.950/22950-i01.zip
|
This Technical Report (TR) presents the results of the Feasibility Study on Priority Service. The intent of this Feasibility Study is to assess the ability of 3GPP specifications to meet high-level requirements identified for Priority Service. This Feasibility Study consisted of a multi-step process, namely:
1. Identify high-level requirements for Priority Service.
2. Determine existing relevant 3GPP specifications for Priority Service.
3. Perform a Gap Analysis to assess the ability of existing 3GPP specifications to meet the high-level Priority Service requirements.
Additional functionalities not documented in this TR are considered outside the scope of this TR. Such additional functionality may be on a network-wide basis, nation-wide basis or particular to a group of users. Such additional functionality shall not compromise conformance to the requirements of the Priority Service defined in this specification.
The Priority Service is intended to be utilised for both Voice and Data and therefore both elements are considered within the scope of this document. While Priority Service is meant for both Voice and Data services, the initial set of requirements address Circuit Switched Services (Voice as well as Data). Multimedia and non-circuit switched aspects of Priority Service have not been addressed in this feasibility study and are for further study.
The Priority Service is intended to interwork with external networks to provide an end-to-end service. Therefore, service interactions with external networks are considered within the scope of this document, although the specification of these interactions may be in other standards. If this occurs, a reference to that specification shall be made.
|
22.951
|
Service aspects and requirements for network sharing
|
TR
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.951/22951-i01.zip
|
In the current dynamic market place, as a result of partnerships, acquisitions, creative agreements among operators and so on, the need for tools that enable various degrees of network sharing is becoming more and more important.
When GSM and then UMTS were specified, the possibility of sharing part or all of the network by two or more separated commercial entities was not considered and as a result the standards lack some functionalities that enable the realisation of such commercial agreements.
GSM was designed under the principle "one operator, one radio access network". The GSM network has some possibilities of infrastructure sharing, but it does not support true radio access network sharing. The initial design of 3GPP system has followed the same principle.
This technical report is aimed to capture the service and user requirements that must be fulfilled by the 3GPP system in order to enable network sharing in a standardised way. Section 5 describes various Network sharing includes various scenarios e.g. spanning from common radio access network connected to multiple core networks toor multiple radio access networks sharing one core network. Section 6 contains a summary of the user classification and network identities. In section 7 the user requirements are described, while section 8 deals with the network operator requirements. Section 9 describes the mobility requirements in a shared network. The rest of the document is covering security (section 10) and charging (section 11). Some conclusions can be found in section 12 and an annex with examples of practical realisation of network sharing is provided.
|
22.952
|
Priority service guide
|
TR
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.952/22952-i01.zip
|
This present document addresses the Service Aspects (Service Description), Network Aspects (Call Flows), and Management Aspects (Operations, Administration, Maintenance, and Provisioning) of Priority Service, based on existing 3GPP specifications.
The Priority Service is intended to be used for both Voice and Data. However, this document only addresses Circuit Switched Voice Service. Data, multimedia and non-circuit switched aspects of Priority Service have not been addressed and are for further study.
The Priority Service is intended to interwork with external networks to provide an end-to-end service. Therefore, service interactions with external networks are considered within the scope of this document, although the specification of these interactions may be in another standard. If this occurs, a reference to that specification is made.
|
22.953
|
Multimedia priority service feasibility study
|
TR
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.953/22953-i01.zip
|
This Technical Report (TR) presents the results of the feasibility study on Multimedia Priority Service. The intent of this feasibility study is to assess the ability of 3GPP specifications to meet high-level requirements identified for Multimedia Priority Service. This feasibility study consisted of a multi-step process, namely:
- Identify high-level requirements for Multimedia Priority Service.
- Determine relevant 3GPP specifications for Multimedia Priority Service.
- Perform a Gap Analysis to assess the ability of existing 3GPP specifications to meet the high-level Multimedia Priority Service requirements.
The present document also presents the results of the subsequent feasibility study on Multimedia Priority Service - Phase 2 for Rel-17 identifying new use cases and associated capabilities to account for current and anticipated MPS User needs for priority voice, data, and video communication capabilities. The feasibility study on Multimedia Priority Service - Phase 2 also identifies new potential requirements for the normative stage 1 requirements specified in TS 22.153[9].
Additional functionalities not documented in this TR are considered outside the scope of this TR. Such additional functionality may be on a network-wide basis, nation-wide basis or particular to a group of users..
The Multimedia Priority Service is intended to be utilised for both Voice and Data in the Packet-switched (PS) domain and the IP Multimedia Subsystem (IMS).
The Multimedia Priority Service is intended to interwork with external networks to provide an end-to-end service. Therefore, service interactions with external networks are considered within the scope of this document, although the specification of these interactions may be in other standards. If this occurs, a reference to that specification is made.
|
22.967
|
Transferring of emergency call data
|
TR
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.967/22967-i01.zip
|
The present document examines the issues associated with the transmission of Emergency Call Data from a vehicle to a Public Service Access Point (PSAP).
Issues associated with the content of the Emergency Call Data or the triggers of the Emergency Calls are outside the scope of this document.
|
22.968
|
Study for requirements for a Public Warning System (PWS) service
|
TR
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.968/22968-i01.zip
|
This Technical Report (TR) represents the results of the Study on Public Warning System (PWS). The intent of this study is to identify requirements and aspects for a Public Warning System. The regulatory requirements and use cases for a public warning service have not been finalized in all regions (i.e. in the USA) therefore, the results of this study are not applicable for those regions which do not have regulatory requirements defined.
The Public Warning System is intended to interwork with external networks to provide an end-to-end service. Therefore, service interactions with a Warning Notification Provider in external networks are considered within the scope of this document, although the specification of these interactions may be in other standards. If this occurs, a reference to that specification shall be made.
|
22.973
|
IMS Multimedia Telephony service; and supplementary services
|
TR
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.973/22973-i01.zip
|
This Technical Report defines the IMS Multimedia Telephony service and associated supplementary services for IMS. It aims to take account and build on the IMS capabilities already provided in 3GPP Release 5 and Release 6.
The objective is to define the minimum set of capabilities required in the IP Multimedia Subsystem to secure multi-vendor and multi-operator inter-operability for the IMS Multimedia Telephony service and related Supplementary Services.
Close cooperation shall be sought with TISPAN. TISPAN requirements, as captured in [2], will be taken into account, and referred to where appropriate.
While the user experience for the IMS Multimedia Telephony service is expected to have some similarity to existing telephony services, the richer capabilities of IMS will be exploited.
|
22.977
|
Feasibility study for speech-enabled services
|
TR
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.977/22977-i01.zip
|
Speech Enabled Services
The advancement in the Automatic Speech Recognition (ASR) technology, coupled with the rapid growth in the wireless telephony market has created a compelling need for speech-enabled services. Voice-activated dialling has become a de facto standard in many of the mobile phones in the market today. The speech recognition technology has also been applied more recently to voice messaging and personal access services. A Voice Extensible Markup Language (Voice XML) has been designed to bring the full power of web development and content delivery to voice response applications [11]. Voice portals that provide voice access to conventional graphically oriented services over the Internet are now becoming popular. Forecasts show that speech-driven services will play an important role on the 3G market. Users of mobile terminals want the ability to access information while on the move and the small portable mobile devices that will be used to access this information need improved user interfaces using speech input.
Multimodal and Multi-device Services
Speech-enabled services may utilize speech alone for input and output interaction, or may also utilise multiple input and output modalities leading to the multimodal services.
Online access to information is fast becoming a must-have. Along with this trend, come new usage models for information access, particularly in mobile environments. Information appliances in cars such as navigation systems are standard in high-end cars already and this will penetrate lower-end vehicles soon. Data access using mobile phones, though limited and currently estimated to take three years to be widespread, has significant momentum that makes it certain to become widespread. In this new computing paradigm a person will expect to have access to information and interactions in a seamless manner in many environments, be it in the office, at home, in the car, often on several different devices. These new access methods have compelling advantages, such as mobile accessibility, low cost, ease of use, and mass market penetration. They also have their limitations - in particular, it is hard to enter and access data using small devices, speech recognition can introduce mistakes that can sometimes be repeating and therefore blocking the transaction; one interaction mode does not suit all circumstances, and so on.
For example, a recent study of task-performance using wireless phones, such as reading world headlines and checking local weather concluded that currently, these services are often poorly designed, have insufficient task analysis, and abuse existing non-mobile design guidelines. The full report from the field study can be downloaded at [6]. The basic conclusion of this study is that wireless access usability fails miserably; accomplishing even the simplest of tasks takes much too long to provide any user satisfaction. It is thus essential for the widespread acceptance of this computing paradigm to provide an efficient and usable interface on the different device platforms that people are expected to use to access and interact with information.
We can expect and already observe a trend towards a new frontier of interactive services: multimodal and multi-device services.
These services exploit the fact that different interaction modes are good at different things - for example, talking is easier than typing, but reading is faster than listening. Multi-modal interfaces combine the use of multiple interaction modes, such as voice, keypad and display to improve the user interface to services.
Different standard bodies are addressing aspects of this space, driven by several industry proposals: W3C (e.g. MMI activity)[11], OMA/WAP Forum, ETSI [1], IETF[14],…). In particular, the W3C MMI [13] aims at defining a programming model for multimodal and multi-device applications.
Additional details and motivations are discussed in [2, 7, 8].
Overview
A brief overview of the speech-enabled services is presented in Chapter 4. The different ways of enabling speech recognition for the speech enabled services are described in chapter 5. Section 6 discusses multimodal services and options to enable multimodal and multi-device services. The scope of the report, references, definitions and abbreviations are detailed in the first few chapters.
|
22.978
|
All-IP network (AIPN) feasibility study
|
TR
|
18.0.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.978/22978-i01.zip
|
The present document studies the feasibility of the progression of the 3GPP system to an AIPN. More specifically, this document:
a) Identifies and describes the objectives and user, business and technological drivers for progression of the 3GPP system to an AIPN:
i) Investigates the High Level Objectives
ii) Investigates Motivations and Drivers
iii) Investigates impacts upon current models (e.g. business/charging/service models)
b) Defines and develops the end-user and AIPN operator aspects of an AIPN:
i) Produces an AIPN vision, taking into account the special requirements for the mobile community e.g. carrier grade, optimisation for the radio environment, recognizing support of multiple access system scenarios.
ii) Investigates needs and requirements associated with the evolution of the 3GPP System to an AIPN.
iii) Investigates requirements associated with the reuse of legacy infrastructure and support of legacy terminals
iv) Investigates migration and cost effective introduction of new technology.
c) Identifies the capability expansion required to introduce the AIPN concept into the 3GPP system (migration and co-existence)
d) Evaluates whether an AIPN should be standardised within 3GPP, and in the case of a positive conclusion identifies the subsequent steps to be taken to achieve this by defining the scope, target, and roadmap for work to be undertaken within Rel-7 and future 3GPP releases.
|
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.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.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.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.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.