WO2022042395A1

WO2022042395A1 - Method for determining service server address, and communication device

Info

Publication number: WO2022042395A1
Application number: PCT/CN2021/113268
Authority: WO
Inventors: 陈朔; 石帅
Original assignee: 华为技术有限公司
Priority date: 2020-08-31
Filing date: 2021-08-18
Publication date: 2022-03-03
Also published as: CN114124889A; CN114124889B

Abstract

The present application provides a method for determining a service server address, and a communication device. The method comprises: sending a first request to a DNS server by means of a first network, the first request being used for requesting a first IP address corresponding to a first domain name, and the first IP address being used for a terminal device to access a first service server by means of the first network; sending a second request sent to the DNS server by means of a second network, the second request being used for requesting a second IP address, and the second IP address being used for the terminal device to access the first service server by means of the second network; and receiving the first IP address and the second IP address sent by the DNS server. According to the method provided by the present application, by performing DNS queries respectively under different network paths, obtaining IP addresses of the service server respectively corresponding to the different network paths, and using the IP addresses respectively corresponding to different networks to interact with the service server on the different network paths, the access rate is ensured, and the service experience under multiple network scenarios is improved.

Description

Method and communication device for determining service server address

This application claims the priority of the Chinese patent application with the application number 202010900839.6 and the application title "Method and Communication Device for Determining Service Server Address" filed with the State Intellectual Property Office on August 31, 2020, the entire contents of which are incorporated by reference in in this application.

technical field

The present application relates to the field of communications, and more particularly, to a method and a communication device for determining an address of a service server.

Background technique

After Huawei launched LinkTurbo technology for the first time in the industry, various partners also released related similar technologies later, and dual-network online has become a standard capability of communication technology. LinkTurbo can be understood as wireless local area networks (WLAN) and data services are online at the same time, using WLAN (such as wireless-fidelity, WiFi) and LTE/5G to improve network performance, for example, in dual WiFi paths ( 2.4GHz band WiFi path and 5GHz band WiFi path) and dual cellular network path, select one or more networks and use it to improve network experience. Wherein, dual cellular network paths can be both LTE networks, or both 5G networks, or , one of the dual-cellular network paths is an LTE network path, and the other is a 5G network path.

Since the WLAN and the cellular network are likely to belong to different network operators, the major operators build networks independently. After the terminal device queries the internet protocol (IP) address of the service server through the domain name system (DNS) server, and accesses the service server by using LinkTurbo technology through the IP address, there will be a cross-network (internet) access to the service server. In the case of cross-operator), the rate of the access channel across the network of the carrier will be limited, which affects the service experience in the multi-network scenario and reduces the communication efficiency.

SUMMARY OF THE INVENTION

The present application provides a method and a communication device for determining the address of a service server. By performing DNS queries under different network paths, respectively, the IP addresses corresponding to the service servers on different network paths are obtained, and the corresponding IP addresses under different networks are used. Addresses interact with service servers on their respective network paths, thereby avoiding cross-network communication when accessing service servers, ensuring access rates, improving service experience in multi-network scenarios, and improving communication efficiency.

In a first aspect, a method for determining an address of a service server is provided, and the execution body of the method may be either a terminal device or a chip applied to the terminal device. The method includes: a terminal device sends a first request to a domain name system DNS server through a first network, where the first request includes a first domain name, and the first request is used to request a first Internet connection of a first service server corresponding to the first domain name Protocol IP address, the first IP address is used by the terminal device to access the first service server through the first network; the terminal device sends a second request to the DNS server through the second network, and the second request includes the first service server domain name, the second request is used to request the second IP address of the first service server, and the second IP address is used by the terminal device to access the first service server through the second network; the terminal device receives the transmission from the DNS server the first information in response to the first request, the first information includes the first IP address; the terminal device receives the second information sent by the DNS server in response to the second request, the second information includes the first Two IP addresses.

In the method for determining the address of the service server provided by the first aspect, the terminal device obtains the corresponding IP addresses of the service server on different network paths by performing DNS queries respectively on different network paths. Terminal devices can use the corresponding IP addresses in different networks to interact with service servers on their respective network paths, thereby avoiding cross-network communication when accessing service servers, ensuring access rates, and improving services in multi-network scenarios. experience and improve communication efficiency.

Optionally, in this embodiment of the present application, the terminal device uses the LinkTurbo technology to access the service server through (or using) the first network and the second network. Optionally, the first network may be a WLAN, for example, the first network is specifically a WIFI network, and the WIFI network may be dual WiFi paths (a WiFi path in the 2.4GHz frequency band and a WiFi path in the 5GHz frequency band). The second network may be a cellular network, and the cellular network may be a dual-cellular network path, wherein the dual-cellular network paths may both be LTE networks, or both may be 5G networks, or, one of the dual-cellular network paths may be an LTE network path, and in addition One is the 5G network path.

In a possible implementation manner of the first aspect, the first network and the second network belong to different network operators, or the first network and the second network belong to the same network operator. For example, the first network may belong to a telecommunications network operator, the second network Unicom or a mobile network operator. Alternatively, the first network may belong to a China Unicom network operator, a second network telecommunication or mobile network operator, or the like. Alternatively, both the first network and the second network belong to a telecommunication network operator or the like.

In a possible implementation manner of the first aspect, the method further includes: the terminal device, according to the first IP address, performs service communication with the first service server through the first network, for example, sending a service to the first service server through the first network. The first service server sends a service request; the terminal device performs service communication with the first service server through the second network according to the second IP address, for example, sends a service request to the first service server through the second network. In this implementation manner, after the terminal device obtains the IP addresses of the service servers corresponding to different networks, it can interact with the service servers under different networks through different IP addresses, which can avoid cross-network access to the server. In the case of communication, the access rate is guaranteed, the service experience in multi-network scenarios is improved, and the communication efficiency is improved.

In a possible implementation manner of the first aspect, the terminal device sends a service request to the first service server through the first network according to the first IP address, where the service request includes the first domain name; the terminal device receives The second information sent by the first service server in response to the service request, the second information includes: a second domain name corresponding to the first domain name, and a third IP address of the second service server corresponding to the second domain name , and the third IP address is used by the terminal device to access the second service server through the first network. In this implementation manner, an HTTP 302 jump occurs in the HTTP request sent by the terminal device to the first service server through the first network. The HTTP 302 jump can be understood as a temporary transfer of resources accessed by the terminal device, and the terminal device needs to obtain a new The resource location (the IP address of the server that actually stores the resource), and then revisit to get the resource. That is, the first service server is not the service server that actually stores the resources that the terminal device needs to access. ) feedback to the terminal device, so that the terminal device can interact with the second service server through the third IP address corresponding to the first network, and pull the stored resources of the second service server, ensuring that the terminal device can accurately and smoothly obtain the required resources to ensure the quality of communication.

In a possible implementation manner of the first aspect, the method further includes: sending, by the terminal device, a service request to the second service server through the first network according to the third IP address.

In a possible implementation manner of the first aspect, the method further includes: the terminal device sends a third request to the DNS server through the second network, where the third request includes the second domain name, and the third request is used to request the fourth IP address corresponding to the second service server, where the fourth IP address is used by the terminal device to access the second service server through the second network; the terminal device receives the message sent by the DNS server in response to the third request third information, where the third information includes the fourth IP address. In this implementation manner, the terminal device can obtain the IP address (fourth IP address) of the second network corresponding to the second service server that actually stores resources through DNS query, so that the terminal device can pass the corresponding IP address of the second network. The fourth IP address interacts with the second service server, and pulls the stored resources of the second service server, which ensures that the terminal device can obtain the required resources accurately and smoothly, and ensures the communication quality.

In a possible implementation manner of the first aspect, the method further includes: the terminal device performs service communication with the second service server through the second network according to the four IP addresses, for example, sending the service to the first service server through the second network. 2. The service server sends a service request.

In a possible implementation manner of the first aspect, the first network is a wireless local area network WLAN, and the second network is a Long Term Evolution System LTE network or a new wireless NR network.

In a second aspect, a method for determining an address of a service server is provided, and the execution body of the method may be either a terminal device or a chip applied to the terminal device. The method includes: a terminal device sends a first request to a domain name system DNS server through a first network, where the first request includes a first domain name, and the first request is used to request a first Internet connection of a first service server corresponding to the first domain name Protocol IP address, the first IP address is used by the terminal device to access the first service server through the first network; the terminal device sends a second request to the DNS server through the second network, and the second request includes the first service server domain name, the second request is used to request the second IP address of the third service server, and the second IP address is used by the terminal device to access the third service server through the second network; the terminal device receives the information sent by the DNS server In response to the first information of the first request, the first information includes the first IP address; the terminal device receives the second information sent by the DNS server in response to the second request, the second information includes the second information IP address. The third service server and the first service server are different service servers, and the CDN data or content stored in the third service server and the first service server are consistent.

In the method for determining the address of the service server provided by the second aspect, the terminal device obtains the corresponding IP addresses of the service server on different network paths by performing DNS query respectively on different network paths. Terminal devices can use the corresponding IP addresses in different networks to interact with service servers on their respective network paths, thereby avoiding cross-network communication when accessing service servers, ensuring access rates, and improving services in multi-network scenarios. experience and improve communication efficiency.

In a possible implementation manner of the second aspect, the method further includes: according to the first IP address, the terminal device performs service communication with the first service server through the first network, for example, sending a service to the first service server through the first network. The first service server sends a service request; the terminal device performs service communication with the third service server through the second network according to the second IP address, for example, sends a service request to the third service server through the second network. In this implementation manner, after the terminal device obtains the IP addresses of the service servers corresponding to different networks, it can interact with the service servers under different networks through different IP addresses, which can avoid cross-network access to the server. In the case of communication, the access rate is guaranteed, the service experience in multi-network scenarios is improved, and the communication efficiency is improved.

