Cloud native password service method and system

Through containerization and k8s resource scheduling, dynamic resource allocation and software integration of cloud native password services are realized, solving the shortcomings of traditional password services in resource utilization and response speed, improving efficiency and convenience, and reducing operations Maintenance cost.

CN119011402AActive Publication Date: 2024-11-22HENAN INFORMATIZATION GRP CO LTD
View PDF 7 Cites 0 Cited by

Patent Information

Application Number
CN202411195429.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-29
Publication Date
2024-11-22
Estimated Expiration
2044-08-29

AI Technical Summary

Technical Problem

Traditional cryptographic services have shortcomings in resource scheduling, service packaging and hardware interface integration, resulting in low resource utilization and slow service response speed, making it difficult to adapt to changing business needs.

Method used

Through containerization and k8s resource scheduling, a comprehensive monitoring system is used to ensure high availability and data security of services, dynamic resource allocation of password services and deep integration of software and hardware, simplify the access process of application systems, and improve resource utilization efficiency and services Response speed.

Benefits of technology

It significantly improves resource utilization efficiency and service response speed, simplifies the access process of application systems, and reduces operation and maintenance costs and management complexity.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119011402A_ABST
    Figure CN119011402A_ABST
Patent Text Reader

Abstract

The invention discloses a cloud native password service method and system, relates to the technical field of cloud native technology and password security, and solves the problems of low resource utilization rate and slow service response speed caused by defects in resource scheduling, service packaging and hardware interface integration. The cloud native password service method comprises the following steps: grouping and packaging provided password services by using a container; dynamically scheduling the container resources; packaging the service capability of the hardware equipment interface; dynamically distributing a route from the application to the service according to the application-service authorization relationship distributed by the tenant; calling hardware password equipment to carry out password service; carrying out containerization and k8s resource scheduling; dynamic resource allocation and software and hardware deep fusion of the password service are realized through a cloud native technology; the resource utilization efficiency and the service response speed are remarkably improved, the access process of the application system is simplified, the service use convenience is improved, and the operation and maintenance cost and the management complexity are greatly reduced.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to cloud native technology and cryptographic security technology, and in particular to a cloud native cryptographic service method and system. Background Art

[0002] With the rapid development of cloud computing technology, dynamic resource allocation and software and hardware integration have become important challenges for cloud services. Traditional cryptographic services are often based on static resource configuration and cannot meet the flexibility and scalability requirements of cloud services.

[0003] There are two traditional solutions for password transformation of application systems: one is practical hardware password equipment, such as server password machines, signature verification servers, timestamp servers, SSL gateways, IPSec VPNs, etc.; the other is to use virtual machines to virtualize password services and provide password services to the outside world with virtual machines as units. Both solutions have shortcomings. The first type has bottlenecks in the reuse of password equipment. Physical equipment is not convenient for resource reuse and there is an imbalance in resource use. The second type uses the physical and logical isolation technology of virtual machines to achieve password isolation and sharing under multi-tenancy, but virtual resources are fixedly allocated and cannot be dynamically adjusted according to the busyness of business applications. The deployment and operation complexity is also much higher.

[0004] Patent No. CN2022102621472 discloses a cloud-native national secret key management method, which involves the field of information security, including managing the keys of the cloud platform and managing the keys of cloud products. The key management of the cloud platform calls the back-end service to transfer to the underlying node according to the user's business request, calls the Barbican component through the underlying node, and transfers to the KMS service through the Barbican component using the Barbican extension plug-in. The KMS service transfers to different hardware devices adapted to the cryptographic facility to obtain the specified key information to encrypt the business storage data; the key management of the cloud product performs business request message parsing according to the user's business request, performs business logic processing through the integrated SDK package, transfers to the KMS service, and transfers to different hardware devices adapted to the cryptographic facility through the KMS service to obtain the specified key information to encrypt the business application data.

