Environment-friendly declaration space intelligent filling method and system

Abstract

The application discloses an environmental protection declaration space intelligent filling method and system, the method comprises the following steps: collecting the page text, control attribute, container level, control event, visible state and route state of the target environmental protection declaration webpage, constructing the page context relationship and generating the field role relationship; analyzing the layout text, table unit, position and unit source of the detection report, generating the monitoring record, monitoring result matrix and report evidence relationship; generating the backfill mapping relationship and writing instruction according to the above, and writing the to-be-backfilled control through script injection; after writing, the webpage is collected again, and the display data, internal data, event response and verification prompt are read, the writing verification relationship is generated, and the backfill mapping relationship and writing instruction are reconstructed when the field role changes. The application realizes accurate space backfilling and traceable verification of environmental protection declaration data by binding the page context reconstruction and the report evidence.

Description

Technical Field

[0001] This application relates to the field of data processing technology, and in particular to a method and system for remote intelligent filling of environmental protection declarations. Background Technology

[0002] Current environmental protection reporting typically relies on manual data entry, API integration, fixed scripts, or general RPA tools for data migration and form completion. However, in actual environmental protection operations, systems for discharge permit implementation reports, pollutant monitoring data reporting, and solid and hazardous waste declarations come from diverse sources. Some outdated systems, locally customized systems, and third-party closed-source systems do not offer API, WebService, or direct database connection permissions, and often lack the conditions for source code modification. This results in high costs, long lead times, and difficulties in implementing traditional API integration methods.

[0003] Meanwhile, environmental protection reporting involves numerous fields and strict business constraints, requiring the simultaneous association of enterprise codes, monitoring cycles, pollutant categories, discharge outlet information, and test report data. Manual repetitive data entry can easily lead to errors and omissions, affecting the accuracy of the reported data and environmental compliance.

[0004] Existing automatic data entry methods typically focus on locating form fields and inputting values, easily overlooking two deeper issues: First, many field names on environmental declaration pages are identical or similar, such as "monitoring value," "monitoring time," and "emission concentration." Their true meaning changes with the discharge outlet, pollutant, reporting cycle, pop-up level, or dynamic page refreshes. If data is entered solely based on field names, DOM paths, or historical scripts, it's easy to write data into controls that appear correct but have incorrect business context. Second, after OCR or structured parsing of the test report, if only the result values ​​are extracted without binding the original PDF page numbers, text block positions, unit conversions, and verification status, the entered data is easily disconnected from the original evidence, making it difficult for users to confirm whether the entered data corresponds to the correct monitoring item and discharge outlet. Summary of the Invention

[0005] To address the aforementioned problems, embodiments of the present invention provide a remote intelligent reporting method for environmental protection declarations, the method comprising:

[0006] Collect the page text, control attributes, container hierarchy, control events, visibility state, and routing state of the target environmental protection declaration webpage to construct the first page context relationship;

[0007] Based on the context of the first page, extract the core parameters of the application, associate them with the control to be filled in, and generate the first field role relationship;

[0008] The system analyzes the layout text, table cells, text block positions, page number positions, and unit sources of the test report to generate monitoring records, a monitoring result matrix, and report evidence relationships.

[0009] A first backfill mapping relationship is generated based on the role relationship in the first field, the monitoring result matrix, and the report evidence relationship;

[0010] Based on the first backfill mapping relationship, a first write instruction is generated, and the monitoring record is written to the control to be backfilled through script injection;

[0011] After writing, the target environmental protection declaration webpage is collected to generate the second page context relationship and the second field role relationship;

[0012] Read the display data, internal data, event responses, and verification prompts of the control to be filled, and generate a write verification relationship;

[0013] A reconstruction trigger relationship is generated based on the second field role relationship, the first field role relationship, and the write verification relationship; when the reconstruction trigger relationship points to the control to be backfilled, a second backfill mapping relationship is generated based on the second field role relationship and the report evidence relationship, and a second write instruction is generated based on the second backfill mapping relationship.

[0014] Furthermore, both the first page context relationship and the second page context relationship include page ownership relationship, control response relationship and page state relationship; the page ownership relationship is formed by the correspondence between page text and container hierarchy, the control response relationship is formed by the correspondence between control attributes and control events, and the page state relationship is formed by the correspondence between visible state and routing state.

[0015] Furthermore, the method for generating the first field role relationship and the second field role relationship includes: determining the application business boundary where the control to be filled is located based on the page affiliation relationship, determining the writing triggering method of the control to be filled based on the control response relationship, determining the page occupancy status of the control to be filled based on the page status relationship, and establishing a field role correspondence relationship between the application business boundary, the writing triggering method, and the page occupancy status and the application core parameters.

[0016] Furthermore, the method for extracting the core parameters of the application includes: extracting the applicant identifier, application period, pollutant attribution, and discharge outlet attribution from the first page context relationship, and writing the applicant identifier, application period, pollutant attribution, and discharge outlet attribution into the field role correspondence relationship; re-extracting the applicant identifier, application period, pollutant attribution, and discharge outlet attribution from the second page context relationship, and using them to generate the second field role relationship.

[0017] Furthermore, the method for generating the report evidence relationship includes: generating the monitoring record based on the page text and the table unit, generating the report positioning relationship based on the text block position and the page number position, generating the unit affiliation relationship based on the unit source, and writing the monitoring record, the report positioning relationship and the unit affiliation relationship into the monitoring result matrix.

[0018] Furthermore, both the first backfill mapping relationship and the second backfill mapping relationship include an attribution matching relationship, a value constraint relationship, and a writing order relationship; the attribution matching relationship is formed by the correspondence between the corresponding field role relationship and the monitoring record, the value constraint relationship is formed by the correspondence between the corresponding field role relationship and the unit attribution relationship, and the writing order relationship is formed by the correspondence between the corresponding field role relationship and the report positioning relationship.

[0019] Furthermore, the method for generating the first write instruction and the second write instruction includes: determining the control to be backfilled based on the attribution matching relationship, determining the write value based on the value constraint relationship, determining the control event triggering order based on the write order relationship, and combining the control to be backfilled, the write value, and the control event triggering order into a corresponding write instruction.

[0020] Further, the method for generating the write verification relationship and the reconstruction trigger relationship includes: establishing a display verification relationship between the display data and the write value; establishing an internal verification relationship between the internal data and the write value; establishing an event verification relationship between the event response and the control event triggering order; establishing a page verification relationship between the verification prompt and the second field role relationship; and forming the write verification relationship by the display verification relationship, the internal verification relationship, the event verification relationship, and the page verification relationship; generating a role replacement flag by a substitution judgment between the second field role relationship and the first field role relationship; generating a write deviation flag by a deviation judgment between the write verification relationship and the first backfill mapping relationship; generating an evidence retention flag by a retention judgment between the report evidence relationship and the second field role relationship; writing the role replacement flag, the write deviation flag, and the evidence retention flag into the reconstruction trigger relationship; and generating the second backfill mapping relationship based on the reconstruction trigger relationship.

[0021] Furthermore, an environmental protection declaration remote intelligent filling method further includes: establishing a linkage status record after executing the first write instruction, and collecting candidate page context relationships; continuing to collect when the candidate page context relationship is a transitional state relationship, and generating a second field role relationship, control inheritance relationship and evidence inheritance relationship when a stable page context relationship is formed, and generating a second backfill mapping relationship and a second write instruction accordingly.

[0022] An environmental protection declaration system with remote intelligent filling, the system includes:

[0023] Page awareness module: Collects page text, control attributes, container hierarchy, control events, visibility state, and routing state of the target environmental protection declaration webpage to construct the first page context relationship;

[0024] Role generation module: Extracts the core parameters of the application based on the context of the first page, associates them with the control to be filled in, and generates the first field role relationship;

[0025] Report Evidence Collection Module: Analyzes the layout text, table cells, text block positions, page number positions, and unit sources of the test report to generate monitoring records, monitoring result matrices, and report evidence relationships;

[0026] Backfill mapping module: Generates a first backfill mapping relationship based on the first field role relationship, the monitoring result matrix, and the report evidence relationship;

[0027] Script writing module: Generates a first writing instruction based on the first backfill mapping relationship, and writes the monitoring record into the control to be backfilled through script injection;

[0028] Post-write perception module: After writing, collect the target environmental protection declaration webpage, generate the second page context relationship and the second field role relationship;

[0029] Write verification module: Reads the display data, internal data, event responses, and verification prompts of the control to be filled, and generates write verification relationships;

[0030] The reconstruction module generates a reconstruction trigger relationship based on the second field role relationship, the first field role relationship, and the write verification relationship. When the reconstruction trigger relationship points to the control to be backfilled, a second backfill mapping relationship is generated based on the second field role relationship and the report evidence relationship, and a second write instruction is generated based on the second backfill mapping relationship.

[0031] The technical effects and advantages of the remote intelligent filing method for environmental protection declaration provided by this invention are as follows:

[0032] This invention achieves accurate, remote backfilling and traceable verification of environmental protection declaration data by reconstructing page context and binding it with report evidence. The invention collects page text, control attributes, container hierarchy, control events, visibility status, and routing status to form a page context relationship. Based on this, it generates field role relationships, ensuring that the business meaning of the control to be backfilled is jointly determined by the declaring entity, declaration period, pollutant attribution, discharge outlet attribution, and page status. This reduces the risk of incorrect filling caused by duplicate fields, pop-up reuse, and page refreshes. It also establishes report evidence relationships by linking monitoring records, table cells, text block positions, page number positions, and unit sources in the testing report, ensuring that the backfilled values ​​correspond to the original report positions and unit attributions, facilitating traceability and verification. After writing, the page is re-collected and a second field role relationship is generated. By writing the verification relationship and reconstructing the trigger relationship, the backfilling mapping relationship is corrected, improving the accuracy, stability, and environmental protection declaration compliance in scenarios without interface or source code modification. Attached Figure Description

[0033] Figure 1 This is a flowchart of an environmental protection declaration method using remote intelligent filling, as shown in Example 1.

[0034] Figure 2 This is a flowchart of the post-write linkage stable state identification and evidence inheritance reconstruction method in Example 2;

[0035] Figure 3 This is a connection diagram of an environmental protection declaration remote intelligent filling system in Example 3. Detailed Implementation

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

[0037] Please see Figure 1 As shown, an embodiment of the present invention provides a remote intelligent filing method for environmental protection declarations, the method comprising:

[0038] S1. Collect the page text, control attributes, container hierarchy, control events, visibility state, and routing state of the target environmental protection declaration webpage to construct the first page context relationship;

[0039] S2. Extract the core parameters of the application based on the context of the first page, associate them with the control to be filled in, and generate the first field role relationship;

[0040] S3. Analyze the layout text, table cells, text block positions, page number positions, and unit sources of the test report to generate monitoring records, monitoring result matrix, and report evidence relationships;

[0041] S4. Generate a first backfill mapping relationship based on the first field role relationship, the monitoring result matrix, and the report evidence relationship;

[0042] S5. Generate a first write instruction based on the first backfill mapping relationship, and write the monitoring record into the control to be backfilled through script injection;

[0043] S6. After writing, collect the target environmental protection declaration webpage and generate the second page context relationship and the second field role relationship;

[0044] S7. Read the display data, internal data, event response, and verification prompt of the control to be filled, and generate a write verification relationship;

[0045] S8. Generate a reconstruction trigger relationship based on the second field role relationship, the first field role relationship, and the write verification relationship; when the reconstruction trigger relationship points to the control to be backfilled, generate a second backfill mapping relationship based on the second field role relationship and the report evidence relationship, and generate a second write instruction based on the second backfill mapping relationship.

[0046] In this embodiment, the first page context relationship is formed before the target environmental protection declaration webpage is written, and the second page context relationship is re-formed after the target environmental protection declaration webpage is written. The first page context relationship and the second page context relationship adopt the same data organization method and are both used to represent the correspondence between the declaration content, form controls and page status in the current page.

[0047] Specifically, after the target environmental protection declaration webpage is loaded, the system first collects the page text and container hierarchy. The page text is the text content on the webpage related to environmental protection declaration business, and the container hierarchy is the nesting relationship between the page area, tabs, pop-ups, table rows and columns, and form groups where the text content is located. The system attaches the page text to the corresponding container hierarchy to form a page ownership relationship. Through this page ownership relationship, it can be determined that a certain field is located within the business boundaries such as the enterprise information area, discharge outlet information area, pollutant monitoring area, and execution report filling area, rather than judging the meaning of the field solely based on the field name.

