The IMS architectural blue-print identifies the concept of a Service Capability Interaction Manager (SCIM) within the "SIP Application Server" domain of the IMS architecture. The definition of the role of SCIM is rather loose in the 3GPP Release 6 specification. It signposts the need for capabilities to address a common problem: the orchestration of the interaction between "capabilities" in the IMS network. In fact, there is no reason to restrict this ability to IMS services; traditional TDM IN equipment performs this task and the deployment of multiple network technologies and Network Elements provides many opportunities for cross-technology service interaction.

OpenCloud have adopted the generic term Service Interaction SLEE (SIS) to denote the wider application of the IMS SCIM concept to include “IN” circuit-switched network technologies (also sometimes referred to as IN Service Broking). OpenCloud Rhino SIS solutions provide IN SIS and SIP SIS capabilities. Service composition and interaction enables core network service chaining by providing multi-service triggering in the service layer, regardless of the networking protocols that are used.

Person-to-person telecommunications services may be composed from existing services, taking the existing service capabilities and re-using them as building blocks to construct new, variant services. Additional call/ session/ messaging logic can be inserted to provide more customised, personalised control of the services. This approach provides:

• The means to realise new service variations quickly and cost-effectively to meet the specific needs of segments of the subscriber base. Service variations can be trialled, refined, enhanced and withdrawn quickly and cost-effectively. Service variants have premium value to subscribers and are proven to reduce subscriber churn;
• Efficient re-use of proven service components – fewer service errors, less testing and quicker to market;
• Lower costs reduce barriers to trialling and adoption of innovative services with as-yet unproven business case;
• Operator control of the on & off-line charging characteristics of such variant services;
• Pre-paid enablement of popular IMS/ SIP product packages that often have fixed capabilities and have not been designed with prepaid cellular capabilities;
• Continued and extended use of existing network assets to deliver revenue earning services;

The service composition and interaction capabilities of Rhino-based solutions can also be used to extend the life and capacity of existing IN platforms by off-loading certain classes of call control from the IN to a IN front-end system. For example, certain classes of on-network and “freephone” calls can be authorised without involving the IN SCP.

Back to top ^

Terms of use Privacy Statement Site by Pepsmedia