CN107911301B

CN107911301B - Message forwarding method and device

Info

Publication number: CN107911301B
Application number: CN201711460547.XA
Authority: CN
Inventors: 彭剑远; 郑国良
Original assignee: Hangzhou H3C Technologies Co Ltd
Current assignee: Hangzhou H3C Technologies Co Ltd
Priority date: 2017-12-28
Filing date: 2017-12-28
Publication date: 2020-11-20
Anticipated expiration: 2037-12-28
Also published as: CN107911301A

Abstract

The embodiment of the application provides a message forwarding method and a message forwarding device, which are applied to a CB (circuit board), and the method comprises the following steps: receiving a plurality of multicast group joining request messages through a cascade interface connected with the PE; determining that the multicast quantity corresponding to the PE exceeds the multicast capacity of the PE; allocating the unicast ECID carried in each multicast group joining request message to a multicast address; when receiving a multicast data message with a multicast address, copying a multicast data message for each unicast ECID corresponding to the multicast address and packaging each unicast ECID; and sending each multicast data message after encapsulating the unicast ECID to the PE through the cascade port so that the PE determines an expansion port corresponding to the unicast ECID carried by each multicast data message and forwards each multicast data message through the determined expansion port. By applying the embodiment of the application, the terminal is ensured to receive the multicast data message under the condition that the multicast quantity exceeds the multicast specification of the PE, and the user experience is improved.

Description

Message forwarding method and device

Technical Field

The present application relates to the field of communications technologies, and in particular, to a method and an apparatus for forwarding a packet.

Background

An IRF (Intelligent Resilient Framework) system includes a CB (control Bridge) and multiple PEs (Port extensions). The CB is used to manage and control the PEs.

When the multicast data message is forwarded based on the IRF system, the terminal sends a multicast group joining request message carrying a multicast address to the CB through the PE. And the CB distributes multicast ECID for the multicast address carried in each multicast group joining request message. And when the CB receives the multicast data message, the CB determines the multicast ECID according to the multicast address of the multicast data message, encapsulates the multicast ECID in the multicast data message and sends the multicast ECID to the PE. And the PE determines a plurality of expansion ports according to the multicast ECID, copies a multicast data message on the plurality of expansion ports respectively, and further forwards the multicast data message.

At present, the PE is influenced by the performance of the PE, and the multicast capability is limited. The multicast capability includes the number of multicast groups and the number of member devices in each multicast group. Wherein, a multicast address corresponds to a multicast group, and the terminal joining a multicast group is the member device of the multicast group.

If the multicast number of the PE exceeds the multicast capability, for example, the multicast group number exceeds the multicast group number specified in the multicast capability, and/or the number of the member devices in a certain multicast group exceeds the member device number specified in the multicast capability, the PE cannot copy enough multicast data packets to each terminal, and further a part of terminals cannot receive the multicast data packets, and the user experience is poor.

Disclosure of Invention

An object of the embodiments of the present application is to provide a message forwarding method and apparatus, so as to ensure that a user equipment receives a multicast data message when a multicast number exceeds a multicast capability of a PE, and improve user experience. The specific technical scheme is as follows:

in order to achieve the above object, an embodiment of the present application provides a packet forwarding method, which is applied to a CB, and the method includes:

receiving a plurality of multicast group joining request messages through a cascade interface connected with the PE; each multicast group join request message carries a multicast address and a unicast ECID (extended Channel Identifier) corresponding to an extended port through which the PE receives the multicast group join request message;

determining that the multicast quantity corresponding to the PE exceeds the multicast capacity of the PE;

allocating the unicast ECID carried in each multicast group joining request message as the unicast ECID corresponding to the multicast address;

when receiving a multicast data message with a multicast address, copying a multicast data message for each unicast ECID corresponding to the multicast address and packaging each unicast ECID;

and sending each multicast data message after encapsulating the unicast ECID to the PE through the cascade port so that the PE determines an expansion port corresponding to the unicast ECID carried by each multicast data message and forwards each multicast data message through the determined expansion port.

In order to achieve the above object, a further embodiment of the present application provides a packet forwarding apparatus, which is applied to a CB, and the apparatus includes:

a receiving unit, configured to receive multiple multicast group join request messages through a cascade interface connected to the PE; each multicast group joining request message carries a multicast address and a unicast ECID corresponding to an expansion port through which the PE receives the multicast group joining request message;

a determining unit, configured to determine that the multicast number corresponding to the PE exceeds the multicast capability of the PE;

the distribution unit is used for distributing the unicast ECID carried in each multicast group joining request message as the unicast ECID corresponding to the multicast address;

the encapsulating unit is used for copying a multicast data message for each unicast ECID corresponding to the multicast address and encapsulating each unicast ECID when receiving the multicast data message with the multicast address;

and the sending unit is used for sending each multicast data message after encapsulating the unicast ECID to the PE through the cascade port so that the PE determines an expansion port corresponding to the unicast ECID carried by each multicast data message and forwards each multicast data message through the determined expansion port.

To achieve the above object, an embodiment of the present application further provides a CB, including a processor and a machine-readable storage medium, where the machine-readable storage medium stores machine-executable instructions capable of being executed by the processor, and the processor is caused by the machine-executable instructions to implement the above message forwarding method.

In the embodiment of the application, when the multicast number corresponding to the PE exceeds the multicast capability of the PE, the CB allocates the unicast ECID to the multicast address. When the CB acquires the multicast data message with the multicast address, the CB copies a multicast data message for each unicast ECID corresponding to the multicast address and encapsulates each unicast ECID, and then the multicast data message is unicast to each terminal through the PE. The CB has better performance and can copy enough multicast data messages. The PE does not need to copy the multicast data message, namely the PE is not limited by the multicast capability of the PE, and only needs to unicast the multicast data message copied by the CB to each terminal, so that the terminal is ensured to receive the multicast data message under the condition that the multicast quantity exceeds the multicast capability of the PE, and the user experience is improved. Of course, it is not necessary for any product or method of the present application to achieve all of the above advantages at the same time.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.

Fig. 1 is a schematic flow chart of a message forwarding method according to an embodiment of the present application;

fig. 2 is a schematic diagram of a networking provided in an embodiment of the present application;

