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
|
|---|---|---|---|---|---|---|
26.967 | eCall data transfer; In-band modem solution | TR | 18.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.967/26967-i00.zip | The European Union eCall requirements, recommendations and guidelines were developed by eSafety Forum, with important additional work produced by ETSI MSG, GSME, 3GPP, and CEN.
Previous work in 3GPP TR 22.967 [2] 'Transfer of Emergency Call Data', examined the issues associated with the transmission of emergency call data from a vehicle to a PSAP. This analysis identified that the preferred option be based on an in-band modem solution.
The objective of this work was to examine and describe the in band modem solution (in band modem and any necessary interface to the ME) for eCall. Because eCall is a European regional requirement, it shall not have an impact on the global circulation of terminals. In the interest of not duplicating work, the set of in-band solutions that were considered are those preferred by GSME unless significant improvements are available. The work assessed the suitability of existing 3GPP in-band solutions, e.g. CTM, to satisfy the requirements for eCall.
The present document assesses the suitability of CTM for eCall. |
26.969 | eCall data transfer; In-band modem solution; Characterization report | TR | 18.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.969/26969-i00.zip | The present document characterizes the performance of the eCall In-band Modem, which is used for reliable transmission of the eCall Minimum Set of Data (MSD) from an In-Vehicle System (IVS) to the Public Safety Answering Point (PSAP) via the voice channel of cellular and PSTN networks.
The European Union eCall requirements, recommendations and guidelines were developed by eSafety Forum [3] and [4], with important additional work produced by ETSI MSG, GSME, 3GPP, and CEN.
Previous work in 3GPP TR 22.967 [5] "Transfer of Emergency Call Data", examined the issues associated with the transmission of emergency call data from a vehicle to a PSAP. This analysis identified that the preferred option be based on an in-band modem solution.
eCall provides reliable full-duplex data communications between IVS and PSAP in addition to emergency voice call (E112) via the cellular network, and can be initiated either automatically or manually [6]. The eCall In-band Modem uses the same voice channel as used for the emergency voice call. eCall allows reliable transmission of MSD alternating with a speech conversation through the existing voice communication paths in cellular mobile phone systems. The expected benefit is that emergency services will be made aware of accidents much more rapidly, will get precise information on location, vehicle type etc. and therefore will be able to reach accident victims faster, with the potential to save many lives annually.
The eCall in-band modems (IVS and PSAP) are fully specified by the 'General description ' TS 26.267 [9] together with the C-code reference as provided in 3GPP TS 26.268 [7]. 3GPP TS 26.269 [8] deals with the conformance testing for eCall modem implementations.
The present document provides a detailed performance characterization of the eCall in-band modem solution. Results from the 3GPP selection tests as well as verification and characterization tests have been collected into this report. It is impossible to test the eCall modem for all conditions that might arise on the transmission path from the IVS to the PSAP. However, the selected set of test scenarios represents a wide range of conditions that are foreseen to potentially occur in the in-band transmission of eCall data over the radio access and core networks as well as the PSTN. |
26.973 | Update to fixed-point basic operators | TR | 18.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.973/26973-i00.zip | The present document covers the following topics:
1) Assessment of the gaps between modern processors and the existing set of basic operators (STL2009) [6].
2) Proposal of an extended set of operators addressing modern DSP architectures as an extension to STL2009.
3) Assessment of merits of an alternative EVS implementation using extended STL2009 Basic Operators.
4) Proposal for validation of an alternative EVS implementation using extended STL2009 Basic Operators. |
26.975 | Performance characterization of the Adaptive Multi-Rate (AMR) speech codec | TR | 18.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.975/26975-i00.zip | The present document provides background information on the performances of the Adaptive Multi-Rate (AMR) speech codec. Experimental test results from the Verification and Characterization phases of testing are reported to illustrate the behavior of AMR in multiple operational conditions. |
26.976 | Performance characterization of the Adaptive Multi-Rate Wideband (AMR-WB) speech codec | TR | 18.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.976/26976-i00.zip | The present document provides information of the AMR Wideband (AMR-WB) Characterisation, Verification and Selection Phases. Experimental test results from the speech quality related testing are reported to illustrate the behaviour of the AMR-WB codec. Additional information is provided, e.g., on implementation complexity of the AMR-WB codec. Also the verification results for the floating-point version of the AMR-WB codec (3GPP TS 26.204) are presented. |
26.978 | Results of the Adaptive Multi-Rate (AMR) noise suppression selection phase | TR | 18.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.978/26978-i00.zip | The present document provides background information on the performance of the six candidates which were proposed as solutions for publication of an example noise suppression solution for application to the GSM Adaptive Multi-Rate (AMR) speech codec. Experimental test results from the speech quality related testing are reported to illustrate the behaviour of the candidate algorithms in multiple operational conditions. Additional information is also provided covering data not necessarily directly associated with speech quality (such as complexity, delay, effect on voice activity factor). |
26.980 | Multimedia telephony over IP Multimedia Subsystem (IMS); Media handling aspects of multi-stream multiparty conferencing for Multimedia Telephony Service for IMS (MTSI) | TR | 18.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.980/26980-i00.zip | The Technical Report provides a study on the media handling aspects of Multi-stream Multiparty Conferencing for MTSI. The study focuses on enabling
• support to receive multi-stream audio/video at the terminals in a multiparty conferencing,
• support for at least two video contents, e.g. one main and one presentation,
• talker ID provisioning,
• compatibility with MTSI TS 26.114 and GSMA IR.94 (Video over LTE) [22] and GSMA IR.92 (VoLTE) [21], and
• applicability to both mobile and fixed access terminals
High-level use cases along with current limitations and recommendations are documented in the present document. |
26.981 | MBMS Extensions for Provisioning and Content Ingestion | TR | 18.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.981/26981-i00.zip | The present document is a study of an interface from external content providers to the BM-SC for provisioning and content ingestion. |
26.982 | Implementation guidelines for Multiparty RTT | TR | 18.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.982/26982-i00.zip | The present document provides the protocol details for the Multiparty Real-Time Text (Multiparty RTT) service in the IP Multimedia (IM) Core Network (CN) subsystem based on the requirements from 3GPP TS 22.173 [2].
The Multiparty RTT service is an operator specific service by which an operator enables the subscribers in conference to use real-time text during the conference session.
The present document is applicable to User Equipment (UE) and Application Servers (AS) which are intended to support the Multiparty RTT service. |
26.985 | Vehicle-to-everything (V2X); Media handling and interaction | TR | 18.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.985/26985-i00.zip | In the present document, media-related use cases of V2X described in TR 22.886 and their requirements in TS 22.186 are analysed in detail, to clarify the operation of advanced driving using networked visual information. The required procedures for media capture, compression, and transmission, based on the mechanisms for media handling and transportation, such as MTSI, MBMS, and FLUS, are investigated. Operation over the PC5 interface is currently outside of the scope of this document. |
26.989 | Mission Critical Push To Talk (MCPTT); Media, codecs and Multimedia Broadcast/Multicast Service (MBMS) enhancements for MCPTT over LTE | TR | 18.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.989/26989-i00.zip | The present document covers the enhancement required to support MCPTT. |
26.996 | Immersive Audio for Split Rendering Scenarios; Performance characterization | TR | 18.1.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.996/26996-i10.zip | This TR presents a characterization of the ISAR split rendering solutions specified in TS 26.249 [4] in terms of audio quality performance and technical properties. The characterization is done for the ISAR baseline solution that is defined as a feature of the IVAS codec.
NOTE: As the ISAR split rendering baseline solution is also incorporated as a feature into the IVAS codec, some of the characterization results of the present document may also appear in similar form in the IVAS characterization TR 26.997 [5]. Both representations are equally valid. |
26.997 | Codec for Immersive Voice and Audio Services (IVAS); Performance characterization | TR | 18.1.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.997/26997-i10.zip | The present document provides information on the Immersive Voice and Audio Services (IVAS) codec Selection Phase which was run using the floating point (3GPP TS 26.258). Experimental test results from the subjective quality testing are reported to illustrate the behaviour of the IVAS codec. Additional information is provided on implementation complexity of the IVAS codec and objective test results. |
26.998 | Support of 5G glass-type Augmented Reality / Mixed Reality (AR/MR) devices | TR | 18.1.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.998/26998-i10.zip | The present document collects information on glass-type AR/MR devices in the context of 5G radio and network services. The primary scope of this Technical Report is the documentation of the following aspects:
- Providing formal definitions for the functional structures of AR glasses, including their capabilities and constraints,
- Documenting core use cases for AR services over 5G and defining relevant processing functions and reference architectures,
- Identifying media exchange formats and profiles relevant to the core use cases,
- Identifying necessary content delivery transport protocols and capability exchange mechanisms, as well as suitable 5G system functionalities (including device, edge, and network) and required QoS (including radio access and core network technologies),
- Identifying key performance indicators and quality of experience factors,
- Identifying relevant radio and system parameters (required bitrates, latencies, loss rates, range, etc.) to support the identified AR use cases and the required QoE,
- Providing a detailed overall power analysis for media AR related processing and communication. |
26.999 | Virtual Reality (VR) streaming interoperability and characterization | TR | 18.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/26_series/26.999/26999-i00.zip | |
27.001 | General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS) | TS | 18.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/27_series/27.001/27001-i00.zip | The present document is based on the principles of terminal adaptor functions presented in the ITU-T I-series of Recommendations (I.460 to I.463).
The PLMN supports a wide range of voice and non-voice services in the same network. In order to enable non-voice traffic in the PLMN there is a need to connect various kinds of terminal equipment to the Mobile Termination (MT). The target of the present document is to outline the functions needed for the terminal adaptation.
The bearer services are described in 3GPP TS 22.002 and the general network configuration is described in 3GPP TS 23.002. The PLMN access reference configuration is defined in 3GPP TS 24.002. The various connection types used in the A/Gb mode or GERAN Iu mode PLMN are presented in 3GPP TS 43.010. Terminology used in the present document is presented in 3GPP TR 21.905 and 3GPP TS 29.990. For support of data services between a PLMN and other networks see 3GPP TS 29.007.
The present document is valid for a 2nd generation PLMN (A/Gb mode) as well as for a 3rd generation PLMN (Iu mode). If text applies only for one of these systems it is explicitly mentioned by using the terms "A/Gb mode" and "UTRAN 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 1: From R99 onwards the following services are no longer required by a PLMN:
- the dual Bearer Services "alternate speech/data" and "speech followed by data";
- the dedicated services for PAD and Packet access;
- BS 21 ... 26 and BS 31 ... 34.
From REL-4 onwards the following service is no longer required by a PLMN:
- the synchronous Bearer Service non-transparent (BS 30 NT).
- non-transparent facsimile (TS 61/62 NT) for the A/Gb mode and GERAN Iu mode.
The support of these services is still optional. The specification of these services is not within the scope of the present document. For that, the reader is referred to former releases.
NOTE2 : The Gb interface does not play any role in the scope of the present document although the term "A/Gb mode" is used. |
27.002 | Terminal Adaptation Functions (TAF) for services using asynchronous bearer capabilities | TS | 18.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/27_series/27.002/27002-i00.zip | The present document defines the interfaces and Terminal Adaptation Functions (TAF) integral to a Mobile Termination (MT) which enable the use of asynchronous bearer services in the PLMN and the attachment of asynchronous terminals to a MT (see 3GPP TS 24.002 [3] and 3GPP TS 23.101 [6]).
The general aspects of Terminal Adaptation Functions are contained in 3GPP TS 27.001 [10].
The present document covers support of these services for the following interfaces and procedures:
(i) ITU-T V.14 [16] procedures.
(ii) ITU-T V.21 [17] DTE/DCE interface.
(iii) ITU-T V.22bis [18] DTE/DCE interface.
(iv) ITU-T V.32 [24] DTE/DCE procedures.
(v) ITU-T I.420 [14] S interface.
(vi) ITU-T V.250 [22] signalling procedures.
The asynchronous data rates between the MT and the IWF are defined in 3GPP TS 22.002 [5].
NOTE: From GSM R99 onwards the following services are no longer required in a PLMN:
- the dual Bearer Services "alternate speech/data" and "speech followed by data";
- the dedicated services for PAD and Packet access;
- the BS 21 ... 26 and BS 31 ... 34.
The support of these services is still optional. The specification of these services is not within the scope of the present document. For that, the reader is referred to GSM Release 98.
NOTE: Please note that the Gb interface does not play any role in the scope of the present document although the term "A/Gb mode" is used. GERAN Iu mode is for further study. |
27.003 | Terminal Adaptation Functions (TAF) for services using synchronous bearer capabilities | TS | 18.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/27_series/27.003/27003-i00.zip | The present document defines Terminal Adaptation Functions (TAF) which are integrated in a Mobile Termination (MT) and which enable the use of synchronous bearer services in the PLMN and the attachment of Synchronous synchronous Terminals terminals to an MT (see 3GPP TS 24.002 [3]). For the case where asynchronous terminals are attached to the TAF when using synchronous bearer services in the PLMN, the reader is referred to 3GPP TS 27.002 [36] for the asynchronous MT-TAF interface specifics and to the present document for synchronous bearer service specifics on the TAF-IWF interface. The general aspects of Terminal Adaptation Functions are contained in specification 3GPP TS 27.001 [9]. The present document covers support of synchronous data services (see 3GPP TS 22.002 [6]) for the following interfaces and procedures:
‑ V.22 [15] DTE/DCE Interface;
‑ V.22 bis [16] DTE/DCE Interface;
‑ V.26 ter [19] DTE/DCE Interface;
‑ X.21 bis [24] DTE/DCE Interface;
‑ X.32 [30] Procedure;
‑ V.25 bis [18] Procedure;
NOTE: From R99 onwards the support of the following services are no longer required by a PLMN:
- the dual Bearer Services "alternate speech/data" and "speech followed by data";
- the dedicated services for PAD and Packet access;
- BS 21 ... 26 and BS 31 ... 34.
From REL-4 onwards the support of the following service is no longer required by a PLMN:
- the synchronous Bearer Service non-transparent (BS 30 NT).
the Teleservice Facsimile non-transparent (TS 61/62 NT) for A/Gb mode.
The support of these services is still optional. The specification of these services is not within the scope of the present document. For that, the reader is referred to GSM R98 or R99 respectively.
NOTE: Please note that the Gb interface does not play any role in the scope of the present document although the term “A/Gb mode” is used. GERAN Iu mode is for further study. |
27.005 | Use of Data Terminal Equipment - Data Circuit terminating Equipment (DTE - DCE) interface for Short Message Service (SMS) and Cell Broadcast Service (CBS) | TS | 18.0.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/27_series/27.005/27005-i00.zip | The present document defines three interface protocols for control of SMS functions within a GSM/UMTS mobile telephone from a remote terminal via an asynchronous interface.
Clause 2 defines a binary protocol ("Block Mode"). The protocol includes error protection and is suitable for use where the link may not be completely reliable. It will be of particular use where control of remote devices is required. Efficient transfer of binary encoded user data is possible.
Clause 3 defines a character-based interfaced based on "AT" commands ("Text Mode"). This mode is suitable for unintelligent terminals or terminal emulators, and for application software built on command structures like those defined in V.25ter. Some of the commands defined in clause 3 will also be useful for implementations of clause 2 and/or clause 4, for example enabling an indication of incoming SMS messages.
Clause 4 defines a character-based interface with hex-encoded binary transfer of message blocks ("PDU Mode"). This mode is suitable for software drivers based on AT command structures which do not understand the content of the message blocks and can only pass them between the MT and "upper level" software resident in the TE.
In all three modes, the terminal is considered to be in control for SMS/CBS transactions.
The present document considers the mobile termination to be a single entity. Other 3GPP/GSM Technical Specifications describe the split of functionality between the mobile equipment and (U)SIM.
The three "modes" referred to above, are represented in figure 0.1.
The "Block mode" is a self contained mode in its own right, and when entered, control will remain within that mode until the procedures to exit the mode are executed, after which control is returned to the V.25ter "command" state or "on-line command" state.
The "Text" and "PDU" modes are not in themselves V.25ter states but are simply sets of commands which will operate in either the V.25ter "command" state or "on-line command" state. The "Text" and "PDU" modes are transitory states and after each operation, control is automatically returned to the V.25ter "command" state or "on-line command" state. Whilst in the V.25ter command state, the MS is available to handle incoming and outgoing calls such as Data or Facsimile.
Figure 0.1: Block, Text and PDU modes
In the "Block mode" and "PDU" mode a mobile is not permitted to modify any component of an SMS/CBS message received from the air interface or an SMS message received from a TE, before passing it on, except where 3GPP TS 23.040 [3] or 3GPP TS 23.041 [4] defines a "component modification facility" and where this "component modification facility" is supported by the mobile. In the Text Mode the mobile may be unable to display characters coded in particular coding schemes. In this case, the mobile shall behave as described in 3GPP TS 23.038 [2] and assume the coding scheme to be the GSM 7 bit default alphabet. |
27.007 | AT command set for User Equipment (UE) | TS | 18.8.0 | C1 | https://www.3gpp.org/ftp/Specs/archive/27_series/27.007/27007-i80.zip | |
28.100 | Management and orchestration; Levels of autonomous network | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.100/28100-i00.zip | The present document specifies the concepts for autonomous networks, autonomous network level, and that use cases , requirements and solutions for the levels of autonomous functions in a 3GPP network. |
27.060 | Packet domain; Mobile Station (MS) supporting Packet Switched services | TS | 18.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/27_series/27.060/27060-i00.zip | The (A/Gb and Iu mode) PLMN supports a wide range of voice and non-voice services in the same network. In order to enable non‑voice traffic in the PLMN there is a need to connect various kinds of terminal equipments to the Mobile Station (MS). The present document defines the requirements for TE-MT interworking over the R-reference point for the Packet Domain , including the protocols and signalling needed to support Packet Switched services, as defined in 3GPP TS 22.060 and 3GPP TS 23.060.
The present document is valid for PLMN in A/Gb mode as well as for PLMN 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". Please note, that the A interface does not play any role in the scope of this document although the term "A/Gb mode" is used. |
28.062 | Inband Tandem Free Operation (TFO) of speech codecs; Service description; Stage 3 | TS | 18.0.0 | S4 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.062/28062-i00.zip | The present document contains the service description for the in-band signalling protocol for the support of Tandem Free Operation of the Half Rate, Full Rate, Enhanced Full Rate, Adaptive Multi Rate narrowband and Adaptive Multi Rate Wide-Band speech codec types in GSM and GSM-evolved 3G systems. |
28.104 | Management and orchestration; Management Data Analytics (MDA) | TS | 18.7.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.104/28104-i70.zip | |
28.105 | Management and orchestration; Artificial Intelligence/ Machine Learning (AI/ML) management | TS | 18.7.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.105/28105-i70.zip | |
28.111 | Management and orchestration; Fault management (FM) | TS | 18.5.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.111/28111-i50.zip | |
28.201 | Charging management; Network slice performance and analytics charging in the 5G System (5GS); Stage 2 | TS | 18.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.201/28201-i20.zip | |
28.202 | Charging management; Network slice management charging in the 5G System (5GS); Stage 2 | TS | 18.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.202/28202-i10.zip | |
28.203 | Charging management; Network slice admission control charging in the 5G System (5GS) | TS | 18.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.203/28203-i10.zip | The present document specifies the Converged Charging description for Network Slice Admission Control charging in the 5G System (5GS), based on Network Slice Admission Control Function (NSACF) of 5GS architecture and procedures specified in 3GPP TS 23.501 [3] and 3GPP TS 23.502 [4].
The charging aspect of Network Slice Admission Control charging is based on charging principles specified in 3GPP TS 32.240 [2].
The following functionalities of Network Slice Admission Control are within the scope:
- number of registered UEs per network slice;
- number of PDU Sessions per network slice. |
28.204 | Charging management; Network slice-specific authentication and authorization charging in the 5G System (5GS) | TS | 18.1.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.204/28204-i11.zip | The present document specifies the Converged Charging description for network slice-specific authentication and authorization charging in the 5G System (5GS) based on Network Slice-Specific Authentication and Authorization Function (NSSAAF) of 5GS architecture and procedures specified in 3GPP TS 23.501 [3] and 3GPP TS 23.502 [4].
The scope is the Network Slice-Specific Authentication and Authorization as specified in TS 23.502 [4] with a AAA Server (AAA-S). |
28.301 | Telecommunication management; Licensed Shared Access (LSA) Controller (LC) Integration Reference Point (IRP); Requirements | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.301/28301-i00.zip | The present document specifies the requirements of the Licensed Shared Access (LSA) Controller (LC) Integration Reference Point (IRP). This IRP allows the NM to interact with the LC. This interaction with the LC enables the NM to configure NEs utilizing LSA spectrum resources.
The following two deployment scenarios are supported:
- one scenario in which the LC communicates LSA spectrum resource availability information to the NM, and
- one scenario in which the LC determines and communicates to the NM constraints on parameters of cells liable to use LSA spectrum resources. |
27.010 | Terminal Equipment to User Equipment (TE-UE) multiplexer protocol | TS | 18.0.0 | C3 | https://www.3gpp.org/ftp/Specs/archive/27_series/27.010/27010-i00.zip | The scope of the present document is to define a multiplexing protocol between a UE and a TE. The multiplexing protocol can be used to send any data, for instance voice, SMS, USSD, fax etc.
The present document describes the protocol, but not the commands or data transported with it. |
28.303 | Telecommunication management; Licensed Shared Access (LSA) Controller (LC) Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.303/28303-i00.zip | The purpose of the present document is to define the mapping of the LSA Controller (LC) Integration Reference Point (IRP) (see 3GPP TS 28.302 [2]) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment and in a SOAP/WSDL environment.
This Solution Set specification is related to 3GPP TS 28.302 V14.0.X. |
28.302 | Telecommunication management; Licensed Shared Access (LSA) Controller (LC) Integration Reference Point (IRP); Information Service (IS) | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.302/28302-i00.zip | The present document specifies the LSA controller (LC) Integration Reference Point (IRP) management operations and notifications that can be communicated between an IRPAgent and one or several IRPManagers.
The present document specifies the semantics and behaviour of operations, notifications and their parameters visible across the reference point in a protocol and technology neutral way. It does not define their syntax and encoding. |
28.304 | Control and monitoring of Power, Energy and Environmental (PEE) parameters Integration Reference Point (IRP); Requirements | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.304/28304-i00.zip | The present document specifies the requirements for the control and monitoring of Power, Energy and Environmental (PEE) parameters in the following types of Radio Access Networks (RAN): GSM, UTRAN and E-UTRAN. |
28.305 | Control and monitoring of Power, Energy and Environmental (PEE) parameters Integration Reference Point (IRP); Information Service (IS) | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.305/28305-i00.zip | The present document specifies the control and monitoring of Power, Energy and Environmental (PEE) parameters Integration Reference Point (IRP) Information Service (IS).
It specifies the semantics and behaviour of operations, notifications and their parameters visible across Itf-N in a protocol and technology neutral way. It does not define their syntax and encoding. |
28.306 | Control and monitoring of Power, Energy and Environmental (PEE) parameters Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.306/28306-i00.zip | The present document specifies the Solution Set definitions for the control and monitoring of Power, Energy and Environmental (PEE) parameters Integration Reference Point (IRP).
The Solution Set definitions are related to 3GPP TS 28.305 V15.0.X [2]. |
28.307 | Telecommunication management; Quality of Experience (QoE) measurement collection Integration Reference Point (IRP); Requirements | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.307/28307-i00.zip | The present document addresses Integration Reference Point (IRP) requirements for the function Quality of Experience (QoE) measurement collection in UMTS and LTE. The measurements that are collected are DASH [2] and MTSI [5] measurements.
The function includes collecting QoE information from UEs frequenting a specified area. |
28.308 | Telecommunication management;Quality of Experience (QoE) measurement collection Integration Reference Point (IRP); Information Service (IS) | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.308/28308-i00.zip | The present document addresses the operations and notifications for the function Quality of Experience (QoE) measurement collection in UMTS and LTE. The measurements that are collected are DASH [4] and MTSI [9] measurements.
The function includes collecting QoE information from UEs frequenting a specified area. |
28.309 | Management of Quality of Experience (QoE) measurement collection Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.309/28309-i00.zip | The present document specifies the Solution Set definitions for the IRP whose semantics are specified in Management of Quality of Experience (QoE) measurement collection Integration Reference Point (IRP): Information Service (3GPP TS 28.308 [19]). The present document is applicable to UMTS networks and EPS networks. |
28.310 | Management and orchestration; Energy efficiency of 5G | TS | 18.8.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.310/28310-i80.zip | |
28.311 | Management and orchestration; Network policy management for mobile networks based on Network Function Virtualization (NFV) scenarios | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.311/28311-i00.zip | The present document contains the architecture, requirements, use cases, procedures and definitions of interfaces for policy management for 4G networks. |
28.312 | Management and orchestration; Intent driven management services for mobile networks | TS | 18.8.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.312/28312-i80.zip | |
28.313 | Management and orchestration; Self-Organizing Networks (SON) for 5G networks | TS | 18.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.313/28313-i20.zip | |
28.314 | Management and orchestration; Plug and Connect; Concepts and requirements | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.314/28314-i00.zip | |
28.315 | Management and orchestration; Plug and Connect; Procedure flows | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.315/28315-i00.zip | |
28.316 | Management and orchestration; Plug and Connect; Data formats | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.316/28316-i00.zip | The present document specifies data formats for Plug and Connect NE in 3GPP systems. |
28.317 | Management and orchestration;Self-configuration of Radio Access Network Entities (RAN NEs) | TS | 18.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.317/28317-i30.zip | |
28.318 | Management and Orchestration; Network and services operations for energy utilities | TS | 18.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.318/28318-i20.zip | |
28.319 | Management and orchestration; Access Control for Management services | TS | 18.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.319/28319-i20.zip | |
28.390 | Telecommunication management; Fixed Mobile Convergence (FMC); Interface Integration Reference Point (IRP) Solution Profiles (SPs) | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.390/28390-i00.zip | The objective of this specification is to define a set of Solution Profiles (SPs) for Interface IRPs. Each SP identifies the necessary and sufficient subset of the 3GPP IRP defined solutions (solutions) required for the network management of a specific operating environment or domain, including that defined for the converged management environments.
A specific operating environment or domain is characterised by a set of Requirement statements. In other words, the solutions identified in a specific SP would satisfy the Requirements listed in that same SP.
An SP, in its simplest form, is nothing else than a list of solutions (e.g. 3GPP IRP defined operations). The purpose is to place a combination of solutions under a common (SP) name so that:
- Operators and vendors need not decide arbitrarily which solutions are to be used to satisfy the Requirements;
- There is one document where readers can have a clear view of solutions, specified in various IRP specifications, required to satisfy the Requirements.
This version of the TS contains a number of SPs defined in clause 4 and onwards, one clause for each SP. |
28.402 | Telecommunication management; Performance Management (PM); Performance measurements for Evolved Packet Core (EPC) and non-3GPP access interworking system | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.402/28402-i00.zip | The present document describes the measurements for EPC and non-3GPP access network interworking.
TS 32.401 [3] describes Performance Management concepts and requirements.
The present document is valid for all measurement types provided by an implementation of EPC and non-3GPP access Interworking System. Only measurement types that are specific to EPC and non-3GPP access interworking are defined within the present documents. Vendor specific measurement types used in EPC and non-3GPP access Interworking System 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) are only be referenced within this specification, wherever there is a need identified for the existence of such a reference.
The definition of the standard measurements is intended to result in comparability of measurement data produced in a multi-vendor network, for those measurement types that can be standardised across all vendors' implementations.
The structure of the present document is as follows:
- Header 1: Network Element (e.g. measurements related to ePDG);
- Header 2: Measurement function (e.g. Tunnel establishment);
- Header 3: Measurements. |
28.403 | Telecommunication management; Performance Management (PM); Performance measurements for Wireless Local Area Network (WLAN) | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.403/28403-i00.zip | The present document describes the measurements for WLAN.
TS 32.401 [3] describes Performance Management concepts and requirements.
The present document is valid for all measurement types provided by an implementation of a WLAN.
Only measurement types that are specific to WLAN are defined within the present document. Vendor specific measurement types used in WLAN are not covered. Instead, these could be applied according to manufacturer's documentation.
Measurements related to "external" technologies (such as WLAN or IP) as described by "external" standards bodies (e.g. IEEE or IETF) are only referenced within the present document, 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. |
28.404 | Telecommunication management; Quality of Experience (QoE) measurement collection; Concepts, use cases and requirements | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.404/28404-i00.zip | The present document addresses concepts, business level use cases and requirements for the function Quality of Experience (QoE) measurement collection in 3GPP networks. The measurements that are collected are DASH [2], MTSI [3], and Virtual Reality (see TS 26.118 [5]) measurements.
The function includes collecting QoE information from UEs frequenting a specified area or an individual UE for a specified end user service/end user service type. |
28.405 | Telecommunication management; Quality of Experience (QoE) measurement collection; Control and configuration | TS | 18.8.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.405/28405-i80.zip | |
28.406 | Telecommunication management; Quality of Experience (QoE) measurement collection; Information definition and transport | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.406/28406-i00.zip | The present document describes Quality of Experience (QoE) measurement collection record content definition and management. It covers the Quality of Experience (QoE) measurement data content, their format and transfer across UMTS networks,LTE networks, and NR networks. The measurements that are collected are DASH [7],MTSI [8], and VR [9] measurements. |
28.500 | Telecommunication management; Management concept, architecture and requirements for mobile networks that include virtualized network functions | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.500/28500-i00.zip | The present document specifies the management concepts, the management requirements and use cases from operators’ perspective for mobile networks that include virtualized network functions which can be part of EPC or IMS, and provides the management architecture for these mobile networks. |
28.510 | Telecommunication management; Configuration Management (CM) for mobile networks that include virtualized network functions; Requirements | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.510/28510-i00.zip | The present document (together with the relevant requirements described in [1], [2], [3] and [4]) specifies the requirements applicable to Configuration Management (CM) of virtualized network functions. |
28.511 | Telecommunication management; Configuration Management (CM) for mobile networks that include virtualized network functions; Procedures | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.511/28511-i00.zip | The present document specifies the Configuration Management (CM) procedures for mobile networks that include virtualized network functions. |
28.512 | Telecommunication management; Configuration Management (CM) for mobile networks that include virtualized network functions; Stage 2 | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.512/28512-i00.zip | The present document is Configuration Management stage 2 specification for mobile networks that include virtualized network functions. |
28.513 | Telecommunication management; Configuration Management (CM) for mobile networks that include virtualized network functions; Stage 3 | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.513/28513-i00.zip | The present document is Configuration Management stage 3 specification for mobile networks that include virtualized network functions. |
28.515 | Telecommunication management; Fault Management (FM) for mobile networks that include virtualized network functions; Requirements | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.515/28515-i00.zip | The present document (together with the relevant requirements described in [2], [3], [4] and [5]) specifies the requirements applicable to Fault Management (FM) of mobile networks that include virtualized network functions. |
28.516 | Telecommunication management; Fault Management (FM) for mobile networks that include virtualized network functions; Procedures | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.516/28516-i00.zip | The present document specifies the Fault Management procedures for mobile networks that include virtualized network functions. |
28.517 | Telecommunication management; Fault Management (FM) for mobile networks that include virtualized network functions; Stage 2 | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.517/28517-i00.zip | The present document is Fault Management stage 2 specification for mobile networks that include virtualized network functions which can be part of EPC or IMS. |
28.518 | Telecommunication management; Fault Management (FM) for mobile networks that include virtualized network functions; Stage 3 | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.518/28518-i00.zip | The present document is Fault Management stage 3 specification for mobile networks that include virtualized network functions which can be part of EPC or IMS. |
28.520 | Telecommunication management; Performance Management (PM) for mobile networks that include virtualized network functions; Requirements | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.520/28520-i00.zip | The present document (together with the relevant requirements described in [2], [3], [4], [5] and [6]) specifies the requirements applicable to Performance Management (PM) of mobile networks that include virtualized network functions. |
28.521 | Telecommunication management; Performance Management (PM) for mobile networks that include virtualized network functions; Procedures | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.521/28521-i00.zip | The present document specifies the Performance Management procedures for mobile networks that include virtualized network functions S. |
28.522 | Telecommunication management; Performance Management (PM) for mobile networks that include virtualized network functions; Stage 2 | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.522/28522-i00.zip | The present document is the Performance Management stage 2 specification for mobile networks that include virtualized network functions. |
28.523 | Telecommunication management; Performance Management (PM) for mobile networks that include virtualized network functions; Stage 3 | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.523/28523-i00.zip | The present document is the Performance Management stage 3 specification for mobile networks that include virtualized network functions. |
28.525 | Telecommunication management; Life Cycle Management (LCM) for mobile networks that include virtualized network functions; Requirements | TS | 18.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.525/28525-i10.zip | The present document (together with the relevant requirements described in [2], [3] and [4]) specifies the requirements applicable to Lifecycle Management (LCM) for mobile networks that include virtualized network functions. |
28.526 | Telecommunication management; Life Cycle Management (LCM) for mobile networks that include virtualized network functions; Procedures | TS | 18.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.526/28526-i10.zip | The present document specifies the Life Cycle Management (LCM) procedures for mobile networks that include virtualized network functions. |
28.527 | Telecommunication management; Life Cycle Management (LCM) for mobile networks that include virtualized network functions; Stage 2 | TS | 18.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.527/28527-i10.zip | The present document is the Life Cycle Management (LCM) stage 2 specification for mobile networks that include virtualized network functions. |
28.528 | Telecommunication management; Life Cycle Management (LCM) for mobile networks that include virtualized network functions; Stage 3 | TS | 18.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.528/28528-i10.zip | The present document is the Life Cycle Management (LCM) stage 3 specification for mobile networks that include virtualized network functions. |
28.530 | Management and orchestration; Concepts, use cases and requirements | TS | 18.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.530/28530-i20.zip | |
28.531 | Management and orchestration; Provisioning | TS | 18.8.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.531/28531-i80.zip | |
28.532 | Management and orchestration; Generic management services | TS | 18.6.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.532/28532-i60.zip | |
28.533 | Management and orchestration; Architecture framework | TS | 18.4.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.533/28533-i40.zip | |
28.535 | Management and orchestration; Management services for communication service assurance; Requirements | TS | 18.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.535/28535-i20.zip | The present document describes, concepts and background, and specifies use cases and requirements for closed control loop communication service assurance solution that adjusts and optimizes the services provided by NG-RAN and 5GC. |
28.536 | Management and orchestration; Management services for communication service assurance; Stage 2 and stage 3 | TS | 18.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.536/28536-i30.zip | |
28.537 | Management and orchestration; Management capabilities | TS | 18.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.537/28537-i20.zip | |
28.538 | Management and orchestration; Edge Computing Management | TS | 18.10.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.538/28538-ia0.zip | |
28.540 | Management and orchestration; 5G Network Resource Model (NRM); Stage 1 | TS | 18.2.1 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.540/28540-i21.zip | |
28.541 | Management and orchestration; 5G Network Resource Model (NRM); Stage 2 and stage 3 | TS | 18.12.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.541/28541-ic0.zip | |
28.550 | Management and orchestration; Performance assurance | TS | 18.5.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.550/28550-i50.zip | |
28.552 | Management and orchestration; 5G performance measurements | TS | 18.11.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.552/28552-ib0.zip | |
28.554 | Management and orchestration; 5G end to end Key Performance Indicators (KPI) | TS | 18.8.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.554/28554-i80.zip | |
28.555 | Management and orchestration; Network policy management for 5G mobile networks; Stage 1 | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.555/28555-i00.zip | The present document specifies the concepts, requirements and use cases for network policy management in 5G networks. |
28.556 | Management and orchestration; Network policy management for 5G mobile networks; Stage 2 and stage 3 | TS | 18.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.556/28556-i10.zip | The present document specifies policy management procedures, stage 2 and stage 3 for policy MnS. |
28.557 | Management and orchestration; Management of Non-Public Networks (NPN); Stage 1 and stage 2 | TS | 18.4.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.557/28557-i40.zip | The present document specifies concepts, use cases, requirements and solutions for management of non-public networks. |
28.558 | Management and orchestration; UE level measurements for 5G system | TS | 18.3.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.558/28558-i30.zip | |
28.611 | Telecommunication management; Evolved Packet Core (EPC) and non-3GPP access interworking system Network Resource Model (NRM) Integration Reference Point (IRP); Requirements | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.611/28611-i00.zip | The present document describes the Network Resource Model (NRM) Integration Reference Point (IRP) requirements for the EPC and WLAN interworking system according to the structure defined in 3GPP TS 23.402 [8] (e.g. ePDG, 3GPP AAA, etc). |
28.612 | Telecommunication management; Evolved Packet Core (EPC) and non-3GPP access interworking system 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.612/28612-i00.zip | The present document is an Integration Reference Point (IRP) named "Evolved Packet Core (EPC) and non-3GPP access interworking system Network resource Model (NRM) IRP; Information Service (IS)", 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 interworking network resources.
The present document specifies the semantics and behaviour of Information Object Class (IOC) attributes and relations visible across the reference point in a protocol and technology neutral way. It does not define their syntax and encoding.
It reuses relevant parts of the generic NRM in 3GPP TS 28.622 [6], either by direct reuse or sub-classing, and in addition to that defines specific IOCs in EPC and non-3GPP access interworking systems.
In order to access the information defined by this NRM, an interface IRP 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 interface IRP is applicable is outside the scope of the present document. |
28.616 | Telecommunication management; Evolved Packet Core (EPC) and non-3GPP access interworking system 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.616/28616-i10.zip | The present document is part of an Integration Reference Point (IRP) named Evolved Packet Core (EPC) and non-3GPP access Interworking System Network Resource Model (NRM) IRP, through which an IRPAgent can communicate configuration management information to one or several IRPManagers concerning EPC and non-3GPP access interworking system resources. The EPC and non-3GPP access Interworking System NRM IRP comprises a set of specifications defining requirements, a protocol neutral information service and one or more solution sets.
The present document specifies the solution sets for the EPC and non-3GPP access interworking system NRM IRP.
This solution set specification is related to 3GPP TS 28.612. |
28.620 | Telecommunication management; Fixed Mobile Convergence (FMC) Federated Network Information Model (FNIM) Umbrella Information Model (UIM) | TS | 18.2.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.620/28620-i20.zip | |
28.621 | Telecommunication management; Generic Network Resource Model (NRM) Integration Reference Point (IRP); Requirements | TS | 18.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.621/28621-i10.zip | The present document defines, in addition to the requirements defined in [1], [2] and [3], the generic network resource information requirements for the present IRP: Generic Network Resource Model IRP and Service Based Management Architecture (SBMA).
Note that the present document is applicable to deployment scenarios using the SBMA as defined in TS 28.533 [10]. For deployment scenarios using the IRP framework as defined in TS 32.102 [2] the latest Rel-14 version of TS 28.621 is applicable. |
28.622 | Telecommunication management; Generic Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS) | TS | 18.11.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.622/28622-ib0.zip | |
28.623 | Telecommunication management; Generic Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 18.11.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.623/28623-ib0.zip | |
28.624 | Telecommunication management; State management data definition Integration Reference Point (IRP); Requirements | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.624/28624-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: State Management Data Definition. |
28.625 | Telecommunication management; State management data definition Integration Reference Point (IRP); Information Service (IS) | TS | 18.0.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.625/28625-i00.zip | The present document specifies the State Management Data Definition IRP Information Service 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.626 | Telecommunication management; State management data definition Integration Reference Point (IRP); Solution Set (SS) definitions | TS | 18.1.0 | S5 | https://www.3gpp.org/ftp/Specs/archive/28_series/28.626/28626-i10.zip | The present document specifies the Solution Set (SS) definitions for the IRP whose semantics is specified in State Management Data Definition IRP: Information Service (IS) (3GPP TS 28.625 [2]). |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.