Method and device for negotiating point-to-point protocol over Ethernet (PPPoE) and related product

Abstract

The invention discloses a PPPoE (Point-to-Point Protocol over Ethernet) negotiation method, a PPPoE negotiation device and a related product, belongs to the technical field of communication, and solves the problem of low message forwarding performance of PE (Point-to-Point Protocol over Ethernet) equipment. According to the specific scheme, an access device receives a first dialing message from a first terminal, the first dialing message is used for requesting to execute a PPPoE negotiation process, and the first terminal is one of a plurality of terminals connected with the access device; the access device generates a first and sixth version Internet protocol IPv6 message according to the first dialing message, the first IPv6 message carries a first identifier and a second identifier, the first identifier indicates an Internet protocol IP address of the access device, the second identifier indicates an IP address of the BRAS, and the first identifier is used for the BRAS to feed back a response message corresponding to the first dialing message; and the access device sends the first IPv6 message to a provider edge (PE) device. The embodiment of the invention is used in a PPPoE (Point to Point Protocol over Ethernet) dialing scene.

Description

Technical Field

[0001] The present application belongs to the field of communication technology, and specifically relates to a PPPoE negotiation method, device and related products. Background Art

[0002] At present, in an Ethernet virtual private network (EVPN) virtual private LAN service (VPLS) network, when a user terminal performs PPP over Ethernet (PPPoE) dial-up, the user terminal can send a dial-up message for requesting to execute a PPPoE negotiation process to a provider edge (PE) device. The dial-up message includes a media access control (MAC) address of the user terminal and a MAC address of a broadband remote access server (BRAS). Thus, the PE device can learn the MAC address of the user terminal while forwarding the dial-up message to the BRAS according to the MAC address of the BRAS, so as to facilitate forwarding a response message corresponding to the dial-up message.

[0003] However, since there may be a situation where there are many user terminals connected to the PE device, this may cause the PE device to learn more MAC addresses of user terminals, thus causing excessive learning pressure on the PE device, which may affect the message forwarding performance of the PE device. Summary of the invention

[0004] The purpose of the embodiments of the present application is to provide a PPPoE negotiation method, apparatus and related products, which can solve the problem of low message forwarding performance of PE devices.

[0005] In a first aspect, an embodiment of the present application provides a PPPoE negotiation method, the method comprising: an access device receives a first dial-up message from a first terminal, the first dial-up message is used to request execution of a PPPoE negotiation process, the first terminal is one of multiple terminals connected to the access device; the access device generates a first Internet Protocol Version 6 (Internet Protocol Version 6, IPv6) message based on the first dial-up message, the first IPv6 message carries a first identifier and a second identifier, the first identifier indicates an Internet Protocol (Internet Protocol, IP) address of the access device, the second identifier indicates an IP address of a BRAS, the first identifier is used by the BRAS to feed back a response message corresponding to the first dial-up message; the access device sends a first IPv6 message to a PE device.

[0006] The embodiment of the present application provides a PPPoE negotiation method. Since the access device is connected to multiple terminals, and when the access device receives a first dial-up message from any one of the multiple terminals, the access device can generate a first IPv6 message according to the first dial-up message, and the first IPv6 message carries a first identifier indicating the IP address of the access device and a second identifier indicating the IP address of the BRAS, so that the PE device can learn the IP address of the access device while forwarding the first IPv6 message to the BRAS according to the IP address of the BRAS, so as to forward the response message corresponding to the first dial-up message based on the first identifier. In other words, even if the number of the above-mentioned multiple terminals is large, the PE device does not need to learn the MAC address of each terminal in the multiple terminals connected to the access device, but only needs to learn the IP address of the access device. Therefore, the number of addresses that the PE device needs to learn can be reduced, thereby reducing the learning pressure of the PE device, and thus improving the message forwarding performance of the PE device.

[0007] In combination with the first aspect and the above-mentioned possible implementation methods, in another possible implementation method, after the above-mentioned access device receives the first dial-up message from the first terminal, the method also includes: the access device carries a service type identifier in the first dial-up message, and the service type identifier indicates the service type of the service corresponding to the first dial-up message, and the service type identifier is used by the BRAS to decapsulate the first IPv6 message.

[0008] In combination with the first aspect and the above possible implementations, in another possible implementation, the above first dial-up message also carries the first MAC address and the first session identifier of the access device. After the above access device sends the first IPv6 message to the PE device, the method further includes: the access device receives a second IPv6 message from the PE device, the second IPv6 message carries a third identifier, the third identifier indicates the IP address of the access device, and the third identifier is determined based on the first MAC address and the first session identifier; the access device decapsulates the second IPv6 message to obtain a first response message, the first response message is a response message corresponding to the first dial-up message; the access device establishes a PPPoE session based on the first response message.

[0009] In combination with the first aspect and the above-mentioned possible implementation methods, in another possible implementation method, the above-mentioned second IPv6 message also carries a service type identifier; the above-mentioned access device decapsulates the second IPv6 message, including: when the service type identifier matches the preset type identifier, the access device decapsulates the second IPv6 message.

[0010] In a second aspect, an embodiment of the present application provides a PPPoE negotiation method, the method comprising: a BRAS receives a first IPv6 message from a PE device, the first IPv6 message carries a first identifier and a second identifier, the first identifier indicates an IP address of an access device, and the second identifier indicates an IP address of the BRAS; the BRAS decapsulates the first IPv6 message to obtain a first dial-up message, the first dial-up message is used to request execution of a PPPoE negotiation process; the BRAS sends a response message corresponding to the first dial-up message to the PE device based on the first identifier.

[0011] The embodiment of the present application provides a PPPoE negotiation method. Since an access device is connected to multiple terminals, and when the access device receives a first dial-up message from any one of the multiple terminals, the access device can generate a first IPv6 message based on the first dial-up message. The first IPv6 message carries a first identifier indicating the IP address of the access device and a second identifier indicating the IP address of the BRAS. In this way, the PE device can learn the IP address of the access device while forwarding the first IPv6 message to the BRAS based on the IP address of the BRAS, so as to forward a response message corresponding to the first dial-up message based on the first identifier. That is to say, even if the number of the above-mentioned multiple terminals is large, the PE device does not need to learn the MAC address of each terminal in the multiple terminals connected to the access device, but only needs to learn the IP address of the access device. Therefore, the number of addresses that the PE device needs to learn can be reduced, thereby reducing the learning pressure of the PE device. In this way, the message forwarding performance of the PE device can be improved.

[0012] In combination with the second aspect and the above-mentioned possible implementation methods, in another possible implementation method, the above-mentioned first IPv6 message also carries a service type identifier; the above-mentioned BRAS decapsulates the first IPv6 message, including: when the service type identifier matches the preset identifier, the BRAS decapsulates the first IPv6 message.

[0013] In combination with the second aspect and the above-mentioned possible implementation methods, in another possible implementation method, the above-mentioned BRAS sends a response message corresponding to the first dial-up message to the PE device based on the first identifier, including: the BRAS sends a first response message to the PE device according to a pre-stored first flow table; the first flow table includes a first identifier, the first response message is a response message corresponding to the first dial-up message, and the first response message is used to establish a PPPoE session with the access device.

[0014] In combination with the second aspect and the above-mentioned possible implementation methods, in another possible implementation method, before the above-mentioned BRAS sends a first response message to the PE device according to the pre-stored first flow table, the method also includes: the BRAS receives a third IPv6 message sent by the access device, and the third IPv6 message carries the first MAC address, the first session identifier and the first identifier of the access device; the BRAS stores the correspondence between the first MAC address, the first identifier and the first session identifier in the first flow table.

[0015] In combination with the second aspect and the above-mentioned possible implementation methods, in another possible implementation method, the above-mentioned first dial-up message also carries the first MAC address and the first session identifier of the access device; the above-mentioned BRAS sends a first response message to the PE device according to the pre-stored first flow table, including: the BRAS determines the first identifier corresponding to the first MAC address and the first session identifier in the first flow table as the third identifier, and the third identifier indicates the IP address of the access device; the BRAS generates a second IPv6 message according to the first response message, and the second IPv6 message carries the third identifier; the BRAS sends the second IPv6 message to the PE device.

[0016] In combination with the second aspect and the above-mentioned possible implementation methods, in another possible implementation method, after the above-mentioned BRAS determines the first identifier corresponding to the first MAC address and the first session identifier in the first flow table as the third identifier, the method also includes: the BRAS carries a service type identifier in the first response message, and the service type identifier indicates the service type of the service corresponding to the first response message, and the service type identifier is used by the access device to decapsulate the second IPv6 message.

[0017] In a third aspect, an embodiment of the present application provides a PPPoE negotiation device, which is a first PPPoE negotiation device, and the first PPPoE negotiation device includes: a receiving module, a processing module, and a sending module. Among them, the receiving module is used to receive a first dial-up message from a first terminal, and the first dial-up message is used to request the execution of a PPPoE negotiation process. The first terminal is one of the multiple terminals connected to the first PPPoE negotiation device. The processing module is used to generate a first IPv6 message according to the first dial-up message received by the receiving module. The first IPv6 message carries a first identifier and a second identifier. The first identifier indicates the IP address of the first PPPoE negotiation device, and the second identifier indicates the IP address of the second PPPoE negotiation device. The first identifier is used for the second PPPoE negotiation device to feedback a response message corresponding to the first dial-up message. The sending module is used to send the first IPv6 message generated by the processing module to the PE device.

[0018] In combination with the third aspect and the above-mentioned possible implementation methods, in another possible implementation method, the above-mentioned processing module is also used to carry a service type identifier in the first dial-up message after the receiving module receives the first dial-up message from the first terminal. The service type identifier indicates the service type of the service corresponding to the first dial-up message, and the service type identifier is used by the second PPPoE negotiation device to decapsulate the first IPv6 message.

[0019] In combination with the third aspect and the above possible implementation, in another possible implementation, the above first dial-up message also carries the first MAC address and the first session identifier of the first PPPoE negotiation device. After the above sending module sends the first IPv6 message to the PE device, the above receiving module is also used to receive the second IPv6 message from the PE device, the second IPv6 message carries a third identifier, the third identifier indicates the IP address of the first PPPoE negotiation device, and the third identifier is determined based on the first MAC address and the first session identifier. The above processing module is also used to decapsulate the second IPv6 message received by the receiving module to obtain a first response message, the first response message is a response message corresponding to the first dial-up message, and a PPPoE session is established based on the first response message.

[0020] In combination with the third aspect and the possible implementations, in another possible implementation, the second IPv6 message further carries a service type identifier. The processing module is specifically configured to decapsulate the second IPv6 message when the service type identifier matches the preset type identifier.

[0021] In a fourth aspect, an embodiment of the present application provides a PPPoE negotiation device, which is a second PPPoE negotiation device, and the second PPPoE negotiation device includes: a receiving module, a processing module, and a sending module. Among them, the receiving module is used to receive a first IPv6 message from a PE device, and the first IPv6 message carries a first identifier and a second identifier. The first identifier indicates the IP address of the first PPPoE negotiation device, and the second identifier indicates the IP address of the second PPPoE negotiation device. The processing module is used to decapsulate the first IPv6 message received by the receiving module to obtain a first dial-up message, and the first dial-up message is used to request the execution of the PPPoE negotiation process. The sending module is used to send a response message corresponding to the first dial-up message processed by the processing module to the PE device based on the first identifier.

[0022] In combination with the fourth aspect and the above possible implementations, in another possible implementation, the above first IPv6 message also carries a service type identifier. The above processing module is specifically configured to decapsulate the first IPv6 message when the service type identifier matches the preset identifier.

[0023] In combination with the fourth aspect and the above-mentioned possible implementation methods, in another possible implementation method, the above-mentioned sending module is specifically used to send a first response message to the PE device according to the first flow table pre-stored by the processing module; the first flow table includes a first identifier, the first response message is a response message corresponding to the first dial-up message, and the first response message is used by the first PPPoE negotiation device to establish a PPPoE session.

[0024] In combination with the fourth aspect and the above possible implementations, in another possible implementation, the above receiving module is further used to receive a third IPv6 message sent by the first PPPoE negotiation device before the sending module sends the first response message to the PE device according to the pre-stored first flow table, wherein the third IPv6 message carries the first MAC address, the first session identifier and the first identifier of the first PPPoE negotiation device. The above processing module is specifically used to store the correspondence between the first MAC address, the first identifier and the first session identifier in the first flow table.

[0025] In combination with the fourth aspect and the above possible implementations, in another possible implementation, the above first dial-up message also carries the first MAC address and the first session identifier of the access device. The above processing module is specifically used to determine the first identifier corresponding to the first MAC address and the first session identifier in the first flow table as a third identifier, and the third identifier indicates the IP address of the first PPPoE negotiation device; and generate a second IPv6 message according to the first response message, and the second IPv6 message carries the third identifier. The above sending module is also used to send the second IPv6 message generated by the processing module to the PE device.

[0026] In combination with the fourth aspect and the above-mentioned possible implementation methods, in another possible implementation method, the above-mentioned processing module is also used to carry a service type identifier in the first response message after determining the first identifier corresponding to the first MAC address and the first session identifier in the first flow table as the third identifier. The service type identifier indicates the service type of the service corresponding to the first response message, and the service type identifier is used by the first PPPoE negotiation device to decapsulate the second IPv6 message.

[0027] In a fifth aspect, an embodiment of the present application provides a PPPoE negotiation system, which includes a first PPPoE negotiation device, a PE device, and a second PPPoE negotiation device; the first PPPoE negotiation device executes the PPPoE negotiation method as described in the first aspect and its possible implementation method; the second PPPoE negotiation device executes the PPPoE negotiation method as described in the second aspect and its possible implementation method.

[0028] In a sixth aspect, an embodiment of the present application provides an access device, which includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the PPPoE negotiation method as described in the first aspect and the possible implementation method of the first aspect thereof is implemented.

[0029] In a seventh aspect, an embodiment of the present application provides a BRAS, which includes a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, it implements the PPPoE negotiation method as described in the second aspect and the possible implementation method of the second aspect.

[0030] In an eighth aspect, an embodiment of the present application provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the PPPoE negotiation method as described in the first aspect and the possible implementation manner of the first aspect is implemented, or the PPPoE negotiation method as described in the second aspect and the possible implementation manner of the second aspect is implemented. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] Figure 1 It is a networking logical topology diagram of the EVPNVPLS or EVPNVPWS solution in the related technology;

[0032] Figure 2 This is one of the flow charts of the PPPoE negotiation method provided in the embodiment of the present application;

[0033] Figure 3 This is the second flow chart of the PPPoE negotiation method provided in the embodiment of the present application;

[0034] Figure 4 It is one of the networking logical topology diagrams of the PPPoE negotiation method provided in the embodiment of the present application;

[0035] Figure 5 This is the third flow chart of the PPPoE negotiation method provided in the embodiment of the present application;

[0036] Figure 6 This is the fourth flow chart of the PPPoE negotiation method provided in the embodiment of the present application;

[0037] Figure 7 This is the second networking logical topology diagram of the PPPoE negotiation method provided in the embodiment of the present application;

[0038] Figure 8 It is a structural diagram of a first PPPoE negotiation device provided in an embodiment of the present application;

[0039] Fig. 9 It is a structural diagram of a second PPPoE negotiation device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0040] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0041] The terms "first", "second", etc. in the specification and claims of this application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way can be interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first", "second", etc. are generally of the same type, and the number of objects is not limited. For example, the first object can be one or more.

[0042] In addition, the term "and / or" in this article is only a description of the association relationship between the associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0043] The terms "at least one (item)", "at least one of" and the like in the specification and claims of the present application refer to any one, any two or a combination of more than two of the objects included therein. For example, at least one (item) of a, b, and c can be represented by: "a", "b", "c", "a and b", "a and c", "b and c" and "a, b and c", where a, b, and c can be single or multiple. Similarly, "at least two (items)" refers to two or more, and its meaning is similar to that of "at least one (item)".

[0044] The implementation of the embodiments of the present application will be described in detail below with reference to the accompanying drawings.

[0045] At present, there are two main technical solutions for carrying home broadband services in metropolitan area networks: EVPN VPLS and EVPN Virtual Private Wire Service (VPWS). VPLS mainly carries PPPOE messages through the metropolitan area network layer 2, and VPWS mainly carries PPPOE messages in a point-to-point manner. In general, for home broadband services, metropolitan area networks are built on the basis of Layer 2 Virtual Private Network (L2VPN) to carry home broadband services. Figure 1 The network logical topology diagram of the EVPNVPLS or EVPN VPWS solution is shown as follows: Figure 1 As shown, the main bearer solution currently used is EVPNVPLS or EVPNVPWS over Internet Protocol Version 6 Segment Routing (SRv6), using SRv6 as the underlying tunnel.

[0046] In the EVPNVPLS networking solution, all PE devices (i.e., access PE devices (including PE device 1 and PE device 2) and service PE devices (including PE device 3 and PE device 4)) will learn the MAC addresses of the optical line termination (OLT) devices (i.e., OLT device 1, OLT device 2, and OLT device 3), and will learn the MAC addresses of all user terminals connected to the OLT devices, i.e., the MAC addresses of the user terminals connected to the home gateway (Home Gateway, HG) 1, the user terminals connected to HG2, and the user terminals connected to HG3. In addition, the BRAS in the metropolitan area network also needs to learn the MAC addresses of all user terminals in the metropolitan area network, so that the user terminal can initiate a PPPoE dial-up process to the BRAS (i.e., BRAS1 and BRAS2) through the OLT device, access PE device, P device, and service PE device, and after the PPPoE dial-up process is successfully performed, the user terminal can access the broadband service server 163 through the core router (Core Router, CR), so that the broadband service server 163 provides broadband service for the user terminal. In summary, all of the above-mentioned PE devices and BRAS will face the MAC address learning of millions of user terminals, which will cause excessive pressure on PE devices and BRAS to learn MAC addresses.

[0047] In addition, the traditional EVPNVPLS networking solution has the following shortcomings:

[0048] 1) A virtual route reflector (VRR) needs to be configured between the access PE device (i.e., PE device 1 and PE device 2) and the P device, and between the P device and the service PE device (i.e., PE device 3 and PE device 4), respectively, so that the messages between the access PE device and the P device, and the messages between the P device and the service PE device can be forwarded through the VRR. However, each VRR also needs to learn millions or tens of millions of MAC addresses for route reflection, which will cause a large pressure on the MAC route learning of the network device; 2) The access PE device (i.e., PE device 1 and PE device 2) and the service PE device (i.e., PE device 3 and PE device 4) form a large Layer 2 network (i.e., L2VPN network), which is prone to loops, thereby causing network storms and network security issues; 3) A route reflector (RR) needs to be configured on the access PE device, so that the messages between the OLT device (i.e., OLT device 1, OLT device 2, and OLT device 3) and the P device can be forwarded through the RR. However, in order to ensure the stability of the network and the normal operation of the equipment, the route reflector (RR) Reflector (RR) needs to be configured with complex MAC filtering rules, otherwise the access PE will also face MAC performance pressure, causing network collapse.

[0049] It is understandable that in the EVPN VPLS network, it is necessary to solve the route reflection pressure of millions of MAC routes on RR and the MAC capacity pressure of all the above PE devices.

[0050] In the EVPN VPWS networking solution, VPWS is deployed on access PE devices (i.e., PE device 1 and PE device 2) with OLT devices (i.e., OLT device 1, OLT device 2, and OLT device 3) as units. The bearer network does not perceive the user MAC, and the VRR only needs to reflect the EVPN connection route.

[0051] However, the EVPNVPWS networking solution may have the following disadvantages:

[0052] 1) Every time an OLT device is added, the VLAN needs to be re-planned end-to-end, and the VPWS between the access PE devices (i.e., PE device 1 and PE device 2) and the service PE devices (i.e., PE device 3 and PE device 4) needs to be re-planned, which makes the deployment complicated. 2) As the number of users increases, the amount of business that needs to be configured with VPWS is large, and the operation is relatively complex, which is not conducive to the rapid opening of services. 3) VLAN conflicts on the service PE devices require re-VLAN planning or isolation through physical interfaces on the service PE devices. 4) The failure of the attachment circuit (AC) affects the port linkage on the service PE device, which in turn affects the normal home broadband service on the access PE device. 5) VPWS only supports 1-to-1 or 1-to-2 backup solutions, that is, each BRAS can only back up one or two OLT devices, and the BRAS utilization rate is low.

[0053] In order to solve the above technical problems, an embodiment of the present application provides a PPPoE negotiation method. Figure 2 A flowchart of a PPPoE negotiation method provided in an embodiment of the present application. Figure 2 As shown, the PPPoE negotiation method may include the following steps 101 to 106.

[0054] Step 101: An access device receives a first dial-up message from a first terminal.

[0055] In some embodiments of the present application, the above-mentioned access device may include any one of the following: a router, a gateway, a switch, and an optical network unit (Optical Network Unit, ONU) device.

[0056] In the embodiment of the present application, the first terminal is one of the multiple terminals connected to the access device.

[0057] In some embodiments of the present application, the above-mentioned multiple terminals can be connected to the access device wirelessly or by wire. The wireless connection may include any of the following: Wireless-Fidelity (Wi-Fi) connection, Bluetooth connection, etc., and the wired connection may include any of the following: serial cable, optical fiber cable, Category 5 cable (CAT5) cable, etc. Of course, the above-mentioned multiple terminals can also be connected to the access device in other forms, which are not limited in the embodiments of the present application.

[0058] In the embodiment of the present application, the first dial-up message is used to request execution of the PPPoE negotiation process.

[0059] In some embodiments of the present application, the first dial-up message is a PPPoE protocol message, and the PPPoE protocol message may specifically be a PPPoE Active Discovery Initiation (PADI) broadcast message.

[0060] In some embodiments of the present application, the first dial message may carry first service information, where the first service information indicates the service that the first terminal wants to obtain, and the service provided by the first terminal is negotiated with the BRAS through the first service information.

[0061] In some embodiments of the present application, when the first terminal needs to perform home broadband services through an access device, the first terminal can send a first dial-up message to the access device through the above-mentioned wireless connection or wired connection, so that the access device can receive the first dial-up message from the first terminal.

[0062] In some embodiments of the present application, after receiving the first dial-up message, the access device may also add the MAC address of the access device and the MAC address of the BRAS in the first dial-up message, so that the BRAS can feed back a response message corresponding to the first dial-up message (for example, the first response message in the following embodiments).

[0063] Step 102: The access device generates a first IPv6 message according to the first dial-up message.

[0064] In an embodiment of the present application, the first IPv6 message carries a first identifier and a second identifier, the first identifier indicates the Internet Protocol IP address of the access device, the second identifier indicates the IP address of the BRAS, and the first identifier is used by the BRAS to feedback a response message corresponding to the first dial-up message.

[0065] In some embodiments of the present application, the above-mentioned first identifier can specifically be a service segment identifier (Segment Identifier, SID) of an access device, and the SID of the access device is used to determine the IP address of the access device, so as to determine the next hop device of the first dial-up message according to the IP address of the access device.

[0066] In some embodiments of the present application, the second identifier may specifically be a service SID of the BRAS.

[0067] In some embodiments of the present application, the number of the second identifiers may be at least one, and correspondingly, the number of the IP addresses of the BRAS may be at least one. Wherein, when the number of the second identifiers is at least two, one of the at least two second identifiers indicates the IP address of the primary BRAS, and the other second identifiers indicate the IP address of the standby BRAS. It can be understood that when the number of the second identifiers is at least two, the number of BRAS is also at least two.

[0068] Exemplarily, assuming that the number of second identifiers can be two, such as node Peer SID1 and node PeerSID2, the Peer SID1 can be specifically the service SID of the primary BRAS, the Peer SID1 indicates the IP address of the primary BRAS, and the Peer SID2 can be specifically the service SID of the backup BRAS, the Peer SID2 indicates the IP address of the backup BRAS.

[0069] In some embodiments of the present application, the access device may encapsulate the first identifier and the second identifier on the first dial-up message to obtain a first IPv6 message.

[0070] In some embodiments of the present application, the access device may perform IPv6 encapsulation on the first dial-up message to encapsulate an IPv6 message header in the outer layer of the first dial-up message, wherein the IPv6 message header includes the first identifier and the second identifier. It can be understood that since the IPv6 message header includes the first identifier, the IPv6 message header can indicate that the next hop device is a BRAS.

[0071] In some embodiments of the present application, after the access device encapsulates the first identifier and the second identifier on the first dial-up message to obtain the first IPv6 message, the access device may also configure a PPPoE flow table on the access device, wherein the PPPoE flow table includes the first identifier and the second identifier, and the PPPoE flow table is used to subsequently send other messages to the BRAS, such as other messages in the PPPoE discovery phase, such as a PPPoE Active Discovery Request (PADR), or messages in the PPPoE session phase.

[0072] Of course, the access device can also encapsulate other identifiers in the first dial-up message to instruct the BRAS to perform other operations. Figure 2 ,like Figure 3 As shown, after the above step 101, the PPPoE negotiation method provided in the embodiment of the present application may further include the following step 201.

[0073] Step 201: The access device carries a service type identifier in a first dial-up message.

[0074] It should be noted that the present application embodiment does not limit the execution order of the above steps 102 and 201. In one example, step 102 may be executed first, and then step 201; in another example, step 201 may be executed first, and then step 102; in another example, step 201 may be executed while step 102 is executed. Figure 3 In the figure, step 102 is executed first and then step 201 is executed for illustration.

[0075] In the embodiment of the present application, the above-mentioned service type identifier indicates the service type of the service corresponding to the first dial-up message, and the service type identifier is used by the BRAS to decapsulate the first IPv6 message.

[0076] It can be understood that, since the service type of the service corresponding to the first dial-up message is the PPPoE dial-up Internet access service type, the above service type identifier can indicate the PPPoE dial-up Internet access service type.

[0077] In some embodiments of the present application, the above service type identifier may specifically be: End.PPPoE opcode.

[0078] In a possible implementation of the present application, the access device may first encapsulate the first identifier and the second identifier on the first dial-up message, and then encapsulate the service type identifier on the first dial-up message to obtain the first IPv6 message.

[0079] In this implementation, illustratively, the access device may first encapsulate an IPv6 message header on the first dial-up message, where the IPv6 message header includes a first identifier and a second identifier, and then add a service type identifier to a function Function field in the first identifier to obtain the first dial-up message.

[0080] In another possible implementation of the present application, the access device may first encapsulate the service type identifier on the first dial-up message, and then encapsulate the first identifier and the second identifier on the first dial-up message to obtain the first IPv6 message.

[0081] In this implementation, illustratively, the access device may first encapsulate an IPv6 message header on the first dial-up message, the IPv6 message header including a service type identifier, and then add the first identifier and the second identifier to the IPv6 message header to obtain a first IPv6 message.

[0082] In another possible implementation of the present application, the access device may encapsulate the first identifier and the second identifier on the first dial-up message while encapsulating the service type identifier on the first dial-up message to obtain the first IPv6 message.

