Processing method capable of customizing JSON (JavaScript Object Notation) transmission format

Abstract

The invention relates to the technical field of communication, and provides a processing method capable of customizing a JSON (JavaScript Object Notation) transmission format, which comprises the following steps of: receiving a request of a front end, reading key values and numerical value attributes configured by current equipment, and storing the key values and the numerical value attributes into temporary data; reading the key value of the current equipment and the type supported by the numerical value and storing the key value and the type in temporary data; transmitting key value attributes and numerical value attributes in the temporary data to a front end; the key value attributes and the numerical value attributes are analyzed through a front end, and formatting configuration options supported by all numerical values are displayed to a user; receiving a key value and an output formatting style of each numerical value configured by a user through a front end, and storing user configuration in temporary data; analyzing user formatting configuration in the temporary data to enable the user configuration to take effect; and transmitting the JSON data according to the effective user configuration. According to the invention, the flexibility and customizability of a data transmission format are improved, and the maintenance cost and technical complexity of an enterprise are reduced through a unified configuration management architecture.

Description

Technical Field

[0001] This invention relates to the field of communication technology, and in particular to a processing method for customizable JSON transmission formats. Background Technology

[0002] JSON (JavaScript Object Notation) is a lightweight data-interchange format based on a key-value pair structure. With its concise syntax and high readability, it is widely used in web services, API interfaces, and data transmission. JSON uses a key-value pair format to transmit data as text, making it easy for humans to read and write, as well as for programs to parse and generate output. However, in practical engineering applications, different clients have significantly different requirements for JSON data transmission formats.

[0003] In existing technologies, JSON data transmission mainly employs fixed format predefined methods and basic configuration file management to achieve basic data exchange functions. However, existing methods do not adequately consider the inherent business relationship between personalized customer needs and standardized system implementation. They struggle to organically integrate flexible user configuration requirements with a unified data processing architecture, requiring customized JSON transmission formats for each customer. This leads to gradually increasing enterprise maintenance costs and difficulties, failing to achieve efficient and low-cost unified management of JSON data transmission formats. Summary of the Invention

[0004] In view of this, the present invention proposes a processing method for customizable JSON transmission formats, which solves the problem that existing methods do not adequately consider the inherent business relationship mechanism between customers' personalized needs and the standardized implementation of the system. They are difficult to organically integrate flexible user configuration requirements with a unified data processing architecture, and require customized JSON transmission formats for each customer, which leads to gradually increasing enterprise maintenance costs and maintenance difficulties, and makes it impossible to achieve efficient and low-cost unified management of JSON data transmission formats.

[0005] The technical solution of this invention is implemented as follows: This invention provides a processing method with a customizable JSON transmission format, including the following steps: Receive requests from the front end, read the key-value and numeric attributes of the current device configuration and store them in temporary data; Read the types supported by the current device key and store them in temporary data; read the types supported by the current device value and store them in temporary data. Transmit the key-value and numeric attributes from the temporary data to the front end; The key-value and numeric attributes are parsed by the front end, and the formatting configuration options supported by each numeric value are displayed to the user. Receive the key-value pairs and output formatting styles for each value configured by the user through the front end, and store the user configuration in temporary data; Parse the user-formatted configuration in the temporary data and write the parsed configuration parameters into the device configuration file to make the user configuration take effect; Transmit JSON data based on the effective user configuration.

[0006] Based on the above technical solutions, preferably, the step of parsing the key-value attributes and numerical attributes through the front end and displaying the formatting configuration options supported by each numerical value to the user includes: After receiving the key-value and numeric attributes, the front-end parses the attribute identifier and the current configuration value in each numeric attribute, looks up the corresponding numeric type information from the temporary data based on the attribute identifier, extracts the formatting options from the found numeric type information, and constructs a list of formatting configuration options that the user can select. The front-end interface then displays the list of formatting configuration options corresponding to each numeric value to the user.

