id stringlengths 5 12 | title stringlengths 8 250 | type stringclasses 2
values | version stringclasses 560
values | working_group stringclasses 30
values | url stringlengths 67 81 | scope stringlengths 0 65.7k |
|---|---|---|---|---|---|---|
32.526 | Telecommunication management; Self-Organizing Networks (SON); Policy Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 11.7.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.526/32526-b70.zip | The present document specifies the Solution Set definitions for the IRP whose semantics is specified in 3GPP TS 32.522 [4] SON Policy Network Resource Model IRP: Information Service (IS).
This Solution Set definitions specification is related to 3GPP TS 32.522 V11.7.X [4]. |
32.455 | Telecommunication management; Key Performance Indicators (KPI) for the Evolved Packet Core (EPC); Definitions | TS | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.455/32455-b00.zip | |
32.532 | Telecommunication management; Software management (SwM); Integration Reference Point (IRP); Information Service (IS) | TS | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.532/32532-b00.zip | |
32.501 | Telecommunication management; Self-configuration of network elements; Concepts and requirements | TS | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.501/32501-b00.zip | |
32.536 | Telecommunication management; Software management Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.536/32536-b00.zip | |
32.541 | Telecommunication management; Self-Organizing Networks (SON); Self-healing concepts and requirements | TS | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.541/32541-b00.zip | |
32.551 | Telecommunication management; Energy Saving Management (ESM); Concepts and requirements | TS | 11.3.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.551/32551-b31.zip | |
32.571 | Telecommunication management; Home Node B (HNB) and Home eNode B (HeNB) management; Type 2 interface concepts and requirements | TS | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.571/32571-b00.zip | |
32.572 | Telecommunication management; Home Node B (HNB) and Home eNode B (HeNB) management; Type 2 interface models and mapping functions | TS | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.572/32572-b00.zip | |
32.581 | Telecommunication management; Home Node B (HNB) Operations, Administration, Maintenance and Provisioning (OAM&P); Concepts and requirements for Type 1 interface HNB to HNB Management System (HMS) | TS | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.581/32581-b00.zip | |
32.582 | Telecommunication management; Home Node B (HNB) Operations, Administration, Maintenance and Provisioning (OAM&P); Information model for Type 1 interface HNB to HNB Management System (HMS) | TS | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.582/32582-b00.zip | |
32.583 | Telecommunication management; Home Node B (HNB) Operations, Administration, Maintenance and Provisioning (OAM&P); Procedure flows for Type 1 interface HNB to HNB Management System (HMS) | TS | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.583/32583-b00.zip | |
32.584 | Telecommunication management; Home Node B (HNB) Operations, Administration, Maintenance and Provisioning (OAM&P); XML definitions for Type 1 interface HNB to HNB Management System (HMS) | TS | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.584/32584-b00.zip | |
32.591 | Telecommunication management; Home enhanced Node B (HeNB) Operations, Administration, Maintenance and Provisioning (OAM&P); Concepts and requirements for Type 1 interface HeNB to HeNB Management System (HeMS) | TS | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.591/32591-b00.zip | |
32.592 | Telecommunication management; Home enhanced Node B (HeNB) Operations, Administration, Maintenance and Provisioning (OAM&P); Information model for Type 1 interface HeNB to HeNB Management System (HeMS) | TS | 11.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.592/32592-b30.zip | |
32.593 | Telecommunication management; Home enhanced Node B (HeNB) Operations, Administration, Maintenance and Provisioning (OAM&P); Procedure flows for Type 1 interface HeNB to HeNB Management System (HeMS) | TS | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.593/32593-b00.zip | |
32.594 | Telecommunication management; Home enhanced Node B (HeNB) Operations, Administration, Maintenance and Provisioning (OAM&P); XML definitions for Type 1 interface HeNB to HeNB Management System (HeMS) | TS | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.594/32594-b00.zip | |
32.600 | Telecommunication management; Configuration Management (CM); Concept and high-level requirements | TS | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.600/32600-b00.zip | |
32.601 | Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP); Requirements | TS | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.601/32601-b00.zip | |
32.602 | Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP); Information Service (IS) | TS | 11.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.602/32602-b20.zip | |
32.446 | Telecommunication management; Trace Management Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 11.5.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.446/32446-b50.zip | |
32.531 | Telecommunication management; Software management (SwM); Concepts and Integration Reference Point (IRP) Requirements | TS | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.531/32531-b00.zip | |
32.502 | Telecommunication management; Self-configuration of network elements Integration Reference Point (IRP); Information Service (IS) | TS | 11.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.502/32502-b10.zip | |
32.616 | Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 11.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.616/32616-b10.zip | |
32.612 | Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Information Service (IS) | TS | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.612/32612-b00.zip | |
32.621 | Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP); Requirements | TS | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.621/32621-b00.zip | The present document defines , in addition to the requirements defined in [1], [2] and [3], the requirements for the present IRP: Generic Network Resources IRP. |
32.622 | Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP); Network Resource Model (NRM) | TS | 11.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.622/32622-b10.zip | The present document specifies the Generic network resource information that can be communicated between an IRPAgent and one or several IRPManagers for network management purposes.
This document specifies the semantics of information object class attributes and relations visible across the reference point in a protocol and technology neutral way. It does not define their syntax and encoding.
The document specifies the information in a generic manner in that the information specified is a base from which all other NRM IRP ISs such as GERAN NRM IRP IS [20] can inherit or have associations with. |
32.611 | Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Requirements | TS | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.611/32611-b00.zip | |
32.631 | Telecommunication management; Configuration Management (CM); Core network resources Integration Reference Point (IRP); Requirements | TS | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.631/32631-b00.zip | The present document defines, in addition to the requirements defined in [1], [2] and [3], the requirements for the present IRP: Core Network Resources IRP. |
32.626 | Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 11.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.626/32626-b20.zip | The TS 32.62x-series (Generic Network Resources IRP) define an Integration Reference Point (IRP) through which an "IRPAgent" (typically an Element Manager or Network Element) can communicate Network Management related information to one or several "IRPManagers" (typically Network Managers).
This TS-family specifies a generic Network Resource Model, NRM (also referred to as a Management Information Model - MIM) with definitions of Information Object Classes (IOCs) and Managed Object Classes (MOCs).
The present document specifies the Solution Sets for the Generic NRM IRP.
These Solution Set specifications are related to 3GPP TS 32.622 V11. 1.X [4]. |
32.636 | Telecommunication management; Configuration Management (CM); Core network resources Integration Reference Point (IRP); Solution Set (SS) Definitions | TS | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.636/32636-b00.zip | The purpose of the present document is to define the mapping of the IRP information model (see TS 32.632 [3]) to the protocol specific details necessary for implementation of this IRP in a specific solution set environment.
This Solution Set specification is related to 3GPP TS 32.632 V11.0.X. |
32.641 | Telecommunication management; Configuration Management (CM); UTRAN network resources Integration Reference Point (IRP); Requirements | TS | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.641/32641-b00.zip | The present document defines, in addition to the requirements defined in [1], [2] and [3], the requirements for the present IRP: UTRAN Network Resources IRP. |
32.642 | Telecommunication management; Configuration Management (CM); UTRAN network resources Integration Reference Point (IRP); Network Resource Model (NRM) | TS | 11.5.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.642/32642-b50.zip | The present document specifies the UTRAN network resource information that can be communicated between an IRPAgent and one or several IRPManagers for network management purposes.
The present document specifies the semantics and behaviour of information object class attributes and relations visible across the reference point in a protocol and technology neutral way. It does not define their syntax and encoding. |
32.646 | Telecommunication management; Configuration Management (CM); UTRAN network resources Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 11.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.646/32646-b20.zip | The present document specifies the Solution Sets for the UTRAN NRM IRP.
This Solution Set specification is related to 3GPP TS 32.642 V11.4.X [4]. |
32.651 | Telecommunication management; Configuration Management (CM); GERAN network resources Integration Reference Point (IRP); Requirements | TS | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.651/32651-b00.zip | The present document defines , in addition to the requirements defined in [1], [2] and [3], the requirements for the present IRP: GERAN Network Resources IRP. |
32.652 | Telecommunication management; Configuration Management (CM); GERAN network resources Integration Reference Point (IRP); Network Resource Model (NRM) | TS | 11.2.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.652/32652-b21.zip | The present document specifies the GERAN network resource information that can be communicated between an IRPAgent and one or several IRPManagers for network management purposes.
This document specifies the semantics and behaviour of information object class attributes and relations visible across the reference point in a protocol and technology neutral way. It does not define their syntax and encoding. |
32.656 | Telecommunication management; Configuration Management (CM); GERAN network resources Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 11.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.656/32656-b20.zip | The present document specifies the Solution Sets for the GERAN NRM IRP.
This Solution Set specification is related to 3GPP TS 32.652 V11.2.X [4]. |
32.661 | Telecommunication management; Configuration Management (CM); Kernel CM Requirements | TS | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.661/32661-b00.zip | |
32.662 | Telecommunication management; Configuration Management (CM); Kernel CM Information Service (IS) | TS | 11.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.662/32662-b10.zip | |
32.666 | Telecommunication management; Configuration Management (CM); Kernel CM Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.666/32666-b00.zip | |
32.671 | Telecommunication management; Configuration Management (CM); State Management Integration Reference Point (IRP); Requirements | TS | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.671/32671-b00.zip | The present document defines, in addition to the requirements defined in 3GPP TS 32.101 [1], 3GPP TS 32.102 [2] and 3GPP TS 32.600 [3], the requirements for the present IRP: State Management. |
32.672 | Telecommunication management; Configuration Management (CM); State Management Integration Reference Point (IRP); Information Service (IS) | TS | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.672/32672-b00.zip | The present document defines the Information Service (IS) part of the State Management IRP. It specifies the semantics of the network resource state and status information visible across the Itf-N. It also specifies the interaction required for the management of the state and status information.
The state and status attributes specified in this document shall be used, where applicable, as attributes in Information Object Class (IOC) definitions of other 3GPP IRPs. When used by the IOC definition, the semantics of the state and status attributes can be qualified and enhanced if deemed necessary. |
32.676 | Telecommunication management; Configuration Management (CM); State Management Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.676/32676-b00.zip | The present document specifies the Solution Set (SS) definitions for the IRP whose semantics is specified in State Management IRP: Information Service (IS) (3GPP TS 32.672 [1]).
This Solution Set definitions specification is related to 3GPP TS 32.672 V11.0.X. |
32.690 | Telecommunication management; Inventory Management (IM); Requirements | TS | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.690/32690-b00.zip | |
32.691 | Telecommunication management; Inventory Management (IM) network resources Integration Reference Point (IRP): Requirements | TS | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.691/32691-b00.zip | The present document defines , in addition to the requirements defined in 3GPP TS 32.101 [1], 3GPP TS 32.102 [2] and 3GPP TS 32.600 [3], the requirements for the present IRP: Inventory Management network resources IRP. |
32.692 | Telecommunication management; Inventory Management (IM) network resources Integration Reference Point (IRP); Network Resource Model (NRM) | TS | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.692/32692-b00.zip | The present document defines an Integration Reference Point (IRP) through which an 'IRPAgent' (typically an Element Manager or Network Element) can communicate Network Management related information to one or several 'IRPManagers' (typically Network Managers).
The present document specifies an Inventory Management Network Resource Model, NRM (also referred to as a Management Information Model - MIM) with definitions of Information Object Classes. |
32.696 | Telecommunication management; Inventory Management (IM) Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 11.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.696/32696-b10.zip | The present document provides the NRM-specific part related to the Inventory Management NRM IRP IS in 3GPP TS 32.692 [1] of solution set definitions.
This Solution Set definitions specification is related to 3GPP TS 32.692 V110..X. |
32.711 | Telecommunication management; Configuration Management (CM); Transport Network (TN) interface Network Resource Model (NRM) Integration Reference Point (IRP); Requirements | TS | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.711/32711-b00.zip | The present document defines , in addition to the requirements defined in [1], [2] and [3], the requirements for the present IRP: Transport Network (TN) interface Network Resource Model (NRM) Integration Reference Point. |
32.632 | Telecommunication management; Configuration Management (CM); Core Network Resources Integration Reference Point (IRP); Network Resource Model (NRM) | TS | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.632/32632-b00.zip | The present document is part of an Integration Reference Point (IRP) named "Core Network Resources IRP", through which an 'IRPAgent' (typically an Element Manager or Network Element) can communicate Configuration Management information to one or several 'IRPManagers' (typically Network Managers) concerning CN resources.
The present document specifies the protocol neutral Core Network Resources IRP: Network Resource Model. It reuses relevant parts of the generic NRM in 3GPP TS 32.622 [16], either by direct reuse or sub-classing, and in addition to that defines CN specific Information Object Classes.
Finally, in order to access the information defined by this NRM, an Interface IRP is needed, such as the Basic CM IRP 3GPP TS 32.60x [17]. However, which Interface IRP that is applicable is outside the scope of the present document. |
32.721 | Telecommunication management; Configuration Management (CM); Repeater network resources Integration Reference Point (IRP); Requirements | TS | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.721/32721-b00.zip | The present document defines, in addition to the requirements defined in 3GPP TS 32.101 [1], 3GPP TS 32.102 [2] and 3GPP TS 32.600 [3], the requirements for the present Repeater network resources IRP. |
32.606 | Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.606/32606-b00.zip | |
32.712 | Telecommunication management; Configuration Management (CM); Transport Network (TN) interface Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) | TS | 11.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.712/32712-b10.zip | The present document is part of an Integration Reference Point (IRP) named "Transport Network (TN) Interface Network Resource Model (NRM) IRP ", through which an "IRPAgent" (typically an Element Manager or Network Element) can communicate Configuration Management information to one or several "IRPManagers" (typically Network Managers) concerning Transport resources. The "Transport Network (TN) Interface Network Resource Model (NRM) IRP" comprises a set of specifications defining Requirements, a protocol neutral Network Resource Model (NRM) and corresponding Solution Set(s).
The present document:
1. specifies the protocol neutral Transport Network Interface Resources IRP: Network Resource Model. It reuses relevant parts of the generic NRM in TS 32.622 [6], either by direct reuse or sub-classing, and in addition to that defines Transport specific Managed Object Classes.
The Configuration Management (CM) area is very large. The intention is to split the specification of the related interfaces in several IRPs - as described in the Introduction clause above. An important aspect of such a split is that the Network Resource Models (NRMs) defined in different IRPs containing NRMs are consistent, and that NRMs supported by an IRPAgent implementation can be accessed as one coherent model through one IRP Information Service.
In order to access the information defined by this NRM, an IRP Information Service (IS) is needed, such as the Basic CM IRP: IS (TS 32.602 [7]) or the Bulk CM IRP: IS (TS 32.612 [8]). However, which Information Service that is applicable is outside the scope of this document.
Finally, regarding the support of the State Management IRP: IS (TS 32.672 [3]), all NRM's of one release shall support the same State Management IRP version.
This specification is related to 3GPP TS 32.672. |
32.731 | Telecommunication management; IP Multimedia Subsystem (IMS) Network Resource Model (NRM) Integration Reference Point (IRP); Requirements | TS | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.731/32731-b00.zip | The present document defines, in addition to the requirements defined in [1], [2] and [3], the requirements for the present IRP: IMS Network Resource Model (NRM) IRP. |
32.716 | Telecommunication management; Configuration Management (CM); Transport Network (TN) interface Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.716/32716-b00.zip | The present document is part of an Integration Reference Point (IRP) named Transport Network (TN) interface Network Resource Model (NRM) IRP, through which an IRPAgent can communicate configuration management information to one or several IRPManagers concerning TN resources. The TN NRM IRP comprises a set of specifications defining Requirements, a protocol neutral Information Service and one or more Solution Set(s).
The present document specifies the Solution Sets for the TN NRM IRP.
This specification is related to 3GPP TS 32.712 [4] V11.0.X. |
32.741 | Telecommunication management; Configuration Management (CM); Signalling Transport Network (STN) interface Network Resource Model (NRM) Integration Reference Point (IRP); Requirements | TS | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.741/32741-b00.zip | The present document defines , in addition to the requirements defined in [1], [2] and [3], the requirements for the Signalling Transport Network (STN) interface NRM IRP. |
32.722 | Telecommunication management; Configuration Management (CM); Repeater network resources Integration Reference Point (IRP); information Service (IS) | TS | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.722/32722-b00.zip | The present document is part of an Integration Reference Point (IRP) named "Repeater Network Resources IRP", through which an "IRPAgent" (typically an Element Manager or Network Element) can communicate Configuration Management information to one or several "IRPManagers" (typically Network Managers) concerning Repeater resources. The "Repeater Network Resources IRP" comprises a set of specifications defining Requirements, a protocol neutral Network Resource Model (NRM) and corresponding Solution Set(s).
The present document specifies the protocol neutral Repeater Network Resources IRP: Network Resource Model.
It reuses relevant parts of the generic NRM in TS 32.622 [10] and 32.642 [5], either by direct reuse or sub-classing, and in addition to that defines Repeater specific Information Object Classes.
The Configuration Management (CM) area is very large. The intention is to split the specification of the related interfaces in several IRPs – as described in the Introduction clause above. An important aspect of such a split is that the Network Resource Models (NRMs) defined in different IRPs containing NRMs are consistent, and that NRMs supported by an IRPAgent implementation can be accessed as one coherent model through one IRP Information Service (IS).
To summarize, the present document has the following main purpose: to define the applied Repeater specific NRM, based on the generic NRM in 3GPP TS 32.622 [10].
In order to access the information defined by this NRM, an IRP IS is needed, such as the Basic CM IRP IS (3GPP TS 32.602[11]) or the Bulk CM IRP IS (3GPP TS 32.612 [12]). However, which IS that is applicable is outside the scope of the present document. |
32.726 | Telecommunication management; Configuration Management (CM); Repeater network resources Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.726/32726-b00.zip | The present specifies the Solution Set definitions for the IRP whose semantics are specified in the Repeater Network Resources IRP NRM Information Service (3GPP TS 32.722 [1]).
This Solution Set specification is related to TS 32.722 v11.0.X. |
32.732 | Telecommunication management; IP Multimedia Subsystem (IMS) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) | TS | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.732/32732-b00.zip | The present document is part of an Integration Reference Point (IRP) named IMS Network Resource Model (NRM) IRP, through which an IRPAgent can communicate configuration management information to one or several IRPManagers concerning IMS resources. The IMS NRM IRP comprises a set of specifications defining Requirements, a protocol neutral Information Service and one or more Solution Set(s).
The present document specifies the protocol neutral IMS NRM IRP: Information Service (IS). It reuses relevant parts of the Generic NRM IRP: IS in 3GPP TS 32.622 [9], either by direct reuse or sub-classing, and in addition to that defines IMS specific Information Object Classes.
Finally, in order to access the information defined by this NRM, an Interface IRP is needed, such as the Basic CM IRP in 3GPP TS 32.602 [10]. However, which Interface IRP that is applicable is outside the scope of the present document. |
32.742 | Telecommunication management; Configuration Management (CM); Signalling Transport Network (STN) interface Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) | TS | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.742/32742-b00.zip | The present document is part of an Integration Reference Point (IRP) named "Signalling Transport Network (STN) network resources IRP", through which an "IRPAgent" (typically an Element Manager or Network Element) can communicate Configuration Management information to one or several "IRPManagers" (typically Network Managers) concerning Signalling Transport resources. This IRP comprises a set of specifications defining Requirements, a protocol neutral Network Resource Model (NRM) and corresponding Solution Set(s).
The present document specifies the protocol neutral STN resources IRP NRM. It reuses relevant parts of the generic NRM in TS 32.622 [6], either by direct reuse or sub-classing, and in addition to that defines Signalling Transport specific Managed Object Classes.
The Configuration Management (CM) area is very large. The intention is to split the specification of the related interfaces in several IRPs - as described in the Introduction clause above. An important aspect of such a split is that the NRMs defined in different IRPs containing NRMs are consistent, and that NRMs supported by an IRPAgent implementation can be accessed as one coherent model through one IRP Information Service (IS).
To summarize, the present document has the following main purpose: to define the applied Signalling Transport Network specific NRM, based on the generic NRM in 3GPP TS 32.622 [6].
In order to access the information defined by this NRM, an IRP IS is needed, such as the Basic CM IRP: IS (TS 32.602 [7]) or the Bulk CM IRP: IS (TS 32.612 [8]). However, which IS is applicable is outside the scope of this document.
Finally, regarding the support of the State Management IRP: IS (TS 32.672 [3]), all NRMs of one release shall support the same State Management IRP version. |
32.746 | Telecommunication management; Configuration Management (CM); Signalling Transport Network (STN) interface Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.746/32746-b00.zip | The present document is part of an Integration Reference Point (IRP) named Signalling Transport Network (STN) interface Network Resource Model (NRM) IRP, through which an IRPAgent can communicate configuration management information to one or several IRPManagers concerning STN resources. The STN NRM IRP comprises a set of specifications defining Requirements, a protocol neutral Information Service and one or more Solution Set(s).
The present document specifies the Solution Sets for the STN NRM IRP.
This specification is related to 3GPP TS 32.742 [9] V11.0.X. |
32.751 | Telecommunication management; Evolved Packet Core (EPC) Network Resource Model (NRM) Integration Reference Point (IRP); Requirements | TS | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.751/32751-b00.zip | The present document defines, in addition to the requirements defined in [1], [2] and [3], the Requirements for the EPC Network Resource Model (NRM) IRP. |
32.752 | Telecommunication management; Evolved Packet Core (EPC) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) | TS | 11.0.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.752/32752-b01.zip | The present document specifies the protocol neutral EPC Network Resource Model IRP Information Service, through which an 'IRPAgent' (typically an Element Manager or Network Element) can communicate information to one or several 'IRPManagers' (typically Network Managers) concerning EPC resources. It reuses relevant parts of the Generic NRM in 3GPP TS 32.622 [6], either by direct reuse or sub-classing, and in addition to that defines EPC specific Information Object Classes.
In order to access the information defined by this NRM, an Interface IRP such as the "Basic CM IRP" is needed (3GPP TS 32.602 [7]). However, which Interface IRP is applicable is outside the scope of the present document. |
32.756 | Telecommunication management; Evolved Packet Core (EPC) Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) Definitions | TS | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.756/32756-b00.zip | The TS 32.75x-series (EPC NRM IRP) define an Integration Reference Point (IRP) named EPC Network Resource Model (NRM) IRP, through which an "IRPAgent" (typically an Element Manager or Network Element) can communicate Network Management related information to one or several "IRPManagers" (typically Network Managers).
The present document provides solution set definitions for EPC Network Resources IRP, which define the mapping of the IRP information model (see TS 32.752 [2]) to the protocol specific details necessary for implementation of this IRP.
This Solution Set definitions specification is related to 3GPP TS 32.752 [2] v11.0.X. |
32.736 | Telecommunication management; IP Multimedia Subsystem (IMS) Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.736/32736-b00.zip | The present document specifies the Solution Set definitions for the IRP whose semantics is specified in IMS (IP Multimedia Subsystem) NRM (Network Resource Model) IRP: Information Service 3GPP TS 32.732 [3].
This Solution Set definitions specification is related to 3GPP TS 32.732 V10.1.X. |
32.761 | Telecommunication management; Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Network Resource Model (NRM) Integration Reference Point (IRP); Requirements | TS | 11.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.761/32761-b10.zip | The present document defines, in addition to the requirements defined in [1], [2] and [3], the Requirements for the E‑UTRAN Network Resource Model (NRM) IRP. |
32.771 | Telecommunication management; Home Node B (HNB) Subsystem (HNS); Network Resource Model (NRM); Integration Reference Point (IRP); Requirements | TS | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.771/32771-b00.zip | The document describes the requirements for Home NodeB Subsystem (HNS), which includes Home NodeB (HNB) and Home NodeB gateway (HNB GW). The HNS NRM IRP requirements are targeted on both HNB and HNB GW NRM. |
32.772 | Telecommunication management; Home Node B (HNB) Subsystem (HNS); Network Resource Model (NRM); Integration Reference Point (IRP); Information Service (IS) | TS | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.772/32772-b00.zip | The present document is an Integration Reference Point (IRP) named "Home Node B Subsystem (HNS) network resources IRP ", through which an 'IRPAgent' (typically an Element Manager or Network Element) can communicate Configuration Management information to one or several 'IRPManagers' (typically Network Managers) concerning HNS resources.
The present document specifies the protocol neutral HNS Network Resources IRP: Network Resource Model. It reuses relevant parts of the generic NRM in 3GPP TS 32.622 [6], either by direct reuse or sub-classing, and in addition to that defines HNS specific Information Object Classes.
In order to access the information defined by this NRM, an IRP IS is needed, such as the Basic CM IRP IS (3GPP TS 32.602 [7]) or the Bulk CM IRP IS (3GPP TS 32.612 [8]). However, which IS that is applicable is outside the scope of the present document.
The present document (NRM specification) is related to the IS in 3GPP TS 32.672 [9] |
32.762 | Telecommunication management; Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) | TS | 11.7.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.762/32762-b70.zip | The present document is part of an Integration Reference Point (IRP) named E-UTRAN Network Resource Model (NRM) IRP, through which an IRPAgent can communicate configuration management information to one or several IRPManagers concerning E-UTRAN resources. The E-UTRAN NRM IRP comprises a set of specifications defining Requirements, a protocol neutral Information Service and one or more Solution Set(s).
The present document specifies the protocol neutral E-UTRAN NRM IRP: Information Service (IS). It reuses relevant parts of the Generic NRM IRP: IS in 3GPP TS 32.622 [6], either by direct reuse or sub-classing, and in addition to that defines E-UTRAN specific Information Object Classes.
In order to access the information defined by this NRM, an Interface IRP such as the "Basic CM IRP" is needed (3GPP TS 32.602 [7]). However, which Interface IRP is applicable is outside the scope of the present document. |
32.766 | Telecommunication management; Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 11.9.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.766/32766-b90.zip | The present document is part of an Integration Reference Point (IRP) named E-UTRAN Network Resource Model (NRM) IRP, through which an IRPAgent can communicate configuration management information to one or several IRPManagers concerning E-UTRAN resources. The E-UTRAN NRM IRP comprises a set of specifications defining Requirements, a protocol neutral Information Service and one or more Solution Set(s).
The present document specifies the Solution Sets for the E-UTRAN NRM IRP.
This Solution Set specification is related to 3GPP TS 32.762 V11. 7.X [4]. |
32.782 | Telecommunication management; Home enhanced Node B (HeNB) Subsystem (HeNS); Network Resource Model (NRM); Integration Reference Point (IRP): Information Service (IS) | TS | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.782/32782-b00.zip | The present document is an Integration Reference Point (IRP) named " Home enhanced Node B Subsystem (HeNS) Network Resources IRP", through which an 'IRPAgent' (typically an Element Manager or Network Element) can communicate Configuration Management information to one or several 'IRPManagers' (typically Network Managers) concerning HeNB-GW resources.
The present document specifies the protocol neutral HeNS Network Resources IRP: Network Resource Model. It reuses relevant parts of the generic NRM in 3GPP TS 32.622 [5], either by direct reuse or sub-classing, and in addition to that defines HeNB-GW specific Information Object Classes.
In order to access the information defined by this NRM, an IRP IS is needed, such as the Basic CM IRP IS (3GPP TS 32.602 [6]) or the Bulk CM IRP IS (3GPP TS 32.612 [7]). However, which IS that is applicable is outside the scope of the present document.
The present document (NRM specification) is related to the IS in 3GPP TS 32.672 [8] |
32.781 | Telecommunication management; Home enhanced Node B (HeNB) Subsystem (HeNS); Network Resource Model (NRM); Integration Reference Point (IRP); Requirements | TS | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.781/32781-b00.zip | The document describes the requirements for Home eNodeB Subsystem (HeNS), which include Home eNodeB (HeNB) and Home eNodeB gateway (HeNB GW). The HeNS NRM IRP requirements are targeted on both HeNB and HeNB GW NRM. |
32.776 | Telecommunication management; Home Node B (HNB) Subsystem (HNS); Network Resource Model (NRM); Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.776/32776-b00.zip | The present document is part of an Integration Reference Point (IRP) named HNS Network Resource Model (NRM) IRP, through which an IRPAgent can communicate configuration management information to one or several IRPManagers concerning HNS resources. The HNS NRM IRP comprises a set of specifications defining Requirements, a protocol neutral Information Service and one or more Solution Set(s).
The present document specifies the Solution Sets for the HNS NRM IRP.
This specification is related to 3GPP TS 32.772 V11.0.X. |
32.792 | Telecommunication management; Generic Radio Access Network (RAN) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) | TS | 11.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.792/32792-b10.zip | The present document specifies the Generic Radio Access Network (RAN) network resource information that can be communicated between an IRPAgent and one or several IRPManagers for network management purposes.
This document specifies the semantics and behaviour of information object class attributes and relations visible across the reference point in a protocol and technology neutral way. It does not define their syntax and encoding.
This document specifies equipment that may be shared between BSS in GSM, UTRAN and E‑UTRAN.
In order to access the information defined by this NRM, an Interface IRP such as the "Basic CM IRP" is needed (3GPP TS 32.602 [5]). However, which Interface IRP is applicable is outside the scope of the present document. |
32.791 | Telecommunication management; Common Radio Access Technology (RAT) Network Resource Model (NRM) Integration Reference Point (IRP); Requirements | TS | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.791/32791-b00.zip | The present document defines, in addition to the requirements defined in 3GPP TS 32.101 [2], 3GPP TS 32.102 [3] and 3GPP TS 32.600 [4], the Requirements for the Common RAT NRM IRP for equipment that may be shared between BSS in GSM, UTRAN and E‑UTRAN.
The present document can be used also for managing the equipment that can be shared by several RATs, even in the cases when it is not being shared. |
32.786 | Telecommunication management; Home enhanced Node B (HeNB) Subsystem (HeNS); Network Resource Model (NRM); Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.786/32786-b00.zip | The present document is part of an Integration Reference Point (IRP) named HeNS Network Resource Model (NRM) IRP, through which an IRPAgent can communicate configuration management information to one or several IRPManagers concerning HeNS resources. The HeNS NRM IRP comprises a set of specifications defining Requirements, a protocol neutral Information Service and one or more Solution Set(s).
The present document specifies the Solution Sets for the HeNS NRM IRP.
This Solution Set specification is related to 3GPP TS 32.782 V11.0.X. |
32.834 | Study on Operations, Administration and Maintenance (OAM) aspects of inter-Radio-Access-Technology (RAT) energy saving | TR | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.834/32834-b00.zip | General material - [2], [3] - and detailed material - [4], [5], [6] - on Energy Saving and/or its Management aspects have been created by 3GPP. The present document focuses on Inter-RAT aspects of Energy Saving, i.e. reducing the capabilities of one RAT to reduce its energy consumption while providing a back-up by another RAT. Concepts and scenarios described in [2], [3] and methods defined in [4], [5], [6] as well as additions to them are analysed to identify the most favourable management solutions in this context and their possible limitations.
The following RATs are considered in this study: GSM, UMTS; LTE, CDMA. |
32.854 | Telecommunication management; Fixed Mobile Convergence (FMC) 3GPP / TM Forum concrete model relationships and use cases | TR | 11.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.854/32854-b10.zip | This document sets out a number of independent operator activity contexts where each context has been chosen to exercise one or more of the operator requirements and to lead to points of intersection of the network model work of 3GPP and TM Forum where some degree of harmonisation would consequently seem valuable.
Each context description focuses on one or more use cases that suitably describe the relevant details of that operator activity with respect to an expected area of intersection. The use cases are first explained and then depicted via one or more stylized network and model diagrams. The model diagram is then developed to a formal model structure.
Finally the set of changes proposed cumulated from all context analyses are provided as a coherent recommendation. Respective concrete models must use this model to support the FMC use cases to claim FMC network management compliance.
It should be noted that the UIM cannot be used directly for implementation. Implementation classes must be derived from those in the UIM by Inheritance or some other appropriate mechanism. Classes derived from those in the UIM (e.g. for the fixed environment) must use different names from those used in the UIM.
This content of this document has been jointly developed by 3GPP and TM Forum as part of the Joint Working Group on Resource Model Alignment [11]. |
32.835 | Telecommunication management; Study of heterogeneous networks management | TR | 1.6.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.835/32835-160.zip | The present document investigates and makes recommendations on how management information can be selected by the manager over Itf-N for heterogeneous networks (see TR 21.905 [1]) nodes that are owned, deployed and maintained by the operator.
The nodes that are owned, deployed or maintained by residential users are out of scope of the present document, such as Home NodeBs, Home eNodeBs. |
32.901 | Telecommunication management; Study on User Data Convergence (UDC) information model handling and provisioning: Example use cases | TR | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.901/32901-b00.zip | |
32.796 | Telecommunication management; Generic Radio Access Network (RAN) Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.796/32796-b00.zip | The present document is part of an Integration Reference Point (IRP) named Generic Radio Access Network (RAN) Network Resource Model (NRM) IRP, through which an IRPAgent can communicate configuration management information to one or several IRPManagers concerning Generic RAN resources. The Generic RAN NRM IRP comprises a set of specifications defining Requirements, a protocol neutral Information Service and one or more Solution Set(s).
The present document specifies the Solution Sets for the Generic RAN NRM IRP.
This Solution Set specification is related to 3GPP TS 32.792 V11.0.X [4]. |
32.853 | Telecommunication management; Final report from the 3GPP - TM Forum Joint Work Group (JWG) on fault management harmonization | TR | 11.1.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.853/32853-b11.zip | |
33.105 | 3G Security; Cryptographic algorithm requirements | TS | 11.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.105/33105-b00.zip | |
33.106 | 3G security; Lawful interception requirements | TS | 11.2.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.106/33106-b20.zip | |
32.833 | Telecommunication management; Study on management of converged networks | TR | 11.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.833/32833-b00.zip | The present document investigates which new functionalities regarding a true end to end management are enabled by a converged OSS. The fragments looked at are Fault Management, Performance Management and Configuration Management. |
33.108 | 3G security; Handover interface for Lawful Interception (LI) | TS | 11.7.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.108/33108-b70.zip | The present document specifies the handover interfaces for Lawful Interception (LI) of Packet-Data Services, Circuit Switched Services, Multimedia Services within the UMTS network and Evolved Packet System (EPS). The handover interface in this context includes the delivery of Intercept Related Information (IRI) through the Handover Interface 2 (HI2) and Content of Communication (CC) through the Handover Interface 3 (HI3) to the Law Enforcement Monitoring Facility (LEMF). |
33.110 | Key establishment between a Universal Integrated Circuit Card (UICC) and a terminal | TS | 11.0.1 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.110/33110-b01.zip | |
33.107 | 3G security; Lawful interception architecture and functions | TS | 11.6.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.107/33107-b60.zip | |
33.102 | 3G security; Security architecture | TS | 11.7.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.102/33102-b70.zip | This specification defines the security architecture, i.e., the security features and the security mechanisms, for the third generation mobile telecommunication system.
A security feature is a service capability that meets one or several security requirements. The complete set of security features address the security requirements as they are defined in "3G Security: Threats and Requirements" (TS 21.133 [1]) and implement the security objectives and principles described in TS 33.120 [2]. A security mechanism is an element that is used to realise a security feature. All security features and security mechanisms taken together form the security architecture.
An example of a security feature is user data confidentiality. A security mechanism that may be used to implement that feature is a stream cipher using a derived cipher key.
This specification defines 3G security procedures performed within 3G capable networks (R99+), i.e. intra-UMTS and UMTS-GSM. As an example, UMTS authentication is applicable to UMTS radio access as well as GSM radio access provided that the serving network node and the MS are UMTS capable. Interoperability with non-UMTS capable networks (R98-) is also covered.
GSM security functions are defined in the TS 43.020 [36].
NOTE: The usage of the authentication management field (AMF) is specified in Annex H and applies for the third (UMTS), fourth (LTE) and fifth (5G system) generation of mobile telecommunication systems. |
33.204 | 3G Security; Network Domain Security (NDS); Transaction Capabilities Application Part (TCAP) user security | TS | 11.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.204/33204-b00.zip | |
33.203 | 3G security; Access security for IP-based services | TS | 11.2.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.203/33203-b20.zip | The scope for this technical specification is to specify the security features and mechanisms for secure access to the IM subsystem (IMS) for the 3G mobile telecommunication system.
Since the scope also encompasses the use of these security features and mechanisms for secure access to IMS in the context of fixed broadband networks and 3GPP2 networks, Annex L and Annex S specify how the material in the main body and other normative Annexes of this document apply to the fixed broadband networks and 3GPP2 networks respectively.
The IMS supports IP Multimedia applications such as video, audio and multimedia conferences. SIP, Session Initiation Protocol, was chosen as the signalling protocol for creating and terminating Multimedia sessions, cf. RFC 3261 [6]. This specification only deals with how the SIP signalling is protected between the subscriber and the IMS, how the subscriber is authenticated and how the subscriber authenticates the IMS. |
33.220 | Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture (GBA) | TS | 11.5.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.220/33220-b50.zip | |
33.221 | Generic Authentication Architecture (GAA); Support for subscriber certificates | TS | 11.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.221/33221-b10.zip | |
33.141 | Presence service; Security | TS | 11.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.141/33141-b00.zip | |
33.234 | 3G security; Wireless Local Area Network (WLAN) interworking security | TS | 11.4.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.234/33234-b40.zip | |
33.246 | 3G Security; Security of Multimedia Broadcast/Multicast Service (MBMS) | TS | 11.2.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.246/33246-b20.zip | The Technical Specification covers the security procedures of the Multimedia Broadcast/Multicast Service (MBMS) for 3GPP systems (UTRAN, GERAN and E-UTRAN). MBMS is a 3GPP system network bearer service over which many different applications could be carried. The actual method of protection may vary depending on the type of MBMS application. |
33.210 | Network Domain Security (NDS); IP network layer security | TS | 11.4.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.210/33210-b40.zip | |
33.223 | Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture (GBA) Push function | TS | 11.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.223/33223-b10.zip | |
33.222 | Generic Authentication Architecture (GAA); Access to network application functions using Hypertext Transfer Protocol over Transport Layer Security (HTTPS) | TS | 11.3.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.222/33222-b30.zip | |
33.310 | Network Domain Security (NDS); Authentication Framework (AF) | TS | 11.2.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.310/33310-b20.zip | |
33.224 | Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture (GBA) push layer | TS | 11.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.224/33224-b10.zip |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.