WO2023185836A1

WO2023185836A1 - Indication method for selection of edge application server, and terminal and network-side device

Info

Publication number: WO2023185836A1
Application number: PCT/CN2023/084380
Authority: WO
Inventors: 吕华章
Original assignee: 维沃移动通信有限公司
Priority date: 2022-03-28
Filing date: 2023-03-28
Publication date: 2023-10-05
Also published as: CN116866884A

Abstract

The present application belongs to the field of wireless communications. Disclosed are an indication method for the selection of an edge application server (EAS), and a terminal and a network-side device. The indication method for the selection of an EAS in the embodiments of the present application comprises: a first network-side device receiving a first request which is sent by a second network-side device, wherein the first request is used for requesting for the first network-side device to indicate a mode for processing a DNS query which is sent by a first terminal; and the first network-side device sending indication information to the second network-side device according to target information of the first terminal, wherein the indication information is used for instructing the second network-side device to process, in a target processing mode, the DNS query which is sent by the first terminal, and the target processing mode is used for selecting, for the first terminal, an EAS that is the same as that of at least one second terminal.

Description

Instruction method, terminal and network side equipment for edge application server selection

cross reference

This invention requires the priority of the Chinese patent application submitted to the China Patent Office on March 28, 2022, with the application number 202210313740.5 and the invention name "Instruction method, terminal and network side device for edge application server selection". All the applications The contents are incorporated herein by reference.

Technical field

The present application belongs to the field of wireless communication technology, and specifically relates to an instruction method for selecting an edge application server, a terminal and a network side device.

Background technique

The Edge Application Server Discovery Function (EASDF) is a network element used to process domain name system (Domain Name System, DNS) queries of terminals. In related technologies, the terminal sends a DNS query to EASDF, and then EASDF makes a judgment based on the DNS query to determine whether to send the DNS query to the central DNS (Central DNS, C-DNS) or the local (Local DNS, L-DNS). Wherein, the EASDF obtains the processing method for DNS query from the session management function (Session Management Function, SMF). EASDF sends the Fully Qualified Domain Name (FQDN) and other information in the DNS query to SMF. SMF provides EASDF with corresponding DNS processing rules to help EASDF determine which DNS service to send the DNS query to. Wherein, the Internet Protocol (IP) address of the DNS server is C-DNS or L-DNS. After C-DNS or L-DNS finds the IP address corresponding to the FQDN, it sends it to EASDF. EASDF saves the query result to SMF and then sends it to the terminal, so that the terminal obtains the server IP address of the requested FQDN.

For actual scenarios, in some cases, if the same Edge Application Server (EAS) IP address can be selected for DNS queries of multiple terminals, it may be possible to provide terminals with lower latency services. For example, in a venue or dormitory, if multiple users use multiple terminals to log in to the same application server for interactive services, then business processing can be optimized in the same application server. If the same EAS IP address can be selected for these terminals, these terminals can select the same application server. From an application layer perspective, this can avoid the business between servers caused by multiple terminals selecting multiple game servers. Interaction and latency. As another example, in a formation use case, such as a vehicle formation, all member units have similar attributes and requirements, such as driving direction and route. For example, in a specific platoon, all units have similar movement characteristics, namely towards Moving in the same direction and speed, close to each other, etc. In this scenario, if the same application server can be used, the delay in command issuance and coordination can be shortened.

However, the relevant technology does not provide the technology of how to select the same EAS for multiple terminals. plan.

Contents of the invention

Embodiments of the present application provide an edge application server selection instruction method, a terminal, and a network side device, which can solve the problem of how to select the same EAS for multiple terminals.

In a first aspect, a method for instructing edge application server selection is provided, including: a first network side device receiving a first request sent by a second network side device, wherein the first request is used to request the first network side device. The side device indicates how to process the DNS query sent by the first terminal; the first network side device sends instruction information to the second network side device according to the target information of the first terminal, wherein the instruction The information is used to instruct the second network side device to use a target processing method to process the DNS query sent by the first terminal, and the target processing method is used to select the same EAS for the first terminal as that of at least one second terminal, The target processing method includes one of the following: using target DNS message processing rules that are the same as the DNS message processing rules corresponding to the at least one second terminal; sending a target edge application carrying the target to the first terminal A target DNS response of a server EAS address that is the same as the EAS address selected for the at least one second terminal.

In a second aspect, an edge application server selection instructing device includes: a first receiving module configured to receive a first request sent by a second network side device, wherein the first request is used to request the first network The side device indicates how to process the DNS query sent by the first terminal; the first sending module is configured to send indication information to the second network side device according to the target information of the first terminal, wherein the indication The information is used to instruct the second network side device to use a target processing method to process the DNS query sent by the first terminal, and the target processing method is used to select the same EAS for the first terminal as that of at least one second terminal, The target processing method includes one of the following: using target DNS message processing rules that are the same as the DNS message processing rules corresponding to the at least one second terminal; sending a target edge application carrying the target to the first terminal A target DNS response of a server EAS address that is the same as the EAS address selected for the at least one second terminal.

In a third aspect, a method for responding to a DNS query is provided, including: a second network side device receiving a first DNS query sent by a first terminal; and the second network side device sending the first DNS query to the first network side device. Request, wherein the first request is used to request the first network side device to indicate a manner of processing the DNS query sent by the first terminal;

The second network side device receives the instruction information sent by the first network side device, wherein the instruction information is used to instruct the second network side device to use a target processing method to process the DNS query sent by the first terminal. Processing, the target processing method is used to select the same EAS for the first terminal as that of at least one second terminal; the second network side device adopts the target processing method to respond to the first DNS query; wherein, The target processing method includes at least one of the following: using target DNS message processing rules, the target DNS message processing rules are the same as the DNS message processing rules corresponding to the at least one second terminal; sending a target edge to the first terminal A target DNS response with an EAS address of the application server, the target EAS address being the same as the at least one second The EAS address selected by the terminal is the same.

In a fourth aspect, a DNS query response device is provided, including: a second receiving module for receiving the first DNS query sent by the first terminal; and a second sending module for sending to the first network side device. A first request, wherein the first request is used to request the first network side device to indicate how to process the DNS query sent by the first terminal; the second receiving module is also used to receive the first The network side device sends instruction information, wherein the instruction information is used to instruct the second network side device to use a target processing method to process the DNS query sent by the first terminal, and the target processing method is used to process the DNS query sent by the first terminal. The terminal selects the same EAS as at least one second terminal; a response module is configured to respond to the first DNS query using the target processing method; wherein the target processing method includes at least one of the following: using the target DNS Message processing rules, the target DNS message processing is the same as the DNS message processing rule corresponding to the at least one second terminal; sending a target DNS response carrying the target edge application server EAS address to the first terminal, the target EAS address The same as the EAS address selected for the at least one second terminal.

In a fifth aspect, a terminal group configuration method is provided, including: a fourth network side device determines EAS deployment information of a target terminal group according to a preset rule, wherein the preset rule indicates that the target terminal group needs to be The terminals in select the same EAS; the fourth network side device sends the EAS deployment information of the target terminal group to the third network side device.

In a sixth aspect, a device for configuring a terminal group is provided, including: a determination module configured to determine EAS deployment information of a target terminal group according to preset rules, wherein the preset rule indicates that the EAS deployment information of the target terminal group needs to be The terminals in the terminal select the same EAS; the third sending module is configured to send the EAS deployment information of the target terminal group to the third network side device.

In a seventh aspect, a DNS query method is provided, including: a first terminal receiving a first message sent by a first network side device, wherein the first message carries DNS policy information; According to the DNS policy information, a DNS query is sent to a DNS server; wherein the DNS server includes EASDF.

In an eighth aspect, a DNS query device is provided, including: a third receiving module, configured to receive a first message sent by a first network side device, wherein the first message carries DNS policy information; a fourth sending module A module configured to send a DNS query to a DNS server according to the DNS policy information; wherein the DNS server includes EASDF.

In a ninth aspect, a terminal 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 implementations are implemented: The steps of the method described in seven aspects.

In a tenth aspect, a terminal is provided, including a processor and a communication interface, wherein the processor is used to implement the steps of the method described in the seventh aspect, and the communication interface is used to communicate with an external device.

In an eleventh aspect, a network side device is provided. The network side device includes a processor and a memory. The memory stores programs or instructions that can be run on the processor. The program or instructions are used by the processor. When executed, the steps of the method described in the first aspect, or the steps of the method described in the third aspect, or the steps of the method described in the fifth aspect are implemented.

In a twelfth aspect, a network side device is provided, including a processor and a communication interface, wherein the processor is used to implement the steps of the method described in the first aspect, or to implement the method described in the third aspect. Steps, or steps for implementing the method as described in the fifth aspect, the communication interface is used to communicate with an external device.

In a thirteenth aspect, a DNS query system is provided, including: a terminal and a network side device. The terminal can be used to perform the steps of the method described in the seventh aspect, and the network side device can be used to perform the steps of the method described in the first aspect. The steps of the method, or the steps of the method described in the third aspect, or the steps of the method described in the fifth aspect.

In a fourteenth 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 fifteenth 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. The steps of the method can either implement the steps of the method described in the third aspect, or implement the steps of the method described in the fifth aspect, or implement the steps of the method described in the seventh aspect.

In a sixteenth 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 method, or the steps of 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 this embodiment of the present application, the first network side device instructs the second network side device to use a target processing method to process the DNS query sent by the first terminal according to the target information of the first terminal. The target processing method Used to select the same EAS for the first terminal and at least one second terminal, so that the second network side device can select the same EAS for the first terminal and the second terminal, shortening the time between the EAS and the first terminal and the second terminal. Communication delay.

Description of drawings

Figure 1 shows a block diagram of a wireless communication system to which embodiments of the present application are applicable;

Figure 2 shows a schematic flow chart of an instruction method for edge application server selection in an embodiment of the present application;

Figure 3 shows a schematic flow chart of the DNS query response method in the embodiment of the present application;

Figure 4 shows a schematic flow chart of a terminal group configuration method in an embodiment of the present application;

Figure 5 shows a schematic flow chart of the DNS query method in the embodiment of the present application;

Figure 6 shows another schematic flow chart of the DNS query response method provided by the embodiment of the present application;

Figure 7 shows another schematic flow chart of the DNS query response method provided by the embodiment of the present application;

Figure 8 shows another schematic flow chart of the terminal group configuration method in the embodiment of the present application;

Figure 9 shows a flow chart of the DNS query method in the application embodiment;

Figure 10 shows a schematic flow chart of an EAS switching method in an embodiment of the present application;

Figure 11 shows a schematic structural diagram of an instruction device for edge application server selection provided by an embodiment of the present application;

Figure 12 shows a schematic structural diagram of a DNS query response device provided by an embodiment of the present application;