[0048] After establishing the page ownership relationship, the system collects the control attributes and control events in the target environmental protection declaration webpage. The control attributes are the name, type, value range, placeholder hint, read-only flag, required flag, and current value status of the control to be filled in. The control events are the front-end response behaviors corresponding to the control to be filled in when it is written, selected, out of focus, refreshed, or verified. The system establishes a correspondence between the control attributes and control events to form a control response relationship. This control response relationship is used to determine the response path that needs to be triggered when the control to be filled in is written, so that subsequent writing instructions can be executed according to the original page interaction mechanism.

[0049] Simultaneously, the system collects visibility status and routing status. Visibility status is used to characterize the display status of page areas, pop-ups, table rows, and control bodies on the current page. Routing status is used to characterize the application step, tab path, pop-up level, and page view position of the current page. The system establishes a correspondence between visibility status and routing status to form a page status relationship. This page status relationship is used to distinguish the business identity of controls with the same name under different application steps, different pop-up levels, and different tab views.

[0050] After the page ownership relationship, control response relationship, and page state relationship are generated, the system uses the control to be filled as an index and writes the page text, container level, control attributes, control events, visibility state, and routing state associated with that control into the same context record, thereby constructing the first page context relationship. After writing, the system collects the target environmental declaration webpage again in the same way to construct the second page context relationship. If the control to be filled corresponding to the first page context relationship is located in the "COD monitoring value" field under the "Wastewater Discharge" tab, and after writing, the page jumps to the "Waste Gas Discharge" tab and a "monitoring value" field with the same name appears, then the page ownership relationship and page state relationship in the second page context relationship change, and the second field role relationship can be generated accordingly.

[0051] In this embodiment, after generating the first page context relationship, the system continues to generate the first field role relationship based on the first page context relationship; after performing the write operation, the system regenerates the second page context relationship and generates the second field role relationship according to the same processing path. The first field role relationship is used to characterize the business identity of the control to be backfilled in the current environmental protection declaration webpage before the write operation, and the second field role relationship is used to characterize the business identity after the state of the page where the control to be backfilled is located changes after the write operation.

[0052] Specifically, the system first reads the page ownership relationship from the first page context. The page ownership relationship already stores the correspondence between page text and container level. Starting from the container level where the control to be filled is located, the system traces back to its parent page area, tab area, pop-up area, and form group. The page text within the same business level as the control is taken as the business boundary text. The system then matches the business boundary text with the core parameters of the declaration to determine the declaration business boundary where the control to be filled is located. The declaration business boundary refers to which type of reporting area in the environmental declaration webpage the control to be filled belongs to, such as the enterprise basic information area, discharge outlet information area, pollutant monitoring area, execution report reporting area, etc. Its determination does not depend solely on the control name, but is jointly limited by the page text and container level.

[0053] After determining the boundaries of the declared business, the system reads the control response relationship from the context of the first page. The control response relationship stores the correspondence between control attributes and control events. Based on the control type, writable state, option source, required field identifier and its corresponding input event, selection event, defocus event and linked refresh event of the control to be filled, the system determines the writing triggering method of the control to be filled. The writing triggering method describes the front-end interaction path that the page should follow to accept the written data. For example, the input box needs to complete the assignment and trigger the input event and defocus event, and the drop-down control needs to complete the option selection and trigger the change event. The event triggering order in subsequent writing instructions remains corresponding to this writing triggering method.

[0054] Subsequently, the system reads the page state relationship from the first page context relationship. The page state relationship stores the correspondence between the visible state and the routing state. The system determines the page occupancy status of the control to be filled based on whether it is currently in the visible page area, whether it is in the current tab path, whether it is in the pop-up layer, and whether it is occupied by a hidden control with the same name. The page occupancy status is used to distinguish the actual business identity of the control with the same name in different page views, and avoid mistaking the control located outside the current business boundary as the control to be filled.

[0055] After obtaining the business boundary of the declaration, the writing trigger method, and the page occupancy status, the system establishes a field role correspondence relationship between the three and the core parameters of the declaration. The core parameters of the declaration include the declaration subject identifier, declaration period, pollutant attribution, and discharge outlet attribution extracted from the context of the first page. The field role correspondence records the business attribution between the control to be filled and the core parameters of the declaration, and also records the writing trigger method and page occupancy status of the control to be filled, thus forming the first field role relationship.

[0056] After the write operation is completed, the system collects the target environmental declaration webpage again to form a second page context relationship. Based on the second page context relationship, it redefines the declaration business boundary, write triggering method, and page occupancy status, thereby generating the second field role relationship. For example, before the write operation, the control to be backfilled is located under the "Wastewater Discharge Outlet" tab and corresponds to "COD Monitoring Value". After the write operation, the page is refreshed and switched to another discharge outlet tab. The page still has a "Monitoring Value" control with the same name. At this time, the second field role relationship records the business identity of the control with the same name after the write operation by redefining the page ownership relationship and page status relationship. This provides a basis for the subsequent reconstruction of the triggering relationship and the generation of the second backfill mapping relationship.

[0057] In this embodiment, the core parameters for declaration are used to define the object to which the control to be filled in belongs in the environmental protection declaration business. The core parameters for declaration include at least the declaration entity identifier, declaration period, pollutant attribution, and discharge outlet attribution. The declaration entity identifier is used to identify the polluting unit, declaration unit, or testing commissioning unit corresponding to the current filling page; the declaration period is used to identify the declaration time range corresponding to the current filling page; the pollutant attribution is used to identify the monitoring item category corresponding to the control to be filled in; and the discharge outlet attribution is used to identify the discharge outlet, monitoring point, or sampling point corresponding to the control to be filled in.

[0058] When the system extracts the core parameters for declaration from the context of the first page, it does not rely solely on a single field name for identification. Instead, it reads the page ownership relationship, control response relationship, and page status relationship layer by layer according to the location of the control to be filled. Specifically, the system first determines the page area, tab area, pop-up area, and form group where the control to be filled is located based on the page ownership relationship, and reads the page text related to the declaration subject, declaration period, pollutants, and discharge outlets from the above areas. Then, it reads the control attributes, current values, option content, and filling prompts adjacent to the page text based on the control response relationship. Subsequently, it determines whether the above page text and controls are within the currently visible page, current routing path, and current business boundary based on the page status relationship. After the above processing, the system determines the text and control values ​​that are within the same business boundary and have a page ownership relationship with the control to be filled as the source of the core parameters for declaration.

