Domain Name System (DNS) Query Method, Device and Network Side Device

Abstract

The present application discloses a Domain Name System (DNS) query method, apparatus, and network-side device, belonging to the field of communication technologies. The method according to an embodiment of the present application includes: a first network-side device receives a first DNS query sent by a first terminal; the first network-side device performs target processing on the first DNS query according to a processing result corresponding to a second DNS query of a second terminal stored therein; wherein, positions of the first terminal and the second terminal are within a target range.

Description

Technical Field

[0001] This application belongs to the field of communication technologies, and particularly relates to a Domain Name System (DNS) query method, apparatus, and network-side device. Background Art

[0002] The Edge Application Server Discovery Function (EASDF) is a core network element used to process Domain Name System (DNS) query requests sent by terminals.

[0003] Currently, the process for EASDF to process terminal DNS queries is as follows: The terminal sends a DNS query to the EASDF. Then, the EASDF makes a judgment based on the DNS query as to whether to send the DNS query to the Central DNS (C-DNS) or the Local DNS (L-DNS). If there is no corresponding processing rule in the EASDF and the DNS query cannot be processed, the EASDF sends information such as the Fully Qualified Domain Name (FQDN) in the DNS query to the Session Management Function (SMF). The SMF provides a corresponding processing rule for the EASDF based on information such as the current terminal location and the FQDN. In the DNS processing rule, the IP address of the DNS server to which this DNS query of the terminal should be sent is included, for example, the IP address of the C-DNS or L-DNS server. Then, after the C-DNS or L-DNS server finds the IP address corresponding to the FQDN and sends the DNS response to the EASDF, the EASDF saves the DNS query result (i.e., the server IP address corresponding to the FQDN in the DNS query) to the SMF, and then the EASDF sends the DNS response to the terminal. In this way, the terminal obtains the server IP address corresponding to the requested FQDN.

[0004] However, in the above solution, if multiple terminals perform DNS queries, the interaction process between the EASDF and the SMF will be relatively cumbersome. Therefore, how to improve the efficiency of DNS queries is a technical problem that those skilled in the art urgently need to solve. Summary of the Invention

[0005] Embodiments of this application provide a Domain Name System (DNS) query method, apparatus, and network-side device, which can solve the technical problem of the relatively cumbersome interaction process between the EASDF and the SMF in the prior art.

[0006] In a first aspect, a DNS query method is provided, which is applied to a first network-side device. The method includes:

[0007] The first network-side device receives a first DNS query sent by a first terminal;

[0008] The first network-side device performs target processing on the first DNS query according to the processing result corresponding to the second DNS query of the second terminal stored;

[0009] Wherein, the positions of the first terminal and the second terminal are within a target range.

[0010] In a second aspect, a Domain Name System (DNS) query method is provided, which is applied to a second network-side device. The method includes:

[0011] The second network-side device receives the first DNS query of the first terminal sent by the first network-side device; the first DNS query is sent according to the processing result corresponding to the second DNS query of the second terminal stored;

[0012] The second network-side device sends a first DNS response corresponding to the first DNS query to the first network-side device;

[0013] Wherein, the positions of the first terminal and the second terminal are within a target range.

[0014] In a third aspect, a Domain Name System (DNS) query method is provided, which is applied to a third network-side device. The method includes:

[0015] The third network-side device receives notification information sent by the first network-side device, where the notification information is used to indicate triggering the insertion of an uplink classifier (UL CL) corresponding to a first DNS response;

[0016] The third network-side device performs the insertion of the uplink classifier (UL CL) corresponding to the first DNS response;

[0017] Wherein, the first DNS response is a DNS response corresponding to the first DNS query sent by the first terminal; the non-insertion of the UL CL corresponding to the first DNS response indicates that there is no second DNS response, or the UL CL corresponding to the second DNS response is not inserted, where the second DNS response is the same as the first DNS response; or, the IP address in the second DNS response is the same as the IP address in the first DNS response, or the IP address segment in the second DNS response is the same as the IP address segment in the first DNS response.

[0018] In a fourth aspect, a Domain Name System (DNS) query apparatus is provided, including:

[0019] A receiving module, configured to receive a first DNS query sent by a first terminal;

[0020] A processing module, configured to perform target processing on the first DNS query according to a processing result corresponding to a second DNS query of a second terminal stored already;

[0021] Wherein, positions of the first terminal and the second terminal are within a target range.

[0022] In a fifth aspect, a Domain Name System (DNS) query apparatus is provided, including:

[0023] A receiving module, configured to receive a first DNS query of a first terminal sent by a first network-side device; the first DNS query is sent according to a processing result corresponding to a second DNS query of a second terminal stored already;

[0024] A sending module, configured to send a first DNS response corresponding to the first DNS query to the first network-side device;

[0025] Wherein, positions of the first terminal and the second terminal are within a target range.

[0026] In a sixth aspect, a Domain Name System (DNS) query apparatus is provided, including:

[0027] A receiving module, configured to receive notification information sent by the first network-side device, where the notification information is used to indicate triggering of insertion of an uplink classifier (UL CL) corresponding to a first DNS response;

[0028] A processing module, configured to perform insertion of the uplink classifier (UL CL) corresponding to the first DNS response;

[0029] Wherein, the first DNS response is a DNS response corresponding to a first DNS query sent by a first terminal; that the UL CL corresponding to the first DNS response is not inserted indicates that there is no second DNS response, or the UL CL corresponding to the second DNS response is not inserted, where the second DNS response is the same as the first DNS response; or, an IP address in the second DNS response is the same as an IP address in the first DNS response, or an IP address segment in the second DNS response is the same as an IP address segment in the first DNS response.

[0030] In a seventh aspect, a first network-side device is provided, where the first network-side device includes a processor, a memory, and a program or instruction stored on the memory and executable on the processor, and when the program or instruction is executed by the processor, steps of the method as described in the first aspect are implemented.

[0031] In an eighth aspect, a first network-side device is provided, including a processor and a communication interface. The communication interface is configured to receive a first DNS query sent by a first terminal, and the processor is configured to perform target processing on the first DNS query according to a processing result corresponding to a second DNS query of a second terminal stored in advance;

[0032] wherein, positions of the first terminal and the second terminal are within a target range.

[0033] In a ninth aspect, a second network-side device is provided. The second network-side device includes a processor, a memory, and a program or instruction stored on the memory and executable on the processor. When the program or instruction is executed by the processor, the steps of the method described in the second aspect are implemented.

[0034] In a tenth aspect, a second network-side device is provided, including a processor and a communication interface. The communication interface is configured to receive a first DNS query sent by a first network-side device; the first DNS query is sent according to a processing result corresponding to a second DNS query of a second terminal stored in advance; the communication interface is further configured to send a first DNS response corresponding to the first DNS query to the first network-side device;

[0035] wherein, positions of the first terminal and the second terminal are within a target range.

[0036] In an eleventh aspect, a third network-side device is provided. The third network-side device includes a processor, a memory, and a program or instruction stored on the memory and executable on the processor. When the program or instruction is executed by the processor, the steps of the method described in the third aspect are implemented.

[0037] In a twelfth aspect, a third network-side device is provided, including a processor and a communication interface. The communication interface is configured to receive notification information sent by the first network-side device, where the notification information is used to indicate triggering the insertion of an uplink classifier (UL CL) corresponding to a first DNS response; the processor is configured to perform the insertion of the UL CL corresponding to the first DNS response; wherein, the first DNS response is a DNS response corresponding to a first DNS query sent by a first terminal; the fact that the UL CL corresponding to the first DNS response is not inserted indicates that there is no second DNS response, or the UL CL corresponding to the second DNS response is not inserted, where the second DNS response is the same as the first DNS response; or, an IP address in the second DNS response is the same as an IP address in the first DNS response, or an IP address segment in the second DNS response is the same as an IP address segment in the first DNS response.

[0038] In a thirteenth aspect, a readable storage medium is provided. A program or instructions are stored on the readable storage medium. When the program or instructions are executed by a processor, the steps of the method described in the first aspect, or the steps of the method described in the second aspect, or the steps of the method described in the third aspect are implemented.

[0039] In a fourteenth aspect, a chip is provided. The chip includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is configured to run a program or instructions to implement the method described in the first aspect, or the method described in the second aspect, or the method described in the third aspect.

[0040] In a fifteenth aspect, a computer program / program product is provided. The computer program / program product is stored in a non-transitory storage medium. The program / program product is executed by at least one processor to implement the steps of the DNS query method described in the first aspect or the second aspect or the third aspect.

