WO2023016566A1

WO2023016566A1 - Resource allocation method and apparatus, and network node

Info

Publication number: WO2023016566A1
Application number: PCT/CN2022/112283
Authority: WO
Inventors: 姜文颖; 程伟强; 龚立艳
Original assignee: 中国移动通信有限公司研究院; 中国移动通信集团有限公司
Priority date: 2021-08-13
Filing date: 2022-08-12
Publication date: 2023-02-16

Abstract

Provided in the present application are a resource allocation method and apparatus, and a network node. The method comprises: a message sending node sending a message to an SRv6 policy path, wherein an IPv6 message header of the message comprises a slice identifier and a resource indication sign; and the resource indication sign is used for indicating, to a message receiving node on the SRv6 policy path, the dynamic allocation of a sub-link resource corresponding to the slice identifier.

Description

Resource allocation method, device and network node

Cross References to Related Applications

This application is based on the Chinese patent application with the application number 202110932008.1 and the application date on August 13, 2021 and the Chinese patent application with the application number 202210946390.6 and the application date on August 8, 2022, and requests the priority of the above-mentioned Chinese patent applications Right, the entire content of the above-mentioned Chinese patent application is hereby incorporated into this application as a reference.

technical field

The present application relates to the technical field of data transmission, and in particular to a resource allocation method, device and network node.

Background technique

At present, the data bearer network supports large-scale hard slicing schemes, mainly adopting the strategy of introducing slice identifiers (such as IDs) into Internet Protocol Version 6-Segment Routing (abbreviation: IPv6SR or SRv6) (English It can be expressed as Policy) on the forwarding plane, that is, the slice identifier is carried in the SRv6 packet header, and the forwarding device associates the slice identifier with the underlying physical link or sub-link resource, and combines the corresponding sub-link physical isolation technology, Such as channelized sub-interfaces, G.8312 (ITU International Telecommunication Union standard) interfaces, Quality of Service (QoS) queues, etc., to provide users with high-quality bearer network hard slicing services with independent resource guarantees.

The forwarding plane carrying slice identifiers can implement fine-grained slices at the sub-interface level. At the same time, because it does not need to expand the control plane protocol, it will not bring too much overhead to network devices, making it possible for the data bearer network to support large-scale slices.

At present, the allocation of underlying physical link resources or sub-link resources (that is, slice resources) corresponding to the slice identifier is mainly a static configuration method, that is, slice resources (physical slice resources) are allocated in advance for each slice identifier on all links in the entire network. link resources or sub-link resources), and establish a mapping relationship, so that when the device forwards the slice user's message, it can find the corresponding sub-link resource according to the slice identifier and forward it.

Since the path of the SRv6 policy forwarding plane of slice users is calculated by the controller in real time according to the requirements of the Service-Level Agreement (SLA), the current static allocation of slice resources requires Each slice identifies reserved resources. Therefore, resources are also reserved on the links that slice users do not pass through the SRv6 policy path, resulting in a great waste of network-wide resources.

Contents of the invention

To solve related technical problems, embodiments of the present application provide a resource allocation method, device, and network node.

An embodiment of the present application provides a resource allocation method, which is applied to a message sending node, and the method includes:

Send packets to the SRv6 policy path;

Wherein, the IPv6 packet header of the message includes a slice identifier and a resource indication flag, and the resource indication flag is used to indicate to the message receiving node on the SRv6 policy path the sublink resource corresponding to the slice identifier Dynamic allocation.

In the above solution, the message includes a bidirectional detection (Bidirectional Forwarding Detection, BFD) message.

In the above solution, the resource indication flag includes a discard flag and/or a resource allocation flag;

The discard flag is used to indicate whether to discard the message when the message receiving node cannot obtain sub-link resources according to the slice identifier;

The resource allocation flag is used to indicate whether the packet receiving node allocates the corresponding sub-link resource according to the slice ID when it cannot obtain the sub-link resource according to the slice ID.

In the above solution, when the discard flag is the first value, it means that the message is discarded when the sub-link resource cannot be obtained according to the slice identifier;

When the discarding flag is the second value, it indicates that the packet is forwarded along a preset default path when sub-link resources cannot be obtained according to the slice identifier.

In the above solution, when the resource allocation flag is the first value, it means that when the sub-link resource cannot be obtained according to the slice identifier, the corresponding sub-link resource is allocated;

When the resource allocation flag is the second value, it indicates that no sub-link resource is allocated when the sub-link resource cannot be obtained according to the slice identifier.

In the above scheme, the IPv6 header of the IPv6 packet includes a network slice identification option in the IPv6 hop-by-hop options header (Hop-By-hop options Header, HBH), new HBH or destination options header (Destination Options Header, DOH);

Wherein, the network slice identification option includes the resource indication flag.

In the above scheme, the resource indicator is recorded in the source address or flow label (Flowlabel) field of the IPv6 message header, and the resource indicator occupies the part of the source address or the Flowlabel field (English can express for bit).

In the above solution, the network slice identification option further includes: option type, option data field length and slice identification.

In the above solution, the resource indication flag includes a discard flag and a resource allocation flag, and the indication meanings when the discard flag and the resource allocation flag are different values include:

The discarding flag is a second value, and the resource allocation flag is a second value, which is used to indicate that when sub-link resources cannot be obtained according to the slice identifier, forward the message along a preset default path;

The discard flag is a second value, and the resource allocation flag is a first value, which is used to indicate that when sublink resources cannot be obtained according to the slice identifier, forward the message along a preset default path, and Allocating corresponding sub-link resources according to resource requirements corresponding to the slice identifier;

The discarding flag is a first value, and the resource allocation flag is a second value, which is used to indicate that the message is discarded when the sub-link resource cannot be obtained according to the slice identifier;

The discarding flag is a first value, and the resource allocation flag is a first value, which is used to indicate that when sublink resources cannot be obtained according to the slice identifier, the message is discarded, and according to the slice identifier, the corresponding resource requirements, allocate corresponding sub-link resources.

In the above solution, when the message sending node is the head node of the SRv6 policy path, the sending of the message to the SRv6 policy path includes:

Sending the first N messages on the SRv6 policy path; wherein, the resource indication flags in the first N messages are used to trigger each message receiving node on the SRv6 policy path to carry out subsections corresponding to the slice identifiers. Dynamic allocation of link resources;

Send the N+1th message to the Mth message on the SRv6 policy path; wherein, the resource indicator in the N+1th message to the Mth message is used to detect the SRv6 policy path Whether each message receiving node on the network has completed the dynamic allocation of sublink resources corresponding to the slice identifier; wherein, M is greater than N, and M and N are both positive integers;

Send the message after the Mth message to the SRv6 policy path; wherein, the resource indicator in the message after the Mth message is used to indicate each message receiving node, and the slice identifier cannot When sublink resources are obtained, the message is discarded.

In the above solution, the resource indication flag includes a discard flag and a resource allocation flag, and when the discard flag and the resource allocation flag are respectively the first value or the second value:

The resource indication flags in the first N packets are: the discard flag is a second value, and the resource allocation flag is a first value;

