Resource scale management

Abstract

Embodiments of the present specification disclose a resource scale management method and apparatus, an electronic device, and a storage medium. The resource scale management method comprises: on the basis of a first node detecting a management instruction, broadcasting, by the first node, target scale information corresponding to the management instruction to at least one second node; then, each time the second node receives a resource management application, processing a target management resource on the basis of a smart contract, the smart contract being used for updating current scale information on the basis of the target management resource when the target management resource matches the current scale information; and finally, on the basis of a processing result of the smart contract, determining feedback information and a feedback target, and sending the feedback information to the feedback target.

Description

Resource scale management Technical Field

[0001] The embodiments of this specification belong to the field of data processing technology, and in particular, relate to methods, devices, electronic devices, and storage media for resource scale management. Background Art

[0002] With the advancement of society and economic development, more and more people are choosing to use their own resources for fundraising, material donations, resource auctions, and other resource management activities. Resource management activities generally have a set resource scale. When the managed resources reach the resource scale, no new resources will be managed.

[0003] Currently, due to a lack of information exchange between different resource management channel organizations, the current scale of resource management activities cannot be accurately determined, causing the actual scale to exceed the preset target scale. In this case, the effective resources managed on the last day are proportionally allocated, and the excess resources are then refunded. This results in users actually investing less resources than they expected, which is not in line with expectations. Not only does this poorly experience the user experience, but the failed management resources cannot be refunded until the management results of the management activity are confirmed, increasing resource costs. Summary of the Invention

[0004] The embodiments of this specification provide a resource scale management method, device, electronic device, and storage medium, and the technical solutions thereof are as follows.

[0005] In a first aspect, an embodiment of the present specification provides a resource scale management method, including: detecting a management instruction based on a first node, broadcasting target scale information corresponding to the management instruction to at least one second node through the first node; whenever the second node receives a resource management application, processing the target management resource based on a smart contract, the smart contract is used to update the current scale information based on the target management resource when the target management resource matches the current scale information; determining feedback information and a feedback object based on the processing result of the smart contract, and sending the feedback information to the feedback object.

[0006] In a second aspect, an embodiment of the present specification provides a resource scale management device, comprising: a detection module for detecting a management instruction based on a first node, and broadcasting target scale information corresponding to the management instruction to at least one second node through the first node; a processing module for processing a target management resource based on a smart contract whenever the second node receives a resource management application, and the smart contract is used to update the current scale information based on the target management resource when the target management resource matches the current scale information; a sending module for determining feedback information and a feedback object based on the processing result of the smart contract, and sending the feedback information to the feedback object.

[0007] On the third aspect, the embodiments of this specification also provide an electronic device, which may include: a processor and a memory; wherein the memory stores a computer program, and the computer program is suitable for being loaded by the processor and executing the above-mentioned blockchain-based resource mobilization scale control method steps.

[0008] In a fourth aspect, an embodiment of this specification provides a computer storage medium, which stores multiple instructions, and the instructions are suitable for being loaded by a processor and executing the above-mentioned blockchain-based resource fundraising scale control method steps.

[0009] The beneficial effects brought about by the technical solutions provided by some embodiments of this specification include at least the following: In one or more embodiments of this specification, the management instruction is detected by the first node, and the target management resource is broadcast in the node network. When the second node receives the resource management application sent by the user, it will judge the target management resource through the smart contract, determine whether the current scale information can match the target management resource, and perform different processing according to the matching situation. Finally, the node network will feedback the application failure to the user based on the processing result or broadcast the latest current scale information to other nodes. Through the above process, decentralized data synchronization of current scale information is achieved, and the resource scale can be accurately controlled, which brings a better experience to users. In addition, the user's resources will not be managed if the application fails, reducing resource costs. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] In order to more clearly illustrate the technical solutions in the embodiments of this specification, the following briefly introduces the drawings required for use in the embodiments. Obviously, the drawings described below are only some embodiments of this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0011] FIG1 is a schematic diagram of a system architecture of a resource scale management method provided in an embodiment of this specification.

[0012] FIG2 is a flow chart of a resource scale management method provided in an embodiment of this specification.

[0013] FIG3 is a schematic diagram showing the principle of the resource recruitment process provided in an embodiment of this specification.

[0014] FIG4 is a flowchart of another resource scale management method provided in an embodiment of this specification.

[0015] FIG5 is a schematic diagram of the structure of a resource scale management device provided in an embodiment of this specification.

[0016] FIG6 is a schematic structural diagram of an electronic device provided in an embodiment of this specification. DETAILED DESCRIPTION

[0017] The technical solutions in the embodiments of this specification will be described clearly and completely below in conjunction with the drawings in the embodiments of this specification.

