A smart rail damage monitoring and transportation maintenance management system
By generating dual-temporal damage records and physical damage chains, processing delayed confirmation tasks, correcting transportation task attribution, and updating transportation conditions, the problem of inconsistent damage record order in the rail damage monitoring system was solved, achieving accurate attribution of transportation tasks and continuity of maintenance tasks.
Patent Information
- Application Number
- CN202611440047.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-09-16
- Publication Date
- 2026-11-17
AI Technical Summary
In existing rail damage monitoring systems, the transmission of detection data, manual verification, and network transmission can cause discrepancies between the order of damage records and the actual order of their evolution. This makes it difficult to accurately assign damage to transportation tasks, resulting in duplicate, omission, or incorrect association of transportation tasks, which affects the continuity of transportation management and maintenance tasks.
The system employs a dual-temporal recording generation module to acquire damage monitoring records, generate physical damage chains, a delayed task confirmation module to process and confirm delayed tasks, a damage task continuation module to connect transportation tasks, a task attribution correction module to correct task attribution, and a transportation maintenance update module to update transportation task conditions, thereby generating rail maintenance tasks.
Improve the consistency of damage timing, reduce errors in transportation task assignment, connect transportation adjustments with rail maintenance, and achieve continuity between historical operation review and transportation adjustments.
Smart Images

Figure CN123118073A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of intelligent operation and maintenance and transportation scheduling management technology for rail transit, specifically to an intelligent rail damage monitoring and transportation operation and maintenance management system. Background Technology
[0002] Rails are subjected to long-term impacts from train wheels and rails, alternating loads, and environmental erosion, making them prone to damage such as cracks, spalling, and wear. Existing rail maintenance systems typically collect damage monitoring data using flaw detection vehicles, rail flaw detectors, or inspection terminals. After verification, the damage location, type, and condition are transmitted to the transportation maintenance management platform. This platform then combines train operation plans, actual operation records, track maintenance windows, and maintenance resources to schedule rail re-inspections or repairs.
[0003] Due to the impact of data feedback, manual review, and network transmission, there may be a gap between the actual damage monitoring time and the confirmation time of the test results. The same rail damage may also be discovered consecutively by different inspection batches, leading to a discrepancy between the order in which damage records enter the management platform and the actual evolution order of the damage status. Before the test results are confirmed, the train may have already passed through the corresponding damaged section. Existing management systems typically update the damage status according to the order of record reception or confirmation, making it difficult to accurately assign transport tasks that pass through during the confirmation lag period to the corresponding damage stage. This can easily result in duplicate assignment, omission of assignment, or association with incorrect damage statuses.
[0004] After late-arrival damage records are entered into the management platform, existing processing methods typically involve either retaining the original transportation task attribution or reprocessing all transportation tasks within the corresponding line area. The former fails to correct the mismatch between historical transportation tasks and actual damage status, while the latter easily expands the scope of adjustments to transportation plans and maintenance tasks, affecting unrelated transportation tasks and existing maintenance arrangements. Furthermore, after the attribution of historical transportation tasks is corrected, the relevant changes are difficult to propagate to the operational condition verification of pending transportation tasks, making it impossible to accurately define the first transportation task requiring adjustment and the corresponding maintenance deadline. This results in a lack of continuous data continuity between rail monitoring, transportation management, and maintenance tasks. Therefore, collaborative management of rail damage monitoring records, actual transportation tasks, and pending transportation tasks is necessary. Summary of the Invention
[0005] Based on the shortcomings of the prior art described above, the purpose of this invention is to provide an intelligent monitoring and transportation operation and maintenance management system for rail damage to solve the aforementioned technical problems.
[0006] To achieve the above objectives, the present invention provides the following technical solution: an intelligent monitoring and transportation maintenance management system for rail damage, comprising: The dual-temporal record generation module obtains damage monitoring records and transportation task records from rail damage monitoring equipment, and associates monitoring time, confirmation time, rail entity identification, damage range, damage type, damage status and maintenance closure record to generate dual-temporal damage records. The entity damage chain generation module groups dual-temporal damage records according to rail entity identification, and generates entity damage chains by continuing dual-temporal damage records with intersecting damage intervals, successive damage types, and no maintenance closure records between adjacent records according to monitoring time. The delayed task module will arrange the transportation tasks that actually passed through the damaged area between the monitoring time and the confirmation time according to the actual passing time, and generate the delayed task sequence. The damage task continuation module divides the damage evolution period into adjacent monitoring times in the physical damage chain. It uniquely assigns the transportation task whose actual passage time falls into the damage evolution period and whose operating section covers the damage area to the corresponding damage evolution period, and generates the damage task continuation chain according to the actual passage time. When the confirmation time sequence and monitoring time sequence of the damage chain of the same entity are inconsistent, the task attribution correction module accesses the corresponding record according to the monitoring time, cancels the original stage attribution of the transportation task within the delayed confirmation task sequence, re-attributes according to the updated damage evolution period, matches the original damage task succession chain with the updated damage task succession chain, and generates a task attribution change segment. The transportation operation and maintenance update module maps the actual operating conditions of transportation tasks within the task assignment change segment to the damage status after reassignment, and generates historical operation review records; it maps the operating constraints corresponding to the chain tail damage status to the planned operating conditions of the transportation tasks to be executed item by item, takes the first conflicting condition task as the starting task for transportation adjustment, and generates rail maintenance tasks based on the planned maintenance deadline boundary of the starting task for transportation adjustment through time limits.
[0007] The present invention is further configured such that the dual-temporal recording generation module includes: Damage monitoring records are obtained through the rail damage monitoring equipment interface, and the rail physical identification, damage range, damage type, damage status and monitoring time are retained; Obtain the confirmation time of the completion of the damage monitoring record review, and associate the confirmation time with the corresponding damage monitoring record; The maintenance and acceptance records are mapped to the damage monitoring records according to the rail physical identification and maintenance section, and maintenance closure records are generated. The monitoring time, confirmation time, and maintenance closure record are linked to the damage monitoring record to generate a dual-temporal damage record.
[0008] The present invention is further configured such that the entity damage chain generation module includes: The rail entity record group is generated by grouping the dual-temporal damage records according to the rail entity identification, track direction and track marking. Arrange the rail entity record groups according to the monitoring time, and generate adjacent candidate records for dual temporal damage records with adjacent time. Perform damage interval intersection verification and damage type continuity verification on adjacent candidate records to generate damage continuity records; Damage transfer records that do not cross the maintenance closure record are sequentially connected according to the monitoring time to generate a physical damage chain.
[0009] The present invention is further configured such that the confirmation delay task module includes: The monitoring time in the dual-temporal damage record is used as the starting point and the confirmation time is used as the ending point to generate a confirmation lag period. Select transportation tasks from the transportation task records whose actual transit time falls within the confirmation lag period and whose task status is "executed", and generate time candidate tasks. Perform coverage verification between the actual running segment of the time candidate task and the damage interval in the dual-temporal damage record to generate a damage crossing task; Damage traversal tasks are sequentially arranged according to the actual passage time, and dual-temporal damage record identifiers are associated with the corresponding tasks to generate a confirmed lag task sequence.
[0010] The present invention is further configured such that dividing the damage evolution period based on adjacent monitoring times in the solid damage chain includes: Arrange the dual-temporal damage records in the physical damage chain according to the monitoring time to generate the record order within the chain; Using the monitoring time of the previous pair of temporal damage records as the starting point and the monitoring time of the next pair of temporal damage records as the ending point, a damage evolution period of left-closed and right-open is generated. The damage status, damage range, and record identifier of the previous bitemporal damage record are associated with the corresponding damage evolution period to generate a period status record; Using the monitoring time of the chain tail dual-temporal damage record as the starting point and the current operation and maintenance processing time as the ending point, a chain tail evolution period is generated, and the chain tail damage status is associated with the chain tail evolution period.
[0011] The present invention is further configured such that the transportation task whose actual transit time falls within the damage evolution period and whose operating segment covers the damage interval is uniquely assigned to the corresponding damage evolution period, and the damage task succession chain is generated according to the actual transit time, including: The actual transit time of the transportation task is mapped to the damage evolution period to generate time-segment candidate tasks; Perform coverage verification between the actual running segment of the candidate task and the damaged interval in the time period status record, and pass the task generation stage. Unique attribution verification is performed based on the entity damage chain identifier and the transportation task identifier, and transportation tasks within the same entity damage chain retain one stage of attribution. Based on the actual completion time, the damage task is sequentially completed, and the stage identifier, damage status, and task identifier are associated to generate a damage task continuation chain.
[0012] The present invention is further configured such that, according to the monitoring time, accessing the corresponding record and canceling the original stage attribution of the transportation task within the delayed task sequence includes: The dual-temporal damage records in the same entity damage chain are arranged according to the monitoring time and the confirmation time, respectively, to generate monitoring order records and confirmation order records; Based on the record identifier, corresponding monitoring sequence record and confirmation sequence record, generate sequence mismatch record for dual temporal damage records where the preceding or subsequent records are inconsistent; Based on the monitoring time of the sequence mismatch record, obtain the adjacent monitoring record corresponding to the access location, and terminate the original connection relationship between the adjacent monitoring records; Connect the mismatched records to the corresponding adjacent monitoring records to generate an updated intra-chain order; Match the confirmed delayed task sequence corresponding to the sequence mismatch record with the original damage task continuation chain, and cancel the original stage assignment of the corresponding transportation task.
[0013] The present invention is further configured such that, based on the updated damage evolution period, the original damage task succession chain and the updated damage task succession chain are mapped to generate a task ownership change segment, including: Based on the order within the update chain, the damage evolution period before and after the order mismatch record is redefined, and an update period record is generated. The transportation tasks assigned during the cancellation phase are reassigned to the update period record according to the actual passage time and actual operating segment, generating an update damage task continuation chain. Based on the original damage task succession chain and the updated damage task succession chain corresponding to the transportation task identifier, a change of ownership record is generated for transportation tasks whose stage identifiers have changed. Arrange the ownership change records according to the actual passage time, and use the first and last ownership change records to define the scope of continuous tasks, thereby generating a task ownership change segment.
[0014] The present invention is further configured such that the transportation operation and maintenance update module generates historical operation review records and transportation adjustment initiation tasks, including: The actual operating conditions of the transportation tasks within the task ownership change segment are matched with the damage status in the updated damage task succession chain to generate historical operation review records. Obtain the damage status of the tail end of the physical damage chain, and call the rail maintenance rules based on the damage type and tail end damage status to generate an operation restriction record; Filter transportation tasks from the transportation task records whose planned passage time is later than the current operation and maintenance processing time and whose operating segment covers the chain tail damage area, and generate a task sequence to be verified. The planned operating conditions and operating restriction records in the task sequence to be verified are matched one by one. The first transportation task that does not meet the restriction is taken as the starting task for transportation adjustment, and the transportation tasks that meet the restriction before it are used to generate a compatible transportation task sequence.
[0015] The present invention is further configured such that, according to the transportation adjustment of the initial task plan, the generation of rail maintenance tasks by setting time limits for maintenance deadlines includes: The schedule for adjusting the initial task of transportation will be used as the maintenance deadline. When the compatible transport task sequence is empty, the current maintenance processing time is used as the maintenance open boundary; when the compatible transport task sequence is not empty, the later of the current maintenance processing time and the time when the last compatible transport task leaves the damaged section is used as the maintenance open boundary. Based on the maintenance open boundary, maintenance close boundary and corresponding damage repair duration, continuous idle periods are selected from the line operation plan to generate candidate maintenance periods; Match each candidate maintenance period with maintenance personnel, maintenance equipment, line closure records, and equipment relocation records to generate a resource fulfillment record. Resource fulfillment records are arranged according to the start time of the candidate maintenance period. The first resource fulfillment record is associated with the entity damage chain and the task ownership change segment to generate a rail maintenance task and update the corresponding transportation and maintenance records.
[0016] This invention provides an intelligent rail damage monitoring, transportation, and maintenance management system. The system uses a dual-temporal record generation module to acquire damage monitoring records and transportation task records from rail damage monitoring equipment. It then associates monitoring time, confirmation time, rail entity identifier, damage interval, damage type, damage status, and maintenance closure record to generate dual-temporal damage records. An entity damage chain generation module groups the dual-temporal damage records according to rail entity identifiers. It then sequentially generates entity damage chains by connecting dual-temporal damage records with intersecting damage intervals, inherited damage types, and no maintenance closure records between adjacent records, based on monitoring time. A confirmation lag task module arranges transportation tasks that actually pass through the damage interval between the monitoring time and confirmation time according to actual passage time, generating a confirmation lag task sequence. Finally, a damage task continuation module divides the damage evolution period based on adjacent monitoring times in the entity damage chain, ensuring that the actual passage time falls within the damage evolution period and the operating section covers the damage area. The transportation tasks are uniquely assigned to the corresponding damage evolution period, and damage task succession chains are generated according to the actual passage time. The task attribution correction module, when the confirmation time order and monitoring time order of the same entity's damage chain are inconsistent, accesses the corresponding record according to the monitoring time, cancels the original stage attribution of the transportation tasks within the delayed confirmation task sequence, and reassigns them according to the updated damage evolution period. It then matches the original damage task succession chain with the updated damage task succession chain, generating a task attribution change segment. The transportation maintenance update module matches the actual operating conditions of the transportation tasks within the task attribution change segment with the reassigned damage status, generating historical operation review records. It matches the operating constraints corresponding to the chain tail damage status with the planned operating conditions of the transportation tasks to be executed item by item, using the first conflicting condition task as the starting task for transportation adjustment. Based on the planned passage time of the starting task for transportation adjustment, it limits the maintenance deadline boundary and generates rail maintenance tasks. The beneficial effects include: 1. Improve the consistency of damage sequence: By retaining the monitoring time and confirmation time separately, and continuing the damage records of the same rail entity according to the monitoring time, it is possible to avoid errors in the order of damage state evolution caused by delayed confirmation or disordered recording. 2. Reduce transportation task assignment errors: By establishing a damaged task continuation chain, the original stage assignment of the affected task can be revoked and reassigned after the late record is accessed, which can reduce the duplicate assignment, omission of assignment and state mismatch of transportation tasks. 3. Connecting Transportation Adjustment and Rail Maintenance: By verifying the damage status of the chain tail to be executed for the transportation task to be performed, the starting task for transportation adjustment and the end boundary for maintenance are generated, which can realize the continuous connection between historical operation review, transportation adjustment and maintenance tasks.
[0017] The above description is only an overview of the technical solution of this application. In order to better understand the technical means of this application and to implement it in accordance with the contents of the specification, and to make the above and other objects, features and advantages of this application more obvious and understandable, specific embodiments of this application are given below. Attached Figure Description
[0018] 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 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. In the drawings: Figure 1 The flowchart illustrates an intelligent monitoring and transportation operation and maintenance management system for rail damage, as shown in an exemplary embodiment of the present invention. Detailed Implementation
[0019] The embodiments of the present invention will be described below with reference to the accompanying drawings and preferred embodiments. Those skilled in the art can easily understand other advantages and effects of the present invention from the content disclosed in this specification. The present invention can also be implemented or applied through other different specific embodiments, and various details in this specification can also be modified or changed based on different viewpoints and applications without departing from the spirit of the present invention. It should be understood that the preferred embodiments are only for illustrating the present invention and not for limiting the scope of protection of the present invention.
[0020] It should be noted that the illustrations provided in the following embodiments are only schematic representations of the basic concept of the present invention. Therefore, the drawings only show the components related to the present invention and are not drawn according to the actual number, shape and size of the components in the actual implementation. In the actual implementation, the form, quantity and proportion of each component can be arbitrarily changed, and the layout of the components may also be more complex.
[0021] In the following description, numerous details are explored to provide a more thorough explanation of embodiments of the invention. However, it will be apparent to those skilled in the art that embodiments of the invention may be practiced without these specific details. In other embodiments, well-known structures and devices are shown in block diagram form rather than in detail to avoid obscuring embodiments of the invention. Example
[0022] A smart rail damage monitoring and transportation operation and maintenance management system, such as Figure 1 As shown, it includes: The dual-temporal record generation module obtains damage monitoring records and transportation task records from rail damage monitoring equipment, and associates monitoring time, confirmation time, rail entity identification, damage range, damage type, damage status and maintenance closure record to generate dual-temporal damage records. The entity damage chain generation module groups dual-temporal damage records according to rail entity identification, and generates entity damage chains by continuing dual-temporal damage records with intersecting damage intervals, successive damage types, and no maintenance closure records between adjacent records according to monitoring time. The delayed task module will arrange the transportation tasks that actually passed through the damaged area between the monitoring time and the confirmation time according to the actual passing time, and generate the delayed task sequence. The damage task continuation module divides the damage evolution period into adjacent monitoring times in the physical damage chain. It uniquely assigns the transportation task whose actual passage time falls into the damage evolution period and whose operating section covers the damage area to the corresponding damage evolution period, and generates the damage task continuation chain according to the actual passage time. When the confirmation time sequence and monitoring time sequence of the damage chain of the same entity are inconsistent, the task attribution correction module accesses the corresponding record according to the monitoring time, cancels the original stage attribution of the transportation task within the delayed confirmation task sequence, re-attributes according to the updated damage evolution period, matches the original damage task succession chain with the updated damage task succession chain, and generates a task attribution change segment. The transportation operation and maintenance update module maps the actual operating conditions of transportation tasks within the task assignment change segment to the damage status after reassignment, and generates historical operation review records; it maps the operating constraints corresponding to the chain tail damage status to the planned operating conditions of the transportation tasks to be executed item by item, takes the first conflicting condition task as the starting task for transportation adjustment, and generates rail maintenance tasks based on the planned maintenance deadline boundary of the starting task for transportation adjustment through time limits.
[0023] The present invention is further configured such that the dual-temporal recording generation module includes: Damage monitoring records are obtained through the interface of the rail damage monitoring equipment, retaining the rail entity identification, damage range, damage type, damage status, and monitoring time. Specifically, this embodiment is applied to rail flaw detection operations on a railway trunk line. The rail damage monitoring equipment adopts a vehicle-mounted ultrasonic flaw detection device. The transportation operation and maintenance management system is connected to the flaw detection device interface, transportation dispatch interface, and maintenance management interface, respectively. The vehicle-mounted ultrasonic flaw detection device completes ultrasonic echo acquisition according to the equipment calibration configuration. In this embodiment, the ultrasonic sampling frequency is 50 MHz, and the line positioning unit outputs mileage position frames at 10 Hz. When the flaw detection program on the device side detects a damage event, it generates a damage event packet and sends it to the transportation operation and maintenance management system through the device interface. Continuous ultrasonic echoes are retained in the flaw detection device, and the damage event packet serves as the input object of this system. The damage event packet includes equipment identification, inspection batch identification, event identification, line code, running direction, track identification, rail side identification, damage start mileage, damage end mileage, damage type code, damage status code, and monitoring time. The physical identification of rails is generated by combining the line code, direction of operation, track identification, rail side identification, and rail section number in sequence, and is used to distinguish the up rail, down rail, left rail, and right rail at the same mileage. The damaged section is represented by a unified track mileage coordinate system, with the start and end positions derived from the mileage mapping results of adjacent positioning frames at the time of the damage event. The positioning error is taken from the flaw detection equipment calibration report, which is ±0.5 m in this embodiment. Subsequent maintenance records will be processed according to this error range to verify the section coverage relationship. The damage type code is derived from the rail damage code table configured in the flaw detection equipment, and the damage status code is derived from the rail operation and maintenance rules confirmed by the railway operating unit. This embodiment uses four levels of status codes, S1 to S4. S1 corresponds to the tracking and observation status, S2 corresponds to the re-inspection arrangement status, S3 corresponds to the restricted operation and maintenance arrangement status, and S4 corresponds to the cessation of related transportation tasks and immediate handling status. The status code only serves as a correspondence between the detection conclusion and the operation and maintenance rules. The specific handling requirements are still taken from the corresponding version of the rail operation and maintenance rules. The monitoring time is taken from the satellite timing unit of the flaw detection equipment, using the format of year, month, day, hour, minute, second, and millisecond. The flaw detection equipment and the transportation operation and maintenance management system use the same standard clock. After receiving the damage event packet, the system sequentially performs event identifier integrity verification, mileage unit unification, time format unification, and duplicate event screening. Duplicate events are matched according to equipment identifier, inspection batch identifier, and event identifier, and only one record with complete content is retained. In this embodiment, the start time of this rail flaw detection operation is used as the time reference to obtain a damage monitoring record with the rail entity identifier "L01-Up-1 strand-Left rail-R125". The damage range is from K125+429.8 m to K125+430.4 m, the damage type is transverse crack inside the rail head, the damage status code is S2, and the monitoring time is 15 minutes, 12 seconds, and 340 milliseconds after the start of the operation. This time is recorded as the first monitoring time.After verifying field integrity, standardizing mileage and time formats, a damage monitoring record to be reviewed is generated. The confirmation time for the completion of damage monitoring record review is obtained and associated with the corresponding damage monitoring record. Specifically, the damage monitoring record to be reviewed is sent to the rail damage review terminal, and the record correspondence is maintained through the detection batch identifier and event identifier. The review terminal displays the damage location, damage type, damage status, equipment echo screenshot, and adjacent positioning frames. Reviewers perform location verification, type verification, and status verification according to the rail flaw detection operation procedures. The review process uses three statuses: pending review, returned for supplementation, and confirmed pass. The status code for pending review is 0, the status code for returned for supplementation is 2, and the status code for confirmed pass is 1. Reviewers execute the return... When performing supplementary operations, the return time, reason for return, and original damage monitoring record are retained, but no confirmation time is generated. After the supplementary data is resubmitted, the original event identifier is retained, and a review version number is added. When the review status changes from 0 or 2 to 1, the platform server generates a confirmation time based on the moment the status change is successful. The confirmation time is derived from the platform server's standard clock to avoid incorrect confirmation order caused by differences in the local clock of the review terminal. When there are more than two reviews, the server time corresponding to the final confirmation is used as the confirmation time, and all previous return records and version records are retained. The valid range of the confirmation time is from the monitoring time to the end of the current platform processing time. When the confirmation time is earlier than the monitoring time, a time anomaly record is generated, and the corresponding damage monitoring record is kept in a pending verification state and not entered into subsequent formal processing; when the confirmation time is equal to the monitoring time, it means that the equipment monitoring and platform confirmation occurred within the same time accuracy range; when the confirmation time is later than the monitoring time, the time range between the two serves as the basis for subsequent retrieval of completed transportation tasks; in this embodiment, the transverse crack record inside the rail head is reviewed at 3 hours, 17 minutes and 33 seconds after the first monitoring time, and the review status changes from pending review to confirmed pass. The platform server records the status change time as the first confirmation time and associates it with the damage monitoring record corresponding to the event identifier. The first monitoring time and the first confirmation time occupy independent fields, and the time period between the two serves as the confirmation lag period for subsequent association of completed transportation tasks; The maintenance and acceptance records are mapped to the damage monitoring records according to the rail physical identifiers and maintenance sections to generate a closed maintenance record. Specifically, the rail maintenance and acceptance records are obtained through the maintenance management interface. The maintenance and acceptance records include the maintenance work order identifier, rail physical identifier, maintenance start mileage, maintenance end mileage, maintenance method, work completion time, acceptance time, and acceptance status. The maintenance methods include rail grinding, welding repair, reinforcement, and rail replacement, with specific codes derived from the work code table of the maintenance management system. The acceptance status includes pending acceptance, acceptance returned, and acceptance passed. Only maintenance records that have passed acceptance are mapped to the closed record. The maintenance and acceptance records and damage monitoring records are mapped to the same rail according to the rail physical identifiers. Then, the maintenance section is verified against the damage section after considering equipment positioning errors. When the rail physical identifiers are consistent, the maintenance section completely covers the damage section, the acceptance time is later than the monitoring time, and the acceptance status is passed, the maintenance work order identifier, maintenance method, acceptance time, and damage event identifier are associated to generate a closed maintenance record. When the maintenance section only covers a portion of the damaged section, the maintenance acceptance record is retained, but no corresponding maintenance closure record for the damage event is generated. If the line direction, track markings, or rail side are inconsistent, the correspondence between the maintenance record and the damage record is terminated. The closure status in the maintenance closure record is represented by 0 and 1, where 0 indicates that there is no acceptance record that meets the coverage conditions, and 1 indicates that there is already an acceptance record that meets the coverage conditions. The closure time is the maintenance acceptance pass time; if the work order is completed but not yet accepted, the closure status remains 0. This status restricts damage records at the same location before and after maintenance from continuing to be connected to the same entity damage chain. In this embodiment, the maintenance work order "WX-027" corresponds to the rail entity "L01-Up-1-Left Rail-R125", the maintenance section is from K125+429.5 m to K125+430.6 m, and the maintenance method is rail replacement. The rail replacement operation is completed 17 hours and 25 minutes after the first monitoring time and passes acceptance 17 hours and 55 minutes after the first monitoring time; the acceptance pass time is recorded as the first closure time. The maintenance section covers the damaged area from K125+429.8 m to K125+430.4 m. The rail physical markings are consistent, and the first closure time is later than the first monitoring time. Therefore, a maintenance closure record with a closure status of 1 is generated. Another maintenance work order belonging to the downtrack is not included in this damage monitoring record due to inconsistent rail physical markings. The monitoring time, confirmation time, and maintenance closure record are linked to the damage monitoring record to generate a dual-temporal damage record. Specifically, the combination of equipment identifier, inspection batch identifier, and event identifier is used as the unique record key for the damage monitoring record. The monitoring time, confirmation time, and review version number are linked through this record key. Then, the maintenance closure record is linked according to the rail entity identifier, damage section, and damage event identifier. When the confirmation status is "passed" and the confirmation time is valid, a formal dual-temporal damage record is generated; when the confirmation status is "pending review" or "returned for supplementation," the record is kept pending verification and not connected to the physical damage chain; the dual-temporal damage record must include at least the dual-temporal record identifier, damage event identifier, rail entity identifier, damage range, damage type, damage status, monitoring time, confirmation time, review version number, closure status, maintenance work order identifier, and closure time; the monitoring time records the actual detection time corresponding to the damage status, the confirmation time records the time when the detection conclusion enters the transportation operation and maintenance management process, and the closure time records the time when the damage is completed and accepted; when no maintenance closure record is obtained, the closure status is 0, and the maintenance work order identifier and closure time remain empty; after obtaining a valid maintenance closure record, the closure status is updated to 1, while retaining the record version before the update; in the dual-temporal damage record finally generated in this embodiment, the monitoring time is the first monitoring time, the confirmation time is the first confirmation time, the damage status is S2, the closure status is 1, and the closure time is... The first closure time is defined as the time sequence of damage records between the first monitoring time and the first closure time. The first confirmation time indicates the time when the detection conclusion enters the transportation operation and maintenance management process. Verification is performed using the same test scenario. Transportation task T301 passes through the damage interval 31 minutes after the first monitoring time, transportation task T305 passes through the damage interval 1 hour and 43 minutes after the first monitoring time, and transportation task T309 passes through the damage interval 2 hours and 36 minutes after the first monitoring time. All three transportation tasks are earlier than the first confirmation time. When only a single time record is established based on the first confirmation time, the three transportation tasks cannot enter the confirmed damage task range. With dual-temporal damage records, all three transportation tasks are between the first monitoring time and the first confirmation time. The subsequent confirmation delay task module generates a confirmation delay task sequence according to their actual passing order. After reaching the first closure time, subsequent damage monitoring records no longer continue to the physical damage chain before maintenance.
[0024] The present invention is further configured such that the entity damage chain generation module includes: The rail entity record group is generated by grouping rail entity identification, track direction, and track marking into dual-temporal damage records. Specifically, this embodiment is applied to the scenario of continuous rail flaw detection and collaborative management of transportation and maintenance on railway trunk lines. The vehicle-mounted ultrasonic flaw detection equipment completes ultrasonic echo acquisition according to the equipment calibration configuration. The track positioning unit outputs mileage position frames at 10 Hz, and generates a damage monitoring record for each damage event detected. After the damage monitoring record is confirmed by the verification terminal, the dual-temporal record generation module generates a dual-temporal damage record, which is then sent to the entity damage chain generation module in an event-triggered manner. The entity damage chain generation module receives data according to the method of one valid dual-temporal damage record corresponding to one processing, without repeating the ultrasonic echo at the equipment end. The received dual-temporal damage record includes dual-temporal record identifier, rail entity identification, track direction, track marking, rail side identification, damage interval, damage type, damage status, monitoring time, confirmation time, and maintenance closure status. Among them, the rail entity identification is generated by combining the track code, track direction, track marking, rail side identification, and rail section number. The track code originates from the track asset ledger, the track direction and track markings from basic transportation scheduling data, the rail side identification from the installation location of flaw detection equipment, and the rail section number from the rail asset management ledger. After obtaining dual-temporal damage records, the integrity verification of rail entity identification, the unification of track direction codes, the unification of track codes, and the removal of duplicate records are performed sequentially. Duplicate records are matched according to the dual-temporal record identification; for records with the same identification, only the record with the newest confirmed version number is retained. If the rail entity identification lacks track direction, track markings, or rail side identification, the corresponding record is retained as a record to be supplemented and is not added to the rail entity record group. The verified dual-temporal damage records are then precisely grouped according to the rail entity identification, track direction, and track markings. A rail entity record group represents a collection of damage records belonging to the same physical rail segment. Records within the group are allowed to have different monitoring times, damage intervals, damage types, and damage states. This record group only defines the physical object of the rail and does not mean that the records within the group belong to the same damage evolution process. In this embodiment, the first dual-temporal damage record, the second dual-temporal damage record, the third dual-temporal damage record, and the fourth dual-temporal damage record are received. The rail entity identifier of all four records is "L01-Up-1 strand-Left rail-R125", and they are therefore classified into the first rail entity record group. Another dual-temporal damage record with the same mileage location but a rail entity identifier of "L01-Down-1 strand-Left rail-R125" is received. Due to the different track direction, it is classified into the second rail entity record group. Through precise grouping at the entity level, erroneous continuation of damage records at the same mileage but with different track directions or different rail sides is avoided. The rail entity record groups are arranged according to monitoring time, and adjacent dual-temporal damage records are generated into adjacent candidate records. Specifically, the dual-temporal damage records in the first rail entity record group are standardized in time format, and the monitoring time is uniformly converted to the time position relative to the start time of this flaw detection operation. The monitoring time accuracy is maintained to the millisecond, and the monitoring time is not rounded. The confirmation time only indicates the order in which the records enter the management platform and does not participate in the damage evolution sorting in this step. The records in the group are stably arranged from earliest to latest according to the monitoring time. Stable arrangement means that when the monitoring times are different, they are arranged according to the monitoring time; when the monitoring times are the same, they are arranged according to the confirmation time; when both the monitoring time and the confirmation time are the same, they are arranged according to the dual-temporal record identifier. This arrangement rule ensures that the same data maintains a consistent intra-chain order when processed repeatedly. After the arrangement is completed, the preceding and following dual-temporal damage records that appear consecutively in time are combined into adjacent candidate records. Each adjacent candidate record includes a candidate record identifier, rail entity identifier, preceding record identifier, following record identifier, preceding monitoring time, following monitoring time, preceding damage interval, following damage interval, preceding damage type, following damage type, and the maintenance closure status between the two records. Adjacent candidate records are relationships to be verified and cannot be directly used as continuation relationships in the entity damage chain. In this embodiment, the first dual-temporal damage record is located at the first monitoring time, the second dual-temporal damage record is located 4 hours after the first monitoring time, the third dual-temporal damage record is located 9 hours after the first monitoring time, and the fourth dual-temporal damage record is located 22 hours after the first monitoring time. After being arranged according to the monitoring time, the first adjacent candidate record between the first and second records, the second adjacent candidate record between the second and third records, and the third adjacent candidate record between the third and fourth records are generated sequentially. This process ensures that subsequent interval verification and type verification are only applied to record relationships with temporal continuity potential. For adjacent candidate records, damage interval intersection verification and damage type succession verification are performed to generate damage succession records; specifically, damage interval intersection verification is performed for each adjacent candidate record. The start and end mileage of the damage interval are derived from dual-temporal damage records, and the positioning error is derived from the rail damage monitoring equipment calibration report. In this embodiment, the positioning error is ±0.5 m, and the equipment calibration error is within ±0.1 m to ±1 m. When the range is m, the damage interval is expanded according to the verification value of the corresponding equipment; when there is no valid verification value, the corresponding record is retained as an interval pending verification; when the intervals intersect for verification, the starting mileage of the damage in the previous record and the subsequent record are expanded by one positioning error in the direction of decreasing line mileage, and the ending mileage of the damage is expanded by one positioning error in the direction of increasing line mileage; when the two expanded damage intervals have a common mileage range, an interval intersection mark is generated; when there is no common mileage range, an interval separation mark is generated; the interval intersection mark indicates that the two records have spatial conditions pointing to the same physical damage location; for adjacent candidate records with interval intersection marks, the damage type acceptance verification continues; the damage type acceptance relationship comes from the rail damage code table and damage evolution relationship table adopted by the railway operating unit; the damage evolution relationship table adopts a discrete correspondence method, recording the previous damage type, the subsequent damage type that can be continued, and the subsequent damage type that cannot be continued; the same damage type can be accepted; suspected rail head internal cracks can be continued with the verified rail head internal transverse cracks; rail head internal transverse cracks cannot be continued with rail surface scratches or rail bottom corrosion. The type acceptance verification does not use similarity scoring or weighting calculation. In this embodiment, the damage range of the first dual-temporal damage record is from K125+429.8 m to K125+430.4 m, the damage range of the second dual-temporal damage record is from K125+429.9 m to K125+430.5 m, the damage range of the third dual-temporal damage record is from K125+430.0 m to K125+430.7 m, and the damage range of the fourth dual-temporal damage record is from K125+429.9 m to K125+430.3 m. The damage type of all four records is transverse crack inside the railhead. After positioning error expansion, the three adjacent candidate records all have a common mileage range, and the damage type acceptance relationship is allowed. Based on this, damage acceptance records are generated respectively. Each damage acceptance record includes the previous record identifier, the next record identifier, the common mileage range, the type acceptance result, and the monitoring time order. The common mileage range retains the overlapping positions of two damage records, without replacing the original damage interval. This process simultaneously satisfies both physical location continuity and damage type continuity, preventing damage records of different locations or types from being connected to the same entity's damage chain simply because they are close in time. Damage acceptance records that do not span the maintenance closure record are sequentially linked according to monitoring time to generate a physical damage chain. Specifically, maintenance closure verification is performed on the damage acceptance records. The maintenance closure record originates from the maintenance management interface and includes maintenance work order identifier, rail entity identifier, maintenance section, maintenance method, acceptance time, and closure status. The closure status is 0 or 1, where 0 indicates that no maintenance acceptance record meeting the coverage conditions has been obtained, and 1 indicates that a record has been obtained that covers the damage section and has passed acceptance. Based on the rail entity identifier corresponding to the damage acceptance record and maintenance closure record, the maintenance closure time is then verified to ensure it falls within the time frame between the previous and subsequent monitoring times. Whether the maintenance interval or repair interval covers the common mileage range corresponding to the damage acceptance record; if no maintenance closure record that meets the time and interval conditions is found, the damage acceptance record is retained as a continuous acceptance record; if a maintenance closure record that meets the conditions and has a closure status of 1 is found, the corresponding damage acceptance record is marked as a closed interruption record; the damage acceptance records in the continuous acceptance status are connected sequentially according to the monitoring time; the chain head record uses the rail entity identifier and the first dual-temporal record identifier to generate a physical damage chain identifier; subsequent records are connected sequentially through the previous record identifier and the next record identifier; the physical damage chain includes at least a physical damage chain identifier, a rail entity identifier, and a chain head. The record includes identifiers, chain tail record identifiers, dual-temporal damage record order, damage state change order, and maintenance closure status. When a closure blocking state is encountered, the current physical damage chain is terminated, and the dual-temporal damage record after the closure record becomes the chain head record of the new physical damage chain. In this embodiment, there is no maintenance closure record between the first adjacent candidate record and the second adjacent candidate record. The first dual-temporal damage record, the second dual-temporal damage record, and the third dual-temporal damage record are consecutive according to the monitoring time to generate the first physical damage chain. There is an accepted track replacement maintenance closure record between the third dual-temporal damage record and the fourth dual-temporal damage record, and the closure time is located at... Between the monitoring times of the two records, the maintenance interval covers a common mileage range. Therefore, the third damage acceptance record is marked as a closed interruption state, and the fourth dual-temporal damage record serves as the head record of the second physical damage chain. When the continuation method of unverified maintenance closure state is adopted, the four dual-temporal damage records will be connected to the same damage chain. After adopting the processing method of this embodiment, the three records before maintenance enter the first physical damage chain, and the fourth record after maintenance enters the second physical damage chain. This result ensures that the physical damage chain is consistent with the actual maintenance boundary of the rail, providing a continuous and traceable data foundation for the subsequent division of damage evolution periods and the attribution of transportation task stages.
[0025] The present invention is further configured such that the confirmation delay task module includes: Using the monitoring time in the dual-temporal damage record as the starting point and the confirmation time as the ending point, a confirmation lag period is generated. Specifically, this embodiment follows the aforementioned railway mainline rail flaw detection scenario. The confirmation lag task module receives the dual-temporal damage record output by the dual-temporal record generation module. The input objects include dual-temporal record identifier, rail entity identifier, damage interval, damage type, damage status, monitoring time, confirmation time, and maintenance closure status. The dual-temporal damage record is sent according to an event-triggered method. Each time the review and confirmation of a damage monitoring record is completed, a confirmation lag period generation process is triggered. The monitoring time comes from the satellite time synchronization unit of the rail damage monitoring equipment, representing the actual time when the damage status is monitored by the equipment. The confirmation time comes from the transportation operation and maintenance management platform server, representing the time when the review status changes to confirmation passed. Both times use the same time reference, maintaining time accuracy to the millisecond. After receiving dual-temporal damage records, time format unification, time reference verification, and confirmation status verification are performed sequentially. If the confirmation status fails, the system remains in a pending state. If the confirmation time is earlier than the monitoring time, a time anomaly record is generated. If the confirmation time is equal to the monitoring time, an empty confirmation lag period is generated, and transportation tasks during the lag period are no longer searched. If the confirmation time is later than the monitoring time, the monitoring time is used as the start point of the confirmation lag period, and the confirmation time is used as the end point. The confirmation lag period adopts a time boundary rule where the start point includes the lag period, but the end point does not. That is, transportation tasks occurring during the monitoring time are excluded from the time boundary. Transportation tasks can enter this time period, and transportation tasks occurring at the confirmation time are transferred to the task processing scope after confirmation; this boundary rule avoids the same transportation task from entering the confirmation lag task sequence and the confirmation pending verification task sequence at the same time; in this embodiment, the first dual-temporal damage record corresponds to the transverse crack inside the rail head, the monitoring time is recorded as the first monitoring time, and the confirmation time is recorded as the first confirmation time. The first confirmation time is located at 3 hours, 17 minutes and 33 seconds after the first monitoring time; after the time format and confirmation status are verified, the first confirmation lag time period is generated with the first monitoring time as the starting point and the first confirmation time period as the ending point, and the first dual-temporal record identifier is associated with this time period; The system filters transportation tasks from the transportation task records that have actual transit times falling within the confirmed lag period and whose task status is "executed," generating time candidate tasks. Specifically, transportation task records are obtained through the transportation scheduling interface. These records originate from the transportation scheduling system and the train operation control system, and include the transportation task identifier, train identifier, planned operating section, actual operating section, planned transit time, actual transit time, and task status. The train operation control system uses a 1... The Hz system reports train position status. When a train leaves a track section, it generates an actual passage record for that section based on the section entry record, section departure record, and train position status. The actual passage time uses the moment when the train's front end first enters the track section corresponding to the damaged section. If the train position status is temporarily missing, the server time in the track section entry record is used. If both the section entry record and position status are missing, the corresponding transportation task is marked as a passage time pending verification and is not included in the time candidate task list. Transportation task status includes planned, in progress, executed, and canceled. Only tasks in the executed status are filtered for confirmation lag periods; planned, in progress, and canceled tasks are retained in their original task statuses. After obtaining the transportation task record, duplicate records are filtered according to the transportation task identifier, and then the actual passage time is converted to the unified time reference used in the dual-temporal damage record. Transportation tasks whose actual passage time falls between the start and end of the confirmation lag period and whose task status is executed are generated as time candidate tasks. Each time candidate task retains the transportation task identifier, train identifier, actual passage time, actual operating section, and task status for the next step of spatial coverage verification. In this embodiment, transportation task T301 completes passage through the corresponding track section 31 minutes after the first monitoring time, transportation task T305 completes passage at 1 hour and 43 minutes, and transportation task T309 completes passage at 2 hours and 36 minutes. All three tasks are in the "executed" status, and their actual passage times all fall within the first confirmation lag period, thus generating three time candidate tasks. Transportation task T312 completes passage after the first confirmation time and does not enter the time candidate task. Transportation task T315 is canceled within the confirmation lag period and also does not enter the time candidate task. Coverage verification is performed on the actual operating section of the time candidate task and the damage interval in the dual-temporal damage record to generate a damage crossing task. Specifically, track space standardization is performed on the actual operating section of the time candidate task. The actual operating section is represented by the track code, running direction, track identification, section start mileage and section end mileage. The relevant fields are derived from the track section occupancy record of the train operation control system. Damage sections and rail entity identifiers are derived from dual-temporal damage records; line codes, directions of travel, and track identifiers use unified codes from the transportation scheduling basic data. Tasks that fail code conversion enter the operational section pending verification state; spatial coverage verification processes line codes, directions of travel, track identifiers, and mileage ranges in sequence; for time candidate tasks, if the line codes, directions of travel, and track identifiers are consistent with the dual-temporal damage records, then it is verified whether the actual operational section contains the damage section; when the starting mileage of the actual operational section is before the starting point of the damage section and the ending mileage is after the ending point of the damage section, a section coverage record is generated; if any of the directions of travel, track identifiers, or mileage ranges fails verification, a section mismatch record is generated; time candidate tasks that pass spatial coverage verification are used to generate damage traversal tasks; a damage traversal task represents an executed transportation task that actually passes through the corresponding damage location during the period when the damage is detected but the detection conclusion has not yet been confirmed. Each damage crossing task includes a damage crossing record identifier, a dual-temporal damage record identifier, a transportation task identifier, actual passage time, actual operating section, and task status. This record retains the correspondence between the transportation task and the specific damage record, without changing the original operation data of the transportation task. In this embodiment, the actual operating sections of transportation tasks T301, T305, and T309 all belong to the L01 line in the up direction, and the section range covers the damage interval from K125+429.8 m to K125+430.4 m. The three tasks generate damage crossing tasks respectively. In addition, the actual passage time of transportation task T210 is within the first confirmation lag period, but its actual operating section belongs to the L01 line in the down direction. The operating direction fails the verification, generating a section mismatch record, and it does not enter the scope of the damage crossing task. Damage crossing tasks are sequentially assigned based on actual passage time. Dual-temporal damage record identifiers are associated with corresponding tasks to generate a confirmation lag task sequence. Specifically, damage crossing tasks undergoing spatial coverage verification are arranged from earliest to latest according to actual passage time; if actual passage times differ, they are arranged chronologically; if actual passage times are the same, they are arranged according to transport task identifiers, ensuring consistent order when processing identical data repeatedly. After arrangement, a preceding task identifier and a following task identifier are recorded for each damage crossing task. The preceding task identifier for the first task remains empty, and the following task identifier for the last task remains empty. The first dual-temporal damage record identifier is associated with the arranged damage crossing tasks. Then, the preceding task identifier, the last task identifier, the number of tasks, the actual passage time sequence, and the corresponding damage interval are combined to generate a confirmation lag task sequence. The confirmation lag task sequence represents the order of executed transport tasks that actually passed through the damage location during the period from the completion of monitoring to verification confirmation for the same damage monitoring record. The number of tasks is derived from the number of damage traversal tasks that have passed time verification and spatial coverage verification. It is only used as a sequence integrity verification field and does not participate in risk scoring. When the confirmed delayed task sequence is empty, a marker for a traversal task without delay is generated, and the subsequent task attribution correction module does not perform historical task attribution cancellation. When the confirmed delayed task sequence is not empty, the task sequence is sent to the damage task continuation module and the task attribution correction module as the task scope for the original stage attribution verification of the transportation task and the local correction of the late record. In this embodiment, transportation tasks T301, T305, and T309 are sequentially continuated according to the actual passage time, with T301 as the first task and T309 as the last task. The three tasks are associated with the first dual-temporal damage record identifier to generate the first confirmed delayed task sequence. When using the processing method that only uses the confirmation time as the starting point of the damage record, the three executed transportation tasks are all located before the confirmation time and cannot enter the damage task scope. After adopting the processing method of this embodiment, the three transportation tasks are completely retained in the first confirmed delayed task sequence, providing continuous task data for subsequent damage stage attribution and historical operation review.
[0026] The present invention is further configured such that dividing the damage evolution period based on adjacent monitoring times in the solid damage chain includes: The dual-temporal damage records in the physical damage chain are arranged according to monitoring time to generate the record order within the chain. Specifically, the physical damage chain identifier and all its contained dual-temporal damage records are obtained. Each record includes at least a record identifier, rail physical identifier, monitoring time, confirmation time, damage interval, and damage status. The monitoring time uses the equipment clock time written by the flaw detection equipment when the damage signal reaches the equipment output condition. The confirmation time uses the server time written by the operation and maintenance management platform when the verification process enters the confirmation completion state. The flaw detection equipment clock and the server clock are synchronized through the railway unified time source, and the time is uniformly converted to millisecond precision. Before processing, the uniqueness of the record identifier, the integrity of the monitoring time, and the consistency of the physical damage chain to which each record belongs are verified. For the same record identifier formed by interface retransmission, only the record with the higher version number is retained. For status revision records formed in the same monitoring batch, the last confirmed version is retained according to the version number, and the original version is used as audit data storage and is not included in the time period division. The remaining records are arranged in ascending order of monitoring time using stable merge sort. When the monitoring time is the same, they are arranged in order of equipment event number and record identifier to maintain the repeatability of the sorting results. The sorting position, the identifier of the preceding record, and the identifier of the following record are written into the in-chain order table to form the in-chain record order. The in-chain record order represents the chronological relationship of each monitoring event of the same damaged entity on the actual monitoring timeline. Its data source is the monitoring time and is not affected by the order of confirmation completion. For example, a damage chain of an entity includes first, second, and third bitemporal damage records. The second record is formed four hours after the first monitoring time, and the third record is formed nine hours after the first monitoring time. Even if the third record is confirmed before the second record, the in-chain record order is still arranged as the first record, the second record, and the third record, thus providing a consistent time basis for subsequent time period boundaries. Using the monitoring time of the previous pair of temporal damage records as the starting point and the monitoring time of the next pair of temporal damage records as the ending point, a left-closed, right-open damage evolution period is generated. Specifically, adjacent records are accessed sequentially according to the order of records in the chain. The monitoring time of the previous record is written into the starting point of the period, and the monitoring time of the next record is written into the ending point of the period. The starting point inclusion flag is set to include, and the ending point inclusion flag is set to exclude, thus generating a left-closed, right-open damage evolution period. The damage evolution period represents the time range from when a damage monitoring result begins to be applicable until the next monitoring result is formed. The time period boundary directly adopts the time of adjacent monitoring events, without setting a fixed duration. The monitoring time of adjacent records remains strictly increasing after processing in step one, so each period has an effective duration. The left-closed, right-open boundary rule ensures that a transportation task that occurs exactly at the next monitoring time enters the next period, avoiding the same task being assigned to both periods simultaneously. Taking the aforementioned three records as an example, the first period starts from the first monitoring time and ends at the second monitoring time; the second period starts from the second monitoring time and ends at the third monitoring time. The second monitoring time corresponds to the exclusion endpoint of the previous time period and the inclusion starting point of the next time period. After the division is completed, the beginning and end connection verification is performed on adjacent time periods to check whether the endpoint of the previous time period is the same as the starting point of the next time period, and to check whether there is overlap or gap between time periods; if the verification is successful, the damage evolution time period is output; if the verification fails, the abnormal record is retained and the task assignment processing of the corresponding entity damage chain is stopped. The damage status, damage range, and record identifier of the previous dual-temporal damage record are associated with the corresponding damage evolution period to generate a period status record. Specifically, for each damage evolution period, the previous dual-temporal damage record corresponding to its starting point is accessed, and the damage status, damage range, and record identifier of that record are written into the period status data item. At the same time, the entity damage chain identifier and the period identifier are associated to form a period status record. The period status record represents the applicable damage status and spatial range within a damage evolution period and is the direct input used by the damage task continuation module when assigning the transportation task stage. The damage status comes from the output results of the flaw detection equipment and the verification results, and can adopt the level code specified by the operation and maintenance rule base. This embodiment adopts a four-level code from D1 to D4, with the level order from low to high. The specific handling rules are stored in the rail operation and maintenance rule base. This step only saves the verified status code and does not recalculate the damage level. The damage range is represented by the track mileage coordinates, including the start point of the range, the end point of the range, the track direction, and the track identifier. The end point of the range comes from the synchronization result of the mileage positioning equipment and the flaw detection signal. Before writing, it is uniformly converted to metric mileage, and the smaller mileage is set as the start point of the range. The record identifier uses a unique character code generated by the operation and maintenance management platform to trace the data source of the time period status. Taking the aforementioned record as an example, the damage interval corresponding to the first record is 0.6 meters before and after a certain mileage point, and the damage status is D1. The first time period is associated with this interval, the D1 status, and the first record identifier. The second record shows that the damage interval extends 0.1 meters along the line direction and the status is updated to D2. The second time period is associated with the interval and the D2 status in the second record. This association process maintains a one-to-one correspondence between status, spatial location, and source record, enabling subsequent transportation tasks to call the damage record that is actually applicable at the time of passage. Starting with the monitoring time of the chain tail dual-temporal damage record and ending with the current maintenance processing time, a chain tail evolution period is generated. The chain tail damage status is associated with the chain tail evolution period. Specifically, the last record in the chain's record sequence is accessed, its monitoring time is written to the starting point of the chain tail evolution period, the time recorded by the platform's unified clock at the start of this maintenance processing transaction is written to the ending point, and the damage status, damage range, and record identifier of the chain tail record are associated with this period. The "current maintenance processing time" represents the transaction time frozen when the maintenance management platform executes the attribution of this damage task or the verification of the transportation plan. It remains unchanged during the same processing process, and its value must not be earlier than the chain tail monitoring time. If an equipment clock anomaly occurs, causing the current maintenance processing time to be earlier than the chain tail monitoring time, the generation of the chain tail evolution period is stopped, a clock calibration event is recorded, and processing is resumed after time synchronization is completed. The chain tail period is regenerated when a new damage record, transportation plan update, or maintenance verification task is triggered. After a new dual-temporal damage record is connected to the entity damage chain, the original chain tail period is closed at the monitoring time of the new record, and a new chain tail period is established by the new record. For historical entity damage chains that have already formed maintenance closure records, the chain tail expansion is stopped and the time period data formed before closure is retained. In this embodiment, the third record was formed nine hours after the first monitoring time, and the current maintenance process occurred twelve hours after the first monitoring time, thus generating a three-hour chain tail evolution period, and associating the D3 state of the third record with the corresponding damage interval. During verification, all time periods are checked sequentially, and the first time period, the second time period, and the chain tail time period continuously cover the first monitoring time to the current maintenance process time; a boundary test task is set at the second and third monitoring times, and the test results all fall only into the time period after the monitoring time. Even if the confirmation order of the three records is the first record, the third record, and the second record, the generated results still maintain the monitoring order of the first record, the second record, and the third record, thereby providing continuous and non-overlapping time period data for the unique stage assignment of the subsequent damage task continuation chain.
[0027] The present invention is further configured such that the transportation task whose actual transit time falls within the damage evolution period and whose operating segment covers the damage interval is uniquely assigned to the corresponding damage evolution period, and the damage task succession chain is generated according to the actual transit time, including: The actual transit time of transportation tasks is mapped to the damage evolution period to generate candidate tasks for that period. Specifically, transportation task records that are in an executed state and have valid actual location sequences are obtained from the transportation scheduling platform, and the transportation task times are converted to a unified time base that is the same as the damage evolution period. Duplicate records with the same task identifier and the same sampling time generated by interface retransmission are deduplicated. Isolated location points where the running speed exceeds the maximum allowable speed recorded in the line's equipment ledger are marked as anomalies and are not used for actual transit time correction. The maximum allowable speed is derived from the line infrastructure ledger and is only used to identify location jumps that do not conform to the continuity of train operation; it is not used in damage risk assessment. The actual transit time is preferentially based on the train entry time recorded by the track section occupancy equipment. If a corresponding occupancy event is missing, the time when the train crosses the center mileage of the damaged section is found from the valid location points adjacent to both sides of the damaged section, and time interpolation is performed according to the mileage change ratio between the two location points. Interpolation stops when the time interval between adjacent valid location points exceeds three sampling cycles, and the corresponding task is marked as a time-pending verification task to avoid estimating the transit time based on long-term missing data. Subsequently, an ordered time index is established according to the start time of each time period, and the actual transit time is sequentially matched with the damage evolution time period. When the actual transit time is greater than or equal to the start time of the time period and earlier than the end time of the time period, the transportation task identifier, the actual transit time, and the corresponding time period identifier are written into the candidate record to generate a time period candidate task. When the actual transit time is exactly equal to the boundary point between adjacent time periods, it is only assigned to the next time period starting from that boundary point, forming a unique candidate relationship from the time dimension. Coverage verification is performed on the actual operating section of the candidate task for the time period and the damaged section in the time period status record to generate a successful task. Specifically, the time period status record corresponding to the candidate task is called to obtain the damaged section, line direction, track identifier, and damage status. At the same time, the line direction, track identifier, and first and last valid mileage covered by the actual position sequence are obtained from the transportation task record to generate the actual operating section of the transportation task. The mileage data is uniformly converted to metric coordinates that increase along the line direction. For reverse operation tasks, the first and last mileages are swapped first, and then the original line direction identifier is retained. The positioning allowable error adopts the error value in the calibration record of the train operation monitoring equipment, which is 0.5 meters in this embodiment. This error is only used to compensate for the equipment measurement deviation between the endpoint of the operating section and the endpoint of the damaged section. The line identifier, direction identifier, and track identifier of the actual operating section and the damaged section are checked in sequence to see if they are consistent. Then, it is checked whether the starting point of the actual operating section is before the starting point of the damaged section and whether the ending point of the actual operating section is after the ending point of the damaged section. When the endpoint difference is within the allowable error range of the equipment positioning, it is treated as an endpoint connection. After all verifications are passed, the transportation task identifier, time period identifier, damage section, and actual passage time are associated to generate a phased passage task. A phased passage task represents a transportation task that actually and completely passes through the damage section within the corresponding damage evolution period. Transportation tasks that meet the time requirements but are in the opposite direction, on different tracks, or turn back before the damage section will not be included in the phased passage task set, thus ensuring that the task phase affiliation satisfies both the time succession relationship and the actual spatial crossing relationship. Unique attribution verification is performed based on the entity damage chain identifier and the transportation task identifier. Transportation tasks within the same entity damage chain retain one stage attribution. A unique verification key is formed using the entity damage chain identifier and the transportation task identifier. The current damage task attribution table is queried item by item for each stage-passing task. If no identical unique verification key exists, the corresponding stage-passing task is written into the attribution table. If identical unique verification keys and identical stage identifiers exist, they are treated as interface retransmissions or duplicate calculation records, and the record with the newer processing version is retained. If identical unique verification keys exist but the stage identifiers are inconsistent, the entity damage chain versions used in the two stages and the inclusion relationship between the actual passage time and the time period boundary are verified separately. Only the stage attribution belonging to the current valid entity damage chain version and conforming to the left-closed right-open boundary rule is retained, and the old version attribution is transferred to the history record. If both stages belong to the current version, the time correspondence record formed in step one is called again for boundary verification. If a unique result still cannot be obtained, the continuation processing of the transportation task is suspended and an attribution anomaly record is generated to prevent ambiguous stage attribution from entering the transportation operation and maintenance update process. The entity damage chain identifier comes from the entity damage chain generation module, and the transportation task identifier comes from the transportation scheduling platform. Both of them use globally unique character encoding. This composite unique verification mechanism maintains the idempotency of processing under the conditions of duplicate data access and chain version update, so that the same transportation task retains only one valid stage attribution in the same entity damage chain. Based on the actual passage time, tasks are sequentially passed through stages. Stage identifiers, damage states, and task identifiers are associated to generate a damage task succession chain. Specifically, tasks that have passed the unique attribution verification are arranged in ascending order of actual passage time. When actual passage times are the same, they are stably sorted according to the character order of the transport task identifiers to ensure a consistent order during repeated execution. The preceding and following task identifiers are written to the sorted tasks in sequence. The stage identifier of the corresponding damage evolution period, the damage state in the period status record, and the transport task identifier are associated with the same chain node, and the entity damage chain identifier and the current chain version are also associated to generate the damage task succession chain. The damage task succession chain represents the ordered succession relationship of transport tasks along the same entity damage chain according to actual passage time. The chain node stores the applicable damage stage and damage state when the task passes, serving as input for the subsequent task attribution correction module to compare the original attribution with the updated attribution. Based on the first monitoring time, the first damage evolution period lasts four hours and is associated with state D1; the second damage evolution period lasts from the fourth hour to the ninth hour and is associated with state D2; and the chain tail evolution period lasts from the ninth hour to the current maintenance processing time and is associated with state D3. Transport tasks T301, T305, and T309 passed through the damage zone 31 minutes, 1 hour 43 minutes, and 2 hours 36 minutes after the first monitoring time, respectively, and were all assigned to the first stage. Task T320 passed through exactly at the fourth hour and was assigned to the second stage according to the left-closed-right-open rule. Task T324 passed through at the sixth hour 15 minutes and was assigned to the second stage. Task T330 passed through at the tenth hour 20 minutes and was assigned to the end of the chain stage. Another task that met the first time period requirement but ran on the opposite track was excluded after verification in step two. Finally, a damage task succession chain was formed with T301, T305, T309, T320, T324, and T330 following in sequence. After verification, there were no tasks with duplicates, double assignments at time period boundaries, or tasks that did not actually cross the damage zone, completing the closed-loop processing from operational data acquisition, spatiotemporal correspondence, unique assignment to chain output.
[0028] The present invention is further configured such that, according to the monitoring time, accessing the corresponding record and canceling the original stage attribution of the transportation task within the delayed task sequence includes: The dual-temporal damage records in the same entity damage chain are arranged according to the monitoring time and confirmation time, generating monitoring order records and confirmation order records. Specifically, when the verification platform completes the confirmation of a dual-temporal damage record, it obtains all dual-temporal damage records in the entity damage chain to which the record belongs, verifies the consistency of rail entity identifier, track direction, track identifier, and entity damage chain identifier, and checks whether the record identifier is unique and whether the confirmation time is earlier than the monitoring time. The monitoring time comes from the device clock of the flaw detection equipment that generates the damage monitoring event, and the confirmation time comes from the server clock when the verification process enters the confirmation completion state. Both types of time are converted to millisecond-level time under the unified railway time source. For records with the same identifier generated by interface retransmission, the record with the higher version number is retained. Then, a stable merge sort is used to process the two record copies separately: the first copy is sorted in ascending order by monitoring time, and if the times are the same, it is sorted by device event sequence number and record identifier in turn; the second copy is sorted in ascending order by confirmation time, and if the times are the same, it is sorted by review serial number and record identifier in turn. For each sorting result, a sequence number, a preceding record identifier, and a following record identifier are written to generate a monitoring sequence record and a confirmation sequence record, respectively. The monitoring sequence record indicates the order in which damage events are actually monitored, and the confirmation sequence record indicates the order in which damage events are reviewed and enter maintenance processing. For example, the first record is formed at the first monitoring time and is confirmed first, the second record is formed in the fourth hour but is confirmed in the eleventh hour, and the third record is formed in the ninth hour and is confirmed in the tenth hour. The monitoring order is first record, second record, and third record, and the confirmation order is first record, third record, and second record, providing two sets of sequential data that can be matched item by item for subsequent identification of late confirmation records. Based on the record identifier corresponding to the monitoring sequence record and confirmation sequence record, a sequence mismatch record is generated for dual-temporal damage records where the preceding or following records are inconsistent. Specifically, using the record identifier of the dual-temporal damage record as the corresponding key, the monitoring sequence record and the confirmation sequence record are concatenated one by one, and the preceding and following record identifiers of the same record in the two sets of sequences are compared. When there is a difference between the preceding or following record identifier, the current record identifier, monitoring sequence number, confirmation sequence number, preceding and following sequence identifiers of monitoring and confirmation, entity damage chain version, and the current round of confirmation event marker are written into the mismatch data item to generate a sequence mismatch record. The sequence mismatch record indicates that the same damage record is inconsistent in the actual monitoring timeline and the verification confirmation timeline. The adjacency relationships within the interaxial structure differ, and their formation is based on inconsistent identifier-level adjacency relationships, without using similarity scoring or empirical thresholds. For adjacent records involved in the same mismatch, they are grouped into the same mismatch group according to the entity damage chain identifier and the identifier of the confirmed event in this round. Among them, records newly confirmed in this round but not yet connected to the monitoring time location are marked as records to be connected, and the remaining records are marked as affected adjacent records. In the aforementioned example, the second record's preceding record in the confirmation order is the third record and there is no subsequent record, while its preceding record in the monitoring order is the first record and its subsequent record is the third record, thus it is marked as a record to be connected. Changes in the adjacency relationship between the first and third records are considered as affected information and grouped into the same mismatch group. This processing preserves the source of the mismatch and the affected boundary, avoiding changes to the actual evolution order of the damage event solely based on the order of confirmation. Based on the monitoring time of the sequence mismatch record, obtain the adjacent monitoring record corresponding to the access location and remove the original connection relationship between adjacent monitoring records. Specifically, access the predecessor record identifier and successor record identifier of the record to be accessed in the monitoring sequence record, and search for the corresponding record in the current entity damage chain. If both predecessor and successor records exist, check whether the connection relationship between the predecessor record and the successor record is saved in the current chain, and check whether the connection relationship belongs to the entity damage chain version frozen at the beginning of this round of processing. After both checks pass, change the valid status of the connection relationship to pending replacement, and save the original predecessor record identifier, the original successor record identifier, and the original chain version, and remove the original connection relationship between the two adjacent monitoring records. When the record to be accessed is at the head of the chain, only remove the original chain head mark of its successor record; when it is at the tail of the chain, only remove the original chain tail mark of its predecessor record. The processing is executed within the same database transaction and uses the entity damage chain version number for concurrent verification. If it is found that the chain version has changed during processing, roll back the current transaction and re-execute with the latest chain version to prevent the chain structure from being destroyed when two late-confirmed records are accessed at the same time. In the aforementioned example, before the second record is confirmed, the current valid chain only contains the connection relationship between the first record and the third record; the monitoring time of the second record is between the two, so the original connection relationship between the first record and the third record is marked as to be replaced, reserving a unique position for the second record to be connected; The sequence mismatch record is connected between the corresponding adjacent monitoring records to generate an updated intra-chain order. Specifically, the record to be connected is written to the connection position, and two continuation relationships are established: the preceding record points to the record to be connected and the record to be connected points to the following record. At the same time, the preceding identifier, following identifier, and intra-chain order number of the three records are updated. When connecting at the beginning or end of the chain, the beginning identifier or end identifier is updated respectively. After the connection is completed, sequential verification is performed from the beginning to the end of the physical damage chain. The records are checked in turn to see if the record identifier is duplicated, if the monitoring time of the later record is earlier than the monitoring time of the previous record, if the continuation relationship spans the maintenance closure record, and if all valid records can be accessed continuously from the beginning to the end of the chain. After the verification is passed, the original chain version is incremented by one version, the new continuation relationship is submitted, and an updated intra-chain order is generated. If the verification fails, all modifications in steps three and four are rolled back, and the sequence mismatch record is retained for anomaly handling. After the connection is completed in the above example, the physical damage chain is updated from the first record to the third record to the first record, the second record, and the third record, and the record order is consistent with their respective monitoring times. The method of partial chain breakage and partial insertion is adopted, which only changes the connection relationship of the record to be connected, while keeping other records in the chain and their source data unchanged; The system maps the delayed confirmation task sequence corresponding to the sequence mismatch record to the original damage task continuation chain, and cancels the original stage assignment of the corresponding transportation task. Specifically, it calls the delayed confirmation task sequence corresponding to the second record, which includes transportation tasks that actually passed through the damage interval from the monitoring time of the second record to the confirmation time of the second record. Then, it uses the entity damage chain identifier and the transportation task identifier to form a corresponding key, and maps it item by item to the original damage task continuation chain saved before this round of chain update. When the mapping is successful, the valid status of the original stage assignment record is changed to "cancelled", and the original stage identifier, original damage status, original actual passage time and original chain version are retained. The transportation task identifier is also written to the set of tasks to be reassigned. When the mapping fails, a task-corresponding exception record is generated, without changing the stage assignment of other transportation tasks. Canceling the original stage assignment means terminating the original stage assignment record from participating in subsequent operation and maintenance verification, while retaining the original record as... For the comparison of old and new attributions, transportation tasks and their operational data are not deleted. In the aforementioned example, the confirmation lag task sequence of the second record includes four transportation tasks that passed through the damage interval at the fourth hour, the sixth hour and fifteen minutes, the eighth hour and forty minutes, and the tenth hour and twenty minutes. The first three tasks originally belonged to the corresponding stage of the first record, and the fourth task originally belonged to the corresponding stage of the third record. All four original stage attributions are marked as revoked and enter the task set to be reassigned. Transportation tasks that passed before the fourth hour retain their original attributions. When the same confirmation event is executed repeatedly, the revoked status and mismatch group identifier prevent revocation again. The processing result is verified to obtain one item of updated in-chain order, four items of revoked stage attribution, and four transportation tasks to be reassigned. These are then passed to the subsequent damage evolution period re-division process, completing the data closed loop from order mismatch identification, in-chain record access to the targeted revocation of affected tasks.
[0029] The present invention is further configured such that, based on the updated damage evolution period, the original damage task succession chain and the updated damage task succession chain are mapped to generate a task ownership change segment, including: The damage evolution period before and after the order mismatch record is redefined based on the order within the update chain, generating an update period record. Specifically, after the verification platform confirms the delayed confirmation damage record, the update period processing transaction is initiated. Input objects include the order within the update chain, the order mismatch record, the original damage evolution period, the dual-temporal damage record, and the current entity damage chain version. The dual-temporal damage record originates from damage monitoring events generated by the 50 MHz ultrasonic flaw detection equipment and the 10 Hz odometer positioning equipment. The monitoring time uses the equipment event time, and the confirmation time uses the verification platform completion time. Both types of time are uniformly converted to iron. The timing is measured in milliseconds from the time source. Before processing, the uniqueness of the record identifier in the updated chain sequence is verified, the monitoring time is sequentially increased, and the chain version is consistent with the result of the order mismatch processing. The record to be accessed, the preceding record, and the following record are obtained from the order mismatch records. Only the local time periods involved in the three are re-divided. The unaffected damage evolution time periods continue to use the original time period records. When the record to be accessed is located between two records, the time period from the original preceding record to the following record is terminated. The first update time period is established from the monitoring time of the preceding record to the monitoring time of the record to be accessed. A second update period is established from the time of the subsequent record monitoring time; when the record to be accessed is at the beginning or end of the chain, a corresponding update period is established at the beginning or end of the chain; each update period adopts a left-closed and right-open boundary, and writes the damage status, damage interval and record identifier of the dual-temporal damage record corresponding to the start of the period into the period status item; the stage identifier is generated when the corresponding dual-temporal damage record first enters the physical damage chain, and is always bound to the record identifier. When the chain version is updated, the stage identifier is continued to be used to prevent the transportation task from being mistakenly recorded as a stage change simply because of the version change; the update period record represents the combination record of time boundary, stage identifier, damage status and damage interval re-formed after the access of the mismatched record; in this embodiment, the first record is formed at the first monitoring time, the second record is formed four hours later, and the third record is formed nine hours later. The second record is confirmed later than the third record. After the second record is accessed, the original period from the first record to the third record is re-divided into the period from the first record to the second record and the period from the second record to the third record, and the damage status of the first record and the second record are associated respectively, so that the update period boundary is consistent with the actual damage monitoring order; The transportation tasks assigned to the cancelled stage are reassigned to the updated time period record according to their actual passage time and actual operating section, generating an updated damage task succession chain. Specifically, the transportation tasks whose original stage assignments have been cancelled are obtained from the previous processing step, and the actual position sequence, actual passage time, line direction, and track identifier of the corresponding task are obtained from the train operation monitoring interface. The train operation monitoring equipment reports the position at a frequency of one hertz, and the track section occupancy equipment reports events when the train enters and leaves the section. Duplicate position records with the same transportation task identifier and the same sampling time are deduplicated, and the position time is converted to a unified time base consistent with the updated time period record. The section endpoints are corrected according to the positioning allowable error in the equipment calibration record. In this embodiment, a 0.5-meter allowable error is used, which is only used to handle the positioning deviation between the operating section endpoint and the damage section endpoint. The actual passage time of each transportation task is sequentially matched with the start and end times of the updated time period record. When the actual passage time is within the left-closed-right-open time period, the corresponding stage identifier is obtained. Subsequently... The system verifies whether the route direction, track markings, and actual operating section of the transportation task cover the damage interval in the status record for that time period. If all conditions are met, the transportation task is reassigned to the corresponding stage. A unique verification key is formed by the physical damage chain identifier and the transportation task identifier to prevent the same task from having two valid stage assignments in the current chain version. The reassigned transportation tasks are merged with transportation tasks not affected by order mismatch, arranged in ascending order according to actual passage time. If the times are the same, a stable sort is performed according to the transportation task identifier. Then, the previous task identifier, the next task identifier, the stage identifier, the damage status, and the current chain version are written to generate an updated damage task succession chain. In this embodiment, task T320 that passed in the fourth hour, task T324 that passed in the sixth hour and fifteen minutes, and task T328 that passed in the eighth hour and forty minutes are reassigned to the corresponding stage of the second record. Task T330 that passed in the tenth hour and twenty minutes is still reassigned to the corresponding stage of the third record, thereby completing the spatiotemporal verification and unique reassignment of the canceled transportation tasks under the updated time boundary. Based on the original damage task succession chain and the updated damage task succession chain corresponding to the transportation task identifier, a change of ownership record is generated for transportation tasks whose stage identifiers have changed. Specifically, the original damage task succession chain frozen before the order mismatch processing is retained, and it and the updated damage task succession chain are marked with the original chain version and the updated chain version, respectively. Using the entity damage chain identifier and the transportation task identifier as the corresponding key, the two succession chains are joined item by item to obtain the stage identifier of the same transportation task in the original chain and the stage identifier in the updated chain. When the two stage identifiers are consistent, the updated ownership is retained and no change record is generated. When the two stage identifiers are inconsistent, the transportation task identifier, actual passage time, original stage identifier, updated stage identifier, original damage status, updated damage status, order mismatch record identifier, and the old and new chain versions are written into the ownership difference data item to generate an ownership change record. When a corresponding transportation task is missing in the original chain or the updated chain, check whether the task has a missing location test, a failed segment coverage verification, or a task cancellation status. Generate a data consistency anomaly record and stop the task from entering the change segment to avoid expanding the scope of operation and maintenance adjustments with incomplete running data. The attribution change record represents the version difference record of the actual change in the damage evolution stage of the same transportation task before and after the damage record is accessed. Its determination adopts the precise correspondence of stage identifiers and does not set an experience scoring threshold. In this embodiment, the stage identifiers of tasks T320, T324, and T328 are changed from the stage corresponding to the first record to the stage corresponding to the second record, and attribution change records are generated respectively. Task T330 belongs to the stage corresponding to the third record before and after the update and does not generate an attribution change record, thereby distinguishing the chain structure update from the actual attribution change of the transportation task. The attribution change records are arranged according to the actual passage time. The first and last attribution change records define the scope of continuous tasks, generating a task attribution change segment. Specifically, all attribution change records corresponding to the same sequence mismatch record are arranged in ascending order of actual passage time. When actual passage times are the same, they are stably sorted according to the transportation task identifier. The attribution change record at the top of the list is used as the change start record, and the attribution change record at the bottom of the list is used as the change end record. Starting from the task corresponding to the change start record, the updated damage task continuation chain is accessed continuously according to the subsequent task identifiers to the task corresponding to the change end record. The task identifier, stage identifier, and actual passage time within this range are grouped into the same change segment. When there is only one attribution change record, this task is used as both the change start task and the change end task. When there is no attribution change record, no task attribution change segment is generated, and this chain update is marked as no task attribution change. The entity damage chain identifier and sequence are... The task attribution change segment is generated by associating the mismatch record identifier, the change start task identifier, the change end task identifier, the corresponding start and end times, and the update chain version, and then transmitted to the transportation operation and maintenance update module. The task attribution change segment represents the range of continuous transportation tasks affected by the late confirmation record in the update damage task continuation chain. Its boundary comes from the actual attribution change of the first and last items and does not extend to compatible tasks outside the boundary. In this embodiment, three attribution change records are obtained and arranged according to the actual time as T320, T324, and T328. Therefore, T320 is used as the change start task and T328 is used as the change end task to form the task attribution change segment. Tasks before the fourth hour and T330, which maintains the third stage attribution, are all outside the change segment. After verification, the task order within the change segment is continuous, the stage identifier is traceable, and the old and new chain versions correspond completely, thereby completing the closed-loop processing of update time reconstruction, task re-attribution, version difference identification, and continuous impact range output.
[0030] The present invention is further configured such that the transportation operation and maintenance update module generates historical operation review records and transportation adjustment initiation tasks, including: The actual operating conditions of transportation tasks within the task assignment change section are mapped to the damage status in the updated damage task continuation chain, generating historical operation review records. Specifically, after the task assignment correction module outputs the task assignment change section, the transportation operation and maintenance update transaction is initiated. Input objects include the task assignment change section, the updated damage task continuation chain, the actual operation record of the transportation task, the rail operation and maintenance rule base, and the current chain version. Train operation monitoring equipment reports position and speed data at a frequency of one hertz. The train formation interface sends axle load and vehicle type when forming and changing train formations. The track section occupancy equipment sends data when the train enters or leaves the damage section. Occupancy events; the above data is converted to the railway unified time source, and duplicate reporting records are deduplicated by combining task identifiers and sampling times. Sampling points whose adjacent position changes exceed the distance corresponding to the maximum allowable speed of the line are marked as location anomalies; the transportation tasks within the task assignment change segment are matched item by item with the updated damage task continuation chain using the transportation task identifier to obtain the stage identifier, damage status, and damage interval after the transportation task is reassigned; the actual passage data segment is formed from the last valid position point before the train enters the damage interval to the first valid position point after the train leaves the damage interval, and the highest valid position point is selected from this data segment. The effective speed is used as the actual passing speed, and the corresponding axle load and vehicle type are obtained from the train formation record. The valid range of the speed data adopts the calibration range of the train operation monitoring equipment, and the valid range of the axle load adopts the line design axle load range. Data exceeding the corresponding range is transferred to the equipment anomaly record. The operation and maintenance rule version valid at the actual passing time of the transportation task is called, and the actual passing speed, axle load, and vehicle type are associated with the damage status after reassignment. This is written into the transportation task identifier, actual passing time, damage stage, actual operating conditions, corresponding restrictions, and review status to generate a historical operation review record. The historical operation review record indicates delayed damage confirmation. After the damage record is accessed, the operational evidence record for the transportation task that has passed through the damaged section is re-formed according to the updated damage status. In this embodiment, tasks T320, T324 and T328 are reassigned to the D2 state corresponding to the second record. The speed limit corresponding to this state when the task actually passes through is 80 kilometers per hour. The actual passing speeds of the three tasks are 76 kilometers per hour, 83 kilometers per hour and 74 kilometers per hour, respectively. Therefore, T320 and T328 are recorded as compliant, and T324 is recorded as speed exceeding the limit. This preserves the traceability relationship between the actual operation of historical transportation tasks and the corresponding damage status under the delayed confirmation condition. The process involves obtaining the tail damage status of the physical damage chain, invoking rail maintenance rules based on the damage type and tail damage status, and generating operational restriction records. Specifically, starting from the head of the damage update task continuation chain, the process continuously accesses the subsequent stage identifiers to obtain the tail stage where no subsequent stage exists. It also verifies that the physical damage chain to which this stage belongs has not formed a maintenance closure record and that the chain version is consistent with the current transportation maintenance update transaction. The damage type, tail damage status, and tail damage interval are obtained from the dual-temporal damage records corresponding to the tail stage. The damage type is derived from the classification results and verification results of the flaw detection equipment, and the tail damage status uses the D1 to D4 level codes specified in the rail maintenance rule library. Using the damage type and tail damage status as rule retrieval conditions, rule records within the effective range of the current maintenance processing time are filtered in the rule library. When multiple valid versions exist, the version with the later effective time and already reviewed and released is retained. The speed limit values in the rule records are determined by the specific rules being considered. The range is from zero to the maximum permissible speed of the line, and the range of the axle load limit is from zero to the line's design axle load. The operating mode is one of normal passage, speed-limited passage, or prohibited passage, and the specific values are derived from the rail maintenance rules issued by the line operator. The rule identifier, rule version, damage type, chain tail damage status, chain tail damage range, speed limit, axle load limit, and permissible operating mode are written into the current entity damage chain to generate an operating restriction record. If there is no valid matching record in the rule base, a rule missing anomaly record is generated, and the automatic formation of transportation adjustment boundaries is paused to prevent the output of release results when there is a lack of restriction basis. In this embodiment, the chain tail record corresponds to the rail head transverse crack and D3 status. The current valid rule stipulates speed limit passage, the passage speed is not higher than 45 kilometers per hour, and the axle load is not higher than 25 tons. Therefore, an operating restriction record containing the above-mentioned restriction content and rule version is formed, so that subsequent transportation tasks adopt the same source and verifiable restriction conditions. The process involves filtering transportation tasks from the transportation task records that have a planned transit time later than the current maintenance processing time and whose operating segments cover the chain tail damage area, generating a task sequence to be verified. Specifically, at the start of the same maintenance update transaction, the current maintenance processing time is frozen, using milliseconds generated after the maintenance management platform server receives the unified railway time signal. Transportation tasks that have been compiled or issued but not yet executed are retrieved from the transportation dispatch platform. Transportation plans are pushed in real-time using plan change events, and incremental consistency checks are performed every sixty seconds. Executed, canceled, missing planned transit times, and expired plan versions are removed. The planned transit times of the remaining transportation tasks are compared with the current maintenance processing time, retaining only tasks with planned transit times later than the current maintenance processing time. Subsequently, the planned route, route direction, track identification, and planned operating segment of the transportation tasks are uniformly converted to the same line mileage coordinates as the chain tail damage area, and then... The system verifies whether the route direction and track markings are consistent and whether the planned operating section includes the chain tail damage zone. Transportation tasks that pass both time and section coverage verifications are arranged in ascending order of planned passage time. If planned passage times are the same, they are arranged stably according to scheduling priority and transportation task identifier. The task identifier, planned passage time, planned speed, planned axle load, operating mode, and planned version are associated to generate a task sequence to be verified. The task sequence to be verified represents the ordered set of transportation tasks that are planned to actually cross the chain tail damage zone after the current maintenance processing time and need to undergo operational restriction verification. In this embodiment, four transportation tasks, T401, T405, T409, and T412, are selected, with planned passage times located 40 minutes, 1 hour and 20 minutes, 2 hours and 10 minutes, and 3 hours after the current maintenance processing time, respectively. Another task operating on the opposite track is excluded by section coverage verification, thus avoiding including transportation tasks that do not pass through the chain tail damage zone in the adjustment scope. The planned operating conditions in the task sequence to be verified are matched with the operating restriction records item by item. The first transportation task that does not meet the restriction is taken as the starting task for transportation adjustment. The transportation tasks that meet the restriction before it are generated into a compatible transportation task sequence. Specifically, the transportation tasks are accessed item by item according to the task sequence to be verified. The planned operating mode is matched with the allowed operating mode in the operating restriction record. The planned speed is compared with the restricted speed, and the planned axle load is compared with the restricted axle load. When the operating mode meets the restriction, the planned speed does not exceed the restricted speed, and the planned axle load does not exceed the restricted axle load, the corresponding transportation task is marked as conditionally compatible. When any restriction is not met, an operating condition conflict record is generated, and the search for a later transportation adjustment starting point is stopped. The transportation task corresponding to the first operating condition conflict record is written into the transportation adjustment starting task. The transportation tasks that are located before this task and meet all restrictions are continued in the original planned order to generate a compatible transportation task sequence. When a verification task results in a conflict, the compatible transport task sequence is empty. When all tasks to be verified meet the restrictions, no transport adjustment start task is generated, and all tasks are written into the compatible transport task sequence. In this embodiment, the planned speeds of T401 and T405 are 40 km / h and 45 km / h, respectively, and their planned axle loads do not exceed 25 tons. Therefore, they enter the compatible transport task sequence in sequence. The planned speed of T409 is 80 km / h, which exceeds the 45 km / h limit in the operation restriction record. Therefore, T409 is used as the transport adjustment start task. Although the planned speed of T412 meets the restriction, its planned passage time is later than the first conflicting task, so it does not enter the compatible transport task sequence before T409. Finally, the historical operation verification record, operation restriction record, compatible transport task sequence composed of T401 and T405, and transport adjustment start task marked with T409 are output, providing continuous data input for subsequent maintenance deadlines limited by the planned passage time of T409.
[0031] The present invention is further configured such that, according to the transportation adjustment of the initial task plan, the generation of rail maintenance tasks by setting time limits for maintenance deadlines includes: The planned transit time of the initial transportation adjustment task is used as the maintenance cutoff boundary. Specifically, this embodiment is applied to maintenance scenarios where the first transportation task after the rail damage status update does not meet the current operational restrictions. Input objects include the initial transportation adjustment task, the current transportation plan version, the physical damage chain identifier, the chain tail damage status, and the current maintenance processing time. The planned transit time of the initial transportation adjustment task is obtained from the transportation dispatching platform. The plan data is pushed in real time when the dispatching plan changes, and incremental consistency checks are performed every sixty seconds. The planned transit time is converted to milliseconds under the railway unified time source to verify that the task status is that it has been prepared or issued, the plan version is valid, and the planned transit time is later than the current maintenance processing time. After verification, the planned transit time is written into the maintenance. The cutoff field of the boundary record forms the maintenance cutoff boundary; the maintenance cutoff boundary represents the latest time that rail maintenance, maintenance quality review, and track release should all be completed. The time required for maintenance quality review and track release is included in the damage repair time of subsequent calls; when the planned passage time of the transportation adjustment starting task changes, the original boundary version is terminated and the maintenance period filtering is re-executed; when the planned passage time is earlier than or equal to the current operation and maintenance processing time, a planned timeliness abnormality record is generated and the automatic generation of rail maintenance tasks is stopped; in this embodiment, the transportation adjustment starting task T409 is planned to pass through the chain tail damage section two hours and ten minutes after the current operation and maintenance processing time, so the planned passage time forms the maintenance cutoff boundary, so that the maintenance arrangement and the first transportation task with conflicting operating conditions are clearly correlated in time. When the compatible transport task sequence is empty, the current maintenance processing time is used as the maintenance open boundary; when the compatible transport task sequence is not empty, the later of the current maintenance processing time and the time when the last compatible transport task leaves the damaged section is used as the maintenance open boundary. Specifically, the compatible transport task sequence is obtained from the previous processing, and it is verified that all transport tasks are located before the start of the transport adjustment task and meet the operation restriction records. When the compatible transport task sequence is empty, the current maintenance processing time frozen at the start of this maintenance update transaction is written into the open field. When the compatible transport task sequence is not empty, the last transport task in the sequence is accessed, and its planned departure time from the damaged section is obtained from the section occupancy plan of the transport scheduling platform. When the last task has entered the running state, the actual departure event update time reported by the track section occupancy device is used. The track section occupancy event uses the railway unified time source and is transmitted in real time when the state changes. The departure time of the last compatible transport task is... The time interval is compared with the current maintenance processing time, and the later time is written into the open field to form the maintenance open boundary. The maintenance open boundary represents the earliest time when the line can enter the maintenance time screening. The departure time is the time when the rear of the train leaves the damaged section and the section occupancy is released. When the compatible transport task sequence is empty, the current maintenance processing time is used to avoid waiting for non-existent preceding transport tasks. In this embodiment, the compatible transport task sequence includes T401 and T405. The last task T405 leaves the damaged section one hour and twenty-four minutes after the current maintenance processing time. This time is later than the current maintenance processing time, so it is used as the maintenance open boundary. When the open boundary is earlier than the deadline boundary, it enters the candidate time period screening. When the open boundary reaches or is later than the deadline boundary, a maintenance window insufficient record is generated and T409 is passed to the transport plan adjustment process to prevent the maintenance operation from conflicting with the section occupancy of compatible transport tasks that have not yet left. Based on the maintenance open boundary, maintenance close boundary, and corresponding damage repair duration, continuous idle periods are selected from the line operation plan to generate candidate maintenance periods. Specifically, the rail maintenance operation quota library is retrieved by searching the damage type and damage status in the chain tail damage record to obtain the corresponding maintenance method and damage repair duration. The maintenance operation quota library is reviewed and published by the line operation unit according to rail type, damage type, and maintenance process. The maintenance duration value is greater than zero and includes the time required for line protection settings, maintenance operations, flaw detection verification, tool removal, and line release. In this embodiment, an emergency reinforcement process is adopted for the D3 state of transverse cracks in the rail head, with a quota maintenance duration of thirty-two minutes. The line operation plan and section occupancy records between the maintenance open boundary and the maintenance close boundary are obtained from the transportation dispatch platform. The transportation task occupancy, shunting occupancy, and scheduled construction occupancy are uniformly converted into start and end time intervals. The occupancy intervals are arranged according to the start time, and overlapping or contiguous intervals are excluded. The occupied sections are merged into continuous occupied sections, and then the continuous occupied sections are deducted from the range from the open boundary to the cutoff boundary to form continuous idle sections. The duration of each continuous idle section is compared with the damage repair time, and only continuous idle sections that can fully accommodate the repair work are retained. The start time of the idle section is used as the candidate start time, and the candidate end time is formed by extending it backward according to the damage repair time. Candidate maintenance time periods are generated. If there is no continuous idle section that meets the repair time, a line time period insufficiency record is generated, and the fragmented idle time is not spliced into candidate time periods. In this embodiment, the maintenance open boundary is located one hour and twenty-four minutes after the current operation and maintenance processing time, and the maintenance cutoff boundary is located two hours and ten minutes after it. The line operation plan shows that there are no other sections occupied within this range, so a continuous idle section of 46 minutes is obtained, and a candidate maintenance time period of 32 minutes is formed from the open boundary, so that the repair work can be completed under continuous line conditions. The candidate maintenance period is matched item by item with maintenance personnel, maintenance equipment, track closure records, and equipment relocation records to generate resource fulfillment records. Specifically, the system obtains the available maintenance personnel and their qualifications from the personnel scheduling interface, the equipment type, availability, and current location from the equipment management interface, track closure records from the transportation scheduling interface, and equipment relocation records from the equipment scheduling interface. Personnel scheduling data and track closure data are pushed in real time when the status changes, and mobile maintenance equipment reports its location every 30 seconds. According to the resource list of emergency reinforcement processes in the maintenance operation quota library, the system verifies whether the number of maintenance personnel meets the quota requirements, whether the qualifications cover rail emergency reinforcement and flaw detection verification, and whether the available time of personnel covers the candidate maintenance period. The system also verifies whether the maintenance equipment includes emergency clamp installation tools, fastening equipment, and rail flaw detection equipment, and whether the available time of the equipment covers the candidate maintenance period. Finally, the system verifies the track closure records. The system checks whether the road direction, track markings, and closure time cover the candidate maintenance period; whether the target location in the equipment transfer record falls within the work area of the damaged section, whether the estimated arrival time is earlier than the candidate start time, and whether the transfer route is in an executable state; when all four types of resources pass the verification, the candidate maintenance period, personnel team identifier, equipment identifier, line closure identifier, and equipment transfer identifier are associated to generate a resource fulfillment record; when any resource fails the verification, a corresponding resource insufficiency record is generated, and the next candidate maintenance period with a later start time is verified; in this embodiment, the maintenance team enters the dispatchable state one hour and fifteen minutes after the current maintenance processing time, the maintenance equipment arrives at the damaged section one hour and twenty-two minutes before, the line closure record covers one hour and twenty-four minutes to two hours, the equipment transfer record is in a confirmed state, and all four types of resources cover the candidate maintenance period of one hour and twenty-four minutes to one hour and fifty-six minutes, thus generating a corresponding resource fulfillment record; Resource fulfillment records are arranged according to the start time of the candidate maintenance period. The first resource fulfillment record is associated with the physical damage chain and the task assignment change section to generate a rail maintenance task and update the corresponding transportation and maintenance records. Specifically, all resource fulfillment records are arranged in ascending order of the start time of the candidate maintenance period. If the start times are the same, they are arranged in order of line closure confirmation time and resource record identifier. The first resource fulfillment record is selected, and its physical damage chain version, operation restriction record version, and transportation plan version are verified to be still valid. After verification, the resource fulfillment record is associated with the physical damage chain identifier, the chain tail damage record identifier, the task assignment change section identifier, and the transportation adjustment start task identifier. The candidate start time is written into the planned start time, the candidate end time is written into the planned completion time, and the maintenance method, maintenance personnel, maintenance equipment, closure section, and maintenance deadline boundary are written into the maintenance work order to generate a rail maintenance task. The system updates the status of the physical damage chain to "pending maintenance," the corresponding line closure period to "occupied," and the maintenance personnel and equipment to "reserved." It also marks the transportation adjustment initiation task T409 as awaiting maintenance result verification. After maintenance, a re-inspection record is obtained through the flaw detection equipment interface, and the acceptance result is obtained through the maintenance acceptance interface. If acceptance is successful, a maintenance closure record is generated, and the waiting status of T409 is lifted. If acceptance fails, the physical damage chain remains valid, and the operation restriction record is re-called. In this embodiment, the rail maintenance task plan starts one hour and twenty-four minutes after the current maintenance processing time and ends one hour and fifty-six minutes later, fourteen minutes earlier than the maintenance deadline boundary corresponding to T409. Verification confirms that the personnel, equipment, line closure, and equipment transfer records are consistent with the maintenance work order, thus completing a closed-loop process from transportation conflict boundaries, continuous idle periods, resource feasibility, to maintenance tasks and transportation maintenance status updates.
[0032] It should be noted that the specific methods by which each module and unit performs operations in the intelligent rail damage monitoring, transportation, and maintenance management system provided in the above embodiments have been described in detail in the system embodiments and will not be repeated here. In practical applications, the intelligent rail damage monitoring, transportation, and maintenance management system provided in the above embodiments can allocate the above functions to different functional modules as needed, that is, divide the internal structure of the system into different functional modules to complete all or part of the functions described above, and this is not a limitation here.
[0033] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.
Claims
1. A smart monitoring and transportation maintenance management system for rail damage, characterized in that, include: The dual-temporal record generation module obtains damage monitoring records and transportation task records from rail damage monitoring equipment, and associates monitoring time, confirmation time, rail entity identification, damage range, damage type, damage status and maintenance closure record to generate dual-temporal damage records. The entity damage chain generation module groups dual-temporal damage records according to rail entity identification, and generates entity damage chains by continuing dual-temporal damage records with intersecting damage intervals, successive damage types, and no maintenance closure records between adjacent records according to monitoring time. The delayed task module will arrange the transportation tasks that actually passed through the damaged area between the monitoring time and the confirmation time according to the actual passing time, and generate the delayed task sequence. The damage task continuation module divides the damage evolution period into adjacent monitoring times in the physical damage chain. It uniquely assigns the transportation task whose actual passage time falls into the damage evolution period and whose operating section covers the damage area to the corresponding damage evolution period, and generates the damage task continuation chain according to the actual passage time. When the confirmation time sequence and monitoring time sequence of the same entity damage chain are inconsistent, the task attribution correction module accesses the corresponding record according to the monitoring time, cancels the original stage attribution of the transportation task within the delayed confirmation task sequence, re-attributes it according to the updated damage evolution period, matches the original damage task succession chain with the updated damage task succession chain, and generates a task attribution change segment. The transportation operation and maintenance update module maps the actual operating conditions of transportation tasks within the task assignment change segment to the damage status after reassignment, and generates historical operation review records; it maps the operating constraints corresponding to the chain tail damage status to the planned operating conditions of the transportation tasks to be executed item by item, takes the first conflicting condition task as the starting task for transportation adjustment, and generates rail maintenance tasks based on the time-limited maintenance deadline boundary of the planned starting task for transportation adjustment.
2. The intelligent monitoring, transportation, and maintenance management system for rail damage according to claim 1, characterized in that, The dual-temporal record generation module includes: Damage monitoring records are obtained through the rail damage monitoring equipment interface, and the rail physical identification, damage range, damage type, damage status and monitoring time are retained; Obtain the confirmation time of the completion of the damage monitoring record review, and associate the confirmation time with the corresponding damage monitoring record; The maintenance and acceptance records are mapped to the damage monitoring records according to the rail physical identification and maintenance section, and maintenance closure records are generated. The monitoring time, confirmation time, and maintenance closure record are linked to the damage monitoring record to generate a dual-temporal damage record.
3. The intelligent monitoring, transportation, and maintenance management system for rail damage according to claim 1, characterized in that, The solid damage chain generation module includes: The rail entity record group is generated by grouping the dual-temporal damage records according to the rail entity identification, track direction and track marking. Arrange the rail entity record groups according to the monitoring time, and generate adjacent candidate records for dual temporal damage records with adjacent time. Perform damage interval intersection verification and damage type continuity verification on adjacent candidate records to generate damage continuity records; Damage transfer records that do not cross the maintenance closure record are sequentially connected according to the monitoring time to generate a physical damage chain.
4. The intelligent monitoring and transportation maintenance management system for rail damage according to claim 1, characterized in that, The delayed task confirmation module includes: The monitoring time in the dual-temporal damage record is used as the starting point and the confirmation time is used as the ending point to generate a confirmation lag period. Select transportation tasks from the transportation task records whose actual transit time falls within the confirmation lag period and whose task status is "executed", and generate time candidate tasks. Perform coverage verification between the actual running segment of the time candidate task and the damage interval in the dual-temporal damage record to generate a damage crossing task; Damage traversal tasks are sequentially arranged according to the actual passage time, and dual-temporal damage record identifiers are associated with the corresponding tasks to generate a confirmed lag task sequence.
5. The intelligent monitoring and transportation maintenance management system for rail damage according to claim 1, characterized in that, Damage evolution periods are divided into adjacent monitoring times within the solid damage chain, including: Arrange the dual-temporal damage records in the physical damage chain according to the monitoring time to generate the record order within the chain; Using the monitoring time of the previous pair of temporal damage records as the starting point and the monitoring time of the next pair of temporal damage records as the ending point, a damage evolution period of left-closed and right-open is generated. The damage status, damage range, and record identifier of the previous bitemporal damage record are associated with the corresponding damage evolution period to generate a period status record; Using the monitoring time of the chain tail dual-temporal damage record as the starting point and the current operation and maintenance processing time as the ending point, a chain tail evolution period is generated, and the chain tail damage status is associated with the chain tail evolution period.
6. The intelligent monitoring, transportation, and maintenance management system for rail damage according to claim 5, characterized in that, Transportation tasks whose actual transit time falls within the damage evolution period and whose operating segment covers the damage area are uniquely assigned to the corresponding damage evolution period. Damage task succession chains are generated based on the actual transit time, including: The actual transit time of the transportation task is mapped to the damage evolution period to generate time-segment candidate tasks; Perform coverage verification between the actual running segment of the candidate task and the damaged interval in the time period status record, and pass the task generation stage. Unique attribution verification is performed based on the entity damage chain identifier and the transportation task identifier, and transportation tasks within the same entity damage chain retain one stage of attribution. Based on the actual completion time, the damage task is sequentially completed, and the stage identifier, damage status, and task identifier are associated to generate a damage task continuation chain.
7. The intelligent monitoring and transportation maintenance management system for rail damage according to claim 1, characterized in that, According to the monitoring time, the corresponding records are accessed, and the original stage attribution of transportation tasks within the delayed task sequence is revoked, including: The dual-temporal damage records in the same entity damage chain are arranged according to the monitoring time and the confirmation time, respectively, to generate monitoring order records and confirmation order records; Based on the record identifier, corresponding monitoring sequence record and confirmation sequence record, generate sequence mismatch record for dual temporal damage records where the preceding or subsequent records are inconsistent; Based on the monitoring time of the sequence mismatch record, obtain the adjacent monitoring record corresponding to the access location, and terminate the original connection relationship between the adjacent monitoring records; Connect the mismatched records to the corresponding adjacent monitoring records to generate an updated intra-chain order; Match the confirmed delayed task sequence corresponding to the sequence mismatch record with the original damage task continuation chain, and cancel the original stage assignment of the corresponding transportation task.
8. The intelligent monitoring and transportation maintenance management system for rail damage according to claim 7, characterized in that, Based on the updated damage evolution period, the original damage task succession chain and the updated damage task succession chain are reassigned, and a task assignment change segment is generated, including: Based on the order within the update chain, the damage evolution period before and after the order mismatch record is redefined, and an update period record is generated. The transportation tasks assigned during the cancellation phase are reassigned to the update period record according to the actual passage time and actual operating segment, generating an update damage task continuation chain. Based on the original damage task succession chain and the updated damage task succession chain corresponding to the transportation task identifier, a change of ownership record is generated for transportation tasks whose stage identifiers have changed. Arrange the ownership change records according to the actual passage time, and use the first and last ownership change records to define the scope of continuous tasks, thereby generating a task ownership change segment.
9. The intelligent monitoring and transportation maintenance management system for rail damage according to claim 8, characterized in that, The transportation operation and maintenance update module generates historical operation review records and transportation adjustment initiation tasks, including: The actual operating conditions of the transportation tasks within the task ownership change segment are matched with the damage status in the updated damage task succession chain to generate historical operation review records. Obtain the damage status of the tail end of the physical damage chain, and call the rail maintenance rules based on the damage type and tail end damage status to generate an operation restriction record; Filter transportation tasks from the transportation task records whose planned passage time is later than the current operation and maintenance processing time and whose operating segment covers the chain tail damage area, and generate a task sequence to be verified. The planned operating conditions and operating restriction records in the task sequence to be verified are matched one by one. The first transportation task that does not meet the restriction is taken as the starting task for transportation adjustment, and the transportation tasks that meet the restriction before it are used to generate a compatible transportation task sequence.
10. The intelligent monitoring and transportation maintenance management system for rail damage according to claim 9, characterized in that, Based on the transportation adjustment start task plan and the time-limited maintenance deadline boundary, the rail maintenance task is generated, including: The schedule for adjusting the initial task of transportation will be used as the maintenance deadline. When the compatible transport task sequence is empty, the current maintenance processing time is used as the maintenance open boundary; when the compatible transport task sequence is not empty, the later of the current maintenance processing time and the time when the last compatible transport task leaves the damaged section is used as the maintenance open boundary. Based on the maintenance open boundary, maintenance close boundary and corresponding damage repair duration, continuous idle periods are selected from the line operation plan to generate candidate maintenance periods; Match each candidate maintenance period with maintenance personnel, maintenance equipment, line closure records, and equipment relocation records to generate a resource fulfillment record. Resource fulfillment records are arranged according to the start time of the candidate maintenance period. The first resource fulfillment record is associated with the entity damage chain and the task ownership change segment to generate a rail maintenance task and update the corresponding transportation and maintenance records.