In a possible implementation manner of the second aspect, the first network and the second network belong to different network operators, or the first network and the second network belong to the same network operator. For example, the first network may belong to a telecommunications network operator, the second network Unicom or a mobile network operator. Alternatively, the first network may belong to a China Unicom network operator, a second network telecommunication or mobile network operator, or the like. Alternatively, both the first network and the second network belong to a telecommunication network operator or the like.

In a third aspect, a method for determining an address of a service server is provided, and the execution body of the method may be either a terminal device or a chip applied to the terminal device. The method includes: a terminal device sends a first request to a DNS server through a first network, where the first request includes a first domain name, and the first request is used to request a first IP address of a first service server corresponding to the first domain name, The first IP address is used by the terminal device to access the first service server through the first network. The terminal device receives first information sent by the DNS server in response to the first request, where the first information includes the first IP address. The terminal device sends a service request to the first service server through the first network according to the first IP address, where the service request includes the first domain name. The terminal device receives second information sent by the first service server in response to the service request, where the second information includes: a second domain name corresponding to the first domain name and a third IP address of the second service server corresponding to the second domain name, The third IP address is used by the terminal device to access the second service server through the first network. The terminal device sends a third request to the DNS server through the second network, the third request includes the second domain name, the third request is used to request a fourth IP address corresponding to the second service server, and the fourth IP address is used for the terminal device Access the second service server through the second network. The terminal device receives third information sent by the DNS server in response to the third request, where the third information includes a fourth IP address.

In the method for determining the service server address provided by the third aspect, the terminal device can maintain a whitelist of domain names, the whitelist of domain names includes one or more domain names, and the domain names included in the whitelist of domain names will be redirected by HTTP 302. The domain name whitelist includes the first domain name. After the terminal device obtains the second domain name corresponding to the first domain name after the HTTP 302 redirection, the second service server that actually stores the resource is queried through DNS corresponding to the operator of the second network. IP address (fourth IP address). Then, the fourth IP address can be used to interact with the second service server to pull the stored resources of the second service server. The terminal device only needs to perform a DNS query process through the second network of China Unicom, and then it can query the IP address (fourth IP address) of the operator of the second network corresponding to the second service server that actually stores the resources that the terminal device needs to access. Reduce signaling overhead, save communication resources, and further improve communication efficiency.

In a possible implementation manner of the third aspect, the first network and the second network belong to different network operators, or the first network and the second network belong to the same network operator. For example, the first network may belong to a telecommunications network operator, the second network Unicom or a mobile network operator. Alternatively, the first network may belong to a China Unicom network operator, a second network telecommunication or mobile network operator, or the like. Alternatively, both the first network and the second network belong to a telecommunication network operator or the like.

In a possible implementation manner of the third aspect, the method further includes: the terminal device performs service communication with the second service server through the second network according to the four IP addresses.

In a possible implementation manner of the third aspect, the first network is a wireless local area network WLAN, and the second network device is a Long Term Evolution System LTE network or a new wireless NR network.

In a fourth aspect, a method for determining an address of a service server is provided, and the execution body of the method may be either a DNS server or a chip applied to the DNS server. The method includes: a DNS server receives a first request from a terminal device, the first request includes a first domain name, the first request is used to request a first IP address of a first service server corresponding to the first domain name, and the first request includes a first domain name. An IP address is used for the terminal device to access the first service server through the first network; the DNS server receives a second request from the terminal device, the second request includes the first domain name, and the second request is used to request The second IP address of the first service server corresponding to the first domain name, where the second IP address is used by the terminal device to access the first service server through the second network;

The DNS server sends first information in response to the first request to the terminal device, where the first information includes the first IP address; the DNS server sends second information in response to the second request to the terminal device, the first information includes the first IP address The second information includes the second IP address.

In the method for determining the address of the service server provided by the fourth aspect, the DNS server determines the corresponding IP addresses of the service server on different network paths according to the DNS query requests respectively sent by the terminal device under different network paths, and assigns the service server to the different network paths. The corresponding IP addresses on the network path are fed back to the terminal device, so that the terminal device can use the corresponding IP addresses under different networks to interact with the service server on their respective network paths, thereby avoiding cross-network communication when accessing the service server. In this case, the access rate is guaranteed, the service experience in multi-network scenarios is improved, and the communication efficiency is improved.

In a possible implementation manner of the fourth aspect, the first network and the second network belong to different network operators, or the first network and the second network belong to the same network operator.

In a possible implementation manner of the fourth aspect, the method further includes: the DNS server receiving a third request from the terminal device, where the third request includes a second domain name, and the second domain name corresponds to the first domain name, The third request is used to request the fourth IP address of the second service server, the second service server is the service server corresponding to the second domain name, and the fourth IP address is used for the terminal device to access the second service through the second network. a service server; the DNS server sends third information in response to the third request to the terminal device, where the third information includes the four IP addresses.

In a possible implementation manner of the fourth aspect, the first network is a wireless local area network WLAN, and the second network device is a Long Term Evolution System LTE network or a new wireless NR network.

In a fifth aspect, a communication device is provided, the communication device comprising a unit for performing each step in the above first aspect or any possible implementation manner of the first aspect, or, comprising a unit for performing the above second aspect The aspect or the unit of each step in the possible implementation manner of any aspect of the second aspect, or, including the unit for performing each step in the above third aspect or any possible implementation manner of the third aspect.

In a sixth aspect, a communication apparatus is provided, the communication apparatus including a unit for performing each step in the above fourth aspect or any possible implementation manner of the fourth aspect.

In a seventh aspect, a communication device is provided, the communication device includes at least one processor and a memory, and the at least one processor is configured to execute the method in the first aspect or any possible implementation manner of the first aspect, or, For performing the above second aspect or the method in any possible implementation manner of the second aspect, or for performing the above third aspect or the method in any possible implementation manner of the third aspect.

In an eighth aspect, a communication device is provided, the communication device includes at least one processor and a memory, where the at least one processor is configured to execute the above fourth aspect or the method in any possible implementation manner of the fourth aspect.

In a ninth aspect, a communication device is provided, the communication device includes at least one processor and an interface circuit, and the at least one processor is configured to execute the method in the above first aspect or any possible implementation manner of the first aspect, Or, for performing the above second aspect or the method in any possible implementation manner of the second aspect, or for performing the above third aspect or the method in any possible implementation manner of the third aspect method.

A tenth aspect provides a communication device, the communication device includes at least one processor and an interface circuit, where the at least one processor is configured to execute the method in the fourth aspect or any of the possible implementations of the fourth aspect.

In an eleventh aspect, a terminal device is provided, and the terminal device includes any one of the communication apparatuses provided in the fifth aspect, the seventh aspect, or the ninth aspect.

A twelfth aspect provides a DNS server, where the DNS server includes any of the communication devices provided in the sixth aspect, the eighth aspect, or the tenth aspect.

A thirteenth aspect provides a computer program product, the computer program product comprising a computer program, when executed by a processor, for performing the method in any one of the first to fourth aspects, or , which is used to execute the method in any possible implementation manner of any one of the first aspect to the fourth aspect.

A fourteenth aspect provides a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and when the computer program is executed, is used to execute any one of the first to third aspects. A method, or a method for performing any possible implementation manner of any one of the first aspect to the fourth aspect.

A fifteenth aspect provides a chip, the chip comprising: a processor for calling and running a computer program from a memory, so that a communication device installed with the chip executes any one of the first to fourth aspects A method, or a method for performing any possible implementation manner of any one of the first aspect to the fourth aspect.

The method for determining the address of a service server provided by the present application obtains the corresponding IP addresses of the service server on different network paths by performing DNS query respectively under different network paths. Terminal devices can use the corresponding IP addresses in different networks to interact with service servers on their respective network paths, thereby avoiding cross-network communication when accessing service servers, ensuring access rates, and improving services in multi-network scenarios. experience and improve communication efficiency.

Description of drawings

Figure 1 is a schematic diagram of a terminal device using LinkTurbo technology.

FIG. 2 is a schematic diagram of an example of a process of accessing a service server by a terminal device under dual networks provided by the present application.

FIG. 3 is a schematic diagram of an example of a communication system provided by the present application and applicable to an embodiment of the present application.

FIG. 4 is a schematic flowchart of an example of a method for determining an address of a service server provided by an embodiment of the present application.

Fig. 5 is an example of a schematic interface diagram displayed by a terminal device provided by the present application when the method provided by the present application is used.

FIG. 6 is a schematic flowchart of another example of a method for determining an address of a service server provided by an embodiment of the present application.

FIG. 7 is a schematic flowchart of an example of a pre-engine processing flow and a post-engine processing flow provided by an embodiment of the present application.

FIG. 8 is a schematic diagram of an example of a pre-engine processing flow provided by an embodiment of the present application.

FIG. 9 is a schematic diagram of an example of a post-engine processing flow provided by an embodiment of the present application.

FIG. 10 is a schematic diagram of an example of DNS query of multiple available networks provided by the present application.

FIG. 11 is a schematic diagram of an example of an MPDNS cache query process provided by the present application.

FIG. 12 is a schematic flowchart of another example of a method for determining an address of a service server provided by an embodiment of the present application.

FIG. 13 is a schematic flowchart of another example of a method for determining an address of a service server provided by an embodiment of the present application.

FIG. 14 is a schematic flowchart of another example of a method for determining an address of a service server provided by an embodiment of the present application.

FIG. 15 is a schematic block diagram of another example of the structure of a communication apparatus provided by an embodiment of the present application.

FIG. 16 is a schematic block diagram of another example of the structure of a communication apparatus provided by an embodiment of the present application.

FIG. 17 is a schematic block diagram of another example of the structure of a communication apparatus provided by an embodiment of the present application.

FIG. 18 is a schematic block diagram of another example of the structure of a communication apparatus provided by an embodiment of the present application.

detailed description

The technical solutions in the present application will be described below with reference to the accompanying drawings.