[0018] Throughout this specification, the claims, and the accompanying drawings, the terms "first," "second," "third," and the like are used to distinguish between different items, not to describe a particular order. Furthermore, the terms "including," "having," and any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or apparatus comprising a series of steps or elements is not limited to the listed steps or elements but may optionally include steps or elements not listed, or may include other steps or elements inherent to the process, method, product, or apparatus.

[0019] The following description provides examples and does not limit the scope, applicability, or examples set forth in the claims. Changes may be made to the functions and arrangements of the elements described without departing from the scope of this specification. Various examples may appropriately omit, replace, or add various processes or components. For example, the described methods may be performed in an order different from the order described, and various steps may be added, omitted, or combined. Furthermore, features described with respect to some examples may be combined in other examples.

[0020] First, some of the embodiments of the present application will be explained below to facilitate understanding by those skilled in the art.

[0021] Blockchain: A decentralized, distributed database technology that uses cryptography and distributed consensus algorithms to link data in blocks, creating an immutable, transparent, and traceable data record system. Blockchain does not rely on a centralized authority or data storage center. Instead, data is maintained and managed by multiple nodes in the network, eliminating single points of failure and improving the system's resilience and reliability.

[0022] Blockchains are generally categorized into three types: public, private, and consortium. Furthermore, combinations of these types are possible, such as private + consortium, or consortium + public.

[0023] Public blockchains are the most decentralized. Participants in a public blockchain (also known as nodes in the blockchain) can access data records, participate in transactions, and maintain accounting rights. Furthermore, each node can freely join or leave the network and perform related operations.

[0024] In contrast, a private blockchain has write permissions controlled by a specific organization or institution, while data read permissions are regulated by that organization. Simply put, a private blockchain can be a weakly centralized system with strict node restrictions and a small number of nodes. This type of blockchain is more suitable for internal use within a specific organization.

[0025] Consortium blockchains are a cross between public and private blockchains, enabling partial decentralization. Each node in a consortium chain typically has a corresponding entity or organization; nodes are authorized to join the network and form a stakeholder alliance to jointly maintain the blockchain's operations.

[0026] Based on the basic characteristics of blockchain, a blockchain is typically composed of several blocks. Each of these blocks is timestamped to indicate the moment of its creation. All blocks strictly follow the timestamps recorded in the blocks, forming a temporally ordered data chain.

[0027] Real data generated in the physical world can be constructed into a standard transaction format supported by the blockchain, and then published to the blockchain. The node devices in the blockchain will conduct consensus processing on the received transactions. After reaching a consensus, the node devices in the blockchain that serve as accounting nodes will package the transactions into blocks and store them persistently in the blockchain.

[0028] Among them, the consensus algorithms supported in the blockchain may include: the first type of consensus algorithm, that is, the consensus algorithm in which node devices need to compete for the accounting right of each accounting cycle; for example, Proof of Work (POW), Proof of Stake (POS), Delegated Proof of Stake (DPOS) and other consensus algorithms; the second type of consensus algorithm, that is, the consensus algorithm in which accounting nodes are elected in advance for each accounting cycle (without the need to compete for accounting rights); for example, Practical Byzantine Fault Tolerance (PBFT) and other consensus algorithms.

[0029] Please refer to FIG1 , which shows a schematic diagram of the system architecture of a resource scale management method provided in an embodiment of this specification.

[0030] As shown in FIG1 , the system architecture of the resource scale management method may include at least a first terminal 100 , a server 200 , a second terminal 300 and a network.

[0031] The first terminal 100 and the second terminal 300 include, but are not limited to, electronic devices such as smartphones, desktop computers, tablet computers, laptops, smart speakers, digital assistants, and smart wearable devices. They may also be software running on the above electronic devices, such as applications. Optionally, the operating system running on the electronic device may include, but is not limited to, Android, iOS, Linux, Windows, etc. Optionally, the first terminal 100 may provide resource scale management services to the resource manager. Based on the manager's operating instructions, the first terminal 100 may access the SDK to send target scale information to the blockchain composed of the server 200 and receive feedback information sent back by the server 200. Based on the applicant's operating instructions, the second terminal 300 may access the SDK to send the target management resource to be applied for to the node network composed of the server 200 and receive feedback information sent back by the server 200.

[0032] The node network formed by the server 200 can provide background services for the terminal 100, judge the current scale information and target management resources based on the smart contract to determine whether the target management resources can match the current scale information, and send corresponding feedback information to the first terminal 100 and / or the second terminal 300 based on the processing results. Specifically, the server 200 can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms.

[0033] The network is used to provide a medium for communication links between the first terminal 100 and the server 200, between the second terminal 300 and the server 200, and between servers 200 and servers 200. The network can include various connection types, such as wired or wireless communication links or fiber optic cables.

