CN115277548B

CN115277548B - A transmission method, device and storage medium

Info

Publication number: CN115277548B
Application number: CN202110480372.9A
Authority: CN
Inventors: 姜文颖; 程伟强; 杨雪; 龚立艳
Original assignee: China Mobile Communications Group Co Ltd; Research Institute of China Mobile Communication Co Ltd
Current assignee: China Mobile Communications Group Co Ltd; Research Institute of China Mobile Communication Co Ltd
Priority date: 2021-04-30
Filing date: 2021-04-30
Publication date: 2024-12-31
Anticipated expiration: 2041-04-30
Also published as: CN115277548A

Abstract

The present invention discloses a transmission method, device and storage medium, including: an SDN controller divides the link corresponding to each network device interface into multiple sub-link resources according to the resource requirements of slice users; establishes a corresponding relationship between a slice identifier SliceID and resource requirements; establishes a one-to-one binding IPv6-based source routing technology policy SRv6Policy tunnel for the user according to the resource requirements of the slice user, and establishes a corresponding relationship between the slice identifier SliceID and the SRv6Policy tunnel. When providing services to the slice user, the forwarding device guides its service traffic to the SRv6Policy tunnel for transmission; establishes a corresponding relationship between SliceID and the sub-link resources of each interface on the SRv6Policy tunnel path. The present invention can meet the first-level slicing requirements of the sub-link granularity for exclusive use of the underlying physical resources, and can also meet the two-level slicing requirements of the sub-link granularity for exclusive use of the underlying physical resources of the industry or virtual operator slice + user slice.

Description

Transmission method, device and storage medium

Technical Field

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

Background

Existing slicing techniques for data bearers include FlexAlgo (flexible algorithm) techniques, SR-TE (segment routing-transport engineering, segmentRouting-TRAFFIC ENGINEERING), SRv Policy (SRv 6 Policy; SRv6: IPv6 based source routing techniques, segment Routing IPv 6) tunneling techniques.

1. The FlexAlgo (FA) technology is briefly described below.

The FA is based on an IGP (interior gateway protocol ) single topology, each node and each L3 link correspond to one or more FA algorithm spaces, and are issued by the IGP protocol to form an IGP sub-algorithm space.

The FA algorithm contains three parts, METRICTYPE (metric type), calcType (calculation type) and Constraint, and different sub-topologies are formed as a result of different FA algorithms. Therefore, the physical network can be divided into a plurality of virtual networks through FlexAlgo, different SIDs (segment identifiers, SEGMENT IDENTIFIER) are used for message encapsulation under different FA slices, different addresses are calculated independently, and the message is guided to be forwarded in the corresponding FA slices.

Fig. 1 is a schematic diagram of a physical networking topology of a device, and fig. 2 is a schematic diagram of a sub-topology of different FA slices, as shown in the figure, where different nodes join different FAs based on IGP METRIC or TE (transmission engineering, TRAFFIC ENGINEERING) Metric calculation, and different physical links join different FlexAlgo by setting color attributes and matching calculation constraints (such as affinity attributes, including a color) of different FAs. Within each FA slice, each node is assigned an independent SID. The resulting different FA slice sub-topologies are shown in fig. 2:

And (3) automatically guiding the service, namely carrying the FA-ID when the prefix SID is announced, and indicating that a specific FA algorithm needs to be used for calculating the prefix to the destination. The service may find the corresponding FA-LSP (ri replacement principle The Liskov Substitution Principle) according to a single prefix SID or a specific SR (Segment Routing) list based on the FA, etc.

2. The SR-TE, SRv6 Policy techniques are briefly described below.

SR-TE and SRv Policy are source routing tunneling techniques, and may calculate paths SEGMENTLIST < SID1, SID2,.. SIDn > meeting the requirements in the network for the user based on SLA (Service-level agreement) requirements, such as delay and bandwidth, of the user, and instruct the user to forward the message along a specified path in the network.

Tunnel path SEGMENTLIST (segment list) may be organized with either a node SID or an adjacency SID. When each hop SID 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, then the tunnel path is a one-hop loose path, as there may be different reachable links between the two nodes.

1. The FlexAlgo slicing technique has the following defects:

The FlexAlgo technology can only ensure node selection and physical link selection, realize coarse granularity slicing at the physical port level, but the existing network cannot ensure that a plurality of links exist between all nodes, so that the end-to-end slice resource exclusive sharing cannot be ensured, and the scheme can only singly share a certain physical link, cannot realize that a plurality of sub-link resources are distributed to different slice users, so that great resource waste can be caused for scenes with physical isolation slice requirements, and the scheme is basically unavailable.

2. The disadvantage of the SR-TE, SRv6 Policy technique for slicing is that:

The SR-TE and SRv Policy solve the path planning problem, guide the message to avoid the congestion section and forward along the designated path, but the resources, such as bandwidth, on each physical link on the forwarding path cannot be guaranteed, because the link resources are shared by all tunnels and cannot be associated with the sub-link physical resources of the bottom layer, only the logical isolation is realized, and the hard slice requirement of the exclusive sharing of the resources required by the user cannot be met.

Thus, the prior art is deficient in that there is no slicing scheme that can correlate the underlying sub-link physical resources.

Disclosure of Invention

The invention provides a transmission method, a transmission device and a storage medium, which are used for solving the problem that no slicing scheme capable of being related to the physical resources of a bottom-layer sub-link exists.

The invention provides the following technical scheme:

A transmission method, comprising:

The software defined network SDN controller divides the links corresponding to each network equipment interface into a plurality of sub-link resources according to the resource requirements of the slicing users;

establishing a corresponding relation between the slice identifier SliceID and the resource requirement;

And establishing a one-to-one binding IPv 6-based source routing technical Policy SRv Policy tunnel for the user according to the resource requirement of the slicing user, and establishing a corresponding relation between slice identifiers SliceID and SRv Policy tunnels.

In practice, further comprising:

slice users are users in a flexible algorithm FA slice based on flexible algorithm FlexAlgo;

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

SRv6 Policy tunnels are tunnels in the FlexAlgo-based FA slice topology to which the slice user belongs.

In practice, further comprising:

The corresponding relation between the slice identifier SliceID and the SRv Policy tunnel is established by allocating a slice identifier SliceID capable of meeting the resource requirements of the slice user to the SRv Policy tunnel.

In practice, further comprising:

Sub-Link Num of Sub-Link identifier is adopted to identify Sub-Link resources, each Sub-Link has own independent bottom physical resources, and the Sub-Link Num is compatible with each type of bottom physical Sub-Link resources by storing and maintaining the corresponding relation between Sub-Link Num and each type of Sub-Link resource ID.

In practice, further comprising:

IPv 6-based source routing technology Capability type, length, value SRv Capabilities sub-TLV and border gateway protocol link type BGP-LS at routing Capability type, length, value Router CAPABILITY TLV are identified with an increase in IPv 6-based source routing technology Capability type, length, value SRv6 Capabilities TLV to indicate that the device supports the Capability to carry SliceID on the forwarding plane and perform slicing.

In practice, further comprising:

An identification is added to the end segment identifier subtype, length, value end.x SID sub-TLV structure to indicate that the device is an adjacency SID of the virtual member sub-link, not an adjacency SID of the physical link.

In practice, further comprising:

The link slice number and corresponding resource information are advertised using a link slice information subtype, length, value Sub-TLV and slice resource subtype, length, value Sub-TLV structure.

In practice, one or a combination of the following treatments are further included:

when SliceID quantity is distributed, distributing preset quantity SliceID for each FA slice on the SDN controller, and then issuing the chips to equipment;

The SDN controller allocates forwarding plane SliceID resources for each user according to the requirements of the slicing users in the FA slicing topology, establishes the corresponding relation between SliceID and the resource requirements of each slicing user, and is not temporarily reserved by SliceID allocated and has no resource requirements;

SliceID, updating according to the bandwidth requirement of the subsequent newly added slice user, and synchronously transmitting the updating information to the equipment.

In practice, 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 for virtual member sub-link end.x SID, correspondence of SliceID number, demand for each SliceID resource, status of each SliceID resource, total remaining slice resources for virtual member sub-link.

In practice, further comprising:

SliceID information of the forwarding plane is carried in BGP SRv Policy messages.

In practice, further comprising:

And configuring a mapping relation between the Color template and the forwarding plane SliceID to enable the tunnel head node equipment to acquire a corresponding SliceID according to the Color attribute of the SRv Policy.

In practice, further comprising:

the SDN controller calculates paths based on SliceID information, FA topology and residual slice resource information of virtual member sub-link End.X corresponding to the FA topology, and uses virtual member sub-link End.XSID to carry out path arrangement.

In the implementation, when the user flow of the slice is guided to SRv Policy tunnel transmission, the forwarding device determines the physical resource of the sub-link of the slice on the outgoing interface according to the indication of the slice mark setting in the end.X SID of the virtual member sub-link when the message is forwarded, and forwards the message through the sub-interface of the physical resource of the corresponding sub-link.

In the implementation, when the slice user traffic is guided to SRv Policy tunnel transmission, the SDN controller updates one or a combination of SliceID of the virtual member Sub-Link and Sub-Link resource Sub-Link Num, sub-Link resource Sub-Link Num state and virtual member Sub-Link residual slice resource information according to the information reported by the equipment.

