Cloud resource processing method and device

Abstract

The application relates to a cloud resource processing method and device. The method comprises the following steps: receiving a cloud resource opening request sent by a user end, wherein the cloud resource opening request carries a cloud resource identifier and an access token; obtaining a temporary key pair according to the access token, wherein the temporary key pair is a key pair with public cloud interface access authority; assembling the temporary key pair and the cloud resource identifier to obtain assembled parameters for interface access; sending an interface access request carrying the assembled parameters to a public cloud interface; and when receiving target feedback information sent by the public cloud, feeding back the target feedback information to the user end, wherein the target feedback information is generated by the public cloud after creating a cloud resource according to the cloud resource identifier in the assembled parameters when the temporary key pair in the assembled parameters passes the interface access authority check. The method can be used to easily realize public cloud resource acquisition.

Description

Technical Field

[0001] This application relates to the field of cloud computing technology, and in particular to a cloud resource processing method and apparatus. Background Technology

[0002] With the development of computer technology, cloud technology has emerged. Cloud technology refers to a hosting technology that unifies hardware, software, network, and other resources within a wide area network (WAN) or local area network (LAN) to achieve data computing, storage, processing, and sharing. Cloud technology includes public cloud technology, which typically refers to a cloud provided by a third-party provider to users. Public clouds are generally accessible via the internet, and their core attribute is shared resource services. Based on the public cloud, vendors provide information on cloud resources for sale, i.e., public cloud resources, including computing, storage, network, and security products, to users for their computing needs via the network.

[0003] In traditional technology, the way users obtain public cloud resources is to connect the third-party platform corresponding to the agent with the public cloud for authentication and authorization. Users first log in through the third-party platform, and then are redirected to the public cloud to purchase, use, and settle accounts. The entire operation entry point is on the third-party platform, and the entire subsequent use is on the public cloud.

[0004] However, the traditional method is cumbersome because it requires logging into a third-party platform first and then being redirected to the public cloud to perform the operation. Summary of the Invention

[0005] Therefore, it is necessary to provide a cloud resource processing method, apparatus, computer equipment, computer-readable storage medium, and computer program product that can be easily operated to address the above-mentioned technical problems.

[0006] Firstly, this application provides a cloud resource processing method. The method includes:

[0007] Receive cloud resource activation requests sent by the user client. The cloud resource activation requests carry cloud resource identifiers and access tokens.

[0008] Obtain a temporary key pair based on the access token. The temporary key pair is a key pair with access permissions to the public cloud interface.

[0009] The temporary key pair and the cloud resource identifier are assembled to obtain the assembly parameters used for interface access;

[0010] Send an interface access request carrying assembly parameters to the public cloud interface;

[0011] When the target feedback information sent by the public cloud is received, the target feedback information is sent back to the user terminal. The target feedback information is generated by the public cloud after creating the cloud resource based on the cloud resource identifier in the assembly parameters, when the interface access permission verification of the temporary key pair in the assembly parameters is passed. Secondly, this application also provides a cloud resource processing device. The device includes:

[0012] The request receiving module is used to receive cloud resource activation requests sent by the user. The cloud resource activation request carries the cloud resource identifier and access token.

[0013] The acquisition module is used to obtain a temporary key pair based on the access token. The temporary key pair is a key pair with public cloud interface access permissions.

[0014] The assembly module is used to assemble temporary key pairs and cloud resource identifiers to obtain assembly parameters for interface access;

[0015] The access module is used to send interface access requests carrying assembly parameters to the public cloud interface;

[0016] The prompt receiving module is used to send target feedback information back to the user terminal when it receives target feedback information sent by the public cloud. The target feedback information is generated by the public cloud after creating cloud resources based on the cloud resource identifier in the assembly parameters when the interface access permission verification of the temporary key pair in the assembly parameters is passed.

[0017] Thirdly, this application also provides a computer device. The computer device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to perform the following steps:

[0018] Receive cloud resource activation requests sent by the user client. The cloud resource activation requests carry cloud resource identifiers and access tokens.

[0019] Obtain a temporary key pair based on the access token. The temporary key pair is a key pair with access permissions to the public cloud interface.

[0020] The temporary key pair and the cloud resource identifier are assembled to obtain the assembly parameters used for interface access;

[0021] Send an interface access request carrying assembly parameters to the public cloud interface;

[0022] When the target feedback information is received from the public cloud, the target feedback information is sent back to the user terminal. The target feedback information is generated by the public cloud after it has successfully verified the interface access permissions of the temporary key pair in the assembly parameters and created the cloud resource based on the cloud resource identifier in the assembly parameters.

[0023] Fourthly, this application also provides a computer-readable storage medium. The computer-readable storage medium stores a computer program thereon, which, when executed by a processor, performs the following steps:

[0024] Receive cloud resource activation requests sent by the user client. The cloud resource activation requests carry cloud resource identifiers and access tokens.

[0025] Obtain a temporary key pair based on the access token. The temporary key pair is a key pair with access permissions to the public cloud interface.

[0026] The temporary key pair and the cloud resource identifier are assembled to obtain the assembly parameters used for interface access;

[0027] Send an interface access request carrying assembly parameters to the public cloud interface;

[0028] When the target feedback information is received from the public cloud, the target feedback information is sent back to the user terminal. The target feedback information is generated by the public cloud after it has successfully verified the interface access permissions of the temporary key pair in the assembly parameters and created the cloud resource based on the cloud resource identifier in the assembly parameters.

[0029] Fifthly, this application also provides a computer program product. The computer program product includes a computer program that, when executed by a processor, performs the following steps:

[0030] Receive cloud resource activation requests sent by the user client. The cloud resource activation requests carry cloud resource identifiers and access tokens.

[0031] Obtain a temporary key pair based on the access token. The temporary key pair is a key pair with access permissions to the public cloud interface.

[0032] The temporary key pair and the cloud resource identifier are assembled to obtain the assembly parameters used for interface access;

[0033] Send an interface access request carrying assembly parameters to the public cloud interface;

[0034] When the target feedback information is received from the public cloud, the target feedback information is sent back to the user terminal. The target feedback information is generated by the public cloud after it has successfully verified the interface access permissions of the temporary key pair in the assembly parameters and created the cloud resource based on the cloud resource identifier in the assembly parameters.

[0035] Sixthly, this application provides a cloud resource processing method. The method includes:

[0036] Send a cloud resource activation request to the server. The cloud resource activation request carries a cloud resource identifier and an access token. The access token is used to obtain a temporary key pair with public cloud interface access permissions. The temporary key pair is used to assemble with the cloud resource identifier to obtain assembly parameters. The assembly parameters are used to access the public cloud interface.

[0037] The system receives target feedback information from the server. This target feedback information is generated and sent to the server by the public cloud after it has successfully verified the interface access permissions of the temporary key pair in the assembly parameters and created the cloud resource based on the cloud resource identifier in the assembly parameters.

[0038] Seventhly, this application also provides a cloud resource processing apparatus. The apparatus includes:

[0039] The sending module is used to send a cloud resource activation request to the server. The cloud resource activation request carries a cloud resource identifier and an access token. The access token is used to obtain a temporary key pair with public cloud interface access permissions. The temporary key pair is used to assemble with the cloud resource identifier to obtain assembly parameters. The assembly parameters are used to access the public cloud interface.

[0040] The receiving module is used to receive the target feedback information from the server. The target feedback information is generated by the public cloud after it creates cloud resources based on the cloud resource identifier in the assembly parameters and sends them to the server when the interface access permission verification of the temporary key pair in the assembly parameters is passed.

[0041] Eighthly, this application also provides a computer device. The computer device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to perform the following steps:

[0042] Send a cloud resource activation request to the server. The cloud resource activation request carries a cloud resource identifier and an access token. The access token is used to obtain a temporary key pair with public cloud interface access permissions. The temporary key pair is used to assemble with the cloud resource identifier to obtain assembly parameters. The assembly parameters are used to access the public cloud interface.

[0043] The system receives target feedback information from the server. This target feedback information is generated and sent to the server by the public cloud after it has successfully verified the interface access permissions of the temporary key pair in the assembly parameters and created the cloud resource based on the cloud resource identifier in the assembly parameters.

[0044] Ninthly, this application also provides a computer-readable storage medium. The computer-readable storage medium stores a computer program thereon, which, when executed by a processor, performs the following steps:

[0045] Send a cloud resource activation request to the server. The cloud resource activation request carries a cloud resource identifier and an access token. The access token is used to obtain a temporary key pair with public cloud interface access permissions. The temporary key pair is used to assemble with the cloud resource identifier to obtain assembly parameters. The assembly parameters are used to access the public cloud interface.

[0046] The system receives target feedback information from the server. This target feedback information is generated and sent to the server by the public cloud after it has successfully verified the interface access permissions of the temporary key pair in the assembly parameters and created the cloud resource based on the cloud resource identifier in the assembly parameters.

[0047] Tenthly, this application also provides a computer program product. The computer program product includes a computer program that, when executed by a processor, performs the following steps:

[0048] Send a cloud resource activation request to the server. The cloud resource activation request carries a cloud resource identifier and an access token. The access token is used to obtain a temporary key pair with public cloud interface access permissions. The temporary key pair is used to assemble with the cloud resource identifier to obtain assembly parameters. The assembly parameters are used to access the public cloud interface.

[0049] The system receives target feedback information from the server. This target feedback information is generated and sent to the server by the public cloud after it has successfully verified the interface access permissions of the temporary key pair in the assembly parameters and created the cloud resource based on the cloud resource identifier in the assembly parameters.

[0050] The aforementioned cloud resource processing method, apparatus, computer equipment, storage medium, and computer program product, upon receiving a cloud resource activation request from a user terminal carrying a cloud resource identifier and an access token, obtains a temporary key pair with public cloud interface access permissions based on the access token, assembles the temporary key pair and the cloud resource identifier to obtain assembly parameters for interface access, and sends an interface access request carrying the assembly parameters to the public cloud interface. This enables access to the public cloud without requiring redirection to the public cloud for operation, allowing the public cloud to perform corresponding operations based on the assembly parameters carried in the interface access request. When the interface permission verification of the temporary key pair passes, the cloud resource is created based on the cloud resource identifier. Thus, upon receiving target feedback information from the public cloud, target feedback information is sent back to the user terminal, informing the user terminal that the cloud resource has been created. The entire process allows for the simple and convenient acquisition of public cloud resources. Attached Figure Description

[0051] Figure 1 This is an application environment diagram of a cloud resource processing method in one embodiment;

[0052] Figure 2 This is a flowchart illustrating a cloud resource processing method in one embodiment;

[0053] Figure 3 This is a flowchart illustrating a user's work order operation in one embodiment;

[0054] Figure 4 This is a schematic diagram of the cloud resource message acquisition process in one embodiment;

[0055] Figure 5 This is a flowchart illustrating a cloud resource processing method in another embodiment;

[0056] Figure 6 This is a flowchart illustrating the cloud resource processing method in yet another embodiment;

[0057] Figure 7 This is a business architecture diagram corresponding to a cloud resource processing method in one embodiment;

[0058] Figure 8 This is a structural block diagram of a cloud resource processing device in one embodiment;

[0059] Figure 9 This is a structural block diagram of a cloud resource processing device in another embodiment;

[0060] Figure 10 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0061] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0062] The cloud resource processing method provided in this application embodiment can be applied to, for example, Figure 1In the application environment shown, client 102 communicates with server 104 via a network, and server 104 communicates with public cloud 106 via a network. A data storage system can store the data that server 104 needs to process. The data storage system can be integrated onto server 104 or placed on the cloud or other servers. Server 104 receives a cloud resource activation request sent by client 102, carrying a cloud resource identifier and an access token. Based on the access token, it obtains a temporary key pair with public cloud interface access permissions. It assembles the temporary key pair and the cloud resource identifier to obtain assembly parameters for interface access and sends an interface access request carrying the assembly parameters to the interface of public cloud 106. When it receives target feedback information from the public cloud, it sends target feedback information back to the client. The target feedback information is generated by the public cloud after creating cloud resources based on the cloud resource identifier in the assembly parameters, provided that the interface access permission verification of the temporary key pair in the assembly parameters is successful. The user terminal 102 can be, but is not limited to, various personal computers, laptops, smartphones, tablets, IoT devices, and portable wearable devices. IoT devices can include smart speakers, smart TVs, smart air conditioners, and smart in-vehicle devices. Portable wearable devices can include smartwatches, smart bracelets, and head-mounted devices. The server 104 can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms. This application's embodiments can be applied to various scenarios, including but not limited to cloud technology, artificial intelligence, smart transportation, and assisted driving.

[0063] In one embodiment, such as Figure 2 As shown, a cloud resource processing method is provided, which can be applied to... Figure 1 Taking server 104 as an example, the following steps are included:

[0064] Step 202: Receive the cloud resource activation request sent by the user terminal. The cloud resource activation request carries the cloud resource identifier and access token.

[0065] A cloud resource activation request refers to a user's request to the server to activate cloud resources. For example, a user can send a cloud resource activation request to the server from their client. The client will then display an interface for a corresponding agent platform. By operating through this agent platform interface, the user can send the cloud resource activation request to the server. An agent is an agent who acts as a proxy for public cloud products. Entrusted by the primary enterprise owning the public cloud, the agent, within a certain region and location, and with certain agency authority, acts on behalf of the primary enterprise in economic activities (including the sale of goods and other activities). The legal consequences of this act directly accrue to the primary enterprise. The primary enterprise owning the public cloud provides the role of agent. Secondary enterprises with this agent role can, within the scope of compliance, act as agents for public cloud products, including SaaS (Software-as-a-Service), IaaS (Infrastructure as a Service), or other ISV (Independent Software Vendor) products, and receive commissions in return. An agent platform refers to a third-party platform, distinct from public clouds, used by agents when acting on behalf of the primary enterprise to conduct economic activities.

[0066] Cloud resource identifiers are the identifiers of the cloud resources a user wants to access, used to distinguish different cloud resources. Cloud resource identifiers include cloud resource product identifiers, cloud resource regions, and cloud resource operation identifiers. Specifically, cloud resource product identifiers differentiate between different cloud resource products, such as computing, storage, network, and security products. Cloud resource regions refer to the areas where cloud resources are deployed, such as Guangzhou or Shenzhen. Cloud resource operation identifiers distinguish between different types of operations, such as querying and computing. Access tokens are the identity authorization information issued by the server to the user after login. The information in the access token includes the identifier and privileges of the user account associated with the process or thread.

[0067] Specifically, when cloud resources need to be activated, users will operate on the client that displays the interface of the agent platform corresponding to the server, and send a cloud resource activation request carrying the cloud resource identifier and access token to the server.

[0068] Step 204: Obtain a temporary key pair based on the access token. The temporary key pair is a key pair with public cloud interface access permissions.

[0069] Temporary key pairs are key pairs granted by the server to users, granting them access to public cloud interfaces. These temporary key pairs enable access to public cloud interfaces; essentially, they represent the user's identity information. Each user account corresponds to a unique temporary key pair, with a one-to-one relationship between user accounts and temporary key pairs. For example, a temporary key pair may include a secretID (secret account) and a secretkey (key).

[0070] Specifically, upon receiving a cloud resource activation request, the server uses the access token to locate the corresponding user account information. It then uses this user account information to retrieve the corresponding temporary key pair, obtaining the user's temporary key pair for public cloud interface access. The user account information includes information about a public cloud shadow account, which is an authenticated public cloud account. This shadow account cannot directly log in to the public cloud, but it can be used to purchase, operate, and use public cloud resources.

[0071] Step 206: Assemble the temporary key pair and cloud resource identifier to obtain assembly parameters for interface access.

[0072] Specifically, after obtaining the temporary key pair, the server will assemble the temporary key pair and the cloud resource identifier to obtain the assembly parameters used for interface access.

[0073] Step 208: Send an interface access request carrying assembly parameters to the public cloud interface.

[0074] In this context, a public cloud interface refers to the interface through which the public cloud provides services. Servers need to send access requests to these public cloud interfaces to access and perform operations. For example, a public cloud interface can specifically refer to a standard public cloud interface, a general-purpose interface applicable to most functions. For instance, an interface implementing a query function is a standard interface. Conversely, a public cloud interface can also refer to a non-standard public cloud interface, an interface used for a few specific functions. For example, an interface implementing a payment function is a non-standard interface.