[0083] In this implementation, illustratively, the access device may first encapsulate an IPv6 message header on the first dial-up message, where the IPv6 message header includes a first identifier, a second identifier, and a service type identifier, to obtain a first IPv6 message.

[0084] It can be seen that since the access device can also carry the service type identifier in the first dial-up message, for example, carry the service type identifier in the IPv6 message header of the first dial-up message, when the second identifier is inaccurate due to interference during the transmission of the first IPv6 message, the BRAS can also determine whether to decapsulate the first IPv6 message based on whether the service type identifier meets a certain condition (for example, whether the service type identifier matches the preset type identifier), instead of decapsulating the first IPv6 message based solely on the second identifier. Therefore, the probability that the BRAS fails to decapsulate the first IPv6 message due to interference can be reduced, thereby reducing the probability of failure of the access device to execute the PPPoE negotiation process. In this way, the success rate of the access device to execute the PPPoE negotiation process can be improved.

[0085] Step 103: The access device sends a first IPv6 message to the PE device.

[0086] It can be understood that the access device can use the PPPoE over IPv6 technology to carry the first dial-up message, so as to send the first dial-up message to the BRAS through the PE device.

[0087] In some embodiments of the present application, the access device may send a first IPv6 message to the PE device through the aggregation device, so that the aggregation device can forward the first IPv6 message to the PE device. The aggregation device may be an OLT device. Of course, the aggregation device may also be other devices, which is not limited in the embodiments of the present application.

[0088] In some embodiments of the present application, the above-mentioned PE device may include at least one of the following: an access PE device and a service PE device, wherein the access PE device is a PE device connected to a user terminal, and the service PE device is a PE device connected to a service network element in the network, wherein the access PE device is used to forward messages between the user terminal and the network (e.g., a provider (Provider, P) device), and the number of the access PE devices may be at least one; the service PE device is used to forward messages between the network (e.g., a P device) and a service network element (e.g., a BRAS); the P device is used to forward messages between the access PE device and the service PE device, and the number of the P devices may be at least one.

[0089] Among them, when the PE device includes an access PE device and a service PE device, after the access PE device receives the first IPv6 message, the access PE device can forward the first IPv6 message to the service PE device through the P device, so that the service PE device can send the first IPv6 message to the BRAS.

[0090] For example, Figure 4 As shown, the number of access PE devices is two, such as PE device 1 and PE device 2, the number of P devices is two, such as P device 1 and P device 2, the number of service PE devices is two, such as PE device 3 and PE device 4, the number of BRAS can be two, such as BRAS1 and BRAS2, the PE device 1 and PE device 2 are used to forward messages between the ONU device and the P device 1 and P device 2, the P device 1 and P device 2 are used to forward messages between the PE device 1 and PE device 2 and the PE device 3 and PE device 4, the PE device 3 and PE device 4 are used to forward messages between the P device 1 and P device 2 and the BRAS 1 and BRAS2 Messages between RAS2, so that the access device (such as ONU device) can send a first IPv6 message to at least one of PE device 1 and PE device 2 through the aggregation device (such as OLT device), so that at least one of PE device 1 and PE device 2 can forward the first IPv6 message to at least one of P device 1 and P device 2, so that at least one of P device 1 and P device 2 can forward the first IPv6 message to at least one of PE device 3 and PE device 4, so that at least one of PE device 3 and PE device 4 can send the first IPv6 message to at least one of BRAS1 and BRAS2.

[0091] It can be understood that since the present application can also deploy access devices (such as ONU devices), the ONU devices, PE devices (i.e., access PE devices and service PE devices) and P devices can form a three-layer network, i.e., a three-layer virtual private network (Layer 3 Virtual Private Network, L3VPN), so that the access PE device can adopt PPPoE over IPv6 over L3VPN technology to forward the received first IPv6 message by addressing through IP and routing. That is, the access PE device can forward the first IPv6 message to the BRAS according to the IP address of the BRAS indicated by the second identifier, and only needs to learn the IP address of the access device, without learning the MAC address of each terminal connected to the access device, so as to forward the response message corresponding to the first IPv6 message to the access device. This reduces the pressure on the PE device to learn the MAC address.

[0092] In this way, compared with the EVPN VPLS bearer solution in the related art, the access PE device and the service PE device only need to learn the IP addresses of a small number of access devices connected to the OLT device, without learning the MAC address of each terminal connected to the access device, and can forward the response message to the access device, so that the pressure of learning MAC addresses of the access PE device and the service PE device can be reduced. In addition, on the one hand, the VRR configured between the access PE device P device, the P device and the service PE device only needs to learn the IP addresses of a small number of access devices connected to the OLT device, without learning the MAC address of each terminal connected to the access device, and can forward the response message to the access device, so that the pressure of learning MAC addresses of network devices can be reduced. On the other hand, the ONU device, the PE device (i.e., the access PE device and the service PE device) and the P device form a three-layer network, not a large two-layer network, so the problem of network storm caused by easy loops in the large two-layer network can be avoided, thereby improving the security of the network. On the other hand, the RR configured in the access PE device only needs to learn the IP addresses of a small number of access devices connected to the OLT device, without having to learn the MAC address of each terminal connected to the access device, and can forward the response message to the access device. Therefore, the performance pressure of the access PE device to learn the MAC address can be reduced, avoiding network crashes.

[0093] Compared with the EVPN VPWS bearer solution in the related art, on the one hand, the ONU device, PE device (i.e., access PE device and service PE device) and P device form a three-layer network instead of a large two-layer network, so it can avoid the problem of end-to-end re-planning of VLAN for newly added OLT devices or newly added access devices in the large two-layer network, but can directly add the routing information of the newly added OLT device or newly added access device to the routing forwarding table stored in the access PE device, service PE device and P device, so as to realize the forwarding of the message of the newly added OLT device or newly added access device, so as to reduce the complexity of deployment and facilitate the rapid opening of services. On the other hand, the ONU device, PE device (i.e., access PE device and service PE device) and P device form a three-layer network instead of a large two-layer network, so there will be no VLAN conflict in the access PE device and the service PE device, so there is no need to re-do VLAN planning or port linkage on the access PE device and the service PE device, thereby avoiding the situation where the access PE device cannot transmit the message of the broadband service. On the other hand, ONU devices, PE devices (i.e., access PE devices and service PE devices) and P devices form a three-layer network rather than a large two-layer network. Therefore, VPWS will not only support 1-to-1 or 1-to-2 backup solutions, that is, each BRAS can back up multiple OLT devices, thereby improving the utilization rate of BRAS.

[0094] In one possible implementation, the access PE device can search the IPv6 routing forwarding table, which includes at least one second correspondence, where the second correspondence is a correspondence between an IPv6 prefix and a next hop information, so as to determine an IPv6 prefix that is the same as the IPv6 prefix of the first IPv6 message from at least one IPv6 prefix in the at least one second correspondence, and determine the device indicated by the next hop information corresponding to the IPv6 prefix as the next hop device (i.e., the P device), so that the access PE device can forward the first IPv6 message to the P device.

[0095] In a possible implementation, the P device may search an IPv6 routing forwarding table, which includes the at least one second correspondence relationship, to determine an IPv6 prefix that is the same as the IPv6 prefix of the first IPv6 message from at least one IPv6 prefix in the at least one second correspondence relationship, and determine a device indicated by a next hop information corresponding to the IPv6 prefix as the next hop device (i.e., the service PE device), so that the P device can forward the first IPv6 message to the service PE device.

[0096] In one possible implementation, the service PE device can search the IPv6 routing forwarding table, which includes the above-mentioned at least one second correspondence, to determine an IPv6 prefix that is the same as the IPv6 prefix of the first IPv6 message from at least one IPv6 prefix in the at least one second correspondence, and determine the device indicated by the next hop information corresponding to the IPv6 prefix as the next hop device (i.e., BRAS), so that the service PE can forward the first IPv6 message to the BRAS.

[0097] In a possible implementation, an IPv6 routing table may be configured in the access PE device, the P device and the service PE device, so that the access PE device, the P device and the service PE device may forward the first IPv6 message according to their configured IPv6 routing tables.

[0098] Among them, the service PE device can first configure the SRv6 table, so that the BRAS can send the IPv6 routing information of the BRAS to the service PE device through the routing protocol, so that the service PE device can store the IPv6 routing information of the BRAS in the SRv6 table, and convert the SRv6 table into an Ethernet virtual private network (Ethernet Virtual Private Network, EVPN) routing table in the form of IPv6 prefix routing to obtain the above-mentioned IPv6 routing forwarding table. Therefore, the service PE device can publish the IPv6 routing forwarding table to the access PE device through the Interior Gateway Protocol (IGP) protocol, so that the access PE device can add the IPv6 routing forwarding table to the IPv6 routing table of the EVPN example to obtain the IPv6 routing forwarding table. Then, the access PE device can exchange routing information with the access device, add the routing information of the access device to the IPv6 routing forwarding table, and forward the IPv6 routing forwarding table to the service PE device, so that the service PE device can update the IPv6 routing forwarding table previously obtained by the service PE device, and forward the IPv6 routing forwarding table sent by the access PE device to the BRAS.

