Flow processing system and device based on PPPoE local shunting device cluster

Abstract

The invention provides a flow processing system and device based on a PPPoE local shunting device cluster, and the system comprises a plurality of preset shunting devices which are locally interconnected and intercommunicated, and a first target PPPoE Session feature table is stored in each preset shunting device. When a destination IP address extracted from a received uplink data message by a first shunting device exists in the stored first target PPPoE Session feature table, and the destination IP address is a second optical network unit ONU belonging to a second shunting device, the uplink data message can be directly reconstructed. According to the embodiment of the invention, the reconstructed data message is obtained and sent to the second shunting equipment, and the second shunting equipment can directly send the reconstructed data message to the corresponding second optical network unit ONU without passing through network side equipment, so that the network path can be shortened, the message forwarding efficiency can be improved, and meanwhile, the occupation of network bandwidth resources can be reduced.

Description

Technical Field

[0001] The present invention relates to the field of communication technology, and in particular to a traffic processing system and equipment based on a PPPoE local shunt device cluster. Background Art

[0002] Home broadband services are a foundational service for major carriers, providing fixed-line internet access services to households. The network architecture for FTTP home broadband services typically involves connecting the internet and the metropolitan area transport network (MAN) via a broadband remote access server (BRAS). The MAN can then connect to different optical line terminals (OLTs). Each OLT connects to corresponding terminal devices (such as mobile phones and computers) via its own optical network unit (ONU) in each household. Related technologies offer traffic diversion solutions for PPPoE session traffic related to a single OLT to address the issue of circuitous and inefficient network paths. However, related technologies lack solutions for PPPoE session traffic across multiple carriers' OLTs, resulting in the continued presence of circuitous and inefficient network paths and high bandwidth usage. Summary of the Invention

[0003] The purpose of the present invention is to provide a traffic processing system and device based on a PPPoE local traffic distribution device cluster, so as to shorten the network path, improve the message forwarding efficiency, and reduce the occupation of network bandwidth resources for the local traffic of PPPoE sessions across optical line terminals (OLTs) of multiple operators.

[0004] The present invention provides a traffic processing system based on a PPPoE local shunt device cluster, the system comprising: a plurality of locally interconnected preset shunt devices, each preset shunt device being connected to a corresponding network-side device; each preset shunt device being further connected to at least one optical line terminal (OLT); each optical line terminal (OLT) being connected to at least one optical network unit (ONU), so as to connect to a terminal device through each optical network unit (ONU); each preset shunt device storing a first target PPPoE Session feature table; wherein the first target PPPoE Session feature table is a combination of first PPPoE Session feature tables corresponding to each preset shunt device; each first PPPoE Session feature table including PPPoE connection feature information initiated by a first terminal corresponding to each optical network unit (ONU) belonging to the same preset shunt device; The first diversion device is used to extract the destination IP address from the upstream data packet if it receives the upstream data packet from the first optical network unit ONU through the first optical line terminal OLT; if the destination IP address exists in the first target PPPoE Session feature table and the destination IP address is the second optical network unit ONU belonging to the second diversion device, reconstruct the upstream data packet to obtain a reconstructed data packet, and send the reconstructed data packet to the second diversion device; the second diversion device is used to send the reconstructed data packet to the second optical network unit ONU through the second optical line terminal OLT.

[0005] Furthermore, each preset diversion device includes a synchronization management module; each synchronization management module is pre-configured with a synchronization interface; each synchronization management module is used to broadcast the device identification of the preset diversion device to which it belongs, so that each other preset diversion device saves the device identification after listening to the device identification, until the device identifications of all preset diversion devices are saved in each preset diversion device; for each synchronization management module, the synchronization management module is used to synchronize the corresponding first PPPoE Session feature table from each other synchronization management module through the synchronization interface configured on the synchronization management module according to the device identifications of all preset diversion devices saved in the preset diversion device to which it belongs, until the first target PPPoE Session feature table is obtained.

[0006] Furthermore, if the designated PPPoE Session feature table corresponding to the first designated diversion device is updated, the first designated synchronization management module in the first designated diversion device is used to: send an update message to the synchronization management module in each other preset diversion device except the first designated diversion device through the synchronization interface configured on the first designated synchronization management module, so that the synchronization management module in each other preset diversion device updates the preset Layer 2 forwarding table according to the update message, and updates the pre-saved first target PPPoE Session feature table.

[0007] Furthermore, the system includes: a new diversion device; the new diversion device is interconnected in the network between multiple preset diversion devices, and the new diversion device includes a new synchronization management module; the new synchronization management module is pre-configured with a new synchronization interface; the new synchronization management module is used to broadcast the new device identification of the new diversion device, so that after each preset diversion device monitors the new device identification, it sends its corresponding first PPPoE Session feature table to the new diversion device through the new synchronization interface.

[0008] Furthermore, for each synchronization management module, the synchronization management module is used to broadcast a preset first maintenance message according to a first preset period; if the designated maintenance message sent by the second designated synchronization management module is not received, and the duration of not receiving the designated maintenance message reaches a preset duration threshold, the first PPPoE Session feature table corresponding to the second designated diversion device is deleted from the first target PPPoESession feature table corresponding to the synchronization management module; wherein the second designated diversion device is the preset diversion device to which the second designated synchronization management module belongs.

[0009] Furthermore, each preset traffic diversion device further stores summary data corresponding to each first PPPoE Session feature table; for each synchronization management module, the synchronization management module is configured to: broadcast, at a second preset period, first summary data corresponding to the first PPPoE Session feature table generated locally; if the specified summary data received from the third designated synchronization management module is identical to the specified existing data stored in the preset traffic diversion device to which the synchronization management module belongs, determine that the synchronization management module is synchronized with the third designated synchronization management module; wherein the specified existing data is the summary data corresponding to the first PPPoE Session feature table pre-synchronized from the third designated synchronization management module to the synchronization management module; If the designated summary data received from the third designated synchronization management module is different from the designated existing data stored in the preset diversion device to which the synchronization management module belongs, a feature table acquisition request is sent to the third designated synchronization management module, so that the third designated synchronization management module sends the second PPPoESession feature table corresponding to the designated summary data to the synchronization management module, and updates the first PPPoE Session feature table corresponding to the designated existing data to the second PPPoESession feature table.

[0010] Furthermore, multiple preset diversion devices correspond to multiple broadband remote access servers BRAS, and each broadband remote access server BRAS stores a corresponding second target PPPoE Session feature table; wherein the second target PPPoE Session feature table is: a combination of the first PPPoE Session feature tables corresponding to all preset diversion devices belonging to the broadband remote access server BRAS; each synchronization management module is pre-configured with a synchronization management programming interface; each synchronization management module is used to obtain and save the second target PPPoE Session feature table stored in each broadband remote access server BRAS through the synchronization management programming interface.

