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
|
|---|---|---|---|---|---|---|
23.035
|
Immediate Service Termination (IST); Stage 2
|
TS
|
18.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.035/23035-i00.zip
|
This Technical Specification specifies the stage 2 description of the Immediate Service Termination (IST) service which provides the means for the HPLMN to terminate all the activities of an HPLMN subscriber in a VPLMN.
Two implementations of IST are described: an implementation based on CAMEL, and an implementation based on a new MAP message.
|
23.038
|
Alphabets and language-specific information
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.038/23038-i00.zip
|
The present document defines the character sets, languages and message handling requirements for SMS, CBS and USSD and may additionally be used for Man Machine Interface (MMI) (3GPP TS 22.030 [2]).
The specification for the Data Circuit terminating Equipment/Data Terminal Equipment (DCE/DTE) interface (3GPP TS 27.005 [8]) will also use the codes specified herein for the transfer of SMS data to an external terminal.
|
23.040
|
Technical realization of the Short Message Service (SMS)
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.040/23040-i00.zip
|
The present document describes the Short Message Service (SMS) for GSM/UMTS/EPS/5GS networks. It defines:
- the services and service elements;
- the network architecture;
- the Service Centre functionality;
- the SMS Router functionality;
- the MSC functionality (with regard to the SMS);
- the SGSN functionality (with regard to the SMS);
- the MME functionality (with regard to the SMS);
- the SMSF functionality;
- the routing requirements;
- the protocols and protocol layering;
for the Mobile Originated and Mobile Terminated Short Message Service Teleservices, as specified in 3GPP TS 22.003 [2] and 3GPP TS 22.105 [32].
The use of radio resources for the transfer of short messages between the MS and the MSC or the SGSN or the MME is described in 3GPP TS 24.011 [13].
The present document also describes the Short Message Service (SMS) for EPS networks supported via "SMS in MME" (see 3GPP TS.23.272 [45], annex C).
The present document also describes the SGSN supporting Diameter based protocol for SMS between the SGSN and the central SMS functions (SMS-GMSC, SMS-IWMSC, SMS-Router) in annex J.
The present document also describes SMS for 5GS networks (see 3GPP TS 23.501 [51] and 3GPP TS 23.502 [52]).
The network aspects of Short Message Service provision are outside the scope of the present document (i.e. the provision of network connectivity between the PLMN subsystems). There is no technical restriction within the present document for the transfer of short messages between different PLMNs. Any such restriction is likely to be subject to commercial arrangements and PLMN operators must make their own provision for interworking or for preventing interworking with other PLMNs as they see fit.
The required and assumed network service offered to the higher layers is defined in the present document.
|
23.042
|
Compression algorithm for text messaging services
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.042/23042-i00.zip
|
The present document introduces the concepts and mechanisms involved in the compression and decompression of a stream of data.
|
23.053
|
Tandem Free Operation (TFO); Service description; Stage 2
|
TS
|
18.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.053/23053-i00.zip
|
The present document defines the stage 2 service description for Tandem Free Operation (TFO) in and between GSM and UMTS. Tandem Free Operation applies only to speech calls.
NOTE: The TFO principles are built so that they could be used as well by other systems other than GSM and UMTS.
In analogy with ITU-T Recommendations I.130 [2] and with reference to ITU-T Recommendations Q.65 VI.1 (Stage 2 of the method for the characterisation of services supported by an ISDN), the second stage of the following three-level structure is derived from a stage 1 service description.
- Stage 1 is an overall service description, from the service subscriber's and user's standpoints, that views the network as a single entity which provides services to the user.
- Stage 2 identifies the functional capabilities and information flows needed to support the service described in stage 1. Furthermore, it identifies various possible physical locations for the functional capabilities. The output of Stage 2, which is signalling system independent, is used as an input to Stage 3, the design of signalling system and switching Recommendations.
- Stage 3 defines the signalling system protocols and switching functions needed to implement the service described in stage 2.
|
23.057
|
Mobile Execution Environment (MExE); Functional description; Stage 2
|
TS
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.057/23057-i00.zip
|
The present document defines the stage 2 and stage 3 description of the Mobile Execution Environment (MExE). Stage 2 identifies the functional capabilities and information flows needed to support the service described in stage 1.
The present document includes information applicable to network operators, service providers and terminal, switch and database manufacturers.
The present document contains the core functions for a Mobile Execution Environment (MExE) which are sufficient to provide a complete service.
MExE uses a number of technologies to realise the requirements of the stage 1 description (TS 22.057 [2]). The present document describes how the service requirements are realised with the selected technologies. The TS is devised into clauses each covering the aspects relating to particular MExE technologies, it is intended that this specification will evolve along with the MExE technologies. A generic clause of the specification covers areas of MExE common to all technologies.
Implementation of this specification outside the UE (User Equipment) is outside the scope of this specification.
|
23.060
|
General Packet Radio Service (GPRS); Service description; Stage 2
|
TS
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.060/23060-i00.zip
|
The present document defines the stage‑2 service description for the General Packet Radio Service (GPRS) which is a packet bearer service and a main part of the packet domain. ITU-T Recommendation I.130 [29] describes a three-stage method for characterisation of telecommunication services, and ITU-T Recommendation Q.65 [31] defines stage 2 of the method. The GPRS described in the present document is also the description of the GERAN and UTRAN related functionality of the Evolved Packet System (EPS) according to TS 23.401 [89].
The present document does not cover the Radio Access Network functionality. TS 43.064 [11] contains an overall description of the GSM EDGE Radio Access Network (GERAN). TS 25.401 [53] contains an overall description of the Universal Terrestrial Radio Access Network (UTRAN). TS 43.051 [74] contains an overall description of GSM/EDGE Radio Access Network.
The present document does not cover the functionality of the GPRS enhancements for the Evolved Universal Terrestrial Radio Access Network (E‑UTRAN). This functionality and also the interoperation functionality between E‑UTRAN and GERAN/UTRAN accesses are described in TS 23.401 [89].
The present document specifies functions, procedures and information which apply to GERAN Iu mode. However, functionality related to GERAN Iu mode is neither maintained nor enhanced since Rel‑9.
|
23.066
|
Support of Mobile Number Portability (MNP); Technical realization; Stage 2
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.066/23066-i00.zip
|
The present document describes several alternatives for the realisation of Mobile Number Portability.
The present document includes information applicable to network operators, service providers, switch and database manufacturers and national regulators.
It is left to operator and implementation decisions which option, or combination of options, is used, taking into account the regulatory and architectural constraints that may prevail. The possible implications of these options on internal node functions and on signalling performance are not covered in the present document.
Normative Annex A of the present document describes the technical realisation of the handling of calls to ported UMTS or GSM mobile subscribers using IN technology.
Normative Annex C of the present document describes the technical realisation of the handling of calls to ported UMTS or GSM mobile subscribers using Signalling Relay technology.
Normative Annex A and Normative Annex C describe alternative solutions. The network operator may choose the solution to be used in his network.
Normative Annex B of the present document describes the technical realisation of the handling of non-call related SCCP signalling for ported UMTS or GSM mobile subscribers using Signalling Relay technology.
The present document does not specify the porting process.
|
23.067
|
enhanced Multi-Level Precedence and Pre-emption Service (eMLPP); Stage 2
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.067/23067-i00.zip
|
The present document specifies the stage 2 description of the enhanced Multi-Level Precedence and Pre-emption Service (eMLPP) which provides different call priorities in combination with fast call set-up and pre-emption for different applications according to 3GPP TS 22.067.
|
23.072
|
Call Deflection (CD) supplementary service; Stage 2
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.072/23072-i00.zip
|
This Technical Specification gives the stage 2 description of the Call Deflection supplementary service.
|
23.078
|
Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 4; Stage 2
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.078/23078-i00.zip
|
The present document specifies the stage 2 description for the fourth phase (see 3GPP TS 22.078 [6]) of the Customized Applications for Mobile network Enhanced Logic (CAMEL) feature which provides the mechanisms to support services of operators which are not covered by standardized services even when roaming outside the HPLMN.
The CAMEL feature is a network feature and not a supplementary service. It is a tool to help the network operator to provide the subscribers with the operator specific services even when roaming outside the HPLMN.
In the present document, the GSM Service Control Function (gsmSCF) is treated as being part of the HPLMN. The regulatory environment in some countries may require the possibility that the gsmSCF and the HPLMN are controlled by different operators, and the gsmSCF and the HPLMN are therefore distinct entities.
The fourth phase of the CAMEL feature supports, in addition to the third phase of the CAMEL:
- Interactions with Optimal Routing;
- Call Party Handling;
- DTMF Mid call procedure for Mobile Originated and Mobile Terminating calls;
- Inclusion of flexible tone injection;
- Provision of location information of called subscriber;
- Provide location information during ongoing call;
- CAMEL control over MT SMS;
- Notification of GPRS mobility management to CSE;
- Inclusion of ODB data in Any Time Modification;
- Enhancement of Any Time Interrogation and Provide Subscriber Information for PS Domain;
- Mobile Number Portability database interrogation;
- Criteria for the provision of location information during ongoing call;
- Enhanced Dialled Services;
- Enhancement to Establish Temporary Connection;
- CAMEL control of trunk originated calls.
CAMEL applicability to IP-based multimedia services is introduced in the fourth phase of the CAMEL. It is specified in 3GPP TS 23.278 [29].
CAMEL is not applicable to Emergency Setup (TS 12), i.e. if an Emergency call is requested, then the gsmSSF shall not be invoked.
The mechanism described in the present document addresses especially the need for information exchange between the VPLMN or IPLMN and the HPLMN for support of operator specific services. Any user procedures for the control of operator specific services are outside the scope of the present document. Subscribers who have subscribed to operator specific services and therefore need the functional support of the CAMEL feature shall be marked in the HPLMN and VPLMN. In case a subscriber is marked to need CAMEL support, the appropriate procedures which provide the necessary information to the VPLMN or the HPLMN are invoked. It is possible for the HPLMN to instruct the VPLMN or IPLMN to interact with a gsmSCF which is controlled by the HPLMN.
The specification of operator specific services is outside the scope of the present document.
|
23.079
|
Support of Optimal Routeing (SOR); Technical realization
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.079/23079-i00.zip
|
The present document specifies the technical realisation of the first phase of the network feature Support of Optimal Routeing (SOR). The first phase of SOR provides:
- as a network operator option, a method to route a call from one mobile subscriber directly to another mobile subscriber who is in the same country as the calling mobile subscriber or in the called mobile subscriber's home country, without needing to connect the call via the HPLMN of the called subscriber, even though the called mobile subscriber has roamed outside his HPLMN;
- a method to forward calls when a called mobile subscriber who has roamed outside his home country is busy, or is not reachable, or does not reply, to a forwarded-to destination in the HPLMN country of the called subscriber or the VPLMN country of the called subscriber, without needing to connect the forwarded call via the VPLMN of the called subscriber;
- a method to combine the optimal routeing described in the first bullet point above with the optimal routeing described in the second bullet point above.
OR of a call is permitted only if all entities involved in handling the call support OR.
Other cases of optimal routeing (e.g. calls where the calling and called subscribers are in different countries, forwarding to a mobile subscriber or multiple forwarding) will be considered for inclusion in later phases.
|
23.081
|
Line Identification supplementary services; Stage 2
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.081/23081-i00.zip
|
The present document gives the stage 2 description of the call identification supplementary services.
The group line identification supplementary services are divided into the following four supplementary services:
‑ Calling line identification presentation CLIP (clause 1);
‑ Calling line identification restriction CLIR (clause 2);
‑ Connected line identification presentation COLP (clause 3);
‑ Connected line identification restriction COLR (clause 4).
|
23.082
|
Call Forwarding (CF) supplementary services; Stage 2
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.082/23082-i00.zip
|
The present document gives the stage 2 description of the call forwarding supplementary services.
The group of supplementary services call offering supplementary services is divided into 4 different supplementary services:
- Call forwarding unconditional (CFU) (clause 1);
- Call forwarding on mobile subscriber busy (CFB) (clause 2);
- Call forwarding on no reply (CFNRy) (clause 3);
- Call forwarding on mobile subscriber not reachable (CFNRc) (clause 4).
|
23.083
|
Call Waiting (CW) and Call Hold (HOLD) supplementary services; Stage 2
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.083/23083-i00.zip
|
The present document gives the stage 2 description of the call completion supplementary services.
The group of call completion supplementary services is divided into the following two supplementary services:
- Call waiting (CW) (clause 1);
- Call hold (HOLD) (clause 2).
|
23.084
|
Multi Party (MPTY) supplementary service; Stage 2
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.084/23084-i00.zip
|
The present document gives the stage 2 description of the multi party supplementary services.
Only one multi party supplementary service has been defined, this is the Multi Party (MPTY) service, and is described in clause 1.
|
23.085
|
Closed User Group (CUG) supplementary service; Stage 2
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.085/23085-i00.zip
|
The present document gives the stage 2 description of the closed user group supplementary service.
The community of interest supplementary service defined is:
- closed user group (CUG) (see clause 1).
|
23.086
|
Advice of Charge (AoC) supplementary services; Stage 2
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.086/23086-i00.zip
|
The present document gives the stage 2 description of the Advice of Charge (AoC) supplementary services.
The charging supplementary services currently defined are:
- Advice of Charge (Information) (AoCI) (clause 1);
- Advice of Charge (Charging) (AoCC) (clause 2).
|
23.087
|
User-to-User Signalling (UUS) supplementary service; Stage 2
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.087/23087-i00.zip
|
The present document gives the stage 2 description of the User-to-User signalling supplementary services.
The User-to-user supplementary service is divided into 3 different services:
- Service 1 (UUS1)
- Service 2 (UUS2)
- Service 3 (UUS3)
|
23.088
|
Call Barring (CB) Supplementary Services; Stage 2
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.088/23088-i00.zip
|
The present document gives the stage 2 description of the call barring services.
The possibility for a mobile subscriber to have certain categories of calls barred originated from or terminated at his access:
Barring of outgoing calls (clause 1):
- Barring of all outgoing calls (BAOC) (Barring program 1);
- Barring of outgoing international calls (BOIC) (Barring program 2);
- Barring of outgoing international calls EXCEPT those directed to the home PLMN country
(BOIC-exHC) (Barring program 3).
Barring of incoming calls (clause 2):
- Barring of all incoming calls (BAIC) (Barring program 1);
- Barring of incoming calls when roaming outside the home PLMN country
(BIC-Roam) (Barring program 2);
- Anonymous Call Rejection (ACR) (Barring program 3).
NOTE: The call barring program "incoming calls when roaming outside the home PLMN country" (clause 2) is only relevant if as a general rule the called mobile subscriber pays the charges for the forwarded part of the call from his home PLMN country to any other country.
|
23.090
|
Unstructured Supplementary Service Data (USSD); Stage 2
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.090/23090-i00.zip
|
The present document gives the stage 2 description of Unstructured Supplementary Service Data (USSD).
The unstructured supplementary service data (USSD) mechanism allows the Mobile Station (MS) user and a PLMN operator defined application to communicate in a way which is transparent to the MS and to intermediate network entities. The mechanism allows development of PLMN specific supplementary services. The following diagram shows how handling of USSD is carried out, independently of the applications.
Figure 1.1: Handling of USSD
The present document defines the requirements for handling USSD at the MS and network entities. It does not include specification of particular applications, nor does it specify how a particular application is selected. Where more than one application exists at a network entity, routing of messages to the correct application is carried out by the USSD handler. The MMI for USSD is specified in TS 22.030 and TS 22.090. The alphabet indicator and the data coding scheme are defined in TS 23.038.
USSD may be initiated by the MS user, or by the network in the following ways:
- Network initiated USSD (clause 1);
- Mobile initiated USSD (clause 2).
|
23.091
|
Explicit Call Transfer (ECT) supplementary service; Stage 2
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.091/23091-i00.zip
|
The present document gives the stage 2 description of the call transfer supplementary services.
Only one call transfer supplementary service has been defined, this is the Explicit Call Transfer (ECT) supplementary service, and is described in the present document.
|
23.093
|
Technical realization of Completion of Calls to Busy Subscriber (CCBS); Stage 2
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.093/23093-i00.zip
|
This Technical Specification gives the stage 2 description of the Completion of Calls to Busy Subscriber (CCBS) supplementary service.
|
23.094
|
Follow-Me (FM); Stage 2
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.094/23094-i00.zip
|
The present document specifies the stage 2 description for the Follow Me feature.
The Follow Me feature enables a mobile subscriber A to manipulate the Follow Me data of a remote party B in such a way that subsequent calls directed to remote party B will be forwarded to subscriber A.
|
23.096
|
Name identification supplementary services; Stage 2
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.096/23096-i00.zip
|
The present document gives the stage 2 description of the Name Identification Supplementary Services.
The group of Name Identification Supplementary Services contains the following Supplementary Service:
CNAP - Calling name presentation (clause 4).
|
23.097
|
Multiple Subscriber Profile (MSP) (Phase 2); Stage 2
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.097/23097-i00.zip
|
The present document specifies the stage 2 description of the Multiple Subscriber Profile (MSP) Supplementary Service Phase 2. MSP Phase 2 is implemented using CAMEL Phase 3.
|
23.101
|
General Universal Mobile Telecommunications System (UMTS) architecture
|
TS
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.101/23101-i00.zip
|
This TS defines the basic physical and functional separation of UMTS. The contents of this specification is limited to those features that are common to all UMTS networks independent of their origin. It identifies and names the reference points and functional groupings appearing at this level.
|
23.107
|
Quality of Service (QoS) concept and architecture
|
TS
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.107/23107-i00.zip
|
The present document provides the framework for Quality of Service within the 3GPP system. The main purpose is to specify the list of attributes applicable to the UMTS Bearer Service and the Radio Access Bearer Service, as well as describe the Quality of Service architecture to be used in the 3GPP system.
|
23.108
|
Mobile radio interface layer 3 specification, core network protocols; Stage 2
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.108/23108-i00.zip
|
The present document specifies the procedures used at the radio interface (Reference Point Um, see 3GPP TS 24.002 [15]) for Call Control (CC), Mobility Management (MM), and Session Management (SM).
When the notations for "further study" or "FS" or "FFS" are present in the present document they mean that the indicated text is not a normative portion of this standard.
These procedures are defined in terms of messages exchanged over the control channels of the radio interface. The control channels are described in 3GPP TS 44.003 [16].
The structured functions and procedures of this protocol and the relationship with other layers and entities are described in general terms in 3GPP TS 24.007 [20].
|
23.110
|
Universal Mobile Telecommunications System (UMTS) access stratum; Services and functions
|
TS
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.110/23110-i00.zip
|
The present document specifies the services provided by the Access Stratum to the rest of the system. The adopted architecture is given by TS 23.101 [2].
The present document describes the main functions visible at the boundary between the Access Stratum and the rest of the system, it describes in general terms the information flows, both control and user data, over this boundary and relevant for the Access Stratum.
The present document is the basis of the detailed specifications of the protocols which rule the information flows, both control and user data, between the Access Stratum and the parts of UMTS outside the Access Stratum, and of the detailed specifications of the UTRAN. These detailed specifications are to be found in other Technical Specifications.
|
23.116
|
Super-Charger technical realization; Stage 2
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.116/23116-i00.zip
|
The present document specifies the stage 2 description of the Super-Charger that provides a mechanism to reduce the signalling traffic associated with mobility.
|
23.119
|
Gateway Location Register (GLR); Stage 2
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.119/23119-i00.zip
|
The present document gives the stage 2 description of the Gateway Location Register (GLR) within the UMTS Core Network as a means of reducing the amount of MAP signalling traffic associated with location management carried over inter-PLMN links for roaming users.
The present document will be restricted of the case where the GLR supports one VPLMN only.
|
23.135
|
Multicall supplementary service; Stage 2
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.135/23135-i00.zip
|
The present document gives the stage 2 description of the Multicall supplementary service.
|
23.139
|
3GPP system - fixed broadband access network interworking; Stage 2
|
TS
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.139/23139-i00.zip
|
This document specifies the Stage 2 system description for the interworking between a 3GPP system and a Fixed Broadband Access network defined by Broadband Forum to provide the IP connectivity to a 3GPP UE using a WLAN and a H(e)NB connected to a Fixed Broadband Access network.
The specification covers the system description mobility, Policy, QoS aspects between 3GPP and a Fixed Broadband Access network as well as the respective interactions with the PCC frameworks. This document specifies the detailed extension to EPC defined in TS 23.401 [2] and TS 23 402 [3] for supporting Fixed Broadband Access Network. The extension to PCC framework are specified in TS 23.203 [4].
|
23.141
|
Presence service; Architecture and functional description
|
TS
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.141/23141-i00.zip
|
The present document describes the stage 2 description (architectural solution and functionalities) for the Presence Service, which includes the elements necessary to realise the stage 1 requirements in TS 22.141 [2].
The present document includes information applicable to network operators, service providers and manufacturers.
|
23.142
|
Value-added Services for SMS (VAS4SMS); Interface and signalling flow
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.142/23142-i00.zip
|
The present document describes the stage 2 of the VAS4SMS (Value Added Service for SMS). It includes:
- The logic architecture;
- The logic elements functionality;
- The signaling flows;
- The interaction with other features.
The service requirements of VAS4SMS are specified in 3GPP TS 22.142 [2].
The functionality and mechanism of SMS Service is defined in 3GPP TS 23.040 [4].
|
23.146
|
Technical realization of facsimile Group 3 non-transparent
|
TS
|
18.0.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.146/23146-i00.zip
|
The present document describes the procedures allowing the technical realization of the real time end‑to‑end facsimile group 3 service within the UMTS PLMN using non‑transparent network support according to the definition of the Teleservices 61 and 62 specified in 3GPP TS 22.003. Within the present document particular attention is given to Teleservice "Alternate speech/facsimile group 3" (Teleservice 61). However, the definitions apply also to Teleservice "Automatic facsimile group 3" (Teleservice 62) with the exception of all actions concerned with the speech phase. Consequently, in the following descriptions the term "Teleservice" denotes both Teleservice 61 and Teleservice 62 as appropriate.
NOTE: V.25bis is outdated. References to V.25bis procedures need to be replaced by corresponding procedures based on V.250 and 3GPP TS 27.007.
|
23.153
|
Out of band transcoder control; Stage 2
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.153/23153-i00.zip
|
The present document specifies the stage 2 description of the Out-of-Band Transcoder Control for speech services. It describes the principles and procedures to support Transcoder Free Operation, Tandem Free Operation and the interworking between TrFO and TFO. Transcoder at the edge is also part of the present document.
The present document specifies functions, procedures and information which apply to GERAN Iu mode. However, functionality related to GERAN Iu mode is neither maintained nor enhanced.
|
23.161
|
Network-Based IP Flow Mobility (NBIFOM); Stage 2
|
TS
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.161/23161-i00.zip
|
The scope of this document is to specify the support of NBIFOM (Network based IP Flow Mobility) i.e. IP flow mobility based on network mobility protocols. This feature supports PDN connections that are simultaneously connected over 3GPP access (i.e. S5/S8 connection to a PDN GW) and a WLAN access (i.e. S2a or S2b connection to the same PDN GW).
|
23.172
|
Technical realization of Circuit Switched (CS) multimedia service UDI/RDI fallback and service modification; Stage 2
|
TS
|
18.0.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.172/23172-i00.zip
|
The present document describes the Service Change and UDI Fallback (SCUDIF) feature. This service is available to UDI/RDI multimedia calls and allows users to achieve successful call establishment when end to end circuit-switched (CS) multimedia is not possible (fallback to speech) or when signalling of the feature is not possible in the network (fallback to preferred service or speech). Furthermore, it allows the users to swap between a multimedia service and basic speech during an established call.
NOTE: In the present document, the term "multimedia" refers to UDI/RDI multimedia unless specifically stated.
|
23.202
|
Circuit switched data bearer services
|
TS
|
18.0.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.202/23202-i00.zip
|
The present document provides an overview of the architecture and issues related to the provision of Circuit Switched Bearer Services in a 3G mobile network (UMTS) operating in UTRAN or GERAN Iu mode. Handover to GERAN A/Gb mode is also considered.
NOTE: The Gb interface does not play any role in the scope of the present document although the term "A/Gb mode" is used.
|
23.205
|
Bearer-independent circuit-switched core network; Stage 2
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.205/23205-i00.zip
|
The present document defines the stage 2 description for the bearer independent CS core network. The stage 2 shall cover the information flow between the GMSC server, MSC server and media gateways. Note that nothing in the present document shall preclude an implementation of a combined MSC Server and MGW. The present document shall show the CS core network termination of the Iu interface in order to cover the information flow stimulus to the core network and describe the interaction with the supplementary and value added services and capabilities.
For the purposes of the present document, the protocol used over the Nc interface is an enhanced call control protocol supporting call bearer separation such as BICC (which is specified in [22]). The protocol used over the Mc interface is H.248 (which is specified in 3GPP TS 29.232 [6]). Existing specifications and recommendations shall not be repeated, as such the relevant specification shall be referred to.
SIP-I based CS core network is further specified in 3GPP TS 23.231 [42].
Local Call Local Switch (LCLS) functionality is further specified in 3GPP TS 23.284 [45].
The present document is applicable only for ATM or IP transport in the CS core network.
Figure 1: CS core network logical architecture
The CAP interfaces and the interfaces towards the HLR are outside the scope of the present document.
Details of Transcoder-Free Operation are outside the scope of the present document. Please see 3GPPTS 23.153 [3] for more information.
The present document specifies functions, procedures and information which apply to GERAN Iu mode. However, functionality related to GERAN Iu mode is neither maintained nor enhanced.
|
23.207
|
End-to-end Quality of Service (QoS) concept and architecture
|
TS
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.207/23207-i00.zip
|
The present document provides the framework for end-to-end Quality of Service involving GPRS and complements TS 23.107 [3] which describes the framework for Quality of Service within UMTS. The end-to-end QoS architecture is provided in Figure 1. The document describes the interaction between the TE/MT Local Bearer Service, the GPRS Bearer Service, and the External Bearer Service, and how these together provide Quality of Service for the End-to-End Service. The document also describes IP level mechanisms necessary in providing end-to-end Quality of Service involving GPRS networks, including possible interaction between the IP level and the GPRS level, as well as the application level and the IP level.
This document covers different architectural aspects of the end-to-end Quality of Service concept and architecture with varying level of detail. In general, other specifications shall be referred to for further details; these other specifications enable the reader to acquire the full understanding of the end-to-end Quality of Service concept and architecture. In particular, the stage 2 specification for the PCC architecture is specified in TS 23.203 [21]. The present document does not contain any requirements for the PCC architecture.
In contrast to the TS 23.107 [3], the present document is only applicable to GPRS packet switched access services, and includes aspects of interworking to the IM subsystem as well as PSTN and other networks. The document does not cover the circuit switched access services.
Figure 1: End-to-End QoS Architecture
|
23.214
|
Architecture enhancements for control and user plane separation of EPC nodes
|
TS
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.214/23214-i00.zip
|
The present document specifies the overall stage 2 level functionality for control and user plane separation of EPC's SGW, PGW and TDF. This enables a flexible placement of the separated control plane and user plane functions for supporting diverse deployment scenarios (e.g. central or distributed user plane function) without affecting the overall functionality provided by these EPC entities.
|
23.216
|
Single Radio Voice Call Continuity (SRVCC); Stage 2
|
TS
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.216/23216-i00.zip
|
This document specifies the architecture enhancements for Single Radio Voice Call Continuity (SRVCC) between the following access systems for voice calls that are anchored in the IMS:
- from E‑UTRAN to 3GPP2 1xCS;
- from E‑UTRAN to UTRAN/GERAN;
- from UTRAN (HSPA) to UTRAN/GERAN.
- from UTRAN/GERAN to E-UTRAN.
- from GERAN to UTRAN (HSPA).
- from NG-RAN to UTRAN.
This document will not describe 3GPP2 functional entities. However, interfaces between both 3GPP and 3GPP2 functional entities are described in this specification.
SRVCC from E‑UTRAN access to 3GPP2 1xCS is covered in this specification, including the handling of IMS emergency call continuity. Handling of non‑voice component and SRVCC from 3GPP2 1xCS to E‑UTRAN direction is not specified in this release.
SRVCC from NG-RAN/E‑UTRAN/UTRAN (HSPA) access and 3GPP UTRAN/GERAN CS accesses for voice calls that are anchored in the IMS, as well as the coordination between the SRVCC for voice call and the handover of non‑voice PS bearers are covered in this specification. SRVCC with IMS emergency call continuity from E-UTRAN/UTRAN (HSPA) to 3GPP UTRAN/GERAN CS accesses and from NG-RAN to UTRAN for voice calls is covered in this specification. SRVCC with eCall over IMS continuity from E-UTRAN/UTRAN (HSPA) to 3GPP UTRAN/GERAN CS accesses is covered in this specification. SRVCC with priority handling from E-UTRAN to 3GPP UTRAN/GERAN CS accesses for voice or voice and video calls is also covered in this specification. The handover of non‑voice PS bearer from E-UTRAN is specified by the procedures defined in TS 23.401 [2], TS 23.060 [10], TS 25.413 [11] and TS 43.129 [12]. The handover of non-voice PS bearer from UTRAN (HSPA) is specified by the procedures defined in TS 23.060 [10], TS 25.413 [11] and TS 43.129 [12]. The handover of non-voice PS bearer from NG-RAN to UTRAN is not supported.
This document specifies the architecture enhancements for Single Radio Video Call Continuity (vSRVCC) from E-UTRAN to UTRAN-CS access for Video Calls that are anchored in the IMS.
|
23.218
|
IP Multimedia (IM) session handling; IM call model; Stage 2
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.218/23218-i00.zip
|
The present document specifies the IP Multimedia (IM) Call Model for handling of an IP multimedia session origination and termination for an IP Multimedia subscriber.
The present document includes interactions between an Application Server and IP multimedia sessions.
The IP Multimedia (IM) Subsystem stage 2 is specified in 3GPP TS 23.228 [3].
|
23.221
|
Architectural requirements
|
TS
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.221/23221-i00.zip
|
This document covers the architectural requirements for 3GPP systems based on UTRAN, E-UTRAN and Iu mode GERAN. In particular it details the high level requirements for the Circuit Switched (CS) Domain and the stage 2 procedures that span more than one domain/subsystem. The reference model to which these procedures apply can be found within TS 23.002 [1]. In addition, A mode to Iu mode handover for CS services is addressed. Detailed architectural requirements within the subsystems are contained within the remainder of the 23 series of specifications e.g. the requirements for the Packet Switched (PS) domain are contained within TS 23.060 [2], TS 23.401 [27] and the requirements for the Bearer Independent CS Core Network are contained in TS 23.205[14].
|
23.226
|
Global text telephony (GTT); Stage 2
|
TS
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.226/23226-i00.zip
|
This 3GPP Technical Specification defines the stage 2 description of the real time Text Conversation Feature called Global Text Telephony, GTT. GTT Stage 2 identifies the functional capabilities needed to support the service described in GTT Stage 1.
This TS contains the core functions for a real time Text Conversation Feature GTT, to be used in combination with other media in conversational services.
GTT offers real time conversation in text, to be used alone or in combination with other conversational media, and interworking with current and emerging text conversation features in the fixed networks and other mobile networks.
GTT uses a number of functional entities to realise the requirements of the stage 1 description (TS 22.226 [3]). This TS describes how the service requirements are realised with these functional entities. As far as possible existing protocols shall be used for the realisation of the Global Text Telephony Feature. This may include e.g. , SIP, 3G.324, or Circuit Switched Voice service as protocol environments, and CTM, AL1 and RTP/text as transmission protocols. It also means usage of existing text presentation format ITU‑T Recommendation T.140 [5], common to all GTT text conversation environments.
|
23.231
|
SIP-I based circuit-switched core network; Stage 2
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.231/23231-i00.zip
|
The present document defines the stage 2 description for the SIP-I based CS core network. The logical architecture for the SIP-I based CS core network is defined in 3GPP TS 23.205 [7].
This stage 2 shall cover the information flows between the GMSC server, MSC server and media gateways that are required to support a SIP-I based Nc interface. Note that nothing in the present document shall preclude an implementation of a combined MSC Server and MGW. The present document shall show the CS core network termination of the Iu and A interfaces in order to cover the information flow stimulus to the core network and describe the interaction with the supplementary and value added services and capabilities.
For the purposes of the present document, the Nc interface profile is based on ITU-T Q.1912.5 [9] SIP-I profile C and is specified in 3GPP TS 29.231 [4]. The Mc interface profile is based on ITU-T H.248.1 [5] and is specified in 3GPP TS 29.232 [8].
Local Call Local Switch (LCLS) functionality is further specified in 3GPP TS 23.284 [31].
The present document is applicable only for IP transport in the CS core network.
Details of Transcoder-Free Operation/Out of Band Transcoder Control are outside the scope of the present document. See 3GPP TS 23.153 [3] for more information.
The present document specifies functions, procedures and information which apply to GERAN Iu mode. However, functionality related to GERAN Iu mode is neither maintained nor enhanced.
|
23.236
|
Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes
|
TS
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.236/23236-i00.zip
|
This document covers the details for the Intra Domain Connection of RAN Nodes to Multiple CN Nodes for GERAN and UTRAN based systems. In particular, it details the impacts to GSM and UMTS systems and the stage 2 procedures for the support of connecting a RNC or BSC to multiple MSC servers or SGSNs. The overall solution is described, and the detailed impacts on the existing specifications are identified. The description of a broadly similar concept for E-UTRAN based systems is not described in the document: instead, it is described in TS 23.401 [22].
NOTE: The specified solution impacts RAN nodes. In case an upgrade of radio networks is not performed, the solutions for deploying NNSF functionality above RAN nodes described in TR 23.924 [23] may be used as a guideline for connecting RAN nodes to multiple MSC servers.
The reference model to which these procedures apply can be found within TS 23.002 [1]. Detailed architectural requirements within the subsystems are contained within the remainder of the 23 series of specifications e.g. the requirements for the Packet Switched (PS) domain are contained within TS 23.060 [2] and the requirements for the Bearer Independent CS Core Network are contained in TS 23.205 [14].
|
23.237
|
IP Multimedia Subsystem (IMS) Service Continuity; Stage 2
|
TS
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.237/23237-i00.zip
|
The present document specifies the architectural requirements and procedures for delivery of IMS Service Continuity.
TS 23.206 [3] is migrated to this specification.
The scope of the specification includes:
- Access Transfer related functionality:
- PS-CS Access Transfer;
- PS-PS Access Transfer;
- PS-PS Access Transfer in conjunction with PS-CS Access Transfer;
- Adding and/or removing media flows to support service;
. MSC Server assisted mid-call feature;
- SRVCC session transfer of IMS emergency session;
- DRVCC session transfer of IMS emergency session.
- Inter‑UE Transfer related functionality:
- Establishment and release of a Collaborative Session;
- Addition of media flows to, modification of media flows in, and release of media flows from a Collaborative Session;
- Transfer of media flows from one UE to another;
- Transfer of the Collaborative Session Control with or without transfer of media flows;
- Transfer of all media flows to a target UE without establishing a Collaborative Session;
- Session discovery;
- Inter-UE Transfer initiated by the target UE or by the SCC AS;
- Replication of media flows by means of Inter-UE Transfer procedures;
- Authorization and other aspects to support Inter-UE Transfer across multiple IMS subscriptions.
The solution is restricted to service continuity using IMS procedures, i.e. mobility mechanisms on the IP-CAN level are not within the scope of this specification.
|
23.240
|
3GPP Generic User Profile (GUP); Architecture (Stage 2)
|
TS
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.240/23240-i00.zip
|
The present document defines the stage 2 architecture description to the 3GPP Generic User Profile (GUP), which includes the elements necessary to realise the stage 1 requirements in TS 22.240 [1].
The present document includes the GUP reference architecture with descriptions of functional entities, and their interfaces and procedures, as well as the high-level information model for the GUP data.
|
23.246
|
Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional description
|
TS
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.246/23246-i00.zip
|
The present document describes the stage 2 description (architectural solution and functionalities) for the MBMS Bearer Service, which includes, together with MBMS User Services defined in TS 26.346 [7], all the elements necessary to realise the stage 1 requirements in TS 22.146 [2] and TS 22.246 [6]. This document encompasses both GPRS and EPS.
The present document also includes considerations on the manner in which User Services should make use of the MBMS Bearer Service described herein. It should be noted that the specification of MBMS User Services in TS 26.346 [7] takes precedence over User Service aspects described in this document.
The present document includes information applicable to network operators, service providers and manufacturers.
|
23.251
|
Network sharing; Architecture and functional description
|
TS
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.251/23251-i00.zip
|
The present document covers the details of Network Sharing for GERAN, UTRAN and E-UTRAN. It shows how several core network operators can share one radio access network and details the impacts on the network architecture. All UEs shall comply with existing requirements, among them PLMN selection and system information reception. The present document also defines requirements for network-sharing supporting UEs.
|
23.259
|
Personal Network Management (PNM); Procedures and information flows; Stage 2
|
TS
|
18.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.259/23259-i00.zip
|
The present document provides the procedure details and the information flows for support of Personal Network Management and Personal Area Network, including the PN redirection and PN access control applications enabled by Personal Network Management (PNM).
|
23.271
|
Functional stage 2 description of Location Services (LCS)
|
TS
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.271/23271-i00.zip
|
The present document specifies the stage 2 of the LoCation Services (LCS) feature in UMTS, GSM and EPS (for E-UTRAN), which provides the mechanisms to support mobile location services for operators, subscribers and third party service providers.
Location Services in 5GC are restricted to regulatory services and are specified in TS 23.501 [54] and TS 23.502 [55] in this release of the specification. The architecture and signalling procedures in NG-RAN are defined in TS 38.305 [56].
The present document replaces the specifications TS 23.171 (Release 1999) and the system and core network parts of GSM 03.71 (Release 1999). TS 43.059 [16] replaces the radio access network parts of GSM 03.71 (Release 1999).
Location Services may be considered as a network provided enabling technology consisting of standardised service capabilities, which enable the provision of location applications. The application(s) may be service provider specific. The description of the numerous and varied possible location applications which are enabled by this technology are outside the scope of the present document. However, clarifying examples of how the functionality being described may be used to provide specific location services may be included.
This stage 2 service description covers the LCS system functional model for the whole system, the LCS system architecture, state descriptions, message flows, etc.
|
23.261
|
IP flow mobility and seamless Wireless Local Area Network (WLAN) offload; Stage 2
|
TS
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.261/23261-i00.zip
|
This document specifies the Stage 2 system description for IP flow mobility between a 3GPP and a WLAN. The technical solution is based on the working principles of DSMIPv6 [2] and it is applicable to both the Evolved Packet System and the I-WLAN mobility architecture.
The specification covers the system description of seamless WLAN offload and IP flow mobility between 3GPP and WLAN as well as the respective interactions with the PCC and ANDSF frameworks. The system description for non seamless WLAN offload is covered in 3GPP TS 23.402 [3].
This document specifies also the detailed extensions to S2c [3] and H1 [4] reference points for IP flow mobility. The extensions to the PCC and to the ANDSF framework are specified respectively in 3GPP TS 23.203 [5] and in 3GPP TS 23.402 [3].
|
23.278
|
Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 4; Stage 2; IM CN Interworking
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.278/23278-i00.zip
|
The present document specifies the stage 2 description for the Customized Applications for Mobile network Enhanced Logic (CAMEL) feature which provides the mechanisms to support services for the IP Multimedia Core Network (IM CN) Subsystem.
|
23.279
|
Combining Circuit Switched (CS) and IP Multimedia Subsystem (IMS) services; Stage 2
|
TS
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.279/23279-i00.zip
|
The present document provides architectural details to combine CS services and IMS services for using them in parallel between the same two users in a peer-to-peer context. The document provides a detailed description of how capabilities and identities are exchanged to enable the combination of CS and IMS services between the same two UEs.
The present document includes the following capabilities that enable the combination of CS and IMS services:
- Radio capability exchange.
- SIP based UE terminal capability exchange.
- MSISDN number exchange in SIP.
- Establishing an IMS session in parallel to an ongoing CS call between the same two UEs.
- Establishing a CS call in parallel to an ongoing IMS session between the same two users UEs.
- Network support for establishing multimedia sessions between a UE that uses IMS origination and a UE that uses CSI termination.
The individual CS call or IMS service that are combined are described in their respective specifications.
|
23.284
|
Local Call Local Switch (LCLS); Stage 2
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.284/23284-i00.zip
|
The present document defines the Stage 2 description for the Local Call Local Switch feature. Local Call Local Switch may be implemented in both BICC based CS core networks as defined in 3GPP TS 23.205 [2] and SIP-I based CS core networks as defined in 3GPP TS 23.231 [3], with a GSM/EDGE Radio Access Network supporting either TDM based or IP based A interface.
This stage 2 shall cover the information flows between the GMSC server, MSC server and media gateways that are required to support Local Call Local Switching highlighting the specific requirements in addition to those defined for BICC based CS core networks 3GPP TS 23.205 [2] and SIP-I based CS core networks 3GPP TS 23.231 [3]. Note that nothing in the present document shall preclude an implementation of a combined MSC Server and MGW. The present document shall show the CS core network termination of the A interface, and the information flows between the BSS and the MSC server, in order to cover the information flow stimulus to the core network and describe the interaction with the supplementary and value added services and capabilities.
The present document specifies functions, procedures and information which apply to GERAN Iu mode. However, functionality related to GERAN Iu mode is neither maintained nor enhanced.
|
23.285
|
Architecture enhancements for V2X services
|
TS
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.285/23285-i00.zip
|
The present document specifies architecture enhancements to facilitate vehicular communications for Vehicle-to-Everything (V2X) services, which includes Vehicle-to-Vehicle (V2V), Vehicle-to-Pedestrian (V2P), Vehicle-to-Infrastructure (V2I), and Vehicle-to-Network (V2N), according to the use cases and service requirements defined in TS 22.185 [2] and TS 22.186 [28].
The following vehicular communications for V2X services are specified:
- V2X communication over PC5 reference point.
- V2X communication over LTE-Uu reference point.
V2X communication over NR PC5 reference point specified in TS 23.287 [30] is supported.
|
23.286
|
Application layer support for Vehicle-to-Everything (V2X) services; Functional architecture and information flows
|
TS
|
18.6.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.286/23286-i60.zip
|
The present document specifies the functional architecture, procedures and information flows for V2X application enabler layer. This specification includes the capabilities of the application layer support for V2X services that are necessary to ensure efficient use and deployment of V2X services over 3GPP systems. The VAE capabilities applies to EPS and 5GS.
|
23.287
|
Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services
|
TS
|
18.4.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.287/23287-i40.zip
|
The present document specifies architecture enhancements to the 5G System to facilitate vehicular communications for Vehicle-to-Everything (V2X) services, over the following reference points, based on service requirements defined in TS 22.185 [2] and TS 22.186 [3]:
- PC5 reference point: NR PC5 RAT, LTE PC5 RAT.
- Uu reference point: NR, E-UTRA.
This specification also covers interworking with EPS.
|
23.292
|
IP Multimedia Subsystem (IMS) centralized services; Stage 2
|
TS
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.292/23292-i00.zip
|
This document specifies the architectural requirements for delivery of consistent services to the user regardless of the attached access type (e.g. CS domain access, or IP-CAN). This is achieved by implementing the services in the IP Multimedia Subsystem (IMS).
Consideration is given to how to access specified IMS-based services (see clause 22.4 of TS 22.101 [9]) whilst still allowing other, bespoke services to be offered by the home operator.
IMS control of services related to those defined in clause 22.4 of TS 22.101 [9] are part of the present scope of this specification.
The scope of the specification includes:
- Session establishment when using CS access for media transmission for an IMS service.
- Support of Service Continuity as specified in TS 23.237 [12].
- Support of Single Radio Voice Call Continuity as specified in TS 23.216 [36].
- Access Domain Selection (ADS).
- IMS control of services where the media is transported via the CS network (e.g. managing of mid-call services).
- Service data management.
The solution is applicable for UEs with or without ICS functionality, and is applicable for the following deployment scenarios:
- An operator who supports for their subscribers only UEs that have ICS functionality.
- An operator who supports for their subscribers only UEs that do not have ICS functionality.
- An operator who supports for their subscribers UEs which do and do not have ICS functionality (to different subscribers and the same subscribers) ensuring the coexistence of UEs that have and do not have ICS functionality.
- Inbound roaming subscribers on an operator's network that supports either the same or different ICS functionality that the inbound roaming subscriber is using, ensuring the coexistence of UEs that have and do not have ICS functionality.
|
23.303
|
Proximity-based services (ProSe); Stage 2
|
TS
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.303/23303-i00.zip
|
The present document specifies the Stage 2 of the Proximity Services (ProSe) features in EPS. ProSe features consist of: ProSe discovery (direct or EPC-level) and ProSe Direct Communication.
ProSe discovery identifies that ProSe-enabled UEs are in proximity, using E-UTRAN (with or without E-UTRAN), WLAN technology or EPC. The details of WLAN-based ProSe Direct Discovery are described in clause 5.3.1.3 and Annex C.
ProSe Direct Communication enables establishment of communication paths between two or more ProSe-enabled UEs that are in direct communication range. The ProSe Direct Communication path could use E-UTRAN or WLAN.
For Public Safety specific usage:
- ProSe-enabled Public Safety UEs can establish the communication path directly between two or more ProSe-enabled Public Safety UEs, regardless of whether the ProSe-enabled Public Safety UE is served by E-UTRAN.
- ProSe Direct Communication is also facilitated by the use of a ProSe UE-to-Network Relay, which acts as a relay between E-UTRAN and UEs.
Security aspects of ProSe are defined in TS 33.303 [29].
|
23.333
|
Multimedia Resource Function Controller (MRFC) - Multimedia Resource Function Processor (MRFP) Mp interface: Procedures descriptions
|
TS
|
18.1.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.333/23333-i10.zip
|
This specification describes the functional requirements and information flows that generate procedures between the Multimedia Resource Function Controller (MRFC) and the Multimedia Resource Function Processor (MRFP), the Mp Interface.
This specification is limited to information flows relevant to the Mp Interface; in order to define these procedures and make the functional requirements clear some triggers from an external interface may be described; these may be specified within the Mr interface for example or within an AS in which the MRFC function resides. However for the overall stage 2 procedures of IMS see 3GPP TS 23.228 [1].
The protocol on the Mp interface is defined to comply with ITU-T H.248.1 Gateway Control Protocol; see [3].The goal of this specification is to provide the input to defining a formal Profile within the H.248 protocol toolbox specifically for the Mp application.
|
23.334
|
IP Multimedia Subsystem (IMS) Application Level Gateway (IMS-ALG) - IMS Access Gateway (IMS-AGW) interface: Procedures descriptions
|
TS
|
18.1.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.334/23334-i10.zip
|
Annex G of 3GPP TS 23.228 [2] gives out an IMS Application Level Gateway (IMS-ALG) and IMS Access Media Gateway (IMS-AGW) based reference model to support NAPT-PT, gate control and traffic policing between IP-CAN and IMS domain.
Figure 1.1: Scope of the specification
Figure 1.1 illustrates the reference model for Iq:
- the dashed line represents the IP signalling-path with SIP (at Gm) as call/session control protocol between the UE and the P-CSCF (IMS-ALG);
- the bold, horizontal line represents the IP media-path (also known as (IP) bearer-path or (IP) data-path; the notion 'media' is used as generic term for "IP application data"); and
- the vertical line represents the Iq control-path with H.248 as gateway/policy control protocol between the IMS-ALG and the IMS-AGW (H.248 messages are transported over IP).
The Iq reference point is between the P-CSCF (IMS-ALG) and the IMS-AGW. It conveys the necessary information that is needed to allocate, modify and release (IP) transport addresses.
The present document defines the stage 2 description for the Iq reference point. The stage 2 shall cover the information flow between the P-CSCF (IMS-ALG) and IMS-AGW. The protocol used over the Iq interface is the gateway control protocol according ITU-T Recommendation H.248 (which is specified for Iq by an H.248 profile according 3GPP TS 29.334 [3]).
|
23.335
|
User Data Convergence (UDC); Technical realization and information flows; Stage 2
|
TS
|
18.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.335/23335-i00.zip
|
The present document describes the procedures and signalling flows associated to the technical realization of the 3GPP User Data Convergence (UDC). It furthermore indicates some requirements for the stage 3 specifications.
Special consideration is put in the following areas:
- reference architecture for the UDC concept
- general description of procedures for the user data manipulation (e.g. create, delete, update, etc.)
- identification of the requirements on the UDC for the applicability of the mechanisms described in this document.
User data convergence is an optional concept to ensure data consistency and simplify creation of new services by providing easy access to the user data, as well as to ensure the consistency of storage and data models and to have minimum impact on traffic mechanisms, reference points and protocols of network elements.
Standization of the Data Model for the Ud interface between Front-Ends and the UDR is out of the scope of 3GPP.
|
23.402
|
Architecture enhancements for non-3GPP accesses
|
TS
|
18.3.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.402/23402-i30.zip
|
This document specifies the stage 2 service description for providing IP connectivity using non-3GPP accesses to the Evolved 3GPP Packet Switched domain. In addition, for E-UTRAN and non-3GPP accesses, the specification describes the Evolved 3GPP PS Domain where the protocols between its Core Network elements are IETF-based.
ITU-T Recommendation I.130 [2] describes a three-stage method for characterisation of telecommunication services, and ITU-T Recommendation Q.65 [3] defines stage 2 of the method.
The specification covers both roaming and non-roaming scenarios and covers all aspects, including mobility between 3GPP and non 3GPP accesses, policy control and charging, and authentication, related to the usage of non-3GPP accesses.
TS 23.401 [4] covers architecture aspects common to the Evolved 3GPP Packet Switched domain.
The procedures defined in the present document for WLAN access selection and PLMN selection replace the corresponding I-WLAN procedures specified in TS 23.234 [5].
Interworking with 5GS is only supported for untrusted non-3GPP access using GTP-based S2b. Enhancements to support interworking with 5GS are captured in TS 23.501 [87] and TS 23.502 [88].
The WLAN Selection Policy specified in clause 4.8.2.1.6 also covers UEs operating in SNPN access mode as defined in TS 23.501 [87].
|
23.468
|
Group Communication System Enablers for LTE (GCSE_LTE); Stage 2
|
TS
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.468/23468-i00.zip
|
The present document provides the stage 2 description for the 3GPP system provided enablers to support group communication services using EUTRAN access. The corresponding stage 1 requirements are defined in TS 22.468 [2].
The group communication system is represented by an Application Server (GCS AS) using the 3GPP system provided enablers for transferring its application signalling and for delivering application data, e.g. media data, to a group of UEs either (i) over MBMS Bearer Services using the Broadcast Mode of MBMS (TS 23.246 [3]); or (ii) over EPS Bearers; or (iii) over both MBMS and EPS bearer services.
The specification covers both roaming and non-roaming scenarios and also includes support for service continuity, i.e. support for continuous reception of application data when a UE changes between reception of application data via EPS and MBMS Bearer Services.
Application level interactions between the UE and the GCS Application Server are out of scope of this specification.
|
23.479
|
Technical Specification Group Services and System Aspects; UE MBMS APIs for Mission Critical Services;
|
TS
|
18.0.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.479/23479-i00.zip
|
The present document defines the application programming interface on the UE for mission critical applications to access mission critical services over MBMS.
This document identifies system architecture and functional model for the definition of the MBMS API for mission critical services.
|
23.586
|
Architectural Enhancements to support Ranging based services and Sidelink Positioning
|
TS
|
18.7.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.586/23586-i70.zip
|
The present document specifies the stage 2 of the Ranging based services and Sidelink positioning in 5G System for commercial, V2X and public safety use cases in in-coverage, partial coverage, and out-of-coverage of 5G network using 5G NR PC5 RAT.
Radio aspects of Ranging based services and Sidelink positioning in 5GS are defined in TS 38.355 [12] and TS 38.305 [5].
Security aspects of Ranging based services and Sidelink positioning in 5GS are defined in TS 33.533 [13].
|
23.700-05
|
Study on architecture enhancements for vehicle-mounted relays
|
TR
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-05/23700-05-i00.zip
|
The scope of this Technical Report is to study and identify potential architecture and system level enhancements for the 5G system to support the operation of base station relays mounted on vehicles, using NR for wireless access toward the UE and for wireless access through an IAB-donor toward the 5GC, i.e. in this release only IAB type relays based on the IAB architecture and functionalities specified in TS 23.501 [2] are studied. The study addresses the service requirements documented in TS 22.261 [3] for the mobile base station relays, and focuses on the following aspects:
- efficient mobility and service continuity for UE or a group of UEs to efficiently deliver data during different mobility scenarios (including mobility of the mobile base station relays);
- provisioning, policies and mechanisms to e.g. manage relay configuration, geographic restrictions, QoS, authorization and control of UEs' access via the mobile base station relay, etc.;
- support for roaming of mobile base station relay (including the roaming of the IAB-UE and gNB-DU in IAB-node), support for regulatory requirements (e.g. emergency, priority services, public safety), and support for location services for UEs accessing a mobile base station relay.
|
23.700-08
|
Study on enhanced support of Non-Public Networks; Phase 2
|
TR
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-08/23700-08-i00.zip
|
The scope of this Technical Report is to study further enhancements of the 5GS to support Non-Public Networks including the following aspects:
1. Support for enhanced mobility by enabling support for idle and connected mode mobility between SNPNs without new network selection.
2. Support for non-3GPP access for SNPN.
3. Address SA WG1 requirements in TS 22.261 [2] related to support for Providing Access to Localized Services.
NOTE: The TS 22.261 [2] requirements for Providing Access to Local Services related to Multicast/Broadcast are not part of the scope.
|
23.700-17
|
Study on Wireless and Wireline Convergence for the 5G System (5GS) (5WWC); Phase 2
|
TR
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-17/23700-17-i00.zip
|
The Technical Report studies and performs evaluations of potential architecture enhancements to enhance the support of Wireline-Wireless convergence in the 5G Core network (5GC). Specifically, two objectives are included:
- Work task #2: Whether and how to improve the support of devices connecting behind 5G-RG including:
Providing differentiated service (e.g. QoS and charging) for UE and Non-3GPP devices connected behind a 5G RG. This may imply s studying ways for 5GC to identify Non-3GPP devices connected behind a 5G RG and/or their traffic. Conclusions may differ for UE and for Non-3GPP devices.
- Work task #3: Trusted/untrusted Non-3GPP access network: How to select a TNGF/N3IWF that supports the S-NSSAI(s) needed by the UE.
|
23.700-18
|
Study on system enabler for service function chaining
|
TR
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-18/23700-18-i00.zip
|
The Technical Report studies and performs evaluations of potential architecture enhancements to enhance the support of service function chaining in the 5G Core network (5GC). Specifically, two objectives are included:
WT#2: Investigate whether traffic steering policy is sufficient to support SA WG1 requirements in TS 22.101 [5], TS 22.261 [6] and TS 22.115 [7], study whether and how to define Service Function Chaining (SFC) policies, and investigate solutions and procedures for the 5G network with SFC capabilities to identify/detect/classify user plane traffic and steer the traffic to a chain of ordered service functions for SFC processing in non-roaming and home routed roaming scenarios.
WT#3: Depending on the outcome of WT#2, specify possible enhancement to northbound APIs for allowing an AF to request network capability exposure functionalities, e.g. request a service function chain for a certain traffic flow, etc. based on service level agreement with the third party.
NOTE 1: This study considers only traffic handled over N6 by PSA UPF(s) in 5G network.
NOTE 2: The definition of terms in RFC 7665 [8] may be re-used when applicable. The study targets the use of traffic steering concept, e.g. defined by 3GPP (FMSS) and SFC mechanisms defined in IETF when applicable. Especially the study aims at reusing user plane mechanisms (e.g. VXLAN, NSH, GENEVE, GRE, VLAN, etc.) defined at IETF to support SFC, as applicable.
NOTE 3: The study for SFC will ensure that existing (per 3GPP Rel-17) deployments flexibility can be preserved in deployments of SFC in 5G network.
NOTE 4: The study assumes a Home Routed roaming PDU Session does not have an offloading point in a VPLMN.
|
23.700-25
|
Study on timing resiliency and TSC and URLLC enhancements
|
TR
|
18.1.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-25/23700-25-i10.zip
|
The objective of this Technical Report is to study and perform an evaluation of potential architecture enhancements for supporting 5G Timing Resiliency and TSC & URLLC enhancements for 5G System (5GS). The following aspects are covered:
- Study how to report 5GS network timing synchronization status (such as divergence from UTC and 5GS network timing source degradation) to UEs and 3rd party applications (AFs):
- Study how RAN and 5GC learn about network 5GS network timing synchronization status to be able to inform UEs and AFs.
- Study if additional information needs to be provided to UEs and AFs to inform about 5GS network timing synchronization status.
- Study how to enable AFs to request time synchronization service in a specific coverage area and how to enforce the coverage area.
- Study how to control 5G time synchronization service based on subscription (i.e. introducing subscription parameter for time synchronization and enforcing it).
- Study how to enable an AF to explicitly provide PER to NEF/PCF.
- Study mechanisms for interworking with TSN transport networks. Study interworking mechanisms with TSN networks deployed in the transport network in order to support of E2E determinism and low latency communication and efficient N3 transmission.
- Study if there is a need for applications to adapt downstream scheduling in order for 5GS to meet really low latency (e.g. 2 msecs) requirement and if there is a need to have feedback from RAN (e.g. for application to consider DL packet transmission time slots to avoid buffering in the RAN) for this purpose.
|
23.700-27
|
Study on 5G System with Satellite Backhaul
|
TR
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-27/23700-27-i00.zip
|
The scope of this Technical Report is to study the following aspects of 5GS with satellite backhaul:
1: Architecture enhancements for support of a backhaul with changing delay (e.g. brought by ISL in satellite networks or changed satellite backhaul on the UP path), and possibly limited bandwidth in case of a gNB with satellite backhaul only (e.g. restricted by the maximum data rate of a satellite beam):
- Policy/QoS control enhancements based on the detected packet delivery latency and/or bandwidth of the satellite backhaul on the UP path;
- Exposure of backhaul information to AFs.
2: Architecture enhancements for support of UPF deployed on GEO satellite with gNB on the ground:
- Whether and how to enable satellite edge computing services via UPF on-board e.g. to reduce the latency for data transmission, and minimize the backhaul resources consumption.
- How to enhance local switch for UEs in a communication when they are served by UPF on-board, e.g. to reduce end to end delay comparing with existing 5G LAN local switch at PSA on the ground.
|
23.700-28
|
Study on Integration of satellite components in the 5G architecture; Phase 2
|
TR
|
18.1.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-28/23700-28-i10.zip
|
The scope of the TR is to investigate further 5GC/EPC enhancements to support satellite access using the work done in Release 17 as baseline with the following 5GC/EPC areas for study:
- Possible enhancements to support of Discontinuous coverage with the following areas of focus:
- Architectural enhancements to support discontinuous coverage for mobility enhancement (e.g. paging enhancement).
- Architectural enhancements considering prediction, awareness and notification of UE wake-up time, power saving optimizations.
|
23.700-33
|
Study on System enhancement for Proximity based Services (ProSe) in the 5G System (5GS); Phase 2
|
TR
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-33/23700-33-i00.zip
|
The scope of this Technical Report is to study and evaluate the possible architecture enhancements to the 5G Proximity-based Services (5G ProSe) system defined in TS 23.304 [3], based on the relevant Stage 1 requirements defined in TS 22.261 [4], TS 22.278 [5] and TS 22.115 [6] and determine which of the solutions can proceed to normative specifications.
This study will consider architecture enhancements in the following areas:
- Support of single NR PC5 hop UE-to-UE Relay for unicast.
- Enhancement of 5G ProSe UE-to-Network Relay functionality.
- Support of path switching between direct NR Uu communication path and direct NR PC5 communication path (i.e. non-relay case).
|
23.700-34
|
Study on SEAL data delivery enabler for vertical applications
|
TR
|
18.1.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-34/23700-34-i10.zip
|
The present document is a technical report which identifies the application enabling layer platform architecture, capabilities and services to efficiently support distribution, storage and delivery for the application content/data for vertical applications.
The study takes into consideration the existing stage 1 and stage 2 work within 3GPP related to data delivery and 3GPP system user plane aspects specified in 3GPP TS 22.261 [2], 3GPP TS 23.501 [6] and 3GPP TS 23.247 [4].
This document will provide recommendations for normative work.
|
23.700-36
|
Study on Application Data Analytics Enablement Service
|
TR
|
18.1.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-36/23700-36-i10.zip
|
The present document is a technical report which identifies the application enabling layer platform architecture, capabilities, and services to support data analytics enablement at the application layer.
The aspects of the study include the investigation of application data analytics services to optimize the application service operation, edge/cloud analytics enablement, data collection aspects per identified application data analytics service, coordination of data collection from multiple sources and unified exposure of data analytics to the vertical/ASP. This study will also identify potential enhancements to existing enablement layer entities (SEAL, eEDGEAPP, vertical specific enablers) to consume application data analytics enablement services.
The study takes into consideration the work done for data analytics in 3GPP TS 23.288 [2] and 3GPP TS 28.104 [3] and other related work outside 3GPP.
|
23.700-38
|
Study on sharing of administrative configuration between interconnected MC service systems
|
TR
|
18.0.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-38/23700-38-i00.zip
|
The present document studies sharing of administrative configuration between interconnected MC service systems, based on stage 1 requirements specified in 3GPP TS 22.280 [2].
This study investigates related use cases and identifies solutions to support exchange administrative configuration, security relevant data and information between interconnected MC service systems.
|
23.700-41
|
Study on enhancement of network slicing; Phase 3
|
TR
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-41/23700-41-i00.zip
|
The Technical Report studies the gaps and performs evaluations of potential architecture enhancements to support Network Slicing with the following objectives:
1. Study whether and how to address the following scenario in order to provide service continuity: if an existing network slice or network slice instance cannot serve the PDU session, or if the existing network slice instance cannot meet the performance requirements of the applications. The study should investigate whether deployment optimization is sufficient. Minimized system optimisations can be considered if valuable.
2. Study whether and how to initiate a registration for a rejected S-NSSAI that was rejected in a first TA of the RA but may be available in another TA of the RA.
3. Study whether and how to support the following stage one Rel-18 EASNS requirements related to roaming specified in TS 22.261 clause 6.1.2.1, i.e. Requirement on enhancement the information available to the UE in roaming scenarios regarding the availability of network slices in VPLMNs available in the roaming country, in order to allow the UE to select and obtain services from the VPLMN supporting the network slices which UE may wish to use.
4. Study whether and how to enhance the system to ensure network controlled behaviour of network slice usage including UE registration and PDU Session establishment (e.g. so that when performing NSAC the network slice can serve UEs/PDU Sessions with actual activity).
5 Study deployment considerations when a service provided has an area of service that does not overlap with the already deployed Tracking Areas and/or have a limited lifetime and how existing mechanisms including network slicing can help support such scenarios. If existing mechanisms are concluded to be not sufficient to achieve the scenarios, study whether and how additional mechanisms can resolve the analysed gap.
6. Study whether and how to enhance the support of NSAC when more than one NSACF is involved in enforcing a shared maximum allowed number of the UEs or PDU Sessions for a network slice in one PLMN or in roaming, in order to avoid fragmentation of the shared maximum allowed number. This item depends on the outcome of corresponding Rel-17 CRs.
|
23.700-46
|
Study on 5GS Deterministic Networking (DetNet) interworking
|
TR
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-46/23700-46-i00.zip
|
The objective of this Technical Report is to study whether and how to enable 3GPP support for DetNet such that a mapping is provided between the central DetNet controller entity (as defined in IETF) and the 5G system. Mapping involves translation of DetNet traffic profile and flow specification to 5GS QoS parameters and TSCAI. The study also considers which information needs to be exposed from the 5G system to the DetNet controller.
The study scope assumes the following:
- Only IP based DetNet is in the scope of the work; MPLS based DetNet is out of scope.
- DetNet over Ethernet TSN is not in the scope of the work as it can be supported based on existing 3GPP and IETF standards.
- It is out of scope to support for edge DetNet node functions in the 3GPP network.
|
23.700-47
|
Study on architectural enhancements for 5G multicast-broadcast services; Phase 2
|
TR
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-47/23700-47-i00.zip
|
This Technical Report studies and evaluates further enhancements to the 5G Multicast/Broadcast Architecture in order to provide the following features.
- Enabling UE's receiving Multicast MBS Session data in RRC Inactive state.
- Study feasible and efficient resource utilization for the same broadcast content to be provided to 5G MOCN network sharing scenarios (i.e. multiple CNs are connected to the same NG-RAN).
- Study whether and how to support on demand multicast MBS session triggered by AF, and efficient resource utilization via 5GC choosing multicast and/or unicast delivery for a certain service.
- Study whether and how to support group message delivery for capability-limited devices, including NEF enhancement, coexistence of existing power saving mechanisms and MBS.
- Study whether there are any identified performance issues for high number of public safety UEs, and if yes study necessary enhancements to 5MBS for that scenario.
|
23.700-48
|
5G System Enhancements for Edge Computing; Phase 2
|
TR
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-48/23700-48-i00.zip
|
The present document describes key issues and solutions for the phase 2 of the system enhancements for Edge Computing in 5GS.
Edge Computing is supported in 5GS since Rel-15. During Rel-17 FS_enh_EC study described in TR 23.748 [4] , further enhancements for supporting Edge Computing have been studied, including discovery and re-discovery of EAS, edge relocation etc. 4 key issues from FS_enh_EC study have been concluded and progressed in TS 23.548 [3]. Some other issues were raised during the Rel-17 study but not studied due to the time limitation in Rel-17.
This technical report will document the study of potential system enhancements for enhanced edge computing support, including:
- improvements to roaming, to support access to EHE in a VPLMN (WT#1);
- defining use cases that may benefit from exposure of additional data via the Local UPF/NEF including describing (on a high level) the characteristics of the data and data delivery to fulfil the use cases; investigating the solutions and their feasibility and suitability for improved network exposure of UE traffic related information to common Edge Application Server via Local UPF/NEF, such as network congestion status (WT#3);
NOTE 1: XR/media and AI/ML services specific QoS information exposure are to be studied in corresponding study items with considering the same exposure framework as defined by this study.
NOTE 2: This objective will look at the use cases and the data to be exposed but not at the actual UPF exposure mechanism or UPF-originated data, if/when already covered by FS_UPEAS.
- investigating the potential need and solutions for supporting offload policies to match more granular sets of UE(s) without exposing operator-internal configurations to 3rd party AFs (WT#5);
- investigating the potential need and solutions to influence of PSA-UPF and EAS (re)location for collection of UEs, e.g. in scenarios when UE(s) should use the same EAS and are not members of a pre-defined group (WT#6);
- investigating potential impacts related to the GSMA Operator Platform Group work, and potential improvements related with 5GC and EHE being operated by different organizations (WT#7);
- investigating the potential need and solutions to avoid the UE to switch the EC traffic away from the EC PDU Session and 5GS altogether, due to conflicting connectivity preferences in the device (e.g. via means outside of 3GPP connectivity, e.g. non-integrated Wifi) (WT#8);
- investigating the potential solutions for the AF to be able to obtain/determine the DNAI that is associated to a certain selected EAS, for subsequent use with already defined services provided to the AF (WT#9).
|
23.700-55
|
Study on enhanced Application Architecture for UAS applications
|
TR
|
18.0.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-55/23700-55-i00.zip
|
The present document analyze requirements and identify key issues and develop potential enhancements to the UAS application architecture. The study includes identification of potential enhancements to the UAS architecture, potential enhancements to the Service Enabler Architecture Layer (SEAL) and corresponding application requirements.
The study bases its work on the existing stage 1 work within 3GPP related to UAS as specified in 3GPP TS 22.125 [2].
The conclusions of the study will be aligned with 3GPP TR 23.700-58 [6]. The recommendations from the study include solutions for the UAS architecture and SEAL that will be considered for normative work.
|
23.700-53
|
Study on access traffic steering, switching and splitting support in the 5G system architecture; Phase 3
|
TR
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-53/23700-53-i00.zip
|
The purpose of this Technical Report is to enhance the ATSSS feature by investigating solutions that can support the following capabilities:
1) Support new steering functionalities that can steer/switch/split non-TCP traffic flows (e.g. UDP traffic flows and IP traffic flows). Two types of such steering functionalities are studied: (i) a steering functionality based on the QUIC protocol and its multipath extensions, and (ii) a steering functionality based on the DCCP protocol and its multipath extensions.
2) Support redundant traffic steering for both GBR and non-GBR traffic flows. With redundant traffic steering, a traffic flow (GBR or non-GBR) can be replicated on multiple access paths and, therefore, can improve transmission reliability and reduce packet latency.
3) Support traffic switching between one non-3GPP access path, from a UE to a N3IWF in a PLMN, and another non-3GPP access path, from the UE to a TNGF in the same PLMN.
4) Support the establishment of a MA PDU Session with one 3GPP access path via 5GC and one non-3GPP access path via ePDG/EPC. This is to complement the existing ATSSS capability that supports the establishment of a MA PDU Session with one non-3GPP access path via 5GC and one 3GPP access path via EPC.
For each of the above capabilities, the conclusions of the study identify whether a solution is required for the normative phase and, if required, which solution to consider in the normative phase.
|
23.700-58
|
Study of further architecture enhancements for uncrewed aerial systems and urban air mobility
|
TR
|
18.1.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-58/23700-58-i10.zip
|
This study item shall address the following system enablers for 5GS and EPS to support additional scenarios and requirements for UAV (Uncrewed Aerial Vehicles) and UAM (Urban Air Mobility) by identifying how and whether existing mechanisms can be re-used, and identifying architectural and functional modifications required:
- a mechanism to transport Broadcast Remote Identification and C2 communications via the 3GPP system;
- a mechanism to support aviation applications such as Detect And Avoid (DAA).
|
23.700-60
|
Study on XR (Extended Reality) and media services
|
TR
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-60/23700-60-i00.zip
|
The Technical Report studies key issues, solutions and conclusions on the support of advanced media services, e.g. High Data Rate Low Latency (HDRLL) services, AR/VR/XR services, and tactile/multi-modality communication services. The objectives include:
Enhancements for supporting multi-modality service:
- Study whether and how to enable delivery of related tactile and multi-modal data (e.g. audio, video and haptic data related to a specific time) with an application to the user at a similar time, focusing on the need for policy control enhancements (e.g. QoS policy coordination).
Enhancements of network exposure to support interaction between 5GS and application:
- Study whether and how interaction between AF and 5GS is needed for application synchronization and QoS policy coordination among multiple UEs or between multiple QoS flows per UE.
- Study exposure of 5GS QoS information (e.g. QoS capabilities) and network conditions to the Application to enable quick codec/rate adaptation help to provide desired QoE (e.g. such as assist in alleviating 5GS congestion).
Study whether and how the following QoS and policy enhancements for XR service and media service transmission are performed:
- Study the traffic characteristics of media service enabling improved network resources usage and QoE.
- Enhance QoS framework to support PDU Set granularity (e.g. video/audio frame/tile, Application Data Unit, control information), where a PDU Set consists of PDUs that have the same QoS requirements.
- Support differentiated QoS handling considering different importance of PDU Sets. e.g. eligible drop packets belong to a less important PDU Set to reduce the resource wasting.
- Whether and how to support uplink-downlink transmission coordination to meet RTT (Round-Trip Time) latency requirements between UE and N6 termination point at the UPF.
- Potential policy enhancements to minimize the jitter, focusing on i.e. requirement provisioning from AF, extension of PCC rule.
Study potential enhancements of power management considering traffic pattern of media services:
- Power saving enhancement e.g. support trade-off of throughput/latency/reliability considering device battery life, whether and how to enhance CDRX, considering XR/media traffic pattern.
NOTE: Whether to define a network slice type supporting media services can be determined during normative phase.
|
23.700-61
|
Study on Seamless UE context recovery
|
TR
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-61/23700-61-i00.zip
|
This study will focus on the mechanism to determine the "unavailability period" in the 5G system for the UE.
|
23.700-62
|
Study on UPF enhancement for Exposure And SBA
|
TR
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-62/23700-62-i00.zip
|
The Technical Report studies on key issue description, solution and conclusion on the support of better integration of UPF into the 5GC SBA. The objectives include:
- Study UPF event exposure service(s) registration/deregistration, and discovery via the NRF.
- Study UPF event exposure service(s) that would support, e.g.:
- Consumption of UPF exposure services by the PCF, NWDAF, CHF, NEF, Trusted AF and other NFs (if needed).
- (To support the UPF exposure service, if needed) Use of SMF services, PCF services, NWDAF services, CHF services, NEF services, Trusted AF services by the UPF.
NOTE 1: This will not define solutions where UPF exposes information that it is not originator of, i.e. not re-expose information owned and exposed by other NFs.
- Relevant Event IDs.
- Evaluate usage of UPF event exposure service(s) as defined in WT#2 also considering the architectural impacts.
NOTE 2: SMF is responsible for controlling UPF packet processing.
NOTE 3: The performance of UP traffic handling shall not be degraded due to mechanisms defined in this study.
NOTE 4: The study shall address generic UPF data exposure mechanisms via SBA based mechanisms, and the coordination with other SIDs for this aspect may be needed in study phase.
This study shall maintain the Rel‑17 backward compatibility on the N3, N6, N9, N4 interfaces.
|
23.700-64
|
Study on enhancements to application layer support for V2X services; Phase 2
|
TR
|
18.1.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-64/23700-64-i10.zip
|
The present document is a technical report which identifies the enhancements to the application architecture to support V2X services specified in 3GPP TS 23.286 [6] considering advanced V2X services like V2P, ToD, etc and edge computing deployments for V2X services.
The study takes into consideration the existing stage 1 and stage 2 work within 3GPP related to advanced V2X services and edge computing in 3GPP TS 22.185 [2], 3GPP TS 22.186 [3], 3GPP TS 23.285 [5], 3GPP TS 23.287 [7], 3GPP TS 23.548 [10] and 3GPP TS 23.558 [11].
The study also takes into consideration the V2X application specific services and recommendations specified by automotive industry bodies (5GAA, ETSI ITS and AECC) related to advanced V2X services for VRU, Haptics/ToD and edge deployments for V2X services.
This document will provide recommendations for normative work.
|
23.700-68
|
Study on Support of reduced capability NR devices; Phase 2
|
TR
|
18.1.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-68/23700-68-i10.zip
|
The scope of the present document is to investigate solutions to support of RRC INACTIVE state with extended DRX cycle longer than 10.24s to enrich the power saving function as studied in TR 38.875 [5].
This study will address the following objective:
Support for enabling of eDRX cycle that is longer than 10.24s in RRC_INACTIVE state with following two aspects:
1) Study the support of the eDRX cycle that is longer than 10.24s and up to 10485.76s for RRC_INACTIVE state for RAN paging (e.g. PTW and eDRX cycle values).
2) Study the MT signalling and data handling for UE with long eDRX cycle in RRC_INACTIVE state.
|
23.700-71
|
Study on enhancement to the 5GC LoCation Services (LCS); Phase 3
|
TR
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-71/23700-71-i00.zip
|
The scope of this Technical Report is to study further enhancements to the to the 5GC LoCation Services including the following aspects:
- Investigate potential architectural enhancements to location service (e.g. in scenarios like edge computing, and other), i.e. support Positioning Signalling via user plane.
- Investigate potential architectural enhancements to location service (e.g. in scenarios like edge computing, and other), i.e. reduction of location service latency, signalling overhead and location estimate exposure.
- Study how the location services can benefit from NWDAF reporting and how the NWDAF use cases can benefit from location services, e.g. enhanced accuracy in certain UE location or population flow statistics data that require UE locations smaller than TA/cell
- Study enhancements to support low power positioning (e.g. for RedCap) including the requirements related to low power high accuracy positioning described in TS 22.104 [7].
- Study necessary enhancement to support regulatory requirement i.e. the network should not notify the UE by any means during the LCS session.
- Study enhancement to support the Flexible and Efficient Periodic and Triggered Location for UE power saving purpose.
- In collaboration with RAN, study specific network functionality related to use of Positioning Reference Units (PRUs) as defined by RAN WGs and study how 5GS to support a specific UE (i.e. Reference UE) to improve the accuracy of positioning, and reduce the signalling:
- Study enhancements to support the location service continuity for UE mobility, i.e. between EPS and 5GS;
- For 5G with satellite access, in collaboration with RAN, study LCS architectural enhancement to support network verified UE location, and to meet location services related requirements defined in TS 22.261 [8].
|
23.700-74
|
Study on generic group management, exposure and communication enhancements
|
TR
|
18.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-74/23700-74-i00.zip
|
The scope of this Technical Report is to study potential enhancements on generic group management, exposure and communication. Specifically, the following aspects are in the scope of the study:
- Enhance group attribute management and group status event reporting:
- set/modify the group attributes: provisioning of service area or QoS applicable to each UE of a given group;
- subscribe to group status event reporting for the event "newly registered or (de)-registered group member".
- Study whether and how to enhance NEF exposure framework to enable capability exposure for provisioning of traffic characteristics and monitoring of performance characteristics applicable to each UE of a given group.
- Support group communication for a 5G VN, which supports multiple SMFs, including support of SMF redundancy for reliability of the 5G VN group communication.
- Whether additional mechanism or enhancement is needed and how to support group communication allowing UE to simultaneously send data to different groups, where each group has a different QoS policy (requirement regarding 5SEI as indicated in clause 6.13.2 of TS 22.261 [6]).
|
23.700-76
|
Study on ad hoc group communication support for mission critical services
|
TR
|
18.0.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-76/23700-76-i00.zip
|
The present document studies solutions to satisfy the requirements identified to support Ad hoc group communication for MCX services. It identifies enhancements to be included in the technical specifications for MCPTT, MCVideo, MCData and in the common functional architecture to support Ad hoc group communications. Requirements for this study are taken from 3GPP TS 22.280 [3].
|
23.700-78
|
Study on Application layer support for Personal IoT Network
|
TR
|
18.1.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-78/23700-78-i10.zip
|
The present document is a technical report capturing the study on application layer support for Personal IoT networks (PIN). The aspects of the study include analyzing application layer architecture requirements of PIN, identifying key issues and supporting PIN application layer functional model. The study also includes information and support from 3GPP network to PIN, service or applications discovery within a PIN or by the UE outside of a PIN via 3GPP network.
The study takes into consideration the work done for PIN in 3GPP TS 23.700-88 [4] and other related work in 3GPP.
|
23.700-79
|
Study of gateway User Equipment (UE) function for Mission Critical (MC) communications
|
TR
|
18.0.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.700-79/23700-79-i00.zip
|
The present document studies solutions to satisfy the requirements for a Gateway UE function. It identifies enhancements to be included in the technical specifications for MCPTT, MCVideo, MCData and in the common functional architecture to support mission critical communications. Requirements for this study are taken from stage 1 requirements, including 3GPP TS 22.179 [2] and 3GPP TS 22.280 [3].
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.