System and method for managing network services using rating function in a communication network

Abstract

Disclosed is a system (300) and a method (500) for managing network services using a Rating Function (RF) (224) in a communication network (100). The system (300) includes a load balancer (304), multiple Platform Front End (PFE) nodes (306), and the RF (224). The load balancer (304) receives network input(s) corresponding to the network service(s) from network interface(s) in the communication network (100) and identifies one PFE node (306) for each network input. Each identified PFE node (306) parses a corresponding network input to generate network data in a format compatible with the RF (224). The network data enables the RF (224) to manage the one or more network services.

Description

[0001] SYSTEM AND METHOD FOR MANAGING NETWORK SERVICES

[0002] USING RATING FUNCTION IN A COMMUNICATION NETWORK

[0003] TECHNICAL FIELD

[0004] [1] The embodiments of the present disclosure generally relate to the field of wireless communication networks. More particularly, the present disclosure relates to a system and a method for managing network services using Rating Function (RF) in a communication network.

[0005] BACKGROUND OF THE INVENTION

[0006] [2] The subject matter disclosed in the background section should not be assumed or construed to be prior art merely because of its mention in the background section. Similarly, any problem statement mentioned in the background section or its association with the subject matter of the background section should not be assumed or construed to have been previously recognized in the prior art.

[0007] [3] In modern telecommunication systems, various types of network services are managed, billed, and rated through complex methods and systems involving multiple subsystems and interfaces. One key component of these systems is the Online Charging Function (OCF) which is responsible for real-time charging and managing the subscriber’s account balance. Another crucial component of the system is Rating Function (RF) node which is responsible for determining the cost associated with a specific service or communication event. These components are the fundamentals for accurate billing of various services such as voice, data, messaging, and multimedia messaging.

[0008] [4] Data parsing and interpretation is required to determine appropriate rate (e.g., tariff) for a network service. The data associated with the network service contains details of the subscriber, the services being used, and other relevant parameters such as duration of the call, amount of data used, or size of the multimedia sent, etc. However, the process of parsing the data to make it usable for the RF node is a computationally expensive task, which increases the resource utilization as the data needs to be extracted and converted into a suitable format for the RF node to process. This makes the entire process highly inefficient and redundant.

[0009] [5] Moreover, the rating requests (e.g., tariff determination requests) for a variety of network services through a variety of interfaces (e.g., Ro, Sy, Gy, Radius etc.) require parsing to comprehend the specifics of the service and the subscriber before applying rules to find the rate (e.g., tariff), which significantly adds to the expenses for parsing and storing the data received from Diameter interfaces in Rating Engine Module.

[0010] [6] In view of the above-mentioned challenges, there is need of a technical solution that can enhance efficiency and accuracy of the rating and billing process and reduce the expenses and computational burden on the network.

[0011] SUMMARY

[0012] [7] The following embodiments present a simplified summary in order to provide a basic understanding of some aspects of the disclosed invention. This summary is not an extensive overview, and it is not intended to identify key / critical elements or to delineate the scope thereof. Its sole purpose is to present some concepts in a simplified form as a prelude to the more detailed description that is presented later.

[0013] [8] According to an embodiment of the present disclosure, a method for managing network services using Rating Function (RF) in a communication network is disclosed. The method includes receiving, by a load balancer from one or more network interfaces in the communication network, one or more network inputs corresponding to the one or more network services. The method further includes identifying, for each network input of the one or more network inputs by the load balancer, a Platform Front End (PFE) node from a plurality of PFE nodes in the communication network. Furthermore, the method includes parsing, by each identified PFE node, a corresponding network input to generate network data in a format compatible with the RF. The network data enables the RF to manage the one or more network services.

[0014] [9] In some aspects of the present disclosure, each network input comprises a service identifier (ID) associated with a corresponding network service from the one or more network services. The PFE node is identified from the plurality of PFE nodes based on the service ID.

[0015]

[0010] In some aspects of the present disclosure, for parsing the network input, the method includes transforming, by the corresponding identified PFE node, the network input using a transformation function specific to a type of the network interface.

[0016]

[0011] In some aspects of the present disclosure, the method further includes transmitting, by each identified PFE node, the RF compatible network data to the RF for determination of a rate for corresponding network service. Moreover, the method includes receiving, by each identified PFE node in response to the transmission of the RF compatible network data, the rate for the corresponding network service from the RF.

[0017]

[0012] In some aspects of the present disclosure, the communication network comprises a plurality of Rating Functions comprising the Rating Function. The load balancer configures each rating Function of the plurality of Rating Functions to perform for managing at least one network service of a plurality of network services in the communication network.

[0013] In some aspects of the present disclosure, the one or more network interfaces comprise a Ro interface, an Sy interface, a Gy interface, and a radius interface, corresponding to the 5thGeneration (5G) telecommunication standards.

[0018]

[0014] According to another embodiment of the present disclosure, a system to manage one or more network services using a Rating Function (RF) in a communication network is provided. The system includes a load balancer and a plurality of Platform Front End (PFE) nodes. The load balancer is configured to receive using a first transceiver module one or more network inputs corresponding to the one or more network services from one or more network interfaces in the communication network. Moreover, the load balancer is configured to identify using a first data processing module, for each network input of the one or more network inputs, a Platform Front End (PFE) node from a plurality of PFE nodes in the communication network. Each identified PFE node is configured to parse using a second data processing module a corresponding network input to generate network data in a format compatible with the RF. The network data enables the RF to manage the one or more network services.

[0019]

[0015] According to yet another embodiment of the present disclosure, a computerprogram product for managing one or more network services for a Rating Function (RF) in a communication network is provided. The computer program product comprises computer-executable instructions that are stored on a non-transitory computer-readable medium and that, when executed by at least one processor performs operations. The operations include receiving by a load balancer from one or more network interfaces in the communication network, one or more network inputs corresponding to the one or more network services. The operations further include identifying, for each network input of the one or more network inputs, a Platform Front End (PFE) node from a plurality of PFE nodes in the communication network. Furthermore, the operations include parsing, by each identified PFE node, a corresponding network input to generate network data in a format compatible with the RF. The network data enables the RF to manage the one or more network services.

[0020] BRIEF DESCRIPTION OF DRAWINGS

[0021]