[0007] Based on the above technical solutions, preferably, the formatting configuration option list includes direct numerical output options, percentage formatting options, timestamp formatting options, and script formatting options. An independent configuration area is generated for each numerical attribute through the front-end interface. The formatting configuration option list is displayed in the configuration area in the form of a drop-down menu. When the user selects different formatting options, the corresponding parameter setting interface is dynamically displayed through the configuration area.

[0008] Based on the above technical solutions, preferably, the step of receiving the key-value pairs and output formatting styles of each value configured by the user through the front end, and storing the user configuration in temporary data, includes: The system receives the formatting configuration options and input formatting parameters corresponding to each value selected by the user in the configuration area. It performs data integrity verification on the received user configuration. After successful verification, it combines the attribute identifier of each value, the selected output formatting style, and the formatting parameters to construct a user configuration record. All user configuration records are indexed according to the attribute identifier and stored in temporary data.

[0009] Based on the above technical solutions, preferably, the user configuration record adopts a key-value pair structure, with the attribute identifier as the primary key and the configuration object as the value. The configuration object includes a formatting type identifier, formatting parameters, and priority information. When the user selects the script formatting option, the configuration object also includes the script code content entered by the user and the script execution environment identifier. The temporary data establishes a hash index according to the primary key of the configuration record to support fast lookup and update operations.

[0010] Based on the above technical solutions, preferably, the step of transmitting JSON data according to the effective user configuration includes: The system reads the effective user configuration from the device configuration file, obtains the raw data to be transmitted, formats the raw data according to the output formatting style corresponding to each value in the user configuration, reorganizes the formatted data according to the attribute identifier, constructs a JSON data structure that conforms to the user-defined format, and transmits the constructed JSON data to the target receiving end.

[0011] Based on the above technical solutions, preferably, the formatting process includes direct numerical output processing, percentage formatting processing, timestamp formatting processing, and script formatting processing. When the output formatting style is a script formatting style, the script code content and script execution environment identifier are extracted from the user configuration, the script code content is run in the corresponding script execution environment, the execution result of the script code is used as the formatted output value of the numerical value, and the formatted output value is filled into the corresponding position of the JSON data structure.

[0012] Based on the above technical solutions, preferably, the step of reading the types supported by the current device key value and storing them in temporary data, and reading the types supported by the current device value and storing them in temporary data, includes: Read the key value type information supported by the current device key value from the device type configuration file, and store the key value type information in temporary data; Read the type information supported by the current device value from the device type configuration file and store the value type information in temporary data.

[0013] Based on the above technical solutions, preferably, the step of transmitting the key-value attributes and numerical attributes in the temporary data to the front end includes: The key-value and numeric attributes in the temporary data are encapsulated according to a preset transmission protocol format to generate a front-end parseable data packet; The system transmits parsable data packets from the front end to the front end via a network communication interface and receives transmission confirmation information returned by the front end.

[0014] Based on the above technical solutions, preferably, the step of parsing the user formatted configuration in the temporary data and writing the parsed configuration parameters into the device configuration file to make the user configuration take effect includes: Read user configuration records from temporary data, parse the attribute identifiers, output formatting styles and formatting parameters in each user configuration record, and generate corresponding configuration parameter entries; The generated configuration parameter entries are converted according to the data format of the device configuration file and written into the specified configuration node of the device configuration file so that the user configuration takes effect.

