CN117640505A

CN117640505A - Data message processing method and device, storage medium and electronic device

Info

Publication number: CN117640505A
Application number: CN202210952385.6A
Authority: CN
Inventors: 王玉保; 舒晔
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2022-08-09
Filing date: 2022-08-09
Publication date: 2024-03-01
Also published as: WO2024032062A1

Abstract

The embodiment of the application provides a data message processing method, a device, a storage medium and an electronic device, wherein the method comprises the following steps: receiving a route which is issued by a route transmitting end node and corresponds to the AC in the first horizontal partition group and is used for carrying an ESI label; if the RT corresponding to the first horizontal segmentation group is matched with the imported RT of the second horizontal segmentation group to which the first AC belongs, packaging a first data message received from the first AC into a second data message; the second data message is sent to the routing sending end node, so that the routing sending end node filters the ACs in the first horizontal segmentation group when broadcasting the first data message, the problem that the horizontal segmentation mechanism based on ESI label extension group attributes cannot realize the horizontal segmentation of the cross-ES in the related technology can be solved, and the nodes receiving the data message filter the ACs in the same cross-rack horizontal segmentation group when broadcasting the data message, so that the horizontal segmentation of the cross-ES is realized.

Description

Data message processing method and device, storage medium and electronic device

Technical Field

The embodiment of the application relates to the field of communication, in particular to a data message processing method, a device, a storage medium and an electronic device.

Background

In RFC7432 (Request For Comments), a horizontal splitting mechanism based on an Ethernet Segment identifier (Ethernet Segment Identifier, abbreviated as ESI) tag extension group attribute is defined, but the horizontal splitting mechanism is only applicable to horizontal splitting within the same ES and cannot be applicable to horizontal splitting across ESIs, fig. 1 is a schematic diagram of a horizontal splitting mechanism based on an ESI tag extension group attribute according to the related art, as shown in fig. 1, when PE1 (Provider Edge) receives a BUM message from CE1 (Customer Edge) and forwards the BUM message to PE2, the ESI tag issued by PE2 as ES2 (Ethernet Segment) is not encapsulated, and thus horizontal splitting across ES1 and ES2 cannot be achieved. Further, when PE1 receives a BUM packet from CE1 and forwards it to PE3, after the BUM packet reaches PE3, it is only forwarded to ES3, but not to ES2, and the horizontal splitting mechanism based on ESI tag extended community attribute in RFC7432 is not supported.

Aiming at the problem that the horizontal segmentation mechanism based on ESI label extension community attribute in the related art can not realize horizontal segmentation across ES, no solution has been proposed yet.

Disclosure of Invention

The embodiment of the application provides a data message processing method, a device, a storage medium and an electronic device, which are used for at least solving the problem that a horizontal segmentation mechanism based on ESI label extension group attributes in the related art cannot realize horizontal segmentation across ES.

According to one embodiment of the present application, there is provided a data packet processing method, including:

receiving a route which is issued by a route transmitting end node and corresponds to an AC in a first horizontal partition group and used for carrying an ESI label, wherein the route used for carrying the ESI label carries a label for marking the first horizontal partition group and a route target RT corresponding to the first horizontal partition group;

under the condition that RT corresponding to the first horizontal partition group is matched with the imported RT of a second horizontal partition group where a first AC is located, packaging a first data message received from the first AC into a second data message, wherein the second data message carries a label for identifying the first horizontal partition group, and the first AC is the AC belonging to the second horizontal partition group on the routing receiving end node;

and sending the second data message to the routing sending end node so that the routing sending end node filters the ACs in the first horizontal partition group when broadcasting the first data message.

According to another embodiment of the present application, there is also provided a data packet processing method applied to a routing sender node, the method including:

issuing a route which corresponds to the AC in the first horizontal partition group and is used for carrying an ESI label to a route receiving end node, wherein the route which is used for carrying the ESI label carries a label for identifying the first horizontal partition group and a route target RT which corresponds to the first horizontal partition group;

receiving a second data message sent by the route receiving end node, wherein the second data message is obtained by encapsulating a first data message received from a first AC according to the route for carrying an ESI tag by the route receiving end node, the second data message carries a tag for identifying the first horizontal partition group, and the first AC is an AC matched according to the route for carrying the ESI tag;

filtering the AC in the first horizontal split group while broadcasting the first data message.

According to another embodiment of the present application, there is also provided a data packet processing apparatus applied to a route receiving end node, the apparatus including:

the first receiving module is used for receiving a route which is issued by a route transmitting end node and corresponds to the AC in the first horizontal partition group and used for carrying an ESI label, wherein the route used for carrying the ESI label carries a label for marking the first horizontal partition group and a route target RT corresponding to the first horizontal partition group;

The encapsulating module is configured to encapsulate, when an RT corresponding to the first horizontal split group is matched with an incoming RT of a second horizontal split group where a first AC is located, a first data packet received from the first AC into a second data packet, where the second data packet carries a tag for identifying the first horizontal split group, and the first AC is an AC belonging to the second horizontal split group on the route receiving end node;

and the first sending module is used for sending the second data message to the routing sending end node so that the routing sending end node filters the ACs in the first horizontal division group when broadcasting the first data message.

According to another embodiment of the present application, there is also provided a data packet processing apparatus applied to a route sender node, the apparatus including:

the issuing module is used for issuing a route which corresponds to the AC in the first horizontal partition group and is used for carrying an ESI label to the route receiving end node, wherein the route which is used for carrying the ESI label carries a label for identifying the first horizontal partition group and a route target RT which corresponds to the first horizontal partition group;

A second receiving module, configured to receive a second data packet sent by the routing receiving end node, where the second data packet is obtained by the routing receiving end node encapsulating, according to the route for carrying an ESI tag, a first data packet received from a first AC, where the second data packet carries a tag identifying the first horizontal partition group, and the first AC is an AC matched according to the route for carrying an ESI tag;

and the filtering module is used for filtering the ACs in the first horizontal division group when the first data message is broadcast.

According to a further embodiment of the present application, there is also provided a computer readable storage medium having stored therein a computer program, wherein the computer program is arranged to perform the steps of any of the method embodiments described above when run.

According to a further embodiment of the present application, there is also provided an electronic device comprising a memory having stored therein a computer program and a processor arranged to run the computer program to perform the steps of any of the method embodiments described above.

In the embodiment of the application, a route which is issued by a route sending end node and corresponds to an AC in a first horizontal partition group and used for carrying an ESI label is received, wherein the route used for carrying the ESI label carries a label for marking the first horizontal partition group and a route target RT corresponding to the first horizontal partition group; under the condition that RT corresponding to the first horizontal partition group is matched with the imported RT of a second horizontal partition group where a first AC is located, packaging a first data message received from the first AC into a second data message, wherein the second data message carries a label for identifying the first horizontal partition group, and the first AC is the AC belonging to the second horizontal partition group on the routing receiving end node; the second data message is sent to the routing sending end node, so that the routing sending end node filters the ACs in the first horizontal segmentation group when broadcasting the first data message, the problem that a horizontal segmentation mechanism based on ESI label extension group attributes cannot realize horizontal segmentation across ES in the related technology can be solved, and the label of the label horizontal segmentation group is packaged into the data message, so that a node receiving the data message filters the ACs in the same horizontal segmentation group across frames when broadcasting the data message, namely does not forward the ACs in the same horizontal segmentation group, and horizontal segmentation across ES is realized.

