TWI732552B - Mobile edge computing platform and packet offloading method based on mobile edge computing - Google Patents

Abstract

A mobile edge computing (MEC) platform and a packet offloading method based on MEC are provided. In the method, an uplink traffic packet from the mobile network is received. An endpoint identification for transmitting user data via tunneling protocol by the user equipment (UE) is obtained from the signaling packet. Whether to forward the uplink traffic packet, which is designed to be transmitted to the core network before, to an internal server is determined according to the endpoint identification and a destination network address of the uplink traffic packet. Accordingly, the efficiency of local offloading can be improved.

Description

Mobile edge computing platform and packet unloading method based on mobile edge computing

The present invention relates to a mobile edge computing (Mobile Edge Computing, MEC) technology, and particularly relates to a mobile edge computing platform and a packet offloading method based on mobile edge computing.

In the mobile edge computing architecture, the user's local offload function is provided, which can provide mobile user-specific services more quickly, and can also reduce the burden on the core network. Mobile edge computing usually uses multiple fields such as the Internet Protocol (IP) address, destination IP address, source port (port), and destination port of the packet to determine whether it is local Uninstalled package. Too many field analysis will increase the processing time of the packet, and then affect the performance.

In view of this, the embodiments of the present invention provide a mobile edge computing platform and a packet unloading method based on mobile edge computing, which check the outer layer information of the packet to confirm whether the packet needs to be unloaded locally, thereby improving processing efficiency.

The mobile edge computing platform of the embodiment of the present invention includes (but is not limited to) a communication transceiver, a storage, and a processor. The communication transceiver receives uplink traffic packets from the mobile network. The memory records several modules. The processor is coupled to the communication transceiver and the storage, and accesses and executes the software modules recorded in the storage. Those software modules include a signaling capture and analysis module and a local uninstallation judgment module. The signaling capture and analysis module obtains the endpoint identification code of the user equipment that transmits user data via a tunneling protocol from the signaling packet, and obtains the user information of the user equipment according to the endpoint identification code. The local offload determination module determines whether to forward the upstream traffic packets originally sent to the core network to the internal server based on the endpoint identification code and the destination network address of the upstream communication packet.

The packet offloading method based on mobile edge computing in the embodiment of the present invention includes (but is not limited to) the following steps: receiving traffic packets from the mobile network. Obtain from the signaling packet the endpoint identification code for the user equipment to transmit user data via the tunnel protocol. Obtain the user information of the user equipment according to the endpoint identification code. According to the endpoint identification code and the destination network address of the upstream traffic packet, it is determined whether to forward the upstream traffic packet originally sent to the core network to the internal server.

Based on the above, the mobile edge computing platform and the packet unloading method based on the mobile edge computing of the embodiments of the present invention check the endpoint identification code corresponding to the packet to obtain more user information, and further combine the destination address to determine whether to forward the packet to the internal Network to unload the packet to the local. In this way, not only can the packet processing time be reduced, but also the flexible comparison conditions can be increased, thereby improving transmission efficiency and enhancing the strength of information security protection.

In order to make the above-mentioned features and advantages of the present invention more comprehensible, the following specific embodiments are described in detail in conjunction with the accompanying drawings.

FIG. 1 is a block diagram of components of a communication architecture according to an embodiment of the present invention. Please refer to Figure 1. This communication architecture includes (but is not limited to) a mobile edge computing (MEC) platform 100, one or more user equipment (User Equipment, UE) 10, a mobile network 20, and an internal server for MEC services 30. Core network 40, and Internet 50.

The user equipment 10 may be a computer host, a smart phone, a tablet computer, a wearable device, or other network-connectable devices.

The mobile network 20 can be a universal mobile communication system terrestrial radio access network (UMTS Terrestrial Radio Access Network, UTRAN), an evolved universal terrestrial radio access network (Evolved Universal Terrestrial Radio Access Network, E-UTRAN) and other generations of operations. Network standard access to the network.

The internal server 30 refers to a server related to internal application services that does not need to go through the core network 40.

The core network 40 may be the core network of various generations of mobile network standards or its network entities (for example, mobility management entity (MME), service gateway (Serving Gateway, S-GW), or storage). Access and mobility management functions (Access and mobility Management Function, AMF), etc.).

