Message distribution method and device, equipment, storage medium and program product

Abstract

The invention provides a message distribution method and device, equipment, a storage medium and a program product, and relates to the field of 5G networks. The method comprises the following steps: in response to a service message sent by user equipment, obtaining an internet protocol destination address in the service message, obtaining a pre-configured shared network protocol destination address, judging whether the service message needs to be subjected to shunting detection according to the pre-configured shared network protocol destination address and the internet protocol destination address, and if yes, sending the service message to the user equipment. And if it is determined that the service message is subjected to shunting detection, obtaining application layer content of the service message, and determining a shunting strategy of the service message according to the application layer content of the service message. Whether the service message is detected and shunted is judged through the pre-configured shared network protocol destination address and the internet protocol destination address in the service message, so that the message shunting accuracy is improved, and the message shunting efficiency is improved.

Description

Technical Field

[0001] This application relates to the field of 5G network traffic splitting, and particularly to a method, apparatus, device, storage medium, and program product for packet traffic splitting. Background Art

[0002] CDN (Content Delivery Network) accelerates the transmission of content and reduces the load on the origin server by storing content on edge nodes close to users. To save limited IP (Internet Protocol) resources, multiple public network services in CDN share the same IP.

[0003] UPF (User Plane Function) can only identify traffic through the IP address and perform traffic splitting based on the IP address, and cannot distinguish different service types under the same IP. It is impossible to achieve precise allocation of service-level traffic, resulting in a mismatch between the network path and service requirements.

[0004] In the prior art, there is mainly the technical problem of low packet traffic splitting efficiency. Summary of the Invention

[0005] This application provides a method, apparatus, device, storage medium, and program product for packet traffic splitting to solve the problem of low packet traffic splitting efficiency in the prior art.

[0006] In a first aspect, this application provides a method for packet traffic splitting, including:

[0007] In response to a service packet sent by a user device, obtain the Internet Protocol destination address in the service packet;

[0008] Obtain the pre-configured shared network protocol destination address;

[0009] According to the pre-configured shared network protocol destination address and the Internet Protocol destination address, determine whether the service packet needs to perform traffic splitting detection;

[0010] If it is determined that the service packet performs traffic splitting detection, obtain the application layer content of the service packet;

[0011] Determine the traffic splitting strategy of the service packet according to the application layer content of the service packet.

[0012] In a possible design, determining the traffic splitting strategy of the service packet according to the application layer content of the service packet includes:

[0013] Detect whether the application layer content contains the domain name information of the Journal Net corresponding to the network protocol destination address;

[0014] If the application layer content contains the domain name information of the Journal Net corresponding to the destination address of the network protocol, the service packet is split to the private network user plane function;

[0015] If the application layer content does not contain the domain name information of the Journal Net corresponding to the destination address of the network protocol, the service packet is split to the public network to access the Journal Net service through the public network.

[0016] In a possible design, after splitting the service packet to the public network to access the Journal Net service through the public network, it further includes:

[0017] If the service packet is split to the public network, it is detected whether the request packet of the service packet successfully establishes a connection with the response packet;

[0018] If it is detected that the request packet of the service packet does not successfully establish a connection with the response packet, it is determined that the application layer information of the service packet is encrypted and the service packet is wrongly split;

[0019] In response to the service packet retransmitted by the user equipment, the service packet is split to the private network user plane function.

[0020] In a possible design, according to the pre-configured shared network protocol destination address and the Internet protocol destination address, it is determined whether the service packet needs to perform split detection, including:

[0021] If the pre-configured shared network protocol destination address includes the Internet protocol destination address, it is determined that the service packet needs to perform split detection.

[0022] In a possible design, before obtaining the pre-configured shared network protocol destination address, it further includes:

[0023] In response to the request packet sent by the user equipment, the request packet is split to the user plane function;

[0024] Receive the response packet returned by the intranet domain name system server; the response packet is generated by the intranet domain name system after receiving the request packet forwarded by the user plane function; the response packet includes a shared address identification bit;

[0025] Extract the Internet protocol destination address and the corresponding shared identification bit in the response packet;

[0026] According to the Internet protocol destination address and the corresponding shared identification bit in the response packet, determine the pre-configured shared network protocol destination address.

[0027] In a possible design, the shared address identification bit is determined by the intranet domain name system according to the Internet protocol destination address in the request packet and the reverse resolution record corresponding to the Internet protocol destination address in the request packet;

[0028] The shared address identification bit is set in the reserved field of the response message.

[0029] In a possible design, after determining the target transmission data according to the request information, it further includes:

[0030] Perform data disk writing processing on the target transmission data according to the transmission rules.

[0031] In a second aspect, the present application provides a message splitting device, including:

[0032] A first acquisition module, configured to acquire the Internet Protocol destination address in the service message in response to the service message sent by the user device;

[0033] A second acquisition module, configured to acquire the pre-configured shared network protocol destination address;

[0034] A judgment module, configured to judge whether the service message needs to be subjected to splitting detection according to the pre-configured shared network protocol destination address and the Internet Protocol destination address;

[0035] A third acquisition module, configured to acquire the application layer content of the service message if it is determined that the service message is to be subjected to splitting detection;

[0036] A determination module, configured to determine the splitting strategy of the service message according to the application layer content of the service message.

[0037] In a third aspect, the present application provides a message splitting device, including:

[0038] A memory, a processor;

[0039] The memory stores computer execution instructions;

[0040] The processor executes the computer execution instructions stored in the memory, so that the processor executes the method according to any item of the first aspect.

[0041] In a fourth aspect, the present application provides a computer-readable storage medium, in which computer execution instructions are stored, and when the computer execution instructions are executed by a processor, they are used to implement the method according to any item of the first aspect.

[0042] In a fifth aspect, the present application provides a computer program product, including a computer program, and when the computer program is executed by a processor, it implements the method according to any item of the first aspect.

[0043] A method, apparatus, device, storage medium, and program product for packet splitting provided by this application. In response to a service packet sent by a user device, obtain the Internet Protocol destination address in the service packet, obtain a preconfigured shared network protocol destination address, and determine whether the service packet needs to be split and detected based on the preconfigured shared network protocol destination address and the Internet Protocol destination address. If it is determined that the service packet is to be split and detected, obtain the application layer content of the service packet, and determine the packet splitting strategy of the service packet based on the application layer content of the service packet. By using the preconfigured shared network protocol destination address and the Internet Protocol destination address in the service packet to determine whether the service packet is detected and split, the accuracy of packet splitting is increased, and thus the efficiency of packet splitting is improved. Description of the Drawings

[0044] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, the following drawings are some embodiments of the present invention. For those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings.

[0045] Figure 1 Schematic diagram of a packet splitting system architecture provided by an embodiment of this application;

[0046] Figure 2 Flow diagram of a packet splitting method provided by an embodiment of this application Figure 1 ;

[0047] Figure 3 Flow diagram of a packet splitting method provided by an embodiment of this application Figure 2 ;

[0048] Figure 4 Flow diagram of a packet splitting method provided by an embodiment of this application Figure 3 ;

[0049] Figure 5 Schematic diagram of the structure of a packet splitting apparatus provided by an embodiment of this application;

[0050] Figure 6 Schematic diagram of the structure of a packet splitting device provided by an embodiment of this application. Detailed Embodiments

[0051] Exemplary embodiments will be described in detail herein, and examples thereof are shown in the accompanying drawings. When the following description refers to the accompanying drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. On the contrary, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims, rather than all embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the scope of protection of the present invention.

[0052] In the embodiments of the present application, words such as "first" and "second" are used to distinguish the same or similar items with basically the same functions and roles. Those skilled in the art can understand that words such as "first" and "second" do not limit the quantity and execution order, and "first", "second", etc. do not necessarily mean different.

[0053] It should be noted that in the embodiments of the present application, words such as "exemplary" or "for example" are used to represent examples, illustrations or explanations. Any embodiment or design solution described as "exemplary" or "for example" in the present application should not be construed as being more preferred or having more advantages than other embodiments or design solutions. Rather, the use of words such as "exemplary" or "for example" is intended to present relevant concepts in a specific manner. In the embodiments of the present application, "at least one" means one or more, and "a plurality" means two or more.

[0054] It should be noted that in the embodiments of the present application, "when..." can be at the instant when a certain situation occurs, or within a period of time after a certain situation occurs. The embodiments of the present application do not make specific limitations in this regard. In addition, a message splitting method provided in the embodiments of the present application is only an example, and the message splitting method may further include more or less content.

[0055] To facilitate a clear description of the technical solutions of the embodiments of the present application, the following briefly introduces some terms and technologies involved in the embodiments of the present application:

[0056] Content Delivery Network (CDN): CDN is a distributed network system that caches content (such as web pages, videos, files, etc.) on edge node servers globally distributed, enabling users to obtain the required data nearby, thereby significantly improving access speed, enhancing service stability, and reducing the load pressure on the origin server.

[0057] User Plane Function (UPF): It is a key component in the 5G network architecture, mainly responsible for processing the transmission of user data traffic. As an anchor point between the radio access network and the Internet, it realizes the routing and forwarding of data packets, and dynamically adjusts the data transmission path according to service requirements, thereby enhancing network flexibility, supporting diverse service needs, and optimizing data transmission efficiency.

[0058] Large network UPF: Usually deployed in the public network, it provides general data services for users in a wide area. It supports multi-tenant and high-concurrency scenarios, and realizes flexible routing and resource allocation through centralized deployment to meet the basic communication needs of the mass market.

[0059] Private network UPF: Customized and deployed for specific industries or scenarios (such as industrial Internet, smart healthcare), it provides differentiated services such as edge computing, ultra-low latency, and data localization. This type of UPF is often combined with a dedicated core network to ensure service security through local traffic splitting, meeting the strict requirements of vertical fields for performance, compliance, and isolation.