The resource indication flags in the N+1th message to the Mth message are: the discarding flag is the first value, and the resource allocation flag is the first value;

The resource indication flag in the packets after the Mth packet: the discard flag is a first value, and the resource allocation flag is a second value.

In the above scheme, the method also includes:

During the process of sending the N+1th packet and the packets after the N+1th packet to the SRv6 policy path, if the return packet of the packet is received, and the discard flag in the received return packet is the first value, and the resource allocation flag is the first value, it is determined that the Mth message has been sent, and the next sent message is the M+1th message.

In the above scheme, the method also includes:

During the process of sending the N+1th packet and the packets after the N+1th packet to the SRv6 policy path, if the return packet of the packet is received, and the discard flag in the received return packet is the first value, and the resource allocation flag is the first value, it is determined that each node of the SRv6 policy path has completed the allocation of sub-link resources.

The embodiment of the present application also provides a resource allocation method, which is applied to a message receiving node, and the method includes:

Receive packets on the SRv6 policy path;

Wherein, the IPv6 header of the message includes a slice identifier and a resource indication flag, and the resource indication flag is used to indicate to the message receiving node the dynamic allocation of sub-link resources corresponding to the slice identifier.

In the above solution, the message includes a BFD message.

In the above scheme, the IPv6HBH, new HBH or DOH of the IPv6 message header includes a network slice identification option;

In the above solution, the resource indication flag is recorded in the source address or Flowlabel field of the IPv6 packet header, and the resource indication flag occupies part of the indication bits of the source address or Flowlabel field.

In the above solution, the network slice identification option further includes: option type, option data field length, and the slice identification.

In the above scheme, the method also includes:

In the case that the sublink resource cannot be obtained according to the slice identifier, the message is processed according to the value indicated by the resource indication flag.

In the above solution, when the resource indication flag includes a discard flag and a resource allocation flag, the processing of the message is performed according to the value indicated by the resource indication flag, including:

When the discarding flag is a second value, and the resource allocation flag is a second value, forwarding the message along a preset default path;

When the discard flag is the second value and the resource allocation flag is the first value, forward the message along a preset default path, and allocate the corresponding sub-link according to the resource requirement corresponding to the slice identifier resource;

When the discarding flag is a first value and the resource allocation flag is a second value, discarding the message;

When the discard flag is the first value and the resource allocation flag is the first value, discard the message, and allocate corresponding sublink resources according to the resource requirement corresponding to the slice identifier.

The embodiment of the present application also provides a network node, the network node is a message sending node, including: a transceiver, wherein the transceiver is configured as:

Send packets to the SRv6 policy path;

The embodiment of the present application also provides a network node, the network node is a message receiving node, including: a transceiver, wherein the transceiver is configured as:

Receive packets on the SRv6 policy path;

The embodiment of the present application also provides a resource allocation device, which is applied to a message sending node, including:

A packet sending unit configured to send packets to the SRv6 policy path;

The embodiment of the present application also provides a resource allocation device, which is applied to a message receiving node, including:

A packet receiving unit configured to receive packets on the SRv6 policy path;

The embodiment of the present application also provides a network node, including: a processor, a memory, and a program stored on the memory and operable on the processor, and when the program is executed by the processor, the above message The steps of any method on the side of the sending node, or the steps of any method on the side of the above message receiving node.

The embodiment of the present application also provides a readable storage medium, where a program is stored on the readable storage medium, and when the program is executed by a processor, the steps of any method on the side of the message sending node are implemented, or the above message sending node is implemented. Steps of either method on the receiving node side.

The technical solutions provided by the embodiments of the present application have the following beneficial effects:

In the resource allocation method, device, and network node provided by the embodiments of the present application, the message of the SRv6 policy path includes a resource indication flag, which is used to trigger the dynamic resource allocation of the SRv6 policy path, so that on the SRv6 policy path, each message The receiving node realizes the dynamic allocation of sub-link resources corresponding to the slice ID according to the resource indication flag, and associates the allocated sub-link resources with the slice ID to ensure that subsequent slice services can be dynamically allocated along the sub-link resources according to the slice ID. Link resources are forwarded so as to have exclusive slice resources, so as to at least solve the problem of waste of resources caused by static allocation of slice resources when sending SRv6 packets in related technologies.

Description of drawings

FIG. 1 is a schematic flowchart of a resource allocation method according to an embodiment of the present application;

FIG. 2 is a schematic structural diagram of a network slice identification option for carrying a resource indication flag according to an embodiment of the present application;

FIG. 3 is a schematic structural diagram of a resource indication flag in an embodiment of the present application;

Fig. 4 is a schematic structural diagram of the application example system of the present application;

Fig. 5 is a schematic diagram of the strategy path of the application example;

FIG. 6 is a schematic flowchart of another resource allocation method according to an embodiment of the present application;

FIG. 7 is a schematic structural diagram of a message sending node in an embodiment of the present application;

FIG. 8 is a schematic structural diagram of a message receiving node according to an embodiment of the present application;

FIG. 9 is a schematic structural diagram of a resource allocation device according to an embodiment of the present application;

FIG. 10 is a schematic structural diagram of another resource allocation device according to an embodiment of the present application.

Detailed ways

In order to make the technical problems, technical solutions and advantages to be solved in this application clearer, the following will describe in detail with reference to the drawings and specific embodiments.

In a data bearer network that supports large-scale slicing, the SRv6 policy paths of slicing users are calculated in real time by the controller based on SLA requirements, and based on the current static allocation of slicing resources, each All slice identifiers reserve resources, so the links that the SRv6 policy path corresponding to the slice user does not pass also need to reserve resources, resulting in a great waste of resources in the entire network. To solve this technical problem, the embodiment of this application provides a The resource allocation method, in the message sent on the SRv6 policy path, includes the resource indication flag, through which the real-time dynamic allocation of slice physical resources on the forwarding plane can be realized, and the problem of huge waste of resources caused by the static allocation of slice resources can be solved .

The embodiment of the present application provides a resource allocation method, which is applied to a message sending node, as shown in FIG. 1, the method includes:

S110, sending a message to the SRv6 policy path;

Wherein, the IPv6 packet header of the message includes a slice identifier (such as ID, which can be specifically expressed as Slice ID) and a resource indication flag (which can be expressed as Flags in English), and the resource indication flag is used to send information to the SRv6 policy path. The message receiving node indicates the dynamic allocation of sub-link resources corresponding to the slice identifier.

In actual application, the sent message may include a BFD message, or may include a user's service message, or may include a newly defined message.

The slice identifier can also be called a network slice identifier (in English, it can be expressed as Network Slice Selector). The embodiment of the present application does not limit the name of the slice identifier, as long as its function is realized.

Using the resource allocation method described in this embodiment, the resource indication flag is used to indicate to the packet receiving node on the SRv6 policy path the dynamic allocation of sub-link resources corresponding to the slice identifier, so that on the SRv6 policy path, each A message receiving node implements dynamic allocation of sub-link resources corresponding to the slice ID according to the resource indication flag, and associates the allocated sub-link resources with the slice ID to ensure that subsequent slice services can be dynamically allocated according to the slice ID. The allocated sub-link resources are forwarded to have exclusive slice resources.