The MEC platform 100 includes (but is not limited to) a communication transceiver 110, a storage 130, and a processor 150. The MEC platform 100 may be a gateway device, a router device, a host computer, a server, etc. between the mobile (access) network 20 and the core network 40.

The communication transceiver 110 may be a network module, interface card, chip or circuit that supports wired communication such as Ethernet and optical fiber technology, or supports wireless communication such as Wi-Fi and Bluetooth.

The storage 130 can be any type of fixed or removable random access memory (Random Access Memory, RAM), read-only memory (Read-Only Memory, ROM), flash memory (Flash Memory) or similar components Or a combination of the above elements. The memory 130 stores code, device configuration, buffered or permanent data, such as the signaling acquisition and analysis module 131 (including the first and second signaling acquisition and analysis modules 132, 133), and the network name system (DNS) Analysis module 134, local uninstallation condition setting module 135, and local uninstallation judgment module 136 and other software modules or program codes, user information, traffic packet related information, control signaling, local uninstallation condition information, etc. , Information and comparison table, and the detailed operation of each software module will be explained in subsequent embodiments.

It should be noted that the aforementioned software modules can be deployed on the same hardware platform, and the communication between the modules is based on a programmatic interface. Alternatively, the aforementioned software modules can also be deployed on different hardware platforms, and the communication between the modules is based on the IP-based communication protocol.

The processor 150 is coupled to the communication transceiver 110 and the storage 130, and may be a CPU, a microprocessor, a microcontroller, a digital signal processing (DSP) chip, or a field programmable logic gate array (Field Programmable Gate). Array, FPGA) and other programmable units or integrated circuits (Integrated Circuit, IC). In this embodiment, the processor 150 is used to perform all operations of the MCE platform 100, and can access and execute those software modules recorded in the storage 130.

In order to facilitate the understanding of the operation process of the present invention, a number of embodiments will be described below in detail. Hereinafter, the method described in the embodiment of the present invention will be described in conjunction with the devices, components, and modules in the communication architecture in FIG. 1. Each process of the method can be adjusted accordingly according to the implementation situation, and it is not limited to this.

2 is a flowchart of a packet unloading method based on mobile edge computing according to an embodiment of the present invention. Please refer to FIG. 2, the processor 150 receives the upper traffic packet from the mobile network 20 through the communication transceiver 110 (step S210). Specifically, an uplink traffic packet is a packet sent by any user equipment 10 via a base station in the mobile network 20, and may include the data traffic (or user data/user plane) that the user equipment 10 intends to send. (user-plane) data). In some embodiments, the base station encapsulates the packet of the user equipment 10 into a tunneling protocol (e.g., GPRS tunneling protocol (GTP) or other similar protocol) format (e.g., GTP-U packet), so that the mobile edge The computing platform 100 receives a GTP-U packet containing data traffic.

It is worth noting that if the mobile edge computing platform 100 is not set up, the uplink traffic packets will be transmitted to the Internet 50 via the core network 40. In the embodiment of the present invention, the mobile edge computing platform 100 is set to determine whether the upstream traffic packet needs to be locally offloaded (ie, forwarded to the internal server 30).

The signaling capture and analysis module 131 can obtain the endpoint identification code of the user equipment 10 that transmits user data via the S1 interface from the signaling packet (step S230). Specifically, the endpoint identification code is carried in the header of the packet related to the tunnel agreement and used to distinguish different connections in the tunnel. For example, the GTP-U packet includes a tunnel endpoint identifier (TEID). In addition, the mobile edge computing platform 100 can further identify which user equipment 10 the tunnel belongs to based on the specific endpoint identification code. That is, the user equipment 10 can be distinguished.

