System and method for upgrading server environment in a communication network

Abstract

Disclosed herein is a system (200) and a method (300) for upgrading server environment in a communication network. The method comprises receiving (302), by a receiving engine (114-2) via a User Interface (UI) (202), an input to access a Network Operations Platform (NOP) (110). The method further comprises navigating (304), by a control engine (114-4), to an automation adoption module (116) within the NOP based on the received input and configuring (306), by a configuration engine (114-6), target servers and services associated with each server requiring an upgradation within the automation adoption module (116). The method further comprises creating (308), by a procedure engine (118), an operational procedure based on the configuration of the target servers and the services and upgrading (310), by an execution manager (122), the server environment by controlling an execution of the operational procedure on the configured target servers.

Description

SYSTEM AND METHOD FOR UPGRADING SERVER ENVIRONMENT IN A COMMUNICATION NETWORKTECHNICAL FIELD

[0001] The embodiments of the present disclosure generally relate to the field of network operations. More particularly, the present disclosure relates to a system and a method for upgrading server environment for servers used by network applications.BACKGROUND OF THE INVENTION

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

[0003] In the rapidly evolving field of telecommunications, particularly with an advent of 5thGeneration (5G) networks, maintaining and upgrading server environment that support 5G node applications has become increasingly critical. The 5G node applications require a reliable, low-latency, and high-throughput performance from an underlying server infrastructure. Consequently, the server environment hosting these applications require regular updates and upgrades to maintain a high performance, security, and reliability essential for 5G operations.

[0004] Heretofore, existing approaches used for upgrading the server environment are both critical and time-consuming. For upgrading the server environment, system administrators typically execute automation scripts such as installing software updates and configuring system settings. The automation scripts are often run on a per-server basis or in small batches, requiring significant manual intervention to ensure that each step is executed correctly, and all necessary elements are updated. This process is not only time-consuming but also prone to human error, leading toinconsistencies in the server environment, potential downtime, and security vulnerabilities.

[0005] Moreover, with an increase in scale of the 5G networks, number of servers required to support the network increases, thereby posing challenges associated with a manual execution of the automation scripts. Further, upgrading a large number of servers results in longer maintenance periods and higher operational costs. Additionally, a lack of standardization of an upgradation process results in degraded performance of the network and even service outages, which are unacceptable in context of critical 5G applications.

[0006] Further, despite development of various automation tools and frameworks designed to streamline server upgrades, core issues like reliance on the manual intervention to initiate and manage the upgrade process remain unresolved. Existing solutions often fall short in providing a fully automated, scalable, and error-resistant method for upgrading the server environment.

[0007] Given the limitations of the existing solutions, there lies a need for an improved approach that automates the upgrading of the server environment, to overcome the aforementioned challenges.SUMMARY

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

[0009] According to an aspect of the present disclosure, disclosed herein is a method for upgrading server environment in a communication network. The method comprises receiving, by a receiving engine via a User Interface (UI), an input to access a Network Operations Platform (NOP). The method further comprisesnavigating, by a control engine, to an automation adoption module within the NOP based on the received input and configuring, by the configuration engine, a group of target servers and a plurality of services associated with each server of the group of target servers requiring an upgradation within the automation adoption module. The method further comprises creating, by a procedure engine, an operational procedure based on the configuration of the group of the target servers and the plurality of services and upgrading, by an execution manager, the server environment by controlling an execution of the operational procedure on the configured group of the target servers.

[0010] In one or more implementations, the method further comprises editing, by the procedure engine via the UI, the operational procedure to update a plurality of automation scripts and configuration files associated with the plurality of automation scripts.

[0011] In one or more implementations, the creating the operational procedure comprises uploading, by the procedure engine, a plurality of automation scripts and configuration files associated with the plurality of automation scripts on the NOP.

[0012] In one or more implementations, one of the plurality of automation scripts includes a configuration management tool script.

