A processing method and device for reporting rail transit AFC failures

Abstract

The application provides a kind of rail transit AFC fault report processing method and device, method includes: in maintenance time, according to the periodic acquisition AFC fault report data of preset time interval;From the AFC fault report data in several preset time intervals, screen out the fault data to be handled;According to the same fault code of the same device code, the fault data to be handled is classified and grouped processing;When the last fault event in the same group in the fault data to be handled is in the recovered state, then report the removal information of the fault event to be handled;When the last fault event in the same group in the fault data to be handled is in the occurrence state, then select greater than or equal to the fault event to be handled in the preset time interval, after hierarchical identification, report the fault data to be handled after hierarchical identification;According to the report information of the fault event to be handled, generate or cancel fault maintenance work order.The method provided in the scheme can effectively identify the real device fault, guide rail transit AFC device maintenance work.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of rail transit AFC data processing, and in particular to a rail transit AFC fault reporting processing method and device. BACKGROUND

[0002] At present, the fault reporting data processing of rail transit AFC equipment is still in a relatively extensive state. In the face of the daily reporting of hundreds of thousands of AFC equipment faults (including false reports and removals) per line, a filtering strategy based on fault type coding is generally used, that is, a list of some common and easily occurring device fault codes is specified, the information of the fault codes in the list is transmitted to generate a maintenance work order, and the fault reports not in the list are completely discarded, completely relying on the manual repair of the site management personnel. There are about 250 rail transit landmark fault types and manufacturer-supplemented fault types, and the original solution artificially discards most of the fault types to reduce fault false reports, and only 32 fault types are retained for management, thereby causing a large number of subjective fault omissions.

[0003] This fault reporting data processing method mainly leads to two adverse consequences:

[0004] 1. Only relying on the fault filtering rules of the list inevitably misses some device fault types, and manual repair by the site management personnel must be used as a substitute supplement, which not only delays the timely response of fault handling, but also increases the work burden of the site management personnel, and over time, it will cause the satisfaction of the rail transit owner to decrease;

[0005] 2. AFC equipment faults often have characteristics such as unstable fault state, non-reproducible, and self-recovery, and often when the maintenance personnel arrive at the scene, they find that the fault has not occurred or has been restored, thereby causing waste of maintenance human resources;

[0006] 3. The fault levels are not fully and reasonably subdivided, resulting in different response requirements mixed together, and the maintenance personnel need to make judgments on the processing priority of the work order generated according to the fault report based on experience, which is easy to cause inconsistency and misjudgment. SUMMARY

[0007] In view of the above problems, the present application mainly analyzes the internal data rules of rail transit AFC equipment fault reporting, combines the manual repair data of the site management personnel, and the actual maintenance results of the on-site maintenance personnel, uses the time dimension correlation analysis method of big data to mine the potential relationship between device fault reporting and real faults, and finally forms a data processing method for intelligent screening of rail transit AFC equipment fault reporting information.

[0008] The application provides a rail transit AFC fault reporting processing method, and has the technical scheme as follows:

[0009] In some embodiments, comprising:

[0010] During the maintenance time, the AFC fault reporting data is periodically acquired according to a preset time interval and written into a local data table;

[0011] The AFC fault reporting data in several preset time intervals is screened to obtain to-be-processed fault data;

[0012] The to-be-processed fault data is classified and grouped according to the same fault code of the same device code;

[0013] When the last fault event in the same group is in a recovered state, the to-be-processed fault event is reported to clear the information;

[0014] When the last fault event in the same group is in an occurrence state, to-be-processed fault events greater than or equal to the preset time interval are selected, classified and identified, and then the to-be-processed fault data after the classification and identification is reported;

[0015] A fault clearing work order or a fault occurrence work order is generated according to the reporting information of the to-be-processed fault event.

[0016] In some embodiments, the to-be-processed fault data is screened from the AFC fault reporting data in several preset time intervals, and specifically comprises:

[0017] After the AFC fault reporting data in several preset time intervals is screened to exclude unnecessary fault data and / or purpose fault data, the to-be-processed fault data is generated; the purpose fault data includes fault data of a multi-purpose device used as a single-purpose device.

[0018] In some embodiments, after the fault clearing work order or the fault occurrence work order is generated according to the reporting information of the to-be-processed fault event, comprising:

[0019] When the work order maintenance department receives the fault occurrence work order, it is detected whether the to-be-processed fault event corresponding to the fault occurrence work order exists in the current processing work order of the work order maintenance department;

[0020] If the to-be-processed fault event corresponding to the fault occurrence work order exists in the current processing work order, the fault occurrence work order is ignored.

[0021] In some embodiments, after the fault clearing work order or the fault occurrence work order is generated according to the reporting information of the to-be-processed fault event, comprising:

[0022] When the fault clearing work order is received by the work order maintenance department, it is detected whether the pending fault event corresponding to the fault clearing work order exists in the current processing work order of the work order maintenance department;

[0023] If the pending fault event corresponding to the fault clearing work order does not exist in the current processing work order, the fault clearing work order is ignored;

[0024] If the pending fault event corresponding to the fault clearing work order exists in the current processing work order, it is analyzed whether there is another pending fault event in addition to the pending fault event in the fault clearing work order in the current processing work order;

[0025] If there is another pending fault event in addition to the pending fault event in the fault clearing work order in the current processing work order, the maintenance requirement of the fault clearing work order is cancelled;

[0026] If there is no another pending fault event in addition to the pending fault event in the fault clearing work order in the current processing work order, the current processing work order is cancelled or abandonment of maintenance is notified according to the order receiving state of the current processing work order.

[0027] In some embodiments, after the revocation, prompting or discarding processing according to the reporting information of the fault work order cleaning process and the fault work order generation process, the present application further comprises:

[0028] The number of false alarms of device faults corresponding to each fault code of each device code in a preset time period is counted and prompted;

[0029] When the number of false alarms of device faults of the same fault code of the same device code exceeds a preset number, the fault event of the fault code of the device code is downgraded.

[0030] In some embodiments, based on the same technical concept, the present application further provides a processing device for AFC fault reporting of rail transit, comprising:

[0031] A fault data screening module is configured to screen out pending fault data from the AFC fault reporting data in a plurality of preset time intervals;

[0032] A grouping and classification module is configured to classify and group the pending fault data according to the same fault code of the same device code;

[0033] A data reporting module is configured to report the clearing information of the pending fault event when the last fault event in the same group is in a recovered state.

[0034] The data reporting module is further configured to: when the last fault event in the to-be-processed fault data in the same group is in an occurrence state, select to-be-processed fault events greater than or equal to the preset time interval, perform hierarchical identification on the to-be-processed fault events, and then report the to-be-processed fault data after hierarchical identification.

[0035] The work order generation module is configured to generate a fault clearing work order or a fault occurrence work order according to the reporting information of the to-be-processed fault event.

[0036] In some embodiments, the fault data screening module is further configured to:

[0037] After the unnecessary fault data and / or the use fault data are screened out from the AFC fault reporting data in the plurality of preset time intervals, the to-be-processed fault data is generated; the use fault data includes fault data of a multi-use device used as a single-use device.

[0038] In some embodiments, the fault data screening module is further configured to:

[0039] The work order processing module is configured to perform canceling, prompting or discarding processing on the fault clearing work order or the fault occurrence work order.

[0040] In some embodiments, the work order processing module specifically includes:

[0041] If the fault event in the fault clearing work order or the fault occurrence work order is in a processing state, the canceling sub-module is configured to:

[0042] The canceling sub-module is configured to perform canceling processing on the fault work order in an unaccepted state.

[0043] The prompting sub-module is configured to issue a prompt to end maintenance in a maintenance state.

[0044] The discarding sub-module is configured to give up maintenance in a maintenance state.

[0045] In some embodiments, the fault data screening module is further configured to:

[0046] The fault statistics module is configured to count and prompt the number of device fault false alarms of each device code corresponding to each fault code in a preset time period.

[0047] The fault degradation module is configured to perform degradation processing on the fault event of the fault code of the same device code when the number of device fault false alarms of the same fault code of the same device code exceeds a preset number.

[0048] The processing method and device for AFC fault reporting of rail transit provided by the application have at least the following beneficial effects:

[0049] 1. The application provides a kind of rail transit AFC fault report processing method and device, the scheme is sufficient to communicate to maintenance service personnel, to all fault types, according to its emergency and importance, different response levels are divided, and the generated maintenance work order is directly labeled with response level label, facilitate maintenance personnel work and avoid the work delay caused by error classification.

[0050] 2. The application provides a kind of rail transit AFC fault report processing method and device, the scheme collects and fuses AFC fault report data, station manual fault data, maintenance work order feedback data history inventory, introduces big data technology to carry out correlation analysis and data distribution characteristic analysis in time dimension, from the nearly mass daily fault report information, the real device fault is identified, and then submitted to subsequent work order stage, guide field maintenance and operation work. BRIEF DESCRIPTION OF DRAWINGS

[0051] The above-mentioned characteristics, technical features, advantages and implementation ways of a kind of rail transit AFC fault report processing method and device will be further described in the following explicit and easy-to-understand way, combined with preferred embodiment, explanation.

[0052] Figure 1 It is the flowchart of one embodiment of the application a kind of rail transit AFC fault report processing method;

[0053] Figure 2 It is the detailed flowchart of another embodiment of the application a kind of rail transit AFC fault report processing method;

[0054] Figure 3 It is the module block diagram of one embodiment of the application a kind of rail transit AFC fault report processing device;

[0055] Figure 4 It is the module block diagram of another embodiment of the application a kind of rail transit AFC fault report processing device;

[0056] Figure 5 It is the module block diagram of another embodiment of the application a kind of rail transit AFC fault report processing device. DETAILED DESCRIPTION

[0057] In the following description, for purposes of explanation and not limitation, specific details are set forth such as particular architectures, techniques, etc. in order to provide a thorough understanding of the embodiments of the present application. However, it will be apparent to those skilled in the art that the present application can be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known methods, devices, circuits, and

[0058] It should be understood that the term "comprises" when used in this specification and the appended claims, specifies the presence of stated features, integers, steps, operations, elements, and / or components, but does not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0059] It should also be further understood that the term "and / or" when used in the specification and in the claims, means any one and / or all possible combinations of one or more of the associated listed items.

[0060] In addition, in the description of the present application, the terms "first", "second", etc. are only used to distinguish descriptions, and cannot be understood as indicating or implying relative importance.

[0061] In order to more clearly illustrate the technical solutions of the embodiments of the present application or the prior art, the specific embodiments of the present application will be described below with reference to the drawings. Obviously, the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can be obtained from these drawings without creative labor, and other embodiments can also be obtained.

[0062] In one embodiment, with reference to Figure 1 A processing method of track traffic AFC fault reporting comprises:

[0063] S100, within the maintenance time, periodically acquiring AFC fault reporting data according to a preset time interval, and writing into a local data table;

[0064] Specifically, in the field of rail transit, in order to adapt to the pace of most people's life, the maintenance time is mostly selected as 7:00 to 23:00 every day, and the fault reporting outside this time domain can be suspended for processing, and the fault reporting information is collected and processed after the maintenance work starts; the trigger frequency of data processing is the preset time interval, which is set to ensure the timeliness of fault work order generation as much as possible, such as 10 minutes, 20 minutes, etc. If it is necessary to improve the accuracy of fault work order (reduce the false alarm rate), the trigger frequency of the process can be reduced according to actual needs. When reading data, the timestamp maximum value of the landed original fault reporting information needs to be read to avoid repeated reading of data. Then, the fault reporting information with the storage time greater than or equal to the maximum value is read from the road network center database as the newly added fault reporting period data. Then the above newly added fault reporting data is written into the local persistent storage database table (Oracle) and the temporary storage memory data table (Redis) at the same time. It is true that other databases that can realize this function can also be used, which is not limited here.

[0065] S200, screening the fault data to be processed from the AFC fault reporting data in several preset time intervals;

[0066] Specifically, the fault data of the rail transit AFC is periodically acquired according to the preset time interval, so as to facilitate subsequent processing of data reporting.

[0067] Since the key point of the data processing method of the present application is the feature analysis of the fault reporting data time distribution, in order to ensure that there is enough data observation window after the fault event at the end of the main data window, the present embodiment selects two data windows of fault events as the observation objects in each process of selecting the feature of the fault reporting data distribution. (Taking the preset time interval of 5 minutes as an example) Among them, the data window of the current time 5 to 10 minutes ago is the main observation object, and the final output of the identified fault event is from this data window; and the data window of the current time 0 to 5 minutes ago is the reference object, which is only used to assist the verification of the main observation object data. The real-time data processing technology in the present embodiment can be realized by using the Flink framework. The advantage of this processing is that the massive AFC equipment fault information is analyzed by using big data technology, and the analysis is used as the theoretical basis for intelligent screening of the reporting information. At the same time, the advanced Flink window technology is used to timely and efficiently perform micro-batch analysis and transmission of data.

[0068] S300, classifying and grouping the fault data to be processed according to the same fault code of the same device code;

[0069] Specifically, the fault event is related to a specific device and a fault type, so the feature analysis of the fault report data time distribution must be limited to each device and fault type, so in this step, the fault report data loaded into Flink in the previous step needs to be classified and grouped by device code and fault code.

[0070] S400, when the last fault event in the same group is in the recovered state, the clearing information of the reported fault event is reported;

[0071] When the last fault event in the same group is in the occurrence state, select the fault event greater than or equal to the preset time interval for hierarchical identification, and then report the hierarchical identification of the fault data to be processed;

[0072] Specifically, according to the time distribution feature analysis of the existing fault report data, the same device and the same fault report exist indefinite periodicity of repetition, and the repetition frequency is from several seconds to several minutes. At the same time, there are also instances of fault clearing devices recovering to normal operation without reporting fault clearing messages. In order to further filter out stable fault information and remove more false reports and recovered fault information, this embodiment sets a filtering standard for repeated reporting outside a certain time limit. This time limit standard can be set independently of the data window length, but must be greater than or equal to the time scale of the data window. Setting a value that is too large will miss some or even all real fault information.

[0073] S500, generating a fault clearing work order or a fault occurrence work order according to the fault event report information.

[0074] Specifically, the state of the last event in the group is used to distinguish the operation process of the work order. That is, if the device state is that the fault has been recovered, a fault clearing work order is directly generated, and if the device state is that the fault has occurred, the process of the fault occurrence work order is entered.

[0075] In one embodiment, on the basis of the above-mentioned embodiment, the AFC fault report data in several preset time intervals is filtered to obtain the fault data to be processed, specifically including:

[0076] After filtering out the fault data to be processed and / or the use fault data from the AFC fault report data in several preset time intervals, the fault data to be processed is generated; the use fault data includes the fault data of a multi-use device as a single-use device.

[0077] Specifically, in the rail transit landmark fault type and the manufacturer's supplementary fault type, there are generally 112 types that do not need to be processed, so in order to avoid data interference, the reporting information related to the 112 types of faults that do not need to be processed needs to be screened out in the temporary memory data table first. In addition, due to management needs, part of the two-way gate equipment will be changed to one-way (only in or only out) gate use, and part of the automatic ticket vending machines that originally accept both paper money and coins will temporarily suspend the paper money transaction function. Therefore, the fault reporting related to the unenabled function modules in these multipurpose devices should be screened out in the temporary memory data table.

[0078] In one embodiment, on the basis of the above-mentioned embodiment, after generating the fault clearing work order or the fault occurrence work order according to the reporting information of the to-be-processed fault event, the following steps are further included:

[0079] When the work order maintenance department receives the fault occurrence work order, it is detected whether the to-be-processed fault event corresponding to the fault occurrence work order already exists in the currently processed work order in the work order maintenance department;

[0080] If the to-be-processed fault event corresponding to the fault occurrence work order already exists in the currently processed work order, the fault occurrence work order is ignored.

[0081] When the work order maintenance department receives the fault clearing work order, it is detected whether the to-be-processed fault event corresponding to the fault clearing work order already exists in the currently processed work order in the work order maintenance department;

[0082] If the to-be-processed fault event corresponding to the fault clearing work order does not exist in the currently processed work order, the fault clearing work order is ignored;

[0083] If the to-be-processed fault event corresponding to the fault clearing work order exists in the currently processed work order, it is analyzed whether there are other to-be-processed fault events in the currently processed work order in addition to the to-be-processed fault event in the fault clearing work order;

[0084] If there are other to-be-processed fault events in the currently processed work order in addition to the to-be-processed fault event in the fault clearing work order, the maintenance requirement of the fault clearing work order is cancelled;

[0085] If there are no other to-be-processed fault events in the currently processed work order in addition to the to-be-processed fault event in the fault clearing work order, the currently processed work order is cancelled or abandonment of maintenance is notified according to the order receiving state of the currently processed work order.

[0086] Specifically, even if a fault work order is generated, there is still a case of automatic system repair afterwards. Therefore, a processing scheme is supplemented. When the fault operation type received by the work order maintenance program is “recovered”, it is checked whether there is a work order for the device and the fault in the current active work order. If not, the event is ignored. If yes, and the fault is not the only fault of the work order, the maintenance requirement of the fault is removed from the work order. If yes, and the fault is the only fault of the work order, the current work stage of the work order is observed. If it is in the unaccepted state, the work order is directly removed. If it is in the accepted but not started maintenance state, the maintenance personnel is notified to return. If it is in the started maintenance state, the event is ignored (the fault clearing information may be triggered by the maintenance operation).

[0087] When the fault operation type received by the work order maintenance program is “occurred”, it is checked whether there is a work order for the device and the fault in the current active work order. If yes, the event is ignored. If not, the next process is continued.

[0088] In one embodiment, on the basis of the above-mentioned embodiment, after the revocation, prompting or discarding processing according to the reporting information of the fault work order cleaning process and the fault work order generation process, it further includes:

[0089] The number of device fault false alarms corresponding to each device code and each fault code of each device code in a preset time period is counted and prompted.

[0090] When the number of device fault false alarms of the same fault code of the same device code exceeds a preset number, the fault event of the fault code of the device code is downgraded.

[0091] Specifically, in the data analysis of the past fault reporting information, there are a few devices that have frequent false alarms. Such faults often cannot be reproduced when the maintenance personnel arrives at the scene, or the site management personnel reports that the fault has never occurred. Therefore, under the technical premise that such false alarms cannot be eliminated from the device source, the present application adopts a method based on data analysis to downgrade such fault reporting. First, false alarm data statistics are triggered twice a day (if real-time false alarm data is required, the triggering frequency can be increased, which is not limited here). The false alarm statistics object is the feedback information of the maintenance personnel to the authenticity of the on-site fault in the maintenance work order system. The statistical time domain can be the last two weeks. If the device false alarm duration exceeds this time range, the device manufacturer can be contacted to troubleshoot the false alarm cause or replace the related device components.

[0092] The finally generated maintenance work order can be distributed to the maintenance personnel through the mobile phone app according to the existing business logic. The overall detailed process can be referred to Figure 2The application is currently applied to the AFC equipment fault screening of some rail transit lines in a city, but can be applied to more extensive equipment fault screening fields by making some changes in combination with data of other cities or other equipment types.

[0093] In one embodiment, based on the same technical concept, the application further provides a processing device for rail transit AFC fault reporting, referring to Figure 3 , comprising:

[0094] The fault data acquisition module 10 acquires AFC fault reporting data periodically according to a preset time interval within a maintenance time and writes the data into a local data table;

[0095] The fault data screening module 20 is used for screening the to-be-processed fault data from the AFC fault reporting data in a plurality of preset time intervals;

[0096] The grouping and classifying module 30 is used for classifying and grouping the to-be-processed fault data according to the same fault code of the same equipment code;

[0097] The data reporting module 40 is used for reporting the clearing information of the to-be-processed fault event when the last fault event in the to-be-processed fault data in the same group is in a recovered state;

[0098] The data reporting module is further used for selecting the to-be-processed fault event greater than or equal to the preset time interval to perform hierarchical identification, and then reporting the to-be-processed fault data after the hierarchical identification when the last fault event in the to-be-processed fault data in the same group is in an occurrence state;

[0099] The work order generation module 50 is used for generating a fault clearing work order or a fault occurrence work order according to the reporting information of the to-be-processed fault event.

[0100] Specifically, the fault data acquisition module is mainly used for periodically acquiring rail transit AFC fault reporting data, and then screening the data through the fault data screening module to screen out unnecessary data. Different equipment and different fault types are classified and grouped through the grouping and classifying module, and then the corresponding data is reported through the data reporting module. Finally, the fault clearing work order and the fault occurrence work order are generated for the reference of maintenance personnel.

[0101] In another embodiment, on the basis of the above embodiment, the fault data screening module is further used for:

[0102] After screening out unnecessary fault data and / or use fault data from the AFC fault reporting data in a plurality of preset time intervals, the to-be-processed fault data is generated. The use fault data includes fault data of a multi-use equipment used as a single-use equipment.

[0103] Specifically, due to management needs, some two-way turnstiles will be converted into one-way (entry or exit only) turnstiles, and some automatic ticket vending machines that originally accepted both banknotes and coins will suspend banknote transactions. Therefore, fault reports related to unactivated functional modules in these multi-purpose devices should be filtered out in the temporary memory data table.

[0104] In another embodiment, based on the above embodiments, a processing device for reporting AFC (Automatic Fare Collection) faults in rail transit is provided, with reference to... Figure 4 It also includes:

[0105] The work order processing module 60 is used to cancel, prompt, or discard fault clearing work orders or fault occurrence work orders.

[0106] Specifically, this module is responsible for filtering the generated fault clearing work orders and fault occurrence work orders. When the last event in a group is not "recovered", if there are faults that have been eliminated in the middle, all cleared faults should be filtered out first, that is, the last clearing event and all events before it, and then the data of the remaining simple fault occurrence events should be examined.

[0107] In one embodiment, based on the above embodiments, the work order processing module specifically includes:

[0108] If the fault event in the fault clearing work order or fault occurrence work order is in the "processing" status, then

[0109] The cancellation submodule is used to cancel faulty work orders that are in an unaccepted state.

[0110] The prompt submodule is used to issue a prompt to end the repair if the order has been accepted but has not yet entered the repair state;

[0111] The discard submodule is used to discard fault work orders when the system is in maintenance mode.

[0112] Specifically, when the fault operation type received by the work order maintenance program is "recovered", it will check whether a work order for the same device and fault already exists in the currently active work orders. If not, the event will be ignored. If it exists, and the fault is not the only fault in the work order, the cancellation submodule will cancel the maintenance request for the fault from the work order. If it exists, and the fault is the only fault in the work order, it will observe the current work stage of the work order. If it is in the unaccepted state, the work order will be canceled directly. If it is in the accepted but not yet started state, the prompting submodule will notify the maintenance personnel to return. If it is in the started state, the discarding submodule will ignore the event (fault clearing information, which may be triggered by the maintenance operation).