[0016] Various embodiments disclosed herein will become better understood from the following detailed description when read with the accompanying drawings. The accompanying drawings constitute a part of the present disclosure and illustrate certain non-limiting embodiments of inventive concepts disclosed herein. Further, components and elements shown in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. For the purpose of consistency and ease of understanding, similar components and elements are annotated by reference numerals in the exemplary drawings.

[0022]

[0017] FIG. 1 is a block diagram illustrating exemplary components of a communication network, in accordance with an embodiment of the present disclosure.

[0023]

[0018] FIG. 2 is a block diagram depicting an Online Charging System (OCS) architecture in the communication network, in accordance with an embodiment of the present disclosure.

[0024]

[0019] FIG 3 is a block diagram of a system to manage network services using Rating Function in the communication network, in accordance with an exemplary embodiment of the present disclosure.

[0025]

[0020] FIG. 4(A) and 4(B) present block diagrams depicting operational architectures of components of the system, in accordance with exemplary embodiments of the present disclosure.

[0021] FIG. 5 illustrates a flow chart that depicts a method for managing the network services using the Rating Function in the communication network, in accordance with an embodiment of the present disclosure.

[0026]

[0022] FIG. 6 illustrates a block diagram depicting operational entities in the components of the system, in accordance with an embodiment of the present disclosure.

[0027] LIST OF REFERENCE NUMERALS

[0028]

[0023] The following list is provided for convenience and in support of the drawing figures and as part of the text of the specification, which describe innovations by reference to multiple items. Items not listed here may nonetheless be part of a given embodiment. For better legibility of the text, a given reference number is recited near some, but not all, recitations of the referenced item in the text. The same reference number may be used with reference to different examples or different instances of a given item. The list of reference numerals is as follows:

[0029] 100 - Communication network

[0030] 102 - Core network

[0031] 104 - Nodes

[0032] 106 - Devices

[0033] 200 - Online Charging System (OCS) Architecture

[0034] 202 - IMS CSCF

[0035] 204 - Network Functions

[0036] 206 - ISC

[0037] 208 - Online Changing System

[0038] 210 - First Set of Interfaces

[0039] 212 - Support Servers

[0040] 212a - Recharging Server

[0041] 212b - Operator’s Post-processing System (OPS)

[0042] 212c - Policy and Charging Rules Function (PCRF) 214 - Third Set of Interfaces

[0043] 216 - Online Charging Function

[0044] 218 - Second Set of Interfaces

[0045] 220 - Account Balance Management Function

[0046] 222 - Charging Gateway Function

[0047] 224 - Rating Function (RF) Node

[0048] 300 - System to Manage Network Interfaces using the RF node

[0049] 301 - Subsystem

[0050] 302 - Network Function

[0051] 304 - Task Load Balancer (Load Balancer)

[0052] 306 - Platform Front End (PFE) Nodes

[0053] 308 - Instructions Repository

[0054] 400-1 - First Operational Architecture

[0055] 400-2 - Second Operational Architecture

[0056] 500 - Method for Managing the Network Services in the Communication Network

[0057] 502-512 - Operational blocks of the method 500

[0058] 600 - Operational Entities

[0059] 602 - Processor

[0060] 604 - Memory

[0061] 606 - Transceiver

[0062] 608 - Communication Bus

[0063] 610 - Transceiver Modules

[0064] 612 - Data Processing Modules

[0065] DETAILED DESCRIPTION OF THE INVENTION

[0066]

[0024] Inventive concepts of the present disclosure will now be described more fully hereinafter with reference to the accompanying drawings, in which examples of one or more embodiments of inventive concepts are shown. Inventive concepts may, however, be embodied in different forms and should not be construed as limited to the embodiments set forth herein. Further, the one or more embodiments disclosed herein are provided to describe the inventive concept thoroughly and completely, and to fully convey the scope of each of the present inventive concepts to those skilled in the art. Furthermore, it should be noted that the embodiments disclosed herein are not mutually exclusive concepts. Accordingly, one or more components from one embodiment may be tacitly assumed to be present or used in any other embodiment.

[0067]

[0025] The following description presents various embodiments of the present disclosure. The embodiments disclosed herein are presented as teaching examples and are not to be construed as limiting the scope of the present disclosure. The present disclosure should in no way be limited to the illustrative implementations, drawings, and techniques illustrated below, including the exemplary design and implementation illustrated and described herein, but may be modified, omitted, or expanded upon without departing from the scope of the present disclosure.

[0068]

[0026] The following description contains specific information pertaining to embodiments in the present disclosure. The detailed description uses the phrases “in some embodiments” which may each refer to one or more or all of the same or different embodiments. The term “some” as used herein is defined as “one, or more than one, or all.” Accordingly, the terms “one,” “more than one,” “more than one, but not all” or “all” would all fall under the definition of “some.” In view of the same, the terms, for example, “in an embodiment” refers to one embodiment and the term, for example, “in one or more embodiments” refers to “at least one embodiment, or more than one embodiment, or all embodiments.”

[0069]

[0027] The term “comprising,” when utilized, means “including, but not necessarily limited to;” it specifically indicates open-ended inclusion in the so- described one or more listed features, elements in a combination, unless otherwise stated with limiting language. Furthermore, to the extent that the terms “includes,” “has,” “have,” “contains,” and other similar words are used in either the detailed description, such terms are intended to be inclusive in a manner similar to the term “comprising.”

[0070]

[0028] In the following description, for the purposes of explanation, various specific details are set forth to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter can each be used independently of one another or with any combination of other features.

[0071]

[0029] The description provided herein discloses exemplary embodiments only and is not intended to limit the scope, applicability, or configuration of the present disclosure. Rather, the foregoing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing any of the exemplary embodiments. Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it may be understood by one of the ordinary skilled in the art that the embodiments disclosed herein may be practiced without these specific details.

[0072]

[0030] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used herein the description, the singular forms "a", "an", and "the" include plural forms unless the context of the invention indicates otherwise.

[0073]

[0031] The terminology and structure employed herein are for describing, teaching, and illuminating some embodiments and their specific features and elements and do not limit, restrict, or reduce the scope of the present disclosure. Accordingly, unless otherwise defined, all terms, and especially any technical and / or scientific terms, used herein may be taken to have the same meaning as commonly understood by one having ordinary skill in the art.