[0013] In one or more implementations, the upgrading the server environment comprises triggering, by the execution manager, an execution of a configuration management tool script to perform a login operation on the configured group of target servers and executing, by the execution manager upon the login operation, one or more of a plurality of automation scripts on the configured group of target servers to upgrade the server environment.

[0014] In one or more implementations, one or more of the plurality of automation scripts further include Docker automation scripts.

[0015] According to another aspect of the present disclosure, a system for upgrading server environment in a communication network is described. The system comprising a receiving engine, a control engine, a configuration engine, a procedure engine and an execution manager. The receiving engine is configured to receive, via a User Interface (UI), an input to access a Network Operations Platform (NOP). The control engine is configured to navigate to an automation adoption module within the NOP based on the received input. The configuration engine is configured to configure a group of target servers, and a plurality of services associated with each server of the group of target servers requiring an upgradation within the automation adoption module. The procedure engine is configured to create an operational procedure based on the configuration of the group of the target servers and the plurality of services. The execution manager is configured to upgrade the server environment by controlling an execution of the operational procedure on the configured group of the target servers.BRIEF DESCRIPTION OF DRAWINGS

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

[0017] FIG. 1 illustrates a block diagram depicting a Network Operations Platform (NOP) server, in accordance with an example embodiment of the present disclosure.

[0018] FIG. 2 illustrates a block diagram of a system for upgrading server environment for servers used by network applications, in accordance with an example embodiment of the present disclosure.

[0019] FIG. 3 illustrates a flowchart depicting a method for upgrading the server environment for the servers used by the network applications, in accordance with an embodiment of the present disclosure.

[0020] FIG. 4 illustrates a schematic block diagram of a computing system for upgrading the server environment for the servers used by the network applications, in accordance with an embodiment of the present disclosure.DETAILED DESCRIPTION OF THE INVENTION

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

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

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

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

[0025] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter can each be used independently of one another or with any combination of other features.

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

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

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

[0029] The present disclosure relates to a system and method for automating an upgradation of server environment for servers used by network applications, particularly in a context of managing the servers that support 5thGeneration (5G) node applications. The present disclosure utilizes a Network Operations Platform (NOP) that integrates an automation adoption module to facilitate configuration, management, and the upgradation of the server environment. The method is designed for upgrading the server environment by utilizing automation scripts, including a configuration management tool script.

[0030] Thus, an aspect of the present disclosure is to provide a system and a method that automates the upgradation of the server environment, thereby streamlining the upgradation process, reducing a need for manual intervention.

[0031] Another aspect of the present disclosure is to provide a system and a method that centralize management of server upgradation tasks by integrating the tasks into a single NOP. The platform provides a unified interface for configuring the servers, creating and executing upgrade procedures.

[0032] Another aspect of the present disclosure is to provide a system and a method that enable the management and the configuration of multiple servers simultaneously, using the configuration management tool script for an efficient and consistent deployment across a communication network.

[0033] Several key terms used in the description play pivotal roles in facilitating the system functionality. In order to facilitate an understanding of the description, the key terms are defined below.

[0034] The NOP- The NOP may refer to a platform designed to manage, monitor, configure, and automate operations across the communication network. The NOP provides interfaces, modules, and engines that enable control and orchestration of network elements, including server environment, applications, and services.

[0035] The automation adoption module- The automation adoption module may refer to a functional module within the NOP that provides an environment for configuring automation tasks, defining target servers, and associating services.

[0036] The target servers- The target servers may refer to a group of computing devices (physical or virtual) within the communication network, configured to perform specific roles such as hosting 5G applications or related services.

[0037] The automation scripts- The automation scripts may refer to the scripts that are used to perform activities such as software installation, system configuration, application deployment, service upgrades, and environment provisioning on the target servers, reducing manual intervention and ensuring consistency.

[0038] Configuration files- The term configuration files may refer to structured files containing predefined parameters, settings, and directives used to define an operational state, behavior, and environment variables of applications, or services.

[0039] The configuration management tool script- This script or a set of instructions are executed by a configuration management tool to automate a management of software configurations, deployment settings, and environment parameters acrossmultiple computing systems. The configuration management tool script facilitates operations such as establishing connections to the target servers.

