CN115941623A

CN115941623A - Resource allocation method, device and network node

Info

Publication number: CN115941623A
Application number: CN202210946390.6A
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-08-13
Filing date: 2022-08-08
Publication date: 2023-04-07

Abstract

The application provides a resource allocation method, a resource allocation device and a network node. The method comprises the following steps: the message sending node sends a message to the SRv6 strategy path; the IPv6 message header of the message comprises a slice identifier and a resource indication mark, and the resource indication mark is used for indicating the dynamic allocation of the sub-link resource corresponding to the slice identifier to a message receiving node on the SRv6 strategy path. By adopting the method, the message of the SRv6 strategy path comprises the resource indication mark which is used for triggering the dynamic allocation of the resource of the SRv6 strategy path, and the problem of resource waste caused by adopting a slice resource static allocation mode when the SRv6 message is sent in the related technology can be at least solved.

Description

Resource allocation method, device and network node

The application claims priority of Chinese patent application with application number 202110932008.1 and application date 2021, 08.13.1.

Technical Field

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

Background

At present, a scheme for a data carrying network to support large-scale hard slicing mainly adopts a mode of introducing a slice identifier (such as an ID) into an Internet Protocol Version 6-Segment Routing (IPv 6 SR or SRv6 for short) Policy (english can be expressed as Policy) forwarding plane, that is, the slice identifier is carried in an SRv6 message header, and a forwarding device associates the slice identifier with a bottom layer physical link or a sublink resource and combines corresponding sublink physical isolation technologies, such as a channelized subinterface, a g.8312 (ITU international telecommunication union standard) interface, a Quality of service (Quality of service, qoS) queue, and the like, to provide a high-Quality carrying network hard slicing service with independent resource guarantee for a user.

The scheme that the forwarding plane carries the slice identifier can realize fine-grained slicing at a sub-interface level, and meanwhile, because the control plane protocol does not need to be expanded, excessive cost cannot be brought to network equipment, so that the data carrying network can support large-scale slicing.

At present, the allocation of bottom physical link resources or sub-link resources (i.e. slice resources) corresponding to slice identifiers is mainly a static configuration method, that is, slice resources (physical link resources or sub-link resources) are allocated to each slice identifier in advance on all links of a whole network, and a mapping relationship is established, so that when an apparatus forwards a message of a slice user, the apparatus can find the corresponding sub-link resource according to the slice identifier for forwarding.

Because the path of the SRv6 policy forwarding plane of the slice user is calculated by the controller in real time according to the Service-Level Agreement (SLA) requirement, and in the current scheme of slice resource static allocation, resources need to be reserved for each slice identifier on all links of the whole network, so that resources need to be reserved for links that the SRv6 policy path of the slice user does not pass through, thereby causing great waste of resources of the whole network.

Disclosure of Invention

In order to solve related technical problems, embodiments of the present application provide a resource allocation method, an apparatus, and a network node, which are used to solve a problem of resource waste caused by a manner of statically allocating slice resources when an SRv6 packet is sent in the prior art.

The embodiment of the application provides a resource allocation method, which is applied to a message sending node, and the method comprises the following steps:

sending a message to the SRv6 strategy path;

the IPv6 header of the packet includes a slice identifier and a resource indicator, where the resource indicator is used to indicate, to a packet receiving node on the SRv6 policy path, dynamic allocation of sub-link resources corresponding to the slice identifier.

In the foregoing scheme, the packet includes a Bidirectional Forwarding Detection (BFD) packet.

In the above scheme, the resource indicator includes a discard flag and/or a resource allocation flag;

the discarding mark is used for indicating whether the message receiving node discards the message or not when the sub-link resource cannot be obtained according to the slice identifier;

and the resource allocation mark is used for indicating whether the message receiving node allocates the corresponding sub-link resource according to the slice identifier when the sub-link resource cannot be acquired according to the slice identifier.

In the above solution, when the discard flag is a first value, it indicates that the message is discarded when the sublink resource cannot be obtained according to the slice identifier;

and when the discarding mark is a second value, the message is forwarded along a preset default path when the sublink resource cannot be obtained according to the slice identifier.

In the above scheme, when the resource allocation flag is a first value, it indicates that the sub-link resource cannot be obtained according to the slice identifier, and allocates the corresponding sub-link resource;

and when the resource allocation mark is a second value, the sub-link resource is not allocated when the sub-link resource cannot be obtained according to the slice identifier.

In the above scheme, an IPv6 Hop-By-Hop Options Header (HBH), a new HBH, or a Destination Options Header (DOH) of the IPv6 packet Header includes a network slice identifier option;

wherein the network slice identification option includes the resource indicator.

In the above scheme, the resource indication flag is recorded in a source address or a flow label (Flowlabel) field of the IPv6 header, and the resource indication flag occupies a part of an indication bit (english may be expressed as bit) of the source address or the Flowlabel field.

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

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

the discarding mark is a second value, and the resource allocation mark is a second value, and is used for indicating that the message is forwarded along a preset default path when the sublink resource cannot be obtained according to the slice identifier;

the discarding mark is a second value, and the resource allocation mark is a first value, and is used for indicating that the message is forwarded along a preset default path when the sublink resource cannot be obtained according to the slice identifier, and allocating the corresponding sublink resource according to the resource requirement corresponding to the slice identifier;

the discarding mark is a first value, and the resource allocation mark is a second value, which is used for indicating that the message is discarded when the sublink resource cannot be obtained according to the slice identifier;

the discarding mark is a first value, and the resource allocation mark is a first value, and is used for indicating that the message is discarded when the sublink resource cannot be obtained according to the slice identifier, and allocating the corresponding sublink resource according to the resource requirement corresponding to the slice identifier.

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

sending the first N messages to the SRv6 strategy path; the resource indication marks in the first N messages are used for triggering each message receiving node on the SRv6 policy path to perform dynamic allocation on the sublink resources corresponding to the slice identifier;

