Cross-platform information encryption transmission method, device, equipment and medium

Abstract

The invention discloses a cross-platform information encryption transmission method and device, equipment and a medium, is applied to a first enterprise platform, and relates to the technical field of computers, and the method comprises the steps: generating a plaintext exception record data packet based on an exception record, and encrypting the data packet through a random root key to obtain a target encrypted exception record data packet; generating a target sub-key based on the random root key, encrypting the target sub-key, and then encoding a target encrypted sub-key obtained by encryption and a target encrypted abnormal record data packet; and performing communication connection with a second enterprise platform through a message queue of a preset proxy server, and sending the encoded target abnormal record notification data packet and the target encryption sub-key to the second enterprise platform, so that the second enterprise platform decrypts the target abnormal record notification data packet based on the target encryption sub-key, and processing the plaintext abnormal record data packet obtained after decryption. Therefore, cross-platform exception notification can be completed while the security is ensured.

Description

A cross-platform method, apparatus, device and medium for encrypted information transmission Technical Field

[0001] This invention relates to the field of computer technology, and in particular to a cross-platform information encryption transmission method, apparatus, device, and medium. Background Technology

[0002] Currently, anomaly log notifications focus primarily on cleaning, filtering, and integrating the data, limiting notifications to a single platform. This neglects the challenges of multi-layered enterprise architectures, preventing cross-LAN notifications and real-time online notifications. Sometimes, traditional offline notification methods are necessary, leading to anomaly logs not reaching the responsible parties promptly and accurately, hindering timely processing. Therefore, a solution to these problems is urgently needed. Furthermore, security issues during information transmission across multi-platform architectures are not considered, and no encryption / decryption solution is provided. Summary of the Invention

[0003] In view of this, the purpose of the present invention is to provide a cross-platform information encryption transmission method, apparatus, device and medium that can realize cross-platform abnormal notification and complete the abnormal recording notification in a multi-layer architecture by means of encrypted message forwarding, thereby completing cross-platform information transmission abnormal notification while ensuring security. The specific solution is as follows: Firstly, this application discloses a cross-platform information encryption transmission method, applied to a first enterprise platform, comprising: generating a plaintext abnormal record data packet based on locally detected abnormal records, and encrypting the plaintext abnormal record data packet using a generated random root key to obtain a target encrypted abnormal record data packet; generating a target subkey based on the random root key and local platform information, and encrypting the target subkey using a preset encryption algorithm to obtain a target encrypted subkey; then encoding the target encrypted subkey and the target encrypted abnormal record data packet using a preset encoding algorithm to obtain a target abnormal record notification data packet; establishing a communication connection with a second enterprise platform through a message queue of a preset proxy server, and sending the target abnormal record notification data packet and the target encrypted subkey to the second enterprise platform after successful connection, so that the second enterprise platform can decrypt the target abnormal record notification data packet based on the target encrypted subkey and process the decrypted plaintext abnormal record data packet; the second enterprise platform is a platform not on the same local area network as the first enterprise platform.

[0004] Optionally, generating plaintext abnormal record data packets based on locally detected abnormal records includes: if an abnormal record is detected, collecting abnormal data corresponding to the abnormal record according to a preset data type; performing a standardization operation on the abnormal data to obtain standardized abnormal data, and encapsulating the standardized abnormal data to encapsulate the standardized abnormal data into plaintext abnormal record data packets.

[0005] Optionally, the step of encrypting the plaintext anomaly record data packet using the generated random root key to obtain the target encrypted anomaly record data packet includes: padding the plaintext anomaly record data packet based on a preset data length to obtain a padded data packet; generating a random root key based on a preset encryption algorithm and encrypting the padded data packet using the random root key to obtain an encrypted anomaly record data packet; generating an encryption integrity verification tag and binding the encryption integrity verification tag, the encrypted anomaly record data packet, and the key identifier corresponding to the random root key to obtain an encrypted anomaly record data packet to be encapsulated; and adding a local framework identifier and a local platform type field to the encrypted anomaly record data packet to be encapsulated to obtain the target encrypted anomaly record data packet.

