A network slice deployment system and method based on NFV-MANO

Abstract

The application discloses a network slice deployment system based on NFV-MANO, comprising an infrastructure resource layer, a network slice layer, a service layer and a management and arrangement unit, the infrastructure resource layer maps physical resources into virtual resources, the virtual resources have access interfaces connected with the physical resources, the network slice layer comprises a plurality of network slices, the network slice comprises one or more service chains, the service chain comprises a plurality of VNFs connected by virtual links, each service chain is used for providing a network service, and the management and arrangement unit manages the infrastructure resource layer, the network slice layer and the service layer; and the application further discloses a network slice deployment method based on NFV-MANO. The application adds the management and arrangement unit to manage the three network layers, so that efficient management and dynamic deployment of the network slice system are realized.

Description

Technical Field

[0001] This invention belongs to the field of network virtualization technology, specifically relating to a network slicing deployment system and method based on NFV-MANO. Background Technology

[0002] Compared to 5G networks, traditional mobile communication networks primarily serve mobile terminals such as smartphones and tablets, offering relatively limited service types and covering most application scenarios. However, in 5G networks, network demands are significantly differentiated, including high-speed and high-throughput network hotspots, low-latency and high-reliability automatic control, highly mobile and high-precision positioning for autonomous driving, and massive access for the Internet of Things (IoT). The focus of network services and infrastructure deployment differs for each, and a single network service cannot meet the diverse network needs of operators.

[0003] Network slicing technology provides differentiated network services for 5G networks to meet varying performance requirements. It establishes multiple independent network slices to satisfy the diverse performance needs of vertical industries within 5G scenarios. Each network slice is designed and customized for a specific network service according to the operator's requirements. Different network slices coexist on the same physical network while remaining isolated from each other, ensuring that the network services provided by different slices do not interfere with each other. However, network slicing may encounter issues such as redundant workflow execution and excessive network resource scheduling during operation. Therefore, efficient management and dynamic deployment of the network slicing system are essential requirements. Summary of the Invention

[0004] To address the problems of the existing technical solutions mentioned above, this invention proposes a network slicing deployment system and method based on NFV-MANO. By establishing an infrastructure resource layer, a network slicing layer, and a service layer, and introducing a Management and Network Orchestration (MANO) unit for Network Functions Virtualization (NFV), the system aims to achieve efficient management and dynamic deployment of network slices.

[0005] The technical solution adopted in this invention is as follows:

[0006] A network slicing deployment system based on NFV-MANO includes an infrastructure resource layer, a network slicing layer, a service layer, and a management orchestration unit. The infrastructure resource layer maps physical resources to virtual resources, and the virtual resources have access interfaces to connect to the physical resources. The network slicing layer includes several network slices, and each network slice includes one or more service chains. Each service chain includes multiple VNFs connected by virtual links, and each service chain is used to provide a network service. The management orchestration unit manages the infrastructure resource layer, the network slicing layer, and the service layer.

[0007] Preferably, the management orchestration unit includes an orchestrator, a VNF manager, a virtual resource manager, and a slice manager. The orchestrator orchestrates network slices and network resources, the VNF manager manages VNF templates, the slice manager manages network slice templates, and the virtual resource manager records virtual resource data and allocates virtual resources.

[0008] Preferably, the orchestrator performs the following steps:

[0009] The orchestrator calculates the virtual resources required for the network slice parameters in the slice request, sends an information acquisition request to the virtual resource manager and receives the existing virtual resource information sent back by the virtual resource manager, and determines whether the existing virtual resources meet the required virtual resources. If they do, the orchestrator sends a network slice creation request to the slice manager. If they do not meet the requirements, the orchestrator puts the slice request back into the slice request queue.

[0010] The orchestrator matches a network slice template according to the network slice parameters and sends the matching result to the slice manager;

[0011] The orchestrator determines the required VNFs based on the preset network functions of the newly created network slice, matches VNF templates according to the required VNFs, and sends the matching results to the VNF manager.

[0012] Preferably, the arranger also performs the following steps:

[0013] The network slice's VNFs and their link information are combined to form a Virtual Function Forwarding Graph (VFFT). The network slice's materialization request and the VFFT VFFT VF template are then sent to the VNF template.

[0014] Preferably, the slice manager performs the following steps:

[0015] Receive the matching result sent by the orchestrator. If the matching result is successful, select the matching network slice template to create a network slice. If the matching result fails, create a new network slice.

[0016] Preferably, the VNF manager performs the following steps:

[0017] Receive the matching result sent by the orchestrator. If the matching result is successful, select the matching VNF template. If the matching result fails, create a new VNF template.

[0018] Based on the virtual function forwarding graph, obtain the VNF and the virtual resources required by the VNF in the VNF template, and send the VNF and the virtual resources required by the VNF as resource requests to the VRM.

[0019] Preferably, the virtual resource manager performs the following steps:

[0020] Configure a virtual resource list, which records the types and capacities of virtual resources and provides an external access interface;

[0021] Receive resource requests from the slice manager or VNF manager and the virtual network function forwarding graph from the orchestrator;

[0022] Provide the required virtual resources based on the resource request;

[0023] Based on the virtual network function forwarding graph, virtual links are used to connect the required virtual resources to form corresponding network services;

[0024] Remove linked virtual resources from the virtual resource list and update the virtual resource list.

[0025] Preferably, the management orchestration unit also includes a VNF directory table, which records the VNF template information to which the VNF belongs and the VNF's own attribute information. The VNF's own attributes include resource requirements, allocation principles, operator policies, and software version information.

[0026] Preferably, the system also includes an SDN controller that adjusts network resources across multiple network slices based on network slice parameters.

[0027] Preferably, the SDN controller performs the following steps:

[0028] Receive network slice parameters and corresponding network services from the service layer;

[0029] Parse network slice parameters to obtain the required virtual resources;

[0030] Obtain virtual resource information of existing network slices and network services in the network slicing layer;

[0031] Determine whether the remaining virtual resources retained after the existing virtual resources are reallocated meet the required virtual resources.

[0032] If the conditions are not met, the SDN controller completes the step of adjusting network resources in multiple network slices based on network slice parameters. If the conditions are met, virtual resources that meet the network services of the existing network slices in the network slice layer are reallocated, and the remaining virtual resources are obtained.

[0033] Create new network slices based on the virtual resources required for network service links.

[0034] Preferably, the network slicing parameters include bandwidth, latency, and QoS.

[0035] Preferably, the physical resources include spectrum, bandwidth, routing and switching equipment, storage centers, and processors, while the virtual resources include large data centers and high-speed network connections.

[0036] A network slicing deployment method based on NFV-MANO includes the following steps:

[0037] S1. The operator provides network requirements, and the service layer customizes network slicing parameters according to the network requirements and records the network slicing parameters as a slice request;

[0038] S2. The orchestrator receives a slice request service sent by the service layer, extracts network slice parameters, matches a network slice template according to the network slice parameters, and sends the matching result to the slice manager;

[0039] S3. The slice manager receives the matching result. If the matching result is successful, the slice manager selects the matching network slice template, creates a network slice, and executes step 5. If the matching result fails, the slice manager creates a new network slice.

[0040] S4. The orchestrator determines the required VNF based on the preset network function of the newly created network slice, matches the required VNF template with the VNF template, and sends the matching result to the VNF manager. If the matching result is successful, the VNF manager selects the matching VNF template. If the matching result fails, the VNF manager creates a new VNF template.

[0041] S5. The Virtual Resource Manager receives a resource request sent by the Slice Manager or VNF Manager, the resource request including the virtual resources required for the materialization of network slices, and also receives a virtual function forwarding diagram sent by the orchestrator.

[0042] S6. The Virtual Resource Manager obtains the required virtual resources based on the resource request, and uses virtual links to connect the required virtual resources according to the virtual network function forwarding graph to form related network services.

[0043] Preferably, step S1 includes the following steps: the service layer sends a slice request and the corresponding network service to the SDN controller, which adjusts network resources in multiple network slices.

[0044] Preferably, the SDN controller performs network resource adjustment across multiple network slices, including the following steps:

[0045] Receive slice requests and corresponding network services from the service layer;

[0046] Parse the network slice parameters in the slice request to obtain the required virtual resources;

[0047] Obtain virtual resource information of existing network slices and network services in the network slicing layer;

[0048] Determine whether the remaining virtual resources retained after the existing virtual resources are reallocated meet the required virtual resources.