[0040] Docker automation scripts- The docker automation scripts containing executable instructions are designed to automate operations related to Docker container environment. These operations include creation, deployment, configuration, scaling, updating, and removal of Docker containers, container images and associated networking components.

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

[0042] FIG. 1 illustrates a block diagram depicting a NOP server 100 (hereinafter referred as a “server 100”), in accordance with an example embodiment of the present disclosure.

[0043] As shown in FIG. 1, the server 100 includes a processor 102, a memory 104, a communication interface 106, an Input / Output (I / O) interface 108, and an NOP 110. Components of the server 100 are coupled to each other via a communication bus 100-2. The processor 102 interacts with each component, thereby coordinating their functions to achieve an automation of the server environment upgradation.

[0044] The processor 102 may include various processing circuitry and communicate with the memory 104, and the communication interface 106 via the communication bus 100-2. The processor 102 is configured to execute instructions or a set of instructions stored in the memory 104 to perform various processes. In an implementation, the processor 102 may also include processing engines.

[0045] The processor 102 may include a general -purpose processor, such as, for example, and without limitation, a Central Processing Unit (CPU), an Application Processor (AP), a dedicated processor, a Graphics-only Processing Unit such as a Graphics Processing Unit (GPU) or the like, a programmable logic device, or any combination thereof.

[0046] The memory 104 stores the set of instructions required by the processor 102 of the server 100 for controlling its overall operations. The memory 104 may include non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of Electrically Programmable Memories (EPROM) or Electrically Erasable and Programmable (EEPROM) memories. In addition, the memory 104 may, in some examples, be considered a non-transitory storage medium. The "non-transitory" storage medium is not embodied in a carrier wave or a propagated signal. However, the term "non-transitory" should not be interpreted as the memory 104 is nonmovable. In some examples, the memory 104 may be configured to store larger amounts of information. In certain examples, a non-transitory storage medium may store data that can, over time, change (e.g., in Random Access Memory (RAM) or cache). The memory 104 may be an internal storage unit or an external storage unit of the server 100, cloud storage, or any other type of external storage.

[0047] The communication interface 106 may include an electronic circuit specific to a standard that enables wired or wireless communication. The communication interface 106 is configured for communicating with external devices via networks.

[0048] The I / O interface 108 may include suitable logic, circuitry, interfaces, and / or codes that may be configured to receive input(s) and present (or display) output(s) on the server 100. For example, the VO interface 108 may have an input interface (not shown) and an output interface (not shown). The input interface may be configured to enable a user to provide input(s) to trigger (or configure) the server 100 for performing data processing operation(s). Examples of the input interface may include, but are not limited to, a touch interface, a mouse, a keyboard, a motionrecognition unit, a gesture recognition unit, a voice recognition unit, or the like. The output interface may be configured to display (or present) output(s) generated (or provided) by the server 100. In some aspects of the present disclosure, the output interface may provide the output(s) based on an instruction provided by the user of the server 100, by way of the input interface. Examples of the output interface may include, but are not limited to, a digital display, an analog display, a touch screen display, an appearance of a desktop, and / or illuminated characters. Aspects of the present disclosure are intended to include or otherwise cover any type of the input interface and output interface in the I / O interface 108, including known, related art, and / or later developed technologies without deviating from the scope of the present disclosure.

[0049] The NOP 110 is the platform that comprises an automation adoption platform 112 and a collection of other modules / engines 114 configured to perform automated server configuration, and system upgrades. These modules (may also be referred as “engines” or “managers”) interact with each other through defined interfaces and workflows to execute the automation scripts, manage target server environment, and perform upgrade operations without requiring manual login to each server.

[0050] Although FIG. 1 illustrates one example of the server 100, various changes may be made to FIG. 1. Further, various components in FIG. 1 may be combined, further subdivided, or omitted, and additional components may be added according to particular needs.