Drawings

FIG. 1 is a schematic diagram of a horizontal segmentation mechanism based on ESI tag extended community attributes in accordance with the related art;

FIG. 2 is a block diagram of the hardware architecture of a computer device of the data message processing method according to the embodiment of the present application;

FIG. 3 is a flowchart I of a data message processing method according to an embodiment of the present application;

FIG. 4 is a second flowchart of a data message processing method according to an embodiment of the present application;

FIG. 5 is a schematic diagram of a horizontal split group across nodes across ES according to an embodiment of the present application;

FIG. 6 is a block diagram I of a data message processing apparatus according to an embodiment of the present application;

fig. 7 is a block diagram two of a data packet processing device according to an embodiment of the present application.

Detailed Description

Embodiments of the present application will be described in detail below with reference to the accompanying drawings in conjunction with the embodiments.

It should be noted that the terms "first," "second," and the like in the description and claims of the present application and the above figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order.

The method embodiments provided in the embodiments of the present application may be performed in a computer device or similar computing apparatus. Taking a mobile terminal as an example, fig. 2 is a block diagram of a hardware structure of a computer device of the data packet processing method according to the embodiment of the present application, as shown in fig. 2, the computer device may include one or more (only one is shown in fig. 2) processors 102 (the processors 102 may include, but are not limited to, a microprocessor MCU or a programmable logic device FPGA, etc. processing means) and a memory 104 for storing data, where the computer device may further include a transmission device 106 for a communication function and an input/output device 108. It will be appreciated by those of ordinary skill in the art that the configuration shown in FIG. 2 is merely illustrative and is not intended to limit the configuration of the computer device described above. For example, the computer device may also include more or fewer components than shown in FIG. 2, or have a different configuration than shown in FIG. 2.

The memory 104 may be used to store a computer program, for example, a software program of application software and a module, such as a computer program corresponding to a data packet processing method in the embodiment of the present application, and the processor 102 executes the computer program stored in the memory 104, thereby performing various functional applications and service chain address pool slicing processing, that is, implementing the method described above. Memory 104 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, memory 104 may further include memory located remotely from processor 102, which may be connected to the computer device via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The transmission means 106 is arranged to receive or transmit data via a network. Specific examples of the network described above may include a wireless network provided by a communications provider of the computer device. In one example, the transmission device 106 includes a network adapter (Network Interface Controller, simply referred to as NIC) that can connect to other network devices through a base station to communicate with the internet. In one example, the transmission device 106 may be a Radio Frequency (RF) module, which is used to communicate with the internet wirelessly.

In this embodiment, a data message processing method running on the computer device or the network architecture is provided, and fig. 3 is a flowchart of a data message processing method according to an embodiment of the present application, as shown in fig. 3, where the flowchart includes the following steps:

step S302, a route which is issued by a route sending end node and corresponds to an AC in a first horizontal partition group and used for carrying an ESI label is received, wherein the route which is used for carrying the ESI label carries a label for identifying the first horizontal partition group and a route target RT corresponding to the first horizontal partition group;

it should be noted that, the access circuit (Attachment Circuit, abbreviated as AC) may be a channel on an entity capable of being used as vES (virtual ES), for example, PW is an entity capable of being used as vES, and PW itself is a channel, so that the AC may be PW; this type of AC may be referred to as a virtual AC.

Note that, the route defined in RFC7432 for carrying an ESI tag is an ES-level Ethernet Auto-discoveryRoute perES (ES-level first-class EVPN route, also referred to as an ES-level RT-1 route) where the ESI is not a reserved value, but other routes may exist in the future for carrying an existing ESI tag, which is generally referred to as a route for carrying an ESI tag in this embodiment.

In an alternative embodiment, the AC corresponding to the route for carrying the ESI label is a second AC, the route for carrying the ESI label further carries a first ESI, a Designated Forwarder (DF) election is performed for the second AC according to the first ESI, and forwarding of a Broadcast, unknown unicast and multicast (BUM) message corresponding to the second AC is performed according to a DF election result, specifically, if the DF election result is DF, a BUM message crossing the horizontal split group may be forwarded, and if the election result is non-DF, the BUM message cannot be forwarded.

Step S304, when RT corresponding to the first horizontal partition group is matched with the imported RT of the second horizontal partition group where the first AC is located, packaging the first data message received from the first AC into a second data message, wherein the second data message carries a label for identifying the first horizontal partition group, and the first AC is an AC belonging to the second horizontal partition group on the route receiving end node, and specifically, the first AC can be any AC in the second horizontal partition group;

it should be noted that this embodiment adopts three concepts of a horizontal split group, an intra-frame horizontal split group, and a cross-frame horizontal split group. When BUM messages are not forwarded between two ACs, the two ACs are said to belong to the same horizontal partition group; the in-frame horizontal partition group is a horizontal partition group in which all ACs in the group are in the same node; when two intra-chassis horizontal split groups distributed on different chassis in the same ethernet virtual private network (Ethernet Virtual Private Network, abbreviated as EVPN) service cannot communicate with each other, the two intra-chassis horizontal split groups are said to belong to the same inter-chassis horizontal split group (that is, member ACs of the two intra-chassis horizontal split groups are member ACs of the same inter-chassis horizontal split group). The present embodiment is a technique of disabling communication between horizontal split groups in different racks, and thus is a technique of constructing at least two horizontal split groups in a rack into the same cross-rack horizontal split group. In addition, when a horizontal split group in a certain rack belongs to a certain cross-rack horizontal split group, the intra-rack horizontal split group is referred to as a horizontal split group component of the cross-rack horizontal split group.

The first horizontal split group and the second horizontal split group in the present embodiment are intra-rack horizontal split groups inside the respective nodes, but when the export RT of the first horizontal split group matches the import RT of the second horizontal split group and the export Route Target (simply referred to as RT) of the second horizontal split group matches the import RT of the first horizontal split group, it can be determined according to the present embodiment that the first horizontal split group and the second horizontal split group belong to the same cross-rack horizontal split group because, at this time, it can be determined that the AC in the first horizontal split group and the AC in the second horizontal split group cannot communicate with each other, in short, the first horizontal split group and the second horizontal split group cannot communicate, but in this case, the horizontal split group identifiers of the first horizontal split group and the second horizontal split group are different as long as the RTs thereof match each other.

Step S306, the second data message is sent to the route sending end node, so that the route sending end node filters the ACs in the first horizontal split group when broadcasting the first data message.

It should be noted that the first data packet in step 306 is the first data packet encapsulated in the second data packet in step 304. The first horizontal split group is determined according to a tag contained in the second data message that identifies the first horizontal split group. The broadcasting the first data message is that the first data message is forwarded when the first data message is a BUM (Broadcast, unknown Unicast and Multicast) message. In an alternative embodiment, the AC in step 306 is a designated repeater (designated Forwarder, abbreviated DF).