[0041] In the embodiments of the present application, since the positions of the first terminal and the second terminal are within the target range, and the first DNS query sent by the first terminal is the same as or similar to the second DNS query, the obtained processing results are also the same as or similar. Then, the first network-side device can use the processing result corresponding to the second DNS query of the second terminal stored in advance to process the current first DNS query, which can reduce the interaction between network-side devices and improve the DNS query efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] Figure 1 is a structural diagram of a wireless communication system to which the embodiments of the present application can be applied;

[0043] Figure 2 is a schematic flowchart of a DNS query method provided by an embodiment of the present application;

[0044] Figure 3 is a schematic interaction flowchart of a DNS query method provided by an embodiment of the present application;

[0045] Figure 4 is a second schematic interaction flowchart of a DNS query method provided by an embodiment of the present application;

[0046] Figure 5 is a second schematic flowchart of a DNS query method provided by an embodiment of the present application;

[0047] Figure 6 is a third schematic flowchart of a DNS query method provided by an embodiment of the present application;

[0048] Figure 7It is one of the schematic structural diagrams of the DNS query device provided by the embodiments of the present application;

[0049] Figure 8 It is the second of the schematic structural diagrams of the network selection device provided by the embodiments of the present application;

[0050] Figure 9 It is the third of the schematic structural diagrams of the network selection device provided by the embodiments of the present application;

[0051] Figure 10 It is the schematic structural diagram of the communication device provided by the embodiments of the present application;

[0052] Figure 11 It is the schematic structural diagram of the network-side device provided by the embodiments of the present application. Detailed implementation manners

[0053] Next, the technical solutions in the embodiments of the present application will be clearly described in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are some, rather than all, of the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art belong to the scope protected by the present application.

[0054] The terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects, rather than to describe a specific order or sequence. It should be understood that such terms may be interchanged under appropriate circumstances so that the embodiments of the present application can be implemented in an order different from those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same category, and the number of objects is not limited. For example, the first object may 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 means an "or" relationship between the associated objects before and after.

[0055] It should be noted that the technology described in the embodiments of this application is not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, and 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 this 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 the New Radio (NR) system for example purposes, and the NR term is used in most of the following descriptions, but these technologies can also be applied to applications other than NR system applications, such as the 6th Generation (6 th Generation, 6G) communication system.

[0056] Figure 1A block 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, an access network device 12, and a core network device 13. Among them, the terminal 11 can also be referred to as a terminal device or a user terminal (User Equipment, UE). The terminal 11 can be a mobile phone, a tablet personal computer, a laptop computer or a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile Internet device (MID), a wearable device, a vehicle-mounted device (VUE), a pedestrian terminal (PUE), etc. Terminal-side devices. Wearable devices include smart watches, bracelets, earphones, glasses, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiments of the present application. The access network device 12 can also be referred to as a radio access network device or a radio access network (Radio Access Network, RAN). The access network device 12 can be a base station. The base station can be referred to as a Node B, an evolved Node B, an access point, a base transceiver station (Base Transceiver Station, BTS), a radio base station, a radio transceiver, a basic service set (Basic Service Set, BSS), an extended service set (Extended Service Set, ESS), a B node, an evolved B node (eNB), a home B node, a home evolved B node, a WLAN access point, a WiFi node, a transmitting and receiving point (Transmitting Receiving Point, TRP), or some other suitable term in the art. As long as the same technical effect is achieved, the base station is not limited to specific technical terms. It should be noted that in the embodiments of the present application, only the base station in the NR system is taken as an example, but the specific type of the base station is not limited.The core network device 13 may also be referred to as a core network (Core Network, CN) or a 5G core (5G core, 5GC) network. The core network device 13 may include but is not limited to at least one of the following: a core network node, a core network function, a mobility management entity (Mobility Management Entity, MME), an access mobility management function (Access Management Function, AMF), a session management function (Session Management Function, SMF), a user plane function (User Plane Function, UPF), a policy control function (Policy Control Function, PCF), a policy and charging rules function unit (Policy and Charging Rules Function, PCRF), an edge application service discovery function (Edge Application Server Discovery Function, EASDF), an application function (Application Function, AF), etc. It should be noted that in the embodiment of the present application, only the core network device in the 5G system is taken as an example, but it is not limited to this.

[0057] In the DNS query method of the embodiment of the present application, the current DNS query is processed using the processing result of the terminal that has initiated the DNS query, which can reduce the interaction between network-side devices and improve the DNS query efficiency.

[0058] The DNS query method provided in the embodiment of the present application is described in detail below through some embodiments and their application scenarios in conjunction with the accompanying drawings.

[0059] Figure 2 This is one of the flow charts of the DNS query method provided in the embodiment of the present application. Figure 2 As shown, the DNS query method provided in this embodiment includes:

[0060] Step 101: A first network-side device receives a first DNS query sent by a first terminal.

[0061] The first network side device may be a core network element capable of processing a DNS query sent by a terminal. For example, the first network side device may refer to EASDF or SMF. The first terminal initiates a first DNS query to the first network side device. The first DNS query may include an FQDN to obtain a first DNS response corresponding to the first DNS query, for example, including: an IP address corresponding to the FQDN.

[0062] Step 102: The first network-side device performs target processing on the first DNS query according to the processing result corresponding to the second DNS query of the second terminal stored previously;

[0063] Among them, the positions of the first terminal and the second terminal are within the target range.

[0064] Specifically, assume that the second terminal has triggered a second DNS query previously and obtained a processing result. The processing result may include: a second DNS response and / or a processing rule. If the current first terminal and the second terminal meet certain conditions, for example, the first DNS query sent by the first terminal is the same as or similar to the second DNS query, and / or the first terminal and the second terminal are within the same target range, then the obtained processing results are also the same or similar. In this case, the processing result of the second terminal stored previously can be used to process the first DNS query to obtain the processing result corresponding to the first DNS query, including a first DNS response and / or a processing rule, so as to improve the efficiency of DNS query.

[0065] Optionally, the first terminal and the second terminal need to be within the same target range. For example, it includes at least one of the following situations: the first terminal and the second terminal are in the same location area, or the FQDNs in the DNS queries sent by the first terminal and the second terminal are the same or the FQDNs belong to the same FQDN list, or both are subscribed terminals, etc.

[0066] In the method of this embodiment, since the positions of the first terminal and the second terminal are within the target range and the first DNS query sent by the first terminal is the same as or similar to the second DNS query, the obtained processing results are also the same or similar. Then, the first network-side device can use the processing result corresponding to the second DNS query of the second terminal stored previously to process the current first DNS query, which can reduce the interaction between network-side devices and improve the DNS query efficiency.

[0067] Optionally, the position of the second terminal and the first terminal being within the target range includes at least one of the following situations:

[0068] The positions of the first terminal and the second terminal are in the same location area. Being in the same location area includes at least one of the following: having the same data network access identifier DNAI, having the same tracking area identifier TAI, or having the same cell identifier Cell ID; or,

[0069] The FQDN in the first DNS query of the first terminal is the same as the FQDN in the second DNS query of the second terminal; or,

[0070] The FQDN in the first DNS query of the first terminal belongs to the same FQDN list as the FQDN in the second DNS query of the second terminal; wherein, the FQDN in the FQDN list or the DNS query to which the FQDN belongs corresponds to the same processing rule;

[0071] Both the first terminal and the second terminal are subscribed terminals; a subscribed terminal is a terminal that can use the DNS service provided by the first network-side device;

[0072] Wherein, the second DNS query and its corresponding processing result have been cached in the first network-side device or the third network-side device.

[0073] Specifically, the first terminal and the second terminal have at least one of the following in common:

[0074] 1. The first terminal and the second terminal are in the same location area, including at least one of the following situations: having the same data network access identifier (DNAI), having the same tracking area identifier (TAI), or having the same cell identifier Cell ID;

[0075] In this case, the first terminal and the second terminal have the same IP address.

[0076] 2. The FQDNs in the DNS queries of the first terminal and the second terminal are the same;

[0077] 3. The FQDNs in the DNS queries of the first terminal and the second terminal belong to an FQDN list. The FQDNs in this FQDN list or the DNS queries to which the FQDNs belong correspond to the same processing rules (handling rules, or DNS handling rules);

[0078] 4. Both the first terminal and the second terminal are subscribed terminals.

[0079] Optionally, the previously initiated DNS query and its corresponding processing result can be cached in the first network-side device or the third network-side device, facilitating the subsequent use of the DNS query and its corresponding processing result to process other DNS queries.

[0080] In one embodiment, step 102 can be implemented in the following several ways:

[0081] One implementation method:

[0082] The processing result corresponding to the second DNS query includes: a second DNS response;

[0083] The first network-side device obtains a first DNS response corresponding to a first DNS query according to a second DNS response;