[0032] Efficient and accurate billing of services is critical for network service providers. This process typically involves complex interaction between various subsystems including the Online Charging Function (OCF) node and the Rating Function (RF) node. These components play a key role in determining the cost associated with specific communication events, such as voice data, and messaging services. A common challenge in this domain is the need to parse and interpret unstructured data received from the network via Diameter interfaces. This data must be meticulously processed to extract relevant information about the services and the subscriber, which is then used by the RF node to apply appropriate pricing rules. However, the current approach of parsing the data is computationally intensive and costly, often leading to in efficiencies in the rating process.

[0074]

[0033] Various aspects of the present disclosure relate to managing network services using Rating Function(s) in a communication network. Some aspects of the present disclosure provide a system and a method for standardizing data for accurate and efficient billing (or rating) of the network services efficiently in the communication network. In some aspects of the present disclosure, the system utilizes a Platform Front End (PFE) to standardize the data into a structured format for the RF node to determine rates (e.g., tariff) for the network services based on a set of predefined rules.

[0075]

[0034] Embodiments of the present disclosure will be described below in detail with reference to the accompanying drawings. FIG. 1 through FIG. 5, discussed below, and the one or more embodiments used to describe the principles of the present disclosure are by way of illustration only and should not be construed in any way to limit the scope of the present disclosure. Those skilled in the art will understand that the principles of the present disclosure may be implemented in any suitably arranged system or device.

[0076]

[0035] FIG. 1 is a block diagram illustrating exemplary components of a communication network 100, in accordance with an embodiment of the present disclosure. The communication network 100 includes a core network 102. The core network 102 (hereinafter interchangeably referred to and designated as ‘network 102’) may be coupled with a plurality of Base Stations (BS) or a plurality of nodes including Node 104-1 through Node 104-N and is configured to facilitate a secured communication among the plurality of nodes (collectively referred to as the “Nodes 104”, and individually referred to as the “Node 104”, hereinafter). The communication network 100 further includes a server (not shown) connected to the core network 102. The server is configured to execute data processing and data storing operations to optimize the network coverage in the communication network 100.

[0077]

[0036] In an embodiment, each of the nodes are configured to be coupled with one or more user devices 106-1, 106-2, 106-3, 106-4, through 106-(N-l), 106-N (collectively referred to as the “user devices 106”, and individually referred to as the “user device 106”, hereinafter). In one aspect, the core network 102 may establish a secured communication between the one or more user devices 106 associated with the plurality of nodes 104. In another aspect, the core network 102 may establish a secured communication between the one or more user devices 106 associated with the same node 104.

[0078]

[0037] In an exemplary embodiment, the core network 102 may effectively establish a secured communication between the user device 106-1 and the user device 106-2, where the user device 106-1 and the user device 106-2 both are coupled with the Node 104-1. In another embodiment, the core network 102 may establish a secured communication between the user device 106-2 and the user device 106-N with equal effectiveness, where the user device 106-2 is coupled with the Node 104-1 and the user device 106-N is coupled with the Node 104-N.

[0079]

[0038] In an exemplary embodiment, the core network 102 (also, referred to as network 102, herein) may be configured as an application server and may be communicably operational or may be integrated with a user device 106 via a network coupled with a server. The core network 102 may pertain to 5thGeneration (5G) service-based architecture and may be configured to interconnect distinct networks associated with the architecture. Therefore, the core network 102 may provide a path for the exchange of information between one or more of the networks, and corresponding subnetworks.

[0080]

[0039] Although FIG. 1 illustrates one example of the communication network 100, various changes may be made to FIG. 1. For example, the communication network 100 may include any number of nodes and user devices 106 in any suitable arrangement, without deviating from the scope of the present disclosure. Further, various components in FIG. 1 may be combined, further subdivided, or omitted and additional components may be added according to particular needs.

[0081]

[0040] FIG. 2 is a block diagram that depicts an Online Charging System (OCS) architecture 200, in accordance with an embodiment of the present disclosure. In some aspects of the present disclosure, the OCS architecture 200 (hereinafter interchangeably referred to as ‘architecture 200’) may include some (or all) of the components of the core network 102. The architecture 200 may include an Internet protocol Multimedia Subsystem Call Session Control Function (IMS-CSCF) 202 coupled to a first set of network elements 204 by an IMS Service Control (ISC) 206. Examples of the first set of network elements 204 may include a Mobile Switching Center (MSC), Serving General Packet Radio System Support Node (SGSN), proxy function, Traffic Detection Function (TDF), etc. as presented in FIG. 2. The first set of network elements comprises network functions corresponding to various network services provided by a service provider associated with the architecture 200.

[0082]

[0041] In some aspects of the present disclosure, the network services associated with the architecture 200 may correspond to operational functionality of the network elements 204. For example, the network services may include, but are not limited to, voice calling network services and Short Messaging Service(s) (SMS) (e.g., through input(s) including credit-control-request and credit-control-answer) corresponding to Ro interface, subscriber policy counter status (identification and alteration) services and advertising application services (e.g., through input(s) including command code values, spending limit request command, spending limit answer command, spending-status-notification requests, spending-status- notification answer command, and session-termination-request command) corresponding to Sy interface, broadband and / or optical fiber network service(s) corresponding to radius interface, network service(s) related to immediate account debit, event based account debit with reservations, session based account debit with reservations, account refund, account balance query, etc. corresponding to Rc interface, network service(s) related to external account recharging corresponding to Rr interface, network service(s) related to determination of a price for a given event or service (e.g., one-time or recurrent charges) corresponding to the Re interface, network service(s) related to service providing operator's post-processing operations corresponding to Bo interface, and online data and multimedia services (e.g., through input(s) related to collection and transfer of charging information from Online Charging Function (OCF) 216 to the Charging Gateway Function (CGF) 222) corresponding to Gy interface in the 5thGeneration (5G) communication network. Aspects of the present disclosure are intended to include or otherwise cover any service associated with the functionality of the network elements 204 as ‘the network services’ without deviating from the scope of the present disclosure.

[0083]