It should be noted that, there may be multiple ACs in the first horizontal partition group, where the ACs may be on different ESs, and the route for carrying the ESI label is a route corresponding to one of the ACs, and the route sending end node filters any AC in the first horizontal partition group when broadcasting the first data packet, and not just filters the AC corresponding to the route for carrying the ESI label.

Through the steps S302 to S306, the problem that the horizontal segmentation mechanism based on the ESI tag extended community attribute in the related art cannot realize the horizontal segmentation of the cross ES can be solved, and the tag identifying the horizontal segmentation group is encapsulated into the data packet, so that the node receiving the data packet filters the AC in the same cross-rack horizontal segmentation group, i.e. does not forward the AC in the same cross-rack horizontal segmentation group, thereby realizing the horizontal segmentation of the cross ES.

Note that, a label identifying a horizontal split group in a certain rack is also referred to as a horizontal split group label of the horizontal split group in the rack in this embodiment.

In an embodiment, the label identifying the first horizontal split group may be carried in particular by a TLV for carrying ESI labels for routing carrying ESI labels.

It should be noted that, the TLV defined by RFC7432 for carrying an ESI tag is referred to as an ESI tag extension group attribute, and other attributes may exist in the future and may also be used to carry an ESI tag, and these attributes are all referred to as "TLV for carrying an ESI tag" in this embodiment. In other embodiments, the horizontal split group label may also be carried with routing attributes that are not responsible for carrying the ESI label.

In an embodiment, in a case where the RT corresponding to the first horizontal split group is the derived RT corresponding to the first horizontal split group, the route for carrying the ESI label further carries first indication information, where the first indication information is used to indicate that the RT corresponding to the first horizontal split group is used to match the imported RT of the second horizontal split group where the first AC is located.

When the export RT and the import RT of the same horizontal partition group are equal, it may not be explicitly indicated on the user interface as the export RT or the import RT, and therefore, if the RT identifying the local horizontal partition group carried in the locally distributed route is the export RT of the local horizontal partition group, the RT identifying the local horizontal partition group for matching with the received RT of the route is the import RT of the local horizontal partition group.

In an embodiment, before the step S304, the method may further include: matching the import RT of the local second horizontal partition group according to the export RT corresponding to the first horizontal partition group; if the lead-in RT is matched with the lead-in RT of the second horizontal division group, at least establishing a first table entry of a first forwarding table by taking the second horizontal division group and a route sending end node as indexes; if the second data packet is a BUM data packet forwarded to the routing sender node, searching the first forwarding table by using at least the second horizontal partition group and the routing sender node as indexes (i.e. at least using identifiers of both the second horizontal partition group and the routing sender node as indexes), and if the first table entry is found, obtaining a label identifying the first horizontal partition group according to the first table entry.

It should be noted that, at a given node, there may be three allocation methods for the horizontal split group label:

mode one: all intra-rack horizontal split groups with the same horizontal split group identifier share the same horizontal split group tag, regardless of which ESI the member of the intra-rack horizontal split group (such as AC) belongs to, and regardless of which (EVPNInstance, abbreviated as EVI) the intra-rack horizontal split group is in;

Mode two: different horizontal split group labels are adopted for the horizontal split groups with the same horizontal split group identifier in different EVIs;

mode three: the ESI tag is used as a horizontal split group tag. One of the water mark splitting group identifiers can be selected on each ESI, and the ESI label is used as the horizontal splitting group label by the horizontal splitting group corresponding to the horizontal splitting group identifier, but the horizontal splitting group label distributed in the first mode or the second mode can still be used by the horizontal splitting group on other ESIs. At most one horizontal split group per EVI per ES may be used in way three.

In this embodiment, when the horizontal split group tag is allocated in the second mode, the first entry of the first forwarding table must be constructed and queried with at least identifiers of the following three: a second horizontal split group (being an intra-chassis horizontal split group), the EVI to which the route for carrying the ESI label belongs, and a route sender node. When the horizontal split group label is allocated in the third mode, how the first forwarding table is constructed depends on whether the node for allocating the horizontal split group label in the second mode exists in the network, and if so, the first forwarding table and the second forwarding table can also be constructed and queried by using identifiers of the first forwarding table, the second forwarding table and the third forwarding table as indexes.

In an embodiment, the method may further include: and before the RT corresponding to the first horizontal partition group is matched with the imported RT of the second horizontal partition group where the first AC is located, configuring or automatically mapping a route target for the second horizontal partition group, wherein when the route target is automatically mapped for the second horizontal partition group, the route target is used as both the exported RT and the imported RT. Further, the routing target is automatically mapped by the domain identifier and the horizontal partition group identifier as a second horizontal partition group, wherein the routing target is determined according to the domain identifier and the horizontal partition group identifier, the domain identifier is a global identifier for identifying a network where the EVPN service is located, and the horizontal partition group identifier is a global identifier for identifying the horizontal partition group in the network.

In an embodiment, the step S304 may specifically include: and encapsulating the first data message by adding the label for identifying the first horizontal division group to the outer layer of the first data message to obtain a second data message.

In one embodiment, all horizontal split groups with the same horizontal split group identifier at the route sender node share the same horizontal split group label (i.e., mode one); or different horizontal split group labels are adopted by the same horizontal split group identifier in different EVIs on the route sending end node (i.e. mode two).

In an embodiment, before the step S304, the method further includes: in the case that different horizontal split group labels (i.e., mode two) are adopted by the horizontal split group with the same horizontal split group identifier on different EVIs on the route sending end node, and the route for carrying the ESI label also carries the RT of the identifier EVI, it is determined that the RT of the identifier EVI matches the RT of the EVI of the local first AC.

In one embodiment, no label is added to the second data packet that corresponds to the MPLS label field in the provider multicast service interface (Provider Multicast Service Interface, abbreviated PMSI) tunnel attribute of the inclusive multicast ethernet label IMET route. In this case, the horizontal split group label is allocated in the second mode.

In an embodiment, the method further includes: the route for carrying the ESI label also carries the ESI, and matches the ESI with the ESI corresponding to the local first AC under the condition that the RT corresponding to the first horizontal partition group is not matched with the imported RT of the second horizontal partition group where the first AC is located; if the matching is successful, when the first data message received from the first AC is encapsulated into the second data message, adding a label value in a TLV (TLV) for carrying the ESI label for the route carrying the ESI label into the second data message.

In an embodiment, the method further includes: when the first condition is met, adding a tag identifying a first horizontal split group according to a first forwarding table before encapsulating a first data packet received from a first AC into a second data packet; when the first condition is not met, matching the ESI with the ESI corresponding to the local first AC, and if the matching is successful, adding a label value in a TLV (TLV) for carrying an ESI label for carrying a route of the ESI label into a second data message when the first data message received from the first AC is packaged into the second data message; the first condition is a second condition or a third condition, the second condition is that second indication information and third indication information exist simultaneously, the third condition is that third indication information exists, the second indication information is indication information written on the first AC when at least one table item corresponding to a second horizontal division group exists in the first forwarding table, and the third indication information is indication information written in a flooding list (flood list) table item corresponding to a route sending end node in an EVI every time at least one table item corresponding to the certain EVI and the route sending end node exists in the first forwarding table.

