DESC:
FORM 2
THE PATENTS ACT, 1970
(39 of 1970)
&
THE PATENTS RULES, 2003

COMPLETE SPECIFICATION
(See section 10 and rule 13)

1. TITLE OF THE INVENTION
SYSTEM AND METHOD FOR ASSET MANAGEMENT
2. APPLICANT(S)
NAME NATIONALITY ADDRESS
JIO PLATFORMS LIMITED INDIAN OFFICE-101, SAFFRON, NR. CENTRE POINT, PANCHWATI 5 RASTA, AMBAWADI, AHMEDABAD 380006, GUJARAT, INDIA
3.PREAMBLE TO THE DESCRIPTION

THE FOLLOWING SPECIFICATION PARTICULARLY DESCRIBES THE NATURE OF THIS INVENTION AND THE MANNER IN WHICH IT IS TO BE PERFORMED.

The present application takes priority from Indian Provisional Applications Bearing Number 202321048718 filed on 19th July 2023 and 202321049118 filed on 20th July 2023, the disclosure of which is hereby incorporated by reference herein.
FIELD OF THE INVENTION
[0001] The present invention relates to the field of wireless communication systems, more particularly relates to a method and a system for asset management.

BACKGROUND OF THE INVENTION
[0002] Asset management is a process of developing, operating, maintaining, upgrading, and disposing of an asset throughout its life cycle. It collects all asset data and compiles reports to optimize the usage of assets.
[0003] Presently available asset management systems manually obtain asset related details such as details relating to middleware and technologies running on a server. This can be very time-consuming.
[0004] Therefore, there is a need for a system/method that can overcome the cumbersome process of manually obtaining details pertaining to assets related details such as details relating to middleware and technology applications without compromising with the system’s security and privacy.
SUMMARY OF THE INVENTION
[0005] One or more embodiments of the present disclosure provide a method and system for asset management.
[0006] In one aspect of the present invention, a method for asset management is disclosed. The method includes the step of receiving, by one or more processors, one or more discovery requests pertaining to discovery data of a plurality of remote assets in a network. The method includes the step of accessing, by the one or more processors, the plurality of remote assets based on the one or more discovery requests received. The method includes the step of executing, by the one or more processors, one or more customized scripts pertaining to the plurality of remote assets accessed. The method includes the step of fetching, by the one or more processors, , output data of the one or more executed customized scripts. The output data pertains to discovery data of each of the plurality of remote assets in the network.
[0007] In one embodiment, the discovery data includes information related to at least one of one or more middleware and technologies/applications running on the plurality of remote assets, wherein the one or more middleware and the technologies/applications including at least one of, version details, locations, installation paths, log paths, home/log paths, error log paths, process ID, and port details.
[0008] In another embodiment, the plurality of remote assets includes at least one of remote servers.
[0009] In yet another embodiment, the fetched output data of the one or more executed customized scripts are stored in a database.
[0010] In yet another embodiment, the customized scripts are a sequence of commands coded in the script.
[0011] In yet another embodiment, the one or more discovery requests are received from at least one of, a network operator.
[0012] In yet another embodiment, the discovery data is transmitted by the one or more processors to a network operator as a response to the one or more discovery requests.
[0013] In yet another embodiment, the step of accessing, the plurality of remote assets based on the one or more discovery requests received, includes the step of identifying, by the one or more processors, the plurality of remote assets based on the one or more discovery requests received. The method further includes the step of logging-in, by the one or more processors, to the identified plurality of remote assets.
[0014] In another aspect of the present invention, a system for asset management is disclosed. The system includes a transceiver configured to receive, one or more discovery requests pertaining to discovery data of a plurality of remote assets in a network. The system includes an accessing unit, configured to access the plurality of remote assets based on the one or more discovery requests received. The system includes an execution unit, configured to execute, one or more customized scripts pertaining to the plurality of remote assets accessed. The system includes a fetching unit, configured to fetch output data of the one or more executed customized scripts. The output data pertains to discovery data of each of the plurality of remote assets in the network.
[0015] In yet another aspect of the present invention, a network operator equipment is disclosed. One or more primary processors communicatively coupled to one or more processors. The one or more primary processors coupled with a memory. The memory stores instructions which when executed by the one or more primary processors causes the UE to transmit, one or more discovery requests and one or more customized scripts to the one or more processors, in order to fetch discovery data of each of the plurality of remote assets in a network.
[0016] In yet another aspect of the present invention, a non-transitory computer-readable medium having stored thereon computer-readable instructions that, when executed by a processor is disclosed. The processor is configured to receive one or more discovery requests pertaining to discovery data of a plurality of remote assets in a network. The processor is configured to access the plurality of remote assets based on the one or more discovery requests received. The processor is configured to execute one or more customized scripts pertaining to the plurality of remote assets accessed. The processor is configured to fetch output data of the one or more executed customized scripts. The output data pertains to discovery data of each of the plurality of remote assets in the network.
[0017] Other features and aspects of this invention will be apparent from the following description and the accompanying drawings. The features and advantages described in this summary and in the following detailed description are not all-inclusive, and particularly, many additional features and advantages will be apparent to one of ordinary skill in the relevant art, in view of the drawings, specification, and claims hereof. Moreover, it should be noted that the language used in the specification has been principally selected for readability and instructional purposes and may not have been selected to delineate or circumscribe the inventive subject matter, resort to the claims being necessary to determine such inventive subject matter.
BRIEF DESCRIPTION OF THE DRAWINGS
[0018] 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. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components, electronic components or circuitry commonly used to implement such components.
[0019] FIG. 1 is an exemplary block diagram of an environment for asset management, according to one or more embodiments of the present invention;
[0020] FIG. 2 is an exemplary block diagram of an architecture for asset management, according to one or more embodiments of the present invention;
[0021] FIG. 3 is an exemplary block diagram of a system for asset management, according to one or more embodiments of the present invention;
[0022] FIG. 4 is a schematic representation of the present system of FIG. 3 workflow, according to the one or more embodiments of the present invention;
[0023] FIG. 5 is a flow diagram illustrating a method for asset management, according to one or more embodiments of the present invention; and
[0024] FIG. 6 is a flow diagram illustrating the method for asset management, according to one or more embodiments of the present invention.
[0025] The foregoing shall be more apparent from the following detailed description of the invention.
DETAILED DESCRIPTION OF THE INVENTION
[0026] Some embodiments of the present disclosure, illustrating all its features, will now be discussed in detail. It must also be noted that as used herein and in the appended claims, the singular forms "a", "an" and "the" include plural references unless the context clearly dictates otherwise.
[0027] Various modifications to the embodiment will be readily apparent to those skilled in the art and the generic principles herein may be applied to other embodiments. However, one of ordinary skill in the art will readily recognize that the present disclosure including the definitions listed here below are not intended to be limited to the embodiments illustrated but is to be accorded the widest scope consistent with the principles and features described herein.
[0028] A person of ordinary skill in the art will readily ascertain that the illustrated steps detailed in the figures and here below are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. These examples are presented herein for purposes of illustration, and not limitation. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed embodiments.
[0029] Referring to FIG. 1, FIG. 1 illustrates an exemplary block diagram of an environment 100 for asset management, according to one or more embodiments of the present invention. The environment 100 includes a network 105, a network operator equipment 110, a server 115, and a system 120. The network operator equipment 110 aids a user to interact with the system 120 for transmitting one or more discovery requests and one or more customized scripts to the one or more processors 305 (shown in FIG. 3), in order to fetch discovery data of each of the plurality of remote assets in the network 105. In an embodiment, the user includes, at least one of, a network operator.
[0030] The term “plurality of remote assets” and “plurality of remote servers” are used in combination and interchangeably herein without limiting the scope of the disclosure.
[0031] For the purpose of description and explanation, the description will be explained with respect to the network operator equipment 110, or to be more specific will be explained with respect to a first network operator equipment 110a, a second network operator equipment 110b, and a third network operator equipment 110c, and should nowhere be construed as limiting the scope of the present disclosure. Each of the network operator equipment 110 from the first network operator equipment 110a, the second network operator equipment 110b, and the third network operator equipment 110c is configured to connect to the server 115 via the network 105.
[0032] In an embodiment, the first network operator equipment 110a is one of, but is not limited to, hubs, switches, routers, bridges, gateways, modems, repeaters, and access points.
[0033] In an embodiment, each of the second network operator equipment 110b, and the third network operator equipment 110c is one of, but not limited to, any electrical, electronic, electro-mechanical or an equipment and a combination of one or more of the above devices such as smartphones, virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other computing device.
[0034] The network 105 includes, by way of example but not limitation, one or more of a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a Public-Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, or some combination thereof. The network 105 may include, but is not limited to, a Third Generation (3G), a Fourth Generation (4G), a Fifth Generation (5G), a Sixth Generation (6G), a New Radio (NR), a Narrow Band Internet of Things (NB-IoT), an Open Radio Access Network (O-RAN), and the like.
[0035] The server 115 may include by way of example but not limitation, one or more of a standalone server, a server blade, a server rack, a bank of servers, a server farm, hardware supporting a part of a cloud service or system, a home server, hardware running a virtualized server, one or more processors executing code to function as a server, one or more machines performing server-side functionality as described herein, at least a portion of any of the above, some combination thereof. In an embodiment, the entity may include, but is not limited to, a vendor, a network operator, a company, an organization, a university, a lab facility, a business enterprise, a defense facility, or any other facility that provides content.
[0036] The environment 100 further includes the system 120 communicably coupled to the server 115 and each of the first network operator equipment 110a, the second network operator equipment 110b, and the third network operator equipment 110c via the network 105. The system 120 is configured for managing the asset. The system 120 is adapted to be embedded within the server 115 or is embedded as the individual entity, as per multiple embodiments of the present invention.
[0037] Operational and construction features of the system 120 will be explained in detail with respect to the following figures.
[0038] FIG. 2 illustrates an exemplary block diagram of an architecture 200 of the system 120 for asset management, according to one or more embodiments of the present invention.
[0039] The architecture 200 of the system 120 includes processors 305 (shown in FIG.3) of the system 120, the plurality of remote servers 115, a distributed cache 205 and a database 210. The processors 305 of the system 120 is configured to manage the asset.
[0040] The processors 305 of the system 120 is configured to execute one or more customized scripts and collect the discovery data from the plurality of remote servers 115. In one embodiment, the discovery data is associated with the plurality of remote servers 115. The discovery data includes information related to one or more middleware and technologies/applications, including at least one of, version details, location, installation paths, log paths, home/log paths, error log paths, process ID, and port details. In an embodiment, the one or more middleware pertains to the plurality of remote servers 115, including at least one of, Apache, Tomcat, JBoss, Oracle Hypertext Transfer Protocol Server (OHS), Webserver, and Web logic. In one embodiment, the technologies/applications running on the plurality of remote assets, including at least one of, Redis, Kafka, Elasticsearch, Docker, Keydb, Aerospike, My Structured Query Language (MySQL), Oracle, Data Business Language (DBL), Spike, Cassandra, MongoDB, Hadoop, and Spark.
[0041] 210In one embodiment, the processor 305 of the system 120 is configured to further capture and retrieve real-time discovered data from the plurality of servers 115. In one embodiment, the processors 305 of the system 120 are configured to fetch the discovery data associated with each of the plurality of servers 115. The discovery data associated with each of the plurality of servers 115 is temporarily stored in the distributed cache 205. In one embodiment, the real-time discovery data associated with each of the plurality of servers 115 is stored in the database 210.
[0042] FIG. 3 is an exemplary block diagram of the system 120 for asset management, according to one or more embodiments of the present invention.
[0043] The system 120 includes the processors 305, a memory 310, a user interface 315, and the database 210. For the purpose of description and explanation, the description will be explained with respect to one or more processors 305, or to be more specific will be explained with respect to the processor 305 and should nowhere be construed as limiting the scope of the present disclosure. The one or more processor 305, hereinafter referred to as the processor 305 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, single board computers, and/or any devices that manipulate signals based on operational instructions.
[0044] As per the illustrated embodiment, the processor 305 is configured to fetch and execute computer-readable instructions stored in the memory 310. The memory 310 may be configured to store one or more computer-readable instructions or routines in a non-transitory computer-readable storage medium, which may be fetched and executed to create or share data packets over a network service. The memory 310 may include any non-transitory storage device including, for example, volatile memory such as RAM, or non-volatile memory such as EPROM, flash memory, and the like.
[0045] The user interface 315 includes a variety of interfaces, for example, interfaces for a Graphical User Interface (GUI), a web user interface, a Command Line Interface (CLI), and the like. The user interface 315 facilitates communication of the system 120. In one embodiment, the user interface 315 provides a communication pathway for one or more components of the system 120. Examples of the one or more components include, but are not limited to, the network operator equipment 110, and the database 210.
[0046] The database 210 is configured to store the data from the network operator equipment 110. The database 210 is one of, but not limited to, a centralized database, a cloud-based database, a commercial database, an open-source database, a distributed database, an end-user database, a graphical database, a No-Structured Query Language (NoSQL) database, an object-oriented database, a personal database, an in-memory database, a document-based database, a time series database, a wide column database, a key value database, a search database, a cache databases, and so forth. The foregoing examples of database 210 types are non-limiting and may not be mutually exclusive e.g., a database can be both commercial and cloud-based, or both relational and open-source, etc.
[0047] Further, the processor 305, in an embodiment, may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processor 305. In the examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processor 305 may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for processor 305 may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the memory 310 may store instructions that, when executed by the processing resource, implement the processor 305. In such examples, the system 120 may comprise the memory 310 storing the instructions and the processing resource to execute the instructions, or the memory 310 may be separate but accessible to the system 120 and the processing resource. In other examples, the processor 305 may be implemented by electronic circuitry.
[0048] In order for the system 120 to manage the asset. The processor 305 includes a transceiver 320, an accessing unit 325, an execution unit 330, and a fetching unit 335 communicably coupled to each other. In an embodiment, operations and functionalities of the transceiver 320, the accessing unit 325, the execution unit 330, and the fetching unit 335 can be used in combination or interchangeably to manage the asset.
[0049] The transceiver 320 is configured to receive the one or more discovery requests pertaining to discovery data of the plurality of remote assets in the network 105. In an embodiment, the discovery data includes information related to one or more middleware and technologies/applications, including at least one of, version details, location, installation paths, log paths, home/log paths, error log paths, process ID, and port details. In an embodiment, the one or more middleware pertains to the plurality of remote servers 115, including at least one of, Apache, Tomcat, JBoss, Oracle Hypertext Transfer Protocol Server (OHS), Webserver, and Web logic. In one embodiment, the technologies/applications running on the plurality of remote assets, includes at least one of, Redis, Kafka, Elasticsearch, Docker, Keydb, Aerospike, My Structured Query Language (MySQL), Oracle, DBL, Spike, Cassandra, MongoDB, Hadoop, and Spark. The one or more discovery requests are messages or queries transmitted within the network 105 to locate and identify various devices, services, or resources such as assets. The one or more discovery requests are typically part of a discovery protocol, which automates the process of detecting and cataloging the plurality of remote assets. In an embodiment, the one or more discovery requests are received from at least one of, a network operator.
[0050] Upon receiving the one or more discovery requests from the transceiver 320, the accessing unit 325 is configured to access the plurality of remote assets based on the one or more discovery requests received. The one or more discovery requests contain information about the plurality of remote assets within the network 105. Based on the information provided in the one or more discovery requests, the accessing unit 325 is configured to initiate connections to the plurality of remote assets, which involves sending further queries, establishing communication sessions, or retrieving data from the plurality of assets. In owing to this, the accessing unit 325 is configured to identify the plurality of remote assets based on the one or more discovery requests received.
[0051] Upon identifying the plurality of remote assets, the accessing unit 325 is configured to log-in to the identified plurality of remote assets. Furthermore, the accessing unit 325 is configured to collect relevant information from the plurality of remote assets, such as status, configuration details, service availability, and performance metrics. In order to this, the accessing unit 225 is configured to update the network's inventory or the database 210 with the newly discovered data about the plurality of remote assets, which ensures that the network 105 has an accurate and up-to-date view of all connected devices and resources.
[0052] Upon logging-in to the identified plurality of remote assets, the execution unit 230 is configured to execute one or more customized scripts pertaining to the plurality of remote assets accessed. The execution unit 230 is configured to select the appropriate script for each remote asset based on predefined criteria such as asset type, current status, and specific tasks that need to be performed. The customized scripts are a sequence of commands coded in the script based on the type of remote assets and perform specific tasks or collect relevant information from the plurality of remote assets. The sequence of commands coded within the scripts can perform a variety of functions, such as configuring device settings, retrieving system logs or status information, performing diagnostics or health checks, and collecting performance metrics or usage statistics, which saves end user time to separately login to the identified plurality of remote assets to check the health status and other details.
[0053] As per one or more embodiments, the execution unit 230 is configured to run the one or more customized scripts on the plurality of remote assets. Further, the execution unit 230 is configured to monitor the execution of the one or more customized scripts in real-time, ensuring that each command is executed successfully, which also handles any errors or exceptions that occur during execution. By doing so, the end user realizes a smooth experience of monitoring all the middleware and technologies/applications in the system 120 at a single place without compromising the system’s security and privacy.
[0054] Upon executing the one or more customized scripts pertaining to the plurality of remote assets accessed, the fetching unit 235 is configured to fetch output data of the one or more executed customized scripts. The fetching unit 235 is configured to recognize patterns in the output data, identifying important metrics, anomalies, or specific data points that need to be fetched. The fetching unit 235 is configured to classify the output data into relevant categories, such as success messages, error logs, performance metrics, etc., to prioritize which type of the data needs to be fetched.
[0055] As per one embodiment, the output data pertains to the discovery data of each of the plurality of remote assets in the network 105. The fetching unit 235 can parse through large volumes of the output data quickly, identifying and extracting relevant information without manual intervention. The fetching unit 235 filters out irrelevant or redundant data, focusing only on the relevant information such as the discovery data that needs to be fetched. The discovery data is transmitted by the one or more processors 305 to the network operator as a response to the one or more discovery requests. Upon fetching the output data of the one or more executed customized scripts, the fetched output data of the one or more executed customized scripts are stored in the database 240.
[0056] FIG. 4 is a schematic representation of the workflow of the system of FIG. 3, according to one or more embodiments of the present invention. More specifically, FIG. 4 illustrates the system 120 configured for asset management. It is to be noted that the embodiment with respect to FIG. 4 will be explained with respect to the first network operator equipment 110a for the purpose of description and illustration and should nowhere be construed as limited to the scope of the present disclosure.
[0057] As mentioned earlier in FIG.1, In an embodiment, the first network operator equipment 110a may encompass electronic apparatuses. These devices are illustrative of, but not restricted to, modems, routers, switches, laptops, tablets, smartphones (including phones), or other devices enabled for web connectivity. The scope of the first network operator equipment 110a explicitly extends to a broad spectrum of electronic devices capable of executing computing operations and accessing networked resources, thereby providing users with a versatile range of functionalities for both personal and professional applications. This embodiment acknowledges the evolving nature of electronic devices and their integral role in facilitating access to digital services and platforms. In an embodiment, the first network operator equipment 110a can be associated with multiple users. Each of the first network operator equipment 110a is communicatively coupled with the processor 305.
[0058] The first network operator equipment 110a includes one or more primary processors 405 communicably coupled to the one or more processors 305 of the system 120. The one or more primary processors 405 are coupled with a memory 410 storing instructions which are executed by the one or more primary processors 405. Execution of the stored instructions by the one or more primary processors 405 enables the first network operator equipment 110a to transmit the one or more discovery requests and the one or more customized scripts to the one or more processors 305 in order to fetch the discovery data of each of the plurality of remote assets in the network 105.
[0059] Furthermore, the one or more primary processors 405 within the first network operator equipment 110a are uniquely configured to execute a series of steps as described herein. This configuration underscores the processor 305 capability to manage operation of the network 105. The operational synergy between the one or more primary processors 405 and the additional processors, guided by the executable instructions stored in the memory 410.
[0060] As mentioned earlier in FIG.3, the system 120 includes the one or more processors 305, the memory 310, the user interface 315, and the database 210. The operations and functions of the one or more processors 305, the memory 310, the user interface 315, and the database 210 are already explained in FIG. 2. For the sake of brevity, a similar description related to the working and operation of the system 120 as illustrated in FIG. 3 has been omitted to avoid repetition.
[0061] Further, the processor 305 includes the transceiver 320, the accessing unit 325, the execution unit 330, and the fetching unit 335. The operations and functions of the transceiver 320, the accessing unit 325, the execution unit 330, and the fetching unit 335 are already explained in FIG. 3. Hence, for the sake of brevity, a similar description related to the working and operation of the system 120 as illustrated in FIG. 3 has been omitted to avoid repetition. The limited description provided for the system 120 in FIG. 3, should be read with the description provided for the system 120 in the FIG. 3 above, and should not be construed as limiting the scope of the present disclosure.
[0062] FIG. 5 is a flow diagram illustrating a method 500 for asset management, according to one or more embodiments of the present invention. For the purpose of description, the method 500 is described with the embodiments as illustrated in FIG. 2 and should nowhere be construed as limiting the scope of the present disclosure.
[0063] At step 505, the method 500 includes the step of receiving the one or more discovery requests pertaining to discovery data of a plurality of remote assets in the network 105 by the transceiver 320. In an embodiment, the discovery data includes information related to one or more middleware and technologies/applications, including at least one of, version details, location, installation paths, log paths, home/log paths, error log paths, process ID, and port details. The one or more discovery requests are messages or queries transmitted within the network 105 to locate and identify various devices, services, or resources such as assets. The one or more discovery requests are typically part of a discovery protocol, which automates the process of detecting and cataloging the plurality of remote assets. In an embodiment, the one or more discovery requests are received from at least one of, a network operator.
[0064] At step 510, the method 500 includes the step of accessing the plurality of remote assets based on the one or more discovery requests received by the accessing unit 325. The one or more discovery requests contain information about the plurality of remote assets being sought within the network 105. Based on the information provided in the one or more discovery requests, the accessing unit 325 is configured to initiate connections to the plurality of remote assets, which involves sending further queries, establishing communication sessions, or retrieving data from the identified assets.
[0065] At step 515, the method 500 includes the step of executing the one or more customized scripts pertaining to the plurality of remote assets accessed by the execution unit 330. The execution unit 330 is configured to select the appropriate script for each remote asset based on predefined criteria such as asset type, current status, and specific tasks that need to be performed. The customized scripts are sequence of commands coded in the script based on the type of remote asset and perform specific tasks or collect relevant information from the plurality of remote assets. The sequence of commands coded within the scripts can perform a variety of functions, such as configuring device settings, retrieving system logs or status information, performing diagnostics or health checks, and collecting performance metrics or usage statistics, which saves end user time to separately login to the identified plurality of remote assets to check the health status and other details.
[0066] As per one or more embodiments, the execution unit 230 is configured to run the one or more customized scripts on the plurality of remote assets. Further, the execution unit 230 is configured to monitor the execution of the one or more customized scripts in real-time, ensuring that each command is executed successfully, which also handles any errors or exceptions that occur during execution. By doing so, the end user realizes a smooth experience of monitoring all the middleware in the system 120 at a single place without compromising the system’s security and privacy.
[0067] At step 520, the method 500 includes the step of fetching output data of the one or more executed customized scripts by the fetching unit 235. The fetching unit 235 can recognize patterns in the output data, identifying important metrics, anomalies, or specific data points that need to be fetched. The fetching unit 235 is configured to classify the output data into relevant categories, such as success messages, error logs, performance metrics, etc., to prioritize which type of the data needs to be fetched.
[0068] As per one embodiment, the output data pertains to the discovery data of each of the plurality of remote assets in the network 105. The fetching unit 235 can parse through large volumes of the output data quickly, identifying and extracting relevant information without manual intervention. The fetching unit 235 filters out irrelevant or redundant data, focusing only on the relevant information such as the discovery data that needs to be fetched. The discovery data is transmitted by the one or more processors 305 to the network operator as a response to the one or more discovery requests. Upon fetching the output data of the one or more executed customized scripts, the fetched output data of the one or more executed customized scripts are stored in the database 240.
[0069] FIG. 6 is a flow diagram illustrating a method 600 for asset management, according to one or more embodiments of the present disclosure.
[0070] At step 605, the method 600 includes the step of identifying the plurality of remote assets based on the one or more discovery requests received by the accessing unit 325.
[0071] At step 610, the method 600 includes the step of logging-in to the identified plurality of remote assets based on identifying the plurality of remote assets by the accessing unit 325. Furthermore, the accessing unit 325 is configured to collect relevant information from the plurality of remote assets, such as status, configuration details, service availability, and performance metrics.
[0072] In order to this, the accessing unit 225 is configured to update the network's inventory or the database 210 with the newly discovered data about the plurality of remote assets, which ensures that the network 105 has an accurate and up-to-date view of all connected devices and resources.
[0073] The present invention further discloses a non-transitory computer-readable medium having stored thereon computer-readable instructions. The computer-readable instructions are executed by the processor 305 is disclosed. The processor 305 is configured to receive one or more discovery requests pertaining to discovery of a plurality of remote assets in a network 105. The processor 305 is configured to access the plurality of remote assets based on the one or more discovery requests received. The processor 305 is configured to execute one or more customized scripts pertaining to the plurality of remote assets accessed. The processor 305 is configured to fetch output data of the one or more executed customized scripts. The output data pertains to discovery data of each of the plurality of remote assets in the network 105.
[0074] A person of ordinary skill in the art will readily ascertain that the illustrated embodiments and steps in description and drawings (FIG.1-6) are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. These examples are presented herein for purposes of illustration, and not limitation. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed embodiments.
[0075] The present disclosure provides technical advancement for fetching output data of the one or more executed customized scripts, identifying the plurality of remote assets based on the one or more discovery requests received, and logging-in to the identified plurality of remote assets without manual intervention. By doing so, the present invention saves end user time to separately login to the identified plurality of remote assets to check the health status and other details and provides smooth experience for end user for monitoring all the middleware in their system at a single place without compromising with the system’s security and privacy.
[0076] The present invention offers multiple advantages over the prior art and the above listed are a few examples to emphasize on some of the advantageous features. The listed advantages are to be read in a non-limiting manner.