In practice, further comprising:

the sub-link resource identification used by the FA slice and the user slice is distinguished by dividing the value space of the sub-link resource identification.

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

In practice, further comprising:

and reserving the residual bandwidth resources which are not allocated to the user slices in the total bandwidth in each FA slice topology, and sharing the use of the non-slice users in the FA slice topology, wherein the traffic of the non-slice users is carried through SRv BE.

In implementation, the FA slice is a FlexAlgo FA slice based on a one-to-one correspondence relationship of dividing a corresponding number for a network according to the number of industries or virtual operators;

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

A transmission method, comprising:

When the forwarding equipment provides service for the slicing user, the service flow of the forwarding equipment is guided to SRv Policy tunnel transmission;

and establishing SliceID corresponding relation with each interface sub-link resource on SRv Policy tunnel paths.

In practice, further comprising:

The interior gateway protocol IGP flood advertises one or a combination of end.x SID per FA slice virtual member sub-link, reserved total bandwidth, sliceID number, or corresponding resource information per SliceID on the link.

In practice, further comprising:

And enabling the tunnel head node equipment to acquire SliceID from BGP SRv Policy messages issued by the SDN controller and writing the SliceID into a position corresponding to the forwarding plane message.

In implementation, when the forwarding device directs the flow of the slice user to SRv Policy tunnel transmission, according to SliceID carried in the forwarding message of the slice user, one sub-link resource capable of meeting the SliceID resource requirement is allocated from the sub-link resources in the idle state corresponding to the physical outgoing interface to forward, and the corresponding relation between SliceID and the sub-link resource and the state of the sub-link resource are maintained.

In implementation, when the forwarding device directs the slice user traffic to SRv Policy tunnel transmission, and when the first slice message arrives at the device, the device searches the local table to obtain the bandwidth resource needed by SliceID according to SliceID carried in the forwarding message, finds the Sub-Link resource Sub-Link Num of the unoccupied bandwidth from the local device Sub-Link resource table, distributes the Sub-Link resource Sub-Link Num to SliceID, forwards the slice user message from the corresponding Sub-port, updates the state of the local Sub-Link resource Sub-Link Num to occupied, and reports one or a combination of updated Sub-Link resource Sub-Link Num occupation, sliceID and Sub-Link Num corresponding relation, sub-Link Num state to the SDN controller through telemetry TELEMETRY.

A network apparatus, comprising:

A processor for reading the program in the memory, performing the following process:

dividing a link corresponding to each network equipment interface into a plurality of sub-link resources according to the resource requirements of slicing users;

Establishing a one-to-one binding IPv 6-based source routing technical Policy SRv Policy tunnel for the user according to the resource requirement of the slicing user, and establishing a corresponding relation between slice identifiers SliceID and SRv Policy tunnels;

and a transceiver for receiving and transmitting data under the control of the processor.

In practice, further comprising:

distributing a forwarding plane SliceID resource for each user according to the requirements of the slicing users in the FA slicing topology, and establishing a corresponding relation between SliceID and the resource requirements of each slicing user, wherein the unallocated SliceID is reserved temporarily and has no resource requirement;

In practice, further comprising:

the following information is maintained and/or updated:

In practice, further comprising:

and performing path calculation based on SliceID information, FA topology and residual slice resource information of the virtual member sub-link End.X corresponding to the FA topology, and performing path arrangement by using the virtual member sub-link End.X SID.

In practice, further comprising:

And determining the FA slice based on FlexAlgo to which the slice user belongs according to the industry or virtual operator to which the slice user belongs.

A network apparatus, comprising:

The dividing module is used for dividing the links corresponding to each network equipment interface into a plurality of sub-link resources according to the resource requirements of the slicing users;

the corresponding module is used for establishing a corresponding relation between the slice identifier SliceID and the resource requirement;

And the binding module is used for establishing one-to-one binding for the users based on the IPv6 source routing technical Policy SRv Policy tunnel according to the resource requirements of the slice users, and establishing the corresponding relation between slice identifiers SliceID and SRv Policy tunnels.

In practice, further comprising:

In implementation, the binding module is further configured to establish a correspondence between the slice identifier SliceID and the SRv Policy tunnel, and allocate a slice identifier SliceID capable of meeting the resource requirement of the slice user to the SRv Policy tunnel.

In implementation, the partitioning module is further configured to identify Sub-Link resources by using Sub-Link identifiers Sub-Link Num, where each Sub-Link has a bottom physical resource that is unique to itself, and is compatible with each type of bottom physical Sub-Link resource by storing and maintaining a corresponding relationship between Sub-Link Num and each type of Sub-Link resource ID.

In implementation, the binding module is further configured to add an identifier to the IPv 6-based source routing technology Capability type, length, value Router CAPABILITY TLV, the IPv 6-based source routing technology Capability subtype, length, value SRv Capabilities sub-TLV, and border gateway protocol link type BGP-LS, the IPv 6-based source routing technology Capability type, length, value SRv Capabilities TLV, to indicate that the device supports the Capability of carrying SliceID on the forwarding plane and performing slicing processing.

In practice, the binding module is further configured to add an identification to the end segment identifier subtype, length, value end.x SID sub-TLV structure to indicate that the device is an adjacency SID of the virtual member sub-link, and not an adjacency SID of the physical link.

In an implementation, the binding module is further configured to advertise the number of link slices and corresponding resource information using a link slice information subtype, length, value Sub-TLV and slice resource subtype, length, value Sub-TLV structure.

In implementations, the partitioning module is further configured to perform one or a combination of the following:

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

In implementation, the binding module is further configured to carry SliceID information of the forwarding plane in BGP SRv Policy messages.

In implementation, the binding module is further configured to configure a mapping relationship between the Color template and the forwarding plane SliceID, so that the tunnel head node device obtains a corresponding SliceID according to the Color attribute of SRv Policy.

In implementation, the binding module is further configured to perform path computation 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 perform path arrangement using the virtual member sub-link end.x SID.

In implementation, the binding module is further configured to, when the slice user traffic is directed to SRv Policy tunnel transmission, enable the forwarding device to determine a physical resource of the slice sub-link on the outgoing interface according to the indication of the slice flag set in the end.x SID of the virtual member sub-link when the message is forwarded, and forward the message through the corresponding sub-link physical resource sub-interface.

In implementation, the binding module is further configured to update one or a combination of the corresponding relationship between SliceID of the virtual member Sub-Link and Sub-Link resource Sub-Link Num, sub-Link resource Sub-Link Num status, and remaining slice resource information of the virtual member Sub-Link according to information reported by the device when the slice user traffic is directed to SRv Policy tunnel transmission.

In practice, the dividing module is further configured to divide the value space of the sub-link resource identifier to distinguish the sub-link resource identifier used by the FA slice from the sub-link resource identifier used by the user slice.

In implementation, the dividing module is further configured to allocate Sub-Link resources corresponding to Sub-Link Num with high 4 bits being 1 to FA slices for use when dividing the value space of the Sub-Link resource identifier, and allocate the remaining Sub-Link Num value space to user slices for use.

In implementation, the partitioning module is further configured to reserve, in each FA slice topology, a remaining bandwidth resource in the total bandwidth that is not allocated to the user slice, and share and use, for a non-slice user in the FA slice topology, traffic of the non-slice user is carried through SRv BE.

In implementation, the dividing module is further configured to divide the FA slices into corresponding FA slices based on FlexAlgo with a one-to-one correspondence for the network according to the number of industries or virtual operators;

A network apparatus, comprising:

when providing service for the slicing user, guiding the service flow to SRv Policy tunnel transmission;

establishing SliceID corresponding relation with each interface sub-link resource on SRv Policy tunnel path;

In practice, further comprising:

In implementation, when the slice user traffic is guided to SRv Policy tunnel transmission, according to SliceID carried in the slice user forwarding message, one sub-link resource capable of meeting the SliceID resource requirement is allocated from the sub-link resources in the idle state corresponding to the physical outgoing interface for forwarding, and the corresponding relation between SliceID and the sub-link resource and the state of the sub-link resource are maintained.

In implementation, when the first slice user flow is guided to SRv Policy tunnel transmission, when the first slice message arrives at the device, the device searches the local table to obtain the bandwidth resource needed by SliceID according to SliceID carried in the forwarding message, finds the Sub-Link resource Sub-Link Num of unoccupied bandwidth from the local device Sub-Link resource table, distributes the Sub-Link resource Sub-Link Num to the SliceID, forwards the slice user message from the corresponding Sub-port, updates the state of the local Sub-Link Num to be occupied, and reports one or a combination of updated Sub-Link resource Sub-Link Num occupation, sliceID and Sub-Link Num corresponding relation, sub-Link Num state to the SDN controller through telemetry TELEMETRY.

A network apparatus, comprising:

The transmission module is used for guiding the service flow to SRv Policy tunnel transmission when providing service for the slicing user;

and the relation module is used for establishing the corresponding relation between SliceID and each interface sub-link resource on the SRv Policy tunnel path.

In practice, the relationship module is further configured to advertise one or a combination of end.x SID, reserved total bandwidth, sliceID number, or corresponding resource information per SliceID virtual member sub-link per FA slice on the link in an interior gateway protocol IGP flood.

In an implementation, the relationship module is further configured to enable the tunnel head node device to obtain SliceID from the BGP SRv Policy message issued by the SDN controller, and write the location corresponding to the forwarding plane message.

In implementation, the transmission module is further configured to allocate, according to SliceID carried in the forwarding message of the slice user, a sub-link resource capable of meeting the SliceID resource requirement from the sub-link resources in an idle state corresponding to the physical outgoing interface to forward the slice user traffic to SRv Policy tunnel transmission, and maintain SliceID a corresponding relationship between the sub-link resource and a state of the sub-link resource.

In implementation, when the transmission module is further configured to direct the slice user traffic to SRv Policy tunnel transmission, and when the first slice packet arrives at the device, the device searches the local table to obtain the bandwidth resource required by SliceID according to SliceID carried in the forwarding packet, finds the Sub-Link resource Sub-Link Num of the unoccupied bandwidth from the local device Sub-Link resource table, allocates the Sub-Link resource Sub-Link Num to SliceID, forwards the slice user packet from the corresponding Sub-port, updates the local Sub-Link resource Sub-Link Num status to occupied, and reports one or a combination of updated Sub-Link resource Sub-Link Num occupation, sliceID and Sub-Link Num correspondence, sub-Link Num status to the SDN controller through telemetry TELEMETRY.

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

The invention has the following beneficial effects:

The technical scheme provided by the embodiment of the invention is a carrying network slicing scheme and mechanism with resource guarantee based on FlexAlgo and SRv. By expanding FlexAlgo technology and combining SRv tunnel encapsulation, the centralized management and control capability of the slice ID and SDN is carried on the forwarding surface, and a data carrying network two-stage slice service with a dynamically adjustable sub-link level and a resource guarantee is provided for users. The first-stage slice is realized by FlexAlgo technology and can be used for slice isolation of different maintenance subjects or for distributing different slices for different industries, and the second-stage slice is realized by carrying slice IDs on a forwarding surface by SRv tunnel technology.

As the independent sharing of each slice resource on the same physical link can be realized, compared with the prior FlexAlgo technology, the method can solve the problems that each slice FlexAlgo can only independently share one physical link, the isolation granularity is coarse, the existing network resource can not be basically satisfied, and the hard isolation of the slice can not be realized by large-scale deployment.

As the bottom physical resource guarantee can be provided for the slice, the hard slice is realized, and compared with the prior SR-TE and SR Policy technologies, the method can solve the problems of soft isolation and complete sharing of physical resources only through tunnels.

Because the single FA enhancement technology and the single SRv policy+forwarding plane slicing technology can only provide one-stage slicing service, the scheme provides a dynamic adjustable sub-link-level two-stage slicing service of the data carrying network with resource guarantee, and can meet the two-stage slicing scene requirements of industry or virtual operator slicing and user slicing.

Drawings

The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description serve to explain the invention and do not constitute a limitation on the invention. In the drawings:

FIG. 1 is a schematic diagram of a physical networking topology of a device in the background art;

FIG. 2 is a schematic diagram of the topology of different FA slices in the background;

Fig. 3 is a schematic flow chart of an implementation of a transmission method of an SDN controller in an embodiment of the present invention;

FIG. 4 is a schematic diagram of an end.X SID sub-TLV structure after Q-flag in an embodiment of the invention;

Fig. 5 is a schematic diagram of a link slice information Sub-TLV structure according to an embodiment of the present invention;

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

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

Fig. 8 is a schematic diagram illustrating the expansion of ISIS SRv Capabilities sub-TLV structure in an embodiment of the present invention;

fig. 9 is an expanded schematic diagram of BGP-LS SRv Capabilities sub-TLV structure in an embodiment of the present invention;

FIG. 10 is a schematic diagram of a BGP SRv Policy extension SliceID according to an example embodiment of the present invention;

FIG. 11 is a schematic diagram of a network architecture according to an embodiment of the present invention;

FIG. 12 is a schematic diagram of the assignment of End SIDs and end.X SIDs for each device in an embodiment of the present invention;

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

fig. 14 is a schematic diagram of a forwarding process of a packet SRv of a user 1 in the power industry in a Policy tunnel according to an embodiment of the present invention;

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

Fig. 16 is a schematic flow chart of a transmission method implementation of a forwarding device side according to an embodiment of the present invention;

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

Detailed Description

The inventors noted during the course of the invention that:

the slicing scheme capable of being related to the physical resources of the bottom-layer sub-link is needed to match the actual resource condition of the existing network, so that the bottom-layer physical resources with granularity of each slicing sub-link are independently shared, and the network value is improved.

The following describes specific embodiments of the present invention with reference to the drawings.

In the description process, the implementation at the SDN controller and forwarding device sides will be described separately, and then an example of the implementation of the combination of the two will be given to better understand the implementation of the solution given in the embodiment of the present invention. Such an illustration does not mean that the two must be implemented cooperatively or separately, and in fact, when the SDN controller and the forwarding device are implemented separately, they solve the problem on their own side, and when the two are used in combination, a better technical effect is obtained.

Fig. 3 is a schematic flow chart of an implementation of an SDN controller side transmission method, which may include:

Step 301, dividing a link corresponding to each network device interface into a plurality of sub-link resources by the SDN controller according to the resource requirements of the sliced user;

302, establishing a corresponding relation between a slice identifier SliceID and a resource requirement;

step 303, establishing a one-to-one binding source routing technology Policy SRv Policy tunnel based on IPv6 for the user according to the resource requirement of the sliced user, and establishing a corresponding relation between slice identifiers SliceID and SRv Policy tunnels.

In practice, further comprising:

The implementation on a forwarding device is described below.

Fig. 16 is a schematic flow chart of an implementation of a forwarding device side transmission method, which may include:

1601, when the forwarding device provides a service for the slicing user, guiding the service flow to SRv Policy tunnel transmission;

Step 1602, establishing SliceID corresponding relation with each interface sub-link resource on SRv Policy tunnel path.

In practice, further comprising:

The following mainly uses an SDN controller, and is described in connection with a forwarding device, so as to facilitate understanding of the relationship between the SDN controller and the forwarding device.

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

In particular, the scheme is a resource-guaranteed carrier network slicing scheme and mechanism based on FlexAlgo and SRv. By expanding the existing FlexAlgo technology and combining SRv tunnel encapsulation, the forwarding plane carries slice ID and centralized management and control capability of SDN (software defined network ), and a dynamically adjustable sub-link level data carrying network two-stage slice service with resource guarantee is provided for users.

The first-stage slice is realized by FlexAlgo technology and can be used for slice isolation of different maintenance subjects or for distributing different slices for different industries, and the second-stage slice is realized by carrying slice IDs on a forwarding surface by SRv tunneling technology to realize the second-stage user-stage or service-stage slice in the first-stage FA slice.

In implementation, the corresponding relation between SliceID and SRv Policy tunnels in FlexAlgo-based FA slices, to which the slice users belong, is established, and the corresponding relation between SliceID and SRv sub-link resources of each interface on the path of the Policy tunnels in the FA slices is established.

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

(1) SDN controller resource management mechanism.

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

In particular, the implementation of the end.x SID allocation, total resource reservation mechanism and method for virtual member sub-links within the FA slice topology, and the number allocation rules for forwarding plane SliceID within the FA slice topology will be described below.

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

In particular, the following will describe the maintenance and update implementation of the information such as the FA slice SliceID, the virtual member sub-link end.xsid, the total reserved resources thereof, and the number of SliceID on the controller, and the requirements and states of each SliceID resource, the total remaining slice resources of the virtual member sub-link, and the like.

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

Firstly, different Locator (locating point) spaces are required to be allocated for each FA slice, then a controller allocates different End SIDs (End SIDs) for nodes in the FA slice topology in the Locator space according to the topology requirements of the first-stage FA slice, each virtual member sub-link allocates different End SIDs, meanwhile, corresponding bandwidth resources are reserved for each FA slice topology according to the bandwidth requirements of the first-stage FA slice, each End SID and the corresponding bandwidth information required to be reserved are issued to corresponding equipment in a network, the equipment executes corresponding configuration, and the corresponding relation between the End SIDs and the reserved bandwidth is saved. The specific examples are shown in the following table:

TABLE 1 dynamic resource Allocation Table for virtual Member sub-Link Adjacent SIDs

FA slice ID	End.X SID	Reserved total bandwidth (G)
			128	X1:1:1 (address space belonging to FA 118)	5G
129	X2:1:1 (address space belonging to FA 129)	10G
			130	X3:1:1 (address space belonging to FA 130)	15G

The information can also be configured directly on the device and reported to the controller by BGP-LS (BGP link status, BGP-LINK STATE; 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, each FA slice occupies 5G bandwidth, the 200G bandwidth is reserved for FA slice topology, and only the remaining 200G bandwidth can be shared for non-slice users.

2) And (5) distributing the quantity of forwarding planes SliceID in the FA slice topology.

