id
stringlengths 4
12
| title
stringlengths 8
250
| type
stringclasses 2
values | version
stringclasses 612
values | working_group
stringclasses 30
values | url
stringlengths 65
81
| scope
stringlengths 0
65.7k
|
|---|---|---|---|---|---|---|
28.627 | Telecommunication management; Self-Organizing Networks (SON) Policy Network Resource Model (NRM) Integration Reference Point (IRP); Requirements | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.627/28627-i00.zip | The present document describes concept and requirements of SON Policy management for Self-Optimization and SON coordination. |
28.628 | Telecommunication management; Self-Organizing Networks (SON) Policy Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.628/28628-i00.zip | The present document is part of an Integration Reference Point (IRP) named Self Organizing Networks (SON) Policy Network Resource Model (NRM) IRP, through which an IRPAgent can communicate management information to one or several IRPManagers concerning SON policies. The SON policy 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 SON policy NRM IRP: Information Service (IS).
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 [11]). However, which Interface IRP is applicable is outside the scope of the present document.
The present document also contains stage 2 descriptions for those functionalities for the Self-Optimization OAM, SON coordination and Energy Saving Management. |
28.629 | Telecommunication management; Self-Organizing Networks (SON) Policy Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 18.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.629/28629-i10.zip | The present document specifies the Solution Set definitions for the IRP whose semantics is specified in 3GPP TS 28.628 [4] SON Policy Network Resource Model IRP: Information Service (IS). |
28.631 | Telecommunication management; Inventory Management (IM) Network Resource Model (NRM) Integration Reference Point (IRP); Requirements | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.631/28631-i00.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 (IM )Network Resource Model (NRM) IRP. |
28.632 | Telecommunication management; Inventory Management (IM) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.632/28632-i00.zip | The present document specifies the Inventory Management (IM) Network Resource Model (NRM) that can be communicated between an IRPAgent and an IRPManager for telecommunication network management purposes, including management of converged networks.
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. |
28.633 | Telecommunication management; Inventory Management (IM) Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 18.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.633/28633-i10.zip | The present document provides the NRM-specific part related to the Inventory Management NRM IRP IS in 3GPP TS 28.632 [1] of solution set definitions. |
28.651 | Telecommunication management; Universal Terrestrial Radio Access Network (UTRAN) Network Resource Model (NRM) Integration Reference Point (IRP); Requirements | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.651/28651-i00.zip | The present document defines, in addition to the requirements defined in [1], [2] and [3], the requirements for the present IRP: Universal Terrestrial Radio Access Network (UTRAN) Network Resource Model (NRM). |
28.652 | Telecommunication management; Universal Terrestrial Radio Access Network (UTRAN) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.652/28652-i00.zip | The present document specifies the UTRAN Network Resource Model (NRM) that can be communicated between an IRPAgent and an IRPManager for telecommunication network management purposes, including management of converged networks.
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. |
28.653 | Telecommunication management; Universal Terrestrial Radio Access Network (UTRAN) Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 18.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.653/28653-i10.zip | The present document specifies the Solution Sets for the UTRAN NRM IRP. |
28.654 | Telecommunication management; GSM/EDGE Radio Access Network (GERAN) Network Resource Model (NRM) Integration Reference Point (IRP); Requirements | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.654/28654-i00.zip | The present document defines, in addition to the requirements defined in [1], [2] and [3], the requirements for the present IRP: GERAN Network Resource Model (NRM) Integration Reference Point (IRP). |
28.655 | Telecommunication management; GSM/EDGE Radio Access Network (GERAN) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.655/28655-i00.zip | The present document specifies the GERAN Network Resource Model (NRM) that can be communicated between an IRPAgent and IRPManagers for telecommunication network management purposes, including management of converged networks.
This document specifies the semantics and behaviour of class attributes and relations visible across the reference point in a protocol and technology neutral way. It does not define their syntax and encoding. |
28.656 | Telecommunication management; GSM/EDGE Radio Access Network (GERAN) Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 18.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.656/28656-i20.zip | The present document is part of an Integration Reference Point (IRP) named GERAN Network Resource Model (NRM) IRP, through which an IRPAgent can communicate configuration management information to one or several IRPManagers concerning GERAN resources. The GERAN NRM IRP comprises a set of specifications defining Requirements, a protocol neutral Information Service and one or more Solution Set definitions.
The present document specifies the Solution Set definitions for the GERAN NRM IRP. |
28.657 | Telecommunication management; Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Network Resource Model (NRM) Integration Reference Point (IRP); Requirements | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.657/28657-i00.zip | |
28.658 | Telecommunication management; Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) | TS | 18.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.658/28658-i10.zip | |
28.659 | Telecommunication management; Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 18.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.659/28659-i10.zip | |
28.661 | Telecommunication management; Generic Radio Access Network (RAN) Network Resource Model (NRM) Integration Reference Point (IRP); Requirements | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.661/28661-i00.zip | The present document defines, in addition to the requirements defined in 3GPP TS 32.101 [2], 3GPP TS 32.102 [3] and 3GPP TS 32.600 [4], the Requirements for the common and generic radio access network equipments that may be shared between BSS in GSM, UTRAN and E‑UTRAN.
The present document can be used also for managing the equipment that can be shared by several RATs, even in the cases when it is not being shared. |
28.662 | Telecommunication management; Generic Radio Access Network (RAN) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) | TS | 18.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.662/28662-i10.zip | |
28.663 | Telecommunication management; Generic Radio Access Network (RAN) Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 18.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.663/28663-i20.zip | The present document is part of an Integration Reference Point (IRP) named Generic Radio Access Network (RAN) Network Resource Model (NRM) IRP, through which an IRPAgent can communicate configuration management information to one or several IRPManagers concerning Generic RAN resources. The Generic RAN NRM IRP comprises a set of specifications defining Requirements, a protocol neutral Information Service and one or more Solution Set(s).
The present document specifies the Solution Sets for the Generic RAN NRM IRP. |
28.667 | Telecommunication management; Radio Planning Tool Access (RPTA) Integration Reference Point (IRP); Requirements | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.667/28667-i00.zip | The present document specifies the requirements of the Radio Planning Tool Access (RPTA) Integration Reference Point (IRP). This IRP allows to read site and antenna data from RPTs. |
28.668 | Telecommunication management; Radio Planning Tool Access (RPTA) Integration Reference Point (IRP); Information Service (IS) | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.668/28668-i00.zip | The present document specifies the Radio Planning Tool Access (RPTA) management operations as well as support object classes, attributes and relations that can be communicated between the Service Provider in the RPT and one or several Service Consumers in the NM.
This document specifies the semantics and behaviour of management operations, support object classes, attributes and relations visible across the reference point in a protocol and technology neutral way. It does not define their syntax and encoding.
This IRP allows the NM to read planned site and antenna data from the RPT. |
28.669 | Telecommunication management; Radio Planning Tool Access (RPTA) Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.669/28669-i00.zip | The present document specifies the Solution Set definitions (SS) of the Radio Planning Tool Access (RPTA) Integration Reference Point (IRP). This IRP allows the NM to read planned site and antenna data from the RPT.
This Solution Set specification is related to 3GPP TS 28.668 V14.0.X [4]. |
28.671 | Telecommunication management; Home Node B (HNB) Subsystem (HNS) Network Resource Model (NRM) Integration Reference Point (IRP); Requirements | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.671/28671-i00.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. |
28.672 | Telecommunication management; Home Node B (HNB) Subsystem (HNS) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.672/28672-i00.zip | The present document specifies the Home Node B Subsystem (HNS) Network Resource Model (NRM) IRP (that can be communicated between an IRPAgent and an IRPManager for telecommunication network management purposes, including management of converged networks.
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.
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. |
28.673 | Telecommunication management; Home Node B (HNB) Subsystem (HNS) Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 18.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.673/28673-i10.zip | The present document is part of an Integration Reference Point (IRP) named HNS Network Resource Model (NRM) IRP, through which an IRPAgent can communicate configuration management information to one or several IRPManagers concerning HNS resources. The HNS NRM IRP comprises a set of specifications defining Requirements, a protocol neutral Information Service and one or more Solution Set(s).
The present document specifies the Solution Sets for the HNS NRM IRP, see 3GPP TS 28.672 [5]. |
28.674 | Telecommunication management; Home enhanced Node B (HeNB) Subsystem (HeNS) Network Resource Model (NRM) Integration Reference Point (IRP); Requirements | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.674/28674-i00.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. |
28.675 | Telecommunication management; Home enhanced Node B (HeNB) Subsystem (HeNS) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.675/28675-i00.zip | The present document specifies the Home enhanced Node B (HeNB) Subsystem (HeNS) Network Resource Model (NRM) IRP that can be communicated between an IRPAgent and an IRPManager for telecommunication network management purposes, including management of converged networks.
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.
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. |
28.676 | Telecommunication management; Home enhanced Node B (HeNB) Subsystem (HeNS) Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 18.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.676/28676-i10.zip | The present document is part of an Integration Reference Point (IRP) named HeNS Network Resource Model (NRM) IRP, through which an IRPAgent can communicate configuration management information to one or several IRPManagers concerning HeNS resources. The HeNS NRM IRP comprises a set of specifications defining Requirements, a protocol neutral Information Service and one or more Solution Set(s).
The present document specifies the Solution Sets for the HeNS NRM IRP, see 3GPP TS 28.675 [2]. |
28.680 | Telecommunication management; Wireless Local Area Network (WLAN) management; Concepts and requirements | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.680/28680-i00.zip | The present document describes the concepts and requirements of WLAN management that focus on WLAN performance monitoring and alarm notifications. |
28.681 | Telecommunication management; Wireless Local Area Network (WLAN) Network Resource Model (NRM) Integration Reference Point (IRP); Requirements | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.681/28681-i00.zip | The present document describes the NRM IRP requirements of WLAN management. |
28.682 | Telecommunication management; Wireless Local Area Network (WLAN) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.682/28682-i00.zip | The present document is part of an Integration Reference Point (IRP) named Wireless Local Area Networks (WLAN) Management Network Resource Model (NRM) IRP, through which an IRPAgent can communicate management information to one or several IRPManagers concerning WLAN management. The WLAN management 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 WLAN management NRM IRP: Information Service (IS).
The present document also contains stage 2 descriptions for those functionalities for the WLAN Management. |
28.683 | Telecommunication management; Wireless Local Area Network (WLAN) Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.683/28683-i00.zip | The present document is part of an Integration Reference Point (IRP) named Wireless Local Area Network (WLAN) Management Network Resource Model (NRM) IRP, through which an IRPAgent can communicate management information to one or several IRPManagers concerning WLAN management. The WLAN management NRM IRP comprises a set of specifications defining Requirements, a protocol neutral Information Service and one or more Solution Set(s).
The present document specifies the Solution Sets for the WLAN NRM IRP. |
28.701 | Telecommunication management; Core Network (CN) Network Resource Model (NRM) Integration Reference Point (IRP); Requirements | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.701/28701-i00.zip | The present document defines, in addition to the requirements defined in [1], [2] and [3], the requirements for the present IRP: Core Network Network Resource Model IRP. |
28.702 | Telecommunication management; Core Network (CN) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) | TS | 18.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.702/28702-i20.zip | The present document is part of an Integration Reference Point (IRP) named "Core Network 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 CN resources.
The present document specifies the protocol neutral Core Network NRM IRP; Information Service. It reuses relevant parts of the generic NRM in 3GPP TS 28.622 [9], 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.602 [10]. However, which Interface IRP that is applicable is outside the scope of the present document. |
28.703 | Telecommunication management; Core Network (CN) Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 18.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.703/28703-i10.zip | The purpose of the present document is to define the mapping of the IRP information model (see TS 28.702 [3]) to the protocol specific details necessary for implementation of this IRP in a specific solution set environment.
This Solution Set specification is related to 3GPP TS 28.702. |
28.704 | Telecommunication management; IP Multimedia Subsystem (IMS) Network Resource Model (NRM) Integration Reference Point (IRP); Requirements | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.704/28704-i00.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. |
28.705 | Telecommunication management; IP Multimedia Subsystem (IMS) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.705/28705-i00.zip | The present document specifies the IP Multimedia Subsystem (IMS) network resource information that can be communicated between an IRPAgent and an IRPManager for telecommunication network management purposes, including management of converged networks.
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.
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 28.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. |
28.706 | Telecommunication management; IP Multimedia Subsystem (IMS) Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 18.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.706/28706-i10.zip | The present document specifies the Solution Sets for the IMS NRM IRP.
The Solution Set definition is related to 3GPP TS 28.705[3]. |
28.707 | Telecommunication management; Evolved Packet Core (EPC) Network Resource Model (NRM) Integration Reference Point (IRP); Requirements | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.707/28707-i00.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. |
28.708 | Telecommunication management; Evolved Packet Core (EPC) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) | TS | 18.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.708/28708-i10.zip | |
28.709 | Telecommunication management; Evolved Packet Core (EPC) Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 18.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.709/28709-i10.zip | |
28.731 | Telecommunication management; Transport Network (TN) interface Network Resource Model (NRM) Integration Reference Point (IRP); Requirements | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.731/28731-i00.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). |
28.732 | Telecommunication management; Transport Network (TN) interface Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) | TS | 18.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.732/28732-i20.zip | The present document specifies the Transport Network (TN) interface Network Resource Model (NRM) that can be communicated between an IRPAgent and an IRPManager for telecommunication network management purposes, including management of converged networks.
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.
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:
- Specifies the protocol neutral Transport Network (TN) interface Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS). It reuses relevant parts of the generic NRM in TS 28.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 28.625 [16]), all NRM's of one release shall support the same State Management IRP version.
This specification is related to 3GPP TS 28.625 [16]. |
28.733 | Telecommunication management; Transport Network (TN) interface Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 18.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.733/28733-i20.zip | The present document is part of an Integration Reference Point (IRP) named Transport Network (TN) interface Network Resource Model (NRM) IRP, through which an IRPAgent can communicate configuration management information to one or several IRPManagers concerning TN resources. The TN NRM IRP comprises a set of specifications defining Requirements, a protocol neutral Information Service and one or more Solution Set(s).
The present document specifies the Solution Sets for the TN NRM IRP. |
28.734 | Telecommunication management; Signalling Transport Network (STN) interface Network Resource Model (NRM) Integration Reference Point (IRP); Requirements | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.734/28734-i00.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. |
28.735 | Telecommunication management; Signalling Transport Network (STN) interface Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.735/28735-i00.zip | The present document is part of an Integration Reference Point (IRP) named "Signalling Transport Network (STN) interface 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 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 interface NRM IRP. It reuses relevant parts of the generic NRM in TS 28.622 [6], either by direct reuse or sub-classing, and in addition to that defines Signalling Transport specific Managed Object Classes.
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 28.625 [3]), all NRMs of one release shall support the same State Management IRP version. |
28.736 | Telecommunication management; Signalling Transport Network (STN) interface Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 18.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.736/28736-i10.zip | The present document is part of an Integration Reference Point (IRP) named Signalling Transport Network (STN) interface Network Resource Model (NRM) IRP, through which an IRPAgent can communicate configuration management information to one or several IRPManagers concerning STN interface resources. The STN interface NRM IRP comprises a set of specifications defining Requirements, a protocol neutral Information Service and one or more Solution Set(s).
The present document specifies the Solution Sets for the STN interface NRM IRP.
This Solution Set definition is related to 3GPP TS 28.735 [9]. |
28.751 | Telecommunication management; Subscription Management (SuM) Network Resource Model (NRM) Integration Reference Point (IRP); Requirements | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.751/28751-i00.zip | The present document defines, in addition to the requirements defined in [1], [2], [3] and [4], requirements for the present IRP: SuM NRM IRP. |
28.752 | Telecommunication management; Subscription Management (SuM) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.752/28752-i00.zip | The present document defines the Network Resource Model (NRM) for the SuM IRP which can be communicated between an IRPAgent and IRPManagers for subscription management purposes, including in the context of converged networks. |
28.753 | Telecommunication management; Subscription Management (SuM) Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 18.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.753/28753-i20.zip | The present document is part of an Integration Reference Point (IRP) named Subscription Management (SuM) Network Resource Model (NRM) IRP, through which an IRPAgent can communicate configuration management information to one or several IRPManagers concerning SuM resources. The SuM NRM IRP comprises a set of specifications defining Requirements, a protocol neutral Information Service and one or more Solution Set(s).
The present document specifies the Solution Sets for the SuM NRM IRP. |
28.819 | Study on continuous integration continuous delivery support for 3GPP NFs | TR | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.819/28819-i00.zip | The present document studies key issues in automating CI-CD based testing of 3GPP NFs after delivery to the operator's operation environment. The present document describes the support the 3GPP system provides for CI-CD and other testing such as:
1) Support for operational and simulation testing
2) Information relating to NFs required for testing
3) Feedback on the new NF's performance |
28.824 | Study on network slice management capability exposure | TR | 18.0.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.824/28824-i01.zip | The present document describes use cases, potential requirements and solutions for exposure of management services to external network slice consumers, e.g. verticals and service providers. The present document provides conclusions and recommendations on the next steps for the standardization. |
28.826 | Study on Nchf charging services phase 2 improvements and optimizations | TR | 18.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.826/28826-i10.zip | The present document studies the potential use cases, requirements, and solutions for the enhancements of the Nchf converge charging service.
The study will cover and identify gaps for:
- optimizations regarding amount of information in the request and number of requests;
- enhancement of input to rating;
- cancelling of chargeable events for unsuccessful scenarios;
- enhancement of non-blocking mechanism;
- enhancements of triggers having more consistent triggers and use of NF specific triggers.
Improvements on how to maintain the source code presentations (yaml and ASN.1) the document structure for these will be studied, |
28.827 | Study on 5G charging for additional roaming scenarios and actors | TR | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.827/28827-i00.zip | The present document studies the potential use cases, requirements, and solutions for the 5G charging for additional roaming scenarios and actors, in regards to roaming local break out and home routed and taking the requirements brought by adoption of GSMA BCE (Billing Charging Evolution), as a replacement for TAP.
The study will cover and identify gaps for:
- charging in the visited MNO network for the purpose of wholesale charging towards the home MNO
- capabilities for reconciliation of wholesale charging reports from the visited MNO network with MNO home network information
- charging in the visited MNO network and convey it to the home MNO network for the purpose of retail charging
- charging in the MNO’s network for the purpose of wholesale charging towards an additional charging model actor e.g. MVNO
- charging in the visited MNO network and convey it to the home MNO’s network for the purpose of home MNO wholesale charging towards an additional charging model actor e.g. MVNO
- charging in the visited MNO network and convey it to an MVNO hosted by a home MNO for the purpose of retail charging |
28.828 | Study on charging aspects for enhanced support of non-public networks | TR | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.828/28828-i00.zip | The present document studies the charging aspects for enhanced support of non-public networks on the TS 23.501 [2], TS 23.502 [3], TS 23.503 [4], TS 23.228 [5] and TS 23.167 [6] incorporating conclusions from TR 23.734 [7] and TR 23.700-07 [8].
The following is studied:
- Charging scenarios and potential charging requirements for Non-Public Networks (i.e. Stand-alone Non-Public Network (SNPN) or Public Network Integrated NPN (PNI-NPN)).
- Possible charging solutions for Non-Public Networks with potential impact on charging architecture, charging functions and charging procedures.
- End user charging and Inter-Provider charging by considering the different business roles. |
28.829 | Study on network and service operations for energy utilities | TR | 18.0.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.829/28829-i01.zip | The present document considers service requirements introduced by the SEI work item related to telecom management [2] and [3]. This feasibility study identifies use cases and requirements for exposing capabilities of the 3GPP management system to external energy utility service providers. The study further considers how management capabilities or what information can be provided to MNOs by the external energy utility service providers. The study will consider both energy utility use cases and requirements. The study of FS_NSCE [4] can be considered for the technical investigation. |
28.830 | Study on Fault Supervision Evolution | TR | 18.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.830/28830-i10.zip | The present document investigates potential use cases, requirements and solutions for the fault supervision evolution, its relation with performance management and fault supervision, relation and interaction with MDAS and COSLA, and potential enhancements for MDA assisted fault management. The present document provides conclusions and recommendations on the normative work. |
28.831 | Study on basic Service-Based Management Architecture (SBMA) enabler enhancements | TR | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.831/28831-i00.zip | The present document … |
28.832 | Study on management aspects of Ultra-Reliable and Low Latency Communications (URLLC) | TR | 18.0.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.832/28832-i01.zip | The present document investigates the potential requirements related to management of the URLLC features defined in RAN side. It documents key issues related to configuration management of URLLC features and to the performance measurements for URLLC service. It provides potential solutions and recommendations for the normative work. |
28.833 | Study on management aspects of 5GLAN | TR | 18.0.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.833/28833-i01.zip | The present document studies the potential use cases, requirements, and enhancements for the management (e.g. performance measurement and related new KPIs regarding VN group communication) to support 5G-LAN capabilities defined by TS 23.501 [2]. The present document provides conclusions and recommendations on standardization phase. |
28.834 | Study on management of cloud-native Virtualized Network Functions (VNF) | TR | 18.0.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.834/28834-i01.zip | The present document studies potential use cases, requirements and solutions for the management of cloud-native virtualized network function and the impacts on the 3GPP management system. The present document provides conclusions and recommendations on the next steps in the standardization. |
28.835 | Study on management aspects of 5G Multiple Operator Core Network (MOCN) network sharing phase 2 | TR | 18.0.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.835/28835-i01.zip | The present document studies on potential requirements, impact on interaction between MOP and POP/NEP, and management architecture and more potential performance measurements of 5G MOCN network sharing. |
28.836 | Study on intent-driven management for network slicing | TR | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.836/28836-i00.zip | The present document specifies potential use cases, requirements, and solutions for intent driven management for network slicing. The document provides conclusions and recommendations on the next steps in the standardization. |
28.837 | Study on management of trace/ Minimization of Drive Tests (MDT) phase 2 | TR | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.837/28837-i00.zip | The present document studies potential enhancements for the management of Trace/MDT based on the existing 5G data collection job "TraceJob" specified in TS 28.621 (stage 1) [2], TS 28.622 (stage 2) [3], TS 28.623 (stage 3) [4] and the Trace/MDT management framework specified in TS 32.421 (stage 1) [5], TS 32.422 (stage 2) [6] and TS 32.423 (stage 3) [7]. The document provides conclusions and recommendations on the next steps in the standardization. |
28.838 | Study on measurement data collection to support RAN intelligence | TR | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.838/28838-i00.zip | The present document contains the concept, use cases, requirements, and potential solutions for collecting the measurement data to support AI/ML enabled RAN with the AI/ML functions residing in OAM. |
28.839 | Study on charging aspects for time sensitive networking | TR | 18.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.839/28839-i10.zip | The present document studies the charging aspects for the support of Time Sensitive Networking based on requirements from TS 22.261 [2] and TS 22.104 [7] of 5G system and vertical domains, the architecture, functional and protocol to enable Time Sensitive Communication and Time Synchronization, described in TS 23.501 [3], TS 23.502 [4], TS 23.503 [5], TR 23.734 [6] and TS 24.519 [8].
The following are studied:
- possible charging scenarios and requirements for 5G System integration as a bridge in TSN network;
- possible charging scenarios and requirements for the Time Sensitive Communications and Time Synchronization service;
- possible new charging aspects for the following key items:
- QoS requirements for TSN (e.g. support for TSC QoS Flows, QoS mapping from TSN QoS information to 5GS QoS profile);
- Edge computing scenario support in TSN Transport (e.g. DS-TT and NW-TT);
- charging enhancement (e.g. new triggers) due to policy control for TSN traffic which may impact the charging;
- potential charging solutions for the above charging scenarios and requirements and taking in account TSN application requirements (e.g. instance survival time). |
28.840 | Study on CHF segmentation | TR | 18.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.840/28840-i10.zip | The present document studies the CHF discovery and selection in order to support the discovery of a CHF by the NF consumers like SMF, AMF, SMSF and PCF based on information about network segments that the CHF belongs to.
The following are studied:
- possible charging scenarios and requirements which makes use of CHF Segmentation.
- potential charging solutions which make use of CHF Segmentation. |
28.841 | Study on management aspects of Internet of Things (IoT) Non-Terrestrial Networks (NTN) enhancements | TR | 18.0.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.841/28841-i01.zip | The present document studies on management aspects of IoT NTN enhancements. It investigates specific IoT NTN related parameters which should be considered by O&M, investigates NRM enhancement, performance measurement and related new KPIs of IoT NTN. It studies the key issues associated with service and network management of IoT NTN enhancements (whether as NG-RAN or E-UTRAN) and potential solutions, and provides recommendations for the further normative work. |
28.842 | Study on data management phase 2 | TR | 18.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.842/28842-i10.zip | The present document studies potential enhancements related to management of management data, specifically enhancing mechanisms for discovery and reporting of management data, retrieval of stored management data, and managing external management data. |
28.843 | Study on structure of charging for verticals | TR | 18.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.843/28843-i10.zip | The present document studies the charging aspects to better support vertical scenarios, which is different with the existing customer charging baseline, specified in TS 32.240 [2], and makes the evolution of charging specifications clearer, which focuses on studying the charging principles and references of verticals charging, and aims to provides an guideline for other charging management TSs that specify the verticals charging.
All terms, definitions and abbreviations used in the present document, that are common across 3GPP TSs, are defined in the 3GPP Vocabulary, TR 21.905 [1]. |
28.844 | Study on charging aspects of satellite in the 5G System (5GS) | TR | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.844/28844-i00.zip | The present document studies on charging aspects of satellite in 5GS based on the TS 23.501 [2] and TS 23.502 [3]:
This study item is to investigate the following aspects of the satellite access:
- Possible business scenarios;
- Possible charging scenarios and potential charging requirements;
- Identify the potential charging solutions.
This study item is to investigate the following aspects of the satellite backhaul:
- Possible business scenarios;
- Possible charging scenarios and potential charging requirements, e.g. related to PCC/QoS control enhancement;
- Identify the potential charging solutions. |
28.845 | Study on charging aspects of ranging based services and sidelink positioning | TR | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.845/28845-i00.zip | The present document studies the charging aspects for Ranging based services and Sidelink Positioning
The following are in the scope:
• Identify the business roles of the Ranging based services and Sidelink Positioning;
• Identify the potential charging scenarios and requirements of the Ranging based services and Sidelink Positioning;
• Identify the potential charging solutions for the Ranging based services and Sidelink Positioning. |
28.863 | Study on Key Quality Indicators (KQIs) for 5G service experience | TR | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.863/28863-i00.zip | The present document investigates the definition and scenarios for KQI. The KQIs and the evaluation of the KQIs for each of the identified scenarios will be investigated. It also provides the analysis for the relation of KQI with the SLS requirements. |
28.864 | Study on Enhancement of the management aspects related to NetWork Data Analytics Functions (NWDAF) | TR | 18.0.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.864/28864-i01.zip | The present document studies the management enhancement for NWDAF (Network Data Analytics Function).
In the present document, with regarding to the analytic, data management and trained ML model provisioning services provided by the NWDAF, also considering different NWDAF deployment scenarios, some fundamental key issues related the management enhancement for NWDAF are discussed. And the corresponding potential solutions are provided and evaluated.
The present document also provides recommendations for the normative specifications work. |
28.865 | Study on Deterministic Communication Service Assurance (DCSA) | TR | 18.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.865/28865-i10.zip | The present document studies potential key issues and solutions for provisioning and assurance of deterministic communication services, e.g. management of related network functions, potential new service requirements and new performance measurements, etc. The present document provides conclusions and recommendations on the normative work. |
28.903 | Study on alignment with ETSI MEC for edge computing management | TR | 18.0.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.903/28903-i01.zip | The present document studies the solutions to support alignment with ETSI MEC from the management perspective for edge computing.
It also identifies potential issues and solutions to support GSMA OPG [2] requirement in coordination with ETSI MEC [3]. |
28.907 | Study on enhancement of management of non-public networks | TR | 18.0.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.907/28907-i01.zip | TS 28.557 [2] introduces management support for non-public networks based on stage 1 service requirements in TS 22.261 [3]. The present document is studies further enhancements to management of non-public networks including the following aspects:
- Study enhanced management of SNPN and PNI-NPN. For example, study new requirements and potential solutions of management capability exposure for SNPN and PNI-NPN, and how the mobile network operator and vertical customer cooperate to realize management and orchestration of network in MNO-Vertical Managed Mode in TS 28.557 [2].
- Study management of vertical as an authorized NPN service customer, e.g. the management of authorized capability of utilizing management services and management data.
- Study requirements and potential solutions to support end to end network management (including RAN domain and CN domain) in NPN scenarios. |
28.908 | Study on Artificial Intelligence/Machine Learning (AI/ ML) management | TR | 18.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.908/28908-i10.zip | The present document studies the Artificial Intelligence / Machine Learning (AI/ML) management capabilities and services for 5GS where AI/ML is used, including management and orchestration (e.g. MDA, see 3GPP TS 28.104 [2]), 5GC (e.g. NWDAF, see 3GPP TS 23.288 [3], and NG-RAN (e.g. RAN intelligence defined in 3GPP TS 38.300 [16] and 3GPP TS 38.401 [19]). |
28.909 | Study on evaluation of autonomous network levels | TR | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.909/28909-i00.zip | The present document studies on evaluation of autonomous network levels. It introduces the relevant studies in other SDOs, concepts of autonomous network levels evaluation and key effectiveness indicators (KEI). It identifies key issues related to autonomous network levels evaluation, documents potential solutions, and provides recommendations for the further normative work. |
28.910 | Study on enhancement of autonomous network levels | TR | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.910/28910-i00.zip | The present document studies on enhancement of autonomous network levels. It introduces the relevant study items and work items in 3GPP, identifies the additional generic MnS requirements of generic autonomous network level for the scenarios defined in Rel-17 and documents potential solutions for the identified generic MnS requirements. It also identifies the enhanced autonomy capabilities corresponding to different autonomous network levels for additional management use cases which is not defined in Rel-17 and documents potential solutions for the enhanced autonomy capabilities. Based on the investigation and studies, it provides recommendations for the further normative work. |
28.912 | Study on enhanced intent driven management services for mobile networks | TR | 18.0.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.912/28912-i01.zip | The present document investigates new areas for enhancing the intent driven management services of 5G network. It identifies and documents key issues and evaluates potential solutions, and provides recommendations for the normative work. |
28.913 | Study on new aspects of Energy Efficiency (EE) for 5G phase 2 | TR | 18.0.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.913/28913-i01.zip | The present document investigates the opportunities for defining new Energy Efficiency (EE) KPIs and new Energy Saving (ES) solutions for 5G. It identifies and documents key issues related to energy efficiency and energy saving, documents and evaluates potential solutions, and provides recommendations for the normative work. |
28.925 | Study on enhancement of service based management architecture | TR | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.925/28925-i00.zip | The present document studies on the potential enhancement of service based management architecture based on the existing 5G service based management architecture. |
29.002 | Mobile Application Part (MAP) specification | TS | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.002/29002-i00.zip | It is necessary to transfer between entities of a Public Land Mobile Network (PLMN) information specific to the PLMN in order to deal with the specific behaviour of roaming Mobile Stations (MS)s. The Signalling System No. 7 specified by CCITT is used to transfer this information.
The present document describes the requirements for the signalling system and the procedures needed at the application level in order to fulfil these signalling needs.
Clauses 1 to 6 are related to general aspects such as terminology, mobile network configuration and other protocols required by MAP.
MAP consists of a set of MAP services that are provided to MAP service-users by a MAP service-provider.
Figure 1.1/1: Modelling principles
Clauses 7 to 13A of the present document describe the MAP services.
Clauses 14 to 17 define the MAP protocol specification and the behaviour of service provider (protocol elements to be used to provide MAP services, mapping on to TC service primitives, abstract syntaxes, etc.).
Clauses 18 to 25 describe the MAP user procedures that make use of MAP services.
The present document specifies functions, procedures and information which apply to GERAN Iu mode. However, functionality related to GERAN Iu mode is neither maintained nor enhanced. |
29.007 | General requirements on interworking between the Public Land Mobile Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN) | TS | 18.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.007/29007-i00.zip | The present document identifies the Mobile‑services Switching Centre/Interworking Functions (MSC/IWFs) and requirements to support interworking between:
a) PLMN and PSTN;
b) PLMN and ISDN;
for circuit switched services in the PLMN. It is not possible to treat ISDN and PSTN as one type of network, even when both ISDN and PSTN subscribers are served by the same exchange because of the limitations of the PSTN subscribers access i.e. analogue connection without D‑channel signalling.
Within the present document, the requirements for voice and non‑voice (data) calls are considered separately.
From R99 onwards the following services are no longer required by a PLMN:
- the dual Bearer Services "alternate speech/data" (BS 61) and "speech followed by data" (BS 81);
- the dedicated services for PAD (BS 4x) and Packet access (BS 5x);
- the single asynchronous and synchronous Bearer Services (BS 21..26, BS 31..34).
From Rel-4 onwards the following services are no longer required by a PLMN:
- the synchronous Bearer Service non-transparent (BS 30 NT);
- the Basic Packet access;
- Non-transparent facsimile (TS 61/62 NT) for the A/Gb mode and GERAN Iu mode.
If a PLMN still provides these services it shall fulfil the specification of former releases.
The present document is valid for a PLMN in A/Gb mode as well as in Iu mode. If text applies only for one of these systems it is explicitly mentioned by using the terms "A/Gb mode" and "Iu mode". If text applies to both of the systems, but a distinction between the ISDN/PSTN and the PLMN is necessary, the term "PLMN" is used.
NOTE: The Gb interface does not play any role in the scope of the present document although the term "A/Gb mode" is used. |
29.010 | Information element mapping between Mobile Station - Base Station System (MS - BSS) and Base Station System - Mobile-services Switching Centre (BSS - MSC); Signalling Procedures and the Mobile Application Part (MAP) | TS | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.010/29010-i00.zip | The scope of the present document is:
i) to provide a detailed specification for the interworking between information elements contained in layer 3 messages sent on the MS-MSC interface (Call Control and Mobility Management parts of 3GPP TS 24.008 [4]) and parameters contained in MAP services sent over the MSC-VLR interface (3GPP TS 29.002 [9]) where the MSC acts as a transparent relay of information;
ii) to provide a detailed specification for the interworking between information elements contained in BSSMAP messages sent on the BSC-MSC interface (3GPP TS 48.008 [12]) and parameters contained in MAP services sent over the MSC-VLR interface (3GPP TS 29.002 [9]) where the MSC acts as a transparent relay of information;
iii) to provide a detailed specification for the interworking between information elements contained in BSSMAP messages (3GPP TS 48.008 [12]) and RANAP ((3GPP TS 25.413 [7]);
iv) to provide a detailed specification for the interworking as in i) and ii) above when the MSC also processes the information;
v) to provide a detailed specification for the interworking between information elements contained in layer 3 messages sent on the MS-SGSN interface (GPRS mobility part of 3GPP TS 24.008 [4]) and parameters contained in MAP services sent over the SGSN-HLR interface (3GPP TS 29.002 [9]);
vi) to provide a detailed specification for the interworking between information elements contained in RANAP messages sent on the SGSN-RNC interface (3GPP TS 25.413 [7]) and parameters contained in S1AP messages sent on the MME-eNodeB interface (3GPP TS 36.413 [21]);
vii) to provide a detailed specification for the interworking between information elements contained in BSSMAP messages (3GPP TS 48.008 [12]) or RANAP messages (3GPP TS 25.413 [7]) during SRVCC handovers.
Interworking for supplementary services is given in 3GPP TS 29.011 [11]. Interworking for the short message service is given in 3GPP TS 23.040 [3] and 3GPP TS 24.011. Interworking between the call control signalling of 3GPP TS 24.008 [4] and the PSTN/ISDN is given in GSM 09.03 [13], 3GPP TS 29.007 [10] and 3GPP TS 49.008 [14] [14]. Interworking between the 'A' and 'E' interfaces for inter-MSC handover signalling is given in 3GPP TS 29.007 [10] and 3GPP TS 49.008 [14] [14]. |
29.011 | Signalling Interworking for supplementary services | TS | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.011/29011-i00.zip | The scope of this Technical Specification is to provide a detailed specification for interworking between the A interface protocol and the Mobile Application Part for handling of supplementary services. The MAP interfaces of interest are the B-, C-, D- and E-interfaces.
The A-, C-, D- and E-interfaces are physical interfaces while the B-interface is an internal interface defined for modelling purposes. Information relating to the modelling interface is not normative in this specification.
Supplementary service signalling may be passed by the MSC/VLR between the A- and E-interfaces after inter-MSC handover. This procedure is transparent as far as supplementary services are concerned therefore interworking concerning this process is not described in this specification.
Clause 2 describes general procedures for interworking between the A- and D- physical interfaces.
Clause 3 describes the general procedures for the SS version negotiation.
Clause 4 describes the mapping of layer 3 radio path messages with Transaction Capabilities (TC) transaction sublayer messages for interworking between the A- and D- physical interfaces.
Clause 5 describes specific interworking procedures for all interfaces relating to call related SS activity.
Clause 6 describes specific interworking procedures for all interfaces relating to call independent SS activity. Clause 6 also covers the interworking between the MAP User (see 3GPP TS 29.002) and the SS handling functions of the network entities (see 3GPP TS 24.010 and 3GPP TS 24.080).
Reference is made to the following Technical Specifications:
- 3GPP TS 22.004 and 3GPP TS 22.08x and 3GPP TS 22.09x-series,
for definition of supplementary services;
- 3GPP TS 23.011, 3GPP TS 23.08x and 3GPP TS 23.09x-series,
for technical realisation of supplementary services;
- 3GPP TS 24.010, 3GPP TS 24.080, 3GPP TS 24.08x and 3GPP TS 24.09x-series,
for radio path signalling procedures for supplementary services;
- 3GPP TS 29.002 (MAP). |
29.013 | Signalling interworking between ISDN supplementary services; Application Service Element (ASE) and Mobile Application Part (MAP) protocols | TS | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.013/29013-i00.zip | The scope of the present document is to provide a specification for interworking between the ISDN Application Service Element (ASE) protocol for supplementary services and the Mobile Application Part (MAP) protocol on MAP D-interface protocol for handling of supplementary services within the digital cellular telecommunications system (Phase 2+). This version of the specification includes the interworking for the Call Completion to Busy Subscriber (CCBS) service between the ISDN CCBS-ASE and MAP.
The MAP protocol for CCBS service is specified in GSM 09.02. The ISDN CCBS-ASE protocol is specified in ETS 300 356‑18. The ISDN CCBS-ASE protocol is also commonly referred to as the SSAP protocol in GSM 03.93. This specification clarifies the interworking within the HLR between these protocols for the Call Completion to Busy Subscriber (CCBS) service.
Clause 4 describes the mapping between MAP application layer messages and SSAP application layer messages.
Clause 5 describes the mapping between MAP message parameters and SSAP message parameters.
Clause 6 describes the dialogue handling on the SSAP interface.
Clause 7 describes the SCCP layer addressing for messages on the SSAP interface. |
29.016 | General Packet Radio Service (GPRS); Serving GPRS Support Node (SGSN) - Visitors Location Register (VLR); Gs interface network service specification | TS | 18.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.016/29016-i00.zip | The present document specifies or references the subset of MTP and SCCP which is used for the reliable transport of BSSAP+ messages in the Gs interface. The present document references the 3GPP TS 29.202 which specifies alternative transport layers that can be applied instead of the MTP. The present document also specifies the SCCP addressing capabilities to be provided in the Gs interface.
The present document is divided into two main parts, clause 5 dealing with the use of MTP and clauses 6 and 7 dealing with the use of SCCP.
Clause 5 of the present document deals with the subset of the MTP that is required between an SGSN and a VLR. It is intended that this implementation of MTP is compatible with a full MTP implementation. Clause 4 references the 3GPP TS 29.202 which specifies alternatives to the MTP.
The SCCP is used to provide message routing between the SGSN and the VLR. The SCCP routing principles specified in the present document allow to connect one SGSN to several VLR. No segmentation at SCCP level is needed on the Gs interface. Only SCCP class 0 is used on the Gs interface. Clauses 6 and 7 identify the SCCP subset that should be used between an SGSN and an VLR. |
29.018 | General Packet Radio Service (GPRS); Serving GPRS Support Node (SGSN) - Visitors Location Register (VLR); Gs interface layer 3 specification | TS | 18.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.018/29018-i00.zip | The present document specifies or references procedures used on the Serving GPRS Support Node (SGSN) to Visitors Location Register (VLR) interface for interoperability between GSM circuit switched services and GSM packet data services.
The present document specifies the layer 3 messages and procedures on the Gs interface to allow coordination between databases and to relay certain messages related to GSM circuit switched services over the GPRS subsystem.
The functional split between VLR and SGSN is defined in 3GPP TS 23.060 [8]. The required procedures between VLR and SGSN are defined in detail in the present document. |
29.060 | General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface | TS | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.060/29060-i00.zip | The present document defines the second version of GTP used on:
- the Gn and Gp interfaces of the General Packet Radio Service (GPRS);
- the Iu, Gn and Gp interfaces of the UMTS system.
NOTE: The version number used in the message headers is 0 for the first version of GTP described in GSM 09.60, and 1 for the second version in 3GPP TS 29.060.
From release 8 onwards, the normative specification of the user plane of GTP version 1 is 3GPP TS 29.281 [41]. All provisions about GTPv1 user plane in the present document shall be superseded by 3GPP TS 29.281 [41].
The present document specifies functions, procedures and information which apply to GERAN Iu mode. However, functionality related to GERAN Iu mode is neither maintained nor enhanced. |
29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | TS | 18.1.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.061/29061-i10.zip | |
29.078 | Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase X; CAMEL Application Part (CAP) specification | TS | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.078/29078-i00.zip | |
29.079 | Optimal media routeing within the IP Multimedia Subsystem (IMS); Stage 3 | TS | 18.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.079/29079-i00.zip | The present document defines optional Optimal Media Routeing (OMR) procedures that can be applied by entities in the IP Multimedia Subsystem (IMS) that control media resources and are capable of manipulating the Session Description Protocol (SDP) as defined by IETF RFC 4566 [6].
The OMR procedures in the present specification relate to the handling of OMR-specific SDP attributes that are documented in TS 24.229 [4]. The OMR procedures use SDP offer/answer related procedures in IETF RFC 3264 [5] and in 3GPP TS 24.229 [4] in a backward-compatible manner.
The 3GPP network architecture, including the configuration and network entities of the IMS, is defined in 3GPP TS 23.002 [2]. The Stage 2 of the IMS is defined 3GPP TS 23.228 [3]. Annex Q of 3GPP TS 23.228 [3] documents the architecture and call flows for OMR.
The OMR procedures in this document are applicable to the following IMS entities that perform as an IMS-ALG or UA according to 3GPP TS 24.229 [4] and that control media resources:
- an IBCF acting as an IMS-ALG;
- a P-CSCF acting as IMS-ALG;
- an AS acting as B2BUA and adapting IMS-ALG procedures to control an MRF;
- an AS acting as B2BUA and adapting UA procedures to control an MRF; and
- an MGCF acting as UA.
NOTE 1: An AS acting as B2BUA to perform application functions such as conferencing or announcements will normally perform separate originating and terminating UA procedures, treating the media resource as an endpoint. An AS acting as B2BUA offering transcoding options will typically follow IMS-ALG procedures.
NOTE 2: The controlled media resource can be a TrGW, IMS-AGW, MRF, or a media function of the entity performing OMR.
The OMR procedures are not applicable for an UE. |
29.108 | Application of the Radio Access Network Application Part (RANAP) on the E-interface | TS | 18.0.0 | R3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.108/29108-i00.zip | The present document describes the subset of Radio Access Network Application Part (RANAP) messages and procedures, defined in 3GPP TS 25.413 [4], which is used on the E‑interface. A general description can be found in 3GPP TS 23.002 [7] and 3GPP TS 23.009 [2].
For the initiation and execution of relocation of SRNS (relocation for short, throughout the whole document) between MSCs a subset of RANAP procedures are used. For the subsequent control of resources allocated to the User Equipment (UE) RANAP procedures are used. The Direct Transfer Elementary Procedure (EP) of RANAP, is used for the transfer of connection management and mobility management messages between the UE and the controlling 3G_MSC. |
29.109 | Generic Authentication Architecture (GAA); Zh and Zn Interfaces based on the Diameter protocol; Stage 3 | TS | 18.1.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.109/29109-i10.zip | The present stage 3 specification defines the Diameter based implementation for bootstrapping Zh interface (BSF-HSS) and Dz interface (BSF-SLF) for HSS resolution for the BSF, the MAP based implementation for bootstrapping Zh' interface (BSF-HLR) and GAA Application Zn interface (BSF-NAF) in Generic Authentication Architecture (GAA). This specification also defines the Web Services based implementation for GAA Application Zn reference point (BSF-NAF). The definition contains procedures, message contents and coding. The procedures for bootstrapping and usage of bootstrapped security association are defined in 3GPP TS 33.220 [5].
The present document also specifies the Diameter and Web Services based implementation for the GAA Application Push Function Zpn reference point (BSF-NAF). The procedures for bootstrapping are defined in 3GPP TS 33.223 [23].
This specification is a part of the Generic Authentication Architecture (GAA) specification series.
The diameter based implementation for the Zh interface is based on re-usage of Cx interface Multimedia-Auth-Request/Answer messages originally between CSCF and HSS. These messages are defined in 3GPP TS 29.229 [3]. The 3GPP IMS mobility management uses the same definitions between CSCF and HSS. The present document defines how the defined messages are used with the bootstrapping and GAA application procedures (e.g. subscriber certificates) and the application logic that is needed in GAA network elements (BSF, HSS, and NAF).
Figure 1.1 depicts the relationships of these specifications to the other specifications for the Diameter based implementations.
Figure 1.1: Relationships to other specifications
Figure 1.2 provides an informal overall quick introduction to the whole signalling procedures in GAA system. The important identifiers are marked bold and optional data items are italicised. The Ub and Ua interfaces, not defined in this TS, are simplified.
NOTE: The Zh' interface (BSF-HLR) is not represented in this figure.
Figure 1.2: The whole signalling procedure in GAA system
Figure 1.3 provides an informal overall quick introduction to the whole signalling procedures in GAA Push Function. The important identifiers are marked bold and optional data items are italicised. The Ua and Upa interfaces, not defined in this TS, are simplified.
Figure 1.3: Signalling procedure in GAA Bootstrapping Push Function |
29.116 | Representational state transfer over xMB reference point between content provider and BM-SC | TS | 18.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.116/29116-i00.zip | The present document describes the REST-based protocol for the xMB reference point between the Content Provider and the BM-SC. The xMB reference point and related stage 2 protocol procedures are defined in 3GPP TS 23.246 [2] and in 3GPP TS 26.346 [3]. |
29.118 | Mobility Management Entity (MME) - Visitor Location Register (VLR) SGs interface specification | TS | 18.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.118/29118-i00.zip | |
29.119 | GPRS Tunnelling Protocol (GTP) specification for Gateway Location Register (GLR) | TS | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.119/29119-i00.zip | The present document describes the signalling requirements and procedures used at network elements related to the GLR for GTP within the 3GPP system at the application level.
The present document gives the description of the systems needed only in the network utilising GLR as the delta document against 3GPP TS 29.060. |
29.120 | Mobile Application Part (MAP) specification for Gateway Location Register (GLR) | TS | 18.0.0 | C4 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.120/29120-i00.zip | The present document describes the signalling requirements and procedures used at network elements related to the GLR for MAP within the 3GPP system at the application level.
The present document gives the description of the systems needed only in the network utilising GLR as the delta document against 3GPP TS 29.002. |
29.122 | T8 reference point for Northbound APIs | TS | 18.8.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/29_series/29.122/29122-i80.zip |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.