Https protocol data forwarding system for ultrahigh frequency data

Abstract

The invention discloses an https protocol data forwarding system for ultrahigh frequency data, and relates to the technical field of data forwarding, the forwarding system comprises a client initialization module, the client initialization module comprises a hardware adaptation layer, a data forwarding layer and a data forwarding layer, the hardware adaptation layer is based on reader-writer development boards of different architectures, generating a binary running file matched with the hardware architecture through a cross compiling tool chain; the library function integration layer is used for integrating an encryption module and a URL (Uniform Resource Locator) analysis module of a Curl library, and loading to a development board system in a dynamic link library or static link library form; and a data processing interface. On the premise of guaranteeing the data transmission security, the transmission efficiency of the ultrahigh frequency data and the stability of the system are greatly improved, many problems in the prior art are effectively solved, and the ultrahigh frequency data transmission system has remarkable innovativeness and practicability, can be widely applied to various scenes with strict requirements on ultrahigh frequency data transmission, and has wide application prospects. And a powerful technical support is provided for the development of related fields.

Description

Technical Field

[0001] The present invention relates to the technical field of data forwarding, and in particular to an HTTPS protocol data forwarding system for ultra-high frequency data. Background Art

[0002] In today's digital age, the efficiency, security, and reliability of data transmission are crucial. Ultra-high frequency data transmission plays a key role in many fields such as the Internet of Things, industrial automation, and financial transactions. At the same time, with the development of network technology, the HTTPS protocol has become an important means to ensure the security of data transmission.

[0003] Because TCP data is transmitted in plain text, any node along the network transmission path (such as routers, switches, and network operators) can easily eavesdrop, view, or even modify the transmitted content using packet capture tools (such as Wireshark), compromising data transmission security. Therefore, we propose an HTTPS protocol data forwarding system for ultra-high-frequency data to address the aforementioned technical issues. Summary of the Invention

[0004] The purpose of the present invention is to provide an HTTPS protocol data forwarding system for ultra-high frequency data to solve the problems raised in the above background technology.

[0005] To achieve the above-mentioned purpose, the present invention adopts the following technical solution: the forwarding system includes: The client initialization module includes: a hardware adaptation layer: based on reader development boards of different architectures, a binary running file matching the hardware architecture is generated through a cross-compilation tool chain; a library function integration layer: an integrated encryption module and a URL parsing module of the Curl library are loaded into the development board system in the form of a dynamic link library or a static link library; a data processing interface: a standardized API interface is provided to realize the conversion and mapping of ultra-high frequency data and https request bodies; The certificate management module includes: storage structure: the certificate file is stored in a format containing the server public key, private key and CA root certificate chain, and the storage path is the directory of the development board file system; verification mechanism: through the structure configuration verification parameters, the certificate validity period, domain name matching and CA signature validity are verified, and dynamic loading of certificates is supported; debug mode: an environment variable switch is provided, and when it is turned on, the certificate chain verification is skipped and only basic format verification is performed; The server module includes: a URL parsing component that supports absolute URL and relative URL parsing; a connection management component that maintains the https connection pool, supports long connections, and automatically handles reconnection logic.

[0006] As a preferred solution, the encryption transmission mechanism of the client reader module is specifically as follows: Handshake phase: The client sends a message, the server returns a message, the client verifies the certificate, and both parties generate a shared key; Data transmission stage: Application layer data is encrypted, and each data packet is accompanied by an authentication tag to achieve encrypted transmission and ensure data integrity and non-tamperability.

[0007] As a preferred solution, the migration process of the certificate management module includes: Certificate format conversion: package the PEM format certificate, private key and CA certificate into a format file; Permission configuration: Set file permissions to ensure that only the root user and the reader / writer process can read; Environment variable configuration: Specify the CA root certificate path.

[0008] As a preferred solution, the debugging mode of the server module is implemented as follows: In the server software configuration file, add SSL parameters and disable client certificate verification; Record all connection requests in debug mode in the log system, including the source IP address, request time, URL path, and some data bytes.

