System and method for dynamic comparison of values in business rule engine

Abstract

The present disclosure provides a system(108) and method(500) for enabling inter data source value comparison in a business rule engine(216). The method(500) comprising receiving(502), by a processing engine(208), a message from one of a plurality of network functions, retrieving(504), by the processing engine(208), data associated with the received message from a plurality of data sources. The method(500) comprising analyzing(506), by the processing engine(208), data corresponding to the received message with the data retrieved from the plurality of data sources, evaluating(508), by the processing engine (208), at least one business rule based on a result of the analysis. The method(500) comprising providing(510), by the processing engine(208), at least one policy rule to one of the plurality of network functions based on the at least one evaluated business rule.

Description

SYSTEM AND METHOD FOR DYNAMIC COMPARISON OF VALUES IN BUSINESS RULE ENGINERESERVATION OF RIGHTS

[0001] A portion of the disclosure of this patent document contains material, which is subject to intellectual property rights such as, but are not limited to, copyright, design, trademark, Integrated Circuit (IC) layout design, and / or trade dress protection, belonging to Jio Platforms Limited (JPL) or its affiliates (herein after referred as owner). The owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all rights whatsoever. All rights to such intellectual property are fully reserved by the owner.TECHNICAL FIELD

[0002] The present disclosure relates to wireless cellular communications, and specifically to a system and a method for enabling inter data source value comparison in a business rule engine.DEFINITION

[0003] As used in the present disclosure, the following terms are generally intended to have the meaning as set forth below, except to the extent that the context in which they are used to indicate otherwise.

[0004] The term ‘PCF’ as used herein, refers to a Policy Control Function responsible for providing policy rules to control user plane behavior, such as Quality of Service (QoS), traffic routing, and access control.

[0005] The term ‘PCRF’ as used herein, refers to a Policy and Charging Rules Function that determines policy control decisions and provides charging rules.

[0006] The term ‘AM’ as used herein, refers to an Access Management that manages access to the network, including the functions responsible for authenticating and authorizing users.

[0007] The term ‘ SM’ as used herein, refers to a Session Management that manages user sessions in a network, including the establishment, maintenance, and termination of sessions.

[0008] The term ‘SLC’ as used herein, refers to a Service Level Control that manages and controls the service level agreements (SLAs) for different services within the network.

[0009] The term ‘Gx’ as used herein, refers to a Gx Interface that acts as a reference point between the PCRF and a Policy and Charging Enforcement Function (PCEF) in Long-Term Evolution (LTE) networks used to exchange policy and charging rules.

[0010] The term ‘AMF’ as used herein, refers to an Access and Mobility Management Function to control plane function in 5G networks responsible for access management, mobility management, and connection management.

[0011] The term ‘SMF’ as used herein, refers to a Session Management Function responsible for session establishment, modification, and release, as well as user plane management.

[0012] The term ‘UDR’ as used herein, refers to a Unified Data Repository that stores subscription data, policy data, and other user-related information.

[0013] The term ‘SPR’ as used herein, refers to a Subscriber Profile Repository in LTE networks that stores subscriber profiles and policy data.

[0014] The term ‘OCS’ as used herein, refers to an Online Charging System that performs real-time charging and billing for network services based on usage.

[0015] The term ‘CHF’ as used herein, refers to a Charging Function in the network responsible for charging-related activities, including collecting charging data and interfacing with billing systems.

[0016] The term ‘BSF’ as used herein, refers to a Binding Support Function in the network that supports binding of user sessions to specific policy and charging rules.

[0017] The term ‘AF’ as used herein, refers to an Application Function that provides application-specific information to the PCF to influence policy decisions.

[0018] The term ‘NRF’ as used herein, refers to a Network Repository Function in the network that maintains a repository of available network functions and their capabilities.

[0019] The term ‘DPI’ as used herein, refers to a Deep Packet Inspection, a technology used to inspect the data part (payload) of packets as they pass through an inspection point, allowing detailed analysis and policy enforcement based on content.

[0020] The term ‘PGW’ as used herein, refers to a Packet Gateway in LTE networks that provides connectivity from the UE (User Equipment) to external packet data networks.

[0021] The term ‘NMS’ as used herein, refers to a Network Management System used for managing, monitoring, and maintaining network infrastructure.

[0022] The term ‘PDN’ as used herein, refers to a Packet Data Network that provides data services to users, enabling connectivity to external data networks, including the Internet.

[0023] The term ‘N28 interface’ as used herein, refers to a standardized interface defined by a 3rd Generation Partnership Project (3GPP). According to the 3GPP standards, the N28 interface facilitates communication between the CHF and the PCF / PCRF within the network. It specifically handles the exchange of Charging Data Records (CDRs) and enables the application of charging rules based on realtime usage data, ensuring accurate billing and charging mechanisms for mobile services.

[0024] The term ‘Sy interface’ as used herein, refers to a Sy Diameter Interface. In the 3GPP specifications, the Sy interface is part of the Diameter protocol used for communication between the network functions within the 5G network. Specifically, it supports interactions between various network functions such as the PCRF, CHF, and other entities involved in policy control, charging, and subscriber management. The Sy interface facilitates the exchange of Diameter messages, enabling policy enforcement, charging data collection, and other network operations critical for efficient network management and service delivery.

[0025] The term ‘Nnrf as used herein, refers to a service that allows retrieving a list of NF instances currently registered in the NRF or the NF Profile of a given NF instance.

[0026] The term ‘Nbsf as used herein, refers to a service that is used for the BSF to provide a PDU session binding functionality, which ensures that an AF request for a certain PDU Session reaches the relevant PCF holding the PDU Session information.

[0027] The term ‘N15’ as used herein, refers to a reference point is between the PCF and the AMF in the case of a non-roaming scenario, or the vPCF (Visited PCF) and AMF in case of a roaming scenario.

[0028] The term ‘Rx’ as used herein, refers to a Roaming Exchange that enables communication and data exchange between the Home PCRF (H-PCRF) in the subscriber's home network and the Visited PCRF (V-PCRF) in the network they are currently roaming in. This exchange allows for the enforcement of policy rules related to quality of service (QoS), charging mechanisms, and service entitlements based on real-time conditions and subscriber profiles.

[0029] The term ‘N7’ as used herein, refers to an interface that triggers session management policies towards the SMF. The SMF controls the User plane Function (UPF). It translates policies received from the PCF to a set of directives / information understood to the UPF and then forwards it to the UPF.

[0030] The term ‘Sd’ as used herein, refers to a reference point that is located between the PCRF and the Traffic Detection Function (TDF) / DPI.BACKGROUND

[0031] The following description of related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section be used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art.

[0032] Wireless communication technology has rapidly evolved over the past few decades. The first generation of wireless communication technology was analog technology that offered only voice services. Further, when the second- generation (2G) technology was introduced, text messaging and data services became possible. The 3G technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth generation (4G) technology revolutionized the wireless communication with faster data speeds, improved network coverage, and security. Fifth-generation (5G) and advanced-generation technology are being deployed, with even faster data speeds, low latency, and the ability to connect multiple devices simultaneously.

[0033] As mobile networks continue to grow, users are increasingly concerned about the quality and performance of their network connections. Typically, Policy Control Function (PCF) and Policy and Charging Rules Functions (PCRF) provides Access and mobility management (AM), and Session management (SM) policy rules. The PCF and PCRF receives data from a Session Management Function (SMF) or an Access and Mobility Management Function (AMF) in create / update / terminate operations. In addition, data is received from a Unified Data Repository (UDR) / Subscription Profile Repository (SPR). This data from the SMF / AMF and the UDR / SPR values are checked with values defined in a Business Rule Engine in the PCF and PCRF, based on a specific interface. Based on these evaluations, the AM / SM policy rules are provided to the AMF / SMF. However, currently only static value comparisons can be performed for values received from the AMF / SMF.

