WO2008098506A1

WO2008098506A1 - Multicast method, multicast system and multicast device

Info

Publication number: WO2008098506A1
Application number: PCT/CN2008/070267
Authority: WO
Inventors: Danfeng Feng; Junping Zhang; Huimin Zhang; Liangyao Mo; Hao Huang
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2007-02-16
Filing date: 2008-02-03
Publication date: 2008-08-21
Also published as: CN101247549B; CN101247549A

Abstract

A multicast method is provided. The method includes the following steps: according to a join group request of a receiver, a sender performs an authentication for the receiver requesting to join the multicast group; the sender adds the authenticated receiver to a forward item corresponding to the multicast group that the sender requests for the join, and transmits the join group request to a forward device; the forward device adds the sender to the forward item corresponding to the multicast group that the sender requests for join according to the join group request from the sender. A multicast system and a multicast device are also provided.The sender performs the authentication for the receiver requesting to join the multicast group, and updates or creates the forward item for the receiver after the pass of the authentication, then reports the join group request to the upstream forward devices stage by stage, and every upstream forward device updates or creates the corresponding forward item for the downstream forward device or the sender.

Description

Multicast method and multicast system and multicast device

The present invention relates to data transmission techniques in wireless communication, and more particularly to a multicast method and a multicast system and a multicast device.

Say

Background technique

Multicast is a data transmission method between unicast and broadcast. That is, the destination address of the data frame is a multicast address, and the sender only transmits the data frame to multiple receivers belonging to the multicast group. end. In wireless communication, the difference between multicast and unicast is that multicast only sends a copy of a book of data; the difference from broadcast is that the multicast traffic is only received and processed by the listening device belonging to the multicast group member. For this one-to-many data transmission, multicast is more efficient than unicast and broadcast.

For example, in a wireless mesh network, any wireless device node can be used as a Mesh network node (for example, MP (Mesh Point), MN (Mesh Node)) or router. Thus each node can communicate with one or more peer nodes and send and receive data. Based on the above principles, the Mesh network is also known as the "multi-hop (lti-hop)" network. However, in the Mesh network, there is no mechanism for the STA to join the multicast group. All the STAs can be added to each multicast group. In this case, multicast flooding occurs when the multicast frame is delivered.

For example, if the STA that has joined the multicast group c wants to join the multicast group a, the STA requests to join the multicast group a to the switch, that is, the Mesh network node (for example, MAP) with access capability. The Mesh network node of the capability creates a multicast forwarding entry corresponding to the multicast group a for the STA, and requests the router, that is, the Mesh network node (for example, MPP) or the routing device outside the Mesh network that has added the portal function. A multicast forwarding entry is created, and the router creates a multicast forwarding entry based on the MAP request.

It can be seen that the Mesh network node with the access capability, the Mesh network node and the routing device that have added the portal function do not authenticate the STA that requests to join the multicast group, and the STA creates a multicast forwarding entry for the STA. The multicast data frame is forwarded. Therefore, multicast transmission according to the existing multicast mode is likely to cause multicast flooding. If all STAs join all multicast groups, even multicast is not multicast, but broadcast.

This adds a lot of unnecessary burden to the Mesh network and seriously affects the security of the system. Moreover, the Mesh network is a wireless transmission environment, and it cannot use the port control and other methods to control the group like the wired network. Broadcasting floods, so the danger of multicast flooding is more prominent in Mesh networks.

It can be seen that the existing multicast technology adds unnecessary burden to the system when transmitting multicast frames, and cannot effectively guarantee the security of the multicast, so that the reliability of the multicast is low. Summary of the invention

In view of this, a main purpose of the embodiments of the present invention is to provide a multicast method, which can effectively suppress multicast flooding, reduce network burden, and improve multicast reliability.

Another main object of the embodiments of the present invention is to provide a multicast system, which can effectively suppress multicast flooding, reduce network load, and improve multicast reliability.

A further main object of the embodiments of the present invention is to provide a multicast device, which can effectively suppress multicast flooding, reduce network load, and improve multicast reliability.

According to a main object of the present invention, the embodiment of the present invention provides a multicast method, including the following steps: The sending end authenticates the receiving end that requests to join the multicast group according to the request of the receiving end to join the multicast group; The receiving end is added to the forwarding entry corresponding to the multicast group that it is requesting to join, and sends a request to join the multicast group to the forwarding device. The forwarding device sends the multicast group request according to the request from the sending end. Add to the forwarding entry corresponding to the multicast group it is requesting to join.

According to another main object of the present invention, an embodiment of the present invention provides a multicast system, including: a receiving end, a sending end, and a forwarding device, where

The receiving end is configured to send a join multicast group request to the sending end, requesting to join the multicast group;

The sending end is configured to authenticate the receiving end that requests to join the multicast group according to the joining group request from the receiving end, and add the receiving end that is authenticated to the forwarding item corresponding to the multicast group that it is requesting to join. Medium, that is, update or create a forwarding entry, and send a join multicast group request to the forwarding device;

The forwarding device is configured to add the sending end to the forwarding item corresponding to the multicast group that the requesting party joins according to the joining multicast group request from the sending end.

According to still another main object of the present invention, an embodiment of the present invention provides a multicast device, including: a transceiver unit, receiving a request for joining a multicast group from the outside, and providing the request to the authentication unit; receiving the authentication result provided by the authentication unit, The forwarding device sends a request to join the multicast group;

The authentication unit receives the multicast group request provided by the transceiver unit, authenticates the request, adds the receiving end of the authentication to the forwarding item corresponding to the multicast group to which the request is made, and provides the authentication result to the transceiver unit.

As shown in the above technical solution, the transmitting end authenticates the receiving end that requests to join the multicast group, and then updates or creates a forwarding entry for the receiving end after the authentication is passed, and then reports the multicast group request to the upstream forwarding device. The upstream forwarding device updates or creates a corresponding forwarding entry for its downstream forwarding device or sender, so that the system does not Any device transmits multicast frames to the illegal receiving end, which suppresses multicast flooding in the network, reduces the burden on the system, and improves the reliability of multicast transmission.

DRAWINGS

FIG. 1 is a schematic structural diagram of a multicast system according to an embodiment of the present invention.

FIG. 2 is an exemplary flowchart of a multicast method in an embodiment of the present invention.

FIG. 3 is a structural diagram of a multicast system according to an embodiment of the present invention.

The figure (4 a c ) is a schematic flowchart of the step-by-step forwarding in the embodiment of the present invention.

Figure 5 (5 a^5d) is a schematic structural diagram of a group information list related message in the embodiment of the present invention.

FIG. 6 is a flowchart of a multicast method 1 according to an embodiment of the present invention.

Figure 7 is a flow chart of the multicast method 2 in the embodiment of the present invention.

FIG. 8 is a flowchart of a multicast method 3 in an embodiment of the present invention.