The following describes the operation mechanism and scheme of the value allocation, the corresponding resource allocation and the state maintenance of the secondary slice user forwarding plane SliceID.

A fixed number SliceID is assigned to each FA slice, or a fixed number SliceID is assigned to each FA slice for delivery to the device.

And the static allocation mode is that a fixed number SliceID, such as 500, is allocated to each FA slice, the reserved forwarding surface SliceID for the FA128 slice topology is 1-500, the reserved forwarding surface SliceID for the FA129 slice topology is 501-1000, and the like, and the reserved forwarding surface SliceID for the FAn slice topology is [ n-128 ] 500+1 ] [ n-128 ] 500+500 ].

The dynamic allocation mode is that a certain number SliceID of the FA slices are allocated to each piece of equipment to be issued, the SliceID information is flooded in the IGP and announced to each piece of equipment.

3) And (3) distributing forwarding surfaces SliceID corresponding to the secondary slice users and maintaining states.

The controller distributes the forwarding plane SliceID resources and the corresponding bandwidth information for each user according to the requirements of slice users in the FA slice topology, and the unallocated SliceID is temporarily reserved;

Specifically, the controller allocates the resources of the forwarding plane SliceID and the corresponding bandwidth information to each user according to the requirements of the users of the second level slice in the first level FA slice topology, and the unallocated SliceID is temporarily reserved. Specifically, the following table shows the results.

TABLE 2 resource demand Allocation Table for forwarding plane SliceID

SliceID of the temporary unallocated bandwidth requirements in the upper table can be updated at any time according to the bandwidth requirements of the subsequent newly added slice users, and the controller is responsible for maintaining the dynamic update table and synchronously issuing the information to the equipment for storage. Wherein the states of SliceID include idle, pre-occupied, unassigned, and the like.

If the head node computation path is needed, each SliceID and corresponding bandwidth resource information needs to be extended by ISIS (intermediate system to intermediate system ), flooded within IGP, and if the controller computation path is all adopted, no flooding is needed.

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

When the slice user traffic in the FlexAlgo FA slice is guided to SRv Policy tunnel transmission, the forwarding device allocates one sub-link resource which can meet the SliceID resource requirement from the sub-link resources in the idle state of the corresponding physical outgoing interface to forward according to SliceID carried in the slice user forwarding message, and maintains the corresponding relation between SliceID and the sub-link resource and the state of the sub-link resource.

The following will describe a method for allocating a sub-link resource (such as MTN (metropolitan area network, metro transport network) subinterface, VLAN (virtual local network, virtual Local Area Network) enhanced subinterface, channelized subinterface resource, flexE subinterface, independent QoS (quality of service ) queue, etc.) capable of meeting the SliceID resource requirement from the sub-link resources in the idle state corresponding to the physical outgoing interface according to SliceID carried in the slice user forwarding message, and a dynamic maintenance mechanism and method for the correspondence between SliceID and sub-link resource and the state of the sub-link resource.

When the slice user flow in the FlexAlgo FA slice is guided to SRv Policy tunnel transmission, sub-Link Num is adopted to identify the bottom physical Sub-Link resource, each Sub-Link has the bottom physical resource which is self-shared, and the corresponding relation between Sub-Link Num and various Sub-Link resource IDs is maintained to be compatible with the bottom physical Sub-Link resources of various types.

Specifically, sub-Link Num is introduced to uniformly identify the bottom physical Sub-Link resources, each Sub-Link has its own independent bottom physical resources, such as MTN Sub-interface, VLAN enhanced Sub-interface, channelized Sub-interface resources, flexE Sub-interfaces, independent QoS queues, etc., and the Sub-Link Num is compatible with the bottom physical Sub-Link resources of each type by maintaining the corresponding relation between Sub-Link Num and the Sub-Link resource IDs of each type.

Specifically, the controller divides each physical Link of all devices in the corresponding primary FA slice topology into a plurality of mutually isolated Sub-links according to the requirements of the secondary slice users, each Sub-Link has own independent bottom physical resources, such as an MTN Sub-interface, a VLAN enhancer Sub-interface, a Channel channelized Sub-interface resource, a FlexE Sub-interface, an independent QoS queue, and the like, and the Sub-Link identifier is identified by Sub-Link Num, wherein the length of the Sub-Link identifier is 4 bytes, the low order represents the Sub-Link resource ID, such as MTNID, VLANID, channelID, flexEID, qoSQueID, the Sub-Link resource ID is less than 32 bits, and the high order is filled with 0.

In practice, the sub-link resource identification used by the FA slice and the user slice is distinguished by dividing the value space of the sub-link resource identification.

User slices, which may also be referred to as forwarding plane slices, i.e., slices that establish SRv tunnels based on SliceID associations with underlying sub-link resources.

In the specific implementation, when the value space of the Sub-Link resource identifier is divided, sub-Link resources corresponding to Sub-Link Num with the upper 4 bits being 1 are allocated to the FA slice for use, and the value space of the rest Sub-Link Num is allocated to the user slice for use.

For example, sub-Link Num corresponding Sub-Link resources with the upper 4 bits 1 are used for being allocated to the FA primary slice.

Taking the example of a sub-link resource as a channelized sub-interface, examples may be as follows (for simplicity, each digit in the following table represents an 8-bit decimal value):

TABLE 3 physical resource Allocation Table for sub-links

In the specific implementation, the sub-link resources 100/200/500M (the total amount cannot exceed the total bandwidth of the corresponding FA primary slice) which are more than the actual secondary slice user requirements by a certain proportion can be pre-allocated on the equipment in advance, so that when a new user comes, the sub-link resources at the bottom layer are available, and the service can be opened quickly.

1. For compatibility with the underlying resources of each type, a Sub-Link identifier is introduced, namely Sub-Link Num, or a channel ID is directly used for identifying a specific Sub-Link without Sub-Link Num.

2. Other physical resources besides Bandwidth may also be configured for MTN subinterfaces/VLAN enhancer interfaces/Channel channelization subinterface resources/FlexE subinterfaces/independent QoS queues, here exemplified only by Bandwidth resources.

The controller issues the configuration of the corresponding relation to each device in the network, and the device executes the related configuration locally and stores the corresponding relation.

The controller is responsible for maintaining the state of each Sub-Link Num on the Link, such as idle, pre-occupied, etc., and updating the state thereof in real time according to the Sub-Link resource Sub-Link Num occupation reported by the device through TELEMETRY (telemetry).

(2) IGP flooding slice-related link information.

The IGP flood advertises one or a combination of end.x SID per FA slice virtual member sub-link, reserved total bandwidth, sliceID number, or corresponding resource information per SliceID on the link.

The method of end.x SID, reserved total bandwidth, sliceID number, and corresponding resource information per SliceID virtual member sub-link per FA slice on IGP flooding advertisement link will be described below.

The IGP floods the slice related link information advertising end.x per FA slice, total reserved bandwidth, sliceID number, and corresponding resource information per SliceID on the link.

1) The end.x SID information for the virtual member sub-link of the FA slice is advertised.

In practice, an identification is added to the end.x SID sub-TLV structure to indicate that the device is an adjacency SID of the virtual member sub-link, rather than an adjacency SID of the physical link.

Specifically, the extended end.X SID sub-TLV (end segment identifier sub-TLV; TLV: type, length, value, tag, length, value) structure is augmented with a flag to indicate that it is the adjacency SID of the virtual member sub-link, not the adjacency SID of the physical link.

Fig. 4 is a schematic structural diagram of an end.x SID sub-TLV after Q-flag, where an algorism field (see fig. 4) corresponding to each virtual member sub-link end.x SID sub-TLV is consistent with an FA Algorithm (Flexible Algorithm) used by the FA slice to which it belongs, and a Q-flag is added to indicate that the adjacent SID is a virtual member sub-link of a certain slice. After the Q-flag is extended, the End.X SID sub-TLV structure is shown in FIG. 4.

The SRv node advertises multiple virtual member sub-links end.x SID by carrying multiple SRv end.x SID sub-TLVs in the same adjacency TLV.

2) Link slice information advertisement SliceID (slice identification) of FA and corresponding resource information advertisement.

The link slice number and corresponding resource information are advertised using link slice information Sub-TLV and slice resource Sub-TLV structures.

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

The reserved total bandwidth resources of the FA, sliceID number, slice resource information corresponding to each SliceID can be advertised by sub-TLVs of GENINFO TLV (basic information TLV) in RFC6823, and when the original system is fragmented, the slice resource information of the interface can be continuously advertised in the extended fragments.

Fig. 5 is a schematic link slice information Sub-TLV structure, and the newly defined link slice information Sub-TLV is shown in fig. 5, where:

Type (8 bit) TBD (to be determined, to be decided) to be applied for;

length (8 bits), message Length, do not contain Type and Length;

Flag (8 bits);

The Ibit is an IPv4 (Internet protocol version 4 ) interface address which indicates that the link identification information is 4 bytes after being set;

Vbit is an IPv6 (internet protocol version 6 ) interface address, after setting, indicating that the link identifier is 16 bytes;

lbit, after setting, indicating that the link identification information is a local link identification of 4 bytes;