In the description of the embodiments of the present application, unless otherwise specified, "/" means or means, for example, A/B can mean A or B; "and/or" in this document is only an association that describes an associated object Relation, it means that there can be three kinds of relations, for example, A and/or B can mean that A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiments of the present application, "plurality" refers to two or more than two.

Hereinafter, the terms "first" and "second" are only used for descriptive purposes, and should not be construed as indicating or implying relative importance or implicitly indicating the number of indicated technical features. Thus, a feature defined as "first" or "second" may expressly or implicitly include one or more of that feature. In the description of this embodiment, unless otherwise specified, "plurality" means two or more.

Additionally, various aspects or features of the present application may be implemented as a method, apparatus, or article of manufacture using standard programming and/or engineering techniques. The term "article of manufacture" as used in this application encompasses a computer program accessible from any computer readable device, carrier or medium. For example, computer readable media may include, but are not limited to: magnetic storage devices (eg, hard disks, floppy disks, or magnetic tapes, etc.), optical disks (eg, compact discs (CDs), digital versatile discs (DVDs) etc.), smart cards and flash memory devices (eg, erasable programmable read-only memory (EPROM), card, stick or key drives, etc.). Additionally, various storage media described herein can represent one or more devices and/or other machine-readable media for storing information. The term "machine-readable medium" may include, but is not limited to, wireless channels and various other media capable of storing, containing, and/or carrying instructions and/or data.

The technical solutions of the embodiments of the present application can be applied to various communication systems, for example: a Global System of Mobile communication (GSM) system, a Code Division Multiple Access (CDMA) system, a wideband Code Division Multiple Access (CDMA) system (Wideband Code Division Multiple Access, WCDMA) system, General Packet Radio Service (General Packet Radio Service, GPRS), Long Term Evolution (Long Term Evolution, LTE) system, LTE Frequency Division Duplex (Frequency Division Duplex, FDD) system, LTE Time Division Duplex (TDD), Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication system, 5th Generation (5th Generation, 5G) system or New Radio (NR), etc.

The terminal device in this embodiment of the present application may refer to a user equipment, an access terminal, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent or user device. The terminal device may also be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a wireless communication Functional handheld devices, computing devices, or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in 5G networks, or terminals in a future evolved Public Land Mobile Network (PLMN) equipment, etc., which are not limited in this embodiment of the present application.

With the continuous growth of the number of users of mobile terminals (such as mobile phones), the business functions supported by various mobile terminals continue to increase. For example, functions such as instant messaging, securities, web browsing, and file download have gradually become the mainstream of terminal devices, especially smart phones. application. In the process of surfing the Internet, the mobile terminal needs to query the domain name of the uniform resource locator (URL) for the Internet protocol (IP) address corresponding to the domain name in order to send data packets. This process needs to be done by querying the Domain Name System (DNS) server.

A DNS server is a distributed host information database that provides mapping and conversion between domain names and IP addresses of business servers, and can resolve domain names to corresponding IP addresses through the DNS server. Terminal devices can access domain names through the domain name resolution service provided by DNS.

The process of domain name access is as follows: Take the terminal device accessing domain name A as an example, when the terminal device accesses the domain name A, it queries whether the IP address of the service server corresponding to the domain name A exists in its cache. If so, the terminal device can directly obtain the IP address of the service server. IP address, access the service server corresponding to the domain name A through the IP address. If it does not exist, the terminal device can send a domain name resolution request to the DNS server, the domain name resolution request carries the domain name A, and the DNS server returns the IP address corresponding to the domain name A, and the terminal device can access the domain name A through the IP address. business server.

In addition, after obtaining the IP address corresponding to the domain name, the terminal device generates and caches a DNS cache record. The DNS cache record is used to indicate the correspondence between the domain name and the IP address. In addition, the terminal device maintains a corresponding time to live (TTL) for each cached DNS cache record. The TTL of the DNS cache record is the retention time of the DNS cache record in the cache of the terminal device. In this way, if the terminal device needs to access the domain name in the DNS cache record again within the TTL of a certain DNS cache record, the terminal device can directly obtain the IP address corresponding to the domain name according to the DNS cache record. If the TTL of the DNS cache record is exceeded, the terminal device needs to access the domain name again, and obtain the IP address corresponding to the domain name through DNS server resolution.

With the advent of IPv6, the multi-address of the host (Multihome) has become more and more popular. Even the widely used Multihome hosts are increasing with the fourth edition of the Internet Protocol (internet protocol version 4, Ipv4). From the server under the fat-tree network architecture of the data center to the smart phone with 4G/Wifi/3G/Bluetooth multi-connection, all are multi-homed hosts. In order to make full use of the multi-connection characteristics of the device, the new multi-path transport layer protocol has become the biggest trend at present. The path transmission control protocol (multipath transmission control protocol, MPTCP) allows transmission control protocol connections to use multiple paths to maximize channel resource usage. Instead of using a single channel as required by the traditional TCP protocol, it supports inverse multiplexing of redundant channel resources, increasing the overall data transfer rate to the sum of all available channels. At the same time, MPTCP is also backward compatible with legacy TCP protocols.

After Huawei launched LinkTurbo technology for the first time in the industry, various partners also released related similar technologies later, and dual-network online has become a standard capability of communication technology. LinkTurbo can be understood as WLAN and data services online at the same time, using WLAN (such as wireless-fidelity, WiFi) and cellular network to improve network performance, intelligently select one or two networks between WiFi and cellular network and use it to improve network performance Network experience. Figure 1 shows a schematic diagram of the use of LinkTurbo technology by terminal equipment. As shown in Figure 1, when LinkTurbo supports turning on WiFi, start the cellular network at the same time to ensure that the dual networks are online at the same time. Wherein, WiFi can include two WiFi paths ( The WiFi path in the 2.4GHz band and the WiFi path in the 5GHz band), the cellular network can include two paths, that is, a dual-cellular path, and the dual-cellular network paths can be both LTE network paths, or both 5G network paths, or, dual-cellular paths One of the network paths is an LTE network path, and the other is a 5G network path. In high-throughput scenarios, the simultaneous online aggregation mode among the four network paths can be selected. In some low-latency scenarios, WiFi and cellular can be used One of the networks is the main data transmission mode, and the other is the backup data transmission mode, that is, the active-standby mode.

2 is a schematic diagram of a process of accessing a service server by a terminal device under dual networks. In the example shown in FIG. 2 , the WiFi network belongs to a telecommunication operator (Telecom Network), and the LTE network belongs to a Unicom operator (Unicom Network). The terminal first performs a DNS query under the default network (for example, WiFi), and the DNS server returns the service server IP address (for example, the IP address is 1.1.1.1) on the WIFI path (or corresponding to the telecommunications network) to the terminal device, and the terminal obtains the After the service server has an IP address, it interacts with the service server whose IP address is 1.1.1.1 on the WiFi path through the telecommunication network to obtain corresponding resources. In addition, the terminal device also interacts with the service server (IP address 1.1.1.1) through the Unicom network on the LTE path, that is, interacts with the service server through WIFI and LTE to obtain corresponding resources. As can be seen from Figure 2, since the IP address 1.1.1.1 is the IP address of the service server corresponding to the telecom network, and the terminal device needs to access the IP address through the Unicom network on the LTE path, the access service server on the LTE path has cross-network access. (across carriers).

At present, due to the independent network construction between major operators, the rate of the operator's cross-network channel will be limited, and in some scenarios, cross-network access may be blocked. For example, in the scenario shown in FIG. 2 , when the terminal device accesses the service server through the Unicom network on the LTE path, the access rate will be limited. That is to say, when the multi-network access of the terminal device belongs to different operator scenarios, the problem of limited multi-network access rate will occur. In order to reduce the impact of cross-network speed limit, content delivery network (CDN) manufacturers solve this problem by deploying cross-network border gateway protocol (BGP) routing, but the cost of deploying cross-network BGP routing is relatively high. High, at present, major CDN manufacturers have basically not deployed corresponding capabilities. Therefore, in the scenario of cross-network (cross-operator) access to CDN servers by terminal devices, the access rate will be limited, and in some scenarios, cross-network access may be blocked. , which affects the service experience in multi-network scenarios and reduces communication efficiency.

In view of this, the present application provides a method for determining the address of a service server. By performing DNS query under different network paths, respectively, the IP addresses corresponding to the service servers on different network paths are obtained, and the corresponding IP addresses under different networks are used. The IP addresses interact with service servers on their respective network paths, thus avoiding cross-network communication when accessing service servers, ensuring access rates, improving service experience in multi-network scenarios, and improving communication efficiency.

The method for determining the service server address provided by the present application will be described in detail below with reference to FIG. 3 and FIG. 4 .

FIG. 3 is a schematic structural diagram of an example of a wireless communication system applicable to an embodiment of the present application. As shown in Figure 3, when the terminal device needs to access the application, it can query the DNS server for the IP address of the service server corresponding to the domain name to be accessed. The IP address is used to access the service server, so as to obtain the data of the application that needs to be accessed. Moreover, the terminal device adopts the dual network connection technology (LinkTurbo technology). In the example shown in Figure 3, the terminal device utilizes a WiFi network and a cellular network to improve network performance. The WiFi network may include two WiFi paths (a WiFi path in the 2.4GHz band and a WiFi path in the 5GHz band). For cellular network (dual SIM), the dual cellular network paths can be both LTE networks or both 5G networks, or, one of the dual cellular network paths is an LTE network path and the other is a 5G network path. Among them, the WiFi belongs to the telecom network operator, the cellular network belongs to the China Unicom network operator, and the terminal device can access the service server through the WiFi network and the cellular network network. Alternatively, the WiFi network and the cellular network can also belong to the same network operator.

FIG. 4 is a schematic flowchart of a method 200 for determining an address of a service server according to an embodiment of the present application. This method can be applied to, for example, the scenario shown in FIG. 1 to FIG. 3 that cross-network occurs when accessing the service server under multiple networks. For example, in the cross-network scenario that occurs in the use of LinkTurbo technology. It should be understood that the method provided by the present application can also be applied to other systems where cross-network occurs when accessing a service server under multiple networks, which is not limited in this embodiment of the present application.