[0099] It can be understood that, for the access PE device, it only needs to learn the IP address of the access device to forward the response message corresponding to the first dial-up message, without learning the MAC address of each terminal in the multiple terminals connected to the access device, thus reducing the pressure on the access PE device to learn the MAC address. For the service PE device, it only needs to learn the IP addresses of the access PE device and the BRAS to forward the response message corresponding to the first dial-up message, without learning the MAC address of each terminal in the multiple terminals connected to the access device, thus reducing the pressure on the service PE device to learn the MAC address. For the BRAS, it only needs to learn the IP addresses of the access PE device, the service PE device and the access device to forward the response message corresponding to the first dial-up message, without learning the MAC address of each terminal in the multiple terminals connected to the access device, thus reducing the pressure on the BRAS to learn the MAC address.

[0100] In this way, compared with the EVPNVPLS bearer solution in the related art, the access PE device and the service PE device only need to learn the IP addresses of the access devices with a small number of OLT devices connected, without learning the MAC address of each terminal connected to the access device, and can forward the response message to the access device, so that the pressure of learning MAC addresses of the access PE device and the service PE device can be reduced. In addition, on the one hand, the VRR configured between the access PE device P device, the P device and the service PE device only needs to learn the IP addresses of the access devices with a small number of OLT devices connected, without learning the MAC address of each terminal connected to the access device, and can forward the response message to the access device, so that the pressure of learning MAC addresses of network devices can be reduced. On the other hand, the ONU device, the PE device (i.e., the access PE device and the service PE device) and the P device form a three-layer network, not a large two-layer network, so the problem of network storm caused by easy loops in the large two-layer network can be avoided, thereby improving the security of the network. On the other hand, the RR configured in the access PE device only needs to learn the IP addresses of a small number of access devices connected to the OLT device, without having to learn the MAC address of each terminal connected to the access device, and can forward the response message to the access device. Therefore, the performance pressure of the access PE device to learn the MAC address can be reduced, avoiding network crashes.

[0101] Compared with the EVPN VPWS bearer solution in the related art, on the one hand, the ONU device, PE device (i.e., access PE device and service PE device) and P device form a three-layer network instead of a large two-layer network. Therefore, the problem of the need to re-plan the VLAN end-to-end for the newly added OLT device or the newly added access device in the large two-layer network can be avoided. Instead, the routing information of the newly added OLT device or the newly added access device can be directly added to the routing forwarding table stored in the access PE device, the service PE device and the P device, so that the message forwarding of the newly added OLT device and the newly added access device can be realized. Therefore, the complexity of deployment can be reduced and the service can be quickly opened. On the other hand, the ONU device, PE device (i.e., access PE device and service PE device) and P device form a three-layer network instead of a large two-layer network. Therefore, there will be no VLAN conflict in the access PE device and the service PE device, so there is no need to re-plan the VLAN or link the ports on the access PE device and the service PE device, thereby avoiding the situation where the access PE device cannot transmit the message of the broadband service. On the other hand, ONU devices, PE devices (i.e., access PE devices and service PE devices) and P devices form a three-layer network rather than a large two-layer network. Therefore, VPWS will not only support 1-to-1 or 1-to-2 backup solutions, that is, each BRAS can back up multiple OLT devices, thereby improving the utilization rate of BRAS.

[0102] Step 104: The BRAS receives a first IPv6 message from the PE device.

[0103] In the embodiment of the present application, the first IPv6 message carries a first identifier and a second identifier, the first identifier indicates the IP address of the access device, and the second identifier indicates the IP address of the BRAS.

[0104] Step 105: The BRAS decapsulates the first IPv6 message to obtain a first dial-up message.

[0105] In the embodiment of the present application, the first dial-up message is used to request execution of the PPPoE negotiation process.

[0106] In some embodiments of the present application, the BRAS may perform IPv6 decapsulation on the first IPv6 message to remove the IPv6 message header of the first IPv6 message to obtain the first dial-up message.

[0107] In some embodiments of the present application, the BRAS may determine whether to decapsulate the first IPv6 message based on the IP address of the access device and the IP address of the BRAS, or the BRAS may determine whether to decapsulate the first IPv6 message based on the service type identifier and the preset identifier.

[0108] In one possible implementation, the BRAS may first detect the IPv6 message header of the first IPv6 message to obtain the second identifier, so that the BRAS may determine the IP address indicated by the second identifier, and decapsulate the first IPv6 message when the IP address indicated by the second identifier is the same as the IP address of the BRAS.

[0109] In a possible implementation, the first IPv6 message also carries a service type identifier. Figure 2 ,like Figure 5 As shown, the above step 105 may specifically include the following step 105a.

[0110] Step 105a: When the service type identifier matches the preset identifier, the BRAS decapsulates the first IPv6 message to obtain a first dial-up message.

[0111] It should be noted that the above-mentioned “business type identifier matches the preset identifier” can be understood as being the same.

[0112] In the embodiment of the present application, if the service type identifier matches the preset identifier, it can be considered that the destination of the first IPv6 message is the BRAS, and therefore, the BRAS can directly decapsulate the first IPv6 message.

[0113] It can be seen that since the first IPv6 message is also encapsulated with a service type identifier, when the second identifier is inaccurate due to interference during the transmission of the first IPv6 message, the BRAS can also determine whether to decapsulate the first IPv6 message based on whether the service type identifier matches the preset identifier, rather than decapsulating the first IPv6 message only based on the second identifier. Therefore, the probability that the BRAS fails to decapsulate the first IPv6 message due to interference can be reduced, thereby reducing the probability of failure of the access device to execute the PPPoE negotiation process. In this way, the success rate of the access device to execute the PPPoE negotiation process can be improved.

[0114] Step 106: The BRAS sends a response message corresponding to the first dial message to the PE device based on the first identifier.

[0115] In some embodiments of the present application, the BRAS may first obtain the IP address of the access device, and then send a response message corresponding to the first dial message to the PE device based on the IP address of the access device.

[0116] In a possible implementation, the BRAS may pre-store the IP address of the access device, so that the BRAS can obtain the IP address of the access device from the BRAS.

[0117] In some embodiments of the present application, the BRAS can encapsulate an IPv6 message header in the outer layer of the response message of the first dial-up message based on the IP address of the access device, and send the encapsulated IPv6 message to the PE device, so that the access device can establish a PPPoE session based on the encapsulated IPv6 message.

[0118] An embodiment of the present application provides a PPPoE negotiation method, where an access device can receive a first dial-up message from a first terminal among multiple terminals connected to the access device, where the first dial-up message is used to request execution of a PPPoE negotiation process, and generate a first IPv6 message based on the first dial-up message, where the first IPv6 message carries a first identifier (the first identifier indicates an IP address of the access device) and a second identifier (the second identifier indicates an IP address of a BRAS), so that the access device can send the first IPv6 message to a PE device, so that the PE device can forward the first IPv6 message to the BRAS, so that the BRAS can receive the first IPv6 message from the PE device, and decapsulate the first IPv6 message to obtain the first dial-up message, and then the BRAS can send a response message corresponding to the first dial-up message to the PE based on the first identifier, so that the PE device can forward the response message to the access device. Since the access device is connected to multiple terminals, and when the access device receives a first dial-up message from any of the multiple terminals, the access device can generate a first IPv6 message according to the first dial-up message, and the first IPv6 message carries a first identifier indicating the IP address of the access device and a second identifier indicating the IP address of the BRAS, so that the PE device can learn the IP address of the access device while forwarding the first IPv6 message to the BRAS according to the IP address of the BRAS, so as to forward the response message corresponding to the first dial-up message based on the first identifier. In other words, even if the number of the above-mentioned multiple terminals is large, the PE device does not need to learn the MAC address of each terminal in the multiple terminals connected to the access device, but only needs to learn the IP address of the access device. Therefore, the number of addresses that the PE device needs to learn can be reduced, thereby reducing the learning pressure of the PE device, and thus improving the message forwarding performance of the PE device.

[0119] In this way, compared with the EVPN VPLS bearer solution in the related art, the access PE device and the service PE device only need to learn the IP addresses of a small number of access devices connected to the OLT device, without learning the MAC address of each terminal connected to the access device, and can forward the response message to the access device, so that the pressure of learning MAC addresses of the access PE device and the service PE device can be reduced. In addition, on the one hand, the VRR configured between the access PE device P device, the P device and the service PE device only needs to learn the IP addresses of a small number of access devices connected to the OLT device, without learning the MAC address of each terminal connected to the access device, and can forward the response message to the access device, so that the pressure of learning MAC addresses of network devices can be reduced. On the other hand, the ONU device, the PE device (i.e., the access PE device and the service PE device) and the P device form a three-layer network, not a large two-layer network, so the problem of network storm caused by easy loops in the large two-layer network can be avoided, thereby improving the security of the network. On the other hand, the RR configured in the access PE device only needs to learn the IP addresses of a small number of access devices connected to the OLT device, without having to learn the MAC address of each terminal connected to the access device, and can forward the response message to the access device. Therefore, the performance pressure of the access PE device to learn the MAC address can be reduced, avoiding network crashes.