[0084] The first DNS response includes at least one of the following: a first Internet Protocol (IP) address, a first Fully Qualified Domain Name (FQDN).

[0085] The first IP address, or the second IP address in the second DNS response, is the corresponding server IP address obtained by the second network-side device through resolving or querying the FQDN included in the first DNS query or the second DNS query.

[0086] Specifically, when the first network-side device receives a first DNS query from a first terminal, if it finds that the processing result corresponding to the second DNS query of a second terminal, such as a second DNS response, is stored, since the first DNS query and the second DNS query are the same or similar, the first network-side device does not need to send the first DNS query to the second network-side device (such as a DNS server) to obtain the first DNS response. The first network-side device directly obtains the first DNS response corresponding to the first DNS query according to the second DNS response, and feeds back the first DNS response to the first terminal.

[0087] For example, the first network-side device has previously saved the correspondence between the FQDN of the second terminal and the IP address. Assume that FQDN = Baidu.com, and the corresponding IP address is: 10.1.1.1.

[0088] Therefore, for the first DNS query of the first terminal, assuming FQDN = Baidu.com, directly send the first DNS response including the IP address: 10.1.1.1 to the first terminal.

[0089] Optionally, obtaining the first DNS response corresponding to the first DNS query can be implemented in the following ways:

[0090] The first network-side device uses the second DNS response as the first DNS response; or,

[0091] The first network-side device generates a first DNS response according to the parameters in the second DNS response; the second DNS response includes at least one of the following: a second IP address, a second FQDN.

[0092] Specifically, the first network-side device directly uses the second DNS response as the first DNS response and feeds it back to the first terminal, and the DNS query efficiency is relatively high. Or, the first network-side device extracts the parameters in the second DNS response and regenerates the first DNS response and sends it to the first terminal. The parameters include, for example, the second IP address and / or the second FQDN.

[0093] For example, in the second DNS response, if it contains FQDN = Baidu.com and the corresponding IP address is 10.1.1.1, then using these two parameters, the first network-side device regenerates the first DNS response, which also contains FQDN = Baidu.com and IP = 10.1.1.1.

[0094] In the above embodiment, since the positions of the first terminal and the second terminal are within the target range, that is, the first DNS query and the second DNS query sent by the first terminal are the same or similar, and / or the first terminal H and the second terminal are in the same location area, the obtained DNS responses are also the same or similar. Then, the first DNS response corresponding to the first DNS query can be obtained by using the second DNS response of the second terminal that has initiated the DNS query, which can reduce the interaction between network-side devices and improve the DNS query efficiency.

[0095] Another implementation method:

[0096] The processing result corresponding to the second DNS query includes: processing rules;

[0097] The first network-side device sends the first DNS query to the second network-side device according to the processing rules; the processing rules specify which second network-side device the first network-side device should send the DNS query to.

[0098] The first network-side device receives the first DNS response corresponding to the first DNS query sent by the second network-side device; the first DNS response includes at least one of the following: the first IP address, the first FQDN.

[0099] Among them, the second network-side device can be a core network element that processes DNS queries, such as a DNS server.

[0100] Specifically, when the first network-side device receives the first DNS query of the first terminal, if it finds that it has stored the processing result corresponding to the second DNS query of the second terminal, such as processing rules, the first DNS query and the second DNS query are the same or similar, and / or the first terminal H and the second terminal are in the same location area, then there is no need to trigger a notification request (Neasdf_DNS Context_Notify Request, which is used to request the SMF to issue processing rules) to the SMF. Instead, directly according to the processing rules corresponding to the second DNS query, it sends the first DNS query to the second network-side device (such as a DNS server). After the first network-side device receives the first DNS response corresponding to the first DNS query sent by the second network-side device, it feeds back the first DNS response to the first terminal.

[0101] In this solution, the DNS queries sent by other second terminals have been reported by the first network-side device to the SMF, and the SMF has configured processing rules for them. Therefore, the first network-side device EASDF can use the configured processing rules to process the current first DNS query without reporting to the SMF to request new processing rules, saving the signaling interaction between network-side devices.

[0102] In the above embodiment, the first network-side device can use the processing rules corresponding to the second DNS query of the second terminal to process the current first DNS query, that is, directly send the first DNS query to the DNS server according to the processing rules to obtain the first DNS response, without reporting to the SMF to request new processing rules, saving the signaling interaction between network-side devices and improving the DNS query efficiency.

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

[0104] The first network-side device sends a request message to the fourth network-side device to determine whether the first terminal is a subscribed terminal; a subscribed terminal is a terminal that can use the DNS service provided by the first network-side device;

[0105] If so, perform the operation of target processing on the first DNS query.

[0106] Among them, the fourth network-side device can be a core network element for data management, such as a Unified Data Management (UDM).

[0107] If the DNS service provided by the operator to the terminal is differentiated, for example, only subscribed terminals can use the same processing rules (handling rules, or DNS handling rules), then the first network-side device EASDF can also trigger a request to the UDM to determine whether the first terminal is a subscribed terminal, where a subscribed terminal is a terminal that can use the DNS service provided by the first network-side device.

[0108] For example, determine whether the Subscription Permanent Identifier (SUPI) corresponding to the first terminal is the same as the SUPI of the terminal subscribed to the operator. If so, the solution in the above embodiment can be executed. If not, the solution in the above embodiment is not executed.

[0109] In the above embodiments, by sending a request message to the fourth network-side device to determine whether the first terminal is a subscribed terminal, if it is a subscribed terminal, the corresponding processing result of the DNS query of other terminals stored can be used to process the first DNS query of the first terminal, improving the efficiency of the DNS query.

[0110] As Figure 3 shown, the DNS query method includes the following steps:

[0111] Step 1, the second terminal sends a second DNS query to EASDF;

[0112] Step 2, EASDF reports the second DNS query to SMF;

[0113] Step 3, SMF sends a processing rule corresponding to the second DNS query to EASDF; the processing rule corresponds to the FQDN in a specific DNS query and the location area where the second terminal is located.

[0114] Step 4, EASDF sends the second DNS query to the DNS server determined or indicated in the rule according to the processing rule;

[0115] Step 5, the DNS server sends a second DNS response corresponding to the second DNS query to EASDF; the second DNS response contains the server IP address;

[0116] Step 6, trigger the UL CL insertion corresponding to the second DNS response (at this time, the UL CL corresponding to the second DNS response has not been inserted); because the second terminal needs to establish an IP connection with the server IP address in the second DNS response, and since the server IP address may be a local server, it is necessary to insert UL CL to divert the uplink traffic of the second terminal to the local server in the DNS response. In this step, by sending the server IP address in the second DNS response to SMF, SMF is allowed to consider and insert UL CL.

[0117] After the UL CL is inserted, SMF triggers Neasdf_DNSContext_Notify Response to inform EASDF that the UL CL has been inserted

[0118] Step 7, (when EASDF receives the notification that the UL CL has been inserted) EASDF sends the second DNS response to the second terminal;

[0119] Step 8, the first terminal sends a first DNS query to EASDF; in this embodiment, the first terminal and the second terminal satisfy at least one of the following conditions:

[0120] The first terminal and the second terminal are in the same location area;

[0121] The FQDN in the first DNS query initiated by the first terminal is the same as the FQDN in the second DNS query initiated by the second terminal;

[0122] The FQDN in the first DNS query of the first terminal and the FQDN in the second DNS query of the second terminal belong to the same FQDN list; among them, the FQDN in the FQDN list or the DNS query to which the FQDN belongs corresponds to the same processing rule;

[0123] Both the first terminal and the second terminal are subscribed terminals.

[0124] Step 9, EASDF obtains the processing result corresponding to the second DNS query of the stored second terminal;

[0125] The first terminal and the second terminal need to meet certain conditions, such as the first terminal and the second terminal being within the target range, and the DNS queries being the same or similar (for example, the FQDNs are the same);

[0126] If the processing result includes a second DNS response, then perform step 10a, EASDF sends a first DNS response to the first terminal; in this step, the process of EASDF forwarding the first DNS query to the second network-side device is saved, and signaling is saved. When EASDF determines that certain conditions in step 9 are met, EASDF does not forward the first DNS query to the DNS server.

[0127] If the processing result includes a processing rule, then perform step 10b, EASDF sends a first DNS query to the DNS server according to the processing rule; in this step, the signaling for EASDF to request the processing rule from the first network-side device is saved: namely: Neasdf_DNSContext_Notify Request; at the same time, since the SMF does not receive the FQDN or the first DNS query reported by EASDF, it will not send a processing rule to EASDF either, thus saving: Neasdf_DNSContext_Update Request signaling.

[0128] Step 11, the DNS server sends a first DNS response corresponding to the first DNS query to EASDF;