[0113] In one embodiment, on the basis of any one of the above embodiments, a rail transit AFC fault reporting processing device is provided, which refers to Figure 5 Further comprising:

[0114] A fault statistics module 70 is configured to count and prompt the number of false alarms of the device fault corresponding to each fault code of each device code in a preset time period;

[0115] A fault degradation module 80 is configured to perform degradation processing on the fault event of the fault code of the device code when the number of false alarms of the device fault of the same fault code of the same device code exceeds a preset number.

[0116] Specifically, in the data analysis of the previous fault reporting information, there are often false alarms of a small number of devices, and often the fault cannot be reproduced when the maintenance personnel arrive at the scene, or the fault never occurs according to the feedback of the site managers. Therefore, under the technical premise that the root cause of the device cannot eliminate such false alarms, the fault degradation module is adopted to degrade the fault reporting by using a data analysis-based method.

[0117] They can be implemented by program codes executable by a computing device, so that they can be stored in a storage device for execution by the computing device, or they can be made into individual integrated circuit modules, or a plurality of modules or steps in them can be made into a single integrated circuit module. Thus, the present application is not limited to any particular combination of hardware and software.

[0118] In the above embodiments, the description of each embodiment has its own emphasis, and the parts not described or recorded in detail in a certain embodiment can be referred to the related description of other embodiments.

[0119] Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be realized by electronic hardware or a combination of computer software and electronic hardware. Whether the functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present application.

[0120] The units described as separate components can or can not be physically separated, and the components shown as units can or can not be physical units, i.e., they can be located in one place or distributed on multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the present embodiment.

[0121] In addition, the various functional units in the embodiments of the present application can be integrated in one processing unit, or each can exist physically as a separate unit, or two or more units can be integrated in one unit. The above-mentioned integrated unit can be implemented in the form of hardware, or in the form of a software functional unit.

[0122] It should be noted that the above embodiments can be freely combined as needed. The above is only a preferred embodiment of the present application, and it should be pointed out that, for those skilled in the art, without departing from the principles of the present application, a number of improvements and refinements can be made, which should be considered as the protection scope of the present application.

Claims

1. A processing method for reporting rail transit AFC failures, characterized in that, The method comprises the steps of: acquiring AFC fault reporting data periodically according to preset time intervals within a maintenance time and writing the AFC fault reporting data into a local data table; screening out to-be-processed fault data from the AFC fault reporting data within a plurality of the preset time intervals; classifying and grouping the to-be-processed fault data according to the same fault code of the same device code; when the last fault event in the to-be-processed fault data in the same group is in a recovered state, reporting clearing information of the to-be-processed fault event; when the last fault event in the to-be-processed fault data in the same group is in an occurrence state, selecting to-be-processed fault events greater than or equal to the preset time interval, performing hierarchical identification on the to-be-processed fault events, and then reporting the to-be-processed fault data after the hierarchical identification; generating a fault clearing work order or a fault occurrence work order according to the reporting information of the to-be-processed fault event; wherein the screening out of the to-be-processed fault data from the AFC fault reporting data within a plurality of the preset time intervals comprises: generating to-be-processed fault data after screening out unnecessary fault data and / or purpose fault data from the AFC fault reporting data within a plurality of the preset time intervals; the purpose fault data includes fault data of a multi-purpose device used as a single-purpose device. 2.The processing method of rail transit AFC fault reporting according to claim 1, characterized in that, after the generating of the fault clearing work order or the fault occurrence work order according to the reporting information of the to-be-processed fault event, comprising: when the fault occurrence work order is received by a work order maintenance department, detecting whether the to-be-processed fault event corresponding to the fault occurrence work order already exists in the current processing work order of the work order maintenance department; if the to-be-processed fault event corresponding to the fault occurrence work order already exists in the current processing work order, ignoring the fault occurrence work order.

3. The processing method of rail transit AFC fault reporting according to claim 2, characterized in that, after the generating of the fault clearing work order or the fault occurrence work order according to the reporting information of the to-be-processed fault event, comprising: when the fault clearing work order is received by the work order maintenance department, detecting whether the to-be-processed fault event corresponding to the fault clearing work order already exists in the current processing work order of the work order maintenance department; if the to-be-processed fault event corresponding to the fault clearing work order does not exist in the current processing work order, ignoring the fault clearing work order; if the to-be-processed fault event corresponding to the fault clearing work order exists in the current processing work order, analyzing whether there are other to-be-processed fault events in addition to the to-be-processed fault event in the fault clearing work order in the current processing work order; if there are other to-be-processed fault events in addition to the to-be-processed fault event in the fault clearing work order in the current processing work order, canceling the maintenance requirement of the fault clearing work order; if there are no other to-be-processed fault events in addition to the to-be-processed fault event in the fault clearing work order in the current processing work order, canceling the current processing work order or notifying of abandonment of maintenance according to the order receiving state of the current processing work order.

4. The processing method of rail transit AFC fault reporting according to claim 3, characterized in that, after the canceling, prompting or discarding processing according to the reporting information of the fault work order cleaning process and the fault work order generation process, further comprising: counting and prompting the number of device fault false alarms corresponding to each fault code of each device code within a preset time period; When the false alarm times of the same fault code of the same equipment coding exceed the preset times, the fault events of the fault code of the equipment coding are downgraded.

5. A processing device for reporting rail transit AFC failures, characterized in that, Comprise: The fault data acquisition module periodically acquires AFC fault reporting data according to a preset time interval within the maintenance time, and writes the AFC fault reporting data into a local data table; The fault data screening module is used for screening out the to-be-processed fault data from the AFC fault reporting data within a plurality of preset time intervals; The grouping classification module is used for classifying and grouping the to-be-processed fault data according to the same fault code of the same equipment coding; The data reporting module is used for reporting the clearing information of the to-be-processed fault event when the last fault event in the to-be-processed fault data in the same group is in the recovered state; The data reporting module is also used for selecting the to-be-processed fault event greater than or equal to the preset time interval when the last fault event in the to-be-processed fault data in the same group is in the occurrence state, and then reporting the to-be-processed fault data after hierarchical identification; The work order generation module is used for generating a fault clearing work order or a fault occurrence work order according to the reporting information of the to-be-processed fault event; The fault data screening module is also used for generating the to-be-processed fault data after screening out the fault data without processing and / or the purpose fault data from the AFC fault reporting data within a plurality of preset time intervals; the purpose fault data includes the fault data of a multi-purpose equipment used as a single-purpose equipment.

6. The processing device for reporting rail transit AFC failures according to claim 5, characterized in that, Further comprise: The work order processing module is used for canceling, prompting or discarding the fault clearing work order or the fault occurrence work order.

7. The processing device for reporting rail transit AFC failures according to claim 6, characterized in that, The work order processing module specifically comprises: If the fault event in the fault clearing work order or the fault occurrence work order is in the processing state, then The canceling submodule is used for canceling the fault work order in the unaccepted state; The prompting submodule is used for issuing a prompt to end the maintenance in the accepted but not entered maintenance state; The discarding submodule is used for giving up the maintenance in the entered maintenance state.

8. The processing device for reporting AFC failures of rail transit according to any one of claims 5-7, characterized in that, Further comprise: The fault statistics module is used for counting and prompting the device fault false alarm times corresponding to each fault code of each equipment coding within a preset time period; The fault degradation module is used for degrading the fault events of the fault code of the equipment coding when the device fault false alarm times of the same fault code of the same equipment coding exceed the preset times.

Images