DNS configuration processing method, device, communication equipment and readable storage medium

Abstract

The present application discloses a method, device, communication device and readable storage medium for processing DNS configuration, which belongs to the field of communication technology. The method for processing DNS configuration includes: a first communication device obtains an operator DNS configuration from a second communication device; the first communication device uses the operator DNS configuration to perform a DNS query operation or a domain name resolution operation; wherein the first communication device includes at least one of the following: an application client, an edge enabling client EEC; the second communication device is an edge enabling server EES or an application function AF.

Description

Technical Field

[0001] The present application belongs to the field of communication technology, and specifically relates to a DNS configuration processing method, device, communication equipment and readable storage medium. Background Art

[0002] Edge Application Server Discovery Function (EASDF) is a core network element that can be used to process Domain Name System (DNS) query requests sent by terminals. Currently, operators have a demand that, when the operator deploys EASDF, the application (Application, APP) or application client (Application Client, AC) on the terminal can use EASDF for DNS query or domain name resolution. Alternatively, the operator's demand is that the application or application client on the terminal can use the DNS server specified by the operator for DNS query or domain name resolution (the DNS server specified by the operator will not be limited to EASDF).

[0003] In the related art, the APP or AC on the terminal obtains the DNS configuration from the operating system (OS) of the terminal, or the APP or AC sends a fully qualified domain name FQDN (Fully Qualified Domain Name) for the terminal OS to resolve. However, there is such a mechanism in the terminal at present. If the OS includes a user-specified DNS configuration, even if the OS includes both the DNS configuration sent by the network side (the DNS configuration sent by the network side may be provided by the operator, i.e., the operator DNS configuration) and the user-specified DNS configuration, the OS may directly use the user-specified DNS configuration for DNS query or domain name resolution. In this way, the application or application client will be unable to use the DNS configuration sent by the network side, which will lead to low flexibility in DNS query or domain name resolution. Summary of the invention

[0004] The embodiments of the present application provide a method, apparatus, communication device and readable storage medium for processing a DNS configuration, which can solve the problem in the prior art that the flexibility of DNS query or domain name resolution is low because the application or application client cannot use the DNS configuration sent by the network side.

[0005] In a first aspect, a method for processing a DNS configuration is provided, comprising:

[0006] The first communication device obtains the operator DNS configuration from the second communication device;

[0007] The first communication device uses the operator DNS configuration to perform a DNS query operation or a domain name resolution operation;

[0008] The first communication device includes at least one of the following: an application client, an edge enabling client EEC; the second communication device is an edge enabling server EES or an application function AF.

[0009] In a second aspect, a method for processing a DNS configuration is provided, including:

[0010] The second communication device sends the operator DNS configuration to the first communication device;

[0011] The first communication device is an application client or an EEC; the second communication device is an EES or an AF.

[0012] In a third aspect, a method for processing DNS configuration is provided, including:

[0013] The third communication device sends the operator DNS configuration to the AF.

[0014] In a fourth aspect, a DNS configuration processing device is provided, including:

[0015] A first acquisition module, used to acquire the operator DNS configuration from the second communication device;

[0016] An execution module, used to use the operator's DNS configuration to perform a DNS query operation or a domain name resolution operation;

[0017] The first communication device includes at least one of the following: an application client, an edge enabling client EEC; the second communication device is an edge enabling server EES or an application function AF.

[0018] In a fifth aspect, a DNS configuration processing device is provided, including:

[0019] A first sending module, used for the second communication device to send the operator DNS configuration to the first communication device;

[0020] The first communication device is an application client or an EEC; the second communication device is an EES or an AF.

[0021] In a sixth aspect, a DNS configuration processing device is provided, including:

[0022] The second sending module is used to send the operator DNS configuration to the AF.

[0023] In the seventh aspect, a communication device is provided, which terminal includes a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the method described in the first aspect, or implements the steps of the method described in the second aspect, or implements the steps of the method described in the third aspect.

[0024] In an eighth aspect, a communication device is provided, including a processor and a communication interface, wherein:

[0025] The communication interface is used to obtain the operator DNS configuration from the second communication device; the processor is used to use the operator DNS configuration to perform a DNS query operation or a domain name resolution operation; wherein the first communication device includes at least one of the following: an application client, an edge enabling client EEC; the second communication device is an edge enabling server EES or an application function AF; or,

[0026] The communication interface is used to send the operator DNS configuration to the first communication device; wherein the first communication device is an application client or EEC; the second communication device is EES or AF; or,

[0027] The communication interface is used to send the operator DNS configuration to the AF.

[0028] In the ninth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method described in the second aspect are implemented, or the steps of the method described in the third aspect are implemented.

[0029] In the tenth aspect, a chip is provided, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instructions to implement 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.

[0030] In the eleventh aspect, a computer program / program product is provided, which is stored in a non-volatile storage medium, and the program / program product is executed by at least one processor to implement 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.

[0031] In an embodiment of the present application, the first communication device can obtain the operator DNS configuration from the second communication device, and use the operator DNS configuration to perform a DNS query operation or a domain name resolution operation, thereby improving the flexibility of the DNS query or domain name resolution. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] Figure 1 is a schematic diagram of a wireless communication system provided in an embodiment of the present application;

[0033] Figure 2 It is one of the flow charts of the processing method of DNS configuration provided in the embodiment of the present application;

[0034] Figure 3 This is the second flowchart of the method for processing DNS configuration provided in the embodiment of the present application;

[0035] Figure 4 This is the third flowchart of the DNS configuration processing method provided in the embodiment of the present application;

[0036] Figure 5 This is the fourth flowchart of the DNS configuration processing method provided in the embodiment of the present application;

[0037] Figure 6 This is the fifth flowchart of the DNS configuration processing method provided in the embodiment of the present application;