[0120] Compared with the EVPN VPWS bearer solution in the related art, on the one hand, the ONU device, PE device (i.e., access PE device and service PE device) and P device form a three-layer network instead of a large two-layer network, so it can avoid the problem of end-to-end re-planning of VLAN for newly added OLT devices or newly added access devices in the large two-layer network, but can directly add the routing information of the newly added OLT device or newly added access device to the routing forwarding table stored in the access PE device, service PE device and P device, so as to realize the forwarding of the message of the newly added OLT device or newly added access device, so as to reduce the complexity of deployment and facilitate the rapid opening of services. On the other hand, the ONU device, PE device (i.e., access PE device and service PE device) and P device form a three-layer network instead of a large two-layer network, so there will be no VLAN conflict in the access PE device and the service PE device, so there is no need to re-do VLAN planning or port linkage on the access PE device and the service PE device, thereby avoiding the situation where the access PE device cannot transmit the message of the broadband service. On the other hand, ONU devices, PE devices (i.e., access PE devices and service PE devices) and P devices form a three-layer network rather than a large two-layer network. Therefore, VPWS will not only support 1-to-1 or 1-to-2 backup solutions, that is, each BRAS can back up multiple OLT devices, thereby improving the utilization rate of BRAS.

[0121] Furthermore, since the ONU device, the access PE device, the service PE device and the P device form a three-layer network, the access device can use the PPPoE over IPv6 technology to forward the first IPv6 message through the three-layer network, rather than forwarding the first IPv6 message through the L2VPN network accessed by EVPN VPLS or EVPN VPWS as in the related art. This can avoid the security problems existing in the L2VPN network while avoiding the deficiencies existing in the above-mentioned EVPN VPLS or EVPNVPWS, thereby improving the security and stability of the network.

[0122] The following is an example to illustrate a specific solution in which the BRAS sends a response message corresponding to the first dial message to the PE device.

[0123] In some embodiments of the present application, Figure 2 ,like Figure 6 As shown, the above step 106 can be specifically implemented through the following step 106a.

[0124] Step 106a: The BRAS sends a first response message to the PE device according to the pre-stored first flow table.

[0125] In the embodiment of the present application, the first flow table includes a first identifier.

[0126] In the embodiment of the present application, the first flow table is used by the BRAS to send a response message corresponding to the first dial message to the PE device.

[0127] In a possible implementation, the first flow table is used to determine the IP address of the access device. It should be noted that the format of the first flow table is not limited in this embodiment of the present application, and those skilled in the art may select it at their own discretion.

[0128] In the embodiment of the present application, the above-mentioned first response message is a response message corresponding to the first dial-up message, and the first response message is used for the access device to establish a PPPoE session.

[0129] In some embodiments of the present application, the first response message may specifically be a PPPoE Active Discovery Offer (PADO) message.

[0130] In some embodiments of the present application, the BRAS may first generate a first response message, and then send the first response message to the PE device according to the first flow table.

[0131] In a possible implementation, the BRAS can determine the service that the first terminal wants to obtain based on the first service information carried in the first dial message, and compare the service that the first terminal wants to obtain with the service that the BRAS can provide, so as to determine the service that the first terminal wants to obtain and that the BRAS can provide. Thus, the BRAS can generate a first response message, which carries the second service information, and the second service information indicates the service that the first terminal wants to obtain and that the BRAS can provide.

[0132] As can be seen, since the first flow table is pre-stored in the BRAS, and the first flow table includes the first identifier, before sending the first response message, the BRAS can accurately determine the destination address of the first response message (i.e., the IP address of the access device indicated by the first identifier) ​​from the first flow table according to the first identifier carried in the first IPv6 message, and accurately send the first response message to the access device through the PE device, so that the access device can receive the first response message. Therefore, it can be avoided that the access device cannot establish a PPPoE session due to the access device being unable to receive the first response message, and thus the success rate of the access device in establishing a PPPoE session can be improved.

[0133] In some embodiments of the present application, before the above step 106a, the PPPoE negotiation method provided by the embodiment of the present application may further include the following steps 301 to 303.

[0134] Step 301: The access device sends a third IPv6 message to the BRAS.

[0135] In the embodiment of the present application, the third IPv6 message is generated based on the second dial-up message sent by the first terminal to the access device.

[0136] The third IPv6 message may be the first IPv6 message or other IPv6 messages. The second dial-up message may be the first dial-up message or other dial-up messages, and the second dial-up message may carry the first MAC address and the first session identifier of the access device.

[0137] In some embodiments of the present application, when the first terminal needs to perform home broadband services through an access device, the first terminal can send a second dial-up message to the access device through the above-mentioned wireless connection or wired connection, so that the access device can receive the second dial-up message from the first terminal and generate a third IPv6 message based on the second dial-up message.

[0138] It should be noted that, for the description of the access device generating the third IPv6 message according to the second dial-up message, reference may be made to the specific description of the access device generating the first IPv6 message according to the first dial-up message, and the embodiments of the present application will not be repeated here.

[0139] Step 302: The BRAS receives a third IPv6 message sent by the access device.

[0140] In the embodiment of the present application, the third IPv6 message carries the first MAC address, the first session identifier and the first identifier of the access device.

[0141] It can be understood that since the second dial-up message carries the first MAC address and the first session identifier of the access device, and the third IPv6 message can carry the first identifier, the third IPv6 message as a whole carries the first MAC address, the first session identifier and the first identifier of the access device.

[0142] In some embodiments of the present application, the third IPv6 message may be the first IPv6 message, or other IPv6 messages sent by the first terminal to the BRAS through the access device.

[0143] Step 303: The BRAS stores the correspondence between the first MAC address, the first identifier, and the first session identifier in the first flow table.

[0144] Thus, it can be known that, since the BRAS can add the correspondence between the first MAC address, the first session identifier and the first identifier of the access device in the pre-stored first flow table according to the third IPv6 message before sending the first response message to the PE device. In this way, after the BRAS generates the first response message, it can accurately determine the identifier (i.e., the third identifier) ​​of the destination address corresponding to the first response message based on the correspondence between the first MAC address, the first session identifier and the first identifier. Therefore, it can be ensured that the BRAS can send the first response message to the access device, thereby avoiding the failure of the access device to establish a PPPoE session due to the inability of the access device to receive the first response message, and thus, the success rate of the access device to establish a PPPoE session can be improved.

[0145] In some embodiments of the present application, the first dial-up message also carries the first MAC address and the first session identifier of the access device. The above step 106a can be implemented by the following steps 106a1 to 106a3, and after the above step 106a3, the PPPoE negotiation method provided in the embodiment of the present application can also include the following steps 401 to 401.

[0146] Step 106a1: The BRAS determines the first identifier corresponding to the first MAC address and the first session identifier in the first flow table as the third identifier.

[0147] In this embodiment of the present application, the third identifier indicates the IP address of the access device.

[0148] In some embodiments of the present application, the third identifier may specifically be a service SID of the access device.

[0149] In some embodiments of the present application, the BRAS may first obtain the first MAC address and the first session identifier from the first dial-up message, and then determine the first identifier corresponding to the first MAC address and the first session identifier based on the corresponding relationship stored in the first process, and determine the first identifier as the third identifier.

[0150] Step 106a2: The BRAS generates a second IPv6 message according to the first response message.

[0151] In the embodiment of the present application, the second IPv6 message carries a third identifier.

[0152] In some embodiments of the present application, the BRAS may perform IPv6 encapsulation on the first response message to encapsulate an IPv6 message header in the outer layer of the first response message, wherein the IPv6 message header includes the third identifier. It can be understood that since the IPv6 message header includes the third identifier, the IPv6 message header can indicate that the next hop device is an access device.

[0153] In some embodiments of the present application, the BRAS may also encapsulate a third identifier in the first response message, and encapsulate a fourth identifier in the first response message to obtain a second IPv6 message. The fourth identifier indicates the IP address of the BRAS, and the fourth identifier is used for the access device to feed back a response message corresponding to the first response message, such as other messages in the PPPoE discovery phase, such as a PPPoE Active Discovery Request (PADR), or a message in the PPPoE session phase.

[0154] In some embodiments of the present application, after the above step 106a1, the PPPoE negotiation method provided by the embodiment of the present application may further include the following step 501.

[0155] Step 501: The BRAS carries a service type identifier in a first response message.

[0156] It should be noted that the present application embodiment does not limit the execution order of the above steps 106a2 and 501. In one example, step 106a2 may be executed first, and then step 501; in another example, step 501 may be executed first, and then step 106a2; in another example, step 501 may be executed while step 106a2 is executed.

[0157] In an embodiment of the present application, the above-mentioned service type identifier indicates the service type of the service corresponding to the first response message, and the service type identifier is used by the access device to decapsulate the second IPv6 message.

[0158] It can be understood that since the service corresponding to the first response message is the same as the service corresponding to the first dial-up message, the service type identifier encapsulated by the BRAS in the first response message is also the same as the service type identifier encapsulated by the access device in the first dial-up message.

[0159] It should be noted that, for the description of BRAS encapsulating the service type identifier in the first response message, reference can be made to the specific description of the access device encapsulating the service type identifier in the first dial-up message in the above embodiment, which will not be repeated in the embodiment of the present application.