[0075] Specifically, after obtaining the assembly parameters for interface access, the server determines the type of the interface to be accessed based on the cloud resource identifier. Based on this type, it identifies the public cloud interface to be accessed and sends an interface access request carrying the assembly parameters to that interface. The interface type to be accessed includes standard and non-standard interfaces. When the interface type is a standard interface, the request can be directly sent via interface call, carrying the assembly parameters. When the interface type is a non-standard interface, annotation matching is required to adapt it to the non-standard interface before sending the request.

[0076] Step 210: When the target feedback information sent by the public cloud is received, the target feedback information is sent back to the user terminal. The target feedback information is generated by the public cloud after creating cloud resources based on the cloud resource identifier in the assembly parameters when the interface access permission verification of the temporary key pair in the assembly parameters is passed.

[0077] The target feedback information is used to indicate that the cloud resource has been successfully created. For example, the target feedback information can specifically be a message indicating that the cloud resource has been successfully created. For instance, the message could be a cloud resource creation instance identifier, which indicates that the resource has been successfully created.

[0078] Specifically, after sending an interface access request carrying assembly parameters to the interface, the public cloud will verify the interface access permissions of the temporary key pair in the assembly parameters to confirm whether the user corresponding to the temporary key pair has interface access permissions. When the interface access permissions verification passes, the public cloud will create a cloud resource according to the cloud resource identifier in the assembly parameters, notify the server of the successful creation of the cloud resource, and send target feedback information to the server. After receiving the target feedback information, the server will send target feedback information back to the user's terminal. Furthermore, the public cloud can notify the server of the successful creation of the cloud resource by sending a message to the server, which can then send the message to the user's terminal. When the user sees the message, they can view the information of the created cloud resource on the interface of the agent platform corresponding to the server displayed on the user's terminal.

[0079] The aforementioned cloud resource processing method, upon receiving a cloud resource activation request from a user carrying a cloud resource identifier and an access token, obtains a temporary key pair with public cloud interface access permissions based on the access token. The temporary key pair and the cloud resource identifier are then assembled to obtain assembly parameters for interface access. An interface access request carrying these assembly parameters is sent to the public cloud interface. This allows access to the public cloud without requiring redirection to the public cloud for operation. The public cloud then performs corresponding operations based on the assembly parameters carried in the interface access request. Upon successful interface permission verification of the temporary key pair, the cloud resource is created based on the cloud resource identifier. Therefore, upon receiving target feedback information from the public cloud, target feedback information is sent back to the user, informing the user that the cloud resource has been created. The entire process allows for a simple and convenient way to acquire public cloud resources.

[0080] In one embodiment, obtaining a temporary key pair based on an access token includes:

[0081] Based on the access token, the user account information is retrieved from the preset account database. The user account information includes information about the public cloud shadow account, which is the certified account of the public cloud.

[0082] Using information from the public cloud shadow account, a temporary key pair is read from the preset account database.

[0083] The preset account database refers to a pre-configured database for storing user account information, including public cloud shadow accounts and login account information for the corresponding proxy platform. The public cloud shadow account is an authenticated account for the public cloud; it cannot directly log in to the public cloud, but it can be used to purchase, operate, and use public cloud resources.

[0084] Specifically, after obtaining the access token, the server retrieves the user account information from a pre-set account database based on the access token. This user account information includes information about the public cloud shadow account. After obtaining the user account information, the server reads the temporary key pair from the pre-set account database using the public cloud shadow account information. The temporary key pair corresponds to the user account information and is updated periodically. For users with interface access permissions, the server periodically updates their temporary key pairs and binds them to the user account information after the update, so that the temporary key pair can be retrieved based on the user account information when needed.

[0085] In this embodiment, by first searching for user account information from a preset account database based on the access token, and then reading the temporary key pair from the preset account database using the information of the public cloud shadow account in the user account information, it is possible to obtain the temporary key pair corresponding to each user.

[0086] In one embodiment, sending an interface access request carrying assembly parameters to the public cloud interface includes:

[0087] Determine the type of interface to be accessed based on the cloud resource identifier;

[0088] When the interface to be accessed is a standard interface, send an interface access request carrying assembly parameters to the standard interface;

[0089] When the interface to be accessed is a non-standard interface, the interface is adapted to the non-standard interface through annotation matching, and an interface access request carrying assembly parameters is sent to the non-standard interface.

[0090] In this context, standard interfaces refer to general-purpose interfaces applicable to most functions in the public cloud. For example, the interface for implementing a query function is a standard interface. Non-standard interfaces refer to interfaces used by a few specific functions in the public cloud. For example, the interface for implementing a payment function is a non-standard interface.

[0091] Specifically, the server first determines the type of the interface to be accessed based on the cloud resource operation identifier in the cloud resource identifier, and then accesses the public cloud according to the type of the interface. When the type of the interface to be accessed is a standard interface, the server can directly send an interface access request carrying assembly parameters to the standard interface through interface calls. When the type of the interface to be accessed is a non-standard interface, the server needs to adapt to the corresponding non-standard interface through annotation matching and send an interface access request carrying assembly parameters to the non-standard interface. Adapting to the corresponding non-standard interface through annotation matching refers to defining a separate controller in Spring (a Java programming language development framework) for routing.

[0092] In this embodiment, by first determining the type of the interface to be accessed based on the cloud resource identifier, and then sending an interface access request carrying assembly parameters to the public cloud interface in different ways according to the type of the interface to be accessed, accurate access to the public cloud can be achieved.

[0093] In one embodiment, after sending an interface access request carrying assembly parameters to the public cloud interface, the method further includes:

[0094] When a cloud resource creation failure message is received from the public cloud, the message is redirected to the user's device.

[0095] Specifically, when cloud resource creation fails, the public cloud will send a cloud resource creation failure message to the server. After receiving the cloud resource creation failure message, the server will convert and adapt the cloud resource creation failure message into a unified error code that can be displayed on the agent platform interface, and push the unified error code to the agent platform interface so that users can confirm the cloud resource creation failure through the agent platform interface and then initiate the cloud resource creation request again.

[0096] In this embodiment, when a cloud resource creation failure message is received from the public cloud, the message is redirected to the user's device, allowing the user to understand the situation regarding the failure of cloud resource creation.

[0097] In one embodiment, after receiving the target feedback information sent by the public cloud and sending the target feedback information to the user terminal, the method further includes:

[0098] When a work order processing request carrying work order information is received, the work order type of the work order to be processed is determined.

[0099] When the work order type is determined to be a valid work order based on the work order information, the work order processing request is pushed to the public cloud;

[0100] Periodically pull the status of pending work orders from the public cloud and provide feedback on the work order status.

[0101] The work order information describes problems encountered during cloud resource usage. For example, specific problems encountered during cloud resource usage could include host corruption, login failures, or operational issues with the reseller platform. Valid work orders refer to faults related to the public cloud. For example, a valid work order could specifically involve issues such as host corruption or login failures. Corresponding to valid work orders, there is also an invalid work order type, which refers to work orders involving operational issues with the reseller platform, i.e., faults unrelated to the public cloud.

[0102] Specifically, after successful cloud resource creation, users can view the created cloud resource information on the agent platform interface corresponding to the server displayed on the user's client and begin using the cloud resource. If a fault occurs during cloud resource use, users can send a work order processing request carrying work order information to the server through the agent platform interface. When receiving a work order processing request with work order information, the server will determine the work order type based on the work order information, i.e., whether the work order is valid or invalid. If the work order type is determined to be valid, the server will push the work order processing request to the public cloud to prompt the public cloud to process the valid work order, and periodically retrieve the work order status from the public cloud and report the work order status back to the sender of the work order processing request. If the work order type is determined to be invalid, the server will push the work order processing request to the corresponding staff on the agent platform for processing. The work order status can specifically include "processing," "awaiting customer supplementation," "pending closure," and "closed."

[0103] Furthermore, in addition to submitting work order processing requests, users can also perform work order operations such as work order evaluation and addition, work order reminder, work order closure, work order cancellation, and work order query. When the server receives a work order request corresponding to a work order operation, it will process it accordingly and pull the work order status from the public cloud for feedback.

[0104] For example, a flowchart illustrating a user's work order process can be shown as follows: Figure 3 As shown.