In this embodiment of the application, for step S110, the message sent on the SRv6 policy path may include a BFD message for detecting the connectivity of the SRv6 policy path, and the BFD message may be triggered from the head node of the SRv6 policy path.

In the embodiment of the present application, the specific implementation of step S110 may include: sending a BFD message to the SRv6 policy path, that is, the BFD connection through the slice user's SRv6 policy candidate path (Candidate Path, CP) (which may be referred to as the SRv6 policy path for short) The establishment process triggers the dynamic allocation of sub-link resources. Specifically, corresponding to the slice link resource requirements of the slice user, the software defined network (Software Defined Network, SDN) controller can calculate the segment list (segmentlist) path of the SRv6 policy primary CP and standby CP for the slice user, and use each link The End.X segment identifier (Segment ID, SID) of the road is used to arrange the path.

In actual application, according to the active CP or each standby CP of the SRv6 policy calculated by the SDN controller, the dynamic resource allocation of the SRv6 policy path can be triggered. On the active CP or each standby CP of the SRv6 policy, the head node (also called The head node (corresponding to the message sending node) periodically sends a message, and the message includes a slice identifier and a resource indication flag, so that the forwarding plane carries the slice identifier to indicate the resource information required by the message, and carries the resource indication flag , indicating that the slice identifies the dynamic allocation of sub-link resources.

In this embodiment of the present application, the resource indication flag may include a discard flag and/or a resource allocation flag;

In actual application, the discard flag may be expressed as D-flag, and the resource allocation flag may be expressed as A-flag.

In this embodiment of the present application, the sub-link resources may include underlying physical sub-link resources, such as including one or more of a G.mtn sub-interface, a channelization sub-interface, and a QoS queue.

In this embodiment of the present application, the resource allocation flag included in the resource indication flag in the message is used to indicate whether to trigger the allocation of the corresponding sub-link resource according to the slice identifier when the sub-link resource cannot be obtained according to the slice identifier; the resource indication flag The discarding flag included is used to indicate whether to discard the message when the sub-link resource cannot be obtained according to the slice identifier. In this way, through the resource allocation flag and the discarding flag, each packet receiving node on the SRv6 policy path can realize The real-time dynamic allocation of underlying physical sub-link resources on the outbound interface and the association of sub-link resources with slice identifiers ensure that subsequent slice service traffic can be forwarded along the dynamically allocated sub-link resources according to slice identifiers, thereby Make sure that the business corresponding to the slice ID has exclusive slice resources.

In the embodiment of the present application, when the discard flag is the first value, for example, 1, it may indicate that the message is discarded when the sub-link resource cannot be obtained according to the slice identifier;

When the discarding flag is the second value, for example, 0, it may indicate that the packet is forwarded along a preset default path when sub-link resources cannot be obtained according to the slice identifier.

In this embodiment of the application, when the resource allocation flag is the first value, such as 1, it may indicate that when the sub-link resource cannot be obtained according to the slice identifier, the corresponding sub-link resource is allocated;

When the resource allocation flag is the second value, such as 0, it may indicate that no sub-link resource is allocated when the sub-link resource cannot be obtained according to the slice identifier.

In the embodiment of this application, the network slice identification option (English can be expressed as Network Slice Selector Option) in the IPv6 message header of the message can carry the resource indication flag. In other words, the IPv6HBH, new HBH or DOH can include network slice identification options;

Wherein, the resource indication flag may be included in the network slice identification option.

In actual application, the IPv6HBH, new HBH or DOH of the IPv6 message header may include a network slice identification option, which means that the network slice identification option may be defined in the HBH, new HBH or DOH header in the IPv6 message header, so The network slice identifier option is used to encapsulate the slice identifier in the IPv6 data plane and carry a discard flag and/or a resource allocation flag, and the slice identifier is used to identify the slice to which the data packet belongs.

In actual application, the format of the network slice identification option can be as shown in Figure 2, and the network slice identification option can include option type (English can be expressed as Option Type), option data field length (English can be expressed as Opt Data Len ), the resource indication flag and the slice identifier.

Wherein, the network slice identification option includes the option type, option data field length, resource indication flag and slice identification representation (i.e. expression form) and their meanings are as follows:

Option type: can include an 8-bit identifier, and the specific value of the 8-bit identifier can be assigned by the Internet Assigned Numbers Authority (IANA); for example, among the 8-bit identifiers, the highest The first 2 bits can be set to 00, which is used to indicate that the message receiving node that cannot recognize the option type can skip the network slice identification option and continue to process the IPv6 header; the third bit in the highest order of the first 3 bits can be set to 0, indicating that the option data in the network slice identification option will not change during packet transmission.

Option data field length: can include an 8-bit identifier. At this time, the data length recorded in the option data field length is in eight digits. The specific value is used to indicate the length of the data carried after the option data field length in the network slice identification option. Data length. Exemplarily, when the specific value indicated by the field length is 6, the data length of the data carried after the indicated option data field length is 6 bytes.

Network slice identifier: an identifier (such as ID) used to indicate the network slice to which the data packet belongs, that is, the slice identifier in this application.

Resource indication flag: may include a 16-bit identifier, as shown in FIG. 3 . Exemplarily, the first bit identifier in the resource indication flag may be a discarding flag bit, which is used to record the discarding flag; when the discarding flag is set to 1, it may indicate that when sub-link resources cannot be obtained according to the slice flag, Discarding the message; when the discarding flag is set to 0, it may indicate that the message is forwarded along a preset default path when sub-link resources cannot be obtained according to the slice identifier. The second identifier in the resource indication flag can be a resource allocation flag bit, which is used to record the resource allocation flag; when the resource allocation flag is set to 1, it can indicate that when the sub-link resource cannot be obtained according to the slice identifier, the allocation corresponding When the resource allocation flag is set to 0, it may indicate that no sub-link resource is allocated when the sub-link resource cannot be obtained according to the slice identifier. As shown in FIG. 3 , the identifiers other than the first and second digits in the resource indication flag can be represented as R, which is used to indicate that the identifier is not used and can be used in the future. Exemplarily, when the message is transmitted, the value of the identifier corresponding to the R bit may be recorded as 0, which is used to indicate that the value corresponding to the identifier is negligible.

In the embodiment of the present application, the source address or the Flowlabel field of the IPv6 message header of the message may carry the resource indicator. In other words, the resource indicator is recorded in the source address or the Flowlabel field of the IPv6 message header, so The resource indication flag occupies part of the indication bits of the source address or Flowlabel field.

Specifically, when a resource indication flag is recorded in the source address or Flowlabel field of the IPv6 packet header, and the resource indication flag includes a resource allocation flag and a discard flag, the source address or the two indication bits in the Flowlabel field can be used for Carries resource allocation flags and discard flags.

In this embodiment of the present application, the resource indication flag may include a discard flag and a resource allocation flag, and the indication meanings of the discard flag and the resource allocation flag when they are different values may include:

When the discarding flag is a second value (for example, 0), and the resource allocation flag is a second value (for example, 0), the resource indication flag is used to indicate that the sublink cannot be obtained according to the slice identifier resources, forwarding the message along the preset default path;

When the discarding flag is a second value (for example, 0), and the resource allocation flag is a first value (for example, 1), the resource indication flag is used to indicate that the sublink cannot be obtained according to the slice identifier For resources, forward the message along a preset default path, and allocate corresponding sub-link resources according to the resource requirements corresponding to the slice identifier;

When the discarding flag is a first value (for example, 1), and the resource allocation flag is a second value (for example, 0), the resource indication flag is used to indicate that the sublink cannot be obtained according to the slice identifier resources, discard the message;

When the discarding flag is the first value (eg, 1), and the resource allocation flag is the first value (eg, 1), the resource indication flag is used to indicate that the sublink cannot be obtained according to the slice identifier resources, discard the packet, and allocate corresponding sub-link resources according to the resource requirement corresponding to the slice identifier.

In actual application, for the BFD packet sent by the BFD establishment process of the SRv6 policy CP of the slice user, when each packet receiving node on the SRv6 policy path receives the BFD packet including the resource indication flag, it can The value indicated by the flag is used to process the BFD message. Specifically, the packet receiving node may process the BFD packet according to the indication meaning of the resource indication flag when the discarding flag and the resource allocation flag are respectively different values.

In the embodiment of the present application, when the message sending node is the head node of the SRv6 policy path, the sending the message to the SRv6 policy path may include:

Wherein, when the resource indication flag includes a discard flag and a resource allocation flag, and the discard flag and the resource allocation flag are respectively the first value or the second value, the resource indication flags in the first N packets , the discarding flag is the second value, and the resource allocation flag is the first value; the first value can be 1, and the second value can be 0, then in the first N messages, the flag bit of D-Flag is 0, the flag bit of A-Flag is 1; in this way, the flag bit of D-Flag is 0, and the flag bit of A-Flag is 1, which can make each message receiving node receiving the message according to D-Flag and A -Flag, when the sub-link resource cannot be obtained according to the slice identifier, report the information to the control plane, and simultaneously forward the message from the physical interface corresponding to the outgoing interface or the non-slicing shared sub-link resource of the outgoing interface (that is, The message is forwarded through the sub-link corresponding to the slice identifier); the control plane can send the data plane to create or occupy the physical sub-link interface resource corresponding to the resource according to the resource requirement corresponding to the slice identifier (that is, allocate the corresponding sub-link resources); in this embodiment of the application, the value of N can be determined through pre-configuration, for example, it is an integer greater than or equal to 1.

In this embodiment of the application, through the first N packets sent, the packets can trigger the dynamic resource allocation on each node along the SRv6 policy path, and the allocated sub-link resources are consistent with the slice identifier in the packet Associated.

In this embodiment of the application, after sending the first N messages, the N+1th message to the Mth message can be sent to the SRv6 policy path; wherein, the N+1th message to the Mth message The resource indication flag in this document is used to detect whether each message receiving node on the SRv6 policy path has completed the dynamic allocation of sub-link resources corresponding to the slice identifier; wherein, M is greater than N, and M and N are all positive integers;

Wherein, among the resource indication flags in the N+1th message to the Mth message, the discarding flag is the first value, the resource allocation flag is the first value, and the first value may be 1, Then in the N+1th message to the Mth message, the flag bit of D-Flag is 1, and the flag bit of A-Flag is 1; thus, the flag bit of D-Flag is 1, and the flag bit of A-Flag is 1. The flag bit is 1, so that each message receiving node receiving the message reports the information to the control plane when the sub-link resource cannot be obtained according to the slice identifier according to the D-Flag and A-Flag, and discards the message at the same time ; The control plane may send the data plane to create or occupy the physical sub-link interface resources of the corresponding bandwidth according to the resource requirements corresponding to the slice identifier (that is, allocate the corresponding sub-link resources).

In the embodiment of this application, during the process of sending the N+1th message and the messages after the N+1th message to the SRv6 policy path, if the return message of the message is received, and the received return If the discarding flag in the message is the first value, and the resource allocation flag is the first value, it is determined that the Mth message has been sent, and the next sent message is the M+1th message.

In the embodiment of this application, during the process of sending the N+1th message and the messages after the N+1th message to the SRv6 policy path, if the return message of the message is received, and the received return If the discard flag in the message is the first value, and the resource allocation flag is the first value, it is determined that each node of the SRv6 policy path has completed the allocation of sub-link resources (it can be understood as determining the SRv6 policy path Each node completes the dynamic allocation and association of sub-link resources corresponding to the slice identifier).

Specifically, in practical applications, when transmitting BFD packets on the SRv6 policy path, each packet receiving node can obtain sublink resources according to the slice identifier in the BFD packet, and then according to the slice identifier in the corresponding Forward the BFD message on the resource; when the sub-link resource cannot be obtained, report the information to the control plane and discard the message at the same time, so that the control plane allocates the corresponding sub-link according to the resource requirement corresponding to the slice identifier resource. In this way, during the process of sending the N+1th BFD packet to the Mth BFD packet until the return packet of the BFD packet is received, if the discard flag in the return packet of the received BFD packet is The first value, and the resource allocation flag is the first value, it can be determined that the detection of the SRv6 policy path is completed, each node of the SRv6 policy path has completed the dynamic allocation and association of the sub-link resources corresponding to the slice identifier, and the BFD state is connected (English can be expressed as UP), so as to further determine that the Mth BFD packet has been sent, the next BFD packet to be sent is the M+1th BFD packet, and change the value indicated by the resource indication flag.

In the embodiment of the present application, according to the return message of the Mth message, it is confirmed that each message receiving node on the SRv6 policy path has completed the dynamic allocation of sub-link resources corresponding to the slice identifier Next, the message after the Mth message can be sent to the SRv6 policy path; wherein, the resource indicator in the message after the Mth message is used to indicate each message receiving node, according to the When the sublink resource cannot be obtained by the slice identifier, the message is discarded.

Wherein, among the resource indication flags in the packets after the Mth packet, the discard flag is a first value, and the resource allocation flag is a second value. The first value can be 1, and the second value can be 0, then in the message after the Mth message, the flag bit of D-Flag is 1, and the flag bit of A-Flag is 0; thus, through D-Flag The flag bit of A-Flag is 1, and the flag bit of A-Flag is 0, so that each message receiving node receiving the message can discard the message according to the D-Flag and A-Flag.

In the embodiment of this application, for BFD packets, after the BFD session (session) state corresponding to the slice policy path is connected, the periodic detection BFD packets can be sent. If the device data plane cannot find the physical If the sublink interface is used, the BFD packet can be discarded.

It should be noted that, in the embodiment of the present application, the BFD message may be at least one of static BFD, dynamic BFD, and SBFD, so as to detect the continuity of the SRv6 policy CP.

In this embodiment of the application, the specific methods for triggering the dynamic allocation and association of resources of the SRv6 policy CP by using the BFD message sent during the BFD establishment process of the SRv6 policy CP of the slice user may include:

When establishing a BFD session for the SRv6 policy CP, the head node of the SRv6 policy path clears the D-flag in the resource indication flag (such as carried in the HBH header) in the first N BFD packets sent (N value is configurable) mark (that is, set the D-flag to 0), and set the A-flag mark (that is, set the A-flag to 1); through this indication method, the resource indication flag in the first N BFD messages triggers all Each message receiving node on the SRv6 policy path dynamically allocates the sub-link resource corresponding to the slice identifier;

The head node sets the D-flag (that is, D-flag is set to 1) and A-flag (that is, A- flag is set to 1); through this indication method, the BFD message sent after the Nth BFD message is used to detect whether each message receiving node on the SRv6 policy path has completed the sub-link resource corresponding to the slice identifier Dynamic allocation until the head node receives the return message of the BFD message whose D-flag mark and A-flag mark are 1 respectively;

Based on this, when the return packet of the BFD packet received by the head node, if the D-flag of the resource indication flag is 1 and the A-flag is 1 in the BFD packet of the received return packet, then the SRv6 Each node of the policy path has completed the dynamic allocation and association of sub-link resources corresponding to the slice identifier, and the BFD state is connected; at the same time, the A-flag in the HBH header is cleared (that is, the A-flag is set to 0); And send a subsequent periodic detection BFD message; wherein, in the subsequent periodic detection BFD message, the resource indication flag in the BFD message is used to indicate each message receiving node, when the slice identifier cannot obtain When sub-link resources are used, the BFD message is discarded.

In actual application, when the BFD session state corresponding to the SRv6 policy CP of the slice is connected, the periodic detection BFD message sent can be set by setting the D-flag flag and clearing the A-flag flag to indicate when the data plane forwards BFD When the packet cannot find the physical sublink interface corresponding to the slice identifier on the outbound interface, the BFD packet is discarded;

In addition, the state of the SRv6 policy can only be connected after the BFD session state corresponding to the CP of the slice SRv6 policy is connected, so that services can be diverted to the SRv6 policy.

On the SRv6 policy path, when the resource indication flag is used for indication, for each message receiving node receiving the message, when the data plane finds the sub-link resource corresponding to the slice identifier indicated by the message on the outbound interface, it will pass The sub-link resource corresponding to the slice identifier forwards the message, and when the data plane cannot find the sub-link resource corresponding to the slice identifier on the outbound interface, according to the D-flag and A in the resource indicator of the message -flag mark bit, perform the following different actions:

The value of the D-flag is 0, and the value of the A-flag is also 0: the packet is forwarded from the physical interface corresponding to the outbound interface or the non-slice shared sublink resource of the outbound interface (that is, through the default The sub-link forwards the BFD message);

The value of the D-flag mark is 0, and the value of the A-flag mark is 1: report the information to the control plane, and at the same time forward the message from the physical interface corresponding to the outgoing interface or the non-slicing shared sub-link resource of the outgoing interface (that is, , forward the BFD message through the default sub-link); the control plane sends the data plane to create or occupy the physical sub-link interface resources of the corresponding bandwidth according to the resource requirements corresponding to the slice identifier (that is, allocate the corresponding sub-link road resources);

The value of the D-flag is 1, and the value of the A-flag is 0: the packet is discarded;

The value of the D-flag is 1, and the value of the A-flag is 1: report the information to the control plane and discard the message at the same time; the control plane sends the data plane to create or occupy the corresponding bandwidth according to the resource requirements corresponding to the slice identifier Physical sub-link interface resources (that is, allocation of corresponding sub-link resources).

The specific implementation process of the resource allocation method described in the embodiment of the present application will be described below in combination with application examples.

As shown in Figure 4, this application example provides a network architecture for the resource allocation method, which may include node devices A, B, C, D, E, F, G, and H, and these eight node devices run ISIS Dynamic routing protocol, and all in the same intermediate system to intermediate system (ISIS) domain, all devices support slicing capabilities, in addition, a Border Gateway Protocol (Border Gateway Protocol) is established between the SDN controller and the forwarding device , BGP)-Link-State (Link-State, LS) connection.

