[go: up one dir, main page]

WO2025052464A1 - Procédé et système d'intégration d'un réseau à une fonction de réseau en cours d'exécution - Google Patents

Procédé et système d'intégration d'un réseau à une fonction de réseau en cours d'exécution Download PDF

Info

Publication number
WO2025052464A1
WO2025052464A1 PCT/IN2024/051661 IN2024051661W WO2025052464A1 WO 2025052464 A1 WO2025052464 A1 WO 2025052464A1 IN 2024051661 W IN2024051661 W IN 2024051661W WO 2025052464 A1 WO2025052464 A1 WO 2025052464A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
running
network function
list
integrating
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/051661
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 WO2025052464A1 publication Critical patent/WO2025052464A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

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
    • H04L41/0856—Retrieval of network configuration; Tracking network configuration history by actively collecting configuration information or by backing up configuration information by backing up or archiving 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/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
    • 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/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
    • 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 the field of network designing, more particularly relates to a method and a system for integrating a network to a running network function.
  • the server has to cater to multiple requests at a time, receiving the request, processing the requests, connecting with other servers and sending the results to the user end. All of these processes go on within specified time frame and over the network thread which may lead to heavy traffic on the network. Heavy traffic ultimately hampers work efficiency of a network and various network components such as server. To alleviate network congestion and traffic, there may be need of adding new networks to already existing ones.
  • the routers or container has to be shut down and restarted after adding the new network to function without any error.
  • CNF Container Network Function
  • VNF Virtual Network Function
  • the Container Network Function Components (CNFC) or container has to stop and redesign the container to instantiate the CNFC or NFs container with updated network.
  • shutting down the running router or CNFC would come with possible downtime when no service can be accessed and to restart the CNFC manual intervention is required. This impacts the quality of service provided.
  • One or more embodiments of the present disclosure provide a method and system for integrating a network to a running network function.
  • the system for adding the network to the running network function includes a retrieval unit configured to retrieve a list of available networks from an Inventory Manager (IM) in response to receiving a first request from a user.
  • the system further includes a transceiver configured to transmit the retrieved list of available networks to the user for selecting at least one suitable network from the list of available networks.
  • the system further includes an adapting unit configured to receive, from the user, a second request for integrating the selected at least one suitable network with the running network function.
  • the adapting unit is configured to integrate, the selected at least one suitable network with the running network function in response to receiving the second request from the user for selected network with the running network function and update the list of available networks at the IM subsequent to integrating the selected at least one suitable network with the running network function.
  • the adapting unit integrates, the selected at least one suitable network with the running network function further by creating, a platform to integrate the selected at least one suitable network with the running network function and reconfiguring, at least one node corresponding to the running network function.
  • the adapting unit is further configured to transmit a confirmation to the user upon successful integration of the selected at least one suitable network with the running network function.
  • the method for adding the network to the running network function includes the step of receiving a plurality of dashboards from a user equipment.
  • the method further includes the step of retrieving a list of available networks from an Inventory Manager (IM) in response to receiving a first request from a user.
  • the method further includes the step of transmitting the retrieved list of available networks to the user for selecting at least one suitable network from the list of available networks.
  • the method further includes the step of receiving, by the one or more processors, from the user, a second request for integrating the selected at least one suitable network with the running network function.
  • the method further includes the step of integrating the selected at least one suitable network with the running network function.
  • the method further includes the step of updating the list of available networks at the IM subsequent to integrating the selected at least one suitable network with the running network function.
  • 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 retrieve a list of available networks from an Inventory Manager (IM) in response to receiving a first request from a user.
  • the processor is configured to transmit the retrieved list of available networks to the user for selecting at least one suitable network from the list of available networks.
  • the processor is configured to receive from the user a second request for integrating the selected at least one suitable network with the running network function.
  • the processor is configured to integrate the selected at least one suitable network with the running network function in response to integrating a selected network with the running network function.
  • the processor is configured to update the list of available networks at the IM subsequent to integrating the selected at least one suitable network with the running network function.
  • 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 a first request to access a list of available networks at the PVIM.
  • the processor further causes the UE to transmit a second request for integrating the selected at least one suitable network with the running network function upon selection of at least one suitable network from the list of available networks received at the User Interface (UI).
  • UI User Interface
  • the processor further causes the UE to receive confirmation of the successful integration of the selected at least one suitable network with the running network function.
  • FIG. 1 is an exemplary block diagram of an environment for integrating a network to a running network function, according to one or more embodiments of the present invention
  • FIG. 2 is an exemplary block diagram of a system for integrating the network to the running network function, 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 implemented in the system of the FIG. 2, according to one or more embodiments of the present invention
  • FIG. 5 is a signal flow diagram for adding the network to the running CNFC, according to one or more embodiments of the present invention.
  • FIG. 6 is a schematic representation of a method for integrating the network to the running network function, according to one or more embodiments of the present invention.
  • the present invention relates to a system and method for integrating a network to a running network function.
  • the system and the method disclosed in the present invention is configured to optimally infuse the network to the running network function without any need to restart the system.
  • the present invention implements a docket swarm adapter (DSA) along with management infrastructure interface to perform basic integration of a network without any disturbance to existing workflow and smooth transition of traffic.
  • DSA docket swarm adapter
  • FIG. 1 illustrates an exemplary block diagram of an environment 100 for integrating a network 106 to a running network function, 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 integrating the network 106 to the running network function.
  • UE User Equipment
  • the network function hereinafter referred to as Container Network
  • CNFC Function Components
  • the CNFC 404 refers to a network function that has been containerized for deployment in a cloud-native environment.
  • the network functions are specific functions performed within the network 106, such as routing, firewalling, load balancing etc.
  • the containerized refers to the process of encapsulating an application and its dependencies into a container.
  • a container is a lightweight, standalone, and executable software package that includes everything needed to run a piece of software, such as the code, runtime, system tools, libraries, and settings.
  • the cloudnative environment refers to an infrastructure and set of practices designed to fully leverage cloud computing models for building, deploying, and operating applications.
  • the running CNFC 404 refers to the network function that is actively operating within the containerized environment.
  • the CNFC 404 is considered as running when it is actively executing the assigned task within the containerized environment.
  • the Network Functions Virtualization adds new capabilities to communications networks and requires a new set of management and orchestration functions to be added to the current model of operations, administration, maintenance and provisioning.
  • the NFV Management and Orchestration (NFV-MANO) architectural framework has the role to manage the infrastructure and orchestrate the resources needed by the Network Services (NSs) and Virtualized Network Functions (VNFs).
  • NSs Network Services
  • VNFs Virtualized Network Functions
  • the NFV-MANO architecture shall provide support to permit service providers to partially or fully virtualize the Network Functions (NFs) needed to create, deploy and operate the services they provide.
  • the NFV-MANO architecture shall be able to support an NS composed of Physical Network Functions (PNFs) and VNFs implemented across multivendor environments.
  • the NFV-MANO architecture shall be able to manage NFV Infrastructure (NFVI) resources, in order to provide NSs and related VNFs and PNFs with the resources needed.
  • NFVI NFV Infrastructure
  • the management of resources for PNFs shall be restricted to provisioning connectivity, e.g. necessary when an NS instance includes a PNF that needs to connect to a VNF.
  • the UE 102 includes, but not limited to, a first UE 102a, a second UE 102b, and a third UE 102c, and should nowhere be construed as limiting the scope of the present disclosure.
  • the UE 102 may include a plurality of UEs as per the requirement.
  • each of the first UE 102a, the second UE 102b, and the third UE 102c, will hereinafter be collectively and individually referred to as the “User Equipment (UE) 102”.
  • UE User Equipment
  • the UE 102 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 a smartphone, 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.
  • a smartphone virtual reality (VR) devices
  • AR augmented reality
  • laptop a general-purpose computer
  • desktop personal digital assistant
  • tablet computer tablet computer
  • mainframe computer or any other computing device.
  • the environment 100 includes the server 104 accessible via 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 network 106 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.
  • PSTN Public-Switched Telephone Network
  • the network 106 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.
  • 3G Third Generation
  • 4G Fourth Generation
  • 5G Fifth Generation
  • 6G Sixth Generation
  • NR New Radio
  • NB-IoT Narrow Band Internet of Things
  • O-RAN Open Radio Access Network
  • the network 106 may also include, by way of example but not limitation, at least a portion of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or a combination thereof, etc. one or more messages, packets, signals, waves, voltage or current levels, some combination thereof, or so forth.
  • the network 106 may also include, 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, a V OIP or some combination thereof.
  • PSTN Public- Switched Telephone Network
  • the environment 100 further includes the system 108 communicably coupled to the server 104 and the UE 102 via the network 106.
  • the system 108 is configured to integrate the network 106 to the running CNFC 404.
  • the system 108 is adapted to be embedded within the server 104 or embedded as an individual entity.
  • FIG. 2 is an exemplary block diagram of the system 108 for integrating the network 106 to the running CNFC 404 (as shown in FIG. 4), according to one or more embodiments of the present invention.
  • the system 108 includes one or more processors 202, a memory 204, a user interface 206, and a database 208.
  • processors 202 for the purpose of description and explanation, the description will be explained with respect to one processor 202 and should nowhere be construed as limiting the scope of the present disclosure.
  • the system 108 may include more than one processor 202 as per the requirement of the network 106.
  • the one or more processors 202 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.
  • the processor 202 is configured to fetch and execute computer-readable instructions stored in the memory 204.
  • the memory 204 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 204 may include any non-transitory storage device including, for example, volatile memory such as RAM, or non-volatile memory such as disk memory, EPROMs, FLASH memory, unalterable memory, and the like.
  • the user interface 206 includes a variety of interfaces, for example, interfaces for a graphical user interface, a web user interface, a Command Line Interface (CLI), and the like.
  • the user interface 206 facilitates communication of the system 108.
  • the user interface 206 provides a communication pathway for one or more components of the system 108. Examples of such components include, but are not limited to, the UE 102 and the database 208.
  • the database 208 is one of, but not limited to, a centralized database, a cloudbased 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.
  • NoStructured Query Language NoSQL
  • object-oriented database a personal database
  • an in-memory database a document-based database
  • a time series database a time series database
  • a wide column database a key value database
  • search database a cache databases
  • the processor 202 includes one or more modules.
  • the one or more modules includes, but not limited to, a retrieval unit 210, a transceiver 212, and an adapting unit 214 communicably coupled to each other for integrating the network 106 to the running CNFC 404.
  • the one or more modules includes, but not limited to, the retrieval unit 210, the transceiver 212, and the adapting unit 214 can be used in combination or interchangeably for integrating the network 106 to the running CNFC 404.
  • the retrieval unit 210, the transceiver 212, and the adapting unit 214 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 202.
  • the programming for the processor 202 may be processor-executable instructions stored on a non-transitory machine -readable storage medium and the hardware for the processor may comprise a processing resource (for example, one or more processors), to execute such instructions.
  • the memory 204 may store instructions that, when executed by the processing resource, implement the processor.
  • the system 108 may comprise the memory 204 storing the instructions and the processing resource to execute the instructions, or the memory 204 may be separate but accessible to the system 108 and the processing resource.
  • the processor 202 may be implemented by electronic circuitry.
  • a first request is received from the user via the User Interface (UI) 206 for integrating the network 106 to the running CNFC 404.
  • the first request is received from the UE 102.
  • the request refers to a structured communication or message sent by the user, asking for a specific action to be performed or for specific information to be provided.
  • the first request refers to the initial interaction initiated by the user.
  • the specific action includes, but is not limited to, retrieving information, initiating a process, executing operation, displaying, integration.
  • the retrieval unit 210 is configured to retrieve a list of available networks 106 from an Inventory Manager (IM).
  • IM Inventory Manager
  • the IM hereinafter referred to as a Physical and Virtual Inventory Manager (PVIM) 402 (as shown in FIG. 4).
  • the PVIM 402 is a component responsible for maintaining and managing the inventory of both physical and virtual network resources.
  • the physical and virtual network resources refer to tangible and intangible components that make up a network infrastructure, providing connectivity and communication capabilities.
  • the physical network resources include, but are not limited to, routers and switches, cables and fiber optics, servers, base stations, data centers.
  • the virtual network resources include, but are not limited to, virtual machines, virtual network functions, cloud-based services, network slices.
  • the PVIM 402 keeps track of the available networks 106, including their status, capabilities, and other relevant attributes.
  • the list of available networks 106 from the PVIM 402 includes detailed information about each network 106, such as network type, availability, capacity, geographical location, and other relevant attributes.
  • the network 106 is categorized as available network 106when a network resource is accessible and capable of being integrated with the running CNFC 404.
  • the list refers to the collection of available networks 106 retrieved from the PVIM 402. [0044]
  • the transceiver 212 is configured to transmit the retrieved list of available networks 106 to the user.
  • the retrieved list of available networks 106 is transmitted to the user for selecting at least one suitable network 106 from the list of available networks 106.
  • the user is allowed to select at least one suitable network 106from the list of available networks 106 via at least one of the UI 206 and the UE 102.
  • the suitable network 106 refers to the network 106 from the list of available networks 106 retrieved from the PVIM 402 that meets the user’s criteria and requirements for integration with the running CNFC 404.
  • the network 106 is categorized as suitable network 106 when the network meets the user’s criteria and requirements for integration with the running CNFC 404.
  • the criteria and requirements for selecting the suitable network 106 include, but are not limited to, network type, bandwidth, latency, geographical location, availability, security features, cost.
  • the adapting unit 214 Upon selecting the suitable network 106 from the list of available networks 106, the adapting unit 214 is configured to receive a second request from the user via the UI 206.
  • the second request from user is received via the UE 102.
  • the second request is received from the user for integrating the selected at least one suitable network 106 with the running CNFC 404.
  • the second request refers to the follow-up communication initiated by the user after selecting a suitable network 106 from the list of available networks 106.
  • the second request includes, but is not limited to, user identification, selected network details, CNFC 404 identification, integration parameters (if any).
  • the user identification includes the information to authenticate the user making the request.
  • the selected network details include the specific information about the chosen network 106 such as its identifier, attributes and any configuration parameters required for integration.
  • the CNFC 404 identification includes the details about the running CNFC 404 that will be integrated with the selected network 106.
  • the integration parameters include any additional setting or preferences for how the integration should be performed. [0046]
  • the selected at least one suitable network 106 is integrated with the running CNFC 404.
  • the adapting unit 214 integrates the selected at least one suitable network 106 with the running CNFC 404 by creating a platform to integrate the selected at least one suitable network 106 with the running CNFC 404.
  • the platform refers to a foundational environment and infrastructure provided by the adapting unit 214 to facilitate the integration of the selected network 106 with the running CNFC 404.
  • the steps to create the platform by the adapting unit 214 include, but not limited to, docker swarm initialization, cluster configuration, allocating resources, dynamic scaling, creating network bridges, automation scripts, configuration files, implementing firewall rules, enabling encryption, deploying containers, service orchestration, setup monitoring tools, centralize logging.
  • the docker swarm initialization involves setting up manager and worker nodes that will host the containers and ensure that the docker swarm cluster is initialized and operational.
  • the cluster configuration configures the docker swarm cluster to ensure that the docker swarm cluster is ready to support the integration.
  • the cluster configuration includes network settings, resource allocation and security policies.
  • the allocating resources includes assigning necessary Central Processing Unit (CPU), memory, and storage resources to support the CNFC 404 and the selected network.
  • the dynamic scaling enables the dynamic scaling capabilities to adjust resource allocation based on real-time demands.
  • the creation of network bridges establishes virtual network bridges to connect the CNFC 404 with selected at least one suitable network 106.
  • the service orchestration refers to orchestrating the deployment of services to ensure that the services are properly started, monitored and maintained.
  • the setting up monitoring tools refers to implementing monitoring tools to track the performance and health of the CNFC 404 and the selected at least one suitable network 106.
  • the centralized logging uses logging tools to collect, analyze and visualize logs from the CNFC 404 and network integration.
  • the adapting unit 214 reconfigures at least one node corresponding to the running CNFC 404.
  • the reconfiguration of the at least one node corresponding to the running CNFC 404 refers to the process of modifying the configuration of one or more modes in the docker swarm or similar orchestration environment to ensure that the integration of the selected network with the running CNFC 404 is successful and optimal.
  • the reconfiguration of the at least one node includes, but not limited to, resource allocation, network configuration, security settings, software and services, storage configuration.
  • the resource allocation refers to adjusting CPU and memory limits by allocating additional CPU and memory resources to the CNFC 404 to handle the increased load or new functionalities provided by the selected network 106.
  • the network configuration includes updating network interfaces and adjusting routing tables.
  • the updating network interfaces refers to configuring the node’s network interfaces to connect with the selected network.
  • the data flow between the CNFC 404 and the selected network 106.
  • the security settings include implementing firewall rules and enabling encryption.
  • the implementing firewall rules refers to adding or updating firewall rules to allow or restrict traffic between the CNFC 404 and the selected network 106.
  • the enabling encryption refers to configuring encryption setting to secure data communication between the CNFC 404 and the selected network 106.
  • the software and services include updating software packages and restarting services.
  • the updating software packages refers to installing or updating software packages required for the CNFC 404 to communicate with the selected network 106.
  • the restarting services refers to restarting or reconfiguring services running on the node to apply the new settings.
  • the storage configuration includes allocating storage and configuring volumes.
  • the allocating storage refers to providing additional storage if the CNFC 404 requires more disk space for logs, data or configuration files related to the selected network 106.
  • the configuring volumes refers to the setting up or modifying storage volumes to ensure data persistence and accessibility.
  • the adapting unit 214 Upon successful integration of the selected at least one suitable network 106 with the running CNFC 404, the adapting unit 214 is further configured to transmit a confirmation to the user. Subsequently the list of available networks 106 at the PVIM 402 is updated. The list of available networks 106 at the PVIM 402 is updated by modifying the list of available networks 106 to reflect the current network configuration. More specifically, the network 106 which is integrated is removed from the list of available networks 106, if the network 106 is no longer available for further integration. Subsequently, the status of the network 106 which is integrated is updated to reflect their new role or state such as indicating that the network is part of specific running CNFC 404.
  • the system 108 integrates the suitable network 106 to the running CNFC 404 without shutting down and then restarting the CNFC 404.
  • the system 108 helps in maintaining the stability and reliability of the CNFC 404.
  • the system 108 eliminates the need of manual intervention to instantiate the added network 106.
  • 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 first request to access a list of available networks 106 at the PVIM 402 (as shown in FIG.4). Further, the one or more primary processors 302 also enables the first UE 102a to transmit the second request for integrating the selected at least one suitable network 106 with the running CNFC 404 (as shown in FIG. 4) upon selection of at least one suitable network 106 from the list of available networks 106 received at the UI 206. Further, the one or more primary processors 302 also enables the first UE 102a to receive the confirmation of the successful integration of the selected at least one suitable network 106 with the running CNFC 404.
  • the one or more processors 202 of the system 108 is configured to add the network 106 to the running CNFC 404.
  • the system 108 includes the one or more processors 202, the memory 204, the user interface 206, and the 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.
  • 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 retrieval unit 210, the transceiver 212, and the adapting unit 214.
  • the operations and functions of the retrieval unit 210, the transceiver 212, and the adapting unit 214 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.
  • the limited description provided for the system 108 in FIG. 3, should be read with the description as provided for the system 108 in the FIG. 2 above, and should not be construed as limiting the scope of the present disclosure.
  • FIG. 4 is an exemplary block diagram of an architecture 400 of the system 108 for integrating the network 106 to the running CNFC 404, according to one or more embodiments of the present invention.
  • the architecture 400 includes the User Interface (UI) 206, the Docker Swarm Adapter (DSA) 406, the Physical and Virtual Inventory Manager (PVIM) 402 and the CNFC 404.
  • the DSA 406 is a conceptual or specific implementation component designed to enable the integration of docker swarm with network functions within the network 106.
  • the DSA 406 is useful in scenarios where network functions (such as VNFs or CNFs) are deployed as containerized services.
  • the docker swarm is a container orchestration tool that allows you to manage a cluster of Docker engines. The docker swarm enables the deployment, scaling, and management of containerized applications across multiple hosts.
  • the request is received from the user via the UI 206 for integrating the network 106 to the running CNFC 404.
  • the UI 206 retrieves the list of available networks 106 from the PVIM 402.
  • the user via the UI 206 selects the at least one suitable network 106 from the list of available networks 106.
  • the UI 206 transmits the request to the DSA 406 for integrating the selected at least one suitable network 106 to the running CNFC 404.
  • the DSA 406 integrates the selected at least one suitable network 106 with the running CNFC 404. Further, the DSA 406 reconfigures the at least one node corresponding to the running CNFC 404.
  • the CNFC 404 Upon integrating with the selected at least one suitable network 106, the CNFC 404 transmits the successful integration with the selected at least one suitable network 106 to the DSA unit 406. Further, the DSA 406 transmits the successful integration of selected at least one suitable network 106 with the running CNFC 404 to the user via the UI 206. Subsequently the list of available networks 106 at the PVIM 402 is updated.
  • FIG. 5 is a signal flow diagram for integrating the network 106 to the running CNFC 404 (as shown in FIG.4), according to one or more embodiments of the present invention.
  • the request is received from the user via the UI 206 for integrating the network 106 to the running CNFC 404.
  • the UI 206 retrieves the list of available networks 106 from the PVIM 402 (as shown in FIG.4).
  • step 504 upon retrieving the list of available networks 106 from the PVIM 402, the user via the UI 206 selects the at least one suitable network 106 from the list of available networks 106.
  • step 506 upon selecting the at least one suitable network 106 from the list of available networks 106, the UI 206 transmits the second request to the DSA 406 for integrating the selected at least one suitable network 106 to running CNFC 404.
  • the DSA unit 406 integrates the selected at least one suitable network 106 with the running CNFC 404. Further, the DSA 406 reconfigures the at least one node corresponding to the running CNFC 404.
  • the CNFC 404 transmits the successful integration with the selected at least one suitable network 106 to the DSA 406.
  • the DSA 406 transmits the successful integration of selected at least one suitable network 106 with the running CNFC 404 to the user via the UI 206.
  • step 514 subsequent to integrating the selected at least one suitable network 106 with the running CNFC 404 the list of available networks 106 at the PVIM 402 is updated.
  • FIG. 6 is a flow diagram of a method 600 for integrating the network 106 to the running CNFC 404 (as shown in FIG.4), 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 retrieving the list of available networks 106 from the PVIM 402 (as shown in FIG.4) in response to receiving the first request from the user by the retrieval unit 210.
  • the method 600 includes the step of transmitting the retrieved list of available networks 106 to the user for selecting at least one suitable network 106 from the list of available networks 106 by the transceiver 212.
  • the method 600 includes the step of receiving the second request from the user for integrating the selected at least one suitable network 106 with the running CNFC 404.
  • the method 600 includes the step of integrating the selected at least one suitable network 106 with the running CNFC 404 by the adapting unit 214. Further, the integrating the selected at least one suitable network 106 with the running CNFC 404 includes the step of creating the platform to integrate the selected at least one suitable network 106 with the running CNFC 404. Thereafter, reconfiguring the at least one node corresponding to the running CNFC 404. In an embodiment upon successful integration of the selected at least one suitable network 106 with the running CNFC 404, the confirmation is transmitted to the user.
  • the method 600 includes the step of updating the list of available networks 106 at the PVIM 402, subsequent to integrating the selected at least one suitable network 106 with the running CNFC 404.
  • the processor 202 is further configured to integrate the selected at least one suitable network 106 with the running CNFC 404 in response to integrating a selected network 106 with the running CNFC 404.
  • the processor 202 is further configured to update the list of available networks 106 at the PVIM 402, subsequent to integrating the selected at least one suitable network 106 with the running CNFC 404.
  • the present disclosure incorporates technical advancement of integrating the new network to running CNFC without shutting down and then restarting the CNFC.
  • the present disclosure eliminates the need for manual intervention to instantiate the added network.
  • the present disclosure saves time and resources by eliminating the downtime. Further, the present disclosure also prevents surge in the network traffic by redirecting the pool of request to newly added network.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