[0105] When submitting a work order processing request, the user first submits the request through the agent platform interface. After receiving the request, the server reviews it to determine the work order type. If the work order type is valid, it is approved and pushed to the public cloud for processing. If the work order type is invalid, it is rejected, and the user must handle the rejection themselves. After the work order processing request is pushed to the public cloud for processing, the server can periodically retrieve the work order status of pending work orders, i.e., retrieve the status progress messages. These status progress messages can specifically include "processing" or "awaiting customer supplementation."

[0106] When submitting work order evaluations, users first submit work order comment data through the agent platform's interface. After receiving the work order comment data, the server reviews it. If the review is approved, the comment interface is invoked to push the work order comment data to the public cloud. If the review is rejected, a comment rejection notification is submitted. Specifically, the server will only push the work order comment data to the public cloud if the comment is valid. A valid comment specifically refers to a comment related to the public cloud that does not involve operations performed by the agent platform.

[0107] When a user requests an order, the server calls the order request API, pushes an order request notification to the public cloud, and retrieves the corresponding work order status from the public cloud, i.e., retrieves the status progress message, which may specifically be "pending completion." When a user completes an order, the server calls the order closure API, pushes an order completion notification to the public cloud. When a user cancels an order, the server also calls the order closure API, pushes a cancellation notification to the public cloud. When a user needs to query work order details, the server calls the details API, retrieves the work order details, and provides feedback.

[0108] It should be noted that the public cloud side only responds to work orders and displays the status as "processing". If a status reversal is initiated, the status will be changed to "awaiting customer supplementation" or "awaiting order closure".

[0109] In this embodiment, when a work order processing request carrying work order information is received, the work order type of the corresponding work order to be processed is determined. When the work order type is determined to be a valid work order based on the work order information, the work order processing request is pushed to the public cloud. This enables effective processing of work order processing requests and saves public cloud resources. By periodically pulling the work order status of the work orders to be processed from the public cloud and providing feedback on the work order status, feedback on the work orders to be processed can be achieved so that users can understand the progress of work order processing.

[0110] In one embodiment, after receiving the target feedback information sent by the public cloud and sending the target feedback information to the user terminal, the method further includes:

[0111] Periodically pull cloud resource messages from the public cloud's message queue;

[0112] Push cloud resource messages to the corresponding target users.

[0113] Among them, cloud resource messages refer to the internal messages provided by the public cloud. Internal messages are a service function designed to facilitate business correspondence among members, similar to email. For example, internal messages can consist of four parts: inbox, outbox, drafts box, and spam box.

[0114] Specifically, since public cloud shadow accounts cannot be directly logged into on the public cloud, users using these accounts cannot directly receive cloud resource messages from the public cloud. Therefore, a server is needed as an intermediary to push these messages to the user's end. First, the public cloud synchronizes its cloud resource messages to its message queue. The server then periodically retrieves these messages from the queue and pushes them to the corresponding target user's end. The target user's end is the terminal used by the recipient of the cloud resource messages, as determined by the public cloud. Furthermore, after retrieving the cloud resource messages, the server preprocesses them to ensure they are pushed in a pre-defined standard format.

[0115] It's important to note that public cloud message queues involve access management policies. After creating a public cloud message queue, once the corresponding channel provider becomes an agent, the public cloud's access management system needs to first create a policy for the channel provider, then create a role, and finally bind the role to the policy. After binding, the public cloud's message center will enable the message queue service for the channel provider, create a message queue, and add the channel provider to the whitelist. Once the channel provider is whitelisted, its server can push messages to the public cloud message queue and periodically pull cloud resource messages from the public cloud message queue.

[0116] For example, the cloud resource message acquisition process involved in this embodiment can be as follows: Figure 4 As shown. Creating policies, creating roles, and binding policies to roles are all pre-configurations performed by the server's corresponding channel partners after they become agents and access the management system. Activating message queue services, selecting a region, creating a message queue, and adding channel partners to the whitelist are all pre-configurations performed by the public cloud's message center after successfully binding policies to roles. After completing these pre-configurations, the server can directly and periodically pull cloud resource messages, i.e., internal messages, from the public cloud's message queue. Simultaneously, the server can also directly push messages (e.g., ...). Figure 4 The message (deleting consumed messages) is sent to the public cloud's message queue. The public cloud can retrieve messages pushed by the server periodically. When pulling cloud resources from the public cloud's message queue, the server needs to send a pull request carrying the node, queue name, and key pair to the public cloud's message queue. Here, the node refers to the specific public cloud node, corresponding to the region where the public cloud is deployed; the queue name is the name of the message queue corresponding to the channel provider; and the key pair is the current temporary key pair.

[0117] In this embodiment, by periodically pulling cloud resource messages from the public cloud's message queue and pushing the cloud resource messages to the corresponding target user, it can act as an intermediary to achieve accurate transmission of cloud resource messages.

[0118] In one embodiment, before receiving the cloud resource activation request sent by the user client, the method further includes:

[0119] Receive user login requests sent by the client, which carry user login information;

[0120] Once the user's login information is verified, an access token is generated and sent to the user's device.

[0121] Specifically, when cloud resources need to be activated, the user first operates on the client side, which displays the interface of the agent platform corresponding to the server, sending a user login request carrying the user's login information to the server. After receiving the user login request, the server verifies the user login information. If the verification is successful, an access token is generated and issued to the user's client so that the user can proceed to the next step. That is, when a user logs in, the server verifies the user login information by comparing it with user information pre-stored in a security database. If the user login information passes the verification, an access token is generated and issued to the user's client.

[0122] In this embodiment, by receiving a user login request carrying user login information and verifying the user login information, an access token can be generated and sent to the user terminal after the user login information is verified, thus achieving accurate issuance of the access token.

[0123] In one embodiment, such as Figure 5 As shown, a cloud resource processing method is provided, which can be applied to... Figure 1 Taking client 102 as an example, the explanation includes the following steps:

[0124] Step 502: Send a cloud resource activation request to the server. The cloud resource activation request carries a cloud resource identifier and an access token. The access token is used to obtain a temporary key pair with public cloud interface access permissions. The temporary key pair is used to assemble with the cloud resource identifier to obtain assembly parameters. The assembly parameters are used to access the public cloud interface.

[0125] Step 504: Receive the target feedback information from the server. The target feedback information is generated and sent to the server by the public cloud after it has successfully verified the interface access permissions of the temporary key pair in the assembly parameters and created the cloud resource based on the cloud resource identifier in the assembly parameters.

[0126] Specifically, when cloud resources need to be activated, the user first operates on the client side, which displays the interface of the agent platform corresponding to the server, sending a user login request carrying the user's login information to the server. After receiving the user login request, the server verifies the user login information. If the verification is successful, it generates and issues an access token to the user's client, allowing the user to proceed to the next step. After receiving the access token, the user operates on the client side, which displays the interface of the agent platform corresponding to the server, sending a cloud resource activation request carrying the cloud resource identifier and the access token to the server.

[0127] Specifically, after receiving a cloud resource activation request, the server retrieves the corresponding user account information based on the access token. Using this user account information, it queries the temporary key pair corresponding to the user, obtaining the temporary key pair that grants the user public cloud interface access permissions. The server then assembles the temporary key pair and the cloud resource identifier to obtain assembly parameters for interface access. Based on the cloud resource identifier, it determines the type of interface to be accessed, and based on that, it identifies the public cloud interface to access. Finally, it sends an interface access request carrying the assembly parameters to the public cloud interface. The public cloud then verifies the interface access permissions of the temporary key pair in the assembly parameters to confirm whether the user corresponding to the temporary key pair has the necessary access permissions. When the interface access permission verification passes, the public cloud creates the cloud resource based on the cloud resource identifier in the assembly parameters and notifies the server of successful cloud resource creation. It also sends target feedback information to the server. Upon receiving the target feedback information from the server, the server sends feedback information back to the user's client. When the user receives the target feedback information from the server, they can view the created cloud resource information on the interface of the agent platform corresponding to the server displayed on their client. The aforementioned cloud resource processing method, by sending a cloud resource activation request carrying a cloud resource identifier and an access token to the server, enables the server to obtain a temporary key pair with public cloud interface access permissions based on the access token. The temporary key pair and the cloud resource identifier are then assembled to obtain assembly parameters for interface access. An interface access request carrying these assembly parameters is then sent to the public cloud interface. This allows access to the public cloud without requiring redirection to the public cloud for operation. The public cloud then performs corresponding operations based on the assembly parameters carried in the interface access request. Upon successful interface permission verification of the temporary key pair, the cloud resource is created based on the cloud resource identifier, and target feedback information is sent back to the server. Therefore, upon receiving the target feedback information from the server, the creation of the cloud resource can be confirmed. The entire process allows for a simple and convenient way to acquire public cloud resources.