Then, the signaling capture analysis module 131 can obtain the user information corresponding to the user equipment 10 according to the endpoint identification code (step S250). Specifically, since the endpoint identification code can be used to identify the user equipment 10, the signaling capture and analysis module 131 can further search for the user information corresponding to the user equipment 10 from the previously stored network-wide user data table. This network-wide user data table is a collection of user information of all user equipment 10 recorded by the carrier (may be in the form of a database, a comparison table, etc.). The user information can be door number, access point name (Access Point Name, APN), base station network address (that is, the network address of the base station in the mobile network 20, and the user equipment 10 is currently receiving This base station service), user network address, or a combination thereof. Wherein, the network address is, for example, an IP address, a media access control (MAC) address, or other identification codes in the network. In addition, unlike the prior art that needs to search for multiple fields in the packet to obtain user information, the embodiment of the present invention can search for recorded user information based on the endpoint identification code, which obviously improves processing efficiency.

In one embodiment, the signaling capture analysis module 131 can first determine whether the endpoint identification code and its user information comply with the local uninstall authority. If it meets the local uninstall authority, the endpoint identification code is provided to the local uninstall judgment module 136 for the local uninstall judgment module 136 to determine whether to forward the uplink traffic packet. In other embodiments, all mechanisms of the local uninstallation determination may be performed by the local uninstallation determination module 136. It should be noted that the setting of the local uninstall permission will be detailed in subsequent embodiments.

In addition, it should be noted that the content in the user information can be changed according to actual needs, and the embodiment of the present invention is not limited.

Then, the local offload determination module 136 can determine whether to forward the upstream traffic packet originally sent to the core network 40 to the internal server 30 based on the endpoint identification code and the destination network address of the upstream traffic packet (step S270 ). Specifically, the local uninstallation judgment module 136 can obtain the local uninstallation condition information set in advance (and can be modified afterwards) from the local uninstallation condition setting module 135. This local uninstallation condition information can record the network addresses (for destination network address comparison) that can/need to be locally uninstalled (that is, sent to the internal server 30). The local unloading judgment module 136 compares whether the endpoint identification code and the destination network address corresponding to the uplink traffic packet have been recorded in the local unloading condition information. If it has been recorded in the local unloading condition information, it means that the upstream traffic packet can be locally unloaded, and the local unloading determination module 136 forwards the upstream traffic packet to the internal server 30. On the other hand, if it has not been recorded in the local offload condition information, the local offload determination module 136 still sends the uplink traffic packet to the core network 40 (for example, the Serving Gateway (S-GW) )).

In one embodiment, the domain network address corresponds to a specific survival time. The local uninstall judging module 136 can obtain the corresponding survival time (the survival time of the corresponding domain network address) according to the destination network address, and determine whether the survival time has expired to confirm the DNS status. If the survival time has not expired, the local offload determination module 136 can remove the tunnel protocol header (even the outer IP header) in the uplink traffic packet, and forward the remaining packets to the internal server 30. If it has expired, the upstream traffic packet can be sent to the core network 40.

The following further describes the establishment of local uninstallation condition information, signaling analysis, DNS resolution, and local uninstallation judgment in order.

FIG. 3 is a flowchart of setting the uninstallation condition according to an embodiment of the present invention. Please refer to Figure 3, the local uninstallation condition setting module 135 waits for the setting personnel to set the user authority for installation information. After obtaining the user authorization data, the setting personnel enters the user interface provided by the local uninstallation condition setting module 135 to modify the user authority for installation information ( Including user information such as door number, APN, base station network address, website address, destination network address, etc., and is related to the aforementioned local uninstall authority) (step S310). It should be noted that all fields are not required, and the level of detail determines the severity of the conditions. The local uninstallation condition setting module 135 can store user information such as door number, APN, and base station network address in the local uninstallation condition information. For example, Table (1) is an example to illustrate local uninstallation condition information: Table (1) Door number APN Base station IP address 0988654321 CHT1 1.2.3.4 0987653210 CHT2 1.2.4.4 0986543210 AUO 3.2.1.2 The local uninstallation condition setting module 135 can set the local uninstallation condition information based on the added or deleted user information (step S320), and further update the local uninstallation condition information to the local uninstallation condition information of the local uninstallation condition setting module 135 (step S330). ).

The local uninstallation condition setting module 135 can set the local uninstallation condition information based on the added or deleted URL information (step S340), and further update the URL information to the domain name system resolution module 134 (step S350, for adding specific URLs) Information), or issue a deletion command to the domain name system analysis module 134 (step S355, for deleting the URL information). The URL information is, for example, domain names such as www.cht.com and www.chtlearn.com.