FIG. 9 is a schematic diagram of implementing multicast transmission in an embodiment of the present invention.

detailed description

The present invention will be further described in detail below with reference to the accompanying drawings.

In the embodiment of the present invention, the transmitting end authenticates the receiving end that requests to join the multicast group, and after the authentication is passed, updates or creates a forwarding entry for the receiving end, and then reports the multicast group request to the upstream forwarding device step by step. Referring to the group join request, each upstream forwarding device updates or creates a corresponding forwarding entry for its downstream forwarding device or sender, so that no device in the system transmits multicast frames for the illegal receiver.

FIG. 1 is a schematic structural diagram of a multicast system according to an embodiment of the present invention. As shown in FIG. 1, the multicast system in this embodiment includes: a receiving end, a sending end, and at least one forwarding device.

The receiving end sends a join group request to the sending end to request to join the multicast group.

The sender, according to the join group request from the receiver, authenticates the receiver that requests to join the multicast group; adds the receiver that passes the authentication to the forwarding entry corresponding to the multicast group that it is requesting to join, that is, updates or creates a forwarding entry. And sending a join group request to the forwarding device;

The forwarding device adds the sender to the forwarding entry corresponding to the multicast group it is requesting to join according to the join group request from the sender.

In actual applications, if the forwarding device is in multiple levels, the forwarding device needs to update or create a forwarding item. The process of forwarding the join group is forwarded to the upstream forwarding device, and the upstream forwarding device creates or updates the forwarding entry for the downstream device. The process of sending the join group request by the sending end and the forwarding device may be: directly forwarding the received joining group request. After the corresponding processing is performed according to the received join group request, a new join group request is generated and sent to the upstream forwarding device, that is, the initiative initiates the request.

After the receiving end joins the multicast group, the sending end further sends the multicast frame from the external multicast source to the receiving end of the corresponding multicast group.

Specifically, the transmitting end of the system as a multicast device includes: an authentication unit and a transceiver unit.

The transceiver unit receives the join group request sent by the external receiver and provides the authentication unit, and receives the authentication result provided by the authentication unit, and adds the receiving end that is authenticated to the forwarding item corresponding to the multicast group that it is requesting to join, that is, the update Or create a forwarding entry and send a join group request to the forwarding device;

The authentication unit receives the join group request provided by the transceiver unit, authenticates the receiver that requests to join the multicast group, and provides the authentication result to the transceiver unit.

In the above multicast device, the authentication unit may perform authentication according to the obtained group information list.

FIG. 2 is an exemplary flowchart of a multicast method in an embodiment of the present invention. As shown in FIG. 2, the multicast method in this embodiment includes the following steps:

In step 201, the receiving end that requests to join the multicast group is authenticated according to the joining group request of the receiving end. Step 202: Add the receiving end that is authenticated to the forwarding item corresponding to the multicast group that it is requesting to join, that is, update or create Forwarding the item, and sending a join group request to the forwarding device;

In this step, adding the receiving end to the forwarding item means: adding the identifier of the receiving end to the forwarding item; Step 203: Adding the sending end to the multicast group to which the requesting party joins according to the joining group request from the sending end In the forwarding item;

In this step, adding the sender to the forwarding entry means: adding the identifier of the sender to the forwarding entry. In the foregoing process, if the forwarding device is in multiple stages, after the step 203, the forwarding device further needs to forward the joining group request to the upstream forwarding device, and the upstream forwarding device creates or updates the forwarding item for the downstream device. The process of sending a join group request by the forwarding device may be: directly forwarding the received join group request, or generating a new join group request and sending the request to the upstream forwarding device after performing corresponding processing according to the received join group request. , that is, it initiates the request by itself.

The above is a general description of the multicast system, the multicast device, and the multicast method in the embodiment of the present invention.

In this embodiment, the security of multicast transmission can be further protected by issuing corresponding intra-group keys and/or multicast group identifiers.

The multicast group identifier in this embodiment may be any unique identifier, such as a multicast address, or The multicast group number and other pre-agreed identifiers used to identify the multicast group. When the technical solution of the present invention is used in different wireless environments, the multicast address is a different type of address. For example, when the technical solution of the present invention is applied to the data link layer, that is, the second layer of the network layer, the multicast address may be Medium access Contro l (MAC) address; when the technical solution of the present invention is applied to the Internet Protocol (IP) layer, the multicast address may be an IP address; The code is used as the multicast group identifier. The multicast frame also carries the same type of multicast group identifier, and the receiving end can select the corresponding intra-group key.

The multicast system, the multicast device, and the multicast method in this embodiment are described in detail below by taking the multicast transmission in the Mesh network as an example.

In this embodiment, the receiving end of the multicast group is authenticated, and the forwarding entry of the multicast group is created for the receiving end, or the receiving end is added to the forwarding item of the multicast group. . The sender can distinguish multiple multicast groups and their forwarding entries based on the multicast group ID.

Thus, in this embodiment, the sending end stores the multicast group information corresponding to each multicast group, including: information of multiple multicast group identifiers, multicast policies, forwarding items, and member lists of multicast groups.

In this embodiment, the legality of the receiving end is authenticated according to the group information list of the receiving end, so that legal members in the non-integrated group can be prevented from joining the multicast group, thereby reducing the burden on the system.

FIG. 3 is a structural diagram of a multicast system according to an embodiment of the present invention. As shown in FIG. 3, the multicast system in this embodiment includes: a sender 301, a receiver 302, and an authentication server 303.

The sending end 301 is configured to: after the receiving end 302 enters the area to which the sending end 301 belongs, request the access authentication information from the receiving end 302; and request the authentication server 303 to perform access authentication on the receiving end 302 according to the response from the receiving end 302. And requesting to obtain the group information list; performing information exchange with the receiving end 302 and the authentication server 303, and providing the authentication information of the receiving end 302 to the authentication server 303; receiving the response from the authentication server 303, including the receiving end 302 group information list, and storing Receiving the group information list of the receiving end 302, confirming that the receiving end 302 successfully accesses, and sending a successful access message to the receiving end 302; and querying whether the current request exists in the group information list of the receiving end 302 according to the joining group request from the receiving end 302. The joined multicast group (that is, whether there is a certain identifier corresponding to the multicast group currently requested to join in the group information list). If yes, the receiving end 302 is a legal group member of the multicast group, and the receiving end 302 is added. The forwarding entry of the multicast group (the forwarding entry of the multicast group has been created) or the receiving end 302 Create a new forwarding entry for the multicast group (the receiving end 302 is the first member of the multicast group, and thus the forwarding entry of the multicast group is not created); receiving the multicast frame from the outside, according to the multicast forwarding entry The received multicast frame is sent to the corresponding receiving end.

The receiving end 302 is configured to apply for access authentication to the sending end 301 according to the request of the sending end 301;

301 performs information exchange, provides authentication information to the authentication server 303 through the sender 301, receives an authentication success message from the S sender 301, sends a join group request to the sender 301, and receives a multicast frame from the sender 301.

The authentication server 303 is configured to perform information interaction with the sending end 301 according to the request from the sending end 301. Acquiring the authentication information of the receiving end 302, and performing access authentication on the receiving end 302. After the access authentication is passed, the group information list of the receiving end 302 is obtained from the external subscription network, and the information list including the receiving end 302 is sent to the sending end 301. the response to.

In an actual application, the sending end 301 may be further configured to: after requesting the multicast group that is currently requested to join in the group information list that is queried to the receiving end 302, request the authentication server 303 to obtain the group information list of the receiving end 302. The obtained group information list may be an updated group information list; the sending end 301 may also obtain the group information list directly from the subscription network or other network device.

When the receiving end 302 exits the current multicast group, the sending end group 301 may send an exit multicast group report (hereinafter referred to as an exit group report).

In this case, the sending end 301 can also update the member list in the multicast group information according to the exit group report from the receiving end 302. The authentication server 303 can also be connected to the contracted network or the contracted network, and can Obtaining the network element of the receiving end 302 group information list from the contracting network.

As an example, the multicast and multicast transmission in the Mesh network is taken as an example, and the Mesh network called the "multi-hop" network has the feature that each wireless device node can transmit and receive multicast frames. Therefore, the multicast system in this embodiment may further include: a forwarding device 304.

Thus, the multicast frame received by the sender 301 may be directly from the routing device or from the forwarding device 304. Therefore, the multicast group information in this embodiment further includes: a forwarding device corresponding to each multicast group.

After the receiving end 301 determines that the receiving end 302 is a legal group member of the multicast group, the sending end 302 sends a request for the receiving end 302 to join the multicast group to the forwarding device 304 according to the multicast group information; After the receiving end 302 deletes the forwarding entry of the corresponding multicast group, the receiving end 302 determines whether there are other members in the forwarding item, that is, whether the receiving end 302 is the last member of the forwarding item of the multicast group, and if so, Deleting the forwarding item and sending an exit group report to the forwarding device 304;

The forwarding device 304 adds the forwarding entry 301 to the forwarding entry of the multicast group according to the joining group request of the sending end 301 (the forwarding entry of the multicast group has been created) or creates a new forwarding entry of the multicast group for the sending end 301. (The sender 301 is the first member of the multicast group, and thus the forwarding entry of the multicast group is not created). According to the exit group report from the sender 301, the sender 301 is forwarded from the corresponding multicast group. Deleted.

The sending end 301 can forward the joining group request to the multiple forwarding devices, but only one of the plurality of forwarding devices that have received the group joining request creates a forwarding item for the sending end 301 or adds the sending end 301 to the existing forwarding. In the item. Specifically, the forwarding device creates a forwarding entry or adds the sending end 301 to the existing forwarding entry, which is determined by a routing mechanism preset in the Mesh network.

If the sending end 301 needs to pass the multiple forwarding devices to receive the multicast frame from the multicast source, the forwarding device 304 sends a request to the upstream forwarding device of the forwarding device 304 according to the request sent by the sending end 301. The upstream forwarding device that receives the request creates a forwarding entry for its downstream forwarding device or adds its downstream forwarding device. Enter an existing forwarding item.

In this case, when the forwarding entry is updated according to the exit group report, after the forwarding device 301 deletes the forwarding entry from the corresponding multicast group, the forwarding device 304 determines whether there are other members in the forwarding entry, that is, determines the sending end. 301 is the last member of the forwarding entry of the multicast group. If yes, the forwarding entry is deleted, and the exit group report is sent to the upstream forwarding device, and the upstream forwarding device that receives the report of the exit group is its downstream forwarding device. Update or delete the forwarding entry. If the corresponding forwarding entry is deleted for its downstream forwarding device, you need to send the exit group report to its upstream forwarding device, and update or delete it step by step.

FIG. 4a is a schematic flowchart of a step-by-step forwarding of a join group request according to an embodiment of the present invention. As shown in FIG. 4a, the transmitting end 301 authenticates the receiving end 302 according to the joining group request and the obtained group information list of the receiving end 302, and then creates or updates a forwarding item for the receiving end 302, and forwards the device through the forwarding device. (n is a positive integer), the join group request is reported step by step, and each forwarding device i (lin) that receives the join group request is updated or created by the downstream forwarding device i-1 (or the sender 301) that sends the request. Corresponding to the forwarding item of the multicast group.

After the sender 301 and all forwarding devices i update or create a forwarding entry, multicast transmission can be implemented. FIG. 4b is a schematic flowchart of forwarding a multicast frame step by step according to an embodiment of the present invention. As shown in FIG. 4b, the forwarding device n receives the multicast frame from the multicast source, searches for the forwarding entry corresponding to the multicast group to which the received multicast frame belongs, and sends the multicast frame to the downstream forwarding device i-1. After being sent to the forwarding device 1, the forwarding device 1 searches for the corresponding forwarding item, and sends the multicast frame to the sending end 301. The transmitting end 301 sends the multicast frame to the receiving end 302 according to the corresponding forwarding item.

Similarly, the exit group report can also be forwarded step by step.

FIG. 4c is a schematic flowchart of a step-by-step forwarding of an exit group report according to an embodiment of the present invention. As shown in Figure 4c, the sender

301, according to the exit group report of the receiving end 302, update or delete the forwarding item for the receiving end 302, and after deleting the corresponding forwarding item, send an exit group report to the forwarding device 1, and the forwarding device 1 updates or deletes the corresponding forwarding item. And after the forwarding item is deleted, it is reported to the forwarding device n step by step. Each forwarding device i ( l i n ) that receives the join group request is a forwarding device that sends the request to the downstream forwarding device i-1 (or the sender 301) to update or delete the corresponding multicast group.

The sending end 301 and all the forwarding devices may directly forward the received joining group request, or may generate a new joining group request and send it to the upstream forwarding device after the corresponding processing according to the received joining group request, that is, the active device itself Initiate a request.

The transmitting end 301 itself can also serve as a forwarding device of the other transmitting end. In this case, the transmitting end 301 also creates, updates, or deletes the forwarding items of the multicast group for the receiving end of the other transmitting end according to the working principle of the forwarding device 304.

Specifically, the transmitting end 301, that is, the multicast device, in this embodiment includes: a transceiver unit 311, an authentication unit 312, and a storage unit 313.

The transceiver unit 31 1 is configured to: after the receiving end 302 enters the area where the sending end 301 belongs, the request receiving end 302 is connected. Entering the authentication information; transmitting an access authentication request to the authentication unit 312 according to the response from the receiving end 302; transmitting an authentication success message from the authentication unit 312 to the receiving end 302, and transmitting the joining group request to the forwarding device 304; At the end 302, the join group request and the exit group report are sent to the authentication unit 312; the multicast frame from the outside is received, according to the multicast group forwarding item provided by the storage unit 313 (for example, including all the receivers belonging to the multicast group) The forwarding item information of the related identifier is sent to the receiving end corresponding to the multicast group to which the multicast group belongs.

