Schedule: Timing Topic - Oracle · Online Mediation Controller complementary applications serve mainly as an example for how applications can be implemented to expand BRM functionality

Online Mediation Controller 2 - 1

Schedule: Timing Topic

<xx> minutes Lecture

<xx> minutes Practice

<xx> minutes Total



Terminology

AAA - Authentication Authorization Accounting

AVP - Attribute Value Pair

CCA - Credit Control Answer

CCR - Credit Control Response

DM - Degraded Mode

IN - Intelligent Network

OCF (S) - Online Charging Function (System)

OFCF (S) - Offline Charging Function (System)

WS - Web Services

SMS - Short Message Service

SCP - Service Control Point


Online Mediation Controller complementary applications serve mainly as an example for how

applications can be implemented to expand BRM functionality with services:

• Announcement Player - Plays an announcement at the beginning of a call to a calling

party.

• Home Zones – Applies rates or service access conditions based on location of

subscriber.

• Threshold Notification - A Diameter Attribute-Value Pair (AVP) threshold value triggers

Service Broker to generate an event. The event can be subscribed to by other

applications.

Portal Communication Protocol (PCP) is a native interface to BRM. ECE is accessed through

an embedded ECE client which communicates directly with the coherence cluster on which

ECE is running. Third party Online Charging Systems (OCS) are accessed through the

Diameter Ro interface.


Application facing Interworking Modules:

• IM-OCF – Interworking Module for Online Charging Function

There are two different IM-OCF’s available. One for BRM (PCP) and one for ECE.

• IM-OFCF – Interworking Module for Offline Charging Function

• IM-WS – Interworking Module for Web Services

Network facing Interworking Modules:

• R-IM-OCF – Interworking Module for Reverse Online Charging Function

• R-IM-OFCF – Interworking Module for Reverse Offline Charging Function

Network domain components:

• CTF - Charging Trigger Function

• NAS - Network Access Server

Interworking modules for accessing legacy networks through AIN, WIN, CAP and INAP can

also be used.

AIN – Advanced Intelligent Network

WIN – Wireless Intelligent Network

CAP – CAMEL Application Part

INAP – Intelligent Network Application Part

<Course name> <Lesson number> - 6


R-IM-OCF RO represented in the diagram:

• Mediates to charging network elements

• Acts as standard service IMS Online Charging Function (OCF), [3GPP TS 32.296]

• Uses Diameter Ro to connect to IMS Charging Trigger Function (CTF)

• Supports session and events charging standards, [3GPP TS 32.299]

• Provides protocol state machines and prebuilt translation of Diameter Ro to an internal

abstraction layer protocol.

IM-OCF PCP represented in the diagram:

• Mediates to BRM for online charging

• Uses BRM native interface (PCP) and translates it to an internal abstraction layer

protocol

• Supports session and events charging standards, [3GPP TS 32.299]

• Is agnostic to the network where the session is ongoing: GSM, AIN, or NGN, IMS

• Can be invoked any time in the service composition (or multiple times, when

conditions change)

The session and events charging standards according to [3GPP TS 32.299] includes:

• SCUR – Session Charging with Units Reservation

• ECUR – Event Charging with Units Reservation

• IEC – Immediate Event Charging

• Balance Enquiry

• Service Price Enquiry

• Refund

<Course name> <Lesson number> - 8

CCR - Credit Control Request

CCA - Credit Control Answer






When using RADIUS, you often see the acronym AAA, which stands for Authentication,

Authorization and Accounting.

In the diagram R-IM-OFCF uses RADIUS to connect to Network Access Server (NAS), acting

as a standard RADIUS Accounting Server as defined in RFC 2866.

IM-OFCF PCP mediates to BRM for authentication and accounting over PCP. The IM-OFCF

PCP translates between PCP and an internal abstraction layer protocol.

A RADIUS accounting flow has a variety of packets:

Accounting Start - When network access is granted to the user by the NAS, an Accounting

Start (a RADIUS Accounting Request packet containing an Acct-Status-Type attribute with the

value "start") is sent by the NAS to the RADIUS server to signal the start of the user's network

access. "Start" records typically contain the user's identification, network address, point of

attachment and a unique session identifier.

Accounting Response - Typically, the client sends Accounting-Request packets until it

receives an Accounting-Response acknowledgement, using some retry interval.

Accounting Update – Periodically, Interim Update records (a RADIUS Accounting Request

packet containing an Acct-Status-Type attribute with the value "interim-update") may be sent

by the NAS to the RADIUS server, to update it on the status of an active session. "Interim"

records typically convey the current session duration and information on current data usage.

Accounting Stop – When the user's network access is closed, the NAS issues a final

Accounting Stop record (a RADIUS Accounting Request packet containing an Acct-Status-

Type attribute with the value "stop") to the RADIUS server, providing information on the final

usage in terms of time, packets transferred, data transferred, reason for disconnect and other

information related to the user's network access.





In the diagram SSUs and deployed in the Signaling Tier to communicate between the

components of the Processing Tier and the network , clients and servers.

Signaling Server Unit (SSU)