In the following description, the method provided by the present application will be described with the terminal device, the DNS server, and the service server as the main body of execution. As an example but not a limitation, the execution subject of the execution method may also be a chip applied to a terminal device, a DNS server, and a service server.

As shown in FIG. 4 , the method 200 shown in FIG. 4 may include S210 to S240. Each step in the method 200 will be described in detail below with reference to FIG. 4 .

S210, the terminal device sends a first request to the DNS server through the first network, where the first request includes a first domain name, the first request is used to request the first IP address of the first service server corresponding to the first domain name, the first The IP address is used by the terminal device to access the first service server through the first network. Correspondingly, the DNS server receives the first request.

S220, the terminal device sends a second request to the DNS server through the second network, where the second request includes the first domain name, and the second request is used to request the second IP address of the first service server. Optionally, the first network and the second network belong to different network operators, or the first network and the second network belong to the same network operator. Correspondingly, the DNS server receives the second request.

S230, the DNS server sends first information in response to the first request to the terminal device, where the first information includes the first IP address.

S240, the DNS server sends second information in response to the second request to the terminal device, where the second information includes the second IP address.

In this embodiment of the present application, the terminal device uses the LinkTurbo technology to access the service server through (or using) the first network and the second network. Optionally, in this embodiment of the present application, the first network may be a WLAN, for example, the first network is specifically a WIFI network, and the WIFI network may have dual WiFi paths (a WiFi path in the 2.4GHz band and a WiFi path in the 5GHz band). The second network may be a cellular network, and the cellular network may be a dual-cellular network path, wherein the dual-cellular network paths may both be LTE networks, or both may be 5G networks, or, one of the dual-cellular network paths may be an LTE network path, and in addition One is the 5G network path. It should be understood that, in this embodiment of the present application, the first network may also be a wireless local area network in other forms. The first network and the second network belong to different network operators, for example, the first network may belong to a telecommunication network operator, the second network Unicom or a mobile network operator. Alternatively, the first network may belong to a China Unicom network operator, a second network telecommunication or mobile network operator, or the like. In this embodiment of the present application, there is no limitation on the specific network operators to which the first network and the second network belong (or correspond to) respectively, as long as the first network and the second network belong to different network operators.

Optionally, in this embodiment of the present application, the first network and the second network may also belong to the same network operator.

It should be understood that, in this embodiment of the present application, there is no limitation on the specific network operators to which the first network and the second network belong (or correspond to) respectively.

Figure 5 shows an example of a schematic interface diagram displayed by the terminal device when the method provided by the present application is used. As shown in Figure a in Figure 5, after the user turns on the mobile data and WIFI, the user is in the terminal Select to open a certain APP on the display interface of the device, such as the "Video" APP, after the APP is started, as shown in Figure b in Figure 5, a dialog box pops up to the user on the display interface of the terminal device, prompting the user to "" WLAN and mobile data are being used at the same time", which means that the end device is using LinkTurbo technology. In this case, the terminal device (APP on the terminal device) can be triggered to execute the method of determining the service server address provided by this application.

In the following description, for convenience of description, the first network is WIFI, the second network is LTE, the first network belongs to a telecom network operator, and the second network belongs to a China Unicom network operator as an example for description. However, this should not impose any limitation on the embodiments of the present application. For example, the first network and the second network may also be other networks, and the first network and the second network may also belong to the same operator. The embodiments of the present application are not limited herein.

In S210, when the terminal device needs to access a certain domain name (for example, the first domain name), if the application on the terminal device creates a hypertext transfer protocol (HTTP) session, the query of the locally cached DNS type record will be invalid. The IP address of the service server corresponding to the first domain name will trigger the generation of the first request, for example, the first request may be a DNS query request. The terminal device (or the APP on the terminal device) can send a first request to the DNS server through the first network (WIFI network), where the first request includes the first domain name, and the first request is used to request the service corresponding to the first domain name The first IP address of the server (ie, the first service server), where WIFI belongs to a telecom operator, and the first IP address is used by the terminal device to access the first service server through the WIFI network. In other words, the first service server can correspond to multiple different IP addresses correspond to different operators, and the first request may be used to request the IP address (first IP address) of the telecommunications network corresponding to the first service server. Correspondingly, the DNS server receives the first request. That is to say, the terminal device can query the IP address of the service server corresponding to the telecommunication network on the WIFI path. For example, the first domain name may be www.xxx.com.

In S220, since the terminal device uses the LinkTurbo technology, it can also send a second request to the DNS server through the second network (LTE network), where the second request includes the first domain name, and the second request is used to request the first domain name. The second IP address of the first service server corresponding to a domain name, where LTE belongs to the operator of China Unicom, and the second IP address is used by the terminal device to access the first service server through the LTE network, that is, the second request is used to request The IP address (second IP address) of the Unicom network corresponding to the first service server. Correspondingly, the DNS server receives the second request. That is, the terminal device can also query the IP address of the service server corresponding to the China Unicom network on the LTE path. It should be understood that, in this embodiment of the present application, S220 is an optional step.

For example, in this embodiment of the present application, the terminal device may copy the first request on the WIFI path to obtain the second request, and then send the second request to the DNS through the LTE network.

In S230, the DNS server queries the IP address (first IP address) of the first application server corresponding to the telecommunication network according to the first request, and then sends first information in response to the first request to the terminal device, the first information Include the first IP address. For example, for different network operators, the first service server may be assigned different IP addresses, and different IP addresses correspond to different network operators. The DNS server may acquire and store multiple IP addresses of the first service server and network operators corresponding to different IP addresses from the operator of the service server. When the DNS server determines that the first request is sent on the network of a telecommunication operator (or may be referred to as a telecommunication network), it can determine that the first request is used to request the IP address of the telecommunication network corresponding to the first service server (the first IP address), thereby returning the IP address (first IP address) of the telecommunications network corresponding to the first service server to the terminal device through the first information. For example, the first information may be a DNS query response message. After acquiring the first IP address, the terminal device can store the correspondence between the first domain name, the first IP address, the WIFI path and the telecommunication network.

In S240, the DNS server queries the IP address (second IP address) of the first application server corresponding to the Unicom network on the LTE path according to the second request, and then sends the second information in response to the second request to the terminal device, The second information includes the first IP address. For example, when the DNS server determines that the second request is sent on the China Unicom operator's network (or may be referred to as the China Unicom network), it can determine that the second request is used to request the IP address of the China Unicom network corresponding to the first service server (second IP address) address, thereby returning the IP address (second IP address) of the Unicom network corresponding to the first service server to the terminal device through second information, for example, the second information can also be a DNS query response message . After acquiring the second IP address, the terminal device can store the correspondence between the first domain name, the second IP address, the LTE path, and the Unicom network.

Optionally, the terminal device may also store the correspondence between the first domain name, the first IP address, the second IP address, the telecommunication network, and the China Unicom network.

After the terminal device obtains the first IP address and the second IP address of the first service server, the terminal device determines the first IP address of the application server corresponding to the Unicom network on the LTE path, and the first IP address corresponding to the telecommunications network on the WIFI path. The second IP address of the application server, wherein the first IP address and the second IP are different. The first IP address and the second IP may correspond to the same application server (for example, a CDN server), or the first IP address and the second IP may correspond to different application servers, and the CDN data or content stored by different application servers are consistent.

Optionally, in this embodiment of the present application, after the DNS server receives the DNS requests sent by the terminal devices on the networks of different operators, the DNS server may filter and select the DNS requests, and only partially affect the dual-network services. The DNS corresponding to the stream is queried.

Optionally, in the embodiment of the application, taking FIG. 6 as an example, on the basis of the method steps shown in FIG. 4 , the method 200 further includes S250 and S260.

S250, the terminal device performs service communication with the first service server through the first network according to the first IP address.

S260, the terminal device performs service communication with the first service server through the second network according to the second IP address.

For the description of S210 to S240 shown in FIG. 6 , reference may be made to the description of these steps in the above-mentioned FIG. 4 , which will not be repeated here for brevity.

In S250, after acquiring the first IP address, the terminal device can perform service communication with the service server (the first service server) through the first IP address corresponding to the WIFI path of the telecommunication network according to the first IP address, for example, to the first IP address. A service server sends an HTTP request to pull resources stored in the service server. That is, the terminal device sends a service request to the service server on the WIFI path of the telecommunication network according to the first IP address to request service resources and data. For example, the service may be a video service or a browsing service Wait.

In S260, after obtaining the second IP address, the terminal device can perform business communication with the service server (the first service server) on the LTE path through the second IP address corresponding to the China Unicom network according to the second IP address, for example, to The first service server sends an HTTP request to pull resources stored in the service server. That is, according to the second IP address, the terminal device sends a service request to the service server on the LTE path of the Unicom network to request service resources and data.

In the method for determining the address of a service server provided by the present application, after the terminal device obtains the IP addresses of the service servers corresponding to different networks, it can interact with the service servers under different networks through different IP addresses, which can avoid accessing The cross-network communication of the server ensures the access rate, improves the service experience in multi-network scenarios, and improves the communication efficiency.

Optionally, in this embodiment of the present application, when the terminal device (specifically, the APP on the terminal device) uses the first IP address to access the first service server, it can query whether the first domain name corresponding to the first IP address corresponds to multiple IP address. In the case where the first domain name corresponds to multiple IP addresses, for example, the first domain name corresponds to the above-mentioned first IP address and second IP address, the APP on the terminal device can use the second IP address to bind the flow of the application Set on the China Unicom network corresponding to the second IP address, send a new HTTP request through (or use) the LTE network of the China Unicom network operator, and the destination address of the HTTP request is the second IP address, that is, through different IP addresses, respectively. Interact with business servers under different networks. If it is found that a certain domain name corresponds to only one IP address, the IP address is used to interact with the service server through only one network path, and no service offload processing is performed.

It should be understood that, in this embodiment of the present application, in a scenario where the first IP address and the second IP address correspond to different application servers (for example, CDN servers), the content of different service servers for the same resource may be inconsistent. Therefore, when the terminal pulls the same resource from different CDN servers, it matches the resource information. If the data of different CDN servers is found to be inconsistent when pulling the resource, it will no longer pull the offloaded data, that is, not under the multi-network path. of concurrent access. Further, when it is determined that the data of the CDN server is inconsistent, the corresponding IP addresses of different CDN servers will be recorded, and these IP addresses will be recorded as multiple abnormal IPs. When using these IPs to initiate resource requests later, no further processing will be performed. Handling of multiple requests for resources.

In the embodiment of the present application, in the process of initiating communication by the APP on the terminal device, there will be a pre-engine processing flow and a post-engine processing flow. FIG. 7 is a schematic diagram showing the processing flow of the pre-engine and the post-engine.

Among them, the processing flow of the front engine includes: the traditional DNS request (legacy DNS request) of the DNS server monitoring application, multi-channel and multi-network DNS query according to the available network, and writing the query result into the first-level cache. The processing flow of the front engine is as follows: It is executed ahead of the post-engine processing flow. For example, the flow shown in FIG. 4 is a possible implementation manner of the processing flow of the pre-engine.

The post-engine processing flow includes: after the terminal device and the CDN server establish a TCP connection through a TCP synchronization message (TCP SYN), the CDN server monitors the HTTP request of the APP (for requesting service data), and performs multiple processing according to the host field in the HTTP request. It performs DNS query on multiple networks, and writes the query result into the secondary cache. The post-engine processing flow is later than the front-end engine processing flow during execution. The host field includes the domain name and/or IP address of the http server to be accessed.

For example, for pre-engine processing, it is started when the application calls the traditional DNS query interface. Figure 8 shows a schematic diagram of the processing flow of the front-end engine. As shown in Figure 8, DNS query is first performed, and DNS query request is performed. Can include: user identification (user identification, UID), host, current network (curNet). When the netd process listens to the traditional DNS query of the whitelist application of the DNS domain name, it triggers the front-end engine to replicate multiple DNS requests on multiple different available networks (multiNets) according to the network on which the original DNS request is based and the currently available network. Query (the DNS domain name can also be controlled by the whitelist or not), and write the IP address (addrs) of the queried CDN server into the first-level cache. When there is any change (new or changed) in the entry in the first level cache, the changed entry is passed to the second level cache.

For the post-engine processing process, it starts when the application initiates a plaintext HTTP Request (HTTP Request) message. Figure 9 shows a schematic diagram of the post-engine processing flow. As shown in Figure 9, the kernel monitors When the HTTP plaintext request message is sent to the whitelist application, the host field in the content of the message, the destination IP (dstAddr) of the message, and the network (curNet) on which the message is currently transmitted are extracted, and written to the three parts of the kernel. level cache. Wherein, curNet can be determined by extracting network identification (netid) information according to the application framework layer mark (fwmark) of the socket (socket). Report the host to emcomd to trigger the post-engine to perform DNS query of multiple available networks (multiNets). The DNS query logic of the post-engine is the same as that of the front-end engine. ), the changed entry is passed to the L3 cache.

FIG. 10 is a schematic diagram of an example of DNS query of multiple available networks provided by the present application. In this embodiment of the present application, the DNS query of multiple available networks may also be referred to as a multipath DNS (multipath transmission domain name system, MPDNS) cache query. As shown in Figure 10, when the application creates and connects a socket, it extracts the destination IP (dstAddr) of the socket and the current network (curNet) it is based on, and then determines what the socket transmission is based on (or used) according to the acceleration algorithm. The target network (targetNet), combined with these three information as the input of the MPDNS cache, finds the target IP (dstAddrlnTargetNet) under the target network after searching in the cache, and finally rewrites the destination IP of the socket with this IP.

FIG. 11 is a schematic diagram of an example of an MPDNS cache query process provided by the present application. In the example shown in Figure 11, the kernel extracts the destination IP of the socket (for IPv4x), the network it is based on (for wlan0), and the NIC ID of the target network (for rmnet0), and uses these three pieces of information as the input of the MPDNS cache, After searching in the cache, get the destination IP under the target network (as IPv4y), and finally replace the destination IP in the socket with IPv4y.

Optionally, in some possible implementations of the present application, after using the method flow shown in FIG. 4 to perform the pre-engine query, taking FIG. 12 as an example, on the basis of the method steps shown in FIG. 200 also includes S241 and S242.

S241, the terminal device sends a service request to the first service server through the first network according to the first IP address, where the service request includes the first domain name.

S242: The first service server sends second information in response to the service request to the terminal device, where the second information includes: a second domain name corresponding to the first domain name, and a third domain name of the second service server corresponding to the second domain name The IP address, and the third IP address is used by the terminal device to access the second service server through the first network.

For the description of S210 to S240 shown in FIG. 12 , reference may be made to the description of these steps in the above-mentioned FIG. 4 , which is not repeated here for brevity.

In S241, after the terminal device completes the query by using the pre-engine processing flow, it is assumed that the service server (first service server) corresponding to the queried first IP address is not a service server that actually stores the resources that the terminal device needs to access, for example , the first service server is a scheduling server. In other words, the HTTP request sent by the terminal device (or the APP on the terminal device) will have an HTTP 302 jump on the WIFI path. The HTTP 302 jump can be understood as a temporary transfer of the resources accessed by the terminal device. The terminal device needs to Get the new resource location (the IP address of the server that actually stores the resource), and then revisit to obtain the resource, which means that the terminal device also needs to perform a post-engine query. Therefore, after the terminal device establishes a TCP session connection with the first service server through a TCP message (for example, a TCP SYN message) on the WIFI path, the terminal device will send the first service server through the WIFI network according to the first IP address. A service request (for example, an HTTP request), where the service request includes the first domain name. In S242, since the first service server is not the service server that actually stores the resources that the terminal device needs to access, that is, an HTTP 302 jump occurs, the first service server determines the service server (for example, the second service server that actually stores the resources) by querying The IP address (third IP address) of the telecommunication network corresponding to the service server), the third IP address is used by the terminal device to access the second service server through the WIFI network. The first service server will send second information in response to the service request to the terminal device, where the second information includes: the IP address (third IP address) of the telecommunications network corresponding to the second service server. At the same time, the first domain name may also be changed to a second domain name. Therefore, the second information further includes: a second domain name corresponding to the first domain name. In this way, the terminal device can obtain the IP address and the corresponding second domain name on the WIFI path corresponding to the second service server that actually stores the resource to be accessed.

After the terminal device obtains the IP address of the second service server on the WIFI path and the corresponding domain name, it can interact with the second service server on the WIFI path through the third IP address corresponding to the telecommunication network, and pull the second service server's IP address. stored resources. E.g. The terminal device can send a service request to the second service server through the WIFI network of the telecom operator according to the IP address of the second service server in the WIFI, and then obtain the required data and resources.

Optionally, in some possible implementation manners of the present application, taking FIG. 13 as an example, based on the method steps shown in FIG. 12 , the method 200 may further include S243 and S244 .

S243, the terminal device sends a third request to the DNS server through the second network, where the third request includes the second domain name, and the third request is used to request a fourth IP address corresponding to the second service server, the fourth IP address The address is used by the terminal device to access the second service server through the second network.

S244, the DNS server sends third information in response to the third request to the terminal device, where the third information includes the fourth IP address.

For the description of S210 to S242 shown in FIG. 13 , reference may be made to the description of these steps in the above-mentioned FIG. 12 , which is not repeated here for brevity.

Since the HTTP request sent by the terminal device is redirected by HTTP 302 on the WIFI path, on the LTE path, the terminal device also needs to re-query the DNS to obtain the IP address of the China Unicom network corresponding to the second service server (the fourth IP address ). That is to say, the terminal device also needs to perform the post-engine processing flow. In S243, the terminal device sends a third request (for example, a DNS query request) to the DNS server through the LTE path network according to the acquired second domain name corresponding to the first domain name, where the third request includes the second domain name, the The third request is used to request the IP address (fourth IP address) of the Unicom network corresponding to the second service server. In S244, the DNS server queries through the MPDNS cache. For example, when the DNS server determines that the third request is sent through the network of the China Unicom operator, it can determine that the third request is used to request the IP address of the China Unicom network corresponding to the second service server. address (fourth IP address) address, thereby returning the IP address (fourth IP address) of the Unicom network corresponding to the second service server to the terminal device through the third information. The third IP address and the fourth IP address are different.

After the terminal device obtains the IP address of the second service server on the LTE path, it can interact with the second service server on the LTE path through the IP address corresponding to the China Unicom network, and pull the stored resources of the second service server. E.g. The terminal device can send a service request to the second service server through the LTE network according to the IP address of the second service server on the LTE path, and then obtain the required data and resources.

It should also be understood that, in this embodiment of the present application, the terminal device may only perform the pre-engine processing flow. Or, in the case of HTTP 302 redirection, the terminal device needs to execute the pre-engine processing flow and the post-engine processing flow.

Optionally, in this embodiment of the present application, the terminal device may maintain a domain name whitelist, where the domain name whitelist includes one or more domain names, and the domain names included in the domain name whitelist can be understood as domain names that will undergo HTTP 302 redirection. Because the domain name included in the whitelist will definitely be redirected by HTTP 302. Therefore, in some possible implementation manners of the present application, taking FIG. 14 as an example, FIG. 14 is a schematic flowchart of a method 300 for determining a service server address according to an embodiment of the present application, as shown in FIG. 14 , shown in FIG. 14 . The resulting method 300 may include S310 to S360. Wherein, the domain name whitelist includes the first domain name.

S310, the terminal device sends a first request to the DNS server through the first network, where the first request includes a first domain name, the first request is used to request the first IP address of the first service server corresponding to the first domain name, the first The IP address is used by the terminal device to access the first service server through the first network. Correspondingly, the DNS server receives the first request.

S320, the DNS server sends first information in response to the first request to the terminal device, where the first information includes the first IP address.

S330, the terminal device sends a service request to the first service server through the first network according to the first IP address, where the service request includes the first domain name.

S340: The first service server sends second information in response to the service request to the terminal device, where the second information includes: a second domain name corresponding to the first domain name and a third IP address of the second service server corresponding to the second domain name , and the third IP address is used by the terminal device to access the second service server through the first network.

S350, the terminal device sends a third request to the DNS server through the second network, the third request includes the second domain name, the third request is used to request a fourth IP address corresponding to the second service server, and the fourth IP address is used to The terminal device accesses the second service server through the second network.

S360: The DNS server sends third information in response to the third request to the terminal device, where the third information includes a fourth IP address.

Specifically, in S310 and S320, the terminal device obtains the first IP address of the first service server. In S330, the terminal device sends a service request (for example, an HTTP request) to the first service server through the WIFI network. In S340, since the first service server is not the service server that actually stores the resources that the terminal device needs to access, the first service server determines, by querying, the telecommunication corresponding to the service server (for example, the second service server) that actually stores the resources. The IP address (third IP address) of the network, the first service server will send second information in response to the service request to the terminal device, the second information includes: the third IP address of the telecommunications network corresponding to the second service server, and a second domain name corresponding to the first domain name. In this way, after obtaining the IP address of the second service server on the WIFI path and the corresponding domain name, the terminal device can interact with the second service server on the WIFI path through the third IP address corresponding to the telecommunication network, and pull the second service server of stored resources.

On the LTE path, the terminal device also needs to perform a DNS query again to obtain the IP address (fourth IP address) of the China Unicom network corresponding to the second service server. In S350, the terminal device will send a third request (for example, a DNS query request) to the DNS server through the LTE network according to the acquired second domain name corresponding to the first domain name, where the third request includes the second domain name, the first domain name The third request is used to request the IP address (fourth IP address) of the Unicom network corresponding to the second service server. In S360, the DNS server queries through the MPDNS cache. For example, if the DNS server determines that the third request is sent through the network of the Unicom operator, it can determine that the third request is used to request the IP address of the China Unicom network corresponding to the second service server (fourth IP address), thereby returning the IP address (fourth IP address) of the Unicom network corresponding to the second service server to the terminal device through the third information. After the terminal device obtains the IP address of the second service server on the LTE path, it can interact with the second service server on the LTE path through the IP address corresponding to the China Unicom network, and pull the stored resources of the second service server. E.g. The terminal device can send a service request to the second service server through the LTE network of China Unicom according to the IP address of the second service server on the LTE path, and then obtain the required data and resources. That is to say, the terminal device only needs to perform a DNS query process through the China Unicom network on the LTE path, and then it can query the IP address (the fourth IP address) of the corresponding China Unicom network of the second service server that actually stores the resources that the terminal device needs to access. ), which can reduce signaling overhead, save communication resources, and further improve communication efficiency.

The method for determining the address of a service server provided by the present application obtains the corresponding IP addresses of the service servers on different network paths by performing DNS queries under different network paths respectively, and uses the corresponding IP addresses under different It interacts with the service server on the path, so as to avoid cross-network communication when accessing the service server, ensure the access rate, improve the service experience in multi-network scenarios, and improve the communication efficiency.

It should be understood that the above is only to help those skilled in the art to better understand the embodiments of the present application, but is not intended to limit the scope of the embodiments of the present application. Those skilled in the art can obviously make various equivalent modifications or changes according to the above examples. For example, some steps in the above method 200 and method 300 may not be necessary, or some new steps may be added. Or a combination of any two or any of the above embodiments. Such modifications, changes or combined solutions also fall within the scope of the embodiments of the present application.

It should be understood that, in various embodiments of the present application, first, second, etc. are only used to indicate that a plurality of objects are different. For example, the first service server and the second service server are only to represent different service servers. It should not have any impact on the service server itself and the number, etc., and the above-mentioned first, second, etc. should not cause any limitation to the embodiments of the present application.

It should also be understood that the manners, situations, categories, and divisions of the embodiments in the embodiments of the present application are only for the convenience of description, and should not constitute a special limitation, and the various manners, categories, situations, and features in the embodiments are not contradictory. can be combined.

It should also be understood that the various numbers and numbers involved in the embodiments of the present application are only for the convenience of description, and are not used to limit the scope of the embodiments of the present application. The size of the sequence numbers of the above processes does not mean the sequence of execution, and the execution sequence of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

It should also be understood that the above description of the embodiments of the present application focuses on emphasizing the differences between the various embodiments, and the unmentioned same or similar points can be referred to each other, and are not repeated here for brevity.

It should also be understood that, in this embodiment of the present application, “predefinition” may be implemented by pre-saving corresponding codes, forms or other means that can be used to indicate relevant information in the device (the application does not limit its specific implementation means) .

The method for determining the address of the service server according to the embodiment of the present application has been described in detail above with reference to FIGS. 1 to 14 . Hereinafter, the communication device according to the embodiment of the present application will be described in detail with reference to FIG. 15 to FIG. 18 .

15 shows a schematic block diagram of a communication apparatus 400 according to an embodiment of the present application. The communication apparatus 400 may correspond to the terminal equipment described in the foregoing method 200 and method 300, or may be a chip or component applied to the terminal equipment, and, Each module or unit of the communication apparatus 400 is respectively configured to execute each action or processing process performed by the terminal device in each of the embodiments of the method 200 and the method 300. As shown in FIG. 15 , the communication apparatus 400 may include: Processing unit 410 and communication unit 420.

As a possible implementation:

The processing unit 410 is configured to generate a first request and a second request.

The communication unit 420 is configured to send a first request to the DNS server through the first network, where the first request includes a first domain name, and the first request is used to request the first Internet Protocol IP of the first service server corresponding to the first domain name address, where the first IP address is used by the terminal device to access the first service server through the first network.

The communication unit 420 is further configured to send a second request to the DNS server through the second network, where the second request includes the first domain name, the second request is used to request the second IP address of the first service server, and the second request includes the first domain name. The second IP address is used for the terminal device to access the first service server through the second network;

The communication unit 420 is further configured to receive first information sent by the DNS server in response to the first request, where the first information includes the first IP address.

The communication unit 420 is further configured to receive second information sent by the DNS server in response to the second request, where the second information includes the second IP address.

The communication device provided by the present application obtains the IP addresses corresponding to the service servers on different network paths respectively by performing DNS queries under different network paths. Terminal devices can use the corresponding IP addresses in different networks to interact with service servers on their respective network paths, thereby avoiding cross-network communication when accessing service servers, ensuring access rates, and improving services in multi-network scenarios. experience and improve communication efficiency.

Optionally, in some embodiments of the present application, the first network and the second network belong to different network operators, or the first network and the second network belong to the same network operator.

For example, the first network may be a WLAN, for example, the first network is specifically a WIFI network, and the WIFI network may be dual WiFi paths (a WiFi path in the 2.4GHz frequency band and a WiFi path in the 5GHz frequency band). The second network may be a cellular network, and the cellular network may be a dual-cellular network path, wherein the dual-cellular network paths may both be LTE networks, or both may be 5G networks, or, one of the dual-cellular network paths may be an LTE network path, and in addition One is the 5G network path.

For example, the first network may belong to a telecommunications network operator, the second network Unicom or a mobile network operator. Alternatively, the first network may belong to a China Unicom network operator, a second network telecommunication or mobile network operator, or the like.

Optionally, in some embodiments of the present application, the processing unit 410 is further configured to generate a service request;

The communication unit 420 is further configured to send to the first service server through the first network according to the first IP address, the service request includes the first domain name;

Receive second information sent by the first service server in response to the service request, where the second information includes: a second domain name corresponding to the first domain name, and a third IP address of the second service server corresponding to the second domain name address, and the third IP address is used by the terminal device to access the second service server through the first network.

Optionally, in some embodiments of the present application, the communication unit 420 is further configured to perform service communication with the second service server through the first network according to the third IP address.

Optionally, in some embodiments of the present application, the processing unit 410 is further configured to generate a third request;

The communication unit 420 is further configured to send a third request to the DNS server through the second network, where the third request includes the second domain name, the third request is used to request the fourth IP address corresponding to the second service server, the The fourth IP address is used for the terminal device to access the second service server through the second network;

Third information sent by the DNS server in response to the third request is received, where the third information includes the fourth IP address.

Optionally, in some embodiments of the present application, the communication unit 420 is further configured to perform service communication with the second service server through the second network according to the four IP addresses.

Optionally, in some embodiments of the present application, the communication unit 420 is further configured to perform service communication with the first service server through the first network according to the first IP address; The second network performs service communication with the first service server.

Optionally, in some embodiments of the present application, the first network is a wireless local area network WLAN, and the second network is a Long Term Evolution System LTE network or a new wireless NR network.

As another possible implementation:

The communication unit 420 is further configured to send a second request to the DNS server through the second network, where the second request includes the first domain name, the second request is used to request the second IP address of the third service server, the second request The IP address is used for the terminal device to access the third service server through the second network;

The communication unit 420 is further configured to receive second information sent by the DNS server in response to the second request, where the second information includes the second IP address. The third service server and the first service server are different service servers, and the CDN data or content stored in the third service server and the first service server are consistent.

Optionally, in some embodiments of the present application, the communication unit 420 is further configured to perform service communication with the first service server through the first network according to the first IP address; The second network performs service communication with the third service server.

As yet another possible implementation:

a processing unit 410, configured to generate a first request;

The communication unit 420 is configured to send a first request to the DNS server through the first network, where the first request includes a first domain name, and the first request is used to request the first IP address of the first service server corresponding to the first domain name, The first IP address is used by the terminal device to access the first service server through the first network;

The communication unit 420 is further configured to receive first information sent by the DNS server in response to the first request, where the first information includes the first IP address;

The communication unit 420 is further configured to send a service request to the first service server through the first network according to the first IP address, where the service request includes the first domain name;

The communication unit 420 is further configured to receive second information sent by the first service server in response to the service request, where the second information includes: a second domain name corresponding to the first domain name, and a second domain name corresponding to the second domain name of the second service server. The third IP address, where the third IP address is used by the terminal device to access the second service server through the first network.

the processing unit 410, further configured to generate a third request;

The communication unit 420 is further configured to send a third request to the DNS server through the second network, where the third request includes a second domain name, and the third request is used to request a fourth IP address corresponding to the second service server, the fourth IP address for the terminal device to access the second service server through the second network;

The communication unit 420 is further configured to receive third information sent by the DNS server in response to the third request, where the third information includes a fourth IP address.

It should be understood that, for the specific process of each unit in the communication apparatus 400 performing the above-mentioned corresponding steps, please refer to the foregoing description in conjunction with FIG. 4, FIG. 6, FIG. 12 to FIG. related description. For the sake of brevity, they are not repeated here.

Optionally, the communication unit 420 may include a receiving unit (module) and a sending unit (module), configured to perform the steps of receiving information and sending information by the terminal device in the foregoing method embodiments. Optionally, the communication apparatus 400 may further include a storage unit for storing the instructions executed by the processing unit 410 and the communication unit 420 . The processing unit 410, the communication unit 420 and the storage unit are communicatively connected, the storage unit stores instructions, the processing unit 410 is used to execute the instructions stored in the storage unit, and the communication unit 420 is used to perform specific signal sending and receiving under the driving of the processing unit 410.

It should be understood that the communication unit 420 may be a transceiver, an input/output interface or an interface circuit, or the like. The storage unit may be a memory. The processing unit 410 may be implemented by a processor. As shown in FIG. 16 , the communication apparatus 500 may include a processor 510 , a memory 520 and a transceiver 530 .

The communication apparatus 400 shown in FIG. 15 or the communication apparatus 500 shown in FIG. 16 can implement various embodiments of the aforementioned method 200 and method 300, and the terminal of the related embodiments shown in FIGS. 4 , 6 , and 12 to 14 . The steps performed by the device. Similar descriptions can refer to the descriptions in the aforementioned corresponding methods. In order to avoid repetition, details are not repeated here.

It should also be understood that the communication apparatus 400 shown in FIG. 15 or the communication apparatus 500 shown in FIG. 16 may be terminal equipment, or the terminal equipment may include the communication apparatus 400 shown in FIG. 15 or the communication apparatus 500 shown in FIG. 16 .

FIG. 17 shows a schematic block diagram of a communication apparatus 600 according to an embodiment of the present application. The communication apparatus 600 may correspond to the DNS server described in the foregoing method 200 and method 300, or may be a chip or component applied to the DNS server, and, The modules or units of the communication apparatus 600 are respectively used to execute the actions or processing procedures performed by the DNS server in each of the above-mentioned methods 200 and 300. As shown in FIG. 17 , the communication apparatus 600 may include: communication unit 610 and processing unit 620.

The communication unit 610 is configured to receive a first request from a terminal device, where the first request includes a first domain name, and the first request is used to request the first IP address of the first service server corresponding to the first domain name, and the first request includes a first domain name. An IP address is used for the terminal device to access the first service server through the first network.

The processing unit 620 is configured to determine the first IP address according to the first request.

The communication unit 610 is further configured to receive a second request from the terminal device, where the second request includes the first domain name, and the second request is used to request the second IP address of the first service server corresponding to the first domain name , and the second IP address is used for the terminal device to access the first service server through the second network.

The processing unit 620 is further configured to determine the second IP address according to the second request.

The communication unit 610 is further configured to send first information in response to the first request to the terminal device, where the first information includes the first IP address;

The communication unit 610 is further configured to send second information in response to the second request to the terminal device, where the second information includes the second IP address.

The communication device provided by the present application, the communication device determines the corresponding IP addresses of the service servers on different network paths according to the DNS query requests respectively sent by the terminal equipment on different network paths, and separates the service servers on different network paths respectively. The corresponding IP address is fed back to the terminal device, so that the terminal device can use the corresponding IP addresses under different networks to interact with the service server on their respective network paths, thereby avoiding cross-network communication when accessing the service server. The access rate is improved, the service experience in multi-network scenarios is improved, and the communication efficiency is improved.

Optionally, in some embodiments of the present application, the communication unit 610 is further configured to:

Receive a third request from the terminal device, the third request includes a second domain name, the second domain name corresponds to the first domain name, the third request is used to request the fourth IP address of the second service server, the second domain name The service server is a service server corresponding to the second domain name, and the fourth IP address is used for the terminal device to access the second service server through the second network;

Sending third information in response to the third request to the terminal device, where the third information includes the quadruple IP address.

Optionally, the communication unit 610 may include a receiving unit (module) and a sending unit (module), configured to perform the steps of receiving information and sending information by the DNS server in each of the foregoing method embodiments. Optionally, the communication apparatus 600 may further include a storage unit for storing the instructions executed by the processing unit 620 and the communication unit 610 . The processing unit 620, the communication unit 610 and the storage unit are communicatively connected, the storage unit stores instructions, the processing unit 620 is used to execute the instructions stored in the storage unit, and the communication unit 610 is used to perform specific signal sending and receiving under the driving of the processing unit 620.

It should be understood that the communication unit 610 may be a transceiver, an input/output interface or an interface circuit, or the like. The storage unit may be a memory. The processing unit 620 may be implemented by a processor. As shown in FIG. 18 , the communication apparatus 700 may include a processor 710 , a memory 720 and a transceiver 730 .

The communication apparatus 600 shown in FIG. 17 or the communication apparatus 700 shown in FIG. 18 can implement the various embodiments of the aforementioned method 200 and method 300, and the DNS of the related embodiments shown in FIGS. 4, 6, 12 to 14. Steps performed by the server. Similar descriptions can refer to the descriptions in the aforementioned corresponding methods. In order to avoid repetition, details are not repeated here.

It should also be understood that the communication apparatus 600 shown in FIG. 17 or the communication apparatus 700 shown in FIG. 18 may be a DNS server, or the DNS server may include the communication apparatus 600 shown in FIG. 17 or the communication apparatus 700 shown in FIG. 18 .

It should also be understood that the division of units in the above apparatus is only a division of logical functions, and may be fully or partially integrated into a physical entity in actual implementation, or may be physically separated. And all the units in the device can be realized in the form of software calling through the processing element; also can all be realized in the form of hardware; some units can also be realized in the form of software calling through the processing element, and some units can be realized in the form of hardware. For example, each unit can be a separately established processing element, or can be integrated in a certain chip of the device to be implemented, and can also be stored in the memory in the form of a program, which can be called by a certain processing element of the device and execute the unit's processing. Function. Here, the processing element may also be called a processor, which may be an integrated circuit with signal processing capability. In the implementation process, each step of the above method or each of the above units may be implemented by an integrated logic circuit of hardware in the processor element or implemented in the form of software being invoked by the processing element.

In one example, a unit in any of the above apparatuses may be one or more integrated circuits configured to implement the above methods, eg, one or more application specific integrated circuits (ASICs), or, one or more A plurality of digital signal processors (DSPs), or, one or more field programmable gate arrays (FPGAs), or a combination of at least two of these integrated circuit forms. For another example, when a unit in the apparatus can be implemented in the form of a processing element scheduler, the processing element can be a general-purpose processor, such as a central processing unit (central processing unit, CPU) or other processors that can invoke programs. For another example, these units can be integrated together and implemented in the form of a system-on-a-chip (SOC).

An embodiment of the present application further provides a communication system, where the communication system includes: a terminal device and a DNS server in the foregoing method 200 and method 300 . Optionally, the communication system may further include the first service server in the method 200 and the method 300 . Further, the communication system may further include the second service server in the above method 200 and method 300.

Embodiments of the present application further provide a computer-readable storage medium for storing computer program codes, where the computer program includes instructions for executing any of the methods for determining an address of a service server provided by the above embodiments of the present application. The readable medium may be a read-only memory (read-only memory, ROM) or a random access memory (random access memory, RAM), which is not limited in this embodiment of the present application.

The present application also provides a computer program product, the computer program product includes an instruction, when the instruction is executed, so that the terminal device, the DNS server, the first service server, and the second service server perform corresponding operations corresponding to the above methods. operation.

An embodiment of the present application further provides a chip located in a communication device, the chip includes: a processing unit and a communication unit, the processing unit may be, for example, a processor, and the communication unit may be, for example, an input/output interface, a pin or a circuit, etc. The processing unit can execute computer instructions, so that the communication device executes any one of the methods for determining the address of the service server provided by the above embodiments of the present application.

Optionally, the computer instructions are stored in a storage unit.

Optionally, the storage unit is a storage unit in the chip, such as a register, a cache, etc., and the storage unit can also be a storage unit located outside the chip in the terminal, such as a read-only memory (ROM). ) or other types of static storage devices that can store static information and instructions, random access memory (RAM), etc. Wherein, the processor mentioned in any one of the above may be a CPU, a microprocessor, an ASIC, or one or more integrated circuits for controlling the program execution of the above-mentioned transmission method of feedback information. The processing unit and the storage unit can be decoupled, respectively disposed on different physical devices, and connected in a wired or wireless manner to implement the respective functions of the processing unit and the storage unit, so as to support the system chip to implement the above embodiments various functions in . Alternatively, the processing unit and the memory may also be coupled on the same device.

Wherein, the communication device, computer-readable storage medium, computer program product or chip provided in this embodiment are all used to execute the corresponding method provided above. Therefore, for the beneficial effects that can be achieved, reference may be made to the above-provided method. The beneficial effects in the corresponding method will not be repeated here.

