Method for processing SRv6 message and gateway equipment

Abstract

The invention provides a method for processing an SRv6 message and gateway equipment, and the method comprises the steps: receiving a first message from a Client connected with an SRv6 tail node, matching the routing information of the first message with an SRv6 forwarding table, obtaining the target routing information matched with the routing information of the first message, and the address information of a target SRv6 head node corresponding to the target routing information, and packaging and sending the first message according to the target routing information and the address information of the target SRv6 head node. Through the method, uplink and downlink flow paths can be unified.

Description

Technical Field

[0001] The present invention relates to the field of communication technology, and in particular to a method and a gateway device for processing SRv6 messages. Background Art

[0002] SR (Segment Routing) uses the head node path selection mechanism, which pre-encapsulates the SID (Segment Identifier) ​​of the segment that the path will pass through in the head node. When the message passes through the SR node, the node forwards the message according to the SID of the message. Except for the head node, other nodes do not need to maintain the path status.

[0003] SRv6 refers to the use of SR in an IPv6 network, using IPv6 addresses as SIDs to forward packets.

[0004] like Figure 1 As shown in the figure, in the SRv6 networking dual-gateway scenario, Client1 has two gateways, Gateway 1 and Gateway 2, and the server's gateway is Gateway 3. The upstream traffic from Client1 to Server is encapsulated through the SRv6 tunnel by Gateway 1 or Gateway 2 and sent to Gateway 3, which is then decapsulated and sent to Server. The downstream traffic from Server to Client1 is encapsulated through the SRv6 tunnel by Gateway 3 and sent to Gateway 1 or Gateway 2, which is then decapsulated and sent to Client1. At this point, the upstream traffic from Client1 to Server may go through Gateway 1, and the downstream traffic from Server to Client1 may go through Gateway 2, resulting in inconsistent upstream and downstream traffic paths, which may cause other problems such as traffic blockage. Summary of the invention

[0005] To overcome the problems existing in the related art, this specification provides a method and a gateway device for processing SRv6 messages.

[0006] According to a first aspect of an embodiment of this specification, a method for processing an SRv6 message is provided, the method being applied to an SRv6 tail node, the method comprising:

[0007] Receive a first message from a Client connected to the SRv6 egress node;

[0008] Matching the routing information of the first message with the SRv6 forwarding table, wherein the SRv6 forwarding table includes a correspondence between the routing information of each message and the address information of the SRv6 head node that sends each message;

[0009] Acquire target routing information matching the routing information of the first message, and address information of the target SRv6 head node corresponding to the target routing information;

[0010] The first message is encapsulated and sent according to the target routing information and the address information of the target SRv6 head node.

[0011] Wherein, the method further comprises:

[0012] Receive a second message sent by each SRv6 head node, where the second message carries source address information of the SRv6 head node that sends the second message;

[0013] Obtain the routing information of the second message and the corresponding source address information of the SRv6 head node and generate an SRv6 forwarding table.

[0014] The routing information includes quintuple information.

[0015] Wherein, the method further comprises:

[0016] Receive a request message sent by a client connected to an SRv6 egress node, where the request message is sent when the client recognizes that the connected SRv6 egress node is not unique;

[0017] According to the request information of the Client, the SRv6 forwarding table is sent to the Client, so that the Client sends the first message according to the SRv6 tail node of the SRv6 forwarding table entry.

[0018] It can be seen from the above embodiments that when SRv6, as the tail node, sends a message to the SRv6 head node, it can encapsulate the first message according to the SRv6 forwarding table to ensure the consistency of the upstream and downstream traffic paths, thereby avoiding the problems of inconsistent upstream and downstream traffic paths, resulting in traffic blockage, etc.

[0019] According to a second aspect of an embodiment of this specification, a method for processing an SRv6 message is provided, the method being applied to an SRv6 head node, the method comprising:

[0020] Receive a second message from a Client connected to the SRv6 head node;

[0021] Matching the routing information of the second message with the SRv6 forwarding table, wherein the SRv6 forwarding table includes a correspondence between the routing information of each message and the address information of the SRv6 tail node that sends each message;

[0022] Obtain target routing information that matches the routing information of the second message, and address information of the target SRv6 tail node corresponding to the target routing information;

[0023] The second message is encapsulated according to the target routing information and the address information of the target SRv6 tail node and sent.

[0024] Wherein, the method further comprises:

[0025] Receive a second message sent by each SRv6 head node, where the second message carries source address information of the SRv6 head node that sends the second message;

[0026] Obtain the routing information of the second message and the corresponding source address information of the SRv6 head node and generate an SRv6 forwarding table.

[0027] It can be seen from the above embodiments that when SRv6 acts as a head node and sends a message to an SRv6 tail node, it can encapsulate the first message according to the SRv6 forwarding table to ensure that the upstream and downstream traffic paths are consistent, thereby avoiding problems such as inconsistent upstream and downstream traffic paths, resulting in traffic blockage, etc.

[0028] According to a third aspect of an embodiment of this specification, a gateway device is provided, wherein the gateway device enables an SRv6 tail node, and the gateway device includes:

[0029] A receiving module, configured to receive a first message from a Client connected to the SRv6 tail node;

[0030] A matching module, configured to match the routing information of the first message with an SRv6 forwarding table, wherein the SRv6 forwarding table includes a correspondence between the routing information of each message and the address information of the SRv6 head node that sends each message;

[0031] The processing module is used to obtain target routing information matching the routing information of the first message and the address information of the target SRv6 head node corresponding to the target routing information, encapsulate the first message according to the target routing information and the address information of the target SRv6 head node, and send it.

[0032] The receiving module is further used to receive a second message sent by each SRv6 head node, wherein the second message carries source address information of the SRv6 head node that sends the second message;

[0033] The processing module is further used to obtain the routing information of the second message and the corresponding source address information of the SRv6 head node and generate an SRv6 forwarding table.

[0034] The receiving module is further configured to receive request information sent by a client connected to the SRv6 tail node, wherein the request information is sent when the client recognizes that the connected SRv6 tail node is not unique;

[0035] The processing module is further configured to send the SRv6 forwarding table to the Client according to the request information of the Client, so that the Client sends the first message according to the SRv6 tail node of the SRv6 forwarding table item.

[0036] According to a fourth aspect of an embodiment of this specification, a gateway device is provided, wherein the gateway device enables an SRv6 head node, and the gateway device includes:

[0037] A receiving module, configured to receive a second message from a Client connected to the SRv6 head node;

[0038] A matching module, configured to match the routing information of the second message with the SRv6 forwarding table, wherein the SRv6 forwarding table includes a correspondence between the routing information of each message and the address information of the SRv6 tail node that sends each message;

[0039] The processing module is used to obtain target routing information matching the routing information of the second message and the address information of the target SRv6 tail node corresponding to the target routing information, encapsulate the second message according to the target routing information and the address information of the target SRv6 tail node, and send it.

[0040] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present specification. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0042] Figure 1 This is a schematic diagram of a dual-gateway network architecture for SRv6 networking according to an exemplary embodiment of the present specification.

[0043] Figure 2 It is a flowchart of a method for processing an SRv6 message according to an exemplary embodiment of the present specification.

[0044] Figure 3 This is a schematic diagram of a dual-gateway network architecture for SRv6 networking according to an exemplary embodiment of the present specification. DETAILED DESCRIPTION

[0045] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementations described in the following exemplary embodiments do not represent all implementations consistent with this specification. Instead, they are merely examples of devices and methods consistent with some aspects of this specification as detailed in the appended claims.

[0046] The terms used in this specification are for the purpose of describing specific embodiments only and are not intended to limit this specification. The singular forms "a", "the" and "the" used in this specification and the appended claims are also intended to include plural forms unless the context clearly indicates otherwise. It should also be understood that the term "and / or" used herein refers to and includes any or all possible combinations of one or more associated listed items.

[0047] It should be understood that although the terms first, second, third, etc. may be used in this specification to describe various information, this information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of this specification, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".

[0048] To solve the above technical problems, the present disclosure provides a method for processing an SRv6 message, which is applied to an SRv6 tail node. Figure 2 As shown, the method includes:

[0049] S201 receives a first message from a Client connected to the SRv6 egress node;

[0050] S202 uses the routing information of the first message to match the SRv6 forwarding table, wherein the SRv6 forwarding table includes a correspondence between the routing information of each message and the address information of the SRv6 head node that sends each message;

[0051] S203: Acquire target routing information matching the routing information of the first message, and address information of the target SRv6 head node corresponding to the target routing information;

[0052] S204 encapsulates the first message according to the target routing information and the address information of the target SRv6 head node and sends it.

[0053] In this embodiment, the SRv6 tail node and the SRv6 head node are relative tail nodes and head nodes, such as Figure 3 As shown in the figure, when Client 1 sends a message to Device 2 first, Gateway 1 (or Gateway 2, depending on the selection of Client 1) is the SRv6 head node, and Gateway 3 is the SRv6 tail node. When Device 2 sends a message to Client 1 first, Gateway 3 is the SRv6 head node, and Gateway 1 (or Gateway 2, depending on the selection of Gateway 3) is the SRv6 tail node.

[0054] In this embodiment, in the SRv6 network, each SRv6 device has a unique encapsulation source-address for the entire network. In this embodiment, the encapsulation source-address can be used as the address information of the head node or tail node of SRv6. When the uplink traffic is sent out through the SRv6 tunnel of gateway 1, the encapsulation source-address1 of gateway 1 is included in the tunnel encapsulation and sent to the SRv6 tail node.

[0055] In one embodiment, if Figure 3 As shown, assuming that Client 1 serves as the client access device 2 (Server), Client 1 selects Gateway 1 as the SRv6 head node device. After receiving the message sent by Client 1, Gateway 1 encapsulates the message and encapsulates the encapsulation source-address1 of Gateway 1 and sends it to Gateway 3 (SRv6 tail node).

[0056] Gateway 3 (SRv6 tail node) unpacks the message and sends it to device 2. In this embodiment, after receiving the message, gateway 3 obtains the encapsulation source-address1 carried in the message and the routing information of the message, where the routing information of the message may be the five-tuple information of the message, and creates an SRv6 forwarding table using the correspondence between encapsulation source-address1 and the five-tuple information of the message.

[0057] When device 2 gives feedback on the message sent by Client 1, the feedback message (first message) arrives at gateway 3 (SRv6 tail node), gateway 3 obtains the routing information of the first message, and uses the routing information of the first message to match the SRv6 forwarding table. As mentioned above, the SRv6 forwarding table in gateway 3 records the routing information and encapsulation source-address1 of the message sent by Client 1 to gateway 3. At this time, the matching result obtained by the above matching is encapsulationsource-address1.

[0058] The first message is encapsulated and sent by using encapsulation source-address1 and the routing information of the first message, so that the first message is sent to gateway 1, thereby achieving the unification of upstream and downstream traffic paths.

[0059] The embodiment of the present disclosure further provides a method for processing an SRv6 message, the method being applied to an SRv6 head node, the method comprising:

[0060] Receive a second message from a Client connected to the SRv6 head node;

[0061] Matching the routing information of the second message with the SRv6 forwarding table, wherein the SRv6 forwarding table includes a correspondence between the routing information of each message and the address information of the SRv6 tail node that sends each message;

[0062] Obtain target routing information that matches the routing information of the second message, and address information of the target SRv6 tail node corresponding to the target routing information;

[0063] The second message is encapsulated according to the target routing information and the address information of the target SRv6 tail node and sent.

[0064] like Figure 3 As shown, in this embodiment, there may be multiple message interactions between Client 1 and Device 2. At this time, when the SRv6 head node (gateway 1) receives the second message from Client 1, the routing information of the second message can be matched with the SRv6 forwarding table.

[0065] The SRv6 forwarding table in gateway 1 may be created after gateway 1 receives the encapsulated first message from gateway 3 and obtains the address information of gateway 3 and the routing information of the first message from the encapsulated first message.

[0066] In this embodiment, each gateway device can set a timer for the SRv6 forwarding table entry it creates. When the timer expires, the SRv6 forwarding table entry can be deleted. Before the timer expires, the upstream and downstream traffic paths can be unified according to the SRv6 forwarding table entry.

[0067] Based on the above method embodiments, the embodiment of the present disclosure further provides a gateway device, wherein the gateway device enables an SRv6 tail node, and the gateway device includes:

[0068] A receiving module, configured to receive a first message from a Client connected to the SRv6 tail node;

[0069] A matching module, configured to match the routing information of the first message with an SRv6 forwarding table, wherein the SRv6 forwarding table includes a correspondence between the routing information of each message and the address information of the SRv6 head node that sends each message;

[0070] The processing module is used to obtain target routing information matching the routing information of the first message and the address information of the target SRv6 head node corresponding to the target routing information, encapsulate the first message according to the target routing information and the address information of the target SRv6 head node, and send it.

[0071] The receiving module is further used to receive a second message sent by each SRv6 head node, wherein the second message carries source address information of the SRv6 head node that sends the second message;

[0072] The processing module is further used to obtain the routing information of the second message and the corresponding source address information of the SRv6 head node and generate an SRv6 forwarding table.

[0073] The receiving module is further configured to receive request information sent by a client connected to the SRv6 tail node, wherein the request information is sent when the client recognizes that the connected SRv6 tail node is not unique;

[0074] The processing module is further configured to send the SRv6 forwarding table to the Client according to the request information of the Client, so that the Client sends the first message according to the SRv6 tail node of the SRv6 forwarding table item.

[0075] The embodiment of the present disclosure further provides a gateway device, wherein the gateway device enables an SRv6 head node, and the gateway device includes:

[0076] A receiving module, configured to receive a second message from a Client connected to the SRv6 head node;

[0077] A matching module, configured to match the routing information of the second message with the SRv6 forwarding table, wherein the SRv6 forwarding table includes a correspondence between the routing information of each message and the address information of the SRv6 tail node that sends each message;

[0078] The processing module is used to obtain target routing information matching the routing information of the second message and the address information of the target SRv6 tail node corresponding to the target routing information, encapsulate the second message according to the target routing information and the address information of the target SRv6 tail node, and send it.

[0079] For the device embodiment, since it basically corresponds to the method embodiment, the relevant parts can refer to the partial description of the method embodiment. The device embodiment described above is only schematic, wherein the modules described as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical modules, that is, they may be located in one place, or they may be distributed on multiple network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this specification. A person of ordinary skill in the art can understand and implement it without paying creative labor.

[0080] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

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

[0082] It should be understood that the present description is not limited to the precise structures that have been 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 description is limited only by the appended claims.

[0083] The above description is only a preferred embodiment of this specification and is not intended to limit this specification. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of this specification should be included in the scope of protection of this specification.

Claims

1. A method for processing an SRv6 message, characterized in that: The method is applied to an SRv6 tail node, and the method includes: Receive a first message from a Client connected to the SRv6 egress node; Matching the routing information of the first message with the SRv6 forwarding table, wherein the SRv6 forwarding table includes a correspondence between the routing information of each message and the address information of the SRv6 head node that sends each message; Acquire target routing information matching the routing information of the first message, and address information of the target SRv6 head node corresponding to the target routing information; The first message is encapsulated and sent according to the target routing information and the address information of the target SRv6 head node.

2. The method according to claim 1, characterized in that The method further comprises: Receive a second message sent by each SRv6 head node, where the second message carries source address information of the SRv6 head node that sends the second message; Obtain the routing information of the second message and the corresponding source address information of the SRv6 head node and generate an SRv6 forwarding table.

3. The method according to claim 1, characterized in that The routing information includes quintuple information.

4. The method according to claim 1, characterized in that: The method further comprises: Receive a request message sent by a client connected to an SRv6 egress node, where the request message is sent when the client recognizes that the connected SRv6 egress node is not unique; According to the request information of the Client, the SRv6 forwarding table is sent to the Client, so that the Client sends the first message according to the SRv6 tail node of the SRv6 forwarding table entry.

5. A method for processing an SRv6 message, characterized in that: The method is applied to an SRv6 head node, and the method comprises: Receive a second message from a Client connected to the SRv6 head node; Matching the routing information of the second message with the SRv6 forwarding table, wherein the SRv6 forwarding table includes a correspondence between the routing information of each message and the address information of the SRv6 tail node that sends each message; Obtain target routing information that matches the routing information of the second message, and address information of the target SRv6 tail node corresponding to the target routing information; The second message is encapsulated according to the target routing information and the address information of the target SRv6 tail node and sent.

6. The method according to claim 5, characterized in that The method further comprises: Receive a second message sent by each SRv6 head node, where the second message carries source address information of the SRv6 head node that sends the second message; Obtain the routing information of the second message and the corresponding source address information of the SRv6 head node and generate an SRv6 forwarding table.

7. A gateway device, characterized in that: The gateway device enables an SRv6 tail node, and the gateway device includes: A receiving module, configured to receive a first message from a Client connected to the SRv6 tail node; A matching module, configured to match the routing information of the first message with an SRv6 forwarding table, wherein the SRv6 forwarding table includes a correspondence between the routing information of each message and the address information of the SRv6 head node that sends each message; The processing module is used to obtain target routing information matching the routing information of the first message and the address information of the target SRv6 head node corresponding to the target routing information, encapsulate the first message according to the target routing information and the address information of the target SRv6 head node, and send it.

8. The gateway device according to claim 7, characterized in that: The receiving module is further configured to receive a second message sent by each SRv6 head node, wherein the second message carries source address information of the SRv6 head node that sends the second message; The processing module is further used to obtain the routing information of the second message and the corresponding source address information of the SRv6 head node and generate an SRv6 forwarding table.

9. The gateway device according to claim 7, characterized in that: The receiving module is further configured to receive request information sent by a client connected to the SRv6 tail node, wherein the request information is sent when the client recognizes that the connected SRv6 tail node is not unique; The processing module is further configured to send the SRv6 forwarding table to the Client according to the request information of the Client, so that the Client sends the first message according to the SRv6 tail node of the SRv6 forwarding table item.

10. A gateway device, characterized in that: The gateway device enables an SRv6 head node, and the gateway device includes: A receiving module, configured to receive a second message from a Client connected to the SRv6 head node; A matching module, configured to match the routing information of the second message with the SRv6 forwarding table, wherein the SRv6 forwarding table includes a correspondence between the routing information of each message and the address information of the SRv6 tail node that sends each message; a processing module, configured to obtain target routing information matching the routing information of the second message, and The address information of the target SRv6 tail node corresponding to the target routing information is encapsulated into a second message according to the target routing information and the address information of the target SRv6 tail node, and the second message is sent.

Images