CN115277548A

CN115277548A - Transmission method, device and storage medium

Info

Publication number: CN115277548A
Application number: CN202110480372.9A
Authority: CN
Inventors: 姜文颖; 程伟强; 杨雪; 龚立艳
Original assignee: China Mobile Communications Group Co Ltd; China Mobile Communications Ltd Research Institute
Current assignee: China Mobile Communications Group Co Ltd; China Mobile Communications Ltd Research Institute
Priority date: 2021-04-30
Filing date: 2021-04-30
Publication date: 2022-11-01

Abstract

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

Description

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, an apparatus, and a storage medium.

Background

The existing slicing technology for data bearing includes FlexAlgo (flexible algorithm) technology, SR-TE (Segment Routing-Traffic Engineering), SRv6Policy (SRv 6 Policy; SRv6: IPv 6-based source Routing IPv 6) tunneling technology.

1. The FlexAlgo (FA for short) technique is briefly described below.

The FA is based on IGP (Interior Gateway Protocol) single topology, each node and each L3 link correspond to one or more FA algorithm spaces, and the FA is issued by the IGP Protocol to form an IGP sub-computation path space.

The FA algorithm comprises three parts: metricType (metric type), calcType (compute type) and Constraint, the result of different FA algorithms is that different sub-topologies are formed. Therefore, the physical network can be divided into a plurality of virtual networks through the FlexAlgo, different SIDs (Segment identifiers) are used for message encapsulation under different FA slices, and different addresses are independently calculated to guide the message to be forwarded on 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 sub-topologies of different FA slices, where, as shown in the figure, the FA examples are as follows: different nodes are added to different FAs based on IGP Metric or TE (Traffic Engineering) Metric calculation paths, and different physical links are added to different FlexAlgo by setting color (color) attributes and matching calculation path constraints (such as affinity attributes including a certain 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:

automatic traffic diversion: by carrying the FA-ID when advertising a prefix SID (prefix SID), it is indicated that a prefix needs to be computed for this purpose using a specific FA algorithm. The service can find a corresponding FA-LSP (The Liskov localization Principle) according to a single prefix SID based on The FA or a specific SR (Segment Routing) list and The like.

2. The SR-TE, SRv6Policy technology is briefly described below.

SR-TE and SRv6Policy are source routing tunnel technologies, and can calculate a path Segmentlist < SID1, SID2, \\ 8230; SIDN > meeting requirements for a user in a network based on SLA (Service-Level Agreement) requirements of the user, such as time delay and bandwidth, and guide user messages to be forwarded in the network along a specified path.

The tunnel path Segmentlist may be arranged with node SIDs or with neighbor SIDs. When each hop SID in the path uses an adjacent SID, the tunnel path is a strict path, and each hop is designated; when some SIDs in the path use node SIDs, then the tunnel path is a one-hop loose path because there may be different reachable links between two nodes.

1. The disadvantages of the FlexAlgo slicing technique are:

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

2. The disadvantages of the SR-TE, SRv6Policy technique for slicing are:

the SR-TE and SRv6Policy solve the path planning problem by themselves, which instructs the packet to avoid the congested road segment and forward along the specified path, but resources, such as bandwidth, on each physical link on the forwarding path cannot be guaranteed, because link resources are also shared by all tunnels, the link resources cannot be associated with sub-link physical resources on the bottom layer, only logical isolation is achieved, and the hard slice requirement of the user for exclusive sharing of resources cannot be met.

Therefore, the prior art has the following defects: there is no slicing scheme that can associate the underlying sublink 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 associated with physical resources of bottom sublinks exists.

The invention provides the following technical scheme:

a method of transmission, comprising:

dividing a link corresponding to each network equipment interface into a plurality of sub-link resources by a Software Defined Network (SDN) controller according to the resource requirements of slice users;

establishing a corresponding relation between slice identification SliceID and resource requirements;

and establishing a one-to-one binding source routing technology strategy SRv6Policy tunnel based on IPv6 for the user according to the resource requirement of the slice user, and establishing a corresponding relation between the slice identifier SliceID and the SRv6Policy tunnel.

In an implementation, the method further comprises the following steps:

slice users are users in flexible algorithm FA slices based on the flexible algorithm FlexAlgo;

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

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

In an implementation, the method further comprises the following steps:

and establishing a corresponding relation between the slice identification SliceID and the SRv6Policy tunnel, namely allocating a slice identification SliceID which can meet the resource requirement of a slice user to the SRv6Policy tunnel.

In an implementation, the method further comprises the following steps:

Sub-Link identifiers Sub-Link Num are adopted to identify Sub-Link resources, each Sub-Link has a bottom-layer physical resource which is owned by the Sub-Link, and the Sub-Link Num and the Sub-Link resource IDs of various types are maintained to be compatible with the bottom-layer physical Sub-Link resources of various types.

In an implementation, the method further comprises the following steps:

and adding identifiers in the IPv 6-based source routing technology CAPABILITY sub-type, the length, the SRv6Capabilities sub-TLV of the routing CAPABILITY type, the length, the value SRv6Capabilities sub-TLV and the IPv 6-based source routing technology CAPABILITY type, the length, the value SRv6Capabilities TLV of the border gateway protocol link type BGP-LS, so as to indicate the CAPABILITY of the equipment for supporting carrying the SliceID on a forwarding plane and carrying out slicing processing.

In an implementation, the method further comprises the following steps:

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

In an implementation, the method further comprises the following steps:

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

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

when the number of sliceIDs is distributed, distributing the preset number of sliceIDs for each FA slice on the SDN controller, and then sending the preset number of sliceIDs to equipment;

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

and updating the SliceID which is not allocated with the bandwidth requirement temporarily according to the bandwidth requirement of the subsequent newly-added slice user, and synchronously sending the updated information to the equipment.

In an implementation, the method further comprises the following steps:

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

FA slice SliceID, virtual member sublink end.X SID, total reserved resources of the virtual member sublink end.X SID, the corresponding relation of the number of SliceIDs, the requirement of each SliceID resource, the state of each SliceID resource and the total residual slice resources of the virtual member sublinks.

In an implementation, the method further comprises the following steps:

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

In an implementation, the method further comprises the following steps:

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

In an implementation, the method further comprises the following steps:

and the SDN controller performs path calculation based on the SliceID information, the FA topology and the residual slice resource information of the virtual member sublink end.X corresponding to the FA topology, and performs path arrangement by using the virtual member sublink end.XSID.

In implementation, when the slice user traffic is guided to the SRv6Policy tunnel for transmission, when the forwarding device forwards a message, the physical resource of the slice sublink is determined on the output interface according to the indication of the slice flag setting in the end.x SID of the virtual member sublink, and the message is forwarded through the corresponding sublink physical resource subinterface.

In implementation, when slice user traffic is guided to SRv6Policy tunnel transmission, the SDN controller updates one or a combination of the following information according to information reported by the device: the corresponding relation between SliceID of the virtual member sublink and sublink resource Sub-Link Num, sublink resource Sub-Link Num state and virtual member sublink residual slice resource information.

In an implementation, the method further comprises the following steps:

the value space of the sublink resource identifiers is divided to distinguish the sublink resource identifiers used by the FA slice and the user slice.

In implementation, when the value space of the sublink resource identifier is divided, the sublink resource corresponding to the Sub-Link Num with the high 4-bit 1 is allocated to the FA slice for use, and the other Sub-Link Num value spaces are allocated to the user slice for use.

In an implementation, the method further comprises the following steps:

and in each FA slice topology, reserving residual bandwidth resources which are not allocated to the user slice in the total bandwidth, sharing and using the residual bandwidth resources for non-slice users in the FA slice topology, and carrying the traffic of the non-slice users through SRv6 BE.

In implementation, the FA slices are divided into corresponding number of FA slices based on FlexAlgo, which have one-to-one correspondence relationship, for a network according to the number of industries or virtual operators;

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

A method of transmission, comprising:

when providing services for the slicing users, the forwarding equipment guides the service flow to SRv6Policy tunnel transmission;

and establishing a corresponding relation between the SliceID and each interface sublink resource on an SRv6Policy tunnel path.

In an implementation, the method further comprises the following steps:

the interior gateway protocol IGP flooding advertises one or a combination of the following information: and the end.X SID of each FA slice virtual member sublink on the link, the reserved total bandwidth, the number of SliceIDs or the resource information corresponding to each SliceID.

In an implementation, the method further comprises the following steps:

and enabling the tunnel head node equipment to acquire the SliceID from a BGP SRv6Policy message issued by the SDN controller and write the SliceID into a position corresponding to the forwarding plane message.

In implementation, when the forwarding device guides the slice user traffic to the SRv6Policy tunnel for transmission, according to the SliceID carried in the slice user forwarding message, a sublink resource capable of meeting the requirement of the SliceID resource is allocated from the sublink resource in the idle state corresponding to the physical output interface for forwarding, and the correspondence between the SliceID and the sublink resource and the state of the sublink resource are maintained.

In implementation, when a forwarding device directs the slice user traffic to SRv6Policy tunnel transmission, when a first slice packet arrives at the device, the device searches a local table according to a SliceID carried in the forwarding packet to obtain bandwidth resources required by the SliceID, finds out a Sub-Link resource Sub-Link Num of unoccupied bandwidth from the Sub-Link resource table of the local device, allocates the Sub-Link resource Sub-Link Num to the SliceID, forwards the slice user packet from a corresponding Sub-port, updates the state of the local Sub-Link resource Sub-Link Num to be occupied, and reports and updates one or a combination of the following information to an SDN controller through a Telemetry teleteleteletool: the occupation condition of Sub-Link Num of the sublink resource, the corresponding relation between SliceID and Sub-Link Num and the state of Sub-Link Num.

A network apparatus, comprising:

a processor for reading the program in the memory, performing the following processes:

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

according to the resource requirement of the slicing user, establishing a one-to-one binding source routing technology strategy SRv6Policy tunnel based on IPv6 for the user, and establishing a corresponding relation between the slicing identification SliceID and the SRv6Policy tunnel;

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

In an implementation, the method further comprises the following steps:

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

In an implementation, the method further comprises the following steps:

and establishing a corresponding relation between the slice identifier SliceID and the SRv6Policy tunnel, namely allocating a slice identifier SliceID which can meet the resource requirement of a slice user to the SRv6Policy tunnel.

In an implementation, the method further comprises the following steps:

an identifier is added to the end segment identifier subtype, length, value end.x SID sub-TLV structure to indicate that the device is an adjacent SID for a virtual member sublink, rather than an adjacent SID for a physical link.

In an implementation, the method further comprises the following steps:

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

distributing SliceID resources of a forwarding plane for each user according to the requirements of slice users in FA slice topology, establishing a corresponding relation between the SliceID and the resource requirements of the slice users, and temporarily reserving the unassigned SliceID without resource requirements;

In an implementation, the method further comprises the following steps:

the following information is maintained and/or updated:

In an implementation, the method further comprises the following steps:

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

In implementation, when the traffic of the slice user is guided to the SRv6Policy tunnel for transmission, when the forwarding device forwards a message, according to the indication of the slice flag setting in the virtual member sublink end.x SID, the physical resource of the slice sublink is determined on the output interface, and the message is forwarded through the corresponding sublink physical resource subinterface.

In an implementation, the method further comprises the following steps:

the method is used for distinguishing the sub-link resource identifiers used by the FA slice and the user slice by dividing the value space of the sub-link resource identifiers.

In an implementation, the method further comprises the following steps:

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

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 slice users;

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

and the binding module is used for establishing a one-to-one binding source routing technical strategy SRv6Policy tunnel based on IPv6 for the user according to the resource requirement of the slice user and establishing the corresponding relation between the slice identification SliceID and the SRv6Policy tunnel.

In an implementation, the method further comprises the following steps:

In implementation, the binding module is further configured to establish a correspondence between the slice identifier SliceID and the SRv6Policy tunnel, where the correspondence is to allocate a slice identifier SliceID that can meet the resource requirement of a slice user to the SRv6Policy tunnel.

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

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

In an implementation, the binding module is further configured to add an identifier at the end segment identifier subtype, length, value end.x SID sub-TLV structure to indicate that the device is an adjacent SID of the virtual member sublink, rather than an adjacent 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 a slice resource subtype, length, value Sub-TLV structure.

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

distributing a SliceID resource of a forwarding plane for each user according to the requirements of slice users in FA slice topology, establishing a corresponding relation between the SliceID and the resource requirements of the slice users, and temporarily reserving unallocated SliceIDs without resource requirements;

and updating the SliceID which is not allocated with the bandwidth requirement temporarily according to the bandwidth requirement of the subsequent newly-added slice user, and synchronously issuing the updated information to the equipment.

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

FA slice SliceID, virtual member sublink end.X SID, total reserved resource of the virtual member sublink end.X SID, corresponding relation of SliceID quantity, requirement of SliceID resource, state of SliceID resource and total residual slice resource of the virtual member sublink.

In an implementation, the binding module is further configured to carry SliceID information of the forwarding plane in a BGP SRv6Policy message.

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

In implementation, the binding module is further configured to perform path calculation based on the SliceID information, the FA topology, and the remaining slice resource information of the virtual member sublink end.x corresponding to the FA topology, and perform path organization using the virtual member sublink end.x SID.

In implementation, the binding module is further configured to, when the slice user traffic is guided to an SRv6Policy tunnel for transmission, enable the forwarding device to determine, according to an indication of a slice flag set in the end.x SID of the virtual member sublink, a slice sublink physical resource on the output interface when forwarding a message, and forward the message through a corresponding sublink physical resource subinterface.

In implementation, the binding module is further configured to update one or a combination of the following information according to the information reported by the device when the slice user traffic is guided to the SRv6Policy tunnel for transmission: the corresponding relation between SliceID of the virtual member sublink and sublink resources Sub-Link Num, the state of the sublink resources Sub-Link Num and the information of the residual slice resources of the virtual member sublink.

In implementation, the dividing module is further configured to divide the value space of the sublink resource identifier to distinguish the sublink resource identifier used by the FA slice from the sublink resource identifier used by the user slice.

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

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

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

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:

when providing services for the slice users, guiding the service flow to SRv6Policy tunnel transmission;

establishing a corresponding relation between the SliceID and each interface sublink resource on an SRv6Policy tunnel path;

In an implementation, the method further comprises the following steps:

the interior gateway protocol IGP flooding advertises one or a combination of the following information: and the end.X SID, the total reserved bandwidth, the number of SliceIDs or the resource information corresponding to each SliceID of the virtual member sublink of each FA slice on the link.

In an implementation, the method further comprises the following steps:

In implementation, when the traffic of the slice user is guided to the SRv6Policy tunnel for transmission, according to the SliceID carried in the slice user forwarding message, a sublink resource capable of meeting the requirements of the SliceID resource is allocated from the sublink resource in the idle state corresponding to the physical output interface for forwarding, and the corresponding relation between the SliceID and the sublink resource and the state of the sublink resource are maintained.

In implementation, when slice user traffic is guided to SRv6Policy tunnel transmission, when a first slice packet arrives at a device, the device searches a local table according to a SliceID carried in a forwarding packet to obtain bandwidth resources required by the SliceID, finds a Sub-Link resource Sub-Link Num of unoccupied bandwidth from the Sub-Link resource table of the local device, allocates the Sub-Link resource Sub-Link Num to the SliceID, forwards the slice user packet from a corresponding Sub-port, updates the state of the local Sub-Link resource Sub-Link Num to be occupied, and reports and updates one or a combination of the following information to an SDN controller through teleteleteleteleteleteleteleteleteleteleteleteletelemetry: the occupation condition of Sub-Link Num of the Sub-Link resource, the corresponding relation between SliceID and Sub-Link Num and the state of Sub-Link Num.

A network apparatus, comprising:

the transmission module is used for guiding the service flow to SRv6Policy tunnel transmission when providing services for the slice users;

and the relation module is used for establishing the corresponding relation between the SliceID and each interface sublink resource on the SRv6Policy tunnel path.

In an implementation, the relationship module is further configured to advertise one or a combination of the following information in an interior gateway protocol IGP flood: and the end.X SID, the total reserved bandwidth, the number of SliceIDs or the resource information corresponding to each SliceID of the virtual member sublink of each FA slice on the link.

In implementation, the relationship module is further configured to enable the tunnel head node device to obtain SliceID from a BGP SRv6Policy message issued by the SDN controller, and write the SliceID into a position corresponding to the forwarding plane packet.

In implementation, the transmission module is further configured to, when the traffic of the slice user is guided to the SRv6Policy tunnel for transmission, allocate a sublink resource that can meet the requirement of the slicid resource from the sublink resource in the idle state corresponding to the physical output interface according to the slicid carried in the slice user forwarding message for forwarding, and maintain the correspondence between the slicid and the sublink resource and the state of the sublink resource.

In implementation, the transmission module is further configured to, when the slice user traffic is guided to the SRv6Policy tunnel for transmission, when a first slice packet arrives at the device, enable the device to search the local table according to the SliceID carried in the forwarding packet to obtain the bandwidth resource required by the SliceID, find the Sub-Link resource Sub-Link Num of the unoccupied bandwidth from the Sub-Link resource table of the local device, allocate the Sub-Link resource Sub-Link Num to the SliceID, forward the slice user packet from the corresponding Sub-port, update the state of the local Sub-Link resource Sub-Link Num to be occupied, and report and update one or a combination of the following information to the SDN controller through the Telemetry teleteleteletelemeter: the occupation condition of Sub-Link Num of the Sub-Link resource, the corresponding relation between SliceID and Sub-Link Num and the state of Sub-Link Num.

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

The invention has the following beneficial effects:

the technical scheme provided by the embodiment of the invention is a resource-guaranteed bearer network slicing scheme and mechanism based on FlexAlgo and SRv 6. By expanding the FlexAlgo technology and combining with the SRv6 tunnel encapsulation, the slice ID and the concentrated management and control capability of the SDN are carried on the forwarding surface, and the dynamically adjustable sublink-level data bearer network two-level slice service with resource guarantee is provided for users. The first-level section is realized by a FlexAlgo technology, so that the method can be used for section isolation of different maintenance subjects or distributing different sections for different industries; because the second-level slice carries the slice ID on the forwarding plane through the SRv6 tunnel technology, the second-level user-level or service-level slice in the first-level FA slice is realized.

Because the slice resources on the same physical link can be shared independently, compared with the existing FlexAlgo technology, the method can solve the problems that each slice of the FlexAlgo can only share one physical link independently, the isolation granularity is coarse, the existing network resources basically cannot be met, and the hard isolation of the slice cannot be realized by large-scale deployment.

Because the bottom layer 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 a tunnel.

Because the single FA enhancement technology and the single SRv6Policy + forwarding plane slicing technology can only provide one-level slicing service, the scheme provides a dynamically adjustable sublink-level data carrying network two-level slicing service with resource guarantee, and can meet the requirements of two-level slicing scenes 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 not to limit 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 diagram illustrating the sub-topology of different FA slices in the prior art;

fig. 3 is a schematic flow chart illustrating an implementation of a transmission method at an SDN controller side according to an embodiment of the present invention;

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

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

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

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

FIG. 8 is an extended schematic diagram of an ISIS SRv6Capabilities sub-TLV structure in an embodiment of the present invention;

FIG. 9 is a schematic diagram of an extended structure of a BGP-LS SRv6Capabilities sub-TLV in an embodiment of the present invention;

FIG. 10 is a schematic structural diagram of a BGP SRv6Policy extension SliceID in the embodiment of the present invention;

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

fig. 12 is a schematic diagram of End SID and end.x SID distribution of each device in the embodiment of the present invention;

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

FIG. 14 is a schematic diagram of a forwarding process of a user 1 message SRv6Policy tunnel in the power industry in an embodiment of the present invention;

fig. 15 is a schematic structural diagram of a network device serving as an SDN controller according to an embodiment of the present invention;

fig. 16 is a schematic flow chart illustrating an implementation of a transmission method at a forwarding device side in an embodiment of the present invention;

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

Detailed Description

The inventor notices in the process of invention that:

a slicing scheme capable of associating physical resources of the sub-links at the bottom layer is needed to match the actual resource condition of the existing network, so that the sharing of the physical resources at the bottom layer of each granularity of the sub-links at the slicing level is realized, and the network value is improved.

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

In the description process, the implementation of the SDN controller and the forwarding device side will be described separately, and then an example of the implementation of the SDN controller and the forwarding device in cooperation will be given to better understand the implementation of the scheme provided in the embodiment of the present invention. Such an explanation does not mean that the two must be implemented cooperatively or separately, and actually, when the SDN controller and the forwarding device are implemented separately, each of them also solves the problem on its 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, as shown in the figure, the method may include:

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

step 302, establishing a corresponding relation between slice identification SliceID and resource requirements;

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

In an implementation, the method further comprises the following steps:

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

In an implementation, the method further comprises the following steps:

The following describes the implementation on the forwarding device.

Fig. 16 is a schematic flow chart of an implementation of a transmission method on a forwarding device side, as shown in the figure, the method may include:

step 1601, when providing services for the slice user, the forwarding device directs the service traffic to SRv6Policy tunnel for transmission;

and step 1602, establishing a corresponding relation between the SliceID and each interface sublink resource on the SRv6Policy tunnel path.

In an implementation, the method further comprises the following steps:

In implementation, when a forwarding device guides a slice user flow to SRv6Policy tunnel transmission, when a first slice packet arrives at the device, the device searches a local table according to a SliceID carried in the forwarding packet to obtain a bandwidth resource required by the SliceID, finds a Sub-Link resource Sub-Link Num of an unoccupied bandwidth from a Sub-Link resource table of the local device, allocates the Sub-Link resource Sub-Link Num to the SliceID, forwards the slice user packet from a corresponding Sub-port, updates the state of the local Sub-Link resource Sub-Link Num to be occupied, and reports and updates one or a combination of the following information to an SDN controller through a Telemetry teleteleteleteleteleteleteleteleteletelemanagement: the occupation condition of Sub-Link Num of the sublink resource, the corresponding relation between SliceID and Sub-Link Num and the state of Sub-Link Num.

In the following, the SDN controller is mainly used, and the forwarding device is described in combination 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, a corresponding number of FA slices based on FlexAlgo are divided for the network in advance, that is, there is a one-to-one correspondence between the industries or virtual operators and the FA slices based on FlexAlgo, and they can be configured in advance. And the controller determines the FA slice based on FlexAlgo according to the industry or virtual operator to which the slice user belongs.

Specifically, the scheme is a resource-guaranteed bearer network slicing scheme and mechanism based on FlexAlgo and SRv 6. By expanding the existing FlexAlgo technology and combining with the centralized management and control capability of an SDN (Software Defined Network) on a forwarding surface when an SRv6 tunnel is packaged, the dynamically adjustable sub-link-level data bearer Network two-level slicing service with resource guarantee is provided for users.

The first-stage slicing is realized by a FlexAlgo technology, and can be used for slicing isolation of different maintenance subjects or distributing different slices for different industries; the second-level slice carries the slice ID on the forwarding plane through an SRv6 tunnel technology to realize the second-level user-level or service-level slice in the first-level FA slice.

In implementation, the correspondence between the sliceID in the FA slice based on FlexAlgo and the SRv6Policy tunnel to which the slice user belongs is established, and the correspondence between the sliceID in the FA slice and the sub-link resources of each interface on the SRv6Policy tunnel path is established.

SliceID and Sub-Link Num will be mainly used as an example for explanation.

(1) SDN controller resource management mechanisms.

When the number of sliceIDs is distributed, distributing a preset number of sliceIDs for each FA slice on the SDN controller, and then sending the preset number of sliceIDs to the equipment;

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

Specifically, the following describes an end.x SID distribution and total resource reservation mechanism and method for a virtual member sublink in an FA slice topology, and an implementation of a policy id number distribution rule of a forwarding plane in the FA slice topology.

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

Specifically, the following will describe the implementation of maintaining the correspondence relationship between the FA slice SliceID, the virtual member sublink end.xsld, the total reserved resources thereof, and the number of sliceids on the controller, and maintaining and updating the information such as the resource requirement and state of each SliceID, the total remaining slice resources of the virtual member sublink.

1) And allocating the end.X SID of the virtual member sublink of the FA primary slice and reserving slice resources.