[0129] Step 12, EASDF sends the first DNS response to the first terminal.

[0130] In another embodiment, after the first network-side device performs target processing on the first DNS query, for example, after obtaining the first DNS response corresponding to the first DNS query, the method further includes:

[0131] The first network-side device determines whether the uplink classifier (UL CL) corresponding to the first DNS response corresponding to the first DNS query has been inserted;

[0132] If not, the first network-side device sends a notification message to the third network-side device, where the notification message is used to indicate triggering the insertion of the UL CL corresponding to the first DNS response;

[0133] If so, do not perform triggering the insertion of the UL CL corresponding to the first DNS response.

[0134] Among them, the third network-side device may be a network element with session management functions, such as an SMF.

[0135] Specifically, after the first network-side device obtains the first DNS response and before sending it to the first terminal, it needs to determine whether the UL CL corresponding to the first DNS response corresponding to the first DNS query has been inserted. If so, do not perform triggering the insertion of the UL CL corresponding to the first DNS response, that is, directly send the first DNS response to the first terminal;

[0136] If not, the first network-side device sends a notification message to the third network-side device to trigger the insertion of the UL CL corresponding to the first DNS response.

[0137] Among them, the UL CL is a form of the UPF user plane function. The SMF can provide some traffic splitting rules on the UL CL so that the uplink traffic of the UE can be split locally. The insertion and removal of the UL CL are determined by the SMF.

[0138] Optionally, "the first network-side device determines whether the UL CL corresponding to the first DNS response corresponding to the first DNS query has been inserted" can be specifically implemented in the following way:

[0139] The first network-side device determines whether there is a second DNS response, where the second DNS response is the same as the first DNS response; or, the IP address in the second DNS response is the same as the IP address in the first DNS response, or, the IP address segment in the second DNS response is the same as the IP address segment in the first DNS response;

[0140] If there is a second DNS response, determine whether the UL CL corresponding to the second DNS response has been inserted.

[0141] Specifically, it is determined whether the UL CL corresponding to the first DNS response has been inserted, that is, it is determined whether there is any other DNS response that has triggered the same UL CL insertion. First, it is determined whether there is a second DNS response, that is, the DNS response corresponding to the previously sent DNS query, and this second DNS response is the same as the first DNS response; or, the IP address in the second DNS response is the same as the IP address in the first DNS response, or, the IP address segment in the second DNS response is the same as the IP address segment in the first DNS response;

[0142] For example, 192.224.0.0 and 192.224.0.1 are two hosts within the same network segment. Because this is a Class C IP address: 192.224.0.X.

[0143] If there is no second DNS response, it means that the uplink classifier UL CL corresponding to the second DNS response has not been inserted, that is, it means that the uplink classifier UL CL corresponding to the first DNS response has not been inserted. The first network-side device sends a notification message to the third network-side device to trigger the insertion of the uplink classifier UL CL corresponding to the first DNS response; if there is a second DNS response, it means that the UL CL corresponding to the first DNS response may have been inserted. Further, it is necessary to determine whether the UL CL corresponding to the second DNS response has been inserted. If the UL CL corresponding to the second DNS response has been inserted, it means that the UL CL corresponding to the first DNS response has been inserted, and then the first DNS response is directly fed back to the first terminal.

[0144] In the above embodiments, by using the UL CL inserted by the existing DNS response, there is no need to repeatedly insert the same UL CL, saving the interaction of the network-side device and improving the efficiency of DNS query.

[0145] As Figure 4 shown, the DNS query method includes the following steps:

[0146] Step 1: The second terminal sends a second DNS query to EASDF;

[0147] Step 2: EASDF reports the second DNS query to SMF;

[0148] Step 3: SMF issues the processing rule corresponding to the second DNS query to EASDF according to the second DNS query reported by EASDF (mainly the FQDN in the second DNS query);

[0149] Step 4: EASDF sends the second DNS query to the DNS server specified in the processing rule according to the processing rule;

[0150] Step 5: The DNS server sends a second DNS response corresponding to the second DNS query to EASDF;

[0151] Step 6: Trigger the insertion of the UL CL corresponding to the second DNS response (at this time, the UL CL corresponding to the second DNS response has not been inserted); The main purpose of this step is the IP address of the server in the second DNS response. In order to establish a user plane between the UE and this IP address, the SMF needs to insert the UL CL.

[0152] Step 7: EASDF sends the second DNS response to the second terminal; The premise for sending is that the SMF notifies EASDF that the insertion of the UL CL has been completed

[0153] Step 8: The first terminal sends a first DNS query to EASDF;

[0154] Step 9: EASDF obtains the processing result corresponding to the second DNS query of the stored second terminal;

[0155] The first terminal and the second terminal need to meet certain conditions. For example, the first terminal and the second terminal are within the target range, and the DNS queries are the same or similar;

[0156] If the processing result includes a second DNS response, then execute Step 9': Determine whether it is necessary to trigger the insertion of the UL CL;

[0157] If it is necessary to trigger, then execute Step 13: Trigger the insertion of the UL CL corresponding to the first DNS response; That is, the second DNS response triggers the insertion of the UL CL, but it needs to meet the following conditions before insertion: The second DNS response is different from the first DNS response, or the server IPs included in the second DNS response and the first DNS response are different or the IP address segments are different; or the second DNS response does not trigger the insertion of the UL CL;

[0158] If it is not necessary to trigger, then execute Step 10a: EASDF sends the first DNS response to the first terminal; This step is equivalent to that EASDF determines that it is not necessary to trigger the insertion of the UL CL, so it is not necessary to trigger the Neasdf_DNSContext_Notifyrequest signaling, saving signaling, that is, the second DNS response has triggered the insertion of the UL CL, and the second DNS response is the same as the first DNS response, the IPs are the same or the IP address segments are the same;

[0159] If the processing result includes a processing rule, then execute Step 10b: EASDF sends a first DNS query to the DNS server according to the processing rule;

[0160] Step 11: The DNS server sends a first DNS response corresponding to the first DNS query to EASDF;

[0161] Step 14: Determine whether it is necessary to trigger UL CL insertion;

[0162] If it is necessary to trigger, execute Step 15: Trigger UL CL insertion corresponding to the first DNS response; similar to Step 13;

[0163] If it is not necessary to trigger, execute Step 12: The EASDF first terminal sends the first DNS response.

[0164] Figure 5 It is the second flow diagram of the DNS query method provided by the embodiments of the present application. As Figure 5 shown, the DNS query method provided by this embodiment includes:

[0165] Step 201: The second network side device receives the first DNS query of the first terminal sent by the first network side device; the first DNS query is sent according to the processing result corresponding to the second DNS query of the second terminal stored;

[0166] Step 202: The second network side device sends the first DNS response corresponding to the first DNS query to the first network side device;

[0167] Wherein, the positions of the first terminal and the second terminal are within the target range.

[0168] Optionally, the second network side device receives the first DNS query sent by the first network side device; the first DNS query is sent according to the processing result corresponding to the second DNS query of the second terminal stored;

[0169] The second network side device sends the first DNS response corresponding to the first DNS query to the first network side device;

[0170] Wherein, the positions of the first terminal and the second terminal are within the target range.

[0171] Optionally, the first DNS response includes at least one of the following: the first Internet Protocol IP address, the first Fully Qualified Domain Name FQDN.

[0172] Optionally, the positions of the second terminal and the first terminal being within the target range include at least one of the following situations:

[0173] The positions of the first terminal and the second terminal are in the same location area, and the being in the same location area includes at least one of the following: having the same Data Network Access DNAI, having the same Tracking Area Identity TAI, or having the same Cell ID; or,

[0174] The FQDN in the first DNS query of the first terminal is the same as the FQDN in the second DNS query of the second terminal; or,

[0175] The FQDN in the first DNS query of the first terminal and the FQDN in the second DNS query of the second terminal belong to the same FQDN list; wherein, the FQDN or the DNS query corresponding to the FQDN in the FQDN list corresponds to the same processing rule;

[0176] Both the first terminal and the second terminal are subscribed terminals; the subscribed terminal is a terminal that can use the DNS service provided by the first network-side device;

[0177] Wherein, the second DNS query and its corresponding processing result have been cached in the first network-side device or the third network-side device.

[0178] The method of this embodiment, its specific implementation process and technical effect are similar to those in the method embodiment of the first network-side device. Specifically, reference can be made to the detailed introduction in the corresponding method embodiment of the first network-side device, which will not be elaborated here.

[0179] Figure 6 It is the third flow diagram of the DNS query method provided by the embodiment of the present application. As Figure 6 shown, the DNS query method provided by this embodiment includes:

[0180] Step 301, The third network-side device receives the notification information sent by the first network-side device, and the notification information is used to indicate triggering the insertion of the uplink classifier UL CL corresponding to the first DNS response;

[0181] Step 302, The third network-side device performs the insertion of the uplink classifier UL CL corresponding to the first DNS response;

[0182] Wherein, the first DNS response is the DNS response corresponding to the first DNS query sent by the first terminal; the non-insertion of the UL CL corresponding to the first DNS response indicates the non-existence of the second DNS response, or the non-insertion of the UL CL corresponding to the second DNS response, wherein the second DNS response is the same as the first DNS response; or, the IP address in the second DNS response is the same as the IP address in the first DNS response, or the IP address segment in the second DNS response is the same as the IP address segment in the first DNS response.

[0183] Wherein, the notification information may be sent by the first network-side device when it determines that the UL CL unique to the first DNS response is not inserted.

[0184] Optionally, the second DNS response is a DNS response corresponding to a second DNS query sent by a second terminal; the positions of the first terminal and the second terminal are within a target range.

[0185] Optionally, the first DNS response includes at least one of the following: a first Internet Protocol (IP) address, a first Fully Qualified Domain Name (FQDN).

[0186] Optionally, the positions of the second terminal and the first terminal being within a target range includes at least one of the following cases:

[0187] The positions of the first terminal and the second terminal are in the same location area, and being in the same location area includes at least one of the following: having the same Data Network Access Identifier (DNAI), having the same Tracking Area Identifier (TAI), or having the same Cell ID; or,

[0188] The FQDN in the first DNS query of the first terminal is the same as the FQDN in the second DNS query of the second terminal; or,

[0189] The FQDN in the first DNS query of the first terminal and the FQDN in the second DNS query of the second terminal belong to the same FQDN list; wherein, the FQDNs in the FQDN list or the DNS queries corresponding to the FQDNs correspond to the same processing rules;

[0190] The first terminal and the second terminal are both subscribed terminals; a subscribed terminal is a terminal that can use the DNS service provided by the first network-side device;

[0191] Wherein, the second DNS query and its corresponding processing result have been cached in the first network-side device or a third network-side device; the processing result includes at least one of the following: a second DNS response or a processing rule.

[0192] Optionally, the method further includes:

[0193] The third network-side device sends a request message to a fourth network-side device to determine whether the first terminal is a subscribed terminal; a subscribed terminal is a terminal that can use the DNS service provided by the first network-side device;

[0194] If so, the third network-side device performs the insertion of an Upward Classifier (UL CL) corresponding to the first DNS response.

[0195] The method of this embodiment, its specific implementation process and technical effects are similar to those in the method embodiment of the first network-side device. Specifically, reference can be made to the detailed introduction in the method embodiment corresponding to the first network-side device, which will not be elaborated here.

[0196] It should be noted that for the DNS query method provided in the embodiments of the present application, the execution entity may be a DNS query device, or a processing module in the DNS query device for executing the DNS query method. In the embodiments of the present application, taking the DNS query device executing the DNS query method as an example, the DNS query device provided in the embodiments of the present application is described.

[0197] Figure 7 is one of the schematic structural diagrams of the DNS query device provided by the present application. As Figure 7 shown, the DNS query device 700 provided in this embodiment includes:

[0198] A receiving module 701, configured to receive a first DNS query sent by a first terminal;

[0199] A processing module 702, configured to perform target processing on the first DNS query according to the processing result corresponding to the second DNS query of the second terminal stored;

[0200] Wherein, the positions of the first terminal and the second terminal are within a target range.

[0201] For the device in this embodiment, since the positions of the first terminal and the second terminal are within the target range, the first DNS query sent by the first terminal is the same as or similar to the second DNS query, and the obtained processing results are also the same as or similar. Then, the first network-side device can be used to process the current first DNS query according to the processing result corresponding to the second DNS query of the second terminal stored, which can reduce the interaction between network-side devices and improve the DNS query efficiency.

[0202] Optionally, the processing result corresponding to the second DNS query includes: a second DNS response;

[0203] The processing module 702 is specifically configured to:

[0204] Obtain a first DNS response corresponding to the first DNS query according to the second DNS response; the first DNS response includes at least one of the following: a first Internet Protocol (IP) address, a first Fully Qualified Domain Name (FQDN).

[0205] Optionally, the processing module 702 is specifically configured to:

[0206] Use the second DNS response as the first DNS response; or,

[0207] Generate the first DNS response according to the parameters in the second DNS response; the second DNS response includes at least one of the following: a second IP address, a second FQDN.

[0208] Optionally, the processing result corresponding to the second DNS query includes: a processing rule;

[0209] The apparatus further includes:

[0210] A sending module, configured to send the first DNS query to a second network-side device according to the processing rule;

[0211] The receiving module 701 is configured to receive a first DNS response corresponding to the first DNS query sent by the second network-side device; the first DNS response includes at least one of the following: a first IP address, a first FQDN.

[0212] Optionally, the processing module 702 is further configured to:

[0213] Determine whether an uplink classifier UL CL corresponding to the first DNS response corresponding to the first DNS query has been inserted;

[0214] If so, do not perform inserting the UL CL corresponding to the first DNS response;

[0215] The sending module is further configured to, if the processing module determines that the UL CL has not been inserted, send a notification message to a third network-side device, where the notification message is used to indicate triggering insertion of the uplink classifier UL CL corresponding to the first DNS response.

[0216] Optionally, the processing module 702 is specifically configured to:

[0217] Determine whether there is a second DNS response, where the second DNS response is the same as the first DNS response; or, an IP address in the second DNS response is the same as an IP address in the first DNS response, or an IP address segment in the second DNS response is the same as an IP address segment in the first DNS response;

[0218] If there is the second DNS response, determine whether an uplink classifier UL CL corresponding to the second DNS response has been inserted.

[0219] Optionally, the positions of the second terminal and the first terminal are within a target range, including at least one of the following situations:

[0220] The positions of the first terminal and the second terminal are in the same location area, and being in the same location area includes at least one of the following: having the same data network access identifier DNAI, having the same tracking area identifier TAI, or having the same cell identifier Cell ID; or,

[0221] The FQDN in the first DNS query of the first terminal is the same as the FQDN in the second DNS query of the second terminal; or,

[0222] The FQDN in the first DNS query of the first terminal and the FQDN in the second DNS query of the second terminal belong to the same FQDN list; wherein, the FQDN in the FQDN list or the DNS query to which the FQDN belongs corresponds to the same processing rule;

[0223] Both the first terminal and the second terminal are subscribed terminals; the subscribed terminal is a terminal that can use the DNS service provided by the first network-side device;

[0224] Wherein, the second DNS query and its corresponding processing result have been cached in the first network-side device or the third network-side device.

[0225] Optionally, the sending module is further configured to:

[0226] Send a request message to the fourth network-side device to determine whether the first terminal is a subscribed terminal; the subscribed terminal is a terminal that can use the DNS service provided by the first network-side device;

[0227] The processing module is configured to perform an operation of performing target processing on the first DNS query if the first terminal is a subscribed terminal.

[0228] The device in this embodiment can be used to execute the method in any of the foregoing method embodiments corresponding to the first network-side device. The specific implementation process and technical effects are similar to those in the method embodiment of the first network-side device. For details, reference can be made to the detailed introduction in the method embodiment corresponding to the first network-side device, which will not be elaborated here.

[0229] Figure 8 This is the second structural schematic diagram of the DNS query device provided by the present application. As Figure 8 shown, the DNS query device 800 provided in this embodiment includes:

[0230] A receiving module 801, configured to receive a first DNS query of a first terminal sent by a first network-side device; the first DNS query is sent according to the processing result corresponding to a second DNS query of a second terminal that has been stored;

[0231] A sending module 802, configured to send a first DNS response corresponding to the first DNS query to the first network-side device;

[0232] Wherein, the positions of the first terminal and the second terminal are within a target range.

[0233] Optionally, the positions of the second terminal and the first terminal are within a target range, including at least one of the following cases:

[0234] The positions of the first terminal and the second terminal are in the same location area, and being in the same location area includes at least one of the following: having the same data network access identifier DNAI, having the same tracking area identifier TAI, or having the same cell identifier Cell ID; or,

[0235] The FQDN in the first DNS query of the first terminal is the same as the FQDN in the second DNS query of the second terminal; or,

[0236] The FQDN in the first DNS query of the first terminal and the FQDN in the second DNS query of the second terminal belong to the same FQDN list; wherein, the FQDNs in the FQDN list or the DNS queries corresponding to the FQDNs correspond to the same processing rules;

[0237] Both the first terminal and the second terminal are subscribed terminals; the subscribed terminal is a terminal capable of using the DNS service provided by the first network-side device;

[0238] Wherein, the second DNS query and its corresponding processing result have been cached in the first network-side device or the third network-side device.

[0239] Optionally, the first DNS response includes at least one of the following: a first Internet Protocol IP address, a first fully qualified domain name FQDN.

[0240] The device in this embodiment can be used to execute the method in any one of the method embodiments corresponding to the foregoing second network-side device. The specific implementation process and technical effects are similar to those in the method embodiment of the second network-side device. For details, reference can be made to the detailed introduction in the method embodiment corresponding to the second network-side device, which will not be elaborated here.

[0241] Figure 9 It is the third structural schematic diagram of the DNS query device provided by this application. As Figure 9 shown, the DNS query device 900 provided in this embodiment includes:

[0242] A receiving module 901, configured to receive the notification information sent by the first network-side device, where the notification information is used to indicate triggering the insertion of an uplink classifier UL CL corresponding to the first DNS response;

[0243] A processing module 902, configured to execute the insertion of the uplink classifier UL CL corresponding to the first DNS response;

[0244] Wherein, the first DNS response is the DNS response corresponding to the first DNS query sent by the first terminal; the non-insertion of the UL CL corresponding to the first DNS response indicates the non-existence of the second DNS response, or the non-insertion of the UL CL corresponding to the second DNS response, where the second DNS response is the same as the first DNS response; or, the IP address in the second DNS response is the same as the IP address in the first DNS response, or the IP address segment in the second DNS response is the same as the IP address segment in the first DNS response.

[0245] Optionally, the second DNS response is the DNS response corresponding to the second DNS query sent by the second terminal; the positions of the first terminal and the second terminal are within the target range.

[0246] Optionally, the first DNS response includes at least one of the following: the first Internet Protocol IP address, the first Fully Qualified Domain Name FQDN.

[0247] Optionally, the positions of the second terminal and the first terminal being within the target range includes at least one of the following situations:

[0248] The positions of the first terminal and the second terminal are in the same location area, and being in the same location area includes at least one of the following: having the same Data Network Access Identifier DNAI, having the same Tracking Area Identifier TAI, or having the same Cell ID; or,

[0249] The FQDN in the first DNS query of the first terminal is the same as the FQDN in the second DNS query of the second terminal; or,

[0250] The FQDN in the first DNS query of the first terminal and the FQDN in the second DNS query of the second terminal belong to the same FQDN list; wherein, the FQDNs in the FQDN list or the DNS queries corresponding to the FQDNs correspond to the same processing rules;

[0251] The first terminal and the second terminal are both subscribed terminals; the subscribed terminal is a terminal that can use the DNS service provided by the first network-side device;

[0252] Wherein, the second DNS query and its corresponding processing result have been cached in the first network-side device or the third network-side device; the processing result includes at least one of the following: the second DNS response or the processing rule.

[0253] Optionally, the sending module is further configured to:

[0254] Send a request message to the fourth network-side device to determine whether the first terminal is a subscribed terminal; the subscribed terminal is a terminal that can use the DNS service provided by the first network-side device;

[0255] The processing module 902 is specifically configured to: if the first terminal is a subscribed terminal, then insert an uplink classifier UL CL corresponding to the first DNS response.

[0256] The device in this embodiment can be used to execute the method in any of the method embodiments corresponding to the foregoing third network-side device. The specific implementation process and technical effects are similar to those in the method embodiment of the third network-side device. For details, reference can be made to the detailed description in the method embodiment corresponding to the third network-side device, which will not be elaborated here.

[0257] The DNS query device in the embodiments of the present application can be a device, a device or an electronic device with an operating system, or a component, an integrated circuit, or a chip in a terminal. The device or electronic 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. 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, etc. The embodiments of the present application do not make specific limitations.

[0258] The DNS query device provided in the embodiments of the present application can implement Figures 2 to 6 each process implemented by the method embodiment and achieve the same technical effects. To avoid repetition, it will not be elaborated here.

[0259] Optionally, as Figure 10 shown, the embodiments of the present application further provide a communication device 1000, including a processor 1001, a memory 1002, and a program or instruction stored on the memory 1002 and executable on the processor 1001. For example, when the communication device 1000 is a terminal, when the program or instruction is executed by the processor 1001, it implements each process of the foregoing DNS query method embodiment and can achieve the same technical effects. When the communication device 1000 is a network-side device, when the program or instruction is executed by the processor 1001, it implements each process of the foregoing DNS query method embodiment and can achieve the same technical effects. To avoid repetition, it will not be elaborated here.

[0260] An embodiment of the present application further provides a first network-side device, including a processor and a communication interface. The communication interface is configured to receive a first DNS query sent by a first terminal, and the processor is configured to perform target processing on the first DNS query according to a processing result corresponding to a second DNS query of a second terminal stored therein; wherein, the positions of the first terminal and the second terminal are within a target range. This embodiment of the first network-side device corresponds to the above-mentioned method embodiment of the first network-side device. Each implementation process and implementation manner of the above method embodiment can be applied to this embodiment of the first network-side device, and the same technical effect can be achieved.

[0261] Specifically, an embodiment of the present application further provides a network-side device. As Figure 11 shown, the network-side device 1100 includes: a processor 1101, a transceiver 1102, a memory 1103, a user interface 1104, and a bus interface, where:

[0262] In an embodiment of the present invention, the network-side device 1100 further includes: a computer program stored on the memory 1103 and executable on the processor 1101. The computer program is executed by the processor 1101 Figure 7 The methods executed by the shown modules achieve the same technical effects. To avoid repetition, they will not be described herein.

[0263] In Figure 11 the bus architecture may include any number of interconnected buses and bridges. Specifically, various circuits of one or more processors represented by the processor 1101 and the memory represented by the memory 1103 are linked together. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art. Therefore, they will not be further described herein. The bus interface provides an interface. The transceiver 1102 may be multiple components, that is, including a transmitter and a receiver, and provides a unit for communicating with various other devices on a transmission medium. For different user devices, the user interface 1104 may also be an interface capable of externally connecting or internally connecting required devices, and the connected devices include but are not limited to a keypad, a display, a speaker, a microphone, a joystick, etc.

[0264] The processor 1101 is responsible for managing the bus architecture and general processing, and the memory 1103 may store data used by the processor 1101 when performing operations.

[0265] An embodiment of the present application further provides a second network-side device, including a processor and a communication interface. The communication interface is configured to receive a first DNS query sent by a first network-side device; the first DNS query is sent according to a processing result corresponding to a second DNS query of a stored second terminal; the communication interface is further configured to send a first DNS response corresponding to the first DNS query to the first network-side device; wherein, positions of the first terminal and the second terminal are within a target range. This embodiment of the second network-side device corresponds to the above-mentioned method embodiment of the second network-side device. Each implementation process and implementation manner of the above method embodiment can be applied to this embodiment of the second network-side device, and the same technical effects can be achieved.

[0266] An embodiment of the present application further provides a third network-side device, including a processor and a communication interface. The communication interface is configured to receive notification information sent by the first network-side device, and the notification information is used to indicate triggering insertion of an uplink classifier UL CL corresponding to a first DNS response; the processor is configured to execute insertion of the uplink classifier UL CL corresponding to the first DNS response; wherein, the first DNS response is a DNS response corresponding to a first DNS query sent by a first terminal; non-insertion of the UL CL corresponding to the first DNS response indicates that there is no second DNS response, or the UL CL corresponding to the second DNS response is not inserted, where the second DNS response is the same as the first DNS response; or, an IP address in the second DNS response is the same as an IP address in the first DNS response, or an IP address segment in the second DNS response is the same as an IP address segment in the first DNS response. This embodiment of the third network-side device corresponds to the above-mentioned method embodiment of the third network-side device. Each implementation process and implementation manner of the above method embodiment can be applied to this embodiment of the third network-side device, and the same technical effects can be achieved.

[0267] An embodiment of the present application further provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, each process of the above-mentioned DNS query method embodiment is implemented, and the same technical effects can be achieved. To avoid repetition, details are not described here again.

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

[0269] Another embodiment of the present application further provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is configured to run programs or instructions to implement each process of the above DNS query method embodiment and can achieve the same technical effects. To avoid repetition, details are not described herein again.

[0270] It should be understood that the chip mentioned in the embodiments of the present application may also be referred to as a system-on-chip, system chip, chip system, or system-on-chip.

[0271] The embodiments of the present application further provide a computer program / program product, which is stored in a non-transitory storage medium. The program / program product is executed by at least one processor to implement each process of the above DNS query method embodiment and can achieve the same technical effects. To avoid repetition, details are not described herein again.

