# US 2025/0217857 A1 · Public Cloud-Based Cloud Resource Conversion Method and Cloud Management Platform

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2025/0217857 A1
- Document ID: US20250217857A1
- Status: Published application
- Kind: A1
- Application number: 19/055,069
- Filed: 2025-02-17
- Published: 2025-07-03
- Earliest claimed: 2022-08-18
- Assignees: Huawei Cloud Computing Technologies Co., Ltd.
- Applicants: Huawei Cloud Computing Technologies Co., Ltd.
- Inventors: Mosong Zhou; Lei Zhu; Qian Peng; Fujun Chen; Shaozhi Zhang; Shijia Ma; Changpeng Yang
- Web page: https://patentgrep.com/patent/US20250217857A1

## CPC

- G06F 9/5072: {Grid computing}
- G06Q 30/04: Billing or invoicing
- G06F 9/4881: {Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues}
- G06F 9/5005: {to service a request}
- G06Q 30/0283: Price estimation or determination
- H04L 12/14: Charging, metering or billing arrangements specially adapted for data communications, e.g. authentication, authorisation and accounting [AAA] framework
- H04M 15/00: Arrangements for metering, time-control or time indication {; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP}
- H04M 15/83: {Notification aspects}
- H04M 15/852: {Low balance or limit reached}
- H04M 15/853: {Calculate maximum communication time or volume}
- H04M 15/854: {Available credit}
- H04M 15/88: {Provision for limiting connection, or expenditure}
- H04M 15/881: {for continuing the call beyond the limit using allow grace}
- H04M 17/00: Prepayment {of wireline communication systems, wireless communication systems or} telephone systems (using a coded card to authorise calls from a telephone set H04M1/675)
- H04W 4/24: Accounting or billing
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04M: TELEPHONIC COMMUNICATION (circuits for controlling other apparatus via a telephone cable and not involving telephone switching apparatus G08)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

A public cloud-based cloud resource conversion method includes receiving, from a cloud resource configuration interface, cloud resource configuration information input by a tenant; creating, in an infrastructure based on the cloud resource configuration information, a cloud resource that belongs to the tenant as a stable cloud resource; receiving a first cloud resource type conversion policy input by the tenant; and converting, a type attribute of the cloud resource from a stable cloud resource type to an unstable cloud resource type.

## Claims

### Claim 1

A method implemented by a cloud management platform, wherein the method comprises:
receiving, from a tenant via a cloud resource configuration interface, cloud resource configuration information comprising a specification and a type attribute of a to-be-created cloud resource, wherein the type attribute indicates a stable cloud resource;
creating, based on the cloud resource configuration information, a cloud resource that has the specification and the type attribute and that is for the tenant;
receiving, from the tenant via a cloud resource type conversion interface, a first cloud resource type conversion policy indicating to convert the type attribute from indicating the stable cloud resource to indicating an unstable cloud resource;
converting, based on the first cloud resource type conversion policy, the type attribute from indicating the stable cloud resource to indicating the unstable cloud resource;
performing first billing on use of the cloud resource in a preferential manner based on type attribute indicating the unstable cloud resource; and
stopping providing, based on the first billing, the cloud resource for the tenant when the tenant does not actively release the cloud resource and idle resources are insufficient.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
receiving, from the tenant, via the cloud resource type conversion interface, and after converting the type attribute, a second cloud resource type conversion policy indicating to convert the type attribute from indicating the unstable cloud resource to indicating the stable cloud resource;
converting, based on the second cloud resource type conversion policy, the type attribute from indicating the unstable cloud resource to indicating the stable cloud resource;
performing second billing on use of the cloud resource in a non-preferential manner based on the type attribute indicating the stable cloud resource; and
continuing providing, based on the second billing, the cloud resource for the tenant when the tenant does not actively release the cloud resource and the idle resources are insufficient.

### Claim 3 (depends on 2)

The method of claim 2, further comprising:
counting type attribute conversion times of the cloud resource; and
forbidding performing next type attribute conversion or charging the tenant for the next type attribute conversion when the type attribute conversion times exceed a threshold.

### Claim 4 (depends on 1)

The method of claim 1, further comprising:
calculating a type attribute conversion ratio of the cloud resource; and
forbidding performing type attribute conversion or charging the tenant when the type attribute conversion ratio exceeds a threshold.

### Claim 5 (depends on 1)

The method of claim 1, wherein after creating the cloud resource, the method further comprises:
performing second billing on use of the cloud resource in a non-preferential manner based on the type attribute indicating the stable cloud resource; and
continuing providing, based on the second billing, the cloud resource for the tenant when the tenant does not actively release the cloud resource and the idle resources are insufficient.

### Claim 6 (depends on 1)

The method of claim 1, wherein the stable cloud resource comprises a pay-per-use billing, a yearly/monthly billing, or a reserved instance.

### Claim 7 (depends on 1)

The method of claim 1, wherein the unstable cloud resource comprises a spot pricing billing or a spot block billing.

### Claim 8 (depends on 1)

The method of claim 1, wherein the cloud resource comprises a computing resource, a network resource, or a storage resource.

### Claim 9

A computing device cluster, comprising:
at least one computing device, comprising:
a memory configured to store instructions; and
one or more processors coupled to the memory, wherein when executed by the one or more processors, the instructions cause the computing device cluster to:
receive, from a tenant via a cloud resource configuration interface, cloud resource configuration information comprising a specification and a type attribute of a to-be-created cloud resource, wherein the type attribute indicates is a stable cloud resource;
create, based on the cloud resource configuration information, a cloud resource that has the specification and the type attribute and that is for the tenant;
receive, from the tenant via a cloud resource conversion interface, a first cloud resource type conversion policy indicating to convert the type attribute from indicating the stable cloud resource to indicating an unstable cloud resource;
convert, based on the first cloud resource type conversion policy, the type attribute from indicating the stable cloud resource to indicating the unstable cloud resource;
perform first billing on use of the cloud resource in a preferential manner based on type attribute indicating the unstable cloud resource; and
stop providing, based on the first billing, the cloud resource for the tenant when the tenant does not actively release the cloud resource and idle resources are insufficient.

### Claim 10 (depends on 9)

The computing device cluster of claim 9, wherein when executed by the one or more processors, the instructions further cause the computing device cluster to:
receive, from the tenant, via the cloud resource type conversion interface, and after converting the type attribute, a second cloud resource type conversion policy indicating to convert the type attribute from indicating the unstable cloud resource to indicating the stable cloud resource;
convert, based on the second cloud resource type conversion policy, the type attribute from indicating the unstable cloud resource to indicating the stable cloud resource;
perform second billing on use of the cloud resource in a non-preferential manner based on the type attribute indicating the stable cloud resource; and
continue providing, based on the second billing, the cloud resource for the tenant when the tenant does not actively release the cloud resource and the idle resources are insufficient.

### Claim 11 (depends on 10)

The computing device cluster of claim 10, wherein when executed by the one or more processors, the instructions further cause the computing device cluster to:
count type attribute conversion times of the cloud resource, and
forbid performing next type attribute conversion or charge the tenant for the next type attribute conversion when the type attribute conversion times exceed a threshold.

### Claim 12 (depends on 9)

The computing device cluster of claim 9, wherein when executed by the one or more processors, the instructions further cause the computing device cluster to:
calculate a type attribute conversion ratio of the cloud resource; and
forbid performing type attribute conversion or charge the tenant when the type attribute conversion ratio of the cloud resource exceeds a threshold.

### Claim 13 (depends on 9)

The computing device cluster of claim 9, wherein when executed by the one or more processors, the instructions further cause the computing device cluster to:
perform second billing on use of the cloud resource in a non-preferential manner based on the type attribute indicating the stable cloud resource; and
continue providing, based on the second billing, the cloud resource for the tenant when the tenant does not actively release the cloud resource and the idle resources are insufficient.

### Claim 14 (depends on 9)

The computing device cluster of claim 9, wherein the stable cloud resource comprises a pay-per-use billing, a yearly/monthly billing, or a reserved instance.

### Claim 15 (depends on 9)

The computing device cluster of claim 9, wherein the unstable cloud resource comprises a spot pricing billing or a spot block billing.

### Claim 16 (depends on 9)

The computing device cluster of claim 9, wherein the cloud resource comprises a computing resource, a network resource, or a storage resource.

### Claim 17

A method implemented by a cloud management platform, wherein the method comprises:
receiving, from a tenant via a cloud resource configuration interface, cloud resource configuration information comprising a specification and a type attribute of a to-be-created cloud resource, wherein the type attribute indicates an unstable cloud resource;
creating, based on the cloud resource configuration information, a cloud resource that has the specification and the type attribute and that is for the tenant;
receiving, from the tenant via a cloud resource conversion interface, a first cloud resource type conversion policy indicating to convert the type attribute from indicating the unstable cloud resource to indicating a stable cloud resource;
converting, based on the first cloud resource type conversion policy, the type attribute from indicating the unstable cloud resource to indicating the stable cloud resource;
performing first billing on use of the cloud resource in a non-preferential manner based on type attribute indicating the stable cloud resource; and
continuing providing, based on the first billing, the cloud resource for the tenant when the tenant does not actively release the cloud resource and idle resources are insufficient.

### Claim 18 (depends on 17)

The method of claim 17, further comprising:
receiving, from the tenant, via the cloud resource type conversion interface, and after converting the type attribute, a second cloud resource type conversion policy indicating to convert the type attribute from indicating the stable cloud resource to indicating the unstable cloud resource;
converting, based on the second cloud resource type conversion policy, the type attribute from indicating the stable cloud resource to indicating the unstable cloud resource;
performing second billing on use of the cloud resource in a preferential manner based on the type attribute indicating the unstable cloud resource; and
stopping providing, based on the second billing, the cloud resource for the tenant when the tenant does not actively release the cloud resource and the idle resources are insufficient.

### Claim 19 (depends on 18)

The method of claim 18, further comprising:
counting type attribute conversion times of the cloud resource; and
forbidding performing next type attribute conversion or charging the tenant for the next type attribute conversion when the type attribute conversion times exceed a threshold.

### Claim 20 (depends on 17)

The method of claim 17, further comprising:
calculating a type attribute conversion ratio of the cloud resource; and,
forbidding performing type attribute conversion or charging the tenant when the type attribute conversion ratio exceeds a threshold.