[0038] Figure 7 This is the sixth flowchart of the method for processing DNS configuration provided in the embodiment of the present application;

[0039] Figure 8 This is the seventh flowchart of the method for processing DNS configuration provided in the embodiment of the present application;

[0040] Fig. 9 It is one of the structural diagrams of the processing device of the DNS configuration provided in the embodiment of the present application;

[0041] Fig.10 This is the second structural diagram of the DNS configuration processing device provided in the embodiment of the present application;

[0042] Fig.11 This is the third structural diagram of the processing device for DNS configuration provided in the embodiment of the present application;

[0043] Fig.12 It is one of the structural diagrams of the communication device provided in the embodiment of the present application;

[0044] Fig.13 This is the second structural diagram of the communication device provided in the embodiment of the present application. DETAILED DESCRIPTION

[0045] The following will be combined with the drawings in the embodiments of the present application to clearly describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field belong to the scope of protection of this application.

[0046] The terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first" and "second" are generally of the same type, and the number of objects is not limited. For example, the first object can be one or more. In addition, "and / or" in the specification and claims represents at least one of the connected objects, and the character " / " generally represents that the objects associated with each other are in an "or" relationship.

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

[0048] Figure 11 is a schematic diagram of a wireless communication system provided in an embodiment of the present application. The wireless communication system may include a first communication device 11, a second communication device 12 and a third communication device 13.

[0049] In the embodiment of the present application, the first communication device 11 can be any device that can perform DNS query or domain name resolution. Optionally, the first communication device 11 can be a terminal (also referred to as user equipment (UE)), an edge enabler client (EEC), an APP or an AC, etc. The EEC, APP or AC can be deployed in the terminal. In the embodiment of the present application, AC and APP can be equivalently replaced.

[0050] The second communication device 12 may be any device that can provide the operator DNS configuration for the first communication device 11. Optionally, the second communication device may be an edge enabler server (EES) or an application function (AF), etc. EES, AF, etc. may be deployed in a data network (DN).

[0051] In specific implementation, in one implementation, the second communication device 12 can provide the operator DNS configuration by itself, and the operator DNS configuration is transmitted between the second communication device 12 and the first communication device 11. In another implementation, the second communication device 12 can obtain the operator DNS configuration from the third communication device 13. In this case, the second communication device 12 can be understood as a third party, and the operator DNS configuration is transmitted from the third communication device 13 to the first communication device 11.

[0052] The third communication device 13 may be a core network device, such as a fifth generation core network (5 th Optionally, the third communication device 13 may be a session management function (SMF), an access and mobility management function (AMF) or a network exposure function (NEF).

[0053] In the embodiment of the present application, the terminal can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer) or a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a handheld computer, a netbook, an ultra-mobile personal computer (ultra-mobile personal computer, UMPC), a mobile Internet device (Mobile Internet Device, MID), augmented reality (augmentedreality, AR) / virtual reality (virtual reality, VR) equipment, a robot, a wearable device (WearableDevice), a vehicle-mounted equipment (VUE), a pedestrian terminal (PUE), a smart home (home appliances with wireless communication functions, such as refrigerators, televisions, washing machines or furniture, etc.) and other terminal-side devices, and wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, game consoles, etc.

[0054] For ease of understanding, some contents involved in the embodiments of the present application are described below:

[0055] EASDF is a core network element that can be used to process DNS query requests sent by UE. EASDF can also be understood as a local DNS resolver (Local DNS Resolver, LDNSR).

[0056] EASDF is a network element used to process DNS queries sent by UE. UE can send DNS queries to EASDF, and then EASDF determines whether to send the DNS query to the central DNS (C-DNS) or the local DNS (L-DNS) based on the DNS query, and then sends the Fully Qualified Domain Name (FQDN) and other information in the DNS query to the Session Management Function (SMF). SMF provides EASDF with the Internet Protocol (IP) address or port number of the corresponding DNS server, such as C-DNS or L-DNS; then, after C-DNS or L-DNS finds the IP address corresponding to the FQDN, it sends it to EASDF, and EASDF saves the query result to SMF and then sends it to UE. In this way, UE obtains the server IP address of the requested FQDN.

[0057] The embodiments of the present application are described in detail below through some embodiments and their application scenarios in conjunction with the accompanying drawings.

[0058] See also Figure 2 , Figure 2 This is one of the flow charts of the method for processing DNS configuration provided by the embodiment of the present application. Figure 2 As shown, the method for processing DNS configuration may include the following steps:

[0059] Step 201: The first communication device obtains the operator DNS configuration from the second communication device.

[0060] In specific implementation, when the first communication device needs to perform a DNS query operation or a domain name resolution operation, in a first implementation method, the first communication device can directly execute step 201 to use the operator's DNS configuration to perform a DNS query operation or a domain name resolution operation; in a second implementation method, the first communication device can first determine whether it is necessary to use the operator's DNS configuration. If it is necessary to use the operator's DNS configuration, step 201 can be executed to use the operator's DNS configuration to perform a DNS query operation or a domain name resolution operation.

[0061] In the above second implementation, if the first communication device does not need to use the operator DNS configuration, any DNS configuration can be obtained from the OS of the first communication device, and the DNS configuration can be used to perform a DNS query operation or a domain name resolution operation. It can be understood that the DNS configuration obtained from the OS of the first communication device may be a user-specified DNS configuration or an operator DNS configuration.

[0062] It can be seen that compared with the prior art, which can only use the DNS configuration obtained from the OS to perform DNS query operations or domain name resolution operations, and the DNS configuration obtained from the OS cannot be guaranteed to be the configuration provided by the operator. The embodiment of the present application can use the operator DNS configuration obtained from the second communication device to perform DNS query operations or domain name resolution operations, thereby improving the flexibility of DNS query or domain name resolution.