[0060] Source Network Address Translation (SNAT): It is a network address translation technology mainly used to modify the source IP address of data packets. Its working principle is that when a device in the internal network needs to communicate with the external network, SNAT will replace the source IP address of the data packet with a specified public IP address, enabling multiple internal devices to access the external network through a single public IP address, and all traffic seen by the external network comes from this public IP address.

[0061] DNS Reverse Lookup (rDNS): It is the process of converting an IP address into a domain name, which is the opposite of forward lookup (finding an IP address through a domain name). It is an important function of the Domain Name System (DNS), mainly used to verify the correspondence between an IP address and a domain name, and has wide applications in network management and security fields.

[0062] Server Name Indication (SNI): It is a network protocol extension. During the SSL / TLS handshake phase, the client sends the domain name of the requested server to the server through SNI, enabling the server to accurately select the corresponding SSL certificate for encrypted communication. This mechanism solves the problem of SSL certificate selection when multiple domain names are hosted on one IP address, enhancing network security and communication efficiency.

[0063] HTTP (Hypertext Transfer Protocol): An application layer protocol used for transferring hypermedia documents (such as HTML). As the foundation of the World Wide Web (WWW), HTTP enables data transfer and interaction through a request-response mechanism between a client (such as a browser) and a server, supporting users to browse and access web resources on the Internet.

[0064] HTTPS (Hypertext Transfer Protocol Secure): A security protocol based on HTTP. By encrypting the data transmitted through the SSL / TLS protocol, HTTPS ensures the secure transfer of data between a client (such as a browser) and a server, preventing data from being tampered with or forged. As the basis for secure communication on the World Wide Web, HTTPS is widely used in scenarios such as e-commerce and online banking that require protecting user privacy and data security.

[0065] For example, the Journal Network is a professional academic resource platform designed to provide users with retrieval, access, and download services for a wealth of academic journals, research papers, and various academic resources. It usually aggregates the latest research results in various academic fields and is widely used in multiple scenarios such as academic research, teaching, and research projects. Teachers and students in colleges and universities often obtain the required research literature and academic resources through the Journal Network to support their teaching, research, and academic exchange needs. With the continuous development of academic research and the increasing demand for knowledge sharing, the access volume of the Journal Network has been rising year by year, becoming an indispensable important tool in the daily scientific research activities of colleges and universities.

[0066] Among them, the Journal Network will be deployed in the external network environment and has an independent public IP address. This deployment method not only ensures the access security and efficiency of the Journal Network but also enables teachers and students in colleges and universities to remotely access various academic resources through the Internet, providing a convenient access experience whether on campus or off campus. At the same time, the setting of the public IP address helps to ensure the high availability and traffic management of the Journal Network, ensuring that users can still use the platform smoothly under high access volumes.

[0067] Among them, the users of the Journal Network are often campus network users. The campus network is a special type of campus network, a local area network built specifically for colleges and universities, research institutes, or educational institutions, aiming to provide information technology support in multiple aspects such as teaching, research, management, and life services for internal users.

[0068] Among them, the user addresses of the campus network are usually private network addresses, mainly communicating with the external network through network address translation technology. Such an address plan not only saves public IP address resources but also enhances the security of the campus network to a certain extent, avoiding direct exposure to the public network environment.

