Amdocs Convergent Charging and Billing Introduction_04_MEC and RLC Overview –

Part 1
Menu
Name of segment in menu Name of Sub-segment in Starts at Slide number in SB
menu
Overview Structure overview 5

MEC RLC Integration Overview 8

MEC definition 11

MEC users 15

Security concepts 17

RLC definition 19

Check yourself 23

Review 26
Glossary
Design requirements
The chart in screen 8 has to be redesigned: >>>>>>>>>>>>>>>
• Figures must be replaced with various figures from the
repository.
• The different applications must include relevant icons from
the repository, in addition to their name. Flow direction
must be maintained.

• Photos in screen 17 need to be replaced

with relevant photos from the repository; other than that the
chart should remain the same. >>>>>>>>>>>
 MEC and MEC
Overview – Part 1
Amdocs Convergent
Charging and Billing
Introduction
10
Let’s Begin!
Amdocs Convergent Charging | High-Level Data Flow
As seen in the previous unit, Amdocs Convergent Charging includes the following components.

This unit will focus on Invoicing.

Master Billing
Rating Logic
Enterprise Customer
Configurator
Catalog Management
(RLC)
(MEC) (BCM)
Messages Files

*Optional:
Mediation Turbo
Invoicing
And/or OCA Charging (TC)
And/or OFCA
Recap
This is the first of this two-part unit.

In previous units you have learned about:

● The purpose and functionality of Amdocs Customer Management (CM)

● The positioning of Customer Management within ABP

● The Amdocs Billing Customer Model

Objectives
By the end of this unit you will be able to:

Explain the functionality of Master Enterprise Catalog (MEC)

Explain the functionality of Rating Logic Configurator (RLC)

Explain MEC and RLC interfaces

Unit Content
In this unit you will learn about:
● MEC-RLC Introduction

● MEC Role Overview and Definition

● MEC User Types and Security Concepts

● RLC Role Overview and Definition

The Full Picture
Amdocs Billing Product (ABP) comprises various Billing value-added components.

At the core of ABP lies Amdocs Convergent Charging, which is reviewed in this course.

Amdocs
Amdocs Amdocs
Subscriber
Document Voucher
Resource
Designer Manager
Manager

Amdocs Service
Amdocs Amdocs
Control
Replenishment Convergent
Platform
Manager Charging
Manager

Amdocs
Amdocs Amdocs
Accounts
Error Manager Collections
Receivable
The Full Picture
Amdocs Billing Product (ABP) comprises various Billing value-added components.

At the core of ABP lies Amdocs Convergent Charging, which is reviewed in this course.

Please click the Amdocs Convergent Charging box.

Amdocs
Amdocs Amdocs
Subscriber
Document Voucher
Resource
Designer Manager
Manager

Amdocs Service
Amdocs Amdocs
Control
Replenishment Convergent
Platform
Manager Charging
Manager

Amdocs
Amdocs Amdocs
Accounts
Error Manager Collections
Receivable
Amdocs Convergent Charging Modules
As seen in previous unit, Amdocs Convergent Charging includes the following components.

This unit will focus on two components:

Master Enterprise Catalog (MEC) and Rating Logic Configurator (RLC).

Master Billing
Rating Logic
Enterprise Customer
Configurator
Catalog Management
(RLC)
(MEC) (BCM)
Messages Files

*Optional:
Mediation Turbo
Invoicing
And/or OCA Charging (TC)
And/or OFCA
Learning Review
The input for MEC is rating logic from RLC, and the output is service, pricing, provisioning
and policy control information.

Please choose the correct answer.

True

False
RLC and MEC Distribution Diagram
The OSS, Billing and Ordering product information is managed in a single interface on a
consolidated data model called Amdocs Shared Product Information Model (ASPIM ).

Amdocs Application

OSS

Billing
MEC

Ordering
Rating Logic
Configurator
(RLC)

Self Service
RLC and MEC Distribution Diagram
During this course, the focus will be on the Billing entities, which are
part of the ASPIM, and which are related to the Billing application.

In this context, RLC and MEC portfolios (Billing flavor) are used to
Amdocs Application
define Billing Offers (BOs).

OSS

Billing
MEC

Ordering
Rating Logic
Configurator
(RLC)

Self Service
RLC and MEC Distribution Diagram
X
During this course, the focus will be on the billing entities, which are
Billing Offer
part of the ASPIM, and which are related to the Billing application.
The main entity of the model for Billing and Charging applications.
In this context, RLC and MEC portfolios (Billing flavor) are used to
It Offers
usually includes: Amdocs Application
define Billing (BOs).

