Patent Description:
With the continuous development of high-value services with large bandwidth, low latency and strong interaction, edge computing has attracted the attention of operators. Access computer room is the main location for edge computing deployment. At this location, according to the existing wired broadband access network architecture, the edge computing server may need to be accessed as a dedicated line user with a fixed IP address, which is often different from Virtual Local Area Network (VLAN) and Internet Protocol address (IPA) network segments of end users. Furthermore, users under the same access device are often horizontally isolated. Therefore, even if the edge computing server and the users are in the same VLAN and IP network segment, they cannot directly perform layer-<NUM> communication, but need to perform layer-<NUM> communication through BRAS (Broadband Remote Access Server).

In addition, Point-to-Point Protocol over Ethernet (PPPoE) access is widely used by end users in the existing network, and PPPoE ends in BRAS. In this way, even if a customer premise equipment (CPE) and an edge computing server are both directly connected to an optical line terminal (OLT), the user and the edge computing server can interact only through BRAS. Users make detours in accessing Mobile Edge Computing Application Server (MEC app server), wasting the link bandwidth from OLT to BRAS/SR. Meanwhile, with the increase of paths, the delay and packet loss may increase, affecting the quality of service experience.

<CIT> provides a system in which addition of a network facility due to an increase in traffic is reduced and mobility for traffic offloading is implemented. The system provides a switch between a first network (CN) and a second network (PDN) and offloading determination means that determines whether or not to offload traffic for the first network, and configures an offload path to bypass the first network for the switch when the offloading is performed. When the traffic is offloaded, the switch forwards a packet to be offloaded to the offload path.

In <CIT>, a traffic offloading function (TOF) of a mobile edge computing (MEC) platform uses a traffic forwarding table and a location database updated by monitoring control plane messages. User plane traffic in a default bearer passes through an extended TOF where the IP packets retrieved from a General Packet Radio Service Tunneling Protocol (GTP) tunnel are forwarded following a policy that is created by detecting (or sniffing) control plane messages exchanged over the S1-MME interface. An additional entity, a location database, is responsible for tracking a location of a UE and other hosts in the mobile network. The location database can be used to guide the forwarding policy creation in an absence of the control plane messages.

This invention is defined by the appended claims. In view of the above technical problems, according to some embodiments of the present invention, a traffic processing method is provided, including: determining whether an upstream traffic message is local traffic; and performing layer-<NUM> forwarding for the upstream traffic message according to a forwarding table stored locally in response to the upstream traffic message being local traffic, wherein determining whether the upstream traffic message is local traffic comprises: determining whether a destination IP of the upstream traffic message matches IP information in the forwarding table; wherein the IP information in the forwarding table is IP information of a device directly connected to the TOF or directly connected to a layer-<NUM> access device to which the TOF is connected or belongs determining that the upstream traffic message is local traffic in response to a match between the destination IP of the upstream traffic message and the IP information in the forwarding table; and determining that the upstream traffic message is not local traffic in response to no match between the destination IP of the upstream traffic message and the IP information in the forwarding table.

According to some embodiments of the present invention, a Traffic Offload Function (TOF) is also provided, including an IP forwarding module for upstream local traffic; where the IP forwarding module for upstream local traffic is configured to determine whether an upstream traffic message is local traffic, and perform layer-<NUM> forwarding for the upstream traffic message according to a forwarding table stored locally in response to the upstream traffic message being local traffic, wherein the IP forwarding module for upstream local traffic is further configured to:determine whether a destination IP of the upstream traffic message matches IP information in the forwarding table; wherein the IP information in the forwarding table is IP information of a device directly connected to the TOF or directly connected to a layer-<NUM> access device to which the TOF is connected or belongs; determine that the upstream traffic message is local traffic in response to a match between the destination IP of the upstream traffic message and the IP information in the forwarding table; and determine that the upstream traffic message is not local traffic in response to no match between the destination IP of the upstream traffic message and the IP information in the forwarding table.

According to some embodiments of the present invention, a layer-<NUM> access device is also provided, including the TOF described above.

According to some embodiments of the present invention, a traffic processing system is also provided, including a layer-<NUM> access device and the TOF described above.

Additional features and advantages of the present invention will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by practice of the present invention. The objects and other advantages of the present invention can be realized and obtained by the structures pointed out in the description, claims and drawings.

The drawings are provided for a further understanding of the technical schemes of the present application, and constitute a part of the description. The drawings and the embodiments of the present application are used to explain the technical schemes of the present application, and do not constitute a restriction on the technical schemes of the present invention.

