Communication methods, satellite system, electronic device and storage medium

Abstract

The present application relates to the technical field of communications. Disclosed are communication methods, a satellite system, an electronic device and a storage medium. In a communication method disclosed in the present application, when a first server has received a domain name resolution request sent by a terminal device, if the first server stores a first IP address corresponding to a first domain name in the domain name resolution request, the first IP address can be directly returned to the terminal device; and when the first server does not store the first IP address corresponding to the first domain name, the domain name resolution request is forwarded to a local domain name server by means of a second server deployed in a geostationary earth orbit satellite, and the first IP address is acquired from the local domain name server by means of the second server. In this way, satellite communication resources can be effectively saved, and the situation of network access failure of a terminal device can be effectively reduced, thereby improving the user experience.

Description

A communication method, satellite system, electronic device, and storage medium

[0001] This application claims priority to Chinese Patent Application No. 202411262375.5, filed on September 10, 2024, entitled “A Communication Method, Satellite System, Electronic Device and Storage Medium”, the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technology, and in particular to a communication method, satellite system, electronic device and storage medium. Background Technology

[0003] When a terminal device (such as a mobile phone) accesses the network, such as accessing a server corresponding to a domain name, it generally needs to first access a local domain name server (LDNS) to query the Internet Protocol (IP) address corresponding to the domain name, and then access the server corresponding to the domain name based on the IP address. For example, as shown in Figure 1, when a user enters the request Http: / / baab.com / index.abc in the browser application interface 101 of terminal device 100, terminal device 100 can send a domain name resolution request carrying the domain name "baab.com" to the LDNS. After receiving the domain name resolution request, the LDNS can obtain the IP address corresponding to the domain name "baab.com" (for example, the IP address is 202.1.201.1) and return the IP address to terminal device 100. Terminal device 100 then accesses the server corresponding to the domain name "baab.com" based on this IP address.

[0004] Among them, terminal devices can establish communication connections with LDNS based on terrestrial networks, such as wireless local area networks (WLAN) and 5G networks, to query the IP address corresponding to the domain name.

[0005] With the rapid development of space information technology, non-terrestrial networks (NTNs), such as satellite networks, have gradually matured, enabling more network services to be provided through them. For example, terminal devices can obtain the IP address corresponding to a domain name from a local DNS (LDNS) via satellite communication. When a terminal device connects to a satellite network and needs to query the IP address corresponding to a domain name, it can send a domain name resolution request carrying the domain name to a forwarding server deployed in the satellite via satellite communication. The forwarding server then sends the domain name resolution request to the LDNS via satellite communication and obtains the IP address returned by the LDNS. When the forwarding server obtains the IP address corresponding to the domain name, it can send that IP address to the terminal device. However, in the satellite communication-based scheme for obtaining the IP address corresponding to a domain name, the increasing demand for network access leads to frequent interactions between the satellite and the ground-based LDNS, resulting in significant consumption of satellite communication resources. Summary of the Invention

[0006] This application provides a communication method, a satellite system, an electronic device, and a storage medium.

[0007] In a first aspect, embodiments of this application provide a communication method for a satellite system. The satellite system includes a first server and a second server. The first server is deployed on a first satellite, which operates in a first Earth orbit. The second server is deployed on a second satellite, which operates in a second Earth orbit, which is higher than the first Earth orbit. The method includes: the first server receiving a first domain name resolution request sent by a terminal device in a ground system. The first domain name resolution request includes a first domain name that the terminal device requests to resolve. The first server stores a mapping relationship between domain names and IP addresses. When the first server determines, based on the mapping relationship between domain names and IP addresses, that it does not store a first IP address corresponding to the first domain name, the first server sends the first domain name resolution request to the second server. The second server sends the first domain name resolution request to a local domain name server in the ground system. The second server receives the first IP address corresponding to the first domain name sent by the local domain name server. The second server sends the first IP address to the first server. The first server sends the first IP address to the terminal device.

[0008] It's understandable that when the first server receives a domain name resolution request from a terminal device, if it stores the IP address corresponding to the first domain name carried in the request, it can directly return the IP address to the terminal device. This eliminates the need to retrieve the IP address from the local terrestrial domain name server each time. This reduces the number of interactions between the satellite server and the local terrestrial domain name server, saving satellite communication resources.

[0009] Furthermore, when the first server does not store the IP address corresponding to the first domain name carried in the domain name resolution request, the domain name resolution request is forwarded to the local domain name server through the second server deployed in the geostationary satellite. The second server obtains the IP address data from the local domain name server based on the satellite-to-ground communication link (or feeder link) between the geostationary satellite and the local domain name server. It can be understood that the network coverage area of ​​the geostationary satellite is much larger than that of the low-orbit satellite, and it operates synchronously with the Earth. Therefore, the satellite-to-ground communication link with the local domain name server can maintain a basically real-time connection. Thus, based on the fact that the second server can obtain the IP address corresponding to the first domain name in real time, the situation of network access failure of the aforementioned terminal devices can be effectively reduced, and the user experience can be improved.

[0010] It is understood that the first server mentioned in this application embodiment can be a secondary server mentioned in this application embodiment, the second server mentioned in this application embodiment can be a primary server mentioned in this application embodiment, and the first domain name mentioned in this application embodiment can refer to the target domain name mentioned in this application embodiment. The first IP address mentioned in this application embodiment can be the IP address corresponding to the target domain name mentioned in this application embodiment. The first satellite mentioned in this application embodiment can be satellite 200 mentioned in this application embodiment. The second satellite mentioned in this application embodiment can be satellite 500 mentioned in this application embodiment.

[0011] In one possible implementation of the first aspect above, the first server sends a first domain name resolution request to the second server, including: the first server identifies the first domain name resolution request as a first type of domain name resolution request, and sends the first domain name resolution request to the second server.

[0012] In some embodiments, the first server in the first satellite can further classify domain name resolution requests and perform different operations on different types of domain name resolution requests. For first-type domain name resolution requests (e.g., domain name resolution requests that need to access the server corresponding to a first-type application), if the first server in the first satellite does not have the IP address corresponding to the first domain name in the domain name resolution request, then the first server in the first satellite forwards the domain name resolution request to the second server in the geostationary satellite. For second-type domain name resolution requests (e.g., domain name resolution requests that need to access the server corresponding to a second-type application), if the first server in the first satellite does not have the IP address corresponding to the first domain name in the domain name resolution request, then it directly returns a resolution failure message to the terminal device, that is, it does not forward the domain name resolution request to the second server. In this way, data transmission between the satellite and the ground can be reduced, and the consumption of satellite resources can be reduced.

[0013] In one possible implementation of the first aspect described above, the satellite system further includes a User Plane Function (UPF); the first server receives a first domain name resolution request sent by a terminal device in the ground system, including: the UPF receiving the first domain name resolution request sent by the terminal device in the ground system; the UPF determining the first domain name resolution request as a first type of domain name resolution request based on the first domain name in the first domain name resolution request, marking the first domain name resolution request with a first identifier, and sending the first domain name resolution request and the first identifier to the first server.

[0014] In one possible implementation of the first aspect above, the User Plane Function (UPF) determines that the first domain name resolution request is a first type of domain name resolution request based on the first domain name in the first domain name resolution request, including: the UPF determines the application corresponding to the first domain name based on the first domain name in the first domain name resolution request, and obtains the contract information and / or user plane forwarding rule information corresponding to the application corresponding to the first domain name, and determines that the first domain name resolution request is a first type of domain name resolution request based on the contract information and / or user plane forwarding rule information corresponding to the application corresponding to the first domain name; or, the UPF obtains the user plane forwarding rule information corresponding to the first domain name based on the first domain name in the first domain name resolution request, and determines that the first domain name resolution request is a first type of domain name resolution request based on the user plane forwarding rule information corresponding to the first domain name.

[0015] In some embodiments, UPF 202 can communicate with network elements of the terrestrial core network, such as the Policy Control Function (PCF) and the Session Management Function (SMF), to obtain subscription information and user plane forwarding rule information associated with each application from network elements of the terrestrial core network such as the SMF and PCF.

[0016] In one possible implementation of the first aspect above, the first server identifies the first domain name resolution request as a first type of domain name resolution request, including: the first server receives the first domain name resolution request and the first identifier sent by the User Plane Function (UPF), and identifies the first domain name resolution request as a first type of domain name resolution request based on the first identifier.

[0017] In one possible implementation of the first aspect above, the method further includes: a first server receiving a second domain name resolution request sent by a terminal device, the second domain name resolution request including a second domain name requested for resolution by the terminal device; when the first server determines, based on the mapping relationship between domain names and IP addresses, that the first server does not store the second IP address corresponding to the second domain name, and identifies the second domain name resolution request as a second type of domain name resolution request, it sends a resolution failure message to the terminal device.

[0018] In some embodiments, for a second type of domain name resolution request, if the first server in the first satellite does not have the IP address corresponding to the first domain name in the domain name resolution request, it directly returns a resolution failure message to the terminal device, that is, it does not forward the domain name resolution request to the second server. This reduces data transmission between the satellite and the ground, thus reducing the consumption of satellite resources.

[0019] In one possible implementation of the first aspect above, the first server receiving the second domain name resolution request sent by the terminal device includes: the User Plane Function (UPF) receiving the second domain name resolution request sent by the terminal device; the UPF determining the second domain name resolution request as a second type of domain name resolution request based on the second domain name in the second domain name resolution request, marking the second domain name resolution request with a second identifier, and sending the second domain name resolution request and the second identifier to the first server.

[0020] In one possible implementation of the first aspect above, the satellite system further includes a third server, which is deployed on the third satellite. The third satellite and the first satellite are located in the same constellation, and there is an inter-satellite routing path between the third satellite and the second satellite. The first server sends a first domain name resolution request to the second server, including: the first server determining that there is no inter-satellite routing path between the first satellite and the second satellite, the first server sending the first domain name resolution request to the third server, and the third server sending the first domain name resolution request to the second server.

[0021] It is understood that the third satellite mentioned in the embodiments of this application may refer to satellite 700 mentioned in the embodiments of this application, and the third server may refer to the first server 701 mentioned in the embodiments of this application.

[0022] When there is no inter-satellite routing path between the first satellite (where the first server is located) and the geostationary satellite, the first server, upon determining that an inter-satellite routing path exists between the third and second satellites, can send the domain name resolution request to the third server on the third satellite. The third server then forwards the domain name resolution request to the second server. This ensures a high success rate for domain name resolution requests, reduces the number of network access failures for users, and improves user experience.

[0023] In one possible implementation of the first aspect above, the second server stores a mapping relationship between domain names and IP addresses, and the second server updates the mapping relationship between domain names and IP addresses from the local domain name server at a shorter interval than the first server updates the mapping relationship between domain names and IP addresses from the local domain name server; the second server sends a first domain name resolution request to the local domain name server, including: the second server determines, based on the mapping relationship between domain names and IP addresses stored in the second server, that the second server does not store a first IP address corresponding to the first domain name, and sends a first domain name resolution request to the local domain name server.

[0024] In some embodiments, the period during which the second server in the geostationary satellite updates domain names and their corresponding IP addresses from the local name server on the ground can be shorter than the period during which the first server in the first satellite updates the same information. Thus, the second server may store more domain names and IP addresses than the first server at certain times. When the second server in the geostationary satellite receives a domain name resolution request from the first server, it can determine whether the IP address corresponding to the first domain name in the request exists in its database. If not, the second server establishes a communication connection with the local name server on the ground to obtain the IP address. If the IP address exists, it directly sends the IP address to the first server, which then forwards it to the terminal device. This effectively reduces the interaction between the satellite server and the local name server on the ground, thus reducing the consumption of satellite resources.

[0025] In one possible implementation of the first aspect described above, the ground system further includes an ephemeris server; the first server sends a first domain name resolution request to the second server, including: the first server sending the first domain name resolution request and the identification information of the first satellite to the second server; the second server receiving the first IP address corresponding to the first domain name sent by the local domain name server, including: the ephemeris server receiving the identification information of the first satellite sent by the local domain name server, the ephemeris server being used to store the mapping relationship between the satellite identification information and ephemeris information; the ephemeris server obtaining the ephemeris information corresponding to the first satellite based on the identification information of the first satellite; the ephemeris server determining the network coverage ground range information of the first satellite based on the ephemeris information of the first satellite; the ephemeris server sending the network coverage ground range information of the first satellite to the local domain name server; the second server receiving the first IP address corresponding to the first domain name sent by the local domain name server, wherein the first IP address is obtained by the local domain name server based on the network coverage ground range information of the first satellite and the mapping relationship between domain names and IP addresses stored by the local domain name server.

