Method for sending dns message, terminal and network side device

Abstract

The application discloses a DNS message sending method, a terminal and a network side device, and belongs to the technical field of wireless communication. The DNS message sending method of the application comprises the following steps: a terminal acquires a message to be sent; in the case that it is determined that the message to be sent is a DNS query, the message to be sent is sent to a target DNS server specified by an operator.

Description

TECHNICAL FIELD

[0001] The present application belongs to the technical field of wireless communication, and particularly relates to a DNS message sending method, a terminal and a network side device. BACKGROUND

[0002] An edge application server discovery function (EASDF) is a core network element for processing a domain name system (DNS) query request sent by a terminal. In the related art, the EASDF is a network element controlled by an operator and used for finding an edge server. The terminal cannot obtain address information of the network element, and thus cannot guarantee that a DNS request sent by the terminal can be sent to the network element, thereby causing the terminal to fail to effectively use a service of finding an edge server provided by the operator. SUMMARY

[0003] Embodiments of the present application provide a DNS message sending method, a terminal and a network side device, and can solve the problem that a terminal cannot guarantee that a DNS request sent by the terminal can be sent to a network element specified by an operator.

[0004] In a first aspect, a DNS message sending method is provided, including: a terminal obtaining a message to be sent; in a case where it is determined that the message to be sent is a DNS query, sending the message to be sent to a target DNS server specified by an operator.

[0005] In a second aspect, a DNS message sending apparatus is provided, including: a first obtaining module configured to obtain a message to be sent; and a first transceiving module configured to, in a case where it is determined that the message to be sent is a DNS query, send the message to be sent to a target DNS server specified by an operator.

[0006] In a third aspect, a DNS server configuration method is provided, including: a network side device receiving indication information sent by a terminal, wherein the indication information indicates that the terminal has a target capability; the network side device obtaining address information of a target DNS server specified by an operator; and the network side device sending the address information of the target DNS server to the terminal.

[0007] In a fourth aspect, a DNS server configuration apparatus is provided, including: a second transceiving module configured to receive indication information sent by a terminal, wherein the indication information indicates that the terminal has a target capability; a second obtaining module configured to obtain address information of a target DNS server specified by an operator; and the second transceiving module is further configured to send the address information of the target DNS server to the terminal.

[0008] In a fifth aspect, a terminal is provided, which comprises a processor, a memory, and a program or instructions stored in the memory and executable on the processor, and the program or instructions, when executed by the processor, implement the steps of the method according to the first aspect.

[0009] In a sixth aspect, a terminal is provided, which comprises a processor and a communication interface, wherein the processor is configured to implement the steps of the method according to the first aspect, and the communication interface is configured to communicate with a network-side device.

[0010] In a seventh aspect, a network-side device is provided, which comprises a processor, a memory, and a program or instructions stored in the memory and executable on the processor, and the program or instructions, when executed by the processor, implement the steps of the method according to the third aspect.

[0011] In an eighth aspect, a network-side device is provided, which comprises a processor and a communication interface, wherein the processor is configured to implement the steps of the method according to the third aspect, and the communication interface is configured to communicate with a terminal.

[0012] In a ninth aspect, a readable storage medium is provided, which stores a program or instructions, and the program or instructions, when executed by a processor, implement the steps of the method according to the first aspect or the steps of the method according to the third aspect.

[0013] In a tenth aspect, a chip is provided, which comprises a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to run a program or instructions to implement the steps of the method according to the first aspect or the steps of the method according to the third aspect.

[0014] In an eleventh aspect, a computer program / program product is provided, which is stored in a non-transitory storage medium, and the program / program product is executed by at least one processor to implement the steps of the method according to the first aspect or the steps of the method according to the third aspect.

[0015] In the embodiments of the present application, the terminal acquires a message to be sent, and in a case where the message to be sent is a DNS query message or a DNS request message, the terminal sends the message to be sent to a target DNS server specified by an operator, so that the DNS query message or the DNS request message of the terminal can be sent to the target DNS server specified by the operator, and the services provided by the target DNS server specified by the operator can be fully utilized. BRIEF DESCRIPTION OF DRAWINGS

[0016] Figure 1Fig. 1 shows a schematic diagram of a wireless communication system to which embodiments of the present application can be applied;

[0017] Figure 2 Fig. 4 shows a schematic diagram of a method for sending a DNS message according to an embodiment of the present application;

[0018] Figure 3 Fig. 5 shows a schematic diagram of a method for configuring a DNS server according to an embodiment of the present application;

[0019] Figure 4 Fig. 6 shows a schematic diagram of a sending device for a DNS message according to an embodiment of the present application;

[0020] Figure 5 Fig. 7 shows a schematic diagram of a configuration device for a DNS server according to an embodiment of the present application;

[0021] Figure 6 Fig. 8 shows a schematic diagram of a communication device according to an embodiment of the present application;

[0022] Figure 7 Fig. 9 shows a schematic diagram of a terminal according to an embodiment of the present application;

[0023] Figure 8 Fig. 10 shows a schematic diagram of a network-side device according to an embodiment of the present application. DETAILED DESCRIPTION

[0024] The technical solutions in the embodiments of the present application will be clearly described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, but not all of them. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art belong to the scope of protection of the present application.

[0025] The terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way can be interchanged under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than that illustrated or described herein, and the objects distinguished by "first", "second" are generally of a kind, and are not limited to the number of objects, for example, the first object can be one or more. In addition, "and / or" in the specification and claims means at least one of the connected objects, and the character " / " generally represents an "or" relationship between the objects before and after it.

[0026] It is worth noting that the technology described in the embodiments of the present application is not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA) and other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described technology can be used in the above-mentioned systems and radio technologies, as well as in other systems and radio technologies. The following description describes a New Radio (NR) system for example purposes, and NR terminology is used in most of the following description, but these technologies can also be applied outside the NR system application, such as in a 6th Generation (6G) communication system. th

[0027] Figure 1 ​A schematic diagram of a wireless communication system to which embodiments of the present application can be applied is shown. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can also be referred to as a terminal device or a user terminal (UE). The terminal 11 can be a terminal-side device such as a mobile phone, a tablet personal computer (PC), a laptop PC, a personal digital assistant (PDA), a palm PC, a netbook, an ultra-mobile personal computer (UMPC), a mobile Internet device (MID), a wearable device, or a vehicle UE (VUE). The wearable device includes a smart watch, a bracelet, a headset, glasses, and the like. It should be noted that the specific type of the terminal 11 is not limited in the embodiments of the present application. The network-side device 12 can be a base station or a core network. The base station can be referred to as a node B, an evolved node B, an access point, a base transceiver station (BTS), a radio base station, a radio transceiver, a basic service set (BSS), an extended service set (ESS), a node B, an evolved node B (eNB), a home node B, a home evolved node B, a WLAN access point, a WiFi node, a transmitting receiving point (TRP), or some other appropriate terminology in the art, as long as the same technical effects are achieved. The base station is not limited to a specific technical term, and it should be noted that only a base station in an NR system is taken as an example in the embodiments of the present application, but the specific type of the base station is not limited.