[0063] During implementation, the second communication device may actively send the operator DNS configuration to the first communication device, or may send the operator DNS configuration to the first communication device based on a request from the first communication device.

[0064] When the second communication device determines to send the operator DNS configuration to the first communication device, the operator DNS configuration can be sent through signaling or protocol data unit (PDU) session or other methods. The specific method can be determined based on actual conditions, and the embodiments of the present application do not limit this.

[0065] In an embodiment of the present application, optionally, the operator DNS configuration may include at least one of the following items of the DNS server specified by the operator: an Internet Protocol IP address; a port number.

[0066] The DNS server designated by the operator can be understood as: a DNS server determined by the operator, or a DNS server that the operator expects the terminal to use. The DNS server designated by the operator can be EASDF, or can be another DNS server designated by the operator.

[0067] Step 202: The first communication device uses the operator's DNS configuration to perform a DNS query operation or a domain name resolution operation.

[0068] The first communication device includes at least one of the following: an application client, an edge enabling client EEC; the second communication device is an edge enabling server EES or an application function AF.

[0069] It should be noted that the specific implementation of the first communication device using the operator's DNS configuration to perform a DNS query operation or a domain name resolution operation can refer to the implementation method of using the DNS configuration to perform a DNS query operation or a domain name resolution operation in the related art, for example, the first communication device directly sends a DNS query to the DNS server whose destination IP address and port number are configured by the operator; or after the first communication device confirms that it is the operator's DNS configuration, it only sends the FQDN to be queried or the domain name resolution, and the terminal is responsible for forwarding. Therefore, it is not described here.

[0070] In the DNS configuration processing method of the present application, the first communication device can obtain the operator DNS configuration from the second communication device, and use the operator DNS configuration to perform a DNS query operation or a domain name resolution operation, thereby improving the flexibility of the DNS query or domain name resolution.

[0071] The specific implementation of step 201 is described below. Step 201 can be implemented by, but is not limited to, the following method 1 and method 2:

[0072] Method 1

[0073] Optionally, the first communication device includes an application client and an EEC, and the second communication device is an EES;

[0074] The first communication device obtains the operator DNS configuration from the second communication device, including:

[0075] The EEC sends a first request message to the EES, where the first request message is used to request the operator DNS configuration;

[0076] The EEC receives the operator DNS configuration sent by the EES;

[0077] The EEC sends the operator DNS configuration to the application client.

[0078] In the first method, when the first communication device needs to perform a DNS query operation or a domain name resolution operation, it can send first request information for requesting the operator's DNS configuration, that is, a DNS configuration request, to the second communication device.

[0079] The second communication device may send the operator DNS configuration to the first communication device in response to the request. Optionally, before sending the operator DNS configuration to the first communication device, the second communication device may verify the legitimacy of the first request information, such as whether the first communication device is qualified to communicate with the second communication device, etc. The operator DNS configuration is sent to the first communication device only if the verification is passed. Otherwise, the operator DNS configuration may not be sent to the first communication device to improve the security of DNS configuration processing.

[0080] After receiving the operator DNS configuration, the first communication device may forward the operator DNS configuration to the application client so that the application client uses the operator DNS configuration to perform DNS query or domain name resolution. The application client may be deployed on the first communication device or on other communication devices. When the application client is deployed on the first communication device, the module that interacts with the second communication device may be other modules in the first communication device other than the application client, such as EEC.

[0081] Optionally, the first communication device includes an EEC and an APP (or AC), and the second communication device may be an EES. Figure 3 As shown, the method for processing DNS configuration may include the following steps:

[0082] Step 301: EEC sends a first request message to EES.

[0083] Step 302: EES verifies the legitimacy of the first request information (Authorization Check).

[0084] If the verification is successful, that is, the first request information is legal, step 303 may be executed; if the verification is unsuccessful, that is, the first request information is illegal, the process may be terminated.

[0085] Step 303: EES sends the operator DNS configuration to EEC.

[0086] Step 304: EEC sends the operator DNS configuration to APP (or AC).

[0087] In method 1, optionally, the first request information may include at least one of the following: location information of the first communication device; identification information of the application client; identification information of the first communication device; and indication information, wherein the indication information is used to indicate that the first communication device requests to obtain the operator DNS configuration.

[0088] The application client may obtain the operator DNS configuration from the first communication device in any of the following ways:

[0089] 1) The application client receives the operator DNS configuration sent by the EEC;

[0090] 2) The application client obtains the operator's DNS configuration by calling the first interface;

[0091] 3) The application client uses the operator DNS configuration by calling the first interface;

[0092] The first interface is an interface between the application client and the EEC, such as an application programming interface (API) interface.

[0093] In 1), the EEC may actively send the operator DNS configuration to the application client. In specific implementation, the operator DNS configuration may be carried in the signaling and sent.

[0094] In 2) and 3), the EEC may send the operator DNS configuration to the application client based on the application client's call to the first interface. In specific implementation, the application client may request to obtain the operator DNS configuration through the first interface, and the EEC may respond to the request and send the operator DNS configuration through the first interface, or may not respond to the request and not send the operator DNS configuration. The specific decision may be based on actual conditions, and this embodiment of the application does not limit this.

[0095] The difference between 2) and 3) is that in 2), the application client obtains the operator's DNS configuration through the API interface. But in 3), the application client sends the FQDN to be resolved or queried through the API interface, and the terminal's OS can select the operator's DNS configuration corresponding to the called interface for DNS resolution.

[0096] In 2) and 3), optionally, the EEC sends the operator DNS configuration to the application client, which is specifically manifested as: the EEC sends the operator DNS configuration to the application client through the first interface.

[0097] Method 2

[0098] Optionally, the first communication device includes an application client, and the second communication device is an AF;

[0099] The application client and the AF obtain the operator DNS configuration, including:

[0100] The first communication device establishes a protocol data unit (PDU) session with the second communication device;