[0026] It is understandable that satellite network coverage information can represent the approximate location of terminal devices. Based on this network coverage information, the local domain name server on the ground can select the application server corresponding to the first domain name that is closest to the terminal device's location from among multiple application servers corresponding to that first domain name. The server then sends the IP address of this closest application server as the IP address corresponding to the first domain name to the cache server. This effectively shortens the access path and reduces latency for the terminal device.

[0027] In one possible implementation of the first aspect above, the network coverage area information of the first satellite includes: the location information of the ground gateway station to which the first satellite is currently connected.

[0028] In one possible implementation of the first aspect above, the method by which the local domain name server obtains the first IP address corresponding to the first domain name based on the network coverage location information of the first satellite and the mapping relationship between domain names and IP addresses stored in the local domain name server includes: the local domain name server determining at least one IP address corresponding to the first domain name based on the mapping relationship between domain names and IP addresses stored in the local domain name server; the local domain name server selecting the first IP address from the at least one IP address, wherein the first IP address is the IP address corresponding to the application server that is closest to the location information of the ground gateway station.

[0029] Secondly, embodiments of this application provide a communication method for a satellite system. The satellite system includes a User Plane Function (UPF) and a second server. The second server is deployed on a second satellite, which operates in a second Earth orbit, which is a geosynchronous orbit. The method includes: the UPF receiving a first domain name resolution request sent by a terminal device in a ground system; the first domain name resolution request includes a first domain name that the terminal device requests to resolve; the UPF determining that the first domain name resolution request is a first type of domain name resolution request based on the first domain name in the first domain name resolution request, and sending the first domain name resolution request to the second server; the second server sending the first domain name resolution request to a local domain name server in the ground system; the second server receiving a first IP address corresponding to the first domain name sent by the local domain name server; and the second server sending the first IP address to the terminal device.

[0030] In some embodiments, domain name resolution requests are classified using UPF. For the second type of domain name resolution request, it may not be sent to the second server for processing. This reduces the data transmission between the geostationary satellite and the ground, thereby reducing the consumption of satellite resources.

[0031] In one possible implementation of the second aspect described above, the satellite system further includes a first server, which is deployed on a first satellite, the first satellite operating in a first Earth orbit, and a second Earth orbit higher than the first Earth orbit; the method further includes: a User Plane Function (UPF) receiving a second domain name resolution request sent by a terminal device; the UPF determining that the second domain name resolution request is a second type of domain name resolution request based on the second domain name in the second domain name resolution request, and sending the second domain name resolution request to the first server; when the first server determines, based on the mapping relationship between domain names and IP addresses, that the first server does not store the second IP address corresponding to the second domain name, the first server sends a resolution failure message to the terminal device; when the first server determines, based on the mapping relationship between domain names and IP addresses, that the first server stores the second IP address corresponding to the second domain name, the first server sends the second IP address to the terminal device.

[0032] In one possible implementation of the second aspect above, the second server sending a first domain name resolution request to the local domain name server includes: when the second server determines that it does not store the IP address corresponding to the first domain name, the second server sends a first domain name resolution request to the local domain name server.

[0033] Thirdly, embodiments of this application provide a satellite system, including: a first server and a second server, the first server being deployed on a first satellite, the first satellite operating in a first Earth orbit, the second server being deployed on a second satellite, the second satellite operating in a second Earth orbit, the second Earth orbit being higher than the first Earth orbit;

[0034] A first server is used to receive a first domain name resolution request sent by a terminal device in the ground system. The first domain name resolution request includes a first domain name that the terminal device requests to resolve. The first server stores a mapping relationship between domain names and IP addresses. When the first server determines, based on the mapping relationship between domain names and IP addresses, that it does not store a first IP address corresponding to a first domain name, it sends a first domain name resolution request to a second server. The second server is used to send the first domain name resolution request to a local domain name server in the ground system. The local domain name server is deployed on the ground. The second server is used to receive the first IP address corresponding to the first domain name sent by the local domain name server. The second server is used to send the first IP address to the first server. The first server is used to send the first IP address to the terminal device. The first IP address is used by the terminal device to access the application server corresponding to the first domain name.

[0035] In one possible implementation of the third aspect above, the first server is configured to send the first domain name resolution request to the second server when the first domain name resolution request is identified as a first type of domain name resolution request.

[0036] In one possible implementation of the third aspect above, the satellite system further includes a User Plane Function (UPF); the User Plane Function (UPF) is used to receive a first domain name resolution request sent by a terminal device; the User Plane Function (UPF) is used to determine that the first domain name resolution request is a first type of domain name resolution request based on the first domain name in the first domain name resolution request, mark the first domain name resolution request with a first identifier, and send the first domain name resolution request and the first identifier to the first server.

[0037] In one possible implementation of the third aspect above, the User Plane Function (UPF) is used to determine the application corresponding to the first domain name based on the first domain name in the first domain name resolution request, and to obtain the contract information and / or user plane forwarding rule information corresponding to the application corresponding to the first domain name, and to determine the first domain name resolution request as a first type of domain name resolution request based on the contract information and / or user plane forwarding rule information corresponding to the application corresponding to the first domain name; or, the User Plane Function (UPF) is used to determine the user plane forwarding rule information corresponding to the first domain name based on the first domain name in the first domain name resolution request, and to determine the first domain name resolution request as a first type of domain name resolution request based on the user plane forwarding rule information corresponding to the first domain name.

[0038] Fourthly, embodiments of this application provide a computer-readable storage medium storing executable instructions, which, when executed on an electronic device, implement the communication method mentioned in embodiments of this application.

[0039] Fifthly, embodiments of this application provide an electronic device, including: a memory for storing instructions executed by one or more processors of the electronic device, and one or more processors for executing the communication methods mentioned in embodiments of this application. Attached Figure Description

[0040] Figure 1 shows a schematic diagram of a browser interface 101 of a terminal device 100 according to some embodiments of this application;

[0041] Figure 2a illustrates a scenario of obtaining the IP address corresponding to a domain name based on satellite communication, according to some embodiments of this application.

[0042] Figure 2b illustrates a flowchart of a method for obtaining the IP address corresponding to a domain name based on satellite communication, according to some embodiments of this application.

[0043] Figure 3a illustrates a scenario based on some embodiments of this application, showing how a cache server deployed in a satellite obtains the IP address corresponding to a domain name.

[0044] Figure 3b illustrates a flowchart of a method for obtaining the IP address corresponding to a domain name based on a cache server, according to some embodiments of this application.

[0045] Figure 4 illustrates a schematic diagram of an iterative query method according to some embodiments of this application;

[0046] Figure 5a illustrates a scenario diagram of a communication method according to some embodiments of this application;

[0047] Figure 5b illustrates a detailed flowchart of a communication method according to some embodiments of this application;

[0048] Figure 6 illustrates a scenario diagram of a communication method for determining IP addresses based on geographical range, according to some embodiments of this application.

[0049] Figure 7 illustrates a flowchart of a communication method that performs different operations on different types of domain name resolution requests, according to some embodiments of this application.

[0050] Figure 8a illustrates a scenario where a secondary cache server forwards domain name resolution requests via auxiliary satellites within a constellation, according to some embodiments of this application.

[0051] Figure 8b illustrates a scenario where UPF and gNB, along with a secondary cache server, are deployed on different satellites, according to some embodiments of this application.

[0052] Figure 8c illustrates a flowchart of a communication method based on the scenario shown in Figure 8a, according to some embodiments of this application.

[0053] Figure 9 illustrates a flowchart of a communication method based on some embodiments of this application, combining a scenario of assisted satellite forwarding of domain name resolution requests with a scenario of classifying domain name resolution requests.

[0054] Figure 10 illustrates a flowchart of a communication method according to some embodiments of this application;

[0055] Figure 11 shows a schematic diagram of the structure of a terminal device according to some embodiments of this application;

[0056] Figure 12 shows a schematic diagram of the structure of a server according to some embodiments of this application. Detailed Implementation

[0057] The illustrative embodiments of this application include, but are not limited to, a communication method, a satellite system, an electronic device, and a storage medium.

[0058] It should be noted that this application does not limit the specific form of the terminal device. Electronic devices can be mobile phones, laptops, tablets, large-screen devices, wearable devices (e.g., smartwatches, smart glasses, helmets), desktop computers, augmented reality (AR) / virtual reality (VR) devices, personal digital assistants (PDAs), and other terminal devices, without any restrictions.

[0059] To better understand the solutions in the embodiments of this application, the terms involved in this application will be explained first.

[0060] DNS: A server that stores the mapping between domain names and IP addresses, used to translate domain names into IP addresses.

[0061] A Uniform Resource Locator (URL) is a unique address for any given resource on the Internet, used to indicate the server and specific location of a webpage on an Internet host. A URL typically includes a protocol (such as HTTP or HTTPS), a domain name (or server name), and the specific path to the resource. For example, for the URL "Http: / / baab.com / index.abc", the protocol is "Http", the domain name is "baab.com", and the specific path to the resource is "index.abc".

[0062] Geostationary Earth Orbit (GEO) Satellites: Satellites operating in geostationary orbit are called geostationary orbit satellites. Geostationary orbit satellites operate at an altitude of approximately 36,000 kilometers. They can provide a large satellite network coverage area; for example, a single geostationary orbit satellite can provide a network covering one-third of the Earth's surface, and can be approximated as moving synchronously with the Earth.

[0063] Medium Earth Orbit (MEO) satellites: Satellites operating in a medium Earth orbit are simply called MEO satellites. A medium Earth orbit is an artificial satellite orbit located between low Earth orbit and geostationary orbit. The orbital period of a medium Earth orbit satellite is generally between 2 and 24 hours.

[0064] Low Earth orbit (LEO) satellites: Satellites operating in a low Earth orbit, also known as LEO satellites, typically operate at altitudes between 300 and 2000 kilometers, for example, 800 kilometers. They travel at speeds greater than the Earth's rotation speed, resulting in smaller network coverage areas and lower data transmission latency with ground equipment.

[0065] Next-generation nodeB (gNB): also known as 5G base station, used to realize the connection between terminal equipment and 5G core network. For example, it is used to route the data sent by the terminal equipment to the data transmission network element in the 5G core network, such as the user plane function (UPF).

[0066] UPF: A network element in the 5G core network used for data routing and forwarding. For example, it is used to receive data sent by the gNB and forward the data to the corresponding server.

[0067] Feeder link: This describes a link in a satellite communication system used for data transmission between a ground gateway station and the satellite. Ground-based terminal equipment establishes a connection with the satellite in space via a service link. Simultaneously, the satellite communicates with the ground gateway via the feeder link. The ground gateway is also generally called a ground station or ground gateway station. The ground gateway station is responsible for routing data from the terminal equipment to terrestrial telephone, television networks, or the Internet.

[0068] Figure 2a illustrates a scenario where the IP address corresponding to a domain name is obtained based on satellite communication.

[0069] As shown in Figure 2a, when terminal device 100 needs to query the IP address corresponding to a target domain name, if terminal device 100 is connected to a satellite network, it can send the domain name resolution request to the forwarding server 301 in low-Earth orbit satellite 300 via gNB 201 and UPF 202 in low-Earth orbit satellite 200. Forwarding server 301 then sends the domain name resolution request to the ground-based LDNS 400 via ground gateway station 003, obtains the IP address corresponding to the target domain name carried in the domain name resolution request from LDNS 400, and sends the IP address corresponding to the target domain name to terminal device 100 via gNB 201 and UPF 202 in low-Earth orbit satellite 200. After receiving the IP address corresponding to the target domain name, terminal device 100 initiates a Transmission Control Protocol (TCP) connection to the application server 001 corresponding to the IP address to achieve network access. It can be understood that application server 001 can update its IP address and domain name with LDNS 400.

[0070] Figure 2b illustrates a flowchart of a method for obtaining the IP address corresponding to a domain name based on the scenario shown in Figure 2a. As shown in Figure 2b, the method includes:

[0071] 1001: Terminal device 100 sends a domain name resolution request to gNB 201 in low-Earth orbit satellite 200.

[0072] It is understood that when terminal device 100 needs to query the IP address corresponding to a target domain name, if terminal device 100 is connected to a satellite network, it can send a domain name resolution request carrying the target domain name to gNB 201 in low-Earth orbit satellite 200 via the satellite network. In some embodiments, the domain name resolution request may carry the target domain name.

[0073] 1002: gNB 201 sends a domain name resolution request to UPF 202 in low-Earth orbit satellite 200.

[0074] It is understandable that when gNB 201 receives a domain name resolution request, it can route the domain name resolution request to UPF 202 in the low-Earth orbit satellite 200 based on the satellite network.

[0075] 1003: UPF 202 sends a domain name resolution request to the forwarding server 301 in the low-Earth orbit satellite 300.

