Computing power resource acquisition method and apparatus, and terminal and network-side device

Abstract

The present application belongs to the field of wireless communications. Disclosed are a computing power resource acquisition method and apparatus, and a terminal and a network-side device. The computing power resource acquisition method in the embodiments of the present application comprises: a first network element acquiring computing power requirement information requested by a terminal, wherein the computing power requirement information comprises at least one of the following: a target computing power service type, identification information of a target device vendor, or computing power load requirement information; and on the basis of the computing power requirement information, the first network element determining a first computing power resource node that provides a computing power service for the terminal.

Description

Methods, devices, terminals and network-side equipment for acquiring computing resources

[0001] Cross-reference to related applications

[0002] This application claims priority to Chinese Patent Application No. 202411995525.3, filed with the Chinese Patent Office on December 31, 2024, entitled “Method, Apparatus, Terminal and Network Side Device for Acquiring Computing Resources”, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application belongs to the field of wireless communication technology, specifically relating to a method, apparatus, terminal, and network-side equipment for acquiring computing resources. Background Technology

[0004] The computing power network aims to integrate scattered computing resources of different types and locations, including idle computing power from data centers, cloud computing platforms, edge computing nodes, and various smart terminals, to build a new computing architecture that is widely connected, flexibly scheduled, and allocated on demand. Leveraging advanced network technologies such as Software Defined Networking (SDN) and Network Functions Virtualization (NFV), it breaks down geographical limitations and supply bottlenecks of computing resources, enabling virtualization, pooling, and intelligent management of these resources. This allows users to access and use computing resources as conveniently as public resources like water and electricity, flexibly allocating the necessary computing power across the network according to their business needs. This improves the overall efficiency of computing power utilization, reduces computing costs, promotes the innovative development and widespread adoption of the digital economy, drives the digital transformation and intelligent upgrading of various industries, and provides strong support for applications with demanding computing power requirements and complex scenarios, such as intelligent manufacturing, telemedicine, high-definition video processing, and immersive virtual reality.

[0005] Therefore, in wireless communication networks, how to obtain sufficient computing resources is a technical problem that needs to be solved in related technologies. Summary of the Invention

[0006] This application provides a method, apparatus, terminal, and network-side device for acquiring computing resources, which can solve the problem of how to acquire computing resources that meet the requirements.

[0007] In a first aspect, a method for acquiring computing power resources is provided, comprising: a first network element acquiring computing power requirement information requested by a terminal, wherein the computing power requirement information includes at least one of the following: target computing power service type, identification information of target equipment vendor, and computing power load requirement information; and the first network element determining a first computing power resource node for providing computing power services to the terminal based on the computing power requirement information.

[0008] Secondly, a method for acquiring computing resources is provided, comprising: a terminal sending a first request to a second network element, wherein the first request is used to request information about a computing resource node, the computing service request carrying computing power requirement information, the computing power requirement information including at least one of the following: target computing power service type, identification information of a target equipment vendor, and computing power load requirement information; the terminal receiving a third reply message sent by the second network element, wherein the third reply message carries identification information of a first computing resource node.

[0009] Thirdly, a method for acquiring computing resources is provided, comprising: a fourth network element receiving a registration message sent by at least one of the computing resource nodes, wherein the registration message is used to register information of the computing resource nodes.

[0010] Fourthly, a computing power resource acquisition device is provided, comprising: a processing module, configured to: acquire computing power requirement information requested by a terminal, wherein the computing power requirement information includes at least one of the following: target computing power service type, identification information of target equipment vendor, and computing power load requirement information; and determine a first computing power resource node for providing computing power services to the terminal based on the computing power requirement information.

[0011] Fifthly, a computing power resource acquisition device is provided, comprising: a sending module, configured to send a first request to a second network element, wherein the first request is used to request information of a computing power resource node, the computing power service request carrying computing power requirement information, the computing power requirement information including at least one of the following: target computing power service type, identification information of a target equipment vendor, and computing power load requirement information; and a receiving module, configured to receive a third reply message sent by the second network element, wherein the third reply message carries identification information of a first computing power resource node.

[0012] In a sixth aspect, a computing power resource acquisition device is provided, comprising: a receiving module, configured to receive a registration message sent by at least one of the computing power resource nodes, wherein the registration message is used to register information of the computing power resource node.

[0013] In a seventh aspect, a computing power resource acquisition device is provided, the device being configured to perform the steps of the method described in the first aspect, or to implement the steps of the method described in the second aspect, or to implement the steps of the method described in the third aspect.

[0014] Eighthly, a terminal is provided, the terminal including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the second aspect.

[0015] In a ninth aspect, a terminal is provided, including a processor and a communication interface, wherein the processor is configured to perform the steps of the method described in the second aspect, and the communication interface is configured to be coupled to the processor.

[0016] In a tenth aspect, a network-side device is provided, the network-side device including a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method as described in the first aspect, or implementing the steps of the method as described in the third aspect.

[0017] Eleventhly, a network-side device is provided, including a processor and a communication interface, wherein the processor is configured to perform the steps of the method described in the first aspect, or to perform the steps of the method described in the third aspect, and the communication interface is configured to be coupled to the processor.

[0018] In a twelfth aspect, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect, or the steps of the method described in the second aspect, or the steps of the method described in the third aspect.

[0019] In a thirteenth aspect, a wireless communication system is provided, comprising: a first network element, a terminal, and a third network element, wherein the first network element is configured to perform the steps of the method described in the first aspect, the terminal is configured to perform the steps of the method described in the second aspect, and the third network element is configured to perform the steps of the method described in the third aspect.

[0020] In a fourteenth aspect, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being configured to run a program or instructions to implement the steps of the method described in the first aspect, or the steps of the method described in the second aspect, or the steps of the method described in the third aspect.

[0021] In a fifteenth aspect, a computer program / program product is provided, the computer program / program product being stored in a storage medium, the computer program / program product being executed by at least one processor to implement the steps of the method as described in the first aspect, or the steps of the method as described in the second aspect, or the steps of the method as described in the third aspect.

[0022] In this embodiment, the first network element determines a first computing power resource node to provide computing power services to the terminal based on the computing power requirement information requested by the terminal. This allows the terminal to obtain at least one of the computing power resources that meet the target computing power service type, the identification information of the target equipment vendor, and the computing power load requirement information. As a result, the terminal can establish a connection with the first computing power resource node and then realize computing power services through the first computing power resource node. Attached Figure Description

[0023] Figure 1 shows a block diagram of a wireless communication system that can be applied to an embodiment of this application;

[0024] Figure 2 shows a flowchart of a method for acquiring computing resources according to an embodiment of this application;

[0025] Figure 3 shows a flowchart of another method for acquiring computing resources provided in an embodiment of this application;

[0026] Figure 4 shows a flowchart of another method for acquiring computing resources provided in an embodiment of this application;

[0027] Figure 5 shows a timing flowchart of a computing resource acquisition method provided in Embodiment 1 of this application;

[0028] Figure 6 shows a timing flowchart of a computing resource acquisition method provided in Embodiment 2 of this application;

[0029] Figure 7 shows a timing flowchart of a computing resource acquisition method provided in Embodiment 3 of this application;

[0030] Figure 8 shows a schematic diagram of a computing power resource acquisition device provided in an embodiment of this application;

[0031] Figure 9 shows a schematic diagram of another computing power resource acquisition device provided in an embodiment of this application;

[0032] Figure 10 shows a schematic diagram of another computing power resource acquisition device provided in an embodiment of this application;

[0033] Figure 11 shows a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0034] Figure 12 shows a schematic diagram of the hardware structure of a terminal provided in an embodiment of this application;

[0035] Figure 13 shows a schematic diagram of the hardware structure of a network-side device provided in an embodiment of this application;

[0036] Figure 14 shows a schematic diagram of the hardware structure of another network-side device provided in an embodiment of this application. Detailed Implementation

[0037] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0038] The terms "first," "second," etc., used in this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, the first object can be one or more. Furthermore, "or" in this application indicates at least one of the connected objects. For example, the scope of protection for "A or B" covers at least three scenarios: Scenario 1: including A but not B; Scenario 2: including B but not A; Scenario 3: including both A and B. In addition, the terms "A and / or B," "at least one of A and B," and "at least one of A or B" also cover at least the above three scenarios. The character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0039] The term "instruction" in this application can be either a direct instruction (or explicit instruction) or an indirect instruction (or implicit instruction). A direct instruction can be understood as the sender explicitly informing the receiver of specific information, the required operation, or the requested result in the instruction sent. An indirect instruction can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the required operation or requested result based on the judgment result.

[0040] It is worth noting that the technologies described in this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), or other systems. The terms "system" and "network" in this application are often used interchangeably, and the described technologies can be used in the systems and radio technologies mentioned above, as well as in other systems and radio technologies. The following description describes New Radio (NR) systems for illustrative purposes, and the term NR is used in most of the following description; however, these technologies can also be applied to systems other than NR systems, such as 6th Generation (6G) communication systems.

[0041] Figure 1 shows a block diagram of a wireless communication system applicable to an embodiment of this application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can also be referred to as User Equipment (UE), and can be a mobile phone, tablet computer, laptop computer, notebook computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR), virtual reality (VR) device, robot, wearable device, flight vehicle, vehicle user equipment (VUE), shipboard equipment, pedestrian user equipment (PUE), smart home (home devices with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), game console, personal computer (PC), ATM, or self-service machine, etc. Wearable devices include: smartwatches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart chains, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among these, in-vehicle devices can also be referred to as in-vehicle terminals, in-vehicle controllers, in-vehicle modules, in-vehicle components, in-vehicle chips, or in-vehicle units, etc. It should be noted that the specific type of terminal 11 is not limited in this application embodiment. Network-side equipment 12 may include access network equipment or core network equipment, wherein access network equipment may also be referred to as Radio Access Network (RAN) equipment, radio access network function, or radio access network unit. Access network equipment may include base stations, Wireless Local Area Network (WLAN) access points (APs), or Wireless Fidelity (WiFi) nodes, etc.Among them, base stations can be referred to as Node B (NB), Evolved Node B (eNB), Next Generation Node B (gNB), New Radio Node B (NR Node B), Access Point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), Radio Base Station, Radio Transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B, Transmit / Receive Point (TRP), Non-Terrestrial Network (NTN) equipment (such as satellite or high altitude platform stations). The term "base station" can be any suitable term in the field, such as "station" or any other appropriate term in the relevant field, as long as the same technical effect is achieved. The term "base station" is not limited to any specific technical term. It should be noted that the embodiments of this application only use the base station in the NR system as an example for introduction, and do not limit the specific type of base station.