[0028] The DNS message sending scheme provided by the embodiments of the present application will be described in detail in combination with the accompanying drawings and some embodiments and application scenarios.

[0029] Figure 2 A flowchart of a DNS message sending method in the embodiments of the present application is shown. The method 200 can be performed by a terminal. In other words, the method can be performed by software or hardware installed on the terminal. As shown in the method can include the following steps. Figure 2

[0030] S210, the terminal acquires a message to be sent.

[0031] ​In the embodiments of the present application, the to-be-sent message can be a to-be-sent message sent by the terminal through an application (APP) on an application layer.

[0032] S212, in a case where it is determined that the to-be-sent message is a DNS query, sending the to-be-sent message to a target DNS server specified by an operator.

[0033] In the embodiments of the present application, in a case where it is determined that the to-be-sent message is a DNS query (which can also be referred to as a DNS request, or a DNS query request), the to-be-sent message is sent to a target DNS server specified by an operator, so that the DNS query message or the DNS request message of the terminal can be sent to the target DNS server specified by the operator, for example, EASDF, so that the services provided by the target DNS server specified by the operator can be fully utilized.

[0034] In one possible implementation, the to-be-sent message can carry a fully qualified domain name (FQDN), in which case the terminal can generate a DNS query containing the fully qualified domain name, and send the generated DNS query to the target DNS server specified by the operator.

[0035] In the embodiments of the present application, the operator refers to an operator that provides services for the terminal. For example, an operator that provides a SIM card for the terminal.

[0036] In one possible implementation of the embodiments of the present application, before S210, the method can further include: receiving address information of the target DNS server from a network side device. In the embodiments of the present application, the address information of the target DNS server can be sent by the network side device to the terminal. For example, the operator can send the IP address of the DNS server specified by the operator to the terminal through the network side device (such as SMF, session management function).

[0037] In one possible implementation, the terminal can receive the address information of the target DNS server from the network side device through PCO in a NAS message.

[0038] Optionally, after receiving the address information of the target DNS server specified by the network side device, the terminal can set the address information of the target DNS server as the DNS server address with the highest priority on the operating system of the terminal, so that the DNS query message or the DNS request message can be sent to the target DNS server.

[0039] In the optional implementation manner, setting the address information of the target DNS server as the DNS server address with the highest priority on the operating system (OS) of the terminal means that the DNS query message or the DNS request message sent by all APPs on the terminal is sent to the target DNS server. Alternatively, when the DNS query message or the DNS request message sent by all APPs on the terminal is sent by the PDUsession (i.e., the PDU session used by the address information of the target DNS server), the target DNS server is the highest priority, or the DNS query message or the DNS request message sent by all APPs on the terminal is sent to the target DNS server. Wherein, the target DNS server is the highest priority compared with other DNS configurations sent by the network side device, or the configuration saved in the terminal OS, or the DNS configuration specified by the user.

[0040] In one possible implementation manner, after receiving the address information of the target DNS server from the network side device through the PDU session, the terminal can bind the address information of the target DNS server to the PDU session, so that the DNS request message or the DNS query message sent on the PDU session can be sent to the target DNS server.

[0041] In one possible implementation manner, in S210, the terminal can obtain the to-be-sent message from the first application, determine that the to-be-sent message is sent on the PDU session, and then in S212, in a case where the to-be-sent message is a DNS query message or a DNS request message, the terminal can use the address information of the target DNS server as the destination address of the to-be-sent message, and send the to-be-sent message; and / or the terminal uses the address information of the target DNS server for DNS query and / or resolution.

[0042] In one possible implementation manner, after receiving the address information of the specified target DNS server from the network side device, the method further includes: forwarding the address information of the target DNS server to a second application on the application layer. Through this possible implementation manner, when the second application sends a DNS query message or a DNS request message, the address of the target DNS server is used as the destination IP, so that the DNS query message or the DNS request message is sent to the target DNS server.

[0043] In a possible implementation, in order to guarantee that the service of the target DNS server is not illegally used, the second application can be an application with a target permission, where the target permission is a permission of being able to receive address information of a DNS server specified by an operator. That is, in the possible implementation, the address information of the target DNS server can be sent only to an application with the permission of receiving the address information of the DNS server specified by the operator.

[0044] In a specific application, the second application can obtain the target permission by signing a contract with the operator, or the second application can also be an application specified by the operator.

[0045] In a possible implementation, the terminal can obtain identification information of the application with the target permission from the network-side device, and then send the target DNS server to the second application with the target permission in the terminal after receiving the address information of the target DNS server specified by the network-side device. The identification information of the application includes at least one of an application (application) ID, an application descriptor (which can include an OS ID, an OS app ID, and the like), and the like. The application descriptor is used to identify an application on a UE OS. The application ID is used to identify an application.

[0046] In a possible implementation of an embodiment of the present application, the network-side device can send the address information of the target DNS server to the terminal only when the terminal has the target capability. In order to enable the network-side device to know whether the terminal has the target capability, in the possible implementation, before receiving the address information of the target DNS server specified by the network-side device, the method further includes: the terminal sending indication information to the network-side device, where the indication information indicates that the terminal has the target capability.

[0047] Optionally, the target capability includes, but is not limited to, at least one of the following:

[0048] (1) The terminal deploys a first function entity, where the first function entity is capable of sending a DNS query request to a DNS server specified by an operator; for example, the terminal is configured with an edge DNS client (EDC) or an edge DNS function, and the EDC or the edge DNS function is capable of sending a DNS query to a target DNS server specified by an operator.

[0049] (2) The terminal supports obtaining address information of a DNS server specified by a network-side device from the network-side device.

[0050] (3) The terminal supports obtaining the address information of the operator-specified DNS server from the network-side device through the PDU session, and configuring the obtained address information of the DNS server to the PDU session, that is, binding the obtained address information of the DNS server to the PDU session.

[0051] (4) The terminal supports that the DNS configuration specified by the operator will not be modified after being obtained. For example, the DNS configuration will not be manually modified by the user, or will not be modified by the APP on the terminal, or the DNS configuration will not be downgraded in priority (resulting in that the DNS configuration of the operator is not used) because the user configures a private DNS configuration.

[0052] (5) The terminal supports forwarding the DNS configuration specified by the operator to an application with a target permission, wherein the target permission is a permission capable of receiving the address information of the DNS server specified by the operator. In this possible implementation manner, the terminal can instruct the network-side device about the application currently deployed on the terminal (for example, the terminal reports the list of the APPs currently on the terminal through a NAS message) so as to let the network-side device determine which application has the target permission and instruct the terminal.

