CN116318944A - Metering data transmission method and system for cloud application, electronic equipment and storage medium - Google Patents

Metering data transmission method and system for cloud application, electronic equipment and storage medium Download PDF

Info

Publication number
CN116318944A
CN116318944A CN202310223093.3A CN202310223093A CN116318944A CN 116318944 A CN116318944 A CN 116318944A CN 202310223093 A CN202310223093 A CN 202310223093A CN 116318944 A CN116318944 A CN 116318944A
Authority
CN
China
Prior art keywords
metering data
cloud application
response information
metering
cloud
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202310223093.3A
Other languages
Chinese (zh)
Inventor
林子翘
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Alibaba China Co Ltd
Original Assignee
Alibaba China Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Alibaba China Co Ltd filed Critical Alibaba China Co Ltd
Priority to CN202310223093.3A priority Critical patent/CN116318944A/en
Publication of CN116318944A publication Critical patent/CN116318944A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
    • H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07F—COIN-FREED OR LIKE APPARATUS
    • G07F9/00—Details other than those peculiar to special kinds or types of apparatus
    • G07F9/002—Vending machines being part of a centrally controlled network of vending machines
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/02—Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
    • H04L63/0272—Virtual private networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0807—Network architectures or network communication protocols for network security for authentication of entities using tickets, e.g. Kerberos
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3247—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving digital signatures

Abstract

The application provides a metering data transmission method of cloud application, which is applied to a preset node in a preset network, wherein the preset network further comprises a selling platform, the preset node and the cloud application are in communication connection through the preset network, and the metering data transmission method comprises the following steps: receiving first metering data reported by the cloud application, wherein the first metering data is metering data of a cloud application layer; reporting the first metering data to the vending platform; receiving first response information returned by the vending platform; and sending the first response information to the cloud application.

Description

Metering data transmission method and system for cloud application, electronic equipment and storage medium
Technical Field
The present disclosure relates to the field of cloud computing, and in particular, to a method, a system, an electronic device, and a storage medium for transmitting metering data of a cloud application.
Background
In a scenario where a user uses a cloud application, how to accurately count and safely report usage for a usage-paid vending mode is a core issue of this vending mode. In the traditional mode, the access to metering software, metering and reporting data, matching a pricing model and the like are all completed by a provider of the cloud application, and the vending platform is only responsible for calculating the cost according to the resource usage amount and the pricing strategy reported by the cloud application. In this scenario, the following problems may exist: firstly, data are transmitted between the cloud application and the vending platform through the public network, so that the problem that the data cannot be reported due to disconnection of the public network may exist. For example, if a machine where the cloud application is located has no public network or is broken maliciously, the cloud application cannot report the data, thereby causing a missing report. Secondly, if the metering information is intercepted and tampered by artificial maliciousness in the reporting process, the metering information cannot be accurately reported, and safety risks exist; finally, if metering software is used, the early access may require software integration, product registration, authorized role creation, and other procedures, which are cumbersome.
Disclosure of Invention
In order to solve the technical problems, embodiments of the present application provide a method, a system, an electronic device, and a storage medium for transmitting metering data of a cloud application.
In a first aspect, an embodiment of the present application provides a method for transmitting metering data of a cloud application, which is applied to a predetermined node in a predetermined network, where the predetermined network further includes a vending platform, where the vending platform, the predetermined node, and the cloud application are communicatively connected through the predetermined network, and the method for transmitting metering data includes: receiving first metering data reported by the cloud application, wherein the first metering data is metering data of a cloud application layer; reporting the first metering data to the vending platform; receiving first response information returned by the vending platform; and sending the first response information to the cloud application.
In a second aspect, an embodiment of the present application provides a metering data transmission system for a cloud application, deployed at a predetermined node in a predetermined network, where the predetermined network further includes a vending platform, where the vending platform, the predetermined node, and the cloud application are communicatively connected through the predetermined network, the metering data transmission system includes: a processor; and a memory, coupled to the processor, for providing instructions to the processor to process the steps of: receiving first metering data reported by the cloud application, wherein the first metering data is metering data of a cloud application layer; reporting the first metering data to the vending platform; receiving first response information returned by the vending platform; and sending the first response information to the cloud application.
In a third aspect, an embodiment of the present application provides an electronic device, including a memory, a processor, and a computer program stored on the memory, where the processor implements the method of the first aspect when the computer program is executed.
In a fourth aspect, embodiments of the present application provide a computer readable storage medium, in which a computer program is stored, which when executed by a processor, implements the method according to the first aspect.
Compared with the prior art, the application has the following advantages: on the one hand, the cloud application can report the metering data to the internal node and the selling platform through the internal network, so that the problem of missing report caused by disconnection of the public network, which is possibly encountered when the cloud application uses the public network to report the metering data, can be effectively avoided; on the other hand, the internal nodes and the vending platform are also communicated through the internal network, so that the external interference is avoided, the metering data is prevented from being intercepted and tampered by artificial maliciousness in the reporting process, and the safety risk is reduced. Moreover, the metering data transmission method does not need to use metering software, so that complex processes of software integration, product registration, authorized role creation and the like when the metering software is used are avoided.
The foregoing description is merely an overview of the technical solutions of the present application, and in order to make the technical means of the present application more clearly understood, it is possible to implement the present application according to the content of the present specification, and in order to make the above and other objects, features and advantages of the present application more clearly understood, the following detailed description of the present application will be given.
Drawings
In the drawings, the same reference numerals refer to the same or similar parts or elements throughout the several views unless otherwise specified. The figures are not necessarily drawn to scale. It is appreciated that these drawings depict only some embodiments according to the application and are not to be considered limiting of its scope.
Fig. 1A is a flow chart of a metering data transmitting method according to a first embodiment of the present application;
fig. 1B is a schematic diagram of a metering data transmitting method according to a first embodiment of the present application;
fig. 2A is a flow chart of a metering data transmitting method according to a second embodiment of the present application;
fig. 2B is a schematic diagram of a metering data transmitting method according to a second embodiment of the present application;
fig. 3A is a flowchart of a metering data transmission method of a cloud application according to a third embodiment of the present application;
FIG. 3B is a schematic diagram of a metering data transmission method of a cloud application according to a third embodiment of the present application;
Fig. 4A is a flowchart of a metering data transmission method of a cloud application according to a fourth embodiment of the present application;
FIG. 4B is a schematic diagram of a metering data transmission method of a cloud application according to a fourth embodiment of the present application;
fig. 5A is a flowchart of a metering data transmission method of a cloud application according to a fifth embodiment of the present application;
FIG. 5B is a schematic diagram of a metering data transmission method of a cloud application according to a fifth embodiment of the present application;
FIG. 5C is a diagram illustrating specifications of cloud resources according to an embodiment of the present application; and
fig. 6 is a block diagram of an electronic device according to an embodiment of the present application.
Detailed Description
Hereinafter, only certain exemplary embodiments are briefly described. As will be recognized by those of skill in the pertinent art, the described embodiments may be modified in various different ways without departing from the spirit or scope of the present application. Accordingly, the drawings and description are to be regarded as illustrative in nature, and not as restrictive.
In order to facilitate understanding of the technical solutions of the embodiments of the present application, the following describes related technologies of the embodiments of the present application. The following related technologies may be optionally combined with the technical solutions of the embodiments of the present application, which all belong to the protection scope of the embodiments of the present application.
The application provides a metering data transmission method of cloud application, which is applied to a preset node in a preset network, wherein the preset network further comprises a selling platform, and the selling platform, the preset node and the cloud application are in communication connection through the preset network.
The cloud application refers to application software on a cloud server, such as relational database software, graph database software, ERP (Enterprise Resource Planning ) software, and other enterprise-level software running on the cloud server. A person skilled in the art may select a cloud application according to a specific application scenario and in combination with the technical principles of the present application.
The vending platform may be, for example, a pay-per-use cloud service platform that may provide services including computing, storage, database, analysis, artificial intelligence, security, etc. For example, the vending platform is a platform of cloud computing vendor a. On the platform of the cloud computing manufacturer a, the user may pay according to actual use conditions, for example, charging by hour, charging by usage amount, and the like. The vending platform may also provide various tools and services to help users manage and optimize resource usage, such as metering and monitoring tools, etc. The vending platform may also provide security functions such as encryption, identity access management, etc.
The predetermined network may be, for example, a network deployed within an enterprise, also known as an "intranet," for connecting various computers and servers within the enterprise. The internal network includes: a vending platform and an internal node (the "internal node" will be described below). In the internal network, the vending platform, the internal node, and the cloud application are communicatively connected via the predetermined network. For example, the respective computers and servers may access each other through VPN connection, for example. The cloud application may also be connected to the internal node through such an internal network, and report resource usage information (e.g., metering data, which will be described below) through the internal network, so that security and privacy of the data may be ensured, and meanwhile, problems of network delay and network jitter that may occur when the cloud service provider uses an external network may also be avoided. In addition, the internal node can acquire some key information of the cloud application, such as resource use condition, charging information and the like, from the internal network, and the information can be reported to the selling platform as metering data. The design of the internal network can improve the data security and privacy of enterprises, and can also report the service condition of cloud application more accurately.
The predetermined node may be, for example, an internal node in the internal network. The internal node may communicate with the cloud application and the vending platform via an internal network. For example, the internal node may receive metering data reported by a cloud application through an internal network, and report the metering data to the vending platform through the internal network.
The internal node may be, for example, a cloud host internal node. In a cloud host, internal nodes may be deployed inside a virtual machine, for example, to assist the virtual machine in metering and volume reporting. The internal node can also acquire the consumption information of the CPU, the memory, the disk and the like of the virtual machine, and convert the information into a standard metering data format for reporting.
The internal node may be, for example, a container internal node. For example, internal nodes may be deployed inside the container to assist the container in metering and reporting usage. The internal node can acquire the consumption information of the CPU, the memory, the network flow and the like of the container, and convert the information into a standard metering data format for reporting.
The internal node may be, for example, a database internal node. In a cloud database, internal nodes may be deployed inside database instances to assist the database in metering and volume reporting. The internal node can acquire the consumption information of the CPU, the memory, the disk, the network flow and the like of the database, and convert the information into a standard metering data format for reporting.
The internal nodes are described above for exemplary purposes. The internal nodes described in this application are not limited to the exemplary descriptions above. The specific implementation manner of the internal nodes may be different according to the type of the cloud application, the selling mode, the internal network, etc., but the internal nodes can complete the transfer of metering data and the information feedback between the cloud application and the selling platform. Those skilled in the art may select the internal node according to the actual situation, as long as the technical principles of the present application can be implemented.
Hereinafter, an example of using database software as a cloud application, an example of using a platform of a cloud computing vendor a as a vending platform, and a case of using database software running on a cloud server of the cloud computing vendor a as an exemplary application scenario by a user will be described.
The metering data transmission method of the cloud application provided in the present application will be exemplarily described with reference to fig. 1A and 1B. Fig. 1A is a flow chart of a metering data transmitting method 100 according to a first embodiment of the present application. Fig. 1B is a schematic diagram of a metering data transmitting method 100 according to a first embodiment of the present application.
As shown in fig. 1A, the metering data transmitting method 100 may include the following steps S101 to S104: in step S101, first metering data reported by a cloud application is received, where the first metering data is metering data of a cloud application layer; in step 102, reporting the first metering data to a vending platform; in step 103, receiving first response information returned by the vending platform; and, in step 104, sending the first response information to the cloud application.
The steps S101 to S104 will be described in detail with reference to specific embodiments.
In step S101, first metering data reported by the cloud application is received, where the first metering data is metering data at a cloud application level.
The first metering data may be, for example, metering data generated when a user uses a cloud application, and the metering data may be used to calculate a fee paid by the user for using the cloud application. In an embodiment, the first metering data may represent a length of time a user uses the cloud application. In an embodiment, the first metering data may represent how much traffic is consumed during use of the cloud application by the user. In an embodiment, the first metering data may represent a size of storage space used by a user during use of the cloud application. In an embodiment, the first metrology data may represent at least two of: the length of time the user uses the cloud application, how much traffic the user consumes during use of the cloud application, and the size of storage space used during use of the cloud application by the user. It will be appreciated by those skilled in the art that the foregoing examples of the first metering data are for illustrative purposes only and are not intended to limit the content of the first metering data, and those skilled in the art may selectively set the first metering data described in the present application according to actual needs, so long as the technical principles of the present application can be implemented.
It should be noted that in the context of cloud applications of the present application, metering data at the cloud application level may be referred to, or metering data at the cloud resource level may be referred to. As described above, the metering data at the cloud application level refers to metering data generated based on traffic consumed by a user or the cloud application and/or a used period of time and/or a used storage space, etc., during use of the cloud application by the user, which reflects dynamic data related to use of the cloud application. In an embodiment, the metering data at the cloud resource level may be, for example, cloud resource data purchased by a cloud application provider (e.g., database software provider) from a cloud service provider (e.g., cloud computing vendor a) (e.g., database software provider purchased 100G of cloud server resources from cloud computing vendor a). In another embodiment, the metering data at the cloud resource level may be, for example, cloud resource data purchased by a user (e.g., a user of database software) from a cloud service provider (e.g., cloud computing vendor a) (e.g., a user of database software purchased 100G of cloud server resources from cloud computing vendor a). The cloud resource data is static, but may also vary (also referred to in the art as "provisioning") with the frequency of usage, duration, etc. of the unused users.
The cloud application may report the first metering data to the internal node over an internal network (e.g., the "internal channel" shown in fig. 1B). The internal network has been described above and will not be described in detail here.
Next, step S102 is entered. In step S102, the first metering data is reported to the vending platform.
The internal node may report the first metering data to the vending platform via an internal network. For example, the internal node may report, through the internal network of the cloud computing vendor a, the time length data of the user using the database software as the first metering data to the vending platform of the cloud computing vendor a. The description of the internal nodes, the internal network, and how the internal nodes communicate with the cloud application has been described above, and will not be repeated here.
Next, the process advances to step S103. In step S103, first response information returned by the vending platform is received.
In an embodiment, the first response information may be response information of the vending platform to the reporting operation of the internal node. In other words, after the vending platform receives the first metering data reported by the internal node, the vending platform may send response information to the internal node, so as to inform the internal node whether the first metering data reported by the internal node has been correctly received by the vending platform. If the first metering data has been correctly received by the vending platform, the first response message is a positive acknowledgement; otherwise, if the first metering data is not correctly received by the vending platform, the first response information is a negative acknowledgement.
In an embodiment, the first response information may be whether the vending platform successfully receives the first metering data. After the vending platform receives the first metering data reported by the internal node, the vending platform may calculate fee information (i.e., billing information) that the user needs to pay to use the cloud application based on the first metering data. For example, taking the example of using database software (i.e., cloud application) on a cloud server of the cloud computing vendor a by the user as described above, the first response information returned to the internal node by the platform of the cloud computing vendor a (i.e., the vending platform) may include information of success (true) or failure (false).
The above description of the first response information is merely exemplary and is not intended to limit the first response information described in the present application. For example, the first response information may include both the response information described above and other response information. Those skilled in the art may select the content of the first response information according to the description of the embodiments of the present application, as long as the technical principles of the present application can be implemented.
Next, the process advances to step S104. In step S104, the first response information is sent to the cloud application.
The internal node may send the first response information from the vending platform to the cloud application. For example, the internal node may send the response information from the cloud computing vendor a platform to the database software through the internal network, so that the database software knows whether the metering data reported by itself is successful. .
As can be seen from the measurement data transmission method 100 described in connection with the specific embodiment, on one hand, the cloud application can report measurement data to the internal node and the vending platform through the internal network, so that the problems of missing report and missing report caused by network disconnection of the public network, which may be encountered when the cloud application uses the public network to report measurement data, can be effectively avoided; on the other hand, communication between the internal node and the selling platform is also carried out through the internal network, so that external interference is avoided, the metering data is prevented from being intercepted and tampered by artificial maliciously in the reporting process, and the safety risk is reduced. Moreover, the metering data transmission method 100 does not need to use metering software, so that complicated processes of software integration, product registration, authorized role creation and the like when the metering software is used are avoided.
A metering data transmission method according to a second embodiment of the present application will be described with reference to fig. 2A to 2B. Fig. 2A is a flow chart of a metering data transmitting method 200 according to a second embodiment of the present application. Fig. 2B is a schematic diagram of a metering data transmission method 200 according to a second embodiment of the present application. As shown in fig. 2A to 2B, the metering data transmitting method 200 includes the following steps S201 to S205: in step S201, first metering data reported by the cloud application is received, where the first metering data is metering data of a cloud application layer; step S202, reporting the first metering data to the vending platform; in step S203, first response information returned by the vending platform is received; in step S204, a digital signature or authentication information is added to the first response information, where the digital signature or the authentication information is used to ensure the authenticity of the first response information; in step S205, the first response information is sent to the cloud application.
It should be noted that step S201, step S202, step S203, and step S205 are the same as or similar to step S101, step S102, step S103, and step S104, respectively, described above with reference to fig. 1A. For simplicity of explanation, descriptions of step S201, step S202, step S203, and step S205 are omitted here. Those skilled in the art can understand these omitted steps in combination with the technical principle of the metering data transmission method 100 of the above first embodiment. Step S204 in the metering data transmitting method 200 will be described in detail below.
In step S204, a digital signature or authentication information is added to the first response information, where the digital signature or the authentication information is used to ensure the authenticity of the first response information.
Digital signatures are one method of signing information in electronic form (e.g., first response information). In an embodiment, signature data may be generated according to the content of the data unit of the first response information, and the signature data is added to the first response information, so as to implement the digital signature; the digital signature may also be implemented by encrypting the data units in the first response information. The additional data or the encryption enables a receiving party (e.g., a cloud application) to confirm the source of the first response information and the integrity of the data unit of the first response information and to provide protection for the data unit from tampering. Digital signatures may be implemented by either public key cryptography or private key cryptography. In an embodiment, the first response information may be digitally signed by a digital signature algorithm such as an RSA algorithm, a Fiat-Shamir algorithm, an elliptic curve digital signature algorithm, a finite automaton digital signature algorithm, or the like.
In another embodiment, authentication information may be added to the first response information. For example, the cloud application may issue an access token to the internal node in advance. Based on the method, the internal node can add the access token into the first response information sent to the cloud application so as to prove the true identity of the internal node, and the false internal node is prevented from sending false first response information to the cloud application.
It will be appreciated by those skilled in the art that the above description of digital signature and authentication information is merely exemplary, and these examples are not intended to limit the digital signature and authentication information described in the present application, and those skilled in the art may select digital signature and authentication information according to the actual application scenario, so long as the technical principles of the present application can be implemented.
After the cloud application receives the first response information, the first response information may be parsed to obtain the digital signature. Because the digital signature is generated according to the data unit of the first response information, the digital signature has a corresponding relation with the data unit, so that the cloud application can compare the digital signature obtained through analysis with the data unit of the first response information, and further judge whether the first response information is tampered. If the digital signature matches a data unit of the first response information, the cloud application may determine that the first response information has not been tampered with; if the digital signature does not match the data unit of the first response information, the cloud application may determine that there is a possibility of tampering with the first response information, in which case the cloud application may request the internal node to resend the first response information. The above description about the first response information being tampered, where the cloud application requests the internal node to resend the first response information is merely exemplary, and those skilled in the art may select a processing manner of the cloud application according to an actual application scenario, so long as the technical principles of the present application can be implemented.
As can be seen from the metering data transmission method 200 described above in connection with the specific embodiment, the communication between the internal node and the cloud application can be improved in security through a digital signature mechanism. As described above, the first response information may include the reply information and the billing information from the vending platform, and thus the digital signature mechanism may effectively verify whether the reply information and the billing information are tampered with. If the response information or the charging information is tampered, the cloud application can request the internal node to resend the first response information, so that the accuracy and the safety of information transfer between the cloud application and the internal node can be improved.
The following disadvantages also exist in the prior art: if the cloud is in error when the metering information is to be reported, the reporting is lost for a certain time, the cloud application needs to restart the reporting flow, and the code logic needs to be integrated by the cloud application, so that the burden of the cloud application is increased.
A metering data transmitting method according to a third embodiment of the present application will be exemplarily described with reference to fig. 3A to 3B. Fig. 3A is a flowchart of a metering data transmission method 300 of a cloud application according to a third embodiment of the present application. Fig. 3B is a schematic diagram of a metering data input method 300 of a cloud application according to a third embodiment of the present application. As shown in fig. 3A, the metering data transmitting method 300 may include the following steps S301 to S305: in step S301, first metering data reported by the cloud application is received, where the first metering data is metering data of a cloud application layer; step S302, reporting the first metering data to the vending platform; in step S303, receiving first response information returned by the vending platform; in step S304, determining whether a predetermined value in the first response information has an error, where if the predetermined value in the first response information has no error, proceeding to step S305, and sending the first response information to the cloud application; and if the preset value in the first response information has an error, re-executing the reporting operation of the first metering data and the receiving operation of the first response information until the preset value in the first response information has no error.
It should be noted that step S301, step S302, step S303, and step S305 correspond to step S101, step S102, step S103, and step S104, respectively, in the first embodiment described above with reference to fig. 1. For simplicity of explanation, descriptions of step S301, step S302, step S303, and step S305 are omitted here. Those skilled in the art can understand these omitted steps in combination with the technical principle of the metering data transmission method 100 of the above first embodiment. Step S304 in the metering data transmitting method 300 will be described in detail below.
In step S304, it is determined whether there is an error in a predetermined value in the first response information.
In an embodiment, the predetermined value in the first response information may be a predetermined field (e.g., true or false) in the reply information of the vending platform. The predetermined field may indicate whether the first metering data reported by the internal node has been properly received by the vending platform. For example, true indicates that the first metering data has been correctly received by the vending platform; false indicates that the first metering data was not properly received by the vending platform. If the predetermined value is true, the metering data transmitting method 300 proceeds to step S305; if the predetermined value is false, the internal node repeatedly executes step S302, step S303 and step S304, in other words, the internal node reports the first metering data to the vending platform again, and the vending platform provides the first response information to the internal node, and the internal node determines whether the predetermined value in the first response information is true again. Step S302, step S303, and step S304 may be repeatedly performed until the internal node determines that the predetermined value in the first response information is true (i.e., the first response information has been correctly received by the vending platform). Executing the retry mechanism described above by the internal node applies to the following scenarios: network jitter, network delay, network timeout or errors caused by the vending platform itself during the reporting process. The retry mechanism described above is not applicable if the error originates from the cause of the cloud application itself.
In an embodiment, the predetermined value in the first response information may be a predetermined field in charging information provided by the vending platform. The predetermined field may represent, for example, a charging type. There is a correspondence between the charging type and the metering data (e.g., the first metering data described above). For example, if the metering data is the length of time used by the user, the charging type is in units of the length of time; if the metering data is the traffic consumed by the user, the charging type is in units of traffic size. After receiving the first response information sent by the vending platform, the internal node can analyze the first response information so as to obtain a preset field of charging information in the first response information, and compare the charging type indicated by the preset field with the first metering data uploaded by the internal node before so as to judge whether the charging type corresponds to the first metering data. If the charging type corresponds to the first metering data, there is no error in the predetermined value in the first response information, and the metering data transmission method 300 proceeds to step S305; if the charging type does not correspond to the first metering data, the internal node repeatedly executes step S302, step S303 and step S304, in other words, the internal node reports the first metering data to the vending platform again, the vending platform provides first response information for the internal node, and the internal node determines whether the predetermined value in the first response information has an error again. Step S302, step S303, and step S304 may be repeatedly performed until the internal node determines that the predetermined value in the first response information has no error.
As can be seen from the above description of the method 300 for transmitting metering data according to the specific embodiment, the internal node has a retry mechanism, and if the metering data (for example, the first metering data) is wrong in the reporting process, and the vending platform does not correctly receive the metering data, the internal node can continuously retry until the vending platform correctly receives the metering data, without the cloud application having to perform the reporting operation again. Therefore, the stability of the reported metering data can be improved, and the calculation overhead of cloud application is reduced.
The prior art also has the following disadvantages: the cloud application has great difficulty in acquiring the usage information (such as the number of virtual CPUs, the total storage amount and the like) of the cloud resource layer, and even cannot acquire the usage information.
A metering data transmitting method according to a fourth embodiment of the present application will be exemplarily described with reference to fig. 4A to 4B. Fig. 4A is a flowchart of a metering data transmission method 400 of a cloud application according to a fourth embodiment of the present application. Fig. 4B is a schematic diagram of a metering data input method 400 of a cloud application according to a fourth embodiment of the present application. As shown in fig. 4A, the metering data transmitting method 400 may include steps S401 to S405: in step S401, first metering data reported by the cloud application is received, where the first metering data is metering data of a cloud application layer; in step S402, receiving a request from the cloud application for second metering data, the second metering data being metering data of a cloud resource level; in step S403, the first metering data is reported to the vending platform; in step S404, first response information returned by the vending platform is received; and in step S405, the first response information and the second metering data are respectively sent to the cloud application.
It should be noted that the first response information transmission operations in step S401, step S403, step S404, and step S405 correspond to step S101, step S102, step S103, and step S104, respectively, in the first embodiment described above with reference to fig. 1. For simplicity of explanation, the description of the first response information transmitting operation in step S401, step S403, step S404, and step S405 is omitted here. Those skilled in the art can understand these omitted steps in combination with the technical principle of the metering data transmission method 100 of the above first embodiment. The second metering data transmitting operation in step S402 and step S405 in the metering data transmitting method 400 will be described in detail below.
In step S402, a request for second metering data from the cloud application is received, the second metering data being metering data of a cloud resource level.
The second metering data may be, for example, cloud resource-level metering data. The metering data of the cloud resource layer has been described above, and this is not repeated here. In the context of a cloud application, the cloud application may not be aware of the cloud resource size purchased by the cloud application provider, and thus the cloud application may request the internal node to inform it of the cloud resource size. For example, the cloud application may send a request to the internal node requesting the internal node to send cloud resource-level metering data to the cloud application. The internal node can learn the size of the cloud resources purchased by the cloud application provider through the internal network and provide the cloud application with the cloud resource-level metering data.
It will be appreciated by those skilled in the art that the above description of the second metrology data is merely exemplary and is not intended to limit the second metrology data described herein, and that the skilled artisan may choose the second metrology data as may be practical, so long as the technical principles of the present application can be implemented. The request for second metering data may be sent over an internal network.
In step S405, the first response information and the second metering data are respectively sent to the cloud application.
As described above, the second metering data may be cloud resource-level metering data. The second metering data may be sent to the cloud application over the internal network. The second metering data is transmitted in the same or similar manner as the first response information described above. For example, the internal node may incorporate a digital signature into the second metering data, which the cloud application may verify in order to determine whether the second metering data has been tampered with.
As can be seen from the measurement data transmission method 400 described in connection with the specific embodiment, the cloud application can obtain measurement data of the cloud resource layer through the internal node, so that the problem that the cloud application cannot know the consumption information of the cloud resource is solved.
In an embodiment, after receiving the request for the second metering data, the metering data transmission method further comprises: reporting the second metering data to the vending platform; and receiving second response information returned by the vending platform. The reporting manner of the second measurement data is the same as or similar to the reporting manner of the first measurement data described above, and will not be described herein.
In an embodiment, the second response information may be response information of the vending platform to the reporting operation of the second metering data. In another embodiment, the second response information may be billing information determined by the vending platform based on the second metering data. Embodiments of the response information and the charging information may refer to the embodiments described above in connection with fig. 1A, and will not be described herein.
The prior art also has the following disadvantages: for different cloud resource specifications, different pricing standards may exist for the cloud application, however, because the cloud application and the vending platform do not belong to the same provider, the cloud application cannot generally learn specific vending information of the vending platform, in this case, the cloud application generally needs to record multiple charging models in advance, if the charging models are modified due to service changes, codes need to be modified in the cloud application, and thus the flexibility of use of the cloud application is poor.
A metering data transmitting method according to a fifth embodiment of the present application will be exemplarily described with reference to fig. 5A to 5B. Fig. 5A is a flowchart of a metering data transmission method 500 of a cloud application according to a fifth embodiment of the present application. Fig. 5B is a schematic diagram of a metering data input method 500 of a cloud application according to a fifth embodiment of the present application. As shown in fig. 5A, the metering data transmitting method 500 may include steps S501 to S506: in step S501, first metering data reported by the cloud application is received, where the first metering data is metering data of a cloud application layer; in step S502, a vending specification and a metering dimension of an application layer of the cloud application are determined according to the first metering data; in step S503, determining a pricing mapping item of an application layer of the cloud application according to the determined selling specification and metering dimension of the application layer; in step S504, the determined pricing mapping item of the application layer and the first metering data are respectively reported to the vending platform; in step S505, first response information returned by the vending platform is received; and, in step S506, transmitting the first response information to the cloud application.
It should be noted that the metering data transmitting method 500 differs from the metering data transmitting method 100 described above with reference to fig. 1A and 1B in the transmitting operation of the pricing map items in step S502, step S503, and step S504. Other steps and operations in the metering data transmission method 500 are the same as or similar to corresponding steps and operations of the metering data transmission method 100, and these same or similar steps and operations are omitted here for simplicity of explanation. Those skilled in the art can understand these omitted steps and operations in combination with the technical principle of the metering data transmission method 100 of the above first embodiment. The transmission operation of the pricing map items in step S502, step S503, and step S504 in the metering data transmitting method 500 will be described in detail below.
In step S502, a vending specification and a metering dimension of an application layer of the cloud application are determined according to the first metering data.
The vending specification may correspond to the cloud resource level metering data described above. For example, the vending specification may be a specification of cloud resources purchased by a cloud application provider (e.g., database software provider) from a cloud service provider (e.g., cloud computing vendor a), including the number of cores of the CPU, the number of servers, the capacity of the memory, the traffic size, and the like. Fig. 5C is a diagram illustrating specifications of cloud resources according to an embodiment of the present application. As shown in fig. 5C, the specification of the cloud resource, including the number of database servers, is that in the example shown in fig. 5C, 2 database servers were purchased by the cloud application provider.
The metering dimension may correspond to the metering data at the cloud application level described above. The metering dimension may be at least one of a time dimension, a bandwidth dimension, and a traffic dimension. Metering dimensions may also include storage dimensions, virtual CPU cores, virtual memory numbers, number of Daily Activities (DAUs), number of users, and the like. For example, the time dimension may correspond to a "usage duration", i.e., a length of time a user uses the cloud application (e.g., a length of time a user uses when using database software); the traffic dimension may be "consumed traffic" corresponding to the amount of traffic consumed by the user during use of the cloud application (e.g., the amount of traffic consumed by the user while using database software). It should be understood by those skilled in the art that the above description of the vending specification and the metering dimension is only exemplary, and is not intended to limit the vending specification and the metering dimension described in the present application, and those skilled in the art may selectively set according to the actual situation, so long as the technical principles of the present application can be implemented.
As can be seen from the description above, the vending specification can exist in a variety of specifications, as can the metering dimension. The selling specification and the metering dimension have a mapping relation. The mapping relation may be stored in the internal node in advance in the form of a mapping relation table. The internal node may also obtain the mapping table from the internal network. Table 1 below shows one example of a mapping relationship table between sales specifications and metering dimensions.
Figure BDA0004120923220000111
TABLE 1
After the internal node receives the first metering data reported by the cloud application, the selling specification and the metering data can be determined according to the first metering data. For example, if the first metering data represents a length of time that the user uses the cloud application, the internal node may determine that the metering dimension is the "time dimension" in table 1; if the first metering data indicates that the cloud application uses 1 database server, the internal node may determine that the vending specification is "vending specification a (1 database server)".
In step S503, a pricing mapping term for the application layer of the cloud application is determined according to the determined vending specification and metering dimension for the application layer.
In an embodiment, the internal node may determine the corresponding pricing map item from the map table based on the vending specification and metering dimension. For example, using Table 1 above as an example, if the internal node determines that the vending specification is "vending specification A (1 database server)", and determines that the metering dimension is "time dimension", the internal node may determine that the pricing map item is "1 yuan/1 minute" from Table 1.
In step S504, the determined pricing mapping terms of the application layer and the first metering data are respectively reported to the vending platform.
The internal node may report the pricing map item and the first metering data to the vending platform, respectively, and the vending platform calculates a price to be paid by the user according to the pricing map item and the first metering data. For example, the pricing map item is "1 yuan/1 minute", the first metering data is "10 minutes", and the price the user needs to pay is "10 yuan".
The internal node may report the pricing map item over an internal network. The reporting process of the pricing map item is the same as or similar to the reporting process of the first metering data, for example, if an error occurs in the reporting process of the pricing map item, the vending platform may also instruct the internal node to re-upload the pricing map item by returning the first response information, and the process is similar to steps S302 to S304 shown in fig. 3A, and will not be repeated here.
As can be seen from the metering data transmission method 500 described above in connection with the specific embodiment, the internal node can determine the pricing mapping term through the mapping relationship between the selling price and the metering dimension, so the cloud application does not need to record various charging models in advance. And if the mapping relation between the selling price and the metering dimension is changed, only the mapping relation table on the internal node is required to be modified, and the code of the cloud application is not required to be modified, so that the use flexibility of the cloud application is improved.
The embodiment of the application also provides a metering data transmission system of a cloud application, which is deployed at a preset node in a preset network, wherein the preset network further comprises a selling platform, the preset node and the cloud application are in communication connection through the preset network, and the metering data transmission system comprises: a processor; and a memory, coupled to the processor, for providing instructions to the processor to process the steps of: receiving first metering data reported by the cloud application, wherein the first metering data is metering data of a cloud application layer; reporting the first metering data to the vending platform; receiving first response information returned by the vending platform; and sending the first response information to the cloud application.
Corresponding to the application scene and the method of the method provided by the embodiment of the application, the embodiment of the application also provides electronic equipment. Such as the internal node described above. For usage scenarios (e.g., cloud applications, vending platforms, internal networks, etc.) of the electronic device, reference may be made to the embodiments described above, which are not repeated herein.
Fig. 6 is a block diagram of an electronic device 600 according to an embodiment of the present application. As shown in fig. 6, the electronic device 600 comprises a memory 601, a processor 602, and a communication interface 603. The processor 602 configures the class to perform the following operations via the communication interface 603: receiving first metering data reported by a cloud application, wherein the first metering data is metering data of a cloud application layer; reporting the first metering data to a vending platform; receiving first response information returned by the vending platform; and sending the first response information to the cloud application.
For specific embodiments of the electronic device 600, reference may be made to the respective embodiments of fig. 1A-1B, fig. 2A-2B, fig. 3A-3B, fig. 4A-4B, and fig. 5A-5B, which are not described herein.
The processor 602, when executing the computer program, implements the methods in the above embodiments. The number of memories 601 and processors 602 may be one or more.
If the memory 601, the processor 602, and the communication interface 603 are implemented independently, the memory 601, the processor 602, and the communication interface 603 may be connected to each other and perform communication with each other through buses. The bus may be an industry standard architecture (Industry Standard Architecture, ISA) bus, an external device interconnect (Peripheral Component Interconnect, PCI) bus, or an extended industry standard architecture (Extended Industry Standard Architecture, EISA) bus, among others. The bus may be classified as an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in fig. 6, but not only one bus or one type of bus.
Alternatively, in a specific implementation, if the memory 601, the processor 602, and the communication interface 603 are integrated on a chip, the memory 601, the processor 602, and the communication interface 603 may perform communication with each other through internal interfaces.
The present embodiments provide a computer-readable storage medium storing a computer program that, when executed by a processor, implements the methods provided in the embodiments of the present application.
The embodiment of the application also provides a chip, which comprises a processor and is used for calling the instructions stored in the memory from the memory and running the instructions stored in the memory, so that the communication device provided with the chip executes the method provided by the embodiment of the application.
The embodiment of the application also provides a chip, which comprises: the input interface, the output interface, the processor and the memory are connected through an internal connection path, the processor is used for executing codes in the memory, and when the codes are executed, the processor is used for executing the method provided by the application embodiment.
It should be appreciated that the processor may be a central processing unit (Central Processing Unit, CPU), but may also be other general purpose processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), field programmable gate arrays (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or any conventional processor or the like. It is noted that the processor may be a processor supporting an advanced reduced instruction set machine (Advanced RISC Machines, ARM) architecture.
Further alternatively, the memory may include a read-only memory and a random access memory. The memory may be volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile Memory may include Read-Only Memory (ROM), programmable ROM (PROM), erasable Programmable ROM (EPROM), electrically Erasable EPROM (EEPROM), or flash Memory, among others. Volatile memory can include random access memory (Random Access Memory, RAM), which acts as external cache memory. By way of example, and not limitation, many forms of RAM are available. For example, static RAM (SRAM), dynamic RAM (Dynamic Random Access Memory, DRAM), synchronous DRAM (SDRAM), double Data Rate Synchronous DRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), and Direct RAM (DR RAM).
In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions in accordance with the present application are produced in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. Computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another.
In the description of the present specification, a description referring to terms "one embodiment," "some embodiments," "examples," "specific examples," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the present application. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, the different embodiments or examples described in this specification and the features of the different embodiments or examples may be combined and combined by those skilled in the art without contradiction.
Furthermore, the terms "first," "second," and the like, are used for descriptive purposes only and are not to be construed as indicating or implying a relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include at least one such feature. In the description of the present application, the meaning of "a plurality" is two or more, unless explicitly defined otherwise.
Any process or method described in flow charts or otherwise herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process. And the scope of the preferred embodiments of the present application includes additional implementations in which functions may be performed in a substantially simultaneous manner or in an opposite order from that shown or discussed, including in accordance with the functions that are involved.
Logic and/or steps described in the flowcharts or otherwise described herein, e.g., may be considered a ordered listing of executable instructions for implementing logical functions, can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions.
It is to be understood that portions of the present application may be implemented in hardware, software, firmware, or a combination thereof. In the above-described embodiments, the various steps or methods may be implemented in software or firmware stored in a memory and executed by a suitable instruction execution system. All or part of the steps of the methods of the embodiments described above may be performed by a program that, when executed, comprises one or a combination of the steps of the method embodiments, instructs the associated hardware to perform the method.
In addition, each functional unit in each embodiment of the present application may be integrated in one processing module, or each unit may exist alone physically, or two or more units may be integrated in one module. The integrated modules may be implemented in hardware or in software functional modules. The integrated modules described above, if implemented in the form of software functional modules and sold or used as a stand-alone product, may also be stored in a computer-readable storage medium. The storage medium may be a read-only memory, a magnetic or optical disk, or the like.
The foregoing is merely exemplary embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think of various changes or substitutions within the technical scope of the present application, which should be covered in the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (11)

