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
|
|---|---|---|---|---|---|---|
29.199-05
|
Open Service Access (OSA); Parlay X web services; Part 5: Multimedia messaging
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-05/29199-05-900.zip
|
The present document is Part 5 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Multimedia Messaging Web Service aspects of the interface. All aspects of the Multimedia Messaging Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL Description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.199-06
|
Open Service Access (OSA); Parlay X web services; Part 6: Payment
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-06/29199-06-900.zip
|
The present document is Part 6 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Payment Web Service aspects of the interface. All aspects of the Payment Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL Description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.199-07
|
Open Service Access (OSA); Parlay X web services; Part 7: Account management
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-07/29199-07-900.zip
|
The present document is Part 7 of the Stage 3 Parlay X Web Service specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Account Management Web Service aspects of the interface. All aspects of the Account Management Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL Description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.199-08
|
Open Service Access (OSA); Parlay X web services; Part 8: Terminal status
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-08/29199-08-900.zip
|
The present document is Part 8 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Terminal Status Web Service aspects of the interface. All aspects of the Terminal Status Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL Description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.199-09
|
Open Service Access (OSA); Parlay X web services; Part 9: Terminal location
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-09/29199-09-900.zip
|
The present document is Part 9 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Terminal Location Web Service aspects of the interface. All aspects of the Terminal Location Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL Description of the interfaces.
The present document has been defined jointly between 3GPP TSG CN WG5, ETSI TISPAN and The Parlay Group.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.199-10
|
Open Service Access (OSA); Parlay X web services; Part 10: Call handling
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-10/29199-10-900.zip
|
The present document is Part 10 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Call Handling Web Service aspects of the interface. All aspects of the Call Handling Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL Description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.199-11
|
Open Service Access (OSA); Parlay X web services; Part 11: Audio call
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-11/29199-11-900.zip
|
The present document is Part 11 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Audio Call Web Service aspects of the interface. All aspects of the Audio Call Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL Description of the interfaces.
The web service had been extended to support media.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
|
29.199-12
|
Open Service Access (OSA); Parlay X web services; Part 12: Multimedia conference
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-12/29199-12-900.zip
|
The present document is Part 12 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Multimedia Conference Web Service aspects of the interface. All aspects of the Multimedia Conference Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL Description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.199-13
|
Open Service Access (OSA); Parlay X web services; Part 13: Address list management
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-13/29199-13-900.zip
|
The present document is Part 13 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Address List Management Web Service aspects of the interface. All aspects of the Address List Management Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
|
29.199-14
|
Open Service Access (OSA); Parlay X web services; Part 14: Presence
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-14/29199-14-900.zip
|
The present document is Part 14 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Presence Web Service aspects of the interface. All aspects of the Presence Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL Description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and the Parlay Consortium.
|
29.199-15
|
Open Service Access (OSA); Parlay X web services; Part 15: Message broadcast
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-15/29199-15-900.zip
|
The present document is Part 15 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Message Broadcast Web Service aspects of the interface. All aspects of the Message Broadcast Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.199-16
|
Open Service Access (OSA); Parlay X web services; Part 16: Geocoding
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-16/29199-16-900.zip
|
The present document is Part 16 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Geocoding Web Service aspects of the interface. All aspects of the Geocoding Web Service are defined here, these being:
• Name spaces
• Sequence diagrams
• Data definitions
• Interface specification plus detailed method descriptions
• Fault definitions
• Service policies
• WSDL Description of the interfaces
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.199-17
|
Open Service Access (OSA); Parlay X web services; Part 17: Application-driven Quality of Service (QoS)
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-17/29199-17-900.zip
|
The present document is Part 17 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Application-driven Quality of Service (QoS) Web Service aspects of the interface. All aspects of the Application-driven QoS Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL Description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.199-18
|
Open Service Access (OSA); Parlay X web services; Part 18: Device capabilities and configuration
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-18/29199-18-900.zip
|
The present document is Part 18 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Device Capabilities and Configuration Web Service aspects of the interface. All aspects of the Device Capabilities and Configuration Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.199-19
|
Open Service Access (OSA); Parlay X web services; Part 19: Multimedia streaming control
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-19/29199-19-900.zip
|
The present document is Part 19 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Multimedia streaming control Web Service aspects of the interface. All aspects of the Multimedia streaming control Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.199-20
|
Open Service Access (OSA); Parlay X web services; Part 20: Multimedia multicast session management
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-20/29199-20-900.zip
|
The present document is Part 20 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Multimedia multicast session management Web Service aspects of the interface. All aspects of the Multimedia multicast session management Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008.
|
29.199-21
|
Open Service Access (OSA); Parlay X web services; Part 21: Content management
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-21/29199-21-900.zip
|
The present document is Part 21 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Multimedia multicast session management Web Service aspects of the interface. All aspects of the Multimedia multicast session management Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL description of the interfaces.
The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.
|
29.199-22
|
Open Service Access (OSA); Parlay X web services; Part 22: Policy
|
TS
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.199-22/29199-22-900.zip
|
The present document is Part 22 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Policy Web Service aspects of the interface. All aspects of the Policy Web Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL description of the interfaces.
|
29.998-01
|
Open Service Access (OSA); Application Programming Interface (API) mapping for OSA; Part 1: General issues on API mapping
|
TR
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-01/29998-01-900.zip
|
The present document is suggesting a mapping of the Application Programming Interface (API) for Open Service Access (OSA) onto CAMEL Application Part (CAP) operations and Mobile Application Part (MAP) operations, and provides an overview of the content and structure of the various parts of the present document. The mapping of the OSA API to the CAP and relevant MAP operations is considered informative and not normative.
The API specification is contained in the 3GPP TS 29.198 series of specifications. An overview of these is available in the introduction of the present document as well as in 3GPP TS 29.198-1 [1]. The concepts and the functional architecture for the Open Service Access (OSA) are described by 3GPP TS 23.198 [3]. The requirements for OSA are defined in 3GPP TS 22.127 [2].
|
29.998-04-1
|
Open Service Access (OSA); Application Programming Interface (API) Mapping for Open Service Access; Part 4: Call Control Service Mapping; Subpart 1: API to CAP Mapping
|
TR
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-04-1/29998-04-1-900.zip
|
The present document investigates how the OSA Call Control Interface Class methods defined in 3GPP TS 29.198-4 [5] can be mapped onto CAMEL Application Part (CAP) operations and Mobile Application Part (MAP) operations.
The mapping of the OSA API to the CAP and relevant MAP operations is considered informative, and not normative. An overview of the mapping TR is contained in the introduction of the present document as well as in 3GPP TR 29.998-1 [10].
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardised interface, i.e. the OSA APIs. The API specification is contained in the 3GPP TS 29.198 series of specifications. An overview of these is available in the introduction of the present document as well as in 3GPP TS 29.198-1 [1]. The concepts and the functional architecture for the Open Service Access (OSA) are described by 3GPP TS 23.198 [3]. The requirements for OSA are defined in 3GPP TS 22.127 [2].
|
29.998-04-4
|
Open Service Access (OSA); Application Programming Interface (API) Mapping for Open Service Access; Part 4: Call Control Service Mapping; Subpart 4: Multiparty Call Control ISC
|
TR
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-04-4/29998-04-4-900.zip
|
The present document investigates how the OSA Call Control Interface Class methods defined in [5] can be mapped onto SIP methods.
The mapping of the OSA API to the SIP is considered informative, and not normative. An overview of the mapping TR is contained in the introduction of the present document as well as in 3GPP TR 29.998-1 [10].
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardised interface, i.e. the OSA APIs. The API specification is contained in the 3GPP TS 29.198 series of specifications. An overview of these is available in the introduction of the present document as well as in 3GPP TS 29.198-1 [1]. The concepts and the functional architecture for the Open Service Access (OSA) are described by 3GPP TS 23.198 [3]. The requirements for OSA are defined in 3GPP TS 22.127 [2].
|
29.998-05-1
|
Open Service Access (OSA); Application Programming Interface (API) Mapping for Open Service Access; Part 5: User Interaction Service Mapping; Subpart 1: API to CAP Mapping
|
TR
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-05-1/29998-05-1-900.zip
|
The present document investigates how the OSA User Interaction Interface Class methods defined in 3GPP TS 29.198‑5 [5] can be mapped onto CAMEL Application Part operations and Mobile Application Part operations.
The mapping of the OSA API to the CAP and relevant MAP operations is considered informative, and not normative. An overview of the mapping TR is contained in the introduction of the present document as well as in 3GPP TR 29.998-1 [10].
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardised interface, i.e. the OSA APIs. The API specification is contained in the 3GPP TS 29.198 series of specifications. An overview of these is available in the introduction of the present document as well as in 3GPP TS 29.198-1 [1]. The concepts and the functional architecture for the Open Service Access (OSA) are described by 3GPP TS 23.198 [3]. The requirements for OSA are defined in 3GPP TS 22.127 [2].
|
29.998-05-4
|
Open Service Access (OSA); Application Programming Interface (API) Mapping for Open Service Access; Part 5: User Interaction Service Mapping; Subpart 4: API to SMS Mapping
|
TR
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-05-4/29998-05-4-900.zip
|
The present document investigates how the OSA User Interaction Interface Class methods defined in 3GPP TS 29.198‑5 [5] can be mapped onto CAMEL Application Part operations and Mobile Application Part operations, within the context of SMS. The mapping of the OSA API to the CAP and relevant MAP operations is considered informative, and not normative. An overview of the mapping TR is contained in the introduction of the present document as well as in 3GPP TR 29.998-1 [10].
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardised interface, i.e. the OSA API's. The API specification is contained in the 3GPP TS 29.198 series of specifications. An overview of these is available in the introduction of the present document as well as in 3GPP TS 29.198-1 [1]. The concepts and the functional architecture for the Open Service Access (OSA) are described by 3GPP TS 23.198 [3]. The requirements for OSA are defined in 3GPP TS 22.127 [2].
|
29.998-06-1
|
Open Service Access (OSA); Application Programming Interface (API) Mapping for Open Service Access; Part 6: User location - user status service mapping; Subpart 1: Mapping to Mobile Application Part (MAP)
|
TR
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-06-1/29998-06-1-900.zip
|
The present document investigates how the OSA Mobility Interface Class methods defined in 3GPP TS 29.198-6 [5] can be mapped onto CAMEL Application Part (CAP) operations and Mobile Application Part (MAP) operations.
The mapping of the OSA API to the CAP and relevant MAP operations is considered informative, and not normative. An overview of the mapping TR is contained in the introduction of the present document as well as in 3GPP TR 29.998-1 [10].
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardised interface, i.e. the OSA API's. The API specification is contained in the 3GPP TS 29.198 series of specifications. An overview of these is available in the introduction of the present document as well as in 3GPP TS 29.198-1 [1]. The concepts and the functional architecture for the Open Service Access (OSA) are described by 3GPP TS 23.198 [3]. The requirements for OSA are defined in 3GPP TS 22.127 [2].
|
29.998-06-2
|
Open Service Access (OSA); Application Programming Interface (API) Mapping for Open Service Access; Part 6: User location - user status service mapping; Subpart 2: Mapping to Session Initiation Protocol (SIP)
|
TR
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-06-2/29998-06-2-900.zip
|
The present document investigates how the OSA Mobility Interface Class methods defined in 3GPP TS 29.198-6 [5] can be mapped onto IMS ISC Interface (SIP) operations.
The mapping of the OSA API to the SIP is considered informative, and not normative. An overview of the mapping TR is contained in the introduction of the present document as well as in 3GPP TR 29.998-1 [10].
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardised interface, i.e. the OSA API's. The API specification is contained in the 3GPP TS 29.198 series of specifications. An overview of these is available in the introduction of the present document as well as in 3GPP TS 29.198-1 [1]. The concepts and the functional architecture for the Open Service Access (OSA) are described by 3GPP TS 23.198 [3]. The requirements for OSA are defined in 3GPP TS 22.127 [2].
|
29.998-08
|
Open Service Access (OSA); Application Programming Interface (API) Mapping for Open Service Access; Part 8: Data Session Control Service Mapping to CAP
|
TR
|
9.0.0
|
CP
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.998-08/29998-08-900.zip
|
The present document investigates how the OSA Data Session Control Interface Class methods defined in 3GPP TS 29.198-8 [5] can be mapped onto CAMEL Application Part operations and Mobile Application Part operations.
The mapping of the OSA API to the CAP and relevant MAP operations is considered informative, and not normative. An overview of the mapping TR is contained in the introduction of the present document as well as in 3GPP TR 29.998-1 [10].
The OSA specifications define an architecture that enables application developers to make use of network functionality through an open standardised interface, i.e. the OSA APIs. The API specification is contained in the 3GPP TS 29.198 series of specifications. An overview of these is available in the introduction of the present document as well as in 3GPP TS 29.198-1 [1]. The concepts and the functional architecture for the Open Service Access (OSA) are described by 3GPP TS 23.198 [3]. The requirements for OSA are defined in 3GPP TS 22.127 [2].
|
30.819
|
Telecommunication management; Project scheduling and open issues for SA5, Release 9
|
TR
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/30_series/30.819/30819-900.zip
|
The present document contains the up-to-date SA5 Work Item Descriptions (WIDs) and captures the status of all SA5 work items in the current Release.
This TR is used as a mean to provide input to the 3GPP work plan handled by MCC.
|
32.111-3
|
Telecommunication management; Fault Management; Part 3: Alarm 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.111-3/32111-3-910.zip
|
The present contains the CORBA Solution Set for the IRP whose semantics is specified in Alarm IRP: Information Service (TS 32.111-2 [6]).
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.111-2 V7.1.X.
|
32.111-5
|
Telecommunication management; Fault Management; Part 5: Alarm Integration Reference Point (IRP): eXtensible Markup Language (XML) definitions
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.111-5/32111-5-900.zip
|
The present document specifies the XML Definitions for the Alarm Integration Reference Point (Alarm IRP) as it applies to Itf-N, in accordance with Alarm IRP IS definitions [3] as well as Notification Log IRP XML Definitions [4].
The present document defines the XML syntax of Alarm IRP notifications that is to be used for the Alarm IRP SOAP Solution Set and in conjunction with Notification Log IRP XML Definitions for Notification Log IRP XML Data File and the NL IRP XML Notification Format [4]. The document defines also the XML syntax for the IOC definitions of the Alarm IRP IS [3], which are used by the XML definitions for the Alarm IRP notifications and the Alarm IRP IS operations.
This specification is related to 3GPP TS 32.111-2 V9.0.X.
|
32.111-7
|
Telecommunication management; Fault Management; Part 7: Alarm IRP SOAP Solution Set (SS)
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.111-7/32111-7-900.zip
|
The present document specifies the SOAP Solution Set for the IRP whose semantics are specified in Alarm IRP: Information Service (3GPP TS 32.111-2 [4]).
This Solution Set specification is related to 3GPP TS 32.111-2 V9.0.X.
|
32.123
|
Telecommunication management; Advanced Alarm Management (AAM) 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.123/32123-900.zip
|
The purpose of Advanced Alarm Management (AAM) IRP is to define an interface through which an IRPManager can categorize alarm notifications.
The present document is the AAM IRP CORBA Solution Set, whose semantics are specified in AAM IRP Information Service (3GPP TS 32.122 [3]).
This Solution Set specification is related to TS 32.122 v9.0.0.
|
32.125
|
Telecommunication management; Advanced Alarm Management (AAM) Integration Reference Point (IRP): eXtensible Markup Language (XML) file format definition
|
TS
|
9.3.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.125/32125-930.zip
|
The purpose of Advanced Alarm Management (AAM) IRP is to define an interface through which an IRPManager can categorize alarm notifications.
The present document is the AAM IRP XML file format definition, whose semantics are specified in AAM IRP Information Service (3GPP TS 32.122 [3]).
This file format definition specification is related to TS 32.122 v9.0.X.
|
32.127
|
Telecommunication management; Advanced Alarm Management (AAM) Integration Reference Point (IRP); SOAP Solution Set (SS)
|
TS
|
9.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.127/32127-910.zip
|
The present specifies the SOAP Solution Set for the IRP whose semantics are specified in the Advanced Alarm Management (AAM) IRP Information Service (3GPP TS 32.122 [3]).
This Solution Set specification is related to TS 32.122 v9.0.X.
|
32.175
|
Telecommunication management; Subscription Management (SuM) Network Resource Model (NRM) Integration Reference Point (IRP): eXtensible Markup Language (XML) definition
|
TS
|
9.3.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.175/32175-930.zip
|
The purpose of this Subscription Management (SuM) Network Resource Model IRP XML definition is to define the mapping of the IRP information model (see TS 32.172 [5]) to the protocol specific details necessary for implementation of this IRP in an XML environment.
This specification is related to 3GPP TS 32.172 V9.3.X.
|
32.303
|
Telecommunication management; Configuration Management (CM); Notification 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.303/32303-900.zip
|
The present document specifies the Common Object Request Broker Architecture (CORBA) Solution Set (SS) for the IRP whose semantics is specified in Notification IRP: Information Service (3GPP TS 32.302 [5]).
This Solution Set specification is related to 3GPP TS 32.302.
|
32.305
|
Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP); eXtensible Markup Language (XML) definition
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.305/32305-900.zip
|
The present document specifies the XML Definitions for the Notification Integration Reference Point (Notification IRP) as it applies to Itf-N, in accordance with Notification IRP IS definitions [3].
This XML Definitions specification defines the Notification IRP XML Notification header format.
This specification is related to 3GPP TS 32.302 V9.0.X.
|
32.307
|
Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP); SOAP Solution Set (SS)
|
TS
|
9.2.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.307/32307-920.zip
|
The present document specifies the SOAP Solution Set for the IRP whose semantics is specified in Notification IRP: Information Service (3GPP TS 32.302 [4]).
This Solution Set specification is related to 3GPP TS 32.302 V9.0.X.
|
32.313
|
Telecommunication management; Generic Integration Reference Point (IRP) management; Common Object Request Broker Architecture (CORBA) Solution Set (SS)
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.313/32313-900.zip
|
The present document specifies the CORBA Solution Set for Generic Integration Reference Point (IRP) management whose capabilities are specified in 3GPP TS 32.312 [1], the Generic IRP management: Information Service.
This Solution Set specification is related to TS 32.312 V9.0.X.
|
32.317
|
Telecommunication management; Generic Integration Reference Point (IRP) management; SOAP Solution Set (SS)
|
TS
|
9.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.317/32317-910.zip
|
The present document specifies the SOAP Solution Set for Generic IRP management whose capabilities are specified in Generic IRP management: Information Service (3GPP TS 32.312 [1]).
This Solution Set specification is related to TS 32.312 V9.0.X.
|
32.323
|
Telecommunication management; Test 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.323/32323-900.zip
|
The present document specifies the CORBA SS for the IRP whose semantics is specified in Test Management IRP IS (3GPP TS 32.322 [6]).
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 3GPP TS 32.322 V9.0.X.
|
32.325
|
Telecommunication management; Test management Integration Reference Point (IRP); eXtensible Markup Language (XML) definitions
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.325/32325-900.zip
|
The present document specifies the XML Definitions for the Test Management IRP (TMIRP) as it applies to Itf-N, in accordance with TM IRP IS definitions [3] as well as Notification Log IRP XML Definitions [4].
This specification is related to 3GPP TS 32.322 V9.0.X.
|
32.327
|
Telecommunication management; Test management Integration Reference Point (IRP); SOAP Solution Set (SS)
|
TS
|
9.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.327/32327-900.zip
|
The present document specifies the SOAP SS for the IRP whose semantics is specified in Test Management IRP IS (3GPP TS 32.322 [5]).
This Solution Set specification is related to 3GPP TS 32.322 V9.0.X.
|
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.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.