[0034] In addition, it should be noted that what is shown in FIG1 is only a system provided by the present disclosure. In practical applications, other systems may also be included, for example, more terminals may be included.

[0035] In the embodiments of this specification, the first terminal 100, the second terminal 300 and the server 200 may be directly or indirectly connected via wired or wireless communication, which is not limited in this disclosure.

[0036] Next, please refer to Figure 2, which shows an overall flow chart of a resource scale management method provided in an embodiment of this specification. The resource scale management method can be used in the server corresponding to the full node in the node network that is responsible for tracking and maintaining the overall data processing process performed by the remaining nodes.

[0037] As shown in FIG2 , the resource scale management method may include at least the following steps.

[0038] Step 201: Based on a management instruction detected by a first node, target scale information corresponding to the management instruction is broadcast to at least one second node through the first node.

[0039] Specifically, the first node may be a node used by a manager who wants to obtain a specified number of resources and perform resource management activities on the resources, and the second node may be a node used by an applicant who wants to hand over certain resources of his own to the manager for management. The first node and the second node can exchange data information in the node network. When the manager wants to perform a new resource management activity, the server will detect the management instruction corresponding to the resource management activity through the first node, and determine the target scale information corresponding to the management instruction. The target scale information may be the total scale of resources that this resource management activity hopes to manage. Then, the server can broadcast the target scale information to the second node through the node network, so that the applicant can make a resource management application for this resource management activity.

[0040] The node network where the first and second nodes reside can be a blockchain network, a wireless sensor network, the internet, a cellular network, a content distribution network, or any other feasible network. Resource management activities can include fund-raising, material donations, product auctions, paid content subscriptions, environmental recycling, points redemption, or any other feasible activity. Managers can select the appropriate node network type for their desired resource management activities based on their hardware availability and activity requirements.

[0041] As an example, if the manager wants to conduct a fund raising activity, the target scale information can be the total amount of fund resources that need to be raised. The applicant will apply through resource management to enable the smart contract to process its own target management resources (that is, the amount that the applicant wants to invest in the fund raising activity). If the target management resources do not exceed the current scale information (that is, the amount of fund resources that the manager has already raised), the target management resources in the applicant's account can be deducted and collected, and the current scale information can be updated at the same time to display the current scale information after deducting the target management resources.

