CN116938873A - Diversion method, network element and medium of domain name query request message - Google Patents

Abstract

The disclosure provides a method for distributing domain name query requests, a network element and a medium, and belongs to the technical field of communication. The method comprises the following steps: receiving a first domain name query request message sent by UE; determining whether the domain name inquired by the UE is the domain name of the private network according to the first domain name inquiry request message; under the condition that the domain name inquired by the UE is the domain name of the target private network, acquiring the addresses and port numbers of M domain name system servers included in the target private network, wherein M is an integer greater than 1; rewriting the destination address and port number of the first domain name query request message as the address and port numbers of the M domain name system servers to obtain M second domain name query request messages; and respectively sending the M second domain name inquiry request messages to the M domain name system servers. Based on the technical scheme provided by the embodiment of the disclosure, the problem that the UE cannot communicate with the application server of the private network possibly caused by the shunt strategy of the related technology can be solved.

Description

Diversion method, network element and medium of domain name query request message

Technical Field

The disclosure belongs to the technical field of communication, and in particular relates to a method, a network element and a medium for distributing domain name query request messages.

Background

In the ul cl (up link classifier ) offloading scenario of the 5G (5 th Generation Mobile Communication Technology, fifth generation mobile communication technology) network, when a UE (User Equipment) establishes a PDU Session (Protocol Data Unit Session protocol data unit Session), it is required to acquire an IP address (Internet Protocol Address ) of a DNS server of a private network to communicate with an application server of the private network.

Typically, when the SMF (Session Management Function ) determines that the UE location changes, triggers an added edge UPF (User Plane Function ) to offload, the SMF requests an offload policy from the PCF (Packet Control Function ), and the PCF issues an offload rule to the edge UPF.

After the edge UPF receives the DNS query request sent by the UE, the edge UPF may parse URL (Uniform Resource Locator ) information in the DNS request, and if it is determined that the DNS query request needs to be shunted to the DNS server of the private network, the UPF modifies the destination address and the port number in the DNS query request to be the address and the port number of the DNS server of the private network, so that the DNS request may be redirected to the DNS server of the private network.

However, in the current splitting manner of the domain name query request message, the issued splitting policy only configures an address and a port number of a private network DNS server, and if the configured private network DNS server fails, a response message cannot be returned for the UE, so that the UE cannot communicate with an application server of the private network.

Disclosure of Invention

The embodiment of the disclosure aims to provide a method, a network element and a medium for offloading a domain name query request, which can solve the problem that a offloading policy of related technology may cause that a UE cannot communicate with an application server of a private network.

In order to solve the above technical problems, the present disclosure is implemented as follows:

in a first aspect, an embodiment of the present disclosure provides a method for splitting a domain name query request, where the method includes: receiving a first domain name query request message sent by User Equipment (UE); determining whether the domain name queried by the UE is the domain name of a private network according to the first domain name query request message; under the condition that the domain name inquired by the UE is the domain name of a target private network, acquiring the addresses and port numbers of M domain name system servers included in the target private network, wherein M is an integer greater than 1; rewriting the destination address and port number of the first domain name query request message to obtain M second domain name query request messages for the addresses and port numbers of the M domain name system servers; and respectively sending the M second domain name inquiry request messages to the M domain name system servers.

In a second aspect, an embodiment of the present disclosure provides a user plane function network element, where the user plane function network element includes: the device comprises a receiving module, a determining module, an acquiring module, a rewriting module and a sending module; the receiving module is used for receiving a first domain name query request message sent by User Equipment (UE); the determining module is configured to determine, according to the first domain name query request packet received by the receiving module, whether the domain name queried by the UE is a domain name of a private network; the acquiring module is configured to acquire addresses and port numbers of M domain name system servers included in a target private network, where M is an integer greater than 1, when the determining module determines that the domain name queried by the UE is a domain name of the target private network; the rewriting module is configured to rewrite the destination address and the port number of the first domain name query request packet, and obtain M second domain name query request packets for the addresses and the port numbers of the M domain name system servers acquired by the acquiring module; the sending module is configured to send the M second domain name query request messages rewritten by the rewriting module to the M domain name system servers respectively.