[0076] In some embodiments, when UPF 202 receives a domain name resolution request, it can find the target low-Earth orbit satellite according to the pre-configured satellite selection and scheduling strategy. For example, it can select the low-Earth orbit satellite 300 that is closest to the low-Earth orbit satellite 200 where UPF 202 is located as the target low-Earth orbit satellite, and send the domain name resolution request to the forwarding storage server 301 in the low-Earth orbit satellite 300 based on the satellite network.

[0077] 1004: The forwarding server 301 in the low-Earth orbit satellite 300 sends a domain name resolution request to the LDNS 400 on the ground.

[0078] It is understandable that when the forwarding server 301 receives a domain name resolution request, it can forward the domain name resolution request to the ground-based LDNS 400 in order to obtain the IP address corresponding to the target domain name from the ground-based LDNS 400.

[0079] 1005: LDNS 400 retrieves the IP address corresponding to the target domain name based on the domain name resolution request.

[0080] In some embodiments, when LDNS 400 receives a domain name resolution request, it can query the IP address corresponding to the target domain name from the data system based on the target domain name carried in the domain name resolution request.

[0081] 1006: LDNS 400 sends the IP address corresponding to the target domain name to forwarding server 301.

[0082] In some embodiments, after obtaining the IP address corresponding to the target domain name, LDNS 400 can send the IP address corresponding to the target domain name to the forwarding server 301.

[0083] 1007: Forwarding server 301 sends the IP address corresponding to the target domain name to UPF 202.

[0084] In some embodiments, when the forwarding server 301 receives the IP address corresponding to the target domain name, it can send the IP address corresponding to the target domain name to the UPF 202.

[0085] 1008: UPF 202 sends the IP address corresponding to the target domain name to gNB 201.

[0086] In some embodiments, when UPF 202 receives the IP address corresponding to the target domain name, it can send the IP address corresponding to the target domain name to gNB 201.

[0087] 1009: gNB 201 sends the IP address corresponding to the target domain name to terminal device 100.

[0088] In some embodiments, when gNB 201 receives the IP address corresponding to the target domain name, it can send the IP address corresponding to the target domain name to terminal device 100.

[0089] 1010: Terminal device 100 accesses the corresponding application server 001 based on its IP address.

[0090] In some embodiments, after receiving the IP address corresponding to the target domain name, the terminal device 100 can access the corresponding application server 001 based on the IP address.

[0091] In some embodiments, the terminal device 100 can access the corresponding application server 001 based on the IP address by sending an access request carrying the IP address to the gNB 201. After receiving the access request, the gNB 201 sends an access request to the UPF 202. After receiving the access request, the UPF 202 sends an access request to the ground gateway station 004. The ground gateway station 004 then sends an access request to the corresponding application server 001.

[0092] Access the corresponding application server 001 based on the IP address carried in the access request.

[0093] It is understandable that in the above method, the forwarding server 301 deployed in satellite 300 needs to forward the domain name resolution request to the ground-based LDNS 400 every time it receives a domain name resolution request from the terminal device, obtain the IP address corresponding to the target domain name from LDNS 400, and then return the IP address corresponding to the target domain name to the terminal device 100. Thus, due to the increasing demand for network access, the number of domain name resolution requests that forwarding server 301 needs to forward is relatively large, leading to frequent interactions between forwarding server 301 and the ground-based LDNS 400, resulting in significant consumption of satellite communication resources.

[0094] To address the aforementioned issues, some implementation schemes employ the deployment of caching servers within satellites to obtain the IP addresses corresponding to domain names. These caching servers can update the domain names and their corresponding IP addresses from the ground-based LDNS 400 at preset intervals (e.g., every hour) and cache them. Thus, when the caching server receives a domain name resolution request from a terminal device, if it already stores the IP address corresponding to the target domain name carried in the request, it can directly return the IP address to the terminal device, eliminating the need to retrieve the IP address from the ground-based LDNS every time. This reduces the number of interactions between the caching server and the ground-based LDNS, conserving satellite communication resources.

[0095] Figure 3a illustrates a scenario where a caching server deployed in a satellite retrieves the IP address corresponding to a domain name. As shown in Figure 3a, when terminal device 100 needs to query the IP address corresponding to a target domain name, if terminal device 100 is connected to a satellite network, it can send the domain name resolution request to the caching server 302 in the low-Earth orbit satellite 300 via gNB 201 and UPF 202 in the low-Earth orbit satellite 200. When the caching server 302 has cached the IP address corresponding to the target domain name, it can send the IP address to terminal device 100. Only when the caching server 302 has not cached the IP address will it send a domain name resolution request to the ground-based LDNS 400 via the ground gateway station 0031, retrieve the IP address corresponding to the target domain name returned by the LDNS 400, and send the retrieved IP address to terminal device 100. After receiving the IP address corresponding to the target domain name, terminal device 100 accesses the corresponding application server based on the IP address. It can be understood that application server 001 can update its IP address and domain name with the LDNS 400.

[0096] It can be understood that the cache server 302 caches the mapping relationship between domain names and IP addresses, and that the cache server 302 can send a domain name resolution request to the ground LDNS 400 based on the ground gateway station 0031 when it does not store the IP address corresponding to the target domain name requested by the terminal device for resolution. That is, in addition to the forwarding function of the forwarding server 301 mentioned above, the cache server 302 also has a caching function.

[0097] Figure 3b illustrates a flowchart of a method for obtaining the IP address corresponding to a domain name based on the scenario shown in Figure 3a. As shown in Figure 3b, the method includes:

[0098] 2001: Terminal device 100 sends a domain name resolution request to gNB 201 in low-Earth orbit satellite 200.

[0099] It is understood that when terminal device 100 needs to query the IP address corresponding to a target domain name, if terminal device 100 is connected to a satellite network, it can send a domain name resolution request carrying the target domain name to gNB 201 in low-Earth orbit satellite 200 via the satellite network. In some embodiments, the domain name resolution request may carry the target domain name.

[0100] 2002: gNB 201 sends a domain name resolution request to UPF 202 in low Earth orbit satellite 200.

[0101] It is understandable that when gNB 201 receives a domain name resolution request, it can route the domain name resolution request to UPF 202 in the low-Earth orbit satellite 200 based on the satellite network.

[0102] 2003: UPF 202 sends a domain name resolution request to cache server 302 in low-Earth orbit satellite 300.

[0103] In some embodiments, when UPF 202 receives a domain name resolution request, it can find the target low-Earth orbit satellite according to the pre-configured satellite selection and scheduling strategy. For example, it can select the low-Earth orbit satellite 300 that is closest to the low-Earth orbit satellite 200 where UPF 202 is located as the target low-Earth orbit satellite, and send the domain name resolution request to the cache server 302 in the low-Earth orbit satellite 300 based on the satellite network.

[0104] 2004: The cache server checks if the IP address corresponding to the target domain name is cached.

[0105] In some embodiments, when the caching server 302 receives a domain name resolution request, it can determine whether the caching server 302 has cached the IP address corresponding to the target domain name. If the caching server 302 has cached the IP address corresponding to the target domain name, it proceeds to step 2005, whereby the IP address corresponding to the target domain name can be sent to UPF 202.

[0106] If the caching server 302 does not cache the IP address corresponding to the target domain name, for example, if it has not yet updated the latest domain name and IP address from LDNS 400, resulting in the IP address corresponding to the target domain name not being cached, then it will switch to 2008, send a domain name resolution request to the ground LDNS 400, and obtain the IP address corresponding to the target domain name returned by LDNS 400.

[0107] 2005: Cache server 302 sends the IP address corresponding to the target domain name to UPF 202.

[0108] In some embodiments, when the cache server 302 has cached the IP address corresponding to the target domain name, it can send the IP address corresponding to the target domain name to the UPF 202.

[0109] In some embodiments, when the cache server 302 receives the IP address corresponding to the target domain name sent by the LDNS 400, it can send the IP address corresponding to the target domain name to the UPF 202.

[0110] 2006: UPF 202 sends the IP address corresponding to the target domain name to gNB 201.

[0111] In some embodiments, when UPF 202 receives the IP address corresponding to the target domain name, it can send the IP address corresponding to the target domain name to gNB 201.

[0112] 2007: gNB 201 sends the IP address corresponding to the target domain name to terminal device 100.

[0113] In some embodiments, when gNB 201 receives the IP address corresponding to the target domain name, it can send the IP address corresponding to the target domain name to terminal device 100.

[0114] 2008: Terminal device 100 accesses the corresponding application server 001 based on its IP address.

[0115] In some embodiments, after receiving the IP address corresponding to the target domain name, the terminal device 100 can access the corresponding application server 001 based on the IP address. In some embodiments, the terminal device 100 can access the corresponding application server 001 based on the IP address by sending an access request carrying the IP address to the gNB 201, and after receiving the access request, the gNB 201 sends an access request to the UPF 202, and after receiving the access request, the UPF 202 sends an access request to the ground gateway station 004, and the ground gateway station 004 sends an access request to the corresponding application server 001.

[0116] 2009: Cache server 302 sends a domain name resolution request to LDNS 400 on the ground.

[0117] In some embodiments, if the caching server 301 does not cache the IP address corresponding to the target domain name, for example, it has not yet updated the latest domain name and IP address from LDNS 400, resulting in the IP address corresponding to the target domain name not being cached, then a domain name resolution request is sent to the ground LDNS 400.

[0118] 2010: LDNS 400 obtains the IP address corresponding to the target domain name based on the domain name resolution request.

[0119] In some embodiments, when LDNS 400 receives a domain name resolution request, it can query the IP address corresponding to the target domain name from the data system based on the target domain name carried in the domain name resolution request.

[0120] 2011: LDNS 400 sends the IP address corresponding to the target domain name to cache server 302.

[0121] It is understandable that when LDNS 400 retrieves the IP address corresponding to the target domain name from the data system, it can send the IP address corresponding to the target domain name to the cache server 302. This allows the cache server 302 to send the IP address corresponding to the target domain name to the terminal device 100 based on the steps from 2005 to 2007.

[0122] In some embodiments, when LDNS 400 determines that the IP address of the target domain name is cached in LDNS 400, it may send the IP address of the target domain name cached in LDNS 400 to cache server 302.

[0123] In some embodiments, when the LDNS 400 determines that the IP address of the target domain name is not cached in the LDNS 400, iterative queries can be performed to obtain the IP address of the target domain name.

[0124] The iterative query process can be illustrated in Figure 4. LDNS 400 sends a domain name resolution request to root name server 401. Root name server 401 returns the IP address of the top-level name server 402 corresponding to the target domain name suffix (e.g., .com) carried in the domain name query request to LDNS 400. LDNS 400 then sends a domain name resolution request to the corresponding top-level name server 402 based on the received IP address. If the top-level name server 402 stores the IP address of the target domain name, it sends the IP address of the target domain name to LDNS 400.

[0125] If the IP address of the target domain name is not stored in the top-level domain name server 402, then the IP address of the authoritative domain name server 403 is sent to LDNS 400. LDNS 400 sends a domain name resolution request to the authoritative domain name server 403 based on the IP address of the authoritative domain name server 403, and the authoritative domain name server 403 sends the IP address of the target domain name to LDNS 400.

[0126] It can be understood that the domain name resolution request sent by terminal device 100 to LDNS 400 through cache server 302 can be regarded as a recursive query. After receiving the recursive query, LDNS 400 can perform the iterative query shown in Figure 4 when the IP address of the target domain name is not cached, and send the query result, i.e. the IP address corresponding to the target domain name, to terminal device 100.

[0127] In some embodiments, when sending a domain name resolution request to the cache server 302, the UPF 202 may also send the identification information of the satellite 200 where the UPF 202 is located. When sending a domain name resolution request to the LDNS 400, the cache server 302 carries the identification information of the satellite 200 where the UPF 202 is located.

[0128] When the ground-based LDNS 400 receives a domain name resolution request and the identification information of the low-Earth orbit satellite 200, it can also send the identification information of the low-Earth orbit satellite 200 to the application server discovery function (or ephemeris server) to obtain the network coverage information of the low-Earth orbit satellite 200 where UPF 202 is located. This network coverage information may include the location information of the ground gateway station 004 currently connected to the low-Earth orbit satellite 200. The application server discovery function server can be authorized and trusted by the operator or managed by the operator, and it can be configured with a mapping relationship between ephemeris information (such as satellite trajectory information) and satellite identification information. When the application server discovery function server 600 receives the satellite identification information of the low-Earth orbit satellite 200, it can obtain the ephemeris information of the low-Earth orbit satellite 200, determine the network coverage information of the satellite 200 based on the ephemeris information (e.g., the location information of the ground gateway station currently connected to the low-Earth orbit satellite), and then send the network coverage information to the ground-based LDNS 400. It is understandable that the network coverage area information of satellite 200 can characterize the approximate location information of terminal device 100.