[0006] Optionally, the step of generating a target subkey based on the random root key and local platform information, encrypting the target subkey using a preset encryption algorithm to obtain a target encrypted subkey, and then encoding the target encrypted subkey and the target encrypted anomaly record data packet using a preset encoding algorithm to obtain a target anomaly record notification data packet includes: generating a subkey to be determined corresponding to the random root key based on the random root key, the local platform identifier, and the local framework identifier, and setting an effective time for the subkey to be determined based on a preset key period to obtain a target subkey; encrypting the target subkey using a preset encryption algorithm to obtain a target encrypted subkey, and encoding the target encrypted subkey and the target encrypted anomaly record data packet using a preset encoding algorithm. The process involves encoding the data to obtain a target anomaly record notification data packet. Correspondingly, after generating a target sub-key based on the random root key and local platform information, encrypting the target sub-key using a preset encryption algorithm to obtain a target encrypted sub-key, and then encoding the target encrypted sub-key and the target encrypted anomaly record data packet using a preset encoding algorithm to obtain the target anomaly record notification data packet, the process further includes: if the target sub-key has exceeded its validity period, then proceeding to the step of generating a sub-key to be determined corresponding to the random root key based on the random root key, the local platform identifier, and the local framework identifier, and setting a validity period for the sub-key to be determined based on a preset key expiration date to obtain the target sub-key, thereby using the newly generated key as the target sub-key.

[0007] Optionally, the step of establishing a communication connection with the second enterprise platform through the message queue of a preset proxy server, and sending the target anomaly record notification data packet and the target encryption subkey to the second enterprise platform after a successful connection, includes: sending a target connection request to the message queue of the preset proxy server to connect with the second enterprise platform, so that the preset proxy server can return the address information of the second enterprise platform to the local machine; establishing a connection with the second enterprise platform based on the address information, and sending the target anomaly record notification data packet and the target encryption subkey to the second enterprise platform after a successful connection.

[0008] Optionally, the step of decrypting the target anomaly record notification data packet based on the target encryption subkey includes: decoding the target anomaly record notification data packet based on the preset encoding algorithm to obtain the target encryption subkey and the target encrypted anomaly record data packet; decrypting the target encryption subkey using the preset encryption algorithm to obtain the target subkey; and decrypting the target encrypted anomaly record data packet using the target subkey to obtain the plaintext anomaly record data packet.

[0009] Optionally, the cross-platform information encryption transmission method further includes: if a pending exception record data packet is received from a third enterprise platform, the pending exception record data packet is decrypted to obtain the target pending plaintext data corresponding to the pending exception record data packet; the platform type of the third enterprise platform is determined; if the third enterprise platform is a subordinate platform corresponding to the first enterprise platform, the target pending plaintext data is approved, an approval completion notification is generated, and the approval completion notification is sent to the subordinate platform; if the third enterprise platform is an superior platform corresponding to the first enterprise platform, the target pending plaintext data is processed, the processed plaintext data is encrypted, and the obtained encrypted processed data is fed back to the superior platform for approval.

[0010] Secondly, this application discloses a cross-platform information encryption transmission device applied to a first enterprise platform, comprising: a data packet encryption module, used to generate a plaintext abnormal record data packet based on locally detected abnormal records, and encrypt the plaintext abnormal record data packet using a generated random root key to obtain a target encrypted abnormal record data packet; a data encoding module, used to generate a target subkey based on the random root key and local platform information, and encrypt the target subkey using a preset encryption algorithm to obtain a target encrypted subkey, and then encode the target encrypted subkey and the target encrypted abnormal record data packet using a preset encoding algorithm to obtain a target abnormal record notification data packet; and a data processing module, used to establish a communication connection with a second enterprise platform through a message queue of a preset proxy server, and after successful connection, send the target abnormal record notification data packet and the target encrypted subkey to the second enterprise platform, so that the second enterprise platform can decrypt the target abnormal record notification data packet based on the target encrypted subkey and process the decrypted plaintext abnormal record data packet; the second enterprise platform is a platform not on the same local area network as the first enterprise platform.

[0011] Thirdly, this application discloses an electronic device, including: a memory for storing a computer program; and a processor for executing the computer program to implement the cross-platform encrypted information transmission method as described above.

[0012] Fourthly, this application discloses a computer-readable storage medium for storing a computer program, wherein the computer program, when executed by a processor, implements the cross-platform encrypted information transmission method as described above.

[0013] In this application, a plaintext anomaly record data packet can be generated based on locally detected anomaly records, and the plaintext anomaly record data packet can be encrypted using a generated random root key to obtain a target encrypted anomaly record data packet; a target subkey can be generated based on the random root key and local platform information, and the target subkey can be encrypted using a preset encryption algorithm to obtain a target encrypted subkey; then, the target encrypted subkey and the target encrypted anomaly record data packet can be encoded using a preset encoding algorithm to obtain a target anomaly record notification data packet; a communication connection is established with a second enterprise platform through a message queue of a preset proxy server, and after a successful connection, the target anomaly record notification data packet and the target encrypted subkey are sent to the second enterprise platform, so that the second enterprise platform can decrypt the target anomaly record notification data packet based on the target encrypted subkey and process the decrypted plaintext anomaly record data packet; the second enterprise platform is a platform that is not on the same local area network as the first enterprise platform.

[0014] Therefore, the method of this application can generate corresponding plaintext anomaly record data packets based on locally detected anomaly records, and then encrypt them using a random root key to obtain target encrypted anomaly record data packets. Further, a corresponding target subkey needs to be generated based on the random root key and local platform information, and then the target subkey is encrypted. The encrypted target subkey and the target encrypted anomaly record data packets are then encoded using a preset encoding algorithm to obtain target anomaly record notification data packets. Further, a connection request needs to be sent to the message queue of a preset proxy message server to establish a communication connection with a second enterprise platform in another local area network. After a successful connection, the target anomaly record notification data packets and the target encrypted subkey are sent to the second enterprise platform, so that the second enterprise platform can decrypt the target anomaly record notification data packets based on the target encrypted subkey and process the resulting plaintext anomaly record data packets. In this way, cross-platform anomaly notification can be achieved, and anomaly record notification in a multi-layered architecture can be completed through encrypted message forwarding, thus ensuring security while completing cross-platform information transmission anomaly notification. Attached Figure Description

[0015] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0016] Figure 1 is a flowchart of a cross-platform information encryption transmission method disclosed in this application; Figure 2 is a flowchart of an information encryption process disclosed in this application; Figure 3 is a schematic diagram of a cross-platform communication connection disclosed in this application; Figure 4 is a flowchart of an information decryption process disclosed in this application; Figure 5 is a schematic diagram of a cross-platform information encryption transmission device disclosed in this application; Figure 6 is a structural diagram of an electronic device disclosed in this application. Detailed Implementation

[0017] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0018] Currently, notifications for abnormal records are typically limited to a single platform, neglecting the potential multi-layered architecture within an enterprise and thus preventing cross-LAN notifications. Furthermore, they fail to consider security issues during information transmission across multiple platforms, lacking a solution for encryption and decryption.

[0019] To overcome the aforementioned technical problems, this application discloses a cross-platform information encryption transmission method, apparatus, device, and medium, which can realize cross-platform abnormal notification and complete abnormal recording notification in a multi-layer architecture through encrypted message forwarding, thereby ensuring security while completing cross-platform information transmission abnormal notification.

[0020] Referring to Figure 1, this embodiment of the invention discloses a cross-platform information encryption transmission method, applied to a first enterprise platform, including: step S11, generating a plaintext abnormal record data packet based on locally detected abnormal records, and encrypting the plaintext abnormal record data packet with a generated random root key to obtain a target encrypted abnormal record data packet.

[0021] In this embodiment, it is necessary to generate corresponding data packets from locally detected anomaly records and encrypt them to obtain the target encrypted anomaly record data packet. Specifically, if an anomaly record is detected, the anomaly data corresponding to the anomaly record is collected according to a preset data type. Specifically, it is necessary to monitor the anomaly triggering interface of each framework platform. When an anomaly is detected, the anomaly data corresponding to the anomaly record is collected according to the preset data type, which includes core fields such as anomaly type, occurrence timestamp, node IP (Internet Protocol Address), and fault code. Then, the anomaly data needs to be standardized to obtain standardized anomaly data, and the standardized anomaly data is encapsulated to encapsulate the standardized anomaly data into a plaintext anomaly record data packet.

[0022] Furthermore, the plaintext anomaly record data packet needs to be encrypted. As shown in Figure 2, AES (Advanced Encryption Standard) encryption is required first. Specifically, the plaintext anomaly record data packet needs to be padded based on a preset data length to obtain a padded data packet, thus ensuring its length meets the AES 128-bit block encryption requirement. Then, a random root key needs to be generated based on a preset encryption algorithm, and the padded data packet is encrypted using this random root key to obtain the encrypted anomaly record data packet. A 256-bit AES root key needs to be generated as the basis for key derivation to avoid insufficient randomness in software-generated keys. Next, an encryption integrity verification tag needs to be generated, and the encryption integrity verification tag, the encrypted anomaly record data packet, and the key identifier corresponding to the random root key are bound together to obtain the encrypted anomaly record data packet to be encapsulated. The generated encryption integrity verification tag is named AuthTag. Finally, a local frame identifier and a local platform type field are added to the encrypted anomaly record data packet to obtain the target encrypted anomaly record data packet. It is important to note that the local frame identifier and local platform type field need to be added to the data packet header so that the receiving end can match the corresponding decryption key. In this way, data security can be ensured through preliminary encryption, thereby improving the security of the cross-platform information encryption transmission method of this application.