sending the (N + 1) th message to the Mth message on the SRv6 strategy path; the resource indication flag in the (N + 1) th to mth messages is used for detecting whether each message receiving node on the SRv6 policy path completes dynamic allocation of the sublink resource corresponding to the slice identifier; wherein M is larger than N, and both M and N are positive integers;

sending the message after the Mth message to the SRv6 strategy path; and the resource indication mark in the message after the Mth message is used for indicating each message receiving node, and when the sublink resource cannot be obtained according to the slice identifier, 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 a first value or a second value:

the resource indicator in the first N messages is: the discarding mark is a second value, and the resource allocation mark is a first value;

the resource indication marks in the (N + 1) th to Mth messages are: the discarding flag is a first value, and the resource allocation flag is a first value;

the resource indication flag in the message after the mth message: the discard flag is a first value and the resource allocation flag is a second value.

In the above scheme, the method further comprises:

in the process of sending the (N + 1) th message and the message after the (N + 1) th message to the SRv6 policy path, if the backhaul message of the message is received, and the discard flag in the received backhaul 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 message to be sent is the (M + 1) th message.

In the foregoing solution, the method further includes:

in the process of sending the (N + 1) th message and the messages after the (N + 1) th message to the SRv6 policy path, if a backhaul message of the message is received, a discard flag in the received backhaul message is a first value, and a resource allocation flag is a first value, it is determined that each node of the SRv6 policy path completes allocation of sub-link resources.

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

receiving a message on an SRv6 strategy path;

the IPv6 header of the packet includes a slice identifier and a resource indicator, where the resource indicator is used to indicate, to the packet receiving node, dynamic allocation of sub-link resources corresponding to the slice identifier.

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

and the resource allocation mark is used for indicating whether the message receiving node allocates the corresponding sub-link resource according to the slice identifier or not when the sub-link resource cannot be acquired according to the slice identifier.

In the above scheme, when the discard flag is a first value, it indicates that the message is discarded when the sublink resource cannot be obtained according to the slice identifier;

and when the resource allocation flag is a second value, the sub-link resource is not allocated when the sub-link resource cannot be obtained according to the slice identifier.

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

In the above scheme, the resource indication flag is recorded in a source address or a flowabel field of the IPv6 header, and the resource indication flag occupies a part of indication bits of the source address or the flowabel field.

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

In the foregoing solution, the method further includes:

and under the condition that the sublink resource cannot be obtained according to the slice identifier, processing the message according to the numerical value indicated by the resource indication mark.

In the foregoing solution, when the resource indicator includes a discard flag and a resource allocation flag, the performing, according to the numerical value indicated by the resource indicator, the processing on the packet includes:

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

when the discarding mark is a second value and the resource allocation mark is a first value, forwarding the message along a preset default path, and allocating corresponding sublink resources according to the resource requirement corresponding to the slice identifier;

when the discarding mark is a first value and the resource allocation mark is a second value, discarding the message;

and when the discarding mark is a first value and the resource allocation mark is a first value, discarding the message and allocating the corresponding sublink resource according to the resource requirement corresponding to the slice identifier.

An embodiment of the present application further provides a network node, where the network node is a packet sending node, and the network node includes: a transceiver, wherein the transceiver is configured to:

sending a message to the SRv6 strategy path;

An embodiment of the present application further provides a network node, where the network node is a packet receiving node, and the network node includes: a transceiver, wherein the transceiver is configured to:

receiving a message on an SRv6 strategy path;

the IPv6 header of the packet includes a slice identifier and a resource indicator, where the resource indicator is used to indicate, to the packet receiving node, dynamic allocation of a sublink resource corresponding to the slice identifier.

The embodiment of the present application further provides a resource allocation apparatus, which is applied to a packet sending node, and includes:

the message sending unit is configured to send a message to the SRv6 policy path;

The embodiment of the present application further provides a resource allocation apparatus, which is applied to a packet receiving node, and includes:

the message receiving unit is configured to receive a message on the SRv6 policy path;

An embodiment of the present application further provides a network node, including: a processor, a memory and a program stored in the memory and executable on the processor, the program implementing the steps of any of the methods at the message sending node side or implementing the steps of any of the methods at the message receiving node side when executed by the processor.

An embodiment of the present application further provides a readable storage medium, where a program is stored, and when the program is executed by a processor, the program implements the steps of any method on the message sending node side, or implements the steps of any method on the message receiving node side.

The technical scheme provided by the embodiment of the application has the following beneficial effects:

according to the resource allocation method, the resource allocation device and the network node provided by the embodiment of the application, the message of the SRv6 policy path includes the resource indication mark, and is used for triggering the dynamic allocation of the resource of the SRv6 policy path, so that on the SRv6 policy path, each message receiving node realizes the dynamic allocation of the sublink resource corresponding to the slice identifier according to the resource indication mark, associates the allocated sublink resource with the slice identifier, ensures that the subsequent slice service can be forwarded along the dynamically allocated sublink resource according to the slice identifier, and can have an exclusive slice resource, thereby at least solving the problem of resource waste caused by adopting a slice resource static allocation mode when the SRv6 message is sent in the related technology.

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 identifier option for carrying a resource indicator according to an embodiment of the present application;

FIG. 3 is a schematic structural diagram of a resource indicator according to an embodiment of the present application;

FIG. 4 is a schematic diagram of an exemplary system architecture for use in the present application;

FIG. 5 is a schematic diagram of an exemplary policy path applied in the present application;

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

fig. 7 is a schematic structural diagram of a message sending node according to the embodiment of the present application;

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

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

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

Detailed Description

To make the technical problems, technical solutions and advantages to be solved by the present application clearer, the following detailed description is made with reference to the accompanying drawings and specific embodiments.

In the data carrying network supporting large-scale slicing, the SRv6 policy path of a slicing user is calculated by the controller in real time according to the SLA requirements, and based on the current slicing resource static allocation mode, resources need to be reserved on all links of the whole network for each slicing identifier, so that links corresponding to the slicing user and not passed by the SRv6 policy path also need to be reserved with resources, thereby causing great waste of resources of the whole network.

An embodiment of the present application provides a resource allocation method, which is applied to a packet sending node, and as shown in fig. 1, the method includes:

s110, sending a message to the SRv6 strategy path;

the IPv6 header of the packet includes a Slice identifier (for example, an ID, which may be specifically expressed as a Slice ID) and a resource indication flag (which may be expressed as Flags in english), where the resource indication flag is used to indicate, to a packet receiving node on the SRv6 policy path, dynamic allocation of a sublink resource corresponding to the Slice identifier.

In practical application, the sent message may include a BFD message, or may include a service message of a user, or may include a newly defined message.

The Slice identifier may also be referred to as a Network Slice identifier (english may be expressed as a Network Slice Selector), and the name of the Slice identifier is not limited in the embodiment of the present application as long as the function of the Slice identifier is implemented.

With the resource allocation method in this embodiment, the resource indicator is used to indicate, to the message receiving node on the SRv6 policy path, dynamic allocation of the sublink resource corresponding to the slice identifier, so that, on the SRv6 policy path, each message receiving node implements dynamic allocation of the sublink resource corresponding to the slice identifier according to the resource indicator, and associates the allocated sublink resource with the slice identifier, thereby ensuring that subsequent slice services can be forwarded along the dynamically allocated sublink resource according to the slice identifier, so as to have an exclusive slice resource.

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

In this embodiment of the application, the specific implementation of step S110 may include: sending a BFD message to the SRv6 policy Path, that is, triggering dynamic allocation of sublink resources through a BFD connection establishment procedure of an SRv6 policy Candidate Path (CP) (which may be referred to as SRv6 policy Path for short) of the slice user. Specifically, a Software Defined Network (SDN) controller may calculate Segment list (Segment) paths of an SRv6 policy master CP and a backup CP for a slice user, corresponding to slice link resource requirements of the slice user, and perform routing of the paths using end.x Segment identifiers (segments ID, SID) of each link.

In actual application, according to a main CP or each standby CP of an SRv6 policy calculated by an SDN controller, dynamic allocation of resources of an SRv6 policy path may be triggered, and on the main CP or each standby CP of the SRv6 policy, a first node (also referred to as a head node, and corresponding to a message sending node) periodically sends a message, where the message includes a slice identifier and a resource indication flag, so that a forwarding plane carries the slice identifier, indicates resource information required by the message, and carries the resource indication flag, to indicate dynamic allocation of sub-link resources corresponding to the slice identifier.

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

In practical application, the discarding flag can be represented as D-flag, and the resource allocation flag can be represented as A-flag.

In an embodiment of the present application, the sublink resource may include an underlying physical sublink resource, such as one or more of a g.mtn subinterface, a channelization subinterface, and a QoS queue.

In the embodiment of the application, the resource allocation flag included in the resource indication flag in the message is used for indicating whether to trigger allocation of the corresponding sublink resource according to the slice identifier when the sublink resource cannot be obtained according to the slice identifier; the discarding mark included in the resource indication mark is used for indicating whether to discard the message when the sublink resource cannot be obtained according to the slice identifier, so that real-time dynamic allocation of the physical sublink resource on the upper bottom layer of the outgoing interface of each message receiving node on the SRv6 policy path can be realized through the resource allocation mark and the discarding mark, the sublink resource is associated with the slice identifier, subsequent slice service flow can be ensured to be forwarded along the dynamically allocated sublink resource according to the slice identifier, and thus, the service corresponding to the slice identifier is ensured to have an exclusive slice resource.

In this embodiment of the application, when the discard flag is a first value, such as 1, it may indicate that the message is discarded when the sublink resource cannot be obtained according to the slice identifier;

when the discard flag is a second value, for example, when the discard flag is 0, it may indicate that the message is forwarded along a preset default path when the sublink resource cannot be obtained according to the slice identifier.

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

when the resource allocation flag is a second value, for example, 0, it may indicate that sub-link resources are not allocated when the sub-link resources cannot be obtained according to the slice identifier.

In this embodiment of the present application, a resource indicator may be carried by a Network Slice identifier Option (english may be expressed as a Network Slice Selector Option) in an IPv6 header of a packet, in other words, an IPv6 HBH, a new HBH, or a DOH of the IPv6 header may include the Network Slice identifier Option;

wherein the network slice identification option may include the resource indicator.

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

In practical applications, the format of the network slice identifier Option may be as shown in fig. 2, and the network slice identifier Option may include an Option Type (english may be expressed as Option Type), an Option Data field length (english may be expressed as Opt Data Len), the resource indicator, and the slice identifier.

The network slice identifier option includes an option type, an option data field length, a resource indicator, and a representation mode (i.e., a representation form) and meaning of the slice identifier as follows:

the option types are: an 8-bit identifier may be included, and a specific value of The 8-bit identifier may be Assigned by The Internet Assigned Numbers Authority (IANA); for example, in the 8-bit identifier, the first 2 bits of the highest order may be set to 00, which is used to indicate that a packet receiving node that cannot identify the option type may skip the network slice identifier option and continue processing the IPv6 header; the 3 rd bit of the first 3 highest order bits may be set to 0, indicating that the option data in the network slice identification option is not changed during the message transmission.

Option data field length: an 8-bit identifier may be included, where the data length recorded in the option data field length is counted in eight bits, and a specific value is used to indicate the data length of the data carried after the option data field length in the network slice identifier option. Illustratively, when the field length specifically indicates a value of 6, the data length of the data carried after the field length of the option data is indicated to be 6 bytes.

Network slice identification: an identifier (such as an ID) for indicating the network slice to which the data packet belongs, i.e. a slice identifier in this application.