[0042] Core network equipment, also known as core network nodes, core network functions, or core network elements, includes, but is not limited to, at least one of the following: Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (L-NEF), and Binding Support. Functions include BSF, Application Function (AF), Location Management Function (LMF), Gateway Mobile Location Centre (GMLC), Network Data Analytics Function (NWDAF), and Non-Terrestrial Network (NTN) equipment (such as satellite or high altitude platform station).It should be noted that the embodiments of this application only use the core network equipment in the NR system as an example for introduction, and do not limit the specific type of core network equipment. If the name of the core network equipment mentioned in the embodiments of this application changes in subsequent protocol versions (e.g., 6G), it is also within the scope of protection of this application.

[0043] Optionally, the core network equipment can be implemented by one or more functional modules in a single device, or by multiple devices working together; this application does not specifically limit this. It is understood that the aforementioned functional modules can be network elements in hardware devices, software functional modules running on dedicated hardware, or virtualized functional modules instantiated on a platform (e.g., a cloud platform).

[0044] The computing power network aims to integrate scattered computing resources of different types and locations, including idle computing power from data centers, cloud computing platforms, edge computing nodes, and various smart terminals, to build a new computing architecture that is widely connected, flexibly scheduled, and allocated on demand. Leveraging advanced network technologies such as Software-Defined Networking (SDN) and Network Functions Virtualization (NFV), it breaks down geographical limitations and supply bottlenecks of computing resources, enabling virtualization, pooling, and intelligent management of these resources. This allows users to access and use computing resources as conveniently as public resources like water and electricity, flexibly allocating the necessary computing power across the network according to their business needs. This improves the overall efficiency of computing power utilization, reduces computing costs, promotes the innovative development and widespread adoption of the digital economy, drives the digital transformation and intelligent upgrading of various industries, and provides strong support for applications with demanding computing power requirements and complex scenarios, such as intelligent manufacturing, telemedicine, high-definition video processing, and immersive virtual reality.

[0045] However, in wireless communication networks, how to acquire sufficient computing resources is a technical problem that needs to be solved. For example, when 6G networks are deployed in the future, the 6G network (core network control node) may not have full control over computing applications and resources. That is, 6G network nodes cannot negotiate and communicate every computing demand parameter (such as latency and computing server) with computing consumers. Under such conditions, how the core network control node can provide consumers with computing services that meet their requirements is a technical problem that needs to be solved.

[0046] To address the aforementioned technical issues, this application provides a computing resource acquisition scheme, enabling the network to select suitable computing resource nodes for the terminal.

[0047] The computing resource acquisition scheme provided in this application will be described in detail below with reference to the accompanying drawings and through some embodiments and application scenarios.

[0048] Figure 2 shows a flowchart of a method for acquiring computing resources according to an embodiment of this application. This method 200 can be executed by a first network element. In other words, the method can be executed by software or hardware installed on the first network element. As shown in Figure 2, the method may include the following steps.

[0049] S210, the first network element obtains the computing power requirement information requested by the terminal, wherein the computing power requirement information includes at least one of the following: target computing power service type, target equipment vendor identification information, and computing power load requirement information.

[0050] In this embodiment of the application, the first network element can be a network element or node with computing power control function, such as a computing power control node or a 6G computing power control node.

[0051] In this embodiment, the computing power requirement information requested by the terminal may carry at least one of the following: target computing power service type, target equipment vendor identification information, and computing power load requirement information. The target computing power service type may indicate the type of computing power service requested by the terminal, such as Extended Reality (XR), Artificial Intelligence (AI), or Autonomous Driving. The target equipment vendor identification information indicates the identifier of the equipment vendor providing the computing power service requested by the terminal. The computing power load requirement information indicates the computing power load status of the computing power resource node (or application server (AS)) desired by the terminal, which may be represented by a computing power load level (e.g., high, medium, or low) or the actual load (percentage figure).

[0052] In some embodiments of this application, the first network element obtaining the computing power requirement information requested by the terminal may include: the first network element receiving a first request from the terminal, and obtaining the computing power requirement information based on the first request.

[0053] In one implementation, the first request may carry the aforementioned computing power requirement information, and the first network element may obtain the aforementioned computing power requirement information from the first request.

[0054] In another implementation, the first request may not carry the aforementioned computing power requirement information. The first network element may obtain the computing power requirement information based on the terminal's subscription information after receiving the first request.

[0055] In another implementation, the first request may carry some of the aforementioned computing power requirement information. The first network element can obtain the computing power requirement information based on the first request and the terminal's subscription information. For example, the first request may carry one or more of the following: target computing power service type, target equipment vendor identification information, and computing power load requirement information. For instance, the terminal may pre-subscribe to the computing power service type it may use. In this case, the first request may not carry the target computing power service type, and the computing power service type requested by the terminal is the computing power service type subscribed to by the terminal.

[0056] In some embodiments, the computing power requirement information may include one or more of the following: target computing power service type, target equipment vendor identification information, and computing power load requirement information. For example, the computing power requirement information may not include the target equipment vendor identification information. In this case, the terminal may not limit the equipment vendor providing the computing power service, as long as the computing power resources provided by that equipment vendor can meet the target computing power service type or computing power load requirement information. As another example, the computing power requirement information may also not carry computing power load requirement information. In this case, the terminal may not limit the computing power load status of the computing power resource nodes providing the computing power service.

[0057] In some embodiments, the first request received by the first network element from the terminal may include: a first request sent by the first network element receiving terminal, that is, the first request received by the first network element may come directly from the terminal. For example, the address information of the first network element, such as the IP address or FQDN of the first network element, can be pre-configured in the terminal. The terminal can send the first request to the first network element through the user plane based on the configured address information of the first network element. This first request may be a computing power service request. Therefore, in these embodiments, optionally, the first request sent by the first network element receiving terminal may include: a first request sent by the first network element receiving terminal through the user plane. For example, the terminal sends the first request to the first network element through the radio access network and UPF.

[0058] In the above embodiments, the terminal may also send a first request to the first network element through control. For example, the terminal sends the first request to the first network element through the radio access network and AMF, or the terminal sends the first request directly to the first network element through the radio access network.

[0059] In other embodiments, the first request received by the first network element from the terminal may include: the first network element receiving a first request sent by the access node. In these embodiments, the access node may be a 6G access node, such as at least one of a Radio Access Network (RAN) device, a 6G Access and Mobility Management (AM) network element, a 6G Session Management (SM) network element, and a 6G Mobility Management (MM) network element. In these embodiments, when the terminal initiates a computing power service request, it may directly send the computing power service request to the core network. The computing power service request may carry at least one of the following: the target computing power service type, the identification information of the target equipment vendor, and computing power load requirement information. After receiving the computing power service request, the core network access node sends the first request to the first network element.

[0060] In the above embodiments, optionally, the first request may carry the terminal's identification information. For example, after receiving the terminal's computing power service request, the access node may select a computing power control node (i.e., the first network element) and send the first request to the first network element, which carries the terminal's identification information, the target computing power service type, the target equipment vendor's identification information, and the computing power load requirement information.

[0061] In one embodiment of the above examples, the access node can select the first network element based on the computing power service types supported by the computing power control node. For example, the access node can query the NRF or make the selection locally. When querying the NRF, the computing power control node has already registered its supported computing power service type information with the NRF before the query, that is, it sends a registration message, which carries the computing power service type information supported by the computing power control node.

[0062] In another embodiment of the above embodiments, the access node can select the computing power control node based on the terminal's subscription. For example, there are multiple computing power control nodes in the network. Computing power control node A can provide computing power control services for subscribed user group A, and computing power control node B can provide computing power control services for subscribed user group A. Therefore, the access node can select the computing power control node according to the terminal's subscription group.

[0063] In some embodiments, after receiving a computing power service request from a terminal, the access node can check the terminal's subscription information to determine whether the terminal authorizes the use of the requested target computing power service type and the target equipment vendor corresponding to the requested target equipment vendor identification information. Optionally, the access node can interact with the UDM to obtain the UE's subscription information. If the terminal supports at least one of the requested target computing power service type and the target equipment vendor identification information, the access node further selects a computing power control node (i.e., the first network element). If the UE does not support the requested target computing power service type or the target equipment vendor identification information, the access node can directly send a reply message to the terminal. This reply message carries a rejection indication and may optionally carry a rejection reason, such as not supporting the target computing power service type or not supporting the target equipment vendor identification information.

[0064] In some embodiments, the access node and the computing power control node can be combined into one, which is the first network element in this application. Therefore, in these embodiments, the first network element receiving the first request from the terminal may include: the first network element receiving the first request sent by the terminal. For example, when the terminal needs computing power services, it can directly send the first request to the core network. For example, the terminal sends the first request through a Non-Access Stratum (NAS) message, and the first network element receives the first request sent by the terminal through a NAS message.

[0065] In some embodiments, the first request may also carry identification information of the second computing resource node. The second computing resource node may be a computing resource node recommended by the terminal. For example, if the terminal pre-configures or obtains information about the second computing resource node from a third-party application, such as at least one of an application ID and address information, the first request may also carry at least one of the application ID and address information of the second computing resource node. The address information may be an IP address or a fully qualified domain name (FQDN).

[0066] S212, the first network element determines the first computing power resource node to provide computing power services to the terminal based on the computing power requirement information.

[0067] In this embodiment, the first network element can determine a first computing power resource node that provides computing power services to the terminal based on computing power requirement information. For example, if the computing power requirement information includes a target computing power service type, the first network element can select a first computing power resource node that can provide the target computing power service type for the terminal. If the first request carries the identification information of a target equipment vendor, the first network element can select a first computing power resource node provided by the equipment vendor corresponding to the identification information, that is, the identification information of the equipment vendor of the first computing power resource node is the same as the identification information of the target equipment vendor. If the computing power requirement information includes computing power load requirement information, the first network element can select a first computing power resource node whose load status matches the computing power load requirement information for the terminal. If the computing power requirement information includes multiple items such as the target computing power service type, the identification information of the target equipment vendor, and the computing power load requirement information, the first network element can select a first computing power resource node that matches multiple items such as the target computing power service type, the identification information of the target equipment vendor, and the computing power load requirement information included in the computing power requirement information for the terminal.

[0068] In this embodiment of the application, the first computing resource node can be one or more.

