Traffic processing system and equipment based on PPPoE local traffic offloading device cluster

Abstract

This invention provides a traffic processing system and device based on a PPPoE local offloading device cluster, including multiple preset offloading devices interconnected locally. Each preset offloading device stores a first target PPPoE Session feature table. When the destination IP address extracted by the first offloading device from a received uplink data packet exists in the stored first target PPPoE Session feature table, and the destination IP address belongs to a second optical network unit (ONU) belonging to a second offloading device, the uplink data packet can be directly reconstructed, and the reconstructed data packet can be sent to the second offloading device. The second offloading device can then directly send the reconstructed data packet to the corresponding second optical network unit (ONU) without going through network-side equipment, thereby shortening the network path, improving packet forwarding efficiency, and reducing the occupation of network bandwidth resources.

Description

Technical Field

[0001] This invention relates to the field of communication technology, and in particular to a traffic processing system and device based on a PPPoE local traffic offloading device cluster. Background Technology

[0002] Home broadband service is a fundamental service of major telecom operators, providing fixed-line internet access to homes. The network architecture of FTTP home broadband services typically involves a Broadband Remote Access Server (BRAS) connecting the internet to a metropolitan area network (MAN). The MAN connects to different Optical Line Terminals (OLTs). Each OLT connects to corresponding terminal devices (such as mobile phones and computers) through its own Optical Network Units (ONUs) for different homes. While some technologies provide traffic offloading solutions for local PPPoE sessions involving a single OLT to address inefficient and circuitous network paths, they lack solutions for local PPPoE sessions involving multiple operators and OLTs. This results in persistent issues of inefficient and circuitous network paths and high bandwidth consumption. Summary of the Invention

[0003] The purpose of this invention is to provide a traffic processing system and device based on a PPPoE local traffic offloading device cluster, which can shorten the network path, improve packet forwarding efficiency, and reduce the occupation of network bandwidth resources for local PPPoE session traffic of multi-carrier cross-optical line terminal OLTs.

[0004] This invention provides a traffic processing system based on a PPPoE local offloading device cluster. The system includes: multiple pre-set offloading devices that are locally interconnected, each pre-set offloading device being connected to its corresponding network-side device; each pre-set offloading device is also connected to at least one optical line terminal (OLT); each OLT is connected to at least one optical network unit (ONU) to connect to terminal devices through each ONU; each pre-set offloading device 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 pre-set offloading device; each first PPPoE Session feature table includes PPPoE connection feature information initiated by a first terminal corresponding to each ONU belonging to the same pre-set offloading device;

[0005] The first splitter is used to extract the destination IP address from the uplink data packet received from the first optical network unit (ONU) via 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 belongs to the second optical network unit (ONU) of the second splitter, the first splitter reconstructs the uplink data packet to obtain a reconstructed data packet and sends the reconstructed data packet to the second splitter. The second splitter is used to send the reconstructed data packet to the second optical network unit (ONU) via the second optical line terminal (OLT).

[0006] Furthermore, each preset traffic splitter 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 identifier of its preset traffic splitter, so that each other preset traffic splitter can hear the device identifier and save the device identifier, until each preset traffic splitter has saved the device identifiers of all preset traffic splitters; 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, based on the device identifiers of all preset traffic splitters saved in the preset traffic splitter, until the first target PPPoE Session feature table is obtained.

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

[0008] Furthermore, the system includes: a newly added traffic splitting device; the newly added traffic splitting device is interconnected with multiple preset traffic splitting devices, and the newly added traffic splitting 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 identifier of the newly added traffic splitting device, so that after each preset traffic splitting device hears the newly added device identifier, it sends its corresponding first PPPoE Session feature table to the newly added traffic splitting device through the newly added synchronization interface.

[0009] Furthermore, for each synchronization management module, the synchronization management module is used to broadcast a preset first live message according to a first preset period; if it does not receive a specified live message sent by the second specified synchronization management module, and the duration of not receiving the specified live message reaches a preset duration threshold, it deletes the first PPPoE Session feature table corresponding to the second specified switching device from the first target PPPoE Session feature table corresponding to the synchronization management module; wherein, the second specified switching device is the preset switching device to which the second specified synchronization management module belongs.

[0010] Furthermore, each preset distribution device also stores summary data corresponding to each first PPPoE Session feature table; for each synchronization management module, the synchronization management module is used to: broadcast the first summary data corresponding to the first PPPoE Session feature table generated locally according to a second preset period; if the specified summary data received from the third specified synchronization management module is the same as the specified existing data stored in the preset distribution device to which the synchronization management module belongs, it is determined that the synchronization management module and the third specified synchronization management module have been synchronized; wherein, the specified existing data is the summary data corresponding to the first PPPoE Session feature table that has been synchronized from the third specified synchronization management module to the synchronization management module in advance;

[0011] If the specified digest data received from the third specified synchronization management module is different from the specified existing data stored in the preset splitter device to which the synchronization management module belongs, a feature table retrieval request is sent to the third specified synchronization management module so that the third specified synchronization management module sends the second PPPoE Session feature table corresponding to the specified digest data to the synchronization management module and updates the first PPPoE Session feature table corresponding to the specified existing data to the second PPPoE Session feature table.

[0012] Furthermore, multiple preset traffic splitting devices correspond to multiple Broadband Remote Access Servers (BRAS), and each BRAS stores its own corresponding second target PPPoE Session feature table. The second target PPPoE Session feature table is a combination of the first PPPoE Session feature tables corresponding to all preset traffic splitting devices belonging to that 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 BRAS through the synchronization management programming interface.

[0013] Furthermore, each Broadband Remote Access Server (BRAS) corresponds to a different network operator.

[0014] Furthermore, each preset traffic splitter also includes a PPPoE Session learning module. Each PPPoE Session learning module is used to: extract first information from the first uplink packet when the first uplink packet is received during the PPPoE session phase, and update the first information to the preset cache table; wherein, the first information includes: destination MAC address, PPPoE SessionID, vlanTag of Layer 2 Ethernet frame header and IP address in IPCP packet;

