Node searching method and device, node equipment, storage medium and computer program product

Abstract

The invention discloses a node searching method and device, node equipment, a storage medium and a computer program product, and the method comprises the steps that a first node receives a first request sent by a second node;

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of communication, and particularly relates to a node searching method and device, a node equipment, a storage medium and a computer program product. BACKGROUND

[0002] Immersive multimedia interactive services, such as extended reality (XR) services, require networks to be flexibly and elastically networked 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

[0003] 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.

[0004] The technical scheme of the embodiments of the present application is implemented as follows:

[0005] The embodiments of the present application provide a node searching method, characterized in that the method is applied to a first node and comprises the following steps.

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

[0007] In the above scheme, the first request is used to search for a third node.

[0008] In the above scheme, the method further comprises the following steps.

[0009] 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.

[0010] In the above scheme, the first request carries one or more of the following:

[0011] computing requirements;

[0012] computing resource requirements;

[0013] dynamic computing resource requirements;

[0014] temporary computing requirements;

[0015] Single computing resource requirement;

[0016] Specific computing resource requirement;

[0017] Computing accuracy;

[0018] Computing task;

[0019] Duration of computing task;

[0020] Identity of third node;

[0021] Application service Key Performance Indicator (KPI);

[0022] Computing requirement of XR application;

[0023] Application identity;

[0024] Location information;

[0025] Type of third node;

[0026] Identity of second node;

[0027] Expected access duration of third node;

[0028] Service duration;

[0029] Service identity;

[0030] Service feature of application or service;

[0031] User identity.

[0032] In the above scheme, the method further comprises one or more of the following:

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

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

[0035] Locally finding the third node meeting the requirement of the first task, the first task being obtained by splitting the computing task and / or the duration of the computing task carried by the first request;

[0036] Negotiating with the second node to reduce the computing accuracy;

[0037] Feeding back the third node meeting the first condition to the second node.

[0038] In the above scheme, the first information comprises one or more of the following:

[0039] a lookup filter of the third node;

[0040] location information;

[0041] a service KPI of the fifth node;

[0042] a computing requirement of the XR service.

[0043] In the foregoing solution, the first condition comprises one or more of the following:

[0044] closest to the second node;

[0045] satisfying a requirement of the second node;

[0046] the third node indicated by the first request;

[0047] matching part or all information carried by the first request;

[0048] satisfying a requirement of the first task.

[0049] In the foregoing solution, the method further comprises:

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

[0051] In the foregoing solution, the second information comprises an identifier and / or available computing capability and / or available computing power duration of the instantiable third node.

[0052] In the foregoing solution, the method further comprises:

[0053] sending a second request to the fourth node.

[0054] In the foregoing solution, the second request is used to find the third node.

[0055] In the foregoing solution, the second request carries one or more of the following:

[0056] computing power requirement;

[0057] computing power resource requirement;

[0058] dynamic computing power resource requirement;

[0059] temporary computing power resource requirement;

[0060] single computing power resource requirement;

[0061] specific computing power resource requirement;

[0062] computing precision;

[0063] computing power task;

[0064] a duration of the computing task;

[0065] an identity of the third node;

[0066] application service KPIs;

[0067] computing power requirements of the XR application;

[0068] an application identity;

[0069] location information;

[0070] a type of the third node;

[0071] an identity of the second node;

[0072] an estimated access duration to the third node;

[0073] a service duration;

[0074] a service identity;

[0075] service characteristics of the application or service;

[0076] a user identity.

[0077] In the above scheme, the method further comprises one or more of the following:

[0078] 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;

[0079] storing information carried by the third request;

[0080] sending a second response to the third node; the second response indicates whether the registration of the third node is successful or not successful; in a case where the second response indicates that the registration of the third node is successful, the second response carries a registration identity.

[0081] In the above scheme, the third request further carries one or more of the following information of the third node:

[0082] an EAS file (profile);

[0083] a registration invalidation time;

[0084] an identity of the third node;

[0085] a fully qualified domain name (FQDN);

[0086] an Internet protocol (IP) address;

[0087] application service provider information;

[0088] information of an edge computing service provider (ECSP, Edge Computing Service Provider);

[0089] permission information;

[0090] a type of the third node;

[0091] location information;

[0092] an available duration;

[0093] service capacity;

[0094] a data network access identifier (DNAI, Data Network Access Identifier);

[0095] load information.

[0096] In the foregoing solution, the method further includes one or more of the following:

[0097] receiving a fourth request sent by the third node; the fourth request at least carries updated computing power information, and is used to request to update information of the third node;

[0098] updating, based on information carried in the fourth request, the information of the third node locally;

[0099] sending a third response to the third node; the third response indicates that information updating of the third node is successful or fails.

[0100] In the foregoing solution, the fourth request carries one or more of the following information of the third node:

[0101] an EAS profile;

[0102] a registration invalidation time;

[0103] a registration identifier;

[0104] an identifier of the third node;

[0105] updated permission information;

[0106] updated location information;

[0107] updated service capacity;

[0108] an updated DNAI;

[0109] updated load information.

[0110] In the foregoing solution, the method further includes one or more of the following:

[0111] receiving a fifth request sent by the third node; the fifth request carrying at least computing power information, for requesting to deregister the third node;

[0112] locally deleting information of the third node;

[0113] sending a fourth response to the third node; the fourth response representing success or failure of deregistration of the third node.

[0114] In the above scheme, the fifth request further carries one or more of the following:

[0115] a registration identifier;

[0116] an identifier of the third node;

[0117] application service provider information;

[0118] information of an ECSP.

[0119] In the above scheme, the computing power information includes one or more of the following:

[0120] a computing type, the computing type including one or more of an accelerated processor (APU), a central processing unit (CPU), a deep learning processing unit (DPU), a graphics processing unit (GPU), a neural processing unit (NPU), and a tensor processing unit (TPU);

[0121] a computing precision, the computing precision including one or more of a million instructions per second (MIPS), a million data memory instructions per second (DMIPS), an operation per second (OPS), and a floating point operation per second (FLOPS);

[0122] a computing power available duration.

[0123] In the above scheme, the first node includes one or more of the following:

[0124] an edge enabler server (EES), an edge configuration server (ECS), and edge configuration management (ECM).

[0125] In the above scheme, the second node includes one or more of the following:

[0126] an edge enabler client (EEC), a terminal, a user equipment (UE), and a user.

[0127] In the above scheme, the third node includes one or more of the following:

[0128] Edge Application Server, EAS, Application Function, AF, Application Service.

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

[0130] In the foregoing solution, the fifth node comprises one or more of the following:

[0131] Application Client, AC, terminal, UE, user.

[0132] Embodiments of the present application also provide a node searching method, applied to a second node, the method comprising:

[0133] sending a first request to a first node.

[0134] In the foregoing solution, the method further comprises:

[0135] receiving a sixth request sent by a fifth node.

[0136] In the foregoing solution, the sixth request carries one or more of the following:

[0137] a profile of the fifth node;

[0138] an identifier of a third node;

[0139] a service KPI of the fifth node;

[0140] a computing power requirement;

[0141] a computing power resource requirement;

[0142] a dynamic computing power resource requirement;

[0143] a temporary computing power resource requirement;

[0144] a single computing power resource requirement;

[0145] a specific computing power resource requirement;

[0146] a computing power requirement of an XR application.

[0147] In the foregoing solution, the first request is used to search for the third node.

[0148] In the foregoing solution, the method further comprises:

[0149] 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.

[0150] In the above scheme, the first request carries one or more of the following:

[0151] Computing power requirements;

[0152] Computing resource requirements;

[0153] Dynamic computing resource requirements;

[0154] Temporary computing power resource requirements;

[0155] Single-use computing resource requirements;

[0156] Specific computing resource requirements;

[0157] Calculation accuracy;

[0158] Computing power tasks;

[0159] Duration of computing tasks;

[0160] The identifier of the third node;

[0161] Application service KPIs;

[0162] The computing power requirements of XR applications;

[0163] Application identifier;

[0164] Location information;

[0165] The type of the third node;

[0166] The identifier of the second node;

[0167] The estimated access duration to the third node;

[0168] Business duration;

[0169] Business identifier;

[0170] Service characteristics of the application or business;

[0171] User ID.

[0172] In the above scheme, the first node includes EES and / or ECM.

[0173] In the above scheme, the second node includes one or more of the following:

[0174] EEC, terminal, UE, user.

[0175] In the above scheme, the third node includes one or more of the following:

[0176] EAS, AF, and application services.

[0177] In the above scheme, the fifth node includes one or more of the following:

[0178] AC, terminal, UE, user. This application also provides a node lookup method applied to a fourth node, the method comprising:

[0179] Receive the second request sent by the first node.

[0180] In the above scheme, the second request is used to find the third node.

[0181] In the above scheme, the second request carries one or more of the following:

[0182] Computing power requirements;

[0183] Computing resource requirements;

[0184] Dynamic computing resource requirements;

[0185] Temporary computing power resource requirements;

[0186] Single-use computing resource requirements;

[0187] Specific computing resource requirements;

[0188] Calculation accuracy;

[0189] Computing power tasks;

[0190] Duration of computing tasks;

[0191] The identifier of the third node;

[0192] Application service KPIs;

[0193] The computing power requirements of XR applications;

[0194] Application identifier;

[0195] Location information;

[0196] The type of the third node;

[0197] The identifier of the second node;

[0198] The estimated access duration to the third node;

[0199] Business duration;

[0200] Business identifier;

[0201] Service characteristics of the application or business;

[0202] User ID.

[0203] The method in the above scheme further includes:

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

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

[0206] In the above scheme, the second information includes the identifier of the instantiable third node and / or the available computing power and / or the available computing power duration.

[0207] In the above scheme, 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.

[0208] In the above scheme, the seventh request carries one or more of the following:

[0209] Service characteristics of the application or business;

[0210] Computing power requirements;

[0211] Computing resource requirements;

[0212] Dynamic computing resource requirements;

[0213] Temporary computing power resource requirements;

[0214] Single-use computing resource requirements;

[0215] Specific computing resource requirements;

[0216] Location information;

[0217] The type of the third node;

[0218] Application identifier;

[0219] Estimated access duration. In the above scheme, the third node is determined based on the type and / or application identifier and / or location information and / or computing power requirements and / or estimated access duration and / or service characteristics carried in the second request.

[0220] In the above scheme, the first node includes one or more of the following:

[0221] EES, ECS, ECM.

[0222] In the above scheme, the second node includes one or more of the following:

[0223] EEC, terminal, UE, user.

[0224] In the above scheme, the third node includes one or more of the following:

[0225] EAS, AF, and application services.

[0226] In the above scheme, the fourth node includes one or more of the following:

[0227] AF and ECSP management systems.

[0228] This application embodiment also provides a node lookup method applied to a third node, the method comprising:

[0229] Receive the seventh request sent by the fourth node.

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

[0231] In the above scheme, the seventh request carries one or more of the following:

[0232] Service characteristics of the application or business;

[0233] Computing power requirements;

[0234] Computing resource requirements;

[0235] Dynamic computing resource requirements;

[0236] Temporary computing power resource requirements;

[0237] Single-use computing resource requirements;

[0238] Specific computing resource requirements;

[0239] Location information;

[0240] The type of the third node;

[0241] Application identifier;

[0242] Estimated visit duration.

[0243] The above scheme, the method further includes one or more of the following:

[0244] Send a third request to the first node; wherein the third request carries at least computing power information for requesting the registration of the third node;

[0245] The system receives a second response sent by the first node; the second response indicates whether the third node's registration was successful or failed, and if the second response indicates that the third node's registration was successful, the second response carries a registration identifier.

[0246] In the above scheme, the third request also carries one or more of the following information from the third node:

[0247] EAS profile;

[0248] Registration expiration time;

[0249] The identifier of the third node;

[0250] FQDN;

[0251] IP address;

[0252] Application service provider information;

[0253] ECSP information;

[0254] Permission information;

[0255] The type of the third node;

[0256] Location information;

[0257] Available duration;

[0258] Business capacity;

[0259] Calculation type;

[0260] Calculation accuracy;

[0261] DNAI;

[0262] Load information.

[0263] The above scheme, the method further includes one or more of the following:

[0264] Send a fourth request to the first node; the fourth request carries at least updated computing power information and is used to request updates to the information of the third node;

[0265] Receive a third response sent by the first node; the third response indicates whether the information update of the third node was successful or failed.

[0266] In the above scheme, the fourth request carries one or more of the following information from the third node:

[0267] EAS profile;

[0268] Registration expiration time;

[0269] Registration mark;

[0270] The identifier of the third node;

[0271] Updated permission information;

[0272] Updated location information;

[0273] Updated service capacity;

[0274] Updated DNAI;

[0275] Updated load information.

[0276] The above scheme, the method further includes one or more of the following:

[0277] Send a fifth request to the first node; the fifth request carries at least computing power information and is used to request to register with the third node;

[0278] Receive the fourth response sent by the first node; the third response indicates whether the third node's deregistration was successful or failed.

[0279] In the above scheme, the fifth request also carries one or more of the following:

[0280] Registration mark;

[0281] The identifier of the third node;

[0282] Application service provider information;

[0283] ECSP information.

[0284] In the above scheme, the computing power information includes one or more of the following:

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

[0286] The computational precision includes one or more of MIPS, DMIPS, OPS, and FLOPS.

[0287] Available computing power duration.

[0288] In the above scheme, the first node includes one or more of the following:

[0289] EES, ECS, ECM.

[0290] In the above scheme, the third node includes one or more of the following:

[0291] EAS, AF, and application services.

[0292] In the above scheme, the fourth node includes one or more of the following:

[0293] AF and ECSP management systems.

[0294] This application also provides a node lookup device, including:

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

[0296] This application also provides a node lookup device, including:

[0297] The first sending unit is used to send the first request to the first node.

[0298] This application also provides a node lookup device, including:

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

[0300] This application also provides a node lookup device, including:

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

[0302] This application embodiment also provides a first node, including: a first processor and a first communication interface;

[0303] in,

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

[0305] This application embodiment also provides a second node, including: a second processor and a second communication interface;

[0306] in,

[0307] The second communication interface is used to send a first request to the first node.

[0308] This application embodiment also provides a fourth node, including: a third processor and a third communication interface;

[0309] in,

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

[0311] This application embodiment also provides a third node, including: a fourth processor and a fourth communication interface;

[0312] in,

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

[0314] This application also provides a node device, characterized in that it includes a processor and a memory for storing computer programs capable of running on the processor.

[0315] When the processor runs the computer program, it executes the steps of any one of the methods described above, whether it is the first node side, the second node side, the third node side, or the fourth node side.

[0316] This application also provides a storage medium storing a computer program thereon, characterized in that the computer program, when executed by a processor, implements the steps of any of the above methods.

[0317] This application also provides a computer program product, including a computer program, characterized in that the computer program, when executed by a processor, implements the steps of the method described in any of the above-mentioned embodiments.

[0318] In the node search method, apparatus, node device, storage medium, and computer program product provided in this application embodiment, 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 this application embodiment, the second node can search for the third node through the first node, and can find a qualified third node to provide services for the relevant application or related business, thereby meeting the data processing needs of the relevant application or related business, ensuring the QoS of the relevant application or related business, and improving the user's QoE. Attached Figure Description

[0319] Figure 1 This is a schematic diagram of a node search method according to an embodiment of this application;

[0320] Figure 2 This is a schematic diagram of the third node registration process in an embodiment of this application;

[0321] Figure 3 This is a schematic diagram of the third node information update process in an embodiment of this application;

[0322] Figure 4 This is a schematic diagram of the registration process for the third node in an embodiment of this application;

[0323] Figure 5 This is a schematic diagram of a node search method according to an embodiment of this application;

[0324] Figure 6 This is a schematic diagram of a node search method according to an embodiment of this application;

[0325] Figure 7 This is a schematic diagram of a node search method according to an embodiment of this application;

[0326] Figure 8 This is a schematic diagram illustrating the interaction flow of the example node search method used in this application;

[0327] Figure 9 This is a schematic diagram of a node search device according to an embodiment of this application;

[0328] Figure 10This is a schematic diagram of a node search device according to an embodiment of this application;

[0329] Figure 11 This is a schematic diagram of a node search device according to an embodiment of this application;

[0330] Figure 12 This is a schematic diagram of a node search device according to an embodiment of this application;

[0331] Figure 13 This is a schematic diagram of the first node structure in an embodiment of this application;

[0332] Figure 14 This is a schematic diagram of the second node structure in an embodiment of this application;

[0333] Figure 15 This is a schematic diagram of the fourth node structure in an embodiment of this application;

[0334] Figure 16 This is a schematic diagram of the third node structure in an embodiment of this application. Detailed Implementation

[0335] Immersive multimedia interaction requires networks to be flexible and elastic in supporting large-scale user communication and computing, and places more stringent demands on network metrics. For example, in terms of network service interaction and collaboration, the metaverse service requires the network to shift from a capability-oriented to a service-oriented approach, enhancing its integration with applications and establishing multiple collaborative modes to better support the needs of strong interaction. In terms of enabling technologies, interactive technologies, artificial intelligence (AI), digital twin technologies, blockchain technologies, and non-fungible tokens (NFTs) are needed to transform the network into a service, supporting the creation and interaction of rich virtual world scenes.

[0336] For future communication networks (such as 5G-A / 6G networks), Extended Reality (XR) services have increasingly demanding and customized computing requirements. The ability to select suitable edge applications with matching computing capabilities is crucial to user experience. However, in related technologies, the equipment serving XR services cannot meet the data processing needs of XR services, resulting in poor QoS and impacting the user's Quality of Experience (QoE).

[0337] Based on this, in various embodiments of this 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; the third node receives the fifth request. It can be seen that in these embodiments, the second node can search for the third node through the first node, finding a suitable third node to provide services for the relevant application or service, thus meeting the data processing needs of the relevant application or service, ensuring the QoS of the relevant application or service, and improving the user's QoE.

[0338] This application provides a node lookup method applied to a first node. The first node may include one or more of the following: EES, ECS, ECM. That is, the first node may be EES and / or ECS and / or ECM. EES can be understood as an edge-enabled server or an edge-enabled service. Figure 1 As shown, the method includes:

[0339] Step 101: Receive the first request sent by the second node.

[0340] In one embodiment, the first request is used to find a third node. The first request can be understood as a search request or discovery request for the third node. For example, if the third node includes EAS, the first request may be an EAS discovery request message.

[0341] In order for the EEC to locate the EAS used to provide services through the EES, in one embodiment, the second node includes one or more of the following:

[0342] EEC, terminal, UE, user.

[0343] In one embodiment, the third node includes one or more of the following:

[0344] EAS, AF, and application services.

[0345] Here, the second node includes EEC and / or terminal and / or UE and / or UE. EEC is a client deployed on the terminal, and the terminal may have EEC and / or AC deployed there. The third node can be EAS and / or AF and / or application service. EAS can be understood as edge application server / edge application service provider. EES corresponds to EEC; EES can provide services to EEC, EES can enable EAS, and EAS can provide services to AC.

[0346] It should be noted that when the first node is EES, the second node is EEC, and the third node is EAS, EEC can use EES to find EAS and select a suitable EAS to provide services for the AC's related services, thereby improving the QoS of the AC's related services and enhancing the user's QoE. The AC's related services include XR services.

[0347] To facilitate the first node's search for a third node that matches the second node's needs, the first request carries information about the third node's requirements. Therefore, in one embodiment, the first request carries one or more of the following:

[0348] Computing power requirements;

[0349] Computing resource requirements;

[0350] Dynamic computing resource requirements;

[0351] Temporary computing power resource requirements;

[0352] Single-use computing resource requirements;

[0353] Specific computing resource requirements;

[0354] Calculation accuracy;

[0355] Computing power tasks;

[0356] Duration of computing tasks;

[0357] The identifier of the third node;

[0358] Application service KPIs;

[0359] The computing power requirements of XR applications;

[0360] Application identifier;

[0361] Computing power requirements;

[0362] Calculation accuracy;

[0363] Computing power tasks;

[0364] Duration of computing tasks;

[0365] Location information;

[0366] The type of the third node;

[0367] The identifier of the second node;

[0368] The estimated access duration to the third node;

[0369] Business duration;

[0370] Business identifier;

[0371] Service characteristics of the application or business;

[0372] User ID.

[0373] Here, the first request must at least carry computing power requirements, and may also carry one or more of the above information besides computing power requirements; computing power requirements can also be understood as computational needs. When the first request carries computing power requirements, it indicates a search for a third node that meets those requirements. Compared to the existing process, carrying computing power requirements in the first request allows the first node to prioritize searching for third nodes that meet those requirements, improving the matching degree between the computing power (computing capacity) of the found third node and the computing power requirements, thereby improving the QoS of the services or applications served by the third node or improving the user's QoE. When the first node is an EES, the second node is an EEC and / or AC, and the third node is an EAS, the EEC carries computing power requirements during the EAS selection process, thus selecting a suitable EAS and providing users with an ultimate XR experience.

[0374] Computing power requirements can be understood as the computing power requirements for third-party nodes. These can include the computing power requirements of applications and / or fifth-party nodes (e.g., AC) and / or XR applications. Third-party nodes can provide services to applications and / or fifth-party nodes and / or XR applications. Computing power requirements can also be described as computing resource requirements, dynamic computing resource requirements, temporary computing resource requirements, one-time computing resource requirements, or specific computing resource requirements. The English terms for computing power requirements 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, and specific resource / capability computing requirements. Computing power requirements must at least include the type of computation and / or computational precision, and may also include the computing task and / or the duration of the computing task and / or the business duration and / or the expected access duration to the third-party node. A computing task can be described as a computational task, and the duration of a computing task can be described as the duration of the computing task. The computation type includes one or more of the following: APU, CPU, DPU, GPU, NPU, TPU. The computation accuracy includes one or more of the following: MIPS, DMIPS, OPS, FLOPS.

[0375] The identifier of a third node can be described as a third node ID (Identifier / Identification). When the third node is an EAS, the identifier of the third node can be the EAS ID. If the first request carries the identifier of the third node, it indicates that the third node indicated by that identifier is being searched.

[0376] Application service KPIs can be understood as AC service KPIs or XR application service KPIs; no specific definition of KPI is provided here. XR applications can be understood as applications related to XR business. When the first request carries application service KPIs, it indicates the search for a third node that can satisfy the application service KPIs to provide the service.

[0377] An application identifier is an identifier for an application, including applications corresponding to AC (Application Client Identification) and / or EEC (Application Entity Identification) and / or XR applications. An application identifier can be described as a third-party application ID, AC ID, application ID, or application type. When the first request carries an application identifier, it indicates a search for a third-party node capable of providing services to the application corresponding to that application identifier.

[0378] A user identifier can be understood as the identifier of a user on the second node, or the identifier of the terminal deploying the second node, such as a UE ID, where UE stands for User Equipment. The user identifier can be used to determine whether a user has access rights to the third node, or for a user to determine whether the third node allows the corresponding user access.

[0379] Location information can be understood as the location information of the second node, or the location information of the terminal deploying the second node. Location information can be physical location information, such as latitude and longitude, or a Tracking Area Identity (TAI), or a Data Network Access Identifier (DNAI). Location information is used to determine the distance to the third node.

[0380] The type of the third node can be described as an EAS type, including Vehicle-to-Everything (V2X) and / or Unmanned Aerial Vehicle (UAV); when the first request carries the type of the third node, it indicates searching for a third node that matches the type of the third node. The identifier of the second node can be described as an EEC identifier or EEC ID, which is used by the first node to identify the second node. The expected access duration to the third node can be described as the expected access duration or the expected access duration to the EAS; when the first request carries the expected access duration to the third node, it indicates searching for a third node whose available computing power duration is greater than or equal to the expected access duration. The service identifier can be described as a service type, including the identifier of an XR service or the identifier of a service type, where XR service or service type includes XR games; when the first request carries the service identifier, it indicates searching for a third node that supports the corresponding service, or searching for a third node that can provide services for the corresponding service.

[0381] The service characteristics of an application or service include one or more of the following: service characteristics of a second node, service characteristics of the service corresponding to the second node, and service characteristics of an XR service, such as high-bandwidth XR gaming. The service characteristics of an application or service can be simply referred to as service characteristics. When the first request carries the service characteristics of the application or service, it indicates a search for a third node that satisfies or possesses those service characteristics.

[0382] To facilitate the second node's ability to ascertain whether the first node has found the third node, the first node, upon receiving the first request, can return a first response to the second node. Based on this, in one embodiment, after receiving the first request, the method further includes:

[0383] Send a first response to the second node, the first response indicating the endpoint information of the found third node or that no third node was found.

[0384] Here, after receiving the first request, the first node searches for a third node based on the first request and returns a 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 select one or more third nodes that meet the computing power requirements and / or service characteristics, based on the application ID, location information, third node type, computing power requirements, and service characteristics carried in the first request; the selected third nodes can provide services for the application corresponding to the application ID and match the type of the third node. As another example, the first node can determine, based on the application ID, location information, and third node type carried in the first request, the third nodes managed by the first node that match all three conditions, and then search for a third node among the determined third nodes that matches the computing power requirements and / or service characteristics carried in the first request.

[0385] If a third node is found, the first response indicates the found third node and may carry endpoint information of the found third node. The endpoint information of the third node is used to access the third node and may 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 some or all of the information carried in the first request; for example, the found third node meets the computing power requirements and / or service characteristics carried in the first request, and / or is closest to the location indicated by the location information carried in the first request. If no third node is found, for example, no third node matching some or all of the information carried in the first request is found; or, for example, no third node matching the computing power requirements and / or service characteristics carried in the first request is found, and / or, no third node closest to the location indicated by the location information carried in the first request is found.

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

[0387] Find the third node based on the first piece of information;

[0388] Locate the third node indicated by the first request locally;

[0389] Find a third node locally that meets the requirements of the first task. The first task is obtained by splitting the computing power task and / or the duration of the computing power task carried by the first request.

[0390] Negotiate with the second node to reduce computational precision;

[0391] The second node is then fed back a third node that satisfies the first condition. In one embodiment, to find a suitable third node, the first information includes one or more of the following:

[0392] The search filter for the third node;

[0393] Location information;

[0394] The service KPIs of the fifth node;

[0395] The computing requirements of XR services.

[0396] In one embodiment, the fifth node includes one or more of the following: AC, terminal, UE, and user. That is, the fifth node can be AC ​​and / or terminal and / or UE and / or user.

[0397] Here, upon receiving a first request and obtaining first information, the first node can search for a third node based on the first information. The first information may include one or more of the following: the third node's search filter, location information (e.g., UE location), the fifth node's service KPIs, and the computational requirements of the XR service. Specifically, the third node's search filter can be described as EAS discovery filters; the fifth node's service KPIs can be described as AC service KPIs, i.e., the fifth node can be an AC; and the XR service's computational requirements can be described as the XR service's computing power requirements.

[0398] Upon receiving a first request, the first node can search locally for the third node indicated by the first request. Once the third node is found, it reports the found third node to the second node. The third node indicated by the first request can be understood as a third node that matches some or all of the information carried in the first request. It should be noted that the first node's local database stores information about third nodes that have successfully registered with the first node. The first node supports third nodes registering and / or updating and / or deregistering. Furthermore, when the first node completes registration, updating, or deregistration of a third node, it can update the locally stored information about the successfully registered third node. After a new third node completes registration, the first node can again search locally for the third node indicated by the first request, and / or search locally for a third node that meets the requirements of the first task.

[0399] Upon receiving a first request, the first node can split the computing power task into multiple first tasks based on the computing power task and / or the duration of the computing power task carried in the first request; and search locally for a third node that meets the requirements of the first task. A first task can be understood as a subtask of the computing power task. Alternatively, if the first node cannot find the third node indicated by the first request locally (i.e., if no third node matching some or all of the information carried in the first request is found), the first node can also split the computing power task into multiple first tasks based on the computing power task and / or the duration of the computing power task carried in the first request; and search locally for a third node that meets the requirements of the first task. The requirements of the first task are determined based on one or more of the following: application identifier, computing power requirement, computing precision, location information, type of third node, identifier of the second node, expected access duration to the third node, business duration, business identifier, service characteristics of the application or business, and user identifier.

[0400] In practical applications, if a third node cannot find all the requirements indicated by the first request, 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, resulting in multiple first tasks. For example, based on the duration of the computing power task, the computing power task can be divided into N sub-time periods; for instance, a computing task from 14:00 to 14:30 can be split into three sub-tasks for the three time periods of 14:00 to 14:10, 14:10 to 14:20, and 14:20 to 14:30.

[0401] If the first request includes computational precision, the first node can negotiate with the second node to reduce the computational precision if it cannot find the third node indicated by the first request locally; alternatively, it can negotiate with the second node to reduce the computational precision if it cannot find a third node locally that meets the requirements of the first task. After reducing the computational precision, the first node can search for the third node locally again based on the updated computational precision and other information carried in the first request.

[0402] If the first node finds the third node, it can send a message to the second node indicating that the third node meets the first condition.

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

[0404] Closest to the second node;

[0405] Meet the requirements of the second node;

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

[0407] Matches some or all of the information carried in the first request;

[0408] To meet the requirements of the primary task.

[0409] Here, satisfying the requirements of the second node can be described as matching some or all of the information carried in the first request, or as satisfying the computing power requirements and / or service characteristics carried in the first request.

[0410] In one embodiment, to find a suitable third node, the method further includes:

[0411] Send a second request to the fourth node.

[0412] Here, the first node can send a second request to the fourth node before receiving the first request; alternatively, it can send a second request to the fourth node based on the first request if it cannot find the third node locally. The second request can carry some or all of the information carried in the first request, used to locate the third node. The second request can be understood as a search request.

[0413] In one embodiment, the fourth node includes the management system of AF and / or ECSP.

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

[0415] Computing power requirements;

[0416] Calculation accuracy;

[0417] Computing power tasks;

[0418] Duration of computing tasks;

[0419] The identifier of the third node;

[0420] Application service KPIs;

[0421] The computing power requirements of XR applications;

[0422] Application identifier;

[0423] Location information;

[0424] The type of the third node;

[0425] The identifier of the second node;

[0426] The estimated access duration to the third node;

[0427] Business duration;

[0428] Business identifier;

[0429] Service characteristics of the application or business;

[0430] User ID.

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

[0432] In one embodiment, to find a suitable third node, the method further includes:

[0433] Receive a second message sent by a fourth node, the second message indicating an instantiable third node.

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

[0435] In one embodiment, the second information includes the identifier of an instantiable third node and / or available computing power and / or available computing power duration.

[0436] Here, when the third node is EAS, the identifier of the third node can be described as EAS ID, the available computing power can include the available computing types, the available computing power can be understood as the available computing power capacity, and the available computing power duration can be understood as the available computing duration.

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

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

[0439] Store the information carried in the third request;

[0440] Send a second response to the third node; the second response indicates whether the third node's registration was successful or failed. If the second response indicates that the third node's registration was successful, the second response carries a registration identifier.

[0441] Here, the first node can receive the third request from the third node before receiving the first request, or it can receive the third request from the third node after sending the second request to the fourth node; the third request must carry at least the computing power information of the third node. The third node can initiate the registration process proactively, or it can initiate the registration process after receiving the second request from the fourth node. For example, the third node sends the third request to the first node after completing instantiation, and the first node receives the third request. Another example is that the first node sends the second request to the fourth node and receives the third request from the third node if it cannot find the third node locally.

[0442] Upon receiving a third request, the first node determines whether the third node has permission to register with the first node. If the third node has permission, the first node completes the registration of the third node and assigns a registration ID to the third node. If the third node does not have permission to register with the first node, the first node rejects the third request and does not allow the third node to register with the first node.

[0443] If a third node has the authority to register with a first node, the first node can also store the information carried by the third request locally. The information carried by the third request can be understood as the registration information of the third node.

[0444] If the first node receives a third request, it can return a second response to the third node.

[0445] To facilitate the first node's determination of whether the third node can meet the computing power requirements, the third piece of information, in one embodiment, includes one or more of the following:

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

[0447] The computational precision includes one or more of MIPS, DMIPS, OPS, and FLOPS.

[0448] Available computing power duration.

[0449] Among them, available computing power duration refers to the available computing power duration, the duration during which computing power services or computing services can be provided.

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

[0451] EAS profile;

[0452] Registration expiration time;

[0453] Third node identifier;

[0454] FQDN;

[0455] IP address;

[0456] Application service provider information;

[0457] ECSP information;

[0458] Permission information;

[0459] Third node type;

[0460] Location information;

[0461] Available duration;

[0462] Business capacity;

[0463] DNAI;

[0464] Load information.

[0465] Here, the third-node identifier can be called the EAS identifier. Permission information indicates the users or user groups allowed to access the third-node; that is, it indicates which users or user groups are permitted access. Permission information may include relevant information about the users or user groups allowed to access the third-node. The third-node type can be called the EAS type, which includes V2X and / or UAV. The location information carried in the third request is the location information of the third-node, which can be the physical location information of the third-node, such as latitude and longitude, or it can be TAI (Target Area Identity).

[0466] Figure 2 The registration process for the third node is shown, such as... Figure 2 As shown, the registration process for the third node is as follows:

[0467] 1. The third node determines whether registration with the first node is required.

[0468] 2. When a third node needs to register with the first node, the third node sends a third request to the first node. The third request is used to request the registration of the third node.

[0469] For example, once the third node has been instantiated and / or is in use, it sends a third request to the first node. This third request carries at least the third node's computing power information, and may also carry one or more of the following information: third node identifier, FQDN, IP address, application service provider information, ECSP information, permission information, third node type, location information, available duration, service capacity, DNAI, and load information. The computing power information includes computation type and / or computation precision and / or available computing power duration.

[0470] In practical applications, when the first node is EES and the third node is EAS, the third request carries the EAS's computing power information, EAS ID, EAS FQDN or IP address, application service provider information or ECSP information, permission information (which users or user groups are allowed to access), EAS type (e.g., V2X, UAV), location information, available duration or available computing power duration, service capacity, and DNAI.

[0471] 3. The first node receives a third request, determines whether the third node has the authority to register, or determines whether to allow the third node to register; if the third node has the authority to register or allows the third node to register, it stores the information carried in the third request and assigns a registration ID to the third node. For example, the first node verifies the third node's application service provider information and / or ECSP information and / or third node ID; if the information is correct, it indicates that the third node has the authority to register on the first node; the first node stores the information carried in the third request.

[0472] 4. The first node sends a second response to the third node. The second response indicates whether the third node's registration was successful or failed. If the second response indicates that the third node's registration was successful, the second response carries a registration identifier.

[0473] After completing registration, the third node can initiate a process to update its registration information before or after the second node initiates a process to search for or discover the third node. Based on this, in one embodiment, the method further includes one or more of the following:

[0474] Receive a fourth request sent by a third node; the fourth request carries at least updated computing power information and is used to request updates to the information of the third node;

[0475] Based on the information carried in the fourth request, update the information of the third node locally;

[0476] Send a third response to the third node; the third response indicates whether the information update of the third node was successful or failed.

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

[0478] EAS profile;

[0479] Registration expiration time;

[0480] Registration mark;

[0481] The identifier of the third node;

[0482] Updated permission information;

[0483] Updated location information;

[0484] Updated service capacity;

[0485] Updated DNAI;

[0486] Updated load information.

[0487] Here, upon receiving the fourth request, the first node determines whether the third node has permission to update the information on the first node. If the third node has permission, it updates its information locally based on the information carried in the fourth request; the information carried in the fourth request can be understood as the registration information that needs to be updated. If the third node does not have permission to update the information on the first node, for example, if the third node is not registered with the first node, the fourth request is rejected.

[0488] If the first node receives the fourth request, it can return a third response to the third node.

[0489] Figure 3 The information update process of the third node is shown; for example... Figure 3 As shown, the information update process for the third node is as follows:

[0490] 1. The third node determines whether it needs to update the registration information to the first node, or whether a registration update is required.

[0491] 2. When 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 is used to request the update of the third node's information.

[0492] For example, if the registration information of the third node changes, or if the validity period 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. It may also carry one or more of the following information of the third node: updated permission information, updated location information, updated availability duration, updated service capacity, updated DNAI, and updated load information.

[0493] In practical applications, when the first node is EES and the third node is EAS, the third request carries the registration identifier, EAS ID, updated computing power information of EAS, updated permission information (which users or user groups are allowed to access), updated location information, updated available duration or available computing power duration, updated service capacity, and updated DNAI.

[0494] 3. Upon receiving the fourth request, the first node determines whether the third node has the authority to update the registration information, or whether to allow the third node to update the registration information. If the third node has the authority to update the registration information or is allowed to do so, the first node updates the locally stored information of the third node based on the information carried in the fourth request. In other words, the first node updates the locally stored information of the third node (which can be called registration information) based on the information carried in the fourth request. For example, the first node verifies the third node's application service provider information and / or ECSP information and / or third node identifier and / or registration identifier. If the information is correct, it indicates that the third node has the authority to update the registration information or is allowed to update the third node's information, and updates the locally stored information of the third node based on the information carried in the fourth request.

[0495] 4. The first node sends a third response to the third node, which indicates whether the third node's update was successful or failed.

[0496] After the third node completes its registration on the first node, it can initiate a registration process with the first node.

[0497] Based on this, in one embodiment, the method further includes one or more of the following:

[0498] Receive a fifth request sent by a third node; the fifth request carries at least computing power information and is used to request to register with the third node;

[0499] Delete the information of the third node locally;

[0500] Send a fourth response to the third node; the fourth response indicates whether the third node's deregistration was successful or failed.

[0501] Here, upon receiving the fifth request, the first node determines whether the third node has permission to deregister on the first node. If the third node has permission to register on the first node, the first node completes the deregistration of the third node. If the third node does not have permission to register on the first node, for example, if the third node has not registered on the first node, and / or the verification of the information carried in the fifth request fails, the fifth request is rejected.

[0502] If a third node has permission to register with a first node, the first node can also delete the third node's information stored locally, that is, delete the third node's registration information stored locally.

[0503] Upon receiving the fifth request, the first node can return a third response to the third node.

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

[0505] Registration mark;

[0506] The identifier of the third node;

[0507] Application service provider information;

[0508] ECSP information.

[0509] Figure 4 The deregistration process for the third node is shown; for example... Figure 4 As shown, the registration process for the third node is as follows:

[0510] 1. The third node determines whether it needs to register with the first node (de-registration).

[0511] 2. When a third node needs to register with a first node, the third node sends a fifth request to the first node. The fifth request is used to request the third node to register.

[0512] For example, if the service of the third node fails, the third node decides to register with the first node and sends a fifth request to the first node. The fifth request carries at least the third node's registration identifier and / or third node identifier, and may also carry the third node's computing power information.

[0513] In practical applications, when the first node is EES and the third node is EAS, the third request carries the EAS registration identifier and / or EAS ID.

[0514] 3. Upon receiving the fifth request, the first node determines whether the third node has permission to register, or whether to allow the third node to register. If the third node has permission to register or is allowed to register, the first node deletes the third node's information, i.e., deletes the third node's information stored locally, to save storage resources for the first node. For example, the first node verifies the third node's registration identifier and / or third node identifier. If the information is correct, the first node determines that the third node has permission to register on the first node. If all services on the third node have ended, the first node allows the third node to register and deletes the third node's information locally, i.e., deletes the locally stored registration information of the third node.

[0515] 4. The first node sends a fourth response to the third node, and the second response indicates whether the third node's registration was successful or failed.

[0516] Correspondingly, embodiments of this application also provide a node lookup 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 an EEC and / or a terminal and / or a UE and / or a user. Figure 5 As shown, the method includes:

[0517] Step 501: Send the first request to the first node.

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

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

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

[0521] Computing power requirements;

[0522] Computing resource requirements;

[0523] Dynamic computing resource requirements;

[0524] Temporary computing power resource requirements;

[0525] Single-use computing resource requirements;

[0526] Specific computing resource requirements;

[0527] Calculation accuracy;

[0528] Computing power tasks;

[0529] Duration of computing tasks;

[0530] The identifier of the third node;

[0531] Application service KPIs;

[0532] The computing power requirements of XR applications;

[0533] Application identifier;

[0534] Location information;

[0535] The type of the third node;

[0536] The identifier of the second node;

[0537] The estimated access duration to the third node;

[0538] Business duration;

[0539] Business identifier;

[0540] Service characteristics of the application or business;

[0541] User ID.

[0542] The third node includes one or more of the following: EAS, AF, and application services. The second node includes one or more of the following: EEC, terminal, UE, and user.

[0543] The first request can be sent based on the sixth request. Therefore, in one embodiment, before sending the first request to the first node, the method further includes:

[0544] Receive the sixth request sent by the fifth node.

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

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

[0547] The profile of the fifth node;

[0548] The identifier of the third node;

[0549] The service KPIs of the fifth node;

[0550] Computing power requirements;

[0551] Computing resource requirements;

[0552] Dynamic computing resource requirements;

[0553] Temporary computing power resource requirements;

[0554] Single-use computing resource requirements;

[0555] Specific computing resource requirements;

[0556] The computing power requirements of XR applications.

[0557] Here, the second node receives the sixth request sent by the fifth node and sends a 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 the AC profile.

[0558] With the first node being EES and the second node being EEC, EEC can receive the sixth request sent by AC. The sixth request carries the AC ID and service identifier (also known as service type, including XR games), and sends the first request to EES based on the sixth request. The sixth request is used to request access to EAS.

[0559] To facilitate the first node in knowing whether it has found the third node, in one embodiment, after receiving the first request, the method further includes:

[0560] Receive a first response sent by the first node, the first response indicating the endpoint information of the third node or that the third node was not found.

[0561] Here, with the second node being the EEC, the EEC receives the first response from the EES and sends an application access response to the AC. The second response may carry the EAS's FQDN and / or IP address, allowing the AC to subsequently access the EAS based on its FQDN and / or IP address.

[0562] Correspondingly, embodiments of this application also provide a node lookup 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. Figure 6 As shown, the method includes:

[0563] Step 601: Receive the second request sent by the first node.

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

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

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

[0567] Computing power requirements;

[0568] Computing resource requirements;

[0569] Dynamic computing resource requirements;

[0570] Temporary computing power resource requirements;

[0571] Single-use computing resource requirements;

[0572] Specific computing resource requirements;

[0573] Calculation accuracy;

[0574] Computing power tasks;

[0575] Duration of computing tasks;

[0576] The identifier of the third node;

[0577] Application service KPIs;

[0578] The computing power requirements of XR applications;

[0579] Application identifier;

[0580] Location information;

[0581] The type of the third node;

[0582] The identifier of the second node;

[0583] The estimated access duration to the third node;

[0584] Business duration;

[0585] Business identifier;

[0586] Service characteristics of the application or business;

[0587] User ID.

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

[0589] 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:

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

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

[0592] 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.

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

[0594] Service characteristics of the application or business;

[0595] Computing power requirements;

[0596] Computing resource requirements;

[0597] Dynamic computing resource requirements;

[0598] Temporary computing power resource requirements;

[0599] Single-use computing resource requirements;

[0600] Specific computing resource requirements;

[0601] Location information;

[0602] The type of the third node;

[0603] Application identifier;

[0604] Estimated visit duration.

[0605] 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.

[0606] Here, if the fourth node sends a 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 with the first node; if the fourth node sends a seventh request to the third node after receiving the second request, the seventh request can be used to query the third node whether the information carried in the seventh request is satisfied, and / or to instruct the third node to initiate registration with the first node. For example, the seventh request can be used to instruct the third node to initiate registration with the first node if the information carried in the seventh request is satisfied.

[0607] It should be noted that the fourth node can send a seventh request to all third nodes it manages. Alternatively, the fourth node can identify a third node among its managed nodes that matches the application identifier, location information, and type carried in the second request, and send a seventh request to that identified third node. The seventh request inquires whether the third node satisfies the information carried in the seventh request, or whether the third node matches the information carried in the seventh request. The seventh request must at least carry the computing power requirement and / or computing precision and / or computing task and / or duration of the computing task and / or service characteristics of the application or business.

[0608] In other words, the fourth node can send the seventh request to all the third nodes it manages, or it can send the seventh request to a subset of the third nodes. For example, a subset of the third nodes could be those that match the application identifier, location information, and type of the third node carried in the second request. The seventh request is used to instruct the third nodes to initiate registration with the first node if the requirements indicated by the seventh request are met.

[0609] In practical applications, when the third node is an EAS and the fourth node is an ECSP management system, the ECSP management system identifies all EASs under its jurisdiction that match the application identifier, EAS type, and location information carried in the second request and sends a seventh request to inquire whether the service characteristics and / or computing power requirements and / or computing precision and / or computing power tasks and / or computing power task duration carried in the second request can be met. The ECSP management system then instructs the EAS to initiate registration with the first node if the requirements indicated in the second request are met.

[0610] EAS fulfilling the requirements of the second request refers to the duration for EAS to fulfill the service characteristics and / or computing power requirements and / or computing accuracy and / or computing power tasks carried in the second request.

[0611] To save on signaling overhead, the fourth node can send a seventh request to a third node that meets the conditions. Based on this, in one embodiment, the third node is determined according to the third node type and / or application identifier and / or location information and / or computing power requirements and / or expected access duration and / or service characteristics carried in the second request.

[0612] In one embodiment, the first node includes one or more of the following:

[0613] EES, ECS, ECM.

[0614] In one embodiment, the second node includes one or more of the following:

[0615] EEC, terminal, UE, user.

[0616] In one embodiment, the third node includes one or more of the following:

[0617] EAS, AF, and application services.

[0618] In one embodiment, the fourth node includes one or more of the following:

[0619] AF and ECSP management systems.

[0620] Correspondingly, embodiments of this application also provide a node lookup method applied to a third node, wherein the third node includes one or more of the following: EAS, AF, and application services; that is, the third node package can be EAS and / or AF and / or application services. Figure 7 As shown, the method includes:

[0621] Step 701: Receive the seventh request sent by the fourth node.

[0622] Here, the fourth node includes the AF and / or ECSP management system.

[0623] In one embodiment, the seventh request is used to inquire whether the fourth node satisfies the information carried in the seventh request, and / or to instruct the third node to initiate registration with the first node. The third node includes one or more of the following: EAS, AF, and application services. The first node includes one or more of the following: EES, ECS, and ECM.

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

[0625] Service characteristics of the application or business;

[0626] Computing power requirements;

[0627] Computing resource requirements;

[0628] Dynamic computing resource requirements;

[0629] Temporary computing power resource requirements;

[0630] Single-use computing resource requirements;

[0631] Specific computing resource requirements;

[0632] Location information;

[0633] The type of the third node;

[0634] Application identifier;

[0635] Estimated visit duration.

[0636] To facilitate the first node's search for the third node, the third node can initiate a registration with the first node. Based on this, in one embodiment, the method further includes one or more of the following:

[0637] Send a third request to the first node; wherein the third request carries at least computing power information for requesting the registration of the third node;

[0638] The system receives a second response sent by the first node; the second response indicates whether the third node's registration was successful or failed, and if the second response indicates that the third node's registration was successful, the second response carries a registration identifier.

[0639] Here, the third node can send a third request to the first node before receiving the seventh request, in order to proactively initiate registration with the first node. For example, the third node can send a third request to the first node after it has been instantiated and / or started being used; it can also send a third request to the first node after receiving the seventh request from the fourth node. The first node includes EES.

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

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

[0642] The computational precision includes one or more of MIPS, DMIPS, OPS, and FLOPS.

[0643] Available computing power duration.

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

[0645] EAS profile;

[0646] Registration expiration time;

[0647] The identifier of the third node;

[0648] FQDN;

[0649] IP address;

[0650] Application service provider information;

[0651] ECSP information;

[0652] Permission information;

[0653] The type of the third node;

[0654] Location information;

[0655] Available duration;

[0656] Business capacity;

[0657] Calculation type;

[0658] Calculation accuracy;

[0659] DNAI;

[0660] Load information.

[0661] The third node includes EAS.

[0662] After a third node successfully registers with a first node, it can also update its registration information with the first node.

[0663] Based on this, in one embodiment, the method further includes one or more of the following:

[0664] Send a fourth request to the first node; the fourth request carries at least updated computing power information and is used to request updates to the information of the third node;

[0665] Receive a third response sent by the first node; the third response indicates whether the information update of the third node was successful or failed.

[0666] Here, the third node can send a fourth request to the first node when its registration information changes or when its validity period is about to expire.

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

[0668] EAS profile;

[0669] Registration expiration time;

[0670] Registration mark;

[0671] The identifier of the third node;

[0672] Updated permission information;

[0673] Updated location information;

[0674] Updated service capacity;

[0675] Updated DNAI;

[0676] Updated load information.

[0677] To conserve storage resources of the first node, when the third node fails, it can proactively initiate a deregistration process with the first node. Based on this, in one embodiment, the method further includes one or more of the following:

[0678] Send a fifth request to the first node; the fifth request carries at least computing power information and is used to request to register with the third node;

[0679] Receive the fourth response sent by the first node; the third response indicates whether the third node's deregistration was successful or failed.

[0680] Here, the third node can send a fifth request to the first node if the third node's service fails, and / or if the third node fails.

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

[0682] Registration mark;

[0683] The identifier of the third node;

[0684] Application service provider information;

[0685] ECSP information.

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

[0687] The following section provides a more detailed description of this application with reference to application examples.

[0688] The first node is EES, the second node is EEC, the third node is EAS, the fourth node is the ECSP management system, and the fifth node is AC, such as Figure 8 As shown, the node lookup method includes the following steps:

[0689] Step 0: EAS Registration.

[0690] Here, the EAS managed by the ECSP management system initiates registration with the EES. Specifically, the ECSP management system can instruct the EAS to initiate registration with the EES, or the ECSP management system can send a third request to the EAS, which instructs a third node to initiate registration with the first node; the EAS then initiates registration with the EES.

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

[0692] EES receives a third request, verifies the application service provider information and / or ECSP information and / or EAS identifier of EAS, and if the verification is correct, determines that EAS has the right to register on EES; EES allows EAS to register, and stores the information carried in the third request locally, that is, EES stores the information / registration information of EAS that has successfully registered locally; EES assigns a registration identifier to EAS and returns a second response to EAS to notify EAS of successful registration; the second response may carry the registration identifier.

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

[0694] Here, the sixth request carries one or more of the following: AC profile, EAS ID, AC service KPI, AC computing power requirements, XR application computing power requirements, AC ID, and business identifier (also known as business type, including XR games); the sixth request is used to request access to EAS.

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

[0696] Here, the first request is used to find the third node.

[0697] The first request carries one or more of the following:

[0698] Application identifier (e.g., AC ID);

[0699] Computing power requirements;

[0700] Computing resource requirements;

[0701] Dynamic computing resource requirements;

[0702] Temporary computing power resource requirements;

[0703] Single-use computing resource requirements;

[0704] Specific computing resource requirements;

[0705] Calculation accuracy;

[0706] Computing power tasks;

[0707] Duration of computing tasks;

[0708] EAS ID;

[0709] Application service KPIs;

[0710] The computing power requirements of XR applications;

[0711] Location information;

[0712] EAS type;

[0713] EEC logo;

[0714] Estimated duration of access to EAS;

[0715] Business duration;

[0716] Business identifier (or business type, including XR games);

[0717] Service characteristics of the application or business;

[0718] User ID.

[0719] Here, the user identifier can be the identifier of the terminal deploying the AC, such as the UE ID; the location information can be the location information of the terminal deploying the AC. Computing power requirements can include one or more of the following: computing type (APU, CPU, DPU, GPU, NPU, TPU), computing precision (MIPS, DMIPS, OPS, FLOPS), and the duration of the computing task. Services include XR services, and the service characteristics of the application or service include high bandwidth for XR games.

[0720] Step 3: EES receives the first request and searches for EAS locally.

[0721] Here, the EES searches for an EAS locally based on the first request. Specifically, the EES matches the information carried in the first request with the information of locally registered EASs to find an EAS that matches the information carried in the first request. If multiple EASs are found, one or more EASs closest to the location indicated by the location information carried in the first request can be selected from among the found EASs. For example, based on the application identifier, EAS type, service characteristics of the application or service, and computing power requirements carried in the first request, the EES searches for one or more EASs among the locally registered EASs that are closest to the location indicated by the location information carried in the first request. The found EAS matches the application identifier, EAS type, service characteristics of the application or service, and computing power requirements.

[0722] If no EAS matching the information carried in the first request is found among the locally registered EASs, proceed to step 4.

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

[0724] Here, the second request carries some or all of the information carried in the first request for locating the EAS. For example, the second request carries one or more of the following: application identifier (e.g., AC ID), location information, EAS type, expected access duration to the EAS, service characteristics of the application or business, computing power requirements, computing precision, computing type, computing power task, and duration of the computing power task.

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

[0726] Here, the ECSP management system can send a seventh request to all EAS managed by the ECSP management system. The seventh request can carry some or all of the information carried in the second request to inquire whether the EAS meets the requirements indicated by the seventh request.

[0727] The ECSP management system can also send a seventh request to EASs that meet the second condition. This seventh request may carry some information from the second request to instruct the EAS meeting the requirements of the seventh request to register with the EES. The second condition is determined based on the information carried in the second request and may include: the EAS information matches one or more of the application identifier, EAS type, and location information carried in the second request. In other words, an EAS meeting the second condition can provide services to the application corresponding to the application identifier, supports the EAS type, and its distance from the location indicated by the location information falls within a set range. The seventh request carries one or more of the following: service characteristics of the application or service, computing power requirements, location information, EAS type, application identifier, and estimated access duration. The EAS determines this based on the EAS type and / or application identifier and / or location information and / or computing power requirements and / or estimated access duration and / or service characteristics carried in the second request.

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

[0729] Service characteristics of the application or business;

[0730] Computing power requirements;

[0731] Computing resource requirements;

[0732] Dynamic computing resource requirements;

[0733] Temporary computing power resource requirements;

[0734] Single-use computing resource requirements;

[0735] Specific computing resource requirements

[0736] Location information;

[0737] EAS type;

[0738] Application identifier;

[0739] Estimated visit duration.

[0740] Step 6: EAS sends a third request to EES.

[0741] Here, EAS can send the third request to EES after receiving the seventh request, or it can send the third request to EES before receiving the seventh request.

[0742] When EAS decides to register with EES, it sends a third request to EES. This third request carries at least one of EAS's computing power information, which includes one or more of the following: computing type, computing precision, and available computing power duration. Computing type includes one or more of the following: APU, CPU, DPU, GPU, NPU, and TPU. Computing precision includes one or more of the following: MIPS, DMIPS, OPS, and FLOPS.

[0743] For example, an EAS that receives the seventh request sends a third request to the EES, or an EAS that meets the requirements indicated by the seventh request sends a third request to the EES. The third request is used to request EAS registration. The third request carries at least the EAS's computing power information, and may also carry one or more of the following information about the EAS: EAS profile, registration expiration time, EAS identifier, FQDN or IP address, application service provider information or ECSP information, permission information, EAS type, location information, service capacity, DNAI, and load information.

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

[0745] Here, EES verifies the application service provider information and / or ECSP information and / or identifier of the EAS carried in the third request. If the information is correct, it determines that the EAS has the authority to register on EES. EES registers the EAS, stores the information carried in the third request sent by the EAS, assigns a registration identifier to the third node, and sends a second response to the EAS. The second response carries the registration identifier, indicating that the EAS registration was successful.

[0746] It should be noted that after EAS completes its registration on EES, it can update EAS's registration information with EES and / or initiate registration.

[0747] For example, if the registration information of an EAS successfully registered on EES changes, the EAS can send a fourth request to EES to request an update to its information. The fourth request must at least carry the EAS's registration identifier or EAS identifier, and updated computing power information. It may also carry one or more of the following information: EAS profile, registration expiration 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, and updated load information. Upon receiving the fourth request, EES verifies the EAS's application service provider information and / or ECSP information and / or identifier. If the information is correct, EES allows the update of the EAS's information and updates the locally stored EAS information based on the information carried in the fourth request. EES then sends a third response to the EAS. The third response may or may not carry the registration identifier, indicating that the EAS update was successful.

[0748] For example, if EAS decides to deregister with EES, it sends a fifth request to EES to request registration. This fifth request may carry EAS's computing power information, and may also carry one or more of the following: EAS's registration identifier, EAS ID, application service provider information, or ECSP information. Upon receiving the fifth request, EES verifies EAS's registration identifier and / or EAS identifier. If the information is correct, and / or the registration identifier and / or EAS identifier exists, EES determines that EAS has permission to register with EES. If all services on EAS have ended, EES allows EAS to register and deletes EAS's information locally, i.e., deletes the locally stored EAS registration information. EES then sends a second response to EAS, indicating that EAS's registration was successful.

[0749] Step 8: EES searches for EAS locally.

[0750] Here, when EES sends a second response to EAS, the information of successfully registered EAS stored locally by EES has changed. At this time, EES searches for EAS based on the updated local information. Specifically, EES matches the information carried in the first request with the information of locally registered EAS to find the EAS that matches the information carried in the first request.

[0751] If no EAS matching all the information carried in the first request is found, the EES can split the computing task into multiple first tasks based on the computing task and / or duration of the computing task carried in the first request. It then performs a secondary match between the other information carried in the first request and the information of locally registered EASs to find a third node that meets the requirements of the first task. For example, the EES might split a computing task from 14:00 to 14:30 into three sub-tasks for three time periods: 14:00 to 14:10, 14:10 to 14:20, and 14:20 to 14:30. Based on the first task, the application identifier carried in the first request, the EAS type, the service characteristics of the application or business, and the computing power requirements, it searches among locally registered EASs for one or more EASs closest to the location information carried in the first request.

[0752] If no third node that meets the requirements of the first task is found, the EEC negotiates with the AC to see if the computational precision can be reduced. If a new computational precision is negotiated, an EAS that meets the new computational precision and other requirements indicated by the first request is searched locally, based on the new computational precision and other information carried in the first request. The other information carried in the first request may include, but is not limited to, one or more of the following: application identifier, EAS type, service characteristics, computation type, duration of the computational task, and the first task.

[0753] If a suitable EAS is still not found after reducing the calculation precision, then the EES will report back to the EEC the EAS that is closest to the DNAI provided by the AC.

[0754] If an EAS is found that matches all the information carried in the first request, and / or an EAS that meets the requirements of the first task is found, then the EES can send the found EAS / EAS list / EAS time-segment list to the EEC, and send the EAS FQDN or IP address.

[0755] Step 9: EES sends its first response to EEC.

[0756] Here, when an EAS is located, it sends a first response to the EEC indicating the located EAS. The first response may carry the EAS identifier and / or FQDN and / or IP address of the EAS that meets 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 some or all of the information carried in the first request, and meeting the requirements of the first task.

[0757] If EAS cannot find EAS, the first response sent to EEC indicates that EAS has not been found.

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

[0759] Here, the fifth response can carry the information carried in the first response. For example, the fifth response carries the EAS's FQDN and / or IP address, which the AC can subsequently use to access the EAS.

[0760] In this embodiment of the application, the EEC takes computing power requirements into account when selecting an EAS, thereby selecting the most suitable EAS to provide users with the ultimate XR experience.

[0761] To implement the method on the first node side of this application embodiment, this application embodiment also provides a node lookup device, which is disposed on the first node, such as... Figure 9 As shown, the device includes:

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

[0763] In one embodiment, the first request is used to locate a third node.

[0764] In one embodiment, the device further includes:

[0765] The second sending unit is used to send a first response to the second node, wherein the first response indicates the endpoint information of the third node or that the third node has not been found.

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

[0767] Computing power requirements;

[0768] Computing resource requirements;

[0769] Dynamic computing resource requirements;

[0770] Temporary computing power resource requirements;

[0771] Single-use computing resource requirements;

[0772] Specific computing resource requirements;

[0773] Calculation accuracy;

[0774] Computing power tasks;

[0775] Duration of computing tasks;

[0776] The identifier of the third node;

[0777] Application service KPIs;

[0778] The computing power requirements of XR applications;

[0779] Application identifier;

[0780] Location information;

[0781] The type of the third node;

[0782] The identifier of the second node;

[0783] The estimated access duration to the third node;

[0784] Business duration;

[0785] Business identifier;

[0786] Service characteristics of the application or business;

[0787] User ID.

[0788] In one embodiment, the device further includes one or more of the following:

[0789] The first search unit is used to search for the third node based on the first information;

[0790] The second search unit is used to search locally for the third node indicated by the first request;

[0791] The third search unit is used to search locally for a third node that meets the requirements of the first task, which is obtained by splitting the computing power task and / or the duration of the computing power task carried by the first request.

[0792] The negotiation unit is used to negotiate with the second node to reduce the calculation accuracy;

[0793] The third sending unit is used to send feedback to the second node that a third node satisfies the first condition.

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

[0795] The search filter for the third node;

[0796] Location information;

[0797] The service KPIs of the fifth node;

[0798] The computing requirements of XR services.

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

[0800] Closest to the second node;

[0801] Meet the requirements of the second node;

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

[0803] Matches some or all of the information carried in the first request;

[0804] To meet the requirements of the primary task.

[0805] In one embodiment, the device further includes:

[0806] The fourth receiving unit is used to receive second information sent by the fourth node, the second information indicating an instantiable third node.

[0807] In one embodiment, the second information includes the identifier of an instantiable third node and / or available computing power and / or available computing power duration.

[0808] In one embodiment, the device further includes:

[0809] The fourth sending unit is used to send the second request to the fourth node.

[0810] In one embodiment, the second request is used to locate a third node.

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

[0812] Computing power requirements;

[0813] Computing resource requirements;

[0814] Dynamic computing resource requirements;

[0815] Temporary computing power resource requirements;

[0816] Single-use computing resource requirements;

[0817] Specific computing resource requirements;

[0818] Calculation accuracy;

[0819] Computing power tasks;

[0820] Duration of computing tasks;

[0821] The identifier of the third node;

[0822] Application service KPIs;

[0823] The computing power requirements of XR applications;

[0824] Application identifier;

[0825] Location information;

[0826] The type of the third node;

[0827] The identifier of the second node;

[0828] The estimated access duration to the third node;

[0829] Business duration;

[0830] Business identifier;

[0831] Service characteristics of the application or business;

[0832] User ID.

[0833] In one embodiment, the device further includes one or more of the following:

[0834] The fifth receiving unit is used to receive a third request sent by the third node; the third request carries at least computing power information and is used to request the registration of the third node;

[0835] Storage unit, used to store the information carried in the third request;

[0836] The fifth sending unit is used to send a second response to the third node; the second response indicates whether the third node's registration is successful or unsuccessful, and if the second response indicates that the third node's registration is successful, the second response carries a registration identifier.

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

[0838] EAS profile;

[0839] Registration expiration time;

[0840] The identifier of the third node;

[0841] FQDN;

[0842] IP address;

[0843] Application service provider information;

[0844] ECSP information;

[0845] Permission information;

[0846] The type of the third node;

[0847] Location information;

[0848] Available duration;

[0849] Business capacity;

[0850] DNAI;

[0851] Load information.

[0852] In one embodiment, the device further includes one or more of the following:

[0853] The sixth receiving unit is used to receive a fourth request sent by the third node; the fourth request carries at least updated computing power information and is used to request updates to the information of the third node.

[0854] The update unit is used to update the information of the third node locally based on the information carried in the fourth request;

[0855] The sixth sending unit is used to send a third response to the third node; the third response indicates whether the information update of the third node was successful or failed.

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

[0857] EAS profile;

[0858] Registration expiration time;

[0859] Registration mark;

[0860] The identifier of the third node;

[0861] Updated permission information;

[0862] Updated location information;

[0863] Updated service capacity;

[0864] Updated DNAI;

[0865] Updated load information.

[0866] In one embodiment, the device further includes one or more of the following:

[0867] The seventh receiving unit is used to receive the fifth request sent by the third node; the fifth request carries at least computing power information and is used to request to register with the third node;

[0868] The delete unit is used to delete information about a third node locally;

[0869] The seventh sending unit is used to send a fourth response to the third node; the fourth response indicates whether the third node's deregistration was successful or failed.

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

[0871] Registration mark;

[0872] The identifier of the third node;

[0873] Application service provider information;

[0874] ECSP information.

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

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

[0877] The computational precision includes one or more of MIPS, DMIPS, OPS, and FLOPS.

[0878] Available computing power duration.

[0879] In one embodiment, the first node includes one or more of the following:

[0880] EES, ECS, ECM.

[0881] In one embodiment, the second node includes one or more of the following:

[0882] EEC, terminal, UE, user.

[0883] In one embodiment, the third node includes one or more of the following:

[0884] EAS, AF, and application services.

[0885] In one embodiment, the fourth node includes one or more of the following:

[0886] AF and ECSP management systems.

[0887] In one embodiment, the fifth node includes one or more of the following:

[0888] AC, terminal, UE, user.

[0889] In practical applications, 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 the processor in the node search device in conjunction with the communication interface. The first search unit, the second search unit, the third search unit, the negotiation unit, the storage unit, the deletion unit, and the update unit can be implemented by the processor in the node search device.

[0890] To implement the method on the second node side of the embodiments of this application, the embodiments of this application also provide a node search device, which is disposed on the second node, such as... Figure 10 As shown, the device includes:

[0891] The first sending unit 1001 is used to send a first request to the first node.

[0892] In one embodiment, the device further includes:

[0893] The eighth receiving unit is used to receive the sixth request sent by the fifth node.

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

[0895] The profile of the fifth node;

[0896] The identifier of the third node;

[0897] The service KPIs of the fifth node;

[0898] Computing power requirements;

[0899] Computing resource requirements;

[0900] Dynamic computing resource requirements;

[0901] Temporary computing power resource requirements;

[0902] Single-use computing resource requirements;

[0903] Specific computing resource requirements;

[0904] The computing power requirements of XR applications.

[0905] In one embodiment, the first request is used to locate a third node.

[0906] In one embodiment, the device further includes:

[0907] The ninth receiving unit is used to receive a first response sent by the first node, wherein the first response indicates the endpoint information of the third node or that the third node has not been found.

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

[0909] Computing power requirements;

[0910] Computing resource requirements;

[0911] Dynamic computing resource requirements;

[0912] Temporary computing power resource requirements;

[0913] Single-use computing resource requirements;

[0914] Specific computing resource requirements;

[0915] Calculation accuracy;

[0916] Computing power tasks;

[0917] Duration of computing tasks;

[0918] The identifier of the third node;

[0919] Application service KPIs;

[0920] The computing power requirements of XR applications;

[0921] Application identifier;

[0922] Location information;

[0923] The type of the third node;

[0924] The identifier of the second node;

[0925] The estimated access duration to the third node;

[0926] Business duration;

[0927] Business identifier;

[0928] Service characteristics of the application or business;

[0929] User ID.

[0930] In one embodiment, the first node includes an EES and / or an ECM.

[0931] In one embodiment, the second node includes one or more of the following:

[0932] EEC, terminal, UE, user.

[0933] In one embodiment, the third node includes one or more of the following:

[0934] EAS, AF, and application services.

[0935] In one embodiment, the fifth node includes one or more of the following:

[0936] AC, terminal, UE, user. In practical applications, the first sending unit 1001, the eighth receiving unit, and the ninth receiving unit can be implemented by a processor in the node lookup device combined with a communication interface.

[0937] To implement the method on the fourth node side of this application embodiment, this application embodiment also provides a node search device, which is set on the fourth node, such as... Figure 11 As shown, the device includes:

[0938] The second receiving unit 1101 is used to receive the second request sent by the first node.

[0939] In one embodiment, the second request is used to locate a third node.

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

[0941] Computing power requirements;

[0942] Computing resource requirements;

[0943] Dynamic computing resource requirements;

[0944] Temporary computing power resource requirements;

[0945] Single-use computing resource requirements;

[0946] Specific computing resource requirements;

[0947] Calculation accuracy;

[0948] Computing power tasks;

[0949] Duration of computing tasks;

[0950] The identifier of the third node;

[0951] Application service KPIs;

[0952] The computing power requirements of XR applications;

[0953] Application identifier;

[0954] Location information;

[0955] The type of the third node;

[0956] The identifier of the second node;

[0957] The estimated access duration to the third node;

[0958] Business duration;

[0959] Business identifier;

[0960] Service characteristics of the application or business;

[0961] User ID.

[0962] In one embodiment, the device further includes:

[0963] The eighth sending unit is used to send the seventh request to the third node; and / or

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

[0965] In one embodiment, the second information includes the identifier of an instantiable third node and / or available computing power and / or available computing power duration.

[0966] 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.

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

[0968] Service characteristics of the application or business;

[0969] Computing power requirements;

[0970] Computing resource requirements;

[0971] Dynamic computing resource requirements;

[0972] Temporary computing power resource requirements;

[0973] Single-use computing resource requirements;

[0974] Specific computing resource requirements;

[0975] Location information;

[0976] The type of the third node;

[0977] Application identifier;

[0978] Estimated visit duration.

[0979] In one embodiment, the third node is determined based on the type and / or application identifier and / or location information and / or computing power requirements and / or expected access duration and / or service characteristics carried in the second request.

[0980] In one embodiment, the first node includes one or more of the following:

[0981] EES, ECS, ECM.

[0982] In one embodiment, the second node includes one or more of the following:

[0983] EEC, terminal, UE, user.

[0984] In one embodiment, the third node includes one or more of the following:

[0985] EAS, AF, and application services.

[0986] In one embodiment, the fourth node includes one or more of the following:

[0987] AF and ECSP management system. In practical applications, the second receiving unit 1101 and the eighth sending unit can be implemented by the processor in the node lookup device.

[0988] To implement the method on the third node side of this application embodiment, this application embodiment also provides a node search device, which is set on the third node, such as... Figure 12 As shown, the device includes:

[0989] The third receiving unit 1201 is used to receive the fifth request sent by the fourth node.

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

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

[0992] Service characteristics of the application or business;

[0993] Computing power requirements;

[0994] Computing resource requirements;

[0995] Dynamic computing resource requirements;

[0996] Temporary computing power resource requirements;

[0997] Single-use computing resource requirements;

[0998] Specific computing resource requirements;

[0999] Location information;

[1000] The type of the third node;

[1001] Application identifier;

[1002] Estimated visit duration.

[1003] In one embodiment, the device further includes one or more of the following:

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

[1005] The tenth receiving unit is used to receive the second response sent by the first node; the second response indicates whether the third node has successfully registered or failed, and if the second response indicates that the third node has successfully registered, the second response carries a registration identifier.

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

[1007] EAS profile;

[1008] Registration expiration time;

[1009] The identifier of the third node;

[1010] FQDN;

[1011] IP address;

[1012] Application service provider information;

[1013] ECSP information;

[1014] Permission information;

[1015] The type of the third node;

[1016] Location information;

[1017] Available duration;

[1018] Business capacity;

[1019] Calculation type;

[1020] Calculation accuracy;

[1021] DNAI;

[1022] Load information.

[1023] In one embodiment, it further includes one or more of the following:

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

[1025] The tenth receiving unit is used to receive the third response sent by the first node; the third response indicates whether the information update of the third node was successful or failed.

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

[1027] EAS profile;

[1028] Registration expiration time;

[1029] Registration mark;

[1030] The identifier of the third node;

[1031] Updated permission information;

[1032] Updated location information;

[1033] Updated service capacity;

[1034] Updated DNAI;

[1035] Updated load information.

[1036] In one embodiment, the device further includes one or more of the following:

[1037] The twelfth sending unit is used to send a fifth request to the first node; the fifth request carries at least computing power information and is used to request to register with the third node;

[1038] The eleventh receiving unit is used to receive the fourth response sent by the first node; the third response indicates whether the third node's deregistration was successful or failed.

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

[1040] Registration mark;

[1041] The identifier of the third node;

[1042] Application service provider information;

[1043] ECSP information.

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

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

[1046] The computational precision includes one or more of MIPS, DMIPS, OPS, and FLOPS.

[1047] Available computing power duration.

[1048] In one embodiment, the first node includes one or more of the following:

[1049] EES, ECS, ECM.

[1050] In one embodiment, the third node includes one or more of the following:

[1051] EAS, AF, and application services.

[1052] In one embodiment, the fourth node includes one or more of the following:

[1053] AF and ECSP management systems.

[1054] In practical applications, 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 implemented by the processor in the node lookup device in conjunction with the communication interface.

[1055] It should be noted that the node search device provided in the above embodiments is only illustrated by the division of the above-described program modules. In practical applications, the above processing can be assigned to different program modules as needed, that is, the internal structure of the device can be divided into different program modules to complete all or part of the processing described above. In addition, the node search device and the node search method embodiments provided in the above embodiments belong to the same concept, and their specific implementation process can be found in the method embodiments, which will not be repeated here.

[1056] Based on the hardware implementation of the above program modules, and in order to implement the method on the first node side of the embodiments of this application, the embodiments of this application also provide a first node, such as... Figure 13 As shown, the first node 1300 includes:

[1057] The first communication interface 1301 is capable of exchanging information with other network nodes;

[1058] The first processor 1302 is connected to the first communication interface 1301 to enable information interaction with other network nodes. When running a computer program, it executes the methods provided by one or more technical solutions on the first node side. The computer program is stored in the first memory 1303.

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

[1060] In one embodiment, the first request is used to locate a third node.

[1061] In one 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 was not found.

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

[1063] Computing power requirements;

[1064] Computing resource requirements;

[1065] Dynamic computing resource requirements;

[1066] Temporary computing power resource requirements;

[1067] Single-use computing resource requirements;

[1068] Specific computing resource requirements;

[1069] Calculation accuracy;

[1070] Computing power tasks;

[1071] Duration of computing tasks;

[1072] The identifier of the third node;

[1073] Application service KPIs;

[1074] The computing power requirements of XR applications;

[1075] Application identifier;

[1076] Location information;

[1077] The type of the third node;

[1078] The identifier of the second node;

[1079] The estimated access duration to the third node;

[1080] Business duration;

[1081] Business identifier;

[1082] Service characteristics of the application or business;

[1083] User ID.

[1084] In one embodiment, the first processor 1302 is used for one or more of the following:

[1085] Find the third node based on the first piece of information;

[1086] Locate the third node indicated by the first request locally;

[1087] Find a third node locally that meets the requirements of the first task. The first task is obtained by splitting the computing power task and / or the duration of the computing power task carried by the first request.

[1088] Negotiate with the second node to reduce computational precision; and / or

[1089] The first communication interface 1301 is also used to send feedback to the second node that a third node meets the first condition.

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

[1091] The search filter for the third node;

[1092] Location information;

[1093] The service KPIs of the fifth node;

[1094] The computing requirements of XR services.

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

[1096] Closest to the second node;

[1097] Meet the requirements of the second node;

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

[1099] Matches some or all of the information carried in the first request;

[1100] To meet the requirements of the primary task.

[1101] In one 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.

[1102] In one embodiment, the second information includes the identifier of an instantiable third node and / or available computing power and / or available computing power duration.

[1103] In one embodiment, the first communication interface 1301 is also used to send a second request to the fourth node.

[1104] In one embodiment, the second request is used to locate a third node.

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

[1106] Computing power requirements;

[1107] Computing resource requirements;

[1108] Dynamic computing resource requirements;

[1109] Temporary computing power resource requirements;

[1110] Single-use computing resource requirements;

[1111] Specific computing resource requirements;

[1112] Calculation accuracy;

[1113] Computing power tasks;

[1114] Duration of computing tasks;

[1115] The identifier of the third node;

[1116] Application service KPIs;

[1117] The computing power requirements of XR applications;

[1118] Application identifier;

[1119] Location information;

[1120] The type of the third node;

[1121] The identifier of the second node;

[1122] The estimated access duration to the third node;

[1123] Business duration;

[1124] Business identifier;

[1125] Service characteristics of the application or business;

[1126] User ID.

[1127] In one embodiment, the first communication interface 1301 is further configured to receive a third request sent by a third node, and / or send a second response to the third node; the third request carries at least computing power information and is used to request the registration of the third node; the second response indicates whether the third node registration is successful or unsuccessful, and if the second response indicates that the third node registration is successful, the second response carries a registration identifier;

[1128] The first processor 1302 is also used to store the information carried in the third request.

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

[1130] EAS profile;

[1131] Registration expiration time;

[1132] The identifier of the third node;

[1133] FQDN;

[1134] IP address;

[1135] Application service provider information;

[1136] ECSP information;

[1137] Permission information;

[1138] The type of the third node;

[1139] Location information;

[1140] Available duration;

[1141] Business capacity;

[1142] DNAI;

[1143] Load information.

[1144] In one 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 carries at least updated computing power information and is used to request updates to the information of the third node; the third response indicates whether the information update of the third node was successful or failed.

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

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

[1147] EAS profile;

[1148] Registration expiration time;

[1149] Registration mark;

[1150] The identifier of the third node;

[1151] Updated permission information;

[1152] Updated location information;

[1153] Updated service capacity;

[1154] Updated DNAI;

[1155] Updated load information.

[1156] In one 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; the fifth request carries at least computing power information and is used to request to register with the third node; the fourth response indicates whether the third node's registration was successful or failed.

[1157] The first processor 1302 is also used to delete information about the third node locally.

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

[1159] Registration mark;

[1160] The identifier of the third node;

[1161] Application service provider information;

[1162] ECSP information.

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

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

[1165] The computational precision includes one or more of MIPS, DMIPS, OPS, and FLOPS.

[1166] Available computing power duration.

[1167] In one embodiment, the first node includes one or more of the following:

[1168] EES, ECS, ECM.

[1169] In one embodiment, the second node includes one or more of the following:

[1170] EEC, terminal, UE, user.

[1171] In one embodiment, the third node includes one or more of the following:

[1172] EAS, AF, and application services.

[1173] In one embodiment, the fourth node includes one or more of the following:

[1174] AF and ECSP management systems.

[1175] In one embodiment, the fifth node includes one or more of the following:

[1176] AC, terminal, UE, user.

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

[1178] Of course, in practical applications, the 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 implement communication between these 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 clarity, in... Figure 13 The general designated all buses as Bus System 1304.

[1179] The first memory 1303 in this embodiment is used to store various types of data to support the operation of the first node 1300. Examples of such data include any computer program used to operate on the first node 1300.

[1180] The methods disclosed in the above embodiments of this application can be applied to the first processor 1302, or implemented by the first processor 1302. The first processor 1302 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the integrated logic circuit of the hardware or by instructions in the form of software in the first processor 1302. The first processor 1302 may 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 methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of this application can be directly reflected as being executed by a hardware decoding processor, or being executed by a combination of hardware and software modules in the decoding processor. The software modules may be located in a storage medium, which is located in the first memory 1303. The first processor 1302 reads the information in the first memory 1303 and completes the steps of the aforementioned method in combination with its hardware.

[1181] In an exemplary embodiment, the first node 1300 may 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, or other electronic components to perform the aforementioned method.

[1182] Based on the hardware implementation of the above program modules, and in order to implement the method on the second node side of the embodiments of this application, the embodiments of this application also provide a second node, such as... Figure 14 As shown, the second node 1400 includes:

[1183] The second communication interface 1401 is capable of exchanging information with other network nodes;

[1184] The second processor 1402 is connected to the second communication interface 1401 to enable information interaction with other network nodes. When running a computer program, it executes the methods provided by one or more technical solutions on the second node side. The computer program is stored in the second memory 1403.

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

[1186] In one embodiment, the second communication interface 1401 is also used to receive a sixth request sent by the fifth node.

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

[1188] The profile of the fifth node;

[1189] The identifier of the third node;

[1190] The service KPIs of the fifth node;

[1191] Computing power requirements;

[1192] Computing resource requirements;

[1193] Dynamic computing resource requirements;

[1194] Temporary computing power resource requirements;

[1195] Single-use computing resource requirements;

[1196] Specific computing resource requirements;

[1197] The computing power requirements of XR applications.

[1198] In one embodiment, the first request is used to locate a third node.

[1199] In one 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 was not found.

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

[1201] Computing power requirements;

[1202] Computing resource requirements;

[1203] Dynamic computing resource requirements;

[1204] Temporary computing power resource requirements;

[1205] Single-use computing resource requirements;

[1206] Specific computing resource requirements;

[1207] Calculation accuracy;

[1208] Computing power tasks;

[1209] Duration of computing tasks;

[1210] The identifier of the third node;

[1211] Application service KPIs;

[1212] The computing power requirements of XR applications;

[1213] Application identifier;

[1214] Location information;

[1215] The type of the third node;

[1216] The identifier of the second node;

[1217] The estimated access duration to the third node;

[1218] Business duration;

[1219] Business identifier;

[1220] Service characteristics of the application or business;

[1221] User ID.

[1222] In one embodiment, the first node includes an EES and / or an ECM.

[1223] In one embodiment, the second node includes one or more of the following:

[1224] EEC, terminal, UE, user.

[1225] In one embodiment, the third node includes one or more of the following:

[1226] EAS, AF, and application services.

[1227] In one embodiment, the fifth node includes one or more of the following:

[1228] AC, terminal, UE, user.

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

[1230] Of course, in practical applications, the 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 implement communication between these components. In addition to the data bus, the bus system 1404 also includes a power bus, a control bus, and a status signal bus. However, for clarity, in... Figure 14 The general designated all buses as Bus System 1404.

[1231] The second memory 1403 in this embodiment is used to store various types of data to support the operation of the second node 1400. Examples of such data include any computer program used to operate on the second node 1400.

[1232] The methods disclosed in the embodiments of this application can be applied to, or implemented by, the second processor 1402. The second processor 1402 may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method can be completed by the integrated logic circuitry of the hardware or by instructions in the form of software within the second processor 1402. The second processor 1402 may be a general-purpose 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 this application. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of this application can be directly manifested as execution by a hardware decoding processor, or execution by a combination of hardware and software modules in the decoding processor. The software modules may be located in a storage medium, specifically a second memory 1403. The second processor 1402 reads information from the second memory 1403 and, in conjunction with its hardware, completes the steps of the aforementioned method.

[1233] In an exemplary embodiment, the second node 1400 may be implemented by one or more ASICs, DSPs, PLDs, CPLDs, FPGAs, general-purpose processors, controllers, MCUs, microprocessors, or other electronic components to perform the aforementioned method.

[1234] Based on the hardware implementation of the above program modules, and in order to implement the method on the fourth node side of the embodiments of this application, the embodiments of this application also provide a fourth node, such as... Figure 15 As shown, the fourth node 1500 includes:

[1235] The third communication interface 1501 is capable of exchanging information with other network nodes;

[1236] The third processor 1502 is connected to the third communication interface 1501 to enable information interaction with other network nodes. When running a computer program, it executes the methods provided by one or more technical solutions on the fourth node side. The computer program is stored in the third memory 1503.

[1237] Specifically, the third communication interface 1501 is used to receive the second request sent by the first node.

[1238] In one embodiment, the second request is used to locate a third node.

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

[1240] Computing power requirements;

[1241] Computing resource requirements;

[1242] Dynamic computing resource requirements;

[1243] Temporary computing power resource requirements;

[1244] Single-use computing resource requirements;

[1245] Specific computing resource requirements;

[1246] Calculation accuracy;

[1247] Computing power tasks;

[1248] Duration of computing tasks;

[1249] The identifier of the third node;

[1250] Application service KPIs;

[1251] The computing power requirements of XR applications;

[1252] Application identifier;

[1253] Location information;

[1254] The type of the third node;

[1255] The identifier of the second node;

[1256] The estimated access duration to the third node;

[1257] Business duration;

[1258] Business identifier;

[1259] Service characteristics of the application or business;

[1260] User ID.

[1261] In one embodiment, the third communication interface 1501 is further configured to send a seventh request to a third node; and / or send second information to a first node, the second information indicating an instantiable third node.

[1262] In one embodiment, the second information includes the identifier of an instantiable third node and / or available computing power and / or available computing power duration.

[1263] 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.

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

[1265] Service characteristics of the application or business;

[1266] Computing power requirements;

[1267] Computing resource requirements;

[1268] Dynamic computing resource requirements;

[1269] Temporary computing power resource requirements;

[1270] Single-use computing resource requirements;

[1271] Specific computing resource requirements;

[1272] Location information;

[1273] The type of the third node;

[1274] Application identifier;

[1275] Estimated visit duration.

[1276] In one embodiment, the third node is determined based on the type and / or application identifier and / or location information and / or computing power requirements and / or expected access duration and / or service characteristics carried in the second request.

[1277] In one embodiment, the first node includes one or more of the following:

[1278] EES, ECS, ECM.

[1279] In one embodiment, the second node includes one or more of the following:

[1280] EEC, terminal, UE, user.

[1281] In one embodiment, the third node includes one or more of the following:

[1282] EAS, AF, and application services.

[1283] In one embodiment, the fourth node includes one or more of the following:

[1284] AF and ECSP management systems.

[1285] It should be noted that the specific processing procedures of the third processor 1502 and the third communication interface 1501 can be understood by referring to the above method.

[1286] Of course, in practical applications, the 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 implement communication between these components. In addition to the data bus, the bus system 1504 also includes a power bus, a control bus, and a status signal bus. However, for clarity, in... Figure 15 The general labeled all buses as Bus System 1504.

[1287] The third memory 1503 in this embodiment is used to store various types of data to support the operation of the fourth node 1500. Examples of such data include any computer program used to operate on the fourth node 1500.

[1288] The methods disclosed in the embodiments of this application can be applied to, or implemented by, the third processor 1502. The third processor 1502 may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method can be completed by the integrated logic circuitry of the hardware or by instructions in the form of software within the third processor 1502. The third processor 1502 may be a general-purpose processor, a DSP, or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The third processor 1502 can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of this application can be directly manifested as execution by a hardware decoding processor, or execution by a combination of hardware and software modules in the decoding processor. The software modules may be located in a storage medium, specifically a third memory 1503. The third processor 1502 reads information from the third memory 1503 and, in conjunction with its hardware, completes the steps of the aforementioned method.

[1289] In an exemplary embodiment, the fourth node 1500 may be implemented by one or more ASICs, DSPs, PLDs, CPLDs, FPGAs, general-purpose processors, controllers, MCUs, microprocessors, or other electronic components to perform the aforementioned method.

[1290] Based on the hardware implementation of the above program modules, and in order to implement the method on the third node side of the embodiments of this application, the embodiments of this application also provide a third node. For example... Figure 16 As shown, the third node 1600 includes:

[1291] The fourth communication interface 1601 is capable of exchanging information with other network nodes;

[1292] The fourth processor 1602 is connected to the fourth communication interface 1601 to enable information interaction with other network nodes and to execute the methods provided by one or more technical solutions on the third node side when running a computer program. The computer program is stored on the fourth memory 1603.

[1293] Specifically, the fourth communication interface 1601 is used to receive the fifth request sent by the fourth node.

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

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

[1296] Service characteristics of the application or business;

[1297] Computing power requirements;

[1298] Computing resource requirements;

[1299] Dynamic computing resource requirements;

[1300] Temporary computing power resource requirements;

[1301] Single-use computing resource requirements;

[1302] Specific computing resource requirements;

[1303] Location information;

[1304] The type of the third node;

[1305] Application identifier;

[1306] Estimated visit duration.

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

[1308] Send a third request to the first node; wherein the third request carries at least computing power information for requesting the registration of the third node;

[1309] The system receives a second response sent by the first node; the second response indicates whether the third node's registration was successful or failed, and if the second response indicates that the third node's registration was successful, the second response carries a registration identifier.

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

[1311] EAS profile;

[1312] Registration expiration time;

[1313] The identifier of the third node;

[1314] FQDN;

[1315] IP address;

[1316] Application service provider information;

[1317] ECSP information;

[1318] Permission information;

[1319] The type of the third node;

[1320] Location information;

[1321] Available duration;

[1322] Business capacity;

[1323] Calculation type;

[1324] Calculation accuracy;

[1325] DNAI;

[1326] Load information.

[1327] In one embodiment, the fourth communication interface 1601 is further used for one or more of the following:

[1328] Send a fourth request to the first node; the fourth request carries at least updated computing power information and is used to request updates to the information of the third node;

[1329] Receive a third response sent by the first node; the third response indicates whether the information update of the third node was successful or failed.

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

[1331] EAS profile;

[1332] Registration expiration time;

[1333] Registration mark;

[1334] The identifier of the third node;

[1335] Updated permission information;

[1336] Updated location information;

[1337] Updated service capacity;

[1338] Updated DNAI;

[1339] Updated load information.

[1340] In one embodiment, the fourth communication interface 1601 is further used for one or more of the following:

[1341] Send a fifth request to the first node; the fifth request carries at least computing power information and is used to request to register with the third node;

[1342] Receive the fourth response sent by the first node; the third response indicates whether the third node's deregistration was successful or failed.

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

[1344] Registration mark;

[1345] The identifier of the third node;

[1346] Application service provider information;

[1347] ECSP information.

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

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

[1350] The computational precision includes one or more of MIPS, DMIPS, OPS, and FLOPS.

[1351] Available computing power duration.

[1352] In one embodiment, the first node includes one or more of the following:

[1353] EES, ECS, ECM.

[1354] In one embodiment, the third node includes one or more of the following:

[1355] EAS, AF, and application services.

[1356] In one embodiment, the fourth node includes one or more of the following:

[1357] AF and ECSP management systems.

[1358] It should be noted that the specific processing procedures of the fourth processor 1602 and the fourth communication interface 1601 can be understood by referring to the above method.

[1359] Of course, in practical applications, the various components in the third node 1600 are coupled together through the bus system 1604. It can be understood that the bus system 1604 is used to implement communication between these components. In addition to the data bus, the bus system 1604 also includes a power bus, a control bus, and a status signal bus. However, for clarity, in... Figure 16 The general labeled all buses as Bus System 1604.

[1360] The fourth memory 1603 in this embodiment is used to store various types of data to support the operation of the third node 1600. Examples of such data include any computer program used to operate on the third node 1600.

[1361] The methods disclosed in the embodiments of this application can be applied to, or implemented by, the fourth processor 1602. The fourth processor 1602 may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method can be completed by the integrated logic circuitry of the hardware or by instructions in the software form of the fourth processor 1602. The fourth processor 1602 may be a general-purpose processor, a DSP, or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The fourth processor 1602 can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of this application can be directly manifested as execution by a hardware decoding processor, or execution by a combination of hardware and software modules in the decoding processor. The software modules may be located in a storage medium, specifically a fourth memory 1603. The fourth processor 1602 reads information from the fourth memory 1603 and, in conjunction with its hardware, completes the steps of the aforementioned method.

[1362] In an exemplary embodiment, the third node 1600 may be implemented by one or more ASICs, DSPs, PLDs, CPLDs, FPGAs, general-purpose processors, controllers, MCUs, microprocessors, or other electronic components to perform the aforementioned method.

[1363] It is understood that the memories (first memory 1303, second memory 1403, third memory 1503, and fourth memory 1603) in the embodiments of this application can be volatile memory or non-volatile memory, or both. Specifically, the non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), ferromagnetic random access memory (FRAM), flash memory, magnetic surface memory, optical disc, or compact disc read-only memory (CD-ROM); the magnetic surface memory can be disk storage or magnetic tape storage. The volatile memory can be random access memory (RAM), which is used as an external cache.By way of example, but not limitation, many forms of RAM are available, 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 (DDRSDRAM), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), SyncLink Dynamic Random Access Memory (SLDRAM), and Direct Rambus Random Access Memory (DRRAM). The memories described in the embodiments of this application are intended to include, but are not limited to, these and any other suitable types of memory.

[1364] In an exemplary embodiment, this application also provides a storage medium, namely a computer storage medium, specifically a computer-readable storage medium, such as a first memory 1303 storing a computer program, which can be executed by a first processor 1302 of a first node 1300 to complete the steps described in the aforementioned first node-side method. Another example is a second memory 1403 storing a computer program, which can be executed by a second processor 1402 of a second node 1400 to complete the steps described in the aforementioned second node-side method. Yet another example is a third memory 1503 storing a computer program, which can be executed by a third processor 1502 of a fourth node 1500 to complete the steps described in the aforementioned fourth node-side method. And yet another example is a fourth memory 1603 storing a computer program, which can be executed by a fourth processor 1602 of a third node 1600 to complete the steps described in the aforementioned third node-side method.

[1365] Computer-readable storage media can be FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface memory, optical disc, or CD-ROM, etc.

[1366] For example, this application also provides a computer program product, including a computer program that can be executed by a first processor 1302 of a first node 1300 to complete the steps described in the aforementioned first node-side method. Alternatively, the computer program can be executed by a second processor 1402 of a second node 1400 to complete the steps described in the aforementioned second node-side method. Alternatively, the computer program can be executed by a third processor 1502 of a fourth node 1500 to complete the steps described in the aforementioned fourth node-side method. Alternatively, the computer program can be executed by a fourth processor 1602 of a third node 1600 to complete the steps described in the aforementioned third node-side method.

[1367] It should be noted that terms such as "first" and "second" are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[1368] In this document, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent three cases: A alone, A and B simultaneously, and B alone. Additionally, the term "one or more" in this document refers to any combination of at least two of a plurality of elements. For example, including one or more of A, B, and C can represent including any one or at least two or more elements selected from the set consisting of A, B, and C.

[1369] Furthermore, the technical solutions described in the embodiments of this application can be combined arbitrarily without conflict.

[1370] The above description is merely a preferred embodiment of this application and is not intended to limit the scope of protection of this application.

Claims

1. A method of node lookup, characterized by, The method applied to a first node comprises: receiving a first request sent by a second node.

2. The method of claim 1, wherein, The first request is used to find a third node.

3. 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.

4. The method of claim 1, wherein, The first request carries one or more of the following: 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 key performance indicator (KPI); computing power requirement of an extended reality (XR) application; application identifier; location information; type of the third node; identifier of the second node; expected access duration to the third node; service duration; service identifier; service characteristics of the application or service; user identifier.

5. The method according to any one of claims 1 to 4, characterized in that, The method further comprises one or more of the following: finding the third node based on first information; locally finding the third node indicated by the first request; locally finding the third node that meets the requirement 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.

6. The method of claim 5, wherein, The first information comprises one or more of the following: a search filter of the third node; location information; service KPI of a fifth node; computing requirement of an XR service.

7. The method of claim 5, wherein, The first condition comprises one or more of the following: closest to the second node; meeting 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; meeting the requirement of the first task.

8. The method according to any one of claims 1 to 5, characterized in that, The method further comprises: receiving second information sent by a fourth node, the second information indicating instantiable third nodes.

9. The method of claim 8, wherein, The second information comprises identifier and / or available computing capacity and / or available computing power duration of the instantiable third nodes.

10. The method according to any one of claims 1 to 5, characterized in that, The method further comprises: sending a second request to the fourth node.

11. The method of claim 10, wherein, The second request is used to find a third node.

12. The method of claim 10, wherein, The second request carries one or more of the following: 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; expected access duration to the third node; service duration; service identifier; service characteristics of the application or service; user identifier.

13. 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 carrying computing power information, and being 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 representing successful or failed registration of the third node, and carrying a registration identifier in the case of representing successful registration of the third node.

14. The method of claim 13, wherein, The third request further carries one or more of the following information of the third node: EAS profile; registration invalidation 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.

15. 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 carrying at least updated computing power information for requesting to update information of the third node; updating, locally, the information of the third node based on information carried by the fourth request; sending a third response to the third node, the third response indicating success or failure of the information update of the third node.

16. The method of claim 15, wherein, The fourth request carries one or more of the following information of the third node: EAS profile; registration invalidation time; registration identity; identity of the third node; updated permission information; updated location information; updated service capacity; updated DNAI; updated load information.

17. 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 carrying at least computing power information for requesting to deregister the third node; deleting, locally, the information of the third node; sending a fourth response to the third node, the fourth response indicating success or failure of the deregistration of the third node.

18. 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.

19. The method according to any one of claims 13 to 18, characterized in that, The computing power information includes one or more of the following: computing type, the computing type including one or more of an accelerated processing unit (APU), a central processing unit (CPU), a deep learning processing unit (DPU), a graphics processing unit (GPU), a neural processing unit (NPU), and a tensor processing unit (TPU); computing precision, the computing precision including one or more of a million instructions per second (MIPS), a million integer operation instructions per second (DMIPS), an operation per second (OPS), and a floating point operation per second (FLOPS); available computing power duration.

20. The method according to any one of claims 1 to 4, 6 to 7, 9, 11 to 18, characterized in that, The first node includes one or more of the following: an edge enabler server (EES), an edge configuration server (ECS), and an edge configuration management (ECM).

21. The method according to any one of claims 1 to 4, 6 to 7, 9, 11 to 18, characterized in that, The second node includes one or more of the following: an edge enabler client (EEC), a terminal, a user equipment (UE), and a user.

22. The method of any one of claims 3-4, 6-7, 9, 11-18, wherein, The third node includes one or more of the following: an edge application server (EAS), an application function (AF), and an application service.

23. The method of claim 8, wherein, The fourth node includes one or more of the following: an AF and an ECSP management system.

24. The method of claim 6 or 7, wherein, The fifth node includes one or more of the following: an application client (AC), a terminal, a UE, and a user.

25. A method of node lookup, the method comprising: The method is applied to the second node and includes: sending a first request to the first node.

26. The method of claim 25, wherein, The method further includes: receiving a sixth request sent by the fifth node.

27. The method of claim 26, wherein, The sixth request carries one or more of the following: a profile of the fifth node; identity of the third node; service KPI of the fifth node; computing power demand; computing power resource demand; dynamic computing power resource demand; temporary computing power resource demand; Single-time computing resource requirement; Specific computing resource requirement; Computing requirement of XR application.

28. The method of claim 25, wherein, The first request is used to find the third node.

29. 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.

30. The method of claim 25, wherein, The first request carries one or more of the following: Computing requirement; Computing resource requirement; Dynamic computing resource requirement; Temporary computing resource requirement; Single-time computing resource requirement; Specific computing resource requirement; Computing precision; Computing task; Duration of computing task; Identity of the third node; Application service KPI; Computing requirement of 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.

31. The method of any of claims 25-30, wherein: The first node comprises an EES and / or an ECM.

32. The method of any one of claims 25 to 30, wherein, The second node comprises one or more of: An EEC, a terminal, a UE, a user.

33. The method of claim 28 or 29, wherein, The third node comprises one or more of: An EAS, an AF, an application service.

34. The method of claim 26 or 27, wherein, The fifth node comprises one or more of: An AC, a terminal, a UE, a user.

35. A method of node lookup, the method comprising: The method applied to the fourth node comprises: receiving a second request sent by the first node.

36. The method of claim 35, wherein, The second request is used to find the third node.

37. The method of claim 35, wherein, The second request carries one or more of the following: Computing requirement; Computing resource requirement; Dynamic computing resource requirement; Temporary computing resource requirement; Single-time computing resource requirement; Specific computing resource requirement; Computing precision; Computing task; Duration of computing task; Identity of the third node; Application service KPI; Computing requirement of 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.

38. 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 the third node that can be instantiated.

39. The method of claim 38, wherein, The second information comprises the identity and / or available computing capacity and / or available computing duration of the third node that can be instantiated.

40. 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 to the first node.

41. The method of claim 38, wherein, The seventh request carries one or more of the following: Service characteristics of the application or service; Computing requirement; Computing resource requirement; Dynamic computing resource requirement; Temporary computing resource requirement; Single-time computing resource requirement; Specific computing resource requirement; Location information; Type of the third node; Application identity; Expected access duration.

42. The method of claim 38, wherein, The third node is determined according to the type and / or application identity and / or location information and / or computing requirement and / or expected access duration and / or service characteristics of the third node carried by the second request.

43. The method of any one of claims 35-37, 39-42, wherein, The first node comprises one or more of: An EES, an ECS, an ECM.

44. The method of claim 37, wherein, The second node comprises one or more of: An EEC, a terminal, a UE, a user.

45. The method of any one of claims 36-37, 39-42, wherein, The third node comprises one or more of: EAS, AF, application service.

46. The method of any one of claims 35-37, 39-42, wherein, The fourth node comprises one or more of: AF, ECSP management system.

47. A method of node lookup, the method comprising: The method applied to the third node comprises: Receiving a seventh request sent by the fourth node.

48. The method of claim 47, wherein, 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.

49. The method of claim 47, wherein, The seventh request carries one or more of: 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.

50. The method of claim 47, wherein, The method further comprises one or more of: 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 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 identifier.

51. 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 the ECSP; Permission information; Type of the third node; Location information; Available duration; Service capacity; Computing type; Computing accuracy; DNAI; Load information.

52. The method of claim 47, wherein, The method further comprises one or more of: 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 represents successful or failed update of information of the third node.

53. 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.

54. The method of claim 47, wherein, The method further comprises one or more of: 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 represents successful or failed deregistration of the third node.

55. The method of claim 51, wherein, The fifth request further carries one or more of: Registration identifier; Identifier of the third node; Application service provider information; Information of the ECSP.

56. The method of any one of claims 50 to 55, wherein, The computing power information comprises one or more of: Computing type, the computing type comprising one or more of: APU, CPU, DPU, GPU, NPU, and TPU; Computing accuracy, the computing accuracy comprising one or more of: MIPS, DMIPS, OPS, and FLOPS; Available computing power duration.

57. The method of any one of claims 48-55, wherein, The first node comprises one or more of: EES, ECS, and ECM.

58. The method of any one of claims 47-55, wherein, The third node comprises one or more of: EAS, AF, and application service.

59. The method of any one of claims 47-55, wherein, The fourth node comprises one or more of: AF, ECSP management system.

60. A node finding apparatus characterized by comprising: Comprising: A first receiving unit, configured to receive a first request sent by a second node.

61. A node finding apparatus characterized by comprising: Comprising: A first sending unit, configured to send a first request to a first node.

62. A node finding apparatus characterized by comprising: Comprising: A second receiving unit, configured to receive a second request sent by the first node.

63. A node finding apparatus characterized by comprising: Comprising: A third receiving unit, configured to receive a seventh request sent by a fourth node.

64. A first node, comprising: 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.

65. A second node, comprising: 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.

66. A fourth node, characterized in that, Comprising: A third processor and a third communication interface; wherein The third communication interface is configured to receive a second request sent by the first node.

67. A third node, the third node comprising: 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.

68. 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 according to any one of claims 1 to 24, or the steps of the method according to any one of claims 25 to 34, or the steps of the method according to any one of claims 35 to 46, or the steps of the method according to any one of claims 47 to 59 when running the computer program.

69. A storage medium having stored thereon a computer program, characterized in that The computer program, when executed by the processor, implements the steps of the method according to any one of claims 1 to 24, or the steps of the method according to any one of claims 25 to 34, or the steps of the method according to any one of claims 35 to 46, or the steps of the method according to any one of claims 47 to 59.

70. A computer program product comprising a computer program, characterised in that, The computer program, when executed by the processor, implements the steps of the method according to any one of claims 1 to 59.

Images