[0034] There is therefore a need in the art to provide an improved system and method that provides a flexibility in creation of policy and charging rules for the PCF and PCRF.SUMMARY

[0035] In an exemplary embodiment, a method for enabling inter data source values comparison in a business rule engine. The method comprises receiving, by a processing engine, a message from one of plurality of networkfunctions and retrieving, by the processing engine, data associated with the received message from a plurality of data sources. The method comprises analyzing, by the processing engine, data corresponding to the received message with the data retrieved from the plurality of data sources. The method comprises evaluating, by the processing engine, at least one business rule based on a result of the analysis. The method further comprises providing, by the processing engine, at least one policy rule to one of the plurality of network functions based on the at least one evaluated business rule.

[0036] In some embodiments, the method comprises applying, by the processing engine, the at least one policy rule to one of the plurality of network functions.

[0037] In some embodiments, the method comprises verifying, by the processing engine, the message received from one of the plurality of network functions. The verification is one of a successful verification and a non-successful verification.

[0038] In some embodiments, upon the successful verification, the data corresponding to the received message and the data retrieved from the plurality of data sources is analyzed and upon non-successful verification, sending, by the processing engine, an error response to one of the plurality of network functions.

[0039] In some embodiments, the analyzing comprises comparing, by the processing engine, data corresponding to the received message and the data retrieved from the plurality of data sources.

[0040] In some embodiments, the plurality of data sources includes a session management function (SMF), a charging function (CHF), a binding support function (BSF), a network repository function (NRF), an access management function (AMF), an application function (AF), an online charging system (OCS), a packet data network (PDN), a packet gateway (PGW), a network management system (NMS), a unified data repository (UDR) and a subscription profile repository (SPR).

[0041] In some embodiments, the data of the received message and the data from the plurality of data sources include at least one of tracking area code (TAC) and radio access technology (RAT) type.

[0042] In some embodiments, one of the plurality of network functions comprises an access management (AM), a session management (SM), a Gx interface, and a service-level commitment (SLC), and the received message from one of the plurality of network functions comprises one of a subscriber notification request (SNR), and an authorization authentication request (AAR).

[0043] In another exemplary embodiment, a system for enabling inter data source value comparison in a business rule engine is described. The system comprises a memory, and a processing engine communicatively coupled with the memory, configured to receive a message from one of a plurality of network functions and retrieve data associated with the received message from a plurality of data sources. The processing engine is configured to analyze data corresponding to the received message with the data retrieved from the plurality of data sources. The processing engine is configured to evaluate at least one business rule based on a result of the analysis. The processing engine is configured to provide at least one policy rule to one of the plurality of network functions based on the at least one evaluated business rule.

[0044] In some embodiments, the processing engine is configured to apply the at least one policy rule to one of the plurality of network functions.

[0045] In some embodiments, the processing engine is configured to verify the message received from one of the plurality of network functions. The verification is one of a successful verification and a non-successful verification.

[0046] In some embodiments, upon the successful verification, the data corresponding to the received message and the data retrieved from the plurality of data sources is analyzed and upon non-successful verification, the processing engine is configured to send an error response to one of the plurality of network functions.

[0047] In some embodiments, to analyze the data, the processing engine (208) is configured to compare data of the received message and the data retrieved from the plurality of data sources.

[0048] In some embodiments, the plurality of data sources includes a session management function (SMF), a charging function (CHF), a binding support function (BSF), a network repository function (NRF), an access management function (AMF), an application function (AF), an online charging system (OCS), a packet data network (PDN), a packet gateway (PGW), a network management system (NMS), an unified data repository (UDR) and a subscription profile repository (SPR).

[0049] In some embodiments, the data of the received message and the data from one of the plurality of data sources include at least one of a tracking area code (TAC) and a radio access technology (RAT) type.

[0050] In some embodiments, one of the plurality of network functions comprises an access management (AM), a session management (SM), a Gx interface, and a service-level commitment (SLC), and the received message from one of the plurality of network functions comprises one of a subscriber notification request (SNR), and an authorization authentication request (AAR).

[0051] In another exemplary embodiment, a user equipment (UE) is described. The UE is communicatively coupled with a network, the coupling comprises steps of receiving, by the network, a connection request from the UE, sending, by the network, an acknowledgment of the connection request to the UE and transmitting a plurality of signals in response to the connection request, the network is configured for performing a method for inter data source value comparison in a business rule engine.

[0052] In yet another exemplary embodiment, a policy control function (PCF) and a policy charging and rules function (PCRF) for enabling inter data source value comparison in a business rule engine is described. The PCF and the PCRF are configured to receive a message from one of a plurality of network functions and retrieve data associated with the received message from a plurality of data sources. The PCF and the PCRF are configured to analyze data correspondingto the received message with the data retrieved from the plurality of data sources. The PCF and the PCRF are configured to evaluate at least one business rule based on a result of the analysis. The PCF and the PCRF are configured to provide at least one policy rule to one of the plurality of network functions based on the at least one evaluated business rule.

[0053] In some embodiments, the plurality of data sources includes a session management function (SMF), a charging function (CHF), a binding support function (BSF), a network repository function (NRF), an access management function (AMF), an application function (AF), an online charging system (OCS), a packet data network (PDN), a packet gateway (PGW), a network management system (NMS), a unified data repository (UDR) and a subscription profile repository (SPR).

[0054] In some embodiments, the data of the received message and the data from the plurality of data sources include tracking area code (TAC) and radio access technology (RAT) types.

[0055] In some embodiments, one of the plurality of network functions comprises an access management (AM), a session management (SM), a Gx interface, and a service-level commitment (SLC). The received message from one of the plurality of network functions comprises one of a subscriber notification request (SNR), and an authorization authentication request (AAR).

[0056] In some embodiments, the PCF and the PCRF are configured to apply the at least one of the corresponding set of policy rules, charging rules, or access rules to one of the plurality of network functions.

[0057] In some embodiments, PCF and the PCRF are configured to verify the message received from one of the plurality of network functions, the verification is one of a successful verification and a non-successful verification.

[0058] In some embodiments, upon the successful verification, the data corresponding to the received message and the data retrieved from the plurality of data sources is analyzed and upon non-successful verification, the PCF and the PCRF are configured to send an error response to one of the plurality of network functions.

[0059] In some embodiments, to analyze the data, the PCF and the PCRF (218) are configured to compare data of the received message and the data retrieved from the plurality of data sources.

[0060] In an exemplary embodiment, the present invention discloses a computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform a method for enabling inter data source values comparison in a business rule engine. The method comprises receiving, by a processing engine, a message from one of plurality of network functions and retrieving, by the processing engine, data associated with the received message from a plurality of data sources. The method comprises analyzing, by the processing engine, data corresponding to the received message with the data retrieved from the plurality of data sources. The method comprises evaluating, by the processing engine, at least one business rule based on a result of the analysis. The method further comprises providing, by the processing engine, at least one policy rule to one of the plurality of network functions based on the at least one evaluated business rule.

[0061] The foregoing general description of the illustrative embodiments and the following detailed description thereof are merely exemplary aspects of the teachings of this disclosure and are not restrictive.OBJECTS OF THE PRESENT DISCLOSURE