[0042] The OCS 208 may be coupled to the ISC 206 by way of a first set of interfaces 210. Examples of interfaces in the first set of interfaces 210 may include, but are not limited to, CAMEL Application Part (CAP) interface, and the Ro interface. The OCS 208 may include networking components configured to determine parameters associated with network services consumed by a user (i.e., a user account) in the communication network. The OCS 208 may include an Online Charging Function (OCF) 216 to determine a set of communication parameters associated with the network service(s) rendered to the user account. Preferably, the OCF 216 may include a Session based Charging Function (SCF) 216a and an Event based Charging Function (ECF) 216b. The SCF 216a may be configured to determine communication parameters associated with session(s) of the network service(s) rendered to the user account. For example, when data is communicated in a session, the SCF 216a may determine a duration of data communication in the session, a size of data communicated in the session, whether the session includes any special conditions (such as data roaming), etc.

[0084]

[0043] The ECF 216b may be configured to determine communication parameters associated with events of network service(s) rendered to the user account. For example, when a text message is communicated, the ECF 216b may determine a size of text message, location of a recipient of the text message, etc. The OCS 208 may further include Account Balance Management Function (ABMF) 220, a Charging Gateway function (CGF) 222, and a Rating Function (RF) 224 (hereinafter interchangeably referred to as ‘RF node 224’ or ‘RF pod 224’ or ‘RF 224’). The ABMF 220, the CGF 222, and the RF node 224 may be coupled with the OCF 216 by a second set of interfaces 218. Preferably, the ABMF 220 may be coupled to the OCF 216 using Rc interface and the RF node 224 may be coupled to the OCF 216 using Re interface. Similarly, the CGF 222 may be coupled to the OCF 216 using Ga interface.

[0085]

[0044] The ABMF 220 may be configured to determine and maintain account(s) corresponding to a session and / or an event associated with the network service. The RF node 224 may be configured to generate rate information (e.g., tariff) for each network service using the predefined network rules. Particularly, the RF node 224 may have a data model customized for the network services opted for the user account. The data model may include strategies for rating and protocols for execution the strategies for the network service(s) opted by the user account. The CGF 222 may be configured to support the RF node 224 by managing policies for determination of rate (e.g., tariff) for each network service associated with user account.

[0045] Furthermore, the OCS 208 may be coupled to support servers 212 by a third set of interfaces 214. The support servers 212 may include a Recharging Server (RS) 212a, an Operator’s Post-processing System (OPS) 212b, and the Policy and Charging Rules Function (PCRF) 212c. The RS 212a may be configured to manage account balance details and recharge(s) details corresponding to the user account. The OPS 212b may be configured to perform post-processing operation(s) for management of rating policies (e.g., tariff policies) for the service provider. The PCRF 212c may be configured to manage policies for e.g., rating rules (tariff rules) generated by the RF node 224 based on the user selected services. Moreover, the PCRF 212c may be configured to manage rate(s) corresponding to various network services that can be accessed by the user account.

[0086]

[0046] The third set of interfaces 214 may include Rr interface, Bo interface, and Sy interface. Particularly, the ABMF 220 may be coupled with the RS 212a using the Rr interface, the CGF 222 may be coupled to the OPS 212b using the Bo interface and the RF node 224 may be coupled to the PCRF 212c using the Sy interface. Preferably, the first set of interfaces 210, the second set of interfaces 218, and the third set of interfaces 214 are network interfaces related to the 5G telecom network. It will be apparent to a person of ordinary skill in the art that the first through third sets of interfaces are standard network interfaces and are segregated based on their appearance in the architecture 200.

[0087]

[0047] Although FIG. 2 illustrates one example of the architecture 200, various changes may be made to FIG. 2. For example, the architecture 200 may include any number of components of similar functionality as of those presented in FIG. 2 in any suitable arrangement, without deviating from the scope of the present disclosure. Further, various components of the architecture 200 as presented in FIG. 2 may be combined, further subdivided, or omitted and additional components may be added according to specific needs or technical advancements in upcoming telecom standards.

[0048] FIG. 3 is a block diagram of a system 300 to manage the network interfaces (cumulatively referring to the first set of interfaces 210, the second set of interfaces 218, and the third set of interfaces 214) using the RF node 224 in the communication network 100, in accordance with an exemplary embodiment of the present disclosure. The system 300 may include a Network Function (NF) 302 (hereinafter interchangeably referred to and designated as ‘Converged Telephony Application Server (CTAS) 302’), a Load Balancer (LB) 304, multiple Platform Front End (PFE) nodes 306 (interchangeably referred to as ‘PFE servers 306’), an instructions repository 308, and the RF node 224.

[0088]

[0049] The NF 302 may be configured to collect network input(s) corresponding to network service(s) in the communication network 100. Each network input for a network service may be collected in a specific format and through a specific type of network interface. For example, the network services may include, but are not limited to voice calling network services and Short Messaging Service(s) (SMS) (e.g., through input(s) including credit-control-request and credit-control-answer) corresponding to the Ro interface, subscriber policy counter status (identification and alteration) services and advertising application services (e.g., through input(s) including command code values, spending limit request command, spending limit answer command, spending-status-notification requests, spending-status- notification answer command, and session-termination-request command) corresponding to the Sy interface, broadband and / or optical fiber network service(s) corresponding to radius interface, network service(s) related to immediate account debit, event based account debit with reservations, session based account debit with reservations, account refund, account balance query, etc. corresponding to the Rc interface, network service(s) related to external account recharging corresponding to the Rr interface, network service(s) related to determination of a price for a given event or service (e.g., one-time or recurrent charges) corresponding to the Re interface, network service(s) related to service providing operator's post-processing operations corresponding to the Bo interface, and online data and multimedia services (e.g., through input(s) related to collection and transfer of charging information from Online Charging Function (OCF) 216 to the Charging Gateway Function (CGF) 222) corresponding to the Gy interface. Aspects of the present disclosure are intended to include or otherwise cover any type of service associated with rating (or charging) of a user account the communication network 100, without deviating from the scope of the present disclosure.

[0089]

[0050] The NF 302 may further be configured to send a network input(s) to the LB 304. In some aspects of the present disclosure, the network input(s) may be operational input that may correspond to utilization of network service(s) from several network services rendered by the communication network 100. Specifically, the network input(s) may correspond to utilization of network service(s) by user account(s) registered with the communication network 100.

[0090]