[0015] The customizable JSON transmission format processing method of the present invention has the following advantages over the prior art: (1) By establishing a front-end and back-end interactive configuration management mechanism, the dynamic reading and transmission of key-value attributes and numerical attributes are realized by using temporary data storage. Combined with the user interface, the formatted configuration options supported by each value are displayed. Through real-time parsing of user-defined configurations and dynamic updates of device configuration files, JSON data is transmitted in a personalized format according to the effective configuration, which improves the flexibility and customizability of data transmission format. At the same time, the unified configuration management architecture reduces enterprise maintenance costs and technical complexity. (2) By establishing a matching mechanism between attribute identifiers and numerical type information, a dynamic lookup algorithm is used to extract formatting options and construct a list of configuration options that users can select. Combined with the interface design of the independent configuration area and the interaction method of the drop-down menu, the corresponding parameter setting interface is dynamically displayed according to the different formatting options selected by the user, which improves the convenience of user configuration operations and the friendliness of the configuration interface. At the same time, the personalized needs of different business scenarios are met through diversified formatting options. (3) By establishing a user configuration data integrity verification mechanism, using key-value pair structured storage to realize the mapping management of attribute identifiers and configuration objects, combining format type identifiers, parameters and priority information for comprehensive configuration, and dynamically expanding the configuration object according to script formatting options to include script code content and execution environment identifiers, the reliability of user configuration processing and the efficiency of data access are improved. Attached Figure Description

[0016] 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 some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0017] Figure 1 This is a flowchart of a customizable JSON transmission format processing method according to the present invention. Detailed Implementation

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

[0019] Please see Figure 1 This invention provides a processing method for customizable JSON transmission formats, comprising the following steps: Receive requests from the front end, read the key-value and numeric attributes of the current device configuration and store them in temporary data; Read the types supported by the current device key and store them in temporary data; read the types supported by the current device value and store them in temporary data. Transmit the key-value and numeric attributes from the temporary data to the front end; The key-value and numeric attributes are parsed by the front end, and the formatting configuration options supported by each numeric value are displayed to the user. Receive the key-value pairs and output formatting styles for each value configured by the user through the front end, and store the user configuration in temporary data; Parse the user-formatted configuration in the temporary data and write the parsed configuration parameters into the device configuration file to make the user configuration take effect; Transmit JSON data based on the effective user configuration.

[0020] Specifically, this embodiment establishes a front-end and back-end interactive configuration management mechanism, utilizes temporary data storage to achieve dynamic reading and transmission of key-value attributes and numerical attributes, combines a user interface to display the formatted configuration options supported by each value, and through real-time parsing of user-defined configurations and dynamic updates of device configuration files, personalizes the formatted transmission of JSON data according to the effective configuration. This solves the contradiction between the traditional fixed JSON transmission format, the diversification of customer needs and system standardization, improves the flexibility and customizability of data transmission format, and reduces enterprise maintenance costs and technical complexity through a unified configuration management architecture.

[0021] The process of receiving requests from the front end, reading the key-value and numerical attributes configured in the current device, and storing them in temporary data includes: After receiving the request from the front end, the key-value attribute and numeric attribute are read from the device configuration file according to the attribute type.

[0022] In one specific embodiment, the device configuration file is stored in JSON format. When reading according to attribute type, the attribute nodes in the JSON file are parsed to extract the attribute name, attribute value and attribute type identifier of each attribute node, and the key-value type attributes and numeric type attributes are read into different data sets respectively.

[0023] The read key-value and numeric attributes are categorized and organized according to attribute identifiers, and then stored in temporary data according to a preset data structure format.

[0024] In one specific embodiment, the preset data structure format includes a key-value attribute mapping table and a numeric attribute mapping table. The read key-value attributes are stored in the key-value attribute mapping table with attribute identifiers as keys and attribute configuration information as values, and the read numeric attributes are stored in the numeric attribute mapping table with attribute identifiers as keys and attribute configuration information as values.

[0025] Specifically, this embodiment establishes a JSON format configuration file parsing mechanism, utilizes an attribute node extraction algorithm to classify and read key-value and numeric attributes, combines attribute identifier classification and organization with a mapping table stored in a preset data structure format, and stores configuration information in the key-value attribute mapping table and the numeric attribute mapping table according to attribute type. This structured data organization solves the contradiction between low efficiency in traditional configuration reading, mixed attribute type management, and disordered data structure, improving the efficiency of configuration data reading and the orderliness of attribute management.