[0051] FIG. 2 illustrates a block diagram of a system 200 for upgrading the server environment for the servers used by the network applications, in accordance with an example embodiment of the present disclosure.

[0052] The system 200 comprises a NOP User Interface (NOP UI) 202, the NOP 110, a group of target servers 204-2, 204-4, 204-N (may also be referred as the target servers 204-2, 204-4, 204-N), an Operations, Administration, and Maintenance (0AM) 206, a database 208, an Identity and Access Management (IAM) 210, andan Elastic Load Balancer 212. The NOP may include the automation adoption platform 112 and the other modules / engines 114. The other modules / engines 114 may include a receiving engine 114-2, a control engine 114-4 and a configuration engine 114-6. Further, the automation adoption platform 112 may include an automation adoption module 116, a procedure engine 118, a server manager 120, an execution manager 122, a log management module 124, and a history management module 126.

[0053] The NOP 110 serves as a central entity that facilitates server environment upgrades, particularly for the servers running the 5G node applications. The NOP UI 202 (hereinafter may also be referred as the “UI 202”) serves as a point of interaction between a user and the NOP 110. The UI 202, accessible through a web browser, allows the users to navigate through various modules of the NOP 110. In an embodiment, the user may correspond to an admin or an automation engineer. Through the UI 202, the user provides an input to initiate an upgrade process. The input may include, but not limited to, a selection of the target servers, types of the automation scripts to be executed.

[0054] The automation adoption platform 112 may enable the automation of network management tasks and includes submodules, such as the automation adoption module 116, the procedure engine 118, the server manager 120, the execution manager 122.

[0055] The receiving engine 114-2 is configured to receive the input via the UI 202 to access the NOP 110. The control engine 114-4 is configured to navigate, based on the received input, to the automation adoption module 116 within the NOP 110. The configuration engine 114-6 may facilitate the configuration of the target servers 204-2, 204-4, 204-N. The configuration engine 114-6 may configure the group of target servers, and a plurality of services associated with each server of the group of target servers requiring an upgradation within the automation adoption module 116.

[0056] The automation adoption module 116, integrated within the automation adoption platform 112 is configured to manage automation processes within theNOP 110. The automation adoption module 116 may interact with other components such as the procedure engine 118, the server manager 120, the execution manager 122 to configure, plan, and execute the upgrade process. The automation adoption module 116 may integrate various automation tools, including configuration management tools to perform specific tasks on the target servers 204-2, 204-4, 204- N. In an implementation, with the automation adoption module 116, complex tasks such as a Docker installation may be automated across multiple servers with simple clicks on the UI 202.

[0057] The procedure engine 118 may manage the creation, and storage of operational procedures. The procedure engine 118 interacts closely with the automation adoption module 116 to ensure that the operational procedures are correctly formulated based on user-configured parameters. In an embodiment, the procedure engine 118 may coordinate with the server manager 120 and the execution manager 122 to execute the operational procedures on the target servers 204-2, 204-4, 204-N. In another embodiment, the procedure engine 118 may enable the users to upload and configure the automation scripts and the configuration files associated with the plurality of automation scripts on the NOP 110, ensuring that correct procedures are applied consistently across the network of the servers.

[0058] The server manager 120 is configured to maintain status and the configuration of the target servers 204-2, 204-4, 204-N. The server manager 120 interacts with the execution manager 122 to ensure that the target servers 204-2, 204-4, 204-N are prepared for the execution of the operational procedures.

[0059] The execution manager 122 is configured to upgrade the server environment by controlling the execution of the operational procedures on the configured group of the target servers. The execution manager 122 may receive the operational procedures from the procedure engine 118 and may coordinate with the server manager 120 to execute the operational procedures on the target servers 204-2, 204- 4, 204-N. In an implementation, the execution manager 122 may ensure that thetasks specified in the operational procedures, such as server upgradation, or Docker upgradations, are carried out efficiently and accurately on each target server.

[0060] The execution manager 122 also communicates with the log management module 124 to record a progress and results of each operation. The log management module 124 is configured to record all activities related to the execution of the operational procedures. In one or more embodiments, logs are crucial for monitoring, auditing, and troubleshooting any issues that may arise during the execution. As the execution manager 122 carries out the upgradation tasks on the target servers 204-2, 204-4, 204-N, the log management module 124 captures detailed logs of these activities, including any errors or issues encountered.

[0061] The history management module 126 maintains a historical record of all the operational procedures executed within the system. In an embodiment, the history management module 126 may store details about each operational procedure, including, but not limited to, the target servers 204-2, 204-4, 204-N involved, the automation scripts used, execution timelines, and outcomes. The history management module 126 may maintain a detailed history of all previous upgrades and automation tasks performed by the NOP 110.

[0062] The target servers 204-2, 204-4, 204-N represent physical or virtual servers that are subject to the upgradation through the automated processes. The target servers 204-2, 204-4, 204-N host the network applications, including the 5G node applications, and require regular upgradations to maintain optimal performance. The target servers 204-2, 204-4, 204-N receive the automation scripts from the execution manager 122, which executes the tasks outlined in the operational procedures, such as software installations and system configurations.

[0063] The 0AM 206 is configured for an overall administration of the NOP 110. The 0AM 206 may be configured for monitoring performance, troubleshooting issues, and ensuring that all the components are functioning correctly. The NOP 110 is integrated with the 0AM 206, allowing the 0AM 206 to retrieve critical information about a state of the system.

[0064] The database 208 is a central repository for all data related to the system's operations. In an embodiment, the database 208 may store configuration settings, user inputs, the automation scripts, the operational procedures, log files, MOP templates and the historical records. The database 208 is accessed by various components, such as the procedure engine 118 and the history management module 126, to retrieve and store information as needed.

[0065] The IAM 210 is configured to manage user authentication and authorization within the NOP 110. The IAM 210 may ensure that only authorized users may access the system 200 and perform specific actions.

[0066] The elastic load balancer 212 distributes incoming network traffic across the various components of the NOP 110 to ensure optimal performance and reliability. In an embodiment, the elastic load balancer 212 may dynamically adjust to changes in traffic patterns, preventing any single component from becoming a bottleneck.

[0067] Although FIG. 2 shows exemplary components of the system 200, in other implementations, the system 200 may include fewer components, different components, differently arranged components, or additional components than depicted in FIG. 2. Additionally, or alternatively, one or more components of the system 200 may perform functions described as being performed by one or more other components of the system 200.

[0068] FIG. 3 illustrates a flowchart depicting the method 300 for automating the upgrading of the server environment of the servers used by the network applications, in accordance with an embodiment of the present disclosure. The method 300 comprises a series of operation steps indicated by blocks 302 through 310. The method 300 starts at block 302.

[0069] At step 302, the receiving engine 114-2 may receive the input to access the NOP 110. The input may be received via the UI 202 presented to the user. The input may include, but is not limited to, the selection of the target servers, desired upgradeparameters, or automation script selections. The NOP 110 may be a software platform hosted on the server 100.

[0070] At step 304, based on the input received, the system 200, using the control engine 114-4, navigates to the automation adoption module 116 within the NOP 110.

[0071] At step 306, the configuration engine 114-6 is configured to configure the target servers and services associated with each server requiring the upgradation. The configuration engine identifies and prepares the appropriate group of servers. In an embodiment, the servers may correspond to, but not limited to, virtual machines, or application servers, targeted for the upgrade, based on an upgrade scope defined by the user. In one or more embodiments, the configuration engine 114-6 may also determine set of services, components, or packages installed on each server that require updating. The configuration may include loading configuration files, validating prerequisites for the upgradation, grouping servers by environment type, and mapping the automation scripts to each server.

[0072] At step 308, the procedure engine 118 may create the operational procedures based on the configuration of the target servers and the services associated with each server. The operational procedure is a structured set of instructions that is executed on the target servers 204-2, 204-4, 204-N to perform the necessary upgradation. The operational procedure is created by uploading the automation scripts and the configuration files associated with the automation scripts to the NOP 110 and selecting the automation scripts along with the associated configuration files for the execution. In an embodiment, the operational procedures may further support version control, template reuse, and conditional logic, enabling flexible automation strategies across different server environment.

