Data entry method and device, electronic equipment and medium

Abstract

The invention relates to a data entry method and device, electronic equipment and a medium, the method is applied to one entry source in multiple entry sources, and the method comprises the following steps: receiving an entry request for entering first data for a target object; determining whether historical input data for the target object exists or not; under the condition that the historical input data for the target object exists, obtaining a historical input source corresponding to the last historical input data; determining whether the historical input source is consistent with an execution input source of the input request; under the condition that the historical input source is inconsistent with the execution input source, determining input priorities of the historical input source and the execution input source; and prohibiting the entry of the first data under the condition that the entry priority indicates that the priority of the historical entry source is higher than the priority of the execution entry source. The input process is convenient, input card control is intelligent, and the intelligent degree of air transportation information management and the collaborative consistency of multiple input sources can be improved.

Description

Technical Field

[0001] The present disclosure relates to the field of logistics and air transportation technology, and in particular to a method, device, electronic device, and medium for data entry. Background Art

[0002] With increasingly stringent requirements for logistics timeliness, air transport and the establishment of multiple regional warehouses for nearby cargo transfers are often used to meet these requirements. During air cargo transport, ground service personnel typically enter payload information (specified as preload weight and actual load weight) via a handheld terminal in the Ground Service Management System (GMS). The GMS then synchronizes this payload information with the terminal dispatch management system of the Air Operations Command Center (AOC). Changes to the payload weight are also synchronized with the terminal dispatch management system in the event of weather conditions, airway control, or cargo additions or returns. Dispatchers using the GMS can assess flight schedules based on preload weight and actual load weight for flight releases.

[0003] In the process of realizing the concept disclosed herein, the inventors discovered that there are at least the following technical problems in the related art: when the handheld terminal is unable to enter or change the payload information due to signal blind spots, equipment failures, etc., the terminal dispatch personnel are mostly notified offline to operate the terminal dispatch management system to enter or change the payload information. However, after the handheld terminal is repaired, it often happens that the terminal dispatch personnel enter or change the payload information through the terminal dispatch management system and the on-site support personnel enter or change the payload information through the ground service management system at the same time. This will result in the multi-source entry of payload information and the final entered data will be inconsistent with the actual situation, which will lead to inaccurate flight release assessment and may cause flight safety risks. Summary of the Invention

[0004] In order to solve the above technical problems or at least partially solve the above technical problems, embodiments of the present disclosure provide a method, device, electronic device, and medium for data entry.

[0005] In a first aspect, an embodiment of the present disclosure provides a method for data entry. The method is applied to one of multiple entry sources, and includes: receiving an entry request for entering first data for a target object; determining whether there is historical entry data for the target object; if there is historical entry data for the target object, obtaining the historical entry source corresponding to the most recent historical entry data; determining whether the historical entry source is consistent with the execution entry source of the entry request; if the historical entry source is inconsistent with the execution entry source, determining the entry priority of the historical entry source and the execution entry source; if the entry priority indicates that the priority of the historical entry source is higher than the priority of the execution entry source, prohibiting the entry of the first data.

[0006] According to an embodiment of the present disclosure, the above-mentioned method also includes: when the above-mentioned entry priority indicates that the priority of the above-mentioned historical entry source is lower than the priority of the above-mentioned execution entry source, entering the above-mentioned first data; when the above-mentioned first data is successfully entered, associating the above-mentioned first data with the corresponding execution entry source and storing it as an entry result; synchronizing the above-mentioned entry result to other entry sources other than the above-mentioned execution entry source; the above-mentioned other entry sources include the above-mentioned historical entry source.

[0007] According to an embodiment of the present disclosure, the above method also includes: entering the above first data when the above historical entry source is consistent with the execution entry source of the above entry request; and entering the above first data when there is no historical entry data for the above target object.

[0008] According to an embodiment of the present disclosure, the target object includes a target flight, and the first data includes a preload weight for the target flight. Entering the first data includes determining whether the preload weight is less than the maximum available payload limit of the target flight; if the preload weight is less than the maximum available payload limit, storing the preload weight in a first database corresponding to the execution entry source; and if the preload weight exceeds the maximum available payload limit, issuing a first prompt indicating a preload excess and entry failure.

[0009] According to an embodiment of the present disclosure, the target object is a target flight, and the first data includes the actual load weight for the target flight. If historical data entry exists for the target object, entering the first data includes: displaying a function key for canceling interception on the front-end display interface; the function key is used to trigger a function for allowing input of the actual load weight after the cancel interception operation is successfully executed; upon receiving a confirmation instruction for the function key, executing the cancel interception operation, including: setting the historical actual load weight to zero, associating the result of the actual load weight being zero with the corresponding execution entry source and storing it as a cancel interception result; synchronizing the cancel interception result to other entry sources other than the execution entry source; the other entry sources include the historical entry source. After receiving feedback from the other entry sources indicating that the cancel interception result synchronization is successful, entering the actual load weight. If historical data entry does not exist for the target object, entering the first data includes: entering the actual load weight.

[0010] According to an embodiment of the present disclosure, the entry of the above-mentioned actual load weight includes: determining whether the above-mentioned actual load weight is less than the maximum available payload limit of the above-mentioned target flight; if the above-mentioned actual load weight is less than the above-mentioned maximum available payload limit, storing the above-mentioned actual load weight in the first database corresponding to the above-mentioned execution entry source; if the above-mentioned actual load weight exceeds the above-mentioned maximum available payload limit, issuing a second prompt message of the actual load weight and entry failure.