In a third aspect, an embodiment of the present disclosure provides a user plane function network element, where the user plane function network element includes a processor, a memory, and a program or an instruction stored on the memory and capable of running on the processor, where the program or the instruction is executed by the processor to implement the steps of the splitting method of the domain name query request according to the first aspect.

In a fourth aspect, embodiments of the present disclosure provide a readable storage medium having stored thereon a program or instructions which, when executed by a processor, implement the steps of the method for splitting a domain name query request according to the first aspect.

In a fifth aspect, an embodiment of the present disclosure provides a chip, where the chip includes a processor and a communication interface, where the communication interface is coupled to the processor, and the processor is configured to execute a program or an instruction, and implement a method for splitting a domain name query request according to the first aspect.

In a sixth aspect, embodiments of the present disclosure provide a computer program product comprising instructions which, when run on a computer, cause the computer to perform the steps of the splitting method of domain name query requests as described in the first aspect.

In the embodiment of the present disclosure, first, after an edge UPF receives a first domain name query request packet sent by a UE, the edge UPF may first determine whether a domain name queried by the first domain name query request packet is a domain name of a private network, and in the case of determining that the UE queries a domain name of a target private network, the edge UPF may determine, according to an identifier of the target private network to be queried, the number of DNS servers included in the target private network, obtain an address and a port number of each DNS server in the target private network, then rewrite a destination address and a port number in the first domain name query request packet, and finally, the edge UPF sends the rewritten domain name query request packet to each DNS server in the private network. Because the edge UPF is a domain name query request message directly rewritten according to the number of DNS servers of the private network, the domain name query request message can be sent to multiple DNS servers of the private network respectively, and the problem that the UE cannot communicate with the application servers in the private network because the address of the application server in the private network cannot be returned to the UE due to failure collision of one DNS server under the condition that the domain name query request message is sent to the other DNS servers only can be avoided.

Drawings

Fig. 1 is a schematic diagram of a DNS query framework provided in an embodiment of the present disclosure;

fig. 2 is a flow chart of a method for splitting a domain name query request according to an embodiment of the disclosure;

FIG. 3 is a schematic diagram of a split logic of a domain name query request according to an embodiment of the present disclosure;

FIG. 4 is a schematic diagram of processing logic of a domain name query response provided by an embodiment of the present disclosure;

fig. 5 is one of possible structural diagrams of a user plane function network element according to an embodiment of the present disclosure;

fig. 6 is a second possible structural diagram of a user plane function network element according to an embodiment of the present disclosure;

fig. 7 is a schematic hardware diagram of a user plane function network element according to an embodiment of the present disclosure.

Detailed Description

The following description of the technical solutions in the embodiments of the present disclosure will be made clearly and completely with reference to the accompanying drawings in the embodiments of the present disclosure, and it is apparent that the described embodiments are some embodiments of the present disclosure, but not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art without inventive effort, based on the embodiments in this disclosure are intended to be within the scope of this disclosure.

The terms first, second and the like in the description and in the claims, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged, where appropriate, such that embodiments of the disclosure may be practiced in sequences other than those illustrated and described herein, and that the objects identified by "first," "second," etc. are generally of the same type and are not limited to the number of objects, e.g., the first object may be one or more. Furthermore, in the description and claims, "and/or" means at least one of the connected objects, and the character "/", generally means that the associated object is an "or" relationship.

It is noted that the techniques described in embodiments of the present disclosure are not limited to LTE (Long Term Evolution )/LTE-a (LTE-Advanced, evolution of LTE) systems, but may also be used in other wireless communication systems, such as CDMA (Code Division Multiple Access ), TDMA (Time Division Multiple Access, time division multiple access), FDMA (Frequency Division Multiple Access ), OFDMA (Orthogonal Frequency Division Multiple Access, orthogonal frequency division multiple access), SC-FDMA (Single-carrier Frequency-Division Multiple Access, single carrier frequency division multiple access), and other systems. The terms "system" and "network" in embodiments of the application are often used interchangeably, and the techniques described may be used for both the above-mentioned systems and radio technologies, as well as other systems and radio technologies. However, the following description describes an NR system for purposes of example and NR terminology is used in much of the following description, although the techniques may also be applied to applications other than NR system applications, such as 6G (6 th Generation) communication systems.