[0005] Patent No. CN2024109390158 discloses a cloud-native cryptographic service high-availability cluster system and implementation method, the system includes a control platform component, an execution node component and a data plane component; the control platform component is used to receive and process leased cryptographic service requests, and send execution cryptographic service instructions to the execution node component; the execution node component is used to receive execution cryptographic service instructions and call the data plane component to implement cryptographic services; the data plane component is used to execute the instructions of the execution node component and complete the cryptographic service through the deployed cryptographic service instance; the cryptographic service management is highly available based on multiple master nodes; the cryptographic service call is highly available based on multiple working nodes. The above invention achieves the following beneficial effects: it solves the high availability problem of cryptographic service management, and also solves the problem of dynamic expansion and reduction of cryptographic service call service nodes, and improves the fault tolerance and stability of cryptographic services in large-scale service call scenarios.

[0006] Although the above patents all use cloud-native methods to solve cryptographic service problems, there are still deficiencies in resource scheduling, service packaging and hardware interface integration, resulting in low resource utilization, slow service response speed, and difficulty in adapting to changing business needs. Summary of the invention

[0007] The purpose of the present invention is to provide a cloud-native cryptographic service method and system, which can ensure the high availability and data security of the service through containerization and k8s resource scheduling, and utilize a comprehensive monitoring system; realize dynamic resource allocation and deep integration of software and hardware for cryptographic services through cloud-native technology, improve resource utilization efficiency and service response speed, simplify the access process of the application system, and improve the convenience of service use, while reducing operation and maintenance costs and management complexity.

[0008] The present invention utilizes the following technical solutions:

[0009] A cloud native cryptographic service method includes the following steps in sequence:

[0010] S1: Virtually split the computing unit and storage unit of the cloud password card to obtain a virtual password card A;

[0011] S2: Bind virtual password card A to container A1 as a high-speed serial computer expansion bus device PCIe;

[0012] S3: encapsulate the service in container A1 to provide the service using the network interface;

[0013] S4: Container A1 sets different parameter configurations according to the service to meet different performance requirements;

[0014] S5: The container management module dynamically schedules the parameter configuration of container A1;

[0015] S6: Container A1 provides a fixed service port to the outside world, and the IP address is dynamically allocated according to the container management module;

[0016] S7: The unified gateway calls the service of container A1 to authenticate the application and performs load balancing on K containers with the same service.

[0017] Preferably, in step S1, the cloud password card is virtually segmented using a hardware accelerated virtualization algorithm to obtain a virtual password card A in the following process:

[0018] S11: define the cloud password card as a physical function module PF of the peripheral device and assign a unique PCIe identifier;

[0019] S12: Create several virtual function devices VF in the physical function module PF and assign unique PCIe identifiers;

[0020] S13: The virtual function device VF shares the physical resources of the peripheral device, thereby obtaining the virtual password card A.

[0021] Preferably, in step S2, the virtual password card A is bound to the container A1; the virtual password card A can be accessed as a virtual function device VF in the container A1, and is independent of the remaining virtual function devices VF.

[0022] Preferably, in step S3, container A1 encapsulates services by calling virtual password card A through remote software development kit SDK; and encapsulates different network interfaces according to the services defined by container A1.

[0023] Preferably, in step S4, parameter configuration includes but is not limited to the number of CPU cores and memory space.

[0024] Preferably, in step S7, the application system calls the unified gateway, and the unified gateway performs application authentication and load balancing; the unified gateway uses a hash algorithm to perform application authentication on the container according to the application identifier Id, the key key and the random number s to obtain an application authentication result value T: T = SM3_HMAC (Id, key, s), SM3_HMAC () represents the hash algorithm; the application system calls the unified gateway to compare the access validity according to the application authentication result value; if the access is valid, it is directly routed to the corresponding service according to the correspondence between the application system and the service; if the access is invalid, the service is denied, and the container management module is used to dynamically reallocate the IP address; the application system has the same calling logic through the hypertext transfer protocol HTTP method and the software development kit SDK method, and unified application authentication is performed by the unified gateway.

