id stringlengths 5 12 | title stringlengths 8 250 | type stringclasses 2 values | version stringclasses 560 values | working_group stringclasses 30 values | url stringlengths 67 81 | scope stringlengths 0 65.7k |
|---|---|---|---|---|---|---|
22.867 | Study on 5G smart energy and infrastructure | TR | 18.2.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.867/22867-i20.zip | The present document is to address study use cases, potential new service requirements for 5G system to support Smart Grid including the following topics:
• Smart Grid services, e.g. IEC standards, and their communications requirements including capacity, latency, availability, end-to-end QoS, resilience/redundancy and security.
• Deployment requirements when considering constraints e.g. service lifetime, coverage (ubiquity), electromagnetic applicability (e.g. penetration, ability to operate in high EM environments,) etc.
• Additional requirements due to operational manageability – e.g. the ability to configure and monitor the real (achieved & up to date) availability of virtual network topologies
• New Smart Grid use cases and potential service function requirements: e.g. on-demand power supply, distributed power supply system, distribution automation, higher accuracy power load measurement and control, meter automation, etc.
• Communication KPI and service requirements for enabling microgrids, DER and specifically distributed generation (DG) that require 5G wireless communication (e.g. wind and solar energy generation, including scenarios at or near residential / consumer premises, etc.) |
22.873 | Study on evolution of the IP Multimedia Subsystem (IMS) multimedia telephony service | TR | 18.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.873/22873-i00.zip | The present document studies new scenarios (e.g. AR/VR communication) for IMS Multimedia Telephony service, identifies potential service requirements, and identifies additional potential requirements on 5G system.
This document also does a gap analysis to existing requirements in 3GPP to identify potential requirements for introduction into 3GPP.
NOTE: Use cases in this document have references to those already specified in 3GPP TR26.918 [2] and TR26.928[3]. This allows an easier breakdown of these use cases to existing features and potential new requirements as well as relevant performance figures. New use cases in this TR are highlighted if they are not covered in 3GPP SA4 work. |
22.874 | 5G System (5GS); Study on traffic characteristics and performance requirements for AI/ML model transfer | TR | 18.2.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.874/22874-i20.zip | This report captures the study of the use cases and the potential performance requirements for 5G system support of Artificial Intelligence (AI)/Machine Learning (ML) model distribution and transfer (download, upload, updates, etc.), and identifies traffic characteristics of AI/ML model distribution, transfer and training for various applications, e.g. video/speech recognition, robot control, automotive, other verticals.
The aspects addressed include:
• AI/ML operation splitting between AI/ML endpoints;
• AI/ML model/data distribution and sharing over 5G system;
• Distributed/Federated Learning over 5G system.
Study of the AI/ML models themselves are not in the scope of the TR. |
22.878 | Study on 5G timing resiliency system | TR | 18.2.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.878/22878-i20.zip | The present document identifies additional potential requirements on the 5G system to support time-synchronization services in public and vertical domains, including both the ability to improve resiliency of timing services involving technologies supported by 5G and the ability to the ability to act as a backup for GNSS timing services.
The use cases address:
• the use of 5G system in concert with other timing technologies as a resilient timing source for end-users in complement/back-up/alternate to GNSS, and
• enhancement to the 5G system to enable time synchronization resiliency if GNSS or other timing services are compromised. |
22.881 | Study on sharing administrative configuration information between interconnected Mission Critical (MCX) service systems | TR | 18.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.881/22881-i10.zip | The present document studies use cases that assess under which circumstances interconnected MCX Service Systems exchange administrative and security relevant data and information.
Its objective is to identify new potential requirements related to the use cases and new high-level security requirements related to interconnection of MCX Service Systems and migration of MCX Users and MCX Service Groups. |
22.890 | Study on supporting railway smart station services | TR | 0.7.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.890/22890-070.zip | The present document analyses use cases of smart railway station such as station operation monitoring and control, passenger supporting services and evolution use cases of business and performance applications currently included in TR22.989 in order to derive potential requirements. |
22.903 | Study on Videotelephony teleservice | TR | 18.0.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.903/22903-i01.zip | |
22.904 | Study on user-centric identifiers and authentication | TR | 18.0.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.904/22904-i01.zip | |
22.906 | Study on IMS based peer-to-peer content distribution services | TR | 18.0.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.906/22906-i01.zip | |
22.908 | Study on Paging Permission with Access Control (PPAC) | TR | 18.0.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.908/22908-i01.zip | |
22.912 | Study into network selection requirements for non-3GPP access | TR | 18.0.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.912/22912-i01.zip | |
22.926 | Guidelines for extraterritorial 5G Systems (5GS) | TR | 18.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.926/22926-i00.zip | |
22.936 | Multi-system terminals | TR | 18.0.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.936/22936-i01.zip | |
22.940 | IP Multimedia Subsystem (IMS) messaging | TR | 18.0.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.940/22940-i01.zip | |
22.942 | Study on Value Added Services (VAS) for Short Message Service (SMS) | TR | 18.0.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.942/22942-i01.zip | |
22.944 | Report on service requirements for UE functionality split | TR | 18.0.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.944/22944-i01.zip | |
22.947 | Study on Personal Broadcast Service (PBS) | TR | 18.0.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.947/22947-i01.zip | |
22.948 | Study of requirements of IP-Multimedia Subsystem (IMS) convergent multimedia conferencing | TR | 18.0.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.948/22948-i01.zip | |
22.949 | Study on a generalized privacy capability | TR | 18.0.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.949/22949-i01.zip | |
22.950 | Priority service feasibility study | TR | 18.0.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.950/22950-i01.zip | |
22.951 | Service aspects and requirements for network sharing | TR | 18.0.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.951/22951-i01.zip | |
22.952 | Priority service guide | TR | 18.0.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.952/22952-i01.zip | |
22.953 | Multimedia priority service feasibility study | TR | 18.0.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.953/22953-i01.zip | |
22.967 | Transferring of emergency call data | TR | 18.0.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.967/22967-i01.zip | |
22.968 | Study for requirements for a Public Warning System (PWS) service | TR | 18.0.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.968/22968-i01.zip | |
22.973 | IMS Multimedia Telephony service; and supplementary services | TR | 18.0.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.973/22973-i01.zip | |
22.977 | Feasibility study for speech-enabled services | TR | 18.0.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.977/22977-i01.zip | |
22.978 | All-IP network (AIPN) feasibility study | TR | 18.0.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.978/22978-i01.zip | |
22.979 | Feasibility study on combined Circuit Switched (CS) calls and IP Multimedia Subsystem (IMS) sessions | TR | 18.0.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.979/22979-i01.zip | |
22.980 | Network composition feasibility study | TR | 18.0.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.980/22980-i01.zip | |
22.982 | Study of Customised Alerting Tone (CAT) requirements | TR | 18.0.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.982/22982-i01.zip | |
22.983 | Services alignment and migration | TR | 18.0.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.983/22983-i01.zip | |
22.985 | Service requirements for the User Data Convergence (UDC) | TR | 18.0.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.985/22985-i01.zip | |
22.986 | Study on Service Specific Access Control | TR | 18.0.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.986/22986-i01.zip | |
22.987 | Study of haptic services requirements | TR | 18.0.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.987/22987-i01.zip | |
22.988 | Study on alternatives to E.164 for Machine-Type Communications (MTC) | TR | 18.0.1 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.988/22988-i01.zip | |
22.989 | Study on Future Railway Mobile Communication System | TR | 18.5.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.989/22989-i50.zip | The present document analyses FRMCS Use cases, system principles of FRMCS and Interworking between GSM-R and FRMCS in order to derive potential requirements. |
22.990 | Study on off-network for rail | TR | 18.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.990/22990-i00.zip | |
23.002 | Network architecture | TS | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.002/23002-i00.zip | |
23.003 | Numbering, addressing and identification | TS | 18.7.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.003/23003-i70.zip | |
23.007 | Restoration procedures | TS | 18.5.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.007/23007-i50.zip | 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 | 18.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.008/23008-i10.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. |
23.009 | Handover procedures | TS | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.009/23009-i00.zip | |
23.011 | Technical realization of Supplementary Services | TS | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.011/23011-i00.zip | |
23.012 | Location management procedures | TS | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.012/23012-i00.zip | |
23.014 | Support of Dual Tone Multi-Frequency (DTMF) signalling | TS | 18.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.014/23014-i00.zip | |
23.015 | Technical realization of Operator Determined Barring (ODB) | TS | 18.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.015/23015-i10.zip | 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. |
23.016 | Subscriber data management; Stage 2 | TS | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.016/23016-i00.zip | |
23.018 | Basic call handling; Technical realization | TS | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.018/23018-i00.zip | |
23.031 | 3G Security; Fraud Information Gathering System (FIGS); Technical realization; Stage 2 | TS | 18.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.031/23031-i00.zip | |
23.032 | Universal Geographical Area Description (GAD) | TS | 18.3.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.032/23032-i30.zip | |
23.034 | High Speed Circuit Switched Data (HSCSD); Stage 2 | TS | 18.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.034/23034-i00.zip | |
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 | |
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 | |
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 | |
23.041 | Technical realization of Cell Broadcast Service (CBS) | TS | 18.7.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.041/23041-i70.zip | |
23.042 | Compression algorithm for text messaging services | TS | 18.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.042/23042-i00.zip | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
23.122 | Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode | TS | 18.11.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.122/23122-ib0.zip | |
23.135 | Multicall supplementary service; Stage 2 | TS | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.135/23135-i00.zip | |
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 | |
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 | |
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 | |
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 | |
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 | |
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 | |
23.167 | IP Multimedia Subsystem (IMS) emergency sessions | TS | 18.2.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.167/23167-i20.zip | |
23.172 | Technical realization of Circuit Switched (CS) multimedia service UDI/RDI fallback and service modification; Stage 2 | TS | 18.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.172/23172-i00.zip | |
23.180 | Mission critical services support in the Isolated Operation for Public Safety (IOPS) mode of operation | TS | 18.1.0 | S6 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.180/23180-i10.zip | |
23.202 | Circuit switched data bearer services | TS | 18.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.202/23202-i00.zip | |
23.203 | Policy and charging control architecture | TS | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.203/23203-i00.zip | 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 | 18.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.204/23204-i00.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.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 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.