It should be noted that, the flooding list may be a forwarding table constructed according to the IMET route issued by the route sender node for the EVI.

In this embodiment, the route for carrying the ESI tag further carries an ESI, and the first AC does not belong to an ES corresponding to the ESI.

In an embodiment, the route for carrying the ESI label further carries fourth indication information, and it is determined according to the fourth indication information that the label corresponding to a multiprotocol label switching (Muti-Protocol Label Switching, abbreviated as MPLS) label field in the PMSI tunnel attribute of the inclusive multicast ethernet label IMET route is not added in the second data packet, and in an optional embodiment, the fourth indication information may be the first indication information.

In this embodiment, further, when the first data packet is a BUM packet, it is determined that a flow label is added to the second data packet according to the fourth indication information.

In one embodiment, there are at least two cross-chassis horizontal split groups in the EVI to which the route for carrying the ESI label belongs.

According to another embodiment of the present application, there is further provided a data packet processing method applied to a routing sender node, and fig. 4 is a second flowchart of the data packet processing method according to the embodiment of the present application, as shown in fig. 4, where the method includes:

Step S402, issuing a route which is corresponding to the AC in the first horizontal partition group and is used for carrying an ESI label to a route receiving end node, wherein the route which is used for carrying the ESI label carries a label for identifying the first horizontal partition group and a route target RT which corresponds to the first horizontal partition group;

step S404, receiving a second data message sent by a route receiving end node, wherein the second data message is obtained by encapsulating a first data message received from a first AC according to a route for carrying an ESI label, the second data message carries a label for identifying the first horizontal split group, and the first AC is an AC matched according to the route for carrying the ESI label;

specifically, the first AC is an AC belonging to the second horizontal split group at the route receiving end node.

In step S406, the AC in the first horizontal split group is filtered when the first data packet is broadcast.

Through the steps S402 to S406, the problem that the horizontal segmentation mechanism based on the ESI label cannot realize horizontal segmentation across ESs in the related art can be solved, and the horizontal segmentation across ES is realized by encapsulating the horizontal segmentation group label into the data message, so that the node receiving the data message filters the AC in the same horizontal segmentation group, i.e. does not forward to the AC in the same horizontal segmentation group, when broadcasting the data message.

In an embodiment, the route for carrying an ESI tag further carries an ESI, and the first AC does not belong to an ES corresponding to the ESI.

In an optional embodiment, the AC corresponding to the route for carrying the ESI label is a second AC, the route for carrying the ESI label further carries a first ESI, DF elections are performed for the second AC according to the first ESI, and forwarding the BUM message corresponding to the second AC according to DF election results, specifically, if the DF election results are DF, the BUM message may be forwarded, and if the election results are non-DF, the BUM message cannot be forwarded.

It should be noted that, the first data packet is encapsulated into the second data packet according to the received route for carrying the ESI label, and specifically, when the RT corresponding to the first horizontal split group matches with the incoming RT of the second horizontal split group where the first AC is located, the first data packet received from the first AC is encapsulated to obtain the second data packet.

In an embodiment, a routing target is configured or automatically mapped for the first horizontal split set, wherein when the routing target is automatically mapped for the first horizontal split set, the routing target serves as both an export RT and an import RT. Further, the domain identifier and the horizontal partition group identifier are used for automatically mapping a routing target for the first horizontal partition group, wherein the routing target is determined according to the domain identifier and the horizontal partition group identifier, the domain identifier is a global identifier for identifying a network where the EVPN service is located, and the horizontal partition group identifier is a global identifier for identifying the horizontal partition group in the network.

In an embodiment, there is also a second AC in the first horizontal split group, the first data message is a BUM message and the first data message is not sent to the second AC and the ESI for the route carrying the ESI label is not the ESI of the ES where the second AC is located.

In an embodiment, the method further includes: a tag identifying the first horizontal split group is assigned to the first horizontal split group.

The present embodiment will be described in detail by way of specific examples.

Fig. 5 is a schematic diagram of a cross-node cross-ES horizontal partition group according to an embodiment of the present application, as shown in fig. 5, which is a common EVPN network, four CEs belong to ES1, ES2, ES3, and ES4, respectively, and corresponding ESIs are ESI401, ESI203, ESI431, and ESI204, respectively, where four PE nodes of PE1, PE2, PE3, and PE4 establish tunnel interworking through an underway network (not shown in the figure), ESIx0y indicates that an ES identified by the ESI spans PEx and PEy two PE nodes, and ESIxyz indicates that an ES identified by the ESI spans PEx, PEy, and PEz three PE nodes.

According to RFC7432, each of ES1, ES2, ES3, and ES4 has a horizontal division function independent of each other, and there is no horizontal division function between different ESs.

Here, on this EVPN network, it is assumed that there are two EVPN services, EVI201 and EVI202, where an AC with VLAN ID 201 on ES1/ES2/ES3/ES4 is assigned to EVI201 and an AC with VLAN ID 202 on ES1/ES2/ES3/ES4 is assigned to EVI202.

Wherein, the AC of EVI201 on ES1/ES2/ES3/ES4 is respectively denoted as AC2011/AC2012/AC2013/AC2014, and the AC of EVI202 on ES1/ES2/ES3/ES4 is respectively denoted as AC2021/AC2022/AC2023/AC2024.

As shown in fig. 5, in the EVI201, by implementing the embodiment of the present application, ES1 and ES2 are made to belong to the same cross-chassis horizontal split group (denoted as horizontal split group a, corresponding to the same cross-chassis horizontal split group consisting of the first horizontal split group and the second horizontal split group described above), while ES3 and ES4 are made to belong to another cross-chassis horizontal split group (denoted as horizontal split group B), on the basis of RFC 7432. A more narrow implementation of the so-called horizontal split group is: the members in the same horizontal partition group do not forward BUM messages, but the members in different horizontal partition groups can forward BUM messages.

In other words, in EVI201, AC2011 (including AC2011 on PE1 and AC2011 on PE 4) and AC2012 (including AC2012 on PE3 and AC2012 on PE 2) make up across-rack horizontal split group a, while AC2013 (including AC2013 on PE1, AC2013 on PE3, and AC2013 on PE 4) and AC2014 (including AC2014 on PE2 and AC2014 on PE 4) make up across-rack horizontal split group B.

For convenience of description, AC201x on PEy is denoted as AC201x_y.

Note that, the horizontal split group division (not shown in the figure) in the EVI202 may be inconsistent with the horizontal split group division in the EVI201 (for example, in the EVI202, ES1 and ES3 may form one cross-rack horizontal split group, and ES2 and ES4 form another cross-rack horizontal split group), but this embodiment describes an implementation of the cross-rack cross-ES multi-horizontal split group only by taking the horizontal split group division in the EVI201 as an example. The method specifically comprises the following steps:

s101, in EVI201, configuring a horizontal split group a (i.e., a horizontal split group identifier with a configuration value of a) for each AC2011 (including AC2011 on PE1 and AC2011 on PE 4) and each AC2012 (including AC2012 on PE3 and AC2012 on PE 2), and simultaneously configuring a horizontal split group B for each AC2013 (including AC2013 on PE1, AC2013 on PE3 and AC2013 on PE 4) and each AC2014 (including AC2014 on PE2 and AC2014 on PE 4), wherein a node where the horizontal split group a exists automatically maps a pair of routing targets for the horizontal split group a, including an export routing target RTaex and an import routing target RTaim, and a node where the horizontal split group B exists automatically maps a pair of routing targets for the horizontal split group B, including an export routing target rtax and an import routing target RTaim; the automatically mapped RTaim may be equal to RTaex and the RTbim may be equal to RTbex; the RTxim/RTxex mapped by different PEs for the same horizontal partition group X (e.g. horizontal partition group a or horizontal partition group B) needs to be the same value, which can be guaranteed by the first mapping method. The first mapping method comprises the following steps: rtxim=rtxex= < domain identification, horizontal split group identification >, where a domain identification is a global identifier identifying a network where the EVPN service is located (referred to as an EVPN domain of the EVPN service), and a horizontal split group identification is a global identifier identifying the horizontal split group X. Each node in the EVPN domain has the same domain identification, and the horizontal partition group X is configured with the same horizontal partition group identification on each node in the EVPN (for example, "a" may be used as the identification of the horizontal partition group a).

It should be noted that, in the EVI201, taking the horizontal partition group B as an example, the AC2013_4 and the AC2014_4 form one intra-frame horizontal partition group of the PE4 (denoted as the intra-frame horizontal partition group B), one object of this embodiment is to construct one inter-frame horizontal partition group (i.e., the inter-frame horizontal partition group B) with the intra-frame horizontal partition group as one of the components, and similarly, the AC2013_1, the AC2013_3 and the AC2014_2 also respectively belong to different horizontal partition group components (i.e., corresponding intra-frame horizontal partition groups) of the inter-frame horizontal partition group B, and the AC2011_1, the AC2011_4, the AC2012_3 and the AC2012_2 also respectively belong to different horizontal partition group components (i.e., corresponding intra-frame horizontal partition groups) of the inter-frame horizontal partition group a.

S102, a node provided with the horizontal partition group A is allocated with a special horizontal partition group label for the horizontal partition group A (namely, allocated with a horizontal partition group component of the node crossing the machine frame horizontal partition group A), and a node provided with the horizontal partition group B is allocated with a special horizontal partition group label for the horizontal partition group B (namely, allocated with a horizontal partition group component of the node crossing the machine frame horizontal partition group B); wherein, the horizontal split group label allocated by PEm for the horizontal split group x is denoted as Lmx, for example, the horizontal split group label allocated by PE2 for the horizontal split group A is denoted as L2a;

S103, each PE reissues RT-1per ES route (namely, ES-level Ethernet Auto-discovery route, ethernet Auto-discovery Route perES, namely, ES-level RT-1 route, which is a route for carrying ESI labels) for the AC configured with the horizontal split group, wherein the RT-1per ES route issued for the AC201x_y by PEy is denoted as R201ESxPEy (corresponding to the route for carrying ESI labels), such as for example, the RT-1per ES route issued for the AC2012_2 on the PE2 is denoted as R201ES2PE2 (wherein PE2 is a route sender node for this route); wherein, the RD of R201ESxPEy carries the RD of EVI201, its ESI label extended Group attribute carries ESx, which accesses, on PEy, the horizontal Split Group label of the intra-rack horizontal Split Group (corresponding to the first horizontal Split Group) to which the AC of EVI201 (i.e., AC201x on PEy) belongs, taking R201ES2PE2 as an example, its route destination RT carries RTaex in addition to the RT carrying the identifier EVI201, and RTaex is carried by a new route destination format (i.e., including the first indication information described above) to be different from the RT of EVI201, and this new route destination format is called horizontal Split Group Import SHG-Import (Split-Horizon Group-Import);

s104, after each PE receives each R201ESxPEy route, the routing target in the SHG-report RT format carried in the routing target matches RTxim of a local horizontal partition group, the horizontal partition group X is hit (that is, one RTxim of the horizontal partition group X is matched with the routing target in the SHG-report RT format), a horizontal partition group distribution table (corresponding to the first forwarding table) table entry SHLxPEy is established, the SHLxPEy takes identifiers of the three horizontal partition groups X, EVI (EVI 201 can be determined through RT carried in R201 ESxPEy) and PEy as indexes, and a horizontal partition group label Lyx can be queried through the SHLxPEy; taking the example that the PE1 receives the R201ES2PE2 route (that is, the route receiving end node of the R201ES2PE2 route), the horizontal partition group X that is hit (that is, the route target of the SHG-report RT format of the route receiving end node may match the route target of the horizontal partition group in a certain rack on the PE 1) is the horizontal partition group a, so the table entry of the horizontal partition group distribution table is established as the SHLaPE2, and the label allocated by the PE2 for the horizontal partition group a is L2a and the corresponding Lyx is L2a, so the result of querying the horizontal partition group distribution table is that the horizontal partition label on the PE2 is L2a when the horizontal partition label on the PE2 is hit.

S105, taking AC2011_1 as an example, PE1 receives a BUM packet P1 (corresponding to the first data packet) from AC2011_1 (corresponding to the first AC), before broadcasting BUM packet P1 to PE2 according to the flooding list table entry ire201_2, because AC2011_1 belongs to the horizontal partition group a (specifically, AC2011_1 belongs to a horizontal partition group component across the rack horizontal partition group a, this horizontal partition group component is an intra-rack horizontal partition group, this intra-rack horizontal partition group corresponds to the second horizontal partition group), and therefore, the identifiers of the horizontal partition groups A, EVI and PE2 are used as indexes to query the horizontal partition group distribution table, and as a result, the horizontal partition group label L2a is obtained therefrom (corresponding to the first table entry), and the label L2a is used to replace the ESI label to encapsulate P1 according to 7432 to obtain the message MEP1 (corresponding to the second data packet), so that the label L2a carries the label L2a (corresponding to the label L2 b) and sends the label L2 to the PE 1. It should be noted that, if the lookup table cannot hit any entry, the forwarding process of obtaining the ESI tag according to the ESI in RFC7432 is still to be continued.

At S106, PE2 receives MEP1, and from L2a carried in MEP1, it can be known that the message encapsulated by MEP1 (i.e., P1) originates from a member (such as AC 2011_1) in the horizontal partition group a, and PE2 cannot broadcast P1 to AC2012_2, but can broadcast to AC2014_2, because AC2012_2 belongs to the horizontal partition group a, and AC2014_2 does not belong to the horizontal partition group a. BUM messages are not forwarded in the same horizontal division group, and BUM messages can be forwarded among different horizontal division groups.