[0073] In an embodiment, the procedure engine 118 may edit the operational procedures to update the automation scripts and the configuration files associated with the plurality of automation scripts via the UI 202. The automation scripts may include, but not limited to, one or more of the configuration management tool script, Docker automation scripts.

[0074] At step 310, the execution manager 122 may upgrade the server environment as per the operational procedures. The execution manager 122 may trigger the configuration management tool script to perform secure login operations on each of the configured target servers. Once access is established, the execution manager 122 proceeds to execute one or more automation scripts associated with the operational procedures. In an embodiment, the automation scripts may include software updates, application deployments, container installations, service restarts, or configuration changes. In an implementation, the automation scripts follow a Yet Another Markup Language (YAML) format.

[0075] In an implementation, the automation process may include the installation or the upgradation of the Docker on the target servers 204-2, 204-4, 204-N. The user may simply upload the automation script of the Docker to the automation adoption module 116 via the UI 202. The Docker installation or upgradation does not require the manual login to each server if the automation script of the Docker is already present. The MOP is created by selecting the Docker script, which is executed on the group of the target servers 204-2, 204-4, 204-N preconfigured as per user’s requirements.

[0076] After the execution of the MOP, the user may review the results through the UI 202. If any adjustments are necessary, the user may edit the operational procedure and re-run the operational procedure on the target servers 204-2, 204-4, 204-N which allows for iterative improvement and refinement to the upgradation process, ensuring that the server environment meets the desired specifications. The editing comprises updating the automation scripts and the configuration files associated with the automation scripts.

[0077] FIG. 4 illustrates a schematic block diagram of a computing system 400 for upgrading the server environment for the servers used by the network applications, in accordance with an embodiment of the present disclosure.

[0078] The computing system 400 includes a network 402, a network interface 404, a processor 406, an Input / Output (I / O) interface 408 and a non-transitory computerreadable storage medium 410 (hereinafter may also be referred to as the “storage medium 410” or the “storage media 410”).

[0079] The network interface 404 includes wireless network interfaces such as Bluetooth, Wi-Fi, Worldwide Interoperability for Microwave Access (WiMAX), General Packet Radio Service (GPRS), or Wideband Code Division Multiple Access (WCDMA) or wired network interfaces such as Ethernet, Universal Serial Bus (USB), or Institute of Electrical and Electronics Engineers-864 (IEEE-864).

[0080] The processor 406 may include various processing circuitry / modules and communicate with the storage medium 410 and the VO interface 408. The processor 406 is configured to execute instructions stored in the storage medium 410 and to perform various processes. The processor 406 may include an intelligent hardware device including a general -purpose processor, such as, for example, and without limitation, a Central Processing Unit (CPU), a dedicated processor, or the like, a graphics-only processing unit such as a GPU, a microcontroller, a programmable logic device, a discrete hardware component, or any combination thereof. The processor 406 may be configured to execute computer-readable instructions 410-2 stored in the storage medium 410 to cause the system 200 to perform various functions.

[0081] The storage medium 410 stores a set of instructions i.e., computer program instructions 410-1 (hereinafter may also be referred to as instructions 410-1) required by the processor 406 for controlling its overall operations.

[0082] The storage media 410 may include an electronic storage medium, a magnetic storage medium, an optical storage medium, a quantum storage medium, or the like. For example, the storage media 410 may include, but are not limited to, hard drives, floppy diskettes, optical disks, flash memory, magnetic or optical cards, solid-state memory devices, or other types of physical media suitable for storing electronic instructions. In one or more embodiments, the storage media 410 includes a Compact Disk-Read Only Memory (CD-ROM), a Compact Disk-Read / Write (CD-R / W), and / or a Digital Video Disc (DVD).

