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 |
|---|---|---|---|---|---|---|
23.078 | Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 4; Stage 2 | TS | 11.3.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.078/23078-b30.zip | |
23.079 | Support of Optimal Routeing (SOR); Technical realization | TS | 11.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.079/23079-b00.zip | |
23.081 | Line Identification supplementary services; Stage 2 | TS | 11.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.081/23081-b00.zip | |
23.007 | Restoration procedures | TS | 11.8.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.007/23007-b80.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.083 | Call Waiting (CW) and Call Hold (HOLD) supplementary services; Stage 2 | TS | 11.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.083/23083-b00.zip | |
23.084 | Multi Party (MPTY) supplementary service; Stage 2 | TS | 11.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.084/23084-b00.zip | |
23.085 | Closed User Group (CUG) supplementary service; Stage 2 | TS | 11.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.085/23085-b00.zip | |
23.086 | Advice of Charge (AoC) supplementary services; Stage 2 | TS | 11.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.086/23086-b00.zip | |
23.087 | User-to-User Signalling (UUS) supplementary service; Stage 2 | TS | 11.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.087/23087-b00.zip | |
23.088 | Call Barring (CB) Supplementary Services; Stage 2 | TS | 11.3.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.088/23088-b30.zip | |
23.090 | Unstructured Supplementary Service Data (USSD); Stage 2 | TS | 11.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.090/23090-b00.zip | |
23.091 | Explicit Call Transfer (ECT) supplementary service; Stage 2 | TS | 11.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.091/23091-b00.zip | |
23.093 | Technical realization of Completion of Calls to Busy Subscriber (CCBS); Stage 2 | TS | 11.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.093/23093-b00.zip | |
23.094 | Follow-Me (FM); Stage 2 | TS | 11.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.094/23094-b00.zip | |
23.096 | Name identification supplementary services; Stage 2 | TS | 11.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.096/23096-b00.zip | |
23.097 | Multiple Subscriber Profile (MSP) (Phase 2); Stage 2 | TS | 11.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.097/23097-b00.zip | |
23.101 | General Universal Mobile Telecommunications System (UMTS) architecture | TS | 11.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.101/23101-b00.zip | |
23.107 | Quality of Service (QoS) concept and architecture | TS | 11.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.107/23107-b00.zip | |
23.108 | Mobile radio interface layer 3 specification, core network protocols; Stage 2 | TS | 11.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.108/23108-b00.zip | |
23.110 | Universal Mobile Telecommunications System (UMTS) access stratum; Services and functions | TS | 11.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.110/23110-b00.zip | |
23.116 | Super-Charger technical realization; Stage 2 | TS | 11.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.116/23116-b00.zip | |
23.119 | Gateway Location Register (GLR); Stage 2 | TS | 11.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.119/23119-b00.zip | |
23.122 | Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode | TS | 11.4.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.122/23122-b40.zip | |
23.135 | Multicall supplementary service; Stage 2 | TS | 11.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.135/23135-b00.zip | |
23.139 | 3GPP system - fixed broadband access network interworking; Stage 2 | TS | 11.4.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.139/23139-b40.zip | |
23.141 | Presence service; Architecture and functional description | TS | 11.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.141/23141-b00.zip | |
23.142 | Value-added Services for SMS (VAS4SMS); Interface and signalling flow | TS | 11.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.142/23142-b00.zip | |
23.146 | Technical realization of facsimile Group 3 non-transparent | TS | 11.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.146/23146-b00.zip | |
23.153 | Out of band transcoder control; Stage 2 | TS | 11.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.153/23153-b10.zip | |
23.040 | Technical realization of the Short Message Service (SMS) | TS | 11.5.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.040/23040-b50.zip | |
23.172 | Technical realization of Circuit Switched (CS) multimedia service UDI/RDI fallback and service modification; Stage 2 | TS | 11.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.172/23172-b00.zip | |
23.202 | Circuit switched data bearer services | TS | 11.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.202/23202-b00.zip | |
23.203 | Policy and charging control architecture | TS | 11.15.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.203/23203-bf0.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 | 11.5.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.204/23204-b50.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 | 11.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.205/23205-b00.zip | |
23.207 | End-to-end Quality of Service (QoS) concept and architecture | TS | 11.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.207/23207-b00.zip | |
23.216 | Single Radio Voice Call Continuity (SRVCC); Stage 2 | TS | 11.11.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.216/23216-bb0.zip | |
23.003 | Numbering, addressing and identification | TS | 11.9.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.003/23003-b90.zip | |
23.221 | Architectural requirements | TS | 11.3.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.221/23221-b30.zip | |
23.226 | Global text telephony (GTT); Stage 2 | TS | 11.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.226/23226-b00.zip | |
23.228 | IP Multimedia Subsystem (IMS); Stage 2 | TS | 11.11.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.228/23228-bb0.zip | |
23.231 | SIP-I based circuit-switched core network; Stage 2 | TS | 11.1.1 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.231/23231-b11.zip | |
23.234 | 3GPP system to Wireless Local Area Network (WLAN) interworking; System description | TS | 11.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.234/23234-b00.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. |
23.236 | Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes | TS | 11.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.236/23236-b00.zip | |
23.237 | IP Multimedia Subsystem (IMS) Service Continuity; Stage 2 | TS | 11.11.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.237/23237-bb0.zip | |
23.240 | 3GPP Generic User Profile (GUP); Architecture (Stage 2) | TS | 11.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.240/23240-b00.zip | |
23.246 | Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional description | TS | 11.2.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.246/23246-b20.zip | |
23.251 | Network sharing; Architecture and functional description | TS | 11.6.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.251/23251-b60.zip | |
23.259 | Personal Network Management (PNM); Procedures and information flows; Stage 2 | TS | 11.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.259/23259-b00.zip | |
23.261 | IP flow mobility and seamless Wireless Local Area Network (WLAN) offload; Stage 2 | TS | 11.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.261/23261-b00.zip | |
23.271 | Functional stage 2 description of Location Services (LCS) | TS | 11.3.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.271/23271-b30.zip | |
23.272 | Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2 | TS | 11.10.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.272/23272-ba0.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.082 | Call Forwarding (CF) supplementary services; Stage 2 | TS | 11.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.082/23082-b00.zip | |
23.279 | Combining Circuit Switched (CS) and IP Multimedia Subsystem (IMS) services; Stage 2 | TS | 11.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.279/23279-b00.zip | |
23.284 | Local Call Local Switch (LCLS); Stage 2 | TS | 11.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.284/23284-b10.zip | |
23.292 | IP Multimedia Subsystem (IMS) centralized services; Stage 2 | TS | 11.8.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.292/23292-b80.zip | |
23.327 | Mobility between 3GPP-Wireless Local Area Network (WLAN) interworking and 3GPP systems | TS | 11.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.327/23327-b00.zip | This document specifies the stage 2 system description for providing mobility between 3GPP Wireless Local Area Network Interworking (I‑WLAN) and 3GPP Systems. The I-WLAN feature defined in TS 23.234 [2] has been discontinued since Release 13 and it is removed from this specification. |
23.333 | Multimedia Resource Function Controller (MRFC) - Multimedia Resource Function Processor (MRFP) Mp interface: Procedures descriptions | TS | 11.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.333/23333-b10.zip | |
23.041 | Technical realization of Cell Broadcast Service (CBS) | TS | 11.6.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.041/23041-b60.zip | |
23.335 | User Data Convergence (UDC); Technical realization and information flows; Stage 2 | TS | 11.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.335/23335-b00.zip | |
23.380 | IMS Restoration Procedures | TS | 11.5.1 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.380/23380-b51.zip | |
23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | TS | 11.11.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.401/23401-bb0.zip | |
23.402 | Architecture enhancements for non-3GPP accesses | TS | 11.10.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.402/23402-ba0.zip | |
23.682 | Architecture enhancements to facilitate communications with packet data networks and applications | TS | 11.5.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.682/23682-b50.zip | |
23.812 | Feasibility study on IP Multimedia Subsystem (IMS) evolution | TR | 11.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.812/23812-b00.zip | The scope of the technical report is to capture the results of a study into the feasibility of enhancing IMS network architecture. This report intends to study the feasibility of enhancing IMS network architecture as follows,
- Investigating architectural improvements to reduce the complexity of signalling procedures by reducing the signalling hops, or the number of options and combinations (by looking at different groupings of combining existing entities);
- Investigating means to improve system-level load balancing and reliability;
- Investigating possibilities for reducing configuration workload to save OPEX.
- Investigating the introduction of IMS Overload Control mechanisms.
Backward compatibility with current IMS specifications shall be ensured.
NOTE: overlap with SA5 and CT4 work need to be monitored.
This report is intended to explore potential architecture improvements and also provide conclusions on the above aspects with respect to potential future normative specification work.
There are a number of functions involved in call session setup in IMS network. Interfaces and interactions between network elements may be a little complicated and not that efficient. It is deemed beneficial to review the current IMS architecture including aspects such as the possible optimization of interfaces/reference points (by looking at different groupings of combining existing entities), reducing options of solutions for the same issues, relevancy of certain functions etc.
IMS network service availability largely relies on the reliability of network entities. If some network elements implementing critical functions (e.g. S-CSCF, HSS) fail, service availability may be impacted. Moreover network elements may not be fully utilized because network load may not be well distributed, e.g. some nodes may be overloaded due to sudden traffic increase, while others may be under loaded to some extent. Though there are some element level approaches to solve these problems, some system level solutions should be studied, for example, the method to distribute load between network elements in different geographical locations especially when a disaster happens, such as earthquake.
Network expansion may require significant manual configurations, and the network maintenance and upgrade may be time-consuming and also may be costly for operators. Introducing self-organization features may improve the network intelligence and reduce the efforts of manual configuration.
The objectives of the study for investigating the introduction of IMS Overload Control mechanisms are to:
- Determine the parts of IMS architecture for which overload control mechanisms are needed;
- Evaluate the applicability of candidate solutions for Overload Control to the SIP entities of the IP multimedia core network architecture, including:
- mechanisms having already been specified or studied within 3GPP and their possible enhancements,
- mechanisms specified or studied by other bodies (e.g. ETSI TISPAN, IETF) and their possible enhancements,
- other mechanisms, if proposed within this work item;
- Provide recommendations based on analysis. |
23.813 | Study on policy solutions and enhancements | TR | 11.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.813/23813-b00.zip | The objective is to study an evolved policy solution through enhancement of 3GPP policy framework. One of the aims of the study is to ensure a policy architecture that provides an extensible framework for easy reuse with new IP based services by identifying areas where improvement of specifications are feasible. The study item will look into solutions for the examples in the section above.
Existing components for consideration in the Policy Study are functions and interfaces to/from
- PCRF, PCEF and BBERF;
- SPR, HSS;
- ANDSF;
- IMS policy decision making entities.
The study aims to provide a more comprehensive way (e.g. going beyond existing 3GPP PCC framework) to handle operator policies for all IP / service flows (IMS and non-IMS) in a coordinated manner and under varying network conditions while keeping in view aspects such as:
- user preferences;
- user subscriptions;
- service requirements;
- terminal capabilities (including converged terminals);
- network capabilities (3GPP and those non 3GPP accesses inter- working with 3GPP);
- Session transfer and terminating policies;
- Security policy control, e.g. firewalling and gating.
Roaming scenarios are considered as part of this study. Compatibility with existing system architecture elements are protected and backward compatibility is expected. All types of policies i.e. static/pre-provisioned, dynamic, network based, UE based are considered in the study.
When a key issue is resolved sufficiently to be incorporated into the specification in an independent manner, the study work may move forward for a decision for normative specification work on such issue(s) using a new work item or a TEI. |
23.842 | Study on network provided location information to the IP Multimedia Subsystem (IMS) | TR | 11.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.842/23842-b00.zip | The present document investigates architecture solutions for making the Network Provided Location Information (NPLI) related to the access network that the UE is camped on available to the IMS nodes whenever the IMS operator needs to record this information either to fulfil legal obligations, for charging or for other purposes.
This study will gather the various existing regulatory and operator requirements that the solution needs to fulfil, in particular:
- whether the provision of the Network Provided Location (NPLI) Information and local time are applicable to all the users served by a network (i.e. "non-roaming" subscribers and inbound roamers) or only to the network operator subscribers;
- whether Network Provided Location (NPLI) and local time need to be made available also if EPS/GPRS and IMS services of a subscriber are provided by different networks;
- what events trigger the need to retrieve the Network Provided Location (NPLI) and local time.
The study is then expected to produce solution candidates which detail the necessary Stage 2 message flows, architecture enhancements and new functionality needed in the EPS and GPRS networks. The solution candidates will also describe what IP Multimedia Subsystem elements are affected in order to obtain the Network Provided Location (NPLI).
The solutions produced will then be assessed against the criteria identified in section 7 where recommendations for normative work will also be made. |
23.849 | Study on Stage 2 aspects of Optimised Service Charging and Allocation of Resources (OSCAR) in the IP Multimedia Subsystem (IMS) whilst roaming | TR | 11.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.849/23849-b00.zip | The present document provides a study into the new (Rel-11) requirements identified by SA WG1 to allow a home network to control a visited network to perform the following IMS functions for its subscribers:
- conferencing (network hosted);
- transcoding;
- tone insertion; and
- announcement insertion. |
23.850 | Study on roaming architecture for voice over IP Multimedia Subsystem (IMS) with local breakout | TR | 11.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.850/23850-b00.zip | In the context of support of roaming for voice over IMS, the GSM Association has decided that local breakout in the visited network will be needed (see GSMA PRD IR.65 [6]). This is because local breakout can be regarded as one cornerstone to allow the replication of the charging principles on which CS roaming is based on. However there are several other aspects that need to be considered e.g. the split/bundling of user and control plane, capturing of SDP information needed to generate charging records, to make such principles applicable to voice over IMS roaming.
This study item will therefore investigate solutions for the provision of voice over IMS in roaming scenarios that facilitate the realization of a charging model that replicates the principles of CS model.
It will be studied whether changes to the core 3GPP specifications are needed and if so which ones. The study will focus on IMS layer and not EPC aspects.
As some of the aspects of the roaming are outside the scope of 3GPP (e.g. decision to anchor media or control plane, interaction with carrier networks, roaming agreements) this study will be performed in close cooperation with the GSM Association which may provide additional requirements and guidance during its development. |
23.854 | Enhancements for Multimedia Priority Service (MPS) | TR | 11.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.854/23854-b00.zip | MPS will enable National Security/Emergency Preparedness (NS/EP) users (herein called Service Users) to make priority calls/sessions using the public networks. This service needs to be ensured also under special conditions such as network congestion. Service Users are the government-authorized personnel, emergency management officials and/or other authorized users. Effective disaster response and management rely on the Service User's ability to communicate during congestion conditions. Service Users are expected to receive priority treatment, in support of mission critical multimedia communications.
The enhancements for MPS evaluated in this document are priority aspects of EPS packet bearer services and priority related interworking between IMS and EPS packet bearer services. These enhancements enable the network to support end-to-end priority treatment for MPS call/session origination/termination, including the Non Access Stratum (NAS) and Access Stratum (AS) signalling establishment procedures at originating/terminating network side as well as resource allocation in the core and radio networks for bearers. Priority treatment will be applicable to IMS based multimedia services, priority EPS bearer services and CS Fallback.
This document clarifies the architectural requirements for MPS, considers the priority service scenarios, and evaluates solution alternatives. Solutions will be proposed and evaluated based on the following three service categories: IMS based multimedia service (voice, video etc), priority EPS bearer services (PS data without IMS interaction) and CS Fallback. Common issues for multiple service categories should be resolved by single solution to limit the amount of overall functionality and to avoid complexity.
The basic eMPS, i.e. priority handling of IMS based multimedia service, EPS bearer services and CS Fallback have completed in Rel‑10. In Rel‑11, Single Radio Voice Call Continuity (SRVCC) from LTE to UTRAN/GERAN/1xCS will be investigated based on Rel‑10 SRVCC specification.
The result of the analysis should be suitable as a basis for normative MPS specification work.
The scope of the MPS part is to further investigate:
- The signalling and procedures for identifying priority and authorizing the usage of priority service.
- The required priority attributes used in enabling end-to-end priority marking and priority treatment during establishment, modification and release of an IMS based priority voice/video/data session.
- The scenarios and capabilities for supporting priority EPS bearer data services.
- The potential impacts on existing and relevant standard procedures in order to provide preferential treatment for MPS requests in the event of congestion.
- Inter-working with other IMS and CS networks to provide an end-to-end priority service. |
23.855 | Data Identification in Access Network Discovery and Selection Function (ANDSF) (DIDA) | TR | 11.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.855/23855-b00.zip | This Technical Report describes proposed extensions to ANDSF Inter-System Routing Policies (ISRP) to provide to operators a better control of the network resources used for each application or IP flow. Specifically the Technical Report focuses on additional mechanism to identify classes of traffic an ISRP applies to.
Any extension to the ANDSF framework which is not related to identification of traffic is outside the scope of this Technical Report. |
23.857 | Study of Evolved Packet Core (EPC) nodes restoration | TR | 11.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.857/23857-b00.zip | The present document contains the study on EPC nodes failure and restoration.
This document will consider any necessary operational protocol recovery mechanisms in the EPS in order to restore the subscriber service in the event of EPC node failure or clean up the hanging resource in other EPC nodes if the recovery of the failed node is not possible. The document will address the following aspects:
- list the different network failure scenarios to be analyzed for EPC nodes: MME, S4-SGSN, SGW and PGW;
- identify precisely the problems resulting from the current definition of the standards;
- list various possible solutions;
- identify pros and cons of possible solutions;
- conclude on potential enhancements to the standards (depending on gains vs complexity). |
23.885 | Feasibility Study of Single Radio Voice Call Continuity (SRVCC) from UTRAN/GERAN to E-UTRAN/HSPA; Stage 2 | TR | 11.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.885/23885-b00.zip | The objective of the feasibility study is to investigate a solution for supporting Single Radio Voice Call Continuity (SRVCC) from 3GPP UTRAN/GERAN CS access to 3GPP E-UTRAN/HSPA access, for voice call initiated in LTE/HSPA access and previously handed over to UTRAN/GERAN CS access, as well as for the voice call directly initiated in UTRAN/GERAN CS access.
This Technical Report investigates solutions for SRVCC for voice calls that are anchored in the IMS.
Coordination between the SRVCC for voice call and the handover of non‑voice PS bearers is also covered. |
23.888 | System improvements for Machine-Type Communications (MTC) | TR | 11.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.888/23888-b00.zip | This Technical Report studies and evaluates architectural aspects of the System Improvements for Machine Type Communications requirements specified in TS 22.368 [2].
Specifically, the following system improvements are considered:
- Architectural enhancements to support a large number of Machine-Type Communication (MTC) devices in the network;
- Architectural enhancements to fulfil MTC service requirements;
- Support combinations of architectural enhancements for MTC, though not all combinations may by possible.
The end-to-end aspects of communication between MTC devices and MTC servers (which can be located outside or inside the network operator's domain) are out of the scope of this study. However, the transport services for MTC as provided by the 3GPP system and the related optimizations are considered in this study. In addition, the aspects needed to ensure that MTC devices and/or MTC servers and/or MTC applications do not cause peak loads of short duration (e.g. a "busy minute" rather than a "busy hour") are within the scope of this TR.
Even though some provided solutions may be beneficial for communications from a MTC Device towards another MTC Device, this particular type communication has not been explicitly considered in this Technical Report.
This Technical Report analyzes architectural aspects to achieve these objectives and to gather technical content until it can be included in the relevant technical specifications.
NOTE: Some aspects in this feasibility study have led into normative specification in TS 23.682 [20], TS 23.060 [21], TS 23.401 [5], TS 23.221 [22] and TS 23.272 [23]. The text of the present document was not updated to align with normative specifications. |
23.903 | Redial solution for voice-video switching | TR | 11.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.903/23903-b00.zip | |
23.919 | Direct tunnel deployment guideline | TR | 11.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.919/23919-b00.zip | |
23.924 | Feasibility study on Non-Access Stratum (NAS) node selection function above Base Station Controller (BSC) / Radio Network Controller (RNC) | TR | 11.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.924/23924-b00.zip | |
23.975 | IPv6 migration guidelines | TR | 11.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.975/23975-b00.zip | |
23.976 | Push architecture | TR | 11.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.976/23976-b00.zip | |
23.977 | Bandwidth And Resource Savings (BARS) and speech enhancements for Circuit Switched (CS) networks | TR | 11.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.977/23977-b00.zip | |
23.979 | 3GPP enablers for Open Mobile Alliance (OMA); Push-to-talk over Cellular (PoC) services; Stage 2 | TR | 11.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.979/23979-b00.zip | |
23.981 | Interworking aspects and migration scenarios for IPv4-based IP Multimedia Subsystem (IMS) implementations | TR | 11.0.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.981/23981-b00.zip | |
24.002 | GSM - UMTS Public Land Mobile Network (PLMN) Access Reference Configuration | TS | 11.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.002/24002-b00.zip | |
24.007 | Mobile radio interface signalling layer 3; General Aspects | TS | 11.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.007/24007-b00.zip | |
24.010 | Mobile radio interface layer 3; Supplementary services specification; General aspects | TS | 11.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.010/24010-b00.zip | |
23.167 | IP Multimedia Subsystem (IMS) emergency sessions | TS | 11.11.0 | S2 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.167/23167-bb0.zip | |
23.218 | IP Multimedia (IM) session handling; IM call model; Stage 2 | TS | 11.6.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/23_series/23.218/23218-b60.zip | |
24.030 | Location Services (LCS); Supplementary service operations; Stage 3 | TS | 11.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.030/24030-b00.zip | |
24.067 | Enhanced Multi-Level Precedence and Pre-emption service (eMLPP); Stage 3 | TS | 11.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.067/24067-b00.zip | |
24.072 | Call Deflection (CD) supplementary service; Stage 3 | TS | 11.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.072/24072-b00.zip | |
24.080 | Mobile radio interface layer 3 supplementary services specification; Formats and coding | TS | 11.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.080/24080-b00.zip | The present document contains the coding of information necessary for support of supplementary service operation on the mobile radio interface layer 3.
Clause 2 gives the functional definitions and contents of messages for call independent supplementary service operations. Messages necessary for support of call related supplementary service operations are defined in TS 24.008.
Clause 3 gives the general format and coding for messages used for call independent supplementary service and the format and coding of information elements used for both call related and call independent supplementary service operations.
Clause 4 gives the specification of the call related and call independent supplementary service operations. |
24.081 | Line Identification supplementary services; Stage 3 | TS | 11.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.081/24081-b00.zip | |
24.082 | Call Forwarding (CF) supplementary services; Stage 3 | TS | 11.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.082/24082-b00.zip | |
24.083 | Call Waiting (CW) and Call Hold (HOLD) supplementary services; Stage 3 | TS | 11.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.083/24083-b00.zip | |
24.084 | Multi Party (MPTY) supplementary service; Stage 3 | TS | 11.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.084/24084-b00.zip | |
24.085 | Closed User Group (CUG) supplementary service; Stage 3 | TS | 11.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.085/24085-b00.zip | |
24.086 | Advice of Charge (AoC) supplementary services; Stage 3 | TS | 11.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.086/24086-b00.zip | |
24.087 | User-to-User Signalling (UUS) Supplementary Service; Stage 3 | TS | 11.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.087/24087-b00.zip | |
24.088 | Call Barring (CB) supplementary service; Stage 3 | TS | 11.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.088/24088-b00.zip | |
24.090 | Unstructured Supplementary Service Data (USSD); Stage 3 | TS | 11.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/24_series/24.090/24090-b00.zip |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.