[0026] The step of reading the types supported by the current device key value and storing them in temporary data, and reading the types supported by the current device value and storing them in temporary data, includes: Read the key value type information supported by the current device key value from the device type configuration file, and store the key value type information in temporary data.

[0027] In one specific embodiment, the key-value type information includes string type, boolean type and enumeration type. By parsing the key-value type configuration node in the device type configuration file, the type identifier and formatting rules of each key-value type are extracted, and the extracted key-value type information is indexed and stored in the key-value type area of ​​temporary data according to the type identifier.

[0028] Read the type information supported by the current device value from the device type configuration file and store the value type information in temporary data.

[0029] In one specific embodiment, the numerical type information includes integer type, floating-point type, percentage type and timestamp type. By parsing the numerical type configuration node in the device type configuration file, the type identifier and corresponding formatting options of each numerical type are extracted, and the extracted numerical type information is indexed and stored in the numerical type area of ​​temporary data according to the type identifier.

[0030] Specifically, this embodiment establishes a device type configuration file parsing mechanism, utilizes a configuration node parsing algorithm to classify and extract key-value type information and numeric type information, combines the associated management of type identifiers and formatting rules, and indexes and stores type information into the key-value type area and numeric type area of ​​temporary data according to attribute type. This structured organization of type information resolves the contradictions between the chaotic nature of traditional device type management, unclear formatting options, and scattered configuration information, improving the standardization of type information management and the accuracy of formatted configuration. Furthermore, it provides users with a rich foundation of configuration options through diverse type support, including strings, booleans, enumerations, integers, floating-point numbers, percentages, and timestamps.

[0031] The process of transmitting key-value and numeric attributes from temporary data to the front end includes: The key-value and numeric attributes in the temporary data are encapsulated according to a preset transmission protocol format to generate a front-end parseable data packet.

[0032] In one specific embodiment, the preset transmission protocol format is JSON format. Key-value attributes are constructed into key-value attribute JSON objects using attribute identifiers as keys and attribute configuration information as keys. Numeric attributes are constructed into numeric attribute JSON objects using attribute identifiers as keys and attribute configuration information as keys. The key-value attribute JSON objects and numeric attribute JSON objects are encapsulated into a unified data packet structure to obtain a front-end parseable data packet.

[0033] The system transmits parsable data packets from the front end to the front end via a network communication interface and receives transmission confirmation information returned by the front end.

[0034] In one specific embodiment, the network communication interface adopts the HTTP protocol and sends the front-end parsable data packet to the receiving address specified by the front-end via a POST request. After receiving the front-end parsable data packet, the front-end parses the key-value attributes and numerical attributes in it, and returns transmission confirmation information including parsing status and data integrity verification results.

[0035] Specifically, this embodiment establishes a data encapsulation mechanism based on a preset transmission protocol format, utilizes JSON format to achieve structured packaging of key-value and numeric attributes, combines HTTP POST request method for network communication transmission, and establishes a data integrity verification feedback mechanism based on the transmission confirmation information returned by the front end. This standardized front-end and back-end data interaction resolves the contradictions between inconsistent traditional data transmission formats, insufficient transmission reliability, and lack of data integrity verification, thereby improving the standardization of data transmission and communication reliability.

[0036] The process involves parsing the key-value and numeric attributes through the front-end to display the formatting configuration options supported by each numeric value to the user, including: After receiving the key-value and numeric attributes, the front-end parses the attribute identifier and the current configuration value in each numeric attribute, looks up the corresponding numeric type information from the temporary data based on the attribute identifier, extracts the formatting options from the found numeric type information, and constructs a list of formatting configuration options that the user can select. The front-end interface then displays the list of formatting configuration options corresponding to each numeric value to the user.