[0011] According to an embodiment of the present disclosure, the execution entry source is an airport dispatch management system or a ground service management system. If the execution entry source is an airport dispatch management system, a third prompt message is also issued to remind flight dispatch personnel to conduct a release assessment and verification if the actual load weight exceeds the maximum release weight limit and is less than the maximum available payload limit.

[0012] According to an embodiment of the present disclosure, the method further includes receiving priority configuration information for multiple entry sources in the entry source list, wherein the priority configuration information includes entry priorities of the entry sources. Determining the entry priorities of the historical entry source and the execution entry source includes determining the entry priorities of the historical entry source and the execution entry source based on the priority configuration information.

[0013] According to an embodiment of the present disclosure, the priority configuration information further includes: the effective period of the input source. The method further includes: receiving control information on the effective period; the control information is used to limit the takeover period of the second input source with a high priority to the first input source with a low priority, and after the takeover is completed, the second input source is controlled to be invalid and the first input source is controlled to be effective; according to the control information, the input effectiveness status of each input source is set; according to the input effectiveness status, whether the execution input source is valid is determined; if the execution input source is valid, the following operations are performed: determining whether the historical input source is consistent with the execution input source of the input request.

[0014] In a second aspect, an embodiment of the present disclosure provides a data entry device. The device is the main body of one of the multiple entry sources, and includes: a request receiving module, a historical data query module, an entry source acquisition module, an entry source comparison module, a priority determination module, and an entry control module. The request receiving module is used to receive an entry request for entering first data for a target object. The historical data query module is used to determine whether there is historical entry data for the target object. The entry source acquisition module is used to obtain the historical entry source corresponding to the most recent historical entry data if there is historical entry data for the target object. The entry source comparison module is used to determine whether the historical entry source is consistent with the execution entry source of the entry request. The priority determination module is used to determine the entry priority of the historical entry source and the execution entry source if the historical entry source and the execution entry source are inconsistent. The entry control module is used to prohibit the entry of the first data if the entry priority indicates that the priority of the historical entry source is higher than the priority of the execution entry source.

[0015] In a third aspect, embodiments of the present disclosure provide an electronic device. The electronic device includes a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other via the communication bus; the memory is configured to store a computer program; and the processor is configured to implement the aforementioned data entry method when executing the program stored in the memory.

[0016] In a fourth aspect, embodiments of the present disclosure provide a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the data entry method described above.

[0017] The above technical solutions provided by the embodiments of the present disclosure have at least some or all of the following advantages:

[0018] When receiving an entry request for a target object, by determining whether there is historical entry data for the target object, it is possible to identify whether it is a first entry situation or a multiple entry situation. For the multiple entry situation, by comparing whether the historical entry source corresponding to the most recent historical entry data is consistent with the execution entry source of the entry request, and in case of inconsistency, identifying the entry priority of the execution entry source and the historical entry source, if the entry priority of the historical entry source is higher than that of the execution entry source, prohibiting the current execution entry source from entering the first data; in this way, after the entry source with a higher priority takes over the entry, the entry priority card Control and prohibition logic: even if a lower-priority entry source returns to normal during the takeover period of a higher-priority entry source, relevant data cannot be entered, thereby effectively avoiding conflicts or repeated entry during the data entry process of multiple data sources, resulting in the entry data being inconsistent with the actual situation (for example, if two data sources are both entered, the result is that the entered data is twice the single entry data). In addition, this set of entry logic supports the simultaneous operation of multiple entry sources, without the need to control the human behavior patterns of each entry source. The entry process is convenient and the entry card control is intelligent, which helps to improve the intelligence level of air transport information management and the collaborative consistency of multiple entry sources. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the present disclosure.

[0020] In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or related technical descriptions. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0021] Figure 1 The system architecture of the data entry method and apparatus applicable to the embodiments of the present disclosure is schematically shown;

[0022] Figure 2 The following schematically shows a flow chart of a method for data entry according to an embodiment of the present disclosure;

[0023] Figure 3 The following schematically shows a flow chart of a method for data entry according to another embodiment of the present disclosure;

[0024] Figure 4 The following schematically shows a flow chart of a method for data entry according to another embodiment of the present disclosure;

[0025] Figure 5The following schematically shows a flow chart of a method for data entry according to yet another embodiment of the present disclosure;

[0026] Figure 6 The following schematically shows a structural block diagram of a data entry device according to an embodiment of the present disclosure;

[0027] Figure 7 The structural block diagram of the electronic device provided by the embodiment of the present disclosure is schematically shown. DETAILED DESCRIPTION

[0028] In cases where a handheld terminal is unable to enter or change payload information due to signal blind spots, equipment failure, or other reasons, the terminal dispatcher is often notified offline to operate the terminal dispatch management system to enter or change the payload information. However, after the handheld terminal is repaired, it is common for the terminal dispatcher and on-site support personnel to enter or change payload information simultaneously through the terminal dispatch management system and the ground service management system. This results in multiple sources of payload information being entered, and the final entered data is inconsistent with the actual situation. This can lead to inaccurate flight release assessments and potential flight safety risks.