A is a Service Broker component that enables Online Mediation Server to connect to IMS-

based signaling networks through standard software and hardware interfaces. There is a

specific SSU implementation to support connection to each network domain.

Processing Tier

Components running on processing servers are stateful. State information is maintained and

distributed across the Processing Tier. Components retrieve and store session state in an in-

memory storage. When one processing server fails, functioning processing servers continue

to retrieve and process all messages, including those stored in the in-memory state of the

failing processing server.

Orchestration Engine (OE)

The OE resides at the center of the Service Broker architecture. The OE invokes applications

in a specific order, according to conditions that determine which application to invoke and in

which order. You specify the applications that the OE invokes, the order in which the OE

invokes the applications, and the conditions that determine whether to invoke an application

or not, using an orchestration logic.

Session Abstraction Layer (SAL)

Communication between the OE and IMs is normalized, based on the SAL protocol.

In the diagram the OE communicates with IMs using the Service Broker internal SAL protocol.

IMs communicate with the network and applications by configuration of SSUs.

Supplementary Modules (SM)

SMs are optional on-board modules, each facilitating Service Broker solutions in a different

manner. The most often used SM by Online Mediation Controller is SM-PME, which is a

flexible XML-based engine that manipulates parameters in the headers and body of internal

Service Broker SAL messages.


Connection to BRM is implemented using a Connection Pool (on the client side) that connects to the BRM Connection Manager (on the server side). A connection is assigned from a pool to execute an operation. If an operation is received and no connection is available it is queued.

OCSB SSU PCP:

• Definition of multiple Connection Pools toward BRM Connection Managers

• Assignment of an OCSB alias to an BRM Connection Pool

IM-OCF PCP

• Extended IM-OCF (online charging function) that support translation of RO onto BRM PCP

IM-OFCF PCP

• IM-OFCF (offline charging function) used for Diameter Accounting support (Rf)

• Implements stateless client

• Extension that support translation of Rf onto BRM PCP

R-IMOFCF RADIUS

• Reverse Interworking Module-Offline Charging Function - Used for Diameter Accounting support (Rf)

• Implements stateless server

• Extension that supports translation of radius onto Rf



In the diagram Online Mediation Controller processes charging requests in degraded mode

using a Local OCF as a primary OCS. The Local OCF consults the Subscriber Store for

predefined set of states the user may be in to determine CDR replay.

Online Mediation Controller generates per-session CDRs. CDRs are replayed during low

activity.

Degraded Mode is available for all network charging interfaces and scenarios.

System Level Degraded Mode:

Triggered when there’s no response from OCS to heartbeat

All active sessions switch AND new sessions are processed in DM

Session Level Degraded Mode:

Triggered when OCS fails to respond during an active session

Only the affected session is processed in DM

New sessions are passed to primary OCS

Degraded Mode Activation:

• Automatic – In case of OCS outage, automatic switch to ‘degraded mode’ of operation

• Manual – Planned outage for OCS maintenance operations


Counters are reset in each Degraded Mode window:

• Degraded Mode information is fetched once in a session to check if the user is in the

same Degraded Mode window.

• If this is the first session in the Degraded Mode window counters will be reset according

to global or Subscriber Store information.

Subscriber Store information includes:

• user-ID,

• user-profile,

• service-ID,

• TOD,

• prefixes,

• network entity address

• counter information


The flow diagram illustrates a use case where a request for an increase in bandwidth quota is

negotiated between GGSN and BRM. In this example the Local OCF takes over for BRM

when Online Mediation Controller goes into Degraded Mode.


To deliver subscriber-specific services, the Online Mediation Controller maintains its own

subscriber profiles.

Subscriber profiles include:

• The service profile.

• An orchestration logic that defines how to route subscriber sessions through

applications.

• An extensible subscriber lifecycle that can define subscriber states and state transitions.

Each state implies a certain set of privileges and prohibitions. For example, you can

configure the Online Mediation Controller to charge Active subscribers, or redirect

Suspended subscribers to top up their accounts.

Degraded Mode interrogates the Subscriber Store for session level Degraded Mode.

The Threshold Notification application stores threshold rules in the Subscriber Store. The

Orchestration Engine (OE) communicates with the Subscriber Store to retrieve threshold rules

from the subscriber profile.

Service Broker includes a web services Subscriber Provisioning API that you use to manage

subscriber data in the Subscriber Store.




The Balance Manager provides a way to enable prepaid subscribers to check their account

balances and replenish ("top up") their accounts either from stored payment account

information or by redeeming a voucher.

There are three user interaction channels to top up and check balance:

• Voice call (IVR) - Top up and check balance through IVR sample applications are

provided.

• SMS – Top up and check balance through SMS is enabled through service providers

specific code.

• WS – Top up and check balance PCP operations are exposed through a SOAP

interface. The interface can be used by service provider’s self service or customer care

portal.

The Balance Manager applications perform four activities, encapsulated in the four methods

in the Balance Manager API:

• authenticate: Authenticates subscribers who want to check their balances or add funds

to their accounts using payment resources stored on BRM.

• check balance: Checks the balance in a subscriber account.