1. A metering data transmission method of a cloud application, applied to a predetermined node in a predetermined network, the predetermined network further comprising a vending platform, wherein the vending platform, the predetermined node and the cloud application are in communication connection through the predetermined network, the metering data transmission method comprising:
receiving first metering data reported by the cloud application, wherein the first metering data is metering data of a cloud application layer;
reporting the first metering data to the vending platform;
receiving first response information returned by the vending platform; and
and sending the first response information to the cloud application.
2. The metering data transmitting method according to claim 1, wherein before the first response information is sent to the cloud application, the metering data transmitting method further comprises:
And adding a digital signature or authentication information into the first response information, wherein the digital signature or the authentication information is used for ensuring the authenticity of the first response information.
3. The metering data transmission method according to claim 1, wherein after receiving the first response information returned by the vending platform and before sending the first response information to the cloud application, the metering data transmission method further comprises:
determining whether a predetermined value in the first response information is erroneous, wherein,
if the preset value in the first response information is not wrong, the first response information is sent to the cloud application; and
and if the preset value in the first response information has an error, re-executing the reporting operation of the first metering data and the receiving operation of the first response information until the preset value in the first response information has no error.
4. The metering data transmission method according to claim 1, further comprising:
receiving a request from the cloud application for second metering data, the second metering data being cloud resource-level metering data; and
And returning the second metering data to the cloud application.
5. The metering data transmission method according to claim 4, after receiving the request for the second metering data, further comprising:
reporting the second metering data to the vending platform;
and receiving second response information returned by the vending platform.
6. The metering data transmission method as claimed in claim 1, wherein the predetermined node is preconfigured with a pricing map comprising a plurality of pricing map items, each pricing map item of the plurality of pricing map items corresponding to a mapping relationship between a vending specification and a metering dimension of the cloud application, wherein,
after receiving the first metering data reported by the cloud application, the metering data transmission method further comprises the following steps:
determining a selling specification and a metering dimension of an application layer of the cloud application according to the first metering data;
determining pricing mapping items of the application level of the cloud application according to the determined selling specification and metering dimension of the application level; and
and reporting the determined pricing mapping items of the application layer to the vending platform.
7. The metering data transmission method according to claim 6, wherein after receiving the first metering data reported by the cloud application, the metering data transmission method further comprises:
determining selling specifications and metering dimensions of the resource layer of the cloud application according to the second metering data;
determining a pricing mapping item of the resource level of the cloud application according to the determined selling specification and metering dimension of the resource level; and
and reporting the determined pricing mapping item of the resource layer to the selling platform.
8. The metering data transmission method of claim 6, wherein the metering dimensions comprise at least one of the following dimensions: time dimension, bandwidth dimension, traffic dimension.
9. A metering data transmission system for a cloud application, deployed at a predetermined node in a predetermined network, the predetermined network further comprising a vending platform, wherein the vending platform, the predetermined node, and the cloud application are communicatively connected through the predetermined network, the metering data transmission system comprising:
a processor; and a memory, coupled to the processor, for providing instructions to the processor to process the steps of:
Receiving first metering data reported by the cloud application, wherein the first metering data is metering data of a cloud application layer;
reporting the first metering data to the vending platform;
receiving first response information returned by the vending platform; and
and sending the first response information to the cloud application.
10. An electronic device comprising a memory, a processor and a computer program stored on the memory, the processor implementing the method of any one of claims 1-8 when the computer program is executed.
11. A computer readable storage medium having stored therein a computer program which, when executed by a processor, implements the method of any of claims 1-8.
CN202310223093.3A 2023-03-03 2023-03-03 Metering data transmission method and system for cloud application, electronic equipment and storage medium Pending CN116318944A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310223093.3A CN116318944A (en) 2023-03-03 2023-03-03 Metering data transmission method and system for cloud application, electronic equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310223093.3A CN116318944A (en) 2023-03-03 2023-03-03 Metering data transmission method and system for cloud application, electronic equipment and storage medium

