WO2009009927A1

WO2009009927A1 - A method and system for implementing multicast service by point-to-point protocol over ethernet

Info

Publication number: WO2009009927A1
Application number: PCT/CN2007/002189
Authority: WO
Inventors: Wenli Cao
Original assignee: Zte Corporation
Priority date: 2007-07-18
Filing date: 2007-07-18
Publication date: 2009-01-22

Abstract

A method for implementing multicast service by point-to-point protocol over Ethernet includes the following steps: (1) both terminals of the PPPoE negotiating the multicast capability information through the discovery stage session, and then entering into the PPP session stage; (2) both terminals of the PPPoE forwarding the multicast data based on the negotiated multicast capability after the setup of the PPP session. Another method for implementing multicast service by point-to-point protocol over Ethernet includes that both terminals of the PPPoE forwarding the multicast protocol data in the form of PPPoE, and forwarding the multicast barrier forward data in the form of IPoE; or both terminals of the PPPoE forwarding the multicast protocol data and the multicast barrier forward data in the form of IPoE. It resolves the problem of the multicast flow copying largely of PPPoE.

Description

Method for implementing multicast service by point-to-point protocol on Ethernet

Technical field

The present invention relates to the field of network communication technologies, and in particular, to a method for implementing a multicast service by using a point-to-point protocol over Ethernet (PPPoE). Background technique

PPPoE is an Ethernet-based point-to-point protocol. The PPPoE session consists of two phases: the discovery phase and the PPP (Point-to-Point Protocol) session phase. The discovery phase is a stateless client/server mode. The purpose is to obtain the MAC address (Media Access Control) of the PPPoE terminator and establish a unique PPPoE session identifier. After the discovery phase is over, it enters the PPP session phase. The PPP session is mainly a negotiation process of three protocols: Link Control Protocol (LCP), authentication, and NCP (Network Control Protocol). The PPP protocol is a protocol at the data link layer that provides a standard way to transport data packets of multiple network layer protocols over a point-to-point link.

The basic idea of IP multicast is that the multicast source only sends one copy of the data, and one or more recipients can receive a copy of the same data. IP multicast technology enables efficient data transfer from point to point in IP networks. IGMP (Internet Group Management Protocol) is responsible for collecting and maintaining the membership of connected network groups. The protocol sends and receives general query messages, specific group query messages, host report messages, and leave messages to maintain various state information of the protocol. IPv6 uses MLD (Multicast Listener Discovery) instead of IGMP and performs similar functions.

As can be seen from the above, the multicast protocol does not provide user authentication support, and cannot effectively control multicast users or perform effective accounting for multicast users.

Most of the current broadband access methods are based on the PPPoE protocol. The PPPoE protocol requires a point-to-point relationship between the end and the end. It does not apply to the point-to-multipoint relationship required by the multicast. That is, the PPPoE protocol itself does not support multicast services. Due to the point-to-point nature of the PPPoE protocol, multicast replication is required for each PPPoE session. As a result, the PPPoE multicast stream is replicated in a Layer 2 environment, which greatly limits the development of multicast services. This has affected the development of new services based on multicast functions to a certain extent. Summary of the invention

The technical problem to be solved by the present invention is to provide a PPPoE method for implementing a multicast service. The two ends of the PPPoE can negotiate the multicast data forwarding mode. When the IPoE forwarding mode is supported at both ends, the PPPoE multicast stream can be copied. The development of multicast services is greatly limited.

To solve the above technical problem, the present invention provides a method for implementing a multicast service by using a point-to-point protocol PPPoE over Ethernet, including the following steps:

(1) Both ends of the PPPoE negotiate multicast performance information through the session in the discovery phase, including the multicast data forwarding mode, and then enter the PPP session phase of the point-to-point protocol;

(2) After the PPP session is established, the two ends of the PPPoE perform multicast data forwarding according to the negotiated multicast data forwarding mode.

The method of the present invention, wherein the step (1) is divided into the following steps:

(1.1) The PPPoE client first sends the broadcast packet actively. PPPoE actively discovers the PADI to find the PPPoE server.

(1.2) After receiving the PADI packet, the PPPoE server checks the service requested by the PPPoE client, and if it can provide the service requested by the host, responds to the PPPoE client to periodically provide a PADO packet by the PPPoE client;