Objects, technical schemes and advantages of the present invention will be clearer from a detailed description of embodiments of the present invention in conjunction with the drawings. It is to be noted that if not in collision, the embodiments and features therein in the present application may be combined with each other.

The steps shown in the flowcharts of the drawings may be performed in a computer system, such as a set of computer-executable instructions. Also, although a logical order is shown in the flowcharts, in some cases, the steps shown or described may be performed in a different order than here.

<FIG> is a schematic diagram of communication between user side equipment and MEC APP server through BRAS in existing networking. As shown in <FIG>, a customer premise equipment (CPE) is directly connected to an Optical Line Terminal (OLT) through a HGU (Home Gateway Unit), and an edge computing server is also directly connected to the OLT, but the user and the edge computing server can interact only through BRAS, which not only wastes the link bandwidth from OLT to BRAS/SR, but also increases the delay and packet loss with the increase of paths, affecting the quality of service experience.

Therefore, according to some embodiments of the present invention, a traffic processing method and a related device are provided, which can realize local traffic offloading on a layer-<NUM> access device, so as to save the link bandwidth from the layer-<NUM> access device, such as OLT, to BRAS/SR, and keep the existing network architecture unaffected.

<FIG> is a flowchart of a traffic processing method according to an embodiment of the present invention, which is applied to a Traffic Offload Function (TOF). As shown in <FIG>, the method includes steps of S201 and S202.

At S201, whether the upstream traffic message is local traffic is determined.

At S202, layer-<NUM> forwarding is performed for the upstream traffic message according to a forwarding table stored locally when the upstream traffic message is local traffic.

In some embodiments, the upstream traffic message is switched to a Broadband Remote Access Server (BRAS) or a Service Router (SR) when the upstream traffic message is not local traffic.

In some embodiments, determining whether the upstream traffic message is local traffic includes:.

In some embodiments, before determining whether the upstream traffic message is local traffic, the method further includes:.

In some embodiments, the forwarding table includes a user forwarding table and a server forwarding table.

The user forwarding table includes user IP information, which is IP information of a user side equipment directly connected to a layer-<NUM> access device to which the TOF is connected or belongs; and the user forwarding table also includes at least one of the following information corresponding to the user IP information:
session type, PPPoE session ID, access port, layer-<NUM> encapsulation information, session state, local traffic value, session time, BRAS/SR MAC.

The server forwarding table includes server IP information, which is IP information of a server device directly connected to the TOF or directly connected to the layer-<NUM> access device to which the TOF belongs; and the server forwarding table also includes at least one of the following information corresponding to the server IP information:
session type, PPPoE session ID, access port, layer-<NUM> encapsulation information, session state, local traffic value, session time, BRAS/SR MAC.

The determining whether the destination IP of the upstream traffic message matches the IP information in the forwarding table includes:.

In some embodiments, establishing the forwarding table includes:.

In some embodiments, the method further includes:.

In some embodiments, performing layer-<NUM> forwarding for the upstream traffic message according to the forwarding table stored locally includes:
modifying a header of layer-<NUM> encapsulation of the upstream traffic message according to the forwarding table stored locally, and sending the modified upstream traffic message, including:.

In some embodiments, if the traffic message belongs to a PPPoE session, PPPoE session encapsulation is added to the header of the layer-<NUM> encapsulation of the modified upstream traffic message, and then the modified upstream traffic message is sent according to the access port.

The destination device corresponding to the destination IP of the upstream traffic message and directly connected to the TOF is a mobile edge computing application server (MEC APP Server) or an optical line terminal (OLT).

The destination device directly connected to the layer-<NUM> access device to which the TOF belongs is a MEC APP Server or a home gateway unit (HGU).

<FIG> is a schematic structural diagram of a Traffic Offload Function (TOF) according to an embodiment of the present invention. As shown in <FIG>, the TOF includes:.

In some embodiments, the IP forwarding module for upstream local traffic is further configured to switch the upstream traffic message to a Broadband Remote Access Server (BRAS) or a Service Router (SR) when the upstream traffic message is not local traffic.

In some embodiments, the IP forwarding module for upstream local traffic is configured to determine whether a destination IP of the upstream traffic message matches IP information in the forwarding table; where the IP information in the forwarding table is IP information of a device directly connected to the TOF or directly connected to a layer-<NUM> access device to which the TOF is connected or belongs;.

In some embodiments, the TOF also includes a user session management module.

The user session management module is configured to establish, update or revoke the forwarding table, including:.

The IP forwarding module for upstream local traffic is configured to determine whether the destination IP of the upstream traffic message matches the server IP information in the server forwarding table when the upstream traffic message is a traffic message sent by user side; and
determine whether the destination IP of the upstream traffic message matches the user IP information in the user forwarding table when the upstream traffic message is a traffic message sent by server side.

In some embodiments, the IP forwarding module for upstream local traffic is configured to modify a header of layer-<NUM> encapsulation of the upstream traffic message according to the forwarding table stored locally and send the modified upstream traffic message, including:.

In some embodiments, the IP forwarding module for upstream local traffic is further configured to, if the traffic message belongs to a PPPoE session, add PPPoE session encapsulation to the header of the layer-<NUM> encapsulation of the modified upstream traffic message, and then send the modified upstream traffic message according to the access port.

<FIG> is a flowchart of a traffic processing method according to another embodiment of the present invention. This embodiment is applied to the networking diagram shown in <FIG>. As shown in <FIG>, a Traffic Offload Function (TOF) is configured in a layer-<NUM> access device.

In this embodiment, the layer-<NUM> access device takes OLT as an example, and the layer-<NUM> access device may also be other access devices such as DSLAM.

The method includes steps of S401, S <NUM> and S403.

At S401, the TOF determines whether an upstream traffic message is local traffic.

The local traffic refers to the traffic of the upstream traffic message where the destination device corresponding to the destination IP is directly connected to the OLT. As shown in <FIG>, when the OLT receives an upstream traffic message sent from HGU and the destination device corresponding to destination IP is MEC APP Server directly connected to the OLT, the upstream traffic message is local traffic. In the same way, when the OLT receives an upstream traffic message sent from MEC APP Server and the destination device corresponding to destination IP is HGU directly connected to the OLT, the upstream traffic message is also local traffic. When the destination device corresponding to the destination IP is not directly connected to the OLT, the upstream traffic message is not local traffic, and layer <NUM> switching is performed according to the original processing to BRAS or SR for further processing.

Specifically, the local traffic refers to the traffic between users and MEC APP server. MEC APP server and OLT are connected through layer-<NUM>, directly or through a layer <NUM> switch. Meanwhile, MEC APP server and OLT are generally deployed in the same computer room. In addition, users can access MAN & Internet through BRAS device, which will also generate traffic. To distinguish these two types of traffic, the traffic between users and MEC APP server is generally called local traffic, and the traffic between users and MAN & Internet is called large network traffic.

The TOF includes two sub-modules: a user session management module and an IP forwarding module for upstream local traffic.

At S402, layer-<NUM> forwarding is performed for the upstream traffic message according to the forwarding table stored locally when the upstream traffic message is local traffic.

The user session management module can establish, update or revoke a forwarding table (session table) by various modes, for example:.

The forwarding table may be a table, and IP information in the forwarding table is IP information of a device directly connected to the TOF or directly connected to a layer-<NUM> access device to which the TOF is connected or belongs. The forwarding table also includes at least one of the following information corresponding to the IP information: session type, PPPoE session ID, access port, layer-<NUM> encapsulation information, session state, local traffic value, session time, BRAS/SR MAC.

In some embodiments, the forwarding table may also include a user forwarding table and a server forwarding table.

The user forwarding table includes user IP information, which is IP information of a user side equipment directly connected to the layer-<NUM> access device to which the TOF is connected or belongs. In this embodiment, the user IP information is HGU IP.

The user forwarding table also includes at least one of the following information corresponding to the user IP information:
session type, PPPoE session ID, access port, layer-<NUM> encapsulation information, session state, local traffic value, session time, BRAS/SR MAC.

The server forwarding table includes server IP information, which is IP information of a server device directly connected to the TOF or directly connected to the layer-<NUM> access device to which the TOF belongs. In this embodiment, the server IP information is MEC APP Server IP.

The server forwarding table also includes at least one of the following information corresponding to the server IP information:
session type, PPPoE session ID, access port, layer-<NUM> encapsulation information, session state, local traffic value, session time, BRAS/SR MAC.

The meanings of the fields in the user forwarding table are as follows:.

