WO2024032499A1

WO2024032499A1 - Dns query method and communication device

Info

Publication number: WO2024032499A1
Application number: PCT/CN2023/111221
Authority: WO
Inventors: 吕华章; 李欢; 孙晓文
Original assignee: 维沃移动通信有限公司
Priority date: 2022-08-09
Filing date: 2023-08-04
Publication date: 2024-02-15
Also published as: CN117640578A

Abstract

The present application belongs to the technical field of communications. Disclosed are a domain name system (DNS) query method and a communication device. The method in the embodiments of the present application comprises: a first communication device receiving a DNS query, wherein the DNS query comprises a fully qualified domain name (FQDN), the first communication device is a communication device under an operator corresponding to a first public land mobile network (PLMN) ID, and the FQDN is a domain name under an operator corresponding to a second PLMN ID; and the first communication device sending the DNS query to a second communication device, wherein the second communication device is a communication device under the operator corresponding to the second PLMN ID.

Description

DNS query method and communication equipment

cross reference

This application claims priority to the Chinese patent application filed with the China Patent Office on August 9, 2022, with application number 202210952543.8 and titled "DNS Query Method and Communication Equipment". The entire content of this application is incorporated into this application by reference. .

Technical field

This application belongs to the field of communication technology, and specifically relates to a DNS query method and communication equipment.

Background technique

Currently, when operators provide business services to terminals, they can deploy Edge Application Server (EAS) close to the terminal side. The edge application server can provide edge computing services for terminals. When the terminal needs to access the edge server, it can access it through the base station and user plane function (UPF) under the operator. However, in some possible application scenarios, the operator where the terminal is located does not deploy EAS locally, but other operators in the same area provide edge computing services. In this way, the terminal will have the need to access the edge application server across operators. That is, terminals under operator A will need to access the edge application server under operator B. However, there is currently a lack of an effective solution to achieve this purpose.

Contents of the invention

Embodiments of the present application provide a DNS query method and communication device, which can solve the problem of terminals being unable to access edge application servers across operators.

In a first aspect, a DNS query method is provided. The method includes: a first communication device receives a Domain Name System (Domain Name System, DNS) query, and the DNS query includes a fully qualified domain name (Fully Qualified Domain Name, FQDN), The first communication device is a communication device under an operator corresponding to a first Public Land Mobile Network (PLMN) ID, and the FQDN is a domain name under an operator corresponding to a second PLMN ID; the third A communication device sends the DNS query to a second communication device, and the second communication device is a communication device under the operator corresponding to the second PLMN ID.

In a second aspect, a DNS query device is provided. The device includes: a receiving module, configured to receive a domain name system DNS query, where the DNS query includes the fully qualified domain name FQDN, and the first communication device is the first public land mobile The communication device under the operator corresponding to the network PLMN ID, the FQDN is the domain name under the operator corresponding to the second PLMN ID; the sending module is used to send the DNS query to the second communication device, the second communication device It is the communication equipment under the operator corresponding to the second PLMN ID.

In a third aspect, a DNS query method is provided. The method includes: a second communication device receiving a DNS query, the DNS query being sent by a first communication device, and the first communication device being an operator corresponding to the first PLMN ID. The DNS query includes FQDN, the FQDN is the domain name of the operator corresponding to the second PLMN ID, and the second communication device is the communication equipment of the operator corresponding to the second PLMN ID. ; The second communication device forwards the DNS query to the DNS server to obtain the EAS IP address corresponding to the FQDN.

In a fourth aspect, a DNS query device is provided. The device includes: a receiving module for receiving a DNS query. The DNS query is sent by a first communication device, and the first communication device is an operator corresponding to the first PLMN ID. The communication equipment under the operator, the DNS query includes FQDN, the FQDN is the domain name under the operator corresponding to the second PLMN ID, and the second communication equipment is the communication under the operator corresponding to the second PLMN ID. Device; sending module, used to forward the DNS query to the DNS server and obtain the EAS IP address corresponding to the FQDN.

In a fifth aspect, a DNS query method is provided. The method includes: a third communication device receives a first request, the first request is used to request a processing rule for an FQDN, and the FQDN is an operation corresponding to the second PLMN ID. The third communication device is a communication device under the operator corresponding to the first PLMN ID; the third communication device sends a first response, the first response contains a first rule, and the third communication device One rule is a processing rule for the FQDN. The first rule is used to instruct a DNS query containing the FQDN to be sent to a second communication device. The second communication device is under the operator corresponding to the second PLMN ID. communication device.

In a sixth aspect, a DNS query device is provided. The device includes: a receiving module for receiving a first request. The first request is used to request a processing rule for an FQDN. The FQDN is corresponding to the second PLMN ID. The domain name under the operator, the third communication device is the communication device under the operator corresponding to the first PLMN ID; the sending module is used to send the first response, the first response contains the first rule, the third One rule is a processing rule for the FQDN. The first rule is used to instruct a DNS query containing the FQDN to be sent to a second communication device. The second communication device is under the operator corresponding to the second PLMN ID. communication device.

In a seventh aspect, a DNS query method is provided. The method includes: a fourth communication device receiving a DNS response. The fourth communication device is a communication device under an operator corresponding to the second PLMN ID. The DNS response includes FQDN and the EAS IP address corresponding to the FQDN; the fourth communication device determines the first information according to the DNS response, the first information includes DNAI and/or the IP address or identification of the second UPF; the third Four communication equipment Prepare to send the first information; wherein, the DNAI is used for user plane selection by the operator corresponding to the first PLMN ID, and the second UPF is the UPF under the operator corresponding to the second PLMN ID, so The IP address or identification of the second UPF is used by the operator corresponding to the first PLMN ID to establish a PDU session to the operator corresponding to the second PLMN ID.

In an eighth aspect, a DNS query device is provided. The device includes: a receiving module for receiving a DNS response. The fourth communication device is a communication device under the operator corresponding to the second PLMN ID. In the DNS response Contains FQDN and the EAS IP address corresponding to the FQDN; a determination module, used to determine the first information according to the DNS response, the first information includes the IP address or identification of the DNAI and/or the second UPF; the sending module, Used to send the first information; wherein the DNAI is used for user plane selection by the operator corresponding to the first PLMN ID, and the second UPF is the UPF under the operator corresponding to the second PLMN ID, The IP address or identification of the second UPF is used by the operator corresponding to the first PLMN ID to establish a PDU session to the operator corresponding to the second PLMN ID.

In a ninth aspect, a communication device is provided. The terminal includes a processor and a memory. The memory stores programs or instructions that can be run on the processor. When the program or instructions are executed by the processor, the following is implemented: The steps of the method described in the first aspect, or the steps of implementing the method described in the third aspect, or the steps of the method described in the fifth aspect, or the steps of the method described in the seventh aspect.

In a tenth aspect, a communication device is provided, including a processor and a communication interface, wherein the communication interface is used to receive a domain name system DNS query, the DNS query includes a fully qualified domain name FQDN, and the communication device is the first A communication device under the operator corresponding to the public land mobile network PLMN ID, and the FQDN is the domain name under the operator corresponding to the second PLMN ID; sending the DNS query to the second communication device, the second communication device is the first A communication device under an operator corresponding to the second PLMN ID; or, the communication interface is used to receive a DNS query, the DNS query is sent by a first communication device, and the first communication device is an operator corresponding to the first PLMN ID The communication device under, the DNS query includes FQDN, the FQDN is the domain name under the operator corresponding to the second PLMN ID, the communication device is the communication device under the operator corresponding to the second PLMN ID; forwarding The DNS queries the DNS server to obtain the EAS IP address corresponding to the FQDN; or, the communication interface is used to receive a first request, and the first request is used to request processing rules for the FQDN, and the FQDN is the first Domain names under the operator corresponding to the second PLMN ID, and the communication device is a communication device under the operator corresponding to the first PLMN ID; sending a first response, where the first response contains a first rule, and the first rule is a processing rule for the FQDN, and the first rule is used to instruct a DNS query containing the FQDN to be sent to a second communication device. The second communication device is a communication device under the operator corresponding to the second PLMN ID. ; Or, the communication interface is used to receive a DNS response, the communication device is a communication device under the operator corresponding to the second PLMN ID, and the DNS response includes the FQDN and the The EAS IP address corresponding to the FQDN; the processor is used to determine the first information according to the DNS response, the first information includes DNAI and/or the IP address or identification of the second UPF; the communication interface is used to send The first information; wherein the DNAI is used for user plane selection by the operator corresponding to the first PLMN ID, the second UPF is the UPF under the operator corresponding to the second PLMN ID, and the third The IP address or identification of the second UPF is used by the operator corresponding to the first PLMN ID to establish a PDU session to the operator corresponding to the second PLMN ID.

In an eleventh aspect, a DNS query system is provided, including: at least two of a first communication device, a second communication device, a third communication device and a fourth communication device, the first communication device being operable to perform: The steps of the DNS query method described in the first aspect, the second communication device can be used to perform the steps of the DNS query method described in the third aspect, and the third communication device can be used to perform the steps of the DNS query method described in the fifth aspect. The steps of the DNS query method, the fourth communication device may be used to perform the steps of the DNS query method described in the seventh aspect.

In a twelfth aspect, a readable storage medium is provided. Programs or instructions are stored on the readable storage medium. When the programs or instructions are executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method are implemented. The steps of the method described in the third aspect, or the steps of implementing the method described in the fifth aspect, or the steps of the method described in the seventh aspect.

In a thirteenth aspect, a chip is provided. The chip includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the method described in the first aspect. Method, or implement the method as described in the third aspect, or implement the method as described in the fifth aspect, or implement the method as described in the seventh aspect.

In a fourteenth aspect, a computer program/program product is provided, the computer program/program product is stored in a storage medium, and the computer program/program product is executed by at least one processor to implement as described in the first aspect The steps of the DNS query method, or the steps of implementing the DNS query method as described in the third aspect, or the steps of implementing the DNS query method as described in the fifth aspect, or the steps of implementing the DNS query method as described in the seventh aspect step.

In the embodiment of this application, when the terminal under the operator corresponding to the first PLMN ID needs to access the edge application server under the operator corresponding to the second PLMN ID, the DNS query of the terminal is forwarded to the terminal corresponding to the second PLMN ID. The communication equipment under the operator can obtain the IP address of the edge application server that needs to be accessed, so that the terminal can access the edge application server across operators.

Description of drawings

Figure 1 is a schematic diagram of a wireless communication system according to an embodiment of the present application;

Figure 2 is a schematic flow chart of a DNS query method according to an embodiment of the present application;

Figure 3 is a schematic flow chart of a DNS query method according to an embodiment of the present application;

Figure 4 is a schematic flow chart of a DNS query method according to an embodiment of the present application;

Figure 5 is a schematic flow chart of a DNS query method according to an embodiment of the present application;

Figure 6 is a schematic flow chart of a DNS query method according to an embodiment of the present application;

Figure 7 is a schematic flow chart of a DNS query method according to an embodiment of the present application;

Figure 8 is a schematic flow chart of a DNS query method according to an embodiment of the present application;

Figure 9 is a schematic flow chart of a DNS query method according to an embodiment of the present application;

Figure 10 is a schematic structural diagram of a DNS query device according to an embodiment of the present application;

Figure 11 is a schematic structural diagram of a DNS query device according to an embodiment of the present application;

Figure 12 is a schematic structural diagram of a DNS query device according to an embodiment of the present application;

Figure 13 is a schematic structural diagram of a DNS query device according to an embodiment of the present application;

Figure 14 is a schematic structural diagram of a communication device according to an embodiment of the present application;

Figure 15 is a schematic structural diagram of a communication device according to an embodiment of the present application;

Figure 16 is a schematic structural diagram of a communication device according to an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be clearly described below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, but not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art fall within the scope of protection of this application.

The terms "first", "second", etc. in the description and claims of this application are used to distinguish similar objects and are not used to describe a specific order or sequence. It is to be understood that the terms so used are interchangeable under appropriate circumstances so that the embodiments of the present application can be practiced in sequences other than those illustrated or described herein, and that "first" and "second" are distinguished objects It is usually one type, and the number of objects is not limited. For example, the first object can be one or multiple. In addition, "and/or" in the description and claims indicates at least one of the connected objects, and the character "/" generally indicates that the related objects are in an "or" relationship.

It is worth pointing out that the technology described in the embodiments of this application is not limited to Long Term Evolution (LTE)/LTE Evolution (LTE-Advanced, LTE-A) systems, and can also be used in other wireless communication systems, such as code Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access, OFDMA), Single-carrier Frequency Division Multiple Access (SC-FDMA) and other systems. The terms "system" and "network" in the embodiments of this application "Network" is often used interchangeably, and the techniques described can be used with the systems and radio technologies mentioned above as well as with other systems and radio technologies. The following description describes the New Radio (NR) interface for example purposes. ) system, and NR terminology is used in most of the following descriptions, but these technologies can also be applied to applications other than NR system applications, such as 6th Generation (6G) communication systems.