[0160] It can be seen that since the BRAS can also encapsulate the service type identifier used by the access device to decapsulate the second IPv6 message in the first response message, when the second identifier is inaccurate due to interference during the transmission of the first IPv6 message, the access device can also determine whether to decapsulate the first IPv6 message based on whether a certain condition is met (for example, whether the service type identifier matches the preset type identifier), instead of decapsulating the second IPv6 message only based on the third identifier. Therefore, the probability of the access device failing to decapsulate the second IPv6 message due to interference can be reduced, thereby reducing the probability of the access device failing to establish a PPPoE session. In this way, the success rate of the access device in establishing a PPPoE session can be improved.

[0161] In a possible implementation manner, the fourth identifier may specifically be a service SID of the BRAS.

[0162] Step 106a3: The BRAS sends a second IPv6 message to the PE device.

[0163] Step 401: An access device receives a second IPv6 message from a PE device.

[0164] In an embodiment of the present application, the above-mentioned first dial-up message also includes a first MAC address and a first session identifier of the access device, and the above-mentioned second IPv6 message carries a third identifier, which indicates the IP address of the access device, and the third identifier is determined based on the first MAC address and the first session identifier.

[0165] Step 402: The access device decapsulates the second IPv6 message to obtain a first response message.

[0166] In the embodiment of the present application, the above-mentioned first response message is a response message corresponding to the first dialing message.

[0167] In some embodiments of the present application, the access device may perform IPv6 decapsulation on the second IPv6 message to remove the IPv6 message header of the second IPv6 message to obtain the first response message.

[0168] In some embodiments of the present application, the second IPv6 message is further encapsulated with a service type identifier. The step 402 can be specifically implemented by the following step 402a.

[0169] Step 402a: When the service type identifier matches the preset type identifier, the access device decapsulates the second IPv6 message to obtain a first response message.

[0170] It should be noted that the above-mentioned “business type identifier matches the preset identifier” can be understood as being the same.

[0171] In the embodiment of the present application, if the service type identifier matches the preset identifier, it can be considered that the destination of the second IPv6 message is the access device, and therefore, the access device can directly decapsulate the second IPv6 message.

[0172] It can be seen that since the second IPv6 message is also encapsulated with a service type identifier, when the second identifier is inaccurate due to interference during the transmission of the first IPv6 message, the access device can also determine whether to decapsulate the second IPv6 message based on whether the service type identifier matches the preset identifier, rather than decapsulating the second IPv6 message only based on the third identifier. Therefore, the probability of the access device failing to decapsulate the second IPv6 message due to interference can be reduced, thereby reducing the probability of the access device failing to establish a PPPoE session. In this way, the success rate of the access device in establishing a PPPoE session can be improved.

[0173] Step 403: The access device establishes a PPPoE session based on the first response message.

[0174] It should be noted that for the instructions on establishing a PPPoE session for an access device, reference may be made to the specific description in the relevant technology, and the embodiments of the present application will not be elaborated here.

[0175] It can be seen that since the BRAS can accurately determine the third identifier based on the first corresponding relationship and encapsulate the third identifier in the first response message, after the BRAS sends the second IPv6 message to the PE device, the PE device can accurately forward the second IPv6 message to the access device. This can avoid the failure of the access device to establish a PPPoE session due to the access device being unable to receive the first response message. In this way, the success rate of the access device in establishing a PPPoE session can be improved.

[0176] The following is a specific example to illustrate the complete process of the PPPoE negotiation method provided in the embodiment of the present application.

[0177] Figure 7 The following is a diagram showing the logical topology of the networking of devices in the PPPoE negotiation method provided in the embodiment of the present application. Figure 7As shown, the access device is an ONU device, and the PE device includes an access PE device and a service PE device. The access PE device includes PE device 1 and PE device 2, and the service PE device includes PE device 3 and PE device 4. Thus, the ONU device can receive a first dial-up message, such as PPPoE protocol message 1, from one of the multiple connected terminals (i.e., the first terminal mentioned above), and add a D-MAC address (i.e., D-MAC=FFFFFF) and an S-MAC address (i.e., S-MAC=AAAAA) to the PPPoE protocol message 1, wherein the D-MAC address is the MAC address of the BRAS, and the S-MAC address is the MAC address of the ONU device, and perform IPv6 encapsulation on the PPPoE protocol message 1, and encapsulate an IPv6 message header in the outer layer of the PPPoE protocol message 1, wherein the IPv6 message header includes a first identifier and a second identifier, wherein the first identifier is DA=the service SID of the BRAS, and the second identifier is SA=the broadband service SID of the ONU device, and a service type identifier is added to the Function field in SA to obtain IPv6 message 1 (i.e., the first IPv6 message). Thus, the ONU device can send the IPv6 message 1 to at least one of the PE devices 1 and PE devices 2 through at least one of the OLT devices 1 and the OLT device 2, so that at least one of the PE devices 1 and the PE devices 2 can search the IPv6 routing table and find the information of the next-hop device (that is, the information of the P device), so that at least one of the PE devices 1 and the PE devices 2 can forward the IPv6 message 1 to the P device, so that the P device can search the IPv6 routing table and find the information of the next-hop device (that is, the information of at least one of the PE devices 3 and the PE devices 4), and forward the IPv6 message to at least one of the PE devices 3 and the PE devices 4, so that at least one of the PE devices 3 and the PE devices 4 can search the IPv6 routing table and find the information of the next-hop device (that is, the information of the BRAS), and forward the IPv6 message 1 to the BRAS.

[0178] In this way, when the BRAS receives the IPv6 message 1, if the BRAS determines that the service type identifier matches the preset identifier, the IPv6 decapsulation of the IPv6 message 1 can be performed to remove the IPv6 message header of the IPv6 message 1, and the PPPoE protocol message 1 is obtained. The session identifier, S-MAC and SA in the PPPoE protocol message are learned, and a return flow table (i.e., the first flow table in the above embodiment) is established. The return flow table includes the corresponding relationship between the session identifier, S-MAC and SA, and, according to the PPPoE protocol message 1, a PPPoE protocol message 2 is generated. In this way, the BRAS can add the D-MAC address (i.e., D-MAC=AAAAAA) and the S-MAC address (i.e., S-MAC=FFFFFF) in the PPPoE protocol message 2. At this time, the D-MAC address is the MAC address of the ONU device, and the S-MAC address is the MAC address of the BRAS, and the PPPoE over IPv6 configuration, according to the session identifier and D-MAC (i.e., the MAC address of the ONU device), search DA (i.e., the broadband service SID of the ONU device) from the return flow table, and encapsulate the IPv6 message header in the outer layer of the PPPoE protocol message 2, the IPv6 message header includes a third identifier and a fourth identifier, the third identifier is DA=the broadband service SID of the ONU device, and the fourth identifier is SA=the service SID of the BRAS, obtain IPv6 message 2, and forward the IPv6 message 2 to at least one of the OLT device 1 and the OLT device 2 through the above-mentioned PE device 3, PE device 4, P device, PE device 1 and PE device 2, so that at least one of the OLT device 1 and the OLT device 2 can forward the IPv6 message 2 to the ONU device, so that the ONU device can establish a PPPoE session based on the IPv6 message 2.

[0179] The above mainly introduces the solution provided by the embodiment of the present application from the perspective of the interaction between the access device and the BRAS. It can be understood that in order to implement the above functions, the access device or BRAS includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should easily realize that, in combination with the algorithm steps of each example described in the embodiments disclosed in this document, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of this application.

[0180] In the embodiment of the present application, the access device or BRAS can be divided into functional modules according to the above method example. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above integrated module can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation.

[0181] In the case of dividing each functional module into corresponding functional modules, Figure 8 A possible schematic diagram of the composition of the PPPoE negotiation device involved in the above embodiment is shown, and the PPPoE negotiation device is a first PPPoE negotiation device. Figure 8 As shown, the first PPPoE negotiation device 40 may include: a receiving module 41, a processing module 42 and a sending module 43. The receiving module 41 is used to receive a first dial-up message from a first terminal, and the first dial-up message is used to request the execution of a PPPoE negotiation process. The first terminal is one of multiple terminals connected to the first PPPoE negotiation device. The processing module 42 is used to generate a first IPv6 message according to the first dial-up message received by the receiving module 41. The first IPv6 message carries a first identifier and a second identifier. The first identifier indicates the IP address of the access device, and the second identifier indicates the IP address of the BRAS. The first identifier is used for the second PPPoE negotiation device to feed back a response message corresponding to the first dial-up message. The sending module 43 is used to send the first IPv6 message generated by the processing module 42 to the PE device.

[0182] In an embodiment of the present application, the above-mentioned processing module 42 is also used to carry a service type identifier in the first dial-up message after the receiving module 41 receives the first dial-up message from the first terminal. The service type identifier indicates the service type of the service corresponding to the first dial-up message, and the service type identifier is used by the second PPPoE negotiation device to decapsulate the first IPv6 message.

[0183] In the embodiment of the present application, the first dial-up message also carries the first MAC address and the first session identifier of the first PPPoE negotiation device. After the sending module 43 sends the first IPv6 message to the PE device, the receiving module 41 is also used to receive the second IPv6 message from the PE device, and the second IPv6 message is encapsulated with a third identifier, and the third identifier indicates the IP address of the first PPPoE negotiation device, and the third identifier is determined based on the first MAC address and the first session identifier. The processing module 42 is also used to decapsulate the second IPv6 message received by the receiving module 41 to obtain a first response message, which is a response message corresponding to the first dial-up message, and establish a PPPoE session based on the first response message.

