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.601 | Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP); Requirements | TS | 9.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.601/32601-900.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 | 9.4.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.592/32592-940.zip | |
32.613 | Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 9.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.613/32613-910.zip | The purpose of this Bulk CM IRP: CORBA Solution Set is to define the mapping of the IRP Information Service 3GPP TS 32.612 [3] to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
This Solution Set specification is related to 3GPP TS 32.612 V9.1.X. |
32.617 | Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Bulk CM IRP SOAP Solution Set (SS) | TS | 9.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.617/32617-900.zip | The present document specifies the SOAP Solution Set for the IRP whose semantics are specified in Bulk CM IRP: Information Service (3GPP TS 32.612 [4]).
This Solution Set specification is related to 3GPP TS 32.612 V9.0.X. |
32.615 | Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): eXtensible Markup Language (XML) file format definition | TS | 9.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.615/32615-920.zip | The present document provides the main part of the XML file format definition for the Bulk Configuration Management IRP IS in 3GPP TS 32.612 [1].
The other parts of this XML file format definition are NRM-specific parts.
Those NRM-specific parts are provided by 3GPP TS 32.625 [11], 32.635 [12], 32.645 [13], 32.655 [14], 32.695 [16], 32.715 [17], 32.735 [18], 32.745 [15], 32.755 [20], 32.765 [19], 32.525 [21], 32.175 [22], 32.725 [23], 32.775 [24] and 32.785 [25].
Bulk CM XML file formats are based on XML [2], XML Schema [3] [4] [5] and XML Namespace [6] standards.
This File Format Definition specification is related to 3GPP TS 32.612 V9.1.X. |
32.621 | Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP); Requirements | TS | 9.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.621/32621-900.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.625 | Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP): Bulk CM eXtensible Markup Language (XML) file format definition | TS | 9.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.625/32625-900.zip | The present document provides the NRM-specific part related to the Generic Network Resources IRP NRM [1] of the XML file format definition for the Bulk Configuration Management IRP IS [2].
The main part of this XML file format definition is provided by 3GPP TS 32.615 [3].
Bulk CM XML file formats are based on XML [4], XML Schema [5] [6] [7] and XML Namespace [8] specifications.
This specification is related to 3GPP TS 32.622 V9.0.X. |
32.611 | Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Requirements | TS | 9.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.611/32611-900.zip | |
32.623 | Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 9.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.623/32623-900.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 CORBA Solution Set.
This Solution Set specification is related to 3GPP TS 32.622 V9.0.X. |
32.631 | Telecommunication management; Configuration Management (CM); Core network resources Integration Reference Point (IRP); Requirements | TS | 9.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.631/32631-900.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.632 | Telecommunication management; Configuration Management (CM); Core Network Resources Integration Reference Point (IRP); Network Resource Model (NRM) | TS | 9.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.632/32632-920.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.622 | Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP); Network Resource Model (NRM) | TS | 9.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.622/32622-910.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.612 | Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Information Service (IS) | TS | 9.1.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.612/32612-911.zip | |
32.641 | Telecommunication management; Configuration Management (CM); UTRAN network resources Integration Reference Point (IRP); Requirements | TS | 9.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.641/32641-900.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 | 9.4.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.642/32642-940.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.633 | Telecommunication management; Configuration Management (CM); Core network resources Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 9.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.633/32633-920.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 CORBA/IDL environment.
This Solution Set specification is related to 3GPP TS 32.632 V9.1.X. |
32.635 | Telecommunication management; Configuration Management (CM); Core network resources Integration Reference Point (IRP); Bulk CM eXtensible Markup Language (XML) file format definition | TS | 9.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.635/32635-910.zip | The present document provides the NRM-specific part related to the Core Network Resources IRP NRM [1] of the XML file format definition for the Bulk Configuration Management IRP IS [2].
The main part of this XML file format definition is provided by 3GPP TS 32.615 [3].
Bulk CM XML file formats are based on XML [4], XML Schema [5] [6] [7] and XML Namespace [8] standards.
This File Format Definition specification is related to 3GPP TS 32.632 V9.1.X. |
32.651 | Telecommunication management; Configuration Management (CM); GERAN network resources Integration Reference Point (IRP); Requirements | TS | 9.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.651/32651-900.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 | 9.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.652/32652-920.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.653 | Telecommunication management; Configuration Management (CM); GERAN network resources Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 9.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.653/32653-920.zip | The purpose of this GERAN Network Resources IRP: CORBA Solution Set is to define the mapping of the IRP information model (see 3GPP TS 32.652 [4]) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
This Solution Set specification is related to 3GPP TS 32.652 V9.2.X. |
32.662 | Telecommunication management; Configuration Management (CM); Kernel CM Information Service (IS) | TS | 9.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.662/32662-900.zip | |
32.643 | Telecommunication management; Configuration Management (CM); UTRAN network resources Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 9.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.643/32643-930.zip | The purpose of this UTRAN Network Resources IRP: CORBA Solution Set is to define the mapping of the IRP information model (see TS 32.642 [4]) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
This Solution Set specification is related to 3GPP TS 32.642 V9.3.X. |
32.645 | Telecommunication management; Configuration Management (CM); UTRAN network resources Integration Reference Point (IRP); Bulk CM eXtensible Markup Language (XML) file format definition | TS | 9.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.645/32645-930.zip | The present document provides the NRM-specific part related to the UTRAN Network Resources IRP NRM [1] of the XML file format definition for the Bulk Configuration Management IRP IS [2].
The main part of this XML file format definition is provided by 3GPP TS 32.615 [3].
Bulk CM XML file formats are based on XML [4], XML Schema [5] [6] [7] and XML Namespace [8] standards.
This File Format Definition specification is related to 3GPP TS 32.642 V9.3.X. |
32.663 | Telecommunication management; Configuration Management (CM); Kernel CM Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 9.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.663/32663-900.zip | The purpose of the present document is to define the mapping of the Kernel CM IRP: IS (see 3GPP TS 32.662 [4]) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
This Solution Set specification is related to 3GPP TS 32.662 V9.0.X [4]. |
32.655 | Telecommunication management; Configuration Management (CM); GERAN network resources Integration Reference Point (IRP); Bulk CM eXtensible Markup Language (XML) file format definition | TS | 9.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.655/32655-920.zip | The present document provides the NRM-specific part related to the GERAN Network Resources IRP NRM [1] of the XML file format definition for the Bulk Configuration Management IRP IS [2].
The main part of this XML file format definition is provided by 3GPP TS 32.615 [3].
Bulk CM XML file formats are based on XML [4], XML Schema [5] [6] [7] and XML Namespace [8] specifications.
This File Format Definition specification is related to 3GPP TS 32.652 V9.2.X. |
32.661 | Telecommunication management; Configuration Management (CM); Kernel CM Requirements | TS | 9.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.661/32661-900.zip | |
32.671 | Telecommunication management; Configuration Management (CM); State Management Integration Reference Point (IRP); Requirements | TS | 9.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.671/32671-900.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.667 | Telecommunication management; Configuration Management (CM); Kernel CM Integration Reference Point (IRP); SOAP Solution Set (SS) | TS | 9.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.667/32667-900.zip | The purpose of the present document is to define the mapping of the Kernel CM IRP: IS (3GPP TS 32.662 [4]) to the protocol specific details necessary for implementation of this IRP in a SOAP/WSDL environment.
This Solution Set specification is related to 3GPP TS 32.662 V9.0.X. |
32.673 | Telecommunication management; Configuration Management (CM); State Management Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 9.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.673/32673-900.zip | The present document specifies the CORBA Solution Set (SS) for the IRP whose semantics is specified in State Management IRP: Information Service (IS) (3GPP TS 32.672 [2]).
Clause 1 to 3 provides background information. Clause 4 provides key architectural features supporting the SS. Clause 5 defines the mapping of operations, notification, parameters and attributes defined in IS to their SS equivalents. Annex A contains the IDL specification.
This Solution Set specification is related to 3GPP TS 32.672 V9.0.X. |
32.675 | Telecommunication management; Configuration Management (CM); State Management Integration Reference Point (IRP); Bulk CM eXtensible Markup Language (XML) file format definition | TS | 9.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.675/32675-900.zip | The present document specifies the XML file format definition for the Bulk Configuration Management IRP IS [2] for the IRP whose semantics is specified in State Management IRP: Information Service (IS) (3GPP TS 32.672 [1]).
Bulk CM XML file formats are based on XML [4], XML Schema [5] [6] [7] and XML Namespace [8] standards.
This File Format Definition specification is related to 3GPP TS 32.672 V9.0.X. |
32.665 | Telecommunication management; Configuration Management (CM); Kernel CM Integration Reference Point (IRP); eXtensible Markup Language (XML) definitions | TS | 9.0.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.665/32665-901.zip | The present document specifies the XML Definitions for the Kernel CM Integration Reference Point (IRP) as it applies to Itf-N, in accordance with Kernel CM IRP IS definitions [3] as well as Notification Log IRP XML Definitions [4].
This specification is related to 3GPP TS 32.662 V9.0.X. |
32.691 | Telecommunication management; Inventory Management (IM) network resources Integration Reference Point (IRP): Requirements | TS | 9.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.691/32691-900.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.690 | Telecommunication management; Inventory Management (IM); Requirements | TS | 9.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.690/32690-900.zip | |
32.712 | Telecommunication management; Configuration Management (CM); Transport Network (TN) interface Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) | TS | 9.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.712/32712-910.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.692 | Telecommunication management; Inventory Management (IM) network resources Integration Reference Point (IRP); Network Resource Model (NRM) | TS | 9.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.692/32692-900.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.711 | Telecommunication management; Configuration Management (CM); Transport Network (TN) interface Network Resource Model (NRM) Integration Reference Point (IRP); Requirements | TS | 9.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.711/32711-900.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.695 | Telecommunication management; Inventory Management (IM) network resources Integration Reference Point (IRP); Bulk Configuration Management (CM) eXtensible Markup Language (XML) file format definition | TS | 9.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.695/32695-900.zip | The present document provides the NRM-specific part related to the Inventory Management NRM IRP IS in 3GPP TS 32.692 [1] of the XML file format definition for the Bulk Configuration Management IRP IS in 3GPP TS 32.612 [2].
The main part of this XML file format definition is provided by 3GPP TS 32.615 [3].
Inventory Management XML file formats are based on XML [4], XML Schema [5] [6] [7] and XML Namespace [8] standards.
This File Format Definition specification is related to 3GPP TS 32.692 V9.0.X. |
32.715 | Telecommunication management; Configuration Management (CM) Transport Network (TN); Network Resource Model (NRM) Integration Reference Point (IRP); Bulk CM eXtensible Markup Language (XML) file format definition | TS | 9.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.715/32715-900.zip | The present document provides the NRM-specific part related to 3GPP TS 32.712 [1] Transport Network (TN) interface NRM IRP IS of the XML file format definition for the 3GPP TS 32.612 [2] Bulk Configuration Management IRP IS.
The main part of this XML file format definition is provided by 3GPP TS 32.615 [3].
Bulk CM XML file formats are based on XML [4], XML Schema [5] [6] [7] and XML Namespace [8] standards.
This File Format Definition specification is related to 3GPP TS 32.712 V9.0.X. |
32.713 | Telecommunication management; Configuration Management (CM); Transport Network (TN) Network Resource Model (NRM) Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 9.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.713/32713-900.zip | The purpose of this Transport Network (TN) interface Network Resource Model IRP: CORBA Solution Set is to define the mapping of the IRP information model in 3GPP TS 32.712 [4] to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
This Solution Set specification is related to 3GPP TS 32.712 V9.0.X. |
32.672 | Telecommunication management; Configuration Management (CM); State Management Integration Reference Point (IRP); Information Service (IS) | TS | 9.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.672/32672-900.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.723 | Telecommunication management; Configuration Management (CM); Repeater network resources Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 9.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.723/32723-900.zip | The purpose of this Repeater Network Resources IRP: CORBA Solution Set is to define the mapping of the IRP information model (see 3GPP TS 32.722 [4]) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
This Solution Set specification is related to 3GPP TS 32.722. |
32.731 | Telecommunication management; IP Multimedia Subsystem (IMS) Network Resource Model (NRM) Integration Reference Point (IRP); Requirements | TS | 9.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.731/32731-900.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.725 | Telecommunication management; Configuration Management (CM); Repeater network resources Integration Reference Point (IRP); Bulk CM eXtensible Markup Language (XML) file format definition | TS | 9.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.725/32725-900.zip | The present document provides the NRM-specific part related to the Repeater Network Resources IRP NRM [1] of the XML file format definition for the Bulk Configuration Management IRP IS [2].
The main part of this XML file format definition is provided by 3GPP TS 32.615 [3].
Bulk CM XML file formats are based on XML [4], XML Schema [5] [6] [7] and XML Namespace [8] standards.
This File Format Definition specification is related to 3GPP TS 32.722 V9.0.X. |
32.721 | Telecommunication management; Configuration Management (CM); Repeater network resources Integration Reference Point (IRP); Requirements | TS | 9.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.721/32721-900.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.722 | Telecommunication management; Configuration Management (CM); Repeater network resources Integration Reference Point (IRP); information Service (IS) | TS | 9.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.722/32722-900.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.732 | Telecommunication management; IP Multimedia Subsystem (IMS) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) | TS | 9.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.732/32732-910.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.741 | Telecommunication management; Configuration Management (CM); Signalling Transport Network (STN) interface Network Resource Model (NRM) Integration Reference Point (IRP); Requirements | TS | 9.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.741/32741-900.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.735 | Telecommunication management; IP Multimedia Subsystem (IMS) Network Resource Model (NRM) Integration Reference Point (IRP); Bulk CM eXtensible Markup Language (XML) file format definition | TS | 9.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.735/32735-910.zip | The present document provides the NRM-specific part related to the IMS NRM IRP [1] of the XML file format definition for the Bulk Configuration Management IRP IS [2].
The main part of this XML file format definition is provided by 3GPP TS 32.615 [3].
Bulk CM XML file formats are based on XML [4], XML Schema [5] [6] [7] and XML Namespace [8] standards.
This File Format Definition specification is related to 3GPP TS 32.732 V9.1.X. |
32.733 | Telecommunication management; IP Multimedia Subsystem (IMS) Network Resource Model (NRM) Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 9.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.733/32733-910.zip | The purpose of this IMS NRM IRP: CORBA Solution Set is to define the mapping of the IRP Information Service (see TS 32.732 [3]) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
This Solution Set specification is related to 3GPP TS 32.732. |
32.742 | Telecommunication management; Configuration Management (CM); Signalling Transport Network (STN) interface Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) | TS | 9.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.742/32742-900.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.752 | Telecommunication management; Evolved Packet Core (EPC) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) | TS | 9.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.752/32752-930.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.743 | Telecommunication management; Configuration Management (CM); Signalling Transport Network (STN) interface Network Resource Model (NRM) Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 9.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.743/32743-900.zip | The present document maps the IRP information model in 32.742 [4] to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
This Solution Set specification is related to 3GPP TS 32.742 V9.0.X. |
32.753 | Telecommunication management; Evolved Packet Core (EPC) Network Resource Model (NRM) Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 9.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.753/32753-920.zip | The present document is part of an Integration Reference Point (IRP) named EPC Network Resource Model (NRM) IRP, through which an IRPAgent can communicate configuration management information to one or several IRPManagers concerning EPC resources. The EPC 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 EPC Network Resources IRP: CORBA Solution Set, which defines the mapping of the IRP information model (see TS 32.752 [2]) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
This Solution Set is related to 3GPP TS 32.752 v9.3.X. |
32.745 | Telecommunication management; Configuration Management (CM); Signalling Transport Network (STN) interface Network Resource Model (NRM) Integration Reference Point (IRP); Bulk CM eXtensible Markup Language (XML) file format definition | TS | 9.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.745/32745-900.zip | The present document provides the NRM-specific part related to the STN Network Resources IRP NRM in 32.742 [1] of the XML file format definition for the Bulk Configuration Management IRP IS (TS 32.612 [2]).
The main part of this XML file format definition is provided by 3GPP TS 32.615 [3].
Bulk CM XML file formats are based on XML [4], XML Schema [5] [6] [7] and XML Namespace [8] specifications.
This File Format Definition specification is related to 3GPP TS 32.742 V9.0.X. |
32.751 | Telecommunication management; Evolved Packet Core (EPC) Network Resource Model (NRM) Integration Reference Point (IRP); Requirements | TS | 9.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.751/32751-900.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.762 | Telecommunication management; Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) | TS | 9.5.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.762/32762-950.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.763 | Telecommunication management; Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Network Resource Model (NRM) Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 9.5.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.763/32763-950.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 E-UTRAN Network Resources IRP: CORBA Solution Set, which defines the mapping of the IRP information model (see TS 32.762 [2]) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
This Solution Set is related to 3GPP TS 32.762 v9. 5.X. |
32.771 | Telecommunication management; Home Node B (HNB) Subsystem (HNS); Network Resource Model (NRM); Integration Reference Point (IRP); Requirements | TS | 9.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.771/32771-910.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.755 | Telecommunication management; Evolved Packet Core (EPC) Network Resource Model (NRM) Integration Reference Point (IRP); eXtensible Markup Language (XML) definitions | TS | 9.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.755/32755-930.zip | The present document provides the XML file format definition for the EPC Network Resource Model IRP IS [2] V9.3.X.
An application of these XML definitions is to build a configuration file for transfer with the Bulk CM IRP using either CORBA Solution Set of 3GPP TS 32.613 [3] or the SOAP Solution Set of 3GPP TS 32.617 [5]. For this application, the basic part of the XML file format definition is provided by 3GPP TS 32.615 [4].
Other applications of these XML definitions are the SOAP solution sets of other IRPs that perform operations on managed objects, for example the Basic CM IRP SOAP SS of 3GPP TS 32.607 [6]. |
32.772 | Telecommunication management; Home Node B (HNB) Subsystem (HNS); Network Resource Model (NRM); Integration Reference Point (IRP); Information Service (IS) | TS | 9.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.772/32772-900.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.761 | Telecommunication management; Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Network Resource Model (NRM) Integration Reference Point (IRP); Requirements | TS | 9.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.761/32761-900.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.765 | Telecommunication management; Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Network Resource Model (NRM) Integration Reference Point (IRP); eXtensible Markup Language (XML) definitions | TS | 9.6.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.765/32765-960.zip | The present document provides the XML definitions for the E-UTRAN Network Resource Model IRP IS [2].
An application of these XML definitions is to build a configuration file for transfer with the Bulk CM IRP using either CORBA Solution Set of 3GPP TS 32.613 [3] or the SOAP Solution Set of 3GPP TS 32.617 [5]. For this application, the basic part of the XML file format definition is provided by 3GPP TS 32.615 [4].
Other applications of these XML definitions are the SOAP solution sets of other IRPs that perform operations on managed objects, for example the Basic CM IRP SOAP SS of 3GPP TS 32.607 [6].
This specification is related to 3GPP TS 32.762 V9. 5.X. |
32.773 | Telecommunication management; Home Node B (HNB) Subsystem (HNS); Network Resource Model (NRM); Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 9.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.773/32773-900.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 HNS Network Resources IRP: CORBA Solution Set, which defines the mapping of the IRP information model (see TS 32.772 [5]) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment. |
32.783 | Telecommunication management; Home enhanced Node B (HeNB) Subsystem (HeNS); Network Resource Model (NRM); Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 9.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.783/32783-900.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 HeNS Network Resources IRP: CORBA Solution Set, which defines the mapping of the IRP information model (see TS 32.782 [2]) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment. |
32.781 | Telecommunication management; Home enhanced Node B (HeNB) Subsystem (HeNS); Network Resource Model (NRM); Integration Reference Point (IRP); Requirements | TS | 9.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.781/32781-910.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.785 | Telecommunication management; Home enhanced Node B (HeNB) Subsystem (HeNS); Network Resource Model (NRM); Integration Reference Point (IRP); Bulk CM eXtensible Markup Language (XML) file format definition | TS | 9.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.785/32785-910.zip | The present document provides the XML file format definition for the HeNS Network Resource Model IRP IS [2].
An application of these XML definitions is to build a configuration file for transfer with the Bulk CM IRP using either CORBA Solution Set of 3GPP TS 32.613 [3] or the SOAP Solution Set of 3GPP TS 32.617 [5]. For this application, the basic part of the XML file format definition is provided by 3GPP TS 32.615 [4].
Other applications of these XML definitions are the SOAP solution sets of other IRPs that perform operations on managed objects, for example the Basic CM IRP SOAP SS of 3GPP TS 32.607 [6]. |
32.775 | Telecommunication management; Home Node B (HNB) Subsystem (HNS); Network Resource Model (NRM); Integration Reference Point (IRP); eXtensible Markup Language (XML) file format definition | TS | 9.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.775/32775-910.zip | |
32.823 | Telecommunication management; Self-Organizing Networks (SON); Study on self-healing | TR | 9.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.823/32823-900.zip | The present document is focused on studying on self-healing of SON. This study provides the general procedure of self-healing, and collects the use cases of self-healing and proposed related requirements. The findings and proposals of the study may be used to help generate new Technical Specifications (TS) and/or enhance existing Technical Specifications. |
32.822 | Telecommunication management; Study on System Maintenance over Itf-N | TR | 9.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.822/32822-900.zip | The present document studies key maintenance functions of element management system (EMS) in order to decide which one is necessary and could be managed over Itf-N, and makes a set of recommendations. |
32.821 | Telecommunication management; Study of Self-Organizing Networks (SON) related Operations, Administration and Maintenance (OAM) for Home Node B (HNB) | TR | 9.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.821/32821-900.zip | The present document intends to study the following:
1) Define SON OAM solution architecture for both LTE and UMTS home NodeB.
2) Identify differences between SON OAM solution architecture for LTE Marco eNodeB and that for LTE and UMTS home NodeB; Propose aligned SON OAM solution architecture.
3) Identify what can be standardized for SON for LTE and UMTS NodeB in 3GPP SA5.
4) Prepare the work for a later implementation work item. |
33.102 | 3G security; Security architecture | TS | 9.6.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.102/33102-960.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. |
32.824 | Telecommunication management; Service Oriented Architecture (SOA) Integration Reference Point (IRP) study | TR | 9.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.824/32824-900.zip | Service Oriented Architecture (SOA) is gaining acceptance in the IS/IT industry. It promises to manage change [1], automate and simplify IT processes [1], optimize implementation [2], maximize (implementation) flexibility and scalability [3], facilitate integration beyond the enterprise (between companies, between partners and customers) [4], simplify development [5] and maintenance; etc.
IRP (Interface Reference Point) is the predominant standard for wireless network management since 2000. 3GPP developed it with 3GPP2 close collaboration. IRP architecture follows closely with that defined by ITU-T TMN work [6]. Besides publishing the IRP specifications, 3GPP also publishes its IRP methodology (e.g., the guidelines, templates on how to develop, maintain and publish IRP specifications). Today, the IRP specification methodology is being shared and jointly evolved and maintained by consortium of SDOs, such as ITU-T.
We note that the principles of SOA are currently being applied to the field of network management [11,12,16,17].
The purpose of this document is to analyse the IRP architecture and to provide a "gap analysis" on what enhancement is needed for the current set of IRP specifications such that it can claim to have the full set of characteristics of SOA. |
33.108 | 3G security; Handover interface for Lawful Interception (LI) | TS | 9.8.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.108/33108-980.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.105 | 3G Security; Cryptographic algorithm requirements | TS | 9.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.105/33105-900.zip | |
33.110 | Key establishment between a Universal Integrated Circuit Card (UICC) and a terminal | TS | 9.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.110/33110-910.zip | |
33.106 | 3G security; Lawful interception requirements | TS | 9.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.106/33106-900.zip | |
32.782 | Telecommunication management; Home enhanced Node B (HeNB) Subsystem (HeNS); Network Resource Model (NRM); Integration Reference Point (IRP): Information Service (IS) | TS | 9.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.782/32782-900.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] |
33.203 | 3G security; Access security for IP-based services | TS | 9.5.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.203/33203-950.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 | 9.4.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.220/33220-940.zip | |
33.107 | 3G security; Lawful interception architecture and functions | TS | 9.4.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.107/33107-940.zip | |
33.221 | Generic Authentication Architecture (GAA); Support for subscriber certificates | TS | 9.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.221/33221-910.zip | |
33.210 | Network Domain Security (NDS); IP network layer security | TS | 9.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.210/33210-910.zip | |
33.141 | Presence service; Security | TS | 9.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.141/33141-910.zip | |
33.223 | Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture (GBA) Push function | TS | 9.2.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.223/33223-920.zip | |
33.246 | 3G Security; Security of Multimedia Broadcast/Multicast Service (MBMS) | TS | 9.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.246/33246-910.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.234 | 3G security; Wireless Local Area Network (WLAN) interworking security | TS | 9.2.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.234/33234-920.zip | |
33.204 | 3G Security; Network Domain Security (NDS); Transaction Capabilities Application Part (TCAP) user security | TS | 9.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.204/33204-900.zip | |
33.224 | Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture (GBA) push layer | TS | 9.2.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.224/33224-920.zip | |
33.222 | Generic Authentication Architecture (GAA); Access to network application functions using Hypertext Transfer Protocol over Transport Layer Security (HTTPS) | TS | 9.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.222/33222-910.zip | |
33.320 | Security of Home Node B (HNB) / Home evolved Node B (HeNB) | TS | 9.7.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.320/33320-970.zip | |
33.402 | 3GPP System Architecture Evolution (SAE); Security aspects of non-3GPP accesses | TS | 9.7.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.402/33402-970.zip | |
33.310 | Network Domain Security (NDS); Authentication Framework (AF) | TS | 9.8.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.310/33310-980.zip | |
33.401 | 3GPP System Architecture Evolution (SAE); Security architecture | TS | 9.9.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.401/33401-990.zip | |
33.812 | Feasibility study on the security aspects of remote provisioning and change of subscription for Machine to Machine (M2M) equipment | TR | 9.2.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.812/33812-920.zip | The scope of this Technical Report is to study the remote subscription management for M2M Equipment (M2ME) when the Machine Communications Identity Module (MCIM) application resides in the UICC and when the MCIM application resides in the M2M equipment. The remote subscription management includes tasks such as remote subscription provisioning and/or remote change of subscription.
The scope of this study includes the definition of a trust model for remote subscription management for M2ME.Security threats and security requirements are identified, and an evaluation of the candidate solutions is presented.
The security implications of the following requirements are within the scope of the study (based on section 5.2.2 of TR 22.868)
1. The possibility to change subscription for M2MEs out in the field (e.g. after contract expiry) without direct human intervention.
2. The possibility to allocate the M2ME at initial power up to a network operator without direct human intervention.
Furthermore, this study includes the following items:
- an investigation of candidate security solutions architectures that allow remote subscription management to take place in a secure manner;
- an identification of current USIM/ISIM functionality that may need to be incorporated in a MCIM application, with or without changes to allow remote subscription management for the M2ME;
- an identification of functionality in the network, in the UICC or in the M2ME, that may need to be added due to the remote subscription management method;
- the study may identify principle requirements for protected storage and the execution environment (e.g. by collaborating with relevant working groups such as the OMTP Hardware group)
This study is beyond the scope of the first requirement identified in SA1 TR 22.868 since section 5.2.2 of TR 22.868 contains a requirement to have "Tamper Save/Theft proof terminal including a UICC". |
33.259 | Key establishment between a UICC hosting device and a remote device | TS | 9.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.259/33259-900.zip | |
33.328 | IP Multimedia Subsystem (IMS) media plane security | TS | 9.3.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.328/33328-930.zip | |
33.905 | Recommendations for Trusted Open Platforms | TR | 9.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.905/33905-900.zip | |
33.919 | 3G Security; Generic Authentication Architecture (GAA); System description | TR | 9.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.919/33919-910.zip | |
33.924 | Identity management and 3GPP security interworking; Identity management and Generic Authentication Architecture (GAA) interworking | TR | 9.4.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.924/33924-940.zip | |
33.828 | IP Multimedia Subsystem (IMS) media plane security | TR | 9.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.828/33828-910.zip |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.