[0023] Step S12: Generate a target subkey based on the random root key and local platform information, and encrypt the target subkey using a preset encryption algorithm to obtain a target encrypted subkey. Then, encode the target encrypted subkey and the target encrypted anomaly record data packet based on a preset encoding algorithm to obtain a target anomaly record notification data packet.

[0024] In this embodiment, as shown in Figure 2, a target subkey needs to be generated based on the random root key and local platform information. This target subkey is then encrypted using a preset encryption algorithm to obtain the target encrypted subkey. Specifically, a subkey to be determined corresponding to the random root key needs to be generated based on the random root key, the local platform identifier, and the local framework identifier. A valid period is then set for the subkey to be determined based on a preset key expiration date to obtain the target subkey. In a specific scenario, a unique AESKey can be derived for each connected framework and platform based on the root key combined with the platform identifier (such as the device SN (Serial Number)) and the framework type (such as "Spring-01" "Dubbo-02"). After encrypting the subkey through the PKI (Public Key Infrastructure) system, it is distributed to the corresponding nodes to ensure that the key is not leaked during the distribution process.

[0025] Furthermore, as shown in Figure 2, the target subkey needs to be encrypted using a preset encryption algorithm to obtain the target encryption subkey. Then, the target encryption subkey and the target encrypted anomaly record data packet are encoded using a preset encoding algorithm to obtain the target anomaly record notification data packet. It should be noted that the preset encoding algorithm is Base64 encoding. In this way, by Base64 encoding the target encrypted anomaly record data packet, the encrypted data can be converted into ASCII (American Standard Code for Information Interchange) characters, thus avoiding garbled characters or data corruption caused by encoding problems when directly transmitting binary data.

[0026] It should be noted that the key needs to be dynamically updated. Specifically, if the target subkey has exceeded its validity period, the process jumps to generating a subkey to be determined corresponding to the random root key based on the random root key, the local platform identifier, and the local framework identifier. The validity period of this subkey is then set based on a preset key expiration date to obtain the target subkey, which is then used as the target subkey. It should also be noted that while a key validity period is set, the specific validity period can be set according to the actual application scenario, such as 24 hours. Before the expiration date, the core node pushes a new AESKey through an encrypted channel, and the old key is retained for 48 hours to accommodate incomplete anomaly notification decryption and prevent data loss during the update process.

[0027] It should be further explained that if problems such as AESKey failure or incorrect parameter format occur during encryption, a local alarm will be triggered immediately, and the encryption will be re-encrypted using a backup AESKey. The cause of the anomaly will be recorded, such as key expiration or missing parameters.

[0028] Step S13: Establish a communication connection with the second enterprise platform through the message queue of the preset proxy server, and after the connection is successful, send the target anomaly record notification data packet and the target encryption subkey to the second enterprise platform, so that the second enterprise platform can decrypt the target anomaly record notification data packet based on the target encryption subkey and process the plaintext anomaly record data packet obtained after decryption; the second enterprise platform is a platform that is not on the same local area network as the first enterprise platform.

[0029] In this embodiment, a connection to other platforms is first required. After a successful connection, the corresponding target anomaly record notification data packet and the target encryption subkey are sent to that platform. Specifically, as shown in Figure 3, a target connection request to connect to the second enterprise platform is first sent to the message queue of the preset proxy server so that the preset proxy server can return the address information of the second enterprise platform to the local machine. As shown in Figure 3, in a specific scenario, the first enterprise platform has a server A (dataServerA) on the 10.0.0.0 network segment with a LAN address of 10.0.0.2, and the second enterprise platform has a server B (dataServerB) on the 192.168.1.0 network segment with a LAN address of 192.168.2.2. They cannot directly access each other in different LANs, but both can connect to the Internet through their own gateways or routers. A satelliteServer acts as a navigation server on the Internet to implement the MQ (Message Queue) function. Ultimately, communication between dataServerA and dataServerB is achieved.

[0030] In this process, the target connection request randomly generates an AESKey for each request. The request parameters are encrypted with the AESKey using AES, and the AESKey is then encrypted using RSA (Rivest-Shamir-Adleman, asymmetric encryption). All request parameters are uniformly Base64 encoded and encrypted. The specific encryption process is as follows: Encryption key: RSA combined with AES is used to encrypt important information; Request data: AES and Base64 are used for hybrid encryption; The encryption key is a locally generated AESkey and RSA encryption using a local public key. Request parameters are encrypted with AES using the AESKey and then Base64 encoded to prevent cracking.

