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 |
|---|---|---|---|---|---|---|
29.329 | Sh interface based on the Diameter protocol; Protocol details | TS | 10.5.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.329/29329-a50.zip | |
29.303 | Domain Name System Procedures; Stage 3 | TS | 10.5.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.303/29303-a50.zip | |
29.333 | Multimedia Resource Function Controller (MRFC) - Multimedia Resource Function Processor (MRFP) Mp interface; Stage 3 | TS | 10.7.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.333/29333-a70.zip | |
29.334 | IMS Application Level Gateway (IMS-ALG) – IMS Access Gateway (IMS-AGW); Iq Interface; Stage 3 | TS | 10.7.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.334/29334-a70.zip | |
29.335 | User Data Convergence (UDC); User data repository access protocol over the Ud interface; Stage 3 | TS | 10.2.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.335/29335-a20.zip | |
29.364 | IP Multimedia Subsystem (IMS) Application Server (AS) service data descriptions for AS interoperability | TS | 10.4.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.364/29364-a40.zip | This specification standardizes
- the structure and the coding of the service data that are transported over the Sh interface between an Application Server supporting Multimedia Telephony supplementary services as defined in 3GPPP TS 22.173 [1] and the HSS. Two optional formats are specified. One is based on a binary coding of the service data and supports the subset of MMTEL services corresponding to PSTN/ISDN and CS supplementary services. The other uses an XML format and supports the full set of MMTEL Services.
- the structure and the coding of a set of generic IMS user group data over the Sh interface.
- the structure and the coding of the service data (ODB Information for IMS Oriented Services) that are transported over the Sh interface between an Application Server supporting services that are subject to IMS-ODB as defined in 3GPP TS 22.041[25] and the HSS.
- the structure and the coding of the IMS CAMEL subscription data transported using Sh interface. |
29.414 | Core network Nb data transport and transport signalling | TS | 10.0.2 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.414/29414-a02.zip | |
29.415 | Core network Nb interface user plane protocols | TS | 10.0.1 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.415/29415-a01.zip | |
29.272 | Evolved Packet System (EPS); Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol | TS | 10.10.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.272/29272-aa0.zip | |
29.816 | Study on PCRF failure and restoration | TR | 10.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.816/29816-a00.zip | The present document contains the results of the study on PCRF failure and restoration.
Target failure and recovery scenarios are detailed; the following scenarios are addressed (incl. roaming):
- Single PCRF deployment (covering also the equivalent scenario of multiple PCRFs with a fixed assignment of PCRFs);
- Multiple PCRFs and the DRA is used;
PCRF node failures of different type (e.g. complete outage, loss of dynamic data) and the aspect of reliability in signaling connections will be studied.
Functional requirements for solutions to handle such cases in a standardized way are defined, considering the network elements PCRF, PCEF, BBERF, AF and DRA and taking operators’ preferences into account (e.g. minimal impact on user experience versus maximal control/minimum risk for the operator).
The study describes the potential solutions, which include procedures and signalling between PCRF and other PCC related network nodes, and procedures and signalling between Diameter clients (i.e. PCEF/BBERF/AF) and the DRA.
Per solution the impacted 3GPP specifications and the necessary changes therein are listed.
The study report finally evaluates the solutions and draws conclusions with respect to the type of solutions and their feasibility in terms of implementation effort/complexity. |
29.994 | Recommended infrastructure measures to overcome specific Mobile Station (MS) and User Equipment (UE) faults | TR | 10.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.994/29994-a00.zip | |
29.332 | Media Gateway Control Function (MGCF) - IM Media Gateway; Mn interface | TS | 10.8.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.332/29332-a80.zip | |
29.909 | Diameter-based protocols usage and recommendations in 3GPP | TR | 10.0.1 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.909/29909-a01.zip | |
31.101 | UICC-terminal interface; Physical and logical characteristics | TS | 10.1.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.101/31101-a10.zip | |
31.103 | Characteristics of the IP Multimedia Services Identity Module (ISIM) application | TS | 10.3.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.103/31103-a30.zip | |
31.111 | Universal Subscriber Identity Module (USIM) Application Toolkit (USAT) | TS | 10.17.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.111/31111-ah0.zip | |
31.115 | Secured packet structure for (Universal) Subscriber Identity Module (U)SIM Toolkit applications | TS | 10.1.1 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.115/31115-a11.zip | |
31.116 | Remote APDU Structure for (U)SIM Toolkit applications | TS | 10.4.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.116/31116-a40.zip | |
29.658 | SIP Transfer of IP Multimedia Service Tariff Information; Protocol specification | TS | 10.1.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.658/29658-a10.zip | |
30.820 | Telecommunication management; Project scheduling and open issues for SA5, Release 10 | TR | 10.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/30_series/30.820/30820-a00.zip | The present document contains the up-to-date SA5 Work Item Descriptions (WIDs) and captures the status of all SA5 work items in the current Release.
This TR is used as a mean to provide input to the 3GPP work plan handled by MCC.
Status list of Work items can be found in Annex A of the present document. |
31.120 | UICC-terminal interface; Physical, electrical and logical test specification | TS | 10.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.120/31120-a00.zip | |
31.130 | (U)SIM Application Programming Interface (API); (U)SIM API for Java™ Card | TS | 10.4.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.130/31130-a40.zip | |
31.131 | C-language binding to (U)SIM API | TS | 10.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.131/31131-a00.zip | |
31.133 | IP Multimedia Services Identity Module (ISIM) Application Programming Interface (API); ISIM API for Java Card™ | TS | 10.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.133/31133-a00.zip | |
31.121 | UICC-terminal interface; Universal Subscriber Identity Module (USIM) application test specification | TS | 10.6.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.121/31121-a60.zip | |
31.220 | Characteristics of the Contact Manager for 3GPP UICC applications | TS | 10.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.220/31220-a00.zip | |
31.124 | Mobile Equipment (ME) conformance test specification; Universal Subscriber Identity Module Application Toolkit (USAT) conformance test specification | TS | 10.8.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.124/31124-a80.zip | |
31.221 | Contact Manager Application Programming Interface (API); Contact Manager API for Java Card | TS | 10.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.221/31221-a00.zip | |
31.213 | Test specification for (U)SIM; Application Programming Interface (API) for Java Card™ | TS | 10.1.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.213/31213-a10.zip | |
32.101 | Telecommunication management; Principles and high level requirements | TS | 10.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.101/32101-a10.zip | |
32.102 | Telecommunication management; Architecture | TS | 10.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.102/32102-a00.zip | |
31.900 | SIM/USIM internal and external interworking aspects | TR | 10.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.900/31900-a00.zip | |
31.122 | Universal Subscriber Identity Module (USIM) conformance test specification | TS | 10.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.122/31122-a00.zip | |
32.111-2 | Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point (IRP): Information Service (IS) | TS | 10.5.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.111-2/32111-2-a50.zip | |
31.828 | UICC access to IMS | TR | 10.0.0 | C6 | https://www.3gpp.org/ftp/Specs/archive/31_series/31.828/31828-a00.zip | |
32.103 | Telecommunication management; Integration Reference Point (IRP) overview and usage guide | TS | 10.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.103/32103-a10.zip | |
32.121 | Telecommunication management; Advanced Alarm Management (AAM) Integration Reference Point (IRP): Requirements | TS | 10.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.121/32121-a00.zip | |
32.111-6 | Telecommunication management; Fault Management; Part 6: Alarm Integration Reference Point (IRP): Solution Set (SS) definitions | TS | 10.4.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.111-6/32111-6-a40.zip | |
32.140 | Telecommunication management; Subscription Management (SuM) requirements | TS | 10.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.140/32140-a00.zip | |
32.141 | Telecommunication management; Subscription Management (SuM) architecture | TS | 10.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.141/32141-a00.zip | |
32.150 | Telecommunication management; Integration Reference Point (IRP) Concept and definitions | TS | 10.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.150/32150-a20.zip | |
32.126 | Telecommunication management; Advanced Alarm Management (AAM) Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 10.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.126/32126-a10.zip | |
32.153 | Telecommunication management; Integration Reference Point (IRP) technology specific templates, rules and guidelines | TS | 10.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.153/32153-a20.zip | |
32.154 | Telecommunication management; Backward and Forward Compatibility (BFC); Concept and definitions | TS | 10.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.154/32154-a00.zip | |
32.155 | Telecommunication management; Requirements template | TS | 10.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.155/32155-a00.zip | |
32.171 | Telecommunication management; Subscription Management (SuM) Network Resource Model (NRM) Integration Reference Point (IRP); Requirements | TS | 10.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.171/32171-a00.zip | The present document defines, in addition to the requirements defined in [1], [2], [3] and [4], requirements for the present SuM NRM IRP. |
32.172 | Telecommunication management; Subscription Management (SuM) Network Resource Model (NRM) Integration Reference Point (IRP): Information Service (IS) | TS | 10.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.172/32172-a20.zip | The present document defines the Network Resources Model (NRM) for the SuM IRP. |
32.176 | Telecommunication management; Subscription Management (SuM) Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 10.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.176/32176-a30.zip | The present document is part of an Integration Reference Point (IRP) named Subscription Management (SuM) Network Resource Model (NRM) IRP, through which an IRPAgent can communicate configuration management information to one or several IRPManagers concerning SuM resources. The SuM NRM IRP comprises a set of specifications defining Requirements, a protocol neutral Information Service and one or more Solution Set(s).
The present document specifies the Solution Sets for the SuM NRM IRP.
This specification is related to 3GPP TS 32.172 [5] V10.2.X. |
32.181 | Telecommunication management; User Data Convergence (UDC); Framework for Model Handling and Management | TS | 10.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.181/32181-a00.zip | |
32.182 | Telecommunication management; User Data Convergence (UDC); Common baseline information model (CBIM) | TS | 10.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.182/32182-a00.zip | |
32.111-1 | Telecommunication management; Fault Management; Part 1: 3G fault management requirements | TS | 10.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.111-1/32111-1-a20.zip | |
32.250 | Telecommunication management; Charging management; Circuit Switched (CS) domain charging | TS | 10.6.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.250/32250-a60.zip | |
32.152 | Telecommunication management; Integration Reference Point (IRP) Information Service (IS) Unified Modelling Language (UML) repertoire | TS | 10.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.152/32152-a10.zip | 3GPP has chosen UML to capture systems behaviour in the IRP IS context.
UML provides a rich set of concepts, notations and model elements to model distributive systems. Usage of all UML notations and model elements is not necessary for the purpose of IRP IS specifications. This TS documents the necessary and sufficient set of UML notations and model elements, including the ones built by the UML extension mechanism <<stereotype>>, for use by 3GPP IRP IS authors. Collectively, this set of notations and model elements is called the 3GPP IRP IS modelling repertoire.
The selection of the UML notations and model elements in this repertoire is based on the needs of the existing 3GPP IRP IS specifications. Future IRP IS releases may require the use of additional UML notations or model elements.
IRP IS specifications shall employ the UML notation and model elements of this repertoire and may also employ other UML notation and model elements considered necessary. However, before any other UML notation and model elements may be employed in an approved 3GPP IRP specification, the other notation and model elements should be agreed for inclusion first in this repertoire. |
32.251 | Telecommunication management;Charging management;Packet Switched (PS) domain charging | TS | 10.15.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.251/32251-af0.zip | The present document is part of a series of Technical Specifications (TSs) specifying charging functionality and charging management in Packet Switched networks (GSM/UMTS, EPS). The 3GPP core network charging architecture and principles are specified in TS 32.240 [1], which provides an umbrella for other charging management documents that specify:
- the content of the CDRs per domain / subsystem / service (offline charging);
- the content of real-time charging messages per domain / subsystem /service (online charging);
- the functionality of online and offline charging for those domains / subsystems / services;
- the interfaces that are used in the charging framework to transfer the charging information (i.e. CDRs or charging events).
The complete document structure for the charging TSs is defined in TS 32.240 [1].
The present document specifies the offline and online charging description for the Packet Switched (PS) domain based on the functional stage 2 description in TS 23.060 [201], TS 23.401 [208] and TS 23.402 [209].
The offline and online charging description for the PS domain encompasses also fixed broadband access in the convergent scenario deployment (i.e. both the fixed broadband access network and Evolved Packet Core (EPC) owned by a single operator) based on the functional stage 2 description in the corresponding Annex of TS 23.203 [215].
This charging description includes the offline and online charging architecture and scenarios specific to the PS domain, as well as the mapping of the common 3GPP charging architecture specified in TS 32.240 [1] onto the PS domain.
It further specifies the structure and content of the CDRs for offline charging, and the charging events for online charging. The present document is related to other 3GPP charging TSs as follows:
- The common 3GPP charging architecture is specified in TS 32.240 [1];
- The parameters, abstract syntax and encoding rules for the CDRs are specified in TS 32.298 [51];
- A transaction based mechanism for the transfer of CDRs within the network is specified in TS 32.295 [54];
- The file based mechanism used to transfer the CDRs from the network to the operator's Billing Domain (e.g. the billing system or a mediation device) is specified in TS 32.297 [52];
- The 3GPP Diameter application that is used for PS domain offline and online charging is specified in TS 32.299 [50].
Note that a CAMEL based prepaid function and protocol is also specified for the PS domain (TS 23.078 [206] and TS 29.078 [202]). CAMEL entities and functions are outside the scope of the present document.
All terms, definitions and abbreviations used in the present document, which are common across 3GPP TSs, are defined in TR 21.905 [100]. Those that are common across charging management in PS domains, services or subsystems are provided in the umbrella document TS 32.240 [1] and are copied into clause 3 of the present document for ease of reading. Finally, those items that are specific to the present document are defined exclusively in the present document.
Furthermore, requirements that govern the charging work are specified in TS 22.115 [101]. |
32.252 | Telecommunication management; Charging management; Wireless Local Area Network (WLAN) charging | TS | 10.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.252/32252-a30.zip | The present document is part of a series of documents that specify charging functionality and charging management in GSM/UMTS networks. The GSM/UMTS core network charging architecture and principles are specified in 3GPP TS 32.240 [1], which provides an umbrella for other charging management documents that specify:
- the content of the CDRs per domain and subsystem (offline charging);
- the content of real-time charging messages per domain / subsystem (online charging);
- the functionality of online and offline charging for those domains and subsystems;
- the interfaces that are used in the charging framework to transfer the charging information (i.e. CDRs or charging events).
The complete document structure for these TSs is defined in 3GPP TS 32.240 [1].
The present document specifies the Offline and Online Charging description for the 3GPP interworked Wireless LAN (WLAN), based on the functional stage 2 description of 3GPP WLAN interworking in 3GPP TS 23.234 [201] as well as the Charging support and Charging differentiation for Mobility between 3GPP-Wireless Local Area Network (WLAN) interworking and 3GPP systems, based on the functional stage 2 description of mobility between 3GPP-WLAN and 3GPP systems in 3GPP TS 23.327 [202]. This charging description includes the offline and online charging architecture and scenarios specific to the 3GPP interworked WLAN, as well as the mapping of the common 3GPP charging architecture specified in 3GPP TS 32.240 [1] onto the 3GPP interworked WLAN. It further specifies the structure and content of the CDRs for offline charging, and the charging events for online charging. The present document is related to other 3GPP charging TSs as follows:
- The common 3GPP charging architecture is specified in 3GPP TS 32.240 [1].
- The parameters, abstract syntax and encoding rules for these CDR types are specified in 3GPP TS 32.298 [51].
- A transaction based mechanism for the transfer of CDRs within the network is specified in 3GPP TS 32.295 [54].
- The file based mechanism used to transfer the CDRs from the network to the operator's billing domain (e.g. the billing system or a mediation device) is specified in 3GPP TS 32.297 [52].
- The 3GPP Diameter application that is used for WLAN offline and online charging is specified in 3GPP TS 32.299 [50].
- The Online and Offline Charging description for Trusted WLAN Access Network to the 3GPP EPC, based on the functional stage 2 description in 3GPP TS 23.402 [209], is specified in 3GPP TS 32.251 [11].
All terms, definitions and abbreviations used in the present document, that are common across 3GPP TSs, are defined in the 3GPP Vocabulary, 3GPP TR 21.905 [100]. Those that are common across charging management in GSM/UMTS domains or subsystems are provided in the umbrella document 3GPP TS 32.240 [1] and are copied into clause 3 of the present document for ease of reading. Finally, those items that are specific to the present document are defined exclusively in the present document.
Furthermore, requirements that govern the charging work are specified in 3GPP TS 22.115 [102]. |
32.260 | Telecommunication management;Charging management;IP Multimedia Subsystem (IMS) charging | TS | 10.16.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.260/32260-ag0.zip | |
32.270 | Telecommunication management; Charging management; Multimedia Messaging Service (MMS) charging | TS | 10.0.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.270/32270-a01.zip | |
32.271 | Telecommunication management; Charging management; Location Services (LCS) charging | TS | 10.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.271/32271-a10.zip | The present document is part of a series of Technical Specifications (TSs) that specify charging functionality and charging management in 3GPP networks. The 3GPP core network charging architecture and principles are specified in TS 32.240 [1], which provides an umbrella for other charging management documents that specify
- the content of the CDRs per domain and subsystem (converged and offline charging);
- the content of real-time charging events per domain / subsystem (converged charging);
- the functionality of online and offline charging for those domains and subsystems;
- the interfaces that are used in the charging framework to transfer the charging information (i.e. CDRs or charging events).
The complete document structure for these TSs is defined in TS 32.240 [1].
The present document specifies the LCS Offline and Online Charging description for the LCS domain, based on the functional stage 2 description of the LCS in TS 23.271 [201], and the Ranging and Sidelink Positioning Converged Charging description based on TS 23.586 [206]. This charging description includes the offline and online charging architecture and scenarios specific to the LCS and converged charging architecture and scenarios specific to the Ranging and Sidelink Positioning, as well as the mapping of the common 3GPP architecture specified in TS 32.240 [1] onto the LCS domain including Ranging and Sidelink Positioning. It further specifies the structure and content of the CDRs for offline charging and the charging events for online charging. The present document is related to other 3GPP charging TSs as follows:
- The common 3GPP charging architecture is specified in TS 32.240 [1];
- The parameters, abstract syntax and encoding rules for these CDR types are specified in TS 32.298 [51].
- A transaction based mechanism for the transfer of CDRs within the network is specified in TS 32.295 [54].
- The file based mechanism used to transfer the CDRs from the network to the operator’s billing domain (e.g. the billing system or a mediation device) is specified in TS 32.297 [52].
- The 3GPP Diameter application that is used for LCS domain offline and online charging is specified in TS 32.299 [50].
- The services, operations and procedures of charging, using Service Based Interface are specified in TS 32.290 [55].
- The charging service of 5G system is specified in TS 32.291 [56].
All terms, definitions and abbreviations, used in the present document, that are common across 3GPP TSs, are defined in TR 21.905 [100]. Those that are common across charging management in GSM/UMTS domains, services, or subsystems are provided in the umbrella document TS 32.240 [1] and are copied into clause 3 of the present document for ease of reading. Finally, those items that are specific to the present document are defined exclusively in the present document.
Furthermore, requirements that govern the charging work are specified in TS 22.115 [101]. |
32.272 | Telecommunication management; Charging management; Push-to-talk over Cellular (PoC) charging | TS | 10.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.272/32272-a10.zip | |
32.273 | Telecommunication management; Charging management; Multimedia Broadcast and Multicast Service (MBMS) charging | TS | 10.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.273/32273-a20.zip | |
32.274 | Telecommunication management; Charging management; Short Message Service (SMS) charging | TS | 10.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.274/32274-a00.zip | |
32.280 | Telecommunication management; Charging management; Advice of Charge (AoC) service | TS | 10.5.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.280/32280-a50.zip | |
32.240 | Telecommunication management; Charging management; Charging architecture and principles | TS | 10.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.240/32240-a10.zip | |
32.295 | Telecommunication management; Charging management; Charging Data Record (CDR) transfer | TS | 10.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.295/32295-a00.zip | |
32.296 | Telecommunication management; Charging management; Online Charging System (OCS): Applications and interfaces | TS | 10.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.296/32296-a30.zip | |
32.297 | Telecommunication management; Charging management; Charging Data Record (CDR) file format and transfer | TS | 10.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.297/32297-a20.zip | |
32.151 | Telecommunication management; Integration Reference Point (IRP) Information Service (IS) template | TS | 10.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.151/32151-a10.zip | The present document contains the template to be used for the production of all Integration Reference Point (IRP) Information Service (IS) specifications within the 3GPP 32-series. |
32.299 | Telecommunication management; Charging management; Diameter charging applications | TS | 10.20.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.299/32299-ak0.zip | |
32.300 | Telecommunication management; Configuration Management (CM); Name convention for Managed Objects | TS | 10.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.300/32300-a00.zip | |
32.301 | Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP); Requirements | TS | 10.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.301/32301-a00.zip | |
32.122 | Telecommunication management; Advanced Alarm Management (AAM) Integration Reference Point (IRP): Information Service (IS) | TS | 10.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.122/32122-a00.zip | |
32.275 | Telecommunication management; Charging management; MultiMedia Telephony (MMTel) charging | TS | 10.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.275/32275-a30.zip | |
32.311 | Telecommunication management; Generic Integration Reference Point (IRP) management; Requirements | TS | 10.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.311/32311-a10.zip | |
32.312 | Telecommunication management; Generic Integration Reference Point (IRP) management; Information Service (IS) | TS | 10.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.312/32312-a10.zip | |
32.316 | Telecommunication management; Generic Integration Reference Point (IRP) management; Solution Set (SS) definitions | TS | 10.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.316/32316-a00.zip | |
32.298 | Telecommunication management; Charging management; Charging Data Record (CDR) parameter description | TS | 10.20.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.298/32298-ak0.zip | |
32.302 | Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP); Information Service (IS) | TS | 10.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.302/32302-a00.zip | |
32.306 | Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Solution Set (SS) definitions | TS | 10.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.306/32306-a20.zip | |
32.326 | Telecommunication management; Test management Integration Reference Point (IRP): Solution Set (SS) definitions | TS | 10.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.326/32326-a10.zip | |
32.331 | Telecommunication management; Notification Log (NL) Integration Reference Point (IRP); Requirements | TS | 10.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.331/32331-a00.zip | |
32.322 | Telecommunication management; Test management Integration Reference Point (IRP); Information Service (IS) | TS | 10.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.322/32322-a10.zip | |
32.341 | Telecommunication management; File Transfer (FT) Integration Reference Point (IRP); Requirements | TS | 10.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.341/32341-a00.zip | |
32.321 | Telecommunication management; Test management Integration Reference Point (IRP); Requirements | TS | 10.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.321/32321-a00.zip | |
32.351 | Telecommunication management; Communication Surveillance (CS) Integration Reference Point (IRP); Requirements | TS | 10.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.351/32351-a00.zip | |
32.352 | Telecommunication management; Communication Surveillance (CS) Integration Reference Point (IRP); Information Service (IS) | TS | 10.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.352/32352-a00.zip | |
32.356 | Telecommunication management; Communication Surveillance (CS) Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 10.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.356/32356-a00.zip | |
32.361 | Telecommunication management; Entry Point (EP) Integration Reference Point (IRP); Requirements | TS | 10.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.361/32361-a00.zip | |
32.362 | Telecommunication management; Entry Point (EP) Integration Reference Point (IRP); Information Service (IS) | TS | 10.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.362/32362-a10.zip | |
32.366 | Telecommunication management; Entry Point (EP) Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 10.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.366/32366-a00.zip | |
32.371 | Telecommunication management; Security Management concept and requirements | TS | 10.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.371/32371-a00.zip | |
32.372 | Telecommunication management; Security services for Integration Reference Point (IRP); Information Service (IS) | TS | 10.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.372/32372-a00.zip | |
32.376 | Telecommunication management; Security services for Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 10.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.376/32376-a10.zip | |
32.381 | Telecommunication management; Partial Suspension of Itf-N Integration Reference Point (IRP); Requirements | TS | 10.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.381/32381-a00.zip | |
32.346 | Telecommunication management; File Transfer (FT) Integration Reference Point (IRP): Solution Set (SS) definitions | TS | 10.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.346/32346-a00.zip | |
32.382 | Telecommunication management; Partial Suspension of Itf-N Integration Reference Point (IRP); Information Service (IS) | TS | 10.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.382/32382-a00.zip | |
32.386 | Telecommunication management; Partial Suspension of Itf-N Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 10.1.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.386/32386-a11.zip | |
32.391 | Telecommunication management; Delta synchronization Integration Reference Point (IRP); Requirements | TS | 10.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.391/32391-a00.zip | |
32.336 | Telecommunication management; Notification Log (NL) Integration Reference Point (IRP): Solution Set (SS) definitions | TS | 10.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.336/32336-a00.zip | |
32.342 | Telecommunication management; File Transfer (FT) Integration Reference Point (IRP); Information Service (IS) | TS | 10.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.342/32342-a00.zip | |
32.401 | Telecommunication management;Performance Management (PM);Concept and requirements | TS | 10.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.401/32401-a30.zip | The present document describes the requirements for the management of performance measurements and the collection of performance measurement result data across GSM, UMTS and LTE networks. It defines the administration of measurement schedules by the Network Element Manager (EM), the generation of measurement results in the Network Elements (NEs) and the transfer of these results to one or more Operations Systems, i.e. EM(s) and/or Network Manager(s) (NM(s)).
The basic Performance Management concept that the present document is built upon is described in clause 4.
The requirements of how an EM administers the performance measurements and how the results can be collected are defined in detail in clause 5. Measurements available for collection by NEs are described in the following specifications:
- TS 52.402 for GSM systems;
- TS 32.405, TS 32.406, TS 32.407 and TS 32.408 for UMTS and combined UMTS/GSM systems;
- TS 32.409 for IMS networks;
- TS 32.425 for E-UTRAN;
- TS 32.426 for EPC;
- TS 32.452 for Home Node B (HNB) Subsystem (HNS);
- TS 32.453 for Home enhanced Node B (HeNB) Subsystem (HeNS);
- TS 28.402 for Evolved Packet Core (EPC) and non-3GPP access Interworking System;
- TS 28.403 for Wireless Local Area Network (WLAN).
Effort has been made to ensure consistency in the definition of measurements between different NEs and generations. The performance measurement result is described in Performance Measurement File Format Definition (3GPP TS 32.432 [29]).
The following is beyond the scope of the present document, and therefore the present document does not describe:
- the formal definition of the interface that the EM uses to administer performance measurements in the NEs;
- the formal definition of the interface that the EM uses to collect measurement results from the NEs;
- how the data, once accumulated and collected, could or should be processed, stored, or presented to an end user;
- the information which may be obtained through the collection and processing of call or event related records which have been produced by the NEs primarily for the purpose of raising bills and other charges.
The management requirements have been derived from existing telecommunications operations experience. The management definitions were then derived from other standardisation work so as to minimise the re-invention factor. References are given as appropriate.
The objectives of this standardisation are:
- to provide the descriptions for a standard set of measurements;
- to produce a common description of the management technique for measurement administration and result accumulation; and
- to define a method for the bulk transmission of measurement results across a management interface.
The definition of the standard measurements is intended to result in comparability of measurement result data produced in a multi-vendor wireless network, for those measurement types that can be standardised across all vendors' implementations.
As far as possible, existing standardisation in the area of Performance Management has been re-used and enhanced where particular requirements, peculiar to the mobile telephony environment, have been recognised.
The present document considers all the above aspects of Performance Management for a GSM, UMTS or LTE network and its NEs defined in the core Technical Specifications. However, only those aspects which are specific to a GSM/UMTS/LTE system and particular to wireless network operation are included in the present document. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.