[0042] As another example, if the manager wants to conduct a paid content subscription activity, the target scale information can be the total subscription amount corresponding to the total number of users who can pay for subscription. The applicant will apply through resource management to enable the smart contract to process its own target management resources (that is, the amount required for the applicant's subscription). If the target management resources do not exceed the current scale information (that is, the paid subscription amount that the manager has collected), the target management resources in the applicant's account can be deducted and collected, and the current scale information can be updated at the same time to display the current scale information after deducting the target management resources.

[0043] As another example, if the management party wants to carry out environmental recycling activities, the target scale information can be the upper limit of the recycling quantity of specified recyclable environmentally friendly items. The applicant will apply through resource management to enable the smart contract to process its own target management resources (that is, the number of recyclable environmentally friendly items that the applicant wants to submit). If the target management resources do not exceed the current scale information (that is, the current recycling quantity of recyclable environmentally friendly items that the management party has collected), the target management resources in the applicant's account can be deducted and collected, and the current scale information can be updated at the same time to display the current scale information after deducting the target management resources.

[0044] For ease of understanding, this embodiment and subsequent embodiments will be explained using the example of a fund resource fundraising activity conducted through a blockchain network. The blockchain network can be a consortium chain, the first node can be an authorized node in the consortium chain, and the second node can be an unauthorized node in the consortium chain. In other embodiments, the blockchain network can also be a public or private chain. The consortium chain divides each blockchain node into a first node and a second node. The first node is an authorized node and will be used by the resource manager, while the second node is an unauthorized node and will be used by users who want to participate in the fundraising and submit fundraising applications. As shown in Figure 3, when the manager wants to start a resource management activity, the manager can access the SDK through the first terminal to send a management instruction to the first node. After the first node detects the management instruction, it will determine the type of resources to be raised and the total amount of resources to be raised (i.e., target scale information) based on the management instruction. This target scale information can be regarded as the upper limit of the resource scale to be raised for this resource management activity. The first node will then broadcast the target scale information to each second node adjacent to the first node. After receiving the target scale information broadcast by the first node, each second node will continue to broadcast it to other nodes, ultimately ensuring that all nodes in the entire alliance chain receive the same target scale information. In other embodiments, in addition to the second blockchain nodes, the first node that receives the management instruction will also broadcast the target scale information to other first nodes.

[0045] As an optional embodiment of this specification, when any node receives broadcast data, it will verify the signature of the broadcast object and decrypt the broadcast data based on the key. After the signature authentication is successful and the hash value of the decrypted data matches the preset hash value, it will store the decrypted data and broadcast the broadcast data to adjacent nodes.

[0046] Specifically, to ensure the security of broadcast data, it is encrypted. Upon receiving broadcast data, both the first and second nodes will first verify the signature of the broadcasting object. Only broadcast objects with signatures unique to the consortium chain are considered other nodes on the consortium chain. The node then uses its own key to decrypt the received broadcast data. The node then calculates the hash value of the decrypted data and compares it with the pre-set hash value for the consortium chain. If the two match, indicating the data is valid, the node will store the decrypted data and broadcast it to other neighboring nodes.

[0047] Step 203: Whenever the second node receives a resource management application, it processes the target management resources based on the smart contract.

[0048] The smart contract is used to update the current scale information based on the target management resource when the target management resource matches the current scale information.

[0049] Specifically, after the administrator broadcasts the target scale information to each second node via the first node, potential users or associated applicant organizations can query the fundraising campaign through the second node and learn the target scale information. Subsequently, the user or applicant organization can submit a resource management request to the second node via SDK access. The second node will determine the target management resource corresponding to the resource management request. The second node will then invoke a smart contract to process the target management resource. Specifically, the smart contract compares the current scale information with the target management resource and calculates the difference in credit limit. If the difference is not negative, it indicates that the target management resource matches the current scale information, and the application will be successfully processed. The smart contract will then retrieve the target management resource from the applicant's account and subtract the target management resource from the current scale information to create the new current scale information. If the difference is negative, it indicates that the current scale information cannot accommodate the target management resource, and the application will fail to process without deducting the credit limit.

[0050] Step 205: Determine feedback information and a feedback target based on the processing result of the smart contract, and send the feedback information to the feedback target.

[0051] Specifically, the smart contract's processing process can represent different result information, such as success or failure, depending on whether the target management resource can be successfully deducted. Different processing results can necessitate different subsequent processing procedures. For example, if the processing is successful, the latest current scale information needs to be broadcast to other nodes for updating. Alternatively, if the processing fails, the applicant for the target management resource needs to be informed that the application has failed because the requested amount exceeds the remaining amount. Therefore, the second node will determine different feedback information and feedback recipients based on the processing results, and send the feedback information to the feedback recipient.

[0052] As an example, different types of feedback information can be pre-configured with different information templates, and a pre-established mapping relationship can be established between the feedback information, processing results, and feedback objects to form a database. In actual practice, the second node can directly query the database based on the processing results to determine the feedback information template and feedback object, and then fill in the template based on the actual data.

[0053] As an optional embodiment of this specification, the method further includes: when the processing result of the smart contract is characterized as a processing failure, generating a reminder message based on the current scale information at the current moment, and sending the reminder message to the feedback object, wherein the reminder message is used to indicate the upper limit of resources that can currently be managed.

[0054] Specifically, a processing result characterized as a processing failure generally means that during the process of the applicant determining the target management resource and submitting the application, other nodes successfully processed the quota and broadcast the latest current scale information, causing the target management resource to exceed the latest current scale information and become unprocessable. In this case, after the processing fails, the second node will determine the current scale information at the current moment, generate a reminder message from this, and send it to the feedback object, allowing the feedback object to determine the latest current scale information based on the reminder message, thereby assisting the feedback object in determining whether to apply again and the application quota that should be filled in when reapplying, thereby improving the success rate of resource management applications.

[0055] As an optional embodiment of this specification, the generation of reminder information based on the current scale information at the current moment includes: determining a statistical time period based on the current moment, and determining the number of processing failures based on historical processing records within the statistical time period; dividing the current scale information based on the number of failures to obtain recommended management resources, and generating reminder information based on the recommended management resources.

[0056] Specifically, within a certain time period, multiple users may submit resource management applications through different second nodes, and most of these applications may fail because the first application submitted was successfully processed. In this case, if the current scale information is directly used to generate reminders, multiple users may still apply using the current scale information. As a result, only a few applications will be successfully processed, while the others' subsequent applications will still fail, resulting in a poor application experience. Therefore, when generating reminders, the node also determines the statistical time period based on the current time, retrieves historical processing records within the statistical time period, and determines the number of processing failures during this period based on the historical processing records. The number of processing failures can be regarded as the number of subsequent simultaneous applications. To prevent the majority of applications from failing again, the current scale information can be divided according to the number of failures to obtain a number of recommended management resources, and the reminder information is ultimately generated based on these recommended management resources. The statistical time period can be set to a preset duration. For example, if the preset duration is 5 minutes and the current time is 12:00, the statistical time period can be 11:55-12:00. The current scale information can be divided equally according to the number of failures, or different weights can be assigned to these users according to the order of application time of each failed application and divided according to the weights.

[0057] In addition, if the user applies according to the reminder information and the application is successful, but the current scale information still exists, the above process can be repeated to generate the reminder information again. Alternatively, the user can wait for a while until the number of processing failures in the statistical time period is zero and then generate the reminder information.

[0058] In the embodiment of this specification, the management instruction is detected by the first node, and the target management resource is broadcast in the node network. When the second node receives the resource management application sent by the user, it will judge the target management resource through the smart contract to determine whether the current scale information can match the target management resource, and perform different processing according to the matching situation. Finally, the node network will feedback the application failure to the user based on the processing result or broadcast the latest current scale information to other nodes. Through the above process, decentralized data synchronization of current scale information is achieved, and the resource scale can be accurately controlled, which brings a better experience to users. In addition, the user's resources will not be managed if the application fails, reducing resource costs.

[0059] The foregoing description of this specification describes specific embodiments. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in an order different from that described in the embodiments and still achieve the desired results. Furthermore, the processes depicted in the accompanying drawings do not necessarily require the specific order shown or the sequential order to achieve the desired results. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0060] As another optional embodiment of this specification, please refer to Figure 4, which shows an overall flow chart of another resource scale management method provided by an embodiment of this specification. This resource scale management method can be used in the server corresponding to the full node in the node network that is responsible for tracking and maintaining the overall data processing process performed by each other node.

[0061] As shown in FIG4 , the resource scale management method may include at least the following steps.

[0062] Step 401: Detect a management instruction based on a first node.

[0063] Specifically, step 401 may refer to step 201 and will not be described in detail here.

[0064] Step 403: Asymmetrically encrypt the target scale information corresponding to the management instruction, and asynchronously broadcast the encrypted target scale information to at least one second node through the first node.

[0065] Specifically, after the first node detects a resource management instruction and determines the target scale information based on it, it uses asymmetric encryption to encrypt the target scale information with a pre-set public key. It then packages the encrypted target scale information and sends it to the adjacent second node via asynchronous broadcast. This approach not only strengthens data confidentiality but also improves data transmission efficiency by eliminating the need to wait for other nodes to complete verification and processing.

[0066] Step 405: Whenever the second node receives a resource management application, it processes the target management resources based on the smart contract.

[0067] The smart contract is used to update the current scale information based on the target management resource when the target management resource matches the current scale information.

[0068] Specifically, step 405 may refer to step 203 and will not be described in detail here.

[0069] Step 407: When the processing result of the smart contract is characterized as successful processing, at least one node adjacent to the second node is determined as a feedback object, and feedback information is generated based on the current scale information at the current moment.

[0070] Specifically, the processing results of a smart contract can be characterized as either successful or unsuccessful. Success means the second node has deducted the target management resources from the applicant and reduced the current scale information accordingly. This reduced current scale information needs to be broadcast to the remaining nodes for update. Therefore, the second node can identify neighboring nodes as feedback targets, and since the content to be broadcast is the current scale information, it will generate notification information based on this information.

[0071] Step 409: Broadcast the feedback information to the feedback object.

[0072] Specifically, in the case of successful processing, the feedback object is the adjacent node, so the feedback information will be sent in a broadcasting manner. Specifically, the broadcasting manner can be asynchronous broadcasting.

[0073] Step 411: When the processing result of the smart contract is characterized as a processing failure, the application object of the resource management application is determined as a feedback object, and feedback information is generated based on the text information corresponding to the processing result.

[0074] Specifically, if the processing fails, this means the second node didn't actually deduct the target management resources from the applicant because the target management resources exceeded the current scale. Therefore, the application failed. In this case, the second node generates corresponding feedback to the applicant, informing them of the failure and the reason for the failure. Therefore, the second node identifies the applicant of the resource management application as the feedback target and generates feedback information based on the text information of the processing result.

[0075] Step 413: Determine the target terminal of the feedback object, and send the feedback information to the target terminal.

[0076] Specifically, in the case of processing failure, the feedback object is the applicant, so the second node can first determine the target terminal to which the applicant sends the resource management application, and send the feedback information to the target terminal to ensure that the applicant can receive the feedback information.

[0077] In the embodiment of this specification, the management instruction is detected by the first node, and after the target management resource is asymmetrically encrypted, the target management resource is asynchronously broadcast in the node network. When the second node receives the resource management application sent by the user, it will judge the target management resource through the smart contract to determine whether the current scale information can match the target management resource, and perform different processing according to the matching situation. For successful processing, feedback information will be generated based on the latest current scale information, and the feedback information will be broadcast to the remaining nodes. For failed processing, feedback information will be generated based on the text information of the processing result, and the feedback information will be sent to the target terminal of the applicant. Through the above process, decentralized data synchronization of the current scale information is achieved, and the resource scale can be accurately controlled. According to the different processing results of each resource management application, different result processing methods are automatically performed, and the scale of resource management is more efficiently controlled.

[0078] The foregoing description of this specification describes specific embodiments. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in an order different from that described in the embodiments and still achieve the desired results. Furthermore, the processes depicted in the accompanying drawings do not necessarily require the specific order shown or the sequential order to achieve the desired results. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0079] Next, please refer to Figure 5, which shows a schematic diagram of the structure of a resource scale management device provided in an embodiment of this specification. It should be noted that the resource scale management device shown in Figure 5 is used to execute the method of the embodiment shown in Figure 2 of this application. For ease of explanation, only the portion relevant to the embodiment of this application is shown. For specific technical details not disclosed, please refer to the embodiment shown in Figure 2 of this application.

[0080] As shown in Figure 5, the resource scale management device may include at least: a detection module 501, which is used to detect a management instruction based on a first node, and broadcast the target scale information corresponding to the management instruction to at least one second node through the first node; a processing module 502, which is used to process the target management resource based on the smart contract whenever the second node receives a resource management application, and the smart contract is used to update the current scale information based on the target management resource when the target management resource matches the current scale information; a sending module 503, which is used to determine feedback information and a feedback object based on the processing result of the smart contract, and send the feedback information to the feedback object.

[0081] As an option in the embodiment of this specification, the detection module 501 is specifically used to: asymmetrically encrypt the target scale information corresponding to the management instruction, and asynchronously broadcast the encrypted target scale information to at least one second node through the first node.

[0082] As an optional embodiment of this specification, when any node receives broadcast data, it will verify the signature of the broadcast object and decrypt the broadcast data based on the key. After the signature authentication is successful and the hash value of the decrypted data matches the preset hash value, it will store the decrypted data and broadcast the broadcast data to adjacent nodes.

[0083] As an optional embodiment of this specification, the sending module 503 is specifically used to: when the processing result of the smart contract is characterized as successful processing, determine at least one node adjacent to the second node as a feedback object, and generate feedback information based on the current scale information at the current moment; when the processing result of the smart contract is characterized as a processing failure, determine the application object of the resource management application as a feedback object, and generate feedback information based on the text information corresponding to the processing result.

[0084] As an optional embodiment of this specification, the sending module 503 is further specifically used to: when the processing result of the smart contract is characterized as successful processing, broadcast the feedback information to the feedback object; when the processing result of the smart contract is characterized as a processing failure, determine the target terminal of the feedback object and send the feedback information to the target terminal.

[0085] As an optional embodiment of this specification, the device also includes: a generation module, which is used to generate reminder information based on the current scale information at the current moment when the processing result of the smart contract is characterized as a processing failure, and send the reminder information to the feedback object, wherein the reminder information is used to indicate the upper limit of resources that can be managed at present.

[0086] As an optional embodiment of this specification, the generation module is specifically used to: determine a statistical time period based on the current moment, and determine the number of processing failures based on historical processing records within the statistical time period; divide the current scale information based on the number of failures, obtain recommended management resources, and generate reminder information based on the recommended management resources.

[0087] Those skilled in the art will clearly understand that the technical solutions of the embodiments of the present application can be implemented with the help of software and / or hardware. "Unit" and "module" in this specification refer to software and / or hardware that can independently perform or cooperate with other components to perform specific functions, where the hardware can be, for example, a field programmable gate array (FPGA), an integrated circuit (IC), etc.

[0088] Each processing unit and / or module in the embodiments of the present application may be implemented by an analog circuit that implements the functions described in the embodiments of the present application, or may be implemented by software that executes the functions described in the embodiments of the present application.

[0089] Next, please refer to FIG6 , which shows a schematic structural diagram of an electronic device provided in an embodiment of this specification.

[0090] As shown in FIG. 6 , the electronic device 600 may include: at least one processor 601 , at least one network interface 604 , a user interface 603 , a memory 605 , and at least one communication bus 602 .

[0091] The communication bus 602 may be used to implement connection and communication among the above components.

[0092] The user interface 603 may include buttons, and the optional user interface may also include a standard wired interface or a wireless interface.

[0093] The network interface 604 may include, but is not limited to, a Bluetooth module, an NFC module, a Wi-Fi module, and the like.

[0094] Among them, the processor 601 may include one or more processing cores. The processor 601 uses various interfaces and lines to connect the various parts of the entire electronic device 600, and executes various functions of the electronic device 600 and processes data by running or executing instructions, programs, code sets or instruction sets stored in the memory 605, and calling data stored in the memory 605. Optionally, the processor 601 can be implemented in at least one hardware form of DSP, FPGA, PLA. The processor 601 can integrate one or a combination of CPU, GPU and modem. Among them, the CPU mainly processes the operating system, user interface and application programs; the GPU is responsible for rendering and drawing the content to be displayed on the display screen; the modem is used to handle wireless communications. It is understandable that the above-mentioned modem may not be integrated into the processor 601, but may be implemented separately through a chip.

