Data transmission method and device for intranet and extranet

Abstract

The application belongs to the technical field of network data transmission, and discloses a data internal and external network transmission method and equipment. The method comprises the following steps: in response to a transmission request of to-be-transmitted data, dividing the to-be-transmitted data according to fields; determining an encryption level according to the sensitivity level of the to-be-transmitted data; generating a plurality of key-value pairs by taking each field name as a key and taking field content as a value, to obtain structured data; mapping each field name into a field code according to a field mapping dictionary, and encrypting the field content according to the corresponding encryption level; and generating a message header comprising a field mapping dictionary identifier, an encryption level identifier and a data type identifier of the to-be-transmitted data; and packaging and transmitting the message header and the structured data. The application realizes the safe transmission of data between internal and external networks.

Description

Technical Field

[0001] This invention belongs to the field of data transmission technology, and in particular relates to a method and device for data transmission between internal and external networks. Background Technology

[0002] The statements in this section are merely background information related to the present invention and do not necessarily constitute prior art.

[0003] Currently, encrypted transmission of data between internal and external networks often employs a unified encryption standard. However, different types of data have varying sensitivities and encryption requirements. Based on this, existing technologies have proposed tiered encryption schemes based on data sensitivity. However, these encryption technologies still rely on overall encryption and cannot differentiate between sensitive fields within the data, leading to issues such as insufficient encryption of highly sensitive data and excessive encryption of less sensitive data. Furthermore, for internal enterprise financial data and contract data, in addition to the aforementioned problems, the control over external transmission is also a factor affecting information security. Currently, the focus is primarily on the encryption of the data itself, impacting enterprise information security management. Summary of the Invention

[0004] In view of this, the present invention provides a method and device for data transmission between intranet and extranet, for realizing secure file transmission.

[0005] One aspect of the present invention provides a data transmission method for internal and external networks, applied to a sender, comprising the following steps:

[0006] In response to a transmission request for data to be transmitted, the data to be transmitted is divided by field;

[0007] The encryption level is determined based on the sensitivity level of the data to be transmitted;

[0008] Multiple key-value pairs are generated using each field name as the key and the field content as the value, resulting in structured data;

[0009] Each field name is mapped to a field code according to the field mapping dictionary, and the field content is encrypted according to the corresponding encryption level; and a message header is generated, which includes a field mapping dictionary identifier, an encryption level identifier, and a data type identifier of the data to be transmitted.

[0010] The message header and structured data are packaged and transmitted.

[0011] In some embodiments, the data type of the data to be transmitted includes tabular data and text data; when the data to be transmitted is text data, dividing the data to be transmitted by field includes: analyzing the text structure, dividing the text data according to chapters, recording the chapter names as fields, and recording the content of each chapter as field content.

[0012] In some embodiments, after the data to be transmitted is divided by field, the sensitivity level of each field is evaluated to determine the encryption level of each field; the message header includes a mapping relationship between field encoding and encryption level identifier.

[0013] In some embodiments, the overall sensitivity level of the file is determined based on the sensitivity level of the data to be transmitted; the approval path is matched based on the overall sensitivity level; it is determined whether the data to be transmitted has passed all the approval procedures on the approval path. If so, field-level sensitivity identification is further performed; if not, the approval process is re-initiated.

[0014] In some embodiments, the enterprise organizational structure is obtained to build reporting links between positions from the bottom up; the number of approval levels is matched based on sensitivity levels, and approval paths are adaptively created based on the position and number of approval levels of the personnel transferring documents.

[0015] In some embodiments, multiple key-value pairs are generated using each field as the key and the field content as the value. After obtaining structured data, the size and hash value of the structured data are calculated, and the data size and hash value are written into the message header.

[0016] In some embodiments, at least one of the field mapping dictionary, encryption level identifier, and data type identifier is updated periodically.

[0017] A second aspect of the present invention provides a method for transmitting data between internal and external networks, applied to a receiver, wherein the receiver is communicatively connected to the sender, the method comprising the following steps:

[0018] Receive encrypted data and parse the message header to obtain the encryption level, field mapping dictionary, and data type;