In addition, the user session management module can also automatically listen or learn data messages through PPPoE/DHCP, establish and maintain an accessed PPPoE/IpoE (IP over Ethernet) user table, and notify the IP forwarding module for upstream local traffic to form a user forwarding table; and establish and maintain a server table for static IP access through manual assignment by administrators and ARP (Address Resolution Protocol) listening, and notify the IP forwarding module for upstream local traffic to form a server host forwarding table.

The user table and user forwarding table contain information such as user IP address, user MAC, PPPoE and IPoE session information, VLAN, access port and gateway MAC. The server table and server forwarding table contain information such as server IP address, VLAN, access port, gateway MAC.

In some embodiment, performing layer-<NUM> forwarding for the upstream traffic message according to the forwarding table stored locally includes:
stripping the original header of layer-<NUM> encapsulation of the packet, adding a new layer-<NUM> header according to the matched user forwarding table or server forwarding table, using a user MAC as a destination MAC or filling in the destination MAC by a server, replacing a source MAC with a gateway MAC (that is, BRAS/SR MAC) in the table entries; adding VLAN tag, adding PPPoE session encapsulation if the packet belongs to a PPPoE session; and sending the packet according to the access port in the matching table entries after the layer-<NUM> encapsulation conversion processing is completed. In this way, packets received by HGU and MEC APP Server are identical with packets from BRAS/SR. In other words, the TOF simulates the layer-<NUM> forwarding function of BRAS or SR, which is completely transparent to HGU and MEC APP Server. Meanwhile, TOF may only intercepts and processes local data traffic, and the user management and layer-<NUM> forwarding functions of BRAS are basically unaffected, which is also completely transparent to BRAS&SR, requiring no changes in functions, configuration and resource planning. Therefore, according to the method and the system of the present invention, the traffic of local users accessing the local edge computing server can be well offloaded, so that the traffic does not need to be forwarded through BRAS or SR, thus shortening the forwarding path, saving the bandwidth and indirectly improving the quality of user experience.

In some embodiments, the IP forwarding module for upstream local traffic analyzes the upstream traffic message from HGU or MEC APP server, extracts the destination IP, and matches the destination IP with the server forwarding table or user forwarding table. If there is a match between the destination IP and the server forwarding table or user forwarding table, it indicates that the traffic is local traffic, which needs to be offloaded and forwarded locally; and if there is no match between the destination IP and the server forwarding table or user forwarding table, it indicates that the traffic is not local traffic, and layer <NUM> switching is performed according to the original processing to BRAS or SR for further processing.

At S403, the upstream traffic message is switched to the BRAS or SR when the upstream traffic message is not local traffic.

That is, layer-<NUM> forwarding is performed for the local traffic and layer-<NUM> transparent transmission is performed for the large network traffic, which is equivalent to layer-<NUM> forwarding for local traffic by BRAS/SR being moved down to an access device (such as OLT). Therefore, this module function is also called gateway proxy (GW proxy) function.

According to the technical schemes of the embodiments of the present invention, TOF may only intercepts and processes local data traffic, and the user management and layer-<NUM> forwarding functions of BRAS are basically unaffected, which is also completely transparent to BRAS&SR, requiring no changes in functions, configuration and resource planning. Therefore, according to the method and the system of the present invention, the traffic of local users accessing the local edge computing server can be well offloaded, so that the traffic does not need to be forwarded through BRAS or SR, thus shortening the forwarding path, saving the bandwidth and indirectly improving the quality of user experience.

<FIG> is a flowchart of a traffic processing method according to another embodiment of the present invention.

The original access device such as OLT or DSLAM can undertake the TOF through software upgrade or new board card. The following is an example of a new board card.

This embodiment is applied to the networking diagram shown in <FIG> or <FIG>. As shown in <FIG>, a TOF processing card is built in a layer-<NUM> access device OLT, and the built-in TOF processing card is connected to an Ethernet line card and PON access line card through a switch board. MEC APP server can be accessed through the Ethernet board, and the TOF function can be realized through the built-in TOF processing card. As shown in <FIG>, a TOF processing card is built in a layer-<NUM> access device OLT. The TOF processing card is connected to the PON access line card through the switch board, and MEC APP Server is directly connected to the TOF. The TOF function can be realized through the built-in TOF processing card.

The method includes steps of S601, S602, S603, S604, S605 and S606.

At S601, the switch board receives an upstream traffic message from a HGU, and matches the destination MAC of the upstream traffic message with the corresponding BRAS/SR MAC.

At S602, the upstream traffic message is sent to the TOF processing card when there is a match between the destination MAC of the upstream traffic message and the corresponding BRAS/SR MAC.

At S603, the upstream traffic message is switched to the BRAS or SR when there is no match between the destination MAC of the upstream traffic message and the corresponding BRAS/SR MAC.

In some embodiments, the switch board has a simple layer-<NUM> traffic offloading capability, that is, the switch board can redirect the traffic according to the destination MAC. In this case, the switch board performs MAC matching for the upstream traffic message from users and servers, and the packet whose destination MAC matching with the BRAS/SR MAC is redirected to the TOF processing card for processing, while other traffic is processed by normal layer-<NUM> forwarding.

At S604, the TOF processing card determines whether the upstream traffic message is local traffic.

The process of determining whether the upstream traffic message is local traffic is similar to the previous embodiment, and will not be described in detail.

At S605, the TOF processing card performs layer-<NUM> forwarding according to the forwarding table when the upstream traffic message is local traffic.

At S606, the TOF processing card is directed to the switch board for normal layer-<NUM> forwarding when the upstream traffic message is not local traffic.

The relevant contents of the forwarding table are similar to those of the previous embodiment, and will not be described in detail.

The TOF processing card analyzes the destination IP, matches the destination IP with the user forwarding table and the server forwarding table, to further distinguish local traffic and not local traffic; where the not local traffic is directed to the switch board for normal layer-<NUM> forwarding, and the local traffic is subjected to layer-<NUM> forwarding by simulating BRAS or SR according to the user forwarding table or server forwarding table.

In this embodiment, when the destination device corresponding to the destination IP of the upstream traffic message is a MEC APP Server, the TOF processing card performs layer-<NUM> forwarding and sends the packet to the MEC APP Server; and when the destination device corresponding to the destination IP of the upstream traffic message is not a directly connected MEC APP Server, the TOF processing card performs layer-<NUM> forwarding and sends the packet to BRAS or SR through an uplink line card on network side.

In addition, the switch board may have a flow mirroring function for protocol. The switch board copies PPPoE and DHCP protocol packets to the TOF board through flow mirroring, and the TOF board listens to the protocol process accordingly, and establishes and maintains the user forwarding table and the server forwarding table. If the switch board does not have the flow mirroring function for protocol, the TOF can also establish and maintain the user forwarding table and server forwarding table through the data message learning and aging mechanism.

In addition, if the switch board does not have layer-<NUM> traffic offloading capability, all traffics can be directed to the TOF board for processing. This method is simple, but requires higher processing performance of the TOF board, and the implementation is the same as that of the previous embodiment.

If an access device cannot be upgraded or built with a TOF processing card, the access device may also be implemented by an external TOF processing device.

This embodiment is applied to the networking diagram shown in <FIG>. As shown in <FIG>, the external TOF processing device is connected to an OLT and a MEC APP Server to realize TOF. Generally, the MEC APP Server is directly connected to the TOF device, and an upper interface of the OLT is also directly connected to the TOF device, while the TOF device is connected to upstream BRAS/SR.

The method includes steps of S901, S902, S903 and S904.

At step S901, the OLT switch board receives an upstream traffic message from a HGU and forwards the upstream traffic message to the TOF processing device.

In this embodiment, the OLT is not limited, but used for forwarding packets.

At step S902, the TOF processing device determines whether the upstream traffic message is local traffic.

The determination process is similar to the above embodiments, and will not be described in detail.

At step S903, the TOF processing device performs layer-<NUM> forwarding for the upstream traffic message according to a forwarding table stored locally when the upstream traffic message is local traffic.

The relevant contents of the forwarding table are similar to the above embodiments, and will not be described in detail.

The layer-<NUM> forwarding is similar to the above embodiments, and will not be described in detail.

At step S904, the TOF processing device performs layer-<NUM> forwarding when the upstream traffic message is not local traffic.

<FIG> is a schematic structural diagram of a layer-<NUM> access device according to an embodiment of the present invention. As shown in <FIG>, the layer-<NUM> access device includes the traffic offloading function (TOF) described in any of the above embodiments.

The layer-<NUM> access device also includes a switch board.

The switch board is configured to receive an upstream traffic message and match a destination MAC of the upstream traffic message with the corresponding BRAS/SR MAC.

When there is a match between the destination MAC of the upstream traffic message and the corresponding BRAS/SR MAC, the switch board sends the upstream traffic message to the Traffic Offload Function (TOF).

When there is no match between destination MAC of the upstream traffic message and the corresponding BRAS/SR MAC, the switch board switches the upstream traffic message to the BRAS or SR.