Resource indication mark: a 16-bit identifier may be included as shown in fig. 3. Exemplarily, the 1 st bit identifier in the resource indicator may be a discard flag bit for recording a discard identifier; when the discard flag is set to 1, it may indicate that the packet is discarded when the sublink resource cannot be obtained according to the slice identifier; when the discard flag is set to 0, it may indicate that the packet is forwarded along a preset default path when the sublink resource cannot be obtained according to the slice identifier. The 2 nd bit identifier in the resource indication flag may be a resource allocation flag bit for recording the resource allocation flag; when the resource allocation flag is set to 1, it may indicate that the corresponding sublink resource is allocated when the sublink resource cannot be obtained according to the slice identifier; when the resource allocation flag is set to 0, it may indicate that sub-link resources are not allocated when the sub-link resources cannot be obtained according to the slice identifier. As shown in fig. 3, the identifier other than the 1 st bit and the 2 nd bit in the resource indicator may be represented as R to indicate that the identifier is not used and is available for future use. For example, when a 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 this embodiment of the present application, a resource indication flag may be carried by a source address or a flowabel field of an IPv6 header of a packet, in other words, the resource indication flag is recorded in the source address or the flowabel field of the IPv6 header, and the resource indication flag occupies a part of an indication bit of the source address or the flowabel field.

Specifically, when a resource indication flag is recorded in a source address or a flowabel field of an IPv6 header, and the resource indication flag includes a resource allocation flag and a discard flag, two indication bits in the source address or the flowabel field may be used to carry the resource allocation flag and the discard flag, respectively.

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

when the discard 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 packet is forwarded along a preset default path when the sublink resource cannot be obtained according to the slice identifier;

when the discard 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 for indicating that the message is forwarded along a preset default path when the sublink resource cannot be obtained according to the slice identifier, and allocating the corresponding sublink resource according to the resource requirement corresponding to the slice identifier;

when the discard flag is a first value (e.g., 1) and the resource allocation flag is a second value (e.g., 0), the resource indication flag is used to indicate that the packet is discarded when the sublink resource cannot be obtained according to the slice identifier;

when the discard flag is a first value (for example, 1), and the resource allocation flag is a first value (for example, 1), the resource indication flag is used to indicate that the message is discarded when the sublink resource cannot be obtained according to the slice identifier, and the corresponding sublink resource is allocated according to the resource requirement corresponding to the slice identifier.

In actual application, for a BFD packet sent in the BFD establishment process of the SRv6 policy CP for a slice user, when each packet receiving node on the SRv6 policy path receives a BFD packet including a resource indication flag, the processing of the BFD packet may be performed according to a numerical value indicated by the resource indication flag. Specifically, the message receiving node may execute processing on the BFD message according to the indication meaning of the resource indication flag when the discard flag and the resource allocation flag are different values, respectively.

In this embodiment of the present application, when the packet sending node is a head node of an SRv6 policy path, the sending a packet to the SRv6 policy path may include:

sending the first N messages to the SRv6 strategy path; the resource indication marks in the first N messages are used for triggering each message receiving node on the SRv6 policy path to dynamically allocate the sublink resources corresponding to the slice identifier;

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 a first value or a second value, the discard flag is the second value and the resource allocation flag is the first value in the resource indication flags in the previous N messages; the first value can be 1, the second value can be 0, in the former N messages, the Flag bit of D-Flag is 0, and the Flag bit of A-Flag is 1; thus, each message receiving node receiving the message can report information to the control plane according to the D-Flag and the A-Flag when the sublink resource cannot be obtained according to the slice identifier by using the Flag bit of the D-Flag as 0 and the Flag bit of the A-Flag as 1, and simultaneously forward the message from the physical port corresponding to the outgoing interface or the non-slice shared sublink resource of the outgoing interface (that is, forward the message through the sublink corresponding to the slice identifier); the control plane can issue a data plane to create or occupy physical sublink interface resources of corresponding resources (namely, allocate corresponding sublink resources) according to resource requirements corresponding to the slice identifiers; in the embodiment of the present application, the value of N may be determined by pre-configuration, such as an integer greater than or equal to 1.

In the embodiment of the present application, through the first N messages sent, the messages can trigger dynamic resource allocation on each node along the SRv6 policy path, and associate the allocated sublink resources with the slice identifier in the message.

In the embodiment of the application, after the first N messages are sent, the (N + 1) th message to the mth message can be sent to the SRv6 policy path; the resource indication flag in the (N + 1) th message to the (M) th message is used for detecting whether each message receiving node on the SRv6 policy path completes dynamic allocation of the sublink resource corresponding to the slice identifier; wherein M is larger than N, and both M and N are positive integers;

wherein, in the resource indication marks from the (N + 1) th message to the M < th > message, the discard mark is a first value, the resource allocation mark is a first value, the first value can be 1, then the (N + 1) th message to the M < th > message, the Flag bit of the D-Flag is 1, and the Flag bit of the A-Flag is 1; thus, each message receiving node receiving the message reports information to the control plane according to the D-Flag and the A-Flag when the sublink resource can not be obtained according to the slice identifier and discards the message at the same time through the Flag bit of the D-Flag being 1 and the Flag bit of the A-Flag being 1; the control plane may issue, according to the resource requirement corresponding to the slice identifier, a physical sub-link interface resource (i.e., allocate a corresponding sub-link resource) for which the data plane creates or occupies a corresponding bandwidth.

In this embodiment of the present application, in the process of sending an N +1 th packet and a packet after the N +1 th packet to an SRv6 policy path, if a backhaul packet of the packet is received, and a discard flag in the received backhaul packet is a first value and a resource allocation flag is a first value, it is determined that the mth packet has been sent and a next packet to be sent is the M +1 th packet.

In this embodiment of the present application, in a process of sending an (N + 1) th packet and a packet after the (N + 1) th packet to an SRv6 policy path, if a backhaul packet of the packet is received, a discard flag in the received backhaul packet is a first value, and a resource allocation flag is a first value, it is determined that each node of the SRv6 policy path completes allocation of a sublink resource (it may be understood that it is determined that each node of the SRv6 policy path completes dynamic allocation and association of a sublink resource corresponding to the slice identifier).

