19.2 Study on Stage 2 aspects of ims Service Brokering uid_320028

Resources: S2

References

Document	Title/Contents
WID(s)
SP-060443	SID on IMS Service Brokering enhancements
Impacted Specifications
-	-
New Dedicated Specifications/Reports
TR 23.810	Study on architecture impacts of Service Brokering

Supporting Individual Members: Telcordia, Comverse, Huawei, BT, Orange, Telecom Italia, T-Mobile, GET (Groupe des Ecoles de Tel).

3GPP has adopted the approach of creating a number of IMS enablers that can be used by a number of services. The success of this approach is proven by the adoption of IMS by other standardisation bodies (e.g. TISPAN, OMA).

Various IMS specifications provide the ability to sequence invocations of IP Multimedia Applications (or their servers) providing a static sequence handing off session control to individual applications (or their servers). This IMS service control architecture was developed in Rel-5 and remained essentially unchanged since. It includes a Service Interaction Manager (SCIM) as part of the Application Server domain (see TS 23.002). Additionally, as part of Rel-7 Open Service Access (OSA) Application Programming Interface (API); Service broker Service Capability Feature (SCF) has been developed (TS 29.198-16).

3GPP and OMA have provided specifications for IMS enablers and applications.

This study looks if the current service interaction management architecture (e.g. SCIM as part of AS and Service Broker as part of OSA SCS) properly supports these enablers and applications along with other non-standard applications.

It studied if enhancement to the current service interaction management architecture are needed in order to satisfy the requirements in TS 22.228.

The study considered the concern that if services are provided by different service providers, then the solutions must be able to prevent undesirable alterations of interaction characteristics.

TR 23.810 has proposed no spin-off activity.

NOTE: UID_31088 "IMS Service Brokering enhancements" was moved back from Rel-8 to Rel-7 in order to give a home to 22228CR0036_(Rel-7)_S1-051232. Hence, Rel-7 ISB has Stage 1 only and is misaligned with Rel-7 Stages 2/3.

19.3 Study on ims utilizing multicast bearer services uid_7049

Resources: S2

References

Document	Title/Contents
WID(s)
SP-060148	SID on IMS utilizing multicast bearer services
Impacted Specifications
-	-
New Dedicated Specifications/Reports
TR 23.847	Enhancements to IMS service functionalities facilitating multicast bearer services

Supporting Individual Members: Siemens, China Mobile, Panasonic, Alcatel.

This work is linked to SA1 Rel-7 MBMS Enhancements (MBMSE) UID_31084.

During the definition of MBMS enhancement requirements in Rel-7 TS 22.228, IMS support of media delivery over multicast bearers was identified as follows:

"Multicast services allow IMS users and service providers to send multimedia to a group of IMS users simultaneously in an unidirectional way of communication. The underlying network may be able to support mechanisms that optimize the delivery of multimedia to the individual members of that group (e.g. MBMS)"

Initial understanding of architectural implications were based on regional services to grouped IMS users provided at hotspots such as a football stadium.

This work studied feasibility of using multicast bearers (e.g. MBMS) in the context of IMS-based applications. It captured the results of technical considerations and solutions into the facilitation of IMS services over multicast bearer services with a focus on the possible enhancements to IMS functionalities and relevant charging, security and service provision procedures. Considerations included:

• Signalling procedures of multicast enabled IMS services should be analyzed based on the grouped communication scenarios and possible optimizations to the delivery mechanisms should be investigated;

• Identify charging and policy control procedures according to the PCC architecture;

• Identify service provision procedures both in Network Elements and UEs;

• Investigate possible security requirements to multicast enabled IMS functionalities and bearer service entities;

• Real-time QoS requirements e.g. delay , interruption;

• UE capability requirements.

TR 23.847 conclusions

• Documented technical alternatives on the reference architecture with preferred developing principles, signalling flows, PCC impacts.

• Alternative signalling flows were documented for both IMS grouped applications, IPTV and more value-added service cases (provided examples of combined signalling flow of IMS and MBMS in the actual use cases).

• Stage 2 and modification to PCC should be created when needed.

• Concerns on security and media plane QoS were removed because of missing appropriate expertise.