Data processing method and device

Abstract

The invention discloses a data processing method and device, and relates to the technical field of computers. A specific embodiment of the method comprises the following steps: acquiring service information; extracting a plurality of business state change events from the business information, and analyzing to obtain a business state before change, a business state after change, a change condition and an execution action which are respectively included in each business state change event so as to correspondingly record the business states, the business states, the change conditions and the execution actions to a preset state machine file; respectively creating corresponding logic interfaces for each business state, each change condition and each execution action in the state machine file; and analyzing the state machine file by using a preset mapping tool to obtain a state machine attribute definition object, and converting the state machine attribute definition object into a corresponding state machine software package by using a preset byte code tool. Therefore, the embodiment of the invention can solve the technical problems of high complexity and low efficiency of the existing service state updating processing.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a data processing method and device. Background Art

[0002] At present, the update process of business systems is very common, providing enterprise users with a synchronous update solution for massive business data, making it easier for enterprise users to manage their business.

[0003] In the process of implementing the present invention, the inventors found that there are at least the following problems in the prior art:

[0004] When users enjoy the unified business scenario update function, the problem of low efficiency in processing business status changes is common. This is because the existing technology lacks an orderly combing of the entire process of all business status change events, and also lacks a historical record of the corresponding business change trajectory. Therefore, for any abnormal events that occur during the change process, it is necessary to check the interfaces one by one or the scripts line by line, which seriously affects the processing efficiency. In addition, the existing technology generally adopts a hard-coded method to write business data, which leads to high complexity of the corresponding business scripts and poor scalability of the business system. Summary of the invention

[0005] In view of this, an embodiment of the present invention provides a data processing method and device, which can solve the technical problems of high complexity and low efficiency in existing business status update processing.

[0006] To achieve the above-mentioned purpose, according to one aspect of an embodiment of the present invention, a data processing method is provided, comprising acquiring business information; extracting multiple business status change events from the business information, and parsing to obtain the business status before the change, the business status after the change, the change condition and the execution action respectively included in each business status change event, so as to record them in a preset state machine file; creating corresponding logical interfaces for each business status, each change condition and each execution action in the state machine file; parsing the state machine file using a preset mapping tool to obtain a state machine attribute definition object, and converting the state machine attribute definition object into a corresponding state machine software package using a preset bytecode tool.

[0007] Optionally, the business state before the change, the business state after the change, the change condition and the execution action respectively included in each business state change event obtained by parsing include:

[0008] Determine the business status before the change is triggered by the change condition;

[0009] And determine that the execution action is triggered by the changed business status.

[0010] Optionally, after parsing each business status change event to obtain the business status before the change, the business status after the change, the change condition, and the execution action, the following is included:

[0011] Analyze each change condition to determine the business events included in each change condition;

[0012] For each change condition:

[0013] Determine whether only one business event is included;

[0014] If so, determining that the changed service state corresponding to the change condition is a simple service state;

[0015] If not, determining that the changed service state corresponding to the change condition is a composite service state;

[0016] To determine the attributes of each business state.

[0017] Optionally, after determining the attributes of each service state, the following steps are included:

[0018] Extract multiple business states from business information;

[0019] Filtering multiple business states to obtain an initial business state and a final business state, and marking them respectively;

[0020] Determine the attributes and logical interfaces corresponding to each business state;

[0021] to generate a collection of state information in a state machine file.

[0022] Optionally, before using a preset mapping tool to parse the state machine file, the following steps are included:

[0023] For each business state change event in the state machine file: insert a preset recorder into the changed business state to record the corresponding business state change event;

[0024] And create the logical interface for each logger in the state machine file.

[0025] Optionally, after determining the business events included in each change condition, the following steps are performed:

[0026] For each business event in the state machine file: generate a corresponding verification tool to determine whether the corresponding business event is completed, if not, keep it, if yes, mark the corresponding business event;

[0027] And create a logical interface for each verification tool in the state machine file.

[0028] Optionally, after generating the corresponding verification tool, it includes:

[0029] The changed business state is a composite business state as a screening condition, so as to screen out the target business state change event from all state change events;