[0184] In the embodiment of the present application, the second IPv6 message also carries a service type identifier. The processing module is specifically configured to decapsulate the second IPv6 message when the service type identifier matches the preset type identifier.

[0185] It should be noted that all relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module and will not be repeated here.

[0186] In the case of dividing each functional module into corresponding functional modules, Fig. 9 A possible schematic diagram of the composition of the PPPoE negotiation device involved in the above embodiment is shown, and the PPPoE negotiation device is a second PPPoE negotiation device. Fig. 9 As shown, the second PPPoE negotiation device 50 may include: a receiving module 51, a processing module 52 and a sending module 53. The receiving module 51 is used to receive a first IPv6 message from a PE device, and the first IPv6 message carries a first identifier and a second identifier. The first identifier indicates the IP address of the first PPPoE negotiation device, and the second identifier indicates the IP address of the second PPPoE negotiation device. The processing module 52 is used to decapsulate the first IPv6 message received by the receiving module 51 to obtain a first dial-up message, and the first dial-up message is used to request the execution of the PPPoE negotiation process. The sending module 53 is used to send a response message corresponding to the first dial-up message processed by the processing module 52 to the PE device based on the first identifier.

[0187] In the embodiment of the present application, the first IPv6 message also carries a service type identifier. The processing module 52 is specifically configured to decapsulate the first IPv6 message when the service type identifier matches a preset identifier.

[0188] In an embodiment of the present application, the above-mentioned sending module 53 is specifically used to send a first response message to the PE device according to the first flow table pre-stored by the processing module 52; the first flow table includes a first identifier, and the first response message is a response message corresponding to the first dial-up message, and the first response message is used by the first PPPoE negotiation device to establish a PPPoE session.

[0189] In the embodiment of the present application, the receiving module 51 is further used to receive a third IPv6 message sent by the first PPPoE negotiation device before the sending module 53 sends the first response message to the PE device according to the pre-stored first flow table, wherein the third IPv6 message carries the first MAC address, the first session identifier and the first identifier of the first PPPoE negotiation device. The processing module 52 is specifically used to store the correspondence between the first MAC address, the first identifier and the first session identifier in the first flow table.

[0190] In the embodiment of the present application, the first dial-up message also carries the first MAC address and the first session identifier of the access device. The processing module 52 is specifically used to determine the first identifier corresponding to the first MAC address and the first session identifier in the first flow table as a third identifier, and the third identifier indicates the IP address of the first PPPoE negotiation device; and generate a second IPv6 message according to the first response message, and the second IPv6 message carries the third identifier. The sending module 53 is also used to send the second IPv6 message generated by the processing module 52 to the PE device.

[0191] In an embodiment of the present application, the above-mentioned processing module 52 is also used to carry a service type identifier in the first response message after determining the first identifier corresponding to the first MAC address and the first session identifier in the first flow table as the third identifier. The service type identifier indicates the service type of the service corresponding to the first response message, and the service type identifier is used by the first PPPoE negotiation device to decapsulate the second IPv6 message.

[0192] It should be noted that all relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module and will not be repeated here.

[0193] The embodiment of the present application also provides a PPPoE negotiation device system, including an access device, a BRAS and a PE device, wherein the access device executes the PPPoE negotiation method described in the above implementation manner, and the BRAS executes the PPPoE negotiation method described in the above implementation manner.

[0194] It should be noted that the specific working process of each functional module in the access device and BRAS provided in the embodiment of the present application can refer to the specific description of the corresponding process in the method embodiment, and the embodiment of the present application will not be described in detail here. The access device and BRAS provided in the embodiment of the present application are used to execute the above-mentioned PPPoE negotiation method, so the same effect as the above-mentioned PPPoE negotiation method can be achieved.

[0195] Through the description of the above implementation methods, technical personnel in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0196] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the modules or units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0197] The units described as separate components may or may not be physically separated, and the components shown as units may be one physical unit or multiple physical units, that is, they may be located in one place or distributed in multiple different places. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0198] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0199] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium, including several instructions to enable a device (which can be a single-chip microcomputer, chip, etc.) or a processor (processor) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (RandomAccess Memory, RAM), disk or optical disk and other media that can store program code.

[0200] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A PPPoE negotiation method, It is characterized in that The method comprises: The access device receives a first dial-up message from a first terminal, where the first dial-up message is used to request execution of a PPPoE negotiation process, and the first terminal is one of multiple terminals connected to the access device; The access device generates a first sixth-version Internet Protocol IPv6 message according to the first dial-up message, wherein the first IPv6 message carries a first identifier and a second identifier, wherein the first identifier indicates an Internet Protocol IP address of the access device, and the second identifier indicates an IP address of the BRAS, and the first identifier is used by the BRAS to feed back a response message corresponding to the first dial-up message; The access device sends the first IPv6 message to the operator edge PE device.

2. The method according to claim 1, It is characterized in that After the access device receives the first dial message from the first terminal, the method further includes: The access device carries a service type identifier in the first dial-up message, where the service type identifier indicates a service type of a service corresponding to the first dial-up message, and the service type identifier is used by the BRAS to decapsulate the first IPv6 message.

3. The method according to claim 1, It is characterized in that The first dial-up message also carries a first media access control MAC address and a first session identifier of the access device; After the access device sends the first IPv6 message to the PE device, the method further includes: The access device receives a second IPv6 message from the PE device, where the second IPv6 message carries a third identifier, where the third identifier indicates an IP address of the access device, and where the third identifier is determined based on the first MAC address and the first session identifier; The access device decapsulates the second IPv6 message to obtain a first response message, where the first response message is a response message corresponding to the first dial-up message; The access device establishes a PPPoE session based on the first response message.

4. The method according to claim 3, It is characterized in that The second IPv6 message also carries a service type identifier; The access device decapsulates the second IPv6 message, including: When the service type identifier matches the preset type identifier, the access device decapsulates the second IPv6 message.

5. A PPPoE negotiation method, It is characterized in that The method comprises: The BRAS receives a first IPv6 message from the PE device, where the first IPv6 message carries a first identifier and a second identifier, where the first identifier indicates an IP address of the access device, and the second identifier indicates an IP address of the BRAS; The BRAS decapsulates the first IPv6 message to obtain a first dial-up message, where the first dial-up message is used to request to execute a PPPoE negotiation process; The BRAS sends a response message corresponding to the first dial message to the PE device based on the first identifier.

6. The method according to claim 5, It is characterized in that The first IPv6 message also carries a service type identifier; The BRAS decapsulates the first IPv6 message, including: When the service type identifier matches a preset identifier, the BRAS decapsulates the first IPv6 message.

7. The method according to claim 5, It is characterized in that The BRAS sends a response message corresponding to the first dial message to the PE device based on the first identifier, including: The BRAS sends a first response message to the PE device according to a pre-stored first flow table; the first flow table includes the first identifier, the first response message is a response message corresponding to the first dial-up message, and the first response message is used by the access device to establish a PPPoE session.

8. The method according to claim 7, It is characterized in that Before the BRAS sends a first response message to the PE device according to the pre-stored first flow table, the method further includes: The BRAS receives a third IPv6 message sent by the access device, where the third IPv6 message carries the first MAC address of the access device, the first session identifier, and the first identifier; The BRAS stores a correspondence between the first MAC address, the first identifier, and the first session identifier in the first flow table.

9. The method according to claim 7, It is characterized in that The first dial-up message also carries the first MAC address of the access device and the first session identifier; The BRAS sends a first response message to the PE device according to the pre-stored first flow table, including: The BRAS determines the first identifier corresponding to the first MAC address and the first session identifier in the first flow table as a third identifier, where the third identifier indicates the IP address of the access device; The BRAS generates a second IPv6 message according to the first response message, where the second IPv6 message carries the third identifier; The BRAS sends the second IPv6 message to the PE device.

10. The method according to claim 9, It is characterized in that After the BRAS determines, in the first flow table, the first identifier corresponding to the first MAC address and the first session identifier as a third identifier, the method further includes: The BRAS carries a service type identifier in the first response message, where the service type identifier indicates a service type of a service corresponding to the first response message, and the service type identifier is used by the access device to decapsulate the second IPv6 message.

11. A PPPoE negotiation system, It is characterized in that The PPPoE negotiation system includes an access device, a PE device and a BRAS; The access device executes the PPPoE negotiation method according to any one of claims 1 to 4; the BRAS executes the PPPoE negotiation method according to any one of claims 5 to 10.

12. An access device, It is characterized in that The method comprises a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the PPPoE negotiation method according to any one of claims 1 to 4 are implemented.

13. A BRAS, It is characterized in that The method comprises a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the PPPoE negotiation method according to any one of claims 5 to 10 are implemented.

14. A readable storage medium, It is characterized in that The readable storage medium stores a program or an instruction, and when the program or the instruction is executed by the processor, the steps of the PPPoE negotiation method according to any one of claims 1 to 4 or 5 to 10 are implemented.

Images