Publications (1)

Publication Number Publication Date
CN116318944A true CN116318944A (en) 2023-06-23

Family

ID=86826766

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310223093.3A Pending CN116318944A (en) 2023-03-03 2023-03-03 Metering data transmission method and system for cloud application, electronic equipment and storage medium

Country Status (1)

Country Link
CN (1) CN116318944A (en)

Similar Documents

Publication Publication Date Title
CN111213340B (en) Selecting attestation delegation for cryptographic functions and making it secure
CN111163129A (en) Resource processing method and device based on cross-link network
CN104869175A (en) Cross-platform account resource sharing implementation method, device and system
JP2013522795A (en) System and method for remote maintenance of client systems in electronic networks using software testing with virtual machines
CN109523045B (en) Method and equipment for providing travel service
WO2018023936A1 (en) Method and device for implementing sharing of wireless access point
CN107360261A (en) A kind of HTTP request processing method, device and electronic equipment
CN114281573A (en) Workflow data interaction method and device, electronic device and readable storage medium
CN109509099A (en) Data trade method and device calculates equipment, storage medium
CN111355684A (en) Internet of things data transmission method, device and system, electronic equipment and medium
CN112036878A (en) Data processing method and device
CN110602234B (en) Block chain network node management method, device, equipment and storage medium
CN115310145A (en) Privacy computing system, method, device, equipment and medium
CN109600254B (en) Method for generating full-link log and related system
CN116318944A (en) Metering data transmission method and system for cloud application, electronic equipment and storage medium
CN111586157B (en) Information processing method, device and equipment
CN111131397B (en) Application management method and system, gateway platform, server and storage medium
CN116095074A (en) Resource allocation method, device, related equipment and storage medium
CN110717752B (en) Electronic resource processing method, device, server and readable storage medium
CN113987598A (en) Block migration method and device
CN109325858B (en) Resource flow transaction method and device, computer equipment and computer readable medium
CN110585717A (en) Information processing method and device
CN115174232B (en) Client installation method, host information processing method and operation and maintenance safety system
CN112862466A (en) Resource transfer method, account settling terminal and server node
CN110912987B (en) Information processing method and related equipment

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination