System and method for synchronization of an EPC plan using BI-directional workflow

Abstract

Disclosed is a method of synchronization of an Enterprise Product Catalog (EPC) incremental / full plan using bi-directional workflow. The method includes sending, 5 by a Provisioning Gateway (PGW) (120), an initialization request to a Fulfillment Management System (FMS) (110) for synchronization of the EPC plan into a plurality of databases. The method further includes receiving, by the PGW (120), data associated with the synchronization of the EPC plan from the FMS (110), wherein the FMS (110) fetches the data from an EPC node based on the request. 10 Further, the method includes performing, by the PGW (120) upon reception of the data associated with the synchronization of the EPC plan, the synchronization of the EPC plan in the plurality of databases.

Description

SYSTEM AND METHOD FOR SYNCHRONIZATION OF AN EPC PLAN USING BI-DIRECTIONAL WORKFLOW TECHNICAL FIELD

[0001] The embodiments of the present disclosure generally relate to the field of communication networks. More particularly, the present disclosure relates to a system and a method for synchronization of an Enterprise Product Catalog (EPC) plan using bi-directional workflow.BACKGROUND OF THE INVENTION

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

[0003] In modern communication network, effective synchronization of Enterprise Product Catalog (EPC) plans in different systems is essential for seamless operation. One of a crucial aspect of the synchronization is a process of transferring data associated with the EPC plan across the network.

[0004] In conventional systems, the EPC plan synchronization is typically a unidirectional workflow, where the synchronization process is fully controlled by an Enterprise Product Catalog (EPC) node. The EPC node control all the synchronization process ensuring alignment of EPC plan data in all the systems, for e.g., different database systems, across the network.

[0005] However, the EPC plan synchronization requires involvement of multiple teams at different stages of the synchronization process. The teams are responsible for configuring, managing, and monitoring the systems that handles EPC plans, including EPC node. The need of manual collaboration of the multiple teams increases the complexity and duration of synchronization process and can lead toineffectiveness and delays in ensuring that the EPC plans are effectively synchronized across entire network.

[0006] In light of the aforementioned challenges, there is a need for an improved system and method for synchronizing EPC plan effectively across a plurality of databases.SUMMARY

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

[0008] In an embodiment, a method for synchronization of an Enterprise Product Catalog (EPC) plan using bi-directional workflow is disclosed. The method includes sending, by a Provisioning Gateway (PGW), an initialization request to a Fulfillment Management System (FMS) for synchronization of the EPC plan into a plurality of databases. The method further includes receiving, by the PGW upon sending the initialization request, data associated with the synchronization of the EPC plan from the FMS. The FMS fetches the data from an EPC node based on the request. Further, the method includes performing, by the PGW upon reception of the data associated with the synchronization of the EPC plan, the synchronization of the EPC plan in the plurality of databases.

[0009] According to some aspect of the present disclosure, the method further includes receiving, by the PGW, a first success response from the FMS upon reception of the initialization request at the FMS. Further, the method includes receiving, by the PGW, a plan sync request from the FMS for synchronization of the EPC plan in the plurality of databases. The plan sync request includes the data associated with the synchronization of the EPC plan. Furthermore, the methodincludes sending, by the PGW, a second success response to the FMS upon reception of the plan sync request.

[0010] According to some aspect of the present disclosure, performing the synchronization of the EPC plan in the plurality of databases comprises updating all tables in each of the plurality of databases based on the received data.

[0011] According to some aspect of the present disclosure, the plurality of databases includes at least one local database and at least one secondary database.

[0012] According to some aspect of the present disclosure, the method further includes receiving, by the PGW from each database of the plurality of databases, a success response on successful synchronization of the EPC plan in a corresponding database among the plurality of databases.

[0013] In another embodiment, a method for synchronization of an Enterprise Product Catalog (EPC) plan using bi-directional workflow is disclosed. The method includes receiving, by a Fulfillment Management System (FMS), a initialization request from a Provisioning Gateway (PGW) for synchronization of the EPC plan into a plurality of databases. Further, the method includes initiating, by the FMS upon receiving the initialization request, a call to an EPC node to fetch data associated with the synchronization of the EPC plan from an EPC node and sending a first success response to the PGW upon initiating the call. Furthermore, the method includes sending, by the FMS, a plan sync request to the PGW. The plan sync request includes the data associated with synchronization of the EPC plan into the plurality of databases.