Firstly, allocating different Locator (positioning point) spaces for each FA slice, then allocating different End SIDs (End SIDs) for each node in the FA slice topology in the Locator space according to the topology requirements of the first-level FA slice by the controller, and allocating different end.X SIDs for each virtual member sublink; meanwhile, according to the bandwidth requirement of the first-level FA slice, reserving corresponding bandwidth resources for each FA slice topology; and transmitting each End SID, end.X SID and the information of the reserved bandwidth to corresponding equipment in the network, executing corresponding configuration by the equipment, and storing the corresponding relation between the end.X SID and the reserved bandwidth. Specifically, the following table can be used:

table 1: dynamic resource allocation table for virtual member sublink adjacent SID

FA slice ID	End.X SID	Total bandwidth reservation (G)
			128	X1:1::1 (belonging to the address space of the FA 118)	5G
129	X2:1::1 (belonging to the FA129 address space)	10G
			130	X3:1::1 (belonging to the address space of FA 130)	15G

The information can also be configured on the equipment directly and reported to the controller through BGP-LS (BGP Link State; BGP: border Gateway Protocol, border Gateway Protocol) so that the information of the two parties is consistent.

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

2) And distributing the number of sliceID of the transfer surface in the FA slice topology.

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

Allocating a fixed number of SliceIDs for each FA slice; or distributing a certain number of sliceIDs for each FA slice and sending the sliceIDs to the equipment.