[0129] The ground-based LDNS 400 can select the application server corresponding to the target domain name from multiple application servers corresponding to the target domain name based on the network coverage information on the ground. For example, the location information of the ground gateway station 004 currently connected to the low-orbit satellite 200 is the closest to the target domain name. The IP address of the closest application server is then sent to the cache server 302 as the IP address corresponding to the target domain name. In this way, the access path and latency of the terminal device 100 can be effectively shortened.

[0130] It is understood that LDNS 400 is used to handle domain name resolution requests from terminal devices within a preset range. For example, a corresponding LDNS can be deployed in the City C area to handle domain name resolution requests sent by terminal devices in the City C area. For instance, when terminal device 100 mentioned in Figures 3a and 3b is located in the City C area, the cache server 302 will send the domain name resolution request sent by terminal device 100 to the LDNS in the City C area.

[0131] In summary, in the method of obtaining the IP address corresponding to the target domain name based on the cache server, when the cache server has cached the IP address corresponding to the target domain name carried in the domain name resolution request sent by the terminal device, it can directly return the IP address corresponding to the target domain name to the terminal device, that is, it is not necessary to obtain the IP address corresponding to the target domain name from the ground LDNS every time. In this way, the number of interactions between the cache server and the ground LDNS can be reduced, saving satellite communication resources.

[0132] However, due to the limited network coverage of low-Earth orbit (LEO) satellites and their continuous orbit around the Earth, when the LDNS that a terminal device wants to access is outside the network coverage of the LEO satellite, the caching server deployed on the LEO satellite cannot communicate with the LDNS. As a result, in some cases, the caching server will be unable to obtain the IP address corresponding to the target domain name from the LDNS, leading to network access failure for the terminal device and affecting the user experience.

[0133] For example, if the terminal device 100 sending the domain name resolution request mentioned in Figure 3b is located in city C, and the network coverage of the low-Earth orbit satellite 300 is in city D, which is far from city C, then the caching server 302 on the low-Earth orbit satellite 300 will be unable to communicate with the LDNS 400 in city C. If the caching server 302 does not cache the IP address corresponding to the target domain name in the domain name resolution request sent by the terminal device 100, the caching server 302 will be unable to obtain the IP address corresponding to the target domain name from the LDNS 400, resulting in network access failure for the terminal device 100 and affecting the user experience.

[0134] To address the aforementioned issues, this application provides a communication method that deploys servers in both low-Earth orbit (LEO) satellites and geostationary satellites. For example, a secondary server is deployed in an LEO satellite, and a primary server is deployed in a geostationary satellite. When the secondary server in the LEO satellite receives a domain name resolution request from a terminal device, if it does not possess the IP address corresponding to the target domain name in the request, it forwards the request to the primary server in the geostationary satellite. The primary server in the geostationary satellite then establishes a communication connection with the ground-based LDNS (Local DNS Service) to obtain the IP address corresponding to the target domain name from the LDNS. It is understood that the network coverage area of ​​geostationary satellites is much larger than that of LEO satellites, and they operate synchronously with the Earth. Therefore, the satellite-to-ground communication link with the LDNS can maintain a near-real-time connection. Thus, by obtaining IP address data from the LDNS in real time via geostationary satellites, the occurrence of network access failures by terminal devices can be effectively reduced, improving the user experience.

[0135] It should be noted that when the primary server is deployed on a geostationary satellite, the secondary server in this embodiment can also be deployed on a low-Earth orbit (LEO) satellite or a medium-Earth orbit (MEO) satellite. In some embodiments, when the secondary server is deployed on a LEO satellite, the primary server can also be deployed on a MEO satellite. The following description uses the example of a secondary server deployed on a LEO satellite and a primary server deployed on a geostationary satellite as an example.

[0136] In some embodiments, the secondary server in the low-Earth orbit satellite and the primary server in the geostationary satellite can both cache the mapping relationship between domain names and IP addresses.

[0137] In some embodiments, the domain name and IP address information cached by the secondary server in the low-Earth orbit satellite and the primary server in the geostationary satellite are identical. When the primary server in the geostationary satellite receives a domain name resolution request from the secondary server, it forwards the request to the ground-based LDNS to obtain the IP address corresponding to the target domain name from the LDNS.

[0138] In some embodiments, both the primary server in the geostationary satellite and the secondary server in the low-Earth orbit satellite can update the domain name and the corresponding IP address from the ground-based LDNS at the same preset period (e.g., every hour) and cache them. It is understood that the preset period can be set according to actual needs, and this application does not limit the specific value of the preset period.

[0139] In some embodiments, the period during which the primary server in a geostationary satellite updates domain names and their corresponding IP addresses from the ground-based LDNS can be shorter than the period during which the secondary server in a low-Earth orbit satellite updates domain names and their corresponding IP addresses from the ground-based LDNS. Thus, the primary server may store more domain names and IP addresses than the secondary server at certain times. When the primary server in a geostationary satellite receives a domain name resolution request from the secondary server, it can determine whether the IP address corresponding to the target domain name in the domain name resolution request exists in the primary server. If not, the primary server establishes a communication connection with the ground-based LDNS to obtain the IP address corresponding to the target domain name from the LDNS; if it exists, it directly sends the IP address corresponding to the target domain name to the secondary server, which then sends the IP address corresponding to the target domain name to the terminal device.

[0140] In some embodiments, the primary server in a geostationary satellite may not cache the mapping relationship between domain names and IP addresses. When the primary server in a geostationary satellite receives a domain name resolution request from a secondary server, it forwards the request to the ground-based LDNS to obtain the IP address corresponding to the target domain name from the LDNS.

[0141] It's understandable that when a secondary server receives a domain name resolution request from a terminal device, if it stores the IP address corresponding to the target domain name carried in the request, it can directly return the IP address to the terminal device. This eliminates the need to retrieve the IP address from the terrestrial LDNS every time. This reduces the number of interactions between the caching server and the terrestrial LDNS, saving satellite communication resources.

[0142] Furthermore, when the secondary server does not store the IP address corresponding to the target domain name carried in the domain name resolution request, the domain name resolution request is forwarded to the LDNS through the primary server deployed in the geostationary satellite. The primary server obtains the IP address data from the LDNS based on the satellite-to-ground communication link (or feeder link) between the geostationary satellite and the LDNS. It can be understood that the network coverage area of ​​geostationary satellites is much larger than that of low-Earth orbit satellites, and they operate synchronously with the Earth. Therefore, the satellite-to-ground communication link with the LDNS can maintain a near-real-time connection. Thus, the primary server's ability to obtain the IP address corresponding to the target domain name in real time effectively reduces the occurrence of network access failures on the aforementioned terminal devices, improving the user experience.

[0143] It should be noted that, in this embodiment of the application, the primary server can establish a communication connection with the ground-based LDNS through the ground gateway station when the feeder link between the satellite where the primary server is located and the ground gateway station is effective (i.e., can communicate normally).

[0144] The communication methods mentioned in the embodiments of this application will be described in detail below.

[0145] It should be noted that the secondary server 203 mentioned in this application embodiment can be used as an example of the first server in this application embodiment, the primary server 501 mentioned in this application embodiment can be used as an example of the second server in this application embodiment, and the secondary server 701 mentioned in this application embodiment can be used as an example of the third server in this application embodiment.

[0146] Figure 5a illustrates a scenario of a communication method. As shown in Figure 5a, when terminal device 100 needs to query the IP address corresponding to a target domain name, if terminal device 100 is connected to a satellite network, it can send the domain name resolution request to the secondary server 203 in the low-Earth orbit satellite 200 via gNB 201 and UPF 202. When the secondary server 203 has cached the IP address corresponding to the target domain name, it can send the IP address to terminal device 100. When the secondary server 203 does not have cached the IP address, it forwards the domain name resolution request to the primary server 501 in the geostationary satellite 500. The primary server 501 in the geostationary satellite 500 establishes a communication connection with the ground-based LDNS 400 based on the ground gateway station 0032 to obtain the IP address corresponding to the target domain name from the ground-based LDNS 400 and send the obtained IP address to terminal device 100. After receiving the IP address corresponding to the target domain name, terminal device 100 accesses the corresponding application server 001 based on the IP address. It is understandable that application server 001 can update its IP address and domain name to LDNS 400.

[0147] It is understandable that geostationary satellites have a large satellite network coverage area and operate synchronously with the Earth. Therefore, the satellite-to-ground communication link with the LDNS can maintain a near-real-time connection. Thus, IP address data in the LDNS can be obtained in real time through geostationary satellites, which can effectively reduce the above-mentioned domain name resolution failures, improve the success rate of domain name resolution, reduce the number of user network access failures, and improve the user experience.

[0148] Figure 5b illustrates a flowchart of a communication method based on the scenario shown in Figure 5a. As shown in Figure 5b, the method includes:

[0149] 3001: Terminal device 100 sends a domain name resolution request to gNB 201 in low-Earth orbit satellite 200.

[0150] It is understandable that when the terminal device 100 detects a network request input by the user, it can determine that it needs to query the IP address corresponding to the target domain name carried in the network request. If the terminal device 100 is connected to a satellite network, it can send a domain name resolution request carrying the target domain name to gNB 201 in the low-Earth orbit satellite 200 through the satellite network.

[0151] In some embodiments, the domain name resolution request may carry the target domain name. For example, as shown in Figure 1 above, when a user enters a network request of Http: / / baab.com / index.abc in the browser application interface 101 of the terminal device 100, the terminal device may send a domain name resolution request carrying the target domain name "baab.com" to the LDNS.

[0152] In some embodiments, the terminal device 100 can be configured to automatically obtain the IP address of the server on the satellite to be accessed when using a satellite network. For example, the terminal device can be manually configured or configured to automatically obtain the IP address of the secondary server 203 of the low-Earth orbit satellite 200.

[0153] In some embodiments, when the terminal device 100 sends a domain name resolution request to the gNB 201 in the low-Earth orbit satellite 200, it may also send the IP address of the secondary server 203 in the low-Earth orbit satellite 200.

[0154] It should be noted that the domain name resolution request mentioned in the embodiments of this application may also be called a DNS request, DNS resolution request, DNS query request, etc., and this application does not limit it.

[0155] 3002: gNB 201 sends a domain name resolution request to UPF 202 in low-Earth orbit satellite 200.

[0156] It is understandable that when gNB 201 receives a domain name resolution request and the IP address of secondary server 203, it can route the IP address of secondary server 203 and the domain name resolution request to UPF 202 in the low-Earth orbit satellite.

[0157] 3003: UPF 202 sends a domain name resolution request to secondary server 203.

[0158] In some embodiments, when UPF 202 receives a domain name resolution request sent by gNB 201 and the IP address of secondary server 203, it can send a domain name resolution request to secondary server 203 based on the IP address of secondary server 203.

[0159] 3004: Secondary server 203 checks whether the IP address corresponding to the target domain name is cached.

[0160] In some embodiments, when a secondary server 203 receives a domain name resolution request, it can determine whether it has cached the IP address corresponding to the target domain name. If the server 203 has cached the IP address corresponding to the target domain name, the process is redirected to 3010, whereby the IP address corresponding to the target domain name can be sent to UPF 202.

[0161] If server 203 does not cache the IP address corresponding to the target domain name, the domain name resolution request can be sent to the target primary server in the geostationary satellite. In this embodiment, the target primary server is taken as primary server 501 in geostationary satellite 500 for illustration.

[0162] In some embodiments, the secondary server 203 may be pre-configured with one or more IP addresses of primary servers. When the secondary server is configured with one IP address of a primary server, the primary server corresponding to that IP address is directly used as the target primary server, and a domain name resolution request is sent to the target primary server based on that IP address. When the secondary server 203 is pre-configured with multiple IP addresses of primary servers, a target primary server can be selected based on an inter-satellite routing strategy, for example, selecting the primary server among the geostationary satellites closest to the current low-Earth orbit satellite 200 as the target primary server. The IP address of the target primary server is then obtained, and a domain name resolution request is sent to the target primary server based on that IP address.

[0163] 3005: Secondary server 203 sends a domain name resolution request to primary server 501.

[0164] In some embodiments, when the secondary server 203 determines that the server 301 has not cached the IP address corresponding to the target domain name, it sends a domain name resolution request to the primary server 501 in the geostationary satellite 500.

[0165] 3006: The primary server 501 sends a domain name resolution request to the ground-based LDNS 400.

[0166] In some embodiments, after receiving a domain name resolution request, the primary server 501 may send the domain name resolution request to the ground-based LDNS 400.

[0167] In some embodiments, both the secondary server 203 and the primary server 501 can cache the mapping relationship between domain names and IP addresses.

[0168] In some embodiments, the domain name and IP address information cached by the secondary server 203 and the primary server 501 are consistent. When the primary server 501 receives a domain name resolution request sent by the secondary server 203, the primary server 501 forwards the domain name resolution request to the ground-based LDNS 400 to obtain the IP address corresponding to the target domain name from the LDNS 400.

[0169] In some embodiments, both primary server 501 and secondary server 203 can update and cache domain names and their corresponding IP addresses from the ground-based LDNS 400 at the same preset period (e.g., every hour). It is understood that the preset period can be set according to actual needs, and this application does not limit the specific value of the preset period.

[0170] In some embodiments, the cycle for the primary server 501 to update the domain name and its corresponding IP address from the ground-based LDNS 400 can be shorter than the cycle for the secondary server 203 to update the domain name and its corresponding IP address from the ground-based LDNS 400. Thus, the primary server 501 may store more domain names and IP addresses than the secondary server 203. When the primary server 501 receives a domain name resolution request from the secondary server 203, it can determine whether the IP address corresponding to the target domain name in the domain name resolution request exists in the primary server 501. If it does not exist, the primary server 501 establishes a communication connection with the ground-based LDNS 400 to obtain the IP address corresponding to the target domain name from the LDNS 400; if it does exist, the IP address corresponding to the target domain name is directly sent to the secondary server 203, which then sends the IP address corresponding to the target domain name to the terminal device.

[0171] In some embodiments, the primary server 501 may not cache the mapping relationship between domain names and IP addresses. When the primary server 501 receives a domain name resolution request sent by the secondary server 203, the primary server 501 forwards the domain name resolution request to the ground-based LDNS 400 to obtain the IP address corresponding to the target domain name from the LDNS 400.

[0172] It is understandable that the ground coverage area of ​​the satellite network of Satellite 500 is greater than that of the satellite network of Satellite 200.

[0173] 3007: LDNS 400 retrieves the IP address corresponding to the target domain name based on the domain name resolution request.

[0174] In some embodiments, when LDNS 400 receives a domain name resolution request, it can query the IP address of the target domain name carried in the domain name resolution request.

[0175] In some embodiments, when LDNS 400 determines that the IP address of the target domain name is cached in LDNS 400, it may send the IP address of the target domain name cached in LDNS 400 to the primary server 501.

[0176] In some embodiments, when the LDNS 400 determines that the IP address of the target domain name is not cached in the LDNS 400, it can perform the iterative query mentioned in Figure 4 above to obtain the IP address of the target domain name.

[0177] It is understood that in some embodiments, there may be multiple IP addresses for the server corresponding to the target domain name. For example, when terminal device 100 detects that a user opens application A or a page within application A, it can detect a network request to access the server of application A. There may be multiple servers corresponding to application A; for example, multiple servers corresponding to application A may be deployed in city C. Therefore, there will be multiple IP addresses for the servers corresponding to application A.

[0178] Therefore, in some embodiments, when UPF202 sends a domain name resolution request to secondary server 203, it can also send the identification information of the satellite 200 where UPF202 is located. When secondary server 203 sends a domain name resolution request to primary server 501, it carries the identification information of the satellite 200 where UPF202 is located; when primary server 203 sends a domain name resolution request to LDNS 400, it carries the identification information of the satellite 200 where UPF202 is located.

[0179] As shown in Figure 6, when the ground-based LDNS 400 receives a domain name resolution request and the identification information of the low-Earth orbit satellite 200, it can also send the identification information of the low-Earth orbit satellite 200 to the application server discovery function (or ephemeris server) 600 to obtain the network coverage area information of the low-Earth orbit satellite 200 where UPF 202 is located. This network coverage area information may include the location information of the ground gateway station 004 currently connected to the low-Earth orbit satellite 200. The application server discovery function server 600 can be authorized and trusted by the operator or managed by the operator. The application server discovery function server 600 can be configured with a mapping relationship between ephemeris information (such as satellite trajectory information) and satellite identification information. When the application server discovery function server 600 receives the satellite identification information of the low-Earth orbit satellite 200, it can obtain the ephemeris information of the low-Earth orbit satellite 200 and determine the network coverage area information of the satellite 200 at that time based on the ephemeris information, such as the location information of the ground gateway station currently connected to the low-Earth orbit satellite. The satellite 200 then transmits the network coverage area information to the ground-based LDNS 400. It can be understood that the network coverage area information from satellite 200 can represent the approximate location of terminal device 100.

[0180] The ground-based LDNS 400 can select the application server corresponding to the target domain name from multiple application servers corresponding to the target domain name based on the network coverage information on the ground. For example, the location information of the ground gateway station 004 currently connected to the low-orbit satellite 200 is the closest to the target domain name. The IP address of the closest application server is then sent to the primary server 501 as the IP address corresponding to the target domain name. In this way, the access path and latency of the terminal device 100 can be effectively shortened.

[0181] 3008: LDNS 400 sends the IP address corresponding to the target domain name to the primary server 501.

[0182] In some embodiments, when LDNS 400 receives the IP address corresponding to the target domain name, it can send the IP address corresponding to the target domain name to the primary server 501.

[0183] 3009: Level 1 server 501 sends the IP address corresponding to the target domain name to Level 2 server 203.

[0184] In some embodiments, when the primary server 501 receives the IP address corresponding to the target domain name, it can send the IP address corresponding to the target domain name to the secondary server 203.

[0185] 3010: Secondary server 203 sends the IP address corresponding to the target domain name to UPF 202.

[0186] In some embodiments, when the secondary server 203 has cached the IP address corresponding to the target domain name, the IP address corresponding to the target domain name can be sent to UPF 202.

[0187] In some embodiments, when the secondary server 203 receives the IP address corresponding to the target domain name sent by the primary server 501, it can send the IP address corresponding to the target domain name to the UPF 202.

[0188] 3011: UPF 202 sends the IP address corresponding to the target domain name to gNB 201.

[0189] In some embodiments, when UPF 202 receives the IP address corresponding to the target domain name, it can send the IP address corresponding to the target domain name to gNB 201.

[0190] 3012: gNB 201 sends the IP address corresponding to the target domain name to terminal device 100.

[0191] In some embodiments, when gNB 201 receives the IP address corresponding to the target domain name, it can send the IP address corresponding to the target domain name to terminal device 100.

[0192] 3013: Terminal device 100 accesses the corresponding application server 001 based on its IP address.

[0193] In some embodiments, after receiving the IP address corresponding to the target domain name, the terminal device 100 can access the corresponding application server (AS) 001 based on the IP address. It should be noted that the application server mentioned in this embodiment can also be referred to as an application function (AF).

[0194] In some embodiments, the terminal device 100 can access the corresponding application server 001 based on the IP address by sending an access request carrying the IP address to the gNB 201. After receiving the access request, the gNB 201 sends an access request to the UPF 202. After receiving the access request, the UPF 202 sends an access request to the ground gateway station 004. The ground gateway station 004 then sends an access request to the corresponding application server 001.

[0195] In summary, based on the communication methods shown in Figures 5a and 5b, if the secondary server in the low-Earth orbit (LEO) satellite does not have the IP address corresponding to the target domain name in the domain name resolution request, the LEO satellite's secondary server forwards the domain name resolution request to the primary server in the geostationary satellite. The primary server in the geostationary satellite then establishes a communication connection with the ground-based LDNS to obtain the IP address corresponding to the target domain name from the LDNS. It can be understood that the geostationary satellite network has a large coverage area and operates synchronously with the Earth. Therefore, the satellite-to-ground communication link with the LDNS can maintain a near-real-time power supply connection. Thus, by obtaining IP address data from the LDNS in real time through the geostationary satellite, the success rate and reliability of domain name resolution requests can be effectively improved, reducing network access failures of the aforementioned terminal devices and enhancing the user experience.

[0196] Furthermore, based on the communication methods shown in Figures 5a and 5b, the application server corresponding to the target domain name that is closest to the coverage area of ​​the low-orbit satellite 200 can be selected based on the network coverage location information of the access satellite of the terminal device, such as the low-orbit satellite 200 mentioned above. The IP address of the nearest application server is then sent to the terminal device as the IP address corresponding to the target domain name. In this way, the access path and latency of the terminal device can be effectively shortened.

[0197] In some embodiments, the secondary server in the low-Earth orbit (LEO) satellite can further classify domain name resolution requests and perform different operations on different types of requests. For a first-type domain name resolution request (e.g., a request to access a server corresponding to a first-type application), if the secondary server in the LEO satellite does not have the IP address corresponding to the target domain name in the request, it forwards the request to the primary server in the geostationary satellite. For a second-type domain name resolution request (e.g., a request to access a server corresponding to a second-type application), if the secondary server in the LEO satellite does not have the IP address corresponding to the target domain name in the request, it directly returns a resolution failure message to the terminal device, i.e., it does not forward the request to the primary server in the geostationary satellite. This reduces data transmission between the geostationary satellite and the ground, thus reducing the consumption of satellite resources.

[0198] Figure 7 illustrates a communication method using an example of a secondary server in a low-Earth orbit satellite performing different operations on different types of domain name resolution requests. The method includes:

[0199] 4001: Terminal device 100 sends a domain name resolution request to gNB 201 in low-Earth orbit satellite 200.

[0200] 4002: gNB 201 sends a domain name resolution request to UPF 202 in low-Earth orbit satellite 200.

[0201] It should be noted that the content of 4001-4002 is similar to that of 3001-3002, and will not be described again in the embodiments of this application.

[0202] 4003: UPF 202 sends a domain name resolution request to secondary server 203.

[0203] In some embodiments, when UPF 202 receives a domain name resolution request sent by gNB 201 and the IP address of secondary server 203, it can send a domain name resolution request to secondary server 203 based on the IP address of secondary server 203.

[0204] In some embodiments, when the UPF202 receives a domain name resolution request from the terminal device 100, it can also determine the application that sent the domain name resolution request based on the target domain name. It can be understood that the server name corresponding to the domain name is the name of the application server corresponding to the application. Therefore, the application that sent the domain name resolution request, or the application corresponding to the target domain name, can be determined based on the server name corresponding to the domain name.

[0205] Then, UPF 202 determines the application category based on the application's associated contract information and / or user plane traffic splitting rules, and marks the domain name resolution request with a different identifier based on the application category. UPF 202 can then send the domain name resolution request and the corresponding identifier to the secondary server 203.

[0206] For example, when the UPF202 receives a domain name resolution request sent by the gNB 201, it identifies the domain name in the domain name resolution request, matches and executes the user plane traffic splitting rules / N4 session rules. This can also be understood as performing rule detection on the domain name resolution request data packet. That is, the UPF202 obtains application subscription information and / or user plane forwarding rule information. The UPF202 can determine the application category based on the application subscription data and / or user plane forwarding rule information, and mark the domain name resolution request with different identifiers.

[0207] For example, when an application is determined to be a first-type application based on the application-associated contract information and / or user plane forwarding rule information, the domain name resolution request is determined to be a first-type domain name resolution request, and a first identifier is marked on the domain name resolution request; when an application is determined to be a second-type application based on the application-associated contract information and / or user plane forwarding rule information, the domain name resolution request is determined to be a second-type domain name resolution request, and a second identifier is marked on the domain name resolution request; when an application is determined to be a third-type application based on the application-associated contract information and / or user plane forwarding rule information, the domain name resolution request is determined to be a third-type domain name resolution request, then no domain name resolution is performed on the domain name resolution request, and a resolution failure message is directly returned to the terminal device 100.

[0208] The first category of applications can be those associated with first-type contract information and / or first-type user plane forwarding rule information, indicating that the service provider of the first-type application has signed a first agreement with the network operator. The second category of applications can be those associated with second-type contract information and / or second-type user plane forwarding rule information, indicating that the service provider of the application has signed a second agreement with the network operator. The third category of applications can be those not associated with contract information and / or user plane forwarding rule information, for example, if the application's service provider has not signed an agreement with the network operator; in this case, the application is not allowed to use DNS resolution services.

[0209] In some embodiments, UPF202 can also determine the user plane forwarding rule information corresponding to the domain name based on the domain name in the domain name resolution request, and determine the category of the domain name resolution request based on the user plane forwarding rule information corresponding to the domain name. That is, the domain name and the user plane forwarding rule information have a corresponding association. For example, if the user plane forwarding rule information corresponding to the domain name is determined to be the first type of user plane forwarding rule information, then the domain name resolution request is determined to be the first type of domain name resolution request; if the user plane forwarding rule information corresponding to the domain name is determined to be the second type of user plane forwarding rule information, then the domain name resolution request is determined to be the second type of domain name resolution request.

[0210] In some embodiments, UPF 202 can be used to communicate with network elements of the terrestrial core network, such as policy control function (PCF) and session management function (SMF), to obtain subscription information and user plane forwarding rule information associated with each application from network elements of the terrestrial core network such as SMF and PCF.

[0211] It should be noted that the above classification method is only an example, and this application does not limit the classification method of domain name resolution requests.

[0212] 4004: Secondary server 203 checks whether the IP address corresponding to the target domain name is cached.

[0213] In some embodiments, when a secondary server 203 receives a domain name resolution request, it can determine whether it has cached the IP address corresponding to the target domain name. If the secondary server 203 has cached the IP address corresponding to the target domain name, it will proceed to step 4010, whereby the IP address corresponding to the target domain name can be sent to UPF 202.

[0214] In some embodiments, if the secondary server 203 does not cache the IP address corresponding to the target domain name, it can be redirected to 40051, where the secondary server 203 determines whether the domain name resolution request is a first type of domain name resolution request.

[0215] In some embodiments, the secondary server 203 and the primary server 501 can update the domain name and the corresponding IP address from the ground-based LDNS400 according to a preset period (e.g., every hour) and cache them.

[0216] 40051: Secondary server 203 checks whether the domain name resolution request is a first-class domain name resolution request.

[0217] If the secondary server 203 determines that the domain name resolution request is a first-class domain name resolution request, it means that a domain name resolution request needs to be sent to the primary server 501. Then, it is transferred to 4005, and the secondary server 203 sends the domain name resolution request to the primary server 501 in the geostationary satellite 500.

[0218] If the secondary server 203 determines that the domain name resolution request is a type II domain name resolution request, it means that it does not need to send a domain name resolution request to the primary server 501. Therefore, it forwards the request to 40052 and sends a resolution failure message to UPF 202, so that UPF 202 can send the resolution failure message to the terminal device. The resolution failure message may include the reason for the resolution failure, such as the secondary server 203 being unable to resolve the request. In some embodiments, the reason for the resolution failure may also be in the form of an identifier, characters, or numbers.

[0219] For example, when the identifier corresponding to the domain name resolution request is a type 1 identifier, the secondary server 203 determines whether the domain name resolution request is a type 1 domain name resolution request and, if so, forwards it to the primary server 501 in the geostationary satellite 500. When the identifier corresponding to the domain name resolution request is a type 2 identifier, it is determined to be a type 2 domain name resolution request. For type 2 domain name resolution requests, a resolution failure message is directly returned to the terminal device 100, meaning the domain name resolution request is not forwarded to the primary server 501 in the geostationary satellite 500. This reduces data transmission between the geostationary satellite and the ground, thus reducing the consumption of satellite resources.

[0220] It should be noted that the resolution failure information mentioned in the embodiments of this application may also be referred to as DNS resolution failure response, DNS query failure response, DNS resolution response, DNS query response, etc., and the embodiments of this application do not limit it.

[0221] 40052: Secondary server 203 sent a parsing failure message to UPF 202.

[0222] 40053: UPF 202 sends a parsing failure message to gNB 201.

[0223] In some embodiments, when UPF 202 receives a parsing failure message, it can send the parsing failure message to gNB 201.

[0224] 40054: gNB 201 sends a parsing failure message to terminal device 100.

[0225] In some embodiments, when gNB 201 receives a parsing failure message, it can send the parsing failure message to terminal device 100.

[0226] It should be noted that the steps for 4005-4013 are similar to those for 3005-3013, and will not be repeated below.

[0227] 4005: Secondary server 203 sends a domain name resolution request to primary server 501 in geostationary satellite 500.

[0228] 4006: The primary server 501 sends a domain name resolution request to the ground-based LDNS.

[0229] 4007: LDNS obtains the IP address corresponding to the target domain name based on the domain name resolution request.

[0230] 4008: LDNS sends the IP address corresponding to the target domain name to the primary server via 501.

[0231] 4009: Level 1 server 501 sends the IP address corresponding to the target domain name to Level 2 server 203.

[0232] 4010: Secondary server 203 sends the IP address corresponding to the target domain name to UPF 202.

[0233] 4011: UPF 202 sends the IP address corresponding to the target domain name to gNB 201.

[0234] 4012: gNB 201 sends the IP address corresponding to the target domain name to terminal device 100.

[0235] 4013: Terminal device 100 accesses the server 001 of the corresponding application based on the IP address.

[0236] In summary, based on the communication method shown in Figure 7, classifying domain name resolution requests can reduce data transmission between geostationary satellites and the ground, thereby reducing the consumption of satellite resources.

[0237] It is understood that, based on the communication method shown in Figure 7, the secondary server 203 determines whether the domain name resolution request is sent to the primary server 501. In some embodiments, the determination of whether the domain name resolution request is sent to the primary server 501 can also be made by the UPF 202.

[0238] That is, when receiving a domain name resolution request, UPF 202 can determine whether the domain name resolution request is a first-type domain name resolution request based on the classification method of domain name resolution requests in step 4003, and directly send the domain name resolution request to the primary server 501. When the domain name resolution request is a second-type domain name resolution request, it will send the domain name resolution request to the secondary server 203. When receiving a domain name resolution request, if the secondary server 203 determines that it does not have the IP address corresponding to the target domain name in the domain name resolution request, it will directly return a resolution failure message to the terminal device 100 based on UPF 202 and gNB 201. If it determines that the secondary server 203 has the IP address corresponding to the target domain name in the domain name resolution request, it will directly return the IP address corresponding to the target domain name to the terminal device 100 based on UPF 202 and gNB 201.

[0239] It is understandable that the primary server 501 can store domain names and IP addresses. When the primary server 501 receives a domain name resolution request sent by the UPF 202, it can determine whether the IP address corresponding to the target domain name in the domain name resolution request exists in the primary server 501. If it does not exist, the primary server 203 establishes a communication connection with the ground-based LDNS 400 to obtain the IP address corresponding to the target domain name from the LDNS 400; if it exists, the IP address corresponding to the target domain name is directly sent to the terminal device 100 based on the UPF 202 and gNB 201.

[0240] In some embodiments, the primary server 501 may not cache the mapping relationship between domain names and IP addresses. When the primary server 501 receives a domain name resolution request, it forwards the domain name resolution request to the ground-based LDNS 400 to obtain the IP address corresponding to the target domain name from the LDNS 400, and sends the IP address corresponding to the target domain name to the terminal device 100 based on UPF 202 and gNB 201.

[0241] In some embodiments, when there is no inter-satellite routing path between the low-Earth orbit satellite 200 where the secondary server 203 is located and the geostationary satellite 500, that is, the secondary server 203 and the primary server cannot directly establish a communication connection. The secondary server 203 can query the auxiliary satellites in the constellation where the low-Earth orbit satellite 200 is located that have an inter-satellite path with the geostationary satellite 500, and forward the domain name resolution request to the primary server 501 in the geostationary satellite 500 through the auxiliary satellites.

[0242] Figure 8a illustrates a scenario where a secondary server 203 forwards a domain name resolution request to a primary server 501 via an auxiliary satellite 700 within constellation 002. As shown in Figure 8a, when there is no inter-satellite routing path between the low-Earth orbit satellite 200 where the secondary server 203 resides and the geostationary satellite 300, the secondary server 203, upon determining that an inter-satellite routing path exists between satellite 700 (the auxiliary satellite) and the geostationary satellite 300, can send the domain name resolution request to the secondary server 701 within satellite 700. The secondary server 701 then forwards the domain name resolution request to the primary server 501 within the geostationary satellite 500.

[0243] In some embodiments, as shown in FIG8b, UPF 202 and gNB 201 can be deployed on different satellites as the secondary server 203. For example, UPF 202 and gNB 201 are deployed on LEO satellite 200, and the secondary server 203 is deployed on LEO satellite 200-1. This application does not impose any limitations.

[0244] Figure 8c illustrates a flowchart of a communication method based on the scenario shown in Figure 8a. As shown in Figure 8c, the method includes:

[0245] 5001: Terminal device 100 sends a domain name resolution request to gNB 201 in low-Earth orbit satellite 200.

[0246] 5002: gNB 201 sends a domain name resolution request to UPF 202 in low-Earth orbit satellite 200.

[0247] 5003: UPF 202 sends a domain name resolution request to secondary server 203.

[0248] 5004: Secondary server 203 checks whether the IP address corresponding to the target domain name is cached.

[0249] It should be noted that the steps for 5001-5004 can be referred to the steps for 3001-3004, or the steps for 4001-40055, which will not be repeated here.

[0250] 50051: Secondary server 203 determines whether there is a routing path between secondary server 203 and primary server 501 in geostationary satellite 500.

[0251] In some embodiments, if the secondary server 203 determines that there is a routing path between the secondary server 203 and the primary server 501 in the geostationary satellite 500, it will switch to 5005 and send a domain name resolution request to the primary server 501 in the geostationary satellite 500.

[0252] In some embodiments, if the secondary server 203 determines that there is no routing path between the secondary server 203 and the primary server 501 in the geostationary satellite 500, it switches to 50052, and the secondary server 203 obtains the secondary server 701 that has a routing path with the primary server 501 in the geostationary satellite 500.

[0253] It is understandable that when secondary server 203 determines that an inter-satellite routing path exists between satellite 200 and satellite 500, it also determines that a routing path exists between secondary server 203 in satellite 200 and primary server 501 in satellite 500, meaning that secondary server 203 and primary server 501 can communicate. Conversely, when secondary server 203 determines that no inter-satellite routing path exists between satellite 200 and satellite 500, it also determines that no routing path exists between secondary server 203 in satellite 200 and primary server 501 in satellite 500, meaning that secondary server 203 and primary server 501 cannot communicate.

[0254] 50052: Secondary server 203 obtains a routing path from primary server 501 in geostationary satellite 500 to secondary server 701.

[0255] In some embodiments, the secondary server 203 may sequentially send link query requests to other satellites in constellation 002 (e.g., processors in other satellites), and the link query requests may carry the identification information of satellite 500. A satellite receiving a link query request can query whether an inter-satellite routing path exists with satellite 500. If it exists, it returns a presence response to the secondary server 203. If it does not exist, it returns a absence response to the secondary server 203. When the secondary server 203 receives a presence response for the first time, for example, when it receives a presence response from satellite 700, it stops sending link query requests to other satellites and sends a domain name resolution request to the secondary server 203 in satellite 700.

[0256] It is understandable that satellites belonging to the same constellation have inter-satellite links (ISLs), which are inter-satellite routing paths. Different constellations must have at least one inter-satellite link to ensure that satellites in different constellations can communicate with each other.

[0257] 50053: Secondary server 203 sends a domain name resolution request to secondary server 701.

[0258] 50054: Secondary server 701 sends a domain name resolution request to primary server 501 in geostationary satellite 500.

[0259] In some embodiments, when the secondary server 701 receives a domain name resolution request, it sends the domain name resolution request to the primary server 501 in the geostationary satellite 500.

[0260] It should be noted that the steps for 5005-5013 can be referred to the steps for 3005-3013, and will not be repeated here.

[0261] 5005: Secondary server 203 sends a domain name resolution request to primary server 501 in geostationary satellite 500.

[0262] 5006: The primary server 501 sends a domain name resolution request to the ground-based LDNS.

[0263] 5007: LDNS obtains the IP address corresponding to the target domain name based on the domain name resolution request.

[0264] 5008: LDNS sends the IP address corresponding to the target domain name to the primary server 501.

[0265] 5009: Level 1 server 501 sends the IP address corresponding to the target domain name to Level 2 server 203.

[0266] In some embodiments, when there is no routing path between the primary server 501 and the secondary server 203, the primary server 501 sends the IP address corresponding to the target domain name to the secondary server 701, and the secondary server 701 sends the IP address corresponding to the target domain name to the secondary server 203.

[0267] In some embodiments, when there is a routing path between the primary server 501 and the secondary server 203, the primary server 501 sends the IP address corresponding to the target domain name to the secondary server 203 through the routing path.

[0268] 5010: Secondary server 203 sends the IP address corresponding to the target domain name to UPF 202.

[0269] 5011: UPF 202 sends the IP address corresponding to the target domain name to gNB 201.

[0270] 5012: gNB 201 sends the IP address corresponding to the target domain name to terminal device 100.

[0271] 5013: Terminal device 100 accesses the server 001 of the corresponding application based on the IP address.

[0272] In summary, based on the communication methods shown in Figures 8a and 8b, when there is no inter-satellite routing path between the low-Earth orbit satellite 200 (where the secondary server 203 is located) and the geostationary satellite 500, the secondary server 203, upon determining that an inter-satellite routing path exists between satellite 700 and the geostationary satellite 500, can send the domain name resolution request to server 701 on satellite 700. Server 701 then forwards the domain name resolution request to the primary server 501 on geostationary satellite 500. This ensures a high success rate for domain name resolution requests, reduces the number of network access failures for users, and improves user experience.

[0273] In summary, based on the communication method in this application embodiment, if the secondary server in the low-Earth orbit satellite does not have the IP address corresponding to the target domain name in the domain name resolution request, the secondary server in the low-Earth orbit satellite forwards the domain name resolution request to the primary server in the geostationary satellite. The primary server in the geostationary satellite then establishes a communication connection with the ground-based LDNS to obtain the IP address corresponding to the target domain name from the LDNS. It can be understood that the geostationary satellite network has a large coverage area and operates synchronously with the Earth. Therefore, the satellite-to-ground communication link with the LDNS can maintain a near-real-time power supply connection. Thus, by obtaining IP address data from the LDNS in real time through the geostationary satellite, the success rate and reliability of domain name resolution requests can be effectively improved, reducing the occurrence of network access failures for the aforementioned terminal devices and enhancing the user experience.

[0274] Furthermore, based on the communication method in this application embodiment, the terminal device can select the application server corresponding to the target domain name that is closest to the coverage geographical range of the low-orbit satellite 200 based on the network coverage location information of the access satellite, such as the low-orbit satellite 200 mentioned above, and send the IP address of the nearest application server as the IP address corresponding to the target domain name to the terminal device. In this way, the access path and latency of the terminal device can be effectively shortened.

[0275] Furthermore, based on the communication method in this application embodiment, by classifying domain name resolution requests, the data transmission between geostationary satellites and the ground can be reduced, thereby reducing the consumption of satellite resources.

[0276] Figure 9 illustrates a flowchart of a communication method based on the scenario shown in Figure 8a, which requires relaying domain name resolution requests via auxiliary satellites, combined with a scenario involving the classification of domain name resolution requests. As shown in Figure 9, the method includes:

[0277] 6001: Terminal device 100 sends a domain name resolution request to gNB 201 in low-Earth orbit satellite 200.

[0278] 6002: gNB 201 sends a domain name resolution request to UPF 202 in low-Earth orbit satellite 200.

[0279] 6003: UPF 202 sends a domain name resolution request to secondary server 203.

[0280] 6004: Secondary server 203 checks whether the IP address corresponding to the target domain name is cached.

[0281] 60051: Secondary server 203 checks whether the domain name resolution request is a first-class domain name resolution request.

[0282] 60052: Secondary server 203 sent a parsing failure message to UPF 202.

[0283] 60053: UPF 202 sends a parsing failure message to gNB 201.

[0284] 60054: gNB 201 sends a parsing failure message to terminal device 100.

[0285] 60055: Secondary server 203 determines whether there is a routing path between secondary server 203 and primary server 501 in geostationary satellite 500.

[0286] It should be noted that steps 6001-60033 and steps 4001-40055 will not be repeated here.

[0287] 60056: Secondary server 203 obtains a routing path from primary server 501 in geostationary satellite 500 to secondary server 701.

[0288] 60057: Secondary server 203 sends a domain name resolution request to secondary server 701.

[0289] 60058: Secondary server 701 sends a domain name resolution request to primary server 501 in geostationary satellite 500.

[0290] 6005: Secondary server 203 sends a domain name resolution request to primary server 501 in geostationary satellite 500.

[0291] 6006: The primary server 501 sends a domain name resolution request to the ground-based LDNS.

[0292] 6007: LDNS obtains the IP address corresponding to the target domain name based on the domain name resolution request.

[0293] 6008: LDNS sends the IP address corresponding to the target domain name to the primary server 501.

[0294] 6009: Level 1 server 501 sends the IP address corresponding to the target domain name to Level 2 server 203.

[0295] 6010: Secondary server 203 sends the IP address corresponding to the target domain name to UPF 202.

[0296] 6011: UPF 202 sends the IP address corresponding to the target domain name to gNB 201.

[0297] 6012: gNB 201 sends the IP address corresponding to the target domain name to terminal device 100.

[0298] 6013: Terminal device 100 accesses the server 001 of the corresponding application based on the IP address.

[0299] It should be noted that the steps for 60056-6013 and 50051-5013 will not be repeated here.

[0300] Figure 10 illustrates a flowchart of a communication method according to an embodiment of this application. As shown in Figure 10, the communication method includes:

[0301] 7001: The terminal device sends a domain name resolution request corresponding to the first domain name to the first server.

[0302] In some embodiments, the first server is deployed on the first satellite, the first satellite operates in the first Earth orbit, the domain name resolution request includes the first domain name, and the first server stores the mapping relationship between the domain name and the IP address.

[0303] The first server may be the secondary server 203 mentioned in the embodiments of this application. The first satellite may refer to the low-Earth orbit satellite 200 or low-Earth orbit satellite 200-1 mentioned in the embodiments of this application.

[0304] In some embodiments, the terminal device may send a domain name resolution request corresponding to the first domain name to the first server in a manner that refers to steps 3001-3003 or steps 5001-5003.

[0305] 7002: The first server checks whether the IP address corresponding to the first domain name is stored.

[0306] In some embodiments, the first server may determine whether an IP address corresponding to the first domain name is stored based on the domain name-IP address mapping stored on the first server. The method by which the first server determines whether an IP address corresponding to the first domain name is stored can refer to step 3004.

[0307] If the first server determines that it has stored the IP address corresponding to the target domain name, it will switch to 7008, and the second server will send the first IP address to the terminal device.

[0308] If the first server determines that it has not stored the IP address corresponding to the target domain name, it will switch to 7003 and send a domain name resolution request to the second server.

[0309] In some embodiments, the second server may be the secondary server 203 mentioned in the embodiments of this application.

[0310] 7003: The first server sends a domain name resolution request to the second server.

[0311] The second server is deployed on the second satellite, which operates in a second Earth orbit, which is higher than the first Earth orbit.

[0312] In some embodiments, the second satellite may be satellite 500 as mentioned in the embodiments of this application, and the second Earth orbit may be a high Earth orbit as mentioned in the embodiments of this application. The ground coverage area of ​​the satellite network of the second satellite is greater than the ground coverage area of ​​the satellite network of the first satellite.

[0313] In some embodiments, the method by which the first server sends a domain name resolution request to the second server can be found in steps 3005, 50051-5005, and 40051-4005.

[0314] 7004: The second server sends a domain name resolution request to the local domain name server.

[0315] In some embodiments, the method by which the second server sends a domain name resolution request to the local domain name server can be found in step 3006.

[0316] In some embodiments, the local domain name server may be the LDNS 500 mentioned in the embodiments of this application.

[0317] 7005: The local domain name server obtains the first IP address corresponding to the first domain name based on the domain name resolution request.

[0318] In some embodiments, the method by which the local domain name server obtains the first IP address corresponding to the first domain name based on the domain name resolution request can be found in step 3007.

[0319] 7006: The local domain name server sends the first IP address to the second server.

[0320] In some embodiments, the method by which the local domain name server sends the first IP address to the second server can be found in 3008.

[0321] 7007: The second server sends the first IP address to the first server.

[0322] 7008: The first server sends the first IP address to the terminal device.

[0323] In some embodiments, the method by which the second server sends the first IP address to the terminal device can be found in 3009-3012 and 5008-5012.

[0324] In summary, based on the communication method in this application embodiment, if the secondary server in the low-Earth orbit satellite does not have the IP address corresponding to the target domain name in the domain name resolution request, the secondary server in the low-Earth orbit satellite forwards the domain name resolution request to the primary server in the geostationary satellite. The primary server in the geostationary satellite then establishes a communication connection with the ground-based LDNS to obtain the IP address corresponding to the target domain name from the LDNS. It can be understood that the geostationary satellite network has a large coverage area and operates synchronously with the Earth. Therefore, the satellite-to-ground communication link with the LDNS can maintain a near-real-time feeder connection. Thus, by obtaining IP address data from the LDNS in real time through the geostationary satellite, the success rate and reliability of domain name resolution requests can be effectively improved, reducing the occurrence of network access failures for the aforementioned terminal devices and enhancing the user experience.

[0325] Furthermore, based on the communication method in this application embodiment, the terminal device can select the application server corresponding to the target domain name that is closest to the coverage geographical range of the low-orbit satellite 200 based on the network coverage location information of the access satellite, such as the low-orbit satellite 200 mentioned above, and send the IP address of the nearest application server as the IP address corresponding to the target domain name to the terminal device. In this way, the access path and latency of the terminal device can be effectively shortened.

[0326] Furthermore, based on the communication method in this application embodiment, by classifying domain name resolution requests, the data transmission between geostationary satellites and the ground can be reduced, thereby reducing the consumption of satellite resources.

[0327] In some embodiments, the communication method mentioned in this application can be used in a communication system, which includes a ground system and a satellite system. The ground system includes terminal equipment, local domain name servers, ground gateway stations, and other equipment. The satellite system includes a first server, a second server, a UPF, a gNB, and other equipment. The first server is deployed on a first satellite, which operates in a first Earth orbit. The second server is deployed on a second satellite, which operates in a second Earth orbit, which is higher than the first Earth orbit.

[0328] This application provides a satellite system including a first server, a second server, a UPF, a gNB, and other devices mentioned in the embodiments of this application. The satellite system provided in this application can execute the communication methods performed by the devices in the satellite system of this application.

[0329] It should be noted that the methods and features in the embodiments of this application can be combined in any form, that is, the embodiments formed by combining the methods and features in the embodiments of this application in any form are all within the protection scope of the embodiments of this application.

[0330] The structure of the terminal device 100, the primary server 203, the secondary server 501, and the LDNS 400 mentioned in the embodiments of this application will be described below.

[0331] Figure 11 shows a schematic diagram of the structure of a terminal device 100. As shown in Figure 11, the terminal device 100 may include a processor 110, a power module 140, a memory 180, a mobile communication module 130, a wireless communication module 120, a sensor module 190, an audio module 150, a camera 170, an interface module 160, buttons 101, and a display screen 102, etc.

[0332] Figure 12 illustrates a schematic diagram of a server structure. The server shown in Figure 12 can be the structure of the primary server 501, secondary server 203, or LDNS 400 mentioned in the embodiments of this application.

[0333] In one embodiment, server 1200 may include one or more processors 1204, system control logic 1208 connected to at least one of the processors 1204, system memory 1212 connected to system control logic 1208, non-volatile memory (NVM) 1216 connected to system control logic 1208, and network interface 1220 connected to system control logic 1208.

[0334] In some embodiments, processor 1204 may include one or more single-core or multi-core processors. In some embodiments, processor 1204 may include any combination of general-purpose processors and special-purpose processors (e.g., graphics processors, application processors, baseband processors, etc.). In embodiments where server 1200 employs eNB (Evolved Node B) 101 or RAN (Radio Access Network) controller 102, processor 1204 may be configured to perform various conforming embodiments, for example, it may be used to perform the methods required by primary server 501, secondary server 203, or LDNS 400 in the embodiments of this application.

[0335] This application provides a computer-readable storage medium storing executable instructions, which, when executed on an electronic device, implement the communication method provided in this application.

[0336] This application provides an electronic device, including: a memory for storing instructions executed by one or more processors of the electronic device, and one or more processors for executing the communication method provided in this application.

[0337] The various embodiments of the mechanisms disclosed in this application can be implemented in hardware, software, firmware, or a combination of these implementation methods. Embodiments of this application can be implemented as computer programs or program code executable on a programmable system, the programmable system including at least one processor, a storage system (including volatile and non-volatile memory and / or storage elements), at least one input device, and at least one output device.

[0338] Program code can be applied to input instructions to execute the functions described in this application and generate output information. The output information can be applied to one or more output devices in a known manner. For the purposes of this application, the processing system includes any system having a processor such as, for example, a digital signal processor (DSP), a microcontroller, an application-specific integrated circuit (ASIC), or a microprocessor.

[0339] The program code can be implemented using a high-level procedural language or an object-oriented programming language to communicate with the processing system. Assembly language or machine language can also be used when needed. In fact, the mechanisms described in this application are not limited to any particular programming language. In either case, the language can be a compiled language or an interpreted language.

