FORM 2
THE PATENTS ACT, 1970 (39 OF 1970) & THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
“SYSTEM AND METHOD FOR SYNCHRONIZING DATA BETWEEN A CENTRALIZED PRODUCT CATALOGUE AND
A USER SYSTEM”
We, Jio Platforms Limited, an Indian National, of Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India.
The following specification particularly describes the invention and the manner in which it is to be performed.

SYSTEM AND METHOD FOR SYNCHRONIZING DATA BETWEEN A CENTRALIZED PRODUCT CATALOGUE AND A USER SYSTEM
FIELD OF THE INVENTION
[0001] Embodiments of the present disclosure generally relate to data
synchronization systems. In particular, the present disclosure relates to data synchronization. More particularly, the present disclosure relates to system and method for synchronizing data between a centralized product catalogue and a user/consumer system in a 5G environment.
BACKGROUND
[0002] The following description of related art is intended to provide
background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section be used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art.
[0003] The field of 5G networks involves numerous system nodes that require
access to products or plans offering data. The creation and maintenance of this data, consisting of 92 tables and their corresponding mapping tables, has proven to be complex and challenging. Additionally, the task of keeping track of each consumer node and its consumed data tables has resulted in chaotic processes.
[0004] In the prior art, handling product or plan offering data, which includes
large number of tables (for example, 92 tables) along with their corresponding

mapping tables, is quite complex. The process of creating and maintaining these data tables, and keeping them synchronized with individual nodes, is complicated and time-consuming. Keeping track of each consumer node and its respective consumed data tables is a chaotic task in previous systems. There is no systematic approach to track the data consumption across different nodes. In the existing system, onboarding new consumers who require access to product catalogue data is a challenging and time-intensive task. There is a need for an easier and faster onboarding process. Prior methods lack an efficient way to synchronize the data from a centralized product catalogue system with the consumer nodes in a systematic manner. This results in inconsistencies and possible data losses. Consumer systems might not require all data but specific portions of it. However, previous methods don't support such selective data access and synchronization. Further, prior systems might not support diverse data formats, which limits the consumer system's ability to utilize the data effectively.
[0005] These problems and limitations in the prior art necessitate the
development of a system and method for synchronization between the centralized product catalogue and consumer in a network such as 4G, 5G, and any like such like network. The present invention aims to tackle these challenges by providing a more streamlined, efficient, and flexible method of managing, tracking, and synchronizing data between the product catalogue system and consumer nodes.
SUMMARY
[0006] This section is provided to introduce certain aspects of the present
disclosure in a simplified form that are further described below in the detailed description. This summary is not intended to identify the key features or the scope of the claimed subject matter.

[0007] An aspect of the present disclosure may relate to a method for
synchronizing data between a centralized product catalogue and a user system. The method includes receiving, by a receiving unit, a request from a user system for access to a centralized product catalogue comprising a plurality of products. Next, the method includes generating, by a generating unit, an interface based on the request, wherein the generated interface comprises a set of data tables corresponding to at least one product of the plurality of products. Next, the method includes configuring, by a processing unit, a display associated with the user system based on the generated interface. Next, the method includes defining, by the processing unit, a workflow configuration for the user system, wherein the workflow configuration comprises at least one of a frequency of receiving updates from the centralized product catalogue and format of the set of data tables. Next, the method includes synchronizing, by a synchronizing unit, the set of data tables at the user system with the centralized product catalogue based on the defined workflow.
[0008] In an exemplary aspect of the present disclosure, the method further
comprises tracking, by the processing unit, a history of data transactions between the centralized product catalogue and the user system.
[0009] In an exemplary aspect of the present disclosure, the method further
comprises tracking the history of data transactions further comprises logging each request for access to the centralized product catalogue and each synchronization operation performed.
[0010] In an exemplary aspect of the present disclosure, the method further
comprises the synchronizing comprises receiving the set of data tables from the centralized product catalogue in at least Excel XLS file format.

[0011] In an exemplary aspect of the present disclosure, the method further
comprises synchronizing the set of data tables at the user system with the centralized product catalogue further comprises performing, by the processing unit, a bulk synchronization operation to transfer a large volume of data at once.
[0012] In an exemplary aspect of the present disclosure, the method further
comprises the bulk synchronization operation is followed by an incremental synchronization operation to update the user system with changes to the data in the centralized product catalogue wherein the incremental synchronization operation comprises updating the user system with changes to the data in the centralized product catalogue that occurred after the bulk synchronization operation.
[0013] In an exemplary aspect of the present disclosure, the method further
comprises the centralized product catalogue is synchronized with the user system via RESTful application program interface (API) after the bulk synchronization operation.
[0014] In an exemplary aspect of the present disclosure, the method further
comprises the workflow configuration defined for the user system comprises orchestration details, and wherein the workflow configuration facilitates in performing a one-time setup for the user system.
[0015] In an exemplary aspect of the present disclosure, the method further
comprises upon completion of the one-time setup, the user system facilitates importing product data from the centralized product catalogue.
[0016] Another aspect of the present disclosure may relate to a system for
synchronizing data between a centralized product catalogue and a user system. The system comprises a receiving unit configured to receive a request from a user system for access to a centralized product catalogue comprising a plurality of

products; a generating unit configured to generate an interface based on the request,
wherein the generated interface comprises a set of data tables corresponding to at
least one product of the plurality of products; a processing unit to configure a
display associated with the user system based on the generated interface; the
5 processing unit configured to define a workflow configuration for the user system,
wherein the workflow configuration comprises at least one of a frequency of
receiving updates from the centralized product catalogue and format of the set of
data tables; and a synchronizing unit configured to synchronize the set of data tables
at the user system with the centralized product catalogue based on the defined
10 workflow.
[0017] Yet another aspect of the present disclosure may relate to a non-transitory
computer readable storage medium storing instructions for synchronizing data between a centralized product catalogue and a user system, the instructions include
15 executable code which, when executed by one or more units of a system, causes: a
receiving unit to receive a request from a user system for access to a centralized product catalogue comprising a plurality of products; a generating unit to generate an interface based on the request, wherein the generated interface comprises a set of data tables corresponding to at least one product of the plurality of products; a
20 processing unit to display associated with the user system based on the generated
interface; the processing unit to define a workflow configuration for the user system, wherein the workflow configuration comprises at least one of a frequency of receiving updates from the centralized product catalogue and format of the set of data tables; and a synchronizing unit to synchronize the set of data tables at the user
25 system with the centralized product catalogue based on the defined workflow.
[0018] Yet another aspect of the present disclosure may relate to a user
equipment (UE) for synchronizing data between a centralized product catalogue
and a user system comprising: a processor configured to: receive a request from a
30 user system for access to a centralized product catalogue comprising a plurality of
6