[0014] According to some aspect of the present disclosure, the method further includes receiving, by the FMS, a second success response upon reception of the plan sync request.

[0015] In another embodiment, a system for synchronization of an Enterprise Product Catalog (EPC) plan using bi-directional workflow is disclosed. The systemincludes a Provisioning Gateway (PGW) configured to send an initialization request to a Fulfillment Management System (FMS) for synchronization of the EPC plan into a plurality of databases. The PGW is further configured to receive, upon sending the initialization request, data associated with the synchronization of the EPC plan from the FMS. The FMS fetches the data from an EPC node based on the request. Further, the PGW is configured to perform, upon reception of the data associated with the synchronization of the EPC plan, the synchronization of the EPC plan in the plurality of databases.

[0016] In another embodiment, a system for synchronization of an Enterprise Product Catalog (EPC) plan using bi-directional workflow is disclosed. The system includes a Fulfillment Management System (FMS) configured to receive a initialization request from a Provisioning Gateway (PGW) for synchronization of the EPC plan into a plurality of databases. The FMS is further configured to initiate, upon receiving the initialization request, a call to an EPC node to fetch data associated with the synchronization of the EPC plan from an EPC node and sending a first success response to the PGW upon initiating the call. Further, the FMS is configured to send a plan sync request to the PGW. The plan sync request includes the data associated with synchronization of the EPC plan into the plurality of databases.BRIEF DESCRIPTION OF DRAWINGS

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

[0018] FIG. 1 illustrates a block diagram of a Provisioning Gateway Charging Function (ProvGW-CHF) system, in accordance with one or more embodiments of the present disclosure.

[0019] FIG. 2 illustrates a functional block diagram of the ProvGW-CHF system, in accordance with one or more embodiments of the present disclosure.

[0020] FIG. 3 illustrates a flow diagram of a method of synchronization of Enterprise Product Catalog (EPC) incremental / full plan using bi-directional workflow, in accordance with the one or more embodiments of the present disclosure.

[0021] FIG. 4 illustrates a flow diagram of a method performed by a Provisioning Gateway (PGW) of the ProvGW-CHF system for synchronization of the EPC plan using bi-directional workflow, in accordance with the one or more embodiments of the present disclosure.

[0022] FIG. 5 illustrates a flow diagram of a method performed by a Fulfillment Management System (FMS) node of the ProvGW-CHF system for synchronization of the EPC plan using bi-directional workflow, in accordance with the one or more embodiments of the present disclosure.DETAILED DESCRIPTION OF THE INVENTION

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

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

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

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

[0027] 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.

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

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

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

[0031] An object of the present disclosure is to provide a system and a method for on-demand plan synchronization for synchronizing one of Enterprise Product Catalog (EPC) incremental plan or full plan in different databases across a network.

[0032] Another object of the present disclosure is to provide the system including a Provisioning Gateway (PGW) and a Fulfillment Management System (FMS). The PGW initiates a call for the on-demand plan synchronization to a Fulfillment Management System (FMS). The FMS fetches data associated with the on-demand plan synchronization from an EPC node.

[0033] Another object of the present disclosure is to provide the system and the method for synchronization of the EPC incremental / full plan using bi-directional workflow which removes a dependency on the EPC node to initiate a synchronization of the EPC plan.

[0034] The term “EPC node” in the entire disclosure may refer to a central node or component that manages all product, services, offers, and pricing plans across the system. The EPC node stores definition of all tariffs and services into different databases across the system.

[0035] In the entire disclosure, the EPC incremental plan corresponds to a newly added tariff plan. The synchronization of the EPC incremental plan corresponds to synchronization of data associated with the newly added tariff plan in different databases. Also, synchronization of the EPC full plan corresponds to synchronization of the data associated with all tariff plans in different databases across the network.

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

