CN113011839A

CN113011839A - Flight guarantee task triggering method and related equipment

Info

Publication number: CN113011839A
Application number: CN202110261180.9A
Authority: CN
Inventors: 苗艳丽; 马晓兵; 何喆; 戴立华; 杜冰; 田思齐
Original assignee: China Travelsky Holding Co
Current assignee: China Travelsky Technology Co Ltd; China Travelsky Holding Co
Priority date: 2021-03-10
Filing date: 2021-03-10
Publication date: 2021-06-22

Abstract

The application provides a flight support task triggering method and related equipment, which can reduce the difficulty of later modification and maintenance of a system and increase the flexibility and stability of the system. The method comprises the following steps: determining a target event splitting and selecting type; splitting the events in the flight service flow according to the splitting and type selection of the target events to obtain an event set; combing N guarantee tasks of each event in the event set; splitting the target guarantee task to obtain attribute information of each subtask in the target guarantee task, wherein the target guarantee task is any one of N guarantee tasks; configuring a business rule of each subtask in the target guarantee task according to the attribute information of each subtask in the target guarantee task; and performing task triggering on the current flight according to the business rule.

Description

Flight guarantee task triggering method and related equipment

Technical Field

The application relates to the field of aviation, in particular to a flight guarantee task triggering method and related equipment.

Background

The development of the civil aviation industry in China is normalized, the service scale is continuously increased, and the future service scale can be expected to be continuously increased. The airport continuously releases more time resources, the flight connection is more compact, and the service guarantee mode and the flow are necessarily adjusted.

In a traditional enterprise-level project development mode, business decision logic or business rules are often hard-coded by programmers and embedded in codes of all parts of a system, and after the system is developed, the business rules are completely fixed in the codes. But airlines are also being served with a variety of services to accommodate the variety of markets and the personalized needs of passengers. The changing business rules and business processes inevitably cause frequent modification to the application program, and the business rules are constantly changed along with the change of business requirements and need to be reflected in relevant information in real time. Once the service requirement changes, developers need to modify and update system codes to change service logic to respond to the change requirement of the service rule, and need to go through links such as requirement analysis, design, coding, testing and release, which brings great difficulty and challenge to later modification and maintenance, the system maintenance task is heavy and expensive, and not only greatly limits the flexibility of the system, but also affects the stability of the system.

Disclosure of Invention

The application provides a flight support task triggering method and related equipment, which reduce the difficulty of later modification and maintenance of a system and increase the flexibility and stability of the system.

A first aspect of the embodiments of the present application provides a method for triggering a flight assurance task, including:

determining a target event splitting and selecting type;

splitting the events in the flight service flow according to the target event splitting and selecting type to obtain an event set;

combing N guarantee tasks of each event in the event set, wherein N is a positive integer greater than or equal to 1;

splitting a target guarantee task to obtain attribute information of each subtask in the target guarantee task, wherein the target guarantee task is any one of the N guarantee tasks;

configuring a business rule of each subtask in the target guarantee task according to attribute information of each subtask in the target guarantee task, wherein the business rule comprises a trigger condition, a responsibility department, an execution flow and an early warning rule, and the business rule is contained in a rule engine library which contains a plurality of business rules configured in advance;

and performing task triggering on the current flight according to the service rule.

A second aspect of the embodiments of the present application provides a device for triggering a flight assurance task, including:

the determining unit is used for determining splitting and type selection of the target event;

the event splitting unit is used for splitting the events in the flight service flow according to the target event splitting model selection to obtain an event set;

the combing unit is used for combing N guarantee tasks of each event in the event set, wherein N is a positive integer greater than or equal to 1;

the task splitting unit is used for splitting a target guarantee task to obtain attribute information of each subtask in the target guarantee task, wherein the target guarantee task is any one of the N guarantee tasks;

the configuration unit is used for configuring a business rule of each subtask in the target guarantee task according to the attribute information of each subtask in the target guarantee task, wherein the business rule comprises a trigger condition, a responsibility department, an execution flow and an early warning rule, the business rule is contained in a rule engine library, and the rule engine library comprises a plurality of business rules configured in advance;

and the triggering unit is used for triggering the task of the current flight according to the service rule.

A third aspect of the embodiments of the present application provides a computer device, which includes at least one connected processor and a memory, where the memory is used to store a program code, and the program code is loaded and executed by the processor to implement the steps of the method for triggering a flight assurance task according to the first aspect.

A fourth aspect of the embodiments of the present application provides a machine-readable medium, which includes instructions that, when executed on a machine, cause the machine to perform the steps of the method for triggering a flight assurance task according to the first aspect.

In summary, it can be seen that, in the embodiments provided in the present application, a rule engine is introduced to strip service rules from complex system codes, a predefined semantic module is used to write service decisions, the complex rules are resident in a rule base, each support task of an event in a flight service flow is finely split in advance to obtain each subtask of each support task, and a service rule is configured for each subtask according to the service rule in the rule engine base configured in advance, so that when the service flow of a current flight is executed, the support task of the current flight is task-triggered by the service rule configured for each subtask to ensure smooth execution of the flight support task, and since the service rule in the rule engine base is configured in advance, when the service requirement changes, only the corresponding service rule needs to be changed, the difficulty of later modification and maintenance is reduced, and the flexibility and the stability of the system are improved.

Drawings

The above and other features, advantages and aspects of various embodiments of the present application will become more apparent from the following detailed description when taken in conjunction with the accompanying drawings. Throughout the drawings, the same or similar reference numbers refer to the same or similar elements. It should be understood that the drawings are schematic and that elements and features are not necessarily drawn to scale.

Fig. 1 is a schematic flowchart of a method for triggering a flight assurance task according to an embodiment of the present application;

fig. 2 is a schematic view of a virtual structure of a triggering device for a flight assurance task according to an embodiment of the present application;

FIG. 3 is a schematic structural diagram of a machine-readable medium provided by an embodiment of the present application;

fig. 4 is a schematic hardware structure diagram of a server according to an embodiment of the present application.

Detailed Description

Embodiments of the present application will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present application are shown in the drawings, it should be understood that the present application may be embodied in various forms and should not be construed as limited to the embodiments set forth herein, but rather are provided for a more thorough and complete understanding of the present application. It should be understood that the drawings and embodiments of the present application are for illustration purposes only and are not intended to limit the scope of the present application.

The terms "include" and variations thereof as used herein are inclusive and open-ended, i.e., "including but not limited to. The term "based on" is "based, at least in part, on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Relevant definitions for other terms will be given in the following description.

It should be noted that the terms "first", "second", and the like in the present application are only used for distinguishing different devices, modules or units, and are not used for limiting the order or interdependence relationship of the functions performed by the devices, modules or units.

It is noted that references to "a", "an", and "the" modifications in this application are intended to be illustrative rather than limiting, and that those skilled in the art will recognize that reference to "one or more" unless the context clearly dictates otherwise.

The method for triggering the flight assurance task provided by the present application is described below from the perspective of a device for triggering the flight assurance task, where the device for triggering the flight assurance task may be a server, or a service unit in the server, and is not particularly limited.

Referring to fig. 1, fig. 1 is a schematic flowchart of a method for triggering a flight assurance task according to an embodiment of the present application, including:

101. and determining the splitting and typing of the target event.

In this embodiment, the trigger device of the flight assurance task may determine the splitting and type selection of the target event, and when the trigger device of the flight assurance task splits the event, there are two dimensional splitting modes, one is splitting based on a service scenario trigger action, and the other is splitting based on a service model attribute change. The split modes of two dimensions have certain advantages and disadvantages, the trigger device of the flight guarantee task preferentially selects the mode of triggering action split based on the service scene based on the advantage and disadvantage analysis of the two split modes and assists in setting message classification so as to ensure that the consumer module can subscribe large messages. Of course, in the actual application process, different event splitting modes may also be selected according to the actual application scenario, and are not limited specifically.

That is to say, the trigger device of the flight support task may first define the relevant service scenario standard trigger action and all the services for calling the system to perform the service operation, assemble the service event meeting the service scenario requirement according to the standard definition event, and the corresponding module processing logic is relatively fixed; when a certain task is triggered, a task message is generated and sent to a task subscriber, the task message carries a trigger service mark (the service mark indicates that the task event is specifically triggered by the system), and effective support can be provided for personalized processing.

It should be noted that, in the whole service event, the service models such as flights and tasks are simultaneously stored, and sufficient attribute change information (change of model attribute information, such as the lead-in time and the lead-in time of a flight) is provided for the service models such as flights and tasks to perform response processing, where the response processing refers to mainly providing change information of the service model attributes, and providing the change information to a module that needs to pay attention to the information, such as change of the lead-in time of a flight, and when the flight monitoring module obtains the change time, it needs to determine whether the flight is a stop flight, whether the stop time is sufficient, whether a fast stop-passing process needs to be started, whether a transit traveler needs to arrange a subsequent task in advance, and the like.

102. And splitting the events in the flight service flow according to the splitting and type selection of the target events to obtain an event set.

In this embodiment, after determining the target event splitting and type selection, the triggering device of the flight assurance task may split the event in the flight service flow according to the target event splitting and type selection to obtain an event set, that is, the triggering device of the flight assurance task may split the event in the entire flight service flow based on the mode in which the service scene triggers the action splitting, that is, split the flight service flow into a plurality of events to obtain the event set.

103. And combing N guarantee tasks of each event in the event set.

In this embodiment, the triggering device for the flight assurance task may comb N assurance tasks of each event in the event set, where N is a positive integer greater than or equal to 1. In the actual production operation of an airline company, some guarantee tasks which occur frequently exist, although the business processes of different airline guarantee tasks are different, the basic business processing processes, the management requirements and the like of the guarantee tasks are approximately similar, and the trigger device of the flight guarantee task can comb the guarantee tasks involved in the production operation process, including specific business flows, and the related trigger conditions, trigger time and the like are solidified in a flow form, so that the system is favorable for establishing a clearer and more complete processing flow.

104. And splitting the target guarantee task to obtain the attribute information of each subtask in the target guarantee task.

In this embodiment, the trigger device of the flight assurance task may split the target assurance task to obtain attribute information of each subtask in the target assurance task, where the target assurance task is any one of the N assurance tasks. Specifically, the triggering device for the flight assurance task may first determine a business processing flow of the target assurance task, split the target assurance task according to the business processing flow, and determine attribute information of each subtask in the target assurance task. That is to say, the flight guarantee task relates to multi-position, multi-department and multi-system in the actual production guarantee, and the guarantee task has the characteristics of uncertainty, high frequency and the like. Once the trigger needs to respond timely and accurately, the guarantee tasks need to have complete business processing specifications, then the guarantee tasks are finely split according to specific business processing flows of all the guarantee tasks by an airline company, and information such as responsibility departments, responsibility posts and the like of each subtask in all the guarantee tasks is determined, so that the guarantee tasks can be completed timely and efficiently. The following description is made by splitting the guarantee task of the boarding gate baggage deduction service scene:

1. the departure system performs a boarding gate pull-down operation;

2. the ground flight support platform receives DCSI gate passenger reducing messages;

3. the ground flight support platform analyzes the message and judges whether the passenger has consigned baggage or not;

4. the passenger has consigned luggage, and the luggage position is judged according to BHS/BRS and GIS data;

5. and generating a 'baggage turning task', and sending the guarantee task to a baggage sorting personnel or a baggage handling personnel.

105. And configuring the business rule of each subtask in the target guarantee task according to the attribute information of each subtask in the target guarantee task.

In this embodiment, the triggering device of the flight assurance task may configure the business rule of each subtask in the target assurance task according to the attribute information of each subtask in the target assurance task, where the business rule includes information such as a triggering condition of the task, a responsibility department of the task, and a responsibility post of the task. The trigger device of the flight support task may set a flight support task business rule according to attribute information of each subtask in the flight support task, where the flight support task business rule includes information of a trigger condition of the task, a responsibility department of the task, a responsibility post of the task, and the like, and may also include other information, such as a sending department of the task, a processing flow specification of the task, an early warning rule of the task, and the like, and is not limited specifically. The trigger device of the flight guarantee task can add the trigger rule to the rule engine library in advance, so that the business rule corresponding to the task can be simply and quickly searched in the actual production and use process, the business operation is completed, and the operation pressure of a user at the production peak is reduced.

It should be noted that the triggering device for the flight assurance task may pre-configure the triggering rule of each assurance task, and add the triggering rule of the assurance task to the rule engine library, which is specifically as follows:

1, the trigger device of the flight support task triggers related service events (related service events refer to flight plans (new, associated VIP, update, and the like), flight dynamics, flight information change, scheduling information (arrival, check-in, boarding, take-off, and the like), flight time adjustment, dispatch events, and message events (announcement, early warning) according to a flight service flow main line, it can be understood that, in the flight operation process, when an event trigger condition is reached, corresponding events are triggered, for example, a newly-added flight plan event is triggered after the flight plan is made up, a related module (the related module refers to a module concerned about a specific service event, for example, a flight monitoring module pays attention to the flight dynamics, and then subscribes to the flight dynamics events), and performs corresponding response processing, for example, a boarding gate passenger reducing baggage event: and generating a task of reducing passengers and turning over the luggage, distributing the task to the luggage loading and unloading personnel, turning over the luggage by the luggage loading and unloading personnel (in place, starting to turn over and ending), and loading to confirm whether the manifest is reworked or not.

2. In order to adapt to the variability of markets and the personalized requirements of passengers, business rules (such as rules of passenger service standards, flight assurance standards and the like) and business processes of the airlines are frequently modified, the business rules are continuously changed along with the change of the business requirements, according to the design of a system architecture, a rule engine is introduced to strip the business rules (including task triggering conditions, triggering departments, receiving departments, execution processes and early warning rules) from system codes, the business rules are independently configured and maintained, the continuously changed business requirements of the airlines are met, and when the business requirements change, only the corresponding business rules need to be changed.

3. After the rule engine is introduced, complicated business rules are split from the business logic components, and at the moment, a general business logic component and a personalized business logic component which meet business processes are built only on the basis of airline guarantee tasks and are matched with the business rule engine to complete business process processing.

4. The constructed business logic component can be directly called at a client to provide services externally, and can be automatically or manually called by production personnel to complete the production operation guarantee task of an airline company.

106. And performing task triggering on the current flight according to the business rule.

In this embodiment, after the flight assurance task triggering device completes the service rule, the task triggering may be performed on the current flight according to the service rule.

It should be noted that the task triggering modes include two modes, one mode is manual triggering, the other mode is system automatic triggering, the flight guarantee task triggering device can display the task triggering mode when the guarantee task execution flow of the current flight starts, and select the target task triggering mode according to the second operation instruction of the user, the target task triggering mode is any one of the task triggering modes, and the task triggering is performed on the current flight based on the target task triggering mode.

In one embodiment, the task triggering of the current flight according to the service rule by the flight support task triggering device includes:

judging whether the first task is successfully triggered or not based on the triggering condition, wherein the first task is a task currently executed in the current flight;

if yes, determining a responsibility department, an execution flow and an early warning rule of the first task according to a business rule corresponding to the first task;

and sending the execution flow and the early warning rule of the first task to a responsibility department of the first task.

In this embodiment, the triggering device of the flight assurance task may first determine whether the first task is successfully triggered according to the triggering condition, and if the first task is successfully triggered, determine the responsibility department, the execution flow and the early warning rule of the first task according to the business rule of the first task, and send the execution flow and the early warning rule of the first task to the responsibility department of the first task, so that the first task is quickly executed.

It should be noted that, in the process of executing the flight support task, when the user wants to check the execution progress of the task, the user may send instruction information, and the trigger device of the flight support task may send task feedback information to the responsibility department of the first task according to the instruction information of the user, and receive and display the progress information of the first task returned by the responsibility department of the first task.

It should be further noted that, in the process of executing the flight support task, the trigger device of the flight support task receives a first operation instruction of the user, where the first operation instruction is an operation of canceling a second task, and the second task is a task in the current flight;

judging whether the user has the authority or not according to the service rule of the second task;

if yes, canceling the second task and sending cancellation information to a responsibility department of the second task;

if not, displaying prompt information, wherein the prompt information indicates that the user does not have the authority to cancel the second task.

That is to say, when receiving a cancel operation instruction for a task, the trigger device for the flight support task can judge whether the user has the authority to cancel according to the business rule of the task, and if the user has the authority to cancel, the trigger device sends cancel information to a related responsibility department, and if the user does not have the authority to cancel, the trigger device sends out prompt information to indicate that the user does not have the authority to cancel the task.

In one embodiment, the operation generated as the first operation instruction at least includes one of a gesture operation, a sliding operation, a clicking operation and a voice control operation, for example, when a user performs a clicking operation on an interface displaying the second task, the triggering device of the flight assurance task may receive the clicking operation, and at this time, the clicking operation generates the first operation instruction, that is, an operation instruction may be defined in advance, for example, a sliding operation may be defined in advance as an operation of canceling the second task (e.g., a left-sliding operation, a right-sliding operation, a top-sliding operation, a bottom-sliding operation, and the like), or a clicking operation may be defined as an operation of canceling the second task (e.g., a double-clicking operation, a mouse-sliding operation, a long-pressing operation, a clicking operation, a simultaneous pressing operation of left and right mouse keys, a middle mouse key of a scroll wheel mouse, and the like), or a gesture operation may be defined, for example, the above is merely an example and does not represent a limitation on the operation for generating the first operation instruction, and the above is only an example. Of course, the first operation instruction may also be generated by setting a corresponding shortcut key on an input device, for example, the input device is a keyboard, and the operation of canceling the second task is performed by setting a "CTRL + a key" on the keyboard, which is not limited specifically.

It is to be understood that the flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The names of messages or information exchanged between a plurality of devices in the embodiments of the present application are for illustrative purposes only, and are not intended to limit the scope of the messages or information.

Although the operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order. Under certain circumstances, multitasking and parallel processing may be advantageous.

It should be understood that the various steps recited in the method embodiments of the present application may be performed in a different order and/or in parallel. Moreover, method embodiments may include additional steps and/or omit performing the illustrated steps. The scope of the present application is not limited in this respect.

Additionally, the present application may also be written with computer program code for performing the operations of the present application in one or more programming languages, including, but not limited to, an object oriented programming language such as Java, Smalltalk, C + +, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).

The present application is described above from the viewpoint of the method for triggering a flight support mission, and the present application is described below from the viewpoint of the device for triggering a flight support mission.

Referring to fig. 2, fig. 2 is a schematic view of a virtual structure of a flight assurance task triggering device according to an embodiment of the present application, where the flight assurance task triggering device 200 includes:

a determining unit 201, configured to determine a target event splitting and typing;

an event splitting unit 202, configured to split an event in a flight service flow according to the target event splitting model selection, so as to obtain an event set;

a combing unit 203, configured to comb N security tasks of each event in the event set, where N is a positive integer greater than or equal to 1;

a task splitting unit 204, configured to split a target guarantee task to obtain attribute information of each subtask in the target guarantee task, where the target guarantee task is any one of the N guarantee tasks;

the configuration unit 205 is configured to configure a business rule of each subtask in the target support task according to attribute information of each subtask in the target support task, where the business rule includes a trigger condition, a responsibility department, an execution flow, and an early warning rule, and the business rule is included in a rule engine library, and the rule engine library includes a plurality of business rules configured in advance;

and the triggering unit 206 is configured to perform task triggering on the current flight according to the service rule.

In a possible implementation manner, the triggering unit 206 is specifically configured to:

judging whether a first task is triggered successfully or not based on the triggering condition, wherein the first task is a task currently executed in the current flight;

In a possible implementation manner, the apparatus further includes:

a transceiver unit 207, wherein the transceiver unit 207 is configured to:

sending task feedback information to a responsibility department of the first task;

and receiving and displaying the progress information of the first task returned by the responsibility department of the first task.

In a possible implementation manner, the task splitting unit 204 is specifically configured to:

determining a business processing flow of the target guarantee task;

and splitting the target guarantee task according to the business processing flow, and determining the attribute information of each subtask in the target guarantee task.

In a possible implementation manner, the transceiver 207 is further configured to receive a first operation instruction of a user, where the first operation instruction is an operation of canceling a second task, and the second task is a task in the current flight;

the determining unit 201 is further configured to:

In a possible implementation manner, the triggering unit 206 is further specifically configured to:

when the guarantee task execution process of the current flight starts, displaying a task trigger mode;

selecting a target task trigger mode according to a second operation instruction of a user, wherein the target task trigger mode is any one task trigger mode in the task trigger modes;

and performing task triggering on the current flight based on the target task triggering mode.

In summary, it can be seen that, in the embodiments provided in the present application, a rule engine is introduced to strip service rules from complex system codes, a predefined semantic module is used to write service decisions, the complex rules are resident in a rule base, each support task of an event in a flight service flow is finely split in advance to obtain each subtask of each support task, and a service rule is configured for each subtask according to the service rule in the rule engine base configured in advance, so that when the service flow of a current flight is executed, the support task of the current flight is task-triggered by the service rule configured for each subtask to ensure smooth execution of the flight support task, and since the service rule in the rule engine base is configured in advance, when the service requirement changes, only the corresponding service rule needs to be changed, the difficulty of later modification and maintenance of the system is reduced, and the flexibility and the stability of the system are improved.

It should be noted that the units described in the embodiments of the present application may be implemented by software, and may also be implemented by hardware. Here, the name of the unit does not constitute a limitation of the unit itself in some cases, and for example, the acquisition unit may also be described as "a unit that acquires credential information of a target user".

The functions described herein above may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), systems on a chip (SOCs), Complex Programmable Logic Devices (CPLDs), and the like.

Referring to fig. 3, fig. 3 is a schematic diagram of an embodiment of a machine-readable medium according to the present application.

As shown in fig. 3, the present embodiment provides a machine-readable medium 300, on which a computer program 311 is stored, and when the computer program 311 is executed by a processor, the steps of the method for triggering the flight assurance task described in fig. 1 are implemented.

In the context of this application, a machine-readable medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

It should be noted that the machine-readable medium described above in this application may be a computer-readable signal medium or a computer-readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present application, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In this application, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, optical cables, RF (radio frequency), etc., or any suitable combination of the foregoing.

The computer readable medium may be embodied in the electronic device; or may exist separately without being assembled into the electronic device.

Referring to fig. 4, fig. 4 is a schematic diagram of a hardware structure of a server according to an embodiment of the present disclosure, where the server 400 may have a relatively large difference due to different configurations or performances, and may include one or more Central Processing Units (CPUs) 422 (e.g., one or more processors) and a memory 432, and one or more storage media 430 (e.g., one or more mass storage devices) storing an application 440 or data 444. Wherein the memory 432 and storage medium 430 may be transient or persistent storage. The program stored on the storage medium 430 may include one or more modules (not shown), each of which may include a series of instruction operations for the server. Still further, the central processor 422 may be arranged to communicate with the storage medium 430, and execute a series of instruction operations in the storage medium 430 on the server 400.

The server 400 may also include one or more power supplies 426, one or more wired or wireless network interfaces 450, one or more input-output interfaces 458, and/or one or more operating systems 441, such as Windows Server, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, and so forth.

The steps performed by the triggering device of the flight assurance task in the above embodiment may be based on the server structure shown in fig. 4.

It should be further noted that, according to an embodiment of the present application, the process of the flight assurance task triggering method described in the flowchart in fig. 1 above may be implemented as a computer software program. For example, embodiments of the present application include a computer program product comprising a computer program carried on a non-transitory computer readable medium, the computer program containing program code for performing the method illustrated in the flow chart diagram of fig. 2 described above.

Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

While several specific implementation details are included in the above discussion, these should not be construed as limitations on the scope of the application. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.

The above description is only a preferred embodiment of the application and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the disclosure herein is not limited to the particular combination of features described above, but also encompasses other arrangements formed by any combination of the above features or their equivalents without departing from the spirit of the disclosure. For example, the above features may be replaced with (but not limited to) features having similar functions disclosed in the present application.

Claims

1. A method for triggering a flight assurance task is characterized by comprising the following steps:

determining a target event splitting and selecting type;

configuring a business rule of each subtask in the target support task according to attribute information of each subtask in the target support task, wherein the business rule comprises a trigger condition, a responsibility department, an execution flow and an early warning rule, and the business rule is contained in a rule engine library which contains a plurality of business rules configured in advance;

2. The method of claim 1, wherein the tasking the current flight according to the business rules comprises:

3. The method of claim 2, further comprising:

4. The method of claim 1, wherein the task splitting of the target assurance task to obtain the attribute information of each subtask in the target assurance task comprises:

determining a business processing flow of the target guarantee task;

5. The method according to any one of claims 1 to 4, further comprising:

receiving a first operation instruction of a user, wherein the first operation instruction is an operation of canceling a second task, and the second task is a task in the current flight;

6. The method of any of claims 1 to 4, wherein the task triggering a current flight according to the business rules comprises:

7. A flight assurance task triggering device, comprising:

the configuration unit is used for configuring a business rule of each subtask in the target support task according to the attribute information of each subtask in the target support task, wherein the business rule comprises a trigger condition, a responsibility department, an execution flow and an early warning rule, the business rule is contained in a rule engine library, and the rule engine library comprises a plurality of business rules configured in advance;

8. The apparatus according to claim 7, wherein the triggering unit is specifically configured to:

9. The apparatus of claim 8, further comprising:

a transceiver unit configured to:

10. A machine-readable medium, comprising instructions which, when run on a machine, cause the machine to perform the steps of the method of triggering a flight assurance task of any of claims 1 to 6 above.