[0001] The present disclosure relates to a policy and charging configuration, and more specifically relates to a method and system for edge-based policy charging control deployment in communications network. The present application is based on, and claims priority from an Indian Application Number 202011037934 filed on 2nd September 2020, the disclosure of which is incorporated herein.

BACKGROUND
[0002] A policy and charging rules function (PCRF) relate to a policy decision point located centrally (i.e., at server or network) that comprises a plurality of policy rules governing a type of network, network services to which a subscriber is authorized to access, bandwidth level and/or limit whilst accessing the network services and further a duration of accessing the network services. Further, the PCRF communicates with access edge devices (e.g., policy enforcement points), applications, and Online Charging System (OCS) platforms to manage subscriber and network information according to the established rules. The PCRF identifies appropriate policy rules by querying a subscription profile repository (SPR) and enforces the appropriate policy rules by sending the appropriate policy rules to, for example, a policy and charging enforcement function (PCEF).
[0003] In traditional scenario, every data-consumption (i.e., accessing the internet resources) is navigated to the OCS. Hence, using a nation-wide bandwidth, increases the response time (latency in charging response) and experiences high load (TPS: Transactions Per Second) on the OCS. This is leading to wastage of resources such as for example, resources required to compute, licenses TPS, network operations, or the like. Further, the TPS cannot be minimized, as quota-slice cannot be implemented dynamically based on Radio Access Technology (RAT), location, plan etc., in the OCS, where quota-slice is a proportional part or reserved portion of a unit/policy/service/offer. Thus, heavy bandwidth consumption redirects to the OCS/ data charging node’s locations for unlimited data flow quota management and thereby the Existing Provisioning System (EPS) is overloaded by provisioning the customers in all PCRF per circle.
[0004] The quota management on the existing PCRF cannot be activated due to following reasons a) existing PCRF does not support the SPR distribution as it requires provisioning of the subscriber in multiple SPRs and b) existing PCRF does not have product life cycle management.
[0005] US8903059B2 discloses some policy and charging control (dPCC) architectures allow the PCRF to interact with several SPRs. These multi-SPR systems typically operate under the assumption that policy information for a subscriber is to be found in its entirety at a single SPR and is indexed or accessed by a subscriber identifier, such as a mobile subscriber ISDN number (MSISDN). As a result, the set of policy rules applied to the subscriber is always controlled by the same entity and is independent of the services or network that the subscriber is accessing.
[0006] US10574833B2 discloses a product related to charging and control of edge services is provided. The apparatus comprises a processor and a memory for storing instructions to be executed by the processor, wherein the apparatus is connectable to a radio access network element and the processor is configured to provide a connection to a core network, to handle applications and/or services for a user equipment connected to the radio access network element, and to handle charging and/or policy control for the applications and/or services.
[0007] US10477385B2 discloses a mobile device management and policy distribution.
[0008] EP2536179B1 discloses a system for selecting a Policy and Charging Rules Function (PCRF) entity.
[0009] ETSI TS 123 203 V10.8.0 discloses a SPR logical entity that contains all subscriber/subscription related information needed for subscription-based policies and IP-CAN bearer level dPCC rules by the PCRF.
[0010] BroadHop introduces breakthrough PCRF architecture in that the policy builder application module is aimed specifically at network service providers as a powerful tool designed to enable application and/or service development in conjunction with BroadHop’s Quantum Network Suite.
[0011] Mobile Broadband Networks can manage congestion while abiding by open internet principles: the edge provider could send the request for QoS treatment to the wireless carrier through a separate registration process, with the wireless carrier remaining in full control of policy rule creation and modification. This would require implementation of application detection and control (ADC) functionality, which enables the wireless carrier to implement a variety of rules based on network conditions (e.g., congestion, time, and day of the week). Wireless carriers can manage like applications using the same set of rules so as to maintain the like end user experience.
[0012] From the analysis of the above prior arts, it can be concluded that the charging is performed by a centralized billing or centralized charging system. Further, there is an increase in data replication because of usage of different data storage for accessing the policies or subscriber profiles. Thereby, increasing the resource usage and latency.
[0013] Thus, there exists a need for an architecture implementing dPCC that overcomes the aforementioned problems and further reduces the wastage of the resources and latency.

OBJECT OF THE DISCLOSURE
[0014] A principal object of the present disclosure is to deploy policy and charging control (dPCC) instances at edge nodes with individual subscriber databases, and further providing each edge node a direct access to other subscriber databases, thereby maintaining single storage of subscriber across all subscriber databases. This is achieved by ensuring that only chargeable events (e.g., PAYU: Pay As You Go) data flows should be sent towards IN/Online Charging System.
[0015] Another object of the present disclosure is to save on nationwide bandwidth by effectively monitoring the provisioning traffic.

