Computing power registration and logout method and device and storage medium

Abstract

The invention provides a computing power registration and logout method and device and a storage medium, and belongs to the technical field of communication. The method comprises the following steps: user equipment UE sends a computing power registration request or a computing power logout request to a first network element; the first network element receives a computing power registration request or a computing power logout request sent by user equipment (UE); and the second network element receives the computing power registration request or the computing power logout request sent by the first network element. Therefore, the computing power information of the UE is registered in the second network element, so that the computing function of the UE is the same as the control plane function of a core network and can be scheduled and used by the network, the UE can cooperate with the network to carry out distributed computing, the task pressure borne by the network is relieved, and the resource utilization efficiency of idle terminal equipment is improved.

Description

A computing power registration and cancellation method, device and storage medium Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to a computing power registration and cancellation method, device, and storage medium. Background Art

[0002] In future network systems, a variety of new services (such as computing power services and perception services) will be introduced to enhance the richness of network services. Terminal devices can typically call services in network devices to provide users with more personalized services. However, the relevant technologies are unclear as to how user devices register and deregister computing power with the core network and how it is used by the network.

[0003] Summary of the Invention

[0004] The computing power registration and cancellation method, device and storage medium proposed in the present disclosure are used to store the computing power registration information of the terminal device in the relevant network element, so that the computing function of the UE and the core network control plane function can be scheduled and used by the network.

[0005] In a first aspect, an embodiment of the present disclosure provides a computing power registration and cancellation method, which is executed by a user equipment UE, and includes: sending a computing power registration request or a computing power cancellation request to a first network element, wherein the computing power registration request is used to request registration of the UE's computing power information, and the computing power cancellation request is used to request cancellation of the UE's computing power information.

[0006] In some embodiments of the present disclosure, the method further includes: receiving a computing power registration result or a computing power cancellation result sent by the first network element.

[0007] In some embodiments of the present disclosure, the computing power registration request includes at least one of the following: an identifier of the UE; a computing power type of the UE; and an available computing power size of the UE.

[0008] In some embodiments of the present disclosure, the computing power deregistration request includes at least: an identifier of the UE.

[0009] In a second aspect, an embodiment of the present disclosure provides a computing power registration and cancellation method, which is executed by a first network element and includes: receiving a computing power registration request or a computing power cancellation request sent by a user equipment UE, wherein the computing power registration request is used to request registration of the UE's computing power information, and the computing power cancellation request is used to request cancellation of the UE's computing power information.

[0010] In some embodiments of the present disclosure, the method further includes: sending a computing power registration request or a computing power cancellation request to the second network element.

[0011] In some embodiments of the present disclosure, the method further includes: receiving a computing power registration result or a computing power cancellation result from a second network element; and sending the computing power registration result or the computing power cancellation result to the UE.

[0012] In some embodiments of the present disclosure, the computing power registration request includes at least one of the following: an identifier of the UE; a computing power type of the UE; and an available computing power size of the UE.

[0013] In some embodiments of the present disclosure, the computing power deregistration request includes at least: an identifier of the UE.

[0014] In a third aspect, an embodiment of the present disclosure provides a computing power registration and cancellation method, which is executed by a second network element and includes: receiving a computing power registration request or a computing power cancellation request sent by a first network element, wherein the computing power registration request is used to request registration of the computing power information of the UE, and the computing power cancellation request is used to request cancellation of the computing power information of the UE.

[0015] In some embodiments of the present disclosure, the method further includes: storing the information carried in the computing power registration request; and marking the state of the UE as an idle state.

[0016] In some embodiments of the present disclosure, the method further includes: receiving a status update request sent by the first network element, wherein the status update request is used to request updating the status of the UE, and the status of the UE includes an idle state and an occupied state.

[0017] In some embodiments of the present disclosure, the method further includes: sending a computing power registration result or a computing power cancellation result to the first network element.

[0018] In some embodiments of the present disclosure, the computing power registration request includes at least one of the following: an identifier of the UE; a computing power type of the UE; and an available computing power size of the UE.

[0019] In some embodiments of the present disclosure, the computing power deregistration request includes at least: an identifier of the UE.

[0020] In a fourth aspect, an embodiment of the present disclosure provides a user equipment UE, including:

[0021] The transceiver unit is used to send a computing power registration request or a computing power cancellation request to the first network element, wherein the computing power registration request is used to request registration of the UE's computing power information, and the computing power cancellation request is used to request cancellation of the UE's computing power information.

[0022] In a fifth aspect, an embodiment of the present disclosure provides a first network element, including:

[0023] The transceiver unit is used to receive a computing power registration request or a computing power cancellation request sent by a user equipment UE, wherein the computing power registration request is used to request to register the computing power information of the UE, and the computing power cancellation request is used to request to cancel the computing power information of the UE.

[0024] In a sixth aspect, an embodiment of the present disclosure provides a second network element, including:

[0025] The transceiver unit is used to receive a computing power registration request or a computing power cancellation request sent by the first network element, wherein the computing power registration request is used to request registration of the UE's computing power information, and the computing power cancellation request is used to request cancellation of the UE's computing power information.

[0026] In the seventh aspect, an embodiment of the present disclosure provides a communication device, which includes a processor and a memory, in which a computer program is stored; the processor executes the computer program stored in the memory so that the communication device executes the method of any one of the above-mentioned first to third aspects.

[0027] In an eighth aspect, an embodiment of the present disclosure provides a communication device, which includes a processor and an interface circuit, wherein the interface circuit is used to receive code instructions and transmit them to the processor; and the processor is used to run the code instructions to execute the method of any one of the first to third aspects above.

[0028] In a ninth aspect, an embodiment of the present invention provides a computer-readable storage medium for storing instructions for the above-mentioned network device, which, when executed, enables the terminal device to execute the method of any one of the above-mentioned first to third aspects.

[0029] In a fourteenth aspect, the present disclosure further provides a computer program product comprising a computer program, which, when executed on a computer, enables the computer to execute the method of any one of the first to third aspects above.

[0030] In a fifteenth aspect, the present disclosure provides a communication system, characterized in that it includes: a user equipment UE, a first network element, and a second network element, wherein:

[0031] The UE is configured to execute the method of the first aspect;

[0032] The first network element is configured to perform the method of the second aspect;

[0033] The second network element is used to execute the method of the third aspect.

[0034] In summary, according to the computing power registration and cancellation method provided by the present disclosure, the method is executed by the user equipment UE, including: sending a computing power registration request or a computing power cancellation request to the first network element, wherein the computing power registration request is used to request registration of the UE's computing power information, and the computing power cancellation request is used to request cancellation of the UE's computing power information. The scheme of the present disclosure clarifies the registration and cancellation process of the UE computing power in the core network by registering the UE's computing power information in the second network element, so that the UE's computing function and the core network control plane function can be scheduled and used by the network, so that the UE can cooperate with the network to perform distributed computing, reduce the task pressure carried by the network, and improve the resource utilization efficiency of idle terminal devices. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] The above and / or additional aspects and advantages of the present disclosure will become apparent and readily understood from the following description of the embodiments in conjunction with the accompanying drawings, in which:

[0036] FIG1 is a schematic diagram of the architecture of a communication system provided by an embodiment of the present disclosure;

[0037] FIG2 is a flow chart of a method for registering and canceling computing power according to an embodiment of the present disclosure;

[0038] FIG3 is a flow chart of a method for registering and canceling computing power according to another embodiment of the present disclosure;

[0039] FIG4 is a flow chart of a method for registering and canceling computing power according to another embodiment of the present disclosure;

[0040] FIG5 is a flowchart of a method for registering and canceling computing power according to another embodiment of the present disclosure;

[0041] FIG6 is a flow chart of a method for registering and canceling computing power according to another embodiment of the present disclosure;

[0042] FIG7 is a flowchart of a method for registering and canceling computing power according to another embodiment of the present disclosure;

[0043] FIG8 is a flowchart of a method for registering and canceling computing power according to another embodiment of the present disclosure;

[0044] FIG9 is a flow chart of a method for computing power registration and cancellation provided in another embodiment of the present disclosure;

[0045] FIG10 is a flowchart of an interactive method for computing power registration and cancellation provided in yet another embodiment of the present disclosure;

[0046] FIG11 is an example diagram of an interactive method for computing power registration and cancellation provided by another embodiment of the present disclosure;

[0047] FIG12 is an example diagram of an interactive method for computing power registration and cancellation provided by another embodiment of the present disclosure;

[0048] FIG13 is a schematic structural diagram of a user equipment UE provided by an embodiment of the present disclosure;

[0049] FIG14 is a schematic structural diagram of a first network element provided by an embodiment of the present disclosure;

[0050] FIG15 is a schematic structural diagram of a second network element provided by an embodiment of the present disclosure;

[0051] FIG16 is a schematic structural diagram of a second network element provided by an embodiment of the present disclosure;

[0052] FIG17 is a schematic structural diagram of a communication device provided by an embodiment of the present disclosure;

[0053] FIG18 is a schematic structural diagram of a communication device provided by one embodiment of the present disclosure, which is a chip or a chip system;

[0054] FIG19 is a schematic structural diagram of a communication system provided by an embodiment of the present disclosure. DETAILED DESCRIPTION

[0055] Exemplary embodiments will be described in detail herein, with examples illustrated in the accompanying drawings. In the following description, when referring to the drawings, identical numerals in different figures represent identical or similar elements, unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all possible implementations consistent with the present disclosure. Rather, they are merely examples of apparatuses and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.

[0056] The terms used in the embodiments of the present disclosure are for the purpose of describing specific embodiments only and are not intended to limit the embodiments of the present disclosure. The singular forms "a," "an," and "the" used in the embodiments of the present disclosure and the appended claims are also intended to include plural forms unless the context clearly indicates otherwise. It should also be understood that the term "and / or" as used herein refers to and includes any or all possible combinations of one or more associated listed items.

[0057] It should be understood that although the terms first, second, third, etc. may be used to describe various information in the embodiments of the present disclosure, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other. For example, without departing from the scope of the embodiments of the present disclosure, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the words "if" and "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".

[0058] The embodiments of the present disclosure are described in detail below. Examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals represent the same or similar elements throughout. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to be used to explain the present disclosure, and should not be understood as limiting the present disclosure.

[0059] To facilitate understanding, the terms involved in this application are first introduced.

[0060] 1. Access and Mobility Management Function (AMF) network element

[0061] Supports terminal devices with different mobility management requirements. It can perform the following key tasks: non-access stratum (NAS) signaling termination; NAS signaling security; access stratum security control; core network inter-node signaling for mobility between 3GPP access networks; idle mode terminal device reachability (including control and execution of paging retransmissions); registration area management; support for intra-system and inter-system mobility; access authentication; access authorization, including roaming rights checking; mobility management control (subscription and policy); support for network slicing; and session management function (SMF) selection.

[0062] 2. Session Management Function (SMF) network element

[0063] Together with the AMF, it can support customized mobility management solutions such as "Mobile Initiated Connection Only" (MICO) or RAN enhancements such as the "RRC Inactive" state. The SMF network element can perform the following main tasks: session management; terminal device IP address allocation and management; user plane function (UPF) selection and control; configure flow control in the UPF to route traffic to the appropriate destination; policy enforcement and quality of service (QoS) control; downlink data notification.

[0064] 3. Unified Data Management (UDM) network element

[0065] UDM is used to manage user identification, subscription data, authentication data, and user service network element registration.

[0066] The various network elements / functions involved in the embodiments of the present disclosure may be an independent hardware device or a function implemented by computer code within a hardware device, and the embodiments of the present disclosure do not limit this.

[0067] 4. Network Exposure Function (NEF) network element

[0068] NEF is a network function that 5GC exposes to the outside world and provides a standard interface. Based on 3GPP network functions, NEF exposes functions and events to other systems, ensuring both openness and system security. NEF standardizes the presentation of 5GC functions and facilitates third-party access.

[0069] 5. Application Function (AF) Network Element

[0070] The AF is similar to an application server, which interacts with other 5G core network control plane NFs and provides business services. The AF can exist for different application services and can be owned by the operator or a trusted third party.

[0071] 6. Authentication Server Function (AUSF) network element

[0072] AUSF is a network element that supports unified authentication service functions in 5G, realizes 3GPP and non-3GPP access authentication, and is a network entity in the 5G core network (5GC).

[0073] 7. Policy Control Function (PCF) network element

[0074] PCF supports a unified policy framework to manage network behavior, provides policy rules to network entities for implementation, and accesses subscription information in the Unified Data Repository (UDR).

[0075] 8. Unified Data Repository (UDR) network element

[0076] UDR is used by UDM to store or read subscription data and PCF to store or read policy data.

[0077] 9. Network Repository Function (NRF) network element

[0078] NRF supports the service discovery function, receives NF discovery requests from NF instances, and provides the information of discovered NF instances (discovered) to the NF instances. It can also maintain NF profiles of available NF instances and their supported services.

[0079] 10. User Plane Function (UPF) network element.

[0080] The UPF serves as the interconnection point between the mobile infrastructure (e.g., RAN) and the data network (DN), performing encapsulation and decapsulation of the GTP-U (GRPS Tunneling Protocol) protocol on the UP. Typically, the UPF serves as the session anchor point for protocol data units (PDUs) within or between radio access technologies (RATs), including sending one or more end marker packets (EMPs) to the gNB (NG-RAN node).

[0081] In order to better understand the solutions disclosed in the embodiments of the present disclosure, the communication system to which the embodiments of the present disclosure are applicable is first described below.