Figure 1 shows a block diagram of a wireless communication system to which embodiments of the present application are applicable. The wireless communication system includes a terminal 11 and a network side device 12. The terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), or a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a palmtop computer, a netbook, or a super mobile personal computer. (ultra-mobile personal computer, UMPC), mobile Internet device (Mobile Internet Device, MID), augmented reality (AR)/virtual reality (VR) equipment, robots, wearable devices (Wearable Device) , Vehicle User Equipment (VUE), Pedestrian User Equipment (PUE), smart home (home equipment with wireless communication functions, such as refrigerators, TVs, washing machines or furniture, etc.), game consoles, personal computers (personal computer, PC), teller machine or self-service machine and other terminal-side devices. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets) bracelets, smart anklets, etc.), smart wristbands, smart clothing, etc. It should be noted that the embodiment of the present application does not limit the specific type of the terminal 11. The network side device 12 may include an access network device or a core network device, where the access network device 12 may also be called a radio access network device, a radio access network (Radio Access Network, RAN), a radio access network function or Wireless access network unit. The access network device 12 may include a base station, a WLAN access point or a WiFi node, etc. The base station may be called a Node B, an evolved Node B (evolved Node B, eNB), an access point, or a Base Transceiver Station (Base Transceiver Station). BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), home B-node, home evolved B-node, Transmitting Receiving Point, TRP) or some other appropriate term in the field, as long as the same technical effect is achieved, the base station is not limited to specific technical terms. It should be noted that in the embodiment of this application, only the base station in the NR system is taken as an example. This introduction does not limit the specific type of base station. Core network equipment may include but is not limited to at least one of the following: core network nodes, core network functions, mobility management entities (Mobility Management Entity, MME), access mobility management functions (Access and Mobility Management Function, AMF), session management functions (Session Management Function, SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Service Discovery function (Edge Application Server Discovery Function, EASDF), unified data management (Unified Data Management, UDM), unified data warehousing (Unified Data Repository, UDR), attributed user server (Home Subscriber Server, HSS), centralized network configuration (Centralized network configuration, CNC), network storage function (Network Repository Function, NRF), network exposure function (Network Exposure Function, NEF), local NEF (Local NEF, or L -NEF), Binding Support Function (Binding Support Function, BSF), Application Function (Application Function, AF), etc. It should be noted that in the embodiment of this application, only the core network equipment in the NR system is used as an example for introduction, and the specific type of the core network equipment is not limited.

The DNS query method and communication device provided by the embodiments of the present application will be described in detail below with reference to the accompanying drawings through some embodiments and application scenarios.

As shown in Figure 2, the embodiment of the present application provides a DNS query method 200, which can be executed by the first communication device. In other words, the DNS query method can be executed by software or hardware installed in the first communication terminal. The DNS query method includes the following steps.

S202: The first communication device receives a domain name system DNS query. The DNS query includes the fully qualified domain name FQDN. The first communication device is a communication device under the operator corresponding to the first public land mobile network PLMN ID, and FQDN is corresponding to the second PLMN ID. domain name under the operator.

When the terminal under the operator corresponding to the first Public Land Mobile Network (Public Land Mobile Network, PLMN) ID wants to access the Edge Application Server (Edge Application Server, EAS) under the operator corresponding to the second PLMN ID, the terminal You can send a Domain Name System (DNS) query and obtain the EAS IP address corresponding to the FQDN through the DNS query process. The first communication device under the operator corresponding to the first PLMN ID can receive the DNS query. Among them, the DNS query includes the fully qualified domain name (Fully Qualified Domain Name, FQDN) of the operator corresponding to the second PLMN ID, and the DNS query is used to query the EAS IP address corresponding to the FQDN.

The first communication device is a communication device under the operator corresponding to the first PLMN ID. The first communication device may be an Edge Application Server Discovery Function (EASDF). Optionally, the first communication device is an EASDF deployed under the operator corresponding to the first PLMN ID, or H-EASDF ( HPLMN EASDF), that is, the current EASDF is the network element of the operator where the terminal is located.

The FQDN included in the DNS query is the domain name under the operator corresponding to the second PLMN ID. Optionally, the FQDN can satisfy at least one of the following:

FQDN is the domain name that the equipment under the operator corresponding to the second PLMN ID can process or resolve;

The equipment under the operator corresponding to the first PLMN ID cannot resolve the FQDN.

Wherein, the device capable of processing or parsing the FQDN under the operator corresponding to the second PLMN ID may be the second communication device. The second communication device may be an EASDF. Alternatively, the EASDF may be an EASDF deployed under the operator corresponding to the second PLMN ID, or a V-EASDF.

In one implementation, the FQDN is a domain name that can be processed or parsed by the equipment of the operator corresponding to the second PLMN ID, which means that the FQDN may be an internal domain name used internally by the second operator, and the resolution of the domain name The process can only be completed within the second operator; or, in order to resolve the FQDN, it is necessary to use the EASDF within the second operator for help; or, only the EASDF within the second operator can configure DNS for the FQDN. DNS message handling rules (DNS message handling rules), EASDF or SMF in the first operator cannot generate DNS message handling rules based on FQDN, nor can it resolve this domain name through the DNS process.

S204: The first communication device sends a DNS query to the second communication device. The second communication device is a communication device under the operator corresponding to the second PLMN ID.

After the first communication device receives the DNS query, since the first communication device cannot parse the FQDN in the DNS query, the first communication device can send the DNS query to the second communication device under the operator corresponding to the second PLMN ID. to resolve or process the FQDN by the second communications device. The second communication device is a communication device under the operator corresponding to the second PLMN ID. Specifically, the second communication device may be a communication device under the operator corresponding to the second PLMN ID and capable of processing or parsing the above-mentioned FQDN. The second communication device may be an EASDF. Alternatively, the EASDF may be an EASDF deployed under the operator corresponding to the second PLMN ID, or a V-EASDF.

Optionally, as an embodiment, when the first communication device sends a DNS query to the second communication device, it may send a DNS query to the second communication device according to the first rule. The first rule is the processing rule of FQDN, and the first rule is Yu instructs to send a DNS query including the FQDN to the second communication device. The first rule may be a DNS message processing rule, and the rule may be obtained from the SMF within the first operator. The first rule instructs the EASDF under the first operator to send the DNS query to the EASDF under the second operator. That is, the DNS query is sent to the EASDF IP address under the second operator.

Optionally, the first rule may be obtained by the first communication device from other devices when receiving a DNS query. Specifically, the first communication device may obtain the first rule through the following steps:

The first communication device sends a first request, and the first request is used to request processing rules for the FQDN;

The first response is received, and the first response contains the first rule.

After receiving the DNS query, the first communication device cannot The FQDN is parsed, so the first communications device can send a first request to request processing rules for the FQDN. After sending the first request, the first communication device may receive a first response to the first request, and the first response may include a first rule, and the first rule is a processing rule for the FQDN.

When sending the first request, the first communication device may optionally send the first request to the third communication device. Correspondingly, when receiving the first response, the first communication device may receive the first response from the third communication device. . Among them, the third link The communication device may be a communication device under the operator corresponding to the first PLMN ID. Alternatively, the third communication device may be a session management function (Session Management Function, SMF) under the operator corresponding to the first PLMN ID, or H-SMF. Here, SMF will generate DNS message processing rules, that is, the first rule, based on the FQDN in the DNS query reported by EASDF, instructing EASDF in the first operator to send the DNS query to EASDF in the second operator.

After receiving the first rule, the first communication device may send a DNS query according to the first rule, that is, forward the DNS query according to the first rule. The first rule may be used to instruct the DNS query containing the FQDN to be sent to the second communication device. When the first communication device sends the DNS query according to the first rule, the first communication device may send the DNS query to the second communication device indicated by the first rule. equipment.

Optionally, the first rule can also be used to indicate the address information of the second communication device to which the DNS query is to be sent. In this way, when the first communication device sends the DNS query to the second communication device, it can be based on the address information indicated by the first rule. The address information sends a DNS query to the second communications device.

In this embodiment of the present application, after sending a DNS query according to the first rule, the first communication device may receive a DNS response to the DNS query. For example, the first communication device may receive a DNS response corresponding to the DNS query from the second communication device. The DNS response can include the FQDN in the DNS query and the Edge Application Server Internet Protocol (EAS IP) address corresponding to the FQDN.

Optionally, as an embodiment, the first communication device receiving the DNS response may receive the DNS response from the second communication device. Specifically, when the first communication device sends a DNS query, it can send the DNS query to the second communication device. After receiving the DNS query, the second communication device can query the DNS server for the ESA IP address corresponding to the FQDN, and When the EAS IP address is queried, a DNS response can be sent to the first communication device, so that the first communication device can receive a DNS response from the second communication device. Wherein, the second communication device is a communication device under the operator corresponding to the second PLMN ID. The second communication device may be an EASDF. Alternatively, the EASDF may be an EASDF or V-EASDF deployed under the operator corresponding to the second PLMN ID.

Optionally, as an embodiment, the first communication device may also receive the first information after sending a DNS query according to the first rule. The first information may include a data network access identifier (Data Network Access Identifier, DNAI) and/or the IP address or identification (ID) of the second user plane (User Plane Function, UPF). The DNAI can be used by the operator corresponding to the first PLMN ID to select the user plane. The DNAI is determined based on the EAS IP address and/or FQDN in the DNS response. The second UPF is a UPF under the operator corresponding to the second PLMN ID. The IP address or identification of the second UPF can be used by the operator corresponding to the first PLMN ID to establish a protocol data unit (Packet Data Unit, PDU) session to the first PLMN ID. The second PLMN ID corresponds to the operator, and the second UPF is determined based on DNAI. The DNAI here can be either the DNAI within the first operator or the DNAI within the second operator.

Optionally, the first communication device receives the first information, which may be the first communication device receiving the first information from the second communication device. The second communication device is a communication device under the operator corresponding to the second PLMN ID. Optionally, the second communication device may be an EASDF under the operator corresponding to the second PLMN ID. In this embodiment, the first communication device can send a DNS query request to the second communication device. After querying the EAS IP address corresponding to the FQDN, the second communication device can send a request to the operator under the second PLMN ID. The fourth communication device (such as SMF or V-SMF) sends a DNS response. The fourth communication device can determine the first information according to the DNS response. For example, the fourth communication device determines the DNAI according to the EAS IP address in the DNS response. The DNAI can The DNI of the second operator may also be the DNAI of the first operator, and then the fourth communication device may send the first information to the second communication device. After receiving the first information, the second communication device can send the first information to the first communication device, so that the first communication device can receive the first information from the second communication device. For the specific implementation of the operations performed by the second communication device and the fourth communication device in this process, reference can be made to the embodiments shown in FIG. 3 and FIG. 5 , which will not be described in detail here. The second communication device may send the first information while sending the DNS response to the first communication device; the second communication device may also use service signaling with the first communication device, such as between two EASDFs. The service message sends the first information to the first communication device.

Optionally, the first communication device receives the first information from the second communication device through the following signaling: Neasdf_DNSContext_Update Request, Neasdf_DNSContext_Update Response, Neasdf_DNSContext_Notify Request, Neasdf_DNSContext_Notify Response.

After receiving the first information, the first communication device may optionally forward the first information to other communication devices. When the first communication device sends the first information, optionally, the first communication device can send the first information to the third communication device. The first information can be used by the third communication device to select a user plane, so that cross-platform communication can be implemented based on the selected user plane. The purpose of the operator's access to EAS. The third communication device is a communication device under the operator corresponding to the first PLMN ID. Optionally, the third communication device may be an SMF. The SMF may be an SMF or H-deployed under the operator corresponding to the first PLMN ID. SMF. The specific implementation method for the third communication device to select the user plane according to the first information can refer to the embodiment shown in Figure 4, which will not be described in detail here. For example, the third communication device can determine the user plane based on the DNAI and perform the UPF selection process.

As shown in Figure 3, the embodiment of the present application provides a DNS query method 300, which can be executed by a second communication device. In other words, the DNS query method can be executed by software or hardware installed in the second communication terminal. The DNS query method includes the following steps.

S302: The second communication device receives a DNS query. The DNS query is sent by the first communication device. The first communication device is a communication device under the operator corresponding to the first PLMN ID. The DNS query contains FQDN, and FQDN is corresponding to the second PLMN ID. domain name under the operator, and the second communication device is a communication device under the operator corresponding to the second PLMN ID.

When the terminal under the operator corresponding to the first PLMN ID wants to access the EAS under the operator corresponding to the second PLMN ID, the terminal can send a DNS query, and the DNS query can include the EAS under the operator corresponding to the second PLMN ID. FQDN, in this case, the second communication device under the operator corresponding to the second PLMN ID can receive the DNS query. The second communication device may be an EASDF. Alternatively, the EASDF may be an EASDF or V-EASDF (VPLMN EASDF) deployed under the operator corresponding to the second PLMN ID.

Optionally, as an embodiment, the second communication device receives the DNS query, which may be the second communication device receiving the DNS query from the first communication device. Specifically, after the terminal sends a DNS request, the first communication device under the operator corresponding to the first PLMN ID can receive the DNS request. Since the FQDN in the DNS query is the domain name under the operator corresponding to the second PLMN ID, and the first communication device is the communication device under the operator corresponding to the first PLMN ID, the FQDN cannot be resolved. Therefore, the first communication device can The DNS request is sent to the second communication device according to the first rule so that the second communication device can process or resolve the FQDN in the DNS query. The first communication device may be an EASDF. Alternatively, the EASDF may be an EASDF or H-EASDF deployed under an operator corresponding to the first PLMN ID. The specific implementation method for the first communication device to send the DNS query to the second communication device according to the first rule can refer to the embodiment shown in Figure 2, and the description will not be repeated here.

The FQDN included in the DNS query is the domain name under the operator corresponding to the second PLMN ID. The DNS query is used to request the EAS IP address corresponding to the FQDN.

Optionally, the FQDN included in the DNS query can satisfy at least one of the following:

Among them, the device under the operator corresponding to the second PLMN ID that can process or resolve the FQDN may be the EASDF under the operator, that is, it may be the second communication device.

S304: The second communication device forwards the DNS query to the DNS server and obtains the EAS IP address corresponding to the FQDN.

After receiving the DNS query, the second communication device may forward the DNS query to the DNS server (DNS server) of the operator corresponding to the second PLMN ID. After receiving the DNS query, the DNS server can query the corresponding EAS IP address according to the FQDN in the DNS query and return it to the second communication device, so that the second communication device can obtain the EAS IP address corresponding to the FQDN.

Optionally, as an embodiment, the second communication device may send a DNS response after obtaining the EAS IP address corresponding to the FQDN. The DNS query response can contain the FQDN and the EAS IP address corresponding to the FQDN.

Optionally, the second communication device sends a DNS response, which may include at least one of the following:

The second communication device sends a DNS response to the first communication device;

The second communications device sends a DNS response to the fourth communications device.

After the second communication device sends a DNS response to the first communication device, the first communication device can receive the DNS response, thereby obtaining the query result of the DNS query.

Optionally, the second communication device may select which communication device to send the DNS response to according to preconfigured rules. For example, if the following rule is set in the second communication device: when a DNS query containing a specific FQDN is received, it is sent to the fourth communication device first, then the second communication device is executed to send a DNS response to the fourth communication device. If the following rule is set in the second communication device: when a DNS query containing a specific FQDN is received, it is sent to the first communication device first, then the second communication device is executed to send a DNS response to the first communication device. The rule for forwarding DNS responses in the second communication device may be set by the fourth communication device.

The fourth communication device is a communication device under the operator corresponding to the second PLMN ID. Optionally, the fourth communication device may be an SMF. The SMF is an SMF or V-SMF deployed under the operator corresponding to the second PLMN ID. . After the second communication device sends a DNS response to the fourth communication device, the fourth communication device can perform user plane selection under the operator corresponding to the second PLMN ID according to the DNS response. For specific implementation methods, please refer to the embodiment shown in Figure 5. The explanation will not be repeated here.

Optionally, after sending the DNS response, the second communication device can also receive the first information. The first information may include the DNAI and/or the IP address or identification of the second UPF. DNAI is used by the operator corresponding to the first PLMN ID to select the user plane. DNAI is determined based on the EAS IP address and/or FQDN in the DNS response. The second UPF is the UPF under the operator corresponding to the second PLMN ID. The IP address or identification of the second UPF is used by the operator corresponding to the first PLMN ID to establish a PDU session to the operator corresponding to the second PLMN ID. UPF is determined based on DNAI. The IP address or identity of the second UPF is also used to establish a cross-operator PDU session or IP route to the EAS IP address in the DNS response. The DNAI in the first information may be the DNAI under the second operator determined based on the EAS IP address or FQDN, or it may be the DNAI under the first operator.

Optionally, the second UPF includes at least one of the following: UPF, local PSA, UL CL.

Optionally, the second communication device receives the first information, which may be the second communication device receiving the first information from the fourth communication device. The fourth communication device is a communication device under the operator corresponding to the second PLMN ID. Optionally, the fourth communication device may be an SMF. In this embodiment, after the second communication device sends the DNS response to the fourth communication device, the fourth communication device can determine the first information based on the DNS response (according to the FQDN or EAS IP address in the DNS response), The first information is then sent to the second communication device so that the second communication device can receive the first information from the fourth communication device. The specific implementation method for the fourth communication device to determine the first information according to the DNS response can refer to the embodiment shown in Figure 5, which will not be described in detail here.

After receiving the first information, the second communication device may optionally send the first information. When the second communication device sends the first information, optionally, the first communication device can send the first information to the first communication device, so that the first communication device can send the first information to the third communication device, and the third communication device can send the first information to the third communication device according to the first communication device. This information is used to select the user plane, so that cross-operator access to EAS can be achieved based on the selected user plane. Wherein, the first communication device and the third communication device are communication devices under the operator corresponding to the first PLMN ID. Optionally, the first communication device may be EASDF or H deployed under the operator corresponding to the first PLMN ID. -EASDF, the third communication device may be an SMF or H-SMF deployed under the operator corresponding to the first PLMN ID. The specific implementation of the first communication device sending the first information and the third communication device selecting the user plane according to the first information may refer to the embodiments shown in FIG. 2 and FIG. 4 and will not be described in detail here. The first communication device selects a user plane according to the first information, which may mean that the first communication device selects a user plane in the operator corresponding to the first PLMN according to the first information, and the selected user plane is used to establish the EAS IP The server corresponding to the address, alternatively, establishes a cross-operator PDU session or IP connection or N9 tunnel to the second UPF.

As shown in Figure 4, the embodiment of the present application provides a DNS query method 400, which can be executed by a third communication device. In other words, the DNS query method can be executed by software or hardware installed in the third communication terminal. The DNS query method includes the following steps.

S402: The third communication device receives the first request. The first request is used to request processing rules for FQDN. FQDN is the domain name under the operator corresponding to the second PLMN ID. The third communication device is the operator corresponding to the first PLMN ID. communication equipment. The third communication device may be an SMF. Alternatively, the SMF may be an SMF or H-SMF deployed under the operator corresponding to the first PLMN ID.

The first request may be Neasdf_DNSContext_Notify Request, Neasdf_DNSContext_Notify Response, Neasdf_DNSContext_Update Request, Neasdf_DNSContext_Update Response.

When the terminal under the operator corresponding to the first PLMN ID wants to access the EAS IP under the operator corresponding to the second PLMN ID, the terminal can send a DNS query, and the DNS query can include the operator corresponding to the second PLMN ID. In this case, the third communication device under the operator corresponding to the first PLMN ID can receive the first request, and the first request is used to request processing rules for the FQDN in the DNS query. The FQDN processing rule refers to where the DNS query containing this FQDN should be sent (generally speaking, it is sent to the DNS server or EASDF).

Optionally, as an embodiment, the third communication device receives the first request, which may be the third communication device receiving the first request from the first communication device. Specifically, after the terminal sends a DNS request, the first communication device under the operator corresponding to the first PLMN ID (which may be an EASDF or H-EASDF deployed under the operator corresponding to the first PLMN ID) can receive the DNS request. . Since the FQDN in the DNS query is the domain name under the operator corresponding to the second PLMN ID, and the first communication device is the communication device under the operator corresponding to the first PLMN ID, the FQDN cannot be resolved. Therefore, the first communication device can A first request is sent to request processing rules for the FQDN. When sending the first request, the first communication device may send it to the third communication device, so that the third communication device may receive the first request from the first communication device.

Among them, the device under the operator corresponding to the second PLMN ID that can process or resolve the FQDN may be the EASDF under the operator, and specifically may be the second communication device in the embodiments of this application.

S404: The third communication device sends a first response. The first response contains a first rule. The first rule is a processing rule for FQDN. The first rule is used to instruct the DNS query containing FQDN to be sent to the second communication device. The second The communication device is a communication device under the operator corresponding to the second PLMN ID.

The first response may be: Neasdf_DNSContext_Notify Request, Neasdf_DNSContext_Notify Response, Neasdf_DNSContext_Update Request, Neasdf_DNSContext_Update Response.

In this embodiment, the processing rule for FQDN can be expressed as a first rule. After receiving the first request, the third communication device may send the first response. The first response may include a first rule, and the first rule may be used to instruct the DNS query including the FQDN to be sent to the second communication device. Wherein, the second communication device is a communication device under the operator corresponding to the second PLMN ID, and can process or parse the FQDN in the DNS query. Optionally, the second communication device may be an EASDF.

Optionally, when the third communication device sends the first response, the third communication device may send the first response to the first communication device. First After receiving the first response, the terminal device may send a DNS query according to the first rule in the first response. For specific implementation methods, please refer to the embodiment shown in Figure 2, and the description will not be repeated here.

Optionally, the first rule is also used to indicate address information of the second communication device. In this way, after the third communication device sends the first rule to the first communication device, when the first communication device sends a DNS query to the second communication device according to the first rule, it can send a DNS query to the second communication device according to the address information indicated by the first rule. The device sends a DNS query. That is, the DNS query is sent to the network element corresponding to the IP address indicated in the first rule. The network element may be the second communication device, that is, the EASDF under the second operator.

Optionally, as an embodiment, the first rule may be configured and obtained by the third communication device based on information obtained from other devices upon receiving the first request. Specifically, when the third communication device receives the first request, the third communication device may include the following steps:

The third communication device sends a second request, and the second request is used to request to obtain the second information;

The third communication device receives the second response, and the second response contains the second information;

The third communication device configures the first rule according to the second information.

When the third communication device receives the first request, it may not be able to generate DNS processing rules based on the FQDN in the DNS query. In this case, when the third communication device receives the first request, it may send a third request. The third please is used to request the second information. The second information may include at least one of the following:

Mapping relationship between FQDN and PLMN ID, PLMN ID is the PLMN ID of the operator that can resolve FQDN;

The address information of the network element that can resolve the FQDN and/or the PLMN ID to which the network element belongs.

After sending the second request, the third communication device may receive a second response to the second request. The second response may include the above-mentioned second information. After receiving the second response, the third communication device may configure the first rule according to the second information in the second response. The first rule may indicate that when the communication device under the operator corresponding to the first PLMN ID receives a DNS query containing a specific FQDN, it needs to send the DNS query to the communication device under the second operator (such as deployed on the second PLMN EASDF or V-EASDF) under the operator corresponding to the ID is parsed, and the specific FQDN is the domain name under the operator corresponding to the second PLMN ID.

The second request may be: Nnef_EASDeployment_Subscribe; after NEF receives the second request, it may also execute Nudr_DM_Query Request to obtain the second information from the UDR;

The second response may be: UDR sends Nudr_DM_Query Response to NEF, and NEF sends Nnef_EASDeployment_Notify to SMF.

Optionally, when sending the second request, the third communication device may send the second request to the Network Exposure Function (NEF). Correspondingly, when receiving the second response, the third communication device may receive the Receive second response. Among them, the second information in the second response can be obtained by NEF from the Unified Data Repository (UDR). The second information in the UDR is provided by the application function (Application Function, AF) and is prepared by AF through NEF. Store in UDR.

In this embodiment of the present application, after sending the first response, the third communication device may optionally include the following steps:

The third communication device receives the first information, and the first information includes the DNAI and/or the IP address or identification of the second UPF;

The third communication device selects a user plane according to the first information.

The DNAI in the first information can be used by the operator corresponding to the first PLMN ID to select the user plane, and the DNAI is determined based on the EAS IP address and/or FQDN in the DNS response. The second UPF is the UPF under the operator corresponding to the second PLMN ID. The IP address or identification of the second UPF can be used by the operator corresponding to the first PLMN ID to establish a PDU session to the operator corresponding to the second PLMN ID. Two UPFs are determined based on DNAI.

Optionally, the third communication device receives the first information, which may be that the third communication device receives the first information from the first communication device, and/or the third communication device receives the first information from the fourth communication device. The first communication device is a communication device deployed under the operator corresponding to the first PLMN ID, which may be EASDF or H-EASDF. The fourth communication device is a communication device deployed under the operator corresponding to the second PLMN ID, which may be SMF or V -SMF. Wherein, in the case where the third communication device receives the first information from the first communication device, the first information may be received by the first communication device from the second communication device and sent to the third communication device, and the second communication device is deployed The communication device under the operator corresponding to the second PLMN ID may be EASDF or V-EASDF. For specific implementation methods, please refer to the specific implementation of the corresponding steps in the embodiments shown in Figures 2 and 3, and the description will not be repeated here. In the case where the third communication device receives the first information from the fourth communication device, the first information can be determined by the fourth communication device according to the EAS IP address and/or FQDN in the DNS response. The specific implementation method can be seen in Figure 5 The specific implementation of the corresponding steps in the embodiment is shown, and the description will not be repeated here.

After receiving the first information, when selecting the user plane based on the first information, the third communication device may include at least one of the following:

The third communication device selects the first UPF and/or UL CL uplink splitter under the operator corresponding to the first PLMN ID according to the first information;

The third communication device selects the second UPF under the operator corresponding to the second PLMN ID according to the first information, or the third communication device triggers the target network element under the operator corresponding to the second PLMN ID to select the second UPF according to the first information. UPF, the target network element includes a fourth communication device. The fourth communication device is a communication device under the operator corresponding to the second PLMN ID. Optionally, the fourth communication device may be deployed under the operator corresponding to the second PLMN ID. V-SMF, or SMF.

Optionally, the third communication device, according to the first information, can select the first UPF under the first operator, and the first UPF is used to establish a PDU session or IP route to the resolved EAS IP address; or , based on the first information, the third communication device can select the first UPF under the first operator, and the first UPF is used to establish PDU session to second UPF or IP route, or N9 tunnel.

Specifically, in the case where the first information includes the DNAI but does not include the address or identification of the second UPF, the third communication device needs to select the first UPF, the second UPF and the UL CL according to the first information, or select according to the first information. The first UPF and UL CL trigger the target network element under the operator corresponding to the second PLMN ID to select the second UPF. In the case where the first information includes the DNAI and the address or identification of the second UPF, the third communication device can select the first UPF and/or UL CL according to the first information without selecting the second UPF or triggering the second PLMN ID. Select the second UPF for the target network element under the corresponding operator.

Optionally, as an embodiment, the third communication device may also perform the following steps:

The third communication device sends a third request, and the third request is used to request to establish or update a PDU session within the operator corresponding to the second PLMN ID; the third request may be: Nsmf_PDUSession_Create Request or Nsmf_PDUSession_Update Request.

Optionally, the third request may also include at least one of the following:

DNAI, this DNAI can be used by the operator corresponding to the second PLMN ID to select the user plane. The DNAI corresponds to the DNAI under the operator corresponding to the first PLMN ID or the second PLMN ID;

The local PDU session anchor (PSA) IP address of the operator corresponding to the first PLMN ID; it can also be the IP address or ID of the first UPF;

The core network tunnel information CN Tunnel Info corresponding to the PSA under the operator corresponding to the first PLMN ID, such as N9 tunnel information, can also be the core network tunnel information of the first UPF. The N9 tunnel information includes at least one of the following: N9 tunnel identifier, N9 tunnel address.

The third communication device receives a third response. The third response includes the IP address and/or the second PLMN ID of the second communication device. The second communication device is a communication device under the operator corresponding to the second PLMN ID. The third response may be: Nsmf_PDUSession_Create Response or Nsmf_PDUSession_Update Response.

Optionally, the third communication device sends the third request. The third communication device may send the third request after selecting the user plane according to the first information. That is, the third communication device sends the third request when the third communication device selects the user plane according to the first information. After selecting the user interface.

Optionally, the third communication device sends the third request, which may be the third communication device sending the third request to the fourth communication device. The fourth communication device is a communication device under the operator corresponding to the second PLMN ID. Specifically, it may be an SMF or V-SMF deployed under the operator corresponding to the second PLMN ID. Correspondingly, the third communication device receives the third response, which may be the third communication device receiving the third response from the fourth communication device. That is, when the third communication device wants to establish or update a PDU session within the operator corresponding to the second PLMN ID, it can send a third request to the fourth communication device. After receiving the third request, the fourth communication device can determine the third communication device. The IP of the second communication device under the operator corresponding to the second PLMN ID address and/or the second PLMN ID, and then sending the IP address and/or the second PLMN ID of the second communication device to the third communication device, and the third communication device may receive the IP address of the second communication device from the fourth communication device and/or second PLMN ID.

Optionally, as an embodiment, the third response received by the third communication device may also include third information, and the third information may include at least one of the following:

DNAI, this DNAI can be used by the operator corresponding to the first PLMN ID to select the user plane, and the DNAI corresponds to the DNAI under the operator corresponding to the first PLMN ID;

The local PDU session anchor (PSA) IP address of the operator corresponding to the second PLMN ID; it can also be the IP address or ID of the second UPF;

The core network tunnel information CN Tunnel Info corresponding to the PSA under the operator corresponding to the second PLMN ID, such as N9 tunnel information, can also be the core network tunnel information of the second UPF. The N9 tunnel information includes at least one of the following: N9 tunnel identifier, N9 tunnel address.

After receiving the third response, the third communication device can establish or update a PDU session within the operator corresponding to the second PLMN ID according to the third information in the third response, thereby achieving the purpose of cross-operator access to the EAS.

In addition, in this embodiment, when the fourth communication device receives the third request, it can select the second UPF according to the information contained in the third request, for example, perform user plane selection according to DNAI; and then select the second UPF included in the third request. The core network tunnel information CN Tunnel Info corresponding to the PSA under the operator corresponding to the first PLMN ID is configured on the second UPF. The configuration method is through the N4 process, such as N4session establishment request or N4session modification request.

As shown in Figure 5, the embodiment of the present application provides a DNS query method 500, which can be executed by the fourth communication device. In other words, the DNS query method can be executed by software or hardware installed in the fourth communication terminal. The DNS query method includes the following steps.

S502: The fourth communication device receives a DNS response. The fourth communication device is a communication device under the operator corresponding to the second PLMN ID. The DNS response includes the FQDN and the EAS IP address corresponding to the FQDN.

When the terminal under the operator corresponding to the first PLMN ID wants to access the EAS under the operator corresponding to the second PLMN ID, the terminal can send a DNS query, and the DNS query can include the EAS under the operator corresponding to the second PLMN ID. FQDN, in this case, the fourth communication device under the operator corresponding to the second PLMN ID can receive the pin The DNS response to this DNS query. The fourth communication device may be an SMF under the operator corresponding to the second PLMN ID, and may be a V-SMF or an SMF.

Optionally, as an embodiment, the fourth communication device receives the DNS query, which may be the fourth communication device receiving the DNS query from the second communication device. Specifically, after the terminal sends a DNS request, the first communication device under the operator corresponding to the first PLMN ID can receive the DNS request. Since the FQDN in the DNS query is the domain name under the operator corresponding to the second PLMN ID, and the first communication device is the communication device under the operator corresponding to the first PLMN ID, the FQDN cannot be resolved. Therefore, the first communication device can The DNS request is sent to the second communication device according to the first rule so that the second communication device can process or resolve the FQDN in the DNS query. After receiving the DNS query, the second communication device can query the EAS IP address corresponding to the FQDN from the DNS server, and then send a DNS response to the fourth communication device. The fourth communication device can receive the DNS response from the second communication device. Wherein, the first communication device is a communication device under the operator corresponding to the first PLMN ID. Optionally, the first communication device may be an EASDF, and the EASDF may be an EASDF deployed under the operator corresponding to the first PLMN ID. or H-EASDF. The specific implementation method for the first communication device to send the DNS query to the second communication device according to the first rule can refer to the embodiment shown in Figure 2, and the description will not be repeated here. The second communication device is a communication device under the operator corresponding to the second PLMN ID. Optionally, the second communication device may be an EASDF. The EASDF may be an EASDF or V deployed under the operator corresponding to the second PLMN ID. -EASDF. The specific implementation method of the second communication device performing a DNS query and sending a DNS response can be referred to the embodiment shown in Figure 2, and the description will not be repeated here.

S504: The fourth communication device determines the first information according to the DNS response, and the first information includes the DNAI and/or the IP address or identification of the second UPF.

Optionally, the first information may also include core network tunnel information CN Tunnel Info corresponding to the PSA or UPF (ie, the second UPF) under the operator corresponding to the selected second PLMN ID, such as N9 tunnel information. The N9 tunnel information includes at least one of the following: N9 tunnel identifier, N9 tunnel address.

After receiving the DNS response, the fourth communication device may determine the first information according to the DNS response. Wherein, the first information may include DNAI and/or the IP address or identification of the second UPF, and DNAI may be used for the first PLMN ID pair. The corresponding operator performs user plane selection. The second UPF is the UPF under the operator corresponding to the second PLMN ID. The IP address or identification of the second UPF is used by the operator corresponding to the first PLMN ID to establish a PDU session to the second The operator corresponding to the PLMN ID.

Optionally, as an embodiment, the fourth communication device determines the first information based on the DNS response, which may include at least one of the following:

The fourth communication device determines the DNAI according to the EAS IP address and/or FQDN in the DNS response; the fourth communication device determines the second UPF according to the DNAI.

Optionally, after the fourth communication device determines the second UPF, it can also determine the core network tunnel information CN Tunnel Info corresponding to the second UPF, such as N9 tunnel information. The N9 tunnel information includes at least one of the following: N9 tunnel identifier, N9 tunnel address.

In this embodiment, the fourth communication device may only determine the DNAI based on the EAS IP address and/or FQDN without selecting the second UPF. In this case, the second UPF may be determined by the operator corresponding to the first PLMN ID. The third communication device under the third communication device makes a selection or the third communication device triggers the target network element under the operator corresponding to the second PLMN ID to select the second UPF. Alternatively, the fourth communication device can also determine the DNAI based on the EAS IP address and/or FQDN, and select the second UPF. In this case, the third communication device under the operator corresponding to the first PLMN ID may not need Make the selection of the second UPF.

S506: The fourth communication device sends the first information.

After determining the first information, the fourth communication device may send the first information to other devices.

Optionally, the fourth communication device sends the first information, which may include:

The fourth communication device sends the first information to the second communication device, and the second communication device is a communication device under the operator corresponding to the second PLMN ID; the signaling for sending the first information may be at least one of the following: Neasdf_DNSContext_Notify Request, Neasdf_DNSContext_Notify Response, Neasdf_DNSContext_Update Request, Neasdf_DNSContext_Update Response.

The fourth communication device sends the first information to the third communication device, and the third communication device is a communication device under the operator corresponding to the first PLMN ID. The signaling for sending the first information may be at least one of the following:

Nsmf_PDUSession_Create Request/Response，

Nsmf_PDUSession_Update Request/Response,

Nsmf_PDUSession_CreateSMContext Request/Response,

Nsmf_PDUSession_UpdateSMContext Request/Response,

Nsmf_PDUSession_SMContextStatusNotify,

Nsmf_PDUSession_StatusNotify,

Nsmf_PDUSession_ContextRequest,

Nsmf_PDUSession_ContextPush.

The second communication device may be an EASDF under the operator corresponding to the second PLMN ID. The third communication device may be an SMF under the operator corresponding to the first PLMN ID.

When the fourth communication device sends the first information to the third communication device, after receiving the first information, the third communication device may select a user plane according to the first information. When the fourth communication device sends the first information to the second communication device, the second communication device may send the first information to the first communication device under the operator corresponding to the first PLMN ID, and then the first communication device The device sends the first information to the third communication device under the operator corresponding to the first PLMN ID. After receiving the first information, the third communication device can select a user plane according to the first information. The specific implementation methods of the second communication device sending the first information to the first communication device, the first communication device sending the first information to the third communication device, and the third communication device selecting the user plane according to the first information can be seen in Figure 2 respectively. , the specific implementation of the corresponding steps in the embodiments described in Figures 3 and 4 will not be repeated here.

Optionally, as an embodiment, the fourth communication device may also perform the following steps:

The fourth communication device receives the third request, and the third request is used to request to establish or update a PDU session within the operator corresponding to the second PLMN ID;

The fourth communication device sends a third response. The third response includes the IP address of the second communication device and the second PLMN ID. The second communication device is a communication device under the operator corresponding to the second PLMN ID.

The third request may be: Nsmf_PDUSession_Create Request or Nsmf_PDUSession_Update Request.

Optionally, the third request may also include at least one of the following:

The third response may be: Nsmf_PDUSession_Create Response or Nsmf_PDUSession_Update Response.

Optionally, when the fourth communication device receives the third request, the fourth communication device may receive the third request after sending the first information, that is, the fourth communication device receives the third request when the fourth communication device sends the third request. After one message.

Optionally, the fourth communication device receives the third request, which may be the fourth communication device receiving the third request from the third communication device. The third communication device is a communication device under the operator corresponding to the first PLMN ID. Specifically, it may be an SMF or H-SMF deployed under the operator corresponding to the first PLMN ID. Correspondingly, the fourth communication device sends the third response, which may be the fourth communication device sending the third response to the third communication device. That is, when the third communication device wants to establish or update a PDU session in the operator corresponding to the second PLMN ID, it can send a third request to the fourth communication device. After receiving the third request, the fourth communication device can determine the third communication device. The IP address and/or the second PLMN ID of the second communication device under the operator corresponding to the second PLMN ID, and then the IP address and/or the second PLMN ID of the second communication device are sent to the third communication device.

Optionally, as an embodiment, the third response sent by the fourth communication device may also include third information, and the third information may include at least one of the following:

DNAI, DNAI is used by the operator corresponding to the first PLMN ID to select the user plane, and DNAI corresponds to the DNAI under the operator corresponding to the first PLMN ID;

The local PSA IP address under the operator corresponding to the second PLMN ID can also be the IP address or ID of the second UPF;

After the fourth communication device sends the third response to the third communication device, the third communication device can establish or update a PDU session in the operator corresponding to the second PLMN ID according to the third information in the third response, so that cross-platform communication can be achieved. The purpose of the operator's access to EAS.

In order to facilitate understanding of the technical solutions provided by the embodiments of the present application, four embodiments may be used as examples for description below.

Embodiment 1: The SMF (or H-SMF) under the operator corresponding to the first PLMN ID configures and feeds back the first rule (to the second PLMN) to the EASDF (or H-EASDF) under the operator corresponding to the first PLMN ID. Processing rules for domain names under the operator corresponding to the ID)

