Dns configuration processing method and apparatus, communication device, and storage medium

Abstract

A domain name system (DNS) configuration processing method and device, a communication device, and a storage medium. The DNS configuration processing method performed by a user equipment (UE) can include determining a DNS configuration used by the UE based on a first DNS configuration received by the UE, if the UE is not configured with a second DNS configuration that meets a preset condition, the first DNS configuration being selected by a network device for the UE.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to the technical field of wireless communication, and more particularly to a domain name system (DNS) configuration processing method and device, a communication device, and a storage medium. BACKGROUND

[0002] With the development of communication technology and information technology, mobile communication networks need to not only meet the connection needs between people, but also meet the communication needs between people and things, and between things. In order to meet the needs of providing low-latency services, edge computing emerges as the times require. Edge computing supports operators and third-party application services to be deployed near the access point of the network where the user equipment (UE) is located, thereby reducing the end-to-end delay and load on the transmission network to achieve efficient service delivery.

[0003] Edge computing is a combination of edge infrastructure, edge network, edge computing platform, and edge application. One edge application service may be provided by multiple edge application servers (EAS).

[0004] When starting an edge application service, the UE needs to know the Internet Protocol (IP) address of the EAS. The UE can select a suitable EAS (for example, the EAS closest to the UE) through an edge application server discovery function (EASDF) function, so that the data flow can be routed locally to the EAS, thereby optimizing service delay, data routing path, and user service experience.

[0005] EAS discovery is a process in which the UE resolves a domain name through DNS to discover a suitable EAS IP address.

[0006] The DNS server can be deployed at different locations in the network. It can be deployed as a central DNS (C-DNS) resolver / server or as a local DNS (L-DNS) resolver / server. SUMMARY

[0007] Embodiments of the present disclosure provide a DNS configuration processing method and device, a communication device, and a storage medium.

[0008] A first aspect of an embodiment of the present disclosure provides a DNS configuration processing method, which is executed by a user equipment (UE), and the method comprises:

[0009] If the UE is not configured with a second DNS configuration that meets preset conditions, the DNS configuration used by the UE is determined based on the first DNS configuration selected by the network device for the UE.

[0010] A second aspect of this disclosure provides a DNS configuration processing method, wherein the method is executed by an SMF, the method comprising:

[0011] Determine the secondary DNS configuration;

[0012] Send a second DNS configuration to the UE, wherein the second DNS configuration is used to enable the UE to obtain DNS services;

[0013] Receive feedback information;

[0014] When the feedback information indicates that the UE does not use the second DNS configuration, the maintenance of the DNS processing rules corresponding to the second DNS configuration is stopped.

[0015] A third aspect of this disclosure provides a DNS configuration processing method, wherein the method is executed by a base station, the method comprising:

[0016] Receive feedback information from the UE, wherein the feedback information indicates that the UE does not use the second DNS configuration, or the feedback information indicates whether the UE uses the second DNS configuration;

[0017] The feedback information is sent to the AMF, wherein the feedback information is used by the AMF to forward it to the SMF, and by the SMF to determine to stop maintaining the DNS processing rules corresponding to the second DNS configuration.

[0018] A fourth aspect of this disclosure provides a DNS configuration processing method, wherein the method is executed by the AMF, the method comprising:

[0019] Receive feedback information from the UE forwarded by the base station;

[0020] The feedback information is sent to the AMF, wherein the feedback information indicates that when the UE does not use the second DNS configuration, it is used by the SMF to determine to stop maintaining the DNS processing rules corresponding to the second DNS configuration.

[0021] A fifth aspect of this disclosure provides a Domain Name System (DNS) configuration processing apparatus, wherein the apparatus includes:

[0022] The first determining module is configured to determine the DNS configuration used by the UE based on the first DNS configuration selected by the network device for the UE if the UE is not configured with a second DNS configuration that meets preset conditions.

[0023] A sixth aspect of this disclosure provides a Domain Name System (DNS) configuration processing apparatus, wherein the apparatus includes:

[0024] The second determining module is configured to determine the second DNS configuration;

[0025] The second sending module is configured to send a second DNS configuration to the UE, wherein the second DNS configuration is used to enable the UE to obtain DNS services;

[0026] The second receiving module is configured to receive feedback information;

[0027] The stop module is configured to stop maintaining the DNS processing rules corresponding to the second DNS configuration when the feedback information indicates that the UE does not use the second DNS configuration.

[0028] A seventh aspect of this disclosure provides a DNS configuration processing apparatus, wherein the apparatus includes:

[0029] The third receiving module is configured to receive feedback information from the UE, wherein the feedback information indicates that the UE does not use the second DNS configuration, or the feedback information indicates whether the UE uses the second DNS configuration;

[0030] The third sending module is configured to send the feedback information to the AMF, wherein the feedback information is used by the AMF to forward it to the SMF, and by the SMF to determine to stop maintaining the DNS processing rules corresponding to the second DNS configuration.

[0031] An eighth aspect of this disclosure provides a DNS configuration processing apparatus, wherein the apparatus includes:

[0032] The fourth receiving module is configured to receive feedback information from the UE forwarded by the base station;

[0033] The fourth sending module is configured to send the feedback information to the AMF, wherein the feedback information indicates that when the UE does not use the second DNS configuration, it is used by the SMF to determine to stop maintaining the DNS processing rules corresponding to the second DNS configuration.

[0034] A ninth aspect of this disclosure provides a communication device, including a processor, a transceiver, a memory, and an executable program stored in the memory and capable of being executed by the processor, wherein when the processor executes the executable program, it performs a DNS configuration processing method as provided in any one of the first to fourth aspects described above.

[0035] A tenth aspect of this disclosure provides a computer storage medium storing an executable program; the executable program, when executed by a processor, enables the DNS configuration processing method provided in any one of the first to fourth aspects.

[0036] The technical solution provided in this disclosure means that after the UE receives the second DNS configuration sent by the network side of the mobile communication network, it will not directly determine to use the second DNS configuration, but will select a DNS configuration suitable for the UE based on the second DNS configuration and the first DNS configuration, so that the UE has sufficient flexibility to select a DNS configuration suitable for the current application scenario.

[0037] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit the embodiments of this disclosure. Attached Figure Description

[0038] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments of the invention and, together with the description, serve to explain the principles of the embodiments of the invention.

[0039] Figure 1 This is a schematic diagram illustrating the structure of a wireless communication system according to an exemplary embodiment;

[0040] Figure 2A This is a flowchart illustrating a DNS configuration processing method according to an exemplary embodiment;

[0041] Figure 2B This is a flowchart illustrating a DNS configuration processing method according to an exemplary embodiment;

[0042] Figure 3 This is a flowchart illustrating a DNS configuration processing method according to an exemplary embodiment;

[0043] Figure 4 This is a flowchart illustrating a DNS configuration processing method according to an exemplary embodiment;

[0044] Figure 5 This is a flowchart illustrating a DNS configuration processing method according to an exemplary embodiment;

[0045] Figure 6 This is a flowchart illustrating a DNS configuration processing method according to an exemplary embodiment;

[0046] Figure 7 This is a schematic diagram illustrating a PDU session processing flow according to an exemplary embodiment;

[0047] Figure 8 This is a flowchart illustrating a PDU session processing method according to an exemplary embodiment;

[0048] Figure 9A This is a schematic diagram illustrating the structure of a DNS configuration processing apparatus according to an exemplary embodiment;

[0049] Figure 9B This is a schematic diagram illustrating the structure of a DNS configuration processing apparatus according to an exemplary embodiment;

[0050] Figure 10 This is a schematic diagram illustrating the structure of a DNS configuration processing apparatus according to an exemplary embodiment;

[0051] Figure 11 This is a schematic diagram illustrating the structure of a DNS configuration processing apparatus according to an exemplary embodiment;

[0052] Figure 12 This is a schematic diagram illustrating the structure of a DNS configuration processing apparatus according to an exemplary embodiment;

[0053] Figure 13 This is a schematic diagram of the structure of a UE according to an exemplary embodiment;

[0054] Figure 14 This is a schematic diagram of the structure of a communication device according to an exemplary embodiment. Detailed Implementation

[0055] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with those of the present invention. Rather, they are merely examples of apparatuses and methods consistent with some aspects of the embodiments of the present invention as detailed in the appended claims.

[0056] The terminology used in this disclosure is for the purpose of describing particular embodiments only and is not intended to be limiting of the present disclosure. The singular forms “a,” “the,” and “the” as used in this disclosure and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any and all possible combinations of one or more of the associated listed items.

[0057] It should be understood that although the terms first, second, third, etc., may be used to describe various information in embodiments of this disclosure, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, first information may also be referred to as second information without departing from the scope of embodiments of this disclosure, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to a determination."

[0058] Please refer to Figure 1 This illustration shows a schematic diagram of the structure of a wireless communication system provided in an embodiment of this disclosure. Figure 1 As shown, the wireless communication system is a communication system based on cellular mobile communication technology. The wireless communication system may include: several UEs 11 and several access devices 12.