[0069] In some embodiments, in S212, the first network element can select a first computing resource node based on a first request and information of at least one computing resource node stored locally, wherein the at least one computing resource node includes the first computing resource node. In these embodiments, the first network element can locally store information of at least one computing resource node. Optionally, the information of the computing resource node may include at least one of the following: the computing service type of the computing resource node, the identification information of the equipment vendor corresponding to the computing resource node (e.g., vendor ID), the application identifier corresponding to the computing resource node (e.g., application ID), the address information of the computing resource node, the computing load information of the computing resource node, and the time period associated with the computing resource node. The time period associated with the computing resource node can be used to indicate the resource load of the computing resource node during certain time periods. For example, a high resource load period: Friday evening 10:00-12:00; a resource load period above 80%: Saturday noon 10:00-12:00; a low resource load period: Monday afternoon 14:00-18:00.

[0070] In some embodiments, the information of the aforementioned computing power resource nodes stored locally in the first network element may be pre-configured in the first network element, that is, the information of at least one of the aforementioned computing power resource nodes is stored in the first network element by configuration.

[0071] In other embodiments, the information of the aforementioned computing resource nodes stored locally in the first network element can be stored in the first network element through registration by the computing resource nodes. In these embodiments, the method may further include the following step: the first network element receives a registration message sent by the first computing resource node, wherein the registration message is used to register the information of the first computing resource node. In these embodiments, the computing resource nodes can register with the first network element, enabling the first network element to obtain the information of the computing resource nodes.

[0072] Optionally, the information of the aforementioned computing resource nodes may include at least one of the following:

[0073] 1) The computing power service type of the computing power resource node; for example, the computing power service type of the computing power resource node is one or more of the following service types: XR, AI, or autonomous driving.

[0074] 2) The identification information of the equipment vendor corresponding to the computing power resource node;

[0075] 3) The application ID corresponding to the computing resource node; representing the identifier of the application that provides computing power services to the computing resource node.

[0076] 4) The address information of the computing power resource node; wherein, the address information may include one or more of the following: IP address, FQDN, etc.

[0077] 5) The computing load information of the computing resource nodes; such as the actual load (percentage figure) and computing load level (e.g., high, medium, low) of the computing resource nodes;

[0078] 6) The time period associated with the computing power resource node. This time period can be used to indicate the computing load information of the computing power resource node in different time periods. For example, the time period with high resource load is: Friday evening 10:00-12:00; the time period with resource load above 80% is: Saturday noon 10:00-12:00; and the time period with low resource load is: Monday afternoon 14:00-18:00.

[0079] In some embodiments, the method may further include: a first network element initiating a subscription message to a computing resource node, the subscription message being used to subscribe to one or more of the aforementioned information of the computing resource node, for example, the subscription message being used to subscribe to the aforementioned information items 1)-6) of the computing resource node, or the subscription message being used to subscribe to a portion of the aforementioned information items 1)-6) of the computing resource node, for example, the subscription message being used to subscribe to the computing load information of the computing resource node, in which case the computing resource node may send the computing load information of the computing resource node to the first network element when the computing load information changes.

[0080] In some implementations, the registration message sent by the computing resource node can be a request-response, a periodic notification, or an event-triggered notification. For example, the computing resource node periodically reports its resource load to the first network element, notifying it at agreed-upon intervals; or, based on event triggering, the computing resource node notifies the first network element when its load exceeds 60% or when its load level is high. In one implementation, the first network element can first subscribe to the computing resource node's information, including its load status. This allows the computing resource node to promptly notify the first network element of its computing load status based on the subscription conditions (e.g., periodic notification requirements, condition-triggered notification requirements), enabling the first network element to understand the real-time load of each computing resource node and allocate computing resources more efficiently.

[0081] In some embodiments, a computing resource node may register its information with a third network element. S212 may include the following steps:

[0082] Step 1: The first network element obtains information about at least one computing power resource node from the third network element, wherein the at least one computing power resource node includes the first computing power resource node.

[0083] Step 2: Based on the first request, the first network element selects the first computing power resource node from the at least one computing power resource node.

[0084] In the above embodiments, the computing power resource node can register its information with the third network element, and the first network element can obtain the information of at least one computing power resource node from the third network element. For example, after receiving the first request, the first network element can send a computing power query request to the third network element, and after receiving the computing power query request, the third network element can return the information of at least one computing power resource node to the first network element.

[0085] In other embodiments, the first network element can send the aforementioned computing power requirement information to the third network element. The third network element can select at least one first computing power resource node that matches the aforementioned computing power requirement information from its locally stored computing power resource nodes, and return the identification information of the at least one first computing power resource node to the first network element. That is, in these embodiments, the third network element can select the computing power resource node to be provided to the terminal and notify the first network element.

[0086] In the above embodiments, the third network element can be a network element with network storage function, for example, the third network element can be an NRF.

[0087] Optionally, the information of the computing resource nodes in the above embodiments may include at least one of the following:

[0088] 1) The computing power service type of the computing power resource node; for example, the computing power service type of the computing power resource node is one or more of the following service types: XR, AI, or autonomous driving.

[0089] 2) The identification information of the equipment vendor corresponding to the computing power resource node;

[0090] 3) The application ID corresponding to the computing resource node; representing the identifier of the application that provides computing power services to the computing resource node.

[0091] 4) The address information of the computing power resource node; wherein, the address information may include one or more of the following: IP address, FQDN, etc.

[0092] 5) The computing load information of the computing resource nodes; such as the actual load (percentage figure) and computing load level (e.g., high, medium, low) of the computing resource nodes;

[0093] 6) The time period associated with the computing power resource node. This time period can be used to indicate the computing load information of the computing power resource node in different time periods. For example, the time period with high resource load is: Friday evening 10:00-12:00; the time period with resource load above 80% is: Saturday noon 10:00-12:00; and the time period with low resource load is: Monday afternoon 14:00-18:00.

[0094] In some embodiments, the first network element may select a computing resource node that matches the information carried in the first request. For example, suppose the information of at least one computing resource node is:

[0095] {Computing resource node A; application ID; AS address; Supported computing service types: AI, XR, autonomous driving; vendor ID belongs to vendor A; Current load level is high};

[0096] {Computing resource node B; application ID; AS address; Supported computing service types: AI, XR; vendor ID belongs to vendor B; Current computing load level is high};

[0097] {Computing resource node C; application ID; AS address; Supported computing service type: XR; vendor ID belongs to vendor B; Current computing load is 10%};

[0098] If the target computing power service type requested by the terminal is autonomous driving, and no target vendor ID is carried, the first network element finds that only A meets the target computing power service type requirements, and then selects computing power resource node A to provide services to the UE.

[0099] When the target computing power service type requested by the terminal is AI, and the required target vendor ID belongs to vendor B, the first network element queries whether the target computing power service type requirement is met by both computing power resource nodes A and B. However, if it is further determined that only computing power resource node B meets the target vendor ID requirement, then computing power resource node B is selected to provide computing power service to the UE.

[0100] When the target computing power service type requested by the UE is XR type, and the required target vendor ID belongs to vendor B, the first network element determines that computing power resource nodes A, B, and C all meet the requirements of the target computing power service type. However, it further determines that only computing power nodes B and C meet the requirements of the target vendor ID. Therefore, the first network element can select one or more nodes based on local rules. In one implementation, the computing power control node can select based on computing power load information, prioritizing computing power resource nodes with lower computing power loads, i.e., computing power resource node B provides computing power services to the UE.

[0101] In some embodiments, if the first network element cannot select a computing power resource node that matches the information carried in the first request, it can select the default computing power resource node to provide computing power services to the terminal. Alternatively, the first network element can reply with a reply message carrying a rejection indication, for example, by sending a reply message to the terminal or access node. The reply message may also carry a rejection reason, such as not supporting the target computing power service type, not supporting the target equipment vendor, or computing power congestion.

[0102] In some embodiments, prior to S212, the method may further include: a first network element determining, based on the terminal's subscription information, that the terminal is authorized to use computing resources corresponding to at least one of the target computing power service type and the target equipment vendor's identification information. For example, the first network element may interact with the UDM to obtain the terminal's subscription information. If the terminal supports the requested target computing power service type or the requested target equipment vendor's identification information, the first network element executes S212 to select computing power resources based on the first request. If the terminal does not support the requested target computing power service type or the requested target equipment vendor's identification information, the first network element may reply with a reply message carrying a rejection indication, for example, replying to the access node or the terminal with a reply message carrying a rejection indication. Optionally, the reply message may also carry a rejection reason (e.g., not supporting the target computing power service type or not supporting the target equipment vendor's identification information).

[0103] In some embodiments, when the first request carries identification information of the second computing power resource node, the first computing power resource node selected by the first network element may be the same as or different from the second computing power resource node. That is, the first network element may directly select the second computing power resource node, or it may select a computing power resource node that matches at least one of the target computing power service type, target equipment vendor identification information, and computing power load requirement information carried in the first request. The selected computing power resource node may or may not be the second computing power resource node. For example, if the information of the second computing power resource node does not match at least one of the target computing power service type, target equipment vendor identification information, and computing power load requirement information carried in the first request, the first network element may select another computing power resource node that matches at least one of these three information. Optionally, if the second computing power resource node matches at least one of the target computing power service type, target equipment vendor identification information, and computing power load requirement information carried in the first request, the first network element may preferentially select the second computing power resource node to provide computing power services to the terminal.

[0104] In some embodiments, after S212, the method may further include: the first network element sending a second request to the first computing power resource node, wherein the second request carries the identification information of the terminal and the target computing power service type.

[0105] In the above embodiments, after the first network element selects a first computing power resource node for the terminal, it sends a second request to the first computing power resource node, requesting the first computing power resource node to provide computing power services for the terminal.

[0106] In some embodiments, after the first network element sends a second request to the first computing resource node, the method may further include: the first network element receiving a first reply message sent by the first computing resource node. In one embodiment, the first reply message may carry the terminal's identification information and the first computing resource node's identification information; in another embodiment, the first reply message may carry the terminal's identification information and indication information instructing the first computing resource node to accept the second request. The first reply message can indicate to the first network element that the first computing resource node has accepted the second request.

[0107] Optionally, in the above embodiments, the identification information of the first computing power resource node may include the address information or application identifier of the first computing power resource node.

[0108] In some embodiments, after S210, the method may further include: the first network element sending a second response message to the terminal, wherein the second response message carries identification information of the first computing power resource node. Through the second response message, the identification information of the first computing power resource node can be indicated to the terminal, thereby enabling the terminal to establish a connection with the first computing power resource node based on the identification information, and then negotiate computing power parameters, such as negotiating at least one of communication latency, transmission rate, and computing power processing latency with the first computing power resource node to establish and execute a computing power task.