xbit after setting, indicating that the sub-link identification information is an end.X SID of 16 bytes;

Bandwidth (8 bits) slice total Bandwidth;

Sub-Link Local Identifier (128 bits) Sub-link identification;

SliceIDCount (8 bits) slice ID number;

FIRSTSLICEID (24 bits) slice ID start value;

Sub-Sub-TLVs slice resource Sub-Sub-TLV for notifying the resource information of each SliceID.

Fig. 6 is a schematic view 1 of a structure of a slice resource sub-sub-TLV, and as shown in the drawing, a newly defined slice resource sub-sub-TLV is used to announce SliceID resource information, and the structure is as follows:

type (8 bit) TBD to be applied for;

length (8 bit) message Length;

Flag (8 bits) reservation;

Reserved (16 bits);

SliceID (24 bits) slice ID value;

Optional Sub-sub-TLVs carrying corresponding slice resource information (maximum reserved link bandwidth, available bandwidth, used bandwidth, time delay, link packet loss rate, etc.) of SliceID, multiplexing sub-TLVs defined in the existing RFC8570 as follows:

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

Fig. 7 is a schematic view of a slice resource Sub-Sub-Sub-TLVs structure, which may also be directly filled with Bandwidth/Delay/.

(3) Device slicing capability advertisement.

The SRv Capabilities sub-TLV at Router CAPABILITY TLV and the SRv Capabilities TLV of BGP-LS are tagged to indicate that the device supports the Capability to carry SliceID on the forwarding plane and perform slicing.

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

The sub-TLV of FADF (Flexible Algorithm Definition Flags, flexible algorithm definition flag bit) of FAD (flexible algorithm definition ) TLV of BGP-LS Node NLRI (Node NLRI; NLRI: network layer reachability information, network Layer Reachability Information) is added with an identification for indicating a calculation path based on virtual member sub-link information of an interface.

Specifically, the FADF sub-TLV of the FAD TLV of the BGP-LS Node NLRI is expanded, and a flag mark is added for indicating the calculation of the virtual member sub-link information based on the interface.

1) And expanding SRv Capabilities sub-TLV of Router CAPABILITY TLV, adding a Q-flag, and indicating that the equipment supports the slice processing capability of the forwarding plane. Fig. 8 is a ISIS SRv Capabilities sub-TLV structure expansion schematic diagram, and specifically shown in fig. 8.

2) And expanding SRv capacity TLVs of the BGP-LS, adding a Q-flag, and enabling the advertising node to have forwarding plane slice processing Capability. Fig. 9 is an expanded schematic diagram of BGP-LS SRv Capabilities sub-TLV structure, which is specifically shown in fig. 9.

(5) Extension BGP SRv6 Policy carries forwarding plane SliceID information.

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

Fig. 10 is a schematic diagram of BGP SRv Policy extension SliceID, which extends BGP SRv Policy, adds SliceID (hatched), and the format after extension is shown in fig. 10.

(6) Dynamic maintenance of slice user forwarding plane SliceID and Sub-Link Num (Sub-Link identifier) correspondence.

The following describes a mechanism and a method for synchronizing SliceID and Sub-Link Num corresponding relation and Sub-Link Num occupation condition of Sub-Link resource in real time by using TELEMETRY to a controller.

When the flow of the sliced user in the FlexAlgo FA slice is guided to SRv6 Policy tunnel transmission, and when the first sliced message arrives at the device, the device searches the local table to obtain SliceID the required bandwidth resource according to SliceID carried in the forwarding message, then finds the Sub-Link resource Sub-Link Num of the unoccupied bandwidth from the local device Sub-Link resource table, distributes the Sub-Link resource Sub-Link Num to SliceID, forwards the sliced user message from the corresponding Sub-port, updates the state of the local Sub-Link resource Sub-Link Num to be occupied, and reports one or a combination of updated Sub-Link resource Sub-Link Num occupation, sliceID and Sub-Link Num corresponding relation, sub-Link Num state to the controller through TELEMETRY.

Specifically, when the first slice message arrives at the device, the device searches the local table to obtain SliceID bandwidth resources, for example, 100M, according to SliceID carried in the forwarding message, then finds unoccupied 100M Sub-Link resources Sub-Link Num from the local device Sub-Link resource table, allocates the unoccupied 100M Sub-Link resources Sub-Link Num to the SliceID, forwards the slice user message from a corresponding Sub-port, for example, an informatization Sub-interface, updates the state of the local Sub-Link resources Sub-Link Num to be occupied, and reports the occupation condition of the updated Sub-Link resources Sub-Link Num to the controller in real time through TELEMETRY. Table 4 is a table of SliceID and Sub-Link Num correspondence, and the specific relationship can be shown in the table.

TABLE 4 SliceID and Sub-Link Num correspondence table

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

(7) Color contained in each adjacent TLV (each sub-TLV of Extended Administrative Group (extended management group)) corresponding to each physical link on the node is required to be contained at least in the FA slice to which each sub-link belongs, and the color is required to be contained in the calculation constraint.

(8) Slice topology generation.

The controller knows the FA slice to which the device belongs according to FAD sub-TLV information reported by each forwarding device through BGP-LS, knows the FA slice to which the device belongs according to color contained in EAG sub-TLVs of adjacent TLVs corresponding to each physical link and FA calculation constraint, and knows that the device needs to calculate the path based on virtual member sub-links in calculating the path according to Q-flag setting of FADF sub-TLVs, so that the controller forms different FA slice topologies according to the FA slice information to which each physical link corresponds to the virtual sub-link further according to Algorithm of end.X SID of the virtual member sub-link.

(9) The forwarding message carries SliceID.

In the mode 1, the tunnel head node equipment acquires SliceID from BGP SRv Policy messages issued by the SDN controller and writes the SliceID in a position corresponding to a forwarding plane message.

Specifically, the tunnel head node obtains SliceID from BGP SRv Polic messages issued by the controller, and writes the SliceID messages into the corresponding positions of the forwarding plane messages.

The controller issues SliceID and CADIDATEPATH paths together (the extended structure is shown in fig. 10) to the SRv6 tunnel head node through the BGP SRv Policy protocol, and the head node device carries SliceID information in the forwarding message when performing SRv6 tunnel encapsulation.

Mode 2. Configuring a mapping relation between a Color template and a forwarding plane SliceID, and obtaining a corresponding SliceID by the tunnel head node device according to the Color attribute of SRv6 Policy.

Specifically, a mapping relationship between a Color template and a forwarding plane SliceID is configured, the head node device obtains a corresponding SliceID according to the Color attribute of SRv Policy, and SliceID information is carried in the forwarding message.

The SliceID information can be placed in the source address, flowLabel (stream label) or HBH (Hop By Hop) fields of the forwarded message, and the SliceID information is indicated to be carried in the message By using 1 flag bit of the TrafficClass field.

(10) The controller calculates the path and the operation mechanism of the forwarding equipment.

The controller calculates the path based on SliceID information, FA topology and residual slice resource information of virtual member sub-link End.X corresponding to the FA topology, and uses virtual member sub-link End.X SID to carry out path arrangement.

The following describes a processing mechanism and method for the controller to perform path computation based on SliceID information, FA topology and the remaining slice resource condition of the virtual member sub-link end.x corresponding to the FA topology, and to perform path arrangement by using the virtual member sub-link end.x SID.

In implementation, in each FA slice topology, the remaining bandwidth resources which are not allocated to the user slices in the total bandwidth are reserved, so that the non-slice users in the FA slice topology are shared for use, and the traffic of the non-slice users is carried through SRv BE.

Specifically, in each FA slice topology, reserving the residual bandwidth resources which are not allocated to the second-level user slice in the total bandwidth, and sharing the use of the residual bandwidth resources for the non-slice users in the FA topology, wherein the traffic of the non-slice users is carried through SRv BE.

Within each FA slice topology, the traffic of the secondary slice user is carried through SRv Policy tunnels whose paths are computed by the controller or tunnel head node. Since only SRv6 Policy strict paths can provide exclusive slice services with strict physical resource guarantee for each hop from end to end for slice users, SRv6 Policy tunnels refer to SRv6 Policy strict paths.

The controller selects a SliceID (assumed to be x) with a state of 'unassigned' from a 'table 2: forwarding surface SliceID corresponds to a resource demand allocation table' according to SLA requirements such as bandwidth, time delay and the like proposed by a secondary slice user, updates 'required bandwidth' information of the forwarding surface SliceID and updates the state to be 'idle', creates a VPN for the forwarding surface and uses a tunneling strategy of a binding mode to bind SRv Policy tunnels one by one, and calculates SRv a Policy master CADIDATEPATH (abbreviated as CP) by taking the SLA demands (bandwidth, time delay and the like) of the user as a calculation constraint in a primary FA slice topology where the secondary slice user is located (for example, taking FAs as calculation factors).

When the path is calculated, the controller needs to combine the resource conditions of virtual member sub-links end.X corresponding to the first-stage FA topology (such as whether enough residual slice bandwidth resources exist, whether time delay meets user requirements or not) to calculate a master-standby CP (CP) which is end-to-end and meets the SLA requirements of the second-stage slice user, only one segmentlist is arranged in each CP, the path of each segmentlist is arranged by using the end.X SID of the Locator space corresponding to the FA slice, and meanwhile, the state of the SliceID (x) in the 'table 2: forwarding surface SliceID corresponding to the resource requirement allocation table' is pre-occupied, and the SliceID (x) is issued to the head node forwarding equipment along with the master-standby CP of BGP SRv Policy.

After SRv Policy issues successfully, the controller updates the real-time state of the SliceID (x) to occupied state.

In implementation, when the slice user traffic in the FlexAlgo FA slice is guided to the SRv Policy tunnel transmission, the forwarding device determines the physical resource of the slice sub-link on the outgoing interface according to the indication of the slice flag set in the end.x SID of the virtual member sub-link when the message is forwarded, and forwards the message through the corresponding sub-link physical resource sub-interface.

When the message is forwarded, the forwarding device further determines the physical resources of the slice sub-link on the outgoing interface according to the indication of the set slice flag in the end.X SID of the virtual member sub-link, and the processing mechanism and method for forwarding the message through the corresponding sub-link physical resource sub-interface are described below.

Forwarding the message along the designated path according to SRv Policy path issued by the controller on the forwarding device, determining the corresponding Sub-Link resource ID (e.g. ChannelID) by each device along the path according to the Q-flag set indication in the end.X SID of the virtual member of the device, knowing the bandwidth resource requirement required by the slice user according to SliceID carried in the forwarding message after determining the interface, allocating a Sub-Link Num capable of meeting SliceID bandwidth requirement from Sub-Link resource Sub-Link Num corresponding to the interface, searching the locally stored 'table 3: sub-Link physical resource allocation table' by the forwarding device according to the Sub-Link Num, determining the corresponding Sub-Link resource ID (e.g. ChannelID, etc.), forwarding the message through the Sub-interface (e.g. ChannelID), thereby ensuring that the service flow has shared channelized Sub-interface physical resource, updating the state of the Sub-Link Num to occupied, and updating the local 'table 4: sliceID and Sub-Link Num' to pass through the corresponding information TELEMETRY.

When the slice user flow in the FlexAlgo FA slice is guided to SRv Policy tunnel transmission, the controller updates one or a combination of the corresponding relation between SliceID of the virtual member Sub-Link and Sub-Link resource Sub-Link, sub-Link state and residual slice resource information of the virtual member Sub-Link according to the information reported by the equipment.

The following describes a mechanism and a method for dynamically updating and maintaining the corresponding relation between SliceID of the virtual member Sub-Link and Sub-Link resource Sub-Link Num, the Sub-Link resource Sub-Link Num state, the remaining slice resource of the virtual member Sub-Link and other information according to the information reported by the device.

After receiving the allocation information of Sub-Link Num reported by the forwarding device through TELEMETRY, the controller saves the corresponding relation and updates the residual slice bandwidth resource information (such as total reserved bandwidth-allocated Sub-Link Num bandwidth) of each virtual member Sub-Link end.X SID in the FA topology.

When the main and standby CP paths of the slicing users are failed, the BE escape path is taken, and the escape path occupies the resources of the non-slicing users in the FA slicing topology.

The following is an example.

(1) And (5) networking description.

Assuming that A, B, C, D, E, F, G, H devices exist in the network, an ISIS dynamic routing protocol is operated and all devices are in the same ISIS domain, all the devices support the FA function and the Q-flag of the FADF sub-sub-TLV is set.

And establishing BGP-LS connection between the SDN controller and the forwarding equipment.

Fig. 11 is a schematic diagram of a network architecture, and a topology structure is shown in fig. 11.

(2) Slicing requirements.

Assuming there are currently 3 industry slicing requirements, the bandwidth requirements are 5G, 10G, 15G, respectively, and the secondary user slicing requirements within each industry are shown in the table.

(3) SRv6 address assignment.

3 Industries are divided into 3 FlexAlgo slices in a network, each FA slice is allocated with different Locator spaces, end SIDs (Q-flag set) and virtual member sub-link end.X SIDs (Q-flag set) are allocated to equipment and links contained in the FA slice in the respective address spaces, and fig. 12 is a schematic diagram of allocation of End SIDs and end.X SIDs of the equipment, and the allocation situation is shown in fig. 12.

Each link affinity attribute in the network at least comprises an affinity (color attribute) which is required to be contained by the path constraint requirement of the FA slice to which the link affinity attribute belongs, and the specific setting is as follows:

Link (two-way)	Affinity attributes
		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)

Fig. 13 is a schematic diagram of FA slice topologies, and 3 FA slice topologies as shown in fig. 13 may be formed on the SDN controller based on the basic configuration.

(4) FA primary slice resource reservation.

And reserving corresponding bandwidth resources for the end.X SIDs of the corresponding virtual member sub-links of each port of each device in each FA slice topology according to the bandwidth requirements of the first-level FA slice on the controller.

Taking a port of the a device as an example, the total reserved bandwidth of the virtual member sub-link is shown in the following table, and the other devices and the like.

(5) And (5) distributing the quantity of forwarding planes SliceID in the FA slice topology.

A certain number SliceID of forwarding devices are allocated to each FA slice on the controller, for example, a forwarding plane SliceID reserved for the FA128 slice topology is 1-200 (i.e., FIRSTSLICEID =1, slicerdcount=200), a forwarding plane SliceID reserved for the FA129 slice topology is 201-600 (i.e., FIRSTSLICEID =201, slicerdcount=400), and a forwarding plane SliceID reserved for the FA130 slice topology is 601-1200 (i.e., FIRSTSLICEID =601, slicerdcount=600).

The above SliceID information is flooded within the IGP and advertised to each device.

(6) Forwarding plane SliceID allocation for two-level slicing users

The controller allocates the forwarding plane SliceID resources and corresponding bandwidth information to each user according to the requirements of the secondary slice users in the primary FA slice topology, and the unallocated SliceID is temporarily reserved.

TABLE 5 resource demand Allocation Table for forwarding plane SliceID

The controller maintains the dynamic update table and sends the updated state to the equipment for storage at any time.

The device floods the above link slice information within IGP.

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

The controller divides each physical Link of all devices in the corresponding primary FA slice topology into a plurality of mutually isolated Sub-links according to the requirements of secondary slice users, and each Sub-Link has own independent bottom physical resource and is identified by Sub-Link Num.

Physical resources corresponding to Sub-Link Num of each port of the device are configured, taking the A device and Channel channelized Sub-interface resources as examples, physical resource allocation of a certain port Sub-Link on the A device is shown in the following table, and other devices are similar to each other:

The Sub-Link Num and the corresponding physical resources pre-allocated on the device need to be larger than the requirements of the actual secondary slicing users by a certain proportion (for example, a certain number of 100M/200M/500M channelized Sub-interface resources are reserved respectively, but the total quantity cannot exceed the total bandwidth of the corresponding FA primary slice), so that when a new user comes, the Sub-interfaces of the bottom Link are already available, and the service can be opened quickly.

(6) SRv6-Policy calculation and message forwarding process.

Taking the example of the slicing resource opening of the user 1 in the power industry, the user needs a 200M bandwidth resource from the A node to the E node.

The Prefix-SID allocated to the power industry user is in the Locator address space corresponding to the FA 130.

The controller creates a VPN for it containing a and E nodes and one-to-one binds SRv the Policy tunnel using the binding mode tunnel Policy and enables HSB configuration for the SRv6 Policy.

The controller calculates a SRv Policy's primary and backup CP for which bandwidth resources from a to E meet 200M requirements within the FA130 topology.

Taking the node A as an example, the controller checks the residual resource conditions of the virtual member sub-links corresponding to the FA130 slice with the ratio of X3:1:3:3:35 when calculating the path, the bandwidth of SliceID is satisfied with the requirement and is free at present, and the controller arranges the calculated segmentlist paths of the master and backup CPs by using the End.X SIDs of the Locator space corresponding to the FA slice according to the operation of each device in the FA130 topology.

The primary and backup CP paths from a to E thus calculated are as follows:

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

Prepared CP: < X3:5: < 100, X3:6::100, X3:7::100, X3:8:: < 100>, sliceID = 601

The controller updates the state of SliceID 601,601 of each link in the FA130 topology to be pre-emptive, and issues SliceID 601,601 to the head node a device along with the primary and standby CP paths through BGP SRv6 Policy protocol.

Fig. 14 is a schematic diagram of a forwarding process of the packet SRv of the power industry user 1 in the Policy tunnel, and when the packet of the power industry user 1 reaches the ingress node a device, the forwarding process of the packet is shown in fig. 14.

The A device iterates the message to a SRv Policy tunnel (tunnel Endpoint is E3:1:100) of the slice FA130 according to a VPN routing Policy to carry, so that the outer IPv6 message header of the SRv Policy tunnel is encapsulated, the SRH segmentlist is < X3:1:100, X3:2:100, X3:3:100, X3:4:100, E3:1:B 100> (wherein E3:1:1:B 100 is the VPN SID corresponding to the traffic), the current SL pointer points to X3:1:100, and the value 601 of SliceID is written into the corresponding position of the forwarded message according to SliceID corresponding to the tunnel (for example, the message is placed in FlowLable, HBH, a source address and the like and indicated by 1 flag bit of TrafficClass).