The local uninstallation condition setting module 135 can set the local uninstallation condition information based on the added or deleted destination network address information (step S360), and further update the destination network address information to the local uninstallation judgment module 136 ( Step S370). In addition, the local uninstallation condition setting module 135 can perform operations such as deleting, adding, and modifying user installation information based on the user authorization data. After the update is completed, the mobile user can take effect when they go online.

FIG. 4 is a flowchart of signaling capture and analysis according to an embodiment of the present invention. Referring to FIG. 4, the signaling capture and analysis module 131 determines the packet type (step S410). If one or more first signaling is received from the core network 40 (the GTP-C packet of the S11 interface will be used as an example, but not limited to this type) (step S421), the first signaling is captured The fetch analysis module 132 can obtain the corresponding door number, access point name, and user from the packets (for example, CreateSession Request and Response packets) related to the creation of a session (create session) in the first signaling. Network address (steps S424 and S425). Then, the first signaling capture and analysis module 132 can also obtain the corresponding endpoint identification code, gate number, and terminal ID from the packets related to modify bearer (for example, Modify Bearer Request and Response packets) in the first signaling. The access point name, base station network address, and user network address are stored, and these user information are stored in the entire network user data table (steps S426 and S427). For example, Table (2) is an example to illustrate user information: Table (2) TEID User IP address Door number APN Base station IP address 789456 10.30.1.2 0988654321 CHT1 1.2.3.4 567831 10.20.1.3 0987653210 CHT2 1.2.4.4 In addition, if the first signaling capture and analysis module 132 receives packets (for example, DeleteSession Request and Response packets) related to the delete session (delete session) from these first signalings (step S422), it can download from the entire network The corresponding user information is deleted from the user data table (step S423).

On the other hand, if one or more second signaling is received from the base station of the mobile network 20 (the following will take the S1-AP packet of the S1 interface as an example, but it is not limited to this type) (step S431). The second signaling capture and analysis module 133 can obtain an initial context setup (initial context setup) packet (for example, an InitialContext SetupRequest packet) from the second signaling (step S432), and obtain the user from the packet The endpoint identification code of the device 10 (for example, TEID, and its value is, for example, 789456, 567891, but not limited to this) (step S433), and then the endpoint identification code is used to find the corresponding data in the user data table of the entire network User information such as APN, door number, user network address, and base station network address (steps S451 and S452). Then, the signaling capture analysis module 131 can compare these combinations (ie, the endpoint identification code) with the local uninstallation condition table information (step S453) to determine whether the endpoint identification code complies with the local uninstallation authority. The signaling capture and analysis module 131 can send the endpoint identification code to the local uninstallation judgment module 136 according to the comparison result (in the case of compliance with the local uninstallation authority) (step S454). Otherwise (not in compliance), there is no need to update the local uninstallation judgment module 136. In addition, if the second signaling capture and analysis module 133 receives the user equipment context release packet (for example, UEContextRelease packet) from the second signaling (step S434), it will notify the local uninstallation determination module 136 The user information corresponding to the endpoint identification code is deleted (step S435).