[0082] The 6G (sixth generation mobile communication system) service-oriented architecture abstracts the functions of network elements into multiple services. Compared with the traditional network architecture, the 6G service-oriented architecture introduces interawareness fusion technology to provide terminal devices with a variety of services (such as perception services, computing power services, artificial intelligence (AI) services, etc.). The 6G service-oriented architecture includes network elements for providing services. Other network elements in the 6G service-oriented architecture achieve deep integration and mutual enhancement of multi-dimensional perception, collaborative communication, and intelligent computing functions through collaboration and sharing with the network elements providing services, thereby enabling the network to have the ability of new information flow intelligent interaction and processing and wide-area intelligent collaboration.

[0083] Please refer to Figure 1, which is a schematic diagram of a 6G service-oriented network architecture provided by an embodiment of the present disclosure. Figure 1 includes network elements in the 6G service-oriented network architecture and interfaces used for communication between each network element. Referring to Figure 1, the dotted box is used to represent the network element providing the service. As shown in Figure 1, the network element can implement capabilities such as sensing and AI calculation, and also has storage capabilities.

[0084] And, the radio access network (RAN) shown in Figure 1 can be an entity on the network side for transmitting or receiving signals. For example, the RAN can be an evolved NodeB (eNB), a transmission reception point (TRP), a next generation NodeB (gNB) in an NR system, a base station in other future mobile communication systems, or an access node in a wireless fidelity (WiFi) system. The embodiments of the present disclosure do not limit the specific technology and specific device form adopted by the network device. The network device provided in the embodiments of the present disclosure can be composed of a centralized unit (CU) and a distributed unit (DU), wherein the CU can also be called a control unit (control unit). The CU-DU structure can be used to split the protocol layer of a network device, such as a base station, and the functions of some protocol layers are placed in the CU for centralized control, and the functions of the remaining part or all of the protocol layers are distributed in the DU, and the DU is centrally controlled by the CU.

[0085] The user equipment (UE) (or terminal device) shown in Figure 1 can be an entity on the user side for receiving or transmitting signals, such as a mobile phone. The terminal device can also be called a terminal, a mobile station (MS), a mobile terminal (MT), etc. The terminal device can be a car with communication functions, a smart car, a mobile phone, a wearable device, a tablet computer, a computer with wireless transceiver functions, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, a wireless terminal device in a smart home, etc. The embodiments of the present disclosure do not limit the specific technology and specific device form adopted by the UE.

[0086] In addition, Figure 1 also includes network elements such as AMF, SMF, and UDM. Among them, based on the collaborative scheduling of AMF network elements and SMF network elements, the terminal device (i.e., the UE in Figure 1) can establish a user plane connection with the network element providing the service through the RAN, so that the network element providing the service can provide the terminal device with the service requested by the terminal device. For the specific process of this part, please refer to the subsequent embodiments.

[0087] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution provided by the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution provided by the embodiment of the present disclosure is also applicable to similar technical problems.

[0088] The following describes in detail the computing power registration and cancellation method, apparatus, device, and storage medium provided by the embodiments of the present disclosure with reference to the accompanying drawings. This method can be applied to the fifth generation mobile communication technology (5G) and its subsequent communication technologies, such as the fifth generation mobile communication technology evolution (5G-advanced) and the sixth generation mobile communication technology (6G), and is not limited in this disclosure.

[0089] FIG2 is a flow chart of a method for registering and canceling computing power provided by an embodiment of the present disclosure. The method is executed by a user equipment (UE). As shown in FIG2 , the method for registering and canceling computing power may include the following steps:

[0090] Step 201: Send a computing power registration request or a computing power cancellation request to the first network element.

[0091] In some embodiments of the present disclosure, a computing power registration request is used to request registration of the computing power information of the UE, and a computing power deregistration request is used to request deregistration of the computing power information of the UE.

[0092] In some embodiments of the present disclosure, the computing power registration request includes at least one of the following: an identifier of the UE; a computing power type of the UE; and an available computing power size of the UE.

[0093] In some embodiments of the present disclosure, the computing power deregistration request includes at least: an identifier of the UE.

[0094] In some optional embodiments of the present disclosure, the identifier of the UE may be a user permanent identifier (SUbscription Permanent Identifier, SUPI), or other identifiers that can uniquely identify the UE, which are not limited in the present disclosure. The identifier of the computing service (CalService ID) may be a code that marks the computing service that can be called. The type of the computing service (Cal Service Type) may be a code or field that marks the type of computing service that can be called. The computing power requirement is the computing power size requirement of the UE for the current computing task to be performed.

[0095] In some embodiments of the present disclosure, the first network element may be an access and mobility management function AMF network element, and the UE sends a computing power registration or computing power cancellation request to the AMF network element to register or cancel the UE's computing power in the core network.

[0096] In some embodiments of the present disclosure, the UE sends a computing power registration request or a deregistration request to the first network element to register or deregister UE information in the core network.

[0097] In summary, according to the computing power registration or deregistration method provided in this disclosure, the method is performed by a user equipment (UE), including: sending a computing power registration request or a computing power deregistration request to a first network element, wherein the computing power registration request is used to request registration of the UE's computing power information, and the computing power deregistration request is used to request deregistration of the UE's computing power information. The solution of this disclosure clarifies the registration and deregistration process of UE computing power in the core network to enable UEs to collaboratively provide computing power services.

[0098] FIG3 is a flow chart of a method for registering and canceling computing power provided in an embodiment of the present disclosure. The method is executed by a user equipment UE. As shown in FIG3 , based on the embodiment shown in FIG2 , the method for registering and canceling computing power may further include the following steps:

[0099] Step 301: Receive a computing power registration result or a computing power cancellation result sent by a first network element.

[0100] In some embodiments of the present disclosure, the UE may receive a computing power registration result or a computing power cancellation result sent by the first network element to complete the computing power registration or computing power cancellation.

[0101] In some embodiments of the present disclosure, the computing power registration result may be the result of a successful computing power registration, indicating that the computing power information of the UE in the core network (specifically, for example, the computing power storage network element) has been successfully registered, indicating that the computing power information of the UE has been stored in the core network and can provide services for certain computing power requests; or the result of a failed computing power registration, indicating that the computing power information of the UE has not been stored in the core network, and the UE can abandon the computing power registration or re-initiate the computing power registration.

[0102] In some embodiments of the present disclosure, the computing power cancellation result may be a successful cancellation of the UE's computing power registration information in the core network (specifically, for example, a computing power storage network element), indicating that the core network has deleted the computing power information of the UE, that is, the UE no longer provides services for computing power requests; or a failure in the cancellation of the computing power registration information, indicating that the core network has failed to delete the computing power information of the UE, and the UE may abandon the computing power cancellation or re-initiate the computing power cancellation.

[0103] In some embodiments of the present disclosure, the first network element may be an access and mobility management function AMF network element.

[0104] In an embodiment of the present disclosure, step 301 may occur after step 201 .

[0105] In summary, according to the computing power registration and deregistration method provided in the present disclosure, the method is performed by a user equipment (UE), including: receiving a computing power registration result or a computing power deregistration result sent by a first network element. The solution of the present disclosure is to complete the computing power registration or deregistration by receiving the computing power registration result or computing power deregistration result sent by the first network element by the UE, and determining whether the computing power registration or computing power deregistration is successful.

