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
|
|---|---|---|---|---|---|---|
32.111-6 | Telecommunication management; Fault Management; Part 6: Alarm Integration Reference Point (IRP): Solution Set (SS) definitions | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.111-6/32111-6-i00.zip | The present document contains the Solution Sets for the IRP whose semantics is specified in Alarm IRP: Information Service (TS 32.111-2 [4]).
These Solution Set specifications are related to 3GPP TS 32.111-2 V14. 0.X [4]. |
32.121 | Telecommunication management; Advanced Alarm Management (AAM) Integration Reference Point (IRP): Requirements | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.121/32121-i00.zip | The purpose of this set of specifications is to provide a mechanism enabling the IRP Manager to improve the information content of alarms, thereby contributing to reduce the time-to-repair. For this configurable rules for advanced alarm filtering are defined to reduce the number of alarms by applying such advanced alarm filtering.
The present document contains the Requirements of Advanced Alarm Management (AAM) on Itf-N IRP.
It defines, for the purpose of AAM on Itf-N, the basic requirements to be fulfilled on Itf-N. |
32.122 | Telecommunication management; Advanced Alarm Management (AAM) Integration Reference Point (IRP): Information Service (IS) | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.122/32122-i00.zip | The purpose of Advanced Alarm Management (AAM) IRP is to define an interface through which an IRPManager can categorize alarm notifications.
The present document is the Information Service of AAM. It defines, for the purpose of categorizing alarm notifications, the information observable and controlled by management system's client and it also specifies the semantics of the interactions used to carry this information. |
32.126 | Telecommunication management; Advanced Alarm Management (AAM) Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.126/32126-i00.zip | The present specifies the Solution Set definitions for the IRP whose semantics are specified in the Advanced Alarm Management (AAM) IRP Information Service (3GPP TS 32.122 [6]).
This Solution Set specification is related to TS 32.122 v14.0.X [6]. |
32.130 | Telecommunication management; Network sharing; Concepts and requirements | TS | 18.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.130/32130-i30.zip | |
32.140 | Telecommunication management; Subscription Management (SuM) requirements | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.140/32140-i00.zip | The present document defines the service requirements and high-level architecture for SuM, including Converged Management of fixed and mobile networks.
SuM is expected evolve in stages over several releases of 3GPP specifications.
The present document provides additional supporting material, which whilst not within the scope of this release, provides an insight towards the future evolution. This is in order that initial work may be done with an appreciation of the wider context expected in future releases of 3GPP specifications.
SuM for 3GPP is primarily concerned with the ability to define subscription profiles and associate the profile with subscribers, users and services that are authorized by agreements. The subscription profile may be used in the process of configuring various network resources (access and core) to make the service a reality for the user.
The management capabilities extend to the creation, modification, synchronization, and re application of subscription profiles.
The present document is oriented towards a standardized interface into the Home Subscriber Server (HSS) in order that services can be provisioned and maintained.
The present document includes information applicable to Network Operators, content providers, and terminal and network manufacturers.
The present document contains the core requirements for SuM, which are sufficient to provide management services.
The method by which applications subscribe to OSA is not within the scope of the present document. |
32.141 | Telecommunication management; Subscription Management (SuM) architecture | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.141/32141-i00.zip | The present document defines the architecture for Subscription Management (SuM) , including Converged Management of fixed and mobile networks. |
32.150 | Telecommunication management; Integration Reference Point (IRP) Concept and definitions | TS | 18.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.150/32150-i10.zip | The present document provides the overall concept for all Integration Reference Point (IRP) specifications.
Relevant IRP overview and high-level definitions are already provided in 3GPP TS 32.101 [1] and TS 32.102 [2].
IRP specifications are intended to be applicable to any management interface (see definition of Integration Reference Point in subclause 3.1). |
32.153 | Telecommunication management; Integration Reference Point (IRP) technology specific templates, rules and guidelines | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.153/32153-i00.zip | The present document contains the templates to be used for the production of Integration Reference Point (IRP) technology-specific specifications. |
32.154 | Telecommunication management; Backward and Forward Compatibility (BFC); Concept and definitions | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.154/32154-i00.zip | The present document gives recommendations to develop future IRP specifications in a Backward Compatible (BC) way so that the group of IRPManager(s) and IRPAgent(s) are not forced to be upgraded in lock step.
The business case for supporting such group, as described above, is complex. It may not relate to the functions of the supported IRPs alone. Rather, it can relate to the cost of coordination of IRPVersion upgrades, the cost of maintaining an old IRPVersion and the cost of using single-vendor or multi-vendor IRPAgents. These considerations are operator deployment scenarios specific.
Clause 4 specifies the Recommendations and clause 5 describes the system context where the Recommendations are applicable.
Editor's Note: The “forward compatability” part is FFS. |
32.155 | Telecommunication management; Requirements template | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.155/32155-i00.zip | The present document contains the template to be used for the production of all IRP based requirements TSs for the 3GPP Telecommunication management.
This template is mainly based on the requirements template (mainly Annex A) in the ITU-T M.3020 recommendation [6]. |
32.156 | Telecommunication management; Fixed Mobile Convergence (FMC) model repertoire | TS | 18.7.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.156/32156-i70.zip | |
32.157 | Telecommunication management; Integration Reference Point (IRP) Information Service (IS) template | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.157/32157-i00.zip | The present document contains the template to be used for the production of all Integration Reference Point (IRP) Information Service (IS) specifications for Converged Management. |
32.158 | Management and orchestration;Design rules for REpresentational State Transfer (REST) Solution Sets (SS) | TS | 18.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.158/32158-i20.zip | The present document defines design rules for REpresentational State Transfer (REST) Solution Sets (SS). These rules are applied when specifying REST Solution Sets. |
32.160 | Management and orchestration; Management service template | TS | 18.7.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.160/32160-i70.zip | |
32.161 | Management and orchestration; JSON expressions (Jex) | TS | 18.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.161/32161-i10.zip | The present TS introduces JSON expressions (Jex). |
32.181 | Telecommunication management; User Data Convergence (UDC); Framework for Model Handling and Management | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.181/32181-i00.zip | The present document specifies the framework for overall management of the User Data Convergence.
In order to accommodate multiple applications and services, existing and new ones, the framework for model handling and management of the UDC as identified by TS 22.101 includes the following items:
- UDC information models:
- UDC information model infrastructure containing the common baseline information model (CBIM), application information models (AIM), and the specialised information model (SIM). The CBIM is standardised in TS 32.cde [4].
- UDC information model handling:
- provide a template and guidelines explaining the design of application information models to be used together with the common baseline information model to create the specialized information model
- describe the process to combine the common baseline information model with application information models in order to produce an operator-specific specialised information model
- Application management data:
- access control data for an application to UDC: identification and authentication
- assignment to an application data model, including linkage to the consolidated data model
- subscription rights for specific events on specific data of specific users
- Consolidated data model management
- lifecycle management of the consolidated data model in the UDR and in the provisioning entity.
- activation/deactivation of application adaptation |
32.182 | Telecommunication management; User Data Convergence (UDC); Common baseline information model (CBIM) | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.182/32182-i00.zip | The present document specifies a Common Baseline Information Model for UDC [2]. This information model denotes an abstract, formal representation of entity types that are common to many applications using the UDR. CBIM describes the basic IOCs of UDC, their properties and their relationships. Detailed requirements for the specification of this Common Baseline Information Model are given in 3GPP TR 22.985 [2] and 3GPP TS 22.101 [3].
From the Common Baseline Information Model specialized information models and data models can be derived. All these derived models are out of the scope of this specification. |
32.240 | Telecommunication management; Charging management; Charging architecture and principles | TS | 18.9.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.240/32240-i90.zip | |
32.250 | Telecommunication management; Charging management; Circuit Switched (CS) domain charging | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.250/32250-i00.zip | The present document is part of a series of Technical Specifications (TSs) that specify charging functionality and charging management in GSM/UMTS networks. The GSM/UMTS core network charging architecture and principles are specified in TS 32.240 [1], which provides an umbrella for other charging management TSs 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 TS 32.240 [1].
The present document specifies the Offline Charging description for the 3GPP Circuit Switched domain, based on the functional descriptions of the 3GPP bearer-, tele- and supplementary services in TS 22.002 [200], TS 22.003 [201] and TS 22.004 [202], respectively. This charging description includes the offline charging architecture and scenarios specific to the CS domain, as well as the mapping of the common charging architecture specified in TS 32.240 [1] onto the CS domain. It further specifies the structure and content of the CDRs for offline 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].
- 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].
Note that online charging for the CS domain is solely based on CAMEL (TS 23.078 [207] and TS 29.078 [213]) and therefore outside the scope of the 32 series of charging specifications.
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.251 | Telecommunication management;Charging management;Packet Switched (PS) domain charging | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.251/32251-i00.zip | |
32.253 | Telecommunication management; Charging management; Control Plane (CP) data transfer domain charging | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.253/32253-i00.zip | The present document is part of a series of documents that specify charging functionality and charging management in GSM/UMTS/LTE networks. The GSM/UMTS/LTE core network charging architecture and principles are specified in TS 32.240 [1], which provides an umbrella for other charging management TSs 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 these TSs is defined in TS 32.240 [1].
The present document specifies the offline and online charging description for Control Plane (CP) data transfer domain, based on the functional stage 2 description in TS 23.682 [243] for Non-IP Data Delivery (NIDD) using SCEF procedures. This charging description includes the offline and online charging architecture and scenarios specific to Control Plane (CP) data transfer domain, as well as the mapping of the common 3GPP charging architecture specified in TS 32.240 [1] onto the Control Plane (CP) data transfer domain. It further specifies the structure and content of the CDRs for offline 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 Control Plane (CP) data transfer domain offline and online charging is specified in TS 32.299 [50].
Control Plane (CP) data transfer is also provided by Short Message Service (SMS), for which charging functionalities are not specified in the present document. SMS charging functionality is defined for Circuit Switched domain in TS 32.250 [10], for Packet Switched domain in TS 32.251 [11] and for SMS Nodes in TS 32.274 [34]. |
32.254 | Telecommunication management; Charging management; Exposure function Northbound Application Program Interfaces (APIs) charging | TS | 18.4.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.254/32254-i40.zip | |
32.255 | Telecommunication management; Charging management; 5G data connectivity domain charging; Stage 2 | TS | 18.7.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.255/32255-i70.zip | |
32.256 | Charging management; 5G connection and mobility domain charging; Stage 2 | TS | 18.6.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.256/32256-i60.zip | |
32.257 | Telecommunication management; Charging management; Edge computing domain charging | TS | 18.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.257/32257-i10.zip | The present document is part of a series of documents that specify charging functionality and charging management in 3GPP networks. The 3GPP core network charging architecture and principles are specified in 3GPP TS 32.240 [2], which provides an umbrella for other charging management TSs 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 these TSs is defined in 3GPP TS 32.240 [2].
The present document specifies the converged offline and online charging description for the Edge Computing domain based on the functional stage 2 description in 3GPP TS 23.501 [8] and 3GPP TS 23.558 [9].
Edge computing in 5G environment involves the services or capabilities provided by multiple service providers and entities in the form of following business roles:
- ASP providing edge application service to the subscribers;
- ECSP providing edge enabling infrastructure and edge enabling services to ASP;
- MNO providing 5GS capabilities supporting edge computing.
The present document specifies following charging aspects for Edge Computing:
- Subscriber charging:
- MNO charges the subscribers for usage of 5GS capabilities supporting edge computing.
- Service-provider charging:
- MNO charges the industry consumer (e.g. ECSP, ASP) for 5GS capabilities provided to support edge computing in total instead of for each individual subscriber;
- ECSP charges the ASP for the edge enabling infrastructure and services.
NOTE: In the Edge Computing deployments, there could be scenarios where one or more of the business roles are supported by a single enterprise, i.e. one enterprise may play a single business role or multiple business roles, for instance the enterprise may only play the MNO role, or play both MNO and ESCP roles. There could be various business models between the service providers and the served consumer(s) for edge computing in 5G environment in manifold business modes such as B2C, B2B and B2B2X, for example (but not limited to). The present document does not impose restrictions to any possible business model or deployment scenario for Edge Computing. |
32.260 | Telecommunication management;Charging management;IP Multimedia Subsystem (IMS) charging | TS | 18.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.260/32260-i30.zip | |
32.270 | Telecommunication management; Charging management; Multimedia Messaging Service (MMS) charging | TS | 18.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.270/32270-i30.zip | The present document is part of a series of Technical Specifications (TSs) that specify charging functionality and charging management in GSM/UMTS networks. The GSM/UMTS core network charging architecture and principles are specified in document 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 TS 32.240 [1].
The present document specifies the offline and online charging description for MMS charging, based on the functional stage 2 descriptions of the MMS in TS 23.140 [201]. This charging description includes the offline and online charging architecture and scenarios specific to the MMS, as well as the mapping of the common 3GPP charging architecture specified in TS 32.240 [1] onto MMS. 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 MMS online charging is specified in TS 32.299 [50].
All terms, definitions and abbreviations used in the present document, that are common across 3GPP TSs, are defined in the 3GPP Vocabulary, 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.271 | Telecommunication management; Charging management; Location Services (LCS) charging | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.271/32271-i00.zip | |
32.272 | Telecommunication management; Charging management; Push-to-talk over Cellular (PoC) charging | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.272/32272-i00.zip | The present document is part of a series of Technical Specifications (TSs) that specify charging functionality and charging management in GSM/UMTS networks. The GSM/UMTS core network charging architecture and principles are specified in TS 32.240 [1], which provides an umbrella for other charging management TSs 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 TS 32.240 [1].
The present document specifies the offline and online charging description for the "Push-to-Talk over Cellular" (PoC) service, based on the functional description of the PoC service in TR 23.979 "3GPP enablers for OMA PoC Services" [200], in OMA-AD-POC "Push to talk over Cellular (PoC) - Architecture" [203], in OMA-CP-POC "OMA PoC Control Plane" [204] and in OMA-UP-POC: "OMA POC User Plane"[205], respectively. This charging description includes the offline and online charging architecture and scenarios specific to PoC, as well as the mapping of the common 3GPP charging architecture specified in TS 32.240 [1] onto the PoC service. 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 PoC offline and online charging is specified in TS 32.299 [50].
All terms, definitions and abbreviations used in the present document, that are common across 3GPP TSs, are defined in the 3GPP Vocabulary, TR 21.905 [100]. Those that are common across charging management in GSM/UMTS domains 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.273 | Telecommunication management; Charging management; Multimedia Broadcast and Multicast Service (MBMS) charging | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.273/32273-i00.zip | The present document is part of a series of Technical Specifications (TSs) that specify charging functionality and charging management in GSM/UMTS networks. The GSM/UMTS core network charging architecture and principles are specified in TS 32.240 [1], which provides an umbrella for other charging management TSs 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 these TSs is defined in TS 32.240 [1].
The present document specifies the Offline and Online Charging description for the Multimedia Broadcast and Multicast Service (MBMS), based on the functional stage 2 description in TS 23.246 [200].
This charging description includes the offline and online charging architecture and scenarios specific to MBMS, as well as the mapping of the common 3GPP charging architecture specified in TS 32.240 [1] onto MBMS.
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 MBMS offline and online charging is specified in TS 32.299 [50].
All terms, definitions and abbreviations used in the present document, that are common across 3GPP TSs, are defined in the 3GPP Vocabulary, TR 21.905 [100]. Those that are common across charging management in GSM/UMTS domains 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.274 | Telecommunication management; Charging management; Short Message Service (SMS) charging | TS | 18.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.274/32274-i10.zip | |
32.275 | Telecommunication management; Charging management; MultiMedia Telephony (MMTel) charging | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.275/32275-i00.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 TSs 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 TS 32.240 [1].
The present document specifies the offline, online and converged charging for MultiMedia Telephony (MMTel) service and supplementary services, based on the functional description of MMTel in TS 22.173 [200]. Charging for the following supplementary services is specified:
- Communications Diversion (CDIV);
- Communication Hold (HOLD);
- CONFerence (CONF);
- Message Waiting Indication (MWI);
- Originating Identity Presentation (OIP) / Originating Identity Restriction (OIR);
- Terminating Identity Presentation (TIP) / Terminating Identity Restriction (TIR);
- Call Barring (CB);
- Explicit Call Transfer (ECT);
- Communication Wait (CW);
- Completion of Communications to Busy Subscriber (CCBS);
- Completion of Communications by No Reply (CCNR);
- Malicious Communication Identification (MCID);
- Customized Alerting Tone (CAT);
- Closed User Group (CUG);
- Personal Network Management (PNM);
- Customized Ringing Signal (CRS);
- Reverse Charging;
- Advice of Charge (AoC).
Charging of these supplementary services is performed at the respective MMTel AS. The MMTel charging aspects are an extension of the basic IMS charging capabilities as specified in the TS 32.260 [20].
This charging description includes the offline, online and converged charging architecture and scenarios specific to the MMTel, as well as the mapping of the common 3GPP charging architecture specified in TS 32.240 [1] onto the MMTel. It further specifies the structure and content of the CDRs, and the charging events.
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 common IMS charging principles are specified in the TS 32.260 [20].
- 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 MMTel 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 [57].
- The charging service of 5G system is specified in TS 32.291 [58]. |
32.276 | Telecommunication management; Charging management; Voice Call Service (VCS) charging | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.276/32276-i00.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 TS 32.240 [1], which provides an umbrella for other charging management TSs that specify:
- the content of the Charging Data Records (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 these TSs is defined in TS 32.240 [1].
The present document specifies the online charging description for Voice Call Service (VCS) charging from a Proxy Function, based on the functional description of the Voice Call Service charging in the EU Roaming Regulations III specifications [298, 299].
The concept of voice call is interpreted as any CS call, whatever the teleservice used (speech, 3.1 kHz audio, Fax, or CS data) except CS video telephony calls (BS 37, 64 kbit/s unrestricted digital info mode).
Voice over LTE is not included in this definition. This charging specification includes the online charging architecture and scenarios specific to VCS charging from a Proxy Function, as well as the mapping of the common 3GPP charging architecture specified in TS 32.240 [1] onto VCS. It further specifies 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 3GPP Diameter application that is used for VCS online charging is specified in TS 32.299 [50].
Offline charging for the VCS is solely based on TS 32.250 [10] and is outside the scope of the present document.
All references, abbreviations, definitions, descriptions, principles and requirements, used in the present document, that are common across 3GPP TSs, are defined in TR 21.905 [100] "Vocabulary for 3GPP Specifications".
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. |
32.277 | Telecommunication management; Charging management; Proximity-based Services (ProSe) charging | TS | 18.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.277/32277-i10.zip | |
32.278 | Telecommunication management;Charging management;Monitoring event charging | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.278/32278-i00.zip | The present document is part of a series of documents that specify charging functionality and charging management in GSM/UMTS/LTE networks. The GSM/UMTS/LTE core network charging architecture and principles are specified in TS 32.240 [1], which provides an umbrella for other charging management TSs 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 these TSs is defined in TS 32.240 [1].
The present document specifies the Offline Charging description for Monitoring Events, based on the functional stage 2 description in TS 23.682 [243]. This charging description includes the offline charging architecture and scenarios specific to Monitoring Events, as well as the mapping of the common 3GPP charging architecture specified in TS 32.240 [1] onto the 3GPP Architecture for Service Capability Exposure. It further specifies the structure and content of the CDRs for offline 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 Monitoring Event offline charging is specified in TS 32.299 [50].
The online charging functionality for Monitoring Events is outside the scope of 3GPP standardisation.
All references, abbreviations, definitions, descriptions, principles and requirements, used in the present document, that are common across 3GPP TSs, are defined in the 3GPP Vocabulary, TR 21.905 [100]. Those that are common across charging management in GSM/UMTS/LTE 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. |
32.279 | Charging management; 5G Multicast-broadcast Services charging | TS | 18.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.279/32279-i10.zip | The present document is part of a series of documents that specify charging functionality and charging management in 3GPP networks. The 3GPP core network charging architecture and principles are specified in TS 32.240 [2], which provides an umbrella for other charging management TSs 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 these TSs is defined in TS 32.240 [2].
The present document specifies the converged charging description for the 5G MBS Session based on the functional stage 2 description in TS 23.247 [9], TS 23.501 [10], TS 23.502 [11] and TS 23.503 [12].
This charging description includes the converged charging architecture and scenarios specific to the 5G MBS Session, with focus on the following charging scenarios:
- MBS session charging for multicast communication.
- MBS session charging for broadcast communication.
It further specifies the structure and content of the CDRs and the charging events for converged charging.
All references, abbreviations, definitions, descriptions, principles and requirements, used in the present document, that are common across 3GPP TSs, are defined in TR 21.905 [1]. Those that are common across charging management in 3GPP networks/domains, services or subsystems are provided in the umbrella TS 32.240 [2] 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. |
32.280 | Telecommunication management; Charging management; Advice of Charge (AoC) service | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.280/32280-i00.zip | The present document specifies the Advice of Charge (AoC) framework for relevant events, sessions, and services. The 3GPP umbrella charging architecture and principles are defined in TS 32.240 [1].
The AoC framework detailed herein provides for both offline and online charging models. It specifies the following:
- The AoC architecture.
- The common principles that govern AoC.
- The AoC function that enables the IMS AoC framework.
- Exemplary message flows.
- AoC interface data description.
All terms, definitions and abbreviations used in the present document, that are common across 3GPP TSs, are defined in the 3GPP Vocabulary, TR 21.905 [100]. Those that are common across charging management in 3GPP network, services or subsystems are provided in the umbrella document TS 32.240 [1] and may be 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.
Requirements that govern the AoC work are specified in TS 22.115 [101]. |
32.281 | Telecommunication management; Charging management; Announcement service | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.281/32281-i00.zip | During any phase of a voice or video call, the Online Charging System (OCS) or Converged Charging System (CCS)may need to deliver billing/charging in-session notifications to the end user via announcements as part of the rating, balance management and billing process. For example, the CCS/OCS may need to inform the user about usage states, threshold crossings, offer statuses, reason for call rejection, alerts about low balances, etc.
Such notifications can be delivered pre-, mid- or post-call.
The Announcement service in the present document provides announcement capabilities for use in a Diameter based online or converged charging session. The CCS/OCS is able to specify that a given announcement be played to a call party in order to deliver charging/billing related notifications. |
32.282 | Charging management; Time-Sensitive Networking (TSN) charging | TS | 18.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.282/32282-i20.zip | The present document is part of a series of documents 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].
The present document specifies the converged charging description for the time sensitive networking domain based on the functional stage 2 description in TS 23.501 [11], TS 23.502 [12] and TS 23.503 [13].
This charging description includes the converged charging architecture, principles, requirements and scenarios specific to the time sensitive networking, with focus on the following charging scenarios: .
- the TSN 5GS bridge configuration and management charging.
- the enabler for time sensitive communication and time synchronization charging.
- the time sensitive communication traffic charging.
It further specifies the structure and content of the CDRs and the charging events for converged charging.
All references, abbreviations, definitions, descriptions, principles and requirements, used in the present document, that are common across 3GPP TSs, are defined in TR 21.905 [8]. Those that are common across charging management in 3GPP networks/domains, services or subsystems are provided in the umbrella 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. |
32.290 | Telecommunication management; Charging management; 5G system; Services, operations and procedures of charging using Service Based Interface (SBI) | TS | 18.9.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.290/32290-i90.zip | |
32.291 | Telecommunication management; Charging management; 5G system, charging service; Stage 3 | TS | 18.10.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.291/32291-ia0.zip | |
32.293 | Telecommunication management; Charging management; Proxy function | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.293/32293-i00.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 TS 32.240 [1], which provides an umbrella for other charging management TSs that specify:
- the content of the Charging Data Records (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 these TSs is defined in TS 32.240 [1].
The present document specifies the Proxy Function in Domestic Service Provider (DSP).
The present document contains the architecture and functions of the Proxy Function logical components and thereby derives the functionality of the Proxy Function interfaces. This charging description only defines the interworking between CAMEL and Diameter. The Ro interface between the Proxy Function and Online Charging System (OCS) is out of scope of the present document.
The present document is related to other 3GPP charging TSs as follows:
- The common 3GPP charging architecture is specified in TS 32.240 [1];
- Voice Call Service (VCS) charging is specified in TS 32.276[36].
All references, abbreviations, definitions, descriptions, principles and requirements, used in the present document, that are common across 3GPP TSs, are defined in TR 21.905 [100] "Vocabulary for 3GPP Specifications". 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. |
32.295 | Telecommunication management; Charging management; Charging Data Record (CDR) transfer | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.295/32295-i00.zip | The present document is part of a series of Technical Specifications (TSs) that specify charging functionality and charging management in 3GPP 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 TSs 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 these TSs is defined in TS 32.240 [1].
The present document specifies the transaction based mechanism for the near real time transfer of CDRs
within the network.
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];
- The file based mechanism used to transfer the CDRs from the network to the operator's Billing Domain (e.g. the post-processing system or a mediation device) is specified in TS 32.297 [52];
The 3GPP Diameter application that is used for offline and online charging is specified in TS 32.299 [50].
All terms, definitions and abbreviations used in the present document, that are common across 3GPP TSs, are defined in the 3GPP Vocabulary, TR 21.905 [100]. Those that are common across charging management in 3GPP 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.296 | Telecommunication management; Charging management; Online Charging System (OCS): Applications and interfaces | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.296/32296-i00.zip | The present document is part of a series of Technical Specifications (TSs) that specify charging functionality and charging management in 3GPP networks. The GSM/UMTS 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 (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 of the charging management TSs is defined in TS 32.240 [1].
The present document covers all internal aspects of the Online Charging System (OCS). The document contains the architecture and functions of the OCS logical components and thereby derives the functionality of the OCS interfaces. A detailed specification of interfaces between the logical OCS components is also included. The functionality of the OCS, as described in the present document, applies to all charging domains (bearer, session and service).
The interfaces connecting to the OCS (e.g. Ro, CAP) are out of the scope of the present document.
NOTE: In the current release the present document is limited to the interface between the charging function and the Rating Function(RF), namely Re.
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 3GPP domains, services, or subsystems are provided in the umbrella document TS 32.240 [1]. 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.297 | Telecommunication management; Charging management; Charging Data Record (CDR) file format and transfer | TS | 18.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.297/32297-i10.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 TSs that specify:
- the content of the CDRs per domain / subsystem / service (offline and converged charging);
- the content of real-time charging messages per domain / subsystem / service (online and converged charging);
- the functionality of online, offline and converged 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 these TSs is defined in TS 32.240 [1].
The present document specifies file based mechanism used to transfer the CDRs from the network to the operator's billing domain (e.g. the post-processing system or a mediation device).
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 3GPP Diameter application that is used for 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 [57].
- The charging service of 5G system is specified in TS 32.291 [58].
All terms, definitions and abbreviations used in the present document, that are common across 3GPP TSs, are defined in the 3GPP Vocabulary, TR 21.905 [100]. Those that are common across charging management in 3GPP 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.298 | Telecommunication management; Charging management; Charging Data Record (CDR) parameter description | TS | 18.9.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.298/32298-i90.zip | |
32.299 | Telecommunication management; Charging management; Diameter charging applications | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.299/32299-i00.zip | The present document is part of a series of Technical Specifications (TSs) that specify charging functionality and charging management in GSM/UMTS networks. The GSM/UMTS 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 (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 TS 32.240 [1].
The present document specifies in detail the Diameter based offline and online charging applications for 3GPP networks. It includes all charging parameters, scenarios and message flows..
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.300 | Telecommunication management; Configuration Management (CM); Name convention for Managed Objects | TS | 18.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.300/32300-i10.zip | The present document is valid for TSs using IRPs and SBMA.
A more detailed background and introduction of the IRP concept is given in 3GPP TS 32.150 [16] and more detailed background for SBMA in 3GPP TS 28.533 [21].
To perform network management tasks, co-operating applications require identical interpretation of names assigned to network resources under management. Such names are required to be unambiguous as well. The present document recommends one name convention for network resources under management in the 3GPP context.
To facilitate integration of network management information obtained via multiple management interfaces based on different Solution Set technologies, identical network resource name semantics shall be conveyed in all management interfaces. The present document specifies one such name convention.
The present document also specifies an IOC/MOC name recommendation (see annex E) in order to avoid potential problems with valid characters in some programming languages.
In this document, the name convention and name recommendation (see annex E) are specified for MO instances whose MO class stereotype is IOC. These specifications are also for MO instances whose MO class stereotype is Support IOC (SupportIOC). |
32.301 | Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP); Requirements | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.301/32301-i00.zip | The purpose of Notification IRP is to define an interface through which an IRPManager can subscribe to an IRPAgent for receiving notifications. The present document is the "Requirements" of Notification IRP. It defines, for the purpose of subscribing to an IRPAgent for receiving notifications, the basic requirements that shall be fulfilled on Itf-N.
How IRPManager discovers the IRPAgent's address or reference (so that IRPManager can invoke an operation) is outside the scope of the present document. |
32.302 | Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP); Information Service (IS) | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.302/32302-i00.zip | The purpose of Notification IRP is to define an interface through which an IRPManager can subscribe to an IRPAgent for receiving notifications. The present document is the "Information Service" of Notification IRP. It defines, for the purpose of subscribing to an IRPAgent for receiving notifications, the information observable and controlled by management system's client and it also specifies the semantics of the interactions used to carry this information. It also defines the information common to all notifications which is called the notificationHeader.
An IRPAgent supporting this IRP IS may emit one or multiple categories of notifications, such as alarms (as specified in Alarm IRP: Information Service [1]) and others. This IRP IS defines a mechanism that IRPManager can use to determine the categories of notifications supported by an IRPAgent. It also defines a mechanism (subscribe and unsubscribe operations) that IRPManager can use to specify the categories of notifications IRPAgent should emit to IRPManager during subscription. It also defines a mechanism (getSubscriptionIds operation) that IRPManager can use to check which categories of notifications it has subscribed to. IRPManager can set and change filter criteria applicable during the life-cycle of a subscription. IRPManager can also exercise flow-control on IRPAgent's emission of notifications (suspendSubscription and resumeSubscription operations).
Using different managerReference, an IRPManager can subscribe several times. It will result in multiple subscriptions. As far as IRPAgent is concerned, notifications are sent to multiple "places".
Using the same managerReference, an IRPManager can subscribe several times specifying different categories of notifications.
This IRP IS does not specify information that is carried in some but not all notifications. That kind of information is specified in other IRP ISs involved. For example, perceivedSeverity is a piece of information specific for notifications carrying alarm information. This information is not defined in the present document but in Alarm IRP: Information Service [1].
How IRPManager discovers the IRPAgent's address or reference (so that IRPManager can invoke an operation) is outside the scope of the present document.
This IRP IS is aligned with ITU-T M.3702 [13] in terms of the definitions of operations for Notification management. |
32.306 | Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Solution Set (SS) definitions | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.306/32306-i00.zip | The present document contains the Solution Sets for the IRP whose semantics is specified in Notification IRP: Information Service (TS 32.302 [7]).
These Solution Set specifications are related to 3GPP TS 32.302 V14.0.X [7]. |
32.311 | Telecommunication management; Generic Integration Reference Point (IRP) management; Requirements | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.311/32311-i00.zip | The purpose of the present document is to define a common service supported by all IRPs such as AlarmIRP. The present document is the "Requirements" part. It defines the requirements that shall be fulfilled by all IRPs, such as AlarmIRP, supporting this common service.
With this common service supported by all IRPs, an IRPManager shall be able to retrieve the profile of operations and notifications supported by a given IRP which is name-contained by an IRPAgent. An IRPManager shall also be able to retrieve the IRPVersions supported by the given IRP. |
32.312 | Telecommunication management; Generic Integration Reference Point (IRP) management; Information Service (IS) | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.312/32312-i00.zip | The purpose of the present document is to define a common service supported by all IRPs such as AlarmIRP. The present document is the "Information Service" part. It defines, for the purpose of supporting the common service, the information observable and controllable by management system's client (i.e. IRPManager) via the Itf-N.
It also specifies the semantics of and the interactions used to carry this information.
With this common service supported by all IRPs, an IRPManager can retrieve the profile of operations and notifications supported by a given IRP name-contained by an IRPAgent. An IRPManager can also retrieve the IRPVersions supported by a given IRP. |
32.316 | Telecommunication management; Generic Integration Reference Point (IRP) management; Solution Set (SS) definitions | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.316/32316-i00.zip | The present document provides the Solution Set definitions for Generic Integration Reference Point (IRP) management, whose capabilities are specified in 3GPP TS 32.312 [1], the Generic IRP management: Information Service.
This Solution Set Definition specification is related to 3GPP TS 32.312 V14.0.X. |
32.321 | Telecommunication management; Test management Integration Reference Point (IRP); Requirements | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.321/32321-i00.zip | The present document describes, in addition to the requirements defined in [1] and [2], the requirements for the Test Management IRP. |
32.322 | Telecommunication management; Test management Integration Reference Point (IRP); Information Service (IS) | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.322/32322-i00.zip | The present document defines the IS part of the Test Management IRP, which describes the semantics of the information and the interactions visible across Itf-N in a protocol independent way. The information is specified by means of information object classes and the interactions by means of operations and notifications. The present document does not specify the syntax (encoding) of the information. |
32.326 | Telecommunication management; Test management Integration Reference Point (IRP): Solution Set (SS) definitions | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.326/32326-i00.zip | The present document contains the Solution Sets for the IRP whose semantics is specified in Test management IRP IS (3GPP TS 32.322 [5]).
This Solution Set specification is related to 3GPP TS 32.322 V14.0.X [5]. |
32.331 | Telecommunication management; Notification Log (NL) Integration Reference Point (IRP); Requirements | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.331/32331-i00.zip | The present document specifies overall requirements for Notification Log Management over Itf-N.
Clause 4 provides the Notification Log Management concept for the manipulation of Notification Logs and the retrieval of notifications selected for logging.
Clause 5 of the present document defines the functional requirements for the Notification Log IRP, for the purpose of Notification Log Management, as seen from a Network Manager (NM) though Itf-N. The Itf-N is fully standardized so as to connect systems of any vendor to an NM via this interface. |
32.332 | Telecommunication management; Notification Log (NL) Integration Reference Point (IRP); Information Service (IS) | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.332/32332-i00.zip | The present document specifies the Information Service for the Notification Log Integration Reference Point (NLIRP) as it applies to Itf-N.
This IRP IS defines the semantics of operations (and their parameters) visible across the Itf-N in a protocol and technology neutral way. It does not define the syntax or encoding of the operations and their parameters. |
32.336 | Telecommunication management; Notification Log (NL) Integration Reference Point (IRP): Solution Set (SS) definitions | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.336/32336-i00.zip | The present document specifies the Solution Sets for the IRP whose semantics is specified in Notification Log (NL) IRP IS (3GPP TS 32.332 [5]).
This Solution Set specification is related to 3GPP TS 32.332 V14.0.X. |
32.341 | Telecommunication management; File Transfer (FT) Integration Reference Point (IRP); Requirements | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.341/32341-i00.zip | The present document specifies the overall requirements for the File Transfer Integration Reference Point (FT IRP) as it applies to the Itf-N. |
32.342 | Telecommunication management; File Transfer (FT) Integration Reference Point (IRP); Information Service (IS) | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.342/32342-i00.zip | The present document specifies the Information Service for the File Transfer Integration Reference Point (FileTransferIRP) as it applies to the Itf-N.
The present document defines the semantics of operations (and their parameters) visible across the Itf-N in a protocol and technology neutral way. It does not define the syntax or encoding of the operations and their parameters. |
32.346 | Telecommunication management; File Transfer (FT) Integration Reference Point (IRP): Solution Set (SS) definitions | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.346/32346-i00.zip | The present document contains the Solution Sets for the IRP whose semantics are specified in File Transfer IRP: Information Service (3GPP TS 32.342 [15]).
This Solution Set specification is related to 3GPP TS 32.342 V14.0.X [15]. |
32.351 | Telecommunication management; Communication Surveillance (CS) Integration Reference Point (IRP); Requirements | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.351/32351-i00.zip | The present document describes the requirements of the Communication Surveillance IRP (CSIRP). |
32.352 | Telecommunication management; Communication Surveillance (CS) Integration Reference Point (IRP); Information Service (IS) | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.352/32352-i00.zip | The present document defines the Information Service (IS) part of the Communication Surveillance IRP (CSIRP).
It describes the semantics of the information and the interactions visible across Itf-N in a protocol independent way.
The information is specified by means of Information Object Classes (IOCs) and the interactions by means of operations and notifications. The present document does not specify the syntax (encoding) of the information. |
32.356 | Telecommunication management; Communication Surveillance (CS) Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.356/32356-i00.zip | The present document specifies the Solution Set definitions for the IRP whose semantics is specified in TS 32.352 [6] Communication Surveillance IRP: Information Service..
This Solution Set definitions specification is related to 3GPP TS 32.352 V14.0.X [6]. |
32.361 | Telecommunication management; Entry Point (EP) Integration Reference Point (IRP); Requirements | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.361/32361-i00.zip | The present document describes the requirements of the EPIRP. |
32.362 | Telecommunication management; Entry Point (EP) Integration Reference Point (IRP); Information Service (IS) | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.362/32362-i00.zip | The present document defines the Information Service (IS) part of the Entry Point IRP (EPIRP).
It describes the semantics of the information and the interactions visible across Itf-N in a protocol independent way.
The information is specified by means of Information Object Classes (IOCs) and SupportIOCs, and the interactions by means of operations and notifications. The present document does not specify the syntax (encoding) of the information. |
32.366 | Telecommunication management; Entry Point (EP) Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.366/32366-i00.zip | The present document specifies the Solution Set definitions for the IRP whose semantics are specified in the Entry Point IRP: Information Service (3GPP TS 32.362 [6]).
This Solution Set definitions specification is related to 3GPP TS 32.362 V14.0.X [6]. |
32.371 | Telecommunication management; Security Management concept and requirements | TS | 18.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.371/32371-i10.zip | The present document defines, in addition to the requirements defined in 3GPP TS 32.101 [1] and 3GPP TS 32.102 [2], the requirements for Security Management IRP.
The purpose of the present document is to specify the necessary security features, services and functions to protect the network management data, including Requests, Responses, Notifications and Files, exchanged across the Itf‑N.
Telecommunication network security can be breached by weaknesses in operational procedures, physical installations, communication links, computational processes and data storage. Of concern here in the present document is the security problems resulting from the weaknesses inherent in the communication technologies (i.e., the 3GPP‑defined Interface IRPs and their supporting protocol stacks) deployed across the Itf-N.
Appropriate level of security for a telecommunication network is essential. Secured access to the network management applications, and network management data, is essential. The 3GPP-defined Interface IRPs (and their supporting protocol stacks), deployed across the Itf-N, are used for such access, and therefore, their security is considered essential.
Many network management security standards exist. However, there is no recommendation on how to apply them in the Itf-N context. Their deployment across the Itf-N is left to operators. The present document and the corresponding solutions identify and recommend security standards in the Itf-N context.
The business case for secured Itf-N is complex as it does not relate to the functions of the Interface IRPs (the functions are constant) but rather, it relates to variants such as the cost of recovering from security breaks, the probability of security incidents and the cost of implementing Security Management, all of which differs depending on specific deployment scenarios.
The present document describes the security functions for a 3G network in terms of Security Domains (subclause 4.1). Clause 5 defines the Itf-N Security Management scope in terms of its context (subclause 5.1) and the possible threats that can occur there are defined in clause 6. Clause 7 specifies the Itf‑N security Requirements. |
32.372 | Telecommunication management; Security services for Integration Reference Point (IRP); Information Service (IS) | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.372/32372-i00.zip | The purpose of the present document is to specify the necessary security features, services and functions to protect the network management data, including Requests, Responses, Notifications and Files, exchanged across the Itf‑N.
The present document specifies the Security Service for IRP Information Service.
This Security Service for IRP IS defines the semantics of management information visible across the Itf-N in a protocol and technology neutral way. It does not define the syntax or encoding of the operations and their parameters.
This Information Service specification is related to 3GPP TS 32.371 [6]. |
32.376 | Telecommunication management; Security services for Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.376/32376-i00.zip | The present document specifies the Solution Set for the IRP whose semantics is specified in 3GPP TS 32.372 [5] Security Service for IRP Information Service.
This Solution Set specification is related to 3GPP TS 32.372 V14.0.X [5].
Note that within the present document there are several alternate solutions. Specific choices will to be made to counter identified security threats, and to consider performance and cost criteria, i.e. an implementation is not expected to have to support every option for every deployment. |
32.381 | Telecommunication management; Partial Suspension of Itf-N Integration Reference Point (IRP); Requirements | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.381/32381-i00.zip | The purpose of Partial Suspension of Itf-N IRP is to define an interface through which an IRPManager can suspend the forwarding of notifications via Itf-N which were generated in parts of the managed systems.
The present document contains the Requirements of Partial Suspension of Itf-N IRP. It defines, for the purpose of generally suspending the forwarding of notifications, the basic requirements to be fulfilled on Itf-N. |
32.382 | Telecommunication management; Partial Suspension of Itf-N Integration Reference Point (IRP); Information Service (IS) | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.382/32382-i00.zip | The purpose of Partial Suspension of Itf-N IRP is to define an interface through which an IRPManager can suspend the forwarding of notifications via Itf-N which were generated in parts of the managed systems.
The present document is the Information Service of Partial Suspension of Itf-N IRP. It defines, for the purpose of suspending generally the forwarding of notifications, the information observable and controlled by management system's client and it also specifies the semantics of the interactions used to carry this information. |
32.386 | Telecommunication management; Partial Suspension of Itf-N Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.386/32386-i00.zip | The present document specifies the Solution Set definitions for the IRP whose semantics is specified Partial Suspension of Itf-N IRP IS (3GPP TS 32.382 [5]).
This Solution Set specification is related to 3GPP TS 32.382 V14.0.X [5]. |
32.391 | Telecommunication management; Delta synchronization Integration Reference Point (IRP); Requirements | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.391/32391-i00.zip | The purpose of Delta Synchronization IRP is to define an interface through which an IRPManager can request only those data which changed (i.e. changed, were created or deleted) from a synchronization point onwards.
The present document contains the Requirements of Delta Synchronization IRP. It defines, for the purpose of Delta Synchronization, the basic requirements to be fulfilled on Itf-N. |
32.392 | Telecommunication management; Delta synchronization Integration Reference Point (IRP); Information Service (IS) | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.392/32392-i00.zip | The purpose of Delta Synchronization IRP is to define an interface through which an IRPManager can request only those data which changed (i.e. changed, were created or deleted) from a synchronization point onwards.
The present document is the Information Service of Delta Synchronization IRP. It defines, for the purpose of Delta Synchronization, the information observable and controlled by management system's client and it also specifies the semantics of the interactions used to carry this information. |
32.396 | Telecommunication management; Delta synchronization Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.396/32396-i00.zip | The present document specifies the Solution Set definitions for the IRP whose semantics is specified in Delta Synchronization IRP IS (3GPP TS 32.392 [5]).
This Solution Set specification is related to 3GPP TS 32.392 V14.0.X [5]. |
32.401 | Telecommunication management;Performance Management (PM);Concept and requirements | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.401/32401-i00.zip | |
32.404 | Telecommunication management; Performance Management (PM); Performance measurements; Definitions and template | TS | 18.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.404/32404-i30.zip | The present document describes definitions and template related to the measurements for UMTS, GSM, LTE and 5G networks (and combined such networks).
TS 32.401 [1] describes Performance Management concepts and requirements.
The present document is valid for all measurement types provided by an implementation of a UMTS, GSM, LTE or 5G network (and combined such networks).
Vendor specific measurements types are not covered. Instead, these could be applied according to manufacturer's documentation.
Measurements related to "external" technologies (such as ATM or IP) as described by "external" standards bodies
(e.g. ITU-T or IETF) shall only be referenced within this specification, wherever there is a need identified for the existence of such a reference.
The definition of the standard measurements is intended to result in comparability of measurement data produced in a multi-vendor network, for those measurement types that can be standardised across all vendors' implementations. |
32.405 | Telecommunication management; Performance Management (PM); Performance measurements; Universal Terrestrial Radio Access Network (UTRAN) | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.405/32405-i00.zip | The present document describes the measurements for Universal Terrestrial Radio Access Network (UTRAN).
TS 32.401 [1] describes Performance Management concepts and requirements.
The present document is valid for all measurement types provided by an implementation of a UTRAN. Only measurement types that are specific to UTRAN are defined within the present documents.
Vendor specific measurement types used inUTRAN are not covered. Instead, these could be applied according to manufacturer's documentation.
Measurements related to "external" technologies (such as ATM or IP) as described by "external" standards bodies (e.g. ITU-T or IETF) shall only be referenced within this specification, wherever there is a need identified for the existence of such a reference.
The definition of the standard measurements is intended to result in comparability of measurement data produced in a multi-vendor network, for those measurement types that can be standardised across all vendors' implementations.
The structure of the present document is as follows:
- Header 1: Network Element (e.g. RNC related measurements);
- Header 2: Measurement function (e.g. soft handover measurements);
- Header 3: Measurements. |
32.406 | Telecommunication management; Performance Management (PM); Performance measurements; Core Network (CN) Packet Switched (PS) domain | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.406/32406-i00.zip | The present document describes the measurements for Core Network (CN) Packet Switched (PS) domain of UMTS or combined UMTS/GSM network.
TS 32.401 [1] describes Performance Management concepts or requirements.
The present document is valid for all measurement types provided by an implementation of a CN PS domain of UMTS network or combined UMTS/GSM network.
Only measurement types that are specific to CN PS domain of UMTS or combined UMTS/GSM network are defined within the present documents.
Vendor specific measurement types used in CN PS domain of UMTS or combined UMTS/GSM network are not covered. Instead, these could be applied according to manufacturer's documentation.
Measurements related to "external" technologies (such as ATM or IP) as described by "external" standards bodies (e.g. ITU-T or IETF) shall only be referenced within this specification, wherever there is a need identified for the existence of such a reference.
The definition of the standard measurements is intended to result in comparability of measurement data produced in a multi-vendor network, for those measurement types that can be standardised across all vendors' implementations.
The structure of the present document is as follows:
- Header 1: Network Element (e.g. RNC related measurements);
- Header 2: Measurement function (e.g. soft handover measurements);
- Header 3: Measurements. |
32.407 | Telecommunication management; Performance Management (PM); Performance measurements; Core Network (CN) Circuit Switched (CS) domain; UMTS and combined UMTS/GSM | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.407/32407-i00.zip | The present document describes the CN CS measurements for UMTS and combined UMTS/GSM.
3GPP TS 32.401 [2] describes Performance Management concepts and requirements.
The present document is valid for all measurement types provided by an implementation of a UMTS network and combined UMTS/GSM network. These may be measurement types defined within the present document, measurements defined within other standards bodies, or vendor specific measurement types.
Only measurement types that are specific to CN CS UMTS or combined UMTS/GSM networks are defined within the present documents. I.e. vendor specific measurement types used in UMTS and combined UMTS/GSM networks. Some ATM or IP measurements defined here are only used for load carrying. The definition of the standard measurements is intended to result in comparability of measurement data produced in a multi-vendor network, for those measurement types that can be standardised across all vendors' implementations.
The structure of the present document is as follows:
- Header 1: Network Element (e.g. MSCServer related measurements);
- Header 2: Measurement function (e.g. handover measurements);
- Header 3: Measurements. |
32.408 | Telecommunication management; Performance Management (PM); Performance measurements; Teleservice | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.408/32408-i00.zip | The present document describes the measurements for UMTS and combined UMTS/GSM.
TS 32.401 [1] describes Performance Management concepts and requirements.
The present document is valid for all measurement types provided by an implementation of a UMTS network and combined UMTS/GSM network.
Only measurement types that are specific to UMTS or combined UMTS/GSM networks are defined within the present documents. Vendor specific measurement types used in UMTS and combined UMTS/GSM networks are not covered. Instead, these could be applied according to manufacturer's documentation.
Measurements related to "external" technologies (such as ATM or IP) as described by "external" standards bodies (e.g. ITU-T or IETF) shall only be referenced within this specification, wherever there is a need identified for the existence of such a reference.
The definition of the standard measurements is intended to result in comparability of measurement data produced in a multi-vendor network, for those measurement types that can be standardised across all vendors' implementations.
The structure of the present document is as follows:
- Header 1: Network Element (e.g. RNC related measurements);
- Header 2: Measurement function (e.g. soft handover measurements);
- Header 3: Measurements. |
32.409 | Telecommunication management; Performance Management (PM); Performance measurements; IP Multimedia Subsystem (IMS) | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.409/32409-i00.zip | The present document describes the measurements of IMS.
3GPP TS 32.401 [5] describes Performance Management concepts and requirements.
The present document is valid for all measurement types provided by an implementation of an IMS network. These may be measurement types defined within the present document, measurements defined within other standards bodies, or vendor specific measurement types.
Only measurement types that are specific to IMS network are defined within the present documents. I.e. vendor specific measurement types and measurements related to "external" technologies used in IMS network, such as ATM or IP, are not covered. Instead, these could be applied as described by the other, "external" standards bodies (e.g. ITU-T or IETF) or according to manufacturer's documentation.
The definition of the standard measurements is intended to result in comparability of measurement data produced in a multi-vendor network, for those measurement types that can be standardised across all vendors' implementations.
The structure of the present document is as follows:
- Header 1: Network Element (e.g. measurements related to CSCF);
- Header 2: Measurement function (e.g. Registration related measurements);
- Header 3: Measurements. |
32.410 | Telecommunication management; Key Performance Indicators (KPI) for UMTS and GSM | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.410/32410-i00.zip | The present document specifies Key Performance Indicators (KPIs) for GSM, UMTS, etc.
KPI definitions include high level KPIs that are:
a) common across GSM and UMTS networks; and
b) specific to network techniques such as GSM and UMTS networks. |
32.411 | Telecommunication management; Performance Management (PM) Integration Reference Point (IRP): Requirements | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.411/32411-i00.zip | The present document specifies the overall requirements for the Performance Management Integration Reference Point (PMIRP) as it applies to the Network Elements (NE), Element Manager (EM) and Network Manager (NM). |
32.412 | Telecommunication management; Performance Management (PM) Integration Reference Point (IRP): Information Service (IS) | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.412/32412-i00.zip | The present document specifies the Information Service for the Performance Management Integration Reference Point (PM IRP) as it applies to the Itf-N.
This IRP IS defines the semantics of operations (and their parameters) visible across the Itf-N in a protocol and technology neutral way. It does not define the syntax or encoding of the operations and their parameters.
This IRP IS is aligned with ITU-T M.3704 [16] in terms of the definitions of operations for Performance management. |
32.416 | Telecommunication management; Performance Management (PM) Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.416/32416-i00.zip | The present document specifies the Solution Set definitions for the IRP whose semantics is specified in PM (Performance Management) IRP: Information Service 3GPP TS 32.412 [7].
This Solution Set definitions specification is related to 3GPP TS 32.412 V14.0.X. |
32.421 | Telecommunication management; Subscriber and equipment trace; Trace concepts and requirements | TS | 18.4.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.421/32421-i40.zip | |
32.422 | Telecommunication management; Subscriber and equipment trace; Trace control and configuration management | TS | 18.6.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.422/32422-i60.zip | |
32.423 | Telecommunication management; Subscriber and equipment trace; Trace data definition and management | TS | 18.6.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.423/32423-i60.zip | |
32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.425/32425-i00.zip | The present document describes the measurements for E-UTRAN.
TS 32.401 [5] describes Performance Management concepts and requirements.
The present document is valid for all measurement types provided by an implementation of an E-UTRAN.
Only measurement types that are specific to E-UTRAN are defined within the present documents. Vendor specific measurement types used in E-UTRAN are not covered. Instead, these could be applied according to manufacturer's documentation.
Measurements related to "external" technologies (such as ATM or IP) as described by "external" standards bodies (e.g. ITU-T or IETF) shall only be referenced within this specification, wherever there is a need identified for the existence of such a reference.
The definition of the standard measurements is intended to result in comparability of measurement data produced in a multi-vendor network, for those measurement types that can be standardised across all vendors' implementations.
The structure of the present document is as follows:
- Header 1: Network Element (e.g. measurements related to eNodeB);
- Header 2: Measurement function (e.g. RRC connection setup related measurements);
- Header 3: Measurements. |
32.426 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Packet Core (EPC) network | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.426/32426-i00.zip | The present document describes the measurements for EPC and combined EPC/UMTS/GSM.
TS 32.401 [1] describes Performance Management concepts and requirements.
The present document is valid for all measurement types provided by an implementation of an EPC network and combined EPC/UMTS/GSM network. Only measurement types that are specific to EPC or combined EPC/UMTS/GSM networks are defined within the present documents.
Vendor specific measurement types used in EPC and combined EPC/UMTS/GSM networks are not covered. Instead, these could be applied according to manufacturer's documentation.
Measurements related to "external" technologies (such as IP) as described by "external" standards bodies (e.g. IETF) shall only be referenced within this specification, wherever there is a need identified for the existence of such a reference.
The definition of the standard measurements is intended to result in comparability of measurement data produced in a multi-vendor network, for those measurement types that can be standardised across all vendors' implementations.
The structure of the present document is as follows:
- Header 1: Network Element (e.g. MME related measurements);
- Header 2: Measurement function;
- Header 3: Measurements. |
32.432 | Telecommunication management; Performance measurement: File format definition | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.432/32432-i00.zip | The present document describes the general semantics of performance measurement result and collection. It defines the report file format, report file conventions and the file transfer procedure. Clause 4 specifies the file format for the bulk transfer of performance measurement results to the NM, while clause 5 discusses the file transfer procedure utilised on that interface.
The present document does not give the definition of any specific file format – such as XML and ASN.1, which will be given in Performance Measurement eXtensible Markup Language (XML) File Format Definition 3GPP TS 32.435 and Performance Measurement Abstract Syntax Notation 1 (ASN.1) File Format Definition 3GPP TS 32.436. |
32.435 | Telecommunication management; Performance measurement; eXtensible Markup Language (XML) file format definition | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.435/32435-i00.zip | The present document describes the XML file format of performance measurement results whose semantics is defined in 3GPP TS 32.432 [5].
This specification is related to 3GPP TS 32.432 V10.2.X. |
32.436 | Telecommunication management; Performance measurement: Abstract Syntax Notation 1 (ASN.1) file format definition | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.436/32436-i00.zip | The present document defines the ASN.1 file format definition for performance measurement results collection whose semantics is defined in 3GPP TS 32.432 [5]. |
32.441 | Telecommunication management; Trace Management Integration Reference Point (IRP); Requirements | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.441/32441-i00.zip | The present document specifies the overall requirements for the Trace Management Integration Reference Point (TraceIRP) as it applies to Itf-N.
The Trace IRP supports the operations that are required for the Subscriber and Equipment trace, the Service Level Trace , the Cell Traffic Trace, Minimization of Drive Tests (MDT) functionalities across UMTS networks or EPS networks and Radio Link Failure (RLF) reporting functionalities across EPS networks GSM Trace is outside of the scope of this specification..
All functions (trace, MDT etc.) specified in this specification supports Network Sharing, with the following condition:
1) It is accepted that the recorded information from the shared network can be sent to any of the operators sharing the network, taking user consent into account. Operators must also agree on sharing the information, but how that agreement is done is outside the scope of this specification. The mapping of TCE IP addresses and TCE addresses must be coordinated among the operators that shares the network. How that coordination is done is outside the scope of this specification..
2) For signalling based activation, the operators that share a network must coordinate the TCE IP addresses and the TCE address mapping must be coordinated. How that coordination is done, is outside the scope of this specification.
3) The 3GPP Managment reference model, 3GPP TS 32.101 [2] is followed.
Editor's note: The requirements for Service Level Tracing are FFS. |
32.442 | Telecommunication management; Trace Management Integration Reference Point (IRP); Information Service (IS) | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.442/32442-i00.zip | The present document describes the mechanism used for control and configuration of the Trace, Minimization of Drive Test (MDT) and Radio Link Failure (RLF) reporting functionality through Itf-N. This specification is applicable to UMTS networks and EPS networks. GSM Trace is outside of the scope of this specification.
The conditions for supporting Network Sharing are stated in 3GPP TS 32.441 [13]. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.