Message forwarding method and device, equipment and storage medium

Abstract

The invention provides a message forwarding method and device, equipment and a storage medium. The method comprises the following steps: responding to a message transmission main line fault, and obtaining at least one candidate network slice with a preset bandwidth between a node and an adjacent node; according to an initial network slice identifier of a main line in a message header of the message, determining a target network slice used when the message is transmitted on a standby line in the candidate network slices; and forwarding the message according to the message header and the target network slice. The method provided by the invention is wide in bandwidth resource.

Description

Technical Field

[0001] The present application relates to the field of data forwarding technology, and in particular to a message forwarding method, apparatus, device and storage medium. Background Art

[0002] SRv6 network slicing can divide the physical network into the required logical slice networks. Messages are transmitted in the network slice of the message transmission line by carrying the slice ID in the message. When the main line fails, it will trigger the topology independent loop free alternate (TI-LFA) escape protection, that is, the message can be transmitted through the backup line to ensure that the message can be forwarded smoothly.

[0003] In existing technologies, to ensure that packets can be forwarded through network slices even on backup lines, network slices related to the service data carried by the packets must be pre-configured on the TI-LFA path. These pre-configured network slices require bandwidth resources and can only transmit packets for the corresponding services, not for other services. This wastes bandwidth resources when the primary line is operating normally. Summary of the Invention

[0004] The present application provides a message forwarding method, apparatus, device and storage medium to solve the technical problem of bandwidth resource waste.

[0005] In a first aspect, the present application provides a message forwarding method, applied to a node of a backup line, comprising:

[0006] In response to a failure in a main message transmission line, obtaining at least one candidate network slice of a preset bandwidth between the node and its adjacent node;

[0007] Determining, in the candidate network slices according to a header of the message, a target network slice used when the message is transmitted on the backup line;

[0008] The message is forwarded using the target network slice.

[0009] Optionally, in the method above, the forwarding the message using the target network slice includes:

[0010] If the node is the starting node of the backup line, the target HBH extension header corresponding to the target network slice and the target SRH of the backup line are added to the message header, and the updated message is sent to the next node in the target network slice;

[0011] If the node is an intermediate node of the backup line, sending the received updated message to the next node in the target network slice;

[0012] If the node is the end node of the backup line, the target HBH extension header and the target SRH are stripped from the message header, and the message is sent to the next node in the initial network slice.

[0013] Optionally, in the method described above, obtaining at least one candidate network slice of a preset bandwidth between the node and its neighboring node includes:

[0014] Receive candidate network slices of at least one preset bandwidth sent by the controller.

[0015] Optionally, in the method described above, obtaining at least one candidate network slice of a preset bandwidth between the target node and the reference node includes:

[0016] receiving slice configuration information sent by the controller;

[0017] Based on the slice configuration information, establish a candidate network slice with at least one preset bandwidth between its adjacent nodes.

[0018] Optionally, in the method described above, the node is the starting node of the backup line, and determining, in the candidate network slices according to the message header of the message, a target network slice used when the message is transmitted on the backup line includes:

[0019] According to the initial network slice identifier of the main line in the message header of the message, the target network slice used when the message is transmitted on the backup line is determined in the candidate network slices.

[0020] Optionally, the method as described above further includes:

[0021] Receive a network slice mapping table sent by the controller, where the network slice mapping table is used to indicate the mapping relationship between the initial network slice and the candidate network slice.

[0022] Optionally, in the method described above, the node is the starting node of the backup line, and the message header includes the initial network slice of the main line for transmitting the message;

[0023] Determining, from the candidate network slices, a target network slice used when the message is transmitted on the backup line, according to an initial network slice identifier of the primary line in a message header of the message, includes:

[0024] According to the network slice mapping table, the candidate network slice corresponding to the initial network slice identifier is determined as the target network slice.

[0025] Optionally, the above method further includes:

[0026] In response to the completion of the message transmission, the bandwidth corresponding to the target network slice is released.

[0027] In a second aspect, a message forwarding method is applied to a controller, comprising:

[0028] In response to a failure of a primary message transmission line, generating at least one candidate network slice of a preset bandwidth between each node in the backup line and its adjacent node;

[0029] The candidate network slice is sent to each node in the backup line.

[0030] In a third aspect, the present application provides a message forwarding device, which is applied to a target node device of a backup line, comprising:

[0031] an acquisition module, configured to acquire, in response to a failure in a main message transmission line, at least one candidate network slice of a preset bandwidth between the node and its adjacent nodes;

[0032] a determination module, configured to determine, from the candidate network slices, a target network slice used when the message is transmitted on the backup line, based on an initial network slice identifier of the primary line in a message header of the message;

[0033] A forwarding module is used to forward the message using the target network slice.

[0034] In a fourth aspect, the present application provides an electronic device, comprising: a processor, and a memory communicatively connected to the processor;

[0035] The memory stores computer-executable instructions;

[0036] The processor executes the computer-executable instructions stored in the memory to implement the method as described in any one of the first aspects.

[0037] In a fifth aspect, the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are executed by a processor, they are used to implement the method as described in any one of the first aspects.

[0038] The message forwarding method provided in the present application obtains at least one candidate network slice of a preset bandwidth between a node and its adjacent nodes in response to a failure in the main line of message transmission; determines the target network slice used when the message is transmitted on the backup line in the candidate network slice according to the initial network slice identifier of the main line in the message header; and forwards the message according to the message header and the target network slice. Compared with the existing technology, when a failure occurs in the main line of message transmission, the candidate network slice is directly obtained, which is irrelevant to the business data in the message. When obtaining the target network slice in the candidate network slice, it is obtained based on the initial network slice identifier of the main line in the message header. It is not necessary to use business-related information to complete message forwarding in the backup line through the network slice, and the target network slice is irrelevant to the business information of the message, that is, one target network slice can be used for messages of different services, and there is no need to configure different network slices for messages of different services, thus saving bandwidth resources. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0040] Figure 1 Schematic diagram of setting up network slices between nodes;

[0041] Figure 2 Data flow diagram for triggering the backup line;

[0042] Figure 3 Schematic diagram of bandwidth provisioning for network slicing;

[0043] Figure 4 A schematic diagram of a message forwarding method in an exemplary embodiment of the present application;

[0044] Figure 5 This is a flowchart of another message forwarding method in an exemplary embodiment of the present application;

[0045] Figure 6 It is a data flow diagram for the transmission of messages through the backup line;

[0046] Figure 7 A network slice mapping diagram between the initial network slice identifier and the candidate network slices;

[0047] Figure 8 This is a schematic diagram of another message forwarding method in an exemplary embodiment of the present application;

[0048] Figure 9 is a flow chart of a message forwarding method applied to a controller;

[0049] Figure 10This is a schematic diagram of the composition of a message forwarding device in an exemplary embodiment of the present application;

[0050] Figure 11 Schematic diagram of an electronic device to which an embodiment of the present application can be applied.

[0051] The above drawings illustrate specific embodiments of the present application, which will be described in more detail below. These drawings and the textual description are not intended to limit the scope of the present application in any way, but rather to illustrate the concepts of the present application to those skilled in the art by reference to specific embodiments. DETAILED DESCRIPTION

[0052] Exemplary embodiments will be described in detail herein, with examples illustrated in the accompanying drawings. In the following description, when referring to the drawings, identical numerals in different figures represent identical or similar elements, unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.

[0053] With the emergence of diverse new services in the 5G and cloud era, different industries, businesses, and users are placing diverse quality of service (QoS) requirements on networks. For example, services such as mobile communications, smart homes, environmental monitoring, smart agriculture, and smart metering require networks to support massive device connections and the frequent transmission of large numbers of small messages. Services such as live streaming, video backhaul, and mobile healthcare place even higher demands on transmission rates. Services such as the Internet of Vehicles, smart grids, and industrial control require millisecond-level latency and near-100% reliability. Therefore, 5G networks must offer massive access, deterministic latency, and extremely high reliability, requiring a flexible and dynamic network to meet the diverse business needs of users and vertical industries.

[0054] In response to the above needs, SRv6 network slicing technology came into being. Through network slicing, multiple dedicated, virtualized, and isolated logical networks can be built on a common physical network to meet the differentiated requirements of different users for network capabilities.

[0055] SRv6 network slicing is one of the key technologies of the fifth generation of mobile communications (5G). It can implement diversion management of network data similar to traffic management. Its essence is to logically divide the existing physical network into multiple different types of virtual networks. According to the service needs of different users, the division is based on indicators such as latency, bandwidth, and reliability, so as to cope with complex and changing application scenarios.