[0106] FIG4 is a flow chart of a method for registering or canceling computing power provided by an embodiment of the present disclosure. The method is executed by a first network element. As shown in FIG3 , the computing power registration and cancellation method may include the following steps:

[0107] Step 401: Receive a computing power registration request or a computing power cancellation request sent by a user equipment UE.

[0108] In some embodiments of the present disclosure, a computing power registration request is used to request registration of the computing power information of the UE, and a computing power deregistration request is used to request deregistration of the computing power information of the UE.

[0109] In some embodiments of the present disclosure, the computing power registration request includes at least one of the following: an identifier of the UE; a computing power type of the UE; and an available computing power size of the UE.

[0110] In some embodiments of the present disclosure, the computing power deregistration request includes at least: an identifier of the UE.

[0111] In some optional embodiments of the present disclosure, the identifier of the UE may be a user permanent identifier (SUbscription Permanent Identifier, SUPI), or other identifiers that can uniquely identify the UE, which are not limited in the present disclosure. The identifier of the computing service (CalService ID) may be a code that marks the computing service that can be called. The type of the computing service (Cal Service Type) may be a code or field that marks the type of computing service that can be called. The computing power requirement is the computing power size requirement of the UE for the current computing task to be performed.

[0112] In some embodiments of the present disclosure, the first network element may be an access and mobility management function AMF network element, which receives a computing power registration request or a computing power cancellation request sent by a user equipment UE to send the request to the second network element.

[0113] In some embodiments of the present disclosure, the first network element may be an access and mobility management function AMF network element.

[0114] In some embodiments of the present disclosure, the second network element may be a computing power storage network element (see the "storage" network element in Figure 1), which can store information about computing power nodes providing computing power services. In the present disclosure, the second network element can store information about UEs that make registration or deregistration requests, such as information about computing power nodes in the core network or information about third-party computing power nodes outside the core network. This disclosure is not limited to this.

[0115] In some possible embodiments, the second network element can be a network element specifically used to store computing power node information, or it can be a general or shared storage network element in the core network, used to store computing power node information and other information, which is not limited by this disclosure.

[0116] In some possible implementations, the second network element may also be deployed outside the core network, and the information stored therein may be exchanged with the core network through the NEF network element, which is not limited in this disclosure.

[0117] In summary, according to the computing power registration and deregistration method provided in this disclosure, the method is performed by a first network element and includes: receiving a computing power registration request or a computing power deregistration request sent by a user equipment (UE), wherein the computing power registration request is used to request registration of the UE's computing power information, and the computing power deregistration request is used to request deregistration of the UE's computing power information. The solution of this disclosure clarifies the process for the first network element to receive UE computing power registration and deregistration requests, so as to enable UEs to collaboratively provide computing power services.

[0118] FIG5 is a flow chart of a method for registering and canceling computing power provided in an embodiment of the present disclosure. The method is executed by a first network element. Based on the embodiment shown in FIG4 , the method for registering and canceling computing power may further include the following steps:

[0119] Step 501: Send a computing power registration request or a computing power cancellation request to a second network element.

[0120] In some embodiments of the present disclosure, the first network element sends a computing power registration request to the second network element to register the UE information therein or sends a computing power cancellation request to the second network element to cancel the UE information stored therein.

[0121] In some embodiments of the present disclosure, the first network element may be an access and mobility management function AMF network element.

[0122] In some embodiments of the present disclosure, the second network element may be a computing power storage network element (see the "storage" network element in Figure 1), which can store information about computing power nodes providing computing power services. In the present disclosure, the second network element can store information about UEs that make registration or deregistration requests, such as information about computing power nodes in the core network or information about third-party computing power nodes outside the core network. This disclosure is not limited to this.

[0123] In some possible embodiments, the second network element can be a network element specifically used to store computing power node information, or it can be a general or shared storage network element in the core network, used to store computing power node information and other information, which is not limited by this disclosure.

[0124] In some possible implementations, the second network element may also be deployed outside the core network, and the information stored therein may be exchanged with the core network through the NEF network element, which is not limited in this disclosure.

[0125] Step 502: Receive computing power registration results or computing power cancellation results from the second network element.

[0126] In some embodiments of the present disclosure, the first network element receives a computing power registration result or a computing power deregistration result from the second network element to transmit the result to the UE.

[0127] In some embodiments of the present disclosure, the computing power registration result may be a successful registration of the UE's computing power information in the core network (specifically, for example, a computing power storage network element), indicating that the UE's computing power information has been stored in the core network and can provide services for certain computing power requests; or a failed registration of the computing power information, indicating that the UE's computing power information has not been stored in the core network, and the UE may abandon the computing power registration or re-initiate the computing power registration.

[0128] In some embodiments of the present disclosure, the computing power cancellation result may be a successful cancellation of the UE's computing power registration information in the core network (specifically, for example, a computing power storage network element), indicating that the core network has deleted the computing power information of the UE, that is, the UE no longer provides services for computing power requests; or a failure in the cancellation of the computing power registration information, indicating that the core network has failed to delete the computing power information of the UE, and the UE may abandon the computing power cancellation or re-initiate the computing power cancellation.

[0129] Step 503: Send the computing power registration result or computing power cancellation result to the UE.

[0130] In some embodiments of the present disclosure, the first network element sends the computing power registration result or the computing power cancellation result to the UE to notify the UE that the registration or cancellation is completed.

[0131] In summary, according to the computing power registration and deregistration method provided in this disclosure, the method is executed by a first network element and includes: sending a computing power registration request or a computing power deregistration request to a second network element; receiving a computing power registration result or a computing power deregistration result from the second network element; and sending the computing power registration result or computing power deregistration result to the UE. As can be seen, this solution clarifies the process by which the first network element receives the UE computing power registration and deregistration results, and through communication between each network element and the UE, enables the UE to collaboratively provide computing power services.

[0132] FIG6 is a flow chart of a method for registering and canceling computing power provided in an embodiment of the present disclosure. The method is executed by a second network element. As shown in FIG6 , the method for registering and canceling computing power may include the following steps:

[0133] Step 601: Receive a computing power registration request or a computing power cancellation request sent by a first network element.

[0134] In some embodiments of the present disclosure, a computing power registration request is used to request registration of the computing power information of the UE, and a computing power deregistration request is used to request deregistration of the computing power information of the UE.

[0135] In some embodiments of the present disclosure, the computing power registration request includes at least one of the following: an identifier of the UE; a computing power type of the UE; and an available computing power size of the UE.

[0136] In some embodiments of the present disclosure, the computing power deregistration request includes at least: an identifier of the UE.

[0137] In some embodiments of the present disclosure, the second network element receives a computing power registration request or a computing power cancellation request sent by the first network element to store the information of the UE sending the request in the second network element, or cancel the stored information of the UE in the second network element.

[0138] In some embodiments of the present disclosure, the first network element may be an access and mobility management function AMF network element.