[0101] The application client receives the operator DNS configuration sent by the AF through the PDU session.

[0102] In the second method, a PDU session is established between the first communication device and the second communication device, and the operator's DNS configuration is transmitted through the PDU session.

[0103] In the second mode, optionally, before the second communication device sends the operator DNS configuration to the first communication device, it can first obtain the operator DNS configuration from the third communication device. In this case, the second communication device can be regarded as a third party, which is used to realize the transmission of the operator DNS configuration between the third communication device and the first communication device.

[0104] In specific implementation, the second communication device can obtain the operator DNS configuration from the third communication device by means of signaling or a second interface, wherein the second interface is the interface between the third communication device and the second communication device, for example, the interface between the core network element NEF and AF, and the traffic impact notification (Nnef_TrafficInfluence_Notify) signaling provided by the NEF network element is used to send the operator DNS configuration, and the interface between the core network element SMF, AMF, etc. and AF, and the event open notification (Nsmf_EventExposure_Notify) signaling provided by SMF is used to send the operator DNS configuration. The specific details can be determined according to the actual situation, and the embodiment of the present application does not limit this.

[0105] Optionally, the second interface may be an open application programming interface framework (Common API Framework, CAPIF). In this case, it can be understood that the API architecture of CAPIF is reused, and the first capability is added to the API architecture, where the first capability is the capability of supporting sending the operator DNS configuration.

[0106] When the third communication device sends the operator DNS configuration to the second communication device through the second interface, before sending the operator DNS configuration to the second communication device through the second interface, the third communication device can perform the registration process of the second interface, that is, the third communication device can publish the calling information of the second interface, and the calling information is used to instruct the second interface to open the first capability to the second communication device in the form of capability opening, that is, the second interface supports sending DNS configuration.

[0107] The second communication device may support discovering an API interface with the first capability. Before the second communication device calls and sends the operator DNS configuration through the second interface, the second communication device may first discover that the second interface supports the first capability. That is, the second communication device requests the operator DNS configuration through the second interface only after discovering that the second interface supports the first capability, so that the success rate of DNS configuration acquisition can be improved.

[0108] In the second mode, optionally, the first communication device may be an APP (or AC), the second communication device may be an AF, and the third communication device may be a core network device, such as SMF, AMF, NEF, etc. In this case, Figure 4 As shown, the method for processing DNS configuration may include the following steps:

[0109] Step 401: The core network device sends the operator DNS configuration to the AF.

[0110] In one implementation, the SMF may send the operator DNS configuration to the AF via Nsmf_EventExposure_Notify signaling.

[0111] In another implementation manner: the SMF may send the operator DNS configuration to the NEF via the Nsmf_EventExposure_Notify signaling, and then the NEF may send the operator DNS configuration to the AF via the Nnef_TrafficInfluence_Notify signaling.

[0112] Step 402: AF establishes a PDU session with APP.

[0113] That is, AF establishes a user plane connection with APP (deployed on UE).

[0114] Step 403: AF sends the operator's DNS configuration to APP.

[0115] See also Figure 5 , Figure 5 This is the fourth flow chart of the method for processing DNS configuration provided by the embodiment of the present application. Figure 5 As shown, the method for processing DNS configuration may include the following steps:

[0116] Step 501: The second communication device sends the operator DNS configuration to the first communication device.

[0117] The first communication device is an application client or an EEC; the second communication device is an EES or an AF.

[0118] In the DNS configuration processing method of this embodiment, the second communication device sends the operator DNS configuration to the first communication device, so that the first communication device can use the operator DNS configuration obtained from the second communication device to perform DNS query operations or domain name resolution operations, thereby improving the flexibility of DNS query or domain name resolution.

[0119] Optionally, the first communication device is an EEC, and the second communication device is an EES;

[0120] Before the second communication device sends the operator DNS configuration to the first communication device, the method further includes:

[0121] The EES receives first request information sent by the EEC, where the first request information is used to request operator DNS configuration.

[0122] Optionally, the first request information includes at least one of the following: location information of the first communication device; identification information of the application client; identification information of the first communication device.

[0123] Optionally, the first communication device is an application client, and the second communication device is an AF;

[0124] The second communication device sends the operator DNS configuration to the first communication device, including:

[0125] The AF establishes a PDU session with the application client;

[0126] The AF sends the operator DNS configuration to the application client through the PDU session.

[0127] Optionally, the second communication device is AF;

[0128] Before the second communication device sends the operator DNS configuration to the first communication device, the method further includes:

[0129] The AF obtains the operator DNS configuration from the third communication device.

[0130] Optionally, the AF obtains the operator DNS configuration from the third communication device, including:

[0131] The AF receives the operator DNS configuration sent by the third communication device; or,

[0132] The AF obtains the operator DNS configuration by calling a second interface, where the second interface is an interface between the third communication device and the AF.

[0133] Optionally, before the AF calls the second interface to obtain the operator DNS configuration, the method further includes:

[0134] The AF discovers that the second interface supports sending the operator DNS configuration.

[0135] Optionally, the operator DNS configuration includes at least one of the following items of the DNS server specified by the operator: an IP address; a port number.

[0136] It should be noted that this embodiment is Figure 2 The embodiment of the second communication device corresponding to the method embodiment, therefore, can refer to Figure 2 The relevant descriptions in the method embodiment can achieve the same beneficial effects. In order to avoid repeated descriptions, they will not be repeated here.

[0137] See also Figure 6 , Figure 6 This is the fifth flow chart of the method for processing DNS configuration provided by the embodiment of the present application. Figure 6 As shown, the method for processing DNS configuration may include the following steps:

[0138] Step 601: The third communication device sends the operator DNS configuration to the AF.