[0009] As a preferred solution, the forwarding method includes the following specific steps: S1: Client initialization: S11. Generate a dynamic library that supports TLS; S12, transplant verification, the transplant verification is to update the dynamic library cache, check whether the library dependencies are complete, and ensure correct linking; S2: Certificate Management: S21, certificate verification logic, when the server requires certificate verification, enable certificate verification, verify the domain name match, and convert the error code into readable information; S22. Switch to debug mode. Define macros in the code. When DEBUG is defined, set verification to disable. S3: Data forwarding: S31, URL parsing, setting target URL; S32. Request construction, wherein the request construction is a data payload, the UHF data is serialized into JSON format, and conversion rules between the UHF data and the https request body are set; S33, connection establishment, the connection establishment is DNS resolution, calling the system function to resolve the IP address corresponding to the domain name; S34. Data transmission, using the curl interface to achieve concurrent transmission.

[0010] As a preferred solution, the conversion rules between the UHF data and the https request body are as follows: The tag EPC is mapped to the JSON field "epc"; Signal strength RSSI is mapped to "rssi" with an accuracy of 1 decimal place. The read timestamp is mapped to "timestamp" in milliseconds.

[0011] As a preferred solution, the collaborative mechanism of asymmetric encryption and symmetric encryption is: Handshake phase: Both parties calculate the shared key using the ECDHE algorithm; Key derivation: derive data encryption keys and authentication keys; Data transmission: The sending end encrypts each data packet, and the receiving end decrypts it through OpenSSL.

[0012] As a preferred solution, the client reader module supports the breakpoint resume function, specifically: When data transmission is interrupted, the offset of the sent bytes is recorded and stored on the development board; After reconnection, data will be transferred through http.

[0013] As a preferred solution, the system supports data compression transmission.

[0014] As a preferred solution, the server module provides a data receiving callback interface, specifies the callback address through the http response header, and the response body contains the processing status code and error details.

[0015] Compared with the prior art, the present invention has obvious advantages and beneficial effects. Specifically, it can be seen from the above technical solution that: The HTTPS protocol data forwarding system for ultra-high frequency data of the present invention, through its unique hardware adaptation, software integration, certificate management and server-side optimization design, greatly improves the transmission efficiency of ultra-high frequency data and the stability of the system while ensuring the security of data transmission, effectively solves many problems existing in the existing technology, has significant innovation and practicality, can be widely used in various scenarios with strict requirements for ultra-high frequency data transmission, and provides strong technical support for the development of related fields.

[0016] In order to more clearly illustrate the structural features and effects of the present invention, the present invention is described in detail below with reference to the accompanying drawings and specific embodiments. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Figure 1 is a general block diagram of a forwarding system according to an embodiment of the present invention; Figure 2This is a sub-block diagram of a forwarding system according to an embodiment of the present invention. DETAILED DESCRIPTION

[0018] In order to make the purpose, technical solutions and advantages of the present invention more clearly understood, the present invention will be further described in detail below with reference to the accompanying drawings and implementation examples. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not intended to limit the present invention.

[0019] It should be noted that when an element is referred to as being "fixed to" another element, it may be directly attached to the other element or there may be an intermediate element. When an element is referred to as being "connected to" another element, it may be directly connected to the other element or there may be an intermediate element. The terms "vertical," "horizontal," "left," "right," and similar expressions used herein are for illustrative purposes only.