[0049] If the conditions are not met, the SDN controller adjusts network resources in multiple network slices according to the network slice parameters, and the process ends. If the conditions are met, virtual resources that meet the network services of the existing network slices in the network slice layer are reallocated, and the remaining virtual resources are obtained.

[0050] Create new network slices based on the virtual resources required for network service links.

[0051] Preferably, step S7 is also included: when the lifecycle of a network slice ends, the virtual resource manager releases the virtual resources occupied by the network slice and updates the virtual resource list.

[0052] The beneficial effects of this invention include: establishing a basic operational flow for network request generation, network slice creation, and network resource allocation by creating an infrastructure resource layer, network slicing layer, and service layer; and adding a management orchestration unit to manage the three network layers to improve network slicing efficiency. Furthermore, the slice manager and VNF manager can be used to provide network slice templates and VNF templates, respectively, further increasing network slice deployment efficiency. Moreover, by configuring the SDN controller to receive network requests from the service layer and reschedule network resources in the network slicing layer, operators can simultaneously submit network requests and adjust resources within their own network slices to meet new network requests. This differs from existing technologies where network slices are created solely by the supplier through the management orchestration unit, improving slice creation efficiency and reducing the load on the management orchestration unit. Furthermore, the SDN controller is also connected to the VNF directory table, allowing the VNF directory table to be queried before creating a network slice based on network slice parameters to check for available VNF templates, thereby improving network slice creation efficiency. Attached Figure Description

[0053] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0054] Appendix Figure 1 This is a structural diagram of a network slicing deployment system based on NFV-MANO in this invention.

[0055] Appendix Figure 2 This is a structural diagram of the network slice layer in a network slice deployment system based on NFV-MANO according to the present invention.

[0056] Appendix Figure 3 This is a structural diagram of the infrastructure resource layer of a network slicing deployment system based on NFV-MANO in this invention.

[0057] Appendix Figure 4 This is a flowchart of a network slicing deployment method based on NFV-MANO in this invention.

[0058] Appendix Figure 5 This is a flowchart illustrating how the SDN controller adjusts network resources across multiple network slices in a network slice deployment method based on NFV-MANO according to the present invention.

[0059] Specific implementation examples

[0060] The following specific embodiments illustrate the implementation of the present invention. Those skilled in the art can easily understand other advantages and effects of the present invention from the content disclosed in this specification. The present invention can also be implemented or applied through other different specific embodiments, and various details in this specification can also be modified or changed based on different viewpoints and applications without departing from the spirit of the present invention. It should be noted that, unless otherwise specified, the following embodiments and features described therein can be combined with each other.

[0061] Reference Appendix Figure 1 The solution adopted in this embodiment includes: a network slicing deployment system based on NFV-MANO, comprising an infrastructure resource layer, a network slicing layer, a service layer, and a management orchestration unit. The infrastructure resource layer maps physical resources to virtual resources, and the virtual resources have access interfaces to connect to physical resources. The network slicing layer includes several network slices, and each network slice includes one or more service chains. Each service chain includes multiple VNFs connected by virtual links, and each service chain is used to provide a network service. The management orchestration unit manages the infrastructure resource layer, the network slicing layer, and the service layer.

[0062] The infrastructure resource layer sits at the bottom of the network slicing model, providing various infrastructure resources to meet the service needs of different network slicing operators. In the infrastructure resource layer, the resources provided to the network slicing layer are virtualized. Virtualized resources are cloud-based logical resources formed by extracting, isolating, and re-representing underlying physical resources. These include network nodes and links, such as large data centers and high-speed network connections. A virtual resource list records resource types and capacities and provides external access interfaces. This list is generated, maintained, and dynamically updated by the Virtual Resource Manager (VRM), which can remove allocated resources or add reclaimed resources for reconfiguration. When the infrastructure resource layer is accessed by other network layers, it uses the resource list to find the access interface allocated to the virtual resources to invoke the corresponding underlying physical resources. These underlying physical resources include, but are not limited to, spectrum, bandwidth, routing and switching equipment, storage centers, and processors.