[0037] FIG. 1 illustrates a block diagram of a Provisioning Gateway Charging Function (ProvGW-CHF) system 100, in accordance with one or more embodimentsof the present disclosure. The ProvGW-CHF system 100 (may also be referred to as “system 100”) is used for subscriber provisioning in communication systems and synchronization of the EPC plans in different databases of the ProvGW-CHF system 100. The subscriber provisioning in communication system may corresponds to subscriber provisioning for one of Fixed Wireless Access (FWA), Outdoor Consumer Premise Equipment (ODCPE), or indoor CPE.

[0038] The ProvGW-CHF system 100 includes the FMS 110, the PGW 120, a local Database (DB) 130, and a secondary Database (DB) 140.

[0039] The FMS 110 is connected between the PGW 120 and the EPC node (not shown in figure). The FMS 110 acts as an ingress node which receives a request from the PGW 120 for initializing synchronization of the EPC plan. Further, the FMS 110 also fetches data associated with the synchronization of the EPC plan from the EPC node upon receiving the request from the PGW 120.

[0040] The PGW 120 handles provisioning data for a plurality of users associated with the plurality of user devices. The provisioning data may include data for subscriber provision and the data associated with the EPC plan synchronization. For instance, the PGW 120 receives the data associated with the synchronization of the EPC plan from the FMS 110 and stores the data into different databases (For example database 1 and database 2) in the network.

[0041] For instance, the PGW 120 may be a primary PGW at location 1 or a secondary PGW at location 2. Each of the primary PGW and the secondary PGW is connected with the local database (for example, database 1) 130 and the secondary database (for example, database 2) 140 at the respective location. In an embodiment, the local database 130 may also be referred to as “primary database”. Further, the secondary database 140 may also be referred to as “Geo database” or “spare database”.

[0042] Further, the network may include a proprietary Internet Protocol (IP) network, Internet, or other data network. The network may include suitable logic, circuitry, and interfaces that may be configured to provide several network ports andseveral communication channels for transmission and reception of data related to operations of various entities of the network.

[0043] In one or more embodiments, if the primary PGW at location 1 gets down then there will be no outage at the location 1 as the request may be routed via secondary PGW at location 2. In this case, the information will be updated in the databases at the location 2.

[0044] For any new plan to be onboarded on the ProvGW-CHF system 100, the EPC node need to synchronize the new plan into the different databases (database 1 and database 2) of the ProvGW-CHF system 100. In the available methods, the network operators wait for the EPC node to initiate the synchronization of the EPC plan. However, the present disclosure discloses a method 200 where the network operators can initiate a request for the synchronization of the EPC plan. Therefore, the dependency of EPC node to synchronize the EPC plans may be removed using the disclosed method 300 as shown in FIG. 3.

[0045] FIG. 2 illustrates a functional block diagram 200 of the ProvGW-CHF system 100, in accordance with one or more embodiments of the present disclosure. The functional block diagram 200 of the ProvGW-CHF system 100 includes the FMS 110, the PGW 120, a local DB 130, and a secondary DB 140. The FMS 110 may include a processor 202, a memory 204, a communication unit 206, and one or more processing modules 208 (hereinafter may be referred to as “processing modules 208”). The processing modules 208 may include a receiving module 210, a transmitting module 212, and a data extraction module 214.

[0046] The one or more components of the FMS 110 are communicatively coupled with the processor 202 (described below) to perform operations for synchronization of the EPC plan using bi-directional workflow. The processor 202 may include various processing circuitry and configured to execute programs or computer readable instructions stored in the memory 204. The processor 202 may also include an intelligent hardware device including a general-purpose processor, such as, for example, and without limitation, a Central Processing Unit (CPU), an ApplicationProcessor (AP), a dedicated processor, or the like, a microcontroller, a Field-Programmable Gate Array (FPGA), a programmable logic device, a discrete hardware component, or any combination thereof. In some cases, the processor 202 may be configured to operate a memory array using a memory controller. In some cases, a memory controller may be integrated into the processor 202. The processor 202 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 204) to cause the FMS 110 to perform various functions.

[0047] The memory 204 is communicatively coupled to the processor 202. A part of the memory 204 may include a RAM, and another part of the memory 204 may include a flash memory or other ROM. The memory 204 is configured to store a set of instructions required by the processor 202 for controlling overall operations of the FMS 110. The memory 204 may include non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. In addition, the memory 204 may, in some examples, be considered a non-transitory storage medium. The "non-transitory" storage medium is not embodied in a carrier wave or a propagated signal. However, the term "non-transitory" should not be interpreted that the memory 204 is non-movable. In some examples, the memory 204 can be configured to store larger amounts of information. In certain examples, a non-transitory storage medium may store data that can, over time, change (e.g., in Random Access Memory (RAM) or cache). The memory 204 can be an internal storage unit or it can be an external storage unit of the FMS 110, cloud storage, or any other type of external storage.

[0048] More specifically, the memory 204 may store computer-readable instructions including instructions that, when executed by a processor (e.g., the processor 202) cause the FMS 110 to perform various functions described herein. In some cases, the memory 204 may contain, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices.

[0049] The communication unit 206 includes an electronic circuit specific to a standard that enables wired or wireless communication. The communication unit 206 is configured to communicate internally between internal hardware components and with external devices via one or more networks. The communication unit 206 may be configured to enable the FMS 110 to communicate with various entities of the system 100 (such as the PGW 120 and network nodes including EPC node) through backhaul connection (e.g. wired backhaul or wireless backhaul) or a network. Examples of the communication unit 206 may include, but are not limited to, a modem, a network interface such as an Ethernet card, a communication port, and / or a Personal Computer Memory Card International Association (PCMCIA) slot and card, an antenna, a radio frequency (RF) transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a coder-decoder (CODEC) chipset, a subscriber identity module (SIM) card, and a local buffer circuit. It will be apparent to a person of ordinary skill in the art that the communication unit 206 may include any device and / or apparatus capable of providing wireless or wired communications between the FMS 110 and various other entities of the system 100.

[0050] In one or more embodiments, the processing module(s) 208 may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the FMS 110. In non-limiting examples, described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processing modules(s) 208 may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processor 202 may comprise 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 module(s) 208. In such examples, the FMS 110 may also comprise the machine-readable storage medium storing the instructions and the processing resource to execute the instructions, orthe machine-readable storage medium may be separate but accessible to the FMS 110 and the processing resource. In other examples, the processing module(s) 208 may be implemented using an electronic circuitry.

[0051] In one or more embodiments, the receiving module 210 may receive an initialization request from the PGW 120 for synchronization of the EPC plan into the plurality of databases. The plurality of databases includes at least one local database 130 and at least one secondary database 140.

[0052] Further, the transmitting module 212 may transmit a call message to the EPC node. The call message triggers the synchronization of the EPC plan from the EPC node. The data extraction module 214 may extract or fetch data associated with the synchronization of the EPC plan from the EPC node upon transmission of the call message.

[0053] The transmitting module 212 may further configured to send a success response to the PGW 120 upon transmitting the call to the EPC node. The transmitting module 212 may then send a plan sync request to the PGW 120 which includes the data associated with synchronization of the EPC plan into the plurality of databases.

[0054] In one or more embodiments, the PGW 120 may include a processor 216, a memory 218, a communication unit 220, an interface 222, and one or more processing modules 224 (hereinafter may be referred to as “processing modules 224”). The processing modules 224 may include a receiving module 226, a transmitting module 228, and a data management module 230.

[0055] The one or more components of the PGW 120 are communicatively coupled with the processor 216 (described below) to perform operations for synchronization of the EPC plan using bi-directional workflow.

[0056] The processor 216 may include various processing circuitry and configured to execute programs or computer readable instructions stored in the memory 218. The processor 216 may also include an intelligent hardware device including ageneral-purpose processor, such as, for example, and without limitation, a Central Processing Unit (CPU), an Application Processor (AP), a dedicated processor, or the like, a microcontroller, a Field-Programmable Gate Array (FPGA), a programmable logic device, a discrete hardware component, or any combination thereof. In some cases, the processor 216 may be configured to operate a memory array using a memory controller. In some cases, a memory controller may be integrated into the processor 216. The processor 216 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 218) to cause the PGW 120 to perform various functions.

[0057] The memory 218 is communicatively coupled to the processor 216. A part of the memory 218 may include a RAM, and another part of the memory 218 may include a flash memory or other ROM. The memory 218 is configured to store a set of instructions required by the processor 216 for controlling overall operations of the PGW 110. The memory 218 may include non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. In addition, the memory 218 may, in some examples, be considered a non-transitory storage medium. The "non-transitory" storage medium is not embodied in a carrier wave or a propagated signal. However, the term "non-transitory" should not be interpreted that the memory 218 is non-movable. In some examples, the memory 218 can be configured to store larger amounts of information. In certain examples, a non-transitory storage medium may store data that can, over time, change (e.g., in Random Access Memory (RAM) or cache). The memory 218 can be an internal storage unit or it can be an external storage unit of the PGW 120, cloud storage, or any other type of external storage.

[0058] More specifically, the memory 218 may store computer-readable instructions including instructions that, when executed by a processor (e.g., the processor 216) cause the PGW 120 to perform various functions described herein. In some cases, the memory 218 may contain, among other things, a BIOS whichmay control basic hardware or software operation such as the interaction with peripheral components or devices.

[0059] The communication unit 220 includes an electronic circuit specific to a standard that enables wired or wireless communication. The communication unit 220 is configured to communicate internally between internal hardware components and with external devices via one or more networks. The communication unit 220 may be configured to enable the PGW 120 to communicate with various entities of the system 100 (such as the FMS 110 and a plurality of databases) through backhaul connection (e.g. wired backhaul or wireless backhaul) or a network. Examples of the communication unit 220 may include, but are not limited to, a modem, a network interface such as an Ethernet card, a communication port, and / or a Personal Computer Memory Card International Association (PCMCIA) slot and card, an antenna, a radio frequency (RF) transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a coder-decoder (CODEC) chipset, a subscriber identity module (SIM) card, and a local buffer circuit. It will be apparent to a person of ordinary skill in the art that the communication unit 220 may include any device and / or apparatus capable of providing wireless or wired communications between the PGW 120 and various other entities of the system 100.

[0060] The interface 222 may include suitable logic, circuitry, a variety of interfaces, and / or codes that may be configured to receive input(s) for initializing a request for synchronization of the EPC plan into the plurality of databases. The variety of interfaces may include interfaces for data input and output devices, referred to as VO devices, storage devices, and the like. For example, the VO interface may have an input interface and an output interface. The interface 222 may facilitate communication of the PGW 120 with various devices and systems connected to it. The interface 222 may also provide a communication pathway for one or more components of the PGW 120. Examples of such components include, but are not limited to, the processing module(s) 224.

[0061] In one or more embodiments, the processing module(s) 224 may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the PGW 120. In non-limiting examples, described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processing modules(s) 224 may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processor 216 may comprise 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 module(s) 224. In such examples, the PGW 120 may also comprise 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 PGW 120 and the processing resource. In other examples, the processing module(s) 224 may be implemented using an electronic circuitry.

[0062] In one or more embodiments, the receiving module 226 may receive a user input via the interface 222 to generate the initialization request. The transmitting module 228 may then send the initialization request to the FMS 110 for synchronization of the EPC plan into the plurality of databases.

[0063] The receiving module 226 may further receive the success response from the FMS upon reception of the initialization request at the FMS 110. The receiving module 226 may further receive the plan sync request from the FMS 110 for synchronization of the EPC plan in the plurality of databases. The plan sync request includes the data associated with the synchronization of the EPC plan. The transmitting module 228 may then send a success response to the FMS 110 upon reception of the plan sync request.

[0064] Further, the data management module 230 may perform the synchronization of the EPC plan in the plurality of databases upon reception of the plan sync request. For instance, performing the synchronization of the EPC plan in the plurality ofdatabases comprises updating all tables in each of the plurality of databases based on the received data.

[0065] Thereafter, the receiving module 226 may receive from each database of the plurality of databases, a success response on successful synchronization of the EPC plan in a corresponding database among the plurality of databases.

[0066] FIG. 3 illustrates a flow diagram of the method 300 of synchronization of the EPC incremental / full plan using bi-directional workflow, in accordance with the one or more embodiments of the present disclosure. The method includes a series of steps from step 1 to step 8 performed by the system 100.

[0067] At step 1, the PGW 120 sends a request for synchronization of the EPC plan to the FMS 110. The request may be for synchronization of EPC incremental plan or full plan. The synchronization of the EPC incremental plan corresponds synchronizing the newly added tariff plan in different databases. Also, synchronization of the EPC full plan corresponds synchronizing all tariff plans in different databases across the network. Different databases may include the local database 130 and the secondary database 140.

[0068] In one or more embodiment, the request may be initiated from an operational interface that includes one of a web-based interface or a command line interface.

[0069] At step 2, the FMS 110 initiates a call to the EPC node and sends a response to the PGW 120 upon successfully initiating the call to the EPC node. For instance, upon receiving the request, the FMS 110 may trigger the EPC node to start the EPC plan synchronization.

[0070] At step 3, the FMS 110 receives a plan sync from the EPC node and send the request for the EPC plan synchronization to the PGW 120.

[0071] At step 4, the PGW 120 triggers the synchronization of the EPC plan and sends a response to the FMS 110.

[0072] At step 5, the PGW 120 performs synchronization of the EPC plan in the local database 130. The MU-PGW 120 performs the synchronization of the EPC plan in the local database 130 by updating all tables in the local database 130.

[0073] At step 6, the PGW 120 receives a response from the local database 130 on successful synchronization of the EPC incremental plan in the local database 130.

[0074] At step 7, the PGW 120 performs the synchronization of the EPC incremental plan in the secondary database 140 by updating all the tables in the secondary database 140.

[0075] At step 8, the PGW 120 receives a response from the secondary database 140 on successful synchronization of the EPC incremental plan in the secondary database 140.

[0076] FIG. 4 illustrates a flow diagram of a method performed by the PGW 120 of the ProvGW-CHF system 100 for synchronization of the EPC plan using bidirectional workflow, in accordance with the one or more embodiments of the present disclosure. The method 400 comprises a series of operation steps indicated by blocks 402 through 412. The method 400 starts at block 402.

[0077] At block 402, the PGW 120 may send the initialization request to the FMS 110 for synchronization of the EPC plan into the plurality of databases including at least one local database (for example, database 130) and at least one secondary database (for example, database 140). The synchronization of the EPC plan may correspond to synchronization of the newly added tariff plan or all the tariff plans in different databases across the network.

[0078] At block 404, the PGW 120 may receive a first success response from the FMS 110 upon reception of the initialization request at the FMS 110. The FMS 110 sends the first success response after forwarding the initialization request to the EPC node.

[0079] At block 406, the PGW 120 may receive the plan sync request from the FMS 110 for synchronization of the EPC plan in the plurality of databases. The plan sync request includes the data associated with the synchronization of the EPC plan. The FMS 110 fetches the data associated with the plan sync request from the EPC node based on the initialization request.

[0080] At block 408, the PGW 120 may send a second success response to the FMS 110 upon reception of the plan sync request.

[0081] At block 410, the PGW 120 may perform the synchronization of the EPC plan in the plurality of databases. For instance, performing the synchronization of the EPC plan in the plurality of databases comprises updating all tables in each of the plurality of databases based on the data associated with the plan sync request.

[0082] At block 412, the PGW 120 may receive, from each database of the plurality of databases, the success response on successful synchronization of the EPC plan in a corresponding database among the plurality of databases.

[0083] FIG. 5 illustrates a flow diagram of a method performed by the FMS node 110 of the ProvGW-CHF system 100 for synchronization of the EPC plan using bidirectional workflow, in accordance with the one or more embodiments of the present disclosure. The method 500 comprises a series of operation steps indicated by blocks 502 through 510. The method 500 starts at block 502.

[0084] At block 502, the FMS (or FMS node) 110 may receive the initialization request from the PGW 120 for synchronization of the EPC plan into the plurality of databases.

[0085] At block 504, the FMS 110 may initiate, upon receiving the initialization request, the call to an EPC node to fetch data associated with the synchronization of the EPC plan from the EPC node

[0086] At block 506, the FMS 110 may send the first success response to the PGW 120 upon initiating the call.