[0020] See also Figures 1 to 2 , an embodiment of the present invention provides an HTTPS protocol data forwarding system for ultra-high frequency data, including: Client initialization module: Hardware adaptation layer: Based on reader development boards of different architectures such as ARM, x86, or MIPS, a binary runtime file matching the hardware architecture is generated through a cross-compilation tool chain (such as GCC for ARM); Library function integration layer: Integrates the encryption module (implementing RSA asymmetric encryption and AES symmetric encryption algorithms) of the OpenSSL library (version ≥ 1.1.1) and the URL parsing module (supporting the HTTP / 2 protocol stack and TLS handshake process) of the Curl library (version ≥ 7.68.0), and loads them into the development board system via a dynamic link library (.so file) or a static link library (.a file); Data processing interface: Provides standardized API interfaces (such as read_uhf_data(*) and send_https_data(*)) to implement the conversion and mapping of ultra-high frequency data (formatted as ISO18000-6C protocol frames) and https request bodies (JSON / XML format); Certificate Management Module: Storage Structure: Uses PKCS#12 format to store certificate files (.p12), including the server public key, private key, and CA root certificate chain. The storage path is the / etc / https_certs / directory of the development board's file system. Verification Mechanism: Configures verification parameters through the X509_VERIFY_PARAM structure of OpenSSL to verify the certificate validity period, domain name matching (subjectAltName field), and CA signature validity. Dynamic loading of certificate revocation lists (CRLs) is supported. Debug Mode: Provides an environment variable switch (DEBUG_CERT=1). When enabled, it skips certificate chain verification and only performs basic format verification. Server module: URL parsing component: supports absolute URL (such as https: / / api.uhf-system.com / data / upload) and relative URL parsing, including domain name (api.uhf-system.com), port (443), path ( / data / upload) and query parameter parsing functions; connection management component: maintains https connection pool, supports Keep-Alive long connection (timeout is configurable, default is 300 seconds), and automatically handles reconnection logic (attempts to reconnect 3 times when network is interrupted, with intervals of 5 seconds, 10 seconds, and 20 seconds); data receiving interface: follows the RESTfulAPI specification, provides POST method to receive data, and the request header includes Content-Type (application / json), User-Agent (UHF-Reader / 1.0) and custom authentication Header (X-UHF-Api-Key).

[0021] The encryption transmission mechanism of the client reader module is specifically as follows: Handshake phase: Using the TLS 1.3 protocol, the client sends a ClientHello message, and the server returns a Certificate and ServerHelloDone message. The client verifies the certificate using the OpenSSL SSL_verify_server_cert(*) function, and both parties use the ECDHE algorithm to generate a shared key. Data transmission phase: Application-layer data is encrypted using the AES-256-GCM algorithm. Each data packet is accompanied by a 128-bit AEAD authentication tag. Encrypted data is sent using OpenSSL's SSL_write(*) function, and decrypted data is received using the SSL_read(*) function. This ensures data integrity (HMAC-SHA256 checksum) and immutability.

[0022] The migration process of the certificate management module includes: Certificate format conversion: Use the OpenSSL command (opensslpkcs12-export) to package the PEM format certificate, private key, and CA certificate into a PKCS#12 format file.

[0023] Permission configuration: Set the file permission to 644 (-rw-r--r--) to ensure that only the root user and the reader / writer process can read it.

[0024] Environment variable configuration: Add exportSSL_CERT_FILE= / etc / https_certs / ca.crt to the / etc / profile of the development board to specify the CA root certificate path.

[0025] The debugging mode of the server module is implemented as follows: In the configuration file of server software such as Nginx / Apache, add the parameter ssl_verify_clientoff; to disable client certificate verification.

[0026] Records all connection requests in debug mode in the log system, including the source IP address, request time, URL path, and the first 1024 bytes of the data payload.

[0027] A method for forwarding HTTPS protocol data for ultra-high frequency data, the forwarding method comprising the following specific steps and parameter configurations: S1: Client initialization S11. Library compilation parameters: Use . / configure --prefix= / usr / local / openssl --with-arch=arm64 --enable-shared to configure OpenSSL, and use make&&makeinstall to complete the compilation; use . / configure --with-ssl= / usr / local / openssl --enable-threads for Curl to generate a dynamic library that supports TLS.