[0139] In some embodiments of the present disclosure, the second network element may be a computing power storage network element (see the "storage" network element in Figure 1), which can store information about computing power nodes providing computing power services. In the present disclosure, the second network element can store information about UEs that make registration or deregistration requests, such as information about computing power nodes in the core network or information about third-party computing power nodes outside the core network. This disclosure is not limited to this.

[0140] In some possible embodiments, the second network element can be a network element specifically used to store computing power node information, or it can be a general or shared storage network element in the core network, used to store computing power node information and other information, which is not limited by this disclosure.

[0141] In some possible implementations, the second network element may also be deployed outside the core network, and the information stored therein may be exchanged with the core network through the NEF network element, which is not limited in this disclosure.

[0142] In summary, according to the computing power registration and cancellation method provided in the present disclosure, the method is executed by the second network element, including: receiving a computing power registration request or a computing power cancellation request sent by the first network element, wherein the computing power registration request is used to request registration of the UE's computing power information, and the computing power cancellation request is used to request cancellation of the UE's computing power information, thereby realizing the sending of the request to register or cancel the UE's computing power information to the second network element.

[0143] FIG7 is a flow chart of a method for registering and canceling computing power provided in an embodiment of the present disclosure. The method is executed by a second network element. As shown in FIG7 , based on the embodiment shown in FIG6 , the method for registering and canceling computing power may further include the following steps:

[0144] Step 701: Store the information contained in the computing power registration request.

[0145] In some embodiments of the present disclosure, the second network element stores the information carried in the accepted computing power registration request to the second network element, so as to register the computing power information of the UE to the second network element.

[0146] In some embodiments of the present disclosure, the information carried in the computing power registration request may include: UE identification, UE computing power type, UE available computing power size and other information.

[0147] In some embodiments of the present disclosure, the second network element may be a computing power storage network element (see the "storage" network element in Figure 1), which can store information about computing power nodes providing computing power services. In the present disclosure, the second network element can store information about UEs that make registration or deregistration requests, such as information about computing power nodes in the core network or information about third-party computing power nodes outside the core network. This disclosure is not limited to this.

[0148] In some possible embodiments, the second network element can be a network element specifically used to store computing power node information, or it can be a general or shared storage network element in the core network, used to store computing power node information and other information, which is not limited by this disclosure.

[0149] In some possible implementations, the second network element may also be deployed outside the core network, and the information stored therein may be exchanged with the core network through the NEF network element, which is not limited in this disclosure.

[0150] Step 702: Mark the UE state as idle.

[0151] In some embodiments of the present disclosure, the second network element marks the state of the above-mentioned UE as idle state, indicating that the UE can provide computing power support for qualified service requests.

[0152] In some embodiments of the present disclosure, the state of the UE that has been called stored in the second network element is occupied state, and it may not be called again before it completes the current computing power service; the state of the UE that has not been called stored in the second network element is idle state, and it can provide computing power services for the business.

[0153] In an embodiment of the present disclosure, steps 701 and 702 may occur after step 601. Specifically, they may occur after receiving a computing power registration request sent by the first network element.

[0154] In summary, the computing power registration and deregistration method provided in this disclosure, performed by a second network element, includes: storing the information carried in the computing power registration request; and marking the UE's status as idle. This disclosed solution clarifies the registration and deregistration process for the second network element in the core network, and can store the UE's computing power information in the second network element to enable the UE to collaboratively provide computing power services.

[0155] FIG8 is a flow chart of a method for registering and canceling computing power provided in an embodiment of the present disclosure. The method is executed by a second network element. As shown in FIG8 , based on the embodiment shown in FIG6 or FIG7 , the method for registering and canceling computing power may further include the following steps:

[0156] Step 801: Receive a status update request sent by a first network element.

[0157] In an embodiment of the present disclosure, the status update request is used to request updating of the UE status, where the UE status includes an idle state and an occupied state.

[0158] In some embodiments of the present disclosure, the first network element may be an access and mobility management function AMF network element.

[0159] In some embodiments of the present disclosure, the second network element may be a computing power storage network element (see the "storage" network element in Figure 1), which can store information about computing power nodes providing computing power services. In the present disclosure, the second network element can store information about UEs that make registration or deregistration requests, such as information about computing power nodes in the core network or information about third-party computing power nodes outside the core network. This disclosure is not limited to this.

[0160] In some possible embodiments, the second network element can be a network element specifically used to store computing power node information, or it can be a general or shared storage network element in the core network, used to store computing power node information and other information, which is not limited by this disclosure.

[0161] In some possible implementations, the second network element may also be deployed outside the core network, and the information stored therein may be exchanged with the core network through the NEF network element, which is not limited in this disclosure.

[0162] In some embodiments of the present disclosure, the second network element may store the status of each UE, such as idle or occupied. A UE that has been called is stored in the second network element as occupied and may not be called again until it completes its current computing service. A UE that has not been called is stored in the second network element as idle and may provide computing services for service requests.

[0163] In one possible implementation, when a terminal device requests a computing service, the first network element may send a status update request to the second network element to change the calling UE state from idle to occupied. In another possible implementation, when the terminal device receives the calculation result fed back by the UE, the first network element may send a status update request to the second network element to change the UE state that has completed the computing service from occupied to idle.

[0164] In an embodiment of the present disclosure, step 801 may occur after step 601 or after steps 701 and 702 .

[0165] In summary, according to the computing power registration and deregistration method provided in the present disclosure, the method is performed by a second network element and includes: receiving a status update request sent by a first network element, wherein the status update request is used to request an update of the UE status, where the UE status includes an idle state and an occupied state. This enables timely changes to the UE status stored in the second network element, thereby improving resource utilization efficiency of idle terminal devices.

[0166] FIG9 is a flow chart of a method for registering and canceling computing power provided in an embodiment of the present disclosure. The method is executed by a second network element. As shown in FIG9 , based on the embodiment shown in FIG6 , FIG7 , or FIG8 , the method for registering and canceling computing power may include the following steps:

[0167] Step 901: Send computing power registration results or computing power cancellation results to the first network element.

[0168] In some embodiments of the present disclosure, the second network element sends a computing power registration result or a computing power deregistration result to the first network element to transmit the result to the UE.

[0169] In some embodiments of the present disclosure, the computing power registration result may be a successful registration of the UE's computing power information in the core network (specifically, for example, a computing power storage network element), indicating that the UE's computing power information has been stored in the core network and can provide services for certain computing power requests; or a failed registration of the computing power information, indicating that the UE's computing power information has not been stored in the core network, and the UE may abandon the computing power registration or re-initiate the computing power registration.

[0170] In some embodiments of the present disclosure, the computing power cancellation result may be a successful cancellation of the UE's computing power registration information in the core network (specifically, for example, a computing power storage network element), indicating that the core network has deleted the computing power information of the UE, that is, the UE no longer provides services for computing power requests; or a failure in the cancellation of the computing power registration information, indicating that the core network has failed to delete the computing power information of the UE, and the UE may abandon the computing power cancellation or re-initiate the computing power cancellation.