[0095] Among them, the memory 605 may include RAM and may also include ROM. Optionally, the memory 605 includes a non-transitory computer-readable medium. The memory 605 can be used to store instructions, programs, codes, code sets or instruction sets. The memory 605 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for at least one function (such as a touch function, a sound playback function, an image playback function, etc.), instructions for implementing the above-mentioned various method embodiments, etc.; the data storage area may store data involved in the above-mentioned various method embodiments, etc. The memory 605 may also be at least one storage device located away from the aforementioned processor 601. As shown in Figure 6, the memory 605 as a computer storage medium may include an operating system, a network communication module, a user interface module and program instructions.

[0096] Specifically, the processor 601 can be used to call the resource scale management application stored in the memory 605, and perform the following operations: based on the first node detecting the management instruction, broadcasting the target scale information corresponding to the management instruction to at least one second node through the first node; whenever the second node receives a resource management application, processing the target management resource based on the smart contract, and the smart contract is used to update the current scale information based on the target management resource when the target management resource matches the current scale information; determining the feedback information and feedback object based on the processing result of the smart contract, and sending the feedback information to the feedback object.

[0097] As an optional embodiment of this specification, broadcasting the target scale information corresponding to the management instruction to at least one second node through the first node includes: asymmetrically encrypting the target scale information corresponding to the management instruction, and asynchronously broadcasting the encrypted target scale information to at least one second node through the first node.

[0098] As an optional embodiment of this specification, when any node receives broadcast data, it will verify the signature of the broadcast object and decrypt the broadcast data based on the key. After the signature authentication is successful and the hash value of the decrypted data matches the preset hash value, it will store the decrypted data and broadcast the broadcast data to adjacent nodes.

[0099] As an optional embodiment of this specification, the determining of feedback information and feedback object based on the processing result of the smart contract includes: when the processing result of the smart contract is characterized as successful processing, determining at least one node adjacent to the second node as a feedback object, and generating feedback information based on the current scale information at the current moment; when the processing result of the smart contract is characterized as a processing failure, determining the application object of the resource management application as a feedback object, and generating feedback information based on the text information corresponding to the processing result.

[0100] As an optional embodiment of this specification, the sending of the feedback information to the feedback object includes: when the processing result of the smart contract is characterized as successful processing, broadcasting the feedback information to the feedback object; when the processing result of the smart contract is characterized as a processing failure, determining the target terminal of the feedback object and sending the feedback information to the target terminal.

[0101] As an optional embodiment of this specification, the method further includes: when the processing result of the smart contract is characterized as a processing failure, generating a reminder message based on the current scale information at the current moment, and sending the reminder message to the feedback object, wherein the reminder message is used to indicate the upper limit of resources that can currently be managed.

[0102] As an optional embodiment of this specification, the generation of reminder information based on the current scale information at the current moment includes: determining a statistical time period based on the current moment, and determining the number of processing failures based on historical processing records within the statistical time period; dividing the current scale information based on the number of failures to obtain recommended management resources, and generating reminder information based on the recommended management resources.

[0103] The embodiments of this specification also provide a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the above method. The computer-readable storage medium may include, but is not limited to, any type of disk, including a floppy disk, an optical disk, a DVD, a CD-ROM, a microdrive, a magneto-optical disk, a ROM, a RAM, an EPROM, an EEPROM, a DRAM, a VRAM, a flash memory device, a magnetic or optical card, a nanosystem (including a molecular memory IC), or any type of medium or device suitable for storing instructions and / or data.

[0104] It should be noted that for the aforementioned method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that this application is not limited by the order of the actions described, because according to this application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by this application.

[0105] In the above embodiments, the description of each embodiment has its own focus. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0106] In the several embodiments provided in this application, it should be understood that the disclosed devices can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some service interface, and the indirect coupling or communication connection of the device or unit can be electrical or other forms.

[0107] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0108] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0109] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable memory. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a memory, including a number of instructions for enabling a computer device (which can be a personal computer, server or network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned memory includes: various media that can store program codes, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk.

[0110] Those skilled in the art will appreciate that all or part of the steps in the various methods of the above embodiments can be completed by instructing related hardware through a program, and the program can be stored in a computer-readable memory, which may include: a flash drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0111] The foregoing description of this specification describes specific embodiments. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in an order different from that described in the embodiments and still achieve the desired results. Furthermore, the processes depicted in the accompanying drawings do not necessarily require the specific order shown or the sequential order to achieve the desired results. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.

Claims