[0028] S12. Porting verification: Update the dynamic library cache using the ldconfig command, execute ldd / usr / bin / uhf-reader to check whether the library dependencies are complete, and ensure that libssl.so and libcurl.so are correctly linked. S2: Certificate Management Process S21. Certificate verification logic: When the server requires certificate verification, enable certificate verification through curl_easy_setopt(curl,CURLOPT_SSL_VERIFYPEER,1L), verify the domain name match through CURLOPT_SSL_VERIFYHOST,2L, and convert the error code into readable information through curl_easy_strerror(*).

[0029] S22. Debug mode switch: Define the #ifdefDEBUG macro in the code. When DEBUG is defined, set curl_easy_setopt(curl,CURLOPT_SSL_VERIFYPEER,0L) to disable verification. S3: Data forwarding process S31. URL parsing: Use curl_easy_setopt(curl,CURLOPT_URL,"https: / / example.com / uhf") to set the target URL, which is internally parsed into components such as domain name, port, and path through cURL's url_parser library.

[0030] S32. Request construction: Header settings: curl_easy_setopt(curl,CURLOPT_httpHEADER,header_list), including "Content-Type:application / json" and "Accept: / ".

[0031] Data payload: Serialize UHF data (such as tag EPC and RSSI values) into JSON format and set the request body through curl_easy_setopt(curl,CURLOPT_POSTFIELDS,post_data).

[0032] S33, connection establishment: execute curl_easy_perform(curl), the internal process is: DNS resolution: Call the system getaddrinfo(*) function to resolve the IP address corresponding to the domain name.

[0033] TLS handshake: The handshake is completed through OpenSSL's SSL_connect(*), taking ≤500ms (when the network is good).

[0034] S34, Data transmission: Use curl's multi interface to implement concurrent transmission, support processing ≥10 readers' data requests at the same time, and set the timeout for each request to 30 seconds (CURLOPT_TIMEOUT_MS, 30000).

[0035] The conversion rules between the UHF data and the https request body are as follows: The tag EPC (128-bit hexadecimal string) is mapped to the JSON field "epc".

[0036] The signal strength RSSI (-100dBm to 0dBm) is mapped to "rssi" with an accuracy of 1 decimal place.

[0037] The read timestamp (Unix timestamp) is mapped to "timestamp" in milliseconds.

[0038] The collaborative mechanism of asymmetric encryption and symmetric encryption is: Handshake phase: The client generates a random number client_random, the server returns server_random, and both parties calculate the shared key master_secret using the ECDHE algorithm (using the P-256 curve), which takes ≤ 100ms.

[0039] Key derivation: The data encryption key (enc_key) and authentication key (auth_key) are derived from the master_secret using the HKDF algorithm (the hash function uses SHA-256). Both are 32 bytes long.

[0040] Data transmission: Each data packet is encrypted using AES-256-GCM mode, with a 12-byte nonce value appended (incremented each time it is sent). The ciphertext is followed by a 16-byte tag. Encryption and decryption are implemented using OpenSSL's EVP_AEAD_CTX_seal(*) and EVP_AEAD_CTX_open(*) functions.

[0041] The client reader module supports the breakpoint resume function, specifically: When data transmission is interrupted, the offset of the sent bytes is recorded and stored in the / var / run / uhf_transfer.state file on the development board.

[0042] After reconnection, data is continued through the HTTP Range header (such as Range:bytes=1024-), supporting a maximum breakpoint offset of 10MB.

[0043] The system supports data compression transmission. Request server-side compression through curl_easy_setopt(curl,CURLOPT_ACCEPT_ENCODING,"gzip,deflate"), and use deflate (compression level 6) as the compression algorithm. The compression rate can reach 30%-50%.

[0044] The server module provides a data receiving callback interface, and specifies the callback address through the X-UHF-Callback-URL in the http response header. The response body contains the processing status code (200 for success, 400 for parameter error, 500 for server error) and error details.