[0029] To avoid conflicts in data entry from multiple sources, as well as issues with duplicate data entry and data changes that can lead to inconsistent data entry results, one feasible approach is to prevent simultaneous data entry from multiple sources (e.g., the ground service management system and the terminal dispatch management system) through management or offline notification. For example, if a handheld terminal malfunctions, one approach is to wait for the handheld terminal to be repaired before re-entering the data. However, this approach requires the on-site support staff to submit payload data after the handheld terminal is repaired. This repair process can delay flight dispatch and affect on-time performance. Another approach is to notify the terminal dispatch staff to submit payload data through the terminal dispatch management system after the handheld terminal malfunctions. During this time, assuming the handheld terminal is repaired, the on-site support staff will be manually informed not to enter payload data through the handheld terminal to avoid data conflicts. Alternatively, after the handheld terminal is repaired, the terminal dispatch staff can be manually informed not to enter data through the terminal dispatch management system anymore. The on-site support staff can then enter data through the ground service management system on the handheld terminal. However, this approach requires significant communication overhead and manual control, and cannot monitor or prevent unauthorized data entry due to poor communication.

[0030] In view of this, embodiments of the present disclosure provide a method, apparatus, electronic device and medium for data entry, and the method is applied to an entry source among multiple entry sources, including: receiving an entry request for entering first data for a target object; determining whether there is historical entry data for the target object; if there is historical entry data for the target object, obtaining the historical entry source corresponding to the most recent historical entry data; determining whether the historical entry source is consistent with the execution entry source of the entry request; if the historical entry source is inconsistent with the execution entry source, determining the entry priority of the historical entry source and the execution entry source; if the entry priority indicates that the priority of the historical entry source is higher than the priority of the execution entry source, prohibiting the entry of the first data.

[0031] The above method can be used in the scenario of entering flight payload data, and can also be expanded and applied to any scenario with the need to resolve entry conflicts.

[0032] The solution provided by the method can identify whether it is the first entry or multiple entry situation by determining whether there is historical entry data for the target object when receiving an entry request for the target object. For the multiple entry situation, the method compares whether the historical entry source corresponding to the most recent historical entry data is consistent with the execution entry source of the entry request. If they are inconsistent, the entry priority of the execution entry source and the historical entry source is identified. If the entry priority of the historical entry source is higher than that of the execution entry source, the execution entry source is prohibited from entering the first data. In this way, after the entry source with a higher priority takes over the entry, the entry priority can be used to The priority card control and prohibition logic prevents the entry of relevant data even if the lower-priority input source returns to normal during the takeover period of the higher-priority input source, thereby effectively avoiding conflicts or repeated entries in the data entry process of multiple data sources, resulting in the input data being inconsistent with the actual situation (for example, if two data sources are both input, the input data will be twice the input data of a single source). In addition, this set of input logic supports the simultaneous operation of multiple input sources, and there is no need to control the human behavior patterns of each input source. The input process is convenient and the input card control is intelligent, which helps to improve the intelligence level of air transport information management and the collaborative consistency of multiple input sources.

[0033] In order to make the purpose, technical solutions and advantages of the embodiments of the present disclosure clearer, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are part of the embodiments of the present disclosure, rather than all of the embodiments. Based on the embodiments in the present disclosure, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present disclosure. In the terms of the embodiments of the present disclosure, priority higher than (>), lower than (<) and equal to (=) are three different size relationships between priority levels; numerical value higher than (≥) and lower than (≤) can include the case where the numerical values ​​are equal.

[0034] Figure 1 The system architecture of the method and apparatus for data entry applicable to the embodiments of the present disclosure is schematically shown.

[0035] Reference Figure 1 As shown, the system architecture 100 of the method and apparatus for data entry applicable to the embodiment of the present disclosure includes: a first terminal device 111 , a first server 112 , a second terminal device 121 and a second server 122 .

[0036] The first terminal device 111 communicates with the first server 112 via a network.

[0037] The second terminal device 121 communicates with the second server 122 via a network.

[0038] The first server 112 and the second server 122 communicate with each other through a network.

[0039] In some application scenarios, a data entry application X may be installed on the first terminal device 111, and the first server 112 is used to provide data processing and data storage services for application X. A data entry application Y may be installed on the second terminal device 121, and the second server 122 is used to provide data processing and data storage services for application Y. Application X and application Y may serve as two different input sources, with the first terminal device 111 corresponding to the first input source and the second terminal device 121 corresponding to the second input source. For example, in the air transportation sector, application X may be a ground service management system (an example of a first input source), and application Y may be an airport dispatch management system (an example of a second input source). On-site support personnel can enter payload information (e.g., preload weight and actual load weight) using the ground service management system installed on the first terminal device 111. AOC airport dispatch personnel can enter payload information using the airport dispatch management system installed on the second terminal device 121.

[0040] The data entry method provided in the embodiment of the present disclosure may be executed by the first terminal device 111 or the second terminal device 121. Accordingly, the first terminal device 111 or the second terminal device 121 serves as a data entry device.

[0041] It is understandable that different input sources in the multiple input sources may refer to: different input systems (which may be various software systems, systems combining software and hardware, etc.), different input terminals, or different input accounts, etc. Different input systems are used as examples here.

[0042] In other application scenarios, the first terminal device 111 and the second terminal device 121 are installed with the same input system, and the difference in input sources comes from different terminal devices. By assigning different input priorities to different terminal devices, the data input method provided by the embodiment of the present disclosure is implemented.

