Network configuration method, data forwarding method, device, equipment and storage medium

Abstract

The embodiment of the invention discloses a network configuration method and device, a data forwarding method and device, equipment and a storage medium, and the network configuration method comprises the steps: obtaining slice configuration information between source end equipment and sink end equipment, and the slice configuration information comprises a network slice ID, bandwidth information, a segment routing traffic engineering strategy and a target service identifier; generating a routing path between the source end device and the sink end device according to the bandwidth information and the segment routing traffic engineering strategy; generating a slice configuration command according to the slice configuration information and the routing path, and issuing the slice configuration command to each device in the routing path, the slice configuration command is used for instructing each device to transmit target service data corresponding to the target service identifier according to a network slice channel corresponding to the network slice ID. According to the embodiment of the invention, the data transmission efficiency can be improved, and the waste of bandwidth resources is reduced.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a network configuration method, a data forwarding method, an apparatus, a device, and a storage medium. Background Technology

[0002] The power grid safety emergency response system, also known as the power grid second-level interruptible load rapid response system, is a highly efficient and sophisticated power grid management tool. Its operation is based on close interaction between the power grid and customers, achieving rapid response and emergency handling for power grid safety through precise control and management of loads.

[0003] In existing technologies, State Grid Corporation of China has adopted a 5G soft slicing mode to achieve second-level access management of power system terminals. The original power grid security emergency response method used MPLS (Multi-Protocol Label Switching) VPN (Virtual Private Network) for service and network isolation, and employed soft slicing technologies such as QoS. However, this was essentially a shared channel; if traffic congestion occurred, it would simultaneously affect other customer networks, which was detrimental to fully guaranteeing the transmission quality for government and enterprise customers. To achieve physical isolation with dedicated channels, slicing technology could be introduced. However, the common slicing technology under 5G networks is FlexE, which is a large-granularity slice (minimum 1Gbps), unsuitable for most government and enterprise scenarios. Furthermore, for power grid security emergency response applications, the cost of using FlexE is too high. Given the large number and dispersed nature of various power-consuming units at the end of the power grid, even the smallest granularity (1Gbps) of FlexE slicing would lead to significant resource waste. Summary of the Invention

[0004] This application provides a network configuration method, a data forwarding method, an apparatus, a device, and a storage medium, which help improve data transmission efficiency and reduce resource waste.

[0005] To address the aforementioned problems, in a first aspect, embodiments of this application provide a network configuration method, including:

[0006] Obtain slice configuration information between the source device and the destination device. The slice configuration information includes network slice ID, bandwidth information, segment routing traffic engineering policy, and target service identifier.

[0007] Based on the bandwidth information and the segment routing traffic engineering strategy, a routing path is generated between the source device and the destination device;

[0008] Based on the slice configuration information and the routing path, a slice configuration command is generated and sent to each device in the routing path. The slice configuration command is used to instruct each device to transmit the target service data corresponding to the target service identifier according to the network slice channel corresponding to the network slice ID.

[0009] Secondly, embodiments of this application provide a data forwarding method applied to a source device, comprising:

[0010] Receive a slice configuration command, the slice configuration command including network slice ID and routing path;

[0011] Configure a network slice instance and a network slice channel corresponding to the network slice ID, and associate the network slice channel with the network slice instance based on the network slice ID;

[0012] When a data packet is received through the target VPN instance, the outgoing interface of the data packet is determined to be the segment routing traffic engineering policy according to the routing table of the target VPN instance. The target VPN instance is a VPN instance associated with the target service identifier.

[0013] According to the configured slice encapsulation method, the data packet and network slice ID are encapsulated into an IPv6 packet;

[0014] The IPv6 packet is sent to the next device through the network slice channel corresponding to the network slice ID.

[0015] Thirdly, embodiments of this application provide a data forwarding method applied to a destination device, comprising:

[0016] Receive a slice configuration command, the slice configuration command including the network slice ID and routing path;

[0017] Configure a network slice instance and a network slice channel corresponding to the network slice ID, and associate the network slice channel with the network slice instance based on the network slice ID;

[0018] Receive IPv6 packets through the network slice channel corresponding to the network slice ID;

[0019] The IPv6 packet is decapsulated, the IPv6 packet header is removed to obtain the data packet, and the data packet is forwarded to the user edge device corresponding to the target VPN instance.

[0020] Fourthly, embodiments of this application provide a network configuration device, including:

[0021] The configuration information acquisition module is used to acquire slice configuration information between the source device and the destination device. The slice configuration information includes network slice ID, bandwidth information, segment routing traffic engineering policy and target service identifier.

[0022] The path generation module is used to generate a routing path between the source device and the destination device based on the bandwidth information and the segment routing traffic engineering strategy.

[0023] The configuration command distribution module is used to generate a slice configuration command based on the slice configuration information and the routing path, and to distribute the slice configuration command to each device in the routing path. The slice configuration command is used to instruct each device to transmit the target service data corresponding to the target service identifier according to the network slice channel corresponding to the network slice ID.

[0024] Fifthly, embodiments of this application provide a data forwarding apparatus applied to a source device, comprising:

[0025] A configuration command receiving module is used to receive slice configuration commands, which include network slice ID and routing path;

[0026] The slice configuration module is used to configure the network slice instance and network slice channel corresponding to the network slice ID, and associate the network slice channel with the network slice instance according to the network slice ID;

[0027] The message outgoing interface determination module is used to determine, when a data packet is received through a target VPN instance, the outgoing interface of the data packet is a segment routing traffic engineering policy based on the routing table of the target VPN instance, wherein the target VPN instance is a VPN instance associated with a target service identifier;

[0028] The message encapsulation module is used to encapsulate the data packet and network slice ID into an IPv6 packet according to the configured slice encapsulation method;

[0029] The packet forwarding module is used to send the IPv6 packet to the next device through the network slice channel corresponding to the network slice ID.

[0030] Sixthly, embodiments of this application provide a data forwarding device applied to a destination device, comprising:

[0031] A configuration command receiving module is used to receive slice configuration commands, which include network slice ID and routing path;

[0032] The slice configuration module is used to configure the network slice instance and network slice channel corresponding to the network slice ID, and associate the network slice channel with the network slice instance according to the network slice ID;

[0033] The message receiving module is used to receive IPv6 messages through the network slice channel corresponding to the network slice ID;

[0034] The packet forwarding module is used to decapsulate the IPv6 packet, remove the IPv6 packet header to obtain the data packet, and forward the data packet to the user edge device corresponding to the target VPN instance.

[0035] In a seventh aspect, embodiments of this application also provide an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the network configuration method described in the first aspect, or the data forwarding method described in the second or third aspect.

[0036] Eighthly, embodiments of this application provide a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the network configuration method described in the first aspect, or the data forwarding method described in the second or third aspect.