SUMMARY
[0016] According to a first aspect, a method is provided for deploying a plurality of policy charging control (dPCC) instances on a plurality of edge nodes in an online charging system, each of the plurality of dPCC instances is associated with a subscriber profile database, each of the plurality of dPCC instances are connected to a central site in an online charging system, the online charging system is configured to charge one or more users for using one or more services. The method includes providing a first dPCC instance, an access to a first subscriber profile database associated with the first dPCC instance. Further, the method includes providing the first dPCC instance, a direct access to a plurality of subscriber profile databases corresponding to each of the plurality of dPCC instances in the architecture.
[0017] In one aspect, the direct access further includes providing one or more applications running at each of the dPCC instances, the direct access to the plurality of subscriber profile databases corresponding to the plurality of dPCC instances, other than the first dPCC instance.
[0018] In one aspect, the method further comprises maintaining a single storage of each of a plurality of user profiles in the subscriber profile database associated with each of the plurality of dPCC instances.
[0019] In one aspect, the method further comprises charging each of the one or more users, for the one or more services consumed by each of the one or more users, the one or more users corresponding to one or more service provider.
[0020] In one aspect, the method further comprises processing a first traffic type at the plurality of dPCC instances, the first traffic type corresponds to a non-charging traffic, wherein the non-charging traffic is independent of charging performed by the online charging system.
[0021] In one aspect, the method further comprises transmitting a second traffic type to the central site in the online charging system, the second traffic type corresponds to a charging traffic, wherein the charging traffic is required to be processed for charging the one or more users for using the one or more services.
[0022] In one aspect, the method further comprises defining a distribution rule to distribute the one or more users in the subscriber profile database associated with each of the plurality of dPCC instances.
[0023] In one aspect, the method further comprises defining a distribution rule to distribute the one or more users in the subscriber profile database associated with each of the plurality of dPCC instances, and fetching a user profile from a subscriber profile database associated with one of the pluralities of dPCC instances, based on the defined distribution rule.
[0024] In one aspect, the method further comprises defining a distribution rule to distribute the one or more users in the subscriber profile database associated with each of the plurality of dPCC instances, fetching a user profile from a subscriber profile database associated with one of the plurality of dPCC instance, based on the defined distribution rule, and processing a charging request associated with the fetched user profile, requested by the first dPCC instance, locally on the one of the plurality of dPCC instance associated with the fetched user profile.
[0025] In one aspect, the where the plurality of dPCC instances receives one or more charging request from multiple vendors in the online charging system, the online charging system comprising one or more sub-charging system, each sub-charging system corresponding to each of the multiple vendors.
[0026] According to a second aspect, a system is provided for deploying a plurality of policy charging control (dPCC) instances on a plurality of edge nodes in an online charging system, each of the plurality of dPCC instances is associated with a subscriber profile database, each of the plurality of dPCC instances are connected to a central site in an online charging system, the online charging system is configured to charge one or more users for using one or more services. The system comprising an access manager configured to provide a first dPCC instance, an access to a first subscriber profile database associated with the first dPCC instance. The access manager is further configured to provide the first dPCC instance, a direct access to a plurality of subscriber profile databases corresponding to each of the plurality of dPCC instances in the architecture.
[0027] These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings. It should be understood, however, that the following descriptions, while indicating preferred embodiments and numerous specific details thereof, are given by way of illustration and not of limitation. Many changes and modifications may be made within the scope of the embodiments herein without departing from the spirit thereof, and the embodiments herein include all such modifications.

BRIEF DESCRIPTION OF FIGURES
[0028] The method and system are illustrated in the accompanying drawings, throughout which like reference letters indicate corresponding parts in the various drawings. The embodiments herein will be better understood from the following description with reference to the drawings, in which:
[0029] FIG. 1 illustrates an architecture implementing a digital policy and charging control (dPCC).
[0030] FIG. 2 illustrates a system implementing edge dPCC nodes.
[0031] FIG. 3 illustrates an overview of a DDF deployment.
[0032] FIG. 4A illustrates a conventional autonomous system for deploying the dPCC.
[0033] FIG. 4B illustrates an autonomous system for deploying the dPCC.
[0034] FIG. 5 illustrates a sample deployment overview of dPCC.
[0035] FIG. 6a illustrates a conventional setup of accessing a subscriber profile repository (SPR).
[0036] FIG. 6b illustrates a proposed setup of accessing the SPR.
[0037] FIG. 7 is a flowchart diagram illustrating a method for edge-based policy charging control deployment in a communications network.