[0063] The network slicing layer is the middle layer of the network slicing model. It consists of several network slices, each an independent end-to-end logical network, assigned to a slice operator to provide one or more network services. A single slice operator can own multiple network slices simultaneously and can reallocate resources among its multiple slice networks using the SDN controller connecting the infrastructure resource layer and the network slicing layer, without submitting network slice requests to vendors—that is, applying for and waiting for resource reallocation through the management orchestration unit. In the NFV architecture, a network service is equivalent to a service chain. Based on the Virtual Network Functions forwarding graph, a group of specific VNFs are connected through virtual links to form a service chain to provide a specific network service. Simultaneously, the modular network function implemented by the VNF entity, obtained after VNF materialization, consists of the VNF template and the corresponding network resources required to run that function. By allocating mutually isolated resources, each VNF template can create multiple VNF entities, but each VNF entity can only be owned and used by one service chain, thus achieving isolation between different network services. A network slice, as a complete logical network, can consist of one or more independent service chains, or it can be directly composed of slice templates and corresponding underlying resources. The VNF manager in the management orchestration unit is used for VNF management, including VNF creation, configuration, physicalization, and dynamic adjustment. Unlike the NFVO in the NFV architecture, which is responsible for the lifecycle management of network services, the system proposed in this embodiment uses a dedicated slice management unit to manage network slices and network services.

[0064] The service layer sits at the top of the network slicing model, providing various unique network services in 5G networks, such as enhanced mobile broadband, ultra-reliable low latency, and massive machine-type communications, to meet users' diverse customized network needs. The Business / Operation Support System (BOSS) serves as the intermediary between the slicing operator and the management unit. It is primarily responsible for traditional network management functions (FCAPS), namely: Fault Management, Configuration Management, Accounting Management, Performance Management, and Security Management.

[0065] The service layer is managed by the network slicing operator. The network slicing operator understands certain user needs through market research, customizes network slicing parameters that can meet these needs, including bandwidth, latency, QoS, etc., and sends the slicing parameters as a slicing request to the network slicing provider to trigger the operation of the entire network slicing system.

[0066] Furthermore, a network slicing deployment system based on NFV-MANO also includes an SDN controller. The SDN controller adjusts network resources across multiple network slices according to network slice parameters. The SDN controller performs the following steps:

[0067] Receive network slice parameters and corresponding network services from the service layer;

[0068] Parse network slice parameters to obtain the required virtual resources;

[0069] Obtain virtual resource information of existing network slices and network services in the network slicing layer;

[0070] Determine whether the remaining virtual resources retained after the existing virtual resources are reallocated meet the required virtual resources.

[0071] If the conditions are not met, the SDN controller completes the step of adjusting network resources in multiple network slices based on network slice parameters. If the conditions are met, virtual resources that meet the network services of the existing network slices in the network slice layer are reallocated, and the remaining virtual resources are obtained.

[0072] Create new network slices based on the virtual resources required for network service links.

[0073] An SDN controller added between the service layer and the network slicing layer receives network requests from the service layer and reschedules network resources in the network slicing layer. This allows operators to submit network requests and simultaneously adjust resources within their own network slices to meet new network requests, without needing to apply to the management orchestrator and wait for resource reallocation. Unlike existing technologies where network slices are established solely by the vendor through the management orchestration unit, the SDN controller improves slice creation efficiency and reduces the load on the management orchestration unit. By unifying the resource optimization methods across multiple operator slice networks, it significantly reduces signaling overhead and the computational burden on the management orchestrator. When an operator performs resource scheduling optimization between different network slices, it only needs to report to the orchestrator and slice manager, without needing to perform resource allocation operations through the virtual resource manager. When a slice network provides multiple network services simultaneously, different network service chains do not interfere with each other, and the virtual network function forwarding graph and related resources that make up the service chain are managed by the orchestrator.

[0074] Furthermore, the management orchestration unit includes an orchestrator, a VNF manager (VNFM), a Virtual Resource Manager (VRM), and a Slice Manager (NSM). The orchestrator orchestrates network slices and network resources, the VNF manager manages VNF templates, the Slice Manager manages network slice templates, and the Virtual Resource Manager records virtual resource data and allocates virtual resources.

[0075] The traditional centralized resource allocation and management model by operators is not feasible in 5G slicing networks: firstly, it is difficult to guarantee the full scheduling and utilization of limited physical resources; secondly, there are investment cost issues for operators. The management and orchestration unit is used to manage different network services and effectively allocate network resources within the network slicing system.

[0076] Furthermore, the orchestrator performs the following steps:

[0077] The orchestrator calculates the virtual resources required for the network slice parameters in the slice request, sends an information acquisition request to the virtual resource manager and receives the existing virtual resource information sent back by the virtual resource manager, and determines whether the existing virtual resources meet the required virtual resources. If they do, the orchestrator sends a network slice creation request to the slice manager. If they do not meet the requirements, the orchestrator puts the slice request back into the slice request queue.

[0078] The orchestrator matches network slice templates based on network slice parameters and sends the matching results to the slice manager;

[0079] The orchestrator determines the required VNFs based on the preset network functions of the newly created network slice, matches VNF templates to the required VNFs, and sends the matching results to the VNF manager.

[0080] Furthermore, the orchestrator performs the following steps:

[0081] The network slice's VNFs and their link information are combined to form a Virtual Function Forwarding Graph (VFFT). The network slice's materialization request and the VFFT VFFT VF template are then sent to the VNF template.

[0082] The orchestrator is primarily responsible for orchestrating network slices and network resources. This includes network slice and VNF template configuration management, verifying VNF template integrity and authorization authentication; VNFM and SM entity management; verifying and authorizing resource requests from VNFM and SM; managing the virtual network function forwarding list that makes up network services, including creation, upgrades, queries, and deletion; automated management of network slices and VNF entities, configuring templates according to trigger rules and operation procedures; resource allocation management of network slices and VNF entities, providing location information of available resources to SM and VNFM by locating different VRMs; collecting resource usage information; and managing the list of available resources.

[0083] When an operator sends a new slice request to the orchestrator, the orchestrator first queries existing slice templates and available network resources. If a suitable template is found, it sends it to the slice manager to create the network slice required by the operator. If no suitable template is found, the orchestrator configures a new slice template based on the slice parameters and service type provided by the operator, completing the customization. When an operator needs to add a new network service to a network slice, the orchestrator searches for or creates relevant VNF ​​templates based on the VNFs required to implement the network service function, generates a Virtual Network Function Forwarding List, and completes the network service request. The establishment of network slice templates and VNF templates further improves slice creation efficiency, eliminating the need to create new templates for function implementation when existing templates exist, thus saving slice creation time.

[0084] Furthermore, the slice manager performs the following steps:

[0085] Receive the matching result sent by the orchestrator. If the matching result is successful, select the matching network slice template to create a network slice. If the matching result fails, create a new network slice.

[0086] The slice manager is responsible for network slice management. This includes: creating and configuring network slice entities based on the network slice templates provided by the orchestrator and performing entity feasibility checks; managing the network slice lifecycle; adjusting the size and dynamically expanding network slice entities; monitoring the integrity and independence of slices during operation; and performing slice decommissioning operations.

[0087] The Slice Manager is a new entity added in NFV-MANO, used for the management of network slice entities. Each network slice entity is a logically independent network, providing users with differentiated services of various performance levels. Network slices are created based on slice templates from the orchestrator and the required types and quantities of resources, and virtual links are generated via the VRM to connect these allocated resources via one-hop or multi-hop connections. Each network slice entity has a corresponding Slice Manager with a unique slice ID, assigned to a specific slice operator responsible for providing the corresponding services to users.

[0088] Furthermore, the VNF manager performs the following steps:

[0089] Receive the matching result sent by the orchestrator. If the matching result is successful, select the matching VNF template. If the matching result fails, create a new VNF template.

[0090] Based on the virtual function forwarding graph, obtain the VNF and the virtual resources required by the VNF in the VNF template, and send the VNF and the virtual resources required by the VNF as resource requests to the VRM.

[0091] Furthermore, the management orchestration unit also includes a VNF directory table, which records the VNF template information to which the VNF belongs and the VNF's own attribute information. The VNF's own attributes include resource requirements, allocation principles, operator policies, and software version information.

[0092] The VNF Manager is responsible for the management of VNF entities. This includes creating and configuring VNF entities based on VNF templates and performing feasibility checks; running VNF entity software updates and upgrades; adjusting and dynamically expanding the size of VNF entities; collecting performance test results and fault event information of underlying resources related to VNF entities; monitoring the integrity of VNF entities during operation and performing automatic repairs; and receiving notifications of changes to VNF lifecycle management and handling entity decommissioning operations.

