FORM 2
THE PATENTS ACT, 1970 (39 OF 1970) & THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
“METHOD AND SYSTEM FOR NETWORK PROVISIONING
AND ACTIVATION”
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.

METHOD AND SYSTEM FOR NETWORK PROVISIONING AND
ACTIVATION
FIELD OF INVENTION
[0001] The present disclosure generally relates to wireless communication systems. More particularly, the present disclosure relates to a method and system for automatically provisioning a network activation using a plurality of provisioning and activation templates maintained in a cache memory or a database.
BACKGROUND OF THE DISCLOSURE
[0002] The following description of the 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 is used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of the prior art.
[0003] In today's digital age, businesses and individuals alike rely heavily on network connectivity to access information, communicate with others, and conduct transactions. As a result, network provisioning and activation have become critical components of network interaction with customer fulfilment stack in telecommunication industry, ensuring that services provided to the customers are properly provisioned in the network nodes and the services are activated quickly. Provisioning involves the initial setup and configuration of services or resources for a customer or user. It includes activities such as allocating network bandwidth, assigning Internet Protocol (IP) addresses, creating user accounts, and configuring hardware or software components necessary to deliver a specific service. Activation refers to the process of enabling or turning on a service that has been provisioned. Once a service or feature is provisioned, activation ensures that it is ready and

operational for the end-user or customer to use. Provisioning and activation requests are requests received from User Equipment(s) for network provisioning and network activation, respectively.
[0004] For the same reason, companies are constantly seeking new ways to improve efficiency of provisioning and activation requests so as to allow easy provision of new services or activate existing ones for their customers.
[0005] In order to properly provision and activate a network, use of a variety of different schemas and headers is necessary for requests due to the wide variety of systems and devices that are involved in the process. Each system may have its own unique requirements, and as such, a standardized format is needed to ensure that all parties can communicate effectively. Accordingly, it is essential to have the correct JavaScript Object Notation (JSON) schemas and header in place. However, the process of preparing the JSON schema and headers for these requests can be quite challenging.
[0006] Traditionally, developers have relied on hard-coded logic or hard configurability to define these parameters. One of the main challenges of using hard-coded or rigidly defined JSON parameters is that it can lead to long adaptation times. Whenever there is a change in the requirements, developers must spend a considerable amount of time updating the code to accommodate these changes. Another issue with hard-coded JSON parameters is that they can create clutter in the code as the business grows. As more parameters are added to the JSON schema, it becomes increasingly difficult to manage and maintain the codebase. This can lead to errors and bugs, which can have serious consequences for the network deployment process.
[0007] To address the challenges with hardcoded schemas, developers are turning towards a template-based approach for defining JSON parameters. With this approach, developers can define templates for different types of requests. However,

such templates need to be customized based on specific requirements, making it difficult to adapt to changes in the business environment.
[0008] Further, over the period of time various solutions have been developed to
5 properly provision and activate a network. However, there are certain challenges
with existing solutions such that these solutions are complex, especially when there are numerous parameters involved. Moreover, these approaches can be tedious and time-consuming, especially when requirements change.
10 [0009] Thus, there exists an imperative need in the art for more flexible approach
for preparing JSON schema and headers that may allow developers to define parameters in a more dynamic and adaptable way, as well as to allow accommodate changes in schemas, thereby reducing the adaptation time and improve the overall efficiency of the network provisioning and activation process, which the present
15 disclosure aims to address.
OBJECTS OF THE DISCLOSURE
[0010] Some of the objects of the present disclosure, which at least one
20 embodiment disclosed herein satisfies are listed herein below.
[0011] It is an object of the present disclosure to provide a system and a method to
define parameters in a more dynamic and adaptable way to reduce the adaptation
time and improve the overall efficiency of the network provisioning and activation
25 process.
[0012] It is another object of the present disclosure to provide a system for dynamically generating JavaScript Object Notation (JSON) schema and headers based on network requirements, for network provisioning and activation purposes. 30
4

[0013] It is another object of the present disclosure to provide a solution that can facilitate dynamic preparation of network provisioning and activation requests without any code-level dependency.
5 [0014] It is yet another object of the present disclosure to provide a solution to
automate the provisioning and activation request process, thereby saving time and resources while also ensuring that all requests are managed accurately and efficiently.
10 [0015] It is yet another object of the present disclosure to provide a solution that
easily adapt to changes in network topology, without having to manually update configuration files or scripts.
SUMMARY OF THE DISCLOSURE
15
[0016] 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.
20
[0017] An aspect of the present disclosure may relate to a method for automatically provisioning a network activation using a plurality of provisioning and activation templates maintained in a target memory. The method comprising receiving, by a transceiver unit, an order request comprising at least a product identifier (ID), a set
25 of request header parameters, a set of request body parameters, and one or more
other factors. Further, the method comprises fetching, by the transceiver unit from a target memory, one or more predefined order provisioning and activation templates based on the product ID associated with the order request. Further, the method comprises configuring, by a workflow configurator, a header workflow
30 associated with the set of request header parameters based on the one or more
predefined order provisioning and activation templates. Further, the method
5

comprises configuring, by the workflow configurator, a body workflow associated
with the set of request body parameters based on the one or more predefined order
provisioning and activation templates. Further, the method comprises fetching, by
the transceiver unit from a predefined product database, a set of product parameters
5 based on at least one of the product ID and a predefined product-order reference
value. Further, the method comprises generating, by a configuration generator, a
parameter configuration in a predefined parameter configuration format based on
at least the one or more other factors. Further, the method comprises generating, by
a request generator, a workflow request based on at least the header workflow, the
10 body workflow and the parameter configuration. Thereafter, the method comprises
automatically provisioning, by a provisioning unit, the network activation associated with the order request based on the workflow request.
[0018] In an exemplary aspect of the present disclosure, the header workflow is
15 configured based on at least one of the product ID associated with the order, a
service name request associated with the order, and a list of one or more predefined attribute-value pairs associated with the order, the one or more predefined attribute-value pairs comprising a workflow name pair, a service name pair, and a subscriber identity module (SIM) card type pair. 20
[0019] In an exemplary aspect of the present disclosure, the body workflow is configured based on at least one of the product ID associated with the order and a predefined workflow name associated with the order.
25 [0020] In an exemplary aspect of the present disclosure, the one or more other
factors are fetched from one or more entities comprising an order detail, a local product catalogue, and a reference value master.
[0021] In an exemplary aspect of the present disclosure, the method further
30 comprises creating, by the request generator, a configuration file request for a single
6

workflow engine, the configuration file request comprising a set of configuration elements, one or more request headers.
[0022] In an exemplary aspect of the present disclosure, the target memory is one
5 of a cache memory and a database.
[0023] In an exemplary aspect of the present disclosure, the header workflow is associated with a set of headers, wherein each header from the set of headers is a header sent in a RESTful Application Programming Interface (API).
10
[0024] In an exemplary aspect of the present disclosure, the header workflow comprises a set of configurations for a set of APIs to be invoked and a set of parameter values corresponding to the set of configurations, to cater one or more request header parameters associated with the set of APIs to be invoked.
15
[0025] In an exemplary aspect of the present disclosure, in an event a parameter value from the set of parameter values is dynamic and is associated with at least one of a customer order and a product catalogue, an Xpath of a customer order JavaScript Object Notation (JSON) schema is defined in a configuration
20 corresponding to said parameter value, to determine a value stored at an Xpath of
an order received to invoke an API and to cater one or more headers associated with said order.
[0026] In an exemplary aspect of the present disclosure, in an event the
25 configuration corresponding to the parameter value is associated with the product
catalogue then at least one of a product catalogue table, a response filed as a final value and one or more input parameters are identified, wherein the one or more input parameters are one or more parameters to be extracted from the customer order based on the Xpath. 30
7

[0027] In an exemplary aspect of the present disclosure, the set of product
parameters is fetched from the predefined product database to identify additional
information related to one or more parameters associated with the order request,
wherein the additional information comprises at least one of a product name, a
5 product billing type, one or more services and one or more features related to one
or more catalogue-driven enrichments.
[0028] In an exemplary aspect of the present disclosure, the parameter
configuration is associated with a value derived from at least one of a persisted
10 order in the predefined product database, one or more customer details, a master
reference value and a product catalogue data.
[0029] In an exemplary aspect of the present disclosure, the parameter
configuration is associated with an information: for picking a value for a
15 corresponding parameter and for configuration of the corresponding parameter, in
production environment during a server on which said corresponding parameter is to be configured is in a running state.
[0030] Another aspect of the present disclosure may relate to a system for
20 automatically provisioning a network activation using a plurality of provisioning
and activation templates maintained in a target memory, the system comprising a
transceiver unit configured to: receive, an order request comprising at least a
product identifier (ID), a set of request header parameters, a set of request body
parameters, and one or more other factors; and fetch, from a target memory, one or
25 more predefined order provisioning and activation templates based on the product
ID associated with the order request. Further, the system comprises a workflow
configurator connected to at least the transceiver unit, the workflow configurator
configured to: configure, a header workflow associated with the set of request
header parameters based on the one or more predefined order provisioning and
30 activation templates; and configure, a body workflow associated with the set of
request body parameters based on the one or more predefined order provisioning
8

and activation templates. The transceiver unit is further configured to fetch, from a
predefined product database, a set of product parameters based on at least one of
the product ID and a predefined product-order reference value. The system also
comprises a configuration generator connected to at least the transceiver unit, the
5 configuration generator is configured to generate, a parameter configuration in a
predefined parameter configuration format based on at least one or more other
factors. Further, the system comprises a request generator connected to at least the
configuration generator, the request generator configured to generate, a workflow
request based on at least the header workflow, the body workflow and the parameter
10 configuration. Also, the system comprises a provisioning unit connected to at least
the request generator, the provisioning unit is configured to automatically provision, the network activation associated with the order request based on the workflow request.
15 [0031] Yet another aspect of the present disclosure may relate to a non-transitory
computer readable storage medium storing instructions for automatically provisioning a network activation using a plurality of provisioning and activation templates maintained in a target memory, the instructions include executable code which, when executed by one or more units of a system causes a transceiver unit to
20 receive, an order request comprising at least a product identifier (ID), a set of
request header parameters, a set of request body parameters, and one or more other factors. Further, the instructions include executable code, which when executed causes the transceiver unit to fetch, from a target memory, one or more predefined order provisioning and activation templates based on the product ID associated with
25 the order request. Further, the instructions include executable code, which when
executed causes a workflow configurator to configure, a header workflow associated with the set of request header parameters based on the one or more predefined order provisioning and activation templates. Further, the instructions include executable code, which when executed causes the workflow configurator
30 to configure, a body workflow associated with the set of request body parameters
based on the one or more predefined order provisioning and activation templates.
9

Further, the instructions include executable code, which when executed causes the
transceiver unit to fetch, from a predefined product database, a set of product
parameters based on at least one of the product ID and a predefined product-order
reference value. Further, the instructions include executable code, which when
5 executed causes a configuration generator to generate, a parameter configuration in
a predefined parameter configuration format based on at least one or more other
factors. Further, the instructions include executable code, which when executed
causes a request generator to generate, a workflow request based on at least the
header workflow, the body workflow and the parameter configuration. Further, the
10 instructions include executable code, which when executed causes a provisioning
unit to automatically provision, the network activation associated with the order request based on the workflow request.
[0032] Yet another aspect of the present disclosure may relate to User Equipment
15 (UE), comprising a transceiver unit, configured to transmit an order request to
execute network activation; and receive from the system, a response to the order request, wherein the response comprises an indication of network activation, and the response is generated at the system based on: receiving, by a transceiver unit, an order request comprising at least a product identifier (ID), a set of request header
20 parameters, a set of request body parameters, and one or more other factors;
fetching, by the transceiver unit from a target memory, one or more predefined order provisioning and activation templates based on the product ID associated with the order request; configuring, by a workflow configurator, a header workflow associated with the set of request header parameters based on the one or more
25 predefined order provisioning and activation templates; configuring, by the
workflow configurator, a body workflow associated with the set of request body parameters based on the one or more predefined order provisioning and activation templates; fetching, by the transceiver unit from a predefined product database, a set of product parameters based on at least one of the product ID and a predefined
30 product-order reference value; generating, by a configuration generator, a
parameter configuration in a predefined parameter configuration format based on
10

at least the one or more other factors; generating, by a request generator, a workflow request based on at least the header workflow, the body workflow and the parameter configuration; and automatically provisioning, by a provisioning unit, the network activation associated with the order request based on the workflow request. 5
BRIEF DESCRIPTION OF THE DRAWINGS
[0033] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods
10 and systems in which like reference numerals refer to the same parts throughout the
different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. 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
15 according to the disclosure are illustrated herein to highlight the 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.
20 [0034] FIG. 1 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.
[0035] FIG. 2 illustrates an exemplary block diagram of a system for automatically
25 provisioning a network activation using a plurality of provisioning and activation
templates maintained in a target memory, in accordance with exemplary implementations of the present disclosure.
[0036] FIG. 3 illustrates an exemplary method flow diagram indicating a method
30 for automatically provisioning a network activation using a plurality of
11

provisioning and activation templates maintained in a target memory, in accordance with exemplary implementations of the present disclosure.
[0037] FIG.4 illustrates an exemplary implementation environment for
5 provisioning a network activation using a plurality of provisioning and activation
templates maintained in a target memory, in accordance with exemplary implementations of the present disclosure.
[0038] The foregoing shall be more apparent from the following more detailed
10 description of the disclosure.
DETAILED DESCRIPTION
[0039] In the following description, for the purposes of explanation, various
15 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
another or with any combination of other features. An individual feature may not
20 address any of the problems discussed above or might address only some of the
problems discussed above.
[0040] The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather,
25 the ensuing description of the exemplary embodiments will provide those skilled in
the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.
30
12

[0041] Specific details are given in the following description to provide a thorough
understanding of the embodiments. However, it will be understood by one of
ordinary skill in the art that the embodiments may be practiced without these
specific details. For example, circuits, systems, processes, and other components
5 may be shown as components in block diagram form in order not to obscure the
embodiments in unnecessary detail.
[0042] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various components/units can be
10 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
15 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.
[0043] Also, it is noted that individual embodiments may be described as a process
20 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 steps not
25 included in a figure.
[0044] 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
30 aspect or design described herein as “exemplary” and/or “demonstrative” is not
necessarily to be construed as preferred or advantageous over other aspects or
13

designs, nor is it meant to preclude equivalent exemplary structures and techniques
known to those of ordinary skill in the art. Furthermore, to the extent that the terms
“includes,” “has,” “contains,” and other similar words are used in either the detailed
description or the claims, such terms are intended to be inclusive—in a manner
5 similar to the term “comprising” as an open transition word—without precluding
any additional or other elements.
[0045] As used herein, a “processing unit” or “processor” or “operating processor” includes one or more processors, wherein processor refers to any logic circuitry for
10 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 microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of
15 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 processor.
20 [0046] 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 communication device” may be any electrical, electronic and/or computing device or equipment, capable of implementing one or more features of the present
25 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 of implementing the one or more features of the present disclosure. Also, the user device may contain at least one input means configured to receive an input
30 from unit(s) which are required to implement the one or more features of the present
disclosure.
14

[0047] 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
5 medium includes read-only memory (“ROM”), random access memory (“RAM”),
magnetic disk storage media, optical storage media, flash memory devices or other 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.
10
[0048] As used herein “interface” or “user interface refers to a shared boundary across which two or more separate components of a system exchange information 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
15 each other, which also includes the methods, functions, or procedures that may be
called.
[0049] All modules, units, components used herein, unless explicitly excluded herein, may be software modules or hardware processors, the processors being a
20 general-purpose processor, a special purpose processor, a conventional processor, a
digital signal processor (DSP), a plurality of microprocessors, one or more 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.
25
[0050] As used herein the transceiver unit includes at least one receiver and at 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.
30
15

[0051] Network provisioning specifically refers to the processes involved in configuring and activating network resources to deliver telecommunication services to customers This includes setting up routers, switches, firewalls, servers, and other network components to ensure that they are working together seamlessly. 5
[0052] Activation involves turning on the network services and resources that have been provisioned. This includes activating user accounts, setting up security protocols, and configuring network settings to ensure that users can access the network and its resources.
10
[0053] JavaScript Object Notation (JSON) schema is a tool that allows developers to define the structure of JSON data. It provides a way to validate JSON data against a schema, ensuring that the data is in the correct format. JSON Schema is particularly useful for network provisioning and activation requests, as it ensures
15 that the data being sent is in the correct format, reducing the risk of errors and
delays.
[0054] Headers are pieces of information that are transmitted along with the
request. They provide additional information about the request, such as the type of
20 data being sent, the format of the data, and the authentication credentials required
to access the requested resource.
[0055] As discussed in the background section, the current known solutions for improving efficiency of provisioning and activation requests so as to allow easy
25 provision of new services or to activate existing ones for the customers, have several
shortcomings such as the process is complex, especially when there are numerous parameters involved. Further, in the existing solutions, the usage of hard-coded or rigidly defined JSON parameters lead to long adaptation times. In the existing arts whenever there is a change in the requirements, developers need to spend a
30 considerable amount of time updating the code to accommodate these changes.
Moreover, in the existing arts as more parameters are added to the JSON schema, it
16

becomes increasingly difficult to manage and maintain the codebase leading to errors and bugs. The existing approaches are tedious and time-consuming, especially when requirements change.
5 [0056] The present disclosure aims to overcome the above-mentioned and other
existing problems in this field of technology by providing flexible approach for preparing JSON schema and headers that may allow developers to define parameters in a more dynamic and adaptable way. The present disclosure discloses a set of templates provided with configurable entities that are used to define the
10 schema and header in accordance with the network requirements. These entities
include data types, data structures, headers, and rules. Each entity can be customized to meet the specific needs of the network deployment. For example, developers can define their own data types, such as integers, strings, or custom objects. They can also define their own data structures, which can be used to
15 organize and manipulate data in a hierarchical manner.
[0057] In addition to the configurable entities, the system also provides possibility
of creation of custom logic for JSON schema and headers. This logic allows
developers to define their own rules for validating JSON data and headers. For
20 example, developers can define rules that enforce certain data types or values for
specific fields. They can also define rules that validate custom headers or modify existing headers.
[0058] Hereinafter, exemplary embodiments of the present disclosure will be
25 described with reference to the accompanying drawings.
[0059] FIG. 1 illustrates an exemplary block diagram of a computing device [100]
upon which the features of the present disclosure may be implemented in
accordance with exemplary implementation of the present disclosure. In an
30 implementation, the computing device [100] may be in communication with a
communication network and may implement a method for automatically
17

provisioning a network activation using a plurality of provisioning and activation
templates maintained in a target memory. In another implementation, the computing
device [100] in communication with the communication network, itself implements
the method for automatically provisioning a network activation using a plurality of
5 provisioning and activation templates maintained in a target memory, using one or
more units present within the computing device [100], wherein a person skilled in the art would appreciate that said one or more units are capable of implementing the features as disclosed in the present disclosure.
10 [0060] The computing device [100] may include a bus [102] or other
communication mechanism for communicating information, and a hardware
processor [104] coupled with bus [102] for processing information. The hardware
processor [104] may be, for example, a general-purpose microprocessor. The
computing device [100] may also include a main memory [106], such as a random-
15 access memory (RAM), or other dynamic storage device, coupled to the bus [102]
for storing information and instructions to be executed by the processor [104]. The
main memory [106] also may be used for storing temporary variables or other
intermediate information during execution of the instructions to be executed by the
processor [104]. Such instructions, when stored in non-transitory storage media
20 accessible to the processor [104], render the computing device [100] into a special-
purpose machine that is customized to perform the operations specified in the
instructions. The computing device [100] further includes a read only memory
(ROM) [108] or other static storage device coupled to the bus [102] for storing static
information and instructions for the processor [104].
25
[0061] A storage device [110], such as a magnetic disk, optical disk, or solid-state
drive is provided and coupled to the bus [102] for storing information and
instructions. The computing device [100] may be coupled via the bus [102] to a
display [112], such as a cathode ray tube (CRT), Liquid crystal Display (LCD),
30 Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for
displaying information to a computer user. An input device [114], including
18

alphanumeric and other keys, touch screen input means, etc. may be coupled to the
bus [102] for communicating information and command selections to the processor
[104]. Another type of user input device may be a cursor controller [116], such as a
mouse, a trackball, or cursor direction keys, for communicating direction
5 information and command selections to the processor [104], and for controlling
cursor movement on the display [112]. 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 the device to specify positions in a plane.
10 [0062] The computing device [100] 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 [100] causes or programs the computing device [100] to be a special-purpose machine. According to one implementation, the techniques herein are performed by the
15 computing device [100] in response to the processor [104] executing one or more
sequences of one or more instructions contained in the main memory [106]. Such instructions may be read into the main memory [106] from another storage medium, such as the storage device [110]. Execution of the sequences of instructions contained in the main memory [106] causes the processor [104] to perform the
20 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.
[0063] The computing device [100] also may include a communication interface
25 [1018] coupled to the bus [102]. The communication interface [118] provides a two-
way data communication coupling to a network link [120] that is connected to a
local network [122]. For example, the communication interface [118] may be an
integrated services digital network (ISDN) card, cable modem, satellite modem, or
a modem to provide a data communication connection to a corresponding type of
30 telephone line. As another example, the communication interface [118] may be a
local area network (LAN) card to provide a data communication connection to a
19

compatible LAN. Wireless links may also be implemented. In any such implementation, the communication interface [118] sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information. 5
[0064] The computing device [100] can send messages and receive data, including
program code, through the network(s), the network link [120] and the
communication interface [118]. In the Internet example, a server [130] might
transmit a requested code for an application program through the Internet [128], the
10 Internet Service Provider (ISP) [126], the local network [122], the host [124] and
the communication interface [118]. The received code may be executed by the processor [104] as it is received, and/or stored in the storage device [110], or other non-volatile storage for later execution.
15 [0065] The computing device [100] encompasses a wide range of electronic
devices capable of processing data and performing computations. Examples of computing device [100] include, but are not limited only to, personal computers, laptops, tablets, smartphones, servers, and embedded systems. The devices may 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 [100]
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.
25 [0066] Referring to FIG. 2, an exemplary block diagram of a system [200] for
automatically provisioning a network activation using a plurality of provisioning and activation templates maintained in a target memory [204], is shown, in accordance with the exemplary implementations of the present disclosure. The system [200] comprises a transceiver unit [202], a target memory [204], a workflow
30 configurator [206], a configuration generator [208], a request generator [210], and
a provisioning unit [212]. Also, all of the components/ units of the system [200] are
20

assumed to be connected to each other unless otherwise indicated below. Also, in
Fig. 2 only a few units are shown, however, the system [200] may comprise multiple
such units or the system [200] may comprise any such numbers of said units, as
required to implement the features of the present disclosure. Further, in an
5 implementation, the system [200] may be in communication with the user device
(may also referred to herein as a user equipment or UE). In another implementation, the system [200] may reside in a server or at a network entity.
[0067] The system [200] is configured for automatically provisioning the network
10 activation using the plurality of provisioning and activation templates maintained
in the target memory [204], with the help of the interconnection between the
components/units of the system [200]. Network activation refers to the process of
setting up or enabling a network service or connection for use. This may involve
various steps and configurations depending on the type of network and the specific
15 requirements of the service being activated.
[0068] The system comprises the transceiver unit [202] that is configured to
receive, an order request comprising at least a product identifier (ID), a set of
request header parameters, a set of request body parameters, and one or more other
20 factors. Further, the transceiver unit [202] fetches, from a target memory [204], one
or more predefined order provisioning and activation templates based on the product ID associated with the order request. The target memory [204] is one of a cache memory and a database.
25 [0069] The product ID refers to a unique identifier assigned to each product or
service offered by a service provider. Order provisioning and activation templates act as standardized templates stored in the target memory [204], specifically designed to guide the provisioning process for different products or services based on specific product identifiers (IDs) received in order requests. These templates
30 serve as predefined frameworks that outline the sequence of steps and
configurations required to provision a particular product or service effectively. The
21

method aims to automate the process of provisioning network activation using the
predefined provisioning and activation templates stored in a designated memory
location such as the target memory [204]. The transceiver unit [202] retrieves the
one or more predefined order provisioning and activation templates from the
5 designated target memory [204]. The selection of templates is based on the product
ID associated with the order request. Each product or service typically has specific
configuration requirements, and these templates contain predefined settings and
parameters necessary for provisioning and activating the corresponding network
services. By fetching the templates based on the product ID, the system ensures that
10 the activation process is tailored to the specific requirements of the order. This
approach streamlines the configuration process, ensuring consistency, accuracy, and efficiency in deploying network services according to the customer's order specifications.
15 [0070] The request header parameters may include but not limited to a Product
Identity (ID), a service name, and a list of attribute-value pairs, which includes but not limited to workflow name, service-name, and Subscriber Identity Module (SIM)-card-type etc. The request body parameters may include but not limited to, the product ID and the workflow name. The one or more other factors are fetched
20 from one or more entities comprising an order detail, a local product catalogue, and
a reference value master. The order detail may include specific information detailing the characteristics and requirements of an order. The local product catalogue refers to a repository or database containing comprehensive information about products and services available within a specific context or domain. The
25 reference value master refers to a central repository or database that stores
standardized reference values, constants, or master data used across multiple systems or processes. For example, the reference value master act as the centralized data repository managed within a Customer Relationship Management (CRM) system, specifically for storing lists of values related to customer or enterprise
30 attributes.
22

[0071] For example, a reference value master (e.g., a separate data space CRM
maintains for customer/enterprise related List of Values (LOVs)). LOVs are
essentially controlled vocabularies or catalogues of permissible values for specific
fields or attributes within a system. They serve as reference data to standardize
5 inputs and ensure that data entered into a system conforms to predefined criteria.
Some data in persisted order are to be mapped first to respective code or name and
then sent to a Fulfilment Management Systems (FMS). For e.g., a salutation field
in customer Name comes as 1 in order. In the FMS, a value corresponding to 1 (i.e.
“Mr”) need to be sent. Hence, a query for a reference data service with ID = 1 as
10 input and get name = Mr. in return.
[0072] Further, the workflow configurator [206] is connected to at least the transceiver unit [202], the workflow configurator [206] configures, a header workflow associated with the set of request header parameters based on the one or
15 more predefined order provisioning and activation templates. Further, the workflow
configurator [206] configures, a body workflow associated with the set of request body parameters based on the one or more predefined order provisioning and activation templates. Utilizing the predefined order provisioning and activation templates, the workflow configurator [206] selects templates that provide strategic
20 guidance and establish the overall structure for the header workflow. The header
workflow is configured based on at least one of the product ID associated with the order, a service name request associated with the order, and a list of one or more predefined attribute-value pairs associated with the order. The one or more predefined attribute-value pairs comprising a workflow name pair, a service name
25 pair, and a subscriber identity module (SIM) card type pair. The body workflow is
configured based on at least one of the product ID associated with the order and a predefined workflow name associated with the order.
[0073] The workflow configurator [206] refers to a component of the system
30 responsible for configuring workflows based on predefined templates and order
parameter. The workflow configurator [206] adjusts or sets up workflows according
23

to the specifics provided in the order request, ensuring that both header and body
workflows are appropriately configured for processing. Based on the received
request, body parameters, which typically include details such as customer
information, product/service specifications, and activation requirements, the
5 workflow configurator [206] identifies which sections or parameters within the
order provisioning and activation templates need to be populated or customized. The body workflow is then structured as a series of tasks or steps that correspond to actions defined in the templates. Each task within the workflow represents a specific configuration action or process that must be executed to complete the
10 activation successfully. The workflow configurator [206] inserts the received
request body parameters into the appropriate fields or placeholders within the templates. This step ensures that the configurations align with the specific details and requirements of the order request. The header workflow is configured to handle metadata and high-level details associated with the order request, such as product
15 identity, service names, and other header parameters, ensuring correct processing
and routing of the request. Body workflow refers to a sequence or set of actions defined in the system's processes that pertain to the body parameters of an order request. The workflow engine may be an application that runs digital workflow software.
20
[0074] The header workflow is associated with a set of headers, wherein each header from the set of headers is a header sent in a RESTful Application Programming Interface (API). The header workflow comprises a set of configurations for a set of APIs to be invoked and a set of parameter values
25 corresponding to the set of configurations, to cater one or more request header
parameters associated with the set of APIs to be invoked. The request header parameters are crucial pieces of information sent along with API requests to provide additional context or instructions to a receiving server. The header workflow ensures that these request header parameters are appropriately configured and
30 included when invoking each API in the set. The set of APIs refers to a cohesive
group of Application Programming Interfaces (APIs) that are specifically selected
24

and configured to perform a series of related tasks or operations within the header
workflow. In an event where a parameter value from the set of parameter values is
dynamic and is associated with at least one of a customer order and a product
catalogue, an Xpath of a customer order JavaScript Object Notation (JSON) schema
5 is defined in a configuration corresponding to said parameter value, to determine a
value stored at an Xpath of an order received to invoke an API and to cater one or more headers associated with said order. The dynamic parameter value refers to a parameter value that is not fixed and can change based on circumstances such as customer orders or updates in the product catalogue. In an event if a parameter value
10 is dynamic and relates to a customer order or a product catalogue, then in a
configuration corresponding to said parameter value an Xpath of customer order JSON schema is defined. The Xpath of customer order JSON schema is defined to determine a value stored at an Xpath of an order received to invoke an API and to cater one or more headers associated with said order. Xpath is a query language
15 used to navigate through elements and attributes within extensible Markup
Language (XML) documents. It provides a standardized way to locate and select nodes in an XML document tree, allowing for precise querying and extraction of data based on specific criteria.
20 [0075] The set of parameter values are essential for determining how APIs should
behave or respond to specific requests, ensuring flexibility and customization in API interactions. The product catalogue provides essential information used to dynamically configure API requests based on current product offerings and specifications. The Xpath is a query language that used to navigate through
25 elements and attributes in XML and JSON documents.
[0076] In an event the configuration corresponding to the parameter value is
associated with the product catalogue then at least one of a product catalogue table,
a response filed as a final value and one or more input parameters are identified.
30 The one or more input parameters are one or more parameters to be extracted from
the customer order based on the Xpath. The product catalogue table refers to a
25

structured representation of product catalogue information, often organized into tables for systematic access and management.
[0077] The transceiver unit [202] is further configured to fetch, from a predefined
5 product database, a set of product parameters based on at least one of the product
ID and a predefined product-order reference value. Using established communication protocols and database connectivity mechanisms, the transceiver unit [202] sends a query to the predefined product database. Upon receiving the query, the predefined product database processes the request and retrieves the
10 corresponding set of product parameters that match the specified product ID and/or
predefined product-order reference value. Once retrieved, the product parameters are transmitted back to the transceiver unit [202]. The predefined product-order reference value refers to a unique identifier or a reference number associated with a specific order placed for a service. The set of product parameters is fetched from
15 the predefined product database to identify additional information related to one or
more parameters associated with the order request, wherein the additional information comprises at least one of a product name, a product billing type, one or more services and one or more features related to one or more catalogue-driven enrichments. In the context of managing products within a system, a “predefined
20 product database” can serve as a “product catalogue”. The set of product parameters
may include a product name, a product billing type, services, features, etc.
[0078] The configuration generator [208] is connected to at least the transceiver unit [202], the configuration generator [208] configured to generate, a parameter
25 configuration in a predefined parameter configuration format based on at least the
one or more other factors. These other factors may include customer requirements, network infrastructure, regulatory compliance, service level agreements, and operational policies. The configuration generator [208] adheres to the predefined parameter configuration format. This format specifies how parameters should be
30 structured, organized, and formatted to ensure consistency and compatibility within
the system. Upon receiving the fetched product parameters and other relevant
26

factors, the configuration generator [208] processes this data to determine how
parameters should be configured and outputs the parameter configuration in the
predefined format. Parameter configuration is a structured set (which may be
construed as a collection or grouping of elements that is organized according to a
5 defined format) of instructions or settings that define how parameters should be
formatted or processed within a system or application. Parameter configurations specify the rules, formats, and relationships governing how parameters are defined, validated, and utilized in various processes. The parameter configuration is associated with a value derived from at least one of a persisted order in the
10 predefined product database, one or more customer details, a master reference value
and a product catalogue data. Here, the product catalogue data refers to a structured repository of information that details the network-related products and services available for provisioning and management. The parameter configuration is associated with an information: for picking a value for a corresponding parameter
15 and for configuration of the corresponding parameter, in production environment
during a server on which said corresponding parameter is to be configured is in a running state. For example, a telecom company offering various mobile plans. The parameter configuration for a new customer's service activation (e.g., data allowance, voice minutes) might be influenced by the specific mobile plan they
20 have chosen. The configuration generator [208] would refer to the persisted order
in the product database to determine the exact parameters and settings associated with the selected plan. For example, suppose a customer such as Mr. ABC signs up for a new 4G data plan. Parameter configurations for ABC’s personal details (first Name, last Name, salutation) are used for account creation and billing purposes.
25 The plan details such as planID and productofferID specify the exact service
package Mr. ABC has selected. The service details (service id, name) indicate that ABC’s plan includes access to 4G data services. This parameter configuration would be sent from a Customer Relationship Management (CRM) system to a backend provisioning system (like FMS - Fulfilment Management System)
30 responsible for activating John's chosen 4G data plan.
27

[0079] The request generator [210] is connected to at least the configuration
generator [208], the request generator [210] is configured to generate, a workflow
request based on at least the header workflow, the body workflow and the parameter
configuration. The request generator [210] is further configured to create a
5 configuration file request for a single workflow engine, the configuration file
request comprising a set of configuration elements, and one or more request headers. The configuration file request refers to generating a configuration file, for the purpose of initiating and defining a workflow within a single workflow engine. For example, consider a software platform for project management where users can
10 initiate new projects. The request generator [210] takes inputs such as project details
(header workflow), project tasks and timelines (body workflow), and specific project settings (parameter configuration). The request generator [210] then creates a configuration file request tailored for the platform’s workflow engine. This request includes all necessary configurations like task dependencies, deadlines, and
15 project milestones, along with headers specifying project priority and team
members involved. This comprehensive request ensures that the project can be accurately executed according to the predefined workflow and settings within the system.
20 [0080] Thereafter, the provisioning unit [212] is configured to automatically
provision, the network activation associated with the order request based on the workflow request. For example, a customer has placed an order for a new service, such as activating a new mobile phone line, setting up broadband internet, or adding a new feature to an existing service. The request generator [210] receives the
25 customer’s order details and creates a workflow request. The provisioning unit
[212] is responsible for carrying out the technical provisioning tasks based on the workflow request received from the request generator [210]. The provisioning unit [212] executes these tasks swiftly and efficiently, ensuring minimal delay between the customer’s order placement and service activation. Once the network activation
30 process is completed, the system generates notifications or updates for both the
customer and internal teams, confirming successful service activation.
28

[0081] Referring to FIG.3, an exemplary flow diagram of a method [300] for
automatically provisioning a network activation using a plurality of provisioning
and activation templates maintained in a target memory [204] in accordance with
5 exemplary implementations of the present disclosure is shown. In an
implementation the method [300] is performed by the system [200]. Further, in an implementation, the system [200] may be present in a server device to implement the features of the present disclosure. Also, as shown in Fig. 3, the method [300] starts at step [302].
10
[0082] At step [304], the method comprises receiving, by a transceiver unit [202], an order request comprising at least a product identifier (ID), a set of request header parameters, a set of request body parameters, and one or more other factors. The one or more other factors are fetched from one or more entities comprising an order
15 detail, a local product catalogue, and a reference value master. Further at step [306],
the method comprises fetching, by the transceiver unit [202] from the target memory [204], one or more predefined order provisioning and activation templates based on the product ID associated with the order request. The target memory [204] is one of a cache memory and a database.
20
[0083] The product ID refers to a unique identifier assigned to each product or service offered by a service provider. Order provisioning and activation templates act as standardized templates stored in the target memory [204], specifically designed to guide the provisioning process for different products or services based
25 on specific product identifiers (IDs) received in order requests. These templates
serve as predefined frameworks that outline the sequence of steps and configurations required to provision a particular product or service effectively.
[0084] The request header parameters may include but not limited to a Product
30 Identity (ID), a service name, and a list of attribute-value pairs, which includes but
not limited to workflow name, service-name, and Subscriber Identity Module
29

(SIM)-card-type etc. The request body parameters may include but not limited to,
the product ID and the workflow name. The one or more other factors are fetched
from one or more entities comprising an order detail, a local product catalogue, and
a reference value master. The order detail may include specific information
5 detailing the characteristics and requirements of an order. The local product
catalogue refers to a repository or database containing comprehensive information
about products and services available within a specific context or domain. The
reference value master refers to a central repository or database that stores
standardized reference values, constants, or master data used across multiple
10 systems or processes. For example, the reference value master act as the centralized
data repository managed within a Customer Relationship Management (CRM) system, specifically for storing lists of values related to customer or enterprise attributes.
15 [0085] For example, a reference value master (e.g., a separate data space CRM
maintains for customer/enterprise related List of Values (LOVs)). LOVs are essentially controlled vocabularies or catalogues of permissible values for specific fields or attributes within a system. They serve as reference data to standardize inputs and ensure that data entered into a system conforms to predefined criteria.
20 Some data in persisted order are to be mapped first to respective code or name and
then sent to Fulfilment Management Systems (FMS). For e.g., a salutation field in customer Name comes as 1 in order. In the FMS, a value corresponding to 1 (i.e. “Mr”) need to be sent. Hence, a query for a reference data service with ID = 1 as input and get name = Mr. in return.
25
[0086] At step [308], the method comprises configuring, by a workflow
configurator [206], a header workflow associated with the set of request header
parameters based on the one or more predefined order provisioning and activation
30 templates.
30

[0087] The header workflow is configured based on at least one of the product ID
associated with the order, a service name request associated with the order, and a
list of one or more predefined attribute-value pairs associated with the order. The
one or more predefined attribute-value pairs comprising a workflow name pair, a
5 service name pair, and a subscriber identity module (SIM) card type pair. The
header workflow is associated with a set of headers, wherein each header from the set of headers is a header sent in a RESTful Application Programming Interface (API). The header workflow comprises a set of configurations for a set of APIs to be invoked and a set of parameter values corresponding to the set of configurations,
10 to cater one or more request header parameters associated with the set of APIs to be
invoked. In an event a parameter value from the set of parameter values is dynamic and is associated with at least one of a customer order and a product catalogue, an Xpath of a customer order JavaScript Object Notation (JSON) schema is defined in a configuration corresponding to said parameter value, to determine a value stored
15 at an Xpath of an order received to invoke an API and to cater one or more headers
associated with said order. In an event the configuration corresponding to the parameter value is associated with the product catalogue then at least one of a product catalogue table, a response filed as a final value and one or more input parameters are identified, wherein the one or more input parameters are one or more
20 parameters to be extracted from the customer order based on the Xpath.
[0088] The set of parameter values are essential for determining how APIs should
behave or respond to specific requests, ensuring flexibility and customization in
API interactions. The product catalogue provides essential information used to
25 dynamically configure API requests based on current product offerings and
specifications. The Xpath is a query language that used to navigate through elements and attributes in XML and JSON documents.
[0089] In an event the configuration corresponding to the parameter value is
30 associated with the product catalogue then at least one of a product catalogue table,
a response filed as a final value and one or more input parameters are identified.
31

The one or more input parameters are one or more parameters to be extracted from the customer order based on the Xpath. The product catalogue table refers to a structured representation of product catalogue information, often organized into tables for systematic access and management. 5
[0090] At step [310], the method comprises configuring, by the workflow
configurator [206], a body workflow associated with the set of request body
parameters based on the one or more predefined order provisioning and activation
templates. The body workflow is configured based on at least one of the product ID
10 associated with the order and a predefined workflow name associated with the
order.
[0091] The workflow configurator [206] refers to a component of the system responsible for configuring workflows based on predefined templates and order
15 parameter. The workflow configurator [206] adjusts or sets up workflows according
to the specifics provided in the order request, ensuring that both header and body workflows are appropriately configured for processing. The header workflow is configured to handle metadata and high-level details associated with the order request, such as product identity, service names, and other header parameters,
20 ensuring correct processing and routing of the request. Body workflow refers to a
sequence or set of actions defined in the system's processes that pertain to the body parameters of an order request. The workflow engine may be an application that runs digital workflow software.
25 [0092] At step [312], the method comprises fetching, by the transceiver unit [202]
from a predefined product database, a set of product parameters based on at least one of the product ID and a predefined product-order reference value. The set of product parameters is fetched from the predefined product database to identify additional information related to one or more parameters associated with the order
30 request, wherein the additional information comprises at least one of a product
name, a product billing type, one or more services and one or more features related
32

to one or more catalogue-driven enrichments. In the context of managing products
within a system, a “predefined product database” can serve as a “product
catalogue”. The set of product parameters may include a product name, a product
billing type, services, features, etc. The predefined product database refers to a
5 structured repository or database within an information system that stores detailed
information about various products offered by a company or organization. The product catalogue is a curated subset or representation of the predefined product database that is tailored for specific purposes such as sales, marketing, or customer interactions.
10
[0093] At step [314], the method comprises generating, by a configuration generator [208], a parameter configuration in a predefined parameter configuration format based on at least the one or more other factors. Parameter configuration is a structured set of instructions or settings that define how parameters should be
15 formatted or processed within a system or application. Parameter configurations
specify the rules, formats, and relationships governing how parameters are defined, validated, and utilized in various processes. The parameter configuration is associated with a value derived from at least one of a persisted order in the predefined product database, one or more customer details, a master reference value
20 and a product catalogue data. The parameter configuration is associated with an
information: for picking a value for a corresponding parameter and for configuration of the corresponding parameter, in production environment during a server on which said corresponding parameter is to be configured is in a running state.
25
[0094] At step [316], the method comprises generating, by a request generator [210], a workflow request based on at least the header workflow, the body workflow and the parameter configuration. The method further comprises creating, by the request generator [210], a configuration file request for a single workflow engine,
30 the configuration file request comprising a set of configuration elements, one or
more request headers. For example, consider a software platform for project
33

management where users can initiate new projects. The request generator [210]
takes inputs such as project details (e.g., header workflow), project tasks and
timelines (e.g., body workflow), and specific project settings (e.g., parameter
configuration). The request generator [210] then creates a configuration file request
5 tailored for the platform’s workflow engine. This request includes all necessary
configurations like task dependencies, deadlines, and project milestones, along with headers specifying project priority and team members involved. This comprehensive request ensures that the project can be accurately executed according to the predefined workflow and settings within the system.
10
[0095] At step [318], the method comprises automatically provisioning, by a provisioning unit [212], the network activation associated with the order request based on the workflow request. For example, a customer has placed an order for a new service, such as activating a new mobile phone line, setting up broadband
15 internet, or adding a new feature to an existing service. The request generator [210]
receives the customer’s order details and creates a workflow request. The provisioning unit [212] is responsible for carrying out the technical provisioning tasks based on the workflow request received from the request generator [210]. The provisioning unit [212] executes these tasks swiftly and efficiently, ensuring
20 minimal delay between the customer’s order placement and service activation.
Once the network activation process is completed, the system generates notifications or updates for both the customer and internal teams, confirming successful service activation.
25 [0096] Thereafter, at step [320], the method [300] is terminated.
[0097] FIG.4 illustrates an exemplary implementation environment for
provisioning a network activation using a plurality of provisioning and activation
templates maintained in a target memory, in accordance with exemplary
30 implementations of the present disclosure.
34

[0098] In a preferred embodiment, the implementation environment [400]
comprises a plurality of components. For example, and by no way limiting the scope
of the present subject matter, the implementation environment [400] comprises an
Enterprise Product Catalogue (EPC) [402], a Fulfilment management system
5 (FMS) [404], a subscription engine [414], a plurality of channels [406], a load
balancer [408], a Customer Relationship Manager (CRM) server [410] comprising
a plurality of micro-services, and a set of database [412]. The set of database may
include a database 1, database 2, and a database 3. The EPC [402], a centralised
data repository which drives Business Support System (BSS) telecom operations
10 and some network nodes too for e.g., 5G charging system, called Policy Control
Function (PCF).
[0099] At the centre, the CRM server [410] containing different micro services are shown in FIG.4 which cater to different Application Programming Interfaces
15 (APIs). Each microservice serves a particular context, e.g., Customer Order
Processing Micro service (COP_MS) deals with order-related APIs which performs submit order, query order, and modify order. Customer Information Service (CIS) instances deal with customer-related APIs which performs create, modify or deactivate customer. Lead-to-Order (L2O) instances deal with APIs that manage the
20 lifecycle of leads and prospects. Operations and Maintenance (OAM) instance deals
with the maintenance and operation of all the microservice instances and communicates with outer products related to alarms, Key Performance Indicators (KPIs) or other management, and health check-up information.
25 [0100] The channels [406] are configured to provide input data to the CRM server
[410] through a load balancer [408]. In an embodiment, some examples of the channels [406] include but are not limited to channel 1 [406A], channel 2 [406B], channel 3 [406C] and a CRM user interface (UI) [406D]. The channels [406] which are tightly coupled to the CRM e.g. CRM User Interface (UI) communicate directly
30 via the load balancer [408] while other systems which belong to different products
communicate to the CRM server [410] using the FMS [404]. FMS is a middleware
35

which links two different products and performs language translations or workflow
management. For example, if one product understands Simple Object Access
Protocol (SOAP) protocol while the other one understands RESTful services, the
FMS [404] translate the messages between these 2 nodes and ensure seamless
5 communication. The CRM [410] is also connected with the FMS [404], SMP
(Service Management Platform) [416], and Data Information Framework (DIF)
[418] via https. The DIF [418] is a copy of the CRM [410], EPC, and Geographical
Information System (GIS) which caches the business data and provides API for fast
access. The SMP [416] which deals with the installation processes at customer
10 premises, handling repair mechanism and technician visit to network sites.
[0101] In a preferred embodiment, an admin user operates the CRM UI [406D] to trigger the CRUD (Create/ Read/ Update/ Delete) operation on the CRM server [410] via the load balancer [408] or FMS. According to the present disclosure, the
15 CRM server [410] stores all order journey configurations cached during the start-
up of micro services. Whenever any change, such as ‘update’, ‘delete’, ‘create’ etc., in order journey configuration is received from the CRM UI [406D], the CRM server [410] processes the same and modifies the stored data in cache. The workflow engine picks the updated configuration item whenever subsequent order
20 submission request comes at the CRM server [410]. Based on the configuration list,
the next milestone is triggered.
[0102] The present disclosure also discloses a User Equipment (UE), comprising a transceiver unit, configured to transmit an order request to execute network
25 activation; and receive from the system [200], a response to the order request,
wherein the response comprises an indication of network activation, and the response is generated at the system [200] based on: receiving, by a transceiver unit [202], an order request comprising at least a product identifier (ID), a set of request header parameters, a set of request body parameters, and one or more other factors;
30 fetching, by the transceiver unit [202] from a target memory [204], one or more
predefined order provisioning and activation templates based on the product ID
36

associated with the order request; configuring, by a workflow configurator, a header
workflow associated with the set of request header parameters based on the one or
more predefined order provisioning and activation templates; configuring, by the
workflow configurator, a body workflow associated with the set of request body
5 parameters based on the one or more predefined order provisioning and activation
templates; fetching, by the transceiver unit [202] from a predefined product
database, a set of product parameters based on at least one of the product ID and a
predefined product-order reference value; generating, by a configuration generator,
a parameter configuration in a predefined parameter configuration format based on
10 at least the one or more other factors; generating, by a request generator, a workflow
request based on at least the header workflow, the body workflow and the parameter configuration; and automatically provisioning, by a provisioning unit [212], the network activation associated with the order request based on the workflow request.
15 [0103] The present disclosure also discloses a non-transitory computer readable
storage medium storing instructions for automatically provisioning a network activation using a plurality of provisioning and activation templates maintained in a target memory, the instructions include executable code which, when executed by one or more units of a system [200] causes a transceiver unit [202] of the system
20 [200] to receive, an order request comprising at least a product identifier (ID), a set
of request header parameters, a set of request body parameters, and one or more other factors. Further, the instructions include executable code, which when executed causes the transceiver unit [202] to fetch, from a target memory [204], one or more predefined order provisioning and activation templates based on the
25 product ID associated with the order request. Further, the instructions include
executable code, which when executed causes a workflow configurator [206] of the system to configure, a header workflow associated with the set of request header parameters based on the one or more predefined order provisioning and activation templates. Further, the instructions include executable code, which when executed
30 causes the workflow configurator [206] to configure, a body workflow associated
with the set of request body parameters based on the one or more predefined order
37

provisioning and activation templates. Further, the instructions include executable
code, which when executed causes the transceiver unit [202] to fetch, from a
predefined product database, a set of product parameters based on at least one of
the product ID and a predefined product-order reference value;. Further, the
5 instructions include executable code, which when executed causes a configuration
generator [208] of the system [200] to generate, a parameter configuration in a predefined parameter configuration format based on at least one or more other factors. Further, the instructions include executable code, which when executed causes a request generator [210] of the system [200] to generate, a workflow request
10 based on at least the header workflow, the body workflow and the parameter
configuration. Further, the instructions include executable code, which when executed causes a provisioning unit [212] of the system [200] to automatically provision, the network activation associated with the order request based on the workflow request.
15
[0104] As is evident from the above, the present disclosure provides technical advantages and advancement over the known solutions, mentioned as follows:
• Improved Network Performance: By properly provisioning and activating
20 network resources, service providers can ensure that their code and
configuration is immune to rapid business changes in the JSON request
preparation logic for any product. This means that users can access the
network quickly and easily, without experiencing delays or downtime.
Network provisioning can also help prevent congestion on the network,
25 ensuring that bandwidth is allocated appropriately to meet the needs of
users.
• Enhanced Security: Properly provisioning and activating network resources
can also help enhance network security. This includes setting up firewalls,
intrusion detection systems, and other security measures to protect against
30 unauthorized access and data breaches. Activation also involves setting up
38

user accounts with appropriate permissions and access levels, ensuring that
sensitive information is only accessible to authorized personnel.
• Streamlined network management: By automating the network provisioning
and activation processes, service providers can streamline network
5 management and reduce the risk of errors or misconfigurations. This can
save time and resources, allowing IT teams to focus on other critical tasks. Accordingly, it may be seen that the system of the current disclosure may act as an essential tool for any service provider that wants to streamline its provisioning and activation processes. 10
[0105] While considerable emphasis has been placed herein on the disclosed
implementations, it will be appreciated that many implementations can be made and
that many changes can be made to the implementations without departing from the
principles of the present disclosure. These and other changes in the implementations
15 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.
39

We Claim:
1. A method for automatically provisioning a network activation using a plurality
of provisioning and activation templates maintained in a target memory [204],
5 the method comprising:
- receiving, by a transceiver unit [202], an order request comprising at least a
product identifier (ID), a set of request header parameters, a set of request
body parameters, and one or more other factors;
- fetching, by the transceiver unit [202] from a target memory [204], one or
10 more predefined order provisioning and activation templates based on the
product ID associated with the order request;
- configuring, by a workflow configurator [206], a header workflow
associated with the set of request header parameters based on the one or more
predefined order provisioning and activation templates;
15 - configuring, by the workflow configurator [206], a body workflow
associated with the set of request body parameters based on the one or more predefined order provisioning and activation templates;
- fetching, by the transceiver unit [202] from a predefined product database, a
set of product parameters based on at least one of the product ID and a
20 predefined product-order reference value;
- generating, by a configuration generator [208], a parameter configuration in
a predefined parameter configuration format based on at least the one or
more other factors;
- generating, by a request generator [210], a workflow request based on at least
25 the header workflow, the body workflow and the parameter configuration;
and
- automatically provisioning, by a provisioning unit [212], the network
activation associated with the order request based on the workflow request.
2. The method as claimed in claim 1, wherein the header workflow is configured
30 based on at least one of the product ID associated with the order, a service
name request associated with the order, and a list of one or more predefined
40

attribute-value pairs associated with the order, the one or more predefined attribute-value pairs comprising a workflow name pair, a service name pair, and a subscriber identity module (SIM) card type pair.
3. The method as claimed in claim 1, wherein the body workflow is configured
5 based on at least one of the product ID associated with the order and a
predefined workflow name associated with the order.
4. The method as claimed in claim 1, wherein the one or more other factors are
fetched from one or more entities comprising an order detail, a local product
catalogue, and a reference value master.
10 5. The method as claimed in claim 1, the method further comprising:
- creating, by the request generator [210], a configuration file request for a single workflow engine, the configuration file request comprising a set of configuration elements, one or more request headers.
6. The method as claimed in claim 1, wherein the target memory [204] is one of
15 a cache memory and a database.
7. The method as claimed in claim 1, wherein the header workflow is associated
with a set of headers, wherein each header from the set of headers is a header
sent in a RESTful Application Programming Interface (API).
8. The method as claimed in claim 1, wherein the header workflow comprises a
20 set of configurations for a set of APIs to be invoked and a set of parameter
values corresponding to the set of configurations, to cater one or more request header parameters associated with the set of APIs to be invoked.
9. The method as claimed in claim 8, wherein in an event a parameter value from
the set of parameter values is dynamic and is associated with at least one of a
25 customer order and a product catalogue, an Xpath of a customer order
JavaScript Object Notation (JSON) schema is defined in a configuration corresponding to said parameter value, to determine a value stored at an Xpath of an order received to invoke an API and to cater one or more headers associated with said order.
30 10. The method as claimed in claim 9, wherein in an event the configuration
corresponding to the parameter value is associated with the product catalogue
41

then at least one of a product catalogue table, a response filed as a final value and one or more input parameters are identified, wherein the one or more input parameters are one or more parameters to be extracted from the customer order based on the Xpath.
11. The method as claimed in claim 1, wherein the set of product parameters is fetched from the predefined product database to identify additional information related to one or more parameters associated with the order request, wherein the additional information comprises at least one of a product name, a product billing type, one or more services and one or more features related to one or more catalogue-driven enrichments.
12. The method as claimed in claim 1, wherein the parameter configuration is associated with a value derived from at least one of a persisted order in the predefined product database, one or more customer details, a master reference value and a product catalogue data.
13. The method as claimed in claim 12, wherein the parameter configuration is associated with an information: for picking a value for a corresponding parameter and for configuration of the corresponding parameter, in production environment during a server on which said corresponding parameter is to be configured is in a running state.
14. A system for automatically provisioning a network activation using a plurality of provisioning and activation templates maintained in a target memory [204], the system comprising:
- a transceiver unit [202] configured to:
o receive, an order request comprising at least a product identifier (ID), a set of request header parameters, a set of request body parameters, and one or more other factors, and o fetch, from a target memory [204], one or more predefined order provisioning and activation templates based on the product ID associated with the order request; - a workflow configurator [206] connected to at least the transceiver unit [202], the workflow configurator [206] configured to:

o configure, a header workflow associated with the set of request header parameters based on the one or more predefined order provisioning and activation templates, and o configure, a body workflow associated with the set of request body parameters based on the one or more predefined order provisioning and activation templates, wherein: the transceiver unit [202] is further configured to fetch, from a predefined product database, a set of product parameters based on at least one of the product ID and a predefined product-order reference value;
- a configuration generator [208] connected to at least the transceiver unit [202], the configuration generator [208] configured to generate, a parameter configuration in a predefined parameter configuration format based on at least one or more other factors;
- a request generator [210] connected to at least the configuration generator [208], the request generator [210] configured to generate, a workflow request based on at least the header workflow, the body workflow and the parameter configuration; and
- a provisioning unit [212] connected to at least the request generator [210], the provisioning unit [212] configured to automatically provision, the network activation associated with the order request based on the workflow request.

15. The system as claimed in claim 14, wherein the header workflow is configured based on at least one of the product ID associated with the order, a service name request associated with the order, and a list of one or more predefined attribute-value pairs associated with the order, the one or more predefined attribute-value pairs comprising a workflow name pair, a service name pair, and a subscriber identity module (SIM) card type pair.
16. The system as claimed in claim 14, wherein the body workflow is configured based on at least one of the product ID associated with the order and a predefined workflow name associated with the order.

17. The system as claimed in claim 14, wherein the one or more other factors are fetched from one or more entities comprising an order details, a local product catalogue, and a reference value master.
18. The system as claimed in claim 14, wherein the request generator [210] is further configured to create a configuration file request for a single workflow engine, the configuration file request comprising a set of configuration elements, one or more request headers.
19. The system as claimed in claim 14, wherein the target memory [204] is one of a cache memory and a database.
20. The system as claimed in claim 14, wherein the header workflow is associated with a set of headers, wherein each header from the set of headers is a header sent in a RESTful Application Programming Interface (API).
21. The system as claimed in claim 14, wherein the header workflow comprises a set of configurations for a set of APIs to be invoked and a set of parameter values corresponding to the set of configurations, to cater one or more request header parameters associated with the set of APIs to be invoked.
22. The system as claimed in claim 21, wherein in an event a parameter value from the set of parameter values is dynamic and is associated with at least one of a customer order and a product catalogue, an Xpath of a customer order JavaScript Object Notation (JSON) schema is defined in a configuration corresponding to said parameter value, to determine a value stored at an Xpath of an order received to invoke an API and to cater one or more headers associated with said order.
23. The system as claimed in claim 22, wherein in an event the configuration corresponding to the parameter value is associated with the product catalogue then at least one of a product catalogue table, a response filed as a final value and one or more input parameters are identified, wherein the one or more input parameters are one or more parameters to be extracted from the customer order based on the Xpath.
24. The system as claimed in claim 14, wherein the set of product parameters is fetched from the predefined product database to identify additional

information related to one or more parameters associated with the order request, wherein the additional information comprises at least one of a product name, a product billing type, one or more services and one or more features related to one or more catalogue-driven enrichments.
25. The system as claimed in claim 14, wherein the parameter configuration is associated with a value derived from at least one of a persisted order in the predefined product database, one or more customer details, a master reference value and a product catalogue data.
26. The system as claimed in claim 25, wherein the parameter configuration is associated with an information: for picking a value for a corresponding parameter and for configuration of the corresponding parameter, in production environment during a server on which said corresponding parameter is to be configured is in a running state.
27. A user equipment (UE), the UE comprising:

- a transceiver unit configured to transmit to a system [200], an order request to execute network activation; and
- the transceiver unit configured to receive from the system [200], a response to the order request, wherein the response comprises an indication of network activation, and the response is generated at the system [200] based on:
o receiving, by a transceiver unit [202], an order request comprising at least a product identifier (ID), a set of request header parameters, a set of request body parameters, and one or more other factors;
o fetching, by the transceiver unit [202] from a target memory [204], one or more predefined order provisioning and activation templates based on the product ID associated with the order request;
o configuring, by a workflow configurator [206], a header workflow associated with the set of request header parameters based on the one or more predefined order provisioning and activation templates;

o configuring, by the workflow configurator [206], a body workflow
associated with the set of request body parameters based on the one or
more predefined order provisioning and activation templates; o fetching, by the transceiver unit [202] from a predefined product
database, a set of product parameters based on at least one of the product
ID and a predefined product-order reference value; o generating, by a configuration generator [208], a parameter
configuration in a predefined parameter configuration format based on
at least the one or more other factors; o generating, by a request generator [210], a workflow request based on
at least the header workflow, the body workflow and the parameter
configuration; and o automatically provisioning, by a provisioning unit [212], the network
activation associated with the order request based on the workflow
request.