[0011] Furthermore, each broadband remote access server BRAS corresponds to a different network operator.

[0012] Furthermore, each preset traffic diversion device further includes a PPPoE Session learning module, each PPPoESession learning module being configured to: during a PPPoE session phase, upon receiving a first uplink message, extract first information from the first uplink message and update the first information into a preset cache table; wherein the first information includes: a destination MAC address, a PPPoESessionID, a vlanTag of a Layer 2 Ethernet frame header, and an IP address in an IPCP message; When a PDAT message is received, the second information is extracted from the PDAT message, and the record corresponding to the second information is deleted from the preset cache table to obtain the first PPPoESession feature table corresponding to the preset diversion device to which the PPPoE Session learning module belongs; wherein the second information includes: destination MAC address, PPPoE SessionID.

[0013] The present invention provides a traffic processing device based on a PPPoE local traffic distribution device cluster, comprising any of the above-mentioned traffic processing systems based on a PPPoE local traffic distribution device cluster.

[0014] The traffic processing system and device based on the PPPoE local diversion device cluster provided by the present invention include multiple preset diversion devices that are locally interconnected, and a first target PPPoE Session feature table is stored in each preset diversion device. When the destination IP address extracted from the received uplink data message by the first diversion device exists in the stored first target PPPoE Session feature table, and the destination IP address is a second optical network unit (ONU) belonging to the second diversion device, the uplink data message can be directly reconstructed, and the obtained reconstructed data message can be sent to the second diversion device. The second diversion device can directly send the reconstructed data message to the corresponding second optical network unit (ONU) without passing through the network side device, thereby shortening the network path, improving the message forwarding efficiency, and reducing the occupation of network bandwidth resources. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] In order to more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the specific embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0016] Figure 1 A schematic diagram of a basic network architecture for an FTTH home broadband service provided by an embodiment of the present invention; Figure 2 A schematic diagram of a traffic processing system based on a PPPoE local traffic distribution device cluster provided by an embodiment of the present invention; Figure 3 A schematic diagram of a traffic processing system based on a PPPoE local traffic distribution device cluster provided by an embodiment of the present invention; Figure 4 A schematic diagram of a traffic processing system based on a PPPoE local traffic distribution device cluster provided by an embodiment of the present invention; Figure 5 A schematic diagram of a traffic processing system based on a PPPoE local traffic distribution device cluster provided by an embodiment of the present invention; Figure 6 A schematic diagram of the connection of a diversion device provided by an embodiment of the present invention; Figure 7 A PPPoE Session feature table processing flow chart provided in an embodiment of the present invention; Figure 8 A logic flow chart of local traffic diversion device processing provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0017] The following will clearly and completely describe the technical solutions of the present invention in conjunction with the embodiments. Obviously, the embodiments described are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of the present invention.

[0018] Home broadband service is the basic service of major operators, providing fixed-line Internet access services based on households. GPON / EPON (GPON stands for Gigabit-Capable Passive Optical Network; EPON stands for Ethernet Passive Optical Network) network technology has been maturely applied to the access network for home Internet access in residential areas. Home users use FTTH / FTTR (FTTH stands for Fiber To The Home; FTTR stands for Fiber to the Room) technology to achieve gigabit high-speed bandwidth access and access to Internet applications through optical network units (ONUs) / optical network terminals (ONTs) (ONUs stand for Optical Network Units; ONTs stand for Optical Network Terminals). For example Figure 1The following is a basic network architecture diagram of an FTTH home broadband service. The Internet data center / cloud application connects to the optical line terminal OLT1 and the optical line terminal OLT2 through the broadband remote access server BRAS (Broadband Remote Access Server) and the metropolitan area transmission network. The optical line terminal OLT1 is connected to the optical network unit ONU in home 1 and the optical network unit ONU in home 2, respectively. The optical line terminal OLT2 is connected to the optical network unit ONU in home 3 and the optical network unit ONU in home 4, respectively. Each optical network unit ONU is connected to its corresponding computer, mobile phone and other terminals. Figure 1 This section only describes the FTTH network of a single operator. In the case of multiple operators, their respective communication facilities will be set up according to the above network structure, including a full set or partial equipment from the optical network unit (ONU) - optical line terminal (OLT) - metropolitan area transport network - broadband remote access server (BRAS). PPPoE (Point-to-Point Protocol Over Ethernet, a network tunneling protocol that encapsulates the Point-to-Point Protocol (PPP) in an Ethernet framework) provides access authentication, session control, and billing functions for terminals. It is currently widely used by various operators in FTTH home broadband access networks. PPPoE is a point-to-point link data link layer protocol that uses a Client / Server model. The PPPoE Client initiates a connection request to the PPPoE Server. After the session negotiation between the two is successful, a PPPoE session is established. Figure 1 In the FTTH network shown, the ONU is generally the PPPoE Client (the home wireless router connected to the ONU can also be the PPPoE Client), the broadband remote access server BRAS is the PPPoE Server, and the user's terminal is the smart terminal such as the computer or mobile phone in the home (connected to the ONU via wireless). The data information of the home smart terminal accessing the Internet application is encapsulated in the PPP packet of the PPPoE message, that is, the information part of the PPP message in the PPPoE message structure. The PPPoE message structure can be referred to the relevant technology and will not be described here. Figure 1 From the perspective of network architecture, this access method is suitable for accessing cloud-based Internet applications or core data centers. The broadband remote access server BRAS is the core aggregation device for user-side access to network center data. At this time, the access path of user service data flow is: ONU-OLT-metropolitan area transmission network-BRAS-Internet / data center.

[0019] With the promotion of decentralized business, Figure 1The network architecture and the simple use of PPPoE to carry service data are unsuitable for efficient communication between service providers. For example, in a point-to-point video communication application between households 1 and 2, the video stream is encapsulated as an IP packet within a PPP packet. The network path for communication is: ONU in household 1 - OLT 1 - metropolitan area transport network - BRAS - metropolitan area transport network - OLT 1 - ONU in household 2. This network path is obviously circuitous and inefficient, making it unsuitable for latency-sensitive services and also consuming metropolitan area network bandwidth between the OLT and BRAS. A simple, direct, efficient, and secure communication path should be: ONU in household 1 - OLT 1 - ONU in household 2. This is suitable for various local services, such as local video services and edge cloud services. Major communications vendors have launched optical line terminals (OLTs) that support local traffic diversion or local traffic offload (TOF) functions. However, these functions are generally not used for home broadband services. Instead, they are applied to specific local planning services. For example, MEC (Mobile edge computing) edge cloud applications are deployed in the end office to complete Layer 2 switching of local traffic through pre-planned VLAN (Virtual Local Area Network) and PON (Passive Optical Network) access ports.

