| Oracle® Communications Service Broker Concepts Guide Release 5.0 Part Number E15180-01 |
|
|
View PDF |
| Oracle® Communications Service Broker Concepts Guide Release 5.0 Part Number E15180-01 |
|
|
View PDF |
This following sections describes typical use cases for implementing solutions based on Service Broker:
Service Broker's interworking modules can mediate between the SCPs and SSPs or MSCs that use different protocols or different flavors of the same protocol.
A combined CDMA/GSM network can be migrated to GSM, enabling operators to deliver CAP-based, Prepaid SCP services to CDMA subscribers and consolidate the service layers of both networks.
Service Broker interacts with the SCP and the MSC, using the following IMs:
CAP IM-SSF to communicate with the GSM SCP through the CAP protocol.
WIN IM-SCF to communicate with the WIN-based MSC.
Figure 5-1 illustrates this example of Service Broker's IM mediation between different protocols.
Operators can add equipment produced by different vendors to their existing, single-vendor environment and mediate between different flavors of the same protocols.
Service Broker can act as a mediator between, for example, an SCP, which uses CAP Phase 4, and an MSC, which uses CAP Phase 1.
Figure 5-2 illustrates this example of Service Broker's capability to support different flavors of CAP to communicate with the MSC and SCP.
Service Broker's service orchestration capabilities enable the delivery of combined services that run in different networks.
Operators can deliver combined services running on different SCPs in a single session in IN and IMS networks.
Service Broker communicates with each of the SCPs to orchestrate a number of services running in different networks, using IM-SSFs that support different protocols.
Figure 5-3 shows an example deployment in which Service Broker first forwards a session to the Prepaid SCP to perform online charging operations and then to the VPN SCP.
Operators can implement ISC, Cx/Sh, Ro/Rf protocols in an IMS network, based on filter criteria stored in the HSS.
Service Broker interacts among various application servers in order to deliver services. Integrating with SOA Service Framework and Enterprise Services bus enables Service Broker to interact with Web Services and an external SOA Service bus.
Figure 5-4 shows an example of a deployment in which Service Broker—integrated with Web Services—communicates with the IMS network and provides service interaction based on the logic retrieved from the HSS.
Operators can implement a Diameter-based online charging request from multiple sources, including different variants of Ro/Diameter and legacy voice calls, using different IN protocols in the IN domain?
Service Broker processes charging requests for normalization and adaptation before sending these requests to an online charging server that analyzes and complies with each request.
For example, a combined UMTS/IMS operator can use Service Broker to unify charging across different services and network elements that originate from different vendors using different variants of the Diameter or Radius protocols, into a common online charging server.
Figure 5-5 shows an example of a deployment in which Service Broker processes charging requests from a legacy MSC, GGSN and CSCF using SM-PME and then forwards the requests to the online charging server.
Service Broker's service delivery capabilities enable the delivery of:
Legacy services to SIP networks
SIP services to legacy networks
Operators can deliver existing IN-based, prepaid services to SIP-based subscribers.
Service Broker mediation enables the delivery of legacy services running on IN SCP platforms to SIP Softswitches and CSCFs. This capability can also be implemented to enable wireline carriers to deliver their existing legacy service platforms, such as Number Portability or Toll-Free, to SIP-based subscribers.
Figure 5-6 shows an example of a deployment in which Service Broker delivers legacy prepaid and VPN services to the Softswitch or CSCF.
Operators can deliver SIP/IMS-based services to a legacy domain, including 2G/2.5G/3G phones and to fixed POTS subscribers.
Service Broker mediation enables the deployment of SIP/IMS platforms that deliver services to mobile subscribers in legacy domains. Using this solution, mobile GSM operators can deploy a SIP implementation of the Voice VPN service over CAP to GSM mobiles as an alternative to their Voice VPN service platform.
Figure 5-7 shows an example of a deployment in which Service Broker delivers SIP services to legacy networks.
Service Broker enables service interaction between SIP/legacy domains and dual-mode handsets that support Voice Call Continuity (VCC).
Operators can provide VCC services between WiFi and the 2G/3G mobile domains.
The VCC capability can be combined with any other SIP-based or IN-based service platform to create a dual-mode handset service combination.
Figure 5-8 shows an example of a deployment in which Service Broker delivers services to both legacy and SIP-based networks.
Service Broker enables migration of Prepaid SCP solutions to an online, unified charging service.
Operators can regain their investment in a legacy Prepaid SCP and continue to provide a wide range of flexible prepaid services, combining call control and online charging capabilities.
Service Broker can act as an SCP frontend to the network to provide the entire prepaid family of services, including prepaid, credit control, spending limit, and roaming control, to an online unified charging service.
Figure 5-9 shows an example of a deployment in which Service Broker delivers online charging services.
Service Broker enables existing, deployed, IN-based services to function within an IMS network.
Operators can deliver existing, IN-based prepaid services to new IMS subscribers.
Service Broker's IM-SSF enables IMS CSCFs to interact with legacy services running on existing SCP IN platforms.
Alternatively, Service Broker interacts with the CSCF through ISC to implement legacy service platforms, such as Number Portability and Toll-Free, to new TISPAN/IMS subscribers in a TISPAN core network.
Figure 5-10 shows an example of a deployment in which Service Broker delivers prepaid services.
|
 Copyright © 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