[0025] Preferably, in step S7, two containers of the same service may call the same virtual password card or different virtual password cards; if different virtual password cards are called, the keys of the virtual password cards are synchronized for consistency; a matching service in the allocated service resources is selected using a random selection algorithm, a weighted polling algorithm and / or a sequential polling algorithm, and the route is directed to this service to complete load balancing.

[0026] A cloud native cryptographic service system includes a unified gateway, a tenant management module, a container management module, a virtual machine management module, a cryptographic resource scheduling module and a hardware cryptographic device module; wherein:

[0027] Unified gateway, used to provide password service interface for application system; unified gateway includes application authentication and load balancing, and provides HTTP and SDK interface forms;

[0028] The tenant management module is used to manage tenant functions, including tenant application authorization, tenant password service allocation, and tenant resource monitoring.

[0029] Container management module: used to manage container resource orchestration, container monitoring, and container images;

[0030] The virtual machine management module is used to uniformly manage the images, instances and resources of the virtual cryptographic machine;

[0031] A cryptographic resource scheduling module is used to schedule cryptographic resource allocation, cryptographic resource usage, and cryptographic resource security access;

[0032] The hardware cryptographic device module is used for unified monitoring, alarm and calling of traditional cryptographic hardware devices.

[0033] Preferably, the cloud-native cryptographic service system utilizes a multi-layer service unit architecture to meet scalable cryptographic service functions; traditional cryptographic hardware devices include but are not limited to cryptographic cards, cloud cryptographic machines, virtualization resource cards supporting SR-IOV, virtual cryptographic machines, and monitoring systems; the monitoring system is used to monitor the calling process of hardware resources, containers, virtual machines, and keys.

[0034] Preferably, after the container management module deploys containerization technology, resource scheduling and allocation management are performed through k8s; after the virtual machine and hardware resources are bound, the service component calls the virtual cryptographic machine to provide basic cryptographic algorithms and storage functions.

[0035] The present invention uses containerization and k8s resource scheduling; it realizes dynamic resource allocation of cryptographic services and deep integration of software and hardware through cloud native technology; it significantly improves resource utilization efficiency and service response speed, simplifies the access process of the application system, improves the convenience of service use, and greatly reduces operation and maintenance costs and management complexity. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] In order to more clearly illustrate the technical solutions in the embodiments of the present invention or related technologies, the drawings required for use in the embodiments or related technical descriptions are briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying creative work.

[0037] Figure 1 It is a principle block diagram of the operation and maintenance service method;

[0038] Figure 2 This is the framework diagram of the operation and maintenance service system. DETAILED DESCRIPTION

[0039] The present invention is described in detail below with reference to the accompanying drawings and embodiments:

[0040] like Figure 1 As shown, a cloud native cryptographic service method described in the present invention comprises the following steps in sequence:

[0041] S1: Virtually split the computing unit and storage unit of the cloud password card to obtain a virtual password card A;

[0042] In this embodiment, the cloud password card is an ultra-high-speed PCI-E encryption card that supports SR-IOV virtualization technology. It complies with the relevant technical specifications of the National Cryptography Administration on PCI password cards and cloud password cards, and can provide high-speed cryptographic computing services for virtualized resource pool isolation and parallel processing for various cloud cryptographic platforms such as cloud cryptographic machines, meeting their requirements for digital signature / verification, asymmetric / symmetric encryption and decryption, data integrity verification, true random number generation, key generation and management, and ensuring the confidentiality, authenticity, integrity and non-repudiation of sensitive data; it supports up to 32 VFs and can be applied to various application fields such as cloud cryptographic machines and cloud signature verification servers;

[0043] In the present invention, a hardware accelerated virtualization algorithm is used to virtually segment the cloud password card; the process of obtaining the virtual password card A is as follows:

[0044] S11: define the cloud password card as a physical function module PF of the peripheral device and assign a unique PCIe identifier;

[0045] S12: Create several virtual function devices VF in the physical function module PF and assign unique PCIe identifiers;

[0046] S13: The virtual function device VF shares the physical resources of the peripheral device, thereby obtaining the virtual password card A;