[0037] The formatting configuration option list includes options for direct numerical output, percentage formatting, timestamp formatting, and script formatting. An independent configuration area is generated for each numerical attribute through the front-end interface. The formatting configuration option list is displayed in the configuration area in the form of a drop-down menu. When the user selects different formatting options, the corresponding parameter setting interface is dynamically displayed through the configuration area.

[0038] In one specific embodiment, the formatting configuration options supported by each value are shown in Table 1.

[0039] Table 1 Reference Table of Numerical Configuration Options ; Table 1 defines various key-value and numeric formatting options that users can configure, including parameters such as select_key, select_value, and default_key. It shows the formatting configuration options supported by each numeric value and serves as the data structure basis for the front-end to display configuration options to the user.

[0040] Specifically, this embodiment establishes a matching mechanism between attribute identifiers and numerical type information, utilizes a dynamic lookup algorithm to extract formatting options, and constructs a list of user-selectable configuration options. Combined with an independent configuration area interface design and drop-down menu interaction, it dynamically displays the corresponding parameter setting interface based on the user's selected formatting options. This visual configuration management resolves the contradiction between the complexity of traditional JSON configuration, the difficulty of user operation, and the lack of intuitive configuration option display. It improves the convenience of user configuration operations and the user-friendliness of the configuration interface, while also meeting the personalized needs of different business scenarios through diverse formatting options.

[0041] The process of receiving the key-value pairs and output formatting styles for each value configured by the user through the front end, and storing the user configuration in temporary data, includes: The system receives the formatting configuration options and input formatting parameters corresponding to each value selected by the user in the configuration area. It performs data integrity verification on the received user configuration. After successful verification, it combines the attribute identifier of each value, the selected output formatting style, and the formatting parameters to construct a user configuration record. All user configuration records are indexed according to the attribute identifier and stored in temporary data.

[0042] The user configuration record adopts a key-value pair structure, with the attribute identifier as the primary key and the configuration object as the value. The configuration object includes a formatting type identifier, formatting parameters, and priority information. When the user selects the script formatting option, the configuration object also includes the script code content entered by the user and the script execution environment identifier. The temporary data establishes a hash index according to the primary key of the configuration record to support fast lookup and update operations.

[0043] In one specific embodiment, an example of a reference request for obtaining and distributing configuration is shown in Table 2.

[0044] Table 2. Example of a Reference Request ; Table 2 shows specific HTTP interface call examples for obtaining and distributing configurations, including the complete JSON format of the request and response. The GetJsonConfig part corresponds to the step of transmitting the key-value and numeric attributes in the temporary data to the front end, and the SetJsonConfig part corresponds to the step of receiving the key-value and output formatting style of each value configured by the user through the front end.

[0045] Specifically, this embodiment establishes a user configuration data integrity verification mechanism, utilizes key-value pair structured storage to manage the mapping between attribute identifiers and configuration objects, combines format type identifiers, parameters, and priority information for comprehensive configuration, and dynamically expands configuration objects to include script code content and execution environment identifiers based on script formatting options. The fast lookup mechanism using hash indexes resolves the contradiction between low efficiency, complex data structures, and insufficient access performance in traditional configuration storage, thereby improving the reliability of user configuration processing and the efficiency of data access.

[0046] The process of parsing the user-formatted configuration in the temporary data and writing the parsed configuration parameters into the device configuration file to make the user configuration take effect includes: Read user configuration records from temporary data, parse the attribute identifiers, output formatting styles and formatting parameters in each user configuration record, and generate corresponding configuration parameter entries.

[0047] In one specific embodiment, when parsing user configuration records, the format type identifier and format parameters are extracted from the configuration object. The corresponding configuration parameter structure template is determined based on the format type identifier. The format parameters are filled into the configuration parameter structure template to generate standardized configuration parameter entries. When the configuration object includes script code content, the script code content and the script execution environment identifier are encapsulated together into the configuration parameter entries.