[0045] In summary, through the hardware adaptation layer in the client initialization module, a cross-compilation toolchain is used to generate binary executable files that precisely match the hardware architecture of reader development boards with different architectures. This design enables the system to be compatible with a wide range of hardware devices, whether common x86 architecture or specialized embedded architecture development boards, ensuring stable operation at the hardware level. This greatly expands the system's application scenarios, reduces development and deployment costs due to hardware differences, and improves the system's scalability and versatility. At the library function integration layer, the encryption module and the Curl library's URL parsing module are integrated and flexibly loaded into the development board system via dynamic or static link libraries. The integration of the encryption module ensures the security of ultra-high-frequency data during transmission, preventing data theft or tampering. The Curl library's URL parsing module provides powerful support for network data transmission, efficiently processing various URL formats and ensuring that data is accurately sent to the target server. This integration approach enriches and strengthens the system's software functionality while also improving its maintainability and upgradeability, facilitating subsequent updates and optimizations to encryption algorithms or network communication libraries. The data processing interface provides a standardized API that enables the conversion and mapping of UHF data into HTTPS request bodies. This standardized interface design allows UHF data from various sources to be easily integrated into the system and quickly and accurately converted into a request body format that complies with the HTTPS protocol. This significantly improves the efficiency and accuracy of data processing, simplifies the development process, reduces development difficulty, and enhances overall system performance. The certificate management module stores certificate files in a format that includes the server's public key, private key, and CA root certificate chain, and sets the storage path to a directory in the development board's file system. This rational storage structure ensures that certificate files are stored securely and orderly, making them easier to manage and find, while also preventing the risk of certificate file loss or tampering. The verification mechanism uses structured configuration verification parameters to comprehensively verify certificate validity, domain name matching, and CA signature validity, and supports dynamic certificate loading. This mechanism effectively guarantees the validity of the certificate throughout the data transmission process, preventing security risks caused by certificate expiration, domain name mismatch, or invalid signature, thereby ensuring the security and reliability of data transmission. The dynamic certificate loading function also enables the system to flexibly respond to situations such as certificate updates, further enhancing the system's adaptability and security. Debug mode provides an environment variable switch. When enabled, it skips certificate chain verification and only performs basic format verification. This debug mode provides convenience during system development and testing, allowing developers to quickly identify problems during debugging and improve development efficiency. At the same time, disabling debug mode during official operation ensures that system security is not affected. The URL parsing component in the server module supports absolute and relative URL parsing, and can flexibly handle various types of URL requests, improving the system's compatibility with requests from different clients and ensuring that data can be accurately parsed and forwarded; The connection management component maintains an HTTPS connection pool, supports persistent connections, and automatically handles reconnection logic. Maintaining persistent connections reduces the overhead of frequent connection establishment and disconnection, improving data transmission efficiency. Automatic reconnection logic enhances system stability, automatically restoring connections in the event of brief network outages, ensuring continuous data transmission and further improving the performance and reliability of the entire data forwarding system.

[0046] This HTTPS protocol data forwarding system for ultra-high frequency data, through its unique hardware adaptation, software integration, certificate management and server-side optimization design, greatly improves the transmission efficiency of ultra-high frequency data and the stability of the system while ensuring the security of data transmission. It effectively solves many problems existing in existing technologies and has significant innovation and practicality. It can be widely used in various scenarios with strict requirements for ultra-high frequency data transmission, providing strong technical support for the development of related fields.

[0047] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent replacements and improvements made within the principles of the present invention should be included in the scope of protection of the present invention.

Claims

1. The https protocol data forwarding system for ultra-high frequency data is characterized by: The forwarding system includes: The client initialization module includes: a hardware adaptation layer: based on reader development boards of different architectures, a binary running file matching the hardware architecture is generated through a cross-compilation tool chain; a library function integration layer: an integrated encryption module and a URL parsing module of the Curl library are loaded into the development board system in the form of a dynamic link library or a static link library; a data processing interface: a standardized API interface is provided to realize the conversion and mapping of ultra-high frequency data and https request bodies; The certificate management module includes: storage structure: the certificate file is stored in a format containing the server public key, private key and CA root certificate chain, and the storage path is the directory of the development board file system; verification mechanism: through the structure configuration verification parameters, the certificate validity period, domain name matching and CA signature validity are verified, and dynamic loading of certificates is supported; debug mode: an environment variable switch is provided, and when it is turned on, the certificate chain verification is skipped and only basic format verification is performed; The server module includes: a URL parsing component that supports absolute URL and relative URL parsing; a connection management component that maintains the https connection pool, supports long connections, and automatically handles reconnection logic.

2. The HTTPS protocol data forwarding system for ultra-high frequency data according to claim 1, characterized in that: The encryption transmission mechanism of the client reader module is specifically as follows: Handshake phase: The client sends a message, the server returns a message, the client verifies the certificate, and both parties generate a shared key; Data transmission stage: Application layer data is encrypted, and each data packet is accompanied by an authentication tag to achieve encrypted transmission and ensure data integrity and non-tamperability.

3. The HTTPS protocol data forwarding system for ultra-high frequency data according to claim 1, characterized in that: The migration process of the certificate management module includes: Certificate format conversion: package the PEM format certificate, private key and CA certificate into a format file; Permission configuration: Set file permissions to ensure that only the root user and the reader / writer process can read; Environment variable configuration: Specify the CA root certificate path.

4. The HTTPS protocol data forwarding system for ultra-high frequency data according to claim 1, characterized in that: The system according to claim 1, wherein the debugging mode of the server module is implemented as follows: In the server software configuration file, add SSL parameters and disable client certificate verification; Record all connection requests in debug mode in the log system, including the source IP address, request time, URL path, and some data bytes.

5. A method for forwarding HTTPS protocol data for ultra-high frequency data, applied to the forwarding system according to any one of claims 1 to 4, characterized in that: The forwarding method includes the following specific steps: S1: Client initialization: S11. Generate a dynamic library that supports TLS; S12, transplant verification, the transplant verification is to update the dynamic library cache, check whether the library dependencies are complete, and ensure correct linking; S2: Certificate Management: S21, certificate verification logic, when the server requires certificate verification, enable certificate verification, verify the domain name match, and convert the error code into readable information; S22. Switch to debug mode. Define macros in the code. When DEBUG is defined, set verification to disable. S3: Data forwarding: S31, URL parsing, setting target URL; S32. Request construction, wherein the request construction is a data payload, the UHF data is serialized into JSON format, and conversion rules between the UHF data and the https request body are set; S33, connection establishment, the connection establishment is DNS resolution, calling the system function to resolve the IP address corresponding to the domain name; S34. Data transmission, using the curl interface to achieve concurrent transmission.

6. The HTTPS protocol data forwarding system for ultra-high frequency data according to claim 1, characterized in that: The conversion rules between the UHF data and the https request body are as follows: The tag EPC is mapped to the JSON field "epc"; Signal strength RSSI is mapped to "rssi" with an accuracy of 1 decimal place. The read timestamp is mapped to "timestamp" in milliseconds.

7. The HTTPS protocol data forwarding system for ultra-high frequency data according to claim 1, characterized in that: The collaborative mechanism of asymmetric encryption and symmetric encryption is: Handshake phase: Both parties calculate the shared key using the ECDHE algorithm; Key derivation: derive data encryption keys and authentication keys; Data transmission: The sending end encrypts each data packet, and the receiving end decrypts it through OpenSSL.

8. The HTTPS protocol data forwarding system for ultra-high frequency data according to claim 1, characterized in that: The client reader module supports the breakpoint resume function, specifically: When data transmission is interrupted, the offset of the sent bytes is recorded and stored on the development board; After reconnection, data will be transferred through http.

9. The HTTPS protocol data forwarding system for ultra-high frequency data according to claim 1, characterized in that: The system supports data compression transmission.

10. The HTTPS protocol data forwarding system for ultra-high frequency data according to claim 1, characterized in that: The server module provides a data receiving callback interface, specifies the callback address through the http response header, and the response body contains the processing status code and error details.

Images