IMS Centralized Services (ICS) provides communication services such that all services, and service control, are only based on IMS mechanisms and enablers. It enables IMS services when using CS access (e.g. TS 24.008, 3GPP2 C.S0001-D ) for the media bearer.
With ICS, the user services are provided by IMS only. User sessions are controlled in IMS via PS or CS access and can be any of those defined in clause 22.4 of TS 22.101.
When using a CS access network, or when using a PS access network that does not support the full duplex speech/video component of an IMS-based service, the CS core network is utilized to establish a circuit bearer for use as media for IMS sessions. The transmission of both bidirectional and unidirectional real-time video media flows shall be supported.
If the PS access network does support the full duplex speech component of an IMS service then existing IMS session procedures are used as specified in TS 23.228.
ICS provides mechanisms to support the use of CS media bearer for IMS sessions. With ICS, IMS sessions using CS media are treated as standard IMS sessions for the purpose of service control and service continuity.
ICS defines signalling mechanisms between the UE and IMS for transport of information required for service continuity when using CS access for media transport.
IMS services as defined in clause 22.4 of TS 22.101 shall be consistently provided when using a CS or a PS access network for the media of the IMS service subject to the capability of the UE and the access network.
Service continuity shall be provided when underlying mobility results in a change of access network capabilities, e.g. support of Gm reference point in conjunction with CS bearer may not be possible after handover from UTRAN to GERAN.
When a user accesses IMS services over a CS network, or a PS network which does not support the full duplex speech or video media flow component of an IMS service, the following IMS session scenarios shall be supported according to the procedures specified in TS 23.228, along with the solution specified in this document.
Basic voice or voice and video service origination and terminating sessions.
Voice or voice and video origination and termination service sessions with Line ID services (e.g. OIP, OIR, TIP, TIR) controlled in IMS.
Voice or voice and video origination and termination service sessions with Communication Barring services controlled in IMS.
Voice or voice and video termination service sessions with Communication Diversion services controlled in IMS.
Voice or voice and video origination and termination service sessions with mid-call services (e.g. Hold/Resume, Conferencing, CW, ECT) controlled in IMS.
Communication services setting modifications (e.g., changing forwarding info or activating barring services, etc).
The solution shall provide for an ICS UE, generic capabilities to enable introduction of new IMS services utilizing CS bearers without further standardisation.
Adding/removing real time video media flow over CS access to/from an IMS session (see TS 22.173).
An ICS UE supporting multimedia telephony shall manage the IMS multimedia telephony communication service settings data as specified in TS 24.173.
For a UE not supporting multimedia telephony, the MSC Server enhanced for ICS may implement a communication service setting conversion function between CS signalling (e.g., as described in TS 24.010) and communication service setting procedures (e.g. as defined in TS 24.173); see also clause 22.214.171.124.
For a UE not supporting multimedia telephony, if the MSC Server enhanced for ICS does not implement a communication service setting conversion function or if the UE is connected to an MSC server not enhanced for ICS, refer to clause 126.96.36.199.1.
Mechanisms that allow data to be synchronized between the HSS and the TAS when legacy CS signalling is used towards the HSS for service settings data management are not specified.
For registration to IMS, the MSC Server enhanced for ICS shall use only a Private User Identity and Public User Identity specifically reserved for IMS registrations from an MSC Server. For systems with a CS domain access based on TS 24.008, the subscriber identity used shall be as defined in clause 20.3 of TS 23.003.
Similar to the temporary Public User Identity (see clause 13.4 of TS 23.003), the ICS specific Public User Identity shall be prohibited from being used to originate sessions and shall be prohibited from being used to identify a terminating subscriber for incoming sessions.
An MSC Server shall use only those Public User Identities representing E.164 numbers from the subscriber's IMS profile to originate and terminate calls.
It shall be possible to provide ICS for an ICS UE and a non ICS UE in home and in visited networks.
Home and visited networks with an MSC Server enhanced for ICS shall support call originations and terminations for ICS UEs and non ICS UEs.
The MSC Server enhanced for ICS avoids conflicts with other IMS registrations (which includes that used by an ICS UE) by using a Private User Identity and Public User Identity specifically reserved for use by MSC Server registrations. See clause 4.6.2 for more information. An IMS operator who provides services for its subscribers, using both ICS UE's and MSC Servers enhanced for ICS needs to make the following provisions in order to avoid registration conflicts:
Configure the ICS specific Private User Identity, as defined in clause 4.6.2 to point to the subscriber's implicit registration set; and
Add the ICS specific Public User Identity, as defined in clause 4.6.2 to the subscriber's implicit registration set.
When the ICS UE establishes the Service Control Signalling Path over I1 or Gm prior to the establishment of the CS Bearer Control Signalling Path, the ICS UE shall use the routing number provided by the network in response to service control signalling as the B-Party number for establishing the CS Bearer Control Signalling Path.