[0139] In the method for processing the DNS configuration of this embodiment, the third communication device sends the operator DNS configuration to the AF. In this way, the AF can forward the operator DNS configuration to the first communication device, so that the first communication device can use the operator DNS configuration obtained from the second communication device to perform a DNS query operation or a domain name resolution operation, thereby improving the flexibility of the DNS query or domain name resolution.

[0140] Optionally, the third communication device sends the operator DNS configuration to the AF, including:

[0141] The third communication device sends the operator DNS configuration to the AF through the second interface;

[0142] The second interface is an interface between the third communication device and the AF.

[0143] Optionally, before the third communication device sends the operator DNS configuration to the AF through the second interface, the method includes:

[0144] The third communication device publishes calling information of the second interface, where the calling information is used to indicate that the second interface supports sending the operator DNS configuration.

[0145] Optionally, the operator DNS configuration includes at least one of the following items of the DNS server specified by the operator: an IP address; a port number.

[0146] It should be noted that this embodiment is Figure 2 The embodiment of the third communication device corresponding to the method embodiment, therefore, can refer to Figure 2 The relevant descriptions in the method embodiment can achieve the same beneficial effects. In order to avoid repeated descriptions, they will not be repeated here.

[0147] It should be noted that the various optional implementations introduced in the embodiments of the present application can be implemented in combination with each other or can be implemented separately, and the embodiments of the present application are not limited to this.

[0148] For ease of understanding, the following examples are provided:

[0149] The embodiment of the present application can realize the provision of the operator's DNS configuration to the application client.

[0150] This can be achieved in two ways:

[0151] Method 1: Use EEC to provide the operator's DNS configuration to the application.

[0152] In method 1, the EEC module can be used. EEC provides an API interface to the application client. When the application wants to use the operator's DNS server address, it can call the API interface. Subsequent DNS queries and domain name resolution can use this DNS server address.

[0153] For easier understanding, please refer to Figure 7 .like Figure 7 As shown, EES can send the operator DNS configuration (DNS configuration from MNO, MNO DNS) to EEC. Then, EEC provides an API interface (API interface corresponding to EEC (API from EEC)) to the application. If the application wants to use the operator DNS configuration, it calls the API interface provided by EEC (If UE want to use MNO DNS, it triggers the API from EEC) to obtain the operator DNS configuration.

[0154] If the application does not want to use the operator DNS configuration, it can call the interface between the application and the UE OS (the API interface corresponding to the UE OS (API from UE OS)) to obtain the DNS configuration in the UE OS (DNS configuration in UE OS).

[0155] Method 2: Use the capability exposure interface to open DNS configuration.

[0156] In method 2, 5GC can send the operator's DNS configuration to AF through the CAPIF capability exposure interface, and then let AF send the operator's DNS configuration to the APP on the UE through the PDU session between AF and the UE application client. In this way, if the application wants to use the operator's configuration, it can use the DNS configuration sent by AF for subsequent domain name resolution or DNS query.

[0157] For easier understanding, please refer to Figure 8 .like Figure 8 As shown in the figure, the NEF of 5GC can send the operator DNS configuration to AF through the CAPIF capability exposure interface. After AF obtains the operator DNS configuration, it can send the IP address to the application client on the UE through the PDU session.

[0158] In this way, if the client wants to use the operator's DNS configuration, it can directly use the address sent by AF to perform DNS query or domain name resolution.

[0159] In method 2, NEF services are reused, and 5GC opens MNO DNS to AF through NEF.

[0160] The AF here may be a third-party one, such as Tencent's AF. Tencent's AF can call the CAPIF interface of 5GC to obtain the operator's DNS; 5GC can also provide MNO DNS to AF through NEF; then Tencent AF can establish a connection with the Tencent client on the UE and send the operator's DNS configuration to the APP. If the application wants to use the operator's DNS configuration, it can call and trigger it by itself.

[0161] In the embodiment of the present application, the first communication device may be: an application client, an EEC. The application client may obtain the MNO DNS from the AF. The EEC may obtain the MNO DNS from the EES.

[0162] The second communication device may be AF. AF may obtain MNO DNS from 5GC (such as NEF). Optionally, AF may call CAPIF to obtain MNO DNS from 5GC, but is not limited thereto. AF may establish a PDU session with the first communication device and then send MNO DNS to APP.

[0163] The third communication device may be a 5G core network device, such as NEF, SMF, etc. The third communication device may provide MNODNS to the AF.

[0164] Example 1: EEC process. For details, please refer to Figure 3 .

[0165] like Figure 3 As shown, the EEC on the UE can request the EES to send the operator DNS configuration. The operator DNS configuration may include the IP address of the DNS server specified by the operator, such as the IP address of the EASDF.

[0166] In this request, the EEC may report at least one of the following: UE location, APP ID, etc.

[0167] EES performs a verification process to verify that the request is legitimate.

[0168] EES sends the operator's DNS configuration to EEC.

[0169] EEC can send the operator's DNS configuration to the APP or AC; it can also use the API interface to let the APP or AC call this API interface.

[0170] Example 2: Use the capability exposure interface to open DNS configuration. For details, see Figure 4 .

[0171] like Figure 4 As shown in the figure, 5GC network elements, such as SMF, AMF, NEF, etc., can send the operator DNS configuration to AF. The method of sending it to AF is to reuse the CAPIF API architecture, that is, to add support for sending the operator DNS configuration in the CAPIF capability exposure API architecture.

[0172] In addition, AF supports the process of discovering the API that supports sending the operator's DNS. It also supports the process of registering the API. In fact, this process is that 5GC opens the operator's DNS configuration to AF in the form of capability opening.

[0173] Alternatively, using NEF services, 5GC sends the MNO DNS to AF through NEF. The AF is a third-party AF, such as Tencent's AF.

[0174] AF establishes a PDU session with the UE APP.

[0175] AF can send the operator's DNS configuration to the UE APP.

