id
stringlengths 5
12
| title
stringlengths 8
250
| type
stringclasses 2
values | version
stringclasses 212
values | working_group
stringclasses 30
values | url
stringlengths 67
81
| scope
stringlengths 0
65.7k
|
|---|---|---|---|---|---|---|
22.973
|
IMS Multimedia Telephony service; and supplementary services
|
TR
|
19.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.973/22973-j00.zip
| |
22.979
|
Feasibility study on combined Circuit Switched (CS) calls and IP Multimedia Subsystem (IMS) sessions
|
TR
|
19.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.979/22979-j00.zip
| |
22.953
|
Multimedia priority service feasibility study
|
TR
|
19.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.953/22953-j00.zip
| |
22.850
|
Study on 3GPP AI/ML Consistency Alignment
|
TS
|
0.5.0
|
SP
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.850/22850-050.zip
| |
22.968
|
Study for requirements for a Public Warning System (PWS) service
|
TR
|
19.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.968/22968-j00.zip
| |
23.007
|
Restoration procedures
|
TS
|
19.2.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.007/23007-j20.zip
|
The data stored in location registers are automatically updated in normal operation; the main information stored in a location register defines the location of each mobile station and the subscriber data required to handle traffic for each mobile subscriber. The loss or corruption of these data will seriously degrade the service offered to mobile subscribers; it is therefore necessary to define procedures to limit the effects of failure of a location register, and to restore the location register data automatically. The present document defines the necessary procedures.
The basic principle is that restoration should be based on radio contact to avoid faulty data being spread in the system.
Subscriber data for supplementary services must also be correctly restored, although the impact on service of corruption of supplementary service data is less severe.
Procedures for supporting these functions are defined in 3GPP TS 29.002 [6] and 3GPP TS 29.060 [8].
The MAP operation "IMSI Attach" is used only in MAP version 1; in MAP version 2 the same function is performed by the MAP operation "Update Location Area". References in this specification to IMSI attach apply only to MAP version 1 network entities.
If the restoration of subscriber data in the VLR is triggered by Location Updating or IMSI Attach, the VLR retrieves subscriber data from the HLR by sending an "Update Location" request, which triggers one or more "Insert Subscriber Data" operations from the HLR. The "Update Location" request may also be used to send the LMSI to the HLR.
If the restoration of subscriber data in the VLR is triggered by a "Provide Roaming Number" request, the behaviour of the VLR depends on whether it is implemented according to MAP version 1 or MAP version 2. For MAP version 2, the VLR retrieves subscriber data from the HLR by sending a "Restore Data" request, which triggers one or more "Insert Subscriber Data" operations from the HLR. The "Restore Data" request is also used to send the LMSI to the HLR. For MAP version 1, the VLR retrieves subscriber data from the HLR by sending a "Send Parameters" request with parameter type "Subscriber Data", which cannot be used to send the LMSI to the HLR.
The VLR number and MSC number in the subscriber data in the HLR are updated by the "Update Location" procedure.
The GGSN (Gateway GPRS Support Node) is the point of PDN interconnection with the GSM PLMN supporting GPRS. The GGSN contains routing information for GPRS users with a PDP context active. The necessary procedures needed to restore GGSN data information after a restart are described in this document.
The SGSN (Serving GPRS Support Node) is the node that is serving the MS. The SGSN stores information regarding e.g. mobility management, routing and security. The necessary procedures needed to restore this SGSN information after a restart are described in this document.
The MME (Mobility Management Entity) is the node that is serving the UE when attached to E-UTRAN. The MME stores information regarding e.g. mobility management, routing and security. The necessary procedures needed to restore this MME information after a restart are described in this document.
A Type A LMU (Location Measurement Unit) is a network node, accessed over the GSM air interface, that is functionally similar to an MS. All requirements associated with a non-GPRS MS in this specification apply also to a Type A LMU except where specified otherwise.
|
23.008
|
Organization of subscriber data
|
TS
|
19.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.008/23008-j00.zip
|
The present document provides details concerning information to be stored in the different entities storing data within a 3GPP network concerning mobile subscriber. A list of entities storing subscriber data is provided in clause 1.
Clause 2 contains all details concerning the definition of the parameters, often given by reference to other specifications, and where the parameter is to be stored.
Table 1 in clause 3 gives a summary overview and clause 4 identifies the reference information required for accessing the information.
In this specification, if there is no specific indication, the following principles apply:
- "SGSN" refers to an SGSN which may support the Gn and Gp interfaces or the S4 interface or both.
- "S4-SGSN" refers to an SGSN which only supports the S4 interface.
- "Gn/Gp-SGSN" refers to an SGSN which only supports the Gn and Gp interfaces.
|
22.983
|
Services alignment and migration
|
TR
|
19.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.983/22983-j00.zip
| |
22.951
|
Service aspects and requirements for network sharing
|
TR
|
19.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.951/22951-j00.zip
| |
22.982
|
Study of Customised Alerting Tone (CAT) requirements
|
TR
|
19.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.982/22982-j00.zip
| |
22.985
|
Service requirements for the User Data Convergence (UDC)
|
TR
|
19.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.985/22985-j00.zip
| |
23.015
|
Technical realization of Operator Determined Barring (ODB)
|
TS
|
19.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.015/23015-j00.zip
|
The network feature Operator Determined Barring (ODB) allows a network operator or service provider to regulate access by subscribers to services (Circuit/Packet Oriented and Interworking WLAN), by the barring of certain categories of incoming or outgoing calls/ Packet Oriented Services or of roaming. Operator Determined Barring applies to all bearer services and teleservices except the Emergency Call teleservice and Emergency Bearer Services; the teleservice Short Message Point-to-Point is therefore subject to Operator Determined Barring in the same way as circuit-switched calls.
The application of specific categories of Operator Determined Barring to a subscription is controlled by the network operator or service provider, using administrative interaction at the HLR; this interface is not standardised.
|
22.952
|
Priority service guide
|
TR
|
19.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.952/22952-j00.zip
| |
22.980
|
Network composition feasibility study
|
TR
|
19.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.980/22980-j00.zip
| |
22.986
|
Study on Service Specific Access Control
|
TR
|
19.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.986/22986-j00.zip
| |
22.987
|
Study of haptic services requirements
|
TR
|
19.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.987/22987-j00.zip
| |
22.988
|
Study on alternatives to E.164 for Machine-Type Communications (MTC)
|
TR
|
19.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.988/22988-j00.zip
| |
23.014
|
Support of Dual Tone Multi-Frequency (DTMF) signalling
|
TS
|
19.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.014/23014-j00.zip
| |
23.011
|
Technical realization of Supplementary Services
|
TS
|
19.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.011/23011-j00.zip
| |
22.990
|
Study on off-network for rail
|
TR
|
19.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.990/22990-j00.zip
| |
23.016
|
Subscriber data management; Stage 2
|
TS
|
19.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.016/23016-j00.zip
| |
23.031
|
3G Security; Fraud Information Gathering System (FIGS); Technical realization; Stage 2
|
TS
|
19.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.031/23031-j00.zip
| |
23.035
|
Immediate Service Termination (IST); Stage 2
|
TS
|
19.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.035/23035-j00.zip
| |
23.012
|
Location management procedures
|
TS
|
19.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.012/23012-j00.zip
| |
23.034
|
High Speed Circuit Switched Data (HSCSD); Stage 2
|
TS
|
19.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.034/23034-j00.zip
| |
23.032
|
Universal Geographical Area Description (GAD)
|
TS
|
19.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.032/23032-j00.zip
| |
23.053
|
Tandem Free Operation (TFO); Service description; Stage 2
|
TS
|
19.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.053/23053-j00.zip
| |
23.018
|
Basic call handling; Technical realization
|
TS
|
19.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.018/23018-j00.zip
| |
23.009
|
Handover procedures
|
TS
|
19.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.009/23009-j00.zip
| |
23.042
|
Compression algorithm for text messaging services
|
TS
|
19.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.042/23042-j00.zip
| |
22.978
|
All-IP network (AIPN) feasibility study
|
TR
|
19.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.978/22978-j00.zip
| |
23.002
|
Network architecture
|
TS
|
19.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.002/23002-j00.zip
| |
23.003
|
Numbering, addressing and identification
|
TS
|
19.4.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.003/23003-j40.zip
| |
23.067
|
enhanced Multi-Level Precedence and Pre-emption Service (eMLPP); Stage 2
|
TS
|
19.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.067/23067-j00.zip
| |
23.057
|
Mobile Execution Environment (MExE); Functional description; Stage 2
|
TS
|
19.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.057/23057-j00.zip
| |
23.066
|
Support of Mobile Number Portability (MNP); Technical realization; Stage 2
|
TS
|
19.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.066/23066-j00.zip
| |
23.072
|
Call Deflection (CD) supplementary service; Stage 2
|
TS
|
19.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.072/23072-j00.zip
| |
23.041
|
Technical realization of Cell Broadcast Service (CBS)
|
TS
|
19.2.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.041/23041-j20.zip
| |
23.079
|
Support of Optimal Routeing (SOR); Technical realization
|
TS
|
19.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.079/23079-j00.zip
| |
23.081
|
Line Identification supplementary services; Stage 2
|
TS
|
19.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.081/23081-j00.zip
| |
23.084
|
Multi Party (MPTY) supplementary service; Stage 2
|
TS
|
19.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.084/23084-j00.zip
| |
23.085
|
Closed User Group (CUG) supplementary service; Stage 2
|
TS
|
19.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.085/23085-j00.zip
| |
23.086
|
Advice of Charge (AoC) supplementary services; Stage 2
|
TS
|
19.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.086/23086-j00.zip
| |
23.083
|
Call Waiting (CW) and Call Hold (HOLD) supplementary services; Stage 2
|
TS
|
19.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.083/23083-j00.zip
| |
23.082
|
Call Forwarding (CF) supplementary services; Stage 2
|
TS
|
19.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.082/23082-j00.zip
| |
23.038
|
Alphabets and language-specific information
|
TS
|
19.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.038/23038-j00.zip
| |
23.087
|
User-to-User Signalling (UUS) supplementary service; Stage 2
|
TS
|
19.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.087/23087-j00.zip
| |
23.088
|
Call Barring (CB) Supplementary Services; Stage 2
|
TS
|
19.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.088/23088-j00.zip
| |
23.090
|
Unstructured Supplementary Service Data (USSD); Stage 2
|
TS
|
19.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.090/23090-j00.zip
| |
23.040
|
Technical realization of the Short Message Service (SMS)
|
TS
|
19.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.040/23040-j00.zip
| |
23.091
|
Explicit Call Transfer (ECT) supplementary service; Stage 2
|
TS
|
19.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.091/23091-j00.zip
| |
23.101
|
General Universal Mobile Telecommunications System (UMTS) architecture
|
TS
|
19.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.101/23101-j00.zip
| |
23.096
|
Name identification supplementary services; Stage 2
|
TS
|
19.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.096/23096-j00.zip
| |
23.097
|
Multiple Subscriber Profile (MSP) (Phase 2); Stage 2
|
TS
|
19.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.097/23097-j00.zip
| |
23.094
|
Follow-Me (FM); Stage 2
|
TS
|
19.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.094/23094-j00.zip
| |
22.870
|
Study on 6G Use Cases and Service Requirements
|
TR
|
0.4.1
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.870/22870-041.zip
| |
23.108
|
Mobile radio interface layer 3 specification, core network protocols; Stage 2
|
TS
|
19.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.108/23108-j00.zip
| |
23.110
|
Universal Mobile Telecommunications System (UMTS) access stratum; Services and functions
|
TS
|
19.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.110/23110-j00.zip
| |
23.116
|
Super-Charger technical realization; Stage 2
|
TS
|
19.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.116/23116-j00.zip
| |
23.107
|
Quality of Service (QoS) concept and architecture
|
TS
|
19.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.107/23107-j00.zip
| |
23.180
|
Mission critical services support in the Isolated Operation for Public Safety (IOPS) mode of operation
|
TS
|
19.1.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.180/23180-j10.zip
|
This document specifies the functional architecture, procedures and information flows needed to support mission critical services in the IOPS mode of operation. IOPS mode of operation allows an isolated 3GPP network to maintain a level of MC services in case the backhaul connection is lost. For example, for EPS the IOPS mode of operation is defined in 3GPP TS 23.401 [2].
The corresponding service requirements are defined in 3GPP TS 22.346 [9] and 3GPP TS 22.280 [11].
The present document is applicable to support mission critical services in the IOPS mode of operation for 3GPP access types, such as E-UTRAN or 5G.
The functional architecture to support mission critical services in the IOPS mode of operation can be used for public safety applications and also for general commercial applications, e.g. utility companies and railways, for the case of a backhaul failure.
|
23.093
|
Technical realization of Completion of Calls to Busy Subscriber (CCBS); Stage 2
|
TS
|
19.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.093/23093-j00.zip
| |
23.203
|
Policy and charging control architecture
|
TS
|
19.2.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.203/23203-j20.zip
|
The present document specifies the overall stage 2 level functionality for Policy and Charging Control that encompasses the following high level functions for IP‑CANs (e.g. GPRS, Fixed Broadband, EPC, etc.):
- Flow Based Charging for network usage, including charging control and online credit control, for service data flows and application traffic;
- Policy control (e.g. gating control, QoS control, QoS signalling, etc.).
The present document specifies the Policy and Charging Control functionality for Evolved 3GPP Packet Switched domain, including both 3GPP accesses GERAN/UTRAN/E-UTRAN and Non-3GPP accesses, according to TS 23.401 [17] and TS 23.402 [18].
The present document specifies functionality for unicast bearers. Broadcast and multicast bearers, such as MBMS contexts for GPRS, are out of scope of the present document.
NOTE: For E-UTRAN access, the usage of functionalities covered in this specification for features such as MBMS, CIoT and V2X is described in TS 23.246 [6], TS 23.682 [42] and TS 23.285 [48], respectively.
|
23.204
|
Support of Short Message Service (SMS) over generic 3GPP Internet Protocol (IP) access; Stage 2
|
TS
|
19.1.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.204/23204-j10.zip
|
The present document specifies the new capabilities and enhancements needed to support SMS over a generic IP Connectivity Access Network (IP-CAN) using IMS capabilities (TS 23.228 [9]). These include (but are not limited) to:
1 Enhancements to the HSS;
2 Communication between the SMS-GMSC/SMS-IWMSC and the HSS;
3 Authentication of service usage and registration;
4 Transfer of UE Terminated SMS, UE Originated SMS, and Delivery reports;
5 Mechanisms to handle SMS when there is more than one IP connection active with the UE, etc.
6 Mechanisms to handle MT-SMS without MSISDN to IMS UE, and SMS between IMS UEs that support MSISDN-less SMS operation.
The document also specifies the capabilities and enhancements needed to support the service level interworking for the Short Message service as defined in the TS 23.040 [2] and in this specification and the Instant Messaging service as defined in OMA-TS-SIMPLE_IM-V1_0 [12]. The features supported from the IM specification are limited to the exchange of short or large immediate messages in pager mode.
NOTE: The page-mode immediate message as defined in TS 24.247[14] is considered as a subset of OMA-TS-SIMPLE-IM-V1_0 [12].
The document also specifies the capabilities and enhancements needed to support service level interworking for the Short Message service, as defined in the TS 23.040 [2] and in this specification and the OMA CPM service as defined in OMA-TS-CPM_Conv_Fnct-V1_0 [17]. The features supported from the CPM specification are the exchange of short or large immediate messages in pager mode, as well as session-based messaging.
The service requirements are described in TS 22.340 [18].
|
23.060
|
General Packet Radio Service (GPRS); Service description; Stage 2
|
TS
|
19.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.060/23060-j00.zip
| |
23.141
|
Presence service; Architecture and functional description
|
TS
|
19.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.141/23141-j00.zip
| |
23.135
|
Multicall supplementary service; Stage 2
|
TS
|
19.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.135/23135-j00.zip
| |
23.142
|
Value-added Services for SMS (VAS4SMS); Interface and signalling flow
|
TS
|
19.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.142/23142-j00.zip
| |
23.146
|
Technical realization of facsimile Group 3 non-transparent
|
TS
|
19.0.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.146/23146-j00.zip
| |
23.202
|
Circuit switched data bearer services
|
TS
|
19.0.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.202/23202-j00.zip
| |
23.167
|
IP Multimedia Subsystem (IMS) emergency sessions
|
TS
|
19.1.1
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.167/23167-j11.zip
| |
23.172
|
Technical realization of Circuit Switched (CS) multimedia service UDI/RDI fallback and service modification; Stage 2
|
TS
|
19.0.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.172/23172-j00.zip
| |
23.161
|
Network-Based IP Flow Mobility (NBIFOM); Stage 2
|
TS
|
19.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.161/23161-j00.zip
| |
23.207
|
End-to-end Quality of Service (QoS) concept and architecture
|
TS
|
19.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.207/23207-j00.zip
| |
23.119
|
Gateway Location Register (GLR); Stage 2
|
TS
|
19.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.119/23119-j00.zip
| |
23.221
|
Architectural requirements
|
TS
|
19.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.221/23221-j00.zip
| |
23.153
|
Out of band transcoder control; Stage 2
|
TS
|
19.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.153/23153-j00.zip
| |
23.078
|
Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 4; Stage 2
|
TS
|
19.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.078/23078-j00.zip
| |
23.247
|
Architectural enhancements for 5G multicast-broadcast services
|
TS
|
19.2.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.247/23247-j20.zip
|
The present document specifies architectural enhancements to the 5G system using NR to support multicast and broadcast communication services, complying to the requirements in TS 22.146 [2], TS 22.246 [3] and TS 22.261 [4]. This document encompasses support for functions such as how to deliver multicast and broadcast communications including support within certain location areas, mobility, MBS session management, policy control and QoS, and support for features e.g. group message delivery.
The present document also covers interworking with E-UTRAN and EPC based eMBMS for Public Safety (e.g. MCX services).
|
23.139
|
3GPP system - fixed broadband access network interworking; Stage 2
|
TS
|
19.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.139/23139-j00.zip
| |
23.255
|
Application layer support for Uncrewed Aerial System (UAS); Functional architecture and information flows;
|
TS
|
19.5.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.255/23255-j50.zip
|
The present document specifies the functional architecture, procedures and information flows for UAS application enabler layer. This specification includes the capabilities of the application layer support for UAS that are necessary to ensure efficient use and deployment of UAS over 3GPP systems. The UAS application enabler capabilities applies to both EPS and 5GS.
|
23.226
|
Global text telephony (GTT); Stage 2
|
TS
|
19.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.226/23226-j00.zip
| |
23.216
|
Single Radio Voice Call Continuity (SRVCC); Stage 2
|
TS
|
19.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.216/23216-j00.zip
| |
23.214
|
Architecture enhancements for control and user plane separation of EPC nodes
|
TS
|
19.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.214/23214-j00.zip
| |
23.236
|
Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes
|
TS
|
19.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.236/23236-j00.zip
| |
23.272
|
Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2
|
TS
|
19.1.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.272/23272-j10.zip
|
This document defines the Stage 2 architecture and specification for the CS Fallback and for SMS over SGs for EPS or CS Fallback and SMS over S102. The scope of this document includes the architecture enhancements for functionality to enable fallback from E-UTRAN access to UTRAN/GERAN CS domain access and to CDMA 1x RTT CS domain access, and functionality to reuse of voice and other CS-domain services (e.g. CS UDI video / LCS / USSD) by reuse of the CS domain. The functionality specified to support SMS over SGs does not trigger any CS Fallback to UTRAN/GERAN. The functionality specified to support SMS over S102 does not trigger any CS Fallback to CDMA 1xRTT CS domain.
In addition this specification includes an SMS in MME architecture option for SMS services only. This functionality does not trigger any CS Fallback and does not require SGs.
The architecture enhancements to support CS fallback to CDMA 1x RTT CS domain access for UEs with single and dual receiver configurations are specified in Annex B.
In this Release of the specification no mechanisms are specified to support CS Fallback to both UTRAN/GERAN and CDMA 1xRTT in the same PLMN. So, even when a UE has the capability to support both CS Fallback to UTRAN/GERAN CS domain and CS Fallback to CDMA 1xRTT CS domain in a given PLMN, the PLMN implements only one of the two.
|
23.218
|
IP Multimedia (IM) session handling; IM call model; Stage 2
|
TS
|
19.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.218/23218-j00.zip
| |
23.240
|
3GPP Generic User Profile (GUP); Architecture (Stage 2)
|
TS
|
19.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.240/23240-j00.zip
| |
23.261
|
IP flow mobility and seamless Wireless Local Area Network (WLAN) offload; Stage 2
|
TS
|
19.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.261/23261-j00.zip
| |
23.122
|
Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode
|
TS
|
19.4.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.122/23122-j40.zip
| |
23.251
|
Network sharing; Architecture and functional description
|
TS
|
19.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.251/23251-j00.zip
| |
23.231
|
SIP-I based circuit-switched core network; Stage 2
|
TS
|
19.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.231/23231-j00.zip
| |
23.246
|
Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional description
|
TS
|
19.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.246/23246-j00.zip
| |
23.259
|
Personal Network Management (PNM); Procedures and information flows; Stage 2
|
TS
|
19.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.259/23259-j00.zip
| |
23.279
|
Combining Circuit Switched (CS) and IP Multimedia Subsystem (IMS) services; Stage 2
|
TS
|
19.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.279/23279-j00.zip
| |
23.205
|
Bearer-independent circuit-switched core network; Stage 2
|
TS
|
19.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.205/23205-j00.zip
| |
23.222
|
Common API Framework for 3GPP Northbound APIs
|
TS
|
19.7.0
|
S6
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.222/23222-j70.zip
| |
23.278
|
Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 4; Stage 2; IM CN Interworking
|
TS
|
19.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.278/23278-j00.zip
| |
23.287
|
Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services
|
TS
|
19.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.287/23287-j00.zip
| |
23.271
|
Functional stage 2 description of Location Services (LCS)
|
TS
|
19.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.271/23271-j00.zip
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.