Data communication method, apparatus, and storage medium

Abstract

The application provides a data communication method, device and storage medium. The method is applied to a gas device including a processing unit and a metering module. The method includes the following steps: obtaining function data, encapsulating the function data into a data frame by using a preset frame structure, sending the data frame to the metering module, and obtaining a response. Flexible data transmission is realized. The preset frame structure encapsulates data, which can accommodate more types of function data, realizes complex data interaction requirements, and thus improves the technical problem of insufficient data transmission capacity of a gas meter in the related art caused by strict limitation of the number of fields, which is difficult to meet the requirements of modern gas management systems on data richness, flexibility and expansibility, and improves the intelligent level of the gas metering device.

Description

Technical Field

[0001] This application relates to the field of gas metering technology, specifically to a data communication method, device, and storage medium. Background Technology

[0002] In gas metering technology applications, the communication protocol design of ultrasonic gas meters has long faced the challenge of insufficient data transmission capabilities. Related technologies generally employ fixed and limited data field structures; for example, some commercial products only support six basic fields for transmitting simple parameters such as instantaneous flow rate, signal gain, time information, and temperature. This limits the capacity to accommodate more types of functional data. Due to the strict limitation on the number of fields, gas meters struggle to meet complex data interaction needs, fundamentally restricting the intelligence level of gas metering devices. This prevents them from meeting the requirements of modern gas management systems for data richness, flexibility, and scalability, severely hindering the industry's development towards higher precision and broader functionality. Summary of the Invention

[0003] This application provides a data communication method, device, and storage medium that can accommodate more types of functional data, realize complex data interaction needs, and thus improve the intelligence level of gas metering devices.

[0004] In a first aspect, a data communication method is provided, applied to a gas device including a processing unit and a metering module, the method comprising: Obtain the functional data to be transmitted from the gas device; The processing unit encapsulates the functional data into a first data frame according to a preset frame structure; the frame structure includes at least a control code, a length field, and a data field. Send the first data frame to the metering module; The metering module responds to the first data frame to obtain a response result; the response result is then encapsulated into a second data frame according to the frame structure. The second data frame is sent to the processing unit.

[0005] In a second aspect, a data communication device is provided for use in a gas appliance including a processing unit and a metering module, the device comprising: The acquisition module is used to acquire the functional data to be transmitted by the gas device; The first encapsulation module is used to encapsulate the functional data into a first data frame according to a preset frame structure through the processing unit; the frame structure includes at least a control code, a length field, and a data field. The first sending module is used to send the first data frame to the metering module; The second encapsulation module is used to respond to the first data frame through the metering module to obtain a response result; and to encapsulate the response result into a second data frame according to the frame structure. The second sending module is used to send the second data frame to the processing unit.

[0006] Thirdly, a computer-readable storage medium is provided having a computer program stored thereon, the computer program being loaded by a processor to perform the steps of any of the methods described herein.

[0007] This application provides a data communication method, apparatus, and storage medium. The method is applied to a gas device including a processing unit and a metering module. The method includes: acquiring functional data, encapsulating it into a data frame using a preset frame structure, sending it to the metering module, and obtaining a response. This achieves flexible data transmission. By encapsulating data using a preset frame structure, it can accommodate more types of functional data and meet complex data interaction needs. This improves the technical problem in related technologies where the data transmission capacity of gas meters is insufficient due to strict limitations on the number of fields, making it difficult to meet the requirements of modern gas management systems for data richness, flexibility, and scalability. This enhances the intelligence level of the gas metering device. Attached Figure Description

[0008] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0009] Figure 1 A schematic flowchart of a data communication method provided in an embodiment of this application; Figure 2 This is a schematic diagram of the frame structure in the data communication method provided in the embodiments of this application; Figure 3 A schematic diagram of the structure of a data communication device provided in an embodiment of this application; Figure 4 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

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

[0011] like Figure 1 As shown, Figure 1 This is a flowchart illustrating a data communication method provided in an embodiment of this application. The embodiment provides a data communication method applied to a gas device including a processing unit and a metering module. The method includes: Step 101: Obtain the functional data to be transmitted from the gas device.

[0012] The processing unit can be a unit within the gas appliance used for data processing, logic control, and communication management. For example, the processing unit can be the main control unit. The metering module can be a module within the gas appliance used for gas metering, data acquisition, and communication with the processing unit. The gas appliance can be a device used for gas metering, control, and data transmission; for example, the gas appliance can be an ultrasonic gas meter, and the metering module can be an ultrasonic gas meter measuring module (UGS). Functional data can be various types of information that the gas appliance needs to transmit during operation, such as instantaneous flow rate, cumulative consumption, equipment status, alarm information, or configuration parameters.

[0013] In this embodiment, the processing unit can generate functional data based on its internal operating logic or a timer. For example, the processing unit can be configured to generate an instruction at regular intervals requesting the metering module to send the current cumulative usage. Furthermore, the functional data can also receive remote instructions or data through an external interface (e.g., communicating with a host computer or cloud platform).

[0014] Step 102: The processing unit encapsulates the functional data into a first data frame according to a preset frame structure; the frame structure includes at least a control code, a length field, and a data field.

[0015] The frame structure can be a specific format in which data is organized and encapsulated during transmission. This frame structure defines the order and meaning of each field in the data frame, ensuring that the data can be correctly parsed by the processing unit and the metering module. The control code can be a field in the frame structure used to indicate the type, function, or operation instruction of the data frame. The length field can be a field in the frame structure used to indicate the length of the data field. The data field can be a field in the frame structure used to carry the actual functional data or response information. This first data frame encapsulates the instructions or data sent by the processing unit to the metering module. In this embodiment, the processing unit can be configured to directly fill the functional data into the data field, calculate the number of bytes in the data field and write it into the length field, and finally select and write the control code according to the function type of the functional data. In some embodiments, the frame structure also includes a frame header, a fixed byte in the communication frame used to identify subsequent content as service data, used to distinguish the wake-up code from subsequent service fields; for example, the frame header can be 0x5D.