[0059] UE11 can be a device that provides voice and / or data connectivity to a user. UE11 can communicate with one or more core networks via a Radio Access Network (RAN). UE11 can be an IoT UE, such as a sensor device, a mobile phone (or "cellular" phone), and a computer with an IoT UE. For example, it can be a fixed, portable, pocket-sized, handheld, computer-embedded, or vehicle-mounted device. Examples include a station (STA), subscriber unit, subscriber station, mobile station, mobile station, remote station, access point, remote terminal, access terminal, user terminal, user agent, user device, or user equipment (UE). Alternatively, UE11 can be a device in an unmanned aerial vehicle (UAV). Alternatively, UE11 can be a vehicle-mounted device, such as a vehicle computer with wireless communication capabilities, or a wireless communication device connected to an external vehicle computer. Alternatively, UE11 can also be a roadside device, such as a street light, traffic light, or other roadside device with wireless communication capabilities.

[0060] Access device 12 can be a network-side device in a wireless communication system. This wireless communication system can be a 4G system (also known as Long Term Evolution, LTE); or it can be a 5G system (also known as a New Radio, NR, or 5G NR system). Alternatively, it can be the next generation after 5G. In this case, the access network in the 5G system can be called NG-RAN (New Generation-Radio Access Network). Alternatively, it can be an MTC system.

[0061] The access device 12 can be an evolved NB (eNB) used in a 4G system. Alternatively, the access device 12 can also be a gNB (gNB) using a centralized-distributed architecture in a 5G system. When the access device 12 adopts a centralized-distributed architecture, it typically includes a central unit (CU) and at least two distributed units (DUs). The central unit is equipped with a protocol stack of the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, and the Media Access Control (MAC) layer; the distributed units are equipped with a physical (PHY) layer protocol stack. This disclosure does not limit the specific implementation of the access device 12.

[0062] Access device 12 and UE11 can establish a wireless connection via a wireless air interface. In different implementations, the wireless air interface is a wireless air interface based on the fourth-generation mobile communication network technology (4G) standard; or, the wireless air interface is a wireless air interface based on the fifth-generation mobile communication network technology (5G) standard, such as a new air interface; or, the wireless air interface can also be a wireless air interface based on a next-generation mobile communication network technology standard based on 5G.

[0063] In some embodiments, UE11 can also establish E2E (End to End) connections. Examples include V2V (vehicle to vehicle), V2I (vehicle to Infrastructure), and V2P (vehicle to pedestrian) communication scenarios in vehicle-to-everything (V2X) communication.

[0064] In some embodiments, the wireless communication system described above may further include a network management device 13.

[0065] Several access devices 12 are connected to network management device 13. Network management device 13 can be a core network device in a wireless communication system, such as a Mobility Management Entity (MME) in an Evolved Packet Core (EPC). Alternatively, it can be other core network devices, such as a Serving Gateway (SGW), a Public Data Network Gateway (PGW), a Policy and Charging Rules Function (PCRF), or a Home Subscriber Server (HSS). The implementation of network management device 13 is not limited in this embodiment.

[0066] like Figure 2A As shown, this disclosure provides a Domain Name System (DNS) configuration processing method, which is executed by the UE. The method includes:

[0067] S100: If the UE is not configured with a second DNS configuration that meets the preset conditions, the DNS configuration used by the UE is determined based on the first DNS configuration selected by the network device for the UE.

[0068] This network device can be a core network device, such as an SMF.

[0069] like Figure 2B As shown, this disclosure provides a Domain Name System (DNS) configuration processing method, which is executed by the UE. The method includes:

[0070] S110: Receive the second DNS configuration sent by SMF;

[0071] S120: Determine the DNS configuration used by the UE based on the second DNS configuration and the first DNS configuration.

[0072] The UE device receives a second DNS configuration from the network side, which can be used to determine the DNS server for the UE to request domain name resolution. The second DNS configuration can indicate the address information of the EASDF that can discover the EAS.

[0073] If the UE requires domain name resolution, it sends a domain name query message to the corresponding EAS based on the second DNS configuration and receives the IP address of the EAS returned by the EAS. In short, the EAS can select an EAS for the UE.

[0074] The selection of an EAS can include EAF discovery and EAS re-discovery. EAS discovery involves the EASDF selecting an EAS that provides edge computing services for the UE and returning the IP address of the selected EAS to the UE. EAS retransmission is mainly used when the EAS determined based on EAS discovery is unavailable or is no longer the optimal EAS. In this case, an EAS is rediscovered and selected, and the IP address of the reselected EAS is sent to the UE.

[0075] After receiving the second DNS configuration sent by the network device (i.e., the network side), the UE will not use the second DNS configuration directly, but will combine the second DNS configuration and the first DNS configuration to determine the DNS configuration used by the UE when obtaining DNS services.

[0076] In this embodiment of the disclosure, the UE will not directly use the second DNS configuration to determine the UE's DNS server after receiving the second DNS configuration. Instead, it will apply the appropriate DNS configuration in different application scenarios according to its own needs and / or the needs of the application, thereby optimizing the UE's communication service quality and the UE's user experience.

[0077] For example, S120 may include: determining whether to use the second DNS configuration or the first DNS configuration based on the attribute information of the first DNS configuration obtained by the UE; if it is determined that the second DNS configuration is used, determining the DNS server of the UE based on the second DNS configuration; and / or, if it is determined that the first DNS configuration is used, determining the DNS server of the UE based on the first DNS configuration.

[0078] The second DNS configuration is a DNS configuration sent by the mobile communication network. For example, the second DNS configuration may be a DNS configuration sent by the SMF within the mobile communication network. The first DNS configuration can be any configuration different from the second DNS configuration. For example, the first DNS configuration may be: the UE's private DNS configuration, the default DNS configuration, or a DNS configuration provided by an application within the UE.

[0079] The step of determining whether to use the second DNS configuration or the first DNS configuration based on the attribute information of the second DNS obtained by the UE includes: determining the second DNS configuration or the first DNS configuration based on the source information of the first DNS configuration. That is, the attribute information includes the source information.

[0080] In one embodiment, regardless of whether it is the second DNS configuration or the first DNS configuration, it may include at least: the address information of a DNS server that can provide DNS services. This address information includes, but is not limited to, an IP address.

[0081] Of course, the above is just an example of S120 execution, and the actual implementation is not limited to the above example.

[0082] In some embodiments, S120 may include:

[0083] If the first DNS configuration does not meet the preset conditions, the second DNS configuration will be used.

[0084] or;

[0085] When the first DNS configuration meets the preset conditions, the first DNS configuration is used.

[0086] If the first DNS configuration does not meet the preset conditions, i.e., it is not a special DNS configuration or a DNS configuration from a specific source, the second DNS configuration will be used preferentially. If the UE uses the second DNS configuration, it means the UE does not use the second DNS configuration.

[0087] At this point, the DNS server for the UE will be determined primarily based on the second DNS configuration. If the DNS server is determined primarily based on the second DNS configuration, the network's EASDF can be used to select the EAS, thereby leveraging the edge deployment characteristics of the mobile communication network's EAS and / or EASDF to provide DNS resolution services and edge computing services with the lowest possible latency.

[0088] If the first DNS configuration meets the preset conditions, that is, the first DNS configuration may be a special DNS configuration or a DNS configuration from a specific source, then considering that if the special DNS configuration or the DNS configuration from a specific source is not used, it may cause some services to be unable to be provided with high quality, the UE's DNS server will be determined based on the first DNS configuration.

[0089] In one embodiment, the first DNS configuration satisfying the preset condition includes at least one of the following:

[0090] The first DNS configuration is the UE's private DNS configuration;

[0091] The first DNS configuration is the application's DNS configuration, and the first DNS configuration is a DNS configuration that is prohibited from being rewritten.

[0092] The UE's private DNS configuration applies to all applications installed within the UE. This private DNS configuration can be a system-level DNS configuration for the UE. Under normal circumstances, if the first DNS configuration is the UE's private DNS configuration, any domain name resolution request triggered by any application or operating system will be sent according to this private DNS configuration to obtain DNS services provided by the DNS server specified in the first DNS configuration.

[0093] In some embodiments, the first DNS configuration is a DNS configuration that prohibits rewriting, including:

[0094] The application indicates that the first DNS configuration is a DNS configuration that cannot be rewritten;

[0095] or,

[0096] The application did not indicate that the first DNS configuration was a rewriteable DNS configuration.

[0097] For example, some applications deploy their DNS information on dedicated DNS servers. In this case, the corresponding DNS information can only be obtained from the corresponding DNS server so that the UE can obtain the correct IP address and thus obtain the application services provided by the application's application server.

[0098] In one scenario, the application might explicitly indicate that the first DNS configuration is a DNS configuration that should not be modified. In another scenario, the application neither explicitly indicates that the first DNS configuration is a DNS configuration that should not be modified, nor explicitly indicates that it can be modified. In this case, to reduce the risk of application service provisioning issues caused by using a second DNS configuration to modify the first DNS configuration, it can be assumed that the application's first DNS configuration is also a DNS configuration that should not be modified.