[0176] It can be seen that through this application, EES provides DNS configuration to EEC, EEC can provide DNS configuration to APP; EES provides DNS to EEC. Alternatively, using capability opening, DNS configuration is opened to AF, and AF uses PDU session to send it to UE APP. In this way, it can ensure that the application can use the DNS configuration provided by the operator without affecting the UE as much as possible, thereby improving the flexibility of DNS query or domain name resolution.

[0177] It should be noted that the execution subject of the DNS configuration processing method provided in the embodiment of the present application may be a DNS configuration processing device, or a control module in the DNS configuration processing device for executing the DNS configuration processing method. In the embodiment of the present application, the DNS configuration processing device provided in the embodiment of the present application is described by taking the DNS configuration processing method executed by the DNS configuration processing device as an example.

[0178] The processing device for DNS configuration in the embodiment of the present application can be a device, a device with an operating system or a communication device, or a component, an integrated circuit, or a chip in a communication device.

[0179] See also Fig. 9 , Fig. 9 900 is one of the structural diagrams of the DNS configuration processing device provided in the embodiment of the present application. The DNS configuration processing device 900 can be applied to the first communication device, such as Fig. 9 As shown, the processing device 900 for DNS configuration includes:

[0180] A first acquisition module 901 is used to acquire the operator DNS configuration from the second communication device;

[0181] An execution module 902 is used to perform a DNS query operation or a domain name resolution operation using the operator DNS configuration;

[0182] The first communication device includes at least one of the following: an application client, an edge enabling client EEC; the second communication device is an edge enabling server EES or an application function AF.

[0183] Optionally, the first communication device includes an application client and an EEC, and the second communication device is an EES; the first acquisition module 901 includes:

[0184] A first sending unit, configured to send a first request message to the EES through the EEC, where the first request message is used to request the operator DNS configuration;

[0185] A first receiving unit, configured to receive the operator DNS configuration sent by the EES through the EEC;

[0186] The second sending unit is used to send the operator DNS configuration to the application client through the EEC.

[0187] Optionally, the first request information includes at least one of the following: location information of the first communication device; identification information of the application client; identification information of the first communication device.

[0188] Optionally, the second sending unit is specifically configured to:

[0189] The EEC sends the operator DNS configuration to the application client through the first interface;

[0190] The first interface is an interface between the application client and the EEC.

[0191] Optionally, the first communication device includes an application client, and the second communication device is an AF;

[0192] The first acquisition module 901 includes:

[0193] A first establishing unit, configured to establish a protocol data unit (PDU) session with the AF;

[0194] The second receiving unit is used to receive the operator DNS configuration sent by the AF through the PDU session.

[0195] Optionally, the operator DNS configuration includes at least one of the following items of the DNS server designated by the operator: an Internet Protocol IP address; a port number.

[0196] The DNS configuration processing device 900 provided in the embodiment of the present application can realize Figure 2 The various processes implemented by the method embodiment and achieving the same technical effect are not described here to avoid repetition.

[0197] See also Fig.10 , Fig.10 FIG. 2 is a second structural diagram of a DNS configuration processing device provided in an embodiment of the present application. The DNS configuration processing device 1000 is applied to a second communication device. Fig.10 As shown, the processing device 1000 for DNS configuration includes:

[0198] The first sending module 1001 is used to send the operator DNS configuration to the first communication device;

[0199] The first communication device is an application client or an EEC; the second communication device is an EES or an AF.

[0200] Optionally, the first communication device is an EEC, and the second communication device is an EES; the apparatus further includes:

[0201] The first receiving module is used to receive the first request information sent by the EEC, where the first request information is used to request the operator DNS configuration.

[0202] Optionally, the first request information includes at least one of the following: location information of the first communication device; identification information of the application client; identification information of the first communication device.

[0203] Optionally, the first communication device is an application client, and the second communication device is an AF;

[0204] The first sending module 1001 includes:

[0205] A second establishing unit, configured to establish a PDU session with the first communication device;

[0206] The third sending unit is used to send the operator DNS configuration to the first communication device through the PDU session.

[0207] Optionally, the second communication device is AF;

[0208] The device also includes:

[0209] The second acquisition module is used to acquire the operator DNS configuration from a third communication device.

[0210] Optionally, the second acquisition module is specifically used to:

[0211] receiving the operator DNS configuration sent by the third communication device; or,

[0212] The operator DNS configuration is obtained by calling a second interface, where the second interface is an interface between the third communication device and the second communication device.

[0213] Optionally, the device further comprises:

[0214] A discovery module is used to discover that the second interface supports sending the operator DNS configuration.

[0215] Optionally, the operator DNS configuration includes at least one of the following items of the DNS server specified by the operator: an IP address; a port number.

[0216] The DNS configuration processing device 1000 provided in the embodiment of the present application can realize Figure 5 The various processes implemented in the method embodiment achieve the same technical effect and will not be described again here to avoid repetition.

[0217] See also Fig.11 , Fig.11 It is a structural diagram of a processing device for DNS configuration provided in an embodiment of the present application.

[0218] like Fig.11 As shown, the processing device 1100 for DNS configuration includes:

[0219] The second sending module 1101 is configured to send the operator DNS configuration to the AF.

[0220] Optionally, the second sending module is specifically configured to:

[0221] Send the operator DNS configuration to AF through the second interface;

[0222] The second interface is an interface between the third communication device and the AF.

[0223] Optionally, the device comprises:

[0224] A publishing module is used to publish the calling information of the second interface, where the calling information is used to indicate that the second interface supports sending the operator DNS configuration.

[0225] Optionally, the operator DNS configuration includes at least one of the following items of the DNS server specified by the operator: an IP address; a port number.

[0226] The DNS configuration processing device 1100 provided in the embodiment of the present application can realize Figure 6 The various processes implemented in the method embodiment achieve the same technical effect and will not be described again here to avoid repetition.