The domain name query request method provided by the embodiment of the present disclosure is described in detail below with reference to the accompanying drawings through specific embodiments and application scenarios thereof.

Fig. 1 is a schematic diagram of a DNS query framework provided in an embodiment of the present disclosure. As shown in fig. 1, the query framework includes: UE100, gNB 101, UPF 102 (edge), UPF 103 (large network), DNS server 104 (large network), DNS master server 105 (master) of private network 1, DNS server 106 (standby) of private network 1. The UE100 is connected to the UPF 102 through the gNB 101, the UPF 102 is connected to the UE100 through an N3 interface, is connected to the UPF 103 through an N9 interface, and is connected to the DNS server 105 and the DNS server 106 through an N6 interface. The UPF 103 is connected to the DNS server 104 through an N6 interface.

It should be noted that fig. 1 is only a schematic diagram, and in practical application, a large network may include an application server and at least one DNS server, for example, a large network may include a primary DNS server and a backup DNS server; the private network may also include an application server and at least one DNS server, and in the context of the disclosed embodiments, the private network is described as including at least two DNS servers, one being a primary DNS server and the other being a backup DNS server. Wherein the application servers in private and large networks are not shown in fig. 1.

It should be noted that, in the embodiment of the present disclosure, the edge UPF is taken as a user plane function network element as an execution body to perform an exemplary description, and the embodiment of the present disclosure does not limit a specific network element of the user plane function network element.

Fig. 2 is a flow chart of a method for splitting a domain name query request according to an embodiment of the disclosure, as shown in fig. 2, the method includes the following steps S201 to S205:

s201, the edge UPF receives a first domain name query request message sent by the UE.

It should be noted that, in the embodiment of the present disclosure, before S201 described above, the UE may first establish a PDU session to the large network UPF through the SMF to obtain an address of a DNS server of the large network, and then the UE sends a domain name query request (i.e., a first domain name query request packet) to the DNS server of the large network.

The first domain name query request message may include an address and a port number of a DNS server of the large network, and a domain name to be queried.

In this embodiment of the present disclosure, the address of the DNS server may be an IP address, or may be another address that may be uniquely identified, which is not specifically limited in this embodiment of the present disclosure.

S202, the edge UPF determines whether the domain name inquired by the UE is the domain name of the private network according to the first domain name inquiry request message.

It may be appreciated that the first domain name query request message includes a domain name to be queried by the UE.

In the embodiment of the present disclosure, an example is described in which a UE needs to access a private network.

S203, under the condition that the domain name queried by the UE is the domain name of the target private network, the edge UPF acquires the addresses and port numbers of M domain name system servers included in the target private network.

Wherein M is an integer greater than 1.

It is understood that a private network may include at least two DNS servers (i.e., domain name system servers).

S204, the edge UPF rewrites the destination address and the port number of the first domain name query request message to obtain M second domain name query request messages for the addresses and the port numbers of the M domain name system servers.

That is, the edge UPF may copy the first domain name query request packet into M domain name query request packets, modify the destination address in each domain name query request packet into addresses of M domain name system servers, and modify the port number in each domain name query request packet into port numbers of M domain name system servers.

S205, the edge UPF respectively sends the M second domain name inquiry request messages to M domain name system servers.

It can be understood that the edge UPF sends corresponding second domain name query request messages to M domain name system servers according to the rewritten destination address and port number in each second domain name query request message.

Illustratively, in connection with fig. 1, after receiving the DNS request message 1 sent by the UE100, the UPF 102 determines that the domain name included in the DNS request message 1 is the domain name of the private network 1, the UPF 102 determines that the number of DNS servers of the private network 1 is 2, and obtains the addresses and port numbers of the 2 DNS servers of the private network 1, and then rewrites the DNS request message 1 into a DNS request message 2 and a DNS request message 3, where the destination address and port number of the DNS request message 2 is the address and port number of the DNS server 105, and the destination address and port number of the DNS request message 3 is the address and port number of the DNS server 106, and then the UPF 102 may send the DNS request message 2 to the DNS server 105 in the private network 1 and send the DNS request message 3 to the DNS server 106.