[0037] The network configuration method, data forwarding method, apparatus, device, and storage medium provided in this application obtain slice configuration information between the source device and the destination device. The slice configuration information includes network slice ID, bandwidth information, segment routing traffic engineering policy, and target service identifier. A routing path between the source device and the destination device is generated based on the bandwidth information and segment routing traffic engineering policy. A slice configuration command is generated based on the slice configuration information and the routing path, and the slice configuration command is sent to each device in the routing path. Each device can transmit the target service data corresponding to the target service identifier based on the network slice channel corresponding to the network slice ID. Since the isolated network slice is dedicated to the transmission of target service data and is not affected by traffic congestion of other users, data transmission efficiency can be improved. Moreover, bandwidth information can be configured based on demand information, reducing the waste of bandwidth resources. Attached Figure Description

[0038] To more clearly illustrate the technical solutions of the embodiments of this application, 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 this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0039] Figure 1This is a flowchart of a network configuration method provided in an embodiment of this application;

[0040] Figure 2 This is a schematic diagram of the slice configuration and routing calculation process in the embodiments of this application;

[0041] Figure 3 This is a physical topology diagram of the power network slice in the embodiments of this application;

[0042] Figure 4 This is a power slicing network topology diagram in an embodiment of this application;

[0043] Figure 5 This is a flowchart of a data forwarding method provided in an embodiment of this application;

[0044] Figure 6 This is a flowchart of a data forwarding method provided in an embodiment of this application;

[0045] Figure 7 This is an example diagram of network slice packet forwarding in the SRv6 TE Policy data plane in this application embodiment;

[0046] Figure 8 This is a schematic diagram of the structure of a network configuration device provided in an embodiment of this application;

[0047] Figure 9 This is a schematic diagram of the structure of a data forwarding device provided in an embodiment of this application;

[0048] Figure 10 This is a schematic diagram of the structure of a data forwarding device provided in an embodiment of this application;

[0049] Figure 11 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0050] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0051] The power grid emergency response system is primarily designed for customers with discrete manufacturing processes, meaning it is particularly suitable for enterprises whose electricity load fluctuates significantly during production. In the event of a power grid emergency, such as overload or equipment failure, the dispatching agency can quickly and accurately locate the interruptible loads within the customer's system and systematically disconnect them according to their priority. This "low-to-high" disconnection strategy ensures the continuity of critical loads, thereby maximizing the protection of normal production for enterprises and the stable operation of the power grid.

[0052] To achieve this goal, electricity customers need to finely differentiate and manage various electricity-consuming units at the end of the power grid. This includes dividing different electricity-consuming units such as medical facilities, transportation, factories, and residential communities into smaller, more granular categories to more accurately understand and control their electricity usage. Simultaneously, leveraging the wide coverage of wireless technology, load control terminals within the area can be effectively managed, ensuring a rapid response and appropriate control measures when needed.

[0053] In this way, the power interruptible load rapid response system can accurately and intelligently manage power-consuming units in the event of a sudden overload of the power grid. It can ensure uninterrupted power supply to high-priority and most sensitive load units such as medical and transportation facilities, thereby avoiding or reducing adverse impacts on important aspects of social and economic life.

[0054] In summary, the second-level interruptible load rapid response system is a forward-looking and practical power grid management tool. It not only improves the security and stability of the power grid but also provides more intelligent and efficient services to electricity customers. With the continuous development and application of smart grid technology, this system will play an even more important role in the future.

[0055] The network configuration method, data forwarding method, apparatus, device, and storage medium provided in this application embodiment can effectively ensure the stable operation of the power grid safety emergency response system.

[0056] Figure 1 This is a flowchart illustrating a network configuration method provided in an embodiment of this application. This network configuration method can be executed by a network element management system, such as... Figure 1 As shown, the method includes steps 110 to 130.

[0057] Step 110: Obtain slice configuration information between the source device and the destination device. The slice configuration information includes network slice ID, bandwidth information, segment routing traffic engineering policy, and target service identifier.

[0058] The network slice ID, or Slice ID, is the core element of a network slice. Each network slice has a unique slice ID, which is used to identify and distinguish different network slices, ensuring that each slice can be correctly identified and managed at both the control and forwarding layers. The source and destination devices are bearer network devices. The target service identifier is for services with high latency requirements, such as the identifier for a power grid safety emergency response system.

[0059] Segment Routing Traffic Engineering Policy (SRv6 TE Policy) is a new tunneling technology developed based on SRv6 technology. SRv6 (Segment Routing IPv6) is a protocol designed based on source routing principles for forwarding IPv6 packets over a network. An SRv6 TE Policy path is represented as a list of segments specifying the path, called a Segment ID List. Each SID list represents an end-to-end path from source to destination and instructs devices in the network to follow the specified path, rather than the shortest path calculated by IGP. If a packet is imported into an SRv6 TE Policy, the SID list is added to the packet from the header, and the remaining devices in the network execute the instructions embedded in the SID list.

[0060] When configuring Slice ID granular slicing, slice configuration information can be obtained from the configuration interface of the network element device management system. When allocating network slice channels to users based on their needs, source and destination device information can be configured. These information can include the device name and IP address, respectively. Additionally, Slice ID, bandwidth information (Slice bandwidth), and segment routing traffic engineering policies also need to be configured. Slice configuration information can also include the number of candidate paths. In a power grid safety emergency response system, to ensure system stability, the number of candidate paths can be configured to 2 to guarantee reliable data transmission.

[0061] The Policy can also be configured with routing constraints, which can include: latency constraints, bandwidth constraints, inclusion constraints, exclusivity constraints, hop count constraints, affinity attributes, etc.

[0062] Step 120: Generate a routing path between the source device and the destination device based on the bandwidth information and the segment routing traffic engineering strategy.

[0063] The SRv6-TE-Policy tunneling technology automatically calculates and selects the path with the optimal network performance between the source and destination devices. This path is then used as the routing path between the source and destination devices. The routing path includes the device identifier and interface information of each forwarding device along the path.

[0064] In some embodiments of this application, generating a routing path between the source device and the destination device based on the bandwidth information and the segment routing traffic engineering strategy includes: generating a primary path and an alternative path between the source device and the destination device based on the bandwidth information and the segment routing traffic engineering strategy, and using the primary path and the alternative path as the routing path.

[0065] The SRv6-TE-Policy tunnel routing technology automatically calculates and selects the path with the best network performance between the source and destination devices as the primary path, and selects the path with the second-best network performance as the alternative path.

[0066] The SRv6-TE-Policy tunneling technology can automatically select a route between the source and the destination, determining the primary and alternative paths between them. Each path includes the device identifier (such as IP address) and interface information of each forwarding device.