REFERENCE NUMERALS

[0077] Environment - 100;
[0078] Network-105;
[0079] Network operator equipment- 110;
[0080] Server - 115;
[0081] System -120;
[0082] Distributed cache- 205;
[0083] Database- 210;
[0084] Processor - 305;
[0085] Memory - 310;
[0086] User interface- 315;
[0087] Transceiver – 320;
[0088] Accessing unit– 325;
[0089] Executing unit – 330;
[0090] Fetching unit– 335.
,CLAIMS:CLAIMS
We Claim:
1. A method (500) for asset management, the method (500) comprising the steps of:
receiving, by one or more processors (305), one or more discovery requests pertaining to discovery data of a plurality of remote assets in a network (105);
accessing, by the one or more processors (305), the plurality of remote assets based on the one or more discovery requests received;
executing, by the one or more processors (305), one or more customized scripts pertaining to the plurality of remote assets accessed; and
fetching, by the one or more processors (305), , output data of the one or more executed customized scripts, wherein the output data pertains to discovery data of each of the plurality of remote assets in the network (105).

2. The method (500) as claimed in claim 1, wherein the discovery data includes information related to at least one of one or more middleware and technologies/applications running on the plurality of remote assets, wherein the one or more middleware and the technologies/applications include at least one of, version details, locations, installation paths, log paths, home/log paths, error log paths, process ID, and port details.

