Node search method and apparatus, node device, storage medium, and computer program product

Abstract

The present application discloses a node search method and apparatus, a node device, a storage medium, and a computer program product. The method comprises: a first node receives a first request sent by a second node.

Description

Cross-reference of Related Applications

[0001] This application is based on and claims priority to Chinese Patent Application No. 202410890028.0, filed on July 3, 2024, the entire contents of which is incorporated herein by reference. TECHNICAL FIELD

[0002] The present application relates to the field of communication technology, and in particular to a node searching method, device, node equipment, storage medium and computer program product. BACKGROUND

[0003] Immersive multimedia interactive services, such as extended reality (XR) services, require networks to be flexible and elastic in networking on the basis of supporting large-scale user communication and computing, and to propose more extreme requirements for network indicators. However, the existing technical solutions have the problem of poor quality of service (QoS) of XR services. SUMMARY

[0004] To solve the problems in the related art, the embodiments of the present application provide a node searching method, device, node equipment, storage medium and computer program product.

[0005] The technical solutions of the embodiments of the present application are implemented as follows:

[0006] The embodiments of the present application provide a node searching method applied to a first node, and the method comprises the following steps.

[0007] Receiving a first request sent by a second node.

[0008] The embodiments of the present application also provide a node searching method applied to a second node, and the method comprises the following steps.

[0009] Sending a first request to a first node.

[0010] The embodiments of the present application also provide a node searching method applied to a fourth node, and the method comprises the following steps.

[0011] Receiving a second request sent by a first node.

[0012] The embodiments of the present application also provide a node searching method applied to a third node, and the method comprises the following steps.

[0013] Receiving a seventh request sent by a fourth node.

[0014] The embodiment of the present application further provides a node searching device, comprising:

[0015] The first receiving unit is configured to receive the first request sent by the second node.

[0016] The embodiment of the present application further provides a node searching device, comprising:

[0017] The first sending unit is configured to send the first request to the first node.

[0018] The embodiment of the present application further provides a node searching device, comprising:

[0019] The second receiving unit is configured to receive the second request sent by the first node.

[0020] The embodiment of the present application further provides a node searching device, comprising:

[0021] The third receiving unit is configured to receive the fifth request sent by the fourth node.

[0022] The embodiment of the present application further provides a first node, comprising a first processor and a first communication interface; wherein,

[0023] The first communication interface is configured to receive the first request sent by the second node.

[0024] The embodiment of the present application further provides a second node, comprising a second processor and a second communication interface; wherein,

[0025] The second communication interface is configured to send the first request to the first node.

[0026] The embodiment of the present application further provides a fourth node, comprising a third processor and a third communication interface; wherein,

[0027] The third communication interface is configured to receive the second request sent by the first node.

[0028] The embodiment of the present application further provides a third node, comprising a fourth processor and a fourth communication interface; wherein,

[0029] The fourth communication interface is configured to receive the seventh request sent by the fourth node.

[0030] The embodiment of the present application further provides a node device, comprising a processor and a memory for storing a computer program capable of running on the processor,

[0031] Wherein, the processor is configured to run the computer program, and execute the steps of any method on the first node side or the second node side or the third node side or the fourth node side.

[0032] The embodiment of the present application further provides a storage medium, which has a computer program stored thereon, and the computer program is executed by a processor to implement the steps of any of the above methods.

[0033] The embodiment of the present application further provides a computer program product, which comprises a computer program, and the computer program is executed by a processor to implement the steps of any of the above methods.

[0034] In the node searching method, the node device, the storage medium and the computer program product provided by the embodiment of the present application, the second node sends a first request to the first node; the first node receives the first request and sends a second request to the fourth node; the fourth node receives the second request and sends a fifth request to the third node; and the third node receives the fifth request. It can be seen that in the embodiment of the present application, the second node can search for the third node through the first node, and can search for the third node meeting the requirements to provide services for the related application or the related service, so as to meet the data processing requirements of the related application or the related service, guarantee the QoS of the related application or the related service, and improve the QoE of the user. BRIEF DESCRIPTION OF DRAWINGS

[0035] FIG. 1 is a flowchart of a node searching method according to an embodiment of the present application;

[0036] FIG. 2 is a schematic diagram of a third node registration process according to an embodiment of the present application;

[0037] FIG. 3 is a schematic diagram of a third node information updating process according to an embodiment of the present application;

[0038] FIG. 4 is a schematic diagram of a third node deregistration process according to an embodiment of the present application;

[0039] FIG. 5 is a flowchart of a node searching method according to an embodiment of the present application;

[0040] FIG. 6 is a flowchart of a node searching method according to an embodiment of the present application;

[0041] FIG. 7 is a flowchart of a node searching method according to an embodiment of the present application;

[0042] FIG. 8 is a schematic diagram of an interaction process of a node searching method according to an embodiment of the present application;

[0043] FIG. 9 is a schematic diagram of a node searching device according to an embodiment of the present application;

[0044] FIG. 10 is a schematic diagram of a node searching device according to an embodiment of the present application;

[0045] FIG. 11 is a schematic diagram of a node searching device according to an embodiment of the present application;

[0046] FIG. 12 is a schematic diagram of a node searching device according to an embodiment of the present application;

[0047] FIG. 13 is a schematic diagram of a first node structure according to an embodiment of the present application;

[0048] FIG. 14 is a schematic diagram of a second node structure according to an embodiment of the present application;

[0049] FIG. 15 is a schematic diagram of a fourth node structure according to an embodiment of the present application;

[0050] FIG. 16 is a schematic diagram of a third node structure according to an embodiment of the present application. DETAILED DESCRIPTION

[0051] Immersive multimedia interaction requires that the network must be flexibly and elastically networked on the basis of supporting large-scale user communication and calculation, and puts forward more extreme requirements for network indicators. For example, the meta-universe business requires the network to change from capability-oriented to service-oriented in terms of network business interaction and cooperation, enhances the fusion design with applications, establishes multiple cooperation modes with applications, and better supports the demand for strong interaction. In terms of enabling technology, interaction technology, artificial intelligence (AI), digital twin technology, blockchain technology and non-fungible token (NFT) are needed to realize the transformation from network to service; support the creation and interaction of rich virtual world scenarios.

[0052] For future communication networks (such as 5G-A / 6G networks), the extended reality (XR) business has more extreme and customized requirements for computing. Whether the user can choose appropriate edge applications with matching computing capabilities becomes a crucial factor affecting user experience. However, in related technologies, the devices providing services for the XR business cannot meet the data processing requirements of the XR business, the QoS of the XR business is poor, and the quality of experience (QoE) of the user is affected.

[0053] Based on this, in various embodiments of the present application, the second node sends a first request to the first node; the first node receives the first request and sends a second request to the fourth node; the fourth node receives the second request and sends a fifth request to the third node; and the third node receives the fifth request. As can be seen, in the embodiments of the present application, the second node can find the third node through the first node, and can find the third node that meets the requirements to provide services for related applications or related businesses to meet the data processing requirements of related applications or related businesses, and can guarantee the QoS of related applications or related businesses and improve the QoE of users.

[0054] Embodiments of the present application provide a node searching method, applied to a first node, the first node can include one or more of the following: an edge enabler client (EES), an edge configuration server (ECS), and an edge configuration management (ECM), that is, the first node can be an EES and / or an ECS and / or an ECM, and the EES can be understood as an edge enabler server or an edge enabler service end. As shown in FIG. 1, the method includes the following steps:

[0055] Step 101: receiving a first request sent by a second node.

[0056] In an embodiment, the first request is used to search for a third node. The first request can be understood as a search request or a discovery request of the third node, for example, in the case where the third node includes an EAS, the first request can be an EAS discovery request (EAS discovery request message).

[0057] In order to enable the EEC to search for an EAS for providing a service through the EES, in an embodiment, the second node includes one or more of the following: an edge enabler client (EEC), a terminal, a user equipment (UE), and a user.

[0058] In an embodiment, the third node includes one or more of the following: an edge application server (EAS), an application function (AF), and an application service.

[0059] Here, the second node includes an EEC and / or a terminal and / or a UE and / or a UE, the EEC is a client deployed on the terminal, and the EEC and / or an AC can be deployed in the terminal. The third node can be an EAS and / or an AF and / or an application service, and the EAS can be understood as an edge application server / edge application service end. The EES corresponds to the EEC, the EES can provide services for the EEC, the EES can be used to enable the EAS, and the EAS can provide services for the AC.

[0060] It should be noted that in the case where the first node is an EES, the second node is an EEC, and the third node is an EAS, the EEC can search for the EAS through the EES, so as to select a suitable EAS to provide services for the related business of the AC, improve the QoS of the related business of the AC, and improve the QoE of the user. The related business of the AC includes an XR business.

[0061] To facilitate the first node to find a third node matching the requirement of the second node, the first request carries the requirement information of the third node. Based on this, in an embodiment, the first request carries one or more of the following:

[0062] computing requirements;

[0063] computing resource requirements;

[0064] dynamic computing resource requirements;

[0065] temporary computing requirements;

[0066] single computing requirements;

[0067] specific computing requirements;

[0068] computing accuracy;

[0069] computing task;

[0070] duration of the computing task;

[0071] identifier of the third node;

[0072] application service Key Performance Indicator (KPI);

[0073] computing requirements of the XR application;

[0074] application identifier;

[0075] computing requirements;

[0076] computing accuracy;

[0077] computing task;

[0078] duration of the computing task;

[0079] location information;

[0080] type of the third node;

[0081] identifier of the second node;

[0082] expected access duration of the third node;

[0083] service duration;

[0084] service identity;

[0085] service characteristics of the application or service;

[0086] user identity.

[0087] Here, the first request carries at least the computing power requirement, and can also carry one or more of the above information other than the computing power requirement; the computing power requirement can also be understood as a computing requirement. In the case where the first request carries the computing power requirement, the first node is characterized by finding a third node that meets the computing power requirement. Compared with the existing process, the first request carrying the computing power requirement can make the first node preferentially find a third node that meets the computing power requirement, improve the matching degree of the computing power capability (computing capability) of the found third node and the computing power requirement, and thus improve the QoS of the service of the third node or improve the QoE of the user. In the case where the first node is an EES, the second node is an EEC and / or an AC, and the third node is an EAS, the EEC carries the computing power requirement in the process of selecting the EAS, so as to select a suitable EAS, which can provide an extreme XR experience for the user.

[0088] The computing requirement can be understood as a computing requirement of the third node, can include an application computing requirement and / or a computing requirement of the fifth node (for example, an AC) and / or an XR application computing requirement, and the third node can provide services for the application and / or the fifth node and / or the XR application. The computing requirement can also be a computing resource requirement, a dynamic computing resource requirement, a temporary computing resource requirement, a one-time computing resource requirement, and a specific computing resource requirement. The English description of the computing requirement can be: computing requirements, computing resource requirements, computing capability requirements, dynamic computing resource / capability requirements, temporary computing resource / capability requirements, one time computing resource / capability requirements, specific resource / capability computing requirements. The computing requirement at least includes a computing type and / or a computing precision, and can further include a computing task and / or a duration of the computing task and / or a service duration and / or an estimated access duration to the third node. The computing task can be described as a computing task, and the duration of the computing task can be described as a computing task duration. The computing type includes one or more of the following: an accelerated processing unit (APU), a central processing unit (CPU), a deep learning processing unit (DPU), a graphics processing unit (GPU), a neural network processing unit (NPU), and a tensor processing unit (TPU).The computing precision includes one or more of the following: Million Instructions Per Second (MIPS), Dhrystone Million Instructions Per Second (DMIPS), Operations Per Second (OPS), Floating-point Operations Per Second (FLOPS).

[0089] The identity of the third node can be described as a third node ID (Identifier / Identification). When the third node is an EAS, the identity of the third node can be an EAS ID. In the case where the first request carries the identity of the third node, it represents a search for the third node indicated by the identity.

[0090] The application service KPI can be understood as an AC service KPI or an XR application service KPI, and the KPI is not limited here. The XR application can be understood as an application related to XR service. In the case where the first request carries the application service KPI, it represents a search for a third node that can provide services that meet the application service KPI.

[0091] The application identity refers to the identity of an application (application), which includes an application corresponding to an AC and / or an application corresponding to an EEC and / or an XR application. The application identity can be described as a third-party application ID, an AC ID (Application Client Identification), an application ID, and an application type. In the case where the first request carries the application identity, it represents a search for a third node that can provide services for the application corresponding to the application identity.

[0092] The user identity can be understood as the identity of a user of the second node or the identity of a terminal deploying the second node, such as a UE ID, where UE refers to a user equipment (User Equipment). The user identity can be used to determine whether the user has access to the third node, or to determine whether the third node allows the corresponding user to access.

[0093] The position information can be understood as position information of the second node or position information of a terminal that deploys the second node. The position information can be physical position information such as latitude and longitude information, can be a tracking area identifier (TAI), and can also be a data network access identifier (DNAI). The position information is used to determine the distance between the third node.

[0094] The type of the third node can be described as an EAS type, and the EAS type includes vehicle-to-everything (V2X) and / or unmanned aerial vehicle (UAV). In a case where the first request carries the type of the third node, the third node that matches the type of the third node is searched for. The identity of the second node can be described as an EEC identity or EEC ID, and the identity of the second node is used for the first node to identify the second node. The predicted access duration of the third node can be described as a predicted access duration or a predicted access duration of the EAS. In a case where the first request carries the predicted access duration of the third node, the third node whose available computing power duration is greater than or equal to the predicted access duration is searched for. The service identity can be described as a service type, and the service identity includes an identity of an XR service or an identity of a service type, and the XR service or the service type includes an XR game. In a case where the first request carries the service identity, the third node that supports the corresponding service or the third node that can provide services for the corresponding service is searched for.

[0095] The service feature of the application or the service includes one or more of the following: a service feature of the second node, a service feature of a service corresponding to the second node, and a service feature of an XR service, such as an XR game wideband. The service feature of the application or the service can be referred to as a service feature. In a case where the first request carries the service feature of the application or the service, the third node that meets or has the service feature is searched for.

[0096] To facilitate the second node to learn whether the first node finds the third node, the first node can return a first response to the second node after receiving the first request. Based on this, in an embodiment, after receiving the first request, the method further includes:

[0097] sending a first response to the second node, the first response indicating endpoint information of the found third node or that no third node is found.

[0098] Here, after receiving the first request, the first node finds the third node based on the first information, and returns the first response to the second node. For example, the first node can select one or more third nodes closest to the location information and / or one or more third nodes satisfying the computing power requirement and / or the service feature based on the application ID, the location information, the type of the third node, the computing power requirement and the service feature carried by the first request; the selected third node can provide a service for the application corresponding to the application ID and match the type of the third node. For another example, the first node can determine the third node matching the application ID, the location information and the type of the third node from the third nodes managed by the first node according to the application ID, the location information and the type of the third node carried by the first request, and find the third node matching the computing power requirement and / or the service feature carried by the first request from the determined third node.

[0099] In the case of finding the third node, the first response indicates the found third node, and the first response can carry the endpoint information of the found third node; the endpoint information of the third node is used to access the third node, and the endpoint information of the third node can include the access address of the third node, such as the IP address and / or FQDN of the third node. The found third node matches part or all of the information carried by the first request, for example, the found third node satisfies the computing power requirement and / or the service feature carried by the first request, and / or is closest to the position indicated by the location information carried by the first request. In the case of not finding the third node, for example, no third node matching part or all of the information carried by the first request is found; for another example, no third node matching the computing power requirement and / or the service feature carried by the first request is found, and / or no third node closest to the position indicated by the location information carried by the first request is found.

[0100] In order to find a suitable third node, in an embodiment, the method further includes one or more of the following:

[0101] Finding the third node based on the first information;

[0102] Locally finding the third node indicated by the first request;

[0103] Locally finding the third node satisfying the requirement of the first task, the first task being split according to the computing power task and / or the time length of the computing power task carried by the first request;

[0104] Negotiating with the second node to reduce the computing precision;

[0105] Feeding back the third node satisfying the first condition to the second node. In order to find a suitable third node, in an embodiment, the first information includes one or more of the following:

[0106] a lookup filter of the third node; location information; a service KPI of the fifth node; a computing requirement of the XR service.

[0107] In an embodiment, the fifth node comprises one or more of: an AC, a terminal, a UE, a user. That is, the fifth node can be an AC and / or a terminal and / or a UE and / or a user.

[0108] Here, the first node can find the third node based on the first information upon receiving the first request and obtaining the first information. The first information can comprise one or more of: a lookup filter of the third node, location information (e.g. UE location), a service KPI of the fifth node, a computing requirement of the XR service. The lookup filter of the third node can be described as EAS discovery filters; the service KPI of the fifth node can be described as an AC service KPI, that is, the fifth node can be an AC; the computing requirement of the XR service can be described as a computing power requirement of the XR service.

[0109] The first node can find the third node indicated by the first request locally based on the first request upon receiving the first request; and feed back the found third node to the second node upon finding the third node indicated by the first request. The third node indicated by the first request can be understood as the third node matching part or all of the information carried by the first request. It should be noted that the local database of the first node stores the related information of the third node registered successfully in the first node, and the first node supports the third node to register and / or update and / or deregister. It should be noted that the first node can update the related information of the third node registered successfully stored locally upon the third node completing registration or update or deregistration; and the first node can further find the third node indicated by the first request locally and / or find the third node meeting the requirement of the first task locally after a new third node completes registration.

[0110] The first node can split the computing power task according to the computing power task and / or the duration of the computing power task carried by the first request to obtain a plurality of first tasks in a case where the first request is received; and locally search for a third node satisfying the demand of the first task. The first task can be understood as a subtask of the computing power task. The first node can also split the computing power task according to the computing power task and / or the duration of the computing power task carried by the first request to obtain a plurality of first tasks in a case where the third node indicated by the first request is not found locally, that is, a third node matching part or all of the information carried by the first request is not found. The first node can also locally search for a third node satisfying the demand of the first task. The demand of the first task is determined according to one or more of the following: an application identifier, a computing power demand, a computing accuracy, location information, a type of the third node, an identifier of the second node, an estimated access duration to the third node, a service duration, a service identifier, a service feature of the application or service, and a user identifier.

[0111] In actual application, the first node can split the computing power task according to the computing power task and / or the duration of the computing power task carried by the first request to obtain a plurality of first tasks in a case where the third node satisfying all the demands indicated by the first request is not found. For example, the computing power task is divided into N sub-period tasks according to the duration of the computing power task; for example, a computing task from 14:00 to 14:30 is split into three subtasks for the time periods of 14:00-14:10, 14:10-14:20, and 14:20-14:30.

[0112] In a case where the first request carries the computing accuracy, the first node can negotiate with the second node to reduce the computing accuracy in a case where the third node indicated by the first request is not found locally; or negotiate with the second node to reduce the computing accuracy in a case where the third node satisfying the demand of the first task is not found locally. After the computing accuracy is reduced, the first node can search for the third node again according to the updated computing accuracy and other information carried by the first request.

[0113] The first node can feed back the third node satisfying the first condition to the second node in a case where the third node is found.

[0114] In an embodiment, the first condition includes one or more of the following:

[0115] Closest to the second node;

[0116] Satisfying the demand of the second node;

[0117] The third node indicated by the first request;

[0118] Matching part or all of the information carried by the first request;

[0119] satisfy the requirement of the first task.

[0120] Here, satisfying the requirement of the second node can be described as matching part or all of the information carried by the first request, or as satisfying the computing power requirement and / or service characteristics carried by the first request.

[0121] To find a suitable third node, in an embodiment, the method further comprises:

[0122] sending a second request to a fourth node.

[0123] Here, the first node can send the second request to the fourth node before receiving the first request, or send the second request to the fourth node based on the first request when no third node is found locally. The second request can carry part or all of the information carried by the first request, for finding the third node. The second request can be understood as a finding request.

[0124] In an embodiment, the fourth node comprises a management system of the AF and / or ECSP.

[0125] In an embodiment, the second request carries one or more of the following:

[0126] computing power requirement; computing accuracy; computing power task; duration of the computing power task; identification of the third node; application service KPI; computing power requirement of the XR application; application identification; location information; type of the third node; identification of the second node; estimated access duration to the third node; service duration; service identification; service characteristics of the application or service; user identification.

[0127] Here, the first node can send second information to the fourth node based on the first request, and the second request carries at least the computing power requirement and / or the computing power requirement of the XR application, and can also carry the above-mentioned other information.

[0128] To find a suitable third node, in an embodiment, the method further comprises:

[0129] receiving second information sent by the fourth node, the second information indicating an instantiable third node.

[0130] Here, the first node can receive the second information sent by the fourth node before or after receiving the first request, or receive the second information sent by the fourth node before or after sending the second request to the fourth node. The instantiable third node can be described as an instantiable EAS, and the instantiable EAS can be used to provide services.

[0131] In an embodiment, the second information comprises identification of the instantiable third node and / or available computing power and / or available computing power duration.

[0132] Here, in the case that the third node is an EAS, the identity of the third node can be described as an EAS ID, the available computing capability can include available computing types, and the available computing capability can be understood as available computing power capability; the available computing power duration can be understood as available computing duration.

[0133] The third node can initiate registration with the first node before or after the second node initiates the process of finding or discovering the third node to the first node. Based on this, in an embodiment, the method further includes one or more of the following:

[0134] receiving a third request sent by the third node; the third request at least carries computing power information, and is used to request registration of the third node;

[0135] storing information carried by the third request;

[0136] sending a second response to the third node; the second response indicates that the registration of the third node is successful or failed, and in the case that the second response indicates that the registration of the third node is successful, the second response carries a registration identity.

[0137] Here, the first node can also receive a third request sent by the third node before receiving the first request, or can receive the third request sent by the third node after sending the second request to the fourth node; the third request at least carries computing power information of the third node. The third node can actively initiate a registration process, or can initiate the registration process in the case that the second request sent by the fourth node is received. For example, the third node sends the third request to the first node after completing instantiation, and the first node receives the third request. For another example, the first node sends the second request to the fourth node in the case that the third node is not found locally, and receives the third request sent by the third node.

[0138] In the case that the third request is received, the first node determines whether the third node has the right to register at the first node; in the case that the third node has the right to register at the first node, the registration of the third node is completed at the first node, and a registration identity (registration ID) can also be allocated to the third node. In the case that the third node does not have the right to register at the first node, the third request is rejected, and the third node is not allowed to register to the first node.

[0139] In the case that the third node has the right to register at the first node, the first node can also store information carried by the third request locally; the information carried by the third request can be understood as registration information of the third node.

[0140] In the case that the third request is received, the first node can return a second response to the third node.

[0141] To facilitate the first node to determine whether the third node can meet the computing power requirement, in an embodiment, the third information, the computing power information includes one or more of the following:

[0142] Computing type, the computing type includes one or more of the following: APU, CPU, DPU, GPU, NPU, TPU;

[0143] Computing precision, the computing precision includes one or more of the following: MIPS, DMIPS, OPS, FLOPS;

[0144] Available computing power duration.

[0145] Among them, the available computing power duration refers to the available computing power duration, the duration that can provide computing power service or computing service.

[0146] In an embodiment, the third request also carries one or more of the following information of the third node:

[0147] EAS file (profile);

[0148] Registration expiration time;

[0149] Third node identifier;

[0150] Fully qualified domain name (FQDN);

[0151] Internet protocol (IP) address;

[0152] Application service provider information;

[0153] Information of edge computing service provider (ECSP);

[0154] Permission information;

[0155] Third node type;

[0156] Location information;

[0157] Available duration;

[0158] Business capacity;

[0159] Data network access identifier (DNAI);

[0160] Load information.

[0161] Here, the third node identifier can be referred to as an EAS identifier. The permission information is used to indicate the user or user group allowed to access the third node, that is, the permission information indicates which user or user group is allowed to access; the permission information can contain relevant information of the user or user group allowed to access the third node. The third node type can be referred to as an EAS type, and the EAS type includes V2X and / or UAV. The location information carried by the third request is the location information of the third node, which can be the physical location information of the third node, such as longitude and latitude, or can be TAI.

[0162] FIG. 2 shows a registration process of the third node. As shown in FIG. 2, the registration process of the third node is as follows:

[0163] 1. The third node determines whether it needs to register with the first node.

[0164] 2. In the case where the third node needs to register with the first node, the third node sends a third request to the first node, and the third request is used to request registration of the third node.

[0165] For example, the third node has completed instantiation and / or the third node is started to be used, and the third node sends a third request to the first node. The third request carries at least the computing power information of the third node, and can also carry one or more of the following information of the third node: the third node identifier, the FQDN, the IP address, the application service provider information, the information of the ECSP, the permission information, the third node type, the location information, the available duration, the service capacity, the DNAI, and the load information. The computing power information includes the computing type and / or the computing accuracy and / or the available computing power duration.

[0166] In actual application, in the case where the first node is an EES and the third node is an EAS, the third request carries the computing power information of the EAS, the EAS ID, the FQDN or IP address of the EAS, the application service provider information or the information of the ECSP, the permission information (which user or user group is allowed to access), the EAS type (such as V2X or UAV), the location information, the available duration or the available computing power duration, the service capacity, and the DNAI.

[0167] 3. The first node receives the third request, determines whether the third node has the permission to register or whether the third node is allowed to register, and in the case where the third node has the permission to register or is allowed to register, stores the information carried by the third request and allocates a registration identifier (registration ID) to the third node. For example, the first node checks the application service provider information and / or the information of the ECSP and / or the third node identifier of the third node, and in the case where the information is correct, it indicates that the third node has the permission to register on the first node; the first node stores the information carried by the third request.

[0168] 4. The first node sends a second response to the third node, the second response indicating that the third node is registered successfully or fails, and in the case that the second response indicates that the third node is registered successfully, the second response carries the registration identifier.

[0169] After the third node completes the registration, the third node can initiate the process of updating the registration information before or after the second node initiates the process of finding or discovering the third node to the first node. Based on this, in an embodiment, the method further comprises one or more of the following:

[0170] receiving a fourth request sent by the third node, the fourth request carrying at least updated computing power information for requesting to update the information of the third node;

[0171] updating the information of the third node locally based on the information carried by the fourth request;

[0172] sending a third response to the third node, the third response indicating that the information update of the third node is successful or fails.

[0173] In an embodiment, the fourth request carries one or more of the following information of the third node:

[0174] EAS profile, registration invalidation time, registration identifier, identifier of the third node, updated permission information, updated location information, updated service capacity, updated DNAI, and updated load information.

[0175] Here, in the case that the first node receives the fourth request, the first node determines whether the third node has the permission to update in the first node; in the case that the third node has the permission to update in the first node, the first node updates the information of the third node locally based on the information carried by the fourth request, and the information carried by the fourth request can be understood as the registration information that needs to be updated. In the case that the third node does not have the permission to update in the first node, for example, the third node is not registered in the first node, the fourth request is rejected.

[0176] In the case that the first node receives the fourth request, the first node can return the third response to the third node.

[0177] FIG. 3 shows a process of updating the information of the third node; as shown in FIG. 3, the process of updating the information of the third node is as follows:

[0178] 1. The third node determines whether the registration information needs to be updated to the first node or determines whether the registration update needs to be performed.

[0179] 2. In the case that the third node needs to update the registration information to the first node, the third node sends a fourth request to the first node, the fourth request being used for requesting to update the information of the third node.

[0180] For example, the registration information of the third node changes, or the validity time of the third node is about to expire, the third node sends a fourth request to the first node. The third request carries at least the registration identifier, the third node identifier, and the updated computing power information of the third node, and can also carry one or more of the following information of the third node: updated permission information, updated location information, updated available time length, updated service capacity, updated DNAI, and updated load information.

[0181] In actual application, in the case where the first node is an EES and the third node is an EAS, the third request carries the registration identifier, the EAS ID, the updated computing power information of the EAS, the updated permission information (which users or user groups are allowed to access), the updated location information, the updated available time length or available computing power time length, the updated service capacity, and the updated DNAI.

[0182] 3. The first node receives the fourth request and determines whether the third node has the permission to update the registration information or whether the third node is allowed to update the registration information. In the case where the third node has the permission to update the registration information or the third node is allowed to update the registration information, the information of the third node stored locally is updated based on the information carried in the fourth request, that is, the information (which can be referred to as registration information) of the third node stored locally is updated based on the information carried in the fourth request. For example, the first node checks the application service provider information of the third node and / or the information of the ECSP and / or the third node identifier and / or the registration identifier. In the case where the information is correct, it is indicated that the third node has the permission to update the registration information or is allowed to update the information of the third node, and the information of the third node stored locally is updated based on the information carried in the fourth request.

[0183] 4. The first node sends a third response to the third node, and the third response indicates whether the third node updates successfully or fails.

[0184] After the third node completes the registration on the first node, the third node can initiate a deregistration process to the first node. Based on this, in an embodiment, the method further includes one or more of the following:

[0185] receiving a fifth request sent by the third node; the fifth request carries at least the computing power information and is used to request to deregister the third node;

[0186] deleting the information of the third node locally;

[0187] sending a fourth response to the third node; the fourth response indicates whether the deregistration of the third node succeeds or fails.

[0188] Here, the first node, upon receiving the fifth request, determines whether the third node has the authority to de-register at the first node; in the case that the third node has the authority to de-register at the first node, completes the de-registration of the third node at the first node. In the case that the third node does not have the authority to de-register at the first node, for example, the third node is not registered at the first node, and / or the information carried by the fifth request fails verification, the fifth request is rejected.

[0189] In the case that the third node has the authority to de-register at the first node, the first node can also delete the information of the third node stored locally, i.e., delete the registration information of the third node stored locally.

[0190] The first node, upon receiving the fifth request, can return a third response to the third node.

[0191] In an embodiment, the fifth request also carries one or more of the following:

[0192] A registration identifier; an identifier of the third node; application service provider information; information of an ECSP.

[0193] FIG. 4 shows a de-registration process of the third node; as shown in FIG. 4, the de-registration process of the third node is as follows:

[0194] 1. The third node determines whether it needs to de-register at the first node.

[0195] 2. In the case that the third node needs to de-register at the first node, the third node sends a fifth request to the first node, the fifth request being used to request de-registration of the third node.

[0196] For example, the service of the third node is invalid, the third node decides to de-register at the first node, and the third node sends a fifth request to the first node. The fifth request carries at least a registration identifier of the third node and / or an identifier of the third node, and can also carry computing power information of the third node.

[0197] In actual application, in the case that the first node is an EES and the third node is an EAS, the third request carries a registration identifier of the EAS and / or an EAS ID.

[0198] 3. The first node receives the fifth request, determines whether the third node has the right to deregister, or determines whether the third node is allowed to deregister; in the case that the third node has the right to deregister or the third node is allowed to deregister, the information of the third node is deleted, that is, the information of the third node saved locally is deleted to save the storage resources of the first node. For example, the first node checks the registration identity of the third node and / or the third node identity, in the case that the information is correct, it is determined that the third node has the right to register in the first node; if the services on the third node have all ended, the first node allows the third node to deregister, and the information of the third node is deleted locally, that is, the registration information of the third node saved locally is deleted.

[0199] 4. The first node sends a fourth response to the third node, and the second response indicates that the third node deregisters successfully or fails.

[0200] Correspondingly, the embodiment of the present application also provides a node searching method, applied to a second node, the second node including one or more of the following: EEC, terminal, UE, user, that is, the second node can be EEC and / or terminal and / or UE and / or user. As shown in FIG. 5, the method includes:

[0201] Step 501: sending a first request to a first node.

[0202] Here, the first node can be an EES. Or,

[0203] In an embodiment, the first request is used to search for a third node.

[0204] In an embodiment, the first request carries one or more of the following:

[0205] Computing power demand; computing power resource demand; dynamic computing power resource demand; temporary computing power resource demand; single computing power resource demand; specific computing power resource demand; computing precision; computing power task; duration of the computing power task; identity of the third node; application service KPI; computing power demand of an XR application; application identity; location information; type of the third node; identity of the second node; expected access duration to the third node; service duration; service identity; service characteristics of the application or service; user identity.

[0206] Wherein, the third node includes one or more of the following: EAS, AF, application service. The second node includes one or more of the following: EEC, terminal, UE, user.

[0207] The first request can be sent based on a sixth request. Based on this, in an embodiment, before sending the first request to the first node, the method further includes:

[0208] Receiving a sixth request sent by a fifth node.

[0209] The fifth node includes one or more of the following: an AC, a terminal, a UE, and a user.

[0210] In an embodiment, the sixth request carries one or more of the following:

[0211] A profile of the fifth node; an identity of the third node; a service KPI of the fifth node; a computing power requirement; a computing power resource requirement; a dynamic computing power resource requirement; a temporary computing power resource requirement; a single-time computing power resource requirement; a specific computing power resource requirement; and a computing power requirement of an XR application.

[0212] Here, the second node receives the sixth request sent by the fifth node, and sends the first request to the first node based on the sixth request; the sixth request is used to access the third node, which can be an EAS; the sixth request can be understood as an application access request. The fifth node can be an AC, and the profile of the fifth node can be described as an AC profile.

[0213] In the case where the first node is an EES and the second node is an EEC, the EEC can receive the sixth request sent by the AC, the sixth request carrying an AC ID and a service identity (service identity is also referred to as service type, including XR game), and send the first request to the EES according to the sixth request. The sixth request is used to request access to an EAS.

[0214] To facilitate the first node to learn whether the third node is found by the first node, in an embodiment, after receiving the first request, the method further includes:

[0215] Receiving a first response sent by the first node, the first response indicating endpoint information of the third node or that the third node is not found.

[0216] Here, in the case where the second node is an EEC, the EEC receives the first response sent by the EES, and sends an application access response to the AC. The second response can carry an FQDN and / or an IP address of the EAS, and the AC can subsequently access the EAS based on the FQDN and / or the IP address of the EAS.

[0217] Correspondingly, an embodiment of the present application also provides a node finding method, applied to a fourth node, the fourth node including an AF and / or an ECSP management system, that is, the fourth node can be an AF and / or an ECSP management system. As shown in FIG. 6, the method includes:

[0218] Step 601: receiving a second request sent by a first node.

[0219] Here, the second request is sent by the first node based on the first request. The second request can be understood as a finding request. The first node includes an EES.

[0220] In one embodiment, the second request is used to locate a third node. The third node may be an EAS.

[0221] In order to find a suitable third node, in one embodiment, the second request carries one or more of the following:

[0222] Computing power requirements; computing resource requirements; dynamic computing resource requirements; temporary computing resource requirements; single computing resource requirements; specific computing resource requirements; computational precision; computing task; duration of computing task; identifier of third node; application service KPIs; computing power requirements for XR applications; application identifier; location information; type of third node; identifier of second node; estimated access duration to third node; business duration; business identifier; service characteristics of application or business; user identifier.

[0223] Here, the second node includes the EEC and / or the terminal.

[0224] In order to find a suitable third node or instruct a third node to initiate registration with the first node, in one embodiment, the method further includes one or more of the following:

[0225] Send a seventh request to the third node; and / or

[0226] Send a second message to the first node, the second message indicating a third node that can be instantiated.

[0227] Here, the fourth node may send a fourth request to the third node and / or send a second message to the first node before or after receiving the second request.

[0228] In one embodiment, the seventh request carries one or more of the following:

[0229] Service characteristics of the application or business; computing power requirements; computing power resource requirements; dynamic computing power resource requirements; temporary computing power resource requirements; single computing power resource requirements; specific computing power resource requirements; location information; type of third node; application identifier; estimated access duration.

[0230] In one embodiment, the seventh request is used to inquire whether the third node satisfies the information carried in the seventh request, and / or to instruct the third node to initiate registration with the first node.

[0231] Here, in a case that the fourth node sends the seventh request to the third node before receiving the second request, the seventh request can be used to instruct the third node to initiate registration to the first node; in a case that the fourth node sends the seventh request to the third node after receiving the second request, the seventh request is used to inquire whether the third node meets the information carried by the seventh request, and / or, is used to instruct the third node to initiate registration to the first node. For example, the seventh request is used to instruct the third node to initiate registration to the first node in a case that the third node meets the information carried by the seventh request.

[0232] It should be noted that the fourth node can send the seventh request to all third nodes managed by the fourth node. The fourth node can also determine, from the third nodes managed by the fourth node, a third node that matches the application identifier, the location information and the type of the third node carried by the second request, and send the seventh request to the determined second node. The seventh request is used to inquire whether the third node meets the information carried by the seventh request, or whether the third node matches the information carried by the seventh request. The seventh request at least carries the computing power requirement and / or the computing accuracy and / or the computing power task and / or the duration of the computing power task and / or the service characteristics of the application or service.

[0233] That is, the fourth node can send the seventh request to all third nodes managed by the fourth node, or can send the seventh request to part of the third nodes. For example, the part of the third nodes can be the third nodes that match the application identifier, the location information and the type of the third node carried by the second request. The seventh request is used to instruct the third node to initiate registration to the first node in a case that the third node meets the requirement indicated by the seventh request.

[0234] In actual application, in a case that the third node is an EAS and the fourth node is an ECSP management system, the ECSP management system sends the seventh request to all EASs under its management to inquire whether the service characteristics and / or the computing power requirement and / or the computing accuracy and / or the computing power task and / or the duration of the computing power task carried by the second request can be met, and instructs the EAS to initiate registration to the first node in a case that the EAS meets the requirement indicated by the second request, in a case that the application identifier, the type of the EAS and the location information carried by the second request all match all the EASs.

[0235] The EAS meeting the requirement indicated by the second request means that the EAS meets the service characteristics and / or the computing power requirement and / or the computing accuracy and / or the computing power task and / or the duration of the computing power task carried by the second request.

[0236] In order to save signaling overhead, the fourth node can send the seventh request to the third node that meets the condition. Based on this, in an embodiment, the third node is determined according to the type of the third node and / or the application identifier and / or the location information and / or the computing power requirement and / or the expected access duration and / or the service characteristics carried by the second request.

[0237] In an embodiment, the first node comprises one or more of the following: EES, ECS, ECM.

[0238] In an embodiment, the second node comprises one or more of the following: EEC, terminal, UE, user.

[0239] In an embodiment, the third node comprises one or more of the following: EAS, AF, application service.

[0240] In an embodiment, the fourth node comprises one or more of the following: AF, ECSP management system.

[0241] Correspondingly, the embodiments of the present application also provide a node searching method, applied to a third node, the third node comprising one or more of the following: EAS, AF, application service, that is, the third node can be EAS and / or AF and / or application service. As shown in FIG. 7, the method comprises:

[0242] Step 701: receiving a seventh request sent by a fourth node.

[0243] Here, the fourth node comprises AF and / or ECSP management system.

[0244] In an embodiment, the seventh request is used to inquire whether the fourth node meets the information carried by the seventh request, and / or is used to instruct the third node to initiate registration to a first node. Wherein, the third node comprises one or more of the following: EAS, AF, application service. The first node comprises one or more of the following: EES, ECS, ECM.

[0245] In an embodiment, the seventh request carries one or more of the following:

[0246] service characteristics of the application or service; computing power demand; computing power resource demand; dynamic computing power resource demand; temporary computing power resource demand; single computing power resource demand; specific computing power resource demand; location information; type of the third node; application identifier; expected access duration.

[0247] In order to facilitate the first node to search for the third node, the third node can initiate registration to the first node. Based on this, in an embodiment, the method further comprises one or more of the following:

[0248] sending a third request to the first node; wherein the third request at least carries computing power information, used to request registration of the third node;

[0249] receiving a second response sent by the first node; the second response represents that the registration of the third node is successful or failed, and in the case that the second response represents that the registration of the third node is successful, the second response carries a registration identifier.

[0250] Here, the third node can send a third request to the first node to initiate registration to the first node proactively, for example, the third node has completed instantiation and / or the third node is started to use, and send the third request to the first node; or send the third request to the first node upon receiving the seventh request sent by the fourth node. The first node comprises an EES.

[0251] In an embodiment, the computing power information comprises one or more of the following:

[0252] A computing type, the computing type comprising one or more of the following: APU, CPU, DPU, GPU, NPU, and TPU;

[0253] A computing precision, the computing precision comprising one or more of the following: MIPS, DMIPS, OPS, and FLOPS;

[0254] A duration of available computing power.

[0255] In an embodiment, the third request further carries one or more of the following information of the third node:

[0256] EAS profile, registration expiration time, identifier of the third node, FQDN, IP address, application service provider information, information of ECSP, permission information, type of the third node, location information, duration of availability, service capacity, computing type, computing precision, DNAI, and load information.

[0257] The third node comprises an EAS.

[0258] After the third node is successfully registered on the first node, the third node can further update registration information to the first node. Based on this, in an embodiment, the method further comprises one or more of the following:

[0259] Sending a fourth request to the first node, the fourth request carrying at least updated computing power information for requesting to update information of the third node;

[0260] Receiving a third response sent by the first node, the third response indicating that the update of the information of the third node is successful or failed.

[0261] Here, the third node can send the fourth request to the first node when the registration information of the third node changes or the validity time of the third node is about to expire.

[0262] In an embodiment, the fourth request carries one or more of the following information of the third node:

[0263] EAS profile; registration invalid time; registration identifier; identifier of the third node; updated permission information; updated location information; updated service capacity; updated DNAI; updated load information.

[0264] To save the storage resource of the first node, the third node can initiate deregistration to the first node actively when the third node is invalid. Based on this, in an embodiment, the method further includes one or more of the following:

[0265] sending a fifth request to the first node; the fifth request carries at least computing power information, and is used to request deregistration of the third node;

[0266] receiving a fourth response sent by the first node; the third response represents success or failure of deregistration of the third node.

[0267] Here, the third node can send the fifth request to the first node when service of the third node is invalid, and / or when the third node is invalid.

[0268] In an embodiment, the fifth request further carries one or more of the following:

[0269] registration identifier; identifier of the third node; application service provider information; information of the ECSP.

[0270] It should be noted that the fifth request can also carry the EAS profile.

[0271] The present application will be described in further detail below in combination with application examples.

[0272] The first node is an EES, the second node is an EEC, the third node is an EAS, the fourth node is an ECSP management system, and the fifth node is an AC, as shown in FIG. 8, the node searching method includes the following steps:

[0273] Step 0: EAS registration.

[0274] Here, the EAS managed by the ECSP management system initiates registration to the EES. Specifically, the ECSP management system can instruct the EAS to initiate registration to the EES, or the ECSP management system sends a third request to the EAS, the third request is used to instruct the third node to initiate registration to the first node; the EAS initiates registration to the EES.

[0275] For example, the EAS sends a third request to the EES, the third request indicates to carry the computing power information, the computing power information includes the computing type (APU, CPU, DPU, GPU, NPU, TPU), the computing precision (MIPS, DMIPS, OPS, FLOPS), and the available computing power duration. The third request can also carry one or more of the following information of the EAS: EAS identifier, FQDN, IP address, application service provider information, information of the ECSP, permission information (which users or user groups are allowed to access), EAS type (such as V2X, UAV), location information (latitude and longitude, TAI), available duration, service capacity, DNAI, load information.

[0276] The EES receives the third request, checks the application service provider information and / or the information of the ECSP and / or the EAS identifier of the EAS, and determines that the EAS has the permission to register on the EES if the check is correct. The EES allows the EAS to register, locally stores the information carried in the third request, that is, the EES locally stores the information / registration information of the successfully registered EAS. The EES allocates a registration identifier to the EAS and returns a second response to the EAS to notify the EAS of the successful registration. The second response can carry the registration identifier.

[0277] Step 1: The AC sends a sixth request to the EEC.

[0278] Here, the sixth request carries one or more of the following: AC profile, EAS ID, AC service KPI, AC computing power requirement, XR application computing power requirement, AC ID, service identifier (service identifier is also referred to as service type, including XR game); the sixth request is used to request access to the EAS.

[0279] Step 2: The EEC receives the sixth request sent by the AC and sends a first request to the EES.

[0280] Here, the first request is used to find the third node. The first request carries one or more of the following:

[0281] application identifier (such as AC ID); computing power requirement; computing power resource requirement; dynamic computing power resource requirement; temporary computing power resource requirement; single computing power resource requirement; specific computing power resource requirement; computing precision; computing power task; duration of the computing power task; EAS ID; application service KPI; XR application computing power requirement; location information; EAS type; EEC identifier; expected access duration to the EAS; service duration; service identifier (or service type, including XR game); service characteristics of the application or service; user identifier.

[0282] Here, the user identity can be an identity of the terminal deploying the AC, such as a UE ID; the location information can be location information of the terminal deploying the AC. The computing power requirement can include one or more of the following: computing type (APU, CPU, DPU, GPU, NPU, TPU), computing precision (MIPS, DMIPS, OPS, FLOPS), duration of computing power task. The service includes XR service, and the service feature of the application or service includes XR game wideband.

[0283] Step 3: The EES receives the first request and locally looks up the EAS.

[0284] Here, the EES locally looks up the EAS according to the first request. Specifically, the EES matches the information carried by the first request with the information of the locally registered EASs to find an EAS matching the information carried by the first request. In the case where multiple EASs are found, one or more EASs closest to the location indicated by the location information carried by the first request can be selected from the multiple found EASs. For example, the EES, based on the application identity, EAS type, service feature of the application or service, and computing power requirement carried by the first request, looks up one or more EASs closest to the location indicated by the location information carried by the first request from the locally registered EASs. The found EAS matches the application identity, EAS type, service feature of the application or service, and computing power requirement.

[0285] In the case where no EAS matching the information carried by the first request is found from the locally registered EASs, step 4 is performed.

[0286] Step 4: The EES sends a second request to the ECSP management system.

[0287] Here, the second request carries part or all of the information carried by the first request, for looking up the EAS. For example, the second request carries one or more of the following: application identity (such as AC ID), location information, EAS type, expected access duration to the EAS, service feature of the application or service, computing power requirement, computing precision, computing type, computing power task, duration of computing power task.

[0288] Step 5: The ECSP management system sends a seventh request to the EAS.

[0289] Here, the ECSP management system can send the seventh request to all EASs managed by the ECSP management system, and the seventh request can carry part or all of the information carried by the second request to inquire whether the EAS meets the requirement indicated by the seventh request.

[0290] The ECSP management system can also send a seventh request to the EAS satisfying the second condition, and the seventh request can carry part of the information carried by the second request to instruct the EAS satisfying the requirement indicated by the seventh request to initiate registration with the EES. The second condition is determined according to the information carried by the second request, and the second condition can include that the information of the EAS matches one or more of the application identifier, the EAS type, and the location information carried by the second request. That is, the EAS satisfying the second condition can provide services for the application corresponding to the application identifier, support the EAS type, and the distance between the EAS and the location indicated by the location information belongs to a set range. The seventh request carries one or more of the following: service characteristics of the application or service, computing power requirement, location information, EAS type, application identifier, expected access duration. The EAS is determined according to the EAS type and / or application identifier and / or location information and / or computing power requirement and / or expected access duration and / or service characteristics carried by the second request.

[0291] In an embodiment, the seventh request carries one or more of the following:

[0292] Service characteristics of the application or service; computing power requirement; computing power resource requirement; dynamic computing power resource requirement; temporary computing power resource requirement; single computing power resource requirement; specific computing power resource requirement; location information; EAS type; application identifier; expected access duration.

[0293] Step 6: The EAS sends a third request to the EES.

[0294] Here, the EAS can send the third request to the EES after receiving the seventh request. The third request can also be sent to the EES before receiving the seventh request.

[0295] Wherein, the EAS sends the third request to the EES in the case of deciding to initiate registration with the EES, and the third request at least carries the computing power information of the EAS, and the computing power information includes one or more of the following: computing type, computing accuracy, available computing power duration. The computing type includes one or more of the following: APU, CPU, DPU, GPU, NPU, and TPU. The computing accuracy includes one or more of the following: MIPS, DMIPS, OPS, and FLOPS.

[0296] For example, the EAS receiving the seventh request sends the third request to the EES, or the EAS satisfying the requirement indicated by the seventh request sends the third request to the EES, and the third request is used to request registration of the EAS. The third request at least carries the computing power information of the EAS, and can also carry one or more of the following information of the EAS: EAS profile, registration invalidation time, EAS identifier, FQDN or IP address, application service provider information or information of the ECSP, permission information, EAS type, location information, service capacity, DNAI, and load information.

[0297] Step 7: The EES receives the third request, and sends a second response to the EAS.

[0298] Here, the EES checks the application service provider information and / or the information and / or the identity of the ECSP carried by the third request, and in the case of correct information, determines that the EAS has the right to register on the EES; the EES registers the EAS, stores the information carried by the third request sent by the EAS, allocates a registration identity for the third node, and sends a second response to the EAS. The second response carries the registration identity, indicating that the EAS registration is successful.

[0299] It should be noted that after the EAS completes the registration on the EES, the registration information of the EAS can be updated to the EES and / or the deregistration can be initiated.

[0300] For example, if the registration information of the EAS registered successfully on the EES is changed, the EAS can send a fourth request to the EES, and the fourth request is used to request to update the information of the EAS. The fourth request at least carries the registration identity or the EAS identity of the EAS, and the computing power information updated by the EAS; the fourth request can also carry one or more of the following information of the EAS: EAS profile, registration invalidation time, updated FQDN or IP address, application service provider information or ECSP information, updated permission information, updated EAS type, updated location information, updated service capacity, updated DNAI, updated load information. In the case of receiving the fourth request, the EES checks the application service provider information and / or the information and / or the identity of the ECSP of the EAS, and in the case of correct information, allows to update the information of the EAS, and updates the information of the EAS stored locally based on the information carried by the fourth request; the EES sends a third response to the EAS; the third response can carry or not carry the registration identity, indicating that the EAS update is successful.

[0301] For another example, the EAS decides to initiate the deregistration to the EES, and sends a fifth request to the EES, and the fifth request is used to request to deregister the EAS; the third request can carry the computing power information of the EAS, and can also carry one or more of the following: registration identity of the EAS, EAS ID, application service provider information or ECSP information. In the case of receiving the fifth request, the EES checks the registration identity and / or the EAS identity of the EAS, and in the case of correct information, and / or, the existence of the registration identity and / or the EAS identity, determines that the EAS has the right to deregister on the EES; if the services on the EAS have all ended, the EES allows the EAS to deregister, and deletes the information of the EAS locally, i.e. deletes the registration information of the EAS saved locally. The EES sends a second response to the EAS, and the second response indicates that the EAS deregistration is successful.

[0302] Step 8: The EES locally looks up the EAS.

[0303] Here, in the case that the EES sends the second response to the EAS, the information of the successfully registered EAS stored by the EES locally is changed, at this time, the EES looks up the EAS based on the locally updated information. Specifically, the EES matches the information carried by the first request with the information of the locally registered EAS to look up the EAS matching the information carried by the first request.

[0304] If no EAS matching all the information carried by the first request is found, the EES can split the computing task according to the computing task and / or the duration of the computing task carried by the first request to obtain multiple first tasks; and perform secondary matching between the other information carried by the first request and the information of the locally registered EAS to locally look up a third node meeting the requirement of the first task. For example, the EES splits a computing task of 14:00-14:30 into three sub-tasks of 14:00-14:10, 14:10-14:20 and 14:20-14:30; and based on the first task, the application identifier, the EAS type, the service feature of the application or service and the computing requirement carried by the first request, looks up one or more EASs closest to the location information carried by the first request in the locally registered EASs.

[0305] If no third node meeting the requirement of the first task is found, whether the computing precision can be reduced is negotiated between the EEC and the AC; in the case that a new computing precision is obtained through the negotiation, based on the new computing precision and the other information carried by the first request, an EAS meeting the new computing precision and other requirements indicated by the first request is locally looked up. The other information carried by the first request can include but is not limited to one or more of the following: application identifier, EAS type, service feature, computing type, duration of the computing task, first task.

[0306] If no suitable EAS is found after the computing precision is reduced, the EES feeds back to the EEC an EAS closest to the DNAI provided by the AC.

[0307] If an EAS matching all the information carried by the first request is found, and / or an EAS meeting the requirement of the first task is found, the EES can feed back to the EEC the found EAS / EAS list / EAS time period list, and feed back the EAS FQDN or IP address.

[0308] Step 9: The EES sends the first response to the EEC.

[0309] Here, the first response sent by the EAS to the EEC indicates the found EAS in the case that the EAS is found, and the first response can carry the EAS identifier and / or FQDN and / or IP address of the EAS satisfying the first condition. The first condition includes one or more of the following: closest to the DNAI provided by the AC, the EAS indicated by the first request, matching part or all of the information carried by the first request, meeting the requirements of the first task.

[0310] The first response sent by the EAS to the EEC in the case that the EAS is not found characterizes that the EAS is not found.

[0311] Step 10: The EEC sends a fifth response to the AC.

[0312] Here, the fifth response can carry the information carried by the first response. For example, the fifth response carries the FQDN and / or IP address of the EAS, and the AC can subsequently access the EAS based on the FQDN and / or IP address of the EAS.

[0313] In the embodiments of the present application, the EEC carries the computing power requirement in the process of selecting the EAS, so as to select the most suitable EAS to provide the user with an extreme XR experience.

[0314] In order to implement the method on the side of the first node, the embodiments of the present application also provide a node searching device arranged on the first node, as shown in FIG. 9, which comprises:

[0315] The first receiving unit 901 is configured to receive the first request sent by the second node.

[0316] In an embodiment, the first request is used to search for the third node.

[0317] In an embodiment, the device further comprises:

[0318] The second sending unit is configured to send a first response to the second node, and the first response indicates the endpoint information of the third node or that the third node is not found.

[0319] In an embodiment, the first request carries one or more of the following:

[0320] Computing power requirement; computing power resource requirement; dynamic computing power resource requirement; temporary computing power resource requirement; single computing power resource requirement; specific computing power resource requirement; computing precision; computing power task; duration of the computing power task; identifier of the third node; application service KPI; computing power requirement of the XR application; application identifier; location information; type of the third node; identifier of the second node; predicted access duration to the third node; service duration; service identifier; service characteristics of the application or service; user identifier.

[0321] In an embodiment, the apparatus further comprises one or more of:

[0322] a first lookup unit configured to look up the third node based on the first information;

[0323] a second lookup unit configured to locally look up the third node indicated by the first request;

[0324] a third lookup unit configured to locally look up the third node satisfying the requirement of the first task, the first task being split from the computing power task and / or the duration of the computing power task carried by the first request;

[0325] a negotiation unit configured to negotiate with the second node to reduce the calculation precision;

[0326] a third sending unit configured to feed back the third node satisfying the first condition to the second node.

[0327] In an embodiment, the first information comprises one or more of:

[0328] a lookup filter of the third node; position information; service KPI of the fifth node; and computing requirement of the XR service.

[0329] In an embodiment, the first condition comprises one or more of:

[0330] closest to the second node; satisfying the requirement of the second node; the third node indicated by the first request; matching part or all information carried by the first request; and satisfying the requirement of the first task.

[0331] In an embodiment, the apparatus further comprises:

[0332] a fourth receiving unit configured to receive second information sent by a fourth node, the second information indicating the instantiable third node.

[0333] In an embodiment, the second information comprises the identity and / or available computing capacity and / or available computing power duration of the instantiable third node.

[0334] In an embodiment, the apparatus further comprises a fourth sending unit configured to send a second request to the fourth node.

[0335] In an embodiment, the second request is used to look up the third node.

[0336] In an embodiment, the second request carries one or more of:

[0337] Computing power requirement; computing power resource requirement; dynamic computing power resource requirement; temporary computing power resource requirement; single computing power resource requirement; specific computing power resource requirement; computing precision; computing power task; duration of computing power task; identity of third node; application service KPI; computing power requirement of XR application; application identity; location information; type of third node; identity of second node; predicted access duration to third node; service duration; service identity; service characteristics of application or service; user identity.

[0338] In an embodiment, the apparatus further comprises one or more of the following:

[0339] a fifth receiving unit, configured to receive a third request sent by the third node; the third request carrying at least computing power information, for requesting registration of the third node;

[0340] a storage unit, configured to store information carried by the third request;

[0341] a fifth sending unit, configured to send a second response to the third node; the second response representing success or failure of registration of the third node, and in the case where the second response represents success of registration of the third node, the second response carrying a registration identity.

[0342] In an embodiment, the third request further carries one or more of the following information of the third node:

[0343] EAS profile; registration invalidation time; identity of the third node; FQDN; IP address; application service provider information; information of ECSP; permission information; type of the third node; location information; available duration; service capacity; DNAI; load information.

[0344] In an embodiment, the apparatus further comprises one or more of the following:

[0345] a sixth receiving unit, configured to receive a fourth request sent by the third node; the fourth request carrying at least updated computing power information, for requesting update of information of the third node;

[0346] an updating unit, configured to update, based on information carried by the fourth request, information of the third node locally;

[0347] a sixth sending unit, configured to send a third response to the third node; the third response representing success or failure of update of information of the third node.

[0348] In an embodiment, the fourth request carries one or more of the following information of the third node:

[0349] EAS profile; registration invalidation time; registration identifier; identifier of the third node; updated permission information; updated location information; updated service capacity; updated DNAI; updated load information.

[0350] In an embodiment, the apparatus further comprises one or more of:

[0351] a seventh receiving unit, configured to receive a fifth request sent by the third node; the fifth request carrying at least computing power information, for requesting deregistration of the third node;

[0352] a deleting unit, configured to delete information of the third node locally;

[0353] a seventh sending unit, configured to send a fourth response to the third node; the fourth response representing success or failure of deregistration of the third node.

[0354] In an embodiment, the fifth request further carries one or more of:

[0355] registration identifier; identifier of the third node; application service provider information; information of the ECSP.

[0356] In an embodiment, the computing power information comprises one or more of:

[0357] computing type, the computing type comprising one or more of: APU, CPU, DPU, GPU, NPU, TPU;

[0358] computing precision, the computing precision comprising one or more of: MIPS, DMIPS, OPS, FLOPS;

[0359] available computing power duration.

[0360] In an embodiment, the first node comprises one or more of: EES, ECS, ECM.

[0361] In an embodiment, the second node comprises one or more of: EEC, terminal, UE, user.

[0362] In an embodiment, the third node comprises one or more of: EAS, AF, application service.

[0363] In an embodiment, the fourth node comprises one or more of: AF, ECSP management system.

[0364] In an embodiment, the fifth node comprises one or more of: AC, terminal, UE, user.

[0365] In actual application, the first receiving unit 901, the second sending unit, the third sending unit, the third receiving unit, the fourth sending unit, the fourth receiving unit, the fifth sending unit, the fifth receiving unit, the sixth sending unit, the sixth receiving unit, the seventh sending unit and the seventh receiving unit can be implemented by a processor in the node searching device in combination with a communication interface, and the first searching unit, the second searching unit, the third searching unit, the negotiating unit, the storage unit, the deleting unit and the updating unit can be implemented by the processor in the node searching device.

[0366] To implement the method on the second node side in the embodiments of the present application, the embodiments of the present application further provide a node searching device arranged on the second node, as shown in FIG. 10, which comprises:

[0367] The first sending unit 1001 is configured to send a first request to a first node.

[0368] In an embodiment, the device further comprises an eighth receiving unit configured to receive a sixth request sent by a fifth node.

[0369] In an embodiment, the sixth request carries one or more of the following: a profile of the fifth node; an identifier of the third node; a service KPI of the fifth node; a computing power requirement; a computing power resource requirement; a dynamic computing power resource requirement; a temporary computing power resource requirement; a single computing power resource requirement; a specific computing power resource requirement; a computing power requirement of an XR application.

[0370] In an embodiment, the first request is used to search for the third node.

[0371] In an embodiment, the device further comprises:

[0372] The ninth receiving unit is configured to receive a first response sent by the first node, and the first response indicates endpoint information of the third node or that the third node is not found.

[0373] In an embodiment, the first request carries one or more of the following:

[0374] a computing power requirement; a computing power resource requirement; a dynamic computing power resource requirement; a temporary computing power resource requirement; a single computing power resource requirement; a specific computing power resource requirement; a computing precision; a computing power task; a time length of the computing power task; an identifier of the third node; an application service KPI; a computing power requirement of an XR application; an application identifier; location information; a type of the third node; an identifier of the second node; an expected access time length to the third node; a service time length; a service identifier; a service feature of an application or a service; a user identifier.

[0375] In an embodiment, the first node comprises an EES and / or an ECM.

[0376] In an embodiment, the second node comprises one or more of: an EEC, a terminal, a UE, a user.

[0377] In an embodiment, the third node comprises one or more of: an EAS, an AF, an application service.

[0378] In an embodiment, the fifth node comprises one or more of: an AC, a terminal, a UE, a user.

[0379] In actual application, the first sending unit 1001, the eighth receiving unit and the ninth receiving unit can be realized by a processor in a node searching device in combination with a communication interface.

[0380] To implement the method on the fourth node side in the embodiments of the present application, the embodiments of the present application further provide a node searching device arranged on the fourth node, as shown in FIG. 11, which comprises:

[0381] A second receiving unit 1101 configured to receive a second request sent by a first node.

[0382] In an embodiment, the second request is used for searching a third node.

[0383] In an embodiment, the second request carries one or more of:

[0384] computing power demand, computing power resource demand, dynamic computing power resource demand, temporary computing power resource demand, single computing power resource demand, specific computing power resource demand, computing precision, computing power task, time length of a computing power task, identifier of the third node, application service KPI, computing power demand of an XR application, application identifier, location information, type of the third node, identifier of the second node, predicted access time length to the third node, service time length, service identifier, service characteristics of an application or service, user identifier.

[0385] In an embodiment, the device further comprises:

[0386] An eighth sending unit configured to send a seventh request to the third node and / or send second information to the first node, wherein the second information indicates the third node that can be instantiated.

[0387] In an embodiment, the second information comprises an identifier and / or available computing capacity and / or available computing power time length of the third node that can be instantiated.

[0388] In an embodiment, the seventh request is used for inquiring whether the third node meets the information carried in the seventh request, and / or is used for instructing the third node to initiate registration to the first node.

[0389] In an embodiment, the seventh request carries one or more of the following:

[0390] service characteristics of the application or service; computing power requirement; computing power resource requirement; dynamic computing power resource requirement; temporary computing power resource requirement; single computing power resource requirement; specific computing power resource requirement; location information; type of the third node; application identifier; expected access duration.

[0391] In an embodiment, the third node determines according to the type of the third node and / or the application identifier and / or the location information and / or the computing power requirement and / or the expected access duration and / or the service characteristics carried by the second request.

[0392] In an embodiment, the first node comprises one or more of the following: EES, ECS, ECM.

[0393] In an embodiment, the second node comprises one or more of the following: EEC, terminal, UE, user.

[0394] In an embodiment, the third node comprises one or more of the following: EAS, AF, application service.

[0395] In an embodiment, the fourth node comprises one or more of the following: AF, ECSP management system.

[0396] In actual application, the second receiving unit 1101 and the eighth sending unit can be realized by a processor in a node searching device.

[0397] In order to realize the method of the third node side in the embodiment of the present application, the embodiment of the present application further provides a node searching device arranged on the third node, as shown in FIG. 12, the device comprises:

[0398] A third receiving unit 1201 configured to receive a fifth request sent by a fourth node.

[0399] In an embodiment, the seventh request is used to inquire whether the fourth node meets the information carried by the fourth request, and / or is used to instruct the third node to initiate registration to the first node.

[0400] In an embodiment, the seventh request carries one or more of the following:

[0401] service characteristics of the application or service; computing power requirement; computing power resource requirement; dynamic computing power resource requirement; temporary computing power resource requirement; single computing power resource requirement; specific computing power resource requirement; location information; type of the third node; application identifier; expected access duration.

[0402] In an embodiment, the device further comprises one or more of the following:

[0403] The ninth sending unit is configured to send a third request to the first node; wherein the third request carries at least the computing power information, and is used to request registration of the third node;

[0404] The tenth receiving unit is configured to receive a second response sent by the first node; the second response indicates success or failure of the registration of the third node, and carries a registration identifier in a case where the second response indicates success of the registration of the third node.

[0405] In an embodiment, the third request further carries one or more of the following information of the third node:

[0406] EAS profile, registration invalidation time, identifier of the third node, FQDN, IP address, application service provider information, information of the ECSP, permission information, type of the third node, location information, available duration, service capacity, computing type, computing precision, DNAI, and load information.

[0407] In an embodiment, the apparatus further comprises one or more of the following:

[0408] The eleventh sending unit is configured to send a fourth request to the first node; the fourth request carries at least updated computing power information, and is used to request update of the information of the third node;

[0409] The tenth receiving unit is configured to receive a third response sent by the first node; the third response indicates success or failure of the update of the information of the third node.

[0410] In an embodiment, the fourth request carries one or more of the following information of the third node:

[0411] EAS profile, registration invalidation time, registration identifier, identifier of the third node, updated permission information, updated location information, updated service capacity, updated DNAI, and updated load information. In an embodiment, the apparatus further comprises one or more of the following:

[0412] The twelfth sending unit is configured to send a fifth request to the first node; the fifth request carries at least the computing power information, and is used to request deregistration of the third node;

[0413] The eleventh receiving unit is configured to receive a fourth response sent by the first node; the third response indicates success or failure of the deregistration of the third node.

[0414] In an embodiment, the fifth request further carries one or more of the following:

[0415] registration identifier, identifier of the third node, application service provider information, and information of the ECSP.

[0416] In an embodiment, the computing power information comprises one or more of the following:

[0417] a computing type, the computing type comprising one or more of the following: APU, CPU, DPU, GPU, NPU, TPU;

[0418] a computing precision, the computing precision comprising one or more of the following: MIPS, DMIPS, OPS, FLOPS;

[0419] a computing power duration.

[0420] In an embodiment, the first node comprises one or more of the following: EES, ECS, ECM.

[0421] In an embodiment, the third node comprises one or more of the following: EAS, AF, application service.

[0422] In an embodiment, the fourth node comprises one or more of the following: AF, ECSP management system.

[0423] In actual application, the third receiving unit 1201, the ninth sending unit, the tenth sending unit, the tenth receiving unit, the eleventh sending unit, the eleventh receiving unit and the twelfth sending unit can be realized by a processor in the node searching device in combination with a communication interface.

[0424] It should be noted that: the above embodiment provides the node searching device when searching for a node, only the above-mentioned division of each program module is exemplified, and in actual application, the above-mentioned processing can be completed by different program modules according to needs, that is, the internal structure of the device is divided into different program modules to complete all or part of the processing described above. In addition, the node searching device and the node searching method provided in the above embodiment belong to the same concept, and the specific implementation process is detailed in the method embodiment, which will not be repeated here.

[0425] Based on the hardware implementation of the above program modules, and in order to realize the method of the first node side in the embodiment of the application, the embodiment of the application further provides a first node, as shown in FIG. 13, the first node 1300 comprises:

[0426] a first communication interface 1301 capable of information interaction with other network nodes;

[0427] a first processor 1302 connected with the first communication interface 1301 to realize information interaction with other network nodes, for running a computer program, executing the method provided by one or more technical solutions of the above-mentioned first node side. And the computer program is stored on the first memory 1303.

[0428] Specifically, the first communication interface 1301 is configured to receive a first request sent by a second node.

[0429] In an embodiment, the first request is used to find a third node.

[0430] In an embodiment, the first communication interface 1301 is further configured to send a first response to the second node, the first response indicating endpoint information of the third node or that the third node is not found.

[0431] In an embodiment, the first request carries one or more of the following:

[0432] computing power requirement; computing power resource requirement; dynamic computing power resource requirement; temporary computing power resource requirement; single computing power resource requirement; specific computing power resource requirement; computing precision; computing power task; duration of the computing power task; identifier of the third node; application service KPI; computing power requirement of an XR application; application identifier; location information; type of the third node; identifier of the second node; estimated access duration to the third node; service duration; service identifier; service characteristics of the application or service; user identifier.

[0433] In an embodiment, the first processor 1302 is configured to perform one or more of the following:

[0434] finding the third node based on the first information; finding the third node indicated by the first request locally; finding the third node satisfying the requirement of a first task locally, the first task being split according to the computing power task and / or duration of the computing power task carried by the first request; negotiating to reduce the computing precision with the second node; and / or

[0435] The first communication interface 1301 is further configured to feed back to the second node the third node satisfying a first condition.

[0436] In an embodiment, the first information includes one or more of the following:

[0437] a search filter of the third node; location information; service KPI of a fifth node; computing requirement of an XR service.

[0438] In an embodiment, the first condition includes one or more of the following:

[0439] closest to the second node; satisfying the requirement of the second node; the third node indicated by the first request; matching part or all of the information carried by the first request; satisfying the requirement of the first task.

[0440] In an embodiment, the first communication interface 1301 is further configured to receive second information sent by a fourth node, the second information indicating an instantiable third node.

[0441] In an embodiment, the second information comprises an identity of the third node and / or available computing capability and / or available computing power duration.

[0442] In an embodiment, the first communication interface 1301 is further configured to send a second request to the fourth node.

[0443] In an embodiment, the second request is used to find the third node.

[0444] In an embodiment, the second request carries one or more of the following:

[0445] computing power requirement; computing power resource requirement; dynamic computing power resource requirement; temporary computing power resource requirement; single computing power resource requirement; specific computing power resource requirement; computing precision; computing power task; duration of the computing power task; identity of the third node; application service KPI; computing power requirement of the XR application; application identity; location information; type of the third node; identity of the second node; estimated access duration to the third node; service duration; service identity; service characteristics of the application or service; user identity.

[0446] In an embodiment, the first communication interface 1301 is further configured to receive a third request sent by the third node, and / or send a second response to the third node; the third request at least carries computing power information, and is used to request registration of the third node; the second response indicates that the registration of the third node is successful or failed, and in a case where the second response indicates that the registration of the third node is successful, the second response carries a registration identity.

[0447] The first processor 1302 is further configured to store the information carried by the third request.

[0448] In an embodiment, the third request further carries one or more of the following information of the third node:

[0449] EAS profile; registration invalidation time; identity of the third node; FQDN; IP address; application service provider information; information of the ECSP; permission information; type of the third node; location information; available duration; service capacity; DNAI; load information.

[0450] In an embodiment, the first communication interface 1301 is further configured to receive a fourth request sent by the third node, and / or send a third response to the third node; the fourth request at least carries updated computing power information, and is used to request update of the information of the third node; the third response indicates that the update of the information of the third node is successful or failed.

[0451] The first processor 1302 is further configured to update information of the third node locally based on information carried in the fourth request.

[0452] In an embodiment, the fourth request carries one or more of the following information of the third node:

[0453] EAS profile, registration invalidation time, registration identifier, identifier of the third node, updated authority information, updated location information, updated service capacity, updated DNAI, and updated load information.

[0454] In an embodiment, the first communication interface 1301 is further configured to receive a fifth request sent by the third node and / or send a fourth response to the third node, wherein the fifth request at least carries computing power information for requesting to deregister the third node, and the fourth response indicates success or failure of deregistration of the third node.

[0455] The first processor 1302 is further configured to delete information of the third node locally.

[0456] In an embodiment, the fifth request further carries one or more of the following:

[0457] registration identifier, identifier of the third node, application service provider information, and information of the ECSP.

[0458] In an embodiment, the computing power information includes one or more of the following:

[0459] computing type, wherein the computing type includes one or more of APU, CPU, DPU, GPU, NPU, and TPU;

[0460] computing precision, wherein the computing precision includes one or more of MIPS, DMIPS, OPS, and FLOPS;

[0461] available computing power duration.

[0462] In an embodiment, the first node includes one or more of the following: EES, ECS, and ECM.

[0463] In an embodiment, the second node includes one or more of the following: EEC, terminal, UE, and user.

[0464] In an embodiment, the third node includes one or more of the following: EAS, AF, and application service.

[0465] In an embodiment, the fourth node includes one or more of the following: AF and ECSP management system.

[0466] In an embodiment, the fifth node comprises one or more of: an AC, a terminal, a UE, a user.

[0467] It should be noted that the specific processing procedures of the first processor 1302 and the first communication interface 1301 can be understood with reference to the above method.

[0468] Of course, in actual application, various components in the first node 1300 are coupled together through the bus system 1304. It can be understood that the bus system 1304 is used to realize the connection and communication between the components. In addition to the data bus, the bus system 1304 also includes a power bus, a control bus and a status signal bus. However, for the purpose of clear illustration, various buses are marked as the bus system 1304 in FIG. 13.

[0469] The first memory 1303 in the embodiment of the present application is used to store various types of data to support the operation of the first node 1300. Examples of these data include: any computer program used for operation on the first node 1300.

[0470] The method disclosed in the above embodiment of the present application can be applied to the first processor 1302 or implemented by the first processor 1302. The first processor 1302 can be an integrated circuit chip with signal processing capability. In the implementation process, each step of the above method can be completed by integrated logic circuits of hardware or instructions in the form of software in the first processor 1302. The above first processor 1302 can be a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The first processor 1302 can implement or execute the disclosed methods, steps and logic block diagrams in the embodiments of the present application. The general-purpose processor can be a microprocessor or any conventional processor, etc. In combination with the steps of the method disclosed in the embodiments of the present application, the hardware decoding processor can be directly embodied to execute the above steps, or the combination of hardware and software modules in the decoding processor can be executed. The software module can be located in a storage medium, which is located in the first memory 1303, and the first processor 1302 reads the information in the first memory 1303 and combines the hardware to complete the steps of the above method.

[0471] In an example embodiment, the first node 1300 can be implemented by one or more Application Specific Integrated Circuits (ASICs), DSPs, Programmable Logic Devices (PLDs), Complex Programmable Logic Devices (CPLDs), Field-Programmable Gate Arrays (FPGAs), general-purpose processors, controllers, microcontrollers (MCUs), microprocessors (Microprocessors), or other electronic elements for executing the foregoing methods.

[0472] Based on the hardware implementation of the foregoing program modules, and in order to implement the method on the second node side according to the embodiments of the present application, the embodiments of the present application further provide a second node, as shown in FIG. 14, the second node 1400 comprises:

[0473] A second communication interface 1401 capable of information interaction with other network nodes;

[0474] A second processor 1402 connected with the second communication interface 1401 to realize information interaction with other network nodes, for running a computer program, and executing the method provided by one or more technical solutions on the second node side. The computer program is stored on the second memory 1403.

[0475] Specifically, the second communication interface 1401 is configured to send a first request to a first node.

[0476] In an embodiment, the second communication interface 1401 is further configured to receive a sixth request sent by a fifth node.

[0477] In an embodiment, the sixth request carries one or more of the following: a profile of the fifth node; an identifier of the third node; a service KPI of the fifth node; a computing power requirement; a computing power resource requirement; a dynamic computing power resource requirement; a temporary computing power resource requirement; a single computing power resource requirement; a specific computing power resource requirement; and a computing power requirement of an XR application.

[0478] In an embodiment, the first request is used to find a third node.

[0479] In an embodiment, the second communication interface 1401 is further configured to receive a first response sent by the first node, the first response indicating endpoint information of the third node or that the third node is not found.

[0480] In an embodiment, the first request carries one or more of the following:

[0481] computing power requirement; computing power resource requirement; dynamic computing power resource requirement; temporary computing power resource requirement; single computing power resource requirement; specific computing power resource requirement; computing precision; computing power task; duration of computing power task; identity of the third node; application service KPI; computing power requirement of XR application; application identity; location information; type of the third node; identity of the second node; predicted access duration to the third node; service duration; service identity; service feature of the application or service; user identity.

[0482] In an embodiment, the first node comprises an EES and / or an ECM.

[0483] In an embodiment, the second node comprises one or more of the following: an EEC, a terminal, a UE, a user.

[0484] In an embodiment, the third node comprises one or more of the following: an EAS, an AF, an application service.

[0485] In an embodiment, the fifth node comprises one or more of the following: an AC, a terminal, a UE, a user.

[0486] It should be noted that the specific processing procedures of the second processor 1402 and the second communication interface 1401 can be understood with reference to the above method.

[0487] Of course, in actual application, various components in the second node 1400 are coupled together through the bus system 1404. It can be understood that the bus system 1404 is used to realize the connection and communication between the components. The bus system 1404 includes not only a data bus, but also a power bus, a control bus and a status signal bus. However, for the purpose of clear illustration, various buses are marked as the bus system 1404 in FIG. 14.

[0488] The second memory 1403 in the embodiment of the application is used to store various types of data to support the operation of the second node 1400. Examples of these data include: any computer programs used to operate on the second node 1400.

[0489] The method disclosed by the embodiments of the present application can be applied to the second processor 1402 or implemented by the second processor 1402. The second processor 1402 can be an integrated circuit chip with signal processing capability. In the implementation process, each step of the above method can be completed by integrated logic circuits of hardware in the second processor 1402 or instructions in the form of software. The second processor 1402 described above can be a general processor, a DSP, or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The second processor 1402 can implement or execute the methods, steps and logic block diagrams disclosed in the embodiments of the present application. The general processor can be a microprocessor or any conventional processor, etc. In combination with the steps of the method disclosed in the embodiments of the present application, the hardware decoding processor can be directly embodied to execute the steps of the method, or the combination of hardware and software modules in the decoding processor can be executed. The software module can be located in the storage medium, which is located in the second memory 1403, and the second processor 1402 reads the information in the second memory 1403 to complete the steps of the above method in combination with the hardware thereof.

[0490] In the exemplary embodiments, the second node 1400 can be implemented by one or more ASICs, DSPs, PLDs, CPLDs, FPGAs, general-purpose processors, controllers, MCUs, microprocessors, or other electronic elements for executing the above method.

[0491] Based on the hardware implementation of the above program module, and in order to implement the method of the fourth node side in the embodiments of the present application, the embodiments of the present application further provide a fourth node, as shown in FIG. 15, the fourth node 1500 includes:

[0492] The third communication interface 1501 can interact with other network nodes.

[0493] The third processor 1502 is connected with the third communication interface 1501 to realize information interaction with other network nodes, and is used to run a computer program to execute the method provided by one or more technical solutions of the fourth node side. The computer program is stored on the third memory 1503.

[0494] Specifically, the third communication interface 1501 is configured to receive a second request sent by a first node.

[0495] In an embodiment, the second request is used to find a third node.

[0496] In an embodiment, the second request carries one or more of the following:

[0497] Computing power requirement; computing power resource requirement; dynamic computing power resource requirement; temporary computing power resource requirement; single computing power resource requirement; specific computing power resource requirement; computing precision; computing power task; duration of computing power task; identity of third node; application service KPI; computing power requirement of XR application; application identity; location information; type of third node; identity of second node; expected access duration to third node; service duration; service identity; service characteristic of application or service; user identity.

[0498] In an embodiment, the third communication interface 1501 is further configured to send a seventh request to the third node; and / or, send second information to the first node, the second information indicating the third node that can be instantiated.

[0499] In an embodiment, the second information comprises identity of the third node that can be instantiated and / or available computing capability and / or available computing power duration.

[0500] In an embodiment, the seventh request is used to inquire whether the third node meets the information carried by the seventh request, and / or, is used to instruct the third node to initiate registration to the first node.

[0501] In an embodiment, the seventh request carries one or more of the following:

[0502] Service characteristic of application or service; computing power requirement; computing power resource requirement; dynamic computing power resource requirement; temporary computing power resource requirement; single computing power resource requirement; specific computing power resource requirement; location information; type of third node; application identity; expected access duration.

[0503] In an embodiment, the third node is determined according to the type of the third node and / or the application identity and / or the location information and / or the computing power requirement and / or the expected access duration and / or the service characteristic carried by the second request.

[0504] In an embodiment, the first node comprises one or more of the following: EES, ECS, ECM.

[0505] In an embodiment, the second node comprises one or more of the following: EEC, terminal, UE, user.

[0506] In an embodiment, the third node comprises one or more of the following: EAS, AF, application service.

[0507] In an embodiment, the fourth node comprises one or more of the following: AF, ECSP management system.

[0508] It should be noted that the specific processing process of the third processor 1502 and the third communication interface 1501 can be understood with reference to the above method.

[0509] Of course, in actual applications, various components in the fourth node 1500 are coupled together through the bus system 1504. It can be understood that the bus system 1504 is used to realize the connection communication between the components. The bus system 1504 includes not only a data bus, but also a power supply bus, a control bus, and a status signal bus. However, for the purpose of clear illustration, various buses are marked as the bus system 1504 in FIG. 15.

[0510] The third memory 1503 in the embodiment of the present application is used to store various types of data to support the operation of the fourth node 1500. Examples of the data include any computer programs used for operation on the fourth node 1500.

[0511] The method disclosed in the above embodiment of the present application can be applied to or implemented by the third processor 1502. The third processor 1502 can be an integrated circuit chip with a signal processing capability. In the implementation process, each step of the above method can be completed by the integrated logic circuit of hardware or the instruction in the form of software in the third processor 1502. The third processor 1502 described above can be a general-purpose processor, a DSP, or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like. The third processor 1502 can implement or execute the disclosed methods, steps, and logic block diagrams in the embodiments of the present application. The general-purpose processor can be a microprocessor or any conventional processor, and the like. In combination with the steps of the method disclosed in the embodiments of the present application, the execution can be directly completed by a hardware decoding processor, or completed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium, which is located in the third memory 1503. The third processor 1502 reads the information in the third memory 1503, and combines the hardware to complete the steps of the foregoing method.

[0512] In the exemplary embodiments, the fourth node 1500 can be implemented by one or more ASICs, DSPs, PLDs, CPLDs, FPGAs, general-purpose processors, controllers, MCUs, microprocessors, or other electronic elements, for executing the foregoing method.

[0513] Based on the hardware implementation of the foregoing program module, and in order to implement the method on the third node side in the embodiments of the present application, the embodiments of the present application further provide a third node. As shown in FIG. 16, the third node 1600 includes:

[0514] The fourth communication interface 1601 is capable of performing information interaction with other network nodes;

[0515] The fourth processor 1602 is connected with the fourth communication interface 1601 to realize information interaction with other network nodes, and is used to run a computer program to execute the method provided by one or more technical solutions of the third node side described above. The computer program is stored on the fourth memory 1603.

[0516] Specifically, the fourth communication interface 1601 is configured to receive a fifth request sent by the fourth node.

[0517] In an embodiment, the seventh request is used to inquire whether the fourth node meets the information carried by the fourth request, and / or is used to instruct the third node to initiate registration to the first node.

[0518] In an embodiment, the seventh request carries one or more of the following:

[0519] service characteristics of the application or service; computing power demand; computing power resource demand; dynamic computing power resource demand; temporary computing power resource demand; single computing power resource demand; specific computing power resource demand; location information; type of the third node; application identifier; expected access duration.

[0520] In an embodiment, the fourth communication interface 1601 is further configured to include one or more of the following:

[0521] send a third request to the first node; wherein the third request carries at least computing power information, and is used to request registration of the third node;

[0522] receive a second response sent by the first node; the second response indicates that the registration of the third node is successful or failed, and in the case that the second response indicates that the registration of the third node is successful, the second response carries a registration identifier.

[0523] In an embodiment, the third request further carries one or more of the following information of the third node:

[0524] EAS profile; registration invalidation time; identifier of the third node; FQDN; IP address; application service provider information; information of the ECSP; permission information; type of the third node; location information; available duration; service capacity; computing type; computing precision; DNAI; load information.

[0525] In an embodiment, the fourth communication interface 1601 is further configured to perform one or more of the following:

[0526] send a fourth request to the first node; the fourth request carries at least updated computing power information, and is used to request update of information of the third node;

[0527] receive a third response sent by the first node; the third response represents success or failure of information updating of the third node.

[0528] In an embodiment, the fourth request carries one or more of the following information of the third node:

[0529] EAS profile; registration invalidation time; registration identifier; identifier of the third node; updated authority information; updated location information; updated service capacity; updated DNAI; updated load information.

[0530] In an embodiment, the fourth communication interface 1601 is further configured to perform one or more of the following:

[0531] send a fifth request to the first node; the fifth request carries at least computing power information, and is used to request deregistration of the third node;

[0532] receive a fourth response sent by the first node; the third response represents success or failure of deregistration of the third node.

[0533] In an embodiment, the fifth request further carries one or more of the following:

[0534] registration identifier; identifier of the third node; application service provider information; information of the ECSP.

[0535] In an embodiment, the computing power information includes one or more of the following:

[0536] computing type, the computing type including one or more of the following: APU, CPU, DPU, GPU, NPU, and TPU;

[0537] computing precision, the computing precision including one or more of the following: MIPS, DMIPS, OPS, and FLOPS;

[0538] available computing power duration.

[0539] In an embodiment, the first node includes one or more of the following: EES, ECS, and ECM.

[0540] In an embodiment, the third node includes one or more of the following: EAS, AF, and application service.

[0541] In an embodiment, the fourth node includes one or more of the following: AF and ECSP management system.

[0542] It should be noted that the specific processing process of the fourth processor 1602 and the fourth communication interface 1601 can be understood with reference to the above method.

[0543] Of course, in practice, the various components of the third node 1600 are coupled together by a bus system 1604. It is understood that more than one bus system can be present in the third node 1600. Further, the bus system 1604 can include one or more buses connected in series or in parallel. As is realizable, the bus system 1604 is used for communicating data, addresses and control signals between the various components of the third node 1600. The bus system 1604 includes a data bus, a control bus, and a state signal bus, although these three buses can be integrated into one bus. For clarity, the various buses are indicated separately in FIG. 16.

[0544] The fourth memory 1603 in the embodiments of the present application is used to store various types of data to support the operation of the third node 1600. Examples of the data include any computer programs for operating on the third node 1600.

[0545] The method disclosed in the embodiments of the present application can be applied to or implemented by the fourth processor 1602. The fourth processor 1602 can be an integrated circuit chip having the processing capability of signals. In the implementation process, the steps of the above method can be completed by the integrated logic circuit of hardware or the instructions in the form of software in the fourth processor 1602. The fourth processor 1602 can be a general-purpose processor, a DSP, or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc. The fourth processor 1602 can implement or execute the methods, steps and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor can be a microprocessor or any conventional processor, etc. In combination with the steps of the method disclosed in the embodiments of the present application, the execution can be directly completed by a hardware decoding processor or by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium, which is located in the fourth memory 1603, and the fourth processor 1602 reads the information in the fourth memory 1603 and combines the hardware to complete the steps of the foregoing method.

[0546] In the exemplary embodiments, the third node 1600 can be implemented by one or more ASICs, DSPs, PLDs, CPLDs, FPGAs, general-purpose processors, controllers, MCUs, microprocessors, or other electronic elements for executing the foregoing method.

[0547] It can be understood that the memory (the first memory 1303, the second memory 1403, the third memory 1503, and the fourth memory 1603) of the embodiments of the present application can be a volatile memory or a non-volatile memory, and can also include both volatile and non-volatile memories. The non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a ferromagnetic random access memory (FRAM), a flash memory, a magnetic surface memory, an optical disc, or a compact disc read-only memory (CD-ROM). The magnetic surface memory can be a disk memory or a tape memory. The volatile memory can be a random access memory (RAM) used as an external cache.By way of example and not limitation, many forms of RAM can be used, such as Static Random Access Memory (SRAM), Synchronous Static Random Access Memory (SSRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDR SDRAM), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), SyncLink Dynamic Random Access Memory (SLDRAM), Direct Rambus Random Access Memory (DRRAM). The memory described in embodiments of the present application is intended to include, but not be limited to, these and any other suitable types of memory.

[0548] In exemplary embodiments, the present embodiments also provide a storage medium, i.e., a computer storage medium, specifically a computer readable storage medium, such as including a first memory 1303 storing a computer program executable by the first processor 1302 of the first node 1300 to perform the steps of the aforementioned first node side method. For example, including a second memory 1403 storing a computer program executable by the second processor 1402 of the second node 1400 to perform the steps of the aforementioned second node side method. For example, including a third memory 1503 storing a computer program executable by the third processor 1502 of the fourth node 1500 to perform the steps of the aforementioned fourth node side method. For example, including a fourth memory 1603 storing a computer program executable by the fourth processor 1602 of the third node 1600 to perform the steps of the aforementioned third node side method.

[0549] The computer readable storage medium can be a memory such as a FRAM, a ROM, a PROM, an EPROM, an EEPROM, a Flash Memory, a magnetic surface memory, an optical disk, or a CD-ROM.

[0550] Exemplarily, the embodiments of the present application further provide a computer program product comprising a computer program executable by the first processor 1302 of the first node 1300 to complete the steps of the aforementioned first node side method. For example, the computer program is executable by the second processor 1402 of the second node 1400 to complete the steps of the aforementioned second node side method. For example, the computer program is executable by the third processor 1502 of the fourth node 1500 to complete the steps of the aforementioned fourth node side method. For example, the computer program is executable by the fourth processor 1602 of the third node 1600 to complete the steps of the aforementioned third node side method.

[0551] It should be noted that "first", "second", and the like are used to distinguish similar objects, and do not necessarily have to describe a specific order or sequence.

[0552] The term "and / or" herein is only a description of the association relationship of the associated objects, which means that there can be three relationships, for example, A and / or B, which can represent three cases of A alone, A and B together, and B alone. In addition, the term "one or more" herein means any combination of at least two of any one or more of a plurality, for example, including one or more of A, B, and C, which can represent any one or at least two or more elements selected from the set consisting of A, B, and C.

[0553] In addition, the technical solutions described in the embodiments of the present application can be arbitrarily combined without conflict.

[0554] The above is only a preferred embodiment of the present application, and is not intended to limit the protection scope of the present application.

Claims

A node searching method applied to a first node, the method comprising: receiving a first request sent by a second node. The method of claim 1, wherein, The first request is used to search for a third node. The method of claim 2, wherein, The method further comprises: sending a first response to the second node, the first response indicating endpoint information of the third node or that the third node is not found. The method of claim 1, wherein, The first request carries one or more of the following: computing power demand; computing power resource demand; dynamic computing power resource demand; temporary computing power resource demand; single computing power resource demand; specific computing power resource demand; computing precision; computing power task; duration of the computing power task; identification of the third node; application service key performance indicator (KPI); computing power demand of an extended reality (XR) application; application identification; location information; type of the third node; identification of the second node; estimated access duration to the third node; service duration; service identification; service characteristics of an application or service; user identification. The method according to any one of claims 1 to 4, wherein The method further comprises one or more of the following: searching for the third node based on first information; locally searching for the third node indicated by the first request; locally searching for the third node that meets the demand of a first task, the first task being split according to the computing power task and / or duration of the computing power task carried by the first request; negotiating with the second node to reduce the computing precision; feeding back to the second node the third node that meets a first condition. The method of claim 5, wherein, The first information comprises one or more of the following: search filter of the third node; location information; service KPI of a fifth node; computing demand of an XR service. The method of claim 5, wherein, The first condition comprises one or more of the following: closest to the second node; meeting the demand of the second node; the third node indicated by the first request; matching part or all of the information carried by the first request; meeting the demand of the first task. The method according to any one of claims 1 to 5, wherein The method further comprises: receiving second information sent by a fourth node, the second information indicating instantiable third nodes. The method of claim 8, wherein, The second information comprises identification and / or available computing capacity and / or available computing power duration of the instantiable third nodes. The method according to any one of claims 1 to 5, wherein The method further comprises: sending a second request to the fourth node. The method of claim 10, wherein, The second request is used to search for a third node. The method of claim 10, wherein, The second request carries one or more of the following: computing power demand; computing power resource demand; dynamic computing power resource demand; temporary computing power resource demand; single computing power resource demand; specific computing power resource demand; computing precision; computing power task; duration of the computing power task; identification of the third node; application service KPI; computing power demand of an XR application; application identification; location information; type of the third node; identification of the second node; estimated access duration to the third node; service duration; service identification; service characteristics of an application or service; user identification. The method of claim 1, wherein, The method further comprises one or more of the following: receiving a third request sent by a third node; The third request at least carries computing power information, and is used to request registration of the third node; storing the information carried by the third request; sending a second response to the third node; The second response represents successful or failed registration of the third node, and in the case that the second response represents successful registration of the third node, the second response carries a registration identification. The method of claim 13, wherein, The third request also carries one or more of the following information of the third node: EAS profile; Registration expiration time; identity of the third node; fully qualified domain name (FQDN); Internet Protocol (IP) address; application service provider information; information of an edge computing service provider (ECSP); Permission information; type of the third node; location information; available duration; service capacity; data network access identifier (DNAI); Load information. The method of claim 1, wherein, The method further includes one or more of the following: Receiving a fourth request sent by the third node; the fourth request at least carries updated computing power information, for requesting to update information of the third node; Updating, locally, information of the third node based on information carried by the fourth request; Sending a third response to the third node; the third response indicates success or failure of updating information of the third node. The method of claim 15, wherein, The fourth request carries one or more of the following information of the third node: EAS profile; Registration expiration time; Registration identity; identity of the third node; updated permission information; updated location information; updated service capacity; updated DNAI; updated load information. The method of claim 1, wherein, The method further includes one or more of the following: Receiving a fifth request sent by the third node; the fifth request at least carries computing power information, for requesting to deregister the third node; Deleting, locally, information of the third node; Sending a fourth response to the third node; the fourth response indicates success or failure of deregistering the third node. The method of claim 17, wherein, The fifth request further carries one or more of the following: Registration identity; identity of the third node; application service provider information; information of an ECSP. The method according to any one of claims 13 to 18, wherein The computing power information includes one or more of the following: Computing type, including one or more of the following: accelerated processing unit (APU), central processing unit (CPU), deep learning processing unit (DPU), graphics processing unit (GPU), neural processing unit (NPU), and tensor processing unit (TPU); Computing precision, including one or more of the following: millions of instructions per second (MIPS), millions of integer operation instructions per second (DMIPS), operations per second (OPS), and floating-point operations per second (FLOPS); Available computing power duration. The method according to any one of claims 1 to 4, 6 to 7, 9, 11 to 18, wherein The first node includes one or more of the following: edge enabler server (EES), edge configuration server (ECS), and edge configuration management (ECM). The method according to any one of claims 1 to 4, 6 to 7, 9, 11 to 18, wherein The second node includes one or more of the following: edge enabler client (EEC), terminal, user equipment (UE), and user. The method according to any one of claims 3 to 4, 6 to 7, 9, 11 to 18, wherein The third node includes one or more of the following: edge application server (EAS), application function (AF), and application service. The method of claim 8, wherein, The fourth node includes one or more of the following: AF and ECSP management system. The method according to claim 6 or 7, wherein The fifth node includes one or more of the following: Application client (AC), terminal, UE, and user. A node searching method applied to a second node, the method including: Sending a first request to a first node. The method of claim 25, wherein, The method further includes: Receiving a sixth request sent by a fifth node. The method of claim 26, wherein, The sixth request carries one or more of the following: a profile of the fifth node; an identity of the third node; a service KPI of the fifth node; a computing power requirement; a computing power resource requirement; a dynamic computing power resource requirement; a temporary computing power resource requirement; a single computing power resource requirement; a specific computing power resource requirement; a computing power requirement of an XR application. The method of claim 25, wherein, The first request is used to find the third node. The method of claim 25, wherein, The method further comprises: receiving a first response sent by the first node, the first response indicating endpoint information of the third node or that the third node is not found. The method of claim 25, wherein, The first request carries one or more of the following: a computing power requirement; a computing power resource requirement; a dynamic computing power resource requirement; a temporary computing power resource requirement; a single computing power resource requirement; a specific computing power resource requirement; a computing precision; a computing power task; a duration of the computing power task; an identity of the third node; an application service KPI; a computing power requirement of an XR application; an application identity; location information; a type of the third node; an identity of the second node; an expected access duration to the third node; a service duration; a service identity; a service characteristic of an application or service; a user identity. The method of any one of claims 25 to 30, wherein, The first node comprises an EES and / or an ECM. The method of any one of claims 25 to 30, wherein, The second node comprises one or more of the following: an EEC, a terminal, a UE, a user. The method of claim 28 or 29, wherein, The third node comprises one or more of the following: an EAS, an AF, an application service. The method of claim 26 or 27, wherein, The fifth node comprises one or more of the following: an AC, a terminal, a UE, a user. A node finding method applied to a fourth node, the method comprising: receiving a second request sent by a first node. The method of claim 35, wherein, The second request is used to find a third node. The method of claim 35, wherein, The second request carries one or more of the following: a computing power requirement; a computing power resource requirement; a dynamic computing power resource requirement; a temporary computing power resource requirement; a single computing power resource requirement; a specific computing power resource requirement; a computing precision; a computing power task; a duration of the computing power task; an identity of the third node; an application service KPI; a computing power requirement of an XR application; an application identity; location information; a type of the third node; an identity of the second node; an expected access duration to the third node; a service duration; a service identity; a service characteristic of an application or service; a user identity. The method of any one of claims 35 to 37, wherein The method further comprises: sending a seventh request to the third node; and / or sending second information to the first node, the second information indicating that the third node can be instantiated. The method of claim 38, wherein, The second information comprises an identity and / or available computing capacity and / or available computing power duration of the third node that can be instantiated. The method of claim 38, wherein, The seventh request is used to inquire whether the third node meets the information carried by the seventh request, and / or is used to instruct the third node to initiate registration with the first node. The method of claim 38, wherein, The seventh request carries one or more of the following: a service characteristic of an application or service; a computing power requirement; a computing power resource requirement; a dynamic computing power resource requirement; a temporary computing power resource requirement; a single computing power resource requirement; a specific computing power resource requirement; location information; a type of the third node; an application identity; an expected access duration. The method of claim 38, wherein, The third node is determined according to the type of the third node and / or the application identity and / or the location information and / or the computing power requirement and / or the expected access duration and / or the service characteristic carried by the second request. The method of any one of claims 35 to 37, 39 to 42, wherein, The first node comprises one or more of the following: an EES, an ECS, an ECM. The method of claim 37, wherein, The second node comprises one or more of the following: an EEC, a terminal, a UE, and a user. The method of any one of claims 36-37, 39-42, wherein, The third node comprises one or more of the following: an EAS, an AF, and an application service. The method of any one of claims 35 to 37, 39 to 42, wherein, The fourth node comprises one or more of the following: an AF and an ECSP management system. A node searching method applied to a third node, the method comprising: receiving a seventh request sent by a fourth node. The method of claim 47, wherein, The seventh request is used to inquire whether the fourth node meets the information carried by a fourth request, and / or is used to instruct the third node to initiate registration to a first node. The method of claim 47, wherein, The seventh request carries one or more of the following: service characteristics of an application or a service; computing power demand; computing power resource demand; dynamic computing power resource demand; temporary computing power resource demand; single computing power resource demand; specific computing power resource demand; location information; type of the third node; application identifier; predicted access duration. The method of claim 47, wherein, The method further comprises one or more of the following: sending a third request to the first node, wherein the third request at least carries computing power information and is used to request registration of the third node; receiving a second response sent by the first node; the second response indicates that the registration of the third node is successful or failed, and in the case that the second response indicates that the registration of the third node is successful, the second response carries a registration identifier. The method of claim 50, wherein, The third request further carries one or more of the following information of the third node: EAS profile; registration invalidation time; identifier of the third node; FQDN; IP address; application service provider information; information of an ECSP; permission information; type of the third node; location information; available duration; service capacity; computing type; computing precision; DNAI; load information. The method of claim 47, wherein, The method further comprises one or more of the following: sending a fourth request to the first node; the fourth request at least carries updated computing power information and is used to request update of information of the third node; receiving a third response sent by the first node; the third response indicates that the update of the information of the third node is successful or failed. The method of claim 52, wherein, The fourth request carries one or more of the following information of the third node: EAS profile; registration invalidation time; registration identifier; identifier of the third node; updated permission information; updated location information; updated service capacity; updated DNAI; updated load information. The method of claim 47, wherein, The method further comprises one or more of the following: sending a fifth request to the first node; the fifth request at least carries computing power information and is used to request deregistration of the third node; receiving a fourth response sent by the first node; the third response indicates that the deregistration of the third node is successful or failed. The method of claim 51, wherein, The fifth request further carries one or more of the following: registration identifier; identifier of the third node; application service provider information; information of an ECSP. The method of any one of claims 50 to 55, wherein, The computing power information comprises one or more of the following: computing type, the computing type comprising one or more of the following: APU, CPU, DPU, GPU, NPU, and TPU; computing precision, the computing precision comprising one or more of the following: MIPS, DMIPS, OPS, and FLOPS; available computing power duration. The method of any one of claims 48 to 55, wherein, The first node comprises one or more of the following: an EES, an ECS, and an ECM. The method of any one of claims 47 to 55, wherein, The third node comprises one or more of the following: an EAS, an AF, an application service. The method of any one of claims 47 to 55, wherein, The fourth node comprises one or more of the following: an AF, an ECSP management system. A node searching apparatus comprises: A first receiving unit configured to receive a first request sent by a second node. A node searching apparatus comprises: A first sending unit configured to send a first request to a first node. A node searching apparatus comprises: A second receiving unit configured to receive a second request sent by a first node. A node searching apparatus comprises: A third receiving unit configured to receive a seventh request sent by a fourth node. A first node comprising: A first processor and a first communication interface; wherein The first communication interface is configured to receive a first request sent by a second node. A second node comprising: A second processor and a second communication interface; wherein The second communication interface is configured to send a first request to a first node. A fourth node comprising: A third processor and a third communication interface; wherein The third communication interface is configured to receive a second request sent by a first node. A third node comprising: A fourth processor and a fourth communication interface; wherein The fourth communication interface is configured to receive a fifth request sent by a fourth node. A node device comprising a processor and a memory for storing a computer program capable of running on the processor, wherein, The processor is configured to execute the steps of the method of any one of claims 1 to 24, or the steps of the method of any one of claims 25 to 34, or the steps of the method of any one of claims 35 to 46, or the steps of the method of any one of claims 47 to 59 when the computer program is run. A storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the method of any one of claims 1 to 24, or the steps of the method of any one of claims 25 to 34, or the steps of the method of any one of claims 35 to 46, or the steps of the method of any one of claims 47 to 59. A computer program product comprising a computer program which, when executed by a processor, implements the steps of the method of any one of claims 1 to 59.

Images