id
stringlengths 5
12
| title
stringlengths 8
250
| type
stringclasses 2
values | version
stringclasses 222
values | working_group
stringclasses 30
values | url
stringlengths 67
81
| scope
stringlengths 0
65.7k
|
---|---|---|---|---|---|---|
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.
|
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.
|
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.
|
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.
|
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.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.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.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.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.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.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.
|
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.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.
|
26.966
|
Evaluation of new HEVC coding tools
|
TR
|
18.0.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.966/26966-i00.zip
|
This Technical Report gathers the opportunities for improving HEVC-based services. This includes documentation of motivating use cases and scenarios. Specifically, potential of improving on the following use cases are identified: the compression performance for stereoscopic 3D content, the network performance related to exploding adaptive streaming traffic, and the demands for very high-quality image applications. HEVC based solutions to address each opportunity are identified: HEVC Multiview profiles, HEVC Scalable profiles, and HEVC 4:4:4 (up to 10 bits) capable profiles. Methodologies to investigate and document the pros and cons of the proposed solutions for each use case are documented. Finally, conclusions are drawn on the relevancy of solutions and if any new normative specification work is to be done.
|
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.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.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.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.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.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.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.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.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.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.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.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.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.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.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.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.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.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.557
|
Management and orchestration; Management of Non-Public Networks (NPN); Stage 1 and stage 2
|
TS
|
18.4.1
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.557/28557-i41.zip
|
The present document specifies concepts, use cases, requirements and solutions for management of non-public networks.
|
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.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.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.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.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.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.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.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.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.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.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.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.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.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.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]).
|
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.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.663
|
Telecommunication management; Generic Radio Access Network (RAN) Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions
|
TS
|
18.2.1
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/28_series/28.663/28663-i21.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.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.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.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.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.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.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.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.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.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.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.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.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.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 …
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.