The embodiment of the disclosure provides a method for splitting a domain name query request, firstly, after an edge UPF receives a first domain name query request message sent by a UE, the edge UPF may first determine whether a domain name queried by the first domain name query request message is a domain name of a private network, under the condition that it is determined that the UE queries a domain name of a target private network, the edge UPF may determine, according to an identifier of the target private network to be queried, the number of DNS servers included in the target private network, obtain an address and a port number of each DNS server in the target private network, then rewrite a destination address and a port number in the first domain name query request message, and finally the edge UPF sends the rewritten domain name query request message to each DNS server in the private network. Because the edge UPF is a domain name query request message directly rewritten according to the number of DNS servers of the private network, the domain name query request message can be sent to multiple DNS servers of the private network respectively, and the problem that the UE cannot communicate with the application servers in the private network because the address of the application server in the private network cannot be returned to the UE due to failure collision of one DNS server under the condition that the domain name query request message is sent to the other DNS servers only can be avoided.

In the embodiment of the disclosure, a DNS rewriting rule table is preconfigured in an edge UPF, and a corresponding relationship among a private network domain name of each private network, an address of a private network domain name system server, and a port number of the private network domain name system server is established; and constructing a DNS rewriting record table in the edge UPF, and establishing a corresponding relation among the session ID, the domain name of the inquired private network and the destination address before rewriting, so that the edge UPF records the DNS rewriting record in the PDU session. Illustratively, the DNS rewrite rule table and DNS rewrite record table may be configured in the edge UPF through a network management interface.

Optionally, in the method for splitting a domain name query request provided in the embodiment of the present disclosure, S203 described above may be specifically executed by S23 described below:

s23, the edge UPF acquires the addresses and port numbers of M domain name system servers of the target private network according to the rewriting rule table and the domain name of the target private network.

The rewriting rule table comprises a private network domain name, an address of a private network domain name system server and a corresponding relation of ports of the private network domain name system server.

It will be appreciated that the edge UPF may have configured therein a rewrite rule table that may indicate the number of DNS servers included by each private network, as well as the address and port number of each DNS server. After the edge UPF obtains the address and the port number of each domain name system server of the target private network queried by the UE based on the rewrite rule table, the received first domain name query request message is rewritten by adopting the obtained address and port number of each domain name system server, thereby obtaining the domain name query request message sent to each domain name system server.

Illustratively, table 1 is one exemplary table of a DNS rewrite rules table. The description will be given taking an address as an IP address.

TABLE 1

With reference to table 1 and fig. 3, assuming that the UE sends a DNS request message 1 to the UPF, the UPF determines that the domain name in the DNS request message 1 is domain name 1, the address is IP3, the UPF queries a DNS rewrite rule table, determines that the domain name 1 includes 2 DNS servers, the addresses are IP 1 and IP 2, and the port numbers are port 1 and port 2, and copies the DNS request message 1 into the DNS request message 1 (the destination address is IP 1, the port is port 1) and the DNS request message 2 (the destination address is IP 2, the port is port 2) according to the DNS rewrite rule table after receiving the DNS request message 1.

Based on the scheme, the edge UPF can query and obtain the addresses and port numbers of M domain name system servers of the target private network according to the configured rewriting rule table and the domain name of the target private network, so that the destination addresses and port numbers in the rewritten M domain name query request messages can be accurately determined.

Optionally, in the method for splitting a domain name query request provided in the embodiment of the present disclosure, after S204 described above, the following S205 may be further included:

s205, generating a target table item of the domain name query rewrite record by the edge UPF.

Wherein, the target table entry includes: the method comprises the steps of establishing a session identifier by UE, inquiring a domain name of a target private network by the UE and inquiring a destination address of a request message by a first domain name.

Referring to fig. 3 and table 2, after the edge UPF rewrites the domain name query request packet, the edge UPF may add a table entry in table 2, and if the session ID established by the UE is ID 1, the edge UPF adds a row of table entries corresponding to ID 1 in table 2 based on the domain name and destination address of the DNS request packet 1. Wherein table 2 is an exemplary table of DNS record rewrites tables.