[0109] Through the technical solutions provided in the embodiments of this application, the first request of the terminal carries at least one of the following: target computing power service type, identification information of the target equipment vendor, and computing power load requirement information. After receiving the first request, the first network element selects a first computing power resource node for the terminal based on the first request, and sends a second request carrying the terminal's identification information and the target computing power service type to the first computing power resource node. This allows the terminal to obtain computing power resources that meet at least one of the target computing power service type, identification information of the target equipment vendor, and computing power load requirement information, enabling the terminal to establish a connection with the first computing power resource node and then realize computing power services through the first computing power resource node.

[0110] Figure 3 illustrates a flowchart of another method for acquiring computing resources according to an embodiment of this application. This method 300 can be executed by a terminal. In other words, the method can be executed by software or hardware installed on the terminal. As shown in Figure 3, the method may include the following steps.

[0111] S310, the terminal sends a first request to the second network element, wherein the first request is used to request information about the computing power resource node, and the computing power service request carries computing power requirement information, which includes at least one of the following: target computing power service type, target equipment vendor identification information, and computing power load requirement information.

[0112] In some embodiments, the second network element can be an access node, and the terminal sending a first request to the second network element may include: the terminal sending a first request to the access node. For example, as described in method 200 above, when the access node and the computing power control node are deployed separately, if the terminal does not have pre-configured address information of the computing power control node, the terminal may send a first request to the core network, and the access node of the core network receives the first request.

[0113] In other embodiments, the second network element can be a computing power control node, and the terminal sending a first request to the second network element may include: the terminal sending a first request to the computing power control node based on pre-configured address information of the computing power control node. For example, if the terminal has pre-configured address information of the computing power control node, the terminal can send the first request to the computing power control node through the user.

[0114] In some other embodiments, the access node and the computing power control node may be set up as one unit. In these cases, the terminal can send a first request to the first network element (i.e., the access node and the computing power control node set up as one unit).

[0115] In some embodiments, if the terminal has pre-configured or obtained identification information of the second computing power node, such as at least one of an application ID and address information, the first request may also carry at least one of the application ID and address information of the second computing power resource node. The address information may be an IP address or a fully qualified domain name (FQDN).

[0116] S312, the terminal receives a third reply message sent by the second network element, wherein the third reply message carries the identification information of the first computing power resource node.

[0117] In this embodiment of the application, the terminal can obtain the identification information of the first computing power resource node from the third reply message, thereby enabling the terminal to interact with the first computing power resource node based on the identification information, and thus complete the computing power task.

[0118] Optionally, the identification information of the first computing power resource node may include at least one of the application identifier of the first computing power resource node and the address information of the first computing power resource node. The address information may be an IP address or a fully qualified domain name (FQDN).

[0119] It should be noted that the first computing resource node and the second computing resource node may be the same node or they may be different nodes.

[0120] In some embodiments, when the second network element is an access node, the third reply message may be a third reply message sent by the access node to the terminal based on the second reply message sent by the first network element in the above method 200. For example, the access node determines that the first computing power resource node is the computing power resource node selected by the network side for the computing power request of the terminal based on the terminal's identification information and the identification information of the first computing power resource node carried in the second reply message, and then sends the third reply message to the terminal.

[0121] In other embodiments, when the second network element is a computing power control node, or a combined access node and computing power control node, the third reply message can be the second reply message sent by the first network element in the above method 200.

[0122] The technical solution provided in this application embodiment allows the terminal to send a first request to the second network element, which carries at least one of the following: target computing power service type, target equipment vendor identification information, and computing power load requirement information. This enables the network-side device to select a first computing power resource node for the terminal and obtain computing power resources for the terminal after receiving the first request, thereby enabling the terminal to establish a connection with the first computing power resource node and realize computing power services through the first computing power resource node.

[0123] In some embodiments, after S312, the method may further include: the terminal negotiating computing power parameters with the first computing power resource node based on the identification information of the first computing power resource node, wherein the computing power parameters include at least one of the following: communication latency, transmission rate, and computing power processing latency. In these embodiments, after receiving the identification information of the first computing power resource node, the terminal can negotiate fine-grained computing power service requirements with the first computing power resource node to establish and execute computing power tasks. Optionally, the terminal can further negotiate computing power tasks with the first computing power resource node through control plane signaling or through the user plane (e.g., IP packets), thereby enabling the terminal to complete computing power tasks through the first computing power resource node.

[0124] Figure 4 shows a flowchart of another computing resource acquisition method according to an embodiment of this application. This method 400 can be executed by a fourth network element. In other words, the method can be executed by software or hardware installed on the fourth network element. As shown in Figure 4, the method may include the following steps.

[0125] S410, the fourth network element receives a registration message sent by at least one computing resource node, wherein the registration message is used to register the information of the computing resource node.

[0126] In this embodiment, the fourth network element can be either the first or third network element in method 200 described above. For example, the fourth network element can be a computing power control node, meaning that computing power resource nodes can directly register with the computing power control node. Alternatively, the fourth network element can be an NRF, meaning that computing power resource nodes register with the NRF.

[0127] Optionally, the information of the computing power resource node includes at least one of the following:

[0128] 1) The computing power service type of the computing power resource node; for example, the computing power service type of the computing power resource node is XR, AI or autonomous driving, etc.

[0129] 2) The identification information of the equipment vendor corresponding to the computing power resource node;

[0130] 3) The application ID corresponding to the computing resource node; representing the identifier of the application that provides computing power services to the computing resource node.

[0131] 4) The address information of the computing power resource node; wherein, the address information may include one or more of the following: IP address, FQDN, etc.

[0132] 5) The computing load information of the computing resource nodes; such as the actual load (percentage figure) and computing load level (e.g., high, medium, low) of the computing resource nodes;

[0133] 6) The time period associated with the computing power resource node. This time period can be used to indicate the computing load information of the computing power resource node in different time periods. For example, the time period with high resource load is: Friday evening 10:00-12:00; the time period with resource load above 80% is: Saturday noon 10:00-12:00; and the time period with low resource load is: Monday afternoon 14:00-18:00.

[0134] In some embodiments, the method may further include the following steps:

[0135] Step 1: The fourth network element receives a computing power query request sent by the first network element, wherein the computing power query request is used to request information about computing power resource nodes;

[0136] Step 2: The fourth network element sends the information of the at least one computing resource node to the first network element.

[0137] In the above embodiments, the fourth network element can be an NRF, and the first network element can be a computing power control node. After receiving a computing power service request from the terminal, such as the first request mentioned above, the first network element can send a computing power query request to the fourth network element to obtain information on at least one computing power resource node.

[0138] In some embodiments, the method may further include: the fourth network element initiating a subscription message to the computing resource node, the subscription message being used to subscribe to one or more of the aforementioned information of the computing resource node, for example, the subscription message being used to subscribe to the aforementioned information items 1)-6) of the first computing resource node, or the subscription message being used to subscribe to some of the aforementioned information items 1)-6) of the computing resource node, for example, the subscription message being used to subscribe to the computing load information of the computing resource node, in which case the computing resource node may send the computing load information of the computing resource node to the fourth network element when the computing load information changes.

[0139] In some implementations, the registration message sent by the computing resource node can be a request-response, a periodic notification, or an event-triggered notification. For example, the computing resource node periodically reports its resource load to the fourth network element, notifying it at agreed-upon intervals; or, for instance, the computing resource node notifies the fourth network element based on event-triggered notifications, such as when its load exceeds 60% or when its load level is high. In one implementation, the fourth network element can first subscribe to the computing resource node's information, including its load status. This allows the computing resource node to promptly notify the fourth network element of its computing load status based on subscription conditions (e.g., periodic notification requirements, condition-triggered notification requirements), enabling the fourth network element to understand the real-time load of each computing resource node and allocate computing resources more efficiently.

[0140] The following uses a 6G system as an example to illustrate the technical solution provided in the embodiments of this application.

[0141] Example 1

[0142] In this embodiment, the computing resource node registers its information with the computing control node or the 6G NRF. The UE sends a computing service request to the 6G access node, the 6G access node selects the computing control node, and the computing control node selects the computing resource node according to the computing service type.

[0143] Figure 5 shows a timing flowchart of the computing resource acquisition method provided in this embodiment. As shown in Figure 5, the method mainly includes the following steps:

[0144] S501a, the computing resource node sends a first message to the fourth network element (i.e., the computing control node), the first message being used to register the information of the computing resource node.

[0145] S501b, the fourth network element (i.e., 6G NRF) of the computing power resource node sends a first message, which is used to register the information of the computing power resource node.

[0146] S501a and S501b are two parallel schemes.

[0147] The first message may include at least one of the following pieces of information about the computing resource node:

[0148] 1) Computing power service type, used to indicate the type of computing power service provided by the computing power resource node, such as XR, AI, autonomous driving, etc.;

[0149] 2) Vendor ID, used to indicate the identification information of the equipment vendor corresponding to the computing power resource node;

[0150] 3) Application ID, used to indicate the application identifier corresponding to the computing power service provided by the computing power resource node;

[0151] 4) Address information, used to indicate the address information of computing resource nodes, including IP address and FQDN, etc.;

[0152] 5) Resource load information, used to indicate the computing load status of computing resource nodes, such as the actual load of computing services (e.g., the percentage of computing services currently occupied) or computing load level (e.g., high, medium, low).

[0153] 6) Time periods associated with resource load, for example, high resource load time period: Friday evening 10:00-12:00; resource load time period above 80%: Saturday noon 10:00-12:00; low resource load time period: Monday afternoon 14:00-18:00.

[0154] It should be noted that in this embodiment, if S501a is used, the computing power resource node (or computing power AS) registers with the computing power control node. That is, without 6G NRF, the subsequent S507 in this embodiment is skipped. After receiving the registration information of S501a, the computing power control node selects a suitable computing power resource node based on the information of the registered computing power resource node received.

[0155] It should be noted that S501a and S501b can be optional steps. For example, they can be implemented by pre-configuring them in the fourth network element. That is, the information of the registered computing resource nodes can be stored in the fourth network element through configuration.

[0156] It should also be noted that the registration information of computing resource nodes can be completed through 6G NRF registration signaling, and can be a single request and response, or a periodic notification or event-triggered notification. For example, a computing resource node periodically reports its resource load to the fourth network element, notifying it at agreed-upon intervals; or, for example, a computing resource node notifies the fourth network element based on event-triggered notification, notifying the fourth network element when its load exceeds 60%, or when its load level is high. In one implementation, the fourth network element can first initiate a subscription message to the computing resource nodes, subscribing to their information, including load status. This allows the computing resource nodes to promptly notify the first network element of their computing load status based on the subscription conditions (e.g., periodic notification requirements, condition-triggered notification requirements), enabling the fourth network element to understand the real-time load of each computing resource node and allocate computing resources more efficiently.

[0157] S502, the terminal sends a second message to the 6G access node, which is used to request information about the computing resource node.

[0158] The 6G access node can be at least one of 6G AM, 6G SM and 6G MM.

[0159] Optionally, the second message may include at least one of the following parameters:

[0160] 1) Types of computing power services, such as XR, AI, and autonomous driving services;

[0161] 2) Vendor ID, representing the equipment vendor's identification information;

[0162] 3) Computing load requirements, used to represent the expected computing load status of computing resource nodes, such as using the aforementioned computing load level or actual service load (percentage figure).

[0163] It should be noted that if the terminal has pre-configured or obtained information about the computing power server from a third-party application, such as at least one of the application ID or address information, the second message can also carry the application ID and the address information of the computing power resource node to the 6G access node, so that the 6G access node can select according to the application ID or address information.

[0164] The S503 6G access node checks the UE's subscription information to determine whether the UE is authorized to use the requested computing power service type or the requested vendor ID.

[0165] The 6G access node can interact with the 6G UDM to obtain the UE's subscription information. If the UE supports the requested computing power service type (i.e., the computing power service type in the second message) or the requested vendor ID (i.e., the vendor ID in the second message), the 6G access node executes S504 to further select a computing power control node; if the UE does not support the requested computing power service type (i.e., the computing power service type in the second message) or the requested vendor ID (i.e., the vendor ID in the second message), the 6G access node directly sends a reply message to the UE (S512). The reply message carries a rejection indication, and optionally, the reply message may also carry a rejection reason (e.g., not supporting the computing power service type, not supporting the vendor ID).

[0166] S503 is an optional step. The 6G access node can also directly execute S504 without determining whether the UE is authorized to use the requested computing power service type or the requested vendor ID.

[0167] S504, 6G access node selects computing power control node.

[0168] In one implementation, the 6G access node can select a computing power control node based on the computing power service type in the second message. For example, if multiple computing power control nodes exist in the network, computing power control node A can support the control and management of AI-type computing power services, while computing power control node B can support the control and management of XR-type computing power services. Therefore, the 6G access node can select based on the computing power service types supported by the computing power control nodes. The 6G access node can query the NRF or make the selection using local configuration. When querying the NRF, the computing power control node has already registered its supported computing power service type information with the NRF before the query, i.e., it sends a registration message carrying the computing power service type information supported by the computing power control node.

[0169] In another implementation, the 6G access node selects the computing power control node based on the UE's subscription. For example, if multiple computing power control nodes exist in the network, computing power control node A can provide computing power control services to subscribed user group A, and computing power control node B can also provide computing power control services to subscribed user group A. Therefore, the 6G access node can select the computing power control node according to the UE's subscription group. The 6G access node can query the NRF or perform the selection based on its local configuration.

[0170] S505, the 6G access node sends a computing power service request to the computing power control node.

[0171] The computing power service request may include at least one of the following:

[0172] 1) UE identification information, such as 6G Globally Unique Temporary Identifier (GUTI) and 6G Generic Public Subscription Identifier (GPSI);

[0173] 2) Types of computing power services, such as XR, AI, and autonomous driving services;

[0174] 3) Vendor ID, which represents the equipment vendor's identification information.

[0175] S506, the computing power control node checks the UE's subscription information to determine whether the UE authorizes the use of the requested computing power service type or the requested vendor ID.

[0176] Optionally, the computing power control node can interact with the 6G UDM to obtain the UE's subscription information. If the UE supports the requested computing power service type (i.e., the computing power service type in the computing power service request) or the requested vendor ID (i.e., the vendor ID in the computing power service request), the computing power control node executes S507 to select computing power resources based on the computing power service type; if the UE does not support the requested computing power service type (i.e., the computing power service type in the computing power service request) or the requested vendor ID (i.e., the vendor ID in the computing power service request), the computing power control node directly sends a reply message (S511) to the 6G access node. This reply message carries a rejection indication. Optionally, the reply message may also carry a rejection reason (e.g., not supporting the computing power service type, not supporting the vendor ID).

[0177] S503 is an optional step.

[0178] It should be noted that both S503 and S506 check the UE's subscription information, and one can choose to execute either one: S503 can be executed without S506, where S503 checks whether the UE supports the requested computing power service type and vendor ID; or S503 can be executed without S503, where S506 checks whether the UE supports the requested computing power service type and vendor ID. Alternatively, both S503 and S506 can be executed. In one implementation, S503 checks whether the UE supports the requested computing power service type, and S506 checks whether the UE supports the requested vendor ID. In another implementation, both S503 and S506 are executed, where S503 checks whether the UE supports the computing power service, and S506 performs a fine-grained check to verify whether the UE supports either the requested computing power service type or the vendor ID.

[0179] S507, when the computing resource node registers its information with the 6G NRF, that is, when all computing resource information is stored in the NRF, the computing control node obtains the computing resource node's information from the NRF.

[0180] For example, the computing power control node can send computing power query information to the NRF, which includes computing power service type and vendor ID, etc. The 6G NRF returns information about one or more computing power resource nodes to the computing power control node, and the information about the computing power resource nodes may include the content of the first message of computing power resource node registration in S501b.

[0181] S508, the computing power control node selects computing power resource nodes based on the computing power service type.

[0182] Optionally, the computing power control node can be selected based on the request parameters in the second message.

[0183] If a suitable computing power resource node cannot be selected, the default computing power resource node can be selected to provide services, or the computing power control node can directly send a reply message (S511) to the 6G access node. This reply message carries a rejection indication. Optionally, the reply message can also carry a rejection reason (such as not supporting computing power service type, not supporting vendor ID, or computing power congestion).

[0184] For example, suppose the information about the computing resource nodes stored in the 6G NRF includes:

[0185] {Computing resource node A; application ID; AS address; Supported computing service types: AI, XR, autonomous driving; vendor ID belongs to vendor A; Current load level is high};

[0186] {Computing resource node B; application ID; AS address; Supported computing service types: AI, XR; vendor ID belongs to vendor B; Current computing load level is high};

[0187] {Computing resource node C; application ID; AS address; Supported computing service type: XR; vendor ID belongs to vendor B; Current computing load is 10%};

[0188] When the UE requests a computing power service type of autonomous driving and does not carry a vendor ID, the computing power control node can query through NRF that only A meets the computing power service type requirements, and then selects computing power resource node A to provide services to the UE.

[0189] When the computing power service type requested by the UE is AI, and the required vendor ID belongs to vendor B, the computing power control node can query through NRF that both computing power resource nodes A and B meet the requirements of the computing power service type. However, if it is further determined that only computing power resource node B meets the vendor ID requirements, then computing power resource node B is selected to provide computing power services to the UE.

[0190] When the UE requests a computing power service of type XR and the required vendor ID belongs to vendor B, the computing power control node determines by querying the NRF that computing power resource nodes A, B, and C all meet the requirements. However, it further determines that only computing power nodes B and C meet the vendor ID requirement. Therefore, the computing power control node can select one or more based on local rules. In one approach, the computing power control node selects based on computing power load information, prioritizing computing power resource nodes with lower computing power loads, i.e., computing power resource node B provides computing power services to the UE.

[0191] S509, the computing power control node sends a computing power task request to the computing power resource node. The computing power task request may include: UE identification information and computing power service type.

[0192] S510, the computing resource node accepts the computing task request and replies to the computing control node with a computing task reply message. Optionally, the computing task reply message may carry UE identification information, the address information of the computing resource node, and the application ID of the computing resource node.

[0193] S511, the computing power control node sends a computing power service response message to the 6G access node. The computing power response message may include UE identification information, address information of computing power resource nodes, or application ID.

[0194] S512, the 6G access node sends a third message to the UE, which carries the address information or application ID of the computing resource node.

[0195] In step S513, using the received address information or application ID of the computing resource node, the UE negotiates fine-grained parameters with the computing resource node (including communication latency requirements, transmission rate requirements, and computing processing latency requirements) to establish and execute computing tasks. Further negotiation of computing tasks can be conducted via control plane signaling or user plane (e.g., IP data packets).

[0196] Example 2

[0197] In this embodiment, the computing resource node registers its information with the fourth network element. The UE directly sends a computing service request to the computing control node, requesting the computing control node to allocate a computing resource node. The computing control node selects a computing resource node based on the computing service type.

[0198] Figure 6 shows a timing flowchart of the computing resource acquisition method provided in this embodiment. As shown in Figure 6, the method mainly includes the following steps:

[0199] S601a, the computing resource node sends a first message to the fourth network element (i.e., the computing control node), the first message being used to register the information of the computing resource node.

[0200] S601b, the fourth network element (i.e., 6G NRF) of the computing power resource node sends a first message, which is used to register the information of the computing power resource node.

[0201] Same as S501a and S501b above.

[0202] S602, the UE obtains the address information of the internally pre-configured computing power control node, such as IP address, FQDN, etc.

[0203] S603, the UE sends the fourth message to the computing power control node.

[0204] The fourth message carries the following:

[0205] Computing power service types, such as XR, AI, and autonomous driving;

[0206] Vendor ID represents the equipment vendor's identification information;

[0207] Computing load requirements;

[0208] application ID;

[0209] Address information of computing resource nodes.

[0210] The fourth message can be transmitted via the control plane (UE->RAN->AMF->computing control node or UE->RAN->computing control node) or via the user plane (UE->RAN->UPF->computing control node).

[0211] It should be noted that if the terminal pre-configures or obtains information about the computing resource nodes from a third-party application, such as the application ID and the address information of the computing resource nodes, the fourth message can also carry the application ID and the address information of the computing resource nodes to the computing control node, so that the computing control node can select according to the application ID or the address information.

[0212] S604, same as S506 in Embodiment 1. The computing power control node checks the UE's subscription information.

[0213] The computing power control node can interact with the 6G UDM to obtain the UE's subscription information. If the UE supports the requested computing power service type (i.e., the computing power service type in the fourth message) or the requested vendor ID (i.e., the vendor ID in the fourth message), the computing power control node executes S605 to select computing power resources based on the computing power service type; if the UE does not support the requested computing power service type (i.e., the computing power service type in the fourth message) and / or the requested vendor ID (i.e., the vendor ID in the fourth message), the computing power control node directly sends a reply message to the UE (S609). This reply message may carry a rejection indication, and optionally, the reply message may also carry a rejection reason (e.g., not supporting the computing power service type, not supporting the vendor ID).

[0214] S604 is an optional step.

[0215] S605, if the computing resource node registers its information with the 6G NRF, meaning all computing resource node information is stored in the NRF, then the computing power control node obtains the computing resource node information from the NRF. Same as S507 in the same embodiment.

[0216] S606, the computing power control node selects computing power resource nodes based on the computing power service type.

[0217] Optionally, the computing power control node may be selected based on the request parameters in the fourth message. The specific selection method is the same as S508 in Embodiment 1.

[0218] In steps S607-S608, the computing power control node sends a computing power task request to the selected computing power resource node and receives a response message from the computing power resource node. This is the same as steps S509-S510 in Embodiment 1.

[0219] S609, the computing power control node sends a computing power service response message to the UE. The computing power response message includes the address information or application ID of the computing power resource node.

[0220] In S610, using the address information or application ID of the computing resource node in the computing power service reply message, the UE negotiates fine-grained parameters with the computing resource node (including communication latency requirements, transmission rate requirements, and computing power processing latency requirements) to establish and execute computing power tasks. Further negotiation of computing power tasks can be conducted via control plane signaling or IP data packets.

[0221] Example 3

[0222] In this embodiment, the computing resource node registers its information with the fourth network element. The UE directly sends a computing service request to the 6G access node to allocate a computing resource node, and the 6G access node selects a computing resource node based on the computing service type.

[0223] The difference between this embodiment and Embodiment 1 is that in this embodiment, the computing power control node and the 6G access node are co-located. Therefore, S504, S505, and S511 in Embodiment 1 are internal logic and do not involve signaling interaction. All other aspects are the same as in Embodiment 1.

[0224] Figure 7 shows a timing flowchart of the computing resource acquisition method provided in this embodiment. As shown in Figure 7, the method mainly includes the following steps:

[0225] S701a, the computing resource node sends a first message to the fourth network element (i.e., the computing control node), the first message being used to register the information of the computing resource node.

[0226] S701b, the fourth network element (i.e., 6G NRF) of the computing power resource node sends a first message, which is used to register the information of the computing power resource node.

[0227] Same as S501a and S501b above.

[0228] S702, the UE sends a second message to the 6G access node.

[0229] The second message can be a NAS service message, and the second message carries:

[0230] Computing power service types, such as XR, AI, and autonomous driving;

[0231] Vendor ID represents the equipment vendor's identification information;

[0232] Computing load requirements;

[0233] application ID;

[0234] Address information of computing resource nodes.

[0235] It should be noted that if the terminal pre-configures or obtains information about the computing resource nodes from a third-party application, such as the application ID and the address information of the computing resource nodes, the second message can also carry the application ID and the address information of the computing resource nodes to the computing control node. In this way, the computing control node can select according to the application ID or the address information.

[0236] S703, the same as S503 in Embodiment 1. The 6G access node checks the UE's subscription information.

[0237] The 6G access node can interact with the 6G UDM to obtain the UE's subscription information. If the UE supports the requested computing power service type (i.e., the computing power service type in the fourth message) or the requested vendor ID (i.e., the vendor ID in the fourth message), the 6G access node executes S704; if the UE does not support the requested computing power service type (i.e., the computing power service type in the fourth message) or the requested vendor ID (i.e., the vendor ID in the fourth message), the 6G access node directly sends a reply message to the UE (S709). This reply message may carry a rejection indication, and optionally, the reply message may also carry a rejection reason (e.g., not supporting the computing power service type, not supporting the vendor ID).

[0238] S704, when a computing power resource node registers its information with the 6G NRF, that is, when the information of all computing power resource nodes is stored in the NRF, the 6G access node sends a computing power resource node information query request to the NRF. The computing power resource node information query request may carry at least one of the following: UE ID, computing power service type, and vendor ID.

[0239] S705, NRF returns the query result to the 6G access node, which may include information about at least one computing resource node.

[0240] S706, 6G access nodes select computing resource nodes based on computing service type.

[0241] Optionally, the 6G access node selects based on the request parameters in the second message. The specific selection method is the same as S508 in Embodiment 1.

[0242] In steps S707-S708, the 6G access node sends a computing power task request to the selected computing power resource node and receives a response message from the computing power resource node. This is the same as steps S509-S510 in Embodiment 1.

[0243] S709, the 6G access node sends a computing power service response message to the UE. The computing power response message includes the address information or application ID of the computing power resource node.

[0244] In S710, using the address information or application ID of the computing resource node in the computing power service reply message, the UE negotiates fine-grained parameters with the computing resource node (including communication latency requirements, transmission rate requirements, and computing power processing latency requirements) to establish and execute computing power tasks. Further negotiation of computing power tasks can be conducted via control plane signaling or IP data packets.

[0245] The computing resource acquisition method provided in this application allows the interaction of 6G network elements (access nodes, computing control nodes) to focus more on the selection and provision of service types, rather than directly involving specific parameter negotiation. It simplifies the information registration of computing resource nodes and is more rational and efficient in design.

[0246] The computing resource acquisition method provided in this application can be executed by a computing resource acquisition device. This application uses the execution of the computing resource acquisition method by a computing resource acquisition device as an example to illustrate the computing resource acquisition device provided in this application.

[0247] This application provides a computing power resource acquisition device. As an example, the computing power resource acquisition device can be a communication device or a component of a communication device, such as a chip. The communication device can be a terminal, a network-side device, or a server, etc. Exemplarily, the terminal can be, but is not limited to, the type of terminal 11 listed above, and the network-side device can be, but is not limited to, the type of network-side device 12 listed above. This application does not impose specific limitations.

[0248] The computing resource acquisition device includes a receiving module, a transmitting module, and a processing module. These modules can be implemented in software or hardware. When implemented in hardware, the processing module can be implemented by a processor. For example, the processor can include general-purpose processors, special-purpose processors, etc., such as central processing units (CPUs), microprocessors, digital signal processors (DSPs), artificial intelligence (AI) processors, graphics processing units (GPUs), application-specific integrated circuits (ASICs), network processors (NPs), field-programmable gate arrays (FPGAs), or other programmable logic devices, gate circuits, transistors, discrete hardware components, etc. The receiving and transmitting modules can be implemented by a communication interface, which can include one or more of the following: transceivers, pins, circuits, buses, radio frequency units, etc.

[0249] Specifically, referring to Figure 8, when the computing power resource acquisition device is a network-side device or a component of a network-side device, the computing power resource acquisition device 800 includes a processing module 802, used to: acquire computing power requirement information requested by the terminal, wherein the computing power requirement information includes at least one of the following: target computing power service type, identification information of the target equipment vendor, and computing power load requirement information; and determine the first computing power resource node to provide computing power services to the terminal based on the computing power requirement information.

[0250] In one implementation, as shown in FIG8, the device further includes: a receiving module 801, configured to receive a registration message sent by at least one computing power resource node, wherein the registration message is used to register information of the computing power resource node, and the at least one computing power resource node includes the first computing power resource node.

[0251] In one implementation, as shown in Figure 8, the device further includes a sending module 803, configured to initiate a subscription message to the at least one computing resource node, wherein the subscription message is used to subscribe to one or more pieces of information of the computing resource node.

[0252] In one implementation, the processing module 802 determines a first computing resource node to provide computing power services to the terminal based on the computing power requirement information, including:

[0253] Based on the computing power requirement information and the information of at least one computing power resource node stored locally, the first computing power resource node is selected, wherein the at least one computing power resource node includes the first computing power resource node.

[0254] In one implementation, the processing module 802 determines a first computing resource node to provide computing power services to the terminal based on the computing power requirement information, including:

[0255] Information on at least one computing resource node is obtained from a third network element, wherein the at least one computing resource node includes the first computing resource node;

[0256] Based on the first request, the first computing power resource node is selected from the at least one computing power resource node.

[0257] In one implementation, the information of the computing resource node includes at least one of the following:

[0258] The computing power service type of the computing power resource node;

[0259] The identification information of the equipment vendor corresponding to the computing power resource node;

[0260] The application identifier corresponding to the computing power resource node;

[0261] The address information of the computing resource nodes;

[0262] The computing load information of the computing resource nodes;

[0263] The time period associated with the computing power resource node.

[0264] In one implementation, as shown in FIG8, the device further includes a receiving module 801 for one of the following:

[0265] Receive the first request sent by the access node, wherein the first request carries the computing power requirement information;

[0266] The terminal sends the first request, wherein the first request carries the computing power requirement information.

[0267] The processing module 802 obtains the computing power requirement information requested by the terminal, including: obtaining the computing power requirement information based on the first request.

[0268] In one implementation, as shown in Figure 8, the device further includes a receiving module 801, used to receive a first reply message sent by the first computing power resource node.

[0269] In one implementation, the first response message carries one of the following: the terminal's identification information and the first computing power resource node's identification information, the terminal's identification information and an instruction indicating that the first computing power resource node accepts the second request.

[0270] In one implementation, as shown in Figure 8, the device further includes a sending module 803, used to send a second reply message to the terminal, wherein the second reply message carries the identification information of the first computing power resource node.

[0271] In one implementation, the processing module 802 is further configured to determine, based on the terminal's subscription information, the computing resources corresponding to at least one of the target computing power service type and the identification information of the target equipment vendor authorized by the terminal.

[0272] In one implementation, the receiving module 801 receives the first request sent by the terminal, including:

[0273] Receive the first request sent by the terminal through the user plane.

[0274] Referring to Figure 9, when the computing power resource acquisition device is a terminal or a component within a terminal, the computing power resource acquisition device 900 includes a sending module 901, used to send a first request to a second network element, wherein the first request is used to request information about a computing power resource node, and the computing power service request carries computing power requirement information, the computing power requirement information including at least one of the following: target computing power service type, identification information of the target equipment vendor, and computing power load requirement information; and a receiving module 902, used to receive a third reply message sent by the second network element, wherein the third reply message carries identification information of a first computing power resource node.

[0275] In one implementation, the first request also carries identification information of the second computing resource node.

[0276] In one implementation, the identification information includes at least one of the following: application identifier and address information.

[0277] In one implementation, as shown in Figure 9, the device may further include: a processing module 903, used to negotiate computing power parameters with the first computing power resource node based on the identification information of the first computing power resource node, wherein the computing power parameters include at least one of the following: communication latency, transmission rate, and computing power processing latency.

[0278] In one implementation, the second network element includes one of the following: an access node, a computing power control node; the sending module 901 sends a first request to the second network element, including one of the following:

[0279] Send the first request to the access node;

[0280] Based on the address information of the pre-configured computing power control node, the first request is sent to the computing power control node.

[0281] Referring to Figure 10, when the computing power resource acquisition device is a network-side device or a component of a network-side device, the computing power resource acquisition device 1000 may include: a receiving module 1001, used to receive a registration message sent by at least one computing power resource node, wherein the registration message is used to register the information of the computing power resource node.

[0282] In one implementation, the receiving module 1001 is further configured to receive a computing power query request sent by the first network element, wherein the computing power query request is used to request information about computing power resource nodes; as shown in FIG10, the device may further include: a sending module 1002 configured to send information about the at least one computing power resource node to the first network element.

[0283] In one implementation, the information of the computing resource node includes at least one of the following:

[0284] The computing power service type of the computing power resource node;

[0285] The identification information of the equipment vendor corresponding to the computing power resource node;

[0286] The application identifier corresponding to the computing power resource node;

[0287] The address information of the computing resource nodes;

[0288] Resource load information of the computing power resource nodes;

[0289] The time period associated with the computing power resource node.

[0290] The computing resource acquisition device provided in this application embodiment can implement the various processes implemented in the method embodiments of Figures 2 to 7 and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0291] As shown in Figure 11, this application embodiment also provides a communication device 1100, including a processor 1101 and a memory 1102. The memory 1102 stores a program or instructions that can run on the processor 1101. For example, when the communication device 1100 is a terminal, when the program or instructions are executed by the processor 1101, they implement the various steps of the above-described computing resource acquisition method 300 embodiment and achieve the same technical effect. When the communication device 1100 is a network-side device, when the program or instructions are executed by the processor 1101, they implement the various steps of the above-described computing resource acquisition method 200 or 400 embodiment and achieve the same technical effect. To avoid repetition, these will not be described again here.

[0292] This application also provides a terminal, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps in the method embodiment shown in FIG3. This terminal embodiment corresponds to the above-described terminal-side method embodiment, and all implementation processes and methods of the above-described method embodiments can be applied to this terminal embodiment and can achieve the same technical effect. The terminal may be the computing power resource acquisition device shown in FIG9. Specifically, FIG12 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of this application.

[0293] The terminal 1200 includes, but is not limited to, at least some of the following components: radio frequency unit 1201, network module 1202, audio output unit 1203, input unit 1204, sensor 1205, display unit 1206, user input unit 1207, interface unit 1208, memory 1209, and processor 1210.

[0294] Those skilled in the art will understand that terminal 1200 may also include a power supply (such as a battery) for powering various components. The power supply can be logically connected to processor 1210 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. The terminal structure shown in Figure 12 does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0295] It should be understood that, in this embodiment, the input unit 1204 may include a graphics processor 12041 and a microphone 12042. The graphics processor 12041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 1206 may include a display panel 12061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 1207 includes a touch panel 12071 and at least one of other input devices 12072. The touch panel 12071 is also called a touch screen. The touch panel 12071 may include a touch detection device and a touch controller. Other input devices 12072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

[0296] In this embodiment, after receiving downlink data from the network-side device, the radio frequency unit 1201 can transmit it to the processor 1210 for processing; in addition, the radio frequency unit 1201 can send uplink data to the network-side device. Typically, the radio frequency unit 1201 includes, but is not limited to, antennas, amplifiers, transceivers, couplers, low-noise amplifiers, duplexers, etc.

[0297] The memory 1209 can be used to store software programs or instructions, as well as various data. The memory 1209 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 1209 may include volatile memory or non-volatile memory. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), 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), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DRRAM). The memory 1209 in this embodiment includes, but is not limited to, these and any other suitable types of memory.

[0298] Processor 1210 may include one or more processing units; optionally, processor 1210 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 1210.

[0299] The radio frequency unit 1201 is used for:

[0300] Send a first request to the second network element, wherein the first request is used to request information about the computing power resource node, and the computing power service request carries computing power requirement information, which includes at least one of the following: target computing power service type, identification information of target equipment vendor, and computing power load requirement information;

[0301] The system receives a third reply message sent by the second network element, wherein the third reply message carries the identification information of the first computing power resource node.

[0302] Optionally, the first request may also carry identification information of the second computing resource node.

[0303] Optionally, the identification information includes at least one of the following: application identifier, address information.

[0304] Optionally, the processor 1210 is configured to negotiate computing power parameters with the first computing power resource node based on the identification information of the first computing power resource node, wherein the computing power parameters include at least one of the following: communication latency, transmission rate, and computing power processing latency.

[0305] Optionally, the second network element includes one of the following: an access node, a computing power control node; the radio frequency unit 1201 sends a first request to the second network element, including one of the following:

[0306] Send the first request to the access node;

[0307] Based on the address information of the pre-configured computing power control node, the first request is sent to the computing power control node.

[0308] The terminal provided in this application embodiment can send a first request carrying at least one of the following: target computing power service type, target equipment vendor identification information, and computing power load requirement information. This allows the network-side device to select a first computing power resource node for the terminal based on the first request after receiving it, and send a second request carrying the terminal's identification information and target computing power service type to the first computing power resource node. This enables the terminal to obtain computing power resources that meet at least one of the target computing power service type, target equipment vendor identification information, and computing power load requirement information, allowing the terminal to establish a connection with the first computing power resource node and then implement computing power services through the first computing power resource node.

[0309] It is understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of method embodiment 300 and achieve the same or corresponding technical effects. To avoid repetition, it will not be described again here.

[0310] This application also provides a network-side device, including a processor and a communication interface. The communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps of the method embodiments shown in FIG2 or 4. This network-side device embodiment corresponds to the above-described network-side device method embodiment. All implementation processes and methods of the above-described method embodiments can be applied to this network-side device embodiment and can achieve the same technical effect.

[0311] Specifically, this application embodiment also provides a network-side device, which can be the computing resource acquisition device shown in FIG8. As shown in FIG13, the network-side device 1300 includes: an antenna 1301, a radio frequency device 1302, a baseband device 1303, a processor 1304, and a memory 1305. The antenna 1301 is connected to the radio frequency device 1302. In the uplink direction, the radio frequency device 1302 receives information through the antenna 1301 and sends the received information to the baseband device 1303 for processing. In the downlink direction, the baseband device 1303 processes the information to be transmitted and sends it to the radio frequency device 1302, which processes the received information and then transmits it through the antenna 1301.

[0312] The method executed by the network-side device in the above embodiments can be implemented in the baseband device 1303, which includes a baseband processor.

[0313] The baseband device 1303 may include at least one baseband board, on which multiple chips are disposed, as shown in FIG13. One of the chips is, for example, a baseband processor, which is connected to the memory 1305 via a bus interface to call the program or instructions in the memory 1305 to execute the network-side device operation shown in the above method embodiment.

[0314] The network-side device may also include a network interface 1306, such as a Common Public Radio Interface (CPRI).

[0315] The processor 1304 is used for:

[0316] Obtain the computing power requirement information requested by the terminal, wherein the computing power requirement information includes at least one of the following: target computing power service type, target equipment vendor identification information, and computing power load requirement information;

[0317] Based on the computing power requirement information, the first computing power resource node is determined to provide computing power services to the terminal.

[0318] Optionally, the radio frequency device 1302 is configured to receive a registration message sent by at least one computing power resource node, wherein the registration message is used to register information of the computing power resource node, and the at least one computing power resource node includes the first computing power resource node.

[0319] Optionally, the radio frequency device 1302 is used to initiate a subscription message to the at least one computing power resource node, wherein the subscription message is used to subscribe to one or more pieces of information of the computing power resource node.

[0320] Optionally, the processor 1304 determines a first computing power resource node to provide computing power services to the terminal based on the computing power requirement information, including: selecting the first computing power resource node based on the computing power requirement information and information of at least one computing power resource node stored locally, wherein the at least one computing power resource node includes the first computing power resource node.

[0321] Optionally, based on the computing power requirement information, the processor 1304 determines a first computing power resource node to provide computing power services to the terminal, including:

[0322] Information on at least one computing resource node is obtained from a third network element, wherein the at least one computing resource node includes the first computing resource node;

[0323] Based on the computing power requirement information, the first computing power resource node is selected from the at least one computing power resource node.

[0324] Optionally, the information of the computing power resource node includes at least one of the following:

[0325] The computing power service type of the computing power resource node;

[0326] The identification information of the equipment vendor corresponding to the computing power resource node;

[0327] The application identifier corresponding to the computing power resource node;

[0328] The address information of the computing resource nodes;

[0329] The computing load information of the computing resource nodes;

[0330] The time period associated with the computing power resource node.

[0331] Optionally, the radio frequency device 1302 is used for one of the following:

[0332] Receive the first request sent by the access node, wherein the first request carries the computing power requirement information;

[0333] The terminal sends the first request, wherein the first request carries the computing power requirement information;

[0334] The processor 1304 obtains the computing power requirement information requested by the terminal, including: obtaining the computing power requirement information based on the first request.

[0335] Optionally, the radio frequency device 1302 is configured to receive a first reply message sent by the first computing power resource node, wherein the first reply message carries one of the following: the identification information of the terminal and the identification information of the first computing power resource node, the identification information of the terminal and the indication information instructing the first computing power resource node to accept the second request.

[0336] Optionally, the radio frequency device 1302 is used to send a second reply message to the terminal, wherein the second reply message carries the identification information of the first computing power resource node.

[0337] Optionally, the processor 1304 is further configured to determine, based on the terminal's subscription information, the computing resources corresponding to at least one of the target computing power service type and the identification information of the target equipment vendor authorized by the terminal.

[0338] In addition, the network-side device 1300 of this application embodiment also includes: a program or instructions stored in the memory 1305 and executable on the processor 134. The processor 1304 calls the program or instructions in the memory 1305 to execute the methods executed by each module shown in FIG8 and achieve the same technical effect. To avoid repetition, it will not be described in detail here.

[0339] Specifically, this application embodiment also provides a network-side device. As shown in FIG14, the network-side device 1400 includes: a processor 1401, a network interface 1402, and a memory 1403. The network-side device may be the computing resource acquisition device shown in FIG10. The network interface 1402 is, for example, a common public radio interface (CPRI).

[0340] The network interface 1402 is used to receive a registration message sent by at least one of the computing power resource nodes, wherein the registration message is used to register the information of the computing power resource node.

[0341] In addition, the network-side device 1400 of this application embodiment also includes: a program or instructions stored in the memory 1403 and executable on the processor 1401. The processor 1401 calls the program or instructions in the memory 1403 to execute the methods executed by each module shown in FIG10 and achieve the same technical effect. To avoid repetition, it will not be described in detail here.

[0342] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described computing resource acquisition method embodiments and achieve the same technical effects. To avoid repetition, they will not be described again here.

[0343] The processor mentioned above is either the processor in the terminal described in the above embodiments or the processor in the network-side device. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk. In some examples, the readable storage medium may be a non-transient readable storage medium.