[0227] Optional, such as Fig.12 As shown, the embodiment of the present application further provides a communication device 1200, including a processor 1201, a memory 1202, and a program or instruction stored in the memory 1202 and executable on the processor 1201. For example, when the communication device 1200 is the aforementioned first communication device, the program or instruction is executed by the processor 1201 to implement the aforementioned Figure 2 When the communication device 1200 is the aforementioned second communication device, the program or instruction is executed by the processor 1201 to implement the above Figure 5When the communication device 1200 is the aforementioned third communication device, the program or instruction is executed by the processor 1201 to implement the above Figure 6 The various processes of the method embodiment can achieve the same technical effect and will not be described again here to avoid repetition.

[0228] An embodiment of the present application also provides a communication device, including a processor and a communication interface.

[0229] Wherein, when the communication device is the aforementioned first communication device, the communication interface is used to obtain the operator DNS configuration from the second communication device; the processor is used to use the operator DNS configuration to perform a DNS query operation or a domain name resolution operation; wherein, the first communication device includes at least one of the following: an application client, an edge enabling client EEC; the second communication device is an edge enabling server EES or an application function AF. This embodiment corresponds to the above-mentioned embodiment 2, and the above-mentioned Figure 2 All implementation processes and implementation methods of the method embodiment are applicable to this embodiment and can achieve the same technical effect.

[0230] When the communication device is the aforementioned second communication device, the communication interface is used to send the operator DNS configuration to the first communication device; wherein the first communication device is an application client or EEC; and the second communication device is EES or AF. This embodiment corresponds to the above-mentioned embodiment 5. Figure 5 All implementation processes and implementation methods of the method embodiment are applicable to this embodiment and can achieve the same technical effect.

[0231] When the communication device is the aforementioned third communication device, the communication interface is used to send the operator DNS configuration to the AF. Figure 6 All implementation processes and implementation methods of the method embodiment are applicable to this embodiment and can achieve the same technical effect.

[0232] Specifically, the embodiment of the present application also provides a communication device. Fig.13 As shown, the communication device 1300 includes: an antenna 131, a radio frequency device 132, and a baseband device 133. The antenna 131 is connected to the radio frequency device 132. In the uplink direction, the radio frequency device 132 receives information through the antenna 131 and sends the received information to the baseband device 133 for processing. In the downlink direction, the baseband device 133 processes the information to be sent and sends it to the radio frequency device 132. The radio frequency device 132 processes the received information and sends it out through the antenna 131.

[0233] The frequency band processing device may be located in the baseband device 133 . The method executed by the network-side device in the above embodiment may be implemented in the baseband device 133 . The baseband device 133 includes a processor 134 and a memory 135 .

[0234] The baseband device 133 may include, for example, at least one baseband board on which a plurality of chips are arranged. Fig.13 As shown, one of the chips is, for example, a processor 134, which is connected to a memory 135 to call a program in the memory 135 to execute the network device operations shown in the above method embodiment.

[0235] The baseband device 133 may further include a network interface 136 for exchanging information with the radio frequency device 132 , and the interface may be, for example, a Common Public Radio Interface (CPRI).

[0236] Specifically, the network side device of the embodiment of the present application further includes: instructions or programs stored in the memory 135 and executable on the processor 134, and the processor 134 calls the instructions or programs in the memory 135 to execute. Figure 2 , Figure 5 or Figure 6 Each process in the method embodiment, or, Fig. 9 , Fig.10 or Fig.11 The methods executed by the modules shown achieve the same technical effects, and therefore will not be described here in detail to avoid repetition.

[0237] The present application also provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the above Figure 2 , Figure 5 or Figure 6 The various processes of the method embodiment can achieve the same technical effect, and are not described here to avoid repetition. The computer-readable storage medium is, for example, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0238] The embodiment of the present application also provides a readable storage medium on which a program or instruction is stored. When the program or instruction is executed by a processor, the above Figure 2 , Figure 5 or Figure 6 The various processes of the method embodiments can achieve the same technical effect, and will not be described again here to avoid repetition.

[0239] The processor is the processor in the terminal described in the above 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 disk.

[0240] The present application also provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the above Figure 2 , Figure 5 or Figure 6 The various processes of the method embodiments can achieve the same technical effect, and will not be described again here to avoid repetition.

[0241] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

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

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

[0244] The above-mentioned drawings are used to describe the embodiments of the present application, but the present application is not limited to the above-mentioned specific implementation modes. The above-mentioned specific implementation modes are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can make many forms without departing from the purpose of the present application and the scope of protection of the claims, all of which are within the protection of the present application.

Claims

1. A method for processing a domain name system DNS configuration, characterized in that: include: The first communication device obtains the operator DNS configuration from the second communication device; The first communication device uses the operator DNS configuration to perform a DNS query operation or a domain name resolution operation; The first communication device includes at least one of the following: an application client, an edge enabling client EEC; the second communication device is an edge enabling server EES or an application function AF; Wherein, the first communication device includes an application client and an EEC, and the second communication device is an EES; The first communication device obtains the operator DNS configuration from the second communication device, including: The EEC sends a first request message to the EES, where the first request message is used to request the operator DNS configuration; The EEC receives the operator DNS configuration sent by the EES; The EEC sends the operator DNS configuration to the application client; The EEC sends the operator DNS configuration to the application client, including: The EEC sends the operator DNS configuration to the application client through a first interface, where the first interface is an interface between the application client and the EEC; or, The first communication device includes an application client, and the second communication device is an AF; The first communication device obtains the operator DNS configuration from the second communication device, including: The application client establishes a protocol data unit (PDU) session with the AF; The application client receives the operator DNS configuration sent by the AF through the PDU session.