TABLE 2

Session ID	Domain name	Destination address before overwriting
			ID 2	Domain name 2	IP 4
ID 1	Domain name 1	IP 3

Based on the scheme, after the domain name query request message is rewritten, the edge UPF can generate a domain name query rewrite record, and the domain name query rewrite record is stored in the query rewrite record table, so that the edge UPF determines how to process the received response message under the condition that the edge UPF receives the response message corresponding to the domain name query request message.

Optionally, in the method for splitting a domain name query request provided in the embodiment of the present disclosure, after S204 described above, the following S206 and S207, or S206 and S208 may be further included:

s206, under the condition that the first response message is received, the edge UPF determines whether a target table entry exists in the domain name query rewrite record.

It should be noted that, the edge UPF may query the DNS overwrite table in combination with the identifier of the domain name in the response packet and the identifier of the PDU session.

S207, if a target table entry exists in the domain name query rewrite record, the edge UPF determines that the first response message is the first received response message.

S208, if the target table item does not exist in the domain name query rewrite record, the edge UPF determines that the first response message is a response message except the first received response message.

It can be understood that after the edge UPF sends a domain name query request to each DNS server of the target private network, each DNS server performs domain name resolution according to the received collocated domain name query request, obtains an address of an application server corresponding to the domain name, and then returns a DNS response message to the edge UPF. It can be understood that the response messages returned by the DNS servers have different return times, and because the addresses of the application servers returned by the DNS servers are the same, the UPF only needs to forward one response message to the UE.

Based on the scheme, after the edge UPF receives a response message, whether the response message sent by the DNS server is the first received response message can be determined according to whether the target table entry in the rewriting record table exists, so that how to process the received response message can be determined.

Optionally, in the method for splitting a domain name query request provided in the embodiment of the present disclosure, after S207 described above, the following S209 and S210 may be further included:

s209, deleting a target table item by the edge UPF under the condition that the received first response message is the first received response message, and rewriting the source address of the first response message to be the destination address of the first domain name query request message to obtain a second response message.

Referring to fig. 4 and table 2, the upf first receives a DNS response message 1 sent by the DNS server 1, determines that a target table entry exists according to the domain name 1 and the session 1 of the PDU session, uses the destination address IP3 recorded in the target table entry as the source address of the response message 3 (i.e., the second response message), and then deletes the table entries corresponding to the domain name 1 and the session 1 in table 2.

S210, the edge UPF sends a second response message to the UE.

It may be appreciated that in the disclosed embodiment, when the edge UPF queries the target table entry, it may be determined that the first response message currently received is the first response message received for the first query request message, and then the edge UPF may rewrite the source address of the first response message as the destination address of the first domain name query request message, obtain the second response message, and send the second response message to the UE, so that the UE does not have a perception of being rewritten.

Based on the scheme, when the edge UPF receives the first response message, the edge UPF can rewrite the destination address of the first domain name query request message recorded in the target table entry to the source address of the first response message, then send the first response message to the UE, and delete the target table entry, so that when the response message is received again subsequently, the first received response message can be determined.

Optionally, in the method for splitting a domain name query request provided in the embodiment of the present disclosure, after S208 described above, the following S211 may further be included:

s211, discarding the first response message by the edge UPF under the condition that the received first response message is the first received response message.

It can be appreciated that the edge UPF only needs to forward the response message sent by one DNS server to the UE, and in the case that the second response message has been forwarded to the UE, the edge UPF may not forward the response messages sent by other DNS servers of the target private network.

Referring to fig. 4, in the case that the UPF receives the DNS response message 2, the UPF queries the DNS overwrite record table to determine whether the DNS response message 2 is the first received response message, and in the case that the target entry is not queried, the UPF discards the DNS response message 2.

Based on the scheme, after receiving a response message, if the edge UPF determines that the response message is not the first received response message corresponding to the first domain name request message, the edge UPF directly discards the received response message, so that the repeated sending of the response message to the UE is avoided.