[0019] The field name is obtained based on the field mapping dictionary, and the field content is obtained by decrypting it using the decryption algorithm corresponding to the encryption level.

[0020] Reconstruct the field names and field contents based on the data type to obtain the data to be transmitted.

[0021] In some embodiments, the data size and hash value are obtained based on the parsing of the message header; after obtaining the field name and field content, the data size and hash value are recalculated, and a data consistency judgment is performed.

[0022] A third aspect of the present invention provides an electronic device including a processor and a memory, wherein the memory stores computer instructions that, when executed by the processor, cause the electronic device to perform the method described thereon.

[0023] The above one or more technical solutions, through field-level sensitivity classification and dynamic encryption, ensure strong security for highly sensitive data while reducing the processing overhead of low-sensitivity data; they use field mapping dictionaries to decouple field names from content and enable scalable updates; the message header centrally carries metadata such as dictionary version, encryption level, and data type, enabling the receiving end to accurately decrypt and restore the data structure without relying on pre-configured settings, thus balancing security, flexibility, and system compatibility.

[0024] In addition, by decoupling the "overall-field level" sensitivity judgment and approval, we can avoid excessive approval of low-sensitivity documents and ensure that high-sensitivity fields are specifically encrypted after approval, which can significantly reduce the data leakage surface and improve transmission efficiency. Attached Figure Description

[0025] The accompanying drawings, which form part of this invention, are used to provide a further understanding of the invention. The illustrative embodiments of the invention and their descriptions are used to explain the invention and do not constitute an improper limitation of the invention.

[0026] Figure 1 A flowchart illustrating a data transmission method for intranet and extranet applications provided by an exemplary embodiment of this application is shown.

[0027] Figure 2 A flowchart illustrating a data transmission method for data recipients on internal and external networks provided in an exemplary embodiment of this application is shown. Detailed Implementation

[0028] Embodiments of this application will now be described in more detail with reference to the accompanying drawings. While some embodiments of this application are shown in the drawings, it should be understood that this application can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of this application. It should be understood that the drawings and embodiments of this application are for illustrative purposes only and are not intended to limit the scope of protection of this application.

[0029] In the description of the embodiments of this application, the term "comprising" and similar terms should be understood as open-ended inclusion, i.e., "including but not limited to". The term "based on" should be understood as "at least partially based on".

[0030] As described in the background section, existing methods for hierarchical encryption based on data sensitivity are still holistic encryption, failing to differentiate between different sensitive fields within the data. This leads to problems such as insufficient encryption of highly sensitive data and excessive encryption of low-sensitivity data, and does not fully consider the encryption needs of enterprises. The transmission method provided by one or more embodiments of the present invention achieves field-level hierarchical encryption while ensuring compliance during external transmission.

[0031] Figure 1 A flowchart illustrating an exemplary embodiment of this application provides a method for data transmission between internal and external networks applied to a data sender, comprising the following steps:

[0032] S101: In response to a request to send data to be transmitted, the data to be transmitted is divided into fields;

[0033] S102: Determine the encryption level based on the sensitivity level of the data to be transmitted;

[0034] S103: Generate multiple key-value pairs with each field name as the key and the field content as the value to obtain structured data;

[0035] S104: Map each field name to a field code according to the field mapping dictionary, encrypt the field content according to the corresponding encryption level, and generate a message header, which includes the version of the field mapping dictionary, the encryption level identifier, and the data type identifier of the data to be transmitted.

[0036] S105: Pack the message header and structured data and transmit them.

[0037] This method reduces the processing overhead of low-sensitivity data while ensuring strong security for highly sensitive data through field-level sensitivity classification and dynamic encryption; it decouples field names and content and enables scalable updates by using a field mapping dictionary; and it centrally carries metadata such as dictionary version, encryption level, and data type in the message header, enabling the receiving end to accurately decrypt and restore the data structure without relying on pre-configured settings, thus balancing security, flexibility, and system compatibility.

[0038] In step S101, the data types of the data to be transmitted include tabular data and text data. For example, tabular data includes financial data such as vouchers, ledgers, and reports, while text data includes contract text.

[0039] When the data to be transmitted is text data, dividing the data by field includes: analyzing the text structure, dividing the text data according to chapters, designating chapter names as fields, and designating the content of each chapter as field content. For example, for a contract text, chapter names such as "Contract Subject," "Contract Clauses," and "Liability for Breach of Contract" can be used as fields, and the specific content of the corresponding chapters can be used as field content. In this way, the structural integrity and logical coherence of the text data can be ensured during transmission.

[0040] In step S102, the encryption level is determined based on the sensitivity level of the data to be transmitted. Encryption levels can be divided into multiple levels, such as low, medium, and high, corresponding to different encryption algorithms and key lengths. This hierarchical encryption improves transmission efficiency while ensuring data security. Therefore, different fields can employ different encryption algorithms based on their sensitivity, ensuring the security of highly sensitive data while avoiding unnecessary system overhead caused by over-encrypting low-sensitivity data.

[0041] For example, a basic AES-128 algorithm is used when the encryption level is low; an AES-256 algorithm is used when the encryption level is medium; and a combined encryption algorithm such as AES+RSA is used when the encryption level is high. This process ensures the security and integrity of the data, preventing errors or information loss during decryption.

[0042] In step S103, multiple key-value pairs are generated using each field name as the key and the field content as the value, resulting in structured data. For example, for the "Contract Subject" field in the contract text, key-value pairs such as {"Contract Subject":"Party A XXX Company, Party B YYY Company"} can be generated.

[0043] Furthermore, after generating structured data in step S103, the size and hash value of the structured data are calculated, and these values ​​are written into the message header for the receiver to verify data integrity. This ensures that the data is not tampered with during transmission.

[0044] In step S104, a pre-configured mapping table is created, consisting of field mapping dictionary identifiers and version mapping tables, encryption level identifiers and encryption algorithm mapping tables, and data type identifiers and data type mapping tables. These mapping tables can have multiple versions and can be stored in the same or different paths. The message body also provides the retrieval address for each of the corresponding field mapping dictionary identifier, encryption level identifier, and data type identifier. The versions and / or addresses of the field mapping dictionary mapping table, encryption level mapping table, and data type mapping table are updated periodically. Because the addresses may change, the mapping table versions may also change, effectively increasing the difficulty of cracking, adapting to constantly changing security requirements, and improving data security.

[0045] The field mapping dictionary is a predefined mapping table used to convert plaintext field names into encoded forms, increasing transmission security. For example, "Contract Subject" might be mapped to "A001," and "Contract Terms" might be mapped to "A002." The field mapping dictionary is updated periodically to enhance security. This mapping effectively prevents data from being illegally intercepted and interpreted during transmission.

[0046] Generate a message header, which includes a field mapping dictionary identifier, an encryption level identifier, and a data type identifier for the data to be transmitted. The message header specifies the mapping relationship between the field mapping dictionary and the encryption level identifier, ensuring that the receiver can determine the correct decryption method based on the field encoding. The data type identifier for the data to be transmitted ensures that the receiver can reconstruct the data content from a table or text format.

[0047] In step S105, the message header and structured data are packaged and transmitted. The packaging process combines the message header and structured data into a complete data packet, which is then sent to the target receiver according to a predetermined transmission protocol. This ensures that data is not lost or corrupted during transmission.

[0048] In response to a data transfer request, the system also retrieves the approved path for the data. Based on the encryption level of the data, the approved path is verified to determine if the approval process is compliant. Data transfer only proceeds after the approval process is deemed compliant. This ensures that the transfer of sensitive data complies with the organization's internal control requirements. This rigorous approval process effectively prevents unauthorized data transfer.

[0049] Finally, the message header and structured data are packaged and transmitted. The packaging process combines the message header and structured data into a single complete data packet, which is then sent to the target receiver according to a predetermined transmission protocol. This method ensures that data is not lost or corrupted during transmission.

