id
stringlengths 4
12
| title
stringlengths 8
250
| type
stringclasses 2
values | version
stringclasses 617
values | working_group
stringclasses 30
values | url
stringlengths 65
81
| scope
stringlengths 0
65.7k
|
|---|---|---|---|---|---|---|
23.035
|
Immediate Service Termination (IST); Stage 2
|
TS
|
11.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.035/23035-b00.zip
| |
23.038
|
Alphabets and language-specific information
|
TS
|
11.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.038/23038-b00.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.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.042
|
Compression algorithm for text messaging services
|
TS
|
11.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.042/23042-b00.zip
| |
23.053
|
Tandem Free Operation (TFO); Service description; Stage 2
|
TS
|
11.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.053/23053-b00.zip
| |
23.057
|
Mobile Execution Environment (MExE); Functional description; Stage 2
|
TS
|
11.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.057/23057-b00.zip
| |
23.060
|
General Packet Radio Service (GPRS); Service description; Stage 2
|
TS
|
11.12.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.060/23060-bc0.zip
| |
23.066
|
Support of Mobile Number Portability (MNP); Technical realization; Stage 2
|
TS
|
11.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.066/23066-b00.zip
| |
23.067
|
enhanced Multi-Level Precedence and Pre-emption Service (eMLPP); Stage 2
|
TS
|
11.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.067/23067-b00.zip
| |
23.072
|
Call Deflection (CD) supplementary service; Stage 2
|
TS
|
11.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.072/23072-b00.zip
| |
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.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.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.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.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
| |
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
| |
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.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
| |
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
| |
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
| |
23.278
|
Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 4; Stage 2; IM CN Interworking
|
TS
|
11.0.1
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.278/23278-b01.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
| |
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.334
|
IP Multimedia Subsystem (IMS) Application Level Gateway (IMS-ALG) - IMS Access Gateway (IMS-AGW) interface: Procedures descriptions
|
TS
|
11.2.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.334/23334-b20.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.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.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.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.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.008
|
Mobile radio interface Layer 3 specification; Core network protocols; Stage 3
|
TS
|
11.17.1
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.008/24008-bh1.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
| |
24.011
|
Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface
|
TS
|
11.1.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.011/24011-b10.zip
| |
24.022
|
Radio Link Protocol (RLP) for circuit switched bearer and teleservices
|
TS
|
11.0.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.022/24022-b00.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
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.