[0272] It should be noted that in this article, the terms "include", "comprise" or any other variant thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements not only includes those elements, but also includes other elements not expressly listed, or also includes elements inherent to such process, method, article or device. Without further limitation, an element defined by the statement "including a..." does not exclude the existence of additional identical elements in the process, method, article or device including that element. In addition, it should be pointed out that the methods and devices in the embodiments of the present application are not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in a reverse order according to the functions involved. For example, the described methods may be performed in an order different from that described, and various steps may be added, omitted, or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0273] Through the description of the above embodiments, those skilled in the art can clearly understand that the above embodiment methods can be implemented by means of software plus a necessary general hardware platform. Of course, they can also be implemented by hardware, but in many cases the former is a better embodiment. Based on such an understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art, can be embodied in the form of a computer software product. The computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions for causing a terminal (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of the present application.

[0274] The embodiments of the present application have been described above in conjunction with the accompanying drawings. However, the present application is not limited to the above specific embodiments. The above specific embodiments are merely illustrative and not restrictive. Under the inspiration of the present application, those of ordinary skill in the art can also make many forms without departing from the purpose of the present application and the scope protected by the claims, and all of them fall within the protection scope of the present application.

Claims

1. A Domain Name System (DNS) query method, characterized in that, Including: A first network-side device receives a first DNS query sent by a first terminal. The first network-side device performs target processing on the first DNS query according to a processing result corresponding to a second DNS query of a second terminal stored therein. Wherein, the first DNS query and the second DNS query are the same or similar, and / or, the positions of the first terminal and the second terminal are within a target range.

2. The DNS query method according to claim 1, wherein The processing result corresponding to the second DNS query includes: a second DNS response. The first network-side device performs target processing on the first DNS query according to a processing result corresponding to a second DNS query request of a second terminal stored therein, including: The first network-side device obtains a first DNS response corresponding to the first DNS query according to the second DNS response; the first DNS response includes at least one of the following: a first Internet Protocol (IP) address, a first Fully Qualified Domain Name (FQDN).

3. The DNS query method according to claim 2, wherein The first network-side device obtains a first DNS response corresponding to the first DNS query according to the second DNS response, including: The first network-side device uses the second DNS response as the first DNS response; or, The first network-side device generates the first DNS response according to parameters in the second DNS response; the second DNS response includes at least one of the following: a second IP address, a second FQDN.

4. The DNS query method according to claim 1, wherein The processing result corresponding to the second DNS query includes: a processing rule. The first network-side device performs target processing on the first DNS query according to a processing result corresponding to a second DNS query of a second terminal stored therein, including: The first network-side device sends the first DNS query to a second network-side device according to the processing rule. The first network-side device receives a first DNS response corresponding to the first DNS query sent by the second network-side device; the first DNS response includes at least one of the following: a first IP address, a first FQDN.

5. The DNS query method according to any one of claims 1-4, characterized in that, After performing the target processing on the first DNS query, the method further includes: The first network-side device determines whether an upstream classifier (UL CL) corresponding to the first DNS response corresponding to the first DNS query has been inserted. If not, the first network-side device sends a notification message to a third network-side device, and the notification message is used to indicate triggering the insertion of the UL CL corresponding to the first DNS response. If so, do not perform triggering the insertion of the UL CL corresponding to the first DNS response.

6. The DNS query method according to claim 5, wherein The first network-side device determines whether an upstream classifier (UL CL) corresponding to the first DNS response corresponding to the first DNS query has been inserted, including: The first network-side device determines whether there is a second DNS response, wherein the second DNS response is the same as the first DNS response; or the IP address in the second DNS response is the same as the IP address in the first DNS response, or the IP address segment in the second DNS response is the same as the IP address segment in the first DNS response. If there is the second DNS response, determine whether the uplink classifier UL CL corresponding to the second DNS response has been inserted.

7. The DNS query method according to any one of claims 1-4, wherein The positions of the second terminal and the first terminal are within a target range, including at least one of the following cases: The positions of the first terminal and the second terminal are in the same location area, and the being in the same location area includes at least one of the following: having the same data network access identifier DNAI, having the same tracking area identifier TAI, or having the same cell identifier Cell ID; or, The FQDN in the first DNS query of the first terminal is the same as the FQDN in the second DNS query of the second terminal; or, The FQDN in the first DNS query of the first terminal and the FQDN in the second DNS query of the second terminal belong to the same FQDN list; wherein, the FQDNs in the FQDN list or the DNS queries to which the FQDNs belong correspond to the same processing rules; The first terminal and the second terminal are both subscribed terminals; the subscribed terminal is a terminal that can use the DNS service provided by the first network-side device; Wherein, the second DNS query and its corresponding processing result have been cached in the first network-side device or the third network-side device.

8. The DNS query method according to any one of claims 1-4, characterized in that The method further includes: The first network-side device sends a request message to the fourth network-side device to determine whether the first terminal is a subscribed terminal; the subscribed terminal is a terminal that can use the DNS service provided by the first network-side device; If so, perform an operation of performing target processing on the first DNS query.

9. A Domain Name System (DNS) query method, characterized in that, Including: The second network-side device receives the first DNS query of the first terminal sent by the first network-side device; The first DNS query is sent according to the processing result corresponding to the second DNS query of the second terminal that has been stored; The second network-side device sends the first DNS response corresponding to the first DNS query to the first network-side device; Wherein, the first DNS query and the second DNS query are the same or similar, and / or, the positions of the first terminal and the second terminal are within a target range.

10. The DNS query method according to claim 9, wherein The first DNS response includes at least one of the following: the first Internet Protocol IP address, the first fully qualified domain name FQDN.

11. The DNS query method according to claim 9 or 10, wherein The positions of the second terminal and the first terminal are within a target range, including at least one of the following cases: The positions of the first terminal and the second terminal are in the same location area, and the being in the same location area includes at least one of the following: having the same data network access identifier DNAI, having the same tracking area identifier TAI, or having the same cell identifier Cell ID; or, The FQDN in the first DNS query of the first terminal is the same as the FQDN in the second DNS query of the second terminal; or, The FQDN in the first DNS query of the first terminal belongs to the same FQDN list as the FQDN in the second DNS query of the second terminal; wherein, the FQDN in the FQDN list or the DNS query corresponding to the FQDN corresponds to the same processing rule; The first terminal and the second terminal are both subscribed terminals; the subscribed terminal is a terminal capable of using the DNS service provided by the first network side device; Wherein, the second DNS query and its corresponding processing result have been cached in the first network side device or the third network side device.

12. A Domain Name System (DNS) query method, characterized in that, Including: The third network side device receives the notification information sent by the first network side device, and the notification information is used to indicate triggering the insertion of the uplink classifier UL CL corresponding to the first DNS response; The third network side device performs the insertion of the uplink classifier UL CL corresponding to the first DNS response; Wherein, the first DNS response is the DNS response corresponding to the first DNS query sent by the first terminal; the non-insertion of the UL CL corresponding to the first DNS response indicates the non-existence of the second DNS response, or the non-insertion of the UL CL corresponding to the second DNS response, wherein the second DNS response is the same as the first DNS response; or, the IP address in the second DNS response is the same as the IP address in the first DNS response, or the IP address segment in the second DNS response is the same as the IP address segment in the first DNS response; the second DNS response is the DNS response corresponding to the second DNS query sent by the second terminal; the first DNS query and the second DNS query are the same or similar, and / or, the positions of the first terminal and the second terminal are within the target range.

13. The DNS query method according to claim 12, wherein The first DNS response includes at least one of the following: the first Internet Protocol IP address, the first Fully Qualified Domain Name FQDN.

14. The DNS query method according to claim 12, wherein The positions of the second terminal and the first terminal being within the target range includes at least one of the following situations: The positions of the first terminal and the second terminal are in the same location area, and the being in the same location area includes at least one of the following: having the same Data Network Access Identifier DNAI, having the same Tracking Area Identifier TAI or having the same Cell ID; or, The FQDN in the first DNS query of the first terminal is the same as the FQDN in the second DNS query of the second terminal; or, The FQDN in the first DNS query of the first terminal belongs to the same FQDN list as the FQDN in the second DNS query of the second terminal; wherein, the FQDN in the FQDN list or the DNS query corresponding to the FQDN corresponds to the same processing rule; The first terminal and the second terminal are both subscribed terminals; the subscribed terminal is a terminal capable of using the DNS service provided by the first network side device; Among them, the second DNS query and its corresponding processing result have been cached in the first network-side device or the third network-side device; the processing result includes at least one of the following: a second DNS response or a processing rule.

15. The DNS query method according to claim 12, wherein The method further includes: The third network-side device sends a request message to the fourth network-side device to determine whether the first terminal is a subscribed terminal; the subscribed terminal is a terminal that can use the DNS service provided by the first network-side device; If so, the third network-side device performs the insertion of the uplink classifier UL CL corresponding to the first DNS response.

16. A Domain Name System (DNS) query device, characterized in that, It includes: A receiving module, configured to receive a first DNS query sent by a first terminal; A processing module, configured to perform target processing on the first DNS query according to the processing result corresponding to the second DNS query of the second terminal that has been stored; Among them, the first DNS query and the second DNS query are the same or similar, and / or, the positions of the first terminal and the second terminal are within a target range.

17. The DNS query device according to claim 16, wherein The processing result corresponding to the second DNS query includes: a second DNS response; The processing module is specifically configured to: Obtain a first DNS response corresponding to the first DNS query according to the second DNS response; the first DNS response includes at least one of the following: a first Internet Protocol IP address, a first Fully Qualified Domain Name FQDN.

18. The DNS query device according to claim 17, wherein The processing module is specifically configured to: Use the second DNS response as the first DNS response; or, Generate the first DNS response according to the parameters in the second DNS response; the second DNS response includes at least one of the following: a second IP address, a second FQDN.

19. The DNS query device according to claim 16, wherein The processing result corresponding to the second DNS query includes: a processing rule; The apparatus further includes: A sending module, configured to send the first DNS query to the second network-side device according to the processing rule; The receiving module, configured to receive the first DNS response corresponding to the first DNS query sent by the second network-side device; the first DNS response includes at least one of the following: a first IP address, a first FQDN.

20. The DNS query device according to any one of claims 16-19, characterized in that, The processing module is further configured to: Determine whether the uplink classifier UL CL corresponding to the first DNS response corresponding to the first DNS query has been inserted; If so, do not perform the insertion of the UL CL triggering the first DNS response; The sending module is further configured to, if the processing module determines that the UL CL has not been inserted, send a notification message to the third network-side device, where the notification message is used to indicate triggering the insertion of the uplink classifier UL CL corresponding to the first DNS response.

21. The DNS query device according to claim 20, wherein The processing module is specifically configured to: Determine whether there is a second DNS response, where the second DNS response is the same as the first DNS response; or, the IP address in the second DNS response is the same as the IP address in the first DNS response, or, the IP address segment in the second DNS response is the same as the IP address segment in the first DNS response; If there is the second DNS response, determine whether the uplink classifier UL CL corresponding to the second DNS response has been inserted.

22. The DNS query device according to any one of claims 16-19, characterized in that The positions of the second terminal and the first terminal are within a target range, including at least one of the following cases: The positions of the first terminal and the second terminal are in the same location area, and the being in the same location area includes at least one of the following: having the same data network access identifier DNAI, having the same tracking area identifier TAI, or having the same cell identifier Cell ID; or, The FQDN in the first DNS query of the first terminal is the same as the FQDN in the second DNS query of the second terminal; or, The FQDN in the first DNS query of the first terminal and the FQDN in the second DNS query of the second terminal belong to the same FQDN list; wherein, the FQDNs in the FQDN list or the DNS queries to which the FQDNs belong correspond to the same processing rules; Both the first terminal and the second terminal are subscribed terminals; the subscribed terminal is a terminal capable of using the DNS service provided by the first network-side device; Wherein, the second DNS query and its corresponding processing result have been cached in the first network-side device or the third network-side device.

23. The DNS query device according to any one of claims 16-19, characterized in that, The sending module is further configured to: Send a request message to the fourth network-side device to determine whether the first terminal is a subscribed terminal; the subscribed terminal is a terminal capable of using the DNS service provided by the first network-side device; The processing module is configured to, if the first terminal is a subscribed terminal, perform an operation of performing target processing on the first DNS query.

24. A Domain Name System (DNS) query device, characterized in that, Including: A receiving module, configured to receive a first DNS query of a first terminal sent by a first network-side device; The first DNS query is sent according to the processing result corresponding to the second DNS query of the second terminal that has been stored; A sending module, configured to send a first DNS response corresponding to the first DNS query to the first network-side device; Wherein, the first DNS query and the second DNS query are the same or similar, and / or, the positions of the first terminal and the second terminal are within a target range.

25. The DNS query device according to claim 24, characterized in that The positions of the second terminal and the first terminal are within a target range, including at least one of the following cases: The positions of the first terminal and the second terminal are in the same location area, and the being in the same location area includes at least one of the following: having the same data network access identifier DNAI, having the same tracking area identifier TAI, or having the same cell identifier Cell ID; or, The FQDN in the first DNS query of the first terminal is the same as the FQDN in the second DNS query of the second terminal; or, The FQDN in the first DNS query of the first terminal and the FQDN in the second DNS query of the second terminal belong to the same FQDN list; wherein, the FQDN in the FQDN list or the DNS query corresponding to the FQDN corresponds to the same processing rule; The first terminal and the second terminal are both subscribed terminals; the subscribed terminal is a terminal capable of using the DNS service provided by the first network-side device; Wherein, the second DNS query and its corresponding processing result have been cached in the first network-side device or the third network-side device.

26. A Domain Name System (DNS) query device, characterized in that, Comprising: A receiving module, configured to receive notification information sent by a first network-side device, where the notification information is used to indicate triggering the insertion of an uplink classifier UL CL corresponding to a first DNS response; A processing module, configured to perform the insertion of an uplink classifier UL CL corresponding to a first DNS response; Wherein, the first DNS response is a DNS response corresponding to a first DNS query sent by a first terminal; the non-insertion of the UL CL corresponding to the first DNS response indicates the non-existence of a second DNS response, or the non-insertion of the UL CL corresponding to the second DNS response, where the second DNS response is the same as the first DNS response; or, the IP address in the second DNS response is the same as the IP address in the first DNS response, or the IP address segment in the second DNS response is the same as the IP address segment in the first DNS response; the second DNS response is a DNS response corresponding to a second DNS query sent by a second terminal; the first DNS query and the second DNS query are the same or similar, and / or, the positions of the first terminal and the second terminal are within a target range.

27. The DNS query device according to claim 26, wherein The first DNS response includes at least one of the following: a first Internet Protocol IP address, a first Fully Qualified Domain Name FQDN.

28. The DNS query device according to claim 26, wherein The positions of the second terminal and the first terminal being within a target range includes at least one of the following situations: The positions of the first terminal and the second terminal are in the same location area, and the being in the same location area includes at least one of the following: having the same Data Network Access Identifier DNAI, having the same Tracking Area Identifier TAI, or having the same Cell ID; or, The FQDN in the first DNS query of the first terminal is the same as the FQDN in the second DNS query of the second terminal; or, The FQDN in the first DNS query of the first terminal and the FQDN in the second DNS query of the second terminal belong to the same FQDN list; wherein, the FQDN in the FQDN list or the DNS query corresponding to the FQDN corresponds to the same processing rule; The first terminal and the second terminal are both subscribed terminals; the subscribed terminal is a terminal capable of using the DNS service provided by the first network-side device; Among them, the second DNS query and its corresponding processing result have been cached in the first network-side device or the third network-side device; the processing result includes at least one of the following: a second DNS response or a processing rule.

29. The DNS query device according to claim 26, wherein The device further includes: a sending module, configured to send a request message to a fourth network-side device to determine whether the first terminal is a subscribed terminal; the subscribed terminal is a terminal capable of using the DNS service provided by the first network-side device; a processing module, specifically configured to: if the first terminal is a subscribed terminal, then perform the insertion of an uplink classifier UL CL corresponding to the first DNS response.

30. A first network-side device, characterized in that, It includes a processor, a memory, and a program or instruction stored on the memory and executable on the processor. When the program or instruction is executed by the processor, the steps of the Domain Name System (DNS) query method according to any one of claims 1 to 8 are implemented.

31. A second network-side device, characterized in that, It includes a processor, a memory, and a program or instruction stored on the memory and executable on the processor. When the program or instruction is executed by the processor, the steps of the Domain Name System (DNS) query method according to any one of claims 9 to 11 are implemented.

32. A third network-side device, characterized in that, It includes a processor, a memory, and a program or instruction stored on the memory and executable on the processor. When the program or instruction is executed by the processor, the steps of the Domain Name System (DNS) query method according to any one of claims 12 to 15 are implemented.

33. A readable storage medium, characterized in that, A program or instruction is stored on the readable storage medium. When the program or instruction is executed by a processor, the steps of the DNS query method according to any one of claims 1 to 8 are implemented, or the steps of the DNS query method according to any one of claims 9 to 11 are implemented, or the steps of the DNS query method according to any one of claims 12 to 15 are implemented.

Images