Network shunting system and network shunting method

Abstract

The invention relates to a network shunting system and a network shunting method. The system comprises an NR base station access network module and an NR base station shunting module, the NR base station access network module is respectively connected with the user equipment and the NR base station shunting module and is used for receiving an uplink data packet sent by the user equipment and sending the received uplink data packet to the NR base station shunting module; the NR base station shunting module is used for analyzing the received uplink data packet and determining the service type of the data corresponding to the uplink data packet; when the service type is a local service, determining a user equipment IP corresponding to the received uplink data packet; and sending the received uplink data packet to a local network corresponding to the IP of the user equipment based on the IP of the user equipment. The problems that an existing network distribution method needs to track and update the context states of a large number of users in real time and recognize and remove GTP-U packet headers, a system is complex, and expenditure is large are solved.

Description

Technical Field

[0001] This application relates to the field of network communication technologies, and in particular, to a network traffic diversion system and a network traffic diversion method. Background Art

[0002] With the rapid development of the mobile Internet and the Internet of Things, various new types of services and applications have emerged continuously, such as high-definition video, cloud gaming, industrial Internet of Things, smart cities, etc. The increase in new services and applications has led to a sharp increase in the number of connections of terminal devices. Consequently, the demand for mobile network traffic has surged. To effectively cope with the traffic growth and improve the user experience, the NR (New Radio) network architecture (an architecture for transmitting and processing data in a wireless communication network based on 5G NR technology) has gradually been widely applied.

[0003] In the NR network architecture, all service data realizes data exchange between the gNB (5G base station) and the 5GC (5G core network) through the N3 interface, and performs packet data transfer between the 5GC and the DN (Data Network) network through the N6 interface. Under this architecture, service data needs to pass through the N3 and N6 interfaces to be transmitted to the DN, and the transmission line is long. Especially for some special scenarios, even if the server is deployed in the DN, it still needs to pass through the N3 and N6 interfaces to be transmitted to the DN, resulting in large transmission delays and potential data security risks. Therefore, implementing local service traffic diversion is an urgent problem to be solved in the NR network architecture.

[0004] The existing network traffic diversion methods mainly work as follows: after receiving an uplink data packet sent by an NR base station, if it is detected that the uplink data packet is uplink user plane data sent by a user terminal to a predetermined local area network device, the GTP-U (GPRS Tunnelling Protocol for User Plane) packet header of the uplink data packet is removed to obtain a local service uplink data packet, and the local service uplink data packet is forwarded to the predetermined local area network device. This network traffic diversion method requires real-time tracking and updating of the context states of a large number of users, and identification and removal of the GTP-U packet header, resulting in problems such as complex systems and high overheads.

[0005] Regarding the existing network traffic diversion methods, which require real-time tracking and updating of the context states of a large number of users, and identification and removal of the GTP-U packet header, resulting in problems such as complex systems and high overheads, no effective solution has been proposed yet. Summary of the Invention

[0006] Based on this, in view of the above technical problems, it is necessary to provide a network traffic diversion system and a network traffic diversion method.

[0007] In a first aspect, the present application provides a network traffic splitting system. The system includes: an NR base station access network module and an NR base station traffic splitting module;

[0008] The NR base station access network module is respectively connected to a user equipment and the NR base station traffic splitting module, 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 traffic splitting module;

[0009] The NR base station traffic splitting module is configured to analyze 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; and based on the user equipment IP, send the received uplink data packet to the local network corresponding to the user equipment IP.

[0010] In one embodiment, the system further includes a core network module;

[0011] The NR base station traffic splitting 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;