[0340] In some cases, the disclosed embodiments may be implemented in hardware, firmware, software, or any combination thereof. The disclosed embodiments may also be implemented as instructions carried or stored thereon on one or more temporary or non-temporary machine-readable (e.g., computer-readable) storage media, which may be read and executed by one or more processors. For example, the instructions may be distributed via a network or through other computer-readable media. Therefore, machine-readable media may include any mechanism for storing or transmitting information in a machine-readable (e.g., computer-readable) form, including but not limited to floppy disks, optical disks, CD-ROMs, magneto-optical disks, read-only memory (ROM), random access memory (RAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic cards or optical cards, flash memory, or tangible machine-readable storage for transmitting information (e.g., carrier waves, infrared signals, digital signals, etc.) using the Internet in the form of electrical, optical, acoustic, or other propagation signals. Therefore, machine-readable media include any type of machine-readable medium suitable for storing or transmitting electronic instructions or information in a machine-readable (e.g., computer-readable) form.

[0341] In the accompanying drawings, some structural or methodological features may be shown in a specific arrangement and / or order. However, it should be understood that such a specific arrangement and / or order may not be necessary. Rather, in some embodiments, these features may be arranged in a manner and / or order different from that shown in the illustrative drawings. Furthermore, the inclusion of structural or methodological features in a particular figure does not imply that such features are required in all embodiments, and in some embodiments, these features may be omitted or may be combined with other features.

[0342] It should be noted that all units / modules mentioned in the device embodiments of this application are logical units / modules. Physically, a logical unit / module can be a physical unit / module, a part of a physical unit / module, or a combination of multiple physical units / modules. The physical implementation of these logical units / modules themselves is not the most important factor; the combination of functions implemented by these logical units / modules is the key to solving the technical problems proposed in this application. Furthermore, to highlight the innovative aspects of this application, the above-described device embodiments of this application have not introduced units / modules that are not closely related to solving the technical problems proposed in this application. This does not mean that the above-described device embodiments do not contain other units / modules.

[0343] It should be noted that in the examples and description of this patent, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one" does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0344] Although this application has been illustrated and described with reference to certain preferred embodiments thereof, those skilled in the art should understand that various changes in form and detail may be made thereto without departing from the spirit and scope of this application.

Claims

A communication method characterized by comprising: For use in a satellite system, the satellite system includes a first server and a second server, the first server being deployed on a first satellite, the first satellite operating in a first Earth orbit, the second server being deployed on a second satellite, the second satellite operating in a second Earth orbit, the second Earth orbit being higher than the first Earth orbit; The method includes: The first server receives a first domain name resolution request sent by a terminal device in the ground system. The first domain name resolution request includes a first domain name that the terminal device requests to resolve. The first server stores a mapping relationship between domain names and IP addresses. When the first server determines, based on the mapping relationship between the domain name and the IP address, that the first server does not store the first IP address corresponding to the first domain name, the first server sends the first domain name resolution request to the second server. The first server sending the first domain name resolution request to the second server includes: the first server identifying the first domain name resolution request as a first type of domain name resolution request and sending the first domain name resolution request to the second server. The classification of the first domain name resolution request is determined based on the contract information and / or user plane forwarding rule information corresponding to the application corresponding to the first domain name. Based on the domain name and IP address mapping relationship stored in the second server, the second server determines that the first IP address corresponding to the first domain name is not stored in the second server, and sends the first domain name resolution request to the local domain name server in the ground system. The period during which the second server updates the domain name and IP address mapping relationship from the local domain name server is less than or equal to the period during which the first server updates the domain name and IP address mapping relationship from the local domain name server. The second server receives the first IP address corresponding to the first domain name sent by the local domain name server; The second server sends the first IP address to the first server; The first server sends the first IP address to the terminal device. The communication method according to claim 1, characterized in that The satellite system also includes a User Plane Function (UPF); The first server receives a first domain name resolution request sent by a terminal device in the ground system, including: The User Plane Function (UPF) receives the first domain name resolution request sent by the terminal device in the ground system; The User Plane Function (UPF) determines that the first domain name resolution request is a first type of domain name resolution request based on the first domain name in the first domain name resolution request, marks the first domain name resolution request with a first identifier, and sends the first domain name resolution request and the first identifier to the first server. The communication method according to claim 2 is characterized in that, The User Plane Function (UPF) determines that the first domain name resolution request is the first type of domain name resolution request based on the first domain name in the first domain name resolution request, including: The User Plane Function (UPF) determines the application corresponding to the first domain name based on the first domain name in the first domain name resolution request, and obtains the contract information and / or user plane forwarding rule information corresponding to the application corresponding to the first domain name. Based on the contract information and / or user plane forwarding rule information corresponding to the application corresponding to the first domain name, it determines that the first domain name resolution request is a first type of domain name resolution request; or, The User Plane Function (UPF) obtains the user plane forwarding rule information corresponding to the first domain name based on the first domain name in the first domain name resolution request, and determines the first domain name resolution request as the first type of domain name resolution request based on the user plane forwarding rule information corresponding to the first domain name. The communication method according to claim 1 is characterized in that, The first server identifies the first domain name resolution request as a first type of domain name resolution request, including: The first server receives the first domain name resolution request and the first identifier sent by the User Plane Function (UPF), and identifies the first domain name resolution request as the first type of domain name resolution request based on the first identifier. The communication method according to any one of claims 1-4 is characterized in that, The method further includes: The first server receives a second domain name resolution request sent by the terminal device, the second domain name resolution request including the second domain name that the terminal device requests to resolve; When the first server determines, based on the mapping relationship between the domain name and the IP address, that the first server does not store the second IP address corresponding to the second domain name, and identifies the second domain name resolution request as a second type of domain name resolution request, it sends a resolution failure message to the terminal device. The communication method according to claim 5 is characterized in that, The first server receives a second domain name resolution request sent by the terminal device, including: The User Plane Function (UPF) receives the second domain name resolution request sent by the terminal device; The User Plane Function (UPF) determines that the second domain name resolution request is a second type of domain name resolution request based on the second domain name in the second domain name resolution request, marks the second domain name resolution request with a second identifier, and sends the second domain name resolution request and the second identifier to the first server. The communication method according to any one of claims 1-4 is characterized in that, The satellite system also includes a third server, which is deployed on the third satellite. The third satellite and the first satellite are located in the same constellation, and there is an inter-satellite routing path between the third satellite and the second satellite. The first server sends the first domain name resolution request to the second server, including: The first server determines that there is no inter-satellite routing path between the first satellite and the second satellite, and then sends the first domain name resolution request to the third server. The third server then sends the first domain name resolution request to the second server. The communication method according to any one of claims 1-4 is characterized in that, The ground system also includes an ephemeris server; The first server sends the first domain name resolution request to the second server, including: the first server sending the first domain name resolution request and the identification information of the first satellite to the second server; The second server receives the first IP address corresponding to the first domain name sent by the local domain name server, including: The ephemeris server receives the identification information of the first satellite sent by the local domain name server, and the ephemeris server is used to store the mapping relationship between the satellite identification information and the ephemeris information. The ephemeris server obtains the ephemeris information corresponding to the first satellite based on the identification information of the first satellite; The ephemeris server determines the network coverage area of ​​the first satellite based on the ephemeris information of the first satellite. The ephemeris server sends the ground coverage information of the first satellite to the local domain name server; The second server receives the first IP address corresponding to the first domain name sent by the local domain name server, wherein the first IP address is obtained by the local domain name server based on the network coverage ground range information of the first satellite and the mapping relationship between domain names and IP addresses stored by the local domain name server. The communication method according to claim 8 is characterized in that, The network coverage area information of the first satellite includes: the location information of the ground gateway station currently connected to the first satellite. The communication method according to claim 9 is characterized in that, The method by which the local domain name server obtains the first IP address based on the network coverage location information of the first satellite and the mapping relationship between domain names and IP addresses stored in the local domain name server includes: The local domain name server determines at least one IP address corresponding to the first domain name based on the mapping relationship between domain names and IP addresses stored in the local domain name server. The local domain name server selects the first IP address from the at least one IP address, where the first IP address is the IP address corresponding to the application server that is closest to the location information of the ground gateway station. A communication method, characterized in that, For use in a satellite system, the satellite system includes a User Plane Function (UPF), a first server and a second server, the first server is deployed on a first satellite, the first satellite operates in a first Earth orbit, the second server is deployed on a second satellite, the second satellite operates in a second Earth orbit, the second Earth orbit is a geosynchronous orbit, and the second Earth orbit is higher than the first Earth orbit; The method includes: The User Plane Function (UPF) receives a first domain name resolution request sent by a terminal device in the ground system; the first domain name resolution request includes a first domain name that the terminal device requests to resolve; The User Plane Function (UPF) determines the first domain name resolution request as a first type of domain name resolution request based on the first domain name in the first domain name resolution request, and sends the first domain name resolution request to the second server. The classification of the first domain name resolution request is determined based on the contract information and / or user plane forwarding rule information corresponding to the application corresponding to the first domain name. Based on the domain name and IP address mapping relationship stored in the second server, the second server determines that the first IP address corresponding to the first domain name is not stored in the second server, and sends the first domain name resolution request to the local domain name server in the ground system. The period during which the second server updates the domain name and IP address mapping relationship from the local domain name server is less than or equal to the period during which the first server updates the domain name and IP address mapping relationship from the local domain name server. The second server receives the first IP address corresponding to the first domain name sent by the local domain name server; The second server sends the first IP address to the terminal device; The User Plane Function (UPF) receives a second domain name resolution request sent by the terminal device. The User Plane Function (UPF) determines that the second domain name resolution request is a second type of domain name resolution request based on the second domain name in the second domain name resolution request, and sends the second domain name resolution request to the first server. The communication method according to claim 11 is characterized in that, The method further includes: When the first server determines, based on the mapping relationship between domain names and IP addresses, that the first server does not store the second IP address corresponding to the second domain name, the first server sends a resolution failure message to the terminal device. When the first server determines that it stores the second IP address corresponding to the second domain name based on the mapping relationship between the domain name and the IP address, the first server sends the second IP address to the terminal device. A satellite system, characterized in that, include: A first server and a second server, wherein the first server is deployed on a first satellite and the first satellite operates in a first Earth orbit, and the second server is deployed on a second satellite and the second satellite operates in a second Earth orbit, the second Earth orbit being higher than the first Earth orbit; The first server is used to receive a first domain name resolution request sent by a terminal device in the ground system. The first domain name resolution request includes a first domain name that the terminal device requests to resolve. The first server stores a mapping relationship between domain names and IP addresses. The first server is configured to send a first domain name resolution request to the second server when it is determined, based on the mapping relationship between the domain name and the IP address, that the first server does not store the first IP address corresponding to the first domain name; wherein, sending the first domain name resolution request to the second server includes: identifying the first domain name resolution request as a first type of domain name resolution request, and sending the first domain name resolution request to the second server, wherein the classification of the first domain name resolution request is determined based on the contract information and / or user plane forwarding rule information corresponding to the application corresponding to the first domain name; The second server is used to determine, based on the mapping relationship between domain names and IP addresses stored in the second server, that the first IP address corresponding to the first domain name is not stored in the second server, and to send the first domain name resolution request to the local domain name server in the ground system. The period during which the second server updates the mapping relationship between domain names and IP addresses from the local domain name server is less than or equal to the period during which the first server updates the mapping relationship between domain names and IP addresses from the local domain name server. The second server is used to receive the first IP address corresponding to the first domain name sent by the local domain name server; The second server is used to send the first IP address to the first server; The first server is used to send the first IP address to the terminal device. The satellite system according to claim 13 is characterized in that, The satellite system also includes a User Plane Function (UPF); The User Plane Function (UPF) is used to receive the first domain name resolution request sent by the terminal device. The User Plane Function (UPF) is used to determine that the first domain name resolution request is a first type of domain name resolution request based on the first domain name in the first domain name resolution request, mark the first domain name resolution request with a first identifier, and send the first domain name resolution request and the first identifier to the first server. The satellite system according to claim 14 is characterized in that, The User Plane Function (UPF) is used to determine the application corresponding to the first domain name based on the first domain name in the first domain name resolution request, and to obtain the subscription information and / or user plane forwarding rule information corresponding to the application corresponding to the first domain name, and to determine that the first domain name resolution request is a first type of domain name resolution request based on the subscription information and / or user plane forwarding rule information corresponding to the application corresponding to the first domain name; or, The User Plane Function (UPF) is used to determine the user plane forwarding rule information corresponding to the first domain name based on the first domain name in the first domain name resolution request, and to determine that the first domain name resolution request is the first type of domain name resolution request based on the user plane forwarding rule information corresponding to the first domain name. A computer-readable storage medium, characterized in that, It stores executable instructions that, when executed on an electronic device, implement the communication method according to any one of claims 1 to 12. An electronic device, characterized in that, include: A memory for storing instructions executed by one or more processors of an electronic device, and said one or more processors for performing the communication method according to any one of claims 1 to 12.

Images