Specifically, in practical application, when a BFD message is transmitted on an SRv6 policy path, each message receiving node can obtain a sublink resource according to a slice identifier in the BFD message, and then forward the BFD message on the corresponding sublink resource according to the slice identifier; and when the sublink resources cannot be obtained, reporting information to the control plane, and discarding the message, so that the control plane allocates the corresponding sublink resources according to the resource requirements corresponding to the slice identifier. In this way, in the process of sending the (N + 1) th BFD packet to the mth BFD packet until receiving the backhaul packet of the BFD packet, if the discard flag in the backhaul packet of the received BFD packet is the first value and the resource allocation flag is the first value, it may be determined that the SRv6 policy path detection is completed, each node of the SRv6 policy path completes dynamic allocation and association of the sub-link resource corresponding to the slice identifier, and the BFD states are communicated (may be expressed as UP in english), thereby further determining that the mth BFD packet has been sent and the next BFD packet to be sent is the (M + 1) th BFD packet, and changing the value indicated by the resource indication flag.

In this embodiment of the present application, when it is determined that each message receiving node on the SRv6 policy path has completed dynamic allocation of the sublink resource corresponding to the slice identifier according to the backhaul message of the mth message, a message after the mth message may be sent to the SRv6 policy path; and the resource indication mark in the message after the Mth message is used for indicating each message receiving node, and when the sublink resource cannot be obtained according to the slice identifier, the message is discarded.

In the resource indication flag in the message after the mth message, the discard flag is a first value, and the resource allocation flag is a second value. The first value may be 1, the second value may be 0, and then in the message after the mth message, the Flag bit of the D-Flag is 1, and the Flag bit of the a-Flag is 0; therefore, each message receiving node receiving the message can discard the message according to the D-Flag and the A-Flag through the Flag bit of the D-Flag being 1 and the Flag bit of the A-Flag being 0.

In the embodiment of the application, for the BFD packet, the periodic detection BFD packet may be sent after a session state corresponding to the slice policy path is connected, and if the physical sub-link interface corresponding to the slice identifier cannot be found at the egress interface on the device data plane, the BFD packet may be discarded.

It should be noted that, in the embodiment of the present application, the BFD packet may be at least one of a static BFD, a dynamic BFD, and an SBFD, so as to detect the on-off of the SRv6 policy CP.

In this embodiment of the present application, the specific manner of triggering dynamic resource allocation and association of the SRv6 policy CP by using the BFD packet sent in the BFD establishment process of the SRv6 policy CP of the slice user may include:

when a BFD session is established for an SRv6 strategy CP, a head node of an SRv6 strategy path clears a D-flag (namely, the D-flag is set to be 0) in a resource indication flag (such as carried in an HBH header) in the first N BFD messages (the N value is configurable), and sets an A-flag (namely, the A-flag is set to be 1); through the indication mode, the resource indication marks in the first N BFD messages trigger each message receiving node on the SRv6 strategy path to dynamically allocate the sub-link resources corresponding to the slice identifier;

setting a D-flag mark (namely setting the D-flag to be 1) and an A-flag mark (namely setting the A-flag to be 1) in an HBH (basic node) in a BFD (bidirectional forwarding detection) message sent by a head node in the subsequent (after the Nth BFD message); by the indication mode, the BFD message sent after the Nth BFD message is used for detecting whether each message receiving node on the SRv6 strategy path completes dynamic allocation of the sub-link resource corresponding to the slice identifier or not until the head node receives the return messages of the BFD message of which the D-flag mark and the A-flag mark are respectively 1;

based on the above, when a head node receives a backhaul message of a BFD message, if a D-flag of a resource indication flag is 1 and an a-flag is 1 in the received BFD message of the backhaul message, it is determined that each node of the SRv6 policy path completes dynamic allocation and association of sub-link resources corresponding to the slice identifier, and the BFD states are connected; meanwhile, clearing an A-flag mark in the HBH header (namely setting the A-flag to be 0); and sending subsequent periodic detection BFD messages; and in the subsequent periodic detection BFD message, the resource indication mark in the BFD message is used for indicating each message receiving node, and when the sub-link resource cannot be obtained according to the slice identifier, the BFD message is discarded.

In practical application, when the BFD session state corresponding to the slice SRv6 strategy CP is communicated, the sent periodic detection BFD message can indicate that the BFD message is discarded when the data plane forwarding BFD message cannot find the physical sub-link interface corresponding to the slice identifier at the outlet interface through setting the D-flag and clearing the A-flag;

in addition, after the BFD session states corresponding to the slice SRv6 policy CP are connected, the states of the SRv6 policy can be connected, so that the service can be directed to the SRv6 policy.

On an SRv6 policy path, when a resource indication mark is adopted for indication, for each message receiving node receiving a message, when a data plane finds a sublink resource corresponding to a slice identifier indicated by the message at an outgoing interface, the message is forwarded through the sublink resource corresponding to the slice identifier, and when the data plane cannot find the sublink resource corresponding to the slice identifier at the outgoing interface, different actions are executed according to a D-flag mark and an A-flag mark bit in the resource indication mark of the message:

the value of the D-flag is 0, and the value of the A-flag is also 0: forwarding the message from a physical port corresponding to the egress interface or a non-slice shared sublink resource of the egress interface (that is, forwarding the BFD message through a default sublink);

the value of the D-flag is 0, the value of the A-flag is 1: reporting information to a control plane, and simultaneously forwarding the message from a physical port corresponding to the egress interface or a non-slice shared sublink resource of the egress interface (that is, forwarding the BFD message through a default sublink); the control plane issues a physical sub-link interface resource (namely, allocates a corresponding sub-link resource) of the data plane for creating or occupying a corresponding bandwidth according to the resource requirement corresponding to the slice identifier;

the value of the D-flag is 1, the value of the A-flag is 0: discarding the message;

the value of the D-flag is 1, the value of the A-flag is 1: reporting information to a control plane, and discarding the message; and the control plane issues a physical sublink interface resource (namely, allocates a corresponding sublink resource) for the data plane to create or occupy a corresponding bandwidth according to the resource requirement corresponding to the slice identifier.

The following describes a specific implementation process of the resource allocation method according to the embodiment of the present application with reference to an application example.