It should be noted that, the splitting method of the domain name query request provided by the embodiment of the present disclosure may also be applied to a 5G customized network neighbor mode, that is, when the edge UPF provides communication services for both the private network and the large network, the UE needs to query the large network domain name and the private network domain name at the same time. In the related art, the UE can be assigned only to the address of the primary, backup or more DNS servers of the large network, and cannot be assigned to the address of the DNS server of the private network. By adopting the method for splitting the domain name query request, which is provided by the embodiment of the disclosure, the requirement of the UE for querying the private network domain name can be met, and the scene of more DNS servers in the private network can be supported.

It should be noted that, in the method for splitting a domain name query request provided in the embodiments of the present disclosure, the execution body may also be a splitting device of the domain name query request, or a control module of the splitting device of the domain name query request, which is used for executing the splitting method of the domain name query request. In the embodiment of the present disclosure, a method for executing splitting of a domain name query request by a splitting device of a domain name query request is taken as an example, and the splitting device of the domain name query request provided in the embodiment of the present disclosure is described.

Fig. 5 is a schematic structural diagram of a user plane functional network element provided in an embodiment of the present disclosure, and as shown in fig. 5, a user plane functional network element 500 includes: a receiving module 501, a determining module 502, an acquiring module 503, a rewriting module 504, and a transmitting module 505; a receiving module 501, configured to receive a first domain name query request packet sent by a user equipment UE; a determining module 502, configured to determine, according to the first domain name query request packet received by the receiving module, whether the domain name queried by the UE is a domain name of a private network; an obtaining module 503, configured to obtain, when the determining module determines that the domain name queried by the UE is a domain name of a target private network, addresses and port numbers of M domain name system servers included in the target private network, where M is an integer greater than 1; a rewriting module 504, configured to rewrite the destination address and the port number of the first domain name query request packet, and obtain M second domain name query request packets for the addresses and the port numbers of the M domain name system servers acquired by the acquiring module; and the sending module 505 is configured to send the M second domain name query request messages rewritten by the rewriting module to the M domain name system servers respectively.

Optionally, the obtaining module is specifically configured to: according to the rewriting rule table and the domain name of the target private network, obtaining the addresses and port numbers of M domain name system servers of the target private network; the rewrite rule table comprises the corresponding relation among private network domain names, addresses of private network domain name system servers and ports of the private network domain name system servers.

Optionally, the user plane function network element further includes: a generating module; the generating module is used for generating a target table item of a domain name query rewrite record after rewriting the destination address and the port number of the first domain name query request message to be the address and the port number of the M domain name system servers; wherein the target table entry includes: the session identifier established by the UE, the domain name of the target private network queried by the UE, and the destination address of the first domain name query request message.

Optionally, the determining module is further configured to determine, after the sending module sends the M second domain name query request messages to the M domain name system servers, whether a target table entry exists in the domain name query rewrite record if a first response message is received; if the target table item exists in the domain name query rewrite record, determining that the first response message is a first received response message; or if the target table entry does not exist in the domain name query rewrite record, determining that the first response message is the response message except the first received response message.

Optionally, the user plane function network element further includes: deleting the module; the deleting module is used for deleting the target table item under the condition that the received first response message is the first received response message; the rewriting module is further configured to rewrite the source address of the first response message to be the destination address of the first domain name query request message, so as to obtain a second response message; and the sending module is also used for sending the second response message to the UE.

Optionally, the sending module is further configured to discard the first response packet if the received first response packet is a response packet other than the first received response packet.

The embodiment of the disclosure provides a user plane functional network element, after the user plane functional network element receives a first domain name query request message sent by a UE, the user plane functional network element may first determine whether a domain name queried by the first domain name query request message is a domain name of a private network, and under the condition that the domain name of a target private network queried by the UE is determined, the user plane functional network element may determine the number of DNS servers included in the target private network according to an identifier of the target private network to be queried, obtain an address and a port number of each DNS server in the target private network, then rewrite a destination address and a port number in the first domain name query request message, and finally the user plane functional network element sends the rewritten domain name query request message to each DNS server in the private network. Because the user plane function network element is the domain name query request message directly rewritten according to the number of the DNS servers of the private network, the domain name query request message can be respectively sent to a plurality of DNS servers of the private network, and the problem that the UE cannot communicate with the application servers in the private network because the address of the application server in the private network cannot be returned to the UE due to reasons such as failure conflict of the DNS server under the condition that the domain name query request message is only sent to one of the DNS servers can be avoided.

The user plane function network element 500 provided in the embodiments of the present disclosure can implement each process implemented by the embodiments of the methods of fig. 1 to fig. 4, and in order to avoid repetition, a description is omitted here.

Illustratively, taking the UPF as the above-mentioned user plane function network element, the DPI (Deep Packet Inspection, deep packet inspection technology) function module in the UPF may implement the steps implemented by the determining module 502 and the obtaining module 503, the DNS overwrite function module in the UPF may implement the steps implemented by the overwrite module 504, and the forwarding module in the UPF may implement the steps implemented by the sending module 505.

Optionally, as shown in fig. 6, the embodiment of the present disclosure further provides a user plane function network element 600, which includes a processor 601, a memory 602, and a program or an instruction stored in the memory 602 and capable of running on the processor 601, where the program or the instruction implements each process of the above-mentioned splitting method embodiment of the domain name query request when executed by the processor 601, and the same technical effects can be achieved, so that repetition is avoided and redundant description is omitted herein.

It should be noted that the network entity or the user plane function network element 700 shown in fig. 7 is only an example, and should not impose any limitation on the functions and the scope of use of the embodiments of the present disclosure.

As shown in fig. 7, the user plane function network element 700 includes a central processing unit (Central Processing Unit, CPU) 701 that can perform various appropriate actions and processes according to a program stored in a ROM (Read Only Memory) 702 or a program loaded from a storage section 708 into a RAM (Random Access Memory ) 703. In the RAM 703, various programs and data required for the system operation are also stored. The CPU 701, ROM 702, and RAM 703 are connected to each other through a bus 704. An I/O (Input/Output) interface 705 is also connected to bus 704.

The following components are connected to the I/O interface 705: an input section 706 including a keyboard, a mouse, and the like; an output section 707 including a CRT (Cathode Ray Tube), an LCD (Liquid Crystal Display ), and the like, a speaker, and the like; a storage section 708 including a hard disk or the like; and a communication section 709 including a network interface card such as a LAN (Local Area Network, wireless network) card, a modem, or the like. The communication section 709 performs communication processing via a network such as the internet. The drive 710 is also connected to the I/O interface 705 as needed. A removable medium 711 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 710 as necessary, so that a computer program read therefrom is mounted into the storage section 708 as necessary.

In particular, according to embodiments of the present disclosure, the processes described below with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method shown in the flowcharts. In such an embodiment, the computer program may be downloaded and installed from a network via the communication portion 709, and/or installed from the removable medium 711. When being executed by a central processing unit (CPU 701), performs the various functions defined in the system of the present application.

The embodiment of the disclosure further provides a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or the instruction is executed by a processor, the processes of the above-mentioned splitting method embodiment of the domain name query request are implemented, and the same technical effects can be achieved, so that repetition is avoided, and no further description is given here.

Wherein the processor is a processor in the electronic device described in the above embodiment. The readable storage medium includes computer readable storage medium such as ROM, RAM, magnetic disk or optical disk.

The embodiment of the disclosure further provides a chip, where the chip includes a processor and a communication interface, where the communication interface is coupled to the processor, and the processor is configured to run a program or an instruction, implement each process of the above-mentioned splitting method embodiment of the domain name query request, and achieve the same technical effect, so that repetition is avoided, and no further description is given here.

It should be understood that the chips referred to in the embodiments of the present disclosure may also be referred to as system-on-chip chips, chip systems, or system-on-chip chips, etc.

The embodiments of the present disclosure provide a computer program product including instructions, which when executed on a computer, cause the computer to perform the steps of the method for splitting a domain name query request as described above, and achieve the same technical effects, and are not repeated here.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element. Furthermore, it should be noted that the scope of the methods and apparatus in the embodiments of the present disclosure is not limited to performing the functions in the order shown or discussed, but may also include performing the functions in a substantially simultaneous manner or in an opposite order depending on the functions involved, e.g., the described methods may be performed in an order different from that described, and various steps may also be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present disclosure may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (e.g., ROM/RAM, magnetic disk, optical disk), including several instructions for causing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the method described in the embodiments of the present disclosure.

The embodiments of the present disclosure have been described above with reference to the accompanying drawings, but the present disclosure is not limited to the above-described embodiments, which are merely illustrative and not restrictive, and many forms may be made by those of ordinary skill in the art without departing from the spirit of the disclosure and the scope of the claims, which are all within the protection of the present disclosure.

Claims (10)

1. A method for offloading a domain name query request, applied to a user plane function network element, the method comprising:

receiving a first domain name query request message sent by User Equipment (UE);

determining whether the domain name queried by the UE is the domain name of a private network according to the first domain name query request message;

under the condition that the domain name inquired by the UE is the domain name of a target private network, acquiring the addresses and port numbers of M domain name system servers included in the target private network, wherein M is an integer greater than 1;

rewriting the destination address and port number of the first domain name query request message to obtain M second domain name query request messages for the addresses and port numbers of the M domain name system servers;

and respectively sending the M second domain name inquiry request messages to the M domain name system servers.

2. The method according to claim 1, wherein the obtaining addresses and port numbers of M domain name system servers included in the target private network includes:

according to the rewriting rule table and the domain name of the target private network, obtaining the addresses and port numbers of M domain name system servers of the target private network;

the rewrite rule table comprises the corresponding relation among private network domain names, addresses of private network domain name system servers and ports of the private network domain name system servers.

3. The method of claim 2, wherein after overwriting the destination address and port number of the first domain name query request message with the address and port numbers of the M domain name system servers, the method further comprises:

generating a target table item of a domain name query rewrite record;

wherein the target table entry includes: the session identifier established by the UE, the domain name of the target private network queried by the UE, and the destination address of the first domain name query request message.

4. A method according to claim 3, wherein after the M second domain name query request messages are sent to the M domain name system servers, the method further comprises:

under the condition of receiving a first response message, determining whether a target table entry exists in the domain name query rewrite record;

if the target table item exists in the domain name query rewrite record, determining that the first response message is a first received response message; or alternatively, the process may be performed,

and if the target table item does not exist in the domain name query rewrite record, determining that the first response message is the response message except the first received response message.

5. The method according to claim 4, wherein the method further comprises:

deleting the target table item under the condition that the received first response message is a first received response message, and rewriting a source address of the first response message to be a destination address of the first domain name query request message to obtain a second response message;

and sending the second response message to the UE.

6. The method according to claim 4, wherein the method further comprises:

and discarding the first response message under the condition that the received first response message is the response message except the first received response message.

7. A user plane function network element, characterized in that the user plane function network element comprises: the device comprises a receiving module, a determining module, an acquiring module, a rewriting module and a sending module;

the receiving module is used for receiving a first domain name query request message sent by User Equipment (UE);

the determining module is configured to determine, according to the first domain name query request packet received by the receiving module, whether the domain name queried by the UE is a domain name of a private network;

the acquiring module is configured to acquire addresses and port numbers of M domain name system servers included in a target private network, where M is an integer greater than 1, when the determining module determines that the domain name queried by the UE is a domain name of the target private network;

the rewriting module is configured to rewrite the destination address and the port number of the first domain name query request packet, and obtain M second domain name query request packets for the addresses and the port numbers of the M domain name system servers acquired by the acquiring module;

the sending module is configured to send the M second domain name query request messages rewritten by the rewriting module to the M domain name system servers respectively.

8. A user plane function network element comprising a processor, a memory and a program or instruction stored on the memory and executable on the processor, which when executed by the processor implements the steps of the method of splitting a domain name query request according to any of claims 1 to 6.

9. A readable storage medium having stored thereon a program or instructions which when executed by a processor performs the steps of the method of splitting a domain name query request according to any of claims 1 to 6.

10. A computer program product comprising instructions which, when run on a computer, cause the computer to perform the steps of the splitting method of domain name query requests of any of claims 1 to 6.