Distributed information entry management method and system applied to precast concrete members

Abstract

The application provides a distributed information entry management method and system applied to prefabricated concrete components, and relates to the technical field of building industrialization. When starting a production process of each prefabricated concrete component, an initial production state code is generated according to design parameters and a production path planning and is attached to the component. When the component enters a current production stage, a current production stage identifier and a to-be-entered field characteristic segment are parsed from the state code. According to this, a field entry value is collected. Then, the entry value is compressed and converted to generate a current field propagation unit, wherein the production stage identifier, the compressed form of the entry value and a subsequent target node identifier are embedded. Then, an updated field propagation unit set and a new to-be-entered field characteristic segment are generated by combination and reconstruction. Further, an updated production state code is generated and is reattached to the component. The application realizes real-time information collection, dynamic updating and orderly flow transfer, and can comprehensively and accurately record production information.

Description

Technical Field

[0001] This invention relates to the field of building industrialization technology, and more specifically, to a distributed information entry and management method and system for precast concrete components. Background Technology

[0002] With the rapid development of industrialized construction, precast concrete components have been widely used in building engineering due to their advantages such as high efficiency, environmental friendliness, and controllable quality. However, as the production scale and complexity of precast concrete components increase, information management in the production process faces numerous challenges.

[0003] Traditional methods of managing precast concrete component information often employ a centralized recording approach, where dedicated personnel record and organize component production information at fixed points. This method has significant limitations. Firstly, because the recording points are relatively fixed, delays and errors can easily occur in information transmission at different stages of component production, leading to untimely updates and an inability to accurately reflect the real-time production status of the components. For example, if information transmission is delayed between the pouring and curing stages, it may affect subsequent production planning. Secondly, centralized information management struggles to effectively integrate and analyze the massive amounts of data generated during component production. Data generated at different production stages are independent and lack effective correlation and aggregation mechanisms, making it difficult for managers to grasp the overall production situation and promptly identify and address problems. Furthermore, information is easily lost or damaged during component circulation, further impacting the accuracy and reliability of information management. Summary of the Invention

[0004] In view of the aforementioned problems, and in conjunction with the first aspect of the present invention, the present invention provides a distributed information entry and management method for precast concrete components, the method comprising: When the production process of each precast concrete component begins, an initial production status code is generated based on the design parameter information and production path planning information of the precast concrete component. The initial production status code is attached to the precast concrete component body. The initial production status code contains a current production stage identifier segment and a field feature segment to be entered. The field feature segment to be entered is used to characterize the propagation path and aggregation method of the field to be entered in the current production stage in subsequent production stages. When a precast concrete component enters the current production stage, the current production stage identifier segment and the field feature segment to be entered are parsed from the current production status code carried by the precast concrete component body. The field entry value is collected at the current production stage according to the field propagation path information recorded in the field feature segment to be entered. The collected field input values ​​are compressed and converted according to the field aggregation method recorded in the feature segment of the field to be input, and a current field propagation unit is generated. The current field propagation unit is embedded with the current production stage identifier, the compressed representation of the field input value, and the target node identifier set of the field in the subsequent production stage. The current field propagation unit is combined and reconstructed with other field propagation units parsed from the current production status code to generate an updated field propagation unit set containing the historical field propagation unit sequence and the current field propagation unit, and a new field feature segment to be entered is generated based on the updated field propagation unit set. The new field feature segment to be entered is recombined with the component base identification segment of the precast concrete component to generate an updated production status code, and the updated production status code is reattached to the precast concrete component body.

[0005] Furthermore, the present invention also provides a distributed information entry and management system for precast concrete components, comprising: A processor; a machine-readable storage medium for storing machine-executable instructions of the processor; wherein the processor is configured to execute the above-described distributed information entry and management method for precast concrete components by executing the machine-executable instructions.

[0006] Based on the above, when each precast concrete component begins its production process, an initial production status code is generated and attached to the component body according to design parameters and production path planning information. When the component enters the current production stage, relevant information is parsed from its production status code, and field input values ​​are collected based on the feature segments of the fields to be entered. The collected field input values ​​are compressed and converted to generate the current field propagation unit, which embeds the current production stage identifier, the compressed representation of the field input values, and the target node identifier set. This not only effectively compresses and organizes the information, reducing the burden of data storage and transmission, but also clarifies the propagation path and aggregation method of information in subsequent production stages. Through combination and reconstruction, an updated set of field propagation units and new feature segments of the fields to be entered are generated, and an updated production status code is further generated and reattached to the component body. This achieves dynamic updating of the production status code and accumulation of information, enabling comprehensive and accurate recording and management of all information in the precast concrete component production process, which helps to improve production efficiency, ensure product quality, and reduce production costs. Attached Figure Description

[0007] Figure 1 This is a schematic diagram of the execution flow of the distributed information entry and management method for precast concrete components provided in an embodiment of the present invention.

[0008] Figure 2This is a schematic diagram of exemplary hardware and software components of a distributed information entry and management system for precast concrete components provided in an embodiment of the present invention. Detailed Implementation

[0009] Figure 1 This is a flowchart illustrating a distributed information entry and management method for precast concrete components, provided by an embodiment of the present invention. A detailed description follows.

[0010] Step S110: When the production process of each precast concrete component begins, an initial production status code is generated based on the design parameter information and production path planning information of the precast concrete component. The initial production status code is attached to the precast concrete component body. The initial production status code contains a current production stage identifier segment and a field feature segment to be entered. The field feature segment to be entered is used to characterize the propagation path and aggregation method of the field to be entered in the current production stage in subsequent production stages.

[0011] Step S111: Extract the design drawing data of precast concrete components from the production scheduling system, parse the component outline parameters, internal reinforcement network parameters and concrete strength grade parameters contained in the design drawing data, and convert the component outline parameters into fixed-length outline feature codes.

[0012] Specifically, in an embodiment of precast concrete component production management, when a floor slab component is ready to begin its production process, the electronic design drawing data file of the floor slab component is first retrieved from the production scheduling system. This design drawing data file is parsed to extract the component's outline parameters, which describe its geometry. These parameters typically exist as a set of three-dimensional spatial coordinate points, such as the length, width, thickness, and chamfer information of the floor slab. Simultaneously, the internal reinforcement network parameters are parsed, including the diameter, quantity, arrangement, and interconnections of the reinforcing bars. Furthermore, the concrete strength grade parameters, such as C30 or C40, are extracted. To convert these parameters into a fixed-length outline feature code, a preset hash mapping function is invoked to map the sequence of points representing the component's outline parameters onto a fixed-length binary byte. For example, by calculating the mean, variance, and higher-order moments of the three-dimensional spatial coordinates of the outline point set, a set of statistical feature values ​​is generated. These statistical feature values ​​are then quantized and encoded into a binary string of length L_pro, which serves as the outline feature code.

[0013] Step S112: Convert the main reinforcement distribution density parameter, stirrup spacing parameter, and embedded part location parameter in the internal reinforcement network parameters of the component into main reinforcement density feature code, stirrup spacing feature code, and embedded part location feature code, respectively. Then, sequentially combine the main reinforcement density feature code, stirrup spacing feature code, embedded part location feature code, and shape contour feature code to generate the component design feature code sequence.

[0014] Following the steps above, the internal reinforcement network parameters of the component are further processed. For the main reinforcement density parameter, based on the number of main reinforcement bars in the design drawings and the effective area of ​​the component cross-section, the number of main reinforcement bars per unit area is calculated. This density value is then converted into a binary main reinforcement density feature code of length L_main using linear quantization encoding. For the stirrup spacing parameter, the spacing value of the stirrups along the longitudinal direction of the component is extracted. This value is converted into a binary stirrup spacing feature code of length L_stirrup using interval mapping encoding. For the embedded part location parameter, the three-dimensional coordinate positions of all embedded parts on the component are parsed from the drawings. These coordinate positions are then encoded using a spatial grid method, dividing the component space into multiple grids. The position of each embedded part is represented by its grid number, ultimately generating an embedded part location feature code composed of all grid numbers, with a length of L_embed. Subsequently, the generated outline feature codes of length L_pro, main reinforcement density feature codes of length L_main, stirrup spacing feature codes of length L_stirrup, and embedded part location feature codes of length L_embed are spliced ​​together in a preset order to form a component design feature code sequence.

[0015] Step S113: Perform dimensionality reduction mapping on the component design feature coding sequence to generate component design feature code. Use the component design feature code as the core component of the component basic identification segment. Combine and splice the component design feature code with the production batch information code to generate a complete component basic identification segment.

[0016] Next, a dimensionality reduction mapping algorithm, such as Locality Sensitive Hashing (LSH), is applied to the obtained component design feature encoding sequence. This algorithm takes the high-dimensional component design feature encoding sequence as input and maps it to a fixed-length component design feature code, much shorter than the original length, through a set of random hash functions. Specifically, the algorithm uses K randomly generated hyperplanes, each dividing the feature space into two regions. A binary bit (0 or 1) is generated based on which side of each hyperplane the component design feature encoding sequence falls on. These K bits are then combined to form a component design feature code of length K. Subsequently, the production batch information of the floor slab component is obtained from the production scheduling system and converted into a fixed-length production batch information code according to predefined encoding rules, such as a 32-bit binary string consisting of year, month, day, and serial number. Finally, the component design feature code of length K is concatenated with the production batch information code of length L_batch, with the component design feature code first and the production batch information code second, forming a complete component basic identifier segment with a total length of K plus L_batch.

[0017] Step S114: Extract the production path planning data of precast concrete components from the production path planning system. The production path planning data includes multiple production stage names and the corresponding input field requirements for each production stage. Each input field requirement includes the field name, field data type, and a list of target nodes for the field's propagation in subsequent production stages.

[0018] Meanwhile, the pre-set production path planning data for the floor slab component is extracted from the production path planning system. This data describes the various stages the component must go through from the start of production to the finished product's warehousing. For example, the production path planning data includes the following production stage names: mold assembly stage, rebar tying stage, embedded part installation stage, concrete pouring stage, curing stage, formwork removal stage, and quality inspection stage. For each production stage, corresponding input field requirements are also defined. Taking the rebar tying stage as an example, its input field requirements may include: field name "Tying Operator ID", field data type "string"; field name "Tying Completion Time", field data type "timestamp"; field name "Tying Quality Self-Inspection Result", field data type "Boolean value". Among them, the propagation target node list for the "Tying Operator ID" field may indicate that this field needs to be propagated to the subsequent quality inspection stage and the finished product delivery stage for quality traceability.

[0019] Step S115: Assign a stage sequence number identifier to each production stage in the production path planning data, convert the field names in the input field requirements corresponding to each production stage into field index codes, convert the field data types into type constraint codes, and convert the list of propagation target nodes for the field in subsequent production stages into a target node bitmap.

[0020] Based on the aforementioned production path planning data, each production stage is first assigned a unique, sequentially increasing stage number. For example, the mold assembly stage is identified as S01, the rebar tying stage as S02, and so on. Next, the input field requirements for each stage are processed. For field names, a pre-defined global field name mapping table is used to convert each field name into a fixed-length field index code; for example, "Tying Operator ID" is mapped to 0001, and "Tying Completion Time" is mapped to 0002. For field data types, a data type mapping table is also used to convert them into a fixed-length type constraint code; for example, string type is mapped to 01, timestamp type to 02, and boolean type to 03. For the propagation target node list, a binary bit string of length N is generated as the target node bitmap based on the total number of all production stages N. Each bit in this bitmap corresponds sequentially to a subsequent production stage (including the current stage itself, but typically not used in the current stage). If this field needs to be propagated to a subsequent production stage, the value of the corresponding bit is set to the first state (e.g., binary 1); otherwise, it is set to the second state (e.g., binary 0). For example, for the rebar tying stage with stage number S02, the propagation target node list for its "Tying Operator ID" field includes the S05 quality inspection stage and the S07 finished product delivery stage. In a bitmap of length 7, the 5th and 7th bits are set to 1, and the remaining bits are set to 0, thus generating the target node bitmap corresponding to this field.

[0021] Step S116: Combine and encode the stage sequence number identifier, field index code, type constraint code and target node bitmap corresponding to each production stage to generate the stage entry feature code corresponding to that production stage. Arrange all the stage entry feature codes corresponding to the production stages in the order of the stage sequence number identifier to generate a stage entry feature code sequence.

[0022] Then, for each production stage, its corresponding stage sequence number, field index code, type constraint code, and the target node bitmap generated in the previous step are combined and encoded according to a predefined format. For example, the stage sequence number can be converted into a fixed-length binary string, and then concatenated with the field index code, type constraint code, and target node bitmap in sequence to form a stage entry feature code for a specific field in that stage. If a production stage has multiple entry field requirements, multiple stage entry feature codes will be generated for that stage. Subsequently, all stage entry feature codes generated by all production stages are sorted according to the order of their respective stage sequence numbers to form a stage entry feature code sequence.

[0023] Step S117: Compress the phase input feature code sequence to generate the initial form of the feature segment to be input. In the initial form of the feature segment to be input, each phase input feature code occupies a fixed bit length, and the arrangement order between phase input feature codes strictly corresponds to the order of production phases.

[0024] To attach the aforementioned stage-entry feature code sequence to the component itself, it needs to be compressed to reduce data size. A lossless compression algorithm, such as Huffman coding or arithmetic coding, is used to compress the stage-entry feature code sequence. The compressed data is the initial form of the feature segment to be entered. In this initial form, to ensure correct parsing later, the compression algorithm is designed so that each stage-entry feature code still occupies a fixed bit length L_feature after decompression, and the order of these stage-entry feature codes after decompression strictly corresponds to the chronological order of the production stages. Thus, in subsequent production stages, by decompressing this feature segment, it can be divided according to a fixed length to sequentially obtain the entry feature information of each production stage.

[0025] Step S118: Combine the initial form of the component basic identifier segment and the feature segment of the field to be entered according to the preset splicing order to generate the binary original form of the initial production status code. Perform verification calculation on the binary original form of the initial production status code to generate a verification code segment. Append the verification code segment to the end of the binary original form of the initial production status code.

[0026] The component basic identifier segment (a binary string of length K plus L_batch) generated in step S113 is combined with the initial form of the field feature segment to be entered (compressed binary data stream) generated in step S117 according to a preset concatenation order, with the component basic identifier segment first and the field feature segment to be entered last, to generate the initial binary raw form of the production status code. To prevent errors in subsequent data transmission or storage, this binary raw form is checked, for example, using a cyclic redundancy check algorithm. Taking the CRC32 algorithm as an example, the entire binary raw form is used as input to calculate a 32-bit checksum. This 32-bit checksum is used as a checksum segment and appended to the end of the initial binary raw form of the production status code to form a new binary string containing checksum information.

[0027] Step S119: Convert the binary original form of the initial production status code after the additional check code segment into a character representation form to generate an initial production status code text string. Write the initial production status code text string into the storage area of ​​the passive RF memory chip so that the passive RF memory chip carries the initial production status code text string.

[0028] To facilitate attachment and retrieval, the raw binary form with the added checksum is converted into a visual character representation. Base64 encoding can be used, encoding every 3 bytes (24 bits) of binary data into 4 printable ASCII characters. After conversion, an initial production status code text string is generated, consisting of uppercase and lowercase letters, numbers, and specific symbols. Then, using an RF reader / writer, this initial production status code text string is written to a designated storage area of ​​a passive RF memory chip. This chip contains non-volatile memory, which can permanently retain the written data even after power is off.

[0029] Step S1110: The passive radio frequency memory chip carrying the initial production status code text string is fixed to the designated position of the precast concrete component casting mold by pre-embedding. After the concrete is cast and demolded, the passive radio frequency memory chip and the precast concrete component body form an integrated carrying relationship.

[0030] Before the production process begins, the passive RF memory chip, with the initial production status code text string already written into it, is placed in a designated location within the precast concrete component casting mold, such as a pre-reserved groove on the bottom or side of the mold's inner wall. The chip is temporarily fixed inside the mold using fixing clips or magnetic adsorption. Concrete is then poured, filling the mold and encasing the chip. After the concrete solidifies, the chip is demolded. At this point, the passive RF memory chip has become an integral part of the concrete component, firmly embedded within it, forming a unified carrying mechanism. The chip can move with the component through various production stages and can be activated at any stage by an external RF reading device to retrieve the stored initial production status code.

[0031] Step S120: When the precast concrete component enters the current production stage, the current production stage identifier segment and the field feature segment to be entered are parsed from the current production status code carried by the precast concrete component body. The field entry value is collected at the current production stage according to the field propagation path information recorded in the field feature segment to be entered.

[0032] Step S121: The radio frequency reading device deployed at the current production stage transmits an activation carrier signal. When the precast concrete component carrying the passive radio frequency memory chip enters the reading range of the radio frequency reading device, the passive radio frequency memory chip receives the activation carrier signal and obtains working power through electromagnetic induction.

[0033] When the floor slab components are transferred to the rebar tying stage, radio frequency (RF) reading devices are deployed at the workstation entrance or designated reading point at this stage. These devices continuously emit RF activation carrier signals of a specific frequency. When a floor slab component with a pre-embedded passive RF memory chip is transported to the effective reading range of the device via a conveyor belt or overhead crane, the antenna coil inside the chip cuts magnetic field lines, generating an induced current. This induced current is rectified and regulated by the chip's internal power management circuitry, providing the necessary power for the chip's internal digital logic circuits and memory. The chip is then activated and enters its working state without an internal battery.

[0034] Step S122: After the passive RF memory chip is powered on, it reads the current production status code text string stored in its storage area and transmits it back to the RF reading device by modulating the current production status code text string into the reflected carrier signal through backscattering.

[0035] After the chip powers on, its internal controller immediately reads the currently stored data from non-volatile memory, namely the current production status code text string written at the beginning of component production or updated after the previous production stage. The chip encodes this text string data according to the RFID technology protocol, and then modulates the data onto the reflected carrier signal by controlling the matching and mismatch of antenna impedance to change the antenna's reflection cross-section to the incident carrier. This backscattering communication method allows the chip to transmit the stored information back to the RFID reader without emitting RFID signals itself.

[0036] Step S123: The radio frequency reading device demodulates the current production status code text string from the received reflected carrier signal, performs character recognition and format verification on the current production status code text string, and confirms that the character composition of the current production status code text string conforms to the preset character encoding rules.

[0037] After receiving the weak reflected signal, the RF reading device amplifies, mixes, filters, and demodulates it internally to reconstruct the baseband data stream sent by the chip, thus obtaining the current production status code text string. Then, the text string undergoes format verification. First, it checks if all characters belong to the Base64 encoded character set. Second, according to preset encoding rules, it checks if the length of the text string meets expectations, such as whether it is a specific length L_code. If both the character composition and length conform to the rules, the text string is considered valid and can proceed to the next step of parsing. If the verification fails, a reread or alarm process may be triggered.

[0038] Step S124: Segment the current production status code text string according to the preset splicing order, extract the component basic identifier segment text string from the beginning of the current production status code text string, extract the field feature segment text string to be entered from the middle of the current production status code text string, and extract the check code segment text string from the end of the current production status code text string.

[0039] After confirming the validity of the text string, it is segmented according to the concatenation order defined in step S118. Since the text string is the result of Base64 encoding, its fixed-length character sequence at the beginning corresponds to the component basic identifier segment. The character length L_id_str of the component basic identifier segment text string is calculated using the formula: the binary length K before encoding plus L_batch divided by 3 and multiplied by 4. Starting from the beginning of the current production status code text string, a substring of length L_id_str is extracted as the component basic identifier segment text string. Next, from the L_id_str position, the portion extending to the end of the text string minus the length of the check code segment (the binary length of the check code segment is 32 bits, corresponding to a Base64 character length of 32 divided by 3 and multiplied by 4, approximately equal to 43 characters, which needs to be precisely calculated according to the actual encoding rules) is extracted as the feature segment text string to be entered. Finally, the fixed-length character substring at the end of the text string is the check code segment text string.

[0040] Step S125: Decompress the text string of the feature segment to be entered. Divide the decompressed data into multiple binary segments of the feature code for each stage according to the fixed bit length of the feature code for each stage. Each binary segment of the feature code for each stage corresponds to the entry feature information of a production stage.

[0041] After obtaining the text string of the feature segment to be entered, it is first Base64 decoded to restore it to a compressed binary data stream. Then, the decompression algorithm corresponding to the compression algorithm in step S117 is called to decompress the binary data stream and recover the original stage entry feature code sequence binary data. According to the design of step S117, each stage entry feature code occupies a fixed bit length L_feature in the decompressed data. Therefore, starting from the beginning bit of the decompressed data, it is sequentially divided according to the step size of L_feature to obtain a series of binary segments of equal length. Each of the above binary segments corresponds to the entry feature information of a specific field in a specific production stage in the production process, that is, the stage entry feature code.

[0042] Step S126: Traverse each stage input feature code binary segment in the order of stage sequence number identifier, and parse out the stage sequence number identifier, field index code, type constraint code and target node bitmap corresponding to the current stage input feature code binary segment from the currently traversed stage input feature code binary segment.

[0043] For each segmented stage input feature code binary segment, reverse parsing is performed according to the combined encoding format defined in step S116. First, the stage sequence number identifier is parsed from the first fixed number of bits of the binary segment, for example, a binary string of length L_seq, and converted into the corresponding stage number. Next, the field index code is parsed from the next fixed number of bits, for example, a binary string of length L_idx. Then, the type constraint code of length L_type is parsed. Finally, the target node bitmap of length N is parsed from the remaining bits. By traversing all stage input feature code binary segments, a detailed list of all field input requirements in the entire production process can be obtained.

[0044] Step S127: Compare the current stage sequence number identifier corresponding to the current production stage with the stage sequence number identifier in the parsed stage input feature code binary segment, and select the target stage input feature code binary segment whose stage sequence number identifier matches the current stage sequence number identifier from all stage input feature code binary segments.

[0045] During the rebar tying stage, the stage number is identified as S02. S02 is compared one by one with the stage number identifiers parsed from the binary segments of the feature codes for each stage in the previous step. Only those binary segments whose parsed stage number identifiers equal S02 are the fields that need to be entered in the current production stage. Through this filtering process, the target stage entry feature code binary segments corresponding to all fields that need to be entered during the rebar tying stage are accurately identified from a large number of stage entry feature codes.

[0046] Step S128: Extract the field index code, type constraint code and target node bitmap from the selected target stage input feature code binary segment, and store the field index code, type constraint code and target node bitmap as the feature parsing result of the field to be input corresponding to the current production stage in the local cache of the current production stage.

[0047] For each selected target stage input feature code binary segment, repeat the parsing process in step S126, but this time only focus on extracting the field index code, type constraint code, and target node bitmap. Store this information in the memory database or cache of the local computer at the rebar tying stage workstation, either as key-value pairs or a structure (e.g., using the field index code as the key and the combination of the type constraint code and the target node bitmap as the value), or directly as a record containing these three elements. This forms the corresponding field feature parsing result for the current production stage, guiding which data needs to be collected, its format, and its future destination.

[0048] Step S129: Read the feature parsing result of the field to be entered from the local cache of the current production stage. The feature parsing result of the field to be entered contains the field index code, the type constraint code and the target node bitmap. The field index code is used to identify the name of the field to be entered, the type constraint code is used to constrain the data type of the field entered value, and the target node bitmap is used to indicate the subsequent production stage to which the field entered value needs to be propagated.

[0049] On the operation interface of the rebar tying station, the system reads the feature parsing results of the fields to be entered generated in the above steps from the local cache. It contains multiple records, each of which clearly indicates a field that must be entered in this stage. For example, the field index code of one record is 0001, which corresponds to "tying operator ID"; the type constraint code is 01, representing a string type; the target node bitmap is a 7-bit binary string, such as 0010010, indicating that this field needs to be propagated to the 5th stage (quality inspection) and the 7th stage (finished product delivery).

[0050] Step S1210: Based on the field index code, find the corresponding field name text from the preset field name mapping table; based on the type constraint code, find the corresponding data type description text from the preset data type mapping table; combine the field name text and the data type description text to generate the input field prompt information for the current production stage.

[0051] To guide on-site operators in data entry, machine-readable encoding needs to be converted into human-readable prompts. Based on the field index code 0001 read from the cache, a reverse lookup of the global field name mapping table used in step S115 is performed to obtain the corresponding field name text "Binding Operator ID". Based on the type constraint code 01, a reverse lookup of the data type mapping table is performed to obtain the corresponding data type description text "String". Then, these two texts are combined, for example, to generate the prompt message "Please enter Binding Operator ID (String)" to guide input on the user interface.

[0052] Step S1211: Render an input control on the human-computer interaction interface of the current production stage. The label area of ​​the input control displays input field prompt information. The input area of ​​the input control is configured as the corresponding input component according to the data type description text. The confirmation button of the input control is associated with a field value submission trigger event.

[0053] On the touchscreen computer at the rebar tying station, an input control is dynamically generated based on the aforementioned prompts. The control's label area displays "Tying Operator ID". The input area, being a string, is rendered as a TextBox. If the type constraint code is 03 (corresponding to a boolean value), the input area may be rendered as a CheckBox or RadioButton. Each input control also includes a Confirm Button; the button's click event is pre-associated with a callback function to trigger subsequent field value submission processing logic when the button is clicked.

[0054] Step S1212: The operator enters the original value through the input field of the input control. The input area of ​​the input control receives the operator's input in real time and temporarily stores the input original value in the memory cache associated with the input control.

[0055] After seeing the on-screen prompts, operators enter their employee ID, such as "ZHANG_SAN," into the text input box using the on-screen keyboard or an external keyboard. The input area captures keyboard events in real time and stores the entered characters "Z," "H," "A," "N," "G," "_," "S," "A," and "N" sequentially into a temporary memory buffer associated with the input control. This buffer is continuously updated during the input process, preserving the current input content.

[0056] Step S1213: When the operator triggers the confirmation button of the input control, the original input value is read from the memory buffer associated with the input control, and the original input value is matched and verified with the type constraint code to check whether the data format of the original input value conforms to the data type requirements specified by the type constraint code.

[0057] After the operator finishes inputting the data, they click the confirmation button on the input control. The button click event is triggered, and the system immediately reads the stored raw input value "ZHANG_SAN" from the memory buffer associated with the control. Next, this value is matched against the type constraint code 01 (string) obtained in step S1210. The verification logic checks whether the input value contains non-string characters. For string types, generally any keyboard-enterable character is considered valid, but length limits or whether it is empty may be checked. If the type constraint code is 02 (timestamp), it checks whether the input string can be successfully parsed into a preset time format.

[0058] Step S1214: After the input raw value passes the data type matching verification, the input raw value is used as the field entry value of the current production stage. The field entry value is associated with the field index code, the current production stage identifier and the target node bitmap to generate the field entry record to be processed in the current production stage.

[0059] The input value “ZHANG_SAN” passed string type validation. The system uses this value as the field entry value for this entry. Then, it retrieves the stage number identifier S02 from the current production stage (rebar tying stage) and reads the target node bitmap 0010010 associated with the field index code 0001 from step S129. These four pieces of information—field index code 0001, field entry value “ZHANG_SAN”, current production stage identifier S02, and target node bitmap 0010010—are associated and packaged to generate a structured field entry record to be processed. For example, they can be combined into a JSON object or serialized into a binary structure, ready for the next step of processing.

[0060] Step S1215: Store the field entry record to be processed in the memory database of the current production stage, and display a prompt message on the human-computer interaction interface that the field entry value has been successfully collected. At the same time, reset the entry control to the initial state that can accept the next input.

[0061] The record for the field to be processed is stored in a local in-memory database (such as a Redis or SQLite in-memory table) at the rebar tying workstation, and the record status is marked as "collected and awaiting processing". Simultaneously, a brief notification pops up on the human-machine interface, displaying "Tying Operator ID successfully collected". Then, the system clears the input area of ​​the previously used input control, resetting it to a blank state, waiting for the operator to input the value of the next field, such as "tying completion time". Steps S129 to S1215 are executed repeatedly until all fields requiring input in the current production stage (i.e., all fields corresponding to the selected target stage input feature code binary segments) have been collected and stored as pending field input records.

[0062] Step S130: Compress and convert the collected field input values ​​according to the field aggregation method recorded in the feature segment of the field to be input, and generate the current field propagation unit. The current field propagation unit embeds the current production stage identifier, the compressed representation of the field input value, and the target node identifier set of the field in the subsequent production stage.

[0063] Step S131: Read the field entry record to be processed from the memory database of the current production stage. The field entry record to be processed contains the field index code, field entry value, current production stage identifier and target node bitmap. The target node bitmap is a fixed-length binary bit string, and each binary bit corresponds to a subsequent production stage.

[0064] After all field values ​​entered during the rebar tying stage have been collected and stored, the conversion process begins for each field entry record to be processed. A record is read from the memory database, for example, the previously stored record corresponding to field index code 0001. This record explicitly contains: field index code 0001, field entry value "ZHANG_SAN", current production stage identifier S02, and target node bitmap 0010010. The target node bitmap 0010010 is a 7-bit binary string, where the 3rd and 5th bits (corresponding to S05) are 1, indicating that the field entry value needs to be passed to the 3rd and 5th production stages.

[0065] Step S132: Query the aggregation method code associated with the field index code from the preset field aggregation rule base according to the field index code. The aggregation method code is used to indicate the compression encoding algorithm and aggregation operation rules of the field input value during the propagation process.

[0066] Based on the read field index code 0001, a pre-configured field aggregation rule base is queried. This rule base defines how each field should be compressed when generating propagation units. For example, for field index code 0001 (operator ID), its corresponding aggregation method code might be A01, indicating the use of a fixed-length string compression algorithm to convert the variable-length string "ZHANG_SAN" into a fixed-length binary code, with a compression ratio of 1:4, meaning one character is compressed into 4 bits of binary. For field index code 0002 (timestamp), its aggregation method code might be A02, indicating the use of a timestamp compression algorithm to convert the standard time format into a binary representation of minutes or seconds starting from a certain epoch. The aggregation method code may also include aggregation operation rules; for example, for some numeric fields, it might indicate that when propagating to subsequent stages, it needs to be accumulated or averaged with other values ​​in the same stage. However, in this step, the main focus is on the selection of the compression encoding algorithm.

[0067] Step S133: Call the compression encoding algorithm corresponding to the aggregation method encoding to compress the field input value, and convert the field input value into a fixed-length field input value compression code. The length of the field input value compression code is determined by the compression ratio specified in the aggregation method encoding.

[0068] Based on the aggregate method code A01 found in the query, the corresponding string compression algorithm is invoked. First, each character in the field input value "ZHANG_SAN" is converted into an 8-bit binary number according to the ASCII code table, resulting in a binary string of length 8 times the number of characters. Then, according to the compression ratio of 1:4 specified in A01, the goal is to compress each character to 4 bits. However, the specific implementation of the compression ratio may be more complex. For example, the algorithm might have a built-in dictionary of common operator IDs, mapping "ZHANG_SAN" to a 10-bit index value in the dictionary, thus compressing it into a 10-bit field input value compression code L_value_code. Regardless of the original string length, after compression, all operator ID fields will generate a fixed-length (e.g., 10-bit) compressed code. For the timestamp of field index code 0002, algorithm A02 is called to convert it into the number of minutes that have elapsed from 00:00 on January 1, 2000 to the current time. This number of minutes is represented by a 20-bit binary number, thereby generating a fixed-length 20-bit field entry value compression code.

[0069] Step S134: Convert the current production stage identifier into a fixed-length stage identifier compression code, convert the field index code into a fixed-length field index compression code, and use the target node bitmap directly as a fixed-length propagation target bitmap.

[0070] The current production stage identifier S02 is a stage sequence number, and its binary representation can be predefined. For example, S02 can be mapped to an 8-bit stage identifier compression code 00000010. The field index code 0001 is already a fixed-length (e.g., 12-bit) binary string and can be directly used as the field index compression code. The target node bitmap 0010010, whose length is equal to the total number of production stages N (7 in this example), is already a fixed length and can be directly used as the propagation target bitmap.

[0071] Step S135: Concatenate the stage identifier compression code, field index compression code, field input value compression code, and propagation target bitmap according to the preset internal order of the propagation unit to generate the binary original form of the current field propagation unit. The length of the binary original form of the current field propagation unit is equal to the sum of the lengths of its components.

[0072] Following a preset internal order, such as stage identifier compression code first, followed by field index compression code, then field input value compression code, and finally propagation target bitmap, the four binary strings generated in steps S133 and S134 are concatenated. Assuming the stage identifier compression code is 8 bits long, the field index compression code is 12 bits long, the field input value compression code is 10 bits long, and the propagation target bitmap is 7 bits long, the total length of the original binary form of the current field propagation unit after concatenation is 8 + 12 + 10 + 7, equal to 37 bits. This binary string contains all the information about the stage that generated the unit, the corresponding field, the compressed representation of the field value, and the subsequent propagation path.

[0073] Step S136: Perform redundant encoding on the original binary form of the current field propagation unit to generate a binary string of the current field propagation unit carrying error correction code. Convert the binary string of the current field propagation unit carrying error correction code into a character representation to generate a text string of the current field propagation unit.

[0074] To improve the data's resistance to physical environmental interference (such as radio frequency signal interference and chip memory cell bit flipping) during component transfer, the aforementioned 37-bit binary raw form is redundantly encoded, for example, using Hamming code or Reed-Solomon code. Taking Hamming code as an example, three parity bits can be inserted after every four data bits, or a global checksum can be calculated based on the overall length and appended to the end. After redundant encoding, a longer binary string carrying error correction codes is generated (e.g., 37 data bits plus several parity bits, with a total length of L_red). Then, similar to step S119, this binary string is Base64 encoded and converted into a current field propagation unit text string composed of printable characters.

[0075] Step S137: Store the generated current field propagation unit text string in the memory database of the current production stage, and associate the current field propagation unit text string with the field entry record to be processed, marking that the field entry record to be processed has been converted into a propagation unit state.

[0076] The text string of the current field propagation unit generated in step S136 is stored back into the memory database of the rebar tying stage, and associated with the original field entry record to be processed. For example, a new field is added to the record to store the pointer to the text string, or it is stored directly. At the same time, the status flag of the record is updated from "collected and pending processing" to "converted into a propagation unit". In this way, each piece of raw data entered corresponds to a standardized unit that can be independently propagated in the production network.

[0077] Step S140: Combine and reconstruct the current field propagation unit with other field propagation units parsed from the current production status code to generate an updated field propagation unit set containing the historical field propagation unit sequence and the current field propagation unit, and generate a new field feature segment to be entered based on the updated field propagation unit set.

[0078] Step S141: Read the current field propagation unit text string from the memory database of the current production stage, and at the same time read the text string of the feature segment of the field to be entered, which was previously parsed from the current production status code, from the local cache of the current production stage.

[0079] During the rebar binding stage, after generating corresponding current field propagation unit text strings for all fields that need to be entered, the combination and reconstruction begins. First, all newly generated current field propagation unit text strings with the status "converted to propagation unit" are read from the memory database. At the same time, the text strings of the feature segments of the fields to be entered (i.e., compressed and encoded historical data) obtained by decompressing the production status codes carried by the components are read from the parsing results stored in the local cache in step S124.

[0080] Step S142: Decompress the text string of the feature segment to be entered, and extract the binary segments of the feature codes of other stages except for the binary segments of the target stage entry feature codes corresponding to the current production stage from the decompressed data.

[0081] The text string of the feature segment to be entered read in step S141 is Base64 decoded, and then a decompression algorithm is called to recover the original stage entry feature code sequence. Since this stage entry feature code sequence contains the encoded information of all the entered fields from the start of production to the previous production stage, according to step S127, the target stage entry feature code binary segment of the current stage (S02) has been filtered out. Now, these binary segments corresponding to the current stage need to be removed from the entire sequence, or more accurately, they no longer need to be used as "templates" for the fields to be entered, because the current stage has completed the entry and generated the propagation unit. The remaining other stage entry feature code binary segments represent the field templates that need to be entered in the future for those production stages that have not yet been executed (such as S03, S04...), as well as historical information that may be generated by earlier stages, has been entered and converted into propagation units (this information may be embedded in the feature code in some form, or stored separately, depending on the design; here it is assumed that the historical propagation units are stored independently, while the feature segments mainly store template information). In a preferred embodiment of this method, the feature segment of the field to be entered not only contains the entry template for the future stage, but also includes the historical propagation unit in compressed form. Therefore, the data obtained after decompression is a composite structure, which requires further separation of the historical propagation unit and the template for the future stage.

[0082] Step S143: Traverse the binary segment of the feature code entered in each other stage, and parse out the historical field propagation unit sequence corresponding to that stage from the binary segment of the feature code entered in each other stage. The historical field propagation unit sequence is composed of multiple field propagation unit text strings generated in an earlier production stage of that stage arranged in the order of generation time.

[0083] For each historical field propagation unit in the decompressed data (which may be encoded within a specific area), it is identified by parsing its internal stage identifier compression code, field index compression code, and other information. Furthermore, these historical field propagation units are arranged according to the order in which they were generated in the production stage, and the chronological order of their generation within each stage. For example, parsing two propagation units generated in the mold assembly stage (S01) from the decompressed data: one corresponding to the "Mold Number" field and the other to the "Assembly Operator ID" field, these propagation units constitute the historical field propagation unit sequence for stage S01.

[0084] Step S144: Arrange all the parsed historical field propagation unit sequences in the order of their corresponding stage number identifiers to generate a total historical field propagation unit sequence. Each element in the total historical field propagation unit sequence is a field propagation unit text string.

[0085] All historical field propagation units parsed from step S143, such as the sequence of stage S01 and any other possible earlier stages, are sorted in ascending order of stage number identifiers S01, S02, etc., and merged into a large, ordered total sequence of historical field propagation units. This sequence records all field information entered for the component from the start of production to the end of the previous production stage. Each element is a field propagation unit text string that has been compressed and redundantly encoded.

[0086] Step S145: Append the current field propagation unit text string to the end of the historical field propagation unit sequence to form an updated field propagation unit sequence that includes the historical field propagation unit sequence and the current field propagation unit text string.

[0087] All current field propagation unit text strings generated during the rebar tying stage (S02) are appended sequentially to the end of the aforementioned historical field propagation unit sequence, according to their generation order. This creates an updated total sequence of field propagation units that contains all historical information up to the current production stage.

[0088] Step S146: Compress the updated field propagation unit sequence by converting all field propagation unit text strings in the updated field propagation unit sequence into a continuous binary data stream, and generating an updated field propagation unit compressed package.

[0089] First, all text strings in the updated field propagation unit sequence are Base64 decoded to restore the binary string carrying the error correction code corresponding to each propagation unit. Then, these binary strings are concatenated end-to-end to form a long binary data stream. Finally, a lossless compression algorithm (such as the DEFLATE algorithm) is applied to this data stream to remove statistical redundancy between data, generating a smaller compressed package of updated field propagation units.

[0090] Step S147: Use the updated field propagation unit compressed package as the new field feature segment to be entered. The new field feature segment to be entered implicitly contains all the field propagation units generated in the production stages, and the order of the field propagation units strictly corresponds to the order of the production stages.

[0091] The updated field propagation unit compressed package generated in step S146 is used as the new feature segment for the fields to be entered. This new feature segment no longer contains the "entry template" for future stages, but instead contains all the historically entered data that has already occurred, compressed and encoded. This data exists in the form of field propagation units, and their arrangement strictly corresponds to the time sequence of the production stages. The "entry template" information for future stages is actually implicitly contained in the "propagation target bitmap" carried by these historical propagation units. By parsing the propagation target bitmap of each historical propagation unit, it can be determined which fields need to be activated or used in which future stage.

[0092] Step S148: Generate new feature segments of fields to be entered based on the updated set of field propagation units.

[0093] Step S1481: Parse the updated field propagation unit compressed package to obtain the text string of each field propagation unit contained in the updated field propagation unit compressed package. Each field propagation unit text string contains a stage identifier compression code, a field index compression code, a field input value compression code, and a propagation target bitmap.

[0094] After generating the updated field propagation unit compressed package during the rebar tying stage, in order to generate new field feature segments to be entered in future production stages, the compressed package needs to be deeply parsed. The compressed package is decompressed to obtain a continuous binary data stream, which is then segmented according to the fixed length determined during the generation of each field propagation unit, resulting in a series of independent field propagation unit binary strings. Error correction decoding is performed on each binary string to restore the original binary form of the field propagation unit. Starting from the beginning of each original binary form, the stage identifier compressed code, field index compressed code, field entry value compressed code, and propagation target bitmap are parsed sequentially according to the internal order defined in step S135. For example, a field propagation unit is parsed with a stage identifier compressed code of 00000010, indicating that the unit was generated during the rebar tying stage; a field index compressed code of 0001, indicating the corresponding tying operator ID field; a field entry value compressed code of a 10-bit binary string; and a propagation target bitmap of 0010010, indicating that the field needs to be propagated to the quality inspection stage and the finished product delivery stage. By traversing the entire compressed file, the above information for all historical and current field propagation units can be obtained.

[0095] Step S1482: Traverse each field propagation unit text string, extract the propagation target bitmap from the currently traversed field propagation unit text string, and perform matching analysis between the extracted propagation target bitmap and the stage sequence identifiers corresponding to all subsequent production stages after the current production stage.

[0096] The current production stage is designated as the rebar tying stage, with stage number S02. From each field propagation unit parsed in step S1481, its propagation target bitmap is extracted. This bitmap is a binary string of length N (total number of stages). The extracted bitmap is matched with the stage numbers of all stages after S02, namely S03, S04, S05, S06, and S07. The purpose of the matching analysis is to determine whether the current field propagation unit needs to be used or activated in each subsequent production stage. For example, for field propagation unit A, its propagation target bitmap is 0010010. Through analysis, the 3rd bit (corresponding to S03) is 0, the 4th bit (S04) is 0, the 5th bit (S05) is 1, the 6th bit (S06) is 0, and the 7th bit (S07) is 1. Analysis results show that the field propagation unit needs to be activated in stages S05 and S07, but not in stages S03, S04, and S06.

[0097] Step S1483: Based on the matching analysis results, determine whether each field propagation unit text string needs to be activated in each subsequent production stage, and generate an activation state vector corresponding to each field propagation unit text string. The activation state vector is a binary bit string with a length equal to the number of subsequent production stages.

[0098] Based on the matching analysis in step S1482, an activation state vector is generated for each field propagation unit. The length of this vector is equal to the number of subsequent production stages, i.e., five stages from S03 to S07. For field propagation unit A, since it needs to be activated in S05 and S07, its corresponding activation state vector can be represented as the binary string 00101, where the five bits from left to right correspond to S03, S04, S05, S06, and S07, respectively. In this vector, the bit corresponding to S05 (the 3rd bit) is 1, the bit corresponding to S07 (the 5th bit) is 1, and the remaining bits are 0.

[0099] Step S1484: Perform a bitwise OR operation on the activation state vectors of all field propagation unit text strings to generate a comprehensive activation state vector. Each binary bit in the comprehensive activation state vector indicates whether at least one field propagation unit needs to be activated in the corresponding subsequent production stage.

[0100] Perform a bitwise logical OR operation on the activation state vectors generated for all field propagation units in step S1483. For example, suppose the activation state vector of field propagation unit A is 00101, that of field propagation unit B is 10000, and that of field propagation unit C is 01000. Perform a bitwise OR operation on these three vectors: the first bit (corresponding to S03) is 1 (0 OR 1 OR 0), the second bit (corresponding to S04) is 1 (0 OR 0 OR 1), the third bit (corresponding to S05) is 1 (1 OR 0 OR 0), the fourth bit (corresponding to S06) is 0 (0 OR 0 OR 0), and the fifth bit (corresponding to S07) is 1 (1 OR 0 OR 0). Therefore, the resulting comprehensive activation state vector is 11101. Each bit of this comprehensive activation state vector is 1, indicating that at least one field propagation unit needs to be activated in the corresponding subsequent production stage. The length of the vector is 5, comprehensively reflecting the data requirements of all future stages.

[0101] Step S1485: Based on the subsequent production stage corresponding to the binary bit with the value of the first state in the comprehensive activation state vector, retrieve the stage entry feature code template corresponding to the subsequent production stage from the preset stage entry feature code template library.

[0102] The activation state vector 11101 indicates that fields need to be activated in all four stages: S03, S04, S05, and S07. Therefore, the corresponding stage entry feature code templates for stages S03, S04, S05, and S07 are retrieved from the pre-defined stage entry feature code template library. These templates are predefined and contain empty slots for fields that may be entered in each stage. For example, the template for the S05 quality inspection stage may have reserved index code slots and type constraint code slots for fields such as "Inspector ID," "Inspection Result," and "Inspection Time," but these slots are not yet filled with information about which historical field propagation unit they belong to.

[0103] Step S1486: Fill the text string of each field propagation unit into the specified position in the retrieved corresponding stage entry feature code template according to the subsequent production stage indicated by the binary bit with the value of the first state in its corresponding activation state vector, and generate the updated stage entry feature code corresponding to each subsequent production stage.

[0104] Returning to each field propagation unit. For field propagation unit A, its activation state vector 00101 indicates that it needs to be filled into templates S05 and S07. Therefore, the key identification information of field propagation unit A, such as the field index compression code and type constraint code (which can be traced from historical data), is filled into a reserved field position in template S05, and similarly into a reserved field position in template S07. For field propagation unit B, its activation state vector 10000 indicates that it needs to be filled into template S03. For field propagation unit C, its activation state vector 01000 indicates that it needs to be filled into template S04. After filling, the originally blank template S03 becomes the S03 post-update stage entry feature code containing the identification information of field propagation unit B; template S04 becomes the S04 post-update stage entry feature code containing the identification information of field propagation unit C; and templates S05 and S07 become the post-update stage entry feature codes containing the identification information of field propagation unit A.

[0105] Step S1487: Arrange all updated stage input feature codes according to the sequence number of the subsequent production stage to generate an updated stage input feature code sequence. Compress the updated stage input feature code sequence to generate a new field feature segment to be entered.

[0106] The updated stage entry feature codes generated in step S1486, corresponding to S03, S04, S05, and S07, are arranged in the order of stage numbers S03, S04, S05, and S07 to form an updated stage entry feature code sequence. Since the corresponding bit in the integrated activation state vector for S06 is 0, it indicates that no field needs to be activated in S06, so no feature code needs to be generated for it. Finally, the sequence is compressed and encoded to generate a binary data stream, which serves as the new field feature segment to be entered. After this field feature segment is written into the component status code, when the component enters stage S03, it can immediately know through parsing that it needs to retrieve the information of field propagation unit B from the historical data carried by the component itself; when entering stage S04, it knows that it needs to retrieve the information of field propagation unit C; and when entering stages S05 and S07, it knows that it needs to retrieve the information of field propagation unit A.

[0107] Step S150: Recombine the new field feature segment to be entered with the component base identification segment of the precast concrete component to generate an updated production status code, and reattach the updated production status code to the precast concrete component body.

[0108] Step S151: Read the component foundation identification segment text string of the precast concrete component from the local cache of the current production stage. The component foundation identification segment text string is a fixed part that is parsed from the current production status code and remains unchanged throughout the production process.

[0109] Read the component basic identifier segment text string segmented in step S124 from the local cache during the rebar binding stage. It contains the component design feature code and production batch information code, which is the unique identifier of the component and remains unchanged throughout the entire production life cycle.

[0110] Step S152: Combine the newly generated feature segment of the field to be entered with the text string of the component basic identifier segment according to the preset concatenation order to generate the intermediate binary form of the updated production status code. The first part of the intermediate binary form of the updated production status code is the binary string corresponding to the text string of the component basic identifier segment, and the second part is the binary string corresponding to the feature segment of the new field to be entered.

[0111] The new field feature segment to be entered (i.e., the updated field propagation unit compressed package) generated in step S147 is treated as binary data. At the same time, the component basic identifier segment text string is Base64 decoded to restore its original binary form (length K plus L_batch). According to the preset concatenation order, the binary form of the component basic identifier segment is placed at the beginning, and the binary data of the new field feature segment to be entered (compressed package) is placed at the end. The two are concatenated together to generate the intermediate binary form of the updated production status code.

[0112] Step S153: Perform length verification on the intermediate binary form of the updated production status code, calculate whether the actual bit length of the intermediate binary form is equal to the preset standard production status code bit length, and when the actual bit length is less than the standard length, fill the end of the intermediate binary form with zero bits until the standard length is reached.

[0113] Production status codes are typically designed with a fixed total length for ease of storage and management. Calculate the actual bit length L_actual of the intermediate binary form described above. Compare this to the preset standard production status code bit length L_standard. Since the new field feature segment to be entered is compressed data, its length may vary, causing L_actual to potentially not equal to L_standard. If L_actual is less than L_standard, padded with consecutive binary 0s at the end of the intermediate binary form until the total length reaches L_standard. If L_actual is greater than L_standard, an error handling mechanism may be triggered because the compressed data exceeds the designed maximum capacity, which may require adjusting the compression algorithm or redesigning the status code structure.

[0114] Step S154: Perform verification calculation on the updated production status code binary string after length verification, generate a new verification code segment, and append the new verification code segment to the end of the updated production status code binary string after length verification to form a complete updated production status code binary string.

[0115] The binary string of length L_standard, after length verification and possible padding in step S153, is calculated again using a checksum algorithm such as CRC32 to generate a new 32-bit checksum segment. This new checksum segment is appended to the end of the binary string to form an updated production status code binary string of length L_standard plus 32 bits.

[0116] Step S155: Convert the complete updated production status code binary string into hexadecimal character representation in groups of four, and generate the updated production status code text string. The character length of the updated production status code text string is equal to the quotient of the binary string length divided by four plus the character length of the check segment after conversion.

[0117] The complete updated production status code binary string is encoded in hexadecimal. The binary string is divided into groups of 4 bits, and each group is converted into a hexadecimal character (0-9, AF). The length of the binary string is then divided by 4 to obtain the character length of the hexadecimal text string. For example, a binary string of L_standard plus 32 bits will be converted into a hexadecimal text string of (L_standard plus 32) divided by 4 characters. This representation is simpler than Base64, but has slightly lower information density. However, it is easier to store and retrieve on resource-constrained RF chips, ultimately generating an updated production status code text string consisting only of hexadecimal characters.

[0118] Step S156: The updated production status code text string is transmitted to the passive radio frequency storage chip carried by the precast concrete component body through the radio frequency writing device via the radio frequency writing signal. After receiving the radio frequency writing signal, the passive radio frequency storage chip writes the updated production status code text string into its storage area, overwriting the original current production status code text string.

[0119] At the exit of the rebar tying stage workstation, an RF writing device is deployed. When a floor slab component with an embedded chip moves to the range of this device, the RF writing device emits an RF signal containing a write command and an updated production status code text string. The passive RF memory chip receives power through electromagnetic induction and wakes up to receive the signal. The controller inside the chip parses the write command and writes the received new hexadecimal text string to a designated address area in the non-volatile memory. This write operation overwrites the previously stored "current production status code text string" read at the entry point of this stage. At this point, the information carried by the component has been updated, containing all production data up to the rebar tying stage. The component, carrying the updated status code, continues to move to the next production stage (e.g., the embedded part installation stage), where steps S120 to S150 are repeated.

[0120] Step S210: After the precast concrete component has completed all the preset production stages, obtain the final production status code text string carried by the precast concrete component body from the final production stage. The final production status code text string contains the component basic identification segment and the final field feature segment to be entered.

[0121] Once the floor slab component has completed the quality inspection phase, i.e., after all preset production stages are finished, before the finished product is put into storage or shipped, the final production status code text string stored in the component's internal chip is read again at the reading device deployed at the final inspection station. The reading process is the same as steps S121 to S124, ultimately obtaining a text string containing the component's basic identifier segment and the final field feature segment to be entered. This final field feature segment to be entered is a compressed package containing all historical production data, continuously updated through all production stages.

[0122] Step S220: Decompress the feature segments of the final fields to be entered, and extract the field propagation unit text strings corresponding to all historical production stages from the decompressed data. Each field propagation unit text string corresponds to a field value entered in a production stage.

[0123] The text string of the final field feature segment to be entered is decoded in hexadecimal to restore it to a binary data stream. Then, it is decompressed to recover the original binary form of the updated total sequence of field propagation units. Next, this binary stream is divided into a series of independent binary strings of field propagation units carrying error correction codes, according to the fixed length determined when each field propagation unit is generated (e.g., the length after adding the 37 bits in step S135 to the redundant encoding). Each of these binary strings corresponds to a specific field value entered in a certain production stage. Subsequently, each binary string is subjected to error correction decoding (using the redundant check bits added in step S136 to correct any possible minor bit errors) to restore the correct original binary form of the field propagation unit.

[0124] Step S230: Group all extracted field propagation unit text strings according to the stage identifier compression code embedded in each field propagation unit text string, and divide the field propagation unit text strings belonging to the same production stage into the same group to generate a set of field propagation unit groups grouped by production stage.

[0125] From the binary raw form of each error-corrected and decoded field propagation unit, the stage identifier compression code is parsed out at a fixed position at the beginning according to the format defined in step S135. For example, 00000001 corresponds to S01, and 00000010 corresponds to S02. Based on these compression codes, all field propagation units are grouped. All units with a stage identifier compression code of 00000001 are assigned to the mold assembly stage group, all units with a compression code of 00000010 are assigned to the rebar binding stage group, and so on, forming a set of field propagation unit groups grouped by production stage.

[0126] Step S240: The text strings of the field propagation units in each set of field propagation units are grouped a second time according to the compression code of the field index they are embedded in, and the text strings of the field propagation units belonging to the same field index are divided into the same subgroup, generating a set of field propagation unit subgroups grouped by field index.

[0127] For each of the aforementioned production stage groups, such as the rebar tying stage group, the internal field index compression codes of all field propagation units within that group are further parsed. For example, 0001, 0002, etc., are parsed out. Based on these field index compression codes, the units within that stage group are further subdivided. All units with a field index compression code of 0001 are assigned to the "Tying Operator ID" subgroup, and all units with a code of 0002 are assigned to the "Tying Completion Time" subgroup, thus forming a refined set of field propagation unit subgroups grouped by field index.

[0128] Step S250: Sort the field propagation unit text strings in each field propagation unit subgroup set according to their generation time, and select the last field propagation unit text string from the sorted sequence as the final valid field propagation unit corresponding to the field index.

[0129] Due to potential data corrections, duplicate entries, or multiple measurements during the production process, the same field may have multiple records in the same production stage. For example, during the rebar tying stage, the "tying quality self-inspection result" may be entered multiple times. By implicitly including time information within each propagation unit or through its position in the overall sequence when generating each propagation unit (e.g., appending the current unit to the end in step S145 implies a temporal order), propagation units within each field subgroup are sorted according to their order of appearance in the overall sequence (i.e., chronological order). Then, the last (i.e., the most recently generated) propagation unit in this ordered sequence is selected as the final valid field propagation unit for that field in this production stage. This ensures that the data used is the most up-to-date.

[0130] Step S260: Decode each final valid field propagation unit, extract the field entry value compression code from the final valid field propagation unit, and call the decompression algorithm associated with the field index compression code to decompress and restore the field entry value compression code to obtain the original field entry value.

[0131] For each final valid field propagation unit selected in step S250, the field index compression code and field input value compression code are parsed from its binary original form. Based on the field index compression code, the field aggregation rule base is queried (same as in step S132) to find its corresponding aggregation method encoding, thereby determining the corresponding decompression algorithm. This decompression algorithm is then called to perform a reverse operation on the field input value compression code. For example, for field index code 0001, the decompression algorithm restores the 10-bit compression code back to the original string "ZHANG_SAN". For field index code 0002, the decompression algorithm restores the 20-bit compression code back to a standard format timestamp.

[0132] Step S270: Organize all the restored original field input values ​​into a structured manner according to their corresponding production stage sequence number and field index code to generate a complete production information archive for precast concrete components. Each production stage in the complete production information archive corresponds to a data subset, and each data subset contains all field names and field input values ​​entered in that stage.

[0133] All the original field values ​​restored in step S260, along with the stage identifiers and field indexes parsed in steps S230 and S240, are structured. A JSON or XML file can be generated, with its top-level structure organized by production stage (S01, S02...). Under each stage, there is a collection of multiple key-value pairs, where the key is the field name text corresponding to the field index code (by querying the field name mapping table again), and the value is the restored original field value. Ultimately, a complete, traceable, analyzable, and archived precast concrete component production information archive is generated, accurately recording all process data of the component from the start to the end of production.

[0134] For example, the method may further include: step S310: after the precast concrete component enters the current production stage and generates the current field propagation unit, the text string of the current field propagation unit is broadcast to multiple storage nodes in the distributed storage system through the network interface at the current production stage.

[0135] After the current field propagation unit text string is generated and stored during the rebar binding stage, in order to enhance data reliability and achieve cross-stage data sharing, the local computing device at the workstation sends the text string to the distributed storage system cluster connected to the factory's industrial network via a network interface (such as Ethernet) in the form of broadcast or multicast. The distributed storage system consists of multiple storage node servers, which jointly manage the production data of all components.

[0136] Step S320: After receiving the current field propagation unit text string, each storage node in the distributed storage system determines whether it needs to store the current field propagation unit text string for a long time based on the propagation target bitmap in the current field propagation unit text string.

[0137] Upon receiving the broadcast text string of the current field propagation unit, each storage node first parses it to extract the internal propagation target bitmap. Each storage node is configured at startup to be responsible for data storage of one or more specific production stages. For example, node A is configured to be responsible for data in the quality inspection stage (S05) and the finished product delivery stage (S07). After receiving the text string, node A parses its propagation target bitmap and finds that the bits corresponding to S05 and S07 are 1, indicating that the field propagation unit needs to be activated and used in stages S05 and S07. Therefore, node A is responsible for storing this data long-term. If node B is responsible for the maintenance stage (S06), and the S06 bit in the bitmap is 0, then node B can ignore the data or only temporarily cache it before discarding it.

[0138] Step S330: For the current field propagation unit text string in the production stage corresponding to the storage node in the propagation target bitmap, where the bit is in the first state, the storage node stores it in the local persistent database and establishes a query mapping table indexed by the component basic identifier segment.

[0139] For data that needs to be stored as indicated by the propagation target bitmap, the storage node writes the propagation unit text string of this field to its local high-reliability persistent database, such as a relational database or key-value store. Simultaneously, to facilitate rapid subsequent retrieval, the storage node extracts the component basic identifier segment from the complete production status code associated with this text string (this identifier segment may be broadcast along with the propagation unit, or the storage node may obtain it through other means), and updates a global query mapping table using the component basic identifier segment as the index key and the storage location of the propagation unit text string of this field as the value. In this way, all relevant data distributed across different nodes can be quickly found using the component ID.

[0140] Step S340: When a subsequent production stage needs to query the historical field propagation unit, the device in the subsequent production stage sends a query request to the distributed storage system with the component basic identifier segment as the query condition. The distributed storage system locates the storage node of the relevant field propagation unit according to the query mapping table.

[0141] When a floor slab component is transferred to the quality inspection stage (S05), the local equipment at this stage needs to acquire all historical data related to that component, especially those fields where the S05 bit is 1 in the propagation target bitmap, such as the "binding operator ID" in the rebar binding stage. The equipment parses the component's basic identification segment from the status code carried by the current component and then initiates a query request to the distributed storage system via the network, including this identification segment. Upon receiving the request, the coordination node of the distributed storage system queries the query mapping table maintained in step S330 to find a list of storage nodes that store field propagation units related to the component's basic identification segment and whose propagation target bitmap points to S05.

[0142] Step S350: The located storage node reads all field propagation unit text strings associated with the component basic identifier segment from the local persistent database, packages all the read field propagation unit text strings, and returns them to the device at the subsequent production stage that initiated the query request.

[0143] Each storage node located by the coordinated node (e.g., node A) performs a retrieval in its local persistent database based on the component basic identifier segment in the query request, reading all field propagation unit text strings associated with that identifier segment. Then, each node packages the data it reads into a data packet and returns it over the network to the quality inspection stage device that initiated the query request.

[0144] Step S360: After receiving the returned set of field propagation unit text strings, the device that initiated the query request sorts the elements in the set according to the stage identifier compression code in the field propagation unit text strings, and generates a historical field propagation unit sequence for subsequent reconstruction of the feature segments of the fields to be entered.

[0145] During the quality inspection phase, the equipment receives and merges data packets returned from multiple storage nodes to obtain a set of text strings containing all relevant historical field propagation units for the current component. Then, the equipment parses each text string in the set, extracting its internal stage identifier compression code. Based on these compression codes, all text strings are sorted according to the production stage order (S01, S02...), ultimately generating an ordered sequence of historical field propagation units. This sequence is directly used in step S140 and subsequent steps, i.e., in the current stage (S05), to reconstruct the feature segments of new fields to be entered, thereby aggregating the distributed but component-related historical data back into the status code carried by the component itself.

[0146] Step S410: After the precast concrete component completes the current production stage and generates the updated production status code, read the target node bitmap from the feature parsing result of the field to be entered corresponding to the current production stage from the local cache of the current production stage, and determine the set of subsequent production stages to which the current field propagation unit needs to be propagated according to the value of each binary bit in the target node bitmap.

[0147] Before the updated production status code is generated and written to the component chip during the rebar tying stage, a pre-dependency check is performed to ensure the integrity and logical correctness of data propagation. The feature parsing results of the fields to be entered, stored in step S128, are read from the local cache. This cache contains the target node bitmap for each field to be entered in the current stage. For example, for field propagation unit A (tying operator ID), its target node bitmap is 0010010. Parsing this bitmap reveals that bits with a value of 1 correspond to bits 5 and 7, thus determining that this field propagation unit needs to be propagated to the quality inspection stage (S05) and the finished product delivery stage (S07). The target node bitmaps of all fields are merged to obtain the set of subsequent production stages to which all fields in the current production stage need to be propagated, such as {S05, S07}.

[0148] Step S420: Extract all historical field propagation unit sequences from the feature segment of the field to be entered in the updated production status code, traverse each historical field propagation unit in the historical field propagation unit sequence, and parse the propagation target bitmap corresponding to each historical field propagation unit from each historical field propagation unit.

[0149] From the updated production status code to be written to the chip, extract its core component—the new field feature segment to be entered. Decompress and parse this feature segment to obtain the historical field propagation unit sequence, which contains all historical field propagation units up to the previous production stage (mold assembly stage S01). Traverse each historical unit; for example, parse a historical unit from stage S01. Its propagation target bitmap might be 1000000, indicating that this unit needs to propagate to stage S02 (the rebar binding stage itself). Since we are currently in stage S02, this bitmap information is mainly used for traceability.

[0150] Step S430: Perform a bit-by-bit comparison between the target node bitmap corresponding to the current field propagation unit and the propagation target bitmap corresponding to each historical field propagation unit, and identify the isolated subsequent production stage corresponding to the target binary bit that has the first state in the target node bitmap but has the second state in the propagation target bitmap of all historical field propagation units.

[0151] This is a crucial logical verification step. The target node bitmap of the current field propagation unit determined in step S410 (e.g., 0010010) is compared bit-by-bit with the propagation target bitmap of each historical field propagation unit parsed in step S420. The focus of the comparison is whether the bits with a value of 1 in the current bitmap (e.g., bits 5 and 7) have also appeared as 1 in any historical bitmap. Assuming that bit 5 has never appeared as 1 in any historical bitmap (i.e., the propagation target of all historical units does not include S05), while bit 7 has appeared as 1 in some historical bitmap, then the comparison result will identify bit 5 as an "isolated subsequent production stage." This means that a new field (binding operator ID) needs to be propagated to S05, but S05 has never received data from any historical stage before, which may present a data dependency problem. Bit 7, however, is not isolated because it has historically propagated data.

[0152] Step S440: Obtain the isolated stage identifier corresponding to the isolated subsequent production stage, and query the set of associated field index codes that are related to the field index compression code in the current field propagation unit from the preset field association rule base according to the isolated stage identifier. Each associated field index code in the set of associated field index codes corresponds to an associated field that needs to be entered before the isolated subsequent production stage.

[0153] Once an isolated subsequent production stage, such as S05, is identified, its stage identifier is immediately obtained. Then, a pre-defined field association rule base is queried. This rule base defines the data dependencies in the production process. For example, for the quality inspection stage (S05), to correctly complete the inspection, in addition to knowing who the current inspector is (possibly entered in this stage), it is usually also necessary to know who the rebar tying operator of the inspected component is (for quality traceability). Therefore, the rule base might define a rule: when a field is to propagate to S05, data for both the "tying operator ID" (field index code 0001) and "tying completion time" (field index code 0002) fields must exist simultaneously. Based on the field index code of the current field propagation unit (e.g., 0001) and the isolated stage identifier S05, the rule base is queried, which may return a set of associated field index codes, such as {0002}, indicating that when field 0001 propagates to S05, field 0002 must exist as a preceding associated field.

[0154] Step S450: Search the historical field propagation unit sequence for whether it contains a historical field propagation unit that matches the index code of each associated field. If there is a missing associated field index code, combine the missing associated field index code and the corresponding isolated stage identifier to generate a field pre-missing alarm message.

[0155] Next, the historical field propagation unit sequence is searched for the existence of a propagation unit with field index code 0002. If the search result shows that the sequence does not contain any unit with field index code 0002, then data is considered missing. At this time, the missing associated field index code 0002 is combined with the isolated stage identifier S05 to generate a clear field prerequisite missing alarm message. The alarm message content can be described as: "Binding completion time (field 0002) is missing. This field is a prerequisite data required for the propagation of the binding operator ID (field 0001) to the quality inspection stage (S05)."

[0156] Step S460: Visualize the pre-missing field alarm information through the human-machine interface of the current production stage, and generate a forced supplement control for the missing related field on the human-machine interface of the current production stage based on the pre-missing field alarm information, and collect the supplement field value corresponding to the missing related field through the forced supplement control.

[0157] During the rebar tying stage, an alarm window immediately pops up on the human-machine interface, displaying the aforementioned missing field alarm information. Simultaneously, the interface dynamically generates a forced data entry control based on the alarm information. This control is similar to the data entry control described in step S1211, but its label area clearly indicates the name of the field to be entered, such as "Please enter the tying completion time (field 0002)". The input area of ​​this control is configured as a date and time selector based on the type constraint code (timestamp) of field 0002. Operators must use this control to input the missing value. When the operator selects a specific time in the date and time selector, such as "2023-10-27 14:30", and clicks confirm, this value is collected as the missing field value.

[0158] Step S470: The collected supplementary field values ​​are compressed and converted according to the aggregation method corresponding to the missing associated field index code to generate supplementary field propagation units. The supplementary field propagation units are inserted into the logical positions in the historical field propagation unit sequence that match the missing associated field index code to form a corrected historical field propagation unit sequence after supplementation correction.

[0159] The collected supplementary field value "2023-10-27 14:30" is processed. Based on its field index code 0002, the field aggregation rule base is queried to obtain the corresponding aggregation method code A02. The compression encoding algorithm corresponding to A02 is called to convert the timestamp into a 20-bit field entry value compression code. Then, the current production stage identifier S02, field index code 0002, the newly generated field entry value compression code, and the original propagation target bitmap of the supplementary field (which can be inferred from the rule base or context, for example, it should also propagate to S05) are combined, and a supplementary field propagation unit text string is generated according to steps S135 to S136. Next, this newly generated supplementary field propagation unit is inserted into the logical position where the unit should originally exist in the historical field propagation unit sequence, according to its field index code 0002 (for example, alongside unit 0001 in the same stage). Finally, a corrected historical field propagation unit sequence containing the necessary preceding data is obtained after supplementary correction.

[0160] Step S480: Regenerate a new field feature segment to be entered based on the historical field propagation unit correction sequence after supplementation and correction, and recombine the new field feature segment to be entered with the component basic identifier segment to generate the updated production status code after supplementation and correction, and reattach the updated production status code after supplementation and correction to the precast concrete component body.

[0161] Based on the correction sequence generated in step S470, step S170 and its sub-steps are re-executed to generate a new feature segment for the field to be entered, which already contains the supplementary data. Then, the new feature segment for the field to be entered is recombined with the component basic identifier segment. After steps such as length verification, adding a checksum, and hexadecimal encoding, an updated production status code text string after supplementary correction is generated. Finally, the corrected status code text string is written to the component chip via an RF writing device, overwriting the previously generated version.

[0162] Step S510: After the precast concrete component enters the current production stage and generates the current field propagation unit, the propagation target bitmap is parsed from the current field propagation unit, and the subsequent production stage sequence to which the current field propagation unit needs to propagate is determined according to the value of each binary bit in the propagation target bitmap.

[0163] After the current field propagation unit is generated during the rebar tying stage, such as field propagation unit A (tying operator ID), its binary form is first parsed to extract the propagation target bitmap inside, assuming it is 0010010. According to this bitmap, the bits with a value of 1 correspond to the 5th and 7th bits, so the original subsequent production stage sequence to which this unit needs to propagate is determined to be [quality inspection stage (S05), finished product delivery stage (S07)].

[0164] Step S520: Extract the stage sequence number identifier of all subsequent production stages after the current production stage and the field aggregation capability descriptor corresponding to each subsequent production stage from the preset production path planning data. The field aggregation capability descriptor is used to characterize the maximum number of field propagation units that the subsequent production stage can process at the same time and the compatibility of field propagation unit types.

[0165] From the production path planning system, detailed information for all production stages following the rebar tying stage (S02), i.e., S03 to S07, is extracted. For each stage, in addition to its stage number, its corresponding field aggregation capability descriptor is also extracted. For example, the curing stage (S06) is a highly automated stage, whose workstation control system is mainly used to execute preset temperature and humidity control programs. Its field aggregation capability descriptor may specify: a maximum number of units that can be processed simultaneously is 0 (indicating that this stage does not receive or process new field input data), or unit type compatibility is "only processing predefined parameter fields related to environmental monitoring sensors". The quality inspection stage (S05) is a stage that requires comprehensive judgment, and its descriptor may specify: a maximum number of units that can be processed simultaneously is 10, and it is compatible with all data types (such as text, numeric, and Boolean values).

[0166] Step S530: Based on the field aggregation capability descriptor corresponding to each subsequent production stage, filter the subsequent production stages in the subsequent production stage sequence, remove the subsequent production stages whose field aggregation capability descriptors do not meet the processing requirements of the current field propagation unit, and generate a filtered effective propagation target stage sequence.

[0167] The processing requirements of field propagation unit A are compared with the aggregation capability descriptors of each subsequent stage. Field propagation unit A is text data with a size of 10-bit compressed code. Comparing it with the descriptor of S06, S06's maximum number of processing units is 0, which does not meet the requirements, so S06 is removed from the propagation target sequence. Comparing it with the descriptor of S05, S05's maximum number of processing units is 10 and it is compatible with all types, meeting the requirements, so S05 is retained. Similarly, the descriptor of S07 might be "accepts all types, maximum number of 5," also meeting the requirements, so S07 is retained. After filtering, the original [S05, S07] sequence remains unchanged, while stages such as S06, which were not originally in the target bitmap, are unaffected. However, if the original bitmap contains S06, it will be removed in this step. Finally, a filtered valid propagation target stage sequence is generated, such as [S05, S07].

[0168] Step S540: Obtain the current load status parameters corresponding to each effective propagation target stage from the global load balancing node of the distributed storage system. The current load status parameters include the current number of queued processing units and the average processing latency. According to the preset load evaluation rules, map the current load status parameters to the load weight value corresponding to each effective propagation target stage.

[0169] To further optimize the overall efficiency of the production line, the filtered effective propagation target stage sequence [S05, S07] is combined with the real-time production status. A query is initiated via the network to the global load balancer node of the distributed storage system to obtain the current load status parameters of the S05 and S07 stages. For example, the current number of queued processing units for S05 is returned as Q_05, and the average processing latency is D_05; the current number of queued processing units for S07 is returned as Q_07, and the average processing latency is D_07. Based on a preset load assessment rule, such as a weighted formula W=α*Q+β*D, where α and β are weighting coefficients, Q_05 and D_05 are substituted into the formula to calculate the load weight value W_05 for S05; similarly, the load weight value W_07 for S07 is calculated. Assuming the calculation result is higher W_05, it indicates that S05 is currently very busy, while lower W_07 indicates that S07 is relatively idle.

[0170] Step S550: Dynamically adjust the propagation target bitmap according to the load weight value corresponding to each effective propagation target stage, and change the binary bits of the effective propagation target stages with load weight values ​​lower than the preset load threshold in the propagation target bitmap from the first state to the second state, thereby generating a dynamic propagation target bitmap after load balancing optimization.

[0171] Set a preset load threshold T_load. Compare the calculated load weight value with the threshold. For example, if W_05 is greater than T_load, it means S05 is overloaded; if W_07 is less than T_load, it means S07 is underloaded. To balance the production line load, it can be decided to temporarily cache data that was originally destined for the busy phase S05 within the component itself, or process it through other means, instead of forcing it to be sent to S05 immediately. Therefore, for the original propagation target bitmap 0010010 (the corresponding bits for S05 and S07 are 1), change the bit (5th bit) corresponding to S05 from 1 to 0, while leaving the bit (7th bit) corresponding to S07 unchanged. This generates a dynamic propagation target bitmap optimized for load balancing, such as 0000010, indicating that in the current production environment, this field propagation unit will preferentially propagate to S07, and will not propagate to S05 for the time being.

[0172] Step S560: Replace the original propagation target bitmap in the current field propagation unit with the dynamic propagation target bitmap to generate a current field propagation unit optimized by load balancing. Combine the current field propagation unit optimized by load balancing with the historical field propagation unit sequence to reconstruct and generate an updated set of field propagation units.

[0173] The original propagation target bitmap 0010010 in field propagation unit A is replaced with the dynamic propagation target bitmap 0000010 generated in step S550. Then, the field propagation unit assembly step is re-executed to generate a current field propagation unit optimized for load balancing. Next, this optimized unit is combined and reconstructed with the historical field propagation unit sequence parsed from the status code to generate an updated field propagation unit set. In this updated field propagation unit set, the target of field propagation unit A points to S07.

[0174] Step S570: Generate a new field feature segment to be entered based on the updated field propagation unit set, and recombine the new field feature segment to be entered with the component basic identifier segment to generate an updated production status code carrying a dynamic propagation target bitmap, and reattach the updated production status code carrying the dynamic propagation target bitmap to the precast concrete component body.

[0175] Based on the updated field propagation unit set generated in step S560, step S170 and its sub-steps are executed to generate a new field feature segment to be entered. This field feature segment implicitly contains dynamic propagation target information pointing to S07. Then, it is recombined with the component basic identifier segment, and after verification, encoding, and other steps, an updated production status code text string carrying a dynamic propagation target bitmap is generated. Finally, the new status code is written to the component chip through an RF writing device. When the component flows to S05, since the propagation target bitmap in its status code does not point to S05, the reading device of S05 will not actively retrieve the field, thus avoiding adding extra processing burden to the busy S05 station. When the component flows to S07, the status code indicates that the field needs to be activated here, and the device of S07 will read and use it normally, thereby realizing dynamic scheduling of data flow based on real-time production line load and optimizing overall production efficiency.

[0176] Step S610: After the precast concrete component enters the current production stage and generates the current field propagation unit, read the stage type identifier code corresponding to the current production stage from the local cache of the current production stage. The stage type identifier code is used to distinguish whether the current production stage belongs to the mold cleaning stage, rebar binding stage, embedded part installation stage, concrete pouring stage, curing stage, demolding stage or finished product inspection stage.

[0177] After generating the current field propagation unit during the rebar tying stage, in order to supplement the generation of some implicit information that is automatically generated during the production process and does not require manual input, the stage type identifier code of the current stage is first read from the local cache. For example, the stage type identifier code of the rebar tying stage is preset to T_02. This identifier code clearly distinguishes this stage from other stages, such as the mold cleaning stage (T_01), the curing stage (T_06), etc.

[0178] Step S620: Retrieve the implicit field activation condition table associated with the current production stage from the preset implicit information activation rule base according to the stage type identifier code. The implicit field activation condition table contains multiple implicit field index codes and activation condition expressions corresponding to each implicit field index code. Each activation condition expression is composed of the field input value range conditions of a specific field index code in the current field propagation unit.

[0179] Based on the stage type identifier T_02, the preset implicit information activation rule base is queried. This rule base defines which implicit fields will be automatically generated at different production stages when specific conditions are met. For example, for the rebar tying stage, the retrieved implicit field activation condition table may contain the following entries: Implicit field index code H_01 (corresponding to "rebar cage tying density level"), whose activation condition expression is "activate when the entered value of field index code 0003 (tying torque value) is greater than the set threshold V_torque". Another entry: Implicit field index code H_02 (corresponding to "operating environment temperature and humidity code"), whose activation condition expression is "always active", meaning it is automatically generated regardless of the entered value.

[0180] Step S630: Parse the field index compression code and field input value compression code from the current field propagation unit, decompress and restore the field input value compression code to obtain the original field input value, and compare the original field input value with the field input value range condition in the activation condition expression corresponding to each implicit field index code.

[0181] From the newly generated current field propagation unit (e.g., the unit corresponding to the binding torque value), parse out its field index compression code (e.g., 0003) and field input value compression code. Call the corresponding decompression algorithm to restore the compression code to the original binding torque value, e.g., T_value. Then, compare T_value with the activation condition expression "T_value is greater than V_torque" of H_01 in step S620. Meanwhile, for H_02, since its condition is "always active," it is directly determined to be active.

[0182] Step S640: When the original value entered into a field falls within the range of values ​​entered into a field corresponding to a certain implicit field index code, it is determined that the implicit field index code is activated in the current production stage, and the implicit field default value generation template associated with the activated implicit field index code is retrieved from the preset implicit field default value library.

[0183] Based on the comparison results, if T_value is greater than V_torque, then the implicit field index code H_01 is determined to be activated. At this point, a template is generated by retrieving the default value associated with H_01 from the preset implicit field default value library. For example, the template for H_01 might be a formula or rule: "Dense grade equals A_grade multiplied by T_value divided by V_torque". For H_02, which is always active, its template is retrieved, for example: "Ambient temperature and humidity code equals the real-time reading of the sensor at the current workstation".

[0184] Step S650: Based on the default value combination rules contained in the implicit field default value generation template, combine the real-time time parameter code of the current production stage with the workstation number parameter code of the current production stage to generate the implicit field default value code, and combine the implicit field index code with the implicit field default value code to form an implicit field key-value pair.

[0185] For template H_02, "Ambient temperature and humidity code equals the real-time reading of the current workstation sensor," the generation rules are executed. The current real-time timestamp, such as T_now, is obtained from the workstation control system. The workstation number, such as W_02, is obtained from the workstation configuration information. T_now is converted into a 24-bit time code according to the preset time encoding rules. W_02 is converted into an 8-bit workstation code according to the workstation encoding rules. These two codes are concatenated to form a 32-bit implicit field default value code. Then, the implicit field index code H_02 is combined with this 32-bit default value code to form a key-value pair (H_02, 32-bit default value code). For H_01, if activated, its default value generation template may involve calculations, such as calculating the "density level" and then mapping it to an 8-bit level code, forming a key-value pair with H_01.

[0186] Step S660: Arrange all implicit field key-value pairs generated in the current production stage according to the size order of the implicit field index code to generate a sequence of implicit field key-value pairs. Compress and encode the sequence of implicit field key-value pairs to generate a fixed-length implicit information segment for the current stage.

[0187] All implicit field key-value pairs generated in step S650, such as (H_01, 8-bit encoding) and (H_02, 32-bit encoding), are sorted according to the implicit field index codes H_01 and H_02 to form a sequence of implicit field key-value pairs. Then, this sequence is compressed and encoded, for example, using a fixed-length encoding method, converting each key-value pair into a fixed-length binary string, and concatenating all the binary strings of the key-value pairs to form a fixed-length implicit information segment for the current stage. The length of this information segment is preset, for example, L_hidden. If the actual generated implicit information is less than the maximum capacity, it is filled with null placeholders.

[0188] Step S670: Append the current stage implicit information segment before the start position of the current field propagation unit to generate an enhanced current field propagation unit carrying implicit information. Combine the enhanced current field propagation unit with the historical field propagation unit sequence to reconstruct and generate an updated field propagation unit set.

[0189] The implicit information segment generated in step S660 is appended as a new data block to the beginning of the original binary form of the current field propagation unit (e.g., the propagation unit for the binding torque value) generated in step S136. This forms a new, longer binary string, namely, an enhanced current field propagation unit carrying implicit information. This enhanced unit contains not only manually entered data (binding torque value) but also automatically generated implicit data (density level and environmental temperature and humidity codes). Then, this enhanced unit is combined and reconstructed with the historical field propagation unit sequence parsed from the status code to generate an updated set of field propagation units, which contains both explicit and implicit data from the production process.

[0190] Step S680: Generate a new field feature segment to be entered based on the updated field propagation unit set, and recombine the new field feature segment to be entered with the component basic identifier segment to generate an updated production status code carrying implicit information, and reattach the updated production status code carrying implicit information to the precast concrete component body.

[0191] Based on the updated field propagation unit set containing implicit information generated in step S670, step S170 and its sub-steps are re-executed to generate a new field feature segment to be entered. This field feature segment already contains implicit information. Then, it is recombined with the component basic identifier segment, and after verification, encoding, and other steps, an updated production status code text string carrying implicit information is generated. Finally, the status code containing more dimensions of production data is written to the component chip through an RF writing device, making the data carried by the component itself more complete.

[0192] In one exemplary embodiment, a distributed information entry and management system for precast concrete components is provided. This system can be a terminal, server, etc., and its internal structure diagram can be as follows: Figure 2As shown, the distributed information entry and management system for precast concrete components includes a processor, memory, input / output interface, communication interface, display unit, and input device. The processor, memory, and input / output interface are connected via a system bus, and the communication interface, display unit, and input device are also connected to the system bus via the input / output interface. The processor provides computing and control capabilities. The memory includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium. The input / output interface is used for exchanging information between the processor and external devices. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, mobile cellular networks, near-field communication, or other technologies. When the computer program is executed by the processor, it implements a distributed information entry and management method for precast concrete components. The display unit is used to form a visually visible image and can be a display screen, projection device, or virtual reality imaging device. The display screen can be an LCD screen or an e-ink screen. The input device can be a touch layer covering the display screen, or a button, trackball, or touchpad set on the shell of the distributed information entry and management system for precast concrete components, or an external keyboard, touchpad, or mouse, etc.

[0193] It should be noted that, in order to simplify the description of the present invention and thus help to understand one or more embodiments of the invention, multiple features may sometimes be grouped into one embodiment, drawing or description thereof in the foregoing description of the embodiments of the present invention.

Claims

1. A distributed information entry and management method applied to precast concrete components, characterized in that, The method includes: When the production process of each precast concrete component begins, an initial production status code is generated based on the design parameter information and production path planning information of the precast concrete component. The initial production status code is attached to the precast concrete component body. The initial production status code contains a current production stage identifier segment and a field feature segment to be entered. The field feature segment to be entered is used to characterize the propagation path and aggregation method of the field to be entered in the current production stage in subsequent production stages. When a precast concrete component enters the current production stage, the current production stage identifier segment and the field feature segment to be entered are parsed from the current production status code carried by the precast concrete component body. The field entry value is collected at the current production stage according to the field propagation path information recorded in the field feature segment to be entered. The collected field input values ​​are compressed and converted according to the field aggregation method recorded in the feature segment of the field to be input, and a current field propagation unit is generated. The current field propagation unit is embedded with the current production stage identifier, the compressed representation of the field input value, and the target node identifier set of the field in the subsequent production stage. The current field propagation unit is combined and reconstructed with other field propagation units parsed from the current production status code to generate an updated field propagation unit set containing the historical field propagation unit sequence and the current field propagation unit, and a new field feature segment to be entered is generated based on the updated field propagation unit set. The new field feature segment to be entered is recombined with the component base identification segment of the precast concrete component to generate an updated production status code, and the updated production status code is reattached to the precast concrete component body. The step of compressing and converting the collected field input values ​​according to the field aggregation method recorded in the feature segment of the field to be input, and generating the current field propagation unit, includes: Read the field entry records to be processed from the memory database of the current production stage. The field entry records to be processed contain the field index code, field entry value, current production stage identifier and target node bitmap. The target node bitmap is a fixed-length binary bit string, and each binary bit corresponds to a subsequent production stage. Based on the field index code, the aggregation method code associated with the field index code is queried from the preset field aggregation rule base. The aggregation method code is used to indicate the compression encoding algorithm and aggregation operation rules of the field input value during the propagation process. The field input value is compressed by calling the compression encoding algorithm corresponding to the aggregation method encoding, and the field input value is converted into a fixed-length field input value compression code. The length of the field input value compression code is determined by the compression ratio specified in the aggregation method encoding. Convert the current production stage identifier into a fixed-length stage identifier compressed code, convert the field index code into a fixed-length field index compressed code, and directly use the target node bitmap as a fixed-length propagation target bitmap; The stage identifier compression code, field index compression code, field input value compression code, and propagation target bitmap are concatenated according to the preset internal order of the propagation unit to generate the binary raw form of the current field propagation unit. The length of the binary raw form of the current field propagation unit is equal to the sum of the lengths of its components. Redundancy encoding is performed on the original binary form of the current field propagation unit to generate a binary string of the current field propagation unit carrying error correction code. The binary string of the current field propagation unit carrying error correction code is converted into a character representation to generate a text string of the current field propagation unit. The generated current field propagation unit text string is stored in the memory database of the current production stage, and the current field propagation unit text string is associated with the field entry record to be processed, marking that the field entry record to be processed has been converted into the propagation unit state; The step of combining and reconstructing the current field propagation unit with other field propagation units parsed from the current production status code to generate an updated field propagation unit set containing the historical field propagation unit sequence and the current field propagation unit includes: Read the current field propagation unit text string from the in-memory database of the current production stage, and at the same time read the text string of the feature segment of the field to be entered, which was previously parsed from the current production status code, from the local cache of the current production stage. The text string of the feature segment to be entered is decompressed, and the binary segments of the feature codes of other stages are extracted from the decompressed data, except for the binary segments of the target stage entry feature codes corresponding to the current production stage. Traverse the binary segment of the feature code entered in each other stage, and parse the historical field propagation unit sequence corresponding to that stage from the binary segment of the feature code entered in each other stage. The historical field propagation unit sequence is composed of multiple field propagation unit text strings generated in an earlier production stage of that stage, arranged in the order of generation time. All the parsed historical field propagation unit sequences are arranged in the order of their corresponding stage number identifiers to generate a total historical field propagation unit sequence. Each element in the total historical field propagation unit sequence is a field propagation unit text string. Append the current field propagation unit text string to the end of the total historical field propagation unit sequence to form an updated total field propagation unit sequence that includes the total historical field propagation unit sequence and the current field propagation unit text string; The updated field propagation unit sequence is compressed by converting all field propagation unit text strings in the updated field propagation unit sequence into a continuous binary data stream, generating an updated field propagation unit compressed package. The updated field propagation unit compressed package is used as the new field feature segment to be entered. The new field feature segment to be entered implicitly contains all field propagation units generated in the production stages, and the order of the field propagation units strictly corresponds to the order of the production stages.

2. The distributed information entry and management method for precast concrete components according to claim 1, characterized in that, When the production process of each precast concrete component begins, an initial production status code is generated based on the design parameters and production path planning information of the precast concrete component, including: The design drawing data of precast concrete components is extracted from the production scheduling system. The component outline parameters, internal reinforcement network parameters and concrete strength grade parameters contained in the design drawing data are analyzed and the component outline parameters are converted into fixed-length outline feature codes. The main reinforcement distribution density parameter, stirrup spacing parameter and embedded part location parameter in the internal reinforcement network parameters of the component are converted into main reinforcement density feature code, stirrup spacing feature code and embedded part location feature code, respectively. The main reinforcement density feature code, stirrup spacing feature code, embedded part location feature code and external contour feature code are sequentially combined to generate the component design feature code sequence. The component design feature coding sequence is subjected to dimensionality reduction mapping to generate component design feature code. The component design feature code is used as the core component of the component basic identification segment. The component design feature code is combined and spliced ​​with the production batch information code to generate a complete component basic identification segment. Production path planning data for precast concrete components is extracted from the production path planning system. The production path planning data includes multiple production stage names and the corresponding input field requirements for each production stage. Each input field requirement includes the field name, field data type, and a list of target nodes for the field's propagation in subsequent production stages. Assign a stage sequence number identifier to each production stage in the production path planning data, convert the field names in the input field requirements corresponding to each production stage into field index codes, convert the field data types into type constraint codes, and convert the list of target nodes for the propagation of the field in subsequent production stages into a target node bitmap. The stage number identifier, field index code, type constraint code and target node bitmap corresponding to each production stage are combined and encoded to generate the stage entry feature code corresponding to that production stage. All the stage entry feature codes corresponding to the production stages are arranged in the order of the stage number identifier to generate the stage entry feature code sequence. The stage input feature code sequence is compressed to generate the initial form of the field feature segment to be input. In the initial form of the field feature segment to be input, each stage input feature code occupies a fixed bit length, and the arrangement order between stage input feature codes strictly corresponds to the order of production stages. The initial forms of the component basic identifier segment and the feature segment of the field to be entered are combined according to the preset splicing order to generate the binary original form of the initial production status code. The binary original form of the initial production status code is verified and a verification code segment is generated. The verification code segment is appended to the end of the binary original form of the initial production status code. The binary original form of the initial production status code after the additional check code segment is converted into a character representation to generate an initial production status code text string. The initial production status code text string is then written into the storage area of ​​the passive RF memory chip, so that the passive RF memory chip carries the initial production status code text string. A passive radio frequency memory chip carrying an initial production status code text string is fixed in a designated position in the casting mold of a precast concrete component by pre-embedding. After the concrete is cast and demolded, the passive radio frequency memory chip and the precast concrete component body form an integrated carrying relationship.

3. The distributed information entry and management method for precast concrete components according to claim 1, characterized in that, When a precast concrete component enters its current production stage, the current production stage identifier segment and the feature segment of the field to be entered are parsed from the current production status code carried by the precast concrete component itself, including: The radio frequency reading device deployed at the current production stage transmits an activation carrier signal. When a precast concrete component carrying a passive radio frequency memory chip enters the reading range of the radio frequency reading device, the passive radio frequency memory chip receives the activation carrier signal and obtains working power through electromagnetic induction. After the passive radio frequency memory chip is powered on, it reads the current production status code text string stored in its storage area and transmits the current production status code text string back to the radio frequency reading device by modulating it into a reflected carrier signal through backscattering. The radio frequency reading device demodulates the current production status code text string from the received reflected carrier signal, performs character recognition and format verification on the current production status code text string, and confirms that the character composition of the current production status code text string conforms to the preset character encoding rules. The current production status code text string is segmented according to the preset splicing order. The component basic identifier segment text string is extracted from the beginning of the current production status code text string, the field feature segment text string to be entered is extracted from the middle of the current production status code text string, and the check code segment text string is extracted from the end of the current production status code text string. The text string of the feature segment to be entered is decompressed. The decompressed data is then divided into multiple binary segments of the feature code for each stage, with each binary segment corresponding to the entry feature information of a production stage. Traverse each stage's input feature code binary segment in the order of stage sequence number identifier, and parse out the corresponding stage sequence number identifier, field index code, type constraint code, and target node bitmap from the currently traversed stage's input feature code binary segment. The current stage sequence number identifier corresponding to the current production stage is compared with the stage sequence number identifier in the parsed binary segment of each stage input feature code. The target stage input feature code binary segment that matches the current stage sequence number identifier is selected from all the binary segments of stage input feature codes. Extract the field index code, type constraint code, and target node bitmap from the selected target stage input feature code binary segment. Use the field index code, type constraint code, and target node bitmap as the feature parsing result of the field to be input corresponding to the current production stage and store them in the local cache of the current production stage.

4. The distributed information entry and management method for precast concrete components according to claim 1, characterized in that, The step of collecting field input values ​​at the current production stage based on the field propagation path information recorded in the feature segment of the field to be input includes: Read the feature parsing results of the field to be entered from the local cache of the current production stage. The feature parsing results of the field to be entered contain the field index code, type constraint code and target node bitmap. The field index code is used to identify the name of the field to be entered, the type constraint code is used to constrain the data type of the field value, and the target node bitmap is used to indicate the subsequent production stage to which the field value needs to be propagated. The corresponding field name text is retrieved from the preset field name mapping table based on the field index code, and the corresponding data type description text is retrieved from the preset data type mapping table based on the type constraint code. The field name text and data type description text are combined to generate the input field prompt information for the current production stage. On the human-computer interaction interface of the current production stage, an input control is rendered. The label area of ​​the input control displays the input field prompt information. The input area of ​​the input control is configured as the corresponding input component according to the data type description text. The confirmation button of the input control is associated with the field value submission trigger event. Operators enter raw values ​​through the input field of the input control. The input field of the input control receives the operator's input in real time and temporarily stores the raw values ​​in the memory cache associated with the input control. When the operator triggers the confirmation button of the input control, the original input value is read from the memory cache associated with the input control, and the original input value is matched and validated against the type constraint code to verify whether the data format of the original input value conforms to the data type requirements specified by the type constraint code. Once the input raw value passes the data type matching validation, the input raw value is used as the field entry value for the current production stage. The field entry value is then associated with the field index code, the current production stage identifier, and the target node bitmap to generate the field entry record to be processed for the current production stage. The records to be entered into the field are stored in the memory database of the current production stage, and a prompt message indicating that the field entry value has been successfully collected is displayed on the human-computer interaction interface. At the same time, the entry control is reset to the initial state that can accept the next input.

5. The distributed information entry and management method for precast concrete components according to claim 1, characterized in that, The step of generating new field feature segments to be entered based on the updated field propagation unit set includes: The updated field propagation unit compressed package is parsed to obtain the text string of each field propagation unit contained in the updated field propagation unit compressed package. Each field propagation unit text string contains a stage identifier compression code, a field index compression code, a field input value compression code, and a propagation target bitmap. Iterate through the text string of each field propagation unit, extract the propagation target bitmap from the currently traversed field propagation unit text string, and perform matching analysis between the extracted propagation target bitmap and the stage sequence identifiers corresponding to all subsequent production stages after the current production stage. Based on the matching analysis results, determine whether each field propagation unit text string needs to be activated in each subsequent production stage, and generate an activation state vector corresponding to each field propagation unit text string. The activation state vector is a binary bit string with a length equal to the number of subsequent production stages. Perform a bitwise OR operation on the activation state vectors of all field propagation unit text strings to generate a comprehensive activation state vector. Each bit in the comprehensive activation state vector indicates whether at least one field propagation unit needs to be activated in the corresponding subsequent production stage. Based on the binary bit in the comprehensive activation state vector that corresponds to the first state, the corresponding stage entry feature code template is retrieved from the preset stage entry feature code template library. Each field propagation unit text string is filled into the specified position in the retrieved corresponding stage entry feature code template according to the subsequent production stage indicated by the binary bit with the first state value in its corresponding activation state vector, thereby generating the updated stage entry feature code corresponding to each subsequent production stage. All updated stage input feature codes are arranged in the order of the serial number identifiers of the subsequent production stages to generate an updated stage input feature code sequence. The updated stage input feature code sequence is then compressed to generate new field feature segments to be input.

6. The distributed information entry and management method for precast concrete components according to claim 1, characterized in that, The step of recombining the new field feature segment to be entered with the component foundation identification segment of the precast concrete component to generate an updated production status code includes: Read the component foundation identification segment text string of the precast concrete component from the local cache of the current production stage. The component foundation identification segment text string is a fixed part that is parsed from the current production status code and remains unchanged throughout the production process. The newly generated field feature segment to be entered is combined with the component basic identifier segment text string according to the preset concatenation order to generate the intermediate binary form of the updated production status code. The first part of the intermediate binary form of the updated production status code is the binary string corresponding to the component basic identifier segment text string, and the second part is the binary string corresponding to the new field feature segment to be entered. The length of the intermediate binary form of the updated production status code is checked. The actual bit length of the intermediate binary form is calculated to see if it is equal to the preset standard production status code bit length. If the actual bit length is less than the standard length, zero bits are padded to the end of the intermediate binary form until the standard length is reached. The updated production status code binary string after length verification is checked and a new check code segment is generated. The new check code segment is appended to the end of the updated production status code binary string after length verification to form a complete updated production status code binary string. The complete updated production status code binary string is converted into hexadecimal character representation in groups of four, generating an updated production status code text string. The character length of the updated production status code text string is equal to the quotient of the binary string length divided by four, plus the character length of the check segment after conversion. The updated production status code text string is transmitted to the passive radio frequency storage chip carried by the precast concrete component body through the radio frequency writing device via the radio frequency writing signal. After receiving the radio frequency writing signal, the passive radio frequency storage chip writes the updated production status code text string into its storage area, overwriting the original current production status code text string.

7. The distributed information entry and management method for precast concrete components according to claim 1, characterized in that, The method further includes: After the precast concrete component has completed all the preset production stages, the final production status code text string carried by the precast concrete component body is obtained from the final production stage. The final production status code text string contains the component basic identification segment and the final field feature segment to be entered. The feature segments of the final fields to be entered are decompressed, and the text strings of field propagation units corresponding to all historical production stages are extracted from the decompressed data. Each field propagation unit text string corresponds to a field value entered in a production stage. All extracted field propagation unit text strings are grouped according to the stage identifier compression code embedded in each field propagation unit text string. Field propagation unit text strings belonging to the same production stage are grouped into the same group to generate a set of field propagation unit groups grouped by production stage. The text strings of the field propagation units in each set of field propagation units are grouped a second time according to the compression code of the field index they are embedded in. The text strings of the field propagation units belonging to the same field index are divided into the same subgroup, generating a set of field propagation unit subgroups grouped by field index. The text strings of field propagation units in each subgroup of field propagation units are sorted according to their generation time, and the last field propagation unit text string in the sorted sequence is selected as the final valid field propagation unit corresponding to the field index. Each final valid field propagation unit is decoded, the field entry value compression code is extracted from the final valid field propagation unit, and the decompression algorithm associated with the field index compression code is called to decompress and restore the field entry value compression code to obtain the original field entry value. All the restored original field values ​​are structured according to their corresponding production stage sequence number and field index code to generate a complete production information archive for precast concrete components. Each production stage in the complete production information archive corresponds to a data subset, and each data subset contains all field names and field values ​​entered in that stage.

8. A distributed information entry and management system for precast concrete components, characterized in that, include: processor; A machine-readable storage medium for storing machine-executable instructions of the processor; The processor is configured to execute the distributed information entry and management method for precast concrete components according to any one of claims 1 to 7 by executing the machine-executable instructions.

Images