Skip Headers
Oracle® Communications Service Broker Concepts Guide
Release 5.0

Part Number E15180-01
Go to Documentation Home
Go to Book List
Book List
Go to Table of Contents
Go to Feedback page
Contact Us

Go to previous page
Go to next page
View PDF

3 Service Broker Service Orchestration

The following sections describe the components and the mechanics of the Oracle Communications Service Broker Orchestration:

About Orchestration Engine

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:

Figure 3-1 shows how OPRs and OLPs are used by the OE to select and download orchestration logic.

Figure 3-1 Orchestration Engine Components (Core Engine: OLRs and OLPs)

Orchestration Engine Components

When triggered by the session control layer, the OE performs the following procedure for each call or session:

  1. 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.

  2. 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.

  3. 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.

About Orchestration Profile Receivers (OPRs)

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:

  1. 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).

  2. Selecting an orchestration profile:

    OPR uses session information (for example, session origination, session destination and IN Service Key) to select an orchestration profile.

  3. 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:

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.

About Orchestration Logic Processors (OLPs)

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.

Supported SAL Requests

The Orchestration Engine supports the following SAL requests: