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 EXECUTING A PLANNED
EVENT”
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 EXECUTING A PLANNED EVENT FIELD OF INVENTION
[0001] The present disclosure generally relates to event management for a network. More particularly, embodiments of the present disclosure relate to methods and systems for providing a proper flow for the execution of any planned event and executing a planned event on network nodes.
BACKGROUND
[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] Wireless communication technology has rapidly evolved over the past few decades, with each generation bringing significant improvements and advancements. The first generation of wireless communication technology was based on analog technology and offered only voice services. However, with the advent of the second generation (2G) technology, digital communication and data services became possible, and text messaging was introduced. The third generation (3G) technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth generation (4G) technology revolutionized wireless communication with faster data speeds, better network coverage, and improved security. Currently, the fifth generation (5G) technology is being deployed, promising even faster data speeds, low latency, and the ability to connect multiple devices simultaneously. With each generation, wireless

communication technology has become more advanced, sophisticated, and capable of delivering more services to its users.
[0004] In various technologies such as in telecom network systems, a planned event is an event that impacts a project or a task and necessitates an alteration in dates, scope or other aspect of that project or task. Such changes need to be managed intelligently, identifying when they are needed and when they are not, understanding the implications of the change to projects and milestones, and putting that change into practice - approving it, communicating it and ensuring it has been enacted.
[0005] The consequence of a poor planned event management process is the risk that milestones are pushed back without understanding how that impacts other milestones causing cumulative and eventually damaging delays to the overall progress of a major event. These delays are often not isolated but can have ripple effects on subsequent tasks and milestones. This cumulative effect can lead to a chain reaction of delays throughout the entire project timeline.
[0006] It is therefore required to build some contingency into events where possible, so that one change does not disrupt the entire project and fall back to previous implementation.
[0007] Thus, there exists an imperative need in the art to provide a method for execution of planned event and monitoring of network nodes (nodes of a telecommunication network), which the present disclosure aims to address.
OBJECTS OF THE DISCLOSURE
[0008] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.

[0009] It is an object of the present disclosure to provide a system and a method for executing a planned event.
[0010] It is an object of the present disclosure to provide a fall-back process if the planned event is not successful and to roll back any changes made on the network nodes.
[0011] It is another object of the present disclosure to provide a solution that can provide a proper flow for the execution of any planned event with proper risk evaluation and impact.
[0012] It is also an object of the present disclosure to provide a request which can be used for the management and control of change management process between a customer and a service provider or between a service provider and a partner and vice versa.
[0013] It is yet another object of the present disclosure to provide a solution that is useful in emergency which requires immediate action and in normal situation also which requires prior approval.
SUMMARY
[0014] 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.
[0015] An aspect of the present disclosure may relate to a method for executing a planned event. The method comprising initiating, by a user interface unit, a planned event create request based on a first input of a first user. Further, the method

comprises receiving, by a data ingestion unit, the planned event create request. Further, the method comprises creating, by the data ingestion unit, a planned event based on the planned event create request. Further, the method comprises identifying, by the data ingestion unit, a request type associated with the planned event. Further, the method comprises assigning, by a resource assurance unit, a workflow to the planned event based on the request type of the planned event upon receiving the planned event from the data ingestion unit. Further, the method comprises processing, by a workflow engine, one or more actions based on the workflow assigned to the planned event. Thereafter, the method comprises executing, by an execution unit, the planned event based on the processing of the one or more actions.
[0016] In an exemplary aspect of the present disclosure, the method comprises storing by a storage unit, the planned event.
[0017] In an exemplary aspect of the present disclosure, the method comprises assigning by the user interface unit, the planned event to a second user based on a second input of the first user.
[0018] In an exemplary aspect of the present disclosure, the method comprises executing, by the execution unit, the planned event in an asynchronous manner.
[0019] In an exemplary aspect of the present disclosure, the method further comprises determining, by a determination unit, a planned event data based on the execution of the planned event; providing, by a provisioning unit, the planned event data to one or more network nodes of a network system, and monitoring, by an analysis unit, the one or more network nodes based on the planned event data for fault management at the one or more network nodes.
[0020] In an exemplary aspect of the present disclosure, the request type is one of a standard planned event or a non-standard planned event.

[0021] In an exemplary aspect of the present disclosure, the method comprises receiving, by the execution unit, an approval for execution of the non-standard planned event.
[0022] Another aspect of the present disclosure may relate to a system for executing a planned event, the system comprising a user interface unit configured to initiate a planned event create request based on a first input of a first user, wherein the planned event create request comprises a set of input parameters. Further, the system comprises a data ingestion unit connected at least to the user interface unit; the data ingestion unit configured to: receive the planned event create request; create a planned event based on the planned event create request; and identify a request type associated with the planned event. Further, the system comprises a resource assurance unit connected at least to the data ingestion unit, the resource assurance unit configured to assign a workflow to the planned event based on the request type of the planned event upon receiving the planned event from the data ingestion unit. Further, a workflow engine connected to at least the resource assurance unit, the workflow engine configured to process one or more actions based on the workflow assigned to the planned event. Further, an execution unit connected to at least the workflow engine, the execution unit configured to execute the planned event based on the processing of the one or more actions.
[0023] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for executing a planned event, the instructions include executable code which, when executed by one or more units of a system cause a user interface unit of the system to initiate a planned event create request based on a first input of a first user, wherein the planned event create request comprises a set of input parameters. Further, instructions are executed to cause a data ingestion unit of the system to receive the planned event create request; create a planned event based on the planned event create request; and identify a request type associated with the planned event. Further, instructions are

executed to cause a resource assurance unit of the system to assign a workflow to the planned event based on the request type of the planned event upon receiving the planned event from the data ingestion unit. Further, instructions are executed cause a workflow engine of the system to process one or more actions based on the workflow assigned to the planned event. Further, instructions are executed to cause an execution unit of the system to execute the planned event based on the processing of the one or more actions.
[0024] Yet another aspect of the present disclosure may relate to a User Equipment (UE), comprising a transmitter unit, configured to transmit to a system, a request to execute a planned event; and a receiver unit, configured to receive from the system, a response to the request, wherein the response comprises an indication of execution of the planned event, and wherein the response is generated at the system based on initiating, by a user interface unit, a planned event create request based on a first input of a first user; receiving, by a data ingestion unit, the planned event create request; creating, by the data ingestion unit, a planned event based on the planned event create request; identifying, by the data ingestion unit, a request type associated with the planned event; assigning, by a resource assurance unit, a workflow to the planned event based on the request type of the planned event upon receiving the planned event from the data ingestion unit; processing, by a workflow engine, one or more actions based on the workflow assigned to the planned event; and executing, by an execution unit, the planned event based on the processing of the one or more actions.
BRIEF DESCRIPTION OF THE DRAWINGS
[0025] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present

disclosure. Also, the embodiments shown in the figures are not to be construed as limiting the disclosure, but the possible variants of the method and system according to the disclosure are illustrated herein to highlight the 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.
[0026] 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.
[0027] FIG. 2 illustrates an exemplary block diagram of a system for executing a planned event, in accordance with exemplary implementations of the present disclosure.
[0028] FIG. 3 illustrates a method flow diagram for executing a planned event, in accordance with exemplary implementations of the present disclosure.
[0029] FIG.4 illustrates an exemplary process for Application Programming Interface (API) based planned event processing and monitoring of network nodes, in accordance with exemplary implementations of the present disclosure.
[0030] The foregoing shall be more apparent from the following more detailed description of the disclosure.
DETAILED DESCRIPTION
[0031] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific

details. Several features described hereafter may each be used independently of one another or with any combination of other features. An individual feature may not address any of the problems discussed above or might address only some of the problems discussed above. 5
[0032] The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. 10 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.
[0033] Specific details are given in the following description to provide a thorough
15 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 may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail.
20
[0034] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various components/units can be implemented interchangeably. While specific embodiments may disclose a particular functionality of these units for clarity, it is recognized that various
25 configurations and combinations thereof are within the scope of the disclosure. The functionality of specific units as disclosed in the disclosure should not be construed as limiting the scope of the present disclosure. Consequently, alternative arrangements and substitutions of units, provided they achieve the intended functionality described herein, are considered to be encompassed within the scope
30 of the present disclosure.
9

[0035] Also, it is noted that individual embodiments may be described as a process which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations may be performed in parallel or 5 concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure.
[0036] The word “exemplary” and/or “demonstrative” is used herein to mean
10 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 aspect or design described herein as “exemplary” and/or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques
15 known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive—in a manner similar to the term “comprising” as an open transition word—without precluding any additional or other elements.
20
[0037] As used herein, a “processing unit” or “processor” or “operating processor” includes one or more processors, wherein processor refers to any logic circuitry for processing instructions. A processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality
25 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 integrated circuits, etc. The processor may perform signal coding data processing, input/output processing, and/or any other functionality that enables the working of
30 the system according to the present disclosure. More specifically, the processor or processing unit is a hardware processor.
10

[0038] 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 5 communication device” may be any electrical, electronic and/or computing device or equipment, capable of implementing one or more features of the present disclosure. The user equipment/device may include, but is not limited to, a mobile phone, smart phone, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, wearable device or any other computing device which is 10 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 from unit(s) which are required to implement the one or more features of the present disclosure.
15 [0039] As used herein, “storage unit” or “memory unit” refers to a machine or computer-readable medium including any mechanism for storing information in a form readable by a computer or similar machine. For example, a computer-readable medium includes read-only memory (“ROM”), random access memory (“RAM”), magnetic disk storage media, optical storage media, flash memory devices or other
20 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.
[0040] As used herein “interface” or “user interface” refers to a shared boundary 25 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 each other, which also includes the methods, functions, or procedures that may be called. 30
11

[0041] All modules, units, components used herein, unless explicitly excluded herein, may be software modules or hardware processors, the processors being a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more 5 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.
[0042] As used herein the transceiver unit includes at least one receiver and at least 10 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.
[0043] As discussed in the background section, the current known solutions have
15 several shortcomings such as delays in processing events on network nodes. The
present disclosure aims to overcome the above-mentioned and other existing
problems in this field of technology by providing a solution for executing planned
events and monitoring of network nodes. Mainly the present disclosure provides a
solution that empowers a Service Management Platform (SMP) to handle and
20 execute planned events (PE) on network nodes. The SMP includes multiple micro
services that interact with each other to fulfil required functionality to create a
planned event and successfully execute such planned event based on execution of
one or more actions which are in accordance with a workflow assigned to the
planned event.
25
[0044] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings.
[0045] FIG. 1 illustrates an exemplary block diagram of a computing device [100]
30 upon which the features of the present disclosure may be implemented in
accordance with exemplary implementation of the present disclosure. In an
12

implementation, the computing device [100] may be in communication with a communication network and may also implement a method [300] for executing a planned event. In another implementation, the computing device [100] in communication with the communication network, itself implements the method 5 [300] for executing a planned event 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.
[0046] The computing device [100] may include a bus [102] or other 10 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-access memory (RAM), or other dynamic storage device, coupled to the bus [102] 15 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 accessible to the processor [104], render the computing device [100] into a special-20 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 [0047] 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), Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for
30 displaying information to a computer user. An input device [114], including alphanumeric and other keys, touch screen input means, etc. may be coupled to the
13

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 information and command selections to the processor [104], and for controlling 5 cursor movement on the display [112]. The 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.
[0048] The computing device [100] may implement the techniques described
10 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
computing device [100] in response to the processor [104] executing one or more
15 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
process steps described herein. In alternative implementations of the present
20 disclosure, hard-wired circuitry may be used in place of or in combination with
software instructions.
[0049] The computing device [100] also may include a communication interface [1018] coupled to the bus [102]. The communication interface [118] provides a two-25 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 telephone line. As another example, the communication interface [118] may be a 30 local area network (LAN) card to provide a data communication connection to a compatible LAN. Wireless links may also be implemented. In any such
14

implementation, the communication interface [118] sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.
5 [0050] 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 Internet Service Provider (ISP) [126], the local network [122], the host [124] and 10 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.
[0051] The computing device [100] encompasses a wide range of electronic 15 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 such as data storage, retrieval, and analysis. Additionally, computing device [100] 20 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.
[0052] Referring to FIG. 2, an exemplary block diagram of a system [200] for 25 executing a planned event on one or more network nodes, is shown, in accordance with the exemplary implementations of the present disclosure. The system [200] comprises at least one user interface unit [202], at least one data ingestion unit [204], at least one resource assurance unit [206], at least one workflow engine [208], at least one execution unit [210], at least one storage unit [212], at least one 30 determination unit [214], at least one provisioning unit [216], and at least one analysis unit [218]. Also, all of the components/ units of the system [200] are
15

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.
[0053] The system [200] is configured for executing a planned event, with the help 10 of the interconnection between the components/units of the system [200].
[0054] At first, a user has to initiate a planned event request. The system [200] comprises the user interface unit [202] to initiate a planned event create request based on a first input of a first user, wherein the planned event create request
15 comprises a set of input parameters. A planned event is an event that is scheduled or prearranged to occur at specific time and typically involves activities such as network maintenance, upgrades, deployments, or configuration changes. For example, the first user is a change requestor. The planned event create request refers to a user-initiated action within a system [200] where a user requests the creation
20 of a planned event. The set of input parameters are specific details or data elements required to describe and define the planned event. It serves as the initial trigger for the system [200] to start processing and organizing the event. The set of input parameters may include name, location, date and time, description, etc. The user interface unit [202] is further configured to assign the planned event to a second
25 user based on a second input of the first user. The second user may be a user who receives the assignment from the first user, say the second user may be an Engineer, indicating they have a technical role in the execution or management of the planned event. The second input from the first user (e.g., change requestor), may involve specifying or selecting the second user who will be responsible for carrying out or
30 managing the event. The second input may include assignment of roles, selection of responsible person, and deadline or timeline details etc.
16

[0055] Further, the data ingestion unit [204] is connected at least to the user interface unit [202], the data ingestion unit [204] is configured to receive the planned event create request. Further, the data ingestion unit [204] creates a planned 5 event based on the planned event create request. Further, the data ingestion unit [204] identifies a request type associated with the planned event. The request type is associated with the planned event created based on the planned event create request. Further, the request type is one of a standard planned event or a non-standard planned event. The standard planned events refer to events that follow a
10 well-established or typical format, process, and timeline. Standard planned events are routine or predictable events in nature and often have predefined procedures and protocols. Non-standard planned events refer to events that deviate from the usual or expected format or require unique planning considerations due to their complexity, novelty, or specific requirements. Further, the storage unit [212] is
15 configured to store the planned event.
[0056] Further, the resource assurance unit [206] is connected at least to the data ingestion unit [204], the resource assurance unit [206] is configured to assign a workflow to the planned event based on the request type of the planned event upon 20 receiving the planned event from the data ingestion unit [204]. The workflow refers to a sequence of tasks that processes a set of data through a specific path from initiation to completion. For example, workflow 1 is assigned to a standard planned event and workflow 2 is assigned to a non-standard planned event.
25 [0057] Further, the workflow engine [208] is connected to at least the resource assurance unit [206], the workflow engine [208] is configured to process one or more actions based on the workflow assigned to the planned event. The workflow engine [208] may be an application that runs digital workflow software.
30 [0058] The one or more actions may include sending notifications or status updates, initiating data processing, triggering decision points within the workflow based on
17

predefined conditions or inputs, and connecting with other systems or applications to exchange data or synchronize activities, and updating the status of the planned event in real-time or at predefined intervals, etc.
5 [0059] The execution unit [210] is connected to at least the workflow engine [208], the execution unit [210] is configured to execute the planned event based on the processing of the one or more actions. The execution unit [210] is further configured to execute, by the execution unit [210], the planned event in an asynchronous manner. The execution unit [210] is further configured to receive an approval for
10 execution of the non-standard planned event. The execution unit [210] is responsible for carrying out a planned event based on the processing of certain actions. This indicates that the execution of the planned event can happen asynchronously, meaning it doesn't have to follow a strict synchronous timeline but can proceed based on when certain conditions or actions are fulfilled.
15
[0060] The system [200] further comprises the determination unit [214] which is connected to at least the execution unit [210], the determination unit [214] is configured to determine a planned event data based on the execution of the planned event. The provisioning unit [216] is connected to at least the determination unit
20 [214], the provisioning unit [216] is configured to provide the planned event data to one or more network nodes of a network system. The analysis unit [218] is connected to at least the provisioning unit [216], the analysis unit [218] is configured to monitor the one or more network nodes based on the planned event data for fault management at the one or more network nodes. The determination
25 unit [214] analyses data related to the execution of the planned event. The provisioning unit [216] transfers the planned event data to the network nodes. This could involve distributing configurations, updates, or commands necessary for the planned event across the network. The analysis unit [218], connected to the provisioning unit [216], monitors the network nodes using the planned event data.
30 This monitoring is crucial for identifying and managing faults or issues that may arise during or after the execution of the planned event.
18

[0061] Referring to FIG.3, an exemplary flow diagram of a method [300] for executing a planned event on one or more network nodes, in accordance with exemplary implementations of the present disclosure is shown. In an 5 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]. At first, a user has to initiate a planned event request.
10 [0062] At step [304], the method [300] comprises initiating, by a user interface unit [202], a planned event create request based on a first input of a first user. The method [300] comprises assigning by the user interface unit [202], the planned event to a second user based on a second input of the first user. For example, the first user is a change requestor. The second user in Engineer. The planned event
15 create request refers to a user-initiated action within a system [200] where a user requests the creation of a planned event. The planned event create request comprises a set of input parameters. The set of input parameters are specific details or data elements required to describe and define the planned event. It serves as the initial trigger for the system [200] to start processing and organizing the event. The second
20 user may be a user who receives the assignment from the first user, say the second user may be an Engineer, indicating they have a technical role in the execution or management of the planned event. The second input from the first user (e.g., change requestor), may involve specifying or selecting the second user who will be responsible for carrying out or managing the event. The second input may include
25 assignment of roles, selection of responsible person, and deadline or timeline details etc.
[0063] At step [306], the method [300] comprises receiving, by a data ingestion unit [204], the planned event create request. 30
19

[0064] At step [308], the method [300] comprises creating, by the data ingestion unit [204], a planned event based on the planned event create request. The method [300] comprises storing by a storage unit [212], the planned event.
5 [0065] Further, at step [310], the method [300] comprises identifying, by the data ingestion unit [204], a request type associated with the planned event. The request type is associated with the planned event created based on the planned event create request. The request type is one of a standard planned event or a non-standard planned event. The standard planned events refer to an event that follows a well-10 established or typical format, process, and timeline. These events are routine or predictable in nature and often have predefined procedures and protocols. The non-standard planned events refer to events that deviate from the usual or expected format or require unique planning considerations due to their complexity, novelty, or specific requirements. Further, the method [300] comprises storing by a storage 15 unit [212], the planned event. The method [300] further comprises receiving, by an execution unit [210], an approval for execution of the non-standard planned event.
[0066] At step [312], the method [300] comprises assigning, by a resource assurance unit [206], a workflow to the planned event based on the request type of
20 the planned event upon receiving the planned event from the data ingestion unit [204]. Workflow refers to a sequence of tasks that processes a set of data through a specific path from initiation to completion. For example, workflow 1 is assigned to a standard planned event and workflow 2 is assigned to a non-standard planned event.
25
[0067] At step [314], the method [300] comprises processing, by a workflow engine [208], one or more actions based on the workflow assigned to the planned event. The workflow engine [208] may be an application that runs digital workflow software. The one or more actions may include sending notifications or status
30 updates, initiating data processing, triggering decision points within the workflow based on predefined conditions or inputs, and connecting with other systems or
20

applications to exchange data or synchronize activities, and updating the status of the planned event in real-time or at predefined intervals, etc.
[0068] At step [316], the method [300] comprises executing, by the execution unit 5 [210], the planned event based on the processing of the one or more actions. Further, the planned event is executed in an asynchronous manner. The execution unit [210] is responsible for carrying out a planned event based on the processing of certain actions. This indicates that the execution of the planned event can happen asynchronously, meaning it doesn't have to follow a strict synchronous timeline but 10 can proceed based on when certain conditions or actions are fulfilled.
[0069] The method [300] further comprises determining, by a determination unit [214], a planned event data based on the execution of the planned event; providing, by a provisioning unit [216], the planned event data to one or more network nodes 15 of a network system; and monitoring, by an analysis unit [218], the one or more network nodes based on the planned event data for fault management at the one or more network nodes.
[0070] The determination unit [214] analyses data related to the execution of the 20 planned event. The provisioning unit [216] transfers the planned event data to the network nodes. This could involve distributing configurations, updates, or commands necessary for the planned event across the network. The analysis unit [218], connected to the provisioning unit [216], monitors the network nodes using the planned event data. Such monitoring is crucial for identifying and managing 25 faults or issues that may arise during or after the execution of the planned event.
[0071] Thereafter, at step [318], the method [300] terminates.
[0072] Referring to FIG. 4, an exemplary process [400] for Application 30 Programming Interface (API) based planned event processing and monitoring of
21

network nodes, in accordance with exemplary implementations of the present disclosure.
[0073] As shown in FIG.4, at first step [402], a user (or a change requestor) initiates 5 a planned event create request based on a first input. For example, a change requestor initiates a planned event create request to a data ingestion microservice/unit [204] using a Service Management Platform (SMP) user interface.
10 [0074] At next step [404], the data ingestion unit [204] creates a planned event based on validation of the planned event create request and identifies a request type associated with the planned event. For example, the data Ingestion unit [204] creates a planned event based upon the input parameters and stores it in a storage unit [212]. If the request is invalid, then the data ingestion unit [204] does not create
15 a planned event and the process moves to step [405] where the request is considered a bad/ invalid request.
[0075] At next step [406], the data ingestion unit [204] identifies a request type associated with the planned event. If the planned event is determined to be a non-20 standard planned event at step [450], then it waits for approval at step [412] and executes the non-standard planned event upon receiving approval at step [412], or at step [414] the planned event is cancelled in case approval is not received.
[0076] If the request type is determined to be a standard planned event at step [408], 25 then the process [400] moves to step [416] and encompasses executing the planned event by an execution unit [210].
[0077] At next step [418], the process [400] encompasses reviewing the planned
event data based on the execution of the planned event. The planned event data
30 could involve distributing configurations, updates, or commands necessary for the
planned event across the network nodes. Further, in case of failed implementation
22

review from the network nodes, the process [400] identifies that the planned event has failed at step [422]. If the implementation review is executed by the network nodes, the process [400] recognizes that the planned event has closed at step [420].
5 [0078] Yet another aspect of the present disclosure may relate to User Equipment (UE), comprising a transmitter unit, configured to transmit to a system [200], a request to execute a planned event; and a receiver unit, configured to receive from the system [200], a response to the request, wherein the response comprises an indication of execution of the planned event. The response is generated at the
10 system [200] based on initiating, by a user interface unit [202], a planned event create request based on a first input of a first user; receiving, by a data ingestion unit [204], the planned event create request; creating, by the data ingestion unit [204], a planned event based on the planned event create request; identifying, by the data ingestion unit [204], a request type associated with the planned event;
15 assigning, by a resource assurance unit [206], a workflow to the planned event based on the request type of the planned event upon receiving the planned event from the data ingestion unit [204]; processing, by a workflow engine [208], one or more actions based on the workflow assigned to the planned event; and executing, by an execution unit [210], the planned event based on the processing of the one or
20 more actions.
[0079] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for executing a planned event, the instructions include executable code which, when executed by one or
25 more units of a system [200] causes a user interface unit [202] of the system [200] to initiate a planned event create request based on a first input of a first user, wherein the planned event create request comprises a set of input parameters. Further, instructions are executed to cause a data ingestion unit [204] of the system [200] to receive the planned event create request; create a planned event based on the
30 planned event create request; and identify a request type associated with the planned event. Further, instructions are executed to cause a resource assurance unit [206] of
23

the system [200] to assign a workflow to the planned event based on the request type of the planned event upon receiving the planned event from the data ingestion unit [204]. Further, instructions are executed to cause a workflow engine [208] of the system [200] to process one or more actions based on the workflow assigned to 5 the planned event. Further, instructions are executed to cause an execution unit [210] of the system [200] to execute the planned event based on the processing of the one or more actions.
[0080] As is evident from the above, the present disclosure provides a technically
10 advanced solution for planned event processing and monitoring of network nodes. The solution as disclosed in the present disclosure provides a request which can be used for the management and control of Change Management process between a customer and a service provider or between a service provider and a partner and vice versa. The control of change management process refers to the ability to
15 manage and oversee the process by which changes are proposed, evaluated, approved, and implemented while providing a service within a business relationship, specifically between a customer and a service provider, or between a service provider and a partner. Also, the solution provides proper flow for the execution of any planned event with proper risk evaluation and impact.
20 Additionally, the solution can be useful in emergency which require immediate action and in normal situation also which requires prior approval. The solution also provides fall back process if the planned event is not successful, and the changes made needs to be rollback. Also, the solution ensures that standardized methods and procedures are used for efficient and prompt handling of all changes to control IT
25 infrastructure and Network, in order to minimize the number and impact of any related incidents upon service.
[0081] While considerable emphasis has been placed herein on the disclosed
implementations, it will be appreciated that many implementations can be made and
30 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
24

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.
5 [0082] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various components/units can be implemented interchangeably. While specific embodiments may disclose a particular functionality of these units for clarity, it is recognized that various configurations and combinations thereof are within the scope of the disclosure. The 10 functionality of specific units as disclosed in the disclosure should not be construed as limiting the scope of the present disclosure. Consequently, alternative arrangements and substitutions of units, provided they achieve the intended functionality described herein, are considered to be encompassed within the scope of the present disclosure.
25

We Claim:
1. A method [300] for executing a planned event, the method [300]
comprising:
- initiating, by a user interface unit [202], a planned event create request based on a first input of a first user;
- receiving, by a data ingestion unit [204], the planned event create request;
- creating, by the data ingestion unit [204], a planned event based on the planned event create request;
- identifying, by the data ingestion unit [204], a request type associated with the planned event;
- assigning, by a resource assurance unit [206], a workflow to the planned event based on the request type of the planned event upon receiving the planned event from the data ingestion unit [204];
- processing, by a workflow engine [208], one or more actions based on the workflow assigned to the planned event; and
- executing, by an execution unit [210], the planned event based on the processing of the one or more actions.

2. The method [300] as claimed in claim 1, the method [300] comprises storing by a storage unit [212], the planned event.
3. The method [300] as claimed in claim 1, the method [300] comprises assigning by the user interface unit [202], the planned event to a second user based on a second input of the first user.
4. The method [300] as claimed in claim 1, the method [300] comprises executing, by the execution unit [210], the planned event in an asynchronous manner.

5. The method [300] as claimed in claim 1 further comprises:
- determining, by a determination unit [214], a planned event data based on the execution of the planned event,
- providing, by a provisioning unit [216], the planned event data to one or more network nodes of a network system, and
- monitoring, by an analysis unit [218], the one or more network nodes based on the planned event data for fault management at the one or more network nodes.

6. The method [300] as claimed in claim 1, wherein the request type is one of a standard planned event or a non-standard planned event.
7. The method [300] as claimed in claim 6 further comprises receiving, by the execution unit [210], an approval for execution of the non-standard planned event.
8. A system [200] for executing a planned event, the system [200] comprising:

- a user interface unit [202] configured to initiate a planned event create request based on a first input of a first user, wherein the planned event create request comprises a set of input parameters;
- a data ingestion unit [204] connected at least to the user interface unit [202], the data ingestion unit [204] configured to:
o receive the planned event create request,
o create a planned event based on the planned event create
request, and o identify a request type associated with the planned event;
- a resource assurance unit [206] connected at least to the data
ingestion unit [204], the resource assurance unit [206]
configured to assign a workflow to the planned event based on
the request type of the planned event upon receiving the planned
event from the data ingestion unit [204];

- a workflow engine [208] connected to at least the resource assurance unit [206], the workflow engine [208] configured to process one or more actions based on the workflow assigned to the planned event; and
- an execution unit [210] connected to at least the workflow engine [208], the execution unit [210] configured to execute the planned event based on the processing of the one or more actions.

9. The system [200] as claimed in claim 8, wherein the system [200] further comprises a storage unit [212], the storage unit [212] configured to store the planned event.
10. The system [200] as claimed in claim 8, wherein the user interface unit [202] is further configured to assign the planned event to a second user based on a second input of the first user.
11. The system [200] as claimed in claim 8, wherein the execution unit [210] is further configured to execute the planned event in an asynchronous manner.
12. The system [200] as claimed in claim 8 further comprises:

- a determination unit [214] connected to at least the execution unit [210], the determination unit [214] configured to determine a planned event data based on the execution of the planned event;
- a provisioning unit [216] connected to at least the determination unit [214], the provisioning unit [216] configured to provide the planned event data to one or more network nodes of a network system; and
- an analysis unit [218] connected to at least the provisioning unit [216], the analysis unit [218] configured to monitor the one or more network nodes based on the planned event data for fault management at the one or more network nodes.

13. The system [200] as claimed in claim 8, wherein the request type is one of a standard planned event or a non-standard planned event.
14. The system [200] as claimed in claim 13, wherein the execution unit [210] is further configured to receive an approval for execution of the non-standard planned event.
15. A User Equipment (UE), comprising:

- a transmitter unit, configured to transmit to a system [200], a request to execute a planned event; and
- a receiver unit, configured to receive from the system [200], a response to the request, wherein the response comprises an indication of execution of the planned event, and the response is generated at the system [200] based on:
o initiating, by a user interface unit [202], a planned event create
request based on a first input of a first user, o receiving, by a data ingestion unit [204], the planned event create
request, o creating, by the data ingestion unit [204], a planned event based on
the planned event create request, o identifying, by the data ingestion unit [204], a request type
associated with the planned event, o assigning, by a resource assurance unit [206], a workflow to the
planned event based on the request type of the planned event upon
receiving the planned event from the data ingestion unit [204], o processing, by a workflow engine [208], one or more actions based
on the workflow assigned to the planned event, and o executing, by an execution unit [210], the planned event based on
the processing of the one or more actions.