Shulou(Shulou.com)06/02 Report--

The surveillance target is related to the flight data. Automatic correlation

The system checks the consistency of each normally updated system track that is allowed to be checked and the matching factors of all valid flight plans (including address code, secondary code, flight number, route and time, etc.). When a system integrated track and a flight plan pass all conditional checks And there is an one-to-one correspondence between the track and the plan (only the only track and the only plan meet the conditions), and the system will automatically establish the relationship between the integrated track of the system and the flight plan. this process is the automatic correlation between the track and the flight plan.

The automatic correlation check is carried out by the system process CETC_TPP and follows the data update. There is no fixed calculation cycle, that is, each track target update or flight plan update will trigger the automatic correlation check, and the relevant results are also reflected immediately.

Object requirements for automatic correlation inspection

Only flight plans and tracks that meet the following conditions are allowed to carry out automatic related inspection:

Flight plans and tracks are free and not relevant.

L the status requirements of the flight plan must be after coordination (including) and before termination or cancellation (excluding). If the scheduled state is pre-activated, whether to allow automatic correlation is determined by the offline parameter switch in the database (PLAN_PREA_COUPLE_PERMIT_HOST is the control switch in the active system state; PLAN_PREA_COUPLE_PERMIT_SPARE is the control switch in the backup system state).

L the flight plan has not been manually related.

The track is normal and cannot be extrapolated or vanished, nor can it be a clearly stated test target or simulation target.

L when the system is a backup system, the correlation between the track and the plan has not been synchronized by the active system.

If the system is set up to restrict the relevant area (PLAN_AUTOCOUPLE_PERMIT_AREA is set to 1), the location of the track target must be within the automatic correlation restricted area defined offline.

L the flight plan for take-off from this site will only be automatically related to the track target of the current position in the control area.

L consider the automatic correlation of address codes

If the system is set to automatic correlation offline need to consider the address code (PLAN_AUTOCOUPLE_ADDRESS is set to 1), and the track and plan are carried with the address code information, the system will first compare whether the address code of both sides is consistent, if the address code is the same, the two sides will be directly related, no other checks will be carried out; if the address code is inconsistent, it is necessary to check the consistency of the secondary code, flight number, route and time.

L does not consider the automatic correlation of address codes

When the system is set to automatically correlate without considering the address code (PLAN_AUTOCOUPLE_ADDRESS is set to 0), or when the track is found to be inconsistent with the planned address code in the address code consistency check, or when the address code consistency check cannot be carried out (at least one of the parties is missing the address code information), the system will check the consistency of the secondary code, if the consistency check of the secondary code cannot be carried out. The consistency check of the flight number will be carried out when the system is set to automatic correlation and the flight number needs to be considered (PLAN_AUTOCOUPLE_CALL is set to 1).

Priority factor: secondary code

The consistency check of the secondary code requires that both the track and the flight plan have a valid secondary code. If at least one side of the track and plan is missing a valid secondary code, the consistency check of the secondary code can not be carried out.

The flight plan may have two secondary codes, ASSR and PSSR, so when the automatic correlation considers PSSR (PLAN_AUTOCOUPLE_PSSR is set to 1), the consistency of the secondary code means that at least one of the ASSR and PSSR in the flight plan is the same as the secondary code of the track; when the automatic correlation does not consider the PSSR (PLAN_AUTOCOUPLE_PSSR is set to 0), the secondary code consistency requires that the ASSR in the flight plan and the secondary code of the track are the same.

Because the secondary code is not unique, the system will check the consistency of the route and time after the consistency of the secondary code is satisfied, and the automatic correlation will be carried out only after all the conditions are met.

The consistency conditions of route and time are as follows, and the requirements must be met at the same time:

The actual location of the track is near the planned route described in the flight plan, that is, the distance to the planned route (the vertical distance to the flight segment or the straight line distance to the report point) is less than the offline threshold parameter (PLAN_AUTOCOUPLE_ROUTE_DISTANCE) set in the database.

According to the current position and speed of the track, the time of arrival at the nearest report point on the planned route is predicted, and the difference between the estimated arrival time of the report point and the planned time does not exceed the threshold value (the parameter PLAN_AUTOCOUPLE_ROUTE_TIME_DEP is used when the takeoff airport in the flight plan is the field, and the other cases are PLAN_AUTOCOUPLE_ROUTE_TIME).

The difference between the current heading of the track and the direction of the nearest planned route does not exceed the threshold (the monitoring data processing VSP parameter PLAN_AUTOCOUPLE_ROUTE_HEADING set offline in the database).

Secondary consideration: flight number

Because the accuracy and uniqueness of the target flight number reported in S-mode radar / ADS-B data / MLAT data is lower than that of the secondary code, the system is set to give priority to the secondary code without considering the address code. when the consistency of the secondary code can not be checked, and the flight number needs to be considered in the automatic correlation of the system setting, the flight number consistency check will be carried out.

Flight number consistency check requires flight number information to be carried in the track data (which can be provided by S-mode radar / ADS-B data / MLAT data participating in target fusion). If the flight numbers of the tracks and flight plans are exactly the same, the flight numbers of the two sides are considered to be the same.

Similar to the case of the secondary code, the system will also carry out an additional route and time consistency check after the flight number consistency is met, and the automatic correlation will not be carried out until all conditions are met, and the route and time consistency check method is the same as in the previous section.

two。 Automatic decorrelation

For the case where the flight plan has been related to the track, the system will cut off the connection between the two when one of the following conditions is met, and the plan and track will return to an unrelated state, a process called automatic de-correlation between flight plan and track.

L automatically change the status of the conditional flight plan to be terminated or cancelled.

When the status of the flight plan related to the track is changed to termination or cancellation, the system will automatically de-relate it.

The track target disappears.

Except for the cases related to the use of address codes, when the track target has a valid secondary code (except in the case of changing to a special secondary code such as 7500, 7600 and 7700), its secondary code is inconsistent with the ASSR and PSSR in the flight plan.

Except for cases related to the use of address codes, the track target does not have a valid secondary code and does not carry flight number information, or flight number information (which is possible when combining ADS-B information or S-mode radar targets), but this flight number is not consistent with the planned flight number.

When a monitoring source that has reported an address code no longer reports the address code, or when the track target flies out of the scope of the monitoring source, if the track target is already related to the plan, it will not be automatically de-correlated.

3. Manual correlation

The correlation between the plan and the track can also be established manually by the controller with control authority, which is called the flight plan and the track manual correlation.

Manual correlation has certain limitations: either the secondary code of the track is consistent with the PSSR or ASSR in the flight plan, or the address codes of both sides are the same, and at least one of the two conditions can be automatically correlated.

When the controller manually correlates the tracks and plans that do not meet the above conditions, the system will give a message of mismatch between the secondary code and the address code.

When the secondary code of the track target is an invalid code, manual correlation cannot be done.

For the integrated track with ADS-B data / S mode radar data participating in fusion, or if it is a pure ADS-B/S mode target, if it carries flight number information but is not related to the flight plan, it will be prompted on the sign to remind the controller to carry out manual correlation.

4. Manual decorrelation

The de-correlation of plans and tracks can also be carried out manually by controllers with control authority, which is called manual de-correlation between flight plans and tracks.

If you have made a manual de-related plan, it can no longer be automatically related to any track.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.