[0020] Related technologies disclose a method for implementing local traffic diversion by learning and analyzing the PPPoE protocol and data packet content to establish a forwarding table. This method solves the problem of diverting local data traffic within a PPPoE session within a single optical line terminal (OLT), specifically the local traffic from home 1 to home 2. However, it does not address how to ensure local traffic diversion between multiple optical line terminals (OLTs).

[0021] In summary, the relevant technologies still have the following disadvantages: 1. Each operator's network is independent and does not support local traffic offloading across operators; 2. It only supports local traffic forwarding within the optical line terminal (OLT) and does not support cross-optical line terminal (OLT); 3. Requires upfront planning and lacks flexibility for later changes; 4. Different manufacturers have different configuration methods, which makes management and maintenance difficult and costly; 5. For TOF boards built into the optical line terminal (OLT), the optical line terminal (OLT) needs to be upgraded. Old equipment is not supported.

[0022] It is a common phenomenon that household A in a residential complex uses the FTTH network of operator A, while household B uses the FTTH network of operator B. Figure 1 In the network architecture, it is assumed that home 1 is a user of operator A and home 3 is a user of operator B. In the prior art, the traffic path from home 1 to home 3 is as follows: ONU of home 1—OLT1—metropolitan area transmission network of operator A—BRAS of operator A—public network transmission network—BRAS of operator B—metropolitan area transmission network of operator B—OLT2—ONU of home 3. It can be seen that the traffic path is lengthy. Based on this, an embodiment of the present invention provides a traffic processing system and device based on a PPPoE local diversion device cluster. This technology can be applied to local traffic forwarding applications of PPPoE sessions across optical line terminals (OLTs).

[0023] To facilitate understanding of this embodiment, firstly, a traffic processing system based on a PPPoE local traffic distribution device cluster disclosed in an embodiment of the present invention is introduced. Figure 2 As shown, the system includes: multiple preset diversion devices 30 that are locally interconnected, each preset diversion device 30 is connected to its corresponding network side device; the network side device may include a broadband remote access server BRAS, etc.; the preset diversion device 30 can be connected to the Internet through a metropolitan area transmission network, a broadband remote access server BRAS; wherein, at least a part of the preset diversion devices 30 may be connected to the same network side device; each preset diversion device 30 is also connected to at least one optical line terminal OLT; the optical line terminal OLT generally refers to a terminal device for connecting an optical fiber trunk line; each optical line terminal OLT is connected to at least one optical network unit ONU, so as to connect to the terminal device through each optical network unit ONU; the optical network unit ONU can be understood as a device that converts optical signals into electrical signals; the terminal device may include a computer, a mobile phone, etc.; in actual applications, each preset diversion device 30 can be connected to one or more optical line terminals OLT, each optical line terminal OLT can be connected to one or more optical network units ONU, usually each optical network unit ONU can correspond to a household, and each optical network unit ONU is connected to a mobile phone, computer, etc. in the corresponding household.

[0024] Each preset diversion device 30 stores a first target PPPoE Session feature table; wherein the first target PPPoE Session feature table is: a combination of the first PPPoE Session feature tables corresponding to each preset diversion device 30; each first PPPoE Session feature table includes the PPPoE connection feature information initiated by the first terminal corresponding to each optical network unit ONU belonging to the same preset diversion device 30, that is, it records the PPPoE connection feature information initiated by the first terminal corresponding to all optical network units ONU in the PPPoE session stage; the first terminal can be the optical network unit ONU itself or the terminal device connected to the optical network unit ONU; the PPPoE connection feature information can include PPPoE-related four-tuple information, namely the local ONU MAC, the vlanTag of the layer 2 Ethernet frame header (supports single-layer or double-layer tags), PPPoESessionID, and the IP address assigned to the local ONU, wherein the local ONU MAC can be understood as the physical address of the optical network unit ONU; the vlanTag of the layer 2 Ethernet frame header is a part of the Ethernet frame header, which is used to mark which VLAN the data frame belongs to; PPPoE The SessionID is a unique identifier used to identify a specific PPPOE session; the IP address assigned by the local ONU is the local IP address assigned by the optical network unit (ONU) to the user's terminal device. For each preset diversion device 30, a first PPPoE Session feature table corresponding to the local end is pre-generated in the preset diversion device 30, including PPPoE connection feature information initiated by the first terminal corresponding to each optical network unit (ONU) belonging to the preset diversion device 30. Multiple locally interconnected preset diversion devices 30 synchronize information and combine the first PPPoE Session feature tables corresponding to each preset diversion device 30 to obtain a first target PPPoE Session feature table. This first target PPPoE Session feature table is stored in each preset diversion device 30.

[0025] The first diversion device is used to extract the destination IP address from the upstream data packet if it receives the upstream data packet from the first optical network unit ONU through the first optical line terminal OLT; if the destination IP address exists in the first target PPPoE Session feature table and the destination IP address is the second optical network unit ONU belonging to the second diversion device, reconstruct the upstream data packet to obtain a reconstructed data packet, and send the reconstructed data packet to the second diversion device; the second diversion device is used to send the reconstructed data packet to the second optical network unit ONU through the second optical line terminal OLT.

[0026] The first diversion device can be any diversion device among the multiple preset diversion devices 30; the first optical line terminal OLT can be any optical line terminal OLT among the at least one optical line terminal OLT connected to the first diversion device; the first optical network unit ONU can be any optical network unit ONU among the at least one optical network unit ONU connected to the first optical line terminal OLT; the uplink data message is usually a PPPoE session data message; the second diversion device is usually different from the first diversion device, the second optical line terminal OLT is one of the optical line terminals OLT connected to the second diversion device, and the second optical network unit ONU is one of the optical network units ONU connected to the second optical line terminal OLT; in actual implementation, the first user sends an uplink data message to the connected first optical network unit ONU by operating the terminal device, and the uplink data message is uploaded to the first diversion device through the connected first optical line terminal OLT. The first diversion device can extract the destination IP address from the received uplink data message, match the destination IP address with the saved first target PPPoESession feature table, to determine whether the destination IP address exists in the first target PPPoE If the Session feature table exists and the destination IP address is the second optical network unit (ONU) belonging to the second shunt device, that is, when it needs to be sent across the optical line terminal (OLT), the first shunt device can reconstruct the uplink data message to obtain a reconstructed data message. Through the reconstruction process, the uplink data message initiated by the first optical network unit (ONU) to the network side device can be changed to a downlink reconstructed data message initiated by the network side device to the second optical network unit (ONU). This can achieve the same effect as the uplink data message being detoured to the network side device and then sent down by the network side device. The first shunt device can send the reconstructed data message to the second shunt device, and the second shunt device can directly send the reconstructed data message to the second optical network unit (ONU) through the second optical line terminal (OLT).

[0027] The system does not require changes to the deployment of existing network facilities, nor does it require upgrades to existing optical line terminals (OLTs). Instead, it only requires deployment of diversion equipment at the same network location as the OLT in the cell access office room, such as Figure 3 The schematic diagram of a traffic processing system based on a PPPoE local distribution device cluster is shown in FIG. Figure 1 On the basis of the system, a splitter device 1 and a splitter device 2 are added between the optical line terminal OLT1, the optical line terminal OLT2 and the metropolitan area transmission network respectively.

[0028] The above-mentioned traffic processing system based on the PPPoE local diversion device cluster includes multiple preset diversion devices that are locally interconnected, and a first target PPPoE Session feature table is stored in each preset diversion device. When the destination IP address extracted from the received uplink data packet by the first diversion device exists in the stored first target PPPoESession feature table, and the destination IP address is the second optical network unit ONU belonging to the second diversion device, the uplink data packet can be directly reconstructed and the obtained reconstructed data packet is sent to the second diversion device. The second diversion device can directly send the reconstructed data packet to the corresponding second optical network unit ONU without passing through the network side device, thereby shortening the network path, improving the message forwarding efficiency, and reducing the occupation of network bandwidth resources.

[0029] Further, such as Figure 4 The diagram shows a traffic processing system based on a PPPoE local diversion device cluster. The system only needs to perform local diversion processing on the user-side upstream PPPoE traffic, and does not need to process the downstream traffic from the network side (i.e., the BRAS side). In the PPPoE upstream traffic, only the PPPoE session phase data packets with the local IP destination address are locally forwarded, which does not affect the forwarding of other packets. The preset diversion device in this solution includes a PPPoE Session learning module, a local PPPoE message diversion module, a Layer 2 switching module, and a PPPoE Session synchronization management module. The PPPoE Session synchronization management module provides a first PPPoE Session feature table synchronization function between preset diversion devices to support local traffic diversion functions across optical line terminals (OLTs) and across operators, such as Figure 4 For local traffic where both the source and sink ONUs are under this shunt device, the shunt device reconstructs the message header and then directly forwards it locally. The effect is the same as Figure 4 The "return local traffic" function can be used to forward local traffic destined for other optical line terminals (OLTs) to the other party's local traffic diversion device for processing.

[0030] Each pre-configured traffic diversion device includes a synchronization management module; each synchronization management module is pre-configured with a synchronization interface. In actual implementation, administrators can specify a synchronization interface for each synchronization management module to enable signature table synchronization. Synchronizing the first PPPoE session signature table between pre-configured traffic diversion devices can be achieved using a proprietary protocol. The appropriate proprietary protocol can be selected based on actual needs. This solution does not specify the specific bearer layer and protocol parameters for implementing this proprietary protocol. Instead, it describes a mechanism for implementing the signature table synchronization protocol.

[0031] Each synchronization management module is configured to broadcast the device identification of its own preset diversion device, so that each other preset diversion device, after hearing the device identification, saves the device identification until each preset diversion device has the device identifications of all preset diversion devices saved. The device identification may also be referred to as a device ID (Identity Document), which may be represented by a MAC address (Media Access Control Address, also known as a local area network address) of the preset diversion device. Different preset diversion devices correspond to different device identifications, and the device identifications can be used to distinguish different preset diversion devices. In actual implementation, each synchronization management module may broadcast the device identification of its own preset diversion device, and each other preset diversion device may hear and save the device identification. Each synchronization management module will perform the process of broadcasting the device identification of its own preset diversion device and listening to each other preset diversion device hear the device identification. Ultimately, each preset diversion device may have the device identifications of all preset diversion devices saved. For example, each preset diversion device may have a device ID table of all preset diversion devices in the entire network.

[0032] For each synchronization management module, the synchronization management module is used to synchronize the first PPPoE Session feature table corresponding to each of the other synchronization management modules, based on the device identifiers of all preset diversion devices stored in the preset diversion device to which it belongs, through the synchronization interface configured on the synchronization management module, until the first target PPPoE Session feature table is obtained. In actual implementation, after the device identifiers of all preset diversion devices are stored in each preset diversion device, for each synchronization management module, the synchronization management module can synchronize the first PPPoE Session feature table generated in each of the other preset diversion devices, based on the device identifiers of all preset diversion devices stored in the preset diversion device to which it belongs, through the synchronization interface, and obtain the first target PPPoE Session feature table after combining them.

[0033] For the traffic processing system based on PPPoE local split device cluster, it is a scenario where the split device is connected to multiple OLTs, that is, the local split device supports the access of multiple OLTs, such as Figure 5The diagram shows a traffic processing system based on a cluster of PPPoE local traffic diversion devices. The diversion devices are connected to OLT1 and OLT2, OLT1 is connected to ONU1, and OLT2 is connected to ONU2. The diversion devices automatically learn the IP allocation information reported by each optical line terminal (OLT) during a PPPoE session and record it in the corresponding first PPPoE session feature table. For this type of local traffic across OLTs, the diversion devices do not require support from a synchronization management module.

[0034] Furthermore, if the designated PPPoE Session feature table corresponding to the first designated diversion device is updated, the first designated synchronization management module in the first designated diversion device is used to: send an update message to the synchronization management module in each other preset diversion device except the first designated diversion device through the synchronization interface configured on the first designated synchronization management module, so that the synchronization management module in each other preset diversion device updates the preset Layer 2 forwarding table according to the update message, and updates the pre-saved first target PPPoE Session feature table.

[0035] The above-mentioned first designated diversion device can be any diversion device among the above-mentioned multiple preset diversion devices; the above-mentioned designated PPPoE Session feature table can be understood as the first PPPoE Session feature table generated by the first designated diversion device. When the PPPoE connection feature information recorded in the designated PPPoE Session feature table is added, deleted or modified, the first designated synchronization management module in the first designated diversion device can send an update message to the synchronization management module in each other preset diversion device in the network. The update message generally includes: the device identifier of the first designated diversion device, the local optical network unit ONU MAC belonging to the first designated diversion device, the update flag of the designated PPPoE Session feature table, and the updated designated PPPoE Session feature table. After receiving the update message, the synchronization management module in each other preset diversion device can update the second-layer forwarding table according to the update message, that is, for the added feature table records, add the corresponding PPPoEClient MAC and port; for the deleted feature table records, delete the second-layer forwarding table of the corresponding MAC, and then synchronize the specified PPPoESession feature table record to the saved first target PPPoE Session feature table to synchronize the update of the first target PPPoE Session feature table.