[0053] (6) The terminal supports forwarding the DNS response received from the DNS server specified by the operator to an application. For example, the DNS response is forwarded to the application that sends the DNS query message or the DNS request message.

[0054] In one possible implementation manner, after the to-be-sent message is sent to the target DNS server specified by the operator, the method further can include: receiving the DNS response returned by the target DNS server, wherein the DNS response carries the address information of a target server (for example, an edge application server (EAS)) that is the server closest to the terminal in topology distance obtained by the DNS server specified by the operator for resolving the to-be-sent message.

[0055] For example, the terminal sends the DNS query message to the target DNS server (for example, an EASDF), and then the EASDF obtains the IP address of a server closest to the terminal in topology distance according to the information such as the Fully Qualified Domain Name (FQDN) of the DNS query message, and returns the IP address of the server to the terminal through the DNS response.

[0056] In the possible implementation manner, in a case where the to-be-sent message is a message sent by a first application, after receiving the DNS response returned by the target DNS server, the method further includes: forwarding the DNS response to the first application on an application layer, where the first application is an application that sends the to-be-sent message.

[0057] In the embodiments of the present application, a new terminal capability is proposed. For a terminal with the terminal capability, at least one of the following operations can be performed:

[0058] (1) Using the function, the terminal can send a DNS query request to an operator-specified DNS server (such as EASDF), and the DNS server can respond to a server IP address (obtained after the DNS server resolves the FQDN in the DNS query) closest to the UE terminal topology for the DNS query;

[0059] (2) The terminal can indicate the terminal capability to the network side through a NAS message; after obtaining the capability indication, the network side can distribute an operator-specified DNS server IP address with an edge server discovery function to the terminal through a PDU session. After receiving the DNS server address, the terminal can set the server IP address as the highest priority, use it for the PDU session, and resolve the DNS query sent by the application.

[0060] For a terminal without the terminal capability, it can not receive the operator-specified DNS server IP address with the edge server discovery function from the 5G core network; or discard the address after receiving the address; or the terminal cannot use the DNS address as the DNS server address with the highest priority; or the terminal cannot send the DNS address to the application on the application layer, or cannot ensure that the DNS query sent in the PDU session is sent to the operator-specified DNS server.

[0061] In the embodiments of the present application, the terminal with the terminal capability receives the DNS server IP address sent by the operator from the network side (through a certain PDU session), and at least one of the following operations is performed:

[0062] (1) The DNS server address is set as the DNS server address with the highest priority on the UE OS; all DNS queries on the UE use the DNS server for query and / or resolution;

[0063] (2) The DNS server is bound to the PDU session; all DNS queries (from the application layer) in the PDU session use the DNS server address for DNS query / resolution;

[0064] (3) All DNS queries (from application layer) within the PDU session are sent to the DNS server address (e.g. EAS DF IP address);

[0065] (4) When an application on the UE invokes an API of the first function, or when the application on the UE does not explicitly indicate not to use the service provided by the first function, the UE will send the DNS query to the DNS server designated by the operator for the DNS query sent by the application;

[0066] (5) The UE OS can forward the DNS server IP address to the application on the application layer.

[0067] In an embodiment, the first function can be an EDC (EDC: edge DNS client, or edge discovery client), or a client supported by the UE, which can send the DNS query on the UE to the DNS server designated by the operator, or which can send the DNS server IP address issued by the operator to the application layer.

[0068] Through the technical solutions provided by the embodiments of the present application, it is ensured that the application on the terminal can use the edge computing service of the operator (i.e. providing an EAS closest to the terminal in topology or routing for the application on the terminal), and it is also ensured that the DNS query sent by the application on the terminal is sent to the DNS server of the operator.

[0069] Corresponding to the DNS message sending method described above, the embodiments of the present application also provide a DNS server configuration method.

[0070] Figure 3 A flowchart of the DNS server configuration method provided by the embodiments of the present application is shown, and the method 300 can be executed by a network side device. In other words, the method can be executed by software or hardware installed on the network side device. As shown in the figure, the method can include the following steps. Figure 3

[0071] S310, the network side device receives the indication information sent by the terminal, wherein the indication information indicates that the terminal has a target capability.

[0072] In the embodiments of the present application, the network side device can include a session management function entity (SMF) or an access and mobility management function entity (AMF).

[0073] ​For example, the terminal can send the indication information to the network side device through a NAS message.

[0074] The NAS message includes, but is not limited to, at least one of the following:

[0075] (1) PDU Session Establishment Request;

[0076] (2) PDU Session Modification Request.

[0077] In one possible implementation, similar to the method 200, the target capability includes, but is not limited to, at least one of the following:

[0078] (1) The terminal is deployed with a first function entity, wherein the first function entity is capable of sending a DNS query request to an operator-specified DNS server; for example, the terminal is configured with an Edge DNS client (EDC) or an Edge DNS function, and the EDC or the Edge DNS function is capable of sending a DNS query to an operator-specified target DNS server.

[0079] (2) The terminal supports obtaining address information of an operator-specified DNS server from the network side device.

[0080] (3) The terminal supports obtaining address information of an operator-specified DNS server from the network side device through a PDU session, and configuring the obtained address information of the DNS server to the PDU session, i.e., binding the obtained address information of the DNS server to the PDU session.