The A device checks the local table according to the X3:1:100 of the DA field, knows that the output interface of the message is GE0/1/0, knows that the bottom Sub-Link Num resource needs to be further determined according to SliceID according to the indication of the Q-flag setting of the X3:1:100, and then allocates a Sub-Link Num 0004 which can meet the 200M bandwidth requirement required by SliceID 601 from Sub-Link Num corresponding to the idle state of the output interface, and locally stores the corresponding relation.

SliceID	Sub-Link Num of Sub-Link identifier
		601	0004

The A device updates the status of Sub-Link Num 0004 to occupied, and reports the updated information to the controller through TELEMETRY. The table is thickened to indicate "occupied"

The device determines the corresponding informationized Sub-interface of the ChannelID 004 according to the Sub-Link Num 0004, and forwards the message through the channelized Sub-interface 004, thereby ensuring that the service flow of the user 1 has the physical resource of the channelized Sub-interface which is exclusive.

And the subsequent devices in the path all execute the same table lookup forwarding, update Sub-Link Num state, report the controller and other operations until the message reaches the tunnel tail node E device. Thus, the physical resource guarantee that the flow of the user 1 in the power industry can obtain 200M channelized sub-interfaces on each link of the forwarding path is ensured.

Based on the same inventive concept, an SDN controller and a computer readable storage medium are also provided in the embodiments of the present invention, and since the principle of solving the problem by these devices is similar to that of the transmission method, the implementation of these devices may refer to the implementation of the method, and the repetition is omitted.

In implementing the technical scheme provided by the embodiment of the invention, the method can be implemented as follows.

Fig. 15 is a schematic diagram of a network device as an SDN controller, where the SDN controller includes:

processor 1500, for reading the program in memory 1520, performs the following process:

a transceiver 1510 for receiving and transmitting data under the control of the processor 1500.

In practice, further comprising:

the following information is maintained and/or updated:

In practice, further comprising:

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

The embodiment of the invention also provides a network device, which comprises:

In practice, further comprising:

For convenience of description, the parts of the above apparatus are described as being functionally divided into various modules or units, respectively. Of course, the functions of each module or unit may be implemented in the same piece or pieces of software or hardware when implementing the present invention.

Fig. 17 is a schematic diagram of a network device as a forwarding apparatus, and as shown in the drawing, the forwarding apparatus includes:

the processor 1700 is configured to read a program in the memory 1720, and execute the following procedures:

a transceiver 1710 for receiving and transmitting data under the control of the processor 1700.

In practice, further comprising:

Wherein in fig. 17, a bus architecture may comprise any number of interconnected buses and bridges, and in particular one or more processors represented by processor 1700 and various circuits of memory represented by memory 1720. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are well known in the art and, therefore, will not be described further herein. The bus interface provides an interface. The transceiver 1710 may be a number of elements, i.e. comprising a transmitter and a receiver, providing a means for communicating with various other apparatus over a transmission medium. The processor 1700 is responsible for managing the bus architecture and general processing, and the memory 1720 may store data used by the processor 1700 in performing operations.

There is also provided in an embodiment of the present invention a computer-readable storage medium storing a computer program for executing the above-described transmission method.

Specific implementations may be found in the implementation of the transmission method.

In summary, in the technical solution provided in the embodiment of the present invention, there are provided:

And expanding SRv Capabilities sub-TLV of Router CAPABILITY TLV and SRv Capabilities TLV of BGP-LS, adding a flag mark, and indicating that the device supports the slice processing Capability of the forwarding plane.

The extended end.x SID sub-TLV structure adds a flag indicating that it is the adjacency SID of the virtual member sub-link, not the adjacency SID of the physical link.

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

Further, a method is provided for IGP flooding advertisement of end.xsid, reserved total bandwidth, sliceID number, and corresponding resource information per SliceID virtual member sub-link per FA slice on the link.

End.X SID allocation, total resource reservation mechanism and method for virtual member sub-links within the FA slice topology, and forwarding plane SliceID quantity allocation rules within the FA slice topology.

And maintaining corresponding relations among the FA slice ID, the virtual member sub-link end.X SID, total reserved resources thereof and SliceID quantity on the controller, and maintaining and updating information such as the requirement and state of each SliceID resource, total residual slice resources of the virtual member sub-link and the like.

And carrying the information of the forwarding plane SliceID for BGP SRv of the Policy structure expansion.

Further, a method is provided in which the tunnel head node obtains SliceID from BGP SRv 6: 6 Polic messages issued by the controller, and writes the SliceID in a corresponding position of the forwarding plane message.

And configuring a mapping relation between the Color template and the forwarding surface SliceID, and acquiring a corresponding SliceID method by the head node equipment according to the Color attribute of the SRv Policy.

The secondary slice user forwarding plane SliceID is a value distribution, corresponding resource distribution and state maintenance operation mechanism and method.

The controller calculates the path based on SliceID information, FA topology and the residual slice resource condition of the corresponding virtual member sub-link End.X, and uses the virtual member sub-link End.X SID to carry out the processing mechanism and method of path arrangement.

And when the forwarding equipment forwards the message, the processing mechanism and the processing method further determine the physical resources of the slice sub-link on the outgoing interface according to the indication of the set slice flag mark in the end.X SID of the virtual member sub-link and forward the message through the corresponding sub-link physical resource sub-interface.

The forwarding device allocates a sub-link resource (such as MTN sub-interface, VLAN enhanced sub-interface, channelized sub-interface resource, flexE sub-interface, independent QoS queue, etc.) which can meet the SliceID resource requirement from the sub-link resources in the idle state of the corresponding physical outgoing interface according to SliceID carried in the forwarding message of the slicing user, and a dynamic maintenance mechanism and method for the corresponding relation between SliceID and the sub-link resource and the state of the sub-link resource.

Furthermore, it provides to introduce Sub-Link Num to uniformly identify the bottom physical Sub-Link resource, each Sub-Link has its own independent bottom physical resource, such as MTN Sub-interface, VLAN enhanced Sub-interface, channelized Sub-interface resource, flexE Sub-interface, independent QoS queue, etc., and by storing and maintaining the corresponding relation between Sub-Link Num and the above Sub-Link resource IDs, it is compatible with the bottom physical Sub-Link resource of each type.

Further, a mechanism and a method for synchronizing the corresponding relation between SliceID and Sub-Link Num and the occupation condition of Sub-Link Num of Sub-Link resources by forwarding equipment to a controller in real time through TELEMETRY are provided.

Further, a mechanism and a method for dynamically updating and maintaining the corresponding relation between SliceID of the virtual member Sub-Link and Sub-Link resource Sub-Link Num, the Sub-Link resource Sub-Link Num state, the residual slice resource of the virtual member Sub-Link and other information are provided according to the information reported by the device by the controller.

The sub-link resource identifiers used by the primary slice and the secondary slice are distinguished by dividing the value space of the sub-link resource identifiers.

Further, sub-Link Num corresponding to Sub-Link Num with high 4 bits being 1 is allocated to the first-stage slice of the FA for use, and the value space of the rest Sub-Link Num is allocated to the second-stage slice for use.

And reserving the residual bandwidth resources which are not allocated to the second-level user slice in the total bandwidth in each FA slice topology, and sharing the use of the non-slice users in the FA topology, wherein the traffic of the non-slice users is carried through SRv BE.

Compared with the prior FlexAlgo technology, the scheme can solve the problems that FlexAlgo slices can only singly share one physical link, the isolation granularity is coarse, the existing network resources can not be basically satisfied, and the hard isolation of the slices can not be realized by large-scale deployment.

The scheme can well provide the bottom physical resource guarantee for the slice, realize hard slice, and solve the problems of soft isolation and complete sharing of physical resources only through the tunnel compared with the prior SR-TE and SR Policy technologies.

The independent FA enhancement technology and the independent SRv policy+forwarding plane slicing technology can only provide one-stage slicing service, and the scheme provides a dynamic adjustable sub-link-level resource-guaranteed two-stage slicing service of a data carrying network, so that the two-stage slicing scene requirements of industry slicing and user slicing can be met.

It will be appreciated by those skilled in the art that embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may 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, magnetic disk storage, optical storage, and the like) 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 will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

It will be apparent to those skilled in the art that various modifications and variations can be made to the present invention without departing from the spirit or scope of the invention. Thus, it is intended that the present invention also include such modifications and alterations insofar as they come within the scope of the appended claims or the equivalents thereof.

Claims

1. A transmission method, comprising:

The software defined network SDN controller divides a link corresponding to each network equipment interface into a plurality of sub-link resources according to the resource requirements of sliced users, and each sub-link resource has a bottom physical resource which belongs to the own exclusive share;

Establishing a one-to-one binding IPv 6-based source routing technical Policy SRv Policy tunnel for the slicing user according to the resource requirement of the slicing user, and establishing a corresponding relation between slice identifiers SliceID and SRv6 Policy tunnels, wherein the corresponding relation between slice identifiers SliceID and SRv6 Policy tunnels is that a slice identifier SliceID capable of meeting the resource requirement of the slicing user is allocated for the SRv6 Policy tunnel;