[0036] The following describes the process of updating the Layer 2 forwarding table. After reconstructing the Layer 2 frame header of a local service packet, the splitter device forwards the packet according to the Layer 2 forwarding mechanism, specifically forwarding it to its bound port based on the destination MAC address. The binding relationship between MAC addresses and ports constitutes the Layer 2 forwarding table. The Layer 2 forwarding table within the splitter device is formed by learning and announcing feature table records. For example, the MAC address and IP address of optical network unit (ONU) ONU_A are MAC_A and IP_A, and ONU_A is assigned to splitter device A. Splitting device A learns the PPPoE session feature record for MAC_A through port A.eth1. Splitting device A then creates a forwarding table entry for A.eth1 and MAC_A. Splitting device A also notifies splitter device B of this learned local feature record. Splitting device B receives this notification through port B.eth1 and creates a Layer 2 forwarding table entry for MAC_A and B.eth1. When the PPPoE service packet destined for IP_A is parsed by the branch device B, after reconstructing the Layer 2 header of the packet, the destination address becomes MAC_A. According to the Layer 2 forwarding mechanism, the packet is sent from B.eth1 to the branch device A. After receiving the packet, the branch device A forwards it from A.eth1 according to the Layer 2 forwarding mechanism, and finally reaches the optical network unit ONU_A.

[0037] Furthermore, the system includes: a new diversion device; the new diversion device is interconnected in the network between multiple preset diversion devices, and the new diversion device includes a new synchronization management module; the new synchronization management module is pre-configured with a new synchronization interface; the new synchronization management module is used to broadcast the new device identification of the new diversion device, so that after each preset diversion device monitors the new device identification, it sends its corresponding first PPPoE Session feature table to the new diversion device through the new synchronization interface.

[0038] The above-mentioned newly added diversion device can be a newly added diversion device, an existing diversion device restarted, or a link that is turned from offline to online. In this case, it can be considered that there is a newly added diversion device; in actual implementation, when there is a newly added diversion device in the system, the newly added synchronization management module in the newly added diversion device can broadcast the newly added device identification of the newly added diversion device to the entire network, so that each preset diversion device that has a network intercommunication relationship with the newly added diversion device can monitor the newly added device identification, and can send the first PPPoE Session feature table generated locally to the newly added diversion device. As a result, the newly added diversion device can be synchronized to the first PPPoE Session feature table of the entire network.

[0039] Furthermore, for each synchronization management module, the synchronization management module is used to broadcast a preset first maintenance message according to a first preset period; the first preset period can be set according to actual needs; the first maintenance message can be understood as a heartbeat packet or other form of message sent periodically by the synchronization management module to maintain the active state of the connection; if the designated maintenance message sent by the second designated synchronization management module is not received, and the duration of not receiving the designated maintenance message reaches a preset duration threshold, the first PPPoE Session feature table corresponding to the second designated diversion device is deleted from the first target PPPoE Session feature table corresponding to the synchronization management module; wherein the second designated diversion device is the preset diversion device to which the second designated synchronization management module belongs.

[0040] The above-mentioned second designated synchronization management module can be a synchronization management module in any diversion device among the above-mentioned multiple preset diversion devices; the above-mentioned designated maintenance message can be understood as a heartbeat packet or other form of message periodically sent by the second designated synchronization management module; the above-mentioned preset time threshold can be set according to actual needs; in actual implementation, each synchronization management module can periodically broadcast the preset first maintenance message, and can also monitor the first maintenance message broadcast by each other synchronization management module. For each synchronization management module, if the synchronization management module does not receive the designated maintenance message sent by the second designated synchronization management module, and the duration reaches the preset time threshold, the record of the first PPPoE Session feature table corresponding to the second designated diversion device can be deleted from the first target PPPoE Session feature table saved in the preset diversion device to which the synchronization management module belongs.

[0041] Furthermore, each preset traffic diversion device further stores summary data corresponding to each first PPPoE Session feature table; for each synchronization management module, the synchronization management module is configured to: broadcast, at a second preset period, first summary data corresponding to the first PPPoE Session feature table generated locally; if the specified summary data received from the third designated synchronization management module is identical to the specified existing data stored in the preset traffic diversion device to which the synchronization management module belongs, determine that the synchronization management module is synchronized with the third designated synchronization management module; wherein the specified existing data is the summary data corresponding to the first PPPoE Session feature table pre-synchronized from the third designated synchronization management module to the synchronization management module; The above-mentioned summary data can be a distillation and summary of the key core data in the first PPPoE Session feature table, with the purpose of presenting key technical parameters or statistical results in a concise manner; the above-mentioned second preset period can be set according to actual needs and is not limited here; the above-mentioned third designated synchronization management module can be a synchronization management module in any diversion device among the above-mentioned multiple preset diversion devices; in actual implementation, each synchronization management module can periodically broadcast the first summary data corresponding to the first PPPoE Session feature table generated by the local end, and can also monitor the first summary data broadcast by each other synchronization management module. For each synchronization management module, if the specified summary data sent by the third designated synchronization management module received by the synchronization management module is consistent with the summary data corresponding to the first PPPoE Session feature table synchronized from the third designated synchronization management module to the synchronization management module in advance, it means that the synchronization management module and the third designated synchronization management module are synchronized.

[0042] If the designated summary data received from the third designated synchronization management module is different from the designated existing data stored in the preset diversion device to which the synchronization management module belongs, a feature table acquisition request is sent to the third designated synchronization management module, so that the third designated synchronization management module sends the second PPPoESession feature table corresponding to the designated summary data to the synchronization management module, thereby updating the first PPPoE Session feature table corresponding to the designated existing data with the second PPPoESession feature table. If the designated summary data received from the third designated synchronization management module is inconsistent with the summary data corresponding to the first PPPoE Session feature table previously synchronized from the third designated synchronization management module to the synchronization management module, the synchronization management module may send a feature table acquisition request to the third designated synchronization management module, requesting the third designated synchronization management module to send the second PPPoESession feature table corresponding to the designated summary data, thereby updating the record in the first PPPoE Session feature table corresponding to the designated existing data stored locally in the synchronization management module.

[0043] Furthermore, multiple preset diversion devices correspond to multiple broadband remote access servers BRAS, and each broadband remote access server BRAS stores a corresponding second target PPPoE Session feature table; wherein the second target PPPoE Session feature table is: a combination of the first PPPoE Session feature tables corresponding to all preset diversion devices belonging to the broadband remote access server BRAS; each synchronization management module is pre-configured with a synchronization management programming interface; each synchronization management module is used to obtain and save the second target PPPoE Session feature table stored in each broadband remote access server BRAS through the synchronization management programming interface.

