A network offloading system and a network offloading method
By parsing data packets and determining the user device IP in the NR base station access network module and diversion module, and sending them directly to the local network or encapsulating them in the core network, the complexity and overhead problems of existing network diversion methods are solved, achieving lower transmission delay and more efficient data processing.
Patent Information
- Application Number
- CN202510820726.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2025-06-19
- Publication Date
- 2025-10-10
- Estimated Expiration
- 2045-06-19
AI Technical Summary
Existing network offload methods require real-time tracking and updating of the context status of a large number of users, as well as identification and removal of GTP-U packet headers. This results in a complex and costly system and fails to effectively address the issues of high transmission latency and data security risks in the NR network architecture.
A network offload system is provided, including an NR base station access network module and an NR base station offload module. The system determines the service type by parsing the uplink data packet and sends it directly to the local network based on the user device IP, or adds GTP-U header encapsulation when providing public network services, thereby reducing dependence on the core network and simplifying the process.
It reduces system complexity and overhead, reduces transmission delay, and especially reduces end-to-end delay by about 30% in local business scenarios, and reduces the load pressure on the core network.
Smart Images

Figure CN120343622B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of network communication technology, and in particular to a network traffic distribution system and a network traffic distribution method. Background Art
[0002] With the rapid development of the mobile internet and the Internet of Things (IoT), a wide range of new services and applications are emerging, such as high-definition video, cloud gaming, the Industrial Internet of Things (IIoT), and smart cities. This proliferation of new services and applications has led to a dramatic increase in the number of connected devices, and consequently, a surge in demand for mobile network traffic. To effectively address this traffic growth and improve user experience, the NR (New Radio) network architecture—an architecture for transmitting and processing data in wireless communication networks based on 5G NR technology—is gaining widespread adoption.
[0003] In the NR network architecture, all service data is exchanged between the gNB (5G base station) and the 5G core network (5G core network) via the N3 interface, and packet data is transmitted between the 5GC and the DN (Data Network) via the N6 interface. In this architecture, service data must be transmitted to the DN via the N3 and N6 interfaces, resulting in long transmission lines. In some specialized scenarios, even if the server is deployed within the DN, data transmission still requires the N3 and N6 interfaces, resulting in high latency and data security risks. Therefore, local service offload is a pressing issue for the NR network architecture.
[0004] Existing network offload methods primarily remove the GTP-U (GPRS Tunnelling Protocol for User Plane) packet header from an uplink data packet received from an NR base station. If the packet is detected as uplink user plane data sent by a user terminal to a predetermined local area network device, the GTP-U packet header is removed to obtain a local service uplink data packet, which is then forwarded to the predetermined local area network device. This network offload method requires real-time tracking and updating of the context status of a large number of users, as well as identification and removal of the GTP-U packet header, resulting in system complexity and high overhead.
[0005] Existing network offload methods require real-time tracking and updating of the context status of a large number of users, as well as identification and removal of GTP-U packet headers. This results in complex systems and high overhead, and no effective solution has yet been proposed. Summary of the Invention
[0006] Based on this, it is necessary to provide a network diversion system and a network diversion method to address the above technical problems.
[0007] In a first aspect, the present application provides a network offloading system. The system comprises: an NR base station access network module and an NR base station offloading module;
[0008] The NR base station access network module is connected to the user equipment and the NR base station offloading module respectively, and is configured to receive an uplink data packet sent by the user equipment, and send the received uplink data packet to the NR base station offloading module;
[0009] The NR base station offloading module is configured to analyze the received uplink data packet, determine the service type of the data corresponding to the uplink data packet, determine the user equipment IP corresponding to the received uplink data packet when the service type is a local service, and send the received uplink data packet to the local network corresponding to the user equipment IP based on the user equipment IP.
[0010] In one embodiment, the system further comprises a core network module;
[0011] The NR base station offloading module is connected to the core network module, and is further configured to add a GTP-U header to the received uplink data packet for encapsulation when the service type is a public network service, and send the encapsulated uplink data packet to the core network module;
[0012] The core network module is configured to send the received encapsulated uplink data packet to a public network.
[0013] In one embodiment, the NR base station offloading module is further configured to, after receiving a downlink data packet, detect whether the received downlink data packet is from a local service server, determine the user equipment identifier and the downlink tunnel endpoint identifier corresponding to the downlink data packet based on a user plane instance management table if it is detected that the downlink data packet is from the local service server, and send the user equipment identifier and the downlink tunnel endpoint identifier corresponding to the downlink data packet to the NR base station access network module; the user plane instance management table is a correspondence table of the user equipment identifier, the downlink tunnel endpoint identifier, the uplink tunnel endpoint identifier, and the user equipment IP of each user equipment; if it is detected that the downlink data packet is from the core network module, the downlink data packet is transmitted to the user plane for GTP-U header stripping processing to obtain internal data without the GTP-U header, and the internal data without the GTP-U header is sent to the NR base station access network module;
[0014] The NR base station access network module is further configured to store the downlink data packet into a downlink data processing queue corresponding to the downlink tunnel endpoint identifier corresponding to the user equipment identifier based on the received user equipment identifier and the downlink tunnel endpoint identifier corresponding to the downlink data packet; and the NR base station access network module is further configured to send the internal data after removing the GTP-U header to the user equipment.
[0015] The core network module is further configured to send the received downlink data packet to the NR base station distribution module.
[0016] In one of the embodiments, the NR base station distribution module comprises a user plane and a control plane, and the control plane and the user plane are connected through an E1 interface;
[0017] The control plane is configured to send interface signaling to the user plane through the E1 interface.
[0018] The user plane is configured to, when receiving the uplink data packet, parse the received uplink data packet to determine the service type of the data corresponding to the uplink data packet; when the service type is a local service, determine the user equipment IP corresponding to the received uplink data packet based on the received interface signaling, and send the received uplink data packet to the local network corresponding to the user equipment IP based on the user equipment IP corresponding to the received uplink data packet; and when the service type is a public network service, add a GTP-U header to the received uplink data packet for encapsulation, and send the encapsulated uplink data packet to a core network module.
[0019] The user plane is further configured to, when receiving a downlink data packet, detect whether the received downlink data packet is from a local service server; if it is detected that the received downlink data packet is from the local service server, determine the user equipment identifier and the downlink tunnel endpoint identifier corresponding to the downlink data packet based on a user plane instance management table, and send the user equipment identifier and the downlink tunnel endpoint identifier corresponding to the downlink data packet to the NR base station access network module; and if it is detected that the received downlink data packet is from the core network module, perform GTP-U header stripping processing on the downlink data packet to obtain internal data after removing the GTP-U header, and send the internal data after removing the GTP-U header to the NR base station access network module.
[0020] In one of the embodiments, a local distribution service module is deployed in the user plane; the local distribution service module comprises a user plane instance management submodule and a distribution rule engine submodule.
[0021] The user plane instance management submodule is connected with the control plane and the split rule engine submodule, and is configured to construct the user plane instance management table based on the received interface signaling, and send the constructed user plane instance management table to the split rule engine submodule;
[0022] The split rule engine submodule is further connected with the core network module, and is configured to, in the case of receiving the downlink data packet, detect whether the received downlink data packet is from the local service server; if it is detected that the received downlink data packet is from the local service server, determine the user equipment identifier and the downlink tunnel endpoint identifier corresponding to the downlink data packet based on the user plane instance management table, and send the user equipment identifier and the downlink tunnel endpoint identifier corresponding to the downlink data packet to the NR base station access network module; if it is detected that the received downlink data packet is from the core network module, send the downlink data packet to the tunnel management submodule.
[0023] In one of the embodiments, the user plane instance management submodule comprises an initial mapping table construction unit, a user equipment IP acquisition unit, and a construction unit.
[0024] The initial mapping table construction unit is configured to parse the received interface signaling to obtain the user equipment identifier, the downlink tunnel endpoint identifier, and the uplink tunnel endpoint identifier corresponding to each user equipment, and construct an initial mapping table of the user equipment based on the obtained user equipment identifier, downlink tunnel endpoint identifier, and uplink tunnel endpoint identifier corresponding to each user equipment.
[0025] The user equipment IP acquisition unit is configured to obtain the user equipment IP corresponding to each uplink tunnel endpoint identifier based on the initial mapping table and a first uplink data packet; the first uplink data packet is the first service data packet containing a complete GTP-U header and user equipment IP obtained according to the data sent by the user equipment after the session establishment between the user equipment and the NR base station access network module.
[0026] The construction unit is configured to construct the user plane instance management table based on the initial mapping table and the user equipment IP corresponding to each uplink tunnel endpoint identifier.
[0027] In one of the embodiments, the user equipment IP acquisition unit comprises a stripping subunit, a parsing subunit, an address extraction subunit, and a user equipment IP acquisition subunit.
[0028] The peeling sub-unit is configured to peel off the GTP-U header of the first uplink data packet to obtain the GTP-U header and internal data of the first uplink data packet.
[0029] The parsing sub-unit is configured to parse the GTP-U header of the first uplink data packet to obtain the uplink tunnel endpoint identifier corresponding to each user equipment.
[0030] The address extraction sub-unit is configured to extract the user equipment IP of each user equipment in the internal data of the first uplink data packet.
[0031] The user equipment IP obtaining sub-unit is configured to determine the user equipment identifier corresponding to the uplink tunnel endpoint identifier based on the initial mapping table, and bind the user equipment identifier corresponding to the uplink tunnel endpoint identifier with the user equipment IP of each user equipment to obtain the user equipment IP corresponding to each uplink tunnel endpoint identifier.
[0032] In one of the embodiments, the local offloading service module further comprises a tunnel management sub-module.
[0033] The tunnel management sub-module is connected to the offloading rule engine sub-module and the core network module, and is configured to, when the service type is a public network service, add a GTP-U header to the received uplink data packet for encapsulation, and send the encapsulated uplink data packet to the core network module.
[0034] The tunnel management sub-module is further connected to the NR base station access network module, and is further configured to perform GTP-U header processing on the received downlink data packet to obtain internal data after removing the GTP-U header, and send the internal data after removing the GTP-U header to the NR base station access network module.
[0035] In a second aspect, the present application further provides a network offloading method. The method is applied to the network offloading system of the first aspect, and comprises the following steps:
[0036] The NR base station access network module receives the uplink data packet sent by the user equipment, and sends the received uplink data packet to the NR base station offloading module for offloading;
[0037] The NR base station offloading module extracts the key information in the received uplink data packet to obtain the key information of the uplink data packet; the key information includes one or more of user equipment IP, target IP, protocol type, source port, and target port.
[0038] The NR base station distribution module determines a service type corresponding to the uplink data packet based on key information of the uplink data packet and a preset distribution rule library.
[0039] When the service type is a local service, the NR base station distribution module determines a user equipment IP corresponding to the uplink data packet, and sends the uplink data packet to a local network corresponding to the user equipment IP based on the user equipment IP corresponding to the uplink data packet.
[0040] When the service type is a public network service, the NR base station distribution module encapsulates the uplink data packet by adding a GTP-U header, and sends the encapsulated information to a core network module.
[0041] The core network module sends the received encapsulated information to a public network.
[0042] In one embodiment, the method further comprises:
[0043] The NR base station distribution module detects whether a received downlink data packet is from a local service server after receiving the downlink data packet.
[0044] If it is detected that the received downlink data packet is from the local service server, the NR base station distribution module determines a user equipment identifier and a downlink tunnel endpoint identifier corresponding to the downlink data packet based on the user plane instance management table.
[0045] The NR base station access network module puts the downlink data packet into a downlink data processing queue of the user equipment determined by the user equipment identifier based on the user equipment identifier and the downlink tunnel endpoint identifier corresponding to the downlink data packet.
[0046] If it is detected that the received downlink data packet is from the core network module, the NR base station distribution module transmits the received downlink data packet to a user plane for GTP-U header processing to obtain internal data after removing the GTP-U header.
[0047] The NR base station access network module sends the internal data after removing the GTP-U header to the user equipment.
[0048] The network distribution system and the network distribution method include an NR base station access network module and an NR base station distribution module. The NR base station access network module is configured to receive an uplink data packet sent by a user equipment and send the received uplink data packet to the NR base station distribution module. The NR base station distribution module is configured to analyze the received uplink data packet, determine the service type of data corresponding to the uplink data packet, determine the user equipment IP corresponding to the received uplink data packet when the service type is a local service, and send the received uplink data packet to a local network corresponding to the user equipment IP based on the user equipment IP. When the service type of data corresponding to the received uplink data packet is a local service, the network distribution system sends the received uplink data packet to a local network corresponding to the user equipment IP by determining the user equipment IP corresponding to the received uplink data packet. This process only needs to determine the user equipment IP corresponding to the uplink data packet, does not need to track and update the context state of a large number of users in real time, does not need a GTP-U packet header, and only needs to determine the user equipment IP, thereby reducing the process, simplifying the system, solving the problem of the existing network distribution method, and needing to track and update the context state of a large number of users in real time and identify and remove the GTP-U packet header, and reducing the system complexity and overhead.
[0049] The details of one or more embodiments of the present application are presented in the following drawings and description to make other features, objects, and advantages of the present application more apparent. BRIEF DESCRIPTION OF DRAWINGS
[0050] The accompanying drawings, which are included to provide a further understanding of the present application, constitute a part of the present application and illustrate exemplary embodiments of the present application and its description, which serve to explain the present application and do not constitute an improper limitation on the present application. In the drawings:
[0051] Figure 1 A first structural block diagram of a network distribution system according to an embodiment of the present application is provided.
[0052] Figure 2 A second structural block diagram of a network distribution system according to an embodiment of the present application is provided.
[0053] Figure 3 A third structural block diagram of a network distribution system according to an embodiment of the present application is provided.
[0054] Figure 4 A hardware structural block diagram of a terminal of a network distribution method according to an embodiment of the present application is provided.
[0055] Figure 5 A first flowchart of a network distribution method according to an embodiment of the present application is provided.
[0056] Figure 6A second flowchart of the network offloading method provided by an embodiment of the present application. DETAILED DESCRIPTION
[0057] In order to more clearly understand the objects, technical solutions and advantages of the present application, the present application will be described and explained in detail below in conjunction with the accompanying drawings and embodiments.
[0058] Unless otherwise defined, technical terms or scientific terms used in the present application shall have the general meaning understood by one of ordinary skill in the art to which the present application pertains. In the present application, the terms "one", "a", "an", "the", "these", and the like similar words do not represent a quantitative limitation, but can be singular or plural. In the present application, the terms "include", "contain", "have" and any variants thereof are intended to cover non-exclusive inclusion; for example, a process, method and system, product or device containing a series of steps or modules (units) are not limited to the listed steps or modules (units), but can include steps or modules (units) not listed, or can include other steps or modules (units) inherent to the process, method, product or device. In the present application, the terms "connected", "connected", "coupled" and the like similar words are not limited to physical or mechanical connections, but can include electrical connections, whether direct or indirect. In the present application, "multiple" means two or more. The association between the associated objects is described by the term "and / or", which means that there can be three relationships, for example, "A and / or B" can mean that A exists alone, A and B exist together, and B exists alone. In general, the character " / " represents an "or" relationship between the objects before and after it. In the present application, the terms "first", "second", "third" and the like are only used to distinguish similar objects, and do not represent a specific order of the objects.
[0059] Reference Figure 1 , Figure 1 is a first structural block diagram of the network offloading system provided by an embodiment of the present application, as shown in Figure 1 The network offloading system comprises an NR base station access network module 11 and an NR base station offloading module 12. The NR base station access network module 11 is connected to the user equipment 10 and the NR base station offloading module 12 respectively, and is configured to receive the uplink data packet sent by the user equipment 10, and send the received uplink data packet to the NR base station offloading module 12. The NR base station offloading module 12 is configured to analyze the received uplink data packet, determine the service type of the data corresponding to the uplink data packet, determine the user equipment IP (Internet Protocol) corresponding to the received uplink data packet when the service type is a local service, and send the received uplink data packet to the local network 13 corresponding to the user equipment IP based on the user equipment IP.
[0060] The NR base station access network module 11 includes a PHY (Physical Layer) and a DU (Distributed Unit). The PHY is responsible for the conversion between digital signals and physical media (such as electromagnetic waves, optical signals), and is used to drive the Radio Unit to complete physical layer operations such as signal modulation, demodulation, channel coding, etc. The PHY function is usually executed by an FPGA (Field-Programmable Gate Array) or ASIC (Application-Specific Integrated Circuit) chip inside the DU, which directly drives the Radio Unit. The specific application process of the PHY can be represented as follows: in the downlink, the MAC (Medium Access Control) layer of the DU issues a scheduling instruction to the PHY, the PHY generates modulated data based on the scheduling instruction, and drives the Radio Unit to perform radio frequency transmission of the generated modulated data. In the uplink, the Radio Unit receives the signal and converts it into an electrical signal, the PHY layer demodulates and decodes the electrical signal, and then transmits the decoded data to the MAC layer, which performs data recombination processing on the decoded data. In addition, the DU is a core component of the 5G base station (gNB) and is responsible for processing bottom-layer protocol functions with high real-time requirements (such as scheduling PHY hardware resources and executing physical layer functions). Because the DU can be deployed close to the user equipment end, it can reduce air interface transmission delay, so in the MEC (Multi-Access Edge Computing) scenario, the DU can be used as a local service offloading anchor point to achieve low-latency data direct transmission. The uplink is the data transmission direction from the user equipment 10 to the network side. The network side can include a public network and a local network. The downlink is the data transmission direction from the network side to the user equipment 10. The user equipment 10 can also be referred to as a terminal. The user equipment 10 includes but is not limited to a mobile phone, a tablet, a watch, a vehicle-mounted T-Box, a smart meter, an AGV (Automated Guided Vehicle Controller) controller, etc. The uplink data packet can be data sent by the user equipment 10 to the NR base station access network module 11 in the uplink.
[0061] Based on this, the process that the NR base station access network module 11 receives the uplink data packet sent by the user equipment 10 and sends the received uplink data packet to the NR base station distribution module 12 can be: the DU generates a scheduling instruction according to the channel state information, service demand and network policy of the user equipment 10, and sends it to the PHY, the PHY layer receives the wireless signal (uplink data packet) from the user equipment 10 based on the scheduling instruction, down-converts it to a baseband signal, and performs demodulation and decoding processing, restores the original data of the uplink data packet sent by the user equipment 10, and then sends the original data to the DU, and the DU receives the original data, performs data reorganization, error detection and correction on the original data, and sends the processed data to the NR base station distribution module 12.
[0062] Further, the service type can include local services and public network services. The local service refers to services provided in a specific local area or within an enterprise. These services are usually managed by the enterprise or organization itself to meet the needs of its internal users. The local service can be a service with limited scope, such as hospital services, school services, factory services, and services within a specific area. The public network service can refer to services provided to the public, which are provided through a public network (such as the Internet) and can be accessed by any user. The public network can include Internet services such as social media platforms, online shopping platforms, video streaming services, etc. It can include public services such as e-government platforms, online education platforms, online medical platforms, etc. It can include mobile applications such as mobile payment applications, navigation applications (navigation maps), etc.
[0063] In the embodiment, the NR base station offloading module 12 is configured to analyze the received uplink data packet, and determine the service type of the data corresponding to the uplink data packet. The specific process can be that the offloading rule engine submodule in the NR base station offloading module 12 first analyzes the received uplink data packet, then extracts the key information in the uplink data packet, and then matches the extracted key information based on the preset offloading rule, and determines the service type of the data corresponding to the uplink data packet based on the matching result. The key information can include at least two of IP quintuple, DNN (Data Network Name) and geographic location information. The IP quintuple can include user equipment IP address, destination IP address, source port number, destination port number and transmission protocol. The DNN can be used to identify a specific network service connected by the user equipment 10. The geographic location information is the current location information of the user equipment 10, which can be obtained through the geographic location of the base station or the GPS (Global Positioning System) information reported by the user equipment 10. The preset offloading rule can be a preset offloading rule library, and can be a multi-dimensional matching strategy. The specific multi-dimensional matching strategy can be at least two dimensions of IP quintuple matching, DNN matching and geographic location matching. The IP quintuple matching can be checking whether the IP quintuple of the uplink data packet matches the preset local service or public network service rule. For example, if a specific IP address range or port number matches the preset local service, the uplink data packet is allocated to the local service. The DNN matching can be checking whether the DNN in the uplink data packet matches the preset local service or public network service rule. For example, some DNNs can be allocated to the enterprise internal network, and other DNNs are used for public network access. The geographic location matching can be checking whether the geographic location of the user equipment 10 is within the preset local service coverage range. For example, if the user equipment 10 is located in the enterprise park, the uplink data packet sent by the user equipment 10 is identified as a local service.
[0064] In the embodiment, when the service type is a local service, the NR base station distribution module 12 needs to determine the user equipment IP corresponding to the received uplink data packet, and send the received uplink data packet to the local network 13 corresponding to the user equipment IP based on the user equipment IP. The process of determining the user equipment IP corresponding to the received uplink data packet by the NR base station distribution module 12 can be that the NR base station distribution module 12 constructs a user plane instance management table (a corresponding relationship table of the user equipment identifier of each user equipment 10, the downlink tunnel endpoint identifier, the uplink tunnel endpoint identifier, and the user equipment IP) based on the received interface signaling in advance, and then, based on the obtained uplink data packet, the user equipment IP corresponding to the uplink tunnel endpoint identifier of the uplink data packet is found in the user plane instance management table based on the extracted uplink tunnel endpoint identifier of the uplink data packet, and the found user equipment IP is determined as the user equipment IP corresponding to the uplink data packet.
[0065] The network distribution system described above, when the data service type corresponding to the received uplink data packet is a local service, determines the user equipment IP corresponding to the received uplink data packet, and sends the received uplink data packet to the local network 13 corresponding to the user equipment IP. This process only needs to determine the user equipment IP corresponding to the uplink data packet, does not need to track and update the context state of a large number of users in real time, does not need the GTP-U packet header, does not need to pass through the core network module, and only needs to determine the user equipment IP to directly transmit to the local network 13, reducing the process and simplifying the system. The existing network distribution method needs to track and update the context state of a large number of users in real time, and identify and remove the GTP-U packet header, which has the problems of complex system and large overhead. Moreover, this method avoids GTP-U header encapsulation and N3 interface transmission delay, and reduces the end-to-end delay by about 30%.
[0066] In addition, in one embodiment, Figure 2 The second structural block diagram of the network distribution system provided for an embodiment of the application is shown in Figure 2 The system further includes a core network module 14, an NR base station distribution module 12 connected to the core network module 14, and configured to, when the service type is a public network service, add a GTP-U header to encapsulate the received uplink data packet, and send the encapsulated uplink data packet to the core network module 14. The core network module 14 is configured to send the received encapsulated uplink data packet to the public network 15.
[0067] The core network module 14 includes at least an SMF (Session Management Function) and a UPF (User Plane Function). The SMF is connected to the UPF through an N4 interface. The SMF is configured to create, modify or release a user session (PDU session) and uniformly control data forwarding rules of the UPF. The UPF is configured to receive data of an uplink data packet forwarded by the NR base station distribution module 12, add a GTP-U header to the received data of the uplink data packet, and route the data with the added GTP-U header to the public network 15 through an N6 interface. The GTP-U header includes at least a tunnel endpoint identifier and a tunnel identifier. The embodiment ensures compatibility with a core network protocol stack by reserving an original IP packet structure and adding only a GTP-U encapsulation layer.
[0068] Further, in an embodiment, the NR base station distribution module 12 is further configured to, after receiving a downlink data packet, detect whether the received downlink data packet is from a local service server. If it is detected that the downlink data packet is from the local service server, determine a user equipment identifier and a downlink tunnel endpoint identifier corresponding to the downlink data packet based on a user plane instance management table, and send the user equipment identifier and the downlink tunnel endpoint identifier corresponding to the downlink data packet to the NR base station access network module 11. The user plane instance management table is a correspondence table of user equipment identifiers, downlink tunnel endpoint identifiers, uplink tunnel endpoint identifiers and user equipment IPs of each user equipment 10. If it is detected that the downlink data packet is from the core network module 14, the downlink data packet is transmitted to a user plane for GTP-U header stripping processing to obtain internal data without the GTP-U header, and the internal data without the GTP-U header is sent to the NR base station access network module 11. The NR base station access network module 11 is further configured to, based on the received user equipment identifier and the downlink tunnel endpoint identifier corresponding to the downlink data packet, store the downlink data packet in a downlink data processing queue corresponding to the downlink tunnel endpoint identifier of the user equipment identifier. The NR base station access network module 11 is further configured to send the internal data without the GTP-U header to the user equipment 10. The core network module 14 is further configured to send the received downlink data packet to the NR base station distribution module 12.
[0069] In the embodiment, the local service server can be a computing or storage node of the access local network 13, carrying a localized service application (such as a MEC platform, a database, etc.). Since the NR base station distribution module 12 and the UPF of the core network module 14 are connected through the N3 interface, the process of detecting whether the received downlink data packet is from the local service server by the NR base station distribution module 12 after receiving the downlink data packet can be: after receiving the downlink data packet, the NR base station distribution module 12 first judges whether the downlink data packet is transmitted to the NR base station distribution module 12 through the N3 interface. If it is transmitted through the N3 interface, it is detected that the received downlink data packet is from the core network module 14. If it is not transmitted through the N3 interface, it is detected that the received downlink data packet is from the local service server. When it is detected that the downlink data packet is from the local service server, the specific process of determining the user equipment identifier and the downlink tunnel endpoint identifier corresponding to the downlink data packet based on the user plane instance management table can be: when the downlink data packet is from the local service server, the user equipment IP in the original IP packet of the downlink data packet can be directly read. Then, based on the read user equipment IP, the user plane instance management table is used to read the user equipment identifier and the downlink tunnel endpoint identifier corresponding to the user equipment IP from the user plane instance management table, and the read user equipment identifier and the downlink tunnel endpoint identifier are determined as the user equipment identifier and the downlink tunnel endpoint identifier corresponding to the downlink data packet. The downlink data packet can be data sent by the network side to the user equipment 10 in the downlink.
[0070] Table 1 is an example of a user plane instance management table. As shown in Table 1, the user plane instance management table includes three user equipments: user equipment 1, user equipment 2 and user equipment 3. The correspondence between the user equipment identifier, the downlink tunnel endpoint identifier, the uplink tunnel endpoint identifier and the user equipment IP of each user equipment is shown in Table 1.
[0071] Table 1
[0072]
[0073] In the embodiment, the NR base station access network module 11 stores the downlink data packet into the downlink data processing queue corresponding to the downlink tunnel endpoint identifier corresponding to the user equipment identifier based on the received user equipment identifier and downlink tunnel endpoint identifier corresponding to the downlink data packet. The queue management unit can be set in the NR base station access network module 11. The queue management unit is used to store the downlink data packet corresponding to each downlink tunnel endpoint identifier to be sent to the user equipment 10 (i.e. the downlink data processing queue of the downlink tunnel endpoint identifier) and maintain the downlink data processing queue of the downlink tunnel endpoint identifier. When the user equipment identifier and the downlink tunnel endpoint identifier corresponding to the downlink data packet are obtained, the queue management unit is used to store the obtained downlink data packet into the downlink data processing queue of the downlink tunnel endpoint identifier corresponding to the user equipment identifier of the downlink data packet. The user plane directly transmits the downlink data packet to the user equipment 10 through the N3 interface tunnel according to the downlink tunnel endpoint identifier, bypasses the core network processing, and the delay can be shortened to 2-5 ms. In addition, the local data does not add a tunnel header, reduces the protocol processing overhead by 30%, and bypasses the N3 interface transmission delay through the direct channel of the base station and the local server. In the industrial Internet of Things scene, the local service delay is reduced by more than 40%, and the load pressure of the core network is reduced by 30%.
[0074] In some cases, the uplink data packet needs to be transmitted from the local network 13 to the public network 15 after being transmitted to the local network 13. In this case, the local network 13 and the public network 15 are connected.
[0075] Figure 3 is a third structural block diagram of the network distribution system provided by an embodiment of the application, like Figure 3As shown, the NR base station shunting module 12 includes a user plane 122 and a control plane 124, and the control plane 124 and the user plane 122 are connected through an E1 interface; the control plane 124 is configured to send interface signaling to the user plane 122 through the E1 interface; the user plane 122 is configured to, when receiving an uplink data packet, parse the received uplink data packet, determine the service type of the data corresponding to the uplink data packet; when the service type is a local service, determine the user equipment IP corresponding to the received uplink data packet based on the received interface signaling, and send the received uplink data packet to the local network 13 corresponding to the user equipment IP based on the user equipment IP corresponding to the received uplink data packet; when the service type is a public network service, encapsulate the received uplink data packet by adding a GTP-U header, and send the encapsulated uplink data packet to the core network module 14; the user plane 122 is further configured to, in the case of receiving a downlink data packet, detect whether the received downlink data packet is from a local service server; if it is detected that the received downlink data packet is from a local service server, determine the user equipment identifier and the downlink tunnel endpoint identifier corresponding to the above-mentioned downlink data packet based on the above-mentioned user plane instance management table, and send the user equipment identifier and the downlink tunnel endpoint identifier corresponding to the above-mentioned downlink data packet to the NR base station access network module 11; if it is detected that the received downlink data packet is from the core network module 14, perform GTP-U header stripping processing on the downlink data packet to obtain internal data after removing the GTP-U header, and send the above-mentioned internal data after removing the GTP-U header to the NR base station access network module 11.
[0076] The above-mentioned interface signaling is a key mechanism for communication between the control plane 124 and the user plane 122, used for coordinating and managing the processing and transmission of data packets. The above-mentioned user plane 122 and control plane 124 are respectively connected with the NR base station access network module 11 and the core network module, and the user plane 122 is in communication connection with the AMF (Access and Mobility Management Function) of the core network module 14 through an N2 interface. The control plane 124 is in communication connection with the UPF of the core network module 14 through an N3 interface, and is connected with the local network 13 through an N6 interface.
[0077] The above-mentioned network shunting system still uses the original NR standard interface processing flow, and the normal access, authentication, service initiation, and handover processes of the terminal are handled by the original N2 interface. Whether the service is a local service or a public network service, the control of the terminal user is still responsible by the core network, thereby ensuring that the local shunting scheme based on the MEC in the NR base station is transparent to the existing network and terminal.
[0078] In addition, the embodiment creates or updates rules and parameters required by the user plane 122 for forwarding through the E1 interface signaling (8.3 section of the bearer context management process) defined by the 3GPP 38.463 protocol, to support the base station offloading module to implement local service intelligent routing.
[0079] In one embodiment, a local offloading service module is deployed in the user plane 122; the local offloading service module includes a user plane instance management submodule and an offloading rule engine submodule; the user plane instance management submodule is connected to the control plane 124 and the offloading rule engine submodule, and is used to construct a user plane instance management table based on the received interface signaling, and send the constructed user plane instance management table to the offloading rule engine submodule; the offloading rule engine submodule is connected to the NR base station access network module 11, and is used to parse the received uplink data packet, and determine the service type of the data corresponding to the uplink data packet; when the service type is a local service, determine the user equipment IP corresponding to the received uplink data packet based on the received user plane instance management table, and send the received uplink data packet to the local network 13 corresponding to the user equipment IP. The offloading rule engine submodule is also connected to the core network module, and is used to detect whether the received downlink data packet is from a local service server when the downlink data packet is received; if it is detected that the received downlink data packet is from the local service server, determine the user equipment identifier and the downlink tunnel endpoint identifier corresponding to the downlink data packet based on the user plane instance management table, and send the user equipment identifier and the downlink tunnel endpoint identifier corresponding to the downlink data packet to the NR base station access network module; if it is detected that the received downlink data packet is from the core network module, send the downlink data packet to the tunnel management submodule.
[0080] The above local offloading service module is used to offload the uplink data packet directly to the local network 13 when the service type is a local service. Through the setting of the local offloading service module, when the service type is a local service, the uplink data packet does not need to pass through the core network, at this time, the local service offloading not only reduces the backhaul bandwidth consumption, but also reduces the service access delay due to the close deployment of the local service, and improves the service experience of the user.
[0081] In another embodiment, the user plane instance management submodule comprises: an initial mapping table construction unit, a user equipment IP acquisition unit and a construction unit; the initial mapping table construction unit is configured to parse the received interface signaling to obtain the user equipment identifier, the downlink tunnel endpoint identifier and the uplink tunnel endpoint identifier corresponding to each user equipment 10, and to construct an initial mapping table of the user equipment 10 based on the obtained user equipment identifier, the downlink tunnel endpoint identifier and the uplink tunnel endpoint identifier corresponding to each user equipment 10; the user equipment IP acquisition unit is configured to obtain the user equipment IP corresponding to each uplink tunnel endpoint identifier based on the initial mapping table and a first uplink data packet; the first uplink data packet is the first service data packet containing a complete GTP-U header and the user equipment IP obtained according to the data sent by the user equipment 10 after the user equipment 10 and the NR base station access network module 11 establish a session; and the construction unit is configured to construct a user plane instance management table based on the initial mapping table and the user equipment IP corresponding to each uplink tunnel endpoint identifier.
[0082] The initial mapping table of the user equipment 10 described above can be a correspondence table of the user equipment identifier, the downlink tunnel endpoint identifier and the uplink tunnel endpoint identifier corresponding to the user equipment 10. Table 2 is an example of an initial mapping table of a user equipment, as shown in Table 2, which includes three user equipments: user equipment 1, user equipment 2 and user equipment 3, and the correspondence of the user equipment identifier, the downlink tunnel endpoint identifier and the uplink tunnel endpoint identifier of each user equipment is shown in Table 2, in which the user equipment IP is unknown.
[0083] Table 2
[0084]
[0085] In the embodiment, the user equipment IP obtaining unit obtains the user equipment IP corresponding to each uplink tunnel endpoint identifier based on the initial mapping table and the first received uplink data packet. The user equipment IP corresponding to each uplink tunnel endpoint identifier can be obtained by stripping the GTP-U header of the first received uplink data packet and parsing the GTP-U header of the first received uplink data packet to obtain the uplink tunnel endpoint identifier corresponding to the user equipment 10, determining the mapping relationship between the uplink tunnel endpoint identifier and the user equipment IP, and obtaining the user equipment IP corresponding to each uplink tunnel endpoint identifier. The first received uplink data packet can be the data packet of the first public network service after the session establishment between the user equipment 10 and the NR base station access network module 11, that is, the first service data packet containing a complete GTP-U header and a user equipment IP. When the uplink data packet is a data packet corresponding to a public network service, the data packet needs to be processed by adding a GTP-U header. At this time, the data packet is service data containing a complete GTP-U header and a user equipment. Therefore, the user equipment IP corresponding to each uplink tunnel endpoint identifier can be obtained by using the data packet of the first public network service after the session establishment between the user equipment 10 and the NR base station access network module 11.
[0086] Further, in another embodiment, the user equipment IP obtaining unit comprises a stripping subunit, a parsing subunit, an address extraction subunit, and a user equipment IP obtaining subunit. The stripping subunit is configured to strip the GTP-U header of the first received uplink data packet to obtain the GTP-U header of the first received uplink data packet and internal data. The parsing subunit is configured to parse the GTP-U header of the first received uplink data packet to obtain the uplink tunnel endpoint identifier corresponding to each user equipment 10. The address extraction subunit is configured to extract the user equipment IP of each user equipment 10 in the internal data of the first received uplink data packet. The user equipment IP obtaining subunit is configured to determine the user equipment identifier corresponding to the uplink tunnel endpoint identifier based on the initial mapping table, and bind the user equipment identifier corresponding to the uplink tunnel endpoint identifier with the user equipment IP of each user equipment 10 to obtain the user equipment IP corresponding to each uplink tunnel endpoint identifier.
[0087] In another embodiment, the local offloading service module further comprises a tunnel management sub-module. The tunnel management sub-module is connected to the offloading rule engine sub-module and the core network module 14, and is configured to add a GTP-U header to the received uplink data packet for encapsulation when the service type is a public network service, and send the encapsulated uplink data packet to the core network module 14. The tunnel management sub-module is also connected to the NR base station access network module, and is further configured to parse the GTP-U header of the received downlink data packet to obtain internal data after removing the GTP-U header, and send the internal data after removing the GTP-U header to the NR base station access network module.
[0088] The method embodiments provided in the present embodiment can be executed in a terminal, a computer or a similar computing device. For example, the method embodiments are executed on a terminal, Figure 4 is a hardware structure block diagram of a terminal of the network splitting method of the present embodiment. As shown in Figure 4 , the terminal can include one or more (only one is shown in Figure 4 ) processor 402 and memory 404 for storing data, wherein the processor 402 can include but not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA. The terminal can further include a transmission device 406 for communication function and an input / output device 408. Those skilled in the art can understand that Figure 4 the structure shown is only schematic, which does not limit the structure of the terminal. For example, the terminal can further include more or less components than those shown in Figure 4 , or have a different configuration from that shown in Figure 4 .
[0089] The memory 404 can be used to store computer programs, such as software programs of application software and modules, such as the computer program corresponding to the network splitting method in the present embodiment. The processor 402 executes various functional applications and data processing by running the computer programs stored in the memory 404, i.e. implements the method described above. The memory 404 can include a high-speed random access memory, and can further include a non-volatile memory, such as one or more magnetic storage devices, flash memories, or other non-volatile solid-state memories. In some examples, the memory 404 can further include a memory remotely arranged with respect to the processor 402, which can be connected to the terminal through a network. Examples of the network include but are not limited to the public network 15, an enterprise intranet, a local area network, a mobile communication network, and combinations thereof.
[0090] The transmission device 406 is used to receive or send data via a network. The network includes a wireless network provided by a communication provider of the terminal. In one example, the transmission device 406 includes a network adapter (Network Interface Controller, NIC) which can be connected to other network devices through a base station so as to communicate with the public network 15. In one example, the transmission device 406 can be a radio frequency (Radio Frequency, RF) module which can communicate with the public network 15 in a wireless manner.
[0091] In the present embodiment, a network splitting method is provided, Figure 5 is a first flowchart of the network splitting method of the present embodiment, as shown in Figure 5 , the flowchart includes the following steps:
[0092] Step S1, the NR base station access network module 11 receives the uplink data packet sent by the user equipment 10, and sends the received uplink data packet to the NR base station distribution module 12 for distribution;
[0093] Step S2, the key information in the received uplink data packet is extracted by using the NR base station distribution module 12, and the key information of the uplink data packet is obtained; the key information includes one or more of user equipment IP, target IP, protocol type, source port and target port;
[0094] Step S3, the NR base station distribution module 12 determines the service type corresponding to the uplink data packet based on the key information of the uplink data packet and the preset distribution rule library;
[0095] The above-mentioned preset distribution rule library can be a public network service rule library and a local service rule library corresponding to a multi-dimensional matching strategy.
[0096] Step S4, when the service type is a local service, the NR base station distribution module 12 determines the user equipment IP corresponding to the uplink data packet, and sends the uplink data packet to the local network 13 corresponding to the user equipment IP based on the user equipment IP corresponding to the uplink data packet;
[0097] Step S5, when the service type is a public network service, the NR base station distribution module 12 adds GTP-U header to encapsulate the uplink data packet, and sends the encapsulated information to the core network module 14;
[0098] The above-mentioned NR base station distribution module 12 adds GTP-U header to encapsulate the internal information of the uplink data packet, which can be adding GTP-U header to encapsulate the received uplink data packet by using the tunnel management sub-module of the local distribution service module deployed in the user plane 122 of the NR base station distribution module 12.
[0099] Step S6, the core network module 14 sends the received encapsulated information to the public network 15.
[0100] The steps S1 to S6 introduce the uplink data processing process. The key information in the uplink data packet is extracted by the NR base station shunting module 12. Based on the extracted key information and the preset shunting rule library, the service type of the uplink data packet is determined. If the service type is a local service, the NR base station shunting module 12 sends the data packet to the corresponding local network 13 according to the user equipment IP. This process does not require the participation of the core network. If the service type is a public network service, the NR base station shunting module 12 encapsulates the data packet by adding a GTP-U header, and sends the encapsulated data to the core network module 14. The core network module 14 sends the encapsulated data to the public network 15. By performing data shunting at the base station level, the local service and the public network service can be quickly distinguished. For the local service, the data is directly routed to the local network 13 at the base station level, avoiding the detour of the core network. The transmission hop count is reduced, and the end-to-end delay is reduced from milliseconds to sub-milliseconds, which is especially suitable for time-sensitive applications. Only public network services are transmitted through the core network, while local services are terminated at the base station side. In this way, the data traffic and processing pressure of the core network are reduced, and the core network bandwidth resources can be saved. By removing the GTP-U header and re-encapsulating only for public network services, the redundant protocol overhead is reduced, and the bandwidth demand of the backhaul network is reduced. In addition, the local service does not need to pass through the expensive core network link, reducing the operator transmission cost.
[0101] In one embodiment, Figure 6 is a second flowchart of the network shunting method of the present embodiment, as shown in Figure 6 The flowchart includes the following steps:
[0102] Step S7, after receiving the downlink data packet, the NR base station shunting module 12 detects whether the received downlink data packet is from a local service server;
[0103] Step S8, if it is detected that the received downlink data packet is from a local service server, the NR base station shunting module 12 determines the user equipment identifier and the downlink tunnel endpoint identifier corresponding to the downlink data packet based on the user plane instance management table;
[0104] Step S9, the NR base station access network module 11 puts the downlink data packet into the downlink data processing queue of the user equipment 10 determined by the user equipment identifier based on the user equipment identifier and the downlink tunnel endpoint identifier corresponding to the downlink data packet;
[0105] Step S10, if it is detected that the received downlink data packet is from the core network module 14, the NR base station shunting module 12 transmits the received downlink data packet to the user plane 122 for GTP-U header processing to obtain the internal data after removing the GTP-U header;
[0106] Step S11, the NR base station access network module 11 sends the internal data after removing the GTP-U header to the user equipment 10.
[0107] The above steps S7 to S11 introduce the downlink data processing process. After receiving the downlink data packet through the NR base station distribution module 12, first detect its source. Based on different sources, if it is detected that the received downlink data packet is from the local service server, the NR base station distribution module 12 will put the downlink data packet into the downlink data processing queue of the user equipment 10 determined by the user equipment identifier based on the user plane instance management table; If it is detected that the received downlink data packet is from the core network module 14, the NR base station distribution module 12 will transmit the received downlink data packet to the user plane 122 for GTP-U header analysis processing, and send the internal data after removing the GTP-U header to the user equipment 10. For local service GTP-U encapsulation or decapsulation and core network forwarding link, it is not necessary to pass through the expensive core network link, which reduces the operator transmission cost.
[0108] It should be understood that, although each step in the flowchart involved in each embodiment as described above is displayed in sequence according to the arrow, these steps are not necessarily executed in sequence according to the arrow. Unless otherwise specified herein, the execution of these steps has no strict order limitation, and these steps can be executed in other orders. Moreover, at least part of the steps in the flowchart involved in each embodiment as described above can include multiple steps or stages, which are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily sequential, but can be alternately or alternately executed with at least part of other steps or steps or stages in other steps.
[0109] It should be noted that each of the above modules can be a functional module or a program module, which can be implemented by software or hardware. For the module implemented by hardware, each of the above modules can be located in the same processor; or each of the above modules can also be located in different processors in any combination.
[0110] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a non-volatile computer readable storage medium, and when the computer program is executed, the processes of the above-mentioned embodiments of the methods can be included. Any reference to memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical storage, high-density embedded non-volatile memory, resistive memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration but not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM), etc. The database involved in the embodiments provided in the present application can include at least one of a relational database and a non-relational database. The non-relational database can include a distributed database based on a block chain, etc., without being limited thereto. The processor involved in the embodiments provided in the present application can be a general-purpose processor, a central processing unit, a graphics processing unit, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, etc., without being limited thereto.
[0111] Any combination of the technical features of the above embodiments can be made. In order to make the description simple, all possible combinations of the technical features in the above embodiments are not described, however, as long as the combination of the technical features does not exist, it should be considered as the scope of the present application.
[0112] The above embodiments only express several implementation manners of the present application, and the description is more specific and detailed, but it should not be understood as a limitation on the scope of the patent of the present application. It should be pointed out that for ordinary skilled in the art, without departing from the concept of the present application, a number of modifications and improvements can be made, which are within the scope of protection of the present application. Therefore, the protection scope of the present application should be subject to the appended claims.
Claims
1. A network traffic distribution system, characterized in that: The system includes: an NR base station access network module and an NR base station offload module; The NR base station access network module is connected to the user equipment and the NR base station offload module, respectively, and is used to receive the uplink data packet sent by the user equipment and send the received uplink data packet to the NR base station offload module; The NR base station offload module includes a user plane and a control plane, and the control plane and the user plane are connected through an E1 interface; the control plane is used to send interface signaling to the user plane through the E1 interface; the user plane is used to parse the received uplink data packet when receiving the uplink data packet, and determine the service type of the data corresponding to the uplink data packet; when the service type is a local service, based on the received interface signaling, determine the user equipment IP corresponding to the received uplink data packet, and based on the user equipment IP corresponding to the received uplink data packet, send the received uplink data packet to the local network corresponding to the user equipment IP; when the service type is a public network service, add a GTP-U header to the received uplink data packet for encapsulation, and encapsulate the encapsulated data packet The uplink data packet is sent to the core network module; the user plane is also used to detect whether the received downlink data packet comes from the local business server when a downlink data packet is received; if it is detected that the received downlink data packet comes from the local business server, the user equipment identifier and the downlink tunnel endpoint identifier corresponding to the downlink data packet are determined based on the user plane instance management table, and the user equipment identifier and the downlink tunnel endpoint identifier corresponding to the downlink data packet are sent to the NR base station access network module; if it is detected that the received downlink data packet comes from the core network module, the downlink data packet is stripped of the GTP-U header to obtain the internal data after the GTP-U header is removed, and the internal data after the GTP-U header is removed is sent to the NR base station access network module.
2. The network traffic distribution system according to claim 1, characterized in that: The system further includes the core network module; The NR base station offload module is connected to the core network module and is further configured to, when the service type is a public network service, add a GTP-U header to the received uplink data packet for encapsulation, and send the encapsulated uplink data packet to the core network module; The core network module is used to send the received encapsulated uplink data packet to the public network.
3. The network traffic distribution system according to claim 2, wherein: The NR base station offload module is further configured to, after receiving a downlink data packet, detect whether the received downlink data packet originates from a local service server; if it is detected that the downlink data packet originates from the local service server, determine, based on the user plane instance management table, a user equipment identifier and a downlink tunnel endpoint identifier corresponding to the downlink data packet, and send the user equipment identifier and the downlink tunnel endpoint identifier corresponding to the downlink data packet to the NR base station access network module; The user plane instance management table is a correspondence table of the user equipment identifier, downlink tunnel endpoint identifier, uplink tunnel endpoint identifier and the user equipment IP of each user equipment; If it is detected that the downlink data packet originates from the core network module, the downlink data packet is transparently transmitted to the user plane for GTP-U header stripping processing, the internal data after the GTP-U header is removed is obtained, and the internal data after the GTP-U header is removed is sent to the NR base station access network module; The NR base station access network module is further configured to, based on the user equipment identifier and the downlink tunnel endpoint identifier corresponding to the received downlink data packet, store the downlink data packet in a downlink data processing queue of the downlink tunnel endpoint identifier corresponding to the user equipment identifier; The NR base station access network module is further configured to send the internal data after removing the GTP-U header to the user equipment; The core network module is also used to send the received downlink data packet to the NR base station offload module.
4. The network traffic distribution system according to claim 1, wherein: A local offload service module is deployed in the user plane; The local offload service module includes: a user plane instance management submodule and a offload rule engine submodule; The user plane instance management submodule is connected to the control plane and the offload rule engine submodule, and is used to construct the user plane instance management table based on the received interface signaling, and send the constructed user plane instance management table to the offload rule engine submodule; The offload rule engine submodule is connected to the NR base station access network module and is configured to parse the received uplink data packet and determine the service type of the data corresponding to the uplink data packet; when the service type is a local service, determine the user equipment IP corresponding to the received uplink data packet based on the received user plane instance management table; based on the user equipment IP corresponding to the received uplink data packet, send the received uplink data packet to the local network corresponding to the user equipment IP; The diversion rule engine submodule is also connected to the core network module, and is used to detect whether the received downlink data packet originates from the local business server when the downlink data packet is received; if it is detected that the received downlink data packet originates from the local business server, the user equipment identifier and downlink tunnel endpoint identifier corresponding to the downlink data packet are determined based on the user plane instance management table, and the user equipment identifier and the downlink tunnel endpoint identifier corresponding to the downlink data packet are sent to the NR base station access network module; if it is detected that the received downlink data packet originates from the core network module, the downlink data packet is sent to the tunnel management submodule.
5. The network traffic distribution system according to claim 4, characterized in that: The user plane instance management submodule includes: an initial mapping table construction unit, a user equipment IP acquisition unit and a construction unit; an initial mapping table construction unit, configured to parse the received interface signaling to obtain the user equipment identifier, the downlink tunnel endpoint identifier, and the uplink tunnel endpoint identifier corresponding to each of the user equipments, and construct an initial mapping table for the user equipment based on the obtained user equipment identifier, the downlink tunnel endpoint identifier, and the uplink tunnel endpoint identifier corresponding to each of the user equipments; The user equipment IP acquisition unit is configured to obtain the user equipment IP corresponding to each uplink tunnel endpoint identifier based on the initial mapping table and the first uplink data packet; the first uplink data packet is the first service data packet including a complete GTP-U header and a user equipment IP obtained based on data sent by the user equipment after a session between the user equipment and the NR base station access network module is established; The construction unit is configured to construct the user plane instance management table based on the initial mapping table and the user equipment IP corresponding to each uplink tunnel endpoint identifier.
6. The network traffic distribution system according to claim 5, characterized in that: The user equipment IP acquisition unit includes: a stripping subunit, a parsing subunit, an address extraction subunit and a user equipment IP acquisition subunit; The stripping subunit is configured to strip the GTP-U header of the first uplink data packet to obtain the GTP-U header and internal data of the first uplink data packet; The parsing subunit is configured to parse the GTP-U header of the first uplink data packet to obtain an uplink tunnel endpoint identifier corresponding to each of the user equipments; The address extraction subunit is configured to extract the user equipment IP address of each user equipment from the internal data of the first uplink data packet; The user equipment IP acquisition subunit is used to determine the user equipment identifier corresponding to the uplink tunnel endpoint identifier based on the initial mapping table, and bind the user equipment identifier corresponding to the uplink tunnel endpoint identifier with the user equipment IP of each user equipment to obtain the user equipment IP corresponding to each uplink tunnel endpoint identifier.
7. The network traffic distribution system according to claim 4, characterized in that: The local offload service module further includes a tunnel management submodule; The tunnel management submodule is connected to the diversion rule engine submodule and the core network module, and is used to add a GTP-U header to the received uplink data packet for encapsulation when the service type is a public network service, and send the encapsulated uplink data packet to the core network module; The tunnel management submodule is also connected to the NR base station access network module, and is also used to parse the GTP-U header of the received downlink data packet to obtain the internal data after removing the GTP-U header, and send the internal data after removing the GTP-U header to the NR base station access network module.
8. A network traffic distribution method, applied to the network traffic distribution system according to any one of claims 2 to 6, characterized in that: The method comprises: The NR base station access network module receives the uplink data packet sent by the user equipment, and sends the received uplink data packet to the NR base station offload module for offloading; Extract key information from the received uplink data packet using the NR base station offload module to obtain key information of the uplink data packet; the key information includes one or more of a user equipment IP, a target IP, a protocol type, a source port, and a target port; The NR base station offloading module determines the service type corresponding to the uplink data packet based on the key information of the uplink data packet and a preset offloading rule library; When the service type is a local service, the NR base station offload module determines the user equipment IP corresponding to the uplink data packet, and based on the user equipment IP corresponding to the uplink data packet, sends the uplink data packet to the local network corresponding to the user equipment IP; When the service type is a public network service, the NR base station offload module adds a GTP-U header to the uplink data packet for encapsulation, and sends the encapsulated information to the core network module; The core network module sends the received encapsulated information to the public network.
9. The method according to claim 8, characterized in that The method further comprises: After receiving the downlink data packet, the NR base station offload module detects whether the received downlink data packet comes from the local service server; If it is detected that the received downlink data packet originates from the local service server, the NR base station offload module determines the user equipment identifier and the downlink tunnel endpoint identifier corresponding to the downlink data packet based on the user plane instance management table; The NR base station access network module places the downlink data packet into a downlink data processing queue of the user equipment determined by the user equipment identifier based on the user equipment identifier and the downlink tunnel endpoint identifier corresponding to the downlink data packet; If it is detected that the received downlink data packet comes from the core network module, the NR base station offload module transparently transmits the received downlink data packet to the user plane for parsing the GTP-U header to obtain the internal data after removing the GTP-U header; The NR base station access network module sends the internal data after removing the GTP-U header to the user equipment.
Citation Information
Patent Citations
Edge shunting system and method for service data in mobile network
CN112788644A
Method, module and system for realizing local service flow shunting
CN117336791A