For the last 15-20 years, intelligence within the telecommunications network has been provided by Intelligent Network Service Control Points (IN SCPs). The main services provided by these IN platforms are number translation services, virtual-private networks and crucially for mobile telephony, pre-paid capabilities. Beyond the “big three” services, IN platforms today implement a wide range of useful network services that we use every day – such as short-code dialling, multiple call leg handling, call screening, caller ID etc.

But SCPs were not originally designed:

• For a multi-service, multi-network telecoms world, or
• To facilitate open development, or
• To provide a platform for service innovation.

Development of IN services for these platforms remains with the Network Equipment Providers (NEP). Whilst telecoms Operators may conceive new services, they have to commission it from their NEP and take their place in the service development schedules.

Rhino Application Server is the ideal core technology for implementing a Next Generation Intelligent Network (NG-IN) platform that complements rather than replaces the existing IN SCP. The IMS blue-print identifies the need for a flexible Service Delivery Platform (SDP) to enable service innovation within the telecoms network. As Rhino is multi-network and multi-protocol, it allows services to be implemented on today’s TDM networks and accessed by the vast majority of today’s subscribers as well as on nascent mobile IP-based networks:

• Rhino can be used alongside the existing IN assets to augment the IN service portfolio. New IN services can be introduced alongside those hosted by the IN SCP. This allows targeted variants of services to be trialled, refined and rolled-out.
• Rhino can be used to add value to the services that are hosted on the IN SCP and create variants of the standard service offerings. Subsets of the network signalling can be directed to the Rhino Application Server before and/or after the IN SCP, allowing additional control of calls, messaging and sessions through the call/ message/ session life-cycle.
• Rhino Service Interaction SLEE (Rhino SIS) can be used to build new and variant services from existing IN services. Existing IN services are used as “service building blocks” that can be plugged together with additional logic to produce new services. The existing IN services can be Rhino-hosted, IN SCP-hosted or hosted on third-party Application Servers.

Mobile Network Operators are using Rhino to implement NG-IN services such as:

• Fixed-mobile substitution offers such as location-based charging
• Charging information services
• Multi-media interaction
• Multi-number services
• Multi-SIM services
• Call group services (such as family calling circles etc)
• Call Personalisation (call groups, location and time-of-day call control)

Back to top ^

Terms of use Privacy Statement Site by Pepsmedia