[0016] In some embodiments, the first data frame includes a first control code; the first control code includes a first region code for characterizing the initiation type of the first data frame and a second region code for characterizing functional data; the processing unit encapsulates the functional data into a first data frame according to a preset frame structure, including: determining the first region code of the first control code based on the attributes of the first data frame initiated by the processing unit; and determining the second region code of the first control code based on the functional type corresponding to the functional data.

[0017] The first control code can be a field used to carry control information to guide the metering module in correctly parsing and processing the data frame. For example, the first control code includes 8 bits, namely Bit7-Bit0; its internal structure can be further divided into different regions to carry different categories of control information. The first region code is a field used to indicate that the first data frame was initiated by the processing unit. For example, the first region code can be Bit7 and / or Bit6-Bit5. When the first region code is Bit7, it can be specified as 0, indicating that the first data frame was initiated by the processing unit; when the first region code is Bit6-Bit5, it can be specified as 00, indicating that the first data frame was initiated by the processing unit.

[0018] The second area code can be a field used to indicate the function type of the functional data carried in the first data frame. For example, the second area code can be Bit4-Bit0. For example, the second area code can be encoded using enumerated values, including: 00001: Read metering data; 00010: Detection mode; 00011: Read real-time clock; 00100: Set real-time clock; 00101: Read operating parameters; 01001: Pulse constant setting; 01010: Active reporting interval setting; 01011: Instantaneous flow rate unit time setting; 01100: User maximum load threshold setting; 01101: Abnormal event threshold time setting; 01110: Constant current alarm setting; 01111: Factory default setting; 10000: Flow coefficient correction; 10001: Operating condition / standard condition conversion setting; 10101: Active pulse signal reporting.

[0019] Through the above technical solution, the processing unit can clearly identify the initiator and functional data type of the data frame when encapsulating the first data frame, so that the metering module can quickly identify the source and intent of the data frame after receiving it without performing complex parsing or additional queries.

[0020] In some embodiments, the first data frame includes a first data field; the function type corresponding to the function data includes a first type of reading data from the metering module and a second type of setting the function of the metering module; the processing unit encapsulates the function data into a first data frame according to a preset frame structure, including: when the function type is the first type, determining the first data field as an empty data field; when the function type is the second type, obtaining the function parameters for setting the function of the metering module in the function data; and determining the first data field based on the function parameters.

[0021] The first data field can be a field used to carry actual functional data or functional parameters. The first type can be an operation to read data from the metering module, such as querying the current measurement value, historical records, or device status; the second type can be an operation to set the functions of the metering module, such as modifying the operating mode, calibration parameters, or controlling valve switches. When the function type is the first type, the processing unit will determine the first data field as an empty data field. When the function type is the second type, the processing unit will extract the functional parameters required to set the metering module's functions from the functional data. Functional parameters can be specific operation instructions or configuration values, such as new thresholds, time settings, or control commands. The processing unit will encode or encapsulate the format and content of the functional parameters into the first data field to ensure that the metering module can correctly parse and execute the corresponding setting operations.

[0022] This application, through the aforementioned technical solution, enables the flexible and efficient construction of a first data frame based on the specific type of functional data. For read-type functional data, setting the first data field to empty significantly reduces the amount of data frame transmission, lowers the load on the communication link, and accelerates data interaction. For setting-type functional data, accurately acquiring and encapsulating functional parameters into the first data field ensures that all necessary configuration information is transmitted completely and accurately to the metering module, thereby improving the success rate and accuracy of functional settings.

[0023] Step 103: Send the first data frame to the metering module.

[0024] In this embodiment, the transmission of data frames can be achieved through various communication interfaces. For example, the first data frame can be sent byte by byte to the metering module via a Serial Peripheral Interface (SPI) or an Inter-Integrated Circuit Bus (I2C). In another implementation, the processing unit can be configured to send the first data frame to the metering module via a Universal Asynchronous Receiver / Transmitter (UART) interface in an asynchronous serial communication manner.

[0025] Step 104: The metering module responds to the first data frame to obtain the response result; the response result is then encapsulated into a second data frame according to the frame structure.

[0026] The response result can be the result information generated by the metering module based on its internal logic and operational status after receiving and processing the first data frame. This response result can indicate whether the operation was successful, failed, or that a data value or status has been updated. The second data frame can be a data frame encapsulated by the metering module and sent to the processing unit. This second data frame carries the metering module's response result to the first data frame or its own status information.

[0027] In this embodiment, after receiving the first data frame, the metering module can be configured to directly parse the control code and perform a preset action according to the operation type indicated by the control code, such as reading internal sensor data or updating the configuration register. After completing the operation, the metering module can be configured to generate a simple status code as a response result. The metering module can be configured to directly use this status code as the content of the data field, while setting the corresponding control code and length field, thereby encapsulating it into a second data frame.

[0028] In some embodiments, the second data frame includes a second control code; the second control code includes a third region code for characterizing the initiation type of the second data frame and a fourth region code for characterizing functional data; the method further includes: determining the third region code of the second control code based on the attribute that the second data frame is initiated or responded to by the metering module; the first region code is different from the third region code; determining the fourth region code of the second control code based on the functional type corresponding to the functional data; the fourth region code matches the second region code.

[0029] The second control code can be a field used to carry and transmit control information about the data frame. For example, the second control code includes 8 bits, Bits 7-0. The third area code is used to indicate whether the second data frame was initiated by the metering module (e.g., periodically reporting data) or as a response to a request from the processing unit. For example, the third area code can be Bit 7 and / or Bits 6-5. When the third area code is Bit 7, it can be specified as 1, indicating that the second data frame is a data frame initiated or responded to by the metering module. When the third area code is Bits 6-5, it can be specified as 01, indicating that the third data frame is a data frame initiated or responded to by the metering module. The first area code is different from the third area code, ensuring clear distinction between the communicating parties at the control code level, enabling the receiver to quickly and unambiguously identify the source of the data frame and its role in the communication process. The fourth area code can be a field used to indicate the type of functional data. The fourth area code corresponds to the second area code and aims to ensure consistency in functional type between response frames and request frames. The description of the fourth region code can be found in the description of the second region code, and will not be repeated here.

[0030] This application enables the second control code of the second data frame to clearly identify the initiator as the metering module and accurately associate it with the corresponding functional data type during data communication between the processing unit and the metering module.

[0031] In some embodiments, the second data frame includes a second data field; encapsulating the response result into a second data frame according to the frame structure includes: determining the second data field based on the response result when the function type is a first type; and determining the second data field as an empty data field when the function type is a second type.

[0032] The second data field can be a field in the second data frame used to carry specific response data or information. For example, if the first type is reading the total gas volume, the second data field will contain the current total gas volume data; or, if the first type is querying the device status, the second data field will contain the device status information. When the function type is the second type (i.e., setting the metering module function), after the metering module successfully executes the setting operation, the response usually only needs to confirm the success or failure of the operation, without needing to return a large amount of specific data. To optimize communication efficiency, the second data field is determined to be an empty data field.

[0033] This application can flexibly and efficiently determine the content of the second data field of the second data frame according to different function types. When specific data needs to be transmitted (e.g., reading data), the second data field can accurately carry the response result; when specific data does not need to be transmitted (e.g., setting function), the second data field is determined to be empty, thereby effectively avoiding unnecessary data transmission, reducing communication overhead, and improving the efficiency of data communication and the response speed of the system.

[0034] In some embodiments, the first data frame includes a first length field; the second data frame includes a second length field; the method further includes: determining the value of the first length field based on the number of first bytes in the first data field; the value of the first length field is the decimal corresponding value of the number of first bytes; determining the value of the second length field based on the number of second bytes in the second data field, the value of the second length field being the decimal corresponding value of the number of second bytes.

[0035] The first length field can be a field used to indicate or store the length information of a data field in the first data frame. For example, the first length field may include 1 byte. Similarly, the second length field can be a field used to indicate or store the length information of a second data field in the second data frame. For example, the second length field may include 1 byte.

[0036] In this embodiment, when encapsulating the first data frame, the processing unit can first calculate the number of bytes of the functional parameters contained in the first data field, then convert the decimal value of that number of bytes into binary or binary-coded decimal (BCD) code form, and write it into the first length field. The process of determining the value of the second length field can refer to the above description and will not be repeated here. This value can be represented in hexadecimal form during frame transmission.

[0037] This application enables the precise calculation and encapsulation of data frame length information within the data frame during data communication between the processing unit and the metering module. This allows the receiver to accurately parse the data field within the data frame based on the length field value, avoiding problems such as data parsing errors, data truncation, or incomplete reading caused by uncertain data field lengths.

[0038] In some embodiments, the second data frame includes a state field; encapsulating the response result into a second data frame according to a frame structure includes: determining the state field based on the working state of the metering module; the working state includes at least a running state performing metering operations, an idle state not performing metering operations, and a verification state performing verification operations.

[0039] The status field can be used to carry information about the metering module's operating status. Setting this status field allows the processing unit to directly obtain the metering module's operational status, rather than just the response data itself. The metering module's operating status can be its current operating mode or activity state. This operating status reflects the execution status of internal tasks within the metering module. For example, the metering module can maintain an internal state machine, updating its operating status based on received commands, internal timer events, or sensor data processing results. The running status can be the state where the metering module is performing metering operations and actively reporting its enable status, including sensor data acquisition, data processing, metering calculation, and data storage. The idle status can be the state where the metering module is not currently performing metering operations and is in a waiting or low-power mode. The verification status can be the mode in which the metering module is performing specific verification tasks such as flow accuracy detection and sensor self-testing.

[0040] After the processing unit sends the first data frame to the metering module, the metering module, after processing the request and preparing to send the response result, will monitor its own operating status in real time. If the metering module is performing metering, data processing, or other activities, its operating status will be determined as "running"; if the metering module is in a waiting command or low-power mode, its operating status will be determined as "idle"; if the metering module receives a verification mode command initiated by the main control unit, its operating status will be determined as "verification mode". The metering module encapsulates this determined operating status information into the status field of the second data frame and sends it to the processing unit along with the response result. The processing unit not only obtains the response data of the request but also the real-time operating context of the metering module, thereby enabling it to more accurately understand the response result and make subsequent decisions and controls based on the actual status of the metering module.

[0041] This application enables the metering module to synchronously transmit its current operating status information when sending response results to the processing unit. This allows the processing unit to monitor the metering module's operation in real time, such as whether it is performing metering operations, is in an idle waiting state, or has entered verification mode. This transparency of the metering module's operating status helps the processing unit more accurately determine the validity of response results, optimize communication strategies, and promptly detect and handle any potential anomalies in the metering module, thereby improving the reliability and intelligence of the entire gas system's data communication.

[0042] Step 105: Send the second data frame to the processing unit.

[0043] The method of sending the second data frame can be referred to the description of the method of sending the first data frame, and will not be repeated here.

[0044] This application achieves structured and reliable data communication between the processing unit and the metering module. Furthermore, through the design of the frame structure, particularly the flexible combination of control codes, length fields, and data fields, different types of functional data and response results can be effectively encapsulated and transmitted, solving the problem of limited data transmission fields in related technologies. For example, if more complex diagnostic information needs to be transmitted, simply carry more data in the data field and adjust the value of the length field accordingly, without changing the basic framework of the communication protocol.

[0045] In some embodiments, the method further includes: adjusting the transmission frequency and content of functional data according to the importance priority and degree of change of the functional data; adopting a real-time transmission mode for functional data that is highly important and changes frequently; and adopting a periodic transmission mode for functional data that is low in importance and changes slowly.

[0046] The importance priority of functional data can be determined by its criticality to system operation or user safety. For example, safety-related alarm data and critical metering data typically have high priority, while some configuration parameters and log information may have lower priority. The importance priority of functional data can be determined based on preset business rules, data type classifications, or user configurations. The importance priority, from highest to lowest, is: abnormal status data, metering data (flow, pressure, temperature), operating parameter data, and clock information. The degree of change in functional data can be determined by the frequency or magnitude of data value changes over time. For example, real-time flow data may change frequently, while information such as device serial numbers and firmware versions may change gradually or remain unchanged. The degree of change in functional data can be assessed through historical data analysis, sensor sampling frequency, or data update strategies.

[0047] Adjusting the transmission frequency and content of functional data allows for the selection of more frequent (e.g., real-time) or sparser (e.g., periodic) transmission methods based on data characteristics. It also allows for transmitting only key fields in some modes or the complete data in others. Real-time transmission mode aims to send data as quickly as possible to minimize latency. This typically involves sending data immediately after its generation or upon reaching specific trigger conditions (e.g., thresholds, event occurrences). For example, interrupt-driven or event-triggered mechanisms can be used to immediately initiate the data frame encapsulation and transmission process once data is generated or its state changes; or a very short polling cycle can be set to check for data updates and transmit them frequently. Periodic transmission mode sends data at preset fixed time intervals. This is suitable for data that does not require high real-time performance but needs to be updated or summarized periodically. For example, timers or schedulers can be used to trigger data acquisition, encapsulation, and transmission at each preset period (e.g., every minute, every hour); or periodic data transmission can be concentrated during system idle periods or low-power modes to optimize resource utilization.

[0048] This application assesses the importance, priority, and variability of functional data before the processing unit encapsulates it into a first data frame according to a preset frame structure, obtaining an evaluation result. Based on the evaluation result, the processing unit intelligently selects an appropriate transmission mode. If the evaluation result indicates that the functional data is highly important and changes frequently, the processing unit immediately initiates a real-time transmission mode to ensure that the data is quickly encapsulated and sent to the metering module. This ensures that critical information (e.g., safety alarms) can be processed in a timely manner, thereby maintaining the system's rapid response capability and security. If the evaluation result indicates that the functional data is of low importance and changes slowly, the processing unit adopts a periodic transmission mode, caching the data and transmitting it in batches over a preset longer time interval. This effectively reduces unnecessary communication overhead, lowers the power consumption of the processing unit and the metering module, and optimizes the utilization of communication bandwidth.

[0049] This application can intelligently adjust data transmission strategies based on the importance, priority, and variability of functional data, avoiding the resource waste and inefficiency problems caused by a uniform transmission mode. This ensures timely and prioritized transmission of critical data, guaranteeing the system's real-time responsiveness and security. Simultaneously, non-critical data is transmitted using more economical methods, effectively reducing communication power consumption and bandwidth usage, thereby significantly improving the overall efficiency, reliability, and energy utilization of gas system data communication.

[0050] In some embodiments, the frame structure further includes a checksum field; the first data frame includes a first checksum; the method further includes: calculating the first checksum according to a preset checksum rule based on the byte values ​​of the first control code, the first length field, and the first data field by the processing unit, and filling the first checksum into the checksum field; after receiving the first data frame by the metering module, recalculating the checksum based on the same preset checksum rule, and comparing the recalculated checksum with the first checksum; if the comparison matches, a response step is executed; if the comparison does not match, a checksum error prompt is sent to the processing unit. This achieves unified frame parsing rules between the two communicating parties, avoiding parsing errors. The checksum can be a 1-byte value obtained by summing the byte values ​​of all data from the frame header to the checksum and then dividing by 255 (0xFF), used to verify the integrity of data transmission.

[0051] In some embodiments, the frame structure further includes a wake-up code field and an end-of-frame field; the wake-up code field is used to wake up the metering module and enter the working state, and the end-of-frame field is used to indicate the end of data frame transmission; the method further includes: filling a preset wake-up code into the wake-up code field and a preset end-of-frame field; the method further includes: filling a preset wake-up code into the wake-up code field and a preset end-of-frame field. This effectively unifies the frame parsing rules between the two communicating parties and avoids parsing errors. The wake-up code is a fixed byte sequence used to wake up the metering module and enter the working state when the processing unit communicates with the metering module. For example, the preset wake-up code can be 3 bytes of 0xFE. The end-of-frame field can be a fixed byte at the end of the communication frame, used to indicate the completion of a frame of data transmission and to define the boundary of the data frame. For example, the preset end-of-frame field can be 0x0D.

[0052] In some embodiments, the method further includes: if the processing unit does not receive the second data frame within a preset time, it determines that the communication has timed out; the processing unit may retransmit the first data frame, the number of retransmissions not exceeding a preset threshold; if the second data frame is still not received after exceeding the preset threshold, a communication fault indication is output. The fault tolerance of communication is improved through the timeout retransmission and fault indication mechanism.

[0053] In some embodiments, the gas device includes multiple metering modules; the frame structure also includes an address field used to identify the target metering module; the method further includes: determining the corresponding address code based on the identification information of the target metering module to be communicated, and filling the address code into the address field; after receiving the first data frame, the metering module compares its own identification information with the address code in the address field; if they match, it executes a response step; if they do not match, it ignores the first data frame. Accurate communication between multiple metering modules is achieved through the address field, expanding application scenarios.

[0054] In some embodiments, the method further includes: encrypting the functional data in the first data field using a preset encryption algorithm by the processing unit to obtain encrypted functional data; filling the encrypted functional data into the first data field and completing the encapsulation of the first data frame; after receiving the first data frame, the metering module decrypts the encrypted functional data in the first data field using a preset decryption algorithm corresponding to the preset encryption algorithm; if decryption is successful, a response step is executed; if decryption fails, the response step is refused and a decryption error message is sent to the processing unit; the preset encryption algorithm can be a symmetric encryption algorithm or an asymmetric encryption algorithm.

[0055] In some embodiments, the working state also includes an abnormal state, which includes at least abnormal traffic acquisition, abnormal power supply voltage, and abnormal communication link. The method further includes: if the metering module detects that it is in an abnormal state in real time, it does not need to wait for the processing unit to send the first data frame, but actively encapsulates an abnormal reporting frame according to a preset frame structure. The abnormal reporting frame includes an abnormal identification code for identifying the abnormal event, abnormal type information representing the specific type of abnormality, and time information of the abnormality occurrence. The metering module sends the abnormal reporting frame to the processing unit. After receiving the abnormal reporting frame, the processing unit outputs an abnormal alarm prompt and records the abnormal type information and the time information of the abnormality occurrence.

[0056] In some embodiments, the fields in the frame structure include mandatory fields and optional fields; the mandatory fields include a control code, a length field, and a data field, and the optional fields include a checksum field, a wake-up code field, a terminator field, an address field, and an encryption field; the method further includes: selecting to enable some or all of the optional fields according to the actual communication scenario and safety level requirements of the gas device; when the optional fields are enabled, filling the field content according to the configuration rules of the corresponding fields and incorporating it into the frame structure; the optional fields that are not enabled are not included in the frame structure, so as to simplify the frame structure and improve communication efficiency.

[0057] For example, in a single-module communication scenario for a household gas meter, the security requirements are low, and there is no need for multi-module differentiation or data encryption. In this case, only the wake-up code field, end-of-module field, and checksum field can be enabled to ensure clear module wake-up frame boundaries and data integrity. Unenabled address and encryption fields are not included in the frame structure, making the frame structure simpler and reducing transmission overhead. In industrial scenarios involving centralized management of multiple metering modules and transmission of commercial metering data, the security requirements are higher. In this case, all optional fields can be enabled. The address field is used to differentiate between different target modules, the encryption field ensures the security of metering data transmission, and the checksum, wake-up code, and end-of-module fields ensure communication reliability and clear boundaries, meeting the communication needs of high-security multi-module systems.

[0058] This application divides the frame structure into mandatory and optional fields. Mandatory fields ensure the implementation of basic communication functions, while optional fields provide flexible functional extensions. This allows the data communication method to dynamically adjust the frame structure composition according to the actual communication scenario and safety level requirements of the gas appliance. For scenarios with low safety requirements and a single module, disabling some optional fields simplifies the frame structure, reducing transmission overhead and parsing complexity. For scenarios with high safety requirements and multiple modules, enabling all optional fields provides complete extended functionality, ensuring the security, accuracy, and reliability of communication.

[0059] The following describes the data communication method provided in the embodiments of this application. Figure 2 As shown, Figure 2 This is a schematic diagram of the frame structure in the data communication method provided in this application embodiment. The frame structure may include a 3-byte wake-up code, a 1-byte frame header, a 1-byte control code, a 1-byte length field, an N-byte data field, a 4-byte status field, a 1-byte checksum, and a 1-byte end character. The length field is the length of the data field; the data field includes communication data; the status field is the status information of the metering module, and downlink frames do not have a status field.

[0060] Part 1: Reading Measurement Data. This can be initiated by an external master control unit, control code: 0x01; data field: none. It can also be responded to by UGS (including active reporting), control code: 0xA1, data field: as shown in Table 1. Table 1 is a schematic table of data fields in the second data frame corresponding to reading measurement data.

[0061] Table 1

[0062] For example, the main control unit sends: FE FE FE 5D 01 00 5E 0D. Here, FE FE FE is the wake-up code, used to wake up the UGS and put it into working mode; 5D is the frame header, used to identify that the following content is business data; 01 is the control code, representing the main control unit's instruction to read metering data; 00 is the length field, meaning the data field is empty; 5E is the checksum, obtained by summing the values ​​of the frame header, control code, and length field, and then taking the remainder when divided by 255; 0D is the end marker, indicating the completion of a frame of data transmission.

[0063] UGS Response: FE FE FE 5D A1 1E 0A 00 00 00 0A 00 00 00 04 00 00 00 00 00CE 09 00 00 4C 0D A7 03 98 03 6B 12 86 0E 10 0E 80 00 00 00 58 0D. Where FE FEFE is the wake-up code, used to wake up the main control unit and put it into working mode; 5D is the frame header; A1 is the control code, corresponding to the UGS response's instruction to read metering data; 1E is the length field, which is 30 in decimal, indicating that the length of the subsequent data field is 30 bytes. The data field contains four bytes for the positive cumulative flow status, four bytes for the positive cumulative flow standard status, and four bytes for the reverse cumulative flow, as well as real-time flow rate, temperature, and pressure. The sum of these bytes is 30, consistent with the value in the length field. 80 00 00 00 is the status field, indicating that UGS is currently in an active reporting enabled state. 58 is the checksum, obtained by summing the values ​​of the frame header, control code, length field, and data field and then taking the remainder after dividing by 255. 0D is the end-of-transmission character, indicating the end of this response frame transmission.

[0064] Part Two: Verification Mode. This can be initiated by an external master control unit, control code: 0x02; data fields: as shown in Table 2, which is a schematic table of data fields in the first data frame corresponding to the verification mode. It can also be responded to by UGS (including active reporting), control code: 0xA2; data fields: as shown in Table 3, which is a schematic table of data fields in the second data frame corresponding to the verification mode.

[0065] Table 2

[0066] Table 3

[0067] For example, the main control unit sends: FE FE FE 5D 02 03 55 AA 00 61 0D (enter verification mode). 02 is the control code, corresponding to the verification mode command initiated by the main control unit; 03 is the length field, indicating that the data field length is 3 bytes; the three bytes of the data field are 55, AA, and 00, where 55 and AA are fixed prefix bytes of the verification mode command, and 00 corresponds to the operation command to enter verification mode; 61 is the checksum.

[0068] UGS Response: FE FE 5D A2 05 00 00 00 00 00 20 00 00 00 24 0D (Status byte 0x20000000 indicates Bit 5 is set to 1, entering detection mode). Control code A2 corresponds to the verification mode instruction in the UGS response; the length field is 05, indicating that the data field length is 5 bytes. The first byte of the data field, 00, is feedback on entering verification mode. The following four bytes are the cumulative usage for verification, displayed as 00 00 00 00, indicating that no actual usage has occurred since entering mode. The subsequent status byte, 0x20000000, indicates that Bit 5 is set to 1, representing that UGS has entered detection mode, which is the current status feedback. 24 is the checksum.

[0069] Part 3: Reading the Real-Time Clock. This can be initiated by an external master control unit, control code: 0x03; data field: none. It can also be responded to by UGS (including proactive reporting), control code: 0xA3; data field: as shown in Table 4. Table 4 is a schematic table illustrating the data fields corresponding to reading or setting the real-time clock.

[0070] Table 4

[0071] For example, the master control unit sends: FE FE FE 5D 03 00 60 0D. Here, 03 is the control code, corresponding to the master control unit's read real-time clock command; the length field is 00; and 60 is the checksum. The UGS response is: FE FE 5D A3 07 21 11 12 0513 54 00 00 00 00 00 B7 0D. Here, A3 is the control code, corresponding to the UGS's read real-time clock command response; the length field is 07, indicating that the data field is 7 bytes long, representing time information in BCD code, with each byte corresponding to a different time part: 21 corresponds to the year (21 years); 11 corresponds to the month (November); 12 corresponds to the day (12th); 05 corresponds to the week (Friday); 13 corresponds to the hour (13:00); 54 corresponds to the minute (54 minutes); and 00 corresponds to the second (00 seconds). These bytes are combined to obtain the current real-time clock information of the UGS. 00 00 00 00 is the state field indicating that UGS is in a normal idle state. B7 is the checksum.

[0072] Part 4: Setting the Real-Time Clock. This can be initiated by an external master control unit, control code: 0x04; data field: as shown in Table 4. It can also be responded to by the UGS (including proactive reporting), control code: 0xA4; data field: none. For example, the master control unit sends: FEFE FE 5D 04 07 21 11 12 05 14 02 10 D7 0D. Here, 04 is the control code, corresponding to the master control unit's instruction to set the real-time clock; the length field is 07, indicating that the data field length is 7 bytes, which are time information represented in BCD code. D7 is the checksum. UGS response: FE FE 5D A4 00 00 00 00 00 010D. A4 is the control code, corresponding to the UGS response to set the real-time clock command; the length field is 00, indicating that the data field of this response has no content, because the response to the setting command only needs to provide feedback on the operation status; 01 is the checksum; 0D is the end character.

[0073] Part 5, Reading Operating Parameters. This can be initiated by an external master control unit, control code: 0x05; data field: none. It can also be responded to by UGS (including proactive reporting), control code: 0xA5; data field: as shown in Table 5. Table 5 is a schematic table of data fields in the second data frame corresponding to reading operating parameters.

[0074] Table 5

[0075] For example, the main control unit sends: FE FE FE 5D 05 00 62 0D, where 05 is the control code, corresponding to the main control unit's instruction to read operating parameters; 00 is the length field, indicating that the data field is empty; and 62 is the checksum.

[0076] UGS response: FE FE FE 5D A5 40 00 00 00 00 00 00 0E 01 00 00 15 0C 01 0006 00 00 00 24 E8 03 01 00 00 00 FC 0C E2 02 AF 07 3C 42 CC 62 39 5A FC 64 3981 52 13 36 29 03 2D 03 BF 08 71 F6 2B 43 68 2D 2C 43 6B 12 AA 10 7F 11 80 0000 00 EA 0D, where A5 is the control code, corresponding to the UGS response read operation parameter command; 40 is the length field, indicating that the second data field of the UGS response frame is 64 bytes long; the 64 bytes following the length field cover various key parameters in the gas meter operation process, such as flow-related parameters, equipment status parameters, calibration parameters, etc.; EA is the checksum.

[0077] Part 6. User Maximum Load Threshold Setting. This can be initiated by an external master control unit, control code: 0x0C; data fields: as shown in Table 6. Table 6 is a schematic table of the data fields in the first and second data frames corresponding to the user maximum load threshold setting. It can also be responded to by UGS, control code: 0xAC; data fields: as shown in Table 6.

[0078] Table 6

[0079] For example, the master control unit sends: FE FE FE 5D 0C 02 C0 12 3D 0D. Here, 0C is the control code, corresponding to the master control unit's instruction to set the user's maximum load threshold. The length field is 02, indicating that the data field length is 2 bytes, which is the set user maximum load value. The aforementioned 2 bytes, C0 12, correspond to the user's maximum load value in L / h. These two bytes transmit the desired maximum load threshold to UGS. 3D is the checksum.

[0080] UGS Response: FE FE 5D AC 02 C0 12 00 00 00 00 DD 0D. Here, AC is the control code, corresponding to the user maximum load threshold setting instruction in the UGS response. The length field is 02, indicating that the data field length is 2 bytes. The 2 bytes of C0 12 represent the received user maximum load value fed back by UGS, which matches the value sent by the main control unit, indicating that UGS has successfully received the setting content. DD is the checksum.

[0081] Part 7. Abnormal Event Threshold Time Setting. This can be initiated by an external master control unit, control code: 0x0D; data fields: as shown in Table 7. Table 7 is a schematic table of the data fields in the first and second data frames corresponding to the abnormal event threshold time setting. It can also be responded to by UGS, control code: 0xAD; data fields: as shown in Table 7.

[0082] Table 7

[0083] For example, the master control unit sends: FE FE FE 5D 0D 03 18 1E 14 B7 0D. Here, 0D is the control code, corresponding to the master control's instruction to set the threshold time for abnormal events. The length field is 03, indicating that the data field length is 3 bytes. These 3 bytes correspond to the threshold time parameters for three abnormal events. Within these 3 bytes, 18 corresponds to the duration of a small flow leakage in hours; 1E corresponds to the duration of a gas quality anomaly in seconds; and 14 corresponds to the duration of reverse flow in seconds. These values ​​are the threshold times for abnormal events that the master control wants to set. B7 is the checksum. UGS response: FE FE 5D AD 0318 1E 14 00 00 00 00 57 0D. In this data structure, AD is the control code, corresponding to the abnormal event threshold time setting instruction in the UGS response. The length field is 03, indicating that the data field length is 3 bytes. The values ​​of 18 1E 14 in the above 3 bytes are consistent with the values ​​sent by the master controller, indicating that UGS has successfully received the threshold time setting content. 57 is the checksum.

[0084] Part 8. Constant Current Alarm Setting. This can be initiated by an external main control unit, control code: 0x0E; data fields: as shown in Table 8. Table 8 is a schematic table of the data fields in the first and second data frames corresponding to the constant current alarm setting. It can also be responded to by UGS, control code: 0xAE; data fields: as shown in Table 8.

[0085] Table 8

[0086] The constant current alarm refers to an alarm triggered under normal usage conditions after account registration when the ultrasonic gas meter operates at any relatively constant flow rate for a duration exceeding the manufacturer's stated setting. Table 9 shows the configuration parameters for the constant current alarm of the ultrasonic gas meter. As shown in Table 9, q1 represents constant flow threshold 1, q2 represents constant flow threshold 2, q3 represents constant flow threshold 3, and q4 represents constant flow threshold 4. t1 represents constant flow timeout threshold 1, t2 represents constant flow timeout threshold 2, and t3 represents constant flow timeout threshold 3. q1-q4 and t1-t can be configured by the user.

[0087] If the user end is not configured, UGS has a set of default parameters: q1=Qmin (minimum flow); q2=Qt (boundary flow); q3=0.5Qmax (half of maximum flow); q4=Qr (overload flow). t1=10h, t2=5h, t3=1h. Wherein, maximum flow: Under normal operating conditions, the gas meter reading meets the upper limit of the maximum permissible error (MPE) requirement (e.g., G1.6-2.5m³ / h, G2.5-4m³ / h, G4-6m³ / h). Minimum flow: Under normal operating conditions, the gas meter reading meets the lower limit of the MPE requirement (e.g., G1.6-0.016m³ / h, G2.5-0.025m³ / h, G4-0.04m³ / h). Boundary flow: The flow rate between the maximum and minimum flow rates, dividing the gas meter's flow range into "high" and "low" zones (e.g., G1.6-0.25 m³ / h, G2.5-0.4 m³ / h, G4-0.6 m³ / h). Overload flow: The maximum flow rate at which the gas meter's reading meets MPE requirements for a short period, and subsequently maintains its metering characteristics under rated operating conditions (e.g., G1.6-3 m³ / h, G2.5-4.8 m³ / h, G4-7.2 m³ / h).

[0088] For example, the main control unit sends: FE FE FE 5D 0E 0B 10 00 FA 00 E2 04 C4 09 0A 05 01AD 0D. Here, 0E is the control code, corresponding to the constant current alarm setting command initiated by the main control unit. The length field is 0B, which is 11 in decimal, indicating that the data field length is 11 bytes, corresponding to the various threshold parameters of the constant current alarm. Within the 11 bytes of the data field, 2 bytes 10 00 correspond to constant flow threshold 1 (unit: L / h); 2 bytes FA 00 correspond to constant flow threshold 2; 2 bytes E2 04 correspond to constant flow threshold 3; 2 bytes C4 09 correspond to constant flow threshold 4; 1 byte 0A corresponds to constant flow timeout threshold 1 (unit: hours); 1 byte 05 corresponds to timeout threshold 2; and 1 byte 01 corresponds to timeout threshold 3. AD is the checksum.

[0089] UGS Response: FE FE 5D AE 0B 10 00 FA 00 E2 04 C4 09 0A 05 01 00 00 00 004D 0D. Here, AE is the control code, corresponding to the constant current alarm setting instruction in the UGS response. The length field is 0B, indicating that the data field length is 11 bytes. The byte content of the above data field is completely consistent with that sent by the master controller, representing that the UGS has successfully received the constant current alarm threshold setting. 4D is the checksum.

[0090] Part 9, Factory Activation Settings. This can be initiated by an external master control unit, control code: 0x0F; data field: none. It can also be responded to by UGS (including proactive reporting), control code: 0xAF; data field: as shown in Table 10. Table 10 is a schematic table of data fields in the second data frame corresponding to the factory activation settings.

[0091] Table 10

[0092] Factory activation involves erasing all metering-related data, resetting it to zero. Each data item is reset to zero, and then set to 1. For example, if all data items are reset to zero, the data field response will be 0x03FF.

[0093] For example, the main control unit sends: FE FE FE 5D 0F 00 6C 0D, where 0F is the control code, corresponding to the factory enable setting command; 00 is the length field; and 6C is the checksum. The UGS response is: FE FE 5D AF 02 FF 03 00 00 00 0010 0D, where AF is the control code, the response to the factory enable setting command; 02 is the length field; FF 03 is the data field, carrying the response parameters for the factory enable setting; and 10 is the checksum.

[0094] Part 10, Operating Condition / Standard Condition Switching Settings. This can be initiated by an external master control unit, control code: 0x11; data fields: as shown in Table 11, which is a schematic table of data fields in the first data frame corresponding to the operating condition / standard condition switching settings. It can also be responded to by UGS (including active reporting), control code: 0xB1; data fields: as shown in Table 12, which is a schematic table of data fields in the second data frame corresponding to the operating condition / standard condition switching settings.

[0095] Table 11

[0096] Table 12

[0097] The operating condition / standard condition conversion function involves the UGS simultaneously measuring both the operating condition cumulative flow and the standard condition cumulative flow during operation. This setting is retained even after power loss and is fed back to the processing unit via the status field of the reporting frame, indicating the type of cumulative flow to be acquired. For example, the main control unit sends: FE FE FE 5D 11 01 01 70 0D, where the control code 11 corresponds to the operating condition / standard condition conversion setting instruction; the length field is 01; the data field 01 represents the conversion mode parameter; and the checksum is 70. The UGS responds: FE FE 5D B1 01 55 00 00 00 00 64 0D, where the control code is B1; the length field is 01; the data field 55 represents the response parameter, indicating that the UGS has successfully received and implemented the conversion mode setting; and the checksum is 64.

[0098] Figure 3 A schematic diagram of a data communication device provided in an embodiment of this application is shown below. Figure 3 As shown, this application provides a data communication device applied to a gas appliance including a processing unit and a metering module. The device 300 includes: an acquisition module 301 for acquiring functional data to be transmitted from the gas appliance; a first encapsulation module 302 for encapsulating the functional data into a first data frame according to a preset frame structure through the processing unit; the frame structure includes at least a control code, a length field, and a data field; a first transmission module 303 for transmitting the first data frame to the metering module; a second encapsulation module 304 for responding to the first data frame through the metering module to obtain a response result; and encapsulating the response result into a second data frame according to the frame structure; and a second transmission module 305 for transmitting the second data frame to the processing unit.

[0099] To implement the method of the embodiments of this application, Figure 4 A schematic diagram of the structure of an electronic device provided in an embodiment of this application, such as... Figure 4 As shown, this application embodiment also provides an electronic device 40 that may include: a memory 401 for storing a computer program; and a processor 402 for implementing the method described above when executing the computer program. The processor 402 can implement the steps of any of the methods described above, which will not be repeated here.

[0100] It should be noted that the electronic devices provided in the above embodiments and the above method embodiments belong to the same concept, and their specific implementation process can be found in the method embodiments, which will not be repeated here.

[0101] Of course, in practical applications, such as Figure 4As shown, the electronic device 40 may further include at least one network interface 403. Various components in the electronic device are coupled together via a bus system 404. It is understood that the bus system 404 is used to implement communication between these components. In addition to a data bus, the bus system 404 also includes a power bus, a control bus, and a status signal bus. However, for clarity, in... Figure 4 Various buses are labeled as bus systems 404. The number of processors 402 can be at least one. Network interface 403 is used for wired or wireless communication between electronic devices and other devices. Memory 401 in this embodiment is used to store various types of data to support the operation of the electronic device. The methods disclosed in the above embodiments can be applied to processor 402, or implemented by processor 402. Processor 402 may be an integrated circuit chip with signal processing capabilities. In implementation, each step of the above method can be completed by the integrated logic circuit of the hardware in processor 402 or by instructions in software form. The processor 402 can be a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. Processor 402 can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. A general-purpose processor can be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of this application can be directly reflected as the combined execution of hardware and software modules in a microcontroller. The software module can reside in a storage medium located in memory 401. Processor 402 reads information from memory 401 and, in conjunction with its hardware, completes the steps of the aforementioned method. In an exemplary embodiment, electronic device 40 can be implemented by one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontrollers (MCUs), microprocessors, or other electronic components to execute the aforementioned method.

[0102] Specifically, embodiments of this application provide a computer-readable storage medium storing a computer program thereon, such as a memory 401 storing the computer program, which can be executed by a processor 402 to complete the aforementioned method steps. The computer-readable storage medium may be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface memory, optical disc, or CD-ROM.

[0103] In addition, each functional unit in the various embodiments of this application can be integrated into one processing unit, or each unit can be a separate unit, or two or more units can be integrated into one unit; the integrated unit can be implemented in hardware or in the form of hardware plus software functional units.

[0104] Those skilled in the art will understand that all or part of the steps of the above method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it performs the steps of the above method embodiments. The aforementioned storage medium includes various media capable of storing program code, such as mobile storage devices, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

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

Claims

1. A data communication method, characterized in that, The method, applied to a gas apparatus including a processing unit and a metering module, comprises: Obtain the functional data to be transmitted from the gas device; The processing unit encapsulates the functional data into a first data frame according to a preset frame structure; the frame structure includes at least a control code, a length field, and a data field. Send the first data frame to the metering module; The metering module responds to the first data frame to obtain a response result; the response result is then encapsulated into a second data frame according to the frame structure. The second data frame is sent to the processing unit.

2. The method according to claim 1, characterized in that, The first data frame includes a first control code; the first control code includes a first region code for characterizing the initiation type of the first data frame and a second region code for characterizing the functional data; The step of encapsulating the functional data into a first data frame according to a preset frame structure by the processing unit includes: The first region code of the first control code is determined based on the attributes of the first data frame initiated by the processing unit. The second region code of the first control code is determined based on the function type corresponding to the function data.

3. The method according to claim 2, characterized in that, The second data frame includes a second control code; the second control code includes a third region code for characterizing the initiation type of the second data frame and a fourth region code for characterizing the functional data; The method further includes: The third region code of the second control code is determined based on the attribute that the second data frame is initiated or responded to by the metering module; the first region code is different from the third region code; The fourth region code of the second control code is determined based on the function type corresponding to the function data; the fourth region code matches the second region code.

4. The method according to claim 1, characterized in that, The first data frame includes a first data field; the function type corresponding to the function data includes a first type of reading data from the metering module and a second type of setting the function of the metering module; The step of encapsulating the functional data into a first data frame according to a preset frame structure by the processing unit includes: When the function type is the first type, the first data field is determined to be an empty data field; When the function type is the second type, the function parameters for setting the function of the metering module are obtained from the function data; The first data field is determined based on the functional parameters.

5. The method according to claim 4, characterized in that, The second data frame includes a second data field; The step of encapsulating the response result into a second data frame according to the frame structure includes: If the function type is the first type, the second data field is determined based on the response result; When the function type is the second type, the second data field is determined to be an empty data field.

6. The method according to claim 5, characterized in that, The first data frame includes a first length field; the second data frame includes a second length field; the method further includes: The value of the first length field is determined based on the number of bytes in the first data field; the value of the first length field is the decimal equivalent of the number of bytes. The value of the second length field is determined based on the number of the second bytes in the second data field, and the value of the second length field is the decimal equivalent of the number of the second bytes.

7. The method according to claim 1, characterized in that, The second data frame includes a state field; the step of encapsulating the response result into a second data frame according to the frame structure includes: The state domain is determined based on the working state of the metering module; the working state includes at least the running state of performing metering operations, the idle state of not performing metering operations, and the verification state of performing verification operations.

8. The method according to any one of claims 1-7, characterized in that, The method further includes: The transmission frequency and content of the functional data are adjusted according to the importance, priority, and degree of change of the functional data. For the functional data that is of high importance and changes frequently, a real-time transmission mode is adopted; For functional data that is of low importance and changes slowly, a periodic transmission mode is adopted.

9. A data communication device, characterized in that, Applied to a gas device including a processing unit and a metering module, the device includes: The acquisition module is used to acquire the functional data to be transmitted by the gas device; The first encapsulation module is used to encapsulate the functional data into a first data frame according to a preset frame structure through the processing unit; the frame structure includes at least a control code, a length field, and a data field. The first sending module is used to send the first data frame to the metering module; The second encapsulation module is used to respond to the first data frame through the metering module to obtain a response result; and to encapsulate the response result into a second data frame according to the frame structure. The second sending module is used to send the second data frame to the processing unit.

10. A computer-readable storage medium, characterized in that, It stores a computer program, which is loaded by a processor to perform the steps of the method according to any one of claims 1-8.

Images