[0062] It is an object of the present disclosure to provide a system and method for enabling inter data source value comparison in a business rule engine of a Policy Control Function (PCF) and a Policy and Charging Rules Functions (PCRF).

[0063] It is an object of the present disclosure to compare dynamic values from data sources (e.g., session management function (SMF, access management function (AMF), packet gateway (PGW), unified data repository (UDR), or subscription profile repository (SPR)), thereby reducing a set of business rules required and increasing flexibility in policy and charging decisions.

[0064] It is an object of the present disclosure to provide a flexible set of business rules, to compare data objects across the various data sources.

[0065] It is an object of the present disclosure to provide a solution that provides flexibility in terms of comparison of operators as predefined in a business rule engine of the PCF and the PCRF network functions.BRIEF DESCRIPTION OF THE DRAWINGS

[0066] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be appreciated by those skilled in the art that disclosure of such drawings includes the disclosure of electrical components, electronic components or circuitry commonly used to implement such components.

[0067] FIG. 1 illustrates an exemplary network architecture for enabling inter data source value comparison in a business rule engine, in accordance with embodiments of the present disclosure.

[0068] FIG. 2 illustrates a block diagram of a system configured for enabling inter data source value comparison in the business rule engine, in accordance with embodiments of the present disclosure.

[0069] FIG. 3 illustrates an exemplary process flow for enabling inter data source value comparison in the business rule engine, in accordance with embodiments of the present disclosure.

[0070] FIG. 4 illustrates an exemplary representation of connection diagram of PCF and PCRF with other network functions connected through a corresponding interface, in accordance with embodiments of the present disclosure.

[0071] FIG. 5 illustrates a flow diagram of a method for enabling inter data source value comparison in the business rule engine, in accordance with embodiments of the present disclosure.

[0072] FIG. 6 illustrates an exemplary block diagram of a computer system in which or with which embodiments of the present disclosure may be implemented.LIST OF REFERENCE NUMERALS100 - Network architecture102-1 and 102-2- Users104-1 and 104-2 -User Equipments106 - Network108 - System202 - Processor204 - Memory206 - A Plurality of Interfaces208 - Processing Engine210 - Database212 - Receiving Engine214 - Retrieval Engine216 - Business rule Engine218, 402 - Policy Control Function (PCF) - Policy and Charging Rules Functions (PCRF)220 - Other Engines400 - Connection diagram404 - Access and Mobility Management Function (AMF)406 - N15 interface408 - Application Function (AF)410 - Roaming Exchange (Rx)412 - Deep Packet Inspection (DPI)414 - Sd interface416 - Session Management Function (SMF)418 - N7 interface420 - Charging Function (CHF)422 - N28 interface424- Nbsf426 - Binding Support Function (BSF)428- Nnrf430 - Network Repository Function (NRF)432 - Online Charging Systems (OCS)434 - Sy diameter interface (Sy)436 - Packet Data Network Gateway (PGW)438 - Gx interface440 - Network Management System (NMS)442 - Subscriber Profile Repository (SPR)500 - Flow diagram600 - Computing system610 - External Storage Device620 - Bus630 - Main Memory640 - Read Only Memory650 - Mass Storage Device660 - Communication Port670 - ProcessorDETAILED DESCRIPTION

[0073] In the following description, for the purposes of explanation, various specific details are set forth in order 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. An individual feature may notaddress all of the problems discussed above or might address only some of the problems discussed above. Some of the problems discussed above might not be fully addressed by any of the features described herein.

[0074] The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the invention as set forth.

[0075] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, networks, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments.

[0076] Also, it is noted that individual embodiments may be described as a process which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination can correspond to a return of the function to the calling function or the main function.

[0077] The word “exemplary” and / or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, anyaspect or design described herein as “exemplary” and / or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive — in a manner similar to the term “comprising” as an open transition word — without precluding any additional or other elements.

[0078] Reference throughout this specification to “one embodiment” or “an embodiment” or “an instance” or “one instance” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, the appearances of the phrases “in one embodiment” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0079] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and / or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. As used herein, the term “and / or” includes any and all combinations of one or more of the associated listed items.

[0080] The present disclosure relates to a system and a method for enabling inter data source value comparison in a business rule engine. Inter data source value comparison refers to a process of comparing data values that are obtained from different sources within the system. It involves taking data from various network functions or repositories, such as, but not limited to, Session Management Function(SMF), Access and Mobility Management Function (AMF), Packet Data Network Gateway (PGW), Unified Data Repository (UDR), and Subscription Profile Repository (SPR), and comparing these values to make more informed and flexible decisions. Currently, when an Access and mobility management (AM) policy, a Session management (SM) Policy, or a Gx request is received at a Policy Control Function (PCF) and Policy and Charging Rules Functions (PCRF), the PCF and PCRF may check business rules for the received request and their associated parameter values from various interfaces. These checks are made against corresponding static values defined in the business rule engine. The static values may be, for example, an individual value, a comma separated value, an array, and the like. However, the parameter values received from the SMF are not compared with parameter values received from other data sources, such as the UDR, SPR, AMF, and the like. The disclosed system and method enable the comparison of values received from one interface, like the AMF or SMF, with values received from another interface, such as the Charging Function (CHF), the UDR, or the SPR. This facilitates evaluation decisions, allowing for the application of the desired policy accordingly.

[0081] The various embodiments throughout the disclosure will be explained in more detail with reference to FIGS. 1-6.

[0082] The FIG. 1, illustrates an exemplary network architecture (100) for enabling inter data source value comparison in a business rule engine, in accordance with embodiments of the present disclosure.

[0083] In FIG. 1, the network architecture (100) may include one or more computing devices or user equipments (UEs) (104-1 and 104-2) associated with one or more users (102-1 and 102-2) in an environment. A person of ordinary skill in the art will understand that one or more users (102-1 and 102-2) may be individually referred to as the user (102) and collectively referred to as the users (102). Similarly, a person of ordinary skill in the art will understand that one or more UEs (104-1 and 104-2) may be individually referred to as the UE ( 104) and collectively referred to as the UEs (104). A person of ordinary skill in the art will appreciate that the terms “computing device(s)” and “user equipment” may be used interchangeablythroughout the disclosure. Although two UEs (104) are depicted in FIG. 1, however any number of the user equipments (104) may be included without departing from the scope of the ongoing description. In an embodiment, each of the UE (104) may have a first unique identifier attribute associated therewith. In an embodiment, the first unique identifier attribute may be indicative of at least one of a Mobile Station International Subscriber Directory Number (MSISDN), International Mobile Equipment Identity (IMEI) number, an International Mobile Subscriber Identity (IMSI), a Subscriber Permanent Identifier (SUPI), and the like.

[0084] In an embodiment, the UE (104) may include smart devices operating in a smart environment, for example, an Internet of Things (loT) system. In such an embodiment, the UE (104) may include, but is not limited to, smart phones, smart watches, smart sensors (e.g., mechanical, thermal, electrical, magnetic, etc.), networked appliances, networked peripheral devices, a networked lighting system, communication devices, networked vehicle accessories, networked vehicular devices, smart accessories, tablets, smart television (TV), computers, a smart security system, a smart home system, other devices for monitoring or interacting with or for the users (102) and / or entities, or any combination thereof. A person of ordinary skill in the art will appreciate that the UE (104) may include, but is not limited to, intelligent, multi-sensing, network-connected devices, which can integrate seamlessly with each other and / or with a central server or a cloudcomputing system or any other device that is network-connected.