[0171] In an embodiment of the present disclosure, step 901 may occur after the above step 601 , or may occur after the above steps 701 and 702 , or may occur after the above step 801 .

[0172] In summary, according to the computing power registration and deregistration method provided in this disclosure, the method is executed by the second UE, including: sending the computing power registration result or computing power deregistration result to the first network element. As can be seen, this solution clarifies the process of the second network element sending the UE computing power registration and deregistration results, thereby achieving the above-mentioned result being sent to the UE through the first network element, completing the entire registration or deregistration process.

[0173] Figure 10 is a flowchart of an interactive method for computing power registration and deregistration provided by an embodiment of the present disclosure. The method can be executed by a communication system, which includes a user equipment UE, a first network element, and a second network element. As shown in Figure 10, the interactive method may include the following steps:

[0174] 1001. The UE sends a computing power registration request or a computing power cancellation request to the first network element.

[0175] In some embodiments of the present disclosure, a computing power registration request is used to request registration of the computing power information of the UE, and a computing power deregistration request is used to request deregistration of the computing power information of the UE.

[0176] 1002. The first network element sends a computing power registration request or a computing power cancellation request to the second network element.

[0177] The principles of the above steps 1001-1002 are the same as the principles of the various steps in the embodiment shown in Figures 2-9 above. Please refer to the relevant description of Figures 2-9 and will not be repeated here.

[0178] In summary, according to the computing power registration and deregistration method provided in this disclosure, through interaction between user equipment (UE), a first network element, and a second network element, the UE sends a computing power registration request or a computing power deregistration request to the first network element, wherein the computing power registration request is used to request registration of the UE's computing power information, and the computing power deregistration request is used to request deregistration of the UE's computing power information; the first network element sends the computing power registration request or computing power deregistration request to the second network element. The solution of this disclosure clarifies a complete workflow for computing power registration and deregistration of UEs in the core network, so that information on the computing power of user equipment (UE) can be stored in the core network and computing power services can be collaboratively provided.

[0179] As an example, a computing power registration and cancellation process is shown in Figure 11.

[0180] Among them, the first network element is the AMF network element, and the second network element is the Storage network element.

[0181] The UE performs a computing power registration operation in the core network and sends a computing power information registration request to the AMF. The request information contains at least (UE identifier SUPI, computing power type, and available computing power size), as shown in step 1 of the figure.

[0182] Among them, AMF sends the request information to the Storage network element, as shown in step 2 of the figure.

[0183] Among them, the Storage network element registers and stores the UE computing power information and marks the UE status as available, as shown in step 3 of the figure.

[0184] The Storage network element returns the computing power registration result to the AMF, as shown in step 4.

[0185] The NEF sends the computing power registration result to the UE, and the computing power registration process ends, as shown in step 5 of the figure.

[0186] As an example, a computing power registration and cancellation process is shown in Figure 12.

[0187] Among them, the first network element is the AMF network element, and the second network element is the Storage network element.

[0188] 1) The UE performs a computing power deregistration operation in the core network and sends a computing power information deregistration request to the AMF. The request information includes (UE identifier SUPI), as shown in step 1 of the figure.

[0189] Among them, AMF sends the request information to the Storage network element, as shown in step 2 of the figure.

[0190] Among them, the Storage network element cancels the corresponding UE computing power information, as shown in step 3 of the figure.

[0191] The Storage network element returns the computing power cancellation result to the AMF, as shown in step 4.

[0192] Among them, AMF sends the information to UE, and the computing power cancellation process ends, as shown in step 5 of the figure.

[0193] In the embodiments provided above, the methods provided in the embodiments of the present application are described from the perspectives of network devices and user devices, respectively. In order to implement the various functions in the methods provided in the embodiments of the present application, the network devices and user devices may include hardware structures and software modules, and the aforementioned functions may be implemented in the form of hardware structures, software modules, or hardware structures plus software modules. One of the aforementioned functions may be implemented in the form of hardware structures, software modules, or hardware structures plus software modules.

[0194] Corresponding to the network device management methods provided in the above-mentioned embodiments, the present disclosure also provides a computing power registration and cancellation device. Since the computing power registration and cancellation device provided in the embodiments of the present disclosure corresponds to the computing power registration and cancellation methods provided in the above-mentioned embodiments, the implementation method of the computing power registration and cancellation method is also applicable to the computing power registration and cancellation device provided in this embodiment, and will not be described in detail in this embodiment.

[0195] FIG13 is a schematic structural diagram of a user equipment UE1300 provided in an embodiment of the present disclosure.

[0196] As shown in Figure 13, the device 1300 may include a transceiver unit 1301, which is used to send a computing power registration request or a computing power cancellation request to the first network element, wherein the computing power registration request is used to request registration of the UE's computing power information, and the computing power cancellation request is used to request cancellation of the UE's computing power information.

[0197] In summary, according to the user equipment UE module provided in the embodiment of the present disclosure, the user equipment UE module sends a computing power registration request or a computing power cancellation request to the first network element, wherein the computing power registration request is used to request registration of the UE's computing power information, and the computing power cancellation request is used to request cancellation of the UE's computing power information. It can be seen that the present disclosure provides a computing power registration and cancellation method, which can enable the UE to establish a connection with the first network element, and then enable the UE to send registration and cancellation requests to the second network element, thereby realizing the UE's computing power registration and cancellation in the core network.

[0198] In some embodiments of the present disclosure, the computing power registration request includes at least one of the following: an identifier of the UE; a computing power type of the UE; and an available computing power size of the UE.

[0199] In some embodiments of the present disclosure, the computing power cancellation request includes at least: an identifier of the UE.

[0200] In some embodiments of the present disclosure, the transceiver unit 1301 is further used to: receive a computing power registration result or a computing power cancellation result sent by the first network element.

[0201] FIG14 is a schematic structural diagram of a first network element 1400 provided in an embodiment of the present disclosure.

[0202] As shown in Figure 14, the device 1400 may include a transceiver unit 1401, which is used to receive a computing power registration request or a computing power cancellation request sent by a user equipment UE, wherein the computing power registration request is used to request registration of the UE's computing power information, and the computing power cancellation request is used to request cancellation of the UE's computing power information.

[0203] In summary, the computing power registration and deregistration apparatus provided in accordance with the embodiments of the present disclosure is configured to receive a computing power registration request or a computing power deregistration request sent by a user equipment (UE). The computing power registration request is used to request registration of the UE's computing power information, while the computing power deregistration request is used to request deregistration of the UE's computing power information. This enables interaction between the user equipment and the core network, laying the foundation for the UE to register and deregister computing power in the core network.

[0204] In some embodiments of the present disclosure, the computing power registration request includes at least one of the following: an identifier of the UE; a computing power type of the UE; and an available computing power size of the UE.

[0205] In some embodiments of the present disclosure, the computing power deregistration request includes at least: an identifier of the UE.