[0043] In some other application scenarios, the above system architecture can be the same terminal device or different terminal devices, and the difference in input sources comes from different input accounts. By assigning different input priorities to different input accounts, the data input method provided by the embodiment of the present disclosure is implemented.

[0044] It can be understood that the system architecture 100 of the present disclosure takes air transportation as an example. The data entry method provided by the embodiment of the present disclosure can also be expanded to apply to scenarios with multiple entry sources, where multiple entry sources can all perform data entry and set relatively high and low entry permissions; wherein, the entry of high-priority permissions is not subject to the disablement restriction of the pre-entry of the low-priority permission entry source; that is, the prior entry of the low-priority permission does not affect the subsequent data entry of the high-priority permission; however, the prior entry of the high-priority permission has a disablement restriction on the subsequent entry of the low-priority permission entry source.

[0045] The first exemplary embodiment of the present disclosure provides a method for data entry. The above method is applied to one of the multiple entry sources. For example, Figure 1 The first input source in the exemplary system architecture 100 is located in the first terminal device 111 , or is applied to the second input source in the second terminal device 121 .

[0046] Figure 2 The flowchart of the data entry method according to an embodiment of the present disclosure is schematically shown.

[0047] Reference Figure 2 As shown, the data entry method provided by the embodiment of the present disclosure includes the following steps: S210, S220, S230a, S240, S250b and S260b.

[0048] In step S210 , an entry request for entering first data for a target object is received.

[0049] The target object mentioned above refers to the object associated with the first data to be entered.

[0050] In some implementation scenarios, the target object may be a target flight. For example, the first data entered for a particular flight may include: a value H13 for the preloaded weight (i.e., the estimated payload weight); or a value H14 for the actual payload weight (i.e., the actual payload weight). The first data may also include information such as the entry time and the account number.

[0051] In step S220 , it is determined whether there is any historical input data for the target object.

[0052] In this step S220 , when the execution subject is the first terminal device 111 , the first terminal device 111 may query whether there is historical entry data for the target object from the local cache or from the database corresponding to the first server 112 .

[0053] When the execution subject is the second terminal device 121 , the second terminal device 121 may query whether there is historical entry data for the target object from a local cache or from a database corresponding to the second server 122 .

[0054] Since the data between the first server 112 and the second server 122 are updated synchronously, no matter whether the execution subject is the first terminal device or the second terminal device, when data is entered based on multiple input sources, the data entry records corresponding to each input source are the same and updated synchronously, so the results of the historical input data obtained by the corresponding query are also the same.

[0055] In step S230a, if there is historical entry data for the target object, the historical entry source corresponding to the most recent historical entry data is obtained.

[0056] In an implementation scenario C1, taking the execution subject as the first terminal device 111 and the execution entry source corresponding to application X as an example, for a target flight that is being loaded but has not yet taken off, it is found that there is historical entry data and there are two records, namely: record R1 corresponding to 11:00 on December 10, 2023: {preload weight H11, entry source is application X, entry account, entry time,...}; record R2 corresponding to 11:05 on December 10, 2023: {preload weight H12, entry source is application Y}; it is determined that the historical entry source corresponding to the most recent historical entry data is application Y.

[0057] In step S240 , it is determined whether the historical entry source is consistent with the execution entry source of the entry request.

[0058] In the above implementation scenario C1, since the historical entry source is application Y and the execution entry source of the entry request is application X, if it is determined that the two are inconsistent, step S250b is executed.

[0059] In step S250b, when the historical entry source is inconsistent with the execution entry source, the entry priority of the historical entry source and the execution entry source is determined.

[0060] For example, the input priority of application Y is higher than that of application X, ensuring that application Y takes over the input of application X. In this embodiment, the historical input source is application Y, the execution input source is application X, and the priority of the historical input source is higher than the priority of the execution input source. Therefore, the subsequent step S260b is executed to prohibit the input of the first data.

[0061] In step S260b, when the input priority indicates that the priority of the historical input source is higher than the priority of the execution input source, inputting of the first data is prohibited.

[0062] In an embodiment of the present disclosure, the entry of high-priority permissions is not subject to the disabling restriction of the pre-entry of the low-priority permission entry source; that is, the prior entry of low-priority permissions does not affect the subsequent data entry of high-priority permissions; however, the prior entry of high-priority permissions has a disabling restriction on the subsequent entry of the entry source of low-priority permissions.

[0063] In some embodiments, in addition to prohibiting the first data from being entered, the method may also include issuing a related prompt message, such as: the preloaded data has been taken over by the AOC terminal dispatcher, and if any adjustments are required, please contact the AOC terminal dispatcher for processing.

[0064] If the first terminal device hosting application X fails, application Y can take over data entry. After application Y enters data, historical data with application Y as the historical entry source is generated. Because application Y's entry priority is higher than application X's, even if the first terminal device corresponding to application X recovers, data entry will not be possible during the period when application Y takes over. In other words, the logic of steps S210 to S260b above ensures that application X cannot enter related data after application Y enters data, effectively avoiding conflicts in data entry from multiple data sources and inconsistencies between the entry results and the actual results.

[0065] In the embodiment including the above steps S210 to S260b, when an entry request for a target object is received, by determining whether there is historical entry data for the target object, it is possible to identify whether it is a first entry situation or a multiple entry situation. For the multiple entry situation, by comparing whether the historical entry source corresponding to the most recent historical entry data is consistent with the execution entry source of the entry request, and if they are inconsistent, identifying the entry priority of the execution entry source and the historical entry source. If the entry priority of the historical entry source is higher than that of the execution entry source, the execution entry source is prohibited from entering the first data. In this way, the entry takeover can be performed at the entry source with a higher priority. Finally, through the card control and prohibition logic of the input priority, even if the lower priority input source returns to normal during the takeover period of the higher priority input source, the relevant data cannot be entered, thereby effectively avoiding conflicts or repeated entries in the data entry process of multiple data sources, resulting in the input data being inconsistent with the actual situation (for example, if two data sources are both input, the input data will be twice the single input data). In addition, this set of input logic supports the simultaneous operation of multiple input sources, and there is no need to control the human behavior patterns of each input source. The input process is convenient and the input card control is intelligent, which helps to improve the intelligence level of air transport information management and the collaborative consistency of multiple input sources.

[0066] Figure 3 The figure schematically shows a flow chart of a data entry method according to another embodiment of the present disclosure.

[0067] Reference Figure 3 As shown, the data entry method provided by the embodiment of the present disclosure includes, in addition to the above steps S210 to S260b, the following steps: S260a, S270 and S280.

[0068] In step S260a, when the input priority indicates that the priority of the historical input source is lower than the priority of the execution input source, the first data is input.

[0069] In another implementation scenario C2, taking the execution subject as the second terminal device 121, the execution entry source corresponding to application Y, and the preload weight H13 as an example, for a target flight that is being loaded but has not yet taken off, it is found that there is historical entry data and there is a record, namely: record R1 corresponding to 11:00 on December 10, 2023: {preload weight H11, entry source is application X}; it is determined that the historical entry source corresponding to the most recent historical entry data is application X.

[0070] In the above implementation scenario C2, since the historical entry source is application X and the execution entry source of the entry request is application Y, if it is determined that the two are inconsistent, step S250b is executed.

[0071] In step S250b, since the historical entry source is application X and the execution entry source is application Y, the priority of the historical entry source is lower than the priority of the execution entry source, and the subsequent step S260a is executed to enter the above-mentioned first data.

[0072] In step S270, when the first data is successfully entered, the first data is associated with the corresponding execution entry source and stored as an entry result.

[0073] In implementation scenario C2, the above input results are stored to obtain corresponding records, for example, record R3 is generated: {preload weight H13, input source is application Y, input account, input time, ...}.

[0074] In step S280, the above-mentioned entry result is synchronized to other entry sources other than the above-mentioned execution entry source; the above-mentioned other entry sources include the above-mentioned historical entry source.

[0075] For example, in implementation scenario C2, the second terminal device 121 (corresponding input source is application Y) synchronizes the input result to the first terminal device (corresponding input source is application X). After receiving the synchronized record R3, the first terminal device stores it in the database of the first server.

[0076] In the embodiment including steps S260a to S280, the above-mentioned entry process embodies the following entry logic: the entry of high-priority permissions is not subject to the pre-entry disabling restriction of the low-priority permission entry source; that is, the prior entry of low-priority permissions does not affect the subsequent data entry of high-priority permissions; however, the prior entry of high-priority permissions has a disabling restriction on the subsequent entry of the low-priority permission entry source. This can effectively ensure that the high-priority entry source can take over the entry after the low-priority entry source encounters a problem, and prohibit the entry of the low-priority entry source during the high-priority entry source takeover, thereby avoiding entry conflicts and inconsistencies.

[0077] Reference Figure 3 As shown, the data entry method provided by the embodiment of the present disclosure, in addition to the above steps S210 to S260b, also includes the following steps corresponding to the branches: S230b and S250a.

[0078] In step S230b, if there is no historical input data for the target object, the first data is input.

[0079] In step S250a, when the historical entry source is consistent with the execution entry source of the entry request, the first data is entered.

[0080] In this embodiment, there is no entry restriction for data entered successively by the same entry source.

[0081] According to an embodiment of the present disclosure, the target object includes a target flight, and the first data includes: a preload weight for the target flight.

[0082] The step of inputting the first data includes:

[0083] Determine whether the above preload weight is less than the maximum available payload limit of the above target flight;

[0084] If the preload weight is less than the maximum available payload limit, storing the preload weight in the first database corresponding to the execution entry source;

[0085] In the case that the above-mentioned preload weight exceeds the above-mentioned maximum available payload limit, a first prompt message of preload excess and entry failure is issued.

[0086] For example, when the execution subject is the first terminal device 111, during the process of entering the first data, if the preload weight H13 to be entered is less than the maximum available payload limit of the aircraft corresponding to the target flight, the entry of application X (as an example of the first entry source, the ground service management system) is successful, and the data source here is marked as application X.

[0087] If the preload weight H13 to be entered exceeds the maximum available payload limit of the aircraft corresponding to the target flight, the entry application X fails, and a first prompt message is sent to the on-site support staff, such as "The entered preload exceeds the maximum available payload limit of the aircraft. The aircraft cannot be transported. Please reconfirm the preload."

[0088] For example, when the execution subject is the second terminal device 121, during the process of entering the first data, if the preload weight H13 to be entered is less than the maximum available payload limit of the aircraft corresponding to the target flight, the entry of application Y (as an example of the second entry source, the ground service management system) is successful, and the data source here is marked as application Y.