[0085] In an embodiment, the UE (104) may include, but is not limited to, a handheld wireless communication device (e.g., a mobile phone, a smart phone, a phablet device, and so on), a wearable computer device (e.g., a head-mounted display computer device, a head-mounted camera device, a wristwatch computer device, and so on), a Global Positioning System (GPS) device, a laptop computer, a tablet computer, or another type of portable computer, a media playing device, a portable gaming system, and / or any other type of computer device with a wireless communication capabilities, and the like. In an embodiment, the UE (104) may include, but is not limited to, any electrical, electronic, electro-mechanical, or an equipment, or a combination of one or more of the above devices such as virtualreality (VR) devices, augmented reality (AR) devices, a laptop, a general-purpose computer, a desktop, a personal digital assistant, a tablet computer, a mainframe computer, or any other computing device. In addition, the UE (104) may include one or more in-built or externally coupled accessories including, but not limited to, a visual aid device such as a camera, an audio aid, a microphone, a keyboard, and input devices for receiving input from the user (102) or an entity such as touch pad, a touch enabled screen, an electronic pen, and the like. A person of ordinary skill in the art will appreciate that the UE (104) may not be restricted to the mentioned devices and various other devices may be used.

[0086] In FIG. 1, the UE (104) may communicate with a system (108) via a network ( 106) . In other words, the UE ( 104) may be communicatively coupled with the network (106), the coupling comprises steps of receiving, by the network (106), a connection request from the UE (104), sending, by the network (106), an acknowledgment of the connection request to the UE (104) and transmitting a plurality of signals in response to the connection request. The plurality of signals is responsible for communicating with the system (108) to enable inter data source value comparison in the business rule engine of the network (106).

[0087] In an embodiment, the network (106) may include at least one of a Fifth Generation (5G) network, a Sixth Generation (6G) network, or the like. The network (106) may enable the UEs (104) to communicate with other devices in the network architecture (100) and / or with the system (108). The network (106) may include a wireless card or some other transceiver connection to facilitate this communication. In another embodiment, the network (106) may be implemented as, or include any of a variety of different communication technologies such as a wide area network (WAN), a local area network (LAN), a wireless network, a mobile network, a Virtual Private Network (VPN), the Internet, the Public Switched Telephone Network (PSTN), or the like. In an embodiment, the network (106) may include one or more base stations, i.e., a base station-1 (112-1) and a base station-2 (112-2) for facilitating communication between the UEs (104). In an embodiment, the base station- 1 (112-1) and the base station-2 (112-2) may be collectively referred as base stations (112). The network (106) may be formed by the basestations (112) communicatively coupled with the UEs (104) to enable telecommunication exchanges between the UEs (104).

[0088] The base stations (112) maybe a network infrastructure that provides wireless access to one or more terminals associated therewith. The base stations (112) may have coverage defined to be a predetermined geographic area (e.g., a radius of 1 kilometre (km) to 3 kms) based on a distance over which a signal may be transmitted. The base stations (112) may include, but are not limited to, a wireless access point, an evolved NodeB (eNodeB), a 5G node or a next generation NodeB (gNB), a wireless point, a transmission point, or a reception point (TRP), and the like. In an embodiment, the base stations (112) may include one or more operational units that enable telecommunication between the UEs (104). In an embodiment, the one or more operational units may include, but not be limited to, transceivers, a baseband unit (BBU), a remote radio unit (RRU), an antenna, mobile switching centres, radio network control units, one or more processors associated thereto.

[0089] In an embodiment, the network (106) may include one or more network entities depicted as a network entity 1 (110-1) and a network entity 2 (110- 2) in FIG. 1. The network entity 1 (110-1) and the network entity 2 ( 110 -2) may be collectively referred to as network entities (110). In an embodiment, the network entities (110) may include, but are not limited to, a Serving Gateway (SGW), a Packet Data Network Gateway (PGW), a Mobility Management Entity (MME), and the like. In some embodiments, where the network (106) is the 5G network, the network (106) may further include a user plane, and a control plane having the network entities (110) such as an Access and Mobility Management Function (AMF) unit, a Session Management Function (SMF) unit, and a Network Exposure Function (NEF) unit, but not limited thereto. In an embodiment, the network entities (110) forming the network (106) may be implemented as a hardware component, a software component, or any combination thereof.

[0090] In an embodiment, the system (108) may be a network entity (e.g., the network entity 1 (110-1) or the network entity 2 (110-2)) indicative of a Policy and Charging Rules Function (PCRF) or a Policy Charging Function (PCF), or acombination thereof. In an embodiment, the PCRF may be configured to enable inter data source value comparison in the business rule engine. As will be explained in detail in conjunction with FIGS. 2 to 6, in order to enable inter data source value comparison, initially, the PCF and the PCRF are configured to receive a message from one of a plurality of network functions and verify the message received from one of the plurality of network functions. Upon successful verification, the PCF and the PCRF are configured to retrieve data from a plurality of data sources. Further, the PCF and the PCRF are configured to compare data of the received message and the data retrieved from the plurality of data sources. Upon comparison, if the data of the received message and the data from the plurality of data sources is matched, the PCF and the PCRF are configured to evaluate at least one business rule to determine at least one of a corresponding set of policy rules, charging rules, or access rules. Further, the PCF and the PCRF are configured to provide the at least one of the corresponding sets of policy rules, charging rules, or access rules to one of the plurality of network functions.

[0091] Although FIG. 1 shows exemplary components of the network architecture (100), in other embodiments, the network architecture (100) may include fewer components, different components, differently arranged components, or additional functional components than depicted in FIG. 1. Additionally, or alternatively, one or more components of the network architecture (100) may perform functions described as being performed by one or more other components of the network architecture (100).

[0092] FIG. 2 illustrates an exemplary block diagram (200) of the system (108), in accordance with an embodiment of the present disclosure.

[0093] In an aspect, the system (108) may include one or more processor(s) (202). The one or more processor(s) (202) may be implemented as one or more microprocessors, microcomputers, microcontrollers, edge or fog microcontrollers, digital signal processors, central processing units, logic circuitries, and / or and devices that process data based on operational instructions. Among other capabilities, the one or more processor(s) (202) may be configured to fetch and execute computer-readable instructions stored in a memory (204) of the system(108). The memory (204) may be configured to store one or more computer- readable instructions or routines in a non-transitory computer readable storage medium, which may be fetched and executed to create or share data packets over a network service. The memory (204) may include any non-transitory storage device including, for example, volatile memory such as Random Access Memory (RAM), or non-volatile memory such as Erasable Programmable Read-Only Memory (EPROM), flash memory, and the like.

[0094] As depicted in FIG. 2, the system (108) may include an interface(s) (206). The interface(s) (206) may include a variety of interfaces, for example, interfaces for data input and output devices, referred to as I / O devices, storage devices, and the like. The interface(s) (206) may facilitate communication to / from the system (108). The interface(s) (206) may also provide a communication pathway for one or more components of the system (108). Examples of such components include, but are not limited to, processing unit / engine(s) (208) and a database (210).

[0095] In an embodiment, the processing engine (208) may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing engine (208). In examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processing engine (208) may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processing engine (208) may include a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the machine-readable storage medium may store instructions that, when executed by the processing resource, implement the processing engine (208). In such examples, the system (108) may include the machine-readable storage medium storing the instructions and the processing resource to execute the instructions, or the machine-readable storage medium may be separate but accessible to the system (108) and the processing resource. In other examples, the processing engine (208) may be implemented by electronic circuitry.

