Edge application server discovery method, device, blockchain system and medium

Abstract

The embodiments of the present application provide a method, device, blockchain system and medium for discovering edge application servers. By discovering functional entities (EAS) according to each edge application server, a blockchain system, namely an EASDF chain, can be formed to directly provide a suitable target EASDF responsible for the corresponding session service according to the DNS query request of the mobile terminal (UE) about the IP address of the EAS server, thereby satisfying the DNS query request of the UE. Compared with the related art, it is necessary to determine the target EASDF and obtain the EAS IP address through SMF, which effectively improves efficiency, reduces the burden of SMF and reduces latency.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a discovery method, device, blockchain system and medium for an edge application server. Background Art

[0002] The application server (EAS) deployed in the edge computing environment has a different DNS information from the DNS of the large network or the central business. There is also the issue of application signing and whether to use MEC services. Therefore, in the 5G network where MEC is deployed, how to find the EAS IP address and enjoy the MEC services has become a top priority.

[0003] Currently, 3GPP SA2 is also actively considering related issues and formulating standards. Although TS23.458 has added the edge application server discovery function (EASDF) network element to independently solve the DNS discovery of 5G networks, thereby solving the problem of EAS IP discovery. However, in the current R17 specification, EASDF is selected by the SMF and notified to the mobile terminal (UE). The UE then initiates a DNS request to the corresponding target network element. This not only increases the workload of the SMF, but also the UE has to wait until the SMF returns the EASDF address before initiating a DNS request, which greatly prolongs the access delay. This conflicts with the goal of high bandwidth / low latency for edge services, so it needs to be improved.

[0004] Invention News

[0005] In view of the shortcomings of the above-mentioned related technologies, the object of this application is to provide a discovery method, device, blockchain system and medium for edge application servers to solve the above-mentioned technical problems.

[0006] The first aspect of the present application provides a method for discovering an edge application server, which is applied to discovering the network address of an edge application server for a mobile terminal of a user in a mobile communication network; the method comprises: forming a blockchain system with each edge application server discovery function entity as a node; the blockchain system receiving a DNS query request from a mobile terminal; wherein the mobile terminal is configured with an access address of the blockchain system as a DNS address; the blockchain system obtains a target node suitable for the mobile terminal through a consensus mechanism; the target node creates a DNS context for a session management function network element connected to the mobile terminal; the target node obtains a target network address of the edge application server; the target node sends a DNS query response corresponding to the DNS request to the terminal; wherein the DNS query response carries the network address of the edge application server.

[0007] In some embodiments, the blockchain system obtains a target node suitable for the DNS query request through a consensus method, including: a consensus of more than a preset number of nodes in the blockchain system obtains an available node closest to the mobile terminal as the target node.

[0008] In some embodiments, the DNS query request carries the network address of the mobile terminal, the IP address or FQDN of the target server, and the location information of the mobile terminal, so that the blockchain system can determine the target node.

[0009] In some embodiments, the edge application server discovery method further includes: in response to a preset event related to a change in location of the mobile terminal, updating the DNS context between the target node and the session management function network element.

[0010] In some embodiments, the edge application server discovers the functional entity through a DNS matching rule to obtain a target node according to the content of the DNS query request; wherein the DNS matching rule is pre-configured or determined by a session management function network element connected to the mobile terminal.

[0011] In some embodiments, the content of the DNS query request also includes: the digital data network that the mobile terminal needs to access and the callback URI.

[0012] In some embodiments, the target node obtains the target network address of the edge application server, including: in response to having obtained the target network address of the edge application server required by the DNS query request, the target node returns the target network address to the mobile terminal; or, when the blockchain system does not have the target network address required by the DNS query request, the target node initiates a DNS query request to the DNS server to obtain the target network address.

[0013] In some embodiments, when the blockchain system does not have the target network address required by the DNS query request, initiating a DNS query request to a DNS server to obtain the target network address includes: responding to initiating a DNS query request to a local or remote DNS server.

[0014] The second aspect of the present application provides a network device, including: a communicator, a memory and a processor; the communicator is used to communicate with the outside; the memory is used to store program instructions; the processor is used to run the program instructions to implement a node in the blockchain system involved in the discovery method of the edge application server as described in any one of the first aspects.

[0015] The third aspect of the present application provides a blockchain system, comprising: a node implemented by the network device described in the second aspect.

[0016] A fourth aspect of the present application provides a computer-readable storage medium storing program instructions, which, when executed, implement the nodes in the blockchain system involved in the method for discovering an edge application server as described in any one of the first aspects.

[0017] As described above, the embodiments of the present application provide a method, device, blockchain system and medium for discovering edge application servers, and form a blockchain system, namely an EASDF chain, by discovering functional entities (EAS) according to each edge application server, so as to directly provide a suitable target EASDF responsible for the corresponding session service according to the DNS query request of the mobile terminal (UE) about the IP address of the EAS server, thereby satisfying the DNS query request of the UE. Compared with the related art, it is necessary to determine the target EASDF and obtain the EAS IP address through SMF, which effectively improves efficiency, reduces the burden of SMF and reduces latency. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 A structural schematic diagram showing an application scenario in an embodiment of the present application.

[0019] Figure 2 A flowchart showing a method for discovering an edge application server in an embodiment of the present application is shown.

[0020] Figure 3 A schematic diagram showing the signaling interaction process of a method for discovering an edge application server in an application example of the present application.

[0021] Figure 4 A schematic diagram showing the structure of a network device in an embodiment of the present application is shown. DETAILED DESCRIPTION

[0022] The following is an explanation of the implementation of the present application by specific examples, and those skilled in the art can easily understand other advantages and effects of the present application from the information disclosed in the present application. The present application can also be implemented or applied through other different specific implementations, and the details in the present application can also be modified or changed in various ways according to different viewpoints and application systems without departing from the spirit of the present application. It should be noted that the embodiments in the present application and the features in the embodiments can be combined with each other without conflict.

[0023] The following is a detailed description of the embodiments of the present application with reference to the accompanying drawings so that those skilled in the art can easily implement the present application. The present application can be embodied in a variety of different forms and is not limited to the embodiments described herein.

[0024] In the representations of the present application, the representations with reference to the terms "one embodiment", "some embodiments", "examples", "specific examples", or "some examples" etc. mean that the specific features, structures, materials or characteristics represented in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. Moreover, the specific features, structures, materials or characteristics represented may be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine the different embodiments or examples represented in the present application and the features of the different embodiments or examples, unless they are contradictory.

[0025] In addition, the terms "first" and "second" are only used to indicate the target, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined as "first" and "second" may explicitly or implicitly include at least one of the features. In the representation of this application, the meaning of "plurality" is two or more, unless otherwise clearly and specifically defined.

[0026] In order to clearly describe the present application, components irrelevant to the description are omitted, and the same reference symbols are given to the same or similar components throughout the specification.

[0027] Throughout the specification, when a device is said to be "connected" to another device, this includes not only the case of "direct connection" but also the case of "indirect connection" by placing other elements therebetween. In addition, when a device is said to "include" a certain component, unless otherwise stated, it does not exclude other components, but means that other components may be included.

[0028] Although the terms first, second, etc. are used to represent various elements in this article in some examples, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, the first interface and the second interface, etc. are represented. Moreover, as used in this article, the singular forms "one", "one" and "the" are intended to also include plural forms, unless there is an opposite indication in the context. It should be further understood that the terms "comprising" and "including" indicate that there are the described features, steps, operations, elements, modules, projects, kinds, and / or groups, but do not exclude the existence, occurrence or addition of one or more other features, steps, operations, elements, modules, projects, kinds, and / or groups. The terms "or" and "and / or" used herein are interpreted as inclusive, or mean any one or any combination. Therefore, "A, B or C" or "A, B and / or C" means "any of the following: A; B; C; A and B; A and C; B and C; A, B and C". Only when the combination of elements, functions, steps or operations is inherently mutually exclusive in some way, will there be an exception to this definition.

[0029] The technical terms used herein are only used to refer to specific embodiments and are not intended to limit the present application. The singular form used herein also includes the plural form unless the sentence clearly indicates the contrary meaning. The meaning of "including" used in the specification is to specify specific characteristics, regions, integers, steps, operations, elements and / or components, and does not exclude the existence or addition of other characteristics, regions, integers, steps, operations, elements and / or components.

[0030] Although not defined differently, all terms, including technical and scientific terms used herein, have the same meaning as those generally understood by those skilled in the art to which this application belongs. Terms defined in commonly used dictionaries are additionally interpreted as having meanings consistent with relevant technical literature and the message of the present disclosure, and as long as they are not defined, they should not be overly interpreted as ideal or very formal meanings.

[0031] At present, in mobile communication networks, when providing edge services for users' mobile terminals UE, it is necessary to find and discover the IP address of the corresponding edge application server EAS. Although the edge application server discovery function network element EASDF is currently used to take charge of this service, the SMF is required to select the appropriate target EASDF for the UE from various EASDFs, which increases the work of the SMF. Moreover, the SMF is also required to return the EAS IP obtained from the DNS query from the target EASDF to the UE, which causes a delay problem.

[0032] In view of this, a corresponding solution is provided in the embodiment of the present application. By forming an innovative block chain system for each EASDF, it can provide the target EASDF itself to complete the DNS query of the EAS IP, without the need for SMF to be responsible for EASDF selection, thereby solving the above problem.

[0033] like Figure 1 As shown, a schematic diagram of an application scenario in an embodiment of the present application is shown.

[0034] exist Figure 1 In the present invention, the mobile terminal 101, namely the UE, may be a smart phone, a tablet computer, etc., and may access a mobile communication network through a wireless base station 102. The mobile communication network may be a 5G network or a later communication standard network, such as 6G.

[0035] The base station 102 is connected to the mobile core network element, the user plane function network element (UPF), and the user plane function network is connected to the session management network element 103 (SMF). SMF is responsible for managing each UPF to serve the corresponding access (nearby) UE. These UPFs may include UPF (PSA), and UPF (L-PSA) and UPF (UL CL / BP) used by edge services. In the figure, UPF (L-PSA) and UPF (UL CL / BP) are used.

[0036] Each edge application server discovery function network element 104 (EASDF) is connected to form a blockchain system 105, which will be referred to as the EASDF chain below. The blockchain system 105 can communicate with the session management network element 103. Each EASDF can be connected to a DNS server, such as a local Local DNS server (LDNS), or an external DNS server.

[0037] The UE can establish a PDU session with the SMF, and the SMF will help the UE call the appropriate UPF to form a path for signaling transmission. Therefore, in some examples, the UE can send a DNS query request about EAS to the EASDF chain in the session; or, in other examples, the UE can send a DNS query request about the EAS server to the EASDF chain outside the session to avoid occupying session resources.

[0038] The DNS query request may include the UE IP address of the UE, and may also include a full domain name FQDN, a digital data network DNN to be accessed, a callback URI, the location information of the UE, etc. The EASDF chain may select the nearest EASDF for the UE as the target EASDF according to the DNN query request and the UE IP address, FQDN, the digital data network DNN to be accessed, the callback URI, the location information of the UE, etc. through DNS rule matching, and then query the EAS IP through the target EASDF and return it to the UE.

[0039] It should be particularly noted that the embodiments of the present application only schematically illustrate some network elements or terminals, which are only used to illustrate the implementation principles of the present application, and are not limited to only these network elements.

[0040] like Figure 2 FIG. 2 is a flow chart showing a method for discovering an edge application server in an embodiment of the present application. The method for discovering an edge application server can be applied to the EASDF chain and the nodes therein.

[0041] The method comprises:

[0042] Step S201: Each edge application server discovers a functional entity as a node to form a blockchain system.

[0043] Step S202: The blockchain system receives a DNS query request from a mobile terminal.

[0044] Among them, the mobile terminal is configured with the access address of the blockchain system as the DNS address. Therefore, when the mobile terminal has an EAS discovery requirement, it triggers the sending of a DNS query request to this access address of the blockchain system.

[0045] Step S203: The blockchain system obtains a target node suitable for the mobile terminal through a consensus mechanism.

[0046] In some embodiments, the content of the DNS query request may include the UE IP address, and may also include: a digital data network that the mobile terminal needs to access and a callback URI.

[0047] In some embodiments, the consensus mechanism may be one of POW, POS, DPOS, etc. Exemplarily, the consensus mechanism may be, for example, that each node may have the same method for determining the target node, such as finding the nearest EASDF for the mobile terminal according to the IP address of the mobile terminal; further, if more than a preset number, such as 2 / 3, of members in each node obtain the same target EASDF through this method, a consensus is reached to obtain the EASDF.

[0048] It can be seen that through the blockchain consensus method, each EASDF can vote on its own to obtain the target EASDF, and no longer needs to be selected by the SMF, which effectively reduces the burden concentrated on the SMF.

[0049] In some embodiments, each EASDF may obtain a target node according to content matching of the DNS query request; wherein the DNS matching rule is pre-configured or determined by a session management function network element connected to the mobile terminal.

[0050] Step S204: the target node creates a DNS context to a session management function network element connected to the mobile terminal.

[0051] In some embodiments, the target node needs to control the appropriate UPF through SMF to form a suitable path for the target node to return the DNS query response to the mobile terminal in the session.

[0052] Step S205: The target node obtains the target network address of the edge application server.

[0053] In some embodiments, in response to having obtained the target network address of the edge application server required for the DNS query request, that is, it can be queried locally, the target node returns the target network address to the mobile terminal; or, when the blockchain system does not have the target network address required for the DNS query request, the target node initiates a DNS query request to the DNS server to obtain the target network address.

[0054] Further optionally, when the blockchain system does not have the target network address required by the DNS query request, initiating a DNS query request to a DNS server to obtain the target network address, includes: responding to initiating a DNS query request to a local or remote DNS server.

[0055] Step S206: The target node sends a DNS query response corresponding to the DNS request to the terminal.

[0056] The DNS query response carries the network address of the edge application server.

[0057] To more intuitively illustrate the specific implementation of the above method, please refer to Figure 3 As shown, a schematic diagram of the signaling interaction process of the discovery method of the edge application server in an application example of the present application is shown.

[0058] It should be noted that the dotted steps in the figure are optional.

[0059] exist Figure 3 In the process, the process includes:

[0060] Step 1: UE initiates a PDU establishment request to SMF, and the PDU session establishment process between the two is called PDU Session Establishment Pocedure.

[0061] Step 2: UE sends a DNS Query to the EASDF chain.

[0062] Among them, the UE configures the access address of the EASDF chain as the default DNS address, and initiates a DNS Query through the access address EASDF chain.

[0063] Step 3: The EASDF chain adapts the DNS query according to the DNS rules such as UE IP address, FQDN, DNN, callback URI, etc., and finally determines which EASDF to serve this session and selects the target EASDF.

[0064] Among them, mainly according to the IP address of UE, the EASDF closest to the user is selected as the target EASDF.

[0065] Steps 4 to 5 are the DNS context establishment process between the target EASDF and SMF, so that the SMF selects an appropriate communication path to return a DNS response to the UE.

[0066] Step 4: The selected target EASDF calls Neasdf_DNSContext_Create Request to initiate a DNS context establishment request to SMF.

[0067] Step 5. The target EASDF calls the service operation Neasdf_DNSContext_Create Response to respond to the SMF.

[0068] Optionally, steps 6 to 7 are the update process of the DNS context of the target EASDF and SMF. Due to the characteristics of UE mobility, its location may change, and the IP address may also change, so the appropriate communication path needs to be updated.

[0069] Step 6: SMF may call Neasdf_DNSContext_Update Request (EASDF context ID, DNS message processing rules) to the target EASDF.

[0070] Among other things, this update may trigger mobility issues, such as when the problem moves to a new location, or is reported via EASDF DNS queries with certain FQDNs, or the update may trigger the insertion / removal of local PSA, such as updating rules to handle DNS information issues or new PCC rule information.

[0071] Step 7: The target EASDF responds with Neasdf_DNSContext_Update Response.

[0072] Optionally, steps 8 to 9 are executed under specific triggers:

[0073] Step 8. If the DNS query message meets the DNS message processing rules, the target EASDF reports the DNS message to SMF by calling Neasdf_DNSContext_Notify Request;

[0074] Step 9. SMF responds with Neasdf_DNSContext_Notify Response;

[0075] If the target EASDF finds the target network address EAS IP required by the DNS Query locally, it goes to step 19 and directly returns it to the UE.

[0076] Alternatively, if the target EASDF fails to obtain the EAS IP locally, steps 12 to 13 are executed.

[0077] Step 12: DNS query is sent to DNS Server.

[0078] The target EASDF processes the DNS query received from the UE: For option A, the target EASDF adds the EDNS client subnet option to the DNS query message specified in RFC 7871 [6] and sends it to the remote server C-DNS server;

[0079] For option B, the target EASDF sends the DNS Query to the local DNS server (LDNS). If there is no DNS message detection template in the DNS message processing rules (which can be preset or provided by SMF) that matches the FQDN requested in the DNS Query, the EASDF can directly send the DNS Query to the pre-configured DNS server / resolver.

