id
stringlengths 4
12
| title
stringlengths 8
250
| type
stringclasses 2
values | version
stringclasses 612
values | working_group
stringclasses 30
values | url
stringlengths 65
81
| scope
stringlengths 0
65.7k
|
|---|---|---|---|---|---|---|
29.519 | 5G System; Usage of the Unified Data Repository Service for Policy Data, Application Data and Structured Data for Exposure; Stage 3 | TS | 18.9.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.519/29519-i90.zip | |
29.520 | 5G System; Network Data Analytics Services; Stage 3 | TS | 18.10.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.520/29520-ia0.zip | |
29.521 | 5G System; Binding Support Management Service; Stage 3 | TS | 18.6.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.521/29521-i60.zip | |
29.522 | 5G System; Network Exposure Function Northbound APIs; Stage 3 | TS | 18.10.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.522/29522-ia0.zip | |
29.523 | 5G System; Policy Control Event Exposure Service; Stage 3 | TS | 18.6.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.523/29523-i60.zip | |
29.524 | 5G System; Cause codes mapping between 5GC interfaces; Stage 3 | TS | 18.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.524/29524-i10.zip | The present document specifies the mapping:
- performed by the AMF between HTTP responses (Status Codes and Protocol or Application Errors) returned by 5GC NFs to the AMF and 5GMM Cause values sent to UEs;
- performed by the SMF between HTTP responses (Status Codes and Protocol or Application Errors) returned by 5GC NFs to SMF and 5GSM Cause values sent to UEs;
- performed by the SMF between N4 errors returned by the UPF and 5GSM Cause values sent to UEs. |
29.525 | 5G System; UE Policy Control Service; Stage 3 | TS | 18.9.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.525/29525-i90.zip | |
29.526 | 5G System; Network Slice-Specific and SNPN Authentication and Authorization services; Stage 3 | TS | 18.7.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.526/29526-i70.zip | |
29.531 | 5G System; Network Slice Selection Services; Stage 3 | TS | 18.9.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.531/29531-i90.zip | |
29.532 | 5G System; 5G Multicast-Broadcast Session Management Services; Stage 3 | TS | 18.6.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.532/29532-i60.zip | |
29.534 | 5G System; Access and Mobility Policy Authorization Service; Stage 3 | TS | 18.4.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.534/29534-i40.zip | |
29.535 | 5G System; AKMA Anchor Services; Stage 3 | TS | 18.6.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.535/29535-i60.zip | |
29.536 | 5G System; Network Slice Admission Control Services; Stage 3 | TS | 18.8.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.536/29536-i80.zip | |
29.537 | 5G System; Multicast/Broadcast Policy Control services; Stage 3 | TS | 18.5.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.537/29537-i50.zip | |
29.538 | Enabling MSGin5G Service; Application Programming Interfaces (API) specification; Stage 3 | TS | 18.8.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.538/29538-i80.zip | |
29.540 | 5G System; SMS Services; Stage 3 | TS | 18.5.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.540/29540-i50.zip | |
29.541 | 5G System; Network Exposure (NE) function services for Non-IP Data Delivery (NIDD) and Short Message Services (SMS); Stage 3 | TS | 18.3.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.541/29541-i30.zip | |
29.542 | 5G System; Session management services for Non-IP Data Delivery (NIDD); Stage 3 | TS | 18.4.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.542/29542-i40.zip | |
29.543 | 5G System; Data Transfer Policy Control Services; Stage 3 | TS | 18.1.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.543/29543-i10.zip | |
29.544 | 5G System; Secured Packet Application Function (SP-AF) services; Stage 3 | TS | 18.2.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.544/29544-i20.zip | |
29.548 | Service Enabler Architecture Layer for Verticals (SEAL); SEAL Data Delivery (SEALDD) Server Services; Stage 3 | TS | 18.2.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.548/29548-i20.zip | |
29.549 | Service Enabler Architecture Layer for Verticals (SEAL); Application Programming Interface (API) specification; Stage 3 | TS | 18.9.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.549/29549-i90.zip | |
29.550 | 5G System; Steering of roaming application function services; Stage 3 | TS | 18.3.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.550/29550-i30.zip | |
29.551 | 5G System; Packet Flow Description Management Service; Stage 3 | TS | 18.5.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.551/29551-i50.zip | |
29.552 | 5G System; Network Data Analytics signalling flows; Stage 3 | TS | 18.7.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.552/29552-i70.zip | |
29.553 | 5G System; 5G ProSe Anchor Services; Stage 3 | TS | 18.4.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.553/29553-i40.zip | |
29.554 | 5G System; Background Data Transfer Policy Control Service; Stage 3 | TS | 18.3.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.554/29554-i30.zip | |
29.555 | 5G System; 5G Direct Discovery Name Management Services; Stage 3 | TS | 18.5.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.555/29555-i50.zip | |
29.556 | Edge Application Server Discovery Services; Stage 3 | TS | 18.6.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.556/29556-i60.zip | |
29.557 | 5G System; Application Function ProSe Service; Stage 3 | TS | 18.4.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.557/29557-i40.zip | |
29.558 | Enabling Edge Applications; Application Programming Interface (API) specification; Stage 3 | TS | 18.10.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.558/29558-ia0.zip | |
29.559 | 5G System; 5G ProSe Key Management Services; Stage 3 | TS | 18.3.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.559/29559-i30.zip | |
29.561 | 5G System; Interworking between 5G Network and external Data Networks; Stage 3 | TS | 18.5.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.561/29561-i50.zip | |
29.562 | 5G System; Home Subscriber Server (HSS) services; Stage 3 | TS | 18.6.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.562/29562-i60.zip | |
29.563 | 5G System; Home Subscriber Server (HSS) services for interworking with Unified Data Management (UDM); Stage 3 | TS | 18.6.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.563/29563-i60.zip | |
29.564 | 5G System; User Plane Function Services; Stage 3 | TS | 18.7.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.564/29564-i70.zip | |
29.565 | 5G System; Time Sensitive Communication and Time Synchronization Function Services; Stage 3 | TS | 18.10.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.565/29565-ia0.zip | |
29.571 | 5G System; Common Data Types for Service Based Interfaces; Stage 3 | TS | 18.10.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.571/29571-ia0.zip | |
29.572 | 5G System; Location Management Services; Stage 3 | TS | 18.9.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.572/29572-i90.zip | |
29.573 | 5G System; Public Land Mobile Network (PLMN) Interconnection; Stage 3 | TS | 18.10.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.573/29573-ia0.zip | |
29.574 | 5G System; Data Collection Coordination Services; Stage 3 | TS | 18.9.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.574/29574-i90.zip | |
29.575 | 5G System; Analytics Data Repository Services; Stage 3 | TS | 18.9.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.575/29575-i90.zip | |
29.576 | 5G System; Messaging Framework Adaptor Services; Stage 3 | TS | 18.6.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.576/29576-i60.zip | |
29.577 | 5G System; IP Short Message Gateway and SMS Router For Short Message Services; Stage 3 | TS | 18.4.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.577/29577-i40.zip | |
29.578 | 5G System; Mobile Number Portability Services; Stage 3 | TS | 18.2.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.578/29578-i20.zip | |
29.579 | 5G System; Interworking MSC For Short Message Services; Stage 3 | TS | 18.4.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.579/29579-i40.zip | |
29.580 | 5G System; Multicast/Broadcast Service Function services; Stage 3 | TS | 18.7.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.580/29580-i70.zip | |
29.581 | 5G System; Multicast/Broadcast Service Transport Services; Stage 3 | TS | 18.5.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.581/29581-i50.zip | |
29.582 | Mission Critical Data (MCData) interworking with Land Mobile Radio (LMR) systems; Stage 3 | TS | 18.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.582/29582-i00.zip | The present document specifies the protocols needed to support a Mission Critical Data (MCData) system interworking with a Land Mobile Radio (LMR) system based on the IWF-2 interface between an MCData server and an Interworking Function (IWF) as described in 3GPP TS 23.283 [80]. |
29.583 | Application layer support for Personal IoT Network (PINAPP); Personal IoT Network (PIN) server services | TS | 18.1.1 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.583/29583-i11.zip | The present document specifies the stage 3 protocol and data model for PIN-9 interface between the PIN application server and PIN server. It provides stage 3 protocol definitions and message flows, and specifies the API for each service offered by the PIN server over PIN-9 interface. The stage 2 functional requirements are defined in 3GPP TS 23.542 [10]. |
29.585 | 5G System (5GS); Session Management Function (SMF) / Centralized User Configuration (CUC) to Access Network Talker Listener (AN-TL) and Core Network Talker Listener (CN-TL) protocol aspects; Stage 3 | TS | 18.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.585/29585-i10.zip | The present document specifies the protocol of communication in the 5G System between:
- the SMF/CUC and the (R)AN/AN-TL, and
- the SMF/CUC and the UPF/CN-TL,
when the (R)AN and the UPF support the Talker and Listener functionality, for the support of Time Sensitive Networking (TSN) enabled Transport Network (TN) as specified in clauses 4.4.8, 5.28a and Annex M of 3GPP TS 23.501 [2] and Annex F of 3GPP TS 23.502 [3]. |
29.586 | 5G System; SideLink Positioning Key Management Services; Stage 3 | TS | 18.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.586/29586-i10.zip | |
29.591 | 5G System; Network Exposure Function Southbound Services; Stage 3 | TS | 18.10.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.591/29591-ia0.zip | |
29.594 | 5G System; Spending Limit Control Service; Stage 3 | TS | 18.4.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.594/29594-i40.zip | |
29.598 | Unstructured data storage services | TS | 18.7.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.598/29598-i70.zip | |
29.641 | 3GPP Registry for Service Names and Port Numbers | TS | 18.2.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.641/29641-i20.zip | The present document defines 3GPP procedures for Service Name and Port Number registry management. These procedures should be followed by 3GPP WGs when requesting new port numbers for the 3GPP allocated port number solution#6, which is specified in clause 4.4 of the 3GPP TR 29.941 [2].
The present document also maintains a database of the 3GPP allocated port numbers. |
29.658 | SIP Transfer of IP Multimedia Service Tariff Information; Protocol specification | TS | 18.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.658/29658-i00.zip | The present document specifies the Stage 3 of the real-time transfer of Tariff Information between a Charge Determination Point (CDP) and a Charge Generation Point (CGP) by means of the Session Initiation Protocol (SIP).
It identifies the protocol procedures and switching functions needed to support the transfer of tariff information related to IP multimedia services. The information needed to support the ISDN User part (ISUP) signalling aspects of charging (ES 201 296 [6]) for Advice of Charge information purposes is also specified, however, it can be used for other purposes as well where applicable.
The present document is applicable to an environment where different operators are working together. It is also applicable to a single network operator environment.
Whether the present document is applicable to a national environment and/or can be used for inter-network purposes depends on regulatory demands and/or bilateral agreements. It should be noted that there are network requirements and signalling limitations that are not covered because they are outside the scope of the present document. Examples of these are as follows:
- the on-line provided advice of charge information may not accurately reflect the correct charging rate due to discount rates, special charging arrangements, etc. It is out of scope to ensure alignment of this information;
- complaint handling between network operators in case of incorrect advice of charge information;
- explicit encryption or special security mechanisms;
- usage of the transferred tariff information for charging purposes;
- interaction between UE and CGP for possible confirmation of provided tariffs;
- any function behind the CGP towards the UE. |
29.673 | 5G System; UE radio capability management services; Stage 3 | TS | 18.4.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.673/29673-i40.zip | |
29.674 | Interface between the UE radio Capability Management Function (UCMF) and the Mobility Management Entity (MME); Stage 3 | TS | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.674/29674-i00.zip | The present document specifies the UE Radio Capability Management Protocol used on the interface between the MME and UCMF as specified in 3GPP TS 23.401 [2]. In the related stage 2 specifications the prefix S17 is used for these common procedures realised by URCMP.
NOTE: As an alternative of URCMP, the MME could use SBI interface to access UCMF Services. |
29.675 | User Equipment (UE) radio capability provisioning service; Stage 3 | TS | 18.4.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.675/29675-i40.zip | |
29.831 | Study on NRF API enhancements to avoid signalling and storing of redundant data | TR | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.831/29831-i00.zip | The present document identifies deficiencies of the NRF APIs as specified in 3GPP TS 29.510 [2] and studies potential optimization solutions. The document will focus on the following aspects:
-avoid data storage overhead in the NRF due to many NFs (especially NFs from the same NF set) registering with identical information,
-avoid signalling overhead (both in terms of payload size and number of HTTP requests) due to discovery responses containing lots of duplicate information and due to the number of data change notification sent when duplicated data are changed one by one.
-avoid processing overhead (both at NRF and its consumers) resulting e.g. from signalling overhead. |
29.857 | Study on Reducing Information Exposure over SBI | TR | 1.3.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.857/29857-130.zip | |
29.866 | Study on IMS Disaster Prevention and Restoration Enhancement | TR | 1.3.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.866/29866-130.zip | |
29.893 | Study on IETF QUIC Transport for 5GC Service Based Interfaces | TR | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.893/29893-i00.zip | The present document analyses the IETF QUIC protocol and its potential use as a transport protocol for the 5GC Service Based Interfaces.
This technical report provides an analysis of the following aspects:
- Features of transport protocol required for 5GC SBI;
- Features of QUIC applicable to 5GC SBI;
- Comparison of the applicable features of QUIC against TCP for the 5GC SBI;
- Key requirements for 5GC SBI in order to support QUIC as a transport protocol;
- Solutions for supporting the key requirements;
- Impacts to 5GC Service Based Interfaces due to introduction of QUIC. |
29.909 | Diameter-based protocols usage and recommendations in 3GPP | TR | 18.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.909/29909-i00.zip | The present document contains a common set of principles, rules and recommendations across 3GPP WGs to ensure Diameter-based interfaces have the same treatment for release control and generating new applications-id. Also to address in a unified manner the use/re-use of AVPs, and other Diameter BASE (see IETF RFC 3588 [x]) related decisions.
The present document covers all aspects of Diameter usage within 3GPP, including description of the current situation of Diameter usage in different 3GPP WGs (CT3, CT4, SA5) in Release 6/7, describe recommendations and conditions to re-use existing Diameter applications (3GPP or IETF application-id), commands, AVPs and/or AVP values, describe recommendations and conditions to define new Diameter applications, commands, AVPs and/or AVP values, and any other related issues, e.g. the cross-release issue, whether to apply proposed guideline back to existing Diameter applications or not, or only new SAE Diameter interfaces, etc.
To achieve maximum benefit from this work it is strongly recommended that all 3GPP Diameter-based protocols follow the recommendations in the present document.
The present document also serves a placeholder for Diameter inter-operator considerations with brief guidelines on how to deploy & realize the inter-operator Diameter-based roaming infrastructure. |
29.935 | Study on User Data Convergence (UDC) data model | TR | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.935/29935-i00.zip | The present document analyses and evaluates the definition of a Reference Data Model (RDM) for Ud interface between Front-Ends (FEs) for the HSS application and the User Data Repository (UDR).
The stage 3 of the Ud interface in the User Data Convergence (UDC architecture) is defined in 3GPP TS 29.335 [2].
The Reference Data Model (RDM) shall comply with the Common Baseline Information Model for UDC as defined in 3GPP TS 32.182 [3] and it shall follow the concepts of the Framework for Model Handling and Management as defined in 3GPP TS 32.181 [4].
The analysis will comprise the general considerations impacting the RDM for HSS.
The analysis will comprise the following topics:
- The general considerations impacting the RDM for HSS;
- Attributes definition: names, syntax, semantics;
- Object classes & Directory Information Tree: object classes names, attributes grouping, LDAP entries, Distinguished Names and Relative Distinguished Names.
Directory information trees, object classes and attributes in this report should be considered informative since they are subject to additions and/or modification depending on the specific implementation as illustrated in the presented alternatives in this technical report. Even the assignment of attributes to object classes may be redistributed, for example,because the normalization of object classes across different domains may result in attributes being moved to a superclass. Naming is provisional. Diagrams used and naming convention are not standardized. |
29.941 | Guidelines on Port Allocation for New 3GPP Interfaces | TR | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.941/29941-i00.zip | IETF has indicated to 3GPP that future IANA port number assignment requests for protocol only used inside 3GPP networks will be likely rejected except if there is a strong justification for it. The present document provides guidelines for resolving the problem with allocating port numbers for new 3GPP interfaces, as an alternative to IANA assigned port numbers.
Starting from 3GPP Rel-17, any 3GPP working group can rely on these guidelines when defining new interfaces, which require new default port number allocation. |
29.949 | Study on technical aspects on roaming end-to-end scenarios with Voice over LTE (VoLTE) IP Multimedia Subsystem (IMS) and other networks | TR | 18.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.949/29949-i00.zip | The present document describes end-to-end use cases and signalling flows based on the roaming architecture for voice over IMS with local breakout. It summarizes the contents of existing 3GPP technical specifications which are needed for roaming use cases. The scenarios used cover the following use cases:
- registration when roaming;
- routeing from originating visited network to originating home network;
- loopback routeing from originating home network to originating visited network;
- routeing when the originating and terminating user reside in the same home network;
- routeing from the originating home network to the terminating home network;
- routeing from the originating visited network to the terminating home network;
- routeing in terminating home network when user resides in this network;
- routeing from terminating home network to the terminating visited network;
- insertion of service related media in the originating home network;
- routeing through transit networks; and
- access transfer scenarios (SRVCC).
Editor's note: It is ffs if the call forwarding service invocation in a Call Deflection case will be considered. |
29.994 | Recommended infrastructure measures to overcome specific Mobile Station (MS) and User Equipment (UE) faults | TR | 18.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.994/29994-i00.zip | The present document clarifies recommended measures which may be adopted by 3GPP infrastructure utilising GSM or GERAN as access network to enable inter-working to be obtained between network and various User Equipment (UE) implementations of the 3GPP specification. The objective is to obtain compatibility without changing the consolidated set of specifications. The present document describes the recommended changes to the infrastructure to cater for specific faults within some types of UE.
The lifetime of the herein described measures together with their potential impact on optimal network performance is out of the scope of the present document. |
30.531 | Work Plan and Working Procedures - RAN WG3 | TR | 1.57.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/30_series/30.531/30531-015700.zip | |
31.101 | UICC-terminal interface; Physical and logical characteristics | TS | 18.1.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.101/31101-i10.zip | The present document specifies the interface between the UICC and the Terminal for 3GPP telecom network operation.
The present document specifies:
- the requirements for the physical characteristics of the UICC;
- the electrical interface between the UICC and the Terminal;
- the initial communication establishment and the transport protocols;
- the model which serves as a basis for the logical structure of the UICC;
- the communication commands and the procedures;
- the application independent files and protocols.
The administrative procedures and initial card management are not part of the present document.
For the avoidance of doubt, references to clauses of ETSI TS 102 221 [1] include all the clauses of that clause, unless specifically mentioned.
The target specification ETSI TS 102 221 [1] contains material that is outside of the scope of 3GPP requirements and the present document indicates which parts are in the scope and which are not.
A 3GPP ME may support functionality that is not required by 3GPP, but the requirements to do so are outside of the scope of 3GPP. |
31.102 | Characteristics of the Universal Subscriber Identity Module (USIM) application | TS | 18.9.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.102/31102-i90.zip | |
31.103 | Characteristics of the IP Multimedia Services Identity Module (ISIM) application | TS | 18.2.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.103/31103-i20.zip | The present document defines the ISIM application for access to IMS services.
The present document specifies:
- specific command parameters;
- file structures;
- contents of EFs (Elementary Files);
- security functions;
- application protocol to be used on the interface between UICC (ISIM) and Terminal.
This is to ensure interoperability between an ISIM and Terminal independently of the respective manufacturer, card issuer or operator.
The present document does not define any aspects related to the administrative management phase of the ISIM. Any internal technical realisation of either the ISIM or the Terminal is only specified where these are reflected over the interface. The present document does not specify any of the security algorithms that may be used. |
31.104 | Characteristics of the Hosting Party Subscription Identity Module (HPSIM) application | TS | 18.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.104/31104-i00.zip | The present document applies to a H(e)NB supporting the HPSIM for H(e)NB Hosting Party authentication. The present document defines the HPSIM application, the UICC application residing in the Hosting Party Module for H(e)NB Hosting Party authentication and provisioning.
The present document specifies
- identification of the Hosting Party
- security mechanism, e.g. authentication based on EAP-AKA method
- support of information for the initial provisioning (e.g. O&M system contact)
- initialisation procedure on H(e)NB-UICC interface
- O&M procedure |
31.105 | Characteristics of the Slice Subscriber Identity Module application | TS | 18.3.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.105/31105-i30.zip | The present document defines the SSIM application for 3GPP telecom network operation related to Network Slice-Specific Authentication and Authorization procedure.
The present document specifies:
- specific command parameters;
- file structures;
- contents of EFs (Elementary Files);
- security functions;
- application protocol to be used on the interface between UICC (SSIM) and ME.
This is to ensure interoperability between a SSIM and an ME independently of the respective manufacturer, card issuer or operator.
The present document does not define any aspects related to the administrative management phase of the SSIM. Any internal technical realisation of either the SSIM or the ME is only specified where these are reflected over the interface. The present document does not specify any of the security algorithms which may be used. |
31.111 | Universal Subscriber Identity Module (USIM) Application Toolkit (USAT) | TS | 18.10.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.111/31111-ia0.zip | |
31.115 | Secured packet structure for (Universal) Subscriber Identity Module (U)SIM Toolkit applications | TS | 18.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.115/31115-i00.zip | The present document specifies the structure of the Secured Packets in implementations using Short Message Service Point to Point (SMS-PP), Short Message Service Cell Broadcast (SMS-CB), Unstructured Supplementary Service Data (USSD) and and Hyper Text Transfer Protocol (HTTP) based on ETSI TS 102 225 [9].
The structure of the Secured Packets shall comply with the one defined in ETSI TS 102 225 [9]. The present document only contains additional requirements or explicit limitations for SIM/USIM applications.
It is applicable to the exchange of secured packets between an entity in a PLMN and an entity in the (U)SIM.
Secured Packets contain application messages to which certain mechanisms according to ETSI TS 102 224 [2] have been applied. Application messages are commands or data exchanged between an application resident in or behind the PLMN and on the (U)SIM. The Sending/Receiving Entity in the PLMN and the UICC are responsible for applying the security mechanisms to the application messages and thus turning them into Secured Packets. |
31.116 | Remote APDU Structure for (U)SIM Toolkit applications | TS | 18.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.116/31116-i00.zip | |
31.117 | Universal Subscriber Identity Module Application Toolkit (USAT) application behavioural test specification | TS | 18.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.117/31117-i00.zip | The present document describes behavioural tests for the USIM Application Toolkit implemented in Mobile Equipment (ME) or Mobile Stations (MS) supporting a non-removable UICC only within the 3GPP digital cellular telecommunications system, in compliance with the relevant requirements, and in accordance with the relevant guidance given in ISO/IEC 9646‑7 [7] and ETSI ETS 300 406 [20].
This document shall provide alternative verification and testing approaches for test cases initially defined in TS 31.124 [2] or ETSI TS 102 384 respectively. To guarantee the highest possible reliability, the verification of existing requirements shall be done using methods defined by ETSI or 3GPP.
A 3GPP ME may support functionality that is not required by 3GPP, but the requirements to do so are outside of the scope of 3GPP. Thus, the present document does not contain tests or references to ETSI TS 102 384 [3] tests for features which are out of scope of 3GPP.
Due to possible limitations in profile handling and updating it is not intended to use the test cases defined within this document with MEs implemented in accordance with Rel-12 or earlier. |
31.120 | UICC-terminal interface; Physical, electrical and logical test specification | TS | 18.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.120/31120-i00.zip | The present document specifies the interface test for the Terminal / UICC.
The present document specifies the tests of:
- physical characteristics of the UICC;
- the electrical interface between the UICC and the Terminal;
- the initial communication establishment and the transport protocols;
- the application independent procedures. |
31.121 | UICC-terminal interface; Universal Subscriber Identity Module (USIM) application test specification | TS | 18.3.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.121/31121-i30.zip | |
31.122 | Universal Subscriber Identity Module (USIM) conformance test specification | TS | 18.4.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.122/31122-i40.zip | The present document provides the Conformance Test Specification for a Universal IC Card (UICC) defined in TS 31.101 [2] with Universal Subscriber Identity Module (USIM) defined in TS 31.102 [3]. |
31.124 | Mobile Equipment (ME) conformance test specification; Universal Subscriber Identity Module Application Toolkit (USAT) conformance test specification | TS | 18.3.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.124/31124-i30.zip | |
31.127 | UICC-terminal interaction; non-removable Universal Subscriber Identity Module (nrUSIM) application behavioural test specification | TS | 18.2.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.127/31127-i20.zip | The present document provides application behavioural tests for a UE to interoperability with dedicated 3GPP network operations. Where there shall be a description for each compliant implementation including the:
- the test case specific setting of the USIM;
- the applicability of each test case;
- the test configurations;
- the conformance requirement(s) and reference(s) to the related core specifications;
- the test purposes; and
- a brief description of the test procedure and the specific acceptance criteria.
The present document is applicable for MEs supporting a non-removable UICC only. MEs that allow access to the physical card interface as defined in ETSI TS 102 221 [8] or ETSI TS 102 671 [29] shall be tested in accordance to TS 31.121 [2].
This document shall provide alternative verification and testing approaches for test cases initially defined in TS 31.121 [2]. If no ETSI or 3GPP defined alternative method to verify an existing requirement is available or if the result generated by the proposed verification method is less reliable, this has to be clearly stated in the test description.
Due to possible limitations in profile handling and updating it is not intended to use the test case defined within this document with 2G only MEs or MEs implemented in accordance to Rel-12 or earlier.
A 3GPP ME may support functionality that is not required by 3GPP, but the requirements to do so are outside of the scope of 3GPP. The present document does not contain tests for features that are out of scope of 3GPP.
In the present document, unless explicitly stated otherwise, for Rel-13 onwards the term E-UTRAN implicitly refers to E-UTRAN in WB-S1 mode. E-UTRAN in NB-S1 mode is always explicitly referred to as NB-IoT. |
31.130 | (U)SIM Application Programming Interface (API); (U)SIM API for Java™ Card | TS | 18.4.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.130/31130-i40.zip | The present document defines the (U)SIM Application Programming Interface extending the "UICC API for Java Card™" [2].
This API allows to develop a (U)SAT application running together with a (U)SIM application and using 3GPP network features.
The present document includes information applicable to 3GPP network operators, service providers, server – (U)SIM – database manufacturers. |
31.131 | C-language binding to (U)SIM API | TS | 18.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.131/31131-i00.zip | A Subscriber Identity Module Application Programming Interface (SIM API) has been defined in TS 42.019 [4] as a technology-independent API by which toolkit applications and (U)SIMs co-operate. That specification is independent of the programming language technology used to create the application, the platform used to host the application and the runtime environment used to execute the application.
The present document includes information applicable to (U)SIM toolkit application developers creating applications using the C programming language ISO/IEC 9899 [7]. The present document describes an interface between toolkit applications written in the C programming language and the (U)SIM in order to realize the co-operation set forth in TS 42.019 [4]. In particular, the API described herein provides the service of assembling proactive commands and disassembling the responses to these commands for the application programmer.
Software tools, integrated software development environments and software management systems that may be used to create application programs are explicitly out of scope of the present document. |
31.133 | IP Multimedia Services Identity Module (ISIM) Application Programming Interface (API); ISIM API for Java Card™ | TS | 18.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.133/31133-i00.zip | The present document defines the ISIM Application Programming Interface extending the "UICC API for Java Card™" [2].
This API allows to develop an application running together with a ISIM application.
The present document includes information applicable to network operators, service providers, server -,–ISIM – and database anufactures. |
31.213 | Test specification for (U)SIM; Application Programming Interface (API) for Java Card™ | TS | 18.1.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.213/31213-i10.zip | The present document covers the minimum characteristics considered necessary in order to provide compliance to TS 31.130 [2].
The present document describes the technical characteristics and methods of test for testing the (U)SIM API for Java CardTM (TS 31.130 [2]) implemented in the (U)SIM. It specifies the following parts:
- test applicability;
- test environment description;
- tests format;
- test area reference;
- conformance requirements;
- test suite files;
- test procedure;
- test coverage; and
- a description of the associated testing tools that shall be used. |
31.220 | Characteristics of the Contact Manager for 3GPP UICC applications | TS | 18.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.220/31220-i00.zip | The present document defines the Contact Manager for 3GPP UICC applications based on OMA DS [7].
The present document specifies the external interface between the Contact Manager Server in the UICC and the Contact Manager External Client in the ME;
Any internal technical realization of either the Contact Manager Server or clients is only specified where these are reflected over the interfaces. |
31.221 | Contact Manager Application Programming Interface (API); Contact Manager API for Java Card | TS | 18.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.221/31221-i00.zip | The present document defines the internal interface characteristics of the Contact Manager for 3GPP UICC applications [2].
The internal interface between the Contact Manager Server application on the UICC and the Contact Manager Client application on the UICC enables Java Card™ platform based applets, defined in [3], [4] and [5], to invoke and register to the Contact Manager Server services. In particular, the Contact Manager Java Card™ based API provides methods to:
- Read/Update/Create/Delete contact(s) in the Contact Manager Server;
- Manage group of contacts in the Contact Manager Server;
- Search for a contact in the Contact Manager Server storage;
- manage the contacts structure;
- Register/Un-register the application to pre-defined events (e.g. application to be notified when contacts are modified in the Contact Manager Server).
This API allows to develop an application running together with a Contact Manager [2]. |
31.822 | Study on GBA_U Based APIs | TR | 18.1.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.822/31822-i10.zip | The present document studies the GBA_U based APIs. |
31.826 | Study on new UICC application for NSSA | TR | 18.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.826/31826-i00.zip | The aim of this Technical Report is to study the aspects for any potential enhancements on the UICC to be developed by CT6 based on the outcome of 3GPP TS 33.501. This work does not include selecting or standardizing any specific EAP method or associated EAP credential types for NSSAA.
For each of the objectives in the scope of the CT6 study, the UICC aspects that are to be covered in this study are as follows:
- Enhancements to support network slice-specific authentication and authorization using the UICC
- Study potential solutions for slice-specific authentication using new specific UICC application
- Study information the UICC application for NSSAA needs to contain
- Study information needed by the ME to select the correct UICC application used for NSSAA, in the case where multiple such UICC applications are available on the UICC. This information will not include UICC application selection based on a specific EAP method or type of EAP credentials.
- Study the interface that the new UICC application should feature in order to support NSSAA
Note: The study item in CT6 will not cover any security-related aspects within SA3's remit. |
31.900 | SIM/USIM internal and external interworking aspects | TR | 18.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.900/31900-i00.zip | The present document describes
- the different cases of interworking between a 2G or 3G ICC and a 2G or 3G ME.
- the different cases of interworking between any given ME/ICC combination and the rest of the network
- the possibilities of interworking between a SIM and a USIM together on a single UICC
- the possibilities of interworking between several USIMs on a single UICC |
31.970 | UICC power optimisation for Machine-Type Communication (MTC) | TR | 18.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.970/31970-i00.zip | The present document has the objective to describe the power consumption caused by UICC when it is idle and identify the potential solutions to allow the reduction or removal of the UICC power supply in order to save power when the UICC is not required for long periods of time.
This document identifies conditions which might need to be applied to the UICC platform. |
32.101 | Telecommunication management; Principles and high level requirements | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.101/32101-i00.zip | The present document establishes and defines the management principles and high-level requirements for the management of PLMNs.
In particular, the present document identifies the requirements for:
- the upper level of a management system;
- the reference model, showing the elements the management system interacts with;
- the network operator processes needed to run, operate and maintain a network;
- the functional architecture of the management system;
- the principles to be applied to management interfaces.
The requirements identified in the present document are directed to the further development of management specifications as well as the development of management products. The present document can be seen as guidance for the development of all other Technical Specification addressing the management of PLMNs.
The present document does not provide physical architectures of the management system. These aspects are defined and discussed in more detail in TS 32.102 [101].
Verbal forms used to indicate requirements in the present document (e.g. "shall", "should", "may") are used in compliance with 3GPP specification Drafting Rules TR 21.801 [104]. |
32.102 | Telecommunication management; Architecture | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.102/32102-i00.zip | The present document identifies and standardises the most important and strategic contexts in the physical architecture for the management of PLMNs. It serves as a framework to help define a telecom management physical architecture for a planned PLMN and to adopt standards and provide products that are easy to integrate.
The requirements identified in the present document are applicable to all further development of 3GPP Telecom Management specifications as well as the development of PLMN Management products. The present document can be seen as guidance for the development of all other Technical Specification addressing the management of PLMNs, except TS 32.101 [2]. |
32.103 | Telecommunication management; Integration Reference Point (IRP) overview and usage guide | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.103/32103-i00.zip | The present document gives an overview about 3GPP's management capabilities and related functionality.
This document is intended to be a guide into the world of 3GPP management specifications, enabling also non-subject matter experts to gain an understanding about 3GPP's management solutions. |
32.107 | Telecommunication management; Fixed Mobile Convergence (FMC) Federated Network Information Model (FNIM) | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.107/32107-i00.zip | On-going industry convergence and pressure to reduce cost is placing an ever-increasing emphasis on the need to rationalize and align various network management aspects across boundaries of standards/specifications producing organizations. The cost, resulting from integration and management challenges, of the lack of a coherent treatment of the whole network has becoming increasingly apparent to the point where operators of networks are demanding action.
This document provides key concepts and principles for the Federated Network Information Model covering all key aspects of a solution to the on-going industry convergence challenge. The proposal focuses on Information Model federation and is constructed to best deal with the various contradictory pressures of the current environment providing a pragmatic and realizable approach. The structure proposed will be called the Federated Network Information Model (FNIM).
The proposal set out in this document:
Explains:
- How, from a technical perspective, a number of standards and specifications generated by different organizations can function together to bring greater coherence to the management of converged networks and hence reduce operations costs.
- Specifically how TM Forum and 3GPP can work with each other and with other industry groups in a Standards Federation to develop a Federated Network Information Model drawing on insights from the broad community (including the TM Forum SID [7], TM Forum MTNM/MTOSI [8], 3GPP SA5 IRPs [14], DMTF CIM [15]).
- How the Federated Network Information Model can be used from a technical perspective (with the focus here being the Network Model).
Recognizes:
- The network is “always on”, therefore changes in management solutions should not impact networks in operation.
- There will always be on-going change.
- That this is only a start on a very long journey.
Allows and enables:
- Decoupling of concerns across the industry whilst growing industry coherence.
- Differing delivery pace across the industry whilst aiming for industry convergence.
- Variety from innovation whilst removing unnecessary variety in management infrastructure.
- Temporary divergences and overlaps during the convergence process.
Ensures:
- Change is made only as a result of understanding of specific market needs.
- Progress by providing coherent solutions to satisfy the needs of all participating industry partners in order not to be blocked by the slowest laggard.
Highlights:
- The challenges of dealing with differing methodologies/tooling used across the standards arena and points out that methodology/tooling differences if ignored will significantly slow progress towards the target.
- The need for development of a new governance regime and points to some of the attributes of such a regime.
- An approach of gradual restructuring and a controlled converging coherence starting small and growing step by value-justified step.
- The challenge of presenting the models so all can have an identical understanding.
- The challenge of interpreting models from different origins, with their different terminology and viewpoints, to arrive at a shared understanding through a federated model. This leads to recognition of the need for a deeper uniform semantic analysis of the area covered by the umbrella information model (UIM) and the navigation points among concrete models which may further lead to the need for the development of information architectures and patterns.
This document focuses on the Information Model aspect of the problem as it is clear that the lack of an agreed-upon, coherent information model across organizational boundaries to support the FMC aspects of the industry that defines the things to be managed and the way they should be expressed is one of the first aspects that need to be tackled.
Editor’s note: Prior to embarking on a further summary of the proposal and its benefits, it is important to emphasize that the definition of the term “model” has to be carefully considered. A model is comprised of parts that themselves can be seen as models. As a consequence whether this activity results in a single model or a set of models depends upon perspective. The critical consideration is whether the parts of the solution can be interrelated and from the perspective of the problem highlighted above whether the parts can be interrelated across what were previously un-navigable barriers. The solution offers this navigability. Conversely it is critical that the solution offers appropriate decoupling of concerns and of governance. Whether this is considered one model or many is not relevant as long as the solution offers the properties, such as those noted above, that are critical for industry success.
This document proposes a Federated approach to model development and emphasizes the need for the development of an Umbrella Information Model (UIM) and its relationships with the other domain specific models. The document also deals with direct relationships between domain/technology specific concrete models.
It is proposed that:
- The work will be published and expressed in UML and will also be published in formats appropriate for each of the participating bodies to absorb (this may require nothing more than the UML format in some cases). The output form required by a particular body will be generated by resources contributed by that body.
- As necessary the model will be embellished using stereotype to express all aspects/properties of the model.
The proposal recognizes that the TM Forum Information Framework (SID) [7] and the TM Forum Integration Framework (MTNM/MTOSI) [8] work provide an enterprise-wide structure and model that can be used to seed the converged model. The proposal recognizes that the 3GPP SA5 group work [14] provides models relating to mobile networks (including RANs, CNs and IMS) that can be used to seed the converged model.
The proposal:
- Ensures on-going reduction in cost of integration and improvement of degree of integration for the purpose of End-to-End management;
- Enables models from many organizations to be used together for the purpose of End-to-End management (recognizing that there are a number of critical governance issues to be overcome to enable this);
- Provides structure for the alignment on a deeper understanding of the semantics and for the development and maintenance of an information architecture and associated patterns;
- Provides both an initial pragmatic solution form and a longer term target;
- Recognizes that the model will evolve in stages, but will never be “completed” and hence this is an on-going activity;
- Recognizes the importance of providing solutions that are backward compatible to existing standards. See [13, 17]
This content of this document has been jointly developed by 3GPP and TM Forum as part of the Joint Working Group on Resource Model Alignment [18]. |
32.111-1 | Telecommunication management; Fault Management; Part 1: 3G fault management requirements | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.111-1/32111-1-i00.zip | The present document specifies the overall requirements for 3GPP Fault Management (FM) as it applies to the Network Elements (NE), Element Manger (EM) and Network Manager (NM).
Clause 4 defines the FM concept and functional requirements for the detection of faults and the generation, collection and presentation of alarms, operational state data and test results across 3GPP systems. These functions are described on a non-formal level since the formal standardization of these functions across the different vendors' equipment is not required. The functional areas specified in the present document cover:
- fault surveillance and detection in the NEs;
- notification of alarms (including alarm cease) and operational state changes;
- retrieval of current alarms from the NEs;
- fault isolation and defence mechanisms in the NEs;
- alarm filtering;
- management of alarm severity levels;
- alarm and operational state data presentation and analysis at the Operations System (OS);
- retention of alarm and operational state data in the NEs and the OS; and
- the management of tests.
Any (re)configuration activity exerted from the EM as a consequence of faults will not be subject of the present document. These are described in [19].
Clause 5 of the present document defines the functional requirements for the standard Itf-N, for the purpose of Fault Management of 3GPP systems , as seen from the Network Manager (NM). The Itf-N is fully standardized so as to connect systems of any vendor to the NM via this interface. |
32.111-2 | Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point (IRP): Information Service (IS) | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.111-2/32111-2-i00.zip | The present document defines the Alarm Integration Reference Point (IRP) Information Service (IS), which addresses the alarm surveillance aspects of Fault Management (FM), applied to the Itf-N.
The purpose of the AlarmIRP is to define an interface through which a "system" (typically a Network Element Manager or a Network Element) can communicate alarm information for its managed objects to one or several Manager Systems (typically Network Management Systems).
The Alarm IRP IS defines the semantics of alarms and the interactions visible across the reference point in a protocol neutral way. It defines the semantics of the operations and notifications visible in the IRP. It does not define the syntax or encoding of the operations, notifications and their parameters. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.