In an alternative embodiment, in step S102, a horizontal split group label is allocated in a manner, and in steps S104 and S105, a horizontal split group distribution table entry corresponding to the route R201ESxPEy is constructed or queried with the identifiers of both horizontal split groups z and PEy as indexes, where the horizontal split group z is an intra-frame horizontal split group corresponding to R201ESxPEy on the route receiving end node (assumed to be PE 1) of R201ESxPEy (taking R201ES2PE2 as an example, and the horizontal split group z corresponding thereto is an intra-frame horizontal split group a on PE 1).

In an alternative embodiment, in step S104, each time there is at least one horizontal partition group distribution table entry in the horizontal partition group X, an indication information F1 (i.e., the second indication information) is written on each AC locally belonging to the horizontal partition group X, and each time there is at least one horizontal partition group distribution table entry corresponding to the far end PEy in the EVI201, an indication information F2 (i.e., the third indication information) is written in a flooding list table entry (denoted as ire201_y) corresponding to PEy in the EVI 201. In this embodiment, in the above step S105, since AC2011_1 belongs to the horizontal partition group a, and there is F1 indication information in AC2011_1 and F2 indication information in ire201_2 (i.e. the second condition), the horizontal partition group distribution table is queried with the three of the horizontal partition group A, EVI and PE2 as indexes, and as a result, the SHLaPE2 table entry is hit, the horizontal partition group label is obtained therefrom as L2a, and the label L2a is used to replace ESI label to encapsulate P1 according to RFC7432 to obtain the message MEP1, so that the label L2a is carried in the MEP1 and the MEP1 is sent to the PE2. In this embodiment, if the second condition is not met, forwarding is still performed as in RFC 7432.

In an alternative embodiment, the third condition may also be used instead of the second condition, in which only the indication information F2 (i.e. the third indication information) is used instead of the indication information F1. In this embodiment, in S103, it is necessary to ensure that the ACs on different PE nodes in the same EVI of the same ES belong to the same cross-chassis horizontal split group, and that the PE nodes supporting this embodiment are all on the same ES.

It should be noted that, based on the scheme in the embodiment of the third condition or the second condition, the forwarding is performed by looking up the horizontal split group distribution table (i.e. the first forwarding table), or the forwarding is performed according to RFC7432, so that the process of looking up the horizontal split group distribution table first and then executing the process of acquiring the ESI label according to the ESI in RFC7432 is avoided, thereby simplifying the forwarding process, improving the forwarding efficiency, and reducing the requirement on forwarding hardware.

In an alternative embodiment, in the above step S101, RTaex/RTaim and RTbex/RTaim are not automatically mapped, but are manually configured, wherein in the same pair of PEs (denoted as PEm and PEn), the PEm-configured RTaex is the same as the PEm-configured RTaim, and the PEm-configured RTaim is the same as the PEm-configured RTaex, in other words, the configured RTaex and RTaim are symmetrical to each other between the same pair of PEs. It should be noted that RTaex and RTaim may be equal on the same PE.

In an embodiment, whether the same cross-chassis horizontal split group may be determined by the following rules: the ACs on two different racks which do not forward BUM messages belong to the same cross-rack horizontal partition group, and the two ACs which can forward BUM messages belong to different cross-rack horizontal partition groups. Whether the ACs of two cross-PE nodes belong to the same cross-chassis horizontal split group, in this embodiment, it does not necessarily have to be related to whether their horizontal split group identifiers are the same value, but is determined by the matching relationship of the routing targets, so long as the derived RT of a certain horizontal split group on one PE can match the imported RT of a certain horizontal split group on the other PE, even if the horizontal split group identifiers of the two horizontal split groups are not the same value, both may be the same cross-chassis horizontal split group.

In an optional present embodiment, in the step S102, dedicated horizontal split group labels are respectively allocated to the horizontal split groups having the same value of the horizontal split group identifiers in different EVIs (i.e. the horizontal split group labels are allocated in the second mode), and accordingly, the TLV for carrying the ESI label in the RT-1per ES route issued for different EVIs in S103 is the same as the value of the dedicated horizontal split group label of the horizontal split group to which the corresponding AC belongs in the EVI; at this time, the Label carried in the MPLS Label field in the PMSI Tunnel attribute of the (or may be encapsulated) inclusive multicast ethernet Label (Inclusive Multicast Ethernet Tag, abbreviated as IMET) route may not be encapsulated, and only the horizontal split group Label needs to be encapsulated.

It should be noted that, by adopting the second mode to allocate the horizontal split group label and carrying the fourth indication information when issuing the route, the label stack layer number can be reduced by one layer label when the EVPN BUM message is forwarded, thereby saving the bandwidth, and the BUM message forwarding also has the capability of overlapping with the flow label, thereby solving the problem that the EVPN BUM message forwarding cannot support the flow label.

In an alternative embodiment, it is assumed that the horizontal split group identifiers of several ACs under the same ESI in the EVI instance to which they belong are all the same, at this time, for the horizontal split groups corresponding to these ACs, the original ESI label may be directly used as the horizontal split group label of the horizontal split group with the horizontal split group identifier (i.e., the horizontal split group label is allocated in the manner of three), and for other ACs on the ESI, the horizontal split group label allocated in the manner of one or two is still required to be used.

When the horizontal split group tag is assigned in the second mode, the same horizontal split group may be assigned different horizontal split group tags for different ESIs. At this time, the horizontal split group labels carried in the RT-1per ES route issued for the ACs on different ESs in the same horizontal split group are also different.

It should be noted that, even if two ACs belonging to different EVI instances are respectively configured with the same horizontal split group identifier, the two ACs essentially belong to different intra-frame horizontal split groups, and even the intra-frame horizontal split groups to which the two ACs belong may have different member sets, for example, for PE4, in one EVI, the corresponding horizontal split group may include ES1 and ES3, and in the other EVI, the corresponding horizontal split group may include ES2 and ES3, and not include ES1.

According to another embodiment of the present application, there is further provided a data packet processing apparatus applied to a route receiving end node, and fig. 6 is a block diagram one of the data packet processing apparatus according to the embodiment of the present application, as shown in fig. 6, including:

the first receiving module is used for receiving a route which is issued by the route transmitting end node and corresponds to the AC in the first horizontal partition group and used for carrying an ESI label, wherein the route used for carrying the ESI label carries a label for identifying the first horizontal partition group and a route target RT corresponding to the first horizontal partition group;

the encapsulation module is used for encapsulating a first data message received from the first AC into a second data message under the condition that RT corresponding to the first horizontal segmentation group is matched with the imported RT of a second horizontal segmentation group where the first AC is located, wherein the second data message carries a label for identifying the first horizontal segmentation group, and the first AC is an AC belonging to the second horizontal segmentation group on a route receiving end node;

In an embodiment, the TLV for carrying the ESI label for the route carrying the ESI label carries a label identifying the first horizontal split group.