As shown in Figure 6, when SMF configures the first rule and feeds the first rule back to EASDF, the following steps can be included:

Step 1: AF provides the second information to NEF.

The second information includes at least one of the following:

Step 2: NEF stores the second information in the UDR.

Step 3: SMF receives the first request from EASDF, and the first request is used to request processing rules for FQDN.

EASDF may send a first request to SMF after receiving a DNS query containing a specific FQDN. Among them, the specific FQDN included in the DNS query is the domain name under the operator corresponding to the second PLMN ID, and EASDF cannot resolve the domain name.

Step 4: SMF sends a second request to NEF, and the second request is used to request to obtain the second information.

Step 5: NEF obtains the second information from the UDR.

Step 6: NEF sends a second response to SMF, and the second response contains the second information.

Step 7: SMF configures the first rule according to the second information.

Step 8: SMF sends the first response to EASDF, and the first response contains the first rule.

Based on the embodiment shown in Figure 6, SMF can configure the first rule, and when the terminal under the operator corresponding to the first PLMN ID needs to access EAS across operators, the SMF can feed back the first rule to EASDF so that EASDF can monitor the terminal. Sent DNS for processing.

Embodiment 2: Processing process of DNS query - only determine the DNAI of the roaming location

As shown in Figure 7, when the terminal under the operator corresponding to the first PLMN ID sends a DNS query request, the DNS processing may include the following steps:

Step 1: The UE sends a DNS query request to the EASDF under the operator corresponding to the first PLMN ID.

The UE is a terminal under the operator corresponding to the first PLMN ID, and the DNS query contains the FQDN under the operator corresponding to the second PLMN ID.

Step 2: The EASDF under the operator corresponding to the first PLMN ID sends a first request to the SMF under the operator corresponding to the first PLMN ID. The first request is used to request processing rules for FQDN.

Step 3: The SMF under the operator corresponding to the first PLMN ID sends the first response to the EASDF under the operator corresponding to the first PLMN ID, and the first response contains the first rule.

Step 4: The EASDF under the operator corresponding to the first PLMN ID sends a DNS query to the EASDF under the operator corresponding to the second PLMN ID according to the first rule.

The EASDF under the operator corresponding to the second PLMN ID can process or resolve the FQDN in the DNS query.

Step 5: The EASDF under the operator corresponding to the second PLMN ID forwards the DNS query to the DNS server.

The DNS server is the DNS server under the operator corresponding to the second PLMN ID.

Step 6: The EASDF under the operator corresponding to the second PLMN ID receives the EAS IP address corresponding to the FQDN from the DNS server.

Step 7: The EASDF under the operator corresponding to the second PLMN ID sends a DNS response to the EASDF under the operator corresponding to the first PLMN ID.