[0031] Furthermore, after receiving the target connection request, the second enterprise platform decrypts it. First, it decrypts the request data, performing Base64 encoding decryption. Then, it performs RSA decryption on the AESKey. Finally, it performs AES decryption on the decrypted data and the AESKey, and then transmits the local address information to the message queue so that the pre-defined proxy server can relay the second enterprise platform's address information to the first enterprise platform. Finally, based on the address information, it establishes a connection with the second enterprise platform, and upon successful connection, sends the target anomaly log notification data packet and the target encryption subkey to the second enterprise platform.

[0032] As shown in Figure 4, after the second enterprise platform receives the target anomaly record notification data packet and the target encrypted subkey transmitted by the first enterprise platform, it first needs to decrypt them. Specifically, it needs to deencode the target anomaly record notification data packet based on the preset encoding algorithm to obtain the target encrypted subkey and the target encrypted anomaly record data packet. Then, it needs to decrypt the target encrypted subkey using the preset encryption algorithm to obtain the target subkey, and then decrypt the target encrypted anomaly record data packet using the target subkey to obtain the plaintext anomaly record data packet. It should be noted that the corresponding AESKey is first obtained through the key identifier in the data packet header, and the integrity of the AuthTag is verified at the same time. If the verification fails, a decryption exception is immediately reported to the sending end. After successful decryption, the exception parameters are parsed and announced through multiple channels (such as the operation and maintenance console pop-up, email, and SMS), and the decrypted exception record is stored in the encrypted database for archiving.

[0033] It should be noted that if a data packet is lost during transmission and the receiving end does not respond within a preset time (e.g., 3 seconds), the sending end will automatically retry the transmission. After three failed retryes, the exception record will be stored in the local cache and retransmitted after the network is restored. Furthermore, events such as encryption failure, decryption exception, and transmission timeout need to be recorded in real time to form an audit log, which will be periodically synchronized to the core nodes to facilitate operation and maintenance to trace problems.

[0034] In this embodiment, a corresponding plaintext anomaly record data packet can be generated based on locally detected anomaly records. This packet is then encrypted using a random root key to obtain a target encrypted anomaly record data packet. Further, a target subkey needs to be generated based on the random root key and local platform information. This target subkey is then encrypted, and the encrypted target subkey and the target encrypted anomaly record data packet are encoded using a preset encoding algorithm to obtain a target anomaly record notification data packet. Further, a connection request needs to be sent to the message queue of a preset proxy message server to establish a communication connection with a second enterprise platform in another local area network. Upon successful connection, the target anomaly record notification data packet and the target encrypted subkey are sent to the second enterprise platform. The second enterprise platform then decrypts the target anomaly record notification data packet based on the target encrypted subkey and processes the resulting plaintext anomaly record data packet. This enables cross-platform anomaly notification and achieves anomaly record notification in a multi-layered architecture through encrypted message forwarding, thus ensuring security while completing cross-platform information transmission anomaly notification.

[0035] In a preferred embodiment, if the local system receives a pending exception record data packet from a third enterprise platform, it decrypts the pending exception record data packet to obtain the target pending plaintext data corresponding to the pending exception record data packet. It should be noted that the decryption method can also refer to the decryption method shown in Figure 4 of the aforementioned embodiments. Then, the platform type of the third enterprise platform needs to be determined. If the third enterprise platform is a subordinate platform corresponding to the first enterprise platform, after approving the target pending plaintext data, an approval completion notification is generated and sent to the subordinate platform. If the third enterprise platform is a superior platform corresponding to the first enterprise platform, the target pending plaintext data is processed, and the processed plaintext data is encrypted. Then, the encrypted processed data is fed back to the superior platform for approval. Therefore, within the same platform, a superior unit can issue a notification of exception records to a subordinate unit, and the subordinate unit, after receiving the notification and completing the processing, feeds back to the superior unit for approval; within the same platform, a superior unit can send a notification of exception records to a subordinate unit, and the superior unit, after receiving the notification, can feed back to the subordinate unit. This achieves a closed-loop notification system. It's also worth noting that different platforms can send notifications of abnormal records to or from subordinate units via messages, enabling cross-platform notification transmission. Subordinate units receiving notifications of abnormal records from superior units can further distribute the notifications, and superior units receiving notifications of abnormal records from subordinate units can forward them to their own superiors, achieving flexibility and diversity in notifications. In this way, the system has a built-in flexible and adaptable organizational structure management mechanism, accommodating different architectures. It supports cascading management between different platforms and hierarchical management within the same platform.

[0036] Referring to Figure 5, this embodiment of the invention discloses a cross-platform information encryption transmission device applied to a first enterprise platform, comprising: a data packet encryption module 11, used to generate a plaintext abnormal record data packet based on locally detected abnormal records, and encrypt the plaintext abnormal record data packet using a generated random root key to obtain a target encrypted abnormal record data packet; a data encoding module 12, used to generate a target subkey based on the random root key and local platform information, and encrypt the target subkey using a preset encryption algorithm to obtain a target encrypted subkey, and then encode the target encrypted subkey and the target encrypted abnormal record data packet using a preset encoding algorithm to obtain a target abnormal record notification data packet; and a data processing module 13, used to establish a communication connection with a second enterprise platform through a message queue of a preset proxy server, and after successful connection, send the target abnormal record notification data packet and the target encrypted subkey to the second enterprise platform, so that the second enterprise platform can decrypt the target abnormal record notification data packet based on the target encrypted subkey and process the decrypted plaintext abnormal record data packet; the second enterprise platform is a platform not on the same local area network as the first enterprise platform.

[0037] In some embodiments, the data packet encryption module 11 may specifically include: a data acquisition unit, used to acquire abnormal data corresponding to the abnormal record according to a preset data type if an abnormal record is detected; and a data encapsulation unit, used to perform a standardization operation on the abnormal data to obtain standardized abnormal data, and to encapsulate the standardized abnormal data to encapsulate the standardized abnormal data into a plaintext abnormal record data packet.

[0038] In some embodiments, the data packet encryption module 11 may specifically include: a data padding unit, used to pad the plaintext anomaly record data packet based on a preset data length to obtain a padded data packet; a data packet encryption unit, used to generate a random root key based on a preset encryption algorithm, and encrypt the padded data packet using the random root key to obtain an encrypted anomaly record data packet; a data binding unit, used to generate an encryption integrity verification tag, and bind the encryption integrity verification tag, the encrypted anomaly record data packet, and the key identifier corresponding to the random root key to obtain an encrypted anomaly record data packet to be encapsulated; and a data packet encapsulation unit, used to add a local framework identifier and a local platform type field to the encrypted anomaly record data packet to be encapsulated to obtain a target encrypted anomaly record data packet.

[0039] In some embodiments, the data encoding module 12 may specifically include: a subkey generation unit, configured to generate a subkey to be determined corresponding to the random root key based on the random root key, the local platform identifier, and the local framework identifier, and to set an effective time for the subkey to be determined based on a preset key period to obtain a target subkey; a data encoding unit, configured to encrypt the target subkey using a preset encryption algorithm to obtain a target encrypted subkey, and to encode the target encrypted subkey and the target encrypted anomaly record data packet using a preset encoding algorithm to obtain a target anomaly record notification data packet; in some embodiments, the cross-platform information encryption transmission device further includes: a step jump unit, configured to jump to the step of generating a subkey to be determined corresponding to the random root key based on the random root key, the local platform identifier, and the local framework identifier, and setting an effective time for the subkey to be determined based on a preset key period to obtain a target subkey if the target subkey has exceeded the effective time, so as to use the newly generated key as the target subkey.

[0040] In some embodiments, the data processing module 13 may specifically include: a request sending unit, configured to send a target connection request to the message queue of a preset proxy server to connect to the second enterprise platform, so that the preset proxy server can return the address information of the second enterprise platform to the local machine; and a data transmission unit, configured to connect to the second enterprise platform based on the address information, and send the target abnormal record notification data packet and the target encryption subkey to the second enterprise platform after the connection is successful.

[0041] In some embodiments, the data processing module 13 may specifically include: a data decoding unit, configured to decode the target anomaly record notification data packet based on the preset encoding algorithm to obtain the target encrypted subkey and the target encrypted anomaly record data packet; and a first data decryption unit, configured to decrypt the target encrypted subkey using the preset encryption algorithm to obtain the target subkey, and decrypt the target encrypted anomaly record data packet using the target subkey to obtain the plaintext anomaly record data packet.

[0042] In some embodiments, the cross-platform information encryption transmission device may further include: a second data decryption unit, configured to decrypt the pending anomaly record data packet sent by a third enterprise platform to obtain target pending plaintext data corresponding to the pending anomaly record data packet if the pending anomaly record data packet is received; a first data processing unit, configured to determine the platform type of the third enterprise platform, and if the third enterprise platform is a subordinate platform corresponding to the first enterprise platform, to approve the target pending plaintext data, generate an approval completion notification, and send the approval completion notification to the subordinate platform; and a second data processing unit, configured to process the target pending plaintext data and encrypt the processed plaintext data if the third enterprise platform is a superior platform corresponding to the first enterprise platform, and then feed back the obtained encrypted processed data to the superior platform for approval.

