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.903 | Study on Videotelephony teleservice | TR | 8.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.903/22903-800.zip | |
22.908 | Study on Paging Permission with Access Control (PPAC) | TR | 8.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.908/22908-810.zip | |
22.912 | Study into network selection requirements for non-3GPP access | TR | 8.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.912/22912-800.zip | |
22.934 | Feasibility study on 3GPP system to Wireless Local Area Network (WLAN) interworking | TR | 8.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.934/22934-800.zip | This document studies the feasibility of interworking between 3GPP systems and Wireless Local Area Networks (WLANs). This document identifies and describes:
- Scenarios for 3GPP - WLAN Interworking
- 3GPP - WLAN interworking service requirements
- Guidelines for standardisation of 3GPP-WLAN interworking
The document includes a number of different scenarios of 3GPP-WLAN interworking ranging from common billing to the provision of services seamlessly between the WLAN and the 3GPP system. In addition, 3GPP-WLAN interworking feasibility study includes the analysis of a number of environments where both the 3GPP system and WLAN may be deployed. Finally, this report outlines some of the different WLAN technologies that may be interworked with 3GPP systems.
It is beyond the scope of 3GPP to develop new system functionalities for WLANs that are not interworking with any 3GPP system functionality. |
22.935 | Feasibility study on Location Services (LCS) for Wireless Local Area Network (WLAN) interworking | TR | 8.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.935/22935-800.zip | The 3GPP has developed and continues to develop Location Services (LCS) requirements and standards for GSM and UMTS. To further the advancement of LCS within the 3GPP, LCS requirements and standards may be extended for 3GPP WLAN interworking to support the same location-based services that have been deployed today for GSM and UMTS. LCS with 3GPP WLAN Interworking system is considered to enlarge the area of location services.
The purpose of the feasibility study is to study a generic interworking functionality for LCS between 3GPP system and WLAN systems (e.g. IEEE 802.11 family, HIPERLAN/2, …). Specifically, the feasibility study aims to:
- Study the LCS requirements for 3GPP WLAN Interworking scenarios.
- Study the different possible LCS architectures for interworking.
Also, the feasibility study will:
- Assess the service requirements for support of LCS over I-WLAN
- Define the MMI aspects, i.e., the minimum set of functions to support LCS when the choice of access system by the user and/or terminal for when both access systems is available.
- Assess the charging requirements and architecture impacts. In particular, consider whether or not WLAN charging for LCS should be integrated with the architecture for UMTS charging for LCS.
- Assess the security requirements, given the prerequisite that a) the security level of the UMTS platform itself is not impacted, b) the security level provided to users in the WLAN mode is comparable to the one of UMTS. |
22.936 | Multi-system terminals | TR | 8.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.936/22936-800.zip | |
22.937 | Requirements for service continuity between mobile and Wireless Local Area Network (WLAN) networks | TR | 8.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.937/22937-810.zip | The present document develops the use cases and requirements for service continuity between a 3GPP network and another network, which can be:
- a TISPAN NGN with an IMS, accessed by a WLAN.
- an ISP accessed via a WLAN
Each access network has its own separate security system and the NOs have a commercial agreement for roaming and handover.
The present document considers use cases whereby:
Editors Note: Text to be added when use cases are agreed
The present document also examines the requirements and implications of:
- service aspects: maintaining service quality and service continuity, while roaming between a 3GPP PLMN and an independently-owned WLAN;
- security aspects: while roaming between a 3GPP PLMN and a WLAN, in particular when networks may be independently authenticated.
- UICC aspects, including NAA types, personalisation and ownership.
The present document is related to ongoing standardisation efforts in the following areas:
- where the WLAN is an I-WLAN , requirements for which are described in [3];
- methods for selecting the 3GPP or the non-3GPP access network, requirements for which are described in [2]. |
22.940 | IP Multimedia Subsystem (IMS) messaging | TR | 8.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.940/22940-800.zip | |
22.942 | Study on Value Added Services (VAS) for Short Message Service (SMS) | TR | 8.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.942/22942-810.zip | |
22.944 | Report on service requirements for UE functionality split | TR | 8.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.944/22944-800.zip | |
22.948 | Study of requirements of IP-Multimedia Subsystem (IMS) convergent multimedia conferencing | TR | 8.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.948/22948-800.zip | |
22.949 | Study on a generalized privacy capability | TR | 8.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.949/22949-800.zip | |
22.950 | Priority service feasibility study | TR | 8.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.950/22950-800.zip | |
22.951 | Service aspects and requirements for network sharing | TR | 8.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.951/22951-800.zip | |
22.952 | Priority service guide | TR | 8.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.952/22952-800.zip | |
22.168 | Earthquake and Tsunami Warning System (ETWS) requirements; Stage 1 | TS | 8.3.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.168/22168-830.zip | This Technical Specification defines the stage one description of the Earthquake and Tsunami Warning System (ETWS) Requirements. Stage one is the set of requirements seen primarily from the users’ and service providers’ points of view.
This TS includes information applicable to network operators, service providers, terminal and network manufacturers, in case of deployment of ETWS. ETWS deployment depends on operator decision or national regulations.
This TS contains the core requirements for the Earthquake and Tsunami Warning System, which are sufficient to provide a complete service.
This TS also contains regional requirements for Earthquake and Tsunami Warning System. |
22.279 | Combined Circuit Switched (CS) and IP Multimedia Subsystem (IMS) sessions; Stage 1 | TS | 8.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.279/22279-800.zip | |
22.146 | Multimedia Broadcast/Multicast Service (MBMS); Stage 1 | TS | 8.4.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.146/22146-840.zip | |
22.953 | Multimedia priority service feasibility study | TR | 8.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.953/22953-800.zip | |
22.977 | Feasibility study for speech-enabled services | TR | 8.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.977/22977-800.zip | |
22.978 | All-IP network (AIPN) feasibility study | TR | 8.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.978/22978-800.zip | |
22.979 | Feasibility study on combined Circuit Switched (CS) calls and IP Multimedia Subsystem (IMS) sessions | TR | 8.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.979/22979-800.zip | |
22.973 | IMS Multimedia Telephony service; and supplementary services | TR | 8.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.973/22973-800.zip | |
22.868 | Study on facilitating machine to machine communication in 3GPP systems | TR | 8.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.868/22868-800.zip | The present document identifies potential requirements to facilitate improvements in M2M communication and the more efficient use of radio and network resources.
Special consideration is given to the following areas for optimisation:
- Charging mechanisms
- Addressing
- Types of communication
- Fixed location, low mobility and low activity terminals
- Handling of large numbers of subscriptions and subscriber data within the network
- Handling issues of large number of M2M subscriptions for the user of M2M services
- Impact of optimisations for security resulting from improvement for M2M |
22.967 | Transferring of emergency call data | TR | 8.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.967/22967-800.zip | |
22.980 | Network composition feasibility study | TR | 8.1.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.980/22980-810.zip | |
22.983 | Services alignment and migration | TR | 8.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.983/22983-800.zip | |
22.982 | Study of Customised Alerting Tone (CAT) requirements | TR | 8.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.982/22982-800.zip | |
23.003 | Numbering, addressing and identification | TS | 8.21.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.003/23003-8l0.zip | |
23.002 | Network architecture | TS | 8.7.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.002/23002-870.zip | |
22.968 | Study for requirements for a Public Warning System (PWS) service | TR | 8.0.0 | S1 | https://www.3gpp.org/ftp/Specs/archive/22_series/22.968/22968-800.zip | |
23.009 | Handover procedures | TS | 8.3.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.009/23009-830.zip | |
23.008 | Organization of subscriber data | TS | 8.13.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.008/23008-8d0.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.015 | Technical realization of Operator Determined Barring (ODB) | TS | 8.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.015/23015-810.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.007 | Restoration procedures | TS | 8.9.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.007/23007-890.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.011 | Technical realization of Supplementary Services | TS | 8.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.011/23011-800.zip | |
23.031 | 3G Security; Fraud Information Gathering System (FIGS); Technical realization; Stage 2 | TS | 8.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.031/23031-800.zip | |
23.012 | Location management procedures | TS | 8.2.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.012/23012-820.zip | |
23.014 | Support of Dual Tone Multi-Frequency (DTMF) signalling | TS | 8.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.014/23014-800.zip | |
23.018 | Basic call handling; Technical realization | TS | 8.5.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.018/23018-850.zip | |
23.032 | Universal Geographical Area Description (GAD) | TS | 8.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.032/23032-800.zip | |
23.038 | Alphabets and language-specific information | TS | 8.3.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.038/23038-830.zip | |
23.034 | High Speed Circuit Switched Data (HSCSD); Stage 2 | TS | 8.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.034/23034-800.zip | |
23.035 | Immediate Service Termination (IST); Stage 2 | TS | 8.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.035/23035-800.zip | |
23.040 | Technical realization of the Short Message Service (SMS) | TS | 8.6.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.040/23040-860.zip | |
23.041 | Technical realization of Cell Broadcast Service (CBS) | TS | 8.11.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.041/23041-8b0.zip | |
23.016 | Subscriber data management; Stage 2 | TS | 8.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.016/23016-810.zip | |
23.053 | Tandem Free Operation (TFO); Service description; Stage 2 | TS | 8.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.053/23053-800.zip | |
23.057 | Mobile Execution Environment (MExE); Functional description; Stage 2 | TS | 8.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.057/23057-800.zip | |
23.042 | Compression algorithm for text messaging services | TS | 8.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.042/23042-800.zip | |
23.060 | General Packet Radio Service (GPRS); Service description; Stage 2 | TS | 8.17.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.060/23060-8h0.zip | |
23.066 | Support of Mobile Number Portability (MNP); Technical realization; Stage 2 | TS | 8.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.066/23066-800.zip | |
23.067 | enhanced Multi-Level Precedence and Pre-emption Service (eMLPP); Stage 2 | TS | 8.0.1 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.067/23067-801.zip | |
23.079 | Support of Optimal Routeing (SOR); Technical realization | TS | 8.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.079/23079-800.zip | |
23.078 | Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 4; Stage 2 | TS | 8.4.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.078/23078-840.zip | |
23.082 | Call Forwarding (CF) supplementary services; Stage 2 | TS | 8.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.082/23082-800.zip | |
23.081 | Line Identification supplementary services; Stage 2 | TS | 8.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.081/23081-800.zip | |
23.083 | Call Waiting (CW) and Call Hold (HOLD) supplementary services; Stage 2 | TS | 8.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.083/23083-800.zip | |
23.072 | Call Deflection (CD) supplementary service; Stage 2 | TS | 8.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.072/23072-800.zip | |
23.086 | Advice of Charge (AoC) supplementary services; Stage 2 | TS | 8.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.086/23086-800.zip | |
23.087 | User-to-User Signalling (UUS) supplementary service; Stage 2 | TS | 8.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.087/23087-800.zip | |
23.088 | Call Barring (CB) Supplementary Services; Stage 2 | TS | 8.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.088/23088-800.zip | |
23.090 | Unstructured Supplementary Service Data (USSD); Stage 2 | TS | 8.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.090/23090-800.zip | |
23.091 | Explicit Call Transfer (ECT) supplementary service; Stage 2 | TS | 8.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.091/23091-800.zip | |
23.093 | Technical realization of Completion of Calls to Busy Subscriber (CCBS); Stage 2 | TS | 8.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.093/23093-800.zip | |
23.084 | Multi Party (MPTY) supplementary service; Stage 2 | TS | 8.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.084/23084-800.zip | |
23.096 | Name identification supplementary services; Stage 2 | TS | 8.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.096/23096-800.zip | |
23.094 | Follow-Me (FM); Stage 2 | TS | 8.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.094/23094-800.zip | |
23.085 | Closed User Group (CUG) supplementary service; Stage 2 | TS | 8.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.085/23085-800.zip | |
23.097 | Multiple Subscriber Profile (MSP) (Phase 2); Stage 2 | TS | 8.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.097/23097-800.zip | |
23.116 | Super-Charger technical realization; Stage 2 | TS | 8.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.116/23116-800.zip | |
23.107 | Quality of Service (QoS) concept and architecture | TS | 8.2.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.107/23107-820.zip | |
23.108 | Mobile radio interface layer 3 specification, core network protocols; Stage 2 | TS | 8.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.108/23108-800.zip | |
23.101 | General Universal Mobile Telecommunications System (UMTS) architecture | TS | 8.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.101/23101-800.zip | |
23.122 | Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode | TS | 8.12.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.122/23122-8c0.zip | |
23.135 | Multicall supplementary service; Stage 2 | TS | 8.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.135/23135-800.zip | |
23.141 | Presence service; Architecture and functional description | TS | 8.1.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.141/23141-810.zip | |
23.110 | Universal Mobile Telecommunications System (UMTS) access stratum; Services and functions | TS | 8.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.110/23110-800.zip | |
23.119 | Gateway Location Register (GLR); Stage 2 | TS | 8.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.119/23119-800.zip | |
23.167 | IP Multimedia Subsystem (IMS) emergency sessions | TS | 8.6.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.167/23167-860.zip | |
23.172 | Technical realization of Circuit Switched (CS) multimedia service UDI/RDI fallback and service modification; Stage 2 | TS | 8.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.172/23172-800.zip | |
23.146 | Technical realization of facsimile Group 3 non-transparent | TS | 8.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.146/23146-800.zip | |
23.202 | Circuit switched data bearer services | TS | 8.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.202/23202-800.zip | |
23.203 | Policy and charging control architecture | TS | 8.15.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.203/23203-8f0.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.153 | Out of band transcoder control; Stage 2 | TS | 8.3.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.153/23153-830.zip | |
23.198 | Open Service Access (OSA); Stage 2 | TS | 8.0.0 | CP | https://www.3gpp.org/ftp/Specs/archive/23_series/23.198/23198-800.zip | The present document specifies the stage 2 of the Open Service Access (OSA). |
23.204 | Support of Short Message Service (SMS) over generic 3GPP Internet Protocol (IP) access; Stage 2 | TS | 8.5.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.204/23204-850.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.221 | Architectural requirements | TS | 8.9.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.221/23221-890.zip | |
23.207 | End-to-end Quality of Service (QoS) concept and architecture | TS | 8.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.207/23207-800.zip | |
23.226 | Global text telephony (GTT); Stage 2 | TS | 8.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.226/23226-800.zip | |
23.216 | Single Radio Voice Call Continuity (SRVCC); Stage 2 | TS | 8.8.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.216/23216-880.zip | |
23.218 | IP Multimedia (IM) session handling; IM call model; Stage 2 | TS | 8.6.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.218/23218-860.zip | |
23.236 | Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes | TS | 8.1.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.236/23236-810.zip | |
23.228 | IP Multimedia Subsystem (IMS); Stage 2 | TS | 8.12.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.228/23228-8c0.zip | |
23.231 | SIP-I based circuit-switched core network; Stage 2 | TS | 8.4.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.231/23231-840.zip | |
23.205 | Bearer-independent circuit-switched core network; Stage 2 | TS | 8.10.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.205/23205-8a0.zip | |
23.251 | Network sharing; Architecture and functional description | TS | 8.4.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.251/23251-840.zip | |
23.237 | IP Multimedia Subsystem (IMS) Service Continuity; Stage 2 | TS | 8.7.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.237/23237-870.zip | |
23.246 | Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional description | TS | 8.4.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.246/23246-840.zip | |
23.234 | 3GPP system to Wireless Local Area Network (WLAN) interworking; System description | TS | 8.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.234/23234-800.zip | This document provides an index to the set of specifications for interworking between 3GPP systems and Wireless Local Area Networks (WLANs).
No further changes to this specification are intended. If any future evolution of the procedures in this specification is necessary, it should be documented in other specifications. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.