fig. 3 is a schematic structural diagram of a message forwarding apparatus according to an embodiment of the present application;

fig. 4 is a schematic structural diagram of a CB provided in an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

At present, the PE is influenced by the performance of the PE, and the multicast capability is limited. If the multicast number of the PE exceeds the multicast capability, the PE cannot copy enough multicast data packets to each terminal, and thus a part of terminals cannot receive the multicast data packets, and the user experience is poor.

In order to ensure that a terminal receives a multicast data message when the multicast number exceeds the multicast capability of a PE, and improve user experience, the embodiment of the present application provides a message forwarding method and apparatus. Referring to fig. 1, fig. 1 is a schematic flowchart of a message forwarding method provided in an embodiment of the present application. The method is applied to CB and comprises the following steps:

step 101: receiving a plurality of multicast group joining request messages through a cascade interface connected with the PE; each multicast group joining request message carries a multicast address and a unicast ECID corresponding to an expansion port through which the PE receives the multicast group joining request message.

Step 102: and determining that the multicast quantity corresponding to the PE exceeds the multicast capacity of the PE.

Step 103: and allocating the unicast ECID carried in each multicast group joining request message to the multicast address as the unicast ECID corresponding to the multicast address.

Step 104: when receiving the multicast data message with the multicast address, copying a multicast data message for each unicast ECID corresponding to the multicast address and packaging each unicast ECID.

Step 105: and sending each multicast data message after encapsulating the unicast ECID to the PE through the cascade port so that the PE determines an expansion port corresponding to the unicast ECID carried by each multicast data message and forwards each multicast data message through the determined expansion port.

In the embodiment of the application, when the multicast number corresponding to the PE exceeds the multicast capability of the PE, the CB allocates the unicast ECID to the multicast address. When the CB acquires the multicast data message with the multicast address, the CB copies a multicast data message for each unicast ECID corresponding to the multicast address and encapsulates each unicast ECID, and then the multicast data message is unicast to each terminal through the PE. The CB has better performance and can copy enough multicast data messages. The PE does not need to copy the multicast data message, namely the PE is not limited by the multicast capability of the PE, and only needs to unicast the multicast data message copied by the CB to each terminal, so that the terminal is ensured to receive the multicast data message under the condition that the multicast quantity exceeds the multicast capability of the PE, and the user experience is improved.

The following describes a packet forwarding method provided in this embodiment with reference to the networking shown in fig. 2.

The networking shown in fig. 2 comprises a CB10, PEs 20-21, terminals 30-31 associated with a CB10 through a PE20, and terminals 32-36 associated with a CB10 through a PE 21.

The

ports

40 and 41 are cascade ports of CB10, the port 42 is an upstream port of PE20, the port 43 is an upstream port of PE21, the

ports

44 and 45 are expansion ports of PE20, and the

ports

46, 47, 48, 49 and 50 are expansion ports of PE 21.

During the link discovery phase, PE20 sends an Extended Port Create request (Extended Port Create request) message 1 to CB10 through Port 42. The expansion port establishment request message 1 carries the identifier of the port 44 and the identifier of the port 45. PE21 sends expansion port setup request message 2 to CB10 through port 43. The expansion port establishment request message 2 carries the identifier of the port 46, the identifier of the port 47, the identifier of the port 48, the identifier of the port 49, and the identifier of the port 50.

Here, the expansion port establishment request message 1 and the expansion port establishment request message 2 are LLDP (Link Layer Discovery Protocol) messages.

In an embodiment of the present application, in order to facilitate the CB to obtain the multicast capability information of each PE, an expansion port establishment request message sent by the PE to the CB may carry its own multicast capability information. Here, the multicast capability information includes the maximum number of multicast groups supported by the PE, i.e., a multicast group number threshold. The multicast capability information further includes a maximum number of member devices supported by each multicast group PE, i.e., a member device number threshold.

Specifically, the extension port establishment request message 1 sent by the PE20 to the CB10 may carry its own multicast capability information 1. Here, multicast capability information 1 includes a multicast group number threshold supported by PE20 and a member device number threshold supported by PE 20. The extension port establishment request message 2 sent by the PE21 to the CB10 may carry its own multicast capability information 2. Here, multicast capability information 2 includes a multicast group number threshold supported by PE21 and a member device number threshold supported by PE 21.

The CB10 receives the expansion port establishment request message 1 through the port 40, establishes E-channels (extension channels) for the port 44 and the port 45 respectively according to the identifier of the port 44 and the identifier of the port 45 carried in the expansion port establishment request message 1, and allocates unicast ECIDs for the port 44 and the port 45 respectively. For example, the CB10 assigns a unicast ECID for port 44 as ECID1 and a unicast ECID for port 45 as ECID 2.

The CB10 receives the expansion port establishment request message 2 through the port 41, establishes E-channels for the port 46, the port 47, the port 48, the port 49, and the port 50 respectively according to the identifier of the port 46, the identifier of the port 47, the identifier of the port 48, the identifier of the port 49, and the identifier of the port 50, which are carried in the expansion port establishment request message 2, and allocates unicast ECIDs for the port 46, the port 47, the port 48, the port 49, and the port 50 respectively. For example, the unicast ECID assigned by the CB10 for port 46 is ECID3, the unicast ECID assigned for port 47 is ECID4, the unicast ECID assigned for port 48 is ECID5, the unicast ECID assigned for port 49 is ECID6, and the unicast ECID assigned for port 50 is ECID 7.

At this time, CB10 records the correspondence between the unicast ECID and the extension, as shown in table 1.

TABLE 1

Unicast ECID	Expansion port
		ECID1
	44
		ECID2	45
ECID3	46
		ECID4	47
ECID5	48
		ECID6	49
ECID7	50

If multicast capability information is carried in the expansion port establishment request message 1 and the expansion port establishment message 2, the CB10 stores the correspondence between the cascade port receiving the expansion port establishment request message and the multicast capability information, as shown in table 2.

TABLE 2

Cascade port	Multicast capability information
		40	Multicast capability information 1
41	Multicast capability information 2

The information recorded in table 2 may also be the multicast capability information of the PE configured in advance in the CB for the user. The examples of the present application are not intended to be limiting.

The CB10 feeds back an Extended Port setup response (Extended Port setup response) message 1 for the Extended Port setup request message 1 to the PE20 through the Port 40, where the Extended Port setup response message 1 carries the ECID1 allocated to the Port 44 and the ECID2 allocated to the Port 45. The CB10 feeds back an expansion port establishment response message 2 for the expansion port establishment request message 2 to the PE21 through the port 41, where the expansion port establishment response message 2 carries: ECID3 assigned to port 46, ECID4 assigned to port 47, ECID5 assigned to port 48, ECID6 assigned to port 49, and ECID7 assigned to port 50.

Here, the expansion port establishment response message 1 and the expansion port establishment response message 2 are LLDP messages.

PE20 receives the expansion port establishment response message 1 through port 42, records the correspondence between the unicast ECID and the expansion port according to the information carried in the expansion port establishment response message 1, as shown in table 3.

TABLE 3

Unicast ECID	Expansion port
		ECID1
	44
		ECID2	45

PE21 receives the expansion port establishment response packet 2 through port 43, and records the correspondence between the unicast ECID and the expansion port according to the information carried in the expansion port establishment response packet 2, as shown in table 4.

TABLE 4

Unicast ECID	Expansion port
		ECID3
	46
		ECID4	47
ECID5	48
		ECID6	49
ECID7	50

When the terminals 30 and 31 need to join the multicast group corresponding to the multicast address IP1, the terminal 30 sends a multicast group join request message 1 to the PE20, and the terminal 31 sends a multicast group join request message 2 to the PE 20. The multicast group join request message 1 and the multicast group join request message 2 both carry multicast addresses IP1 corresponding to multicast groups to which joining is requested.

The PE20 receives the multicast group join request message 1 through the port 44, determines the ECID1 corresponding to the port 44 according to the correspondence recorded in table 3, encapsulates the ECID1 in the multicast group join request message 1, and sends the request message to the CB10 through the port 42. The PE20 receives the multicast group join request message 2 through the port 45, determines the ECID2 corresponding to the port 45 according to the correspondence recorded in table 3, encapsulates the ECID2 in the multicast group join request message 2, and sends the request message to the CB10 through the port 42.

The CB10 receives the multicast group join request message 1 and the multicast group join request message 2 through the port 40, and determines that the multicast group corresponding to the multicast address IP1 includes 2 member devices, where the multicast group join request message 1 and the multicast group join request message 2 carry the multicast address IP 1.

The CB10 determines, according to table 2, that the port 40 receiving the multicast group join request packet 1 and the multicast group join request packet 2 corresponds to the multicast capability information 1. The CB10 detects whether the current multicast number of PE20 exceeds the multicast capability information 1. Specifically, the CB10 detects whether the number of PE20 multicast groups exceeds the multicast group number threshold in the multicast capability information 1, and detects whether the number of member devices in the multicast group corresponding to the multicast address IP1 exceeds the member device number threshold in the multicast capability information 1. Here, the number of PE multicast groups is: 1 and the sum of the number of correspondence relationships between the multicast address and the multicast ECID for the PE stored in the CB.

If the CB10 determines that the number of PE20 multicast groups does not exceed the multicast group number threshold in the multicast capability information 1, and the number of member devices in the multicast group corresponding to the multicast address IP1 does not exceed the member device number threshold in the multicast capability information 1, the CB10 allocates a multicast ECID to the multicast address IP1, for example, the multicast ECID allocated to the multicast address IP1 is ECID 8.

CB10 records the correspondence of both multicast address and multicast ECID for PE20 as shown in table 5.

TABLE 5

Multicast address	Multicast ECID
		IP1	ECID8

The CB10 records the correspondence between the multicast address for PE20 and the cascade port receiving the multicast group join request message, as shown in table 6.

TABLE 6

Multicast address	Cascade port
		IP1	Port
40

The CB10 determines the port 44 corresponding to the ECID1 carried in the multicast group join request message 1 according to table 1, and uses the port 44 as an extension port corresponding to the multicast ECID 8. The CB10 carries the multicast ECID8 and the port 44 in the multicast group join response message 1 for the multicast group join request message 1, and sends the multicast ECID and the port 40 to the PE 20.

In addition, the CB10 determines, according to table 1, that the port 45 corresponds to the ECID2 carried in the multicast group join request packet 2, and uses the port 45 as an extension port corresponding to the multicast ECID 8. The CB10 carries the multicast ECID8 and the port 45 in the multicast group join response message 2 for the multicast group join request message 2, and sends the multicast ECID and the port 45 to the PE20 through the port 40.

PE20 receives multicast group join response message 1 and multicast group join response message 2 through port 42, and records the correspondence between multicast ECID and extension port, as shown in table 7.

TABLE 7

Multicast ECID	Expansion port
		ECID8	Port
44
	ECID8	Port	45

At this time, if the CB10 receives the multicast data packet 1 with the multicast address IP1, the ECID8 corresponding to the IP1 is determined according to table 5, and the port 40 corresponding to the IP1 is determined according to table 6. The CB10 encapsulates the ECID8 in the multicast data packet 1 and sends it to the PE20 through the port 40.

After receiving the multicast data packet 1 through the port 42, the PE20 determines, according to table 7, that the ECID8 carried in the multicast data packet 1 corresponds to 2 expansion ports, including the port 44 and the port 45. PE20 replicates a multicast data message 1 at port 44 and port 45, respectively. PE20 then sends multicast datagram 1 to terminal 30 via port 44 and multicast datagram 1 to terminal 31 via port 45.

In the embodiment of the present application, if the CB10 determines that the number of PE20 multicast groups exceeds the multicast group number threshold in the multicast capability information 1, for example, the multicast group number threshold in the multicast capability information 1 is 10, if the CB10 stores 10 correspondence relationships between multicast addresses for the PE20 and multicast ECIDs, that is, if the PE20 already has 10 multicast groups, and in addition to the multicast group corresponding to the multicast address IP1, the PE20 has 11 multicast groups, 11>10, and exceeds the multicast group number threshold in the multicast capability information 1, regardless of whether the number of member devices in the multicast group corresponding to the multicast address IP1 exceeds the member device number threshold in the multicast capability information 1, the CB10 allocates the ECID1 carried in the multicast group join request message 1 to the multicast address IP1, allocates the ECID2 carried in the multicast group join request message 2 to the multicast address IP1, and the CB10 records the correspondence relationship between the multicast address for the PE20 and the ECID, as shown in table 8.

TABLE 8

Multicast address	Unicast ECID
		IP1	ECID1
IP1	ECID2

The CB10 records the correspondence between the multicast address for PE20 and the tandem port receiving the multicast group join request message, as shown in table 6 above.

At this time, if the CB10 receives the multicast data packet 2 with the multicast address IP1, 2 unicast ECIDs corresponding to the IP1 are determined according to table 8, including ECID1 and ECID 2. CB10 determines port 40 to which IP1 corresponds according to table 6. The CB10 copies a multicast data packet 2 for the ECID1 and encapsulates the ECID1, copies a multicast data packet 2 for the ECID2 and encapsulates the ECID2, and sends the 2 multicast data packets 2 encapsulated with the ECID to the PE20 through the port 40.

After receiving the multicast data packet 2 through the port 42, the PE20 determines, according to table 3, that the port 44 corresponds to the ECID1 carried in the multicast data packet 2, and that the port 45 corresponds to the ECID2 carried in the multicast data packet 2. For multicast data packet 2 encapsulating the ECID1, PE20 sends the multicast data packet 2 to the terminal 30 through port 44. For the multicast data packet 2 encapsulating the ECID2, the PE20 sends the multicast data packet 2 to the terminal 31 through the port 45.

In an embodiment of the present application, the threshold of the number of member devices in the multicast capability information 2 is 4.

When the

terminals

32, 33, 34, and 35 need to join the multicast group corresponding to the multicast address IP2, the 4

terminals

32, 33, 34, and 35 send multicast group join request packets carrying the multicast address IP2 requesting to join to the PE21, and it can be determined that the number of the member devices of the multicast group corresponding to the multicast address IP2 of the PE21 is 4 and does not exceed the threshold of the number of the member devices in the multicast capability information 2. If the CB10 further determines that the number of PE21 multicast groups does not exceed the multicast group number threshold in the multicast capability information 2, based on table 4, table 2, and table 1, through the interaction between PE21 and CB10, CB10 assigns a multicast ECID to the multicast address IP2, for example, the multicast ECID assigned to the multicast address IP2 is ECID9, determines an extension port corresponding to ECID9, and sends ECID9 and the extension port corresponding to ECID9 to PE 21.

At this time, CB10 records the correspondence between the multicast address and the multicast ECID for PE21, as shown in table 9 below.

TABLE 9

Multicast address	Multicast ECID
		IP2	ECID9

The CB10 records the correspondence between the multicast address for PE21 and the cascade port receiving the multicast group join request message, as shown in table 10.

Watch 10

Multicast address	Cascade port
		IP2	Port
41

PE21 records the correspondence between multicast ECID and extension, as shown in table 11.

TABLE 11

Multicast ECID	ExtensionMouth piece
		ECID9	Port
46
	ECID9	Port 47
ECID9			Port	48
	ECID9	Port			49

The process of the

terminals

32, 33, 34, and 35 joining the multicast group corresponding to the multicast address IP2 may refer to the above process of the terminals 30 and 31 joining the multicast group corresponding to the multicast address IP1, and is not described herein again.

When the terminal 36 needs to join the multicast group corresponding to the multicast address IP2, the terminal 36 sends a multicast group join request message 3 carrying the multicast address IP2 requesting to join to the PE21, so that it can be determined that the number of member devices of the multicast group corresponding to the multicast address IP2 is 5, 5>4, and exceeds the threshold of the number of member devices in the multicast capability information 2. The multicast group join request message 3 carries the ECID7 corresponding to the port 50.

In an embodiment of the present application, to save CB resources, when the CB10 determines that the number of member devices in the multicast group corresponding to the multicast address IP2 exceeds the threshold of the number of member devices in the multicast capability information 2, if the number of the PE21 multicast group does not exceed the threshold of the number of multicast groups in the multicast capability information 2, the CB10 allocates the ECID7 carried in the multicast group join request packet 3 to the multicast address IP2, and the CB10 records the correspondence between the multicast address and the unicast ECID for the PE21, as shown in table 12.

TABLE 12

Multicast address	Unicast ECID
		IP2	ECID7

At this time, if the CB10 receives the multicast data packet 3 with the multicast address IP2, the multicast ECID9 corresponding to IP2 is determined according to table 9, and the unicast ECID7 corresponding to IP2 is determined according to table 12. CB10 determines IP2 corresponding port 41 from table 10. The CB10 copies a multicast data packet 3 for the ECID9 and encapsulates the ECID9, copies a multicast data packet 3 for the ECID7 and encapsulates the ECID7, and sends the 2 multicast data packets 3 encapsulated with the ECID to the PE21 through the port 41.

After receiving the multicast data packet 3 through the port 43, the PE21 determines the port 50 corresponding to the ECID7 carried in the multicast data packet 3 according to table 4, and determines the

ports

46, 47, 48, and 49 corresponding to the ECID9 carried in the multicast data packet 3 according to table 11. For the multicast data packet 3 carrying the ECID7, the PE21 sends the multicast data packet 3 to the terminal 36 through the port 50. For multicast data packet 3 carrying the ECID9, PE21 copies one multicast data packet 3 at

ports

46, 47, 48, 49, respectively. PE21 then sends multicast datagram 3 to terminal 32 via port 46, multicast datagram 3 to terminal 33 via port 47, multicast datagram 3 to terminal 34 via port 48, and multicast datagram 3 to terminal 35 via port 49.

In an embodiment of the present application, in order to improve the synchronization of the information acquired by the terminal, when the CB10 determines that the number of member devices in the multicast group corresponding to the multicast address IP2 exceeds the threshold of the number of member devices in the multicast capability information 2, regardless of whether the number of PE21 multicast groups exceeds the threshold of the number of multicast groups in the multicast capability information 2, the CB10 allocates the ECID7 carried in the multicast group join request packet 3 to the multicast address IP 2. The CB10 identifies the ECID9 corresponding to the multicast address IP2 from table 9, and identifies the port 41 corresponding to the multicast address IP2 from table 10. The CB10 sends an information acquisition request message 1 carrying the ECID9 to the PE21 through the port 41.

PE21 receives information acquisition request message 1 through port 43, and determines, according to table 11, the expansion port corresponding to ECID9 carried in information acquisition request message 1, including

ports

46, 47, 48, and 49. PE21 determines from Table 4 that port 46 corresponds to ECID3, port 47 corresponds to ECID4, port 48 corresponds to ECID5, and port 49 corresponds to ECID 6. The PE21 carries the ECID3 corresponding to the port 46, the ECID4 corresponding to the port 47, the ECID5 corresponding to the port 48, and the ECID6 corresponding to the port 49 in the information acquisition response message 1 to the information acquisition request message 1, and sends the information acquisition response message 1 to the CB10 through the port 43.

CB10 receives information acquisition response message 1 through port 41. The CB10 assigns the ECID3, ECID4, ECID5, and ECID6 carried in the information acquisition response packet 1 to the multicast address IP 2. CB10 deletes table 9 and records the correspondence between the multicast address and unicast ECID for PE21, as shown in table 13.

Watch 13

Multicast address	Unicast ECID
		IP2	ECID7
IP2	ECID3
		IP2	ECID4
IP2	ECID5
		IP2	ECID6

At this time, if the CB10 receives the multicast data packet 4 with the multicast address IP2, 5 unicast ECIDs corresponding to the IP2 are determined according to the table 13, including ECID7, ECID3, ECID4, ECID5, and ECID 6. CB10 determines IP2 corresponding port 41 from table 10. The CB10 copies 1 multicast data packet 4 for 5 unicast ECIDs respectively and encapsulates each unicast ECID, where an ECID7 is encapsulated in one multicast data packet 4, an ECID3 is encapsulated in one multicast data packet 4, an ECID4 is encapsulated in one multicast data packet 4, an ECID5 is encapsulated in one multicast data packet 3, and an ECID6 is encapsulated in one multicast data packet 4, and sends the 5 multicast data packets 4 encapsulated with ECIDs to the PE21 through the ports 41 respectively.

After the PE21 receives 5 multicast datagrams 4 through the port 43, it determines, according to table 4, that the port 50 corresponding to the ECID7, the port 46 corresponding to the ECID3, the port 47 corresponding to the ECID4, the port 48 corresponding to the ECID5, and the port 49 corresponding to the ECID6 are carried in the multicast datagrams 4. For the multicast data packet 4 carrying the ECID7, the PE21 sends the multicast data packet 4 to the terminal 36 through the port 50. For the multicast data packet 4 carrying the ECID3, the PE21 sends the multicast data packet 4 to the terminal 32 through the port 46. For the multicast data packet 4 carrying the ECID4, the PE21 sends the multicast data packet 4 to the terminal 33 through the port 47. For the multicast data packet 4 carrying the ECID5, the PE21 sends the multicast data packet 4 to the terminal 34 through the port 48. For the multicast data packet 4 carrying the ECID6, the PE21 sends the multicast data packet 4 to the terminal 35 through the port 49.

Corresponding to the embodiment of the message forwarding method, the embodiment of the application also provides a message forwarding device. Referring to fig. 3, fig. 3 is a schematic structural diagram of a packet forwarding device provided in this embodiment, and is applied to a CB, where the device includes:

a receiving unit 301, configured to receive multiple multicast group join request messages through a cascade interface connected to the PE; each multicast group joining request message carries a multicast address and a unicast ECID corresponding to an expansion port through which the PE receives the multicast group joining request message;

a determining unit 302, configured to determine that the multicast number corresponding to a PE exceeds the multicast capability of the PE;

the allocating unit 303 is configured to allocate the unicast ECID carried in each multicast group join request message as a unicast ECID corresponding to the multicast address;

an encapsulating unit 304, configured to copy a multicast data packet for each unicast ECID corresponding to the multicast address and encapsulate each unicast ECID when receiving a multicast data packet with the multicast address;

a sending unit 305, configured to send each multicast data packet encapsulated with the unicast ECID to the PE through the cascade interface, so that the PE determines an extension interface corresponding to the unicast ECID carried in each multicast data packet, and forwards each multicast data packet through the determined extension interface.

In one embodiment of the present application, the multicast capability may include a member device number threshold;

in this case, the determining unit 302 may be specifically configured to determine that the number of member devices of the multicast address corresponding to the PE exceeds the threshold of the number of member devices corresponding to the PE, and then determine that the multicast number corresponding to the PE exceeds the multicast capability of the PE.

In one embodiment of the present application, the multicast capability may include a multicast group number threshold;

in this case, the determining unit 302 may be specifically configured to determine that the number of multicast groups corresponding to the PE exceeds the threshold of the number of multicast groups corresponding to the PE, and then determine that the number of multicast groups corresponding to the PE exceeds the multicast capability of the PE.

In an embodiment of the present application, the multicast capability may further include a member device number threshold;

in this case, the determining unit 302 may be further configured to determine that the number of multicast groups corresponding to the PE does not exceed the threshold of the number of multicast groups corresponding to the PE, and determine that the number of member devices of the multicast address corresponding to the PE exceeds the threshold of the number of member devices corresponding to the PE;

the allocating unit 303 may be further configured to allocate a corresponding multicast ECID to a multicast address carried in the first group multicast group join request message, and allocate a unicast ECID carried in the second group multicast group join request message to the multicast address as a unicast ECID corresponding to the multicast address; the number of multicast group joining request messages included in the first group of multicast group joining request messages is a member device number threshold value corresponding to the PE, and the second group of multicast group joining request messages include multicast group joining request messages except the first group of multicast group joining request messages;

the encapsulating unit 304 may be further configured to copy, when receiving a multicast data packet with a multicast address, a multicast data packet for a multicast ECID corresponding to the multicast address and encapsulate the multicast ECID, copy, for each unicast ECID corresponding to the multicast address, a multicast data packet and encapsulate each unicast ECID;

the sending unit 305 may also be configured to send the multicast data packet after encapsulating the multicast ECID and each multicast data packet after encapsulating the unicast ECID to the PE through the cascade interface, so that the PE determines the unicast ECID carried in each multicast data packet or an extension port corresponding to the multicast ECID, and forwards each multicast data packet through the determined extension port.

In an embodiment of the present application, the determining unit 302 may be further configured to determine that the number of multicast groups corresponding to a PE does not exceed the threshold of the number of multicast groups corresponding to the PE, and determine that the number of member devices of a multicast address corresponding to the PE does not exceed the threshold of the number of member devices corresponding to the PE;

the allocating unit 303 may also be configured to allocate a corresponding multicast ECID to a multicast address carried in the multiple multicast group join request messages;

the encapsulating unit 304 may be further configured to encapsulate, when receiving a multicast data packet with a multicast address, a multicast ECID corresponding to the multicast address in the multicast data packet;

the sending unit 305 may further be configured to send the multicast data packet after encapsulating the multicast ECID to the PE through the cascade interface, so that the PE determines an extension port corresponding to the multicast ECID carried in the multicast data packet, and forwards the multicast data packet through the determined extension port.

By applying the embodiment of the application, when the multicast quantity corresponding to the PE exceeds the multicast capacity of the PE, the CB allocates the unicast ECID for the multicast address. When the CB acquires the multicast data message with the multicast address, the CB copies a multicast data message for each unicast ECID corresponding to the multicast address and encapsulates each unicast ECID, and then the multicast data message is unicast to each terminal through the PE. The CB has better performance and can copy enough multicast data messages. The PE does not need to copy the multicast data message, namely the PE is not limited by the multicast capability of the PE, and only needs to unicast the multicast data message copied by the CB to each terminal, so that the terminal is ensured to receive the multicast data message under the condition that the multicast quantity exceeds the multicast capability of the PE, and the user experience is improved.

Corresponding to the embodiment of the message forwarding method, an embodiment of the present application further provides a CB, including a processor and a machine-readable storage medium, where the machine-readable storage medium stores machine-executable instructions capable of being executed by the processor, and the processor is caused by the machine-executable instructions to implement the message forwarding method.

As shown in fig. 4, the CB includes a processor 401 and a machine-readable storage medium 402, the machine-readable storage medium 402 storing machine-executable instructions executable by the processor 401.

In addition, as shown in fig. 4, the CB may further include: a communication interface 403 and a communication bus 404; the processor 401, the machine-readable storage medium 402, and the communication interface 403 complete communication with each other through the communication bus 404, and the communication interface 403 is used for communication between the CB and other devices.

Wherein the machine-executable instructions comprise: receive instructions 412, determine instructions 422, allocate instructions 432, encapsulate instructions 442, and send instructions 452.

The processor 401, being received with the instructions 412, causes implementation of: receiving a plurality of multicast group joining request messages through a cascade interface connected with the PE; each multicast group joining request message carries a multicast address and a unicast ECID corresponding to an expansion port through which the PE receives the multicast group joining request message;

processor 401 is determined that instructions 422 cause implementation of: determining that the multicast quantity corresponding to the PE exceeds the multicast capacity of the PE;

processor 401 is assigned instructions 432 to cause implementation of: allocating the unicast ECID carried in each multicast group joining request message as the unicast ECID corresponding to the multicast address;

the processor 401 is encapsulated with instructions 442 to implement: when receiving a multicast data message with a multicast address, copying a multicast data message for each unicast ECID corresponding to the multicast address and packaging each unicast ECID;

the processor 401 is sent instructions 452 to cause implementation of: and sending each multicast data message after encapsulating the unicast ECID to the PE through the cascade port so that the PE determines an expansion port corresponding to the unicast ECID carried by each multicast data message and forwards each multicast data message through the determined expansion port.

processor 401 is caused by determining instructions 422 to specifically implement: and determining that the number of member devices of the multicast address corresponding to the PE exceeds the threshold value of the number of the member devices corresponding to the PE, and determining that the multicast number corresponding to the PE exceeds the multicast capacity of the PE.

processor 401 is caused by determining instructions 422 to specifically implement: and determining that the number of the multicast groups corresponding to the PE exceeds the threshold value of the number of the multicast groups corresponding to the PE, and determining that the number of the multicast groups corresponding to the PE exceeds the multicast capability of the PE.

processor 401 is caused by determining instructions 422 to further enable: determining that the number of multicast groups corresponding to the PE does not exceed a multicast group number threshold corresponding to the PE, and determining that the number of member devices of a multicast address corresponding to the PE exceeds a member device number threshold corresponding to the PE;

processor 401 is assigned instructions 432 to cause further implementation of: distributing corresponding multicast ECID for the multicast address carried in the first group of multicast group join request message, and distributing the unicast ECID carried in the second group of multicast group join request message as the unicast ECID corresponding to the multicast address; the number of multicast group joining request messages included in the first group of multicast group joining request messages is a member device number threshold value corresponding to the PE, and the second group of multicast group joining request messages include multicast group joining request messages except the first group of multicast group joining request messages;

the processor 401 is caused by the encapsulated instructions 442 to further implement: when receiving a multicast data message with a multicast address, copying a multicast data message for a multicast ECID corresponding to the multicast address and packaging the multicast ECID, and copying a multicast data message for each unicast ECID corresponding to the multicast address and packaging each unicast ECID;

the processor 401 is caused by the send instructions 452 to further implement: and sending the multicast data message after the multicast ECID is packaged and the multicast data message after each unicast ECID is packaged to the PE through the cascade port, so that the PE determines the unicast ECID carried by each multicast data message or an expansion port corresponding to the multicast ECID, and forwards each multicast data message through the determined expansion port.

In one embodiment of the application, the processor 401 is caused by the determining instructions 422 to further implement: determining that the number of multicast groups corresponding to the PE does not exceed a multicast group number threshold corresponding to the PE, and determining that the number of member devices of a multicast address corresponding to the PE does not exceed a member device number threshold corresponding to the PE;

processor 401 is assigned instructions 432 to cause further implementation of: distributing corresponding multicast ECID for multicast address carried in multiple multicast group joining request message

The processor 401 is caused by the encapsulated instructions 442 to further implement: when receiving a multicast data message with a multicast address, encapsulating a multicast ECID corresponding to the multicast address in the multicast data message;