[0081] (4) The terminal supports that, after obtaining an operator-specified DNS configuration, the DNS configuration will not be modified. For example, the DNS configuration will not be manually modified by a user, or will not be modified by an APP on the terminal, or the DNS configuration will not be lowered in priority (resulting in that the operator's configuration is not used) because a user configures a private DNS configuration.

[0082] (5) The terminal supports forwarding an operator-specified DNS configuration to an application with a target permission, wherein the target permission is a permission capable of receiving address information of an operator-specified DNS server. In this possible implementation, the terminal can indicate to the network side device an application currently deployed on the terminal (for example, the terminal reports a list of APPs currently on the terminal through a NAS message), so as to let the network side device determine which application has the target permission and indicate to the terminal.

[0083] (6) The terminal supports forwarding the DNS response received from the DNS server designated by the operator to an application. For example, the DNS response is forwarded to the application that sent the DNS query message or the DNS request message.

[0084] S312, the network-side device acquires address information of a target DNS server designated by an operator.

[0085] In one possible implementation, the network-side device can acquire the address information of the target DNS server based on subscription information of the terminal, location information of the terminal, and a user plane PDU session anchor (PSA) to which the terminal is anchored. For example, after receiving the capability indication information of the terminal, the SMF can send an Nnrf_NFDiscoveryrequest to a network repository function (NRF) network element to find a target DNS server, such as an EASDF.

[0086] S314, the network-side device sends the address information of the target DNS server to the terminal.

[0087] In S314, the network-side device can also send application identification information having the permission to receive the address information of the target DNS server to the terminal.

[0088] For example, the network-side device can send the address information of the target DNS server to the terminal through protocol configuration options (PCO).

[0089] In one possible implementation, after receiving the indication information of the terminal, the network-side device can determine the application identification information having the permission to receive the address information of the target DNS server, and the determination can be made through one of the following:

[0090] 1. The network-side device (for example, an AMF or an SMF) sends an Nudm_SDM_Getrequest or an Nudm_SDM_Subscriberequest to a unified data management (UDM) entity to request to obtain subscription information in the UDM, and the UDM feeds back to the AMF or the SMF: APP identification information that is subscribed by the operator;

[0091] 2. The SMF or UDM sends Nudr_DM_Query request or Nudr_DM_Subscribe request to the Unified Data Repository (UDR) to request the subscription information in the UDR, and the UDR feeds back to the SMF or UDM: the APP identification information of the operator's subscription; if the UDM requests the UDR, the SMF can request the UDM to obtain the APP identification information of the operator's subscription from the UDR.

[0092] After receiving the APP identification information of the operator's subscription fed back by the UDM or UDR, the SMF sends the receivable APP identification information to the terminal. For example, the terminal is sent through the NAS message.

[0093] Alternatively, the network side device can also receive the first indication information sent by the terminal, wherein the first indication information indicates the application on the terminal, and then determine the application on the terminal which can obtain the address information of the target DNS server according to the first indication information. Then the network side device sends the application identification of the determined application to the terminal.

[0094] The APP identification information of the operator's subscription can be saved in the UDR. One possible case is: dataset = Application data, Data Subset = subscriptionapplicationID, Data Key = SUPI, GPSI, Internal Group Identifier, External Group Identifier or applicationID, etc. at least one or more.

[0095] Alternatively, the APP identification information of the operator's subscription can also be saved in the UDM. In the UDM, the data saving mode can be: in the Subscription data type = Session Management Subscription data, Data Subset = subscriptionapplicationID, Data Key = SUPI, GPSI, Internal Group Identifier, External Group Identifier or applicationID, etc. at least one or more.

[0096] In a possible implementation, after the network-side device acquires the address information of the target DNS server specified by the operator, the method further includes at least one of the following:

[0097] (1) The network-side device indicates a function identifier to the terminal, where the function identifier is used to indicate that the address information of the target DNS server will be sent to a function entity corresponding to the function identifier after the address information is received by an operating system or a chip.

[0098] (2) The network-side device indicates an application identifier to the terminal, where the application identifier is used to indicate an application that can obtain the address information of the target DNS server. The application identifier can be the APP application identifier information acquired from the UDM or the UDR, or can be an application identifier of an application that can obtain the address information of the target DNS server in a current application of the terminal.

[0099] In the possible implementation, the network-side device can indicate the function identifier and / or the application identifier at the same time when the address information of the target DNS server is sent to the terminal, or can indicate the function identifier and / or the application identifier before or after the address information of the target DNS server is sent, which is not limited in the embodiments of the present application.

[0100] In the embodiments of the present application, the network-side device, when knowing that the terminal has the target capability, provides the address information of a DNS server closest to the terminal in topology or routing to the application on the terminal, so that the terminal can use the DNS server to perform DNS query and / or resolution, to fully utilize the edge computing service provided by the operator.

[0101] It should be noted that the DNS message sending method provided in the embodiments of the present application can be executed by a DNS message sending device, or a control module in the DNS message sending device for executing the DNS message sending method. In the embodiments of the present application, the DNS message sending device executes the DNS message sending method, and the DNS message sending device provided in the embodiments of the present application is described.

[0102] Figure 4 A structure schematic diagram of the DNS message sending device provided in the present application is shown, as shown in the figure, the device mainly includes: a first acquisition module 401, configured to acquire a message to be sent; and a first transceiver module 402, configured to send the message to be sent to a target DNS server specified by an operator in a case where it is determined that the message to be sent is a DNS query. Figure 4

[0103] ​In a possible implementation, the first transceiving module 402 is further configured to receive the address information of the specified target DNS server from the network-side device before obtaining the message to be sent.

[0104] In a possible implementation, the apparatus can further include a first setting module 403 configured to set the address information of the target DNS server as the DNS server address with the highest priority on the operating system of the terminal.

[0105] In a possible implementation, the first transceiving module 402 receives the address information of the specified target DNS server from the network-side device, including:

[0106] The address information of the specified target DNS server is received from the network-side device through a PDU session.

[0107] In a possible implementation, the apparatus further includes a second setting module 404 configured to bind the address information of the target DNS server to the PDU session.

[0108] In a possible implementation, the first obtaining module 401 obtains the message to be sent, including: obtaining the message to be sent from a first application, and determining that the message to be sent is sent on the PDU session.

[0109] The first transceiving module 402 sends the message to be sent to the target DNS server specified by the operator, including at least one of the following:

[0110] The address information of the target DNS server is used as the destination address of the message to be sent, and the message to be sent is sent.

[0111] The address information of the target DNS server is used for DNS query and / or resolution.

[0112] In a possible implementation, the first transceiving module 402 is further configured to forward the address information of the target DNS server to a second application on the application layer.

[0113] In a possible implementation, the second application is an application with a target permission, where the target permission is a permission capable of receiving the address information of the DNS server specified by the operator.

[0114] In a possible implementation, the first obtaining module 401 is further configured to obtain identification information of the application with the target permission from the network-side device before obtaining the message to be sent.

[0115] In a possible implementation, the first transceiving module 402 is further configured to send indication information to the network-side device before receiving the address information of the designated target DNS server from the network-side device, where the indication information indicates that the terminal has the target capability.

[0116] In a possible implementation, the target capability includes at least one of the following:

[0117] The terminal is deployed with a first function entity, where the first function entity is capable of sending a DNS query request to an operator-designated DNS server.

[0118] The terminal supports obtaining address information of an operator-designated DNS server from a network-side device.

[0119] The terminal supports obtaining address information of an operator-designated DNS server from a network-side device through a PDU session, and configuring the obtained address information of the DNS server to the PDU session.

[0120] The terminal supports that, after obtaining an operator-designated DNS configuration, the DNS configuration is not modified.

[0121] The terminal supports forwarding an operator-designated DNS configuration to an application having a target permission, where the target permission is a permission of being capable of receiving address information of an operator-designated DNS server.

[0122] The terminal supports forwarding a DNS response received from an operator-designated DNS server to an application.

[0123] In a possible implementation, the first transceiving module 402 is further configured to, after sending the to-be-sent message to the operator-designated target DNS server, receive a DNS response returned by the target DNS server, where the DNS response carries address information of a target server, and the target server is a server closest to the terminal in a topology after resolving the to-be-sent message.

[0124] In a possible implementation, the first transceiving module 402 is further configured to, after receiving the DNS response returned by the target DNS server, forward the DNS response to a first application on an application layer, where the first application is an application of sending the to-be-sent message.

[0125] The DNS message sending device in the embodiments of the present application can be a device, or a component, an integrated circuit, or a chip in a terminal. The device can be a mobile terminal or a non-mobile terminal. Exemplarily, the mobile terminal can include, but is not limited to, the types of the terminal 11 listed above, and the non-mobile terminal can be a server, a network attached storage (NAS), a personal computer (PC), a television (TV), a teller machine, or a self-service machine, and the like, which are not limited in the embodiments of the present application.

[0126] The DNS message sending device in the embodiments of the present application can be a device with an operating system. The operating system can be an Android operating system, an ios operating system, or other possible operating systems, which are not limited in the embodiments of the present application.

[0127] The DNS message sending device provided in the embodiments of the present application can implement each process of the method embodiment implemented by the terminal and achieve the same technical effects. To avoid repetition, details are not described herein. Figures 2-3

[0128] It should be noted that the DNS server configuration method provided in the embodiments of the present application can be executed by a DNS server configuration device, or a control module in the DNS server configuration device for executing the DNS server configuration method. In the embodiments of the present application, the DNS server configuration method is executed by the DNS server configuration device, which is used to illustrate the DNS server configuration device provided in the embodiments of the present application.

[0129] Figure 5 A structure schematic diagram of the DNS server configuration device provided in the embodiments of the present application is shown in FIG. 5, which mainly includes a second transceiver module 501 and a second acquisition module 502. Figure 5

[0130] In the embodiments of the present application, the second transceiver module 501 is configured to receive indication information sent by a terminal, where the indication information indicates that the terminal has a target capability; the second acquisition module 502 is configured to acquire address information of a target DNS server specified by an operator; and the second transceiver module 501 is further configured to send the address information of the target DNS server to the terminal.

[0131] ​​In a possible implementation, the second obtaining module 502 obtains address information of a target DNS server designated by an operator, including: obtaining the address information of the target DNS server based on subscription information of the terminal, location information of the terminal, and a user plane PSA to which the terminal is anchored.

[0132] In a possible implementation, the second transceiving module 501 sends the address information of the target DNS server to the terminal, including: sending the address information of the target DNS server to the terminal through PCO.

[0133] In a possible implementation, the second transceiving module 501 is further configured to perform one of the following:

[0134] indicate a function identifier to the terminal, where the function identifier is used to indicate that the address information of the target DNS server will be sent to a function entity corresponding to the function identifier when an operating system or a chip receives the address information of the target DNS server;

[0135] indicate an application identifier to the terminal, where the application identifier is used to indicate an application that can obtain the address information of the target DNS server.

[0136] In a possible implementation, the second obtaining module 502 is further configured to perform one of the following:

[0137] receive first indication information sent by the terminal, where the first indication information indicates an application on the terminal; and determine, according to the first indication information, an application on the terminal that can obtain the address information of the target DNS server from the applications on the terminal;

[0138] obtain an application identifier of an operator from a unified data management entity (UDM) or a unified data repository (UDR).

[0139] In a possible implementation, the target capability includes at least one of the following:

[0140] the terminal deploys a first function entity, where the first function entity can send a DNS query request to a DNS server designated by an operator;

[0141] the terminal supports obtaining address information of a DNS server designated by an operator from a network side device;

[0142] the terminal supports obtaining address information of a DNS server designated by an operator from a network side device through a PDU session, and configuring the obtained address information of the DNS server to the PDU session;

[0143] The terminal supports that the DNS configuration made by the operator is not modified after being acquired;

[0144] The terminal supports forwarding the DNS configuration made by the operator to an application with a target permission, wherein the target permission is a permission of being able to receive address information of the DNS server specified by the operator.

[0145] The terminal supports forwarding the DNS response received from the DNS server specified by the operator to the application.

[0146] The DNS server configuration apparatus in the embodiment of the present application can be an apparatus, or a component, an integrated circuit, or a chip in a network side device.

[0147] The DNS server configuration apparatus in the embodiment of the present application can be an apparatus with an operating system. The operating system can be an Android operating system, an ios operating system, or other possible operating systems, which are not limited in the embodiment of the present application.

[0148] The DNS server configuration apparatus provided in the embodiment of the present application can implement each process of the method embodiment of Figures 2-3 The network side device, and achieve the same technical effects. To avoid repetition, details are not described herein.

[0149] Optionally, as shown in Figure 6 The present application also provides a communication device 600, which includes a processor 601, a memory 602, and a program or instruction stored in the memory 602 and executable on the processor 601. When the communication device 600 is a terminal, the program or instruction is executed by the processor 601 to implement each process of the above-mentioned DNS message sending method embodiment, and achieve the same technical effects. When the communication device 600 is a network side device, the program or instruction is executed by the processor 601 to implement each process of the above-mentioned DNS server configuration method embodiment, and achieve the same technical effects. To avoid repetition, details are not described herein.

[0150] The present application also provides a terminal, which includes a processor and a communication interface. The processor is configured to implement each process of the above-mentioned DNS message sending method embodiment. The communication interface is configured to communicate with a network side device. The terminal embodiment corresponds to the above-mentioned terminal side method embodiment. Each implementation process and implementation manner of the above-mentioned method embodiment can be applied to the terminal embodiment, and achieve the same technical effects. Specifically, Figure 7 A hardware structure diagram of a terminal for implementing the embodiment of the present application.

[0151] The terminal 700 includes, but is not limited to, a radio frequency unit 701, a network module 702, an audio output unit 703, an input unit 704, a sensor 705, a display unit 706, a user input unit 707, an interface unit 708, a memory 709, and a processor 710, etc.

[0152] Those skilled in the art can understand that the terminal 700 can further include a power supply (such as a battery) for supplying power to each component, and the power supply can be logically connected to the processor 710 through a power management system, so as to realize functions such as management of charging, discharging, and power consumption management through the power management system. Figure 7 The terminal structure shown in the figure is not a limitation on the terminal, and the terminal can include more or less components than the figure, or combine certain components, or different component arrangements, which are not described here.

[0153] It should be understood that in the embodiments of the present application, the input unit 704 can include a graphics processor (GPU) 7041 and a microphone 7042, and the graphics processor 7041 processes image data of a still picture or a video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 706 can include a display panel 7061, which can be configured in the form of a liquid crystal display, an organic light-emitting diode, etc. The user input unit 707 includes a touch panel 7071 and other input devices 7072. The touch panel 7071 is also called a touch screen. The touch panel 7071 can include two parts of a touch detection device and a touch controller. The other input devices 7072 can include, but are not limited to, a physical keyboard, function keys (such as volume control keys, on-off keys, etc.), trackballs, mice, joysticks, etc., which are not described here.

[0154] In the embodiments of the present application, the radio frequency unit 701 receives downlink data from a network side device and processes the data by the processor 710; in addition, it sends uplink data to the network side device. Generally, the radio frequency unit 701 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.

[0155] The memory 709 can be used to store software programs or instructions and various data. The memory 709 can mainly include a storage program or instruction area and a storage data area, wherein the storage program or instruction area can store an operating system, application programs or instructions required by at least one function (such as a sound playing function, an image playing function, etc.), etc. In addition, the memory 709 can include a high-speed random access memory, and can also include a non-transitory memory, which can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. For example, at least one magnetic disk storage device, a flash memory device, or other non-transitory solid-state memory device.

[0156] The processor 710 can include one or more processing units; optionally, the processor 710 can integrate an application processor and a modem processor, wherein the application processor mainly processes an operating system, a user interface, and application programs or instructions, etc., and the modem processor mainly processes wireless communication, such as a baseband processor. It can be understood that the above-mentioned modem processor can also not be integrated into the processor 710.

[0157] The processor 710 is configured to acquire a message to be sent by the terminal.

[0158] The radio frequency unit 701 is configured to, in a case where it is determined that the message to be sent is a domain name system (DNS) query, send the message to be sent to a target DNS server specified by an operator.

[0159] In the embodiments of the present application, the terminal acquires a message to be sent, and in a case where it is determined that the message to be sent is a DNS query message or a DNS request message, the terminal sends the message to be sent to a target DNS server specified by an operator, so that the DNS query message or the DNS request message of the terminal can be ensured to be sent to the target DNS server specified by the operator, and the services provided by the target DNS server specified by the operator can be fully utilized

[0160] Optionally, the radio frequency unit 701 is further configured to, before the terminal acquires the message to be sent, receive address information of the target DNS server from a network side device.

[0161] Optionally, the processor 710 is further configured to set the address information of the target DNS server as a DNS server address with the highest priority on an operating system of the terminal.

[0162] Optionally, the radio frequency unit 701 receives the address information of the target DNS server from the network side device through a protocol data unit (PDU) session.

[0163] Optionally, the processor 710 is further configured to bind the address information of the target DNS server to the PDU session.

[0164] Optionally, the processor 710 obtains the to-be-sent message from a first application, determines that the to-be-sent message is to be sent over the PDU session, and the radio frequency unit 701 sends the to-be-sent message using the address information of the target DNS server as a destination address of the to-be-sent message, and / or performs DNS query and / or resolution using the address information of the target DNS server.

[0165] Optionally, the radio frequency unit 701 is further configured to forward the address information of the target DNS server to a second application on an application layer.

[0166] Optionally, the second application is an application having a target permission, where the target permission is a permission to receive address information of an operator-specified DNS server.

[0167] Optionally, the radio frequency unit 701 is further configured to obtain, from a network side device, identification information of an application having the target permission.

[0168] Optionally, the radio frequency unit 701 is further configured to send, to the network side device, indication information indicating that the terminal has a target capability.

[0169] Optionally, the target capability includes at least one of the following:

[0170] The terminal deploys a first function entity, where the first function entity is capable of sending a DNS query request to an operator-specified DNS server.

[0171] The terminal supports obtaining, from a network side device, address information of an operator-specified DNS server.

[0172] The terminal supports obtaining, from a network side device, address information of an operator-specified DNS server through a PDU session, and configuring the obtained address information of the DNS server to the PDU session.

[0173] The terminal supports that, after obtaining an operator-specified DNS configuration, the DNS configuration is not modified.

[0174] The terminal supports forwarding, to an application having a target permission, an operator-specified DNS configuration, where the target permission is a permission to receive address information of an operator-specified DNS server.

[0175] The terminal forwards a DNS response received from an operator-specified DNS server to an application.

[0176] Optionally, the radio frequency unit 701 is further configured to receive a DNS response returned by the target DNS server after sending the message to be sent to the target DNS server, wherein the DNS response carries address information of a target server, and the target server is a server closest to the terminal in a topology distance obtained by resolving the message to be sent.

[0177] Optionally, the radio frequency unit 701 is further configured to forward the DNS response to a first application on an application layer after receiving the DNS response returned by the target DNS server, wherein the first application is an application that sends the message to be sent.

[0178] The embodiment of the application further provides a network side device, comprising a processor and a communication interface, the processor is configured to implement various processes of the DNS server configuration method embodiment, and the communication interface is configured to communicate with a terminal. The network side device embodiment corresponds to the network side device method embodiment, and each implementation process and implementation manner of the method embodiment can be applied to the network side device embodiment and achieve the same technical effects.

[0179] Specifically, the embodiment of the application further provides a network side device. As shown in the Figure 8 The network device 800 comprises an antenna 801, a radio frequency device 802, and a baseband device 803. The antenna 801 is connected to the radio frequency device 802. In the uplink direction, the radio frequency device 802 receives information through the antenna 801 and sends the received information to the baseband device 803 for processing. In the downlink direction, the baseband device 803 processes the information to be sent and sends it to the radio frequency device 802. The radio frequency device 802 processes the received information and sends it out through the antenna 801.

[0180] The above frequency band processing device can be located in the baseband device 803. The method executed by the network side device in the above embodiment can be implemented in the baseband device 803, which comprises a processor 804 and a memory 805.

[0181] The baseband device 803 may, for example, comprise at least one baseband board, which is provided with a plurality of chips, as shown in Figure 8 One of the chips is, for example, the processor 804, which is connected to the memory 805 to call the programs in the memory 805 and execute the network device operations shown in the above method embodiment.

[0182] The baseband device 803 can further include a network interface 806 for interacting with the radio frequency device 802, which is, for example, a common public radio interface (CPRI).

[0183] Specifically, the network side device of the embodiment of the present application further includes instructions or programs stored in the memory 805 and executable on the processor 804, and the processor 804 invokes the instructions or programs in the memory 805 to execute the method performed by each module shown in the above embodiments and achieve the same technical effects. To avoid repetition, the details are not described herein. Figure 5 The method performed by each module shown in the above embodiments and achieve the same technical effects. To avoid repetition, the details are not described herein.

[0184] The embodiment of the present application further provides a readable storage medium, and the readable storage medium stores programs or instructions, which are executed by a processor to implement each process of the above-mentioned DNS message sending method embodiment or implement each process of the above-mentioned DNS server configuration method embodiment, and achieve the same technical effects. To avoid repetition, the details are not described herein.

[0185] The processor is the processor in the terminal in the above-mentioned embodiments. The readable storage medium includes a computer readable storage medium, such as a computer readable only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0186] The embodiment of the present application further provides a chip, and the chip includes a processor and a communication interface. The communication interface is coupled with the processor, and the processor is used to run programs or instructions to implement each process of the above-mentioned DNS message sending method embodiment or implement each process of the above-mentioned DNS server configuration method embodiment, and achieve the same technical effects. To avoid repetition, the details are not described herein.

