id
stringlengths 5
12
| title
stringlengths 8
250
| type
stringclasses 2
values | version
stringclasses 214
values | working_group
stringclasses 30
values | url
stringlengths 67
81
| scope
stringlengths 0
65.7k
|
|---|---|---|---|---|---|---|
32.333
|
Telecommunication management; Notification Log (NL) Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS)
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.333/32333-900.zip
|
The present document specifies the CORBA Solution Set for the IRP whose semantics are specified in 3GPP TS 32.332 [6] Notification Log IRP: Information Service.
Clause 1 to 3 provides background information. Clause 4 provides key architectural features supporting the SS.
Clause 5 defines the mapping of operations, notification, parameters and attributes defined in IS to their SS equivalents. Clause 6 describes the notification interface containing the push method. Annex A contains the IDL specification.
This Solution Set specification is related to TS 32.332 V9.0.X.
|
32.335
|
Telecommunication management; Notification Log (NL) Integration Reference Point (IRP); eXtensible Markup Language (XML) solution definitions
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.335/32335-900.zip
|
The present document specifies the XML Definitions for the Notification Log IRP as it applies to Itf-N, in accordance with the requirements in 3GPP TS 32.331 [3] and Information Service definitions in 3GPP TS 32.332 [4].
This XML Definitions specification defines the XML syntax of the NL IRP XML Data File.
This specification is related to 3GPP TS 32.332 V9.0.X.
|
32.337
|
Telecommunication management; Notification Log (NL) Integration Reference Point (IRP); SOAP Solution Set (SS)
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.337/32337-900.zip
|
The present document specifies the SOAP SS for the IRP whose semantics is specified in Notification Log (NL) IRP IS (3GPP TS 32.332 [5]).
This Solution Set specification is related to 3GPP TS 32.332 V9.0.X.
|
32.343
|
Telecommunication management; File Transfer (FT) Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS)
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.343/32343-900.zip
|
The present document specifies the Common Object Request Broker Architecture (CORBA) Solution Set (SS) for the IRP whose semantics is specified in File Transfer IRP: Information Service 3GPP TS 32.342 [7].
This Solution Set specification is related to 3GPP TS 32.342 V9.0.X.
|
32.345
|
Telecommunication management; File Transfer (FT) Integration Reference Point (IRP); eXtensible Markup Language (XML) definitions
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.345/32345-900.zip
|
The present document specifies the XML Definitions for the File Transfer IRP (FTIRP) as it applies to Itf-N, in accordance with FT IRP IS definitions [3], for usage with the SOAP Solution Set [6] as well as Notification Log IRP XML Definitions [4].
This specification is related to 3GPP TS 32.342 V9.0.X.
|
32.347
|
Telecommunication management; File Transfer (FT) Integration Reference Point (IRP); SOAP Solution Set (SS)
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.347/32347-900.zip
|
The present document specifies the SOAP Solution Set for the IRP whose semantics are specified in File Transfer IRP: Information Service (3GPP TS 32.342 [4]).
This Solution Set specification is related to 3GPP TS 32.342 V9.0.X.
|
32.353
|
Telecommunication management; Communication Surveillance (CS) Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS)
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.353/32353-900.zip
|
The present document specifies the CORBA Solution Set for the IRP whose semantics are specified in TS 32.352 [6] Communication Surveillance IRP: Information Service.
This Solution Set specification is related to 3GPP TS 32.352 V9.0.X.
|
32.355
|
Telecommunication management; Communication Surveillance (CS) Integration Reference Point (IRP); eXtensible Markup Language (XML) definitions
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.355/32355-900.zip
|
The present document specifies the XML Definitions for the Communication Surveillance IRP (CSIRP) as it applies to Itf-N, in accordance with CS IRP IS definitions [3], for usage with the Notification Log IRP XML Definitions [4].
This specification is related to 3GPP TS 32.352 V9.0.X.
|
32.357
|
Telecommunication management; Communication Surveillance (CS) Integration Reference Point (IRP); SOAP Solution Set (SS)
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.357/32357-900.zip
|
The present document specifies the SOAP SS for the IRP whose semantics is specified in Communication Surveillance (CS) IRP IS (3GPP TS 32.352 [5]).
This Solution Set specification is related to 3GPP TS 32.352 V9.0.X.
|
32.363
|
Telecommunication management; Entry Point (EP) Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS)
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.363/32363-900.zip
|
The present document specifies the CORBA Solution Set for the IRP whose semantics are specified in the Entry Point IRP: Information Service (3GPP TS 32.362 [6]).
This Solution Set specification is related to 3GPP TS 32.362 V9.0.X.
|
32.365
|
Telecommunication management; Entry Point (EP) Integration Reference Point (IRP); eXtensible Markup Language (XML) definitions
|
TS
|
9.0.1
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.365/32365-901.zip
|
The present document specifies the XML Definitions for the Entry Point IRP (EPIRP) as it applies to Itf-N, in accordance with EP IRP IS definitions [3] as well as Notification Log IRP XML Definitions [4].
This specification is related to 3GPP TS 32.362 V9.0.X.
|
32.367
|
Telecommunication management; Entry Point (EP) Integration Reference Point (IRP); SOAP Solution Set (SS)
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.367/32367-900.zip
|
The present document specifies the SOAP Solution Set for the IRP whose semantics are specified in Entry Point IRP: Information Service (3GPP TS 32.362 [4]).
This Solution Set specification is related to 3GPP TS 32.362 V9.0.X.
|
32.373
|
Telecommunication management; Security services for Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) solution
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.373/32373-900.zip
|
The present document specifies the CORBA Solution for the IRP whose semantics is specified in 3GPP TS 32.372 [5] Security Service for IRP Information Service.
This Solution Set specification is related to 3GPP TS 32.372 [5].
Note that within the present document there are several alternate solutions. Specific choices will to be made to counter identified security threats , and to consider performance and cost criteria, i.e. an implementation is not expected to have to support every option for every deployment.
|
32.375
|
Telecommunication management; Security services for Integration Reference Point (IRP); File integrity solution
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.375/32375-900.zip
|
The present document contains the Security Services for IRP: File integrity solution whose semantics are specified in 3GPP TS 32.372 [5].
This solution specification is related to 3GPP TS 32.372 V 9.0.X [5].
|
32.383
|
Telecommunication management; Partial Suspension of Itf-N Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS)
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.383/32383-900.zip
|
The purpose of Partial Suspension of Itf-N IRP is to define an interface through which an IRPManager can suspend the forwarding of notifications via Itf-N which were generated in parts of the managed systems.
The present document is the "CORBA Solution Set" of Partial Suspension of Itf-N IRP for the IRP whose semantics is specified in Partial Suspension of Itf-N IRP Information Service (3GPP TS 32.382 [5]).
|
32.385
|
Telecommunication management; Partial Suspension of Itf-N Integration Reference Point (IRP): eXtensible Markup Language (XML) file format definition
|
TS
|
9.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.385/32385-910.zip
|
The purpose of Partial Suspension of Itf-N IRP is to define an interface through which an IRPManager can suspend the forwarding of notifications via Itf-N which were generated in parts of the managed systems.
The present document is the eXtensible Markup Language (XML) file format definition of Partial Suspension of Itf-N IRP for the IRP whose semantics is specified in Partial Suspension of Itf-N IRP: Information Service (TS 32.382 [9]).
This XML Definitions specification defines the XML syntax of the Partial Suspension of Itf-N IRP.
This XML Definitions specification is related to 3GPP TS 32.382 V9.0.x.
|
32.387
|
Telecommunication management; Partial Suspension of Itf-N Integration Reference Point (IRP); SOAP Solution Set (SS)
|
TS
|
9.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.387/32387-910.zip
|
The present document specifies the SOAP SS for the IRP whose semantics is specified Partial Suspension of Itf-N IRP IS (3GPP TS 32.382 [5]).
This Solution Set specification is related to 3GPP TS 32.382 V9.0.X.
|
32.393
|
Telecommunication management; Delta synchronization Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS)
|
TS
|
9.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.393/32393-910.zip
|
The purpose of Delta Synchronization IRP is to define an interface through which an IRPManager can request only those data which changed (i.e. changed, were created or deleted) from a synchronization point onwards.
The present document is the "CORBA Solution Set" of Delta Synchronization IRP for the IRP whose semantics is specified in Delta Synchronization IRP: Information Service (3GPP TS 32.392 [5]).
|
32.395
|
Telecommunication management; Delta synchronisation Integration Reference Point (IRP); eXtensible Markup Language (XML) file format definition
|
TS
|
9.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.395/32395-910.zip
|
The purpose of Delta Synchronisation IRP is to define an interface through which an IRPManager can request only those data which changed (i.e. changed, were created or deleted) from a synchronisation point onwards.
The present document is the eXtensible Markup Language (XML) file format definition of Delta Synchronisation IRP for the IRP whose semantics is specified in Delta Synchronisation IRP: Information Service (3GPP TS 32.392 [11]).
This XML Definitions specification defines the XML syntax of the Delta Synchronisation IRP XML Data File.
This XML Definitions specification is related to 3GPP TS 32.392 V9.0.X.
|
32.397
|
Telecommunication management; Delta synchronization Integration Reference Point (IRP); SOAP Solution Set (SS)
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.397/32397-900.zip
|
The present document specifies the SOAP SS for the IRP whose semantics is specified in Delta Synchronization IRP IS (3GPP TS 32.392 [5]).
This Solution Set specification is related to 3GPP TS 32.392 V9.0.X.
|
32.413
|
Telecommunication management; Performance Management (PM) Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.413/32413-900.zip
|
The present document specifies the Common Object Request Broker Architecture (CORBA) Solution Set (SS) for the IRP whose semantics is specified in PM (Performance Management) IRP: Information Service 3GPP TS 32.412 [7].
This Solution Set specification is related to 3GPP TS 32.412 [7].
|
32.415
|
Telecommunication management; Performance Management (PM) Integration Reference Point (IRP); eXtensible Markup Language (XML) definitions
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.415/32415-900.zip
|
The present document specifies the XML definitions for the Performance Management (PM) Integration Reference Point (IRP) as it applies to Itf-N, in accordance with PM IRP IS definitions in 3GPP TS 32.412 [3], for usage with the SOAP Solution Set [6] as well as Notification Log IRP XML definitions in 3GPP TS 32.335 [4].
This specification is related to 3GPP TS 32.412 V9.0.X.
|
32.417
|
Telecommunication management; Performance Management (PM) Integration Reference Point (IRP); SOAP Solution Set (SS)
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.417/32417-900.zip
|
The present document specifies the SOAP Solution Set for the IRP whose semantics are specified in Performance Management IRP: Information Service (3GPP TS 32.412 [4]).
This Solution Set specification is related to 3GPP TS 32.412 V8.0.X.
|
32.443
|
Telecommunication management; Trace Management (Trace) Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)
|
TS
|
9.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.443/32443-910.zip
|
This Solution Set specification is related to 3GPP TS 32.442 [7].
|
32.445
|
Telecommunication management; Trace Management (Trace) Integration Reference Point (IRP): eXtensible Markup Language (XML) file format definition
|
TS
|
9.2.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.445/32445-920.zip
|
The present document is the eXtensible Markup Language (XML) file format definition of Trace IRP for the IRP whose semantics is specified in Trace IRP: Information Service (3GPP TS 32.442 [3]).
This XML Definitions specification defines the XML syntax of the Trace IRP XML Data File for the notifications related to Trace IRP. The XML file definitions for a trace data file can be found in Annex A of 3GPP TS 32.423 [4].
This XML File Format Definition specification is related to 3GPP TS 32.442 V9.0.X.
|
32.447
|
Telecommunication management; Trace Management Integration Reference Point (IRP): SOAP Solution Set (SS)
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.447/32447-900.zip
|
The present document specifies the SOAP Solution Set for the IRP whose semantics are specified in Trace Management IRP: Information Service (3GPP TS 32.442 [5]).
This Solution Set specification is related to 3GPP TS 32.442 V9.0.X.
|
32.503
|
Telecommunication management; Self-configuration of network elements Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS)
|
TS
|
9.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.503/32503-910.zip
|
The present document is the "CORBA Solution Set" of Software Management IRP for the IRP whose semantics is specified in Software Management IRP Information Service (3GPP TS 32.502 [7]).
|
32.505
|
Telecommunication management; Self-configuration of network elements Integration Reference Point (IRP): eXtensible Markup Language (XML) file format definition
|
TS
|
9.2.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.505/32505-920.zip
|
The present document is the "XML file format definition" of Self-Configuration IRP (SCIRP) for the IRP whose semantics are specified in Self-Configuration IRP Information Service (3GPP TS 32.502 [2]).
This file format definition specification is related to TS 32.502 V9.0.X.
|
32.507
|
Telecommunication management; Self-configuration of network elements Integration Reference Point (IRP): SOAP Solution Set (SS)
|
TS
|
9.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.507/32507-910.zip
|
The present document specifies the SOAP Solution Set for the IRP whose semantics are specified in Self-Configuration of Network Elements Integration Reference Point (IRP): Information Service (3GPP TS 32.502 [4]).
This Solution Set specification is related to 3GPP TS 32.502 V9.0.X.
|
32.523
|
Telecommunication management; Self-Organizing Networks (SON); Policy Network Resource Model (NRM) Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS)
|
TS
|
9.3.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.523/32523-930.zip
|
The purpose of this SON Policy Network Resource Model IRP: CORBA Solution Set is to define the mapping of the IRP information model (see TS 32.522 [4]) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
This Solution Set is related to 3GPP TS 32.522 v9.3.X.
|
32.525
|
Telecommunication management; Self-Organizing Networks (SON) Policy Network Resource Model (NRM) Integration Reference Point (IRP); eXtensible Markup Language (XML) file format definition
|
TS
|
9.2.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.525/32525-920.zip
|
The present document provides the XML file format definition for the SON Policy Network Resource Model IRP IS [2].
An application of these XML definitions is to build a configuration file for transfer with the Bulk CM IRP using either CORBA Solution Set of 3GPP TS 32.613 [3] or the SOAP Solution Set of 3GPP TS 32.617 [5]. For this application, the basic part of the XML file format definition is provided by 3GPP TS 32.615 [4].
Other applications of these XML definitions are the SOAP solution sets of other IRPs that perform operations on managed objects, for example the Basic CM IRP SOAP SS of 3GPP TS 32.607 [6].
This specification is related to 3GPP TS 32.522 V9. 3.X.
|
32.533
|
Telecommunication management; Software management (SwM); Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS)
|
TS
|
9.5.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.533/32533-950.zip
|
The present document is the "CORBA Solution Set" of Software Management IRP for the IRP whose semantics is specified in Software Management IRP Information Service (3GPP TS 32.532 [5]).
This Solution Set specification is related to 3GPP TS 32.532 [5] V9.3.X.
|
32.535
|
Telecommunication management; Software Management Integration Reference Point (IRP); eXtensible Markup Language (XML) definitions
|
TS
|
9.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.535/32535-910.zip
|
The present document provides the XML file format definition for the Software Management Integration Reference Point (IRP) IS [3] V9.2.X.
The present document specifies the XML Definitions for the Software Management Integration Reference Point (IRP) as it applies to Itf-N, in accordance with Software Management IRP IS definitions [3] as well as Notification Log IRP XML Definitions [4].
|
32.537
|
Telecommunication management; Software management (SwM); Integration Reference Point (IRP); SOAP Solution Set (SS)
|
TS
|
9.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.537/32537-910.zip
|
The present document specifies the SOAP Solution Set for the IRP whose semantics are specified in Software management Integration Reference Point (IRP): Information Service (3GPP TS 32.532 [4]).
This Solution Set specification is related to 3GPP TS 32.532 V9.0.X.
|
32.603
|
Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS)
|
TS
|
9.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.603/32603-910.zip
|
The purpose of this Basic Configuration Management (CM) IRP: CORBA Solution Set is to define the mapping of the Basic CM IRP: IS (see 3GPP TS 32.602 [4]) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
This document defines NRM independent data types and methods.
This Solution Set specification is related to 3G TS 32.602 V8.1.X.
|
32.607
|
Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP); SOAP Solution Set (SS)
|
TS
|
9.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.607/32607-910.zip
|
The purpose of this Basic CM IRP: SOAP Solution Set is to define the mapping of the Basic CM IRP: IS (3GPP TS 32.602 [4]) to the protocol specific details necessary for implementation of this IRP in a SOAP/WSDL environment.
The present document defines NRM independent data types and methods.
This Solution Set specification is related to 3G TS 32.602 V9.0.X.
|
32.613
|
Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)
|
TS
|
9.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.613/32613-910.zip
|
The purpose of this Bulk CM IRP: CORBA Solution Set is to define the mapping of the IRP Information Service 3GPP TS 32.612 [3] to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
This Solution Set specification is related to 3GPP TS 32.612 V9.1.X.
|
32.615
|
Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): eXtensible Markup Language (XML) file format definition
|
TS
|
9.2.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.615/32615-920.zip
|
The present document provides the main part of the XML file format definition for the Bulk Configuration Management IRP IS in 3GPP TS 32.612 [1].
The other parts of this XML file format definition are NRM-specific parts.
Those NRM-specific parts are provided by 3GPP TS 32.625 [11], 32.635 [12], 32.645 [13], 32.655 [14], 32.695 [16], 32.715 [17], 32.735 [18], 32.745 [15], 32.755 [20], 32.765 [19], 32.525 [21], 32.175 [22], 32.725 [23], 32.775 [24] and 32.785 [25].
Bulk CM XML file formats are based on XML [2], XML Schema [3] [4] [5] and XML Namespace [6] standards.
This File Format Definition specification is related to 3GPP TS 32.612 V9.1.X.
|
32.617
|
Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Bulk CM IRP SOAP Solution Set (SS)
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.617/32617-900.zip
|
The present document specifies the SOAP Solution Set for the IRP whose semantics are specified in Bulk CM IRP: Information Service (3GPP TS 32.612 [4]).
This Solution Set specification is related to 3GPP TS 32.612 V9.0.X.
|
32.623
|
Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS)
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.623/32623-900.zip
|
The TS 32.62x-series (Generic Network Resources IRP) define an Integration Reference Point (IRP) through which an "IRPAgent" (typically an Element Manager or Network Element) can communicate Network Management related information to one or several "IRPManagers" (typically Network Managers).
This TS-family specifies a generic Network Resource Model, NRM (also referred to as a Management Information Model - MIM) with definitions of Information Object Classes (IOCs) and Managed Object Classes (MOCs).
The present document specifies the CORBA Solution Set.
This Solution Set specification is related to 3GPP TS 32.622 V9.0.X.
|
32.625
|
Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP): Bulk CM eXtensible Markup Language (XML) file format definition
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.625/32625-900.zip
|
The present document provides the NRM-specific part related to the Generic Network Resources IRP NRM [1] of the XML file format definition for the Bulk Configuration Management IRP IS [2].
The main part of this XML file format definition is provided by 3GPP TS 32.615 [3].
Bulk CM XML file formats are based on XML [4], XML Schema [5] [6] [7] and XML Namespace [8] specifications.
This specification is related to 3GPP TS 32.622 V9.0.X.
|
32.633
|
Telecommunication management; Configuration Management (CM); Core network resources Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS)
|
TS
|
9.2.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.633/32633-920.zip
|
The purpose of the present document is to define the mapping of the IRP information model (see TS 32.632 [3]) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
This Solution Set specification is related to 3GPP TS 32.632 V9.1.X.
|
32.635
|
Telecommunication management; Configuration Management (CM); Core network resources Integration Reference Point (IRP); Bulk CM eXtensible Markup Language (XML) file format definition
|
TS
|
9.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.635/32635-910.zip
|
The present document provides the NRM-specific part related to the Core Network Resources IRP NRM [1] of the XML file format definition for the Bulk Configuration Management IRP IS [2].
The main part of this XML file format definition is provided by 3GPP TS 32.615 [3].
Bulk CM XML file formats are based on XML [4], XML Schema [5] [6] [7] and XML Namespace [8] standards.
This File Format Definition specification is related to 3GPP TS 32.632 V9.1.X.
|
32.643
|
Telecommunication management; Configuration Management (CM); UTRAN network resources Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS)
|
TS
|
9.3.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.643/32643-930.zip
|
The purpose of this UTRAN Network Resources IRP: CORBA Solution Set is to define the mapping of the IRP information model (see TS 32.642 [4]) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
This Solution Set specification is related to 3GPP TS 32.642 V9.3.X.
|
32.645
|
Telecommunication management; Configuration Management (CM); UTRAN network resources Integration Reference Point (IRP); Bulk CM eXtensible Markup Language (XML) file format definition
|
TS
|
9.3.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.645/32645-930.zip
|
The present document provides the NRM-specific part related to the UTRAN Network Resources IRP NRM [1] of the XML file format definition for the Bulk Configuration Management IRP IS [2].
The main part of this XML file format definition is provided by 3GPP TS 32.615 [3].
Bulk CM XML file formats are based on XML [4], XML Schema [5] [6] [7] and XML Namespace [8] standards.
This File Format Definition specification is related to 3GPP TS 32.642 V9.3.X.
|
32.653
|
Telecommunication management; Configuration Management (CM); GERAN network resources Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS)
|
TS
|
9.2.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.653/32653-920.zip
|
The purpose of this GERAN Network Resources IRP: CORBA Solution Set is to define the mapping of the IRP information model (see 3GPP TS 32.652 [4]) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
This Solution Set specification is related to 3GPP TS 32.652 V9.2.X.
|
32.655
|
Telecommunication management; Configuration Management (CM); GERAN network resources Integration Reference Point (IRP); Bulk CM eXtensible Markup Language (XML) file format definition
|
TS
|
9.2.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.655/32655-920.zip
|
The present document provides the NRM-specific part related to the GERAN Network Resources IRP NRM [1] of the XML file format definition for the Bulk Configuration Management IRP IS [2].
The main part of this XML file format definition is provided by 3GPP TS 32.615 [3].
Bulk CM XML file formats are based on XML [4], XML Schema [5] [6] [7] and XML Namespace [8] specifications.
This File Format Definition specification is related to 3GPP TS 32.652 V9.2.X.
|
32.663
|
Telecommunication management; Configuration Management (CM); Kernel CM Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS)
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.663/32663-900.zip
|
The purpose of the present document is to define the mapping of the Kernel CM IRP: IS (see 3GPP TS 32.662 [4]) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
This Solution Set specification is related to 3GPP TS 32.662 V9.0.X [4].
|
32.665
|
Telecommunication management; Configuration Management (CM); Kernel CM Integration Reference Point (IRP); eXtensible Markup Language (XML) definitions
|
TS
|
9.0.1
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.665/32665-901.zip
|
The present document specifies the XML Definitions for the Kernel CM Integration Reference Point (IRP) as it applies to Itf-N, in accordance with Kernel CM IRP IS definitions [3] as well as Notification Log IRP XML Definitions [4].
This specification is related to 3GPP TS 32.662 V9.0.X.
|
32.667
|
Telecommunication management; Configuration Management (CM); Kernel CM Integration Reference Point (IRP); SOAP Solution Set (SS)
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.667/32667-900.zip
|
The purpose of the present document is to define the mapping of the Kernel CM IRP: IS (3GPP TS 32.662 [4]) to the protocol specific details necessary for implementation of this IRP in a SOAP/WSDL environment.
This Solution Set specification is related to 3GPP TS 32.662 V9.0.X.
|
32.673
|
Telecommunication management; Configuration Management (CM); State Management Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS)
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.673/32673-900.zip
|
The present document specifies the CORBA Solution Set (SS) for the IRP whose semantics is specified in State Management IRP: Information Service (IS) (3GPP TS 32.672 [2]).
Clause 1 to 3 provides background information. Clause 4 provides key architectural features supporting the SS. Clause 5 defines the mapping of operations, notification, parameters and attributes defined in IS to their SS equivalents. Annex A contains the IDL specification.
This Solution Set specification is related to 3GPP TS 32.672 V9.0.X.
|
32.675
|
Telecommunication management; Configuration Management (CM); State Management Integration Reference Point (IRP); Bulk CM eXtensible Markup Language (XML) file format definition
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.675/32675-900.zip
|
The present document specifies the XML file format definition for the Bulk Configuration Management IRP IS [2] for the IRP whose semantics is specified in State Management IRP: Information Service (IS) (3GPP TS 32.672 [1]).
Bulk CM XML file formats are based on XML [4], XML Schema [5] [6] [7] and XML Namespace [8] standards.
This File Format Definition specification is related to 3GPP TS 32.672 V9.0.X.
|
32.695
|
Telecommunication management; Inventory Management (IM) network resources Integration Reference Point (IRP); Bulk Configuration Management (CM) eXtensible Markup Language (XML) file format definition
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.695/32695-900.zip
|
The present document provides the NRM-specific part related to the Inventory Management NRM IRP IS in 3GPP TS 32.692 [1] of the XML file format definition for the Bulk Configuration Management IRP IS in 3GPP TS 32.612 [2].
The main part of this XML file format definition is provided by 3GPP TS 32.615 [3].
Inventory Management XML file formats are based on XML [4], XML Schema [5] [6] [7] and XML Namespace [8] standards.
This File Format Definition specification is related to 3GPP TS 32.692 V9.0.X.
|
32.713
|
Telecommunication management; Configuration Management (CM); Transport Network (TN) Network Resource Model (NRM) Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS)
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.713/32713-900.zip
|
The purpose of this Transport Network (TN) interface Network Resource Model IRP: CORBA Solution Set is to define the mapping of the IRP information model in 3GPP TS 32.712 [4] to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
This Solution Set specification is related to 3GPP TS 32.712 V9.0.X.
|
32.715
|
Telecommunication management; Configuration Management (CM) Transport Network (TN); Network Resource Model (NRM) Integration Reference Point (IRP); Bulk CM eXtensible Markup Language (XML) file format definition
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.715/32715-900.zip
|
The present document provides the NRM-specific part related to 3GPP TS 32.712 [1] Transport Network (TN) interface NRM IRP IS of the XML file format definition for the 3GPP TS 32.612 [2] Bulk Configuration Management IRP IS.
The main part of this XML file format definition is provided by 3GPP TS 32.615 [3].
Bulk CM XML file formats are based on XML [4], XML Schema [5] [6] [7] and XML Namespace [8] standards.
This File Format Definition specification is related to 3GPP TS 32.712 V9.0.X.
|
32.723
|
Telecommunication management; Configuration Management (CM); Repeater network resources Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS)
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.723/32723-900.zip
|
The purpose of this Repeater Network Resources IRP: CORBA Solution Set is to define the mapping of the IRP information model (see 3GPP TS 32.722 [4]) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
This Solution Set specification is related to 3GPP TS 32.722.
|
32.725
|
Telecommunication management; Configuration Management (CM); Repeater network resources Integration Reference Point (IRP); Bulk CM eXtensible Markup Language (XML) file format definition
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.725/32725-900.zip
|
The present document provides the NRM-specific part related to the Repeater Network Resources IRP NRM [1] of the XML file format definition for the Bulk Configuration Management IRP IS [2].
The main part of this XML file format definition is provided by 3GPP TS 32.615 [3].
Bulk CM XML file formats are based on XML [4], XML Schema [5] [6] [7] and XML Namespace [8] standards.
This File Format Definition specification is related to 3GPP TS 32.722 V9.0.X.
|
32.733
|
Telecommunication management; IP Multimedia Subsystem (IMS) Network Resource Model (NRM) Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS)
|
TS
|
9.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.733/32733-910.zip
|
The purpose of this IMS NRM IRP: CORBA Solution Set is to define the mapping of the IRP Information Service (see TS 32.732 [3]) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
This Solution Set specification is related to 3GPP TS 32.732.
|
32.735
|
Telecommunication management; IP Multimedia Subsystem (IMS) Network Resource Model (NRM) Integration Reference Point (IRP); Bulk CM eXtensible Markup Language (XML) file format definition
|
TS
|
9.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.735/32735-910.zip
|
The present document provides the NRM-specific part related to the IMS NRM IRP [1] of the XML file format definition for the Bulk Configuration Management IRP IS [2].
The main part of this XML file format definition is provided by 3GPP TS 32.615 [3].
Bulk CM XML file formats are based on XML [4], XML Schema [5] [6] [7] and XML Namespace [8] standards.
This File Format Definition specification is related to 3GPP TS 32.732 V9.1.X.
|
32.743
|
Telecommunication management; Configuration Management (CM); Signalling Transport Network (STN) interface Network Resource Model (NRM) Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS)
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.743/32743-900.zip
|
The present document maps the IRP information model in 32.742 [4] to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
This Solution Set specification is related to 3GPP TS 32.742 V9.0.X.
|
32.745
|
Telecommunication management; Configuration Management (CM); Signalling Transport Network (STN) interface Network Resource Model (NRM) Integration Reference Point (IRP); Bulk CM eXtensible Markup Language (XML) file format definition
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.745/32745-900.zip
|
The present document provides the NRM-specific part related to the STN Network Resources IRP NRM in 32.742 [1] of the XML file format definition for the Bulk Configuration Management IRP IS (TS 32.612 [2]).
The main part of this XML file format definition is provided by 3GPP TS 32.615 [3].
Bulk CM XML file formats are based on XML [4], XML Schema [5] [6] [7] and XML Namespace [8] specifications.
This File Format Definition specification is related to 3GPP TS 32.742 V9.0.X.
|
32.753
|
Telecommunication management; Evolved Packet Core (EPC) Network Resource Model (NRM) Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS)
|
TS
|
9.2.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.753/32753-920.zip
|
The present document is part of an Integration Reference Point (IRP) named EPC Network Resource Model (NRM) IRP, through which an IRPAgent can communicate configuration management information to one or several IRPManagers concerning EPC resources. The EPC NRM IRP comprises a set of specifications defining Requirements, a protocol neutral Information Service and one or more Solution Set(s).
The present document specifies the EPC Network Resources IRP: CORBA Solution Set, which defines the mapping of the IRP information model (see TS 32.752 [2]) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
This Solution Set is related to 3GPP TS 32.752 v9.3.X.
|
32.755
|
Telecommunication management; Evolved Packet Core (EPC) Network Resource Model (NRM) Integration Reference Point (IRP); eXtensible Markup Language (XML) definitions
|
TS
|
9.3.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.755/32755-930.zip
|
The present document provides the XML file format definition for the EPC Network Resource Model IRP IS [2] V9.3.X.
An application of these XML definitions is to build a configuration file for transfer with the Bulk CM IRP using either CORBA Solution Set of 3GPP TS 32.613 [3] or the SOAP Solution Set of 3GPP TS 32.617 [5]. For this application, the basic part of the XML file format definition is provided by 3GPP TS 32.615 [4].
Other applications of these XML definitions are the SOAP solution sets of other IRPs that perform operations on managed objects, for example the Basic CM IRP SOAP SS of 3GPP TS 32.607 [6].
|
32.763
|
Telecommunication management; Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Network Resource Model (NRM) Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)
|
TS
|
9.5.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.763/32763-950.zip
|
The present document is part of an Integration Reference Point (IRP) named E-UTRAN Network Resource Model (NRM) IRP, through which an IRPAgent can communicate configuration management information to one or several IRPManagers concerning E-UTRAN resources. The E-UTRAN NRM IRP comprises a set of specifications defining Requirements, a protocol neutral Information Service and one or more Solution Set(s).
The present document specifies the E-UTRAN Network Resources IRP: CORBA Solution Set, which defines the mapping of the IRP information model (see TS 32.762 [2]) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
This Solution Set is related to 3GPP TS 32.762 v9. 5.X.
|
32.765
|
Telecommunication management; Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Network Resource Model (NRM) Integration Reference Point (IRP); eXtensible Markup Language (XML) definitions
|
TS
|
9.6.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.765/32765-960.zip
|
The present document provides the XML definitions for the E-UTRAN Network Resource Model IRP IS [2].
An application of these XML definitions is to build a configuration file for transfer with the Bulk CM IRP using either CORBA Solution Set of 3GPP TS 32.613 [3] or the SOAP Solution Set of 3GPP TS 32.617 [5]. For this application, the basic part of the XML file format definition is provided by 3GPP TS 32.615 [4].
Other applications of these XML definitions are the SOAP solution sets of other IRPs that perform operations on managed objects, for example the Basic CM IRP SOAP SS of 3GPP TS 32.607 [6].
This specification is related to 3GPP TS 32.762 V9. 5.X.
|
32.773
|
Telecommunication management; Home Node B (HNB) Subsystem (HNS); Network Resource Model (NRM); Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS)
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.773/32773-900.zip
|
The present document is part of an Integration Reference Point (IRP) named HNS Network Resource Model (NRM) IRP, through which an IRPAgent can communicate configuration management information to one or several IRPManagers concerning HNS resources. The HNS NRM IRP comprises a set of specifications defining Requirements, a protocol neutral Information Service and one or more Solution Set(s).
The present document specifies the HNS Network Resources IRP: CORBA Solution Set, which defines the mapping of the IRP information model (see TS 32.772 [5]) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
|
32.775
|
Telecommunication management; Home Node B (HNB) Subsystem (HNS); Network Resource Model (NRM); Integration Reference Point (IRP); eXtensible Markup Language (XML) file format definition
|
TS
|
9.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.775/32775-910.zip
| |
32.783
|
Telecommunication management; Home enhanced Node B (HeNB) Subsystem (HeNS); Network Resource Model (NRM); Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS)
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.783/32783-900.zip
|
The present document is part of an Integration Reference Point (IRP) named HeNS Network Resource Model (NRM) IRP, through which an IRPAgent can communicate configuration management information to one or several IRPManagers concerning HeNS resources. The HeNS NRM IRP comprises a set of specifications defining Requirements, a protocol neutral Information Service and one or more Solution Set(s).
The present document specifies the HeNS Network Resources IRP: CORBA Solution Set, which defines the mapping of the IRP information model (see TS 32.782 [2]) to the protocol specific details necessary for implementation of this IRP in a CORBA/IDL environment.
|
32.785
|
Telecommunication management; Home enhanced Node B (HeNB) Subsystem (HeNS); Network Resource Model (NRM); Integration Reference Point (IRP); Bulk CM eXtensible Markup Language (XML) file format definition
|
TS
|
9.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.785/32785-910.zip
|
The present document provides the XML file format definition for the HeNS Network Resource Model IRP IS [2].
An application of these XML definitions is to build a configuration file for transfer with the Bulk CM IRP using either CORBA Solution Set of 3GPP TS 32.613 [3] or the SOAP Solution Set of 3GPP TS 32.617 [5]. For this application, the basic part of the XML file format definition is provided by 3GPP TS 32.615 [4].
Other applications of these XML definitions are the SOAP solution sets of other IRPs that perform operations on managed objects, for example the Basic CM IRP SOAP SS of 3GPP TS 32.607 [6].
|
32.821
|
Telecommunication management; Study of Self-Organizing Networks (SON) related Operations, Administration and Maintenance (OAM) for Home Node B (HNB)
|
TR
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.821/32821-900.zip
|
The present document intends to study the following:
1) Define SON OAM solution architecture for both LTE and UMTS home NodeB.
2) Identify differences between SON OAM solution architecture for LTE Marco eNodeB and that for LTE and UMTS home NodeB; Propose aligned SON OAM solution architecture.
3) Identify what can be standardized for SON for LTE and UMTS NodeB in 3GPP SA5.
4) Prepare the work for a later implementation work item.
|
32.822
|
Telecommunication management; Study on System Maintenance over Itf-N
|
TR
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.822/32822-900.zip
|
The present document studies key maintenance functions of element management system (EMS) in order to decide which one is necessary and could be managed over Itf-N, and makes a set of recommendations.
|
32.823
|
Telecommunication management; Self-Organizing Networks (SON); Study on self-healing
|
TR
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.823/32823-900.zip
|
The present document is focused on studying on self-healing of SON. This study provides the general procedure of self-healing, and collects the use cases of self-healing and proposed related requirements. The findings and proposals of the study may be used to help generate new Technical Specifications (TS) and/or enhance existing Technical Specifications.
|
32.824
|
Telecommunication management; Service Oriented Architecture (SOA) Integration Reference Point (IRP) study
|
TR
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.824/32824-900.zip
|
Service Oriented Architecture (SOA) is gaining acceptance in the IS/IT industry. It promises to manage change [1], automate and simplify IT processes [1], optimize implementation [2], maximize (implementation) flexibility and scalability [3], facilitate integration beyond the enterprise (between companies, between partners and customers) [4], simplify development [5] and maintenance; etc.
IRP (Interface Reference Point) is the predominant standard for wireless network management since 2000. 3GPP developed it with 3GPP2 close collaboration. IRP architecture follows closely with that defined by ITU-T TMN work [6]. Besides publishing the IRP specifications, 3GPP also publishes its IRP methodology (e.g., the guidelines, templates on how to develop, maintain and publish IRP specifications). Today, the IRP specification methodology is being shared and jointly evolved and maintained by consortium of SDOs, such as ITU-T.
We note that the principles of SOA are currently being applied to the field of network management [11,12,16,17].
The purpose of this document is to analyse the IRP architecture and to provide a "gap analysis" on what enhancement is needed for the current set of IRP specifications such that it can claim to have the full set of characteristics of SOA.
|
33.812
|
Feasibility study on the security aspects of remote provisioning and change of subscription for Machine to Machine (M2M) equipment
|
TR
|
9.2.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.812/33812-920.zip
|
The scope of this Technical Report is to study the remote subscription management for M2M Equipment (M2ME) when the Machine Communications Identity Module (MCIM) application resides in the UICC and when the MCIM application resides in the M2M equipment. The remote subscription management includes tasks such as remote subscription provisioning and/or remote change of subscription.
The scope of this study includes the definition of a trust model for remote subscription management for M2ME.Security threats and security requirements are identified, and an evaluation of the candidate solutions is presented.
The security implications of the following requirements are within the scope of the study (based on section 5.2.2 of TR 22.868)
1. The possibility to change subscription for M2MEs out in the field (e.g. after contract expiry) without direct human intervention.
2. The possibility to allocate the M2ME at initial power up to a network operator without direct human intervention.
Furthermore, this study includes the following items:
- an investigation of candidate security solutions architectures that allow remote subscription management to take place in a secure manner;
- an identification of current USIM/ISIM functionality that may need to be incorporated in a MCIM application, with or without changes to allow remote subscription management for the M2ME;
- an identification of functionality in the network, in the UICC or in the M2ME, that may need to be added due to the remote subscription management method;
- the study may identify principle requirements for protected storage and the execution environment (e.g. by collaborating with relevant working groups such as the OMTP Hardware group)
This study is beyond the scope of the first requirement identified in SA1 TR 22.868 since section 5.2.2 of TR 22.868 contains a requirement to have "Tamper Save/Theft proof terminal including a UICC".
|
33.821
|
Rationale and track of security decisions in Long Term Evolution (LTE) RAN / 3GPP System Architecture Evolution (SAE)
|
TR
|
9.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.821/33821-900.zip
|
The scope of this 3GPP Technical Report is rationale and track of security decisions in Long Term Evolved (LTE) RAN and 3GPP System Architecture Evolution (SAE) for release 8.
Disclaimer: This TR reflects the discussions held in 3GPP SA3 while 3GPP SA3 was working towards TS 33.401. This TR is useful to better understand the basis on which decisions in TS 33.401 were taken, and the alternatives that were discussed towards the decision. Some of the text in this TR reflected 3GPP SA3’s decision. However 3GPP’s position on EPS Security Architecture is reflected in the normative text in TS 33.401.
|
34.171
|
Terminal conformance specification; Assisted Global Positioning System (A-GPS); Frequency Division Duplex (FDD)
|
TS
|
9.4.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/34_series/34.171/34171-940.zip
|
The present document specifies the measurement procedures for the conformance test of the minimum performance requirements for FDD mode of UTRA user equipment (UE) where the only Assisted Global Navigation Satellite System (A-GNSS) supported is Assisted Global Positioning System (A-GPS) L1 C/A. The procedures for UEs that support other or additional A-GNSSs are specified in 3GPP TS 34.172 [18].
Tests are only applicable to those mobiles that are intended to support the appropriate functionality. To indicate the circumstances in which tests apply, this is noted in the "definition and applicability" part of the test.
|
36.800
|
Universal Terrestrial Radio Access (UTRA) and Evolved Universal Terrestrial Radio Access (E-UTRA); Extended UMTS / LTE 800 Work Item Technical Report
|
TR
|
9.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.800/36800-900.zip
|
The present document is a technical report of the Extended UMTS/LTE 800 work item, which was established at TSG RAN#42. The objective of this work item is to provide UTRA and E-UTRA specification support for FDD in the Extended 800 MHz band in Japan. In addition to the schedule and status of the work items, the report includes a description of the motivation, requirements, study results and specification recommendations.
|
36.805
|
Evolved Universal Terrestrial Radio Access (E-UTRA); Study on minimization of drive-tests in next generation networks
|
TR
|
9.0.0
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.805/36805-900.zip
|
The present document is intended to capture findings produced in the context of the Feasibility Study on Minimization of Drive-Tests (MDT) in next generation networks.
The study aims at assessing the feasibility, benefits and complexity of automating the collection of UE measurements to minimize the need of manual drive-tests. The work under this study should take the following steps.
1. Define use cases and requirements for minimizing drive tests in next generation LTE/HSPA networks
2. Based on the defined use cases and requirements, study the necessity of defining new UE measurements logging and reporting capabilities for minimizing drive tests and analyse the impact on the UE
Policy control mechanism and transport mechanism (including message syntax) for the new UE measurement logging and reporting capabilities are outside of the scope of the study. The study should focus on new logging and reporting capabilities for measurements already available at the UE.
|
36.806
|
Evolved Universal Terrestrial Radio Access (E-UTRA); Relay architectures for E-UTRA (LTE-Advanced)
|
TR
|
9.0.0
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.806/36806-900.zip
|
The present document is related to the study item “Further advancements for E-UTRA” [2].
The document describes relay architectures being discussed for E-UTRA (LTE-Advanced).
|
36.810
|
Universal Terrestrial Radio Access (UTRA) and Evolved Universal Terrestrial Radio Access (E-UTRA); UMTS / LTE in 800 MHz for Europe
|
TR
|
9.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.810/36810-900.zip
|
The present document is a technical report of the "UMTS/LTE in 800 MHz for Europe" work item which was approved at TSG RAN #43 [2]. The purpose of this work item is to provide specification support for LTE and UMTS with paired channel arrangement in the band 790-862 MHz.
The report provides motivation for requirements and a list of recommended changes to the specifications.
|
36.814
|
Evolved Universal Terrestrial Radio Access (E-UTRA); Further advancements for E-UTRA physical layer aspects
|
TR
|
9.2.0
|
R1
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.814/36814-920.zip
|
This document is related to the technical report for physical layer aspect of the study item “Further advancements for E-UTRA” [1]. The purpose of this TR is to help TSG RAN WG1 to define and describe the potential physical layer evolution under consideration and compare the benefits of each evolution techniques, along with the complexity evaluation of each technique.
This activity involves the Radio Access work area of the 3GPP studies and has impacts both on the Mobile Equipment and Access Network of the 3GPP systems.
This document is intended to gather all information in order to compare the solutions and gains vs. complexity, and draw a conclusion on way forward.
This document is a ‘living’ document, i.e. it is permanently updated and presented to TSG-RAN meetings.
|
36.815
|
Further Advancements for E-UTRA; LTE-Advanced feasibility studies in RAN WG4
|
TR
|
9.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.815/36815-910.zip
|
The present document is the technical report on "LTE-Advanced Feasibility Studies in 3GPP RAN WG4".
In particular it facilitates within TSG RAN the preparation of the ITU-R submission template with the parameters which are considered as RAN4 responsibility. The ITU-R submission template and its responsibility across the WGs is captured in [3] and discussed in RAN. The ITU-R submission template has been copied in Annex A.1.
This document is intended to gather the relevant background information in order to address critical UE and BS RF requirements and draw a conclusion on the feasibility of the identified RF scenarios and parameters.
|
36.821
|
Extended UMTS/LTE 1500 work item technical report
|
TR
|
9.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.821/36821-910.zip
|
The present document is a technical report of the Extended UMTS/LTE 1500 work item, which was established at TSG RAN#44. The objective of this work item is to provide UTRA and E-UTRA specification support for FDD in the Extended 1500 MHz band in Japan. In addition to the schedule and status of the work items, the report includes a description of the motivation, requirements, study results and specification recommendations.
|
36.902
|
Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Self-configuring and self-optimizing network (SON) use cases and solutions
|
TR
|
9.3.1
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.902/36902-931.zip
|
The present document provides descriptions of agreed use cases and solutions with regards to self configuring and self optimizing networks.
The scope of the self configuring and self optimizing functionality is defined in TS 36.300 [2].
|
36.938
|
Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Improved network controlled mobility between E-UTRAN and 3GPP2/mobile WiMAX radio technologies
|
TR
|
9.0.0
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.938/36938-900.zip
|
It is expected that IP based 3GPP services will be provided through various access technologies, including existing broadband radio access standards like IEEE 802.16e/ETSI BRAN, and 3GPP2 including HRPD and 1xRTT. In order to achieve this, inter-technology mobility between E-UTRAN and 3GPP2/Mobile WiMAX is considered in the study item "Improved Network Controlled Mobility between E-UTRAN and 3GPP2/Mobile WiMAX Radio Technologies".
The purpose of this TR is to help TSG RAN to capture a stage 2 level solution for each of the studied mobility scenarios, which can be used as a basis to initiate the stage 3 work when moving to the work item phase. This activity involves the Radio Access Network work area of the 3GPP studies for mobility and has impacts on both the Mobile Equipment and Access Network of the 3GPP systems. Architecture impact involving non-RAN nodes is under the responsibility of SA2.
|
22.112
|
USIM Application Toolkit (USAT) Interpreter; Stage 1
|
TS
|
8.0.0
|
C6
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.112/22112-800.zip
|
The present document specifies a system to make Mobile Operator services, based on USAT functionality and USIM based security functionality, available to an internet environment. This is achieved by specifying the necessary components and protocols for a secure narrow band channel between the internet application and an USAT Interpreter on the USIM. The actual application could be developed using the application language of choice. Two types of applications interfaces are used as examples, i.e., mark-up language based on WML and Remote Procedure Call (RPC).
The interpreter and the secure narrow band channel form a core platform to enable services like:
- Advanced security functionality, e.g., digital signatures in m-commerce applications
- Value added services based on position and roaming
- Controlled activation and management of other applications, e.g. multimedia and payment type of applications.
The secure narrow band channel is achieved by specifying the following:
- specific application and content related functionalities of the interface between the application system and the USAT Gateway;
- specific functionalities and protocols of the interface between the USAT Gateway and the USAT Interpreter associated with a USIM, achieved by defining a low level command set for interpretation by the USAT Interpreter;
- defined level of functionality available to the application server for the implementation of USIM based services such as PKI, location services, push and broadcast services, event based services, etc..
The present document does not specify any elements of the protocol stack between the application server and the USAT Gateway, the mark-up language definition, and the transport protocols between the USAT Gateway and the USAT Interpreter.
|
22.168
|
Earthquake and Tsunami Warning System (ETWS) requirements; Stage 1
|
TS
|
8.3.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.168/22168-830.zip
|
This Technical Specification defines the stage one description of the Earthquake and Tsunami Warning System (ETWS) Requirements. Stage one is the set of requirements seen primarily from the users’ and service providers’ points of view.
This TS includes information applicable to network operators, service providers, terminal and network manufacturers, in case of deployment of ETWS. ETWS deployment depends on operator decision or national regulations.
This TS contains the core requirements for the Earthquake and Tsunami Warning System, which are sufficient to provide a complete service.
This TS also contains regional requirements for Earthquake and Tsunami Warning System.
|
22.401
|
TISPAN; Videotelephony over NGN Service Description
|
TS
|
8.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.401/22401-800.zip
|
The present document defines the requirements for a videotelephony service which may be supported by a TISPAN NGN. These requirements form the basis for the definition of network capabilities.
The present document provides interoperability service requirements for interconnection between existing networks and a TISPAN NGN, and between TISPAN NGN.
The present document only provides requirements for IP multimedia based networks. Services provided by a TISPAN NGN to support legacy terminals and interfaces (PSTN/ISDN emulation) are defined in existing PSTN/ISDN documents. Requirements for PSTN/ISDN emulation are out of scope of the present document and are described in other documents.
The applicability of PSTN/ISDN simulation services to the videotelephony service requirements are defined in the present document.
The requirements in the present document are described from the user point of view. The requirements do not take into account capabilities of existing protocols defined for the IMS. The evolution or modifications to these protocols are beyond the scope of the present document.
NOTE: The present document uses the term "NGN" only in the context of TISPAN.
|
22.868
|
Study on facilitating machine to machine communication in 3GPP systems
|
TR
|
8.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.868/22868-800.zip
|
The present document identifies potential requirements to facilitate improvements in M2M communication and the more efficient use of radio and network resources.
Special consideration is given to the following areas for optimisation:
- Charging mechanisms
- Addressing
- Types of communication
- Fixed location, low mobility and low activity terminals
- Handling of large numbers of subscriptions and subscriber data within the network
- Handling issues of large number of M2M subscriptions for the user of M2M services
- Impact of optimisations for security resulting from improvement for M2M
|
22.892
|
Study on IMS Centralized Services (ICS) requirements
|
TR
|
8.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.892/22892-800.zip
|
The present document provides a study of the service experience and suggested service requirements for IP Multimedia System (IMS) Centralized Services (ICS). ICS enables the delivery of IMS based services to users regardless of the attached access network type; e.g. CS domain access or IP Based Access Networks. Service continuity between access networks is also considered. User and service provider perspectives are considered along with service scenarios as the basis for identifying service requirements. Based on the previous considerations, service requirements are identified and conclusions are drawn.
|
23.506
|
TISPAN; IP Multimedia Subsystem (IMS); Stage 2 description [3GPP TS 23.228 Release 7, modified]
|
TS
|
8.1.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.506/23506-810.zip
|
The present document provides the ETSI endorsement of the 3GPP TS 23.228 "IP Multimedia Subsystem; Stage 2, Release 7".
The present document provides the necessary adaptions to the 3GPP IP Multimedia Core Network Subsystem (IMS), in order to support the Access Networks and terminals in the scope of the present NGN Release. The present document also includes certain elements from 3GPP Release 8 (TS 23.228 v8.2.0)
|
23.507
|
TISPAN; Voice Call Continuity (VCC); Stage 2 [3GPP TS 23.206 Release 7, modified]
|
TS
|
8.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.507/23507-800.zip
|
The present document provides the ETSI TISPAN endorsement of 3GPP TS.23.206 [3] " Voice Call Continuity (VCC) between Circuit Switched (CS) and IP Multimedia Subsystem (IMS); Stage 2: Release 7”.
The current VCC solution explained in the TS.23.206 is essentially defined for a core IMS provider that is a mobile operator (that has also CS domain). In Informative Annex ZA theres is a possible scenario how the solution can be extended to a generic IMS operator (e.g. when fixed network operator and CS mobile network operator are separate organisations).
|
23.508
|
TISPAN; Presence Service; Architecture and functional description [Endorsement of 3GPP TS 23.141 and OMA-AD-Presence_SIMPLE-V1_0]
|
TS
|
8.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.508/23508-800.zip
|
(Void)
|
23.509
|
TISPAN; NGN Architecture to support emergency communication from citizen to authority [Endorsed document 3GPP TS 23.167, Release 7]
|
TS
|
8.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.509/23509-800.zip
|
The present document provides the ETSI endorsement of the 3GPP TS 23.167 [1].
The present document defines the architectural description for emergency services in the IP Multimedia Core Network Subsystem (IMS), including the elements necessary to support IP Multimedia (IM) emergency services
The present document covers also the Access Network aspects that are crucial for the provisioning of IMS emergency services.
|
23.511
|
TISPAN; XML Document Management; Architecture and functional description [OMA-AD-XDM-V1_0-20051006-C modified]
|
TS
|
8.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.511/23511-800.zip
|
(Void)
|
23.517
|
TISPAN; IP Multimedia Subsystem (IMS); Functional architecture
|
TS
|
8.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.517/23517-800.zip
|
The present document describes the IP Multimedia Subsystem (IMS) core component of the TISPAN NGN functional architecture and its relationships to other subsystems and components.
|
23.521
|
Telecommunications and Internet converged Services and Protocols for Advanced Networks (TISPAN); Support of Short Message Service (SMS) over NGN IMS subsystem; Stage 2; [Endorsement of 3GPP TS 23.204 Release 7]
|
TS
|
8.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.521/23521-800.zip
|
The present document provides the ETSI TISPAN endorsement of 3GPP TS.23.204 [1] "Support of Short Message Service (SMS) over generic 3GPP Internet Protocol (IP) access; Stage 2 (Release 7)”.
|
23.611
|
TISPAN; XML Document Management; Architecture and functional description [OMA-AD-XDM-V1_0-20051006-C modified]
|
TS
|
8.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.611/23611-800.zip
|
(Void)
|
23.810
|
Study on architecture impacts of Service Brokering
|
TR
|
8.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.810/23810-800.zip
|
The objective is to study if there is enhancement needed to the current service interaction management architecture (e.g. SCIM as part of AS and Service Broker as part of OSA SCS) in order to satisfy requirements in TS 22.228 [1].
This technical report contains the results of a study on service interaction management architecture with focus on the following aspects:
- considering through scenarios, if the current service interaction management architecture sufficiently manages interactions between application servers, within the Home Network or on third party servers, and
- determine, through a functional element architecture study, whether there is a need for enhancement of the architecture, as well as any required extensions to the current IMS protocols and procedures.
In addition, alternative mechanisms to improve preventing interacting services may be identified.
|
23.811
|
Service level interworking for messaging services; Stage 2
|
TR
|
8.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.811/23811-800.zip
|
This document contains the results of the study into the architectural requirements and comes up with the solution of the service level interworking for the Short Message service as defined in the TS 23.040 [6] and Instant Messaging service as defined in OMA-TS-SIMPLE_IM-V1_20070816-C [8]. Considerations include overall requirements, architectural requirements, evaluation of potential architectural solutions and alternative architectures.
The objective is to identify an architectural solution that allows completely service level interworking between SMS and SIMPLE IM without degrading existing services, under the service requirements defined in the TS 22.340 [2] and TS 22.105 [3]. In addition, how to charge for the interworked services shall be considered in this study as well.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.