WO2025052451A1 - Procédé et système de gestion d'une ou de plusieurs fonctions de réseau dans un réseau - Google Patents

Procédé et système de gestion d'une ou de plusieurs fonctions de réseau dans un réseau Download PDF

Info

Publication number
WO2025052451A1
WO2025052451A1 PCT/IN2024/051647 IN2024051647W WO2025052451A1 WO 2025052451 A1 WO2025052451 A1 WO 2025052451A1 IN 2024051647 W IN2024051647 W IN 2024051647W WO 2025052451 A1 WO2025052451 A1 WO 2025052451A1
Authority
WO
WIPO (PCT)
Prior art keywords
user
network
network functions
event request
processors
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/IN2024/051647
Other languages
English (en)
Inventor
Aayush Bhatnagar
Ankit Murarka
Rizwan Ahmad
Kapil Gill
Arpit Jain
Shashank Bhushan
Jugal Kishore
Meenakshi Sarohi
Kumar Debashish
Supriya KAUSHIK DE
Gaurav Kumar
Kishan Sahu
Gaurav Saxena
Vinay Gayki
Mohit Bhanwria
Durgesh KUMAR
Rahul Kumar
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Jio Platforms Ltd
Original Assignee
Jio Platforms Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Jio Platforms Ltd filed Critical Jio Platforms Ltd
Publication of WO2025052451A1 publication Critical patent/WO2025052451A1/fr
Anticipated expiration legal-status Critical
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/085—Retrieval of network configuration; Tracking network configuration history
    • H04L41/0853—Retrieval of network configuration; Tracking network configuration history by actively collecting configuration information or by backing up configuration information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/02—Standardisation; Integration
    • H04L41/0213—Standardised network management protocols, e.g. simple network management protocol [SNMP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities

Definitions

  • the present invention relates to communication network management, more particularly relates to a method and a system for management of one or more network functions in the communication network.
  • the communication network comprises of many network elements which are configured to operate in specific manners to improve credibility of the communication network.
  • NF network function
  • the network functions which may be container network function (CNF) or virtual network function (VNF) etc. are managed at the backend by manual interventions. Managing each network function (NF) by different interfaces is time and resource inefficient, which may also invoke unwanted co-ordination errors in the network.
  • One or more embodiments of the present disclosure provide a method and system for management of one or more network functions in a network.
  • the system for management of the one or more network functions in the network includes a transceiver configured to receive an event request from a user using a User Equipment (UE).
  • the event request pertains to accessing data pertaining to one or more network functions in the network.
  • the system further includes a querying unit configured to query an Inventory Manager (IM) to search for the data pertaining to the one or more network functions based on the received event request.
  • the system further includes a retrieving unit configured to retrieve information of the searched data pertaining to the one or more network functions based on the received event request.
  • the system further includes a generating unit configured to generate an Inventory Manager User Interface (IM_UI) between the user and the IM.
  • IM_UI Inventory Manager User Interface
  • the transceiver subsequent to receiving the event request from the user using the UE is further configured to transmit an event acknowledgment response to the user using the UE.
  • the event request is received from at least one of, a Hypertext Transfer Protocol (HTTP).
  • HTTP Hypertext Transfer Protocol
  • the querying unit queries the IM to search for the data pertaining to the one or more network functions based on the received event request, by assigning, a task to at least a first instance to search for the data pertaining to the one or more network functions at the IM. Thereafter, the querying unit is configured to maintain one or more substitute instances and re-assign the task to the one or more substitute instances when the first instance fails to perform the task.
  • the IM_UI is an async based interface for communication between the user and the IM.
  • the IM includes a database to store the data related to the one or more network functions.
  • modifying the searched data includes operations of one of, create, update, fetch and delete the searched data.
  • the generating unit is further configured to generate one or more flavors pertaining to attributes of the one or more network functions based on the user customizing one or more parameters in one or more categories from the UE.
  • the one or more parameters include at least one of, Central Processing Unit (CPU) and Random Access Memory (RAM).
  • the method for management of network functions in the network includes the step of receiving an event request from a user using a User Equipment (UE).
  • the event request pertains to accessing data pertaining to one or more network functions in the network.
  • the method further includes the step of querying an Inventory Manager (IM) to search for the data pertaining to the one or more network functions based on the received event request.
  • the method further includes the step of retrieving information of the searched data pertaining to the one or more network functions based on the received event request.
  • the method further includes the step of generating an Inventory Manager User Interface (IM_UI) between the user and the IM.
  • IM_UI Inventory Manager User Interface
  • the IM_UI enables the user to modify the searched data pertaining to the one or more network functions stored at the IM on retrieval of the searched data.
  • a non-transitory computer-readable medium having stored thereon computer-readable instructions is disclosed.
  • the computer-readable instructions are executed by a processor.
  • the processor is configured to receive an event request from a user using a User Equipment (UE).
  • the event request pertains to accessing data pertaining to one or more network functions in the network.
  • the processor is configured to query an Inventory Manager (IM) to search for the data pertaining to the one or more network functions based on the received event request.
  • the processor is configured to retrieve information of the searched data pertaining to the one or more network functions based on the received event request.
  • the processor is configured to generate an Inventory Manager User Interface (IM_UI) between the user and the IM.
  • the IM_UI enables the user to modify the searched data pertaining to the one or more network functions stored at the IM on retrieval of the searched data.
  • UE User Equipment
  • the UE includes one or more primary processors communicatively coupled to one or more processors, the one or more primary processors coupled with a memory.
  • the processor causes the UE to transmit, at least one of, an event request to the one or more processors.
  • the event request pertains to accessing data pertaining to one or more network functions in the network.
  • FIG. 1 is an exemplary block diagram of an environment for management of one or more network functions in a network, according to one or more embodiments of the present invention
  • FIG. 2 is an exemplary block diagram of a system for management of the one or more network functions in the network, according to one or more embodiments of the present invention
  • FIG. 3 is a schematic representation of a workflow of the system of FIG. 1, according to the one or more embodiments of the present invention
  • FIG. 4 is an exemplary block diagram of an architecture of IM_UI interface, according to one or more embodiments of the present invention.
  • FIG. 5 is a signal flow diagram of IM_UI interface, according to one or more embodiments of the present invention.
  • FIG. 6 is a schematic representation of a method for management of the one or more network functions in the network, according to one or more embodiments of the present invention.
  • the present invention discloses a method and a system for management of one or more Network Functions (NF) in a network.
  • the present invention includes an interface which is completely based on micro service architecture.
  • the interface is configured to manage multiple container network functions (CNFs) or virtual network functions (VNFs) simultaneously in terms of network function visualization (NFV).
  • CNFs container network functions
  • VNFs virtual network functions
  • the interface is completely event driven and is based on standard application programming interface (API).
  • FIG. 1 illustrates an exemplary block diagram of an environment 100 for management of one or more network functions in a network 106, according to one or more embodiments of the present disclosure.
  • the environment 100 includes a User Equipment (UE) 102, a server 104, the network 106 and a system 108 communicably coupled to each other for management of the one or more network functions in the network 106.
  • UE User Equipment
  • the one or more network functions refer to a specific task or service within the network 106 that is responsible for handling various operations necessary for network communication and management.
  • the one or more network functions include, but are not limited to, routing, switching, firewalling, load balancing, DNS resolution, session management.
  • the managing of the one or more network functions in the network 106 include, but are not limited to, Inventory Management (IM), Network Management Systems (NMS), orchestration systems, policy-based management, event-driven workflows, analytics-driven workflows, User Interfaces (UI) and Application Programming Interfaces (APIs).
  • the environment 100 includes the server 104 accessible from the network 106.
  • the server 104 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.
  • 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 side, a defense facility side, or any other facility that provides service.
  • the system 108 includes one or more processors 202, a memory 204, and a user interface 206.
  • an Inventory Manger (IM) 218 is communicably coupled with the system 108. Further, the IM 218 includes a database 208.
  • the transceiver 210 is configured to transmit an event acknowledgment response to the user using the UE 102.
  • the event acknowledgment response is a message sent by the system 108 to the user using the UE 102 to confirm the receipt of the event request.
  • the event acknowledgement response confirms that the event request has been successfully received and is being processed.
  • the event acknowledgement response includes information about the status of the event request. The status of the event request is at least one of, received, in process, or pending.
  • the querying unit 212 queries the IM 218 by assigning a task to at least a first instance.
  • the task is assigned to the at least first instance to search for the data pertaining to the one or more network functions at the IM 218.
  • the task refers to the activity of searching and retrieving data related to one or more network functions at the IM 218 based on the received event request.
  • the instance is a specific execution thread or process dedicated to performing particular task. More specifically, the first instance is a specific execution thread or process to search for the data pertaining to the one or more network functions at the IM 218. Further, the querying unit 212 maintains one or more substitute instances.
  • the one or more substitute instances are backup processes or threads prepared to take over the task if the first instance encounters issues.
  • the issues refer to problems or disruptions that impact the successful execution of the search task or the overall process.
  • the issues are at least one of, system failures, performance degradation, data retrieval errors, query errors, memory leaks, CPU overload, connectivity issues, network latency, incorrect configurations, version incompatibility, storage failures, or service unavailability.
  • the querying unit 212 reassigns the task to the one or more substitute instances.
  • the retrieving unit 214 Upon searching the data, the retrieving unit 214 is configured to retrieve information of the searched data. More specifically, the retrieving unit 214 retrieves the information of the searched data pertaining to the one or more network functions based on the received event request.
  • the information of the searched data refers to the specific details and data that have been retrieved from the IM 218 in response to the query initiated by the querying unit 212.
  • the searched data includes, but is not limited to, configuration data, status data, performance data.
  • the sender can initiate a request and continue with other tasks without waiting for an immediate response, and the receiver can process the request and respond when it is ready.
  • the communication between the user and the IM 218 from the IM_UI does not require both the user and the IM 218 to be active or wait for the response simultaneously, instead the data exchanges occur independently.
  • the IM_UI includes, but not limited to, user interaction, customization, data display, real-time updates, and editing functions. Further the IM_UI enables the user to modify the searched data pertaining to the one or more network functions stored at the IM 218.
  • the modifying of the searched data includes operations. The operations is at least one of, create, update, fetch, and delete the searched data.
  • the IM_UI is generated to allow the user to interact with and modify the data that has been searched by the querying unit 212 and retrieved by the retrieving unit 214 from the IM 218. More specifically, the IM_UI is tailored to present the specific data related to the network functions that the user has requested. The IM_UI is designed to facilitate the specific actions the user needs to perform, such as creating, updating, fetching, or deleting the searched data. The IM_UI is likely generated with controls and options that align with the operations such as creating, updating, fetching, or deleting the searched data.
  • the one or more flavors pertaining to the set of attributes of the one or more network functions is generated based on the user customizing one or more parameters in one or more categories from the UE 102.
  • the one or more parameters refer to the specific adjustable settings or values that define the characteristics and performance of the one or more network functions.
  • the one or more parameters include at least one of, CPU, RAM, storage capacity, and network bandwidth.
  • the one or more flavors are the customized configurations generated by the system 108 when the user modifies the one or more parameters like CPU and RAM. For example, the user generates a flavor that allocates 4 CPU cores and 8 GB of RAM to the network function for high performance tasks. The flavor might generate just 1 CPU core and 2GB of RAM for basic tasks.
  • the one or more categories refer to the broader groups or classifications that encompass related one or more parameters.
  • the one or more categories represent different aspects of the network function's configuration, where each category includes specific parameters that can be adjusted by the user.
  • the one or more categories include at least one of, processing power, memory, storage, and networking. More specifically, the one or more flavors are generated based on the user modifying one or more parameters in one or more categories refers that the users are allowed to adjust settings within various groups of related parameters.
  • the related parameters are the specific, adjustable settings within the category that directly influence how an attribute of the one or more network functions operate. For example, the user might decide to increase the RAM in the Memory category while also increasing the CPU cores in the Processing Power category.
  • the system 108 By managing the one or more network functions in the network 106, the system 108 enhance the efficiency, reliability, and ease of managing network infrastructure using both Cloud-Native Network Functions (CNFs) and Virtual Network Functions (VNFs).
  • CNFs Cloud-Native Network Functions
  • VNFs Virtual Network Functions
  • the system 108 reduces the complexity of managing NFs, thereby minimizing the chances of human error and increasing operational efficiency. Further, the system 108 improves the reliability of the network 106 by reducing downtime.
  • FIG. 3 describes a preferred embodiment of the system 108 of FIG. 2, according to various embodiments of the present invention. It is to be noted that the embodiment with respect to FIG. 3 will be explained with respect to the first UE 102a and the system 108 for the purpose of description and illustration and should nowhere be construed as limited to the scope of the present disclosure.
  • each of the first UE 102a, the second UE 102b, and the third UE 102c may include an external storage device, a bus, a main memory, a read-only memory, a mass storage device, communication port(s), and a processor.
  • the exemplary embodiment as illustrated in FIG. 3 will be explained with respect to the first UE 102a without deviating from the scope of the present disclosure and the limiting the scope of the present disclosure.
  • the first UE 102a includes one or more primary processors 302 communicably coupled to the one or more processors 202 of the system 108.
  • the one or more primary processors 302 are coupled with a memory 304 storing instructions which are executed by the one or more primary processors 302. Execution of the stored instructions by the one or more primary processors 302 enables the first UE 102a to transmit the at least one of the event requests to the one or more processors 202.
  • the event request pertains to accessing data pertaining to one or more network functions in the network 106.
  • the one or more processors 202 of the system 108 is configured to manage the one or more network functions in the network 106.
  • the system 108 includes the one or more processors 202, the memory 204, and the user interface 206.
  • an Inventory Manger (IM) 218 is communicably coupled with the system 108.
  • the IM 218 includes a database 208.
  • the operations and functions of the one or more processors 202, the memory 204, the user interface 206, and the database 208 are already explained in FIG. 2. For the sake of brevity, a similar description related to the working and operation of the system 108 as illustrated in FIG. 2 has been omitted to avoid repetition.
  • the processor 202 includes the transceiver 210, the querying unit 212, the retrieving unit 214, and the generating unit 216.
  • the operations and functions of the transceiver 210, the querying unit 212, the retrieving unit 214, and the generating unit 216 are already explained in FIG. 2.
  • a similar description related to the working and operation of the system 108 as illustrated in FIG. 2 has been omitted to avoid repetition.
  • FIG. 4 is an exemplary block diagram of an architecture 400 of the IM-UI interface, according to one or more embodiments of the present invention.
  • the architecture 400 includes the User Interface (UI) 206, a Physical and virtual Inventory Manager (PVIM) 402, and the database 208.
  • UI User Interface
  • PVIM Physical and virtual Inventory Manager
  • the event request from the user is received from the UI 206.
  • the event request pertains to accessing data pertaining to one or more network functions in the network 106.
  • the event request is received from at least one of, a Hypertext Transfer Protocol (HTTP).
  • HTTP Hypertext Transfer Protocol
  • the event acknowledgement response is transmitted to the user using the UI 206.
  • the event request is transmitted to the PVIM 402.
  • the PVIM 402 is the inventory manager responsible for handling queries related to the one or more network functions, managing data retrieval, and storing data in the database 208.
  • the PVIM 402 searches the data pertaining to the one or more network functions based on the received event request. Upon searching the data pertaining to the one or more network functions, the PVIM 402 retrieves the information of the searched data from the database 208.
  • the UI 206 enables the user to modify the searched data pertaining to the one or more network functions present at the PVIM 402.
  • the modifying the searched data includes operations of at least one of, create, update, fetch and delete the searched data.
  • the searched data includes information related to sites, pods, hosts, VNFs (Virtual Network Functions), and VNFCs (Virtual Network Function Components).
  • the UI 206 facilitates provisioning, updating, or deletion of network resources such as hosts and pods.
  • the UI 206 is an async based interface for the communication between the user and the PVIM 402.
  • one or more flavors pertaining to attributes of the one or more network functions are generated based on the user customizing one or more parameters in one or more categories from the UI 206.
  • FIG. 5 is a flow diagram 500 of the IM_UI interface, according to one or more embodiments of the present invention.
  • the flow diagram 500 includes the UI 206, the PVIM 402, the database 208 and the business logic 502.
  • the event request is received from the user using the UI 206.
  • the event request pertains to accessing data pertaining to the one or more network functions in the network 106.
  • the event request is received via at least one of, a Hypertext Transfer Protocol (HTTP).
  • HTTP Hypertext Transfer Protocol
  • the event acknowledgement response is transmitted to the user using the UI 206.
  • the PVIM 402 searches for the data pertaining to the one or more network functions based on the received event request.
  • the PVIM 402 searches for the data by assigning the task to at least one instance to search for the data.
  • the PVIM 402 maintains the one or more substitute instances. Thereafter the PVIM 402 re-assigns the tasks to the one or more substitute instances when the first instance fails to perform the task.
  • the PVIM 402 retrieves the information of the searched data from the database 208.
  • the business logic 502 component implements the functional operations associated with the event requests.
  • the business logic 502 processes requests sent to the PVIM 402, ensuring that appropriate actions (such as querying, updating, or deleting data) are performed.
  • the business logic 502 acts as the intermediary that processes event requests, interfaces with the PVIM 402 handles data retrieval and modification and ensures that the UI 206 provides the user with the necessary functionality to manage network functions.
  • the business logic 502 is central to the operation of the system, making sure that all components work together seamlessly.
  • the UI 206 enables the user to modify the searched data pertaining to the one or more network functions at the PVIM 402.
  • the modifying the searched data includes operations of at least one of create, update, fetch and delete the searched data.
  • the searched data includes information related to sites, pods, hosts, VNFs (Virtual Network Functions), and VNFCs (Virtual Network Function Components).
  • the VNF is a software implementation of a network function that can run on a virtualized infrastructure (such as virtual machines or containers) instead of being tied to specific hardware.
  • the VNFs can perform various networking tasks like firewalls, load balancers, routers, and more.
  • the VNFC is a smaller, modular component that makes up part of the VNF.
  • the VNFC is typically a software module or a microservice that handles a specific function within the VNF. Multiple VNFCs can be combined to form a complete VNF, allowing for greater flexibility and scalability.
  • the UI 206 facilitates provisioning, updating, or deletion of network resources such as hosts and pods.
  • the UI 206 is an async based interface for the communication between the user and the PVIM 402.
  • one or more flavors pertaining to attributes of the one or more network functions are generated based on the user customizing one or more parameters in one or more categories from the UI 206.
  • FIG. 6 is a flow diagram of method 600 for management of the one or more network functions in the network 106, according to one or more embodiments of the present invention.
  • the method 600 is described with the embodiments as illustrated in FIG. 2 and should nowhere be construed as limiting the scope of the present disclosure.
  • the method 600 includes the step of receiving an event request from a user using the UE 102 by the transceiver 210.
  • the event request pertains to accessing data pertaining to one or more network functions in the network 106.
  • the event acknowledgement response is transmitted to the user using the UE 102.
  • the event request is received from at least one of, a Hypertext Transfer Protocol (HTTP).
  • HTTP Hypertext Transfer Protocol
  • the method 600 includes the step of querying the IM 218 to search for the data pertaining to the one or more network functions based on the received event request by the querying unit 212.
  • the querying unit 212 queries the IM 218 to search for the data pertaining to the one or more network functions by assigning the task to at least the first instance to search for the data pertaining to the one or more network functions at the IM 218. Thereafter, the querying unit 212 maintains the one or more substitute instances and reassigns the task to the one or more substitute instances when the first instance fails to perform the task.
  • the IM 218 includes a database to store the data related to the one or more network functions.
  • the method 600 includes the step of retrieving the information of the searched data pertaining to the one or mor network functions based on the received event request by the retrieving unit 214.
  • the method 600 includes the step of generating, the IM_UI between the user and the IM 218 by the generating unit 216.
  • the IM_UI enables the user to modify the searched data pertaining to the one or more network functions stored at the IM 218 on retrieval of the searched data.
  • the IM_UI is an async based interface for communication between the user and the IM 218.
  • the modifying of the searched data includes operations of at least one of, create, update, fetch and delete the searched data.
  • generating the one or more flavors pertaining to attributes of the one or more network functions based on the user customizing one or more parameters in one or more categories from the UE 102.
  • the one or more parameters include at least one of, Central Processing Unit (CPU) and Random Access Memory (RAM)
  • 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 202.
  • the processor 202 is configured to receive an event request from the user using the UE 102.
  • the event request pertains to accessing data pertaining to one or more network functions in the network 106.
  • the processor 202 is further configured to query the IM 218 to search for the data pertaining to the one or more network functions based on the received event request.
  • the processor 202 is further configured to retrieve the information of the searched data pertaining to the one or more network functions based on the received event request.
  • the processor 202 is further configured to generate the IM_UI between the user and the IM 218.
  • the IM_UI enabling the user to modify the searched data pertaining to the one or more network functions stored at the IM 218.
  • FIG.1-6 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.
  • the present disclosure incorporates technical advancement of enhancing the efficiency, reliability, and ease of managing network infrastructure using both Cloud- Native Network Functions (CNFs) and Virtual Network Functions (VNFs).
  • CNFs Cloud- Native Network Functions
  • VNFs Virtual Network Functions
  • the present invention reduces the complexity of managing NFs, thereby minimizing the chances of human error and increasing operational efficiency. Further, the present invention improves the reliability of the network by reducing downtime.
  • the present invention can deliver faster responses to configuration changes and reduce the overall operational cost, making it more scalable and sustainable.
  • the present invention enhances accuracy and improves the overall consistency of the network environment.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer And Data Communications (AREA)

Abstract

La présente divulgation concerne un système (108) et un procédé (600) de gestion d'une ou de plusieurs fonctions de réseau dans un réseau (106). Le système (108) comprend un émetteur-récepteur (210) pour recevoir une demande d'événement provenant d'un utilisateur à l'aide d'un équipement utilisateur (UE) (102). Le système (108) comprend une unité d'interrogation (212) pour interroger un gestionnaire d'inventaire (IM) (218) en vue de rechercher les données concernant la ou les fonctions de réseau. Le système (108) comprend une unité de récupération (214) pour récupérer des informations des données recherchées concernant la ou les fonctions de réseau sur la base de la demande d'événement reçue. Le système (108) comprend une unité de génération (216) pour générer une interface utilisateur de gestionnaire d'inventaire (IM_UI) entre l'utilisateur et l'IM (218). L'IM_UI permet à l'utilisateur de modifier les données recherchées concernant la ou les fonctions de réseau stockées au niveau de l'IM (218).
PCT/IN2024/051647 2023-09-06 2024-09-05 Procédé et système de gestion d'une ou de plusieurs fonctions de réseau dans un réseau Pending WO2025052451A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
IN202321060025 2023-09-06
IN202321060025 2023-09-06

Publications (1)

Publication Number Publication Date
WO2025052451A1 true WO2025052451A1 (fr) 2025-03-13

Family

ID=94923015

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IN2024/051647 Pending WO2025052451A1 (fr) 2023-09-06 2024-09-05 Procédé et système de gestion d'une ou de plusieurs fonctions de réseau dans un réseau

Country Status (1)

Country Link
WO (1) WO2025052451A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017080499A1 (fr) * 2015-11-11 2017-05-18 中兴通讯股份有限公司 Procédé et dispositif de gestion pour gérer une transmission d'instruction et une fonction de mise à l'échelle de fonction de réseau virtualisé (vnf) automatique
EP3178199B1 (fr) * 2014-08-07 2019-03-20 Intel IP Corporation Gestion de fonction de réseau virtualisé
US10904106B2 (en) * 2017-06-09 2021-01-26 International Business Machines Corporation Mechanism for fault diagnosis and recovery of network service chains
US20230075951A1 (en) * 2020-02-07 2023-03-09 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for registration data retrieval

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3178199B1 (fr) * 2014-08-07 2019-03-20 Intel IP Corporation Gestion de fonction de réseau virtualisé
WO2017080499A1 (fr) * 2015-11-11 2017-05-18 中兴通讯股份有限公司 Procédé et dispositif de gestion pour gérer une transmission d'instruction et une fonction de mise à l'échelle de fonction de réseau virtualisé (vnf) automatique
US10904106B2 (en) * 2017-06-09 2021-01-26 International Business Machines Corporation Mechanism for fault diagnosis and recovery of network service chains
US20230075951A1 (en) * 2020-02-07 2023-03-09 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for registration data retrieval

Similar Documents

Publication Publication Date Title
US11089117B2 (en) Discovery of remote storage services and associated applications
US11089115B2 (en) Discovery of cloud-based infrastructure and resources
US10931774B2 (en) Discovery and service mapping of application programming interface proxies
US10749943B1 (en) Discovery and mapping of cloud-based resources
AU2019201345B2 (en) System for building and modeling web pages
US11188385B2 (en) Batching asynchronous web requests
US10970107B2 (en) Discovery of hyper-converged infrastructure
US10719503B1 (en) Interface for supporting integration with cloud-based service providers
US11611489B2 (en) Functional discovery and mapping of serverless resources
US9971823B2 (en) Dynamic replica failure detection and healing
US11277369B1 (en) Message queue architecture and interface for a multi-application platform
US10924344B2 (en) Discovery and mapping of cloud-based resource modifications
US10776732B2 (en) Dynamic multi-factor ranking for task prioritization
US11263201B2 (en) Interface for supporting integration with cloud-based service providers
US11240304B2 (en) Selective server-side execution of client-side scripts
AU2019204978B2 (en) External data management in a remote network management platform
US10715608B2 (en) Automatic server cluster discovery
US11064046B2 (en) Distributed queueing in a remote network management architecture
WO2025052451A1 (fr) Procédé et système de gestion d'une ou de plusieurs fonctions de réseau dans un réseau
WO2025052464A1 (fr) Procédé et système d'intégration d'un réseau à une fonction de réseau en cours d'exécution
WO2025017654A1 (fr) Procédé et système de configuration d'un ou de plusieurs attributs de nœuds dans un réseau
WO2025017662A1 (fr) Procédé et système de gestion de défaillance dans réseau
WO2025013079A1 (fr) Système et procédé de gestion de fonctionnement du réseau
WO2025062435A1 (fr) Procédé et système de gestion d'une opération de fonction de réseau de conteneurs (cnf)
WO2017094194A1 (fr) Système informatique et procédé de gestion de dispositif

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24862297

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2024862297

Country of ref document: EP