Static allocation mode: distributing a fixed number of SliceIDs for each FA slice, wherein if 500 SliceIDs are distributed, the SliceIDs of forwarding surfaces reserved for the FA128 slice topology are 1-500, the SliceIDs of forwarding surfaces reserved for the FA129 slice topology are 501-1000, and so on, the SliceIDs of forwarding surfaces reserved for the FAn slice topology are [ n-128 ] 500+1 ] to [ n-128 ] 500+500 ].

Dynamic allocation mode: and distributing a certain number of SliceIDs for each FA slice, issuing the SliceIDs to the equipment, and flooding information of the SliceIDs in the IGP and informing each equipment.

3) And distributing and maintaining the states of the SliceIDs of the forwarding surfaces corresponding to the users of the secondary slices.

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

Specifically, the controller allocates a forwarding plane SliceID resource and corresponding bandwidth information to each user according to the requirements of secondary slice users in the primary FA slice topology, and the unallocated SliceID is temporarily reserved. Specific examples thereof are shown in the following table.

Table 2: resource demand allocation table corresponding to SliceID of forwarding surface

The sliceids which are not allocated with bandwidth requirements temporarily in the table above 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, unallocated, and the like.

If the route calculation needs to be carried out by the head node, each SliceID and corresponding bandwidth resource information need to be expanded through ISIS (Intermediate system to Intermediate system) and flooded in the IGP; if all the controllers are adopted for calculating the paths, flooding is not needed.

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

When slice user flow in FA slices of FlexAlgo is guided to an SRv6Policy tunnel for transmission, forwarding equipment allocates a sublink resource capable of meeting the SliceID resource requirement from the sublink resource in an idle state corresponding to a physical output interface according to SliceID carried in a slice user forwarding message for forwarding, and maintains the corresponding relation between the SliceID and the sublink resource and the state of the sublink resource.

A method for allocating a sub-link resource (such as MTN (metropolitan Area Network) sub-interface, VLAN (Virtual Local Area Network) enhancer interface, channelization sub-interface resource, flexE sub-interface, independent QoS (Quality of Service) queue, etc.) that can meet the requirements of the SliceID resource from the sub-link resource in the idle state corresponding to the physical output interface to the forwarding device according to the SliceID carried in the slice user forwarding message; the corresponding relation between the SliceID and the sub-link resource and the dynamic maintenance mechanism and method of the state of the sub-link resource are explained.

When slice user flow in FA slices of FlexAlgo is guided to an SRv6Policy tunnel for transmission, sub-Link Num is adopted to identify bottom-layer physical Sub-Link resources, each Sub-Link has a bottom-layer physical resource which is owned by the Sub-Link, and the Sub-Link resources of various types are compatible by storing and maintaining the corresponding relation between the Sub-Link Num and the Sub-Link resource IDs of various types.

Specifically, sub-Link Num is introduced to uniformly identify bottom-layer physical Sub-Link resources, each Sub-Link has a bottom-layer physical resource which is shared independently, such as an MTN Sub-interface, a VLAN enhancer interface, a channelized Sub-interface resource, a FlexE Sub-interface, an independent QoS queue and the like, and the Sub-Link Num is maintained and corresponding to the ID of each type of Sub-Link resource to be compatible with each type of bottom-layer physical Sub-Link resource.

Specifically, the controller divides each physical Link corresponding to all devices in the primary FA slice topology into a plurality of Sub-links isolated from each other according to the requirements of the secondary slice users, each Sub-Link has its own exclusive bottom-layer physical resources, such as MTN Sub-interfaces, VLAN enhancer interfaces, channel channelization Sub-interface resources, flexE Sub-interfaces, independent QoS queues, and is identified by Sub-Link Num, the length of the Sub-Link identifier is 4 bytes, wherein the low bits represent Sub-Link resource IDs, such as MTNID, VLAN ID, channel ID, flexEID, qosqueued, the Sub-Link resource IDs are less than 32 bits, and the high bits are filled with 0.

In implementation, the value space of the sublink resource identifier is divided to distinguish the sublink resource identifiers used by the FA slice and the user slice.

The user slice, which may also be referred to as a forwarding plane slice, is a slice for establishing an SRv6 tunnel based on the SliceID associated with the underlying sublink resource.

In specific implementation, when the value space of the sublink resource identifier is divided, sublink resources corresponding to Sub-Link Num with the height of 4 bits being 1 are allocated to FA slices for use, and the other Sub-Link Num value spaces are allocated to user slices for use.

For example, the sublink resource corresponding to the Sub-Link Num with the upper 4 bits being 1 is used for being allocated to the FA level one slice for use.

Taking the sublink resource as the channelized subinterface as an example, an example may be as follows (for simplicity, each number in the following table represents a decimal value of 8 bits):

table 3: sublink physical resource allocation table

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

1. To be compatible with each type of underlying resource, a sublink identifier is therefore introduced: sub-Link Num; it is also possible to use the ChannelID directly to identify a specific sublink without the need for Sub-Link Num.

2. Physical resources other than Bandwidth may also be configured for MTN subinterface/VLAN enhancer interface/Channel channelized subinterface resources/FlexE subinterface/independent QoS queues, only the Bandwidth resources being exemplified here.

The controller issues the configuration of the corresponding relation to each device in the network, and the devices execute the relevant configuration locally and store the corresponding relation.

The controller is responsible for maintaining the state of each Sub-Link Num on the Link, such as idle state, pre-occupation state, occupied state and the like, and updating the state of the Sub-Link Num in real time according to the occupation condition of the Sub-Link resource Sub-Link Num reported by the equipment through telemeasurement.

(2) IGP floods slice-related link information.

Advertising one or a combination of the following information at IGP flooding: and the end.X SID of each FA slice virtual member sublink on the link, the reserved total bandwidth, the number of SliceIDs or the resource information corresponding to each SliceID.