[0059] When generating the first field role relationship, the system will write the declaration subject identifier, declaration period, pollutant attribution and discharge outlet attribution obtained from the first page context relationship into the field role correspondence relationship. The field role correspondence relationship is used to record the business attribution between the control to be filled and the core declaration parameters, and at the same time, it will take into account the declaration business boundary, writing trigger method and page occupancy status. Therefore, the role of the control to be filled is not determined by the control name alone, but is jointly limited by the core declaration parameters, page attribution relationship, control response relationship and page status relationship.

[0060] After the first write instruction is executed, the system re-collects the target environmental protection declaration webpage to form a second page context relationship. Following the same extraction path as the first page context relationship, it re-obtains the declaration entity identifier, declaration period, pollutant attribution, and discharge outlet attribution. The re-obtained core declaration parameters are used to generate the second field role relationship. If the control to be backfilled was located in the "COD monitoring value" reporting area of ​​"wastewater discharge outlet DW001" before writing, and the page switches to another discharge outlet area due to the linked refresh after writing, the system re-reads the visibility status of the current tab, the current discharge outlet text, and the control with the same name through the second page context relationship, thereby generating the second field role relationship corresponding to the page status after writing. This second field role relationship continues to participate in the generation of the reconstruction trigger relationship and the second backfill mapping relationship.

[0061] In this embodiment, after obtaining the test report, the system first performs page-level parsing to obtain the page text, table cells, text block positions, page number positions, and unit sources. The page text refers to the readable text content on the test report page, including the report title, test item name, monitoring point name, test time, test results, and explanatory text. The table cell refers to the unit area in the test report that carries monitoring data in a row and column format, and it maintains a corresponding relationship with the table header, row title, and column title. When parsing, the system does not directly use a single identification value as the data to be filled in, but first determines the attribution relationship between the page text and the table cells, and then extracts the monitoring item, monitoring value, monitoring time, monitoring point, and testing method from the attribution relationship to form a monitoring record.

[0062] The system further generates a report positioning relationship based on the text block position and page number position. The text block position is used to record the boundary of the text block of the monitoring record in the detection report page and its relative position with adjacent text and adjacent table cells; the page number position is used to record the report page and the area within the page where the monitoring record is located. The report positioning relationship is not used for display alone, but is bound to the monitoring record to indicate that the monitoring record comes from the specific page position in the detection report. Thus, when generating the first backfill mapping relationship in the future, the system can retain the correspondence between the monitoring record and the original report source.

[0063] The system also generates unit attribution relationships based on the unit source. The unit source refers to the location of the unit corresponding to the monitoring value in the test report, including the unit in the table header, the unit attached to the project name, the unit in the result column, and the unit in the report description text. The system establishes a link between the unit source and the corresponding monitoring record to form a unit attribution relationship. When there are similar monitoring items in the same test report but the unit labeling positions are inconsistent, the system uses the unit in the same table cell area, the same row and column header area, or the adjacent area of ​​the same text block as the unit source of the monitoring record.

[0064] After forming monitoring records, report location relationships, and unit affiliation relationships, the system writes these three into the monitoring result matrix. The monitoring result matrix is ​​used to store the structured results after parsing the test report. Each matrix record is associated with at least one monitoring record, one report location relationship, and one unit affiliation relationship. For example, when the "COD" monitoring result of "Wastewater Discharge Outlet DW001" in the test report is located in a certain test result table, the system forms a monitoring record with the pollutant item, monitoring value, monitoring point, and testing time, forms a report location relationship with its page number and table cell position, and forms a unit affiliation relationship with the unit in the header of the result table. The above content is then written into the same monitoring result matrix record. This monitoring result matrix then participates in the generation of the first backfill mapping relationship together with the first field role relationship.

[0065] In this embodiment, after generating the first field role relationship, the monitoring result matrix, and the report evidence relationship, the system establishes a first backfill mapping relationship. The first backfill mapping relationship is used to limit the corresponding path between the control to be backfilled before writing and the monitoring record in the detection report. After writing, when the system generates the second field role relationship based on the second page context relationship, it establishes a second backfill mapping relationship in the same mapping formation method, so that the page state after writing can continue to inherit the original report evidence relationship.

[0066] Both the first and second backfill mapping relationships include attribution matching relationships, value constraint relationships, and writing order relationships. For the first backfill mapping relationship, the corresponding field role relationship is the first field role relationship; for the second backfill mapping relationship, the corresponding field role relationship is the second field role relationship. Thus, the field role relationship participates in the mapping establishment both before and after writing, rather than being used as a separate field label.

[0067] Specifically, the system first reads the declaration business boundary, core declaration parameters, page occupancy status, and write triggering method of the control to be filled based on the corresponding field role relationship. Then, it reads the monitoring records from the monitoring result matrix. The monitoring records include the monitoring items, monitoring values, monitoring time, monitoring points, and testing methods obtained from the test report. The system establishes an association between the declaration subject identifier, declaration period, pollutant attribution, and discharge outlet attribution in the field role relationship and the corresponding content in the monitoring records item by item to form an attribution matching relationship. This attribution matching relationship is used to determine whether a certain monitoring record belongs to the environmental protection declaration object pointed to by the current control to be filled.

[0068] After the attribution matching relationship is formed, the system forms a value constraint relationship based on the corresponding field role relationship and unit attribution relationship. The unit attribution relationship comes from the report evidence relationship and is used to record the unit in the monitoring record from the unit identifier in the header, result column, adjacent text of the project name and description text of the test report. The system establishes a correspondence between the field type, filling prompt, option content and page validation requirements of the control to be filled and the unit source and numerical expression method of the monitoring record to determine the value form of the written value. Therefore, the written value is not extracted from the test report alone, but is formed after being jointly limited by the field role relationship and the unit attribution relationship.

[0069] Subsequently, the system establishes a writing order relationship based on the corresponding field role relationship and report positioning relationship. The report positioning relationship originates from the text block position and page number position, and is used to record the position of the monitoring record within the page of the original test report and its relationship with adjacent text and table cells. The system establishes a correspondence between the report positioning relationship and the writing triggering method of the control to be filled, and determines the writing order and event triggering order of the monitoring record entering the page control. For controls with page linkage, the system first determines the control used to limit the business boundary, and then determines the control that carries the monitoring value, so that the writing order relationship is consistent with the original page interaction path of the target environmental protection declaration webpage.