[0051] The LB 304 may be configured to retrieve the network input(s) from the NF 302 and extract information from each of network input(s). The information may be related to a user account corresponding to the network input, a network service corresponding to the network input, a type of network service, a network interface rendering the network input to the NF 302, a type of the network interface, etc. Particularly, each network input includes a service identifier (ID) associated with a corresponding network service. The LB 304 may be configured to determine a service type for the network service (or corresponding network interface) based on the service ID retrieved from the network input. The LB 304 may further be configured to identify a PFE node 306 from the multiple PFE nodes 306 for each network input based on the service ID (or the service type). Each PFE node 306 is dedicatedly configured for a specific service type (i.e., customized to operate for a particular type of input corresponding to a specific network service and / or a specific network interface). The LB 304 may determine one PFE node 306 suitable for each network input from the multiple PFE nodes 306 in the system 300. Thereafter, the LB 304 may send the network input(s) to their corresponding PFE nodes 306.

[0052] Each PFE node 306 may be configured as a network node (or a server implementation) that defines the rules and format for communication between a network interface (front-end) and the Rating Function node 224 (back-end). Each PFE node 306 essentially establishes how the front-end and back-end interact, including the messages they exchange, the data formats they use, and the actions they perform to ensure seamless and reliable communication between the networkfacing part (i.e., front-end) of an application and its underlying logic and data (i.e., back-end). Particularly, each PFE node 306 may be configured to receive a specific type of network input (corresponding to a specific type of network service or a specific type of network interface) from the LB 304. Moreover, each PFE node 306 may be configured to parse the network input to generate network data in a format compatible with the RF 224. The network data enables the RF to manage the network service(s) associated with the corresponding network input. Preferably, each PFE node 306 may be equipped with a data transformer (i.e., transformation function block) configured to transform the network input to generate network data in the format compatible with the RF 224 using a transformation function. In some aspects of the present disclosure the transformation function may be dependent on the format compatible by the RF 224 and a format of the corresponding network input. In simpler words, each PFE node 306 may be configured to transform (or standardize) the network input to the format compatible with the RF 224. In some aspects of the present disclosure, the network input may be received in an encrypted format specific to the corresponding network interface. Each PFE node 306 identified for each network input may be configured to decrypt the corresponding network input to a standard format (i.e., network data in a diameter charging format) compatible with the RF 224. Thereafter, each PFE node 306 may be configured to send the network data to the RF 224 for further operations.

[0091]

[0053] The RF 224 may be configured to receive the RF compatible network data from each PFE node 306 corresponding to the network input and determine a rate of the network service associated with the network data (i.e., the transformed network input) using a set of predefined rating protocols (or rules). The RF 224 may be configured as a logical element within the Online Charging System (OCS) 208 responsible for determining a rate at which a user's credit should be decremented / provided for service usage. The RF 224 essentially calculates the cost of a service based on various factors and parameters before, during, or after service delivery.

[0092]

[0054] Particularly, the RF 224 may be configured to determine a rate for the network service for the network input through processing of the network data using the predefined rating protocols. The rate for the network input (corresponding to the network service utilized by the user account) may be associated with a variety of operations of the RF 224. For example, the rate of the network service may be associated with identification of networking service(s) associated with the network input, tariff of the network service(s) associated with the network input, information of events associated with the network input (for example, in case of a telephonic communication event, information of a caller, receiver, duration of call, plan opted by the calling account, plan opted by the receiving account, etc.). In some aspects of the present disclosure, the RF 224 may include a rule engine (not shown) configured to apply rule(s) (e.g., through templates of rating plans opted by the user account corresponding to the network input) on the network data received for a network input to enable the RF 224 determine the rate for the network input. The RF 224 may further be configured to share the rate to the PFE node(s) 306 corresponding to each network input, to be shared back to the NF 302 via the LB 304. The NF 302 may further notify each user account about the rate corresponding to the network input.

[0093]

[0055] The system 300 further includes an instructions repository 308 configured to store computer program instructions and / or codes for operation(s) of various components of the system 300. For example, the instructions repository 308 may be configured to store computer program instructions corresponding to the operation(s) performed by the various components of the system 300 for managing the network services using the RF 224 in the communication network, as presented above. In an embodiment of the present disclosure, the instructions repository 308 may be configured as a non-transitory storage medium. Examples of the instructions repository 308 configured as the non-transitory storage medium includes hard drives, solid-state drives, flash drives, Compact Disk (CD), Digital Video Disk (DVD), and the like. Aspects of the present disclosure are intended to include or otherwise cover any type of non-transitory storage medium as the instructions repository 308, without deviating from the scope of the present disclosure. As will be appreciated, any such computer program instructions stored in the instructions repository 308 may be executed by one or more computer processors, including without limitation a general -purpose computer or special purpose computer, or other programmable processing apparatus to produce a machine, such that the computer program instructions which execute on the computer processor(s) or other programmable processing apparatus create means for implementing the function(s) specified.

[0094]

[0056] Although FIG. 3 illustrates one example of the system 300, various changes may be made to FIG. 3. For example, the system 300 may include multiple load balancer (LB) pods 304 communicating with multiple PFE pods 306 (as presented later in FIG. 4(A) or multiple PFE pods 306 communicating with multiple RF pods 224 (as presented later in FIG. 4(A), or any suitable arrangement, without deviating from the scope of the present disclosure. Further, various components of the system 300 in FIG. 3 may be combined, further subdivided, or omitted and additional components may be added according to particular needs.

[0095]

[0057] FIG. 4(A) and 4(B) present block diagrams depicting operational architectures 400 (i.e., first operational architecture 400-1 and second operational architecture 400-2) of the components of the system 300, in accordance with exemplary embodiments of the present disclosure.

[0096]

[0058] Particularly, FIG. 4(A) presents the first operational architecture 400-1 illustrating interactions between multiple Load Balancer (LB) pods 304 and multiple PFE pods 306, in accordance with an embodiment of the present disclosure. The first operational architecture 400-1 is opted for the system 300 to manage interactions between the LB pods 304 and PFE pods 306 in the system 300 by dividing the traffic (or communication interactions) between them to enhance the throughput of the system 300 and reduce the operational latency. For example, the communication interaction between the LB pods 304 and the PFE pods 306 is logically designed in such a way that each LB pod 304 receives the network input of a specific count of user accounts (e.g., each LB pod receives network input of 1000 user accounts) and similarly, each PFE pod 306 is logically designed to transform the network input to RF compatible network data for a specific count of network input (i.e., corresponding to specific count of user accounts) (e.g., each PFE pod is configured to transform 1000 network inputs to corresponding RF compatible network data).

[0097]

[0059] In simpler words, in an exemplary scenario, the system 300 may include two LB pods 304 and two PFE pods 306 communicatively coupled to each other. Each of the LB pod 304 may be configured to receive different sets of network input(s) from the NF 302, comprising network inputs of different user accounts. Moreover, each PFE pod 306 may be configured to transform the network input into the network data. Such an architecture of the system helps in parallel processing of network data (or network inputs) and helps reducing the computational latency. Moreover, each LB pod 304 and each PFE pod 306 may comprise multiple processing engines (in active / standby state). In an aspect of the present disclosure, one processing engine in the pod (referring to the LB pods 304 and the PFE pods 306) may be configured as a primary engine to perform operation(s) as configured, and other processing engine(s) in the pod may be configured as secondary engines that provide back-up (or standby) processing capabilities to the pod when a fault is detected in the primary engine.

[0098]

[0060] As will be apparent to a person of ordinary skill in the art, FIG. 4(A) presents two LB pods 304 (i.e., first LB pod 304-1 and second LB pod 304-2) and two PFE pods 306 (i.e., first PFE pod 306-1 and second PFE pod 306-2) in the first operational architecture 400-1 of the components of the system 300 for illustration only, and the scope of the disclosure is not limited to it. Aspects of the present disclosure are intended to include or otherwise cover embodiments of the first operational architecture 400-1 comprising any number of PFE pods 306 and any number of LB pods 304, without deviating from the scope of the present disclosure.

[0099]

[0061] Particularly, FIG. 4(B) presents the second operational architecture 400-2 illustrating interactions between multiple PFE pods 306 and multiple RE pods 224, in accordance with an embodiment of the present disclosure. The second operational architecture 400-2 is opted by the system 300 to manage interactions between the PFE pods 306 and RE pods 224 in the system 300 by dividing the traffic (or communication interactions) between them to enhance the throughput of the system 300 and reduce the operational latency. For example, the communication interaction between the PFE pods 306 and the RE pods 224 is logically designed in such a way that each PFE pod 306 receives the network input of a specific count of user accounts (e.g., each PFE pod 306 receives network input of 1000 user accounts) and similarly, each RE pod 224 is logically designed to perform rating of network services for a specific count of network data (corresponding to specific count of user accounts) (e.g., each RE pod 224 is configured to determine the rate of 1000 network data corresponding to 1000 user accounts).

[0100]

[0062] In simpler words, in an exemplary scenario, the system 300 may include two PFE pods 306 and two RF pods 224 communicatively coupled to each other. Each of the PFE pod 306 may be configured to receive different sets of network input(s) from the LB 304, comprising network inputs of different user accounts. Moreover, each PFE pod 306 may be configured to transform the network input into the network data and share it with one of the RF pods 224 i.e., pre-aligned with the PFE pod 224. Such an architecture 400-2 of the system 300 helps in parallel processing of network data (or network inputs) and helps reducing the computational latency. Moreover, each PFE pod 306 and each RF pod 224 may comprise multiple processing engines (in active state). In an aspect of the present disclosure, one processing engine in the pod (referring to the RF pods 224 and the PFE pods 306) may be configured as a primary engine to perform operation(s) as configured, and other processing engine(s) in the pod may be configured as secondary engines, that provide back-up processing capabilities to the pod when a fault is detected in the primary engine.

[0101]

[0063] As will be apparent to a person of ordinary skill in the art, FIG. 4(B) presents two PFE pods 306 (i.e., first PFE pod 306-1 and second PFE pod 306-2) and two RF pods 224 (i.e., first RF pod 224-1 and second RF pod 224-2) in the second operational architecture 400-2 of the components of the system 300 for illustration only, and the scope of the disclosure is not limited to it. Aspects of the present disclosure are intended to include or otherwise cover embodiments of the second operational architecture 400-2 comprising any number of PFE pods 306 and any number of RF pods 224, without deviating from the scope of the present disclosure.

[0102] FIG. 5 illustrates a flow chart that depicts a method 500 for managing the network services using the Rating Function 224 in the communication network 100, in accordance with an embodiment of the present disclosure. The method 500 depicts operations performed by various entities of the system 300 for managing the network services in the communication network 100 by way of blocks 502 through 512.

[0103]

[0064] At block 502, the LB 304 may receive network input(s) corresponding to the network services from corresponding network interfaces in the communication network 100. Each network input comprises a service ID associated with corresponding network service utilized (or opted) by the user account in the communication network 100.

[0104]

[0065] At block 504, the LB 304 identifies a PFE node 306 for each network input. In some aspects of the present disclosure, the PFE node 306 is identified from the multiple PFE nodes 306 in the communication network 100 based on the service ID. Specifically, the service ID is associated with network service(s) and / or network interface(s) corresponding to the network input. The LB 304 may determine the type of network interface (or the type of network service) corresponding to the network input and identify a format of the network input. Thereafter, the LB 304 may identify a PFE node 306 configured to transform the network input of the identified format to the RF compatible network data (i.e., RF compatible standard format).

[0105]

[0066] At block 506, each identified PFE node 306 may receive the corresponding network data from LB 304 and parse the network data to generate the network data in the format compatible with the RF 224. The network data enables the RF to manage the network service(s) associated with the network input. In some aspects of the present disclosure, each identified PFE node 306 may utilize a transformation function specific to the type of network interface for parsing the network input and generating the network data. Specifically, the network input may be received in an encrypted format that is decrypted by the corresponding PFE node 306 using the transformation function.

[0106]

[0067] At block 508, each identified PFE node 306 may transmit the RF compatible network data to the RF 224 for determination of the rate for corresponding network service. The RF 224 may utilize a set of predefined rating protocols (i.e., utilizing rules of rating engines) to determine the rate of each network service. In some aspects of the present disclosure, the rate of the network service may be indicative of the tariff (for charging the user account) for the network service(s).

[0107]

[0068] At block 510, the PFE nodes 306 may receive the rates of the network service(s) from the RF 224. Moreover, the PFE nodes 306 may render the rates of the network service(s) to the NF 302 through the LB 304.

[0069] At block 512, the NF 302 may generate notification(s) for network service(s) comprising the rate(s) and other information (e.g., account identifiers, opted plans, etc.) and render the notification(s) to respective user accounts.

[0108]

[0070] FIG. 6 illustrates a block diagram depicting operational entities 600 in the components of the system 300, in accordance with an embodiment of the present disclosure. Particularly, the operational entities 600 may be utilized for implementation of the components of the system 300 such as, but not limited to, the LB 304, the PFE(s) 306, and the RF(s) 224. The operational entities 600 may include a processor 602, a memory 604, a transceiver 606, transceiver modules 610, and data processing modules 612, communicatively coupled through a communication bus 608.

[0109]

[0071] The processor 602 may include processing circuitry, logic, interface(s), and / or code(s), that enable the component of the system 300 to execute data processing operation(s) (e.g., generation, modification, execution, etc.) pertaining to a corresponding functionality of the component, as is mentioned above. The processor 602 may include one or a plurality of processors, including a general- purpose processor, such as, for example, and without limitation, a Central Processing Unit (CPU), an Application Processor (AP), a dedicated processor, a graphics-only processing unit such as a Graphics Processing Unit (GPU) or the like, a programmable logic device, or any combination thereof.

[0110]

[0072] According to an exemplary embodiment, the transceiver modules 610 and the data processing modules 612 (cumulatively referred to as ‘the modules’) may be implemented as a combination of hardware and software programming (for example, programmable instructions) to implement operations of the component through the processor 602 and / or the transceiver 606. In non-limiting examples, described herein, such combinations of hardware and software programming may be implemented in several different ways, without deviating from the scope of the present disclosure. Each module of the modules (i.e., the transceiver modules 610 and the data processing modules 612) may include suitable logic, circuitry, interfaces, and / or codes. The programming for the modules may be performed through processor-executable instructions stored in the memory 604 (e.g., a non- transitory machine-readable storage medium) and a hardware for the modules may comprise a processing resource (for example, the processor 602), to execute such instructions. Preferably, the first transceiver module 610-1 may enable the transceiver 606 for transmission and / or reception of data and / or instructions for the LB 304, the second transceiver module 610-2 may enable the transceiver 606 for transmission and / or reception of data and / or instructions for the PFE node 306, and the third transceiver module 610-3 may enable the transceiver 606 for transmission and / or reception of data and / or instructions for the RF node 224. Similarly, the first data processing module 612-1 may enable the processor 602 for processing operations pertaining to the LB 304, the second data processing module 612-2 enable the processor 602 for processing operations pertaining to the PFE node 306, and the third data processing module 612-3 may enable the processor 602 for processing operations pertaining to the RF node 224, as presented in FIG. 3 through FIG. 5 above. In an embodiment of the present disclosure, the modules for a single component (i.e., the LB 304, the PFE node 306, and the RF node 224) may be combined to a single module or each module of the modules may be further subdivided into different modules.

[0111]

[0073] The memory 604 may be configured to store data and / or instruction(s) required by the processor 602 for execution of processing operations of the component it is deployed in. A part of the memory 604 may include a Random Access Memory (RAM), a cache memory, or a Read Only Memory (ROM). The memory 604 may include non-volatile storage elements. Examples of such nonvolatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. In addition, the memory 604 may, in some examples, be considered a non-transitory storage medium. The "non-transitory" storage medium is not embodied in a carrier wave or a propagated signal. However, the term "non-transitory" should not be interpreted T1 as the memory 604 is non-movable. In some examples, the memory 604 may be configured to store larger amounts of information. In certain examples, a non- transitory storage medium may store data that can, over time, change (e.g., in RAM or cache). The memory 604 may be an internal storage unit or an external storage unit of the component of the system 300 it is deployed in, cloud storage, or any other type of external storage. Aspects of the present disclosure are intended to include or otherwise cover any data storage medium as ‘the memory 604’, without deviating from the scope of the present disclosure.

[0112]

[0074] The transceiver 606 may include interface(s), logic, circuitry, and / or codes to enable communication between the component it is deployed in with the other components of the system 300. Examples of the transceiver 606 may include, but are not limited to, a Modulator-Demodulator (MODEM), a network interface such as an Ethernet card, a communication port, and / or a Personal Computer Memory Card International Association (PCMCIA) slot and card, an antenna, a radio frequency (RF) transceiver, amplifier(s), a tuner, oscillator(s), a digital signal processor, a Coder-Decoder (CODEC) chipset, a Subscriber Identity Module (SIM) card, and a local buffer circuit.

[0113]

[0075] Examples of the communication bus 608 may include, but are not limited to, a Peripheral Component Interconnect (PCI)ZPCI Extended (PCI-X) bus, Small Computer System Interface (SCSI), Universal Serial Bus (USB), and a Front Side Bus (FSB). Aspects of the present disclosure are intended to include or otherwise cover any type of coupling means present or related to later developed technologies, that may be configured to connect the communicatively couple the operational entities 600, without deviating from the scope of the present disclosure.

[0114]

[0076] Although FIG. 6 illustrates exemplary operational entities for deployment of the components (e.g., the LB 304, the PFE node(s) 306, and the RF 224) of the system 300, various changes may be made to FIG. 6. For example, the operational components (e.g., the LB 304, the PFE node(s) 306, and the RF 224) may include any number of components in addition to the components shown in FIG. 6. Further, various components in FIG. 6 may be combined, further subdivided, or omitted, and additional components may be added according to particular needs.

[0115]

[0077] Now, referring to the technical abilities and advantageous effect of the present disclosure, operational advantages that may be provided by one or more embodiments presented by way of the system 300, its components (e.g., the LB 304, PFE node 306, and RF 224, etc.), and the method 500. The system 300 by way of the method 500 provides processing of unstructured (or encrypted) data corresponding to network service(s), converting it a more generic and structured format before transmitting it to the RF node 224, for determination of rate(s) of the network service(s) to be charged to the user account(s). This transformation ensures compatibility with all types of network inputs (or messages) enhancing the universality of the system 300.

[0116]

[0078] A further potential advantage of the embodiments disclosed herein includes the RF node 224 that offers scalability, as it can receive data in a generic and compatible format, thereby reducing the time required for parsing data, thereby improving efficiency. The system 300 enhances the scalability and speed of the PFE node 306 due to its stateless nature, in response to the network information being stored by the Account Balance Management Function (ABMF) (not shown) and the RF node 224. Moreover, standardization of network input(s) corresponding to multiple network services from a variety of network interface to RF compatible network data for determination of the rate of the network service eliminates the need of different RF nodes for each network interface and thus substantially reduces the expenses involved in deployment and maintenance of the Online Charging System.

[0117]

[0079] Moreover, the operational architectures 400-1 and 400-2 of the system enable parallel processing of the data through the PFEs 306 and the RF 224, thereby reducing the computational latency of the system 300. As the present disclosure provides use of a RF for determination of rate(s) of multiple types of network inputs (received through a variety of network interfaces and corresponding to a variety of network services), therefore, such an implementation reduces the cost of deployment effectively. Moreover, due to parallel processing capabilities of the system (presented through the operational architectures), the system 300 provides a highly efficient and fast solution for managing network services in the communication network 100 with low redundancy.

[0118]

[0080] Those skilled in the art will appreciate that the methodology described herein in the present disclosure may be carried out in other specific ways than those set forth herein in the above disclosed embodiments without departing from essential characteristics and features of the present invention. The above-described embodiments are therefore to be construed in all aspects as illustrative and not restrictive.

[0119]

[0081] The drawings and the forgoing description give examples of embodiments. Those skilled in the art will appreciate that one or more of the described elements may well be combined into a single functional element. Alternatively, certain elements may be split into multiple functional elements. Elements from one embodiment may be added to another embodiment. For example, orders of processes described herein may be changed and are not limited to the manner described herein. Any combination of the above features and functionalities may be used in accordance with one or more embodiments.

[0120]

[0082] In the present disclosure, each of the embodiments has been described with reference to numerous specific details which may vary from embodiment to embodiment. The foregoing description of the specific embodiments disclosed herein may reveal the general nature of the embodiments herein that others may, by applying current knowledge, readily modify and / or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications are intended to be comprehended within the meaning of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and is not limited in scope.

Claims

1. We Claim:

1. A method (500) for managing one or more network services using a Rating Function (RF) (224) in a communication network (100), the method (500) comprising: receiving, by a load balancer (304) from one or more network interfaces in the communication network (100), one or more network inputs corresponding to the one or more network services; identifying, for each network input of the one or more network inputs by the load balancer (304), a Platform Front End (PFE) node (306) from a plurality of PFE nodes (306) in the communication network (100); and parsing, by each identified PFE node (306), a corresponding network input to generate network data in a format compatible with the RF (224), wherein the network data enables the RF (224) to manage the one or more network services.

2. The method (500) as claimed in claim 1, wherein each network input comprises a service identifier (ID) associated with a corresponding network service from the one or more network services, wherein the PFE node (306) is identified from the plurality of PFE nodes (306) based on the service ID.

3. The method (500) as claimed in claim 1, wherein for parsing the network input, the method (500) comprises transforming, by the corresponding identified PFE node (306), the network input using a transformation function specific to a type of the network interface.

4. The method (500) as claimed in claim 1, comprising: transmitting, by each identified PFE node (306), the RF (224) compatible network data to the RF (224) for determination of a rate for corresponding network service; and receiving, by each identified PFE node (306) in response to the transmission of the RF (224) compatible network data, the rate for the corresponding network service from the RF (224).

5. The method (500) as claimed in claim 1, wherein the communication network (100) comprises a plurality of Rating Functions comprising the Rating Function (224), wherein the load balancer (304) configures each rating Function of the plurality of Rating Functions for managing at least one network service of a plurality of network services in the communication network (100).

6. The method (500) as claimed in claim 1, wherein the one or more network interfaces comprise a Ro interface, an Sy interface, a Gy interface, and a radius interface, corresponding to 5thGeneration (5G) telecommunication standards.

7. A system (300) to manage one or more network services using a Rating Function (RF) (224) in a communication network (100), the system (300) comprising: a load balancer (304) configured to receive, using a first transceiver module (610-1) from one or more network interfaces in the communication network (100), one or more network inputs corresponding to the one or more network services, and identify, using a first data processing module (612-1) for each network input of the one or more network inputs, a Platform Front End (PFE) node from a plurality of PFE nodes (306) in the communication network (100); and the plurality of PFE nodes (306) communicatively coupled with the load balancer (304), wherein each identified PFE node (306) is configured to parse, using a second data processing module (612-2), a corresponding network input to generate network data in a format compatible with the RF (224), wherein the network data enables the RF (224) to manage the one or more network services.

8. The system (300) as claimed in claim 7, wherein each network input comprises a service identifier (ID) associated with a corresponding network servicefrom the one or more network services, wherein the PFE node (306) is identified from the plurality of PFE node s (306) based on the service ID.

9. The system (300) as claimed in claim 7, wherein to parse the network input, the identified PFE node (306), using the second data processing module (612-2), is configured to transform the corresponding network input using a transformation function specific to a type of the network interface.

10. The system (300) as claimed in claim 7, wherein each identified PFE node (306), using a second transceiver module (610-2), is configured to: transmit the RF (224) compatible network data to the RF (224) for determination of a rate for corresponding network service; and receive, in response to the transmission of the RF (224) compatible network data, the rate for the corresponding network service from the RF (224).

11. The system (300) as claimed in claim 7, wherein the communication network (100) comprises a plurality of Rating Functions comprising the Rating Function (224), wherein the load balancer (304), using the first data processing module (612-1), configures each rating Function of the plurality of Rating Functions for managing at least one network service of a plurality of network services in the communication network (100).

12. The system (300) as claimed in claim 7, wherein the one or more network interfaces comprise a Ro interface, an Sy interface, a Gy interface, and a radius interface, corresponding to 5thGeneration (5G) telecommunication standards.

13. A computer-program product for managing one or more network services for a Rating Function (RF) (224) in a communication network (100), the computerprogram product comprising computer-executable instructions that are stored on a non-transitory computer-readable medium and that, when executed by at least one processor performs operations comprising:receiving, by a load balancer (304) from one or more network interfaces in the communication network (100), one or more network inputs corresponding to the one or more network services; identifying, for each network input of the one or more network inputs, a Platform Front End (PFE) node from a plurality of PFE nodes (306) in the communication network (100); and parsing a corresponding network input to generate network data in a format compatible with the RF (224), wherein the network data enables the RF (224) to manage the one or more network services.

Images