[0099] If the first DNS configuration is the application's DNS configuration, and if the application explicitly indicates that the first DNS configuration can be used, then the second configuration can be considered not to meet the preset conditions.

[0100] Using this method, the UE can select the appropriate DNS configuration for the current application scenario based on different source methods or different DNS configurations, determine the DNS server based on the effective DNS configuration, and request the corresponding DNS service from the corresponding DNS server.

[0101] In some embodiments, the first DNS configuration may further include:

[0102] The DNS configuration cached locally by the UE may include, but is not limited to, historical DNS configurations and / or temporary DNS configurations issued by the network side before issuing the second DNS configuration.

[0103] The default DNS configuration can be either the application's default DNS configuration or the UE's DNS configuration. This default DNS configuration has a lower priority; that is, when the UE, application, or network side does not provide a DNS configuration or provides an available DNS configuration, the UE will use this default DNS configuration. However, it is important to note that this is merely an example of a default DNS configuration, and the actual implementation is not limited to this.

[0104] In some embodiments, if the first DNS configuration is the locally cached historical DNS configuration and / or temporary DNS configuration or default DNS configuration, then the first DNS configuration can be considered as a DNS configuration that does not meet the preset conditions.

[0105] In summary, in this embodiment of the disclosure, if the first DNS configuration is a DNS configuration that does not meet the preset conditions, the network side shall first determine the second DNS configuration by combining the UE's location information and / or the EAS deployment information, so that the UE can obtain DNS services with low latency and high service quality according to the second DNS configuration.

[0106] In some embodiments, the method further includes: sending a Protocol Data Unit (PDU) session request message;

[0107] S110 may include:

[0108] The receiving network device returns a PDU session establishment acceptance message based on the PDU session request, wherein the PDU session establishment acceptance message carries the second DNS configuration.

[0109] A PDU session request message can be sent by a UE to request the establishment of a PDU session. The application that triggers the PDU session can be one or more applications.

[0110] Upon receiving a PDU session request message, the network provides a second DNS configuration for the UE in response to the message. This second DNS configuration is carried in the PDU session establishment accept message returned to the UE. If the network does not intend to respond to the PDU session request message, it may send a PDU session rejection message. In this case, the network does not need to determine the second DNS configuration for the UE; that is, the second DNS configuration may not be carried in the PDU session rejection message.

[0111] The determination and transmission of the second DNS configuration are triggered by PDU session request messages and PDU session request acceptance messages, without the need to introduce new messages. This approach features strong compatibility with related technologies and low signaling overhead.

[0112] After the UE receives the second DNS configuration, it can determine whether to use the second DNS configuration to obtain DNS services. If the UE decides to obtain DNS services based on the first DNS configuration, which is different from the second DNS configuration, it will inform the network side that the second DNS configuration is not currently being used.

[0113] Therefore, in some embodiments, reference is made to Figure 3 As shown, the method further includes:

[0114] S130: When the second DNS configuration is not applied, send feedback information to the network side, wherein the feedback information indicates that the UE does not use the second DNS configuration; or, the feedback information indicates whether the UE uses the second DNS configuration.

[0115] By sending this feedback information, the network side will know that the UE has not implemented the second DNS configuration. The network side can then suspend subsequent configuration operations related to the second DNS configuration or the maintenance of DNS processing rules related to the second DNS configuration.

[0116] The feedback information may include one or more bits. Assuming that the feedback information is indicated by one bit, the two bit values ​​of that bit can respectively indicate whether the UE uses the second DNS configuration to obtain DNS services and whether the UE does not use the second DNS configuration to obtain DNS services.

[0117] In some embodiments, S130 may include:

[0118] When determining the DNS server for the UE based on its private DNS configuration, the feedback information is sent to the network side.

[0119] The UE's private DNS configuration can be a system-level DNS configuration. If a second DNS configuration is received, and the UE has a private DNS configuration, the UE can determine whether to use the second DNS configuration to obtain DNS services in the first instance and promptly report this to the network side. Using the second DNS configuration to obtain DNS services may include at least the following steps: determining a DNS server based on the second DNS configuration, sending a DNS resolution request to the determined DNS server to obtain the IP address returned by the DNS, etc.

[0120] In some embodiments, if the first DNS configuration that meets the preset conditions is not the UE's private DNS configuration, the UE may not send feedback information to the network side, or it may send feedback information.

[0121] If the first DNS configuration is an application-defined DNS configuration that is prohibited from being modified, then after the UE receives the second DNS configuration, the UE's system side needs to interact with the application side to determine whether the first DNS configuration is a modified DNS configuration. This determination process may take a relatively long time. It's possible that by the time the UE determines that it will not use the second DNS configuration, the PDU session establishment request message process has already ended. In this case, the UE will at least not report the feedback information during the PDU session establishment request message triggering process. Of course, the UE can also report the feedback information during the PDU session request message triggering process.

[0122] In some embodiments, if an application installed in the UE prioritizes providing its own DNS configuration information to the UE's system side, the system side can also determine whether a first DNS configuration meeting preset conditions exists based on the DNS configuration information submitted by the application before receiving the second DNS configuration. Alternatively, after receiving the second DNS configuration, the UE's system side can interact with the application through an Application Programming Interface (API) to determine whether the application's DNS configuration meets the preset conditions. If the UE can promptly determine whether the application's DNS configuration meets the preset conditions, it can also send the feedback information to the network side during the process triggered by the PDU session establishment request message.

[0123] The feedback information can be carried in an Information Element (IE) or a Container.

[0124] For example, this feedback information can be sent to the network side in the response message of the PDU session establishment request acceptance message.

[0125] In some embodiments, the second DNS configuration includes:

[0126] SMF is the address information of the Edge Application Server Discovery Function (EASDF) selected by the UE.

[0127] The EASDF can discover EASs that can provide services to the UE. The second DNS configuration includes the address information of the EASDF. The UE can then send a domain name resolution request to the corresponding EASDF based on the address information to obtain the address information of the EAS that can provide the corresponding application services.

[0128] In some embodiments, the method further includes:

[0129] Send a Protocol Data Unit (PDU) session request message;

[0130] The second DNS configuration received from the network side includes:

[0131] The receiving network device returns a PDU session establishment acceptance message based on the PDU session request, wherein the PDU session establishment acceptance message carries the second DNS configuration.

[0132] like Figure 4 As shown, this disclosure provides a DNS configuration processing method, wherein the method is executed by the Session Management Function (SMF), and the method includes...

[0133] S210: Determine the second DNS configuration;

[0134] S220: Send a second DNS configuration to the UE, wherein the second DNS configuration is used to enable the UE to obtain DNS services;

[0135] S230: Receive feedback information;

[0136] S240: When receiving the feedback information indicating that the UE does not use the second DNS configuration, stop maintaining the DNS processing rules corresponding to the second DNS configuration.

[0137] SMF will determine the second DNS configuration for the UE, and then send the determined second DNS configuration to the UE so that the UE can determine the DNS server for obtaining DNS services.

[0138] After completing the second DNS configuration, SMF will also receive feedback information sent by the UE.

[0139] In one embodiment, the UE may send feedback information only when it does not use the second DNS configuration information. In this case, the SMF can assume that the UE does not use the second DNS configuration when it receives the feedback information.

[0140] In another embodiment, the UE may send feedback information regardless of whether a second DNS configuration is used. In this case, the content of the feedback information indicates whether the UE is using the second DNS configuration. The SMF will then determine whether the UE is using the second DNS configuration based on the content of the feedback information.

[0141] Based on the reception status or content of the feedback information, if the SMF determines that the UE does not use the second DNS configuration issued by the SMF, it will stop maintaining the DNS processing rules corresponding to the second DNS configuration, thereby reducing the overhead caused by maintaining the DNS processing rules corresponding to the second DNS configuration.

[0142] The DNS processing rules here include, but are not limited to, rules that respond to DNS query messages sent by the UE. For example, the DNS processing rules may at least indicate the IP address of the DNS server responding to the DNS query message from the UE.

[0143] For example, DNS processing rules may include the corresponding IP address for constructing the Extended Domain Name System (EDNS) client subnet option. This IP address may indicate the server or resolver responding to the UE's DNS query message.

[0144] As another example, DNS processing rules may include the corresponding local DNS server IP address. In this case, the DNS processing rules may also instruct EASDF to simply forward DNS queries to a pre-configured DNS server or resolver.

[0145] The DNS processing rules corresponding to the cessation of maintenance of the second DNS configuration mentioned here include, but are not limited to, at least one of the following:

[0146] SMF does not need to send a DNS context update request (Neasdf_DNSContext_Update Request) message to the EASDF indicated by the second DNS configuration. This DNS context update request message can carry the EASDF context identifier (ID) and DNS processing rules, and can be used to update or delete the UE's DNS processing rules stored in the EASDF.

[0147] Receive context update response (Neasdf_DNSContext_UpdateResponse) messages returned by DNS servers such as EASDF.