[0344] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above-described computing resource acquisition method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0345] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0346] This application also provides a computer program / program product, which is stored in a storage medium. The computer program / program product is executed by at least one processor to implement the various processes of the above-described computing resource acquisition method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0347] This application embodiment also provides a wireless communication system, including: a first network element, a terminal and a fourth network element. The first network element can be used to execute the steps of the computing resource acquisition method 200 as described above. The terminal can be used to execute the steps of the computing resource acquisition method 300 as described above. The fourth network element can be used to execute the steps of the computing resource acquisition method 400 as described above.

[0348] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0349] From the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of computer software products plus necessary general-purpose hardware platforms, and of course, they can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.), and the computer software product includes several instructions to cause the terminal or network-side device to execute the methods described in the various embodiments of this application.

[0350] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other implementations under the guidance of this application without departing from the spirit and scope of the claims. All of these implementations are within the protection scope of this application.

Claims

1. A method for acquiring computing resources, comprising: The first network element obtains the computing power requirement information requested by the terminal, wherein the computing power requirement information includes at least one of the following: target computing power service type, target equipment vendor identification information, and computing power load requirement information; Based on the computing power requirement information, the first network element determines the first computing power resource node to provide computing power services to the terminal.

2. The method according to claim 1, wherein, The method further includes: The first network element receives a registration message sent by at least one computing resource node, wherein the registration message is used to register the information of the computing resource node, and the at least one computing resource node includes the first computing resource node.

3. The method according to claim 2, wherein, The method further includes: The first network element initiates a subscription message to the at least one computing resource node, wherein the subscription message is used to subscribe to one or more pieces of information of the computing resource node.

4. The method according to any one of claims 1 to 3, wherein, Based on the computing power requirement information, the first network element determines a first computing power resource node to provide computing power services to the terminal, including: The first network element selects the first computing power resource node based on the computing power requirement information and the information of at least one computing power resource node stored locally, wherein the at least one computing power resource node includes the first computing power resource node.

5. The method according to claim 1, wherein, Based on the computing power requirement information, the first network element determines a first computing power resource node to provide computing power services to the terminal, including: The first network element obtains information about at least one computing power resource node from the third network element, wherein the at least one computing power resource node includes the first computing power resource node; Based on the first request, the first network element selects the first computing resource node from the at least one computing resource node.

6. The method according to claim 2 or 5, wherein, The information of the computing power resource node includes at least one of the following: The computing power service type of the computing power resource node; The identification information of the equipment vendor corresponding to the computing power resource node; The application identifier corresponding to the computing power resource node; The address information of the computing resource nodes; The computing load information of the computing resource nodes; The time period associated with the computing power resource node.

7. The method according to any one of claims 1 to 6, wherein, The first network element obtains the computing power requirement information requested by the terminal, including one of the following: The first network element receives a first request sent by the access node, wherein the first request carries the computing power requirement information; The first network element receives a first request sent by the terminal, wherein the first request carries the computing power requirement information.

8. The method according to any one of claims 1 to 7, wherein, After the first network element determines the first computing power resource node to provide computing power services to the terminal based on the computing power requirement information, the method further includes: The first network element sends a second request to the first computing power resource node, wherein the second request carries the identification information of the terminal and the target computing power service type.

9. The method according to claim 8, wherein, After the first network element sends a second request to the first computing resource node, the method further includes: The first network element receives a first reply message sent by the first computing power resource node, wherein the first reply message carries one of the following: the identification information of the terminal and the identification information of the first computing power resource node, the identification information of the terminal and the indication information instructing the first computing power resource node to accept the second request.

10. The method according to claim 7, wherein, After the first network element receives the first request from the terminal, the method further includes: The first network element sends a second reply message to the terminal, wherein the second reply message carries the identification information of the first computing power resource node.

11. The method according to any one of claims 1 to 10, wherein, After the first network element obtains the computing power requirement information requested by the terminal, the method further includes: Based on the terminal's subscription information, the first network element determines that the terminal is authorized to use computing resources corresponding to at least one of the target computing power service type and the target equipment vendor's identification information.

12. The method according to claim 7, wherein, The first network element receives the first request sent by the terminal, including: The first network element receives the first request sent by the terminal through the user plane.

13. A method for acquiring computing resources, comprising: The terminal sends a first request to the second network element, wherein the first request is used to request information about the computing power resource node, and the computing power service request carries computing power requirement information, which includes at least one of the following: target computing power service type, identification information of target equipment vendor, and computing power load requirement information; The terminal receives a third reply message sent by the second network element, wherein the third reply message carries the identification information of the first computing power resource node.

14. The method according to claim 13, wherein, The first request also carries identification information of the second computing resource node.

15. The method according to claim 13 or 14, wherein, The identification information includes at least one of the following: application identifier, address information.

16. The method according to any one of claims 13 to 15, wherein, After the terminal receives the third reply message sent by the second network element, the method further includes: The terminal negotiates computing power parameters with the first computing power resource node based on the identification information of the first computing power resource node, wherein the computing power parameters include at least one of the following: communication latency, transmission rate, and computing power processing latency.

17. The method according to any one of claims 13 to 16, wherein, The second network element includes one of the following: an access node, a computing power control node; the terminal sends a first request to the second network element, including one of the following: The terminal sends the first request to the access node; The terminal sends the first request to the computing power control node based on the address information of the pre-configured computing power control node.

18. A method for acquiring computing resources, comprising: The fourth network element receives a registration message sent by at least one computing resource node, wherein the registration message is used to register the information of the computing resource node.

19. The method according to claim 18, wherein, The method further includes: The fourth network element receives a computing power query request sent by the first network element, wherein the computing power query request is used to request information about computing power resource nodes; The fourth network element sends information about the at least one computing resource node to the first network element.

20. The method according to claim 18 or 19, wherein, The information includes at least one of the following: The computing power service type of the computing power resource node; The identification information of the equipment vendor corresponding to the computing power resource node; The application identifier corresponding to the computing power resource node; The address information of the computing resource nodes; Resource load information of the computing power resource nodes; The time period associated with the computing power resource node.

21. A computing power resource acquisition device, comprising: Processing module, used for: Obtain the computing power requirement information requested by the terminal, wherein the computing power requirement information includes at least one of the following: target computing power service type, target equipment vendor identification information, and computing power load requirement information; Based on the computing power requirement information, the first computing power resource node is determined to provide computing power services to the terminal.

22. The apparatus according to claim 21, wherein, The device further includes a receiving module, which is also configured to receive a registration message sent by at least one computing resource node, wherein the registration message is used to register information of the computing resource node, and the at least one computing resource node includes the first computing resource node.

23. The apparatus according to claim 22, wherein, The sending module is further configured to initiate a subscription message to the at least one computing resource node, wherein the subscription message is used to subscribe to one or more pieces of information of the computing resource node.

24. The apparatus according to any one of claims 21 to 23, wherein, Based on the computing power requirement information, the processing module determines the first computing power resource node to provide computing power services to the terminal, including one of the following: Based on the computing power requirement information and the information of at least one computing power resource node stored locally, the first computing power resource node is selected, wherein the at least one computing power resource node includes the first computing power resource node. Information on at least one computing power resource node is obtained from a third network element. Based on the first request, the first computing power resource node is selected from the at least one computing power resource node, wherein the at least one computing power resource node includes the first computing power resource node.

25. The apparatus according to any one of claims 21 to 24, wherein, The device further includes: a receiving module, used for one of the following: Receive a first request sent by the access node, wherein the first request carries the computing power requirement information; Receive a first request sent by the terminal, wherein the first request carries the computing power requirement information; The processing module obtains the computing power requirement information requested by the terminal, including: obtaining the computing power requirement information based on the first request.

26. The apparatus according to any one of claims 21 to 25, wherein, Also includes: The receiving module is configured to receive a first reply message sent by the first computing power resource node, wherein the first reply message carries one of the following: the identification information of the terminal and the identification information of the first computing power resource node, the identification information of the terminal and the indication information instructing the first computing power resource node to accept the second request.

27. The apparatus according to claim 25, wherein, Also includes: The sending module sends a second request to the first computing power resource node, wherein the second request carries the identification information of the terminal and the target computing power service type.

28. The apparatus according to claim 27, wherein, The sending module is further configured to send a second reply message to the terminal, wherein the second reply message carries the identification information of the first computing power resource node.

29. The apparatus according to any one of claims 21 to 27, wherein, The processing module is further configured to determine, based on the terminal's subscription information, the computing resources corresponding to at least one of the target computing power service type and the target equipment vendor's identification information that the terminal is authorized to use.

30. The apparatus according to claim 25, wherein, The receiving module receives the first request sent by the terminal, including: receiving the first request sent by the terminal through the user plane.

31. A computing power resource acquisition device, comprising: The sending module is used to send a first request to the second network element, wherein the first request is used to request information of the computing power resource node, and the computing power service request carries computing power requirement information, which includes at least one of the following: target computing power service type, identification information of target equipment vendor, and computing power load requirement information; The receiving module is used to receive a third reply message sent by the second network element, wherein the third reply message carries the identification information of the first computing power resource node.

32. The apparatus according to claim 31, wherein, Also includes: The processing module is used to negotiate computing power parameters with the first computing power resource node based on the identification information of the first computing power resource node, wherein the computing power parameters include at least one of the following: communication latency, transmission rate, and computing power processing latency.

33. The apparatus according to claim 31 or 32, wherein, The second network element includes one of the following: an access node, a computing power control node; the sending module sends a first request to the second network element, including one of the following: Send the first request to the access node; Based on the pre-configured computing power control node information, the first request is sent to the computing power control node.

34. A computing power resource acquisition device, comprising: A receiving module is configured to receive a registration message sent by at least one of the computing power resource nodes, wherein the registration message is used to register the information of the computing power resource node.

35. The apparatus according to claim 34, wherein, The receiving module is further configured to receive a computing power query request sent by the first network element, wherein the computing power query request is used to request information about computing power resource nodes; The device further includes a sending module, used to send information about the at least one computing resource node to the first network element.

36. A network-side device, comprising a processor and a memory, the memory storing a program or instructions executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the computing resource acquisition method as described in any one of claims 1 to 12, or implement the steps of the computing resource acquisition method as described in any one of claims 18 to 20.

37. A terminal comprising a processor and a memory, the memory storing a program or instructions executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the computing resource acquisition method as described in any one of claims 13 to 17.

38. A readable storage medium storing a program or instructions that, when executed by a processor, implement the steps of the computing resource acquisition method as described in any one of claims 1 to 12, or the steps of the computing resource acquisition method as described in any one of claims 13 to 17, or the steps of the computing resource acquisition method as described in any one of claims 18 to 20.

Images