[0043] Furthermore, this application also discloses an electronic device. FIG6 is a structural diagram of an electronic device 20 according to an exemplary embodiment. The content in the figure should not be considered as any limitation on the scope of use of this application.

[0044] Figure 6 is a schematic diagram of the structure of an electronic device 20 provided in an embodiment of this application. Specifically, the electronic device 20 may include: at least one processor 21, at least one memory 22, a power supply 23, a communication interface 24, an input / output interface 25, and a communication bus 26. The memory 22 stores a computer program, which is loaded and executed by the processor 21 to implement the relevant steps in the cross-platform encrypted information transmission method disclosed in any of the foregoing embodiments. Furthermore, the electronic device 20 in this embodiment may specifically be an electronic computer.

[0045] In this embodiment, the power supply 23 is used to provide operating voltage for each hardware device on the electronic device 20; the communication interface 24 can create a data transmission channel between the electronic device 20 and external devices, and the communication protocol it follows can be any communication protocol applicable to the technical solution of this application, and is not specifically limited here; the input / output interface 25 is used to acquire external input data or output data to the outside world, and its specific interface type can be selected according to specific application needs, and is not specifically limited here.

[0046] In addition, the memory 22, as a carrier for resource storage, can be a read-only memory, random access memory, disk or optical disk, etc. The resources stored thereon can include operating system 221, computer program 222, etc., and the storage method can be temporary storage or permanent storage.

[0047] The operating system 221 is used to manage and control the various hardware devices on the electronic device 20 and the computer program 222, which may be Windows Server, Netware, Unix, Linux, etc. In addition to including a computer program capable of performing the cross-platform encrypted information transmission method executed by the electronic device 20 as disclosed in any of the foregoing embodiments, the computer program 222 may further include computer programs capable of performing other specific tasks.

[0048] Furthermore, this application also discloses a computer-readable storage medium for storing a computer program; wherein, when the computer program is executed by a processor, it implements the aforementioned cross-platform encrypted information transmission method. Specific steps of this method can be found in the corresponding content disclosed in the foregoing embodiments, and will not be repeated here.

[0049] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the apparatus disclosed in the embodiments, since it corresponds to the method disclosed in the embodiments, the description is relatively simple; relevant parts can be referred to in the method section.

[0050] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0051] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be implemented directly by hardware, a software module executed by a processor, or a combination of both. The software module can be located in random access memory (RAM), main memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.

[0052] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0053] The technical solutions provided in this application have been described in detail above. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the above embodiments are only for the purpose of helping to understand the methods and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.

Claims

1. A cross-platform method for encrypted information transmission, characterized in that, The method, applied to a first enterprise platform, includes: generating a plaintext anomaly record data packet based on locally detected anomaly records, and encrypting the plaintext anomaly record data packet using a generated random root key to obtain a target encrypted anomaly record data packet; generating a target subkey based on the random root key and local platform information, and encrypting the target subkey using a preset encryption algorithm to obtain a target encrypted subkey; then encoding the target encrypted subkey and the target encrypted anomaly record data packet using a preset encoding algorithm to obtain a target anomaly record notification data packet; establishing a communication connection with a second enterprise platform through a message queue of a preset proxy server, and sending the target anomaly record notification data packet and the target encrypted subkey to the second enterprise platform after a successful connection, so that the second enterprise platform can decrypt the target anomaly record notification data packet based on the target encrypted subkey and process the decrypted plaintext anomaly record data packet; the second enterprise platform is a platform not on the same local area network as the first enterprise platform.

2. The cross-platform encrypted information transmission method according to claim 1, characterized in that, The step of generating plaintext abnormal record data packets based on locally detected abnormal records includes: if an abnormal record is detected, collecting abnormal data corresponding to the abnormal record according to a preset data type; performing a standardization operation on the abnormal data to obtain standardized abnormal data, and encapsulating the standardized abnormal data to encapsulate the standardized abnormal data into plaintext abnormal record data packets.

3. The cross-platform encrypted information transmission method according to claim 1, characterized in that, The step of encrypting the plaintext anomaly record data packet using a generated random root key to obtain a target encrypted anomaly record data packet includes: padding the plaintext anomaly record data packet based on a preset data length to obtain a padded data packet; generating a random root key based on a preset encryption algorithm and encrypting the padded data packet using the random root key to obtain an encrypted anomaly record data packet; generating an encryption integrity verification tag and binding the encryption integrity verification tag, the encrypted anomaly record data packet, and the key identifier corresponding to the random root key to obtain an encrypted anomaly record data packet to be encapsulated; and adding a local framework identifier and a local platform type field to the encrypted anomaly record data packet to be encapsulated to obtain the target encrypted anomaly record data packet.