The authentication unit 312 is configured to request the authentication server 303 to perform access authentication on the receiving end 302 according to the joining group request from the transceiver unit 31 1 and request to obtain the group information list; and receive the receiving end 302 from the authentication server 303. The group information list is stored in the storage unit 313, the receiving end 302 is successfully accessed, and the successful access message is sent to the transceiver unit 31 1; And the corresponding group information list is obtained from the storage unit 313, and the multicast group that the current request to join is included in the group information list of the receiving end 302. If yes, the receiving end 302 is determined to be a legal group member of the multicast group. The receiving end 302 is added to the multicast group, and the pre-stored multicast group information including the forwarding item is updated, that is, the receiving end 302 joins the forwarding item of the multicast group (the forwarding item of the multicast group has been created) or is received. End 302 creates a new forwarding entry for the multicast group (the receiving end 302 is the first member of the multicast group, and thus is not created. And the multicast group information is sent to the storage unit 313, and the group success message is sent to the transceiver unit 311. If not, the receiver 302 is determined to be illegal. The member of the group, refuses to join the multicast group, sends a join group failure message to the transceiver unit 31 1 , or sends an access authentication request to the authentication server 303 (re-acquires the group information list of the receiver 302); according to the packet from the transceiver unit 31 1 The group report and the forwarding item in the multicast group information stored in the storage unit 313 are updated (the corresponding multicast group information in the storage unit 313 is read, updated, and then sent to the storage unit 313 for storage, and the original is deleted. The information is that the receiving end 302 is deleted from the forwarding entry of the corresponding multicast group. If the receiving end 302 is the last member of the multicast group forwarding item, the forwarding item may be deleted.

The storage unit 313 stores a list of group information from the authentication unit 312 and provides it to the authentication unit 312. The multicast group information including the forwarding items from the authentication unit 312 is stored and provided to the transceiver unit 31 1 and the authentication unit 312.

In the above-mentioned transmitting end 301 as a multicast device, the authenticating unit 312 can also obtain the group information list directly from the contract network or other network devices. If the group information list of the receiving end includes the multicast group that the user is currently requesting to join, and the authentication unit 312 does not store the multicast group information of the multicast group, for example, the receiving end is the first member of the multicast group, The authentication unit 312 does not create a member list of the multicast group. In this case, the authentication unit 312 generates multicast group information including a multicast group member list and a multicast group identifier, and then provides the multicast group information to the transceiver unit 311.

The above-mentioned functional unit may also be included in the forwarding device 304. That is to say, the forwarding device 304 may also serve as a transmitting end of other receiving ends, that is, a multicast device.

In a practical application, the forwarding device 304 may be a wireless device node such as a MAP or an MPP. If the forwarding device 304 is an MPP, the multicast frame received by the device may be from a wireless device node in the mesh network as a routing device. It can also come from a router outside the Mesh network.

In the actual application, the following scenarios may also be encountered: The receiving end first accesses the sending end 1, that is, the sending end 1 is the original transmitting end of the receiving end, receives the multicast frame sent by the sending end 1, and then switches for some reason. To the sender 2, that is, the sender 2 is the current sender of the receiver.

In this case, the sender 2 does not have the group information list of the receiver, but the group information list of the receiver can be obtained from the network element such as the authentication server 303, and can also be obtained from the sender 1.

If the sender 2 is obtained from the sender 1, the sender 1 can exchange some information (including a group information list) or all information about the receiver with the "fast handover mechanism" to the sender 2 through the "fast handover mechanism". o

For example, in the fast handover process, for example, the sender 2 initiates a group information list request to the sender 1. Figure

5a is a schematic structural diagram of a group information list request frame in the embodiment of the present invention. As shown in FIG. 5a, the group information list request frame includes: a group information query (Group List Query) information element (Information El ement, IE). As shown in Figure 5b, the group information list query IE includes information such as the MAC address (STA MAC Addres s) of the receiving end (such as STA).

After receiving the request frame as shown in FIG. 5a, the transmitting end 1 sends a group information list response frame to the transmitting end 2. Figure

5c is a schematic structural diagram of a group information list response frame in the embodiment of the present invention. As shown in Figure 5c, the group information list response frame includes: Group Li st Re sponse IE. As shown in FIG. 5d, the group information list response IE includes a list of group information about the receiving end (such as STA) stored in the transmitting end 1.

Of course, it can also be carried in a message frame in the fast handover mechanism, and the group information list is used as an information resource, and is encapsulated in the resource information container data information element (Resource Information Container Data IE) at the originating end of the receiving end and The current sender interacts.

In this way, the sending end 301 can also send a group information list query frame as shown in FIG. 5a to the original sending end of different receiving ends, requesting to obtain a group information list, and receiving the group information list as shown in FIG. 5c from the original transmitting end of different receiving ends. Responding to the frame, and storing the group information list in the frame; if the sending end 301 is the original transmitting end of a certain receiving end, the frame may be queried according to the received group information list as shown in FIG. 5a, and the receiving end group The information list is sent to the current sender of the receiving end through a group information list response frame as shown in FIG. 5c.

In the following, a Mesh network node (such as MAP) with access capability is used as the transmitting end, the STA is used as the receiving end, the AS is used as the authentication server, the accessing Mesh network node (such as MAP), and/or the ordinary Mesh network node (such as MP) and/or a Me sh network node (such as MPP) with an export function as an example of a forwarding device, and a multicast method based on the above system and device will be described.

The multicast method of this embodiment includes Method 1, Method 2, and Method 3. The method 1 is: the STA first applies to the AS to register and register a multicast group, and then applies to the MAP to join the multicast group. After determining that the group information list of the STA includes the multicast group currently applied for, the MAP STA joins a multicast forwarding entry or creates a new multicast forwarding for it. If the group information list of the STA does not include the multicast group that is currently applied for, the network group is denied to join the multicast group. The method 2 is as follows: The MAP does not include the current application in determining the group information list of the STA. After the joined multicast group, the AS applies to the subscription network to obtain the group information list of the STA, that is, updates the group information list of the STA, and authenticates the STA to join the multicast group again through the updated group information list. Method 3 is: After determining that the STA group information list does not include the multicast group currently applied for, the MAP directly requests the subscription network to obtain the group information list of the STA, updates the current list, and passes the updated group information. The list authenticates the STA again.

FIG. 6 is a flowchart of a multicast method 1 according to an embodiment of the present invention. As shown in FIG. 6, the multicast method 1 in this embodiment includes the following steps:

Step 601: The user of the STA subscribes to register one or more multicast groups in the subscription network through the AS.

The foregoing step 601 is a process of opening a new service and registering a multicast group for the user of the STA, and may also be performed after the subsequent step, or concurrently with the subsequent steps.

Step 602: The STA wants to access the subscription network to which the MME belongs. Therefore, the MAP sends an identity authentication request to the STA, requesting the STA to apply for access authentication.

In this method, the identity authentication request may be an 802. IX EAP Request; the MAP may also not send the request to the STA, but the STA sends the access authentication request directly to the MAP, that is, directly performs step 603.

Step 603: The STA sends an identity authentication response to the MAP according to the request of the MAP, requesting access authentication. In this method, the identity authentication response may be an 802. IX EAP Response.

Step 604: The MAP sends an access authentication request to the AS according to the identity authentication response sent by the STA, and requests the STA that accesses the network to perform authentication.

In this method, the access authentication request may be an EAP Request, and the EAP Reque st may also be sent to the AS in the Access Request of the RADIUS protocol.

Step 605: The AS exchanges information with the STA through the MAP to obtain authentication authentication information of the STA, and authenticates the STA.

Step 606 to step 607, after the authentication succeeds, the AS sends a group information list request to the subscription network, requests to obtain the group information list of the authenticated STA, and receives the group information list of the STA from the subscription network.

Step 608: The AS sends an access authentication response including the group information list of the STA to the MAP.

Step 609: After receiving the access authentication response, the MAP saves the group information list of the STA, and sends an authentication success message to the STA.

In this method, the authentication success message may be an EAP Succes s message; the MAP may also obtain the group information list of the STA directly from the subscription network; or, the MAP obtains the group information list of the STA from the MAP to which the STA originally belongs. Step 610: When a multicast group needs to be added, the STA sends a join group request to the MAP to request to join a multicast group.

In this step, the join group request sent by the STA to the MAP may be an IGMP Report (IGMP Report) message based on the Internet Protocol Management (IGMP) protocol, or may be a request message based on the MLD protocol, or may be ACTION frame.

Step 611: The MAP queries the internally stored group information list of the STA according to the request of the STA. If the group information list includes the multicast group that the STA is currently applying to join, the MAP approves the request of the STA. If the forwarding group has a forwarding entry, the multicast group information of the multicast group is updated, that is, the forwarding entry of the multicast group is updated, and step 612 is performed; if the STA is the first group member of the multicast group to which the current application is added. Then, a forwarding entry is created for the multicast group, and step 612 is performed.

In this step, if the group information list does not include the multicast group that the STA is currently applying to join, the STA is determined to be an illegal group member. The MAP may also include the multicast group that the STA is currently applying to join in the group information list. And re-acquiring the group information list of the STA to the subscription network, and querying the updated group information list to include the multicast group that the STA is currently applying to join.

Step 612: The MAP sends a join group request to its upstream forwarding device, such as a MAP, or MPP, or MP of another STA.

In this step, the join group request sent by the MAP may be an IGMP Report message from the STA, that is, a direct join group request of the STA; or an IGMP Report message generated by the MAP itself.

Step 613: The MAP or the MPP or the MP as the forwarding device updates the MAP for sending the request or creates a forwarding entry of the multicast group to which the request is added according to the received join group request.

In the foregoing steps 612 to 613, if there are multiple upstream forwarding devices of the MAP, the upstream forwarding device needs to be forwarded up to the routing device or the MPP carrying the router, and the upstream forwarding device updates the downstream forwarding device that sends the group request. Create a forwarding entry for the multicast group to which the STA is currently applied.

In this way, all nodes add their downstream nodes to the corresponding multicast forwarding entries.

Steps 614 to 616, after receiving the multicast frame from the routing device, the MPP that is the forwarding device searches for the forwarding entry of the multicast group to which the multicast frame belongs, and sends the received multicast frame according to the forwarded forwarding item. If the MAP that receives the multicast frame is also used as the forwarding device of the other MAP or MP, the MAP also searches for the forwarding entry of the multicast group to which the multicast frame belongs, and receives the forwarding entry according to the forwarded entry. The multicast frame is sent to the corresponding downstream forwarding device until the multicast frame is sent to the corresponding STA.

In this way, the STAs in the non-multicast group are prevented from receiving the multicast frames of the multicast group, which reduces the burden on the system. Step 617: When the STA wants to exit a multicast group, send an exit group report to the MAP.

Step 618: The MAP updates, according to the report of the STA, a forwarding item of the multicast group that the STA requests to exit, for example, The STA is deleted from the forwarding entry.

If the STA is the last member of the queried group, that is, before the STA is deleted, the forwarding entry of the multicast group includes only the STA, and then the process proceeds to step 619. Otherwise, the process ends after this step. .

Step 619 to step 620, the MAP sends an exit group report to its upstream forwarding device, for example, the MAP, MP, or MPP of the other STA, and the MAP or MP or MPP as the forwarding device reports the report according to the received exit group. The MAP updates the forwarding entry of the exiting multicast group, for example, deleting the MAP from the forwarding entry.

In the foregoing steps 619 to 620, if the upstream forwarding device of the MAP is multiple, when the MAP is determined to be the last member of the multicast group, the forwarding device of the MAP needs to send an exit to the upstream forwarding device. Group report. The upstream forwarding device of the forwarding device deletes or updates the forwarding entry of the multicast group according to whether the forwarding device is the last member of the multicast group. By analogy, each forwarding device can be forwarded up to the MPP of the access routing device, and the upstream forwarding device updates or deletes the forwarding entry of the multicast group that the STA exits for the downstream forwarding device.

At this point, the process ends.

In the above process, after step 617, the STA may also cancel the registered multicast group to the AS; the STA may also perform step 601 to register a new multicast group at any time; after step 620, if the MPP receives the exit group report Then, the forwarding entry of the corresponding multicast group is found. If no STA is used by the STA in the entire mesh network, the exit group report is sent to the router.

The above is a description of the method 1 in the present embodiment, and the method 2 in the present embodiment will be described in detail below. Figure 7 is a flow chart of the multicast method 2 in the embodiment of the present invention. As shown in the figure, the multicast method 2 in this embodiment includes the following steps:

Step 701: The STA wants to access the subscription network to which the MME belongs. Therefore, the MAP sends an identity authentication request to the STA, requesting the STA to apply for access authentication.

In this method, the identity authentication request may be an 802. IX EAP Request; the MAP may not send the request to the STA, but the STA sends the access authentication request directly to the MAP, that is, directly performs step 702.

Step 702: The STA sends an identity authentication response to the MAP according to the request of the MAP, requesting access authentication. In this method, the identity authentication response may be an 802. IX EAP Response.

Step 703: The MAP sends an access authentication request to the AS according to the identity authentication response sent by the STA, and requests the STA that accesses the network to perform authentication.

Step 704: The AS exchanges information with the STA through the MAP, and obtains authentication authentication information of the STA. Certify.

Step 705 to step 706, after the authentication succeeds, the AS sends a group information list request to the subscription network, requests to obtain the group information list of the authenticated STA, and receives the group information list of the STA from the subscription network.

Step 707: The AS sends an access authentication response including the group information list of the STA to the MAP.

Step 708: After receiving the access authentication response, the MAP saves the group information list of the STA, and sends an authentication success message to the STA.

In this method, the authentication success message may be an EAP Succes s message; the MAP may also obtain the group information list of the STA directly from the subscription network; or, the MAP obtains the group information list of the STA from the MAP to which the STA originally belongs.

Step 709: The user of the STA subscribes to register one or more multicast groups in the subscription network through the AS.

The foregoing step 709 is a process of opening a new service and registering a multicast group for the user of the STA, and may also be performed after the subsequent step or concurrently with the subsequent steps.

Step 710: When a multicast group needs to be added, the STA sends a join group request to the MAP to request to join a multicast group.

In this step, the join group request sent by the STA to the MAP may be an IGMP Report message based on the IGMP protocol, a request message based on the MLD protocol, or an ACT ION frame.

Step 711: The MAP queries the internally stored group information list of the STA according to the request of the STA. If the group information list includes the multicast group that the STA currently joins, the request of the STA is approved. If there is a forwarding entry in the joined multicast group, the multicast group information of the multicast group is updated, that is, the forwarding entry of the multicast group is updated, and step 717 is performed; if the STA is the first of the multicast group to which the current application is added. A group member creates a forwarding entry for the multicast group and performs step 717. If the group information list does not include the multicast group that the STA is currently applying to join, the STA is not determined to be an illegal group member but is executed. Step 712.

Step 712 to step 715, the MAP sends an access authentication request to the AS, and requests to obtain a group information list of the STA. The AS sends a group information list request to the subscription network, requests to obtain a group information list of the authenticated STA, and receives the group information list from the subscribed network. The STA group information list; the AS sends an access authentication response including the STA group information list to the MAP.

In the foregoing steps 712 to 715, the MAP may also re-acquire the group information list of the STA directly to the subscription network; or obtain the group information list from the STA original MAP.

Step 716: The MAP updates the group information list of the STA that is stored in the STA according to the group information list of the received STA, and queries the updated group information list to include the multicast group that the STA is currently applying to join. Then, step 717 is performed. Otherwise, the STA is denied to join the multicast group that it is applying to join.

In this way, the correctness of the MAP to authenticate the STA that requests to join the multicast group is improved. Step 717: The MAP sends a join group request to its upstream forwarding device, such as a MAP, or MP, or MPP of another STA.

Step 718: The MAP or the MP or the MPP as the forwarding device updates the STA that sends the request or creates a forwarding entry of the multicast group to which the request is added according to the received join group request.

In the above steps 717 to 718, if there are multiple upstream forwarding devices of the MAP, it is required to forward up to the routing device or the MPP carrying the router, and the upstream forwarding device updates the downstream forwarding device that sends the group request. Or create a forwarding entry for the multicast group that the STA is currently applying to join.

In this way, all nodes add their downstream nodes to the forwarding entries of the corresponding multicast group.

Steps 719 to 721, after receiving the multicast frame from the routing device, the MPP that is the forwarding device searches for the forwarding entry of the multicast group to which the multicast frame belongs, and sends the received multicast frame according to the forwarded forwarding item. If the MAP that receives the multicast frame is also used as the forwarding device of the other MAP or MP, the MAP also searches for the forwarding entry of the multicast group to which the multicast frame belongs, and receives the forwarding entry according to the forwarded entry. The multicast frame is sent to the corresponding downstream MAP until the multicast frame is sent to the corresponding STA.

In this way, the STAs in the non-multicast group are prevented from receiving the multicast frames of the multicast group, which reduces the burden on the system. Step 722: When the STA wants to exit a multicast group, send an exit group report to the MAP.

Step 723: The MAP updates, according to the report of the STA, a forwarding item of the multicast group that the STA requests to exit, for example, deleting the STA from the forwarding item.

If the STA is the last member of the queried group, that is, before the STA is deleted, the forwarding entry of the multicast group includes only the STA, and then the process proceeds to step 724. Otherwise, the process ends after this step. .

Step 724 to step 725, the MAP sends an exit group report to the upstream forwarding device, and the MAP or MP or MPP as the forwarding device updates the forwarding entry of the multicast group exited by the STA for the MAP that sends the report according to the received exit group report. , for example, remove the MAP from the forwarding entry.

In the foregoing steps 724 to 725, if the upstream forwarding device of the MAP is multiple, when the MAP is determined to be the last member of the multicast group, the forwarding device of the MAP needs to send an exit to the upstream forwarding device. Group report. The upstream forwarding device of the forwarding device deletes or updates the forwarding entry of the multicast group according to whether the forwarding device is the last member of the multicast group. By analogy, each forwarding device can be forwarded up to the MPP of the access routing device, and the upstream forwarding device updates or deletes the forwarding entry of the multicast group exited by the STA for the downstream forwarding device.

At this point, the process ends.

In the above process, after step 722, the STA may also cancel the registered multicast group to the AS; the STA may also Step 709 is performed at any time to register a new multicast group. After step 725, if the MPP receives the exit group report and finds the forwarding entry of the corresponding multicast group, it is found that none of the STAs in the entire mesh network use the multicast. If it is grouped, it sends an exit group report to the router.

The above is a description of the method 2 in the present embodiment, and the method 3 in the present embodiment will be described in detail below. FIG. 8 is a flowchart of a multicast method 3 in an embodiment of the present invention. As shown in FIG. 8, the multicast method in this embodiment

3 includes the following steps:

Step 80: 807, the STA wants to access the subscription network to which the MME belongs. Therefore, the MAP sends an identity authentication request to the STA, requesting the STA to apply for access authentication. The STA sends the access authentication to the AS through the MAP according to the request of the MAP. The AS performs the information exchange with the STA through the MAP, obtains the authentication authentication information of the STA, authenticates the STA, and after the authentication succeeds, sends a group information list request to the subscription network, requesting to obtain the group information list of the authenticated STA, and The group information list of the STAs from the contracted network is sent to the MAP through the access authentication response.

The operation of the above step 80 f step 807 can be the same as the step 70 f step 707 in the method 2 of the embodiment.

Step 808: After receiving the access authentication response, the MAP saves the group information list of the STA, and sends an authentication success message to the STA.

Step 809: The user of the STA registers one or more multicast groups through the AS in the contracted network.

The foregoing step 809 is a process of opening a new service and registering a multicast group for the user of the STA, and may also be performed after the subsequent step or concurrently with the subsequent steps.

Step 810: When a multicast group needs to be added, the STA sends a join group request to the MAP to request to join a multicast group.

Step 811: The MAP queries the internally stored group information list of the STA according to the request of the STA. If the group information list includes the multicast group that the STA is currently applying to join, the MAP approves the request of the STA. If there is a forwarding entry in the broadcast group, the multicast group information of the multicast group is updated, that is, the forwarding entry of the multicast group is updated, and step 815 is performed; if the STA is the first group member of the multicast group to which the current application is added. Then, a forwarding entry is created for the multicast group, and step 815 is performed. If the group information list does not include the multicast group that the STA is currently applying to join, the STA is not determined to be an illegal group member, but step 812 is performed. .

Step 812 to step 813, the MAP directly sends a group information list request to the subscription network, requests to obtain a group information list of the authenticated STA, and receives a group information list of the STA from the subscription network. In the foregoing steps 812 to 813, the MAP may also reacquire the group information list of the STA through the AS to the subscription network; or obtain the group information list from the STA original MAP.

Step 814: The MAP updates the group information list of the STA that is stored in the STA according to the group information list of the received STA, and queries the updated group information list to include the multicast group that the STA is currently applying to join. Then, go to step 815. Otherwise, the STA is denied to join the multicast group it is applying to join.

In this way, the correctness of the MAP to authenticate the STA requesting to join the multicast group is improved.

Step 815: The MAP sends a join group request to its upstream forwarding device, such as a MAP, or MP, or MPP of another STA.

Step 816: The MAP or the MP or the MPP as the forwarding device sends a MAP update for the request or a forwarding entry of the multicast group to which the associated STA applies to join according to the received join group request.

In the foregoing steps 815 to 816, if there are multiple upstream forwarding devices of the MAP, the upstream forwarding device needs to be forwarded up to the routing device or the MPP carrying the router, and the upstream forwarding device updates the downstream forwarding device that sends the group request. Or create a forwarding entry for the multicast group that the STA is currently applying to join.

Steps 817 to 819, after receiving the multicast frame from the routing device, the MPP that is the forwarding device searches for the forwarding entry of the multicast group to which the multicast frame belongs, and receives the received multicast frame according to the forwarded forwarding item. The MAP is sent to the corresponding MAP. If the MAP that receives the multicast frame is also used as the forwarding device of the other MAP or MP, the MAP also searches for the forwarding entry of the multicast group to which the multicast frame belongs, and receives the forwarding entry according to the forwarded item. The received multicast frame is sent to the corresponding downstream MAP or MP until the multicast frame is sent to the corresponding STA.

In this way, the STAs in the non-multicast group are prevented from receiving the multicast frames of the multicast group, which reduces the burden on the system. Step 820: When the STA wants to exit a multicast group, send an exit group report to the MAP.

Step 821: The MAP updates, according to the report of the STA, a forwarding item of the multicast group that the STA wants to exit, for example, deleting the STA from the forwarding item.

If the STA is the last member of the queried group, that is, before the STA is deleted, the forwarding entry of the multicast group includes only the STA, and then step 822 is continued. Otherwise, the process ends after this step. .

Step 822 to step 823, the MAP sends an exit group report to the upstream forwarding device, and the MAP or MP or MPP as the forwarding device updates the forwarding entry of the multicast group exited by the STA for the MAP that sends the report according to the received exit group report. , for example, remove the MAP from the forwarding entry.

In the above steps 822 to 823, if there are multiple upstream forwarding devices of the MAP, the MAP is determined. When it is the last member of the multicast group, the forwarding device of the MAP needs to send an exit group report to its upstream forwarding device. The upstream forwarding device of the forwarding device deletes or updates the forwarding entry of the multicast group according to whether the forwarding device is the last member of the multicast group. By analogy, each forwarding device can forward up to the MPP of the access routing device, and the upstream forwarding device updates or deletes the forwarding entry of the multicast group that the STA exits.

At this point, the process ends.

In the above process, after step 820, the STA may also cancel the registered multicast group to the AS; the STA may also perform step 809 to register a new multicast group at any time; after step 823, if the MPP receives the exit group report Then, the forwarding entry of the corresponding multicast group is found. If no STA is used by the STA in the entire mesh network, the exit group report is sent to the router.

FIG. 9 is a schematic diagram of implementing multicast transmission in an embodiment of the present invention. As shown in Figure 9, the multicast system includes: MPP, ΜΡ ΜΡ 2 > ΜΑΡ ΜΑΡ 4 STA1~STA6. MAPI mouth MAP2 is connected to MP1, MAP3 mouth MAP4 is connected to MP2; STA1 and STA2 are connected to MAPU STA3 to MAP2, STA4 is connected to MAP3; STA5 and STA6 are connected to MAP4; STA1, STA3 and STA5 is a member of the a multicast group, and STA2, STA4, and STA6 are members of the b multicast group.

If STA3 sends the IGMP report added to group b to MAP 2, MAP2 authenticates it and finds

STA3 is not a legal member of the multicast group it requests. MAP2 refuses to send STA3 to MP1 (directly forwards the received message, or generates a new message and sends it). IGMP report, other nodes in the network do not need to send. The IGMP report reduces the burden on the nodes and reduces the occupation of network bandwidth.

If MAP2 does not authenticate STA3, it directly creates or adds STA3 to the b-group forwarding entry according to the IGMP report sent by STA3, and then forwards the IGMP report to MP1. After receiving the report, MP1 finds that There are forwarding entries for group b, so MAP2 is added to the list of forwarding entries for its group b.

Thus, when MP 1 receives the multicast data frame of group b, it will send multicast data to both MAPI and MAP2. It can be seen that if the technical solution in this embodiment is applied to the Mesh network, the STA cannot join the multicast group arbitrarily, and randomly receives the data frame of a multicast group, thereby increasing the security of the multicast data. Moreover, the number of multicast frames forwarded by each MAP, MPP, and MP is effectively suppressed, thereby suppressing multicast flooding in the network. When the size of the mesh network is relatively large, the effect of this scheme is very obvious.

In this embodiment, as the transmitting end of the multicast device, an intra-group key may be generated for each multicast group, the multicast frame is encrypted by using the intra-group key, and the intra-group key and the multicast group identifier are sent to The receiving end in the corresponding multicast group, that is, the receiving end that authenticates, the receiving end in the multicast group decrypts the received multicast frame by using the same intra-group key according to the multicast group identifier. The implementation principle can be the same as that of the first embodiment.

The above is only the preferred embodiment of the present invention and is not intended to limit the scope of the present invention. Any modifications, equivalent substitutions, and improvements made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Claims

Claim

A multicast method, characterized in that the method comprises the following steps:

The sender authenticates the receiver that requests to join the multicast group according to the request of the receiver to join the multicast group. The sender adds the receiver that passes the authentication to the forwarding entry corresponding to the multicast group it is requesting to join, and sends the packet to the forwarding device. Sending a request to join the multicast group; wherein, the forwarding device adds the sending end to the forwarding item corresponding to the multicast group to which the requesting party joins according to the request to join the multicast group from the sending end.

2. The method according to claim 1, wherein the authenticating of the receiving end requesting to join the multicast group is:

The sender obtains a list of group information of the receiving end;

According to the request to join the multicast group sent by the receiving end, query whether the group information list corresponding to the receiving end includes the multicast group that the receiving end is currently applying to join. If yes, the authentication succeeds. Otherwise, the authentication fails.

The method according to claim 2, wherein the method further comprises: the receiving end registering the multicast group with the subscription network, and the subscription network updating the pre-stored group information list of the receiving end;

The obtaining, by the sending end, the group information list of the receiving end includes:

The receiving end requests the sending end to perform access authentication; the sending end sends an access authentication request to the authentication server according to the request of the receiving end; the authentication server requests the subscription network to obtain the group information list of the receiving end according to the received authentication request, and Sending a list of group information from the subscription network to the sender; the sender receiving and storing the group information list of the receiver from the authentication server;

Or the obtaining, by the sending end, the group information list of the receiving end includes:

The sending end requests the sending end that has been accessed by the receiving end to obtain the group information list of the receiving end, and receives and stores the group information list from the original sending end.

The method according to claim 1, wherein, if the authentication fails, the method further comprises: the sending end acquiring, from the subscription network, the group information list corresponding to the receiving end that the authentication fails, according to the acquired group. The information list authenticates the receiving end.

The method according to any one of claims 1 to 4, wherein the sending end adds the receiving end of the authentication to the forwarding item corresponding to the multicast group to which the request is to be joined:

If the forwarding entry of the multicast group is not requested, the forwarding entry of the multicast group is created for the receiving end, and the receiving end that passes the authentication is added to the forwarding item.

If the forwarding entry of the multicast group that has been requested to join is added, the receiving end is added to the forwarding entry; the forwarding device adds the sending end to the group that it requests to join according to the request for joining the multicast group from the sending end. The forwarding entries corresponding to the broadcast group are:

If there is no forwarding entry of the multicast group to be joined, the forwarding entry of the multicast group is created for the sending end; if the forwarding entry of the multicast group that has been requested to join is added, the sending end is added to the forwarding In the item.

The method according to claim 1, wherein the forwarding device further adds the sending end to the forwarding item corresponding to the multicast group that it is requesting to join according to the joining multicast group request from the sending end, and the method further Includes:

The forwarding device requests the upstream forwarding device to join the multicast group joined by the receiving end.

If the upstream forwarding device does not have a forwarding entry of the multicast group that the receiving end requests to join, the upstream forwarding device creates a forwarding entry of the multicast group, and adds a downstream forwarding device to the forwarding entry;

If the forwarding device of the multicast group that the receiving end requests to join is already in the upstream forwarding device, the upstream forwarding device adds the downstream forwarding device to the existing forwarding entry.

The method according to claim 6, wherein the method further comprises: the upstream forwarding device receiving the multicast frame, and sending the multicast step by step according to the forwarding item corresponding to the multicast group to which the received multicast frame belongs frame.

The method according to claim 1, wherein after the sending end adds the receiving end of the authentication to the forwarding item corresponding to the multicast group to which the request is to be added, the method further includes:

The sending end updates or deletes the forwarding entry corresponding to the multicast group that the receiving end exits according to the receiving end of the multicast group report. If the forwarding item corresponding to the multicast group is deleted, the sending end sends the exit group to the forwarding device. Broadcast Group Report·

The forwarding device updates or deletes the forwarding entry corresponding to the multicast group that is logged out by the receiving end according to the received quit multicast group report. If the forwarding entry corresponding to the multicast group is deleted, the forwarding device forwards the packet to the upstream. The device sends an exit multicast group report.

The upstream forwarding device updates or deletes the forwarding entry corresponding to the multicast group exited by the receiving end according to the received exiting multicast group report.

A multicast system, the system comprising: a receiving end, a sending end, and a forwarding device, wherein

The sending end is configured to authenticate the receiving end that requests to join the multicast group according to the joining multicast group request from the receiving end, and add the receiving end that is authenticated to the forwarding item corresponding to the multicast group that the requesting party joins. And sending a join multicast group request to the forwarding device;

The system according to claim 9, wherein the system further comprises: an authentication server, configured to acquire authentication information of the receiving end from the sending end according to a request from a sending end, and perform the authentication information on the receiving end After the access authentication is passed, the group information list of the receiving end is obtained from the external subscription network; and the receiving end group information list is sent to the sending end;

The sending end is further configured to: request, according to an access request from the receiving end, access authentication to the receiving end to the authentication server; send the authentication information from the receiving end to the authentication server; receive and store the receiving from the authentication server a list of group information at the end;

The receiving end is further configured to request access to the sending end; provide authentication information to the sending end; and send a join multicast group request to the sending end.

The system according to claim 9, wherein the system further comprises: an upstream forwarding device of the forwarding device;

The forwarding device is further configured to request the upstream forwarding device to join the multicast group that the receiving end joins; the upstream forwarding device is configured to add the forwarding device to the request to join according to the request from the forwarding device The multicast group corresponds to the forwarding entry.

The system according to claim 11, wherein the receiving end is further configured to send an exit multicast group report to the sending end;

The sending end is further configured to: according to the exiting multicast group report of the receiving end, update or delete the forwarding item corresponding to the multicast group that the receiving end exits, if the forwarding item corresponding to the multicast group is deleted, The forwarding device sends an exit multicast group report;

The forwarding device is further configured to update or delete, according to the received exiting multicast group report, the forwarding entry corresponding to the multicast group that is deleted by the receiving end, and if the forwarding item corresponding to the multicast group is deleted, Sending an exit multicast group report to its upstream forwarding device;

The upstream forwarding device is further configured to update or delete the forwarding item corresponding to the multicast group that the receiving end exits according to the received exiting multicast group report.

The system according to any one of claims 9 to 12, wherein the transmitting end is: a wireless mesh Mesh network node having access capability;

The receiving end is: STA;

The forwarding device includes: a node of a Mesh network, a Mesh network node with access capability, a Mesh network node with an egress function, one or any combination of routers.

14. A multicast device, comprising:

a transceiver unit, configured to receive a request for joining a multicast group from the outside, and provide the request to the authentication unit; The authentication result provided by the element sends a request to join the multicast group to the forwarding device;

The authentication unit is configured to receive the multicast group request provided by the transceiver unit, authenticate the request, add the receiving end that is authenticated to the forwarding item corresponding to the multicast group to which the request is to be added, and provide the authentication result to the receiving and sending unit.

The device according to claim 14, wherein the device further comprises a storage unit, configured to store a list of group information from the transceiver unit, and provide the authentication unit; store the forwarding item from the authentication unit, and Provided to the transceiver unit;

The transceiver unit is further configured to: store the group information list obtained from the outside in the storage unit; and send the received multicast frame according to the forwarding item provided by the storage unit;

The authentication unit is further configured to send the forwarding item to which the receiving end is added to the storage unit.