3 Invoking Applications Based on the Previous Session Route

This chapter describes how to set up an application to run based on the previous route of the session in Oracle Communications Service Controller.

About Invoking Applications Based on the Previous Session Route

You can set up an application to run based on the previous route of the session. For example, you can set up a pre-paid application to run only if the session contains tags indicating that a home zone application precedes the pre-paid application in the orchestration chain.

To enable applications in the orchestration chain to get the information about applications through which the session is routed, you need to tag the session when it passes through an application. For example, if the OE routes the session to a home zone application, you can tag the session with the tag HomeZoneAppInvoked. This allows next applications in the orchestration chain to be aware of the hoe zone application was triggered.

Then you can set up one of the next applications in the chain (such as a bill shock prevention application) to run only if the session contains the HomeZoneAppInvoked tag.

As the session passes through applications in the orchestration chain, all tags are accumulated. Therefore, any subsequent application in the orchestration chain can be aware of those tagged applications which were previously triggered.

The OE adds tags to the session when routing it to the IM defined in the orchestration logic. You define a tag to be added as a part of the configuration of the appropriate IM.

Note:

Service Controller does not support tags when the Diameter-based orchestration mode is enabled. For more information on the Diameter-based orchestration mode, see the discussion on improving performance in Diameter-only environments in Service Broker Online Mediation Controller Implementation Guide Release 6.1.

Tagging a Session

To tag a session, edit the session XML source code. Add tags to the application header fields.

Checking Tags in a Session

You can set up an application to run depending on the application through which the session has already passed. For example, you can set up a condition that invokes the following applications in the chain:

  • Home zone

  • Online charging

If, for example, the session does not contain a tag specifying it should access the VPN application, it skips the VPN application and continues to the pre-paid application.

You can use regular expressions. For example, if your tag is .*1234.* the message is routed to all numbers that contain 1234, regardless of the numbers that precede or succeed it.