[0030] For each target business state change event in the state machine file: insert a preset timer task in the business state before the change to regularly determine whether multiple business events included in the corresponding change conditions are all marked. If not, keep it, if yes, change the business state;

[0031] And create a logical interface for each scheduled task in the state machine file.

[0032] Optionally, after creating the logical interface for each validation tool in the state machine file, include:

[0033] Determine the logical interface, the verification tool and the logical interface of the verification tool corresponding to each business event;

[0034] To generate a collection of event information in the state machine file.

[0035] Optionally, after converting the state machine attribute definition object into a corresponding state machine package, include:

[0036] Using an extensible style sheet transfer language process to convert the format of the state machine file to obtain a corresponding document template file, so as to visualize the document template file in a graphic visualization software to generate a corresponding state machine flow chart;

[0037] The state machine software package is associated with the state machine flow chart.

[0038] In addition, the present invention also provides a data processing device, including an acquisition module for acquiring business information; a parsing module for extracting multiple business status change events from the business information, and parsing each business status change event to obtain the business status before the change, the business status after the change, the change condition and the execution action, so as to record them in a preset state machine file; an interface module for creating a corresponding logical interface for each business status, each change condition and each execution action in the state machine file; a processing module for parsing the state machine file using a preset mapping tool to obtain a state machine attribute definition object, and using a preset bytecode tool to convert the state machine attribute definition object into a corresponding state machine software package.

[0039] An embodiment of the above invention has the following advantages or beneficial effects: the present invention realizes the process of obtaining the data source for generating a state machine software package by acquiring business information; and the present invention automatically parses the business information by extracting multiple business state change events from the business information, and parses each business state change event to obtain the business state before the change, the business state after the change, the change condition and the execution action, so as to record the business information in a preset state machine file accordingly, thereby achieving the business purpose of clarifying the overall process of the business state change, and obtaining the orderly business processing logic and recording it in the state machine file; at the same time, the present invention creates a corresponding logical interface for each business state, each change condition and each execution action in the state machine file, thereby achieving the technical purpose of separating the business logic description and the business processing implementation, and reserves a corresponding expansion slot for each business event, thereby maximizing the business scenarios applicable to the present invention; in addition, the present invention parses the state machine file by using a preset mapping tool to obtain a state machine attribute definition object, and uses a preset bytecode tool to convert the state machine attribute definition object into a corresponding state machine software package, thereby simply and quickly generating the corresponding state machine software package, thereby saving the human cost and computing resources of the present invention in generating the state machine software package.

[0040] The further effects of the above-mentioned non-conventional optional manner will be described below in conjunction with the specific implementation manner. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] The accompanying drawings are used to better understand the present invention and do not constitute an improper limitation of the present invention.

[0042] Figure 1 is a schematic diagram of the main flow of the data processing method according to the first embodiment of the present invention;

[0043] Figure 2 is a schematic diagram of the main flow of a data processing method according to a second embodiment of the present invention;

[0044] Figure 3 is a schematic diagram of the main flow of a data processing method according to a third embodiment of the present invention;

[0045] Figure 4 is a schematic diagram of main modules of a data processing device according to an embodiment of the present invention;

[0046] Figure 5 is an exemplary system architecture diagram to which embodiments of the present invention may be applied;

[0047] Figure 6 It is a schematic diagram of the structure of a computer system of a terminal device or a server suitable for implementing an embodiment of the present invention. DETAILED DESCRIPTION

[0048] The following is a description of exemplary embodiments of the present invention in conjunction with the accompanying drawings, including various details of the embodiments of the present invention to facilitate understanding, which should be considered as merely exemplary. Therefore, it should be recognized by those of ordinary skill in the art that various changes and modifications may be made to the embodiments described herein without departing from the scope and spirit of the present invention. Similarly, for clarity and conciseness, the description of well-known functions and structures is omitted in the following description.

[0049] Figure 1 is a schematic diagram of the main flow of the data processing method according to the first embodiment of the present invention. Figure 1 As shown, the data processing method includes:

[0050] Step S101, obtaining business information.

[0051] In the embodiment, obtaining business information clarifies the data processing object of the present invention, and the business information also serves as the basic data source for subsequent parsing to obtain state machine files, generate state machine software packages, and visualize the state machine flow chart. In a further embodiment, after obtaining the business information, a blank state machine file can be created to correspond to the business information, wherein the format of the state machine file can be an extensible markup language (XML) file, which is convenient for quickly and clearly defining multiple attributes and multiple structures of data, and is easy for data interaction.

[0052] Step S102, extract multiple business status change events from the business information, and parse each business status change event to obtain the business status before the change, the business status after the change, the change condition and the execution action, so as to record them in a preset state machine file accordingly.

[0053] In the embodiment, after the processing of this step, each business state change event is extracted and sorted, and then in the subsequent execution processing of the state machine software package, after executing each business state change event, all business state change events can be sequentially connected by matching the same business state before the change according to the current business state after the change, thereby achieving the technical purpose of correctly sorting the business state changes of the whole process, and further, while enhancing the readability of the state machine software package of the present invention, it also paves the way for the subsequent generation of the corresponding state machine flow chart.

[0054] In some embodiments, in order to further clarify the logical order of business processing corresponding to each business status change event, when parsing the business status before the change, the business status after the change, the change condition and the execution action included in each business status change event, it can be determined that the change condition is triggered by the business status before the change; and it is determined that the execution action is triggered by the business status after the change. For example, the logical order of a business status change event is: in the business status before the change, in response to determining that the corresponding change condition is met, the business status is changed (i.e., converted to the business status after the change), and the corresponding execution action is executed.

[0055] In some embodiments, in order to clearly classify the business status, each business status change event can be parsed to obtain the business status before the change, the business status after the change, the change condition and the execution action, and then each change condition is parsed to determine the business events included in each change condition; for each change condition: determine whether it includes only one business event; if so, determine that the business status after the change corresponding to the change condition is a simple business status; if not, determine that the business status after the change corresponding to the change condition is a composite business status; to determine the attributes of each business status. For example, if the change condition of business status S1 is only to complete business event E1, then business status S1 belongs to a simple business status; if the change condition of business status S2 is to complete business events E2 and E3, then business status S2 belongs to a composite business status; if the change condition of business status S3 is to complete business events E4 or E5, then business status S3 belongs to a composite business status. Through the processing of this step, the attributes of different business states are divided, so that it is clear whether the adjacent business states correspond to serial changes or parallel changes, thereby further clarifying the overall business status flow process, which helps to improve the accuracy of business process combing of this technical solution.

[0056] In some embodiments, in order to clearly define each business state in the state machine file so that it can be reviewed based on the corresponding business state definition information when the corresponding business state change event is running, after determining the attributes of each business state, multiple business states can be extracted from the business information; the initial business state and the final business state are screened from the multiple business states and marked respectively; the attributes and logical interfaces corresponding to each business state are determined; and a state information set is generated in the state machine file.

[0057] Step S103: creating corresponding logical interfaces for each service state, each change condition and each execution action in the state machine file.

[0058] In an embodiment, after the processing of this step, corresponding expansion slots are reserved for each service process included in the service information, achieving the technical purpose of separating service description and service implementation, thereby further simplifying and clarifying the corresponding service logic description code, enhancing the readability of the service logic script, facilitating relevant developers to quickly follow up on the service, and thus improving the efficiency of service processing.

[0059] For example, in each state machine file, multiple service state change events included can be defined respectively using Extensible Markup Language, including but not limited to: First, a uniquely defined state machine number for each state machine file can be generated, which can be represented by "<stageMachine id=...>"; Second, multiple corresponding service states are defined respectively (which can be distinguished by adding "" with a line break), using "<stage name=...>" to represent the name of each service state, using "<enterMethod=...>" to represent the entry state logic interface of each service state, using "<existMethod=...>" to represent the exit state logic interface of each service state, using "<isLasted=true or false>" to represent whether this service state is the final service state, using "<compositeType=serial or parallel>" to represent the corresponding attribute information of this service state (i.e., the above simple service state or composite service state), and after the definition is completed, the end of this part of the content is characterized by adding "" with a line break; At the same time, in the " <events>"In the " section, define the corresponding multiple business events (that is, state change events), you can use " <event> Reject< / event> "To define a business event rejected by a processing end, you can use" <event> Submit< / event> "To define a business event submitted by a processing end, you can use" <event> Revok< / event> "Defines a business event that is canceled by a processing end; in addition, in " <transfers>Define each state change event in the "part", such as the statement "<transfer from="business state 1”to"business state 2”trigger="…”callMethod="…”condition="…”>", where "transfer from” and "to” respectively correspond to the business state before the change and the business state after the change, "trigger” is the logical interface of the change event, "callMethod” is the logical interface for executing the action, and "condition” is the logical interface for verifying the change event. In a further embodiment, each XML file may include the content of one or more state machine files, and the state and file to which the corresponding content belongs are characterized by format indentation.

[0060] Step S104, use a preset mapping tool to parse the state machine file to obtain a state machine attribute definition object, and use a preset bytecode tool to convert the state machine attribute definition object into a corresponding state machine software package.

[0061] In some embodiments, in order to be able to locate the corresponding business state in real time during the operation of the state machine software package, before using the preset mapping tool to parse the state machine file, for each business state change event in the state machine file: insert a preset recorder in the business state after the change to record the corresponding business state change event; and create a logical interface for each recorder in the state machine file. After the processing of this step, it can effectively avoid the situation in the prior art: when the business state is abnormal, because there is a lack of the historical track of the business state change, it is necessary to check the state machine code to determine the business state, and then analyze the corresponding possible exceptions; thus enhancing the debugging efficiency and practical performance of the state machine software package of the present invention.

[0062] In some embodiments, in order to monitor the completion degree of each business event and thus accurately and timely promote the corresponding business processing, after determining the business events included in each change condition, for each business event in the state machine file: generate a corresponding verification tool to determine whether the corresponding business event is completed, if not, keep it, if so, mark the corresponding business event; and create a logical interface for each verification tool in the state machine file.

[0063] In some embodiments, in order to differentiate the business status change events with more complex change conditions, thereby ensuring the timed monitoring and correct advancement of the corresponding business status change events, after generating the corresponding verification tool, the business status after the change can be used as a screening condition to filter out the target business status change event from all status change events; for each target business status change event in the state machine file: insert a preset timed task into the business status before the change to regularly determine whether the multiple business events included in the corresponding change conditions are all marked, if not, maintain them, if so, change the business status; and create a logical interface for each timed task in the state machine file.

[0064] In some embodiments, in order to clearly define all business events in the state machine file so that erroneous descriptions can be automatically detected when running the corresponding state machine file, after creating a logical interface for each verification tool in the state machine file, the logical interface, verification tool and the logical interface of the verification tool corresponding to each business event can be determined; so as to generate an event information set in the state machine file.

[0065] In the embodiment, after this step of processing, the BeanDefinition property definition file is used to quickly and conveniently generate the corresponding state machine software package, so as to save a lot of logic for repeatedly processing the relevant state by the business system, thereby saving a lot of server resources and improving the overall performance of this product. On the other hand, the relevant developers only need to complete the mapping of the business interface and the logic interface in the basic framework, and then release the state machine program online, thereby saving labor costs to a great extent and improving the implementation cost performance of this technical solution.

[0066] In some embodiments, in order to further enhance the readability of the state machine file, the state machine attribute definition object can be converted into a corresponding state machine software package, and then the state machine file can be formatted using an extensible stylesheet transformation language process to obtain a corresponding document template file, so as to visualize the document template file in a graphic visualization software to generate a corresponding state machine flowchart; and the state machine software package and the state machine flowchart are associated. After this step of processing, the state machine file is further parsed in the form of a flowchart, so that relevant developers can quickly follow up on the corresponding business processing.

[0067] Figure 2 is a schematic diagram of the main flow of a data processing method according to a second embodiment of the present invention, the data processing method comprising:

[0068] Step S201, obtaining business information.

[0069] Step S202, extract multiple business status change events from the business information, and parse each business status change event to obtain the business status before the change, the business status after the change, the change condition and the execution action, so as to record them into a preset state machine file accordingly.

[0070] Preferably, it is determined that the change condition is triggered by the business state before the change, and it is determined that the execution action is triggered by the business state after the change.

[0071] Step S203: creating corresponding logical interfaces for each service state, each change condition and each execution action in the state machine file.

[0072] Step S204: parse each change condition to determine the business events included in each change condition.

[0073] Step S205, determining whether each change condition includes only one business event, if yes, executing step S206, if no, executing step S207.

[0074] Step S206: Determine whether the changed service state corresponding to the change condition is a simple service state.

[0075] Step S207: determine that the changed service state corresponding to the change condition is a composite service state.

[0076] Step S208: Determine the attributes of each service status.

[0077] Step S209: Generate a state information set in the state machine file.

[0078] Preferably, multiple business states are extracted from the business information; an initial business state and a final business state are screened from the multiple business states and marked respectively; the attributes and logical interfaces corresponding to each business state are determined; and a state information set is generated in a state machine file.

[0079] Step S210, for each service state change event in the state machine file: insert a preset recorder into the changed service state, and create a logical interface for each recorder in the state machine file.

[0080] Preferably, the recorder is used to record corresponding business status change events.

[0081] Step S211, for each business event in the state machine file: generate a corresponding verification tool, and create a logical interface for each verification tool in the state machine file.

[0082] Preferably, the verification tool is used to determine whether the corresponding business event is completed, if not, keep it, if yes, mark the corresponding business event.

[0083] Step S212, for each composite service state in the state machine file: inserting a preset scheduled task into the corresponding service state before the change, and creating a logical interface for each scheduled task in the state machine file.

[0084] Preferably, the timing task uses timing to determine whether multiple business events included in the corresponding change condition are all marked, if not, maintain, if yes, change the business status.

[0085] Step S213: Generate an event information set in the state machine file.

[0086] Preferably, the logical interface, the verification tool and the logical interface of the verification tool respectively corresponding to each business event are determined; so as to generate an event information set in the state machine file.

[0087] Step S214: Use a preset mapping tool to parse the state machine file to obtain a state machine attribute definition object.

[0088] Step S215: using a preset bytecode tool, convert the state machine attribute definition object into a corresponding state machine software package.

[0089] Step S216: convert the format of the state machine file using the extensible style sheet transfer language process to obtain a corresponding document template file.

[0090] Step S217, visualizing the document template file in Graphviz to generate a corresponding state machine flow chart.

[0091] Step S218: Associating the state machine software package with the state machine flow chart.

[0092] Figure 3 is a schematic diagram of the main flow of a data processing method according to a third embodiment of the present invention, the data processing method comprising:

[0093] Step S301, obtaining business information.

[0094] Step S302, extract multiple business status change events from the business information, and parse each business status change event to obtain the business status before the change, the business status after the change, the change condition and the execution action, so as to record them in a preset state machine file accordingly.

[0095] Preferably, it is determined that the change condition is triggered by the business state before the change, and it is determined that the execution action is triggered by the business state after the change.

[0096] Step S303: Create corresponding logical interfaces for each service state, each change condition and each execution action in the state machine file.

[0097] Step S304: parse each change condition to determine the business events included in each change condition.

[0098] Step S305, determine whether each change condition includes only one business event, if yes, execute step S306, if no, execute step S307.

[0099] Step S306: determine that the changed service state corresponding to the change condition is a simple service state.

[0100] Step S307: determine that the changed service state corresponding to the change condition is a composite service state.

[0101] Step S308: Determine the attributes of each service status.

[0102] Step S309: Generate a state information set in the state machine file.

[0103] Preferably, multiple business states are extracted from the business information; an initial business state and a final business state are screened from the multiple business states and marked respectively; the attributes and logical interfaces corresponding to each business state are determined; and a state information set is generated in a state machine file.

[0104] Step S310, for each service state change event in the state machine file: insert a preset recorder into the changed service state, and create a logical interface for each recorder in the state machine file.

[0105] Preferably, the recorder is used to record corresponding business status change events.

[0106] Step S311, for each business event in the state machine file: generate a corresponding verification tool, and create a logical interface for each verification tool in the state machine file.

[0107] Preferably, the verification tool is used to determine whether the corresponding business event is completed, if not, keep it, if yes, mark the corresponding business event.

[0108] Step S312, for each composite service state in the state machine file: inserting a preset scheduled task into the service state before the corresponding change, and creating a logical interface for each scheduled task in the state machine file.

[0109] Preferably, the timing task uses timing to determine whether multiple business events included in the corresponding change condition are all marked, if not, maintain, if yes, change the business status.

[0110] Step S313: Generate an event information set in the state machine file.

[0111] Preferably, the logical interface, the verification tool and the logical interface of the verification tool respectively corresponding to each business event are determined; so as to generate an event information set in the state machine file.

[0112] Step S314: Use a preset mapping tool to parse the state machine file to obtain a state machine attribute definition object.

[0113] Step S315: Use a preset bytecode tool to convert the state machine attribute definition object into a corresponding state machine software package.

[0114] Figure 4 is a schematic diagram of main modules of a data processing device according to an embodiment of the present invention, such as Figure 4 As shown, the data processing device 400 includes an acquisition module 401, a parsing module 402, an interface module 403 and a processing module 404. The acquisition module 401 is used to acquire business information; the parsing module 402 is used to extract multiple business state change events from the business information, and parse each business state change event to obtain the business state before the change, the business state after the change, the change condition and the execution action, so as to record them in a preset state machine file; the interface module 403 is used to create a corresponding logical interface for each business state, each change condition and each execution action in the state machine file; the processing module 404 is used to parse the state machine file using a preset mapping tool to obtain a state machine attribute definition object, and use a preset bytecode tool to convert the state machine attribute definition object into a corresponding state machine software package.

[0115] In some embodiments, the analysis module 402 is also used to: when parsing each business status change event to obtain the business status before the change, the business status after the change, the change condition and the execution action respectively included, determine that the change condition is triggered by the business status before the change; and determine that the execution action is triggered by the business status after the change.

[0116] In some embodiments, the parsing module 402 is also used to: after parsing each business status change event to obtain the business status before the change, the business status after the change, the change condition and the execution action, parse each change condition to determine the business events included in each change condition; for each change condition: determine whether it includes only one business event; if so, determine that the business status after the change corresponding to the change condition is a simple business status; if not, determine that the business status after the change corresponding to the change condition is a composite business status; to determine the attributes of each business status.

[0117] In some embodiments, the parsing module 402 is also used to: after determining the attributes of each business state, extract multiple business states from the business information; filter out the initial business state and the final business state from the multiple business states, and mark them respectively; determine the attributes and logical interfaces corresponding to each business state; and generate a state information set in the state machine file.

[0118] In some embodiments, the interface module 403 is also used to: before using a preset mapping tool to parse the state machine file, for each business state change event in the state machine file: insert a preset recorder into the changed business state to record the corresponding business state change event; and create a logical interface for each recorder in the state machine file.

[0119] In some embodiments, the interface module 403 is also used to: after determining the business events included in each change condition, for each business event in the state machine file: generate a corresponding verification tool to determine whether the corresponding business event is completed, if not, maintain it, if yes, mark the corresponding business event; and create a logical interface for each verification tool in the state machine file.

[0120] In some embodiments, the interface module 403 is also used to: after generating the corresponding verification tool, use whether the changed business state is a composite business state as a screening condition to screen out the target business state change event from all state change events; for each target business state change event in the state machine file: insert a preset timed task into the business state before the change to periodically determine whether multiple business events included in the corresponding change condition are all marked, if not, maintain them, if yes, change the business state; and create a logical interface for each timed task in the state machine file.

[0121] In some embodiments, the parsing module 402 is also used to: after creating a logical interface for each verification tool in the state machine file, determine the logical interface, verification tool and the logical interface of the verification tool corresponding to each business event respectively; so as to generate an event information set in the state machine file.

[0122] In some embodiments, the processing module 404 is also used to: after converting the state machine property definition object into a corresponding state machine software package, use an extensible stylesheet transformation language process to convert the format of the state machine file to obtain a corresponding document template file, so as to visualize the document template file in a graphic visualization software to generate a corresponding state machine flowchart; and associate the state machine software package with the state machine flowchart.