[0067] By generating a primary path and alternative paths when generating routing paths between the source and destination devices, the reliability of data transmission can be guaranteed.

[0068] Step 130: Generate a slice configuration command based on the slice configuration information and the routing path, and send the slice configuration command to each device in the routing path. The slice configuration command is used to instruct each device to transmit the target service data corresponding to the target service identifier according to the network slice channel corresponding to the network slice ID.

[0069] Figure 2 This is a schematic diagram of the slice configuration and routing calculation process in an embodiment of this application, as shown below. Figure 2As shown, when configuring devices involved in a service, it is necessary to obtain the device's role in this configuration (such as source device, forwarding device, destination device, etc.) based on the acquired physical resource and logical resource related data, LLDP (Link Layer Discovery Protocol) topology information, and BGP-LS topology information. Different slice configuration commands are then generated based on these roles. The slice configuration commands are roughly divided into three modules: Slice ID, SRV6-TE-Policy, and L2EVPN / L3EVPN. L2EVPN / L3EVPN represents the service information, enabling the configuration of network slices to be associated with the target service.

[0070] When generating commands and configuring devices, Slice ID-related configurations need to be performed on all devices involved in the business. SRV6-TE-Policy and L2EVPN / L3EVPN only need to be configured on the source and destination devices. After allocating commands and variables, the SRv6-TE-Policy tunnel routing technology automatically performs route calculations and selections to achieve intelligent selection of the best quality path and issue slice configuration commands. The slice configuration commands are then sent to each device in the routing path. After receiving the slice configuration commands, each device can perform relevant configurations, configure the network slice instance corresponding to the Slice ID, and configure the network slice channel, associating the network slice instance and network slice channel according to the Slice ID.

[0071] Slice ID-based network slicing is a network slicing technology applied in SRv6 networking scenarios. Each network has a unique Slice ID, used to identify virtual logical networks and the physical bandwidth and other resources used by those logical networks. Furthermore, Slice ID-related information is encapsulated in IPv6 data packets, and devices forward packets carrying the Slice ID through the corresponding logical network.

[0072] Slice ID-based network slicing defines the following concepts: network slice instance, network slice channel, and network slice packet.

[0073] In all networks that have deployed SRv6 network slicing, a network slice instance represents an independent virtual network, and each virtual network is identified by a unique network slice instance ID, or Slice ID. The general attributes of this slice are defined by the network slice instance, such as the slice's description. Only after a network slice instance has been configured on the device can a physical device be mapped to the virtual slice network identified by that network slice instance ID.

[0074] A network slice channel is a logical channel on a device interface used to forward network slice packets. Network slice channels also need to be identified by a Slice ID and associated with a network slice instance. Multiple network slice channels can be created on each interface, and each network slice channel can be assigned an independent scheduling queue. The scheduling queues of different network slice channel interfaces do not affect each other.

[0075] Network slice packets are IPv6 packets transmitted within a network slice instance. The IPv6 header of a network slice packet carries a Slice ID to identify the network slice instance to which the packet belongs. In other words, network slice packets carrying Slice ID information will be forwarded using the network slice channel identified by the Slice ID.

[0076] A BGP (Border Gateway Protocol) IPv6 SR Policy peer is established between the controller (network element management system) and the forwarding devices. The controller then advertises the BGP IPv6 SR Policy routes to the forwarding devices, enabling the creation of SRv6 TE Policies on those devices. Therefore, in the control plane, the NLRI (Network Layer Reachability Information) of the BGP IPv6 SR Policy routes needs to be extended to support Sub-TLV (Sub-Type Length Value) carrying Slice ID information. Comware follows the draft-dong-idr-sr-policy-vtn-01 and uses the VTN (Virtual Transport Network) Sub-TLV defined therein to carry Slice ID information; hence, it can also be called Slice ID Sub-TLV. Comware carries the Slice ID Sub-TLV in BGP IPv6 SR Policy routes primarily by adding the Slice ID Sub-TLV to the Tunnel Encaps Attribute. Comware is an operating system developed based on Linux. It leverages Linux's open-source nature and powerful networking capabilities. By using the Linux kernel, this operating system can achieve high-performance network communication, including handling large amounts of network traffic and providing a variety of network services.

[0077] This application combines Slice ID-based network slicing with SRv6-TE-Policy tunneling to achieve intelligent selection of the best quality path. The specific working mechanism is as follows: In the SRv6 TE Policy scenario, to implement a Slice ID-based network slicing scheme, the SRv6 TE Policy routing path (including primary and alternative paths) needs to be associated with the Slice ID. When a source node needs to redirect traffic to the SRv6 TE Policy for forwarding, the device will, based on the Slice ID associated with the SRv6 TE Policy routing path, guide the traffic into the corresponding slice network for forwarding. During this process, there is no need to establish a mapping relationship between the Color extended community attribute of the BGP route and the Slice ID, because the traffic is directly redirected through the SRv6 TE Policy. Therefore, in the SRv6 TE Policy scenario, the Slice ID-based network slicing scheme does not require changes to the control plane's route learning process. This design makes the network slicing scheme more flexible and easier to implement.

[0078] In some embodiments of this application, the slice configuration information further includes a slice encapsulation method, which includes HBH (Hop-by-Hop, extended header) slice method or source address slice method. In the data forwarding plane, based on the difference in encapsulation method, Slice ID slices can be divided into the following two types: HBH slice carrying method, which uses the option field of the IPv6 Hop-by-Hop Extension Header to carry the Slice ID information; and source address slice carrying method, which uses the lower 32 bits of the IPv6 packet source address to carry the Slice ID information.

[0079] The embodiments of this application can be applied to power grid emergency response systems. Figure 3 This is a physical topology diagram of the power network slice in the embodiments of this application, such as... Figure 3 As shown, in the small-granularity slicing private network solution, the distribution network equipment without optical cable coverage includes: second-level load control, three-remote control, pole-mounted switches, etc. These distribution network equipment are connected to the unified management scenario of the power control center. The second-level load control is connected to the load control terminal cabinet through a router or 5G, while the three-remote control and pole-mounted switches are connected through 5G CPE (Customer Premise Equipment).

[0080] Second-level load control is a term in power systems, primarily referring to the rapid control of electrical loads. In a power system, a load refers to equipment or processes that consume electrical energy. To maintain the stable operation of the power system, load management and control are necessary. "Second-level" refers to the extremely short timescale of the control, which can be completed within seconds. Load control refers to reducing or limiting load consumption through control measures. Therefore, second-level load control typically refers to the rapid reduction or limitation of electrical load within a very short period of time.