[0070] For example: The first field, role relationship, indicates that the control to be backfilled belongs to the COD monitoring value reporting area of ​​wastewater discharge outlet DW001. There are monitoring records in the monitoring result matrix corresponding to the discharge outlet and the pollutant item. The report evidence relationship records the page number, table cell position and unit source of the monitoring record. Based on this, the system forms the attribution matching relationship, value constraint relationship and writing order relationship, and combines the three into the first backfill mapping relationship. If the page status changes after writing, the system regenerates the above three types of relationships according to the second field, role relationship, to form the second backfill mapping relationship.

[0071] In this embodiment, after forming the first backfill mapping relationship, the system generates a first write instruction based on the attribution matching relationship, value constraint relationship and writing order relationship therein. After the writing is completed, the system generates a second write instruction based on the second backfill mapping relationship. The first write instruction and the second write instruction adopt the same organization method and are both used to instruct the front-end script to complete the control positioning, value writing and event triggering in the target environmental protection declaration webpage.

[0072] Specifically, the system first determines the controls to be backfilled based on the attribution matching relationship. The attribution matching relationship stores the correspondence between the field role relationship and the monitoring record. The system reads the declaration subject identifier, declaration period, pollutant attribution, and discharge outlet attribution from this correspondence relationship, and checks them against the declaration business boundary where the control to be backfilled is located. Controls that are in the same business boundary after verification are identified as controls to be backfilled. This processing method does not use the control name as the positioning basis, but determines the identity of the control by the business attribution recorded in the field role relationship, so that controls with the same name can be distinguished.

[0073] After identifying the control to be filled, the system determines the write value based on the value constraint relationship. The value constraint relationship stores the correspondence between field role relationships and unit affiliation relationships. The system reads the monitoring values ​​from the monitoring records and combines them with the unit source, control type, filling prompts, and page validation requirements to form the write value. The write value is the data to be written before entering the target environmental protection declaration webpage. It maintains a source association with the monitoring records and is consistent with the unit affiliation relationship. For input boxes, the write value enters the control in text form; for drop-down controls, the write value first establishes a correspondence with the option content, and then selects the option that matches it; for date controls, the write value enters the control according to the date expression acceptable to the page.

[0074] Subsequently, the system determines the triggering order of control events based on the writing order relationship. The writing order relationship stores the correspondence between field role relationships and report positioning relationships, and accepts the writing triggering method of the backfill control. The system determines the execution order of assignment, selection, change, defocus, linkage refresh and verification triggers according to the original interaction path of the target environmental protection declaration webpage, so that the page state after writing can be received by the webpage's own event mechanism. For pages with linkage relationships, the system first triggers the control events used to limit the boundaries of the declaration business, and then triggers the control events carrying the monitoring values.

[0075] The system combines the control to be backfilled, the written value, and the order of control event triggering into a corresponding write instruction. This write instruction records the control addressing information, the data to be written, the event triggering path, and the source relationship corresponding to the monitoring record. For example, when the attribution matching relationship points to the "COD monitoring value" control of "wastewater discharge outlet DW001", the value constraint relationship points to the corresponding monitoring record and its unit source, and the writing order relationship points to the page interaction path of first selecting the discharge outlet and then writing the monitoring value, the system generates the first write instruction accordingly. If the page switching after writing causes the second backfill mapping relationship to be re-formed, the system generates the second write instruction in the same way.

[0076] In this embodiment, after the first write instruction is executed, the system generates a write verification relationship based on the control to be filled, the write value, and the control event triggering order recorded in the first write instruction. The write verification relationship is used to record the correspondence between the page display status, control submission status, front-end event response status, and page business verification status after the write value enters the target environmental protection declaration webpage.

[0077] Specifically, the system first reads the display data of the controls to be filled in on the page. The display data refers to the content of the controls displayed to the user on the target environmental protection declaration webpage, including the text displayed in the input box, the selected content of the drop-down control, the content displayed in the date control, and the content displayed in the table cell. The system establishes a display verification relationship between the display data and the written value to characterize the correspondence between the content displayed on the page and the data written this time.

[0078] Subsequently, the system reads the internal data of the control to be filled in. The internal data refers to the value state of the control used for submission in the page runtime environment, including control value, selected item identifier, hidden submission value, and form submission value. The system establishes an internal validation relationship between the internal data and the written value to characterize the connection between the content displayed on the page and the actual submitted content, avoiding the situation where only the visible text on the page changes but the submitted value is not synchronized.

[0079] After obtaining the internal data, the system reads the event responses of the control to be backfilled during the writing process. The event response refers to the front-end response results formed by the control to be backfilled during the process of assignment, selection, change, defocusing, linkage refresh and page verification triggering. The system establishes an event verification relationship between the event response and the control event triggering order to characterize whether the event path required by the first write instruction has been received and executed by the target environmental protection declaration webpage.

[0080] The system further reads the verification prompts generated by the target environmental protection declaration webpage. The verification prompts refer to the prompt information generated by the page for field format, mandatory status, business affiliation, unit expression, and submission conditions. The system establishes a page verification relationship with the verification prompts and the role relationship of the second field. The role relationship of the second field is generated by the second page context relationship re-collected after writing and is used to represent the business identity of the control to be filled in after writing. Therefore, the page verification relationship is not only used to record whether the page accepts the written value, but also to record whether the declaration business boundary, pollutant affiliation, discharge outlet affiliation, and declaration cycle pointed to by the verification prompt correspond to the role relationship of the second field.

[0081] The system writes the display verification relationship, internal verification relationship, event verification relationship, and page verification relationship into the same write verification relationship. For example, after the first write instruction writes the COD monitoring value of wastewater outlet DW001 into the corresponding control, the system reads the page display value, control submission value, input event response, and page verification prompt respectively, and establishes a correspondence between the above content and the write value, the control event triggering order, and the role relationship of the second field, thereby forming a write verification relationship. This write verification relationship then participates in the generation of the reconstruction trigger relationship.

[0082] In one implementation, to ensure that the formation process of the reconstruction trigger relationship has a defined data processing path, the system uses the control to be backfilled as an index to perform relationship quantification processing on the first field role relationship, the second field role relationship, the write verification relationship, and the report evidence relationship, and generates the reconstruction trigger value corresponding to the control to be backfilled according to the following formula:

[0083] ;

[0084] ;

[0085] ;

[0086] ;