3. The method (500) as claimed in claim 1, wherein the plurality of remote assets includes at least one of remote servers.

4. The method (500) as claimed in claim 1, wherein the fetched output data of the one or more executed customized scripts are stored in a database (210).

5. The method (500) as claimed in claim 1, wherein the customized scripts are a sequence of commands coded in the script.

6. The method (500) as claimed in claim 1, wherein the one or more discovery requests are received from at least one of, a network operator.

7. The method (500) as claimed in claim 1, wherein the discovery data is transmitted by the one or more processors (305) to a network operator as a response to the one or more discovery requests.

8. The method (500) as claimed in claim 1, wherein the step of accessing, the plurality of remote assets based on the one or more discovery requests received, includes the steps of:
identifying, by the one or more processors (305), the plurality of remote assets based on the one or more discovery requests received; and
logging-in, by the one or more processors (305), to the identified plurality of remote assets.

9. A system (120) for asset management, the system (120) comprising:
a transceiver (320), configured to, receive, one or more discovery requests pertaining to discovery data of a plurality of remote assets in a network (105);
an accessing unit (325), configured to, access, the plurality of remote assets based on the one or more discovery requests received;
an execution unit (330), configured to, execute, one or more customized scripts pertaining to the plurality of remote assets accessed; and
a fetching unit (335), configured to, fetch output data of the one or more executed customized scripts, wherein the output data pertains to discovery data of each of the plurality of remote assets in the network (105).