• Pricing definitions: UC, RC and OC rating OSS

• End of Cycle (EOC) Discounts and Penalties

Billing
• Service definitions: activation,
MEC barring…

• Charge and/or Event Distribution Configuration

Ordering
Rating Logic
Configurator
(RLC)

Self Service
RLC and MEC Distribution Diagram
RLC and MEC are tightly related, since RLC elements are the
building blocks required to create billing business elements in MEC.

Amdocs Application

OSS

Billing
MEC

Ordering
Rating Logic
Configurator
(RLC)

Self Service
RLC and MEC Distribution Diagram
Billing product data can be RLC
divided into two
X
RLC and MEC are tightly related, since elements arecategories:
the building blocks required to
create billing business elements
• Billing in MEC.
Technical information
• Defined in RLC by technical implementers

• Billing Business information Amdocs Application

• Defined in MEC by business (Billing) implementers
• Based on technical elements imported from RLCOSS

Billing
MEC
MEC
Business
elements
Ordering
Rating Logic RLC
Configurator Basic technical elements
(RLC)

Self Service
RLC and MEC Distribution Diagram
Most of the technical data, such as the elements in the Implementation repository, is
handled in the Rating Logic Configurator (RLC), which will now be the center of focus.

Amdocs Application

OSS

Billing
MEC

Ordering
Rating Logic
Configurator
(RLC)

Self Service
RLC and MEC Distribution Diagram
We will start by discussing the billing data that is maintained in MEC.

Amdocs Application

OSS

Billing
MEC

Ordering
Rating Logic
Configurator
(RLC)

Self Service
What Have We Discussed So Far?

Unit content:
● MEC-RLC Introduction

● MEC Role Overview and Definition

● MEC User Types and Security Concepts

● RLC Role Overview and Definition

Amdocs Convergent Charging Modules
As we mentioned, this unit will focus on two components.

The first is Master Enterprise Catalog (MEC).

Master Billing
Rating Logic
Enterprise Customer
Configurator
Catalog Management
(RLC)
(MEC) (BCM)
Messages Files

*Optional:
Mediation Turbo
Invoicing
And/or OCA Charging (TC)
And/or OFCA
MEC in Amdocs CES
MEC is a foundation product, available in in two forms:

• As a standalone product that can be provided with no other

accompanying product.

• As a platform for designing product catalogs, for integration

with both Amdocs and non-Amdocs applications

Simplify experience
CES suite
Harness data
Stay ahead
Revenue Management;
Be efficient Customer Management; OSS

Cross-suite tools
This chart shows MEC positioning Master Enterprise Cross Portfolio Smart Client
Catalog (MEC) Installer (XPI) Framework (ASCF)

within the Amdocs catalog: Security

Manager (ASM)
Monitoring
Framework (AMF)
Process Manager (APM)

Integration
Integration Framework (AIF) Web Services Factory (WSF)

Performance and scalability

Platforms Virtualization
MEC Highlights
MEC is a single centralized master repository for all product and service information.
This is where operators define, blend, bundle, and price their entire service offerings.

Its main benefits:

• Being a single point of entry for all product catalogs of
the organization.
• Enabling flexible definition of the catalog entities, and
enterprise-wide catalog management.
• Includes role-based, data-driven security, with
extended user authorization capabilities
MEC UI | Example
How does it actually look like?

• The MEC Client is has a user-friendly, highly-flexible GUI.

• Users can open, close or change the size and location of the various views,
according to their needs and preferences.

• MEC users can also set their preferences that determine the default behavior and
display of the various views.
What Have We Discussed So Far?

Unit content:
● MEC-RLC Introduction

● MEC Role Overview and Definition

● MEC User Types and Security Concepts

● RLC Role Overview and Definition

MEC User Types
There are three main groups of MEC users:

Please click each box to learn more.

Technical users

Business users

Administration users
MEC User Types
There are three main groups of MEC users:

Please click each box to learn more.

Technical users • Work mainly with the Designer perspective. However, they use
the Catalog perspective extensively for testing purposes.

• For defining the templates on which future catalog elements are

based they use basic building blocks, referred to in MEC as
Business users elementary types.

• Although the application provides a set of built-in elementary

types, technical users can create additional elementary types
that meet specific requirements.
Administration users
1 2
MEC User Types
There are three main groups of MEC users:

Please click each box to learn more.

Technical users • Require a thorough understanding of the business logic that

underlies the structure of the product catalog that they are
creating.

• Knowledge in Java programming is needed in order to use the

Business users MEC open user interface feature, and in Groovy, to be able to
create custom validations.

Administration users
1 2
MEC User Types
There are three main groups of MEC users:

Please click each box to learn more.

Technical users • Work with the Catalog perspective. Their main task is to create
and update the elements created based on the templates
defined previously by the technical users. In most cases, the
creation of elements involves providing values for the fields of
the underlying template.
Business users
• Create and execute queries and business rules.

• Need to understand the business logic on which the catalog

structure is based, as well as know the requirements for
managing catalog elements.
Administration users
MEC User Types
There are three main groups of MEC users:

Please click each box to learn more.

Technical users • Work with the Administration perspective.

• Their main task is to configure MEC and manage the activities

that require interfacing with external applications, such as
creating a list of external clients for distributing and releasing
Business users projects.

Administration users
Challenge Yourself
MEC supports role-based, data-driven user access management.

What do you think is the purpose of user access management?

Please choose the correct answer.

To restrict users from accessing and viewing items or

performing activities, based on Security and Proficiency.

To make sure all users have full access to the data, with no
restriction that might be automatically caused by their role.
MEC Security Concepts
Within MEC, the Amdocs Security Manager (ASM) is responsible
for Authentication i and Authorization i .

Elementary
Resources Elements Queries Templates Types

Policy

Roles Client App. Manager Business Imp. Technical Imp.

Users

User Properties:
Business Entity: ROW
Department: Marketing Self
Billing Ann Dan Yan Kan Chan Ran
Seniority: Expert Service
MEC Security Concepts
The chart below demonstrates MEC Security Concepts

At the bottom of this chart, you can see users assigned to roles. It isElementary
Elements Queries Templates defined
Resources Types
within ASM, Amdocs Security Manager. ASM also defines user properties for each
user, such as user seniority, and the business entity to which the user belongs.

Policy

Roles Client App. Manager Business Imp. Technical Imp.

Users

User Properties:
Business Entity: ROW
Department: Marketing Self
Billing Ann Dan Yan Kan Chan Ran
Seniority: Expert Service
MEC Security Concepts
The chart below demonstrates MEC Security Concepts

Elementary
Resources Elements Queries Templates Types

Policy

Roles Client App. Manager Business Imp. Technical Imp.

At the top of the chart, you can see the resources defined
Users in MEC, such as elements, queries, and templates.

User Properties:
Business Entity: ROW
Department: Marketing Self
Billing Ann Dan Yan Kan Chan Ran
Seniority: Expert Service
MEC Security Concepts
The chart below demonstrates MEC Security Concepts

Elementary
Resources Elements Queries Templates Types

Policy

Roles Client App. Manager Business Imp. Technical Imp.

Users

User Properties:
User Access Management is set by defining policies that connect
Business Entity: ROW
the roles defined in
Department: Marketing SelfASM
with the resources defined in MEC.
Billing Ann Dan Yan Kan Chan Ran
Seniority: Expert Service
MEC Security Concepts | Example
Ensuring managers will only have reading rights for elements in MEC will be
defined in MEC, and also via the user properties in ASM.

See the green path below:

Elementary
Resources Elements Queries Templates Types

Policy

Roles Client App. Manager Business Imp. Technical Imp.

Users

User Properties:
Business Entity: ROW
Department: Marketing Self
Billing Ann Dan Yan Kan Chan Ran
Seniority: Expert Service
What Have We Discussed So Far?

Unit content:
● MEC-RLC Introduction

● MEC Role Overview and Definition

● MEC User Types and Security Concepts

● RLC Role Overview and Definition

Amdocs Convergent Charging Modules
The second component this unit is focused on is Rating Logic Configurator (RLC).

Master Billing
Rating Logic
Enterprise Customer
Configurator
Catalog Management
(RLC)
(MEC) (BCM)
Messages Files

*Optional:
Mediation Turbo
Invoicing
And/or OCA Charging (TC)
And/or OFCA
RLC Highlights
The objects defined in RLC are used in rating and billing processes by various Amdocs
convergent charging applications (mainly MEC and TC).