[0081] The three remote technologies include remote signaling, remote measurement, and remote control. Remote signaling refers to using communication technology to monitor equipment status information, such as alarm status, switch position, or valve position. Remote measurement refers to using communication technology to transmit the measured values ​​of the measured variable. Remote control refers to using communication technology to issue commands to change the status of operating equipment. Remote measurement involves using communication technology to measure electrical parameters of substations, such as load, current, voltage, and power, from a remote location (e.g., a dispatch center). Remote signaling involves remote signal transmission; important warning signals from substations are directly displayed at the dispatch center via communication technology. Remote control involves remote control operations.

[0082] A pole-mounted switch is a type of safety switch used on utility poles to ensure electrical safety. Its main function is to isolate high voltage in the circuit.

[0083] Figure 4 This is a power slicing network topology diagram in an embodiment of this application, such as... Figure 3 and Figure 4 As shown, the power grid is divided into a safety production control area and a management information area. Therefore, the network isolation scheme is managed according to these two areas. For the safety production control area: (1) The wireless side uses RB (Resource Block) resource reservation to achieve hard isolation; (2) The transmission side is isolated by uRPSF slices (i.e., network slices based on Slice ID), and enters 2B FlexE for isolation on the B device; (3) On the core network side, each province / major city deploys a physically independent UPF for the production control area and divides logically independent UPF tenants to carry services. For the management information area: (1) The wireless side uses different 5QI (5G QoS Identifier) ​​priority scheduling to achieve logical isolation; (2) The transmission side uses VLANs to achieve logical isolation in different uRPSF slices; (3) The core network side management information area shares the operator's ToB dedicated UPF (User Plane Function), which is responsible for carrying the slice services of the third and fourth zones and is logically isolated from other ToB services. An additional N6 interface leased line to the power company is required. The Slice ID and SRv6 TE Policy in this application embodiment are mainly used on the transmission side.

[0084] This application's embodiments address remote control and transmission for power grid safety emergency response systems. Based on Slice-ID technology, it slices links in Mbps granularity for the numerous and scattered distributions within a customer network. This enables precise and intelligent control of each power-consuming unit while maximizing network resource conservation while meeting user needs. By combining Mbps small-granular slicing with SRv6-TE-Policy tunneling, it achieves intelligent selection of the optimal quality path. Specific functionalities are as follows: Slice ID-based network slicing divides the network into small-granular hard-isolated channels, ensuring network stability for users and preventing traffic congestion; based on the slices, network bandwidth is finely controlled, with a minimum bandwidth of 1Mbps for each slice network, allowing for a maximum of 6000 physical network slices to be divided, fully meeting existing service requirements; the Slice ID-based network slicing solution distinguishes different network slices by introducing Slice IDs into the data plane, completely decoupling data forwarding from control plane routing calculations. Furthermore, different slice networks can share a single SRv6 Locator, saving SRv6 Locator resources and reducing the pressure on control plane routing calculations.

[0085] The network configuration method provided in this application obtains slice configuration information between the source device and the destination device. The slice configuration information includes network slice ID, bandwidth information, segment routing traffic engineering policy, and target service identifier. A routing path between the source device and the destination device is generated based on the bandwidth information and the segment routing traffic engineering policy. A slice configuration command is generated based on the slice configuration information and the routing path, and the slice configuration command is sent to each device in the routing path. Each device can transmit the target service data corresponding to the target service identifier based on the network slice channel corresponding to the network slice ID. Since the isolated network slice is dedicated to the transmission of target service data, it is not affected by traffic congestion of other users, which can improve data transmission efficiency. Moreover, bandwidth information can be configured based on demand information, reducing the waste of bandwidth resources.

[0086] Figure 5 This is a flowchart of a data forwarding method provided in an embodiment of this application. This data forwarding method can be applied to source devices in a bearer network, such as... Figure 5 As shown, the method includes steps 510 to 550.

[0087] Step 510: Receive a slice configuration command, which includes a network slice ID and a routing path.

[0088] The source device receives a slice configuration command from the network element management system. This command includes the network slice ID and a routing path. The routing path can include a primary path and alternative paths. The routing path is generated by the network element management system based on the configured bandwidth information and routing traffic engineering policies; details can be found in the above embodiment and will not be repeated here.

[0089] Step 520: Configure the network slice instance and network slice channel corresponding to the network slice ID, and associate the network slice channel with the network slice instance according to the network slice ID.

[0090] The source device needs to configure an SRV6 TE Policy based on the slice configuration command. This involves configuring the outgoing interface of the target VPN instance corresponding to the target service identifier as the segment routing traffic engineering policy SRV6 TE Policy. It also needs to configure the network slice instance corresponding to the network slice ID, configure the network slice channel, and associate the network slice instance and the network slice channel based on the network slice ID to facilitate the subsequent forwarding of data packets through the network slice channel.

[0091] Step 530: When a data packet is received through the target VPN instance, the outgoing interface of the data packet is determined to be a segment routing traffic engineering policy according to the routing table of the target VPN instance. The target VPN instance is a VPN instance associated with the target service identifier.

[0092] When the source device receives a data packet based on the target VPN instance, it queries the routing table of the target VPN instance to determine that the outgoing interface of the data packet is SRV6 TE Policy. Then, it can add a Slice ID to the packet based on the configured slice encapsulation method.

[0093] Step 540: According to the configured slice encapsulation method, the data packet and network slice ID are encapsulated into an IPv6 packet.

[0094] The slice encapsulation method includes HBH (Hop-by-Hop, extended header) slice method or source address slice method. In the data forwarding plane, based on the difference in encapsulation method, there are two types of Slice ID slices: HBH slice carrying method, which uses the option field of the IPv6 Hop-by-Hop Extension Header to carry the Slice ID information; and source address slice carrying method, which uses the lower 32 bits of the IPv6 packet source address to carry the Slice ID information.

[0095] Based on the configured slice encapsulation method, a network slice ID is added to the IPv6 packet header to encapsulate the data packet into an IPv6 packet.

[0096] Step 550: Send the IPv6 packet to the next device through the network slice channel corresponding to the network slice ID.

[0097] The source device looks up the IPv6 FIB (Forwarding Information Base) table based on the destination address to determine the outgoing interface. Based on the network slice instance, it then sends the IPv6 packet to the next device through the network slice channel corresponding to the network slice ID on that outgoing interface. The forwarding mechanism varies slightly depending on the configured slice encapsulation method.

[0098] The data forwarding method provided in this application, after receiving a slice configuration command, configures a network slice instance and a network slice channel corresponding to the network slice instance ID, and associates the network slice channel and the network slice instance according to the network slice ID. When a data packet is received through the target VPN instance, the outgoing interface of the data packet is determined to be a segment routing traffic engineering policy according to the routing table of the target VPN instance. The data packet and the network slice ID are encapsulated into an IPv6 packet according to the configured slice encapsulation method, and the IPv6 packet is sent to the next device through the network slice channel corresponding to the network slice ID. By configuring the network slice instance and network slice channel corresponding to the network slice ID, the target service data can be transmitted based on the network slice channel corresponding to the network slice ID. Since the isolated network slice is dedicated to the transmission of target service data and is not affected by traffic congestion of other users, the data transmission efficiency can be improved. Moreover, the bandwidth information of the network slice can be configured based on the demand information, reducing the waste of bandwidth resources.

[0099] In some embodiments of this application, the configured slice encapsulation method includes the HBH slice method;

[0100] The step of encapsulating the data packet and network slice ID into an IPv6 packet according to the configured slice encapsulation method includes: encapsulating the data packet with a segment routing header, the segment routing header carrying a list of SIDs for segment routing traffic engineering policies; encapsulating the data packet with the segment routing header with an HBH extension header, the HBH extension header carrying the network slice ID; and encapsulating the data packet with the segment routing header and the HBH extension header with an IPv6 basic packet header to obtain the IPv6 packet.

[0101] The Segment Routing Header (SRH) is a mechanism that adds routing information to IPv6 packets, designed to improve the routing flexibility and programmability of network traffic. SRH can explicitly define a communication path as a series of "segments," each of which can be any network node or a combination of nodes. This flexibility allows SRH to support complex network topologies and easily adapt to changing traffic loads or network topology changes.

[0102] Based on the above technical solution, the step of sending the IPv6 packet to the next device through the network slice channel corresponding to the network slice ID includes: parsing the HBH extension header to obtain the network slice ID; and sending the IPv6 packet to the next device through the network slice channel corresponding to the network slice ID.

[0103] When forwarding IPv6 packets, the source device or intermediate device parses the information in the HBH extension header, obtains the SliceID value, and looks up the network slicing channel corresponding to the SliceID on the outgoing interface. Then, it forwards the IPv6 packets to the next device through the network slicing channel.

[0104] In some other embodiments of this application, the configured slice encapsulation method includes source address slice method;

[0105] The step of encapsulating the data packet and network slice ID into an IPv6 packet according to the configured slice encapsulation method includes: encapsulating the data packet with a segment routing header, carrying a list of SIDs for segment routing traffic engineering policies in the segment routing header; encapsulating the data packet with the segment routing header with an IPv6 basic packet header, and carrying the network slice ID in the source address in the IPv6 basic packet header to obtain the IPv6 packet.

[0106] Encapsulate the data packet with an SRH header and an IPv6 basic header, modify the source address in the IPv6 header to IPv6Prefix+Padding+Slice ID, and carry the Slice ID in the IPv6 header.

[0107] Based on the above technical solution, the step of sending the IPv6 packet to the next device through the network slice channel corresponding to the network slice ID includes: obtaining the network slice ID from the source address of the IPv6 basic packet header; and sending the IPv6 packet to the next device through the network slice channel corresponding to the network slice ID.

[0108] When a source device or intermediate device forwards an IPv6 packet, it analyzes the source address in the IPv6 basic packet header. If the high-order bits of the source address in the IPv6 packet header match the locally configured slice common prefix, it means that the packet needs to be forwarded through the network slice channel identified by the Slice ID. In this case, the Slice ID value can be obtained from the low 32 bits of the source address, and the corresponding network slice channel can be found on the outgoing interface based on the Slice ID. The IPv6 packet is then forwarded to the next device through this network slice channel.

[0109] Intermediate devices also need to configure the network slice instance and network slice channel corresponding to the network slice ID based on the slice configuration commands issued by the network element device management system, and associate the network slice channel with the network slice instance according to the network slice ID. When an intermediate device receives an IPv6 packet through a network slice channel and forwards the IPv6 packet, it looks up the corresponding network slice channel on the outgoing interface according to the network slice ID, and forwards the IPv6 packet through that network slice channel.

[0110] Figure 6 This is a flowchart of a data forwarding method provided in an embodiment of this application. This data forwarding method can be applied to source devices in a bearer network, such as... Figure 6 As shown, the method includes steps 610 to 640.

[0111] Step 610: Receive a slice configuration command, which includes a network slice ID and a routing path.

[0112] The destination device receives a slice configuration command from the network element management system. This command includes the network slice ID and routing path. The routing path can include a primary path and alternative paths. The routing path is generated by the network element management system based on configured bandwidth information and routing traffic engineering policies; details can be found in the above embodiment and will not be repeated here.

[0113] Step 620: Configure the network slice instance and network slice channel corresponding to the network slice ID, and associate the network slice channel with the network slice instance according to the network slice ID.

[0114] The destination device needs to configure an SRV6 TE Policy based on the slice configuration command, setting the current device as the tail node of the SRV6 TE Policy. It also needs to configure a network slice instance corresponding to the network slice ID, configure a network slice channel, and associate the network slice instance and network slice channel based on the network slice ID so that it can receive IPv6 packets through the network slice channel in the future.

[0115] Step 630: Receive IPv6 packets through the network slice channel corresponding to the network slice ID.

[0116] The destination device receives IPv6 packets forwarded by the previous device through the network slice channel corresponding to the network slice ID.

[0117] Step 640: Decapsulate the IPv6 packet, remove the IPv6 packet header to obtain the data packet, and forward the data packet to the user edge device corresponding to the target VPN instance.

[0118] After an IPv6 packet reaches the tail node of the SRV6 TE Policy (i.e., the destination device) through the network slicing channel, the destination device uses the destination address of the IPv6 packet to look up the local SID table. If a match is found, the device executes the action corresponding to the End SID: decrementing the packet's Segment Left (SL) by 1, updating the IPv6 destination address to End.DT4SID, and then looking up the local SID table based on End.DT4SID. The device then executes the forwarding action corresponding to End.DT4SID: decapsulating the packet, removing the IPv6 header, and matching the corresponding target VPN instance based on End.DT4SID. In the target VPN instance's routing table, the data packet is forwarded to the user edge device through a table lookup. The End SID identifies a specific destination node in the SRv6 network, and the actions corresponding to the End SID are: updating the IPv6 destination IP address and looking up the IPv6 routing table for packet forwarding. The End.DT4 SID is used to identify IPv4 VPN instances in the network. The corresponding forwarding action is to decapsulate the packet and look up the IPv4 VPN instance routing table for forwarding.

[0119] The data forwarding method provided in this application, upon receiving a slice configuration command, configures a network slice instance and a network slice channel corresponding to the network slice ID, associates the network slice channel and the network slice instance according to the network slice ID, receives IPv6 packets through the network slice channel corresponding to the network slice ID, decapsulates the IPv6 packets, removes the IPv6 packet header to obtain the data packets, and forwards the data packets to the user edge device corresponding to the target VPN instance. By configuring the network slice instance and network slice channel corresponding to the network slice ID, target service data can be transmitted based on the network slice channel corresponding to the network slice ID. Since the isolated network slice is dedicated to the transmission of target service data and is not affected by traffic congestion of other users, data transmission efficiency can be improved. Moreover, the bandwidth information of the network slice can be configured based on demand information, reducing the waste of bandwidth resources.

[0120] Figure 7 This is an example diagram of network slice packet forwarding in the SRv6 TE Policy data plane in this application embodiment, such as... Figure 7 As shown, network slice instance 1 and network slice instance 2 exist in the SRv6 network. Meanwhile, network slice channel 1 and network slice channel 2, associated with network slice instance 1 and instance 2, are configured on the forwarding interfaces of PE 1 (source device), P (intermediate device), and PE 2 (destination device), respectively. When traffic between two sites CE1 and CE2 in the target VPN instance VPN A needs to be forwarded through the SRv6 TE Policy tunnel, this policy is associated with network slice instance 1. The following is the specific forwarding process of CE1 sending packets to CE2:

[0121] (1) CE 1 sends an IPv4 unicast packet to PE 1. After receiving this packet, PE 1 will consult the routing table of VPN instance A to determine that the outgoing interface of the packet is SRv6 TE Policy. Then, according to the configured slice encapsulation method, PE 1 will begin adding Slice ID information to the IPv6 packet:

[0122] The Slice ID is encapsulated using the HBH slicing method: encapsulates the SRH header, which carries the SIDList of the SRv6TE Policy; encapsulates the HBH extension header, which carries the ID of the network slice instance associated with the candidate path selected by the SRv6 TE Policy (in this example, the Slice ID field is set to 1); and encapsulates the IPv6 basic packet header. Figure 7 The HBH slicing method is used to encapsulate Slice IDs as an example.

[0123] The Slice ID is encapsulated using source address slicing: An SRH header is encapsulated, carrying the SID List of the SRv6TE Policy; an IPv6 basic header is encapsulated, modifying the source address in the IPv6 header to IPv6 Prefix + Padding + Slice ID. In this example, the IPv6 Prefix configured on PE 1 is 2001:1000:A::, with a length of 64, and the Slice ID is 1. Therefore, the source address is 2001:1000:A::1, and this packet needs to be forwarded through the slice network with Slice ID 1.

[0124] (2) PE 1 looks up the IPv6 FIB table based on the destination address. Its outgoing interface is the interface between PE 1 and P. During forwarding, the processing mechanism of PE 1 varies slightly depending on the configured slice encapsulation method:

[0125] The HBH slicing method is used to encapsulate the Slice ID: PE 1 parses the information in the HBH header, obtains the Slice ID value, finds the corresponding network slice channel on the outgoing interface, and forwards the packet to P through the network slice channel.

[0126] The Slice ID is encapsulated using source address slicing: PE 1 analyzes the source address in the IPv6 header. If the high-order bits of the source address in the IPv6 header match the locally configured slice common prefix, it indicates that the packet needs to be forwarded through the network slice channel identified by the Slice ID. PE 1 obtains the Slice ID value from the low 32 bits of the source address and finds the corresponding network slice channel on the outgoing interface based on the Slice ID information. The packet is then forwarded to P through this network slice channel.

[0127] (3) The intermediate P device repeats the processing flow in step (2). When forwarding, it searches for the network slice channel corresponding to the Slice ID on the outgoing interface and forwards the packet through the network slice channel.

[0128] (4) After the packet arrives at the tail node PE 2, PE 2 uses the packet's IPv6 destination address to look up the Local SID table. If it can match the End SID, PE 2 decrements the packet's SL by 1 and updates the IPv6 destination address to End.DT4 SID. PE 2 looks up the Local SID table based on End.DT4 SID and performs the forwarding action corresponding to End.DT4 SID, that is, decapsulates the packet, removes the IPv6 packet header, and matches VPN A based on End.DT4 SID. In VPN A's routing table, it forwards the packet to CE 2 by looking up the table.

[0129] This application adapts Slice ID slicing technology to the power grid emergency response system, enabling the automatic generation of complex service parameters, automatic service distribution, and automatic discovery of services and network topology through the network element device management system. By combining Slice ID slicing service configuration with the SRv6-TE-Policy tunnel routing and optimization mechanism, when configuring slicing services, the routing paths of the SRv6 TE Policy (i.e., each candidate path, including the primary path and alternative paths) are associated with the Slice ID, automatically obtaining the current network performance and selecting the optimal path.

[0130] This application combines 5G small-granularity slicing (Mbps level) with SRv6-TE-Policy intelligent routing, solving the problems of resource waste (minimum 1Gbps) and insufficient isolation of MPLS VPN in traditional FlexE slicing. Through the dual encapsulation mode of Slice ID (HBH extension header / source address embedding), it is compatible with the forwarding capabilities of different devices and avoids the limitations of the single identification method in the prior art. Through BGP-LS topology awareness and automatic generation of service parameters, it realizes full-process automation of slicing policy, which is different from the defects of existing technologies that rely on manual policy configuration.

[0131] This application's embodiments, based on Mbps-level slicing, enable a single physical network to support 6000 independent slices, significantly improving resource utilization compared to FlexE technology and adapting to the needs of massive, dispersed nodes at the end of the power grid. Through intelligent binding of SRv6-TE-Policy and Slice ID, latency of critical service paths is reduced, meeting the power grid's second-level response requirements. Based on Slice ID hard slicing technology, physical isolation of each service channel is ensured, and combined with slice-level encryption strategies, cross-slice attacks are prevented, resulting in significantly improved security compared to VxLAN / QoS solutions.

[0132] Figure 8 This is a schematic diagram of the structure of a network configuration device provided in an embodiment of this application, as shown below. Figure 8 As shown, the device includes:

[0133] The configuration information acquisition module 810 is used to acquire slice configuration information between the source device and the destination device. The slice configuration information includes network slice ID, bandwidth information, segment routing traffic engineering policy and target service identifier.

[0134] The path generation module 820 is used to generate a routing path between the source device and the destination device based on the bandwidth information and the segment routing traffic engineering strategy.

[0135] The configuration command distribution module 830 is used to generate a slice configuration command based on the slice configuration information and the routing path, and distribute the slice configuration command to each device in the routing path. The slice configuration command is used to instruct each device to transmit the target service data corresponding to the target service identifier according to the network slice channel corresponding to the network slice ID.

[0136] Optionally, the path generation module is specifically used for:

[0137] Based on the bandwidth information and the segment routing traffic engineering strategy, a primary path and alternative paths are generated between the source device and the destination device, and the primary path and the alternative paths are used as the routing paths.

[0138] Optionally, the slice configuration information may also include a slice encapsulation method, which may include HBH slice method or source address slice method.

[0139] The network configuration apparatus provided in this application embodiment is used to implement the steps of the network configuration method described in this application embodiment. The specific implementation of each module of the apparatus is described in the corresponding steps, and will not be repeated here.

[0140] The network configuration device provided in this application obtains slice configuration information between the source device and the destination device. The slice configuration information includes network slice ID, bandwidth information, segment routing traffic engineering policy, and target service identifier. Based on the bandwidth information and segment routing traffic engineering policy, a routing path is generated between the source device and the destination device. Based on the slice configuration information and the routing path, a slice configuration command is generated and sent to each device in the routing path. Each device can transmit target service data corresponding to the target service identifier based on the network slice channel corresponding to the network slice ID. Since the isolated network slice is dedicated to the transmission of target service data and is not affected by traffic congestion of other users, data transmission efficiency can be improved. Moreover, bandwidth information can be configured based on demand information, reducing the waste of bandwidth resources.

[0141] Figure 9 This is a schematic diagram of a data forwarding device provided in an embodiment of this application. This data forwarding device is applied to a source device, such as... Figure 9 As shown, the device includes:

[0142] The configuration command receiving module 910 is used to receive slice configuration commands, the slice configuration commands including network slice ID and routing path;

[0143] The slice configuration module 920 is used to configure the network slice instance and network slice channel corresponding to the network slice ID, and associate the network slice channel with the network slice instance according to the network slice ID;

[0144] The packet outgoing interface determination module 930 is used to determine, when a data packet is received through a target VPN instance, the outgoing interface of the data packet is a segment routing traffic engineering policy according to the routing table of the target VPN instance, wherein the target VPN instance is a VPN instance associated with a target service identifier;

[0145] The message encapsulation module 940 is used to encapsulate the data packet and network slice ID into an IPv6 packet according to the configured slice encapsulation method;

[0146] The packet forwarding module 950 is used to send the IPv6 packet to the next device through the network slice channel corresponding to the network slice ID.

[0147] Optionally, the configured slice encapsulation method includes the HBH slice method;

[0148] The message encapsulation module is specifically used for:

[0149] The data packet is encapsulated with a segmented routing header, which carries a list of SIDs for segmented routing traffic engineering policies.

[0150] Encapsulate the data packet containing the segmented routing header with an HBH extension header, and carry the network slice ID in the HBH extension header;

[0151] The data packet containing the segmented routing header and the HBH extension header is encapsulated with an IPv6 basic header to obtain the IPv6 packet.

[0152] Optionally, the message forwarding module is specifically used for:

[0153] Parse the HBH extension header to obtain the network slice ID;

[0154] The IPv6 packet is sent to the next device through the network slice channel corresponding to the network slice ID.

[0155] Optionally, the configured slice encapsulation method includes source address slice method;

[0156] The message encapsulation module is specifically used for:

[0157] The data packet is encapsulated with a segmented routing header, which carries a list of SIDs for segmented routing traffic engineering policies.

[0158] The data packet encapsulating the segmented routing header is encapsulated with an IPv6 basic packet header, and the network slice ID is carried in the source address in the IPv6 basic packet header to obtain the IPv6 packet.

[0159] Optionally, the message forwarding module is specifically used for:

[0160] Obtain the network slice ID from the source address of the IPv6 basic packet header;

[0161] The IPv6 packet is sent to the next device through the network slice channel corresponding to the network slice ID.

[0162] The data forwarding apparatus provided in this application embodiment is used to implement the steps of the data forwarding method described in this application embodiment. The specific implementation of each module of the apparatus is described in the corresponding steps, and will not be repeated here.

[0163] The data forwarding device provided in this application, after receiving a slice configuration command, configures a network slice instance and a network slice channel corresponding to the network slice instance ID, and associates the network slice channel and the network slice instance according to the network slice ID. When a data packet is received through the target VPN instance, the device determines the outgoing interface of the data packet as a segment routing traffic engineering policy according to the routing table of the target VPN instance. The device encapsulates the data packet and the network slice ID into an IPv6 packet according to the configured slice encapsulation method, and sends the IPv6 packet to the next device through the network slice channel corresponding to the network slice ID. By configuring the network slice instance and network slice channel corresponding to the network slice ID, the target service data can be transmitted based on the network slice channel corresponding to the network slice ID. Since the isolated network slice is dedicated to the transmission of target service data and is not affected by traffic congestion of other users, the data transmission efficiency can be improved. Moreover, the bandwidth information of the network slice can be configured based on the demand information, reducing the waste of bandwidth resources.

[0164] Figure 10 This is a schematic diagram of a data forwarding device provided in an embodiment of this application. This data forwarding device is applied to a destination device, such as... Figure 10 As shown, the device includes:

[0165] The configuration command receiving module 1010 is used to receive slice configuration commands, the slice configuration commands including network slice ID and routing path;

[0166] The slice configuration module 1020 is used to configure the network slice instance and network slice channel corresponding to the network slice ID, and associate the network slice channel with the network slice instance according to the network slice ID;

[0167] The message receiving module 1030 is used to receive IPv6 messages through the network slice channel corresponding to the network slice ID;

[0168] The packet forwarding module 1040 is used to decapsulate the IPv6 packet, remove the IPv6 packet header to obtain the data packet, and forward the data packet to the user edge device corresponding to the target VPN instance.

[0169] The data forwarding apparatus provided in this application embodiment is used to implement the steps of the data forwarding method described in this application embodiment. The specific implementation of each module of the apparatus is described in the corresponding steps, and will not be repeated here.

[0170] The data forwarding device provided in this application, upon receiving a slice configuration command, configures a network slice instance and a network slice channel corresponding to the network slice ID, associates the network slice channel and the network slice instance according to the network slice ID, receives IPv6 packets through the network slice channel corresponding to the network slice ID, decapsulates the IPv6 packets, removes the IPv6 packet header to obtain data packets, and forwards the data packets to the user edge device corresponding to the target VPN instance. By configuring the network slice instance and network slice channel corresponding to the network slice ID, target service data can be transmitted based on the network slice channel corresponding to the network slice ID. Since the isolated network slice is dedicated to the transmission of target service data and is not affected by traffic congestion of other users, data transmission efficiency can be improved. Moreover, the bandwidth information of the network slice can be configured based on demand information, reducing the waste of bandwidth resources.

[0171] Figure 11 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application, such as... Figure 11 As shown, the electronic device 1100 may include one or more processors 1110 and one or more memories 1120 connected to the processors 1110. The electronic device 1100 may also include an input interface 1130 and an output interface 1140 for communicating with another device or system. Program code executed by the processor 1110 may be stored in the memory 1120.

[0172] The processor 1110 in the electronic device 1100 calls the program code stored in the memory 1120 to execute the network configuration method or data forwarding method in the above embodiments.

[0173] This application also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the network configuration method or data forwarding method as described in this application.

[0174] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the network configuration method or data forwarding method as described in this application embodiment.

[0175] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the apparatus embodiments, since they are fundamentally similar to the method embodiments, the description is relatively simple; relevant parts can be referred to the descriptions in the method embodiments.

[0176] The foregoing has provided a detailed description of a network configuration method, data forwarding method, apparatus, device, and storage medium provided in the embodiments of this application. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the embodiments above are only for the purpose of helping to understand the methods and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.

[0177] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

Claims

1. A network configuration method, characterized in that, include: Obtain slice configuration information between the source device and the destination device. The slice configuration information includes network slice ID, bandwidth information, segment routing traffic engineering policy, and target service identifier. Based on the bandwidth information and the segment routing traffic engineering strategy, a routing path is generated between the source device and the destination device; Based on the slice configuration information and the routing path, a slice configuration command is generated and sent to each device in the routing path. The slice configuration command is used to instruct each device to transmit the target service data corresponding to the target service identifier according to the network slice channel corresponding to the network slice ID.

2. The method according to claim 1, characterized in that, The step of generating a routing path between the source device and the destination device based on the bandwidth information and the segment routing traffic engineering strategy includes: Based on the bandwidth information and the segment routing traffic engineering strategy, a primary path and alternative paths are generated between the source device and the destination device, and the primary path and the alternative paths are used as the routing paths.

3. The method according to claim 1, characterized in that, The slice configuration information also includes the slice encapsulation method, which includes either the extended header HBH slice method or the source address slice method.

4. A data forwarding method, characterized in that, Applied to source-end devices, including: Receive a slice configuration command, the slice configuration command including network slice ID and routing path; Configure a network slice instance and a network slice channel corresponding to the network slice ID, and associate the network slice channel with the network slice instance based on the network slice ID; When a data packet is received through the target VPN instance, the outgoing interface of the data packet is determined to be the segment routing traffic engineering policy according to the routing table of the target VPN instance. The target VPN instance is a VPN instance associated with the target service identifier. According to the configured slice encapsulation method, the data packet and network slice ID are encapsulated into an IPv6 packet; The IPv6 packet is sent to the next device through the network slice channel corresponding to the network slice ID.

5. The method according to claim 4, characterized in that, The configured slice packaging method includes the HBH slice method; The step of encapsulating the data packet and network slice ID into an IPv6 packet according to the configured slice encapsulation method includes: The data packet is encapsulated with a segmented routing header, which carries a list of SIDs for segmented routing traffic engineering policies. Encapsulate the data packet containing the segmented routing header with an HBH extension header, and carry the network slice ID in the HBH extension header; The data packet containing the segmented routing header and the HBH extension header is encapsulated with an IPv6 basic header to obtain the IPv6 packet.

6. The method according to claim 5, characterized in that, Sending the IPv6 packet to the next device through the network slice channel corresponding to the network slice ID includes: Parse the HBH extension header to obtain the network slice ID; The IPv6 packet is sent to the next device through the network slice channel corresponding to the network slice ID.

7. The method according to claim 4, characterized in that, The configured slice encapsulation method includes source address slice method; The step of encapsulating the data packet and network slice ID into an IPv6 packet according to the configured slice encapsulation method includes: The data packet is encapsulated with a segmented routing header, which carries a list of SIDs for segmented routing traffic engineering policies. The data packet encapsulating the segmented routing header is encapsulated with an IPv6 basic packet header, and the network slice ID is carried in the source address in the IPv6 basic packet header to obtain the IPv6 packet.

8. The method according to claim 7, characterized in that, Sending the IPv6 packet to the next device through the network slice channel corresponding to the network slice ID includes: Obtain the network slice ID from the source address of the IPv6 basic packet header; The IPv6 packet is sent to the next device through the network slice channel corresponding to the network slice ID.

9. A data forwarding method, characterized in that, Applied to terminal equipment, including: Receive a slice configuration command, the slice configuration command including network slice ID and routing path; Configure a network slice instance and a network slice channel corresponding to the network slice ID, and associate the network slice channel with the network slice instance based on the network slice ID; Receive IPv6 packets through the network slice channel corresponding to the network slice ID; The IPv6 packet is decapsulated, the IPv6 packet header is removed to obtain the data packet, and the data packet is forwarded to the user edge device corresponding to the target VPN instance.

10. A network configuration device, characterized in that, include: The configuration information acquisition module is used to acquire slice configuration information between the source device and the destination device. The slice configuration information includes network slice ID, bandwidth information, segment routing traffic engineering policy and target service identifier. The path generation module is used to generate a routing path between the source device and the destination device based on the bandwidth information and the segment routing traffic engineering strategy. The configuration command distribution module is used to generate a slice configuration command based on the slice configuration information and the routing path, and to distribute the slice configuration command to each device in the routing path. The slice configuration command is used to instruct each device to transmit the target service data corresponding to the target service identifier according to the network slice channel corresponding to the network slice ID.

11. A data forwarding device, characterized in that, Applied to source-end devices, including: A configuration command receiving module is used to receive slice configuration commands, which include network slice ID and routing path; The slice configuration module is used to configure the network slice instance and network slice channel corresponding to the network slice ID, and associate the network slice channel with the network slice instance according to the network slice ID; The message outgoing interface determination module is used to determine, when a data packet is received through a target VPN instance, the outgoing interface of the data packet is a segment routing traffic engineering policy based on the routing table of the target VPN instance, wherein the target VPN instance is a VPN instance associated with a target service identifier; The message encapsulation module is used to encapsulate the data packet and network slice ID into an IPv6 packet according to the configured slice encapsulation method; The packet forwarding module is used to send the IPv6 packet to the next device through the network slice channel corresponding to the network slice ID.

12. A data forwarding device, characterized in that, Applied to terminal equipment, including: A configuration command receiving module is used to receive slice configuration commands, which include network slice ID and routing path; The slice configuration module is used to configure the network slice instance and network slice channel corresponding to the network slice ID, and associate the network slice channel with the network slice instance according to the network slice ID; The message receiving module is used to receive IPv6 messages through the network slice channel corresponding to the network slice ID; The packet forwarding module is used to decapsulate the IPv6 packet, remove the IPv6 packet header to obtain the data packet, and forward the data packet to the user edge device corresponding to the target VPN instance.

13. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the network configuration method according to any one of claims 1 to 3, or the data forwarding method according to any one of claims 4 to 8, or the data forwarding method according to claim 9.

14. A computer-readable storage medium having a computer program stored thereon, characterized in that, When executed by a processor, the program implements the network configuration method according to any one of claims 1 to 3, or the data forwarding method according to any one of claims 4 to 8, or the data forwarding method according to claim 9.

Images