Among them, the allocation of End SID and End.X SID of each device in the network architecture is shown in Figure 5.

Based on this network architecture, it is assumed that slice user 1 in the current network needs an exclusive slice link resource with a bandwidth of 100 megabits per second (Mbps) from node A to node E.

Wherein, the SDN controller allocates slice identification resources for slice user 1 according to the slice requirement of slice user 1. For example, if the allocated slice identification is 1, and the corresponding resource information is 100M bandwidth, then the allocated slice identification and slice user The relationship between them is shown in Table 1 below:

Table 1

In the case of allocating the slice identifier resource, the SDN controller synchronizes the slice identifier resource to each node in the network.

On the basis of the above-mentioned slice identification resources allocated, the controller or head node calculates a segmentlist path of the SRv6 strategy primary CP and standby CP with bandwidth resources from A to E meeting the 100M requirement according to the requirements of slice user 1, and uses each The End.X SID of the link is used to arrange the path. Among them, End.X represents the node type of each node, and End.X SID represents the link type of the link between each node.

The calculated active CP and standby CP can be expressed as:

Main CP: <X3:1::100, X3:2::100, X3:3::100, X3:4::100>;

Backup CP: <X3:5::100, X3:6::100, X3:7::100, X3:8::100>.

On the basis of establishing the active CP and the standby CP, associate the slice identifier marked as "1" with the SRv6 policy path (including the active CP and the standby CP).