[0048] The generated configuration parameter entries are converted according to the data format of the device configuration file and written into the specified configuration node of the device configuration file so that the user configuration takes effect; In one specific embodiment, the device configuration file is stored in JSON format. The configuration parameter entries are converted into JSON object format, with attribute identifiers as the keys of the JSON object and JSON sub-objects including formatted configuration information as the values. The converted JSON object is updated to the formatted configuration node of the device configuration file through a file write operation, and a configuration update timestamp is generated to mark the configuration as effective.

[0049] In one specific embodiment, the error codes and descriptions for configuration errors are shown in Table 3.

[0050] Table 3 Example of Configuration Error Codes ; Table 3 defines the error codes and descriptions for various configuration errors, such as script execution errors and excessive script execution time, which involve handling various abnormal situations that may occur during the parsing of user formatted configurations in temporary data.

[0051] Specifically, this embodiment establishes a user configuration record parsing mechanism, utilizes a matching algorithm between format type identifiers and configuration parameter structure templates to generate standardized configuration parameter entries, combines the encapsulation of script code content and execution environment identifiers, and performs data format conversion and node updates according to the JSON format requirements of the device configuration file. By using configuration update timestamps, it resolves the contradiction between the complexity of traditional user configuration applications, difficulties in format conversion, and unclear configuration effectiveness status, improving the automation level of configuration applications and the standardization level of data formats. Simultaneously, the timestamp mechanism provides a reliable basis for confirming the effectiveness of configuration management and status tracking.

[0052] The transmission of JSON data according to the effective user configuration includes: The system reads the effective user configuration from the device configuration file, obtains the raw data to be transmitted, formats the raw data according to the output formatting style corresponding to each value in the user configuration, reorganizes the formatted data according to the attribute identifier, constructs a JSON data structure that conforms to the user-defined format, and transmits the constructed JSON data to the target receiving end.

[0053] The formatting process includes direct numerical output processing, percentage formatting processing, timestamp formatting processing, and script formatting processing. When the output formatting style is script formatting style, the script code content and script execution environment identifier are extracted from the user configuration, the script code content is run in the corresponding script execution environment, the execution result of the script code is used as the formatted output value of the numerical value, and the formatted output value is filled into the corresponding position of the JSON data structure.

[0054] Specifically, this embodiment establishes a mechanism for reading effective user configurations and acquiring raw data. It utilizes diverse formatting algorithms to achieve direct numerical output, percentage, timestamp, and script formatting. This is combined with data reorganization using attribute identifiers and the construction of user-defined JSON data structures. Furthermore, it dynamically extracts script code content and execution environment identifiers based on the script formatting style for script execution. By precisely mapping formatted output values ​​to JSON data structures, it resolves the contradiction between the rigidity of traditional data transmission formats, the inability to meet personalized needs, and the insufficient dynamic formatting capabilities. This enhances the personalized customization capabilities and formatting flexibility of JSON data transmission, while script-based formatting meets the highly customized data output requirements of complex business scenarios.

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

Claims

1. A method for processing customizable JSON transmission formats, characterized in that, Includes the following steps: Receive requests from the front end, read the key-value and numeric attributes of the current device configuration and store them in temporary data; Read the types supported by the current device key and store them in temporary data; read the types supported by the current device value and store them in temporary data. Transmit the key-value and numeric attributes from the temporary data to the front end; The key-value and numeric attributes are parsed by the front end, and the formatting configuration options supported by each numeric value are displayed to the user. Receive the key-value pairs and output formatting styles for each value configured by the user through the front end, and store the user configuration in temporary data; Parse the user-formatted configuration in the temporary data and write the parsed configuration parameters into the device configuration file to make the user configuration take effect; Transmit JSON data based on the effective user configuration.