[0148] If the UE uses the second DNS configuration to obtain DNS services, then when the UE needs to obtain DNS services, EASDF will receive the DNS query message sent by the UE to the DNS server such as EASDF corresponding to the second DNS configuration.

[0149] If it is determined that the DNS message generated by the DNS query message conforms to the DNS processing rules, the EASDF indicated by the second DNS configuration invokes the DNS Context Notification Request (Neasdf_DNSContext_Notify Request) message to report the DNS message to the SMF; the DNS processing rules here may include: DNS message reporting rules.

[0150] After receiving the DNS Context Notification Request message, SMF will send a DNS Context Notification Request Response (Neasdf_DNSContext_Notify Response) message to EASDF.

[0151] EASDF receives DNS query messages from the UE;

[0152] The DNS query message is processed according to the DNS processing rules. For example, the EDNS client subnet option is added to the DNS query message according to the DNS processing rules, and the DNS query message with the added EDNS client subnet option is sent to the C-DES server. Another example is that EASDF sends the DNS to the local DNS server.

[0153] When EASDF receives a DNS response message from the DNS system, it will determine whether it can be sent to the UE based on the DNS processing rules.

[0154] If the IP address or Fully Qualified Domain Name (FQDN) of the EAS in the DNS response message matches a DNS rule provided by the SMF, the EASDF can send a DNS message report to the SMF by invoking a DNS Context Notification Request. This DNS message report includes EAS information, at least the EAS's IP address. If the EASDF receives multiple EAS IP addresses from the contacted DNS server, the DNS message report includes all the EAS IP addresses from the DNS response message. Additionally, the DNS message report may also include the received FQDN and EDNS client subnet options.

[0155] In one embodiment, according to DNS processing rules, after receiving a DNS response message, the EASDF first caches the DNS response message until it receives a notification from the SMF that it has received a DNS message report, and then sends the DNS response message to the UE. If DNS response message caching and reporting are configured according to the DNS processing rules, reporting control rules may also be set. For example, assuming the DNS processing rules restrict reporting to a single instance, the EASDF needs to send a DNS message report to the SMF according to the detection template restricted by the DNS processing rules for each DNS response message received, and then send the DNS response message to the UE only after receiving a notification from the SMF based on the DNS message report.

[0156] EASDF can respond to service operations via the DNS Context Notification Request (Neasdf_DNSContext_Notify Request) message.

[0157] EASDF receives DNS context notification response (Neasdf_DNSContext_Notify Response) messages from SMF.

[0158] SMF can optionally perform the selection and insertion of the uplink classifier or the local session anchor UPF, and select and insert the UL CL / BP and Local PSA.

[0159] Based on EAS information received from EASDF, other UPF selection criteria, and service experience or performance analysis of edge applications, SMF can determine DNAI and N6 data routing information related to DNAS. SMF can optionally perform Uplink Classifier (UL CL) / Branching Point (BP) selection and insertion and Local PDU Session Anchor (PSA). In the UL CL case, SMF determines traffic detection rules and data routing rules based on the IP address range of each Data Network Access Identifier (DNAI).

[0160] SMF invokes a DNS Context Update Request (Neasdf_DNSContext_Update Request) to send a request message to EASDF, carrying DNS processing rules. These DNS processing rules instruct EASDF to send cached DNS response messages to the UE (User Equipment).

[0161] EASDF sends a response message to SMF for the DNS context update request (Neasdf_DNSContext_Update Response).

[0162] EASDF sends a DNS response message to the terminal UE.

[0163] In some embodiments, S210 may include:

[0164] The second DNS configuration is determined based on the deployment information of the Edge Server (EAS) and / or the location of the UE.

[0165] Based on the UE's location information, the nearest EASDF is selected, and then the second DNS configuration is determined, etc.

[0166] Based on the UE's location information and the EAS deployment information, select EASDF, which is relatively close to both the UE and the EAS.

[0167] The second DNS configuration determined based on the EAS deployment information and / or the UE's location enables the UE to obtain DNS services from a DNS server that is relatively close to it, thereby ensuring DNS service response latency.

[0168] The deployment information for this EAS indicates the deployment location of the EAS, and other related information.

[0169] In some embodiments, determining the second DNS configuration based on the deployment information of the Edge Server (EAS) and the location of the UE includes:

[0170] The second DNS configuration is determined based on at least one of the following: the deployment information of the EAS, the location information of the UE, the subscription information of the UE, the local configuration of the SMF, and the policy information associated with the PDU session.

[0171] For example, the UE's subscription information indicates whether the UE can use EASDF to participate in the provision of DNS services. The SMF's local policy and / or policy information associated with the PDU session can be used to select the appropriate EASDF for the UE.

[0172] Different PDU sessions may involve different services, and different services may use different policies. Therefore, the SMF can generate the second DNS configuration based on local policies and / or policies requested from the Policy Control Function (PCF). The policy information associated with the PDU session may be policy information from the PCF. Of course, the above is just an example, and the specific implementation is not limited to the above example.

[0173] In some embodiments, S210 may include: determining the second DNS configuration upon receiving a PDU session establishment request message from the UE;

[0174] S220 may include: sending a PDU session establishment acceptance message to the UE of the PDU session establishment request message, wherein the PDU session establishment acceptance message carries the second DNS configuration.

[0175] The feedback information can be carried in the response message of the PDU session establishment acceptance message and returned to the network.

[0176] In some embodiments, S230 may include: receiving a PDU session update uplink request message carrying the feedback information.

[0177] In some embodiments, S210 may include: selecting an EASDF, wherein the first DSN configuration includes address information of the selected EASDF.

[0178] Furthermore, the method also includes:

[0179] The selected EASDF sends the UE's network protocol IP address, the UE's Subscriber Permanent Identifier (SUPI), the notification endpoint's identification information, and DNS processing rules. This notification endpoint can be one that the EASDF needs to send a DNS message report to upon receiving a DNS response message to ensure the security of the DNS service.

[0180] like Figure 5 As shown, this functional embodiment provides a DNS configuration processing method, wherein the method is executed by the base station and includes:

[0181] S310: Receive feedback information from the UE, wherein the feedback information indicates whether the UE uses the second DNS configuration sent by the network side;

[0182] S320: Send the feedback information to the AMF, wherein the feedback information is used for the AMF to forward to the SMF, and when instructing the UE not to use the second DNS configuration, the SF determines to stop maintaining the DNS processing rules corresponding to the second DNS configuration.

[0183] This DNS configuration process is performed by the base station, which can be an eNB or gNB, etc. In short, "base station" here refers to any network element in the access network.

[0184] The base station receives feedback information from the UE indicating whether the UE uses the second DNS configuration sent by the network side. For example, in one embodiment, the feedback information simply indicates that the UE does not use the second DNS configuration sent by the network side.

[0185] This feedback information can be carried in a Non-Access Stratum (NAS) message. In this case, the base station can directly send the NAS message to the SMF via the AMF.

[0186] Of course, feedback information can also be carried in Radio Resource Control (RRC) messages. The base station parses the RRC message, discovers that it contains feedback information, and sends this feedback information to the AMF. The AMF then forwards it to the SMF. If the UE does not use the second DNS configuration, the SMF will stop maintaining the DNS processing rules of the second DNS configuration after receiving this feedback information.

[0187] In this embodiment of the disclosure, the feedback information may be carried in the IE or container of the message sent by the UE to the base station.

[0188] In some embodiments, receiving feedback information from the UE includes:

[0189] A response message is received that carries the feedback information and indicates that the session establishment accepts the PDU message.

[0190] The response message established by the PDU session carries the feedback information, without the need to introduce a special message. It has the characteristics of strong compatibility with related technologies, that is, the feedback information transmission is simple.

[0191] In one embodiment, S320 may include:

[0192] Send an N2 PDU session response message carrying the feedback information to the AMF.

[0193] In this embodiment of the disclosure, the feedback information is carried in the N2 PDU reply response message sent by the base station to the AMF, so that the AMF receives the feedback information when it receives the N2 PDU session response message.

[0194] like Figure 6 As shown, this disclosure provides a DNS configuration processing method, wherein the method is executed by the AMF, and the method includes:

[0195] S410: Receive feedback information from the UE forwarded by the base station;

[0196] S420: Send the feedback information to the AMF, wherein the feedback information indicates that when the UE does not use the second DNS configuration, it is used by the SMF to determine to stop maintaining the DNS processing rules corresponding to the second DNS configuration.

[0197] After receiving feedback information from the UE forwarded by the base station, the AMF will send the feedback information to the SMF. If the feedback information indicates that the UE does not use the second DNS configuration, the SMF will stop maintaining the DNS processing rules corresponding to the second DNS configuration, thereby reducing the overhead of maintaining the second DNS configuration on the network side.

[0198] In some embodiments, S420 may include: receiving an N2 PDU session response message carrying the feedback information.

[0199] The feedback information is carried in the N2 PDU session response message, which makes receiving feedback information convenient.

[0200] In addition to meeting the connectivity needs between people, 5G networks also need to address the communication needs between people and things, and between things themselves. The nearly 100ms latency of 4G networks cannot meet the requirements of business scenarios such as connected vehicles, industrial control, and AR / VR. The network needs lower processing latency and higher processing power, requiring data processing capabilities and services to be provided close to the network edge where data is generated.

[0201] Edge computing enables operators and third-party application services to be deployed near the access point of the network where the UE is located, thereby achieving efficient service delivery by reducing end-to-end latency and load on the transmission network.

[0202] 5G edge computing is a combination of edge infrastructure, edge network, edge computing platform, and edge applications. The UPF (User Provider Interface) acts as a connecting anchor, collaborating with the 5G core network, edge computing platform, and terminals to fulfill various functions in 5G edge computing scenarios. The interaction of the SMF (Service Provider Interface), UPF, and PCF (Process Provider Interface) enables traffic offloading and policy functions in 5G edge computing. The unified capability open node (NEF) is responsible for the interaction between external edge applications and the 5G network. The edge computing platform, as an AF (Area Function) in the 5G network, manages sessions and policies through NEF / PCF-SMF-UPF. Edge applications deployed on the edge computing platform can belong to one or more network slices.

[0203] 3GPP 5G networks support the deployment of Edge Hosting Environments (EHEs) within the Data Network Domain (DN) outside the session anchor point (UPF). The EHE may be under the control of an operator or a third party. Local deployments of EHE networks can have user plane connections with both centralized and local deployment PSA UPFs within the same data network.

[0204] 3GPP 5G networks support Edge Application Server Discovery Function (EASDF). EASDF has a user plane connection with PSA UPF, processes DNS messages according to SMF instructions, and is used to transmit DNS signaling with the UE.

[0205] An edge application service may be provided by multiple Edge Application Servers (EAS). When starting an edge application service, the user terminal (UE) needs to know the IP address of the application server. The UE can use the EASDF function to select a suitable EAS (e.g., the EAS closest to the UE), so that data flow can be routed from the local device to the EAS, thereby optimizing service latency, data routing paths, and user service experience.

[0206] On the UE side, various factors may affect the terminal's use of EASDF DNS information sent by the network side for DNS queries.

[0207] UE private DNS configuration;

[0208] DNS configuration for UE local caching;

[0209] DNS configuration provided by the application;

[0210] The default DNS configuration.

[0211] In related technologies, the network side sends EASDF DNS information to the UE (i.e., one of the aforementioned second DNS configurations), but the UE can adopt other DNS configurations based on other factors. For edge computing services deployed by telecommunications operators or services with high latency requirements, it is necessary to use the telecommunications operator's DNS configuration to ensure that latency and routing are optimized, thereby improving the user experience.

[0212] However, if the UE uses local DNS configuration, the operator's DNS configuration cannot be truly implemented, thus failing to optimize latency and routing and improve user experience.

[0213] However, UEs that have deployed CDNs or require access to services through user-defined configurations do not want their DNS configurations to be rewritten by the EASDF DNS information sent by the telecommunications operator.

[0214] If the UE does not use EASDF DNS information, the network side will not know this and will continue to maintain the EASDF DNS processing rules based on the UE status, such as location information.

[0215] The UE should use the EASDF DNS information sent to it by the network for DNS configuration whenever possible, unless the UE or application must use its own DNS configuration:

[0216] For edge computing services deployed by telecommunications operators or services with high latency requirements, the application uses the EASDF DNS information sent by the operators.

[0217] For other services, such as applications that have deployed their own CDN, or services that require access through user-defined private configurations, the application has its own DNS configuration.

[0218] The UE can select the DNS configuration based on the following information:

[0219] UE private DNS configuration;

[0220] DNS configuration for UE local caching;

[0221] DNS configuration provided by the application;

[0222] The default DNS configuration. EASDF DNS information received from the network side; this EASDF DNS information is one of the aforementioned second DNS configurations.

[0223] If the UE receives EASDF DNS information from the network side, it should use this information for DNS configuration whenever possible, unless:

[0224] The application indicates that its DNS configuration cannot be rewritten;

[0225] or,

[0226] The application did not explicitly state that its DNS configuration could be rewritten.

[0227] The UE is configured with a private DNS configuration.

[0228] If the UE is configured with a private DNS configuration that can be applied to all PDU sessions, after receiving EASDFDNS information from the network side, the UE will send feedback to the network side indicating that the UE uses the private DNS information and does not use the EASDF DNS information.

[0229] After receiving feedback from the UE, the network side will no longer maintain the EASDF DNS processing rules for the current PDU session.

[0230] If the FQDN in the DNS query matches the FQDN provided by the SMF, then according to the SMF directive EASDF, one of the following options will be executed:

[0231] 1) Option A: EASDF includes the EDNS Client Subnet option in its DNS query message and sends the DNS query message to the DNS server to resolve the FQDN. The DNS server, in conjunction with the EDNS Client Subnet option, resolves the EAS IP address and sends a DNS response to EASDF.

[0232] 2) Option B: EASDF sends a DNS query message to the local DNS server, which is responsible for resolving the FQDN in the corresponding L-DN. EASDF receives the DNS Response message from the local DNS server.

[0233] The EAS discovery process using EASDF is as follows: the SMF sends the EASDF address and corresponding priority information to the UE for the UE to decide on its DNS policy. Optionally, after learning the UE's DNS policy, the SMF reports or redirects DNS information according to the operator's policy. This ensures optimal EAS selection in edge computing application scenarios, optimizes latency and routing, and guarantees a good user experience.

[0234] refer to Figure 7 As shown, the method provided in this disclosure embodiment may include the following steps:

[0235] 1. PDU Session Creation Process: In this PDU session creation process, the UE sends a PDU session establishment request to the SMF.

[0236] 2. During the PDU session establishment process, the SMF performs EASDF selection, choosing an EASDF as the DNS server for the PDU session based on the UE's subscription information. The SMF obtains EAS deployment information through PCF PDU session-related policies, or the SMF pre-configures EAS deployment information based on the UE's subscription, and selects an EASDF according to the EAS deployment information.

[0237] If the SMF determines, based on its local configuration, that the interaction between the EASDF and the DNS Server in the DN needs to be conducted via PSAUPF, then the SMF configures PSA UPF within the N4 rule to forward DNS messages between the EASDF and the DN.

[0238] 3. The SMF sends a Neasdf_DNSContext_Create Request to the selected EASDF, carrying information such as the UE IP address, SUPI, DNN, notification endpoint, and DNS processing rules.

[0239] After completing this process, the SMF sends the EASDF IP address as a DNS server to the UE in the PDU Session Establishment Accept message. The UE configures EASDF as the DNS server for this PDU session, unless:

[0240] The application indicates that its DNS configuration cannot be rewritten;

[0241] The application did not explicitly state that its DNS configuration could be rewritten;

[0242] UE has private DNS configuration

[0243] If the user has configured private DNS information on the UE that can be applied to all PDU sessions, after receiving the EASDF DNS information from the network side, the UE can report the configuration of private DNS information to the network side in the following ways:

[0244] RRC, N2, and Nsmf_PDUSession_UpdateSMContext Request are shown in Figure 9.

[0245] If the SMF receives a notification that the UE has a private DNS configuration, steps 5 through 19 below will no longer be executed.

[0246] 4. EASDF creates a DNS context for the PDU session and stores the UE IP address, SUPI, notification endpoint, and any DNS processing rules that may be provided in the DNS context. EASDF calls the service operation Neasdf_DNSContext_CreateResponse and sends a response message to SMF.

[0247] 5. The SMF can call the Neasdf_DNSContext_Update Request(EASDF context ID, DNS processing rule) to the EASDF. The conditions for triggering the update process include, but are not limited to: the UE moving to a new location, or the EASDF reporting certain FQDN EASDF DNS queries, or the insertion / deletion of a local PSA causing an update to the DNS processing rule.

[0248] 6. EASDF responds to the Neasdf_DNSContext_Update Response by sending an update response message to SMF.

[0249] 7. The terminal UE sends a DNS query message to EASDF.

[0250] The UE previously received priority indications for EASDF address and DNS information provided by SMF. Based on the priority indications, it made DNS policy decisions and sent DNS queries to the Edge Application Server Discovery Function (EASDF). EASDF then performed the discovery or selection of the edge application server.

[0251] 8. If the query message conforms to the processing rules for DNS message reporting, EASDF reports the DNS message to SMF by calling Neasdf_DNSContext_Notify Request.

[0252] 9. SMF responds with the Neasdf_DNSContext_Notify Response, sending the response message to EASDF.

[0253] 10. If the DNS processing rules for the FQDN received in the report need to be updated, for example, to provide updated information to build EDNS Client Subnet option information, SMF will call Neasdf_DNSContext_Update Request(DNS processing rule) to EASDF.

[0254] For option A, the DNS processing rule includes the corresponding IP address used to construct the EDNS client subnet option. For option B, the DNS processing rule includes the corresponding "local DNS server IP address". The DNS processing rule can also instruct EASDF to simply forward DNS queries to a pre-configured DNS server / resolver.

[0255] 11. EASDF responds to the Neasdf_DNSContext_Update Response by sending a response message to SMF.

[0256] 12. EASDF processes DNS query messages received from the terminal UE, specifically as follows:

[0257] - For option A mentioned above, EASDF adds the EDNS client subnet option to the DNS query message and sends it to the C-DNS server;

[0258] - For option B mentioned above, EASDF sends a DNS Query message to the local DNS server.

[0259] If no DNS message detection template in the DNS processing rules provided by SMF matches the FQDN requested in the DNS Query, then EASDF can directly send the DNS Query to the pre-configured DNS server / resolver.

[0260] 13. EASDF receives the DNS Response from the DNS system and determines whether it can be sent to the UE.

[0261] 14. If the EAS IP address or FQDN in the DNS response message matches the reporting criteria provided by the SMF, EASDF can send a DNS message to the SMF, including the EAS information, by invoking the Neasdf_DNSContext_Notify request. If EASDF receives multiple EAS IP addresses from the contacted DNS server, the DNS message report may contain multiple EAS IP addresses. The DNS message report may include the FQDN and EDNS client subnet options received in the DNS response message.

[0262] Upon receiving DNS processing rules, EASDF first caches the DNS Response message until it receives notification from the SMF before sending it to the UE. If DNS response message caching and reporting are requested and single-report control is set, EASDF will perform a report to the SMF once it detects a DNS message detection template match.

[0263] 15. SMF calls Neasdf_DNSContext_Notify to respond to service operations.

[0264] 16. SMF can optionally perform the selection and insertion of the uplink classifier or the local session anchor UPF, and select and insert ULCL / BP and Local PSA.

[0265] Based on EAS information received from EASDF, other UPF selection criteria, and service experience or performance analysis of edge applications, SMF can determine DNAI and N6 data routing information related to DNAS. SMF can optionally perform UL CL / BP and Local PSA selection and insertion. In the UL CL case, SMF determines traffic detection rules and data routing rules based on the IP address range of each DNAI.

[0266] 17. The SMF calls the Neasdf_DNSContext_Update Request to send a request message to the EASDF, carrying the DNS processing rules. The DNS processing rules instruct the EASDF to send the cached DNS response message to the terminal UE.

[0267] 18. EASDF responds to the Neasdf_DNSContext_Update Response by sending a response message to SMF.

[0268] 19. EASDF sends a DNS response to the terminal UE.

[0269] refer to Figure 8 As shown, PDU session establishment and context update may include:

[0270] 1. The UE establishes a PDU session establishment request with the access network (AN). RAN is the radio access network (AN).

[0271] 2. AMF should be selected as SMF;

[0272] 3. The AMF sends an Nsmf_PDUSession_CreateSMContext Request to the selected SMF;

[0273] 4. SMF obtains or updates contract data from User Data Management (UDM);

[0274] 5. The SMF sends an Nsmf_PDUSession_CreateSMContext Response to the AMF;

[0275] 6. PDU session authentication / authorization;

[0276] 7a. Select PCF;

[0277] 7b. Establishing / modifying session management policy associations;

[0278] 8. Select UPF;

[0279] 9. SMF initiates SM policy association modification;

[0280] 10a. The SMF sends an N4 Session Establishment / Modification Request to the UPF;

[0281] 10b UPF sends an N4 Session Establishment / Modification Response to SMF;

[0282] 11. SMF sends N1N2 message transfer to AMF (Namf_Communication_N1N2MessageTransfer);

[0283] 12. The AMF sends an N2 PDU Session Request to the (R)AN, which is a NAS message.

[0284] 13. (R)AN sends access network resource setup (PDU sessionestablishment accept) to UE;

[0285] 14. N2 PDU Session Response;

[0286] The transmission of the first uplink data;

[0287] 15. The AMF sends a PDU session context update request (Nsmf_PDUSession_UpdateSMContextRequest) to the SMF;

[0288] 16. SMF registers with UDM.

[0289] 17. The SMF returns a PDU session context update response (Nsmf_PDUSession_UpdateSMContextResponse) to the AMF;

[0290] 18. PDU session context status notification (Nsmf_PDUSession_SMContextStatusNotify);

[0291] 19. IPv6 address determined;

[0292] 20. SMF initiates SM policy association modification.

[0293] 21. SMF's contract data for unsubscribing from UDM.

[0294] like Figure 9A As shown in the figure, this disclosure provides a DNS configuration processing apparatus, wherein the apparatus includes:

[0295] The first determining module 120 is configured to determine the DNS configuration used by the UE based on the first DNS configuration selected by the network device for the UE if the UE is not configured with a second DNS configuration that meets preset conditions.

[0296] In some embodiments, such as Figure 9B As shown, the DNS configuration processing device may further include:

[0297] The first receiving module 110 is configured to receive a second DNS configuration sent by a network device such as SMF.

[0298] The DNS configuration processing unit can be included in the UE.

[0299] In one embodiment, the first receiving module 110 and / or the first determining module 120 may be a program module; after the program module is executed by the processor, it can receive the second DNS configuration sent by the SMF and determine the DNS configuration finally used by the UE, i.e. the DNS configuration that is effective in the UE, based on the second DNS configuration and the first DNS configuration.

[0300] In another embodiment, the first receiving module 110 and / or the first determining module 120 may be a hardware-software hybrid module, which includes, but is not limited to, various programmable arrays; the programmable arrays include, but are not limited to, field-programmable arrays and / or complex programmable arrays.

[0301] In another embodiment, the first receiving module 110 and / or the first determining module 120 may be pure hardware modules; the pure hardware modules include, but are not limited to, application-specific integrated circuits.

[0302] In one embodiment, the first determining module 120 is configured to determine to use the second DNS configuration when the first DNS configuration does not meet the preset conditions; or to determine to use the first DNS configuration when the first DNS configuration meets the preset conditions.

[0303] In one embodiment, the first DNS configuration satisfying the preset condition includes at least one of the following:

[0304] The first DNS configuration is the UE's private DNS configuration;

[0305] The first DNS configuration is the application's DNS configuration, and the first DNS configuration is a DNS configuration that is prohibited from being rewritten.

[0306] In one embodiment, the first DNS configuration is a DNS configuration that prohibits rewriting, including:

[0307] The application indicates that the first DNS configuration is a DNS configuration that cannot be rewritten;

[0308] or,

[0309] The application did not indicate that the first DNS configuration was a rewriteable DNS configuration.

[0310] In one embodiment, the apparatus further includes:

[0311] The first sending module is configured to send feedback information to the network side when determining the DNS server of the UE according to the first DNS configuration, wherein the feedback information indicates that the UE does not use the second DNS configuration, or the feedback information indicates whether the UE uses the second DNS configuration.

[0312] In one embodiment, the first sending module is configured to send the feedback information to the network side when determining the DNS server of the UE based on the UE's private DNS configuration.

[0313] In one embodiment, the second DNS configuration includes:

[0314] SMF is the address information of the Edge Application Server Discovery Function (EASDF) selected by the UE.

[0315] like Figure 10 As shown in the figure, this disclosure provides a DNS configuration processing apparatus, wherein the apparatus includes:

[0316] The second determining module 210 is configured to determine the second DNS configuration;

[0317] The second sending module 220 is configured to send a second DNS configuration to the UE, wherein the second DNS configuration is used to enable the UE to obtain DNS services;

[0318] The second receiving module 230 is configured to receive feedback information;

[0319] The stop module 240 is configured to stop maintaining the DNS processing rules corresponding to the second DNS configuration when the feedback information indicates that the UE does not use the second DNS configuration.

[0320] The DNS configuration processing unit may be contained in the SMF.

[0321] In one embodiment, the second determining module 210, the second sending module 220, the second receiving module 230, and the stopping module 240 can all be program modules. After being executed by the processor, the program module can realize the operation of each of the above modules.

[0322] In another embodiment, the second determining module 210, the second sending module 220, the second receiving module 230, and the stopping module 240 may all be hardware-software hybrid modules; the hardware-software hybrid modules include, but are not limited to, various programmable arrays; the programmable arrays include, but are not limited to, field-programmable arrays and / or complex programmable arrays.

[0323] In some embodiments, the second determining module 210, the second sending module 220, the second receiving module 230, and the stopping module 240 may all be pure hardware modules, including but not limited to application-specific integrated circuits.

[0324] In one embodiment, the second receiving module 230 is configured to receive a PDU session update uplink request message carrying the feedback information.

[0325] like Figure 11 As shown in the figure, this disclosure provides a DNS configuration processing apparatus, wherein the apparatus includes:

[0326] The third receiving module 310 is configured to receive feedback information from the UE, wherein the feedback information indicates that the UE does not use the second DNS configuration, or the feedback information indicates whether the UE uses the second DNS configuration;

[0327] The third sending module 320 is configured to send the feedback information to the AMF, wherein the feedback information is used by the AMF to forward it to the SMF, and by the SMF to determine to stop maintaining the DNS processing rules corresponding to the second DNS configuration.

[0328] In one embodiment, the third receiving module 310 and the third sending module 320 can both be program modules. After being executed by the processor, the program module can realize the operation of the above-mentioned modules.

[0329] In another embodiment, the third receiving module 310 and the third transmitting module 320 may both be hardware-software hybrid modules; the hardware-software hybrid modules include, but are not limited to, various programmable arrays; the programmable arrays include, but are not limited to, field-programmable arrays and / or complex programmable arrays.

[0330] In some embodiments, the third receiving module 310 and the third transmitting module 320 may both be pure hardware modules, including but not limited to application-specific integrated circuits.

[0331] In one embodiment, the third receiving module 310 is configured to receive a response message carrying the feedback information in the form of a PDU session establishment acceptance message.

[0332] In one embodiment, the third sending module 320 is configured to send an N2 PDU session response message carrying the feedback information to the AMF.

[0333] In one embodiment, the third receiving module 310 is configured to receive a response message carrying the feedback information in the form of a PDU session establishment acceptance message.

[0334] In one embodiment, the third sending module 320 is configured to send an N2 PDU session response message carrying the feedback information to the AMF.

[0335] like Figure 12 As shown in the figure, this disclosure provides a DNS configuration processing apparatus, wherein the apparatus includes:

[0336] The fourth receiving module 410 is configured to receive feedback information from the UE forwarded by the base station;

[0337] The fourth sending module 420 is configured to send the feedback information to the AMF, wherein the feedback information indicates that when the UE does not use the second DNS configuration, it is used by the SMF to determine to stop maintaining the DNS processing rules corresponding to the second DNS configuration.

[0338] In one embodiment, the fourth receiving module 410 and the fourth sending module 420 may both be program modules. After being executed by the processor, the program modules can perform the operations of the above-mentioned modules.

[0339] In another embodiment, the fourth receiving module 410 and the fourth transmitting module 420 may both be hardware-software hybrid modules; the hardware-software hybrid modules include, but are not limited to, various programmable arrays; the programmable arrays include, but are not limited to, field-programmable arrays and / or complex programmable arrays.

[0340] In some embodiments, the fourth receiving module 410 and the fourth transmitting module 420 may both be pure hardware modules, including but not limited to application-specific integrated circuits.

[0341] In one embodiment, the fourth receiving module 410 is configured to receive an N2PDU session response message carrying the feedback information.

[0342] This disclosure provides a communication device, including:

[0343] Memory used to store processor-executable instructions;

[0344] The processor is connected to the memory separately;

[0345] The processor is configured to execute the control method and / or information processing method of the terminal provided by any of the aforementioned technical solutions.

[0346] The processor may include various types of storage media, which are non-transitory computer storage media that can continue to store information after the communication device loses power.

[0347] Here, the communication equipment includes: an access device or a UE, or a core network device. The access network device may include at least the aforementioned base station. The core network device may include at least the aforementioned SMF and / or AMF.

[0348] The processor can be connected to the memory via a bus or similar means to read executable programs stored in the memory, for example, such as... Figures 2A to 8 At least one of the methods shown.

[0349] Figure 13 This is a block diagram illustrating a UE 800 according to an exemplary embodiment. For example, the UE 800 may be a mobile phone, computer, digital broadcast user equipment, messaging transceiver, game console, tablet device, medical device, fitness equipment, personal digital assistant, etc.

[0350] Reference Figure 13 UE800 may include one or more of the following components: processing component 802, memory 804, power supply component 806, multimedia component 808, audio component 810, input / output (I / O) interface 812, sensor component 814, and communication component 816.

[0351] Processing component 802 typically controls the overall operation of UE 800, such as operations associated with display, telephone calls, data communication, camera operation, and recording. Processing component 802 may include one or more processors 820 to execute instructions to complete all or part of the steps of the methods described above. Furthermore, processing component 802 may include one or more modules to facilitate interaction between processing component 802 and other components. For example, processing component 802 may include a multimedia module to facilitate interaction between multimedia component 808 and processing component 802.

[0352] Memory 804 is configured to store various types of data to support operation on UE 800. Examples of this data include instructions for any application or method operating on UE 800, contact data, phonebook data, messages, pictures, videos, etc. Memory 804 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0353] Power supply component 806 provides power to various components of UE800. Power supply component 806 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to UE800.

[0354] The multimedia component 808 includes a screen that provides an output interface between the UE 800 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touchscreen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors may sense not only the boundaries of the touch or swipe action but also the duration and pressure associated with the touch or swipe operation. In some embodiments, the multimedia component 808 includes a front-facing camera and / or a rear-facing camera. When the UE 800 is in an operating mode, such as a shooting mode or a video mode, the front-facing camera and / or the rear-facing camera may receive external multimedia data. Each front-facing camera and rear-facing camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

[0355] Audio component 810 is configured to output and / or input audio signals. For example, audio component 810 includes a microphone (MIC) configured to receive external audio signals when UE 800 is in an operating mode, such as call mode, recording mode, and voice recognition mode. The received audio signals may be further stored in memory 804 or transmitted via communication component 816. In some embodiments, audio component 810 also includes a speaker for outputting audio signals.

[0356] I / O interface 812 provides an interface between processing component 802 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to, home buttons, volume buttons, power buttons, and lock buttons.

[0357] Sensor assembly 814 includes one or more sensors for providing status assessments of various aspects of UE 800. For example, sensor assembly 814 can detect the on / off state of UE 800, the relative positioning of components such as the display and keypad of UE 800, changes in the position of UE 800 or one of its components, the presence or absence of user contact with UE 800, the orientation or acceleration / deceleration of UE 800, and temperature changes of UE 800. Sensor assembly 814 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor assembly 814 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, sensor assembly 814 may also include an accelerometer, a gyroscope, a magnetometer, a pressure sensor, or a temperature sensor.

[0358] Communication component 816 is configured to facilitate wired or wireless communication between UE 800 and other devices. UE 800 can access wireless networks based on communication standards, such as WiFi, 2G, or 3G, or combinations thereof. In one exemplary embodiment, communication component 816 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, communication component 816 also includes a near-field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on radio frequency identification (RFID) technology, Infrared Data Association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0359] In an exemplary embodiment, UE800 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the methods described above.

[0360] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 804 including instructions, which can be executed by the processor 820 of the UE 800 to perform the above-described method. For example, the non-transitory computer-readable storage medium may be a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc.

[0361] like Figure 14 As shown in the illustration, one embodiment of this disclosure illustrates the structure of an access device. For example, the communication device 900 can be provided as a network-side device. This communication device can be the aforementioned access device and / or core network device.

[0362] Reference Figure 14 The communication device 900 includes a processing component 922, which further includes one or more processors, and memory resources represented by a memory 932 for storing instructions, such as application programs, that can be executed by the processing component 922. The application programs stored in the memory 932 may include one or more modules, each corresponding to a set of instructions. Furthermore, the processing component 922 is configured to execute instructions to perform any of the methods described above applied to the access device, such as... Figures 2A to 8 The method shown.

[0363] The communication device 900 may also include a power supply component 1926 configured to perform power management of the communication device 900, a wired or wireless network interface 950 configured to connect the communication device 900 to a network, and an input / output (I / O) interface 958. The communication device 900 can operate on an operating system stored in memory 932, such as Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™, or similar.

[0364] Other embodiments of the invention will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the invention that follow the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of the invention are indicated by the following claims.

[0365] It should be understood that the present invention is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of the invention is limited only by the appended claims.

Claims

1. A method for configuring and processing Domain Name System (DNS), wherein, The method, executed by the user equipment (UE), includes: Receive the second DNS configuration sent by SMF; The DNS configuration used by the UE is determined based on the second DNS configuration and the first DNS configuration; The method further includes: If the first DNS configuration does not meet the preset conditions, the second DNS configuration will be used. or; When the first DNS configuration meets the preset conditions, it is determined that the first DNS configuration will be used; The first DNS configuration satisfies at least one of the following preset conditions: The first DNS configuration is the UE's private DNS configuration, wherein the UE's private DNS configuration applies to all applications installed within the UE; The first DNS configuration is the application's DNS configuration, and the first DNS configuration is a DNS configuration that is prohibited from being rewritten.

2. The method according to claim 1, wherein, The first DNS configuration is a DNS configuration that prohibits rewriting, including: The application indicates that the first DNS configuration is a DNS configuration that cannot be rewritten; or, The application did not indicate that the first DNS configuration was a rewriteable DNS configuration.

3. The method according to claim 1 or 2, wherein, The method further includes: When determining the DNS server of the UE according to the first DNS configuration, feedback information is sent to the network side, wherein the feedback information indicates that the UE does not use the second DNS configuration, or the feedback information indicates whether the UE uses the second DNS configuration.

4. The method according to claim 3, wherein, When determining the DNS server for the UE based on the first DNS configuration, sending feedback information to the network side includes: When determining the DNS server for the UE based on its private DNS configuration, the feedback information is sent to the network side.

5. The method according to any one of claims 1-4, wherein, The second DNS configuration includes: The SMF is the address information of the Edge Application Server Discovery Function (EASDF) selected by the UE.