Figure 13 shows a schematic structural diagram of a terminal group configuration method provided by an embodiment of the present application;

Figure 14 shows a schematic structural diagram of a DNS query device provided by an embodiment of the present application;

Figure 15 shows a schematic structural diagram of a communication device provided by an embodiment of the present application;

Figure 16 shows a schematic diagram of the hardware structure of a terminal provided by an embodiment of the present application;

Figure 17 shows a schematic hardware structure diagram of a network-side device provided by 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 are often used interchangeably, and the described technology can be used not only for the above-mentioned systems and radio technologies, but also for other systems and radio technologies. The following description describes a New Radio (NR) system for example purposes, and NR terminology is used in much of the following description, but these techniques can also be applied to applications other than NR system applications, such as 6th ^generation Generation, 6G) communication system.

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 Real (virtual reality, VR) equipment, robots, wearable devices (Wearable Devices), vehicle user equipment (VUE), pedestrian terminals (Pedestrian User Equipment, PUE), smart homes (home equipment with wireless communication functions , such as refrigerators, TVs, washing machines or furniture, etc.), game consoles, personal computers (PCs), teller machines or self-service machines and other terminal-side devices. Wearable devices include: smart watches, smart bracelets, smart headphones, smart phones, etc. Glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, 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 and/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), or a radio access network. function or radio access network unit. The access network device 12 may include a base station, a Wireless Local Area Network (WLAN) access point or a WiFi node, etc. The base station may be called a Node B, an evolved Node B (eNB), an access point, 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 suitable 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 the present application This introduction only takes the base station in the NR system as an example, and does not limit the specific type of base station. The core network equipment may include but is not limited to at least one of the following: core network node, core network function, mobility management entity (Mobility Management Entity, MME), access mobility management function (Access and Mobility Management Function, AMF), session management function (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 (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), centralized network configuration ( Centralized network configuration (CNC), Network Repository Function (NRF), 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 technical solutions provided by the embodiments of the present application will be described in detail below with reference to the accompanying drawings through some embodiments and their application scenarios.

Figure 2 shows a schematic flowchart of a method for instructing edge application server selection in an embodiment of the present application. The method 200 can be executed by the first network side device. In other words, the method may be executed by software or hardware installed on the first network side device. In this embodiment of the present application, the first network side device may be an SMF in the core network. As shown in Figure 2, the method may include the following steps.

S210. The first network side device receives the first request sent by the second network side device, where the The first request is used to request the first network side device to indicate a manner of processing the DNS query sent by the first terminal.

For example, after receiving a DNS query (which may also be called a DNS request, or a DNS query request) sent by the first terminal, the second network side device may request the first network side device for a method of processing the DNS query.

In this embodiment of the present application, the second network side device may be EASDF.

S212: The first network side device sends instruction information to the second network side device according to the target information of the first terminal, where the instruction information is used to instruct the second network side device to use a target processing method to process The DNS query sent by the first terminal is processed, and the target processing method is used to select the same EAS for the first terminal as that of at least one second terminal.

In this embodiment of the present application, the target processing method may include the following two processing methods (1) or (2).

(1) Use target DNS message handling rules (DNS message handling rules), which are the same as the DNS message handling rules corresponding to the at least one second terminal. The target DNS message processing rules are used for both the DNS query of the first terminal and the DNS query of the second terminal, so that the same EAS can be selected for the two terminals. For example, after receiving the above instruction from the SMF, EASDF can set the same DNS message processing rules for the DNS queries of the first terminal and the second terminal, that is, send the DNS queries of the first terminal and the second terminal to the same DNS server (server), thereby ensuring that the DNS server feeds back the same DNS response, so that the first terminal and the second terminal obtain the same EAS IP address. Because the same DNS server is used and the same FQDN is queried, the same EAS IP address can be found.

(2) Send a target DNS response carrying a target EAS address to the first terminal, where the target EAS address is the same as the EAS address selected for the at least one second terminal. That is, the first network side device instructs the second network side device to directly send a target DNS response of the target EAS address (for example, target EAS IP address) to the first terminal, where the target EAS address carried in the target DNS response is the same as the target EAS address carried in the target DNS response to the second terminal. The EAS addresses carried in the sent DNS responses are the same, so it can be determined that the first terminal obtains the same EAS address as the second terminal, and thereby accesses the same EAS as the second terminal. In this way, the EAS IP address can be directly provided to the UE by the 5G Core Network (5G Core Network, 5GC), avoiding dynamic changes in the DNS server query results and being directly designated by the 5GC.

Optionally, the target DNS response (which can be a DNS response triggered by 5GC or a response sent by a DNS server) can carry one target EAS address or multiple target EAS addresses. In the case of carrying multiple target EAS addresses, the target DNS response can also carry the priority corresponding to each target EAS address. After receiving the target DNS response, the first terminal can receive the responses in order from high to low priority. In other words, the first terminal can first access the target EAS address with the highest priority, and then access the target EAS address with the second highest priority if the access fails. Similarly, the second terminal can also access the target EAS address with the second highest priority. Access according to the rules, thereby ensuring that the first terminal and the second terminal access the same EAS.

In this embodiment of the present application, the first network side device can, based on the target information of the first terminal, To determine that the same EAS as the at least one second terminal needs to be selected for the first terminal, the first network side device sends the indication information to the second network side device.

In a possible implementation, the target information of the first terminal includes but is not limited to at least one of the following (1) to (6).

(1) The contract information of the first terminal. For example, the subscription information of the first terminal includes: a first indication, the first indication is used to indicate that the first terminal is allowed to use the same EAS with at least one second terminal. That is to say, when the first terminal is authorized to use the same EAS as other terminals, the second network side device can be instructed to use the above target processing method. For example, the operator can configure the same EAS IP address for multiple terminals as a value-added service, and the first terminal and the second terminal have signed and purchased the operator's edge computing optimization service, then the 5GC will be verified first, indicating that These two terminals are eligible to use the operator's value-added services.

(2) Location information of the first terminal. For example, when the first terminal and the second terminal are close in location, the second network side device may be instructed to use the above target processing method. In this embodiment of the present application, the location information of the first terminal may include at least one of the following: (a) The identity of the cell accessed by the first terminal, for example, when the first terminal and the second terminal are in the same cell In the case of, instruct the second network side device to use the target processing method; (b) the tracking area where the first terminal is located, for example, when the first terminal and the second terminal are in the same tracking area or a similar area In the case of a tracking area, instruct the second network side device to use the target processing method; (c) the IP address of the first terminal, for example, when the first terminal and the second terminal are in the same IP address segment In this case, instruct the second network side device to use the target processing method; (d) serve the protocol data unit (Protocol Data Unit, PDU) session anchor (PDU Session Anchor, PSA) of the first terminal, for example , when the PSA serving the first terminal and the second terminal is the same, instruct the second network side device to use the target processing method; (e) the data network access identifier (Data) of the first terminal Network Access Identifier (DNAI), for example, when the DNAI of the first terminal and the second terminal are the same, instruct the second network side device to use the target processing method. (f) The identification of the base station accessed by the first terminal. For example, when the base station identifiers accessed by the first terminal and the second terminal are the same (that is, the two terminals access the 5GC through one base station), then the same EAS IP address can be selected for them. If the location information of the first terminal is the same as the location information of the second terminal, the scenario described above may be satisfied: the first terminal and the second terminal perform interactive services (for example, interactive games) in the same room or venue. ). Therefore, these two terminals are qualified to use the same EAS IP address.

(3) The fully qualified domain name (Fully Qualified Domain Name, FQDN) in the DNS query of the first terminal. For example, when the FQDN in the first terminal's DNS query is a specified FQDN, it may be determined that the first terminal selects the same EAS as the second terminal whose query request contains these specified FQDNs, indicating that the second network The side device uses the target processing method. Optionally, the first FQDN is the same as the second FQDN, wherein the first FQDN is the FQDN in the DNS query of the first terminal, and the second FQDN is the DNS of the at least one second terminal. The FQDN in the DNS query to which the message processing rule applies. Through this optional solution, only when the FQDNs in the respective DNS queries of the first terminal and the second terminal are the same, Use this service. For example, if both the first terminal and the second terminal request access to FQDN=aaaa.com, it means that the two terminals are requesting services from the same third-party service provider. Therefore, it is reasonable to select the same EAS IP address for them.

(4) The Data Network Name (DNN) accessed by the first terminal. For example, when the first terminal accesses specific DNNs, it may be determined that the first terminal selects the same EAS as the second terminal that accesses these specific DNNs, and the second network side device is instructed to use the target processing method.

(5) The Data Network (DN) accessed by the first terminal. For example, when the first terminal accesses specific DNs, it may be determined that the same EAS is selected for the first terminal as the second terminal accessing these specific DNs, and the second network side device is instructed to use the target processing method.

(6) Single Network Slice Selection Assistance Information (S-NSSAI) of the first terminal. For example, when the S-NSSAI of the first terminal is a specific DN, the second network side device may be instructed to use the target processing method.

In a possible implementation of the embodiment of this application, the target DNS message processing rules include one of the following:

(1) Target DNS client subnet (EDNS-client-subnet, ECS) option. For example, using the target DNS message processing rule for the first terminal and the second terminal means using the same ESC option for the first terminal and the second terminal. Among them, the ECS option is usually an auxiliary information used by the DNS server to provide the terminal with an EAS IP address closest to the terminal when performing DNS resolution. The closest distance can be the closest geographical location or the closest route.

(2) Target local DNS server address.

In a possible implementation, sending the indication information by the first network side device to the second network side device may include the following steps:

Step 1: The first network side device determines to select the same EAS for the first terminal as the at least one second terminal according to the target information of the first terminal;

Step 2: The first network side device sends the indication information to the second network side device.

That is to say, in this possible implementation, the first network side device may determine that it is necessary to select the same EAS for the first terminal as the at least one second terminal according to the target information of the first terminal, and then , the first network side device sends the indication information to the second network side device.

In a specific application, the first network side device may not save the target information of the first terminal. Therefore, in a possible implementation, the first network side device determines based on the target information of the first terminal. Before selecting the same EAS for the first terminal as the at least one second terminal, the method may further include: the first network side device obtains target information of the first terminal.

For example, the first network side device may obtain the subscription data of the first terminal from the UDM. For example, the SMF can send Nudm_SDM_Get) or Nudm_SDM_Subscribe via UDM to restore the terminal's subscription information and input parameters: the first UE's subscription permanent identifier (Subscription Permanent Identifier, SUPI). UDM can send the first UE's subscription information to the SMF. The subscription information of the first UE saved by UDM may be: the current UE is authorized to use the same EAS, for example For example, the session management subscription data of the first UE (data required for PDU session establishment) may include an element whose value is: UE is authorized to select the same EAS authorization to indicate whether the UE is authorized to use the same EAS.

For another example, the first network side device may obtain the location information of the first UE from the AMF. The location information mainly includes the location of the first terminal in the radio access network (Radio Access Network, RAN). For example, if the first terminal and the second terminal both access the 5GC from a RAN or a set of specified RANs, the first terminal and the second terminal can be regarded as being within the same location range. For example, SMF recovers the location information of the first UE from AMF: Namf_EventExposure_Subscribe. In the output parameter, Event ID=Location Report, AMF can send the location information of the first UE to SMF. Among them, the location information of the first UE includes but is not limited to: cell ID (Cell ID) and tracking area identifier (Tracking Area Identifier, TAI), and may also be the accessed base station ID.

For another example, the first network side device can also obtain the User Plane Function (UPF) identifier (for example, PSA ID) and DNAI of the first terminal.

In a possible implementation, a target terminal group may be predefined, and the first network side device determines to select the same EAS for terminals in the target terminal group. Therefore, in this possible implementation, the first network side device determines to select the same EAS for the first terminal as the at least one second terminal according to the target information of the first terminal, which may include the following step:

Step 1: The first network side device determines that the first terminal belongs to a target terminal group according to the target information of the first terminal, wherein the at least one second terminal belongs to the target terminal group;

Step 2: The first network side device determines to select the same EAS as the at least one second terminal for the first terminal.

Optionally, the configuration description information of the target terminal group may be predefined. For example, the configuration description information may include at least one cell identifier, indicating that terminals located in at least one cell corresponding to the at least one cell identifier form a target terminal group. For another example, the configuration description information may include at least one target FQDN, indicating that terminals querying the at least one target FQDN form a target terminal group. For another example, the configuration description information may include a target IP address segment, indicating that terminals located in the target IP address segment form a target terminal group. Therefore, in a possible implementation, the first network side device determines that the first terminal belongs to the target terminal group based on the target information of the first terminal, including the following steps:

Step 1: The first network side device compares the target information of the first terminal with the configuration description information of the target terminal group;

Step 2: When it is determined that the target information of the first terminal satisfies at least one item of the configuration description information of the target terminal group, determine that the first terminal belongs to the target terminal group.

Wherein, the target information of the first terminal satisfies at least one item of the configuration description information of the target terminal group including at least one of the following:

(1) The target information of the first terminal is the same as at least one item in the configuration description information of the target terminal group; for example, the configuration description information of the target terminal group includes multiple FQDNs, and the DNS query of the first terminal The FQDN is the same as one of multiple FQDNs. For another example, the target terminal The configuration description information of the group includes a target cell identity, and the cell identity of the first terminal is the same as the target cell identity.

(2) The target information of the first terminal is within the scope of at least one item of the configuration description information of the target terminal group. For example, the configuration description information of the target terminal group may include a target IP address segment, and the IP address of the first terminal is within the target IP address segment.

In a possible implementation, the configuration description information of the target terminal group includes but is not limited to at least one of the following:

(1) Target subscription information; for example, allowing to use the same EAS with other terminals.

(2) Target location information; for example, the target location information includes but is not limited to at least one of the following: at least one target cell identifier; at least one target tracking area identifier; at least one IP address segment; at least one target PSA; at least one target DNAI; at least one target base station identifier.

(3) At least one target FQDN; the FQDN carried in the DNS query of the terminals in the target terminal group.

(4) At least one target DNN.

(5) At least one target S-NSSAI.

Optionally, the configuration description information of the target terminal group may also include analysis information of the first terminal's Network Data Analysis Function (NWDAF).

Using the above possible implementation methods, a target terminal group is determined. The terminals in this group all use the same EAS IP address. Then as long as a new terminal is determined to meet the configuration description information of the target terminal group, the new terminal can be confirmed. , you also need to configure the same EAS IP address for it.

In a possible implementation, before the first network side device determines that the first terminal belongs to the target terminal group according to the target information of the first terminal, the method may further include: The side device obtains EAS deployment information of the target terminal group, where the EAS deployment information includes the configuration description information.

Optionally, the EAS deployment information may also include a processing method corresponding to the target terminal group, and the processing method corresponding to the target terminal group includes one of the following:

(1) The target DNS message processing rules adopted by terminals in the target terminal group. That is to say, the target DNS message processing rules are used for DNS queries of terminals in the target terminal group. The first network side device determines that the first terminal belongs to the target terminal group based on the EAS deployment information. The first terminal's DNS query adopts the target DNS message processing rule. For example, use the same ECS option (that is, the target ECS option), or use the same local DNS server (that is, the target local DNS server).

(2) The target EAS address carried in the DNS response sent to the terminal in the target terminal group. That is to say, all DNS queries for terminals in the target terminal group are processed by sending a DNS response carrying the target EAS address to the terminal. The first network side device determines that the first terminal belongs to the target based on the EAS deployment information. In the case of a terminal group, it is determined to adopt a processing method of sending a DNS response carrying the target EAS address to the first terminal.

In a possible implementation, the first network side device may obtain the EAS deployment information of the target terminal group from the third network side device. For example, the first network side device can, when idle, from The third network side device obtains the EAS deployment information of the target terminal group, or the first network side device may also obtain the EAS deployment information of the target terminal group from the third network side device after receiving the first request. In a possible implementation, the first network side device obtains the EAS deployment information of the target terminal group from the third network side device, including: the first network side device uses the target information of the first terminal , obtain the EAS deployment information of the target terminal group from the third network side device. For example, after receiving the first request, the first network side device may obtain the EAS deployment information of the target terminal group from the third network side device based on the target information of the first terminal. For example, the first network side device may obtain the EAS deployment information of the target terminal group in the area (such as a cell or tracking area) where the first terminal is located from the third network side device.

For example, the EAS deployment information of the target terminal group can be saved in the UDR, and the first network side device (for example, SMF) can restore this information from the UDR. For example, the SMF can send signaling to NEF: Nnef_EASDeployment_Subscribe, and NEF can obtain the target from the UDR. The EAS deployment information of the terminal group is notified to SMF.

In a possible implementation, in order to enable terminals in the target terminal group to access the same EAS, after the first network side device obtains the EAS deployment information of the target terminal group, the method may further include: The first network side device sends a first message to the first terminal according to the EAS deployment information, where the first message carries DNS policy information, and the DNS policy information includes at least one of the following:

(1) Address information of the DNS server, instructing the first terminal to send a DNS query to the DNS server. The DNS server includes at least one of the following: EASDF; that is, it is hoped that all terminals in the target terminal group will use EASDF. as the DNS server IP address without using other DNS server IP addresses.

(2) Condition information, which includes at least one of the following: location condition information and at least one target FQDN.

For example, if the DNS policy information includes the above (1) and (2), it instructs the first terminal to send the DNS query to the DNS server corresponding to the address information in (1) if the information in the condition information is satisfied. .

In a possible implementation, the location condition information may include at least one of the following:

(1) At least one target cell identifier;

(2) At least one target tracking area identifier;

(3) At least one IP address segment;;

(4) At least one target PSA;

(5) At least one target DNAI;

(6) At least one target base station identifier.

The condition information is sent to the terminal, so that the terminal determines which DNS server the DNS query should be sent to based on the terminal location, the FQDN in the DNS query sent by the terminal, and the IP address segment where the UE's IP address is located. If the conditions are met, it should be sent to the EASDF corresponding to the address information in the DNS policy information, because sending to the same EASDF can ensure that the same EAS IP address is used.

In this embodiment of the present application, when the first network side device receives a request from the second network side device to indicate how to process the DNS query sent by the first terminal, the first network side device sends a request to the third network side device according to the target information of the first terminal. The second network side device instructs to use a target processing method to process the DNS query sent by the first terminal. The target processing method is used to select the same EAS for the first terminal as that of at least one second terminal, so that the second network side device can The first terminal and the second terminal select the same EAS to shorten the communication delay between the EAS and the first terminal and the second terminal.

Figure 3 shows a schematic flowchart of a DNS query response method in an embodiment of the present application. The method 300 can be executed by the second network side device. In other words, the method may be executed by software or hardware installed on the second network side device. In this embodiment of the present application, the second network side device may be EASDF. As shown in Figure 3, the method may include the following steps.

S310. The second network side device receives the first DNS query sent by the first terminal.

S312. The second network side device sends a first request to the first network side device, where the first request is used to request the first network side device to instruct the first network side device to process the DNS query sent by the first terminal. The way.

S314: The second network side device receives the instruction information sent by the first network side device, where the instruction information is used to instruct the second network side device to use a target processing method to process the DNS sent by the first terminal. The query is processed, and the target processing method is used to select the same EAS for the first terminal as that of at least one second terminal.

The first network side device may use the description in method 200 to send the indication information to the second network side device. For details, please refer to the description in method 300, which will not be described again here.

S316: The second network side device responds to the first DNS query using the target processing method.

Wherein, the target processing method includes at least one of the following:

Using target DNS message processing rules, the target DNS message processing rules are the same as the DNS message processing rules corresponding to the at least one second terminal;

A target DNS response carrying a target edge application server EAS address is sent to the first terminal, where the target EAS address is the same as the EAS address selected for the at least one second terminal.

In a possible implementation, the second network side device adopts the target processing method to respond to the first DNS query, which may include:

The second network side device uses the target DNS message processing rule to send a second DNS query to a target DNS server, where the target DNS server is the same as the DNS server corresponding to the at least one second terminal;

The second network side device receives the first DNS response returned by the target DNS server, wherein the first DNS response carries at least one EAS address;

The second network side device returns the first DNS response to the first terminal.

For example, the second network side device may carry a target ECS option in the second DNS query, and the target ECS option is the same as the ECS option corresponding to the at least one second terminal, or the second network side device may carry the target ECS option in the second DNS query. The second DNS query carries a target local DNS server address, and the target local DNS server is a local DNS service corresponding to the at least one second terminal. server address, allowing a secondary DNS query to be sent to the target DNS server.

In this embodiment of the present application, the DNS query of the first terminal is sent to the same DNS server as the second terminal, so that the same DNS server can respond to the DNS query of the first terminal and the DNS query of the second terminal, As a result, the EAS address carried in the first DNS response sent to the first terminal is likely to be the same as the EAS address carried in the DNS response sent to the second terminal.

In a possible implementation, the first DNS response may carry one EAS address or multiple EAS addresses. When the first DNS response carries multiple EAS addresses, the first DNS response may also carry The priority corresponding to each EAS address.

In a possible implementation, the second network side device adopts the target processing mode, and responding to the first DNS query may include: the second network side device sends a second DNS response, wherein the second DNS response carries the target EAS address. That is, in this possible implementation, the second network side device directly sends a second DNS response to the first terminal, and the second DNS response carries the above-mentioned target EAS address.

Optionally, the second DNS response may carry one target EAS address or multiple target EAS addresses. In the case of carrying multiple target EAS addresses, the second DNS response may also carry the priority corresponding to each target EAS address. After receiving the second DNS response, the first terminal may respond in order from high to low priority. Access in sequence, that is to say, the first terminal can access the target EAS address with the highest priority first, and then access the target EAS address with the second highest priority if the access fails. Similarly, the second terminal can also access Access is performed according to the same rules, thereby ensuring that the first terminal and the second terminal access the same EAS.

Through the technical solutions provided by the embodiments of this application, the second network side device can respond to the DNS query of the first terminal using the same target processing method as the second terminal, thereby making it possible for the first terminal to connect with the second terminal. into the same EAS.

Figure 4 shows a schematic flowchart of a terminal group configuration method in an embodiment of the present application. The method 400 can be executed by a fourth network side device. In other words, the method may be executed by software or hardware installed on the fourth network side device. In this embodiment of the present application, the fourth network side device may be an application function (Application Function, AF) network element. As shown in Figure 4, the method may include the following steps.

S410: The fourth network side device determines the EAS deployment information of the target terminal group according to the preset rules, where the preset rules indicate that the same EAS needs to be selected for the terminals in the target terminal group.

For example, for a certain application, its service provider can set preset rules to select the same EAS for terminals in the target terminal group.

S412: The fourth network side device sends the EAS deployment information of the target terminal group to the third network side device.

For example, AF can save the EAS deployment information of the target terminal group into the UDR.

In a possible implementation, the preset rules include but are not limited to at least one of the following:

(1) Select the same EAS for terminals with target subscription information; for example, select the same EAS for a terminal that is authorized to use an EAS with other terminals for subscription.

(2) Select the same EAS for terminals in close locations; for example, select the same EAS for terminals in the same location area, where the proximity (or the same location area) can be achieved through at least one cell, at least one tracking area, at least one It is defined by the base station, IP address segment, PSA, DNAI, etc. of the service terminal, which are not specifically limited in the embodiments of this application.

(3) Select the same EAS for terminals accessing the same DNN;

(4) Select the same EAS for terminals accessing the same DN;

(5) Select the same EAS for the terminal querying the target FQDN;

(6) Select the same EAS for the terminal with target S-NSSAI.

In this embodiment of the present application, the EAS deployment information of the target terminal group is the same as the EAS deployment information of the target terminal group in the above method 200. For details, please refer to the description in the method 200.

In a possible implementation, the EAS deployment information may include configuration description information of the target terminal group, and the configuration description information includes at least one of the following:

(1) Target subscription information; optionally, the target subscription information may include: allowing to use the same EAS with other terminals.

(2) Target location information.

(3) At least one target FQDN. The FQDN carried in the DNS query of the terminals in the target terminal group.

(4) At least one target DNN.

(5) At least one target S-NSSAI.

In a possible implementation, the target location information includes at least one of the following:

(1) At least one target cell identifier;

(2) At least one target tracking area identifier;

(3) At least one IP address segment;

(4) At least one target PSA;

(5) At least one target DNAI;

(6) At least one target base station identifier.

In a possible implementation, the EAS deployment information also includes a processing method corresponding to the target terminal group, and the processing method corresponding to the target terminal group includes one of the following:

(1) The target DNS message processing rules adopted by the terminals in the target terminal group;

(2) The target EAS address carried in the DNS response sent to the terminal in the target terminal group.

In a possible implementation, the target DNS message processing rules include one of the following: target ECS options, target local DNS server address.

In a possible implementation, after the fourth network side device sends the EAS deployment information of the target terminal group to the third network side device, the method further includes:

The fourth network side device determines to update the target EAS address of the target terminal group, and/or the fourth network side device determines to update the target local DNS server address of the target terminal group;

The fourth network side device notifies the terminals in the target terminal group to re-initiate DNS query.

In the above possible implementation manner, the fourth network side device may determine to update the target EAS address of the target terminal group. For example, in order to achieve EAS load balancing, the fourth network side device determines to update the target EAS address of the target terminal group, and/ Or after determining to update the target local DNS server address of the target terminal group, notify the terminals in the target terminal group to re-initiate a DNS query to relocate the EAS accessed by the terminals in the target terminal group.

Through the technical solutions provided by the embodiments of this application, the fourth network side device can determine the EAS deployment information of the target terminal group, and send the EAS deployment information of the target terminal group to the third network side device, so that multiple terminals can be configured to access The conditions and processing methods of the same EAS facilitate processing of the terminal's DNS query when it receives the terminal's DNS query later.

The EAS deployment information provided by the AF can guide the SMF and EASDF to select the same EAS for the target terminal. However, the information provided by AF is not decisive. That is, if AF does not decide to select the same EAS IP address A for a certain FQDN of a terminal in a certain location, SMF must follow this configuration.

Figure 5 shows a schematic flowchart of the DNS query method in this embodiment of the present application. The method 500 can be executed by the first terminal. In other words, the method may be performed by software or hardware installed on the first terminal. As shown in Figure 5, the method may include the following steps.

S510: The first terminal receives the first message sent by the first network side device, where the first message carries DNS policy information.

In this embodiment of the present application, the DNS policy information is the same as the DNS policy information in method 200. For the manner in which the first network side device sends the first message, please refer to the description in method 200, which will not be described again here.

In a possible implementation, the DNS policy information includes at least one of the following:

(1) The address information of the DNS server;

When the DNS policy information includes the address information of the DNS server, it is equivalent to the first terminal saving multiple DNS server addresses. When the first terminal meets the condition information, the first terminal uses the DNS server, that is, A DNS query is sent to the DNS server. If the condition is not met, a local DNS server is used, that is, a DNS query is sent to the local DNS server.

In a possible implementation, the location condition information includes at least one of the following:

At least one target cell identifier;

At least one target tracking area identifier;

At least one IP address range;

At least one target PSA;

at least one target DNAI;

At least one target base station identifier.

S512: The first terminal sends a DNS query to a DNS server according to the DNS policy information; wherein the DNS server includes EASDF.

In a possible implementation, the first terminal sends a request to the DNS server based on the DNS policy information. A DNS server sending a DNS query can include the following steps:

Step 1: The first terminal compares the target information of the first terminal with the condition information;

Step 2: When it is determined that the target information of the first terminal satisfies at least one of the condition information, the first terminal sends a DNS query to the second network side device;

Wherein, the target information of the first terminal satisfying at least one of the condition information includes at least one of the following:

The target information of the first terminal is the same as at least one item of the condition information; for example,

The target information of the first terminal is within the scope of at least one item of the condition information.

In a possible implementation, the target information of the first terminal includes at least one of the following:

The location information of the first terminal;

The FQDN in the DNS query of the first terminal;

In a possible implementation, the location information of the first terminal includes at least one of the following: a cell identity accessed by the first terminal, a tracking area where the first terminal is located, and an IP address of the first terminal. Address, PDU session anchor PSA serving the first terminal, data network access identifier DNAI of the first terminal, and base station identifier accessed by the first terminal.

In S512, when the target information of the first terminal is compared with the condition information, it can be determined whether the target information of the first terminal satisfies the condition information. For example, if the condition information includes multiple FQDNs, and if the FQDN in the DNS query of the first terminal is the same as one of the multiple FQDNs, it is determined that the target information of the first terminal satisfies the condition information. For another example, if the configuration description information of the target terminal group includes a target cell identifier, and the cell identifier of the first terminal is the same as the target cell identifier, it is determined that the target information of the first terminal satisfies the condition information. For another example, the condition information may include an IP address segment. If the IP address of the first terminal is within the IP address segment, it is determined that the target information of the first terminal satisfies the condition information.

In a possible implementation, after the first terminal sends a DNS query to the second network side device, the method may further include the following steps:

Step 1: The first terminal receives a DNS response returned by the second network side device, where the DNS response carries at least one EAS address;

The second network side device may send a DNS response to the first terminal in the manner described in the above method 300. The DNS response may include the first DNS response or the second DNS response in the method 300. For details, please refer to the method 300. The description will not be repeated here.

Step 2: The first terminal accesses the EAS corresponding to one of the at least one EAS address.

In this embodiment of the present application, the DNS response may carry an EAS address. Then, after receiving the DNS response, the first terminal directly accesses the EAS corresponding to the EAS address. Alternatively, the DNS response may also carry multiple EAS addresses and priorities corresponding to each of the EAS addresses. In this case, the first terminal may access any one of the EASs, or the first terminal may The terminal accessing the EAS corresponding to one of the at least one EAS address may also include: the first terminal first accesses the one with a higher priority according to the priorities corresponding to the multiple EAS addresses. The EAS corresponding to the EAS address.

In a possible implementation, after the first terminal accesses the EAS corresponding to one of the at least one EAS address, the method further includes: when the target information of the first terminal is changed. In the case of , the first terminal re-sends the DNS query to the DNS server according to the DNS policy information. For example, if the location of the first terminal changes, the first terminal can re-send a DNS query to the DNS server according to the DNS policy information.

Taking the first network side device as SMF and the second network side device as EASDF as an example, the technical solution provided by the embodiment of the present application will be described below.

In the implementation column of this application, SMF considers that the same EAS should be selected for the DNS query of a group of UEs or the same DNS message handling rule (DNS message handling rule) should be selected. The conditions and indicators of UEs considered by SMF are as follows:

(1) UE location: When the UE location is close, it is deemed to have selected the same EAS service. Among them, the UEs can be considered to be in close proximity under the following conditions:

(1) Same DNAI.

(2) The same UE IP address segment.

(3) UE accesses from a group of RAN (for example, TAI list, cell ID, NR Node B Identifier, gNB ID), especially venue services, which are accessed through several nearby base stations. Coming in, it can be regarded as a set of terminals.

(4) The PDU Session Anchor (PSA) serving the UE is the same. Because if the UPF serving multiple UEs is the same UPF, multiple UEs are considered to access the same DN.

(5) The same data network name (Data Network Name, DNN).

(6) The same single network slice selection assistance information (Single Network Slice Selection Assistance Information, S-NSSAI).

(2) FQDN, only the default FQDN can enjoy this service.

(3) UE contract information.

(4) Analysis of Network Data Analytics Function (NWDAF).

If at least one of the above conditions is met, the SMF should configure the DNS queries of these UEs as follows:

-Configure the same DNS message handling rules (mainly the DNS query forwarding mechanism, including: using the same ECS option; or forwarding DNS queries to the same local DNS server IP);

- Instruct EASDF to send the same DNS response to these endpoints. The DNS response includes the same EAS that these endpoints should use.

Figure 6 shows another schematic flowchart of the DNS query response method provided by the embodiment of the present application. As shown in Figure 6, the method 600 mainly includes the following steps.

S601a: Select EASDF for the UE. In this step, you can select the same EASDF for multiple terminals to ensure that the same EAS IP address can be used.

S601b: The terminal sends a DNS query, which includes: UE IP address and FQDN.

S602: After EASDF receives the DNS query from the terminal, it sends Neasdf_DNSContext_Notify Request to SMF to notify SMF of the FQDN to be queried, and also requests SMF to issue DNS message handling rules. The processing rule described is mainly that SMF instructs EASDF to which DNS server the DNS query should be sent.

S603: SMF sends a response indicating receipt of the EASDF request.

Next, S604 starts to S611 and collects the target information of the UE for the SMF. Through this information, the SMF can determine that the DNS query for this terminal needs to use the same set of DNS message handling rules as for other UEs.

S604 to S606: SMF obtains the UE's subscription data from UDM.

S604: SMF sends Nudm_SDM_Get or Nudm_SDM_Subscribe to restore the terminal's subscription information, where the input parameters include: UE SUPI. The contract information means that the current terminal can use the value-added services provided by the operator, that is, the same EAS IP address can be selected for the terminal.

S605: UDM returns a response indicating that the request was received.

S606: The UDM can send the UE's subscription information to the SMF. The subscription information of the UE saved by UDM is: Only when the current UE is authorized to use the same EAS can SMF optimize it.

S607 to S609: SMF obtains the location of the UE from the AMF. The location of this UE is mainly the location of the UE on the RAN side. If several terminals access 5GC or EASDF from a RAN or a set of specified RANs, SMF can regard these terminals as being within a location range and configure the same DNS message handling rule for them.

S607: SMF restores the UE's location information from AMF: Namf_EventExposure_Subscribe, in the output parameter, Event ID=Location Report.

S608: AMF sends response.

S609: AMF sends the UE's location to SMF. The most important location information is: Cell ID and TAI. For example, the UE's location can be sent to SMF through signaling Namf_EventExposure_Notify.

SMF can set a rule. For example, when the UE location of the UE, such as cell ID or TAI, etc., is within a range, these UEs are deemed to be able to use the same EAS.

For example, terminals with Cell ID=1 to 10 and TAI=1 to 10 are considered to be in similar locations and can use the same EAS or the same DNS message handling rule.

The identifier of the base station accessed by the terminal, for example, gNB ID, can also be provided as location information.

S610: The SMF determines the UPF ID (for example, PSA ID) and DNAI of the serving UE.

SMF can directly obtain this information without searching for other network elements.

S611: After the SMF collects the target information of the UE, the SMF executes the decision rules to determine whether the same DNS message processing rules need to be configured for the terminal or the same DNS response needs to be sent.

S612: When the SMF determines that it is necessary to select the same DNS message handling rule for the UE's DNS query as that of other terminals, the SMF sends an update to the EASDF to update the The rules for this DNS query of the UE: use the same ECS option or the same local DNS server IP address.

For example, SMF can use signaling: Neasdf_DNSContext_Update Request (DNS message handling rules), which can carry:

Baseline DNS handling actions information:

The baseline DNS handling actions ID (Baseline DNS handling actions ID) can include:

-ECS option;

-Local DNS server IP address.

What is sent here is to instruct EASDF how to handle the DNS query of the UE. Since these UEs all use one EAS, the same EAS can be queried according to exactly the same processing rules.

Using the same DNS message processing rules is an implementation method for selecting the same EAS.

S613: EASDF returns a response.

S614: EASDF sends the UE's DNS query to the DNS server in a rule. Among them, these DNS queries of all UEs that meet the conditions are sent to the same DNS server with the same DNS message handling rule.

S615: The DNS server returns a DNS response to the EASDF, where the EAS IP addresses carried in the DNS responses returned by the DNS server to all UEs that meet the conditions are the same.

Optionally, the DNS response can carry multiple EAS IP addresses, each IP address corresponds to a priority, and the UE can access one by one according to the priority.

S616, EASDF sends a Neasdf_DNSContext_Notify request to SMF. This request is used to notify SMF of the DNS query for the terminal and the returned DNS response. The main purpose is to report the EAS IP address to SMF.

S617, SMF returns Neasdf_DNSContext_Notify response to EASDF.

S618, when the EAS IP address is determined, SMF selects PSA.

S619, EASDF sends a DNS response to the UE.

In this embodiment of the present application, the SMF can indicate DNS message processing rules to multiple EASDFs. Then, multiple EASDFs share this processing rule to ensure that the same EAS is selected or used for multiple terminals.

Figure 7 shows another schematic flow chart of the DNS query response method provided by the embodiment of the present application. As shown in Figure 7, the method 700 mainly includes the following steps.

S701a-S710, the same as S601a-S610.

S711: The SMF determines based on the conditions that the UE's DNS query directly feeds back the EAS IP address and directly feeds back the DNS response, that is, there is no need to query the DNS server.

S712: SMF sends an update to EASDF, instructing EASDF to directly send a DNS response to the UE, and at the same time, sends the EAS IP address to EASDF. At this time, SMF needs to specify which EAS IP address to send to the terminal in the DNS response. The specific EAS IP address to choose can be decided by SMF.

That is, SMF instructs EASDF how to handle the UE's DNS query. Since the UE is different from other The UE needs to use an EAS, so just send the IP address directly to the UE, which is regarded as querying the same EAS.

S713: EASDF returns a response.

S717: EASDF sends a DNS response to the UE, and the DNS response carries the EAS IP address indicated by SMF.

In the embodiment of this application, the SMF can instruct multiple EASDFs on the processing method of sending DNS responses.

Figure 8 shows another schematic flowchart of the terminal group configuration method in the embodiment of the present application. As shown in Figure 8, the method 800 mainly includes the following steps.

S801: AF provides information such as the location or FQDN of a specific UE, indicating the DNS message handling rule (DNS message handling rule) or EAS IP address.

Specifically, AF considers that DNS queries for a group of UEs should select the same EAS or use the same DNS message handling rule. For example, the DNS queries include the same FQDN, or the terminals are in the same location. AF provides target DNS message handling rules (DNS message handling rules) or target EAS IP addresses. Specifically, AF can set the following conditions:

(1) Same DNAI.

(2) The same UE IP address segment.

(3) UE accesses from a group of RAN (for example, TAI list, cell ID), especially venue services. It accesses through several nearby base stations and can be regarded as a group of terminals.

(2) The same Data Network Name (DNN)

(3) The same single network slice selection assistance information (Single Network Slice Selection Assistance Information, S-NSSAI).

(4) FQDN, only the default FQDN can enjoy this service.

(5) UE contract information.

(6) Analysis of Network Data Analytics Function (NWDAF).

If at least one of the above conditions is met, AF provides the corresponding configuration as follows:

-Target DNS message processing rules (mainly the mechanism for forwarding DNS queries, including: using the same ECS option; or forwarding DNS queries to the same local DNS server IP)

- Target EAS IP address, i.e., send the same EAS IP address to these terminals. The DNS response includes the same EAS that these endpoints should use.

S802: NEF verifies whether this AF request is legal.

S803: Under the condition of verification that it is legal, NEF saves the information sent by AF (called the EAS deployment information of the terminal group in this application, and may also be called other information names) to the UDR. For example, NEF can save this information to UDR through signaling: Nudr_DM_Create or Nudr_DM_Update. The storage format is as shown in Table 1. Of course, it is not limited to this, as long as the storage location can be clearly defined.

Table 1

S804: UDR sends response to NEF.

S805: NEF sends a response to AF.

SMF can recover this information from the UDR, and then decide based on this information whether the same EAS or the same DNS message processing rules need to be selected for DNS queries of some UEs.

S806: SMF restores the information in the UDR, that is, obtains the above saved information from the UDR. For example, SMF can use the signaling: Nnef_EASDeployment_Subscribe to NEF to obtain the above information from the UDR.

SMF can restore the information in the UDR when receiving a request for a processing method for a DNS query sent by EASDF. For example, SMF can obtain the EAS IP address or processing rules in the area where the terminal that sends the DNS query is located.

Alternatively, SMF can also restore the information in the UDR when it is idle.

S807: NEF sends response to SMF.

S808: NEF notifies SMF of the above information. For example, NEF notifies SMF of the above information through Nnef_EASDeployment_Notify. That is, after SMF subscribes to NEF, let NEF obtain the above information from UDR.

S809: SMF sends a notification response to AF.

S810: SMF obtains the target DNS message processing rule or target EAS IP address corresponding to specific conditions (for example, specific region, specific FQDN).

Figure 9 shows a flow chart of the DNS query method in the embodiment of the application. In the embodiment of the application, the execution process of the UE is optimized, so that the UE can distinguish the DNS query that needs to be sent to the EASDF based on FQDN, etc., And DNS queries that need to be sent directly to the local DNS server. As shown in Figure 9, the method 900 mainly includes the following steps.

S901a: Optionally, establish a PDU session of the UE.

S901b, the uplink classifier (UL CL)/branching point (Branching point, BP) is inserted into the local DNS server that the UE can access locally.

S902, SMF sends the following content to the UE (or UE operating system (OS), UE EDC, edge discovery function (edge discovery function)) through the NAS message: condition information, for example, at least one target FQDN, UE location condition Information and EASDF IP address, etc.

In other words, SMF tells the UE that when the UE is in this location and the DNS sent by the UE When the query contains the specified FQDN, the UE (or EDC) needs to send the DNS query to EASDF instead of the local DNS server.

This is equivalent to storing multiple sets of DNS server IP addresses inside the UE.

-When the UE is in a specific area and the FQDN in the DNS query sent is a domain name in the list, EASDF is used;

-If not, the local DNS server is used.

Or, in another scenario, when the UE is in a specific area and the FQDN in the DNS query sent is a domain name in the list, the local DNS server is used. This ensures that all qualified terminals send DNS queries to the same server. A local DNS server.

The SMF needs to be configured with an N4 rule for the UL CL before S902 is given to the UE: when the UE sends a DNS query with the destination IP address to EASDF, the UL CL routes the DNS query to EASDF (via C-PSA routing, that is, central user plane routing).

S903. The UE returns a response to the SMF.

S904a and S905a, when the FQDN and UE location do not meet the conditions, the UE's DNS query is sent to the L-PSA through UL CL/BP, and then sent to the local DNS server, and the local DNS server provides feedback.

S904b and S905b, under the FQDN and UE location that meet the conditions, the UE's DNS query is sent to C-PSA through UL CL/BP, and then sent to EASDF, and EASDF provides feedback according to the method described in the above method 600 or method 700 embodiment. .

In the embodiment of this application, after the network side selects the same EAS for multiple terminals, if an EAS switch occurs, the network side must also take corresponding measures to ensure it. Figure 10 shows a schematic flow chart of an EAS switching method in an embodiment of the present application. As shown in Figure 10, the method mainly includes the following steps.