FIG. 5 is a flowchart of DNS resolution according to an embodiment of the present invention. Please refer to FIG. 5, the left half of the figure is responsible for processing the information from the local uninstallation condition setting module 135. If the domain name system analysis module 134 receives the newly added URL information (that is, the domain name to be added) (step S514), it will save it to the locally uninstalled domain name and (domain) network URL Compare the table (step S515). If the domain name system analysis module 134 receives the deleted web address information (ie, the domain name to be deleted) (step S511), it will query the domain name to be deleted in the domain name and web address comparison table Corresponding to the network address (step S512), and issue a delete command to delete the network address to the local uninstallation judgment module 136 (step S513). On the other hand, the right half of the figure is for processing traffic packets from the core network 40 (GTP-U downlink packets are taken as an example below, but not limited to this). If the domain name system resolution module 134 receives a GTP-U downlink packet to be transmitted to a certain user equipment 10 (step S521), it determines whether the packet is a domain name system (DNS) used to query the domain Respond to the packet (step S522). If it is a response packet, the domain name system analysis module 134 determines whether the domain name contained in the response packet exists in the domain name table (recorded in the local uninstallation condition information) that needs to be uninstalled locally (that is, whether it can be locally Uninstall) (step S523). If it exists in the domain name table that needs to be uninstalled locally, the domain name system analysis module 134 obtains and returns the corresponding domain network address and its survival time (for example, TTL (Time To Live)) to the local uninstallation The judgment module 136 (for the local uninstallation judgment module 136 judges whether to forward the uplink traffic packet based on the domain network address and survival time), and stores the domain network address and survival time and other information to the network A comparison table of domain names and web addresses (steps S524 and S525). For example, Table (3) is an example to illustrate the comparison table of domain names and Internet URLs: Table (3) Domain name IP address www.cht.com 10.20.1.1 www.chtlearn.com 10.20.2.2

Fig. 6 is a flowchart of a local uninstallation judgment according to an embodiment of the present invention. Please refer to Figure 6. The left half of the figure is for processing the data transferred from each module. If the command and its endpoint identification code are received from the signaling capture analysis module 131 (step S611), the local uninstallation judgment module 136 judges whether the command is a new or deleted command (step S612). If it is a new command, the local uninstallation judgment module 136 adds a locally uninstallable endpoint identification code from the local uninstallation condition information (step S613); if it is a deletion command, the local uninstallation judgment module 136 adds the local uninstallation condition information from the local uninstallation condition information. The endpoint identification code that can be uninstalled locally is deleted (step S614).

If a command and its destination network address are received from the local uninstallation condition setting module 135 (step S621), the local uninstallation determination module 136 determines whether the command is a new or deleted command (step S622). If it is a new command, the local uninstall judging module 136 adds a destination network address that can be uninstalled locally from the local uninstall condition information (step S623); if it is a delete command, the local uninstall judging module 136 downloads the condition from the local The destination network address that can be uninstalled locally is removed from the information (step S624).

If the command from the domain name system analysis module 134 and its domain network address and survival time are received (step S631), the local uninstallation judgment module 136 judges whether the command is a new or deleted command (step S632). If it is a new command, the local uninstall judging module 136 adds a local uninstallable domain network URL and its survival time from the local uninstall condition information (step S633); if it is a delete command, the local uninstall judging module 136 automatically From the local uninstallation condition information, delete the local uninstallable domain network URL and its survival time (step S634).

On the other hand, the right half of the figure is processing the user's GTP-U uplink packet (that is, an example of uplink traffic packet, but not limited to this). After the local uninstallation determining module 136 receives the GTP-U uplink packet (step S651), it extracts the endpoint identification code from the packet and looks up a table (for example, local uninstallation condition information) to determine whether local uninstallation is required (step S652). If local uninstallation is required, the local uninstallation determining module 136 compares whether the destination network address recorded in the inner layer of the packet is a network address that needs to be uninstalled locally (step S653), and determines the destination network address Whether the survival time of the user has expired (step S655). If it is not expired, the local uninstallation judging module 136 can remove the outer IP and GTP fields for local uninstallation (step S657), and forward the remaining packets to the corresponding local uninstallation server (ie, the internal server 30) (Step S658). On the other hand, if it has expired, the local uninstall judging module 136 can delete the corresponding network address information (step S656), and send the GTP-U uplink packet to the S-GW of the core network 40 (step S654) ) (That is, no local uninstallation is required).

In order to facilitate the reader to better understand the inventive spirit of the embodiments of the present invention, another embodiment is described below:

The first step: the setting staff conducts user permissions for installation settings. Step 2: The local uninstallation condition setting module 135 sends the URL information in the setting to the domain name system analysis module 134, sends the destination IP information to the local uninstallation judgment module 136, and sends the remaining user IP addresses, User information such as door number, base station IP address, APN, etc. is stored in the local uninstallation condition setting module 135 and is searched by the subsequent signaling acquisition and analysis module 131. The third step: The signaling capture and analysis module 131 will automatically capture the signaling information of mobile users on the entire network, and after analyzing the signaling, store the user IP address, door number, base station IP, APN and other users of the entire network. Information to the entire network user data table. The fourth step: the communication transceiver 110 receives the user traffic packet in the MEC area. If the signaling capture and analysis module 131 determines that the packet is an upstream packet, it will be directed to the local offload determination module 136, and if it is a downstream packet, it will be directed to the network domain. The name system resolution module 134. Step 5: If the domain name system resolution module 134 determines that the packet is a DNS response packet, and the domain name it queried has a URL to be uninstalled locally, then the corresponding IP address and its TTL will be sent to the local uninstallation judgment module Group 136. The sixth step: when the user generates a signaling procedure in the MEC area, the signaling capture and analysis module 131 captures the TEID in the user's signaling information. The seventh step: The signaling capture and analysis module 131 uses the TEID to query the corresponding user information (including user IP address, door number, base station IP address, and APN) in the user data table of the entire network, and compare these The user information is inquired from the local uninstallation condition setting module 135. If the local uninstallation condition information is met, the signaling capture and analysis module 131 transmits the TEID to the local uninstallation judgment module 136. The eighth step: the local uninstallation judging module 136 receives the user traffic packet in the MEC area and grabs the TEID in the packet and looks up the table to determine whether the local uninstallation is required. If local uninstallation is required, the local uninstallation determining module 136 then grabs the destination IP address and determines whether it is a local uninstallation destination IP address, and determines that the TTL of the IP address has not expired. Finally, the local offload determination module 136 removes the GTP header of the qualified packets and sends them to the internal server 30 corresponding to the MEC service; the unqualified packets are sent to the core network 40.

In summary, the mobile edge computing platform and the packet offloading method based on mobile edge computing of the embodiments of the present invention include the following features:

The embodiment of the present invention uses multiple channels, including data from base stations, APNs, user numbers, browsing websites, etc., as conditions for local uninstallation, thereby increasing the flexibility of comparison.

The embodiments of the present invention provide administrators with multiple local uninstallation condition settings, which can be set in a small area to achieve fine control of a single user's behavior, or a large area can be set to control user behavior in an entire area, which can manage mobile edge network users more flexibly.

The embodiment of the present invention only needs to look at the outer layer information of the packet to confirm whether it is a packet that needs to be uninstalled locally, thereby increasing the packet processing efficiency.

In terms of commercial applications, the embodiments of the present invention provide that enterprise users can not only manage the local uninstallation of company employees in a more subtle way to meet the needs of the enterprise, but also improve information security protection and prevent internal data from leaking.

Although the present invention has been disclosed in the above embodiments, it is not intended to limit the present invention. Anyone with ordinary knowledge in the relevant technical field can make some changes and modifications without departing from the spirit and scope of the present invention. The protection scope of the present invention shall be subject to those defined by the attached patent application scope.

10: User equipment 20: Mobile Internet 30: Intranet 40: core network 50: Internet 100: Mobile Edge Computing Platform 110: Communication transceiver 130: storage 131: Signaling Capture and Analysis Module 132: The first signaling capture and analysis module 133: The second signaling capture and analysis module 134: Domain Name System Resolution Module 135: Local uninstall condition setting module 136: Local uninstall judgment module S210~S270, S310~S370, S410~S454, S511~S525, S611~S658: steps

FIG. 1 is a block diagram of components of a mobile edge computing platform according to an embodiment of the present invention. 2 is a flowchart of a packet unloading method based on mobile edge computing according to an embodiment of the present invention. FIG. 3 is a flowchart of setting the uninstallation condition according to an embodiment of the present invention. FIG. 4 is a flowchart of signaling capture and analysis according to an embodiment of the present invention. FIG. 5 is a flowchart of Domain Name System (DNS) resolution according to an embodiment of the present invention. Fig. 6 is a flowchart of a local uninstallation judgment according to an embodiment of the present invention.

S210~S270:

Claims (8)

