A service protection method for slice fault in 5g power grid slicing

Abstract

The application discloses a service protection method for slice faults in a 5G power grid slice, and the method comprises the following steps: acquiring service streams of a power virtual private network terminal device, forming VNF service chains from the acquired service streams, and processing different VNF service chains by different network slices; when a network slice has a fault, a corresponding slice protection scheme is used to process the network slice according to the type of the VNF service chain processed by the network slice, and the slice protection scheme is that when a network slice in an MEC has a fault, a backup slice pre-placed is used to take over the service chain of the main slice to perform a service operation. According to the importance of the network slice or the service chain, the application sets corresponding protection schemes according to the importance of the power grid service chain, so that different services in the 5G slice network can be better served, the power grid system is better served, and the stability and reliability of the power grid operation are improved.

Description

Technical Field

[0001] This invention belongs to the field of communication technology, and specifically relates to a service protection method for slice faults in 5G power grid slicing. Background Technology

[0002] In new power systems, new energy sources such as wind power and solar power have been vigorously promoted, the scale of distribution networks has continued to expand, the number of connected devices has increased significantly, and the structure of distribution networks has become increasingly complex. At the same time, the access of distributed power sources, intelligent converged terminals, and interrupted load terminals has also placed higher demands on the network's ability to process services.

[0003] The differentiated characteristics and demands of the power industry necessitate that 5G network slicing play a crucial role in smart grids. Smart grid services based on 5G network slicing can effectively improve end-to-end Service Level Agreement (SLA) guarantees, service isolation, and operational independence. The 5G network is divided into three layers: the infrastructure layer, the service enablement layer, and the application value layer. The infrastructure layer includes various wireless access node devices and virtualization-based shared hardware devices. The service enablement layer includes the current core network control plane and some access-side network element functions. These functions run in a network function virtualization (NFV) manner within physical devices uniformly managed by the data center. The service enablement layer is a natural evolution of the existing network architecture and will apply key technologies including Software-Defined Networking (SDN), Network Function Virtualization (NFV), and MEC. Vertically, the communication network is subdivided into multiple virtual private networks; horizontally, it forms a programmable, elastic, flexible, and reliable layered architecture.

[0004] Network slicing isolation in the power industry mainly includes two dimensions: isolation between power and other industries and individual user communication services, and isolation between services in different power sector segments. Services are selected and routed to the corresponding core network slice to achieve network slice routing and resource isolation. For potential emergency support needs within power service network slices, technologies such as priority admission and load control can be used to prioritize high-priority power services and prevent services in other slices from impacting the performance of power services.

[0005] However, when a network slice itself malfunctions, it can impact the services offered by terminal devices, thereby affecting the stability and reliability of the power grid. Therefore, there is an urgent need to research a protection mechanism that ensures different service requirements are met when a power network slice itself fails. Summary of the Invention

[0006] In order to ensure that different service requirements are protected to a certain extent when a network slice in the MEC (Edge Computing) pool fails in a 5G slicing network, this application proposes a service protection method for slice failure in 5G power grid slicing. This application classifies the service chains in the power grid and provides corresponding service protection strategies for different service chains, thereby avoiding the impact of service slice failure on terminal equipment and ensuring the stability and reliability of network operation.

[0007] This invention is achieved through the following technical solution:

[0008] A service protection method for slice faults in 5G power grid slicing, the method comprising:

[0009] The service flow of the power virtual private network terminal equipment is obtained and formed into a VNF service chain. Different network slices process different VNF ​​service chains.

[0010] When a network slice fails, a corresponding slice protection scheme is adopted according to the type of VNF service chain it is handling. The slice protection scheme is to take over the service chain of the main slice and perform service operations through a pre-placed backup slice when a network slice in the MEC fails.

[0011] The protection method proposed in this application starts from the importance of network slicing or the service chain, and sets up corresponding protection schemes according to the importance of the power grid service chain to meet the protection of different services in 5G slicing network, better serve the power grid system, ensure that the services of terminal equipment are not affected in the case of main slice failure, and improve the stability and reliability of power grid operation.

[0012] As a preferred embodiment, when a network slice fails, this application employs a corresponding slice protection scheme based on the type of VNF service chain it is processing, specifically including:

[0013] When the business chain type is a control-type business chain, a 1-to-1 protection scheme is adopted, that is, when the main slice fails, the corresponding backup slice can take over the business data executed by the main slice in a timely manner and process it.

[0014] When the business chain type is an application-type business chain, a 1-to-N protection scheme is adopted, that is, one backup slice can take over and process the business data executed by N main slices; where N is an integer greater than or equal to 2.

[0015] When the business chain type is a data acquisition business chain, the backup core VNF function network element is used to protect it.

[0016] The control-type business chain requires greater protection than the application-type business chain, and the application-type business chain requires greater protection than the data acquisition-type business chain.

[0017] This application divides the power grid service chain into three categories and adopts different fault slicing protection schemes for these three categories. Based on the importance of the service chain, 1-to-1, 1-to-N and core network element unit VNF ​​protection are adopted respectively. By selecting different protection scheme types according to the importance of the service chain, the cost of network construction can be reduced, and the service chain protection strategy can be implemented with minimal cost.

[0018] As a preferred embodiment, the method of this application further includes:

[0019] The resources in the MEC required for the protection scheme are allocated in advance, and the number and location of backup slices are planned.

[0020] As a preferred implementation, the resource allocation of this application needs to meet three conditions;

[0021] Determine the type of VNF service chain being processed by the current main slice;

[0022] The backup slice is designated to provide services to the VNF service chain processed by the main slice on the MEC.

[0023] The CPU and RAM resources provided by the MEC in the network serve as constraints.

[0024] As a preferred embodiment, the objective function for placing backup slices in this application is to determine the optimal number of slices and the number of available MECs while meeting the service latency and reliability requirements of power services in a 5G environment.

[0025] As a preferred embodiment, the objective function of this application is expressed as:

[0026]

[0027]

[0028]

[0029] Where, d v Indicates the size of the demand; b uv q represents the bandwidth between the service request point v and the primary slice on the MEC u that provides the service; q represents the failure probability of the MEC. ,when MEC The slice assigned to request point v is the primary slice; otherwise, it is the backup slice. ,when MEC When active, it can request nodes. Provide services; ,when In MEC The value placed on The A slice is selected if it is not placed; otherwise, it is an unplaced slice.

[0030] As a preferred embodiment, the backup slice placement issue in this application also needs to meet the following constraints:

[0031] The primary and backup slices of the demand point should not be hosted in the same MEC;

[0032] The demand points are assigned to one primary slice and one backup slice, respectively.

[0033] Demand points cannot be assigned on unassigned slices;

[0034] Slices cannot be hosted on MECs that do not provide services;

[0035] Demand points cannot be allocated to MECs that do not provide services;

[0036] The total CPU and storage resources allocated to each slice cannot exceed the CPU and storage resources used by each MEC.

[0037] MEC and bandwidth constraints at demand points;

[0038] The reliability of the implemented protection scheme should be greater than or equal to the reliability expected at the demand point;

[0039] The total delay should be less than or equal to the maximum delay that the demand point can tolerate.

[0040] As a preferred embodiment, the constraints of this application are expressed as follows:

[0041] .

[0042] As a preferred embodiment, the method of this application uses a metaheuristic algorithm of non-dominated sorting genetic algorithm to solve the objective function.

[0043] In a preferred embodiment, the method of this application further includes setting a value that reflects the goodness of the desired optimization objective as the cutoff target for the solution iteration process.

[0044] Compared with the prior art, the present invention has the following advantages and beneficial effects:

[0045] 1. Based on the characteristics of power services, this application divides power services according to their importance and sets different protection schemes for different levels of importance. When a slice in the network fails, it is only necessary to process the service according to the backup slices placed in different MECs in advance, so as to avoid service interruption, ensure the normal processing of power grid services, and improve the quality of network services.

[0046] 2. This application pre-allocates MEC resources and plans the location and number of backup slices in the MEC. Then, protection operations for the power grid service chain can be completed according to the service types and constraints supported by the backup slices, thereby ensuring the protection of important services in the power virtual network and avoiding the impact of slice failures on power grid services. Attached Figure Description

[0047] The accompanying drawings, which are included to provide a further understanding of embodiments of the invention and form part of this application, do not constitute a limitation thereof. In the drawings:

[0048] Figure 1 This is a flowchart of a method according to an embodiment of the present invention.

[0049] Figure 2 This is a 1:1 protection scheme according to an embodiment of the present invention.

[0050] Figure 3 This is a 1:N protection scheme according to an embodiment of the present invention.

[0051] Figure 4 This is a backup scheme for key network element devices in this embodiment of the invention. Detailed Implementation

[0052] To make the objectives, technical solutions, and advantages of the present invention clearer, the present invention will be further described in detail below with reference to the embodiments and accompanying drawings. The illustrative embodiments and descriptions of the present invention are only used to explain the present invention and are not intended to limit the present invention.

[0053] Example:

[0054] In 5G slicing networks, to prevent different service requirements from being affected by slice failures when network slices in the MEC pool fail, and to ensure the stability and reliability of 5G slicing network operation, this embodiment proposes a service protection method for slice failures in 5G power grid slicing. This embodiment classifies the service chains in the power grid according to the service quality requirements of different service chains, and provides corresponding service protection strategies for different service chains to prevent the service requirements of terminal devices from being affected by slice failures, thereby ensuring the stability and reliability of network operation.

[0055] Specifically, such as Figure 1As shown, the method proposed in this embodiment includes the following steps:

[0056] Step 1: Obtain the service flow of the power virtual private network terminal device, and form a VNF service chain from the obtained service flow. Different network slices process different VNF ​​service chains.

[0057] Step 2: When a network slice fails, the corresponding slice protection scheme is adopted according to the type of VNF service chain it is handling. The slice protection scheme protects the service chain based on 5G slices placed in different MECs. If a network slice placed in an MEC fails, the service chain of the primary slice is taken over by a pre-determined backup slice to perform service operations.

[0058] This embodiment categorizes the service chains in the power grid into three types:

[0059] I. Control-related business chain: This refers to the power operating system issuing control commands to terminal equipment to ensure the normal operation of the terminal equipment and to control the terminal equipment in case of emergencies. This type of business needs to be protected.

[0060] II. Application-related business chain: This refers to the business types generated by certain applications that require key protection during the operation of terminal devices. These businesses include the information status of terminal devices, such as handling sudden traffic surges.

[0061] III. Data Acquisition Business Chain: This refers to the business needs that need to be processed by terminal devices during their daily operation.

[0062] Different slice protection schemes are set for the three types of business chains mentioned above: For control-type business chains, since key protection is required for control-type services, this embodiment adopts a 1-to-1 protection scheme. That is, when the primary slice fails, a backup slice can promptly take over the business data executed by the primary slice and process it, ensuring the safe issuance of control commands. The protection scheme is as follows: Figure 2 As shown, in the event of a failure, the demand points are reassigned to dedicated backup slices hosted on different MECs. Both the primary and backup slices are assigned to only one demand point. For application-type service chains, the required protection is less than that for control-type services. Therefore, this embodiment adopts a 1-to-N protection scheme, meaning one backup slice can take over and process the service data executed by N primary slices. This reduces resource waste, lowers costs, and better serves the power grid service. The protection scheme is as follows: Figure 3 As shown, in the event of a failure, demand points will be reassigned to shared backup slices hosted on different MECs. That is, the primary slice hosts only one demand point, while the backup slice is distributed among different MECs. Each requirement point is shared; for data acquisition service chains, since the impact of a failure in data acquisition services on the entire network is minimal, this embodiment uses a backup core VNF functional network element for protection, as described in the protection scheme below. Figure 4 As shown, if a core network element fails, the demand will be reassigned to a shared backup slice hosted on different MECs. The backup slice protects the core network element portion of the service. Here, N is an integer greater than or equal to 2.

[0063] The method proposed in this embodiment also requires prior allocation of resources in the MEC required for the protection scheme, as well as planning the number and location of backup slices. Resource allocation must meet three important conditions, including:

[0064] 1) Determine the importance (i.e. type) of the business chain being processed by the current main slice;

[0065] 2) Designate the backup slice to provide services for the VNF service chain processed by the main slice on the MEC;

[0066] 3) The CPU and RAM resources provided by EMC in the network can be regarded as constraints of this scheme.

[0067] The target function for placing backup slices is:

[0068] (1)

[0069] (2)

[0070] (3)

[0071] In the objective function, (1) represents the total number of slices serving a certain demand point, (2) represents the number of MECs in an active state, and (3) represents minimizing the total response time. The trade-off between the above objectives can be expressed as follows: the more backup slices there are, the higher the service reliability and the shorter the response time, but the greater the cost will be.

[0072] in, These represent the MEC set and the business request point set, respectively. Indicates the maximum number of slices to place on each MEC; d v Indicates the size of the demand; b uv This represents the bandwidth between the service request point v and the primary slice on the MEC u providing the service; b mv Indicates the business request point With MEC providing services The bandwidth between backup slices on the network; q represents the failure probability of the MEC; ,when MEC The slice assigned to request point v is the primary slice; otherwise, it is the backup slice. ,when MEC When active, it can request nodes. Provide services; ,when In MEC The value placed on The One slice is selected; otherwise, it is an unplaced slice. Represented as a business request point MEC service The The main slice is a single slice. This is shown as a business request point. MEC service The Each slice is a backup slice; ,when Represented as a business request point MEC service The value is The A slice.

[0073] Primary and backup slices are easily placed in the same MEC. When the MEC is in a fault state, the above protection scheme cannot guarantee the reliable implementation of the service chain. Therefore, in order to prevent the impact on the entire power grid service when the MEC is in a fault state, the placement of backup slices needs to meet the following constraints:

[0074]

[0075] Among them, constraint 1 states that the primary slice and backup slice of demand point v should not be hosted in the same MEC; constraints 2 and 3 ensure that a given demand point v is precisely assigned to one primary slice and one backup slice, respectively; constraint 4 states that demand points cannot be assigned to unassigned slices; constraint 5 states that slices (primary slices and backup slices) cannot be hosted on MECs that are not providing services; constraint 6 states that demand points cannot be assigned to MECs that are not providing services; constraints 7 and 8 state that the total CPU and storage resources allocated to each slice cannot exceed the CPU and storage resources owned by each MEC; constraint 9 restricts the MEC... With demand points Bandwidth constraints; Constraint 10 indicates that the reliability of the implemented protection scheme should be greater than or equal to the requirement point. Desired reliability The left side indicates different MECs Availability of primary and backup slices; Constraint 11 states that total latency should be less than or equal to the demand point. Maximum allowable latency ,in Indicate demand points The request in MEC The first one hosted by the upper management The time spent processing each slice, i.e., the demand point. CPU resources required With MEC Assigned to the The ratio of CPU resources allocated to each slice. .

[0076] This embodiment employs a metaheuristic algorithm based on the Non-Dominated Sorting Genetic Algorithm (NSGA-II) to solve the aforementioned objective function. This algorithm is used to determine the optimal number of slices and MEC to meet the service latency and reliability requirements of power services in a 5G environment. Since this algorithm requires continuous iteration to achieve the desired optimization objective, a goodness value reflecting the desired optimization objective is assigned to it. It should be noted that this solution algorithm is existing technology and will not be elaborated upon further here.

[0077] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0078] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0079] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0080] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0081] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of the present invention. It should be understood that the above description is only a specific embodiment of the present invention and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

Claims

1. A service protection method for slice faults in 5G power grid slicing, characterized in that, The method includes: The service flow of the power virtual private network terminal equipment is obtained and formed into a VNF service chain. Different network slices process different VNF ​​service chains. When a network slice fails, a corresponding slice protection scheme is adopted based on the type of VNF service chain it handles. This slice protection scheme involves a pre-placed backup slice taking over the service chain of the primary slice to perform service operations when a network slice in the MEC fails. Specifically, the slice protection scheme includes: When the business chain type is a control-type business chain, a 1-to-1 protection scheme is adopted, that is, when the main slice fails, the corresponding backup slice can take over the business data executed by the main slice in a timely manner and process it. When the business chain type is an application-type business chain, a 1-to-N protection scheme is adopted, that is, one backup slice can take over and process the business data executed by N main slices; where N is an integer greater than or equal to 2. When the business chain type is a data acquisition business chain, the backup core VNF function network element is used to protect it. The protection level required for the control-type business chain is greater than that required for the application-type business chain, and the protection level required for the application-type business chain is greater than that required for the data acquisition-type business chain. The method also includes: The resources in the MEC required for the protection scheme are pre-allocated, and the number and location of backup slices are planned. The resource configuration needs to meet three conditions, including: determining the type of VNF service chain being processed by the current main slice; specifying that the backup slice provides services for the VNF service chain processed by the main slice on the MEC; and the CPU and RAM resources provided by the MEC in the network as constraints. The objective function for backup slice placement is to determine the optimal number of slices and the number of available MECs while meeting the service latency and reliability requirements of power services in a 5G environment. The placement of backup slices also needs to meet the following constraints: The primary and backup slices at the point of demand should not be hosted in the same MEC; The demand points are assigned to one primary slice and one backup slice, respectively. Demand points cannot be assigned on unassigned slices; Slices cannot be hosted on MECs that do not provide services; Demand points cannot be allocated to MECs that do not provide services; The total CPU and storage resources allocated to each slice cannot exceed the CPU and storage resources used by each MEC. MEC and bandwidth constraints at demand points; The reliability of the implemented protection scheme should be greater than or equal to the reliability expected at the demand point; The total delay should be less than or equal to the maximum delay that the demand point can tolerate.

2. The service protection method for slice faults in 5G power grid slicing according to claim 1, characterized in that, This method uses a metaheuristic algorithm based on non-dominated sorting genetic algorithm to solve the objective function.

3. The service protection method for slice faults in 5G power grid slicing according to claim 2, characterized in that, The method also includes setting a goodness value that reflects the desired optimization objective as the cutoff target for the solution iteration process.

Images