[0187] It should be understood that the chip mentioned in the embodiment of the present application can also be referred to as a system chip, a system chip, a chip system or a system on chip, etc.

[0188] The embodiment of the present application further provides a computer program / program product, which is stored in a non-transient storage medium. The program / program product is executed by at least one processor to implement each process of the above-mentioned DNS message sending method embodiment or implement each process of the above-mentioned DNS server configuration method embodiment, and achieve the same technical effects. To avoid repetition, the details are not described herein.

[0189] It should be noted that, in the present document, the terms "comprises", "comprising", or any other variations 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 can include other elements not expressly listed or inherent to such process, method, article, or apparatus. An element proceeded by "comprises... a" does not, without more constraints, exclude the presence of additional identical elements in the process, method, article, or apparatus that comprises the element. Furthermore, it is to be understood that the method and apparatus of the present application can be carried out by more than one process, method, article, or apparatus either simultaneously, concurrently, or with intervening action that are carried out at the same time, in any order, or in an overlapping manner. For example, the described method can be performed in a different order or simultaneously, and the various steps can be combined or omitted, or additional steps can be added, without departing from the scope of the described method. Also, features described with respect to certain examples can be combined in other examples.

[0190] From the above description of the embodiments, it is apparent that the method of the above-described embodiments can be realized by means of software and general-purpose hardware platforms. Of course, it can also be realized by hardware, but in many cases, the former is a better embodiment. Based on such an understanding, the technical solutions of the present application, essentially or in other words, the part that contributes to the prior art, can be embodied in the form of a computer software product, which is stored in a storage medium (such as a ROM / RAM, a magnetic disk, or an optical disk) and includes a number of instructions to make a terminal (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) execute the methods described in various embodiments of the present application.

[0191] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-described specific embodiments, which are merely illustrative rather than restrictive, and a person of ordinary skill in the art can make many forms under the inspiration of the present application without departing from the scope of the present application and the protection scope of the claims, which are all within the protection scope of the present application.

Claims

1. A method for sending DNS messages, characterized in that, include: The terminal obtains the message to be sent; If it is determined that the message to be sent is a Domain Name System (DNS) query, the message to be sent will be sent to the target DNS server specified by the operator. The method further includes, before the terminal acquires the message to be sent: The terminal sends an indication message to the network-side device, wherein the indication message indicates that the terminal possesses the target capability; Receive the address information of the target DNS server from the network-side device; The target capability includes at least one of the following: The terminal is equipped with a first functional entity, which is capable of sending DNS query requests to a DNS server designated by the operator. The terminal supports obtaining the address information of the DNS server specified by the operator from the network-side device; The terminal supports obtaining the address information of the DNS server specified by the operator from the network-side device through the PDU session, and configuring the obtained DNS server address information to the PDU session; The terminal supports obtaining the DNS configuration specified by the operator, and this DNS configuration will not be modified. The terminal supports forwarding the DNS configuration specified by the operator to applications with target permissions, wherein the target permissions are the permissions to receive the address information of the DNS server specified by the operator. The terminal supports forwarding DNS responses received from the DNS server specified by the operator to the application.