Further comprises:

SliceID information of the forwarding plane is carried in BGPSRv6 Policy messages and sent to SRv6 Policy tunnel head nodes, or,

And configuring a mapping relation between the Color template and the forwarding plane SliceID, so that the SRv6 Policy tunnel header node equipment obtains a corresponding SliceID according to the Color attribute of SRv Policy.

2. The method as recited in claim 1, further comprising:

3. The method as recited in claim 1, further comprising:

Sub-Link Num is adopted to identify Sub-Link resources, and the corresponding relation between Sub-Link Num and Sub-Link resource IDs of various types is maintained to be compatible with the bottom physical Sub-Link resources of various types.

4. The method as recited in claim 1, further comprising:

IPv 6-based source routing technology Capability type, length, value Router CAPABILITY TLV IPv 6-based source routing technology Capability subtype, length, value SRv Capabilities sub-TLV, and border gateway protocol link type BGP-LS add an identification to the IPv 6-based source routing technology Capability type, length, value SRv Capabilities TLV to indicate that the network device supports the Capability to carry SliceID on the forwarding plane and perform slicing.

5. The method as recited in claim 1, further comprising:

An identification is added to the end segment identifier subtype, length, value end.x SID sub-TLV structure to indicate that the network device is an adjacency SID of a virtual member sub-link, rather than an adjacency SID of a physical link.

6. The method as recited in claim 1, further comprising:

7. The method of claim 1, or 2, further comprising one or a combination of the following treatments:

When SliceID quantity is distributed, distributing preset quantity SliceID for each FA slice on the SDN controller, and then issuing the distributed quantity to network equipment;

the SDN controller allocates the forwarding plane SliceID resources for each slice user according to the requirements of the slice users in the FA slice topology, establishes the corresponding relation between SliceID and the resource requirements of each slice user, and is temporarily reserved for the unallocated SliceID without the resource requirements;

And SliceID, temporarily not distributing the resource requirement, updating according to the resource requirement of the subsequent newly added slice user, and synchronously transmitting the updating information to the network equipment.

8. The method of claim 1 or 2, further comprising:

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

9. The method of claim 1 or 2, further comprising:

The SDN controller calculates paths based on SliceID information, FA slice topology and residual slice resource information of virtual member sub-link End.X corresponding to the FA slice topology, and uses virtual member sub-link End.X SIDs to carry out path arrangement.

10. The method of claim 1 wherein when directing sliced user traffic to SRv Policy tunnel transport, the network device determines sliced sub-link physical resources on the outgoing interface according to the indication of slice flag set in the virtual member sub-link end.x SID and forwards the message through the corresponding sub-link physical resource sub-interface when forwarding the message.

11. The method of claim 10, wherein when directing the sliced user traffic to the SRv Policy tunnel, the SDN controller updates one or a combination of SliceID of the virtual member Sub-Link and Sub-Link resource Sub-Link Num, sub-Link resource Sub-Link Num status, virtual member Sub-Link remaining sliced resource information according to information reported by the network device.

12. The method as recited in claim 1, further comprising:

13. The method of claim 12, wherein when dividing the value space of the Sub-Link resource identifier, sub-Link resources corresponding to Sub-Link Num with high 4 bits being 1 are allocated to FA slices for use, and the remaining Sub-Link Num value space is allocated to user slices for use.

14. The method of claim 1 or 2, further comprising:

15. The method of claim 2, 7, 12 or 13, wherein the FA slices are FlexAlgo-based FA slices having a one-to-one correspondence with a corresponding number of divided for a network according to the number of industries or virtual operators;

16. A transmission method, comprising:

When providing service for a slicing user, the forwarding device guides the service flow to SRv 6:6 Policy tunnel for transmission, wherein the SRv 6:6 Policy tunnel is allocated with a slicing identifier SliceID which can meet the resource requirement of the slicing user;

Each forwarding device along SRv of the Policy tunnel path establishes a corresponding relation between SliceID and corresponding sub-link resources of the outgoing interface, wherein each sub-link resource has a bottom physical resource which is independently shared by itself;

Further comprises:

And each forwarding device along the SRv Policy tunnel path allocates one sub-link resource meeting the SliceID resource requirement from the sub-link resources in the idle state of the corresponding physical outgoing interface to forward according to SliceID carried in the forwarding message of the slicing user, and maintains SliceID the corresponding relation between the sub-link resource and the state of the sub-link resource.

17. The method as recited in claim 16, further comprising:

18. The method as recited in claim 16, further comprising:

and enabling the tunnel head node equipment to acquire SliceID from BGPSRv Policy messages issued by the SDN controller and writing the SliceID into a position corresponding to the forwarding plane message.

19. The method of claim 16, wherein when the forwarding device directs the slice user traffic to SRv Policy tunneling, and when the first slice packet arrives at the forwarding device, the forwarding device searches the local table for bandwidth resources required by SliceID according to SliceID carried in the forwarding packet, finds Sub-Link resources Sub-Link Num of unoccupied bandwidth from a Sub-Link resource table of the forwarding device, allocates the Sub-Link resources Sub-Link Num to SliceID, forwards the slice user packet from a corresponding Sub-port, updates a local Sub-Link Num status to occupied, and reports one or a combination of updated Sub-Link resources Sub-Link Num occupation, sliceID and Sub-Link Num correspondence, sub-Link Num status to the SDN controller through telemetry TELEMETRY.

20. A network apparatus, comprising:

Dividing a link corresponding to each network equipment interface into a plurality of sub-link resources according to the resource requirements of slicing users, wherein each sub-link resource has a bottom physical resource which is independent of the sub-link resource;

Establishing a one-to-one binding IPv 6-based source routing technology Policy SRv Policy tunnel for the slicing user according to the resource requirement of the slicing user, and establishing a corresponding relation between slice identifiers SliceID and SRv6 Policy tunnels, wherein the corresponding relation between slice identifiers SliceID and SRv6 Policy tunnels is that a slice identifier SliceID which can meet the resource requirement of the slicing user is allocated for the SRv6 Policy tunnels, and the method further comprises carrying SliceID information of a forwarding plane in BGPSRv6 Policy messages and sending the SliceID information to SRv6 Policy tunnel head nodes, or configuring a mapping relation between a Color template and the forwarding plane SliceID to enable SRv6 Policy tunnel head node equipment to obtain corresponding SliceID according to Color attributes of SRv6 Policy;

21. A network apparatus, comprising:

The dividing module is used for dividing the link corresponding to each network equipment interface into a plurality of sub-link resources according to the resource requirements of the slicing user, and each sub-link resource has a bottom physical resource which is independent of the sub-link resource;

The binding module is used for establishing a one-to-one binding source routing technology Policy SRv based on IPv6 Policy tunnel for the slicing user according to the resource requirement of the slicing user, and establishing a corresponding relation between slice identifiers SliceID and SRv6 Policy tunnel, wherein the corresponding relation between slice identifiers SliceID and SRv6 Policy tunnel is that a slice identifier SliceID capable of meeting the resource requirement of the slicing user is allocated for the SRv6 Policy tunnel;

The binding module is further configured to carry SliceID information of the forwarding plane in BGPSRv Policy messages and send the SliceID information to the SRv Policy tunnel header node, or configure a mapping relationship between the Color template and the forwarding plane SliceID, so that the SRv6 Policy tunnel header node device obtains the corresponding SliceID according to the Color attribute of the SRv6 Policy.

22. A network apparatus, comprising:

When providing service for a slicing user, guiding the service flow to SRv to transmit through a Policy tunnel, wherein the SRv Policy tunnel is allocated with a slicing identifier SliceID which can meet the resource requirement of the slicing user;

Each forwarding device along the SRv6 Policy tunnel path establishes a corresponding relation between SliceID and corresponding sub-link resources of an outgoing interface, each sub-link resource has own independent underlying physical resource, each forwarding device along the SRv Policy tunnel path allocates one sub-link resource meeting the SliceID resource requirement from the sub-link resources of the idle state of the corresponding physical outgoing interface according to SliceID carried in a forwarding message of a slicing user to forward, and maintains the corresponding relation between SliceID and the sub-link resource and the state of the sub-link resource;

23. A network apparatus, comprising:

The transmission module is used for guiding the service flow to SRv Policy tunnel for transmission when providing service for the slicing user, wherein the SRv Policy tunnel is allocated with a slicing identifier SliceID which can meet the resource requirement of the slicing user;

and the relation module is used for establishing SliceID corresponding relation between each forwarding device along the SRv Policy tunnel path and the corresponding sub-link resource of the outgoing interface, wherein each sub-link resource has a bottom physical resource which is independently shared by the forwarding device along the SRv Policy tunnel path, and distributing one sub-link resource which can meet the SliceID resource requirement from the sub-link resources in the idle state of the corresponding physical outgoing interface to forward according to SliceID carried in the forwarding message of the slicing user by each forwarding device along the SRv Policy tunnel path, and maintaining SliceID corresponding relation between the sub-link resource and the state of the sub-link resource.

24. A computer readable storage medium, characterized in that the computer readable storage medium stores a computer program for executing the method of any one of claims 1 to 19.