[0087] In the formula, Indicates the first There are several fields to be filled in, such as "monitoring value", "emission concentration", and "monitoring time". express Before writing The role relationship field is derived from the first role relationship field generated from the context relationship of the first page. Represents the first in a certain type of relation The comparison dimensions, such as the role relationship field, can include dimensions like the reporting entity, reporting period, pollutant attribution, discharge outlet attribution, and page status. Show The first time after writing Each field represents a role / relationship item. This represents a set of comparison dimensions for the role relationship of fields. It is used to calculate whether the business identity of a field has changed before and after writing. For example, if the control originally belonged to "wastewater discharge outlet COD monitoring value", after writing and refreshing the page, it becomes the same "monitoring value" under another discharge outlet. This represents the set of comparison dimensions for the write verification relationship. It is used to determine whether the actual write result is consistent with the first backfill mapping relationship, such as displayed data, internal data, event response, verification prompts, etc. This represents the set of comparison dimensions for the relationship of evidence in the report. It is used to determine whether the current field role can still be supported by the original evidence in the detection report, such as monitoring records, report page number positions, text block positions, unit sources, table cell positions, etc. , , These represent the adjustment coefficients for the three types of deviations, where... Used for field role drift detection Used for writing verification deviation judgment. Used to report evidence and maintain judgment; This represents the evidence preservation judgment function, used to determine the relationship between reported and presented evidence. Relationship with the second field's role Whether it still matches, the larger the value, the stronger the evidence supporting the current field role; the smaller the value, the weaker the evidence. This indicates that the reported evidence remains biased; This represents a difference judgment function used to determine whether two relation items are consistent. It can be set to take the smaller value when consistent and the larger value when inconsistent; it can also output a normalized difference value based on the degree of similarity, which is used to compare the degree of difference between two relation items. Indicates a control to be filled. The field role drift deviation is compared. and Determine whether the business identity of the control has changed before and after the write operation; Indicates a control to be filled. The first one formed after writing Write a validation relationship item, such as displayed data, internal data, event response, page validation prompts, etc.; Indicates a control to be filled. The first backfill mapping relationship Each expected mapping item, such as expected write value, expected control event triggering order, expected value constraints, etc. Indicates a control to be filled. The write verification deviation is determined by comparing the actual verification relationship after the write operation. Expected items in the mapping relationship with the first backfill It determines whether there are write failures, events not triggered, page validation errors, or other issues. Indicates a control to be filled. The comprehensive reconstruction trigger value.

[0088] In one implementation, after the system forms the second field role relationship and the write verification relationship, it generates a reconstruction trigger relationship. The reconstruction trigger relationship is used to record the connection status between the page business identity, the write result and the report evidence after the write, and to determine whether it is necessary to regenerate the second backfill mapping relationship with the page status after the write.

[0089] Specifically, the system first performs a replacement judgment between the second field role relationship and the first field role relationship. The replacement judgment does not compare whether the control names are the same, but compares the correspondence between the two in terms of the declared business boundaries, declared core parameters, page occupancy status and write triggering method. If the tab, pop-up level, discharge outlet affiliation, pollutant affiliation or control event path of the control to be filled changes after writing, the system writes the change into the role replacement flag. The role replacement flag is used to indicate whether the business identity of the control to be filled has been replaced relative to before writing.

[0090] The system then performs a deviation judgment between the write verification relationship and the first backfill mapping relationship. The first backfill mapping relationship includes the attribution matching relationship, the value constraint relationship, and the write order relationship. The write verification relationship includes the display verification relationship, the internal verification relationship, the event verification relationship, and the page verification relationship. The system maps the displayed data and internal data to the write values ​​in the first backfill mapping relationship, maps the event responses to the control event triggering order in the first backfill mapping relationship, and maps the verification prompts to the field roles pointed to by the first backfill mapping relationship. If the business identity reflected in the page display content, control submission content, event execution path, and page prompts is inconsistent with the first backfill mapping relationship, the system generates a write deviation mark. The write deviation mark is used to characterize the applicability of the first backfill mapping relationship in the page state after writing.

[0091] The system will also maintain the report evidence relationship with the second field role relationship. The report evidence relationship includes monitoring records, report location relationship and unit affiliation relationship. The system will establish a correspondence between the reporting entity identifier, reporting period, pollutant affiliation and discharge outlet affiliation in the second field role relationship and the monitoring record source, report page number position, text block position and unit source in the report evidence relationship. If the original evidence in the test report can still support the control to be filled in by the second field role relationship, the system will generate an evidence retention mark. The evidence retention mark is used to indicate whether the report evidence relationship can still be used as the basis for filling in after the page role changes.

[0092] The system writes the role replacement marker, write deviation marker, and evidence retention marker into the same reconstruction trigger relationship. This reconstruction trigger relationship uses the control to be backfilled as an index and records the corresponding paths between the field role before writing, the field role after writing, the write verification result, and the report evidence acceptance result. When the reconstruction trigger relationship points to the control to be backfilled, the system re-establishes the attribution matching relationship, value constraint relationship, and write order relationship based on the second field role relationship and the report evidence relationship, forming a second backfill mapping relationship.

[0093] For example: The first backfill mapping relationship originally pointed to the "COD monitoring value" control of "wastewater discharge outlet DW001". After writing, the page was refreshed and switched to another discharge outlet area. The page still has a "monitoring value" control with the same name. The system identifies the current discharge outlet affiliation of the control with the same name through the role relationship of the second field, determines the deviation between the original writing path and the current page state through the write verification relationship, and confirms the monitoring record corresponding to the current discharge outlet and pollutants in the test report through the report evidence relationship. Thus, the system generates a second backfill mapping relationship, so that the subsequent second write command can be executed according to the business identity of the page after writing. Example 2:

[0094] like Figure 2 As shown, this embodiment further improves upon the design of Embodiment 1. The difference is that, in the actual operation of Embodiment 1, it was found that after the target environmental protection declaration webpage is injected with script, due to page tab linkage, pop-up refresh, dropdown option reloading, table row redrawing, and front-end validation callbacks, the page may simultaneously contain the original controls to be filled, newly generated controls, and hidden controls within a short period. This causes the second page context relationship to be formed based on an unstable page state, resulting in inconsistency between the second field role relationship and the controls to be filled ultimately carried by the page, failing to stably maintain the continuity between the report evidence relationship and the roles of the fields after injection. Based on this, an environmental protection declaration remote intelligent filling method further includes:

[0095] After executing the first write command, the system does not immediately use the page state collected for the first time as the second page context relationship. Instead, it establishes a linkage state record based on the control event triggering order in the first write command. The linkage state record is used to save the page response process triggered by this write. Its recording objects include the event response of the control to be backfilled, container level changes, visibility state changes, routing state changes, verification prompt changes, and page text changes associated with the control to be backfilled. The linkage state record is indexed by the control to be backfilled pointed to by the first backfill mapping relationship and is associated with the first field role relationship.