DETAILED DESCRIPTION
[0038] In the following detailed description of embodiments of the invention, numerous specific details are set forth in order to provide a thorough understanding of the embodiment of invention. However, it will be obvious to a person skilled in the art that the embodiments of the invention may be practiced with or without these specific details. In other instances, well known methods, procedures and components have not been described in details so as not to unnecessarily obscure aspects of the embodiments of the invention.
[0039] Furthermore, it will be clear that the invention is not limited to these embodiments only. Numerous modifications, changes, variations, substitutions and equivalents will be apparent to those skilled in the art, without parting from the scope of the invention.
[0040] The accompanying drawings are used to help easily understand various technical features and it should be understood that the embodiments presented herein are not limited by the accompanying drawings. As such, the present disclosure should be construed to extend to any alterations, equivalents and substitutes in addition to those which are particularly set out in the accompanying drawings. Although the terms first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are generally only used to distinguish one element from another.
[0041] The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. Also, the various embodiments described herein are not necessarily mutually exclusive, as some embodiments can be combined with one or more other embodiments to form new embodiments. The term “or” as used herein, refers to a non-exclusive or, unless otherwise indicated. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein can be practiced and to further enable those skilled in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.
[0042] As detailed earlier, in traditional scenario, every data-consumption (User-accessing the internet) goes to the Online Charging System (OCS), which is sitting at central site. Hence using the nation-wide bandwidth, increases the response time (Latency in charging response) and puts high load (TPS: Transactions Per Second) on OCS. While with dPCC, most of this usage (>80%) is accounted at the edge itself and only the usage, which needs to be charged goes to the central site OCS for charging. Hence reducing the WAN-link requirement and TPS at OCS by a great amount.
[0043] Secondly, as of now, in Operator’s Network, subscriber is to be provisioned at every PCRF (Policy and Charging Rules Function), as they do not have the DDF (data distribution function) kind of functionality and it increases the data-storage requirements at PCRF. So, if there are 10 edge sites in a circle, then for each 20Mn subscribers, there will be 200Mn profiles (10X). While with dPCC, it uses DDF to locate the subscriber profile internally and subscriber profile is only maintained in one SPR, without any replication.
[0044] The present disclosure provides scalable instances of policy control and charging (dPCC) at each edge node which is associated with its own subscriber profile repository (SPR) database and has access to all other SPR database directly. This provides single replication of subscriber in all the SPR databases, thereby reducing latency. A data distribution function (DDF) decides distribution of subscribers in all the SPRs using a best match rule. Further, the method provides processing all the non-charging transactions/traffic at edge node PCRF (policy and charging rules function) and sending charging related transactions at central site, to online charging system (OCS) for billing purposes. Thus, the present disclosure reduces the processing load at OCS, which are non-essential and thereby saves network resources significantly. Also, the method does not require redundancy of subscriber data at multiple SPRs, as each edge node dPCC instance has access to all the SPRs.
[0045] Further, the present disclosure aims to solve problem of increased latency, data replication and usage of different data stores while implementing traditional dPCC-as an edge-based dPCC deployment model, which utilizes automatic SPR lookup by providing each edge dPCC node access to SPR database. This way, any dPCC node can access any SPR and can handle any subscriber’s diameter/API with the DDF.
[0046] Further, the present disclosure aims at deploying dPCC instances at edge nodes with individual subscriber databases, and further providing each edge node a direct access to other subscriber databases, thereby maintaining single storage of subscriber across all subscriber databases.
[0047] Referring to FIG. 1, an architecture (100) implementing a digital policy and charging control (dPCC) is disclosed. The dPCC is a common engine used for Policy and Charging Rules Function (PCRF) and Online Charging System (OCS) on same instance.
[0048] The architecture (100) comprises a plurality of nodes (102a-e) (each node deploying the dPCC also referred to as edge-dPCC nodes) connected to a subscriber profile database (104) (hereinafter referred as “Subscriber Profile Repository (SPR) database (104)”). Further, each of the edge-dPCC nodes is connected to electronic devices (106a-e) (hereinafter referred to as “electronic device (106)”), associated with a client that is subscribed to network services such for example, internet resource package, VoLTE services, or the like. The electronic device (106) may be a device having a screen and capable of performing human-machine interaction, such as mobile phone, notebook, computer, tablet, desktop computer, virtual reality (VR) device, Augmented reality (AR) device, server, or the like. The edge-dPCC nodes (102a-e) may be any network node that are either a connection point, communication endpoint, interface points, service relaying station, or the like that are deployed at client-side.
[0049] The communication between each of the edge-dPCC nodes (102a-e) and the electronic device (106) and similarly communication between the edge-dPCC nodes (102a-e) and the SPR (104) can be through a network (108) using any network interfaces (not shown). The network (108) may include, but are not limited to, any one or more different types of communications network such as for example, public networks (e.g., internet), private networks (e.g., frame-relay networks), wireless networks, cellular networks, telephone networks (e.g., public switched telephone network), cloud-based networks, or any other suitable private or public packet switched or circuit switched networks.
[0050] In addition, the network interfaces may include communication links and associated networking devices (e.g., link-layer switches, routers, etc.,) for transmitting network traffic over any suitable type of medium including, but not limited to, fiber communication such as hybrid fiber-coaxial (HFC) medium, a microwave medium, a radio frequency communication medium, a satellite communication medium or any combination thereof.
[0051] Unlike conventional dPCC system the proposed architecture (100) provides scalable instances of the dPCC at each edge-dPCC nodes (102a-e) that is associated with its own SPR database (104) and also has access to all other SPR databases directly. Hence there is no data replication.
[0052] Referring to FIG. 2, a system (200) implementing the edge dPCC nodes (102a-c) is depicted. The architecture (200) includes a central site (210), edge dPCC nodes (102a-c) connected to a packet data network gateway (P-GW) (220a-c) and a dPCC engine (230).
[0053] The central site (210) comprises an Order management (OM) unit (202), a Customer relationship management (CRM) unit (204) and a billing unit (206). In an example, when a customer buys any sim including (package and plan) from a physical store, portal, application, etc., the subscription information will be obtained by and/or transmitted to the OM unit (202). The OM unit (202) works as an orchestrator in the central site (210). The CRM unit (204) can be configured to manage the administrative services such as managing relationship with the customer and further to create a subscriber profile of the customer. The subscriber profile may include, for example, subscription details such as validity of any services, value added services usage threshold, personnel details of the customer, billing cycle details, and the like. The billing unit (206) can be configured to generate a bill based on the subscriber profile.
[0054] The OM unit (202) can be further configured to route the subscriber profile to a management unit (240). The management unit (240) comprises an Application Programming Interface (API) layer (242) configured to interface between the OM unit (202) and the management unit (240). The management unit (240) further comprises a product information unit (244) i.e., product catalogue that knows offers and packages opted by the subscriber/customer. The management unit (240) further comprises a Data Distribution Function (DDF) unit (246) that can be configured to distribute and store the subscriber profiles into any of the SPR database (104a-c) situated in the network (108) (as shown in FIG. 3).
[0055] Referring to FIG. 3, the DDF unit (246) communicates with each of the edge-dPCC nodes (102a-c) and can be interface to access any of the SPR database(s) (104a-c).
[0056] The DDF unit (246) is configured to define a distribution rule to distribute the one or more users in the SPR database (104a-c) associated with each of the plurality of dPCC instances (i.e., edge-dPCC nodes (102a-c)). The distribution of the subscriber profiles into multiple SPRs database(s) (104), by the DDF unit (246) can be based on at least one criterion that is international mobile subscriber identity (IMSI), Mobile Station International Subscriber Directory Number (MSISDN), gateway, location and subscriber identity based.
[0057] The DDF unit (246) can be configured to fetch a user profile from the SPR database (104a-c) associated with one of the pluralities of dPCC instances, based on the defined distribution rule. Further, the DDF unit (246) can be configured to process a charging request associated with the fetched user profile, requested by the first dPCC instance, locally on the one of the pluralities of dPCC instance associated with the fetched user profile. The plurality of dPCC instances receives one or more charging request from multiple vendors in the online charging system (i.e., the central site (210)). The online charging system comprises one or more sub-charging system, each sub-charging system corresponding to each of the multiple vendors.
[0058] The DDF unit (246) provides options to intelligently distribute the subscriber profile to multiple SPR databases (104a-c), without any data replication. Any dPCC node can handle any subscriber’s diameter or API traffic.
[0059] The dPCC engine (230) is a modular solution, where the SPR (104) and the dPCC engine (230) can be scaled independently. Hence, if the subscriber volume is increased significantly, as compared to the network TPS, it is possible to only scale up the SPR (104) and not the whole solution. By virtue of the DDF unit (246), it is possible to distribute subscriber profiles, across multiple databases, without any data replication by matching business rule based on best match and not on first match approach. Further, the distribution is based on best match means, it checks for the maximum length check. If there are 3 entries in the DDF Table as below:
a. 404-SPR (104a)
b. 40456- SPR (104b)
c. 404567-SPR (104c)
[0060] A request is received with subscriber Identity: 40456709123034. Then the proposed dPCC engine (230) uses the best match and not the first routing entry. In other words, the dPCC engine (230) will look up the SPR (104c) (based on longest match: 404567) and not the SPR (104a) (based on first match: 404). Hence making the design more robust and operational friendly. Thus, by virtue of the DDF unit (246), the dPCC engine (230) can segregate the SPRs, based on subscriber-ID or other network information and hence, every dPCC node (102a-c) can access the subscriber profile in any (an all) SPRs (104a-c). Hence, subscriber provisioning is only required at one SPR and not at each site/SPR. The SPR segregation criteria include IMSI, MSISDN, Gateway, Location, Subscriber Identity.
[0061] The proposed dPCC architecture provides several advantages such as, for example, multi-vendor solution providing multiple customized/non-standard call flows with adjacent NEPs and multi-vendor IT Stack, business processes i.e., separate business flows for network operators. Further, the proposed dPCC architecture avoids data replication across multiple sites in dPCRF-SPR, new edge technology.
[0062] Referring back to FIG. 2, each edge-dPCC node (102a-c) includes a dPCC engine (230) that is configured to access multiple SPR databases (104a-c) from multiple edge-dPCC nodes (102a-c). Each edge-dPCC node (102a-c) is connected to the central site (210) via the management unit that provides an online charging system (OCS) to multiple vendors.
[0063] The dPCC engine (230) is configured to provide a first dPCC instance (i.e., at edge-dPCC node (102a)), an access to a first subscriber profile database (i.e., SPR database (104a)) associated with the first dPCC instance and thereafter provide the first dPCC instance, a direct access to a plurality of subscriber profile databases (located at each of the SPR databases (104b-c)) corresponding to each of the plurality of dPCC instances (i.e., edge-dPCC node (102b-c)) in the OCS.
[0064] Thus, the dPCC engine (230) is configured to provide one or more applications running at each of the dPCC instances (at each of the edge-dPCC nodes (102b-c)), the direct access to the plurality of subscriber profile databases (the SPR databases (104a-c) corresponding to the plurality of dPCC instances, other than the first dPCC instance (edge-dPCC nodes (102a)). Each of the SPR databases (104a-c) configured to maintain a single storage of each of the plurality of user profiles associated with each of the plurality of dPCC instances.
[0065] The dPCC engine (230) can be configured to process a first traffic type at the plurality of dPCC instances. The first traffic type corresponds to a non-charging traffic, where the non-charging traffic is independent of charging performed by the OCS. Further, the dPCC engine (230) can be configured to transmit a second traffic type to the central site (210) in the OCS. The second traffic type corresponds to a charging traffic, wherein the charging traffic is required to be processed for charging the one or more users for using the one or more services.
[0066] For example, when users start using plans or packages, there are interfaces Gx and Gy at dPCC. There are P-Gateway, dPCC, SPR at every node (edge dPCC nodes (102a-c)). The interface Gx is responsible for Policy and the interface Gy responsible for charging. Let us consider that user “X” has taken a subscription package (voice, data). Now, when the user starts using a package, the P-GW (220a-c) will first determine and fetches the subscriber profile from each SPR database(s) (104). The subscriber profile may include, for example, plans, packages, speed, balance, bandwidth, and the like. The subscriber profile fetched from the SPR databases (104a-c) is transmitted to the respective dPCC engine (230). If the request from the user is related to policy (like any unlimited package) then the interface Gx will be enabled and respond to the respective dPCC engine (230) and if the request is related to charging (real time deduction from balance), then the interface Gy will be enabled and responds to the receptive dPCC engine (230). The receptive dPCC engine (230) can be configured to charge each of the one or more users, for the one or more services consumed by each of the one or more users, the one or more users corresponding to one or more service provider.
[0067] Thus, the provision of the dPCC engine (230) can enable categorization between the policy and charging and thereby avoiding the traffic associated with the policy and charging. Further, any of the SPR databases (104a-c) will store the data of subscribers and all the SPRs databases (104a-c) are connected and accessible to each other that avoids the replication of data into databases.
[0068] Similarly, for multiple instances of dPCC, multiple instances of P-GW (220) can be created for multiple vendors and the dPCC engine (230) will respond accordingly over Diameter and RADIUS (Remote Authentication Dial-In User Service) protocols. These protocols are used to transfer the messages from and to northbound network elements.
[0069] In another example, consider that the usage consumption (data used by end-user) is reported over the interfaces Gx and Gy. The usage-reported over Gx is non-monetary (i.e., it doesn’t require any rating, free quota; say 1GB per day limit), while usage reported over Gy can be Non-monetary or Monetary (Rated usage, Rs. 0.1 per MB etc.). In general, all data consumption is reported over the OCS (at the central site (210)). But it is a costly affair, as out of it only 15-25% usage is non-monetary (usage that needs to be charged/rated). The usage reported over Gx and Gy reference points (interfaces) are handled by different nodes (PCRF for Gx and OCS for Gy). Hence, the proposed dPCC engine (230) is a common engine to work as a PCRF or OCS or both, thereby providing the flexibility to use either interface for usage metering/ balance Management.
[0070] Referring to FIG. 4A, where a conventional autonomous system (400a) for deploying the dPCC is shown. The autonomous system (400a) includes a PaCo (Packet Core) site (402) comprising one or more network gateways i.e., Gateway GPRS Support Node (GGSN) or PGW. Each gateway is part of a core network that connects the receptive cellular networks to the internet. The autonomous system (400a) further comprises a PCRF (404) that is a software node designated in real-time to determine policy rules in a multimedia network. As a policy tool, the PCRF plays a central role in next-generation networks. The autonomous system (400a) further comprises a MPLS network (406) that provides connectivity between a first IP network and a second network. Furthermore, the autonomous system (400a) comprises charging/provisioning unit (408) configured to provide the subscription/service charging/provisioning features such as for example, Quota management (UL), Quota management (PAYU), balance management, product management, and provisioning.
[0071] Unlike the conventional autonomous system (400a), the proposed autonomous system (400b) deploys an edge-dPCRF (410) that now incorporates the Quota management and product management of the charging/provisioning unit (408). Thus, by virtue of this, FUP (Fair Usage Policy) with Lower Speed and UL Quota can be supported to further reduce the Gy Traffic. Also, one place for all configuration across the circle-edge Nodes can be achieved in the proposed edge-dPCRF (410) along with dynamic slicing based on the RAT (Radio Access Technology), Time Location etc., to reduce TPS spike. Also, no IMSI based routing mechanism is required at GGSN/ PGW and provisioning system. That is, a webscale cloud native PCRF and SPR is provided. The dPCC engine (230) is configured to adapt existing API signatures of existing provisioning system to make sure no changes in existing APIs.
[0072] For example, the dPCC engine (230) (may also be referred as, for example, the dPCRF engine (410) takes over the Quota-Management (for Unlimited or Non-monetary Quota), which can be moved at the edge and only the Monetary usage (usage that is to be charged: Rs 0.2per MB), is to be sent to the OCS in the central site (210). The product management functionality is needed to manage multiple subscriptions for a single subscriber. For example: if a user is having 1Base-Plan (Data-Usage: Rs0.2 per MB), One Add-On (1.5GB free per day). Then how to decide, which usage to be used first.
[0073] A sample deployment overview of FIG. 4b is illustrated in FIG. 5, where the dPCC engine (230) communicates with multiple SPR databases (104a-c) and are separately located from the central site (210). Thus, processing all the non-charging transactions/traffic is at the edge-dPCC nodes (102a-c) (e.g., the edge PCRF node) and sending only charging related transactions at the central site (210) for billing purposes.
[0074] Thus, the present disclosure reduces the processing load at the OCS (i.e., central site (210)) (e.g., 10%), saving the network resources significantly. Also, the method does not require redundancy of subscriber data at multiple SPR databases (104a-c), as each edge-dPCC node (102a-c) has access to all the SPR databases (104). Further, the present disclosure results in reduction of Gy TPS by e.g., 60%, reduction provisioning TPS by e.g., 50%, as single subscriber provisioning in the SPR and no Sy is required.
[0075] In the case of non-home Subscriber, the dPCC does not forward the request to another dPCC (a shown in FIG. 6a, conventional). Instead of that basis on distribution rule defined in the DDF unit (246), it will fetch subscriber profile only from respected SPR database (104a-c) and process locally on the received node (shown in FIG.6b). That is, referring to FIG. 6b, each application executed at each of the edge-dPCC node (102a-c) incorporates the DDF functionality (as detailed in FIG. 3). Thus, it is by virtue of the DDF functionality, that each application of the edge-dPCC node (102a) has direct access to a plurality of other subscriber profile databases (of Apps) i.e., SPR databases (104b/c) executed at the edge-dPCC node (102b) or edge-dPCC node (102c). Unlike conventional mechanisms, as shown in FIG. 6a, where in order to transmit the plurality subscriber profile executed at the edge-dPCC node (102a) to the edge-dPCC node (102b) or edge-dPCC node (102c), the edge-dPCCab node (102a) transmits the data associated with the subscriber profile to the SPR database (102b/c) of each Apps (at the edge-dPCC node (102b) or edge-dPCC node (102c)) and then forwards to the respective Apps at the edge-dPCC node (102b) or edge-dPCC node (102c), thereby creating data replication.
[0076] Hence, to overcome the data replication and further to enhance the policy charging mechanisms, the present disclosure allows the edge-dPCC node (102a) to directly transmit the data associated with the subscriber profile to the respective Apps executed at the edge-dPCC node (102b) or edge-dPCC node (102c) by leveraging the DDF functionality at both the edge-dPCC node (102a) and the edge-dPCC node (102b) or edge-dPCC node (102c)) (as shown in FIG. 6b).
[0077] FIG. 7 is a flowchart diagram illustrating a method (700) for edge-based policy charging control deployment in a communications network.
[0078] At step 702, the method includes providing the first dPCC instance, an access to the first subscriber profile database associated with the first dPCC instance.
[0079] At step 704, the method includes providing the first dPCC instance, the direct access to the plurality of subscriber profile databases corresponding to each of the plurality of the dPCC instances in the architecture.
[0080] The various actions, acts, blocks, steps, or the like in the flow diagram may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some of the actions, acts, blocks, steps, or the like may be omitted, added, modified, skipped, or the like without departing from the scope of the invention.
[0081] The embodiments disclosed herein can be implemented using at least one software program running on at least one hardware device and performing network management functions to control the elements.
[0082] It will be apparent to those skilled in the art that other embodiments of the invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention. While the foregoing written description of the invention enables one of ordinary skill to make and use what is considered presently to be the best mode thereof, those of ordinary skill will understand and appreciate the existence of variations, combinations, and equivalents of the specific embodiment, method, and examples herein. The invention should therefore not be limited by the above described embodiment, method, and examples, but by all embodiments and methods within the scope of the invention. It is intended that the specification and examples be considered as exemplary, with the true scope of the invention being indicated by the claims.
[0083] The methods and processes described herein may have fewer or additional steps or states and the steps or states may be performed in a different order. Not all steps or states need to be reached. The methods and processes described herein may be embodied in, and fully or partially automated via, software code modules executed by one or more general purpose computers. The code modules may be stored in any type of computer-readable medium or other computer storage device. Some or all the methods may alternatively be embodied in whole or in part in specialized computer hardware.
[0084] The results of the disclosed methods may be stored in any type of computer data repository, such as relational databases and flat file systems that use volatile and/or non-volatile memory (e.g., magnetic disk storage, optical storage, EEPROM and/or solid-state RAM).
[0085] The various illustrative logical blocks, modules, routines, and algorithm steps described in connection with the embodiments disclosed herein can be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. The described functionality can be implemented in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the disclosure.
[0086] Moreover, the various illustrative logical blocks and modules described in connection with the embodiments disclosed herein can be implemented or performed by a machine, such as a general purpose processor device, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components or any combination thereof designed to perform the functions described herein. A general purpose processor device can be a microprocessor, but in the alternative, the processor device can be a controller, microcontroller, or state machine, combinations of the same, or the like. A processor device can include electrical circuitry configured to process computer-executable instructions. In another embodiment, a processor device includes an FPGA or other programmable device that performs logic operations without processing computer-executable instructions. A processor device can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. Although described herein primarily with respect to digital technology, a processor device may also include primarily analog components. A computing environment can include any type of computer system, including, but not limited to, a computer system based on a microprocessor, a mainframe computer, a digital signal processor, a portable computing device, a device controller, or a computational engine within an appliance, to name a few.
[0087] The elements of a method, process, routine, or algorithm described in connection with the embodiments disclosed herein can be embodied directly in hardware, in a software module executed by a processor device, or in a combination of the two. A software module can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of a non-transitory computer-readable storage medium. An exemplary storage medium can be coupled to the processor device such that the processor device can read information from, and write information to, the storage medium. In the alternative, the storage medium can be integral to the processor device. The processor device and the storage medium can reside in an ASIC. The ASIC can reside in a user terminal. In the alternative, the processor device and the storage medium can reside as discrete components in a user terminal.
[0088] Conditional language used herein, such as, among others, "can," "may," "might," "may," “e.g.,” and the like, unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain alternatives include, while other alternatives do not include, certain features, elements and/or steps. Thus, such conditional language is not generally intended to imply that features, elements and/or steps are in any way required for one or more alternatives or that one or more alternatives necessarily include logic for deciding, with or without other input or prompting, whether these features, elements and/or steps are included or are to be performed in any particular alternative. The terms “comprising,” “including,” “having,” and the like are synonymous and are used inclusively, in an open-ended fashion, and do not exclude additional elements, features, acts, operations, and so forth. Also, the term “or” is used in its inclusive sense (and not in its exclusive sense) so that when used, for example, to connect a list of elements, the term “or” means one, some, or all of the elements in the list.
[0089] Disjunctive language such as the phrase “at least one of X, Y, Z,” unless specifically stated otherwise, is otherwise understood with the context as used in general to present that an item, term, etc., may be either X, Y, or Z, or any combination thereof (e.g., X, Y, and/or Z). Thus, such disjunctive language is not generally intended to, and should not, imply that certain alternatives require at least one of X, at least one of Y, or at least one of Z to each be present.
[0090] While the detailed description has shown, described, and pointed out novel features as applied to various alternatives, it can be understood that various omissions, substitutions, and changes in the form and details of the devices or algorithms illustrated can be made without departing from the scope of the disclosure. As can be recognized, certain alternatives described herein can be embodied within a form that does not provide all of the features and benefits set forth herein, as some features can be used or practiced separately from others.

CLAIMS:CLAIMS

We Claim:

1. A method for deploying a plurality of policy charging control (dPCC) instances on a plurality of edge nodes (102a-e) in an online charging system, each of the plurality of dPCC instances is associated with a subscriber profile database, each of the plurality of dPCC instances are connected to a central site (210) in the online charging system, the online charging system is configured to charge one or more users for using one or more services, the method comprising:
providing a first dPCC instance, an access, by a dPCC engine (230), to a first subscriber profile database (104a) associated with the first dPCC instance; and
providing the first dPCC instance, a direct access, by the dPCC engine (230), to a plurality of subscriber profile databases (104-c) corresponding to each of the plurality of dPCC instances in the architecture.

2. The method as claimed in claim 1, wherein the direct access further comprising:
providing one or more applications running at each of the dPCC instances, the direct access to the plurality of subscriber profile databases corresponding to the plurality of dPCC instances, other than the first dPCC instance.

3. The method as claimed in claim 1, further comprising:
maintaining a single storage of each of a plurality of user profiles in the subscriber profile database associated with each of the plurality of dPCC instances.

4. The method as claimed in claim 1, further comprising:
charging each of the one or more users, for the one or more services consumed by each of the one or more users, the one or more users corresponding to a single or multiple service providers.
5. The method as claimed in claim 1, further comprising:
processing a first traffic type at the plurality of dPCC instances, the first traffic type corresponds to a non-charging traffic, wherein the non-charging traffic is independent of charging performed by the online charging system.

6. The method as claimed in claim 1, further comprising:
transmitting a second traffic type to the central site in the online charging system, the second traffic type corresponds to a charging traffic, wherein the charging traffic is required to be processed for charging the one or more users for using the one or more services.

7. The method as claimed in claim 1, further comprising:
defining a distribution rule to distribute the one or more users in the subscriber profile database associated with each of the plurality of dPCC instances.

8. The method as claimed in claim 1, further comprising:
defining a distribution rule to distribute the one or more users in the subscriber profile database associated with each of the plurality of dPCC instances; and
fetching a user profile from a subscriber profile database associated with one of the plurality of dPCC instances, based on the defined distribution rule.

9. The method as claimed in claim 1, further comprising:
defining a distribution rule to distribute the one or more users in the subscriber profile database associated with each of the plurality of dPCC instances;
fetching a user profile from a subscriber profile database associated with one of the plurality of dPCC instance, based on the defined distribution rule; and
processing a charging request associated with the fetched user profile, requested by the first dPCC instance, locally on the one of the plurality of dPCC instance associated with the fetched user profile.

10. The method as claimed in claim 1, wherein the plurality of dPCC instances receives one or more charging request from multiple vendors in the online charging system, the online charging system comprising one or more sub-charging system, each sub-charging system corresponding to each of the multiple vendors.

11. A system (200) for deploying a plurality of policy charging control (dPCC) instances on a plurality of edge nodes (102a-e) in an online charging system, each of the plurality of dPCC instances is associated with a subscriber profile database (104), each of the plurality of dPCC instances are connected to a central site (210) in the online charging system, the online charging system is configured to charge one or more users for using one or more services, the system (200) comprising:
a dPCC engine (230) configured to:
provide a first dPCC instance, an access to a first subscriber profile database associated with the first dPCC instance, and
provide the first dPCC instance, a direct access to a plurality of subscriber profile databases (104a-c) corresponding to each of the plurality of dPCC instances in the architecture.

12. The system (200) as claimed in claim 11, wherein the dPCC engine is further configured to:
provide one or more applications running at each of the dPCC instances, the direct access to the plurality of subscriber profile databases corresponding to the plurality of dPCC instances, other than the first dPCC instance.

13. The system (200) as claimed in claim 11, wherein the subscriber profile database (104) is configured to maintain a single storage of each of a plurality of user profiles associated with each of the plurality of dPCC instances.

14. The system (200) as claimed in claim 11, wherein the dPCC engine (230) is further configured to:
charge each of the one or more users, for the one or more services consumed by each of the one or more users, the one or more users corresponding to one or more service provider.

15. The system (200) as claimed in claim 11, wherein the dPCC engine (230) is further configured to:
process a first traffic type at the plurality of dPCC instances, the first traffic type corresponds to a non-charging traffic, wherein the non-charging traffic is independent of charging performed by the online charging system.

16. The system (200) as claimed in claim 11, wherein the dPCC engine (230) is further configured to:
transmit a second traffic type to the central site in the online charging system, the second traffic type corresponds to a charging traffic, wherein the charging traffic is required to be processed for charging the one or more users for using the one or more services.

17. The system (200) as claimed in claim 11, further comprising:
a data distribution function (DDF) unit (246) configured to define a distribution rule to distribute the one or more users in the subscriber profile database associated with each of the plurality of dPCC instances.

18. The system (200) as claimed in claim 11, further comprising:
a DDF unit (246) configured to:
define a distribution rule to distribute the one or more users in the subscriber profile database associated with each of the plurality of dPCC instances; and
fetch a user profile from a subscriber profile database associated with one of the plurality of dPCC instances, based on the defined distribution rule.

19. The system (200) as claimed in claim 11, further comprising:
a DDF unit (246) configured to:
define a distribution rule to distribute the one or more users in the subscriber profile database associated with each of the plurality of dPCC instances;
fetch a user profile from a subscriber profile database associated with one of the plurality of dPCC instance, based on the defined distribution rule; and
process a charging request associated with the fetched user profile, requested by the first dPCC instance, locally on the one of the plurality of dPCC instance associated with the fetched user profile.

20. The system (200) as claimed in claim 11, wherein the plurality of dPCC instances receives one or more charging request from multiple vendors in the online charging system, the online charging system comprising one or more sub-charging system, each sub-charging system corresponding to each of the multiple vendors.