[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 traffic splitting module 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 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; the user plane instance management table is a corresponding relationship 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, transparently transmit the downlink data packet to the user plane for GTP-U header stripping processing 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;

[0014] The NR base station access network module is further configured to store the downlink data packet into the downlink data processing queue corresponding to the downlink tunnel endpoint identifier of the user equipment identifier based on the user equipment identifier and the downlink tunnel endpoint identifier corresponding to the received downlink data packet; 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 splitting module.

[0016] In one embodiment, the NR base station splitting module includes 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, analyze 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; 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;

[0019] The user plane is further configured to, when receiving a downlink data packet, detect whether the received downlink data packet comes from a local service server; if it is detected that the received downlink data packet comes 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 comes 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 embodiment, a local splitting service module is deployed in the user plane; the local splitting service module includes: a user plane instance management sub-module and a splitting rule engine sub-module;

[0021] The user plane instance management sub-module, which is connected to the control plane and the traffic splitting rule engine sub-module, 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 traffic splitting rule engine sub-module;

[0022] The traffic splitting rule engine sub-module, which is also connected to the core network module, is used to detect whether the received downlink data packet comes from the local service server when receiving the downlink data packet; if it is detected that the received downlink data packet comes from the local service server, based on the user plane instance management table, determine the user equipment identifier and the 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; if it is detected that the received downlink data packet comes from the core network module, send the downlink data packet to the tunnel management sub-module.

[0023] In one embodiment, the user plane instance management sub-module includes: an initial mapping table construction unit, a user equipment IP acquisition unit, and a construction unit;

[0024] The initial mapping table construction unit is used 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 the 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 used 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 containing a complete GTP-U header and the user equipment IP obtained according to the data sent by the user equipment after the session is established between the user equipment and the NR base station access network module;

[0026] The construction unit is used 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 embodiment, the user equipment IP acquisition unit includes: a stripping sub-unit, a parsing sub-unit, an address extraction sub-unit, and a user equipment IP acquisition sub-unit;

[0028] The stripping unit 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;

[0029] The parsing subunit is configured to parse the GTP-U header of the first uplink data packet to obtain the uplink tunnel endpoint identifiers corresponding to the respective user devices;

[0030] The address extraction subunit is configured to extract the user device IPs of the respective user devices from the internal data of the first uplink data packet;

[0031] The user device IP acquisition subunit is configured to determine, based on the initial mapping table, the user device identifier corresponding to the uplink tunnel endpoint identifier, and bind the user device identifier corresponding to the uplink tunnel endpoint identifier to the user device IPs of the respective user devices, so as to obtain the user device IPs corresponding to the respective uplink tunnel endpoint identifiers.

[0032] In one embodiment, the local traffic splitting service module further includes a tunnel management sub-module;

[0033] The tunnel management sub-module is connected to the traffic splitting 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 for encapsulation to the received uplink data packet, 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 parsing processing on 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.

[0035] In a second aspect, the present application further provides a network traffic splitting method. Applied to the network traffic splitting system described in the first aspect above, the method includes:

[0036] The NR base station access network module receives an uplink data packet sent by a user device, and sends the received uplink data packet to the NR base station traffic splitting module for traffic splitting;

[0037] The NR base station traffic splitting module is used to extract key information from the received uplink data packet to obtain the key information of the uplink data packet; the key information includes one or more of a user device IP, a target IP, a protocol type, a source port, and a target port;

[0038] The NR base station traffic splitting module determines the service type corresponding to the uplink data packet based on the key information of the uplink data packet and a preset traffic splitting rule library;

[0039] When the service type is a local service, the NR base station traffic splitting 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;

[0040] When the service type is a public network service, the NR base station traffic splitting module encapsulates the uplink data packet by adding a GTP-U header, and sends the encapsulated information to the core network module;

[0041] The core network module sends the received encapsulated information to the public network.

[0042] In one embodiment, the method further includes:

[0043] After receiving a downlink data packet, the NR base station traffic splitting module detects whether the received downlink data packet is from a local service server;

[0044] If it is detected that the received downlink data packet is from the local service server, the NR base station traffic splitting 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;

[0045] The NR base station access network module places the downlink data packet into the 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 traffic splitting module transparently transmits the received downlink data packet to the user plane for GTP-U header parsing 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 above network traffic splitting system and network traffic splitting method include: an NR base station access network module and an NR base station traffic splitting 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 traffic splitting module; the NR base station traffic splitting module is configured to analyze 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; and based on the user equipment IP, send the received uplink data packet to the local network corresponding to the user equipment IP. When the service type of the data corresponding to the received uplink data packet is a local service, by determining the user equipment IP corresponding to the received uplink data packet, the received uplink data packet is sent to the local network 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 states 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, reducing the process and making the system simple, solving the problems of the existing network traffic splitting method that it needs to track and update the context states of a large number of users in real time and identify and remove the GTP-U packet header, resulting in a complex system and high overhead.

[0049] Details of one or more embodiments of the present application are set forth in the following drawings and description to make other features, objects, and advantages of the present application more concise and understandable. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] The drawings described herein are used to provide a further understanding of the present application and form a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation to the present application. In the drawings:

[0051] Figure 1 is the first structural block diagram of the network traffic splitting system provided by an embodiment of the present application;

[0052] Figure 2 is the second structural block diagram of the network traffic splitting system provided by an embodiment of the present application;

[0053] Figure 3 is the third structural block diagram of the network traffic splitting system provided by an embodiment of the present application;

[0054] Figure 4 is the hardware structural block diagram of the terminal of the network traffic splitting method provided by an embodiment of the present application;

[0055] Figure 5 is the first flow chart of the network traffic splitting method provided by an embodiment of the present application;

[0056] Figure 6This is the second flowchart of the network traffic splitting method provided by an embodiment of the present application. Detailed implementation manners

[0057] To understand the purpose, technical solution and advantages of the present application more clearly, the present application will be described and explained below with reference to the accompanying drawings and embodiments.

