Download presentation
Presentation is loading. Please wait.
Published byAlannah Campbell Modified over 7 years ago
1
Amdocs Convergent Charging and Billing Introduction_06_TC_Overview
Menu Name of segment in menu Name of Sub-segment in menu Starts at Slide number in SB Overview Structure overview 5 Introduction convergent charging overview 8 Architecture Fundamentals 13 TC Interactions |Applications TC Main Components Event Server 18 IMDG 20 File2E 23 DB2E 24 High Availability 28 AVM 30 TC System Topology 32 Failure Detection and H/A Components 33 Amdocs Error Manager 34 Check yourself Review 39 Production guidelines: This slide presents the slides to go from the storyboard menu Please pay attention that the slide numbers that I use are the numbers written on the slides (not the numbers on the PowerPoint slides)
2
Glossary
3
Design Requirements Replace circles with relevant icons from repository on slide 8.2>>. Please add relevant illustration to each of the features slide 8.3>>>>>>>>>>>>>>>>> redesign the chart, using relevant elements from repository slide 31>>>>>>>>>>>>>>>>>>>>>>>>>> Production guidelines: Please pay attention that the screen numbers that I use are the numbers written on the slides (not the numbers on the PowerPoint slides)
4
Turbo Charging Overview
Slide 1/page 1 Turbo Charging Overview Amdocs Convergent Charging and Billing: Introduction
5
Slide 1 / page 2
6
Slide 1 / page 3
7
Slide 1 / page 4
8
Slide 1 / page 5
9
Slide 1 / page 6 20
10
Slide 1 / page 7 Let’s Begin!
11
Recap Slide 2 In previous units you have learned about:
Purpose and functionality of the various connectors that interface with TC Architecture of each of these connectors Main processes that are run by each module Production guidelines: See template for animation, duration etc. Animation alternate automatically Bullets entrance animation: “Fly In”> from left, duration: 0.75
12
Objectives Slide 3 By the end of this unit you will be able to:
Explain the scope of Turbo Charging (TC) Conceptualize the TC architecture Identify the interfaces to and from TC Production guidelines: See template for animation, duration etc. Animation alternate automatically Number of the objective entrance animation: “Fade”, duration: 0.75 Objective entrance animation: “Fly In”> from left, duration: 0.75
13
Unit Content Slide 4 In this unit you will learn about: Introduction
Architecture Fundamentals TC Main Components High Availability Production guidelines: See template for animation, duration etc. Animation alternate automatically Bullets entrance animation: “Fly In”> from left, duration: 0.75
14
The Full Picture Slide 5 / page 1
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 Subscriber Resource Manager Amdocs Voucher Manager Amdocs Service Control Platform Manager Amdocs Document Designer Accounts Receivable Collections Replenishment Amdocs Error Manager Convergent Charging Production guidelines: Center element gets orange frame, the rest of the elements gets colored grey as demonstrated in the next slide.
15
The Full Picture Slide 5 / page 2
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 Subscriber Resource Manager Amdocs Voucher Manager Amdocs Service Control Platform Manager Amdocs Document Designer Accounts Receivable Collections Replenishment Amdocs Error Manager Convergent Charging Production guidelines: Use chart from 02_Data Flow in ABP_SB>>slide 6/page 1 Center element gets orange frame, the rest of the elements gets colored grey as demonstrated in the next slide. Directions to click appear above the chart.
16
Amdocs Convergent Charging Modules
Slide 6 Amdocs Convergent Charging Modules As seen in the previous unit, Amdocs Convergent Charging includes the following components. This unit will focus on Turbo Charging (TC). Master Enterprise Catalog (MEC) Billing Customer Management (BCM) *Optional: Mediation And/or OCA And/or OFCA Turbo Charging (TC) Invoicing Messages Files Rating Logic Configurator (RLC) Production guidelines: Use chart from 02_Data Flow in ABP_SB>>slide 12 mediation should be highlighted.
17
Learning Review Slide 7 What is Turbo Charging (TC)?
Please choose the correct answer. A UI for defining technical service-related data that has the rating logic and the tech definition. An integrated online and offline charging platform that can operate in multiple processing modes. A component that serves as a single point of offer definition and has the full set of rates. Production guidelines: See template for animation, duration etc. Allow 2 attempts in each question Generic feedbacks: Very Good Try Again Incorrect, note the correct answer Additional text in feedback according SB Reset to initial state when revisiting Correct answers are indicated by ID
18
Portfolio Orientation
Slide 8/page 1 The Bigger Picture The following points about the convergent charging system give a quick introduction. Please click each box to learn more. System Highlights System Structure Production guidelines: When the user rolls over each box on the left, a box appears on the right with content as shown on each slide. The orange frame is for developers. The selected box remains colored, the rest turn grey. Portfolio Orientation
19
Portfolio Orientation
Slide 8/page 2 The Bigger Picture The following points about the convergent charging system give a quick introduction. Please click each box to learn more. System Highlights Unified definition of pricing, rating, and policy parameters Holistic customer data management System Structure Optimized, standards-based charging and policy integration (Sy) Unified operations and monitoring Production guidelines: When the user rolls over each box on the left, a box appears on the right with content as shown on each slide. The orange frame is for developers. The selected box remains colored, the rest turn grey. Replace circles with relevant icons from repository. Rich charging and business context for policy triggers Portfolio Orientation
20
The Bigger Picture Slide 8/page 3
The following points about the convergent charging system give a quick introduction. Please click each box to learn more. System Highlights Amdocs Policy Controller Amdocs Convergent Charging Sy Customer & Subscriber Management Master Enterprise Catalog APP SERVER Gy Gx Rx PCEF System Structure Production guidelines: When the user rolls over each box on the left, a box appears on the right with content as shown on each slide. The orange frame is for developers. The selected box remains colored, the rest turn grey. redesign the chart, using relevant elements from repository. Portfolio Orientation
21
The Bigger Picture Slide 8/page 4
The following points about the convergent charging system give a quick introduction. Please click each box to learn more. System Highlights Invoicing & Document Designer Partner Management Policy Controller Convergent Charging Service Platform Master Enterprise Catalog Accounts Receivable & Collections Notification Manager Service Control Online Charging Adaptor BSS Customer Layer Core Network and Service Enablers Order Capture CRM Self Service Customer Manager GUI Product Enterprise Catalog Integration Layer Mediation Offline Charging Adaptor Customer Management System Structure Production guidelines: When the user rolls over each box on the left, a box appears on the right with content as shown on each slide. The orange frame is for developers. The selected box remains colored, the rest turn grey. Portfolio Orientation
22
TC Interactions | Networks
Slide 9/page 1 TC Interactions | Networks This chart presents how TC interacts with various types of networks. Note that many of the interfaces that are not DIAMETER-based, require connectors. Sy Gy INAP, AIN Rf, GTP Rx SMPP MSML, MSCML VXML Switch/ SSP PSTN NGN Networks & IMS (xDSL, WiMAX, LTE) AS S-CSCF Soft Switch Amdocs Policy Controller Gx Policy interfaces Wireless Networks (GSM/UMTS, CDMA/WCDMA) SIP/ ISC CAP, WIN MSC SMS-C MMS-C SGSN PDSN GGSN IP-Probe IVR/MS Amdocs Service Platform Amdocs Convergent Charging Production guidelines:
23
TC Interactions | Networks
Slide 9/page 2 TC Interactions | Networks This charts presents how TC interacts with various types of networks. Note that many of the interfaces which are not DIAMETER-based, require connectors. X TC interactions with various types of networks: It deploys quickly across multi-network environments. It is fully 3GPP R11 compliant for advanced data services. It supports legacy and IMS networks. Sy Gy INAP, AIN Rf, GTP Rx SMPP MSML, MSCML VXML Switch/ SSP PSTN NGN Networks & IMS (xDSL, WiMAX, LTE) AS S-CSCF Soft Switch Amdocs Policy Controller Gx Policy interfaces Wireless Networks (GSM/UMTS, CDMA/WCDMA) SIP/ ISC CAP, WIN MSC SMS-C MMS-C SGSN PDSN GGSN IP-Probe IVR/MS Amdocs Service Platform Amdocs Convergent Charging Production guidelines: Pop up appears when link from prev. slide is clicked
24
How it is used in charging?
Slide 10/page 1 Diameter The Diameter protocol is used in charging: Please click each box to learn more. What is it? Diameter is a communication protocol, adopted by the 3GPP organization as the standard for charging and policy interfaces. Succeeds its predecessor - RADIUS protocol. Diameter uses reliable transport protocols (TCP and SCTP). How it is used in charging? Production guidelines: When the user rolls over each box on the left, a box appears on the right with content as shown on each slide. The orange frame is for developers. The selected box remains colored, the rest turn grey.
25
How it is used in charging?
Slide 10/page 2 Diameter The Diameter protocol is used in charging: Please click each box to learn more. What is it? For charging purposes, it is used to implement both offline and online credit control for all services (voice, data, and messaging) DCCA = Diameter Credit Control Application OCS = Online Charging System For policy control purposes, it is used to implement policy enforcement. How it is used in charging? Production guidelines: When the user rolls over each box on the left, a box appears on the right with content as shown on each slide. The orange frame is for developers. The selected box remains colored, the rest turn grey.
26
Challenge Yourself Slide 11
Diameter performs three functions, referred to as AAA. What are these functions? Please drag each function to its correct definition. Collect info , with which to monitor the actual consumption of network services against a subscriber's allowance Restrict users from viewing or modifying items, or performing activities. Ensure that the user is the person who is logging in. Production guidelines: Correct answer: Authentication: make sure the user is the person that is logging in. Authorization: restrict users from viewing or modifying items, or performing activities. Accounting: collect info to monitor the actual consumption of network services against a subscriber's allowance Authentication Authorization Accounting
27
What Have We Discussed So Far?
Slide 12 What Have We Discussed So Far? Unit content: Introduction Architecture Fundamentals TC Main Components High Availability Production guidelines: See template for animation, duration etc. Animation alternate automatically All topics appear on screen when user enter the screen Topics that were covered are grayed out gradually
28
TC Highlights Slide 13/page 1
The experts are willing to give you both sales and IT highlights. Please click each character to find out more. Production guidelines: Once each character is clicked – the other character is getting grey. the relevant content appears in the textbox
29
Sales TC Highlights Slide 13/page 2
The experts are willing to give you both Sales and IT highlights. Please click each character to find out more. Its an innovative product and technology, delivering flexible, real-time, event processing at breakthrough performance levels. Convergent services, across lines of business and payment means, Ongoing rerating. Telco-grade monitoring capabilities, providing preemptive detection and SLA monitoring. Production guidelines: Once each character is clicked – the other character is getting grey. the relevant content appears in the textbox Sales
30
Sales TC Highlights Slide 13/page 2
The experts are willing to give you both Sales and IT highlights. Please click each character to find out more. Precompiled code for Business Implementation Converts RLC business logic into a set of compiled libraries that execute that logic Flexible implementation and a short time-to-market Performance of compiled code (vs. interpretation) Production guidelines: Once each character is clicked – the other character is getting grey. the relevant content appears in the textbox Sales
31
IT TC Highlights Slide 13/page 3 1 2 3
The experts are willing to give you both Sales and IT highlights. Please click each character to find out more. E2E Real-Time Charging 3GPP compliant architecture and interfaces Direct network connectivity via Diameter or any proprietary protocol Next-Generation Prepaid and Real-Time Support Designed for advanced data services Leverages cloud technology with Elastic OCS Production guidelines: Once each character is clicked – the other character is getting grey. the relevant content appears in the textbox IT 1 2 3
32
IT TC Highlights Slide 13/page 4 1 2
The experts are willing to give you both Sales and IT highlights. Please click each character to find out more. High availability architecture enables 24x7 charging availability with GR capabilities Pre-integrated Amdocs PCRF, enabling innovative data monetization Two-tier, best in class in-memory technology: Local cache via Amdocs In-Memory Object Store (AIMOS) - complex event-processing technology Carrier-grade Central In-Memory-Data-Grid (IMDG) Production guidelines: Once each character is clicked – the other character is getting grey. the relevant content appears in the textbox IT 1 2
33
TC Interactions |Applications
Slide 14/page 1 TC Interactions |Applications TC interacts with various applications. Amdocs Convergent Charging Enterprise Product Catalog Customer Management Event Routing Real-time Rating and Event Processing Account and Balance Management Charging Session Management Usage Data Customer Data Voucher Manager Amdocs Offline Charging Adaptor Amdocs Online Charging Adaptor Recharge Manager DRA Fixed Mobile IMS Session Control PCRF Production guidelines: Chart should be redesigned using elements and components from repository After clicking next, the screen gets grey (apart from the framed elements) as demonstrated in the next slides
34
TC Interactions |Applications
Slide 14/page 2 TC Interactions |Applications TC interacts with various applications. Please click each application to find out more about. Amdocs Convergent Charging Enterprise Product Catalog Customer Management Event Routing Real-time Rating and Event Processing Account and Balance Management Charging Session Management Usage Data Customer Data Voucher Manager Amdocs Offline Charging Adaptor Amdocs Online Charging Adaptor Recharge Manager DRA Fixed Mobile IMS Session Control PCRF A voucher is a one-time payment method that may be purchased at a kiosk or store and which the purchaser can use, at his or her convenience, to recharge a communications services provider account. Amdocs Voucher Manager handles all aspects of prepaid vouchers, including ordering and distribution, voucher maintenance, queries and reports. Production guidelines: Chart should be redesigned using elements and components from repository After clicking next, the screen gets grey (apart from the framed elements) as demonstrated in the next slides
35
TC Interactions |Applications
Slide 14/page 3 TC Interactions |Applications TC interacts with various applications. Please click each application to find out more about. Amdocs Convergent Charging Enterprise Product Catalog Customer Management Event Routing Real-time Rating and Event Processing Account and Balance Management Charging Session Management Usage Data Customer Data Voucher Manager Amdocs Offline Charging Adaptor Amdocs Online Charging Adaptor Recharge Manager DRA Fixed Mobile IMS Session Control PCRF Amdocs Recharge Manager recharges and adjusts prepaid account balances. It also monitors and logs the transaction details, and enables viewing of recharge transactions and the prepaid balance information. Production guidelines: Chart should be redesigned using elements and components from repository After clicking next, the screen gets grey (apart from the framed elements) as demonstrated in the next slides
36
TC Interactions |Applications
Slide 14/page 3 TC Interactions |Applications TC interacts with various applications. Please click each application to find out more about. Amdocs Convergent Charging Enterprise Product Catalog Customer Management Event Routing Real-time Rating and Event Processing Account and Balance Management Charging Session Management Usage Data Customer Data Voucher Manager Amdocs Offline Charging Adaptor Amdocs Online Charging Adaptor Recharge Manager DRA Fixed Mobile IMS Session Control PCRF Online Charging Adaptor (OCA) is a charging front end for Turbo Charging used to provide enhanced network connectivity for data charging scenarios. Production guidelines: Chart should be redesigned using elements and components from repository After clicking next, the screen gets grey (apart from the framed elements) as demonstrated in the next slides
37
TC Interactions |Applications
Slide 14/page 4 TC Interactions |Applications TC interacts with various applications. Please click each application to find out more about. Diameter Routing Agents (DRAs) are external, third-party components that perform the following functions: Forward the event traffic to the currently active site and return the responses to the network elements. Maintain statistics representing the quality of service at each site and expose them through Web services (SOAP or HTTP). Handle Degraded mode when the active site is not functioning well. Amdocs Convergent Charging Enterprise Product Catalog Customer Management Event Routing Real-time Rating and Event Processing Account and Balance Management Charging Session Management Usage Data Customer Data Voucher Manager Amdocs Offline Charging Adaptor Amdocs Online Charging Adaptor Recharge Manager DRA Fixed Mobile IMS Session Control PCRF Production guidelines: Chart should be redesigned using elements and components from repository After clicking next, the screen gets grey (apart from the framed elements) as demonstrated in the next slides
38
TC Interactions |Applications
Slide 14/page 5 TC Interactions |Applications TC interacts with various applications. Please click each application to find out more about. Amdocs Convergent Charging Enterprise Product Catalog Customer Management Event Routing Real-time Rating and Event Processing Account and Balance Management Charging Session Management Usage Data Customer Data Voucher Manager Amdocs Offline Charging Adaptor Amdocs Online Charging Adaptor Recharge Manager DRA Fixed Mobile IMS Session Control PCRF An Amdocs Mediation-based component that receives usage event records from various network elements or mediators, validates these records, and then reformats them for further processing by Turbo Charging. Production guidelines: Chart should be redesigned using elements and components from repository After clicking next, the screen gets grey (apart from the framed elements) as demonstrated in the next slides
39
TC Interfaces Slide 15/page 1
Which applications will send data to Turbo Charging? Please click each box to learn more. Turbo Charging charges for use of services offered by a provider. Network Element Amdocs Replenishment Manager (RPL) Amdocs Invoicing Turbo Charging (TC) Production guidelines: Replace circles with icons from repository. Next slides shows “hovered” state of each element.
40
TC Interfaces Slide 15/page 2 i
Which applications will send data to Turbo Charging? Please click each box to learn more. These services are supported over a network infrastructure that includes network elements. The network elements are clients of Turbo Charging, which send events in sockets or files. These are the entities from where we receive the events. Network Element Amdocs Replenishment Manager (RPL) Amdocs Invoicing Turbo Charging (TC) Each implementation could be receiving different types of events from different network elements for different services like VoIP, IPTV, Gaming and so forth. Production guidelines: Replace circles with icons from repository. Next slides shows “hovered” state of each element. i
41
TC Interfaces Slide 15/page 3
Which applications will send data to Turbo Charging? Please click each box to learn more. The Amdocs Replenishment Manager is a gateway for users performing balance operations like topping up a balance, checking a balance and closing a balance. It might be connected to CSRs, ATMs, IVR systems, Amdocs Voucher Management and so on. These systems generate events and send them to Turbo Charging for processing. Network Element Amdocs Replenishment Manager (RPL) Amdocs Invoicing Turbo Charging (TC) Production guidelines: Replace circles with icons from repository. Next slides shows “hovered” state of each element.
42
TC Interfaces Slide 15/page 4
Which applications will send data to Turbo Charging? Please click each box to learn more. Amdocs Invoicing will request data to include in the bill at the end of the cycle and will issue an end-of-cycle rerate request. These are also sent as events to Turbo Charging for processing. Network Element Amdocs Replenishment Manager (RPL) Amdocs Invoicing Turbo Charging (TC) Production guidelines: Replace circles with icons from repository. Next slides shows “hovered” state of each element.
43
What Have We Discussed So Far?
Slide 16 What Have We Discussed So Far? Unit content: Introduction Architecture Fundamentals TC Main Components High Availability Production guidelines: See template for animation, duration etc. Animation alternate automatically All topics appear on screen when user enter the screen Topics that were covered are grayed out gradually
44
Convergent Charging - Architecture
Slide 17/page 1 Convergent Charging - Architecture This chart shows the TC architecture. We will now review its various applications by zone: Network Element File2E Usage DB Customer Mgmnt DB2E DB Server Customer DB Product Catalog Implementation Complier Offline Mediation AVM AEM A&C CSR AMC External Systems Dispatch Invoicing Extract Operation Domain Network Domain Business and Financials Domain Online Charging Events Offline Charging Files Usage Query Persistence Control, management Recycle Offline Charging Events Notifications Event Server In-Memory Data Grid
45
Convergent Charging - Architecture
Slide 17/page 2 Convergent Charging - Architecture This chart shows the TC architecture. We will now review its various applications by zone: Network Element File2E Usage DB Customer Mgmnt DB2E DB Server Customer DB Product Catalog Implementation Complier Offline Mediation AVM AEM A&C CSR AMC External Systems Dispatch Invoicing Extract Operation Domain Network Domain Business and Financials Domain Online Charging Events Offline Charging Files Usage Query Persistence Control, management Recycle Offline Charging Events Notifications Event Server In-Memory Data Grid
46
Slide 18 Event Server Event Server Event Server (ES) is the main processing daemon of the TC event processing platform: It can receive incoming events (EDRs) from multiple systems: Various NEs (Network Elements) Mediation Amdocs RPL (Replenishment/Recharge Manager) Subsequently, it processes the events Then it uses the result to: Respond to the NEs and replenishment agents Store the rated events and accumulators in the Usage database
47
Challenge Yourself Slide 19/page 1
Event Server The ES architecture defines the following modules and functions as part of a single, configurable process: Please arrange the steps of the process in the correct order: Network Interface Route to Customer Evaluation Write to IMDG Persistence Persistence Evaluation Network Interface Production Guidelines: This should not be an actual question but a guided exercise. When the user drags a box to its correct place, it gets a green glow. If the place is not correct while hover it has a red glow, and when released the box jumps back to its starting point. Write to IMDG Route to Customer
48
Challenge Yourself Slide 19/page 1
Event Server The ES architecture defines the following modules and functions as part of a single, configurable process: Please arrange the steps of the process in the correct order. Network Interface Route to Customer Evaluation Write to IMDG Persistence Network Interface Persistence Evaluation Production Guidelines: This should not be an actual question but a guided exercise. When the user drags a box to its correct place, it gets a green glow. If the place is not correct while hover it has a red glow, and when released the box jumps back to its starting point. **this is only an example for the elements behavior** Write to IMDG Route to Customer
49
Challenge Yourself Slide 19/page 2
Event Server The ES architecture defines the following modules and functions as part of a single, configurable process: Please arrange the steps of the process in the correct order. Network Interface Route to Customer Evaluation Write to IMDG Persistence Production Guidelines: This should not be an actual question but a guided exercise. When the user drags a box to its correct place, it gets a green glow. If the place is not correct while hover it has a red glow, and when released the box jumps back to its starting point. **this is the correct order**
50
Convergent Charging - Architecture
Slide 17/page 3 Convergent Charging - Architecture This chart represents the TC architecture. We will now review its various applications by zone: Network Element File2E Usage DB Customer Mgmnt DB2E DB Server Customer DB Product Catalog Implementation Complier Offline Mediation AVM AEM A&C CSR AMC External Systems Dispatch Invoicing Extract Operation Domain Network Domain Business and Financials Domain Online Charging Events Offline Charging Files Usage Query Persistence Control, management Recycle Offline Charging Events Notifications Event Server In-Memory Data Grid
51
IMDG Overview Slide 20 Let’s define the In Memory Data Grid (IMDG):
Data Grid is the combination of computers that works together to manage information and reach a common goal of storing data in a highly-available distributed cache. Data is stored in memory, is always available and consistent. Please click each box to learn which solutions IMDG provides: Linear Scalability Partitioned Replication Low Latency No Single Point of failure Elastic The IMDG solution provides: Production guidelines: The chart is presented schematically. Should be re designed.
52
IMDG Overview Slide 21/page 1 What are the benefits of using IMDG?
Highly-efficient event processing: Event counters and data is shared among all processing units. The grid provides a simple way to grow and shrink capacity for event processing Rapidly responding to fluctuating event processing requirements Adding and removing processing units is simple and done on the fly. The key to elasticity lies in the smart use of data grids. Click here to get more technical information about elasticity
53
IT IMDG Overview Slide 22/page 2 Elastic Online Charging Cloud X 1 2
What are the benefits in using IMDG? Dynamic allocation of charging resources using an elastic, highly-available cloud topology: Highly efficient event processing: event counters and data is shared among all processing units. The grid provides a simple way to grow and shrink capacity for event processing Rapidly responding to fluctuating event processing requirements Adding and removing processing units is simple and done on the fly The key to elasticity lies in the smart use of data grids Click here to get more technical information about elasticity Improved capacity planning - easily expand processing power in line with demand Reduced operational costs - handle demand peaks Enhanced high availability: Building redundancy architecture leveraging N+M HA architecture Continuous service when the database is down or slow Session-level geo-redundancy Production guidelines: This pop up appears after clicking the link in the previous slide, and it contains two screens IT 1 2
54
In-Memory Data Grid (IMDG)
Slide 22/page 3 IMDG Overview Elastic Online Charging Cloud X What are the benefits in using IMDG? IMDG serves as the layer that holds a replica of the ES Mem (instead of another ES as happens currently). This provides the flexibility to take down and bring up machines much more easily. It is not bound to H/A. Furthermore H/A will support N+M architecture, which no other competitor offers today. It is not dependent on the database, therefore RAC is not necessary. Highly efficient event processing: event counters and data is shared among all processing units. The grid provides a simple way to grow and shrink capacity for event processing Rapidly responding to fluctuating event processing requirements Adding and removing processing units is simple and done on the fly The key to elasticity lies in the smart use of data grids Click here to get more technical information about elasticity Network Elements In-Memory Data Grid (IMDG) Business Logic Persistent Data Layer ES Network FE and Routing Decouples the business processes from the underlying infrastructure Production guidelines: This pop up appears after clicking the link in the previous slide, and it contains two screens IT 1 2
55
Convergent Charging - Architecture
Slide 17/page 4 Convergent Charging - Architecture This chart represents the TC architecture. We will now review its various applications by zone: Network Element File2E Usage DB Customer Mgmnt DB2E DB Server Customer DB Product Catalog Implementation Complier Offline Mediation AVM AEM A&C CSR AMC External Systems Dispatch Invoicing Extract Operation Domain Network Domain Business and Financials Domain Online Charging Events Offline Charging Files Usage Query Persistence Control, management Recycle Offline Charging Events Notifications Event Server In-Memory Data Grid
56
File to Event Slide 23/page 1 File2E
File to Event (File2E) Server is a TC process that extracts event data from files and then sends the events contained in these files to the relevant event servers. File2E can receive files from various systems: Amdocs Mediation External mediation systems (SCF) Rejected Event Recycler VoIP GSM IPTV Event Server Need an elaborated explanation? Click the figure to learn more!
57
File to Event Slide 23/page 2 X File2E | Tell Me More File2E
Customers consume a variety of services offered by their provider including: VoIP, IPTV, GSM and more. The network infrastructure supporting these services, generates an event that details service usage every time a service is consumed. These events are stored in files. In Turbo Charging, internally-formatted events are processed by the event servers. Therefore, an intermediate process is necessary, with which to take the raw events from the input file and translate them into the format expected by the event servers, to enable them to perform tasks like rating. X File to Event (File2E) Server is a TC process that extracts event data from files and then sends the events contained in these files to the relevant Event Servers. File2E can receive files from various systems: Amdocs Mediation External mediation systems (SCF) Rejected Event Recycler VoIP GSM IPTV Event Server Need an elaborated explanation? Click the figure!
58
File to Event Slide 23/page 3 X File2E | Tell Me More File2E
File2E extracts raw event data from the files, reformats them and then sends the events contained in these files to their event servers. The re-formatted events are sent from the File2E into the system, similar to how events are processed in a standard network connection. One File2E process might distribute data to several event server processes, consistent with the event resource attributes. The event servers might be located on the same machine as File2E or on a different one. X File to Event (File2E) Server is a TC process that extracts event data from files and then sends the events contained in these files to the relevant Event Servers. File2E can receive files from various systems: Amdocs Mediation External mediation systems (SCF) Rejected Event Recycler VoIP GSM IPTV Event Server Need an elaborated explanation? Click the figure!
59
Convergent Charging - Architecture
Slide 17/page 4 Convergent Charging - Architecture This chart represents the TC architecture. We will now review its various applications by zone: Network Element File2E Usage DB Customer Mgmnt DB2E DB Server Customer DB Product Catalog Implementation Complier Offline Mediation AVM AEM A&C CSR AMC External Systems Dispatch Invoicing Extract Operation Domain Network Domain Business and Financials Domain Online Charging Events Offline Charging Files Usage Query Persistence Control, management Recycle Offline Charging Events Notifications Event Server In-Memory Data Grid
60
Updating Customer and Resource Data
Slide 24/page 1 DB2E DB Server Customer DB Updating Customer and Resource Data The following components are involved in updating customer and resource data in TC: Please click each box to learn more. Update Handler (UH) A process that is responsible for the transfer of changes from the BCM database to the internal TC customer database In addition, it updates the TC customer database with changes to the generic applicative tables (GATs) and informs the GAT2E process of the latest updates Database to Event Server (DB2E) Production guidelines: When the user rolls over each box on the left, a box appears on the right with content as shown on each slide. The orange frame is for developers. The selected box remains colored, the rest turn grey. 1 2
61
Updating Customer and Resource Data
Slide 24/page 2 DB2E DB Server Customer DB Updating Customer and Resource Data The following components are involved in updating customer and resource data in TC: Please click each box to learn more. Update Handler (UH) Update handler can work in two modes: Full mode – In this mode, the UH transfers a mass of system customers from BCM to the internal TC customer DB. Incremental mode – In this mode, the UH extracts and loads data according to external requests. for example: transactions from TRB, files from A&C (Audit & Control), or any other source. Database to Event Server (DB2E) Production guidelines: When the user rolls over each box on the left, a box appears on the right with content as shown on each slide. The orange frame is for developers. The selected box remains colored, the rest turn grey. 1 2
62
Updating Customer and Resource Data
Slide 24/page 3 DB2E DB Server Customer DB Updating Customer and Resource Data The following components are involved in updating customer and resource data in TC: Please click each box to learn more. Update Handler (UH) The DB2E component detects changes in the internal customer database and transfers this data to the ES that is responsible for handling this customer. These changes are transferred from BCM to the internal customer database, which serves as a master and back-up for the TC application. From this database, data is inserted into the in-memory representation in the Amdocs In-Memory Object Storage (AIMOS). Database to Event Server (DB2E) Production guidelines: When the user rolls over each box on the left, a box appears on the right with content as shown on each slide. The orange frame is for developers. The selected box remains colored, the rest turn grey.
63
Updating Customer and Resource Data
Slide 24/page 3 DB2E DB Server Customer DB Updating Customer and Resource Data The following components are involved in updating customer and resource data in TC: Please click each box to learn more. Update Handler (UH) The DB2E component detects changes in the internal customer database and transfers this data to the ES that is responsible for handling this customer. These changes are transferred from BCM to the internal customer database, which serves as a master and back-up for the TC application. From this database, data is inserted into the in-memory representation in the Amdocs In-Memory Object Storage (AIMOS). Database to Event Server (DB2E)
64
Customer Information Updates
Slide 25 Customer Information Updates After reviewing the various components, we can understand the Customer Information Updates process flow: BCM Update Handler Extracting Publishing Reading Customers Tech. Events Control DB2E ES Event TRB
65
Challenge Yourself | Slide 26
Changes in the customer and resource data include the following: Please choose all the correct answers. Creation of new customers Updates of offers and offer parameters Changing of pay channel details Updates of the resources available to the customer Change in the logical date of the system
66
What Have We Discussed So Far?
Slide 27 What Have We Discussed So Far? Unit content: Introduction Architecture Fundamentals TC Main Components High Availability Production guidelines: See template for animation, duration etc. Animation alternate automatically All topics appear on screen when user enter the screen Topics that were covered are grayed out gradually
67
! Challenge Yourself Availability: 𝑢𝑝𝑡𝑖𝑚𝑒 𝑡𝑜𝑡𝑎𝑙 𝑡𝑖𝑚𝑒 Slide 28
High availability is measured by the percentage of time during which the system/component is available for all its users. What should be the uptime to declare high availability? Please choose the correct answer. 100% 95.555% 99.555% 99.999% ! Availability: 𝑢𝑝𝑡𝑖𝑚𝑒 𝑡𝑜𝑡𝑎𝑙 𝑡𝑖𝑚𝑒 Production guidelines: See template for animation, duration etc. Allow 2 attempts in each question Generic feedbacks: Very Good Try Again Incorrect, note the correct answer Additional text in feedback according SB Reset to initial state when revisiting Correct answers are indicated by ID
68
High Availability (H/A)
Slide 29 High Availability (H/A) Process failure Host failure IMDG node failure Database persistence failure Database failure What is high availability? Many failure scenarios are possible in complex systems that contain many interrelated entities – click here for an example. High availability is a method for ensuring the continuous functioning of the system. Availability Manager is the main component responsible for the high availability processes. High Availability across all layers (as seen in chart:) i Primary DB App Host 1 Active ES Shadow ES Alternate IMDG App Host 2 Replication Persistence
69
Convergent Charging - Architecture
Slide 17/page 5 Convergent Charging - Architecture This chart represents the TC architecture. We will now review its various applications by zone: Network Element File2E Usage DB Customer Mgmnt DB2E DB Server Customer DB Product Catalog Implementation Complier Offline Mediation AVM AEM A&C CSR AMC External Systems Dispatch Invoicing Extract Operation Domain Network Domain Business and Financials Domain Online Charging Events Offline Charging Files Usage Query Persistence Control, management Recycle Offline Charging Events Notifications Event Server In-Memory Data Grid
70
Availability Manager (AVM)
Slide 30/page 1 Availability Manager (AVM) The following points about the AVM provide a quick introduction. Please click each box to learn more. What is AVM? The AVM maintains a highly-available system. Its main purpose is to monitor the state of all of the processes and ensure that the system is continuously available, as well as detecting failures of network entities in real-time. Decisions it makes about failovers are based on at least a cross-check between the data gathered from all critical processes in the system. AVM function when a failure is detected Production guidelines: When the user rolls over each box on the left, a box appears on the right with content as shown on each slide. The orange frame is for developers. The selected box remains colored, the rest turn grey. AVM Responsibilities
71
Availability Manager (AVM)
Slide 30/page 2 Availability Manager (AVM) The following points about the AVM provide a quick introduction. Please click each box to learn more. What is AVM? When a failure is detected, the Availability Manager receives a message containing this information and immediately invokes a set of commands to handle it. AVM locates an alternative component that can take control of the failed component’s responsibility. It also updates its internal network snapshot. AVM function when a failure is detected Production guidelines: When the user rolls over each box on the left, a box appears on the right with content as shown on each slide. The orange frame is for developers. The selected box remains colored, the rest turn grey. AVM Responsibilities
72
Availability Manager (AVM)
Slide 30/page 3 Availability Manager (AVM) The following points about the AVM provide a quick introduction. Please click each box to learn more. What is AVM? Starting the daemons through the Availability Manager plug-in to Amdocs Monitoring & Control (AMC) Monitoring the health of each process Moving processes (and their segments, in the case of the Event Server) to another host at the time of failover Sending admin messages to processes AVM function when a failure is detected Production guidelines: When the user rolls over each box on the left, a box appears on the right with content as shown on each slide. The orange frame is for developers. The selected box remains colored, the rest turn grey. AVM Responsibilities
73
Challenge Yourself | Availability Manager
Slide 31/page 1 Challenge Yourself | Availability Manager Let’s have a look at the process flow: Please drag each sentence to its correct location. Application Servers AVM AMC The AVM component is the system controller responsible for monitoring each of the servers in the event processing flow. AMC will then send these commands to AVM. AVM will then send the command on the proper server in order to be executed. Commands to start, stop, shift, suspend, and resume processes can be issued through AMC. Production guidelines: redesign the chart, using relevant elements from repository. The AVM component is the system controller responsible for monitoring each of the servers in the Event Processing flow. AVM will then send the command on the proper server, to be executed. Commands to start, stop, shift, suspend, and resume processes can be issued through AMC. AMC will then send these commands to AVM. All commands must pass through AVM!
74
Challenge Yourself | Availability Manager
Slide 31/page 1 Challenge Yourself | Availability Manager Let’s have a look at the process flow: Please drag each sentence to its correct location. Application Servers AVM AMC The AVM component is the system controller responsible for monitoring each of the servers in the Event Processing flow. AMC will then send these commands to AVM. All commands must pass through AVM! AVM will then send the command on the proper server, to be executed. Commands to start, stop, shift, suspend, and resume processes can be issued through AMC. Production guidelines: redesign the chart, using relevant elements from repository.
75
TC System Topology Slide 32/page 1
So how does it actually work? Have a look at this representation of the small server high availability system topology.
76
Here we can clearly see that we have three servers (Host 1, 2, and 3).
Slide 32/page 2 TC System Topology So how does it actually work? Have a look at this representation of the small server high availability system topology. Here we can clearly see that we have three servers (Host 1, 2, and 3).
77
TC System Topology Slide 32/page 3
So how does it actually work? Have a look at this representation of the small server high availability system topology. As seen on Host 1, each host has active and passive Event Server processes, each can handle different groups and different functionality based on a configurable system topology.
78
TC System Topology Slide 32/page 4
So how does it actually work? Have a look at this representation of the small server high availability system topology. You can also see the internal and external watchdog processes of the Availability Manager component. If these detect a fault in an Event Server process, the customer groups served by that process can be transferred to the backup event servers on the other hosts.
79
TC System Topology Slide 32/page 5
So how does it actually work? Have a look at this representation of the small server high availability system topology. Different customer groups reside in the AIMOS on each of our hosts. For example, Customer groups 1,2,3, and 4 are processed on the active event server on Host 1.
80
TC System Topology Slide 32/page 6
So how does it actually work? Have a look at this representation of the small server high availability system topology. The passive (or hot standby) Event Server processes for these customer groups are located on Hosts 2 and 3. Customer groups 1 and 2 are on Host 2 customer groups 3 and 4 are on Host 3.
81
Try It Yourself Slide 32/page 7 1 3 5 2 4 6 3 1 2 6 4 5
To better understand how it works, click the customer groups that are processed on the active event server on each host: 1 3 5 2 4 6 3 1 2 Production guidelines: When the learner rolls over the groups that are on the top part of the chart (marked in blue numbers) the group gets a red frame’ ant its twin-group (same number only green) gets frame as well. 6 4 5
82
Failure Detection and H/A Components
Slide 33/page 1 Failure Detection and H/A Components These four components have a role in failure detection: Please click each box to learn more. App Host 3 EWD Active ES Shadow ES IWD Agent App Host 2 App Host 1 Availability Manager (AVM) Master Availability Manager (AVM) Slave Quorum Availability Manager (AVM) Gathers availability info from all sources Decides/Executes failover or change of routing Maintains routing tables and site topology Internal Watchdog (IWD) External Watchdog (EWD) Production guidelines: When the user click each box on the left, the box on the middle receives content as shown on each slide. The selected box gets colored (and should also change in “hover” mode) the rest remain grey. The chart on the right receives a glowing frame around the relevant component as demonstrated. Agent
83
Failure Detection and H/A Components
Slide 33/page 2 Failure Detection and H/A Components These four components have a role in failure detection: Please click each box to learn more. App Host 3 EWD Active ES Shadow ES IWD Agent App Host 2 App Host 1 Availability Manager (AVM) Master Availability Manager (AVM) Slave Quorum Availability Manager (AVM) Detect abnormal behavior Reports queues and buffers state Internal Watchdog (IWD) External Watchdog (EWD) Production guidelines: When the user click each box on the left, the box on the middle receives content as shown on each slide. The selected box gets colored (and should also change in “hover” mode) the rest remain grey. The chart on the right receives a glowing frame around the relevant component as demonstrated. Agent
84
Failure Detection and H/A Components
Slide 33/page 3 Failure Detection and H/A Components These four components have a role in failure detection: Please click each box to learn more. App Host 3 EWD Active ES Shadow ES IWD Agent App Host 2 App Host 1 Availability Manager (AVM) Master Availability Manager (AVM) Slave Quorum Availability Manager (AVM) Wraps every process monitored by AVM Captures process failure and attempts to restart Internal Watchdog (IWD) External Watchdog (EWD) Production guidelines: When the user click each box on the left, the box on the middle receives content as shown on each slide. The selected box gets colored (and should also change in “hover” mode) the rest remain grey. The chart on the right receives a glowing frame around the relevant component as demonstrated. Agent
85
Failure Detection and H/A Components
Slide 33/page 4 Failure Detection and H/A Components These four components have a role in failure detection: Please click each box to learn more. App Host 3 EWD Active ES Shadow ES IWD Agent App Host 2 App Host 1 Availability Manager (AVM) Master Availability Manager (AVM) Slave Quorum Availability Manager (AVM) Acts as AVM representative on every host to carry commands Receives local heartbeats from all components residing on the host Collects operational measurement Internal Watchdog (IWD) External Watchdog (EWD) Production guidelines: When the user click each box on the left, the box on the middle receives content as shown on each slide. The selected box gets colored (and should also change in “hover” mode) the rest remain grey. The chart on the right receives a glowing frame around the relevant component as demonstrated. Agent
86
Amdocs Error Manager (AEM)
Slide 34/page 1 Amdocs Error Manager (AEM) There is also a solution for usage errors - Amdocs Error Manager (AEM). Please click each box to learn more. AEM Description AEM is an error management module, which: Accepts the rejected records and allows users to make corrections Handles errors from multiple systems into a single resolution platform Enables automated/manual error resolution AEM GUI Production guidelines: When the user rolls over each box on the left, a box appears on the right with content as shown on each slide. The orange frame is for developers. The selected box remains colored, the rest turn grey.
87
Amdocs Error Manager (AEM)
Magnifying glass on all screen shots as default. ! Slide 34/page 2 Amdocs Error Manager (AEM) There is also a solution for usage errors - Amdocs Error Manager (AEM). Please click each box to learn more. AEM Description Easy-to-use graphic interface enables rapid and flexible configuration of new rules for error correction: AEM GUI Production guidelines: When the user rolls over each box on the left, a box appears on the right with content as shown on each slide. The orange frame is for developers. The selected box remains colored, the rest turn grey.
88
What Have We Discussed So Far?
Slide 35 What Have We Discussed So Far? Unit content: Introduction Architecture Fundamentals TC Main Components High Availability Production guidelines: See template for animation, duration etc. Animation alternate automatically All topics appear on screen when user enter the screen Topics that were covered are grayed out gradually
89
Check Yourself Slide 36/page 1
What are the steps that are performed in File2E? Please arrange the steps of the process in the correct order. Translates them into the format that the ES can receive Takes the events in a file Sends them to the relevant ES for processing Sends them to the relevant ES for processing Production guidelines The correct answer is on the next slide. Takes the events in a file Translates them into the format that the ES can receive
90
Check Yourself Slide 36/page 2
What are the steps that are performed in File2E? Please arrange the steps of the process in the correct order. Translates them into the format that the ES can receive Takes the events in a file Sends them to the relevant ES for processing Sends them to the relevant ES for processing Production guidelines This is the correct answer Takes the events in a file Translates them into the format that the ES can receive
91
Check Yourself Slide 37 Drop down list example:
Can you define each component’s functionality? Please select the correct value from the list. is the system controller responsible for monitoring each of the servers in the event processing flow. Commands to start, stop, shift, suspend, and resume processes can be issued through These commands will be sent to , where all commands must pass before they are executed in Turbo Charging. will then send the command on the proper server, to be executed. AVM AMC Production guidelines: The correct answer: AVM is the system controller responsible for monitoring each of the servers in the event processing flow. Commands to start, stop, shift, suspend, and resume processes can be issued through AMC. these commands will be sent to AVM, where all AMC commands must pass before they are executed in Turbo Charging. AVM will then send the command on the proper server in order to be executed.
92
Slide 38 Check Yourself Which of the failure detection components acts as AVM representative on every host to carry commands? Please choose the correct answer. IWD OWD Agents AMC Production guidelines: See template for animation, duration etc. Allow 2 attempts in each question Generic feedbacks: Very Good Try Again Incorrect, note the correct answer Additional text in feedback according SB Reset to initial state when revisiting Correct answers are indicated by ID
93
Review Slide 39 In this unit you have learnt to:
Explain the scope of Turbo Charging (TC) Conceptualize the TC architecture Identify the interfaces to and from TC Production guidelines: See template for animation, duration etc. Animation alternate automatically All objective appear on screen when user enter the screen Objectives are greyed out gradually
Similar presentations
© 2025 SlidePlayer.com Inc.
All rights reserved.