S1001. Establish a PDU session for the UE.

S1002, discover an EAS IP address (source EAS IP address).

Specifically, an EAS IP address can be discovered for the UE through the method described in the above method 600 or method 700 embodiment.

S1003, the UE and the EAS previously performed uplink transmission (the source IP address is the IP address of the UE, and the target IP address is the source EAS IP address) and downlink transmission (the source IP address is the source EAS IP address, and the target IP address is the UE) through the remote PSA. IP address).

S1004, AF or 5G core network (5GC) triggers the EAS IP address replacement process.

S1005, UPF replaces the source EAS IP address in the uplink transmission sent by the UE with the new EAS IP address, and replaces the new EAS IP address in the downlink transmission with the source EAS IP address.

Alternatively, EAS relocation can also be performed. For example, if AF triggers relocation (relocation), for example, EAS load balancing, you can AF update the IP address of EAS to 5GC; then, let the UE perform a DNS query again, and then The description of the method 600 or the method 700 embodiment may be used to select an EAS for the UE. For another example, if the UE moves and triggers relocation, the UE can query DNS after arriving at the new location, and then use method 600 or 700 to use new DNS message processing rules or EAS IP addresses.

This method illustrates that AF provides an EAS IP address to replace the destination EAS IP addresses of multiple terminals. This also enables the selection of the same EAS for multiple terminals to a certain extent.

For the instructing method for edge application server selection provided by the embodiment of the present application, the execution subject may be an instructing device for edge application server selection. In this embodiment of the present application, the instruction device for edge application server selection is used as an example to illustrate the instruction method for edge application server selection.

Figure 11 shows a schematic structural diagram of an edge application server selection instructing device provided by an embodiment of the present application. As shown in Figure 11, the device mainly includes: a first receiving module 1101 and a first sending module 1102.

In this embodiment of the present application, the first receiving module 1101 is used to receive a first request sent by a second network side device, wherein the first request is used to request the first network side device to instruct the first terminal to send The way to process DNS queries of the domain name system; the first sending module 1102 is configured to send indication information to the second network side device according to the target information of the first terminal, wherein the indication information is used to indicate the The second network side device uses a target processing method to process the DNS query sent by the first terminal. The target processing method is used to select the same EAS for the first terminal as that of at least one second terminal. The target processing method Including one of the following: using target DNS message processing rules, the target DNS message processing rules are the same as the DNS message processing rules corresponding to the at least one second terminal; sending a target carrying the EAS address of the target edge application server to the first terminal DNS response, the target EAS address is the same as the EAS address selected for the at least one second terminal.

The contract information of the first terminal;

The location information of the first terminal;

The fully qualified domain name FQDN in the DNS query of the first terminal;

The data network name DNN accessed by the first terminal;

The data network DN accessed by the first terminal;

Single network slice selection assistance information S-NSSAI of the first terminal.

In a possible implementation, the subscription information of the first terminal includes: a first indication, the first indication is used to indicate that the first terminal is allowed to use the same EAS with at least one second terminal.

In a possible implementation, the first FQDN and the second FQDN are the same, wherein the first FQDN is the FQDN in the DNS query of the first terminal, and the second FQDN is the at least one first FQDN. 2. The FQDN in the DNS query to which the terminal's DNS message processing rules apply.

In a possible implementation, the target DNS message processing rules include one of the following:

Target DNS client subnet ECS options;

Target local DNS server address.

In a possible implementation, the target DNS response carries at least one of the following: at least one target EAS address and a priority corresponding to each target EAS address.

In a possible implementation, the first sending module 1102 sends indication information to the second network side device, including:

Determine to select the same EAS for the first terminal as the at least one second terminal according to the target information of the first terminal;

Send the indication information to the second network side device.

In a possible implementation, the first receiving module 1101 is further configured to: the first network side device obtains the target information of the first terminal.

In a possible implementation, the first sending module 1102 determines to select the same EAS for the first terminal as the at least one second terminal according to the target information of the first terminal, including:

Determine that the first terminal belongs to a target terminal group according to the target information of the first terminal, wherein the at least one second terminal belongs to the target terminal group;

It is determined that the same EAS as that of the at least one second terminal is selected for the first terminal.

In a possible implementation, the first sending module 1102 determines that the first terminal belongs to the target terminal group according to the target information of the first terminal, including:

Compare the target information of the first terminal with the configuration description information of the target terminal group;

When it is determined that the target information of the first terminal satisfies at least one item of the configuration description information of the target terminal group, determine that the first terminal belongs to the target terminal group;

The target information of the first terminal is the same as at least one item of the configuration description information of the target terminal group;

The target information of the first terminal is located within the scope of at least one item of configuration description information of the target terminal group.

In a possible implementation, the configuration description information of the target terminal group includes at least one of the following:

Target contract information;

Target location information;

At least one target FQDN;

At least one target DNN;

At least one target S-NSSAI.

In a possible implementation, the target subscription information includes: allowing the user to use the same EAS with other terminals.

At least one target cell identifier;

At least one target tracking area identifier;

At least one IP address range;

At least one target PSA;

at least one target DNAI;

At least one target base station identifier.

In a possible implementation, the first receiving module 1101 is also configured to obtain EAS deployment information of the target terminal group, where the EAS deployment information includes the configuration description information.

The target DNS message processing rules adopted by terminals in the target terminal group;

The target EAS address carried in the DNS response sent to the terminal in the target terminal group.

In a possible implementation, the first receiving module 1101 obtains the EAS deployment information of the target terminal group, including:

Obtain EAS deployment information of the target terminal group from the third network side device.

In a possible implementation, the first receiving module 1101 obtains the EAS deployment information of the target terminal group from the third network side device, including:

Using the target information of the first terminal, obtain the EAS deployment information of the target terminal group from the third network side device.

In a possible implementation, the first sending module 1102 is also used to:

According to the EAS deployment information, a first message is sent to the first terminal, wherein the first message carries DNS policy information, and the DNS policy information includes at least one of the following:

Address information of the DNS server, instructing the first terminal to send a DNS query to the DNS server, where the DNS server includes at least one of the following: EASDF;

Condition information, the condition information includes at least one of the following: location condition information, at least one target FQDN.

At least one target cell identifier;

At least one target tracking area identifier;

At least one IP address range;

At least one target PSA;

at least one target DNAI;

At least one target base station identifier.

Figure 12 shows a schematic structural diagram of a DNS query response device provided by an embodiment of the present application. As shown in Figure 12, the device 1200 mainly includes: a second receiving module 1201, a second sending module 1202 and a response module 1203.

In this embodiment of the present application, the second receiving module 1201 is used to receive the first DNS query sent by the first terminal; the second sending module is used to send the first request to the first network side device, wherein the The first request is used to request the first network side device to instruct the DNS query sent by the first terminal. The second receiving module 1201 is also used to receive the instruction information sent by the first network side device, wherein the instruction information is used to instruct the second network side device to use the target processing method to process the query. The DNS query sent by the first terminal is processed, and the target processing method is used to select the same EAS for the first terminal as that of at least one second terminal; the response module 1203 is used to use the target processing method to process the Respond to the first DNS query; wherein the target processing method includes at least one of the following: using target DNS message processing rules, the target DNS message processing rules are the same as the DNS message processing rules corresponding to the at least one second terminal; The first terminal sends a target DNS response carrying a target edge application server EAS address, where the target EAS address is the same as the EAS address selected for the at least one second terminal.

In a possible implementation, the response module 1203 adopts the target processing method to respond to the first DNS query, including:

Using the target DNS message processing rules, send a second DNS query to a target DNS server, where the target DNS server is the same as the DNS server corresponding to the at least one second terminal;

Receive the first DNS response returned by the target DNS server, wherein the first DNS response carries at least one EAS address;

In a possible implementation, the second DNS query carries a target ECS option, and the target ECS option is the same as the ECS option corresponding to the at least one second terminal, or the second DNS query carries There is a target local DNS server address, and the target local DNS server is the same as the local DNS server address corresponding to the at least one second terminal.

In a possible implementation, the first DNS response carries multiple EAS addresses and priorities corresponding to each of the EAS addresses.

In a possible implementation, the response module 1203 uses the target processing method to respond to the first DNS query, including: sending a second DNS response to the first terminal, where the second DNS response contains the target EAS address.

Figure 13 shows a schematic structural diagram of a terminal group configuration method provided by an embodiment of the present application. As shown in Figure 13, the device 1300 mainly includes: a determination module 1301 and a third sending module 1302.

In this embodiment of the present application, the determination module 1301 is configured to determine the EAS deployment information of the target terminal group according to preset rules, wherein the preset rules indicate that the same EAS needs to be selected for the terminals in the target terminal group; The third sending module 1302 is configured to send the EAS deployment information of the target terminal group to the third network side device.

In a possible implementation, the preset rules include at least one of the following:

Select the same EAS for terminals with target subscription information;

Select the same EAS for terminals located in close proximity;

Select the same EAS for terminals accessing the same DNN;

Select the same EAS for terminals accessing the same DN;

Select the same EAS for the terminal querying the target FQDN;

Select the same EAS for the terminal with target S-NSSAI.

In a possible implementation, the EAS deployment information includes configuration description information of the target terminal group, and the configuration description information includes at least one of the following:

Target contract information;

Target location information;

At least one target FQDN;

At least one target DNN;

At least one target S-NSSAI.

At least one target cell identifier;

At least one target tracking area identifier;

At least one IP address range;

At least one target PSA;

at least one target DNAI;

At least one target base station identifier.

In a possible implementation, the determination module 1301 is also used to:

Determine to update the target EAS address of the target terminal group, and/or determine to update the target local DNS server address of the target terminal group;

Notify the terminals in the target terminal group to re-initiate DNS query.

Figure 14 shows a schematic structural diagram of a DNS query device provided by an embodiment of the present application. The device is applied to a first terminal. As shown in Figure 14, the device 1400 mainly includes: a third receiving module 1401, used to receive the first The first message sent by the network side device, wherein the first message carries DNS policy information; the fourth sending module 1402 is used to send a DNS query to the DNS server according to the DNS policy information; wherein the DNS The server includes EASDF.

The address information of the DNS server;

In a possible implementation, the fourth sending module 1402 sends a DNS query to the DNS server according to the DNS policy information, including:

Compare the target information of the first terminal with the condition information;

When it is determined that the target information of the first terminal satisfies at least one of the condition information, send a DNS query to the second network side device;

The target information of the first terminal is the same as at least one item of the condition information;

At least one target cell identifier;

At least one target tracking area identifier;

At least one IP address range;

At least one target PSA;

at least one target DNAI;

At least one target base station identifier.

The location information of the first terminal;

The FQDN in the DNS query of the first terminal;