[0015] 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 PPPoE Session feature table corresponding to the preset distribution device to which the PPPoE Session learning module belongs; wherein, the second information includes: destination MAC address and PPPoE SessionID.

[0016] The present invention provides a traffic processing device based on a PPPoE local traffic splitting device cluster, including the traffic processing system based on the PPPoE local traffic splitting device cluster mentioned above.

[0017] The present invention provides a traffic processing system and device based on a PPPoE local offloading device cluster, comprising multiple preset offloading devices interconnected locally. Each preset offloading device stores a first target PPPoE Session feature table. When the destination IP address extracted by the first offloading device from the received uplink data packet exists in the stored first target PPPoE Session feature table, and the destination IP address belongs to the second optical network unit (ONU) of the second offloading device, the uplink data packet can be directly reconstructed, and the reconstructed data packet can be sent to the second offloading device. The second offloading device can then directly send the reconstructed data packet to the corresponding second optical network unit (ONU) without going through network-side equipment, thereby shortening the network path, improving packet forwarding efficiency, and reducing the occupation of network bandwidth resources. Attached Figure Description

[0018] To more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the specific embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0019] Figure 1A schematic diagram of the basic network architecture for FTTH home broadband service provided in an embodiment of the present invention;

[0020] Figure 2 A schematic diagram of a traffic processing system based on a PPPoE local traffic offloading device cluster provided in an embodiment of the present invention;

[0021] Figure 3 A schematic diagram of a traffic processing system based on a PPPoE local traffic offloading device cluster provided in an embodiment of the present invention;

[0022] Figure 4 A schematic diagram of a traffic processing system based on a PPPoE local traffic offloading device cluster provided in an embodiment of the present invention;

[0023] Figure 5 A schematic diagram of a traffic processing system based on a PPPoE local traffic offloading device cluster provided in an embodiment of the present invention;

[0024] Figure 6 This is a connection diagram of a diversion device provided in an embodiment of the present invention;

[0025] Figure 7 A flowchart of PPPoE Session feature table processing is provided for an embodiment of the present invention;

[0026] Figure 8 This is a flowchart illustrating the processing logic of a local traffic splitting device, as provided in an embodiment of the present invention. Detailed Implementation

[0027] The technical solution of the present invention will be clearly and completely described below with reference to the embodiments. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0028] Home broadband service is a fundamental service of major telecom operators, providing fixed-line internet access to homes. GPON / EPON (GPON stands for Gigabit-Capable Passive Optical Network; EPON stands for Ethernet Passive Optical Network) network technology has been maturely applied to residential home internet access networks. Home users utilize FTTH / FTTR (FTTH stands for Fiber To The Home; FTTR stands for Fiber to the Room) technology, achieving gigabit high-speed bandwidth access and internet applications through Optical Network Units (ONUs) / Optical Network Terminals (ONTs). Figure 1 The diagram illustrates a basic network architecture for FTTH home broadband services. Internet data centers / cloud applications connect to optical line terminals (OLT1 and OLT2) via a Broadband Remote Access Server (BRAS) and a metropolitan area network. OLT1 connects to the optical network units (ONUs) in homes 1 and 2, respectively. OLT2 connects to the ONUs in homes 3 and 4, respectively. Each ONU connects to its corresponding computer, mobile phone, or other terminal. Figure 1 This only describes the FTTH network situation of a single operator. In the case of multiple operators, each will set up its own communication facilities according to the above network structure, including a complete set or part of the equipment from the Optical Network Unit (ONU) to the Optical Line Terminal (OLT) to the Metropolitan Area Network (MAN) to the Broadband Remote Access Server (BRAS).

[0029] PPPoE (Point-to-Point Protocol Over Ethernet) is a network tunneling protocol that encapsulates the Point-to-Point Protocol (PPP) within an Ethernet framework. It provides access authentication, session control, and accounting functions for terminals and is currently widely used by various operators in FTTH home broadband access networks. PPPoE is a point-to-point data link layer protocol that uses a Client / Server model. A PPPoE client initiates a connection request to a PPPoE server, and after session negotiation is successful, a PPPoE session is established. Figure 1In the FTTH network shown, the ONU (Online User Unit) is typically the PPPoE Client (or a home wireless router connected to the ONU can also act as the PPPoE Client), the Broadband Remote Access Server (BRAS) is the PPPoE Server, and the user's terminal is a smart terminal such as a computer or mobile phone (connected wirelessly to the ONU). The data information for home smart terminals accessing internet applications is encapsulated in the PPP packets of the PPPoE message, specifically the Information section of the PPPoE message structure. The PPPoE message structure can be found in relevant technical documents and will not be elaborated upon here. Figure 1 From a network architecture perspective, 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 users to access network center data. In this case, the access path for user business data flow is: ONU—OLT—Metropolitan Area Network—BRAS—Internet / Data Center.

[0030] With the promotion of decentralized services, Figure 1 The current network architecture and the simple use of PPPoE to carry business data are unsuitable for efficient communication and interaction at the business end. For example, in a point-to-point video communication application between Home 1 and Home 2, the video stream is encapsulated in PPP packets as IP packets. The network path for communication is: Home 1's ONU—OLT1—Metropolitan Area Network—BRAS—Metropolitan Area Network—OLT1—Home 2's ONU. Clearly, this network path is circuitous and inefficient, unfavorable for latency-sensitive business applications, and also consumes metropolitan area network bandwidth resources between the OLT and BRAS. A simpler, more direct, efficient, and secure communication path would be: Home 1's ONU—OLT1—Home 2's ONU. This is also suitable for various local business applications, such as local video services and edge cloud services. Major telecommunications manufacturers have launched optical line terminals (OLTs) that support local traffic offloading (TOF) or local traffic offloading functions. However, these functions are generally not intended for home broadband services, but rather for specific local planning services. For example, in the deployment of MEC (Mobile edge computing) edge cloud applications at the central office, Layer 2 switching of local traffic is accomplished through pre-planned VLAN (Virtual Local Area Network) and PON (Passive Optical Network) access ports.

[0031] In related technologies, a method for achieving local traffic offloading is disclosed, which establishes a forwarding table by learning and analyzing the PPPoE protocol and data packet content. This method solves the problem of local data traffic offloading for PPPoE sessions related to a single optical line terminal (OLT), namely the local traffic from home 1 to home 2 mentioned above. However, it does not explain how to ensure the offloading mechanism of local traffic among multiple OLTs.

[0032] In summary, the relevant technologies still have the following drawbacks:

[0033] 1. Each operator's network is independent and does not support cross-operator local traffic offloading;

[0034] 2. It can only support local traffic forwarding within the same optical line terminal OLT, and does not support forwarding across optical line terminal OLTs;

[0035] 3. It requires advance planning and lacks flexibility to accommodate later changes;

[0036] 4. Different manufacturers have different configuration methods, which makes management and maintenance difficult and costly.

[0037] 5. For TOF boards built into the Optical Line Terminal (OLT), the OLT needs to be upgraded; older equipment is not supported.

[0038] It's a common phenomenon in a residential community where resident A uses operator A's FTTH network, while resident B uses operator B's FTTH network. Figure 1 Assuming that Home 1 is a user of Operator A and Home 3 is a user of Operator B in the network architecture, the traffic path from Home 1 to Home 3 in the prior art is as follows: Home 1's ONU—OLT1—Operator A's metropolitan area transport network—Operator A's BRAS—public network transport network—Operator B's BRAS—Operator B's metropolitan area transport network—OLT2—Home 3's ONU. As can be seen, the traffic path is lengthy. Based on this, this invention provides a traffic processing system and device based on a PPPoE local traffic splitting device cluster. This technology can be applied to the application of PPPoE session local traffic forwarding across optical line terminal OLTs.

[0039] To facilitate understanding of this embodiment, a traffic processing system based on a PPPoE local traffic offloading device cluster disclosed in this embodiment of the invention will first be introduced, such as... Figure 2As shown, the system includes: multiple pre-set splitter devices 30 interconnected locally, each pre-set splitter device 30 connected to its corresponding network-side device; the network-side device may include a Broadband Remote Access Server (BRAS), etc.; the pre-set splitter devices 30 can be connected to the Internet through a metropolitan area network or a Broadband Remote Access Server (BRAS); at least some of the pre-set splitter devices 30 may be connected to the same network-side device; each pre-set splitter device 30 is also connected to at least one Optical Line Terminal (OLT); the OLT typically refers to a terminal device used to connect to an optical fiber trunk; each OLT is connected to at least one Optical Network Unit (ONU) to connect to a terminal device; the ONU can be understood as a device that converts optical signals into electrical signals; the terminal device may include a computer, mobile phone, etc.; in practical applications, each pre-set splitter device 30 can connect to one or more OLTs, each OLT can connect to one or more ONUs, typically each ONU corresponds to a household, and each ONU connects to a mobile phone, computer, etc. in the corresponding household.

[0040] Each preset splitter 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 splitter device 30; each first PPPoE Session feature table includes PPPoE connection feature information initiated by the first terminal corresponding to each optical network unit (ONU) belonging to the same preset splitter device 30, that is, it records the PPPoE connection feature information initiated by the first terminal corresponding to all optical network units (ONUs) 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, local ONU MAC, VLANTag in the Layer 2 Ethernet frame header (supporting single or double tags), PPPoE SessionID, and 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 in the Layer 2 Ethernet frame header is part of the Ethernet frame header and is used to mark which VLAN the data frame belongs to; PPPoE 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 equipment. For each preset traffic splitter 30, a first PPPoE Session feature table corresponding to the local end is pre-generated in the preset traffic splitter 30, which includes PPPoE connection feature information initiated by the first terminal corresponding to each optical network unit (ONU) belonging to the preset traffic splitter 30; multiple locally interconnected preset traffic splitters 30 combine the first PPPoE Session feature tables corresponding to each preset traffic splitter 30 through information synchronization to obtain a first target PPPoE Session feature table, and each preset traffic splitter 30 stores the first target PPPoE Session feature table.

[0041] The first splitter is used to extract the destination IP address from the uplink data packet received from the first optical network unit (ONU) via 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 belongs to the second optical network unit (ONU) of the second splitter, the first splitter reconstructs the uplink data packet to obtain a reconstructed data packet and sends the reconstructed data packet to the second splitter. The second splitter is used to send the reconstructed data packet to the second optical network unit (ONU) via the second optical line terminal (OLT).

[0042] The first splitter device can be any one of the multiple preset splitter devices 30; the first optical line terminal (OLT) can be any one of the at least one OLT connected to the first splitter device; the first optical network unit (ONU) can be any one of the at least one ONU connected to the first OLT; the uplink data packet is typically a PPPoE session data packet; the second splitter device is typically different from the first splitter device, the second OLT is one of the OLTs connected to the second splitter device, and the second ONU is one of the ONUs connected to the second OLT; in actual implementation, the first user sends an uplink data packet to the connected first ONU through the terminal device, which is then uploaded to the first splitter device through the connected first OLT. The first splitter device can extract the destination IP address from the received uplink data packet and match the destination IP address with the stored first target PPPoE session feature table to determine whether the destination IP address exists in the first target PPPoE session. If the Session characteristic table exists, and the destination IP address belongs to the second optical network unit (ONU) of the second splitter, indicating a need for cross-optical line terminal (OLT) transmission, the first splitter can reconstruct the uplink data packet to obtain a reconstructed data packet. Through this reconstruction, the uplink data packet initiated by the first ONU to the network-side device can be changed into a reconstructed downlink data packet initiated by the network-side device to the second ONU. This achieves the effect of the uplink data packet being routed through the network-side device before being sent by it. The first splitter can then send this reconstructed data packet to the second splitter, which can then directly send it to the second ONU via the second OLT.