The method for the end.x SID, the total reserved bandwidth, the number of sliceids and the resource information corresponding to each SliceID of the virtual member sublink per FA slice on the IGP flooding advertisement link will be described below.

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

1) End.x SID information for the virtual member sublink of the FA slice is advertised.

In implementation, an identifier is added to the end.x SID sub-TLV structure to indicate that the device is an adjacent SID of a virtual member sublink, rather than an adjacent SID of a 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 an adjacent SID for a virtual member sublink, rather than an adjacent SID for a physical link.

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

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

2) Notification of link slice information: the SliceID (slice identity) of the FA and the corresponding resource information announcement.

The number of link slices and corresponding resource information is 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 resource of the FA, the number of sliceids and the slice resource information corresponding to each SliceID can be notified through a sub-TLV of a GENINFO TLV (basic information TLV) in RFC6823, and when an original system slice is full, the slice resource information of the interface can be continuously notified in an extended slice.

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

type (8 bit): TBD (to be determined) is to be applied;

length (8 bit): the message Length does not contain Type and Length;

flags (8 bit): marking;

ibit: after setting, indicating that the link identification information is 4 bytes of IPv4 (Internet Protocol Version 4) interface address;

vbit: after setting, indicating that the link identification is an IPv6 (Internet Protocol Version 6) interface address with 16 bytes;

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

xbit: after setting, indicating that the sublink identification information is 16 bytes of end.X SID;

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

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

SliceIDCount (8 bit): the number of slice IDs;

FirstSliceID (24 bit): a slice ID start value;

Sub-TLVs: and the slice resource sub-sub-TLV is used for announcing the resource information of each SliceID.

Fig. 6 is a schematic structural diagram 1 of a slice resource sub-sub-TLV, and as shown in the figure, the newly defined slice resource sub-sub-TLV is used for announcing resource information of a SliceID, and the structure is as follows:

type (8 bit): TBD is to be applied;

length (8 bit): the length of the message;

flags (8 bit): reserving;

reserved (16 bit): reserving;

SliceID (24 bit): a slice ID value;

optional Sub-Sub-TLVs: slice resource information (maximum reserved link bandwidth, available bandwidth, used bandwidth, time delay, link packet loss rate and the like) corresponding to the SliceID is carried, and sub-TLV defined in the prior RFC8570 can be reused, as follows:

type (Type)	Description (Explanation)
		33	Unidirective Link Delay
34	Min/Max Unidirective Link Delay (minimum/maximum Unidirectional Link Delay)
		35	Unidirective Delay Variation
36	Unidirectional Link Loss
		37	Unidirective Residual Bandwidth (Unidirectional Residual Bandwidth)
38	Unidirectional Available bandWidth)
		39	Unidirective unused Bandwidth (Unidirectional utilization of Bandwidth)

Fig. 7 is a structural diagram of a Sub-Sub-TLV of slice resources 2, and the optional Sub-Sub-TLVs can also be directly filled in with Bandwidth/Delay/. The structural diagram is shown in fig. 7:

(3) Device slice capability advertisement.

And adding identifications in the SRv6Capabilities sub-TLV of the Router CAPABILITY TLV and the SRv6Capabilities TLV of the BGP-LS to indicate the CAPABILITY of the equipment for supporting the SliceID carried on the forwarding surface and carrying out slicing processing.

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

And adding an identifier in FADF (Flexible Algorithm Definition Flags) sub-TLV of FAD (Flexible Algorithm Definition) TLV of BGP-LS Node NLRI (Node NLRI; NLRI: network Layer Reachability Information) for indicating that the virtual member sub-link Information based on the interface is calculated during the route calculation.

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 that the virtual member sub-link information based on the interface is calculated when the link is calculated.

1) And expanding the SRv6Capabilities sub-TLV of the Router CAPABILITY TLV, and adding a Q-flag to indicate that the equipment supports the slice processing CAPABILITY of the forwarding plane. Fig. 8 is an extended schematic diagram of an ISIS SRv6Capabilities sub-TLV structure, which is specifically shown in fig. 8.

2) And the SRv6 Capability TLV of the BGP-LS is expanded, a Q-flag is added, and the notification node has the forwarding plane slice processing capacity. FIG. 9 is a schematic diagram of an extended structure of BGP-LS SRv6Capabilities sub-TLV, which is specifically shown in FIG. 9.

(5) The extended BGP SRv6Policy carries the forwarding plane SliceID information.

Specifically, the BGP SRv6Policy structure extension carries the SliceID information of the forwarding plane.

Fig. 10 is a schematic structural diagram of BGP SRv6Policy extension SliceID, where BGP SRv6Policy is extended and SliceID (shaded) is added, and the format after extension is as shown in fig. 10.

(6) And (3) dynamically maintaining the corresponding relation between the SliceID of the slice user forwarding plane and Sub-Link Num (Sub-Link identifier).

The following describes a mechanism and a method for real-time synchronizing SliceID and Sub-Link Num correspondence and Sub-Link resource Sub-Link Num occupation conditions to a controller by a forwarding device through Telemetry.

When slice user flow in an FA slice of FlexAlgo is guided to an SRv6Policy tunnel for transmission, when a first slice message reaches equipment, the equipment searches a local table according to a SliceID carried in a forwarding message to obtain a bandwidth resource required by the SliceID, finds a Sub-Link resource Sub-Link Num of unoccupied bandwidth from the Sub-Link resource table of the local equipment, allocates the Sub-Link resource Sub-Link Num to the SliceID, forwards the slice user message from a corresponding Sub-port, updates the state of the Sub-Link resource Sub-Link Num to be occupied, and reports and updates one or a combination of the following information to a controller through Telemetry: the occupation condition of Sub-Link Num of the Sub-Link resource, the corresponding relation between SliceID and Sub-Link Num and the state of Sub-Link Num.

Specifically, when a first slice message reaches the device, the device searches the local table according to the SliceID carried in the forwarding message to obtain the bandwidth resource required by the SliceID, if the bandwidth resource is 100M, the unoccupied 100M Sub-Link resource Sub-Link Num is found from the local device Sub-Link resource table, the resource is allocated to the SliceID, the slice user message is forwarded from the corresponding Sub-port, such as an informatization Sub-interface, meanwhile, the state of the local Sub-Link resource Sub-Link Num is updated to be occupied, and the occupation condition of the updated Sub-Link resource Sub-Link Num is reported to the controller in real time through Telemetry. Table 4 is a table of correspondence between SliceID and Sub-Link Num, and the specific relationship can be shown as table.

Table 4: sliceID and Sub-Link Num corresponding relation table

SliceID	Sub-Link Num
			1	0001
2	0002
		501	0003
502	0004
		1001	0005
……	……

(7) Color contained in each EAG (Extended assisted Group, extended Administrative Group) sub-TLV of each adjacent TLV corresponding to each physical link on the node at least contains color required to be contained in the routing constraint of the FA slice to which each sub-link belongs.

(8) And generating a slice topology.

The controller can know the FA slice to which the equipment belongs according to the FAD sub-TLV information reported by each forwarding equipment through BGP-LS; according to color contained in EAG sub-TLVs of adjacent TLVs corresponding to each physical link, and FA route calculation constraint, knowing the FA slice to which the color belongs; according to the Q-flag setting of the FADF sub-TLV, when the user knows that the user needs to calculate the path based on the virtual member sublink on the device, the user further knows the FA slice information of the virtual sublink corresponding to each physical link according to the Algorithm of the end.X SID of the virtual member sublink, and different FA slice topologies are formed on the controller.

(9) SliceID is carried in the forwarding message.

Mode 1: and the tunnel head node equipment acquires the SliceID from a BGP SRv6Policy message issued by the SDN controller and writes the SliceID into a position corresponding to the forwarding plane message.

Specifically, the tunnel head node obtains the SliceID from the BGP SRv6policy message sent from the controller, and writes the SliceID into the corresponding position of the forwarding plane packet.

The controller sends the SliceID and the CadidatePath together (see an expansion structure in figure 10) to a head node of the SRv6 tunnel through a BGP SRv6Policy protocol, and when the head node equipment encapsulates the SRv6 tunnel, sliceID information is carried in a forwarding message.