[0050] For example, the message header uses JSON format and includes the following required fields: {dict, encryption, data_info, fields_order}. Here, dict includes the dictionary identifier for the field mappings and the download address; encryption indicates the encryption level; data_info stores metadata such as the data type, size, and hash value of the file to be transmitted; and fields_order stores the ordered array of field encodings to reconstruct the original structure. To prevent special characters from corrupting the transmission protocol, the entire message header is Base64 encoded and encapsulated with the message body using a 4-byte prefix for transmission.

[0051] Through the steps described above, this method enables secure and efficient transmission of different types of data, and is particularly suitable for data transmission scenarios containing sensitive information. This method effectively improves the security and reliability of data transmission.

[0052] The aforementioned sensitivity-level-based encryption method is implemented based on the overall sensitivity of the file to be transmitted. However, in reality, not all fields in a file are highly sensitive. Undifferentiated encryption of all fields without differentiation can easily lead to unnecessary system overhead. Furthermore, the external transmission of enterprise files requires control. Currently, the control method for highly sensitive files typically involves prior approval before transmission. However, the current approval process and its correlation with file sensitivity levels are artificially set. Approval conditions and paths are defined, requiring the file sender to apply for approval in advance. For example, regulations might specify which personnel must review financial data exceeding a certain amount. However, there is a lack of monitoring regarding the sensitivity of uploaded files and the compliance of the approval path. The system allows transmission as soon as approval is detected, which is detrimental to enterprise data security.

[0053] Based on this, in some embodiments, in step S102, the overall sensitivity level of the file is first determined according to the sensitivity level of the data to be transmitted; the approval path is matched according to the overall sensitivity level; it is determined whether the data to be transmitted has passed all the approval procedures on the approval path. If yes, field-level sensitivity identification is further performed; if no, the approval process is re-initiated.

[0054] For example, the data to be transmitted is financial data. A primary risk item and other risk items are distinguished, and scoring rules are set for each. The sensitivity level is determined based on the total score of the primary and other risk items. For instance, the maximum sensitivity level is set to 5, the score range for the primary risk item is 1-5, and the range for other risk items is 0-2. The overall sensitivity level of the financial data is calculated as follows: Sensitivity Level = min(5, Primary Risk Item Score + ceil(Cumulative Score of Other Risk Items / 2)), where the ceil function represents upward calculus. Based on this calculation method, if the primary risk item score is already high, such as 5, even if all other risk items are 0, the overall score is still 5. The accumulation of other risk items may increase sensitivity; therefore, the impact of other risk items is compressed to a score increment of 0-2. The ceil function ensures that even a small contribution adds at least 1, preventing the transmission risk from being underestimated.

[0055] Taking vouchers as an example, the main risk item is the privacy information strength P, with a value range of 1-5. If it contains bank card / ID number, the value is 5; if it only contains the full name of the customer / supplier, the value is 3; and if it contains neither of the above information, the value is 1. Other risk items include the amount level A (based on the percentage of a single transaction amount to the annual revenue), the number of times it has been transmitted externally T (including this transmission), and the document timeliness Δt (days since creation). The percentage of a single transaction amount to the annual revenue is assigned different values ​​depending on the range. For example, if it is greater than or equal to 1%, A is assigned 5; within the range [0.5%, 1%), A is assigned 4; within the range [0.1%, 0.5%), A is assigned 3; within the range (0, 0.1%), A is assigned 2; and if it is 0, A is assigned 1. "Transmitted externally" can be understood as having been approved; the more times it has been transmitted, the lower the risk. The more days since creation, the lower the document timeliness Δt. Voucher sensitivity level = min(5, P + ceil((A + T + Δt) / 2)).

[0056] Taking ledgers as an example, the main risk item is the importance of the account (S). For accounts such as paid-in capital, main business revenue, cash, and bank deposits, the value is 5. For accounts receivable / payable, expenses, etc., the score decreases accordingly. Other risk items include customer / supplier importance (C), balance as a percentage of net assets (B), and document timeliness (Δt). The higher the customer / supplier importance, the larger the value of C; the higher the balance as a percentage of net assets, the larger the value of B; and the more days since creation, the lower the document timeliness (Δt). Ledger sensitivity level = min(5, S + ceil((C + B + Δt) / 2)).

