Ims Centralized Services concept

TR 22.892 conclusions

• TR 22.892 clause 6 identifies requirements for the 3GPP system on IMS Centralized Services (ICS), which should be used as a basis for introducing ICS requirements into Rel-8.

• ICS related requirements should be captured in a single place (a new clause in TS 22.101 is one alternative).

TR 23.892 conclusions

• ICS architecture solutions Different approaches have been identified as possible solutions to enable ICS for ICS UE. The SIP Application Server approach with I1-cs and I1-ps is recommended as the working assumption for ICS UE.

I1-cs IMS CS Control Channel implemented over the CS domain

I1-ps IMS CS Control Channel implemented over the PS domain

The remaining conclusions cover:

• Use of ICCC (IMS CS Control Channel)

• Centralization of conditional call forwarding

• ICS UE receiving home IMS services via an IMSC (ICS Enhanced MSC Server)

• Handling of multiple media for ICS

• Use of ICCC for CS terminations

• Relation between ICS and Service Continuity

• Relation between ICS and MMSC (Multimedia Session Continuity)

• T-ADS (Terminating - Access Domain Selection)

Genealogy of this spec:

this spec	descendant(s)
23.892	23.292

19.6 Study on Architecture of ims based Customized Alerting Tone (cat) uid_380078

Resources: S2

References

Document	Title/Contents
WID(s)
SP-070905	SID on the Architecture of IMS based Customized Alerting Tone
Impacted Specifications
-	-
New Dedicated Specifications/Reports
TR 23.872	Study on architecture of IP Multimedia Subsystem (IMS) based Customized Alerting Tone (CAT)

Supporting Individual Members: China Mobile, SK Telecom , Comverse, LG Electronics, Huawei.

This study is linked to Rel-7 Study on Multimedia Telephony Capabilities for IMS (MITE) UID_31082, Rel-8 Support of Customised Alerting Tone Service (CAT) UID_340029 and Rel-8 Study on Customized Alerting Tone (CAT) solution for voice and video call in CS domain (FS_CAT_VVC_CS) UID_360031.

CAT is an alerting tone customized by the called subscriber or the calling subscriber which may e.g. be a piece of recorded or composed music, greeting words, voice, advertisement or video. With CAT, the caller can experience favourable songs, multimedia clips or other customized alerting or ringing instead of traditional ones.

Following the completion of TS 22.182 (CAT requirements), standardization of one solution among various alternatives for implementing the basic functions of IMS based CAT (including voice and video call) in IMS domain.

CAT in CS domain was studied by CT4 in TR 29.882 (Customized Alerting Tones in 3GPP CS domain).

Inter-working issues were taken into consideration especially in case when a CAT user is changing domains (between IMS and CS).

This work studied architectural impacts and potential enhancements to IMS specifications to meet the TS 22.182 requirements for CAT in IMS domain, including:

• Architecture and procedures to support basic call scenarios for CAT (including both voice and video call) in IMS domain;

• Interaction with other service, e.g. IMS Multimedia Telephony Supplementary Services;

• Abnormal case handling (e.g. when CAT server fails);

• Multiple domains (including IMS and CS) roaming/interworking.

TR 23.872 Conclusion

• Both, Forking and Early-Session models need to be specified in Rel-8.

• Gateway model (RFC 3960) supports CAT provided by terminating IMS network without additional stage 2.

• CAT inter-working between CS and IMS is included in Rel-8;

• Service Notification requires no additional stage 2 specification;

• Content indirection is not to be included.