La présente divulgation concerne un système (108) et un procédé (600) destinés à intégrer un réseau (106) à une fonction de réseau en cours d'exécution. Le système (108) comprenant une unité de récupération (210) destinée à récupérer une liste de réseaux disponibles (106) à partir d'un gestionnaire d'inventaire (IM) (402). Le système (108) comprend un émetteur-récepteur (212) destiné à transmettre la liste récupérée de réseaux disponibles à l'utilisateur pour sélectionner au moins un réseau approprié parmi la liste de réseaux disponibles. Le système (108) comprend une unité d'adaptation (214) destinée à recevoir, de l'utilisateur, une seconde demande d'intégration du ou des réseaux appropriés sélectionnés avec la fonction de réseau en cours d'exécution. En outre, l'unité d'adaptation (214) intègre ledit au moins un réseau approprié sélectionné avec la fonction de réseau en cours d'exécution (404) et met à jour la liste de réseaux disponibles au niveau de l'IM (402).
PCT/IN2024/051661 2023-09-06 2024-09-06 Procédé et système d'intégration d'un réseau à une fonction de réseau en cours d'exécution Pending WO2025052464A1 (fr)

Applications Claiming Priority (2)

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

Publications (1)

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

Family

ID=94923210

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IN2024/051661 Pending WO2025052464A1 (fr) 2023-09-06 2024-09-06 Procédé et système d'intégration d'un réseau à une fonction de réseau en cours d'exécution