[0043] This system does not require changes to the existing network infrastructure deployment, nor does it require upgrades to existing optical line terminals (OLTs) or other equipment. It only requires the deployment of a traffic splitter at the same network location as the OLT in the community access center's equipment room, such as... Figure 3 The diagram shown illustrates a traffic processing system based on a PPPoE local traffic offloading device cluster. Figure 1 Based on the system, splitter device 1 and splitter device 2 are added between optical line terminal OLT1, optical line terminal OLT2 and metropolitan area transport network, respectively.

[0044] The aforementioned traffic processing system based on a PPPoE local offloading device cluster includes multiple pre-set offloading devices that are interconnected locally. Each pre-set offloading device stores a first target PPPoE Session feature table. When the destination IP address extracted by the first offloading device from the received uplink data packet exists in the stored first target PPPoE Session feature table, and the destination IP address belongs to the second optical network unit (ONU) of the second offloading device, the uplink data packet can be directly reconstructed, and the reconstructed data packet can be sent to the second offloading device. The second offloading device can then directly send the reconstructed data packet to the corresponding second optical network unit (ONU) without going through network-side equipment, thereby shortening the network path, improving packet forwarding efficiency, and reducing the occupation of network bandwidth resources.

[0045] Furthermore, such as Figure 4 The diagram illustrates a traffic processing system based on a PPPoE local traffic offloading device cluster. This system only performs local offloading processing on user-side uplink PPPoE traffic, while requiring no processing on downlink traffic from the network side (i.e., the BRAS side). Furthermore, within the PPPoE uplink traffic, only PPPoE session phase data packets with local IP destination addresses are forwarded locally, without affecting the forwarding of other packets. The pre-configured offloading devices in this solution include a PPPoE Session learning module, a local PPPoE packet offloading 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 among the pre-configured offloading devices to support local traffic offloading functions across optical line terminal (OLT) and across operators. Figure 4 For local traffic where both the source and destination ONUs are under the same distribution device, after the header reconstruction is performed on the distribution device, it is forwarded directly locally, achieving the same effect as... Figure 4 The "return to local traffic" feature allows local traffic destined for other optical line terminals (OLTs) to be forwarded to the local distribution equipment of the destination for processing.

[0046] Each pre-configured splitter device includes a synchronization management module; each synchronization management module is pre-configured with a synchronization interface; in actual implementation, relevant administrators can specify the synchronization interface for each synchronization management module, thus enabling the feature table synchronization function. The first PPPoE Session feature table synchronization between pre-configured splitter devices can be achieved through a proprietary protocol. A suitable 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, but clarifies one mechanism for implementing the feature table synchronization protocol.

[0047] Each synchronization management module broadcasts the device identifier of its assigned preset distribution device, so that each other preset distribution device can hear and save the device identifier, until each preset distribution device has all the device identifiers of the preset distribution devices. This device identifier can also be called a device ID (Identity Document), which can be represented by the MAC address (Media Access Control Address, also known as a LAN address) of the preset distribution device. Different preset distribution devices have different device identifiers, which can be used to distinguish between different preset distribution devices. In actual implementation, for each synchronization management module, it can broadcast the device identifier of its assigned preset distribution device. Each other preset distribution device can hear and save this device identifier. Each synchronization management module will perform the process of broadcasting the device identifier of its assigned preset distribution device and listening to each other preset distribution device to hear the device identifier. Ultimately, each preset distribution device can save all the device identifiers of the preset distribution devices, for example, each preset distribution device can save a table of device IDs for the entire network of preset distribution devices.

[0048] For each synchronization management module, it synchronizes its corresponding first PPPoE Session feature table from each of the other synchronization management modules through a synchronization interface configured on the module, based on the device identifiers of all preset switching devices stored in its own preset switching device, until the first target PPPoE Session feature table is obtained. In actual implementation, after each preset switching device has stored the device identifiers of all preset switching devices, for each synchronization management module, it can synchronize the first PPPoE Session feature tables generated in each of the other preset switching devices through the synchronization interface, based on the device identifiers of all preset switching devices stored in its own preset switching device, and combine them to obtain the first target PPPoE Session feature table.

[0049] For a traffic processing system based on a PPPoE local traffic splitter cluster, the scenario is where one traffic splitter connects to multiple OLTs, meaning the local traffic splitter supports the access of multiple OLTs, such as... Figure 5The diagram illustrates a traffic processing system based on a PPPoE local traffic splitting device cluster. The splitting devices are connected to OLT1 and OLT2; OLT1 is connected to ONU1, and OLT2 is connected to ONU2. The splitting devices can automatically learn the IP allocation information during the PPPoE session reported by each optical line terminal OLT and record it in the corresponding first PPPoE Session characteristic table. For this type of cross-OLT local traffic, the splitting devices do not require the support of a synchronization management module.

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

[0051] The aforementioned first designated offloading device can be any one of the aforementioned multiple preset offloading devices; the aforementioned designated PPPoE Session feature table can be understood as the first PPPoE Session feature table generated by the first designated offloading device itself. 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 offloading device can send an update message to the synchronization management module in each of the other preset offloading devices in the network. The update message typically includes: the device identifier of the first designated offloading device, the local optical network unit (ONU) MAC belonging to the first designated offloading 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 of the other preset traffic splitting devices can update the Layer 2 forwarding table according to the update message. That is, for the added feature table record, the corresponding PPPoEClient MAC and port are added; for the deleted feature table record, the corresponding MAC is deleted from the Layer 2 forwarding table, and then the specified PPPoE Session feature table record is synchronized to the saved first target PPPoE Session feature table to synchronize and update the first target PPPoE Session feature table.

