Computing resource awareness methods and apparatuses, and processor-readable storage medium
By using resource access awareness and control messages in the computing network, the problems of accidental access and unauthorized modification between resource consumers and providers are solved, thereby improving the service quality and business satisfaction of computing services.
Patent Information
- Application Number
- PCT/CN2026/084919
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-06
- Filing Date
- 2026-03-20
- Publication Date
- 2026-11-12
AI Technical Summary
In computing networks, situations where resource consumers accidentally access computing resources or resource providers arbitrarily alter computing resources can lead to interruptions in computing services and poor service quality.
The first resource call awareness message enables all devices to be aware of the call to computing resources, and the resource call control message controls the call to the target computing resources to ensure that all devices can call the target computing resources and avoid accidental access.
It improves the service quality of computing services, ensures that computing services can meet business needs, prevents accidental access and unauthorized changes, and enhances the efficiency of resource management and scheduling.
Smart Images

Figure CN2026084919_12112026_PF_FP_ABST
Abstract
Description
Computational resource awareness methods, devices, and processor-readable storage media Cross-referencing
[0001] This application incorporates Chinese Patent Application No. 2025105753068, filed on May 6, 2025, entitled “Computational Resource Awareness Method, Apparatus and Processor-Readable Storage Medium”, which is incorporated herein by reference in its entirety. Technical Field This disclosure relates to the field of communication technology, and in particular to a computing resource awareness method, apparatus, and processor-readable storage medium. Background Technology
[0002] Computing power networks can share computing resources with computing power consumers, thereby efficiently utilizing idle computing resources while obtaining the benefits of shared computing resources. Since 6G networks integrate computing power with the network itself, opening up computing resources through mobile communication networks to provide computing services will be an inevitable trend.
[0003] In related technologies, when computing resources are made available through mobile communication networks, there may be situations where resource consumers accidentally access computing resources, or where resource providers arbitrarily change computing resources. This can lead to problems such as service interruption and failure to meet service requirements, resulting in poor service quality of current computing services. Summary of the Invention
[0004] According to various embodiments of the present disclosure, a computing resource awareness method, apparatus, and processor-readable storage medium are provided.
[0005] In a first aspect, this disclosure provides a computing resource awareness method. Applied to resource-owning devices, the method includes:
[0006] Receive a first resource call awareness message sent by a first network function entity. The first resource call awareness message is used to indicate the call to the computing service API of the target computing resource. The target computing resource is the computing resource provided by all devices of the resource.
[0007] Send the resource access control message for the computing service API to the first network function entity.
[0008] Secondly, this disclosure provides a computing resource awareness method. Applied to a first network functional entity, the method includes:
[0009] Receive a resource request message from the resource requesting device for the computing service API of the target computing resource, wherein the target computing resource is the computing resource provided by the resource-owning device;
[0010] If the target computing resource is a protected computing resource, a first resource call awareness message is sent to all devices that own the resource. The first resource call awareness message is used to indicate the call to the computing service API of the target computing resource.
[0011] Receive resource call control messages for the computing service API sent by all devices of the resource.
[0012] Thirdly, this disclosure provides a computing resource awareness method. Applied to a resource allocation device, the method includes:
[0013] Send a first resource call request message to the first network function entity for the computing service API of the target computing resource, wherein the target computing resource is the computing resource provided by the device that owns the resource;
[0014] Receive the resource call control message for the computing service API sent by the first network function entity.
[0015] Fourthly, this disclosure provides a computing resource awareness method. Applied to a resource allocation device, the method includes:
[0016] The system receives a second resource call awareness message sent by a first network function entity. The second resource call awareness message is used to indicate whether at least one of the target computing resource and the computing service API of the target computing resource has changed.
[0017] Fifthly, this disclosure provides a computing resource awareness method. Applied to a first network functional entity, the method includes:
[0018] Receive resource change notification messages for the target resource from all devices in the resource;
[0019] A second resource call awareness message is sent to the resource call device, the second resource call awareness message being used to indicate whether at least one of the target computing resource and the computing service API of the target computing resource has changed.
[0020] Sixthly, this disclosure provides a computing resource awareness method. Applied to resource-owning devices, the method includes:
[0021] A resource change notification message for the target resource is sent to a first network function entity. The resource change notification message is used to trigger a second resource call awareness message. The second resource call awareness message is used to indicate whether at least one of the target computing resource and the computing service API of the target computing resource has changed.
[0022] In a seventh aspect, this disclosure provides a computing resource sensing device applied to resource-owning devices, including a memory, a transceiver, and a processor:
[0023] A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations:
[0024] The transceiver receives a first resource call awareness message sent by a first network function entity. The first resource call awareness message is used to indicate the call to the computing service API of the target computing resource, and the target computing resource is the computing resource provided by all devices of the resource.
[0025] The transceiver sends the resource access control message for the computing service API to the first network function entity.
[0026] Eighthly, this disclosure provides a computing resource awareness device applied to a first network functional entity, including a memory, a transceiver, and a processor:
[0027] A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations:
[0028] The transceiver receives a resource call request message from the resource call device for the computing service API of the target computing resource, wherein the target computing resource is the computing resource provided by the resource-owning device.
[0029] If the target computing resource is a protected computing resource, a first resource call awareness message is sent to all devices of the resource through the transceiver. The first resource call awareness message is used to indicate the call to the computing service API of the target computing resource.
[0030] The transceiver receives resource call control messages from all devices of the resource's computing service API.
[0031] Ninthly, this disclosure provides a computing resource awareness device for use in a resource allocation device, including a memory, a transceiver, and a processor:
[0032] A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations:
[0033] The transceiver sends a first resource call request message for the computing service API of the target computing resource to the first network function entity, wherein the target computing resource is the computing resource provided by the resource-owning device;
[0034] The transceiver receives resource call control messages for the computing service API sent by the first network function entity.
[0035] In a tenth aspect, this disclosure provides a computing resource awareness device for use in a resource allocation device, comprising a memory, a transceiver, and a processor:
[0036] A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations:
[0037] The transceiver receives a second resource call awareness message sent by a first network function entity. The second resource call awareness message is used to indicate whether at least one of the target computing resource and the computing service API of the target computing resource has changed.
[0038] In the eleventh aspect, this disclosure provides a computing resource awareness device applied to a first network functional entity, including a memory, a transceiver, and a processor:
[0039] A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations:
[0040] The transceiver receives resource change notification messages for the target resource from all devices that control the resource.
[0041] A second resource call awareness message is sent by the transceiver to the resource call device. The second resource call awareness message is used to indicate whether at least one of the target computing resource and the computing service API of the target computing resource has changed.
[0042] In a twelfth aspect, this disclosure provides a computing resource awareness device applied to resource-owning devices, including a memory, a transceiver, and a processor:
[0043] A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations:
[0044] The transceiver sends a resource change notification message for the target resource to the first network function entity. The resource change notification message is used to trigger a second resource call awareness message. The second resource call awareness message is used to indicate whether at least one of the target computing resource and the computing service API of the target computing resource has changed.
[0045] In a thirteenth aspect, this disclosure provides a computing resource sensing device applied to resource-owning devices, comprising:
[0046] The first receiving module is configured to receive a first resource call awareness message sent by a first network function entity. The first resource call awareness message is used to indicate the call to the computing service API of the target computing resource, wherein the target computing resource is the computing resource provided by all devices of the resource.
[0047] The first sending module is used to send the resource call control message of the computing service API to the first network function entity.
[0048] In a fourteenth aspect, this disclosure provides a computing resource awareness device applied to a first network functional entity, comprising:
[0049] The second receiving module is used to receive a resource invocation request message for a target computing resource's computing service API sent by a resource invocation device, wherein the target computing resource is a computing resource provided by the resource-owning device; and to receive a resource invocation control message for the computing service API sent by the resource-owning device through the transceiver.
[0050] The second sending module is used to send a first resource call awareness message to all devices of the resource through the transceiver when the target computing resource is a protected computing resource. The first resource call awareness message is used to indicate the call of the computing service API of the target computing resource.
[0051] In a fifteenth aspect, this disclosure provides a computing resource sensing device applied to a resource allocation device, comprising:
[0052] The third sending module is used to send a first resource call request message of the computing service API of the target computing resource to the first network function entity, wherein the target computing resource is the computing resource provided by the resource-owning device;
[0053] The third receiving module is used to receive the resource call control message of the computing service API sent by the first network function entity.
[0054] In a sixteenth aspect, this disclosure provides a computing resource sensing device applied to a resource allocation device, comprising:
[0055] The third sending module is used to receive a second resource call awareness message sent by the first network function entity. The second resource call awareness message is used to indicate whether at least one of the target computing resource and the computing service API of the target computing resource has changed.
[0056] The first processing module is used to process the call to the computing service API of the target computing resource based on the second resource call awareness message.
[0057] In a seventeenth aspect, this disclosure provides a computing resource awareness device applied to a first network functional entity, comprising:
[0058] The second receiving module is used to receive resource change notification messages for the target resource sent by all devices of the resource.
[0059] The second sending module is used to send a second resource call awareness message, which is used to indicate whether at least one of the target computing resource and the computing service API of the target computing resource has changed.
[0060] In an eighteenth aspect, this disclosure provides a computing resource sensing device applied to resource-owning devices, comprising:
[0061] The second processing device is used to generate a resource change notification message for the target resource. The resource change notification message is used to trigger a second resource call awareness message. The second resource call awareness message is used to indicate whether at least one of the target computing resource and the computing service API of the target computing resource has changed.
[0062] The first sending device is used to send the resource change notification message to the first network function entity.
[0063] In a nineteenth aspect, this disclosure also provides a processor-readable storage medium. The processor-readable storage medium stores a program thereon, which, when executed by a processor, implements any one of the computing resource awareness methods described in the first to sixth aspects.
[0064] In a twentieth aspect, this disclosure also provides a computer program product. The computer program product includes a computer program that, when executed by a processor, implements any one of the computing resource awareness methods described in the first to sixth aspects.
[0065] The above description is merely an overview of the technical solution disclosed herein. In order to better understand the technical means of this disclosure and to implement it in accordance with the contents of the specification, and to make the above and other objects, features and advantages of this disclosure more apparent and understandable, specific embodiments of this disclosure are described below. Attached Figure Description
[0066] Various other advantages and benefits will become apparent to those skilled in the art upon reading the detailed description of the embodiments described below. The accompanying drawings are for illustrative purposes only and are not intended to limit the scope of this disclosure. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings:
[0067] Figure 1 is a schematic diagram of a CAPIF architecture provided in related technologies;
[0068] Figure 2 is a schematic diagram of another CAPIF architecture provided in related technologies;
[0069] Figure 3 is an application scenario diagram of a computing resource awareness method provided in an embodiment of this disclosure;
[0070] Figure 4 is a flowchart illustrating a computing resource awareness method provided in an embodiment of this disclosure;
[0071] Figure 5 is a signaling interaction diagram of a computing resource awareness method provided in an embodiment of this disclosure;
[0072] Figure 6 is a signaling interaction diagram of another computing resource awareness method provided in an embodiment of this disclosure;
[0073] Figure 7 is a signaling interaction diagram of another computing resource awareness method provided in an embodiment of this disclosure;
[0074] Figure 8 is a signaling interaction diagram of another computing resource awareness method provided in an embodiment of this disclosure;
[0075] Figure 9 is a signaling interaction diagram of another computing resource awareness method provided in an embodiment of this disclosure;
[0076] Figure 10 is a signaling interaction diagram of another computing resource awareness method provided in an embodiment of this disclosure;
[0077] Figure 11 is a structural block diagram of a computing resource sensing device provided in an embodiment of this disclosure;
[0078] Figure 12 is a structural block diagram of another computing resource sensing device provided in an embodiment of this disclosure;
[0079] Figure 13 is a structural block diagram of another computing resource sensing device provided in an embodiment of this disclosure;
[0080] Figure 14 is a structural block diagram of another computing resource sensing device provided in an embodiment of this disclosure;
[0081] Figure 15 is a structural block diagram of another computing resource sensing device provided in an embodiment of this disclosure;
[0082] Figure 16 is a structural block diagram of another computing resource sensing device provided in an embodiment of this disclosure. Detailed Implementation
[0083] The embodiments of the technical solutions disclosed herein will now be described in detail with reference to the accompanying drawings. These embodiments are merely illustrative of the technical solutions disclosed herein and are therefore intended to limit the scope of protection of this disclosure.
[0084] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs; the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of this disclosure; the terms “comprising” and “having”, and any variations thereof, in the specification, claims and foregoing description of the drawings of this disclosure are intended to cover non-exclusive inclusion.
[0085] In the description of the embodiments of this disclosure, technical terms such as "first" and "second" are used only to distinguish different objects and should not be construed as indicating or implying relative importance or implicitly specifying the number, specific order, or primary or secondary relationship of the indicated technical features. In the description of the embodiments of this disclosure, "a plurality of" means two or more, unless otherwise explicitly defined.
[0086] In this document, the term "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this disclosure. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.
[0087] In the description of the embodiments of this disclosure, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.
[0088] In the description of the embodiments of this disclosure, the term "multiple" refers to two or more (including two), similarly, "multiple groups" refers to two or more (including two groups), and "multiple pieces" refers to two or more (including two pieces).
[0089] In the description of the embodiments of this disclosure, the technical terms "center," "longitudinal," "lateral," "length," "width," "thickness," "upper," "lower," "front," "rear," "left," "right," "vertical," "horizontal," "top," "bottom," "inner," "outer," "clockwise," "counterclockwise," "axial," "radial," and "circumferential" indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings. They are only for the convenience of describing the embodiments of this disclosure and simplifying the description, and are not intended to indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, they should not be construed as limitations on the embodiments of this disclosure.
[0090] In the description of the embodiments of this disclosure, unless otherwise expressly specified and limited, technical terms such as "installation," "connection," "joining," and "fixing" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral part; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; they can refer to the internal communication of two components or the interaction between two components. Those skilled in the art can understand the specific meaning of the above terms in the embodiments of this disclosure according to the specific circumstances.
[0091] The computing resource awareness method, apparatus, and processor-readable storage medium provided in this disclosure can improve the quality of computing services.
[0092] The method and apparatus are based on the same disclosed concept. Since the methods and apparatus solve problems in similar ways, the implementation of the apparatus and methods can refer to each other, and repeated parts will not be described again.
[0093] The relevant technologies will be explained below.
[0094] Computing power networks can share computing resources with computing power consumers, thereby efficiently utilizing idle computing resources while obtaining the benefits of sharing them. When computing resources are provided, the resource owner is unaware of the resource consumer consuming the computing resources, and the resource consumer is also unaware of the resource owner providing the computing resources.
[0095] The aforementioned computing power network may include computing power networks oriented towards the bearer network and mobile computing power networks.
[0096] Because 6G networks integrate computing power with the network itself, providing computing services by opening up computing resources through mobile communication networks will inevitably become a development trend. For example, computing resources can be opened up using the Common API Framework Architecture (CAPIF) architecture of mobile communication networks.
[0097] Figure 1 is a schematic diagram of a CAPIF architecture provided in related technologies. The CAPIF architecture shown in Figure 1 includes an API invoker, a CAPIF provider, and an API provider. The API invoker and the CAPIF provider interact through a service protocol, and the CAPIF provider and the API provider interact through a service API protocol.
[0098] Figure 2 is a schematic diagram of another CAPIF architecture provided in the related technology. Compared with Figure 1, the CAPIF architecture shown in Figure 2 adds a resource owner, which can grant access to protected resources related to resources exposed by the API provider.
[0099] It should be understood that the API caller and the resource owner mentioned above can be the same entity or two separate entities. The resource owner can be a user of the terminal device, who can use the terminal device to provide authorization information.
[0100] However, current Radio Access Network Slicing Assistance Information (RNAA) for mobile communication networks is limited to terminal devices, and its resources are limited to network resources, such as the terminal device's location information and network information, excluding computing resources. Current computing networks lack content regarding resource owners' and consumers' perception of computing resources. Consequently, when opening computing resources through mobile communication networks, there may be situations where resource-consuming devices accidentally access computing resources, or resource providers arbitrarily modify computing resources. This leads to problems such as service interruptions and failure to meet service requirements, resulting in poor service quality for current computing services.
[0101] To address the aforementioned issues, embodiments of this disclosure provide a computing resource awareness method, apparatus, and processor-readable storage medium. Through a first resource call awareness message, the resource-owning device providing the target computing resource is made aware of the call to the computing resource. Furthermore, through a resource call control message, the resource-owning device controls the call to the target computing resource. This prevents the resource-owning device from unauthorized access to the target computing resource, ensuring that the computing service meets business needs and thereby improving the service quality of the computing service.
[0102] The following describes the application scenarios of the computing resource awareness method provided in the embodiments of this disclosure.
[0103] Figure 3 illustrates an application scenario of a computing resource awareness method provided in this embodiment. As shown in Figure 3, there is interaction between the resource-owning device and the second network functional entity, interaction between the second network functional entity and the first network functional entity, and interaction between the first network functional entity and the resource-calling device.
[0104] In this context, the resource-owning device can be a combined entity of a computing resource provider and a computing resource owner, eliminating the distinction between the two. The resource-owning device can authorize resource-calling devices that access its computing service information via APIs. For the 6G network architecture, to enable network management of computing resources and orchestration of computing services, a new Computing Control Function (CCF) network element has been added to the core network. This CCF element can act as a logical resource-owning device and interact with other entities.
[0105] The first network function entity can be an entity that deploys the core functions of CAPIF and provides an open API to the resource-invoking device. For example, the first network function entity can be a Network Exposure Function (NEF) network element, a Service Capability Exposure Function (SCEF) network element, or a Computing Exposure Function (CEF) network element added to implement the open computing service API, etc.
[0106] The second network function entity can be the entity corresponding to the API provider. The second network function entity can host one or more computing service APIs and sign a service API agreement with the first network function entity to provide computing service APIs to resource-invoking devices. The second network function entity can provide functions such as API opening, API publishing, and API management, and can also extend the functions of publishing, managing, and opening computing service APIs.
[0107] Resource invocation devices can be entities corresponding to computing resource consumers or API callers. Computing resource consumers can use computing services provided by the network and obtain information about open computing resources through the CAPIF framework. API callers sign service agreements with CAPIF providers and can use CAPIF APIs and service APIs. API callers can extend and enhance the calling computing service APIs.
[0108] The computing resource information may include at least one of computing node information and computing service information. A computing node can be a logical node that provides computing capabilities, and the types of computing nodes include, but are not limited to: terminal devices, Radio Access Network (RAN) devices, Network Function (NF) elements in the core network, Mobile Edge Computing (MEC) devices, cloud servers, servers, Central Processing Units (CPUs), Graphics Processing Units (GPUs), etc.
[0109] The technical solutions of the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this disclosure, and not all embodiments. Based on the embodiments of this disclosure, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this disclosure.
[0110] In one embodiment, as shown in Figure 4, a flowchart of a computing resource awareness method is provided to illustrate how resource-owning devices can be aware of computing resource calls. This computing resource awareness method is applied to resource-owning devices and includes steps S201-S202:
[0111] S201, Receive the first resource call awareness message sent by the first network function entity.
[0112] In this disclosure, when a resource-invoking device invokes the computing service API of a target computing resource, it can send a first resource invoking awareness message to the resource-owning device through a first network function entity, thereby enabling the resource-owning device to be aware of the invoking of the target computing resource's computing service API.
[0113] The first resource invocation awareness message is used to indicate the invocation of the computing service API of the target computing resource, which is the computing resource provided by all devices of the resource.
[0114] For example, the resource-invoking device can send a resource invoking request message for the computing service API of the target computing resource to the first network function entity. Subsequently, the first network function entity identifies whether the target computing resource is a protected computing resource. If the target computing resource is identified as a protected computing resource, the first network function entity sends a first resource invoking awareness message to the resource-owning device. If the target computing resource is identified as an unprotected computing resource, the first network function entity directly instructs the resource-invoking device to invoke the computing service API. That is, for unprotected computing resources, the resource-invoking device can directly invoke them; for protected computing resources, the resource-owning device needs to be aware of and control the invoking of the computing service API.
[0115] For example, the resource request message may include the identifier of the resource requesting device and the identifier of the computing service API of the target computing resource. Upon receiving the resource request message, the resource requesting device can also verify its identity based on its identifier. If the resource requesting device's authentication is successful, it can then determine whether the computing resource is protected based on the identifier of the computing service API of the target computing resource.
[0116] In some embodiments, the aforementioned first resource invocation awareness message includes authorization request information for the resource invocation device to invoke the computing service API. That is, when the computing service API of the protected computing resource is invoked, not only can the resource-owning device be notified, but the resource-owning device can also authorize the invocation, thereby further preventing the target computing resource on the resource-owning device from being accessed accidentally.
[0117] Accordingly, the aforementioned first resource invocation awareness message may also include the identifier of the resource invocation device and the identifier of the target computing resource's computing service API. Through the identifier of the resource invocation device and the identifier of the target computing resource's computing service API, all devices can accurately perceive which device wants to invoke which computing resource's computing service API, thereby more accurately determining whether to authorize the resource invocation device to invoke the computing service API.
[0118] S202, Send a resource call control message for the computing service API to the first network function entity.
[0119] In this step, after all the devices that own the resources receive the first resource call awareness message, they can send a resource call control message for the computing service API to the first network function entity to control the call to the computing service API of the target computing resource.
[0120] In some embodiments, where the first resource call awareness message includes authorization request information for the computing service API, the resource call control message includes authorization indication information for the resource call device to call the computing service API. That is, the call to the computing service API is controlled by a resource call control message indicating whether authorization is granted.
[0121] For example, the authorization indication information described above can indicate whether authorization was successful or failed. When the authorization indication information indicates successful authorization, the resource-invoking device can invoke the computing service API of the template computing resource. When the authorization indication information indicates failed authorization, the resource-invoking device is prohibited from invoking the computing service API of the template computing resource.
[0122] In some embodiments, the authorization instruction information may also include additional information. If the authorization instruction information indicates successful authorization, then the authorization instruction information includes authorization condition information. Alternatively, if the authorization instruction information indicates authorization failure, then the authorization instruction information includes authorization failure reason information.
[0123] The authorization conditions mentioned above include at least one of the following: the number of valid calls to the computing service API by the resource calling device and the valid time period.
[0124] For example, the authorization condition information can indicate that the resource-invoking device can only call the target computing resource's computing service API once. Alternatively, the authorization condition information can indicate that the resource-invoking device can call the target computing resource's computing service API N times, meaning the resource-invoking device can call the target resource's computing service API N times without needing to re-authorize N times, where N is an integer greater than or equal to 1. Finally, the authorization condition information can indicate the valid time for the resource-invoking device to call the target computing resource's computing service API, meaning that within the valid time, the resource-invoking device can directly access the target computing resource's computing service API without needing to re-authorize.
[0125] In some embodiments, after receiving a resource access control message, the first network function entity may send the resource access control message to a resource access device. If the authorization indication information in the resource access control message indicates successful authorization, the resource access device may invoke the computing service API of the target computing resource to obtain information on the computing services that can be opened on the network.
[0126] The computing service information includes at least one of the following: computing service identifier, computing service type, computing service service time, computing service service scope, and computing resource protection instructions.
[0127] The computing resource awareness method provided in this embodiment involves a resource-owning device receiving a first resource call awareness message from a first network function entity. This message indicates a call to a computing service API of a target computing resource, which is a computing resource provided by the resource-owning device. Subsequently, the resource-owning device sends a resource call control message for the computing service API to the first network function entity. By using the first resource call awareness message to allow the resource-owning device providing the target computing resource to be aware of the computing resource call, and by using the resource call control message to control the call to the target computing resource, the resource-owning device can be protected from unauthorized access to the target computing resource. This ensures that the computing service meets business needs and improves the quality of service.
[0128] The interaction between the resource-owning devices, the first network function entity, and the resource-calling device during the process of calling the target computing resource is described below. Figure 5 is a signaling interaction diagram of a computing resource awareness method provided in an embodiment of this disclosure. As shown in Figure 5, the computing resource awareness method includes S301-S306:
[0129] S301, The resource retrieval device sends a first resource retrieval request message for the computing service API of the target computing resource to the first network function entity.
[0130] The target computing resource refers to the computing resources provided by all devices that own the resource. The first resource request message may include the identifier of the device requesting the resource and the identifier of the computing service API of the target computing resource.
[0131] In some embodiments, after receiving a resource request message, the resource requesting device can also verify its identity based on its identifier. Once the resource requesting device is successfully authenticated, the identifier of the target computing resource's computing service API is used to further identify whether the computing resource is protected.
[0132] S302, The first network functional entity determines whether the target computing resource is a protected computing resource.
[0133] If yes, then execute S303; otherwise, execute S306.
[0134] S303, The first network function entity sends a first resource call awareness message to all devices of the resource. The first resource call awareness message is used to indicate the call to the computing service API of the target computing resource.
[0135] In some embodiments, the aforementioned first resource invocation awareness message includes authorization request information for the resource invocation device to invoke the computing service API. That is, when the computing service API of the protected computing resource is invoked, not only can the resource-owning device be notified, but the resource-owning device can also authorize the invocation, thereby further preventing the target computing resource on the resource-owning device from being accessed accidentally.
[0136] In some embodiments, the first resource call awareness message may further include the identifier of the resource call device and the identifier of the computing service API of the target computing resource.
[0137] For example, by using the identifier of the resource-calling device and the identifier of the computing service API of the target computing resource, all devices can accurately perceive which device wants to call the computing service API of which computing resource, thereby more accurately determining whether to authorize the resource-calling device to call the computing service API.
[0138] S304. All resource devices send resource call control messages for the computing service API to the first network function entity.
[0139] In some embodiments, where the first resource call awareness message includes authorization request information for the computing service API, the resource call control message includes authorization indication information for the resource call device to call the computing service API. That is, the call to the computing service API is controlled by a resource call control message indicating whether authorization is granted.
[0140] In some embodiments, the authorization instruction information may indicate authorization success or authorization failure. If the authorization instruction information indicates authorization success, then the authorization instruction information includes authorization condition information. Alternatively, if the authorization instruction information indicates authorization failure, then the authorization instruction information includes authorization failure reason information.
[0141] The authorization conditions mentioned above include at least one of the following: the number of valid calls to the computing service API by the resource calling device and the valid time period.
[0142] S305. The first network function entity sends a resource call control message for the computing service API to the resource call device.
[0143] S306. Resource call device calls the computing service API of the target computing resource.
[0144] In some embodiments, if the authorization indication information in the resource call control message indicates successful authorization, the resource call device can call the computing service API of the target computing resource to obtain information on the computing services that can be opened on the network.
[0145] The computing service information includes at least one of the following: computing service identifier, computing service type, computing service service time, computing service service scope, and computing resource protection instructions.
[0146] The following describes how the resource-owning device revokes the resource-calling device's authorization to call the computing service API. Figure 6 is a signaling interaction diagram of another computing resource awareness method provided in this embodiment of the disclosure. As shown in Figure 6, this computing resource awareness method includes S401-S408:
[0147] S401, The resource retrieval device sends a first resource retrieval request message for the computing service API of the target computing resource to the first network function entity.
[0148] S402. When the target computing resource is a protected computing resource, the first network function entity sends an authorization request to all devices that call the resource to call the computing service API.
[0149] S403. All resource devices send authorization instructions to the first network function entity for the resource calling device to call the computing service API. The authorization instructions indicate that the authorization was successful.
[0150] S404. The first network function entity sends an authorization instruction message to the resource calling device for calling the computing service API. The authorization instruction message indicates that the authorization was successful.
[0151] S405. All resource devices send an authorization revocation instruction message for the Computing Service API to the first network function entity.
[0152] In some embodiments, when the resource-owning device determines that it will no longer authorize the resource-calling device, it may send an authorization revocation instruction message for the computing service API to the first network function entity, instructing the first network function entity to revoke the resource-calling device's authorization to call the computing service API.
[0153] The aforementioned authorization revocation instruction message may include the identifier of the resource-invoking device and the identifier of the target resource's computing service API, thereby instructing the resource-invoking device to revoke the authorization and the computing service API whose authorization was revoked by the resource-invoking device.
[0154] In some embodiments, the authorization revocation instruction message may further include authorization revocation condition information, which may include time period information, that is, the authorization of the resource calling device to the computing service API is revoked during the time period, and the authorization of the resource calling device to the computing service API is maintained outside the time period.
[0155] S406. The first network function entity revokes the authorization for the resource calling device to call the computing service API based on the authorization revocation request message.
[0156] In some embodiments, the authorization revocation instruction message may include an identifier of the resource-invoking device and an identifier of the computing service API of the target resource. Accordingly, the first network function entity may revoke the resource-invoking device's authorization to invoke the computing service API based on the identifier of the resource-invoking device and the identifier of the computing service API of the target resource.
[0157] S407. The first network function entity sends an authorization revocation notification message for the computing service API to the resource calling device.
[0158] S408. The first network function entity sends a message to all devices of the resource indicating that the authorization revocation of the computing service API has been successful.
[0159] It should be understood that after the authorization is successfully revoked, the resource-invoking device cannot continue to call the computing service API. When the resource-invoking device needs to continue to obtain computing service information from the computing service API, it can send a resource invoking request message to the first network function entity again to initiate the authorization process for calling the computing service API.
[0160] In this embodiment of the disclosure, by having the resource-owning device actively send an authorization revocation instruction message for the computing service API, the resource-owning device revokes the authorization of the resource-calling device, thereby realizing the control of the resource-owning device over the calling of computing resources.
[0161] The following describes how to register the computing service API for the target computing resource. Figure 7 is a signaling interaction diagram of another computing resource awareness method provided in this embodiment of the present disclosure. As shown in Figure 7, the computing resource awareness method includes S501-S508:
[0162] S501. All devices of the resource send a registration request message to the second network function entity. The registration request message is used to request the registration of the computing service API of the target computing resource.
[0163] In this disclosure, the computing resources on all devices of the resource can be exposed by registering the computing service API of the target computing resource, so that the resource calling devices can call the corresponding computing service API.
[0164] The computing resources include computing nodes on the target computing resources and computing service information deployed on the computing nodes.
[0165] In some embodiments, the registration request message may include at least one of the following registration information: the identifier of the computing service API, information of all devices owning the resource, the access address of the computing service API, the computing node information corresponding to the computing service API, and the computing service information corresponding to the computing service API.
[0166] The information of all resource-owned devices may include at least one of the names and identifiers of the resource-owned devices; the access address of the computing service API may be the Uniform Resource Locator for the computing service API; and the computing node information corresponding to the computing service API may include the computing node identifier, computing node type, etc.
[0167] In some embodiments, the computing service information includes at least one of the following: computing service identifier, computing service type, computing service service time, computing service service scope, and computing resource protection instruction information.
[0168] It should be understood that the protection indication information for the aforementioned computing resources is used to indicate whether they are protected computing resources.
[0169] S502, the second network function entity sends a publish request message to the first network function entity.
[0170] In some embodiments, after receiving a registration request message, the second network function entity may first authenticate the registration permissions of all devices related to the resource. After successful authentication, the second network function entity may send a publication request message to the first network function entity.
[0171] The release request message includes information about all devices with resources and information about the computing service API of the target computing resource.
[0172] For example, the information for resource-owned devices may include at least one of the name and identifier of whether extended support for resource-owned devices is available.
[0173] For example, the information of the computing service API includes at least one of the following: computing service API identifier, computing service API type, communication type corresponding to the computing service API, interface information corresponding to the computing service API, protocol information corresponding to the computing service API, data format information corresponding to the computing service API, computing node information corresponding to the computing service API, and computing service information corresponding to the computing service API.
[0174] The aforementioned computing service API type can also be a computing service type; the aforementioned interface information may include IP address, port number, Uniform Resource Identifier (URI), etc.; the aforementioned computing service API corresponding protocol information may include protocol identifier and version number.
[0175] The computing service information includes at least one of the following: computing service identifier, computing service type, computing service service time, computing service service scope, and computing resource protection instructions.
[0176] S503. The first network function entity registers the computing service API of the target computing resource to the API service list of the first network function entity according to the publish request message.
[0177] In some embodiments, when a first network function entity receives a publish request message, the first network function entity may check whether a second network function entity is authorized to publish the service API.
[0178] For example, if it is found that the second network function entity is authorized to publish service APIs, the first network function entity registers the computing service API of the target computing resource to the API service list of the first network function entity based on the information in the publish request message.
[0179] The API service list includes at least one computing service API that can be invoked by resource-invoking devices.
[0180] S504. The first network function entity sends a publish response message to the second network function entity.
[0181] The response message indicates whether the computing service API was published successfully or failed to be published.
[0182] S505, the second network function entity sends a registration response message to the first network function entity.
[0183] The response message indicates whether the Computing Service API registration was successful or failed.
[0184] S505, The resource retrieval device sends a first resource retrieval request message for the computing service API of the target computing resource to the first network function entity.
[0185] S506. When the target computing resource is a protected computing resource, the first network function entity sends an authorization request to all devices that call the resource to call the computing service API.
[0186] S507. All resource devices send authorization instructions to the first network function entity for the resource calling device to call the computing service API.
[0187] S508, The first network function entity sends authorization instruction information to the resource calling device.
[0188] It should be understood that when the computing service information of all devices in the computing resources changes, all devices in the computing resources can send an update request to the second network function entity. This request carries the updated computing service information. The second network function entity can then synchronize the updated computing service information to the first network function entity so that the second network function entity can maintain the latest available computing service APIs. The process of updating computing service information is similar to the registration process of computing service APIs, and will not be described in detail here.
[0189] The following describes how resource callers can perceive changes to computing resources. Figure 8 is a signaling interaction diagram of another computing resource perception method provided in this embodiment of the disclosure. As shown in Figure 8, this computing resource perception method includes S601-S602:
[0190] S601. All devices of the resource send a resource change notification message for the target resource to the first network function entity.
[0191] The resource change notification message is used to trigger the second resource call awareness message, which is used to indicate whether at least one of the target computing resource and the computing service API of the target computing resource has changed.
[0192] In some embodiments, the target computing resources may include computing nodes, computing services, computing service information, etc.
[0193] In some embodiments, if the second resource invocation awareness message indicates that at least one of the target computing resource and the computing service API of the target computing resource has changed, then the second resource invocation awareness message includes the changed target computing resource and at least one of the computing service API of the target computing resource.
[0194] It should be understood that the embodiments of this disclosure do not limit the resource ownership device from sending the resource change notification message of the target resource to the first network function entity. In some embodiments, the resource ownership device may first send the resource change notification message to the second network function entity, and then the second network function entity may send the resource change notification message to the first network function entity.
[0195] S602, The first network function entity sends a second resource call perception message to the resource call device.
[0196] The second resource invocation awareness message is used to indicate whether at least one of the target computing resource and the computing service API of the target computing resource has changed.
[0197] In this disclosure, by sending a second resource access awareness message to the resource access device, the resource access device can be promptly informed of changes in computing resources, reducing the likelihood of changes at business terminals and thereby improving the service quality of computing services.
[0198] The resource-requesting device can be either a device that has subscribed to the target computing resource or a device that is currently using the target computing resource.
[0199] In some embodiments, when the resource invocation device is a subscribed device of the target computing resource, the resource invocation device invokes the computing service API of the target computing resource according to the update indication information in the second resource invocation awareness message to obtain the target computing resource.
[0200] In some embodiments, when the resource-requesting device is the device currently using the target computing resource, the second resource-requesting awareness message also includes the identification information of the resource-requesting device. In this case, the resource-requesting device can determine the change confirmation result of the computing service API of the target computing resource. Subsequently, the resource-requesting device sends a change response message corresponding to the second resource-requesting awareness message to the first network function entity, the change response message including the change confirmation result.
[0201] The aforementioned change confirmation result is used to indicate whether the resource-calling device agrees to change the target resource.
[0202] For example, if the target resource is changed with consent, the resource retrieval device will call the computing service API of the target computing resource according to the update instruction information in the second resource retrieval perception message to obtain the target computing resource.
[0203] For example, if the target resource is refused to be changed, the first network function entity sends a resource recovery instruction message to the resource-owning device, and the resource-owning device restores at least one of the changed target computing resource and the computing service API of the target computing resource based on the resource recovery instruction message.
[0204] Figure 9 is a signaling interaction diagram of another computing resource awareness method provided in this embodiment of the present disclosure. As shown in Figure 9, the computing resource awareness method includes S701-S703:
[0205] S701. All devices of the resource send a resource change notification message for the target resource to the first network function entity.
[0206] The resource change notification message is used to trigger the second resource call awareness message, which is used to indicate whether at least one of the target computing resource and the computing service API of the target computing resource has changed.
[0207] S702, The first network function entity sends a second resource call perception message to the resource call device.
[0208] S703. When the resource calling device is a subscribed device of the target computing resource, the resource calling device calls the computing service API of the target computing resource according to the update indication information in the second resource calling perception message to obtain the target computing resource.
[0209] Figure 10 is a signaling interaction diagram of another computing resource awareness method provided in this embodiment of the present disclosure. As shown in Figure 10, the computing resource awareness method includes S801-S805:
[0210] S801. All devices of the resource send a resource change notification message for the target resource to the first network function entity.
[0211] The resource change notification message is used to trigger the second resource call awareness message, which is used to indicate whether at least one of the target computing resource and the computing service API of the target computing resource has changed.
[0212] S802, The first network function entity sends a second resource call perception message to the resource call device.
[0213] S803. When the resource-invoking device is the device currently using the target computing resource, the resource-invoking device determines whether the change confirmation result of the computing service API of the target computing resource is "agree to change".
[0214] If yes, then execute S804; otherwise, execute S805.
[0215] S804. The resource retrieval device then calls the computing service API of the target computing resource according to the update indication information in the second resource retrieval perception message to obtain the target computing resource.
[0216] S805, The resource-requesting device sends a resource recovery instruction message to all devices that own the resource.
[0217] The resource recovery request message is used to request the recovery of at least one of the target computing resource and the computing service API of the target computing resource.
[0218] In some embodiments, the resource recovery instruction message includes at least one of the target computing resource before the change and the computing service API of the target computing resource.
[0219] In some embodiments, the resource consuming device may also update the configuration of computing resources, or trigger a computing session update process initiated by a computing resource consumer to the network.
[0220] In this embodiment of the disclosure, when the computing resources subscribed to or currently used by a resource-invoking device change, the resource-invoking device senses the second resource-invoking sensing message and provides feedback on whether it agrees to the change. If necessary, it may trigger a configuration update of the computing service or re-initiate a computing service policy update request to the network to obtain better computing services or ensure the continuity and quality of computing services.
[0221] It should be understood that although the steps in the flowcharts of the above embodiments are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the above embodiments may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.
[0222] Based on the same concept, this disclosure also provides a computing resource sensing device for implementing the computing resource sensing method described above. The solution provided by this device is similar to the implementation described in the above method; therefore, the specific limitations in one or more computing resource sensing device embodiments provided below can be found in the limitations of the computing resource sensing method described above, and will not be repeated here.
[0223] In one embodiment, as shown in FIG11, a computing resource sensing device 900 is provided, which is applied to resource-owning devices. The computing resource sensing device 900 includes a first receiving module 901 and a first transmitting module 902.
[0224] The first receiving module 901 is used to receive a first resource call perception message sent by the first network function entity. The first resource call perception message is used to indicate the call to the computing service API of the target computing resource. The target computing resource is the computing resource provided by all devices of the resource.
[0225] The first sending module 902 is used to send resource call control messages for the computing service API to the first network function entity.
[0226] In one embodiment, the first resource call awareness message includes authorization request information for the resource call device to call the computing service API; the resource call control message includes authorization indication information for the resource call device to call the computing service API.
[0227] In one embodiment, if the authorization instruction information indicates successful authorization, the authorization instruction information includes authorization condition information; or, if the authorization instruction information indicates authorization failure, the authorization instruction information includes authorization failure reason information.
[0228] In one embodiment, the authorization condition information includes at least one of the following: the number of valid calls to the computing service API by the resource calling device and the valid time period.
[0229] In one embodiment, the first sending module 902 is further configured to send an authorization revocation indication message for the computing service API to the first network function entity, the authorization revocation indication message being used to instruct the first network function entity to revoke the authorization for the resource calling device to call the computing service API;
[0230] The first receiving module 901 is also used to receive a successful authorization revocation message for the computing service API sent by the first network function entity.
[0231] In one embodiment, the first sending module 902 is further configured to send a registration request message to the second network function entity, the registration request message being used to request the registration of the computing service API of the target computing resource.
[0232] In one embodiment, the registration request message includes at least one of the following registration information: the identifier of the computing service API, information of all devices owning the resource, the access address of the computing service API, the computing node information corresponding to the computing service API, and the computing service information corresponding to the computing service API.
[0233] In one embodiment, the computing service information includes at least one of the following: computing service identifier, computing service type, computing service service time, computing service service scope, and computing resource protection indication information.
[0234] In one embodiment, the first sending module 902 is further configured to send a resource change notification message of the target resource to the first network function entity. The resource change notification message is used to trigger a second resource call awareness message. The second resource call awareness message is used to indicate whether at least one of the target computing resource and the computing service API of the target computing resource has changed.
[0235] In one embodiment, the first receiving module 901 is further configured to receive a resource recovery instruction message sent by the first network function entity, wherein the resource recovery request message is used to request the recovery of at least one of the target computing resource and the computing service API of the target computing resource.
[0236] In one embodiment, as shown in FIG12, a computing resource sensing device 1000 is provided, which is applied to a first network functional entity. The computing resource sensing device 1000 includes a second receiving module 1001 and a second sending module 1002.
[0237] The second receiving module 1001 is used to receive a resource call request message for a target computing resource's computing service API sent by a resource calling device, wherein the target computing resource is a computing resource provided by all the resource-owning devices; and to receive resource call control messages for the computing service API sent by all the resource-owning devices through a transceiver.
[0238] The second sending module 1002 is used to send a first resource call awareness message to all devices of the resource through a transceiver when the target computing resource is a protected computing resource. The first resource call awareness message is used to indicate the call to the computing service API of the target computing resource.
[0239] In one embodiment, the second sending module 1002 is further configured to send a resource call control message to a resource call device.
[0240] In one embodiment, the first resource call awareness message includes authorization request information for the resource call device to call the computing service API; the resource call control message includes authorization indication information for the resource call device to call the computing service API.
[0241] In one embodiment, if the authorization instruction information indicates successful authorization, the authorization instruction information includes authorization condition information; or, if the authorization instruction information indicates authorization failure, the authorization instruction information includes authorization failure reason information.
[0242] In one embodiment, the authorization condition information is used to indicate at least one of the valid number of times and the valid time for the resource calling device to call the computing service API.
[0243] In one embodiment, the second receiving module 1001 is further configured to receive an authorization revocation request message for the computing service API sent by all devices of the resource;
[0244] The computing resource sensing device 1000 also includes a second processing module, used to revoke the authorization for the resource calling device to call the computing service API according to the authorization revocation request message;
[0245] The second sending module 1002 is also used to send an authorization revocation notification message for the computing service API to the resource calling device; and to send an authorization revocation success message for the computing service API to all resource devices.
[0246] In one embodiment, the second receiving module 1001 is further configured to receive a publish request message sent by the second network function entity;
[0247] The second processing module is also used to register the computing service API of the target computing resource to the API service list of the first network function entity according to the release request message. The API service list includes at least one computing service API that can be requested and invoked by the resource calling device.
[0248] In one embodiment, the publish request message includes information about all devices with resources and information about the computing service API of the target computing resource.
[0249] In one embodiment, the information of the computing service API includes at least one of the following: computing service API identifier, computing service API type, communication type corresponding to the computing service API, interface information corresponding to the computing service API, protocol information corresponding to the computing service API, data format information corresponding to the computing service API, computing node information corresponding to the computing service API, and computing service information corresponding to the computing service API.
[0250] In one embodiment, the computing service information includes at least one of the following: computing service identifier, computing service type, computing service service time, computing service service scope, and computing resource protection indication information.
[0251] In one embodiment, the second receiving module 1001 is further configured to receive a resource change notification message for the target resource sent by all devices of the resource;
[0252] The second sending module 1002 is further configured to send a second resource call awareness message to the resource call device, the second resource call awareness message being used to indicate whether at least one of the target computing resource and the computing service API of the target computing resource has changed.
[0253] In one embodiment, if the resource calling device is the device currently using the target computing resource, the second resource calling awareness message also includes the identification information of the resource calling device; the second receiving module 1001 is further configured to receive a change response message corresponding to the second resource calling awareness message sent by the resource calling device, the change response message including the change confirmation result of the computing service API of the target computing resource.
[0254] In one embodiment, if the change confirmation result is a rejection of the change, the second sending module 1002 is further configured to send a resource recovery instruction message to all resource-owning devices, wherein the resource recovery request message is used to request the recovery of at least one of the target computing resource and the computing service API of the target computing resource.
[0255] In one embodiment, as shown in FIG13, a computing resource sensing device 1100 is provided, which is applied to a resource calling device. The computing resource sensing device 1100 includes a third sending module 1101 and a third receiving module 1102.
[0256] The third sending module 1101 is used to send a first resource call request message of the computing service API of the target computing resource to the first network function entity. The target computing resource is the computing resource provided by all devices of the resource.
[0257] The third receiving module 1102 is used to receive resource call control messages for the computing service API sent by the first network function entity.
[0258] In one embodiment, the first resource call awareness message includes authorization request information for the resource call device to call the computing service API; the resource call control message includes authorization indication information for the resource call device to call the computing service API.
[0259] In one embodiment, if the authorization instruction information indicates successful authorization, the authorization instruction information includes authorization condition information; or, if the authorization instruction information indicates authorization failure, the authorization instruction information includes authorization failure reason information.
[0260] In one embodiment, the authorization condition information includes at least one of the following: the number of valid calls to the computing service API by the resource calling device and the valid time period.
[0261] In one embodiment, the third receiving module 1102 is further configured to receive a second resource call awareness message sent by the first network function entity, the second resource call awareness message being used to indicate whether at least one of the target computing resource and the computing service API of the target computing resource has changed.
[0262] In one embodiment, when the resource calling device is a subscribed device of the target computing resource, the computing resource sensing device 1100 further includes: a third processing module, used to call the computing service API of the target computing resource according to the update indication information in the second resource calling sensing message, and obtain the target computing resource.
[0263] In one embodiment, if the resource calling device is the device currently using the target computing resource, the second resource calling awareness message also includes the identification information of the resource calling device; the third processing module is further used to determine the change confirmation result of the computing service API of the target computing resource;
[0264] The third sending module 1101 is also used to send a change response message corresponding to the second resource call perception message to the first network function entity. The change response message includes a change confirmation result.
[0265] In one embodiment, if the change confirmation result is "agree to change", the third processing module is further configured to continue to call the computing service API of the target computing resource to obtain the target computing resource according to the update indication information in the second resource call perception message.
[0266] In one embodiment, if the change confirmation result is a rejection of the change, the change response message is used to trigger a resource recovery indication message, and the resource recovery request message is used to request the recovery of at least one of the target computing resource and the computing service API of the target computing resource.
[0267] In one embodiment, this disclosure also provides a computing resource sensing device applied to a resource requisition device, the computing resource sensing device comprising: a third sending module and a first processing module.
[0268] The third sending module is used to receive a second resource call awareness message sent by the first network function entity. The second resource call awareness message is used to indicate whether at least one of the target computing resource and the computing service API of the target computing resource has changed.
[0269] The first processing module is used to process the call to the computing service API of the target computing resource based on the second resource call perception message.
[0270] In one embodiment, if the resource-calling device is a subscribed device for the target computing resource, the method further includes:
[0271] Based on the update indication information in the second resource call awareness message, the computing service API of the target computing resource is called to obtain the target computing resource.
[0272] In one embodiment, if the resource calling device is the device currently using the target computing resource, the second resource calling awareness message also includes the identification information of the resource calling device; the first processing module is further configured to determine the change confirmation result of the computing service API of the target computing resource;
[0273] The third sending module is also used to send a change response message corresponding to the second resource call perception message to the first network function entity. The change response message includes a change confirmation result.
[0274] In one embodiment, if the change confirmation result is "agree to change", the first processing module is further configured to continue to call the computing service API of the target computing resource to obtain the target computing resource according to the update indication information in the second resource call perception message.
[0275] In one embodiment, if the change confirmation result is a rejection of the change, the change response message is used to trigger a resource recovery indication message, and the resource recovery request message is used to request the recovery of at least one of the target computing resource and the computing service API of the target computing resource.
[0276] In one embodiment, this disclosure also provides a computing resource awareness device applied to a first network functional entity, the computing resource awareness device comprising: a second receiving module and a second transmitting module.
[0277] The second receiving module is used to receive resource change notification messages for the target resource sent by all devices of the resource.
[0278] The second sending module is used to send a second resource call awareness message, which is used to indicate whether at least one of the target computing resource and the computing service API of the target computing resource has changed.
[0279] In one embodiment, if the resource calling device is the device currently using the target computing resource, the second resource calling awareness message also includes the identification information of the resource calling device; the second receiving module is used to receive the change response message corresponding to the second resource calling awareness message sent by the resource calling device, the change response message including the change confirmation result of the computing service API of the target computing resource.
[0280] In one embodiment, if the change confirmation result is a rejection of the change, the second sending module is used to send a resource recovery instruction message to all devices of the resource, and the resource recovery request message is used to request the recovery of at least one of the target computing resource and the computing service API of the target computing resource.
[0281] In one embodiment, this disclosure also provides a computing resource sensing device applied to resource-owning devices, the computing resource sensing device comprising: a second processing device and a first transmitting device.
[0282] The second processing device is used to generate a resource change notification message for the target resource. The resource change notification message triggers a second resource call awareness message, which indicates whether at least one of the target computing resource and the computing service API of the target computing resource has changed.
[0283] The first transmitting device is used to send a resource change notification message to the first network function entity.
[0284] In one embodiment, the computing resource awareness device further includes:
[0285] The second processing module is used to receive a resource recovery instruction message sent by the first network function entity, and the resource recovery request message is used to request the recovery of at least one of the target computing resource and the computing service API of the target computing resource.
[0286] It should be noted that the apparatus provided in this embodiment can implement all the method steps implemented in the above method embodiment and can achieve the same technical effect. Therefore, the parts and beneficial effects that are the same as those in the method embodiment will not be described in detail here.
[0287] It should be noted that the module division in this embodiment is illustrative and represents only one logical functional division; in actual implementation, other division methods may be used. Furthermore, the functional modules in the various embodiments of this disclosure can be integrated into one processing module, or each module can exist physically separately, or two or more modules can be integrated into one module. The integrated modules described above can be implemented in hardware or as software functional modules.
[0288] If the integrated module is implemented as a software functional module and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of this disclosure, in essence, or the part that contributes to the related technology, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods of the various embodiments of this disclosure.
[0289] It should be noted that the apparatus provided in this embodiment can implement all the method steps implemented in the above method embodiment and can achieve the same technical effect. Therefore, the parts and beneficial effects that are the same as those in the method embodiment will not be described in detail here.
[0290] As shown in Figure 14, this embodiment of the present disclosure also provides a computing resource awareness device to implement the above-mentioned computing resource awareness method on all device sides. The computing resource awareness device includes a processor 1201, a memory 1202, and a transceiver 1203.
[0291] Memory 1202 is used to store computer programs; transceiver 1203 is used to receive and send data under the control of processor 1201. Processor 1201 is used to read the computer program from memory and perform the following operations:
[0292] The transceiver receives a first resource call awareness message sent by a first network function entity. The first resource call awareness message is used to indicate the call to the computing service API of the target computing resource. The target computing resource is the computing resource provided by all devices of the resource.
[0293] The transceiver sends resource access control messages for the computing service API to the first network function entity.
[0294] In some embodiments, the first resource call awareness message includes authorization request information for the resource call device to call the computing service API; the resource call control message includes authorization indication information for the resource call device to call the computing service API.
[0295] In some embodiments, if the authorization instruction information indicates successful authorization, the authorization instruction information includes authorization condition information; or, if the authorization instruction information indicates authorization failure, the authorization instruction information includes authorization failure reason information.
[0296] In some embodiments, the authorization condition information includes at least one of the following: the number of valid calls to the computing service API by the resource calling device and the valid time period.
[0297] In some embodiments, the processor 1201 is further configured to read a computer program from the memory 1202 and perform the following operations:
[0298] The transceiver sends an authorization revocation instruction message for the computing service API to the first network function entity. The authorization revocation instruction message is used to instruct the first network function entity to revoke the authorization for the resource calling device to call the computing service API.
[0299] The transceiver receives a successful authorization revocation message for the computing service API sent by the first network function entity.
[0300] In some embodiments, the processor 1201 is further configured to read a computer program from the memory 1202 and perform the following operations:
[0301] The transceiver sends a registration request message to the second network function entity. The registration request message is used to request the registration of the computing service API of the target computing resource.
[0302] In some embodiments, the registration request message includes at least one of the following registration information: the identifier of the computing service API, information of all devices owning the resource, the access address of the computing service API, the computing node information corresponding to the computing service API, and the computing service information corresponding to the computing service API.
[0303] In some embodiments, the computing service information includes at least one of the following: computing service identifier, computing service type, computing service service time, computing service service scope, and computing resource protection instruction information.
[0304] In some embodiments, the processor 1201 is further configured to read a computer program from the memory 1202 and perform the following operations:
[0305] The transceiver sends a resource change notification message for the target resource to the first network function entity. The resource change notification message is used to trigger a second resource call awareness message. The second resource call awareness message is used to indicate whether at least one of the target computing resource and the computing service API of the target computing resource has changed.
[0306] In some embodiments, the processor 1201 is further configured to read a computer program from the memory 1202 and perform the following operations:
[0307] The transceiver receives a resource recovery instruction message sent by the first network function entity. The resource recovery request message is used to request the recovery of at least one of the target computing resource and the computing service API of the target computing resource.
[0308] In Figure 14, the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors (represented by processors) and memories (represented by memory). The bus architecture can also link various other circuits, such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. The transceiver can be multiple components, including transmitters and receivers, providing a unit for communicating with various other devices over a transmission medium, including wireless channels, wired channels, optical fibers, etc. For different user equipment, the user interface 1204 can also be an interface capable of connecting external or internal devices, including but not limited to keypads, displays, speakers, microphones, joysticks, etc.
[0309] The processor is responsible for managing the bus architecture and general processing, while the memory can store the data used by the processor 1201 when performing operations.
[0310] In some embodiments, the processor may be a CPU (Central Processing Unit), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), or a CPLD (Complex Programmable Logic Device), and the processor may also adopt a multi-core architecture.
[0311] The processor executes any of the methods provided in the embodiments of this disclosure by invoking a program stored in memory, according to the obtained executable instructions. The processor and memory may also be physically separated.
[0312] As shown in Figure 15, this embodiment of the present disclosure also provides a computing resource awareness device to implement the computing resource awareness method on the first network functional entity side described above. The computing resource awareness device includes a processor 1301, a memory 1302, and a transceiver 1303.
[0313] Memory 1302 is used to store computer programs; transceiver 1303 is used to send and receive data under the control of processor 1301; processor 1301 is used to read the computer program in memory 1302 and perform the following operations:
[0314] The transceiver receives resource call request messages from the resource call device for the computing service API of the target computing resource, where the target computing resource is the computing resource provided by all the devices that provide the resource.
[0315] If the target computing resource is a protected computing resource, a first resource call awareness message is sent to all devices that own the resource via a transceiver. The first resource call awareness message is used to indicate the call to the computing service API of the target computing resource.
[0316] The transceiver receives resource call control messages from the computing service API sent by all devices.
[0317] In some embodiments, processor 1301 is further configured to read a computer program from memory 1302 and perform the following operations:
[0318] The transceiver sends resource access control messages to the resource access device.
[0319] In some embodiments, the first resource call awareness message includes authorization request information for the resource call device to call the computing service API; the resource call control message includes authorization indication information for the resource call device to call the computing service API.
[0320] In some embodiments, if the authorization instruction information indicates successful authorization, the authorization instruction information includes authorization condition information; or, if the authorization instruction information indicates authorization failure, the authorization instruction information includes authorization failure reason information.
[0321] In some embodiments, authorization condition information is used to indicate at least one of the valid number of times and the valid time for a resource calling device to call the computing service API.
[0322] In some embodiments, processor 1301 is further configured to read a computer program from memory 1302 and perform the following operations:
[0323] Receive authorization revocation request messages for the computing service API sent by all devices of the resource through the transceiver;
[0324] Based on the authorization revocation request message, revoke the authorization for the resource-calling device to call the computing service API;
[0325] Send authorization revocation notification messages for the computing service API to the resource-calling device via the transceiver;
[0326] The transceiver sends a message indicating successful authorization revocation of the computing service API to all devices in the resource.
[0327] In some embodiments, processor 1301 is further configured to read a computer program from memory 1302 and perform the following operations:
[0328] Receive publish request messages sent by the second network function entity through the transceiver;
[0329] According to the release request message, the computing service API of the target computing resource is registered to the API service list of the first network function entity. The API service list includes at least one computing service API that can be requested and invoked by the resource-invoking device.
[0330] In some embodiments, the publish request message includes information about all devices with resources and information about the computing service API of the target computing resource.
[0331] In some embodiments, the information of the computing service API includes at least one of the following: computing service API identifier, computing service API type, communication type corresponding to the computing service API, interface information corresponding to the computing service API, protocol information corresponding to the computing service API, data format information corresponding to the computing service API, computing node information corresponding to the computing service API, and computing service information corresponding to the computing service API.
[0332] In some embodiments, the computing service information includes at least one of the following: computing service identifier, computing service type, computing service service time, computing service service scope, and computing resource protection instruction information.
[0333] In some embodiments, processor 1301 is further configured to read a computer program from memory 1302 and perform the following operations:
[0334] Receive resource change notification messages for the target resource from all devices using the transceiver;
[0335] A second resource call awareness message is sent by the transceiver to the resource call device. The second resource call awareness message is used to indicate whether at least one of the target computing resource and the computing service API of the target computing resource has changed.
[0336] In some embodiments, if the resource-requesting device is the device currently using the target computing resource, the second resource-requesting awareness message further includes identification information of the resource-requesting device; the processor 1301 is also configured to read the computer program in the memory 1302 and perform the following operations:
[0337] The transceiver receives a change response message corresponding to the second resource call awareness message sent by the resource call device. The change response message includes a confirmation result of the change to the computing service API of the target computing resource.
[0338] In some embodiments, if the change confirmation result is a rejection of the change, the processor 1301 is further configured to read the computer program in the memory 1302 and perform the following operations:
[0339] The transceiver sends a resource recovery instruction message to all devices of the resource, and the resource recovery request message is used to request the recovery of at least one of the target computing resource and the computing service API of the target computing resource.
[0340] In Figure 15, the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors (represented by a processor) and memories (represented by memory). The bus architecture can also link various other circuits, such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides the interface. The transceiver can be multiple components, including a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium, including wireless channels, wired channels, optical fibers, etc. The processor is responsible for managing the bus architecture and general processing, and the memory can store data used by the processor 1301 during operation.
[0341] The processor can be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor can also adopt a multi-core architecture.
[0342] As shown in Figure 16, this embodiment of the present disclosure also provides a computing resource awareness device to implement the above-described computing resource awareness method on the resource access device side. The computing resource awareness device includes a processor 1401, a memory 1402, and a transceiver 1403.
[0343] Memory 1402 is used to store computer programs; transceiver 1403 is used to send and receive data under the control of processor 1402; processor 1402 is used to read the computer program in memory 1402 and perform the following operations:
[0344] The transceiver sends a first resource call request message for the computing service API of the target computing resource to the first network function entity. The target computing resource is the computing resource provided by all devices of the resource.
[0345] The transceiver receives resource call control messages for the computing service API sent by the first network function entity.
[0346] In some embodiments, the first resource call awareness message includes authorization request information for the resource call device to call the computing service API; the resource call control message includes authorization indication information for the resource call device to call the computing service API.
[0347] In some embodiments, if the authorization instruction information indicates successful authorization, the authorization instruction information includes authorization condition information; or, if the authorization instruction information indicates authorization failure, the authorization instruction information includes authorization failure reason information.
[0348] In some embodiments, the authorization condition information includes at least one of the following: the number of valid calls to the computing service API by the resource calling device and the valid time period.
[0349] In some embodiments, the processor 1402 is further configured to read a computer program from the memory 1402 and perform the following operations:
[0350] The transceiver receives a second resource call awareness message sent by the first network function entity. The second resource call awareness message is used to indicate whether at least one of the target computing resource and the computing service API of the target computing resource has changed.
[0351] In some embodiments, where the resource calling device is a subscribed device for the target computing resource, the processor 1402 is further configured to read the computer program in the memory 1402 and perform the following operations:
[0352] Based on the update indication information in the second resource call awareness message, the computing service API of the target computing resource is called to obtain the target computing resource.
[0353] In some embodiments, if the resource-requesting device is the device currently using the target computing resource, the second resource-requesting awareness message further includes identification information of the resource-requesting device; the processor 1402 is also configured to read the computer program in the memory 1402 and perform the following operations:
[0354] Determine the confirmation results of the changes to the computing service API of the target computing resource;
[0355] The transceiver sends a change response message corresponding to the second resource call awareness message to the first network function entity. The change response message includes a change confirmation result.
[0356] In some embodiments, if the change confirmation result is "agreement to the change," the processor 1402 is further configured to read the computer program in the memory 1402 and perform the following operations:
[0357] Based on the update indication information in the second resource call awareness message, continue to call the computing service API of the target computing resource to obtain the target computing resource.
[0358] In some embodiments, if the change confirmation result is a rejection of the change, the change response message is used to trigger a resource recovery indication message, and the resource recovery request message is used to request the recovery of at least one of the target computing resource and the computing service API of the target computing resource.
[0359] In Figure 16, the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors (represented by processors) and memories (represented by memory). The bus architecture can also link various other circuits, such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. The transceiver can be multiple components, including transmitters and receivers, providing a unit for communicating with various other devices over a transmission medium, including wireless channels, wired channels, optical fibers, etc. For different user equipment, the user interface 1404 can also be an interface capable of connecting external or internal devices, including but not limited to keypads, displays, speakers, microphones, joysticks, etc.
[0360] The processor is responsible for managing the bus architecture and general processing, while the memory can store the data used by the processor 1401 when performing operations.
[0361] In some embodiments, the processor may be a CPU (Central Processing Unit), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), or a CPLD (Complex Programmable Logic Device), and the processor may also adopt a multi-core architecture.
[0362] The processor executes any of the methods provided in the embodiments of this disclosure by invoking a program stored in memory, according to the obtained executable instructions. The processor and memory may also be physically separated.
[0363] This disclosure provides a computing resource awareness device for use in a resource allocation device, including a memory, a transceiver, and a processor:
[0364] Memory is used to store computer programs; transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer programs from memory and perform the following operations:
[0365] The transceiver receives a second resource call awareness message sent by the first network function entity. The second resource call awareness message is used to indicate whether at least one of the target computing resource and the computing service API of the target computing resource has changed.
[0366] In some embodiments, where the resource-calling device is a subscribed device for the target computing resource, the processor is further configured to read a computer program from memory and perform the following operations:
[0367] Based on the update indication information in the second resource call awareness message, the computing service API of the target computing resource is called to obtain the target computing resource.
[0368] In some embodiments, if the resource-requesting device is the device currently using the target computing resource, the second resource-requesting awareness message further includes identification information of the resource-requesting device; the processor is also configured to read the computer program in memory and perform the following operations:
[0369] Determine the confirmation results of the changes to the computing service API of the target computing resource;
[0370] The transceiver sends a change response message corresponding to the second resource call awareness message to the first network function entity. The change response message includes a change confirmation result.
[0371] In some embodiments, if the change confirmation result is "agreement to the change," the processor is further configured to read the computer program in memory and perform the following operations:
[0372] Based on the update indication information in the second resource call awareness message, continue to call the computing service API of the target computing resource to obtain the target computing resource.
[0373] In some embodiments, if the change confirmation result is a rejection of the change, the change response message is used to trigger a resource recovery indication message, and the resource recovery request message is used to request the recovery of at least one of the target computing resource and the computing service API of the target computing resource.
[0374] This disclosure provides a computing resource awareness device applied to a first network functional entity, including a memory, a transceiver, and a processor:
[0375] Memory is used to store computer programs; transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer programs from memory and perform the following operations:
[0376] Receive resource change notification messages for the target resource from all devices using the transceiver;
[0377] A second resource call awareness message is sent by the transceiver to the resource call device. The second resource call awareness message is used to indicate whether at least one of the target computing resource and the computing service API of the target computing resource has changed.
[0378] In some embodiments, if the resource-requesting device is the device currently using the target computing resource, the second resource-requesting awareness message further includes identification information of the resource-requesting device; the processor is also configured to read the computer program in memory and perform the following operations:
[0379] The transceiver receives a change response message corresponding to the second resource call awareness message sent by the resource call device. The change response message includes a confirmation result of the change to the computing service API of the target computing resource.
[0380] In some embodiments, if the change confirmation result is a rejection, the processor is further configured to read the computer program in memory and perform the following operations:
[0381] The transceiver sends a resource recovery instruction message to all devices of the resource, and the resource recovery request message is used to request the recovery of at least one of the target computing resource and the computing service API of the target computing resource.
[0382] This disclosure provides a computing resource awareness device applied to resource-owning devices, including a memory, a transceiver, and a processor:
[0383] Memory is used to store computer programs; transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer programs from memory and perform the following operations:
[0384] The transceiver sends a resource change notification message for the target resource to the first network function entity. The resource change notification message is used to trigger a second resource call awareness message. The second resource call awareness message is used to indicate whether at least one of the target computing resource and the computing service API of the target computing resource has changed.
[0385] In some embodiments, the processor is also configured to read a computer program from memory and perform the following operations:
[0386] The transceiver receives a resource recovery instruction message sent by the first network function entity. The resource recovery request message is used to request the recovery of at least one of the target computing resource and the computing service API of the target computing resource.
[0387] This disclosure also provides a processor-readable storage medium, which can be any available medium or data storage device that can be accessed by a processor, including but not limited to magnetic memory (e.g., floppy disk, hard disk, magnetic tape, magneto-optical disk (MO)), optical memory (e.g., CD, DVD, BD, HVD), and semiconductor memory (e.g., ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state drive (SSD)).
[0388] In one embodiment, this disclosure also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described access control method for an AI serving cell.
[0389] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this disclosure can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this disclosure may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this disclosure may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.
[0390] Those skilled in the art will understand that embodiments of this disclosure can be provided as methods, systems, or computer program products. Therefore, this disclosure can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this disclosure can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage and optical storage) containing computer-usable program code.
[0391] This disclosure is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this disclosure. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer-executable instructions. These computer-executable instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in one or more flowchart illustrations and / or one or more block diagrams.
[0392] These processor-executable instructions may also be stored in a processor-readable memory that can instruct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the processor-readable memory produce an article of manufacture including instruction means that implement the functions specified in one or more flowcharts and / or one or more block diagrams.
[0393] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.
[0394] Obviously, those skilled in the art can make various modifications and variations to this disclosure without departing from its spirit and scope. Therefore, if such modifications and variations fall within the scope of the claims of this disclosure and their equivalents, this disclosure is also intended to include such modifications and variations.
[0395] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this disclosure, and not to limit them. Although this disclosure has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. These modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this disclosure, and they should all be covered within the scope of the claims and specification of this disclosure. In particular, as long as there is no structural conflict, the various technical features mentioned in the various embodiments can be combined in any way. This disclosure is not limited to the specific embodiments disclosed herein, but includes all technical solutions falling within the scope of the claims.
Claims
A method of computing resource awareness, applied to a resource owning device, wherein, The method comprises: receiving a first resource invocation awareness message sent by a first network function entity, the first resource invocation awareness message being used to indicate invocation of a computing service API of a target computing resource, the target computing resource being a computing resource provided by a resource owning device; sending a resource invocation control message of the computing service API to the first network function entity. The method of claim 1, wherein, The first resource invocation awareness message comprises authorization request information of invocation of the computing service API by a resource invocation device; and the resource invocation control message comprises authorization indication information of invocation of the computing service API by the resource invocation device. The method of claim 2, wherein, In a case where the authorization indication information indicates that authorization is successful, authorization condition information is included in the authorization indication information; or In a case where the authorization indication information indicates that authorization fails, authorization failure reason information is included in the authorization indication information. The method of claim 3, wherein, The authorization condition information comprises at least one of a valid number of invocations of the computing service API by the resource invocation device and a valid time. The method of claim 2, wherein, The method further comprises: sending an authorization revocation indication message of the computing service API to the first network function entity, the authorization revocation indication message being used to indicate revocation of invocation authorization of the computing service API by the resource invocation device by the first network function entity; receiving an authorization revocation success message of the computing service API sent by the first network function entity. The method according to any one of claims 1 to 5, wherein The method further comprises: sending a registration request message to a second network function entity, the registration request message being used to request registration of the computing service API of the target computing resource. The method of claim 6, wherein, The registration request message comprises at least one of the following registration information: an identifier of the computing service API, information of the resource owning device, an access address of the computing service API, information of a computing power node corresponding to the computing service API, and computing service information corresponding to the computing service API. The method of claim 7, wherein, The computing service information comprises at least one of the following: a computing service identifier, a computing service type, a service time of the computing service, a service range of the computing service, and protection indication information of the computing resource. The method according to any one of claims 1 to 5, wherein The method further comprises: sending a resource change notification message of the target resource to the first network function entity, the resource change notification message being used to trigger a second resource invocation awareness message, the second resource invocation awareness message being used to indicate whether at least one of the target computing resource and the computing service API of the target computing resource has changed. The method of claim 9, wherein, The method further comprises: receiving a resource recovery indication message sent by the first network function entity, the resource recovery request message being used to request recovery of at least one of the changed target computing resource and the computing service API of the target computing resource. A computing resource awareness method, applied to a first network function entity, wherein, The method comprises: receiving a resource invocation request message of a computing service API of a target computing resource sent by a resource invocation device, the target computing resource being a computing resource provided by a resource owning device; In a case where the target computing resource is a protected computing resource, a first resource invocation awareness message is sent to the resource owner device, the first resource invocation awareness message being used to indicate invocation of a computing service API of the target computing resource; The resource invocation control message of the computing service API sent by the resource owner device is received. The method of claim 11, wherein, The method further comprises: The resource invocation control message is sent to the resource invocation device. The method of claim 11, wherein, The first resource invocation awareness message comprises authorization request information of the resource invocation device invoking the computing service API; and the resource invocation control message comprises authorization indication information of the resource invocation device invoking the computing service API. The method of claim 13, wherein, In a case where the authorization indication information indicates that authorization is successful, authorization condition information is included in the authorization indication information; or In a case where the authorization indication information indicates that authorization fails, authorization failure reason information is included in the authorization indication information. The method of claim 14, wherein, The authorization condition information is used to indicate at least one of a valid number of times and a valid time of the resource invocation device invoking the computing service API. The method of claim 13, wherein, The method further comprises: An authorization revocation request message of the computing service API sent by the resource owner device is received; According to the authorization revocation request message, invocation authorization of the resource invocation device to the computing service API is revoked; An authorization revocation notification message of the computing service API is sent to the resource invocation device; An authorization revocation success message of the computing service API is sent to the resource owner device. The method according to any one of claims 11-16, wherein The method further comprises: A publication request message sent by a second network function entity is received; According to the publication request message, a computing service API of the target computing resource is registered to an API service list of the first network function entity, the API service list comprising at least one computing service API requested to be invoked by the resource invocation device. The method of claim 17, wherein, The publication request message comprises information of the resource owner device and information of the computing service API of the target computing resource. The method of claim 18, wherein, The information of the computing service API comprises at least one of the following: a computing service API identifier, a computing service API type, a communication type corresponding to the computing service API, interface information corresponding to the computing service API, protocol information corresponding to the computing service API, data format information corresponding to the computing service API, computing power node information corresponding to the computing service API, and computing service information corresponding to the computing service API. The method of claim 19, wherein, The computing service information comprises at least one of the following: a computing service identifier, a computing service type, a service time of the computing service, a service range of the computing service, and protection indication information of the computing resource. The method according to any one of claims 11-16, wherein The method further comprises: A resource change notification message of the target resource sent by the resource owner device is received; A second resource invocation awareness message is sent to the resource invocation device, the second resource invocation awareness message being used to indicate whether at least one of the target computing resource and a computing service API of the target computing resource has changed. The method of claim 21, wherein, In a case where the resource calling device is a device currently using the target computing resource, the second resource calling awareness message further includes identification information of the resource calling device; and the method further includes: receiving a change response message corresponding to the second resource calling awareness message sent by the resource calling device, the change response message including a change confirmation result of a computing service API of the target computing resource. The method of claim 22, wherein, In a case where the change confirmation result is a refusal to change, the method further includes: sending a resource recovery indication message to the resource owning device, the resource recovery request message being used to request recovery of at least one of the changed target computing resource and the computing service API of the target computing resource. A computing resource awareness method is applied to a resource calling device, wherein, The method includes: sending a first resource calling request message of a computing service API of a target computing resource to a first network function entity, the target computing resource being a computing resource provided by a resource owning device; receiving a resource calling control message of the computing service API sent by the first network function entity. The method of claim 24, wherein, The first resource calling awareness message includes authorization request information of the resource calling device calling the computing service API; and the resource calling control message includes authorization indication information of the resource calling device calling the computing service API. The method of claim 25, wherein, In a case where the authorization indication information indicates that authorization is successful, the authorization indication information includes authorization condition information; or In a case where the authorization indication information indicates that authorization fails, the authorization indication information includes authorization failure reason information. The method of claim 26, wherein, The authorization condition information includes at least one of a valid number of times and a valid time of the resource calling device calling the computing service API. The method of any one of claims 24-27, wherein, The method further includes: receiving a second resource calling awareness message sent by the first network function entity, the second resource calling awareness message being used to indicate whether at least one of a target computing resource and a computing service API of the target computing resource has changed. The method of claim 28, wherein, In a case where the resource calling device is a subscribed device of the target computing resource, the method further includes: calling the computing service API of the target computing resource according to update indication information in the second resource calling awareness message to obtain the target computing resource. The method of claim 28, wherein, In a case where the resource calling device is a device currently using the target computing resource, the second resource calling awareness message further includes identification information of the resource calling device; and the method further includes: determining a change confirmation result of a computing service API of the target computing resource; sending a change response message corresponding to the second resource calling awareness message to the first network function entity, the change response message including the change confirmation result. The method of claim 30, wherein, In a case where the change confirmation result is an agreement to change, the method further includes: continuing to call the computing service API of the target computing resource according to update indication information in the second resource calling awareness message to obtain the target computing resource. The method of claim 30, wherein, In a case where the change confirmation result is a rejection of the change, the change response message is used to trigger the resource recovery indication message, and the resource recovery request message is used to request recovery of at least one of the target computing resource and the computing service API of the target computing resource. A computing resource awareness method is applied to a resource calling device, wherein, The method comprises: receiving a second resource invocation awareness message sent by a first network function entity, the second resource invocation awareness message being used to indicate whether at least one of a target computing resource and a computing service API of the target computing resource has changed. The method of claim 33, wherein, In a case where the resource invocation device is a subscribed device of the target computing resource, the method further comprises: invoking the computing service API of the target computing resource according to update indication information in the second resource invocation awareness message to obtain the target computing resource. The method of claim 33, wherein, In a case where the resource invocation device is a device currently using the target computing resource, the second resource invocation awareness message further comprises identification information of the resource invocation device; the method further comprises: determining a change confirmation result of the computing service API of the target computing resource; sending, to the first network function entity, a change response message corresponding to the second resource invocation awareness message, the change response message comprising the change confirmation result. The method of claim 35, wherein, In a case where the change confirmation result is an approval of the change, the method further comprises: continuing to invoke the computing service API of the target computing resource according to the update indication information in the second resource invocation awareness message to obtain the target computing resource. The method of claim 35, wherein, In a case where the change confirmation result is a rejection of the change, the change response message is used to trigger the resource recovery indication message, and the resource recovery request message is used to request recovery of at least one of the target computing resource and the computing service API of the target computing resource. A computing resource awareness method, applied to a first network function entity, wherein, The method comprises: receiving a resource change notification message of a target resource sent by a resource owner device; sending, to a resource invocation device, a second resource invocation awareness message, the second resource invocation awareness message being used to indicate whether at least one of a target computing resource and a computing service API of the target computing resource has changed. The method of claim 38, wherein, In a case where the resource invocation device is a device currently using the target computing resource, the second resource invocation awareness message further comprises identification information of the resource invocation device; the method further comprises: receiving a change response message corresponding to the second resource invocation awareness message sent by the resource invocation device, the change response message comprising a change confirmation result of the computing service API of the target computing resource. The method of claim 39, wherein, In a case where the change confirmation result is a rejection of the change, the method further comprises: sending, to the resource owner device, a resource recovery indication message, the resource recovery request message being used to request recovery of at least one of the target computing resource and the computing service API of the target computing resource. A computing resource awareness method, applied to a resource owning device, wherein, The method comprises: sending, to a first network function entity, a resource change notification message of a target resource, the resource change notification message being used to trigger a second resource invocation awareness message, the second resource invocation awareness message being used to indicate whether a change occurs in at least one of a target computing resource and a computing service API of the target computing resource. The method of claim 41, wherein, The method further includes: receiving, from the first network function entity, a resource recovery indication message, the resource recovery indication message being used to request recovery of the changed at least one of the target computing resource and the computing service API of the target computing resource. A computing resource-aware apparatus, applied to a resource owning device, wherein, comprising a memory, a transceiver, and a processor: the memory is configured to store a computer program; the transceiver is configured to transceive data under control of the processor; the processor is configured to read the computer program in the memory and perform the following operations: receiving, by the transceiver, a first resource invocation awareness message from a first network function entity, the first resource invocation awareness message being used to indicate an invocation of a computing service API of a target computing resource, the target computing resource being a computing resource provided by a resource owning device; sending, by the transceiver, a resource invocation control message of the computing service API to the first network function entity. A computing resource awareness apparatus is applied to a first network function entity, wherein, comprising a memory, a transceiver, and a processor: the memory is configured to store a computer program; the transceiver is configured to transceive data under control of the processor; the processor is configured to read the computer program in the memory and perform the following operations: receiving, by the transceiver, a resource invocation request message of a computing service API of a target computing resource from a resource invocation device, the target computing resource being a computing resource provided by a resource owning device; in a case where the target computing resource is a protected computing resource, then sending, by the transceiver, a first resource invocation awareness message to the resource owning device, the first resource invocation awareness message being used to indicate the invocation of the computing service API of the target computing resource; receiving, by the transceiver, a resource invocation control message of the computing service API from the resource owning device. A computing resource-aware apparatus is applied to a resource calling device, wherein, comprising a memory, a transceiver, and a processor: the memory is configured to store a computer program; the transceiver is configured to transceive data under control of the processor; the processor is configured to read the computer program in the memory and perform the following operations: sending, by the transceiver, a first resource invocation request message of a computing service API of a target computing resource to a first network function entity, the target computing resource being a computing resource provided by a resource owning device; receiving, by the transceiver, a resource invocation control message of the computing service API from the first network function entity. A computing resource-aware apparatus is applied to a resource calling device, wherein, comprising a memory, a transceiver, and a processor: the memory is configured to store a computer program; the transceiver is configured to transceive data under control of the processor; the processor is configured to read the computer program in the memory and perform the following operations: receive, by the transceiver, a second resource invocation awareness message sent by the first network function entity, the second resource invocation awareness message being used to indicate whether at least one of the target computing resource and a computing service API of the target computing resource changes. A computing resource awareness apparatus is applied to a first network function entity, wherein, comprising a memory, a transceiver, and a processor: the memory is configured to store a computer program; the transceiver is configured to transceive data under control of the processor; the processor is configured to read the computer program in the memory and perform the following operations: receive, by the transceiver, a resource change notification message of a target resource sent by a resource owning device; A computing resource-aware apparatus, applied to a resource owning device, wherein, send, by the transceiver, a second resource invocation awareness message to a resource invocation device, the second resource invocation awareness message being used to indicate whether at least one of the target computing resource and a computing service API of the target computing resource changes. comprising a memory, a transceiver, and a processor: the memory is configured to store a computer program; the transceiver is configured to transceive data under control of the processor; the processor is configured to read the computer program in the memory and perform the following operations: A computing resource-aware apparatus, applied to a resource owning device, wherein, send, by the transceiver, a resource change notification message of a target resource to a first network function entity, the resource change notification message being used to trigger a second resource invocation awareness message, the second resource invocation awareness message being used to indicate whether at least one of the target computing resource and a computing service API of the target computing resource changes. comprising: a first receiving module configured to receive a first resource invocation awareness message sent by a first network function entity, the first resource invocation awareness message being used to indicate invocation of a computing service API of a target computing resource, the target computing resource being a computing resource provided by a resource owning device; A computing resource awareness apparatus is applied to a first network function entity, wherein, a first sending module configured to send a resource invocation control message of the computing service API to the first network function entity. comprising: a second receiving module configured to receive a resource invocation request message of a computing service API of a target computing resource sent by a resource invocation device, the target computing resource being a computing resource provided by a resource owning device; receive a resource invocation control message of the computing service API sent by the resource owning device; A computing resource-aware apparatus is applied to a resource calling device, wherein, a second sending module configured to, in a case where the target computing resource is a protected computing resource, send a first resource invocation awareness message to the resource owning device, the first resource invocation awareness message being used to indicate invocation of a computing service API of a computing resource. comprising: a third sending module configured to send a first resource invocation request message of a computing service API of a target computing resource to a first network function entity, the target computing resource being a computing resource provided by a resource owning device; A computing resource-aware apparatus is applied to a resource calling device, wherein, a third receiving module configured to receive a resource invocation control message of the computing service API sent by the first network function entity. comprising: a third sending module configured to receive a second resource invocation awareness message sent by a first network function entity, the second resource invocation awareness message being used to indicate whether at least one change of a target computing resource and a computing service API of the target computing resource; The first processing module is configured to process the call of the computing service API of the target computing resource according to the second resource call awareness message. A computing resource awareness apparatus is applied to a first network function entity, wherein, The method comprises the following steps: The second receiving module is configured to receive a resource change notification message of a target resource sent by a resource owner device. The second sending module is configured to send a second resource call awareness message, which is used to indicate whether at least one of the target computing resource and a computing service API of the target computing resource has changed. A computing resource-aware apparatus, applied to a resource owning device, wherein, The method comprises the following steps: The second processing device is configured to generate a resource change notification message of a target resource, which is used to trigger a second resource call awareness message, and the second resource call awareness message is used to indicate whether at least one of the target computing resource and a computing service API of the target computing resource has changed. The first sending device is configured to send the resource change notification message to a first network function entity. A processor-readable storage medium, wherein, The processor readable storage medium stores a program, and the program is used to make the processor execute the method in any one of claims 1 to 42.