[0123] It should be noted that the data processing method and the data processing device described in the present invention have a corresponding relationship in terms of specific implementation contents, so the repeated contents will not be described again.

[0124] Figure 5 An exemplary system architecture 500 is shown to which the data processing method or data processing device according to the embodiment of the present invention can be applied.

[0125] like Figure 5 As shown, system architecture 500 may include terminal devices 501, 502, 503, a network 504 and a server 505. Network 504 is used to provide a medium for communication links between terminal devices 501, 502, 503 and server 505. Network 504 may include various connection types, such as wired, wireless communication links or optical fiber cables, etc.

[0126] The user can use the terminal devices 501, 502, 503 to interact with the server 505 through the network 504 to receive or send messages, etc. Various communication client applications can be installed on the terminal devices 501, 502, 503.

[0127] The terminal devices 501 , 502 , and 503 may be various electronic devices having a page display processing screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers, desktop computers, and the like.

[0128] The server 505 may be a server that provides various services, such as a background management server (only an example) that provides support for users to use the terminal devices 501, 502, and 503. The background management server may analyze and process the received data such as the product information query request, and feed back the processing results (such as target push information, product information - only an example) to the terminal device.

[0129] It should be noted that the data processing method provided in the embodiment of the present invention is generally executed by the server 505 , and accordingly, the computing device is generally disposed in the server 505 .

[0130] It should be understood that Figure 5 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to implementation requirements.

[0131] Reference below Figure 6 , which shows a schematic diagram of the structure of a computer system 600 of a terminal device suitable for implementing an embodiment of the present invention. Figure 6 The terminal device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention.

[0132] like Figure 6 As shown, the computer system 600 includes a central processing unit (CPU) 601, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 602 or a program loaded from a storage part 608 into a random access memory (RAM) 603. In the RAM 603, various programs and data required for the operation of the computer system 600 are also stored. The CPU 601, the ROM 602, and the RAM 603 are connected to each other via a bus 604. An input / output (I / O) interface 605 is also connected to the bus 604.

[0133] The following components are connected to the I / O interface 605: an input section 606 including a keyboard, a mouse, etc.; an output section 607 including a cathode ray tube (CRT), a liquid crystal page display processor (LCD), etc., and a speaker, etc.; a storage section 608 including a hard disk, etc.; and a communication section 609 including a network interface card such as a LAN card, a modem, etc. The communication section 609 performs communication processing via a network such as the Internet. A drive 610 is also connected to the I / O interface 605 as needed. A removable medium 611, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 610 as needed, so that a computer program read therefrom is installed into the storage section 608 as needed.

[0134] In particular, according to the embodiments disclosed in the present invention, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present invention include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 609, and / or installed from the removable medium 611. When the computer program is executed by the central processing unit (CPU) 601, the above-mentioned functions defined in the system of the present invention are executed.

[0135] It should be noted that the computer-readable medium shown in the present invention may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, 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), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present invention, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, device or device. In the present invention, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries a computer-readable program code. This propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, optical cable, RF, etc., or any suitable combination of the above.

[0136] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present invention. In this regard, each box in the flow chart or block diagram can represent a module, a program segment, or a part of a code, and the above-mentioned module, program segment, or a part of a code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flow chart, and the combination of the boxes in the block diagram or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0137] The modules involved in the embodiments of the present invention may be implemented by software or hardware. The modules described may also be set in a processor, for example, it may be described as: a processor includes an acquisition module, a parsing module, an interface module and a processing module. The names of these modules do not constitute limitations on the modules themselves in some cases.