(1.3) the PPPoE client selects a suitable server in the PPPoE server that responds to the PADO, and sends a PPPoE active discovery request PADR to notify the PPPoE server;

(1.4) after receiving the PADR packet, the PPPoE server confirms whether the service requested by the client is supported, and if so, starts to assign a unique session identifier to the user, starts the PPP state machine to prepare to start the PPP session, and Send a session confirmation packet PPPoE actively discovers the session confirmation PADS to the PPPoE client.

In the above steps, the two ends of the PPPoE complete the negotiation of the multicast performance information in the discovery phase by carrying the multicast performance information supported by the packets in the respective packets.

Further, in step (1.1), the PADI packet includes multicast performance information.

Further, in step (1.2), if the PPPoE server supports the multicast performance negotiation function, it includes the multicast performance information supported by the PADO packet, or only the multicast performance information of the client request it supports. If the PPPoE server does not support the multicast performance protocol The function of the quotient ignores the multicast performance information in the PADI packet.

Further, in step (1.3), if the PPPoE client supports the function of multicast performance negotiation, the multicast performance information in the PADO is checked. If the PADO has multicast performance information supported or requested by the PADO, The PADR packet contains the multicast performance requested by itself. If there is no multicast performance information supported or requested by PADO, or there is no multicast performance information in PADO, the PADR packet does not contain multicast performance information, or continues to be included. The requested multicast performance information; if the PPPoE client does not support the multicast performance negotiation function, the multicast performance information in the PADO is ignored.

Further, in step (1.4), if the PPPoE server supports the multicast performance requested by the client, the PADS packet includes the multicast performance requested by the PPPoE client; if the multicast requested by the client is not supported Performance, or does not support multicast performance negotiation, or the PAD packet does not contain multicast performance information. The PADS packet does not contain multicast performance information.

The method of the present invention, wherein, in step (2), after receiving the PADS, the PPPoE client starts a PPP state machine to prepare to start a PPP session if the PPPoE server allocates a session identifier; If the PPPoE client requests the multicast performance negotiation, the multicast performance information in the PADS is checked. If the PADS has the multicast performance information requested by itself, the multicast performance is forwarded when the multicast data is forwarded. If the PADS does not have the multicast performance information requested by itself, or the client does not request the negotiation of the multicast performance, the multicast performance information in the PADS is ignored. When multicast data is forwarded, the default multicast performance is used. PPPoE mode, forwarded.

The method of the present invention, wherein, in step (1), the method for negotiating multicast performance information by the two ends of the PPPoE through the discovery phase includes using the existing label TAG of the PPPoE to negotiate multicast performance information, where the PPPoE's existing tag TAG includes the service name Service-Name and the vendor-specific tag Vendor-Specific TAG. Alternatively, the PPPoE TAG is extended to support the negotiation of multicast performance information. If the PPPoE does not support the multicast performance TAG, it is ignored. The TAG.

The method of the present invention, wherein the PPPoE multicast forwarding mode is supported at both ends of the PPPoE, or the PPPoE multicast forwarding mode and the IPoE multicast forwarding mode are supported at the same time; according to the negotiation result, one of the following forwarding modes may be adopted. :

A. The PPPoE mode is adopted for the multicast protocol data, and the IPoE mode is adopted for the multicast bearer forwarding data. B. IPoE is adopted for multicast protocol data and multicast bearer forwarding data.

C. The PPPoE mode and the IPoE mode are used for the multicast protocol data, and the multicast bearer forwarding data is IPoE.

D. PPPoE is used for both multicast protocol data and multicast bearer forwarding data.

Another technical problem to be solved by the present invention is to provide a method for implementing multicast service by PPPoE, which can simultaneously solve the problem of massive multicast replication of PPPoE and the control and charging of IP multicast users.

For the above technical problem, the present invention also provides a method for implementing a multicast service in a point-to-point protocol PPPoE over Ethernet. The multicast data includes multicast protocol data and multicast bearer forwarding data. After the PPP session of the PPPoE session is established, Both ends of the PPPoE use the PPPoE mode to forward the multicast protocol data, and the multicast bearer forwards the data in the IPoE mode. In the multicast process, the multicast protocol data and the multicast bearer forwarding data need to be associated with the source address. Thereby implementing the multicast service.

In the method of the present invention, when the two ends of the PPPoE use the PPPoE mode to forward the multicast protocol data, the multicast protocol data is further forwarded by using the IPoE.

The method of the present invention, wherein the source address comprises an IP address and a MAC address.

Another technical problem to be solved by the present invention is to provide a method for implementing multicast service by using PPPoE, which can solve the problem of massive copying of multicast streams of PPPoE.

For the above technical problem, the present invention also provides a method for implementing a multicast service in a point-to-point protocol PPPoE over Ethernet. The multicast data includes multicast protocol data and multicast bearer forwarding data. After the PPP session of the PPPoE session is established, The multicast data is forwarded by the two ends of the PPPoE in the IPoE mode, and the multicast service is implemented.

Compared with the prior art, the method of the present invention can ensure that PPPoE supports multicast services exactly like IP multicast, can solve the problem of massive multicast replication of PPPoE, and can also solve the problem of control and charging of IP multicast users. It satisfies the requirements of network operators for multicast services, and is used to improve the uniformity of operation and management of multi-service networks and facilitate the development of multiple services. BRIEF abstract

1 is a schematic structural diagram of a network according to an embodiment of the present invention;

Figure 2 is a flow chart of an embodiment of the present invention; FIG. 3 is a schematic diagram of a signaling flow of a PPPoE session according to an embodiment of the present invention. Preferred embodiment of the invention

The invention is described in detail below with reference to the accompanying drawings and specific embodiments.

As shown in FIG. 1, in a schematic diagram of a network structure for implementing a multicast service on a PPPoE protocol according to an embodiment of the present invention, a PPPoE terminal 10 is connected to an access server 30 through an Ethernet switch 20, and is connected to a network side of the server 30. Connect to the Internet40. Between the PPPoE terminal 10 and the Ethernet switch 20, the link between the Ethernet switch 20 and the access server 30 is an Ethernet link.

The PPPoE terminal 10 has PPPoE function and multicast function. Ethernet switch 20 has a bridge forwarding function. The access server 30 has a PPPoE termination function and a multicast function.

As shown in FIG. 2, the process for implementing the multicast service on the PPPoE protocol according to the embodiment of the present invention includes:

Step 201: The two ends of the PPPoE negotiate multicast performance information through the session in the discovery phase, and then enter the PPP session phase.

The process of negotiating multicast performance information through the discovery phase session at both ends of the PPPoE includes the following steps:

Step Bl, the PPPoE client first sends the broadcast packet PADI to find the PPPoE server. Optionally, the PADI packet may include multicast performance information.

Step B2: After receiving the PADI packet, the PPPoE server checks the service requested by the client, and if it can provide the service requested by the host, responds to a PADO packet of the PPPoE client. If the PPPoE server supports the multicast performance negotiation function, optionally, it can include the multicast performance and other information it supports in the PADO package, or only the multicast performance and other information of the client request it supports. If the PPPoE server does not support the multicast performance negotiation function, the multicast performance information in the PADI packet is ignored.

In step B3, the PPPoE client selects a suitable server in the PPPoE server that responds to PADO, and sends a PADR to notify the PPPoE server. If the client supports the multicast performance negotiation function, check the multicast performance information in PADO. If PADO has its own The multicast performance information supported or requested includes the multicast performance requested by the PADR packet. If there is no multicast performance information supported or requested by PADO, or there is no multicast performance information in PADO, it is in the PADR package. Does not include multicast performance information, or continues to contain the requested multicast performance information; if the client does not support the multicast performance negotiation function, the multicast performance information in PADO is ignored;

Step B4: After receiving the PADR packet, the PPPoE server confirms whether the service requested by the client is supported. If supported, starts to assign a unique session identifier to the user, starts the PPP state machine to prepare to start the PPP session, and sends a session confirmation. Package PADS. If the server supports the multicast performance requested by the client, the PADS packet includes the multicast performance requested by the client. If the multicast performance requested by the client is not supported, or the multicast performance negotiation function is not supported, or the PADR packet is included. If the multicast performance information is not included, the multicast performance information is not included in the PADS packet.

Step B5: After the PPPoE client receives the PADS, if the PPPoE server allocates a session identifier, the PPP state machine is started to prepare to start the PPP session. If the client requests the multicast performance negotiation, check the multicast performance information in the PADS. If the PADS has the multicast performance information requested by itself, the multicast performance is negotiated when the multicast data is forwarded. Forwarding; if the PADS does not have the multicast performance information requested by itself, or if the client does not request the negotiation of multicast performance, the multicast performance information in the PADS is ignored, and the default multicast performance is used when forwarding the multicast data. , that is, PPPoE mode, for forwarding.

There are two methods for negotiating multicast performance information on the two ends of the PPPoE through the discovery phase: (1) Using PPPoE's existing TAG (tag) to negotiate multicast performance information. Such as: Service Name Service-Name, Vendor-specific label Vendor-Specific TAG.

(2) Extend the PPPoE TAG to support the negotiation of multicast performance information.

If the multicast performance is not supported on either end of the PPPoE, the TAG can be ignored.

The multicast performance information refers to the multicast data forwarding mode, and can also be said to be the encapsulation type used in multicast data forwarding. It is the forwarding mode used when multicast data is forwarded after the PPPoE session is established. The multicast data includes multicast protocol data and multicast bearer forwarding data, and the multicast protocol data includes IGMP and MLD protocol packets. Both the multicast protocol data and the multicast bearer forwarding data can use the following forwarding methods:

1 PPPoE mode: It means the way to use PPPoE sessions when multicast data is forwarded. Forward.

2 IPoE (IP over Ethernet, IP protocol carried over Ethernet) mode: It means that IPOE sessions are forwarded during multicast data forwarding, that is, multicast data originally carried in PPPoE sessions is now used. IPoE is directly forwarded and does not need to be encapsulated in PPPoE.

In addition, the multicast protocol data can also use the following forwarding methods:

PPPoE mode and IPoE mode: It means that the multicast protocol data is sent twice at the same time, one is sent by PPPoE, and the other is sent by IPoE.

When multicast data is forwarded, the encapsulation format of the multicast protocol data and the multicast bearer forwarding data can be arbitrarily combined. The description of the various combinations is as follows:

1) The multicast protocol data is forwarded by using the PPPoE method, and the multicast bearer forwarding data is forwarded by using the IPoE method;

In this case, the multicast protocol data is forwarded by using the PPPoE method. Therefore, the multicast protocol can be added to the multicast group to perform user-specific service admission processing, and the multicast user can be effectively controlled. Use the multicast protocol Query message and the 4 advertised message as the keepalive mechanism of the user-specific multicast group to detect the multicast groups that the user has joined and the duration of joining the multicast group. The user performs effective billing. Since the multicast bearer forwarding data is forwarded by using the IPoE method, multicast replication is not required for each PPPoE session, which solves the problem of massive multicast replication of PPPoE and control and accounting of IP multicast users.

The multicast protocol data is forwarded by the PPPoE mode. When the multicast bearer forwarding data is forwarded by the IPoE method, the multicast protocol data and the multicast bearer forwarding data need to be associated with the source address in the multicast process. The source address here can be IP. Address or MAC address.

2) The multicast protocol data is forwarded by using PPPoE mode and IPoE mode, and the multicast bearer forwarding data is forwarded by using IPoE mode;

In this case, the multicast protocol data that can be sent using the IPoE method can be connected.

The intermediate device between the PPPoE client and the network completes the Snooping/Proxy function of the multicast protocol, so that the existing multicast implementation of the intermediate device remains unchanged and is compatible with the existing device.

At this time, both ends of the PPPoE can receive the multicast protocol data in the PPPoE mode and the IPoE mode at the same time. Therefore, the two ends can check the multicast protocol of the two modes by matching the source address. The data is the same, and the multicast protocol data of the two modes and the multicast bearer forwarding data of the IPoE mode are associated. The source address here may be an IP address or a MAC address.

3) The multicast protocol data and the multicast bearer forwarding data are forwarded by using the PPPoE method. In this case, the existing PPPoE multicast implementation is the same as the existing PPPoE multicast implementation.

4) The multicast protocol data and the multicast bearer forwarding data are forwarded by using the IPoE method. In this case, the same as the existing IPoE multicast implementation, the efficient replication of PPPoE multicast data is realized.

5) Other combinations, this situation does not make much sense.

1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 quotient +-+-+-+-+-+-+- +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- + ° I TAG— TYPE I TAG—LENGTH I. +-+-+-+_+-+-+- -+- +-+-+-+-+-+-+-+_+-+-+-+-+- -+-+-+- +-+-+- +-+-+-+ I TAG-VALUE ... -

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- +-+-+-+ TAG—The TYPE field is a 16-bit value (network byte order) indicating the type of TAG.