Country Status (1)

Country Link
WO (1) WO2025052464A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170272523A1 (en) * 2016-03-21 2017-09-21 International Business Machines Corporation Replacing a virtual network function in a network service

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170272523A1 (en) * 2016-03-21 2017-09-21 International Business Machines Corporation Replacing a virtual network function in a network service

Similar Documents

Publication Publication Date Title
US11089117B2 (en) Discovery of remote storage services and associated applications
US10771344B2 (en) Discovery of hyper-converged infrastructure devices
US10915518B2 (en) Partial discovery of cloud-based resources
US10931774B2 (en) Discovery and service mapping of application programming interface proxies
US10970107B2 (en) Discovery of hyper-converged infrastructure
EP3218817B1 (fr) Configuration d'un réseau
US11520621B2 (en) Computational instance batching and automation orchestration based on resource usage and availability
US10951483B2 (en) Agent-assisted discovery of network devices and services
US10776732B2 (en) Dynamic multi-factor ranking for task prioritization
US20200328941A1 (en) Discovery and mapping of cloud-based resource modifications
US8543680B2 (en) Migrating device management between object managers
US10963314B2 (en) Discovery and mapping of a platform-as-a-service environment
US20230337062A1 (en) Cellular system observability centralized for all domains and vendors
US20230337021A1 (en) Automated public network monitoring and maintenance of cellular network system
US20230337063A1 (en) Cellular system observability architecture
US20230336433A1 (en) Data collection for cellular system
US20160043894A1 (en) Automatic reconfiguration of network parameters during file system failover
US20240265059A1 (en) Common Fragment Caching for Web Documents
US12299505B2 (en) Decentralized framework for providing application programming interface gateways
WO2025052464A1 (fr) Procédé et système d'intégration d'un réseau à une fonction de réseau en cours d'exécution
US11829749B2 (en) Incremental update for offline data access
US20190306691A1 (en) Discovery and Service Mapping of Serverless Resources
WO2025057218A1 (fr) Procédé et système de gestion de ressources d'une fonction réseau dans un réseau
US20150281378A1 (en) Method and apparatus for automating creation of user interface across multi-clouds
WO2025017669A1 (fr) Procédé et système d'imbrication de flux de travail

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: 24862310

Country of ref document: EP

Kind code of ref document: A1