When the SDN controller calculates the path, the SDN controller sends the above path to the head node A through the BGP SRv6 policy.

According to the active CP and standby CP calculated for slice user 1, the BFD packets sent during the corresponding BFD connection establishment process are used to trigger the dynamic allocation and association of resources on the CP in the SRv6 policy. The sub-interface link resources on each node device are The QoS queue is taken as an example. Along the SRv6 policy path (including the active CP and the standby CP) corresponding to the above-mentioned slice user 1, the dynamic allocation process of the sub-link resource corresponding to the slice identifier is as follows:

After the head node A of the SRv6 policy path receives the BGP SRv6 policy path (including the active CP and standby CP) and the slice ID SliceID1 issued by the controller, according to the BFD configuration corresponding to the SRv6 CP and standby CP) enable BFD;

Taking the establishment of the BFD queue session of the main CP as an example, the head node A sets the D-flag carried in the forwarding plane message to 0 and the A-flag to 1 in the first N BFD messages sent along the main CP;

The BFD message is forwarded along the main CP<X3:1::100, X3:2::100, X3:3::100, X3:4::100>, and the head node A finds out Port 0/0/1, on the outbound port 0/0/1, according to the SliceID1 carried in the packet header of the forwarding plane, if the corresponding QoS queue cannot be found on the data plane, according to D-flag is 0, A- flag is 1, report information to the control plane, and at the same time forward the BFD message from the physical interface corresponding to the outbound interface or the non-slice shared sub-link resource of the outbound interface; SliceID1 knows that the resource requirement is 100M bandwidth, so it creates a QoS queue with 100M bandwidth for it on the delivery data plane, associates it with SliceID1, and saves the corresponding relationship locally;