As shown in fig. 4, the present application example provides a network architecture for the resource allocation method, where the network architecture may include node devices a, B, C, D, E, F, G, and H, the eight node devices run an ISIS dynamic routing Protocol, and are all in the same Intermediate system to Intermediate system (ISIS) domain, all devices support slicing capability, and a Border Gateway Protocol (BGP) -connection State (Link-State, LS) connection is established between an SDN controller and a forwarding device.

The End SID and end.x SID of each device in the network architecture are allocated as shown in fig. 5.

Based on the network architecture, it is assumed that a 100 megabits per second (Mbps) bandwidth-exclusive slice link resource from node a to node E is needed for slice user 1 in the current network.

For example, if the allocated slice identifier is 1 and the corresponding resource information is 100M bandwidth, the relationship between the allocated slice identifier and the slice user is as shown in table 1 below:

TABLE 1

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

On the basis of the distributed slice identification resources, the controller or the head node calculates a segmentlist path of the SRv6 strategy main CP and the standby CP, the bandwidth resources from A to E of which meet the 100M requirement, according to the requirement of the slice user 1, and uses the end.X SID of each link to arrange the path. Wherein, 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 primary and backup CPs may be represented as:

and (3) main CP: 100 in the formula (3: 1), 100 in the formula (3: 2), 100 in the formula (3: 3) and 100 in the formula (3: 4);

preparing a CP: 100 parts of X3:5, 100 parts of X3:6, 100 parts of X3:7 and 100 parts of X3: 8.

Upon establishing the primary and backup CPs, the slice identification identified as "1" is associated with the SRv6 policy path (including the primary and backup CPs).

And under the condition that the SDN controller calculates the path, the SDN controller issues the path to the head node A through a BGP SRv6 strategy.

According to the main CP and the standby CP calculated for the slice user 1, the BFD message sent in the corresponding BFD connection establishment process is utilized to trigger the dynamic allocation and association of resources on the SRv6 strategy CP, the sub-interface link resources on each node device take QoS queue as an example, and along the SRv6 strategy path (including the main CP and the standby CP) corresponding to the slice user 1, the dynamic allocation process of the sub-link resources corresponding to the slice identifier is as follows:

after receiving a BGP SRv6 policy path (comprising a main CP and a standby CP) and a slice identifier SliceID1 issued by a controller, a head node A of the SRv6 policy path starts BFD for the SRv6 policy path (comprising the main CP and the standby CP) according to the BFD configuration corresponding to the SRv6 policy path;

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

the BFD message is forwarded along a main CP (ratio of X3:1: 100, X3:2: 100, X3:3: 100, X3:4: 100), an exit port 0/0/1 is found out at a head node A according to the ratio of X3:1: 100, information is reported to a control plane according to the indication that D-flag is 0 and A-flag is 1 under the condition that a corresponding QoS queue cannot be found at a data plane according to SliceID1 carried in a forwarding plane message head on the exit port 0/0/1, and the BFD message is forwarded from a non-slice shared link resource of a physical port corresponding to an exit interface or the exit interface; the control plane learns that the resource requirement is 100M bandwidth according to SliceID1 carried in a message header of a BFD message, and then issues a data plane to create a QoS queue with 100M bandwidth for the data plane, associates the QoS queue with the SliceID1 and locally stores the corresponding relation;

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

in the subsequent BFD messages (i.e. the messages after the Nth message, namely the (N + 1) th BFD message and the BFD messages after the (N + 1) th BFD message) sent by the head node A, setting a D-flag carried in the forwarding plane message as 1 and setting an A-flag as 1, wherein the D-flag is used for detecting whether each node on the main CP completes the dynamic allocation of the sub-link resources corresponding to the SliceID 1;

if the resource allocation of the 100M bandwidth QoS queue of the SliceID1 on the output interface corresponding to the equipment A, B, C and D on the main CP is successful, the BFD message is forwarded from the QoS queue associated with the SliceID1 of the corresponding output interface on the equipment A, B, C and D;

if the resource allocation and association of the QoS queue with the bandwidth of 100M on the corresponding output interface of the devices A, B, C and D along the way are not finished, and the QoS queue associated with the SliceID1 cannot be found on the data plane, sending information to the control plane according to the indication that the D-flag is 1 and the A-flag is 1, and simultaneously discarding the BFD message; the device control plane learns that the resource requirement is 100M bandwidth according to the SliceID1, then issues a QoS queue of which the data plane creates 100M bandwidth for the device control plane, associates the QoS queue with the SliceID1, and locally stores the corresponding relation;

in the above process, the BFD state on the SRv6 policy CP remains unconnected (english may be expressed as Down) state;

when a head node A of an SRv6 strategy path receives a return message of a BFD message with a D-flag of 1 and an A-flag of 1, indicating that resource allocation and association of a SliceID1 corresponding to a 100M bandwidth QoS queue on an output interface corresponding to all nodes along a main CP are finished, and then BFD states are communicated; and simultaneously clearing an A-flag mark (A-flag = 0) carried in the forwarding surface message, and continuously sending a subsequent periodic detection BFD message.

Similarly, the connection process of the BFD queue on the backup CP of the calculated SRv6 policy path is the same as that of the backup CP (the connection process is performed simultaneously with the BFD session establishment process of the main CP), and is not described in detail here.

Based on the above process, when the states of the BFD session of the master CP and the backup CP are both connected, the state of the SRv6 policy is connected, and the service traffic of the slice user 1 is introduced into the SRv6 policy bearer, so that it is ensured that the traffic of the slice user 1 can obtain the exclusive physical resource guarantee of the QoS queue of 100M on each link of the SRv6 policy forwarding path.

It can be seen from the above description that, in the resource allocation method provided in this embodiment of the present application, the dynamic allocation of the sublink resource corresponding to the slice identifier is indicated to the packet receiving node on the SRv6 policy path by the resource indicator, so that real-time dynamic allocation and association of physical resources required by a slice on the SRv6 policy path of the bearer network are implemented, and the problems that the resource is greatly wasted and is not suitable for large-scale deployment in the existing network due to the static allocation scheme of the slice resource can be solved.

Correspondingly, an embodiment of the present application further provides a resource allocation method, which is applied to a packet receiving node, and as shown in fig. 6, the method includes:

s610, receiving a message on the SRv6 strategy path;

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 in the embodiment of the present application, in a packet, a resource indicator indicates dynamic allocation of a sublink resource corresponding to a slice identifier, so that on an SRv6 policy path, each packet receiving node implements dynamic allocation of the sublink resource corresponding to the slice identifier according to the resource indicator, and associates the allocated sublink resource with the slice identifier, thereby ensuring that a subsequent slice service can be forwarded along the dynamically allocated sublink resource according to the slice identifier, so as to have an exclusive slice resource.

the discarding mark is used for indicating whether the message receiving node discards the message or not when the sublink resource cannot be obtained according to the slice identifier;

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

when the discard flag is the second value, it may indicate that the packet is forwarded along a preset default path when the sublink resource cannot be obtained according to the slice identifier.

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

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

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

In this embodiment of the present application, the resource indication flag may be recorded in a source address of the IPv6 header or a flowabel field, and the resource indication flag may occupy a part of indication bits of the source address or the flowabel field.

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

In this embodiment, the method may further include:

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

When the resource allocation method provided in the embodiment of the present application is applied to a packet receiving node, the specific manner and the specific content of the resource indicator, and the specific manner of performing real-time dynamic allocation and association of the sublink resource corresponding to the slice identifier according to the resource indicator may refer to the detailed description of the application of the above method to a packet sending node, and are not described here again.

An embodiment of the present application further provides a network node, where the network node is a packet sending node, and as shown in fig. 7, the packet sending node 700 includes: a transceiver 710, wherein the transceiver 710 is configured to:

sending a message to the SRv6 strategy path;

the IPv6 packet header of the packet includes a slice identifier and a resource indicator, where the resource indicator is used to indicate, to a packet receiving node on the SRv6 policy path, dynamic allocation of a sublink resource corresponding to the slice identifier.

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

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

In this embodiment of the present application, when the discard flag is a first value, it indicates that the packet is discarded when the sublink resource cannot be obtained according to the slice identifier;

In the embodiment of the present application, when the resource allocation flag is a first value, it indicates that a corresponding sublink resource is allocated when a sublink resource cannot be obtained according to the slice identifier;

In the embodiment of the application, the IPv6 HBH, the new HBH, or the DOH of the IPv6 header includes a network slice identifier option;

In this embodiment of the present application, the resource indication flag is recorded in a source address or a flowabel field of the IPv6 header, and the resource indication flag occupies a part of an indication bit of the source address or the flowabel field.

In this embodiment, the network slice identifier option further includes: an option type, an option data field length, and the slice identifier.

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

the discarding mark is a second value, and when the resource allocation mark is the second value, the resource indication mark is used for indicating that the message is forwarded along a preset default path when the sublink resource cannot be obtained according to the slice identifier;

the discarding mark is a second value, and when the resource allocation mark is a first value, the resource indication mark is used for indicating that the message is forwarded along a preset default path when the sublink resource cannot be obtained according to the slice identifier, and allocating the corresponding sublink resource according to the resource requirement corresponding to the slice identifier;

when the discard flag is a first value and the resource allocation flag is a second value, the resource indication flag is used for indicating that the message is discarded when the sublink resource cannot be obtained according to the slice identifier;

and when the discarding mark is a first value and the resource allocation mark is a first value, the resource indication mark is used for indicating that the message is discarded when the sublink resource cannot be obtained according to the slice identifier, and the corresponding sublink resource is allocated according to the resource requirement corresponding to the slice identifier.

In this embodiment, the transceiver 710 is further configured to:

sending the (N + 1) th message to the Mth message on the SRv6 strategy path; the resource indication flag in the (N + 1) th message to the (M) th message is used for detecting whether each message receiving node on the SRv6 policy path completes dynamic allocation of the sublink resource corresponding to the slice identifier; wherein M is larger than N, and both M and N are positive integers;

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 a first value or a second value:

the resource indication marks in the (N + 1) th message to the Mth message are as follows: the discarding flag is a first value, and the resource allocation flag is a first value;

In this embodiment, the transceiver 710 is further configured to:

in the process of sending the (N + 1) th message and the message after the (N + 1) th message to the SRv6 policy path, if the backhaul message of the message is received, the discard flag in the received backhaul 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 message to be sent is the (M + 1) th message.

In this embodiment, the transceiver 710 is further configured to:

An embodiment of the present application further provides a network node, where the network node is a packet receiving node, and as shown in fig. 8, the packet receiving node 800 includes: a transceiver 810, wherein the transceiver 810 is configured to:

receiving a message on an SRv6 strategy path;

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

In this embodiment, the transceiver 810 is further configured to:

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

when the discarding mark is a second value and the resource allocation mark is a first value, forwarding the message along a preset default path and reporting information to a control plane, so that the control plane allocates corresponding sub-link resources according to the resource requirement corresponding to the slice identifier;

and when the discarding mark is a first value and the resource allocation mark is the first value, discarding the message and reporting information to the control plane, so that the control plane allocates the corresponding sub-link resource according to the resource requirement corresponding to the slice identifier.

An embodiment of the present application further provides a resource allocation apparatus, which is applied to a packet sending node, and as shown in fig. 9, the packet sending node 900 includes:

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

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

when the discarding mark is a first value and the resource allocation mark is a second value, the resource indication mark is used for indicating that the message is discarded when the sublink resource cannot be obtained according to the slice identifier;

and when the discarding mark is a first value and the resource allocation mark is a first value, the resource indication mark is used for indicating that the message is discarded when the sublink resource cannot be obtained according to the slice identifier, and allocating the corresponding sublink resource according to the resource requirement corresponding to the slice identifier.

In this embodiment of the application, when the packet sending node is a head node of an SRv6 policy path, the packet sending unit 910 is further configured to:

sending the message after the Mth message to the SRv6 strategy path; and the resource indication marks in the messages after the Mth message are used for indicating all message receiving nodes, and when the sublink resources cannot be obtained according to the slice identifiers, the messages are discarded.