[0057] Taking the report as an example, the main risk item is the forecast attribute F. If it includes revenue / profit forecasts, it is assigned a value of 5. If it includes cost / expense forecasts and balance sheet forecasts, the score decreases accordingly. Other risk items include forecast shock I and document timeliness Δt. Forecast shock I represents the amount of change of the forecast value relative to the current value. Report sensitivity level = min(5, F + ceil((Δt + I) / 2)).

[0058] For example, the data to be transmitted is contract data. A primary risk item and other risk items are distinguished, and scoring rules are set for each. The sensitivity level is determined based on the total score of the primary and other risk items. For instance, the maximum sensitivity level is set to 5, the score range for the primary risk item is 1-5, and the range for other risk items is 0-2. The primary risk item C is determined based on the contract type and the type of sensitive clauses. Contract types include strategic / framework contracts, procurement / sales contracts, labor contracts, etc. Sensitive clauses include confidentiality, price, technology, intellectual property, exclusivity, and performance-based clauses, etc. Different types of contracts have pre-set scores for containing different types of sensitive clauses. Other risk items include contract amount level A, partner importance B, number of external transmissions T, and document timeliness Δt. The higher the contract amount, the larger A value; the more important the partner, the larger B value; the more times the data has been externally transmitted, the smaller T value; and the more days since creation, the lower the document timeliness Δt. Contract sensitivity level = min(5, C + ceil((A + B + T + Δt) / 3)).

[0059] The approval path includes single-level and multi-level approvals; the higher the sensitivity, the more approval levels there are. Optionally, the company's organizational structure and job positions can be obtained to build a reporting chain between positions from the bottom up. The number of approval levels is matched based on the sensitivity level, and the approval path is adaptively created based on the position and number of approval levels of the personnel transmitting the document. For example, a financial data reporting chain could be: Finance Department Funds Specialist, Funds Supervisor, Finance Manager, Legal Head, Legal Manager; a contract data reporting chain could be: Procurement Supervisor, Finance Manager, Legal Manager, CFO / CEO. Based on this, if the company's organizational structure changes or there are job changes, the reporting chain can be updated adaptively, and the approval path determined based on the sensitivity of the data to be transmitted can also be updated accordingly.

[0060] After determining that the data to be transmitted has passed all approval procedures along the prescribed approval path, the sensitivity level of each field is assessed to determine the encryption level for each field, thereby achieving tiered encryption at the field level. For financial data, the assessment process comprehensively considers the data's commercial value, privacy level, and legal compliance requirements. For example, bank account information is typically rated as highly sensitive and requires the highest level of encryption, while publicly available financial statement data may be rated as low sensitive and require a lower level of encryption. For contract texts, the assessment process considers the importance of the clauses, confidentiality requirements, and legal risks. For example, price terms and confidentiality clauses are typically rated as highly sensitive, while general descriptions may be rated as low sensitive. This assessment ensures that data is appropriately protected during transmission. For example, the sensitivity level of each field can be determined by setting a mapping relationship between fields and sensitivity levels. It is important to note that the maximum sensitivity level of a field cannot exceed the overall sensitivity level of the data to be transmitted.

[0061] By decoupling sensitivity assessment and approval at both the overall and field levels, excessive approval of low-sensitivity documents is avoided, while ensuring that highly sensitive fields are specifically encrypted after approval. This significantly reduces the data leakage surface and improves transmission efficiency. The approval process is synchronized with the enterprise's organizational structure in real time, eliminating the need for manual maintenance of workflow templates when positions change or rules are adjusted.

[0062] Figure 2 A flowchart illustrating an exemplary embodiment of this application provides a method for data transmission between internal and external networks applied to a data receiver, comprising the following steps:

[0063] S201: Receive encrypted data and parse the message header to obtain the encryption level, field mapping dictionary, and data type;

[0064] S202: Obtain the field name based on the field mapping dictionary, and decrypt the field content based on the decryption algorithm corresponding to the encryption level;