2. The processing method for a customizable JSON transmission format as described in claim 1, characterized in that, The process involves parsing the key-value and numeric attributes through the front-end to display the formatting configuration options supported by each numeric value to the user, including: After receiving the key-value and numeric attributes, the front-end parses the attribute identifier and the current configuration value in each numeric attribute, looks up the corresponding numeric type information from the temporary data based on the attribute identifier, extracts the formatting options from the found numeric type information, and constructs a list of formatting configuration options that the user can select. The front-end interface then displays the list of formatting configuration options corresponding to each numeric value to the user.

3. The processing method for a customizable JSON transmission format as described in claim 2, characterized in that, The formatting configuration option list includes options for direct numerical output, percentage formatting, timestamp formatting, and script formatting. An independent configuration area is generated for each numerical attribute through the front-end interface. The formatting configuration option list is displayed in the configuration area in the form of a drop-down menu. When the user selects different formatting options, the corresponding parameter setting interface is dynamically displayed through the configuration area.

4. The processing method for a customizable JSON transmission format as described in claim 1, characterized in that, The process of receiving the key-value pairs and output formatting styles for each value configured by the user through the front end, and storing the user configuration in temporary data, includes: The system receives the formatting configuration options and input formatting parameters corresponding to each value selected by the user in the configuration area. It performs data integrity verification on the received user configuration. After successful verification, it combines the attribute identifier of each value, the selected output formatting style, and the formatting parameters to construct a user configuration record. All user configuration records are indexed according to the attribute identifier and stored in temporary data.

5. The processing method for a customizable JSON transmission format as described in claim 4, characterized in that, The user configuration record adopts a key-value pair structure, with the attribute identifier as the primary key and the configuration object as the value. The configuration object includes a formatting type identifier, formatting parameters, and priority information. When the user selects the script formatting option, the configuration object also includes the script code content entered by the user and the script execution environment identifier. The temporary data establishes a hash index according to the primary key of the configuration record to support fast lookup and update operations.

6. The processing method for a customizable JSON transmission format as described in claim 1, characterized in that, The transmission of JSON data according to the effective user configuration includes: The system reads the effective user configuration from the device configuration file, obtains the raw data to be transmitted, formats the raw data according to the output formatting style corresponding to each value in the user configuration, reorganizes the formatted data according to the attribute identifier, constructs a JSON data structure that conforms to the user-defined format, and transmits the constructed JSON data to the target receiving end.

7. The processing method for a customizable JSON transmission format as described in claim 6, characterized in that, The formatting process includes direct numerical output processing, percentage formatting processing, timestamp formatting processing, and script formatting processing. When the output formatting style is script formatting style, the script code content and script execution environment identifier are extracted from the user configuration, the script code content is run in the corresponding script execution environment, the execution result of the script code is used as the formatted output value of the numerical value, and the formatted output value is filled into the corresponding position of the JSON data structure.

8. The processing method for a customizable JSON transmission format as described in claim 1, characterized in that, The step of reading the types supported by the current device key value and storing them in temporary data, and reading the types supported by the current device value and storing them in temporary data, includes: Read the key value type information supported by the current device key value from the device type configuration file, and store the key value type information in temporary data; Read the type information supported by the current device value from the device type configuration file and store the value type information in temporary data.

9. The processing method for a customizable JSON transmission format as described in claim 1, characterized in that, The process of transmitting key-value and numeric attributes from temporary data to the front end includes: The key-value and numeric attributes in the temporary data are encapsulated according to a preset transmission protocol format to generate a front-end parseable data packet; The system transmits parsable data packets from the front end to the front end via a network communication interface and receives transmission confirmation information returned by the front end.

10. The processing method for a customizable JSON transmission format as described in claim 1, characterized in that, The process of parsing the user-formatted configuration in the temporary data and writing the parsed configuration parameters into the device configuration file to make the user configuration take effect includes: Read user configuration records from temporary data, parse the attribute identifiers, output formatting styles and formatting parameters in each user configuration record, and generate corresponding configuration parameter entries; The generated configuration parameter entries are converted according to the data format of the device configuration file and written into the specified configuration node of the device configuration file so that the user configuration takes effect.

Images