[0056] The transmission path of a message may include multiple nodes. Figure 1 A schematic diagram of setting up network slices between nodes, such as Figure 1 As shown, the data channels between interconnected node devices can be network sliced, and the message is transmitted in the network slice of the message transmission line by carrying the slice ID in the message. For example, the message includes a message header and payload data. The message header may include the Internet Protocol Version 6 (IPv6) address, hop-by-hop extension header, segment routing extension header (SRH), etc.

[0057] The message transmission line can include various nodes. When the main message transmission line fails, the topology independent loop free alternate (TI-LFA) escape line, that is, the backup line, will be triggered. For example, Figure 2 The data flow diagram for triggering the backup line is as follows: Figure 2 As shown in the figure, when nodes P1 and P2 fail, a backup route, P1-P3-P2, can be used. To ensure service bandwidth by still using network slicing on P1-P3-P2, it is necessary to pre-configure a slice interface corresponding to Slice ID1 at the TI-LFA routing egress and reserve bandwidth. This requires service slice awareness on TI-LFA for configuration, which results in strong coupling with the service. For each new service slice, service slice information must also be deployed on all TI-LFA paths. Figure 3 Schematic diagram of bandwidth configuration for network slices, such as Figure 3 As shown, different services require different bandwidths to be configured for packet forwarding.

[0058] However, only in failure scenarios will traffic trigger the escape route along the TI-LFA path, which is the backup route. Under normal circumstances, slice service traffic will not use the backup route. If a large number of slice instances and slice interfaces for services are deployed in advance, interface bandwidth resources will be wasted because slice interface resources are strongly reserved.

[0059] After consideration, the inventors found that if, when a message transmission line failure is discovered, the process of configuring network slices between backup lines is not coupled with the business, one network slice can complete the forwarding of messages for multiple services, and there is no need to configure a corresponding network slice for each business. That is, a public network slice can be configured for the transmission of messages for different services, which can solve the problem of bandwidth resource waste.

[0060] Based on this, the message forwarding method provided in this application is intended to solve the above technical problems of the prior art.

[0061] The following specific embodiments describe in detail the technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0062] Figure 4 This is a schematic diagram of a message forwarding method in an example implementation of the present application. The message forwarding method of the present application is applied to a node in a backup line, such as Figure 4 As shown, the message forwarding method may include steps S410 to S430.

[0063] S410, in response to a failure in a main message transmission line, obtaining a candidate network slice of at least one preset bandwidth between a node and its adjacent node.

[0064] In an exemplary embodiment of the present application, a main line failure means that the main line cannot transmit messages. This may be caused by a disconnection of a connecting line in the main line or a node failure in the main line, which prevents message transmission. This application does not limit the specific form of the above failure.

[0065] In this example implementation, the above-mentioned node is a device capable of forwarding messages, such as a routing forwarding device, and the above-mentioned node is not specifically limited in this example implementation.

[0066] When a main line failure is detected, a backup line can be enabled. The backup line includes multiple nodes. After the backup line is started, a candidate network slice with at least one preset bandwidth between the node and its adjacent node can be obtained, where the adjacent node is a node adjacent to and directly connected to the node.

[0067] In this example implementation, any of the candidate network slices can support the transmission of messages of at least one service type. The specific value of the preset bandwidth can be customized according to user needs. For example, the preset bandwidth is 10M, 20M, etc., which is not specifically limited in this example implementation.

[0068] S420, based on the initial network slice identifier of the main line in the message header of the message, determine the target network slice used when the message is transmitted on the backup line in the candidate network slices.

[0069] In an example implementation of the present application, an initial network slice identifier may be set in the message header of the message. The specific form of the initial network slice identifier may be customized according to user needs and is not specifically limited in this example implementation. For example, the above-mentioned initial network port slice identifier may be SliceID1, SliceID2, etc., an initial HBH extension header.

[0070] After obtaining the above-mentioned initial network slice identifier, the target network slice identifier can be determined from the above-mentioned candidate network slice identifiers. Specifically, the target network slice corresponds to the above-mentioned initial network slice.

[0071] In an example implementation, the target network slice may correspond to multiple initial network slice identifiers, which may correspond to messages of different service types.

[0072] S430: Forward the message according to the message header and the target network slice.

[0073] In this example implementation, after obtaining the above-mentioned target network slice, the above-mentioned message can be forwarded using the above-mentioned target network slice.

[0074] The message forwarding method in the present application obtains at least one candidate network slice of a preset bandwidth between a node and its adjacent nodes in response to a failure in the main line of message transmission; determines the target network slice used when the message is transmitted on the backup line in the candidate network slice according to the initial network slice identifier of the main line in the message header; and forwards the message using the target network slice. Compared with the existing technology, when a failure occurs in the main line of message transmission, the candidate network slice is directly obtained, which is irrelevant to the business data in the message. When obtaining the target network slice in the candidate network slice, it is obtained based on the initial network slice identifier of the main line in the message header. There is no need to use business-related information, and message forwarding can be completed in the backup line through the network slice. The target network slice is irrelevant to the business information of the message, that is, one target network slice can be used for messages of different services, and there is no need to configure different network slices for messages of different services, thus saving bandwidth resources.

[0075] In an exemplary embodiment of the present application, the above-mentioned node may be a starting node, an intermediate node or an end node. Specifically, Figure 5 This is a flow chart of another message forwarding method in an example implementation manner of this application, such as Figure 5 As shown, when forwarding a message using the target network slice, steps S510 to S530 may be included.

[0076] S510: Determine whether the node is a starting node of a backup line.

[0077] In this example implementation, if the node is the starting node of the backup line, step S520 is executed; if not, step S530 is executed.

[0078] S520, add the target HBH extension header corresponding to the target network slice and the target SRH of the backup line to the message header, and send the updated message to the next node in the target network slice.

[0079] In this example implementation, the above-mentioned target network slice is configured with a target HBH extension header. The specific form of the target HBH extension header can be customized according to user needs. For example, the target HBH extension header can be SliceID100, SliceID200, etc., which is not specifically limited in this example implementation.

[0080] After obtaining the target HBH extension header of the target network slice, the target HBH extension header can be added to the message header of the message. The specific location of the target HBH extension header in the message header is not specifically limited in this embodiment. The target HBH extension header is SliceID100 as an example for explanation. Figure 6 This is the data flow diagram for the message transmission through the backup line, such as Figure 6 As shown, a main line failure occurs between node P1 and node P2, triggering the backup line P1-P3-P2, where P1 is the starting node. The message may include an initial HBH extension header. If the above-mentioned node is the starting node, that is, node P1, at this time, the target HBH extension header can be added to the message header and the above-mentioned initial HBH extension header is updated. Specifically, the initial HBH extension header SliceID1 is updated to SliceID1, SliceID100.

[0081] In this exemplary embodiment, the starting node can obtain the target SRH extension header of the backup line. When the backup route is determined, the starting node can obtain the target SRH extension header and add the target SRH extension header of the backup line to the message header of the message. Figure 6 As shown, the starting node of the backup line is P1, and the target SRH extension header of the backup line is (P3, P2). The starting node P1 can add the target SRH extension header (P3, P2) of the backup line to the message header.

[0082] After updating the message header, the message can be transmitted to the next node, i.e., the P3 node, through the target network slice corresponding to the target HBH extension header SliceID100 according to the target SRH extension header (P3, P2) of the backup line.

[0083] S530: Determine whether the node is an intermediate node of the backup line.

[0084] In this example implementation, if the node is an intermediate node of the backup line, step S540 is executed; if not, it indicates that the node is a midpoint node, and step S550 is executed.

[0085] S540, sending the received updated message to the next node in the target network slice.

[0086] In this example embodiment, if the node is an intermediate node, the updated message is sent to the next node of the target network slice based on the message header. For example, if the HBH extension header included in the message header of the updated message is SliceID1 and SliceID100, the message can be transmitted to the next node using SliceID100 corresponding to the target network slice.

[0087] It should be noted that the HBH extension header is modified by the above-mentioned starting node, and the subsequent transmission of the message can be completed based on the HBH extension header.

[0088] S550, the target HBH extension header and the target SRH are stripped from the message header, and the message is sent to the next node in the initial network slice.

[0089] In this example implementation, if the node is a terminal node, the terminal node can remove the target HBH extension header and the target SRH from the message header, so that the message can continue to be forwarded according to the main line that has not failed. Figure 6 As shown, the terminal node of the backup line is P2, and the target HBH extension header in the message header and the target SRH extension header of the backup line can be stripped off by the terminal node P2, that is, SliceID100 and the target SRH extension header (P3, P2) can be stripped off and sent to the next node of the initial network slice.

[0090] Specifically, such as Figure 6 As shown, the message header sent by the terminal node P2 only includes the initial SRH extension header and the initial HBH extension header of the initial line, that is, P2 can send the message to the next node PE4 of the initial line according to the initial SRH extension header and the initial HBH extension header of the initial line.

