10.9 Service-Level Interworking for Messaging Services (messiw) uid_340031

Resources: S1,S2,C3,C1

References

Document	Title/Contents
WID(s)
SP-070816	S1,S2 WID on Support of Service-Level Interworking for Messaging Services
CP-080575	C3 WID on Support of Service-Level Interworking for Messaging Services - Stage 3
Impacted Specifications
TS 22.105	Services and service capabilities - S1
TS 22.340	IP Multimedia Subsystem (IMS) messaging; Stage 1 - S1
TS 23.204	Support of Short Message Service (SMS) over generic 3GPP Internet Protocol (IP) access; Stage 2 - S2
TS 24.229	Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 - C1
TS 24.341	Support of SMS over IP networks; Stage 3 - C1 [Interaction with service level interworking at the IP-SM-GW. Cover interaction with service level interworking, Add reference to new stage 3 TS]
New Dedicated Specifications/Reports
TR 23.811	Service level interworking for messaging services; Stage 2 - S2
TS 29.311	Service Level Interworking for Messaging Services; Stage 3 - C3

Supporting Individual Members: Huawei, Comverse, China Mobile, BT, Ericsson, Telecom Italia, Orange, RIM, ZTE.

UID	Name	Resource	Hyperlink	TS_TR
340031	Service-Level Interworking for Messaging Services	S1,S2,C3,C1	SP-070816	-
350047	Stage 1 for MESSIW	S1	SP-070816	22.105, 22.340
350048	Stage 2 for MESSIW	S2	SP-070816	23.811, 23.204
400016	Stage 3 for MESSIW	C3	CP-080773	29.311
400017	Stage 3 for MESSIW	C1	CP-080773	24.229

There is interest in service-level interworking for messaging services, e.g. between Short Message (SM) and existing Instant Messaging (IM) services. Other types of messaging interworking need also to be considered.

This work 1st defines the scenarios for service-level interworking between:

• SMS and IM services;

• Interworking scenarios as requested by OMA in SP-060851;

In a 2nd step, it implements the solution(s) fulfilling the required service-level interworking scenarios and requirements.

This work considered with priority the following aspects:

• Provide a consistent service experience to the user when service-level interworking takes place;

• Determine the scenarios where this service-level interworking is applicable;

• Provide requirements for suitable security mechanisms for interworked messages (e.g. stop certain messages from being interworked);

• Provide the service-level interworking authorization;

• Avoid overlap with OMA;

• Provide appropriate mechanisms to apply charging principles for interworking;

• Provide requirements to support service-level interworking;

• Consider interaction with existing functionality in TS 23.040 (Technical realization of Short Message Service);

SA2 TR 23.811 concluded that the two Alternative Architectures for the service-level interworking are identical in the terminating cases and only differ in the originating case. Alternative 1 is using iFCs to route the Instant Messages to the IP-SM-GW, while Alternative 2 goes through BGCF in order to reach IP-SM-GW. TR 23.811 recommends to include Alternative 1 in SA2 TS 23.204. The architecture and flows have been added to TS 23.204 and TR 23.811 was not updated anymore.

SA2 added the service-level interworking via CR to TS 23.204.

CT3 work enhances the relevant 3GPP protocols to support the requirements in TS 23.204 including:

• Procedures to implement service level interworking between SM and IM guaranteeing that existing SMS and IM services are not impacted;

• Enhancement of the IP-SM-GW as an Application Server to support service selection, authorization and mapping between SM and IM protocols;

• Interaction between service level interworking and transport layer interworking;

CT3 new TS 29.331 contains Stage3 supporting this feature under 3GPP IMS architecture.