It can be understood that the memory in this embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory. Wherein, the non-volatile memory may be ROM, programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically erasable programmable read-only memory (electrically EPROM) , EEPROM) or flash memory. Volatile memory can be RAM, which acts as an external cache. There are many different types of RAM such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate Synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory Access memory (direct rambus RAM, DR RAM).

The terms "system" and "network" are often used interchangeably herein. The term "and/or" in this article is only an association relationship to describe the associated objects, indicating that there can be three kinds of relationships, for example, A and/or B, it can mean that A exists alone, A and B exist at the same time, and A and B exist independently B these three cases. In addition, the character "/" in this document generally indicates that the related objects are an "or" relationship.

Various messages/information/equipment/network element/system/device/action/operation/process/concept that may appear in this application are given names. It can be understood that these specific names do not Constitutes a limitation on related objects, and the assigned names can be changed according to factors such as the scene, context or usage habits. The understanding of the technical meaning of the technical terms in this application should mainly be based on the functions embodied/executed in the technical solution. and technical effects.

In the various embodiments of the present application, if there is no special description or logical conflict, the terms and/or descriptions between different embodiments are consistent and can be referred to each other, and the technical features in different embodiments are based on their inherent Logical relationships can be combined to form new embodiments.

Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of this application.

The methods in the embodiments of the present application may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are executed in whole or in part. The computer may be a general purpose computer, special purpose computer, computer network, or other programmable device. The computer program or instructions may be stored in or transmitted over a computer-readable storage medium. The computer-readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server that integrates one or more available media.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the above-described systems, devices and units may refer to the corresponding processes in the foregoing method embodiments, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented. On the other hand, 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 units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as independent products, may be stored in a computer-readable storage medium. Based on such understanding, the technical solution of the present application can be embodied in the form of a software product in essence, or the part that contributes to the prior art or the part of the technical solution, and the computer software product is stored in a readable storage medium , including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned readable storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk, etc. that can store program codes medium.

The above are only specific embodiments of the present application, but the protection scope of the present application is not limited to this. should be covered within the scope of protection of this application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

A method for determining an address of a service server, comprising:

The terminal device sends a first request to a domain name system DNS server through the first network, where the first request includes a first domain name, and the first request is used to request the first Internet protocol of the first service server corresponding to the first domain name IP address, where the first IP address is used by the terminal device to access the first service server through the first network;

The terminal device sends a second request to the DNS server through the second network, where the second request includes the first domain name, and the second request is used to request the second IP address of the first service server, The second IP address is used by the terminal device to access the first service server through the second network;

receiving, by the terminal device, first information sent by the DNS server in response to the first request, where the first information includes the first IP address;

The terminal device receives second information sent by the DNS server in response to the second request, where the second information includes the second IP address.
The method according to claim 1, wherein the first network and the second network belong to different network operators, or the first network and the second network belong to the same network operator .
The method according to claim 1 or 2, wherein the method further comprises:

The terminal device sends a service request to the first service server through the first network according to the first IP address, where the service request includes the first domain name;

The terminal device receives second information sent by the first service server in response to the service request, where the second information includes: a second domain name corresponding to the first domain name, and a second domain name corresponding to the second domain name. The third IP address of the second service server, where the third IP address is used by the terminal device to access the second service server through the first network.
The method according to claim 3, wherein the method further comprises:

The terminal device performs service communication with the second service server through the first network according to the third IP address.
The method according to claim 3 or 4, wherein the method further comprises:

The terminal device sends a third request to the DNS server through the second network, where the third request includes the second domain name, and the third request is used to request a fourth IP address corresponding to the second service server , the fourth IP address is used by the terminal device to access the second service server through the second network;

The terminal device receives third information sent by the DNS server in response to the third request, where the third information includes the fourth IP address.
The method according to claim 5, wherein the method further comprises:

The terminal device performs service communication with the second service server through the second network according to the four IP addresses.
The method according to claim 1, wherein the method further comprises:

The terminal device performs service communication with the first service server through the first network according to the first IP address;

The terminal device communicates with the first service server through the second network according to the second IP address.
The method according to any one of claims 1 to 7, wherein the first network is a wireless local area network (WLAN), and the second network is a Long Term Evolution System (LTE) network or a new wireless NR network.
A method for determining an address of a service server, comprising:

The domain name system DNS server receives a first request from the terminal device, the first request includes a first domain name, and the first request is used to request the first IP address of the first service server corresponding to the first domain name, so The first IP address is used by the terminal device to access the first service server through the first network;

The DNS server receives a second request from the terminal device, where the second request includes the first domain name, and the second request is used to request the second request of the first service server corresponding to the first domain name. IP address, where the second IP address is used by the terminal device to access the first service server through the second network;

sending, by the DNS server, first information in response to the first request to the terminal device, where the first information includes the first IP address;

The DNS server sends second information in response to the second request to the terminal device, where the second information includes the second IP address.
The method according to claim 9, wherein the first network and the second network belong to different network operators, or the first network and the second network belong to the same network operator .
The method according to claim 9 or 10, wherein the method further comprises:

The DNS server receives a third request from the terminal device, the third request includes a second domain name, the second domain name corresponds to the first domain name, and the third request is used to request a second service server The fourth IP address of the second service server is the service server corresponding to the second domain name, and the fourth IP address is used by the terminal device to access the second service server through the second network;

The DNS server sends, to the terminal device, third information in response to the third request, where the third information includes the quad IP address.
The method according to any one of claims 9 to 11, wherein the first network is a wireless local area network (WLAN), and the second network is a Long Term Evolution System (LTE) network or a new wireless NR network.
A communication device, comprising:

processing unit: used to generate the first request and the second request;

The communication unit is further configured to send a first request to a domain name system DNS server through the first network, where the first request includes a first domain name, and the first request is used to request the first service server corresponding to the first domain name. a first Internet Protocol IP address, where the first IP address is used by the communication device to access the first service server through the first network;

The communication unit is further configured to send a second request to the DNS server through a second network, where the second request includes the first domain name, and the second request is used to request the first service server of the first service. Two IP addresses, where the second IP address is used by the communication device to access the first service server through the second network;

The communication unit is further configured to receive first information sent by the DNS server in response to the first request, where the first information includes the first IP address;

The communication unit is further configured to receive second information sent by the DNS server in response to the second request, where the second information includes the second IP address.
The communication device according to claim 13, wherein the first network and the second network belong to different network operators, or the first network and the second network belong to the same network operator business.
The communication device according to claim 13 or 14, characterized in that:

The communication unit is further configured to send a service request to the first service server through the first network according to the first IP address, where the service request includes the first domain name;

The communication unit is further configured to receive second information sent by the first service server in response to the service request, where the second information includes: a second domain name corresponding to the first domain name, the first domain name The third IP address of the second service server corresponding to the second domain name, where the third IP address is used by the communication device to access the second service server through the first network.
The communication device according to claim 15, wherein:

The communication unit is further configured to perform service communication with the second service server through the first network according to the third IP address.
The communication device according to claim 15 or 16, characterized in that,

The communication unit is further configured to send a third request to the DNS server through the second network, where the third request includes the second domain name, and the third request is used to request the corresponding domain name of the second service server. a fourth IP address, where the fourth IP address is used by the communication device to access the second service server through the second network;

The communication unit is further configured to receive third information sent by the DNS server in response to the third request, where the third information includes the fourth IP address.
The communication device according to claim 17, wherein:

The communication unit is further configured to perform service communication with the second service server through the second network according to the four IP addresses.
The communication device according to claim 13, wherein:

The communication unit is further configured to perform service communication with the first service server through the first network according to the first IP address;

The communication unit is further configured to communicate with the first service server through the second network according to the second IP address.
The communication device according to any one of claims 13 to 19, wherein the first network is a wireless local area network (WLAN), and the second network is a Long Term Evolution System (LTE) network or a new wireless NR network.
A communication device, comprising:

a communication unit, configured to receive a first request from a terminal device, where the first request includes a first domain name, and the first request is used to request a first IP address of a first service server corresponding to the first domain name, The first IP address is used by the terminal device to access the first service server through the first network;

The communication unit is further configured to receive a second request from the terminal device, where the second request includes the first domain name, and the second request is used to request a first service corresponding to the first domain name the second IP address of the server, where the second IP address is used by the terminal device to access the first service server through the second network;

a processing unit, configured to determine the first IP address and the second IP address according to the first request and the second request;

The communication unit is further configured to send first information in response to the first request to the terminal device, where the first information includes the first IP address;

The communication unit is further configured to send second information in response to the second request to the terminal device, where the second information includes the second IP address.
The communication device according to claim 21, wherein the first network and the second network belong to different network operators, or the first network and the second network belong to the same network operator business.
The communication device according to claim 21 or 22, characterized in that:

The communication unit is further configured to receive a third request from the terminal device, where the third request includes a second domain name, the second domain name corresponds to the first domain name, and the third request is used to request The fourth IP address of the second service server, the second service server is the service server corresponding to the second domain name, and the fourth IP address is used by the terminal device to access the second service through the second network server;

The communication unit is further configured to send third information in response to the third request to the terminal device, where the third information includes the four IP addresses.
The communication device according to any one of claims 21 to 23, wherein the first network is a wireless local area network (WLAN), and the second network is a Long Term Evolution System (LTE) network or a new wireless NR network.
A communication device, characterized in that the device comprises at least one processor coupled to at least one memory:

the at least one processor for executing computer programs or instructions stored in the at least one memory to cause the communication device to perform the method of any one of claims 1 to 8, or to perform the method as claimed in claim 1 The method of any one of 9 to 12.
A computer-readable storage medium, characterized in that, a computer program or instruction is stored in the computer-readable storage medium, and when the computer reads and executes the computer program or instruction, the computer is made to execute as claimed in claims 1 to 8 The method of any one of claims 9 to 12, or perform the method of any one of claims 9 to 12.
A chip, characterized by comprising: a processor for calling and running a computer program from a memory, so that a communication device installed with the chip executes the method according to any one of claims 1 to 8, or A method as claimed in any one of claims 9 to 12 is performed.