Resource allocation method and device, equipment and medium
By secretly dividing service requests and hardware identity identification in a cloud and multi-core environment, a trust chain is built for request allocation, which solves the problems of waste of cloud computing resources and insufficient real-time performance, and achieves efficient and stable allocation of resources and real-time service response.
Patent Information
- Application Number
- CN202510725226.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-05-30
- Publication Date
- 2025-08-08
AI Technical Summary
In the one-cloud multi-core scenario, cloud computing resource allocation has limitations, resulting in waste of computing resources and insufficient real-time performance, and cannot support high-intensive and real-time operation.
By receiving service requests and dividing them into request queues according to the secret level, the identity of the hardware components is identified and the trust chain is formed, and request allocation is carried out according to the correspondence between the secret level and the trust chain, and dynamic priority scheduling is realized.
It improves resource utilization, ensures that computing power accurately matches task requirements, avoids resource waste, improves business stability and real-timeness, and adapts to the needs of high-density and real-time scenarios.
Smart Images

Figure CN120455401A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of computer technology, and in particular to a resource allocation method, device, equipment and medium. Background Art
[0002] With the accelerated development of the information and communication technology (ICT) industry, cloud computing has become a key form of ICT innovation. In scenarios with multiple cores and a single cloud, the following issues often arise: Hardware resources are highly complex, and resource allocation is limited. Related technical solutions typically allocate tasks according to unified standards and process large numbers of business requests using a single trust mechanism, disregarding hardware differences. This can lead to significant waste of computing resources in cloud environments and, in scenarios with high real-time requirements, can easily lead to inaccurate task allocation and delayed business responses. Summary of the Invention
[0003] The present invention provides a resource allocation method, device, equipment and medium to at least solve the problem in related technologies of waste of cloud environment computing resources and insufficient real-time performance to support current business operations.
[0004] The present invention provides a resource allocation method, comprising:
[0005] Receiving a business processing request, classifying the business processing request according to a preset classification rule, and obtaining a request queue of a corresponding classification level;
[0006] Query the identities of the hardware components in the current platform, classify the hardware components according to the identities according to the preset type classification rules, and form a trust chain with the classified hardware components with corresponding identity types as carriers;
[0007] According to the correspondence between the confidentiality level of the request queue and the trust chain, the request queue is assigned to the corresponding trust chain for processing.
[0008] The present invention also provides a resource allocation device, comprising:
[0009] A request classification module is used to receive business processing requests, classify the business processing requests according to preset confidentiality classification rules, and obtain a request queue of the corresponding confidentiality level;
[0010] A trust chain composition module is used to query the identities of hardware components in the current platform, classify the hardware components according to the identities according to preset type classification rules, and form a trust chain with the classified hardware components with corresponding identity types as carriers;
[0011] The task allocation module is used to allocate the request queue to the corresponding trust chain for processing according to the corresponding relationship between the confidentiality level of the request queue and the trust chain.
[0012] The present invention also provides an electronic device, comprising: a memory for storing a computer program; and a processor for implementing the steps of any one of the above-mentioned resource allocation methods when executing the computer program.
[0013] The present invention also provides a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a processor, the steps of any one of the above-mentioned resource allocation methods are implemented.
[0014] Through the present invention, the received business processing requests are divided into request queues of different confidentiality levels according to the confidentiality level, and the identities of the hardware components in the current platform are identified and classified to form trust chains of different identity types. According to the relationship between the confidentiality level of the request queue and the trust chain, the request queue can be effectively allocated to the corresponding trust chain according to the request confidentiality level; in this way, according to the processing of the trust chain, the allocation of requests according to the confidentiality level in a one-cloud multi-core environment can be reasonably controlled, and dynamic priority scheduling can be performed within the corresponding trust chain to achieve stable and efficient operation of a large number of business processing requests, improve real-time performance, ensure that computing power accurately matches task requirements, avoid waste of resources, and thus solve the problem that the traditional cloud computing resource reliability allocation method leads to waste of cloud environment computing power resources and insufficient real-time performance to support current business operation, improve the effective utilization rate of virtual machine resources, ensure the stable and efficient operation of upper-layer business, and deeply adapt to high-density and real-time scenarios.
[0015] In addition, the present invention also provides a corresponding resource allocation device, electronic device and computer-readable storage medium for the resource allocation method, which have the same or corresponding technical features as the above-mentioned resource allocation method and have the same effects as above. BRIEF DESCRIPTION OF THE DRAWINGS
[0016] In order to more clearly illustrate the embodiments of the present invention, the following is a brief introduction to the drawings required for use in the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.
[0017] Figure 1 A flowchart of a resource allocation method provided in an embodiment of the present invention;
[0018] Figure 2 A schematic diagram of classifying business processing requests according to preset confidentiality classification rules provided in an embodiment of the present invention;
[0019] Figure 3 A schematic diagram of classifying hardware components according to preset type classification rules provided in an embodiment of the present invention;
[0020] Figure 4 A schematic diagram of allocating request queues to corresponding trust chains for processing provided by an embodiment of the present invention;
[0021] Figure 5 A schematic diagram of the structure of a resource allocation device provided by an embodiment of the present invention. DETAILED DESCRIPTION
[0022] "One cloud, multiple cores" refers to the use of a single cloud platform to manage computing resources with different chip architectures, enabling unified management and scheduling of heterogeneous resources. This cloud platform shields underlying architecture differences, providing users with a consistent cloud computing service experience. This "one cloud, multiple cores" architecture, with its heterogeneous computing capabilities, high scalability, and flexible adaptability to diverse application workloads, has gradually become a mainstream development direction in the cloud computing field. However, this architecture presents unprecedented complexity in various hardware resources. Different chip architectures exhibit significant differences in instruction sets, processing performance, and security mechanisms. Coupled with the collaborative operation of diverse storage devices and network components, ensuring the security and reliability of resources presents significant challenges.
[0023] Current research on resource reliability in cloud computing environments focuses on the trustworthiness of cloud computing system platforms from the perspectives of computer hardware, operating systems, and applications. Secondly, research on trust mechanisms between service providers and consumers involves establishing trust models to analyze the relationship between service providers' reputation, service quality commitments, and consumer trust decisions, aiming to improve the success rate and stability of service transactions. However, current research has significant shortcomings. In research on the trustworthiness of cloud computing system platforms, applying the same level of trustworthiness verification to all requests not only wastes valuable computing resources but can also cause delays in responses to common query services, impacting user experience. For scenarios with extremely high real-time requirements, complex trustworthiness verification can prevent task allocation from accurately matching hardware resources, resulting in processing delays. Research on trust mechanisms between service providers and consumers focuses solely on the trust mechanism itself, without considering whether consumers require trust verification. In reality, different consumers have different security requirements and risk tolerance for services. Some consumers with lower security requirements may prioritize cost and efficiency. Excessive trust verification can increase the barrier to entry for service use and reduce user satisfaction.
[0024] In order to solve the problems such as the above-mentioned traditional cloud computing resource reliability allocation method causing waste of computing resources in the entire cloud environment and insufficient real-time performance to support current business operations, the present invention provides a resource allocation method.
[0025] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of them. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making any creative efforts shall fall within the scope of protection of the present invention.
[0026] It should be noted that, in the description of the present invention, the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, article, or apparatus comprising a series of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, article, or apparatus. The terms "first," "second," etc., in the present invention are used to distinguish similar objects, and are not used to describe a particular order or precedence.
[0027] In order to enable those skilled in the art to better understand the solutions of the present invention, the present invention is further described in detail below with reference to the accompanying drawings and specific implementation methods.
[0028] In conjunction with the specific application environment architecture or specific hardware architecture on which the execution of the resource allocation method depends, the specific application environment architecture or the specific hardware architecture is described herein.
[0029] An embodiment of the present invention provides a resource allocation method, which is described in detail in conjunction with the execution flow of the resource allocation method. Figure 1 A flow chart of a resource allocation method provided in an embodiment of the present invention is shown in FIG. Figure 1 As shown, the method includes:
[0030] S101: Receive a business processing request, classify the business processing request according to a preset confidentiality classification rule, and obtain a request queue of a corresponding confidentiality level.
[0031] It should be noted that the confidentiality level refers to the degree of confidentiality. Step S101 can be performed by the request classification module. In a complex computing environment with one cloud and multiple cores, the request classification module can serve as the core hub for the creation of system service units, taking on the key task of real-time monitoring and classification of business requests. This module acts as an intelligent sorter for the entire system. Through precise identification and classification, it ensures that requests with different security requirements can be adaptively treated in the subsequent processing flow, effectively improving resource utilization efficiency and ensuring data security.
[0032] When the current platform receives a front-end business processing request, the business processing request can be passed to the request classification module, which will classify the received business processing request according to the preset classification rules and obtain a request queue of the corresponding classification level. The preset classification rules can be formulated based on business needs and security policies. The classification rules can be stored in the system in the form of configuration files or database tables, allowing administrators to flexibly adjust and update them according to actual business changes and security requirements. When a business processing request is received, the key information in the request is automatically extracted and matched one by one with the preset classification rules. The classification level of the request is determined based on the matching results. Based on the classification results, the request can be assigned to the corresponding request queue. Each classification level can correspond to an independent request queue.
[0033] S102: Query the identities of the hardware components in the current platform, classify the hardware components according to the preset type classification rules based on the identities of the hardware components, and form a trust chain with the classified hardware components having corresponding identity types as carriers.
[0034] In implementation, step S102 can be performed by a trust chain composition module. The trust chain composition module can query the hardware information of each component in the current platform and classify the components according to preset classification rules. The preset classification rules can be developed based on the hardware's functional characteristics, security requirements, and application scenarios. The classification rules can be stored in the platform management system in the form of configuration files or database tables, allowing administrators to flexibly adjust them based on business development and technological updates. After obtaining the identity information of the hardware components, the key features of the hardware are automatically extracted. These features are then matched against the preset classification rules one by one, and the hardware's identity type is determined based on the matching results. Based on the classification results, a trust chain is constructed using hardware components with corresponding identity types as carriers. A trust chain is a series of resource chains consisting of hardware resources such as CPUs, memory, hard drives, and network cards. A trust chain can be used to establish a logical chain of trust transfer in network communications, ensuring the legitimacy of digital certificates and the credibility of the holder's identity. Its essence is to pass trust from the root certificate (trust anchor) to the end-entity certificate through a hierarchical certificate verification relationship. The trust chain begins with a root trust anchor, a high-security hardware component. It serves as the source of the trust chain and possesses the highest degree of trust. From this root trust anchor, other hardware components are sequentially connected according to the hardware's security level and functional dependencies. During the trust chain construction process, each hardware component must undergo identity authentication and security measurement. Only hardware that passes verification and whose measurement results meet expectations is included in the trust chain. Trust relationships are communicated between hardware components through digital signatures and encrypted communication, ensuring the integrity and security of the trust chain. All hardware components in each trust chain can correspond to a single identity type, or, depending on the specific situation (such as the presence of non-domestic chips), hardware components in a trust chain can correspond to multiple identity types. This is not a limitation here.
[0035] S103: According to the correspondence between the confidentiality level of the request queue and the trust chain, the request queue is assigned to the corresponding trust chain for processing.
[0036] In implementation, step S103 can be performed by the task allocation module. The task allocation module can allocate the request queue to the corresponding trust chain for processing based on the established correspondence between the confidentiality level of the request queue and the trust chain. In actual applications, as the business environment and security threats change, the correspondence is not static. A dynamic adjustment mechanism can be set here. The administrator can manually modify the configuration according to the actual situation, or automatically monitor and adjust it through the security situation awareness system. In the present invention, the confidentiality level of the request queue can be matched with the pre-established confidentiality level-trust chain correspondence table to quickly locate the corresponding trust chain. After the request enters the trust chain, it can be processed in sequence according to the hardware function order of the trust chain.
[0037] In the above-mentioned resource allocation method provided by the embodiment of the present invention, the received business processing requests are divided into request queues of different levels according to the confidentiality level, and the identities of the hardware components in the current platform are identified and classified to form trust chains of different identity types. According to the relationship between the confidentiality level of the request queue and the trust chain, the request queue can be effectively allocated to the corresponding trust chain according to the request confidentiality level; in this way, according to the processing of the trust chain, the allocation of requests according to the confidentiality level in a one-cloud multi-core environment can be reasonably controlled, and dynamic priority scheduling can be performed within the corresponding trust chain to achieve stable and efficient operation of a large number of business processing requests, improve real-time performance, ensure that computing power accurately matches task requirements, avoid resource waste, and thus solve the problem that the traditional cloud computing resource reliability allocation method leads to waste of cloud environment computing power resources and insufficient real-time performance to support current business operations, improve the effective utilization rate of virtual machine resources, ensure the stable and efficient operation of upper-layer businesses, and deeply adapt to high-density and real-time scenarios.
[0038] Furthermore, in a specific implementation, in the above-mentioned resource allocation method provided in an embodiment of the present invention, step S101 classifies the business processing requests according to a preset confidentiality classification rule to obtain a request queue of a corresponding confidentiality level, which may specifically include: monitoring the business processing requests to obtain multi-dimensional information of the business processing requests; classifying the multi-dimensional information obtained by monitoring according to a preset confidentiality classification rule to obtain the corresponding confidentiality level of the business processing requests; adding a corresponding label to the business processing request based on the corresponding confidentiality level of the business processing request to generate a request queue with a corresponding confidentiality level label.
[0039] In practice, the request classification module monitors business processing requests and determines their classification level through in-depth analysis of multiple dimensions, including business attributes, data content, and transmission protocols. To achieve this precise classification level, the module incorporates a dynamically updateable rules engine to continuously optimize classification strategies to adapt to evolving business scenarios and security requirements.
[0040] After determining the confidentiality level, the request classification module can assign corresponding tags to each request. These tags not only include the confidentiality level, but also key information such as the request's priority, timeliness, and resource requirements, allowing the subsequent system to more efficiently schedule tasks and allocate resources. Figure 2 The embodiment of the present invention provides a schematic diagram of classifying business processing requests according to preset confidentiality classification rules. Figure 2 As shown, requests can be divided into four queues according to their confidentiality levels: top secret queue, confidential queue, secret queue and general queue.
[0041] In specific implementation, the above steps may include adding corresponding labels to the business processing requests based on the corresponding confidentiality levels of the business processing requests, and generating a request queue with corresponding confidentiality level labels. Specifically, the steps may include: when the confidentiality level of the business processing request is top secret, adding a top secret label to the business processing request, and generating a request queue with a top secret label; when the confidentiality level of the business processing request is confidential, adding a confidential label to the business processing request, and generating a request queue with a confidential label; when the confidentiality level of the business processing request is secret, adding a secret label to the business processing request, and generating a request queue with a secret label; when the confidentiality level of the business processing request is general, adding a general label to the business processing request, and generating a request queue with a general label.
[0042] Furthermore, in the specific implementation, in the above resource allocation method provided by the embodiment of the present invention, in order to resist increasingly complex malicious attacks and ensure the security of the request queue, after executing step S101 to obtain the request queue of the corresponding confidentiality level, as shown in FIG. Figure 2 As shown, it may also include: using a national secret algorithm to encrypt and store the request queue. The national secret algorithm may include a symmetric encryption algorithm, an asymmetric encryption algorithm, a hash algorithm, a key exchange algorithm, a random number generation algorithm, and the like.
[0043] In the above steps, the national secret algorithm is used to encrypt and store the request queue, which may specifically include: generating a key corresponding to the request queue through a hash algorithm based on the request header and the confidentiality level keyword; and encrypting and storing the request queue using the key.
[0044] In practice, the key generation process of the present invention can utilize a combination of a request header and a confidentiality keyword. The request header contains basic information such as the request source and transmission protocol, while the confidentiality keyword specifies the security level of the request. These two are then combined and encrypted using a specific hash algorithm to generate a key. This key generation method ensures the key's dynamic nature while being closely linked to the properties of the request itself. Even if an attacker obtains partial request data, it is difficult to decipher the key.
[0045] Accordingly, after executing step S102 to form a trust chain with the classified hardware components having corresponding identity types as carriers, the following steps may be further performed: encrypting and storing the trust chain using a national secret algorithm. The encryption storage method of the trust chain may refer to the encryption storage method of the request queue described above.
[0046] Correspondingly, step S103 allocates the request queue to the corresponding trust chain for processing according to the correspondence between the confidentiality level of the request queue and the trust chain. Specifically, it may include: verifying the request queue and the trust chain, and after the verification is successful, allocating the request queue to the corresponding trust chain for processing according to the correspondence between the confidentiality level of the request queue and the trust chain.
[0047] During implementation, verifying the request queue and trust chain can further ensure the security and accurate execution of business. After successful verification, the request queue is assigned to the trust chain for processing based on the corresponding relationship, realizing the reasonable scheduling and security of resources.
[0048] Furthermore, in specific implementation, in the above-mentioned resource allocation method provided in an embodiment of the present invention, step S102 classifies the hardware components according to the preset type classification rules based on the identities of the hardware components, and forms a trust chain with the classified hardware components with corresponding identity types as carriers. Specifically, it may include: classifying the hardware components according to the preset type classification rules based on the processing and modification properties of the hardware components to obtain hardware components with at least two identity types; adding corresponding labels to the hardware components with at least two identity types to form a trust chain with the hardware components with corresponding identity types as carriers.
[0049] Figure 3 The schematic diagram of the embodiment of the present invention provides a method for classifying hardware components according to the preset type classification rules. Figure 3 As shown, after querying the identity of the hardware part, the present invention can classify the hardware components according to the processing and modification attributes of the hardware components according to preset classification rules, categorizing them into first-category components, second-category components, and third-category components. Processing and modification attributes refer to the characteristics of the hardware components' sources, production links, and degree of localization of key materials / components involved in the manufacturing process. Here, first-category components can be purely domestic components, meaning that the processing and modification attributes meet the requirement of full-chain localization, from design and core components to production and manufacturing, without reliance on imported technology. Second-category components can be non-domestic chip components, where the core chip is imported but other components are processed and modified domestically, or the entire equipment is assembled and adapted domestically. In this case, the processing and modification attributes reflect partial localization, but because the core chip is not domestically produced, the entire component is classified as non-pure domestic production. Third-category components can be purely non-domestic components, where the entire processing and modification process is completed overseas, with no domestic involvement in any production links, and the processing and modification attributes meet the requirement of full-chain non-domestic production.
[0050] This invention can tie the trust level of hardware components to their technological autonomy by categorizing them by processing and modification attributes (e.g., purely domestically produced, non-domestic chips, and non-domestic). Purely domestically produced components can serve as the root node of the trust chain, carrying the highest level of trust transfer. Non-domestic chip components can form a partial trusted node. Non-domestic components can be incorporated into the trust chain as edge nodes. Hardware component labels in the trust chain can serve as a basis for dynamic verification and achieve risk isolation. Through classification, labeling, and chain-based management, this invention can achieve security control and supply chain optimization from the hardware layer to the system layer. Using the trust chain as a link, it can promote the transition of domestically produced hardware from usability to trustworthiness.
[0051] Furthermore, in a specific implementation, in the above-mentioned resource allocation method provided in an embodiment of the present invention, step S103 allocates the request queue to the corresponding trust chain for processing, which may specifically include: allocating the request queue with a top secret label and the request queue with a confidential label to the first trust chain for processing; allocating the request queue with a secret label to the second trust chain for processing; and allocating the request queue with a general label to the third trust chain for processing.
[0052] Figure 4 A schematic diagram of allocating request queues to corresponding trust chains for processing provided by an embodiment of the present invention. In implementation, if all components in the entire trust chain are first-category components (such as purely domestic components), it is defined as a first trust chain; if some components are second-category components (such as some chips are non-domestic components), it is defined as a second trust chain; if all are third-category components (such as purely non-domestic components), it is defined as a third trust chain. After decryption and identity verification are completed, the identity of the request is confirmed, and the request is allocated to different trust chains for processing according to the confidentiality level of the request. Request queues with top-secret labels and request queues with confidential-level labels are allocated to the first trust chain for processing, request queues with secret-level labels are allocated to the second trust chain for processing, and request queues with general-level labels are allocated to the third trust chain for processing.
[0053] Furthermore, in a specific implementation, in the above-mentioned resource allocation method provided in an embodiment of the present invention, before executing step S103 and allocating the request queue to the corresponding trust chain for processing according to the correspondence between the confidentiality level of the request queue and the trust chain, it may also include: pre-associating the trust chain with a processable confidentiality level range; and establishing a correspondence between the confidentiality level of the request queue and the trust chain based on the matching result between the confidentiality level of the request queue and the confidentiality level range associated with the trust chain.
[0054] In practice, the present invention can pre-set a range of security levels for each trust chain. When a request queue is received, its security level is matched with the security level range of the trust chain to establish a corresponding relationship. This process achieves secure scheduling and processing of business requests through precise matching of security levels and trust capabilities, improving overall processing efficiency.
[0055] It should be pointed out that the above-mentioned resource allocation method provided by the present invention can be applied to domestic and non-domestic mixed deployment servers in a one-cloud, multi-core environment. According to this method, request distribution control according to the confidentiality level is performed in the one-cloud, multi-core environment, which can process business requests more safely, stably and efficiently, and realize the safe, reliable, stable and efficient operation of a large number of business requests in a domestic environment, and efficiently allocate business requests to the virtual machine trust chain for processing, avoiding malicious attacks on hardware resources and waste of resources, and is more suitable for business request processing in a one-cloud, multi-core environment.
[0056] Through the description of the above implementation methods, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus the necessary general hardware platform, and of course it can also be implemented by hardware, but in many cases the former is a better implementation method.
[0057] An embodiment of the present application also provides a resource allocation device. Figure 5 This is a schematic diagram of the structure of the resource allocation device provided by an embodiment of the present invention. This embodiment is based on the perspective of functional modules, such as Figure 5 As shown, the device includes:
[0058] The request classification module 10 is used to receive business processing requests, classify the business processing requests according to the preset classification rules, and obtain a request queue of the corresponding classification level;
[0059] The trust chain composition module 11 is used to query the identities of the hardware components in the current platform, classify the hardware components according to the preset type classification rules based on the identities of the hardware components, and form a trust chain with the classified hardware components having the corresponding identity types as carriers;
[0060] The task allocation module 12 is used to allocate the request queue to the corresponding trust chain for processing according to the corresponding relationship between the confidentiality level of the request queue and the trust chain.
[0061] In the above-mentioned resource allocation device provided in the embodiment of the present invention, the received business processing requests can be divided into request queues of different levels according to the confidentiality level through the interaction of the above-mentioned three modules, and the identities of the hardware components in the current platform can be identified and classified to form trust chains of different identity types. According to the relationship between the confidentiality level of the request queue and the trust chain, the request queue is allocated to the corresponding trust chain according to the request confidentiality level; in this way, the allocation of requests according to the confidentiality level in a one-cloud multi-core environment can be reasonably controlled, and dynamic priority scheduling can be performed within the corresponding trust chain to achieve stable and efficient operation of a large number of business processing requests, improve real-time performance, ensure that computing power accurately matches task requirements, avoid resource waste, and thus solve the problem that the traditional cloud computing resource reliability allocation method leads to waste of cloud environment computing power resources and insufficient real-time performance to support current business operations, improve the effective utilization rate of virtual machine resources, ensure the stable and efficient operation of upper-layer businesses, and deeply adapt to high-density and real-time scenarios.
[0062] Since the embodiments of the resource allocation apparatus correspond to the embodiments of the resource allocation method, the description of the features in the corresponding embodiments of the resource allocation apparatus can be found in the description of the corresponding embodiments of the resource allocation method, and will not be repeated here. The embodiments of the resource allocation apparatus have the same beneficial effects as the aforementioned resource allocation method.
[0063] Furthermore, in a specific implementation, in the above-mentioned resource allocation device provided in an embodiment of the present invention, the request classification module 10 can be specifically used to monitor business processing requests to obtain multi-dimensional information of the business processing requests; classify the multi-dimensional information obtained by monitoring according to preset confidentiality classification rules to obtain the corresponding confidentiality level of the business processing request; based on the corresponding confidentiality level of the business processing request, add corresponding labels to the business processing request to generate a request queue with the corresponding confidentiality level label.
[0064] Furthermore, in a specific implementation, in the above-mentioned resource allocation device provided by an embodiment of the present invention, the request classification module 10 can be specifically used to encrypt and store the request queue using a national secret algorithm after obtaining the request queue of the corresponding confidentiality level. The trust chain composition module 11 can be specifically used to encrypt and store the trust chain using a national secret algorithm after forming a trust chain with classified hardware components having corresponding identity types as carriers. The task allocation module 12 can be specifically used to verify the request queue and the trust chain. After the verification is successful, the request queue is assigned to the corresponding trust chain for processing according to the correspondence between the confidentiality level of the request queue and the trust chain.
[0065] Furthermore, in specific implementation, in the above-mentioned resource allocation device provided in an embodiment of the present invention, the request classification module 10 can be specifically used to generate a key corresponding to the request queue through a hash algorithm based on the request header and the confidentiality keyword; and use the key to encrypt and store the request queue.
[0066] Furthermore, in specific implementation, in the above-mentioned resource allocation device provided in the embodiment of the present invention, the trust chain composition module 11 can be specifically used to classify hardware components according to preset type classification rules based on the processing and modification properties of the hardware components, and obtain hardware components of at least two identity types; add corresponding labels to hardware components of at least two identity types, and form a trust chain with the classified hardware components of the corresponding identity types as carriers.
[0067] Furthermore, in a specific implementation, in the resource allocation device provided in the embodiment of the present invention, the request classification module 10 can be used to add a top secret label to the business processing request when the confidentiality level of the business processing request is top secret, thereby generating a request queue with a top secret label; add a confidential label to the business processing request when the confidentiality level of the business processing request is confidential, thereby generating a request queue with a confidential label; add a secret label to the business processing request when the confidentiality level of the business processing request is secret, thereby generating a request queue with a secret label; add a general label to the business processing request when the confidentiality level of the business processing request is general, thereby generating a request queue with a general label. The task allocation module 12 can be used to allocate the request queue with a top secret label and the request queue with a confidential label to the first trust chain for processing; allocate the request queue with a secret label to the second trust chain for processing; and allocate the request queue with a general label to the third trust chain for processing.
[0068] Furthermore, in a specific implementation, the above-mentioned resource allocation device provided in an embodiment of the present invention may also include: a relationship establishment module for pre-associating the trust chain with a processable confidentiality level range; and establishing a corresponding relationship between the confidentiality level of the request queue and the trust chain based on the matching result between the confidentiality level of the request queue and the confidentiality level range associated with the trust chain.
[0069] An embodiment of the present application further provides an electronic device, comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to execute the steps in any one of the above resource allocation method embodiments.
[0070] An embodiment of the present invention further provides a computer-readable storage medium, in which a computer program is stored. The computer program is configured to execute the steps of any of the above-mentioned resource allocation method embodiments when running.
[0071] In an exemplary embodiment, the computer-readable storage medium may include, but is not limited to, various media that can store computer programs, 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.
[0072] An embodiment of the present invention further provides a computer program product, which includes a computer program. When the computer program is executed by a processor, the steps in any one of the above-mentioned resource allocation method embodiments are implemented.
[0073] An embodiment of the present invention further provides another computer program product, including a non-volatile computer-readable storage medium, wherein the non-volatile computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of any of the above-mentioned resource allocation method embodiments are implemented.
[0074] Professionals may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the above description has generally described the components and steps of each example according to their functions. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present invention.
[0075] The above is a detailed introduction to the resource allocation method, device, equipment and medium provided by the present invention. Specific examples are used herein to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only used to help understand the method and core ideas of the present invention. It should be pointed out that for ordinary technicians in this technical field, without departing from the principles of the present invention, several improvements and modifications can be made to the present invention, and these improvements and modifications also fall within the scope of protection of the present invention.
Claims
1. A resource allocation method, characterized in that: include: Receiving a business processing request, classifying the business processing request according to a preset classification rule, and obtaining a request queue of a corresponding classification level; Query the identities of the hardware components in the current platform, classify the hardware components according to the identities according to the preset type classification rules, and form a trust chain with the classified hardware components with corresponding identity types as carriers; According to the correspondence between the confidentiality level of the request queue and the trust chain, the request queue is assigned to the corresponding trust chain for processing.
2. The resource allocation method according to claim 1, characterized in that: The business processing requests are classified according to the preset classification rules to obtain a request queue of the corresponding classification level, including: Monitoring the business processing request to obtain multi-dimensional information of the business processing request; Classify the multi-dimensional information obtained through monitoring according to the preset confidentiality classification rules to obtain the corresponding confidentiality level of the business processing request; Based on the corresponding confidentiality level of the business processing request, a corresponding label is added to the business processing request to generate a request queue with the corresponding confidentiality level label.
3. The resource allocation method according to claim 1, wherein: After obtaining the request queue of the corresponding confidentiality level, it also includes: The request queue is encrypted and stored using a national secret algorithm; After forming a trust chain with classified hardware components having corresponding identity types as carriers, it also includes: The trust chain is encrypted and stored using a national secret algorithm; Allocating the request queue to a corresponding trust chain for processing according to the correspondence between the confidentiality level of the request queue and the trust chain includes: The request queue and the trust chain are verified. After the verification is successful, the request queue is assigned to a corresponding trust chain for processing according to the corresponding relationship between the confidentiality level of the request queue and the trust chain.
4. The resource allocation method according to claim 3, characterized in that: The request queue is encrypted and stored using a national secret algorithm, including: Based on the request header and the confidentiality keyword, a key corresponding to the request queue is generated through a hash algorithm; The request queue is encrypted and stored using the key.
5. The resource allocation method according to claim 1, characterized in that: Classifying the hardware components according to the identities of the hardware components according to preset type classification rules, and forming a trust chain with the classified hardware components having corresponding identity types as carriers, including: Classifying the hardware components according to a preset type classification rule based on the processing and modification attributes of the hardware components to obtain hardware components of at least two identity types; Corresponding tags are added to hardware components of at least two identity types to form a trust chain with hardware components of corresponding identity types as carriers.
6. The resource allocation method according to claim 2, characterized in that: Based on the corresponding confidentiality level of the business processing request, a corresponding label is added to the business processing request to generate a request queue with the corresponding confidentiality level label, including: When the confidentiality level of the business processing request is top secret, adding a top secret label to the business processing request to generate a request queue with the top secret label; When the confidentiality level of the business processing request is confidential, adding a confidentiality level tag to the business processing request to generate a request queue with the confidentiality level tag; When the confidentiality level of the business processing request is secret, a secret-level tag is added to the business processing request to generate a request queue with the secret-level tag; When the confidentiality level of the business processing request is general, adding a general-level tag to the business processing request to generate a request queue with the general-level tag; Allocating the request queue to the corresponding trust chain for processing includes: Assigning the request queue with the top secret label and the request queue with the confidential label to the first trust chain for processing; Assign the request queue with the secret-level label to the second trust chain for processing; Assign the request queue with the general label to the third trust chain for processing.
7. The resource allocation method according to claim 1, characterized in that: Before allocating the request queue to the corresponding trust chain for processing according to the correspondence between the confidentiality level of the request queue and the trust chain, the method further includes: Pre-associate the trust chain with a range of processable confidentiality levels; A corresponding relationship between the confidentiality level of the request queue and the trust chain is established according to a matching result between the confidentiality level of the request queue and the confidentiality level range associated with the trust chain.
8. A resource allocation device, characterized in that: include: A request classification module is used to receive business processing requests, classify the business processing requests according to preset confidentiality classification rules, and obtain a request queue of the corresponding confidentiality level; A trust chain composition module is used to query the identities of hardware components in the current platform, classify the hardware components according to the identities according to preset type classification rules, and form a trust chain with the classified hardware components having corresponding identity types as carriers; The task allocation module is used to allocate the request queue to the corresponding trust chain for processing according to the corresponding relationship between the confidentiality level of the request queue and the trust chain.
9. An electronic device, characterized in that: include: Memory for storing computer programs; A processor, configured to implement the steps of the resource allocation method according to any one of claims 1 to 7 when executing the computer program.
10. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, wherein when the computer program is executed by a processor, the steps of the resource allocation method according to any one of claims 1 to 7 are implemented.