10. The system (120) as claimed in claim 9, wherein the discovery data includes information related to at least one of one or more middleware and technologies/applications running on the plurality of remote assets, wherein the one or more middleware and the technologies/applications include at least one of, version details, locations, installation paths, log paths, home/log paths, error log paths, process ID, and port details.

11. The system (120) as claimed in claim 9, wherein the plurality of remote assets includes at least one of remote servers.

12. The system (120) as claimed in claim 9, wherein the fetched output data of the one or more executed customized scripts are stored in a database (210).

13. The system (120) as claimed in claim 9, wherein the customized scripts are a sequence of commands coded in the script.

14. The system (120) as claimed in claim 9, wherein the one or more discovery requests are received from at least one of, a network operator.

15. The system (120) as claimed in claim 9, wherein the discovery data is transmitted by the one or more processors (205) to a network operator as a response to the one or more discovery requests.

16. The system (120) as claimed in claim 9, wherein the accessing unit (325), accesses, the plurality of remote assets based on the one or more discovery requests received, by:
identifying, the plurality of remote assets based on the one or more discovery requests received; and
logging-in, to the identified plurality of remote assets.

17. A network operator equipment (110), comprising:
one or more primary processors (405) communicatively coupled to one or more processors (305), the one or more primary processors (405) coupled with a memory (410), wherein said memory (410) stores instructions which when executed by the one or more primary processors (405) causes the network operator equipment (110) to:
transmit, one or more discovery requests and one or more customized scripts to the one or more processors (305), in order to fetch discovery data of each of the plurality of remote assets in a network (105); and
wherein the one or more processors (305) is configured to perform the steps as claimed in claim 1.