the processor 401 is caused by the send instructions 452 to further implement: and sending the multicast data message after the multicast ECID is packaged to the PE through the cascade port so that the PE determines an expansion port corresponding to the multicast ECID carried by the multicast data message and forwards the multicast data message through the determined expansion port.

The communication bus 404 may be a PCI (Peripheral Component Interconnect) bus, an EISA (Extended Industry Standard Architecture) bus, or the like. The communication bus 404 may be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, only one thick line is shown in FIG. 4, but this does not indicate only one bus or one type of bus.

The machine-readable storage medium 402 may include a RAM (Random Access Memory) and may also include a NVM (Non-Volatile Memory), such as at least one disk Memory. Additionally, the machine-readable storage medium 402 may also be at least one storage device located remotely from the aforementioned processor.

Processor 401 may be a general-purpose Processor including a CPU (Central Processing Unit), an NP (Network Processor), etc.; but also DSPs (Digital Signal Processing), ASICs (Application Specific Integrated circuits), FPGAs (Field Programmable Gate arrays) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components.

Corresponding to the embodiment of the message forwarding method, an embodiment of the present application further provides a machine-readable storage medium, which stores machine-executable instructions, and when the machine-readable storage medium is called and executed by a processor, the machine-executable instructions cause the processor to implement the message forwarding method.

Wherein the machine-executable instructions comprise: receiving instructions, determining instructions, distributing instructions, encapsulating instructions, and sending instructions.

When invoked and executed by a processor, receiving instructions cause the processor to: receiving a plurality of multicast group joining request messages through a cascade interface connected with the PE; each multicast group joining request message carries a multicast address and a unicast ECID corresponding to an expansion port through which the PE receives the multicast group joining request message;

when invoked and executed by a processor, the determining instructions cause the processor to: determining that the multicast quantity corresponding to the PE exceeds the multicast capacity of the PE;

when invoked and executed by a processor, the allocation instructions cause the processor to: allocating the unicast ECID carried in each multicast group joining request message as the unicast ECID corresponding to the multicast address;

when invoked and executed by a processor, the encapsulated instructions cause the processor to: when receiving a multicast data message with a multicast address, copying a multicast data message for each unicast ECID corresponding to the multicast address and packaging each unicast ECID;

when invoked and executed by a processor, the send instructions cause the processor to: and sending each multicast data message after encapsulating the unicast ECID to the PE through the cascade port so that the PE determines an expansion port corresponding to the unicast ECID carried by each multicast data message and forwards each multicast data message through the determined expansion port.

when invoked and executed by a processor, the determining instructions cause the processor to specifically implement: and determining that the number of member devices of the multicast address corresponding to the PE exceeds the threshold value of the number of the member devices corresponding to the PE, and determining that the multicast number corresponding to the PE exceeds the multicast capacity of the PE.

when invoked and executed by a processor, the determining instructions cause the processor to specifically implement: and determining that the number of the multicast groups corresponding to the PE exceeds the threshold value of the number of the multicast groups corresponding to the PE, and determining that the number of the multicast groups corresponding to the PE exceeds the multicast capability of the PE.

when invoked and executed by a processor, the determining instructions cause the processor to further implement: determining that the number of multicast groups corresponding to the PE does not exceed a multicast group number threshold corresponding to the PE, and determining that the number of member devices of a multicast address corresponding to the PE exceeds a member device number threshold corresponding to the PE;

when invoked and executed by a processor, the allocation instructions cause the processor to further implement: distributing corresponding multicast ECID for the multicast address carried in the first group of multicast group join request message, and distributing the unicast ECID carried in the second group of multicast group join request message as the unicast ECID corresponding to the multicast address; the number of multicast group joining request messages included in the first group of multicast group joining request messages is a member device number threshold value corresponding to the PE, and the second group of multicast group joining request messages include multicast group joining request messages except the first group of multicast group joining request messages;

when invoked and executed by a processor, the wrapper instructions cause the processor to further implement: when receiving a multicast data message with a multicast address, copying a multicast data message for a multicast ECID corresponding to the multicast address and packaging the multicast ECID, and copying a multicast data message for each unicast ECID corresponding to the multicast address and packaging each unicast ECID;

when invoked and executed by a processor, the send instructions cause the processor to further implement: and sending the multicast data message after the multicast ECID is packaged and the multicast data message after each unicast ECID is packaged to the PE through the cascade port, so that the PE determines the unicast ECID carried by each multicast data message or an expansion port corresponding to the multicast ECID, and forwards each multicast data message through the determined expansion port.

In one embodiment of the application, the determining instructions, when invoked and executed by the processor, cause the processor to further implement: determining that the number of multicast groups corresponding to the PE does not exceed a multicast group number threshold corresponding to the PE, and determining that the number of member devices of a multicast address corresponding to the PE does not exceed a member device number threshold corresponding to the PE;

when invoked and executed by a processor, the allocation instructions cause the processor to further implement: distributing corresponding multicast ECID for the multicast address carried in the multiple multicast group joining request messages;

when invoked and executed by a processor, the wrapper instructions cause the processor to further implement: when receiving a multicast data message with a multicast address, encapsulating a multicast ECID corresponding to the multicast address in the multicast data message;

when invoked and executed by a processor, the send instructions cause the processor to further implement: and sending the multicast data message after the multicast ECID is packaged to the PE through the cascade port so that the PE determines an expansion port corresponding to the multicast ECID carried by the multicast data message and forwards the multicast data message through the determined expansion port.

It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.

All the embodiments in the present specification are described in a related manner, and the same and similar parts among the embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments. Especially, for the embodiments of the message forwarding apparatus, the CB, and the machine-readable storage medium, since they are basically similar to the embodiments of the message forwarding method, the description is relatively simple, and for the relevant points, reference may be made to the partial description of the embodiments of the message forwarding method.

The above description is only for the preferred embodiment of the present application, and is not intended to limit the scope of the present application. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application are included in the protection scope of the present application.

Claims

1. A message forwarding method is applied to a Control Bridge (CB), and the method comprises the following steps:

receiving a plurality of multicast group joining request messages through a cascade interface of a connection port expansion device PE; each multicast group joining request message carries a multicast address and a unicast extended channel identifier ECID corresponding to an extended port of the PE receiving the multicast group joining request message;

allocating the unicast ECID carried in each multicast group joining request message to the multicast address as the unicast ECID corresponding to the multicast address;

when receiving the multicast data message with the multicast address, copying one multicast data message for each unicast ECID corresponding to the multicast address and packaging each unicast ECID;

2. The method of claim 1, wherein the multicast capability comprises a member device count threshold;

the step of determining that the multicast number corresponding to the PE exceeds the multicast capability of the PE includes:

and determining that the number of member devices of the multicast address corresponding to the PE exceeds a threshold of the number of member devices corresponding to the PE, and determining that the multicast number corresponding to the PE exceeds the multicast capability of the PE.

3. The method of claim 1, wherein the multicast capability comprises a multicast group number threshold;

and if the multicast group number corresponding to the PE is determined to exceed the multicast group number threshold corresponding to the PE, determining that the multicast number corresponding to the PE exceeds the multicast capability of the PE.

4. The method of claim 3, wherein the multicast capability further comprises a member device count threshold;

the method further comprises the following steps:

determining that the number of multicast groups corresponding to the PE does not exceed a multicast group number threshold corresponding to the PE, and determining that the number of member devices of the multicast address corresponding to the PE exceeds a member device number threshold corresponding to the PE;

distributing corresponding multicast ECID for the multicast address carried in the first group of multicast group join request message, and distributing the unicast ECID carried in the second group of multicast group join request message to the multicast address as the unicast ECID corresponding to the multicast address; the number of multicast group join request messages included in the first group of multicast group join request messages is a member device number threshold corresponding to the PE, and the second group of multicast group join request messages include multicast group join request messages except the first group of multicast group join request messages;

when receiving a multicast data message with the multicast address, copying a part of the multicast data message for a multicast ECID corresponding to the multicast address and packaging the multicast ECID, and copying a part of the multicast data message for each unicast ECID corresponding to the multicast address and packaging each unicast ECID;

and sending the multicast data message after the multicast ECID is packaged and the multicast data message after each unicast ECID is packaged to the PE through the cascade port, so that the PE determines the unicast ECID carried by each multicast data message or an expansion port corresponding to the multicast ECID, and forwards each multicast data message through the determined expansion port.

5. The method of claim 4, further comprising:

determining that the number of multicast groups corresponding to the PE does not exceed a multicast group number threshold corresponding to the PE, and determining that the number of member devices of the multicast address corresponding to the PE does not exceed a member device number threshold corresponding to the PE;

distributing corresponding multicast ECID for the multicast address carried in the multicast group join request messages;

when receiving the multicast data message with the multicast address, encapsulating the multicast ECID corresponding to the multicast address in the multicast data message;

and sending the multicast data message after the multicast ECID is packaged to the PE through the cascade port so that the PE determines an expansion port corresponding to the multicast ECID carried by the multicast data message and forwards the multicast data message through the determined expansion port.

6. A message forwarding device is applied to a Control Bridge (CB), and the device comprises:

a receiving unit, configured to receive multiple multicast group join request messages through a cascade interface of a connection port expansion device PE; each multicast group joining request message carries a multicast address and a unicast extended channel identifier ECID corresponding to an extended port of the PE receiving the multicast group joining request message;

the packaging unit is used for copying a multicast data message for each unicast ECID corresponding to the multicast address and packaging each unicast ECID when receiving the multicast data message with the multicast address;

7. The apparatus of claim 6, wherein the multicast capability comprises a member device count threshold;

the determining unit is specifically configured to:

8. The apparatus of claim 6, wherein the multicast capability comprises a multicast group number threshold;

the determining unit is specifically configured to:

9. The apparatus of claim 8, wherein the multicast capability further comprises a member device count threshold;

the determining unit is further configured to determine that the number of multicast groups corresponding to the PE does not exceed the threshold of the number of multicast groups corresponding to the PE, and determine that the number of member devices of the multicast address corresponding to the PE exceeds the threshold of the number of member devices corresponding to the PE;

the allocating unit is further configured to allocate a corresponding multicast ECID to the multicast address carried in the first group multicast group join request message, and allocate a unicast ECID carried in the second group multicast group join request message to the multicast address as a unicast ECID corresponding to the multicast address; the number of multicast group join request messages included in the first group of multicast group join request messages is a member device number threshold corresponding to the PE, and the second group of multicast group join request messages include multicast group join request messages except the first group of multicast group join request messages;

the encapsulating unit is further configured to copy, when receiving the multicast data packet with the multicast address, a part of the multicast data packet for a multicast ECID corresponding to the multicast address and encapsulate the multicast ECID, and copy, for each unicast ECID corresponding to the multicast address, a part of the multicast data packet and encapsulate each unicast ECID;

the sending unit is further configured to send the multicast data packet after encapsulating the multicast ECID and each multicast data packet after encapsulating the unicast ECID to the PE through the cascade port, so that the PE determines the unicast ECID carried by each multicast data packet or an extension port corresponding to the multicast ECID, and forwards each multicast data packet through the determined extension port.

10. The apparatus according to claim 9, wherein the determining unit is further configured to determine that the number of multicast groups corresponding to the PE does not exceed a multicast group number threshold corresponding to the PE, and determine that the number of member devices of the multicast address corresponding to the PE does not exceed a member device number threshold corresponding to the PE;

the allocating unit is further configured to allocate a corresponding multicast ECID to the multicast address carried in the multicast group join request messages;

the encapsulating unit is further configured to encapsulate, when receiving a multicast data packet with the multicast address, a multicast ECID corresponding to the multicast address in the multicast data packet;

the sending unit is further configured to send the multicast data packet after encapsulating the multicast ECID to the PE through the cascade interface, so that the PE determines an extension port corresponding to the multicast ECID carried in the multicast data packet, and forwards the multicast data packet through the determined extension port.

11. A control bridge, CB, comprising a processor and a machine-readable storage medium storing machine-executable instructions executable by the processor, the processor being caused by the machine-executable instructions to: carrying out the method steps of any one of claims 1 to 5.