[0096] After the linkage status record is formed, the system collects the candidate page context relationship of the target environmental protection declaration webpage according to the control event triggering order. The candidate page context relationship does not independently replace the second page context relationship, but is used to record the intermediate state of the page in the linkage process. Each time the system collects the candidate page context relationship, it reads the page ownership relationship, control response relationship and page status relationship, and matches them with the declaration business boundary, write triggering method and page occupation status in the first field role relationship. When the above correspondence results show that the container level of the control to be filled is still changing, the control event is still being triggered, the visibility state is still switching, and the routing state is still not pointing to the current filling area, the system marks the candidate page context relationship as a transitional state relationship.

[0097] When the page affiliation, control response, and page state relationships in the candidate page context relationship correspond to the content displayed on the current page, and the visible state, control event response, and routing state of the control to be filled all point to the same application business boundary, the system determines the candidate page context relationship as a stable page context relationship. The stable page context relationship is used to replace the second page context relationship directly collected in Implementation Example 1, and the second field role relationship is generated accordingly. Thus, the second field role relationship is not formed based on the instantaneous page state after writing, but based on the stable page state after the page linkage is completed.

[0098] When generating the second field role relationship, the system also establishes a control inheritance relationship. The control inheritance relationship is used to record the connection between the control to be filled in the first field role relationship and the current control to be filled in the stable page context relationship. The system maps the declaration subject identifier, declaration period, pollutant attribution, discharge outlet attribution, declaration business boundary and write triggering method in the first field role relationship to the page attribution relationship, control response relationship and page state relationship of the current control in the stable page context relationship. When the current control continues the business attribution in the first field role relationship, the system marks it as a role continuation control. When the current control switches to a new discharge outlet attribution, pollutant attribution or declaration period due to page linkage, the system marks it as a role replacement control and writes the mark into the control inheritance relationship.

[0099] The system further establishes an evidence inheritance relationship based on the control inheritance relationship. The evidence inheritance relationship is used to limit the succession path of the report evidence relationship after the page role changes. Specifically, the system maps the monitoring records, report location relationship, and unit affiliation relationship in the report evidence relationship to the declaration entity identifier, declaration period, pollutant affiliation, and discharge outlet affiliation in the second field role relationship. When the report evidence relationship can support the role continuation control, the system writes the original report evidence relationship into the evidence inheritance relationship. When the control inheritance relationship points to the role replacement control, the system redetermines the monitoring records corresponding to the current declaration business boundary from the monitoring result matrix based on the second field role relationship, and writes the redetermined monitoring records, report location relationship, and unit affiliation relationship into the evidence inheritance relationship.

[0100] The system generates a second backfill mapping relationship based on stable page context relationships, control inheritance relationships, and evidence inheritance relationships. The attribution matching relationship in the second backfill mapping relationship is established by the monitoring records in the second field role relationship and the evidence inheritance relationship. The value constraint relationship is established by the unit attribution relationship in the second field role relationship and the evidence inheritance relationship. The writing order relationship is established by the control response relationship in the second field role relationship and the stable page context. The system then generates a second write instruction based on this second backfill mapping relationship, so that the second write instruction corresponds to the currently backfilled control after the linkage is completed, rather than the intermediate state control in the writing process.

[0101] For example: After the first write instruction writes the "COD monitoring value" of "wastewater discharge outlet DW001" in the test report to the target environmental declaration webpage, the page refreshes in conjunction with the discharge outlet selection control. The original "monitoring value" control is briefly retained, and then a "monitoring value" control with the same name is generated under the current tab. The system identifies the candidate page context relationship in this process through the linkage status record, and forms a stable page context relationship after the page affiliation relationship, control response relationship and page status relationship are stable. If the stable page context relationship indicates that the current control still corresponds to "wastewater discharge outlet DW001", the report evidence relationship is written into the evidence inheritance relationship; if the stable page context relationship indicates that the current control has switched to another discharge outlet, the system re-determines the corresponding monitoring record from the monitoring result matrix according to the role relationship of the second field, and generates the second backfill mapping relationship and the second write instruction accordingly. Example 3:

[0102] like Figure 3 As shown, based on the same inventive concept as the aforementioned environmental protection declaration remote intelligent filling method, this application provides an environmental protection declaration remote intelligent filling system. The system and method embodiments in this application are based on the same inventive concept. The system includes:

[0103] Page awareness module: Collects page text, control attributes, container hierarchy, control events, visibility state, and routing state of the target environmental protection declaration webpage to construct the first page context relationship;

[0104] Role generation module: Extracts the core parameters of the application based on the context of the first page, associates them with the control to be filled in, and generates the first field role relationship;

[0105] Report Evidence Collection Module: Analyzes the layout text, table cells, text block positions, page number positions, and unit sources of the test report to generate monitoring records, monitoring result matrices, and report evidence relationships;

[0106] Backfill mapping module: Generates a first backfill mapping relationship based on the first field role relationship, the monitoring result matrix, and the report evidence relationship;

[0107] Script writing module: Generates a first writing instruction based on the first backfill mapping relationship, and writes the monitoring record into the control to be backfilled through script injection;

[0108] Post-write perception module: After writing, collect the target environmental protection declaration webpage, generate the second page context relationship and the second field role relationship;

[0109] Write verification module: Reads the display data, internal data, event responses, and verification prompts of the control to be filled, and generates write verification relationships;

[0110] The reconstruction module generates a reconstruction trigger relationship based on the second field role relationship, the first field role relationship, and the write verification relationship. When the reconstruction trigger relationship points to the control to be backfilled, a second backfill mapping relationship is generated based on the second field role relationship and the report evidence relationship, and a second write instruction is generated based on the second backfill mapping relationship.

[0111] Obviously, those skilled in the art can make various modifications and variations to this invention without departing from its spirit and scope. Therefore, if these modifications and variations fall within the scope of the claims of this invention and their equivalents, this invention also intends to include these modifications and variations.

[0112] The above description is merely a preferred embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any equivalent substitutions or modifications made by those skilled in the art within the scope of the technology disclosed in the present application, based on the technical solution and concept of the present application, should be covered within the scope of protection of the present application.

Claims

1. A remote intelligent filling method for environmental protection declarations, characterized in that the method... include: Collect the page text, control attributes, container hierarchy, control events, visibility state, and routing state of the target environmental protection declaration webpage to construct the first page context relationship; Based on the context of the first page, extract the core parameters of the application, associate them with the control to be filled in, and generate the first field role relationship; The system analyzes the layout text, table cells, text block positions, page number positions, and unit sources of the test report to generate monitoring records, a monitoring result matrix, and report evidence relationships. A first backfill mapping relationship is generated based on the role relationship in the first field, the monitoring result matrix, and the report evidence relationship; Based on the first backfill mapping relationship, a first write instruction is generated, and the monitoring record is written to the control to be backfilled through script injection; After writing, the target environmental protection declaration webpage is collected to generate the second page context relationship and the second field role relationship; Read the display data, internal data, event responses, and verification prompts of the control to be filled, and generate a write verification relationship; A reconstruction trigger relationship is generated based on the second field role relationship, the first field role relationship, and the write verification relationship; when the reconstruction trigger relationship points to the control to be backfilled, a second backfill mapping relationship is generated based on the second field role relationship and the report evidence relationship, and a second write instruction is generated based on the second backfill mapping relationship.

2. The environmental protection declaration remote intelligent filling method according to claim 1, characterized in that, Both the first page context relationship and the second page context relationship include page ownership relationship, control response relationship and page state relationship; the page ownership relationship is formed by the correspondence between page text and container hierarchy, the control response relationship is formed by the correspondence between control attributes and control events, and the page state relationship is formed by the correspondence between visible state and routing state.

3. The environmental protection declaration remote intelligent filling method according to claim 2, characterized in that, The method for generating the first field role relationship and the second field role relationship includes: determining the application business boundary where the control to be filled is located based on the page affiliation relationship, determining the write triggering method of the control to be filled based on the control response relationship, determining the page occupancy status of the control to be filled based on the page status relationship, and establishing a field role correspondence relationship between the application business boundary, the write triggering method, and the page occupancy status and the application core parameters.

4. The environmental protection declaration remote intelligent filling method according to claim 3, characterized in that, The method for extracting the core parameters of the application includes: extracting the applicant identifier, application period, pollutant attribution, and discharge outlet attribution from the first page context relationship, and writing the applicant identifier, application period, pollutant attribution, and discharge outlet attribution into the field role correspondence relationship; re-extracting the applicant identifier, application period, pollutant attribution, and discharge outlet attribution from the second page context relationship, and using them to generate the second field role relationship.

5. The environmental protection declaration remote intelligent filling method according to claim 1, characterized in that, The method for generating the report evidence relationship includes: generating the monitoring record based on the page text and the table unit; generating the report positioning relationship based on the text block position and the page number position; generating the unit affiliation relationship based on the unit source; and writing the monitoring record, the report positioning relationship, and the unit affiliation relationship into the monitoring result matrix.

6. The environmental protection declaration remote intelligent filling method according to claim 5, characterized in that, Both the first backfill mapping relationship and the second backfill mapping relationship include an attribution matching relationship, a value constraint relationship, and a writing order relationship. The attribution matching relationship is formed by the correspondence between the corresponding field role relationship and the monitoring record. The value constraint relationship is formed by the correspondence between the corresponding field role relationship and the unit attribution relationship. The writing order relationship is formed by the correspondence between the corresponding field role relationship and the report positioning relationship.

7. The environmental protection declaration remote intelligent filling method according to claim 6, characterized in that, The method for generating the first write instruction and the second write instruction includes: determining the control to be backfilled based on the attribution matching relationship, determining the write value based on the value constraint relationship, determining the control event triggering order based on the write order relationship, and combining the control to be backfilled, the write value, and the control event triggering order into a corresponding write instruction.

8. The environmental protection declaration remote intelligent filling method according to claim 7, characterized in that, The method for generating the write verification relationship and the reconstruction trigger relationship includes: establishing a display verification relationship between the display data and the write value; establishing an internal verification relationship between the internal data and the write value; establishing an event verification relationship between the event response and the control event triggering order; establishing a page verification relationship between the verification prompt and the second field role relationship; and forming the write verification relationship by the display verification relationship, the internal verification relationship, the event verification relationship, and the page verification relationship; generating a role replacement flag by a substitution judgment between the second field role relationship and the first field role relationship; generating a write deviation flag by a deviation judgment between the write verification relationship and the first backfill mapping relationship; generating an evidence retention flag by a retention judgment between the report evidence relationship and the second field role relationship; writing the role replacement flag, the write deviation flag, and the evidence retention flag into the reconstruction trigger relationship; and generating the second backfill mapping relationship based on the reconstruction trigger relationship.

9. The method for remote intelligent filling of environmental protection declarations according to claim 1, characterized in that, Also includes: After executing the first write command, a linkage status record is established, and the context relationship of candidate pages is collected; When the candidate page context relationship is in a transitional state, the data collection continues. When a stable page context relationship is formed, a second field role relationship, control inheritance relationship, and evidence inheritance relationship are generated, and a second backfill mapping relationship and a second write instruction are generated accordingly.

10. An environmental protection declaration system with remote intelligent filling, characterized in that the system... include: Page awareness module: Collects page text, control attributes, container hierarchy, control events, visibility state, and routing state of the target environmental protection declaration webpage to construct the first page context relationship; Role generation module: Extracts the core parameters of the application based on the context of the first page, associates them with the control to be filled in, and generates the first field role relationship; Report Evidence Collection Module: Analyzes the layout text, table cells, text block positions, page number positions, and unit sources of the test report to generate monitoring records, monitoring result matrices, and report evidence relationships; Backfill mapping module: Generates a first backfill mapping relationship based on the first field role relationship, the monitoring result matrix, and the report evidence relationship; Script writing module: Generates a first writing instruction based on the first backfill mapping relationship, and writes the monitoring record into the control to be backfilled through script injection; Post-write perception module: After writing, collect the target environmental protection declaration webpage, generate the second page context relationship and the second field role relationship; Write verification module: Reads the display data, internal data, event responses, and verification prompts of the control to be filled, and generates write verification relationships; The reconstruction module generates a reconstruction trigger relationship based on the second field role relationship, the first field role relationship, and the write verification relationship. When the reconstruction trigger relationship points to the control to be backfilled, a second backfill mapping relationship is generated based on the second field role relationship and the report evidence relationship, and a second write instruction is generated based on the second backfill mapping relationship.

Images