[0065] S203: Reconstruct the field names and field contents according to the data type to obtain the data to be transmitted.

[0066] In step S201, the system receives an encrypted data packet from the sender. This data packet consists of a message header and an encrypted data body. The system performs preliminary processing on the received data packet to extract key information from the message header. This information includes the encryption level, field mapping dictionary, and data type. The encryption level can be divided into three levels: low, medium, and high, corresponding to encryption algorithms of different complexities. The field mapping dictionary provides the correspondence between the original field names and the encrypted field names. The data type specifies the data format, including tables and text.

[0067] In step S202, based on the parsed field mapping dictionary, the encrypted field names are obtained and mapped back to the original field names. Then, the system selects the appropriate decryption algorithm to decrypt the field content according to the encryption level in the message header.

[0068] In step S203, based on the parsed data type, the obtained field names and field contents are reorganized to reconstruct the original data format. For example, if the data type is a table, the field names and field contents are reorganized into a table; if the data type is text, it is reconstructed into text. This step ensures the readability and usability of the data after decryption, enabling the recipient to correctly understand and use the data.

[0069] Step S202 also performs data consistency verification. Specifically, in addition to the information parsed in step S201, the system extracts two verification pieces of information from the message header: data size and hash value. The data size is in bytes, and the hash value is usually generated using algorithms such as SHA-256 or MD5. This information is used for subsequent consistency verification to ensure that the data has not been tampered with during transmission. Based on the data reconstructed in step S202, the data size and hash value are recalculated. The data size is obtained by calculating the byte length of the reconstructed data; the hash value is calculated using the same hash algorithm as the sender. The data size and hash value extracted from the message header are compared with the recalculated data size and hash value. If the two sets of values ​​are completely consistent, it indicates that the data has not been tampered with during transmission, and the consistency check passes; if there is an inconsistency, it indicates that the data may have been tampered with or that an error occurred during transmission, and the system will refuse to receive the data and request retransmission from the sender. This mechanism effectively ensures the security and reliability of the data, ensuring that the data maintains its original state during transmission.

[0070] In a preferred embodiment, when performing data consistency checks, the system also records the results and generates logs, including information such as data reception time, data source, and consistency check results, for subsequent auditing and troubleshooting. These records provide strong support for the system's security and traceability, ensuring that problems can be quickly located and resolved.

[0071] Using the methods described above, the system can securely receive and parse encrypted data, and ensure data integrity and reliability through consistency checks, effectively preventing data from being tampered with or damaged during transmission. This method has significant application value in the field of data transmission, providing users with enhanced security and a better data transmission experience.

[0072] based on Figure 1 The provided transmission method, in embodiments of the present invention, also provides a data intranet / extranet transmission device applied to a sender, comprising: a source data receiving module configured to, in response to a transmission request for data to be transmitted, divide the data to be transmitted by field; an encryption level determination module configured to, determine an encryption level based on the sensitivity level of the data to be transmitted; a data encryption module configured to, using each field name as a key and the field content as a value, generate multiple key-value pairs to obtain structured data; map each field name to a field code according to a field mapping dictionary, encrypt the field content according to the corresponding encryption level; generate a message header, the message header including a field mapping dictionary identifier, an encryption level identifier, and a data type identifier of the data to be transmitted; and package and transmit the message header and the structured data.

[0073] based on Figure 2The provided transmission method, in an embodiment of the present invention, also provides a data transmission device for intranet and extranet, applied to a receiver, comprising: an encrypted data receiving module configured to receive encrypted data and obtain an encryption level, a field mapping dictionary, and a data type based on message header parsing; a data decryption module configured to obtain field names based on the field mapping dictionary and decrypt the field content based on the decryption algorithm corresponding to the encryption level; and a data reconstruction module configured to reconstruct the field names and field content according to the data type to obtain the data to be transmitted.

[0074] The memory in this embodiment of the invention is used to store various types of data to support, for example... Figure 1 or Figure 2 The execution of the method shown.