The DNS response contains the FQDN in the DNS query and the EAS IP address corresponding to the FQDN.

Step 8: The EASDF under the operator corresponding to the second PLMN ID sends a DNS response to the SMF under the operator corresponding to the second PLMN ID.

Step 7 and step 8 can be performed at the same time, or step 7 is performed first and then step 8 is performed, or step 8 is performed first and then step 7 is performed. There is no specific limitation here.

Step 9: The SMF under the operator corresponding to the second PLMN ID determines the DNAI based on the DNS response.

Step 10: The SMF under the operator corresponding to the second PLMN ID sends the first information to the SMF under the operator corresponding to the first PLMN ID, and the first information includes DNAI.

Step 11: The SMF under the operator corresponding to the second PLMN ID sends the first information to the EASDF under the operator corresponding to the second PLMN ID, and the first information contains DNAI.

Step 12: The EASDF under the operator corresponding to the second PLMN ID sends the first information to the EASDF under the operator corresponding to the first PLMN ID, and the first information includes DNAI.

Step 13: The EASDF under the operator corresponding to the first PLMN ID sends the first information to the SMF under the operator corresponding to the first PLMN ID. The first information includes DNAI.

It should be noted that the above-mentioned steps 10 to 13 are optional. For example, only step 10 may be performed without performing steps 11 to 13, or steps 11 to 13 may be performed without step 10.

Step 14: The SMF under the operator corresponding to the first PLMN ID performs user plane selection based on the first information.

When the SMF under the operator corresponding to the first PLMN ID selects the user plane based on the first information, it may include:

Select the first UPF and/or UL CL under the operator corresponding to the first PLMN ID according to the first information;

Select the second UPF under the operator corresponding to the second PLMN ID according to the first information, or trigger the SMF under the operator corresponding to the second PLMN ID to select the second UPF according to the first information.

Embodiment 3: DNS Query Processing—Determining DNAI Roamingly and Selecting the Second UPF

As shown in Figure 8, when the terminal under the operator corresponding to the first PLMN ID sends a DNS query request, the DNS processing may include the following steps:

Step 9: The SMF under the operator corresponding to the first PLMN ID determines the DNAI based on the DNS response and selects the second UPF based on the DNAI.

Step 10: The SMF under the operator corresponding to the second PLMN ID sends the first information to the SMF under the operator corresponding to the first PLMN ID. The first information includes the DNAI and the address or identification of the second UPF.

Step 11: The SMF under the operator corresponding to the second PLMN ID sends the first information to the EASDF under the operator corresponding to the second PLMN ID. The first information includes the DNAI and the address or identification of the second UPF.

Step 12: The EASDF under the operator corresponding to the second PLMN ID sends the first information to the EASDF under the operator corresponding to the first PLMN ID. The first information includes the DNAI and the address or identification of the second UPF.

Step 13: The EASDF under the operator corresponding to the first PLMN ID sends the first information to the SMF under the operator corresponding to the first PLMN ID. The first information includes the DNAI and the address or identification of the second UPF.

Select the first UPF and/or UL CL under the operator corresponding to the first PLMN ID according to the first information.

Embodiment 4: PDU session establishment process

As shown in Figure 9, when a PDU session is established or updated between the SMF under the operator corresponding to the first PLMN ID and the SMF under the operator corresponding to the second PLMN ID, the following steps may be included:

Step 1: The SMF under the operator corresponding to the first PLMN ID sends a third request to the SMF under the operator corresponding to the second PLMN ID. The third request is used to request establishment or update within the operator corresponding to the second PLMN ID. PDU session.

Step 2: The SMF under the operator corresponding to the second PLMN ID determines the IP address and/or the second PLMN ID of the EASDF under the operator corresponding to the second PLMN ID.

Step 3: The SMF under the operator corresponding to the second PLMN ID sends a third response to the SMF under the operator corresponding to the first PLMN ID. The third response contains the IP address of the EASDF and/or the second PLMN ID.

Step 4: The SMF under the operator corresponding to the second PLMN ID sends the third information to the SMF under the operator corresponding to the first PLMN ID.

The third information includes at least one of the following:

The local PSA IP address of the operator corresponding to the second PLMN ID;

The core network tunnel information CN Tunnel Info corresponding to the PSA under the operator corresponding to the second PLMN ID.

Optionally, the third information may be carried in the third response.

Step 5: The SMF under the operator corresponding to the first PLMN ID establishes or updates a PDU session with the SMF under the operator corresponding to the second PLMN ID based on the third response and the third information.

For the DNS query method provided by the embodiment of the present application, the execution subject may be a DNS query device. In the embodiment of the present application, the DNS query method performed by the DNS query device is used as an example to illustrate the DNS query device provided by the embodiment of the present application.

Figure 10 is a schematic structural diagram of a DNS query device according to an embodiment of the present application. This device may correspond to the first communication device in other embodiments. As shown in Figure 10, the device 1000 includes the following modules.

The receiving module 1001 is configured to receive a domain name system DNS query, the DNS query includes the fully qualified domain name FQDN, and the first communication device is a communication device under the operator corresponding to the first public land mobile network PLMN ID, and the FQDN It is the domain name under the operator corresponding to the second PLMN ID;

The sending module 1002 is configured to send the DNS query to a second communication device, where the second communication device is a communication device under the operator corresponding to the second PLMN ID.

Optionally, as an embodiment, the sending module 1002 is used to:

The DNS query is sent to the second communication device according to a first rule, the first rule is a processing rule for the FQDN, and the first rule is used to instruct the DNS query containing the FQDN to be sent to the second communication device. Second communication device.

Optionally, as an embodiment, the sending module 1002 is also configured to send a first request, where the first request is used to request processing rules for the FQDN;

The receiving module 1001 is also configured to receive a first response, where the first response contains the first rule.

Optionally, as an embodiment, the sending module 1002 is configured to send the first request to a third communication device. The third communication device is a communication device under the operator corresponding to the first PLMN ID. ;

The receiving module 1001 is configured to receive the first response from the third communication device.

Optionally, as an embodiment, the FQDN is a domain name under the operator corresponding to the second PLMN ID, including at least one of the following:

The FQDN is a domain name that can be processed or resolved by the equipment of the operator corresponding to the second PLMN ID;

Optionally, as an embodiment, the first rule is also used to indicate the address information of the second communication device;

Among them, the sending module 1002 is also used for:

The DNS query is sent according to the address information indicated by the first rule.

Optionally, as an embodiment, the receiving module 1001 is also used to:

Receive DNS response;

Wherein, the DNS response includes the FQDN and the edge application server Internet Protocol EAS IP address corresponding to the FQDN.

Optionally, as an embodiment, the receiving module 1001 is also used to:

The DNS response is received from a second communication device, which is a communication device under the operator corresponding to the second PLMN ID.

Optionally, as an embodiment, the receiving module 1001 is also configured to receive first information, where the first information includes the data network access identifier DNAI and/or the IP address or identification of the second user plane UPF;

The sending module 1002 is also used to send the first information;

Wherein, the DNAI is used for user plane selection by the operator corresponding to the first PLMN ID, the DNAI is determined based on the EAS IP address and/or the FQDN in the DNS response, and the second UPF For the UPF under the operator corresponding to the second PLMN ID, the IP address or identification of the second UPF is used by the operator corresponding to the first PLMN ID to establish a protocol data unit PDU session to the second PLMN. The operator corresponding to the ID, the second UPF is determined based on the DNAI.

Optionally, as an embodiment, the receiving module 1001 is also used to:

The first information is received from a second communication device, which is a communication device under an operator corresponding to the second PLMN ID.

Optionally, as an embodiment, the sending module 1002 is also used to:

Send the first information to a third communication device, where the third communication device is a communication device under the operator corresponding to the first PLMN ID.

The device 1000 according to the embodiment of the present application can refer to the process of the method 200 corresponding to the embodiment of the present application, and each unit/module in the device 1000 and the above-mentioned other operations and/or functions are respectively to implement the corresponding process in the method 200, And can achieve the same or equivalent technical effects. For the sake of simplicity, they will not be described again here.

Figure 11 is a schematic structural diagram of a DNS query device according to an embodiment of the present application. This device may correspond to the second communication device in other embodiments. As shown in Figure 11, the device 1100 includes the following modules.

The receiving module 1101 is used to receive a DNS query. The DNS query is sent by a first communication device. The first communication device is a communication device under the operator corresponding to the first PLMN ID. The DNS query contains the FQDN, so The FQDN is the domain name under the operator corresponding to the second PLMN ID, and the second communication device is the communication device under the operator corresponding to the second PLMN ID;

The sending module 1102 is used to forward the DNS query to the DNS server to obtain the EAS IP address corresponding to the FQDN.

Optionally, as an embodiment, the sending module 1102 is also used to:

Send DNS response;

Wherein, the DNS query response includes the FQDN and the EAS IP address.

Optionally, as an embodiment, the sending module 1102 is used for at least one of the following:

Send the DNS response to the first communication device;

Send the DNS response to a fourth communication device, the fourth communication device is a communication device under the operator corresponding to the second PLMN ID, and the DNS response is used to under the operator corresponding to the second PLMN ID User interface selection.

Optionally, as an embodiment, the receiving module 1101 is configured to receive first information, where the first information includes DNAI and/or the IP address or identification of the second UPF;

The sending module 1102 is used to send the first information;

Optionally, as an embodiment, the receiving module 1101 is used to:

The first information is received from a fourth communication device, which is a communication device under the operator corresponding to the second PLMN ID.

Optionally, as an embodiment, the sending module 1102 is used to:

Send the first information to the first communications device.

The device 1100 according to the embodiment of the present application can refer to the process corresponding to the method 300 of the embodiment of the present application, and each unit/module in the device 1100 and the above-mentioned other operations and/or functions are respectively to implement the corresponding process in the method 300, And can achieve the same or equivalent technical effects. For the sake of simplicity, they will not be described again here.

Figure 12 is a schematic structural diagram of a DNS query device according to an embodiment of the present application. This device may correspond to a third communication device in other embodiments. As shown in Figure 12, the device 1200 includes the following modules.

The receiving module 1201 is used to receive a first request. The first request is used to request processing rules for FQDN. The FQDN is the domain name under the operator corresponding to the second PLMN ID. The third communication device is the first Communication equipment under the operator corresponding to the PLMN ID;

Sending module 1202, configured to send a first response, the first response includes a first rule, the first rule is a processing rule for the FQDN, and the first rule is used to indicate that the DNS containing the FQDN will be Inquiries sent to A second communication device, the second communication device is a communication device under the operator corresponding to the second PLMN ID.

Optionally, as an embodiment, the receiving module 1201 is used to:

The first request is received from a first communication device, which is a communication device under the operator corresponding to the first PLMN ID. The first request is received by the first communication device after receiving DNS Sent in case of query, the DNS query contains the FQDN;

Among them, the sending module 1202 is used for:

Send the first response to the first communications device.

Optionally, as an embodiment, the first rule is also used to indicate the address information of the second communication device.

Optionally, as an embodiment, the device 1200 also includes a configuration module 1203, wherein:

The sending module 1202 is used to send a second request, and the second request is used to request to obtain second information;

The receiving module 1201 is configured to receive a second response, where the second response contains the second information;

The configuration module 1203 is used to configure the first rule according to the second information;

Wherein, the second information includes at least one of the following:

The mapping relationship between the FQDN and the PLMN ID, where the PLMN ID is the PLMN ID to which the operator that can parse the FQDN belongs;

Optionally, as an embodiment, the sending module 1202 is used to:

Send the second request to the network opening function NEF;

Among them, the receiving module 1201 is used for:

The second response is received from the NEF.

Optionally, as an embodiment, the second information is obtained by the NEF from the unified data storage UDR, the second information is provided by the application function AF and is pre-stored by the AF to the NEF through the NEF. described in the UDR.

Optionally, as an embodiment, the device 1200 further includes a determining module 1204, wherein:

The receiving module 1201 is also configured to receive first information, where the first information includes DNAI and/or the IP address or identification of the second UPF;

The determination module 1204 is used to select a user plane according to the first information;

Wherein, the DNAI is used for user plane selection by the operator corresponding to the first PLMN ID, the DNAI is determined based on the EAS IP address and/or the FQDN in the DNS response, and the second UPF For the UPF under the operator corresponding to the second PLMN ID, the IP address or identification of the second UPF is used by the operator corresponding to the first PLMN ID to establish a PDU session to the operator corresponding to the second PLMN ID. Operator, the second UPF is determined based on the DNAI.

Optionally, as an embodiment, the determination module 1204 is used for at least one of the following:

Select the first UPF and/or UL CL uplink splitter under the operator corresponding to the first PLMN ID according to the first information;

Select the second UPF under the operator corresponding to the second PLMN ID according to the first information, or trigger the target network element under the operator corresponding to the second PLMN ID to select the second UPF according to the first information, The target network element includes a fourth communication device, and the fourth communication device is a communication device under the operator corresponding to the second PLMN ID.

Optionally, as an embodiment, the receiving module 1201 is also used for at least one of the following:

the third communication device receives the first information from the first communication device;

The third communication device receives the first information from a fourth communication device, and the fourth communication device is a communication device under the operator corresponding to the second PLMN ID.

Optionally, as an embodiment, the sending module 1202 is also configured to send a third request, where the third request is used to request the establishment or update of a PDU session within the operator corresponding to the second PLMN ID;

The receiving module 1201 is also configured to receive a third response, where the third response includes the IP address of a second communication device and/or the second PLMN ID, and the second communication device is the second PLMN. The communication device under the operator corresponding to the ID.

Optionally, as an embodiment, the sending module 1202 is used to:

Send the third request to a fourth communication device, where the fourth communication device is a communication device under the operator corresponding to the second PLMN ID;

Among them, the receiving module 1201 is used for:

The third response is received from the fourth communications device.

Optionally, as an embodiment, the third response also includes third information, and the third information includes at least one of the following:

DNAI, the DNAI is used for user plane selection by the operator corresponding to the first PLMN ID, and the DNAI corresponds to the DNAI under the operator corresponding to the first PLMN ID;

The local PSA IP address of the operator corresponding to the second PLMN ID;

Core network tunnel information CN Tunnel Info corresponding to the PSA under the operator corresponding to the second PLMN ID.

The device 1200 according to the embodiment of the present application can refer to the process corresponding to the method 400 of the embodiment of the present application, and each unit/module and the above-mentioned other operations and/or functions in the device 1200 are respectively to implement the corresponding process in the method 400, And can achieve the same or equivalent technical effects. For the sake of simplicity, they will not be described again here.

Figure 13 is a schematic structural diagram of a DNS query device according to an embodiment of the present application. This device may correspond to the fourth communication device in other embodiments. As shown in Figure 13, the device 1300 includes the following modules.

The receiving module 1301 is used to receive a DNS response. The fourth communication device is a communication device under the operator corresponding to the second PLMN ID. The DNS response includes the FQDN and the EAS IP address corresponding to the FQDN;

Determining module 1302, configured to determine first information according to the DNS response, where the first information includes DNAI and/or the IP address or identification of the second UPF;

Sending module 1303, used to send the first information;

Wherein, the DNAI is used for user plane selection by the operator corresponding to the first PLMN ID, the second UPF is the UPF under the operator corresponding to the second PLMN ID, and the IP address of the second UPF or The identifier is used by the operator corresponding to the first PLMN ID to establish a PDU session to the operator corresponding to the second PLMN ID.

Optionally, as an embodiment, the receiving module 1301 is used to:

receiving the DNS response from the second communications device;

Wherein, the second communication device is a communication device under the operator corresponding to the second PLMN ID, and the EAS IP address is obtained by the second communication device forwarding a DNS query to a DNS server, and the DNS The query is sent by the first communication device, which is a communication device under the operator corresponding to the first PLMN ID, and the DNS query includes the FQDN.

Optionally, as an embodiment, the determination module 1302 is used for at least one of the following:

Determine the DNAI based on the EAS IP address and/or the FQDN in the DNS response;

The second UPF is determined based on the DNAI.

Optionally, as an embodiment, the sending module 1303 is used to:

Send the first information to a second communication device, where the second communication device is a communication device under the operator corresponding to the second PLMN ID;

Send the first information to a third communication device, where the third communication device is a communication device under an operator corresponding to the first PLMN ID.

Optionally, as an embodiment, the receiving module 1301 is also configured to receive a third request, where the third request is used to request to establish or update a PDU session within the operator corresponding to the second PLMN ID;

The sending module 1303 is also used to send a third response. The third response includes the IP address of the second communication device and the second PLMN ID. The second communication device corresponds to the second PLMN ID. communications equipment under the operator.

Optionally, as an embodiment, the receiving module 1301 is used to:

Receive the third request from a third communication device, where the third communication device is a communication device under the operator corresponding to the first PLMN ID;

Among them, the sending module 1303 is used for:

Send the third response to the third communication device.

The local PSA IP address of the operator corresponding to the second PLMN ID;

The core network tunnel information corresponding to the PSA under the operator corresponding to the second PLMN ID.

The device 1300 according to the embodiment of the present application can refer to the process corresponding to the method 500 of the embodiment of the present application, and each unit/module and the above-mentioned other operations and/or functions in the device 1300 are respectively to implement the corresponding process in the method 500, And can achieve the same or equivalent technical effects. For the sake of simplicity, they will not be described again here.

The DNS query device in the embodiment of the present application may be an electronic device, such as an electronic device with an operating system, or may be a component in the electronic device, such as an integrated circuit or chip. The electronic device may be a terminal or other devices other than the terminal. For example, terminals may include but are not limited to the types of terminals 11 listed above, and other devices may be servers, network attached storage (Network Attached Storage, NAS), etc., which are not specifically limited in the embodiment of this application.

The DNS query device provided by the embodiments of the present application can implement each process implemented by the method embodiments of Figures 2 to 9, and achieve the same technical effect. To avoid duplication, the details will not be described here.

Optionally, as shown in Figure 14, this embodiment of the present application also provides a communication device 1400, including a processor m01 and a memory 1402. The memory 1402 stores programs or instructions that can be run on the processor 1401, for example , when the communication device 1400 is the first communication device, when the program or instruction is executed by the processor 1401, each step of the DNS query method embodiment shown in FIG. 2 is implemented, and the same technical effect can be achieved. The communication device 1400 When it is a second communication device, when the program or instruction is executed by the processor 1401, the DNS query method shown in Figure 3 is implemented. Each step of the method embodiment can achieve the same technical effect. When the communication device 1400 is a third communication device, when the program or instruction is executed by the processor 1401, each step of the DNS query method embodiment shown in Figure 4 is implemented. steps, and can achieve the same technical effect. When the communication device 1400 is the fourth communication device, when the program or instruction is executed by the processor 1401, each step of the DNS query method embodiment shown in Figure 5 is implemented, and can achieve The same technical effects are not repeated here to avoid repetition.

Embodiments of the present application also provide a communication device, including a processor and a communication interface. The communication interface is used to receive a domain name system DNS query. The DNS query includes a fully qualified domain name FQDN. The communication device is the first public land mobile network. The communication device under the operator corresponding to the PLMN ID, the FQDN is the domain name under the operator corresponding to the second PLMN ID; sending the DNS query to the second communication device, the second communication device is the domain name corresponding to the second PLMN ID A communication device under the operator; or, the communication interface is used to receive a DNS query, the DNS query is sent by the first communication device, and the first communication device is a communication device under the operator corresponding to the first PLMN ID, so The DNS query includes FQDN, the FQDN is the domain name under the operator corresponding to the second PLMN ID, and the communication device is the communication device under the operator corresponding to the second PLMN ID; forward the DNS query to DNS The server obtains the EAS IP address corresponding to the FQDN; or, the communication interface is used to receive the first request, the first request is used to request the processing rules for the FQDN, and the FQDN is the operator under the corresponding second PLMN ID. domain name, the communication device is a communication device under the operator corresponding to the first PLMN ID; send a first response, the first response contains a first rule, and the first rule is the processing rule of the FQDN, The first rule is used to instruct the DNS query containing the FQDN to be sent to a second communication device, and the second communication device is a communication device under the operator corresponding to the second PLMN ID; or, the communication interface is used to receive DNS response, the communication device is a communication device under the operator corresponding to the second PLMN ID, the DNS response includes the FQDN and the EAS IP address corresponding to the FQDN; the processor is used to determine the first response according to the DNS response Information, the first information includes DNAI and/or the IP address or identification of the second UPF; the communication interface is used to send the first information; wherein the DNAI is used for the operator corresponding to the first PLMN ID to conduct user plane Select, the second UPF is the UPF under the operator corresponding to the second PLMN ID, and the IP address or identification of the second UPF is used for the operator corresponding to the first PLMN ID to establish a PDU session to the operator. The operator corresponding to the second PLMN ID. This communication device embodiment corresponds to the above communication device side method embodiment. Each implementation process and implementation method of the above method embodiment can be applied to this communication device embodiment, and can achieve the same technical effect. Specifically, FIG. 15 is a schematic diagram of the hardware structure of a communication device that implements an embodiment of the present application.

The terminal 1500 includes but is not limited to: a radio frequency unit 1501, a network module 1502, an audio output unit 1503, an input unit 1504, a sensor 1505, a display unit 1506, a user input unit 1507, an interface unit 1508, a memory 1509, a processor 1510, etc. At least some parts.

Those skilled in the art can understand that the terminal 1500 may also include a power supply (such as a battery) that supplies power to various components. The power supply may be logically connected to the processor 1510 through a power management system, thereby managing charging, discharging, and power consumption through the power management system. Management and other functions. The terminal structure shown in FIG. 15 does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown in the figure, or some components may be combined or arranged differently, which will not be described again here.

It should be understood that in the embodiment of the present application, the input unit 1504 may include a graphics processing unit (GPU) 15041 and a microphone 15042. The GPU 15041 is used for recording data by an image capture device (such as a camera) in the video capture mode or the image capture mode. The image data obtained from still pictures or videos is processed. The display unit 1506 may include a display panel 15061, which may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like. The user input unit 1507 includes a touch panel 15071 and at least one of other input devices 15072 . Touch panel 15071, also known as touch screen. The touch panel 15071 may include two parts: a touch detection device and a touch controller. Other input devices 15072 may include but are not limited to physical keyboards, function keys (such as volume control keys, switch keys, etc.), trackballs, mice, and joysticks, which will not be described again here.

