| 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 |
The following sections describe the components and the mechanics of the Oracle Communications Service Broker Orchestration:
The Orchestration Engine (OE) is core to Service Broker functionality) and is responsible for the delivery of multiple services per session (see "Orchestration Engine").
To perform service orchestration, the OE requires an orchestration logic. An orchestration logic defines applications through which the OE should pass a session and the order in which these applications must be invoked.
Service orchestration is performed using the following components:
Orchestration Profile Receivers (OPRs)
Orchestration Logic Processors (OLPs)
Figure 3-1 shows how OPRs and OLPs are used by the OE to select and download orchestration logic.
When triggered by the session control layer, the OE performs the following procedure for each call or session:
Orchestration profile selection: The OE uses an OPR to select and retrieve an orchestration profile. The orchestration profile includes information on the type of OLP to use next, and the specific parameters that type of OLP requires.
The OE uses either HSS OPR, LSS OPR, or any other installed OPR as defined in the OE configuration settings.
Application triggering: The OE interacts with an OLP component. The type of the OLP is specified by the OPR that was used in the previous step. Using the information included in the profile, the OLP obtains orchestration logic, processes the orchestration logic and determines which application to trigger next. Once an application is selected by the OLP, the OE routes the session towards that application and waits for the application to return.
When the session returns, the OE continues processing the orchestration logic, looking for the next application to trigger. This process repeats until orchestration is completed. At this stage the OE routes the session back to the session control entity.
When OE triggers an OPR, the OPR responds with an orchestration profile. The OPR performs the following steps in order to obtain an orchestration profile:
Connecting to a profile server that holds subscriber data and orchestration profiles:
OPR connects to a Home Subscriber Server (HSS) or to an on-board profile server (called Local Subscriber Server).
Selecting an orchestration profile:
OPR uses session information (for example, session origination, session destination and IN Service Key) to select an orchestration profile.
Obtaining the orchestration profile:
OPR obtains the selected orchestration profile and forwards it to the OE.
Different OPRs connect different sources of subscriber data and orchestration profiles. Service Broker installation includes the following OPRs:
HSS Orchestration Profile Receiver
The Home Subscriber Server (HSS) is the primary user database in the IMS domain. It contains subscription-related information including subscriber applications and orchestration profiles. The HSS OPR uses the Diameter protocol over the standard Sh interface to connect the HSS and select orchestration profile.
LSS Orchestration Profile Receiver
Service Broker offers an on-board implementation of a profile server, called Local Subscriber Server (LSS). The LSS is capable of storing subscriber profiles, including orchestration logic given in the Initial Filter Criteria (iFC) format. The LSS OPR connects the LSS to look up subscriber profiles with orchestration logic.
Default Orchestration Profile Receiver
When this OPR is used, the OE does not retrieve an orchestration profile from an external server. Instead, the OE triggers the Static Route OLP with its pre-configured orchestration logic.
It is possible to add new OPRs to Service Broker, to connect to other profile sources that exist in the operator's network. Service Broker can apply orchestration logic defined in HSS or any other profile source to the legacy domain.
Orchestration Logic Processors (OLPs) obtain orchestration logic and process it in order to determine which applications to invoke and in which order. The OLP is triggered by the OE. It requires profile data and provides the address of the application that needs to be invoked in return. When the application finishes its processing and returns to the OE, the OE triggers the OLP again to receive the address of the next application to invoke.
Different OLPs are used to process different formats of profiles and orchestration logic rules. Service Broker installation includes the following OLPs listed. By default, the OE is installed with an OLP that executes initial Filter Criteria (iFC). It is possible to add new OLPs to Service Broker to support additional formats of orchestration logics.
Initial Filter Criteria (iFC) OLP
Initial Filter Criteria (iFC) is a standard format for specifying orchestration logic, specified in ETSI TS 129 228 V7.11.0, IP Multimedia (IM) Subsystem Cx and Dx Interfaces. iFC is a set of rules in XML format, composed of conditions (Trigger Points) and application servers that will be invoked if a condition is met. The conditions are given in logic expressions and can be applied on the content fields within the session.
Static Route OLP
The Static Route OLP uses a preconfigured list of applications to determine which applications to invoke and in which order.
|
 Copyright © 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