6. A DNS configuration processing method, wherein, Executed by SMF, the method includes: Determine the secondary DNS configuration; A second DNS configuration is sent to the UE, wherein the second DNS configuration is used for the UE to determine the DNS configuration to be used by the UE based on the second DNS configuration and the first DNS configuration. When the first DNS configuration does not meet a preset condition, the UE determines to use the second DNS configuration; or, when the first DNS configuration meets the preset condition, the UE determines to use the first DNS configuration. Wherein, the first DNS configuration satisfies at least one of the following preset conditions: The first DNS configuration is the UE's private DNS configuration, wherein the UE's private DNS configuration applies to all applications installed within the UE; The first DNS configuration is the application's DNS configuration, and the first DNS configuration is a DNS configuration that prohibits rewriting; Receive feedback information; When the feedback information indicates that the UE does not use the second DNS configuration, the maintenance of the DNS processing rules corresponding to the second DNS configuration is stopped.

7. The method according to claim 6, wherein, The received feedback information includes: Receive a PDU session update uplink request message carrying the feedback information.

8. A DNS configuration processing method, wherein, The method, executed by the base station, includes: The system receives feedback information from the UE, wherein the feedback information is sent by the UE after determining the DNS configuration to be used by the UE based on a second DNS configuration and a first DNS configuration. Specifically, if the first DNS configuration does not meet a preset condition, the UE determines to use the second DNS configuration; or, if the first DNS configuration meets the preset condition, the UE determines to use the first DNS configuration. The first DNS configuration meeting the preset condition includes at least one of the following: The first DNS configuration is the UE's private DNS configuration, wherein the UE's private DNS configuration applies to all applications installed within the UE; The first DNS configuration is the application's DNS configuration, and the first DNS configuration is a DNS configuration that prohibits rewriting; Wherein, the feedback information indicates that the UE does not use the second DNS configuration, or the feedback information indicates whether the UE uses the second DNS configuration; The feedback information is sent to the AMF, wherein the feedback information is used by the AMF to forward it to the SMF, and by the SMF to determine to stop maintaining the DNS processing rules corresponding to the second DNS configuration.

9. The method according to claim 8, wherein, The receiving of feedback information from the UE includes: A response message is received that carries the feedback information and indicates that the session establishment accepts the PDU message.

10. The method according to claim 9, wherein, Sending the feedback information to the AMF includes: Send an N2 PDU session response message carrying the feedback information to the AMF.

11. A DNS configuration processing method, wherein, Executed by AMF, the method includes: The system receives feedback information forwarded by the base station from the UE, wherein the feedback information is sent by the UE after determining the DNS configuration to be used by the UE based on a second DNS configuration and a first DNS configuration, wherein the UE determines to use the second DNS configuration when the first DNS configuration does not meet a preset condition; or, the UE determines to use the first DNS configuration when the first DNS configuration meets the preset condition; wherein the first DNS configuration meeting the preset condition includes at least one of the following: The first DNS configuration is the UE's private DNS configuration, wherein the UE's private DNS configuration applies to all applications installed within the UE; The first DNS configuration is the application's DNS configuration, and the first DNS configuration is a DNS configuration that prohibits rewriting; The feedback information is sent to the SMF, wherein the feedback information indicates that when the UE does not use the second DNS configuration, the SMF determines to stop maintaining the DNS processing rules corresponding to the second DNS configuration.

12. The method according to claim 11, wherein, The feedback information from the UE forwarded by the base station includes: Receive an N2 PDU session response message carrying the feedback information.

13. A DNS configuration processing apparatus, wherein, The device, applied to a user equipment (UE), includes: The first receiving module is configured to receive the second DNS configuration sent by the SMF; The first determining module is configured to determine the DNS configuration used by the UE based on the second DNS configuration and the first DNS configuration; The first determining module is further configured to determine to use the second DNS configuration when the first DNS configuration does not meet the preset conditions; or to determine to use the first DNS configuration when the first DNS configuration meets the preset conditions. The first DNS configuration satisfies at least one of the following preset conditions: The first DNS configuration is the UE's private DNS configuration; The first DNS configuration is the application's DNS configuration, and the first DNS configuration is a DNS configuration that is prohibited from being rewritten.

14. The apparatus according to claim 13, wherein, The first DNS configuration is a DNS configuration that prohibits rewriting, including: The application indicates that the first DNS configuration is a DNS configuration that cannot be rewritten; or, The application did not indicate that the first DNS configuration was a rewriteable DNS configuration.

15. The apparatus according to claim 13 or 14, wherein, The device further includes: The first sending module is configured to send feedback information to the network side when determining the DNS server of the UE according to the first DNS configuration, wherein the feedback information indicates that the UE does not use the second DNS configuration, or the feedback information indicates whether the UE uses the second DNS configuration.

16. The apparatus according to claim 15, wherein, The first sending module is configured to send the feedback information to the network side when determining the DNS server of the UE based on the UE's private DNS configuration.

17. The apparatus according to any one of claims 13 to 16, wherein, The second DNS configuration includes: SMF is the address information of the Edge Application Server Discovery Function (EASDF) selected by the UE.

18. A DNS configuration processing apparatus, wherein, Applied to SMF, the device includes: The second determining module is configured to determine the second DNS configuration; The second sending module is configured to send a second DNS configuration to the UE, wherein the second DNS configuration is used for the UE to determine the DNS configuration to be used by the UE based on the second DNS configuration and the first DNS configuration. When the first DNS configuration does not meet a preset condition, the UE determines to use the second DNS configuration; or, when the first DNS configuration meets the preset condition, the UE determines to use the first DNS configuration. Wherein, the first DNS configuration satisfies at least one of the following preset conditions: The first DNS configuration is the UE's private DNS configuration, wherein the UE's private DNS configuration applies to all applications installed within the UE; The first DNS configuration is the application's DNS configuration, and the first DNS configuration is a DNS configuration that prohibits rewriting; The second receiving module is configured to receive feedback information; The stop module is configured to stop maintaining the DNS processing rules corresponding to the second DNS configuration when the feedback information indicates that the UE does not use the second DNS configuration.

19. The apparatus according to claim 18, wherein, The second receiving module is configured to receive a PDU session update uplink request message carrying the feedback information.

20. A DNS configuration processing apparatus, wherein, Applied to a base station, the device includes: The third receiving module is configured to receive feedback information from the UE, wherein the feedback information is sent by the UE after determining the DNS configuration to be used by the UE based on the second DNS configuration and the first DNS configuration, wherein the UE determines to use the second DNS configuration when the first DNS configuration does not meet a preset condition; or, the UE determines to use the first DNS configuration when the first DNS configuration meets the preset condition; wherein the first DNS configuration meeting the preset condition includes at least one of the following: The first DNS configuration is the UE's private DNS configuration, wherein the UE's private DNS configuration applies to all applications installed within the UE; The first DNS configuration is the application's DNS configuration, and the first DNS configuration is a DNS configuration that prohibits rewriting; Wherein, the feedback information indicates that the UE does not use the second DNS configuration, or the feedback information indicates whether the UE uses the second DNS configuration; The third sending module is configured to send the feedback information to the AMF, wherein the feedback information is used by the AMF to forward it to the SMF, and by the SMF to determine to stop maintaining the DNS processing rules corresponding to the second DNS configuration.

21. The apparatus according to claim 20, wherein, The third receiving module is configured to receive a response message of a PDU session establishment acceptance message carrying the feedback information.

22. The apparatus according to claim 21, wherein, The third sending module is configured to send an N2 PDU session response message carrying the feedback information to the AMF.

23. A DNS configuration processing apparatus, wherein, Applied to AMF, the device includes: The fourth receiving module is configured to receive feedback information from the UE forwarded by the base station. The feedback information is sent by the UE after determining the DNS configuration to be used by the UE based on a second DNS configuration and a first DNS configuration. Specifically, if the first DNS configuration does not meet a preset condition, the UE determines to use the second DNS configuration; or, if the first DNS configuration meets the preset condition, the UE determines to use the first DNS configuration. The first DNS configuration meeting the preset condition includes at least one of the following: The first DNS configuration is the UE's private DNS configuration, wherein the UE's private DNS configuration applies to all applications installed within the UE; The first DNS configuration is the application's DNS configuration, and the first DNS configuration is a DNS configuration that prohibits rewriting; The fourth sending module is configured to send the feedback information to the SMF, wherein the feedback information indicates that when the UE does not use the second DNS configuration, it is used by the SMF to determine to stop maintaining the DNS processing rules corresponding to the second DNS configuration.

24. The apparatus according to claim 23, wherein, The fourth receiving module is configured to receive an N2 PDU session response message carrying the feedback information.

25. A communication device, comprising a processor, a transceiver, a memory, and an executable program stored in the memory and capable of being executed by the processor, wherein, When the processor runs the executable program, it performs the method provided as claimed in any one of claims 1 to 5, 6 to 7, 8 to 10, or 11 to 12.

26. A computer storage medium storing an executable program; the executable program, when executed by a processor, is capable of implementing the method provided in any one of claims 1 to 5, 6 to 7, 8 to 10, or 11 to 12.

Images