[0044] The above-mentioned broadband remote access server BRAS is a network device specially used for broadband access management. It is located between the user access network and the operator's core network and provides functions such as user access authentication, authorization, billing, address allocation and traffic management. In actual implementation, the number of preset diversion devices may be the same as or different from that of the broadband remote access server BRAS, that is, a broadband remote access server BRAS may be connected to only one preset diversion device, or may be connected to a part of multiple preset separation devices. For example, a broadband remote access server BRAS may be connected to one, two or three preset diversion devices, etc., and the specific setting can be made according to actual needs and is not limited here; the broadband remote access server BRAS may be an operator A BRAS, an operator B BRAS, etc.; each broadband remote access server BRAS stores a corresponding second target PPPoE Session feature table, and the second target PPPoE Session feature table is specifically a combination of the first PPPoE Session feature tables corresponding to all preset diversion devices belonging to the broadband remote access server BRAS. For example, taking the broadband remote access server BRAS as an operator A BRAS, the operator A BRAS is connected to two preset diversion devices through the operator A metropolitan area transmission network, and the operator A BRAS stores a combination of the first PPPoE Session feature tables corresponding to the two preset diversion devices.

[0045] In this embodiment, each synchronization management module is also pre-configured with a synchronization management programming interface. Through this synchronization management programming interface, each synchronization management module can synchronize the second target PPPoE session feature table from each broadband remote access server (BRAS). For example, if the multiple broadband remote access servers (BRASs) are operator A's BRAS and operator B's BRAS, the pre-set traffic diversion device A can synchronize the second target PPPoE session feature table stored therein from operator A's BRAS and synchronize the second target PPPoE session feature table stored therein from operator B's BRAS, ultimately forming a complete first target PPPoE session feature table. Synchronizing from each broadband remote access server (BRAS) means that the data stored by each broadband remote access server (BRAS) is used as the basis. Specifically, the user can use the synchronization management programming interface to select whether to use the second target PPPoE session feature table to generate or overwrite the first target PPPoE session feature table. Furthermore, the synchronization management programming interface can also provide read and write configuration operations for the feature table using the SNMP or NETCONF management protocols.

[0046] In addition, in this embodiment, each synchronization management module can also support manual maintenance of the feature table addition and deletion, so that users can control the local diversion of specific PPPoE client devices as needed. Users can also use the synchronization management module to reasonably configure the default aging time of the PPPoE session feature table. The synchronization management module provides extended processing capabilities for the first PPPoE Session feature table, and these capability interfaces can be expanded as needed. It supports automatic synchronization across multiple splitting devices in cross-optical line terminals (OLTs) and cross-operator scenarios through a feature table synchronization protocol. It also provides a synchronization management programming interface to synchronize records from the current second-target PPPoE Session feature table on the broadband remote access server (BRAS). It also supports manual maintenance of feature table additions and deletions, allowing users to control local splitting of specific PPPoE client devices as needed. It also allows for reasonable configuration of the default aging time for the PPPoE session feature table. Furthermore, each broadband remote access server BRAS corresponds to a different network operator. For example, there are two broadband remote access servers BRAS, which correspond to operator A and operator B respectively. Accordingly, these two broadband remote access servers BRAS can also be called operator A BRAS and operator B BRAS respectively.

[0047] In actual applications, if the uplink of each optical line terminal OLT needs to be independent, for example, in a cross-operator scenario, there is a requirement for independent management between the diversion devices, and they are deployed in different end-office rooms, the optical line terminals OLTs of different operators are connected to their respective diversion devices, and then connected to their respective network side devices through the diversion devices. Figure 6 The figure shows a connection diagram of a diversion device. The diversion devices in the figure use a ring topology, but other topologies can also be used, such as a chain topology or a fully connected topology. Considering the requirements for network connectivity redundancy, protection, and fault tolerance, this solution uses a ring topology as an example. Topology loop prevention is ensured by Layer 2 or Layer 3 protocols, such as enabling STP (Spanning Tree Protocol) at Layer 2 to block redundant links to prevent loops. For details, please refer to relevant technologies and will not be elaborated here. The links between the diversion devices are used for both synchronization of the first PPPoE Session feature table and transmission of local data traffic.

[0048] Further, such as Figure 4 As shown, each preset diversion device also includes a PPPoE Session learning module, and each PPPoE Session learning module is used to: in the PPPoE session stage, when the first uplink message is received, extract the first information from the first uplink message, and update the first information to the preset cache table; wherein the first information includes: the destination MAC address, the PPPoE SessionID, the vlanTag of the second layer Ethernet frame header, and the IP address in the IPCP message; the destination MAC address can be understood as the MAC address of the destination optical network unit ONU to which the first uplink message is to be sent; the IP address in the above-mentioned IPCP message can be understood as the IP address assigned by the destination optical network unit ONU.

[0049] Upon receiving a PDAT (Protocol Data Allocation Table) message, the system extracts the second information from the PDAT message, deletes the record corresponding to the second information from the preset cache table, and obtains a first PPPoE session feature table corresponding to the preset offload device to which the PPPoE session learning module belongs. The second information includes the destination MAC address and the PPPoE Session ID. The PDAT message is a special message in the PPPoE protocol used to notify a network device to terminate the current PPPoE session.

[0050] like Figure 7The figure shows a PPPoE session feature table processing flow chart. This diagram illustrates how PPPoE session feature table entries are added or updated (in the case of an update, a historical entry for the specified MAC address may already exist in the feature table) via PPP packets obtained from the Network Control Protocol (NCP) IP address during the PPPoE session phase, and deleted via the PADT message upon PPPoE termination. Furthermore, similar to ARP learning, the PPPoE session feature table also has a default aging time. Upon receiving a PPPoE session message or a PPPoE keep-alive LCP (Link Control Protocol) message, the aging time of the PPPoE session feature table is refreshed. After the aging time expires, the relevant PPPoE session feature table is deleted.