products; generate an interface based on the request, wherein the generated
interface comprises a set of data tables corresponding to at least one product of the
plurality of products; configure a display associated with the user system based on
the generated interface; define a workflow configuration for the user system,
5 wherein the workflow configuration comprises at least one of a frequency of
receiving updates from the centralized product catalogue and format of the set of data tables; and synchronize the set of data tables at the user system with the centralized product catalogue based on the defined workflow.
10 OBJECTS OF THE INVENTION
[0019] Some of the objects of the present disclosure, which at least one
embodiment disclosed herein satisfies are listed herein below.
15 [0020] It is an object of the present disclosure to provide a system and method
for synchronization between the centralized product catalogue and consumer in 5G.
[0021] It is another object of the present disclosure to provide a system and
method for synchronization between the centralized product catalogue and
20 consumer in 5G that simplify the process of managing and synchronizing product
or plan offering data across different system nodes. This data involves multiple tables and their corresponding mapping tables, which present invention aims to handle in a more efficient manner.
25 [0022] It is yet another object of the present disclosure to provide a system and
method for synchronization between the centralized product catalogue and consumer in 5G that aims to systematically track each consumer node along with its consumed data tables. This represents a significant improvement over the prior chaotic tracking methods.
7

[0023] It is yet another object of the present disclosure to provide a system and
method for synchronization between the centralized product catalogue and
consumer in 5G that make the onboarding of new consumers more straightforward
5 and faster. This is achieved through the Product Sync Catalogue, which facilitates
the process of getting product catalogue data.
[0024] It is yet another object of the present disclosure to provide a system and
method for synchronization between the centralized product catalogue and
10 consumer in 5G that synchronize data from a centralized product catalogue system
to consumer nodes in a systematic and efficient way. This process reduces inconsistencies and prevents data loss.
[0025] It is yet another object of the present disclosure to provide a system and
15 method for synchronization between the centralized product catalogue and
consumer in 5G that enables consumer systems to access and synchronize specific portions of data, not just the entirety of it. This ensures that the consumer systems get exactly what they need.
20 [0026] It is yet another object of the present disclosure to provide a system and
method for synchronization between the centralized product catalogue and consumer in 5G that aims to provide data in various formats like XLS and JSON, thus enhancing the versatility of the system and allowing the consumer to utilize the data more effectively.
25
[0027] It is yet another object of the present disclosure to provide a system and
method for synchronization between the centralized product catalogue and consumer in 5G that enables both automated and manual data synchronization. It provides an 'Incremental Sync' mechanism that can deliver updated data on-
8

demand. This feature allows for a more controlled and timely data sync based on the needs of the consumer.
[0028] It is yet another object of the present disclosure to provide a system and
5 method for synchronization between the centralized product catalogue and
consumer in 5G that keeps track of the history and follow-ups of data transactions between consumer and catalogue. This feature aids in maintaining a clear record of data exchanges and tracking any changes or updates.
10 [0029] It is yet another object of the present disclosure to provide a system and
for synchronization between the centralized product catalogue and consumer in 5G that is designed to be flexible and scalable, allowing for the easy addition of new consumers and the ability to manage increased amounts of data as the system grows.
15 DESCRIPTION OF THE DRAWINGS
[0030] The accompanying drawings, which are incorporated herein, and
constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same
20 parts throughout the different drawings. Components in the drawings are not
necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Also, the embodiments shown in the figures are not to be construed as limiting the disclosure, but the possible variants of the method and system according to the disclosure are illustrated herein to highlight the
25 advantages of the disclosure. It will be appreciated by those skilled in the art that
disclosure of such drawings includes disclosure of electrical components or circuitry commonly used to implement such components.
[0031] FIG. 1 illustrates an exemplary block diagram representation of 5th
30 generation core (5GC) network architecture.
9

[0032] FIG. 2 illustrates an exemplary block diagram of a computing device
upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure. 5
[0033] FIG. 3 illustrates an exemplary block diagram of a system for
synchronizing data between a centralized product catalogue and a user system, in accordance with exemplary implementations of the present disclosure.
10 [0034] FIG. 4 illustrates a method flow diagram for synchronizing data between
a centralized product catalogue and a user system in accordance with exemplary implementations of the present disclosure.
[0035] FIG. 5 illustrates a system block diagram for synchronizing data between
15 a centralized product catalogue and a user system, in accordance with exemplary
implementations of the present disclosure.
[0036] FIG. 6 illustrates an exemplary user interface (UI) to create a view for a
user system, in accordance with exemplary implementations of the present
20 disclosure.
[0037] FIG. 7 illustrates an exemplary user interface (UI) to configure a
consumer system with a created view, in accordance with exemplary implementations of the present disclosure. 25
[0038] FIG. 8 illustrates an exemplary user interface (UI) to define a workflow
configuration for each consumer system, in accordance with exemplary implementations of the present disclosure.
10

[0039] FIG. 9 illustrates an exemplary user interface (UI) to execute a bulk sync
operation upon request, in accordance with exemplary implementations of the present disclosure.
5 [0040] The foregoing shall be more apparent from the following more detailed
description of the disclosure.
DETAILED DESCRIPTION
10 [0041] 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 may each be used independently of one
15 another or with any combination of other features. An individual feature may not
address any of the problems discussed above or might address only some of the problems discussed above.
[0042] The ensuing description provides exemplary embodiments only, and is
20 not intended to limit the scope, applicability, or configuration of the disclosure.
Rather, the ensuing description of the exemplary embodiments will provide those
skilled in the art with an enabling description for implementing an exemplary
embodiment. It should be understood that various changes may be made in the
function and arrangement of elements without departing from the spirit and scope
25 of the disclosure as set forth.
[0043] Specific details are given in the following description to provide a
thorough understanding of the embodiments. However, it will be understood by one
of ordinary skill in the art that the embodiments may be practiced without these
30 specific details. For example, circuits, systems, processes, and other components
11

may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail.
[0044] Also, it is noted that individual embodiments may be described as a
5 process which is depicted as a flowchart, a flow diagram, a data flow diagram, a
structure diagram, or a block diagram. Although a flowchart may describe the
operations as a sequential process, many of the operations may be performed in
parallel or concurrently. In addition, the order of the operations may be re-arranged.
A process is terminated when its operations are completed but could have additional
10 steps not included in a figure.
[0045] The word “exemplary” and/or “demonstrative” is used herein to mean
serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any
15 aspect or design described herein as “exemplary” and/or “demonstrative” is not
necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed
20 description or the claims, such terms are intended to be inclusive—in a manner
similar to the term “comprising” as an open transition word—without precluding any additional or other elements.
[0046] As used herein, a “processing unit” or “processor” or “operating
25 processor” includes one or more processors, wherein processor refers to any logic
circuitry for processing instructions. A processor may be a general-purpose
processor, a special purpose processor, a conventional processor, a digital signal
processor, a plurality of microprocessors, one or more microprocessors in
association with a (Digital Signal Processing) DSP core, a controller, a
30 microcontroller, Application Specific Integrated Circuits, Field Programmable
12

Gate Array circuits, any other type of integrated circuits, etc. The processor may
perform signal coding data processing, input/output processing, and/or any other
functionality that enables the working of the system according to the present
disclosure. More specifically, the processor or processing unit is a hardware
5 processor.
[0047] As used herein, “a user equipment”, “a user device”, “a smart-user-
device”, “a smart-device”, “an electronic device”, “a mobile device”, “a handheld device”, “a wireless communication device”, “a mobile communication device”, “a
10 communication device” may be any electrical, electronic and/or computing device
or equipment, capable of implementing the features of the present disclosure. The user equipment/device may include, but is not limited to, a mobile phone, smart phone, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, wearable device or any other computing device which is capable
15 of implementing the features of the present disclosure. Also, the user device may
contain at least one input means configured to receive an input from at least one of a transceiver unit, a processing unit, a storage unit, a detection unit and any other such unit(s) which are required to implement the features of the present disclosure.
20 [0048] As used herein, “storage unit” or “memory unit” refers to a machine or
computer-readable medium including any mechanism for storing information in a form readable by a computer or similar machine. For example, a computer-readable medium includes read-only memory (“ROM”), random access memory (“RAM”), magnetic disk storage media, optical storage media, flash memory devices or other
25 types of machine-accessible storage media. The storage unit stores at least the data
that may be required by one or more units of the system to perform their respective functions.
[0049] As used herein “interface” or “user interface refers to a shared boundary
30 across which two or more separate components of a system exchange information
13

or data. The interface may also be referred to a set of rules or protocols that define communication or interaction of one or more modules or one or more units with each other, which also includes the methods, functions, or procedures that may be called. 5
[0050] All modules, units, components used herein, unless explicitly excluded
herein, may be software modules or hardware processors, the processors being a
general-purpose processor, a special purpose processor, a conventional processor,
a digital signal processor (DSP), a plurality of microprocessors, one or more
10 microprocessors in association with a DSP core, a controller, a microcontroller,
Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array circuits (FPGA), any other type of integrated circuits, etc.
[0051] As used herein the transceiver unit include at least one receiver and at
15 least one transmitter configured respectively for receiving and transmitting data,
signals, information or a combination thereof between units/components within the system and/or connected with the system.
[0052] As used herein the term ‘consumer system’ and ‘user system’ are
20 interchangeably used with similar scope of the present disclosure.
[0053] As discussed in the background section, the current known solutions have
several shortcomings. Further, handling a product or plan offering data, which includes a large number of tables (for example, 92 tables) along with their
25 corresponding mapping tables, is quite complex. The process of creating and
maintaining these data tables, and keeping them synchronized with individual nodes, is complicated and time-consuming. Keeping track of each consumer node and its respective consumed data tables is a chaotic task in previous systems. There is no systematic approach to track the data consumption across different nodes. In
30 the existing system, onboarding new consumers who require access to product
14

catalogue data is a challenging and time-intensive task. There is a need for an easier
and faster onboarding process. Prior methods lack an efficient way to synchronize
the data from a centralized product catalogue system with the consumer nodes in a
systematic manner. This results in inconsistencies and possible data losses.
5 Consumer systems might not require all data but specific portions of it. However,
previous methods don't support such selective data access and synchronization. Further, prior systems might not support diverse data formats, which limits the consumer system's ability to utilize the data effectively.
10 [0054] These problems and limitations in the background necessitate the
development of a system and method for synchronization between the centralized product catalogue and consumer in 4G, 5G or 6G, and any other such like communication network. The present disclosure aims to overcome the above-mentioned and other existing problems in this field of technology by providing
15 method and system for synchronizing data between a centralized product catalogue
and a consumer system. The present invention aims to tackle these challenges by providing a more streamlined, efficient, and flexible method of managing, tracking, and synchronizing data between the product catalogue system and consumer nodes.
20 [0055] FIG. 1 illustrates an exemplary block diagram representation of 5th
generation core (5GC) network architecture, in accordance with exemplary implementation of the present disclosure. As shown in FIG. 1, the 5GC network architecture [100] includes a user equipment (UE) [102], a radio access network (RAN) [104], an access and mobility management function (AMF) [106], a Session
25 Management Function (SMF) [108], a Service Communication Proxy (SCP) [110],
an Authentication Server Function (AUSF) [112], a Network Slice Specific Authentication and Authorization Function (NSSAAF) [114], a Network Slice Selection Function (NSSF) [116], a Network Exposure Function (NEF) [118], a Network Repository Function (NRF) [120], a Policy Control Function (PCF) [122],
30 a Unified Data Management (UDM) [124], an application function (AF) [126], a
15

User Plane Function (UPF) [128], a data network (DN) [130], wherein all the components are assumed to be connected to each other in a manner as obvious to the person skilled in the art for implementing features of the present disclosure.
5 [0056] Radio Access Network (RAN) [104] is the part of a mobile
telecommunications system that connects user equipment (UE) [102] to the core network (CN) and provides access to different types of networks (e.g., 5G network). It consists of radio base stations and the radio access technologies that enable wireless communication.
10
[0057] Access and Mobility Management Function (AMF) [106] is a 5G core
network function responsible for managing access and mobility aspects, such as UE registration, connection, and reachability. It also handles mobility management procedures like handovers and paging.
15
[0058] Session Management Function (SMF) [108] is a 5G core network
function responsible for managing session-related aspects, such as establishing, modifying, and releasing sessions. It coordinates with the User Plane Function (UPF) for data forwarding and handles IP address allocation and QoS enforcement.
20
[0059] Service Communication Proxy (SCP) [110] is a network function in the
5G core network that facilitates communication between other network functions by providing a secure and efficient messaging service. It acts as a mediator for service-based interfaces.
25
[0060] Authentication Server Function (AUSF) [112] is a network function in
the 5G core responsible for authenticating UEs during registration and providing security services. It generates and verifies authentication vectors and tokens.
16

[0061] Network Slice Specific Authentication and Authorization Function
(NSSAAF) [114] is a network function that provides authentication and authorization services specific to network slices. It ensures that UEs can access only the slices for which they are authorized. 5
[0062] Network Slice Selection Function (NSSF) [116] is a network function
responsible for selecting the appropriate network slice for a UE based on factors such as subscription, requested services, and network policies.
10 [0063] Network Exposure Function (NEF) [118] is a network function that
exposes capabilities and services of the 5G network to external applications, enabling integration with third-party services and applications.
[0064] Network Repository Function (NRF) [120] is a network function that acts
15 as a central repository for information about available network functions and
services. It facilitates the discovery and dynamic registration of network functions.
[0065] Policy Control Function (PCF) [122] is a network function responsible
for policy control decisions, such as QoS, charging, and access control, based on
20 subscriber information and network policies.
[0066] Unified Data Management (UDM) [124] is a network function that
centralizes the management of subscriber data, including authentication, authorization, and subscription information. 25
[0067] Application Function (AF) [126] is a network function that represents
external applications interfacing with the 5G core network to access network capabilities and services.
17

[0068] User Plane Function (UPF) [128] is a network function responsible for
handling user data traffic, including packet routing, forwarding, and QoS enforcement.
5 [0069] Data Network (DN) [130] refers to a network that provides data services
to user equipment (UE) in a telecommunications system. The data services may include but are not limited to Internet services, private data network related services.
[0070] FIG. 2 illustrates an exemplary block diagram of a computing device
10 [200] (also referred to herein as a computer system [200]) upon which the features
of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure. In an implementation, the computing device [200] may also implement a method for synchronizing data between a centralized product catalogue and a consumer system utilising the system. In
15 another implementation, the computing device [200] itself implements the method
for synchronizing data between a centralized product catalogue and a consumer system using one or more units configured within the computing device [200], wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.
20
[0071] The computing device [200] may include a bus [202] or other
communication mechanism for communicating information, and a processor [204] coupled with the bus [202] for processing information. The processor [204] may be, for example, a general purpose microprocessor. The computing device [200]
25 may also include a main memory [206], such as a random access memory (RAM),
or other dynamic storage device, coupled to the bus [202] for storing information and instructions to be executed by the processor [204]. The main memory [206] also may be used for storing temporary variables or other intermediate information during execution of the instructions to be executed by the processor [204]. Such
30 instructions, when stored in non-transitory storage media accessible to the processor
18

[204], render the computing device [200] into a special-purpose machine that is
customized to perform the operations specified in the instructions. The computing
device [200] further includes a read only memory (ROM) [208] or other static
storage device coupled to the bus [202] for storing static information and
5 instructions for the processor [204].
[0072] A storage device [210], such as a magnetic disk, optical disk, or solid-
state drive is provided and coupled to the bus [202] for storing information and instructions. The computing device [200] may be coupled via the bus [202] to a
10 display [212], such as a cathode ray tube (CRT), Liquid crystal Display (LCD),
Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for displaying information to a computer user. An input device [214], including alphanumeric and other keys, touch screen input means, etc. may be coupled to the bus [202] for communicating information and command selections to the processor
15 [204]. Another type of user input device may be a cursor controller [216], such as
a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor [204], and for controlling cursor movement on the display [212]. This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow
20 the device to specify positions in a plane.
[0073] The computing device [200] may implement the techniques described
herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware and/or program logic which in combination with the computing device [200] causes
25 or programs the computing device [200] to be a special-purpose machine.
According to one implementation, the techniques herein are performed by the computing device [200] in response to the processor [204] executing one or more sequences of one or more instructions contained in the main memory [206]. Such instructions may be read into the main memory [206] from another storage medium,
30 such as the storage device [210]. Execution of the sequences of instructions
19

contained in the main memory [206] causes the processor [204] to perform the process steps described herein. In alternative implementations of the present disclosure, hard-wired circuitry may be used in place of or in combination with software instructions. 5
[0074] The computing device [200] also may include a communication interface
[218] coupled to the bus [202]. The communication interface [218] provides a two-way data communication coupling to a network link [220] that is connected to a local network [222]. For example, the communication interface [218] may be an
10 integrated services digital network (ISDN) card, cable modem, satellite modem, or
a modem to provide a data communication connection to a corresponding type of telephone line. As another example, the communication interface [218] may be a local area network (LAN) card to provide a data communication connection to a compatible LAN. Wireless links may also be implemented. In any such
15 implementation, the communication interface [218] sends and receives electrical,
electromagnetic or optical signals that carry digital data streams representing various types of information.
[0075] The computing device [200] can send messages and receive data,
20 including program code, through the network(s), the network link [220] and the
communication interface [218]. In the Internet example, a server [230] might
transmit a requested code for an application program through the Internet [228], the
Host [224] the ISP [226], the local network [222] and the communication interface
[218]. The received code may be executed by the processor [204] as it is received,
25 and/or stored in the storage device [210], or other non-volatile storage for later
execution. The computing device [200] encompasses a wide range of electronic
devices capable of processing data and performing computations. Examples of
computing device [200] include, but are not limited only to, personal computers,
laptops, tablets, smartphones, servers, and embedded systems. The devices may
30 operate independently or as part of a network and can perform a variety of tasks
20

such as data storage, retrieval, and analysis. Additionally, computing device [200] may include peripheral devices, such as monitors, keyboards, and printers, as well as integrated components within larger electronic systems, showcasing their versatility in various technological applications. 5
[0076] Referring to FIG. 3, an exemplary block diagram of a system [300] for
synchronizing data between a centralized product catalogue and a user system, is shown, in accordance with the exemplary implementations of the present disclosure. The system [300] comprises at least one receiving unit [302], at least
10 one generating unit [304], at least one processing unit [306], at least one
synchronizing unit [308] and at least one tracking unit [310]. Also, all of the components/ units of the system [300] are assumed to be connected to each other unless otherwise indicated below. As shown in the figures all units shown within the system should also be assumed to be connected to each other. Also, in FIG. 3
15 only a few units are shown, however, the system [300] may comprise multiple such
units or the system [300] may comprise any such numbers of said units, as required to implement the features of the present disclosure. Further, in an implementation, the system [300] may be present in a user device to implement the features of the present disclosure. The system [300] may be a part of the user device / or may be
20 independent of but in communication with the user device (may also referred herein
as a UE). In another implementation, the system [300] may reside in a server or a network entity. In yet another implementation, the system [300] may reside partly in the server/ network entity and partly in the user device.
25 [0077] The system [300] is configured for synchronizing data between a
centralized product catalogue and a consumer system synchronizing data between a centralized product catalogue and a consumer system, with the help of the interconnection between the components/units of the system [300].
21

[0078] The system [300] comprises a receiving unit [302] configured to receive
a request from a user system for access to a centralized product catalogue
comprising a plurality of products. In an exemplary aspect, the receiving unit [302]
of the system [300] may receive the request from the user system such as, but not
5 limited to, sales department, billing department, information department, audit
department and finance department etc. in an enterprise (for example telecom etc.). The user system may request for accessing the centralized product catalogue, which may have a plurality of products such as, but not limited to, pricing, allowances, international calling rates, service plan, subscriber demand, subscriber count and
10 the like. The centralized product catalogue may comprise different products of
different user systems or departments in the enterprise. In an exemplary aspect, the request may be in XLS and JSON format. Further, as used herein the “centralized product catalogue” may refer to a unified repository that stores and manages comprehensive information associated with products such as product descriptions,
15 product features and product specifications, a product pricing, product inventory
levels, and any other such like information associated with the products.
[0079] The system [300] comprises a generating unit [304] configured to
generate an interface based on the request, wherein the generated interface
20 comprises a set of data tables corresponding to at least one product of the plurality
of products. For example, for requesting one product out of plurality of products, the user first requests access to a centralized product catalogue containing information related to the plurality of products such as but not limed to pricing, allowances, international calling rates, service plan, subscriber demand, subscriber
25 count etc. Then, in case the user requests international calling rates product, the
system generates an interface displaying the set of data tables related to international calling rates product. The generating unit [304] of the system [300] may generate the interface based on the request of the user system. The generated interface may comprise the set of data tables corresponding to at least one product
30 of the plurality of products. In an exemplary aspect, the generating unit [304] may
22

generate a view wizard interface based on required data tables of the user system or
department from the centralized product catalogue. The view wizard interface may
comprise a configuration of data tables from the centralized product catalogue that
the user system requires. The view wizard interface may have different data tables
5 based on specific data requirements of the user system. Further, as used herein, the
View Wizard Interface may refer to a user-friendly interface that guides a user of the interface through a series of steps to create, manage, and analyse complex data views, reports, and dashboard. In an exemplary aspect, the set of data tables comprises products details such as, but not limited to, pricing, allowances,
10 international calling rates, service plan, plan offering, geographic location plan
offering, subscriber demand, subscriber count and the like and mapping of the products with corresponding user system or departments. For example, a user system or departments such as sales may have mapped or relevant products such as pricing and allowances and another user system or departments such as billing may
15 have mapped or relevant products such as pricing and international calling rates and
the like in the data tables.
[0080] The system [300] comprises a processing unit [306] to configure a
display associated with the user system based on the generated interface. The
20 processing unit [306] of the system [300] may configure the display associated with
the user system based on the generated interface. In an exemplary aspect, the view wizard interface may further be customized based on the requirements of the user system or departments. After generating the view wizard interface, the processing unit [306] may configure the display associated with the user system. This
25 customized configuration setup allows the user system or department to request and
receive only the specific data tables or all tables from the centralized product catalogue, streamlining the data acquisition process as per requirement or need.
[0081] The system [300] further comprises the processing unit [306] configured
30 to define a workflow configuration for the user system, wherein the workflow
23

configuration comprises at least one of a frequency of receiving updates from the
centralized product catalogue and format of the set of data tables. The processing
unit [306] may further define the workflow configuration for the user system or
department. The workflow configuration may comprise at least one of the
5 frequency of receiving updates from the centralized product catalogue and format
of the set of data tables. The workflow configuration may be defined based on user system, product types and vendor specific. In an exemplary aspect, the updates may receive from the centralized product catalogue on demand or periodically. In an exemplary aspect, the workflow configuration may comprise details of an
10 orchestration system for data synchronization between a centralized product
catalogue and the user system. The orchestration system may comprise details of workflow specific to the user system and the product details. The workflow configuration defined for the user system comprises orchestration details and the workflow configuration facilitates in performing a one-time setup for the user
15 system. Further, upon completion of the one-time setup, the user system facilitates
in importing product data from the centralized product catalogue.
[0082] In an exemplary aspect, user system mapped with view wizard interface
is sync with all mapped data tables to consumer node via the orchestrator system.
20 In an exemplary aspect, the consumer node synchronises the mapped data tables
from centralized product catalogue such as but not limited to enterprise product catalogue (EPC) [500A] (as shown in FIG. 5), wherein the EPC [500A] is a product catalogue where product gets defined and fetched by the consumer node to be stored it in their corresponding local database. Further, the configuration of orchestrator is
25 defined in workflow configuration. In an exemplary aspect, the orchestrator system
is an operations, administration and management (OAM) module that may be configured to store the data associated with microservices and/or channels such as a Data Information Framework (DIF), a subscription engine (SE), a WEB PORTAL, and any other such like microservices and/or channels. The workflow
24

configuration is provisioning way where the user system details are provided to the orchestrator.
[0083] The system [300] comprises a synchronizing unit [308] configured to
5 synchronize the set of data tables at the user system with the centralized product
catalogue based on the defined workflow. The synchronizing unit [308] may synchronize the set of data tables at the user system or department with the centralized product catalogue based on the defined workflow. In an exemplary aspect, the synchronizing comprises receiving the set of data tables from the
10 centralized product catalogue in at least Excel XLS file format. The synchronizing
unit [308] may perform a bulk synchronization operation to transfer a large volume of data at once. The bulk synchronization operation is followed by an incremental synchronization operation to update the user system with changes to the data in the centralized product catalogue. The centralized product catalogue is synchronized
15 with the user system via RESTful application program interface (API) after the bulk
synchronization operation. Further, as used herein, the “RESTful application program interface (API) may refer to an interface that uses Representational State of Resource (REST) architecture to enable an exchange product data with the user system, by utilizing HTTP methods (GET, POST, PUT, DELETE) to perform
20 CRUD (Create, Read, Update, Delete) operations, and to ensure seamless
communication, data exchange, and synchronization with the user system. Further, the RESTful API may provide real-time product data to the user system, receive updates from the user system, perform crud operations on product data and ensure data consistency and accuracy.
25
[0084] In one exemplary embodiment, the method for synchronizing data
between a centralized product catalogue and a user system includes receiving the set of data tables from the centralized product catalogue in at least Excel XLS file format. For example, a new user system is onboarded and requests access to the
30 centralized product catalogue containing information on multiple products. The
25

system receives this request and generates an interface displaying the relevant data
tables for the requested products. The processing unit then configures the user
system's display based on this interface and defines a workflow configuration
specifying how often updates are received and the format of the data tables. During
5 the initial synchronization, a bulk synchronization operation is performed where a
large volume of product data is exported from the centralized product catalogue
into an Excel XLS file. The file is then transmitted to the user system, where the
data is imported and integrated. Subsequently, any updates to the product data in
the centralized catalogue, such as new product additions or modifications to
10 existing product details, are synchronized incrementally. These updates are also
provided in Excel XLS file format, ensuring the user system maintains current and accurate product data.
[0085] In an exemplary aspect, centralized product catalogue may fetch the
15 mapping data tables of view wizard interface to create data records to be exported.
The records fetched from centralized product catalogue may exported into XLS file.
This exported data records file is sent to orchestration of data with user system using
vendor-workflow configuration. The orchestration system may provide
confirmation of data response send by the user system. This is process cycle of sync
20 of centralized product catalogue data with user system.
[0086] In an exemplary aspect, the synchronizing unit [308] may configure to
execute a bulk data synchronization operation based on receiving a request from
the user system, wherein the bulk data is exported from the centralized product
25 catalogue to the user system. The bulk data is exported from the centralized product
catalogue in an XLS file format. Further, the centralized product catalogue consists of at least 92 data tables with their respective mapping tables.
[0087] The system [300] comprises a tracking unit [310], which is configured to
30 track a history of data transactions between the centralized product catalogue and
26

the user system. Further, tracking the history of data transactions further comprises logging each request for access to the centralized product catalogue and each synchronization operation performed.
5 [0088] In an exemplary aspect, an aspect of the present disclosure provides a
system for synchronization between the centralized product catalogue and consumer in 5G, said system executing the steps of : creating a view interface for each consumer system, said view interface comprising the configuration of required data tables; configuring the consumer system with the created view, wherein the
10 consumer system can request specific or all data tables from the product catalogue;
defining a workflow configuration for each consumer system, including details of an orchestration system for data synchronization; initiating a one-time setup for the consumer system, wherein after setup completion, the consumer system is ready to import data from the product catalogue; upon request from the consumer system,
15 executing a Bulk Sync operation, where all or selected data from the product
catalogue is exported to an XLS file and sent to the consumer system; providing an Incremental Sync operation, wherein updates to the data in the product catalogue after the Bulk Sync operations are sent to the consumer system on-demand via RESTful APIs; tracking the history and follow-ups of data transactions between the
20 consumer system and the product catalogue, wherein the data transactions are
logged for future reference and reconciliation; enabling the consumer system to periodically request updates to the data records in the product catalogue.
[0089] Referring to FIG. 4, an exemplary method flow diagram [400] for
25 synchronizing data between a centralized product catalogue and a user system, in
accordance with exemplary implementations of the present disclosure is shown. In
an implementation the method [400] is performed by the system [300]. Further, in
an implementation, the system [300] may be present in a server device to implement
the features of the present disclosure. Also, as shown in FIG. 4, the method [400]
30 starts at step [402].
27

[0090] At step [404], the method [400] as disclosed by the present disclosure
comprises receiving, by a receiving unit [302], a request from a user system for
access to a centralized product catalogue comprising a plurality of products. The
5 method [400] implemented by the receiving unit [302] of the system [300] may
receive the request from a user system for access to the centralized product catalogue comprising a plurality of products. In an exemplary aspect, the receiving unit [302] of the system [300] may receive the request from the user system such as, but not limited to, sales department, billing department, information department,
10 audit department and finance department etc. in an enterprise (for example telecom
etc.). The user system may request for accessing the centralized product catalogue, which may have a plurality of products such as, but not limited to, pricing, allowances, international calling rates, service plan, subscriber demand, subscriber count and the like. The centralized product catalogue may comprise different
15 products of different user systems or departments in the enterprise. In an exemplary
aspect, the request may be in XLS and JSON format.
[0091] Next, at step [406], the method [400] as disclosed by the present
disclosure comprises generating, by a generating unit [304], an interface based on
20 the request, wherein the generated interface comprises the set of data tables
corresponding to at least one product of the plurality of products. The generating unit [304] of the system [300] may generate the interface based on the request, wherein the generated interface comprises a set of data tables corresponding to at least one product of the plurality of products. The generating unit [304] of the
25 system [300] may generate the interface based on the request of the user system.
The generated interface may comprise the set of data tables corresponding to at least one product of the plurality of products. In an exemplary aspect, the generating unit [304] may generate a view wizard interface based on required data tables of the user system or department from the centralized product catalogue. The view wizard
30 interface may comprise a configuration of data tables from the centralized product
28

catalogue that the user system requires. The view wizard interface may have
different data tables based on specific data requirements of the user system. In an
exemplary aspect, the set of data tables comprises products details such as, but not
limited to, pricing, allowances, international calling rates, service plan, plan
5 offering, geographic location plan offering, subscriber demand, subscriber count
and the like and mapping of the products with corresponding user system or
departments. For example, a user system or departments such as sales may have
mapped or relevant products such as pricing and allowances and another user
system or departments such as billing may have mapped or relevant products such
10 as pricing and international calling rates and the like in the data tables.
[0092] Next, at step [408], the method [400] as disclosed by the present
disclosure comprises configuring, by a processing unit [306], a display associated with the user system based on the generated interface. The system [300] comprises
15 a processing unit [306] to configure the display associated with the user system
based on the generated interface. The processing unit [306] of the system [300] may configure the display associated with the user system based on the generated interface. In an exemplary aspect, the view wizard interface may further be customized based on the requirements of the user system or departments. After
20 generating the view wizard interface, the processing unit [306] may configure the
display associated with the user system. This customized configuration setup allows the user system or department to request and receive only the specific data tables or all tables from the centralized product catalogue, streamlining the data acquisition process as per requirement or need.
25
[0093] Next, at step [410], the method [400] as disclosed by the present
disclosure comprises defining, by the processing unit [306], a workflow configuration for the user system, wherein the workflow configuration comprises at least one of a frequency of receiving updates from the centralized product
30 catalogue and format of the set of data tables. The processing unit [306] of the
29

system [300] further may define the workflow configuration for the user system,
wherein the workflow configuration comprises at least one of a frequency of
receiving updates from the centralized product catalogue and format of the set of
data tables. The processing unit [306] may further define the workflow
5 configuration for the user system or department. The workflow configuration may
comprise at least one of a frequency of receiving updates from the centralized product catalogue and format of the set of data tables. The workflow configuration may be defined based on user system, product types and vendor specific. In an exemplary aspect, the updates may receive from the centralized product catalogue
10 on demand or periodically. In an exemplary aspect, the workflow configuration may
comprise details of an orchestration system for data synchronization between a centralized product catalogue and the user system. The orchestration system may comprise details of workflow specific to the user system and the product details. The workflow configuration defined for the user system comprises orchestration
15 details and the workflow configuration facilitates in performing a one-time setup
for the user system. Further, upon completion of the one-time setup, the user system facilitates in importing product data from the centralized product catalogue. Further, in accordance with the present disclosure, upon completion of the one-time setup, the user system initiates the synchronization process with the centralized
20 product catalogue via the RESTful API. The user system sends a request to the CPC
to import the latest product data, which includes product descriptions, features, pricing, and inventory levels. The centralized product catalogue processes the request and responds with the requested data in a standardized format. The user system then receives the data and updates its local product catalogue, ensuring that
25 the latest product information is now available to users.
[0094] In an exemplary aspect, user system mapped with view wizard interface
is sync with all mapped data tables to consumer node via the orchestrator system.
As used herein, the consumer node may refer to a node that synchronises the
30 mapped data tables from centralized product catalogue such as but not limited to
30

enterprise product catalogue (EPC) [500A], wherein the EPC [500A] is a product
catalogue where product gets defined and fetched by the consumer node to be stored
it in their corresponding local database. Further, the configuration of orchestrator is
defined in workflow configuration. In an exemplary aspect, the orchestrator system
5 is an operations, administration and management (OAM) module that may be
configured to store the data associated with microservices and/or channels such as a Data Information Framework (DIF), a subscription engine (SE), a web portal, and any other such like microservices and/or channels. The workflow configuration is provisioning way where the user system details are provided to the orchestrator.
10
[0095] Next, at step [412], the method [400] as disclosed by the present
disclosure comprises synchronizing, by a synchronizing unit [308], the set of data tables at the user system with the centralized product catalogue based on the defined workflow. The synchronizing unit [308] of the system [300] may synchronize the
15 set of data tables at the user system with the centralized product catalogue based on
the defined workflow. The synchronizing unit [308] may synchronize the set of data tables at the user system or department with the centralized product catalogue based on the defined workflow. In an exemplary aspect, the synchronizing comprises receiving the set of data tables from the centralized product catalogue in at least
20 Excel XLS file format. The synchronizing unit [308] may perform a bulk
synchronization operation to transfer a large volume of data at once. The bulk synchronization operation is followed by an incremental synchronization operation to update the user system with changes to the data in the centralized product catalogue. The centralized product catalogue is synchronized with the user system
25 via RESTful application program interface (API) after the bulk synchronization
operation.
[0096] In an exemplary aspect, centralized product catalogue may fetch the
mapping data tables of view wizard interface to create data records to be exported.
30 The records fetched from centralized product catalogue may exported into XLS file.
31

The exported data records file is sent to orchestration of data with user system using
vendor-workflow configuration. The orchestration system may provide
confirmation of data response send by the user system. This is process cycle of sync
of centralized product catalogue data with user system. Further, as used herein, the
5 “incremental synchronization operation” may refer to an operation for updating the
changes made to the product data since the last bulk synchronization operation, to ensure that the user system reflects the latest updates, additions, or deletions made to the product catalogue, thereby maintaining data consistency and accuracy across the enterprise.
10
[0097] In an exemplary aspect, a tracking unit [310] of system [300] may track
a history of data transactions between the centralized product catalogue and the user system. Further, tracking the history of data transactions further comprises logging each request for access to the centralized product catalogue and each
15 synchronization operation performed.
[0098] In an exemplary aspect, the synchronizing unit [308] may configure to
execute a bulk data synchronization operation based on receiving a request from
the user system, wherein the bulk data is exported from the centralized product
20 catalogue to the user system. The bulk data is exported from the centralized product
catalogue in an XLS file format. Further, the centralized product catalogue consists of at least 92 data tables with their respective mapping tables.
[0099] Thereafter, the method [400] terminates at step [414].
25
[0100] The present disclosure further discloses a non-transitory computer
readable storage medium storing instructions for synchronizing data between a centralized product catalogue and a user system, the instructions include executable code which, when executed by one or more units of a system, causes: a receiving
30 unit [302] to receive a request from a user system for access to a centralized product
32

catalogue comprising a plurality of products; a generating unit [304] to generate an
interface based on the request, wherein the generated interface comprises a set of
data tables corresponding to at least one product of the plurality of products; a
processing unit [306] to display associated with the user system based on the
5 generated interface; the processing unit [306] to define a workflow configuration
for the user system, wherein the workflow configuration comprises at least one of
a frequency of receiving updates from the centralized product catalogue and format
of the set of data tables; and a synchronizing unit [308] to synchronize the set of
data tables at the user system with the centralized product catalogue based on the
10 defined workflow.
[0101] Referring to FIG. 5, a system block diagram [500] for synchronizing data
between a centralized product catalogue and a user system, in accordance with
exemplary implementations of the present disclosure is shown. In an embodiment,
15 the process of how an API (Application Programming Interface) request is handled
within a particular system, such as EPC (Enterprise Product Catalogue) [500A] is disclosed herein.
[0102] As used herein, Enterprise Product Catalogue (EPC) [500A] provides the
20 core components necessary to centralize, configure, integrate, and maintain the
product and service portfolio across the enterprise. EPC [500A], a centralized
catalogue, contains all of the commercial and technical elements you use to define
usable product and service building blocks and resulting offers. The EPC [500A]
comprises an EPC instance [508a], an EPC interface [508b], an IAM instance [504]
25 and OAM instance [510].
[0103] Channels [502]: These are the various user interfaces through which the
API request can come. These could be web applications or external systems.
Essentially, a channel is any point of interaction between a user (or another system)
30 and Enterprise Product Catalogue (EPC) [500A]. The channels may comprise
33

subscriber engine (SE) [502a], Digital marketplace (DMP) [502b], web portal
[502c] and customer relations management (CRM) user interface (UI) [502d]. As
used herein, the SE [502a] enables operators to handle multiple content platforms,
routing each subscription-specific event to the respective platform. As used herein,
5 DMP [502b] refers to a market platform, which provides details of vendors,
products and services. As used herein, the web portal [502c] refers to a self-help
portal via which a user/customer can login, view his/her profile and manage his/her
services. As used herein, the customer relations management (CRM) user interface
(UI) [502d] is refers to a user interface (UI) configured for customer relations
10 management that is manged by an authorised operator associated with the CRM.
[0104] IAM (Identity Access Management) Instance [504]: This is a system
that ensures the security of the system by managing user identities and controlling
their access to resources. When an API request comes in, the IAM system
15 authenticates (confirms the identity of the user or system making the request) and
authorizes (checks whether the requester has permission to access the requested data or functionality) the request.
[0105] Load Balancer [506]: After the IAM system has validated the request, it
20 goes to the Load Balancer. The Load Balancer's job is to distribute incoming
network traffic across multiple servers (in this case, EPC application instances) to ensure no single server becomes overwhelmed with too many requests.
[0106] Backend EPC Application Instance [508a]: Once the Load Balancer
25 distributes the request, it lands at one of the backend EPC application instances,
which may connect through one or more EPC interface [508b]. This is where the request is processed, and the appropriate response is generated.
[0107] OAM (Operations, Administration, and Management) Instance
30 [510]: This is a framework for managing and controlling network systems. In this
34

case, it manages the registry of microservices (small, independent processes that together form a larger application), their dependencies, and other information required for the microservices to communicate with each other.
5 [0108] FMS (Fulfilment management system) [512]: This is the middleware
used to integrate the API services with other system nodes. Middleware is software that acts as a bridge between an operating system or database and applications, especially on a network. In an exemplary aspect, unified assurance platform (UAP) [516] and Data information framework (DIF) [518] may be present for API service
10 processing. As used herein, the DIF may refer to a centralized data management
platform that serves as a source of validating one or more critical entities associated with an enterprise such as a customer data, a product catalogue data, and an enterprise reference master data. Further, the DIF may also aggregate data from multiple functional systems, to provide a unified and authoritative view of critical
15 information and may offers high-performance, read-only APIs to various channels
to leverage data caching in order to ensure ultra-fast access to frequently used the one or more critical entities. Further, as used herein, the “UAP” may refer to a platform responsible for managing the entire lifecycle of work orders related to activities such as an installation, a repair, a disconnection, a network issues, field
20 visits, and any other such like activities. Further, the UAP may provide a unified
platform for managing assets, tracking work orders, and ensuring efficient resource allocation. Further, the UAP may in conjunction with the DIF leverage an APIs to access accurate and up-to-date entity information associated with the one or more critical entities, to enable seamless workflows in accordance with the various
25 embodiments of the present disclosure.
[0109] ES Cluster (Elasticsearch Cluster) [514]: This is the database used to
store data. An Elasticsearch cluster is a group of one or more Elasticsearch nodes
instances that are connected together. The power of an Elasticsearch cluster lies in
30 the distribution of tasks, storing data, and in failure tolerance.
35

[0110] As used herein, Elastic Load Balancing (ELB) [520] refers to the
automated distribution of incoming application traffic across multiple targets, such
as virtual servers or containers, within one or more availability zones. The ELB
5 [520] ensures the high availability and reliability of applications by spreading the
traffic load to prevent any single server from becoming a bottleneck. The ELB [520] also monitors the health of registered targets and directs traffic only to healthy instances, thereby enhancing fault tolerance and scalability of the system.
10 [0111] It would be appreciated by the person skilled in the art that the API
requests are efficiently handled, processed, and responded to in a secure and balanced manner, while also ensuring the system is robust and scalable.
[0112] In an exemplary aspect, process for synchronizing data between a
15 centralized product catalogue and a user/consumer system is given below:
[0113] Referring to FIG. 6 an exemplary user interface (UI) [600] to create a
view for a user system , in accordance with exemplary implementations of the
present disclosure is shown. The system [300] creates the view for each
20 user/consumer system. Each consumer system will require specific data tables from
the product catalogue. The view on the UI is created for each consumer system representing these specific data requirements. It's essentially a customized filter to simplify the process of data handling for the consumer system.
25 [0114] Referring to FIG. 7 an exemplary user interface (UI) [700] to configure
a consumer system with a created view, in accordance with exemplary implementations of the present disclosure is shown. Once the view has been created, it is used to configure the consumer system. This setup allows the consumer system to request and receive only the specific data tables they require from the
30 product catalogue, streamlining the data acquisition process.
36

[0115] Referring to FIG. 8 an exemplary user interface (UI) [800] to define a
workflow configuration for each consumer system, in accordance with exemplary
implementations of the present disclosure is shown. Workflow configuration for
5 each consumer system includes the details of an orchestration system for data
synchronization. The orchestration system is responsible for the actual data
transmission process between the product catalogue and the consumer system. In
an exemplary aspect, a one-time setup is initiated for the consumer system. This
step involves the completion of the initial configuration process. After this setup,
10 the consumer system is equipped to import data from the product catalogue.
[0116] Referring to FIG. 9 illustrates an exemplary user interface (UI) [900] to
execute a bulk sync operation upon request, in accordance with exemplary implementations of the present disclosure is shown. The consumer system can
15 request a bulk sync operation, where all or selected data from the product catalogue
is exported into an XLS file. This file is then sent to the consumer system, enabling the transfer of a large volume of data at once. In an exemplary aspect post the bulk sync operation, any updates or changes to the data in the product catalogue can be sent to the consumer system on-demand. This happens via RESTful APIs, and the
20 process is known as the Incremental Sync operation. Further, history is tracked, and
data transactions follow-ups takes place All the data transactions between the consumer system and the product catalogue are logged and tracked. This step ensures a record is kept of all data exchanges, which can be helpful for future reference, troubleshooting, and reconciliation. Furthermore, the consumer system
25 is enabled to periodically request updates. The consumer system has the ability to
request periodic updates to the data records in the product catalogue. This ensures the consumer system always has the most up-to-date data from the product catalogue.
37

[0117] In an exemplary implementation, a Telecom company may have a
centralized product catalogue system. This catalogue consists of various data about their mobile plans, including the pricing, data allowances, network speeds, international calling rates, and more, which are all stored on 92 tables. Now, different departments or systems in the Telecom company need this information. For instance, the sales department might need information about the pricing and allowances, the billing department might need information about the pricing and international calling rates, and so forth.
[0118] As is evident from the above, the present disclosure provides a technical
advancement over the existing solutions. Any consumer system that wants product catalogue data information can approach product catalogue through Product Sync Catalogue. On boarding a new consumer is easy. With one time view and workflow configuration, the system will start receiving the data tables information. Consumers can request data in XLS, JSON format. Product Sync Catalogue tracks the history and follows up with the transaction of data between consumer and catalogue. This is the easy and fastest way to onboard any external system who wants this product catalogue data in their system. EPC supports bulk and incremental sync mechanisms. Incremental Sync provides on demand data to consumer systems updated or created in product catalogue after bulk sync till date. These can be automated or manually demanded. Consumers can periodically ask for data records to be updated with product catalogue records.
[0119] Further, in accordance with the present disclosure, it is to be
acknowledged that the functionality described for the various components/units can be implemented interchangeably. While specific embodiments may disclose a particular functionality of these units for clarity, it is recognized that various configurations and combinations thereof are within the scope of the disclosure. The functionality of specific units, as disclosed in the disclosure, should not be construed as limiting the scope of the present disclosure. Consequently, alternative

arrangements and substitutions of units, provided they achieve the intended functionality described herein, are considered to be encompassed within the scope of the present disclosure.
[0120] While considerable emphasis has been placed herein on the disclosed
embodiments, it will be appreciated that many embodiments can be made and that many changes can be made to the embodiments without departing from the principles of the present disclosure. These and other changes in the embodiments of the present disclosure will be apparent to those skilled in the art, whereby it is to be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting.

I/We Claim:
1. A method for synchronizing data between a centralized product catalogue and
a user system, the method comprising:
receiving, by a receiving unit [302], a request from the user system for access to a centralized product catalogue comprising a plurality of products;
generating, by a generating unit [304], an interface based on the request, wherein the generated interface comprises a set of data tables corresponding to at least one product of the plurality of products;
configuring, by a processing unit [306], a display associated with the user system based on the generated interface;
defining, by the processing unit [306], a workflow configuration for the user system, wherein the workflow configuration comprises at least one of a frequency of receiving updates from the centralized product catalogue and format of the set of data tables; and
synchronizing, by a synchronizing unit [308], the set of data tables at the user system with the centralized product catalogue based on the defined workflow.
2. The method as claimed in claim 1, comprises tracking, by the processing unit [306], a history of data transactions between the centralized product catalogue and the user system.
3. The method as claimed in claim 2, wherein tracking the history of data transactions further comprises logging each request for access to the centralized product catalogue and each synchronization operation performed.

4. The method as claimed in claim 1, wherein synchronizing the set of data tables at the user system with the centralized product catalogue further comprises performing, by the processing unit [306], a bulk synchronization operation to transfer a large volume of data at once.
5. The method as claimed in claim 4, wherein the bulk synchronization operation is followed by an incremental synchronization operation to update the user system with changes to the data in the centralized product catalogue wherein the incremental synchronization operation comprises updating the user system with changes to the data in the centralized product catalogue that occurred after the bulk synchronization operation.
6. The method as claimed in claim 5, wherein the centralized product catalogue is synchronized with the user system via RESTful application program interface (API) after the bulk synchronization operation.
7. The method as claimed in claim 1, wherein the workflow configuration defined for the user system comprises orchestration details, and wherein the workflow configuration facilitates in performing a one-time setup for the user system.
8. The method as claimed in claim 7, wherein, upon completion of the one-time setup, the user system facilitates in importing product data from the centralized product catalogue.
9. A system for synchronizing data between a centralized product catalogue and a user system, the system comprises:

a receiving unit [302] configured to receive a request from the user system for access to a centralized product catalogue comprising a plurality of products;
a generating unit [304] configured to generate an interface based on the request, wherein the generated interface comprises a set of data tables corresponding to at least one product of the plurality of products;
a processing unit [306] to configure a display associated with the user system based on the generated interface;
the processing unit [306] configured to define a workflow configuration for the user system, wherein the workflow configuration comprises at least one of a frequency of receiving updates from the centralized product catalogue and format of the set of data tables; and
a synchronizing unit [308] configured to synchronize the set of data tables at the user system with the centralized product catalogue based on the defined workflow.
10. The system as claimed in claim 9, comprises tracking unit configured to track a history of data transactions between the centralized product catalogue and the user system.
11. The system as claimed in claim 10, wherein tracking the history of data transactions further comprises logging each request for access to the centralized product catalogue and each synchronization operation performed.
12. The system as claimed in claim 9, wherein the synchronizing unit [308] configured to perform a bulk synchronization operation to transfer a large volume of data at once.

13. The system as claimed in claim 12, wherein the bulk synchronization operation is followed by an incremental synchronization operation to update the user system with changes to the data in the centralized product catalogue.
14. The system as claimed in claim 13, wherein the centralized product catalogue is synchronized with the user system via RESTful application program interface (API) after the bulk synchronization operation.
15. The system as claimed in claim 9, wherein the workflow configuration defined for the user system comprises orchestration details, and wherein the workflow configuration facilitates in performing a one-time setup for the user system.
16. The system as claimed in claim 15, wherein, upon completion of the one-time setup, the user system facilitates in importing product data from the centralized product catalogue.
17. A user equipment (UE) for synchronizing data between a centralized product catalogue and a user system comprising:
a processor configured to:
receive a request from the user system for access to a centralized product catalogue comprising a plurality of products;
generate an interface based on the request, wherein the generated interface comprises a set of data tables corresponding to at least one product of the plurality of products;
configure a display associated with the user system based on the generated interface;

define a workflow configuration for the user system, wherein the workflow configuration comprises at least one of a frequency of receiving updates from the centralized product catalogue and format of the set of data tables; and
synchronise the set of data tables at the user system with the centralized product catalogue based on the defined workflow.