[0138] As another aspect, the present invention also provides a computer-readable medium, which may be included in the device described in the above embodiment; or it may exist independently without being assembled into the device. The above computer-readable medium carries one or more programs. When the above one or more programs are executed by a device, the device includes obtaining business information; extracting multiple business status change events from the business information, and parsing each business status change event to obtain the business state before the change, the business state after the change, the change condition and the execution action, so as to record the corresponding state machine file; creating corresponding logical interfaces for each business state, each change condition and each execution action in the state machine file; using a preset mapping tool to parse the state machine file to obtain a state machine attribute definition object, and using a preset bytecode tool to convert the state machine attribute definition object into a corresponding state machine software package. According to the technical solution of the embodiment of the present invention, it is possible to solve the technical problem of high complexity and low efficiency in the existing business status update processing.

[0139] The above specific implementations do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may occur depending on design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.< / transfers> < / events>

Claims

1. A data processing method, characterized in that: include: Obtain business information; Extract multiple business status change events from the business information, and parse each business status change event to obtain the business status before the change, the business status after the change, the change condition, and the execution action, so as to record them in a preset state machine file accordingly; In the state machine file, a corresponding logical interface is created for each business state, each change condition and each execution action; The state machine file is parsed using a preset mapping tool to obtain a state machine attribute definition object, and the state machine attribute definition object is converted into a corresponding state machine software package using a preset bytecode tool.

2. The method according to claim 1, characterized in that The business status change event is analyzed to obtain the business status before the change, the business status after the change, the change condition and the execution action, including: Determine the business status before the change is triggered by the change condition; And determine that the execution action is triggered by the changed business status.

3. The method according to claim 1, characterized in that After parsing each business status change event to obtain the business status before the change, the business status after the change, the change condition, and the execution action, it includes: Analyze each change condition to determine the business events included in each change condition; For each change condition: Determine whether only one business event is included; If so, determining that the changed service state corresponding to the change condition is a simple service state; If not, determining that the changed service state corresponding to the change condition is a composite service state; To determine the attributes of each business state.

4. The method according to claim 3, characterized in that After determining the attributes of each business state, including: Extract multiple business states from business information; Filtering multiple business states to obtain an initial business state and a final business state, and marking them respectively; Determine the attributes and logical interfaces corresponding to each business state; to generate a collection of state information in a state machine file.

5. The method according to claim 1, characterized in that Before using the preset mapping tool to parse the state machine file, it includes: For each business state change event in the state machine file: insert a preset recorder into the changed business state to record the corresponding business state change event; And create the logical interface for each logger in the state machine file.

6. The method according to claim 3, characterized in that After determining the business events included in each change condition, including: For each business event in the state machine file: generate a corresponding verification tool to determine whether the corresponding business event is completed, if not, keep it, if yes, mark the corresponding business event; And create a logical interface for each verification tool in the state machine file.

7. The method according to claim 6, characterized in that After generating the corresponding verification tools, including: The changed business state is a composite business state as a screening condition, so as to screen out the target business state change event from all state change events; For each target business state change event in the state machine file: insert a preset timer task in the business state before the change to regularly determine whether multiple business events included in the corresponding change conditions are all marked. If not, keep it, if yes, change the business state; And create a logical interface for each scheduled task in the state machine file.

8. The method according to claim 6, characterized in that After creating the logical interface for each validation tool in the state machine file, include: Determine the logical interface, the verification tool and the logical interface of the verification tool corresponding to each business event; To generate a collection of event information in the state machine file.

9. The method according to any one of claims 1 to 8, characterized in that: After converting the state machine property definition object into the corresponding state machine package, including: Using an extensible style sheet transfer language process to convert the format of the state machine file to obtain a corresponding document template file, so as to visualize the document template file in a graphic visualization software to generate a corresponding state machine flow chart; The state machine software package is associated with the state machine flow chart.

10. A data processing device, characterized in that: include: Acquisition module, used to obtain business information; A parsing module is used to extract multiple business status change events from the business information, and parse each business status change event to obtain the business status before the change, the business status after the change, the change condition and the execution action, so as to record the corresponding information in a preset state machine file; An interface module, used to create a corresponding logical interface for each service state, each change condition and each execution action in the state machine file; The processing module is used to parse the state machine file using a preset mapping tool to obtain a state machine attribute definition object, and to convert the state machine attribute definition object into a corresponding state machine software package using a preset bytecode tool.

11. An electronic device, characterized in that: include: one or more processors; a storage device for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1 to 9.

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

Images