[0047] S2: Bind virtual password card A to container A1 as a high-speed serial computer expansion bus device PCIe;

[0048] In the present invention, the virtual password card A is bound to the container A1; the bound virtual card A can be accessed as a certain virtual function device VF in the container A1, and is independent of the remaining virtual function devices VF;

[0049] S3: encapsulate the service in container A1 to provide the service using the network interface;

[0050] In the present invention, container A1 encapsulates services by calling virtual password card A through remote software development kit SDK; and encapsulates different network interfaces according to the services defined by container A1;

[0051] S4: Container A1 sets different parameter configurations according to the service to meet different performance requirements;

[0052] In the present invention, parameter configuration includes but is not limited to the number of CPU cores and memory space;

[0053] S5: The container management module dynamically schedules the parameter configuration of container A1;

[0054] S6: Container A1 provides a fixed service port to the outside world, and the IP address is dynamically allocated according to the container management module;

[0055] S7: The unified gateway calls the service of container A1 to authenticate the application and performs load balancing on K containers with the same service.

[0056] In the present invention, the application system calls the unified gateway, and the unified gateway performs application authentication and load balancing; the unified gateway uses a hash algorithm to perform application authentication on the container according to the application identifier Id, the key key and the random number s to obtain an application authentication result value T: T=SM3_HMAC(Id, key, s), where SM3_HMAC() represents the hash algorithm; the application system calls the unified gateway to compare the access validity according to the application authentication result value; if the access is valid, it is directly routed to the corresponding service according to the corresponding relationship between the application system and the service; if the access is invalid, the service is rejected, and the container management module is used to dynamically reallocate the IP address; the application system has the same calling logic through the hypertext transfer protocol HTTP method and the software development kit SDK method, and both are unified application authentication by the unified gateway;

[0057] In the present invention, two containers of the same service can call the same virtual password card or different virtual password cards; if different virtual password cards are called, the keys of the virtual password cards are synchronized for consistency; a matching service in the allocated service resources is selected by using a random selection algorithm, a weighted polling algorithm and / or a sequential polling algorithm, and the route is directed to this service to complete load balancing;

[0058] Embodiment 1:

[0059] The computing unit and storage unit of the cloud password card are virtually divided by using a hardware accelerated virtualization algorithm to obtain a virtual password card A: the cloud password card is defined as a physical function module PF of a peripheral device and is assigned a unique PCIe identifier; several virtual function devices VF are created in the physical function module PF and are assigned a unique PCIe identifier; the virtual function devices VF share the physical resources of the peripheral device, thereby obtaining a virtual password card A;

[0060] Bind virtual password card A as a high-speed serial computer expansion bus device PCIe to container A1; bind virtual password card A to container A1; in container A1, the bound virtual card A can be accessed as a virtual function device VF, and is independent of the remaining virtual function devices VF; encapsulate services in container A1 (container A1 encapsulates services by calling virtual password card A through a remote software development kit SDK; and encapsulates different network interfaces according to the services defined in container A1) to provide services using network interfaces;

[0061] Container A1 sets different parameter configurations according to the service, such as the number of CPU cores and memory space, to meet different performance requirements; the container management module dynamically schedules the parameter configuration of container A1; container A1 provides a fixed service port to the outside world, and the IP address is dynamically allocated according to the container management module; the unified gateway calls the service of container A1 for application authentication and performs load balancing on K containers with the same service; the application system calls the unified gateway, which performs application authentication and load balancing; the unified gateway uses a hash algorithm to authenticate the container application based on the application identifier Id, the key key and the random number s to obtain the application authentication result value T: T = SM3_HMAC(Id, key, s), SM3_HMAC() Represents a hash algorithm; the application system calls the unified gateway to compare the access validity based on the application authentication result value; if the access is valid, it is directly routed to the corresponding service based on the correspondence between the application system and the service; the application system has the same calling logic through the Hypertext Transfer Protocol HTTP method and the Software Development Kit SDK method, and both are authenticated by the unified gateway; two containers of the same service can call the same virtual password card or different virtual password cards; if different virtual password cards are called, the keys of the virtual password cards are synchronized for consistency; a matching service in the allocated service resources is selected using a random selection algorithm, a weighted polling algorithm, and / or a sequential polling algorithm, and the route is directed to this service to complete load balancing.