[0058] Unless otherwise defined, the technical terms or scientific terms involved in the present application shall have the general meanings understood by those with ordinary skills in the technical field to which the present application belongs. In the present application, words such as "a", "one", "a kind of", "the", "these" and the like do not indicate a limitation in quantity, and they can be singular or plural. The terms "including", "comprising", "having" and any variants thereof involved in the present application are intended to cover non-exclusive inclusion; for example, a process, method, system, product or device including a series of steps or modules (units) is not limited to the listed steps or modules (units), but may include unlisted steps or modules (units), or may include other steps or modules (units) inherent in these processes, methods, products or devices. The terms "connected", "coupled" and the like involved in the present application do not limit to physical or mechanical connections, but may include electrical connections, whether direct or indirect. The "multiple" involved in the present application means two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" may represent: A exists alone, A and B exist simultaneously, and B exists alone. Usually, the character " / " indicates that the objects associated before and after are in an "or" relationship. The terms "first", "second", "third" and the like involved in the present application are only used to distinguish similar objects and do not represent a specific sorting of the objects.

[0059] See Figure 1 , Figure 1 This is the first structural block diagram of the network traffic splitting system provided by an embodiment of the present application. As Figure 1 shown, the network traffic splitting system includes: an NR base station access network module 11 and an NR base station traffic splitting module 12; the NR base station access network module 11 is respectively connected to a user equipment 10 and the NR base station traffic splitting module 12, and is configured to receive an uplink data packet sent by the user equipment 10 and send the received uplink data packet to the NR base station traffic splitting module 12; the NR base station traffic splitting module 12 is configured to analyze 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 (Internet Protocol) corresponding to the received uplink data packet; and based on the user equipment IP, send the received uplink data packet to the local network 13 corresponding to the user equipment IP.

[0060] The above-mentioned NR base station access network module 11 includes a PHY (Physical Layer) and a DU (Distributed Unit). Among them, the above-mentioned 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, and channel coding. The PHY function is usually executed by an FPGA (Field-Programmable Gate Array) or an ASIC (Application-Specific Integrated Circuit) chip inside the DU, which directly drives the radio unit. The specific application process of the PHY can be expressed 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. The MAC layer performs data recombination processing on the decoded data. In addition, the above-mentioned DU is a core component of a 5G base station (gNB), and is responsible for processing low-level protocol functions with high real-time requirements (such as scheduling PHY hardware resources and executing this physical layer function). Because the DU can be deployed close to the user equipment side, it can reduce the air interface transmission delay. Therefore, in the MEC (Multi-Access Edge Computing) scenario, the DU, as a local service offloading anchor point, can achieve direct transmission of low-latency data. The above-mentioned uplink refers to the data transmission direction from the user equipment 10 to the network side. The above-mentioned network side can include a public network and a local network. The above-mentioned downlink refers to the data transmission direction from the network side to the user equipment 10. The above-mentioned user equipment 10 can also be called a terminal. The above-mentioned user equipment 10 includes, but is not limited to, devices such as mobile phones, tablets, watches, in-vehicle T-Boxes, smart meters, and AGV (Automated Guided Vehicle Controller) controllers. The above-mentioned uplink data packet can be the data sent by the user equipment 10 to the NR base station access network module 11 during the uplink.

[0061] Based on this, the process by which the above-mentioned 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 traffic splitting module 12 can be as follows: The DU generates a scheduling instruction according to the channel state information, service requirements, 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 to recover the original data of the uplink data packet sent by the user equipment 10, and then sends the original data to the DU. After receiving the original data, the DU performs processing such as data recombination, error detection and correction on the original data, and sends the processed data to the NR base station traffic splitting module 12.

[0062] Furthermore, the above-mentioned service types can include local services and public network services. The above-mentioned local services refer to services provided within 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 above-mentioned local services can be services with a limited service scope, such as services within a specific area such as hospital services, school services, and factory services. The above-mentioned public network services can refer to services provided to the public. These services are provided through a public network (such as the Internet), and any user can access them. The public network can include Internet services such as social media platforms, online shopping platforms, and video streaming services, can include public services such as e-government platforms, online education platforms, and online medical platforms, and can include mobile applications such as mobile payment applications and navigation applications (navigation maps).