In an embodiment, in a case that the RT corresponding to the first horizontal split group is an derived RT corresponding to the first horizontal split group, the route for carrying the ESI label further carries first indication information, where the first indication information is used to indicate that the RT corresponding to the first horizontal split group is used to match an imported RT of the second horizontal split group where the first AC is located.

In an embodiment, the apparatus further includes:

the first matching module is used for matching the imported RT of the local second horizontal segmentation group according to the exported RT corresponding to the first horizontal segmentation group;

the establishing module is used for establishing a first table entry of a first forwarding table by taking at least the first horizontal partition group and the route sending end node as indexes if the first table entry is matched with the imported RT of the second horizontal partition group;

and the searching module is used for searching a first forwarding table by taking at least the first horizontal segmentation group and the routing sending end node as indexes if the second data message is the BUM data message forwarded to the routing sending end node, and obtaining a label for identifying the first horizontal segmentation group according to the first table item if the first table item is searched.

In an embodiment, the apparatus further includes:

and the first mapping module is used for configuring or automatically mapping a routing target for the second horizontal segmentation group before the RT corresponding to the first horizontal segmentation group is matched with the imported RT of the second horizontal segmentation group where the first AC is located, wherein when the routing target is automatically mapped for the second horizontal segmentation group, the routing target is used as both the exported RT and the imported RT.

In an embodiment, the first mapping module is further configured to automatically map a routing target for the second horizontal partition group through a domain identifier and a horizontal partition group identifier, where the routing target is determined according to the domain identifier and the horizontal partition group identifier, the domain identifier is a global identifier for identifying a network where the EVPN service is located, and the horizontal partition group identifier is a global identifier for identifying the horizontal partition group in the network.

In an embodiment, the encapsulation module 34 is further configured to encapsulate the first data packet by adding a tag identifying the first horizontal split group to an outer layer of the first data packet, so as to obtain a second data packet.

In one embodiment, all horizontal split groups with the same horizontal split group identifier on the route sender node share the same horizontal split group label; or different horizontal split group labels are adopted by the same horizontal split group identifier in different EVIs on the route transmitting end node.

In an embodiment, the apparatus further includes:

and the first determining module is used for determining that the RT of the identifier EVI is matched with the RT of the EVI of the local first AC under the condition that different horizontal segmentation group labels are adopted by the horizontal segmentation group with the same horizontal segmentation group identifier on different EVIs on the route sending end node and the route used for carrying the ESI label also carries the RT of the identifier EVI.

In an embodiment, no label corresponding to the MPLS label field in the PMSI tunnel attribute of the inclusive multicast ethernet label IMET route is added to the second data packet.

In an embodiment, the apparatus further includes:

the second matching module is used for carrying ESI in the routing carrying the ESI label, and matching the ESI with the ESI corresponding to the local first AC under the condition that the RT corresponding to the first horizontal division group is not matched with the imported RT of the second horizontal division group where the first AC is located;

and the first adding module is used for adding a label value in the TLV for carrying the ESI label for the route for carrying the ESI label in the second data message when the first data message received from the first AC is packaged into the second data message if the matching is successful.

In an embodiment, the apparatus further includes:

A second adding module, configured to add, when the first condition is satisfied, a tag identifying the first horizontal split group according to the first forwarding table before encapsulating the first data packet received from the first AC into the second data packet;

the third adding module is used for matching the ESI with the ESI corresponding to the local first AC when the first condition is not met, and adding a label value in a TLV (time limit value) used for carrying the ESI label and used for carrying the route of the ESI label into the second data message when the first data message received from the first AC is packaged into the second data message if the matching is successful;

the first condition is a second condition or a third condition, the second condition is that second indication information and third indication information exist simultaneously, the third condition is that third indication information exists, the second indication information is indication information written on the first AC when at least one table item corresponding to a second horizontal division group exists in the first forwarding table, and the third indication information is indication information written on a flooding list (flood list) table item corresponding to a route sending end node in the EVI every time at least one table item corresponding to a certain EVI and the route sending end node exists in the first forwarding table.

In an embodiment, the route for carrying the ESI tag further carries an ESI, and the first AC does not belong to an ES corresponding to the ESI.

In an embodiment, the device further comprises: the second determining module is configured to further carry fourth indication information in the route for carrying the ESI label, and determine that no label corresponding to the MPLS label field in the PMSI tunnel attribute of the inclusive multicast ethernet label IMET route is added in the second data packet according to the fourth indication information.

In another embodiment, the apparatus further comprises: and the fourth adding module is used for adding the flow label to the second data message when the first data message is the BUM message.

According to another embodiment of the present application, there is further provided a data packet processing apparatus applied to a routing sender node, and fig. 7 is a block diagram two of the data packet processing apparatus according to the embodiment of the present application, as shown in fig. 7, where the apparatus includes:

the issuing module is used for issuing a route which corresponds to the AC in the first horizontal partition group and is used for carrying the ESI label to the route receiving end node, wherein the route which is used for carrying the ESI label carries a label for identifying the first horizontal partition group and a route target RT which corresponds to the first horizontal partition group;

The second receiving module is used for receiving a second data message sent by the routing receiving end node, wherein the second data message is obtained by encapsulating a first data message received from a first AC according to a route for carrying an ESI label, the second data message carries a label for identifying a first horizontal division group, and the first AC is an AC matched according to the route for carrying the ESI label;

In one embodiment, the apparatus further comprises:

and the second mapping module is used for configuring or automatically mapping the routing targets for the first horizontal partition group, wherein when the routing targets are automatically mapped for the first horizontal partition group, the routing targets serve as an export RT and an import RT at the same time.

In an embodiment, the second mapping module is further configured to automatically map a routing target for the first horizontal partition group through a domain identifier and a horizontal partition group identifier, where the routing target is determined according to the domain identifier and the horizontal partition group identifier, the domain identifier is a global identifier for identifying a network where the EVPN service is located, and the horizontal partition group identifier is a global identifier for identifying the horizontal partition group in the network.

In an embodiment, there is a second AC in the first horizontal split group, the first data message is a BUM message and the first data message is not sent to the second AC and the ESI for the route carrying the ESI tag is not the ESI of the ES where the second AC is located.

In one embodiment, the apparatus further comprises:

an allocation module for allocating a tag identifying the first horizontal split group to the first horizontal split group.

Embodiments of the present application also provide a computer readable storage medium having a computer program stored therein, wherein the computer program is arranged to perform the steps of any of the method embodiments described above when run.

In one exemplary embodiment, the computer readable storage medium may include, but is not limited to: a usb disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a removable hard disk, a magnetic disk, or an optical disk, or other various media capable of storing a computer program.

Embodiments of the present application also provide an electronic device comprising a memory having a computer program stored therein and a processor arranged to run the computer program to perform the steps of any of the method embodiments described above.

In an exemplary embodiment, the electronic apparatus may further include a transmission device connected to the processor, and an input/output device connected to the processor.

Specific examples in this embodiment may refer to the examples described in the foregoing embodiments and the exemplary implementation, and this embodiment is not described herein.