[0080] Step 13: DNS Server returns a DNS Response.

[0081] After obtaining the EAS IP, the target EASDF needs to negotiate with the SMF for an appropriate path to return to the UE.

[0082] Step 14: If the IP address or FQDN of the EAS in the DNS response message matches the reporting condition provided by the SMF, the target EASDF may send a DNS message including the EAS information to the SMF by calling the Neasdf_DNSContext_Notify request.

[0083] Alternatively, if the target EASDF receives multiple EAS IP addresses from the contacted DNS server, the DNS message report may include multiple EAS IP addresses. The DNS message report may include the FQDN and ECS options received in the DNS response message. According to the obtained DNS message processing rules, the target EASDF does not send a DNS Response message to the UE first, but waits for the SMF instruction in step 17 to execute and send a DNS Response, that is, caches the DNS Response message first.

[0084] Step 15. SMF calls Neasdf_DNSContext_Notify to respond to the service operation.

[0085] Step 16: SMF can select UPF UL-CL / BP and UPF Local PSA (L-PSA), and insert UPF ULCL / BP and UPF Local PSA. That is, SMF selects a suitable UPF to form a path to return the DNS Response.

[0086] Step 17. SMF calls Neasdf_DNSContext_Update Request.

[0087] Wherein, after the return path is determined, the target EASDF sends the DNS Response message cached in step 14 to the UE. Possibly, the DNS rule corresponding to the Neasdf_DNSContext_Update Request may instruct the target EASDF not to send the DNS Response message corresponding to the FQDN range and / or EAS IP address range belonging to the dynamic ARP attack (Dynamic ARP Inspection);

[0088] Step 18: The target EASDF responds with Neasdf_DNSContext_Update Response.

[0089] Step 19: The target EASDF sends a DNS Response message to the UE, which carries the obtained EAS IP.

[0090] It should be noted that the process or method represented by the flowchart of the above embodiment of the present application can be understood as a module, fragment or part of a code that represents one or more executable instructions for implementing the steps of a specific logical function or process. And the scope of the preferred embodiment of the present application includes other implementations, in which the functions may not be performed in the order shown or discussed, including performing the functions in a substantially simultaneous manner or in a reverse order according to the functions involved.

[0091] For example, Figure 2 , Figure 3 The order of the steps in the embodiments may be changed in specific scenarios and is not limited to the above.

[0092] like Figure 4 As shown, a schematic diagram of the circuit structure of a network device in an embodiment of the present application is shown.

[0093] The network device 400 may be a server, a server group, etc.

[0094] The network device 400 includes a bus 401, a processor 402, a memory 403, and a communicator 404. The processor 402 and the memory 403 can communicate with each other through the bus 401. The memory 403 may store program instructions. The processor 402 implements, for example, Figure 1 The target node in the blockchain system is the target EASDF.

[0095] The bus 401 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, although Figure 1 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0096] In some embodiments, the processor 402 may be implemented as a central processing unit (CPU), a microprocessing unit (MCU), a system on chip (System On Chip), or a field programmable logic array (FPGA). The memory 403 may include a volatile memory (Volatile Memory) for temporary storage of data when running a program, such as a random access memory (Random Access Memory, RAM).

[0097] The memory 403 may also include a non-volatile memory (non-volatile memory) for data storage, such as a read-only memory (ROM), a flash memory, a hard disk drive (HDD), or a solid-state disk (SSD).

[0098] The communicator 404 is used to communicate with the outside. In a specific example, the communicator 404 may include one or more wired and / or wireless communication circuit modules. For example, the wired communication circuit module may include one or more of a wired network card, a USB module, a serial interface module, etc. For another example, the wireless communication protocol followed by the wireless communication module includes: for example, near field communication (NFC) technology, infrared (IR) technology, global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), wideband code division multiple access (WCDMA), time division code division multiple access (TD-SCDMA), long term evolution (LTE), Bluetooth (BT), global navigation satellite system (GNSS), etc. One or more.

[0099] In an embodiment of the present application, a blockchain system may be provided, which is characterized by comprising: Figure 4 The node implemented by the network device.

[0100] In an embodiment of the present application, a computer-readable storage medium may also be provided, storing program instructions, and the program instructions are executed when running by the node in the blockchain system in the previous embodiment, namely, EASDF.