[0075] It is understood that the memory can be volatile memory or non-volatile memory, or it may include both volatile and non-volatile memory. The memory in this embodiment of the invention is capable of storing, for example... Figure 1 or Figure 2 The computer programs corresponding to each step in the method shown are as follows. The operating system contains various system programs, such as the framework layer, core library layer, and driver layer, used to implement various basic business functions and handle hardware-based tasks. Application programs can contain various other applications.

[0076] As an example, a processor can be an integrated circuit chip with signal processing capabilities, such as a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc., where a general-purpose processor can be a microprocessor or any conventional processor, etc.

[0077] Specifically, according to embodiments of this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program including functions for executing... Figure 1 or Figure 2 The program code for the method shown. In such an embodiment, the computer program can be downloaded and installed from a network via a communication component, and / or installed from a removable medium. When the computer program is executed by the central processing unit, it performs the various functions defined in the apparatus of this application.

[0078] in, Figure 1 or Figure 2The computer program instructions corresponding to the method shown may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in the process. Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0079] The above description is merely a preferred embodiment of the present invention and is not intended to limit the invention. Various modifications and variations can be made to the present invention by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

Claims

1. A data interworking transmission method, applied to a sender, characterized in that, The method comprises the following steps: dividing the to-be-transmitted data by field in response to a transmission request of the to-be-transmitted data; the data type of the to-be-transmitted data comprises table data and text data, the table data is financial data, including vouchers, account books and reports, and the text data is contract text; distinguishing main risk items and other risk items, setting score rules of the main risk items and the other risk items respectively, and judging the overall sensitivity level according to the total scores of the main risk items and the other risk items; matching an approval path according to the overall sensitivity level; judging whether the to-be-transmitted data has passed all approval procedures on the approval path, and if not, reinitiating an approval process; if yes, further performing field-level sensitivity identification, evaluating the sensitivity level of each field, and determining the encryption level of each field; generating a plurality of key-value pairs with each field name as a key and field content as a value to obtain structured data; mapping each field name to a field code according to a field mapping dictionary, encrypting the field content according to the corresponding encryption level, and generating a message header, wherein the message header comprises a field mapping dictionary identifier, an encryption level identifier, a data type identifier of the to-be-transmitted data, and a mapping relationship between the field code and the encryption level identifier; packing and transmitting the message header and the structured data; the approval path comprises one-level approval and multi-level approval, and the method further comprises the following steps: obtaining an enterprise organizational structure and a post setting, and constructing a reporting link between posts from bottom to top; 2. The data transmission method according to claim 1, wherein, matching the number of approval levels based on the sensitivity level, and adaptively creating an approval path based on the post of the file transmission personnel and the number of approval levels.

3. The data transmission method according to claim 1, wherein, When the to-be-transmitted data is text data, the step of dividing the to-be-transmitted data by field comprises the following steps:

4. The data transmission method according to claim 1, wherein, analyzing a text structure, dividing the text data by chapter, recording chapter names as fields, and recording chapter contents as field content.

5. A data interworking transmission method applied to a receiving party, wherein the receiving party is connected with a sending party in the method according to any one of claims 1-4, characterized in that, After generating a plurality of key-value pairs with each field as a key and field content as a value to obtain structured data, the method further comprises the following steps: calculating the size and the hash value of the structured data, and writing the size and the hash value into the message header. At least one of the field mapping dictionary, the encryption level identifier and the data type identifier is updated periodically. The method comprises the following steps:

6. The data transmission method of claim 5, wherein, receiving encrypted data, and obtaining an encryption level, a field mapping dictionary and a data type based on message header analysis; 7. An electronic device, comprising: obtaining a field name based on the field mapping dictionary, and obtaining field content by decryption based on a decryption algorithm corresponding to the encryption level; reconstructing the field name and the field content according to the data type to obtain to-be-transmitted data. The method further comprises the following steps: obtaining the size and the hash value based on the message header analysis; after obtaining the field name and the field content, recalculating the size and the hash value, and performing data consistency judgment. The electronic device comprises a processor and a memory, and the memory stores computer instructions, which, when executed by the processor, cause the electronic device to perform the method of any one of claims 1 to 4.

Images