[0051] Specifically, such as Figure 7As shown, first, the PPPoE Session learning module extracts the Layer 2 message (corresponding to the first uplink message mentioned above) from the received message and executes the first judgment condition, that is, whether the Layer 2 message meets the following conditions: source MAC = BRAS MAC and Ether_type = 0x8864 and PPPoE frame header code = 0x00 and PPP header protocol = 0x8021 and IPCP code = 2 / ack; if these conditions are met, it can be considered that the received message is obtained through the NCP IP address of the PPPoE session phase. At this time, the destination MAC address, PPPoESessionID, vlanTag of the Layer 2 Ethernet frame header and the IP address in the IPCP message can be extracted from the Layer 2 message and this information is added or updated to the preset cache table; the second judgment condition is executed, that is, whether the Layer 2 message meets the following conditions: Ether_type = 0x8864 and PPPoE frame header code = 0xa7. If this condition is met, it is confirmed that the PDAT message has been received, and the destination MAC address, PPPoE protocol ID, and IP address in the PDAT message are extracted from the PDAT message. SessionID, delete the corresponding record in the preset cache table, and finally obtain the first PPPoE Session feature table corresponding to the preset diversion device to which the PPPoE Session learning module belongs, and then perform PPPoE local traffic message processing; if the second-layer message does not meet the first judgment condition and is confirmed to be a PPP message obtained by a non-NCP IP address, the second judgment condition is directly executed. If the second judgment condition is not met and it is confirmed to be a non-PDAT message, the PPPoE local traffic message processing process is executed. In this embodiment, the fields to be extracted are simpler, which helps to improve the efficiency and accuracy of traffic processing. By learning the NCP IP address allocation of the PPP IPCP message in the PPPoE session phase and the PADT message terminated by PPPoE, the IP-MAC-PPPoESessionID-vlanTag table entry record of the first PPPoE Session feature table is automatically maintained, providing a data basis for the identification of PPPoE local traffic.

[0052] like Figure 4 As shown, each preset diversion device also includes a local PPPoE message diversion module, which realizes the direct local forwarding of local traffic carried by PPPoE, that is, during the PPPoE session phase, the service traffic with both the source and destination locally is locally exchanged through the local diversion device of this solution, without having to go up to the core side of the broadband remote access server BRAS. This traffic diversion device will not damage the control function of the PPP protocol, including the discovery phase of PPPoE link establishment, the link control protocol LCP, network control protocol NCP, and authentication protocol in the PPP session phase. It only encapsulates the PPPoE Ethernet frame header field of the data exchanged during the PPPoE session phase. Figure 8 The logic of the local traffic distribution device processing logic flow chart shown in the figure is replaced. The content of the PPPoE layer 2 message is reconstructed including: 1. Source MAC = BRAS MAC; 2. Destination MAC = PPPoE Client MAC matching the destination IP in the first target PPPoE Session signature table; 3. Vlan Tag = PPPoE Layer 2 frame VLAN Tag matched by the destination IP in the first target PPPoE Session signature table; 4. PPPoE Session ID = PPPoESession ID that matches the destination IP in the first target PPPoE Session signature table; The effect of the above processing is that the upstream PPPoE session data packets initiated by the source ONU to the BRAS are changed to downstream PPPoE session data packets initiated by the BRAS to the destination ONU. In other words, the effect is like the PPPoE session data packets sent down by the BRAS after the PPPoE session data packets have been routed to the BRAS. Figure 8 The specific process is as follows: The local PPPoE packet splitting module extracts the Layer 2 packet and performs the first judgment condition, namely, whether the Layer 2 packet meets the following conditions: Ether_type = 0x8864 in the Ethernet frame header, code = 0x00 in the PPPoE frame header, and protocol = 0x0021 in the PPP header. If these conditions are met, it is considered a PPPoE data packet. The destination IP address of the PPP data packet is then extracted from the Layer 2 packet and checked to see if it exists in the stored first-target PPPoE session feature table. If so, the Layer 2 packet is reconstructed and general Layer 2 forwarding is performed. If the Layer 2 packet does not meet the first judgment condition and is determined not to be a PPPoE data packet, or if the destination IP address does not exist in the stored first-target PPPoE session feature table, general Layer 2 forwarding is performed according to existing technologies. In this way, traffic within the cell flows directly within the cell network without having to circumvent the remote BRAS.

[0053] like Figure 4As shown, each pre-configured traffic diversion device also includes a Layer 2 switching module. This Layer 2 switching module can be a general-purpose Layer 2 switching module for receiving output packets from the local PPPoE packet diversion module and performing Layer 2 forwarding. This system can be implemented using underlying hardware such as an ASIC (Application Specific Integrated Circuit) or FPGA (Field Programmable Gate Array) chip, or through software including an SDN (Software-Defined Networking) controller, network management system, or specialized application software such as a PPPoE proxy or forwarding gateway. The implementation logic remains the same.

[0054] The traffic processing system based on a PPPoE local traffic splitting device cluster demonstrates a technology that supports multi-operator deployment across multiple OLTs to implement local data traffic splitting within PPPoE sessions. This solution eliminates the circuitous long-distance transmission of PPPoE local data packets from user terminals to the broadband remote access server (BRAS). Deploying the local traffic splitting devices in the central office (CO) of the optical line terminal (OLT) allows local service traffic to be exchanged locally, optimizing network resources and improving service QoS (Quality of Service). Furthermore, the local traffic splitting devices in this solution synchronize PPPoE session information between devices and identify local traffic across operators and OLTs, truly achieving local traffic flow. This supports the construction of modern digital smart networks with multi-operator convergence within local networks. This solution proposes a proprietary, hardware-software-integrated local traffic splitting device suitable not only for PON networks but also for any other wireless or wired access networks using the PPPoE protocol, improving the transmission efficiency of local intercommunication traffic initiated by terminal devices. The present invention provides a traffic processing device based on a PPPoE local traffic distribution device cluster, comprising any of the above-mentioned traffic processing systems based on a PPPoE local traffic distribution device cluster.

[0055] By deploying the traffic diversion equipment in this solution, local application traffic no longer needs to be routed through remote BRAS equipment. Even in the case of heterogeneous operator FTTX (Fiber To The X), interactive forwarding can be achieved directly within the local cell area, improving the end-to-end transmission efficiency of local service traffic, reducing transmission delay, reducing the probability of packet loss, and optimizing service quality. In particular, it enhances the user experience for delay-sensitive applications such as video interaction.

[0056] by Figure 1Assuming that home 1 is a user of operator A and home 3 is a user of operator B, without using the traffic diversion equipment in this solution, the traffic path from home 1 to home 3 is as follows: ONU of home 1 - OLT1 - metropolitan area transport network of operator A - BRAS of operator A - public network transport network - BRAS of operator B - metropolitan area transport network of operator B - OLT2 - ONU of home 3. After applying the traffic diversion equipment in this solution, Figure 3 As shown, the traffic distribution device 1 generates the following feature table record through the session message allocated by the PPPoE IP address:

[0057] The traffic distribution device 2 generates the following feature table record based on the session message allocated by the PPPoE IP address:

[0058] Through the PPPoE session feature table synchronization function between the split devices, the following feature tables are generated on both split devices 1 and 2:

[0059] When splitter device 1 receives traffic destined for home 3, it changes the destination MAC address in the Ethernet frame header to the MAC address of the ONU in home 3. Then, by checking the Layer 2 forwarding table, it finds that the MAC address of the ONU in home 3 is to be forwarded to the synchronous interface link. Therefore, splitter device 1 sends the data packet to splitter device 2. After receiving the data packet, splitter device 2 directly forwards it to the local OLT 2. In this way, the entire forwarding path is ONU in home 1—OLT 1—splitter device 1—splitter device 2—OLT 2—ONU in home 3, which greatly shortens the transmission path, improves forwarding efficiency, and enhances user service experience. Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the above embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the above embodiments, or replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A traffic processing system based on a PPPoE local traffic distribution device cluster, characterized in that: The system includes: a plurality of locally interconnected preset shunt devices, each of the preset shunt devices being connected to a corresponding network-side device; each of the preset shunt devices being further connected to at least one optical line terminal (OLT); each of the optical line terminal (OLT) being connected to at least one optical network unit (ONU) so as to connect to a terminal device through each of the optical network units (ONU); each of the preset shunt devices storing a first target PPPoE Session feature table; wherein the first target PPPoE Session feature table is a combination of the first PPPoE Session feature tables corresponding to each of the preset shunt devices; each of the first PPPoE Session feature tables includes PPPoE connection feature information initiated by a first terminal corresponding to each of the optical network units (ONU) belonging to the same preset shunt device; The first splitting device is configured to, if receiving an uplink data packet from a first optical network unit (ONU) through a first optical line terminal (OLT), extract a destination IP address from the uplink data packet; if the destination IP address exists in the first target PPPoE Session feature table and the destination IP address belongs to a second optical network unit (ONU) of a second splitting device, reconstruct the uplink data packet to obtain a reconstructed data packet; and send the reconstructed data packet to the second splitting device; The second traffic distribution device is used to send the reconstructed data message to the second optical network unit ONU through the second optical line terminal OLT.

2. The system according to claim 1, wherein: Each of the preset diversion devices includes a synchronization management module; each of the synchronization management modules is pre-configured with a synchronization interface; Each of the synchronization management modules is used to broadcast the device identification of the preset diversion device to which it belongs, so that each of the other preset diversion devices saves the device identification after listening to the device identification, until each of the preset diversion devices saves the device identifications of all the preset diversion devices; For each of the synchronization management modules, the synchronization management module is used to synchronize the corresponding first PPPoE Session feature table from each of the other synchronization management modules through the synchronization interface configured on the synchronization management module according to the device identifications of all the preset diversion devices stored in the preset diversion device to which it belongs, until the first target PPPoE Session feature table is obtained.

3. The system according to claim 2, wherein: If the designated PPPoESession feature table corresponding to the first designated offloading device is updated, the first designated synchronization management module in the first designated offloading device is configured to: Through the synchronization interface configured on the first designated synchronization management module, an update message is sent to the synchronization management module in each other preset diversion device except the first designated diversion device, so that the synchronization management module in each other preset diversion device updates the preset two-layer forwarding table according to the update message, and updates the pre-saved first target PPPoE Session feature table.

4. The system according to claim 1, wherein: The system includes: a newly added diversion device; the newly added diversion device is interconnected with a plurality of the preset diversion devices through a network; the newly added diversion device includes a newly added synchronization management module; the newly added synchronization management module is pre-configured with a newly added synchronization interface; The newly added synchronization management module is used to broadcast the newly added device identification of the newly added diversion device, so that after each of the preset diversion devices monitors the newly added device identification, it sends its corresponding first PPPoESession feature table to the newly added diversion device through the newly added synchronization interface.

5. The system according to claim 2, wherein: For each of the synchronization management modules, the synchronization management module is used to broadcast a preset first dimension active message according to a first preset period; If the designated keep-alive message sent by the second designated synchronization management module is not received, and the duration of not receiving the designated keep-alive message reaches a preset duration threshold, the first PPPoE Session feature table corresponding to the second designated diversion device is deleted from the first target PPPoESession feature table corresponding to the synchronization management module; wherein the second designated diversion device is the preset diversion device to which the second designated synchronization management module belongs.

6. The system according to claim 2, wherein: Each of the preset traffic diversion devices further stores summary data corresponding to each first PPPoE Session feature table; and for each of the synchronization management modules, the synchronization management module is configured to: Broadcasting the first summary data corresponding to the first PPPoE Session feature table generated by the local end according to a second preset period; If the designated summary data received from the third designated synchronization management module is identical to the designated existing data stored in the preset traffic diversion device to which the synchronization management module belongs, it is determined that the synchronization management module is synchronized with the third designated synchronization management module; wherein the designated existing data is the summary data corresponding to the first PPPoE session feature table previously synchronized from the third designated synchronization management module to the synchronization management module; If the designated summary data received from the third designated synchronization management module is different from the designated existing data stored in the preset diversion device to which the synchronization management module belongs, a feature table acquisition request is sent to the third designated synchronization management module, so that the third designated synchronization management module sends the second PPPoE Session feature table corresponding to the designated summary data to the synchronization management module, and updates the first PPPoE Session feature table corresponding to the designated existing data to the second PPPoE Session feature table.

7. The system according to claim 2, wherein: Multiple preset traffic diversion devices correspond to multiple broadband remote access servers (BRASs), and each of the broadband remote access servers (BRASs) stores a corresponding second target PPPoE session feature table; wherein the second target PPPoE session feature table is a combination of the first PPPoE session feature tables corresponding to all preset traffic diversion devices belonging to the broadband remote access server (BRAS); and each of the synchronization management modules is pre-configured with a synchronization management programming interface. Each of the synchronization management modules is used to obtain and save the second target PPPoE Session feature table stored in each of the broadband remote access servers BRAS through the synchronization management programming interface.

8. The system according to claim 7, characterized in that Each broadband remote access server BRAS corresponds to a different network operator.

9. The system according to claim 1, wherein: Each of the preset traffic distribution devices further includes a PPPoE Session learning module, and each of the PPPoE Session learning modules is configured to: During the PPPoE session phase, when a first uplink message is received, first information is extracted from the first uplink message, and the first information is updated into a preset cache table; wherein the first information includes: a destination MAC address, a PPPoESessionID, a vlanTag of a Layer 2 Ethernet frame header, and an IP address in an IPCP message; When a PDAT message is received, second information is extracted from the PDAT message, and the record corresponding to the second information is deleted from the preset cache table to obtain a first PPPoE Session feature table corresponding to the preset diversion device to which the PPPoE Session learning module belongs; wherein the second information includes: the destination MAC address and the PPPoESessionID.

10. A traffic processing device based on a PPPoE local traffic distribution device cluster, characterized in that: A traffic processing system based on a PPPoE local diversion device cluster comprising the traffic processing system according to any one of claims 1 to 9.

Images