In this embodiment of the present application, after receiving downlink data from the network side device, the radio frequency unit 1501 can transmit it to the processor 1510 for processing; in addition, the radio frequency unit 1501 can send uplink data to the network side device. Generally, the radio frequency unit 1501 includes, but is not limited to, an antenna, amplifier, transceiver, coupler, low noise amplifier, duplexer, etc.

Memory 1509 may be used to store software programs or instructions as well as various data. The memory 1509 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, an application program or instructions required for at least one function (such as a sound playback function, Image playback function, etc.) etc. Additionally, memory 1509 may include volatile memory or nonvolatile memory, or memory 1509 may include both volatile and nonvolatile memory. Among them, non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), electrically removable memory. Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory. Volatile memory can be random access memory (Random Access Memory, RAM), static random access memory (Static RAM, SRAM), dynamic random access memory (Dynamic RAM, DRAM), synchronous dynamic random access memory (Synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDRSDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (Synch link DRAM) , SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DRRAM). Memory 1509 in embodiments of the present application includes, but is not limited to, these and any other suitable types of memory.

The processor 1510 may include one or more processing units; optionally, the processor 1510 integrates an application processor and a debugger. Modem and demodulation processor, among which the application processor mainly processes operations involving the operating system, user interface and application programs, etc., and the modem and demodulation processor mainly processes wireless communication signals, such as baseband processor. It can be understood that the above modem processor may not be integrated into the processor 1510.

Among them, the radio frequency unit 1501 is used to receive a domain name system DNS query, the DNS query includes the fully qualified domain name FQDN, and the communication device is a communication device under the operator corresponding to the first public land mobile network PLMN ID, and the FQDN is the domain name under the operator corresponding to the second PLMN ID; sends the DNS query to the second communication device, which is the communication device under the operator corresponding to the second PLMN ID; or, the radio frequency unit 1501, Used to receive DNS queries. The DNS queries are sent by the first communication device. The first communication device is the communication device under the operator corresponding to the first PLMN ID. The DNS query contains the FQDN, and the FQDN is the first PLMN ID. The domain name under the operator corresponding to the second PLMN ID, and the communication device is the communication device under the operator corresponding to the second PLMN ID; forward the DNS query to the DNS server to obtain the EAS IP address corresponding to the FQDN; Or, the radio frequency unit 1501 is configured to receive a first request, the first request is used to request processing rules for FQDN, the FQDN is the domain name under the operator corresponding to the second PLMN ID, and the communication device is the first The communication device under the operator corresponding to the PLMN ID; sends a first response, the first response contains a first rule, the first rule is a processing rule for the FQDN, and the first rule is used to indicate that the The DNS query of the FQDN is sent to a second communication device, which is a communication device under the operator corresponding to the second PLMN ID; or, the radio frequency unit 1501 is used to receive a DNS response, and the communication device is The communication device under the operator corresponding to the second PLMN ID, the DNS response includes the FQDN and the EAS IP address corresponding to the FQDN; the processor 1510 is used to determine the first information according to the DNS response, the third A piece of information includes DNAI and/or the IP address or identification of the second UPF; the radio frequency unit 1501 is used to send the first information; wherein the DNAI is used for the operator corresponding to the first PLMN ID to select the user plane, so The second UPF is a UPF under the operator corresponding to the second PLMN ID, and the IP address or identification of the second UPF is used by the operator corresponding to the first PLMN ID to establish a PDU session to the second The operator corresponding to the PLMN ID.

Embodiments of the present application also provide a communication device, including a processor and a communication interface. The communication interface is used to receive a domain name system DNS query. The DNS query includes a fully qualified domain name FQDN. The communication device is the first public land mobile network. A communication device under the operator corresponding to the PLMN ID, and the FQDN is the domain name under the operator corresponding to the second PLMN ID; sending the DNS query to the second communication device, the second communication device being the second PLMN ID a communication device under the corresponding operator; or, the communication interface is used to receive a DNS query, the DNS query is sent by a first communication device, and the first communication device is a communication device under the operator corresponding to the first PLMN ID, The DNS query includes FQDN, the FQDN is the domain name under the operator corresponding to the second PLMN ID, and the communication device is the communication device under the operator corresponding to the second PLMN ID; forward the DNS query to DNS server, obtains the EAS IP address corresponding to the FQDN; or, the communication interface is used to receive a first request, the first request is used to request processing rules for the FQDN, and the FQDN is the operator corresponding to the second PLMN ID domain name under, the communication device is a communication device under the operator corresponding to the first PLMN ID; send a first response, the first response contains a first rule, the first rule is the processing rule of the FQDN , the first rule is used to instruct the DNS query containing the FQDN to be sent to a second communication device, and the second communication device is a communication device under the operator corresponding to the second PLMN ID; or, the communication interface is used to Receive a DNS response, the communication device is a communication device under the operator corresponding to the second PLMN ID, and the DNS response includes the FQDN and the EAS IP address corresponding to the FQDN; the processor is configured to determine the second PLMN according to the DNS response. Information, the first information includes DNAI and/or the IP address or identification of the second UPF; the communication interface is used to send the first information; wherein the DNAI is used by the operator corresponding to the first PLMN ID to conduct user The second UPF is a UPF under the operator corresponding to the second PLMN ID, and the IP address or identification of the second UPF is used to establish a PDU session to the operator corresponding to the first PLMN ID. The operator corresponding to the second PLMN ID. This communication device embodiment corresponds to the above-mentioned communication device method embodiment. Each implementation process and implementation manner of the above-mentioned method embodiment can be applied to this communication device embodiment, and can achieve the same technical effect.

Specifically, the embodiment of the present application also provides a communication device. As shown in Figure 16, the communication device 1600 includes: a processor 1601, a network interface 1602 and a memory 1603. Among them, the network interface 1602 is, for example, a common public radio interface (CPRI).

Specifically, the communication device 1600 of the embodiment of the present invention also includes: instructions or programs stored in the memory 1603 and executable on the processor 1601. The processor 1601 calls the instructions or programs in the memory 1603 to execute the steps shown in FIGS. 10 to 13 . It shows the execution method of each module and achieves the same technical effect. To avoid duplication, it will not be repeated here.

Embodiments of the present application also provide a readable storage medium. Programs or instructions are stored on the readable storage medium. When the program or instructions are executed by a processor, each process of the above DNS query method embodiment is implemented, and the same can be achieved. The technical effects will not be repeated here to avoid repetition.

Wherein, the processor is the processor in the terminal described in the above embodiment. The readable storage medium includes computer readable storage media, such as computer read-only memory ROM, random access memory RAM, magnetic disk or optical disk, etc.

An embodiment of the present application further provides a chip. The chip includes a processor and a communication interface. The communication interface and The processor is coupled, and the processor is used to run programs or instructions to implement each process of the above DNS query method embodiment, and can achieve the same technical effect. To avoid duplication, the details will not be described here.

It should be understood that the chips mentioned in the embodiments of this application may also be called system-on-chip, system-on-a-chip, system-on-chip or system-on-chip, etc.

Embodiments of the present application further provide a computer program/program product. The computer program/program product is stored in a storage medium. The computer program/program product is executed by at least one processor to implement the above DNS query method embodiment. Each process can achieve the same technical effect. To avoid repetition, we will not go into details here.

Embodiments of the present application also provide a DNS query system, including: at least two of a first communication device, a second communication device, a third communication device and a fourth communication device. The first communication device may be used to perform: The steps of the DNS query method shown in Figure 2. The second communication device can be used to perform the steps of the DNS query method shown in Figure 3. The third communication device can be used to perform the DNS query method shown in Figure 4. The fourth communication device may be used to perform the steps of the DNS query method shown in Figure 5.