[0089] If the preload weight H13 to be entered exceeds the maximum available payload limit of the aircraft corresponding to the target flight, the entry application Y fails, and a first prompt message is sent to the on-site support staff, for example, "The entered preload exceeds the maximum available payload limit of the aircraft. The aircraft cannot be transported. Please reconfirm the preload."

[0090] According to some other embodiments of the present disclosure, the target object is a target flight, and the first data includes: the actual load weight for the target flight.

[0091] Wherein, in the case where there is historical input data for the target object, inputting the first data includes:

[0092] A function key for canceling the cut-off is displayed on the front-end display interface; the function key is used to trigger the function of allowing the input of the actual load weight after the cancel cut-off operation is successfully executed;

[0093] Upon receiving a confirmation instruction for the function key, executing a cancel operation, including: setting the historical actual load weight to zero, and associating the result of the actual load weight being zero with the corresponding execution entry source and storing it as a cancel result; synchronizing the cancel result to other entry sources other than the execution entry source; the other entry sources include the historical entry source;

[0094] After receiving the feedback result of successful cancellation of the cut-off result synchronization sent by other input sources, the above-mentioned actual load weight is entered.

[0095] Wherein, in the absence of historical input data for the target object, the first data is input, including: inputting the actual load weight.

[0096] By setting the function key and operation to cancel loading, when initiating a load change, it is necessary to first submit the cancellation, set the original load weight to 0, and then submit the new load weight. This setting helps to avoid the dispatcher using the old load weight for calculation during the release assessment while waiting for confirmation of the load data change, without being aware of the change in the load weight. The cancellation operation helps to ensure that operators of multiple input sources are informed that there are user-required changes to the load data, which serves as a change operation flow identifier.

[0097] According to an embodiment of the present disclosure, the execution entry source is an airport dispatch management system (e.g., application Y) or a ground service management system (e.g., application X), and the actual load weight entry includes:

[0098] Determine whether the actual load weight is less than the maximum available payload limit of the target flight;

[0099] When the actual load weight is less than the maximum available payload limit, the actual load weight is stored in the first database corresponding to the execution entry source;

[0100] When the actual load weight exceeds the maximum available payload limit, a second prompt message of the actual load weight and entry failure is issued.

[0101] If the input source is the terminal dispatch management system, a third prompt message will be issued to remind the flight dispatcher to conduct a release assessment and verification if the actual load is greater than the maximum release weight limit (data updated in real time) and less than the maximum available payload limit. The maximum release weight limit is updated in real time and is generally less than the maximum available payload limit. As an example, the third prompt message is used to remind the dispatcher of the following: The actual load entered exceeds the latest maximum release weight limit. Please confirm whether a new release assessment is required.

[0102] Figure 4 The figure schematically shows a flow chart of a data entry method according to yet another embodiment of the present disclosure.

[0103] In addition to the above steps S210 to S260b, or a combination of steps S210 to S260b and at least one of {S260a, S270 and S280}, S230b, and S250a, the data entry method further includes the following steps: S410. Figure 4 Detailed implementation of step S410 and step S250b is shown in FIG. The above step S410 is performed before step S250b. The above priority configuration information can be adjusted or updated.

[0104] In step S410 , priority configuration information for a plurality of input sources in the input source list is received, where the priority configuration information includes input priorities of the input sources.

[0105] Wherein, in step S250b, the entry priorities of the above historical entry sources and the above execution entry sources are determined, which specifically includes the following steps S2501b: according to the above priority configuration information, the entry priorities of the above historical entry sources and the above execution entry sources are determined.

[0106] Figure 5 The following schematically shows a flow chart of a data entry method according to yet another embodiment of the present disclosure.

[0107] According to an embodiment of the present disclosure, the priority configuration information further includes: a valid period of the entry source.

[0108] Based on the above embodiment, the data entry method includes, in addition to the above steps S210 to S260b and S410, or a combination of steps S210 to S260b and at least one of {S260a, S270 and S280}, S230b, S250a and S410, the following steps: S510, S520 and S530.

[0109] In step S510, the control information of the above-mentioned effective period is received; the above-mentioned control information is used to limit the takeover period of the high-priority second input source to take over the input of the low-priority first input source, and after the takeover is completed, the second input source is controlled to be invalid and the first input source is controlled to be effective.

[0110] In step S520, the entry validation status of each entry source is set according to the above-mentioned control information.

[0111] In step S530, it is determined whether the execution entry source is valid according to the entry validity status.

[0112] In the case that the execution entry source is valid, the following step S240 is performed: determining whether the historical entry source is consistent with the execution entry source of the entry request.

[0113] By regulating the entry effectiveness status of the entry source based on the control information, the entry time periods of the high-priority entry source and the low-priority entry source can be effectively switched. For example, after the high-priority entry source takes over the entry, the low-priority entry source can also enter data after it returns to normal. By setting the entry effectiveness period of the high-priority entry source, if the high-priority entry source becomes invalid at a certain moment (at which moment the low-priority entry source has returned to normal), the low-priority entry source can continue to enter data.

[0114] A second exemplary embodiment of the present disclosure provides a data entry device.

[0115] Figure 6 The figure schematically shows a structural block diagram of a data entry device according to an embodiment of the present disclosure.

[0116] The data entry device 600 provided in the embodiment of the present disclosure is a main body of one of the multiple entry sources, for example, Figure 1 The first terminal device 111 or the second terminal device 121 in the exemplary system architecture 100 .

[0117] Reference Figure 6 As shown, the data entry device 600 provided by the embodiment of the present disclosure includes: a request receiving module 601, a historical data query module 602, an entry source acquisition module 603, an entry source comparison module 604, a priority determination module 605 and an entry control module 606.

[0118] The request receiving module 601 is used to receive an entry request for entering first data for a target object.

[0119] The historical data query module 602 is used to determine whether there is historical input data for the target object.

[0120] The input source acquisition module 603 is used to acquire the historical input source corresponding to the most recent historical input data when there is historical input data for the target object.

[0121] The input source comparison module 604 is used to determine whether the historical input source is consistent with the execution input source of the input request.

[0122] The priority determination module 605 is configured to determine the entry priorities of the historical entry source and the execution entry source when the historical entry source and the execution entry source are inconsistent.

[0123] The entry control module 606 is configured to prohibit entry of the first data when the entry priority indicates that the priority of the historical entry source is higher than the priority of the execution entry source.

[0124] According to an embodiment of the present disclosure, the entry control module 606 is further configured to: enter the first data when the entry priority indicates that the priority of the historical entry source is lower than the priority of the execution entry source.

[0125] The above-mentioned device 600 further includes: a storage module and a data synchronization module.

[0126] The storage module is configured to associate the first data with the corresponding execution entry source and store the associated first data as an entry result when the first data is successfully entered.

[0127] The data synchronization module is used to synchronize the input results to other input sources other than the execution input source; the other input sources include the historical input source.

[0128] According to an embodiment of the present disclosure, the entry control module 606 is further configured to: enter the first data when the historical entry source is consistent with the execution entry source of the entry request.

[0129] According to an embodiment of the present disclosure, the entry control module 606 is further configured to: enter the first data when there is no historical entry data for the target object.

[0130] According to an embodiment of the present disclosure, the above-mentioned apparatus 600 further includes: a priority configuration module.

[0131] The priority configuration module is further configured to receive priority configuration information for a plurality of input sources in the input source list, wherein the priority configuration information includes input priorities of the input sources.

[0132] The step of determining the entry priorities of the historical entry source and the execution entry source includes: determining the entry priorities of the historical entry source and the execution entry source according to the priority configuration information.

[0133] According to an embodiment of the present disclosure, the priority configuration information further includes: a valid period of the entry source.

[0134] The above-mentioned device 600 further includes: a control module and a validity determination module.

[0135] The above-mentioned control module is used to: receive control information on the above-mentioned effective period; the above-mentioned control information is used to limit the takeover period of the high-priority second input source to take over the input of the low-priority first input source, and control the above-mentioned second input source to become invalid after the takeover is completed, and control the above-mentioned first input source to become effective; and is used to: set the input effectiveness status of each input source according to the above-mentioned control information.

[0136] The validity determination module is used to determine whether the execution entry source is valid according to the entry validity status.

[0137] In the case that the execution entry source is valid, the entry source comparison module 604 performs the following operations: determining whether the historical entry source is consistent with the execution entry source of the entry request.

[0138] For more details and beneficial effects of this embodiment, please refer to the detailed introduction of the first embodiment, which will not be repeated here.

[0139] Any number of the functional modules included in the above-mentioned device 600 can be combined into one module for implementation, or any one of the modules can be split into multiple modules. Alternatively, at least part of the functions of one or more of these modules can be combined with at least part of the functions of other modules and implemented in one module. At least one of the functional modules included in the device 600 can be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on a chip, a system on a substrate, a system on a package, an application-specific integrated circuit (ASIC), or can be implemented by hardware or firmware such as any other reasonable way of integrating or packaging the circuit, or implemented in any one of the three implementation methods of software, hardware and firmware or in an appropriate combination of any of them. Alternatively, at least one of the functional modules included in the device 600 can be at least partially implemented as a computer program module, which can perform the corresponding function when the computer program module is executed.

[0140] A third exemplary embodiment of the present disclosure provides an electronic device.

[0141] Figure 7The structural block diagram of the electronic device provided by the embodiment of the present disclosure is schematically shown.

[0142] Reference Figure 7 As shown, the electronic device 700 provided by the embodiment of the present disclosure includes a processor 701, a communication interface 702, a memory 703 and a communication bus 704, wherein the processor 701, the communication interface 702 and the memory 703 communicate with each other through the communication bus 704; the memory 703 is used to store computer programs; the processor 701 is used to implement the data entry method as described above when executing the program stored in the memory.

[0143] A fourth exemplary embodiment of the present disclosure further provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the data entry method described above.

[0144] The computer-readable storage medium may be included in the device or apparatus described in the above embodiments, or may exist independently without being incorporated into the device or apparatus. The computer-readable storage medium carries one or more programs, and when the one or more programs are executed, the method according to the embodiments of the present disclosure is implemented.

[0145] According to an embodiment of the present disclosure, a computer-readable storage medium may be a non-volatile computer-readable storage medium, such as, but not limited to, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

[0146] It should be noted that the collection, collection, updating, analysis, processing, use, transmission, and storage of user personal information involved in the technical solutions provided by the embodiments of this disclosure all comply with the provisions of relevant laws and regulations, are used for legitimate purposes, and do not violate public order and good morals. Necessary measures are taken with respect to user personal information to prevent unauthorized access to user personal information data and to maintain the security of user personal information, network security, and national security.

[0147] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the terms "comprises," "comprising," or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article, or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or device. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of other identical elements in the process, method, article, or device comprising the element.

[0148] The foregoing description is intended only to provide specific embodiments of the present disclosure, intended to enable those skilled in the art to understand and implement the present disclosure. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present disclosure. Therefore, the present disclosure is not to be limited to the embodiments shown herein, but is to be construed in the broadest manner consistent with the principles and novel features claimed herein.

Claims

1. A method for data entry, characterized in that: Applied to one of multiple input sources, the method includes: receiving an entry request for entering first data for a target object; Determining whether there is historical entry data for the target object; If there is historical entry data for the target object, obtaining the historical entry source corresponding to the most recent historical entry data; Determining whether the historical entry source is consistent with the execution entry source of the entry request; In the case that the historical entry source and the execution entry source are inconsistent, determining the entry priority of the historical entry source and the execution entry source; In a case where the entry priority indicates that the priority of the historical entry source is higher than the priority of the execution entry source, entry of the first data is prohibited.

2. The method according to claim 1, characterized in that Also includes: When the input priority indicates that the priority of the historical input source is lower than the priority of the execution input source, inputting the first data; If the first data is successfully entered, the first data is associated with the corresponding execution entry source and stored as an entry result; Synchronizing the input result to other input sources other than the input execution source; The other entry sources include the historical entry sources.

3. The method according to claim 1, characterized in that Also includes: When the historical entry source is consistent with the execution entry source of the entry request, entering the first data; In the case that there is no historical entry data for the target object, the first data is entered.

4. The method according to claim 2 or 3, characterized in that The target object includes a target flight, and the first data includes: a preload weight for the target flight; The step of inputting the first data includes: determining whether the preload weight is less than the maximum available payload limit of the target flight; When the preload weight is less than the maximum available payload limit, storing the preload weight in a first database corresponding to the execution entry source; In the case where the preload weight exceeds the maximum available payload limit, a first prompt message of preload excess and entry failure is issued.

5. The method according to claim 2 or 3, characterized in that The target object is a target flight, and the first data includes: an actual load weight for the target flight; Wherein, in the case where there is historical input data for the target object, inputting the first data includes: A function key for canceling the cut-off is displayed on the front display interface; the function key is used to trigger the function of allowing the input of the actual load weight after the cancel cut-off operation is successfully executed; Upon receiving a confirmation instruction for the function key, executing a cancel operation, including: setting the historical actual load weight to zero, and associating the result of the actual load weight being zero with the corresponding execution entry source and storing it as a cancel result; synchronizing the cancel result to other entry sources other than the execution entry source; the other entry sources include the historical entry source; After receiving the feedback result of successful cancellation of the cut-off result synchronization sent by other input sources, the actual load weight is input; Wherein, in the case that there is no historical input data for the target object, entering the first data includes: entering the actual load weight.

6. The method according to claim 5, characterized in that Entering the actual load weight includes: Determining whether the actual load weight is less than the maximum available payload limit of the target flight; When the actual load weight is less than the maximum available payload limit, storing the actual load weight in the first database corresponding to the execution entry source; When the actual load weight exceeds the maximum available payload limit, a second prompt message of the actual load weight and entry failure is issued.

7. The method according to claim 6, characterized in that The execution entry source is the terminal scheduling management system or the ground service management system; In case the execution entry source is the terminal scheduling management system, when the actual load weight is greater than the maximum release weight limit and less than the maximum available payload limit, a third prompt message is also issued to remind the flight dispatcher to conduct a release assessment and verification.

8. The method according to claim 1, characterized in that Also includes: Receiving priority configuration information for a plurality of input sources in the input source list, the priority configuration information comprising: input priorities of the input sources; Determining the input priority of the historical input source and the execution input source includes: The entry priorities of the historical entry source and the execution entry source are determined according to the priority configuration information.

9. The method according to claim 8, characterized in that The priority configuration information also includes: the effective period of the input source; The method further comprises: receiving control information for the effective period; the control information is used to limit the takeover period of the second input source with a higher priority to take over the input of the first input source with a lower priority, and control the second input source to be invalid after the takeover is completed, and control the first input source to be effective; According to the control information, set the entry validity status of each entry source; Determining whether the execution entry source is valid according to the entry validity status; In the case that the execution entry source is valid, the following operations are performed: determining whether the historical entry source is consistent with the execution entry source of the entry request.

10. A data entry device, characterized in that: The device is a main body of one of the multiple input sources, and the device includes: A request receiving module, configured to receive an entry request for entering first data for a target object; A historical data query module is used to determine whether there is historical input data for the target object; An input source acquisition module is used to acquire the historical input source corresponding to the most recent historical input data when there is historical input data for the target object; An input source comparison module, configured to determine whether the historical input source is consistent with the execution input source of the input request; a priority determination module, configured to determine the entry priorities of the historical entry source and the execution entry source when the historical entry source and the execution entry source are inconsistent; An entry control module is configured to prohibit entry of the first data when the entry priority indicates that the priority of the historical entry source is higher than the priority of the execution entry source.

11. An electronic device, characterized in that: The processor, the communication interface, the memory and the communication bus are connected to each other via the communication bus. Memory for storing computer programs; A processor, configured to implement the method according to any one of claims 1 to 9 when executing a program stored in a memory.

12. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 1 to 9 is implemented.

Images