In some embodiments, the upstream traffic message is directly switched to the BRAS or the SR when the TOF is directly connected to the BRAS or the SR and the upstream traffic message is not local traffic.

The TOF switches the upstream traffic message to the BRAS or the SR through the switch board when the switch board is directly connected to the BRAS or the SR and the upstream traffic message is not local traffic.

<FIG> is a schematic structural diagram of a traffic processing system according to an embodiment of the present invention. As shown in <FIG>, the traffic processing system includes a layer-<NUM> access device and the traffic offloading function (TOF) described in any of the above embodiments.

The layer-<NUM> access device is configured to receive an upstream traffic message and forward the upstream traffic message to the TOF.

The TOF is directly connected to a BRAS or a SR.

A destination device corresponding to a destination IP of the upstream traffic message and directly connected to the TOF is a MEC APP Server.

A destination device corresponding to a destination IP of the upstream traffic message and directly connected to the layer-<NUM> access device is a HGU.

<FIG> is a flowchart of a method for establishing a forwarding table according to an embodiment of the present invention. As shown in <FIG>, the method includes a step of S1301.

At step S1301, for PPPoE dynamic access mode, the forwarding table is dynamically established by listening to PPPoE process, or the forwarding table is established in a self-learning manner by listening to a data message of a session;.

The forwarding table is used for a TOF to determine whether the upstream traffic message is local traffic.

The forwarding table includes IP information of a device directly connected to the TOF or directly connected to a layer-<NUM> access device to which the TOF is connected or belongs.

The forwarding table also includes at least one of the following information corresponding to the IP information:
session type, PPPoE session ID, access port, layer-<NUM> encapsulation information, session state, local traffic value, session time, BRAS/SR Media Access Control address (MAC).

The forwarding table is also used for the TOF to perform layer-<NUM> forwarding for the upstream traffic message.

The user forwarding table includes user IP information, which is IP information of a user side equipment directly connected to a layer-<NUM> access device to which the TOF is connected or belongs, and the user forwarding table also includes at least one of the following information corresponding to the user IP information:
session type, PPPoE session ID, access port, layer-<NUM> encapsulation information, session state, local traffic value, session time, BRAS/SR MAC.

The server forwarding table includes server IP information, which is IP information of a server device directly connected to the TOF or directly connected to the layer-<NUM> access device to which the TOF belongs, and the server forwarding table also includes at least one of the following information corresponding to the server IP information:
session type, PPPoE session ID, access port, layer-<NUM> encapsulation information, session state, local traffic value, session time, BRAS/SR MAC.

<FIG> is a schematic structural diagram of an apparatus for establishing a forwarding table according to an embodiment of the present invention. As shown in <FIG>, the apparatus includes an establishing unit.

The establishment unit is configured to: for a PPPoE dynamic access mode, dynamically establish the forwarding table by listening to PPPoE process or establish the forwarding table in a self-learning manner by listening to a data message of a session;.

The forwarding table is used for a TOF to determine whether an upstream traffic message is local traffic.

The forwarding table also includes at least one of the following information corresponding to the IP information:.

The apparatus also includes an update or revocation unit.

The update or revocation unit is configured to: for the PPPoE dynamic access mode, dynamically update or revoke the forwarding table by listening to the PPPoE process; or update the forwarding table in a self-learning manner by listening to the data message of the session, and revoke the forwarding table through aging mechanism;.

Compared with related technologies, through the technical schemes of the embodiments of the present invention, local traffic offloading can be realized on a layer-<NUM> access device.

Claim 1:
A traffic processing method, applied to a Traffic Offload Function, TOF, comprising:
determining (<NUM>) whether an upstream traffic message is local traffic; and
performing (<NUM>) layer-<NUM> forwarding for the upstream traffic message according to a forwarding table stored locally in response to the upstream traffic message being local traffic;
characterized in that determining whether the upstream traffic message is local traffic comprises:
determining whether a destination IP of the upstream traffic message matches IP information in the forwarding table; wherein the IP information in the forwarding table is IP information of a device directly connected to the TOF or directly connected to a layer-<NUM> access device to which the TOF is connected or belongs;
determining that the upstream traffic message is local traffic in response to a match between the destination IP of the upstream traffic message and the IP information in the forwarding table; and
determining that the upstream traffic message is not local traffic in response to no match between the destination IP of the upstream traffic message and the IP information in the forwarding table.