CN115277548A - A transmission method, device and storage medium - Google Patents

Abstract

The invention discloses a transmission method, a transmission device and a storage medium, wherein the transmission method comprises the following steps: the SDN controller divides a link corresponding to each network equipment interface into a plurality of sub-link resources according to the resource requirements of slice users; establishing a corresponding relation between slice identification SliceID and resource requirements; and establishing a one-to-one binding source routing technology strategy SRv6Policy tunnel based on IPv6 for the user according to the resource requirement of the slice user, and establishing a corresponding relation between the slice identification SliceID and the SRv6Policy tunnel. When providing services for the slice user, the forwarding equipment guides the service flow to the SRv6Policy tunnel for transmission; and establishing a corresponding relation between the SliceID and each interface sublink resource on an SRv6Policy tunnel path. By adopting the method and the device, the requirement of one-level slicing for exclusive sharing of the bottom physical resources with the granularity of the sub-link can be met, and the requirement of two-level slicing for exclusive sharing of the bottom physical resources with the granularity of the sub-link of the industry or virtual operator slicing and the user slicing can also be met.

Description

A transmission method, device and storage medium

technical field

The present invention relates to the field of communication technology, in particular to a transmission method, device and storage medium.

Background technique

Existing slicing technologies for data bearing include FlexAlgo (flexible algorithm) technology, SR-TE (Segment Routing-Traffic Engineering), SRv6 Policy (SRv6 policy; SRv6: IPv6-based source routing technology, Segment Routing IPv6 ) tunnel technology.

1. The following is a brief description of the FlexAlgo (referred to as FA) technology.

FA is based on the IGP (Interior Gateway Protocol) single topology. Each node and each L3 link corresponds to one or more FA algorithm spaces, which are released by the IGP protocol to form an IGP sub-calculation path space.

The FA algorithm includes three parts: MetricType (measurement type), CalcType (calculation type) and Constraint (constraint). The results of different FA algorithms are different sub-topologies. Therefore, through FlexAlgo, the physical network can be divided into multiple virtual networks. Under different FA slices, different SIDs (SegmentIDentifier) are used for packet encapsulation, and different addresses are calculated independently to guide the forwarding of packets in the corresponding FA slices.

Figure 1 is a schematic diagram of the physical networking topology of the device, and Figure 2 is a schematic diagram of the sub-topology of different FA slices. Added to different FAs, different physical links are added to different FlexAlgos by setting the color (color) attribute to match the path calculation constraints of different FAs (such as affinity attributes, including a certain color). In each FA slice, each node is assigned an independent SID. The different FA slice subtopologies formed are shown in Figure 2:

Automatic service diversion: By carrying the FA-ID when announcing the prefix SID (prefix SID), it means that a specific FA algorithm needs to be used to calculate the prefix for this purpose. The service can find the corresponding FA-LSP (The Liskov Substitution Principle) based on the FA-based single prefix SID or specific SR (Segment Routing, Segment Routing) list.

2. The following is a brief description of SR-TE and SRv6 Policy technologies.

SR-TE and SRv6 Policy itself is a source routing tunnel technology, which can calculate a path that meets the needs of the user in the network based on the user's SLA (Service-Level Agreement, Service-Level Agreement) requirements, such as delay and bandwidth. Segmentlist<SID1, SID2, ... SIDn>, instructs user packets to be forwarded in the network along the specified path.

The tunnel path Segmentlist (segment list) can be arranged by node SID or adjacent SID. When the SID of each hop in the path uses an adjacent SID, the tunnel path is a strict path, and each hop is specified; when some SIDs in the path use node SIDs, the tunnel path is a loose one-hop path path, because there may be different reachable links between two nodes.

1. The deficiencies of FlexAlgo slicing technology lie in:

FlexAlgo technology can only guarantee node selection and physical link selection, and realize coarse-grained slicing at the physical port level. However, in the current network, there is no guarantee that there are multiple links between all nodes, so end-to-end slicing cannot be guaranteed. Exclusive sharing of resources, and in this scheme, slice users can only exclusively share a certain physical link, and it is impossible to allocate multiple sub-link resources to different slice users. Therefore, it will cause a huge resource consumption for scenarios that require physical isolation of slices. Waste, basically useless.

2. The disadvantages of SR-TE and SRv6 Policy technology for slicing are:

The path planning problem solved by SR-TE and SRv6 Policy guides packets to avoid congested roads and forward along specified paths, but the resources on each physical link on the forwarding path, such as bandwidth, cannot be guaranteed. Because the link resources are still shared by all tunnels, they cannot be associated with the underlying sub-link physical resources, and only achieve logical isolation, which cannot meet the hard slicing requirements of exclusive resources required by users.

Therefore, the disadvantage of the prior art is that there is no slicing scheme that can associate the physical resources of the underlying sub-links.

Contents of the invention

The present invention provides a transmission method, device and storage medium to solve the problem that there is no slicing scheme that can be associated with the physical resources of the underlying sub-links.

The invention provides the following technical solutions:

A method of transmission comprising:

The software-defined network SDN controller divides the link corresponding to each network device interface into multiple sub-link resources according to the slice user resource requirements;

Establish the corresponding relationship between the slice identifier SliceID and resource requirements;

According to the resource requirements of the slice user, establish a one-to-one binding IPv6-based source routing technology policy SRv6 Policy tunnel for the user, and establish a corresponding relationship between the slice identifier SliceID and the SRv6 Policy tunnel.

In implementation, it further includes:

A slice user is a user in the flexible algorithm FA slice based on the flexible algorithm FlexAlgo;

SliceID is the SliceID in the FlexAlgo-based FA slice to which the slice user belongs;

The SRv6 Policy tunnel is a tunnel in the FlexAlgo-based FA slice topology to which the slice user belongs.

In implementation, it further includes:

Establishing the correspondence between the slice identifier SliceID and the SRv6 Policy tunnel is to assign a slice identifier SliceID that can meet the slice user resource requirements for the SRv6 Policy tunnel.

In implementation, it further includes:

The sub-link identifier Sub-Link Num is used to identify sub-link resources. Each sub-link has its own exclusive underlying physical resources. By saving and maintaining the correspondence between Sub-Link Num and various types of sub-link resource IDs, Compatible with various types of underlying physical sub-link resources.

In implementation, it further includes:

IPv6-based source routing technical capability subtype, length, value SRv6 Capabilities sub-TLV of routing capability type, length, value Router CAPABILITY TLV and IPv6-based source routing technical capability type of Border Gateway Protocol link type BGP-LS, Length and value SRv6 Capability TLV adds flags to indicate that the device supports the ability to carry SliceID on the forwarding plane and perform slice processing.

In implementation, it further includes:

Add an identifier to the end segment identifier subtype, length, and value End.X SID sub-TLV structure to indicate that the device is an adjacent SID of a virtual member sublink, not an adjacent SID of a physical link.

In implementation, it further includes:

Use the link slice information subtype, length, value Sub-TLV and slice resource subtype, length, value Sub-sub-TLV structure to announce the number of link slices and corresponding resource information.

In implementation, one or a combination of the following processing is further included:

When assigning the number of SliceIDs, after assigning a preset number of SliceIDs to each FA slice on the SDN controller, send them to the device;

According to the needs of slice users in the FA slice topology, the SDN controller allocates SliceID resources on the forwarding plane for each user, and establishes the corresponding relationship between the SliceID and the resource requirements of each slice user. The unallocated SliceID is temporarily reserved and has no resource requirements;

SliceIDs that have not been assigned bandwidth requirements are updated according to the bandwidth requirements of subsequent new slice users, and the updated information is sent to the device synchronously.

In implementation, it further includes:

The SDN controller maintains and/or updates the following information:

FA slice SliceID, virtual member sub-link End.X SID, total reserved resources of virtual member sub-link End.X SID, corresponding relationship of The total remaining slice resources of the link.

In implementation, it further includes:

The SliceID information of the forwarding plane is carried in the BGP SRv6 Policy message.

In implementation, it further includes:

Configure the mapping relationship between the Color template and the SliceID on the forwarding plane, so that the tunnel head node device can obtain the corresponding SliceID according to the Color attribute of the SRv6Policy.

In implementation, it further includes:

The SDN controller performs path calculation based on the SliceID information, the FA topology, and the remaining slice resource information of the virtual member sub-link End.X corresponding to the FA topology, and uses the virtual member sub-link End.XSID to perform path arrangement.

In the implementation, when the slice user traffic is directed to the SRv6 Policy tunnel for transmission, the forwarding device determines the slice sub- link physical resource, and forward the message through the corresponding sub-link physical resource sub-interface.

During implementation, when guiding slice user traffic to the SRv6 Policy tunnel for transmission, the SDN controller updates one or a combination of the following information according to the information reported by the device: The corresponding relationship between sub-link resources, Sub-Link Num status, and virtual member sub-link remaining slice resource information.

In implementation, it further includes:

By dividing the value space of the sub-link resource identifiers, it is used to distinguish the sub-link resource identifiers used by the FA slice and the user slice.

During the implementation, when dividing the value space of the sub-link resource identifier, the sub-link resource corresponding to the Sub-Link Num whose upper 4 bits are 1 is allocated to the FA slice, and the rest of the Sub-Link Num value space is allocated to the user sliced to use.

In implementation, it further includes:

In each FA slice topology, the remaining bandwidth resources not allocated to user slices in the reserved total bandwidth are shared by non-slice users in the FA slice topology, and the traffic of non-slice users is carried by SRv6 BE.

During implementation, the FA slice is based on the number of industries or virtual operators, and the network is divided into a corresponding number of FA slices based on FlexAlgo that have a one-to-one correspondence;

The SDN controller determines the FlexAlgo-based FA slice to which the slice user belongs according to the industry or virtual operator to which it belongs.

A method of transmission comprising:

When the forwarding device provides services for the users of the slice, it directs its service traffic to the SRv6 Policy tunnel for transmission;

On the SRv6 Policy tunnel path, establish the correspondence between the SliceID and the sublink resources of each interface.

In implementation, it further includes:

One or a combination of the following information is flooded in the IGP: the End.X SID of each FA slice virtual member sub-link on the link, the total reserved bandwidth, the number of SliceIDs, or the resource information corresponding to each SliceID.

In implementation, it further includes:

Make the tunnel head node device obtain the SliceID from the BGP SRv6 Policy message sent by the SDN controller, and write it into the corresponding position of the forwarding plane message.

During implementation, when the forwarding device guides slice user traffic to the SRv6 Policy tunnel for transmission, according to the SliceID carried in the forwarding packet of the slice user, it allocates a sub-link resource that can meet the SliceID resource requirement from the idle state sub-link resources of the corresponding physical outbound interface. The sub-link resource is forwarded, and the corresponding relationship between the SliceID and the sub-link resource and the state of the sub-link resource are maintained.

During implementation, when the forwarding device directs slice user traffic to the SRv6 Policy tunnel for transmission, when the first slice packet arrives at the device, the device checks the local table to obtain the bandwidth resource required by the SliceID according to the SliceID carried in the forwarded packet, and then Find the sub-link resource Sub-Link Num of unoccupied bandwidth from the sub-link resource table of the local device, assign it to the SliceID, forward the slice user packets from the corresponding sub-port, and update the local sub-link The status of the resource Sub-Link Num is occupied, and one or a combination of the following information is reported to the SDN controller through telemetry: Sub-link resource Sub-Link Num occupancy, SliceID and Sub-Link Num correspondence, Sub-Link LinkNum state.

A network device comprising:

The processor, which reads the program in the memory, performs the following processes:

Divide the link corresponding to each network device interface into multiple sub-link resources according to the user resource requirements of the slice;

Establish the corresponding relationship between the slice identifier SliceID and resource requirements;

According to the resource requirements of the slice user, establish a one-to-one binding IPv6-based source routing technology policy SRv6 Policy tunnel for the user, and establish a corresponding relationship between the slice identifier SliceID and the SRv6 Policy tunnel;

Transceiver, used to receive and transmit data under the control of the processor.

In implementation, it further includes:

A slice user is a user in the flexible algorithm FA slice based on the flexible algorithm FlexAlgo;

SliceID is the SliceID in the FlexAlgo-based FA slice to which the slice user belongs;

The SRv6 Policy tunnel is a tunnel in the FlexAlgo-based FA slice topology to which the slice user belongs.

In implementation, it further includes:

Establishing the correspondence between the slice identifier SliceID and the SRv6 Policy tunnel is to assign a slice identifier SliceID that can meet the slice user resource requirements for the SRv6 Policy tunnel.

In implementation, it further includes:

The sub-link identifier Sub-Link Num is used to identify sub-link resources. Each sub-link has its own exclusive underlying physical resources. By saving and maintaining the correspondence between Sub-Link Num and various types of sub-link resource IDs, Compatible with various types of underlying physical sub-link resources.

In implementation, it further includes:

IPv6-based source routing technical capability subtype, length, value SRv6 Capabilities sub-TLV of routing capability type, length, value Router CAPABILITY TLV and IPv6-based source routing technical capability type of Border Gateway Protocol link type BGP-LS, Length and value SRv6 Capability TLV adds flags to indicate that the device supports the ability to carry SliceID on the forwarding plane and perform slice processing.

In implementation, it further includes:

Add an identifier to the end segment identifier subtype, length, and value End.X SID sub-TLV structure to indicate that the device is an adjacent SID of a virtual member sublink, not an adjacent SID of a physical link.

In implementation, it further includes:

Use the link slice information subtype, length, value Sub-TLV and slice resource subtype, length, value Sub-sub-TLV structure to announce the number of link slices and corresponding resource information.

In implementation, one or a combination of the following processing is further included:

When assigning the number of SliceIDs, after assigning a preset number of SliceIDs to each FA slice on the SDN controller, send them to the device;

According to the needs of slice users in the FA slice topology, assign SliceID resources on the forwarding plane to each user, and establish the corresponding relationship between SliceID and the resource requirements of each slice user. Unallocated SliceIDs are temporarily reserved and have no resource requirements;

SliceIDs that have not been assigned bandwidth requirements are updated according to the bandwidth requirements of subsequent new slice users, and the updated information is sent to the device synchronously.

In implementation, it further includes:

To maintain and/or update the following information:

FA slice SliceID, virtual member sub-link End.X SID, total reserved resources of virtual member sub-link End.X SID, corresponding relationship of The total remaining slice resources of the link.

In implementation, it further includes:

The SliceID information of the forwarding plane is carried in the BGP SRv6 Policy message.

In implementation, it further includes:

Configure the mapping relationship between the Color template and the SliceID on the forwarding plane, so that the tunnel head node device can obtain the corresponding SliceID according to the Color attribute of the SRv6Policy.

In implementation, it further includes:

Path calculation is performed based on SliceID information, FA topology, and remaining slice resource information of the virtual member sub-link End.X corresponding to the FA topology, and path arrangement is performed using the virtual member sub-link End.X SID.

In the implementation, when the slice user traffic is directed to the SRv6 Policy tunnel for transmission, the forwarding device determines the slice sub- link physical resource, and forward the message through the corresponding sub-link physical resource sub-interface.

During implementation, when guiding slice user traffic to the SRv6 Policy tunnel for transmission, the SDN controller updates one or a combination of the following information according to the information reported by the device: The corresponding relationship between sub-link resources, Sub-Link Num status, virtual member sub-link remaining slice resource information.

In implementation, it further includes:

By dividing the value space of the sub-link resource identifiers, it is used to distinguish the sub-link resource identifiers used by the FA slice and the user slice.

During the implementation, when dividing the value space of the sub-link resource identifier, the sub-link resources corresponding to the Sub-Link Num whose upper 4 bits are 1 are allocated to the FA slice, and the rest of the Sub-Link Num value space is allocated to the user sliced to use.

In implementation, it further includes:

In each FA slice topology, the remaining bandwidth resources not allocated to user slices in the reserved total bandwidth are shared by non-slice users in the FA slice topology, and the traffic of non-slice users is carried by SRv6 BE.

During implementation, the FA slice is based on the number of industries or virtual operators, and the network is divided into a corresponding number of FA slices based on FlexAlgo that have a one-to-one correspondence;

According to the industry or virtual operator to which the slice user belongs, the FlexAlgo-based FA slice to which it belongs is determined.

A network device comprising:

A division module, configured to divide the link corresponding to each network device interface into multiple sub-link resources according to the slice user resource requirements;

The corresponding module is used to establish the corresponding relationship between the slice identifier SliceID and the resource requirement;

The binding module is configured to establish a one-to-one binding IPv6-based source routing technology policy SRv6 Policy tunnel for the user according to the resource requirements of the slice user, and establish a corresponding relationship between the slice identifier SliceID and the SRv6 Policy tunnel.

In implementation, it further includes:

A slice user is a user in the flexible algorithm FA slice based on the flexible algorithm FlexAlgo;

SliceID is the SliceID in the FlexAlgo-based FA slice to which the slice user belongs;

The SRv6 Policy tunnel is a tunnel in the FlexAlgo-based FA slice topology to which the slice user belongs.

During implementation, the binding module is further used to establish a corresponding relationship between the slice identifier SliceID and the SRv6 Policy tunnel, which is to assign a slice identifier SliceID that can meet the slice user resource requirements for the SRv6 Policy tunnel.

During implementation, the division module is further used to identify sub-link resources with the sub-link identifier Sub-Link Num. Each sub-link has its own exclusive underlying physical resources. By saving and maintaining Sub-Link Num and various types of sub-links The corresponding relationship between road resource IDs is used to be compatible with various types of underlying physical sub-link resources.

In the implementation, the binding module is further used in routing capability type, length, value Router CAPABILITY TLV based on IPv6 source routing technology subtype, length, value SRv6Capabilities sub-TLV and border gateway protocol link type BGP-LS based IPv6 source routing technology capability type, length, and value SRv6 Capability TLV adds an identifier to indicate that the device supports the ability to carry SliceID on the forwarding plane and perform slice processing.

In the implementation, the binding module is further used to add an identifier to the end segment identifier subtype, length, and value End.X SID sub-TLV structure to indicate that the device is an adjacent SID of a virtual member sublink, not a physical link Adjacent SID of the road.

During implementation, the binding module is further configured to use the link slice information subtype, length, value Sub-TLV and slice resource subtype, length, value Sub-sub-TLV structure to announce the number of link slices and corresponding resource information.

In implementation, the division module is further used to perform one or a combination of the following processes:

When assigning the number of SliceIDs, after assigning a preset number of SliceIDs to each FA slice on the SDN controller, send them to the device;

According to the needs of slice users in the FA slice topology, assign SliceID resources on the forwarding plane to each user, and establish the corresponding relationship between SliceID and the resource requirements of each slice user. Unallocated SliceIDs are temporarily reserved and have no resource requirements;

SliceIDs that have not been assigned bandwidth requirements are updated according to the bandwidth requirements of subsequent new slice users, and the updated information is sent to the device synchronously.

In practice, the segmentation module is further used to maintain and/or update the following information:

FA slice SliceID, virtual member sub-link End.X SID, total reserved resources of virtual member sub-link End.X SID, corresponding relationship of The total remaining slice resources of the link.

During implementation, the binding module is further used to carry the SliceID information of the forwarding plane in the BGP SRv6 Policy message.

During implementation, the binding module is further used to configure the mapping relationship between the Color template and the SliceID on the forwarding plane, so that the tunnel head node device obtains the corresponding SliceID according to the Color attribute of the SRv6 Policy.

During implementation, the binding module is further used to perform path calculation based on the SliceID information, the FA topology, and the remaining slice resource information of the virtual member sub-link End.X corresponding to the FA topology, and use the virtual member sub-link End.X SID to perform path calculation. routing.

During implementation, the binding module is further used to direct the slice user traffic to the SRv6 Policy tunnel for transmission, so that the forwarding device, when forwarding the message, according to the indication of the slice flag in the virtual member sub-link End.X SID, Determine the sub-link physical resources of the slice on the outgoing interface, and forward the packet through the corresponding sub-link physical resource sub-interface.

During implementation, the binding module is further used to guide slice user traffic to the SRv6 Policy tunnel for transmission, and update one or a combination of the following information according to the information reported by the device: the SliceID of the virtual member sub-link and the sub-link resource Sub- Correspondence between Link Num, status of sub-link resource Sub-Link Num, virtual member sub-link remaining slice resource information.

During implementation, the division module is further configured to divide the value space of the sub-link resource ID to distinguish the sub-link resource ID used by the FA slice and the user slice.

During implementation, the division module is further used to allocate the sub-link resource corresponding to the Sub-Link Num whose upper 4 bits are 1 to the FA slice when dividing the value space of the sub-link resource identifier, and the remaining Sub-Link Num is taken as The value space is allocated for use by user slices.

During implementation, the division module is further used to reserve the remaining bandwidth resources in the total bandwidth that are not allocated to user slices in each FA slice topology for shared use by non-slice users in the FA slice topology, and the traffic of non-slice users passes through SRv6 BE bearer.

During implementation, the division module is further used for the FA slice to divide the corresponding number of FA slices based on FlexAlgo with a one-to-one correspondence for the network according to the number of industries or virtual operators;

According to the industry or virtual operator to which the slice user belongs, the FlexAlgo-based FA slice to which it belongs is determined.

A network device comprising:

The processor, which reads the program in the memory, performs the following processes:

When providing services for the slice users, direct their service traffic to the SRv6 Policy tunnel for transmission;

Establish the corresponding relationship between the SliceID and the sub-link resources of each interface on the SRv6 Policy tunnel path;

Transceiver, used to receive and transmit data under the control of the processor.

In implementation, it further includes:

One or a combination of the following information is flooded in the IGP: the End.X SID of each FA slice virtual member sub-link on the link, the total reserved bandwidth, the number of SliceIDs, or the resource information corresponding to each SliceID.

In implementation, it further includes:

Make the tunnel head node device obtain the SliceID from the BGP SRv6 Policy message sent by the SDN controller, and write it into the corresponding position of the forwarding plane message.

During the implementation, when the slice user traffic is directed to the SRv6 Policy tunnel for transmission, according to the SliceID carried in the forwarding message of the slice user, a sublink resource that can meet the resource requirements of the SliceID is allocated from the idle sublink resources of the corresponding physical outbound interface. Link resources are used for forwarding, and the corresponding relationship between SliceID and sub-link resources and the status of sub-link resources are maintained.

During implementation, when slice user traffic is directed to the SRv6 Policy tunnel for transmission, when the first slice packet arrives at the device, the device searches the local table to obtain the bandwidth resources required by the SliceID according to the SliceID carried in the Find the sub-link resource Sub-Link Num of unoccupied bandwidth in the sub-link resource table of the device, assign it to the SliceID, forward the slice user packet from the corresponding sub-port, and update the local sub-link resource Sub -Link Num status is occupied, and report to the SDN controller through telemetry Telemetry to update one or a combination of the following information: sub-link resource Sub-Link Num occupancy, SliceID and Sub-Link Num correspondence, Sub-Link Num state.

A network device comprising:

A transmission module, configured to direct its service traffic to the SRv6Policy tunnel for transmission when providing services to users of the slice;

The relationship module is used to establish the corresponding relationship between the SliceID and the sub-link resources of each interface on the SRv6 Policy tunnel path.

During implementation, the relationship module is further used to flood and notify one or a combination of the following information in the interior gateway protocol IGP: the End.X SID of each FA slice virtual member sub-link on the link, the total reserved bandwidth, the number of SliceIDs, or Each SliceID corresponds to resource information.

During implementation, the relationship module is further used to enable the tunnel head node device to obtain the SliceID from the BGP SRv6Policy message sent by the SDN controller, and write it into the corresponding position of the forwarding plane message.

During implementation, when the transmission module is further used to guide the slice user traffic to the SRv6 Policy tunnel for transmission, according to the SliceID carried in the slice user forwarding message, allocate a sub-link resource that can meet the requirements from the idle state sub-link resources of the corresponding physical outbound interface. The sub-link resource required by the SliceID resource is forwarded, and the corresponding relationship between the SliceID and the sub-link resource and the state of the sub-link resource are maintained.

During implementation, the transmission module is further used to guide slice user traffic to the SRv6 Policy tunnel for transmission. When the first slice packet arrives at the device, the device will check the local table to obtain the required bandwidth for the SliceID according to the SliceID carried in the forwarded packet. After resources, find the unoccupied sub-link resource Sub-Link Num from the sub-link resource table of the local device, assign it to the SliceID, forward the slice user packets from the corresponding sub-port, and update the local The status of sub-link resource Sub-Link Num is occupied, and one or a combination of the following information is reported to the SDN controller through telemetry: sub-link resource Sub-Link Num occupancy, SliceID and Sub-Link Num correspondence , Sub-Link Num state.

A computer-readable storage medium storing a computer program for executing the above transmission method.

The beneficial effects of the present invention are as follows:

The technical solutions provided in the embodiments of the present invention are resource-guaranteed bearer network slicing solutions and mechanisms based on FlexAlgo and SRv6. By extending the FlexAlgo technology, combined with SRv6 tunnel encapsulation, carrying the slice ID on the forwarding plane and the centralized management and control capabilities of SDN, it provides users with a dynamically adjustable sub-link level resource-guaranteed two-level data bearer network slicing service. Among them, because the first-level slice is implemented by FlexAlgo technology, it can be used for slice isolation of different maintenance subjects or to allocate different slices for different industries; because the second-level slice uses the SRv6 tunnel technology, the slice ID is carried on the forwarding plane to realize the first-level FA Secondary user-level or business-level slices within slices.

Since the resources of each slice on the same physical link can be exclusively shared, compared with the existing FlexAlgo technology, it can be solved that each slice of FlexAlgo can only share one physical link exclusively, and the isolation granularity is coarse. Deployment implements slice hard isolation.

Because it can provide underlying physical resource guarantee for slices and realize hard slices, compared with the existing SR-TE and SR Policy technologies, it can solve the problem of soft isolation only through tunnels and complete sharing of physical resources.

Since the independent FA enhancement technology and the independent SRv6 Policy + forwarding plane slicing technology can only provide one-level slicing services, this solution provides a dynamically adjustable sub-link-level resource-guaranteed two-level slicing service for data bearer networks , which can meet the two-level slicing scenario requirements of industry or virtual operator slicing + user slicing.

Description of drawings

The accompanying drawings described here are used to provide a further understanding of the present invention, and constitute a part of the present invention. The schematic embodiments of the present invention and their descriptions are used to explain the present invention, and do not constitute improper limitations to the present invention. In the attached picture:

FIG. 1 is a schematic diagram of the physical networking topology of equipment in the background technology;

Fig. 2 is a schematic diagram of different FA slice sub-topologies in the background technology;

FIG. 3 is a schematic diagram of the implementation flow of the transmission method on the SDN controller side in the embodiment of the present invention;

Figure 4 is a schematic diagram of the structure of the End.X SID sub-TLV after the Q-flag in the embodiment of the present invention;

5 is a schematic diagram of the structure of the link slice information Sub-TLV in the embodiment of the present invention;

FIG. 6 is a schematic diagram 1 of a slice resource sub-sub-TLV structure in an embodiment of the present invention;

FIG. 7 is a schematic diagram 2 of a slice resource sub-sub-TLV structure in an embodiment of the present invention;

Fig. 8 is a schematic diagram of the structure extension of ISIS SRv6 Capabilities sub-TLV in the embodiment of the present invention;

FIG. 9 is a schematic diagram of the structure extension of BGP-LS SRv6 Capabilities sub-TLV in the embodiment of the present invention;

FIG. 10 is a schematic diagram of the structure of the BGP SRv6 Policy extended SliceID in the embodiment of the present invention;

FIG. 11 is a schematic diagram of a network networking structure in an embodiment of the present invention;

Fig. 12 is a schematic diagram of allocation of End SID and End.X SID of each device in the embodiment of the present invention;

FIG. 13 is a schematic diagram of the topology of each FA slice in the embodiment of the present invention;

Fig. 14 is a schematic diagram of the forwarding process of the SRv6 Policy tunnel of the electric power industry user 1 message in the embodiment of the present invention;

15 is a schematic structural diagram of a network device serving as an SDN controller in an embodiment of the present invention;

FIG. 16 is a schematic diagram of an implementation flow of a transmission method on the forwarding device side in an embodiment of the present invention;

FIG. 17 is a schematic structural diagram of a network device serving as a forwarding device in an embodiment of the present invention.

Detailed ways

The inventor noticed during the invention that:

It is necessary to have a slicing scheme that can be associated with the physical resources of the underlying sub-links to match the actual resources of the existing network, realize the exclusive use of the underlying physical resources at the sub-link granularity of each slice, and improve the value of the network.

Specific embodiments of the present invention will be described below in conjunction with the accompanying drawings.

During the description, the implementation of the SDN controller and the forwarding device will be described respectively, and then an example of the cooperation between the two will be given to better understand the implementation of the solution given in the embodiment of the present invention. Such an explanation does not mean that the two must be implemented together or separately. In fact, when the SDN controller and the forwarding device are implemented separately, they each solve their own problems. When the two are used in combination, A better technical effect will be obtained.

Figure 3 is a schematic diagram of the implementation process of the SDN controller side transmission method, as shown in the figure, which may include:

Step 301, the SDN controller divides the link corresponding to each network device interface into multiple sub-link resources according to the slice user resource requirements;

Step 302, establishing a corresponding relationship between the slice identifier SliceID and the resource requirement;

Step 303: According to the resource requirements of the slice user, establish a one-to-one binding IPv6-based source routing technology policy SRv6 Policy tunnel for the user, and establish a corresponding relationship between the slice identifier SliceID and the SRv6Policy tunnel.

In implementation, it further includes:

A slice user is a user in the flexible algorithm FA slice based on the flexible algorithm FlexAlgo;

SliceID is the SliceID in the FlexAlgo-based FA slice to which the slice user belongs;

The SRv6 Policy tunnel is a tunnel in the FlexAlgo-based FA slice topology to which the slice user belongs.

In implementation, it further includes:

Establishing the correspondence between the slice identifier SliceID and the SRv6 Policy tunnel is to assign a slice identifier SliceID that can meet the slice user resource requirements for the SRv6 Policy tunnel.

The implementation on the forwarding device will be described below.

Figure 16 is a schematic diagram of the implementation process of the forwarding device side transmission method, as shown in the figure, may include:

Step 1601. When the forwarding device provides services for the users of the slice, guide their service traffic to the SRv6Policy tunnel for transmission;

Step 1602, establish the corresponding relationship between the SliceID and each interface sub-link resource on the SRv6 Policy tunnel path.

In implementation, it further includes:

One or a combination of the following information is flooded in the IGP: the End.X SID of each FA slice virtual member sub-link on the link, the total reserved bandwidth, the number of SliceIDs, or the resource information corresponding to each SliceID.

In implementation, it further includes:

Make the tunnel head node device obtain the SliceID from the BGP SRv6 Policy message sent by the SDN controller, and write it into the corresponding position of the forwarding plane message.

During implementation, when the forwarding device guides slice user traffic to the SRv6 Policy tunnel for transmission, according to the SliceID carried in the forwarding packet of the slice user, it allocates a sub-link resource that can meet the SliceID resource requirement from the idle state sub-link resources of the corresponding physical outbound interface. The sub-link resource is forwarded, and the corresponding relationship between the SliceID and the sub-link resource and the state of the sub-link resource are maintained.

During implementation, when the forwarding device directs slice user traffic to the SRv6 Policy tunnel for transmission, when the first slice packet arrives at the device, the device checks the local table to obtain the bandwidth resource required by the SliceID according to the SliceID carried in the forwarded packet, and then Find the sub-link resource Sub-Link Num of unoccupied bandwidth from the sub-link resource table of the local device, assign it to the SliceID, forward the slice user packets from the corresponding sub-port, and update the local sub-link The status of the resource Sub-Link Num is occupied, and one or a combination of the following information is reported to the SDN controller through telemetry: Sub-link resource Sub-Link Num occupancy, SliceID and Sub-Link Num correspondence, Sub-Link LinkNum state.

The following mainly focuses on the SDN controller, combined with the forwarding device to illustrate, so as to understand the relationship between the two.

During implementation, the FA slice is based on the number of industries or virtual operators, and the network is divided into a corresponding number of FA slices based on FlexAlgo that have a one-to-one correspondence;

The SDN controller determines the FlexAlgo-based FA slice to which the slice user belongs according to the industry or virtual operator to which it belongs.

That is, according to the number of industries or virtual operators, the corresponding number of FlexAlgo-based FA slices are divided for the network in advance, that is, there is a one-to-one correspondence between industries or virtual operators and FlexAlgo-based FA slices, which can be configured in advance. The controller determines the FlexAlgo-based FA slice to which the slice user belongs according to the industry or virtual operator to which the slice user belongs.

Specifically, the solution is a resource-guaranteed bearer network slicing solution and mechanism based on FlexAlgo and SRv6. By extending the existing FlexAlgo technology, combined with SRv6 tunnel encapsulation, the slice ID is carried on the forwarding plane and the centralized control capability of SDN (Software Defined Network), providing users with dynamically adjustable sub-link level Resource-guaranteed data bearer network two-level slicing service.

Among them, the first-level slicing is implemented by FlexAlgo technology, which can be used to isolate slices of different maintenance subjects or allocate different slices for different industries; the second-level slicing uses SRv6 tunnel technology to carry slice IDs on the forwarding plane to implement Secondary user-level or business-level slices.

During implementation, establishing the correspondence between the SliceID and the SRv6Policy tunnel in the FlexAlgo-based FA slice to which the slice user belongs is to establish the correspondence between the SliceID in the FA slice and the sublink resources of each interface on the SRv6 Policy tunnel path.

The following will mainly take SliceID and Sub-Link Num as examples for illustration.

(1) SDN controller resource management mechanism.

When assigning the number of SliceIDs, after assigning a preset number of SliceIDs to each FA slice on the SDN controller, send them to the device;

The SDN controller allocates forwarding plane SliceID resources and corresponding bandwidth information to each user according to the needs of slice users in the FA slice topology, and unallocated SliceIDs are temporarily reserved.

Specifically, the following will describe the End.X SID allocation of virtual member sub-links in the FA slice topology, the total resource reservation mechanism and method, and the implementation of the SliceID quantity allocation rule on the forwarding plane in the FA slice topology.

The SDN controller maintains and/or updates the following information:

FA slice SliceID, virtual member sub-link End.X SID, total reserved resources of virtual member sub-link End.X SID, corresponding relationship of The total remaining slice resources of the link.

Specifically, the following will maintain the corresponding relationship between FA slice SliceID, virtual member sub-link End.XSID and its total reserved resources, and the number of SliceIDs on the controller. The implementation of maintaining and updating information such as the total remaining slice resources of the road will be described.

1) End.X SID allocation and slice resource reservation of the virtual member sub-links of the FA first-level slice.

First, it is necessary to allocate different Locator (location point) spaces for each FA slice, and then the controller allocates different End SIDs (end SIDs) for each node in the FA slice topology in the Locator space according to the topology requirements of the first-level FA slice. ), different End.X SIDs are assigned to each virtual member sub-link; at the same time, according to the bandwidth requirements of the first-level FA slice, corresponding bandwidth resources are reserved for each FA slice topology; each End SID, End.X SID and the required The reserved bandwidth information is sent to the corresponding device in the network, and the device performs corresponding configuration and saves the corresponding relationship between the End.X SID and the reserved bandwidth. The details can be shown in the following table:

Table 1: Virtual member sub-link adjacency SID dynamic resource allocation table

FA slice ID End.X SID Reserved total bandwidth (G) 128 X1:1::1 (belongs to the address space of FA118) 5G 129 X2:1::1 (belongs to the address space of FA129) 10G 130 X3:1::1 (belongs to the address space of FA130) 15G

The above information can also be configured directly on the device and reported to the controller through BGP-LS (BGP link state, BGP-LinkState; BGP: Border Gateway Protocol, Border Gateway Protocol), so that the information of both parties is consistent.

If a 400G physical link is pre-allocated with 40 first-level FA slices, and each FA slice occupies 5G bandwidth, it means that 200G bandwidth is reserved for FA slice topology, and only the remaining 200G bandwidth can be shared with non-slice users .

2) Allocation of the number of SliceIDs on the forwarding plane in the FA slice topology.

The following describes the operation mechanism and scheme of the value assignment of the SliceID on the user forwarding plane of the second-level slice, corresponding resource assignment, and status maintenance.

Assign a fixed number of SliceIDs to each FA slice; or assign a certain number of SliceIDs to each FA slice and send them to the device.

Static allocation method: assign a fixed number of SliceIDs to each FA slice, such as 500, the SliceIDs of the forwarding plane reserved for the FA128 slice topology are 1 to 500, and the SliceIDs of the forwarding plane reserved for the FA129 slice topology are 501 to 1000. By analogy, the SliceID of the forwarding plane reserved for the FAn slice topology is [(n-128)*500+1] ~ [(n-128)*500+500].

Dynamic allocation method: A certain number of SliceIDs are assigned to each FA slice and sent to the device, and the information of the SliceID is flooded in the IGP and notified to each device.

3) Allocation and state maintenance of the forwarding plane SliceID corresponding to the second-level slice user.

According to the needs of slice users in the FA slice topology, the controller allocates forwarding plane SliceID resources and corresponding bandwidth information to each user, and unallocated SliceIDs are temporarily reserved;

SliceIDs that have not been assigned bandwidth requirements are updated according to the bandwidth requirements of subsequent new slice users, and the updated information is sent to the device synchronously.

Specifically, the controller allocates forwarding plane SliceID resources and corresponding bandwidth information to each user according to the needs of users of the second-level slices in the first-level FA slice topology, and unallocated SliceIDs are temporarily reserved. The details can be shown in the table below.

Table 2: Allocation table of resource requirements corresponding to SliceID on the forwarding plane

The SliceIDs in the above table that have not been assigned bandwidth requirements can be updated at any time according to the bandwidth requirements of subsequent new slice users. The controller is responsible for maintaining the dynamic update table, and synchronously sends the above information to the device for storage. Wherein, the state of the SliceID includes idle, pre-occupied, occupied, unallocated and so on.

If the head node needs to be used for path calculation, each SliceID and the corresponding bandwidth resource information need to be expanded through ISIS (Intermediate system to intermediate system, Intermediate system to intermediate system) and flooded in the IGP; if all paths are calculated using the controller, then no Flooding is required.

4) Sub-Link Num corresponds to resource allocation and status maintenance.

When guiding the slice user traffic in the FA slice of FlexAlgo to the SRv6 Policy tunnel for transmission, the forwarding device allocates a sub-link resource in the idle state corresponding to the physical outbound interface according to the SliceID carried in the forwarding packet of the slice user. The sub-link resource required by the SliceID resource is forwarded, and the corresponding relationship between the SliceID and the sub-link resource and the state of the sub-link resource are maintained.

Next, according to the SliceID carried in the packet forwarded by the slice user, the forwarding device will allocate a sublink resource (such as MTN (Metropolitan Area Transmission network, Metro transport network) sub-interface, VLAN (Virtual Local Area Network, Virtual LocalArea Network) enhanced sub-interface, channelized sub-interface resources, FlexE sub-interface, independent QoS (Quality of Service, Quality of Service) queue, etc.); SliceID The corresponding relationship with the sub-link resource and the dynamic maintenance mechanism and method of the state of the sub-link resource will be described.

When guiding the slice user traffic in the FA slice of FlexAlgo to the SRv6 Policy tunnel for transmission, the Sub-Link Num is used to identify the underlying physical sub-link resources. Each sub-link has its own exclusive underlying physical resources. By saving and maintaining the Sub-Link The corresponding relationship between Link Num and various types of sub-link resource IDs is compatible with various types of underlying physical sub-link resources.

Specifically, Sub-Link Num is introduced to uniformly identify the underlying physical sub-link resources. Each sub-link has its own exclusive underlying physical resources, such as MTN sub-interfaces, VLAN enhanced sub-interfaces, channelized sub-interface resources, and FlexE sub-interfaces. , independent QoS queue, etc., by saving and maintaining the corresponding relationship between the Sub-Link Num and the above-mentioned various types of sub-link resource IDs, it is compatible with various types of underlying physical sub-link resources.

Specifically, the controller divides each physical link corresponding to all devices in the first-level FA slice topology into multiple isolated sub-links according to the needs of users of the second-level slicing, and each sub-link has its own exclusive underlying Physical resources, such as MTN sub-interfaces, VLAN enhanced sub-interfaces, Channel channelized sub-interface resources, FlexE sub-interfaces, independent QoS queues, etc., are identified by Sub-Link Num, and the length of the sub-link identifier is 4 bytes. The low bit represents the sub-link resource ID, such as MTNID, VLANID, ChannelID, FlexEID, and QoSQueID. If the sub-link resource ID is less than 32 bits, the high bit is filled with 0.

In implementation, the value space of sub-link resource identifiers is divided to distinguish the sub-link resource identifiers used by FA slices and user slices.

A user slice may also be referred to as a forwarding plane slice, that is, a slice that establishes an SRv6 tunnel based on the association between the SliceID and the underlying sub-link resources.

In the specific implementation, when dividing the value space of the sub-link resource identifier, the sub-link resources corresponding to the Sub-Link Num whose upper 4 bits are 1 are allocated to the FA slice, and the rest of the Sub-Link Num value space is allocated to User slices are used.

For example, the sub-link resources corresponding to the Sub-Link Num whose upper 4 bits are 1 are allocated to the FA first-level slice.

Taking sub-link resources as channelized sub-interfaces as an example, the example can be as follows (for concise expression, each number in the following table represents an 8-bit decimal value):

Table 3: Sub-link physical resource allocation table

During specific implementation, sub-link resources of 100M\200M\500M can be pre-allocated on the device in advance (the total amount cannot exceed the total bandwidth of the corresponding FA level-1 slice), so that the new When the user comes, the underlying sub-link resources are already available, and the service can be opened quickly.

1. In order to be compatible with various types of underlying resources, a sub-link identifier: Sub-Link Num is introduced; the Sub-Link Num may not be required, but ChannelID is directly used to identify a specific sub-link.

2. It is also possible to configure physical resources other than Bandwidth (bandwidth) for MTN sub-interfaces/VLAN enhanced sub-interfaces/Channel channelization sub-interface resources/FlexE sub-interfaces/independent QoS queues. Only bandwidth resources are used as examples here.

The controller sends the configuration of the above-mentioned corresponding relationship to each device in the network, and the device executes the relevant configuration locally and stores the above-mentioned corresponding relationship.

The controller is responsible for maintaining the status of each Sub-Link Num on the link, such as idle, pre-occupied, occupied, etc., and updating its Sub-Link Num occupancy in real time according to the sub-link resource Sub-Link Num occupancy reported by the device through Telemetry. state.

(2) IGP floods the link information related to the slice.

One or a combination of the following information is flooded in the IGP: the End.X SID of each FA slice virtual member sub-link on the link, the total reserved bandwidth, the number of SliceIDs, or the resource information corresponding to each SliceID.

The method for IGP flooding notification of the End.X SID, total reserved bandwidth, number of SliceIDs, and resource information corresponding to each SliceID of virtual member sublinks of each FA slice on the link will be described below.

IGP floods the link information related to the slice, and notifies the End.X of each FA slice on the link, the total reserved bandwidth, the number of SliceIDs, and the resource information corresponding to each SliceID.

1) Notification of the End.X SID information of the virtual member sub-link of the FA slice.

During implementation, an identifier is added to the End.X SID sub-TLV structure to indicate that the device is an adjacent SID of a virtual member sub-link rather than an adjacent SID of a physical link.

Specifically, extend the End.X SID sub-TLV (end segment identifier sub-TLV; TLV: type, length, value, Tag, Length, Value) structure to add a flag (flag) to indicate that it is a virtual member sub-link The adjacency SID of the physical link, not the adjacency SID of the physical link.

Figure 4 is a schematic diagram of the structure of the End.X SID sub-TLV after Q-flag, as shown in the figure, the Algorithm (algorithm) field (see Figure 4) corresponding to each virtual member sub-link End. The FA algorithm (Flexible Algorithm) used by the FA slice to which it belongs is consistent, and a Q-flag is added to indicate that the adjacent SID is a virtual member sublink of a certain slice. After extending the Q-flag, the End.X SID sub-TLV structure is shown in Figure 4.

An SRv6 node advertises multiple virtual member sublink End.X SIDs by carrying multiple SRv6 End.X SID sub-TLVs in the same adjacency TLV.

2) Link slice information notification: FA SliceID (slice identifier) and corresponding resource information notification.

Use link slice information Sub-TLV and slice resource Sub-sub-TLV structures to announce the number of link slices and corresponding resource information.

Specifically, the newly defined link slice information Sub-TLV and slice resource Sub-sub-TLV (sub-sub-TLV) structures are used to announce the number of link slices and corresponding resource information.

The reserved total bandwidth resources of FA, the number of SliceIDs, and the slice resource information corresponding to each SliceID can be notified through the sub-TLV of the GENINFO TLV (basic information TLV) in RFC6823. Continue to advertise the slice resource information of the interface in the extended slice.

Figure 5 is a schematic diagram of the link slice information Sub-TLV structure, and the newly defined link slice information sub-TLV is shown in Figure 5, where:

Type (8bit): TBD (to be determined, to be decided) pending application;

Length (8bit): message length, excluding Type (type) and Length (length);

Flags (8bit): flag;

Ibit: After setting, it indicates that the link identification information is a 4-byte IPv4 (Internet Protocol Version 4, Internet Protocol Version 4) interface address;

Vbit: After setting, it indicates that the link identifier is a 16-byte IPv6 (Internet Protocol Version 6, Internet Protocol Version 6) interface address;

Lbit: After setting, it indicates that the link identification information is a 4-byte local link identification;

Xbit: After setting, it indicates that the sublink identification information is a 16-byte End.X SID;

Bandwidth(8bit): the total bandwidth of the slice;

Sub-Link Local Identifier (128bit): sub-link identifier;

SliceIDCount(8bit): number of slice IDs;

FirstSliceID (24bit): slice ID start value;

Sub-sub-TLVs: slice resource sub-sub-TLV, used to announce the resource information of each SliceID.

Figure 6 is a schematic diagram 1 of the slice resource sub-sub-TLV structure. As shown in the figure, the newly defined slice resource sub-sub-TLV is used to notify the resource information of the SliceID, and the structure is as follows:

Type(8bit): TBD pending application;

Length(8bit): message length;

Flags(8bit): reserved;

Reserved(16bit): reserved;

SliceID (24bit): slice ID value;

Optional Sub-sub-sub-TLVs: carry slice resource information corresponding to SliceID (maximum reserved link bandwidth, available bandwidth, used bandwidth, delay, link packet loss rate, etc.), which can be reused in the existing RFC8570 The defined sub-TLV is as follows:

Type (type) Description 33 Unidirectional Link Delay (one-way link delay) 34 Min/Max Unidirectional Link Delay (minimum/maximum unidirectional link delay) 35 Unidirectional Delay Variation (unidirectional delay variation) 36 Unidirectional Link Loss (unidirectional link loss) 37 Unidirectional Residual Bandwidth (one-way residual bandwidth) 38 Unidirectional Available Bandwidth (one-way available bandwidth) 39 Unidirectional Utilized Bandwidth (unidirectional utilization of bandwidth)

Figure 7 is a schematic diagram of the slice resource sub-sub-TLV structure 2. Optional Sub-sub-sub-TLVs can also be directly filled in with Bandwidth/Delay/.... The structural diagram is shown in Figure 7:

(3) Notification of device slicing capabilities.

Add flags to the SRv6 Capabilities sub-TLV of the Router CAPABILITY TLV and the SRv6Capability TLV of BGP-LS to indicate that the device supports the ability to carry SliceID on the forwarding plane and perform slice processing.

Specifically, the SRv6 Capabilities sub-TLV (SRv6 Capabilities sub-TLV) of the Router CAPABILITY TLV (routing capability TLV) and the SRv6 Capability TLV of BGP-LS are extended, and a flag is added to indicate that the device supports forwarding plane slice processing capabilities.

In BGP-LS Node NLRI (node NLRI; NLRI: Network Layer Reachability Information, Network Layer Reachability Information) FAD (Flexible Algorithm Definition, Flexible Algorithm Definition) TLV FADF (Flexible Algorithm Definition Flags, flexible algorithm definition flag) sub - The TLV adds a flag to indicate that the path calculation is based on the virtual member sublink information of the interface.

Specifically, the FADF sub-TLV of the FAD TLV of the BGP-LS Node NLRI is extended, and a flag is added to indicate that the calculation is based on the virtual member sublink information of the interface when calculating the path.

1) Extend the SRv6 Capabilities sub-TLV of the Router CAPABILITY TLV, and add a Q-flag to indicate that the device supports the slice processing capability of the forwarding plane. FIG. 8 is a schematic diagram of the structure extension of ISIS SRv6Capabilities sub-TLV, as shown in FIG. 8 .

2) Extend the SRv6 Capability TLV of BGP-LS, add a Q-flag, and notify the node that it has the ability to process slices in the forwarding plane. Figure 9 is a schematic diagram of the extended BGP-LS SRv6 Capabilities sub-TLV structure, as shown in Figure 9 in detail.

(5) The extended BGP SRv6 Policy carries the SliceID information of the forwarding plane.

The SliceID information of the forwarding plane is carried in the BGP SRv6 Policy message.

Specifically, the BGP SRv6 Policy structure is extended to carry forwarding plane SliceID information.

Figure 10 is a schematic diagram of the extended SliceID structure of the BGP SRv6 Policy. The BGP SRv6 Policy is extended and the SliceID (shaded part) is added. The expanded format is shown in Figure 10.

(6) Dynamic maintenance of the corresponding relationship between SliceID and Sub-Link Num (sub-link identifier) on the slice user forwarding plane.

The following describes the mechanism and method for the forwarding device to synchronize the corresponding relationship between the SliceID and the Sub-Link Num and the occupancy of the sub-link resource Sub-Link Num to the controller in real time through Telemetry.

When the slice user traffic in the FA slice of FlexAlgo is directed to the SRv6 Policy tunnel for transmission, when the first slice packet arrives at the device, the device checks the local table to obtain the bandwidth resource required by the SliceID according to the SliceID carried in the forwarded packet, and then Find the sub-link resource Sub-LinkNum of unoccupied bandwidth from the sub-link resource table of the local device, assign it to the SliceID, forward the slice user packet from the corresponding sub-port, and update the local sub-link resource The Sub-Link Num status is occupied, and one or a combination of the following information is reported to the controller through Telemetry: sub-link resource Sub-Link Num occupancy, SliceID and Sub-Link Num correspondence, Sub-LinkNum status.

Specifically, when the first slice packet arrives at the device, the device checks the local table to obtain the bandwidth resources required by the SliceID according to the SliceID carried in the forwarded packet. The occupied 100M sub-link resource Sub-Link Num is allocated to the SliceID, and the slice user message is forwarded from the corresponding sub-port, such as the information sub-interface, and the local sub-link resource Sub-Link Num is updated at the same time The status is occupied, and the Sub-Link Num occupancy status of the sub-link resource is reported to the controller in real time through Telemetry. Table 4 is a corresponding relationship between SliceID and Sub-Link Num, and the specific relationship can be shown in the table.

Table 4: Correspondence between SliceID and Sub-Link Num

SliceID Sub-link identifier Sub-Link Num 1 0001 2 0002 501 0003 502 0004 1001 0005 ... ...

(7) The color color contained in the EAG (Extended Administrative Group, extended management group) sub-TLV of each adjacent TLV corresponding to each physical link on the node needs to include at least the FA slice to which each sub-link belongs. The color color required to be included in road constraints.

(8) Slice topology generation.

The controller will know the FA slice to which the device belongs according to the FAD sub-TLV information reported by each forwarding device through BGP-LS; according to the color contained in the EAG sub-TLV corresponding to the adjacent TLV of each physical link combined with the FA path calculation constraints, it will know its The FA slice to which it belongs; according to the Q-flag setting of the FADF sub-TLV, it is known that the path calculation needs to be performed on the device based on the virtual member sub-link, so it is further based on the Algorithm of the virtual member sub-link End.X SID Know the FA slice information to which the virtual sub-links corresponding to each physical link belong, so as to form different FA slice topologies on the controller.

(9) SliceID is carried in the forwarded message.

Method 1: The tunnel head node device obtains the SliceID from the BGP SRv6 Policy message delivered by the SDN controller, and writes it into the corresponding position of the forwarding plane message.

Specifically, the tunnel head node obtains the SliceID from the BGP SRv6 Policy message sent by the controller, and writes the SliceID into the corresponding position of the message on the forwarding plane.

The controller issues the SliceID and the CadidatePath path (see Figure 10 for the extended structure) to the head node of the SRv6 tunnel through the BGP SRv6Policy protocol. When the head node device performs SRv6 tunnel encapsulation, it carries the SliceID information in the forwarded message.

Method 2: Configure the mapping relationship between the Color template and the SliceID on the forwarding plane, and the tunnel head node device obtains the corresponding SliceID according to the Color attribute of the SRv6Policy.

Specifically, the mapping relationship between the Color template and the SliceID on the forwarding plane is configured, and the head node device obtains the corresponding SliceID according to the Color attribute of the SRv6Policy, and carries the SliceID information in the forwarding message.

Among them: the SliceID information can be placed in the source address address of the forwarded message, FlowLabel (flow label) or HBH (Hop By Hop, hop-by-hop) field; by using a flag bit of the TrafficClass (transmission level) field, indicate the The packet carries SliceID information.

(10) Controller path calculation and forwarding device operation mechanism.

The controller performs path calculation based on the SliceID information, the FA topology, and the remaining slice resource information of the virtual member sub-link End.X corresponding to the FA topology, and uses the virtual member sub-link End.X SID to perform path arrangement.

In the following, the controller performs path calculation based on SliceID information, FA topology and the remaining slice resources of the corresponding virtual member sub-link End.X, and uses the virtual member sub-link End.X SID to perform path arrangement processing mechanism and The method is explained.

During implementation, in each FA slice topology, the remaining bandwidth resources not allocated to user slices in the total bandwidth are reserved for shared use by non-slice users in the FA slice topology, and the traffic of non-slice users is carried by SRv6 BE.

Specifically, in each FA slice topology, the remaining bandwidth resources not allocated to secondary user slices in the reserved total bandwidth are shared by non-slice users in the FA topology, and the traffic of non-slice users is carried by SRv6 BE.

In each FA slice topology, the traffic of secondary slice users is carried through the SRv6 Policy tunnel, and the path is calculated by the controller or the tunnel head node. Since only SRv6 Policy strict paths can provide slicing users with exclusive slicing services with strict physical resource guarantees for each end-to-end hop, SRv6 Policy tunnels refer to SRv6 Policy strict paths.

According to the SLA requirements such as bandwidth and delay proposed by the second-level slice user, the controller selects a SliceID (assumed to be x) whose state is "unallocated" from "Table 2: Resource Requirement Allocation Table Corresponding to SliceID on the Forwarding Plane", and updates its "Required bandwidth" information, and update the status to "idle"; at the same time, create a VPN for it and use the binding (binding) mode tunnel policy to bind the SRv6 Policy tunnel one-to-one, and in the second slice where the user is located In the level FA slicing topology (for example, FA is used as the path calculation factor), the user's SLA requirements (bandwidth, delay, etc.) are used as the path calculation constraints to calculate the SRv6 Policy active and standby CadidatePath (CP for short).

When calculating the path, the controller needs to combine the resource conditions of the virtual member sub-link End.X corresponding to its first-level FA topology (such as whether there are enough remaining slice bandwidth resources, whether the delay meets user needs, etc.), and calculate a path There is only one segmentlist in each CP, and the path of each segmentlist is arranged using the End.X SID of the Locator space corresponding to the FA slice; at the same time, update "Table 2 : The status of SliceID(x) in the resource requirement allocation table corresponding to SliceID on the forwarding plane is pre-occupied, and the SliceID(x) is delivered to the forwarding device of the head node together with the active and standby CPs of the BGPSRv6 Policy.

After the SRv6 Policy is delivered successfully, the real-time status of the SliceID(x) is updated on the controller as occupied.

During the implementation, when the slice user traffic in the FA slice of FlexAlgo is directed to the SRv6 Policy tunnel for transmission, the forwarding device forwards the packet according to the indication of setting the slice flag in the virtual member sub-link End.X SID. The sub-link physical resource of the slice is determined on the interface, and the packet is forwarded through the corresponding sub-link physical resource sub-interface.

Next, when forwarding packets on the forwarding device, according to the indication of setting the slice flag flag in the virtual member sub-link End.X SID, further determine the slice sub-link physical resources on the outgoing interface, and The processing mechanism and method for packet forwarding by the link physical resource sub-interface are described.

On the forwarding device, according to the SRv6 Policy path delivered by the controller, the packet is forwarded along the specified path. After determining the outgoing interface, according to the SliceID carried in the forwarded message, know the bandwidth resource requirements required by the user of the slice, and allocate a sub-link resource that can satisfy the sub-link Num of the idle state corresponding to the outgoing interface. The Sub-Link Num required by the SliceID bandwidth, the forwarding device searches the locally stored "Table 3: Sub-link Physical Resource Allocation Table" according to the Sub-Link Num, determines the corresponding sub-link resource ID (such as: ChannelID, etc.), and The message is forwarded through the sub-interface (such as the channelized sub-interface), thereby ensuring that the service flow has an exclusive channelized sub-interface physical resource; at the same time, the state of the Sub-LinkNum is updated as occupied, and the local "Table 4 : SliceID and Sub-Link Num correspondence table", and report the above information to the controller through Telemetry.

When directing slice user traffic in the FA slice of FlexAlgo to the SRv6 Policy tunnel for transmission, the controller updates one or a combination of the following information based on the information reported by the device: the SliceID of the virtual member sub-link and the sub-link resource Sub-Link The corresponding relationship between Num, sub-link resource Sub-Link Num status, virtual member sub-link remaining slice resource information.

Next, according to the above information reported by the device, the controller performs the correspondence between the SliceID of the virtual member sub-link and the sub-link resource Sub-Link Num, the status of the sub-link resource Sub-Link Num, and the virtual member sub-link The mechanism and method for dynamically updating and maintaining information such as remaining slice resources are described.

After the controller receives the allocation information of the Sub-Link Num reported by the forwarding device through Telemetry, it saves the corresponding relationship, and updates the remaining slice bandwidth resource information of each virtual member sub-link End.X SID in the FA topology (such as: total reserved Reserved bandwidth - allocated Sub-Link Num bandwidth).

When both the active and standby CP paths of a slice user fail, the BE escape path is used, and the escape path occupies resources of non-slice users in the FA slice topology.

The following examples are used to illustrate.

(1) Network description.

Assume that there are devices A, B, C, D, E, F, G, and H in the network, running the ISIS dynamic routing protocol, and all of them are in the same ISIS domain. All devices support the FA function and advertise the FADF sub-sub - The Q-flag of the TLV is set.

A BGP-LS connection is established between the SDN controller and the forwarding device.

FIG. 11 is a schematic diagram of a network networking structure, and the topology structure is shown in FIG. 11 .

(2) Slicing requirements.

Assume that there are currently three industry slicing requirements, and the bandwidth requirements are 5G, 10G, and 15G respectively. The secondary user slicing requirements in each industry are shown in the table.

(3) SRv6 address allocation.

In the network, 3 industries are divided into 3 FlexAlgo slices, and each FA slice is allocated a different Locator space, and the devices and links included in this FA slice are allocated End SID (Q-flag is set) in their respective address spaces and virtual member sub-link End.X SID (Q-flag is set), Figure 12 is a schematic diagram of allocation of End SID and End.X SID of each device, and the allocation situation is shown in Figure 12 .

The affinity attribute of each link in the network must at least contain the affinity (color attribute) required by the FA slice path calculation constraint to which it belongs. The specific settings are as follows:

link (two-way) affinity attribute A-B, A-F, B-C, F-G, G-H, H-E, C-G 0x00000111 (green, yellow, blue) C-D, D-E 0x00000101 (green, blue) B-F 0x00000110 (green, yellow) D-H 0x00000100 (green)

Figure 13 is a schematic diagram of each FA slice topology. Based on the above basic configuration, three FA slice topologies as shown in Figure 13 can be formed on the SDN controller.

(4) FA first-level slice resource reservation.

According to the bandwidth requirements of the first-level FA slice, the controller reserves corresponding bandwidth resources for the corresponding virtual member sub-link End.X SID of each port of each device in the topology of each FA slice.

Taking a port of device A as an example, the total reserved bandwidth of virtual member sub-links is shown in the following table, and the same applies to other devices.

(5) Allocation of the number of SliceIDs on the forwarding plane in the FA slice topology.

Allocate a certain number of SliceIDs for each FA slice on the controller and send them to the device. For example, the SliceID of the forwarding plane reserved for the FA128 slice topology is 1 to 200 (that is, FirstSliceID=1, SliceIDCount=200). The reserved forwarding plane SliceIDs are 201-600 (namely FirstSliceID=201, SliceIDCount=400), and the reserved forwarding plane SliceIDs for the FA130 slice topology are 601-1200 (namely FirstSliceID=601, SliceIDCount=600).

The above SliceID information is flooded in the IGP and notified to each device.

(6) Allocation of SliceID on the forwarding plane corresponding to the second-level slice user

The controller allocates forwarding plane SliceID resources and corresponding bandwidth information to each user according to the needs of users of the second-level slice in the first-level FA slice topology, and unallocated SliceIDs are temporarily reserved.

Table 5: Allocation table of resource requirements corresponding to SliceID on the forwarding plane

The dynamic update table is maintained on the controller, and the updated state is sent to the device for storage at any time.

The device floods the above link slice information in the IGP.

(5) Sub-Link Num corresponds to resource allocation and status maintenance.

The controller divides each physical link corresponding to all devices in the first-level FA slice topology into multiple isolated sub-links according to the needs of users of the second-level slicing. Each sub-link has its own exclusive underlying physical resources. And identified by Sub-Link Num.

Configure the physical resources corresponding to the Sub-Link Num of each port of the device. Taking device A and channelized sub-interface resources as an example, the sub-link physical resource allocation of a port on device A is shown in the following table, and other devices are similar:

The Sub-Link Num pre-allocated on the device and the corresponding physical resources need to be higher than the actual needs of the second-level slice users (for example, a certain number of 100M\200M\500M channelized sub-interface The total amount cannot exceed the total bandwidth of the corresponding FA first-level slice), so that when a new user comes, the sub-interface of the underlying link is already available, and the service can be opened quickly.

The controller sends the configuration of the above-mentioned corresponding relationship to each device in the network, and the device executes the relevant configuration locally and stores the above-mentioned corresponding relationship.

(6) SRv6-Policy path calculation and packet forwarding process.

Take the slice resource activation of user 1 in the power industry as an example. The user needs a 200M bandwidth resource from node A to node E.

The Prefix-SID assigned to users in the power industry is in the Locator address space corresponding to FA130.

The controller creates a VPN including nodes A and E, binds the SRv6 Policy tunnel one-to-one using the tunnel policy in binding mode, and enables HSB configuration for the SRv6 Policy.

The controller calculates a SRv6Policy active/standby CP whose bandwidth resources from A to E meet the 200M requirement in the FA130 topology.

Taking node A as an example, the controller checks the remaining resources of the X3:1:: and X3:3:: virtual member sublinks corresponding to the FA130 slice when calculating the path. Currently, the bandwidth of SliceID 601 meets the requirements and is idle; Each device in the FA130 topology follows this operation, and the calculated segmentlist paths of the active and standby CPs are arranged using the End.X SID of the Locator space corresponding to the FA slice.

The calculated active and standby CP paths from A to E are as follows:

Main CP: <X3:1::100, X3:2::100, X3:3::100, X3:4::100>, SliceID=601

Backup CP: <X3:5::100, X3:6::100, X3:7::100, X3:8::100>, SliceID=601

The controller updates the state of the SliceID 601 of each link in the FA130 topology to preoccupied, and sends the SliceID 601 to the head node A device along with the active and standby CP paths through the BGP SRv6 Policy protocol.

Figure 14 is a schematic diagram of the SRv6 Policy tunnel forwarding process of a message from user 1 in the electric power industry. When the message from user 1 in the electric power industry reaches the ingress node A device, the message forwarding process is shown in Figure 14 .

Device A iterates the packet to the SRv6 Policy tunnel of slice FA130 (tunnel Endpoint is E3:1:100) according to the VPN routing policy, and then encapsulates the outer layer IPv6 packet header of the SRv6 Policy tunnel, and its SRH segmentlist is <X3:1::100, X3:2::100, X3:3::100, X3:4::100, E3:1::B100> (E3:1::B100 is the VPN corresponding to this traffic SID), the current SL pointer points to X3:1::100; and according to the SliceID corresponding to the tunnel, write the value 601 of the SliceID into the corresponding position of the forwarded message (for example, it can be placed in FlowLable, HBH, source address, etc., and Indicated by 1 flag bit of TrafficClass).

According to the X3:1::100 of the DA field, device A checks the local table, knows that the outbound interface of the message is GE0/1/0, and according to the Q-flag setting instruction of X3:1::100, knows that further Determine the underlying Sub-Link Num resource according to the SliceID, and then allocate a Sub-Link Num 0004 that can meet the 200M bandwidth requirement of SliceID 601 from the Sub-Link Num of the sub-link resource in the idle state corresponding to the outbound interface. Save the correspondence.

SliceID Sub-link identifier Sub-Link Num 601 0004

Device A updates the status of Sub-Link Num 0004 to occupied, and reports the updated information to the controller through Telemetry. Bold in the table indicates "occupied"

The device determines the information sub-interface of the corresponding ChannelID 004 according to the Sub-Link Num 0004, and forwards the message through the channelization sub-interface 004, so as to ensure that the service traffic of user 1 has exclusive channelization sub-interface physical resources.

Subsequent devices in the path perform the same table lookup and forwarding, update the Sub-Link Num status, and report to the controller until the packet reaches the tunnel end node E device. In this way, it is ensured that the traffic of user 1 in the power industry can obtain the physical resource guarantee of 200M channelized sub-interfaces on each link of the forwarding path.

Based on the same inventive concept, an SDN controller and a computer-readable storage medium are also provided in the embodiment of the present invention. Since the problem-solving principle of these devices is similar to that of the transmission method, the implementation of these devices can refer to the implementation of the method, repeat The place will not be repeated.

When implementing the technical solution provided by the embodiment of the present invention, it can be implemented in the following manner.

FIG. 15 is a schematic structural diagram of a network device serving as an SDN controller. As shown in the figure, the SDN controller includes:

The processor 1500 is used to read the program in the memory 1520 and execute the following processes:

Divide the link corresponding to each network device interface into multiple sub-link resources according to the user resource requirements of the slice;

Establish the corresponding relationship between the slice identifier SliceID and resource requirements;

According to the resource requirements of the slice user, establish a one-to-one binding IPv6-based source routing technology policy SRv6 Policy tunnel for the user, and establish a corresponding relationship between the slice identifier SliceID and the SRv6 Policy tunnel;

The transceiver 1510 is used for receiving and sending data under the control of the processor 1500 .

In implementation, it further includes:

A slice user is a user in the flexible algorithm FA slice based on the flexible algorithm FlexAlgo;

SliceID is the SliceID in the FlexAlgo-based FA slice to which the slice user belongs;

The SRv6 Policy tunnel is a tunnel in the FlexAlgo-based FA slice topology to which the slice user belongs.

In implementation, it further includes:

Establishing the correspondence between the slice identifier SliceID and the SRv6 Policy tunnel is to assign a slice identifier SliceID that can meet the slice user resource requirements for the SRv6 Policy tunnel.

In implementation, it further includes:

The sub-link identifier Sub-Link Num is used to identify sub-link resources. Each sub-link has its own exclusive underlying physical resources. By saving and maintaining the correspondence between Sub-Link Num and various types of sub-link resource IDs, Compatible with various types of underlying physical sub-link resources.

In implementation, it further includes:

IPv6-based source routing technical capability subtype, length, value SRv6 Capabilities sub-TLV of routing capability type, length, value Router CAPABILITY TLV and IPv6-based source routing technical capability type of Border Gateway Protocol link type BGP-LS, Length and value SRv6 Capability TLV adds flags to indicate that the device supports the ability to carry SliceID on the forwarding plane and perform slice processing.

In implementation, it further includes:

Add an identifier to the end segment identifier subtype, length, and value End.X SID sub-TLV structure to indicate that the device is an adjacent SID of a virtual member sublink, not an adjacent SID of a physical link.

In implementation, it further includes:

Use the link slice information subtype, length, value Sub-TLV and slice resource subtype, length, value Sub-sub-TLV structure to announce the number of link slices and corresponding resource information.

In implementation, one or a combination of the following processing is further included:

When assigning the number of SliceIDs, after assigning a preset number of SliceIDs to each FA slice on the SDN controller, send them to the device;

According to the needs of slice users in the FA slice topology, assign SliceID resources on the forwarding plane to each user, and establish the corresponding relationship between SliceID and the resource requirements of each slice user. Unallocated SliceIDs are temporarily reserved and have no resource requirements;

SliceIDs that have not been assigned bandwidth requirements are updated according to the bandwidth requirements of subsequent new slice users, and the updated information is sent to the device synchronously.

In implementation, it further includes:

To maintain and/or update the following information:

FA slice SliceID, virtual member sub-link End.X SID, total reserved resources of virtual member sub-link End.X SID, corresponding relationship of The total remaining slice resources of the link.

In implementation, it further includes:

The SliceID information of the forwarding plane is carried in the BGP SRv6 Policy message.

In implementation, it further includes:

Configure the mapping relationship between the Color template and the SliceID on the forwarding plane, so that the tunnel head node device can obtain the corresponding SliceID according to the Color attribute of the SRv6Policy.

In implementation, it further includes:

Path calculation is performed based on SliceID information, FA topology, and remaining slice resource information of the virtual member sub-link End.X corresponding to the FA topology, and path arrangement is performed using the virtual member sub-link End.X SID.

In the implementation, when the slice user traffic is directed to the SRv6 Policy tunnel for transmission, the forwarding device determines the slice sub- link physical resource, and forward the message through the corresponding sub-link physical resource sub-interface.

During implementation, when guiding slice user traffic to the SRv6 Policy tunnel for transmission, the SDN controller updates one or a combination of the following information according to the information reported by the device: The corresponding relationship between sub-link resources, Sub-Link Num status, and virtual member sub-link remaining slice resource information.

In implementation, it further includes:

By dividing the value space of the sub-link resource identifiers, it is used to distinguish the sub-link resource identifiers used by the FA slice and the user slice.

During the implementation, when dividing the value space of the sub-link resource identifier, the sub-link resource corresponding to the Sub-Link Num whose upper 4 bits are 1 is allocated to the FA slice, and the rest of the Sub-Link Num value space is allocated to the user sliced to use.

In implementation, it further includes:

In each FA slice topology, the remaining bandwidth resources not allocated to user slices in the reserved total bandwidth are shared by non-slice users in the FA slice topology, and the traffic of non-slice users is carried by SRv6 BE.

During implementation, the FA slice is based on the number of industries or virtual operators, and the network is divided into a corresponding number of FA slices based on FlexAlgo that have a one-to-one correspondence;

According to the industry or virtual operator to which the slice user belongs, the FlexAlgo-based FA slice to which it belongs is determined.

Wherein, in FIG. 15 , the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by the processor 1500 and various circuits of the memory represented by the memory 1520 are linked together. The bus architecture can also link together various other circuits such as peripherals, voltage regulators, and power management circuits, etc., which are well known in the art and therefore will not be further described herein. The bus interface provides the interface. Transceiver 1510 may be a plurality of elements, including a transmitter and a receiver, providing a means for communicating with various other devices over transmission media. The processor 1500 is responsible for managing the bus architecture and general processing, and the memory 1520 can store data used by the processor 1500 when performing operations.

An embodiment of the present invention also provides a network device, including:

A division module, configured to divide the link corresponding to each network device interface into multiple sub-link resources according to the slice user resource requirements;

The corresponding module is used to establish the corresponding relationship between the slice identifier SliceID and the resource requirement;

The binding module is configured to establish a one-to-one binding IPv6-based source routing technology policy SRv6 Policy tunnel for the user according to the resource requirements of the slice user, and establish a corresponding relationship between the slice identifier SliceID and the SRv6 Policy tunnel.

In implementation, it further includes:

A slice user is a user in the flexible algorithm FA slice based on the flexible algorithm FlexAlgo;

SliceID is the SliceID in the FlexAlgo-based FA slice to which the slice user belongs;

The SRv6 Policy tunnel is a tunnel in the FlexAlgo-based FA slice topology to which the slice user belongs.

During implementation, the binding module is further used to establish a corresponding relationship between the slice identifier SliceID and the SRv6 Policy tunnel, that is, assigning a slice identifier SliceID that can meet the slice user resource requirements for the SRv6 Policy tunnel.

During implementation, the division module is further used to identify sub-link resources with the sub-link identifier Sub-Link Num. Each sub-link has its own exclusive underlying physical resources. By saving and maintaining Sub-Link Num and various types of sub-links The corresponding relationship between road resource IDs is used to be compatible with various types of underlying physical sub-link resources.

In the implementation, the binding module is further used in routing capability type, length, value Router CAPABILITY TLV based on IPv6 source routing technology subtype, length, value SRv6Capabilities sub-TLV and border gateway protocol link type BGP-LS based IPv6 source routing technology capability type, length, and value SRv6 Capability TLV adds an identifier to indicate that the device supports the ability to carry SliceID on the forwarding plane and perform slice processing.

In the implementation, the binding module is further used to add an identifier to the end segment identifier subtype, length, and value End.X SID sub-TLV structure to indicate that the device is an adjacent SID of a virtual member sublink instead of a physical link Adjacent SID of the road.

During implementation, the binding module is further configured to use the link slice information subtype, length, value Sub-TLV and slice resource subtype, length, value Sub-sub-TLV structure to announce the number of link slices and corresponding resource information.

In implementation, the division module is further used to perform one or a combination of the following processes:

When assigning the number of SliceIDs, after assigning a preset number of SliceIDs to each FA slice on the SDN controller, send them to the device;

According to the needs of slice users in the FA slice topology, assign SliceID resources on the forwarding plane to each user, and establish the corresponding relationship between SliceID and the resource requirements of each slice user. Unallocated SliceIDs are temporarily reserved and have no resource requirements;

SliceIDs that have not been assigned bandwidth requirements are updated according to the bandwidth requirements of subsequent new slice users, and the updated information is sent to the device synchronously.

In practice, the segmentation module is further used to maintain and/or update the following information:

FA slice SliceID, virtual member sub-link End.X SID, total reserved resources of virtual member sub-link End.X SID, corresponding relationship of The total remaining slice resources of the link.

During implementation, the binding module is further used to carry the SliceID information of the forwarding plane in the BGP SRv6 Policy message.

During implementation, the binding module is further used to configure the mapping relationship between the Color template and the SliceID on the forwarding plane, so that the tunnel head node device obtains the corresponding SliceID according to the Color attribute of the SRv6 Policy.

During implementation, the binding module is further used to perform path calculation based on the SliceID information, the FA topology, and the remaining slice resource information of the virtual member sub-link End.X corresponding to the FA topology, and use the virtual member sub-link End.X SID to perform path calculation. routing.

During implementation, the binding module is further used to direct the slice user traffic to the SRv6 Policy tunnel for transmission, so that the forwarding device, when forwarding the message, according to the indication of the slice flag in the virtual member sub-link End.X SID, Determine the sub-link physical resources of the slice on the outgoing interface, and forward the packet through the corresponding sub-link physical resource sub-interface.

During implementation, the binding module is further used to guide slice user traffic to the SRv6 Policy tunnel for transmission, and update one or a combination of the following information according to the information reported by the device: the SliceID of the virtual member sub-link and the sub-link resource Sub- Correspondence between Link Num, status of sub-link resource Sub-Link Num, virtual member sub-link remaining slice resource information.

During implementation, the division module is further configured to divide the value space of the sub-link resource ID to distinguish the sub-link resource ID used by the FA slice and the user slice.

During implementation, the division module is further used to allocate the sub-link resource corresponding to the Sub-Link Num whose upper 4 bits are 1 to the FA slice when dividing the value space of the sub-link resource identifier, and the remaining Sub-Link Num is taken as The value space is allocated for use by user slices.

During implementation, the partitioning module is further used to reserve the remaining bandwidth resources in the total bandwidth not allocated to user slices in each FA slice topology for shared use by non-slice users in the FA slice topology, and the traffic of non-slice users passes through SRv6 BE bearer.

During implementation, the division module is further used for the FA slice to divide the corresponding number of FA slices based on FlexAlgo with a one-to-one correspondence for the network according to the number of industries or virtual operators;

According to the industry or virtual operator to which the slice user belongs, the FlexAlgo-based FA slice to which it belongs is determined.

For the convenience of description, each part of the device described above is divided into various modules or units by function and described separately. Of course, when implementing the present invention, the functions of each module or unit can be implemented in one or more pieces of software or hardware.

Figure 17 is a schematic structural diagram of a network device serving as a forwarding device. As shown in the figure, the forwarding device includes:

The processor 1700 is used to read the program in the memory 1720 and execute the following processes:

When providing services for the slice users, direct their service traffic to the SRv6 Policy tunnel for transmission;

Establish the corresponding relationship between the SliceID and the sub-link resources of each interface on the SRv6 Policy tunnel path;

The transceiver 1710 is used for receiving and sending data under the control of the processor 1700 .

In implementation, it further includes:

One or a combination of the following information is flooded in the IGP: the End.X SID of each FA slice virtual member sub-link on the link, the total reserved bandwidth, the number of SliceIDs, or the resource information corresponding to each SliceID.

In implementation, it further includes:

Make the tunnel head node device obtain the SliceID from the BGP SRv6 Policy message sent by the SDN controller, and write it into the corresponding position of the forwarding plane message.

During the implementation, when the slice user traffic is directed to the SRv6 Policy tunnel for transmission, according to the SliceID carried in the forwarding message of the slice user, a sublink resource that can meet the resource requirements of the SliceID is allocated from the idle sublink resources of the corresponding physical outbound interface. Link resources are used for forwarding, and the corresponding relationship between SliceID and sub-link resources and the status of sub-link resources are maintained.

During implementation, when slice user traffic is directed to the SRv6 Policy tunnel for transmission, when the first slice packet arrives at the device, the device searches the local table to obtain the bandwidth resources required by the SliceID according to the SliceID carried in the Find the sub-link resource Sub-Link Num of unoccupied bandwidth in the sub-link resource table of the device, assign it to the SliceID, forward the slice user packet from the corresponding sub-port, and update the local sub-link resource Sub -Link Num status is occupied, and report to the SDN controller through telemetry Telemetry to update one or a combination of the following information: sub-link resource Sub-Link Num occupancy, SliceID and Sub-Link Num correspondence, Sub-Link Num state.

Wherein, in FIG. 17 , the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by the processor 1700 and various circuits of the memory represented by the memory 1720 are linked together. The bus architecture can also link together various other circuits such as peripherals, voltage regulators, and power management circuits, etc., which are well known in the art and therefore will not be further described herein. The bus interface provides the interface. Transceiver 1710 may be a plurality of elements, including a transmitter and a receiver, providing a means for communicating with various other devices over transmission media. The processor 1700 is responsible for managing the bus architecture and general processing, and the memory 1720 can store data used by the processor 1700 when performing operations.

An embodiment of the present invention also provides a network device, including:

A transmission module, configured to direct its service traffic to the SRv6Policy tunnel for transmission when providing services to users of the slice;

The relationship module is used to establish the corresponding relationship between the SliceID and the sub-link resources of each interface on the SRv6 Policy tunnel path.

During implementation, the relationship module is further used to flood and notify one or a combination of the following information in the interior gateway protocol IGP: the End.X SID of each FA slice virtual member sub-link on the link, the total reserved bandwidth, the number of SliceIDs, or Each SliceID corresponds to resource information.

During implementation, the relationship module is further used to enable the tunnel head node device to obtain the SliceID from the BGP SRv6Policy message sent by the SDN controller, and write it into the corresponding position of the forwarding plane message.

During implementation, when the transmission module is further used to guide the slice user traffic to the SRv6 Policy tunnel for transmission, according to the SliceID carried in the slice user forwarding message, allocate a sub-link resource that can meet the requirements from the idle state sub-link resources of the corresponding physical outbound interface. The sub-link resource required by the SliceID resource is forwarded, and the corresponding relationship between the SliceID and the sub-link resource and the state of the sub-link resource are maintained.

During implementation, the transmission module is further used to guide slice user traffic to the SRv6 Policy tunnel for transmission. When the first slice packet arrives at the device, the device will check the local table to obtain the required bandwidth for the SliceID according to the SliceID carried in the forwarded packet. After resources, find the unoccupied sub-link resource Sub-Link Num from the sub-link resource table of the local device, assign it to the SliceID, forward the slice user packets from the corresponding sub-port, and update the local The status of sub-link resource Sub-Link Num is occupied, and one or a combination of the following information is reported to the SDN controller through telemetry: sub-link resource Sub-Link Num occupancy, SliceID and Sub-Link Num correspondence , Sub-Link Num state.

For the convenience of description, each part of the device described above is divided into various modules or units by function and described separately. Of course, when implementing the present invention, the functions of each module or unit can be implemented in one or more pieces of software or hardware.

An embodiment of the present invention also provides a computer-readable storage medium, where the computer-readable storage medium stores a computer program for executing the above transmission method.

For specific implementation, please refer to the implementation of the transmission method.

In summary, in the technical solutions provided by the embodiments of the present invention, it is provided:

The SRv6 Capabilities sub-TLV of the Router CAPABILITY TLV and the SRv6Capability TLV of BGP-LS are extended, and a flag is added to indicate that the device supports the slice processing capability of the forwarding plane.

A flag is added to the extended End.X SID sub-TLV structure to indicate that it is the adjacent SID of the virtual member sub-link instead of the adjacent SID of the physical link.

The newly defined link slice information Sub-TLV and slice resource Sub-sub-TLV structures are used to announce the number of link slices and corresponding resource information.

Further, a method for IGP flood notification of the End.XSID, total reserved bandwidth, number of SliceIDs, and resource information corresponding to each SliceID of virtual member sublinks of each FA slice on the link is provided.

The End.X SID allocation of virtual member sub-links in the FA slice topology, the mechanism and method of total resource reservation, and the allocation rules for the number of SliceIDs on the forwarding plane in the FA slice topology.

On the controller, maintain the corresponding relationship between FA slice ID, virtual member sub-link End.X SID and its total reserved resources, and the number of SliceIDs, the resource requirements and status of each SliceID, the total remaining slice resources of virtual member sub-links, etc. Maintenance and updating of information.

Extends the BGP SRv6 Policy structure to carry SliceID information on the forwarding plane.

Further, a method is provided in which the tunnel head node obtains the SliceID from the BGP SRv6 Policy message sent by the controller, and writes it into the corresponding position of the message on the forwarding plane.

Configure the mapping relationship between the Color template and the SliceID on the forwarding plane. The head node device obtains the corresponding SliceID according to the Color attribute of the SRv6 Policy.

The operation mechanism and method of SliceID value allocation, corresponding resource allocation, and state maintenance of the second-level slice user forwarding plane.

The controller performs path calculation based on SliceID information, FA topology and the remaining slice resources of the corresponding virtual member sub-link End.X, and uses the processing mechanism and method of virtual member sub-link End.X SID for path arrangement.

When forwarding packets, the forwarding device further determines the physical resources of the slice sub-links on the outbound interface according to the indication of setting the slice flag in the virtual member sub-link End. The processing mechanism and method for packet forwarding by the resource sub-interface.

According to the SliceID carried in the packet forwarded by the slice user, the forwarding device allocates a sublink resource (such as MTN subinterface, VLAN enhanced subinterface, etc.) , channelized sub-interface resources, FlexE sub-interfaces, independent QoS queues, etc.); the corresponding relationship between SliceID and sub-link resources and the dynamic maintenance mechanism and method of the status of sub-link resources.