[0052] The following explains the process of updating the Layer 2 forwarding table. After reconstructing the Layer 2 frame header of the local service packet, the distribution device will forward the Layer 2 packet according to the Layer 2 forwarding mechanism, that is, forward it to its bound port according to the destination MAC address. The binding relationship between MAC and port is the Layer 2 forwarding table. The relevant Layer 2 forwarding table in the distribution device is formed through the learning and announcement of feature table records. For example, the MAC and IP of the optical network unit ONU_A are MAC_A and IP_A, and the optical network unit ONU_A belongs to distribution device A. Distribution device A learns the PPPoE session feature record of MAC_A through port A.eth1. Then, distribution device A forms forwarding table entries for A.eth1 and MAC_A. At the same time, distribution device A announces this learned local feature record to distribution device B. Distribution device B receives this announcement on port B.eth1 and forms Layer 2 forwarding table entries for MAC_A and B.eth1. When the distribution device B resolves a PPPoE service packet destined for IP_A, 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 distribution device A. After receiving it, the distribution device A forwards the packet from A.eth1 according to the Layer 2 forwarding mechanism, and finally it reaches the optical network unit ONU_A.

[0053] Furthermore, the system includes: a newly added traffic splitting device; the newly added traffic splitting device is interconnected with multiple preset traffic splitting devices, and the newly added traffic splitting 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 identifier of the newly added traffic splitting device, so that after each preset traffic splitting device hears the newly added device identifier, it sends its corresponding first PPPoE Session feature table to the newly added traffic splitting device through the newly added synchronization interface.

[0054] The aforementioned newly added traffic offloading device can be a newly added traffic offloading device, a restart of an existing traffic offloading device, or a connection that has been switched from offline to online. In actual implementation, when a new traffic offloading device is added to the system, the new synchronization management module in the new traffic offloading device can broadcast the new device identifier of the new traffic offloading device to the entire network. In this way, each preset traffic offloading device that has a network interconnection relationship with the new traffic offloading device can listen to the new device identifier and send its locally generated first PPPoE Session feature table to the new traffic offloading device. Thus, the new traffic offloading device can synchronize with the first PPPoE Session feature table of the entire network.

[0055] Furthermore, for each synchronization management module, the synchronization management module is used to broadcast a preset first live message at a first preset period; the first preset period can be set according to actual needs; the first live 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 a specified live message sent by a second specified synchronization management module is not received, and the duration of not receiving the specified live message reaches a preset duration threshold, the first PPPoE Session feature table corresponding to the second specified switching device is deleted from the first target PPPoE Session feature table corresponding to the synchronization management module; wherein, the second specified switching device is the preset switching device to which the second specified synchronization management module belongs.

[0056] The aforementioned second designated synchronization management module can be the synchronization management module of any of the aforementioned multiple preset switching devices; the aforementioned designated live message can be understood as a heartbeat packet or other form of message periodically sent by the second designated synchronization management module; the aforementioned preset duration threshold can be set according to actual needs; in actual implementation, each synchronization management module can periodically broadcast a preset first live message, and can also listen to the first live message broadcast by each other synchronization management module. For each synchronization management module, if the synchronization management module does not receive the designated live message sent by the second designated synchronization management module, and the duration reaches the preset duration threshold, it can delete the record of the first PPPoE Session feature table corresponding to the second designated switching device from the first target PPPoE Session feature table saved by the preset switching device to which the synchronization management module belongs.

[0057] Furthermore, each preset distribution device also stores summary data corresponding to each first PPPoE Session feature table; for each synchronization management module, the synchronization management module is used to: broadcast the first summary data corresponding to the first PPPoE Session feature table generated locally according to a second preset period; if the specified summary data received from the third specified synchronization management module is the same as the specified existing data stored in the preset distribution device to which the synchronization management module belongs, it is determined that the synchronization management module and the third specified synchronization management module have been synchronized; wherein, the specified existing data is the summary data corresponding to the first PPPoE Session feature table that has been synchronized from the third specified synchronization management module to the synchronization management module in advance;

[0058] The aforementioned summary data can be an extraction and summary of key core data from the first PPPoE Session feature table, with the aim of presenting key technical parameters or statistical results in a concise manner. The aforementioned second preset period can be set according to actual needs and is not limited here. The aforementioned third designated synchronization management module can be the synchronization management module in any of the aforementioned multiple preset splitting devices. In actual implementation, each synchronization management module can periodically broadcast the first summary data corresponding to the first PPPoE Session feature table generated on its own end, and can also listen to the first summary data broadcast by each other synchronization management module. For each synchronization management module, if the designated 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 that was previously synchronized from the third designated synchronization management module to the synchronization management module, it indicates that the synchronization management module has synchronized with the third designated synchronization management module.

[0059] If the specified digest data received from the third designated synchronization management module differs from the specified existing data stored in the preset distribution device to which the synchronization management module belongs, the synchronization management module sends a feature table retrieval request to the third designated synchronization management module. This prompts the third designated synchronization management module to send the second PPPoE Session feature table corresponding to the specified digest data to the synchronization management module, updating the first PPPoE Session feature table corresponding to the specified existing data to the second PPPoE Session feature table. If the specified digest data received by the synchronization management module from the third designated synchronization management module is inconsistent with the digest data corresponding to the first PPPoE Session feature table pre-synchronized from the third designated synchronization management module to the synchronization management module, the synchronization management module can send a feature table retrieval request to the third designated synchronization management module to request the third designated synchronization management module to send the second PPPoE Session feature table corresponding to the specified digest data, thereby updating the record in the first PPPoE Session feature table corresponding to the specified existing data stored locally.

[0060] Furthermore, multiple preset traffic splitting devices correspond to multiple Broadband Remote Access Servers (BRAS), and each BRAS stores its own corresponding second target PPPoE Session feature table. The second target PPPoE Session feature table is a combination of the first PPPoE Session feature tables corresponding to all preset traffic splitting devices belonging to that 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 BRAS through the synchronization management programming interface.

