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.371 | Telecommunication management; Security Management concept and requirements | TS | 6.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.371/32371-620.zip | |
32.353 | Telecommunication management; Communication Surveillance (CS) Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 6.4.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.353/32353-640.zip | The present document specifies the CORBA Solution Set for the IRP whose semantics are specified in TS 32.352 [6] Communication Surveillance IRP: Information Service.
This Solution Set specification is related to 3GPP TS 32.352 V9.0.X. |
32.332 | Telecommunication management; Notification Log (NL) Integration Reference Point (IRP); Information Service (IS) | TS | 6.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.332/32332-630.zip | |
32.411 | Telecommunication management; Performance Management (PM) Integration Reference Point (IRP): Requirements | TS | 6.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.411/32411-630.zip | |
32.412 | Telecommunication management; Performance Management (PM) Integration Reference Point (IRP): Information Service (IS) | TS | 6.9.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.412/32412-690.zip | |
32.401 | Telecommunication management;Performance Management (PM);Concept and requirements | TS | 6.4.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.401/32401-641.zip | The present document describes the requirements for the management of performance measurements and the collection of performance measurement result data across GSM, UMTS and LTE networks. It defines the administration of measurement schedules by the Network Element Manager (EM), the generation of measurement results in the Network Elements (NEs) and the transfer of these results to one or more Operations Systems, i.e. EM(s) and/or Network Manager(s) (NM(s)).
The basic Performance Management concept that the present document is built upon is described in clause 4.
The requirements of how an EM administers the performance measurements and how the results can be collected are defined in detail in clause 5. Measurements available for collection by NEs are described in the following specifications:
- TS 52.402 for GSM systems;
- TS 32.405, TS 32.406, TS 32.407 and TS 32.408 for UMTS and combined UMTS/GSM systems;
- TS 32.409 for IMS networks;
- TS 32.425 for E-UTRAN;
- TS 32.426 for EPC;
- TS 32.452 for Home Node B (HNB) Subsystem (HNS);
- TS 32.453 for Home enhanced Node B (HeNB) Subsystem (HeNS);
- TS 28.402 for Evolved Packet Core (EPC) and non-3GPP access Interworking System;
- TS 28.403 for Wireless Local Area Network (WLAN).
Effort has been made to ensure consistency in the definition of measurements between different NEs and generations. The performance measurement result is described in Performance Measurement File Format Definition (3GPP TS 32.432 [29]).
The following is beyond the scope of the present document, and therefore the present document does not describe:
- the formal definition of the interface that the EM uses to administer performance measurements in the NEs;
- the formal definition of the interface that the EM uses to collect measurement results from the NEs;
- how the data, once accumulated and collected, could or should be processed, stored, or presented to an end user;
- the information which may be obtained through the collection and processing of call or event related records which have been produced by the NEs primarily for the purpose of raising bills and other charges.
The management requirements have been derived from existing telecommunications operations experience. The management definitions were then derived from other standardisation work so as to minimise the re-invention factor. References are given as appropriate.
The objectives of this standardisation are:
- to provide the descriptions for a standard set of measurements;
- to produce a common description of the management technique for measurement administration and result accumulation; and
- to define a method for the bulk transmission of measurement results across a management interface.
The definition of the standard measurements is intended to result in comparability of measurement result data produced in a multi-vendor wireless network, for those measurement types that can be standardised across all vendors' implementations.
As far as possible, existing standardisation in the area of Performance Management has been re-used and enhanced where particular requirements, peculiar to the mobile telephony environment, have been recognised.
The present document considers all the above aspects of Performance Management for a GSM, UMTS or LTE network and its NEs defined in the core Technical Specifications. However, only those aspects which are specific to a GSM/UMTS/LTE system and particular to wireless network operation are included in the present document. |
32.414 | Telecommunication management; Performance Management (PM) Integration Reference Point (IRP): Common Management Information Protocol (CMIP) Solution Set (SS) | TS | 6.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.414/32414-610.zip | The present document defines the performance management integration reference point for the CMIP solution set. It provides all the GDMO and ASN.1 definitions necessary to implement the PM IRP Information Service (TS 32.412 [7]) for the CMIP interface. In detail:
- clause 4 contains an introduction to some basic concepts of the CMIP interfaces;
- clause 5 contains the GDMO definitions for the Performance Management over the CMIP interfaces;
- clause 6 contains the ASN.1 definitions supporting the GDMO definitions provided in clause 5.
This Solution Set specification is based on 3GPP TS32.412 (v6.4.0). |
32.413 | Telecommunication management; Performance Management (PM) Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 6.9.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.413/32413-690.zip | The present document specifies the Common Object Request Broker Architecture (CORBA) Solution Set (SS) for the IRP whose semantics is specified in PM (Performance Management) IRP: Information Service 3GPP TS 32.412 [7].
This Solution Set specification is related to 3GPP TS 32.412 [7]. |
32.422 | Telecommunication management; Subscriber and equipment trace; Trace control and configuration management | TS | 6.5.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.422/32422-650.zip | |
32.423 | Telecommunication management; Subscriber and equipment trace; Trace data definition and management | TS | 6.6.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.423/32423-660.zip | |
32.432 | Telecommunication management; Performance measurement: File format definition | TS | 6.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.432/32432-610.zip | |
32.421 | Telecommunication management; Subscriber and equipment trace; Trace concepts and requirements | TS | 6.7.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.421/32421-670.zip | |
32.403 | Telecommunication management; Performance Management (PM); Performance measurements; UMTS and combined UMTS/GSM | TS | 6.9.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.403/32403-690.zip | The present document describes the measurements for UMTS and combined UMTS/GSM.
TS 32.401 [12] describes Performance Management concepts and requirements.
The present document is valid for all measurement types provided by an implementation of a UMTS network and combined UMTS/GSM network.
Only measurement types that are specific to UMTS or combined UMTS/GSM networks are defined within the present documents. Vendor specific measurement types used in UMTS and combined UMTS/GSM networks are not covered. Instead, these could be applied according to manufacturer's documentation.
Measurements related to "external" technologies (such as ATM or IP) as described by "external" standards bodies (e.g. ITU-T or IETF) shall only be referenced within this specification, wherever there is a need identified for the existence of such a reference.
The definition of the standard measurements is intended to result in comparability of measurement data produced in a multi-vendor network, for those measurement types that can be standardised across all vendors' implementations.
The structure of the present document is as follows:
- Header 1: Network Element (e.g. RNC related measurements);
- Header 2: Measurement function (e.g. soft handover measurements);
- Header 3: Measurements. |
32.435 | Telecommunication management; Performance measurement; eXtensible Markup Language (XML) file format definition | TS | 6.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.435/32435-620.zip | |
32.601 | Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP); Requirements | TS | 6.1.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.601/32601-611.zip | |
32.600 | Telecommunication management; Configuration Management (CM); Concept and high-level requirements | TS | 6.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.600/32600-600.zip | |
32.603 | Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 6.4.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.603/32603-640.zip | The purpose of this Basic Configuration Management (CM) IRP: CORBA Solution Set is to define the mapping of the Basic CM IRP: IS (see 3GPP TS 32.602 [4]) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
This document defines NRM independent data types and methods.
This Solution Set specification is related to 3G TS 32.602 V8.1.X. |
32.604 | Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP) Common Management Information Protocol (CMIP) Solution Set (SS) | TS | 6.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.604/32604-610.zip | The present document specifies the Common Management Information Protocol (CMIP) Solution Set (SS) for the Basic CM Integration Reference Point (IRP): Information Service defined in TS 32.602 [6]. In detail:
• Clause 4 provides the basic concept of the CMIP SS and the mapping between the IOCs, operations and notifications defined in TS 32.602 (Basic Configuration Management IRP: Information Service) [6] to the corresponding CMIP SS equivalents.
• Clause 5 contains the GDMO definitions for the Basic Configuration Management IRP over the CMIP interfaces,
• Clause 6 contains the ASN.1 definitions supporting the GDMO definitions provided in clause 5.
This Solution Set specification is related to 3GPP TS 32.602 V6.1.X. |
32.611 | Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Requirements | TS | 6.1.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.611/32611-611.zip | |
32.612 | Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Information Service (IS) | TS | 6.5.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.612/32612-650.zip | |
32.613 | Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 6.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.613/32613-630.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.614 | Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Common Management Information Protocol (CMIP) Solution Set (SS) | TS | 6.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.614/32614-610.zip | The present document specifies the Common Management Information Protocol (CMIP) Solution Set (SS) for the Bulk CM Integration Reference Point (IRP): Information Service defined in TS 32.612 [4]. In detail:
• Clause 4 contains an introduction to some concepts that are the base for some specific aspects of the CMIP interfaces.
• Clause 5 contains the GDMO definitions for the Alarm Management over the CMIP interfaces
Clause 6 contains the ASN.1 definitions supporting the GDMO definitions provided in clause 5.
This Solution Set specification is related to 3GPP TS 32.612 V6.2.X. |
32.615 | Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): eXtensible Markup Language (XML) file format definition | TS | 6.3.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.615/32615-631.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 | 6.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.621/32621-600.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 | 6.7.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.622/32622-671.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.602 | Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP); Information Service (IS) | TS | 6.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.602/32602-610.zip | |
32.436 | Telecommunication management; Performance measurement: Abstract Syntax Notation 1 (ASN.1) file format definition | TS | 6.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.436/32436-610.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 | 6.6.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.623/32623-660.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.624 | Telecommunication management; Configuration Management (CM); Generic network resources: Integration Reference Point (IRP): Common Management Information Protocol (CMIP) Solution Set (SS) | TS | 6.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.624/32624-620.zip | The present document specifies the Common Management Information Protocol (CMIP) Solution Set (SS) for the Generic Network Resource Integration Reference Point (IRP): Network Resource Model defined in 3GPP TS 32.622 [4].
In detail:
• Clause 4 contains an introduction to some concepts that are the base for some specific aspects of the CMIP interfaces.
• Clause 5 contains the GDMO definitions for the Alarm Management over the CMIP interfaces
• Clause 6 contains the ASN.1 definitions supporting the GDMO definitions provided in clause 5.
This Solution Set specification is related to 3GPP TS 32.622 V6.4.X [4]. |
32.625 | Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP): Bulk CM eXtensible Markup Language (XML) file format definition | TS | 6.7.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.625/32625-670.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.633 | Telecommunication management; Configuration Management (CM); Core network resources Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 6.7.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.633/32633-670.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.632 | Telecommunication management; Configuration Management (CM); Core Network Resources Integration Reference Point (IRP); Network Resource Model (NRM) | TS | 6.6.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.632/32632-661.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.631 | Telecommunication management; Configuration Management (CM); Core network resources Integration Reference Point (IRP); Requirements | TS | 6.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.631/32631-600.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.634 | Telecommunication management; Configuration Management (CM); Core network resources Integration Reference Point (IRP): Common Management Information Protocol (CMIP) Solution Set (SS) | TS | 6.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.634/32634-620.zip | The present document specifies the Common Management Information Protocol (CMIP) Solution Set (SS) for the CN Network Resource Integration Reference Point (IRP): Network Resource Model defined in 3GPP TS 32.632 [4]. In detail:
• Clause 4 contains an introduction to some concepts that are the base for some specific aspects of the CMIP interfaces.
• Clause 5 contains the GDMO definitions for the Alarm Management over the CMIP interfaces
• Clause 6 contains the ASN.1 definitions supporting the GDMO definitions provided in clause 5.
This Solution Set specification is related to 3GPP TS 32.632 V6.2.X [4]. |
32.644 | Telecommunication management; Configuration Management (CM); UTRAN network resources Integration Reference Point (IRP): Common Management Information Protocol (CMIP) Solution Set (SS) | TS | 6.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.644/32644-630.zip | The present document specifies the Common Management Information Protocol (CMIP) Solution Set (SS) for the UTRAN Network Resource Integration Reference Point (IRP): Network Resource Model defined in 3GPP TS 32.642 [4].
In detail:
• Clause 4 contains an introduction to some concepts that are the base for some specific aspects of the CMIP interfaces.
• Clause 5 contains the GDMO definitions for the Alarm Management over the CMIP interfaces
• Clause 6 contains the ASN.1 definitions supporting the GDMO definitions provided in clause 5.
This Solution Set specification is related to 3GPP TS 32.642 V6.4.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 | 6.9.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.645/32645-690.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.651 | Telecommunication management; Configuration Management (CM); GERAN network resources Integration Reference Point (IRP); Requirements | TS | 6.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.651/32651-600.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 | 6.2.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.652/32652-621.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 | 6.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.653/32653-620.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.654 | Telecommunication management; Configuration Management (CM); GERAN network resources Integration Reference Point (IRP): Common Management Information Protocol (CMIP) Solution Set (SS) | TS | 6.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.654/32654-610.zip | The present document specifies the Common Management Information Protocol (CMIP) Solution Set (SS) for the GERAN Network Resource Integration Reference Point (IRP): Network Resource Model defined in 3GPP TS 32.652 [4]. In detail:
• Clause 4 contains an introduction to some concepts that are the base for some specific aspects of the CMIP interfaces.
• Clause 5 contains the GDMO definitions for the Alarm Management over the CMIP interfaces
• Clause 6 contains the ASN.1 definitions supporting the GDMO definitions provided in clause 5.
This Solution Set specification is related to 3GPP TS 32.652 V6.0.X. |
32.655 | Telecommunication management; Configuration Management (CM); GERAN network resources Integration Reference Point (IRP); Bulk CM eXtensible Markup Language (XML) file format definition | TS | 6.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.655/32655-620.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 | 6.2.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.661/32661-621.zip | |
32.662 | Telecommunication management; Configuration Management (CM); Kernel CM Information Service (IS) | TS | 6.7.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.662/32662-670.zip | |
32.663 | Telecommunication management; Configuration Management (CM); Kernel CM Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 6.7.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.663/32663-670.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.635 | Telecommunication management; Configuration Management (CM); Core network resources Integration Reference Point (IRP); Bulk CM eXtensible Markup Language (XML) file format definition | TS | 6.7.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.635/32635-670.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.642 | Telecommunication management; Configuration Management (CM); UTRAN network resources Integration Reference Point (IRP); Network Resource Model (NRM) | TS | 6.7.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.642/32642-670.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.643 | Telecommunication management; Configuration Management (CM); UTRAN network resources Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 6.8.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.643/32643-680.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.664 | Telecommunication management; Configuration Management (CM); Kernel CM Integration Reference Point (IRP); Common Management Information Protocol (CMIP) Solution Set (SS) | TS | 6.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.664/32664-620.zip | The present document specifies the Common Management Information Protocol (CMIP) Solution Set (SS) for the Kernel Configuration Management IRP: Information Service defined in 3GPP TS 32.662 [7]. In detail:
• Clause 4 contains an introduction to some concepts that are the base for some specific aspects of the CMIP interfaces.
• Clause 5 contains the GDMO definitions for the Kernel Configuration Management IRPover the CMIP interfaces
• Clause 6 contains the ASN.1 definitions supporting the GDMO definitions provided in clause 5.
This Solution Set specification is related to 3GPP TS 32.662 V6.3.X. |
32.672 | Telecommunication management; Configuration Management (CM); State Management Integration Reference Point (IRP); Information Service (IS) | TS | 6.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.672/32672-610.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.671 | Telecommunication management; Configuration Management (CM); State Management Integration Reference Point (IRP); Requirements | TS | 6.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.671/32671-600.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.641 | Telecommunication management; Configuration Management (CM); UTRAN network resources Integration Reference Point (IRP); Requirements | TS | 6.0.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.641/32641-601.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.691 | Telecommunication management; Inventory Management (IM) network resources Integration Reference Point (IRP): Requirements | TS | 6.0.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.691/32691-601.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.675 | Telecommunication management; Configuration Management (CM); State Management Integration Reference Point (IRP); Bulk CM eXtensible Markup Language (XML) file format definition | TS | 6.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.675/32675-620.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.690 | Telecommunication management; Inventory Management (IM); Requirements | TS | 6.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.690/32690-610.zip | |
32.692 | Telecommunication management; Inventory Management (IM) network resources Integration Reference Point (IRP); Network Resource Model (NRM) | TS | 6.4.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.692/32692-640.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.673 | Telecommunication management; Configuration Management (CM); State Management Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS) | TS | 6.4.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.673/32673-640.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.711 | Telecommunication management; Configuration Management (CM); Transport Network (TN) interface Network Resource Model (NRM) Integration Reference Point (IRP); Requirements | TS | 6.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.711/32711-600.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 | 6.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.695/32695-610.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.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 | 6.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.713/32713-630.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.714 | Telecommunication management; Configuration Management (CM); Transport Network (TN) Network Resource Model (NRM) Integration Reference Point (IRP); Common Management Information Protocol (CMIP) Solution Set (SS) | TS | 6.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.714/32714-600.zip | The purpose of this Transport Network (TN) interface Network Resource Model IRP: CMIP Solution Set is to define the mapping of the IRP information model (see 3GPP TS 32.712 [4]) to the protocol specific details necessary for implementation of this IRP in a Q3 environment.
This Solution Set specification is related to 3GPP TS 32.712 V6.0.X |
32.674 | Telecommunication management; Configuration Management (CM); State Management Integration Reference Point (IRP): Common Management Information Protocol (CMIP) Solution Set (SS) | TS | 6.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.674/32674-610.zip | The present document specifies the Common Management Information Protocol (CMIP) Solution Set (SS) for the State Management IRP: Information Service defined in 3GPP TS 32.672 [6]. In detail:
• Clause 4 contains an introduction to some concepts that are the base for some specific aspects of the CMIP interfaces.
• Clause 5 contains the GDMO definitions for the State Management IRP over the CMIP interfaces.
• Clause 6 contains the ASN.1 definitions supporting the GDMO definitions provided in clause 5.
This Solution Set is related to 3GPP TS 32.672 V6.0.X [6]. |
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 | 6.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.715/32715-620.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.712 | Telecommunication management; Configuration Management (CM); Transport Network (TN) interface Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) | TS | 6.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.712/32712-600.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.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 | 6.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.745/32745-630.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.744 | Telecommunication management; Configuration Management (CM); Signalling Transport Network (STN) interface Network Resource Model (NRM) Integration Reference Point (IRP): Common Management Information Protocol (CMIP) Solution Set (SS) | TS | 6.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.744/32744-610.zip | The purpose of this STN Network Resources IRP: CMIP Solution Set is to define the mapping of the IRP information model (see 3GPP TS 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 V6.0.X. |
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 | 6.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.743/32743-630.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.803 | Telecommunication management; Process guide; Use cases in Unified Modelling Language (UML) | TR | 6.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.803/32803-600.zip | The present document is a guide for developing subscription management requirements in the form of use cases.
The present document is used to allow use case process information to be removed from 3GPP TS 32.140 on "Telecommunication management; Subscription Management (SuM) Requirements". It is intended that this applies only to the Subscription Management (SuM) work item in Release 6. |
32.742 | Telecommunication management; Configuration Management (CM); Signalling Transport Network (STN) interface Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) | TS | 6.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.742/32742-630.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.741 | Telecommunication management; Configuration Management (CM); Signalling Transport Network (STN) interface Network Resource Model (NRM) Integration Reference Point (IRP); Requirements | TS | 6.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.741/32741-600.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.815 | Telecommunication management; Charging management; Online Charging System (OCS) architecture study | TR | 6.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.815/32815-610.zip | The present document analyses the architectures and functions of the OCS and thereby derives the functionality of the OCS reference points. It is expected that the content of the present document will serve as a basis for detailed 3GPP specifications of reference points between the logical OCS functionalities. The functionality of the OCS, as described in the present document, applies to all charging domains (bearer, session and service). |
33.102 | 3G security; Security architecture | TS | 6.5.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.102/33102-650.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.105 | 3G Security; Cryptographic algorithm requirements | TS | 6.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.105/33105-600.zip | |
32.805 | Telecommunication management; Process guide; Backward compatibility recommendations | TR | 6.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.805/32805-600.zip | The present document gives recommendations to develop future IRP specifications in a Backward Compatible (BC) way so that the group of IRPManager(s) and IRPAgent(s) are not forced to be upgraded in lock step.
The business case for supporting such group, as described above, is complex. It may not relate to the functions of the supported IRPs alone. Rather, it can relate to the cost of coordination of IRPVersion upgrades, the cost of maintaining an old IRPVersion and the cost of using single-vendor or multi-vendor IRPAgents. These considerations are operator deployment scenarios specific.
Clause 2 provides the list of references. Clause 3 provides the definitions and abbreviations used in the document. Clause 4 specifies the Recommendations. Clause 5 describes the system context where the Recommendations are applicable. |
33.108 | 3G security; Handover interface for Lawful Interception (LI) | TS | 6.10.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.108/33108-6a0.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). |
32.804 | Telecommunication management; Control of Remote Electrical Tilting (RET) antennas; Requirements | TR | 6.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/32_series/32.804/32804-620.zip | The present document defines the requirements for the network wide control of RET antennas via the Itf-N.
Two example types of RET antennas are those that are tilted using a mechanical tilting mechanism and those that use a phased array.
The control of RET antennas has been studied in 3GPP RAN3 with an approved work item for “Remote Control of Electrical Tilting Antennas” provided in RP-030193 at RAN#19 in March 2003, producing TR 25.802 [1].
The RET control mechanism makes use of the Iuant interface, which is defined in the following set of specifications for General Aspects and Principles [8], Layer 1 [9], Signalling Transport [10], and Remote Electrical Tilting (RET) Antennas Application Part (RETAP) Signalling [11].
The ability to control Antenna tilt permits cell size to be adjusted, thereby permitting control of up and downlink throughput.
The ability to control Antenna tilts remotely from a network management system permits a network wide perspective to be obtained and for settings to be adjusted in response to predicted population movements, or in response to performance monitoring data to help make the best use of the available radio access network.
Figure 1 shows the main Network Elements (NEs) and depicts the two system contexts A and B where the IRPagent may be located either in the Element Manager (EM), or within the Network Element (NE).
Figure 1 |
33.141 | Presence service; Security | TS | 6.2.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.141/33141-620.zip | |
33.106 | 3G security; Lawful interception requirements | TS | 6.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.106/33106-610.zip | |
33.107 | 3G security; Lawful interception architecture and functions | TS | 6.6.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.107/33107-660.zip | |
33.210 | Network Domain Security (NDS); IP network layer security | TS | 6.6.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.210/33210-660.zip | |
33.222 | Generic Authentication Architecture (GAA); Access to network application functions using Hypertext Transfer Protocol over Transport Layer Security (HTTPS) | TS | 6.6.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.222/33222-660.zip | |
33.200 | 3G Security; Network Domain Security (NDS); Mobile Application Part (MAP) application layer security | TS | 6.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.200/33200-610.zip | This technical specification covers the security mechanisms and procedures necessary to protect the MAP protocol. The complete set of enhancements and extensions to facilitate security protection for the MAP protocol is termed MAPsec and it covers transport security in the MAP protocol itself and the security management procedures.
The security mechanisms specified for MAP are on the application layer. This means that MAPsec is independent of the network and transport protocols to be used.
This technical specification contains the stage-2 specification for security protection of the MAP protocol. The actual implementation (stage-3) specification can be found in the MAP stage-3 specification, TS 29.002 [4].
NOTE: It is explicitly noted that automated key management and key distribution is not part of Rel‑5. All key management and key distribution in Rel‑5 shall therefore be carried out by other means (see Annex A). |
33.234 | 3G security; Wireless Local Area Network (WLAN) interworking security | TS | 6.9.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.234/33234-690.zip | |
33.220 | Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture (GBA) | TS | 6.13.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.220/33220-6d0.zip | |
33.203 | 3G security; Access security for IP-based services | TS | 6.11.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.203/33203-6b0.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.310 | Network Domain Security (NDS); Authentication Framework (AF) | TS | 6.2.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.310/33310-620.zip | |
33.246 | 3G Security; Security of Multimedia Broadcast/Multicast Service (MBMS) | TS | 6.12.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.246/33246-6c0.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.817 | Feasibility study on (Universal) Subscriber Interface Module (U)SIM security reuse by peripheral devices on local interfaces | TR | 6.1.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.817/33817-610.zip | This Feasibility Study report conducts a threat analysis and determines the feasibility of Reuse of a Single SIM, USIM, or ISIM by peripheral devices on local interfaces to access multiple networks. Most important for this Reuse is the authentication and key agreement (AKA) function provided by these applications. The peripheral devices include 3GPP and WLAN devices that function as integrated or attachable peripherals on Laptops or PDAs or other mobile data devices. The multiple access networks of interest correspondingly include 3GPP and WLAN type networks. The objective of this study is to realize the diverse usage models with multiple external (wired or wireless) interfaces from a security point of view, without incorporating significant changes to the 3GPP and WLAN infrastructure. It also studies the impact on current security specifications for 3GPP, especially given that some issues have already been identified surrounding key setting procedures, USIM sequence number synchronization, UICC presence detection/UICC application presence detection and termination of the UICC usage etc. It also studies additional user authentication requirements (e.g. PINs) when used over local interfaces like Bluetooth, IR or USB. Further more it studies the impact on having many entities using the same security mechanism and any 3GPP core network elements. Reuse of security functions provided by applications on the UICC does not have an impact on ownership and control of the UICC, which remains with the issuer of the UICC. This Feasibility Study may be used as a basis for future CRs to TS 33.234 as and when any of the proposals are developed by SA WG3. |
33.810 | 3G Security; Network Domain Security / Authentication Framework (NDS/AF); Feasibility Study to support NDS/IP evolution | TR | 6.0.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.810/33810-600.zip | The scope of this feasibility study is limited to authentication of network elements which are using NDS/IP, and located in the inter-operator domain.
It means that this study concentrates on authentication of Security Gateways (SEG), and the corresponding Za‑interfaces. Authentication of elements in the intra-operator domain is considered as an internal issue for the operators. This is quite much in line with [6] which states that only Za is mandatory, and that the security domain operator can decide if the Zb-interface is deployed or not, as the Zb-interface is optional for implementation.
However, NDS/AF can easily be adapted to intra-operator use. This is just a simplification of the inter-operator case as all NDS/IP NEs and the PKI infrastructure belong to the same operator. Validity of certificates may be restricted to the operator's domain.
This work might also later be extended to provide entity authentication services to non-control plane nodes, but this has not been studied.
Possible use of multi-purpose PKI solutions (e.g. providing end-user security) for NDS/AF has not been studied. On the contrary, it is recommended to use a dedicated and profiled PKI for NE authentication in NDS/IP. Different applications make different demands on a PKI and it may make sense to build a lightweight PKI for each purpose rather than to build one that solves all problems. Complexity is one of the main impediments to PKI deployment today [11].
The NDS architecture for IP-based protocols is illustrated in figure 1.
Figure 1: NDS architecture for IP-based protocols [6] |
33.221 | Generic Authentication Architecture (GAA); Support for subscriber certificates | TS | 6.4.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.221/33221-640.zip | |
34.108 | Common test environments for User Equipment (UE); Conformance testing | TS | 6.6.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.108/34108-660.zip | The present document contains definitions of reference conditions and test signals, default parameters, reference radio bearer configurations used in radio bearer interoperability testing, common radio bearer configurations for other test purposes, common requirements for test equipment and generic set-up procedures for use in UE conformance tests. |
34.109 | Terminal logical test interface; Special conformance testing functions | TS | 6.4.0 | R2 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.109/34109-640.zip | |
33.978 | Security aspects of early IP Multimedia Subsystem (IMS) | TR | 6.6.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.978/33978-660.zip | The present document documents an interim security solution for early IMS implementations that are not fully compliant with the IMS security architecture specified in TS 33.203 [2]. For security reasons, the provisions in this TR only apply to IMS procedures used over the 3GPP PS domain. |
33.919 | 3G Security; Generic Authentication Architecture (GAA); System description | TR | 6.2.0 | S3 | https://www.3gpp.org/ftp/Specs/archive/33_series/33.919/33919-620.zip | |
34.123-1 | User Equipment (UE) conformance specification; Part 1: Protocol conformance specification | TS | 6.7.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.123-1/34123-1-670.zip | The present document specifies the protocol conformance testing for the 3rd Generation User Equipment (UE).
This is the first part of a multi-part test specification. The following information can be found in this part:
- the overall test structure;
- the test configurations;
- the conformance requirement and reference to the core specifications;
- the test purposes; and
- the description of the tests’ procedures, the specific test requirements and the messages exchanged.
The following information relevant to the tests described in the present document can be found in accompanying specifications:
- the default setting of the test parameters [9];
- the applicability of each test case and the Implementation Conformance Statement (ICS) pro-forma [11].
Note: The present document does not contain any tests on the USIM, or the interface between the UE and the USIM. These tests are documented elsewhere.
The present document is valid for UE implemented according to 3GPP releases starting from Release 1999 up to the Release indicated on the cover page of the present document. |
34.122 | Terminal conformance specification; Radio transmission and reception (TDD) | TS | 6.0.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.122/34122-600.zip | This present document specifies the measurement procedure for the conformance test of the mobile station that contain transmitting characteristics, receiving characteristics and performance requirements in addition to requirements for support of RRM (Radio Resource Management) in both UTRATDD modes. The two options are the 3,84 Mcps TDD Option and 1,28 Mcps TDD Option, respectively.
The requirements are listed in different clauses only if the corresponding parameters deviate. More generally, tests are only applicable to those mobiles that are intended to support the appropriate functionality. To indicate the circumstances in which tests apply, this is noted in the “definition and applicability” part of the test.
For example only release 5 and later UE declared to support HSDPA shall be tested for this functionality. In the event that for some tests different conditions apply for different releases, this is indicated within the text of the test itself. |
34.123-2 | User Equipment (UE) conformance specification; Part 2: Implementation conformance statement (ICS) proforma specification | TS | 6.7.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.123-2/34123-2-670.zip | The present document provides the Implementation Conformance Statement (ICS) proforma for 3rd Generation User Equipment (UE), in compliance with the relevant requirements, and in accordance with the relevant guidance given in ISO/IEC 9646-7 [2] and ETS 300 406 [3].
The present document also specifies a recommended applicability statement for the test cases included in TS 34.123-1. These applicability statements are based on the features implemented in the UE.
Special conformance testing functions can be found in 3GPP TS 34.109 [45] and the common test environments are included in 3GPP TS 34.108 [44].
The present document is valid for UE implemented according to 3GPP releases starting from Release 1999 up to the Release indicated on the cover page of the present document. |
34.124 | Electromagnetic compatibility (EMC) requirements for mobile terminals and ancillary equipment | TS | 6.2.0 | R4 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.124/34124-620.zip | |
34.171 | Terminal conformance specification; Assisted Global Positioning System (A-GPS); Frequency Division Duplex (FDD) | TS | 6.6.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.171/34171-660.zip | The present document specifies the measurement procedures for the conformance test of the minimum performance requirements for FDD mode of UTRA user equipment (UE) where the only Assisted Global Navigation Satellite System (A-GNSS) supported is Assisted Global Positioning System (A-GPS) L1 C/A. The procedures for UEs that support other or additional A-GNSSs are specified in 3GPP TS 34.172 [18].
Tests are only applicable to those mobiles that are intended to support the appropriate functionality. To indicate the circumstances in which tests apply, this is noted in the "definition and applicability" part of the test. |
34.229-2 | Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); User Equipment (UE) conformance specification; Part 2: Implementation Conformance Statement (ICS) specification | TS | 6.4.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.229-2/34229-2-640.zip | |
34.121 | Terminal conformance specification, Radio transmission and reception (FDD) | TS | 6.4.0 | R5 | https://www.3gpp.org/ftp/Specs/archive/34_series/34.121/34121-640.zip | The present document specifies the measurement procedures for the conformance test of the user equipment (UE) that contain transmitting characteristics, receiving characteristics and performance requirements in addition to requirements for support of RRM (Radio Resource Management) in FDD mode.
The requirements are listed in different clauses only if the corresponding parameters deviate. More generally, tests are only applicable to those mobiles that are intended to support the appropriate functionality. To indicate the circumstances in which tests apply, this is noted in the “definition and applicability” part of the test.
For example only Release 5 and later UE declared to support HSDPA shall be tested for this functionality. In the event that for some tests different conditions apply for different releases, this is indicated within the text of the test itself. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.