The BFD message is forwarded to devices B, C, and D along the main CP, so that each node A, B, C, and D on the main CP, according to the indication that D-flag is 0 and A-flag is 1 in the BFD message , start to allocate a QoS queue with 100M bandwidth for SliceID1 on the corresponding outbound interface;

Head node A will send The D-flag carried in the forwarding plane message is set to 1, and the A-flag is set to 1, which is used to detect whether each node on the main CP has completed the dynamic allocation of sub-link resources corresponding to SliceID1;

If the 100M bandwidth QoS queue resources corresponding to SliceID1 on the outgoing interface of devices A, B, C, and D along the route on the active CP are allocated successfully, the BFD packets will be associated with SliceID1 on the corresponding outgoing interface on devices A, B, C, and D. The QoS queue is forwarded;

If the resource allocation and association of 100M bandwidth QoS queue resources on the outbound interfaces of devices A, B, C, and D along the route has not been completed, and the QoS queue associated with SliceID1 cannot be found on the data plane, then D-flag is 1 and A-flag is 1. The device sends information to the control plane and discards the BFD packet at the same time; the control plane of the device learns that the resource requirement is 100M bandwidth according to SliceID1, so it sends the data plane to create a QoS queue with 100M bandwidth for it, and associates it with SliceID1. Save the corresponding relationship;

In the above process, the BFD state on the SRv6 policy CP remains disconnected (English can be expressed as Down) state;

When the head node A of the SRv6 policy path receives the return packet of the BFD packet whose D-flag is 1 and A-flag is 1, it indicates that the QoS queue corresponding to SliceID1 corresponding to 100M bandwidth has been completed on the outbound interfaces of all nodes along the path of the main CP. After resource allocation and association, the BFD state is connected; at the same time, the A-flag (A-flag=0) carried in the forwarding plane message is cleared, and subsequent periodic detection BFD messages are continuously sent.

Similarly, on the standby CP of the calculated SRv6 policy path, the connection process of the BFD queue is the same as above (simultaneously with the establishment process of the BFD session of the active CP), and will not be described in detail here.

Based on the above process, when the states of the BFD sessions of the active CP and the standby CP are both connected, the state of the SRv6 policy is connected, and the service traffic of slice user 1 is introduced into the SRv6 policy to bear, thus ensuring that the traffic of slice user 1 is Each link of the SRv6 policy forwarding path can obtain the exclusive physical resource guarantee of 100M QoS queue.

It can be seen from the above description that the resource allocation method provided by the embodiment of the present application uses the resource indication flag to indicate to the message receiving node on the SRv6 policy path the dynamic allocation of sub-link resources corresponding to the slice identifier, so as to realize the dynamic allocation of sub-link resources on the bearer network SRv6 policy path. The real-time dynamic allocation and association of the physical resources required by slices can solve the problem of great waste of resources caused by the static slice resource allocation scheme, which is not suitable for large-scale deployment on the live network.

Correspondingly, the embodiment of the present application also provides a resource allocation method, which is applied to a message receiving node, as shown in FIG. 6, the method includes:

S610, receiving a message on the SRv6 policy path;

Wherein, the received message may include a BFD message, or may include a service message of a user, or may include a newly defined message.

In the resource allocation method provided by the embodiment of the present application, in the message, the resource indication flag is used to indicate the dynamic allocation of sub-link resources corresponding to the slice identifier, so that on the SRv6 policy path, each message receiving node The indication flag realizes the dynamic allocation of sub-link resources corresponding to the slice ID, and associates the allocated sub-link resources with the slice ID, so as to ensure that subsequent slice services can be forwarded along the dynamically allocated sub-link resources according to the slice ID , to be able to have exclusive slice resources.

In this embodiment of the present application, when the discard flag is the first value, it may indicate that the message is discarded when the sub-link resource cannot be obtained according to the slice identifier;

When the discarding flag is the second value, it may indicate that the packet is forwarded along a preset default path when sub-link resources cannot be obtained according to the slice identifier.

In the embodiment of the present application, when the resource allocation flag is the first value, it may indicate that when sub-link resources cannot be obtained according to the slice identifier, corresponding sub-link resources are allocated;

When the resource allocation flag is the second value, it may indicate that no sub-link resource is allocated when the sub-link resource cannot be obtained according to the slice identifier.

In the embodiment of the present application, the IPv6 HBH, new HBH or DOH of the IPv6 packet header may include a network slice identification option;

In the embodiment of the present application, the source address or Flowlabel field of the IPv6 packet header may record the resource indication flag, and the resource indication flag may occupy part of the indication bits of the source address or Flowlabel field.

In this embodiment of the present application, the network slice identification option may further include: option type, option data field length, and the slice identification.

In the embodiment of the present application, the method may also include:

In this embodiment of the present application, when the resource indication flag includes a discard flag and a resource allocation flag, the processing of the message according to the value indicated by the resource indication flag may include:

When the resource allocation method provided by the embodiment of the present application is applied to the message receiving node, the indication mode of the resource indication flag, the specific indication content, and the real-time dynamic allocation and association of sub-link resources corresponding to the slice identifier according to the resource indication flag For the specific way, you can refer to the detailed description of the above method applied to the message sending node, which will not be described here.

The embodiment of the present application also provides a network node. The network node is a message sending node. As shown in FIG. 7, the message sending node 700 includes: a transceiver 710, wherein the transceiver 710 is configured as:

Send packets to the SRv6 policy path;

In this embodiment of the present application, the message may include a BFD message, or may include a service message of a user, or may include a newly defined message.

In this embodiment of the present application, the resource indication flag includes a discard flag and/or a resource allocation flag;

In the embodiment of the present application, when the discard flag is the first value, it means that the message is discarded when the sub-link resource cannot be obtained according to the slice identifier;

In the embodiment of the present application, when the resource allocation flag is the first value, it means that when the sub-link resource cannot be obtained according to the slice identifier, the corresponding sub-link resource is allocated;

In the embodiment of the present application, the IPv6HBH, new HBH or DOH of the IPv6 message header includes a network slice identification option;

In this embodiment of the present application, the resource indication flag is recorded in the source address or Flowlabel field of the IPv6 packet header, and the resource indication flag occupies part of the indication bits of the source address or Flowlabel field.

In this embodiment of the present application, the network slice identification option further includes: option type, option data field length, and the slice identification.

In the embodiment of the present application, the resource indication flag includes a discard flag and a resource allocation flag;

When the discarding flag is the second value, and the resource allocation flag is the second value, the resource indication flag is used to indicate that when sub-link resources cannot be obtained according to the slice identifier, forwarding along the preset default path said message;

When the discarding flag is the second value and the resource allocation flag is the first value, the resource indication flag is used to indicate that when sub-link resources cannot be obtained according to the slice identifier, forwarding along the preset default path The message, and according to the resource requirements corresponding to the slice identifier, allocate corresponding sub-link resources;

When the discarding flag is the first value, and the resource allocation flag is the second value, the resource indication flag is used to indicate that the packet is discarded when sub-link resources cannot be obtained according to the slice identifier;

When the discard flag is the first value, and the resource allocation flag is the first value, the resource indication flag is used to indicate that the packet is discarded when the sub-link resource cannot be obtained according to the slice identifier, and According to the resource requirements corresponding to the slice identifiers, corresponding sub-link resources are allocated.

In the embodiment of the present application, the transceiver 710 is further configured as:

In this embodiment of the present application, the resource indication flag includes a discard flag and a resource allocation flag, and when the discard flag and the resource allocation flag are respectively the first value or the second value:

The embodiment of the present application also provides a network node. The network node is a message receiving node. As shown in FIG. 8, the message receiving node 800 includes: a transceiver 810, wherein the transceiver 810 is configured as:

Receive packets on the SRv6 policy path;

In this embodiment of the application, the message may include a BFD message, or may include a user's service message, or may include a newly defined message.

In the embodiment of the present application, the transceiver 810 is further configured as:

In this embodiment of the present application, when the resource indication flag includes a discard flag and a resource allocation flag, the transceiver 810 is further configured to:

When the discard flag is the second value and the resource allocation flag is the first value, forward the packet along the preset default path, and report information to the control plane, so that the control plane identifies the Resource requirements, allocate corresponding sub-link resources;

When the discard flag is the first value and the resource allocation flag is the first value, discard the message, and report information to the control plane, so that the control plane allocates the corresponding resource requirements according to the resource requirements corresponding to the slice identifier sublink resource.

The embodiment of the present application also provides a resource allocation device, which is applied to a message sending node. As shown in FIG. 9, the message sending node 900 includes:

A message sending unit 910, configured to send a message to the SRv6 policy path;

In the embodiment of the present application, when the message sending node is the head node of the SRv6 policy path, the message sending unit 910 is further configured as:

In the embodiment of the present application, the message sending unit 910 is further configured as:

In practical applications, the packet sending unit 910 may be implemented by a transceiver in the packet sending node.

The embodiment of the present application also provides a resource allocation device, which is applied to a message receiving node. As shown in FIG. 10, the message receiving node 1000 includes:

A packet receiving unit 1010 configured to receive packets on the SRv6 policy path;

In the embodiment of the present application, the message receiving unit 1010 is further configured as:

In this embodiment of the present application, when the resource indication flag includes a discard flag and a resource allocation flag, the message receiving unit 1010 is further configured to:

In practical applications, the message receiving unit 1010 may be implemented by a transceiver in a message receiving node.

The embodiment of the present application also provides a network node, including: a processor, a memory, and a program stored on the memory and operable on the processor. When the program is executed by the processor, the aforementioned message The steps described in the method on the side of the sending node, or the steps described in the method on the side of the message receiving node are implemented.

Wherein, the network node may include the above-mentioned message sending node or a message receiving node. On the message sending node and the message receiving node, when the program is executed by the processor, the specific implementation process of the foregoing resource allocation method embodiment is realized. Reference may be made to the above detailed description, and no further description is given here.

In addition, the specific embodiment of the present application also provides a readable storage medium on which a program is stored, and when the program is executed by a processor, the steps described in the aforementioned message sending node side method are implemented, or the aforementioned message receiving node side method is implemented. the steps.

Specifically, the computer-readable storage medium is applied to the above-mentioned message sending node or message receiving node. When it is applied to the message sending node or message receiving node, the execution steps in the corresponding resource allocation method are detailed in Method Implementation example, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed methods and devices may be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or May be integrated into another system, or some features may be ignored, or not implemented. In another point, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, each unit may be physically included separately, or two or more units may be integrated into one unit. The above-mentioned integrated units can be implemented in the form of hardware, or in the form of hardware plus software functional units.

The above-mentioned integrated units implemented in the form of software functional units may be stored in a computer-readable storage medium. The above-mentioned software functional units are stored in a storage medium, and include several instructions to enable a computer device (which may be a personal computer, server, or network device, etc.) to execute some steps of the sending and receiving methods described in various embodiments of the present application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory, referred to as ROM), random access memory (Random Access Memory, referred to as RAM), magnetic disk or optical disc, etc., which can store program codes. medium.

What have been described above are some embodiments of the present application, and it should be pointed out that those skilled in the art can make some improvements and modifications without departing from the principles described in the application, and these improvements and modifications should also be regarded as For the scope of protection of this application.

Claims

A resource allocation method applied to a message sending node, the method comprising:

Send packets to the SRv6 policy path;

Wherein, the IPv6 packet header of the message includes a slice identifier and a resource indication flag, and the resource indication flag is used to indicate to the message receiving node on the SRv6 policy path the sublink resource corresponding to the slice identifier Dynamic allocation.
The resource allocation method according to claim 1, wherein the message includes a bidirectional detection (BFD) message.
The resource allocation method according to claim 1, wherein the resource indication flag comprises a discard flag and/or a resource allocation flag;

The discard flag is used to indicate whether to discard the message when the message receiving node cannot obtain sub-link resources according to the slice identifier;

The resource allocation flag is used to indicate whether the packet receiving node allocates the corresponding sub-link resource according to the slice ID when it cannot obtain the sub-link resource according to the slice ID.
The resource allocation method according to claim 3, wherein, when the discard flag is a first value, it means that the message is discarded when sub-link resources cannot be obtained according to the slice identifier;

When the discarding flag is the second value, it indicates that the packet is forwarded along a preset default path when sub-link resources cannot be obtained according to the slice identifier.
The resource allocation method according to claim 3, wherein when the resource allocation flag is a first value, it indicates that when sub-link resources cannot be obtained according to the slice identifier, corresponding sub-link resources are allocated;

When the resource allocation flag is the second value, it indicates that no sub-link resource is allocated when the sub-link resource cannot be obtained according to the slice identifier.
The resource allocation method according to claim 1, wherein the IPv6 hop-by-hop option header HBH, new HBH or destination option header DOH of the IPv6 message header includes a network slice identification option;

Wherein, the network slice identification option includes the resource indication flag.
The resource allocation method according to claim 1, wherein the resource indication flag is recorded in the source address or flow label field of the IPv6 message header, and the resource indication flag occupies a portion of the source address or flow label field Partial indicator.
The resource allocation method according to claim 6, wherein the network slice identification option further includes: option type, option data field length and the slice identification.
The resource allocation method according to claim 5, wherein the resource indication flag includes a discard flag and a resource allocation flag;

When the discarding flag is the second value, and the resource allocation flag is the second value, the resource indication flag is used to indicate that when sub-link resources cannot be obtained according to the slice identifier, forwarding along the preset default path said message;

When the discarding flag is the second value and the resource allocation flag is the first value, the resource indication flag is used to indicate that when sub-link resources cannot be obtained according to the slice identifier, forwarding along the preset default path The message, and according to the resource requirements corresponding to the slice identifier, allocate corresponding sub-link resources;

When the discarding flag is the first value, and the resource allocation flag is the second value, the resource indication flag is used to indicate that the packet is discarded when sub-link resources cannot be obtained according to the slice identifier;

When the discard flag is the first value, and the resource allocation flag is the first value, the resource indication flag is used to indicate that the packet is discarded when the sub-link resource cannot be obtained according to the slice identifier, and According to the resource requirements corresponding to the slice identifiers, corresponding sub-link resources are allocated.
The resource allocation method according to any one of claims 1 to 9, wherein, when the message sending node is the head node of the SRv6 policy path, sending the message to the SRv6 policy path includes:

Sending the first N messages on the SRv6 policy path; wherein, the resource indication flags in the first N messages are used to trigger each message receiving node on the SRv6 policy path to carry out subsections corresponding to the slice identifiers. Dynamic allocation of link resources;

Send the N+1th message to the Mth message on the SRv6 policy path; wherein, the resource indicator in the N+1th message to the Mth message is used to detect the SRv6 policy path Whether each message receiving node on the network has completed the dynamic allocation of sublink resources corresponding to the slice identifier; wherein, M is greater than N, and M and N are both positive integers;

Send the message after the Mth message to the SRv6 policy path; wherein, the resource indicator in the message after the Mth message is used to indicate each message receiving node, and the slice identifier cannot When sublink resources are obtained, the message is discarded.
The resource allocation method according to claim 10, wherein the resource indication flag includes a discard flag and a resource allocation flag, and when the discard flag and the resource allocation flag are respectively the first value or the second value:

The resource indication flags in the first N packets are: the discard flag is a second value, and the resource allocation flag is a first value;

The resource indication flags in the N+1th message to the Mth message are: the discarding flag is the first value, and the resource allocation flag is the first value;

The resource indication flag in the packets after the Mth packet: the discard flag is a first value, and the resource allocation flag is a second value.
The resource allocation method according to claim 11, wherein the method further comprises:

During the process of sending the N+1th packet and the packets after the N+1th packet to the SRv6 policy path, if the return packet of the packet is received, and the discard flag in the received return packet is the first value, and the resource allocation flag is the first value, it is determined that the Mth message has been sent, and the next sent message is the M+1th message.
The resource allocation method according to claim 11, wherein the method further comprises:

During the process of sending the N+1th packet and the packets after the N+1th packet to the SRv6 policy path, if the return packet of the packet is received, and the discard flag in the received return packet is the first value, and the resource allocation flag is the first value, it is determined that each node of the SRv6 policy path has completed the allocation of sub-link resources.
A resource allocation method applied to a message receiving node, the method comprising:

Receive packets on the SRv6 policy path;

Wherein, the IPv6 header of the message includes a slice identifier and a resource indication flag, and the resource indication flag is used to indicate to the message receiving node the dynamic allocation of sub-link resources corresponding to the slice identifier.
The resource allocation method according to claim 14, wherein the message includes a BFD message.
The resource allocation method according to claim 14, wherein the resource indication flag comprises a discard flag and/or a resource allocation flag;

The discard flag is used to indicate whether to discard the message when the message receiving node cannot obtain sub-link resources according to the slice identifier;

The resource allocation flag is used to indicate whether the packet receiving node allocates the corresponding sub-link resource according to the slice ID when it cannot obtain the sub-link resource according to the slice ID.
The resource allocation method according to claim 16, wherein, when the discard flag is a first value, it means that the message is discarded when sub-link resources cannot be obtained according to the slice identifier;

When the discarding flag is the second value, it indicates that the packet is forwarded along a preset default path when sub-link resources cannot be obtained according to the slice identifier.
The resource allocation method according to claim 16, wherein when the resource allocation flag is a first value, it indicates that when sub-link resources cannot be obtained according to the slice identifier, corresponding sub-link resources are allocated;

When the resource allocation flag is the second value, it indicates that no sub-link resource is allocated when the sub-link resource cannot be obtained according to the slice identifier.
The resource allocation method according to claim 14, wherein the IPv6 HBH, the new HBH or the DOH of the IPv6 message header include a network slice identification option;

Wherein, the network slice identification option includes the resource indication flag.
The resource allocation method according to claim 14, wherein the resource indication flag is recorded in the source address or flow label field of the IPv6 message header, and the resource indication flag occupies a portion of the source address or flow label field Partial indicator.
The resource allocation method according to claim 19, wherein the network slice identification option further includes: option type, option data field length and the slice identification.
The resource allocation method according to any one of claims 14 to 21, wherein the method further comprises:

In the case that the sublink resource cannot be obtained according to the slice identifier, the message is processed according to the value indicated by the resource indication flag.
The resource allocation method according to claim 22, wherein when the resource indication flag includes a discard flag and a resource allocation flag, the processing of the message is performed according to the value indicated by the resource indication flag, including :

When the discarding flag is a second value, and the resource allocation flag is a second value, forwarding the message along a preset default path;

When the discard flag is the second value and the resource allocation flag is the first value, forward the message along a preset default path, and allocate the corresponding sub-link according to the resource requirement corresponding to the slice identifier resource;

When the discarding flag is a first value and the resource allocation flag is a second value, discarding the message;

When the discard flag is the first value and the resource allocation flag is the first value, discard the message, and allocate corresponding sublink resources according to the resource requirement corresponding to the slice identifier.
A network node, the network node is a message sending node, including: a transceiver, wherein the transceiver is configured as:

Send packets to the SRv6 policy path;

Wherein, the IPv6 packet header of the message includes a slice identifier and a resource indication flag, and the resource indication flag is used to indicate to the message receiving node on the SRv6 policy path the sublink resource corresponding to the slice identifier Dynamic allocation.
A network node, the network node is a message receiving node, including: a transceiver, wherein the transceiver is configured as:

Receive packets on the SRv6 policy path;

Wherein, the IPv6 header of the message includes a slice identifier and a resource indication flag, and the resource indication flag is used to indicate to the message receiving node the dynamic allocation of sub-link resources corresponding to the slice identifier.
A resource allocation device, applied to a message sending node, comprising:

A packet sending unit configured to send packets to the SRv6 policy path;

Wherein, the IPv6 packet header of the message includes a slice identifier and a resource indication flag, and the resource indication flag is used to indicate to the message receiving node on the SRv6 policy path the sublink resource corresponding to the slice identifier Dynamic allocation.
A resource allocation device, applied to a message receiving node, comprising:

A packet receiving unit configured to receive packets on the SRv6 policy path;

Wherein, the IPv6 header of the message includes a slice identifier and a resource indication flag, and the resource indication flag is used to indicate to the message receiving node the dynamic allocation of sub-link resources corresponding to the slice identifier.
A network node, comprising: a processor, a memory, and a program stored on the memory and operable on the processor, when the program is executed by the processor, any one of claims 1 to 13 is implemented The resource allocation method, or implement the resource allocation method according to any one of claims 14 to 23.
A readable storage medium, on which a program is stored, and when the program is executed by a processor, the steps in the resource allocation method according to any one of claims 1 to 13 are realized, or the steps in the resource allocation method according to any one of claims 1 to 13 are realized, or the The steps in the resource allocation method described in any one of requirements 14 to 23.