[0063] In this embodiment, the above-mentioned NR base station traffic splitting module 12 is used to parse the received uplink data packet and determine the service type of the data corresponding to the uplink data packet. The specific process may be that the traffic splitting rule engine sub-module in the NR base station traffic splitting module 12 first parses the received uplink data packet, then extracts the key information in the uplink data packet, and then based on the preset traffic splitting rules, matches the extracted key information, and determines the service type of the data corresponding to the uplink data packet based on the matching result. Among them, the above-mentioned key information may include at least two of the IP five-tuple, DNN (Data Network Name), and geographical location information. The above-mentioned IP five-tuple may include the user equipment IP address, destination IP address, source port number, destination port number, and transport protocol. The above-mentioned DNN can be used to identify the specific network service to which the user equipment 10 is connected. The above-mentioned geographical location information is the current location information of the user equipment 10, which may be obtained through the geographical location of the base station or the GPS (Global Positioning System) information reported by the user equipment 10. The above-mentioned preset traffic splitting rules may be a preset traffic splitting rule library, which may be a multi-dimensional matching strategy. The specific multi-dimensional matching strategy may be at least two dimensions of IP five-tuple matching, DNN matching, and geographical location matching. The above-mentioned IP five-tuple matching may be to check whether the IP five-tuple of the uplink data packet matches the preset local service or public network service rules. For example, if a specific IP address range or port number matches the preset local service, this uplink data packet is assigned to the local service. The above-mentioned DNN matching may be to check whether the DNN in the uplink data packet matches the preset local service or public network service rules. For example, some DNNs may be assigned to the enterprise internal network, while other DNNs are used for public network access. The above-mentioned geographical location matching may be to check whether the geographical location of the user equipment 10 is within the coverage range of the preset local service. For example, if the user equipment 10 is located within the enterprise park, the uplink data packet sent by it is identified as a local service.

[0064] In this embodiment, when the service type is a local service, the NR base station traffic splitting module 12 needs to determine the user equipment IP corresponding to the received uplink data packet, and based on the user equipment IP, send the received uplink data packet to the local network 13 corresponding to the user equipment IP. Among them, the process for the NR base station traffic splitting module 12 to determine the user equipment IP corresponding to the received uplink data packet can be that the NR base station traffic splitting module 12 constructs a user plane instance management table (a correspondence table of the user equipment identifier, downlink tunnel endpoint identifier, uplink tunnel endpoint identifier, and user equipment IP of each user equipment 10) in advance based on the received interface signaling. Furthermore, when obtaining the uplink data packet, based on the extracted uplink tunnel endpoint identifier of the 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, and the found user equipment IP is determined as the user equipment IP corresponding to the uplink data packet.

[0065] In the above network traffic splitting system, when the data service type corresponding to the received uplink data packet is a local service, by determining the user equipment IP corresponding to the received uplink data packet, the received uplink data packet is sent 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 status of a large number of users in real time, does not need a 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 making the system simple. It solves the problems of the existing network traffic splitting method, which needs to track and update the context status of a large number of users in real time, and identify and remove the GTP-U packet header, resulting in a complex system and high overhead. Moreover, this method avoids GTP-U header encapsulation and N3 interface transmission delay, reducing the end-to-end delay by about 30%.

[0066] In addition, in one embodiment, Figure 2 is the second structural block diagram of the network traffic splitting system provided by an embodiment of the present application. As Figure 2 shown, the system further includes a core network module 14; an NR base station traffic splitting module 12, connected to the core network module 14, and further configured to add a GTP-U header for encapsulation to the received uplink data packet when the service type is a public network service, 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 above core network module 14 includes at least an SMF (Session Management Function) and a UPF (User Plane Function). Among them, the above SMF is connected to the UPF through an N4 interface. The SMF is used to create, modify, or release a user session (PDU session) and uniformly control the data forwarding rules of the UPF. The UPF is used to receive the data of the uplink data packets forwarded by the NR base station shunting module 12. Furthermore, the UPF performs GTP-U header encapsulation processing on the received uplink data packet data and routes the processed data to the public network 15 through the N6 interface. The above GTP-U header at least contains key fields such as a tunnel endpoint identifier and a tunnel identifier. In this embodiment, by retaining the original IP data packet structure and only adding a GTP-U encapsulation layer, compatibility with the core network protocol stack is ensured.

[0068] Further, in one embodiment, the NR base station shunting module 12 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 a 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 11; 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 10; if it is detected that the downlink data packet originates from the core network module 14, transparently transmit the downlink data packet to the user plane for GTP-U header stripping processing 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 11; the NR base station access network module 11 is further configured to store the downlink data packet in the downlink data processing queue corresponding to the downlink tunnel endpoint identifier corresponding to the user equipment identifier based on the user equipment identifier and the downlink tunnel endpoint identifier corresponding to the received downlink data packet; the NR base station access network module 11 is further configured to send the internal data after removing 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 shunting module 12.

[0069] In this embodiment, the above local service server may be a computing or storage node accessing the local network 13, and bear local service applications (such as MEC platforms, databases, etc.). Since the NR base station traffic splitting module 12 and the UPF of the core network module 14 are connected through the N3 interface, the process for the NR base station traffic splitting module 12 to detect whether the received downlink data packet is from the local service server after receiving the downlink data packet may be as follows: After receiving the downlink data packet, the NR base station traffic splitting module 12 first determines whether the downlink data packet is transmitted to the NR base station traffic splitting 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. Among them, 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 may 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, using the user plane instance management table, the user equipment identifier and the downlink tunnel endpoint identifier corresponding to the user equipment IP are read from the user plane instance management table, and the read user equipment identifier and downlink tunnel endpoint identifier are determined as the user equipment identifier and the downlink tunnel endpoint identifier corresponding to the downlink data packet. The above downlink data packet may be data sent by the network side to the user equipment 10 during 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 example includes three user equipments: User Equipment 1, User Equipment 2, and User Equipment 3. The corresponding relationships between the user equipment identifiers, downlink tunnel endpoint identifiers, uplink tunnel endpoint identifiers, and user equipment IPs of each user equipment are shown in Table 1:

[0071] Table 1

[0072]

[0073] In this 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 according to the user equipment identifier and the downlink tunnel endpoint identifier corresponding to the received downlink data packet. A queue management unit may be set in the NR base station access network module 11. The queue management unit is used to store the downlink data packets to be sent to the user equipment 10 corresponding to each downlink tunnel endpoint identifier (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. After obtaining the user equipment identifier and the downlink tunnel endpoint identifier corresponding to the downlink data packet, the queue management unit is used to store the obtained downlink data packet into the downlink data processing queue corresponding to the downlink tunnel endpoint identifier of the user equipment identifier of the downlink data packet. The user plane directly sends the downlink data packet to the user equipment 10 through the N3 interface tunnel according to the downlink tunnel endpoint identifier, bypassing the core network processing, and the latency can be reduced to 2 - 5 ms. In addition, the local data does not add a tunnel header, reducing the protocol processing overhead by 30%, and through the direct connection channel between the base station and the local server, the N3 interface transmission delay is avoided. In the industrial Internet of Things scenario, the local service latency is reduced by more than 40%, and at the same time, the load pressure on the core network is reduced by 30%.

[0074] In some cases, after the uplink data packet is transmitted to the local network 13, it needs to be transmitted from the local network 13 to the public network 15. In this case, the local network 13 and the public network 15 are connected.

[0075] Figure 3 It is the third structural block diagram of the network traffic splitting system provided by an embodiment of the present application, as Figure 3As shown in the figure, the NR base station traffic splitting 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 used to send interface signaling to the user plane 122 through the E1 interface; the user plane 122 is used to parse the received uplink data packet when receiving an 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 13 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 send the encapsulated uplink data packet to the core network module 14; the user plane 122 is further used to detect whether the received downlink data packet comes from a local service server when receiving a downlink data packet; if it is detected that the received downlink data packet comes from a local service server, based on the above user plane instance management table, determine the user equipment identifier and the downlink tunnel endpoint identifier corresponding to the downlink data packet, and send the user equipment identifier corresponding to the downlink data packet and the above downlink tunnel endpoint identifier to the NR base station access network module 11; if it is detected that the received downlink data packet comes from the core network module 14, perform GTP-U header stripping processing on the downlink data packet to obtain the internal data after removing the GTP-U header, and send the above internal data after removing the GTP-U header to the NR base station access network module 11.

[0076] The above interface signaling is a key mechanism for communication between the control plane 124 and the user plane 122, and is used to coordinate and manage the processing and transmission of data packets. The above user plane 122 and control plane 124 are respectively connected to the NR base station access network module 11 and the core network module. The user plane 122 is communicatively connected to the AMF (Access and Mobility Management Function) of the core network module 14 through the N2 interface. The control plane 124 is communicatively connected to the UPF of the core network module 14 through the N3 interface and is connected to the local network 13 through the N6 interface.

[0077] The above network traffic splitting system still adopts the original NR standard interface processing flow. The normal access, authentication, service initiation, handover and other processes of the terminal are processed through the original N2 interface. Whether it is a local service or a public network service, the control of the end user is still the responsibility of the core network, thus ensuring that the local traffic splitting scheme in the NR base station based on MEC is transparent to the existing network and terminal.

[0078] In addition, in this embodiment, the rules and parameters required for the forwarding of the user plane 122 are dynamically created or updated through the E1 interface signaling (the bearer context management process in Section 8.3) defined by the 3GPP 38.463 protocol, so as to support the base station shunting module to implement intelligent routing of local services.

[0079] In one embodiment, a local shunting service module is deployed in the user plane 122; the local shunting service module includes: a user plane instance management sub-module and a shunting rule engine sub-module; the user plane instance management sub-module is connected to the control plane 124 and the shunting rule engine sub-module, 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 shunting rule engine sub-module; the shunting rule engine sub-module is connected to the NR base station access network module 11, and is used to analyze 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, based on the received user plane instance management table, determine the user equipment IP corresponding to the received uplink data packet; based on the user equipment IP corresponding to the received uplink data packet, send the received uplink data packet to the local network 13 corresponding to the user equipment IP. The shunting rule engine sub-module is also connected to the core network module, and is used to detect whether the received downlink data packet comes from a local service server when receiving a downlink data packet; if it is detected that the received downlink data packet comes from a local service server, then based on the user plane instance management table, determine the user equipment identifier and the 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; if it is detected that the received downlink data packet comes from the core network module, then send the downlink data packet to the tunnel management sub-module.

[0080] The above local shunting service module is used to directly shunt the uplink data packet to the local network 13 when the service type is a local service. Through the setting of the local shunting service module, when the service type is a local service, there is no need to go through the core network. At this time, local service shunting not only reduces the consumption of backhaul bandwidth, but also the close deployment of local services can reduce the service access delay and improve the user's service experience.

[0081] In another embodiment, the user plane instance management sub-module includes: 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 construct an initial mapping table of the user equipment 10 based on the user equipment identifier, the downlink tunnel endpoint identifier, and the uplink tunnel endpoint identifier corresponding to each user equipment 10 obtained; 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 containing a complete GTP-U header and the user equipment IP obtained according to the data sent by the user equipment 10 after the session between the user equipment 10 and the NR base station access network module 11 is established; 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 above initial mapping table of the user equipment 10 may 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 the initial mapping table of a user equipment. As shown in Table 2, it includes three user equipments: User Equipment 1, User Equipment 2, and User Equipment 3. 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, and the user equipment IP is unknown in Table 2.

[0083] Table 2

[0084]

[0085] In this embodiment, the above user equipment IP acquisition unit obtains the user equipment IP corresponding to each uplink tunnel endpoint identifier based on the initial mapping table and the first uplink data packet received. It can be by stripping the GTP-U header of the first uplink data packet received and parsing the GTP-U header of the first 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, that is, obtaining the user equipment IP corresponding to each uplink tunnel endpoint identifier. The above first uplink data packet can be the data packet after adding the GTP-U header to the first public network service data packet 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 the complete GTP-U header and the user equipment IP. When the uplink data packet is a data packet corresponding to a public network service, it is necessary to add a GTP-U header to the data packet for processing. At this time, the data packet is the service data containing the complete GTP-U header and the user equipment. Therefore, the first public network service data packet after the session establishment between the user equipment 10 and the NR base station access network module 11 can be used to construct the user plane instance management table.

[0086] Further, in another embodiment, 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 used to strip the GTP-U header of the first uplink data packet to obtain the GTP-U header and the internal data of the first uplink data packet; the parsing subunit is used to parse the GTP-U header of the first uplink data packet to obtain the uplink tunnel endpoint identifier corresponding to each user equipment 10; the address extraction subunit is used to extract the user equipment IP of each user equipment 10 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 to the user equipment IP of each user equipment 10 to obtain the user equipment IP corresponding to each uplink tunnel endpoint identifier.

[0087] Wherein, in another embodiment, the local traffic steering service module further includes a tunnel management sub-module; the tunnel management sub-module is connected to the traffic steering rule engine sub-module and the core network module 14, and is used to encapsulate the received uplink data packet by adding a GTP-U header 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 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.

[0088] The method embodiments provided in this embodiment can be executed on a terminal, a computer, or a similar computing device. For example, when running on a terminal, Figure 4 is a hardware block diagram of the terminal of the network traffic splitting method in this embodiment. As Figure 4 shown, the terminal may include one or more ( Figure 4 only one is shown in the figure) processors 402 and a memory 404 for storing data. Among them, the processor 402 may include, but is not limited to, a processing device such as a microprocessor MCU or a field programmable gate array FPGA. The above terminal may further include a transmission device 406 for communication functions and an input / output device 408. Those of ordinary skill in the art can understand that Figure 4 the structure shown is only schematic and does not limit the structure of the above terminal. For example, the terminal may further include more or fewer components than Figure 4 shown in the figure, or have a different configuration from Figure 4 shown in the figure.

[0089] The memory 404 can be used to store computer programs. For example, software programs and modules of application software, such as the computer program corresponding to the network traffic splitting method in this embodiment. The processor 402 executes various functional applications and data processing by running the computer program stored in the memory 404, that is, implements the above method. The memory 404 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memories, or other non-volatile solid-state memories. In some instances, the memory 404 may further include a memory remotely provided with respect to the processor 402, and these remote memories may be connected to the terminal through a network. Examples of the above networks include, but are not limited to, a 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 above network includes a wireless network provided by the communication provider of the terminal. In one instance, the transmission device 406 includes a network adapter (abbreviated as NIC), which can be connected to other network devices through a base station and thus can communicate with the public network 15. In one instance, the transmission device 406 may be a radio frequency (abbreviated as RF) module, which can communicate with the public network 15 wirelessly.

[0091] In this embodiment, a network traffic splitting method is provided. Figure 5 is the first flowchart of the network traffic splitting method in this embodiment. As Figure 5 shown, the process includes the following steps:

[0092] Step S1, the access network module 11 of the NR base station receives the uplink data packet sent by the user equipment 10, and sends the received uplink data packet to the NR base station traffic splitting module 12 for traffic splitting;

[0093] Step S2, the NR base station traffic splitting module 12 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 the user equipment IP, target IP, protocol type, source port, and target port;

[0094] Step S3, the NR base station traffic splitting 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 traffic splitting rule library;

[0095] The above preset traffic splitting 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 traffic splitting module 12 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 13 corresponding to the user equipment IP;

[0097] Step S5, when the service type is a public network service, the NR base station traffic splitting module 12 adds a GTP-U header to the uplink data packet for encapsulation, and sends the encapsulated information to the core network module 14;

[0098] The above NR base station traffic splitting module 12 adds a GTP-U header to the internal information of the uplink data packet for encapsulation, which can be to add a GTP-U header to the received uplink data packet by using the tunnel management sub-module of the local traffic splitting service module deployed in the user plane 122 of the NR base station traffic splitting module 12.

[0099] Step S6, the core network module 14 sends the received encapsulated information to the public network 15.

[0100] The above steps S1 to S6 introduce the uplink data processing process. The NR base station splitting module 12 extracts key information from the uplink data packet. Based on the extracted key information and the preset splitting rule library, the service type of the uplink data packet is determined. If the service type is a local service, the NR base station splitting 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 splitting 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 splitting at the base station level, it can quickly distinguish between local services and public network services. For local services, the data is directly routed to the local network 13 at the base station level, avoiding detouring through the core network. The number of transmission hops is reduced, and the end-to-end delay is reduced from the millisecond level to the sub-millisecond level, which is especially suitable for latency-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 on the core network are reduced, and the core network bandwidth resources can be saved. By removing the GTP-U header and only re-encapsulating in the case of public network services, the redundant protocol overhead is reduced, and the bandwidth requirement of the backhaul network is lowered. In addition, local services do not need to pass through expensive core network links, reducing the operator's transmission costs.

[0101] Among them, in one embodiment, Figure 6 is the second flowchart of the network splitting method of this embodiment, as Figure 6 shown. This process includes the following steps:

[0102] Step S7, after receiving the downlink data packet, the NR base station splitting module 12 detects whether the received downlink data packet comes from a local service server;

[0103] Step S8, if it is detected that the received downlink data packet comes from a local service server, the NR base station splitting 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 places 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 comes from the core network module 14, the NR base station splitting module 12 transparently transmits the received downlink data packet to the user plane 122 for parsing the GTP-U header processing to obtain the internal data after removing the GTP-U header;

[0106] Step S11: The access network module 11 of the NR base station 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 traffic splitting module 12, it first detects its source. Based on different sources, if it is detected that the received downlink data packet comes from the local service server, the NR base station traffic splitting module 12 places 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 comes from the core network module 14, the NR base station traffic splitting module 12 transparently transmits the received downlink data packet to the user plane 122 for GTP-U header parsing processing, and sends the internal data after removing the GTP-U header to the user equipment 10. For local services, the GTP-U encapsulation or decapsulation and core network forwarding links are reduced, and there is no need to go through expensive core network links, reducing the operator's transmission cost.

[0108] It should be understood that although the steps in the flowcharts involved in the above-described embodiments are shown in sequence according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless there is a clear description in this article, the execution of these steps has no strict order limit, and these steps can be executed in other orders. Moreover, at least some of the steps in the flowcharts involved in the above-described embodiments may include multiple steps or multiple stages. These steps or stages are not necessarily executed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be executed alternately or alternately with at least a part of other steps or steps or stages in other steps.

[0109] It should be noted that the above-mentioned various modules can be functional modules or program modules, and can be implemented either by software or by hardware. For the modules implemented by hardware, the above-mentioned various modules can be located in the same processor; or the above-mentioned various modules can also be located in different processors in any combination form.

[0110] Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be completed by instructing relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above methods. Among them, any reference to a memory, database, or other medium used in the embodiments provided in the present application can include at least one of non-volatile and volatile memories. Non-volatile memories can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memories can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM), etc. The databases involved in the embodiments provided in the present application can include at least one of relational databases and non-relational databases. Non-relational databases can include distributed databases based on blockchain, etc., without limitation. The processors involved in the embodiments provided in the present application can be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, data processing logics based on quantum computing, etc., without limitation.

[0111] The technical features of the above embodiments can be combined arbitrarily. For the sake of concise description, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, it should be considered as the scope recorded in this specification.

[0112] The above-described embodiments only represent several implementation manners of the present application. The description is relatively specific and detailed, but it should not be construed as a limitation on the patent scope of the present application. It should be noted that for those of ordinary skill in the art, without departing from the concept of the present application, several modifications and improvements can be made, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the appended claims.

Claims

1. A network shunt system, characterized in that, The system includes: an NR base station access network module and an NR base station traffic splitting module; The NR base station access network module is respectively connected to a user equipment and the NR base station traffic splitting module, 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 traffic splitting module; The NR base station traffic splitting module is configured to analyze 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 user equipment IP, send the received uplink data packet to the local network corresponding to the user equipment IP.

2. The network shunting system according to claim 1, wherein The system further includes a core network module; The NR base station traffic splitting 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 configured to send the received encapsulated uplink data packet to a public network.

3. The network traffic splitting system according to claim 2, wherein: The NR base station traffic splitting module 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 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; The user plane instance management table is a corresponding relationship 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, transparently transmit the downlink data packet to the user plane for GTP-U header stripping processing 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; The NR base station access network module is further configured to store the downlink data packet in the downlink data processing queue corresponding to the downlink tunnel endpoint identifier corresponding to the user equipment identifier based on the user equipment identifier and the downlink tunnel endpoint identifier corresponding to the received downlink data packet; 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 further configured to send the received downlink data packet to the NR base station traffic splitting module.

