WO2022007657A1 - 一种域名系统请求的发送方法及装置 - Google Patents

一种域名系统请求的发送方法及装置 Download PDF

Info

Publication number
WO2022007657A1
WO2022007657A1 PCT/CN2021/102830 CN2021102830W WO2022007657A1 WO 2022007657 A1 WO2022007657 A1 WO 2022007657A1 CN 2021102830 W CN2021102830 W CN 2021102830W WO 2022007657 A1 WO2022007657 A1 WO 2022007657A1
Authority
WO
WIPO (PCT)
Prior art keywords
address
dns
request information
dns request
terminal device
Prior art date
Application number
PCT/CN2021/102830
Other languages
English (en)
French (fr)
Inventor
姚琦
宗在峰
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP21838923.7A priority Critical patent/EP4171086A4/en
Publication of WO2022007657A1 publication Critical patent/WO2022007657A1/zh
Priority to US18/150,591 priority patent/US20230164111A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4552—Lookup mechanisms between a plurality of directories; Synchronisation of directories, e.g. metadirectories

Definitions

  • the present application relates to the field of communication technologies, and in particular, to a method and apparatus for sending a domain name system request.
  • a packet data unit (PDU) session (session) is connected to a data network (DN) through a packet data unit session anchor (PSA) network element, thereby enabling the terminal device to communicate with the DN.
  • the application server application server, AS
  • the PSA network element is also connected in communication with a domain name system (domain name system, DNS) server.
  • DNS domain name system
  • the DNS server receives the DNS request information from the PSA network element, parses the domain name in the DNS request information, and obtains the Internet protocol of the application server.
  • the (internet protocol, IP) address is then provided to the terminal device through the PSA network element, so that the terminal device realizes data transmission with the application server according to the IP address of the application server.
  • multi-homing multi-homing
  • multiple PSA network elements exist in one PDU session.
  • User plane paths leading to different PSA network elements are branched at branch point (BP) equipment.
  • One PSA network element corresponds to one DNS server, and different PSA network elements correspond to different DNS servers.
  • the terminal device includes multiple addresses and corresponds to multiple PSA network elements.
  • One address of the terminal device corresponds to one PSA network element, and different addresses of the terminal device correspond to different PSA network elements.
  • the source (source) address in the DNS request information is an address of the terminal device and corresponds to a PSA network element
  • the destination (destination) address in the DNS request information is a address of the DNS server. If there is no correspondence between the PSA network element corresponding to the source address in a DNS request message and the DNS server corresponding to the destination address, that is, the PSA network element corresponding to the source address and the DNS server corresponding to the destination address cannot communicate, the error occurs. The phenomenon of "DNS resolution failure" results in low DNS resolution efficiency.
  • Embodiments of the present application provide a method and device for sending a domain name system request, which can improve DNS resolution efficiency.
  • an embodiment of the present application provides a method for sending a domain name system request, and the execution body of the method may be a terminal device or a chip applied in the terminal device.
  • the following description will be given by taking the execution subject being a terminal device as an example.
  • the method includes: the terminal device determines the address of the first domain name system DNS server corresponding to the first application.
  • the terminal device determines the first address of the terminal device according to the address of the first DNS server and the address of the terminal device corresponding to the address of the first DNS server. After that, the terminal device transmits DNS request information.
  • the DNS request information includes the identifier of the first application, the address of the first DNS server, and the first address of the terminal device.
  • the first DNS server corresponds to the first address of the terminal device
  • the PSA network elements can communicate with each other. Since the DNS request information sent by the terminal device includes the address of the first DNS server and the first address of the terminal device, the DNS request information can be transmitted to the first DNS server through the PSA network element corresponding to the terminal device, thereby improving the DNS performance.
  • the success rate of resolution reduces the phenomenon of "DNS resolution failure" caused by "inability to communicate between the DNS server and the PSA network element" in the prior art.
  • the method for sending a domain name system request in this embodiment of the present application further includes: the terminal device receiving the address of the first DNS server from the SMF network element of the session management function and the terminal device corresponding to the address of the first DNS server the address of.
  • the terminal device receiving the address of the first DNS server from the SMF network element of the session management function and the terminal device corresponding to the address of the first DNS server the address of.
  • the SMF network element can provide the terminal device with the information of "the address of the first DNS server and the address of the terminal device corresponding to the address of the first DNS server".
  • determining the address of the first DNS server corresponding to the first application by the terminal device includes: the terminal device receiving the identifier of the first application from the SMF network element and the identifier of the DNS server corresponding to the identifier of the first application. address. For example, "the identifier of the first application and the address of the DNS server corresponding to the identifier of the first application" may be carried in a routing rule and transmitted to the terminal device. Afterwards, the terminal device determines the address of the first DNS server according to the identifier of the first application and the address of the DNS server corresponding to the identifier of the first application.
  • the terminal device can determine the first DNS server according to the information provided by the SMF network element the address of.
  • the identifier of the first application corresponds to multiple DNS servers.
  • the terminal device determines the address of the first DNS server according to the identifier of the first application and the address of the DNS server corresponding to the identifier of the first application.
  • the preset policy includes at least one of the following: the priority of the first DNS server satisfies the priority condition among the priorities of the plurality of DNS servers; the distance between the first DNS server and the terminal device satisfies the separation distance condition.
  • the terminal device can determine one DNS server from the multiple DNS servers according to a preconfigured preset policy, as the first DNS server, and then determine the first DNS server The address of the server.
  • an embodiment of the present application provides a method for sending a domain name system request, and the execution body of the method may be a branch point BP device, or a chip applied in the BP device.
  • the following description takes the execution subject being a BP device as an example.
  • the method includes: the BP device receives the domain name system DNS request information from the terminal device, and then the BP device updates at least one of the source address and the destination address in the DNS request information to obtain the updated DNS request information.
  • the source address in the updated DNS request information is the first address of the terminal device, and the destination address in the updated DNS request information is the address of the first DNS server.
  • the BP device sends the updated DNS request information to the first packet data unit session anchor PSA network element according to the source address in the updated DNS request information.
  • the first PSA network element corresponds to the first address of the terminal device, and the destination address in the updated DNS request information is used by the first PSA network element to send the updated DNS request information to the first DNS server, enabling the first The DNS server resolves the updated DNS request information.
  • the destination address in the updated DNS request information is the address of the first DNS server.
  • the first PSA network element corresponding to the first address of the terminal device can communicate with the first DNS server. In this way, the updated DNS request information can be transmitted to the first DNS server through the first PSA network element, thereby improving DNS resolution. This reduces the phenomenon of "DNS resolution failure" caused by "inability to communicate between the DNS server and the PSA network element" in the prior art.
  • the BP device updates at least one of the source address and the destination address in the DNS request information, including: the BP device updates the source address in the DNS request information according to the identifier of the first application in the DNS request information and at least one of the destination addresses, or the BP device updates the destination address in the DNS request information according to the source address in the DNS request information, or the BP device updates the destination address in the DNS request information according to the destination address in the DNS request information. source address.
  • the BP device in the process of updating the DNS request information by the BP device, can update the DNS request based on the identifier of the first application in the DNS request information, or the source address of the DNS request information, or the destination address of the DNS request information At least one of the source address and the destination address in the information to obtain the updated DNS request information.
  • the BP device updates at least one of the source address and the destination address in the DNS request information according to the identifier of the first application in the DNS request information, including: the BP device determines that the identifier of the first application corresponds to address of the first DNS server, and then the BP device updates the destination address in the DNS request information to the address of the first DNS server.
  • the BP device determines the first address of the terminal device according to the address of the first DNS server and the address of the terminal device corresponding to the address of the first DNS server, and then the BP device sets the source address in the DNS request information as the first address of the terminal device. address.
  • the BP device can update the source address and the destination address in the DNS request information based on the identifier of the first application, so as to obtain the updated DNS request information.
  • the BP device determines the address of the first DNS server corresponding to the identifier of the first application, including: the BP device receives the identifier of the first application and the identifier of the first application from the SMF network element of the session management function address of the corresponding DNS server, and then the BP device determines the address of the first DNS server according to the identifier of the first application and the address of the DNS server corresponding to the identifier of the first application.
  • the BP device can determine the first DNS according to the information provided by the SMF network element The address of the server.
  • the BP device updates the source address in the DNS request information according to the destination address in the DNS request information, including: if the destination address in the DNS request information is the address of the first DNS server, then the BP device according to The address of the first DNS server and the address of the terminal device corresponding to the address of the first DNS server determine the first address of the terminal device. After that, the BP device updates the source address in the DNS request information to the first address of the terminal device.
  • the BP device after receiving the DNS request information, the BP device replaces the source address in the DNS request information based on the destination address in the DNS request information, so as to ensure that the PSA network element corresponding to the source address in the updated DNS request information is the same as the source address in the updated DNS request information. Communication between the first DNS servers is possible.
  • the method for sending a domain name system request in this embodiment of the present application further includes: the BP device receives the address of the first DNS server from the SMF network element and the address of the terminal device corresponding to the address of the first DNS server.
  • the SMF network element can provide the BP device with the information of "the address of the first DNS server and the address of the terminal device corresponding to the address of the first DNS server".
  • the BP device updates the destination address in the DNS request information according to the source address in the DNS request information, including: if the source address in the DNS request information is the first address of the terminal device, then the BP device according to The first address of the terminal device and the address of the DNS server corresponding to the first address of the terminal device determine the address of the first DNS server. After that, the BP device updates the destination address in the DNS request information to the address of the first DNS server.
  • the BP device after receiving the DNS request information, the BP device replaces the destination address in the DNS request information based on the source address in the DNS request information, so as to ensure that the PSA network element corresponding to the source address in the updated DNS request information is the same as the source address in the DNS request information. Communication between the first DNS servers is possible.
  • the method for sending a domain name system request in this embodiment of the present application further includes: the BP device receives the first address of the terminal device from the SMF network element and the address of the DNS server corresponding to the first address of the terminal device.
  • the SMF network element can provide the BP device with the information of "the first address of the terminal device and the address of the DNS server corresponding to the first address of the terminal device".
  • the method for sending a domain name system request in this embodiment of the present application further includes: the BP device receives response information for the DNS request information from the first PSA network element. After that, the BP device updates at least one of the source address and the destination address in the response information, and obtains the updated response information.
  • the source address in the updated response information is the destination address of the pre-update DNS request information, and the destination address in the updated response information is the source address of the pre-update DNS request information.
  • the BP device sends the updated response information to the terminal device.
  • the DNS request information includes the identifier of the first application
  • the response information includes the Internet Protocol IP address of the application server corresponding to the first application.
  • the updated response information includes the IP address of the application server corresponding to the first application, the destination address of the DNS request information before the update, and the source address of the DNS request information before the update.
  • the terminal device After the terminal device sends the DNS request information, it needs to monitor the response message carrying the source address and destination address of the DNS request information before the update.
  • the BP device can replace at least one of the source address and the destination address in the response information, so as to ensure that the terminal device can monitor the response message carrying the source address and destination address of the DNS request information before updating.
  • an embodiment of the present application provides a method for sending a domain name system request.
  • the execution body of the method may be a branch point BP device, or a chip applied in the BP device.
  • the following description takes the execution subject being a BP device as an example.
  • the method includes: the BP device receives the domain name system DNS request information from the terminal device, and then the BP device sends the DNS request information to the first packet data unit session anchor PSA network element corresponding to the destination address according to the destination address in the DNS request information .
  • the DNS request information is used by the first PSA network element to send the DNS request information to the first DNS server, so as to enable the first DNS server to resolve the DNS request information.
  • the destination address of the DNS request information corresponds to the first PSA network element
  • the destination address of the DNS request information is the address of the first DNS server
  • the first DNS server and the first PSA network element can communicate with each other, which can reduce the number of The phenomenon of "DNS resolution failure" caused by "inability to communicate between the DNS server and the PSA network element" in the prior art improves the success rate of DNS resolution.
  • an embodiment of the present application provides a method for sending a domain name system request, where the execution body of the method may be the first PSA network element, or may be a chip applied in the first PSA network element.
  • the following description will be given by taking the execution subject being the first PSA network element as an example.
  • the method includes: the first PSA network element sends DNS request information to the first domain name system DNS server.
  • the DNS request information includes the address of the first DNS server and the second address of the terminal device corresponding to the second PSA network element.
  • the first PSA network element receives response information for the DNS request information from the first DNS server.
  • the first PSA network element sends response information to the branch point BP device according to the forwarding rule information.
  • the forwarding rule information is used to instruct the first PSA network element to send a data packet whose destination address is the second address to the BP device, and the data packet includes response information.
  • the response information is response information to the DNS request information. That is to say, in the process of the first DNS server feeding back the response information, after the first PSA network element receives the response information from the first DNS server, even if the destination address of the response information is the second address of the terminal device, the second PSA network element is not the same as the second PSA.
  • the first PSA network element can also send response information to the BP device according to the forwarding rule information, so that the response information can be provided to the terminal device through the BP device.
  • the method for sending a domain name system request in this embodiment of the present application further includes: the first PSA network element receives forwarding rule information from the session management function SMF network element. That is, the SMF network element provides the first PSA network element with forwarding rule information, so that the first PSA network element forwards the response information according to the forwarding rule information.
  • the first PSA network element receives response information for the DNS request information from the first DNS server, including: the first PSA network element passes through a tunnel between the first PSA network element and the first DNS server Response information to the DNS request information from the first DNS server is received.
  • the DNS request information includes the identifier of the first application
  • the response information includes the Internet Protocol IP address of the application server corresponding to the first application.
  • the tunnel between the first PSA network element and the first DNS server can shield the destination address in the response information, so that the response information can be transmitted from the first DNS server to the first PSA network element.
  • an embodiment of the present application provides an apparatus for sending a domain name system request, where the apparatus for sending a domain name system request includes: a unit for performing each step in any of the foregoing aspects.
  • the device for sending the domain name system request may be a terminal device in the first aspect or any possible design of the first aspect, or a chip that implements the function of the above-mentioned terminal device.
  • the device for sending a domain name system request includes corresponding modules, units, or means for implementing the above method, and the modules, units, or means can be implemented by hardware, software, or by executing corresponding software in hardware.
  • the hardware or software includes one or more modules or units corresponding to the above functions.
  • an embodiment of the present application provides a device for sending a domain name system request, including a processor and an interface circuit, where the processor is configured to communicate with other devices through the interface circuit, and execute the method for sending a domain name system request provided by any of the above aspects .
  • the processor includes one or more.
  • the device for sending the domain name system request may be a terminal device in the first aspect or any possible design of the first aspect, or a chip that implements the function of the above-mentioned terminal device.
  • an embodiment of the present application provides an apparatus for sending a domain name system request, including: a processor and a memory; the memory is used to store computer instructions, when the processor executes the instructions, so that the domain name system requests
  • the sending apparatus executes the method described in any one of the above aspects.
  • the device for sending the domain name system request may be a terminal device in the first aspect or any possible design of the first aspect, or a chip that implements the function of the above-mentioned terminal device.
  • an embodiment of the present application provides an apparatus for sending a domain name system request, including: a processor; the processor is configured to be coupled to a memory, and after reading an instruction in the memory, execute any of the above-mentioned steps according to the instruction.
  • the device for sending the domain name system request may be a terminal device in the first aspect or any possible design of the first aspect, or a chip that implements the function of the above-mentioned terminal device.
  • an embodiment of the present application provides an apparatus for sending a domain name system request, where the apparatus for sending a domain name system request includes: a unit for performing each step in any of the foregoing aspects.
  • the device for sending the domain name system request may be the BP device in the second aspect or any possible design of the second aspect, or a chip that implements the function of the above-mentioned BP device; or, the device for sending the domain name system request may be the above-mentioned first
  • the BP device in any of the three aspects or any possible design of the third aspect, or a chip that implements the functions of the above BP device.
  • the device for sending a domain name system request includes corresponding modules, units, or means for implementing the above method, and the modules, units, or means can be implemented by hardware, software, or by executing corresponding software in hardware.
  • the hardware or software includes one or more modules or units corresponding to the above functions.
  • an embodiment of the present application provides a device for sending a domain name system request, including a processor and an interface circuit, where the processor is configured to communicate with other devices through the interface circuit, and execute the method for sending a domain name system request provided in any of the above aspects .
  • the processor includes one or more.
  • the device for sending the domain name system request may be the BP device in the second aspect or any possible design of the second aspect, or a chip that implements the function of the above-mentioned BP device; or, the device for sending the domain name system request may be the above-mentioned first
  • the BP device in any of the three aspects or any possible design of the third aspect, or a chip that implements the functions of the above BP device.
  • an embodiment of the present application provides an apparatus for sending a domain name system request, including: a processor and a memory; the memory is used to store a computer instruction, and when the processor executes the instruction, the domain name system request
  • the sending apparatus performs the method described in any one of the above aspects.
  • the device for sending the domain name system request may be the BP device in the second aspect or any possible design of the second aspect, or a chip that implements the function of the above-mentioned BP device; or, the device for sending the domain name system request may be the above-mentioned first
  • the BP device in any of the three aspects or any possible design of the third aspect, or a chip that implements the functions of the above BP device.
  • an embodiment of the present application provides an apparatus for sending a domain name system request, including: a processor; the processor is configured to be coupled to a memory, and after reading an instruction in the memory, execute the above-mentioned method according to the instruction The method of any aspect.
  • the device for sending the domain name system request may be the BP device in the second aspect or any possible design of the second aspect, or a chip that implements the function of the above-mentioned BP device; or, the device for sending the domain name system request may be the above-mentioned first
  • the BP device in any of the three aspects or any possible design of the third aspect, or a chip that implements the functions of the above BP device.
  • an embodiment of the present application provides an apparatus for sending a domain name system request, where the apparatus for sending a domain name system request includes: a unit for performing each step in any of the foregoing aspects.
  • the device for sending the domain name system request may be the first PSA network element in the fourth aspect or any possible design of the fourth aspect, or a chip that implements the function of the first PSA network element.
  • the device for sending a domain name system request includes corresponding modules, units, or means for implementing the above method, and the modules, units, or means can be implemented by hardware, software, or by executing corresponding software in hardware.
  • the hardware or software includes one or more modules or units corresponding to the above functions.
  • an embodiment of the present application provides a device for sending a domain name system request, including a processor and an interface circuit, where the processor is configured to communicate with other devices through the interface circuit, and execute the sending of the domain name system request provided in any of the above aspects method.
  • the processor includes one or more.
  • the device for sending the domain name system request may be the first PSA network element in the fourth aspect or any possible design of the fourth aspect, or a chip that implements the function of the first PSA network element.
  • an embodiment of the present application provides an apparatus for sending a domain name system request, including: a processor and a memory; the memory is used to store a computer instruction, and when the processor executes the instruction, the domain name system request
  • the sending apparatus performs the method described in any one of the above aspects.
  • the device for sending the domain name system request may be the first PSA network element in the fourth aspect or any possible design of the fourth aspect, or a chip that implements the function of the first PSA network element.
  • an embodiment of the present application provides an apparatus for sending a domain name system request, including: a processor; the processor is configured to be coupled to a memory, and after reading an instruction in the memory, execute the above-mentioned method according to the instruction The method of any aspect.
  • the device for sending the domain name system request may be the first PSA network element in the fourth aspect or any possible design of the fourth aspect, or a chip that implements the function of the first PSA network element.
  • an embodiment of the present application provides a computer-readable storage medium, where instructions are stored in the computer-readable storage medium, and when the computer-readable storage medium runs on a computer, the computer can execute any one of the preceding aspects.
  • an embodiment of the present application provides a computer program product including instructions, which, when run on a computer, enables the computer to execute the method for sending a domain name system request in any one of the above aspects.
  • an embodiment of the present application provides a circuit system, where the circuit system includes a processing circuit, and the processing circuit is configured to execute the method for sending a domain name system request according to any one of the foregoing aspects.
  • an embodiment of the present application provides a chip, where the chip includes a processor, the processor is coupled with a memory, the memory stores program instructions, and when the program instructions stored in the memory are executed by the processor, any one of the above aspects is implemented The sending method of the DNS request.
  • an embodiment of the present application provides a system for sending a domain name system request, where the system for sending a domain name system request includes the terminal device in any one of the above-mentioned first aspect, or includes any one of the second aspect
  • FIG. 1 is a schematic diagram of a network architecture provided by an embodiment of the present application.
  • FIG. 2 is a schematic diagram of still another network architecture provided by an embodiment of the present application.
  • FIG. 3 is a schematic flowchart of a method for sending a domain name system request according to an embodiment of the present application
  • FIG. 4 is a schematic flowchart of still another method for sending a domain name system request according to an embodiment of the present application
  • FIG. 5 is a schematic flowchart of another method for sending a domain name system request according to an embodiment of the present application
  • FIG. 6 is a schematic flowchart of another method for sending a domain name system request provided by an embodiment of the present application.
  • FIG. 7 is a schematic flowchart of another method for sending a domain name system request provided by an embodiment of the present application.
  • FIG. 8 is a schematic flowchart of another method for sending a domain name system request according to an embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of an apparatus for sending a domain name system request according to an embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of still another apparatus for sending a domain name system request according to an embodiment of the present application.
  • references to the terms “comprising” and “having” in the description of this application, and any variations thereof, are intended to cover non-exclusive inclusion.
  • a process, method, system, product or device comprising a series of steps or units is not limited to the listed steps or units, but optionally also includes other unlisted steps or units, or optionally also Include other steps or units inherent to these processes, methods, products or devices.
  • "a plurality of" includes two or more.
  • words such as “exemplary” or “for example” are used to represent examples, illustrations or illustrations. Any embodiments or designs described in the embodiments of the present application as “exemplary” or “such as” should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of words such as “exemplary” or “such as” is intended to present the related concepts in a specific manner.
  • DNS is a distributed database on the Internet that maps domain names and Internet protocol (IP) addresses to each other, and can map domain names to IP addresses of application servers.
  • IP Internet protocol
  • domain name resolution the process of mapping the domain name to the IP address of the application server.
  • a domain name also known as a domain
  • a domain is the name of a computer or computer group on the Internet consisting of a string of names separated by dots, which is used to identify the electronic location or geographic location of the computer during data transmission.
  • the domain name can be www.123456.com.cn.
  • the domain name resolution device in the DNS is the DNS server.
  • the DNS server can analyze the domain name requested by the terminal device through the domain name resolution mechanism, and obtain the IP address of the application server corresponding to the domain name.
  • the number of DNS servers may be multiple and distributed in a hierarchical structure.
  • the DNS sequentially resolves the domain name through the DNS servers in the lower to higher layers until the IP address of the application server corresponding to the above-mentioned domain name is obtained.
  • the domain name resolution mechanism is not described in detail in this embodiment of the present application.
  • the process for the terminal device to access the target domain name is as follows: after acquiring the target domain name, the terminal device sends DNS request information carrying the target domain name to the DNS server.
  • the DNS server receives the DNS request information from the terminal device.
  • the DNS server parses out the IP address of the target application server corresponding to the target domain name, and carries the IP address of the target application server in the response information and sends it to the terminal device.
  • the terminal device receives the response information from the DNS server, so that the terminal device obtains the IP address of the target application server, and implements data transmission with the target application server according to the IP address.
  • DNS request information may also be described as "request message", or "domain name resolution request message”.
  • the "response message” may also be described as a "response message”, or a “DNS response (response)", or a "domain name resolution response message", corresponding to the DNS request information.
  • a PDU session is a connection between an end device and a data network, and is used to transmit data between the end device and the data network.
  • End devices can be connected to the same data network or to different data networks through multiple PDU sessions.
  • End devices may connect to the same data network through one or more PDU sessions served by different PSA network elements.
  • the PSA network element may be a user plane function (UPF) network element connected to the data network.
  • PSA can also be noted as PDU Session Anchor UPF.
  • UPF user plane function
  • a PDU session is connected to the data network through multiple PSA network elements.
  • the user plane paths leading to different PSA network elements are branched on the BP device.
  • the BP device may also be a UPF network element.
  • a terminal device includes a plurality of addresses and corresponds to a plurality of PSA network elements.
  • One address of the terminal device corresponds to one PSA network element, and different addresses of the terminal device correspond to different PSA network elements.
  • the terminal device sends DNS request information to the BP device.
  • the BP device receives the DNS request information from the terminal device.
  • the DNS request information includes, in addition to the target domain name, a source address and a destination address.
  • the source address in the DNS request information is an address of the terminal device and corresponds to a PSA network element.
  • the destination address in the DNS request information is the address of a DNS server. If there is no correspondence between the PSA network element corresponding to the source address in a DNS request message and the DNS server corresponding to the destination address, that is, the PSA network element corresponding to the source address and the DNS server corresponding to the destination address cannot communicate, the error occurs.
  • the phenomenon of "DNS resolution failure" results in low DNS resolution efficiency.
  • an embodiment of the present application provides a method for sending a domain name system request.
  • the system may support fifth-generation (fifth-generation, 5G) mobile communication technology communication system, such as NR access technology; or, the system may also be a communication system supporting multiple wireless technologies, such as a communication system supporting LTE technology and new radio (new radio, NR) access technology .
  • 5G fifth-generation
  • NR new radio
  • the system can also be adapted to future-oriented communication technologies.
  • FIG. 1 taking a communication system supporting 5G mobile communication technology as an example, the network architecture of the system is introduced.
  • the network elements in the 5G network architecture include terminal devices, access network (AN) equipment, access and mobility management function (AMF) network elements, session management function (session management function, SMF) network elements element, PSA network element, BP equipment, and data network (DN), etc. Only two PSA network elements are shown in Figure 1 .
  • FIG. 1 is only a schematic diagram, and does not constitute a limitation on the applicable scenarios of the method for sending a domain name system request according to the embodiment of the present application.
  • the terminal device also known as user equipment (UE), terminal equipment, mobile station (MS), mobile terminal (MT), etc., is a device that provides voice/data connectivity to users.
  • devices such as handheld or in-vehicle devices with wireless connectivity.
  • the terminal device may specifically be: a mobile phone (mobile phone), a tablet computer, a notebook computer, a palmtop computer, a mobile internet device (MID), a wearable device, a virtual reality (virtual reality, VR) device, an augmented reality (augmented reality) device reality, AR) equipment, wireless terminals in industrial control, wireless terminals in self driving, wireless terminals in remote medical surgery, wireless terminals in smart grid (smart grid) Terminal, wireless terminal in transportation safety, wireless terminal in smart city, or wireless terminal in smart home, terminal device in future 5G communication network or communication network after 5G etc., which are not limited in the embodiments of the present application.
  • the access network device may also be a radio access network (radio access network, RAN) device, which is a device deployed in a radio access network to provide a wireless communication function.
  • RAN radio access network
  • the RAN devices involved in the embodiments of the present application include, for example, but not limited to, the following various forms of macro base stations, micro base stations (also referred to as small stations), relay stations, transmission reception points (transmission reception points, TRP), and the following: Generation of network nodes (g Node B, gNB), evolved Node B (ng evolved Node B, ng-eNB) connected to the next-generation core network, etc., can also include wireless local area network (wireless local area network, WLAN) access equipment, etc. RAN equipment for non-3rd generation partnership project (3GPP) systems.
  • 3GPP non-3rd generation partnership project
  • the AMF network element has the functions of terminal device mobility management, registration management, connection management, legal interception, support for the transmission of session management (session management, SM) information between the terminal device and the SMF, access authentication and access authorization.
  • session management session management
  • the SMF network element has functions such as session management and roaming.
  • session management functions such as session establishment, modification and release.
  • Roaming functions may include charging data collection, signaling to support authentication/authorization with external data networks.
  • the PSA network element is a functional network element on the user plane. It is mainly responsible for connecting to external networks and processing user packets, such as forwarding, charging, and lawful interception. Optionally, the PSA network element may also receive data. Only two PSA network elements are shown in FIG. 1 , which are denoted as PSA network element 1 and PSA network element 2 respectively.
  • the BP equipment can receive the upstream data packets from the terminal device, and distribute the upstream data packets to the PSA network elements corresponding to the source addresses according to the source addresses of the upstream data packets.
  • the BP equipment can also receive downlink data packets from the PSA network element, aggregate the downlink data packets received from the PSA network element, and send them to the terminal device.
  • the BP device may also be implemented as a UPF network element.
  • a data network is a network that provides services for terminal devices. For example, some data networks provide terminal devices with Internet access functions, and other data networks provide terminal devices with short message functions.
  • the terminal device communicates with the AMF network element through the N1 interface
  • the AN device communicates with the AMF network element through the N2 interface
  • the AN device communicates with the BP device through the N3 interface
  • the BP device communicates with the SMF network element through the N4 interface
  • the BP device communicates with the SMF network element through the N9 interface.
  • Communicate with the UPF network element the UPF network element communicates with the SMF network element through the N4 interface
  • the UPF network element accesses the data network through the N6 interface
  • the AMF network element communicates with the SMF network element through the N11 interface.
  • the dashed line shows a path that enables control plane signaling interaction
  • the solid line shows a path that enables user plane data interaction.
  • the data networks connected to different PSA network elements are located in different data centers (data centers, DCs). Still taking the scenario shown in FIG. 1 as an example, the distribution status of the data network will be described.
  • the data network connected to the PSA network element 1 may be a central data network or a central data center.
  • PSA network element 1 can be recorded as central PSA, or C-PSA for short.
  • the data network connected to the PSA network element 1 may also be a remote data network (remote data network) or a remote data center (remote data center). In this case, PSA network element 1 can be recorded as remote PSA, or R-PSA for short.
  • the PSA network element 1 is also able to communicate with the DNS server in the above-mentioned data network.
  • the data network connected to the PSA network element 2 is located in a local DC or an edge data network (EDN).
  • the PSA network element 2 can be recorded as Local PSA, abbreviated as L-PSA.
  • L-PSA Different L-PSA network elements can identify different digital suffixes.
  • the first L-PSA network element may be denoted as L-PSA_1, and the second L-PSA network element may be denoted as L-PSA_2.
  • the PSA network element 2 is also able to communicate with the DNS server in the local DC. There may be no IP connectivity between the PSA NEs in different DCs and the DNS server, so they cannot communicate.
  • PSA network element 1 cannot communicate with the DNS server in the local DC.
  • PSA network element 2 cannot communicate with the DNS server in the central DC.
  • the SMF network element inserts the PSA network element 2 as a local PSA into the session path, so that the terminal device can access nearby Applications in the local DN.
  • BP equipment and L-PSA network elements can be deployed separately or in one. In the scenario shown in FIG. 2 , the function of the BP device and the function of the PSA network element 2 are implemented by the same network element, which may be the PSA network element 2 .
  • the local DC or edge data network can be implemented as a mobile/multi-access edge computing (MEC) node.
  • MEC node includes an MEC platform and data plane functional network elements.
  • various application servers, DNS servers, etc. may be deployed on the MEC platform, which is not specifically limited in this embodiment of the present application.
  • the MEC platform in the embodiment of the present application may also be called an MEC system or others, which is not specifically limited in the embodiment of the present application.
  • the data plane functional network element can be implemented by the PSA network element.
  • An application server is a carrier that can provide corresponding services.
  • the WeChat application server may be a carrier capable of providing WeChat services.
  • the carrier may be a virtual device, such as a virtual machine or a container, or a physical device, which is not specifically limited in this embodiment of the present application.
  • the embodiment of the present application provides a first method for sending a domain name system request, and the method for sending a domain name system request is applied in a domain name resolution process.
  • the method for sending a domain name system request according to the embodiment of the present application includes the following steps:
  • the terminal device creates a PDU session.
  • the terminal device initiates a session creation request message to create a PDU session.
  • the PDU session creation process is completed by the network equipment (such as the SMF network element and the UPF network element) and the terminal device.
  • the network equipment such as the SMF network element and the UPF network element
  • the terminal device For the detailed implementation process of the session creation process, reference may be made to the prior art, which will not be repeated here.
  • the user plane path of the PDU session includes: the path from the RAN device to the BP device, and the path from the BP device to the PSA network element.
  • the number of PSA network elements is two or more.
  • the PSA network element may be the PSA network element in the local DC or the PSA network element in the central DC.
  • the terminal devices are assigned a plurality of addresses.
  • the address assigned to the terminal device may be a specific address, such as the address of the Internet Protocol Version 4 (IPv4), or it may be an address prefix (prefix), such as the Internet Protocol Version 4 (IPv4) address.
  • IPv6 Internet Protocol Version 6
  • One address of the terminal device corresponds to one PSA network element, and different addresses of the terminal device correspond to different PSA network elements.
  • the multiple addresses of the terminal device can be allocated by the SMF network element or by the PSA network element.
  • a PSA network element assigns an address to a terminal device
  • one PSA network element assigns one address to the terminal device
  • different PSA network elements assign different addresses to the terminal device. Exemplarily, see Table 1, which shows the correspondence between the addresses of the terminal devices and the PSA network elements.
  • the address of the terminal device PSA network element The address of the terminal device@0 C-PSA The address of the terminal device@1 L-PSA_1 ... The address of the terminal device@n L-PSA_n
  • Table 1 shows (n+1) addresses of the terminal device, which are respectively denoted as: address@0 of the terminal device, address@1 of the terminal device, . . . , address@n of the terminal device.
  • the number of PSA network elements is (n+1), which are respectively denoted as: C-PSA, L-PSA_1, ..., L-PSA_n.
  • C-PSA C-PSA
  • L-PSA_1 a number of PSA network elements
  • PSA network elements can serve or access specific data networks/data centers.
  • DNS servers can be deployed in these "data networks/data centers" to perform DNS resolution through the DNS servers.
  • the DNS server can also be deployed on the PSA network element, and the DNS server can also be deployed on the path between the PSA network element and the "data network/data center”.
  • This embodiment of the present application does not limit the deployment location of the DNS server, which ensures that the PSA network element can send the DNS request information to the corresponding DNS server after receiving the DNS request information. In this way, there is a corresponding relationship between the DNS server and "data network/data center", and there is also a corresponding relationship between PSA and "data network/data center”.
  • Table 2 shows the correspondence between the PSA network element and the DNS server by taking "address of the DNS server" as an example.
  • the address of the DNS server may be identified by an IP address or a domain name or the like.
  • the addresses of at least two DNS servers are different. That is, the addresses of the DNS servers are not exactly the same.
  • the addresses of different DNS servers can be the same or different.
  • Table 2 shows the addresses of (n+1) DNS servers, which are respectively denoted as: IP@0, IP@1, . . . , IP@n.
  • IP@0, IP@1, ..., IP@n may have the same address.
  • the number of PSA network elements is (n+1), which are respectively denoted as: C-PSA, L-PSA_1, ..., L-PSA_n.
  • C-PSA C-PSA
  • L-PSA_1 corresponds to the "C-PSA” network element.
  • L-PSA_1 corresponds to, ..., "IP@n” corresponds to "L-PSA_n” NE.
  • Table 1 only shows the “correspondence between the address of the terminal device and the PSA network element” in the form of a “table”.
  • Table 2 only shows the “correspondence between the PSA network element and the DNS server” in the form of a “table”. Table 1 and Table 2 may be combined in the same table to present "the correspondence between the address of the terminal device and the PSA network element” and the “correspondence between the PSA network element and the DNS server", to which the embodiments of the present application Not limited.
  • the terminal device determines the address of the first DNS server corresponding to the first application.
  • the first application may refer to a software product installed on the terminal device and used to access the service provided by the application server.
  • These software products may also be referred to as application clients.
  • the "first DNS server corresponding to the first application” refers to that an application server corresponding to the first application is deployed on the data network corresponding to the first DNS server.
  • the address of the first DNS server may be identified by an IP address or a domain name or the like.
  • the first application may be a WeChat client on the terminal device.
  • the application server is a WeChat application server, which provides services for the WeChat client on the terminal device.
  • the first DNS server is a DNS server capable of resolving DNS request information including the WeChat application. Taking the scenario shown in Figure 2 as an example, if the application server in the central DC has the application "WeChat" deployed, but the application server in the local DC is not deployed with the application "WeChat", the first DNS server can It is the DNS server in the central DC, which can be recorded as the "C-DNS" server.
  • the first DNS server is the DNS server in the central DC, which can be Note as "L-DNS” server.
  • Table 3-1 shows "correspondence between different applications and different DNS servers" by taking "application identifier” and "address of DNS server” as examples.
  • the identity of the application can be a fully qualified domain name (FQDN).
  • FQDN fully qualified domain name
  • App ID The address of the DNS server FQDN_1 IP@1 FQDN_1 IP@2 FQDN_2 IP@1 FQDN_3 IP@3 ... ... FQDN_n IP@2
  • Table 3-1 shows the identifiers of n applications, which are respectively denoted as: FQDN_1, FQDN_2, ..., FQDN_n.
  • the number of DNS servers is at least two.
  • Table 3-1 shows the addresses of the three DNS servers, which are respectively recorded as IP@1, IP@2, and IP@3. In Table 3-1, there is a correspondence between applications and DNS servers in the same row.
  • the terminal device may pre-configure the information "correspondence between applications and DNS servers", or the SMF network element, PCF network element or other network elements may send the information "correspondence between applications and DNS servers” information to the terminal device.
  • the SMF network element or the PCF network element sends the user routing selection policy (URSP) to the terminal device with the above-mentioned "application and DNS server.” Correspondence between” information.
  • URSP user routing selection policy
  • the terminal device determines the address of the first DNS server corresponding to the first application, such as but not limited to the processing process shown in FIG. 4 :
  • the SMF network element sends the identifier of the first application and the address of the DNS server corresponding to the identifier of the first application to the terminal device.
  • the terminal device receives the identifier of the first application from the SMF network element and the address of the DNS server corresponding to the identifier of the first application.
  • the identifier of the first application and the address of the DNS server corresponding to the identifier of the first application may be presented in the form of a table, or may be presented in other forms, which are not limited in this embodiment of the present application.
  • the first application may be one application among the n applications in Table 3-1.
  • the terminal device determines the address of the first DNS server according to the identifier of the first application and the address of the DNS server corresponding to the identifier of the first application.
  • the address of the DNS server is the address of the first DNS server.
  • the identifier of the first application is "FQDN_3".
  • the application identified by "FQDN_3” only has a corresponding relationship with the DNS server with the address "IP@3", that is, only the DNS server with the address "IP@3” can be deployed with the There is communication with the application server of the "first application”. In this way, the address of the first DNS server is "IP@3".
  • the terminal device determines one DNS server from the plurality of DNS servers based on a certain preset policy as the first DNS server.
  • the terminal device determines from a plurality of DNS servers a first DNS server that satisfies a preset policy.
  • the preset strategy includes at least one of the following:
  • the first item the priority of the first DNS server satisfies the priority condition among the priorities of the plurality of DNS servers.
  • the priority of the first DNS server is the highest among the priorities of the plurality of DNS servers.
  • the second item the distance between the first DNS server and the terminal device satisfies the separation distance condition.
  • the distance between the first DNS server and the terminal device is less than or equal to the distance threshold, or, among the distances between the plurality of DNS servers and the terminal device, the distance between the first DNS server and the terminal device is the smallest.
  • the identifier of the first application is "FQDN_1".
  • Table 3-1 there is a corresponding relationship between the application identified by "FQDN_1” and the DNS server with the address "IP@1" and the DNS server with the address "IP@2", that is, the application with the address "IP@2" has a corresponding relationship.
  • the DNS server of 1" and the DNS server with the address of "IP@2" can resolve the DNS request information corresponding to the "first application".
  • the address of the first DNS server is "IP@1" . If the distance between the DNS server whose address is "IP@2" and the terminal device satisfies the separation distance condition, the address of the first DNS server is "IP@2".
  • Table 3-2 in addition to showing "correspondence between different applications and different DNS servers", “priorities of different DNS servers” are also shown.
  • App ID The address of the DNS server priority FQDN_1 IP@1 3 FQDN_1 IP@2 2 FQDN_2 IP@1 3 FQDN_3 IP@3 4 ... ... ... FQDN_n IP@2 2
  • the identifier of the first application is "FQDN_1".
  • Table 3-2 there is a corresponding relationship between the application identified by "FQDN_1” and the DNS server with the address "IP@1" and the DNS server with "IP@2".
  • the preset policy is implemented as the first item, if the priority of the DNS server whose address is "IP@1" is higher than that of the DNS server whose address is "IP@2", the address of the first DNS server is " IP@1".
  • the terminal device can determine the correspondence of the first application according to the information provided by the SMF network element.
  • the address of the first DNS server is the address of the first DNS server.
  • the terminal device determines the first address of the terminal device according to the address of the first DNS server and the address of the terminal device corresponding to the address of the first DNS server.
  • the description about the "address of the terminal device” is as follows: There may be one or more addresses of the terminal device.
  • the address of the terminal device can be assigned by the SMF network element or by the UPF (PSA) network element.
  • One address of the terminal device corresponds to one PSA network element, and different addresses of the terminal device correspond to different PSA network elements.
  • the PSA network element corresponding to the first address of the terminal device is denoted as the first PSA network element.
  • the description about "the address of the terminal device corresponding to the address of the first DNS server” is as follows: Since there is a correspondence between the PSA network element and the DNS server, please refer to the relevant description in Table 2 for details. In addition, there is also a corresponding relationship between the PSA network element and the address of the terminal device. For details, please refer to the relevant description in Table 1. For the address of the terminal device and the DNS server that have a corresponding relationship with the same "PSA network element”, there is also a corresponding relationship between the two. Exemplarily, see Table 4. Table 4 takes “address of DNS server” as an example, and shows “correspondence between DNS server and address of terminal device”.
  • the address of the terminal device The address of the DNS server The address of the terminal device@0 IP@0 The address of the terminal device@1 IP@1 Address of end device@2 IP@2 ... ... The address of the terminal device@n IP@n
  • Table 4 shows (n+1) addresses of the terminal device, which are respectively denoted as: the address of the terminal device @0, the address of the terminal device @1, . . . , and the address of the terminal device @n.
  • the number of DNS servers is (n+1), and the addresses of the (n+1) DNS servers are respectively recorded as: IP@0, IP@1, IP@2, ..., IP@n.
  • IP@0, IP@1, IP@2, ..., IP@n there is a correspondence between the addresses of the terminal apparatuses and the DNS servers in the same row.
  • the information of "the address of the first DNS server and the address of the terminal device corresponding to the address of the first DNS server" may be information preconfigured by the terminal device, or may be generated by the SMF network element, the PCF network element or other network elements.
  • the element is the information sent by the terminal device, for example:
  • the SMF network element sends the address of the first DNS server and the address of the terminal device corresponding to the address of the first DNS server to the terminal device.
  • the terminal device receives the address of the first DNS server from the SMF network element and the address of the terminal device corresponding to the address of the first DNS server.
  • the SMF network element when the SMF network element inserts the BP device in the user plane path of the PDU session, the SMF network element sends the address of the first DNS server and the address of the terminal device corresponding to the address of the first DNS server to the terminal device.
  • the above information is carried in a routing rule (routing rule) issued to the terminal device.
  • the terminal device sends DNS request information to the BP device.
  • the BP device receives the DNS request information from the terminal device.
  • the DNS request information includes the identifier of the first application, the address of the first DNS server, and the first address of the terminal device.
  • the source address of the DNS request information is the first address of the terminal device
  • the destination address of the DNS request information is the address of the first DNS server.
  • the identifier of the first application is "FQDN_1"
  • the address of the first DNS server is "IP@1”
  • the address of the terminal device is "address of the terminal device@1”.
  • the identifier of the application in the DNS request information is "FQDN_1”
  • the source address of the DNS request information is "terminal device address@1”
  • the destination address of the DNS request information is "IP@1”.
  • the terminal device sends DNS request information to the BP device.
  • the BP device receives the DNS request information from the terminal device.
  • the BP device determines the PSA network element corresponding to the source address according to the source address of the DNS request information, and then sends the DNS request information to the PSA network element corresponding to the source address.
  • the PSA network element corresponding to the source address receives the DNS request information from the BP device.
  • the PSA network element corresponding to the source address is the "C-PSA" network element
  • the BP device sends DNS request information to the C-PSA network element.
  • the C-PSA network element receives the DNS request information from the BP device. After that, the C-PSA network element sends the DNS request information to the C-DNS server according to the destination address in the DNS request information.
  • the C-DNS server receives the DNS request information from the C-PSA network element, parses the DNS request information, and obtains response information for the DNS request information.
  • the response information includes the IP address of the application server.
  • the response information is then transmitted to the terminal device by the C-DNS server, the C-PSA network element and the BP device to provide the terminal device with the IP address of the application server, thereby enabling data transmission between the terminal device and the application server.
  • the BP device sends DNS request information to the L-PSA network element.
  • the L-PSA network element receives the DNS request information from the BP device.
  • the L-PSA network element sends the DNS request information to the L-DNS server according to the destination address in the DNS request information.
  • the L-DNS server receives the DNS request information from the L-PSA network element, parses the DNS request information, and obtains response information of the DNS request information.
  • the response information is then transmitted from the L-DNS server, the L-PSA network element and the BP device to the terminal device to provide the terminal device with the IP address of the application server.
  • the network device (such as SMF network element or PCF network element, etc.) provides the terminal device with “correspondence between different applications and different DNS servers” and “DNS server”. Correspondence with the address of the terminal device".
  • the terminal device can also use the address of the first DNS server and the address of the terminal device corresponding to the address of the first DNS server according to the address of the first DNS server. , to determine the first address of the terminal device. Since there is a correspondence between the address of the first DNS server and the first address of the terminal device, and the first address of the terminal device corresponds to a PSA network element, that is, the first DNS server corresponds to the first address of the terminal device.
  • the PSA network elements can communicate with each other.
  • the DNS request information sent by the terminal device includes the address of the first DNS server and the first address of the terminal device, the DNS request information can be transmitted to the first DNS server through the PSA network element corresponding to the terminal device, thereby improving the DNS performance.
  • the success rate of resolution reduces the phenomenon of "DNS resolution failure" caused by "inability to communicate between the DNS server and the PSA network element" in the prior art.
  • the embodiment of the present application provides a second method for sending a domain name system request, and the method for sending a domain name system request is applied in a domain name resolution process.
  • the method for sending a domain name system request according to the embodiment of the present application includes the following steps:
  • the terminal device creates a PDU session.
  • S601 may refer to the relevant description of S301, which will not be repeated here.
  • the terminal device sends DNS request information to the BP device.
  • the BP device receives the DNS request information from the terminal device.
  • the DNS request information includes the identifier, source address and destination address of the first application.
  • the source address and the destination address selected by the terminal device are not limited, and the specific implementation process may refer to the prior art, which will not be repeated here.
  • the BP device updates at least one of the source address and the destination address in the DNS request information, and obtains the updated DNS request information.
  • the source address in the updated DNS request information is the first address of the terminal device, and the destination address in the updated DNS request information is the address of the first DNS server.
  • the updated DNS request information there is a correspondence between the PSA network element corresponding to the source address and the first DNS server, and they can communicate with each other. Please refer to the relevant description of S303, which will not be repeated here to avoid the PSA network element The phenomenon of "DNS resolution failure" caused by the inability to communicate with the DNS server.
  • BP device to update at least one of the source address and destination address in the DNS request information, and obtain the updated DNS request information.
  • three examples are used to illustrate:
  • Example 1 The BP device updates at least one of the source address and the destination address in the DNS request information according to the identifier of the first application in the DNS request information, and obtains the updated DNS request information.
  • the source address and destination address in the update DNS request information are determined according to the identifier of the first application, and the application server corresponding to the first application is deployed in the data network corresponding to the first DNS server, so the first DNS server can Parse the DNS request information.
  • the PSA network element corresponding to the first DNS server can be determined, and then the first address of the terminal device is determined, and the PSA network element corresponding to the first address of the terminal device can communicate with the first DNS server, In order to improve the efficiency of DNS request information parsing.
  • the BP device performs the following steps:
  • the BP device determines the address of the first DNS server corresponding to the identifier of the first application.
  • the BP device may determine the address of the first DNS server corresponding to the first application according to "correspondence between different applications and different DNS servers".
  • S6031 can be specifically implemented as the following steps 1 and 2:
  • Step 1 The SMF network element sends the identifier of the first application and the address of the DNS server corresponding to the identifier of the first application to the BP device.
  • the BP device receives the identifier of the first application from the SMF network element and the address of the DNS server corresponding to the identifier of the first application.
  • the identifier of the first application and the address of the DNS server corresponding to the identifier of the first application may be presented in the form of a table, or may be presented in other forms, which are not limited in this embodiment of the present application.
  • the first application may be one application among the n applications in Table 3-1.
  • step 1 may also be implemented as: the SMF network element sends the identifier of the application deployed in the data network to the BP device.
  • the BP device receives the identifier of the application deployed in the data network from the SMF network element.
  • step 1 may also be implemented as: the SMF network element sends the identifier of the application server deployed in the data network to the BP device.
  • the BP device receives the identifier of the application server deployed in the data network from the SMF network element.
  • the BP device can determine the identifier of the first application and the address of the DNS server corresponding to the identifier of the first application according to the information received from the SMF network element.
  • Step 2 The BP device determines the address of the first DNS server according to the identifier of the first application and the address of the DNS server corresponding to the identifier of the first application.
  • step 2 please refer to the relevant description of S3022. That is to say, the terminal device in S3022 is replaced by the BP device, and the specific method and process are the same, which will not be repeated here.
  • the BP device determines the address of the first DNS server, if the destination address in the DNS request information is consistent with the address of the first DNS server, the BP device does not need to perform S6032. If the destination address in the DNS request information is inconsistent with the address of the first DNS server, the BP device executes S6032:
  • the BP device updates the destination address in the DNS request information to the address of the first DNS server.
  • the BP device replaces the destination address in the DNS request information with "IP@2" .
  • the BP device determines the first address of the terminal device according to the address of the first DNS server and the address of the terminal device corresponding to the address of the first DNS server.
  • S6033 please refer to the relevant description of S303. That is to say, the terminal device in S303 is replaced by the BP equipment, and the specific method flow is the same, which will not be repeated here.
  • the BP device determines the first address of the terminal device, if the source address in the DNS request information is consistent with the first address of the terminal device, the BP device does not need to perform S6034. If the source address in the DNS request information is inconsistent with the first address of the terminal device, the BP device executes S6034:
  • the BP device sets the source address in the DNS request information as the first address of the terminal device.
  • the BP device replaces the source address in the DNS request information with It is "Address of terminal device@2".
  • the BP device updates the source address and the destination address in the DNS request information based on the application identifier in the DNS request information, so as to obtain the updated DNS request information.
  • Example 2 The BP device updates the destination address in the DNS request information according to the source address in the DNS request information.
  • the source address in the DNS request information is “address of the terminal device@1”, and the DNS request If the destination address in the information is not "IP@1", the BP device updates the destination address in the DNS request information to "IP@1". In the case where the source address in the DNS request message is "address of the terminal device@2" and the destination address in the DNS request message is not "IP@2", the BP device updates the destination address in the DNS request message to "IP@2" @2".
  • the BP device updates the destination address in the DNS request information based on the source address in the DNS request information, so as to obtain the updated DNS request information.
  • Example 2 as a possible implementation manner, the BP device performs the following steps 3 and 4:
  • Step 3 if the source address in the DNS request information is the first address of the terminal device, then the BP device determines the address of the first DNS server according to the first address of the terminal device and the address of the DNS server corresponding to the first address of the terminal device. address.
  • the BP device determines that the address of the first DNS server is "IP@1”. In the case where the source address in the DNS request information is “address of the terminal device@2”, the BP device determines that the address of the first DNS server is "IP@2".
  • the information "the first address of the terminal device and the address of the DNS server corresponding to the first address of the terminal device” may be information preconfigured by the BP device, or information issued by the SMF network element for the BP device, That is, the SMF network element sends the first address of the terminal device and the address of the DNS server corresponding to the first address of the terminal device to the BP device.
  • the BP device receives the first address of the terminal device from the SMF network element and the address of the DNS server corresponding to the first address of the terminal device.
  • Step 4 The BP device updates the destination address in the DNS request information to the address of the first DNS server.
  • the BP device sends the destination address in the DNS request information Update to "IP@1".
  • the BP device updates the destination address in the DNS request information to "IP@2" @2".
  • the BP device when determining that the source address in the DNS request information is the first address of the terminal device, the BP device updates the destination address in the DNS request information with the source address in the DNS request information as the criterion to obtain the updated DNS request information.
  • Example 3 The BP device updates the source address in the DNS request information according to the destination address in the DNS request information.
  • the destination address in the DNS request information is "IP@1", and the address in the DNS request information is "IP@1".
  • the BP device updates the source address in the DNS request information to "address of the terminal device@1".
  • the BP device updates the source address in the DNS request information to "terminal device address@2" The address of the device@2".
  • the BP device updates the source address in the DNS request information based on the destination address in the DNS request information, so as to obtain the updated DNS request information.
  • Example 3 as a possible implementation manner, the BP device performs the following steps 5 and 6:
  • Step 5 If the destination address in the DNS request information is the address of the first DNS server, then the BP device determines the first address of the terminal device according to the address of the first DNS server and the address of the terminal device corresponding to the address of the first DNS server. address.
  • the BP device determines that the first address of the terminal device is "address of the terminal device@1".
  • the BP device determines that the first address of the terminal device is "address of the terminal device@2".
  • the information of "the address of the first DNS server and the address of the terminal device corresponding to the address of the first DNS server” may be information preconfigured by the BP device, or information issued by the SMF network element for the BP device, That is, the SMF network element sends the address of the first DNS server and the address of the terminal device corresponding to the address of the first DNS server to the BP device.
  • the BP device receives the address of the first DNS server of the terminal device from the SMF network element and the address of the terminal device corresponding to the address of the first DNS server.
  • Step 6 The BP device updates the source address in the DNS request information to the first address of the terminal device.
  • the BP device converts the source address in the DNS request information Update to "Address of terminal device@1".
  • the BP device updates the source address in the DNS request information to "terminal device address@2" The address of the device@2".
  • the BP device when determining that the destination address in the DNS request information is the address of the first DNS server, the BP device takes the destination address in the DNS request information as the criterion to update the source address in the DNS request information to obtain the updated DNS request information.
  • the update rule of the BP device is "update at least one of the source address and the destination address in the DNS request information based on the identifier of the first application in the DNS request information" .
  • the update rule of the BP device is "update the destination address in the DNS request information based on the source address in the DNS request information”.
  • the update rule of the BP device is "update the source address in the DNS request information based on the destination address in the DNS request information”.
  • the update rule in any of the above three examples may be pre-configured on the BP device, or may be configured by the SMF network element for the BP device.
  • the update rules of any one of the above three examples may be configured with the terminal device as the granularity, that is, the update rules for different DNS request information sent by the same terminal device are the same, and the update rules for the DNS request information of different terminal devices may be the same. , can also be different. In this case, if N terminal devices are all served by the BP device, the BP device needs to configure the update rule N times.
  • the update rule of any of the above three examples can also be configured by "BP device" for granularity, that is, for a BP device, the BP device adopts the same update rule to update the source address and/or destination in the DNS request information. address. In this case, if all N terminal devices are served by the BP device, the BP device needs to configure an update rule once.
  • the BP device sends the updated DNS request information to the first PSA network element according to the source address in the updated DNS request information.
  • the first PSA network element receives the updated DNS request information from the BP device.
  • the first PSA network element is the PSA network element corresponding to the first address of the terminal device.
  • the BP device determines the first PSA network element according to the source address in the updated DNS request information, and then the BP device sends the updated DNS request information to the first PSA network element.
  • the BP device determines the first PSA network element according to the source address in the updated DNS request information, and then the BP device sends the updated DNS request information to the first PSA network element.
  • the first PSA network element sends the updated DNS request information to the first DNS server according to the destination address in the updated DNS request information.
  • the first DNS server receives the updated DNS request information from the first PSA network element.
  • the first DNS server has a corresponding relationship with the first PSA network element.
  • the first DNS server parses the updated DNS request information to obtain response information.
  • the DNS request information includes the identifier of the first application.
  • the response information includes the IP address of the application server corresponding to the first application.
  • the source address of the response information is the destination address of the updated DNS request information, and the destination address of the response information is the source address of the updated DNS request information.
  • the first DNS server sends response information to the first PSA network element.
  • the first PSA network element receives the response information from the first DNS server.
  • the destination address of the response information is the source address of the updated DNS request information, that is, the first address of the terminal device.
  • the first DNS server sends the response information to the first PSA network element according to the destination address of the response information.
  • the first PSA network element sends response information to the BP device.
  • the BP device receives the response information from the first PSA network element.
  • the source address of the response information is the destination address of the updated DNS request information
  • the destination address of the response information is the source address of the updated DNS request information
  • the BP device updates at least one of the source address and the destination address in the response information, and obtains the updated response information.
  • the source address in the updated response information is the destination address of the pre-update DNS request information
  • the destination address in the updated response information is the source address of the pre-update DNS request information
  • the BP device replaces the source address in the DNS request information with “address of the terminal device@3” with “address of the terminal device@2”, then in S609, the BP device will The destination address is replaced by "Address of End Device@2" with "Address of End Device@3". If in S603, the BP device replaces the destination address in the DNS request message with "IP@1" with "IP@2”, then in S609, the BP device replaces the source address in the response message with "IP@2" is "IP@1".
  • the BP device sends the updated response information to the terminal device.
  • the terminal device receives the updated response information from the BP device.
  • the updated response information includes the IP address of the application server corresponding to the first application, the destination address of the DNS request information before the update, and the source address of the DNS request information before the update.
  • the terminal device After the terminal device performs S602 to send the DNS request information, it monitors the response message carrying the source address and destination address of the DNS request information before the update.
  • the BP device can replace at least one of the source address and the destination address in the response information, so as to ensure that the terminal device can monitor the response message carrying the source address and destination address of the DNS request information before updating.
  • the BP device can update at least one of the source address and the destination address in the DNS request information, obtain the updated DNS request information, and then Send the updated DNS request information. Since the source address in the updated DNS request information is the first address of the terminal device, the destination address in the updated DNS request information is the address of the first DNS server.
  • the first PSA network element corresponding to the first address of the terminal device can communicate with the first DNS server. In this way, the updated DNS request information can be transmitted to the first DNS server through the first PSA network element, thereby improving DNS resolution. This reduces the phenomenon of "DNS resolution failure" caused by "inability to communicate between the DNS server and the PSA network element" in the prior art.
  • the embodiment of the present application provides a third method for sending a domain name system request, and the method for sending a domain name system request is applied in a domain name resolution process.
  • the method for sending a domain name system request according to the embodiment of the present application includes the following steps:
  • the terminal device creates a PDU session.
  • S801 may refer to the relevant description of S301, which will not be repeated here.
  • the terminal apparatuses are assigned a plurality of addresses. Wherein, one address among the multiple addresses corresponds to one PSA network element, and different addresses among the multiple addresses correspond to different PSA network elements.
  • the SMF network element respectively delivers forwarding rule information to the C-PSA network element and the L-PSA network element to indicate
  • the C-PSA network element and the L-PSA network element send the data packet to the BP device when receiving the data packet with a specific destination address.
  • the forwarding rule information issued to the C-PSA network element is used to indicate that the C-PSA network element receives the destination address as "terminal device address@1", “terminal device address@2", ..., When the data packet of "address of the terminal device@n" is sent, the data packet is sent to the BP device.
  • the number of destination addresses in the forwarding rule information delivered to the C-PSA network element is (N-1).
  • multiple destination addresses may be combined in one forwarding rule information, or may be carried in different forwarding rule information, and transmitted to the C-PSA network element, which is not limited in this embodiment of the present application.
  • the L-PSA_1 network element is taken as an example to illustrate: the forwarding rule information delivered to the L-PSA_1 network element is used to indicate the L-PSA_1 network element.
  • - PSA_1 network element sends the data packet to the BP equipment when the destination address is "address of the terminal device@1", "address of the terminal device@2", ..., "address of the terminal device@n” .
  • the terminal device is allocated N addresses, correspondingly, the number of destination addresses in the forwarding rule information delivered to the L-PSA_1 network element is (N-1).
  • N the number of destination addresses in the forwarding rule information delivered to the L-PSA_1 network element.
  • multiple destination addresses may be combined in one forwarding rule information, or may be carried in different forwarding rule information, and transmitted to the L-PSA_1 network element, which is not limited in this embodiment of the present application.
  • For sending forwarding rule information to other network elements in the L-PSA network element reference may be made to the above description, and details are not repeated this time.
  • the terminal device sends DNS request information to the BP device.
  • the BP equipment receives the DNS request information from the terminal device.
  • the DNS request information includes the identifier, source address and destination address of the first application.
  • the source address of the DNS request information is the second address of the terminal device, which corresponds to the second PSA network element.
  • the destination address of the DNS request information is the address of the first DNS server, which corresponds to the first PSA network element.
  • the DNS request The source address of the information is "address of the terminal device@0", and the destination address of the DNS request information is "IP@1".
  • the first DNS server is the "L-DNS_1" server
  • the second PSA network element is the "C-PSA” network element.
  • the source address of the DNS request information is "address of the terminal device@1”
  • the destination address of the DNS request information is "IP@0”.
  • the first DNS server is the "C-DNS” server
  • the second PSA network element is the "L-PSA_1” network element.
  • the BP device sends the DNS request information to the first PSA network element corresponding to the destination address according to the destination address in the DNS request information.
  • the first PSA network element receives the DNS request information from the BP device.
  • the BP device sends DNS request information to the "C-PSA” network element. If the destination address of the DNS request information is "IP@1", the first PSA network element is the "L-PSA_1” network element. The BP device sends DNS request information to the "L-PSA_1" network element.
  • the first PSA network element sends DNS request information to the first DNS server.
  • the first DNS server receives the DNS request information from the first PSA network element.
  • the first PSA network element sends the DNS request information to the first DNS server according to the destination address in the DNS request information.
  • the first DNS server is a "C-DNS” server.
  • the "C-PSA” network element sends DNS request information to the "C-DNS” server.
  • the first PSA network element is the "L-PSA_1” network element, the first server is the "L-DNS” server.
  • the "L-PSA” network element sends DNS request information to the "L-DNS” server.
  • the first DNS server parses the DNS request information to obtain response information.
  • the DNS request information includes the identifier of the first application.
  • the response information includes the IP address of the application server corresponding to the first application.
  • the source address of the response information is the destination address of the DNS request information, and the destination address of the response information is the source address of the DNS request information.
  • the first DNS server sends response information to the first PSA network element.
  • the first PSA network element receives the response information from the first DNS server.
  • the source address of the response information is the address of the first DNS server, and the destination address of the response information is the second address of the terminal device.
  • the second address of the terminal device corresponds to the second PSA network element.
  • S806 can be specifically implemented as the following process:
  • the first PSA network element receives response information for the DNS request information from the first DNS server through the tunnel between the first PSA network element and the first DNS server.
  • a tunnel is established between the first PSA network element and the first DNS server.
  • the destination address of the response information is the second address of the terminal device, and the source address of the response information is the address of the first DNS server, since the second address of the terminal device corresponds to the second PSA network element, the response information can be passed through the first DNS server. Tunneling between a PSA network element and the first DNS server.
  • the destination address of the response information is "address@0 of the terminal device", and the source address of the response information is "IP@1".
  • the first DNS server is the "L-DNS_1" server
  • the first PSA network element is the "L-PSA_1” network element. Since the response information can be transmitted from the first DNS server to the first PSA network element through the tunnel. Therefore, in addition to carrying the source address and destination address in the response information, the response information also needs to encapsulate the address of the tunnel between the first PSA network element and the first DNS server to shield the destination address in the response information, so that the response information can be transmitted from the first PSA network element to the first DNS server.
  • a DNS server is transmitted to the first PSA network element.
  • the first PSA network element sends response information to the BP device according to the forwarding rule information.
  • the BP device receives the response information from the first PSA network element.
  • the first PSA network element sends response information to the BP device based on the forwarding rule information.
  • the forwarding rule information instructs the first PSA network element to send the data packet whose destination address is the second address to the BP device.
  • the data packet includes the above-mentioned response information.
  • the forwarding rule information may be preconfigured information, or may be information configured by the SMF network element for the first PSA. That is, the SMF network element sends forwarding rule information to the first PSA network element. Correspondingly, the first PSA network element receives the forwarding rule information from the SMF network element.
  • the BP device sends response information to the terminal device.
  • the terminal device receives the response information from the BP device.
  • the response information includes the IP address of the application server corresponding to the first application, the destination address of the DNS request information, and the source address of the DNS request information.
  • the BP device After receiving the DNS request information from the terminal device, the BP device sends the DNS request information to the first PSA network element corresponding to the destination address according to the destination address in the DNS request information. Since the destination address of the DNS request information corresponds to the first PSA network element, and the destination address of the DNS request information is the address of the first DNS server, the first DNS server and the first PSA network element can communicate with each other, which can reduce existing The phenomenon of "DNS resolution failure" caused by "inability to communicate between the DNS server and the PSA network element" in the technology improves the success rate of DNS resolution.
  • the first PSA network element can also send response information to the BP device according to the forwarding rule information, so that the response information can be provided to the terminal device through the BP device.
  • the embodiments of the present application also provide a device for sending a domain name system request, and the device for sending a domain name system request may be a network element in the above method embodiments, or a device including the above network element, or a device that can be used for a network element. part.
  • the apparatus for sending the domain name system request includes corresponding hardware structures and/or software modules for executing each function.
  • FIG. 9 shows a schematic structural diagram of an apparatus 900 for sending a domain name system request.
  • the apparatus 900 for sending a domain name system request includes a transceiver module 901 and a processing module 902 .
  • the processing module 902 is configured to determine the address of the first domain name system DNS server corresponding to the first application.
  • the processing module 902 is further configured to determine the first address of the terminal device according to the address of the first DNS server and the address of the terminal device corresponding to the address of the first DNS server.
  • the transceiver module 901 is used for sending DNS request information.
  • the DNS request information includes the identifier of the first application, the address of the first DNS server, and the first address of the terminal device.
  • the transceiver module 901 is further configured to receive the address of the first DNS server and the address of the terminal device corresponding to the address of the first DNS server from the SMF network element of the session management function.
  • the transceiver module 901 is configured to receive the identifier of the first application from the SMF network element and the address of the DNS server corresponding to the identifier of the first application.
  • the processing module 902 is configured to determine the address of the first DNS server according to the identifier of the first application and the address of the DNS server corresponding to the identifier of the first application.
  • the identifier of the first application corresponds to multiple DNS servers.
  • the processing module 902 is specifically configured to: determine the first DNS server that satisfies the preset policy from the plurality of DNS servers.
  • the preset policy includes at least one of the following: the priority of the first DNS server satisfies the priority condition among the priorities of the plurality of DNS servers; the distance between the first DNS server and the terminal device satisfies the separation distance condition.
  • the transceiver module 901 is configured to receive domain name system DNS request information from a terminal device.
  • the processing module 902 is configured to update at least one of the source address and the destination address in the DNS request information to obtain updated DNS request information.
  • the source address in the updated DNS request information is the first address of the terminal device, and the destination address in the updated DNS request information is the address of the first DNS server.
  • the transceiver module 901 is further configured to send the updated DNS request information to the first packet data unit session anchor PSA network element according to the source address in the updated DNS request information.
  • the first PSA network element corresponds to the first address of the terminal device, and the destination address in the updated DNS request information enables the updated DNS request information to be sent by the first PSA network element to the first DNS server.
  • the processing module 902 is specifically configured to: update at least one of the source address and the destination address in the DNS request information according to the identifier of the first application in the DNS request information, or, according to the DNS request information
  • the source address in the DNS request information is updated, or the source address in the DNS request information is updated according to the destination address in the DNS request information.
  • the processing module 902 is specifically configured to: determine the address of the first DNS server corresponding to the identifier of the first application; update the destination address in the DNS request information to the address of the first DNS server; The address of the DNS server and the address of the terminal device corresponding to the address of the first DNS server determine the first address of the terminal device; the source address in the DNS request information is the first address of the terminal device.
  • the transceiver module 901 is configured to receive the identifier of the first application and the address of the DNS server corresponding to the identifier of the first application from the SMF network element of the session management function.
  • the processing module 902 is configured to determine the address of the first DNS server according to the identifier of the first application and the address of the DNS server corresponding to the identifier of the first application.
  • the processing module 902 is specifically configured to: if the destination address in the DNS request information is the address of the first DNS server, then according to the address of the first DNS server and the terminal corresponding to the address of the first DNS server The address of the device is determined, the first address of the terminal device is determined, and the source address in the DNS request information is updated to the first address of the terminal device.
  • the transceiver module 901 is further configured to receive the address of the first DNS server from the SMF network element and the address of the terminal device corresponding to the address of the first DNS server.
  • the processing module 902 is specifically configured to: if the source address in the DNS request information is the first address of the terminal device, then according to the first address of the terminal device and the DNS corresponding to the first address of the terminal device The address of the server, determining the address of the first DNS server, and updating the destination address in the DNS request information to the address of the first DNS server.
  • the transceiver module 901 is further configured to receive the first address of the terminal device from the SMF network element and the address of the DNS server corresponding to the first address of the terminal device.
  • the transceiver module 901 is further configured to receive response information for the DNS request information from the first PSA network element.
  • the processing module 902 is configured to update at least one of the source address and the destination address in the response information to obtain the updated response information.
  • the source address in the updated response information is the destination address of the pre-update DNS request information, and the destination address in the updated response information is the source address of the pre-update DNS request information.
  • the transceiver module 901 is further configured to send the updated response information to the terminal device.
  • the transceiver module 901 is configured to receive domain name system DNS request information from a terminal device.
  • the transceiver module 901 is further configured to send the DNS request information to the first packet data unit session anchor PSA network element corresponding to the destination address according to the destination address in the DNS request information, enabling the DNS request information to be sent by the first PSA network element to the first DNS server.
  • the transceiver module 901 is configured to send DNS request information to the first domain name system DNS server.
  • the DNS request information includes the address of the first DNS server and the second address of the terminal device corresponding to the second PSA network element.
  • the transceiver module 901 is further configured to receive response information for the DNS request information from the first DNS server.
  • the processing module 902 is configured to make the transceiver module 901 send response information to the branch point BP device according to the forwarding rule information.
  • the forwarding rule information is used to instruct the first PSA network element to send the data packet whose destination address is the second address to the BP device; the data packet includes response information.
  • the transceiver module 901 is configured to receive forwarding rule information from the SMF network element of the session management function.
  • the transceiver module 901 is configured to receive response information for the DNS request information from the first DNS server through a tunnel between the first PSA network element and the first DNS server.
  • processing module 902 in this embodiment of the present application may be implemented by a processor or a processor-related circuit component
  • transceiver module 901 may be implemented by a transceiver or a transceiver-related circuit component.
  • the apparatus 900 for sending a domain name system request may further include a storage module 903 for storing program codes and data of the apparatus 900, and the data may include, but is not limited to, original data or intermediate data.
  • the processing module 902 may be a processor or a controller, for example, a central processing unit (central processing unit, CPU), a general-purpose processor, a digital signal processing (digital signal processing, DSP), an application-specific integrated Circuit (application specific integrated circuit, ASIC), field-programmable gate array (field-programmable gate array, FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. It may implement or execute the various exemplary logical blocks, modules and circuits described in connection with this disclosure.
  • a processor may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and the like.
  • the transceiver module 901 may be a transceiver, a transceiver circuit, a communication interface, or the like.
  • the storage module 903 may be a memory.
  • the processing module 902 is a processor
  • the transceiver module 901 is a communication interface
  • the storage module 903 is a memory
  • the structure of the device for sending the domain name system request involved in the embodiment of the present application may be as shown in FIG. 10 . .
  • FIG. 10 shows a simplified schematic diagram of a possible design structure of the apparatus for sending a domain name system request involved in the embodiment of the present application.
  • the apparatus 1000 for sending a domain name system request includes: a processor 1002 , a communication interface 1003 , and a memory 1001 .
  • the apparatus 1000 for sending a domain name system request may further include a bus 1004 .
  • the communication interface 1003 , the processor 1002 and the memory 1001 can be connected to each other through the bus 1004 .
  • the bus 1004 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, or the like.
  • the bus 1004 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one line is shown in FIG. 10, but it does not mean that there is only one bus or one type of bus.
  • a computer program product includes one or more computer instructions.
  • the computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • Computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website site, computer, server, or data center over a wire (e.g. coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (eg infrared, wireless, microwave, etc.) means to transmit to another website site, computer, server or data center.
  • a computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, a data center, or the like that includes an integration of one or more available media.
  • Useful media may be magnetic media (eg, floppy disk, hard disk, magnetic tape), optical media (eg, digital video disc (DVD)), or semiconductor media (eg, solid state disk (SSD)), etc. .
  • the disclosed system, apparatus and method may be implemented in other manners.
  • the device embodiments described above are only illustrative.
  • the division of modules is only a logical function division.
  • there may be other division methods for example, multiple modules or components may be combined or integrated. to another system, or some features can be ignored, or not implemented.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or modules, and may be in electrical or other forms.
  • a module described as a separate component may or may not be physically separated, and a component shown as a module may or may not be a physical module, that is, it may be located in one place, or may be distributed to multiple network devices (such as terminal devices). )superior. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution in this embodiment.
  • each functional module in each embodiment of the present application may be integrated into one processing module, or each functional module may exist independently, or two or more modules may be integrated into one module.
  • the above-mentioned integrated modules can be implemented in the form of hardware, or can be implemented in the form of hardware plus software function modules.
  • the present application can be implemented by means of software plus necessary general-purpose hardware, and of course hardware can also be used, but in many cases the former is a better implementation manner .
  • the technical solutions of the present application can be embodied in the form of software products in essence, or the parts that make contributions to the prior art.
  • the computer software products are stored in a readable storage medium, such as a floppy disk of a computer. , a hard disk or an optical disk, etc., including several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the methods described in the various embodiments of the present application.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请提供一种域名系统请求的发送方法及装置，涉及通信技术领域，能够提高域名系统DNS解析效率。该方法包括：终端装置确定第一应用对应的第一DNS服务器的地址。终端装置根据第一DNS服务器的地址和与第一DNS服务器的地址对应的终端装置的地址，确定终端装置的第一地址。之后，终端装置发送DNS请求信息。其中，DNS请求信息包括第一应用的标识、第一DNS服务器的地址和终端装置的第一地址。

Description

一种域名系统请求的发送方法及装置
本申请要求于2020年07月06日提交国家知识产权局、申请号为202010642999.5、发明名称为“一种域名系统请求的发送方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种域名系统请求的发送方法及装置。
背景技术
分组数据单元(packet data unit，PDU)会话(session)通过分组数据单元会话锚点(packet data unit session anchor，PSA)网元接入到数据网络(data network，DN)，从而使得终端装置与DN中的应用服务器(application server，AS)进行数据传输。PSA网元还与域名系统(domain name system，DNS)服务器通信连接。其中，对于部署于同一数据网络中的PSA网元、应用服务器和DNS服务器而言，DNS服务器接收来自PSA网元的DNS请求信息，对DNS请求信息中的域名进行解析，得到应用服务器的互联网协议(internet protocol，IP)地址，然后通过PSA网元提供给终端装置，以使终端装置根据上述应用服务器的IP地址，实现与应用服务器之间的数据传输。
在多宿主(multi-homing，MH)场景中，一个PDU会话存在多个PSA网元。通向不同PSA网元的用户面路径在分支点(branch point，BP)设备上分支。一个PSA网元与一台DNS服务器对应，且不同PSA网元与不同DNS服务器对应。在MH场景中，终端装置包括多个地址，且与多个PSA网元对应。其中，终端装置的一个地址对应一个PSA网元，终端装置的不同地址对应不同的PSA网元。
在MH场景中，对于一条DNS请求信息而言，DNS请求信息中的源(source)地址为终端装置的一个地址，且与一个PSA网元对应，DNS请求信息中的目的(destination)地址为一台DNS服务器的地址。若一条DNS请求信息中的源地址对应的PSA网元和目的地址对应的DNS服务器之间不存在对应关系，即源地址对应的PSA网元和目的地址对应的DNS服务器之间无法通信，则出现“DNS解析失败”的现象，导致DNS解析效率低。
发明内容
本申请实施例提供一种域名系统请求的发送方法及装置，能够提高DNS解析效率。
为达到上述目的，本申请实施例采用如下技术方案：
第一方面，本申请实施例提供一种域名系统请求的发送方法，该方法的执行主体可以是终端装置，也可以是应用于终端装置中的芯片。下面以执行主体是终端装置为例进行描述。该方法包括：终端装置确定第一应用对应的第一域名系统DNS服务器的地址。终端装置根据第一DNS服务器的地址和与第一DNS服务器的地址对应的终端装置的地址，确定终端装置的第一地址。之后，终端装置发送DNS请求信息。其中，DNS请求信息包括第一应用的标识、第一DNS服务器的地址和终端装置的第一地址。
由于第一DNS服务器的地址和终端装置的第一地址之间存在对应关系，且终端装置的第一地址对应一个PSA网元，也就是说，第一DNS服务器与终端装置的第一地址所对 应的PSA网元之间能够通信。由于终端装置发出的DNS请求信息是包括上述第一DNS服务器的地址和终端装置的第一地址，如此，DNS请求信息能够通过终端装置对应的PSA网元传输至第一DNS服务器，从而提高了DNS解析的成功率，减少现有技术中“DNS服务器与PSA网元之间无法通信”所导致的“DNS解析失败”的现象。
在一种可能的设计中，本申请实施例域名系统请求的发送方法还包括：终端装置接收来自会话管理功能SMF网元的第一DNS服务器的地址和与第一DNS服务器的地址对应的终端装置的地址。例如，“第一DNS服务器的地址和与第一DNS服务器的地址对应的终端装置的地址”可以承载于路径选择规则(routing rule)中，传输给终端装置。也就是说，SMF网元能够为终端装置提供“第一DNS服务器的地址和与第一DNS服务器的地址对应的终端装置的地址”这一信息。
在一种可能的设计中，终端装置确定第一应用对应的第一DNS服务器的地址，包括：终端装置接收来自SMF网元的第一应用的标识和与第一应用的标识对应的DNS服务器的地址。例如，“第一应用的标识和与第一应用的标识对应的DNS服务器的地址”可以承载于路径选择规则(routing rule)中，传输给终端装置。之后，终端装置根据第一应用的标识和与第一应用的标识对应的DNS服务器的地址，确定第一DNS服务器的地址。
如此，在SMF网元为终端装置提供“第一应用的标识和第一应用的标识对应的DNS服务器的地址”的情况下，终端装置即可依据SMF网元提供的信息，确定第一DNS服务器的地址。
在一种可能的设计中，第一应用的标识对应多个DNS服务器。终端装置根据第一应用的标识和与第一应用的标识对应的DNS服务器的地址，确定第一DNS服务器的地址，包括：终端装置从多个DNS服务器中确定满足预设策略的第一DNS服务器。其中，预设策略包括以下至少一项：第一DNS服务器的优先级在多个DNS服务器的优先级中满足优先级条件；第一DNS服务器与终端装置之间的距离满足间隔距离条件。
如此，在第一应用的标识对应多个DNS服务器的情况下，终端装置能够依据预配置的预设策略，从多个DNS服务器中确定一个DNS服务器，作为第一DNS服务器，进而确定第一DNS服务器的地址。
第二方面，本申请实施例提供一种域名系统请求的发送方法，该方法的执行主体可以是分支点BP设备，也可以是应用于BP设备中的芯片。下面以执行主体是BP设备为例进行描述。该方法包括：BP设备接收来自终端装置的域名系统DNS请求信息，之后，BP设备更新DNS请求信息中的源地址和目的地址中的至少一项，得到更新后的DNS请求信息。其中，更新后的DNS请求信息中的源地址为终端装置的第一地址，更新后的DNS请求信息中的目的地址为第一DNS服务器的地址。BP设备根据更新后的DNS请求信息中的源地址，向第一分组数据单元会话锚点PSA网元发送更新后的DNS请求信息。其中，第一PSA网元与终端装置的第一地址对应，更新后的DNS请求信息中的目的地址用于第一PSA网元向第一DNS服务器发送更新后的DNS请求信息，使能第一DNS服务器解析更新后的DNS请求信息。
由于更新后的DNS请求信息中的源地址为终端装置的第一地址，更新后的DNS请求信息中的目的地址为第一DNS服务器的地址。终端装置的第一地址对应的第一PSA网元与第一DNS服务器之间能够通信，如此，更新后的DNS请求信息能够通过第一PSA网元 传输至第一DNS服务器，从而提高了DNS解析的成功率，减少现有技术中“DNS服务器与PSA网元之间无法通信”所导致的“DNS解析失败”的现象。
在一种可能的设计中，BP设备更新DNS请求信息中的源地址和目的地址中的至少一项，包括：BP设备根据DNS请求信息中第一应用的标识，更新DNS请求信息中的源地址和目的地址中的至少一项，或者，BP设备根据DNS请求信息中的源地址，更新DNS请求信息中的目的地址，或者，BP设备根据DNS请求信息中的目的地址，更新DNS请求信息中的源地址。
也就是说，BP设备在更新DNS请求信息的过程中，BP设备能够基于DNS请求信息中的第一应用的标识，或DNS请求信息的源地址，或DNS请求信息的目的地址，来更新DNS请求信息中的源地址和目的地址中的至少一项，以得到更新后的DNS请求信息。
在一种可能的设计中，BP设备根据DNS请求信息中第一应用的标识，更新DNS请求信息中的源地址和目的地址中的至少一项，包括：BP设备确定第一应用的标识对应的第一DNS服务器的地址，之后，BP设备将DNS请求信息中的目的地址更新为第一DNS服务器的地址。BP设备根据第一DNS服务器的地址和与第一DNS服务器的地址对应的终端装置的地址，确定终端装置的第一地址，之后，BP设备将DNS请求信息中的源地址为终端装置的第一地址。
如此，BP设备即可基于第一应用的标识来更新DNS请求信息中的源地址和目的地址，以得到更新后的DNS请求信息。
在一种可能的设计中，BP设备确定第一应用的标识对应的第一DNS服务器的地址，包括：BP设备接收来自会话管理功能SMF网元的第一应用的标识和与第一应用的标识对应的DNS服务器的地址，之后，BP设备根据第一应用的标识和与第一应用的标识对应的DNS服务器的地址，确定第一DNS服务器的地址。
如此，在SMF网元为BP设备提供“第一应用的标识和第一应用的标识对应的DNS服务器的地址”的情况下，BP设备即可根据SMF网元提供的信息，来确定第一DNS服务器的地址。
在一种可能的设计中，BP设备根据DNS请求信息中的目的地址，更新DNS请求信息中的源地址，包括：若DNS请求信息中的目的地址为第一DNS服务器的地址，则BP设备根据第一DNS服务器的地址和与第一DNS服务器的地址对应的终端装置的地址，确定终端装置的第一地址。之后，BP设备将DNS请求信息中的源地址更新为终端装置的第一地址。
也就是说，BP设备接收DNS请求信息之后，以DNS请求信息中的目的地址为基准，替换DNS请求信息中的源地址，以保证更新后的DNS请求信息中的源地址对应的PSA网元与第一DNS服务器之间能够通信。
在一种可能的设计中，本申请实施例域名系统请求的发送方法还包括：BP设备接收来自SMF网元的第一DNS服务器的地址和与第一DNS服务器的地址对应的终端装置的地址。
也就是说，SMF网元能够为BP设备提供“第一DNS服务器的地址和与第一DNS服务器的地址对应的终端装置的地址”这一信息。
在一种可能的设计中，BP设备根据DNS请求信息中的源地址，更新DNS请求信息中 的目的地址，包括：若DNS请求信息中的源地址为终端装置的第一地址，则BP设备根据终端装置的第一地址和与终端装置的第一地址对应的DNS服务器的地址，确定第一DNS服务器的地址。之后，BP设备将DNS请求信息中的目的地址更新为第一DNS服务器的地址。
也就是说，BP设备接收DNS请求信息之后，以DNS请求信息中的源地址为基准，替换DNS请求信息中的目的地址，以保证更新后的DNS请求信息中的源地址对应的PSA网元与第一DNS服务器之间能够通信。
在一种可能的设计中，本申请实施例域名系统请求的发送方法还包括：BP设备接收来自SMF网元的终端装置的第一地址和与终端装置的第一地址对应的DNS服务器的地址。
也就是说，SMF网元能够为BP设备提供“终端装置的第一地址和与终端装置的第一地址对应的DNS服务器的地址”这一信息。
在一种可能的设计中，本申请实施例域名系统请求的发送方法还包括：BP设备接收来自第一PSA网元的针对DNS请求信息的响应信息。之后，BP设备更新响应信息中的源地址和目的地址中的至少一项，得到更新后的响应信息。其中，更新后的响应信息中的源地址为更新前的DNS请求信息的目的地址，更新后的响应信息中的目的地址为更新前的DNS请求信息的源地址。然后，BP设备向终端装置发送更新后的响应信息。其中，DNS请求信息包括第一应用的标识，响应信息包括第一应用对应的应用服务器的互联网协议IP地址。
这里，更新后的响应信息包括第一应用对应的应用服务器的IP地址、更新前的DNS请求信息的目的地址和更新前的DNS请求信息的源地址。由于终端装置发送DNS请求信息之后，需监听携带更新前的DNS请求信息的源地址和目的地址的响应消息。BP设备能够替换响应信息中的源地址和目的地址中的至少一项，以保证终端装置能够监听到携带更新前的DNS请求信息的源地址和目的地址的响应消息。
第三方面，本申请实施例提供一种域名系统请求的发送方法，该方法的执行主体可以是分支点BP设备，也可以是应用于BP设备中的芯片。下面以执行主体是BP设备为例进行描述。该方法包括：BP设备接收来自终端装置的域名系统DNS请求信息，之后，BP设备根据DNS请求信息中的目的地址，向目的地址对应的第一分组数据单元会话锚点PSA网元发送DNS请求信息。其中，DNS请求信息用于第一PSA网元向第一DNS服务器发送DNS请求信息，使能第一DNS服务器解析DNS请求信息。
这里，由于DNS请求信息的目的地址与第一PSA网元对应，DNS请求信息的目的地址为第一DNS服务器的地址，第一DNS服务器与第一PSA网元之间能够通信，也就能够减少现有技术中“DNS服务器与PSA网元之间无法通信”所导致的“DNS解析失败”的现象，提高DNS解析的成功率。
第四方面，本申请实施例提供一种域名系统请求的发送方法，该方法的执行主体可以是第一PSA网元，也可以是应用于第一PSA网元中的芯片。下面以执行主体是第一PSA网元为例进行描述。该方法包括：第一PSA网元向第一域名系统DNS服务器发送DNS请求信息。其中，DNS请求信息包括第一DNS服务器的地址和对应第二PSA网元的终端装置的第二地址。之后，第一PSA网元接收来自第一DNS服务器的针对DNS请求信息的响应信息。然后，第一PSA网元根据转发规则信息，向分支点BP设备发送响应信息。其中，转发规则信息用于指示第一PSA网元将目的地址为第二地址的数据包发送至BP设备，数 据包包括响应信息。
这里，响应信息是针对DNS请求信息的响应信息。也就是说，在第一DNS服务器反馈响应信息的过程中，第一PSA网元接收来自第一DNS服务器的响应信息之后，即使响应信息的目的地址是终端装置的第二地址，与第二PSA网元对应，第一PSA网元也能够根据转发规则信息，向BP设备发送响应信息，使得响应信息能够通过BP设备提供给终端装置。
在一种可能的设计中，本申请实施例域名系统请求的发送方法还包括：第一PSA网元接收来自会话管理功能SMF网元的转发规则信息。也就是说，由SMF网元为第一PSA网元提供转发规则信息，以使第一PSA网元根据转发规则信息，转发响应信息。
在一种可能的设计中，第一PSA网元接收来自第一DNS服务器的针对DNS请求信息的响应信息，包括：第一PSA网元通过第一PSA网元和第一DNS服务器之间的隧道接收来自第一DNS服务器的针对DNS请求信息的响应信息。其中，DNS请求信息包括第一应用的标识，响应信息包括第一应用对应的应用服务器的互联网协议IP地址。
也就是说，第一PSA网元和第一DNS服务器之间的隧道，能够屏蔽响应信息中的目的地址，使得响应信息能够从第一DNS服务器传输至第一PSA网元。
第五方面，本申请实施例提供一种域名系统请求的发送装置，该域名系统请求的发送装置包括：用于执行上述任一方面中各个步骤的单元。该域名系统请求的发送装置可以为上述第一方面或第一方面任一种可能的设计中的终端装置，或者实现上述终端装置功能的芯片。所述域名系统请求的发送装置包括实现上述方法相应的模块、单元、或手段(means)，该模块、单元、或手段可以通过硬件实现，软件实现，或者通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块或单元。
第六方面，本申请实施例提供一种域名系统请求的发送装置，包括处理器和接口电路，处理器用于通过接口电路与其它装置通信，并执行以上任一方面提供的域名系统请求的发送方法。该处理器包括一个或多个。该域名系统请求的发送装置可以为上述第一方面或第一方面任一种可能的设计中的终端装置，或者实现上述终端装置功能的芯片。
第七方面，本申请实施例提供了一种域名系统请求的发送装置，包括：处理器和存储器；该存储器用于存储计算机指令，当该处理器执行该指令时，以使该域名系统请求的发送装置执行上述任一方面所述的方法。该域名系统请求的发送装置可以为上述第一方面或第一方面任一种可能的设计中的终端装置，或者实现上述终端装置功能的芯片。
第八方面，本申请实施例提供了一种域名系统请求的发送装置，包括：处理器；所述处理器用于与存储器耦合，并读取存储器中的指令之后，根据所述指令执行如上述任一方面所述的方法。该域名系统请求的发送装置可以为上述第一方面或第一方面任一种可能的设计中的终端装置，或者实现上述终端装置功能的芯片。
第九方面，本申请实施例提供一种域名系统请求的发送装置，该域名系统请求的发送装置包括：用于执行上述任一方面中各个步骤的单元。该域名系统请求的发送装置可以为上述第二方面或第二方面任一种可能的设计中的BP设备，或者实现上述BP设备功能的芯片；或者，该域名系统请求的发送装置可以为上述第三方面或第三方面任一种可能的设计中的BP设备，或者实现上述BP设备功能的芯片。所述域名系统请求的发送装置包括实现上述方法相应的模块、单元、或手段(means)，该模块、单元、或手段可以通过硬件实现， 软件实现，或者通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块或单元。
第十方面，本申请实施例提供一种域名系统请求的发送装置，包括处理器和接口电路，处理器用于通过接口电路与其它装置通信，并执行以上任一方面提供的域名系统请求的发送方法。该处理器包括一个或多个。该域名系统请求的发送装置可以为上述第二方面或第二方面任一种可能的设计中的BP设备，或者实现上述BP设备功能的芯片；或者，该域名系统请求的发送装置可以为上述第三方面或第三方面任一种可能的设计中的BP设备，或者实现上述BP设备功能的芯片。
第十一方面，本申请实施例提供了一种域名系统请求的发送装置，包括：处理器和存储器；该存储器用于存储计算机指令，当该处理器执行该指令时，以使该域名系统请求的发送装置执行上述任一方面所述的方法。该域名系统请求的发送装置可以为上述第二方面或第二方面任一种可能的设计中的BP设备，或者实现上述BP设备功能的芯片；或者，该域名系统请求的发送装置可以为上述第三方面或第三方面任一种可能的设计中的BP设备，或者实现上述BP设备功能的芯片。
第十二方面，本申请实施例提供了一种域名系统请求的发送装置，包括：处理器；所述处理器用于与存储器耦合，并读取存储器中的指令之后，根据所述指令执行如上述任一方面所述的方法。该域名系统请求的发送装置可以为上述第二方面或第二方面任一种可能的设计中的BP设备，或者实现上述BP设备功能的芯片；或者，该域名系统请求的发送装置可以为上述第三方面或第三方面任一种可能的设计中的BP设备，或者实现上述BP设备功能的芯片。
第十三方面，本申请实施例提供一种域名系统请求的发送装置，该域名系统请求的发送装置包括：用于执行上述任一方面中各个步骤的单元。该域名系统请求的发送装置可以为上述第四方面或第四方面任一种可能的设计中的第一PSA网元，或者实现上述第一PSA网元功能的芯片。所述域名系统请求的发送装置包括实现上述方法相应的模块、单元、或手段(means)，该模块、单元、或手段可以通过硬件实现，软件实现，或者通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块或单元。
第十四方面，本申请实施例提供一种域名系统请求的发送装置，包括处理器和接口电路，处理器用于通过接口电路与其它装置通信，并执行以上任一方面提供的域名系统请求的发送方法。该处理器包括一个或多个。该域名系统请求的发送装置可以为上述第四方面或第四方面任一种可能的设计中的第一PSA网元，或者实现上述第一PSA网元功能的芯片。
第十五方面，本申请实施例提供了一种域名系统请求的发送装置，包括：处理器和存储器；该存储器用于存储计算机指令，当该处理器执行该指令时，以使该域名系统请求的发送装置执行上述任一方面所述的方法。该域名系统请求的发送装置可以为上述第四方面或第四方面任一种可能的设计中的第一PSA网元，或者实现上述第一PSA网元功能的芯片。
第十六方面，本申请实施例提供了一种域名系统请求的发送装置，包括：处理器；所述处理器用于与存储器耦合，并读取存储器中的指令之后，根据所述指令执行如上述任一方面所述的方法。该域名系统请求的发送装置可以为上述第四方面或第四方面任一种可能 的设计中的第一PSA网元，或者实现上述第一PSA网元功能的芯片。
第十七方面，本申请实施例提供一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机可以执行上述任一方面中任一项的域名系统请求的发送方法。
第十八方面，本申请实施例提供一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机可以执行上述任一方面中任一项的域名系统请求的发送方法。
第十九方面，本申请实施例提供一种电路系统，电路系统包括处理电路，处理电路被配置为执行如上述任一方面中任一项的域名系统请求的发送方法。
第二十方面，本申请实施例提供一种芯片，芯片包括处理器，处理器和存储器耦合，存储器存储有程序指令，当存储器存储的程序指令被处理器执行时实现上述任一方面任意一项的域名系统请求的发送方法。
第二十一方面，本申请实施例提供一种域名系统请求的发送系统，该域名系统请求的发送系统包括上述第一方面中任一项中的终端装置，或包括第二方面中任一项中的BP设备，或包括第三方面中任一项中的BP设备和第四方面中任一项中的第一PSA网元。
其中，第五方面至第二十一方面中任一种设计所带来的技术效果可参考上文所提供的对应的方法中的有益效果，此处不再赘述。
附图说明
图1为本申请实施例提供的一种网络架构的示意图；
图2为本申请实施例提供的再一种网络架构的示意图；
图3为本申请实施例提供的一种域名系统请求的发送方法的流程示意图；
图4为本申请实施例提供的再一种域名系统请求的发送方法的流程示意图；
图5为本申请实施例提供的又一种域名系统请求的发送方法的流程示意图；
图6为本申请实施例提供的又一种域名系统请求的发送方法的流程示意图；
图7为本申请实施例提供的又一种域名系统请求的发送方法的流程示意图；
图8为本申请实施例提供的又一种域名系统请求的发送方法的流程示意图；
图9为本申请实施例提供的一种域名系统请求的发送装置的结构示意图；
图10为本申请实施例提供的再一种域名系统请求的发送装置的结构示意图。
具体实施方式
本申请的说明书以及附图中的术语“第一”和“第二”等是用于区别不同的对象，或者用于区别对同一对象的不同处理，而不是用于描述对象的特定顺序。此外，本申请的描述中所提到的术语“包括”和“具有”以及它们的任何变形，意图在于覆盖不排他的包含。例如包含了一系列步骤或单元的过程、方法、系统、产品或设备没有限定于已列出的步骤或单元，而是可选地还包括其他没有列出的步骤或单元，或可选地还包括对于这些过程、方法、产品或设备固有的其它步骤或单元。本申请实施例中，“多个”包括两个或两个以上。本申请实施例中，“示例性的”或者“例如”等词用于表示作例子、例证或说明。本申请实施例中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言，使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念。
首先，介绍本申请实施例中所涉及的技术术语：
1、域名解析
DNS是互联网上作为域名(domain name)和互联网协议(internet protocol，IP)地址相互映射的一个分布式数据库，能够将域名映射为应用服务器的IP地址。这里，将域名映射为应用服务器的IP地址的过程，即称为“域名解析”。
其中，域名，也称为网域，是由一串用点分隔的名字组成的因特网上某一台计算机或计算机组的名称，用于在数据传输时标识计算机的电子方位或地理位置。例如，域名可以为www.123456.com.cn。
其中，DNS中的域名解析设备即为DNS服务器。这里，DNS服务器能够通过域名解析机制，对终端装置请求的域名进行解析，得到域名对应的应用服务器的IP地址。可选的，DNS服务器的数量可以为多个，且以阶层式的架构分布。在上述域名解析机制中，DNS依次通过由低到高的阶层的DNS服务器，对域名进行解析，直至得到上述域名对应的应用服务器的IP地址。本申请实施例对域名解析机制不做详细赘述。
示例性的，终端装置访问目标域名的过程如下：终端装置获取目标域名后，向DNS服务器发送携带目标域名的DNS请求信息。相应的，DNS服务器接收来自终端装置的DNS请求信息。之后，DNS服务器解析出上述目标域名对应的目标应用服务器的IP地址，并将上述目标应用服务器的IP地址携带在响应信息中发送给终端装置。相应的，终端装置接收来自DNS服务器的响应信息，以使终端装置获取上述目标应用服务器的IP地址，并根据该IP地址实现与上述目标应用服务器之间的数据传输。这里，“DNS请求信息”也可以描述为“请求消息”，或“域名解析请求消息”。“响应消息”也可以描述为“应答消息”，或“DNS回复(response)”，或“域名解析应答消息”，与DNS请求信息相对应。
2、PDU会话
PDU会话，是终端装置和数据网络之间的连接，用于在终端装置和数据网络之间传输数据。终端装置可以通过多个PDU会话，来连接到相同的数据网络或者不同的数据网络。
3、MH机制
终端装置可以通过由不同的PSA网元提供服务的一个或多个PDU会话，来连接到相同的数据网络。这里，PSA网元可以为连接到数据网络的用户面功能(user plane function，UPF)网元。PSA也可以记为PDU会话锚点UPF。在本申请实施例中，以“UPF作为PSA”为例进行示例性说明。在MH机制中，一个PDU会话通过多个PSA网元接入到数据网络中。通向不同的PSA网元的用户面路径BP设备上分支。这里，BP设备也可以是一个UPF网元。
在MH机制中，终端装置包括多个地址，且与多个PSA网元对应。其中，终端装置的一个地址对应一个PSA网元，终端装置的不同地址对应不同的PSA网元。
在终端装置访问目标域名的过程中，终端装置向BP设备发送DNS请求信息。相应的，BP设备接收来自终端装置的DNS请求信息。其中，DNS请求信息除了包括目标域名之外，还包括源地址和目的地址。其中，DNS请求信息中的源地址为终端装置的一个地址，且与一个PSA网元对应。DNS请求信息中的目的地址为一台DNS服务器的地址。若一条DNS请求信息中的源地址对应的PSA网元和目的地址对应的DNS服务器之间不存在对应关系，即源地址对应的PSA网元和目的地址对应的DNS服务器之间无法通信，则出现“DNS解析失败”的现象，导致DNS解析效率低。
有鉴于此，本申请实施例提供了一种域名系统请求的发送方法，首先对本申请实施例域名系统请求的发送方法所适用的系统进行说明，该系统可以是支持第五代(fifth-generation，5G)移动通信技术的通信系统，例如NR接入技术；或者，该系统还可以是支持多种无线技术的通信系统，例如支持LTE技术和新无线(new radio，NR)接入技术的通信系统。另外，该系统也可以适用于面向未来的通信技术。
参见图1，以支持5G移动通信技术的通信系统为例，对该系统的网络架构进行介绍。该5G网络架构中的网元包括终端装置、接入网络(access network，AN)设备、接入与移动管理功能(authentication management function，AMF)网元、会话管理功能(session management function，SMF)网元、PSA网元、BP设备和数据网络(data network，DN)等。图1中仅示出了两个PSA网元。图1仅为示意图，并不构成对本申请实施例域名系统请求的发送方法的适用场景的限定。
其中，终端装置，又称为用户设备(user equipment，UE)、终端设备、移动台(mobile station，MS)、移动终端(mobile terminal，MT)等，是一种向用户提供语音/数据连通性的设备，例如，具有无线连接功能的手持式设备或车载设备等。终端装置具体可以为：手机(mobile phone)、平板电脑、笔记本电脑、掌上电脑、移动互联网设备(mobile internet device，MID)、可穿戴设备、虚拟现实(virtual reality，VR)设备、增强现实(augmented reality，AR)设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程手术(remote medical surgery)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、或智慧家庭(smart home)中的无线终端，未来5G通信网络或5G之后的通信网络中的终端装置等，本申请实施例对此不作限定。
接入网络设备，也可以为无线接入网络(radio access network，RAN)设备，其是一种部署在无线接入网用以提供无线通信功能的装置。可选的，本申请实施例所涉及的RAN设备包括例如但不限于如下各种形式的宏基站，微基站(也称为小站)，中继站，发送接收点(transmission reception point，TRP)，下一代网络节点(g Node B，gNB)、连接下一代核心网的演进型节点B(ng evolved Node B，ng-eNB)等，还可以包括无线局域网(wireless local area network，WLAN)接入设备等非第三代合作伙伴计划(3rd generation partnership project，3GPP)系统的RAN设备。
AMF网元，具有终端装置的移动性管理、注册管理、连接管理、合法监听、支持传输终端装置和SMF之间的会话管理(session management，SM)信息、接入认证和接入授权等功能。
SMF网元，具有会话管理、漫游等功能。其中，会话管理功能，例如，会话建立、修改和释放。漫游功能可以包括计费数据收集、支持与外部(external)数据网络进行认证/授权的信令传输。
PSA网元，是用户面的功能网元，主要负责连接外部网络，以及对用户报文进行处理，如转发、计费、合法监听等。可选的，PSA网元还可以接收数据。图1中仅示出了两个PSA网元，分别记为PSA网元1和PSA网元2。
BP设备，能够从终端装置接收上行数据包，并根据上行数据包的源地址分发给源地址对应的PSA网元。BP设备还能够从PSA网元接收下行数据包，并汇聚从PSA网元收到的 下行数据包，发送给终端装置。这里，BP设备也可以实现为UPF网元。
数据网络，是为终端装置提供服务的网络，如一些数据网络为终端装置提供上网功能，另一些数据网络为终端装置提供短信功能等。
其中，终端装置通过N1接口与AMF网元通信，AN设备通过N2接口与AMF网元通信，AN设备通过N3接口与BP设备通信，BP设备通过N4接口与SMF网元通信，BP设备通过N9接口与UPF网元通信，UPF网元通过N4接口与SMF网元通信，UPF网元通过N6接口接入数据网络，AMF网元通过N11接口与SMF网元通信。在图1中，虚线示出了能够进行控制面信令交互的路径，实线示出了能够进行用户面数据交互的路径。
需要说明的是，与不同的PSA网元连接的数据网络位于不同的数据中心(data center，DC)。仍以图1所示的场景为例，对数据网络的分布状况进行说明。参见图2，与PSA网元1连接的数据网络可以是中心数据网络(central data network)或中心数据中心(central data center)。此种情况下，PSA网元1可以记为central PSA，简称为C-PSA。与PSA网元1连接的数据网络也可以是远端数据网络(remote data network)或远端数据中心(remote data center)。此种情况下，PSA网元1可以记为remote PSA，简称为R-PSA。PSA网元1还能够与上述数据网络中的DNS服务器通信。与PSA网元2连接的数据网络位于本地DC或边缘数据网络(edge data network，EDN)。此种情况下，PSA网元2可以记为Local PSA，简称为L-PSA。不同的L-PSA网元可以标识不同的数字后缀。例如，第一个L-PSA网元可以记为L-PSA_1,第二个L-PSA网元可以记为L-PSA_2。PSA网元2还能够与本地DC中的DNS服务器通信。位于不同DC中的PSA网元和DNS服务器之间可能没有IP连通，无法通信。例如，PSA网元1无法与本地DC中的DNS服务器通信。PSA网元2无法与中心DC中的DNS服务器通信。当终端装置所处的位置存在PSA网元2，以使终端装置接入本地DC中的DN时，SMF网元将该PSA网元2作为本地PSA插入到会话路径中，以便终端装置能够就近访问本地DN中的应用。BP设备与L-PSA网元可以分开部署，也可以合一部署。在图2所示的场景中，BP设备的功能和PSA网元2的功能由同一网元来实现，该网元可以是PSA网元2。
这里，本地DC或边缘数据网络可以实现为移动边缘计算(mobile/multi-access edge computing，MEC)节点。通常，MEC节点包括MEC平台以及数据面功能网元。其中，MEC平台上可以部署各种应用服务器和DNS服务器等，本申请实施例对此不作具体限定。本申请实施例中的MEC平台也可以称之为MEC系统或其他，本申请实施例对此不作具体限定。数据面功能网元可以由PSA网元来实现。应用服务器是指能够提供相应服务的载体。例如，微信应用服务器可以是能够提供微信服务的载体。其中，载体可以是虚拟设备，如虚拟机或容器等，也可以是实体设备，本申请实施例对此不作具体限定。
本申请实施例描述的系统以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定。本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
下面对本申请实施例提供的域名系统请求的发送方法进行具体阐述。
需要说明的是，本申请下述实施例中各个网元之间的消息名字或消息中各参数的名字等只是一个示例，具体实现中也可以是其他的名字，在此统一说明，以下不再赘述。
本申请实施例提供第一种域名系统请求的发送方法，该域名系统请求的发送方法应用在域名解析过程中。参见图3，本申请实施例域名系统请求的发送方法包括如下步骤：
S301、终端装置创建PDU会话。
示例性的，终端装置发起会话创建请求消息，以创建PDU会话。PDU会话创建流程由网络设备(如SMF网元和UPF网元)和终端装置共同完成。会话创建流程的详细实现过程可以参见现有技术，这里不再赘述。
PDU会话的用户面路径包括：从RAN设备到BP设备的路径，和BP设备到PSA网元的路径。这里，PSA网元的数量是两个或两个以上。PSA网元可以是本地DC中的PSA网元，可以是中心DC中的PSA网元。相应的，终端装置被分配多个地址。在实际应用过程中，终端装置被分配的地址可以是具体地址，如互联网通信协议第四版(internet protocol version 4，IPv4)的地址，也可以是地址前缀(prefix)，如互联网通信协议第六版(internet protocol version 6，IPv6)的地址前缀。终端装置的一个地址对应一个PSA网元，终端装置的不同地址对应不同PSA网元。终端装置的多个地址可以由SMF网元分配,也可以是由PSA网元分配。在PSA网元为终端装置分配地址的情况下，一个PSA网元为终端装置分配一个地址，不同的PSA网元为终端装置分配不同的地址。示例性的，参见表1，表1示出了终端装置的地址与PSA网元之间的对应关系。
表1
终端装置的地址 PSA网元
终端装置的地址@0 C-PSA
终端装置的地址@1 L-PSA_1
…  
终端装置的地址@n L-PSA_n
参见表1，表1示出了终端装置的(n+1)个地址，分别记为：终端装置的地址@0、终端装置的地址@1、…、终端装置的地址@n。PSA网元的数量为(n+1)个，分别记为：C-PSA、L-PSA_1、…、L-PSA_n。在表1中，位于同一行的终端装置的地址与PSA网元之间存在对应关系。如表1所示，“终端装置的地址@0”与“C-PSA”网元对应，“终端装置的地址@1”与“L-PSA_1”网元对应，…，“终端装置的地址@n”与“L-PSA_n”网元对应。
另外，PSA网元能够服务或接入特定的数据网络/数据中心。这些“数据网络/数据中心”中可以部署DNS服务器，以通过DNS服务器进行DNS解析。DNS服务器也可以部署在PSA网元上，DNS服务器还可以部署在PSA网元与“数据网络/数据中心”之间的路径上。本申请实施例对DNS服务器的部署位置不作限定，保障PSA网元收到DNS请求信息之后，能够将DNS请求信息发送至对应的DNS服务器。如此，DNS服务器和“数据网络/数据中心”之间存在对应关系，PSA与“数据网络/数据中心”之间也存在对应关系。也就是说，对于与同一“数据网络/数据中心”存在对应关系的PSA网元和DNS服务器而言，两者之间能够通信，也就存在对应关系。示例性的，参见表2，表2以“DNS服务器的地址”为例，示出了PSA网元与DNS服务器之间的对应关系。这里，DNS服务器的地址可以由IP地址或域名等来标识。这里，至少有两个DNS服务器的地址是不同的。也就是说，DNS服务器的地址不完全相同。不同DNS服务器的地址可以相同，也可以不同。
表2
DNS服务器的地址 PSA网元
IP@0 C-PSA
IP@1 L-PSA_1
…  
IP@n L-PSA_n
参见表2，表2示出了(n+1)个DNS服务器的地址，分别记为：IP@0、IP@1、…、IP@n。其中，“IP@0、IP@1、…、IP@n”中可能有地址相同的情况。PSA网元的数量为(n+1)个，分别记为：C-PSA、L-PSA_1、…、L-PSA_n。在表2中，位于同一行中的DNS服务器与PSA网元之间存在对应关系，如表2所示例如，“IP@0”与“C-PSA”网元对应，“IP@1”与“L-PSA_1”网元对应，…，“IP@n”与“L-PSA_n”网元对应。
需要说明的是，表1仅以“表格”的形式示出了“终端装置的地址与PSA网元之间的对应关系”。表2仅以“表格”的形式示出了“PSA网元与DNS服务器之间的对应关系”。表1和表2可以合并在同一表格中，以呈现“终端装置的地址与PSA网元之间的对应关系”和“PSA网元与DNS服务器之间的对应关系”，本申请实施例对此不作限定。
S302、终端装置确定第一应用对应的第一DNS服务器的地址。
其中，第一应用可以是指安装在终端装置上，用于访问应用服务器提供的服务的软件产品。这些软件产品也可以称为应用客户端。
其中，“第一应用对应的第一DNS服务器”是指，与第一DNS服务器对应的数据网络部署有第一应用对应的应用服务器。第一DNS服务器的地址可以由IP地址或域名等来标识。
示例性的，第一应用可以是终端装置上的微信客户端。相应的，应用服务器是微信应用服务器，为终端装置上的微信客户端提供服务。第一DNS服务器是能够解析包括微信应用的DNS请求信息的DNS服务器。以图2所示的场景为例，若中心DC中的应用服务器上部署有“微信”这一应用，而本地DC中的应用服务器上未部署“微信”这一应用，则第一DNS服务器可以是中心DC中的DNS服务器，可以记为“C-DNS”服务器。反之，若中心DC中的应用服务器上未部署“微信”这一应用，而本地DC中的应用服务器上部署有“微信”这一应用，则第一DNS服务器是中心DC中的DNS服务器，可以记为“L-DNS”服务器。
需要说明的是，由于不同数据网络可能部署有不同的应用，而同一数据网络中的应用服务器通常由数据网络对应的DNS服务器负责解析。所以，不同应用与不同DNS服务器之间也就存在一定的对应关系。示例性的，参见表3-1，表3-1以“应用的标识”和“DNS服务器的地址”为例，示出了“不同应用与不同DNS服务器之间的对应关系”。这里，应用的标识可以是全限定域名(fully qualified domain name，FQDN)。数据网络与DNS服务器的地址之间具有一一对应关系，所以，“不同应用与不同DNS服务器之间的对应关系”也能够指示DNS服务器对应的数据网络中部署有哪些应用。
表3-1
应用的标识 DNS服务器的地址
FQDN_1 IP@1
FQDN_1 IP@2
FQDN_2 IP@1
FQDN_3 IP@3
… …
FQDN_n IP@2
参见表3-1，表3-1示出了n个应用的标识，分别记为：FQDN_1、FQDN_2、…、FQDN_n。DNS服务器的数量为至少两个。表3-1中示出了三个DNS服务器的地址，分别记为：IP@1、IP@2和IP@3。在表3-1中，位于同一行的应用与DNS服务器之间存在对应关系。如表3-1所示，“FQDN_1”所标识的应用与地址为“IP@1”的DNS服务器之间存在对应关系，“FQDN_1”所标识的应用与地址为“IP@2”的DNS服务器之间存在对应关系，“FQDN_2”所标识的应用与地址为“IP@1”的DNS服务器之间存在对应关系，“FQDN_3”所标识的应用与地址为“IP@3”的DNS服务器之间存在对应关系，“FQDN_n”所标识的应用与地址为“IP@2”的DNS服务器之间存在对应关系。其中，终端装置可以预配置“应用与DNS服务器之间的对应关系”这一信息，也可以由SMF网元、PCF网元或其他网元发送“应用与DNS服务器之间的对应关系”这一信息给终端装置。例如，SMF网元或PCF网元在PDU会话的用户面路径中插入BP设备的过程中，为终端装置发送使用者路由选取策略(user routing selection policy，URSP)时携带上述“应用与DNS服务器之间的对应关系”信息。
这里，“终端装置确定第一应用对应的第一DNS服务器的地址”的方式有多种，可以例如但不限于图4所示的处理过程：
S3021、SMF网元向终端装置发送第一应用的标识和与第一应用的标识对应的DNS服务器的地址。相应的，终端装置接收来自SMF网元的第一应用的标识和与第一应用的标识对应的DNS服务器的地址。
示例性的，“第一应用的标识和与第一应用的标识对应的DNS服务器的地址”可以表格的形式呈现，也可以其他形式呈现，本申请实施例对此不作限定。以表3-1为例，第一应用可以是表3-1中的n个应用中的一个应用。
S3022、终端装置根据第一应用的标识和与第一应用的标识对应的DNS服务器的地址，确定第一DNS服务器的地址。
这里，若第一应用的标识对应一个DNS服务器的地址，则该DNS服务器的地址即为第一DNS服务器的地址。示例性的，仍以表3-1示出的“不同应用与不同DNS服务器之间的对应关系”为例，第一应用的标识为“FQDN_3”。在表3-1中，“FQDN_3”所标识的应用仅与地址为“IP@3”的DNS服务器之间存在对应关系，也就是说，仅地址为“IP@3”的DNS服务器能够与部署有“第一应用”的应用服务器通信，如此，第一DNS服务器的地址即为“IP@3”。
若第一应用的标识对应两个或两个以上的DNS服务器的地址，则终端装置基于一定的预设策略，从多个DNS服务器中确定一个DNS服务器，作为第一DNS服务器。示例性的，终端装置从多个DNS服务器中确定满足预设策略的第一DNS服务器。其中，预设策略包括以下至少一项：
第一项：第一DNS服务器的优先级在多个DNS服务器的优先级中满足优先级条件。例如，第一DNS服务器的优先级在多个DNS服务器的优先级中的等级最高。
第二项：第一DNS服务器与终端装置之间的距离满足间隔距离条件。例如，第一DNS服务器与终端装置之间的距离小于或等于距离阈值，或者，在上述多个DNS服务器分别与终端装置之间的距离中，第一DNS服务器与终端装置之间的距离最小。
示例性的，仍以表3-1示出的“不同应用与不同DNS服务器之间的对应关系”为例，第一应用的标识为“FQDN_1”。在表3-1中，“FQDN_1”所标识的应用分别与地址为“IP@1” 的DNS服务器和“IP@2”的DNS服务器之间存在对应关系，也就是说，地址为“IP@1”的DNS服务器和地址为“IP@2”的DNS服务器能够解析“第一应用”对应的DNS请求信息。在预设策略实现为第二项的情况下，若地址为“IP@1”的DNS服务器与终端装置之间的距离满足间隔距离条件，则第一DNS服务器的地址即为“IP@1”。若地址为“IP@2”的DNS服务器与终端装置之间的距离满足间隔距离条件，则第一DNS服务器的地址即为“IP@2”。
示例性的，参见表3-2，在表3-2中，除了示出了“不同应用与不同DNS服务器之间的对应关系”之外，还示出了“不同DNS服务器的优先级”。
表3-2
应用的标识 DNS服务器的地址 优先级
FQDN_1 IP@1 3
FQDN_1 IP@2 2
FQDN_2 IP@1 3
FQDN_3 IP@3 4
… … …
FQDN_n IP@2 2
参见表3-2，在表3-2中，关于“不同应用与不同DNS服务器之间的对应关系”的相关说明可以参见表3-1的介绍，此处不再赘述。在表3-2中，地址为“IP@1”的DNS服务器的优先级为3，地址为“IP@2”的DNS服务器的优先级为2，地址为“IP@3”的DNS服务器的优先级为4。这里，在“优先级”这一列中，数字的取值越大，对应的优先级越高。或反之，数字的取值越大，对应的优先级越低，本申请实施例对此不作限定。
以表3-2示出的“不同应用与不同DNS服务器之间的对应关系”为例，第一应用的标识为“FQDN_1”。在表3-2中，“FQDN_1”所标识的应用分别与地址为“IP@1”的DNS服务器和“IP@2”的DNS服务器之间存在对应关系。在预设策略实现为第一项的情况下，若地址为“IP@1”的DNS服务器的优先级高于地址为“IP@2”的DNS服务器，则第一DNS服务器的地址即为“IP@1”。
需要说明的是，本申请实施例中仅以“优先级”和“距离”作为示例，对预设策略的具体实现进行示例性说明。在实际应用过程中，还可以根据实际应用需求设置其他的预设策略，本申请实施例对此不作限定。
如此，在SMF网元为终端装置提供“第一应用的标识和第一应用的标识对应的DNS服务器的地址”的情况下，终端装置能够依据SMF网元提供的信息，来确定第一应用对应的第一DNS服务器的地址。
S303、终端装置根据第一DNS服务器的地址和与第一DNS服务器的地址对应的终端装置的地址，确定终端装置的第一地址。
其中，关于“终端装置的地址”的说明如下：终端装置的地址可以有一个或多个。终端装置的地址可由SMF网元分配或由UPF(PSA)网元分配。终端装置的一个地址对应一个PSA网元，终端装置的不同地址对应不同PSA网元。终端装置的第一地址对应的PSA网元，记为第一PSA网元。
其中，关于“与第一DNS服务器的地址对应的终端装置的地址”的说明如下：由于PSA网元和DNS服务器之间存在对应关系，详见表2中的相关说明。并且，PSA网元与终端装置的地址之间也存在对应关系，详见表1中的相关说明。对于与同一“PSA网元”存在对应关系的终端装置的地址和DNS服务器而言，两者之间也就存在对应关系。示例性的， 参见表4，表4以“DNS服务器的地址”为例，示出了“DNS服务器与终端装置的地址之间存在的对应关系”。
表4
终端装置的地址 DNS服务器的地址
终端装置的地址@0 IP@0
终端装置的地址@1 IP@1
终端装置的地址@2 IP@2
… …
终端装置的地址@n IP@n
参见表4，表4示出了终端装置的(n+1)个地址，分别记为：终端装置的地址@0、终端装置的地址@1、…、终端装置的地址@n。DNS服务器的数量为(n+1)个，(n+1)个DNS服务器的地址分别记为：IP@0、IP@1、IP@2、…、IP@n。在表4中，位于同一行的终端装置的地址与DNS服务器之间存在对应关系。如表4所示，“终端装置的地址@0”与地址“IP@0”标识的DNS服务器之间存在对应关系，“终端装置的地址@1”与地址“IP@1”标识的DNS服务器之间存在对应关系，“终端装置的地址@2”与地址“IP@2”标识的DNS服务器之间存在对应关系，…，“终端装置的地址@n”与地址“IP@n”标识的DNS服务器之间存在对应关系。
示例性的，仍以表4示出的“DNS服务器与终端装置的地址之间存在的对应关系”为例，若第一DNS服务器的地址为“IP@1”，则终端装置的第一地址为“终端装置的地址@1”。若第一DNS服务器的地址为“IP@2”，则终端装置的第一地址为“终端装置的地址@2”。
其中，“第一DNS服务器的地址和与第一DNS服务器的地址对应的终端装置的地址”这一信息可以是终端装置预配置的信息，也可以是由SMF网元、PCF网元或其他网元为终端装置下发的信息，例如：
SMF网元向终端装置发送第一DNS服务器的地址和与第一DNS服务器的地址对应的终端装置的地址。相应的，终端装置接收来自SMF网元的第一DNS服务器的地址和与第一DNS服务器的地址对应的终端装置的地址。
示例性的，SMF网元在PDU会话的用户面路径中插入BP设备的过程中，SMF网元向终端装置发送第一DNS服务器的地址和与第一DNS服务器的地址对应的终端装置的地址。例如，在下发给终端装置的路径选择规则(routing rule)中携带上述信息。
S304、终端装置向BP设备发送DNS请求信息。相应的，BP设备接收来自终端装置的DNS请求信息。
其中，DNS请求信息包括第一应用的标识、第一DNS服务器的地址和终端装置的第一地址。这里，DNS请求信息的源地址为终端装置的第一地址，DNS请求信息的目的地址为第一DNS服务器的地址。
示例性的，第一应用的标识为“FQDN_1”，第一DNS服务器的地址为“IP@1”，终端装置的地址为“终端装置的地址@1”。此种情况下，DNS请求信息中的应用的标识为“FQDN_1”，DNS请求信息的源地址为“终端装置的地址@1”，DNS请求信息的目的地址为“IP@1”。
示例性的，参见图5，终端装置向BP设备发送DNS请求信息。相应的，BP设备接收来自终端装置的DNS请求信息。之后，BP设备根据DNS请求信息的源地址，确定源地址 对应的PSA网元，再向源地址对应的PSA网元发送DNS请求信息。相应的，源地址对应的PSA网元接收来自BP设备的DNS请求信息。这里，若源地址对应的PSA网元为“C-PSA”网元，则BP设备向C-PSA网元发送DNS请求信息。相应的，C-PSA网元接收来自BP设备的DNS请求信息。之后，C-PSA网元根据DNS请求信息中的目的地址向C-DNS服务器发送DNS请求信息。相应的，C-DNS服务器接收来自C-PSA网元的DNS请求信息，并对DNS请求信息进行解析，得到针对DNS请求信息的响应信息。其中，响应信息包括应用服务器的IP地址。响应信息再由C-DNS服务器、C-PSA网元和BP设备传输到终端装置，为终端装置提供应用服务器的IP地址，从而使得终端装置与应用服务器之间能够进行数据传输。若源地址对应的PSA网元为“L-PSA”网元，则BP设备向L-PSA网元发送DNS请求信息。相应的，L-PSA网元接收来自BP设备的DNS请求信息。之后，L-PSA网元根据DNS请求信息中的目的地址向L-DNS服务器发送DNS请求信息。相应的，L-DNS服务器接收来自L-PSA网元的DNS请求信息，并对DNS请求信息进行解析，得到DNS请求信息的响应信息。响应信息再从L-DNS服务器、L-PSA网元和BP设备传输到终端装置，为终端装置提供应用服务器的IP地址。
需要说明的是，在终端装置的位置发生变化的情况下，网络设备(如SMF网元或PCF网元等)为终端装置提供“不同应用与不同DNS服务器之间的对应关系”和“DNS服务器与终端装置的地址之间存在的对应关系”。
本申请实施例域名系统请求的发送方法，终端装置确定第一应用对应的第一DNS服务器的地址之后，还能够根据第一DNS服务器的地址和与第一DNS服务器的地址对应的终端装置的地址，确定终端装置的第一地址。由于第一DNS服务器的地址和终端装置的第一地址之间存在对应关系，且终端装置的第一地址对应一个PSA网元，也就是说，第一DNS服务器与终端装置的第一地址所对应的PSA网元之间能够通信。由于终端装置发出的DNS请求信息是包括上述第一DNS服务器的地址和终端装置的第一地址，如此，DNS请求信息能够通过终端装置对应的PSA网元传输至第一DNS服务器，从而提高了DNS解析的成功率，减少现有技术中“DNS服务器与PSA网元之间无法通信”所导致的“DNS解析失败”的现象。
本申请实施例提供第二种域名系统请求的发送方法，该域名系统请求的发送方法应用在域名解析过程中。参见图6，本申请实施例域名系统请求的发送方法包括如下步骤：
S601、终端装置创建PDU会话。
其中，S601的具体实现过程可以参见S301的相关说明，此处不再赘述。
S602、终端装置向BP设备发送DNS请求信息。相应的，BP设备接收来自终端装置的DNS请求信息。
其中，DNS请求信息包括第一应用的标识、源地址和目的地址。在S602中，对终端装置所选取的源地址和目的地址不作限定，具体实现过程可以参见现有技术，此处不再赘述。
S603、BP设备更新DNS请求信息中的源地址和目的地址中的至少一项，得到更新后的DNS请求信息。
其中，更新后的DNS请求信息中的源地址为终端装置的第一地址，更新后的DNS请求信息中的目的地址为第一DNS服务器的地址。这里，在更新后的DNS请求信息中，源 地址对应的PSA网元和第一DNS服务器之间有对应关系，能够通信，可以参见S303的相关说明，此处不再赘述，避免由于PSA网元与DNS服务器之间无法通信所导致的“DNS解析失败”的现象。
其中，“BP设备更新DNS请求信息中的源地址和目的地址中的至少一项，得到更新后的DNS请求信息”的方式有多种，下面，以三个示例进行说明：
示例一、BP设备根据DNS请求信息中第一应用的标识，更新DNS请求信息中的源地址和目的地址中的至少一项，得到更新后的DNS请求信息。
这里，更新DNS请求信息中的源地址和目的地址是根据第一应用的标识来确定的，第一DNS服务器对应的数据网络中部署了第一应用对应的应用服务器，所以，第一DNS服务器能够解析该DNS请求信息。确定第一DNS服务器后，即可确定第一DNS服务器对应的PSA网元，进而确定终端装置的第一地址，终端装置的第一地址对应的PSA网元与第一DNS服务器之间能够通信，以提高DNS请求信息解析效率。
示例性的，参见图7，为了得到更新后的DNS请求信息，BP设备执行如下步骤：
S6031、BP设备确定第一应用的标识对应的第一DNS服务器的地址。
示例性的，BP设备可以根据“不同应用与不同DNS服务器之间的对应关系”来确定第一应用对应的第一DNS服务器的地址。这里，关于“不同应用与不同DNS服务器之间的对应关系”的介绍可以参见S302的相关说明，此处不再赘述。S6031可以具体实现为如下步骤一和步骤二：
步骤一、SMF网元向BP设备发送第一应用的标识和与第一应用的标识对应的DNS服务器的地址。相应的，BP设备接收来自SMF网元的第一应用的标识和与第一应用的标识对应的DNS服务器的地址。
示例性的，“第一应用的标识和与第一应用的标识对应的DNS服务器的地址”可以以表格的形式呈现，也可以其他形式呈现，本申请实施例对此不作限定。以表3-1为例，第一应用可以是表3-1中的n个应用中的一个应用。
或者，步骤一也可以实现为：SMF网元向BP设备发送数据网络中部署的应用的标识。相应的，BP设备接收来自SMF网元的数据网络中部署的应用的标识。或者，步骤一也可以实现为：SMF网元向BP设备发送数据网络中部署的应用服务器的标识。相应的，BP设备接收来自SMF网元的数据网络中部署的应用服务器的标识。如前所述，数据网络与DNS服务器之间存在对应关系，则BP设备能够根据从SMF网元接收的信息，确定第一应用的标识和与第一应用的标识对应的DNS服务器的地址。
步骤二、BP设备根据第一应用的标识和与第一应用的标识对应的DNS服务器的地址，确定第一DNS服务器的地址。
这里，关于步骤二的介绍可以参见S3022的相关说明。也就是说，由BP设备替代S3022中的终端装置，具体方法流程相同，此处不再赘述。
在BP设备确定第一DNS服务器的地址之后，若DNS请求信息中的目的地址与第一DNS服务器的地址一致，则BP设备无需执行S6032。若DNS请求信息中的目的地址与第一DNS服务器的地址不一致，则BP设备执行S6032：
S6032、BP设备将DNS请求信息中的目的地址更新为第一DNS服务器的地址。
示例性的，若第一DNS服务器的地址为“IP@2”，DNS请求信息中的目的地址为“IP@3”， 则BP设备将DNS请求信息中的目的地址替换为“IP@2”。
S6033、BP设备根据第一DNS服务器的地址和与第一DNS服务器的地址对应的终端装置的地址，确定终端装置的第一地址。
这里，关于S6033的介绍可以参见S303的相关说明。也就是说，由BP设备替代S303中的终端装置，具体方法流程相同，此处不再赘述。
在BP设备确定终端装置的第一地址之后，若DNS请求信息中的源地址与终端装置的第一地址一致，则BP设备无需执行S6034。若DNS请求信息中的源地址与终端装置的第一地址不一致，则BP设备执行S6034：
S6034、BP设备将DNS请求信息中的源地址为终端装置的第一地址。
示例性的，若终端装置的第一地址为“终端装置的地址@2”，DNS请求信息中的源地址为“终端装置的地址@3”，则BP设备将DNS请求信息中的源地址替换为“终端装置的地址@2”。
如此，BP设备以DNS请求信息中的应用的标识为准，来更新DNS请求信息中的源地址和目的地址，以得到更新后的DNS请求信息。
示例二、BP设备根据DNS请求信息中的源地址，更新DNS请求信息中的目的地址。
示例性的，仍以表4示出的“DNS服务器与终端装置的地址之间存在的对应关系”为例，在DNS请求信息中的源地址是“终端装置的地址@1”，且DNS请求信息中的目的地址不是“IP@1”的情况下，BP设备将DNS请求信息中的目的地址更新为“IP@1”。在DNS请求信息中的源地址是“终端装置的地址@2”，且DNS请求信息中的目的地址不是“IP@2”的情况下，BP设备将DNS请求信息中的目的地址更新为“IP@2”。
这里，BP设备以DNS请求信息中的源地址为准，来更新DNS请求信息中的目的地址，以得到更新后的DNS请求信息。
在示例二中，作为一种可能的实现方式，BP设备执行如下步骤三和步骤四：
步骤三、若DNS请求信息中的源地址为终端装置的第一地址，则BP设备根据终端装置的第一地址和与终端装置的第一地址对应的DNS服务器的地址，确定第一DNS服务器的地址。
示例性的，仍以表4示出的“DNS服务器与终端装置的地址之间存在的对应关系”为例，在DNS请求信息中的源地址是“终端装置的地址@1”的情况下，结合表4，BP设备确定第一DNS服务器的地址为“IP@1”。在DNS请求信息中的源地址是“终端装置的地址@2”的情况下，BP设备确定第一DNS服务器的地址为“IP@2”。
这里，“终端装置的第一地址和与终端装置的第一地址对应的DNS服务器的地址”这一信息可以是BP设备预配置的信息，也可以是SMF网元为BP设备下发的信息，即：SMF网元向BP设备发送终端装置的第一地址和与终端装置的第一地址对应的DNS服务器的地址。相应的，BP设备接收来自SMF网元的终端装置的第一地址和与终端装置的第一地址对应的DNS服务器的地址。
步骤四、BP设备将DNS请求信息中的目的地址更新为第一DNS服务器的地址。
示例性的，在DNS请求信息中的源地址是“终端装置的地址@1”，且DNS请求信息中的目的地址不是“IP@1”的情况下，BP设备将DNS请求信息中的目的地址更新为“IP@1”。在DNS请求信息中的源地址是“终端装置的地址@2”，且DNS请求信息中的目的地址不是 “IP@2”的情况下，BP设备将DNS请求信息中的目的地址更新为“IP@2”。
如此，BP设备在确定DNS请求信息中的源地址为终端装置的第一地址的情况下，以DNS请求信息中的源地址为准，来更新DNS请求信息中的目的地址，以得到更新后的DNS请求信息。
示例三、BP设备根据DNS请求信息中的目的地址，更新DNS请求信息中的源地址。
示例性的，仍以表4示出的“DNS服务器与终端装置的地址之间存在的对应关系”为例，在DNS请求信息中的目的地址是“IP@1”，且DNS请求信息中的源地址不是“终端装置的地址@1”的情况下，BP设备将DNS请求信息中的源地址更新为“终端装置的地址@1”。在DNS请求信息中的目的地址是“IP@2”，且DNS请求信息中的源地址不是“终端装置的地址@2”的情况下，BP设备将DNS请求信息中的源地址更新为“终端装置的地址@2”。
这里，BP设备以DNS请求信息中的目的地址为准，来更新DNS请求信息中的源地址，以得到更新后的DNS请求信息。
在示例三中，作为一种可能的实现方式，BP设备执行如下步骤五和步骤六：
步骤五、若DNS请求信息中的目的地址为第一DNS服务器的地址，则BP设备根据第一DNS服务器的地址和与第一DNS服务器的地址对应的终端装置的地址，确定终端装置的第一地址。
示例性的，仍以表4示出的“DNS服务器与终端装置的地址之间存在的对应关系”为例，在DNS请求信息中的目的地址为“IP@1”的情况下，结合表4，BP设备确定终端装置的第一地址为“终端装置的地址@1”。在DNS请求信息中的目的地址为“IP@2”的情况下，结合表4，BP设备确定终端装置的第一地址为“终端装置的地址@2”。
这里，“第一DNS服务器的地址和与第一DNS服务器的地址对应的终端装置的地址”这一信息可以是BP设备预配置的信息，也可以是SMF网元为BP设备下发的信息，即：SMF网元向BP设备发送第一DNS服务器的地址和与第一DNS服务器的地址对应的终端装置的地址。相应的，BP设备接收来自SMF网元的终端装置的第一DNS服务器的地址和与第一DNS服务器的地址对应的终端装置的地址。
步骤六、BP设备将DNS请求信息中的源地址更新为终端装置的第一地址。
示例性的，在DNS请求信息中的目的地址是“IP@1”，且DNS请求信息中的源地址不是“终端装置的地址@1”的情况下，BP设备将DNS请求信息中的源地址更新为“终端装置的地址@1”。在DNS请求信息中的目的地址是“IP@2”，且DNS请求信息中的源地址不是“终端装置的地址@2”的情况下，BP设备将DNS请求信息中的源地址更新为“终端装置的地址@2”。
如此，BP设备在确定DNS请求信息中的目的地址为第一DNS服务器的地址的情况下，以DNS请求信息中的目的地址为准，来更新DNS请求信息中的源地址，以得到更新后的DNS请求信息。
需要说明的是，在上述示例一中，BP设备的更新规则为“以DNS请求信息中的第一应用的标识为基准，来更新DNS请求信息中的源地址和目的地址中的至少一项”。在上述示例二中，BP设备的更新规则为“以DNS请求信息中的源地址为基准，来更新DNS请求信息中的目的地址”。在上述示例三中，BP设备的更新规则为“以DNS请求信息中的目的地址为基准，来更新DNS请求信息中的源地址”。上述三个示例中任一示例的更新规则可以 是预先配置在BP设备上的，也可以是SMF网元为BP设备配置的。上述三个示例中任一示例的更新规则可以是以终端装置为粒度进行配置，即针对同一终端装置发送的不同DNS请求信息的更新规则相同，针对不同终端装置的DNS请求信息的更新规则可以相同，也可以不同。此种情况下，若N个终端装置都由该BP设备服务时，BP设备需要配置N次更新规则。上述三个示例中任一示例的更新规则也可以是“BP设备”为粒度进行配置，即对于一个BP设备而言，BP设备采用同一更新规则来更新DNS请求信息中的源地址和/或目的地址。此种情况下，若N个终端装置都由该BP设备服务时，BP设备需要配置1次更新规则。
S604、BP设备根据更新后的DNS请求信息中的源地址，向第一PSA网元发送更新后的DNS请求信息。相应的，第一PSA网元接收来自BP设备的更新后的DNS请求信息。
其中，第一PSA网元是与终端装置的第一地址对应的PSA网元。
示例性的，BP设备根据更新后的DNS请求信息中的源地址，确定第一PSA网元，之后，BP设备再向第一PSA网元发送更新后的DNS请求信息，具体实现过程可以参见现有技术，此处不再赘述。
S605、第一PSA网元根据更新后的DNS请求信息中的目的地址，向第一DNS服务器发送更新后的DNS请求信息。相应的，第一DNS服务器接收来自第一PSA网元的更新后的DNS请求信息。
其中，第一DNS服务器与第一PSA网元存在对应关系。
S606、第一DNS服务器解析更新后的DNS请求信息，得到响应信息。
其中，DNS请求信息包括第一应用的标识。相应的，响应信息包括第一应用对应的应用服务器的IP地址。响应信息的源地址为更新后的DNS请求信息的目的地址，响应信息的目的地址为更新后的DNS请求信息的源地址，S606的具体实现过程可以参见现有技术，此处不再赘述。
S607、第一DNS服务器向第一PSA网元发送响应信息。相应的，第一PSA网元接收来自第一DNS服务器的响应信息。
示例性的，响应信息的目的地址为更新后的DNS请求信息的源地址，即终端装置的第一地址。第一DNS服务器根据响应信息的目的地址，向第一PSA网元发送响应信息，具体实现过程可以参见现有技术，此处不再赘述。
S608、第一PSA网元向BP设备发送响应信息。相应的，BP设备接收来自第一PSA网元的响应信息。
这里，响应信息的源地址为更新后的DNS请求信息的目的地址，响应信息的目的地址为更新后的DNS请求信息的源地址。
S609、BP设备更新响应信息中的源地址和目的地址中的至少一项，得到更新后的响应信息。
其中，更新后的响应信息中的源地址为更新前的DNS请求信息的目的地址，更新后的响应信息中的目的地址为更新前的DNS请求信息的源地址。
示例性的，若在S603中，BP设备将DNS请求信息中的源地址由“终端装置的地址@3”替换为“终端装置的地址@2”，则在S609中，BP设备将响应信息中的目的地址由“终端装置的地址@2”替换为“终端装置的地址@3”。若在S603中，BP设备将DNS请求信息中的 目的地址由“IP@1”替换为“IP@2”，则在S609中，BP设备将响应信息中的源地址由“IP@2”替换为“IP@1”。
S610、BP设备向终端装置发送更新后的响应信息。相应的，终端装置接收来自BP设备的更新后的响应信息。
这里，更新后的响应信息包括第一应用对应的应用服务器的IP地址、更新前的DNS请求信息的目的地址和更新前的DNS请求信息的源地址。终端装置执行S602发送DNS请求信息之后，监听携带更新前的DNS请求信息的源地址和目的地址的响应消息。BP设备能够替换响应信息中的源地址和目的地址中的至少一项，以保证终端装置能够监听到携带更新前的DNS请求信息的源地址和目的地址的响应消息。
本申请实施例域名系统请求的发送方法，BP设备接收来自终端装置的DNS请求信息之后，能够更新DNS请求信息中的源地址和目的地址中的至少一项，得到更新后的DNS请求信息，再发送更新后的DNS请求信息。由于更新后的DNS请求信息中的源地址为终端装置的第一地址，更新后的DNS请求信息中的目的地址为第一DNS服务器的地址。终端装置的第一地址对应的第一PSA网元与第一DNS服务器之间能够通信，如此，更新后的DNS请求信息能够通过第一PSA网元传输至第一DNS服务器，从而提高了DNS解析的成功率，减少现有技术中“DNS服务器与PSA网元之间无法通信”所导致的“DNS解析失败”的现象。
本申请实施例提供第三种域名系统请求的发送方法，该域名系统请求的发送方法应用在域名解析过程中。参见图8，本申请实施例域名系统请求的发送方法包括如下步骤：
S801、终端装置创建PDU会话。
其中，S801的具体实现过程可以参见S301的相关说明，此处不再赘述。如表1所示，终端装置被分配了多个地址。其中，多个地址中的一个地址与一个PSA网元对应，多个地址中的不同地址与不同PSA网元对应。
需要说明的是，在PDU会话的用户面路径中插入BP设备和L-PSA网元的过程中，SMF网元分别下发转发规则信息给C-PSA网元和L-PSA网元，以指示C-PSA网元和L-PSA网元在收到特定目的地址的数据包时将数据包发送至BP设备。具体地，下发给C-PSA网元的转发规则信息，用于指示C-PSA网元在收到目的地址为“终端装置的地址@1”、“终端装置的地址@2”，…，“终端装置的地址@n”的数据包时，将数据包发送给BP设备。若终端装置分配了N个地址，对应的，下发给C-PSA网元的转发规则信息中的目的地址的数量为(N-1)个。当然，多个目的地址可以合并在一条转发规则信息中，也可以承载于不同转发规则信息中，传输给C-PSA网元，本申请实施例对此不作限定。类似地，在给L-PSA网元中的一个网元发送转发规则信息时，以L-PSA_1网元为例，进行说明：下发给L-PSA_1网元的转发规则信息，用于指示L-PSA_1网元在收到目的地址为“终端装置的地址@1”、“终端装置的地址@2”，…，“终端装置的地址@n”的数据包时，将数据包发送给BP设备。若终端装置分配了N个地址，对应的，下发给L-PSA_1网元的转发规则信息中的目的地址的数量为(N-1)个。当然，多个目的地址可以合并在一条转发规则信息中，也可以承载于不同转发规则信息中，传输给L-PSA_1网元，本申请实施例对此不作限定。对于给L-PSA网元中的其他网元发送转发规则信息时，可以参见上述说明，此次不再赘述。
S802、终端装置向BP设备发送DNS请求信息。相应的，BP设备接收来自终端装置 的DNS请求信息。
其中，DNS请求信息包括第一应用的标识、源地址和目的地址。其中，DNS请求信息的源地址为终端装置的第二地址，与第二PSA网元对应。DNS请求信息的目的地址为第一DNS服务器的地址，与第一PSA网元对应。
示例性的，以表1示出的“终端装置的地址与PSA网元之间的对应关系”和表2示出的“PSA网元与DNS服务器之间的对应关系”为例，若DNS请求信息的源地址为“终端装置的地址@0”，DNS请求信息的目的地址为“IP@1”。此种情况下，第一DNS服务器为“L-DNS_1”服务器，第二PSA网元即为“C-PSA”网元。若DNS请求信息的源地址为“终端装置的地址@1”，DNS请求信息的目的地址为“IP@0”。此种情况下，第一DNS服务器为“C-DNS”服务器，第二PSA网元即为“L-PSA_1”网元。
S803、BP设备根据DNS请求信息中的目的地址，向目的地址对应的第一PSA网元发送DNS请求信息。相应的，第一PSA网元接收来自BP设备的DNS请求信息。
示例性的，以表2示出的“PSA网元与DNS服务器之间的对应关系”为例，若DNS请求信息的目的地址为“IP@0”，则第一PSA网元为“C-PSA”网元。BP设备向“C-PSA”网元发送DNS请求信息。若DNS请求信息的目的地址为“IP@1”，则第一PSA网元为“L-PSA_1”网元。BP设备向“L-PSA_1”网元发送DNS请求信息。
S804、第一PSA网元向第一DNS服务器发送DNS请求信息。相应的，第一DNS服务器接收来自第一PSA网元的DNS请求信息。
示例性的，第一PSA网元根据DNS请求信息中的目的地址，向第一DNS服务器发送DNS请求信息。若第一PS A网元为“C-PSA”网元，则第一DNS服务器为“C-DNS”服务器。“C-PSA”网元向“C-DNS”服务器发送DNS请求信息。若第一PSA网元为“L-PSA_1”网元，则第一服务器为“L-DNS”服务器。“L-PSA”网元向“L-DNS”服务器发送DNS请求信息。S804的具体实现过程可以参见现有技术，此处不再赘述。
S805、第一DNS服务器解析DNS请求信息，得到响应信息。
其中，DNS请求信息包括第一应用的标识。相应的，响应信息包括第一应用对应的应用服务器的IP地址。响应信息的源地址为DNS请求信息的目的地址，响应信息的目的地址为DNS请求信息的源地址，S805的具体实现过程可以参见现有技术，此处不再赘述。
S806、第一DNS服务器向第一PSA网元发送响应信息。相应的，第一PSA网元接收来自第一DNS服务器的响应信息。
其中，响应信息的源地址为第一DNS服务器的地址，响应信息的目的地址为终端装置的第二地址。终端装置的第二地址与第二PSA网元对应。这里，S806可以具体实现为如下过程：
第一PSA网元通过第一PSA网元和第一DNS服务器之间的隧道接收来自第一DNS服务器的针对DNS请求信息的响应信息。
其中，第一PSA网元与第一DNS服务器之间建立隧道。在响应信息的目的地址是终端装置的第二地址，响应信息的源地址是第一DNS服务器的地址的情况下，由于终端装置的第二地址与第二PSA网元对应，响应信息可以通过第一PSA网元与第一DNS服务器之间的隧道传输。
示例性的，响应信息的目的地址为“终端装置的地址@0”，响应信息的源地址为“IP@1”。 此种情况下，第一DNS服务器为“L-DNS_1”服务器，第一PSA网元即为“L-PSA_1”网元。由于响应信息能够通过隧道从第一DNS服务器向第一PSA网元传输。所以，响应信息除了携带源地址和目的地址之外，响应信息还需封装第一PSA网元与第一DNS服务器之间隧道的地址，以屏蔽响应信息中的目的地址，使得响应信息能够从第一DNS服务器传输至第一PSA网元。
S807、第一PSA网元根据转发规则信息，向BP设备发送响应信息。相应的，BP设备接收来自第一PSA网元的响应信息。
其中，转发规则信息的相关说明可以参见S801的介绍，此处不再赘述。第一PSA网元基于转发规则信息发送响应信息至BP设备。这里，转发规则信息指示第一PSA网元将目的地址为第二地址的数据包发送至BP设备。数据包包括上述响应信息。
其中，转发规则信息可以是预配置的信息，也可以是SMF网元为第一PSA配置的信息。即，SMF网元向第一PSA网元发送转发规则信息。相应的，第一PSA网元接收来自SMF网元的转发规则信息。
S808、BP设备向终端装置发送响应信息。相应的，终端装置接收来自BP设备的响应信息。
这里，响应信息包括第一应用对应的应用服务器的IP地址、DNS请求信息的目的地址和DNS请求信息的源地址。
本申请实施例域名系统请求的发送方法，BP设备接收来自终端装置的DNS请求信息之后，根据DNS请求信息中的目的地址，向目的地址对应的第一PSA网元发送DNS请求信息。由于DNS请求信息的目的地址与第一PSA网元对应，DNS请求信息的目的地址为第一DNS服务器的地址，第一DNS服务器与第一PSA网元之间能够通信，也就能够减少现有技术中“DNS服务器与PSA网元之间无法通信”所导致的“DNS解析失败”的现象，提高DNS解析的成功率。在第一DNS服务器反馈响应信息的过程中，第一PSA网元接收来自第一DNS服务器的响应信息之后，即使响应信息的目的地址是终端装置的第二地址，与第二PSA网元对应，第一PSA网元也能够根据转发规则信息，向BP设备发送响应信息，使得响应信息能够通过BP设备提供给终端装置。
上述主要从各个网元之间交互的角度对本申请实施例提供的方案进行了介绍。相应的，本申请实施例还提供了域名系统请求的发送装置，该域名系统请求的发送装置可以为上述方法实施例中的网元，或者包含上述网元的装置，或者为可用于网元的部件。可以理解的是，该域名系统请求的发送装置为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
图9示出了一种域名系统请求的发送装置900的结构示意图。该域名系统请求的发送装置900包括收发模块901和处理模块902。
比如，以域名系统请求的发送装置900为上述方法实施例中图3的终端装置为例，
处理模块902用于确定第一应用对应的第一域名系统DNS服务器的地址。处理模块 902还用于根据第一DNS服务器的地址和与第一DNS服务器的地址对应的终端装置的地址，确定终端装置的第一地址。收发模块901用于发送DNS请求信息。其中，DNS请求信息包括第一应用的标识、第一DNS服务器的地址和终端装置的第一地址。
在一种可能的设计中，收发模块901还用于接收来自会话管理功能SMF网元的第一DNS服务器的地址和与第一DNS服务器的地址对应的终端装置的地址。
在一种可能的设计中，收发模块901用于接收来自SMF网元的第一应用的标识和与第一应用的标识对应的DNS服务器的地址。处理模块902用于根据第一应用的标识和与第一应用的标识对应的DNS服务器的地址，确定第一DNS服务器的地址。
在一种可能的设计中，第一应用的标识对应多个DNS服务器。处理模块902具体用于：从多个DNS服务器中确定满足预设策略的第一DNS服务器。其中，预设策略包括以下至少一项：第一DNS服务器的优先级在多个DNS服务器的优先级中满足优先级条件；第一DNS服务器与终端装置之间的距离满足间隔距离条件。
比如，以域名系统请求的发送装置900为上述方法实施例中图6的BP设备为例，
收发模块901用于接收来自终端装置的域名系统DNS请求信息。处理模块902用于更新DNS请求信息中的源地址和目的地址中的至少一项，得到更新后的DNS请求信息。其中，更新后的DNS请求信息中的源地址为终端装置的第一地址，更新后的DNS请求信息中的目的地址为第一DNS服务器的地址。收发模块901还用于根据更新后的DNS请求信息中的源地址，向第一分组数据单元会话锚点PSA网元发送更新后的DNS请求信息。其中，第一PSA网元与终端装置的第一地址对应，更新后的DNS请求信息中的目的地址使能更新后的DNS请求信息由第一PSA网元发送给所述第一DNS服务器。
在一种可能的设计中，处理模块902具体用于：根据DNS请求信息中第一应用的标识，更新DNS请求信息中的源地址和目的地址中的至少一项，或者，根据DNS请求信息中的源地址，更新DNS请求信息中的目的地址，或者，根据DNS请求信息中的目的地址，更新DNS请求信息中的源地址。
在一种可能的设计中，处理模块902具体用于：确定第一应用的标识对应的第一DNS服务器的地址；将DNS请求信息中的目的地址更新为第一DNS服务器的地址；根据第一DNS服务器的地址和与第一DNS服务器的地址对应的终端装置的地址，确定终端装置的第一地址；将DNS请求信息中的源地址为终端装置的第一地址。
在一种可能的设计中，收发模块901用于接收来自会话管理功能SMF网元的第一应用的标识和与第一应用的标识对应的DNS服务器的地址。处理模块902用于根据第一应用的标识和与第一应用的标识对应的DNS服务器的地址，确定第一DNS服务器的地址。
在一种可能的设计中，处理模块902具体用于：若DNS请求信息中的目的地址为第一DNS服务器的地址，则根据第一DNS服务器的地址和与第一DNS服务器的地址对应的终端装置的地址，确定终端装置的第一地址，将DNS请求信息中的源地址更新为终端装置的第一地址。
在一种可能的设计中，收发模块901还用于接收来自SMF网元的第一DNS服务器的地址和与第一DNS服务器的地址对应的终端装置的地址。
在一种可能的设计中，处理模块902具体用于：若DNS请求信息中的源地址为终端装置的第一地址，则根据终端装置的第一地址和与终端装置的第一地址对应的DNS服务 器的地址，确定第一DNS服务器的地址，将DNS请求信息中的目的地址更新为第一DNS服务器的地址。
在一种可能的设计中，收发模块901还用于接收来自SMF网元的终端装置的第一地址和与终端装置的第一地址对应的DNS服务器的地址。
在一种可能的设计中，收发模块901还用于接收来自第一PSA网元的针对DNS请求信息的响应信息。处理模块902用于更新响应信息中的源地址和目的地址中的至少一项，得到更新后的响应信息。其中，更新后的响应信息中的源地址为更新前的DNS请求信息的目的地址，更新后的响应信息中的目的地址为更新前的DNS请求信息的源地址。收发模块901还用于向终端装置发送更新后的响应信息。
比如，以域名系统请求的发送装置900为上述方法实施例中图8由BP设备执行为例，
收发模块901用于接收来自终端装置的域名系统DNS请求信息。收发模块901还用于根据DNS请求信息中的目的地址，向目的地址对应的第一分组数据单元会话锚点PSA网元发送所述DNS请求信息，使能DNS请求信息由第一PSA网元发送给第一DNS服务器。
比如，以域名系统请求的发送装置900为上述方法实施例中图8由第一PSA网元执行为例，
收发模块901用于向第一域名系统DNS服务器发送DNS请求信息。其中，DNS请求信息包括第一DNS服务器的地址和对应第二PSA网元的终端装置的第二地址。收发模块901还用于接收来自第一DNS服务器的针对DNS请求信息的响应信息。处理模块902用于根据转发规则信息，使收发模块901向分支点BP设备发送响应信息。其中，转发规则信息用于指示第一PSA网元将目的地址为第二地址的数据包发送至BP设备；数据包包括响应信息。
在一种可能的设计中，收发模块901用于接收来自会话管理功能SMF网元的转发规则信息。
在一种可能的设计中，收发模块901用于通过第一PSA网元和第一DNS服务器之间的隧道接收来自第一DNS服务器的针对DNS请求信息的响应信息。
其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
应理解，本申请实施例中的处理模块902可以由处理器或处理器相关电路组件实现，收发模块901可以由收发器或收发器相关电路组件实现。
可选的，域名系统请求的发送装置900还可以包括存储模块903，用于存储装置900的程序代码和数据，数据可以包括不限于原始数据或者中间数据等。
一种可能的方式中，处理模块902可以是处理器或控制器，例如可以是中央处理器(central processing unit，CPU)，通用处理器，数字信号处理(digital signal processing，DSP)，应用专用集成电路(application specific integrated circuit，ASIC)，现场可编程门阵列(field－programmable gate array，FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框，模块和电路。处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，DSP和微处理器的组合等等。收发模块901可以是收发器、收发电路或通信接口等。 存储模块903可以是存储器。
一种可能的方式中，当处理模块902为处理器，收发模块901为通信接口，存储模块903为存储器时，本申请实施例所涉及的域名系统请求的发送装置的结构可以为图10所示。
图10示出了本申请实施例中所涉及的域名系统请求的发送装置的一种可能的设计结构的简化示意图。域名系统请求的发送装置1000包括：处理器1002、通信接口1003、存储器1001。可选的，域名系统请求的发送装置1000还可以包括总线1004。其中，通信接口1003、处理器1002以及存储器1001可以通过总线1004相互连接。总线1004可以是外设部件互连标准(peripheral component interconnect，PCI)总线或扩展工业标准结构(extended industry standard architecture，EISA)总线等。总线1004可以分为地址总线、数据总线、控制总线等。为便于表示，图10中仅用一条线表示，但并不表示仅有一根总线或一种类型的总线。
本领域普通技术人员可以理解：在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时，全部或部分地产生按照本申请实施例的流程或功能。计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包括一个或多个可用介质集成的服务器、数据中心等数据存储设备。可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，数字视频光盘(digital video disc，DVD))、或者半导体介质(例如固态硬盘(solid state disk，SSD))等。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统，装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，模块的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个模块或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或模块的间接耦合或通信连接，可以是电性或其它的形式。
作为分离部件说明的模块可以是或者也可以不是物理上分开的，作为模块显示的部件可以是或者也可以不是物理模块，即可以位于一个地方，或者也可以分布到多个网络设备(例如终端装置)上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能模块可以集成在一个处理模块中，也可以是各个功能模块独立存在，也可以两个或两个以上模块集成在一个模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用硬件加软件功能模块的形式实现。
通过以上的实施方式的描述，所属领域的技术人员可以清楚地了解到本申请可借助软件加必需的通用硬件的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实 施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在可读取的存储介质中，如计算机的软盘，硬盘或光盘等，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述的方法。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，在本申请揭露的技术范围内的变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (33)

  1. 一种域名系统DNS请求的发送方法，其特征在于，包括：
    终端装置确定第一应用对应的第一DNS服务器的地址；
    所述终端装置根据所述第一DNS服务器的地址和与所述第一DNS服务器的地址对应的所述终端装置的地址，确定所述终端装置的第一地址；
    所述终端装置发送DNS请求信息，所述DNS请求信息包括所述第一应用的标识、所述第一DNS服务器的地址和所述终端装置的第一地址。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    所述终端装置接收来自会话管理功能SMF网元的所述第一DNS服务器的地址和与所述第一DNS服务器的地址对应的所述终端装置的地址。
  3. 根据权利要求1或2所述的方法，其特征在于，所述终端装置确定第一应用对应的第一DNS服务器的地址，包括：
    所述终端装置接收来自SMF网元的所述第一应用的标识和与所述第一应用的标识对应的DNS服务器的地址；
    所述终端装置根据所述第一应用的标识和与所述第一应用的标识对应的DNS服务器的地址，确定所述第一DNS服务器的地址。
  4. 根据权利要求3所述的方法，其特征在于，所述第一应用的标识对应多个DNS服务器，所述终端装置根据所述第一应用的标识和与所述第一应用的标识对应的DNS服务器的地址，确定所述第一DNS服务器的地址，包括：
    所述终端装置从所述多个DNS服务器中确定满足预设策略的所述第一DNS服务器；
    其中，所述预设策略包括以下至少一项：
    所述第一DNS服务器的优先级在所述多个DNS服务器的优先级中满足优先级条件；
    所述第一DNS服务器与所述终端装置之间的距离满足间隔距离条件。
  5. 一种域名系统DNS请求的发送方法，其特征在于，包括：
    分支点BP设备接收来自终端装置的域名系统DNS请求信息；
    所述BP设备更新所述DNS请求信息中的源地址和目的地址中的至少一项，得到更新后的DNS请求信息，其中，所述更新后的DNS请求信息中的源地址为所述终端装置的第一地址，所述更新后的DNS请求信息中的目的地址为第一DNS服务器的地址；
    所述BP设备根据所述更新后的DNS请求信息中的源地址，向第一分组数据单元会话锚点PSA网元发送所述更新后的DNS请求信息；所述第一PSA网元与所述终端装置的第一地址对应；所述更新后的DNS请求信息中的目的地址使能所述更新后的DNS请求信息由所述第一PSA网元发送给所述第一DNS服务器。
  6. 根据权利要求5所述的方法，其特征在于，所述BP设备更新所述DNS请求信息中的源地址和目的地址中的至少一项，包括：
    所述BP设备根据所述DNS请求信息中第一应用的标识，更新所述DNS请求信息中的源地址和目的地址中的至少一项；
    或者，所述BP设备根据所述DNS请求信息中的源地址，更新所述DNS请求信息中的目的地址；
    或者，所述BP设备根据所述DNS请求信息中的目的地址，更新所述DNS请求信息 中的源地址。
  7. 根据权利要求6所述的方法，其特征在于，所述BP设备根据所述DNS请求信息中第一应用的标识，更新所述DNS请求信息中的源地址和目的地址中的至少一项，包括：
    所述BP设备确定所述第一应用的标识对应的所述第一DNS服务器的地址；
    所述BP设备将所述DNS请求信息中的目的地址更新为所述第一DNS服务器的地址；
    所述BP设备根据所述第一DNS服务器的地址和与所述第一DNS服务器的地址对应的所述终端装置的地址，确定所述终端装置的第一地址；
    所述BP设备将所述DNS请求信息中的源地址为所述终端装置的第一地址。
  8. 根据权利要求7所述的方法，其特征在于，所述BP设备确定所述第一应用的标识对应的所述第一DNS服务器的地址，包括：
    所述BP设备接收来自会话管理功能SMF网元的所述第一应用的标识和与所述第一应用的标识对应的DNS服务器的地址；
    所述BP设备根据所述第一应用的标识和与所述第一应用的标识对应的DNS服务器的地址，确定所述第一DNS服务器的地址。
  9. 根据权利要求6所述的方法，其特征在于，所述BP设备根据所述DNS请求信息中的目的地址，更新所述DNS请求信息中的源地址，包括：
    若所述DNS请求信息中的目的地址为所述第一DNS服务器的地址，则所述BP设备根据所述第一DNS服务器的地址和与所述第一DNS服务器的地址对应的所述终端装置的地址，确定所述终端装置的第一地址；
    所述BP设备将所述DNS请求信息中的源地址更新为所述终端装置的第一地址。
  10. 根据权利要求7至9任一项所述的方法，其特征在于，所述方法还包括：
    所述BP设备接收来自SMF网元的所述第一DNS服务器的地址和与所述第一DNS服务器的地址对应的所述终端装置的地址。
  11. 根据权利要求6所述的方法，其特征在于，所述BP设备根据所述DNS请求信息中的源地址，更新所述DNS请求信息中的目的地址，包括：
    若所述DNS请求信息中的源地址为所述终端装置的第一地址，则所述BP设备根据所述终端装置的第一地址和与所述终端装置的第一地址对应的DNS服务器的地址，确定所述第一DNS服务器的地址；
    所述BP设备将所述DNS请求信息中的目的地址更新为所述第一DNS服务器的地址。
  12. 根据权利要求11所述的方法，其特征在于，所述方法还包括：
    所述BP设备接收来自SMF网元的所述终端装置的第一地址和与所述终端装置的第一地址对应的DNS服务器的地址。
  13. 根据权利要求5至12任一项所述的方法，其特征在于，所述方法还包括：
    所述BP设备接收来自所述第一PSA网元的针对所述DNS请求信息的响应信息；
    所述BP设备更新所述响应信息中的源地址和目的地址中的至少一项，得到更新后的响应信息，其中，所述更新后的响应信息中的源地址为更新前的所述DNS请求信息的目的地址，所述更新后的响应信息中的目的地址为更新前的所述DNS请求信息的源地址；
    所述BP设备向所述终端装置发送所述更新后的响应信息。
  14. 根据权利要求13所述的方法，其特征在于，
    所述DNS请求信息包括第一应用的标识；
    所述响应信息包括所述第一应用对应的应用服务器的互联网协议IP地址。
  15. 一种域名系统DNS请求的发送方法，其特征在于，包括：
    分支点BP设备接收来自终端装置的域名系统DNS请求信息；
    所述BP设备根据所述DNS请求信息中的目的地址，向所述目的地址对应的第一分组数据单元会话锚点PSA网元发送所述DNS请求信息，使能所述DNS请求信息由所述第一PSA网元发送给第一DNS服务器。
  16. 一种域名系统DNS请求信息的发送方法，其特征在于，包括：
    第一分组数据单元会话锚点PSA网元向第一域名系统DNS服务器发送DNS请求信息，所述DNS请求信息包括所述第一DNS服务器的地址和对应第二PSA网元的终端装置的第二地址；
    所述第一PSA网元接收来自所述第一DNS服务器的针对所述DNS请求信息的响应信息；
    所述第一PSA网元根据转发规则信息，向分支点BP设备发送所述响应信息，其中，所述转发规则信息用于指示所述第一PSA网元将目的地址为所述第二地址的数据包发送至所述BP设备；所述数据包包括所述响应信息。
  17. 根据权利要求16所述的方法，其特征在于，所述方法还包括：
    所述第一PSA网元接收来自会话管理功能SMF网元的所述转发规则信息。
  18. 根据权利要求16或17所述的方法，其特征在于，所述第一PSA网元接收来自所述第一DNS服务器的针对所述DNS请求信息的响应信息，包括：
    所述第一PSA网元通过所述第一PSA网元和所述第一DNS服务器之间的隧道接收来自所述第一DNS服务器的针对所述DNS请求信息的响应信息。
  19. 根据权利要求16至18任一项所述的方法，其特征在于，
    所述DNS请求信息包括第一应用的标识；
    所述响应信息包括所述第一应用对应的应用服务器的互联网协议IP地址。
  20. 一种域名系统DNS请求的发送装置，其特征在于，包括：用于执行权利要求1至4任一项所述的各个步骤的单元。
  21. 一种域名系统DNS请求的发送装置，其特征在于，包括：处理器，用于调用存储器中的程序，以使得所述域名系统DNS请求的发送装置执行权利要求1至4任一项所述的域名系统DNS请求的发送方法。
  22. 一种域名系统DNS请求的发送装置，其特征在于，包括：处理器和接口电路，所述接口电路用于与其它装置通信，所述处理器用于执行权利要求1至4任一项所述的域名系统DNS请求的发送方法。
  23. 一种域名系统DNS请求的发送装置，其特征在于，包括：用于执行权利要求5至14任一项所述的各个步骤的单元。
  24. 一种域名系统DNS请求的发送装置，其特征在于，包括：处理器，用于调用存储器中的程序，以使得所述域名系统DNS请求的发送装置执行权利要求5至14任一项所述的域名系统DNS请求的发送方法。
  25. 一种域名系统DNS请求的发送装置，其特征在于，包括：处理器和接口电路，所 述接口电路用于与其它装置通信，所述处理器用于执行权利要求5至14任一项所述的域名系统DNS请求的发送方法。
  26. 一种域名系统DNS请求的发送装置，其特征在于，包括：用于执行权利要求15所述的各个步骤的单元。
  27. 一种域名系统DNS请求的发送装置，其特征在于，包括：处理器，用于调用存储器中的程序，以使得所述域名系统DNS请求的发送装置执行权利要求15所述的域名系统DNS请求的发送方法。
  28. 一种域名系统DNS请求的发送装置，其特征在于，包括：处理器和接口电路，所述接口电路用于与其它装置通信，所述处理器用于执行权利要求15所述的域名系统DNS请求的发送方法。
  29. 一种域名系统DNS请求的发送装置，其特征在于，包括：用于执行权利要求16至19任一项所述的各个步骤的单元。
  30. 一种域名系统DNS请求的发送装置，其特征在于，包括：处理器，用于调用存储器中的程序，以使得所述域名系统DNS请求的发送装置执行权利要求16至19任一项所述的域名系统DNS请求的发送方法。
  31. 一种域名系统DNS请求的发送装置，其特征在于，包括：处理器和接口电路，所述接口电路用于与其它装置通信，所述处理器用于执行权利要求16至19任一项所述的域名系统DNS请求的发送方法。
  32. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质存储程序，所述程序被处理器调用时，权利要求1至4任一项所述的域名系统DNS请求的发送方法被执行，或者权利要求5至14任一项所述的域名系统DNS请求的发送方法被执行，或者权利要求15所述的域名系统DNS请求的发送方法被执行，或者权利要求16至19任一项所述的域名系统DNS请求的发送方法被执行。
  33. 一种计算机程序，其特征在于，当所述程序被处理器调用时，权利要求1至4任一项所述的域名系统DNS请求的发送方法被执行，或者权利要求5至14任一项所述的域名系统DNS请求的发送方法被执行，或者权利要求15所述的域名系统DNS请求的发送方法被执行，或者权利要求16至19任一项所述的域名系统DNS请求的发送方法被执行。
PCT/CN2021/102830 2020-07-06 2021-06-28 一种域名系统请求的发送方法及装置 WO2022007657A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP21838923.7A EP4171086A4 (en) 2020-07-06 2021-06-28 METHOD AND APPARATUS FOR SENDING A DOMAIN NAME SYSTEM REQUEST
US18/150,591 US20230164111A1 (en) 2020-07-06 2023-01-05 Method and apparatus for sending domain name system request

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010642999.5A CN113973098A (zh) 2020-07-06 2020-07-06 一种域名系统请求的发送方法及装置
CN202010642999.5 2020-07-06

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/150,591 Continuation US20230164111A1 (en) 2020-07-06 2023-01-05 Method and apparatus for sending domain name system request

Publications (1)

Publication Number Publication Date
WO2022007657A1 true WO2022007657A1 (zh) 2022-01-13

Family

ID=79552736

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/102830 WO2022007657A1 (zh) 2020-07-06 2021-06-28 一种域名系统请求的发送方法及装置

Country Status (4)

Country Link
US (1) US20230164111A1 (zh)
EP (1) EP4171086A4 (zh)
CN (1) CN113973098A (zh)
WO (1) WO2022007657A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114221878A (zh) * 2022-02-21 2022-03-22 飞狐信息技术（天津）有限公司 一种故障节点检测方法、系统、电子设备及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102611763A (zh) * 2011-01-25 2012-07-25 中国移动通信集团公司 Dns查询的方法及设备
CN105391811A (zh) * 2014-08-29 2016-03-09 腾讯科技（深圳）有限公司 域名解析方法、应用服务器的访问方法及其终端
CN109640319A (zh) * 2019-01-16 2019-04-16 腾讯科技（深圳）有限公司 基于接入信息的调度方法、装置及电子设备
US20200120446A1 (en) * 2018-10-16 2020-04-16 Cisco Technology, Inc. Methods and apparatus for selecting network resources for ue sessions based on locations of multi-access edge computing (mec) resources and applications

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109788078B (zh) * 2017-11-13 2020-10-16 华为技术有限公司 应用服务器切换方法、设备及系统
US11218438B2 (en) * 2019-04-12 2022-01-04 Huawei Technologies Co., Ltd. System, apparatus and method to support data server selection

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102611763A (zh) * 2011-01-25 2012-07-25 中国移动通信集团公司 Dns查询的方法及设备
CN105391811A (zh) * 2014-08-29 2016-03-09 腾讯科技（深圳）有限公司 域名解析方法、应用服务器的访问方法及其终端
US20200120446A1 (en) * 2018-10-16 2020-04-16 Cisco Technology, Inc. Methods and apparatus for selecting network resources for ue sessions based on locations of multi-access edge computing (mec) resources and applications
CN109640319A (zh) * 2019-01-16 2019-04-16 腾讯科技（深圳）有限公司 基于接入信息的调度方法、装置及电子设备

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: "Solution for the KI#1: Discovery of edge application server based on DNS mechanism", 3GPP DRAFT; S2-1911170, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Reno, NV, USA; 20191118 - 20191122, 8 November 2019 (2019-11-08), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051821273 *
See also references of EP4171086A4

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114221878A (zh) * 2022-02-21 2022-03-22 飞狐信息技术（天津）有限公司 一种故障节点检测方法、系统、电子设备及存储介质

Also Published As

Publication number Publication date
US20230164111A1 (en) 2023-05-25
EP4171086A4 (en) 2023-12-20
EP4171086A1 (en) 2023-04-26
CN113973098A (zh) 2022-01-25

Similar Documents

Publication Publication Date Title
US11528770B2 (en) Session management method, apparatus, and system
CN112153098B (zh) 一种应用迁移方法及装置
CN109842906B (zh) 一种通信的方法、装置及系统
CN110365727B (zh) 通信方法和相关装置
WO2018232570A1 (zh) 一种注册及会话建立的方法、终端和amf实体
JP2020532243A (ja) データ伝送方法、デバイス、およびシステム
WO2019185062A1 (zh) 一种通信方法及装置
US20150117209A1 (en) Traffic distribution in heterogenous network environment
WO2019095837A1 (zh) 数据处理方法、装置及设备
JP7043631B2 (ja) Ｓｓｃモードを決定するための方法および装置
WO2020048469A1 (zh) 一种通信的方法及装置
US20200228618A1 (en) Content delivery method, device, and system
CN113812134A (zh) 边缘计算服务中用于管理ue的标识符的方法和设备
KR20200130043A (ko) 에지 컴퓨팅 서비스에서 단말의 식별자 관리 방법 및 장치
US11863519B2 (en) Communication method and apparatus for handling DNS messages
WO2019242525A1 (zh) 数据传输方法、相关装置及系统
CN110784434A (zh) 通信方法及装置
CN113473569B (zh) 应用服务器的发现方法及相关装置
CN112398959A (zh) Rlc信道确定方法和装置
US20240098583A1 (en) PDU session continuity for a UE moving between a telecommunications network and a gateway device
US8705471B2 (en) Method and system for implementing ID/locator mapping
WO2022007657A1 (zh) 一种域名系统请求的发送方法及装置
KR101481337B1 (ko) 소프트웨어 정의 네트워크 기반 이동통신 시스템 및 이의 단말 접속 처리 방법
CN113709905A (zh) 一种通信方法、装置及计算机可读存储介质
WO2017124231A1 (zh) 分配互联网协议地址的方法、控制面网关和用户面网关

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 2021838923

Country of ref document: EP

Effective date: 20230120

NENP Non-entry into the national phase

Ref country code: DE