[0101] That is, the method steps in the above embodiments are implemented as software or computer code that can be stored in a recording medium (such as a CD ROM, RAM, floppy disk, hard disk or magneto-optical disk), or are implemented as computer code originally stored in a remote recording medium or a non-temporary machine-readable medium downloaded via a network and to be stored in a local recording medium, so that the method represented herein can be stored in such software processing on a recording medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware (such as an ASIC or FPGA).

[0102] In summary, the embodiments of the present application provide a method, device, blockchain system and medium for discovering edge application servers, and form a blockchain system, namely an EASDF chain, by discovering functional entities (EAS) according to each edge application server, so as to directly provide a suitable target EASDF responsible for the corresponding session service according to the DNS query request of the mobile terminal (UE) about the IP address of the EAS server, thereby satisfying the DNS query request of the UE. Compared with the related art, it is necessary to determine the target EASDF and obtain the EAS IP address through SMF, which effectively improves efficiency, reduces the burden of SMF and reduces latency.

[0103] The above embodiments are merely illustrative of the principles and effects of the present application and are not intended to limit the present application. Anyone familiar with the technology may modify or change the above embodiments without violating the spirit and scope of the present application. Therefore, all equivalent modifications or changes made by a person of ordinary skill in the art without departing from the spirit and technical ideas disclosed in the present application shall still be covered by the claims of the present application.

Claims

1. A method for discovering an edge application server, characterized in that: The method is applied to discover the network address of an edge application server for a mobile terminal of a user in a mobile communication network; the method comprises: Each edge application server discovers a functional entity as a node to form a blockchain system; The blockchain system receives a DNS query request from a mobile terminal; wherein the mobile terminal is configured with an access address of the blockchain system as a DNS address; The blockchain system obtains a target node suitable for the DNS query request through a consensus method; The target node creates a DNS context to a session management function network element connected to the mobile terminal; The target node obtains the target network address of the edge application server; The target node sends a DNS query response corresponding to the DNS query request to the terminal; The DNS query response carries the target network address of the edge application server.

2. The method for discovering an edge application server according to claim 1, characterized in that: The blockchain system obtains a target node suitable for the DNS query request through a consensus method, including: More than a preset number of nodes in the blockchain system participate in the consensus, and an available node closest to the mobile terminal is obtained as the target node.

3. The method for discovering an edge application server according to claim 2, characterized in that: The DNS query request carries the network address of the mobile terminal, so that the blockchain system can determine the location of the mobile terminal based on the network address.

4. The method for discovering an edge application server according to claim 1, characterized in that: Also includes: In response to a preset event related to a change in location of the mobile terminal, the DNS context is updated between the target node and the session management function network element.

5. The method for discovering an edge application server according to claim 2, characterized in that: The edge application server discovers the functional entity through a DNS matching rule to obtain a target node according to the content of the DNS query request; wherein the DNS matching rule is pre-configured or configured by a session management function network element connected to the mobile terminal.

6. The method for discovering an edge application server according to claim 2 or 5, characterized in that: The content of the DNS query request also includes: the FQDN, the digital data network, and the callback URI that the mobile terminal needs to access.

7. The method for discovering an edge application server according to claim 1, characterized in that: include: In response to having obtained the target network address of the edge application server required by the DNS query request, the target node returns the target network address to the mobile terminal; Alternatively, when the blockchain system does not have the target network address required by the DNS query request, the target node initiates a DNS query request to the DNS server to obtain the target network address.

8. The method for discovering an edge application server according to claim 7, characterized in that: When the blockchain system does not have the target network address required by the DNS query request, the target node initiates a DNS query request to the DNS server to obtain the target network address, including: In response to the blockchain system not having the target network address required by the DNS query request, the target node initiates a DNS query request to a local or remote DNS server.

9. A network device, characterized in that: include: Communicator, memory and processor; The communicator is used for communicating with the outside; The memory is used to store program instructions; The network device is applied to or implements a node in a blockchain system, and the processor is used to run the program instructions to implement the edge application server discovery method described in any one of claims 1 to 8.

10. A blockchain system, characterized in that: include: A node implemented by the network device according to claim 9.

11. A computer-readable storage medium, characterized in that: Program instructions are stored, and when the program instructions are executed, the method for discovering the edge application server according to any one of claims 1 to 8 is implemented.

Images