Mode 2: and configuring a mapping relation between the Color template and the SliceID of the forwarding surface, and acquiring the corresponding SliceID by the tunnel head node equipment according to the Color attribute of the SRv6 Policy.

Specifically, a Color template and a forwarding surface SliceID mapping relation is configured, the head node device obtains a corresponding SliceID according to the Color attribute of the SRv6Policy, and SliceID information is carried in a forwarding message.

Wherein: the SliceID information can be placed in a source address, a FlowLabel (flow label) or an HBH (Hop By Hop) field of a forwarding message; the 1 flag bit of a TrafficClass field is used to indicate that the message carries the SliceID information.

(10) The controller calculates the route and transmits the apparatus operation mechanism.

The controller performs path calculation based on the SliceID information, the FA topology and the residual slice resource information of the virtual member sublink end.X corresponding to the FA topology, and uses the SID of the virtual member sublink end.X to perform path arrangement.

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

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

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

Within each FA slice topology, traffic for secondary slice users is carried through SRv6Policy tunnels, the paths of which are computed by the controller or tunnel header node. Since only the SRv6Policy strict path can provide the slicing user with an exclusive slicing service with strict physical resource guarantee per hop end to end, the SRv6Policy tunnel is referred to as SRv6Policy strict path.

The controller is according to SLA requirements such as bandwidth, time delay that the second grade section user put forward, from "table 2: selecting a SliceID (assumed as x) with an unallocated state from a resource demand allocation table corresponding to the SliceID of the forwarding plane, updating information of a required bandwidth of the SliceID, and updating the state to be idle; and meanwhile, creating a VPN for the SRv6Policy, binding the SRv6Policy tunnel one by using a tunnel Policy of a binding mode, and calculating the SRv6Policy main and standby cadidatePath (CP for short) by taking SLA requirements (bandwidth, time delay and the like) of a user as path calculation constraints in a primary FA slice topology where a secondary slice user is located (for example, taking FA as a path calculation factor).

When calculating a path, the controller needs to calculate a primary and standby CP which meets the requirements of the secondary slice user SLA end to end by combining with the resource conditions of the virtual member sublinks end.x corresponding to the primary FA topology (if the controller has enough residual slice bandwidth resources, whether the time delay meets the user requirements, and the like), wherein each CP has only one segment, and each segment path is arranged by using the end.x SID of the Locator space corresponding to the FA slice; simultaneously update "table 2: the state of SliceID (x) in a resource demand allocation table corresponding to the SliceID of the forwarding plane is pre-occupied, and the SliceID (x) is issued to the head node forwarding equipment along with the main and standby CPs of BGP SRv6 Policy.

And after the SRv6Policy is successfully issued, the controller updates the real-time state of the SliceID (x) to be occupied.

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

Next, when a message is forwarded on a forwarding device, according to an indication of a slice flag set in a virtual member sublink end.x SID, a processing mechanism and a method for further determining a slice sublink physical resource on an output interface and forwarding the message through a corresponding sublink physical resource subinterface are described.

On a forwarding device, forwarding a message along a specified path according to an SRv6Policy path issued by a controller, after determining an interface according to an indication of a Q-flag set in an end.X SID of a virtual member sublink of the device, each device along the path knows the bandwidth resource requirement required by the slice user according to a SliceID carried in the forwarding message, allocates a Sub-Link Num capable of meeting the SliceID bandwidth requirement to the subliceID resource from a subliceresource Sub-Link Num in an idle state corresponding to the output interface, and the forwarding device searches a locally stored table 3 according to the Sub-Link Num: a sub-link physical resource allocation table "for determining a corresponding sub-link resource ID (e.g. ChannelID, etc.), and forwarding the message through the sub-interface (e.g. channelized sub-interface), thereby ensuring that the service traffic has an exclusive shared channelized sub-interface physical resource; and meanwhile, the state of the Sub-Link Num is updated to be occupied, and a local table 4 is updated: sliceID and Sub-Link Num correspondence table' and reports the information to the controller through Telemetry.

When guiding the slice user flow in the FA slice of FlexAlgo to SRv6Policy tunnel transmission, the controller updates one or the combination of the following information according to the information reported by the equipment: the corresponding relation between SliceID of the virtual member sublink and sublink resource Sub-Link Num, sublink resource Sub-Link Num state and virtual member sublink residual slice resource information.

The following describes a mechanism and a method for a controller to perform dynamic update and maintenance on information such as a correspondence between a SliceID of a virtual member sublink and sublink resource Sub-Link Num, a sublink resource Sub-Link Num state, and a virtual member sublink residual slice resource according to the information reported by the device.

After receiving the distribution information of the Sub-Link Num reported by the forwarding device through the telemetric, the controller stores the corresponding relationship and updates the remaining slice bandwidth resource information (such as total reserved bandwidth-distributed Sub-Link Num bandwidth) of each virtual member sublink.

And when the main CP paths and the standby CP paths of the slice users have faults, the BE escape path is taken, and the escape path occupies the resources of the non-slice users in the FA slice topology.

The following is an example.

(1) And (5) networking description.

The method comprises the steps that A, B, C, D, E, F, G and H devices are assumed in a network, an ISIS dynamic routing protocol is operated, all the devices are in the same ISIS domain, all the devices support an FA function, and Q-flag bits of FADF sub-sub-TLVs are announced to the outside.

And a BGP-LS connection is established between the SDN controller and the forwarding equipment.

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

(2) Slicing requirements.

Suppose that there are currently 3 industry slice requirements, the bandwidth requirements are 5G, 10G, and 15G, respectively, and the secondary user slice requirements in each industry are shown in the table.

(3) SRv6 address allocation.

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

The affinity attribute of each link in the network at least includes the affinity (color attribute) included in the FA slice route calculation constraint requirement, and is specifically set as follows:

link (bidirectional)	Affinity Properties
		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 each FA slice topology, and based on the basic configuration, 3 FA slice topologies as shown in fig. 13 may be formed on the SDN controller.

(4) And reserving FA first-level slice resources.

And reserving corresponding bandwidth resources for the corresponding virtual member sublink end.X SID of each port of each device in each FA slice topology according to the bandwidth requirement of the primary FA slice on the controller.

Taking a certain port of the device a as an example, the total bandwidth reserved by the virtual member sublink is shown in the following table, and so on for other devices.

(5) And distributing the number of sliceID of the transfer surface in the FA slice topology.

And allocating a certain number of sliceids to each FA slice on the controller, and sending the sliceids to the equipment, wherein the sliceids of forwarding surfaces reserved for the FA128 slice topology are 1-200 (namely, first SliceID =1, sliceidcount = 200), the sliceids reserved for the FA129 slice topology are 201-600 (namely, first SliceID id =201, sliceidcount = 400), and the sliceids reserved for the FA130 slice topology are 601-1200 (namely, first SliceID id =601, sliceidcount = 600).

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

(6) SliceID distribution of forwarding surface corresponding to secondary slice user

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

Table 5: sliceID corresponding resource demand distribution table of forwarding surface

And maintaining the dynamic update table on the controller, and issuing the updated state to the equipment for storage at any time.

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

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

The controller divides each physical Link corresponding to all the equipment in the primary FA slice topology into a plurality of mutually isolated sublinks according to the requirements of secondary slice users, each sublink has a bottom layer physical resource which is exclusively shared by the sublink, and the sublinks are identified through Sub-Link Num.

Configuring physical resources corresponding to Sub-Link Num of each port of the device, taking a device a and a Channel channelization Sub-interface resource as an example, allocating physical resources of a Sub-Link of a certain port on the device a as shown in the following table, and other devices are similar:

the Sub-Link Num pre-allocated on the device and the corresponding physical resource need to be more than the requirement of the actual secondary slice user by a certain proportion (for example, a certain amount of 100M \200M \500Mchannelized Sub-interface resources are respectively reserved, but the total amount cannot exceed the total bandwidth of the corresponding FA primary slice), so that when a new user comes, the Sub-interface of the bottom Link is already provided, and the service can be quickly opened.