[0062] like Figure 2 As shown, a cloud native cryptographic service system includes a unified gateway, a tenant management module, a container management module, a virtual machine management module, a cryptographic resource scheduling module and a hardware cryptographic device module; wherein,

[0063] Unified gateway, used to provide password service interface for application system; unified gateway includes application authentication and load balancing, and provides HTTP and SDK interface forms;

[0064] The tenant management module is used to manage tenant functions, including tenant application authorization, tenant password service allocation, and tenant resource monitoring.

[0065] Container management module: used to manage container resource orchestration, container monitoring, and container images;

[0066] In the present invention, after the container management module deploys the containerization technology, resource scheduling and allocation management are performed through k8s; after the virtual machine and hardware resources are bound, the service component calls the virtual cryptographic machine to provide basic cryptographic algorithms and storage functions;

[0067] The virtual machine management module is used to uniformly manage the images, instances and resources of the virtual cryptographic machine;

[0068] A cryptographic resource scheduling module is used to schedule cryptographic resource allocation, cryptographic resource usage, and cryptographic resource security access;

[0069] Hardware cryptographic device module, used for unified monitoring, alarm and calling of traditional cryptographic hardware devices;

[0070] In the present invention, traditional cryptographic hardware devices include but are not limited to cryptographic cards, cloud cryptographic machines, virtualized resource cards supporting SR-IOV, virtual cryptographic machines, and monitoring systems; the monitoring system is used to monitor the calling process of hardware resources, containers, virtual machines, and keys;

[0071] In the present invention, the cloud-native cryptographic service system utilizes a multi-layer service unit architecture to meet scalable cryptographic service functions;

[0072] (1) Architecture design: Build a multi-layer service unit architecture, including unified gateway, tenant management and other modules, to ensure the coordination between modules;

[0073] (2) Containerized deployment: Encapsulate cryptographic services through containers and use container technologies such as Docker to achieve rapid deployment of services;

[0074] (3) Resource scheduling and allocation: Kubernetes dynamically schedules container resources and adjusts resource allocation in real time based on tenant demand and service load conditions:

[0075] (4) Hardware resource abstraction and integration: encapsulate the service capabilities of hardware cryptographic devices and virtualized cryptographic cards, and provide a unified calling interface;

[0076] (5) Provide a password service interface to the application system through a unified gateway, supporting both HTTP and SDK access methods;

[0077] (6) Monitoring system implementation: Establish a comprehensive monitoring system to provide real-time monitoring and alarm for the use of hardware resources, containers, virtual machines, and keys.

Claims

1. A cloud-native cryptographic service method, characterized in that: The following steps are included in sequence: S1: Virtually split the computing unit and storage unit of the cloud password card to obtain a virtual password card A; S2: Bind virtual password card A to container A1 as a high-speed serial computer expansion bus device PCIe; S3: encapsulate the service in container A1 to provide the service using the network interface; S4: Container A1 sets different parameter configurations according to the service to meet different performance requirements; S5: The container management module dynamically schedules the parameter configuration of container A1; S6: Container A1 provides a fixed service port to the outside world, and the IP address is dynamically allocated according to the container management module; S7: The unified gateway calls the service of container A1 to authenticate the application and performs load balancing on K containers with the same service.

2. The cloud-native cryptographic service method according to claim 1, characterized in that: In step S1, the cloud password card is virtually segmented using a hardware accelerated virtualization algorithm to obtain a virtual password card A. The process is as follows: S11: define the cloud password card as a physical function module PF of the peripheral device and assign a unique PCIe identifier; S12: Create several virtual function devices VF in the physical function module PF and assign unique PCIe identifiers; S13: The virtual function device VF shares the physical resources of the peripheral device, thereby obtaining the virtual password card A.

