7.15 Ims Restoration Procedures (ims_rp) uid_400012

Resources: C4,C1

References

Document	Title/Contents
WID(s)
CP-080447	WID on IMS Restoration Procedures
Impacted Specifications
TS 24.229	Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 - C1 [Added new information elements and detailed behaviour]
TS 29.228	IP Multimedia (IM) Subsystem Cx and Dx Interfaces; Signalling flows and message contents - C4 [Updated ABNF command]
TS 29.229	Cx and Dx interfaces based on the Diameter protocol; Protocol details - C4 [Defined new AVPs]
TS 29.230	Diameter applications; 3GPP specific codes and identifiers - C4 [Updated procedures of network elements handling SIP signalling]
New Dedicated Specifications/Reports
TS 23.380	IMS Restoration Procedures - C4

Supporting Individual Members: Ericsson, Vodafone, France Telecom, Huawei, Nortel, Hewlett-Packard, ZTE, Alcatel-Lucent.

UID	Name	Resource	Hyperlink	TS_TR
400012	IMS Restoration Procedures	C4,C1	CP-080447	-
400026	IMS Restoration Procedures	C4	CP-080447	23.380, 29.228, 29.229, 29.230, 23.008
400027	IMS Restoration Procedures	C1	CP-080447	24.229

This work is triggered by TR 23.820 Study on Restoration Procedures (FS_IMS_RP) UID_350018.

This work specifies the procedures recommended in TR 23.820, e.g. covering the S-CSCF service interruption scenario.

7.16 Ims Application Server Service Data Descriptions for as interoperability (ims_asio) uid_410003

Resources: C4

References

Document	Title/Contents
WID(s)
CP-080451	WID on IMS Application Server Service Data Descriptions for AS interoperability
Impacted Specifications
TS 29.328	IP Multimedia Subsystem (IMS) Sh interface; Signalling flows and message contents
TS 29.329	Sh interface based on the Diameter protocol; Protocol details
New Dedicated Specifications/Reports
TS 29.364	IP Multimedia Subsystem (IMS) Application Server (AS) service data descriptions for AS interoperability

Supporting Individual Members: Alcatel-Lucent, Verizon Wireless, Nortel Networks, Nokia-Siemens Networks, ZTE.

UID	Name	Resource	Hyperlink	TS_TR
410003	IMS Application Server Service Data Descriptions for AS interoperability	C4	CP-080451	29.328, 29.329, 29.364

This work is triggered by TR 29.864 Study on IMS Application Server (AS) service data descriptions for AS interoperability UID_360030 (FS_IMS_ASIO).

Application data for IMS is defined as being ‘Transparent'. Transparency in this case refers to the fact that the HSS, and the Sh interface, do not semantically understand the data just syntactically how to deal with its entirety. ASs are free to store data without an openly distributed definition of the stored content, however, because the data is transparent (the format is not standardized) it is potentially an issue for one AS to make use of data defined for another AS (e.g. the ASs are supplied by different vendors).

Standardizing the data formats facilitates interoperation among ASs supplied by the same, or different, vendors. These AS vendors may be primary and secondary suppliers of the same Service Provider (SP) within a SP's IMS network. This is especially true of mature services, such as the features provided in basic voice subscriptions, and is likely to be true of any future services that achieve a wide deployment.

There has already been work incorporated into 3GPP from TISPAN that point towards the need to define common data. The UE may update a service setting (e.g. a forwarded to number) in an AS via the Ut interface. The AS may store this information in transparent data in the HSS, but unless the data is defined it cannot be shared with other ASs.

Some benefits of standardizing the data formats for services:

1 Multi-vendor AS support.

Today's telecom SPs regularly use two or more vendors to provide identical capabilities. Standardization has facilitated this, as products must conform to the defined interfaces. Service providers use this to build competition among vendors and to build business contingencies. The AS market, especially for high penetration services, is expected to follow a similar path.

2 Data Synchronization

In defining IMS centralized services, interworking between the HLR/HSS and the Telephony Application Server may occur to exchange data that is administered in the CS domain and IMS. The definition of IMS AS service data descriptions facilitates this exchange.

3 Feature Interaction

Advertising and defining data for each application is expected to increase communication regarding features within applications. This will make the integration of complex features more likely to succeed, as the information is available to examine for interactions.

4 User re-homing and load balancing

To facilitate re-homing of users to application servers and load balancing, the definition of IMS AS service data descriptions increases the opportunity for hosting services on alternative ASs.

This work standardized the necessary components of an AS subscriber data definition by using the methods proposed in TR 29.864. These procedures enable applications to define, extend and publish data definitions.

Redefine the OMA XDM XML based data of the AS providing Presence, IM, etc. is out of the scope of this work.