It should be noted that, in this document, the terms "comprising", "comprises" or any other variations thereof are intended to cover a non-exclusive inclusion, such that a process, method, article or device that includes a series of elements not only includes those elements, It also includes other elements not expressly listed or inherent in the process, method, article or apparatus. Without further limitation, an element defined by the statement "comprises a..." does not exclude the presence of additional identical elements in a process, method, article or apparatus that includes that element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, but may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved. Functions may be performed, for example, the methods described may be performed in an order different from that described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus the necessary general hardware platform. Of course, it can also be implemented by hardware, but in many cases the former is better. implementation. Based on this understanding, the technical solution of the present application can be embodied in the form of a computer software product that is essentially or contributes to the existing technology. The computer software product is stored in a storage medium (such as ROM/RAM, disk , CD), including several instructions to cause a terminal (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in various embodiments of this application.

The embodiments of the present application have been described above in conjunction with the accompanying drawings. However, the present application is not limited to the above-mentioned specific implementations. The above-mentioned specific implementations are only illustrative and not restrictive. Those of ordinary skill in the art will Inspired by this application, many forms can be made without departing from the purpose of this application and the scope protected by the claims, all of which fall within the protection of this application.

Claims

A DNS query method, including:

The first communication device receives a domain name system DNS query. The DNS query includes the fully qualified domain name FQDN. The first communication device is a communication device under the operator corresponding to the first public land mobile network PLMN ID. The FQDN is the first public land mobile network PLMN ID. 2. The domain name under the operator corresponding to the PLMN ID;

The first communication device sends the DNS query to a second communication device, and the second communication device is a communication device under the operator corresponding to the second PLMN ID.
The method of claim 1, wherein the first communication device sending the DNS query to the second communication device includes:

The first communication device sends the DNS query to the second communication device according to a first rule, the first rule is a processing rule for the FQDN, and the first rule is used to indicate that the DNS query containing the FQDN will be A DNS query is sent to the second communications device.
The method according to claim 2, wherein when the first communication device receives the DNS query, the method further includes:

The first communication device sends a first request, the first request is used to request processing rules for the FQDN;

The first communication device receives a first response, where the first response includes the first rule.
The method of claim 3, wherein the first communication device sending the first request includes:

The first communication device sends the first request to a third communication device, and the third communication device is a communication device under the operator corresponding to the first PLMN ID;

Wherein, the first communication device receives a first response, including:

The first communications device receives the first response from the third communications device.
The method according to claim 1, wherein the FQDN is a domain name under an operator corresponding to the second PLMN ID, including at least one of the following:

The FQDN is a domain name that can be processed or resolved by the equipment of the operator corresponding to the second PLMN ID;

The equipment under the operator corresponding to the first PLMN ID cannot resolve the FQDN.
The method according to claim 2, wherein the first rule is also used to indicate address information of the second communication device;

Wherein, the first communication device sends the DNS query to the second communication device according to the first rule, including:

The first communication device sends the DNS query to the second communication device according to the address information indicated by the first rule.
The method of claim 1, further comprising:

The first communication device receives a DNS response;

Wherein, the DNS response includes the FQDN and the edge application server Internet Protocol EAS IP address corresponding to the FQDN.
The method of claim 7, wherein the first communication device receives a DNS response, comprising:

The first communication device receives the DNS response from a second communication device, and the second communication device is a communication device under the operator corresponding to the second PLMN ID.
The method of claim 7, further comprising:

The first communication device receives first information, where the first information includes the data network access identifier DNAI and/or the IP address or identification of the second user plane UPF;

The first communication device sends the first information;

Wherein, the DNAI is used for user plane selection by the operator corresponding to the first PLMN ID, the DNAI is determined based on the EAS IP address and/or the FQDN in the DNS response, and the second UPF For the UPF under the operator corresponding to the second PLMN ID, the IP address or identification of the second UPF is used by the operator corresponding to the first PLMN ID to establish a protocol data unit PDU session to the second PLMN. The operator corresponding to the ID, the second UPF is determined based on the DNAI.
The method of claim 9, wherein the first communication device receiving the first information includes:

The first communication device receives the first information from a second communication device, and the second communication device is a communication device under the operator corresponding to the second PLMN ID.
The method of claim 9, wherein the first communication device sending the first information includes:

The first communication device sends the first information to a third communication device, and the third communication device is a communication device under the operator corresponding to the first PLMN ID.
A DNS query method, including:

The second communication device receives a DNS query. The DNS query is sent by the first communication device. The first communication device is a communication device under the operator corresponding to the first PLMN ID. The DNS query contains FQDN. The FQDN is the domain name under the operator corresponding to the second PLMN ID, and the second communication device is the communication device under the operator corresponding to the second PLMN ID;

The second communication device forwards the DNS query to the DNS server to obtain the FQDN corresponding EAS IP address.
The method according to claim 12, wherein the FQDN is a domain name under an operator corresponding to the second PLMN ID, including at least one of the following:

The FQDN is a domain name that can be processed or resolved by the equipment of the operator corresponding to the second PLMN ID;

The equipment under the operator corresponding to the first PLMN ID cannot resolve the FQDN.
The method of claim 12, further comprising:

The second communication device sends a DNS response;

Wherein, the DNS query response includes the FQDN and the EAS IP address.
The method of claim 14, wherein the second communication device sends a DNS response including at least one of the following:

The second communication device sends the DNS response to the first communication device;

The second communication device sends the DNS response to a fourth communication device, the fourth communication device is a communication device under the operator corresponding to the second PLMN ID, and the DNS response is used for the second PLMN User plane selection under the operator corresponding to the ID.
The method of claim 14, wherein the method further includes:

The second communication device receives first information, where the first information includes DNAI and/or the IP address or identification of the second UPF;

The second communication device sends the first information;

Wherein, the DNAI is used for user plane selection by the operator corresponding to the first PLMN ID, the DNAI is determined based on the EAS IP address and/or the FQDN in the DNS response, and the second UPF For the UPF under the operator corresponding to the second PLMN ID, the IP address or identification of the second UPF is used by the operator corresponding to the first PLMN ID to establish a protocol data unit PDU session to the second PLMN. The operator corresponding to the ID, the second UPF is determined based on the DNAI.
The method of claim 16, wherein the second communication device receiving the first information includes:

The second communication device receives the first information from a fourth communication device, and the fourth communication device is a communication device under the operator corresponding to the second PLMN ID.
The method of claim 16, wherein the second communication device sending the first information includes:

The second communication device sends the first information to the first communication device.
A DNS query method, including:

The third communication device receives the first request. The first request is used to request processing rules for FQDN. The FQDN is the domain name under the operator corresponding to the second PLMN ID. The third communication device is the first PLMN ID. Communication equipment under the corresponding operator;

The third communication device sends a first response, the first response contains a first rule, the first rule is a processing rule for the FQDN, and the first rule is used to indicate that the DNS containing the FQDN The query is sent to the second communication device, which is a communication device under the operator corresponding to the second PLMN ID.
The method according to claim 19, wherein the FQDN is a domain name under an operator corresponding to the second PLMN ID, including at least one of the following:

The FQDN is a domain name that can be processed or resolved by the equipment of the operator corresponding to the second PLMN ID;

The equipment under the operator corresponding to the first PLMN ID cannot resolve the FQDN.
The method of claim 19, wherein the third communication device receiving the first request includes:

The third communication device receives the first request from the first communication device. The first communication device is a communication device under the operator corresponding to the first PLMN ID. The first request is generated by the first communication device. The communication device sends upon receiving a DNS query, the DNS query containing the FQDN;

Wherein, the third communication device sends a first response, including:

The third communication device sends the first response to the first communication device.
The method of claim 19, wherein the first rule is further used to indicate address information of the second communication device.
The method according to claim 19, wherein when the third communication device receives the first request, the method further includes:

The third communication device sends a second request, the second request is used to request to obtain second information;

The third communication device receives a second response, where the second response includes the second information;

The third communication device configures the first rule according to the second information;

Wherein, the second information includes at least one of the following:

The mapping relationship between the FQDN and the PLMN ID, where the PLMN ID is the PLMN ID to which the operator that can parse the FQDN belongs;

The address information of the network element that can resolve the FQDN and/or the PLMN ID to which the network element belongs.
The method of claim 23, wherein the third communication device sends a second request, including:

The third communication device sends the second request to the network opening function NEF;

Wherein, the third communication device receives a second response, including:

The third communications device receives the second response from the NEF.
The method of claim 24, wherein:

The second information is obtained by the NEF from the unified data storage UDR. The second information is provided by the application function AF and is pre-stored into the UDR by the AF through the NEF.
The method of claim 19, further comprising:

The third communication device receives first information, where the first information includes DNAI and/or the IP address or identification of the second UPF;

The third communication device selects a user plane according to the first information;

Wherein, the DNAI is used for user plane selection by the operator corresponding to the first PLMN ID, the DNAI is determined based on the EAS IP address and/or the FQDN in the DNS response, and the second UPF For the UPF under the operator corresponding to the second PLMN ID, the IP address or identification of the second UPF is used by the operator corresponding to the first PLMN ID to establish a PDU session to the operator corresponding to the second PLMN ID. Operator, the second UPF is determined based on the DNAI.
The method according to claim 26, wherein the third communication device selects a user plane according to the first information, including at least one of the following:

The third communication device selects the first UPF and/or UL CL uplink splitter under the operator corresponding to the first PLMN ID according to the first information;

The third communication device selects a second UPF under the operator corresponding to the second PLMN ID according to the first information, or the third communication device triggers the second UPF corresponding to the second PLMN ID according to the first information. The target network element under the operator selects the second UPF. The target network element includes a fourth communication device. The fourth communication device is a communication device under the operator corresponding to the second PLMN ID.
The method of claim 26, wherein the third communication device receives the first information including at least one of the following:

the third communication device receives the first information from the first communication device;

The third communication device receives the first information from a fourth communication device, and the fourth communication device is a communication device under the operator corresponding to the second PLMN ID.
The method of claim 19, further comprising:

The third communication device sends a third request, the third request is used to request to establish or update a PDU session within the operator corresponding to the second PLMN ID;

The third communication device receives a third response, the third response includes the IP address of the second communication device and/or the second PLMN ID, and the second communication device is corresponding to the second PLMN ID. under the operator communication device.
The method of claim 29, wherein the third communication device sends a third request, including:

The third communication device sends the third request to a fourth communication device, and the fourth communication device is a communication device under the operator corresponding to the second PLMN ID;

Wherein, the third communication device receives a third response, including:

The third communication device receives the third response from the fourth communication device.
The method of claim 29, wherein the third response further includes third information, and the third information includes at least one of the following:

DNAI, the DNAI is used for user plane selection by the operator corresponding to the first PLMN ID, and the DNAI corresponds to the DNAI under the operator corresponding to the first PLMN ID;

The local PSA IP address of the operator corresponding to the second PLMN ID;

The core network tunnel information CN Tunnel Info corresponding to the PSA under the operator corresponding to the second PLMN ID.
A DNS query method, including:

The fourth communication device receives a DNS response, the fourth communication device is a communication device under the operator corresponding to the second PLMN ID, and the DNS response includes the FQDN and the EAS IP address corresponding to the FQDN;

The fourth communication device determines first information based on the DNS response, where the first information includes DNAI and/or the IP address or identification of the second UPF;

The fourth communication device sends the first information; wherein the DNAI is used for the operator corresponding to the first PLMN ID to select the user plane, and the second UPF is the operator corresponding to the second PLMN ID. Under the UPF, the IP address or identification of the second UPF is used by the operator corresponding to the first PLMN ID to establish a PDU session to the operator corresponding to the second PLMN ID.
The method of claim 32, wherein the fourth communication device receives a DNS response, comprising:

The fourth communication device receives the DNS response from the second communication device;

Wherein, the second communication device is a communication device under the operator corresponding to the second PLMN ID, and the EAS IP address is obtained by the second communication device forwarding a DNS query to a DNS server, and the DNS The query is sent by the first communication device, which is a communication device under the operator corresponding to the first PLMN ID, and the DNS query includes the FQDN.
The method according to claim 32, wherein the FQDN is the second PLMN ID corresponding to The domain name under the operator includes at least one of the following:

The FQDN is a domain name that can be processed or resolved by the equipment of the operator corresponding to the second PLMN ID;

The equipment under the operator corresponding to the first PLMN ID cannot resolve the FQDN.
The method of claim 32, wherein the fourth communication device determines the first information based on the DNS response, including at least one of the following:

The fourth communication device determines the DNAI according to the EAS IP address and/or the FQDN in the DNS response;

The fourth communication device determines the second UPF based on the DNAI.
The method of claim 32, wherein the fourth communication device sending the first information includes:

The fourth communication device sends the first information to a second communication device, and the second communication device is a communication device under the operator corresponding to the second PLMN ID;

The fourth communication device sends the first information to a third communication device, and the third communication device is a communication device under the operator corresponding to the first PLMN ID.
The method of claim 32, wherein the method further includes:

The fourth communication device receives a third request, the third request is used to request to establish or update a PDU session within the operator corresponding to the second PLMN ID;

The fourth communication device sends a third response, the third response includes the IP address of the second communication device and the second PLMN ID, and the second communication device is the operator corresponding to the second PLMN ID. communication equipment.
The method of claim 37, wherein the fourth communication device receiving a third request includes:

The fourth communication device receives the third request from a third communication device, and the third communication device is a communication device under the operator corresponding to the first PLMN ID;

Wherein, the fourth communication device sends a third response, including:

The fourth communication device sends the third response to the third communication device.
The method according to claim 37, wherein the third response further includes third information, and the third information includes at least one of the following:

DNAI, the DNAI is used for user plane selection by the operator corresponding to the first PLMN ID, and the DNAI corresponds to the DNAI under the operator corresponding to the first PLMN ID;

The local PSA IP address of the operator corresponding to the second PLMN ID;

The core network tunnel information corresponding to the PSA under the operator corresponding to the second PLMN ID.
A DNS query device, including:

A receiving module, configured to receive a domain name system DNS query. The DNS query contains a fully qualified domain name FQDN. The first communication device is a communication device under the operator corresponding to the first public land mobile network PLMN ID. The FQDN is The domain name under the operator corresponding to the second PLMN ID;

A sending module, configured to send the DNS query to a second communication device, where the second communication device is a communication device under the operator corresponding to the second PLMN ID.
The device according to claim 40, wherein the sending module is also used for:

The DNS query is sent to the second communication device according to a first rule, the first rule is a processing rule for the FQDN, and the first rule is used to instruct the DNS query containing the FQDN to be sent to the second communication device. Second communication device.
A DNS query device, including:

A receiving module, configured to receive a DNS query. The DNS query is sent by a first communication device. The first communication device is a communication device under the operator corresponding to the first PLMN ID. The DNS query contains the FQDN. The FQDN is the domain name under the operator corresponding to the second PLMN ID, and the second communication device is the communication device under the operator corresponding to the second PLMN ID;

The sending module is used to forward the DNS query to the DNS server and obtain the EAS IP address corresponding to the FQDN.
The device according to claim 42, wherein the sending module is also used for:

Send DNS response;

Wherein, the DNS query response includes the FQDN and the EAS IP address.
A DNS query device, including:

A receiving module, configured to receive a first request. The first request is used to request processing rules for FQDN. The FQDN is the domain name under the operator corresponding to the second PLMN ID. The third communication device is the first PLMN. Communication equipment under the operator corresponding to the ID;

A sending module, configured to send a first response. The first response contains a first rule. The first rule is a processing rule for the FQDN. The first rule is used to indicate that a DNS query containing the FQDN will be performed. Sent to the second communication device, which is a communication device under the operator corresponding to the second PLMN ID.
The device of claim 45, wherein the device further comprises a configuration module, wherein:

The sending module is also used to send a second request, and the second request is used to request to obtain the second information;

The receiving module is also configured to receive a second response, where the second response contains the second information;

The configuration module is used to configure the first rule according to the second information;

Wherein, the second information includes at least one of the following:

The mapping relationship between the FQDN and the PLMN ID, where the PLMN ID is the PLMN ID to which the operator that can parse the FQDN belongs;

The address information of the network element that can resolve the FQDN and/or the PLMN ID to which the network element belongs.
A DNS query device, including:

A receiving module, configured to receive a DNS response, the fourth communication device is a communication device under the operator corresponding to the second PLMN ID, and the DNS response includes the FQDN and the EAS IP address corresponding to the FQDN;

Determining module, configured to determine first information according to the DNS response, where the first information includes DNAI and/or the IP address or identification of the second UPF;

A sending module, used to send the first information;

Wherein, the DNAI is used for user plane selection by the operator corresponding to the first PLMN ID, the second UPF is the UPF under the operator corresponding to the second PLMN ID, and the IP address of the second UPF or The identifier is used by the operator corresponding to the first PLMN ID to establish a PDU session to the operator corresponding to the second PLMN ID.
The device according to claim 47, wherein the determining module is used for at least one of the following:

Determine the DNAI based on the EAS IP address and/or the FQDN in the DNS response;

The second UPF is determined based on the DNAI.
A communication device, including a processor and a memory, the memory stores a program or instructions that can be run on the processor, and when the program or instructions are executed by the processor, any one of claims 1 to 11 is implemented. The steps of the DNS query method, or the steps of implementing the DNS query method as described in any one of claims 12 to 18, or the steps of implementing the DNS query method of any one of claims 19 to 31, or The steps of implementing the DNS query method according to any one of claims 32 to 39.
A readable storage medium on which programs or instructions are stored. When the programs or instructions are executed by a processor, the steps of the DNS query method according to any one of claims 1 to 11 are implemented, or the steps of the DNS query method are implemented. The steps of the DNS query method as described in any one of claims 12 to 18, or the steps of implementing the DNS query method as described in any one of claims 19 to 31, or the steps of implementing the DNS query method as described in any one of claims 32 to 39. Follow the steps of the DNS query method described above.