[0096] In an embodiment, the database (210) may include data that may be either stored or generated as a result of functionalities implemented by any of the components of the processor (202) or the processing engine (208). In an embodiment, the database (210) may be separate from the system (108). In an embodiment, the database (210) may be indicative of including, but not limited to, a relational database, a distributed database, a cloud-based database, or the like.

[0097] In an exemplary embodiment, the processing engine (208) may include one or more engines selected from any of a receiving engine (212), a retrieval engine (214), a business rule engine (216) and other engines (220) having functions that may include, but are not limited to, testing, storage, and peripheral functions, such as a wireless communication unit for remote operation, audio unit for alerts and the like. The business rule engine (216) may include a Policy Control Function (PCF) and a Policy and Charging Rules Function (PCRF) (218). In an embodiment, each engine, the receiving engine (212), the retrieval engine (214), the business rule engine (216) and the other engines (220) may be configured using the PCF and the PCRF (218) for enabling inter data source value comparison in the business rule engine (216).

[0098] In an embodiment, the receiving engine (212) may receive a message from one of a plurality of network functions. One of the plurality of network functions may include an AM, a SM, a Gx interface, and a SLC. The message received from one of the plurality of network functions may include one of a subscriber notification request (SNR), and an authorization authentication request (AAR). The SNR is a message typically used in Diameter-based protocols (part of 3GPP standards) to request notifications about changes in a subscriber’s profile or status. For example, an SNR message may be sent from the PCF and PCRF (218) to various data sources (e.g., the UDR or SPR) to request notification when there is a change in the subscriber's data, such as an update to the subscription plan or policy profile.

[0099] Additionally, the AAR is a message used in Diameter-based protocols to request authorization and authentication for a user’s session or service request. It is commonly used in scenarios where network services need to verifythat the user is authorized to access a specific service and to authenticate the user’s credentials. For example, when a user tries to access a particular service, the data sources (e.g., PGW) sends an AAR message to the PCRF to check if the user is authorized and authenticated forthat service.

[0100] The PCF and PCRF (218) may verify the message received from one of the plurality of network functions. The PCF and PCRF (218) may verify the received message from one of the plurality of network functions through a series of checks and validations. This verification process typically involves examining the message content, ensuring it meets predefined criteria, and confirming its authenticity.

[0101] By way of an example, the PCF and PCRF (218) may analyze the content of the received message to ensure it conforms to the expected format and structure. This involves checking for required fields, data types, and permissible value. Further, the PCF and PCRF (218) may verify whether the received message complies with the established policies and rules. This includes ensuring that the message adheres to regulatory requirements, network protocols, and business guidelines. Further, the PCF and PCRF (218) may authenticate a sender of the message to ensure its legitimacy. This may involve verifying digital signatures, user credentials, or session tokens. Additionally, authorization checks may be performed to determine whether the sender has the necessary permissions to perform the requested action. Moreover, the PCF and PCRF (218) may verify the integrity of the message to detect any tampering or unauthorized modifications. This is often achieved through cryptographic techniques such as message digests or digital signatures.

[0102] The verification may be one of a successful verification and a non- successfiil verification. If the verification is non-successfiil, the PCF and PCRF (218) may send an error response to one of the plurality of network functions. The error response may be to inform the sender of the message about the encountered problem and may include guidance on corrective actions to be taken for the nature of the error, such as invalid message format, authentication failure, or policy violation.

[0103] Upon successful verification, the retrieval engine (214) may retrieve data associated with the received message from a plurality of data sources. The plurality of data sources may include a SMF, a CHF, a BSF, a NRF, an AMF, an AF, an OCS, a PDN, a PGW, a NMS, an UDR and a SPR.

[0104] The PCF and PCRF (218) may analyze data corresponding to the received message with the data retrieved from the plurality of data sources. The analysis may be performed by comparing data of the received message and the data retrieved from the plurality of data sources. In an embodiment, the data of the received message and the data retrieved from the plurality of data sources may include at least one of a tracking area code (TAC) and a radio access technology (RAT) type.

[0105] TAC is a parameter used in cellular networks to identify a geographic area within which a mobile device is currently located. It is typically received as part of the signalling messages exchanged between network elements. In an embodiment, the TAC received from one of the SMF may be compared with the TAC stored in a subscriber’s profile in repositories like the SPR or UDR. RAT type indicates the type of wireless communication technology being used by a mobile device to connect to the network, such as UTE, 5G, or Wi-Fi. Similar to TAC, the RAT type may also be part of the signalling messages exchanged between various data sources. In an embodiment, the RAT type may be evaluated against custom values stored in repositories like SPR.

[0106] In an embodiment, the at least one business rule may be stored in the business rule engine (216). The at least one business rule may define conditions, criteria, and actions to be taken based on specific scenarios. For example, the predefined set of business rules may include, but is not limited to, access control rules, Quality of Service (QoS) rules, charging rules, and policy enforcement rules. The access control rules may specify conditions for granting or denying access to network resources based on user identity, device type, or location. Further, QoS rules may define parameters for traffic prioritization, bandwidth allocation, and service differentiation based on service requirements and network conditions. Further, the charging rules may determine tariff rates, billing policies, and chargingmechanisms for different services and usage paterns, considering subscriber profiles and service characteristics. Additionally, the policy enforcement rules may govern the enforcement of network policies, including traffic shaping, throtling, and redirection based on network conditions and policy objectives.

[0107] Upon comparison, if the data of the received message and the data from the plurality of data sources is matched, the PCF and PCRF (218) may evaluate the at least one business rule to determine at least one policy rule (e.g., a set of policy rules, charging rules, or access rules).

[0108] For example, if the comparison reveals that a subscriber’s session parameters align with certain predefined criteria outlined in the business rules, the PCF and PCRF (218) may reference these rules to make decisions regarding policy enforcement. This may include applying QoS policies to prioritize network traffic, enforcing access control rules to regulate resource usage, or implementing charging rules to bill the subscriber accordingly.

[0109] Furthermore, the evaluation process may include considering various factors, such as network conditions, subscriber preferences, and service agreements to ensure that the decisions align with regulatory requirements and business objectives. This evaluation ensures that the network operates efficiently and in accordance with established policies and standards.

[0110] Overall, by evaluating the predefined set of business rules in conjunction with the matched data, the PCF and PCRF (218) may determine appropriate set of policy rules, charging rules, or access rules to be applied in response to the received message.

[0111] The set of policy rules often include Quality of Service (QoS) directives, which specify how different types of traffic are to be treated based on priority levels. For instance, streaming services may be given higher priority over regular browsing to ensure uninterrupted service. Policy rules may also encompass access control policies, which define which users or devices can access specific network resources and under what conditions, thus ensuring network security and proper resource allocation. Additionally, these policy rules might dictate bandwidthallocation to manage congestion and optimize network performance, ensuring that critical services maintain their performance during peak usage times.

[0112] The charging rules are directives that determine how subscribers are billed for their usage of network services. These may include real-time charging mechanisms that bill users based on data consumption, duration of usage, or specific services accessed. The charging rules may also include tiered pricing models, where different usage levels are billed at different rates, encouraging efficient use of network resources. The charging rules may also enforce usage caps or apply additional charges for exceeding predefined limits, helping to manage network load and ensure fair usage across the subscriber base.