[0087] At block 508, the FMS 110 may send the plan sync request to the PGW 120. The plan sync request includes the data associated with synchronization of the EPC plan into the plurality of databases.

[0088] At block 510, the FMS 110 may receive the second success response upon reception of the plan sync request.

[0089] Now, referring to the technical abilities and advantageous effect of the present disclosure, operational advantages that may be provided by embodiments disclosed herein may include enabling the provisioning gateway to initiate a request for the EPC plan synchronization thereby implementing the on-demand plan synchronization. The disclosed method also reduces complexity and wait duration of synchronization process by enabling the provisioning gateway to directly initiate the request of plan synchronization whenever required. Further, the disclosed method and system removes the of the EPC node and enables the on-demand provision for EPC plan synchronization.

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

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

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

[0093] The following list is provided for convenience and in support of the drawing figures and as part of the text of the specification, which describe innovations by reference to multiple items. Items not listed here may nonetheless be part of a given embodiment. For better legibility of the text, a given reference number is recited near some, but not all, recitations of the referenced item in the text. The same reference number may be used with reference to different examples or different instances of a given item. The list of reference numerals is:100 - Provisioning Gateway Charging Function (ProvGW-CHF) system 110 - Fulfillment Management System (FMS)120 - Provisioning Gateway (PGW)130 - Local Database (DB)140 - Secondary Database (DB)200 - Functional block diagram of the ProvGW-CHF system 100202 - Processor of the FMS 110204 - Memory of the FMS 110206 - Communication unit of the FMS 110208 - Processing modules of the FMS 110210 - Receiving module of the FMS 110212 - Transmitting module of the FMS 110214 - Data extraction module of the FMS 110216 - Processor of the PGW 120218 - Memory of the PGW 120220 - Communication unit of the PGW 120222- Interface224 - Processing modules of the PGW 120226 - Receiving module of the PGW 120228 - Transmitting module of the PGW 120230 - Data management module of the PGW 120300 - Flow diagram of method of synchronization of the EPC incremental / full plan400 - Method performed by the PGW 120 of the ProvGW-CHF system 100 402-412 - One or more steps of the method 400500 - Method performed by the FMS node 110 of the ProvGW-CHF system 100502-510 - One or more steps of the method 500

Claims

We claim:

1. A method (400) for synchronization of an Enterprise Product Catalog (EPC) plan using bi-directional workflow, the method (400) comprising:sending, by a Provisioning Gateway (PGW) (120), an initialization request to a Fulfillment Management System (FMS) (110) for synchronization of the EPC plan into a plurality of databases;receiving, by the PGW (120) upon sending the initialization request, data associated with the synchronization of the EPC plan from the FMS (110), wherein the FMS (110) fetches the data from an EPC node based on the request; andperforming, by the PGW (120) upon reception of the data associated with the synchronization of the EPC plan, the synchronization of the EPC plan in the plurality of databases.

2. The method (400) as claimed in claim 1, further comprising receiving, by the PGW (120), a first success response from the FMS (110) upon reception of the initialization request at the FMS (110);receiving, by the PGW (120), a plan sync request from the FMS (110) for synchronization of the EPC plan in the plurality of databases, wherein the plan sync request includes the data associated with the synchronization of the EPC plan; andsending, by the PGW (120), a second success response to the FMS (110) upon reception of the plan sync request.

3. The method (400) as claimed in claim 1, wherein performing the synchronization of the EPC plan in the plurality of databases comprises updating all tables in each of the plurality of databases based on the received data.

4. The method (400) as claimed in claim 1, wherein the plurality of databases includes at least one local database and at least one secondary database.

5. The method (400) as claimed in claim 1, further comprising receiving, by the PGW (120) from each database of the plurality of databases, a success response on successful synchronization of the EPC plan in a corresponding database among the plurality of databases.

6. A method (500) for synchronization of an Enterprise Product Catalog (EPC) plan using bi-directional workflow, the method (500) comprising: receiving, by a Fulfillment Management System (FMS) (110), an initialization request from a Provisioning Gateway (PGW) (120) for synchronization of the EPC plan into a plurality of databases;initiating, by the FMS (110) upon receiving the initialization request, a call to an EPC node to fetch data associated with the synchronization of the EPC plan from an EPC node and sending a first success response to the PGW (120) upon initiating the call; andsending, by the FMS (110), a plan sync request to the PGW (120), wherein the plan sync request includes the data associated with synchronization of the EPC plan into the plurality of databases.