• top up: Adds funds to ("tops up") an account using the subscriber’s payment resources

stored on BRM.

• voucher top up: Adds funds to an account by redeeming a voucher.

In the sample flow a Media Resource Function (MRF) and Application Server (AS) interact to

manage an IVR request for TopUp:

• HTTP_Get: MRF asking for IVR logic.

• HTTP_Ok VXML: xml file containing IVR interaction for recharge of balance.

• HTTP_Get: AS receives instruction to increase balance and sends message toward

Online Mediation Controller to do TopUp.


The diagram illustrates:

• The firing application specific events over WS interface

• Events being processed by:

- Online Mediation Controller’s Event Processor

- External processor (e.g. SOA BUS)

- Interworking Module-Application Server Function for SAL (IM-ASF-SAL) connects Service Broker with SAL applications, that is either out-of-the-box Service Broker applications, or applications that you implement using the SAL API.

Types of applications that may make use of the Event Notification Framework include:

• Advice of Charge (AoC) Application – fires events that are used to trigger user notification on service costs

• Bill Shock application – fires events that are used to trigger user notification on consumption thresholds

• Credit card recharge – fires events that are used to trigger automatic recharge from user’s credit account to prepaid account

• Parental control applications – to send reports to parents on consumption and which services accessed



IM-WS is a network-facing module that enables Online Mediation Controller to receive

messages from, and send messages to, web services using Simple Object Access Protocol

(SOAP) or Representative State Transfer (REST) protocol.

IM-WS sends message to a web service by sending an event notification submitted by an

application in the SAL Format. It translates this message into a SOAP or REST message and

sends it to a web service through the Web Services SSU.

WS integration examples:

• Diameter API may not be supported by a SMSC network device. In this case WS

SOAP API can be used between the SMSC and Online Mediation Controller instead of

Diameter Ro.

• A legacy SCP network element may do rating, not charging. WS SOAP API may then be

used toward IM-WS to get a balance. IM-WS Network and application facing module

provides Out-Of-The-Box support for WS APIs:

• Top-up and Balance enquiry WS APIs - Interface for service providers portal

• User data provisioning


Supplementary Module-Parameter Mapping Engine (SM-PME) is a flexible XML-based

engine that manipulates parameters in the headers and body of internal Service Broker SAL

messages. SM-PME complements generic solutions with specific requirements and allows

fine tuning of parameter mediation for standard and non-standard protocol parameters. OE

can chain SM-PME at any point of the service orchestration in the same way that it chains

Interworking Modules.



In the diagram an application invokes Online Mediation Controller interfaces that interact with:

• Voice media resources like a MRF on an IMS network

• SMSCs sending and receiving short messages over SMPP

Roaming conditions - Entering and leaving home and visited networks.

R-IM-ASF – Reverse - Interworking Module - Application Server Function


Voice user interaction:

The interface is network agnostic and supports user interaction through IMS – using MRF

through Media Server Control Markup Language (MSCML). MSCML is a separate license.

SMS user interaction:

Short Message Peer-to-Peer (SMPP) is used by clients to connected to a SMSC (Short

Message Service Center). In SMPP terms, the client is called an Extended Short Message

Entity (ESME). Online Mediation Controller interfaces:

• Act as an ESME for two way messaging over SMPP v3.4

- Receive Short message from a user (e.g. for top up through SMS)

- Send SMS to user (e.g. To notify user on certain event)

• Support these SMPP messages:

- Submit_sm – send message towards SMSC

- Deliver_sm – receive message from SMSC and receive delivery receipts/ACKs



Mediation Controller provides functions enriching OCS/BRM features beyond pure rating and balance

management:

• Degraded Mode

- Charging/service continuity when OCS becomes unavailable

- Available for all network charging interfaces and scenarios

- Makes use of a locally stored OCF and Subscriber Store to manage degraded requests.

• Events Notification

- Expose charging applications events towards external systems for advanced business

logic execution

• Web Service Integration

- To enable integration with any WS supported system for charging, events exposure,

queries and other purposes.

• Parameter Manipulation Engine

- XML based configuration of parameter manipulation and transformation

• Top-Up and Balance Enquiry

The diagram illustrates how these features are part of the Online Mediation Controller product.




BRM – Oracle Communications Billing & Revenue Management


SCP - Service Control Point



DCCA - Diameter Credit-Control Application


PCEF – Policy and Charging Enforcement Function is part of a 3G/4G network. The PCEF

detects an event which triggers notification to the PCRF to download policy rules

PCRF - Policy and Charging Rules Function is the node designated in real-time to determine

policy rules in a multimedia network:

• Provides the PCEF with Policy Rules:

- Network flow detection information

- QOS, Gating, Charging information

- Binding of AF sessions

AF - Application Function. Applications that require control or influence over:

- Policies

- Qos

Rx – Diameter interface is used to communicate between the AF and PCRF

Gx – Diameter interface is used to communicate between the PCEF and PCRF



Answer: c


Answer: b


Answer: a



Documents

Schedule: Timing Topic - Oracle · Online Mediation Controller complementary applications serve mainly as an example for how applications can be implemented to expand BRM functionality