[0093] In the NFV architecture, each VNF has a corresponding VNF manager, meaning each VNF manager can manage one or more VNFs of the same or different types. Detailed configuration parameters and operational behaviors of each VNF are stored in a corresponding VNF template. The VNFManager (VNF Manager) creates the corresponding VNF entity based on this template and monitors its operational status. All online VNF entities write their configuration template information and their own attributes, such as resource requirements, allocation principles, operator policies, and software version information, into a description file and store it in the VNF Catalogue. By accessing the catalogue, the VNF entity's relevant information can be viewed, and the underlying resources required to implement the VNF can be allocated according to the requirements in the description file. The VNFManager also accesses the catalogue to check if the VNF's software version matches the resources and performs software updates and upgrades.

[0094] Furthermore, Virtual Explorer performs the following steps:

[0095] Configure a virtual resource list, which records the types and capacities of virtual resources and provides an external access interface;

[0096] Receive resource requests from the slice manager or VNF manager and the virtual network function forwarding graph from the orchestrator;

[0097] Provide the required virtual resources based on the resource request;

[0098] Based on the virtual network function forwarding graph, virtual links are used to connect the required virtual resources to form corresponding network services;

[0099] Remove linked virtual resources from the virtual resource list and update the virtual resource list.

[0100] The Virtual Resource Manager is responsible for managing the underlying resources of the sliced ​​network, recording and allocating virtual resources. This includes mapping management from physical resources to virtual resources; virtual resource control, allocation, updating, release, and reclamation; creating virtual links and nodes, supporting the implementation of virtual network function forwarding lists; managing the directory list of physical and virtual resources, resource discovery; forwarding statistics on virtual resource usage and remaining resources; and collecting and forwarding performance and fault information of physical hardware, software resources, and virtual resources.

[0101] SDN controllers are added to Virtual Resource Managers (VRMs) to allocate and schedule resources to authorized users. These SDN controllers are integrated into the VRM unit of the orchestration manager and are monitored and queried by the VRM. The VRM controls and manages the underlying resources of the entire network slice, including physical hardware (computing, storage, routing, switching, etc.), software (controllers), and virtual resources (virtual machines). VRMs can be partitioned based on resource type (e.g., dedicated VRMs for computing, storage, and networking), infrastructure vendor (e.g., one VRM per vendor for their own resources), or geographical location (e.g., a single VRM for a single node or multiple nodes in the same region). The mapping from virtual to physical resources is collectively referred to as Virtual Network Embedding (VNE), a process of extracting and representing physical resources. After mapping, a software image is formed, and external services can access the image and connect to the corresponding physical resources through an interface. The list of virtual resources is managed and controlled by the VRM, including operations such as updating the list, upgrading images, and adding / deleting resources.

[0102] There is no specific order in which the steps performed by each structure in the management orchestration unit are executed; the order in which each structure is executed is based on the functions and purposes to be achieved.

[0103] A network slicing deployment method based on NFV-MANO, proposed according to a network slicing deployment system based on NFV-MANO, includes the following steps:

[0104] S1. The operator provides network requirements, and the service layer customizes network slicing parameters according to the network requirements and records the network slicing parameters as a slice request.

[0105] S2. The orchestrator receives the slice request service sent by the service layer, extracts the network slice parameters, matches the network slice template according to the network slice parameters, and sends the matching result to the slice manager;

[0106] S3. The slice manager receives the matching result. If the matching result is successful, the slice manager selects the matching network slice template, creates a network slice, and executes step 5. If the matching result fails, the slice manager creates a new network slice.

[0107] S4. The orchestrator determines the required VNFs based on the preset network functions of the newly created network slice, matches VNF templates according to the required VNFs, and sends the matching results to the VNF manager. If the matching result is successful, the VNF manager selects the matching VNF template; if the matching result fails, the VNF manager creates a new VNF template.

[0108] S5. The Virtual Resource Manager receives resource requests from the Slice Manager or VNF Manager. The resource requests include the virtual resources required for the materialization of network slices. It also receives the virtual function forwarding diagram sent by the orchestrator.

[0109] S6. The Virtual Resource Manager obtains the required virtual resources based on the resource request, and uses virtual links to connect the required virtual resources according to the virtual network function forwarding graph to form related network services.

[0110] Furthermore, step S1 includes the following steps: the service layer sends the slice request and the corresponding network service to the SDN controller, and the SDN controller adjusts network resources in multiple network slices.

[0111] Furthermore, the SDN controller performs network resource adjustments across multiple network slices, including the following steps:

[0112] Receive slice requests and corresponding network services from the service layer;

[0113] Parse the network slice parameters in the slice request to obtain the required virtual resources;

[0114] Obtain virtual resource information of existing network slices and network services in the network slicing layer;

[0115] Determine whether the remaining virtual resources retained after the existing virtual resources are reallocated meet the required virtual resources.

[0116] If the conditions are not met, the SDN controller adjusts network resources in multiple network slices according to the network slice parameters, and the process ends. If the conditions are met, virtual resources that meet the network services of the existing network slices in the network slice layer are reallocated, and the remaining virtual resources are obtained.

[0117] Create new network slices based on the virtual resources required for network service links.

[0118] Furthermore, step S7 is included: when the lifecycle of a network slice ends, the Virtual Resource Manager releases the virtual resources occupied by the network slice and updates the virtual resource list.

[0119] The above embodiments are preferred embodiments of the present invention, but the embodiments of the present invention are not limited to the above embodiments. Any changes or substitutions that can be conceived without creative effort should be covered within the protection scope of the present invention. Therefore, the protection scope of the present invention should be determined by the scope defined in the claims.

Claims

1. A network slicing deployment method based on NFV-MANO, characterized in that, Including the following steps: S1. The operator provides network requirements, and the service layer customizes network slicing parameters according to the network requirements and records the network slicing parameters as a slice request. S2. The orchestrator receives the slice request service sent by the service layer, extracts the network slice parameters, matches the network slice template according to the network slice parameters, and sends the matching result to the slice manager; S3. The slice manager receives the matching result. If the matching result is successful, the slice manager selects the matching network slice template, creates a network slice, and executes step 5. If the matching result fails, the slice manager creates a new network slice. S4. The orchestrator determines the required VNFs based on the preset network functions of the newly created network slice, matches VNF templates according to the required VNFs, and sends the matching results to the VNF manager. If the matching result is successful, the VNF manager selects the matching VNF template; if the matching result fails, the VNF manager creates a new VNF template. S5. The Virtual Resource Manager receives a resource request sent by the Slice Manager or VNF Manager. The resource request includes virtual resources required for the materialization of the network slice. It also receives a Virtual Function Forwarding Graph sent by the Orchestrator. The Virtual Function Forwarding Graph consists of VNFs in the network slice and their link information. S6. The virtual resource manager obtains the required virtual resources based on the resource request, and uses virtual links to connect the required virtual resources according to the virtual function forwarding graph to form related network services; Step S1 includes the following steps: the service layer sends the slice request and the corresponding network service to the SDN controller, and the SDN controller adjusts network resources in multiple network slices; The SDN controller is also connected to the VNF directory table, enabling it to query the VNF directory table to check if there are available VNF templates to select before creating a network slice based on the network slice parameters.

2. The network slicing deployment method based on NFV-MANO as described in claim 1, characterized in that, The SDN controller performs network resource adjustments across multiple network slices, including the following steps: Receive slice requests and corresponding network services from the service layer; Parse the network slice parameters in the slice request to obtain the required virtual resources; Obtain virtual resource information of existing network slices and network services in the network slicing layer; Determine whether the remaining virtual resources retained after the existing virtual resources are reallocated meet the required virtual resources. If the conditions are not met, the SDN controller adjusts network resources in multiple network slices according to the network slice parameters, and the process ends. If the conditions are met, virtual resources that meet the network services of the existing network slices in the network slice layer are reallocated, and the remaining virtual resources are obtained. Create new network slices based on the virtual resources required for network service links.

3. The network slicing deployment method based on NFV-MANO as described in claim 1, characterized in that, It also includes step S7: when the lifecycle of a network slice ends, the virtual resource manager releases the virtual resources occupied by the network slice and updates the virtual resource list.

4. A network slicing deployment system based on NFV-MANO, based on the network slicing deployment method according to any one of claims 1 to 3, characterized in that, The deployment system includes an infrastructure resource layer, a network slicing layer, a service layer, and a management orchestration unit. The infrastructure resource layer maps physical resources to virtual resources, and the virtual resources have access interfaces to connect to the physical resources. The network slicing layer includes several network slices, and each network slice includes one or more service chains. Each service chain includes multiple Virtual Network Functions (VNFs) connected by virtual links. Each service chain provides a network service. The management orchestration unit manages the infrastructure resource layer, the network slicing layer, and the service layer. The service layer is at the top of the network slicing model and is used to provide various unique network services in the 5G network.