(6) SRv6-Policy routing and message forwarding processes.

Taking the slice resource of the user 1 in the power industry as an example, 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 including the nodes A and E for the VPN, one-to-one binds an SRv6Policy tunnel by using a tunnel Policy of a binding mode, and enables HSB configuration for the SRv6 Policy.

The controller calculates a master-slave CP of SRv6Policy for which bandwidth resources from A to E meet 200M requirements in the FA130 topology.

Taking the node A as an example, the controller checks X3: 1:andX 3: 3:correspondingto the FA130 slice that the SliceID 601 bandwidth meets the requirement and is idle at present when the path is calculated; the controller operates each device in the topology of the FA130 according to the operation, and arranges the calculated segmentlist paths of the main and standby CPs by using the end.x SID of the Locator space corresponding to the FA slice.

The primary CP path from a to E thus calculated is as follows:

and (3) main CP: < X3:1: 100, X3:2: 100, X3:3: 100, X3:4: 100> and SliceID =601

Preparing a CP: < X3:5: 100, X3:6: 100, X3:7: 100, X3:8: 100> and SliceID =601

The controller updates the states of the SliceIDs 601 of all links in the FA130 topology to be pre-occupied, and issues the SliceIDs 601 to the head node A equipment along with the main CP path through a BGP SRv6Policy protocol.

Fig. 14 is a schematic diagram of a forwarding process of a SRv6Policy tunnel for a user 1 in the power industry, where when a message of the user 1 in the power industry reaches an ingress node a device, the forwarding process of the message is as shown in fig. 14.

The device A iterates the packet to an SRv6Policy tunnel (the tunnel Endpoint is E3:1: 100) of the slice FA130 according to the VPN routing Policy for carrying, so that the outer layer IPv6 packet header of the SRv6Policy tunnel is encapsulated, the segment of the SRH is (X3: 1:100, X3:2: 100, X3:3: 100, X3:4: 100, E3:1: B100) (wherein E3:1: B100 is the traffic corresponding to the VPN SID), and the current SL pointer points to X3:1: 100; and according to the SliceID corresponding to the tunnel, writing the value 601 of the SliceID into the corresponding position of the forwarding message (for example, the SliceID can be placed in a FlowLable, an HBH, a source address and the like, and indication is carried out through 1 flag bit of a trafficClass).

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

SliceID	Sub-Link Num
		601	0004

The device a updates the status of Sub-Link Num 0004 to occupied and reports the update information to the controller through telemeasure. The table is thickened to indicate that the vehicle is occupied "

The device determines the corresponding ChannelID 004 information Sub-interface according to the Sub-Link Num 0004, and forwards the message through the channelized Sub-interface 004, so as to ensure that the service flow of the user 1 has the unique channelized Sub-interface physical resource.

And all subsequent equipment in the path executes the same operations of table look-up forwarding, updating the Sub-Link Num state, reporting to the controller and the like until the message reaches the tunnel tail node E equipment. This ensures that the traffic of the power industry user 1 can obtain the physical resource guarantee of 200M channelized sub-interface on each link of the forwarding path.

Based on the same inventive concept, the embodiment of the present invention further provides an SDN controller and a computer-readable storage medium, and since the principle of solving the problem of these devices is similar to that of the transmission method, the implementation of these devices may refer to the implementation of the method, and repeated details are not described again.

When the technical scheme provided by the embodiment of the invention is implemented, the implementation can be carried out as follows.

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

the processor 1500, which is used to read the program in the memory 1520, executes the following processes:

the transceiver 1510 is used to receive and transmit data under the control of the processor 1500.

In an implementation, the method further comprises the following steps:

SliceID is SliceID in FA slices based on FlexAlgo, to which slice users belong;

In an implementation, the method further comprises the following steps:

and adding identifications in the IPv 6-based source routing technology CAPABILITY sub-type, the length, the SRv6Capabilities sub-TLV of the routing CAPABILITY type, the length, the value Router Capabilities TLV and the IPv 6-based source routing technology CAPABILITY type, the length, the value SRv6Capabilities TLV of the border gateway protocol link type BGP-LS to indicate the CAPABILITY of equipment supporting carrying the SliceID on a forwarding plane and carrying out slicing processing.

In an implementation, the method further comprises the following steps:

the following information is maintained and/or updated:

In an implementation, the method further comprises the following steps:

and configuring a mapping relation between the Color template and the SliceID of the forwarding surface, so that the tunnel head node equipment acquires the corresponding SliceID according to the Color attribute of the SRv6 Policy.

In an implementation, the method further comprises the following steps:

In implementation, when the slice user traffic is guided to the SRv6Policy tunnel for transmission, the SDN controller updates one or a combination of the following information according to the information reported by the device: the corresponding relation between SliceID of the virtual member sublink and sublink resource Sub-Link Num, sublink resource Sub-Link Num state and virtual member sublink residual slice resource information.

In an implementation, the method further comprises the following steps:

In implementation, when the value space of the sublink resource identifier is divided, the sublink resource corresponding to the Sub-Link Num with the high 4 bits as 1 is allocated to the FA slice for use, and the other Sub-Link Num value spaces are allocated to the user slice for use.

In an implementation, the method further comprises the following steps:

In fig. 15, among other things, the bus architecture may include any number of interconnected buses and bridges, with one or more processors represented by processor 1500 and various circuits of memory represented by memory 1520 being linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 1510 may be a number of elements including a transmitter and a receiver that provide 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.

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

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 slice users;

In an implementation, the method further comprises the following steps:

In an implementation, the binding module is further configured to establish a correspondence between the slice identifier SliceID and the SRv6Policy tunnel, where the correspondence is to allocate a slice identifier SliceID that can meet the resource requirement of a slice user to the SRv6Policy tunnel.

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

In an implementation, the binding module is further configured to carry the SliceID information of the forwarding plane in a BGP SRv6Policy message.

In implementation, the binding module is further configured to update one or a combination of the following information according to the information reported by the device when the slice user traffic is guided to the SRv6Policy tunnel for transmission: the corresponding relation between SliceID of the virtual member sublink and sublink resource Sub-Link Num, sublink resource Sub-Link Num state and virtual member sublink residual slice resource information.

In implementation, the dividing module is further configured to divide the value space of the sublink resource identifier to distinguish the sublink resource identifier used by the FA slice and the user slice.

For convenience of description, each part of the above-described apparatus is separately described as being functionally divided into various modules or units. Of course, the functionality of the various modules or units may be implemented in the same one or more pieces of software or hardware in practicing the invention.

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

a processor 1700, which reads the program in the memory 1720, executes the following processes:

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

In an implementation, the method further comprises the following steps:

In fig. 17, among other things, the bus architecture may include any number of interconnected buses and bridges, with one or more processors represented by processor 1700 and various circuits of memory represented by memory 1720 being linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 1710 may be a plurality of elements including 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.

In implementation, the relationship module is further configured to enable the tunnel head node device to obtain the SliceID from a BGP SRv6Policy message issued by the SDN controller, and write the SliceID into a position corresponding to the forwarding plane packet.

In implementation, the transmission module is further configured to, when the traffic of the slice user is guided to the SRv6Policy tunnel for transmission, allocate a sublink resource that can meet the requirements of the slicink resource from the sublink resource in the idle state corresponding to the physical output interface according to the slicink id carried in the slice user forwarding message to perform forwarding, and maintain the correspondence between the slicink and the sublink resource and the state of the sublink resource.

The embodiment of the invention also provides a computer readable storage medium, and the computer readable storage medium stores a computer program for executing the transmission method.

The specific implementation can be seen 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 the SRv6Capabilities sub-TLV of the Router Capabilities TLV and the SRv6Capabilities TLV of the BGP-LS, and adding a flag mark to indicate that the equipment supports the slice processing CAPABILITY of the forwarding plane.