In a possible implementation, the third receiving module 1401 is also configured to receive a DNS response returned by the second network side device, wherein the DNS response carries at least one EAS address; access and the at least one The EAS corresponding to one of the EAS addresses.

In a possible implementation, the DNS response carries multiple EAS addresses and priorities corresponding to each of the EAS addresses.

In a possible implementation, the third receiving module 1401 accesses the EAS corresponding to one of the at least one EAS address, including: priority access according to the priorities corresponding to the multiple EAS addresses. The EAS corresponding to the EAS address with high priority.

In a possible implementation, the fourth sending module 1402 is also configured to re-send the first terminal to the DNS server according to the DNS policy information when the target information of the first terminal changes. DNS query.

Optionally, as shown in Figure 15, this embodiment of the present application also provides a communication device 1500, which includes a processor 1501 and a memory 1502. The memory 1502 stores programs or instructions that can be run on the processor 1501, such as , when the communication device 1500 is a network-side device, when the program or instruction is executed by the processor 1501, it implements each step of the above-mentioned edge application server selection instruction method embodiment, or implements each step of the above-mentioned DNS query response method embodiment, Or implement each step of the above terminal group configuration method embodiment, and achieve the same technical effect. When the communication device 1500 is a terminal, when the program or instruction is executed by the processor 1501, each step of the above DNS query method embodiment is implemented, and the same technical effect can be achieved. To avoid duplication, it will not be repeated here. Repeat.

An embodiment of the present application also provides a terminal, including a processor and a communication interface. The processor is used to implement each step of the above DNS query method embodiment, and the communication interface is used to communicate with external devices. This terminal embodiment corresponds to the above-mentioned terminal-side method embodiment. Each implementation process and implementation manner of the above-mentioned method embodiment can be applied to this terminal embodiment, and can achieve the same technical effect. Specifically, FIG. 16 is a schematic diagram of the hardware structure of a terminal that implements an embodiment of the present application.

The terminal 1600 includes but is not limited to: a radio frequency unit 1601, a network module 1602, an audio output unit 1603, an input unit 1604, a sensor 1605, a display unit 1606, a user input unit 1607, an interface unit 1608, a memory 1609, a processor 1610, etc. At least some parts.

Those skilled in the art can understand that the terminal 1600 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 1610 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. 16 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 1604 may include a graphics processing unit (Graphics Processing Unit, GPU) 16041 and a microphone 16042. The graphics processor 16041 is responsible for the image capture device (GPU) in the video capture mode or the image capture mode. Process the image data of still pictures or videos obtained by cameras (such as cameras). The display unit 1606 may include a display panel 16061, which may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like. The user input unit 1607 includes a touch panel 16071 and at least one of other input devices 16072. Touch panel 16071, also known as touch screen. The touch panel 16071 may include two parts: a touch detection device and a touch controller. Other input devices 16072 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 1601 can transmit it to the processor 1610 for processing; in addition, the radio frequency unit 1601 can send uplink data to the network side device. Generally, the radio frequency unit 1601 includes, but is not limited to, an antenna, amplifier, transceiver, coupler, low noise amplifier, duplexer, etc.

Memory 1609 may be used to store software programs or instructions as well as various data. The memory 1609 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 1609 may include volatile memory or nonvolatile memory, or memory 1609 may include both volatile and nonvolatile memory. Among them, the 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 1609 in embodiments of the present application includes, but is not limited to, these and any other suitable types of memory.

The processor 1610 may include one or more processing units; optionally, the processor 1610 integrates an application processor and a modem processor, where the application processor mainly handles operations related to the operating system, user interface, application programs, etc., Modem processors mainly process wireless communication signals, such as baseband processors. It can be understood that the above modem processor may not be integrated into the processor 1610.

The radio frequency unit 1601 is configured to receive the first message sent by the first network side device, where the first message carries DNS policy information;

The processor 1610 is configured to send a DNS query to a DNS server according to the DNS policy information; wherein the DNS server includes EASDF.

Embodiments of the present application also provide a network-side device, including a processor and a communication interface. The processor is used to implement each step of the above-mentioned edge application server selection instruction method embodiment, or to implement each step of the above-mentioned DNS query response method embodiment. , or implement each step of the above terminal group configuration method embodiment, and the communication interface is used to communicate with external devices. This network-side device embodiment corresponds to the above-mentioned network-side device method embodiment. Each implementation process and implementation manner of the above-mentioned method embodiment can be applied to this network-side device embodiment, and can achieve the same technical effect.

Specifically, the embodiment of the present application also provides a network side device. As shown in Figure 17, the network side device 1700 includes: a processor 1701, a network interface 1702, and a memory 1703. Among them, the network interface 1702 is, for example, a common public radio interface (CPRI).

Specifically, the network side device 1700 in this embodiment of the present invention also includes: instructions or programs stored in the memory 1703 and executable on the processor 1701. The processor 1701 calls the instructions or programs in the memory 1703 to execute the instructions shown in Figures 11-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, the readable storage medium stores a program or instructions, and when the program or instructions are executed by the processor, each process of the above edge application server selection instruction method embodiment is implemented. Either implement each process of the above DNS query response method embodiment, or implement each process of the above terminal group configuration method embodiment, or implement each process of the above DNS query method embodiment, and achieve the same technical effect. In order to avoid Repeat, I won’t go into details here.

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 is coupled to the processor. The processor is used to run programs or instructions to implement the above instructions for edge application server selection. Each process of the method embodiment, or implementing the above DNS query Each process of the response method embodiment, or each process of the above terminal group configuration method embodiment, or each process of the above DNS query method embodiment, and can achieve the same technical effect, to avoid duplication, will not be repeated here. Repeat.

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-mentioned selection of the edge application server. Indicates each process of the method embodiment, or implements each process of the above DNS query response method embodiment, or implements each process of the above terminal group configuration method embodiment, or implements each process of the above DNS query method embodiment, and can To achieve the same technical effect, to avoid repetition, we will not repeat them here.

Embodiments of the present application also provide a DNS query system, including: a terminal and a network-side device. The terminal can be used to execute the steps of the DNS query method as described above. The network-side device can be used to execute the above-mentioned edge application server. Each step of the selected instruction method embodiment, or the steps of the response method of the DNS query as described above, or the various processes of the above terminal group configuration method embodiment, and can achieve the same technical effect, in order to avoid duplication, I won’t go into details here.

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 , optical disk), including several instructions to cause a terminal (which can be a mobile phone, computer, server, air conditioner, or network-side device, etc.) to execute the method 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

An instruction method for edge application server selection, including:

The first network side device sends indication information to the second network side device according to the target information of the first terminal, wherein the indication information is used to instruct the second network side device to use a target processing method to process the first The DNS query sent by the terminal is processed. The target processing method is used to select the same edge application server EAS for the first terminal as the at least one second terminal. The target processing method includes one of the following:

Using target DNS message processing rules, the target DNS message processing rules are the same as the DNS message processing rules corresponding to the at least one second terminal;

A target DNS response carrying a target edge application server EAS address is sent to the first terminal, where the target EAS address is the same as the EAS address selected for the at least one second terminal.
The method of claim 1, further comprising:

The first network side device receives a first request sent by the second network side device, where the first request is used to request the first network side device to indicate a manner of processing the domain name system DNS query sent by the first terminal.
The method according to claim 1 or 2, wherein the target information of the first terminal includes at least one of the following:

The contract information of the first terminal;

The location information of the first terminal;

The fully qualified domain name FQDN in the DNS query of the first terminal;

The data network name DNN accessed by the first terminal;

The data network DN accessed by the first terminal;

Single network slice selection assistance information S-NSSAI of the first terminal.
The method according to claim 3, wherein the subscription information of the first terminal includes: a first indication, the first indication is used to indicate that the first terminal is allowed to use the same EAS with at least one second terminal.
The method according to claim 3, wherein the location information of the first terminal includes at least one of the following: a cell identifier accessed by the first terminal, a tracking area where the first terminal is located, the first The IP address of the terminal, the PDU session anchor PSA serving the first terminal, the data network access identifier DNAI of the first terminal, and the base station identifier accessed by the first terminal.
The method according to claim 1 or 2, wherein the first FQDN is the same as the second FQDN, wherein the first FQDN is the FQDN in the DNS query of the first terminal, and the second FQDN is the At least one FQDN in the DNS query to which the DNS message processing rule of the second terminal is applied.
The method according to claim 1 or 2, wherein the target DNS message processing rules include one of the following:

Target DNS client subnet ECS options;

Target local DNS server address.
The method according to claim 1 or 2, wherein the target DNS response carries at least one of the following: at least one target EAS address and a priority corresponding to each target EAS address.
The method according to any one of claims 1 to 8, wherein the first network side device sends indication information to the second network side device, including:

The first network side device determines to select the same EAS for the first terminal as the at least one second terminal according to the target information of the first terminal;

The first network side device sends the indication information to the second network side device.
The method according to claim 9, wherein before the first network side device determines to select the same EAS for the first terminal as the at least one second terminal according to the target information of the first terminal, The method also includes:

The first network side device obtains target information of the first terminal.
The method according to claim 9, wherein the first network side device determines to select the same EAS for the first terminal as the at least one second terminal according to the target information of the first terminal, including:

The first network side device determines that the first terminal belongs to a target terminal group based on the target information of the first terminal, wherein the at least one second terminal belongs to the target terminal group;

The first network side device determines to select the same EAS as the at least one second terminal for the first terminal.
The method according to claim 11, wherein the first network side device determines that the first terminal belongs to the target terminal group according to the target information of the first terminal, including:

The first network side device compares the target information of the first terminal with the configuration description information of the target terminal group;

When it is determined that the target information of the first terminal satisfies at least one item of the configuration description information of the target terminal group, determine that the first terminal belongs to the target terminal group;

Wherein, the target information of the first terminal satisfies at least one item of the configuration description information of the target terminal group including at least one of the following:

The target information of the first terminal is the same as at least one item of the configuration description information of the target terminal group;

The target information of the first terminal is located within the scope of at least one item of configuration description information of the target terminal group.
The method according to claim 12, wherein the configuration description information of the target terminal group includes at least one of the following:

Target contract information;

Target location information;

At least one target FQDN;

At least one target DNN;

At least one target S-NSSAI.
The method of claim 13, wherein the target subscription information includes: allow Use the same EAS as other terminals.
The method of claim 13, wherein the target location information includes at least one of the following:

At least one target cell identifier;

At least one target tracking area identifier;

At least one IP address range;

At least one target PSA;

at least one target DNAI;

At least one target base station identifier.
The method according to claim 12, wherein before the first network side device determines that the first terminal belongs to the target terminal group according to the target information of the first terminal, the method further includes:

The first network side device obtains EAS deployment information of the target terminal group, where the EAS deployment information includes the configuration description information.
The method according to claim 16, wherein the EAS deployment information further includes a processing method corresponding to the target terminal group, and the processing method corresponding to the target terminal group includes one of the following:

The target DNS message processing rules adopted by terminals in the target terminal group;

The target EAS address carried in the DNS response sent to the terminal in the target terminal group.
The method according to claim 16 or 17, wherein the first network side device obtains the EAS deployment information of the target terminal group, including:

The first network side device obtains the EAS deployment information of the target terminal group from the third network side device.
The method according to claim 18, wherein the first network side device obtains the EAS deployment information of the target terminal group from the third network side device, including:

The first network side device uses the target information of the first terminal to obtain the EAS deployment information of the target terminal group from the third network side device.
The method according to claim 16 or 17, wherein after the first network side device obtains the EAS deployment information of the target terminal group, the method further includes:

The first network side device sends a first message to the first terminal according to the EAS deployment information, where the first message carries DNS policy information, and the DNS policy information includes at least one of the following:

Address information of the DNS server, instructing the first terminal to send a DNS query to the DNS server, where the DNS server includes at least one of the following: EASDF;

Condition information, the condition information includes at least one of the following: location condition information, at least one target FQDN.
The method according to claim 20, wherein the location condition information includes at least one of the following:

At least one target cell identifier;

At least one target tracking area identifier;

At least one IP address range;

At least one target PSA;

at least one target DNAI;

At least one target base station identifier.
A response method to a DNS query, including:

The second network side device receives the first DNS query sent by the first terminal;

The second network side device receives instruction information sent by the first network side device, wherein the instruction information is used to instruct the second network side device to process the DNS query sent by the first terminal in a target processing manner, The target processing method is used to select the same EAS for the first terminal as that of at least one second terminal;

The second network side device adopts the target processing method to respond to the first DNS query;

Wherein, the target processing method includes at least one of the following:

Using target DNS message processing rules, the target DNS message processing rules are the same as the DNS message processing rules corresponding to the at least one second terminal;

A target DNS response carrying a target edge application server EAS address is sent to the first terminal, where the target EAS address is the same as the EAS address selected for the at least one second terminal.
The method of claim 22, wherein the method further includes:

The second network side device sends a first request to the first network side device, where the first request is used to request the first network side device to indicate a manner of processing the DNS query sent by the first terminal. .
The method according to claim 22 or 23, wherein the second network side device adopts the target processing method to respond to the first DNS query, including:

The second network side device uses the target DNS message processing rule to send a second DNS query to a target DNS server, where the target DNS server is the same as the DNS server corresponding to the at least one second terminal;

The second network side device receives the first DNS response returned by the target DNS server, wherein the first DNS response carries at least one EAS address;

The second network side device returns the first DNS response to the first terminal.
The method of claim 24, wherein:

The second DNS query carries a target ECS option, and the target ECS option is the same as the ECS option corresponding to the at least one second terminal, or,

The second DNS query carries a target local DNS server address, and the target local DNS server is the same as the local DNS server address corresponding to the at least one second terminal.
The method according to claim 24, wherein the first DNS response carries multiple EAS addresses and priorities corresponding to each of the EAS addresses.
The method according to claim 22 or 23, wherein the second network side device adopts Using the target processing method to respond to the first DNS query includes:

The second network side device sends a second DNS response to the first terminal, where the second DNS response carries the target EAS address.
A terminal group configuration method, including:

The fourth network side device determines the EAS deployment information of the target terminal group according to the preset rules, wherein the preset rules indicate that the same EAS needs to be selected for the terminals in the target terminal group;

The fourth network side device sends the EAS deployment information of the target terminal group to the third network side device.
The method of claim 28, wherein the preset rules include at least one of the following:

Select the same EAS for terminals with target subscription information;

Select the same EAS for terminals located in close proximity;

Select the same EAS for terminals accessing the same DNN;

Select the same EAS for terminals accessing the same DN;

Select the same EAS for the terminal querying the target FQDN;

Select the same EAS for the terminal with target S-NSSAI.
The method according to claim 28, wherein the EAS deployment information includes configuration description information of the target terminal group, and the configuration description information includes at least one of the following:

Target contract information;

Target location information;

At least one target FQDN;

At least one target DNN;

At least one target S-NSSAI.
The method of claim 30, wherein the target location information includes at least one of the following:

At least one target cell identifier;

At least one target tracking area identifier;

At least one IP address range;

At least one target PSA;

at least one target DNAI;

At least one target base station identifier.
The method according to claim 30 or 31, wherein the target subscription information includes: allowing to use the same EAS with other terminals.
The method according to claim 28, wherein the EAS deployment information further includes a processing method corresponding to the target terminal group, and the processing method corresponding to the target terminal group includes one of the following:

The target DNS message processing rules adopted by terminals in the target terminal group;

The target EAS address carried in the DNS response sent to the terminal in the target terminal group.
The method of claim 33, wherein the target DNS message processing rules include one of the following: target ECS options, target local DNS server address.
The method according to claim 34, wherein after the fourth network side device sends the EAS deployment information of the target terminal group to the third network side device, the method further includes:

The fourth network side device determines to update the target EAS address of the target terminal group, and/or the fourth network side device determines to update the target local DNS server address of the target terminal group;

The fourth network side device notifies the terminals in the target terminal group to re-initiate DNS query.
A DNS query method, including:

The first terminal receives the first message sent by the first network side device, where the first message carries DNS policy information;

The first terminal sends a DNS query to a DNS server according to the DNS policy information; wherein the DNS server includes EASDF.
The method according to claim 36, wherein the DNS policy information includes at least one of the following:

The address information of the DNS server;

Condition information, the condition information includes at least one of the following: location condition information, at least one target FQDN.
The method according to claim 37, wherein the first terminal sends a DNS query to the DNS server according to the DNS policy information, including:

The first terminal compares the target information of the first terminal with the condition information;

When it is determined that the target information of the first terminal satisfies at least one of the condition information, the first terminal sends a DNS query to the second network side device;

Wherein, the target information of the first terminal satisfying at least one of the condition information includes at least one of the following:

The target information of the first terminal is the same as at least one item of the condition information;

The target information of the first terminal is within the scope of at least one item of the condition information.
The method according to claim 37, wherein the location condition information includes at least one of the following:

At least one target cell identifier;

At least one target tracking area identifier;

At least one IP address range;

At least one target PSA;

at least one target DNAI;

At least one target base station identifier.
The method according to claim 38, wherein the target information of the first terminal includes at least one of the following:

The location information of the first terminal;

The fully qualified domain name FQDN in the DNS query of the first terminal.
The method according to claim 40, wherein the location information of the first terminal includes at least one of the following: a cell identifier accessed by the first terminal, a tracking area where the first terminal is located, the first The IP address of the terminal, the PDU session anchor PSA serving the first terminal, the data network access identifier DNAI of the first terminal, and the base station identifier accessed by the first terminal.
The method according to any one of claims 36 to 41, wherein after the first terminal sends a DNS query to the second network side device, the method further includes:

The first terminal receives a DNS response returned by the second network side device, wherein the DNS response carries at least one EAS address;

The first terminal accesses the EAS corresponding to one of the at least one EAS address.
The method according to claim 42, wherein the DNS response carries multiple EAS addresses and priorities corresponding to each of the EAS addresses.
The method of claim 43, wherein the first terminal accesses the EAS corresponding to one of the at least one EAS address, including:

The first terminal preferentially accesses the EAS corresponding to the EAS address with a higher priority according to the priorities corresponding to the multiple EAS addresses.
The method of claim 42, wherein after the first terminal accesses the EAS corresponding to one of the at least one EAS address, the method further includes:

When the target information of the first terminal is changed, the first terminal resends the DNS query to the DNS server according to the DNS policy information.
An indication device for edge application server selection, including:

The first sending module is configured to send indication information to the second network side device according to the target information of the first terminal, wherein the indication information is used to instruct the second network side device to use a target processing method to process the The DNS query sent by the first terminal is processed. The target processing method is used to select the same EAS for the first terminal as that of at least one second terminal. The target processing method includes one of the following:

Using target DNS message processing rules, the target DNS message processing rules are the same as the DNS message processing rules corresponding to the at least one second terminal;

A target DNS response carrying a target edge application server EAS address is sent to the first terminal, where the target EAS address is the same as the EAS address selected for the at least one second terminal.
The device of claim 46, wherein the device further comprises:

A first receiving module configured to receive a first request sent by the second network side device, wherein the first request is used to request the first network side device to instruct the domain name system DNS query sent by the first terminal. The way to deal with it.
A DNS query response device, including:

a second receiving module, configured to receive the first DNS query sent by the first terminal;

The second receiving module is also configured to receive indication information sent by the first network side device, wherein the indication information is used to instruct the second network side device to adopt a target processing method for the DNS query sent by the first terminal. Perform processing, and the target processing method is used to select the first terminal with at least A second terminal with the same EAS;

A response module, configured to respond to the first DNS query using the target processing method;

Wherein, the target processing method includes at least one of the following:

Using target DNS message processing rules, the target DNS message processing rules are the same as the DNS message processing rules corresponding to the at least one second terminal;

A target DNS response carrying a target edge application server EAS address is sent to the first terminal, where the target EAS address is the same as the EAS address selected for the at least one second terminal.
The device of claim 48, wherein the device further comprises:

The second sending module is configured to send a first request to the first network side device, where the first request is used to request the first network side device to indicate a manner of processing the DNS query sent by the first terminal. .
A terminal group configuration device, including:

A determination module configured to determine the EAS deployment information of the target terminal group according to preset rules, wherein the preset rules indicate that the same EAS needs to be selected for the terminals in the target terminal group;

The third sending module is configured to send the EAS deployment information of the target terminal group to the third network side device.
A DNS query device, including:

The third receiving module is configured to receive the first message sent by the first network side device, wherein the first message carries DNS policy information;

The fourth sending module is configured to send a DNS query to a DNS server according to the DNS policy information; wherein the DNS server includes EASDF.
A network side device, including 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, any one of claims 1 to 21 is implemented. The step of indicating the edge application server selection method described in the item, or the step of implementing the response method of the DNS query as described in any one of claims 22 to 27, or implementing the terminal group as described in any one of claims 28 to 35. The steps of the configuration method.
A terminal, including a processor and a memory, the memory stores programs or instructions that can be run on the processor, and when the programs or instructions are executed by the processor, the implementation as claimed in any one of claims 36 to 45 is provided. Follow the steps of the DNS query method described above.
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 instruction method selected by the edge application server according to any one of claims 1 to 21 are implemented. , or implement the steps of the DNS query response method as described in any one of claims 22 to 27, or implement the steps of the terminal group configuration method as described in any one of claims 28 to 35, or implement the steps of claim 36 Go to the steps of the DNS query method described in any one of 45.