5. A network slicing deployment system based on NFV-MANO as described in claim 4, characterized in that, The management orchestration unit includes an orchestrator, a VNF manager, a virtual resource manager, and a slice manager. The orchestrator orchestrates network slices and network resources, the VNF manager manages VNF templates, the slice manager manages network slice templates, and the virtual resource manager records virtual resource data and allocates virtual resources.

6. A network slicing deployment system based on NFV-MANO as described in claim 5, characterized in that, The orchestrator performs the following steps: The orchestrator calculates the virtual resources required for the network slice parameters in the slice request, sends an information acquisition request to the virtual resource manager and receives the existing virtual resource information sent back by the virtual resource manager, and determines whether the existing virtual resources meet the required virtual resources. If they do, the orchestrator sends a network slice creation request to the slice manager. If they do not meet the requirements, the orchestrator puts the slice request back into the slice request queue. The orchestrator matches a network slice template according to the network slice parameters and sends the matching result to the slice manager; The orchestrator determines the required VNFs based on the preset network functions of the newly created network slice, matches VNF templates according to the required VNFs, and sends the matching results to the VNF manager.

7. A network slicing deployment system based on NFV-MANO as described in claim 5, characterized in that, The orchestrator also performs the following steps: The network slice's VNFs and their link information are combined to form a Virtual Function Forwarding Graph (VFFT). The network slice's materialization request and the VFFT VFFT VF template are then sent to the VNF template.

8. A network slicing deployment system based on NFV-MANO as described in claim 6, characterized in that, The slice manager performs the following steps: Receive the matching result sent by the orchestrator. If the matching result is successful, select the matching network slice template to create a network slice. If the matching result fails, create a new network slice.

9. A network slicing deployment system based on NFV-MANO as described in claim 6, characterized in that, The VNF manager performs the following steps: Receive the matching result sent by the orchestrator. If the matching result is successful, select the matching VNF template. If the matching result fails, create a new VNF template. Based on the virtual function forwarding graph, obtain the VNF and the virtual resources required by the VNF in the VNF template, and send the VNF and the virtual resources required by the VNF as resource requests to the Virtual Resource Manager (VRM).

10. A network slicing deployment system based on NFV-MANO as described in claim 5, characterized in that, The virtual resource manager performs the following steps: Configure a virtual resource list, which records the types and capacities of virtual resources and provides an external access interface; Receive resource requests from the slice manager or VNF manager and the virtual function forwarding graph from the orchestrator; Provide the required virtual resources based on the resource request; Based on the virtual function forwarding diagram, virtual links are used to connect the required virtual resources to form corresponding network services; Remove linked virtual resources from the virtual resource list and update the virtual resource list.

11. A network slicing deployment system based on NFV-MANO as described in claim 4, characterized in that, The management and orchestration unit also includes a VNF directory table, which records the VNF template information to which the VNF belongs and the VNF's own attribute information. The VNF's own attributes include resource requirements, allocation principles, operator policies, and software version information.

12. A network slicing deployment system based on NFV-MANO as described in claim 4, characterized in that, It also includes an SDN controller that adjusts network resources across multiple network slices based on network slice parameters.

13. A network slicing deployment system based on NFV-MANO as described in claim 12, characterized in that, The SDN controller performs the following steps: Receive network slice parameters and corresponding network services from the service layer; Parse network slice parameters to obtain the required virtual resources; Obtain virtual resource information of existing network slices and network services in the network slicing layer; Determine whether the remaining virtual resources retained after the existing virtual resources are reallocated meet the required virtual resources. If the conditions are not met, the SDN controller completes the step of adjusting network resources in multiple network slices based on network slice parameters. If the conditions are met, virtual resources that meet the network services of the existing network slices in the network slice layer are reallocated, and the remaining virtual resources are obtained. Create new network slices based on the virtual resources required for network service links.

14. A network slicing deployment system based on NFV-MANO as described in claim 4, characterized in that, The network slicing parameters include bandwidth, latency, and QoS.

15. A network slicing deployment system based on NFV-MANO as described in claim 4, characterized in that, The physical resources include spectrum, bandwidth, routing and switching equipment, storage centers, and processors, while the virtual resources include large data centers and high-speed network connections.

Images