The extended end.x SID sub-TLV structure adds a flag to indicate that it is an adjacent SID for a virtual member sublink, rather than an adjacent SID for a physical link.

Newly defined link slice information Sub-TLV and slice resource Sub-TLV structures are used to advertise link slice numbers and corresponding resource information.

Further, methods of end.xsid, reserved total bandwidth, number of sliceids, and resource information per SliceID of virtual member sublinks per FA slice on IGP flooding advertisement links are provided.

An end.X SID distribution and total resource reservation mechanism and a method of a virtual member sublink in an FA slice topology, and a distribution rule of the number of SliceIDs of a forwarding plane in the FA slice topology.

And the controller maintains the corresponding relation among FA slice ID, virtual member sublink end.X SID and total reserved resource thereof, and SliceID quantity, and maintains and updates information such as the requirement and state of each SliceID resource, the total residual slice resource of the virtual member sublink and the like.

And the BGP SRv6Policy structure is extended to carry the SliceID information of a forwarding plane.

Further, a method for acquiring the sliceID from the BGP SRv6policy message issued by the tunnel head node from the controller and writing the sliceID into the corresponding position of the forwarding plane message is provided.

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

And the operation mechanism and the method for value distribution, corresponding resource distribution and state maintenance of the secondary slice user forwarding plane SliceID.

The controller carries out path calculation based on SliceID information, FA topology and the residual slice resource condition of the corresponding virtual member sublink end.X, and uses the SID of the virtual member sublink end.X to carry out path arrangement.

When the message is forwarded on the forwarding equipment, according to the indication of the setting of the slice flag in the end.X SID of the virtual member sublink, the physical resource of the slice sublink is further determined on the output interface, and the message is forwarded through the corresponding sublink physical resource subinterface.

A method that the forwarding device allocates a sublink resource (such as MTN subinterface, VLAN enhancer interface, channelized subinterface resource, flexe subinterface, independent QoS queue, etc.) capable of meeting the SliceID resource requirement from the sublink resource in idle state corresponding to the physical output interface according to SliceID carried in the slice user forwarding message; a corresponding relation between SliceID and sub-link resources and a dynamic maintenance mechanism and a method for the state of the sub-link resources.

Furthermore, sub-Link Num is introduced to uniformly identify bottom layer physical Sub-Link resources, each Sub-Link has a bottom layer physical resource which is shared by the Sub-Link, such as an MTN Sub-interface, a VLAN enhancer interface, a channelized Sub-interface resource, a Flexe Sub-interface, an independent QoS queue and the like, and the corresponding relation between the Sub-Link Num and the Sub-Link resource IDs of various types is maintained, so that the bottom layer physical Sub-Link resources of various types are compatible.

Further, a mechanism and a method for synchronizing the correspondence between the SliceID and the Sub-Link Num and the occupation condition of the Sub-Link resource Sub-Link Num to the controller in real time through Telemetry by the forwarding device are provided.

Further, a mechanism and a method are provided for the controller to perform dynamic update and maintenance on the information such as the correspondence between the sliceID of the virtual member sublink and sublink Num, the sublink resource Sub-Link Num state, and the virtual member sublink residual slice resource according to the information reported by the device.

And by dividing the value space of the sublink resource identifiers, the sublink resource identifiers used by the first-level slice and the second-level slice are separated.

Further, sub-Link resources corresponding to Sub-Link Num with the high 4 bits of 1 are allocated to the FA primary slice for use, and the other Sub-Link Num value spaces are allocated to the secondary slice for use.

And in each FA slice topology, reserving residual bandwidth resources which are not allocated to the secondary user slice in the total bandwidth, sharing and using the residual bandwidth resources for non-slice users in the FA topology, and carrying the traffic of the non-slice users through SRv6 BE.

In implementation, the FA slices are FlexAlgo-based FA slices which are divided into corresponding numbers and have one-to-one correspondence for a network according to the number of industries or virtual operators;

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

The scheme can provide bottom layer physical resource guarantee for the slicing well, realizes hard slicing, and can solve the problems of soft isolation and complete physical resource sharing only through a tunnel compared with the conventional SR-TE and SR Policy technologies.

The single FA enhancement technology and the single SRv6Policy + forwarding plane slicing technology can only provide one-level slicing service, the scheme provides a dynamically adjustable sublink-level resource-guaranteed data carrying network two-level slicing service, and can meet the requirements of two-level slicing scenes of industry slicing and user slicing.

As will be appreciated by one skilled in the art, 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, 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 flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams 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 changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include such modifications and variations.

Claims

1. A method of transmission, comprising:

and establishing a one-to-one binding source routing technology strategy SRv6Policy tunnel based on IPv6 for the user according to the resource requirement of the slice user, and establishing a corresponding relation between the slice identification SliceID and the SRv6Policy tunnel.

2. The method of claim 1, further comprising:

SliceID is SliceID in FA slices based on FlexAlgo, to which slice users belong;

3. The method of claim 1, further comprising:

4. The method of claim 1, further comprising:

5. The method of claim 1, further comprising:

6. The method of claim 1, further comprising:

7. The method of claim 1, further comprising:

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

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

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

10. The method of claim 1, further comprising:

the SliceID information of the forwarding plane is carried in the BGPSRv 6Policy message.

11. The method of claim 1, further comprising:

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

13. The method of claim 1, wherein when the slice user traffic is directed to SRv6Policy tunneling, enabling a forwarding device to determine a slice sublink physical resource on an egress interface according to an indication of a slice flag setting in a virtual member sublink end.x SID when forwarding a message, and forwarding the message through a corresponding sublink physical resource subinterface.

14. The method of claim 13, wherein when slice user traffic is directed to SRv6Policy tunneling, the SDN controller updates one or a combination of the following information according to information reported by the device: the corresponding relation between SliceID of the virtual member sublink and sublink resources Sub-Link Num, the state of the sublink resources Sub-Link Num and the information of the residual slice resources of the virtual member sublink.

15. The method of claim 1, further comprising:

16. The method of claim 15, wherein when a value space of the sublink resource identifier is divided, a sublink resource corresponding to a Sub-Link Num with a high order of 4 being 1 is allocated to an FA slice for use, and the remaining Sub-Link Num value spaces are allocated to user slices for use.

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

18. The method according to any one of claims 2 to 17, wherein the FA slices are FlexAlgo-based FA slices divided into a corresponding number of one-to-one correspondence for the network according to the number of industries or virtual operators;

19. A method of transmission, comprising:

20. The method of claim 19, further comprising:

21. The method of claim 19, further comprising:

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

22. The method of claim 19, wherein when a forwarding device directs slice user traffic to SRv6Policy tunneling, according to a SliceID carried in a slice user forwarding message, a sublink resource capable of meeting a requirement of the SliceID resource is allocated from a sublink resource corresponding to an idle state of a physical egress interface for forwarding, and a correspondence between the SliceID and the sublink resource and a state of the sublink resource are maintained.

23. The method of claim 22, wherein when a forwarding device directs the slice user traffic to SRv6Policy tunneling, when a first slice packet arrives at the device, the device searches a local table according to a SliceID carried in the forwarding packet to obtain bandwidth resources required by the SliceID, finds a Sub-Link resource Sub-Link Num of an unoccupied bandwidth from the Sub-Link resource table of the local device, allocates the Sub-Link resource Sub-Link Num to the SliceID, forwards the slice user packet from a 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 the following information to the SDN controller through teleteleteleteleteleteleteleteleteleteletelemetry: the occupation condition of Sub-Link Num of the Sub-Link resource, the corresponding relation between SliceID and Sub-Link Num and the state of Sub-Link Num.

24. A network apparatus, comprising:

25. A network apparatus, comprising:

and the binding module is used for establishing a one-to-one binding of the source routing technology strategy SRv6Policy tunnel based on the IPv6 for the user according to the resource requirement of the slice user and establishing a corresponding relation between the slice identifier SliceID and the SRv6Policy tunnel.

26. A network apparatus, comprising:

27. A network apparatus, comprising:

28. 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 23.