2. The method according to claim 1, characterized in that, After receiving the address information of the specified target DNS server from the network-side device, the method further includes: Set the address information of the target DNS server to the address of the highest priority DNS server on the terminal's operating system.

3. The method according to claim 1, characterized in that, Receiving the address information of the target DNS server from the network-side device includes: The terminal receives the address information of the target DNS server from the network-side device through a Protocol Data Unit (PDU) session.

4. The method according to claim 3, characterized in that, After receiving the address information of the target DNS server from the network-side device, the method further includes: Bind the address information of the target DNS server to the PDU session.

5. The method according to claim 4, characterized in that, The terminal obtains a message to be sent, including: obtaining the message to be sent from a first application and determining that the message to be sent will be sent on the PDU session; Sending the message to be sent to the target DNS server specified by the operator includes at least one of the following: The message to be sent is sent using the address information of the target DNS server as the destination address of the message to be sent. DNS queries and / or resolutions are performed using the address information of the target DNS server.

6. The method according to claim 1, characterized in that, After receiving the address information of the specified target DNS server from the network-side device, the method further includes: The address information of the target DNS server is forwarded to the second application at the application layer.

7. The method according to claim 6, characterized in that, The second application is an application with target permissions, wherein the target permissions are the permissions to receive address information of the DNS server specified by the operator.

8. The method according to claim 7, characterized in that, Before the terminal acquires the message to be sent, the method further includes: Obtain the identification information of the application with the target permissions from the network-side device.

9. The method according to any one of claims 1 to 8, characterized in that, After sending the message to be sent to the target DNS server specified by the operator, the method further includes: Receive a DNS response returned by the target DNS server, wherein the DNS response carries the address information of the target server, and the target server is the server whose topological distance to the terminal is closest as obtained by resolving the message to be sent.

10. The method according to claim 9, characterized in that, After receiving the DNS response returned by the target DNS server, the method further includes: The DNS response is forwarded to a first application at the application layer, wherein the first application is the application that sent the message to be sent.

11. A method for configuring a DNS server, characterized in that, include: The network-side device receives an indication message sent by the terminal, wherein the indication message indicates that the terminal possesses the target capability; The network-side device obtains the address information of the target DNS server specified by the operator; The network-side device sends the address information of the target DNS server to the terminal; The target capability includes at least one of the following: The terminal is equipped with a first functional entity, which is capable of sending DNS query requests to a DNS server designated by the operator. The terminal supports obtaining the address information of the DNS server specified by the operator from the network-side device; The terminal supports obtaining the address information of the DNS server specified by the operator from the network-side device through the PDU session, and configuring the obtained DNS server address information to the PDU session; The terminal supports obtaining the DNS configuration specified by the operator, and this DNS configuration will not be modified. The terminal supports forwarding the DNS configuration specified by the operator to applications with target permissions, wherein the target permissions are the permissions to receive the address information of the DNS server specified by the operator. The terminal supports forwarding DNS responses received from the DNS server specified by the operator to the application.

12. The method according to claim 11, characterized in that, The network-side device obtains the address information of the target DNS server specified by the operator, including: The network-side device obtains the address information of the target DNS server based on the terminal's subscription information, the terminal's location information, and the user plane PDU session anchor point (PSA) to which the terminal is anchored.

13. The method according to claim 11, characterized in that, The network-side device sends the address information of the target DNS server to the terminal, including: The network-side device sends the address information of the target DNS server to the terminal through the Protocol Configuration Option (PCO).

14. The method according to claim 13, characterized in that, After the network-side device obtains the address information of the target DNS server specified by the operator, the method further includes at least one of the following: The network-side device indicates a function identifier to the terminal, wherein the function identifier is used to indicate that when the operating system or chip receives the address information of the target DNS server, it will send the address information to the function entity corresponding to the function identifier; The network-side device indicates an application identifier to the terminal, wherein the application identifier is used to indicate an application that can obtain the address information of the target DNS server.

15. The method according to claim 14, characterized in that, Before the network-side device indicates the application identifier to the terminal, the method further includes one of the following: The network-side device receives first indication information sent by the terminal, wherein the first indication information indicates an application on the terminal; based on the first indication information, it determines an application on the terminal that can obtain the address information of the target DNS server; The network-side device obtains the application identifier signed with the operator from the Unified Data Management Entity (UDM) or the Unified Data Repository (UDR).

16. A DNS message sending apparatus, characterized in that, include: The first acquisition module is used to acquire messages to be sent. The first transceiver module is used to send the message to be sent to the target DNS server specified by the operator when it is determined that the message to be sent is a DNS query. The first transceiver module is further configured to send indication information to the network-side device before acquiring the message to be sent, wherein the indication information indicates that the device has the target capability; and to receive the address information of the specified target DNS server from the network-side device; The target capability includes at least one of the following: The device is equipped with a first functional entity, which is capable of sending DNS query requests to a DNS server specified by the operator. The device supports obtaining the address information of the DNS server specified by the operator from network-side devices; The device supports obtaining the address information of the DNS server specified by the operator from the network-side device through the PDU session, and configuring the obtained DNS server address information to the PDU session; The device supports ensuring that the DNS configuration specified by the operator is not modified after it is obtained; The device supports forwarding the DNS configuration specified by the operator to applications with target permissions, wherein the target permissions can be the permission to receive the address information of the DNS server specified by the operator. The device supports forwarding DNS responses received from a DNS server designated by the operator to the application.

17. The apparatus according to claim 16, characterized in that, The device further includes a first setting module, configured to set the address information of the target DNS server to the address of the highest priority DNS server on the operating system of the device.

18. The apparatus according to claim 17, characterized in that, The first transceiver module receives the address information of the specified target DNS server from the network-side device, including: The address information of the specified target DNS server is received from the network-side device through a PDU session.

19. The apparatus according to claim 18, characterized in that, Also includes: The second setting module is used to bind the address information of the target DNS server to the PDU session.

20. The apparatus according to claim 19, characterized in that, The first acquisition module acquires the message to be sent, including: acquiring the message to be sent from the first application, and determining that the message to be sent will be sent on the PDU session; The first transceiver module sends the message to be sent to the target DNS server specified by the operator, including at least one of the following: The message to be sent is sent using the address information of the target DNS server as the destination address of the message to be sent. DNS queries and / or resolutions are performed using the address information of the target DNS server.

21. The apparatus according to claim 16, characterized in that, The first transceiver module is also used to forward the address information of the target DNS server to a second application at the application layer.

22. The apparatus according to claim 21, characterized in that, The second application is an application with target permissions, wherein the target permissions are the permissions to receive address information of the DNS server specified by the operator.

23. The apparatus according to claim 22, characterized in that, The first acquisition module is further configured to acquire the identification information of the application with the target permissions from the network-side device before acquiring the message to be sent.

24. The apparatus according to any one of claims 16 to 23, characterized in that, The first transceiver module is further configured to receive a DNS response returned by the target DNS server after sending the message to be sent to the target DNS server specified by the operator, wherein the DNS response carries the address information of the target server, and the target server is the server with the closest topological distance to the device obtained by resolving the message to be sent.

25. The apparatus according to claim 24, characterized in that, The first transceiver module is further configured to forward the DNS response to a first application at the application layer after receiving the DNS response returned by the target DNS server, wherein the first application is the application that sends the message to be sent.

26. A configuration apparatus for a DNS server, characterized in that, include: The second transceiver module is used to receive indication information sent by the terminal, wherein the indication information indicates that the terminal has the target capability; The second acquisition module is used to obtain the address information of the target DNS server specified by the operator; The second transceiver module is further configured to send the address information of the target DNS server to the terminal; The target capability includes at least one of the following: The terminal is equipped with a first functional entity, which is capable of sending DNS query requests to a DNS server designated by the operator. The terminal supports obtaining the address information of the DNS server specified by the operator from the network-side device; The terminal supports obtaining the address information of the DNS server specified by the operator from the network-side device through the PDU session, and configuring the obtained DNS server address information to the PDU session; The terminal supports obtaining the DNS configuration specified by the operator, and this DNS configuration will not be modified. The terminal supports forwarding the DNS configuration specified by the operator to applications with target permissions, wherein the target permissions are the permissions to receive the address information of the DNS server specified by the operator. The terminal supports forwarding DNS responses received from the DNS server specified by the operator to the application.

27. The apparatus according to claim 26, characterized in that, The second acquisition module acquires the address information of the target DNS server specified by the operator, including: Based on the terminal's subscription information, the terminal's location information, and the user plane PSA to which the terminal is anchored, the address information of the target DNS server is obtained.

28. The apparatus according to claim 26, characterized in that, The second transceiver module sends the address information of the target DNS server to the terminal, including: The PCO sends the address information of the target DNS server to the terminal.

29. The apparatus according to claim 28, characterized in that, The second transceiver module is also used for one of the following: The terminal is instructed to indicate a function identifier, wherein the function identifier is used to indicate that when the operating system or chip receives the address information of the target DNS server, it will send the address information to the function entity corresponding to the function identifier; The terminal is instructed with an application identifier, wherein the application identifier is used to indicate an application capable of obtaining the address information of the target DNS server.

30. The apparatus according to claim 29, characterized in that, The second acquisition module is also used for one of the following: Receive first indication information sent by the terminal, wherein the first indication information indicates an application on the terminal; determine, based on the first indication information, an application on the terminal that can obtain the address information of the target DNS server; Obtain the application identifier signed with the operator from the Unified Data Management Entity (UDM) or the Unified Data Repository (UDR).

31. A terminal, characterized in that, It includes a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the method for sending DNS messages as described in any one of claims 1 to 10.

32. A network-side device, characterized in that, It includes a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the DNS server configuration method as described in any one of claims 11 to 15.

33. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the DNS message sending method as described in any one of claims 1 to 10, or the steps of the DNS server configuration method as described in any one of claims 11 to 15.

Images