Federal Cluster Identifier Mapping and National Cryptographic Security Access Method and Device
By generating federated node identifiers and national cryptographic security authentication, combined with dynamic trust scoring and version vector synchronization, the problems of inconsistent cross-architecture identifiers, weak security access, and high performance overhead in federated learning are solved, achieving unified and efficient synchronization of cross-architecture identifier management and security access.
Patent Information
- Application Number
- CN202611247247.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-08-17
- Publication Date
- 2026-11-17
AI Technical Summary
Existing federated learning suffers from problems such as inconsistent cross-architecture identifiers, weak secure access, difficulty in adapting to heterogeneous environments, and high performance overhead. In particular, it is difficult to achieve effective identifier management and security authentication in heterogeneous hardware and operating system environments.
By generating federated node identifiers, combining device certificates and dynamic tokens for national cryptographic security authentication, and using dynamic trust scores and version vectors for synchronization, a unified identifier, secure encrypted channel, and lightweight synchronization mechanism are established to achieve cross-architecture identifier management and secure access.
It achieves unified description and automatic generation of identifiers across architecture environments, improving security, defending against man-in-the-middle attacks, reducing network traffic and latency, and improving overall performance.
Smart Images

Figure CN123122891A_ABST
Abstract
Description
Technical Field
[0001] The embodiments of the present invention relate to the fields of multi-cluster federation management and information security technology, and in particular to a federation cluster identifier mapping and national cryptographic security access method and device. Background Technology
[0002] Federated learning has become a core technical framework for cross-institutional data collaboration. The participating parties (hereinafter referred to as "federated nodes") run different operating systems (CentOS, Ubuntu, Kylin, UOS), use different container orchestration platforms (Kubernetes, K3s, OpenShift), and have inconsistent hardware architectures (x86, ARM, Kunpeng, Hygon, Phytium). Federated nodes must identify and authenticate each other to ensure that the data used for federated training is not contaminated and that communication is not hijacked. However, existing identifier management schemes for federated learning generally have four problems: (a) Inconsistent cross-architecture identification: Different clusters maintain their own node identifiers, and there is no unified mapping across clusters. The same physical node has different identifiers in different clusters, and the federated coordination nodes cannot construct a globally consistent identity view.
[0003] (b) Weak security access: Most solutions use static keys (pre-shared keys) or basic TLS one-way authentication, which cannot withstand the continuous verification required by the Zero Trust model and cannot prevent man-in-the-middle attacks, identity forgery and credential replay.
[0004] (c) Difficulty in adapting to heterogeneous environments: The existing solution is designed with a single technology stack (x86 + Kubernetes standard distribution), which makes it difficult to deploy flexibly in the domestic IT innovation environment (ARM / Kunpeng / Hygon / Phytium + Kylin / UOS + K3s / OpenShift).
[0005] (d) High performance overhead: Node identifiers are synchronized using full synchronization or Gossip broadcasting, resulting in high bandwidth and latency at scales of 100+ nodes. The lack of hardware acceleration for cryptographic operations further slows down overall performance. Summary of the Invention
[0006] To address the aforementioned technical problems, embodiments of the present invention provide a method for federated cluster identifier mapping and national cryptographic security access, comprising: The federated node combines its original identification information with a predefined CEL expression template to form a federated node identifier, which has an auto-incrementing identification version number; The federated node and the federated control plane implement national cryptographic security authentication based on encrypted device certificates and dynamic tokens generated by the federated control plane. If the national cryptographic security certification is passed and the dynamic trust score of the federal node determined by the federal control plane meets the preset threshold requirements, the federal node reports an identifier registration request to the federal control plane based on the federal node identifier. If the federated node identifier is verified, the federated control plane registers the federated node identifier and the original identification information to a preset mapping table; The federal control plane distributes the mapping table in the registered federal node cluster; In response to the triggering of a preset synchronization condition, the federation node sends the version vector of the mapping table maintained locally by the corresponding federation node to the federation control plane. The synchronization condition represents a version vector incremental synchronization event. The federated node receives the incremental data packet issued by the federated control plane and updates its local mapping table based on the incremental data packet. The incremental data packet is data generated by the federated control plane based on the version vector and the mapping table when the global current version number of the mapping table has a version number greater than the version number corresponding to the version vector.
[0007] In one embodiment, the federated node processes its original identification information in conjunction with a predefined CEL expression template to form a federated node identifier, including the following: Collect the original identification information; The extended attribute set of the federation node is generated based on the CEL expression template; The federated node identifier is generated based on the CEL expression, the original identification information, and the extended attribute set.
[0008] In one embodiment, national cryptographic security authentication with the federal control plane is implemented based on the encrypted device certificate, including: The federation node signs the first random number, the first timestamp, and the federation node identifier based on its local private key to obtain the first signature; The federation node generates an authentication request based on the first signature, device certificate, first timestamp, and federation node identifier. The federated node sends the authentication request to the federated control plane; The federal control plane verifies each parameter in the authentication request.
[0009] In one embodiment, national cryptographic security authentication with the federal control plane is achieved based on a dynamic token generated by the encrypted federal control plane, including: After the national cryptographic security certification based on the device certificate is passed, the federated node establishes a temporary secure channel with the federated control plane; The federated node obtains a dynamic token generated by the federated control plane using a shared key, a session identifier, a second random number, and a second timestamp through the temporary secure channel. The federated node decrypts the dynamic token based on the shared key stored locally to determine the second timestamp; The federated node calculates the expected token value based on the shared key, session identifier, and second timestamp; The federation node generates a confirmation token based on the expected token value and the dynamic token; The federation node sends the confirmation token to the federation control plane through the temporary security channel; The federal control plane verifies the confirmation token.
[0010] In one embodiment, the dynamic trust score of the federated node determined by the federated control plane meets a preset threshold requirement, including the following: The behavior score is determined based on the success rate and abnormal request rate of the national cryptographic security authentication of the federated nodes in the first time period. The request frequency score is determined based on the deviation between the number of national cryptographic security authentication requests made by the federated node in the second time period and the historical baseline. A certificate validity score is determined based on the validity of the device certificates of the federated nodes; The certificate revocation status score is determined based on the revocation status of the device certificate of the federated node; The dynamic trust score of the federation node is obtained by weighting and summing the behavior score, request frequency score, certificate validity score, and revocation status score together with preset weights. When the dynamic trust score is not less than a preset threshold, the dynamic trust score meets the preset threshold requirement.
[0011] In one embodiment, the method further includes: If the national cryptographic security authentication is passed and the dynamic trust score of the federated node determined by the federated control plane meets the preset threshold requirements, the federated node derives a session master key based on the session identifier generated during the national cryptographic security authentication process. The federated node derives a session encryption key and a session MAC key based on the session master key; The federated node constructs an encrypted channel between itself and the federated control plane based on the national cryptographic algorithm. The encrypted channel is used for communication between the federated node and the federated control plane. In response to the triggering of the key rotation cycle, the federated node, based on the current session encryption key and session MAC key, encrypts and transmits a new session encryption key and session MAC key to the federated control plane through the encryption channel.
[0012] In one embodiment, the identifier registration request includes a federated node identifier, the original identifier information federated node cluster name, and a third timestamp; The step of registering the federal node identifier and its original identification information to a preset mapping table by the federal control plane, upon successful verification of the federal node identifier, includes: If the federal control plane verifies all parameters of the identifier registration request and it passes the verification, the federal node identifier and the original identifier information are written into a preset mapping table, and a confirmation response is returned to the federal node.
[0013] In one embodiment, the method further includes: In response to the triggering of a preset synchronization condition, the federated node constructs a version vector corresponding to the mapping table maintained locally by the federated node, using the federated node identifier as the key and the version number of the federated node identifier as the value. The federated node receives incremental data packets issued by the federated control plane and updates its local mapping table based on the incremental data packets, including: The federal control plane combines the version vector to traverse the locally maintained mapping table and counts the target federal node identifiers and their corresponding version number increments in the locally maintained mapping table whose version number is greater than the version number of the corresponding federal node identifier in the version vector. The incremental data packet is generated based on the target federation node identifier and the corresponding version number increment, and then returned to the federation node; The federated node receives the incremental data packet and updates the mapping table maintained locally by the federated node accordingly.
[0014] In one embodiment, the method further includes: When the federal control plane detects a conflicting node with conflicting information in its locally maintained mapping table, it determines the registration mode of the conflicting node. The registration mode includes an automatic mode in which the federal control plane automatically completes the registration and a non-automatic mode in which the federal control plane completes the registration according to the user's instructions. The conflicting node is a federal node recorded in the mapping table. If all the conflicting nodes are registered in automatic mode, the federal control plane will retain the conflicting nodes that have completed registration first in the mapping table. If the registration mode of the conflicting node involves a non-automatic mode, the federated control plane generates a conflict event and sends it to a manual processing queue.
[0015] Another embodiment of the present invention also provides a federated cluster identifier mapping and national cryptographic security access device, including federated nodes and a federated control plane, wherein: The federated node combines its original identification information with a predefined CEL expression template to form a federated node identifier, which has an auto-incrementing identification version number; The federated node and the federated control plane implement national cryptographic security authentication based on encrypted device certificates and dynamic tokens generated by the federated control plane. If the national cryptographic security certification is passed and the dynamic trust score of the federal node determined by the federal control plane meets the preset threshold requirements, the federal node reports an identifier registration request to the federal control plane based on the federal node identifier. If the federated node identifier is verified, the federated control plane registers the federated node identifier and the original identification information to a preset mapping table; The federal control plane distributes the mapping table in the registered federal node cluster; In response to the triggering of a preset synchronization condition, the federation node sends the version vector of the mapping table maintained locally by the corresponding federation node to the federation control plane. The synchronization condition represents a version vector incremental synchronization event. The federated node receives the incremental data packet issued by the federated control plane and updates its local mapping table based on the incremental data packet. The incremental data packet is data generated by the federated control plane based on the version vector and the mapping table when the global current version number of the mapping table has a version number greater than the version number corresponding to the version vector.
[0016] Based on the solutions disclosed in the above embodiments, it is evident that by establishing a technical architecture of "unified identifier generation, national cryptographic security channel first, and interactive requests within the encrypted channel," the identifier management challenge of heterogeneous federated clusters is addressed collaboratively from three dimensions: the identifier layer, the security layer, and the synchronization layer. At the identifier layer, a unified description of heterogeneous node attributes and automatic generation of federated node identifiers are achieved based on a general expression language template, eliminating cross-architecture identifier silos. At the security layer, two-factor authentication using device certificates and dynamic tokens, along with dynamic trust scoring of federated nodes, enables zero-trust continuous verification of federated nodes, significantly improving security and effectively defending against man-in-the-middle attacks, identifier spoofing, and session token replay attacks. At the synchronization layer, incremental synchronization using version vectors enables lightweight propagation of identifier changes, significantly reducing network traffic and latency compared to full synchronization at multi-node scales.
[0017] Other features and advantages of this application will be set forth in the following description. The objectives and other advantages of this application can be realized and obtained through the structures particularly pointed out in the written description and drawings.
[0018] The technical solution of this application will be further described in detail below with reference to the accompanying drawings and embodiments. Attached Figure Description
[0019] To more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the specific embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.
[0020] Figure 1 This is a flowchart illustrating the federal cluster identifier mapping and national cryptographic security access method in an embodiment of the present invention.
[0021] Figure 2 This is a flowchart illustrating the federal cluster identifier mapping and national cryptographic security access method in another embodiment of the present invention.
[0022] Figure 3 This is a structural block diagram of the federated cluster identifier mapping and national cryptographic security access device in an embodiment of the present invention. Detailed Implementation
[0023] The specific embodiments of the present invention will now be described in detail with reference to the accompanying drawings, but these are not intended to limit the scope of the invention.
[0024] It should be understood that various modifications can be made to the embodiments disclosed herein. Therefore, the following description should not be considered as limiting, but merely as an example of embodiments. Other modifications within the scope of this disclosure will be apparent to those skilled in the art.
[0025] The accompanying drawings, which are included in and form part of this specification, illustrate embodiments of the present disclosure and, together with the general description of the disclosure given above and the detailed description of the embodiments given below, serve to explain the principles of the disclosure.
[0026] These and other features of the invention will become apparent from the following description of preferred forms of embodiments given as non-limiting examples, with reference to the accompanying drawings.
[0027] It should also be understood that although the invention has been described with reference to some specific examples, those skilled in the art can certainly implement many other equivalent forms of the invention.
[0028] The above and other aspects, features and advantages of this disclosure will become more apparent when taken in conjunction with the accompanying drawings and in view of the following detailed description.
[0029] Specific embodiments of the present disclosure are described thereafter with reference to the accompanying drawings; however, it should be understood that the disclosed embodiments are merely examples of the present disclosure and can be implemented in various ways. Well-known and / or repeated functions and structures are not described in detail to avoid unnecessary or redundant details that could obscure the present disclosure. Therefore, the specific structural and functional details disclosed herein are not intended to be limiting, but are merely representative of the present disclosure and are intended to teach those skilled in the art to use the present disclosure in a variety of substantially any suitable detailed structures.
[0030] This specification may use the phrases “in one embodiment,” “in another embodiment,” “in yet another embodiment,” or “in still another embodiment,” all of which may refer to one or more of the same or different embodiments according to this disclosure.
[0031] The embodiments of the present invention will now be described in detail with reference to the accompanying drawings.
[0032] like Figure 1 As shown, this embodiment of the invention provides a method for federal cluster identifier mapping and national cryptographic security access, including: S1: The federated node processes its original identification information by combining it with a predefined CEL expression template to form a federated node identifier, which has an auto-incrementing identification version number; S2: The federation node and the federation control plane implement national cryptographic security authentication based on the encrypted device certificate and the dynamic token generated by the federation control plane; S3: When the national cryptographic security certification is passed and the dynamic trust score of the federated node determined by the federated control plane meets the preset threshold requirement, the federated node reports an identifier registration request to the federated control plane based on the federated node identifier. S4: If the federated node identifier is verified, the federated control plane registers the federated node identifier and the original identification information to a preset mapping table; S5: The federated control plane distributes the mapping table in the registered federated node cluster; S6: In response to the triggering of a preset synchronization condition, the federation node sends the version vector of the mapping table maintained locally by the corresponding federation node to the federation control plane, whereby the synchronization condition represents a version vector incremental synchronization event. S7: The federated node receives the incremental data packet issued by the federated control plane and updates the local mapping table based on the incremental data packet. The incremental data packet is data generated by the federated control plane based on the version vector and the mapping table when the global current version number of the mapping table has a version number greater than the version number corresponding to the version vector.
[0033] This embodiment is applied to a federated cluster environment, which includes a federated control plane and multiple federated nodes. The federated control plane is deployed in an independent management cluster, and node agents are deployed on each federated node. The node agents serve as the sole communication agents for the federated nodes in the federated network and are deployed on each federated node in the form of Kubernetes DaemonSet.
[0034] The solution in this embodiment, according to the data processing flow, includes: collecting the original identification information of each federation node, converting it into a unified format, and generating a federation node identifier; registering the federation node identifier to a preset global mapping table, and performing incremental synchronization through version vectors; performing national cryptographic two-factor authentication on the federation node, and establishing an encrypted communication channel.
[0035] In one embodiment, the federated node processes its original identification information in conjunction with a predefined CEL expression template to form a federated node identifier, including the following: S101: Collect the original identification information; S102: Generate the extended attribute set of the federation node based on the CEL expression template; S103: Generate the federated node identifier based on the CEL expression, the original identification information, and the extended attribute set.
[0036] For example, the node agent of each federated node collects the original identification attribute information of its own node from the local operating environment of each federated node at a preset period. The preset period is 30 seconds by default, and can be adjusted through configuration. The original identification attribute information includes, but is not limited to: node universal unique identifier (UUID), CPU architecture type, CPU vendor information, operating system type, operating system version, kernel version, hostname, container runtime type, container runtime version, cluster API server address, cluster name, and network domain. Supported operating systems include, but are not limited to, CentOS 7 / 8, Ubuntu 20.04 / 22.04 / 24.04, Kylin V10, and UOS V20; supported container platforms include, but are not limited to, Kubernetes 1.22 and above, K3s 1.24 and above, and OpenShift 4.10 and above.
[0037] The node agent loads a predefined Common Expression Language (CEL) expression template, uses the collected original identifier attribute information as input variables to perform CEL expression parsing, and generates a standardized Federation Node Identifier (FNI). The CEL expression template is mounted in the node agent container as a Kubernetes ConfigMap, supporting runtime hot reloading by monitoring file changes through the inotify mechanism. When adding a heterogeneous platform, only the corresponding CEL template configuration entry needs to be added to the ConfigMap; no modification to the core code is required.
[0038] For example, the FNI format is a string formed by concatenating the node UUID, cluster name, platform type, and architecture type in a preset order, specifically in the format "node UUID.cluster name.platform type.architecture type". For instance, when the node UUID is "a1b2c3d4", the cluster name is "karmada-cluster-01", the platform type is "k8s", and the architecture type is "arm64", the generated FNI is "a1b2c3d4.karmada-cluster-01.k8s.arm64".
[0039] Meanwhile, the node agent generates an extended attribute set according to the CEL expression template. The extended attribute set includes at least the operating system version, container runtime type and version, kernel version, and network domain.
[0040] The node agent maintains an auto-incrementing identifier version number for the FNI, which is an unsigned 64-bit integer with an initial value of 1. The identifier version number is automatically incremented by 1 when any of the following events occur: (a) node attribute changes, including container runtime upgrades, operating system patch updates, etc.; (b) node re-registration; (c) identifier remapping caused by a mapping policy change. The identifier version number is simultaneously written to the node's local embedded database and the control plane's etcd to ensure that the version number is not lost after the node agent restarts.
[0041] Before a federated node establishes a communication connection with the federated control plane, or before a direct communication connection is established between federated nodes, it is necessary to perform Chinese cryptographic two-factor authentication and establish a Chinese cryptographic transport layer security (mTLS) encrypted channel.
[0042] In one embodiment, for a new federated node joining the cluster for the first time, the federated node has pre-obtained an (SM2) device certificate (such as an SM2 device certificate) and a shared secret distributed by the administrator via an out-of-band channel (including the cloud platform console or manual configuration). The shared secret may be, but is not limited to, a 256-bit key. After the new federated node starts up, it first performs national cryptographic two-factor authentication. After successful authentication and the establishment of an encrypted channel, it then performs subsequent identifier reporting and registration steps through the encrypted channel. For registered federated nodes, they reuse the established encrypted channel during normal communication, and only re-execute the authentication process in this step when the connection is disconnected and rebuilt, the session key rotation fails and rollback occurs, or the node recovers from a degraded mode.
[0043] The two-factor authentication includes two stages: a first factor and a second factor. In one embodiment, national cryptographic security authentication with the federal control plane is implemented based on the encrypted device certificate, including: S201: The federation node signs the first random number, the first timestamp, and the federation node identifier based on its local private key to obtain the first signature; S202: The federation node generates an authentication request based on the first signature, device certificate, first timestamp, and federation node identifier; S203: The federated node sends the authentication request to the federated control plane; S204: The federal control plane verifies each parameter in the authentication request.
[0044] For example, the requesting federated node generates a first random number and signs data containing the first random number, a first timestamp, and its own FNI using its SM2 private key. The signed result (first signature), the device certificate, the first random number, the first timestamp, and the FNI are then packaged to generate an authentication request, which is sent to the verifying party. In this embodiment, the verifying party is the federated control plane, but it could also be other target federated nodes.
[0045] Upon receiving the authentication request, the verifier can perform the following verification operations: (a) check whether the deviation between the first timestamp and the local time is within the allowed range, which is ±300 seconds by default (the exact range is not fixed), to defend against clock deviation and replay attacks; (b) extract the public key from the device certificate and verify the legality of the signature using the SM2 signature verification algorithm; (c) query the local certificate revocation list to confirm that the device certificate has not been revoked and has not expired. If all the above verifications pass, the second factor verification will proceed. If any verification fails, the connection will be immediately rejected and a security audit log will be recorded.
[0046] After completing the national cryptographic security certification based on the device certificate, the second factor of the national cryptographic security certification will be implemented.
[0047] Based on a dynamic token generated by the encrypted federal control plane, national cryptographic security authentication with the federal control plane is implemented, including: S205: After the national cryptographic security authentication based on the device certificate is passed, the federated node establishes a temporary secure channel with the federated control plane; S206: The federated node obtains a dynamic token generated by the federated control plane using a shared key, a session identifier, a second random number, and a second timestamp through the temporary secure channel; S207: The federated node decrypts the dynamic token based on the shared key stored locally to determine the second timestamp; S208: The federated node calculates the expected token value based on the shared key, session identifier, and second timestamp; S209: The federation node generates a confirmation token based on the expected token value and the dynamic token; S230: The federation node sends the confirmation token to the federation control plane through the temporary security channel; S231: The federal control plane verifies the confirmation token.
[0048] For example, after the national cryptographic security authentication based on the device certificate is passed, the federated node establishes a temporary secure channel with the federated control plane. Then, the verifier generates a session identifier and calculates a dynamic token using the HMAC-SM3 algorithm with a pre-shared key. The input to the dynamic token includes at least the second random number sent by the requester, the session identifier, and the second timestamp. The verifier returns the dynamic token and session identifier to the requester's federated node through the temporary secure channel.
[0049] After receiving the dynamic token and session identifier, the requesting federated node decrypts them using the pre-shared key stored locally. It then independently calculates the expected token value using the decryption result and the shared key, and compares it with the received dynamic token. If they match, the requesting federated node generates a confirmation token based on the expected token value and the dynamic token, and returns it to the verifier for verification. For example, the confirmation token is the HMAC-SM3 calculation result using the dynamic token and the session identifier as input. Upon receiving the confirmation token, the verifier verifies the expected value calculated locally. If verification is successful, the verifier binds the session identifier to the requesting federated node and writes it to the session cache. The default lifespan of the session cache is 5 minutes (configurable), and a session identifier in the format "fed-session-session identifier" is generated.
[0050] In one embodiment, such as Figure 2As shown, the dynamic trust score of the federated node determined by the federated control plane meets the preset threshold requirement, including the following: S301: Determine a behavior score based on the success rate and abnormal request rate of the national cryptographic security authentication of the federated node in the first time period; S302: Determine the request frequency score based on the deviation between the number of national cryptographic security authentication requests made by the federated node in the second time period and the historical baseline; S303: Determine the certificate validity score based on the validity of the device certificate of the federated node; S304: Determine the certificate revocation status score based on the revocation status of the device certificate of the federated node; S305: Combine the behavior score, request frequency score, certificate validity score, and revocation status score with preset weights and perform a weighted summation to obtain the dynamic trust score of the federation node; S306: When the dynamic trust score is not less than a preset threshold, the dynamic trust score meets the preset threshold requirement.
[0051] For example, the federal control plane calculates a dynamic trust score for the requesting federated node for each communication request. This dynamic trust score uses a weighted multi-factor model, with a total score from 0 to 100, and is calculated by weighting the following four factors: (a) Behavioral score, with a weight of 30% in this embodiment. Behavioral score = (Number of successful authentications / Total number of authentication attempts) 50 + (1 - number of abnormal requests / total number of requests) 50. Abnormal requests include: authentication requests with failed signature verification, requests with timestamp deviations exceeding ±300 seconds, requests initiated by nodes whose certificates have been revoked, and requests whose session tokens have expired or been replayed. The statistics window is the most recent 30 days. When the total number of authentication attempts is less than the minimum statistical count of 10, the behavior score uses the default value of 50 points.
[0052] (b) Certificate validity score, which has a weight of 25% in this embodiment. If the certificate has expired, the certificate validity score is 0; if the remaining valid days of the certificate are greater than or equal to 30 days, the certificate validity score is 100; if the remaining valid days of the certificate are less than 30 days, the certificate validity score is the remaining valid days divided by 30 and then multiplied by 100.
[0053] (c) Certificate revocation status score, with a weight of 25% in this embodiment. If the certificate is in the certificate revocation list, the certificate revocation status score is 0; if the certificate is not in the certificate revocation list but the certificate revocation list was last updated more than 7 days ago, the certificate revocation status score is 50; if the certificate is not in the certificate revocation list and the certificate revocation list is the latest (updated no more than 7 days ago), the certificate revocation status score is 100.
[0054] (d) Request frequency score, with a weight of 20% in this embodiment. The number of authentication requests in the most recent minute is calculated, with the baseline value being the P95 value of the historical 1-minute window average number of requests for the federated node. If the number of requests in the most recent minute does not exceed the baseline value, the request frequency score is 100; if the number of requests in the most recent minute exceeds the baseline value but does not exceed twice the baseline value, the request frequency score is 100 - 50. (Number of requests in the last minute - Limit value) / Baseline value); If the number of requests in the last minute exceeds twice the baseline value, the request frequency score is 0 and a rate limiting alarm is triggered.
[0055] The above scores are weighted and summed: the dynamic trust score equals 0.3 multiplied by the behavior score, 0.25 multiplied by the certificate validity score, 0.25 multiplied by the certificate revocation status score, and 0.2 multiplied by the request frequency score. If the overall trust score is greater than or equal to 60, access is allowed; if the overall trust score is less than 60, access is denied and recorded in the security audit log. The trust score result is written to Prometheus metrics in real time for monitoring, display, and alerting.
[0056] Furthermore, the method also includes: S307: When the national cryptographic security authentication is passed and the dynamic trust score of the federation node determined by the federation control plane meets the preset threshold requirement, the federation node derives a session master key based on the session identifier generated during the national cryptographic security authentication process. S308: The federated node derives a session encryption key and a session MAC key based on the session master key; S309: The federated node constructs an encrypted channel between the federated node and the federated control plane based on the national cryptographic algorithm. The encrypted channel is used for communication between the federated node and the federated control plane. S310: In response to the triggering of the key rotation cycle, the federated node, based on the current session encryption key and session MAC key, encrypts and transmits a new session encryption key and session MAC key to the federated control plane through the encryption channel.
[0057] For example, after passing the national cryptographic security authentication and the dynamic trust score of the federated node determined by the federated control plane meets the preset threshold requirements, both parties use the session identifier to enter the encrypted channel establishment phase. Specifically, both parties negotiate the national cryptographic suite and try the following suites in order of priority (not limited to the following suites): TLS_ECC_SM4_SM3, TLS_ECC_SM2_WITH_SM4_SM3, and TLS_ECDHE_SM2_WITH_SM4_SM3. Then, the session master key is derived using the session identifier negotiated in the two-factor authentication and the public and private key pairs of both parties. The session master key can be derived, but is not limited to, through the SM2 key exchange algorithm combined with the session identifier. Afterward, the session encryption key and session MAC key are derived from the session master key. The session encryption key can be, but is not limited to, 128 bits, and the session MAC key can be derived from the session master key through the SM4 key derivation function. Finally, both parties use the derived session encryption key and session MAC key to establish an mTLS encrypted channel based on the negotiated national cryptographic suite for subsequent communication interactions.
[0058] In this embodiment, SM2 signing, SM3 hashing, and SM4 encryption / decryption operations are preferentially executed at the hardware level by calling the KAE hardware acceleration card through the PKCS#11 standard interface. The KAE hardware acceleration card includes an SM2 asymmetric cryptographic engine, an SM3 hash cryptographic engine, and an SM4 symmetric cryptographic engine. When the KAE hardware acceleration is detected to be unavailable, it automatically downgrades to a pure software implementation of GmSSL v3.0, optimized for multi-threaded parallelism through OpenMP, with SM4 using CTR mode to support parallel encryption and decryption.
[0059] In this embodiment, after the encrypted channel is established, the session encryption key and session MAC key are automatically rotated once every preset rotation period. The preset rotation period is 60 minutes by default, but can be configured. During rotation, the federated control plane generates new temporary key material, encrypts the new key material using the currently valid old session key, and sends the key rotation message to the federated node through the established encrypted channel. The federated node receives and decrypts the key rotation message, extracts the new key material, re-executes the SM2 key exchange to derive a new session key, and returns an acknowledgment message to the control plane. Both parties synchronously switch to the new session key, and existing communication is not interrupted during the rotation process. If the federated control plane does not receive the acknowledgment message within a preset timeout period, it reverts to re-executing the complete two-factor authentication handshake process.
[0060] Furthermore, after the national cryptographic mTLS encrypted channel is established, the federated node reports an identifier registration request to the federated control plane through the encrypted channel. The node agent sends the identifier registration request to the federated control plane via gRPC one-way remote procedure call (Unary RPC). In this embodiment, the identifier registration request includes at least the FNI, the identifier version number, the original attribute key-value pair, the cluster name, and a third timestamp.
[0061] The step of registering the federal node identifier and its original identification information to a preset mapping table by the federal control plane, upon successful verification of the federal node identifier, includes: S401: If the federal control plane verifies all parameters of the identifier registration request and passes the verification, the federal node identifier and the original identifier information are written into a preset mapping table, and a confirmation response is returned to the federal node.
[0062] For example, after receiving the identifier registration request, the federal control plane performs the following verification operations: (a) verifying whether the FNI format is valid; (b) verifying whether the deviation between the timestamp and the local time is within the allowed range, the allowed range being ±300 seconds by default; (c) if the FNI already exists in the global registry, checking whether the reported identifier version number is greater than the version number stored in the control plane etcd, to prevent the old version from overwriting the new version.
[0063] After successful verification, the federated control plane writes the FNI and original identification information into the Kubernetes custom resource FederationNodeMapping, stores it in etcd, and returns a reporting confirmation response. The confirmation response includes the acceptance identifier, confirmation information, and the global version number assigned by the federated control plane.
[0064] When a report fails, the node agent performs an exponential backoff retries. The waiting time for the nth retry is the smaller of 2 raised to the power of n times 100 milliseconds and 30 seconds. After 10 consecutive failed retries, the node enters degrade mode, suspends initiating new identity changes, responds to query requests using the locally cached identity view, and triggers an alarm to notify the administrator.
[0065] Next, the federated control plane synchronously distributes the FederationNodeMapping custom resource (equivalent to a mapping table) to all registered participant clusters through the Karmada multi-cluster management framework. Each participant cluster maintains a copy of the FederationNodeMapping custom resource in its local etcd. When a conflict occurs between the local copy and the federated control plane data, the version number stored in the federated control plane's etcd takes precedence; that is, the data maintained by the federated control plane is the authoritative data source.
[0066] The FederationNodeMapping custom resource is defined in apiGroup:federation.io / v1. Its spec field contains the local identifier (FNI), federation identifier, cluster name, platform type, architecture type, extended attribute key-value pairs, and mapping strategy. Its status field contains the version number, node status, and last heartbeat time. The node status includes active, offline, and conflicted states. The mapping strategy includes automatic and manual modes: In automatic mode, the control plane automatically generates the federation identifier, which is a short identifier formed by hashing the concatenated string of the local identifier and cluster name using SHA256 and appending a fixed prefix; in manual mode, the control plane waits for the administrator to manually specify the federation identifier in the status field.
[0067] In one embodiment, the method further includes: S8: In response to the triggering of a preset synchronization condition, the federated node constructs a version vector corresponding to the mapping table maintained locally by the federated node, using the federated node identifier as the key and the version number of the federated node identifier as the value. The federated node receives incremental data packets issued by the federated control plane and updates its local mapping table based on the incremental data packets, including: S701: The federation control plane combines the version vector to traverse the locally maintained mapping table and counts the target federation node identifiers and their corresponding version number increments in the locally maintained mapping table whose version number is greater than the version number of the federation node identifier corresponding to the version vector. S702: Generate the incremental data packet based on the target federation node identifier and the corresponding version number increment, and return it to the federation node; S703: The federated node obtains the incremental data packet and updates the mapping table maintained locally by the federated node accordingly.
[0068] For example, each federated node and the federated control plane maintain a local version vector. This version vector is a key-value mapping table with the FNI as the key and the largest identifier version number synchronized to that FNI as the value; the data structure is a map.<FederationNodeID, uint64> .
[0069] The synchronization conditions mentioned above are the triggering conditions for incremental synchronization, including any one or more of the following combinations: a) Timed trigger: Incremental synchronization checks are performed periodically at a preset period, which is 30 seconds by default; b) Event triggering: When the original identifier attribute of any federation node changes, or when a node is re-registered or the mapping strategy changes, resulting in identifier remapping, the identifier version number is incremented and incremental synchronization is initiated immediately; c) New Node Bootstrapping Trigger: After a new federation node completes two-factor authentication for the first time, the control plane returns the full version vector and the identification information of all active nodes for the node to initialize its local view; d) Recovery Trigger: After a node recovers from degraded mode, it immediately initiates incremental synchronization to retrieve the changed data from the degrade period; e) Manual triggering: Administrators can force synchronization through command-line tools or API.
[0070] When the synchronization condition is triggered, the initiating node sends its local version vector to the federated control plane via a bidirectional gRPC stream. Upon receiving the synchronization request, the federated control plane iterates through the current version numbers of all nodes in the global identifier registry. For each node: if the global current version number is greater than the corresponding version number in the initiating node's version vector, or if the node record does not exist in the initiating node's version vector, all incremental changes to that node since the known version number of the initiating node are packaged into an incremental data packet; if the global current version number is equal to or less than the corresponding version number in the initiating node's version vector, the node is skipped, and no change data is packaged.
[0071] The federal control plane returns the incremental data packets to the initiating node via a bidirectional gRPC stream. Upon receiving the incremental data packets, the initiating node applies the incremental changes one by one, updates its local identity view, and updates the corresponding entries in its local version vector to the highest synchronized version number.
[0072] The gRPC bidirectional stream synchronization channel supports breakpoint resumption and exponential backoff retries. The incremental data packets only contain change records within the version number difference range and do not include full identification data. With a federated node scale of 100, incremental synchronization reduces network traffic by more than 80% compared to full synchronization, and the synchronization latency (P99) can be less than 500 milliseconds.
[0073] Furthermore, the method also includes: S9: When the federal control plane detects a conflicting node with conflicting information in its locally maintained mapping table, it determines the registration mode of the conflicting node. The registration mode includes an automatic mode in which the federal control plane automatically completes the registration and a non-automatic mode in which the federal control plane completes the registration according to the user's instructions. The conflicting node is a federal node recorded in the mapping table. S10: If all the conflicting nodes are registered in automatic mode, the federated control plane will retain the conflicting nodes that have completed registration first in the mapping table; S11: If the registration mode of the conflicting node involves a non-automatic mode, the federated control plane generates a conflict event and sends it to the manual processing queue.
[0074] For example, during incremental synchronization, if the same federated identifier is claimed by multiple sources, or different clusters claim to represent the same physical node, a conflict arbitration procedure is triggered. Each FederationNodeMapping record carries a hybrid logical clock timestamp. During conflict arbitration, the mapping policy field in the records of both conflicting parties is checked first: (a) If both conflicting parties are in automatic mode, the last writer wins the arbitration, the record with the newer hybrid logical clock timestamp overwrites the record with the older timestamp, the overwritten record is not deleted, it is marked as a conflict state and written to the conflict audit log; (b) If either conflicting party is in manual mode, automatic arbitration is not performed, the conflict record is marked as a conflict state and written to the conflict audit log, awaiting administrator intervention. The conflict audit log is persistently stored in the federated control plane etcd, and administrators can query and manually adjudicate it through command-line tools.
[0075] Based on the above embodiments, the solution described in this application has the following beneficial effects: (I) Unified Identification Across Architectures. Through a highly scalable identification architecture awareness mechanism based on CEL expressions, different operating systems (CentOS, Ubuntu, Kylin, UOS), different container platforms (Kubernetes, K3s, OpenShift), and different hardware architectures (x86, ARM, Kunpeng, Hygon, Phytium) are uniformly described, eliminating identifier silos in heterogeneous environments. The federated node identity recognition accuracy reaches 100%. Adding a new platform only requires configuring a CEL expression template, with an expansion cycle of no more than one day. Compared to existing solutions that require 3 to 6 months of code-level modification, the expansion efficiency is improved by more than an order of magnitude.
[0076] (II) Zero-Trust Secure Access in Compliant with Domestic Information Technology. By combining KAE hardware acceleration with national cryptographic two-factor authentication, employing SM2, SM3, and SM4 national cryptographic algorithms and dynamic tokens, along with a multi-factor weighted dynamic trust scoring model, the zero-trust security concept of "never trust, always verify" is implemented. Hardware acceleration increases cryptographic throughput by 5 to 10 times, reducing single authentication latency from approximately 120 milliseconds in pure software solutions to approximately 15 milliseconds. In a scenario with 100 concurrent authentication nodes, control plane CPU utilization is reduced from approximately 78% to approximately 22%. The solution meets the requirements of Level 3 of the China Information Security Protection Scheme (CIS) 2.0 for cryptographic algorithms and identity authentication, effectively defending against man-in-the-middle attacks, identifier forgery, and session token replay attacks.
[0077] (III) Cross-Stack Interaction and Declarative Extension. Driven by the identifier mapping engine of the Karmada multi-cluster management framework, combined with custom resource definitions and controller reconcile loops, mapping strategies are managed declaratively and executed automatically. Adding a new cluster platform only requires registration to the Karmada control plane and configuration of a CEL template; no modification to the core control plane code is needed, reducing the extension cycle from days to hours. Mapping strategies (automatic or manual) and conflict arbitration rules can be dynamically adjusted via kubectl commands or API.
[0078] (iv) High-performance incremental synchronization and hardware acceleration. Through the version vector incremental synchronization mechanism, network bandwidth consumption is reduced by more than 80% compared to full synchronization at a scale of more than 100 federated nodes. gRPC bidirectional flow reduces connection establishment overhead, and the synchronization latency P99 is less than 500 milliseconds. KAE hardware acceleration improves the performance of national cryptographic operations by 5 to 10 times. The pure software degradation solution can achieve 60% to 70% of the throughput performance of KAE hardware acceleration on a 16-core server. Medium-sized federated clusters (no more than 50 nodes) can meet the usage requirements.
[0079] (v) Strategy-driven conflict arbitration mechanism. Through mapping strategy (automatic or manual) diversion control, in automatic mode the system automatically arbitrates based on hybrid logical clock timestamps to achieve second-level autonomous healing; in manual mode, the system forcibly retains human decision-making power, refuses automatic overwriting, and, together with conflict marking and audit log mechanism, achieves zero data loss and full-process traceability, balancing system autonomy efficiency and core asset security.
[0080] like Figure 3 As shown, another embodiment of the present invention also provides a federated cluster identifier mapping and national cryptographic security access device, including a federated node and a federated control plane, wherein: The federated node combines its original identification information with a predefined CEL expression template to form a federated node identifier, which has an auto-incrementing identification version number; The federated node and the federated control plane implement national cryptographic security authentication based on encrypted device certificates and dynamic tokens generated by the federated control plane. If the national cryptographic security certification is passed and the dynamic trust score of the federal node determined by the federal control plane meets the preset threshold requirements, the federal node reports an identifier registration request to the federal control plane based on the federal node identifier. If the federated node identifier is verified, the federated control plane registers the federated node identifier and the original identification information to a preset mapping table; The federal control plane distributes the mapping table in the registered federal node cluster; In response to the triggering of a preset synchronization condition, the federation node sends the version vector of the mapping table maintained locally by the corresponding federation node to the federation control plane. The synchronization condition represents a version vector incremental synchronization event. The federated node receives the incremental data packet issued by the federated control plane and updates its local mapping table based on the incremental data packet. The incremental data packet is data generated by the federated control plane based on the version vector and the mapping table when the global current version number of the mapping table has a version number greater than the version number corresponding to the version vector.
[0081] In one embodiment, the federated node processes its original identification information in conjunction with a predefined CEL expression template to form a federated node identifier, including the following: Collect the original identification information; The extended attribute set of the federation node is generated based on the CEL expression template; The federated node identifier is generated based on the CEL expression, the original identification information, and the extended attribute set.
[0082] In one embodiment, national cryptographic security authentication with the federal control plane is implemented based on the encrypted device certificate, including: The federation node signs the first random number, the first timestamp, and the federation node identifier based on its local private key to obtain the first signature; The federation node generates an authentication request based on the first signature, device certificate, first timestamp, and federation node identifier. The federated node sends the authentication request to the federated control plane; The federal control plane verifies each parameter in the authentication request.
[0083] In one embodiment, national cryptographic security authentication with the federal control plane is achieved based on a dynamic token generated by the encrypted federal control plane, including: After the national cryptographic security certification based on the device certificate is passed, the federated node establishes a temporary secure channel with the federated control plane; The federated node obtains a dynamic token generated by the federated control plane using a shared key, a session identifier, a second random number, and a second timestamp through the temporary secure channel. The federated node decrypts the dynamic token based on the shared key stored locally to determine the second timestamp; The federated node calculates the expected token value based on the shared key, session identifier, and second timestamp; The federation node generates a confirmation token based on the expected token value and the dynamic token; The federation node sends the confirmation token to the federation control plane through the temporary security channel; The federal control plane verifies the confirmation token.
[0084] In one embodiment, the dynamic trust score of the federated node determined by the federated control plane meets a preset threshold requirement, including the following: The behavior score is determined based on the success rate and abnormal request rate of the national cryptographic security authentication of the federated nodes in the first time period. The request frequency score is determined based on the deviation between the number of national cryptographic security authentication requests made by the federated node in the second time period and the historical baseline. A certificate validity score is determined based on the validity of the device certificates of the federated nodes; The certificate revocation status score is determined based on the revocation status of the device certificate of the federated node; The dynamic trust score of the federation node is obtained by weighting and summing the behavior score, request frequency score, certificate validity score, and revocation status score together with preset weights. When the dynamic trust score is not less than a preset threshold, the dynamic trust score meets the preset threshold requirement.
[0085] In one embodiment, the federated node is further configured to: If the national cryptographic security authentication is passed and the dynamic trust score of the federated node determined by the federated control plane meets the preset threshold requirements, the federated node derives a session master key based on the session identifier generated during the national cryptographic security authentication process. The federated node derives a session encryption key and a session MAC key based on the session master key; The federated node constructs an encrypted channel between itself and the federated control plane based on the national cryptographic algorithm. The encrypted channel is used for communication between the federated node and the federated control plane. In response to the triggering of the key rotation cycle, the federated node, based on the current session encryption key and session MAC key, encrypts and transmits a new session encryption key and session MAC key to the federated control plane through the encryption channel.
[0086] In one embodiment, the identifier registration request includes a federated node identifier, the original identifier information federated node cluster name, and a third timestamp; The step of registering the federal node identifier and its original identification information to a preset mapping table by the federal control plane, upon successful verification of the federal node identifier, includes: If the federal control plane verifies all parameters of the identifier registration request and it passes the verification, the federal node identifier and the original identifier information are written into a preset mapping table, and a confirmation response is returned to the federal node.
[0087] In one embodiment, the federated node is further configured to: In response to the triggering of a preset synchronization condition, the federated node constructs a version vector corresponding to the mapping table maintained locally by the federated node, using the federated node identifier as the key and the version number of the federated node identifier as the value. The federated node receives incremental data packets issued by the federated control plane and updates its local mapping table based on the incremental data packets, including: The federal control plane combines the version vector to traverse the locally maintained mapping table and counts the target federal node identifiers and their corresponding version number increments in the locally maintained mapping table whose version number is greater than the version number of the corresponding federal node identifier in the version vector. The incremental data packet is generated based on the target federation node identifier and the corresponding version number increment, and then returned to the federation node; The federated node receives the incremental data packet and updates the mapping table maintained locally by the federated node accordingly.
[0088] In one embodiment, the federal control plane is further used for: When the federal control plane detects a conflicting node with conflicting information in its locally maintained mapping table, it determines the registration mode of the conflicting node. The registration mode includes an automatic mode in which the federal control plane automatically completes the registration and a non-automatic mode in which the federal control plane completes the registration according to the user's instructions. The conflicting node is a federal node recorded in the mapping table. If all the conflicting nodes are registered in automatic mode, the federal control plane will retain the conflicting nodes that have completed registration first in the mapping table. If the registration mode of the conflicting node involves a non-automatic mode, the federated control plane generates a conflict event and sends it to a manual processing queue.
[0089] Another embodiment of the present invention also provides an electronic device for forming a federated node, comprising: One or more processors; Memory, configured to store one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the federated cluster identifier mapping and national cryptographic security access method as described above.
[0090] Another embodiment of the present invention also provides an electronic device for forming a device containing a federal control plane, comprising: One or more processors; Memory, configured to store one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the federated cluster identifier mapping and national cryptographic security access method as described above.
[0091] Furthermore, one embodiment of the present invention also provides a storage medium storing a computer program, which, when executed by a processor, implements the federated cluster identifier mapping and national cryptographic security access method as described above. It should be understood that the various solutions in this embodiment have the corresponding technical effects in the above method embodiments, and will not be repeated here.
[0092] Furthermore, embodiments of the present invention also provide a computer program product, which is tangibly stored on a computer-readable medium and includes computer-readable instructions, which, when executed, cause at least one processor to perform a method such as the federated cluster identifier mapping and national cryptographic security access method described in the embodiments above.
[0093] It should be noted that the computer storage medium of the present invention can be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, system, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, a random access storage medium (RAM), a read-only storage medium (ROM), an erasable programmable read-only storage medium (EPROM or flash memory), an optical fiber, a portable compact disk read-only storage medium (CD-ROM), an optical storage medium, a magnetic storage medium, or any suitable combination thereof. In the present invention, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, system, or device. In the present invention, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media can also be any computer-readable medium other than computer-readable storage media, which can send, propagate, or transmit a program configured for use by or in connection with an instruction execution system, system, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wireless, antenna, optical fiber, RF, etc., or any suitable combination thereof.
[0094] Furthermore, those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present invention can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage and optical storage) containing computer-usable program code.
[0095] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1One or more processes and / or boxes Figure 1 A system that specifies functions in one or more boxes.
[0096] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including an instruction set implemented in a process. Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.
[0097] Those skilled in the art should understand that the discussion of any of the above embodiments is merely exemplary and is not intended to imply that the scope of protection of this application is limited to these examples; within the framework of this application, the technical features of the above embodiments or different embodiments can also be combined, the steps can be implemented in any order, and there are many other variations of different aspects of one or more embodiments of this application as described above, which are not provided in detail for the sake of brevity.
Claims
1. A method for mapping federated cluster identifiers and secure access using national cryptographic standards, characterized in that, include: The federated node combines its original identification information with a predefined CEL expression template to form a federated node identifier, which has an auto-incrementing identification version number; The federated node and the federated control plane implement national cryptographic security authentication based on encrypted device certificates and dynamic tokens generated by the federated control plane. If the national cryptographic security certification is passed and the dynamic trust score of the federal node determined by the federal control plane meets the preset threshold requirements, the federal node reports an identifier registration request to the federal control plane based on the federal node identifier. If the federated node identifier is verified, the federated control plane registers the federated node identifier and the original identification information to a preset mapping table; The federal control plane distributes the mapping table in the registered federal node cluster; In response to the triggering of a preset synchronization condition, the federation node sends the version vector of the mapping table maintained locally by the corresponding federation node to the federation control plane. The synchronization condition represents a version vector incremental synchronization event. The federated node receives the incremental data packet issued by the federated control plane and updates its local mapping table based on the incremental data packet. The incremental data packet is data generated by the federated control plane based on the version vector and the mapping table when the global current version number of the mapping table has a version number greater than the version number corresponding to the version vector.
2. The federated cluster identifier mapping and national cryptographic security access method according to claim 1, characterized in that, The federated node processes its original identification information by combining it with a predefined CEL expression template to form a federated node identifier, including the following: Collect the original identification information; The extended attribute set of the federation node is generated based on the CEL expression template; The federated node identifier is generated based on the CEL expression, the original identification information, and the extended attribute set.
3. The federated cluster identifier mapping and national cryptographic security access method according to claim 1, characterized in that, Based on the encrypted device certificate, national cryptographic security authentication with the federal control plane is implemented, including: The federation node signs the first random number, the first timestamp, and the federation node identifier based on its local private key to obtain the first signature; The federation node generates an authentication request based on the first signature, device certificate, first timestamp, and federation node identifier. The federated node sends the authentication request to the federated control plane; The federal control plane verifies each parameter in the authentication request.
4. The federated cluster identifier mapping and national cryptographic security access method according to claim 1, characterized in that, Based on a dynamic token generated by the encrypted federal control plane, national cryptographic security authentication with the federal control plane is implemented, including: After the national cryptographic security certification based on the device certificate is passed, the federated node establishes a temporary secure channel with the federated control plane; The federated node obtains a dynamic token generated by the federated control plane using a shared key, a session identifier, a second random number, and a second timestamp through the temporary secure channel. The federated node decrypts the dynamic token based on the shared key stored locally to determine the second timestamp; The federated node calculates the expected token value based on the shared key, session identifier, and second timestamp; The federation node generates a confirmation token based on the expected token value and the dynamic token; The federation node sends the confirmation token to the federation control plane through the temporary secure channel; The federal control plane verifies the confirmation token.
5. The federated cluster identifier mapping and national cryptographic security access method according to claim 1, characterized in that, The dynamic trust score of the federated node determined by the federated control plane meets the preset threshold requirement, including the following: The behavior score is determined based on the success rate and abnormal request rate of the national cryptographic security authentication of the federated nodes in the first time period. The request frequency score is determined based on the deviation between the number of national cryptographic security authentication requests made by the federated nodes in the second time period and the historical baseline. A certificate validity score is determined based on the validity of the device certificates of the federated nodes; The revocation status score of the certificate is determined based on the revocation status of the device certificate of the federated node; The dynamic trust score of the federation node is obtained by weighting and summing the behavior score, request frequency score, certificate validity score, and revocation status score together with preset weights. When the dynamic trust score is not less than a preset threshold, the dynamic trust score meets the preset threshold requirement.
6. The federated cluster identifier mapping and national cryptographic security access method according to claim 1, characterized in that, The method further includes: If the national cryptographic security authentication is passed and the dynamic trust score of the federated node determined by the federated control plane meets the preset threshold requirements, the federated node derives a session master key based on the session identifier generated during the national cryptographic security authentication process. The federated node derives a session encryption key and a session MAC key based on the session master key; The federated node constructs an encrypted channel between itself and the federated control plane based on the national cryptographic algorithm. The encrypted channel is used for communication between the federated node and the federated control plane. In response to the triggering of the key rotation cycle, the federated node, based on the current session encryption key and session MAC key, encrypts and transmits a new session encryption key and session MAC key to the federated control plane through the encryption channel.
7. The federated cluster identifier mapping and national cryptographic security access method according to claim 1, characterized in that, The identifier registration request includes the federated node identifier, the original identifier information (federated node cluster name), and a third timestamp. The step of registering the federal node identifier and its original identification information to a preset mapping table by the federal control plane, upon successful verification of the federal node identifier, includes: If the federal control plane verifies all parameters of the identifier registration request and it passes the verification, the federal node identifier and the original identifier information are written into a preset mapping table, and a confirmation response is returned to the federal node.
8. The federated cluster identifier mapping and national cryptographic security access method according to claim 1, characterized in that, The method further includes: In response to the triggering of a preset synchronization condition, the federated node constructs a version vector corresponding to the mapping table maintained locally by the federated node, using the federated node identifier as the key and the version number of the federated node identifier as the value. The federated node receives incremental data packets issued by the federated control plane and updates its local mapping table based on the incremental data packets, including: The federal control plane combines the version vector to traverse the locally maintained mapping table and counts the target federal node identifiers and their corresponding version number increments in the locally maintained mapping table whose version number is greater than the version number of the corresponding federal node identifier in the version vector. The incremental data packet is generated based on the target federation node identifier and the corresponding version number increment, and then returned to the federation node; The federated node receives the incremental data packet and updates the mapping table maintained locally by the federated node accordingly.
9. The federated cluster identifier mapping and national cryptographic security access method according to claim 1, characterized in that, The method further includes: When the federal control plane detects a conflicting node with conflicting information in its locally maintained mapping table, it determines the registration mode of the conflicting node. The registration mode includes an automatic mode in which the federal control plane automatically completes the registration and a non-automatic mode in which the federal control plane completes the registration according to the user's instructions. The conflicting node is a federal node recorded in the mapping table. If all the conflicting nodes are registered in automatic mode, the federal control plane will retain the conflicting nodes that have completed registration first in the mapping table. If the registration mode of the conflicting node involves a non-automatic mode, the federated control plane generates a conflict event and sends it to a manual processing queue.
10. A federal cluster identifier mapping and national cryptographic security access device, characterized in that, This includes federated nodes and the federated control plane, among which: The federated node combines its original identification information with a predefined CEL expression template to form a federated node identifier, which has an auto-incrementing identification version number; The federated node and the federated control plane implement national cryptographic security authentication based on encrypted device certificates and dynamic tokens generated by the federated control plane. If the national cryptographic security certification is passed and the dynamic trust score of the federal node determined by the federal control plane meets the preset threshold requirements, the federal node reports an identifier registration request to the federal control plane based on the federal node identifier. If the federated node identifier is verified, the federated control plane registers the federated node identifier and the original identification information to a preset mapping table; The federal control plane distributes the mapping table in the registered federal node cluster; In response to the triggering of a preset synchronization condition, the federation node sends the version vector of the mapping table maintained locally by the corresponding federation node to the federation control plane. The synchronization condition represents a version vector incremental synchronization event. The federated node receives the incremental data packet issued by the federated control plane and updates its local mapping table based on the incremental data packet. The incremental data packet is data generated by the federated control plane based on the version vector and the mapping table when the global current version number of the mapping table has a version number greater than the version number corresponding to the version vector.