A mobile edge computing (Mobile Edge Computing, MEC) platform includes: a communication transceiver that receives an uplink traffic packet from a mobile network; a memory that records multiple software modules; and a processor, coupled The communication transceiver and the storage are connected, and the software modules recorded in the storage are accessed and executed, and the software modules include: a signaling acquisition and analysis module, which obtains a user from the signaling packet The device transmits an endpoint identification code of user data via a tunneling protocol, and obtains user information of the user equipment according to the endpoint identification code; and a local offload determination module based on the endpoint identification code and the uplink A destination network address of a traffic packet determines whether to forward the upstream traffic packet originally sent to a core network to an internal server, where the communication transceiver receives downstream traffic from one of the core networks Packets, and the software modules further include: a Domain Name System (DNS) resolution module, which determines whether the downlink traffic packet is a response packet for querying a domain, and obtains the packet according to the domain A network address corresponding to the downstream traffic packet and its survival time, and the local offload determination module determines whether to forward the upstream traffic packet based on the network address and the survival time. The mobile edge computing platform according to claim 1, wherein the user information includes a door number, an access point name (APN), and a base Station network address, and a user network address, the signaling capture analysis module determines whether the user information and the endpoint ID conform to a local uninstall permission, and if it meets the local uninstall permission, the local uninstall The judgment module judges whether to forward the upstream traffic packet. The mobile edge computing platform according to claim 1, wherein the local uninstallation judgment module obtains the corresponding survival time according to the destination network address, and determines whether the survival time has expired, and if the survival time has not expired, Then the local offload determination module removes the tunnel protocol header in the uplink traffic packet and forwards the remaining packets to the internal server. The mobile edge computing platform of claim 2, wherein the communication transceiver receives at least one first signaling from the core network and at least one second signaling from a base station, and the signaling is captured and analyzed The module obtains the corresponding door number, the access point name, and the user network address from the packet related to create session in the at least one first signaling, and from the at least one first signaling In the packet about modify bearer, obtain the corresponding endpoint identification code, the door number, the access point name, the base station network address, and the user network address, and store them accordingly An entire network user data table, and the signaling capture analysis module obtains the endpoint identification code from the packet about initial context setup in the at least one second signaling, and then uses the endpoint identification The code is used to query the user information from the network-wide user data table. A packet offloading method based on mobile edge computing includes: receiving an uplink traffic packet from a mobile network; Obtain an endpoint identification code of a user equipment that transmits user data via a tunneling protocol from a signaling packet; obtain user information of the user equipment based on the endpoint identification code; and based on the endpoint identification code and a purpose of the uplink traffic packet The local network address determines whether to forward the upstream traffic packet originally sent to a core network to an internal server; receive a downstream traffic packet from one of the core networks; determine whether the downstream traffic packet is a query A response packet from a domain; and a domain network address corresponding to the downlink traffic packet and its survival time are obtained according to the domain, and it is judged whether to forward the uplink traffic packet originally sent to the core network The step to the internal server includes: judging whether to forward the uplink traffic packet according to the network address and the survival time. The packet unloading method based on mobile edge computing according to claim 5, wherein the user information includes a door number, an access point name, a base station network address, and a user network address, wherein it is determined whether to The step of forwarding the upstream traffic packet originally sent to the core network to the internal server includes: judging whether the endpoint identifier complies with a local uninstall authority; and if it complies with the local uninstall authority, judging whether to forward the upstream Communications packet. The packet offloading method based on mobile edge computing according to claim 5, wherein the step of judging whether to forward the uplink traffic packet according to the network domain network address and the survival time includes: Obtain the corresponding survival time according to the destination network address; determine whether the survival time has expired; if the survival time has not expired, remove the tunnel protocol header in the uplink traffic packet and forward the remaining packets to the Internal server. The packet offloading method based on mobile edge computing according to claim 6, further comprising: receiving at least one first signaling from the core network and at least one second signaling from a base station; Obtain the corresponding door number, the name of the access point, and the user network address for the packet for creating a conference in the first signaling; obtain the corresponding end from the packet for modifying the bearer in the at least one first signaling The point identification code, the door number, the access point name, the base station network address, and the user network address are stored in a network-wide user data table; from the at least one second signaling Obtain the endpoint identification code in the packet created in relation to the initial context; and query the user information from the network-wide user data table according to the endpoint identification code.

Images