7. The method (500) as claimed in claim 6, further comprising receiving, by the FMS (110), a second success response upon reception of the plan sync request.

8. The method (500) as claimed in claim 6, wherein the plurality of databases includes at least one local database and at least one secondary database.

9. A system (100) for synchronization of an Enterprise Product Catalog (EPC) plan using bi-directional workflow, the system (100) comprising: a Provisioning Gateway (PGW) (120) configured to:send an initialization request to a Fulfillment Management System (FMS) (110) for synchronization of the EPC plan into a plurality of databases;receive, upon sending the initialization request, data associated with the synchronization of the EPC plan from the FMS (110), wherein the FMS (110) fetches the data from an EPC node based on the request; andperform, upon reception of the data associated with the synchronization of the EPC plan, the synchronization of the EPC plan in the plurality of databases.

10. The system (100) as claimed in claim 9, wherein the PGW (120) is further configured to:receive a first success response from the FMS (110) upon reception of the initialization request at the FMS (110);receive a plan sync request from the FMS (110) for synchronization of the EPC plan in the plurality of databases, wherein the plan sync request includes the data associated with the synchronization of the EPC plan; and send a second success response to the FMS (110) upon reception of the plan sync request.

11. The system (100) as claimed in claim 9, wherein, to perform the synchronization of the EPC plan in the plurality of databases, the PGW (120) is configured to update all tables in each of the plurality of databases based on the received data.

12. The system (100) as claimed in claim 9, wherein the plurality of databases includes at least one local database and at least one secondary database.

13. The system (100) as claimed in claim 9, wherein the PGW (120) is further configured to receive, from each database of the plurality of databases, a success response on successful synchronization of the EPC plan in a corresponding database among the plurality of databases.

14. A system (100) for synchronization of an Enterprise Product Catalog (EPC) plan using bi-directional workflow, the system (100) comprising: a Fulfillment Management System (FMS) (110) configured to: receive an initialization request from a Provisioning Gateway (PGW) (120) for synchronization of the EPC plan into a plurality of databases;initiate, upon receiving the initialization request, a call to an EPC node to fetch data associated with the synchronization of the EPC plan from an EPC node and sending a first success response to the PGW (120) upon initiating the call; andsend a plan sync request to the PGW (120), wherein the plan sync request includes the data associated with synchronization of the EPC plan into the plurality of databases.

15. The system (100) as claimed in claim 14, wherein the FMS (110) is further configured to receive a second success response upon reception of the plan sync request.

16. A computer program product comprising computer-executable instructions that are stored on a non-transitory computer-readable medium and that, when executed by at least one processor performs operations comprising:sending, by a Provisioning Gateway (PGW) (120), an initialization request to a Fulfillment Management System (FMS) (110) for synchronization of an Enterprise Product Catalog (EPC) plan into a plurality of databases;1receiving, by the PGW (120) upon sending the initialization request, data associated with the synchronization of the EPC plan from the FMS (110), wherein the FMS (110) fetches the data from an EPC node based on the request; andperforming, by the PGW (120) upon reception of the data associated with the synchronization of the EPC plan, the synchronization of the EPC plan in the plurality of databases17. A computer program product comprising computer-executable instructions that are stored on a non-transitory computer-readable medium and that, when executed by at least one processor performs operations comprising:receiving, by a Fulfillment Management System (FMS) (110), an initialization request from a Provisioning Gateway (PGW) (120) for synchronization of an Enterprise Product Catalog (EPC) plan into a plurality of databases;initiating, by the FMS (110) upon receiving the initialization request, a call to an EPC node to fetch data associated with the synchronization of the EPC plan from an EPC node and sending a first success response to the PGW (120) upon initiating the call; andsending, by the FMS (110), a plan sync request to the PGW (120), wherein the plan sync request includes the data associated with synchronization of the EPC plan into the plurality of databases.

Images