2. The method according to claim 1, characterized in that The first request information includes at least one of the following: location information of the first communication device; identification information of the application client; identification information of the first communication device.

3. The method according to claim 1 or 2, characterized in that: The operator DNS configuration includes at least one of the following items of the DNS server designated by the operator: Internet Protocol IP address; port number.

4. A method for processing DNS configuration, characterized in that: include: The second communication device sends the operator DNS configuration to the first communication device; The first communication device is an application client or an EEC; the second communication device is an EES or an AF; Wherein, the second communication device is AF; Before the second communication device sends the operator DNS configuration to the first communication device, the method further includes: The AF obtains the operator DNS configuration from the third communication device; The AF obtains the operator DNS configuration from the third communication device, including: The AF obtains the operator DNS configuration by calling a second interface, where the second interface is an interface between the third communication device and the AF; or, The first communication device is an application client, and the second communication device is an AF; The second communication device sends the operator DNS configuration to the first communication device, including: The AF establishes a PDU session with the application client; The AF sends the operator DNS configuration to the application client through the PDU session.

5. The method according to claim 4, characterized in that Before the AF calls the second interface to obtain the operator DNS configuration, the method further includes: The AF discovers that the second interface supports sending the operator DNS configuration.

6. The method according to claim 4 or 5, characterized in that: The operator DNS configuration includes at least one of the following items of the DNS server specified by the operator: IP address; port number.

7. A method for processing DNS configuration, characterized in that: include: The third communication device sends the operator DNS configuration to the AF, where the third communication device is a core network device; The third communication device sends the operator DNS configuration to the AF, including: The third communication device sends the operator DNS configuration to the AF through the second interface, where the second interface is an interface between the third communication device and the AF.

8. The method according to claim 7, characterized in that Before the third communication device sends the operator DNS configuration to the AF through the second interface, the method includes: The third communication device publishes calling information of the second interface, where the calling information is used to indicate that the second interface supports sending the operator DNS configuration.

9. The method according to claim 7 or 8, characterized in that: The operator DNS configuration includes at least one of the following items of the DNS server specified by the operator: IP address; port number.

10. A DNS configuration processing device, characterized in that: Applied to a first communication device, the apparatus includes: A first acquisition module, used to acquire the operator DNS configuration from the second communication device; An execution module, used to use the operator's DNS configuration to perform a DNS query operation or a domain name resolution operation; The first communication device includes at least one of the following: an application client, an edge enabling client EEC; the second communication device is an edge enabling server EES or an application function AF; Wherein, the first communication device includes an application client and an EEC, and the second communication device is an EES; The first acquisition module includes: A first sending unit, configured to send a first request message to the EES through the EEC, where the first request message is used to request the operator DNS configuration; A first receiving unit, configured to receive the operator DNS configuration sent by the EES through the EEC; A second sending unit, configured to send the operator DNS configuration to the application client through the EEC; The second sending unit is specifically used for: The EEC sends the operator DNS configuration to the application client through a first interface, where the first interface is an interface between the application client and the EEC; or, The first communication device includes an application client, and the second communication device is an AF; The first acquisition module includes: A first establishing unit, configured to establish a protocol data unit (PDU) session with the AF; The second receiving unit is used to receive the operator DNS configuration sent by the AF through the PDU session.

11. The device according to claim 10, characterized in that The first request information includes at least one of the following: location information of the first communication device; identification information of the application client; identification information of the first communication device.

12. The device according to claim 10 or 11, characterized in that The operator DNS configuration includes at least one of the following items of the DNS server designated by the operator: Internet Protocol IP address; port number.

13. A DNS configuration processing device, characterized in that: Applied to a second communication device, the apparatus comprises: A first sending module, used to send the operator DNS configuration to the first communication device; The first communication device is an application client or an EEC; the second communication device is an EES or an AF; Wherein, the second communication device is AF; The device also includes: A second acquisition module, used to acquire the operator DNS configuration from a third communication device; Wherein, the second acquisition module is specifically used for: Acquire the operator DNS configuration by calling a second interface, where the second interface is an interface between the third communication device and the second communication device; or, The first communication device is an application client, and the second communication device is an AF; The first sending module includes: A second establishing unit, configured to establish a PDU session with the first communication device; The third sending unit is used to send the operator DNS configuration to the first communication device through the PDU session.

14. The device according to claim 13, characterized in that The device also includes: A discovery module is used to discover that the second interface supports sending the operator DNS configuration.

15. The device according to claim 13 or 14, characterized in that The operator DNS configuration includes at least one of the following items of the DNS server specified by the operator: IP address; port number.

16. A DNS configuration processing device, characterized in that: The device is a core network device, and the device includes: The second sending module is used to send the operator DNS configuration to the AF; Wherein, the second sending module is specifically used for: The operator DNS configuration is sent to the AF via a second interface, where the second interface is an interface between the device and the AF.

17. The device according to claim 16, characterized in that The device comprises: A publishing module is used to publish the calling information of the second interface, where the calling information is used to indicate that the second interface supports sending the operator DNS configuration.

18. The device according to claim 16 or 17, characterized in that The operator DNS configuration includes at least one of the following items of the DNS server specified by the operator: IP address; port number.

19. A communication device, characterized in that: The method comprises a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the method for processing the DNS configuration according to any one of claims 1 to 3; Or, the steps of the method for processing DNS configuration according to any one of claims 4 to 6; Or, the steps of the method for processing DNS configuration as described in any one of claims 7 to 9.

20. A readable storage medium, characterized in that: The readable storage medium stores a program or instruction, and when the program or instruction is executed by the processor, the steps of the method for processing the DNS configuration according to any one of claims 1 to 3 are implemented; Or, the steps of the method for processing DNS configuration according to any one of claims 4 to 6; Or, the steps of the method for processing DNS configuration as described in any one of claims 7 to 9.

Images