RLC offers real-time rating support, using a GUI-based configurator for DIAMETER messages.
• Single integration point for the protocol and the business
• Reusable Diameter Data Dictionary, for fast implementation,
including standard Gy and Sy OOB
• Modifying Diameter protocol via RLC implementation –
AVP parsing and business logic definition
RLC Implementation Repository (IR)
This is a technical development environment used to define the data dictionary:

(For example, pricing item types, customer attributes, event types and more.)

Example:
• It is edited via RLC UI, which enables rapid
introduction of new services and pricing
schemes when code changes are expected.

• It is used to identify specific charge types in

the Billing system.
RLC Implementation Repository (IR)
X
• Technical development environment used to define data dictionary:
Implementation Repository Entities
(e.g. pricing item
• types, customer
Elementary attributes, event types and more.)
types
• Customer
• It is edited via RLC UI. That enables rapid introduction of new services and pricing schemes
• Event
where code changes areTypes
expected.
• External Records
• Used to identify specific charge types in the Billing system.
• Qualification Criteria
• Pricing Item Types
• Subscriber Parameters
• External Records
• Generic Reference Tables (GRT)
RLC Implementation Repository (IR)
X
Pricing Item
• Technical development environment used Type (PIT)data
to define – dictionary:
Basic technical element
(e.g. pricing item types,
i customer attributes, event types and more.)

• It is edited via RLC UI. That enables rapid introduction of new services and pricing schemes
where code changes are expected.
Hierarchy – Object
Oriented
• Used to identify specific charge typesApproach
in the Billing system.
i

Technical data –
rating formulas
RLC Implementation Repository (IR)
A PI is an accumulation of all events rated by a single pricing item, X
in a single
• Technical cycle of aenvironment
development single subscriber/agreement.
used to define data dictionary:

(e.g. pricing item types, customer attributes, event types and more.)

• It is edited via RLC UI. That enables rapid introduction of new services and pricing schemes
where code changes are expected.

• Used to identify specific charge types in the Billing system.

1 2
RLC Implementation Repository (IR)
X
• Technical development environment used to define data dictionary:
• The PI Extract is a charge Accumulations (PI) extract that is sent from TC
(e.g. pricingtoitem
Invoicing
types,ascustomer
part of Bill-Day calculations
attributes, (during
event types andthe “Bill Preparation”
more.)
process).
• It is edited via RLC UI. That enables rapid introduction of new services and pricing schemes
• The extract process extracts data from TC DB (and by TC) to Invoicing,
where code changes are expected.
according to RLC definitions.
As part of this process, the data is mapped from PI structure (TC DB) to
• Used to identify specific charge types in the Billing system.
charge structure (Invoicing), including attaching a charge code to each PI.

1 2
What Have We Discussed So Far?

Unit content:
● MEC-RLC Introduction

● MEC Role Overview and Definition

● MEC User Types and Security Concepts

● RLC Role Overview and Definition

Check Yourself
Do the following sentences describe MEC correctly?

Please choose the correct answer.

True False
1. It is a single point of entry for all product catalogs of the
organization.

2. It enables flexible definition of the catalog entities, and

enterprise-wide catalog management.

3. It includes role-based, data-driven security, with extended

user authorization capabilities.
Check Yourself
Billing product data can be divided into two categories:

Please select the correct value from the list.

• The Billing Technical information is defined in RLC

• The Billing Business information is defined in MEC

and is based on technical elements imported from RLC
 Check Yourself
There are three main groups of MEC users:

Please drag each sentence to its correct area.

Technical users Business users Administration users

Manage the activities that require Responsible for defining the

interfacing with external templates on which future Use the Catalog perspective
applications, such as creating a catalog elements, representing extensively for testing purposes.
list of external clients. products and services, are based.

Create and execute queries and Work mainly with the Designer Create and update the elements
Configure Enterprise Product
business rules. perspective. created based on the defined
Catalog.
template.
Check Yourself
There are three main groups of MEC users:

Technical users Business users Administration users

• Work mainly with the

Designer perspective • Configure Enterprise
• Create and update the
• Use the Catalog Product Catalog
elements created based • Manage the activities
perspective extensively
on the defined that require interfacing
for testing purposes.
template.
• Responsible for defining with external
• Create and execute applications, such as
the templates on which
queries and business creating a list of
future catalog elements,
rules. external clients.
representing products
and services, are based.
Review
In this unit you have learnt to:

Explain the functionality of Master Enterprise Catalog (MEC)

Explain the functionality of Rating Logic Configurator (RLC)

Explain MEC and RLC interfaces