[0069] Specifically, when a campus network user accesses the journal network through the campus network, because the user's own IP address is a private network address, the traffic needs to be converted by SNAT at the intranet egress device. After SNAT conversion, the user's own IP address will become a public network address (IP#1). At the same time, the journal network will set permissions. If the source address of the message is IP#1, the journal network will authorize access, otherwise, it will not be authorized.

[0070] After the campus network user signs up for the first time, UPF will generate a diversion rule for the domain name, and divert the DNS message corresponding to the domain name to the intranet UPF. Because the journal network domain name has been deployed and configured in advance, the large network UPF can identify and divert messages containing the journal network domain name.

[0071] For example, when a campus user requests to resolve the journal network domain name, the DNS query message first reaches the large network UPF, is diverted to the private network UPF, and finally reaches the campus network's intranet DNS. According to the configuration, the intranet DNS directly resolves the journal network domain name and returns the A record of 1.1.1.1.

[0072] Among them, the large network UPF will learn the A record in the DNS message, that is, the address 1.1.1.1. Then, it will add this address to its own diversion rules. Later, when it encounters a message with the destination address as this address, it will divert it to the intranet through the private network UPF.

[0073] Among them, IP address resources are limited. In order to save IP resources, CDN service providers usually let multiple services share the same IP address, and CDN nodes will distinguish services through domain names and other information. For example, a journal website is deployed on a CDN node, but different public network services are often deployed on the same CDN node, so multiple different public network services may reuse the same IP address.

[0074] Specifically, when multiple services share the same public network IP (such as 1.1.1.1), the large network UPF can only identify traffic by IP address. This IP-based packet diversion method cannot distinguish different service types under the same IP (such as journal network and public network service 1). All traffic sent to this IP is forced to be directed to the campus network, causing non-target service traffic to enter the intranet by mistake.

[0075] For example, when the journal website and public network service 1 use the same public IP address 1.1.1.1, due to the above-mentioned DNS learning process, the large network UPF has added this address to its own diversion rules. Then, once there is traffic with this IP address, it will first forward it to the campus network and then reach the CDN node.

[0076] Among them, if a user accesses public network service 1, this traffic will first enter the campus network, and then return to the public network server and CDN node, forming an invalid path, resulting in increased pressure on the dedicated line bandwidth between the campus network and the external network CDN, resulting in a waste of dedicated line bandwidth.

[0077] Among them, the detour of public network service 1 in the campus network increases the number of network hops, resulting in increased end-to-end delay. At the same time, if there is a problem with the subsequent intranet routing, it will also affect the normal forwarding of the user's public network service. All of these have caused redundant delays in routing.

[0078] Among them, the school behavior statistics system of the campus network will analyze the segmented services, and public network service 1 may also be mistakenly identified as intranet traffic by the intranet security system and intercepted, resulting in the failure of public network service 1 and reducing the availability of the service.

[0079] Based on this, in order to solve the technical problem that the existing message diversion method has low accuracy in message diversion, which in turn leads to low message diversion efficiency, the embodiments of the present application provide a message diversion method, device, equipment, storage medium and program product, which can be used in the field of message diversion.

[0080] The inventive concept of this application is that: because multiple public network services in CDN share the same IP architecture and the UPF splits traffic based on IP, the network path and service demand cannot be accurately matched. Based on this technical problem, the inventor uses public network IP sharing information, and the large network UPF performs segmented detection and splitting based on this, so that the traffic accessing the journal network is transmitted through the intranet, while the process of accessing other public network services with the same IP address is transmitted through the public network, thereby improving the efficiency of message splitting.

[0081] Optional, Figure 1 A schematic diagram of a message diversion system architecture provided in an embodiment of the present application, wherein the application data processing system is a computer device. Figure 1 In the above architecture, the above architecture includes at least one of a data acquisition device 11, a processing device 12 and a display device 13.

[0082] It is understandable that the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the application data processing system architecture. In other feasible implementations of the present application, the above architecture may include more or fewer components than shown in the figure, or combine certain components, or split certain components, or arrange the components differently, which can be determined according to the actual application scenario and is not limited here. Figure 1 The components shown may be implemented in hardware, software, or a combination of software and hardware.

[0083] In the specific implementation process, the data acquisition device 11 may include an input / output interface or a communication interface, and the data acquisition device 11 may be connected to the processing device through the input / output interface or the communication interface.

[0084] During the packet splitting process, the processing device 12 is used to respond to the service packet sent by the user device, obtain the Internet Protocol destination address in the service packet, and at the same time obtain the pre-configured shared network protocol destination address; and based on the pre-configured shared network protocol destination address and the Internet Protocol destination address, determine whether the service packet needs to be split and detected, then perform split and detection on the determined service packet to obtain the application layer content of the service packet; finally, determine the split strategy of the service packet according to the application layer content of the service packet.

[0085] The display device 13 may also be a touch display screen or the screen of the terminal device for receiving user instructions while displaying the above content to achieve interaction with the user.

[0086] It should be understood that the above processing device may be implemented by a processor reading and executing instructions in a memory or by a chip circuit.

[0087] In addition, the network architecture and service scenarios described in the embodiments of the present application are for more clearly explaining the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. Those of ordinary skill in the art know that with the evolution of the network architecture and the emergence of new service scenarios, the technical solutions provided by the embodiments of the present application are equally applicable to similar technical problems.

[0088] The following uses specific embodiments to detail the technical solutions of the present application and how the technical solutions of the present application solve the above technical problems. These specific embodiments below can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below with reference to the accompanying drawings.

[0089] Figure 2 Flow schematic of a packet splitting method provided for an embodiment of the present application Figure 1 As Figure 2 shown, the method includes:

[0090] S201. In response to the service packet sent by the user device, obtain the Internet Protocol destination address in the service packet.

[0091] In this embodiment, the large network UPF receives the service packet sent by the user device and obtains the Internet Protocol destination address in the service packet.

[0092] S202. Obtain the pre-configured shared network protocol destination address.

[0093] S203. Determine whether the service packet needs to be shunted and detected according to the pre-configured shared network protocol destination address and the Internet protocol destination address.

[0094] Among them, if the pre-configured shared network protocol destination address includes the Internet protocol destination address, it is determined that the service packet needs to be shunted and detected.

[0095] For example, when the DNS response packet returns to the public network UPF, the public network UPF extracts the public network IP address of the journal network and marks this IP address. After that, when a service packet with this IP address as the destination address is encountered, a new detection mechanism will be triggered.

[0096] For example, for an unmarked IP address, the public network UPF will shunt the service packet in the normal way. That is, add this IP address to the shunting rule, and the traffic outlet corresponding to this rule is the private network UPF.

[0097] S204. If it is determined that the service packet is to be shunted and detected, obtain the application layer content of the service packet.

[0098] Specifically, the public network UPF receives the DNS request packet sent by the user equipment. The header of the DNS request packet contains the journal network domain name information. The public network UPF shunts the DNS request packet to the private network UPF according to the domain name in the DNS request packet.

[0099] More specifically, if this domain name has been sent to the private network UPF by the relevant core network equipment before and a shunting rule is formed, it is shunted to the private network UPF according to this shunting rule; if this packet is a service packet, the UPF shunts it through the IP address.

[0100] Further, after receiving the packet, the private network UPF modifies the destination address of this DNS request packet to the address of the internal network DNS, forwards it to the campus network gateway (usually a firewall device), and then reaches the internal network DNS server.

[0101] Even further, the internal network DNS server queries its own cache to find the IP address corresponding to this domain name and observes whether there is such an IP address.

[0102] Optionally, if there is such an IP address, check the cache again to check whether there is a reverse resolution record of this IP address.

[0103] Among them, since the IP address has been queried, the number of reverse resolution records is at least 1.

[0104] Further, if the number of reverse resolution records queried is 1, construct a DNS reverse resolution message, request this information from a higher-level DNS server through recursive query, obtain relevant records, and proceed to step S205.

[0105] It should be noted that DNS reverse resolution is the process of finding the corresponding domain name through an IP address. In this process, the DNS system needs to convert the given IP address into a special query format. For IPv4 addresses, such as 192.0.2.1, the domain name for reverse query will be 1.2.0.192.in-addr.arpa, that is, arrange the IP address in reverse order and append the.in-addr.arpa suffix. For IPv6 addresses, a similar method is adopted and the.ip6.arpa suffix is used.

[0106] It should also be noted that DNS reverse resolution can significantly improve network security and management efficiency. Through reverse resolution, the legitimacy of DNS query requests can be verified to ensure that the requests come from legitimate domain names or IP addresses, thereby reducing the impact of network attacks and spam traffic. At the same time, according to the reverse resolution results, DNS query requests from different sources can be diverted to appropriate processing paths, optimizing traffic distribution, improving resolution efficiency and network performance. In addition, the information provided by reverse resolution can also help network administrators better understand the traffic sources and network behaviors, so as to make more informed management decisions.

[0107] Even further, if the number of reverse resolution records queried is greater than 1, directly proceed to step S205.

[0108] Optionally, if there is no such IP address, initiate a query request to the root DNS server to obtain the IP address.

[0109] S205: Determine the traffic diversion strategy according to the application layer content of the service message.

[0110] In this embodiment, the UPF queries the application layer content of the service message to determine the traffic diversion strategy of the service message.

[0111] A packet splitting method provided in this embodiment, in response to a service packet sent by a user device, obtains the Internet Protocol destination address in the service packet, obtains a pre-configured shared network protocol destination address, determines whether the service packet needs to be split and detected according to the pre-configured shared network protocol destination address and the Internet Protocol destination address. If it is determined that the service packet is to be split and detected, then obtains the application layer content of the service packet, and determines the splitting strategy of the service packet according to the application layer content of the service packet. In this application, it is determined whether the service packet is detected and split through the pre-configured shared network protocol destination address and the Internet Protocol destination address in the service packet, which increases the accuracy of packet splitting, and thus improves the efficiency of packet splitting.

[0112] Figure 3 It is a schematic flow of a packet splitting method provided in an embodiment of this application Figure 2 , on the basis of the Figure 2 embodiment, as Figure 3 shown, the specific implementation steps of the above S205 include:

[0113] S301. Detect whether the application layer content contains the domain name information of the Journal Net corresponding to the network protocol destination address.

[0114] In this embodiment, the large network UPF queries the application layer content of the packet and determines whether the content contains the domain name information of the Journal Net corresponding to the public network IP address.

[0115] Among them, the access between the user device and the Journal Net server is usually completed through the HTTP or HTTPS protocol.

[0116] Specifically, if it is completed through the HTTP protocol, the Host Header contains the target domain name accessed by the user.

[0117] Specifically, if it is completed through the HTTPS protocol, in the TLS handshake stage of the HTTPS request, the user device will send SNI information indicating the target domain name, and then the domain name will be saved in the SNI information.

[0118] S302. If the application layer content contains the domain name information of the Journal Net corresponding to the network protocol destination address, then split the service packet to the dedicated network user plane function.

[0119] In this embodiment, if the judgment result of the large network UPF is yes, then the application layer content contains the domain name information of the Journal Net corresponding to the network protocol destination address, and the large network UPF splits the service packet to the dedicated network UPF, and then accesses the Journal Net service through the internal network.

[0120] S303. If the application layer content does not contain the domain name information of the Journal Net corresponding to the destination address of the network protocol, the service message is split to the public network to access the Journal Net service through the public network.

[0121] In this embodiment, if the judgment result of the large network UPF is negative, it means that the application layer content does not contain the domain name information of the Journal Net corresponding to the destination address of the network protocol. The large network UPF splits the service message to the public network to access the Journal Net service through the public network.

[0122] It should be noted that the large network UPF plans the network path for the service message by detecting whether the application layer content contains the domain name information of the Journal Net corresponding to the destination address of the network protocol, and accurately splits the service message to the target network domain, avoiding the waste of network resources caused by route redundancy and improving the message splitting efficiency and network performance.

[0123] It should also be noted that after splitting the service message to the public network to access the Journal Net service through the public network, it further includes:

[0124] S304. If the service message is split to the public network, it is detected whether the request message of the service message successfully establishes a connection with the response message.

[0125] In this embodiment, after the message initiated by the user equipment is transmitted through the public network, it is detected whether the request message of the service message successfully establishes a connection with the response message by determining whether the authorization and response of the Journal Net service are obtained.

[0126] S305. If it is detected that the request message of the service message does not successfully establish a connection with the response message, it is determined that the application layer information of the service message is encrypted and the service message is wrongly split.

[0127] Among them, the reason why the request message of the service message does not successfully establish a connection with the response message is that this service should be sent through the internal network and can obtain the authorized access to the Journal Net only after the SNAT address conversion of the internal network gateway. However, since the large network UPF does not detect the domain name information for the Journal Net, it is wrongly forwarded through the public network.

[0128] For example, since the user device may encrypt application layer information, such as TLS1.3 + ESNI / ECH. Encrypted Server Name Indication (ESNI) is an extension of TLS1.3 that encrypts the SNI field to prevent a man-in-the-middle from seeing the domain name information. Encrypted ClientHello (ECH) further encrypts the entire TLS ClientHello message, including the SNI information. In this case, the public network UPF will not be able to extract the domain name information and will thus incorrectly forward the packet over the public network.

[0129] S306. In response to the service packet retransmitted by the user device, split the service packet to the private network user plane function.

[0130] In this embodiment, when the access request initiated by the user device fails, the request will be re-initiated. At this time, the public network UPF splits the packet to the private network UPF. At the same time, the packet will obtain journal network authorization and access by means of the SNAT address translation of the internal network gateway.

[0131] In this embodiment, the public network UPF plans the network path for the service packet by detecting whether the application layer content contains the domain name information of the journal network corresponding to the destination address of the network protocol, and accurately splits the service packet to the target network domain; at the same time, by detecting whether the request packet and the response packet of the service packet are successful, it determines whether the service packet is incorrectly split due to the encryption of the application layer information of the service packet, and re-splits it in a timely manner. These all avoid the waste of network resources caused by route redundancy and improve the packet splitting efficiency and network performance.

[0132] Figure 4 Flow schematic of a packet splitting method provided for an embodiment of this application Figure 3 , on the basis of Figure 2 and Figure 3 the embodiment, as Figure 4 shown, before the above S202, it further includes:

[0133] S401. In response to the request packet sent by the user device, split the request packet to the user plane function.

[0134] S402. Receive the response packet returned by the internal network domain name system server; the response packet is generated by the internal network domain name system after receiving the request packet forwarded by the user plane function; the response packet includes a shared address identification bit.

[0135] Among them, the shared address identification bit is determined by the internal network domain name system according to the Internet protocol destination address in the request packet and the reverse resolution record corresponding to the Internet protocol destination address in the request packet.

[0136] Among them, the shared address identification bit is set in the reserved field of the response message.

[0137] It should be noted that this embodiment does not require developing new fields, but only uses existing fields to transmit information. It is a data interaction mechanism, and for UPF, base stations, and network transmission devices, the existing functions can be reused to complete it.

[0138] S403. Extract the Internet Protocol destination address and the corresponding shared identification bit in the response message.

[0139] S404. Determine the pre-configured shared network protocol destination address according to the Internet Protocol destination address and the corresponding shared identification bit in the response message.

[0140] Among them, the structure of a DNS message is divided into a header, a question section, an answer section, an authority section, and an additional section. Among them, the Header (header) has a fixed length of 12 bytes and contains the following fields:

[0141] Table 1: DNS message structure

[0142]

[0143] Specifically, by means of the Z field of the Header message, when the DNS server replies to the DNS request message, the last bit of these 3 bits is selectively used and set to 0 or 1.

[0144] For example, when this bit is set to 0, it means this is a normal DNS response message. Then the result of reverse resolution is that there is only one domain name under this IP address.

[0145] For example, when this bit is set to 1, it means that the public IP address corresponding to this domain name is a shared IP address. Then more than one public service shares this IP address, and it is assumed that this IP address is the public IP address.

[0146] It should be noted that by using the last bit of the Z field of the Header message to indicate the nature of the IP address, the traffic splitting mechanism can identify the response with the shared address identification bit and implement special processing strategies accordingly, such as load balancing and cache optimization, thereby significantly improving network efficiency and user experience.

[0147] In this embodiment, by using the last bit of the Z field of the Header message to indicate the nature of the IP address, the traffic splitting mechanism can identify the response with the shared address identification bit and implement special processing strategies accordingly, such as load balancing and cache optimization, thereby significantly improving network efficiency and user experience, and further improving the efficiency of message traffic splitting.

[0148] Figure 5 This is a schematic structural diagram of a packet splitting device provided by an embodiment of the present application. As Figure 5 shown, the device includes: a first acquisition module 51, a second acquisition module 52, a judgment module 53, a third acquisition module 54, and a determination module 55.

[0149] The first acquisition module 51 is configured to acquire the Internet Protocol destination address in the service packet in response to the service packet sent by the user equipment.

[0150] The second acquisition module 52 is configured to acquire a pre-configured shared network protocol destination address.

[0151] The judgment module 53 is configured to judge whether the service packet needs to be subjected to splitting detection according to the pre-configured shared network protocol destination address and the Internet Protocol destination address.

[0152] The third acquisition module 54 is configured to acquire the application layer content of the service packet if it is determined that the service packet is to be subjected to splitting detection.

[0153] The determination module 55 is configured to determine the splitting strategy of the service packet according to the application layer content of the service packet.

[0154] In a possible design, determining the splitting strategy of the service packet according to the application layer content of the service packet includes:

[0155] The determination module 55 is further configured to detect whether the application layer content contains the domain name information of the Journal Net corresponding to the network protocol destination address;

[0156] If the application layer content contains the domain name information of the Journal Net corresponding to the network protocol destination address, the service packet is split to the private network user plane function;

[0157] If the application layer content does not contain the domain name information of the Journal Net corresponding to the network protocol destination address, the service packet is split to the public network to access the Journal Net service through the public network.

[0158] In a possible design, after the service packet is split to the public network to access the Journal Net service through the public network, it further includes:

[0159] The determination module 55 is further configured to detect whether the request packet of the service packet successfully establishes a connection with the response packet if the service packet is split to the public network;

[0160] If it is detected that the request packet of the service packet does not successfully establish a connection with the response packet, it is determined that the application layer information of the service packet is encrypted and the service packet is wrongly split;

[0161] In response to the service message retransmitted by the user device, the service message is split to the private network user plane function.

[0162] In a possible design, according to the pre-configured shared network protocol destination address and the Internet protocol destination address, it is determined whether the service message needs to be split and detected, including:

[0163] The determination module 53 is further configured to determine that the service message needs to be split and detected if the pre-configured shared network protocol destination address includes the Internet protocol destination address.

[0164] In a possible design, before obtaining the pre-configured shared network protocol destination address, it further includes:

[0165] The second obtaining module 52 is further configured to split the request message to the user plane function in response to the request message sent by the user device;

[0166] Receive the response message returned by the intranet domain name system server; the response message is generated by the intranet domain name system after receiving the request message forwarded by the user plane function; the response message includes a shared address identification bit;

[0167] Extract the Internet protocol destination address and the corresponding shared identification bit in the response message;

[0168] Determine the pre-configured shared network protocol destination address according to the Internet protocol destination address and the corresponding shared identification bit in the response message.

[0169] In a possible design, the shared address identification bit is determined by the intranet domain name system according to the Internet protocol destination address in the request message and the reverse resolution record corresponding to the Internet protocol destination address in the request message.

[0170] The shared address identification bit is set in the reserved field of the response message.

[0171] A message splitting device provided in this embodiment can execute a message splitting method in the foregoing embodiment, and its implementation principle and technical effect are similar, which will not be elaborated here in this embodiment.

[0172] In the specific implementation of the foregoing message splitting method, each module can be implemented as a processor, and the processor can execute the computer execution instructions stored in the memory, so that the processor executes the foregoing message splitting method.

[0173] Figure 6 It is a schematic structural diagram of a message splitting device provided in an embodiment of the present application. As Figure 6As shown, the electronic device 60 includes: at least one processor 61 and a memory 62. The electronic device 60 further includes a communication component 63. Among them, the processor 61, the memory 62, and the communication component 63 are connected through a bus 64.

[0174] In a specific implementation process, at least one processor 61 executes the computer-executable instructions stored in the memory 62, so that at least one processor 61 executes a packet splitting method belonging to claims 1-7 executed on the side of the above packet splitting device.

[0175] For the specific implementation process of the processor 61, reference can be made to the above method embodiments. Their implementation principles and technical effects are similar, and will not be elaborated here in this embodiment. In the above embodiments, it should be understood that the processor may be a central processing unit (English: Central Processing Unit, abbreviated: CPU), or other general-purpose processors, digital signal processors (English: Digital Signal Processor, abbreviated: DSP), application specific integrated circuits (English: Application Specific Integrated Circuit, abbreviated: ASIC), etc. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc. The steps of the method disclosed in combination with the invention can be directly embodied as being executed by a hardware processor, or executed by a combination of hardware and software modules in the processor.

[0176] The memory may include high-speed RAM memory and may also include non-volatile storage NVM, such as at least one disk memory.

[0177] The bus may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, the buses in the drawings of this application are not limited to only one bus or one type of bus.

[0178] The functions implemented by the above-mentioned packet splitting device and master control device are introduced for the solution provided by the embodiments of the present invention. It can be understood that in order to implement the above functions, the packet splitting device or the master control device includes the corresponding hardware structures and / or software modules for executing each function. Combining the units and algorithm steps of each example described in the embodiments disclosed in the embodiments of the present invention, the embodiments of the present invention can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the technical solution of the embodiments of the present invention.

[0179] This application also provides a computer-readable storage medium, in which computer-executable instructions are stored, and when the computer-executable instructions are executed by a processor, they are used to implement a packet splitting method as described above.

[0180] The above-readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk. The readable storage medium can be any available medium accessible by a general-purpose or special-purpose computer.

[0181] An exemplary readable storage medium is coupled to the processor, so that the processor can read information from the readable storage medium and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can be located in an application specific integrated circuit (ASIC). Of course, the processor and the readable storage medium can also exist as discrete components in an electronic device or a master control device.

[0182] This application also provides a computer program product, including a computer program. The computer program is stored in a readable storage medium, and at least one processor of the electronic device can read the computer program from the readable storage medium, and at least one processor executes the computer program to enable the electronic device to execute the solution provided in any of the above embodiments.

[0183] Those of ordinary skill in the art will understand that all or part of the steps of implementing the above method embodiments can be completed by hardware related to program instructions. The foregoing program can be stored in a computer-readable storage medium. When the program is executed, it performs the steps including those of the above method embodiments; and the foregoing storage medium includes various media such as ROM, RAM, magnetic disks, or optical discs that can store program codes.

[0184] So far, the technical solutions of the present application have been described in conjunction with the preferred embodiments shown in the accompanying drawings. However, it is easy for those skilled in the art to understand that the protection scope of the present application is obviously not limited to these specific embodiments. The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that they can still modify the technical solutions described in the foregoing embodiments, or perform equivalent replacements on some or all of the technical features; and these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the various embodiments of the present application.

Claims

1. A message splitting method, characterized in that, Including: In response to a service message sent by a user device, obtain the Internet Protocol destination address in the service message; Obtain a pre-configured shared network protocol destination address; According to the pre-configured shared network protocol destination address and the Internet Protocol destination address, determine whether the service message needs to be subjected to traffic splitting detection; If it is determined that the service message is to be subjected to traffic splitting detection, obtain the application layer content of the service message; Determine the traffic splitting strategy of the service message according to the application layer content of the service message.

2. The method according to claim 1, wherein The determining the traffic splitting strategy of the service message according to the application layer content of the service message includes: Detect whether the application layer content contains domain name information of the Journal Net corresponding to the network protocol destination address; If the application layer content contains domain name information of the Journal Net corresponding to the network protocol destination address, split the service message to the private network user plane function; If the application layer content does not contain domain name information of the Journal Net corresponding to the network protocol destination address, split the service message to the public network to access the Journal Net service through the public network.

3. The method according to claim 2, wherein After the splitting the service message to the public network to access the Journal Net service through the public network, it further includes: If the service message is split to the public network, detect whether the request message of the service message successfully establishes with the response message; If it is detected that the request message of the service message does not successfully establish with the response message, determine that the application layer information of the service message is encrypted and the service message is mis-split; In response to the re-transmitted service message of the user device, split the service message to the private network user plane function.

4. The method according to claim 1, wherein The determining whether the service message needs to be subjected to traffic splitting detection according to the pre-configured shared network protocol destination address and the Internet Protocol destination address includes: If the pre-configured shared network protocol destination address includes the Internet Protocol destination address, determine that the service message needs to be subjected to traffic splitting detection.

5. The method according to any one of claims 1 to 4, characterized in that Before the obtaining the pre-configured shared network protocol destination address, it further includes: In response to a request message sent by a user device, split the request message to the user plane function; Receive a response message returned by an intranet domain name system server; the response message is generated by the intranet domain name system after receiving the request message forwarded by the user plane function; the response message includes a shared address flag bit; Extract the Internet Protocol destination address and the corresponding shared flag bit in the response message; Determine the pre-configured shared network protocol destination address according to the Internet Protocol destination address and the corresponding shared flag bit in the response message.

6. The method according to claim 5, wherein The shared address flag bit is determined by the intranet domain name system according to the Internet Protocol destination address in the request message and the reverse resolution record corresponding to the Internet Protocol destination address in the request message; The shared address flag bit is set in the reserved field of the response message.

7. A message shunting device, characterized in that, Including: A first obtaining module, configured to obtain the Internet Protocol destination address in the service message in response to a service message sent by a user device; A second obtaining module, configured to obtain a pre-configured shared network protocol destination address; A determination module, configured to determine whether the service message needs to be subjected to traffic splitting detection according to the pre-configured shared network protocol destination address and the Internet protocol destination address; A third acquisition module, configured to acquire the application layer content of the service message if it is determined that the service message is to be subjected to traffic splitting detection; A determination module, configured to determine the traffic splitting policy of the service message according to the application layer content of the service message.

8. A message shunting device, characterized in that, Comprising: A memory and a processor; The memory stores computer execution instructions; The processor executes the computer execution instructions stored in the memory, so that the processor executes the method according to any one of claims 1-7.

9. A computer-readable storage medium, characterized in that, Computer execution instructions are stored in the computer-readable storage medium, and when the computer execution instructions are executed by the processor, they are used to implement the method according to any one of claims 1-7.

10. A computer program product, characterized in that, Comprising a computer program, which when executed by a processor implements the method according to any one of claims 1-7.

Images