[0128] In one embodiment, after receiving the target feedback information from the server, the method further includes:

[0129] Send a work order processing request carrying work order information to the server;

[0130] Receive the work order status feedback from the server.

[0131] Specifically, in the event of a failure while using cloud resources, users can send a work order processing request, carrying work order information, to the server through the agent platform interface on their client. Upon receiving the work order processing request, the server will determine the type of the work order based on the work order information. If the work order is determined to be valid, the server will push the work order processing request to the public cloud to prompt the public cloud to process the valid work order. The server will also periodically retrieve the work order status from the public cloud and provide feedback to the client. Furthermore, in addition to submitting work order processing requests, users can also perform work order operations such as work order evaluation and addition, expediting, closing, canceling, and querying work orders through the client. When the server receives a work order request corresponding to a work order operation, it will process it accordingly and retrieve the work order status from the public cloud for feedback.

[0132] In this embodiment, by sending a work order processing request carrying work order information to the server and receiving the work order status feedback from the server, feedback on the work order can be achieved so that the server can process it.

[0133] In one embodiment, after receiving the target feedback information from the server, the method further includes:

[0134] Receive cloud resource messages from the server. These cloud resource messages are messages that the server periodically pulls from the public cloud's message queue.

[0135] Specifically, since public cloud shadow accounts cannot be directly logged into on the public cloud, users using these accounts cannot receive public cloud resource messages. Therefore, a server is needed as an intermediary to push these messages to the user's end. The public cloud synchronizes its resource messages to its message queue, and the server periodically retrieves these messages from the queue. After retrieving the messages, the server sends them back to the user. It's important to note that public cloud resource messages can be pushed to specific target users. Therefore, after retrieving the messages, the server needs to determine which target users the messages should be pushed to before proceeding. Furthermore, after retrieving the messages, the server preprocesses them to ensure they are in a pre-defined standard format for delivery.

[0136] In this embodiment, by receiving cloud resource messages from the server, communication with the public cloud can be achieved through the server as an intermediary.

[0137] In one embodiment, such as Figure 6 As shown in the diagram, the cloud resource processing method of this application is illustrated by a flowchart, which specifically includes the following steps:

[0138] First, the user operates on the client side, which displays the interface of the agent platform (equivalent to a local cloud) corresponding to the server, to initiate the cloud resource activation process and send a message carrying the cloud resource identifier (i.e., Figure 6 The cloud resource activation request, containing the cloud resource identifier and access token, is sent to the server. Upon receiving the request, the server will retrieve the cloud resource activation information from the preset account database (i.e., the cloud resource identifier and access token). Figure 6 In IAM (Identity and Access Management), user account information is retrieved (i.e., Figure 6 The system uses the account ID in the user account information to read the temporary key pair from the preset account database.

[0139] After obtaining the temporary key pair, the server will assemble the temporary key pair and the cloud resource identifier to obtain the assembly parameters used for interface access (i.e., Figure 6 The assembly domain, operation, key pair, and business parameters (where the business parameters correspond to the product) are included. Simultaneously, the server determines the type of the interface to be accessed based on the cloud resource identifier. When the interface type is a standard interface, an interface access request carrying the assembly parameters is sent to the standard interface. When the interface type is a non-standard interface, annotation matching is used to adapt to the non-standard interface, and an interface access request carrying the assembly parameters is sent to the non-standard interface (i.e.,...). Figure 6 (Special product logic is adapted to different processing methods through annotation matching.) It should be noted that special product logic refers to the different types of interfaces corresponding to the functions of each cloud product, and the special logic needs to be adapted separately.

[0140] When the server receives a cloud resource creation failure message from the public cloud (i.e.) Figure 6 When a public cloud error code is encountered, it indicates that cloud resource creation has failed. In this case, the server will convert and adapt the public cloud error code into a unified error code that can be displayed on the agent platform interface (i.e., adapt the public cloud error code to the unified error code for the local cloud), and push this unified error code to the agent platform interface (i.e., Figure 6 (Return to frontend in the middle).

[0141] When the server receives the target feedback information from the public cloud, it indicates that the cloud resource has been successfully created. The server will then translate the target feedback information onto the agent platform's interface to notify the user that the cloud resource has been successfully created and can be used. The target feedback information is generated by the public cloud after creating the cloud resource based on the cloud resource identifier in the assembly parameters, once the interface access permission verification of the temporary key pair in the assembly parameters is passed.

[0142] Furthermore, the business architecture diagram corresponding to the cloud resource processing method of this application can be as follows: Figure 7 As shown, it mainly includes a cloud resource portal and console, a billing module, an account module, a work order management module, an internal messaging module, and an IAM module.

[0143] The cloud resource portal and console are separate components. The cloud resource portal is designed for displaying cloud resources, showcasing basic information such as the cloud resources supported by the reseller platform, their introductions, instructions, and operation manuals. Users can view and purchase cloud resources through the portal. The console is for cloud resource operation and usage. Users can purchase resources through the reseller platform interface or activate cloud resources through the console. The console also provides operations for cloud resource instances, covering all supported cloud resource types. Operations include instance usage, configuration changes, and monitoring. It serves as the user's entry point for accessing cloud resources. The console is categorized by resource type, with menus divided into compute, storage, and network resource types.

[0144] The billing module is primarily responsible for the order placement and payment environment during the user's cloud resource activation process. It also generates and retrieves orders generated by users using cloud resource products, enabling users to view orders, bills, and issue invoices. Furthermore, the billing module provides reporting capabilities, offering multi-dimensional billing and order reports, as well as resource consumption statistics charts, facilitating timely information access for administrators on the agent platform.

[0145] The account module is responsible for user registration on the agent platform and real-name authentication of the corresponding public cloud shadow accounts. It is a fundamental capability of the platform. Cloud resource purchases involve public cloud resource operations, which require a real-name authenticated agent account on the public cloud, i.e., a public cloud shadow account. The account module connects with the public cloud account system to enable the public cloud resource purchase function. As a fundamental capability of the platform, it also provides basic platform account management capabilities.

[0146] The cloud resource processing method in this application provides a complete closed loop of cloud resource creation, operation, and settlement functions. When users operate cloud resources, a resource entry point is required. When users encounter resource usage problems, environmental issues, instance failures, etc., a work order entry point is required to facilitate communication with the public cloud and help users troubleshoot usage problems. The work order module provides an entry point to facilitate communication and troubleshooting between users and the public cloud when faults occur.

[0147] The in-site messaging module serves as a message channel. When a user purchases or destroys cloud resources, this module sends a public cloud channel message, ensuring the user receives timely notifications regarding public cloud resource creation, destruction, and billing after activation. This connects the agent platform with the public cloud channel. Users can view and subscribe to messages without logging into the public cloud.

[0148] Among them, IAM (Identity and Access Management) is mainly used to manage registration, accounts, whitelists, authorization & permissions, proxy accounts (i.e., public cloud shadow accounts) and in-site messages.

[0149] In addition, such as Figure 7 As shown, the public cloud basic interface services include cloud interfaces, account-related services, and message queues. The Account & Permissions unit primarily involves management of service suspension due to overdue payments, message center, permissions, and accounts. The product module also provides additional product interfaces. For data storage, it mainly uses a distributed database (DistributedMySQL) and a remote dictionary service (CRedis, Remote Dictionary Server). The infrastructure includes edge clusters and physical machine deployments / cloud hosts.

[0150] It should be noted that the cloud resource processing method used in this application differs from the traditional converged cloud model. It directly provides interface sales capabilities through the public cloud to sell platform cloud resources. This platform does not use third-party platforms to redirect to the public cloud. It covers all functions including product portal, resource console, purchase, billing, order, in-site messaging, and work orders. It can meet the needs of agents to build their own cloud platforms based on the public cloud. Agents' users purchase, use, and settle accounts all through the agent platform. The agent platform serves as the underlying infrastructure, applicable to large enterprises to build their own cloud platforms based on the public cloud. This allows them to enjoy public cloud resources while maintaining a closed business loop, increasing scalability and platform technical capabilities. The agent platform is integrated with the public cloud at its core, including account information, agent whitelisting, channel management, billing, and work order integration. Through the agent platform, a self-contained loop for user purchase, use, settlement, and work order feedback is achieved. Users do not need to log in to the public cloud to use cloud resources; they can use them directly through the agent platform. Users purchase cloud resources through the agent platform, the public cloud activates the cloud resources, and users utilize and settle cloud resource payments, billing information, and order details on the agent platform. Specifically, the agent platform provides billing capabilities and offers two payment modes: mandatory payment on behalf of the user and self-payment. In the mandatory payment mode, the user's payment is directly deducted by the agent, and the agent settles with the public cloud, while the user settles with the agent. In the self-payment mode, the user settles directly with the public cloud through payment channels such as UnionPay and WeChat. The agent platform integrates with the public cloud's ticket processing. When users encounter problems while using cloud resources, they can directly contact the public cloud by submitting a ticket, which the public cloud will then handle and follow up on, providing convenience for users. The agent platform also integrates with the public cloud's internal messaging system. After purchasing cloud resources through the agent platform, users can receive internal messages from the public cloud on the agent platform without needing to log in to the public cloud to view them.

[0151] The agent platform involved in this embodiment can meet users' needs for reselling public cloud resources. It also eliminates concerns about customer loss caused by the traditional method of redirecting users to the public cloud when using cloud resources, which lacks platform activity and traffic maintenance. After registering as a public cloud channel provider and activating agent permissions, agents can act as agents for public cloud resources. The product covers IaaS, PaaS (Platform as a Service), and SaaS products. IaaS provides sub-services such as computing, storage, networking, and security to meet users' needs for using public cloud resources, while also providing basic functions to facilitate user access to cloud resources. The product offers flexible and convenient payment options, including mandatory payment on behalf and self-payment, to meet different customer needs. It also provides modules for billing, in-site messaging, and support tickets to enhance the user experience.

[0152] It should be understood that although the steps in the flowcharts of the embodiments described above 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 embodiments described above 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.

[0153] Based on the same inventive concept, this application also provides a cloud resource processing apparatus for implementing the cloud resource processing method described above. The solution provided by this apparatus is similar to the implementation scheme described in the above method; therefore, the specific limitations in one or more cloud resource processing apparatus embodiments provided below can be found in the limitations of the cloud resource processing method described above, and will not be repeated here.

[0154] In one embodiment, such as Figure 8 As shown, a cloud resource processing device is provided, including: a request receiving module 802, an acquisition module 804, an assembly module 806, an access module 808, and a prompt receiving module 810, wherein:

[0155] The request receiving module 802 is used to receive cloud resource activation requests sent by the user terminal. The cloud resource activation request carries a cloud resource identifier and an access token.

[0156] The acquisition module 804 is used to obtain a temporary key pair based on the access token. The temporary key pair is a key pair with public cloud interface access permissions.

[0157] Assembly module 806 is used to assemble temporary key pairs and cloud resource identifiers to obtain assembly parameters for interface access;

[0158] Access module 808 is used to send an interface access request carrying assembly parameters to the public cloud interface;

[0159] The prompt receiving module 810 is used to send target feedback information to the user terminal when it receives target feedback information sent by the public cloud. The target feedback information is generated by the public cloud after creating cloud resources based on the cloud resource identifier in the assembly parameters when the interface access permission verification of the temporary key pair in the assembly parameters is passed.

[0160] The aforementioned cloud resource processing device, upon receiving a cloud resource activation request from a user terminal carrying a cloud resource identifier and an access token, obtains a temporary key pair with public cloud interface access permissions based on the access token, assembles the temporary key pair and the cloud resource identifier to obtain assembly parameters for interface access, and sends an interface access request carrying the assembly parameters to the public cloud interface. This enables access to the public cloud without requiring redirection to the public cloud for operation, allowing the public cloud to perform corresponding operations based on the assembly parameters carried in the interface access request. When the interface permission verification of the temporary key pair passes, the cloud resource is created based on the cloud resource identifier. Thus, upon receiving target feedback information from the public cloud, target feedback information is sent back to the user terminal, informing the user terminal that the cloud resource has been created. The entire process allows for simple and convenient acquisition of public cloud resources.

[0161] In one embodiment, the acquisition module is further configured to retrieve user account information from a preset account database based on the access token. The user account information includes information about a public cloud shadow account, which is an authenticated account of the public cloud. The module then reads a temporary key pair from the preset account database using the information of the public cloud shadow account.

[0162] In one embodiment, the access module is further configured to determine the type of the interface to be accessed based on the cloud resource identifier. When the type of the interface to be accessed is a standard interface, an interface access request carrying assembly parameters is sent to the standard interface. When the type of the interface to be accessed is a non-standard interface, the module adapts to the non-standard interface through annotation matching and sends an interface access request carrying assembly parameters to the non-standard interface.

[0163] In one embodiment, the prompt receiving module is further configured to, when receiving a cloud resource creation failure prompt from the public cloud, convert the cloud resource creation failure prompt to the user terminal.

[0164] In one embodiment, the cloud resource processing device further includes a work order processing module. The work order processing module is used to determine the work order type of the work order to be processed when it receives a work order processing request carrying work order information. When the work order type is determined to be a valid work order based on the work order information, the work order processing request is pushed to the public cloud. The work order processing module is also used to periodically pull the work order status of the work order to be processed from the public cloud and provide feedback on the work order status.

[0165] In one embodiment, the cloud resource processing device further includes a message processing module, which is used to periodically pull cloud resource messages from the public cloud's message queue and push the cloud resource messages to the corresponding target user terminal.

[0166] In one embodiment, the request receiving module is further configured to receive a user login request sent by the user terminal. The user login request carries user login information. After the user login information is verified, an access token is generated and issued to the user terminal.

[0167] In one embodiment, such as Figure 9 As shown, a cloud resource processing device is provided, including: a sending module 902 and a receiving module 904, wherein:

[0168] The sending module 902 is used to send a cloud resource activation request to the server. The cloud resource activation request carries a cloud resource identifier and an access token. The access token is used to obtain a temporary key pair with public cloud interface access permissions. The temporary key pair is used to assemble with the cloud resource identifier to obtain assembly parameters. The assembly parameters are used to access the public cloud interface.

[0169] The receiving module 904 is used to receive the target feedback information from the server. The target feedback information is generated by the public cloud after creating cloud resources based on the cloud resource identifier in the assembly parameters when the interface access permission verification of the temporary key pair in the assembly parameters is passed.

[0170] The aforementioned cloud resource processing device, by sending a cloud resource activation request carrying a cloud resource identifier and an access token to the server, enables the server to obtain a temporary key pair with public cloud interface access permissions based on the access token. The temporary key pair and the cloud resource identifier are assembled to obtain assembly parameters for interface access. An interface access request carrying these assembly parameters is then sent to the public cloud interface. This allows access to the public cloud without requiring redirection to the public cloud for operation. The public cloud then performs corresponding operations based on the assembly parameters carried in the interface access request. When the interface permission verification of the temporary key pair passes, the cloud resource is created based on the cloud resource identifier, and target feedback information is sent back to the server. Upon receiving the target feedback information from the server, the creation of the cloud resource can be confirmed. The entire process allows for simple and convenient acquisition of public cloud resources.

[0171] Each module in the aforementioned cloud resource processing device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device, or stored in the memory of a computer device as software, so that the processor can call and execute the operations corresponding to each module.

[0172] In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 10As shown, this computer device includes a processor, memory, input / output interfaces (I / O), and a communication interface. The processor, memory, and I / O interfaces are connected via a system bus, and the communication interface is also connected to the system bus via the I / O interfaces. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and a database. The internal memory provides the environment for the operating system and computer programs stored in the non-volatile storage media. The database stores user account information and other data. The I / O interfaces are used for exchanging information between the processor and external devices. The communication interface is used for communicating with external terminals via a network. When the computer program is executed by the processor, it implements a cloud resource processing method.

[0173] Those skilled in the art will understand that Figure 10 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0174] In one embodiment, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to perform the following steps:

[0175] Receive cloud resource activation requests sent by the user client. The cloud resource activation requests carry cloud resource identifiers and access tokens.

[0176] Obtain a temporary key pair based on the access token. The temporary key pair is a key pair with access permissions to the public cloud interface.

[0177] The temporary key pair and the cloud resource identifier are assembled to obtain the assembly parameters used for interface access;

[0178] Send an interface access request carrying assembly parameters to the public cloud interface;

[0179] When the target feedback information is received from the public cloud, the target feedback information is sent back to the user terminal. The target feedback information is generated by the public cloud after it has successfully verified the interface access permissions of the temporary key pair in the assembly parameters and created the cloud resource based on the cloud resource identifier in the assembly parameters.

[0180] In one embodiment, when the processor executes the computer program, it further performs the following steps: based on the access token, it searches for user account information from a preset account database, the user account information including information of a public cloud shadow account, the public cloud shadow account being an authenticated account of the public cloud, and reads a temporary key pair from the preset account database using the information of the public cloud shadow account.

[0181] In one embodiment, when the processor executes the computer program, it further performs the following steps: determining the type of the interface to be accessed based on the cloud resource identifier; when the type of the interface to be accessed is a standard interface, sending an interface access request carrying assembly parameters to the standard interface; when the type of the interface to be accessed is a non-standard interface, adapting to the non-standard interface through annotation matching, and sending an interface access request carrying assembly parameters to the non-standard interface.

[0182] In one embodiment, when the processor executes the computer program, it further performs the following steps: when it receives a cloud resource creation failure message from the public cloud, it translates the cloud resource creation failure message to the user terminal.

[0183] In one embodiment, when the processor executes the computer program, it further implements the following steps: when a work order processing request carrying work order information is received, the work order type of the work order to be processed is determined; when the work order type is determined to be a valid work order based on the work order information, the work order processing request is pushed to the public cloud; the work order status of the work order to be processed is periodically retrieved from the public cloud, and the work order status is fed back.

[0184] In one embodiment, when the processor executes the computer program, it also performs the following steps: periodically pulls cloud resource messages from the public cloud's message queue and pushes the cloud resource messages to the corresponding target user terminal.

[0185] In one embodiment, when the processor executes the computer program, it further performs the following steps: receiving a user login request sent by the user terminal, the user login request carrying user login information, and generating and issuing an access token to the user terminal after the user login information is verified.

[0186] In one embodiment, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to perform the following steps:

[0187] Send a cloud resource activation request to the server. The cloud resource activation request carries a cloud resource identifier and an access token. The access token is used to obtain a temporary key pair with public cloud interface access permissions. The temporary key pair is used to assemble with the cloud resource identifier to obtain assembly parameters. The assembly parameters are used to access the public cloud interface.

[0188] The system receives target feedback information from the server. This target feedback information is generated and sent to the server by the public cloud after it has successfully verified the interface access permissions of the temporary key pair in the assembly parameters and created the cloud resource based on the cloud resource identifier in the assembly parameters.

[0189] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, the computer program performing the following steps when executed by a processor:

[0190] Receive cloud resource activation requests sent by the user client. The cloud resource activation requests carry cloud resource identifiers and access tokens.

[0191] Obtain a temporary key pair based on the access token. The temporary key pair is a key pair with access permissions to the public cloud interface.

[0192] The temporary key pair and the cloud resource identifier are assembled to obtain the assembly parameters used for interface access;

[0193] Send an interface access request carrying assembly parameters to the public cloud interface;

[0194] When the target feedback information is received from the public cloud, the target feedback information is sent back to the user terminal. The target feedback information is generated by the public cloud after it has successfully verified the interface access permissions of the temporary key pair in the assembly parameters and created the cloud resource based on the cloud resource identifier in the assembly parameters.

[0195] In one embodiment, when the computer program is executed by the processor, it further performs the following steps: based on the access token, it searches for user account information from a preset account database, the user account information including information of a public cloud shadow account, the public cloud shadow account being an authenticated account of the public cloud, and reads a temporary key pair from the preset account database using the information of the public cloud shadow account.

[0196] In one embodiment, when the computer program is executed by the processor, it further performs the following steps: determining the type of the interface to be accessed based on the cloud resource identifier; when the type of the interface to be accessed is a standard interface, sending an interface access request carrying assembly parameters to the standard interface; when the type of the interface to be accessed is a non-standard interface, adapting to the non-standard interface through annotation matching, and sending an interface access request carrying assembly parameters to the non-standard interface.

[0197] In one embodiment, when the computer program is executed by the processor, it further performs the following steps: when a cloud resource creation failure message is received from the public cloud, the cloud resource creation failure message is translated and sent to the user terminal.

[0198] In one embodiment, when the computer program is executed by the processor, it further performs the following steps: when a work order processing request carrying work order information is received, the work order type of the work order to be processed is determined; when the work order type is determined to be a valid work order based on the work order information, the work order processing request is pushed to the public cloud; the work order status of the work order to be processed is periodically retrieved from the public cloud, and the work order status is fed back.

[0199] In one embodiment, when the computer program is executed by the processor, it also performs the following steps: periodically pulls cloud resource messages from the public cloud's message queue and pushes the cloud resource messages to the corresponding target user terminal.

[0200] In one embodiment, when the computer program is executed by the processor, it further performs the following steps: receiving a user login request sent by the user terminal, the user login request carrying user login information, and generating and issuing an access token to the user terminal after the user login information is verified.

[0201] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, the computer program performing the following steps when executed by a processor:

[0202] Send a cloud resource activation request to the server. The cloud resource activation request carries a cloud resource identifier and an access token. The access token is used to obtain a temporary key pair with public cloud interface access permissions. The temporary key pair is used to assemble with the cloud resource identifier to obtain assembly parameters. The assembly parameters are used to access the public cloud interface.

[0203] The system receives target feedback information from the server. This target feedback information is generated and sent to the server by the public cloud after it has successfully verified the interface access permissions of the temporary key pair in the assembly parameters and created the cloud resource based on the cloud resource identifier in the assembly parameters.

[0204] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, performs the following steps:

[0205] Receive cloud resource activation requests sent by the user client. The cloud resource activation requests carry cloud resource identifiers and access tokens.

[0206] Obtain a temporary key pair based on the access token. The temporary key pair is a key pair with access permissions to the public cloud interface.

[0207] The temporary key pair and the cloud resource identifier are assembled to obtain the assembly parameters used for interface access;

[0208] Send an interface access request carrying assembly parameters to the public cloud interface;

[0209] When the target feedback information is received from the public cloud, the target feedback information is sent back to the user terminal. The target feedback information is generated by the public cloud after it has successfully verified the interface access permissions of the temporary key pair in the assembly parameters and created the cloud resource based on the cloud resource identifier in the assembly parameters.

[0210] In one embodiment, when the computer program is executed by the processor, it further performs the following steps: based on the access token, it searches for user account information from a preset account database, the user account information including information of a public cloud shadow account, the public cloud shadow account being an authenticated account of the public cloud, and reads a temporary key pair from the preset account database using the information of the public cloud shadow account.

[0211] In one embodiment, when the computer program is executed by the processor, it further performs the following steps: determining the type of the interface to be accessed based on the cloud resource identifier; when the type of the interface to be accessed is a standard interface, sending an interface access request carrying assembly parameters to the standard interface; when the type of the interface to be accessed is a non-standard interface, adapting to the non-standard interface through annotation matching, and sending an interface access request carrying assembly parameters to the non-standard interface.

[0212] In one embodiment, when the computer program is executed by the processor, it further performs the following steps: when a cloud resource creation failure message is received from the public cloud, the cloud resource creation failure message is translated and sent to the user terminal.

[0213] In one embodiment, when the computer program is executed by the processor, it further performs the following steps: when a work order processing request carrying work order information is received, the work order type of the work order to be processed is determined; when the work order type is determined to be a valid work order based on the work order information, the work order processing request is pushed to the public cloud; the work order status of the work order to be processed is periodically retrieved from the public cloud, and the work order status is fed back.

[0214] In one embodiment, when the computer program is executed by the processor, it also performs the following steps: periodically pulls cloud resource messages from the public cloud's message queue and pushes the cloud resource messages to the corresponding target user terminal.

[0215] In one embodiment, when the computer program is executed by the processor, it further performs the following steps: receiving a user login request sent by the user terminal, the user login request carrying user login information, and generating and issuing an access token to the user terminal after the user login information is verified.

[0216] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, performs the following steps:

[0217] Send a cloud resource activation request to the server. The cloud resource activation request carries a cloud resource identifier and an access token. The access token is used to obtain a temporary key pair with public cloud interface access permissions. The temporary key pair is used to assemble with the cloud resource identifier to obtain assembly parameters. The assembly parameters are used to access the public cloud interface.

[0218] The system receives target feedback information from the server. This target feedback information is generated and sent to the server by the public cloud after it has successfully verified the interface access permissions of the temporary key pair in the assembly parameters and created the cloud resource based on the cloud resource identifier in the assembly parameters.

[0219] It should be noted that the user information (including but not limited to user account information) and data (including but not limited to data used for analysis, data stored, data displayed) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of the relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions.

[0220] 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, and when executed, it 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 application 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 application 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 application 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.

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

[0222] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A cloud resource processing method, characterized in that, Applied to a server, the method includes: Receive a user login request sent by the user terminal, wherein the user login request carries user login information; When the user login information is verified, an access token is generated and sent to the user's terminal. The system receives a cloud resource activation request sent by a user client. The cloud resource activation request carries a cloud resource identifier and an access token. The access token refers to the identity authorization information issued by the server to the user client after the user logs into the third-party platform corresponding to the server. Based on the access token, user account information is retrieved from a preset account database. The user account information includes information about a public cloud shadow account. The public cloud shadow account is an authenticated account of the public cloud and cannot directly log in to the public cloud. Using the information of the public cloud shadow account, a temporary key pair is read from the preset account database. The temporary key pair is a key pair with public cloud interface access permissions and is updated regularly. After the update is completed, it is bound to the user account information. The temporary key pair and the cloud resource identifier are assembled to obtain assembly parameters for interface access; Send an interface access request carrying the assembly parameters to the public cloud interface; When the target feedback information sent by the public cloud is received, the target feedback information is fed back to the user terminal. The target feedback information is generated by the public cloud after creating cloud resources based on the cloud resource identifier in the assembly parameters when the interface access permission verification of the temporary key pair in the assembly parameters is passed.

2. The method according to claim 1, characterized in that, The interface that sends the interface access request carrying the assembly parameters to the public cloud includes: The type of the interface to be accessed is determined based on the cloud resource identifier; When the interface to be accessed is a standard interface, an interface access request carrying the assembly parameters is sent to the standard interface. When the interface to be accessed is a non-standard interface, the interface is adapted to the non-standard interface through annotation matching, and an interface access request carrying the assembly parameters is sent to the non-standard interface.

3. The method according to claim 1, characterized in that, After sending the interface access request carrying the assembly parameters to the public cloud interface, the method further includes: When a cloud resource creation failure message is received from the public cloud, the message is forwarded to the user's client.

4. The method according to any one of claims 1 to 3, characterized in that, After receiving the target feedback information sent by the public cloud and sending the target feedback information back to the user terminal, the process further includes: When a work order processing request carrying work order information is received, the work order type of the work order to be processed is determined. When the work order type is determined to be a valid work order based on the work order information, the work order processing request is pushed to the public cloud; The status of the pending work orders is periodically pulled from the public cloud and the work order status is fed back.

5. The method according to any one of claims 1 to 3, characterized in that, After receiving the target feedback information sent by the public cloud and sending the target feedback information back to the user terminal, the process further includes: Periodically pull cloud resource messages from the message queue of the public cloud; The cloud resource message is pushed to the corresponding target user terminal.

6. A cloud resource processing method, characterized in that, The method includes: Send a user login request to the server, the user login request carrying user login information; Receive the access token issued by the server after the user's login information has been verified; A cloud resource activation request is sent to the server. The cloud resource activation request carries a cloud resource identifier and an access token. The access token is the identity authorization information issued by the server to the user after the user logs in to the third-party platform corresponding to the server. The access token is used to look up user account information from a preset account database. The user account information includes information about a public cloud shadow account. The public cloud shadow account is an authenticated account of the public cloud and cannot directly log in to the public cloud. It is used to read a temporary key pair from the preset account database. The temporary key pair is a key pair with public cloud interface access permissions and is updated periodically. After the update is completed, it is bound to the user account information. The temporary key pair is used to assemble with the cloud resource identifier to obtain assembly parameters. The assembly parameters are used to access the public cloud interface. The system receives target feedback information from the server. This target feedback information is generated and sent to the server by the public cloud after it has successfully verified the interface access permissions of the temporary key pair in the assembly parameters and created the cloud resource based on the cloud resource identifier in the assembly parameters.

7. A cloud resource processing device, characterized in that, The device includes: The request receiving module is used to receive user login requests sent by the user terminal. The user login requests carry user login information. When the user login information is verified, an access token is generated and issued to the user terminal. The module also receives cloud resource activation requests sent by the user terminal. The cloud resource activation requests carry cloud resource identifiers and access tokens. The access token refers to the identity authorization information issued by the server to the user terminal after the user logs into the third-party platform corresponding to the server. The acquisition module is used to retrieve user account information from a preset account database based on the access token. The user account information includes information about a public cloud shadow account. The public cloud shadow account is an authenticated account of the public cloud and cannot directly log in to the public cloud. The module reads a temporary key pair from the preset account database using the information of the public cloud shadow account. The temporary key pair is a key pair with public cloud interface access permissions and is updated regularly. After the update is completed, it is bound to the user account information. An assembly module is used to assemble the temporary key pair and the cloud resource identifier to obtain assembly parameters for interface access; The access module is used to send an interface access request carrying the assembly parameters to the public cloud interface; The prompt receiving module is used to send the target feedback information to the user terminal when it receives the target feedback information sent by the public cloud. The target feedback information is generated by the public cloud after creating cloud resources based on the cloud resource identifier in the assembly parameters when the interface access permission verification of the temporary key pair in the assembly parameters is passed.

8. The apparatus according to claim 7, characterized in that, The access module is further configured to determine the type of the interface to be accessed based on the cloud resource identifier. When the type of the interface to be accessed is a standard interface, an interface access request carrying the assembly parameters is sent to the standard interface. When the type of the interface to be accessed is a non-standard interface, the module adapts to the non-standard interface through annotation matching and sends an interface access request carrying the assembly parameters to the non-standard interface.

9. The apparatus according to claim 7, characterized in that, The prompt receiving module is also used to, when receiving a cloud resource creation failure prompt from the public cloud, convert the cloud resource creation failure prompt to the user terminal.

10. The apparatus according to any one of claims 7 to 9, characterized in that, The device further includes a work order processing module, which is used to determine the work order type of the work order to be processed when a work order processing request carrying work order information is received; when the work order type is determined to be a valid work order based on the work order information, the work order processing request is pushed to the public cloud; and the work order status of the work order to be processed is periodically pulled from the public cloud and the work order status is fed back.

11. The apparatus according to any one of claims 7 to 9, characterized in that, The device also includes a message processing module, which is used to periodically pull cloud resource messages from the message queue of the public cloud and push the cloud resource messages to the corresponding target user terminal.

12. A cloud resource processing device, characterized in that, The device includes: The sending module is used to send a user login request to the server, the user login request carrying user login information, receive an access token issued by the server after the user login information is verified, and send a cloud resource activation request to the server, the cloud resource activation request carrying a cloud resource identifier and an access token. The access token refers to the identity authorization information issued by the server to the user after the user logs into the third-party platform corresponding to the server. The access token is used to look up user account information from a preset account database. The user account information includes information about a public cloud shadow account. The public cloud shadow account is an authenticated account of the public cloud and cannot directly log in to the public cloud. The module is also used to read a temporary key pair from the preset account database. The temporary key pair is a key pair with public cloud interface access permissions and is updated periodically. After the update is completed, it is bound to the user account information. The temporary key pair is used to assemble with the cloud resource identifier to obtain assembly parameters. The assembly parameters are used to access the public cloud interface. The receiving module is used to receive the target feedback information fed back by the server. The target feedback information is generated and sent to the server by the public cloud after it has successfully verified the interface access permission of the temporary key pair in the assembly parameters and created the cloud resource based on the cloud resource identifier in the assembly parameters.

13. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 6.

14. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.

15. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.

Images