[0083] In one or more implementations, the storage medium 410 stores computer program code configured to cause the computing system 400 to perform at least a portion of the processes and / or methods. Accordingly, in at least one implementation, the computing system 400 performs the method for upgrading the server environment for the servers used by the network applications.

[0084] Embodiments of the present disclosure have been described above with reference to flowchart illustrations of methods and systems according to embodiments of the disclosure, and / or procedures, algorithms, steps, operations, formulae, or other computational depictions, which may also be implemented as computer program products. In this regard, each block or step of the flowchart, and combinations of blocks (and / or steps) in the flowchart, as well as any procedure, algorithm, step, operation, formula, or computational depiction can be implemented by various means, such as hardware, firmware, and / or software including one or more computer program instructions embodied in computer-readable program code. As will be appreciated, any such computer program instructions may be executed by one or more computer processors, including without limitation a general-purpose computer or special purpose computer, or other programmable processing apparatus to perform a group of operations comprising the operations or blocks described in connection with the disclosed method.

[0085] Further, these computer program instructions, such as embodied in computer-readable program code, may also be stored in one or more computer- readable memory or memory devices (ex. the storage medium 410) that can direct a computer processor or other programmable processing apparatus to function in a particular manner, such that the instructions 410-2 stored in the computer-readable memory or memory devices produce an article of manufacture including instruction means which implement the function specified in the block(s) of the flowchart(s).

[0086] It will further be appreciated that the term “computer program instructions” as used herein refer to one or more instructions that can be executed by the one or more processors (for example, the processor 406) to perform one or more functionsas described herein. The instructions 410-2 may also be stored remotely such as on a server, or all or a portion of the instructions can be stored locally and remotely.

[0087] Separate instances of these methods / processes may be executed on or distributed across any number of separate computer systems. A variety of alternative implementations will be understood by those having ordinary skill in the art.

[0088] Now, referring to the technical abilities and advantageous effect of the present disclosure, operational advantages that may be provided by one or more embodiments is the automation of the server environment upgradation which significantly increases an operational efficiency by reducing the time and effort required for manual configuration and the execution.

[0089] Another noteworthy advantage provided by the one or more embodiments may include, but not limited thereto, an ability of the system to automate the software installations and the upgradations without requiring the manual login to each server, particularly in environment with the large number of servers.

[0090] Further, by automating repetitive tasks such as the software installation and the system configuration, the present disclosure minimizes a risk of human error, ensuring that the upgradations are performed consistently and correctly across all the target servers. Furthermore, the operational procedures may be executed on a desired group of servers with the simple click on the UI.

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

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

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

[0094] The following list is provided for convenience and in support of the drawing figures and as part of the text of the specification, which describe innovations by reference to multiple items. Items not listed here may nonetheless be part of a given embodiment. For better legibility of the text, a given reference number is recited near some, but not all, recitations of the referenced item in the text. The same reference number may be used with reference to different examples or different instances of a given item. The list of reference numerals is:100- NOP server / Server100-2 - Communication bus102-Processor104-Memory106- Communication interface108-Input / Output (I / O) interface110- Network Operations Platform (NOP)112- Automation adoption platform114- Other modules / engines114-2- Receiving engine114-4-Control engine114-6- Configuration engine116- Automation adoption module118- Procedure engine120- Server manager122- Execution manager124-Log management module126- History management module202- NOP UI204-2, 204-4, 204-N- Target servers206- Operations, Administration, and Maintenance (0AM)208- Database210- Identity and Access Management (IAM) 210,212- Elastic Load Balancer300- Method for automating upgrading of server environment of servers used by network applications302- 310- Steps to perform method 300400- Computing System402- Network404- Network Interface406- Processor408- I / O interface410- Non transitory computer readable storage medium410-2- Instructions

Claims

We Claim:

1. A method (300) for upgrading server environment in a communication network, the method comprising: receiving (302), by a receiving engine (114-2) via a User Interface (UI) (202), an input to access a Network Operations Platform (NOP) (110); navigating (304), by a control engine (114-4), to an automation adoption module (116) within the NOP (110) based on the received input; configuring (306), by a configuration engine (114-6), a group of target servers (204-2, 204-4, 204-N), and a plurality of services associated with each server of the group of target servers (204-2, 204-4, 204-N) requiring an upgradation within the automation adoption module (116); creating (308), by a procedure engine (118), an operational procedure based on the configuration of the group of the target servers (204-2, 204-4, 204-N) and the plurality of services; and upgrading (310), by an execution manager (122), the server environment by controlling an execution of the operational procedure on the configured group of the target servers.

2. The method (300) as claimed in claim 1, further comprising editing, by the procedure engine (118) via the UI (202), the operational procedure to update a plurality of automation scripts and configuration files associated with the plurality of automation scripts.

3. The method (300) as claimed in claim 1, wherein the creating the operational procedure comprises uploading, by the procedure engine (118), a plurality of automation scripts and configuration files associated with the plurality of automation scripts on the NOP (110).

4. The method (300) as claimed in claim 3, wherein one of the plurality of automation scripts includes a configuration management tool script.

5. The method (300) as claimed in claim 1, wherein the upgrading the server environment comprises: triggering, by the execution manager (122), an execution of a configuration management tool script to perform a login operation on the configured group of target servers; and executing, by the execution manager (122) upon the login operation, one or more of a plurality of automation scripts on the configured group of target servers to upgrade the server environment.

6. The method (300) as claimed in claim 3, wherein one or more of the plurality of automation scripts further include Docker automation scripts.

7. A system (200) for upgrading server environment in a communication network, the system comprising: a receiving engine (114-2) configured to receive, via a User Interface (UI) (202), an input to access a Network Operations Platform (NOP) (110); a control engine (114-4) configured to navigate to an automation adoption module (116) within the NOP (110) based on the received input; a configuration engine (114-6) configured to configure a group of target servers (204-2, 204-4, 204-N), and a plurality of services associated with each server of the group of target servers (204-2, 204-4, 204-N) requiring an upgradation within the automation adoption module (116); a procedure engine (118) configured to create an operational procedure based on the configuration of the group of the target servers (204-2, 204-4, 204-N) and the plurality of services; and an execution manager (122) configured to upgrade the server environment by controlling an execution of the operational procedure on the configured group of the target servers.

8. The system (200) as claimed in claim 7, wherein the procedure engine (118) is further configured to edit via the UI (202), the operational procedure, to update aplurality of automation scripts and configuration files associated with the plurality of automation scripts.

9. The system (200) as claimed in claim 7, wherein, to create the operational procedure, the procedure engine (118) is configured to upload a plurality of automation scripts and configuration files associated with the plurality of automation scripts on the NOP (110).

10. The system (200) as claimed in claim 9, wherein one of the plurality of automation scripts includes a configuration management tool script.

11. The system (200) as claimed in claim 7, wherein, to upgrade the server environment, the execution manager (122) is configured to: trigger an execution of a configuration management tool script to perform a login operation on the configured group of target servers; and execute, upon the login operation, one or more of a plurality of automation scripts on the configured group of target servers to upgrade the server environment.

12. The system (200) as claimed in claim 9, wherein one or more of the plurality of automation scripts further include Docker automation scripts.

13. A computer program product comprising computer-executable instructions that are stored on a non-transitory computer-readable medium and that, when executed by at least one processing unit performs operations comprising: receiving, via a User Interface (UI) (202), an input to access a Network Operations Platform (NOP) (110); navigating to an automation adoption module (116) within the NOP (110) based on the received input; configuring a group of target servers (204-2, 204-4, 204-N), and a plurality of services associated with each server of the group of target servers (204-2, 204-4, 204-N) requiring an upgradation within the automation adoption module (116);creating an operational procedure based on the configuration of the group of the target servers (204-2, 204-4, 204-N) and the plurality of services; and upgrading the server environment by controlling an execution of the operational procedure on the configured group of the target servers.

Images