4. The network shunting system according to any one of claims 1 to 3, characterized in that The NR base station traffic splitting 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 configured 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 send the encapsulated uplink data packet to the core network module; The user plane is further used to, when receiving a downlink data packet, detect whether the received downlink data packet comes from a local service server; if it is detected that the received downlink data packet comes from the local service server, based on the user plane instance management table, determine the user equipment identifier and the 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; If it is detected that the received downlink data packet comes from the core network module, perform GTP-U header stripping processing on the 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.

5. The network shunting system according to claim 4, wherein A local offloading service module is deployed in the user plane; The local offloading service module includes: a user plane instance management sub-module and a offloading rule engine sub-module; The user plane instance management sub-module, which is connected to the control plane and the offloading rule engine sub-module, 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 offloading rule engine sub-module; The offloading rule engine sub-module, which is connected to the NR base station access network module, 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, based on the received user plane instance management table, determine the user equipment IP corresponding to the received uplink data packet; 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 shunt rule engine sub-module is also connected to the core network module, and is used to detect whether the received downlink data packet comes from the local service server when receiving the downlink data packet; if it is detected that the received downlink data packet comes from the local service server, based on the user plane instance management table, determine the user equipment identifier and the 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; if it is detected that the received downlink data packet comes from the core network module, send the downlink data packet to the tunnel management sub-module.