4. The cross-platform encrypted information transmission method according to claim 2, characterized in that, The process of generating a target subkey based on the random root key and local platform information, encrypting the target subkey using a preset encryption algorithm to obtain a target encrypted subkey, and then encoding the target encrypted subkey and the target encrypted anomaly record data packet using a preset encoding algorithm to obtain a target anomaly record notification data packet includes: generating a subkey to be determined corresponding to the random root key based on the random root key, the local platform identifier, and the local framework identifier, and setting an effective time for the subkey to be determined based on a preset key period to obtain a target subkey; encrypting the target subkey using a preset encryption algorithm to obtain a target encrypted subkey, and encoding the target encrypted subkey and the target encrypted anomaly record data packet using a preset encoding algorithm. The method further includes: generating a target subkey based on the random root key and local platform information, encrypting the target subkey using a preset encryption algorithm to obtain a target encrypted subkey, and then encoding the target encrypted subkey and the target encrypted anomaly record data packet using a preset encoding algorithm to obtain a target anomaly record notification data packet. The method also includes: if the target subkey has exceeded its validity period, then proceeding to the step of generating a subkey to be determined corresponding to the random root key based on the random root key, the local platform identifier, and the local framework identifier, and setting a validity period for the subkey to be determined based on a preset key expiration date to obtain the target subkey, thereby using the newly generated key as the target subkey.

5. The cross-platform encrypted information transmission method according to claim 1, characterized in that, The step of establishing a communication connection with the second enterprise platform through the message queue of a preset proxy server, and sending the target anomaly record notification data packet and the target encryption subkey to the second enterprise platform after a successful connection, includes: sending a target connection request to the message queue of the preset proxy server to connect with the second enterprise platform, so that the preset proxy server can return the address information of the second enterprise platform to the local machine; establishing a connection with the second enterprise platform based on the address information, and sending the target anomaly record notification data packet and the target encryption subkey to the second enterprise platform after a successful connection.

6. The cross-platform encrypted information transmission method according to claim 4, characterized in that, The step of decrypting the target anomaly record notification data packet based on the target encryption subkey includes: decoding the target anomaly record notification data packet based on the preset encoding algorithm to obtain the target encryption subkey and the target encrypted anomaly record data packet; decrypting the target encryption subkey using the preset encryption algorithm to obtain the target subkey; and decrypting the target encrypted anomaly record data packet using the target subkey to obtain the plaintext anomaly record data packet.

7. The cross-platform encrypted information transmission method according to any one of claims 1 to 6, characterized in that, Also includes: If a pending exception record data packet is received from a third enterprise platform, the pending exception record data packet is decrypted to obtain the target pending plaintext data corresponding to the pending exception record data packet. The platform type of the third enterprise platform is determined. If the third enterprise platform is a subordinate platform corresponding to the first enterprise platform, the target plaintext data to be processed is approved, an approval completion notification is generated, and the approval completion notification is sent to the subordinate platform. If the third enterprise platform is the superior platform corresponding to the first enterprise platform, then the target plaintext data to be processed is processed, the processed plaintext data is encrypted, and the encrypted processed data is then fed back to the superior platform for approval.

8. A cross-platform encrypted information transmission device, characterized in that, The system, applied to a first enterprise platform, includes: a data packet encryption module for generating plaintext anomaly record data packets based on locally detected anomaly records, and encrypting the plaintext anomaly record data packets using a generated random root key to obtain a target encrypted anomaly record data packet; a data encoding module for generating a target subkey based on the random root key and local platform information, encrypting the target subkey using a preset encryption algorithm to obtain a target encrypted subkey, and then encoding the target encrypted subkey and the target encrypted anomaly record data packet using a preset encoding algorithm to obtain a target anomaly record notification data packet; and a data processing module for establishing a communication connection with a second enterprise platform through a message queue of a preset proxy server, and sending the target anomaly record notification data packet and the target encrypted subkey to the second enterprise platform after a successful connection, so that the second enterprise platform can decrypt the target anomaly record notification data packet based on the target encrypted subkey and process the decrypted plaintext anomaly record data packet; the second enterprise platform is a platform not on the same local area network as the first enterprise platform.

9. An electronic device, characterized in that, include: Memory, used to store computer programs; A processor for executing the computer program to implement the cross-platform encrypted information transmission method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, Used to store computer programs, wherein the computer programs, when executed by a processor, implement the cross-platform encrypted information transmission method as described in any one of claims 1 to 7.

Images