1. A resource scale management method, comprising: detecting a management instruction based on the first node, broadcasting target scale information corresponding to the management instruction to at least one second node through the first node; Whenever the second node receives a resource management request, processing a target management resource based on a smart contract, wherein the smart contract is configured to update the current scale information based on the target management resource when the target management resource matches the current scale information; Determine feedback information and a feedback target based on the processing result of the smart contract, and send the feedback information to the feedback target.

2. The method according to claim 1, wherein broadcasting the target scale information corresponding to the management instruction to at least one second node through the first node comprises: Asymmetrically encrypt the target scale information corresponding to the management instruction, and asynchronously broadcast the encrypted target scale information to at least one second node through the first node.

3. According to the method described in claim 1, when any node receives broadcast data, it will verify the signature of the broadcast object and decrypt the broadcast data based on the key. After the signature authentication is successful and the hash value of the decrypted data matches the preset hash value, it will store the decrypted data and broadcast the broadcast data to adjacent nodes.

4. The method according to claim 1, wherein determining feedback information and feedback recipients based on the processing result of the smart contract comprises: When the processing result of the smart contract is characterized as successful, determining at least one node adjacent to the second node as a feedback target, and generating feedback information based on the current scale information at the current moment; When the processing result of the smart contract is characterized as a processing failure, the application object of the resource management application is determined as a feedback object, and feedback information is generated based on text information corresponding to the processing result.

5. The method according to claim 4, wherein sending the feedback information to the feedback object comprises: When the processing result of the smart contract is characterized as successful processing, broadcasting the feedback information to the feedback object; When the processing result of the smart contract is characterized as a processing failure, a target terminal of the feedback object is determined, and the feedback information is sent to the target terminal.

6. The method according to claim 1, further comprising: When the processing result of the smart contract is characterized as a processing failure, a reminder message is generated based on the current scale information at the current moment, and the reminder message is sent to the feedback object. The reminder message is used to indicate the upper limit of resources that can be managed at present.

7. The method according to claim 6, wherein generating reminder information based on the current scale information at the current moment comprises: Determine a statistical time period based on the current moment, and determine the number of processing failures based on historical processing records within the statistical time period; The current scale information is divided based on the number of failures to obtain recommended management resources, and reminder information is generated based on the recommended management resources.

8. A resource scale management device, comprising: a detection module, configured to detect a management instruction based on a first node, and broadcast target scale information corresponding to the management instruction to at least one second node through the first node; a processing module, configured to process a target management resource based on a smart contract whenever the second node receives a resource management request, wherein the smart contract is configured to update the current scale information based on the target management resource when the target management resource matches the current scale information; A sending module is used to determine feedback information and a feedback object based on the processing result of the smart contract, and send the feedback information to the feedback object.

9. The device according to claim 8, wherein the detection module is specifically configured to: Asymmetrically encrypt the target scale information corresponding to the management instruction, and asynchronously broadcast the encrypted target scale information to at least one second node through the first node.

10. According to the device according to claim 8, when any node receives broadcast data, it will verify the signature of the broadcast object and decrypt the broadcast data based on the key. After the signature authentication is successful and the hash value of the decrypted data matches the preset hash value, the decrypted data will be stored and broadcast to adjacent nodes.

11. The device according to claim 8, wherein the sending module is specifically configured to: When the processing result of the smart contract is characterized as successful, determining at least one node adjacent to the second node as a feedback target, and generating feedback information based on the current scale information at the current moment; When the processing result of the smart contract is characterized as a processing failure, the application object of the resource management application is determined as a feedback object, and feedback information is generated based on text information corresponding to the processing result.

12. The device according to claim 11, wherein the sending module is further configured to: When the processing result of the smart contract is characterized as successful processing, broadcasting the feedback information to the feedback object; When the processing result of the smart contract is characterized as a processing failure, a target terminal of the feedback object is determined, and the feedback information is sent to the target terminal.

13. The apparatus according to claim 8, further comprising: A generation module is configured to generate a reminder message based on the current scale information at the current moment when the processing result of the smart contract is characterized as a processing failure, and send the reminder message to the feedback object, wherein the reminder message is used to indicate the upper limit of resources that can be managed at present.

14. The apparatus according to claim 13, wherein the generating module is specifically configured to: Determine a statistical time period based on the current moment, and determine the number of processing failures based on historical processing records within the statistical time period; The current scale information is divided based on the number of failures to obtain recommended management resources, and reminder information is generated based on the recommended management resources.

15. An electronic device comprising a processor and a memory; The processor is connected to the memory; The memory is used to store executable program code; The processor runs a program corresponding to the executable program code by reading the executable program code stored in the memory, so as to execute the method according to any one of claims 1 to 7.

16. A computer-readable storage medium having a computer program stored thereon, wherein the computer-readable storage medium stores instructions, and when the instructions are executed on a computer or a processor, the computer or processor is caused to execute the steps of the method according to any one of claims 1 to 7.

Images