Furthermore, it provides the introduction of Sub-Link Num to uniformly identify the underlying physical sub-link resources. Each sub-link has its own exclusive underlying physical resources, such as MTN sub-interfaces, VLAN enhanced sub-interfaces, channelized sub-interface resources, FlexE Sub-interfaces, independent QoS queues, etc. are compatible with various types of underlying physical sub-link resources by maintaining the correspondence between Sub-Link Num and the above-mentioned types of sub-link resource IDs.

Further, a mechanism and method are provided for the forwarding device to synchronize the corresponding relationship between the SliceID and the Sub-LinkNum and the occupancy of the sub-link resource Sub-LinkNum to the controller in real time through Telemetry.

Further, it is provided that the controller performs the correspondence between the SliceID of the virtual member sub-link and the sub-link resource Sub-Link Num, the state of the sub-link resource Sub-Link Num and the virtual member sub-link according to the above information reported by the device A mechanism and method for dynamically updating and maintaining information such as link remaining slice resources.

By dividing the value space of the sub-link resource identifiers, the sub-link resource identifiers used by the first-level slice and the second-level slice are distinguished.

Further, it is provided that the sub-link resources corresponding to the Sub-Link Num whose upper 4 bits are 1 are allocated to the first-level slice of the FA, and the rest of the value space of the Sub-Link Num is allocated to the second-level slice.

In each FA slice topology, the remaining bandwidth resources not allocated to secondary user slices in the reserved total bandwidth are shared by non-slice users in the FA topology, and the traffic of non-slice users is carried by SRv6 BE.

During implementation, the FA slice is based on the number of industries or virtual operators, and the network is divided into a corresponding number of FA slices based on FlexAlgo that have a one-to-one correspondence;

The SDN controller determines the FlexAlgo-based FA slice to which the slice user belongs according to the industry or virtual operator to which it belongs.

This solution can realize the exclusive sharing of resources of each slice on the same physical link. Compared with the existing FlexAlgo technology, it can solve the problem that each slice of FlexAlgo can only share one physical link exclusively, and the isolation granularity is coarse. The problem of hard isolation of slices in large-scale deployment.

This solution can provide the underlying physical resource guarantee for slicing and realize hard slicing. Compared with the existing SR-TE and SRPolicy technologies, it can solve the problem of soft isolation only through tunnels and complete sharing of physical resources.

The separate FA enhancement technology and the separate SRv6 Policy + forwarding plane slicing technology can only provide one-level slicing services. This solution provides a dynamically adjustable sub-link-level resource-guaranteed two-level slicing service for the data bearer network, which can It meets the requirements of the two-level slicing scenario of industry slicing + user slicing.

Those skilled in the art should understand that the embodiments of the present invention may be provided as methods, systems, or computer program products. Accordingly, the present invention can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, optical storage, etc.) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It should be understood that each procedure and/or block in the flowchart and/or block diagram, and a combination of procedures and/or blocks in the flowchart and/or block diagram can be realized by computer program instructions. These computer program instructions may be provided to a general purpose computer, special purpose computer, embedded processor, or processor of other programmable data processing equipment to produce a machine such that the instructions executed by the processor of the computer or other programmable data processing equipment produce a An apparatus for realizing the functions specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to operate in a specific manner, such that the instructions stored in the computer-readable memory produce an article of manufacture comprising instruction means, the instructions The device realizes the function specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

These computer program instructions can also be loaded onto a computer or other programmable data processing device, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby The instructions provide steps for implementing the functions specified in the flow chart or blocks of the flowchart and/or the block or blocks of the block diagrams.

Obviously, those skilled in the art can make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. Thus, if these modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalent technologies, the present invention also intends to include these modifications and variations.

Claims (28)

1. A transmission method, characterized in that, comprising: The software-defined network SDN controller divides the link corresponding to each network device interface into multiple sub-link resources according to the slice user resource requirements; Establish the corresponding relationship between the slice identifier SliceID and resource requirements; According to the resource requirements of the slice user, establish a one-to-one binding IPv6-based source routing technology policy SRv6 Policy tunnel for the user, and establish a corresponding relationship between the slice identifier SliceID and the SRv6 Policy tunnel. 2. The method of claim 1, further comprising: A slice user is a user in the flexible algorithm FA slice based on the flexible algorithm FlexAlgo; SliceID is the SliceID in the FlexAlgo-based FA slice to which the slice user belongs; The SRv6 Policy tunnel is a tunnel in the FlexAlgo-based FA slice topology to which the slice user belongs. 3. The method of claim 1, further comprising: Establishing the correspondence between the slice identifier SliceID and the SRv6 Policy tunnel is to assign a slice identifier SliceID that can meet the slice user resource requirements for the SRv6 Policy tunnel. 4. The method of claim 1, further comprising: The sub-link identifier Sub-Link Num is used to identify sub-link resources. Each sub-link has its own exclusive underlying physical resources. By saving and maintaining the correspondence between Sub-Link Num and various types of sub-link resource IDs, Compatible with various types of underlying physical sub-link resources. 5. The method of claim 1, further comprising: IPv6-based source routing technical capability subtype, length, value SRv6 Capabilities sub-TLV of routing capability type, length, value Router CAPABILITY TLV and IPv6-based source routing technical capability type of Border Gateway Protocol link type BGP-LS, Length and value SRv6 Capability TLV adds flags to indicate that the device supports the ability to carry SliceID on the forwarding plane and perform slice processing. 6. The method of claim 1, further comprising: Add an identifier to the end segment identifier subtype, length, and value End.X SID sub-TLV structure to indicate that the device is an adjacent SID of a virtual member sublink, not an adjacent SID of a physical link. 7. The method of claim 1, further comprising: Use the link slice information subtype, length, value Sub-TLV and slice resource subtype, length, value Sub-sub-TLV structure to announce the number of link slices and corresponding resource information. 8. The method according to claim 1 or 2, further comprising one of the following processes or a combination thereof: When assigning the number of SliceIDs, after assigning a preset number of SliceIDs to each FA slice on the SDN controller, send them to the device; According to the needs of slice users in the FA slice topology, the SDN controller allocates SliceID resources on the forwarding plane for each user, and establishes the corresponding relationship between the SliceID and the resource requirements of each slice user. The unallocated SliceID is temporarily reserved and has no resource requirements; SliceIDs that have not been assigned bandwidth requirements are updated according to the bandwidth requirements of subsequent new slice users, and the updated information is sent to the device synchronously. 9. The method according to claim 1 or 2, further comprising: The SDN controller maintains and/or updates the following information: FA slice SliceID, virtual member sub-link End.X SID, total reserved resources of virtual member sub-link End.X SID, corresponding relationship of The total remaining slice resources of the link. 10. The method of claim 1, further comprising: The SliceID information of the forwarding plane is carried in the BGPSRv6 Policy message. 11. The method of claim 1, further comprising: Configure the mapping relationship between the Color template and the SliceID on the forwarding plane, so that the tunnel head node device can obtain the corresponding SliceID according to the Color attribute of the SRv6Policy. 12. The method according to claim 1 or 2, further comprising: The SDN controller performs path calculation based on the SliceID information, the FA topology, and the remaining slice resource information of the virtual member sub-link End.X corresponding to the FA topology, and uses the virtual member sub-link End.XSID to perform path arrangement. 13. The method according to claim 1, wherein when guiding slice user traffic to the SRv6Policy tunnel for transmission, the forwarding device is configured according to the slice flag in the virtual member sublink End.X SID when forwarding the message. bit, determine the sub-link physical resource of the slice on the outbound interface, and forward the message through the corresponding sub-link physical resource sub-interface. 14. The method according to claim 13, wherein when guiding slice user traffic to the SRv6Policy tunnel for transmission, the SDN controller updates one or a combination of the following information according to the information reported by the device: Correspondence between SliceID and sub-link resource Sub-Link Num, status of sub-link resource Sub-Link Num, virtual member sub-link remaining slice resource information. 15. The method of claim 1, further comprising: By dividing the value space of the sub-link resource identifiers, it is used to distinguish the sub-link resource identifiers used by the FA slice and the user slice. 16. The method according to claim 15, wherein when dividing the value space of the sub-link resource identifier, the sub-link resource corresponding to the Sub-Link Num whose upper 4 bits are 1 is allocated to the FA slice for use , and the remaining Sub-Link Num value space is allocated to user slices. 17. The method of claim 1 or 2, further comprising: In each FA slice topology, the remaining bandwidth resources not allocated to user slices in the reserved total bandwidth are shared by non-slice users in the FA slice topology, and the traffic of non-slice users is carried by SRv6 BE. 18. The method according to any one of claims 2 to 17, wherein the FA slicing is based on the number of industries or virtual operators, and the network is divided into a corresponding number of FlexAlgo-based FAs that have a one-to-one correspondence. slice; The SDN controller determines the FlexAlgo-based FA slice to which the slice user belongs according to the industry or virtual operator to which it belongs. 19. A transmission method, comprising: When the forwarding device provides services for the users of the slice, it directs its service traffic to the SRv6 Policy tunnel for transmission; On the SRv6 Policy tunnel path, establish the correspondence between the SliceID and the sublink resources of each interface. 20. The method of claim 19, further comprising: One or a combination of the following information is flooded in the IGP: the End.X SID of each FA slice virtual member sub-link on the link, the total reserved bandwidth, the number of SliceIDs, or the resource information corresponding to each SliceID. 21. The method of claim 19, further comprising: Make the tunnel head node device obtain the SliceID from the BGPSRv6 Policy message sent by the SDN controller, and write it into the corresponding position of the forwarding plane message. 22. The method according to claim 19, wherein when the forwarding device directs the slice user traffic to the SRv6Policy tunnel for transmission, according to the SliceID carried in the slice user forwarding message, the sub-chain in the idle state corresponding to the physical outgoing interface Allocate a sub-link resource that can meet the resource requirements of the SliceID for forwarding, and maintain the corresponding relationship between the SliceID and the sub-link resource and the status of the sub-link resource. 23. The method according to claim 22, wherein when the forwarding device guides slice user traffic to the SRv6Policy tunnel for transmission, when the first slice message arrives at the device, the device makes the device according to the SliceID carried in the forwarding message, After checking the local table to obtain the bandwidth resource required by the SliceID, find the unoccupied sub-link resource Sub-Link Num from the sub-link resource table of the local device, assign it to the SliceID, and send the user packet of the slice to the The corresponding sub-port is forwarded, and the state of the local sub-link resource Sub-Link Num is updated to be occupied, and one or a combination of the following information is reported to the SDN controller through telemetry Telemetry: sub-link resource Sub-Link Num occupancy, Correspondence between SliceID and Sub-Link Num, Sub-Link Num status. 24. A network device, comprising: The processor, which reads the program in the memory, performs the following processes: Divide the link corresponding to each network device interface into multiple sub-link resources according to the user resource requirements of the slice; Establish the corresponding relationship between the slice identifier SliceID and resource requirements; According to the resource requirements of the slice user, establish a one-to-one binding IPv6-based source routing technology strategy SRv6 Policy tunnel for the user, and establish a corresponding relationship between the slice identifier SliceID and the SRv6 Policy tunnel; Transceiver, used to receive and transmit data under the control of the processor. 25. A network device, comprising: A division module, configured to divide the link corresponding to each network device interface into multiple sub-link resources according to the slice user resource requirements; The corresponding module is used to establish the corresponding relationship between the slice identifier SliceID and the resource requirement; The binding module is configured to establish a one-to-one binding IPv6-based source routing technology policy SRv6 Policy tunnel for the user according to the resource requirements of the slice user, and establish a corresponding relationship between the slice identifier SliceID and the SRv6 Policy tunnel. 26. A network device, comprising: The processor, which reads the program in the memory, performs the following processes: When providing services for the slice users, direct their service traffic to the SRv6 Policy tunnel for transmission; Establish the corresponding relationship between the SliceID and the sub-link resources of each interface on the SRv6 Policy tunnel path; Transceiver, used to receive and transmit data under the control of the processor. 27. A network device, comprising: A transmission module, configured to direct its service traffic to the SRv6Policy tunnel for transmission when providing services to users of the slice; The relationship module is used to establish the corresponding relationship between the SliceID and the sub-link resources of each interface on the SRv6 Policy tunnel path. 28. A computer-readable storage medium, wherein the computer-readable storage medium stores a computer program for executing the method according to any one of claims 1 to 23.

Images