Livestock breeding intelligent management and control cloud system and method thereof

Abstract

The present application relates to the field of information technology for livestock breeding, in particular to an intelligent management and control cloud system for livestock breeding and a method thereof, the system comprising a procedure processing module, a state acquisition module, a condition determination module and a task generation module, the procedure processing module generating a procedure item data table, the state acquisition module generating a field state data table, the condition determination module comparing livestock identity categories, execution time periods and target operation values, and generating a procedure condition satisfaction result, and the task generation module generating a completion record, a supplementary operation task, an overdue operation task or a device control instruction accordingly.In the present application, by incorporating breeding procedures, field states, personnel operation records and device operation states into the same determination chain, the completion record is written into a breeding process archive table, the supplementary operation task and the overdue operation task are sent to a user terminal, and the device control instruction is sent to a controller via a barn gateway, thereby forming a procedure-driven cloud management and control closed loop.

Description

Technical Field

[0001] This invention belongs to the field of information technology for livestock farming, specifically, it relates to a cloud system and method for intelligent management and control of livestock farming. Background Technology

[0002] The field of livestock information technology involves establishing information service systems around agricultural production knowledge, operational standards, operation records, and process data. These systems support the dissemination, application, and record management of livestock technology information through the storage and retrieval of technical procedures, production archives, and personnel operation data. Specifically, a traditional livestock farming intelligent management and control cloud system refers to a system that stores livestock farming procedures, equipment operation instructions, feeding standards, disease prevention and control records, and personnel training records in a cloud database. User terminals log in with accounts to access farming technology data, submit operation records, and maintain farming process data.

[0003] Current livestock farming management typically relies on cloud-based databases to store farming procedures, equipment specifications, feeding standards, disease prevention and control records, and training records. Users rely on terminals to access information and submit work records. However, there is a lack of calculable correspondence between procedure items, on-site data collection, personnel work records, and equipment operating status. It is difficult to form a continuous management chain for work completion status, supplementary work requirements, overdue work situations, and equipment control actions in the same process. The results of pen management still require manual verification of data and records, and process archives and on-site control status are easily scattered. Summary of the Invention

[0004] To address the technical problems existing in the prior art, embodiments of the present invention provide a smart management and control cloud system and method for livestock farming.

[0005] To solve the above-mentioned technical problems, the present invention provides the following technical solution: A smart cloud system for livestock farming management, comprising: The procedure processing module is used to receive the breeding procedure text entered by the management terminal, extract the livestock identity category, pen number, execution period, target operation value, equipment name, expected action status and record voucher type from the breeding procedure text, and generate a procedure entry data table. The status acquisition module, connected to the procedure processing module, is used to receive livestock identification data uploaded by the ear tag reader, pen number data uploaded by the pen gateway, field status data uploaded by the sensor, equipment operation status uploaded by the controller, and personnel operation records submitted by the user terminal, and to generate a field status data table according to the livestock identification data, pen number data, and collection time. The condition determination module, connected to the status acquisition module, is used to read the procedure entry data table and the on-site status data table, compare the consistency between the livestock identity category and the livestock identity data, compare the range between the execution time period and the collection time, compare the difference between the target operation value and the actual operation value in the personnel operation record, and generate the result that the procedure conditions are met. The task generation module, connected to the condition determination module, is used to generate completion records, supplementary work tasks, overdue work tasks, or equipment control instructions based on the results of fulfilling the procedural conditions, combined with the collection time and equipment operating status in the field status data table, and the deadline time, equipment name, and expected action status of the execution period in the procedural entry data table. The completion records are written into the aquaculture process archive table, the supplementary work tasks and overdue work tasks are sent to the user terminal, and the equipment control instructions are sent to the controller through the pen gateway.

[0006] The following are further optimizations of the above technical solution by the present invention: The procedure processing module includes: The text receiving submodule is configured to receive the aquaculture procedure text entered by the management terminal, read the corresponding entry account, entry time and text version identifier of the aquaculture procedure text, and generate a procedure text receiving record. The field extraction submodule, connected to the text receiving submodule, is configured to locate the livestock identity category, pen number, execution period, target operation value, equipment name, expected action status, and record voucher type from the procedure text receiving record according to the pre-stored field name table, and generate the procedure field extraction results; The entry generation submodule, connected to the field extraction submodule, is configured to write the extracted procedure fields into the procedure entry data table by entry number.

[0007] Further optimization: The field extraction submodule is specifically configured as follows: read the field start identifier and field end identifier corresponding to each field name in the pre-stored field name table, determine the position of the field start identifier in the aquaculture procedure text as the field extraction start point, determine the position of the field end identifier in the aquaculture procedure text as the field extraction end point, extract the field content according to the field extraction start point and field extraction end point, establish a mapping relationship between the extracted field content and the corresponding field name, and generate a field content mapping table; correspondingly, the entry generation submodule is configured to generate a procedure entry data table according to the field content mapping table.

[0008] Further optimization: The status acquisition module includes: The identity receiving submodule is configured to receive livestock identity data uploaded by the ear tag reader, establish a correspondence between the livestock identity data and the receiving time, and generate a livestock identity receiving record; The barracks receiving submodule is connected to the identity receiving submodule and is configured to receive barracks number data uploaded by the barracks gateway, establish a correspondence between the barracks number data and the gateway communication address, and generate barracks number receiving records. The status table submodule, connected to the pen receiving submodule, is configured to receive on-site status data uploaded by sensors, equipment operating status uploaded by controllers, and personnel operation records containing actual operation values ​​submitted by user terminals. It writes livestock identity reception records, pen number reception records, on-site status data, equipment operating status, and personnel operation records into the on-site status data table according to the collection time.

[0009] Further optimization: The specific configuration of the status table submodule is as follows: read the reception time from the livestock identity reception record, the reception time from the pen number reception record, the collection time from the field status data, the reporting time from the equipment operation status, and the operation time from the personnel operation record; compare the maximum interval between each time with the pre-stored synchronization interval threshold; when the maximum interval does not exceed the pre-stored synchronization interval threshold, write the livestock identity reception record, pen number reception record, field status data, equipment operation status, and personnel operation record into the same field status record; when the maximum interval exceeds the pre-stored synchronization interval threshold, generate a status synchronization anomaly record.

[0010] Further optimization: The condition determination module includes: The identity comparison submodule is configured to read the livestock identity category from the procedure entry data table and the livestock identity data from the field status data table, compare the livestock identity category with the livestock identity data for consistency, and generate an identity consistency result. The time period comparison submodule, connected to the identity comparison submodule, is configured to read the execution time period and the collection time, compare the collection time with the execution time period within a range, and generate a time period matching result. The numerical comparison submodule, connected to the time period comparison submodule, is configured to read the target operation value and the actual operation value, calculate the difference between the target operation value and the actual operation value, and generate the numerical matching result. The condition determination module is configured to aggregate the identity consistency result, time period hit result, and numerical compliance result to generate the procedure condition satisfaction result.

[0011] Further optimization: The specific configuration of the numerical comparison submodule is as follows: read the allowable deviation value corresponding to the target operation value in the pre-stored allowable deviation table, subtract the target operation value from the actual operation value and take the absolute value to obtain the operation value difference, compare the operation value difference with the allowable deviation value, generate a numerical compliance result when the operation value difference does not exceed the allowable deviation value, and generate a numerical deviation result when the operation value difference exceeds the allowable deviation value.

[0012] Further optimization: The task generation module includes: The result allocation submodule is configured to read the procedure condition fulfillment result, and based on the identity consistency result, time period hit result, and value compliance result in the procedure condition fulfillment result, combined with the collection time and equipment operating status in the field status data table, and the end time, equipment name, and expected action status of the execution period in the procedure entry data table, determine at least one control output among the completion record, supplementary work task, overdue work task, and equipment control instruction. The record writing submodule, connected to the result allocation submodule, is configured to write the completion record to the aquaculture process archive table. The task sending submodule, connected to the result allocation submodule, is configured to send supplementary job tasks and overdue job tasks to the user terminal. The instruction forwarding submodule, connected to the result allocation submodule, is configured to send device control instructions to the controller via the gatehouse gateway.

[0013] Further optimization: The result allocation submodule is specifically configured as follows: when the identity consistency result, time period hit result, and value conformance result are all true, a completion record is generated; when the identity consistency result and time period hit result are true but the value conformance result is false, a supplementary job task is generated; when the identity consistency result is true, the time period hit result is false, and the collection time is later than the deadline of the execution time period, an overdue job task is generated; when the equipment operating status corresponding to the equipment name in the field status data table does not reach the expected action status corresponding to the equipment name in the procedure entry data table, an equipment control instruction is generated to make the equipment operating status tend towards the expected action status.

[0014] This invention also provides a smart management and control cloud method for livestock farming, which is executed based on the above-mentioned smart management and control cloud system for livestock farming, and includes the following steps: S1: Receive the breeding procedure text entered by the management terminal, extract the livestock identity category, pen number, execution time period, target operation value, equipment name, expected action status and record voucher type from the breeding procedure text, and generate a procedure entry data table; S2: Receive livestock identification data uploaded by ear tag readers, pen number data uploaded by pen gateways, field status data uploaded by sensors, equipment operation status uploaded by controllers, and personnel operation records submitted by user terminals, and generate a field status data table according to livestock identification data, pen number data, and collection time. S3: Read the procedure entry data table and the field status data table, compare the consistency between the livestock identity category and the livestock identity data, compare the execution time period with the collection time, compare the difference between the target operation value and the actual operation value in the personnel operation record, and generate the procedure condition satisfaction result. S4: Based on the results of meeting the procedural conditions, and combined with the collection time and equipment operating status in the field status data table, as well as the deadline, equipment name, and expected action status of the execution period in the procedural item data table, generate completion records, supplementary work tasks, overdue work tasks, or equipment control instructions. Write the completion records into the aquaculture process archive table, send the supplementary work tasks and overdue work tasks to the user terminal, and send the equipment control instructions to the controller through the pen gateway.

[0015] The present invention, by adopting the above technical solution, has at least the following beneficial effects: 1. This invention breaks down the livestock breeding procedure text into livestock identity category, pen number, execution period, target operation value, equipment name, expected action status, and record voucher type. It establishes a common source judgment relationship with livestock identity data, pen number data, on-site status data, equipment operation status, and personnel operation records. Based on identity consistency, time range, and operation value difference, it forms the result of procedure condition satisfaction. Then, it generates a completion record according to the result, supplements the operation tasks, overdue operation tasks, and equipment control instructions, so that operation records, process archives, user terminal prompts, and pen controller actions enter the same cloud management chain, reducing the links of data retrieval and manual verification, and enhancing the consistency of management results. Attached Figure Description

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

[0017] Figure 1 This is the overall architecture diagram of the intelligent management and control cloud system for livestock breeding of the present invention; Figure 2 This is a flowchart illustrating the generation process of the aquaculture procedure items for this invention. Figure 3 This is a flowchart of the process for tabulating the field status data according to the present invention; Figure 4 This is a flowchart of the procedure condition determination process of the present invention; Figure 5 This is a flowchart for generating the control output of the present invention. Detailed Implementation

[0018] To make the technical problems, technical solutions and advantages of the present invention clearer, a detailed description will be given below in conjunction with the accompanying drawings and specific embodiments.

[0019] This embodiment provides a smart livestock farming management and control cloud system and method. During the production management process in livestock farm pens, managers maintain farming procedures through management terminals. Ear tags worn by livestock are identified by ear tag readers. The pen gateway receives communication data from the pen side. Sensors continuously generate on-site status data related to the pen environment or operational status. The controller reports the equipment operating status of the pen equipment. User terminals submit personnel work records. The cloud side establishes a correspondence between the farming procedure text, on-site status data, personnel work records, and equipment operating status, enabling procedure entries to participate in work completion judgment, supplementary work prompts, overdue work prompts, and equipment control command generation. The aforementioned smart livestock farming management and control cloud system and method include a smart livestock farming management and control cloud system and a related smart livestock farming management and control cloud method, wherein the system is the main implementation object, and the method is the associated implementation object.

[0020] In traditional livestock farming management, farming procedures, equipment specifications, work records, and equipment operating status are usually presented as independent documents or records. Managers need to consult the procedures before verifying on-site records, and there is a lack of direct data correspondence between equipment control actions and procedure entries. This embodiment transforms the farming procedure text into a procedure entry data table, and converts on-site collected data and personnel work records into an on-site status data table. Then, it generates a result indicating that the procedure conditions are met through condition judgment. This result drives the completion of records, the generation of supplementary work tasks, overdue work tasks, and equipment control instructions, thereby forming a cloud-based management and control link centered around the same procedure entry.

[0021] Please see Figure 1 and Figure 2The procedure processing module receives the livestock breeding procedure text entered by the management terminal, extracts the livestock identity category, pen number, execution time period, target operation value, equipment name, expected action status, and record voucher type from the text, and generates a procedure entry data table. The livestock breeding procedure text refers to the textualized procedure content entered by the management terminal to regulate livestock breeding operations. This textual procedure content includes information on livestock, pen location, operation time, operation quantity, equipment actions, and voucher requirements. The procedure entry data table is a data table generated by the procedure processing module in a field-based manner. This data table uses the entry number as an index, writing the livestock identity category, pen number, execution time period, target operation value, equipment name, expected action status, and record voucher type corresponding to the same procedure into the same record, allowing the subsequent condition judgment module to read and compare the corresponding fields by entry. The expected action status refers to the field in the procedure entry used to indicate the operating state that the equipment should achieve. This field, together with the equipment name, defines the basis for generating subsequent equipment control commands.

[0022] In one embodiment, the procedure processing module includes a text receiving submodule, a field extraction submodule, and an entry generation submodule. The text receiving submodule receives the aquaculture procedure text entered from the management terminal, reads the corresponding entry account, entry time, and text version identifier, and generates a procedure text receiving record. The procedure text receiving record is a data object that records the source and version of the same aquaculture procedure text. The record carries the entry account, entry time, text version identifier, and the main text of the aquaculture procedure text, and is used to determine the source boundary of the parsed text during subsequent field extraction. The entry account identifies the source of the personnel's permissions for entering the aquaculture procedure text, the entry time identifies the time sequence in which the text entered the system, and the text version identifier distinguishes different entry versions of the same procedure entry.

[0023] The field extraction submodule is connected to the text receiving submodule. The field extraction submodule locates the livestock identity category, pen number, execution period, target operation value, equipment name, expected action status, and record voucher type from the received procedure text records according to a pre-stored field name table, generating the procedure field extraction results. The pre-stored field name table refers to a pre-maintained field identification rule table. This table records the start and end identifiers for each field name. The start identifier defines the beginning position of the field content in the livestock breeding procedure text, and the end identifier defines the end position. The procedure field extraction results refer to the set of field content extracted by the field extraction submodule from the received procedure text records. The results retain the correspondence between field names and field content and provide this correspondence to the entry generation submodule.

[0024] The entry generation submodule is connected to the field extraction submodule. The entry generation submodule writes the extracted field results into the procedure entry data table according to the entry number. The entry number is an index field used to uniquely point to a procedure entry. During the writing process, the entry generation submodule associates the livestock identity category, pen number, execution period, target operation value, equipment name, expected action status, and record voucher type from the same extracted field results to the same entry number, so that all judgment fields can be retrieved at once when the same procedure entry is read later. If an older version of the record for the same entry number already exists, the entry generation submodule distinguishes between retaining or updating the record based on the text version identifier, ensuring that the source of records in the procedure entry data table remains traceable.

[0025] In one embodiment, the field extraction submodule reads the field start and end identifiers corresponding to each field name in the pre-stored field name table. It determines the position of the field start identifier in the aquaculture procedure text as the field extraction start point and the position of the field end identifier as the field extraction end point. Field content is extracted according to the field extraction start and end points, and a mapping relationship is established between the extracted field content and the corresponding field name to generate a field content mapping table. The field content mapping table is a data structure that associates field names with extracted field content one-to-one. This data structure allows the entry generation submodule to read the corresponding field content according to the field name, rather than relying on manual verification of the field meaning. Accordingly, the entry generation submodule generates a procedure entry data table according to the field content mapping table. If the field start or end identifier fails to form a valid correspondence in the aquaculture procedure text, the field extraction submodule marks the corresponding field as pending verification and prevents the field from being formally written into the procedure entry data table until the management terminal supplements or corrects the corresponding field content.

[0026] In this embodiment, by decomposing the aquaculture procedure text into procedure text receiving records, procedure field extraction results, field content mapping tables, and procedure item data tables, the text procedure can be transformed into structured fields that can be read by the condition judgment module, thereby providing clear data sources for subsequent identity consistency comparison, time period range comparison, operation value difference comparison, and equipment expected action status comparison.

[0027] Please see Figure 1 and Figure 3The status acquisition module is connected to the procedure processing module. The status acquisition module receives livestock identification data uploaded by ear tag readers, pen number data uploaded by the pen gateway, on-site status data uploaded by sensors, equipment operating status uploaded by the controller, and personnel work records submitted by the user terminal. It then generates an on-site status data table based on the livestock identification data, pen number data, and the time of data collection. Specifically, livestock identification data refers to data read by the ear tag reader that identifies the individual livestock or livestock category; pen number data refers to data uploaded by the pen gateway that identifies the pen location; on-site status data refers to data collected by sensors that describes the pen environment or work site status; equipment operating status refers to data uploaded by the controller that describes the current operational status of the equipment; and personnel work records refer to data submitted by the user terminal that describes the personnel's work performance. The on-site status data table is a status record table generated by the status acquisition module based on the livestock identification data, pen number data, and the time of data collection. This record table provides the condition determination module with on-site comparison objects.

[0028] In one embodiment, the status acquisition module includes an identity receiving submodule, a pen receiving submodule, and a status tabulation submodule. The identity receiving submodule receives livestock identity data uploaded by the ear tag reader and establishes a correspondence between the livestock identity data and the receiving time, generating a livestock identity receiving record. The livestock identity receiving record refers to a record object that binds livestock identity data to the receiving time, and is used to confirm whether the corresponding livestock enters the subsequent status tabulation process within the same collection cycle. If the livestock identity data uploaded by the ear tag reader lacks identifiable identity information, the identity receiving submodule writes this data into an identity anomaly record, preventing the data from directly entering the on-site status data table.

[0029] The fence receiving submodule is connected to the identity receiving submodule. The fence receiving submodule receives fence number data uploaded by the fence gateway and establishes a correspondence between the fence number data and the gateway communication address, generating a fence number reception record. This fence number reception record refers to the record object after binding the fence number data with the gateway communication address; the gateway communication address indicates the communication source of the fence number data. The fence receiving submodule provides the fence number reception record to the status tabulation submodule, enabling the status tabulation submodule to assign field status data and equipment operating status to the corresponding fence.

[0030] The status tabulation submodule is connected to the pen receiving submodule. It receives on-site status data uploaded by sensors, equipment operating status uploaded by the controller, and personnel operation records containing actual operation values ​​submitted by the user terminal. It writes the livestock identification reception record, pen number reception record, on-site status data, equipment operating status, and personnel operation records into the on-site status data table according to the collection time. The actual operation value refers to the field in the personnel operation record used to describe the number of operations performed. The actual operation value is compared with the target operation value in the subsequent condition judgment module. The status tabulation submodule uses the collection time as the aggregation basis, writing livestock identification reception records, pen number reception records, on-site status data, equipment operating status, and personnel operation records obtained within the same time range into the same on-site status record, so that the same on-site status record can correspond to a set of identifiable on-site information.

[0031] In one embodiment, the status tabulation submodule reads the reception time from the livestock identity reception record, the reception time from the pen number reception record, the collection time from the field status data, the reporting time from the equipment operation status, and the operation time from the personnel operation record. It compares the maximum interval between these times with a pre-stored synchronization interval threshold. When the maximum interval does not exceed the pre-stored synchronization interval threshold, the corresponding data is written into the same field status record. When the maximum interval exceeds the pre-stored synchronization interval threshold, a status synchronization anomaly record is generated. The pre-stored synchronization interval threshold refers to a pre-configured time boundary used to determine whether multi-source data belongs to the same status tabulation range. This time boundary can be jointly determined by the farm equipment collection cycle, personnel operation submission rules, and pen gateway reporting rules. A status synchronization anomaly record is used to mark records where multi-source data failed to complete synchronization. This record is not used as a direct basis for determining whether the procedural conditions are met, but it can be used for subsequent verification of data sources.

[0032] In this embodiment, by aggregating livestock identification data, pen number data, on-site status data, equipment operating status, and personnel operation records according to the collection time, the on-site status data table can simultaneously carry the object field, location field, time field, status field, and operation field required for procedure determination, thereby avoiding the condition determination module from repeatedly extracting data from multiple sources during subsequent comparisons.

[0033] Please see Figure 1 and Figure 4The condition determination module is connected to the status acquisition module. It reads the procedure entry data table and the on-site status data table, compares the livestock identity category with the livestock identity data for consistency, compares the execution time period with the collection time for range, and compares the target operation value with the actual operation value in the personnel operation record for difference, generating a procedure condition satisfaction result. This result, generated by the condition determination module based on identity consistency, time period matching, and operation value compliance, informs the task generation module whether the on-site status corresponding to the current procedure entry meets the conditions for generating a completion record, supplementing operation tasks, overdue operation tasks, or equipment control commands.

[0034] In one embodiment, the condition determination module includes an identity comparison submodule, a time period comparison submodule, and a numerical comparison submodule. The identity comparison submodule reads the livestock identity categories from the procedure entry data table and the livestock identity data from the field status data table, compares the livestock identity categories with the livestock identity data for consistency, and generates an identity consistency result. The identity consistency result indicates whether the livestock identity category defined by the procedure entry corresponds to the livestock identity data in the field status data table. If the livestock identity data falls within the category range corresponding to the livestock identity category, the identity comparison submodule generates an identity consistency result indicating consistency; if the livestock identity data does not fall within the category range corresponding to the livestock identity category, the identity comparison submodule generates an identity consistency result indicating inconsistency. The identity consistency result serves as input for subsequent determinations by the time period comparison submodule and the task generation module.

[0035] The time period comparison submodule is connected to the identity comparison submodule. The time period comparison submodule reads the execution time period and the data collection time, compares the data collection time with the execution time period, and generates a time period match result. The execution time period refers to the executable time range defined in the procedure entry data table, and the data collection time refers to the time field associated with the field status record in the field status data table. The time period match result indicates whether the data collection time falls within the execution time period. If the data collection time is within the execution time period's defined range, the time period comparison submodule generates a time period match result indicating a match; if the data collection time is not within the execution time period's defined range, the time period comparison submodule generates a time period match result indicating a mismatch. The time period match result and the identity consistency result are then used together in the subsequent branch judgment of the numerical comparison submodule or the task generation module.

[0036] The numerical comparison submodule is connected to the time-period comparison submodule. The numerical comparison submodule reads the target operation value and the actual operation value, calculates the difference between the target and actual operation values, and generates a result indicating that the procedure conditions are met. Here, the target operation value refers to the operation quantity field defined in the procedure entry data table, the actual operation value refers to the operation quantity field submitted in the personnel's operation record, and the operation value difference refers to the degree of deviation of the actual operation value from the target operation value. The numerical comparison submodule reads the allowable deviation value corresponding to the target operation value from the pre-stored allowable deviation table, subtracts the target operation value from the actual operation value, and takes the absolute value to obtain the operation value difference. This difference is compared with the allowable deviation value. If the difference does not exceed the allowable deviation value, a numerical compliance result is generated; if the difference exceeds the allowable deviation value, a numerical deviation result is generated. The allowable deviation value is a configuration field in the pre-stored allowable deviation table used to limit the acceptable deviation range of the target operation value. The pre-stored allowable deviation table can be configured by the aquaculture procedure management personnel according to the operation type and procedure requirements.

[0037] In one embodiment, the condition determination module combines the identity consistency result, the time period hit result, and the numerical conformity result or numerical deviation result into a procedure condition fulfillment result. If the identity consistency result indicates consistency, the time period hit result indicates a hit, and a numerical conformity result is generated, then the procedure condition fulfillment result indicates that the main operational conditions of the corresponding procedure item are met. If the identity consistency result indicates consistency, the time period hit result indicates a hit, but a numerical deviation result is generated, then the procedure condition fulfillment result indicates that there is an operational numerical deviation in the corresponding procedure item. If the identity consistency result indicates consistency, but the time period hit result indicates a miss, then the procedure condition fulfillment result indicates that the time condition of the corresponding procedure item is not met. If the identity consistency result indicates inconsistency, then the procedure condition fulfillment result does not enter the completion record generation branch under the corresponding livestock identity category.

[0038] In this embodiment, by generating identity consistency results, time period hit results, job value difference, value compliance results, and value deviation results layer by layer, the result of meeting the procedure conditions can retain the judgment source of different condition items, thereby enabling the task generation module to generate different types of control outputs based on different condition states.

[0039] Please see Figure 1 and Figure 5The task generation module is connected to the condition determination module. The task generation module generates completion records, supplementary tasks, overdue tasks, or equipment control commands based on the fulfillment of procedural conditions. It writes completion records to the breeding process archive table, sends supplementary and overdue tasks to the user terminal, and sends equipment control commands to the controller via the pen gateway. Specifically, a completion record is a record written to the breeding process archive table indicating that a procedural item has reached a completed state; a supplementary task is a task that prompts personnel to perform additional tasks or tasks; an overdue task is a task that prompts personnel that a procedural item has not reached a completed state beyond its execution period; and an equipment control command is a control object sent to the controller via the pen gateway to bring the equipment's operating state towards the expected action state. The breeding process archive table stores livestock identification data, pen number data, procedural item-related results, and completion records.

[0040] In one embodiment, the task generation module includes a result allocation submodule, a record writing submodule, a task sending submodule, and an instruction forwarding submodule. The result allocation submodule reads the procedural condition fulfillment results and, based on the identity consistency result, time period matching result, and numerical compliance result in the procedural condition fulfillment results, combined with the acquisition time and equipment operating status in the field status data table, and the deadline time, equipment name, and expected action status of the execution period in the procedural entry data table, determines at least one of the following control outputs: completed record, supplementary work task, overdue work task, and equipment control instruction. The control output refers to the output object allocated by the task generation module to the record writing submodule, task sending submodule, or instruction forwarding submodule based on the procedural condition fulfillment results.

[0041] The record writing submodule is connected to the result allocation submodule. The record writing submodule writes completed records into the breeding process archive table. Upon completion, the record is associated with the entry number in the corresponding procedure entry data table, the livestock identity data in the field status data table, the pen number data, and the collection time. This allows the breeding process archive table to trace the procedure execution status by livestock identity or pen number. If a completed record lacks an entry number or the necessary associated fields in the field status data table, the record writing submodule moves the completed record to a pending verification state and does not write it into the breeding process archive table as a valid completion.

[0042] The task sending submodule is connected to the result allocation submodule. The task sending submodule sends supplementary and overdue task assignments to the user terminal. Supplementary task assignments carry the target task value, actual task value, and the difference between the target and overdue task values, allowing the user terminal to display that the corresponding procedure entry has a task value deviation. Overdue task assignments carry the deadline and collection time for the execution period, allowing the user terminal to display that the time condition for the corresponding procedure entry has not been met. The task sending submodule selects the receiving user terminal based on the management relationship corresponding to the personnel account or building number in the personnel work record, ensuring that the task prompt returns to the corresponding personnel or building management object.

[0043] The instruction forwarding submodule is connected to the result allocation submodule. The instruction forwarding submodule sends device control instructions to the controller via the enclosure gateway. Each device control instruction carries the device name, enclosure number, and target action information, which is determined by the expected action state. Before sending, the instruction forwarding submodule reads the binding relationship between the enclosure gateway and the enclosure number, and the mapping relationship between the controller and the device name. When the enclosure number matches a enclosure gateway and the device name matches a controller, the instruction forwarding submodule sends the device control instruction to the corresponding enclosure gateway, which then forwards it to the corresponding controller. When the enclosure number cannot match a enclosure gateway, or the device name cannot match a controller, the instruction forwarding submodule generates an instruction forwarding exception record and prevents the device control instruction from entering the controller.

[0044] In one embodiment, the result allocation submodule generates a completion record when the identity consistency result, time period hit result, and numerical value conformance result are all true. When the identity consistency result and time period hit result are true but the numerical value conformance result is false, the result allocation submodule generates a supplementary task. When the identity consistency result is true, the time period hit result is false, and the data collection time is later than the deadline of the execution period, the result allocation submodule generates an overdue task. When the equipment operating status corresponding to the equipment name in the field status data table does not reach the expected action status corresponding to the equipment name in the procedure entry data table, the result allocation submodule generates equipment control instructions to bring the equipment operating status toward the expected action status. The above branches execute according to the procedure conditions satisfying the results and equipment operating status. The completion record is entered into the aquaculture process archive table, the supplementary task and overdue task are entered into the user terminal, and the equipment control instructions are entered into the pen gateway and controller.

[0045] In this embodiment, by configuring corresponding destinations for completion records, supplementary work tasks, overdue work tasks, and equipment control instructions, the result of fulfilling the procedure conditions no longer generates only a single prompt result. Instead, it can output different control objects based on identity conditions, time period conditions, numerical conditions, and equipment status conditions. This allows the breeding process archive, personnel task prompts, and pen equipment control to form a continuous processing relationship under the same procedure item.

[0046] This embodiment also provides a smart management and control cloud method for livestock farming. This method is executed according to the aforementioned smart management and control cloud system for livestock farming and corresponds to the procedure processing module, status acquisition module, condition determination module, and task generation module in the aforementioned system embodiment. During execution, the method receives the livestock farming procedure text entered by the management terminal, extracts the livestock identity category, pen number, execution time period, target operation value, equipment name, expected action status, and record voucher type from the livestock farming procedure text, and generates a procedure entry data table. This step corresponds to the processing procedure of the aforementioned procedure processing module, and the procedure entry data table serves as the procedure-side input for subsequent condition determination.

[0047] The method continues to receive livestock identification data uploaded by ear tag readers, pen number data uploaded by pen gateways, field status data uploaded by sensors, equipment operating status uploaded by controllers, and personnel operation records submitted by user terminals. It then generates a field status data table based on the livestock identification data, pen number data, and data collection time. This step corresponds to the processing procedure of the aforementioned status acquisition module, and the field status data table serves as the field-side input for subsequent condition determination.

[0048] This method continues to read the procedure entry data table and the field status data table, compares the consistency between the livestock identity category and the livestock identity data, compares the execution time period with the collection time, and compares the difference between the target operation value and the actual operation value in the personnel operation record to generate a procedure condition satisfaction result. This step corresponds to the processing procedure of the aforementioned condition determination module, and the procedure condition satisfaction result serves as the basis for determining the subsequent control output.

[0049] This method continues to generate completion records, supplementary work tasks, overdue work tasks, or equipment control instructions based on the fulfillment of procedural conditions. The completion records are written to the aquaculture process archive table, supplementary and overdue work tasks are sent to the user terminal, and equipment control instructions are sent to the controller via the pen gateway. This step corresponds to the processing of the aforementioned task generation module, enabling the method flow to inherit the publicly disclosed data sources, field processing, condition judgment, and output allocation rules in the aforementioned system structure.

[0050] In this embodiment, the method-related embodiment does not change the module boundaries of the aforementioned system embodiment. Each step in the method is executed collaboratively by the corresponding module in the aforementioned system. The procedure entry data table, the field status data table, and the procedure condition satisfaction results have the same meaning in both the system embodiment and the method-related embodiment. By establishing a correspondence between the method steps and system modules, the same set of intelligent livestock farming management logic can be implemented both in a system structure manner and in a method execution sequence manner to explain its data flow and control output process.

[0051] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A cloud-based intelligent management and control system for livestock farming, characterized in that, The system includes: The procedure processing module is used to receive the breeding procedure text entered by the management terminal, extract the livestock identity category, pen number, execution period, target operation value, equipment name, expected action status and record voucher type from the breeding procedure text, and generate a procedure entry data table. The status acquisition module, connected to the procedure processing module, is used to receive livestock identification data uploaded by the ear tag reader, pen number data uploaded by the pen gateway, field status data uploaded by the sensor, equipment operation status uploaded by the controller, and personnel operation records submitted by the user terminal, and to generate a field status data table according to the livestock identification data, pen number data, and collection time. The condition determination module, connected to the status acquisition module, is used to read the procedure entry data table and the on-site status data table, compare the consistency between the livestock identity category and the livestock identity data, compare the range between the execution time period and the collection time, compare the difference between the target operation value and the actual operation value in the personnel operation record, and generate the result that the procedure conditions are met. The task generation module, connected to the condition determination module, is used to generate completion records, supplementary work tasks, overdue work tasks, or equipment control instructions based on the results of fulfilling the procedural conditions, combined with the collection time and equipment operating status in the field status data table, and the deadline time, equipment name, and expected action status of the execution period in the procedural entry data table. The completion records are written into the aquaculture process archive table, the supplementary work tasks and overdue work tasks are sent to the user terminal, and the equipment control instructions are sent to the controller through the pen gateway.

2. The intelligent management and control cloud system for livestock breeding according to claim 1, characterized in that, The procedure processing module includes: The text receiving submodule is configured to receive the aquaculture procedure text entered by the management terminal, read the corresponding entry account, entry time and text version identifier of the aquaculture procedure text, and generate a procedure text receiving record. The field extraction submodule, connected to the text receiving submodule, is configured to locate the livestock identity category, pen number, execution period, target operation value, equipment name, expected action status, and record voucher type from the procedure text receiving record according to the pre-stored field name table, and generate the procedure field extraction results; The entry generation submodule, connected to the field extraction submodule, is configured to write the extracted procedure fields into the procedure entry data table by entry number.

3. The intelligent management and control cloud system for livestock breeding according to claim 2, characterized in that, The field extraction submodule is specifically configured as follows: read the field start identifier and field end identifier corresponding to each field name in the pre-stored field name table, determine the position of the field start identifier in the aquaculture procedure text as the field extraction start point, determine the position of the field end identifier in the aquaculture procedure text as the field extraction end point, extract the field content according to the field extraction start point and field extraction end point, establish a mapping relationship between the extracted field content and the corresponding field name, and generate a field content mapping table; correspondingly, the entry generation submodule is configured to generate a procedure entry data table according to the field content mapping table.

4. The intelligent management and control cloud system for livestock breeding according to claim 1, characterized in that, The status acquisition module includes: The identity receiving submodule is configured to receive livestock identity data uploaded by the ear tag reader, establish a correspondence between the livestock identity data and the receiving time, and generate a livestock identity receiving record; The barracks receiving submodule is connected to the identity receiving submodule and is configured to receive barracks number data uploaded by the barracks gateway, establish a correspondence between the barracks number data and the gateway communication address, and generate barracks number receiving records. The status table submodule, connected to the pen receiving submodule, is configured to receive on-site status data uploaded by sensors, equipment operating status uploaded by controllers, and personnel operation records containing actual operation values ​​submitted by user terminals. It writes livestock identity reception records, pen number reception records, on-site status data, equipment operating status, and personnel operation records into the on-site status data table according to the collection time.

5. The intelligent management and control cloud system for livestock breeding according to claim 4, characterized in that, The specific configuration of the status table submodule is as follows: read the reception time from the livestock identity reception record, the reception time from the pen number reception record, the collection time from the field status data, the reporting time from the equipment operation status, and the operation time from the personnel operation record; compare the maximum interval between each time with the pre-stored synchronization interval threshold; when the maximum interval does not exceed the pre-stored synchronization interval threshold, write the livestock identity reception record, pen number reception record, field status data, equipment operation status, and personnel operation record into the same field status record; when the maximum interval exceeds the pre-stored synchronization interval threshold, generate a status synchronization anomaly record.

6. The intelligent management and control cloud system for livestock breeding according to claim 1, characterized in that, The condition determination module includes: The identity comparison submodule is configured to read the livestock identity category from the procedure entry data table and the livestock identity data from the field status data table, compare the livestock identity category with the livestock identity data for consistency, and generate an identity consistency result. The time period comparison submodule, connected to the identity comparison submodule, is configured to read the execution time period and the collection time, compare the collection time with the execution time period within a range, and generate a time period matching result. The numerical comparison submodule, connected to the time period comparison submodule, is configured to read the target operation value and the actual operation value, calculate the difference between the target operation value and the actual operation value, and generate the numerical matching result. The condition determination module is configured to aggregate the identity consistency result, time period hit result, and numerical compliance result to generate the procedure condition satisfaction result.

7. The intelligent management and control cloud system for livestock breeding according to claim 6, characterized in that, The specific configuration of the numerical comparison submodule is as follows: read the allowable deviation value corresponding to the target operation value in the pre-stored allowable deviation table, subtract the target operation value from the actual operation value and take the absolute value to obtain the operation value difference, compare the operation value difference with the allowable deviation value, generate a numerical compliance result when the operation value difference does not exceed the allowable deviation value, and generate a numerical deviation result when the operation value difference exceeds the allowable deviation value.

8. The intelligent management and control cloud system for livestock breeding according to claim 1, characterized in that, The task generation module includes: The result allocation submodule is configured to read the procedure condition fulfillment result, and based on the identity consistency result, time period hit result, and value compliance result in the procedure condition fulfillment result, combined with the collection time and equipment operating status in the field status data table, and the end time, equipment name, and expected action status of the execution period in the procedure entry data table, determine at least one control output among the completion record, supplementary work task, overdue work task, and equipment control instruction. The record writing submodule, connected to the result allocation submodule, is configured to write the completion record to the aquaculture process archive table. The task sending submodule, connected to the result distribution submodule, is configured to send supplementary job tasks and overdue job tasks to the user terminal. The instruction forwarding submodule, connected to the result allocation submodule, is configured to send device control instructions to the controller via the gatehouse gateway.

9. The intelligent management and control cloud system for livestock breeding according to claim 8, characterized in that, The result allocation submodule is specifically configured as follows: when the identity consistency result, time period hit result, and numerical conformity result are all true, a completion record is generated; when the identity consistency result and time period hit result are true but the numerical conformity result is false, a supplementary job task is generated; when the identity consistency result is true, the time period hit result is false, and the collection time is later than the deadline of the execution time period, an overdue job task is generated. When the operating status of the equipment corresponding to the equipment name in the field status data table does not reach the expected action status corresponding to the equipment name in the procedure entry data table, a device control command is generated to make the operating status of the equipment tend to the expected action status.

10. A cloud-based intelligent management and control method for livestock farming, characterized in that, The execution of the intelligent management and control cloud system for livestock breeding according to any one of claims 1-9 includes the following steps: S1: Receive the breeding procedure text entered by the management terminal, extract the livestock identity category, pen number, execution time period, target operation value, equipment name, expected action status and record voucher type from the breeding procedure text, and generate a procedure entry data table; S2: Receive livestock identification data uploaded by ear tag readers, pen number data uploaded by pen gateways, field status data uploaded by sensors, equipment operation status uploaded by controllers, and personnel operation records submitted by user terminals, and generate a field status data table according to livestock identification data, pen number data, and collection time. S3: Read the procedure entry data table and the field status data table, compare the consistency between the livestock identity category and the livestock identity data, compare the execution time period with the collection time, compare the difference between the target operation value and the actual operation value in the personnel operation record, and generate the procedure condition satisfaction result. S4: Based on the results of meeting the procedural conditions, and combined with the collection time and equipment operating status in the field status data table, as well as the deadline, equipment name, and expected action status of the execution period in the procedural item data table, generate completion records, supplementary work tasks, overdue work tasks, or equipment control instructions. Write the completion records into the aquaculture process archive table, send the supplementary work tasks and overdue work tasks to the user terminal, and send the equipment control instructions to the controller through the pen gateway.

Images