[0113] The access rules involve directives that control how and when subscribers can access network services. The access rules may include authentication requirements to verify user identity before granting access, ensuring security, and preventing unauthorized usage. The access rules may also define timebased access restrictions, allowing or denying service access during certain times of the day or in specific locations, which may be useful for managing network load and providing customized service experiences. Furthermore, access rules may include parental control settings that restrict access to certain types of content, enhancing user safety and compliance with regulatory standards.

[0114] Further, the PCF and PCRF (218) may provide the determined set of policy rules, charging rules, or access rules to one of the plurality of network functions. For example, if the evaluation process results in the determination of specific QoS policies to be applied to the subscriber's session, the PCF and PCRF (218) may transmit these policies to the relevant network functions responsible for traffic management and prioritization. Similarly, if chaiging rules are established for billing purposes based on the evaluated data and business rules, these rules are communicated to the appropriate charging function within the network. By providing the determined set of policy rules, charging rules, or access rules to the relevant network functions, the PCF and PCRF (218) ensure consistent and uniform enforcement of policies across the network infrastructure.

[0115] FIG. 3 illustrates an exemplary process flow (300) for enabling inter data source value comparison in the business rule engine, in accordance with an embodiment of the disclosure. In order to enable the inter data source value comparison, initially, the processing engine (208) receives a message from one of the plurality of network functions. This message may include various types of requests or notifications, such as a subscriber notification request (SNR), an authorization authentication request (AAR), a policy request, a session update request, or a resource allocation request. The data or content of the message may include data elements such as, but not limited to, tracking area code (TAC), radio access technology (RAT) type, subscriber identifier, quality of service (QoS) parameters, location identifiers, or service usage parameters.

[0116] At step 302, the processing engine (208) checks if the received message is valid to ensure it meets predefined criteria. This step is crucial for ensuring that only valid messages proceed through the subsequent steps. The predefined criteria may include checking whether the session in which the request is sent exist or not. If the session does not exist, an error response may be sent. Additionally, the predefined criteria may include verifying that all mandatory fields are present in the message. If any mandatory field is missing, the message may be considered invalid.

[0117] For example, if the received message is the SNR, the processing engine (208) may first check if the session associated with the request exists. If the session does not exist, an error code (e.g., error response) is returned to the sender (e.g., the one of the plurality of network functions). Additionally, the processing engine (208) may verify that all required fields, such as subscriber ID and TAC, are included in the message. If any of these mandatory fields are missing, the message is flagged as invalid and will not proceed further in the process.

[0118] If the message is invalid, the process moves to step 304 where the processing engine (208) sends an error response to one of the plurality of network functions. In an aspect, when the message validation is not successful only error code is sent in response. For example, if session is not present then 404 error code may be is send in response. In some embodiments, 400 error code may also be sentin response. This ensures that the sender is informed of the invalidity of the message and the nature of the error, allowing for corrective actions. Upon validation of the received message, the process flow (300) moves to step 306. Here, the processing engine (208) gathers the required data from a plurality of data sources and interfaces. These data sources may include, but is not limited to, PGW, UDR, SPR, AMF, SMF, OCS, CHF, BSF, AF, , and NEF. At step 308, the processing engine (208) begins evaluating the at least one business rule. The processing engine (208) checks the data gathered from the various data sources against the at least one business rule. It is crucial that a business rule exists for the matching source to proceed with the evaluation.

[0119] Further, at step 310, the processing engine (208) determines whether there is a match between the data from the received message and the data gathered from the plurality of data sources based on the at least one business rule. If no match is found, the process flow (300) loops back to continue evaluating additional rules. If a match is found, the process flow (300) moves to step 312.

[0120] When a rule match is found, the processing engine (208) applies the corresponding rule action at step 312. This action involves the implementation of the determined policy rules, charging rules, or access rules based on the matched business rule. At step 314, the processing engine (208) checks whether there are more rules to evaluate. If there are additional rules to be evaluated, the process flow loops back to step 308 to continue the evaluation. This iterative process ensures that all relevant rules are considered.

[0121] Once all rules have been evaluated and appropriate actions have been applied, the processing engine (208), at step 316, sends a response with the associated action to the network function that initiated the request, ensuring that the requesting network function is informed of the applied rules and actions, facilitating further actions based on these policies.

[0122] FIG. 4 illustrates an exemplary representation of connection diagram (400) of PCF and PCRF with other network functions connected through a corresponding interface, in accordance with embodiments of the present disclosure.

[0123] As shown in the FIG. 4, the PCF and the PCRF (402) may communicate with a plurality of network functions through a plurality of interfaces. This interconnected network enables an efficient implementation and enforcement of policy and charging rules across the network. The plurality of network functions include a session management function (SMF) (416), a charging function (CHF) (420), a binding support function (BSF) (426), a network repository function (NRF) (430), an access management function (AMF) (404), an application function (AF) (408), an online charging system (OCS) (432), a packet data network (PDN) gateway (PGW) (436), a network management system (NMS) (440), an unified data repository (UDR) and a subscription profile repository (SPR) (442).

[0124] The AMF (404) may communicate with the PCF and the PCRF (402) viaaN15 interface (406). DPI (412) may communicate with the PCF and the PCRF (402) viaa Sd interface (414). The DPI (412) is critical for analysing network traffic in real-time, providing detailed information about data flows, which helps the PCF and PCRF (402) in making informed policy decisions. The SMF (416) may communicate with the PCF and the PCRF (402) via a N7 interface (418). The SMF (416) is responsible for session establishment, modification, and release, and its interaction with the PCF and PCRF (402) ensures that policies are enforced throughout the lifecycle of a session. The CHF (420) may communicate with the PCF and the PCRF (402) via a N28 interface (422). The CHF (420) handles the charging data records (CDRs) and interacts with the PCF and PCRF (402) to apply charging rules based on usage data, ensuring accurate billing, and charging mechanisms.

[0125] The BSF (426) may communicate with the PCF and the PCRF (402) via a Nbsf interface (424). The BSF (426) manages the bindings of user sessions and internet protocol IP addresses, which is crucial for maintaining session continuity and enforcing policies related to user identity and session binding. The NRF (430) may communicate with the PCF and the PCRF (402) via a Nnrf interface (428). The NRF (430) provides a repository of network functions and their services, enabling the PCF and PCRF (402) to discover and interact with other network entities dynamically. The AF (408) may communicate with the PCF and the PCRF(402) via a Rx interface (410). The AF (408) provides application-level information and requirements, enabling the PCF and PCRF (402) to apply application-specific policies that enhance the quality of experience for end-users. The PGW (436) may communicate with the PCF and the PCRF (402) via a Gx interface (438) . The PGW (436) acts as a gateway to external packet data networks, and its interaction with the PCF and the PCRF (402) is essential for enforcing policies related to data traffic management and QoS. The OCS (432) may communicate with the PCF and the PCRF (402) via a Sy interface (434). The OCS (432) is responsible for real-time charging and credit control, interacting with the PCF and the PCRF (402) to ensure that usage policies are aligned with the user's credit status and account balance.

[0126] FIG. 5 illustrates a flow diagram of a method (500) for enabling inter data source value comparison in the business rule engine (216), in accordance with an embodiment of the present disclosure.

[0127] The method (500), at step 502 includes receiving, by a processing engine, a message from one of a plurality of network functions, in examples, the message may be received through the network using simple network management protocol (SNMP). One of the plurality of network functions may include, but is not limited to, an AM, a SM, a Gx interface, and a SLC. The received message from one of the plurality of network functions may include, but is not limited to, one of a SNR, and an AAR.

[0128] In some embodiments, method (500), includes verifying, by the processing engine, the message received from one of the plurality of network functions. The verification is one of a successful verification and a non-successfiil verification. In some embodiments, upon non-successfiil verification, the method (500) includes sending, by the processing engine, an error response to one of the plurality of network functions.

[0129] Upon successful verification, the method (500), at step 504 includes retrieving, by the processing engine (208), data associated with the received message from a plurality of data sources. The plurality of data sources may include, but is not limited to, a SMF, a CHF, a BSF, a NRF, an AMF, an AF, an OCS, a PDN, a PGW, a NMS, an UDR and a SPR. In an embodiment, the data corresponding tothe received message and the data retrieved from the plurality of data sources includes at least one of a TAC and a RAT type.

[0130] The method (500), at step 506 includes analyzing, by the processing engine, data corresponding to the received message with the data retrieved from the plurality of data sources. In some embodiments, the analyzing includes comparing, by the processing engine (208), data corresponding to the received message and the data retrieved from the plurality of data sources.

[0131] Upon comparing, if the data of the received message and the data from the plurality of data sources is matched, the method (500), at step 508 includes, evaluating, by the processing engine (208), at least one business rule based on a result of the analysis.

[0132] The method (500), at step 510 includes providing, by the processing engine, provide at least one policy rule (e.g., set of policy rules, charging rules, or access rules) to one of the plurality of network functions based on the at least one evaluated business rule. In some embodiments, the method (500), includes applying, by the processing engine, the at least one policy rule, to one of the plurality of network functions.

[0133] In some embodiments, the present disclosure relates to a UE communicatively coupled with a network. The coupling comprises steps of receiving, by the network, a connection request from the UE, sending, by the network, an acknowledgment of the connection request to the UE, and transmitting a plurality of signals in response to the connection request. The inter data source value comparison in a business rule engine in the network is enabled by a method comprises receiving, by a processing engine, a message from one of plurality of network functions and retrieving, by the processing engine, data associated with the received message from a plurality of data sources. The method comprises analyzing, by the processing engine, data corresponding to the received message with the data retrieved from the plurality of data sources. The method comprises evaluating, by the processing engine, at least one business rule based on a result of the analysis. The method further comprises providing, by the processing engine, atleast one policy rule to one of the plurality of network functions based on the at least one evaluated business rule.

[0134] In some embodiments, the present disclosure relates to a computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform a method for enabling inter data source values comparison in a business rule engine. The method comprises receiving, by a processing engine, a message from one of plurality of network functions and retrieving, by the processing engine, data associated with the received message from a plurality of data sources. The method comprises analyzing, by the processing engine, data corresponding to the received message with the data retrieved from the plurality of data sources. The method comprises evaluating, by the processing engine, at least one business rule based on a result of the analysis. The method further comprises providing, by the processing engine, at least one policy rule to one of the plurality of network functions based on the at least one evaluated business rule.

[0135] In yet another exemplary embodiment, a policy control function (PCF) and a policy charging and rules function (PCRF) for enabling inter data source value comparison in a business rule engine is described. The PCF and the PCRF are configured to receive a message from one of a plurality of network functions and retrieve data associated with the received message from a plurality of data sources. The PCF and the PCRF are configured to analyze data corresponding to the received message with the data retrieved from the plurality of data sources. The PCF and the PCRF are configured to evaluate at least one business rule based on a result of the analysis. The PCF and the PCRF are configured to provide at least one policy rule to one of the plurality of network functions based on the at least one evaluated business rule.

[0136] FIG. 6 illustrates an exemplary computer system (600) in which or with which embodiments of the present disclosure may be implemented. As shown in FIG. 6, the computer system may include an external storage device (610), a bus (620), a main memory (630), a read-only memory (640), a mass storage device(650), communication port(s) (660), and a processor (670). A person skilled in the art will appreciate that the computer system may include more than one processor and communication ports. The processor (670) may include various modules associated with embodiments of the present disclosure. The communication port(s) (660) may be any of an RS -232 port for use with a modem-based dialup connection, a 10 / 100 Ethernet port, a Gigabit or 10 Gigabit port using copper or fiber, a serial port, a parallel port, or other existing or future ports. The communication port(s) (660) may be chosen depending on a network, such a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system connects.

[0137] The main memory (630) may be random access memory (RAM), or any other dynamic storage device commonly known in the art. The read-only memory (640) may be any static storage device(s) e.g., but not limited to, a Programmable Read Only Memory (PROM) chips for storing static information e.g., start-up or Basic Input / Output System (BIOS) instructions for the processor (670). The mass storage device (650) may be any current or future mass storage solution, which can be used to store information and / or instructions. Exemplary mass storage device (650) includes, but is not limited to, Parallel Advanced Technology Attachment (PATA) or Serial Advanced Technology Attachment (SATA) hard disk drives or solid-state drives (internal or external, e.g., having Universal Serial Bus (USB) and / or Lirewire interfaces), one or more optical discs, Redundant Array of Independent Disks (RAID) storage, e.g., an array of disks.

[0138] The bus (620) communicatively couples the processor (670) with the other memory, storage, and communication blocks. The bus (620) may be, e.g., a Peripheral Component Interconnect (PCI) / PCI Extended (PCI-X) bus, Small Computer System Interface (SCSI), Universal Serial Bus (USB), or the like, for connecting expansion cards, drives, and other subsystems as well as other buses, such a front side bus (FSB), which connects the processor 670 to the computer system.

[0139] Optionally, operator and administrative interfaces, e.g., a display, keyboard, joystick, and a cursor control device, may also be coupled to the bus(620) to support direct operator interaction with the computer system. Other operator and administrative interfaces can be provided through network connections connected through the communication port(s) (660). Components described above are meant only to exemplify various possibilities. In no way should the aforementioned exemplary computer system limit the scope of the present disclosure.

[0140] The present disclosure provides technical advancement related to enabling the inter data source value comparison in the business rule engine. This advancement addresses the limitations of existing solutions by utilizing dynamic values from sources like SMF, AMF, PGW, UDR, and SPR in business rule creation. By integrating the dynamic values into rule logic, organizations may reduce the complexity associated with managing numerous static rules. This approach allows for more generalized rules that adapt dynamically to varying conditions, thereby streamlining rule maintenance and ensuring consistent and efficient policy enforcement. Moreover, the ability to compare data objects across multiple sources enhances flexibility, enabling businesses to make more informed decisions based on real-time insights. This flexibility extends to the comparison of operators within the Business Rule Engine of PCF / PCRF NFs, empowering organizations to optimize resource allocation and operational strategies with greater precision and responsiveness.

[0141] While the foregoing describes various embodiments of the invention, other and further embodiments of the invention may be devised without departing from the basic scope thereof. The scope of the invention is determined by the claims that follow. The invention is not limited to the described embodiments, versions, or examples, which are included to enable a person having ordinary skill in the art to make and use the invention when combined with information and knowledge available to the person having ordinary skill in the art.ADVANTAGES OF THE PRESENT DISCLOSURE

[0142] The present disclosure provides a system and method for enabling inter data source value comparison in the business rule engine.

[0143] The present disclosure compares dynamic values from various data sources, including SMF, AMF, PGW, UDR, SPR, such that a set of business rules used when comparing static values are reduced.

[0144] The present disclosure provides a flexible set of business rules to compare data objects across the various data sources.

[0145] The present disclosure provides a solution that provides flexibility in terms of comparison of operators as defined in the business rule engine of the PCF and PCRF.

Claims

CLAIMSWe claim:

1. A method (500) for enabling inter data source value comparison in a business rule engine (216), the method (500) comprising: receiving (502), by a processing engine (208), a message from one of a plurality of network functions; retrieving (504), by the processing engine (208), data associated with the received message from a plurality of data sources; analyzing (506), by the processing engine (208), data corresponding to the received message with the data retrieved from the plurality of data sources; evaluating (508), by the processing engine (208), at least one business rule based on a result of the analysis; and providing (510), by the processing engine (208), at least one policy rule to one of the plurality of network functions based on the at least one evaluated business rule.

2. The method (500) as claimed in claim 1, further comprising applying, by the processing engine (208), the at least one policy rule to one of the plurality of network functions.

3. The method (500) as claimed in claim 1, comprising verifying, by the processing engine (208), the message received from one of the plurality of network functions, wherein the verification is one of a successful verification and a non-successful verification.

4. The method (500) as claimed in claim 3, wherein upon the successful verification, the data corresponding to the received message and the data retrieved from the plurality of data sources is analyzed, and wherein upon the non-successful verification, sending, by the processing engine (208), an error response to one of the plurality of network functions.

5. The method (500) as claimed in claim 1, wherein the analyzing comprises comparing, by the processing engine (208), data corresponding to the received message and the data retrieved from the plurality of data sources.

6. The method (500) as claimed in claim 1, wherein the plurality of data sources comprises a session management function (SMF) (416), a charging function (CHF) (420), a binding support function (BSF) (426), a network repository function (NRF) (430), an access management function (AMF) (404), an application function (AF) (408), an online charging system (OCS) (432), a packet data network (PDN), a packet gateway (PGW) (436), a network management system (NMS) (440), a unified data repository (UDR) and a subscription profile repository (SPR) (442).

7. The method (500) as claimed in claim 1, wherein one of the plurality of network functions comprises an access management (AM), a session management (SM), a Gx interface, and a service-level commitment (SLC), and wherein the received message from one of the plurality of network functions comprises one of a subscriber notification request (SNR), and an authorization authentication request (AAR).

8. The method (500) as claimed in claim 1, wherein the data corresponding to the received message and the data retrieved from the plurality of data sources comprises at least one of a tracking area code (TAC) and a radio access technology (RAT) type.

9. A system (108) for enabling inter data source value comparison in a business rule engine, the system (108) comprising: a memory (204); and a processing engine (208) communicatively coupled with the memory (204), configured to: receive a message from one of a plurality of network functions;retrieve data associated with the received message from a plurality of data sources; analyze data corresponding to the received message with the data retrieved from the plurality of data sources; evaluate at least one business rule based on a result of the analysis; and provide at least one policy rule to one of the plurality of network functions based on the at least one evaluated business rule.

10. The system (108) as claimed in claim 9, wherein the processing engine (208) is configured to apply the at least one policy rule to one of the plurality of network functions.

11. The system (108) as claimed in claim 9, wherein the processing engine (208) is configured to verify the message received from one of the plurality of network functions, wherein the verification is one of a successful verification and a non-successful verification.

12. The system (108) as claimed in claim 11, wherein upon the successful verification, the data corresponding to the received message and the data retrieved from the plurality of data sources is analyzed, and wherein upon the non-successful verification, the processing engine (208) is configured to send an error response to one of the plurality of network functions.

13. The system (108) as claimed in claim 9, wherein to analyze the data, the processing engine (208) is configured to compare data corresponding to the received message and the data retrieved from the plurality of data sources.

14. The system (108) as claimed in claim 9, wherein the plurality of data sources comprises a session management function (SMF) (416), a charging function (CHF) (420), a binding support function (BSF) (426), a network repository function (NRF) (430), an access management function (AMF)(404), an application function (AF) (408), an online charging system (OCS) (432), a packet data network (PDN), a packet gateway (PGW) (436), a network management system (NMS) (440), a unified data repository (UDR) and a subscription profile repository (SPR) (442).

15. The system (108) as claimed in claim 9, wherein the data corresponding to the received message and the data retrieved from the plurality of data sources comprises at least one of a tracking area code (TAC) and a radio access technology (RAT) type.

16. The system (108) as claimed in claim 9, wherein one of the plurality of network functions comprises an access management (AM), a session management (SM), a Gx interface, and a service-level commitment (SLC), and wherein the received message from one of the plurality of network functions comprises one of a subscriber notification request (SNR), and an authorization authentication request (AAR).

17. A policy control function (PCF) and a policy charging and rules function (PCRF) (218) for enabling inter data source value comparison in a business rule engine (216), wherein the PCF and the PCRF (218) are configured to: receive a message from one of a plurality of network functions; retrieve data associated with the received message from a plurality of data sources; analyze data corresponding to the received message with the data retrieved from the plurality of data sources; evaluate at least one business rule based on a result of the analysis; and provide at least one policy rule to one of the plurality of network functions based on the at least one evaluated business rule.

18. The PCF and the PCRF (218) as claimed in claim 17, wherein the plurality of data sources comprises a session management function (SMF) (416), a charging function (CHF) (420), a binding support function (BSF) (426), a network repository function (NRF) (430), an access management function (AMF) (404), an application function (AF) (408), an online charging system (OCS) (432), a packet data network (PDN), a packet gateway (PGW) (436), a network management system (NMS) (440), a unified data repository (UDR) and a subscription profile repository (SPR) (442).

19. The PCF and the PCRF (218) as claimed in claim 17, wherein the data corresponding to the received message and the data retrieved from the plurality of data sources comprises at least one of a tracking area code (TAC) and a radio access technology (RAT) type.

20. The PCF and the PCRF (218) as claimed in claim 17, wherein one of the plurality of network functions comprises an access management (AM), a session management (SM), a Gx interface, and a service-level commitment (SLC), and wherein the received message from one of the plurality of network functions comprises one of a subscriber notification request (SNR), and an authorization authentication request (AAR).

21. The PCF and the PCRF (218) as claimed in claim 17, further configured to verify the message received from one of the plurality of network functions, wherein the verification is one of a successful verification and a nonsuccessful verification.

22. The PCF and the PCRF (218) as claimed in claim 21, wherein upon the successful verification, the data corresponding to the received message and the data retrieved from the plurality of data sources is analyzed, and wherein upon the non-successful verification, the PCF and the PCRF (218) areconfigured to send an error response to one of the plurality of network functions.

23. The PCF and the PCRF (218) as claimed in claim 17, wherein to analyze the data, the PCF and the PCRF (218) are configured to compare data corresponding to the received message and the data retrieved from the plurality of data sources.

24. A user equipment (UE) (104) communicatively coupled with a network (106), the coupling comprises steps of: receiving, by the network (106), a connection request from the UE (104); sending, by the network (106), an acknowledgment of the connection request to the UE (104); and transmitting a plurality of signals in response to the connection request, wherein the network is configured to execute a method (500) for enabling inter data source value comparison in a business rule engine (216) as claimed in claim 1 .

25. A computer program product comprising a non-transitory computer- readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to execute a method (500) for enabling inter data source value comparison in a business rule engine (216), the method (500) comprising: receiving (502), by a processing engine (208), a message from one of a plurality of network functions; retrieving (504), by the processing engine (208), data associated with the received message from a plurality of data sources; analyzing (506), by the processing engine (208), data corresponding to the received message with the data retrieved from the plurality of data sources;evaluating (508), by the processing engine (208), at least one business rule based on a result of the analysis; and providing (510), by the processing engine (208), at least one policy rule to one of the plurality of network functions based on the at least one evaluated business rule.

Images