WO2019080927A1

WO2019080927A1 - Message processing method and device, and computer-readable storage medium

Info

Publication number: WO2019080927A1
Application number: PCT/CN2018/112084
Authority: WO
Inventors: 付志涛
Original assignee: 中兴通讯股份有限公司
Priority date: 2017-10-27
Filing date: 2018-10-26
Publication date: 2019-05-02
Also published as: CN109729006B; CN109729006A

Abstract

A message processing method, which comprises: when a node needs to calculate a path, detecting whether there is a received RSVP-TE message and whether the message carries a routing instance number (301); when such message exists and carries the routing instance number, detecting whether a path from the node to a next node comprises a path pertaining to the carried routing instance number, and if so, calculating a path according to the carried routing instance number (302); if not, traversing the routing instance number of the node to calculate a path (303); and sending to the next node the RSVP-TE message carrying the calculated path and the routing instance number to which the path pertains (304).

Description

Message processing method and device, computer readable storage medium

Technical field

The present disclosure relates to, but is not limited to, the field of communication technologies, and in particular, to a message processing method and apparatus, and a computer readable storage medium.

Background technique

The Resource Reservation Protocol-Traffic Engineer (RSVP-TE) is an extension of the traditional Resource Reservation Protocol (RSVP) for multi-protocol label switching. The traffic engineering is implemented in the Switching (MPLS)/IP (Internet Protocol) network. The traffic is forwarded in the Traffic Engineer (TE) tunnel through the information release, path calculation, signaling interaction, and traffic forwarding.

The path calculation relies on the traffic engineering-based Interior Gateway Protocol-Import Engineering (IGP-TE) flooding of TE links and attributes to form a TE database, and then through Constrained Shortest Path First (Constrained Shortest Path First, The CSPF algorithm calculates the path information of a tunnel. IGP-TE generally includes extensions of TE for Open Shortest Path First (OSPF) and Intermediate System to Intermediate System (ISIS).

With the application and development of the network, the internal gateway protocol (IGP) internally divides the network logically by the instance number. The physical number of the physical device can be divided into multiple logical devices by using the instance number. Currently, there are two types of division. :

The first type: divided by exclusive port mode;

As shown in Figure 1, three physical devices R1, R2, and R3 can be divided into two logical devices by dividing instance 1 and instance 2 on each device. Link L12 and link L23 belong to instance 1. Road L21 and link L32 belong to instance 2, and each device is divided into two logical devices;

Second: divided by shared port mode;

As shown in Figure 2, three physical devices, R1, R2, and R3, are also configured with routing instance 1 and routing instance 2 for each device to divide the device into two logical devices. The first method is the link. L12 and link L23 belong to both instance 1 and instance 2. This division is more logically distinguishable.

According to the characteristics of the isolation, the entire tunnel path is preferably located in the same routing instance.

Summary of invention

The present disclosure provides a message processing method and apparatus, and a computer readable storage medium, which enables a path of an entire tunnel to be located in the same routing instance as much as possible.

The technical solution of the embodiment of the present disclosure is implemented as follows:

An embodiment of the present disclosure provides a packet processing method, including: when a node needs to calculate a path, detecting whether there is a received RSVP-TE packet and whether the received RSVP-TE packet carries a routing instance number; When there is a received RSVP-TE packet and the received RSVP-TE packet carries the route instance number, it is detected whether the path of the node to the next hop node includes the path belonging to the carried route instance number. When the path belongs to the carried route instance number, the path is calculated according to the carried route instance number; when the path belonging to the carried route instance number is not included, the route instance number calculation path of the node is traversed; Send an RSVP-TE packet carrying the calculated path and its associated route instance number to the next hop node.

Embodiments of the present disclosure also provide a computer readable storage medium storing one or more programs, the one or more programs being executable by one or more processors to implement the following Step: When the node needs to calculate the path, it detects whether there is a received RSVP-TE packet and the received RSVP-TE packet carries the route instance number; if there is a received RSVP-TE packet and has received When the RSVP-TE packet carries the route instance number, it is detected whether the path of the node to the next hop node includes the path belonging to the carried route instance number, and when the route belonging to the carried route instance number is included, Calculating the path according to the carried route instance number; when the path belonging to the carried route instance number is not included, traversing the route instance number of the node to calculate the path; sending the carried path and the route instance number to which it belongs The RSVP-TE packet is sent to the next hop node.

The embodiment of the present disclosure further provides a message processing apparatus, including a path calculation unit and a sending unit, wherein: the path calculating unit is configured to calculate a path of the node to which the node belongs to the next hop node, and calculate the path and the path to which it belongs. The routing instance number is output to the sending unit, and the sending unit is configured to send the RSVP-TE packet carrying the calculated path and the route instance number to which it belongs to the next hop node.

BRIEF abstract

FIG. 1 is a schematic structural diagram of dividing a physical device into multiple logical devices by using an exclusive port mode in some cases;

2 is a schematic structural diagram of dividing a physical device into multiple logical devices by using a shared port mode in some cases;

FIG. 3 is a schematic flowchart of a packet processing method according to an embodiment of the present disclosure;

4 is a schematic structural diagram of a message processing apparatus according to a first embodiment of the present disclosure;

FIG. 5 is a schematic structural diagram of a message processing apparatus according to a second embodiment of the present disclosure;

FIG. 6 is a schematic structural diagram of a type-Length-Value (TLV) of a route instance number according to an alternative embodiment of the present disclosure;

FIG. 7 is a schematic flowchart of processing when receiving an RSVP-TE packet according to an optional embodiment of the present disclosure;

FIG. 8 is a schematic flowchart of processing when an RSVP-TE packet is sent according to an optional embodiment of the present disclosure;

FIG. 9 is a schematic structural diagram of dividing a physical device into multiple logical devices by using a shared port mode according to an alternative embodiment of the present disclosure.

Detailed

Embodiments of the present disclosure will be described below with reference to the accompanying drawings.

In some cases, according to the characteristics of isolation, the entire tunnel path is preferably located in the same Route Instance. However, in some cases, when RSVP-TE is deployed in the environment of routing multiple instances, the header is assumed. Point path calculation selects the path of instance 1. However, when sending signaling, the instance number selected by itself is not transmitted to the downstream node. When the downstream node has a loose node, the path needs to be calculated at the loose node. At this time, the loose node can select The path of the instance 1 can also be selected as the path of the instance 2. Therefore, in the routing multi-instance environment, the paths of the same tunnel may be in different instances, and the route isolation effect is not achieved.

As shown in FIG. 3, a message processing method according to the present disclosure may include the following steps:

Step 301: When the node needs to calculate the path, it is detected whether there is a received RSVP-TE packet and the received RSVP-TE packet carries the routing instance number.

Step 302: When there is a received RSVP-TE packet and the received RSVP-TE packet carries the route instance number, it is detected whether the path of the node to the next hop node includes the route instance number that belongs to the carried Path; when included, go to step 303; when not included, go to step 304;

Step 303: Calculate the path according to the carried route instance number, and go to step 305;

Step 304: traverse the route instance number calculation path of the node;

Step 305: Send an RSVP-TE packet carrying the calculated path and the route instance number to which it belongs to the next hop node.

Optionally, the packet processing method further includes: traversing the routing instance number of the node when there is no received RSVP-TE packet, or the received RSVP-TE packet does not carry the routing instance number. Calculate the path.

Optionally, the packet processing method further includes: after step 301, when there is no received RSVP-TE packet, or the received RSVP-TE packet does not carry the routing instance number, step 304 is performed.

Optionally, the packet processing method further includes: when the node does not need to calculate a path, forward the received RSVP-TE packet to the next hop node.

It can be noted that the received RSVP-TE packet may include a routing instance number or may not include a routing instance number.

Optionally, the packet processing method further includes: when the node needs to calculate a backup path, detecting whether the path of the node to the next hop node includes other routing instances belonging to the primary path, except the primary path. The path of the number; when included, the backup path is calculated according to the route instance number of the primary path; when not included, the route instance number of the node is traversed to calculate the backup path.

The present disclosure also discloses a computer readable storage medium storing one or more programs, the one or more programs being executable by one or more processors to implement the following steps: When the node needs to calculate the path, it checks whether there is a received RSVP-TE packet and whether the received RSVP-TE packet carries the route instance number; if there is a received RSVP-TE packet and the received RSVP- If the path of the route to the next hop node is included in the TE packet, the path of the route to the next hop node is included in the path of the route instance number. The route instance number calculation path is carried; when the route belonging to the carried route instance number is not included, the route instance number of the node is traversed; the RSVP carrying the calculated path and the route instance number to which it belongs is sent. - TE message to the next hop node.

Optionally, the one or more programs may be executed by one or more processors to implement the following steps: when there is no received RSVP-TE message, or there is no received RSVP-TE message When carrying the route instance number, it traverses the route instance number calculation path of the node.

Optionally, the one or more programs may be executed by one or more processors to implement the following steps: when the node does not need to calculate a path, forward the received RSVP-TE message directly to the next Jump the node.

Optionally, the one or more programs may also be executed by one or more processors to implement the following steps: when the node needs to calculate a backup path, detect the path of the node to the next hop node except the main Outside the path, whether the path of the route instance number of the primary path is included; when included, the backup path is calculated according to the route instance number of the primary path; when not included, the route instance number of the node is traversed to calculate the backup path.

As shown in FIG. 4, a message processing apparatus according to the present disclosure may include a path calculation unit 401 and a sending unit 402, wherein: the path calculation unit 401 is configured to calculate a path of a node to which the node belongs to the next hop node, and The calculated path and the route instance number to which it belongs are output to the sending unit 402. The sending unit 402 is configured to send the RSVP-TE packet carrying the calculated path and the route instance number to which it belongs to the next hop node.

Optionally, as shown in FIG. 5, the packet processing apparatus further includes a receiving unit 403, where: the receiving unit 403 is configured to receive an RSVP-TE packet, and detect, according to the received RSVP-TE packet, whether the node to which the node belongs The path calculation unit 401 is required to calculate the path, and the path calculation unit 401 is configured to calculate the path; and the route instance number is received in the received RSVP-TE message. The path calculation unit 401 is further configured to receive the notification and output route instance number of the receiving unit 403, and detect whether the path of the node to which the node belongs to the next hop node includes the path belonging to the carried route instance number, when When the path of the carried route instance number is the path, the path is calculated according to the carried route instance number; when the path belonging to the carried route instance number is not included, the route instance number calculation path of the node to which the node belongs is traversed.

Optionally, the path calculation unit 401 is further configured to: when the notification of the receiving unit 403 is not received, or when the routing instance number output by the receiving unit 403 is not received, traverse the routing instance number of the node to which the node belongs.

Optionally, the receiving unit 403 is further configured to output the received RSVP-TE message directly to the sending unit 402 when the node to which the node belongs does not need to calculate the path; the sending unit 402 is further configured to: The received RSVP-TE packet is directly forwarded to the next hop node.

Optionally, the path calculation unit 401 is further configured to: when the node to which the node belongs needs to calculate the backup path, detect whether the path of the node to which the node belongs to the next hop node includes other routes belonging to the primary path, except the primary path. Path of the instance number; when included, the backup path is calculated according to the route instance number of the primary path; when not included, the route instance number of the node is traversed to calculate the backup path.

The present disclosure is also provided with a few alternative embodiments to explain the present disclosure in order to better describe the present disclosure.

An alternative embodiment

1 path calculation, returning the path, while returning the instance number of the path;

When a node performs path calculation, it returns a path and returns the route instance number of the path.

2 extending the RSVP-TE protocol, carrying the routing instance number, and carrying the routing instance number in the signaling interaction of the RSVP-TE tunnel;

It can be noted that, in some cases, the present disclosure may carry the RSVP-TE protocol by carrying the routing instance number in the RSVP-TE tunnel signaling interaction, and carries the routing instance number in the signaling, and defines the length of the protocol number to be 2 bytes. In accordance with the routing instance number, an object can be added or expanded in an existing field. Figure 6 shows the extended TLV structure of the newly added object, and Reserved is a 2-byte reserved field.

For the processing of the routing instance number in the RSVP-TE packet, when the node needs the path calculation, the path calculation is optionally performed in the instance number carried in the signaling.

When the node does not need the path calculation, the instance number can be ignored. When the node needs the path calculation, the path calculation needs to be prioritized in the instance number carried in the signaling.

4 When calculating the backup path according to the local policy, the backup path calculation is performed in the specified route instance according to the local policy by searching the route instance number of the primary path.

Another alternative embodiment

The processing flow of the RSVP-TE receiving packet, as shown in Figure 7, is performed according to whether the packet carries the routing instance number information. When not carrying, the node traverses the routing instance number when calculating the path. The path calculation is performed until the path calculation is successful. When carrying, the node calculates the path number in the packet according to the instance number in the packet.

The process of sending the RSVP-TE packet is as shown in Figure 8. The local number is calculated according to whether the local calculation and the upstream packet carry the route instance number. When there is no path calculation, the instance number in the packet does not change. When the local path is calculated, the instance number in the packet is changed to the instance number of the local path and continues to be sent downstream.

Yet another alternative embodiment:

As shown in Figure 1, the multi-instance of the routing type of the port type is established. The tunnel is established from the physical device R1 to the physical device R3, and is loose to the intermediate node R2 (that is, the intermediate node R2 is a loose node). The route instance is divided into: link L12, link L23 belongs to instance 1, link L21, and link L32 belong to instance 2.

When the R1 path is calculated, the destination is R2. When the selected path is the L12 of the instance 1, the PATH packet sent to the R2 carries the route instance number of the instance 1.

When R2 receives the PATH message sent by R1, the instance number in the read message is 1. When the path is calculated to the path of R3, optionally, it can be calculated in instance 1. The calculated path is L23, due to calculation. The path is still instance 1, and when R2 sends a PATH message to R3, the route instance still fills in the value of instance 1.

Thus, the entire path that the physical device R1 establishes to the physical device R3 is L12 and L23, and belongs to the routing instance 1.

Yet another optional embodiment:

As shown in Figure 9, the multi-instance of the port type is shared. The tunnel is established from the physical device R1 to the physical device R3 and is loose to the intermediate node R2 (that is, the intermediate node R2 is a loose node). The division of the routing instance is as follows: the link L12, the link L23, and the link L13 belong to the instance 1, and the link L12, the link L23, and the link L31 belong to the instance 2. The links L12 and L23 links are in both

instances

1 and 2.

The path to the R2 is calculated at the head node R1. When the calculated path is the link L12, since the link L12 belongs to the instance 1 and the instance 2, the instance number returned by the path calculation determines the PATH message sent as the R2. Value, in this case returning both instance 1 and instance 2 are possible;

The head node R1 sends a PATH message to the intermediate node R2, carrying the route instance number 1 or the route instance number 2;

When receiving the PATH message sent by R1, the intermediate node R2 reads the instance number in the packet. When the instance number is 1, and the path is calculated to the path of R3, it can optionally be calculated in the instance 1. The calculated path is L23. When the instance number is 2, the path is calculated to the path of R3, optionally calculated in the example 2, and the calculated path is the link L23;

When R2 sends a PATH message to R3, the routing instance fills in the instance number of the local node path. Thus, the entire path established by R1 to R3 is link L12 and link L23, belonging to route instance 1 or instance 2.

When a backup path is created for the above path, the path calculation can be performed according to the route instance number adopted by the primary path.

On the R1 node, when the primary path is determined to be successful with the instance 1, when the R1 node calculates the backup path, the route instance 1 is also used for calculation, so that the calculated path is the link L13.

The primary path is the link L12 and the link L23, and the backup path is the link L13, which belongs to the routing instance 1.

Embodiments of the present disclosure also provide a computer readable storage medium storing computer executable instructions that, when executed, implement the message processing method described above.

The message processing method and apparatus and the computer readable storage medium provided by the present disclosure transmit an RSVP-TE message carrying a route instance number to which the path calculated by the local node belongs to the next hop node and preferentially follow the received RSVP-TE. The routing instance number carried in the packet calculates the path, so that in the routing multi-instance environment, the path of the same tunnel is located in the same instance as much as possible, or even the largest possible, thus truly achieving the effect of route isolation.

The message processing method and apparatus and the computer readable storage medium provided by the present disclosure transmit an RSVP-TE message carrying a route instance number to which the path calculated by the local node belongs to the next hop node and preferentially follow the received RSVP-TE. The routing instance number carried in the packet calculates the path, so that in the routing multi-instance environment, the downstream node can perform related path calculation with reference, so that the path of the same tunnel is located in the same instance as much as possible, and thus the real The effect of route isolation.

One of ordinary skill in the art will appreciate that all or a portion of the steps described above can be accomplished by a program that instructs the associated hardware, such as a read-only memory, a magnetic or optical disk, and the like. Optionally, all or part of the steps of the foregoing embodiments may also be implemented by using one or more integrated circuits. Accordingly, each module/unit in the foregoing embodiment may be implemented in the form of hardware, or may be implemented by using a software function module. The form is implemented. The present disclosure is not limited to any specific form of combination of hardware and software.

Those of ordinary skill in the art will appreciate that all or some of the steps, systems, and functional blocks/units of the methods disclosed above may be implemented as software, firmware, hardware, and suitable combinations thereof. In a hardware implementation, the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may be composed of several physical The components work together. Some or all of the components may be implemented as software executed by a processor, such as a digital signal processor or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit. Such software may be distributed on a computer readable medium, which may include computer storage media (or non-transitory media) and communication media (or transitory media). As is well known to those of ordinary skill in the art, the term computer storage medium includes volatile and nonvolatile, implemented in any method or technology for storing information, such as computer readable instructions, data structures, program modules or other data. Sex, removable and non-removable media. Computer storage media include, but are not limited to, Random Access Memory (RAM), Read-Only Memory (ROM), and Electrically Erasable Programmable Read-only Memory (EEPROM). Flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical disc storage, magnetic cassette, magnetic tape, disk storage or other magnetic storage device, or Any other medium used to store the desired information and that can be accessed by the computer. Moreover, it is well known to those skilled in the art that communication media typically includes computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and can include any information delivery media. .

A person skilled in the art can understand that the technical solutions of the present disclosure may be modified or equivalent, without departing from the spirit and scope of the present disclosure, and should be included in the scope of the claims of the present disclosure.

Claims

A packet processing method, comprising:

When the node needs to calculate the path, it detects whether there is a received traffic engineering resource reservation protocol RSVP-TE packet and whether the received RSVP-TE packet carries the routing instance number;

When there is a received RSVP-TE packet and the received RSVP-TE packet carries the route instance number, it is detected whether the path of the node to the next hop node includes the path belonging to the carried route instance number. When a path belonging to the carried route instance number is included, the path is calculated according to the carried route instance number; when the path belonging to the carried route instance number is not included, the route instance number calculation path of the node is traversed ;

Send an RSVP-TE packet carrying the calculated path and its associated route instance number to the next hop node.
The packet processing method according to claim 1, wherein the packet processing method further comprises:

When there is no received RSVP-TE packet, or the received RSVP-TE packet does not carry the routing instance number, the route instance number of the node is traversed.
The packet processing method according to claim 1, wherein the packet processing method further comprises:

When the node does not need to calculate a path, the received RSVP-TE packet is directly forwarded to the next hop node.
The packet processing method according to claim 1, wherein the packet processing method further comprises:

When the node needs to calculate the backup path, it is detected whether the path of the node to the next hop node includes other paths belonging to the route instance number of the primary path, except for the primary path;

When included, the backup path is calculated according to the route instance number of the primary path; when not included, the route instance number of the node is traversed to calculate the backup path.
A computer readable storage medium, characterized in that the computer readable storage medium stores one or more programs, the one or more programs being executable by one or more processors to implement the following steps:

When the node needs to calculate the path, it detects whether there is a received traffic engineering resource reservation protocol RSVP-TE packet and whether the received RSVP-TE packet carries the routing instance number;

When there is a received RSVP-TE packet and the received RSVP-TE packet carries the route instance number, it is detected whether the path of the node to the next hop node includes the path belonging to the carried route instance number. When a path belonging to the carried route instance number is included, the path is calculated according to the carried route instance number; when the path belonging to the carried route instance number is not included, the route instance number calculation path of the node is traversed ;

Send an RSVP-TE packet carrying the calculated path and its associated route instance number to the next hop node.
A message processing apparatus, comprising: a path calculation unit and a sending unit, wherein:

The path calculation unit is configured to: calculate a path from the node to which the node belongs to the next hop node, and output the calculated path and the route instance number to which it belongs to the sending unit;

The sending unit is configured to: send a traffic engineering-based resource reservation protocol RSVP-TE packet carrying the calculated path and its associated route instance number to the next hop node.
The message processing device according to claim 6, further comprising a receiving unit, wherein:

The receiving unit is configured to: receive an RSVP-TE packet, and detect, according to the received RSVP-TE packet, whether the node to which the node belongs needs to calculate a path, and when the path needs to be calculated, notify the path calculation unit to calculate the path; and detect the received RSVP-TE. Whether the route instance number is carried in the packet, and when carried, the route instance number carried is output to the path calculation unit;

The path calculation unit is further configured to: receive the notification of the receiving unit and the output route instance number, and detect whether the path of the node to which the node belongs to the next hop node includes the path belonging to the carried route instance number, and includes the belonging to the When the path of the carried route instance number is described, the path is calculated according to the carried route instance number; when the path belonging to the carried route instance number is not included, the route instance number of the node to which the node belongs is traversed.
The message processing device according to claim 7, wherein the path calculation unit is further configured to:

When the notification of the receiving unit is not received, or the routing instance number output by the receiving unit is not received, the routing instance number of the node to which it belongs is traversed.
The message processing device according to claim 7, wherein the receiving unit is further configured to:

When the node to which the node belongs does not need to calculate the path, the received RSVP-TE packet is directly output to the sending unit;

The sending unit is further configured to forward the received RSVP-TE message directly to the next hop node.
The message processing device according to claim 6, wherein the path calculation unit is further configured to:

When the node to which the node belongs needs to calculate the backup path, it is detected whether the path of the node to which the node belongs to the next hop node includes the path of the route instance number of the primary path, except for the primary path.

When included, the backup path is calculated according to the route instance number of the primary path; when not included, the route instance number of the node is traversed to calculate the backup path.