[0061] The aforementioned Broadband Remote Access Server (BRAS) is a network device specifically designed for broadband access management. Located between the user access network and the operator's core network, it provides functions such as user access authentication, authorization, billing, address allocation, and traffic management. In actual implementation, the number of preset splitter devices may be the same as or different from the Broadband Remote Access Server (BRAS). That is, a Broadband Remote Access Server (BRAS) may connect to only one preset splitter device, or it may connect to a portion of multiple preset splitter devices. For example, a Broadband Remote Access Server (BRAS) may connect to one, two, or three preset splitter devices, etc. The specific configuration can be based on actual needs and is not limited here. The Broadband Remote Access Server (BRAS) can be a BRAS of operator A, a BRAS of operator B, etc. Each Broadband Remote Access Server (BRAS) stores its own corresponding second target PPPoE Session feature table. The second target PPPoE Session feature table is specifically a combination of the first PPPoE Session feature tables corresponding to all preset splitter devices belonging to the Broadband Remote Access Server (BRAS). For example, if the Broadband Remote Access Server (BRAS) is a BRAS of operator A, and this operator A BRAS connects to two preset splitter devices through the operator A metropolitan area network, then the operator A BRAS stores a combination of the first PPPoE Session feature tables corresponding to these two preset splitter devices.

[0062] In this embodiment, each synchronization management module is pre-configured with a synchronization management programming interface. Each synchronization management module can use this interface to synchronize a second target PPPoE Session characteristic table from each Broadband Remote Access Server (BRAS). For example, if multiple Broadband Remote Access Servers (BRASs) are operator A's BRAS and operator B's BRAS, a pre-configured splitter device A can synchronize the second target PPPoE Session characteristic table stored in operator A's BRAS and the second target PPPoE Session characteristic table stored in operator B's BRAS, ultimately forming a complete first target PPPoE Session characteristic table. The significance of synchronizing from each Broadband Remote Access Server (BRAS) is that the data stored in each BRAS is used as the standard; that is, the user can use the synchronization management programming interface to choose whether to generate or overwrite the first target PPPoE Session characteristic table using the second target PPPoE Session characteristic table. Furthermore, this synchronization management programming interface can also provide read / write configuration operations on the characteristic table using SNMP or Netconf management protocols.

[0063] In addition, in this embodiment, each synchronization management module can also support manual maintenance of the feature table by adding and deleting entries, allowing users to control local traffic distribution for specific PPPoE client devices as needed. Users can also configure the default aging time of the PPPoE session feature table through the synchronization management module.

[0064] The aforementioned synchronization management module provides extended processing capabilities for the first PPPoE Session feature table, and these capabilities can be expanded as needed. It supports automatic synchronization between multiple split-line devices across optical line terminals (OLTs) and across different operators via the feature table synchronization protocol. It can also synchronize records from the current second target PPPoE Session feature table from the Broadband Remote Access Server (BRAS) by providing a synchronization management programming interface. Manual maintenance of the feature table, including adding and deleting entries, is also supported, allowing users to control local split-line traffic on specific PPPoE client devices as needed, and to configure the default aging time of the PPPoE session feature table.

[0065] 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.

[0066] In practical applications, if the uplink of each Optical Line Terminal (OLT) needs to be independent, such as in cross-carrier scenarios where the splitting devices require independent management and are deployed in different central office rooms, the OLTs of different carriers connect to their respective splitting devices, and then access their respective network-side devices through the splitting devices. Figure 6 The diagram shows a connection schematic of a traffic splitting device. The splitting devices in the diagram use a ring topology, but other topologies can also be used, such as chain topologies or fully connected topologies. Considering the requirements for network connectivity redundancy protection and fault tolerance, this solution uses a ring topology as an example. Loop prevention is guaranteed by Layer 2 or Layer 3 protocols. For example, Layer 2 can use STP (Spanning Tree Protocol) to block redundant links to prevent loops. For details, please refer to relevant technologies; they will not be elaborated here. The links between the splitting devices are used for both synchronizing the first PPPoE Session feature table and transmitting local data traffic.

[0067] Furthermore, such as Figure 4 As shown, each preset traffic splitter also includes a PPPoE Session learning module. Each PPPoE Session learning module is used to: extract first information from the first uplink packet when the first uplink packet is received during the PPPoE session phase, and update the first information to the preset cache table; wherein, the first information includes: destination MAC address, PPPoE SessionID, vlanTag of Layer 2 Ethernet frame header and IP address in IPCP packet; the destination MAC address can be understood as the MAC address of the destination optical network unit (ONU) to which the first uplink packet is to be sent; the IP address in the IPCP packet can be understood as the IP address assigned to the destination optical network unit (ONU).

[0068] When a PDAT (Protocol Data Allocation Table) 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 PPPoE Session feature table corresponding to the preset traffic distribution device to which the PPPoE Session learning module belongs. The second information includes: destination MAC address and PPPoE SessionID. The PDAT message is a special message in the PPPoE protocol used to notify network devices to terminate the current PPPoE session.

[0069] like Figure 7The diagram illustrates a PPPoE Session signature table processing flowchart. It describes how PPPoE Session signature table entries are added or updated using PPP packets obtained from the NCP (Network Control Protocol) IP address during the PPPoE session (updates may occur when a historical entry with the specified MAC address already exists in the signature table). Entries are deleted using PADT packets indicating PPPoE termination. Additionally, similar to ARP learning, this PPPoE Session signature table has a default aging time. Upon receiving a PPPoE Session phase packet or a PPPoE Keep-alive LCP (Link Control Protocol) keep-alive packet, the aging time of the PPPoE Session signature table is refreshed. After the aging time expires, the relevant PPPoE Session signature table entries are deleted.

[0070] Specifically, such as Figure 7As shown, the PPPoE Session learning module first extracts the Layer 2 packet (corresponding to the first uplink packet mentioned above) from the received packet. It then executes the first conditional check, determining whether the Layer 2 packet meets the following conditions: source MAC = BRAS MAC, Ether_type = 0x8864, PPPoE frame header code = 0x00, PPP header protocol = 0x8021, and IPCP code = 2 / ack. If these conditions are met, it can be considered that the received packet is a PPP packet obtained through the NCP IP address in the PPPoE session phase. At this point, the destination MAC address, PPPoE SessionID, Layer 2 Ethernet frame header vlanTag, and IP address in the IPCP packet can be extracted from the Layer 2 packet, and this information is added to or updated in the preset cache table. Next, it executes the second conditional check, determining whether the Layer 2 packet meets the following conditions: Ether_type = 0x8864 and PPPoE frame header code = 0xa7. If this condition is met, it is confirmed that a PDAT packet has been received, and the destination MAC address, PPPoE... The SessionID is used to delete the corresponding record in the preset cache table, ultimately obtaining the first PPPoE Session feature table corresponding to the preset traffic distribution device to which the PPPoE Session learning module belongs. Subsequent PPPoE local traffic packet processing can then proceed. If a Layer 2 packet does not meet the first judgment condition and is confirmed as a PPP packet obtained from a non-NCP IP address, the second judgment condition is directly executed. If the second judgment condition is not met and is confirmed as a non-PDDT packet, the PPPoE local traffic packet processing process is then executed. In this embodiment, the fields to be extracted are more concise, thus helping to improve the efficiency and accuracy of traffic processing. By learning the NCP IP address allocation of PPP IPCP packets during the PPPoE session phase and the PADT packets terminating PPPoE, the IP-MAC-PPPoESessionID-vlanTag entries in the first PPPoE Session feature table are automatically maintained, providing a data foundation for the identification of PPPoE local traffic.

[0071] like Figure 4 As shown, each preset traffic splitting device also includes a local PPPoE packet splitting module. This local PPPoE packet splitting module enables the local traffic carried on PPPoE to be forwarded directly on the local side. That is, during the PPPoE session, the service traffic with both source and destination on the local side is switched locally through the local traffic splitting device of this solution, without having to go uplink to the core side of the Broadband Remote Access Server (BRAS).

[0072] This traffic splitter will not disrupt the control functions of the PPP protocol, including the discovery phase of PPPoE link establishment, the Link Control Protocol (LCP), Network Control Protocol (NCP), and authentication protocols during the PPP session. It only modifies the header encapsulation fields of PPPoE Ethernet frames used for data exchange during the PPPoE session phase. Figure 8 The flowchart shown illustrates the logic replacement process for a local traffic splitter. The reconstructed PPPoE Layer 2 message includes:

[0073] 1. Source MAC = BRAS MAC;

[0074] 2. Destination MAC = PPPoE Client MAC matching the destination IP in the first target PPPoE Session feature table;

[0075] 3. VLAN Tag = VLANTag of the PPPoE Layer 2 frame matching the destination IP in the first target PPPoE Session feature table;

[0076] 4. PPPoE SessionID = PPPoE Session ID matching the destination IP in the first target PPPoE Session feature table;

[0077] The effect of the above processing is that the uplink PPPoE session data packets initiated by the source ONU to the BRAS are changed into downlink PPPoE session data packets initiated by the BRAS to the destination ONU. In other words, the effect is the same as the PPPoE session data packets being routed through the BRAS and then sent by the BRAS. Figure 8 The specific process is as follows: The local PPPoE packet splitting module extracts the Layer 2 packets and executes the first judgment condition, namely, whether the Layer 2 packets meet 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 can be considered a PPPoE data packet. At this time, the destination IP address of the PPP data packet can be extracted from the Layer 2 packet, and it is determined whether the destination IP address exists in the stored first target PPPoE Session feature table. If it exists, the Layer 2 packet can be reconstructed and general Layer 2 forwarding processing can be performed. If the Layer 2 packet does not meet the first judgment condition, it is confirmed that it is not a PPPoE data packet, or the destination IP address does not exist in the stored first target PPPoE Session feature table, then general Layer 2 forwarding processing can be performed according to existing technology. In this way, the traffic within the cell flows directly within the cell network without detouring through the remote BRAS.

[0078] like Figure 4 As shown, each preset traffic splitting device also includes a Layer 2 switching module. This Layer 2 switching module can be a general-purpose Layer 2 switching module, used to receive output packets from the local PPPoE packet splitting module and perform Layer 2 forwarding. The implementation mechanism of this system can be implemented through underlying hardware ASIC (Application Specific Integrated Circuit) or FPGA (Field Programmable Gate Array) chips, or through software including SDN (Software-Defined Networking) controllers, network management systems, or specialized application software such as PPPoE proxies or forwarding gateways; the implementation logic is the same.

[0079] The aforementioned traffic processing system based on a PPPoE local traffic splitting device cluster elucidates a technology that supports local data traffic splitting in PPPoE sessions between multiple splitting devices deployed across OLTs by multiple operators. This solution not only breaks the remote, roundabout transportation of PPPoE local data packets from user terminals to the Broadband Remote Access Server (BRAS), but also deploys the local traffic splitting devices at the central office of the Optical Line Terminal (OLT), allowing 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 support the synchronization of PPPoE session information between devices and support the identification of local traffic across operators and OLTs, truly achieving the effect of local traffic transfer. This provides support for the construction of modern digital smart network communities with multi-operator convergence in local networks. This solution proposes a proprietary local traffic splitting device that combines hardware and software, applicable not only to PON networks but also to any other wireless or wired access network using the PPPoE protocol, facilitating improved efficiency of local interconnection traffic transmission initiated by terminal devices.

[0080] The present invention provides a traffic processing device based on a PPPoE local traffic splitting device cluster, including the traffic processing system based on the PPPoE local traffic splitting device cluster mentioned above.

[0081] By deploying the offloading 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) deployment, interactive forwarding can be directly achieved within the local cell area, improving the end-to-end transmission efficiency of local service traffic, reducing transmission latency, reducing packet loss probability, and optimizing service quality. In particular, it enhances the user experience for latency-sensitive applications such as video interaction.

[0082] by Figure 1 Assuming Home 1 is a user of Operator A and Home 3 is a user of Operator B, without the traffic splitting equipment in this solution, the traffic path from Home 1 to Home 3 is as follows: Home 1's ONU—OLT1—Operator A's metropolitan area network—Operator A's BRAS—public network transmission network—Operator B's BRAS—Operator B's metropolitan area network—OLT2—Home 3's ONU. After applying the traffic splitting equipment in this solution, such as... Figure 3 As shown, the traffic splitter 1 generates the following feature table record based on the session packets allocated by the PPPoE IP address:

[0083]

[0084] The traffic splitter 2 generates the following feature table record based on the session packets allocated by the PPPoE IP address:

[0085]

[0086] Through the PPPoE session characteristic table synchronization function between the splitter devices, the following characteristic tables are formed on both splitter device 1 and splitter device 2:

[0087]

[0088] When splitter 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 destined for home 3 should be forwarded to the synchronization interface link. Therefore, splitter 1 sends the data packet to splitter 2. After receiving it, splitter 2 forwards it directly to the local OLT2. In this way, the entire forwarding path is ONU of home 1 — OLT1 — splitter 1 — splitter 2 — OLT2 — ONU of home 3, which greatly shortens the transmission path, improves forwarding efficiency, and enhances the user's service experience.

[0089] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features; and these modifications or substitutions 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 offloading device cluster, characterized in that, The system includes: multiple pre-set traffic splitting devices that are locally interconnected, each pre-set traffic splitting device being connected to its corresponding network-side device; each pre-set traffic splitting device is also connected to at least one optical line terminal (OLT); each OLT is connected to at least one optical network unit (ONU) to connect to terminal devices through each ONU; each pre-set traffic splitting device 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 pre-set traffic splitting device; each first PPPoE Session feature table includes PPPoE connection feature information initiated by a first terminal corresponding to each ONU belonging to the same pre-set traffic splitting device; If the first splitter receives an uplink data packet from a first optical network unit (ONU) via a first optical line terminal (OLT), it extracts the 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) belonging to the second splitter, it reconstructs the uplink data packet to obtain a reconstructed data packet and sends the reconstructed data packet to the second splitter. The second splitter is used to send the reconstructed data packet to the second optical network unit (ONU) via the second optical line terminal (OLT).

2. The system according to claim 1, characterized in that, Each of the preset traffic splitting 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 identifier of its own preset distribution device, so that each other preset distribution device can hear the device identifier and save the device identifier, until each preset distribution device has saved the device identifiers of all preset distribution 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, based on the device identifiers of all the preset switching devices stored in the preset switching device, until the first target PPPoE Session feature table is obtained.

3. The system according to claim 2, characterized in that, If the specified PPPoESession feature table corresponding to the first specified traffic splitter is updated, the first specified synchronization management module in the first specified traffic splitter is used for: Through the synchronization interface configured on the first designated synchronization management module, update messages are sent to the synchronization management modules in each of the other preset split devices besides the first designated split device, so that the synchronization management modules in each of the other preset split devices update the preset Layer 2 forwarding table and update the pre-saved first target PPPoE Session feature table according to the update messages.

4. The system according to claim 1, characterized in that, The system includes: a newly added traffic splitting device; the newly added traffic splitting device is interconnected with multiple preset traffic splitting devices, and the newly added traffic splitting 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 identifier of the newly added traffic splitting device, so that after each of the preset traffic splitting devices hears the newly added device identifier, it sends its corresponding first PPPoESession feature table to the newly added traffic splitting device through the newly added synchronization interface.

5. The system according to claim 2, characterized in that, For each of the synchronization management modules, the synchronization management module is used to broadcast a preset first-dimensional live message according to a first preset period; If no specified liveness message is received from the second specified synchronization management module, and the duration of not receiving the specified liveness message reaches a preset duration threshold, the first PPPoE Session feature table corresponding to the second specified switching device is deleted from the first target PPPoE Session feature table corresponding to the synchronization management module; wherein, the second specified switching device is the preset switching device to which the second specified synchronization management module belongs.

6. The system according to claim 2, characterized in that, Each of the preset traffic splitting devices also stores summary data corresponding to each first PPPoE Session feature table; for each of the synchronization management modules, the synchronization management module is used for: Broadcast the first summary data corresponding to the first PPPoE Session feature table generated on this end according to the second preset period; If the specified digest data received from the third specified synchronization management module is the same as the specified existing data stored in the preset distribution device to which the synchronization management module belongs, it is determined that the synchronization management module and the third specified synchronization management module have been synchronized; wherein, the specified existing data is the digest data corresponding to the first PPPoE Session feature table in the synchronization management module that has been synchronized from the third specified synchronization management module to the synchronization management module in advance; If the specified digest data received from the third specified synchronization management module is different from the specified existing data stored in the preset distribution device to which the synchronization management module belongs, a feature table retrieval request is sent to the third specified synchronization management module, so that the third specified synchronization management module sends the second PPPoE Session feature table corresponding to the specified digest data to the synchronization management module, and updates the first PPPoE Session feature table corresponding to the specified existing data to the second PPPoE Session feature table.

7. The system according to claim 2, characterized in that, Multiple preset traffic splitting devices correspond to multiple Broadband Remote Access Servers (BRAS). Each BRAS stores its own corresponding second target PPPoE Session feature table. The second target PPPoE Session feature table is a combination of the first PPPoE Session feature tables corresponding to all preset traffic splitting devices belonging to the BRAS. Each synchronization management module 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 of the Broadband Remote Access Servers (BRAS) corresponds to a different network operator.

9. The system according to claim 1, characterized in that, Each of the preset traffic splitting devices also includes a PPPoE Session learning module, and each PPPoE Session learning module is used for: During the PPPoE session, when the first uplink packet is received, the first information is extracted from the first uplink packet and updated to the preset cache table; wherein, the first information includes: destination MAC address, PPPoESessionID, vlanTag of Layer 2 Ethernet frame header and IP address in IPCP packet. 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 the first PPPoE Session feature table corresponding to the preset traffic splitting device to which the PPPoE Session learning module belongs; wherein, the second information includes: the destination MAC address and the PPPoE SessionID.

10. A traffic processing device based on a PPPoE local traffic splitting device cluster, characterized in that, The system includes the traffic processing system based on a PPPoE local offloading device cluster as described in any one of claims 1-9.

Images