The TAG_LENGTH field is 16 bits and is an unsigned value (network byte order) indicating the number of bytes of TAG_VALUE.

The description of the charged multicast performance TAG is as follows:

This TAG is used to negotiate the multicast forwarding mode information. The TAG_TYPE value is defined as 0x0111, and can also be defined as other values, as long as the type values are not conflicting. TAG— VALUE is 2 bytes long. The first byte indicates the multicast data type. Possible values are: Multicast protocol data (value is defined as 1), and multicast bearer forwarding data (value is defined as 2) (if Indicates the forwarding mode of each data request, and includes two TAGs in one message. The second byte indicates the multicast forwarding mode. The preferred values are: PPPoE mode (value is defined as 1), IPoE mode (value is defined as 2), PPPoE mode, and IPoE mode (value is defined as 3).

Multicast performance TAG is optional. Its default value is PPPoE. If this option is not negotiated, PPPoE is used to forward multicast data, which is compatible with existing PPPoE multicast implementations.

In this embodiment, the multicast performance negotiation result at both ends of the PPPoE is as follows: For the IPoE way.

Step 202: After the PPP session is established, the two ends of the PPPoE perform multicast data forwarding according to the negotiated multicast performance.

When multicast data is forwarded, the multicast data is forwarded using the negotiated multicast data forwarding performance. The other data is still forwarded using PPPoE.

According to the negotiation result in the foregoing step 202, the IGMP report message of the PPPoE client is sent to the Ethernet switch 20, and the Ethernet switch 20 sends the IGMP report message to the server. After receiving the request of the packet, the access server establishes a multicast distribution tree and then forwards the multicast data to the PPPoE client in IPoE mode. At the same time, the data of other PPPoEs is forwarded to the PPPoE client through PPPoE.

As shown in FIG. 3, a schematic diagram of a signaling flow of a PPPoE session according to an embodiment of the present invention includes the following steps:

Step 301: The PPPoE client first sends a broadcast packet PADI to find a PPPoE server, where the PADI packet includes multicast performance information.

Step 302: After receiving the PADI packet, the PPPoE server checks the service requested by the client, and if it can provide the service requested by the host, responds to the PPPoE client with a PADO packet, where the PADO packet includes multicast performance information.

Step 303: The PPPoE client selects a suitable server in the PPPoE server that responds to the PADO, and sends a PADR to notify the PPPoE server, where the PADR packet includes the multicast performance information.

Step 304: After receiving the PADR packet, the PPPoE server confirms whether the service requested by the client is supported. If it supports, the user is assigned a unique session identifier, and the multicast data forwarding mode is determined to be IPoE mode, and the PPP state machine is started. Prepare to start a PPP session and send a session confirmation packet PADS to the PPPoE client;

Step 305: After the discovery phase ends, the PPP state machine starts a PPP session. First, the LCP protocol is negotiated.

Step 306: After the LCP negotiation succeeds, the PPPoE client sends a message of the authentication request to the PPPoE server.

Step 307: The PPPoE server returns a PPPoE client authentication success or failure message. Step 308: After the authentication succeeds, the NCP negotiation is performed, and the NCP negotiation succeeds. The session was established successfully.

Step 309: After the PPP session is successfully established, the PPPoE client sends the IGMP report message to the access server according to the negotiation result.

Step 311: After receiving the request of the packet, the access server establishes a multicast distribution tree, and then forwards the multicast data to the PPPoE client by using IPoE.

Step 309: At the same time, the access server forwards the PPPoE data of the PPPoE to the PPPoE client through PPPoE.

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

Industrial applicability

The method for implementing the multicast service on the PPPoE protocol of the present invention can ensure that the PPPoE supports the multicast service exactly like the IP multicast, solves the problem of massive copying of the multicast stream of the PPPoE, and can also solve the control and calculation of the IP multicast user. The fee problem satisfies the requirements of the network operator for the multicast service, and is used to improve the uniformity of operation and management of the multi-service network and facilitate the development of multiple services.

Claims

Claim

A point-to-point protocol on an Ethernet PPPoE method for implementing a multicast service, which is characterized by the following steps:

2. The method of claim 1 wherein step (1) is divided into the following steps:

In the preceding step, the two ends of the PPPoE complete the negotiation of the multicast performance information in the discovery phase by carrying the multicast performance information supported by the packets in the respective packets.

3. The method according to claim 2, wherein in step (1.1), the PADI packet includes multicast performance information.

The method according to claim 2, wherein in step (1.2), if the PPPoE server supports the function of multicast performance negotiation, it includes the multicast performance information it supports in the PADO package, or only includes It supports multicast performance information requested by the client, if the PPPoE If the server does not support the multicast performance negotiation function, the multicast performance information in the PADI packet is ignored.

The method according to claim 2, wherein in step (1.3), if the PPPoE client supports the function of multicast performance negotiation, checking the multicast performance information in the PADO, if there is a PADO The multicast performance information supported or requested by the user includes the multicast performance requested by the PADR packet. If there is no multicast performance information supported or requested by PADO, or there is no multicast performance information in PADO, the PADR packet is included. The multicast performance information is not included, or the multicast performance information of the request is continued. If the PPPoE client does not support the multicast performance negotiation function, the multicast performance information in the PADO is ignored.

The method according to claim 2, wherein in step (1.4), if the PPPoE server supports multicast performance requested by the client, the PADS packet includes the multicast requested by the PPPoE client. Performance: If the multicast performance requested by the client is not supported, or the multicast performance negotiation function is not supported, or the PADR packet does not contain multicast performance information, the PADS packet does not contain multicast performance information.

The method according to claim 2, wherein in step (2), after receiving the PADS, the PPPoE client starts a PPP state machine to prepare to start if the PPPoE server allocates a session identifier. If the PPPoE client requests the multicast performance negotiation, the multicast performance information in the PADS is checked. If the PADS has the multicast performance information requested by itself, the multicast data is forwarded. The multicast performance is forwarded. If the PADS does not have the multicast performance information requested by itself, or the client does not request the negotiation of the multicast performance, the multicast performance information in the PADS is ignored. When the multicast data is forwarded, the default is used. The multicast performance, that is, the PPPoE mode, is forwarded.

The method according to claim 1, wherein in the step (1), the method for negotiating multicast performance information by the two ends of the PPPoE through the discovery phase includes using the existing label TAG of the PPPoE to negotiate the multicast performance. The information of the PPPoE existing label TAG includes a service name Service-Name and a vendor-specific label Vendor-Specific TAG. Alternatively, the PPPoE TAG is extended to support the negotiation of the multicast performance information, if the PPPoE does not support the group at either end. If the performance TAG is broadcast, the TAG is ignored.

The method of claim 1, wherein the PPPoE multicast forwarding mode is supported at both ends of the PPPoE, or the PPPoE multicast forwarding mode and the IPoE multicast forwarding mode are supported at the same time; According to the negotiation result, one of the following forwarding methods can be used:

A. The PPPoE mode is adopted for the multicast protocol data, and the IPoE mode is adopted for the multicast bearer forwarding data.

B. The IPoE mode is adopted for multicast protocol data and multicast bearer forwarding data.

C. The PPPoE mode and the IPoE mode are used for the multicast protocol data, and the IPoE mode is used for the multicast bearer forwarding data.

D. PPPoE is adopted for multicast protocol data and multicast bearer forwarding data.

A method for implementing a multicast service in a point-to-point protocol (PPPoE) on an Ethernet network. The multicast data includes the multicast protocol data and the multicast bearer forwarding data. The PPPoE session is established after the PPP session of the PPPoE session is established. The multicast protocol data is forwarded by using the PPPoE mode, and the multicast bearer forwarding data is forwarded by using the IPoE mode. In the multicast process, the multicast protocol data and the multicast bearer forwarding data need to be associated with the source address, thereby implementing The multicast service.

The method of claim 10, wherein, when the two ends of the PPPoE use the PPPoE mode to forward the multicast protocol data, the multicast protocol data is further forwarded by using the IPoE.

12. The method according to claim 10, wherein the source address comprises an IP address and a MAC address.

A method for implementing a multicast service in a point-to-point protocol (PPPoE) on an Ethernet network. The multicast data includes the multicast protocol data and the multicast bearer forwarding data. The PPPoE session is established after the PPP session of the PPPoE session is established. The multicast protocol data and the multicast bearer forwarding data are forwarded in an IPoE manner, thereby implementing the multicast service.