[0091] It should be noted that in the above steps, the order of determining whether a node is an intermediate node, a starting node, and an end node can be customized according to user needs. For example, the order of determining whether a node is an end node can be determined first, and then whether it is a starting node; or the order of determining whether a node is an intermediate node can be determined first, and then whether it is a starting node. This is not specifically limited in this example embodiment.

[0092] In one exemplary embodiment of the present application, when a primary message transmission line fails, the starting node of the backup line sends the backup line's topology information, i.e., detailed node connection information, to a controller. The controller then generates, based on this backup line's topology information, at least one candidate network slice with a preset bandwidth between each node on the backup line and its adjacent nodes, and sends the candidate network slice to each node on the backup line.

[0093] In another example implementation, when a primary message transmission line fails, the starting node of the backup line sends the backup line's topology information, i.e., detailed node connection information, to the controller. The controller then generates slice configuration information based on the backup line's topology information and sends this slice configuration information to each node, which then generates the candidate network slices.

[0094] In an example implementation, if the node is a starting node, the starting node will also receive a network slice mapping table sent by the above-mentioned controller, where the network slice mapping table is used to indicate the mapping relationship between the initial network slice identifier and the candidate network slice.

[0095] For example, Figure 7 A network slice mapping diagram between the initial network slice identifier and the candidate network slice. Optionally, a candidate network slice can correspond to one or more initial network slice identifiers, that is, the candidate network slice can transmit messages of different data types, which can reduce the waste of bandwidth resources.

[0096] like Figure 7 As shown, the initial network slice identifiers corresponding to the candidate network slice SliceID100 (TI-LFA) include SliceID1, SliceID2, and SliceID3, and the initial network slice identifiers corresponding to the candidate network slice SliceID200 (TI-LFA) include SliceID4, SliceID5, and SliceID6. In this example implementation, there is no specific limitation on the number of initial network slice identifiers corresponding to the above-mentioned candidate network slices.

[0097] In an example implementation of the present application, the starting node can determine the target network slice from the candidate network slices according to the initial network slice identifier of the main line in the message header. Specifically, the target network slice identifier corresponding to the initial network slice identifier is used as the target network slice. For example, Figure 7As shown, if the initial network slice is identified as SliceID1, the corresponding target network slice is SliceID100 (TI-LFA); if the initial network slice is identified as SliceID5, the corresponding target network slice is SliceID200 (TI-LFA). The specific method for obtaining the target network slice can be customized according to user needs and is not specifically limited in this embodiment.

[0098] In an example implementation of the present application, after detecting that the transmission of the above-mentioned message is completed, the bandwidth corresponding to the above-mentioned target network slice is released, so that other lines in the backup line can use the bandwidth, thereby improving the utilization rate of bandwidth resources and improving the data forwarding efficiency of the backup line.

[0099] Figure 8 This is a schematic diagram of another message forwarding method in an exemplary embodiment of the present application. When forwarding a message, if the main message transmission line fails, the method may include the following steps:

[0100] S810, the starting node receives the candidate network slice and the network slice mapping table, and the intermediate node and the end node receive the candidate network slice.

[0101] S820, the starting node determines the candidate network slice corresponding to the initial network slice identifier as the target network slice according to the network slice mapping table.

[0102] S830, the starting node adds the target HBH extension header corresponding to the target network slice and the target SRH of the backup line to the message header, and uses the target network slice to transmit the message to the intermediate node.

[0103] S840, the intermediate node determines the target network slice among the candidate network slices based on the message header, and uses the target network slice to transmit the message to the terminal node.

[0104] S850: The destination node strips the target HBH extension header and the target SRH from the message header.

[0105] It should be noted that the specific contents of steps S810 to S850 have been described in detail above and will not be repeated here.

[0106] In response to a failure in the main line for message transmission, a candidate network slice of at least one preset bandwidth between a node and its adjacent nodes is obtained; based on the initial network slice identifier of the main line in the message header, the target network slice used when the message is transmitted on the backup line is determined in the candidate network slice; and the message is forwarded using the target network slice. Compared with the existing technology, when a failure occurs in the main line for message transmission, the candidate network slice is directly obtained, which is irrelevant to the business data in the message. When obtaining the target network slice in the candidate network slice, it is obtained based on the initial network slice identifier of the main line in the message header. No business-related information is required, and message forwarding can be completed through the network slice in the backup line. The target network slice is irrelevant to the business information of the message, that is, one target network slice can be used for messages of different services, and there is no need to configure different network slices for messages of different services, thereby saving bandwidth resources. Furthermore, after the end node completes the transmission, the target HBH extension header corresponding to the target network slice is stripped off so that it does not affect the normal transmission of the main line for message transmission. Furthermore, after detecting that the above-mentioned message transmission is completed, the bandwidth corresponding to the above-mentioned target network slice is released, so that other lines in the backup line can use the bandwidth, thereby improving the utilization rate of bandwidth resources and improving the data forwarding efficiency of the backup line.

[0107] It should be noted that for the aforementioned method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that this application is not limited by the order of the actions described, because according to this application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in this specification are all optional embodiments, and the actions and modules involved are not necessarily required by this application.

[0108] It should be further noted that, although the various steps in the flowchart are shown in sequence as indicated by the arrows, these steps are not necessarily performed in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and these steps may be performed in other orders. Moreover, at least a portion of the steps in the flowchart may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily performed at the same time, but may be performed at different times. The execution order of these sub-steps or stages is not necessarily to be performed in sequence, but may be performed in turn or alternately with other steps or at least a portion of the sub-steps or stages of other steps.

[0109] Figure 9 Flowchart of a message forwarding method applied to a controller, which may include the following steps:

[0110] S910, in response to a failure of a primary message transmission line, generating at least one candidate network slice of a preset bandwidth between each node in a backup line and its adjacent node;

[0111] S910, sending the candidate network slice to each node in the backup line.

[0112] In this example embodiment, the candidate network slice is sent to each node in the backup line so that the nodes in the backup line determine the target network slice used when the message is transmitted on the backup line in the candidate network slice, and complete the message forwarding based on the target slice.

[0113] It should be noted that the specific details of the above steps can be referred to the message forwarding method applied to the node of the backup line, and will not be described in detail here.

[0114] Figure 10 The present application provides a message forwarding device 1000, which is applied to a target node device of a backup line. The device includes an acquisition module 1010, a determination module 1020, and a forwarding module 1030, wherein:

[0115] The acquisition module 1010 can be used to respond to a failure in the main line of message transmission and obtain a candidate network slice of at least one preset bandwidth between a node and its adjacent nodes.

[0116] The determination module 1020 can be used to determine the target network slice used when the message is transmitted on the backup line in the candidate network slices based on the message header of the message.

[0117] The forwarding module 1030 can be used to forward the message according to the message header and the target network slice.

[0118] In an example embodiment, the forwarding module 1030 is configured to add the target HBH extension header corresponding to the target network slice and the target SRH of the backup line to the message header if the node is the starting node of the backup line, and send the updated message to the next node in the target network slice; if the node is the intermediate node of the backup line, send the received updated message to the next node in the target network slice; if the node is the end node of the backup line, strip the target HBH extension header and the target SRH from the message header, and send the message to the next node in the initial network slice of the transmission main line.

[0119] In an example embodiment, the acquisition module 1010 can be used to receive at least one candidate network slice of a preset bandwidth sent by the controller.

[0120] In an example embodiment, the acquisition module 1010 can be used to receive slice configuration information sent by the controller; and establish a candidate network slice with at least one preset bandwidth between its adjacent nodes based on the slice configuration information.

[0121] In an example embodiment, the node is the starting node of the backup line, and the determination module 1020 can be used to determine the target network slice used when the message is transmitted on the backup line in the candidate network slices based on the initial network slice identifier of the main line in the message header.

[0122] In an example embodiment, when the node is the starting node of a backup line, the acquisition module 1010 can also receive a network slice mapping table sent by the controller, where the network slice mapping table is used to indicate the mapping relationship between the initial network slice identifier and the candidate network slice.

[0123] In an example embodiment, the determination module 1020 can be used to determine the candidate network slice corresponding to the initial network slice identifier as the target network slice according to the network slice mapping table.

[0124] In an example embodiment, the message forwarding device 1000 can also be used to release the bandwidth corresponding to the target network slice in response to the completion of message transmission.

[0125] It should be understood that the above-described device embodiments are merely illustrative, and the device of the present application may also be implemented in other ways. For example, the division of units / modules in the above-described embodiments is merely a logical functional division, and actual implementations may employ other division methods. For example, multiple units, modules, or components may be combined or integrated into another system, or some features may be omitted or not implemented.

[0126] In addition, unless otherwise specified, the functional units / modules in the various embodiments of the present application may be integrated into a single unit / module, each unit / module may exist physically separately, or two or more units / modules may be integrated together. The aforementioned integrated units / modules may be implemented in the form of hardware or software program modules.

[0127] If the integrated unit / module is implemented in hardware, the hardware may be digital circuits, analog circuits, etc. The physical implementation of the hardware structure includes, but is not limited to, transistors, memristors, etc. Unless otherwise specified, the processor may be any appropriate hardware processor, such as a CPU, GPU, FPGA, DSP, and ASIC. Unless otherwise specified, the storage unit may be any appropriate magnetic storage medium or magneto-optical storage medium, such as resistive random access memory (RRAM), dynamic random access memory (DRAM), static random access memory (SRAM), enhanced dynamic random access memory (EDRAM), high-bandwidth memory (HBM), hybrid memory cube (HMC), etc.

[0128] If the integrated unit / module is implemented in the form of a software program module and sold or used as an independent product, it can be stored in a computer-readable memory. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, which is stored in a memory and includes a number of instructions for enabling a computer device (which can be a personal computer, server or network device, etc.) to execute all or part of the steps of the various embodiments of the present application. The aforementioned memory includes various media that can store program codes, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk.

[0129] Figure 11 This is a schematic diagram of the structure of an electronic device 1100 provided in this application. Figure 11 As shown, the electronic device 1100 may include: at least one processor 1110 , a memory 1120 , and a communication interface 1130 .

[0130] The memory 1120 is used to store programs. Specifically, the programs may include program codes, and the program codes include computer operation instructions.

[0131] The memory 1120 may include a high-speed RAM memory, and may also include a non-volatile memory (non-volatile memory), such as at least one disk memory.

[0132] The processor 1110 is configured to execute computer-executable instructions stored in the memory 1120 to implement the monitoring method described in the aforementioned method embodiment. The processor 1110 may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application.

[0133] The electronic device 1100 may also include a communication interface 1130, so that it can communicate and interact with external devices through the communication interface 1130. In a specific implementation, if the communication interface 1130, the memory 1120, and the processor 1110 are implemented independently, the communication interface 1130, the memory 1120, and the processor 1110 can be interconnected via a bus to achieve mutual communication. The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus. Buses can be divided into address buses, data buses, control buses, etc., but this does not mean that there is only one bus or one type of bus.

[0134] Optionally, in a specific implementation, if the communication interface 1130, the memory 1120 and the processor 1110 are integrated on a chip, the communication interface 1130, the memory 1120 and the processor 1110 can complete communication through an internal interface.

[0135] The present application also provides a computer-readable storage medium, which may include: a USB flash drive, a mobile hard disk, a read-only memory random access memory, a disk or an optical disk, and other media that can store program codes. Specifically, the computer-readable storage medium stores program instructions, which are used for the monitoring method in the above embodiment.

[0136] In the above embodiments, the description of each embodiment has its own focus. For parts not described in detail in a certain embodiment, please refer to the relevant description of other embodiments. The technical features of the above embodiments can be combined arbitrarily. In order to make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0137] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the present application that follow the general principles of the present application and include common knowledge or customary techniques in the art not disclosed herein. The description and examples are to be considered as exemplary only, and the true scope and spirit of the present application are indicated by the following claims.

[0138] It should be understood that the present application is not limited to the exact structure described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

[0139] It should be understood that the above-described device embodiments are merely illustrative, and the device of the present application may also be implemented in other ways. For example, the division of units / modules in the above-described embodiments is merely a logical functional division, and actual implementations may employ other division methods. For example, multiple units, modules, or components may be combined or integrated into another system, or some features may be omitted or not implemented.

[0140] In addition, unless otherwise specified, the functional units / modules in the various embodiments of the present application may be integrated into a single unit / module, each unit / module may exist physically separately, or two or more units / modules may be integrated together. The aforementioned integrated units / modules may be implemented in the form of hardware or software program modules.

[0141] If the integrated unit / module is implemented in hardware, the hardware may be digital circuits, analog circuits, etc. The physical implementation of the hardware structure includes, but is not limited to, transistors, memristors, etc. Unless otherwise specified, the processor may be any appropriate hardware processor, such as a CPU, GPU, FPGA, DSP, and ASIC. Unless otherwise specified, the storage unit may be any appropriate magnetic storage medium or magneto-optical storage medium, such as resistive random access memory (RRAM), dynamic random access memory (DRAM), static random access memory (SRAM), enhanced dynamic random access memory (EDRAM), high-bandwidth memory (HBM), hybrid memory cube (HMC), etc.

[0142] If the integrated unit / module is implemented in the form of a software program module and sold or used as an independent product, it can be stored in a computer-readable memory. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, which is stored in a memory and includes a number of instructions for enabling a computer device (which can be a personal computer, server or network device, etc.) to execute all or part of the steps of the various embodiments of the present application. The aforementioned memory includes various media that can store program codes, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk.

[0143] In the above embodiments, the description of each embodiment has its own emphasis. For parts not described in detail in a particular embodiment, please refer to the relevant description of other embodiments. The technical features of the above embodiments can be combined in any way. To keep the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0144] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the present application that follow the general principles of the present application and include common knowledge or customary techniques in the art not disclosed herein. The description and examples are to be considered as exemplary only, and the true scope and spirit of the present application are indicated by the following claims.

[0145] It should be understood that the present application is not limited to the exact structure described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

Claims

1. A message forwarding method, characterized in that: Applied to a node of a backup line, the method comprises: In response to a failure in a main message transmission line, obtaining at least one candidate network slice of a preset bandwidth between the node and its adjacent node; Determine, in the candidate network slices, a target network slice used when the message is transmitted on the backup line according to a message header of the message; The message is forwarded according to the message header and the target network slice.

2. The method according to claim 1, characterized in that The forwarding the message according to the message header and the target network slice includes: If the node is the starting node of the backup line, the target Hop-By-Hop (HBH) extension header corresponding to the target network slice and the target Segment Routing Header (SRH) extension header of the backup line are added to the message header, and the updated message is sent to the next node in the target network slice; If the node is an intermediate node of the backup line, sending the received updated message to the next node in the target network slice; If the node is the end node of the backup line, the target HBH extension header and the target SRH are stripped from the message header, and the message is sent to the next node in the initial network slice of the transmission main line.

3. The method according to claim 1, characterized in that The obtaining of at least one candidate network slice of a preset bandwidth between the node and its neighboring node includes: Receive candidate network slices of at least one preset bandwidth sent by the controller.

4. The method according to claim 1, characterized in that: The obtaining of at least one candidate network slice of a preset bandwidth between the target node and the reference node includes: Receive slice configuration information sent by the controller; Based on the slice configuration information, establish a candidate network slice with at least one preset bandwidth between its adjacent nodes.

5. The method according to claim 3 or 4, characterized in that: The node is a starting node of the backup line, and determining, in the candidate network slices according to the message header of the message, a target network slice used when the message is transmitted on the backup line, includes: According to the initial network slice identifier of the main line in the message header of the message, the target network slice used when the message is transmitted on the backup line is determined in the candidate network slices.

6. The method according to claim 5, characterized in that The method further comprises: Receive a network slice mapping table sent by a controller, where the network slice mapping table is used to indicate a mapping relationship between the initial network slice identifier and the candidate network slice; The node is the starting node of the backup line, and the message header includes the initial network slice of the main line for transmitting the message; The determining, according to the initial network slice identifier of the primary line in the message header of the message, a target network slice used when the message is transmitted on the backup line from among the candidate network slices, comprises: According to the network slice mapping table, the candidate network slice corresponding to the initial network slice identifier is determined as the target network slice.

7. A message forwarding method, characterized in that: Applied to a controller, the method comprises: In response to a failure of a main message transmission line, generating a candidate network slice of at least one preset bandwidth between each node in the backup line and its adjacent node; The candidate network slice is sent to each node in the backup line, so that the nodes in the backup line determine the target network slice used when the message is transmitted on the backup line in the candidate network slice, and complete message forwarding based on the target slice.

8. A message forwarding device, applied to a target node device of a backup line, characterized in that: include: An acquisition module, configured to acquire, in response to a failure in a main message transmission line, a candidate network slice of at least one preset bandwidth between the node and its adjacent nodes; A determination module, used to determine, in the candidate network slices according to a header of the message, a target network slice used when the message is transmitted on the backup line; A forwarding module is used to forward the message according to the message header and the target network slice.

9. An electronic device, characterized in that: include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory to implement the method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, which are used to implement the method according to any one of claims 1 to 7 when executed by a processor.

Images