3. The cloud-native cryptographic service method according to claim 1, characterized in that: In the step S2, the virtual password card A is bound to the container A1; the virtual password card A can be accessed as a virtual function device VF in the container A1 and is independent of the remaining virtual function devices VF.

4. The cloud-native cryptographic service method according to claim 1, characterized in that: In step S3, container A1 encapsulates services by calling virtual password card A through remote software development kit SDK; and encapsulates different network interfaces according to the services defined by container A1.

5. The cloud-native cryptographic service method according to claim 1, characterized in that: In step S4, parameter configuration includes but is not limited to the number of CPU cores and memory space.

6. The cloud-native cryptographic service method according to claim 1, characterized in that: In step S7, the application system calls the unified gateway, and the unified gateway performs application authentication and load balancing; The unified gateway uses a hash algorithm to authenticate the container based on the application identifier Id, the key key, and the random number s to obtain an application authentication result value T: T = SM3_HMAC (Id, key, s), where SM3_HMAC() represents a hash algorithm; The application system calls the unified gateway to compare the access validity based on the application authentication result value; if the access is valid, it is directly routed to the corresponding service based on the correspondence between the application system and the service; if the access is invalid, the service is denied, and the container management module is used to dynamically reallocate the IP address; the application system has the same calling logic through the Hypertext Transfer Protocol HTTP method and the Software Development Kit SDK method, and both are authenticated by the unified gateway.

7. The cloud-native cryptographic service method according to claim 1, characterized in that: In step S7, two containers of the same service may call the same virtual password card or different virtual password cards; if different virtual password cards are called, the keys of the virtual password cards are synchronized for consistency; a matching service in the allocated service resources is selected by using a random selection algorithm, a weighted polling algorithm and / or a sequential polling algorithm, and the route is directed to this service to complete load balancing.

8. A cloud-native cryptographic service system according to any one of claims 1 to 7, characterized in that: It includes a unified gateway, a tenant management module, a container management module, a virtual machine management module, a cryptographic resource scheduling module and a hardware cryptographic device module; among which, Unified gateway, used to provide password service interface for application system; unified gateway includes application authentication and load balancing, and provides HTTP and SDK interface forms; The tenant management module is used to manage tenant functions, including tenant application authorization, tenant password service allocation, and tenant resource monitoring. Container management module: used to manage container resource orchestration, container monitoring, and container images; The virtual machine management module is used to uniformly manage the images, instances and resources of the virtual cryptographic machine; A cryptographic resource scheduling module is used to schedule cryptographic resource allocation, cryptographic resource usage, and cryptographic resource security access; The hardware cryptographic device module is used for unified monitoring, alarm and calling of traditional cryptographic hardware devices.

9. The cloud-native cryptographic service system according to claim 8, characterized in that: The cloud-native cryptographic service system utilizes a multi-layer service unit architecture to meet scalable cryptographic service functions; traditional cryptographic hardware devices include but are not limited to cryptographic cards, cloud cryptographic machines, virtualized resource cards supporting SR-IOV, virtual cryptographic machines, and monitoring systems; the monitoring system is used to monitor the calling process of hardware resources, containers, virtual machines, and keys.

10. The cloud-native cryptographic service system according to claim 8, characterized in that: After the container management module is deployed with containerization technology, resource scheduling and allocation management are performed through k8s; after the virtual machine and hardware resources are bound, the service component calls the virtual cryptographic machine to provide basic cryptographic algorithms and storage functions.

Citation Information

Patent Citations

  • Method for generating full dynamic password of multi-service system

    CN107528844A

  • Virtual card system and adaptive virtual card method

    CN113207116A

  • Virtualized cloud password service system based on channel isolation and implementation method thereof

    CN113949551A

  • Cloud password service platform based on OAuth authentication and password resource allocation method

    CN115086015A

  • Multi-tenant isolated password resource automatic scheduling system and method in cloud environment

    CN117319212A