In this embodiment of the application, the message sending unit 910 is further configured to:

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

An embodiment of the present application further provides a resource allocation apparatus, which is applied to a packet receiving node, as shown in fig. 10, where the packet receiving node 1000 includes:

a message receiving unit 1010 configured to receive a message on an SRv6 policy path;

In this embodiment of the application, the message receiving unit 1010 is further configured to:

and under the condition that the sublink resource cannot be obtained according to the slice identifier, executing the processing of the message according to the numerical value indicated by the resource indication mark.

In this embodiment of the application, when the resource indication flag includes a discard flag and a resource allocation flag, the packet 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.

An embodiment of the present application further provides a network node, including: a processor, a memory, and a program stored in and executable on the memory, the program, when executed by the processor, implementing the steps of the message sending node-side method or the steps of the message receiving node-side method.

The network node may include the above-mentioned message sending node or be a message receiving node, and when the program is executed by the processor on the message sending node and the message receiving node, the specific implementation process of the embodiment of the resource allocation method may be implemented by referring to the above detailed description, which is not described here.

In addition, a readable storage medium is provided, in which a program is stored, and the program implements the steps of the message sending node side method or the steps of the message receiving node side method when the program is executed by a processor.

Specifically, the computer-readable storage medium is applied to the above-mentioned packet sending node or packet receiving node, and when the computer-readable storage medium is applied to the packet sending node or the packet receiving node, the execution steps in the corresponding resource allocation method are detailed in the method embodiment, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed method and apparatus may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may be physically included alone, or two or more units may be integrated into one unit. The integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional unit.

The integrated unit implemented in the form of a software functional unit may be stored in a computer readable storage medium. The software functional unit is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute some steps of the transceiving method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

While the foregoing is directed to embodiments of the present application, it will be apparent to those skilled in the art that various changes and modifications can be made herein without departing from the spirit and scope of the application, and that such changes and modifications are to be considered as within the scope of the application.

Claims

1. A resource allocation method is applied to a message sending node, and the method comprises the following steps:

sending a message to the SRv6 strategy path;

2. The method according to claim 1, wherein the messages comprise bidirectional detection (BFD) messages.

3. The method according to claim 1, wherein the resource indicator flag comprises a discard flag and/or a resource allocation flag;

4. The method according to claim 3, wherein the discard flag has a first value indicating that the packet is discarded when the sublink resource is not available according to the slice identifier;

5. The method according to claim 3, wherein when the resource allocation flag has a first value, indicating that the sub-link resource cannot be obtained according to the slice identifier, the corresponding sub-link resource is allocated;

6. The method according to claim 1, wherein the IPv6 hop-by-hop option header HBH, new HBH, or destination option header DOH of the IPv6 packet header includes a network slice identifier option;

7. The method according to claim 1, wherein the resource indicator is recorded in a source address or a flow label field of the IPv6 header, and the resource indicator occupies a part of indicator bits of the source address or the flow label field.

8. The method of claim 6, wherein the network slice identification option further comprises: an option type, an option data field length, and the slice identifier.

9. The method according to claim 5, wherein the resource indicator flag comprises a discard flag and a resource allocation flag;

10. The method according to any one of claims 1 to 9, wherein when the message sending node is a head node of an SRv6 policy path, the sending a message to the SRv6 policy path includes:

sending messages after the Mth message to the SRv6 strategy path; and the resource indication mark in the message after the Mth message is used for indicating each message receiving node, and when the sublink resource cannot be obtained according to the slice identifier, the message is discarded.

11. The method according to claim 10, wherein the resource indicator flag comprises a discard flag and a resource allocation flag, and when the discard flag and the resource allocation flag are respectively a first value or a second value:

the resource indicator in the first N messages is: the discarding flag is a second value, and the resource allocation flag is a first value;

12. The method of claim 11, further comprising:

13. The method of claim 11, further comprising:

14. A resource allocation method is applied to a message receiving node, and the method comprises the following steps:

receiving a message on an SRv6 strategy path;

15. The method of claim 14, wherein the messages comprise BFD messages.

16. The resource allocation method according to claim 14, wherein the resource indication flag comprises a discard flag and/or a resource allocation flag;

17. The method according to claim 16, wherein the discard flag has a first value indicating that the message is discarded when the sublink resource is not available according to the slice identifier;

18. The method according to claim 16, wherein when the resource allocation flag has a first value, indicating that the sub-link resource cannot be obtained according to the slice identifier, the corresponding sub-link resource is allocated;

19. The method according to claim 14, wherein the IPv6 HBH, the new HBH, or the DOH of the IPv6 header includes a network slice identifier option;

20. The method according to claim 14, wherein the resource indication flag is recorded in a source address or a flow label field of the IPv6 header, and the resource indication flag occupies a part of indication bits of the source address or the flow label field.

21. The method of claim 19, wherein the network slice identification option further comprises: an option type, an option data field length, and the slice identifier.

22. The method of any one of claims 14 to 21, wherein the method further comprises:

23. The method according to claim 22, wherein when the resource indicator includes a discard flag and a resource allocation flag, the performing the processing on the packet according to the value indicated by the resource indicator includes:

24. A network node, wherein the network node is a packet sending node, comprising: a transceiver, wherein the transceiver is configured to:

sending a message to the SRv6 strategy path;

25. A network node, wherein the network node is a packet receiving node, comprising: a transceiver, wherein the transceiver is configured to:

receiving a message on an SRv6 strategy path;

26. A resource allocation apparatus, applied to a packet sending node, includes:

27. A resource allocation device, applied to a message receiving node, includes:

28. A network node, comprising: a processor, a memory and a program stored on the memory and executable on the processor, the program, when executed by the processor, implementing the resource allocation method of any one of claims 1 to 13 or implementing the resource allocation method of any one of claims 14 to 23.

29. A readable storage medium, characterized in that the readable storage medium has stored thereon a program which, when being executed by a processor, carries out the steps in the resource allocation method according to any one of claims 1 to 13, or carries out the steps in the resource allocation method according to any one of claims 14 to 23.