It will be appreciated by those skilled in the art that the modules or steps of the application described above may be implemented in a general purpose computing device, they may be concentrated on a single computing device, or distributed across a network of computing devices, they may be implemented in program code executable by computing devices, so that they may be stored in a storage device for execution by computing devices, and in some cases, the steps shown or described may be performed in a different order than that shown or described herein, or they may be separately fabricated into individual integrated circuit modules, or multiple modules or steps of them may be fabricated into a single integrated circuit module. Thus, the present application is not limited to any specific combination of hardware and software.

The foregoing description is only of the preferred embodiments of the present application and is not intended to limit the same, but rather, various modifications and variations may be made by those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the principles of the present application should be included in the protection scope of the present application.

Claims

1. A method for processing a data packet, the method being applied to a routing receiver node, the method comprising:

2. The method of claim 1, wherein the step of determining the position of the substrate comprises,

the TLV for carrying ESI labels for the route for carrying ESI labels carries a label identifying the first horizontal split group.

3. The method of claim 1, wherein the step of determining the position of the substrate comprises,

in the case that the RT corresponding to the first horizontal split group is the derived RT corresponding to the first horizontal split group, the route for carrying the ESI label further carries first indication information, where the first indication information is used to indicate that the RT corresponding to the first horizontal split group is used to match the imported RT of the second horizontal split group where the first AC is located.

4. A method according to claim 3, wherein prior to said encapsulating the first data message received from the first AC into the second data message, the method further comprises:

matching the import RT of the local second horizontal partition group according to the export RT corresponding to the first horizontal partition group;

If the importing RT is matched with the importing RT of the second horizontal partition group, at least establishing a first table entry of a first forwarding table by taking the second horizontal partition group and the routing sending end node as indexes;

and if the second data message is the BUM data message forwarded to the routing sending end node, searching the first forwarding table at least by taking the second horizontal segmentation group and the routing sending end node as indexes, and if the first table item is searched, obtaining a label for identifying the first horizontal segmentation group according to the first table item.

5. The method according to claim 1, wherein the method further comprises:

before the RT corresponding to the first horizontal partition group is matched with the imported RT of a second horizontal partition group where the first AC is located, a routing target is configured or automatically mapped for the second horizontal partition group, wherein when the routing target is automatically mapped for the second horizontal partition group, the routing target is used as an exported RT and an imported RT at the same time.

6. The method of claim 1, wherein encapsulating the first data message received from the first AC into the second data message comprises:

and encapsulating the first data message by adding a label for identifying the first horizontal partition group to the outer layer of the first data message to obtain the second data message.

7. The method of claim 1, wherein the step of determining the position of the substrate comprises,

all the horizontal segmentation groups with the same horizontal segmentation group identifier on the route sending end node share the same horizontal segmentation group label; or alternatively

And the horizontal partition groups with the same horizontal partition group identifier on different EVIs on the route sending end node adopt different horizontal partition group labels.

8. The method of claim 7, wherein prior to encapsulating the first data message received from the first AC into the second data message, the method further comprises:

and under the condition that different horizontal split group labels are adopted by the horizontal split groups with the same horizontal split group identifiers on different EVIs on the route sending end node and the routes used for carrying ESI labels also carry RT of an identification EVI, determining that the RT of the identification EVI is matched with the RT of the local EVI of the first AC.

9. The method of claim 8, wherein the step of determining the position of the first electrode is performed,

and no label corresponding to the MPLS label field in the PMSI tunnel attribute of the inclusive multicast Ethernet mark IMET route is added in the second data message.

10. The method according to claim 1, wherein the method further comprises:

The route for carrying the ESI label also carries ESI, and when RT corresponding to the first horizontal partition group is not matched with the imported RT of the second horizontal partition group where the first AC is located, the ESI is matched with the local ESI corresponding to the first AC;

and if the matching is successful, when the first data message received from the first AC is encapsulated into a second data message, adding a label value in the TLV for carrying the ESI label in the route for carrying the ESI label in the second data message.

11. The method according to claim 4, wherein the method further comprises:

when a first condition is met, adding a label for identifying the first horizontal split group according to the first forwarding table before the first data message received from the first AC is encapsulated into a second data message;

when the first condition is not met, matching the ESI with the ESI corresponding to the local first AC, and if matching is successful, adding a tag value in the TLV for carrying the ESI tag of the route for carrying the ESI tag in a second data packet when the first data packet received from the first AC is packaged in the second data packet;

The first condition is a second condition or a third condition, the second condition is that second indication information and third indication information exist simultaneously, the third condition is that third indication information exists, the second indication information is that indication information is written on the first AC when at least one table item corresponding to the second horizontal splitting group exists in the first forwarding table, and the third indication information is that indication information is written on a flooding list table item corresponding to the routing sending end node in an EVI every time at least one table item corresponding to a certain EVI and the routing sending end node exists in the first forwarding table.

12. The method according to any one of claims 1 to 11, wherein,

the route for carrying the ESI label also carries an ESI, and the first AC does not belong to an ES corresponding to the ESI.

13. A method for processing a data packet, applied to a routing sender node, the method comprising:

14. The method of claim 13, wherein the step of determining the position of the probe is performed,

and configuring or automatically mapping a routing target for the first horizontal partition group, wherein when the routing target is automatically mapped for the first horizontal partition group, the routing target is used as an export RT and an import RT at the same time.

15. The method of claim 14, wherein automatically mapping routing targets for the first horizontal split group comprises:

and automatically mapping a routing target for the first horizontal partition group through a domain identifier and a horizontal partition group identifier, wherein the routing target is determined according to the domain identifier and the horizontal partition group identifier, the domain identifier is a global identifier for identifying a network where the EVPN service is located, and the horizontal partition group identifier is a global identifier for identifying the horizontal partition group in the network.

16. The method of claim 13, wherein the step of determining the position of the probe is performed,

a second AC exists in the first horizontal split group, the first data message is a BUM message and the first data message is not sent to the second AC and the ESI for the route carrying the ESI label is not the ESI of the ES in which the second AC is located.

17. A method according to any one of claims 13 to 16, wherein prior to the receiving route being issued by the sending end node for the ESI tag carrying route corresponding to the AC in the first horizontally split group, the method further comprises:

a tag identifying the first horizontal split group is allocated to the first horizontal split group.

18. A data message processing apparatus for use in routing a receiving end node, the apparatus comprising:

19. A data message processing apparatus for use in routing a sender node, the apparatus comprising:

a second receiving module, configured to receive a second data packet sent by the route receiving end node, where the second data packet is obtained by the route receiving end node encapsulating, according to the route for carrying an ESI tag, a first data packet received from the first AC, where the second data packet carries a tag identifying the first horizontal partition group, and the first AC is an AC matched according to the route for carrying an ESI tag;

20. A computer readable storage medium having a computer program stored therein, wherein the computer program is arranged to perform the method of any of claims 1 to 12, 13 to 17 when run.

21. An electronic device comprising a memory having stored therein a computer program and a processor arranged to run the computer program to perform the method of any of claims 1 to 12, 13 to 17.