6. The network shunting system according to claim 5, wherein The user plane instance management sub-module includes: an initial mapping table construction unit, a user equipment IP acquisition unit, and a construction unit; The initial mapping table construction unit is used 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 user equipment identifier, the downlink tunnel endpoint identifier, and the uplink tunnel endpoint identifier corresponding to each obtained user equipment; The user equipment IP acquisition unit is used 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 containing a complete GTP-U header and the user equipment IP obtained according to the data sent by the user equipment after the user equipment establishes a session with the NR base station access network module; The construction unit is used 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.

7. The network shunting system according to claim 6, wherein The user equipment IP acquisition unit includes: a stripping sub-unit, a parsing sub-unit, an address extraction sub-unit, and a user equipment IP acquisition sub-unit; The stripping sub-unit is used to strip the GTP-U header of the first uplink data packet to obtain the GTP-U header and the internal data of the first uplink data packet; The parsing sub-unit is used to parse the GTP-U header of the first uplink data packet to obtain the uplink tunnel endpoint identifier corresponding to each user equipment; The address extraction sub-unit is used to extract the user equipment IP of each user equipment from the internal data of the first uplink data packet; The user equipment IP acquisition sub-unit 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.

8. The network shunting system according to claim 5, wherein The local shunt service module further includes a tunnel management sub-module; The tunnel management sub-module, which is connected to the traffic splitting rule engine sub-module and the core network module, is used to add a GTP-U header for encapsulation to the received uplink data packet when the service type is a public network service, and send the encapsulated uplink data packet to the core network module; The tunnel management sub-module is also connected to the NR base station access network module, and is further 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.

9. A network shunting method, applied to the network shunting system described in any one of claims 2 to 7, characterized in that, The method includes: 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 traffic splitting module for traffic splitting; Use the NR base station traffic splitting module to extract 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 the user equipment IP, target IP, protocol type, source port, and target port; The NR base station traffic splitting module determines the service type corresponding to the uplink data packet based on the key information of the uplink data packet and a preset traffic splitting rule library; When the service type is a local service, the NR base station traffic splitting 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 traffic splitting module adds a GTP-U header for encapsulation to the uplink data packet, and sends the encapsulated information to the core network module; The core network module sends the received encapsulated information to the public network.

10. The method according to claim 9, wherein The method further includes: After receiving the downlink data packet, the NR base station traffic splitting module detects whether the received downlink data packet comes from the local service server; If it is detected that the received downlink data packet comes from the local service server, the NR base station traffic splitting 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 in the downlink data processing queue of the user equipment determined by the user equipment identifier corresponding to the downlink data packet based on the user equipment identifier and the downlink tunnel endpoint identifier; If it is detected that the received downlink data packet comes from the core network module, the NR base station traffic splitting 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.

Images