[0206] In some embodiments of the present disclosure, the transceiver unit 1401 is further configured to send a computing power registration request or a computing power cancellation request to the second network element.

[0207] In some embodiments of the present disclosure, the transceiver unit 1401 is further configured to receive a computing power registration result or a computing power cancellation result from the second network element.

[0208] In some embodiments of the present disclosure, the transceiver unit 1401 is further configured to send a computing power registration result or a computing power cancellation result to the UE.

[0209] FIG15 is a schematic structural diagram of a second network element 1500 provided in an embodiment of the present disclosure.

[0210] As shown in Figure 15, the device 1500 may include a transceiver unit 1501, which is used to receive a computing power registration request or a computing power cancellation request sent by the first network element, wherein the computing power registration request is used to request registration of the UE's computing power information, and the computing power cancellation request is used to request cancellation of the UE's computing power information.

[0211] In summary, according to the computing power registration and cancellation device provided by the embodiment of the present disclosure, the second network element is used to receive a computing power registration request or a computing power cancellation request sent by the first network element, wherein the computing power registration request is used to request registration of the UE's computing power information, and the computing power cancellation request is used to request cancellation of the UE's computing power information, thereby registering the UE's computing power information in the second network element, or canceling the UE's computing power information in the second network element, to prepare for the UE to provide computing power services for the collaborative network.

[0212] In some embodiments of the present disclosure, the computing power registration request includes at least one of the following: an identifier of the UE; a computing power type of the UE; and an available computing power size of the UE.

[0213] In some embodiments of the present disclosure, the computing power deregistration request is used to request deregistration of the computing power information of the UE.

[0214] In some embodiments of the present disclosure, the device further includes a storage unit 1502 for storing information carried in a computing power registration request.

[0215] In some embodiments of the present disclosure, the apparatus further includes a processing unit 1503, configured to mark the state of the UE requesting computing power registration as an idle state.

[0216] In some embodiments of the present disclosure, the transceiver unit 1501 is further configured to receive a status update request sent by the first network element, wherein the status update request is used to request an update of the UE status, and the UE status includes an idle state and an occupied state.

[0217] In some embodiments of the present disclosure, the transceiver unit 1501 is further configured to send a computing power registration result or a computing power cancellation result to the first network element.

[0218] Please refer to Figure 17, which is a schematic diagram of the structure of a communication device 1600 provided in an embodiment of the present application. Communication device 1600 can be a network device or a terminal device, or a chip, chip system, or processor that supports a network device to implement the above-mentioned method, or a chip, chip system, or processor that supports a terminal device to implement the above-mentioned method. This device can be used to implement the method described in the above-mentioned method embodiment. For details, please refer to the description of the above-mentioned method embodiment.

[0219] The communication device 1600 may include one or more processors 1601. The processor 1601 may be a general-purpose processor or a dedicated processor. For example, it may be a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processing unit may be used to control the communication device (e.g., a base station, a baseband chip, a terminal device, a terminal device chip, a DU or CU, etc.), execute computer programs, and process computer program data.

[0220] Optionally, the communication device 1600 may further include one or more memories 1602, on which a computer program 1604 may be stored. The processor 1601 executes the computer program 1604 to cause the communication device 1600 to perform the method described in the above method embodiment. Optionally, the memory 1602 may also store data. The communication device 1600 and the memory 1602 may be provided separately or integrated together.

[0221] Optionally, the communication device 1600 may further include a transceiver 1605 and an antenna 1606. The transceiver 1605 may be referred to as a transceiver unit, a transceiver, or a transceiver circuit, and is configured to implement transceiver functions. The transceiver 1605 may include a receiver and a transmitter. The receiver may be referred to as a receiver or a receiving circuit, and is configured to implement a receiving function; the transmitter may be referred to as a transmitter or a transmitting circuit, and is configured to implement a transmitting function.

[0222] Optionally, the communication device 1600 may further include one or more interface circuits 1607. The interface circuit 1607 is configured to receive code instructions and transmit the instructions to the processor 1601. The processor 1601 executes the code instructions to enable the communication device 1600 to perform the method described in the above method embodiment.

[0223] In one implementation, processor 1601 may include a transceiver for implementing receiving and transmitting functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing the receiving and transmitting functions may be separate or integrated. The transceiver circuit, interface, or interface circuit may be used for reading and writing code / data, or may be used for transmitting or delivering signals.

[0224] In one implementation, processor 1601 may store a computer program 1603. Computer program 1603, when executed on processor 1601, enables communication device 1600 to perform the method described in the above method embodiment. Computer program 1603 may be embedded in processor 1601, in which case processor 1601 may be implemented by hardware.

[0225] In one implementation, the communication device 1600 may include a circuit that can implement the functions of sending, receiving, or communicating in the aforementioned method embodiments. The processor and transceiver described in this application can be implemented on an integrated circuit (IC), an analog IC, a radio frequency integrated circuit RFIC, a mixed signal IC, an application specific integrated circuit (ASIC), a printed circuit board (PCB), an electronic device, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal oxide semiconductor (CMOS), N-type metal oxide semiconductor (nMetal-oxide-semiconductor, NMOS), P-type metal oxide semiconductor (positive channel metal oxide semiconductor, PMOS), bipolar junction transistor (bipolar junction transistor, BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

[0226] The communication device described in the above embodiments may be a network device or a terminal device, but the scope of the communication device described in this application is not limited thereto, and the structure of the communication device may not be limited to FIG17. The communication device may be an independent device or may be part of a larger device. For example, the communication device may be:

[0227] (1) An independent integrated circuit (IC), or chip, or chip system or subsystem;

[0228] (2) a collection of one or more ICs, optionally including a storage component for storing data and computer programs;

[0229] (3) ASIC, such as modem;

[0230] (4) Modules that can be embedded in other devices;

[0231] (5) Receivers, terminal devices, intelligent terminal devices, cellular phones, wireless devices, handheld devices, mobile units, vehicle-mounted devices, network devices, cloud devices, artificial intelligence devices, etc.;

[0232] (6)Others, etc.

[0233] If the communication device can be a chip or a chip system, please refer to the schematic diagram of the chip structure shown in Figure 18. The chip shown in Figure 18 includes a processor 1701 and an interface 1702. The number of processors 1701 can be one or more, and the number of interfaces 1702 can be multiple.

[0234] Optionally, the chip further includes a memory 1703, which is used to store necessary computer programs and data.

[0235] Those skilled in the art will also appreciate that the various illustrative logical blocks and steps listed in the embodiments of the present application can be implemented by electronic hardware, computer software, or a combination of both. Whether such functions are implemented by hardware or software depends on the specific application and the design requirements of the entire system. Those skilled in the art may use various methods to implement the functions for each specific application, but such implementation should not be construed as exceeding the scope of protection of the embodiments of the present application.

[0236] The present application also provides a readable storage medium having instructions stored thereon, which implement the functions of any of the above method embodiments when executed by a computer.

[0237] The present application also provides a computer program product, which implements the functions of any of the above method embodiments when executed by a computer.

[0238] Figure 19 is a structural diagram of a communication system provided by an embodiment of the present disclosure. As shown in Figure 19, the communication system includes: a user equipment UE for executing the methods shown in Figures 2 and 3 above; a first network element for executing the methods shown in Figures 4 and 5 above; and a second network element for executing the methods shown in Figures 6 and 7 above.

[0239] In the above embodiments, all or part of the embodiments can be implemented by software, hardware, firmware, or any combination thereof. When implemented using software, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer programs. When the computer program is loaded and executed on a computer, all or part of the processes or functions according to the embodiments of the present application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer program can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media integrated therein. Available media may be magnetic media (eg, floppy disks, hard disks, tapes), optical media (eg, high-density digital video discs (DVDs)), or semiconductor media (eg, solid state disks (SSDs)).

[0240] Those skilled in the art will understand that the various numerical numbers such as first and second involved in this application are only for the convenience of description and are not used to limit the scope of the embodiments of this application, and also indicate the order of precedence.

[0241] In this application, "at least one" can also be described as one or more, and "a plurality" can be two, three, four, or more, which is not limited in this application. In the embodiments of this application, for a technical feature, "first," "second," "third," "A," "B," "C," and "D" are used to distinguish technical features within the technical feature. There is no order of precedence or size between the technical features described by "first," "second," "third," "A," "B," "C," and "D."

[0242] The correspondences shown in the tables in this application can be configured or predefined. The values ​​of the information in each table are examples only and can be configured to other values, which are not limited by this application. When configuring the correspondence between information and parameters, it is not necessarily required to configure all the correspondences shown in each table. For example, in the tables in this application, the correspondences shown in certain rows may not be configured. For another example, appropriate deformation adjustments can be made based on the above tables, such as splitting, merging, etc. The names of the parameters shown in the titles of the above tables can also use other names that can be understood by the communication device, and the values ​​or representations of the parameters can also use other values ​​or representations that can be understood by the communication device. When implementing the above tables, other data structures can also be used, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables or hash tables, etc.

[0243] The predefined in this application may be understood as defined, predefined, stored, pre-stored, pre-negotiated, pre-configured, solidified, or pre-burned.

[0244] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0245] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0246] The above are only specific embodiments of the present application, but the scope of protection of this application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A computing power registration and cancellation method, characterized in that: The method is performed by a user equipment UE, and the method includes: Send a computing power registration request or a computing power cancellation request to the first network element, The computing power registration request is used to request registration of the computing power information of the UE, and the computing power cancellation request is used to request cancellation of the computing power information of the UE.

2. The method according to claim 1, characterized in that The method further comprises: Receive the computing power registration result or computing power cancellation result sent by the first network element.

3. The method according to claim 1 or 2, characterized in that: The computing power registration request includes at least one of the following: an identifier of the UE; The computing power type of the UE; The available computing power of the UE.

4. The method according to any one of claims 1 to 3, characterized in that The computing power cancellation request at least includes: The identifier of the UE.

5. A computing power registration and cancellation method, characterized in that: The method is performed by a first network element, and the method includes: Receive a computing power registration request or computing power cancellation request sent by a user equipment UE, The computing power registration request is used to request registration of the computing power information of the UE, and the computing power cancellation request is used to request cancellation of the computing power information of the UE.

6. The method according to claim 5, characterized in that The method further comprises: The computing power registration request or the computing power cancellation request is sent to the second network element.

7. The method according to claim 5 or 6, characterized in that: The method further comprises: receiving a computing power registration result or a computing power cancellation result from the second network element; The computing power registration result or the computing power cancellation result is sent to the UE.

8. The method according to any one of claims 5 to 7, characterized in that The computing power registration request includes at least one of the following: an identifier of the UE; The computing power type of the UE; The available computing power of the UE.

9. The method according to any one of claims 5 to 8, characterized in that The computing power cancellation request at least includes: The identifier of the UE.

10. A method for registering and canceling computing power, characterized in that: The method is performed by a second network element, and the method includes: receiving a computing power registration request or a computing power cancellation request sent by the first network element, The computing power registration request is used to request registration of the computing power information of the UE, and the computing power cancellation request is used to request cancellation of the computing power information of the UE.

11. The method according to claim 10, characterized in that The method further comprises: Storing the information contained in the computing power registration request; The state of the UE is marked as an idle state.

12. The method according to claim 10 or 11, characterized in that: The method further comprises: receiving a status update request sent by the first network element, The status update request is used to request to update the status of the UE, and the status of the UE includes an idle state and an occupied state.

13. The method according to any one of claims 10 to 12, characterized in that The method further comprises: Send the computing power registration result or the computing power cancellation result to the first network element.

14. The method according to any one of claims 10 to 13, characterized in that The computing power registration request includes at least one of the following: an identifier of the UE; The computing power type of the UE; The available computing power of the UE.

15. The method according to any one of claims 10 to 14, characterized in that The computing power cancellation request at least includes: The identifier of the UE.

16. A user equipment UE, characterized in that: include: A transceiver unit, configured to send a computing power registration request or a computing power cancellation request to the first network element, The computing power registration request is used to request registration of the computing power information of the UE, and the computing power cancellation request is used to request cancellation of the computing power information of the UE.

17. A first network element, characterized in that: include: The transceiver unit is used to receive a computing power registration request or a computing power cancellation request sent by a user equipment UE, The computing power registration request is used to request registration of the computing power information of the UE, and the computing power cancellation request is used to request cancellation of the computing power information of the UE.

18. A second network element, characterized in that: include: A transceiver unit, configured to receive a computing power registration request or a computing power cancellation request sent by the first network element, The computing power registration request is used to request registration of the computing power information of the UE, and the computing power cancellation request is used to request cancellation of the computing power information of the UE.

19. A communication device, characterized in that: The device comprises a processor and a memory, wherein the memory stores a computer program, and the processor executes the computer program stored in the memory so that the device performs: The method according to any one of claims 1 to 4; or A method as claimed in any one of claims 5 to 9; or A method as claimed in any one of claims 10 to 14.

20. A communication device, characterized in that: include: processor and interface circuitry, wherein The interface circuit is used to receive code instructions and transmit them to the processor; The processor is configured to execute the code instructions to perform: The method according to any one of claims 1 to 4; or A method as claimed in any one of claims 5 to 9; or A method as claimed in any one of claims 10 to 14.

21. A computer-readable storage medium, for storing instructions, which, when executed, enable the following method to be implemented: The method according to any one of claims 1 to 4; or A method as claimed in any one of claims 5 to 9; or A method as claimed in any one of claims 10 to 14.

22. A communication system, characterized in that: The system includes a user equipment UE, a first network element, and a second network element, wherein: The UE is used to perform the method according to any one of claims 1 to 4; The first network element is used to perform the method according to any one of claims 5 to 9; The second network element is used to execute the method according to any one of claims 10 to 14.

Images