CN116186107A - Service data processing method, device, equipment and storage medium - Google Patents
Service data processing method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN116186107A CN116186107A CN202211634619.9A CN202211634619A CN116186107A CN 116186107 A CN116186107 A CN 116186107A CN 202211634619 A CN202211634619 A CN 202211634619A CN 116186107 A CN116186107 A CN 116186107A
- Authority
- CN
- China
- Prior art keywords
- rule
- condition
- target
- service data
- state
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 36
- 230000004044 response Effects 0.000 claims abstract description 124
- 238000012545 processing Methods 0.000 claims abstract description 47
- 238000000034 method Methods 0.000 claims description 60
- 230000008569 process Effects 0.000 claims description 38
- 238000012795 verification Methods 0.000 claims description 30
- 230000007613 environmental effect Effects 0.000 claims description 15
- 230000002688 persistence Effects 0.000 claims description 11
- 230000006399 behavior Effects 0.000 description 28
- 230000008859 change Effects 0.000 description 12
- 238000010586 diagram Methods 0.000 description 11
- 238000004891 communication Methods 0.000 description 7
- 238000011161 development Methods 0.000 description 6
- 238000002955 isolation Methods 0.000 description 6
- 238000012827 research and development Methods 0.000 description 5
- 235000010627 Phaseolus vulgaris Nutrition 0.000 description 4
- 244000046052 Phaseolus vulgaris Species 0.000 description 4
- 230000002159 abnormal effect Effects 0.000 description 4
- 239000011159 matrix material Substances 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 230000008901 benefit Effects 0.000 description 3
- 238000013507 mapping Methods 0.000 description 3
- 230000007246 mechanism Effects 0.000 description 3
- 230000005012 migration Effects 0.000 description 3
- 238000013508 migration Methods 0.000 description 3
- 230000002085 persistent effect Effects 0.000 description 3
- 230000006978 adaptation Effects 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 239000000047 product Substances 0.000 description 2
- 239000010979 ruby Substances 0.000 description 2
- 229910001750 ruby Inorganic materials 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 238000002347 injection Methods 0.000 description 1
- 239000007924 injection Substances 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 239000010410 layer Substances 0.000 description 1
- 238000002360 preparation method Methods 0.000 description 1
- 238000000926 separation method Methods 0.000 description 1
- 239000002356 single layer Substances 0.000 description 1
- 239000000243 solution Substances 0.000 description 1
- 239000007858 starting material Substances 0.000 description 1
- 239000013589 supplement Substances 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2458—Special types of queries, e.g. statistical queries, fuzzy queries or distributed queries
- G06F16/2465—Query processing support for facilitating data mining operations in structured databases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/26—Visual data mining; Browsing structured data
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/284—Relational databases
- G06F16/285—Clustering or classification
- G06F16/287—Visualization; Browsing
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- General Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Fuzzy Systems (AREA)
- Computational Linguistics (AREA)
- Software Systems (AREA)
- Probability & Statistics with Applications (AREA)
- Mathematical Physics (AREA)
- Debugging And Monitoring (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application discloses a business data processing method, a device, equipment and a storage medium, which belong to the technical field of data processing and are used for receiving business data; determining target conditions matched with the service data from preset matching rules, and judging whether the target conditions contain state conditions or not; if the state condition is contained, determining a target rule response queue mapped with the target condition based on a preset state machine mode, and executing response operation in the target rule response queue; and determining a target rule response queue mapped with the target condition according to different service data in different states, and returning an execution result corresponding to the service data, namely, the service decision corresponding to the service data in different states can be obtained, so that the diversity of the service decision is improved.
Description
Technical Field
The present disclosure relates to the field of data processing technologies, and in particular, to a method, an apparatus, a device, and a storage medium for processing service data.
Background
At present, when a rule engine is used for realizing agile research and development of a service scene, the working mode of the conventional rule engine is found to match the received service data with various rules in a rule base so as to obtain a corresponding service decision result.
Whereas the sentences defined by the various rules in the rule base are generally "… if …", such rule engines cannot be applied to services with various scenes or state changes, and the service decision result is relatively single.
Therefore, the prior art has the problem that the service decision obtained by using the rule engine has low diversity.
Disclosure of Invention
The main purpose of the application is to provide a business data processing method, a device, equipment and a storage medium, which aim to solve the technical problem of low business decision diversity obtained by using a rule engine.
In order to achieve the above object, the present application provides a service data processing method, which includes the following steps:
receiving service data;
determining target conditions matched with the service data from preset matching rules, and judging whether the target conditions contain state conditions or not;
if the state condition is contained, determining a target rule response queue mapped with the target condition based on a preset state machine mode, and executing response operation in the target rule response queue;
and returning an execution result corresponding to the service data.
Compared with the prior art that a rule engine cannot be suitable for services with various scenes or state changes, the service data processing method provided by the application has the advantage that the obtained service decision result is single; the method and the device receive service data; determining target conditions matched with the service data from preset matching rules, and judging whether the target conditions contain state conditions or not; if the state condition is contained, determining a target rule response queue mapped with the target condition based on a preset state machine mode, and executing response operation in the target rule response queue; and determining a target rule response queue mapped with the target condition according to different service data in different states, and returning an execution result corresponding to the service data, namely, the service decision corresponding to the service data in different states can be obtained, so that the diversity of the service decision is improved.
Drawings
Fig. 1 is a schematic flow chart of a first embodiment of a service data processing method of the present application;
fig. 2 is a schematic diagram of a first scenario of a service data processing method according to a first embodiment of the present application;
fig. 3 is a second scenario diagram of a service data processing method according to the first embodiment of the present application;
fig. 4 is a schematic diagram of a third scenario of a service data processing method according to the first embodiment of the present application;
fig. 5 is a fourth scenario diagram of a service data processing method according to the first embodiment of the present application;
fig. 6 is a schematic diagram of a fifth scenario of a service data processing method according to the first embodiment of the present application;
fig. 7 is a schematic diagram of a sixth scenario of a service data processing method according to the first embodiment of the present application;
fig. 8 is a schematic view of a seventh scenario of a service data processing method according to the first embodiment of the present application;
fig. 9 is an eighth scenario diagram of a service data processing method according to the first embodiment of the present application;
fig. 10 is a schematic diagram of a ninth scenario of a service data processing method according to the first embodiment of the present application;
fig. 11 is a logic architecture diagram of a service data processing method according to a second embodiment of the present application;
fig. 12 is a schematic structural diagram of a service data processing device of a hardware running environment according to an embodiment of the present application.
The realization, functional characteristics and advantages of the present application will be further described with reference to the embodiments, referring to the attached drawings.
Detailed Description
It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the present application. Although the terms first, second, third, etc. may be used herein to describe various information, these information should not be limited by these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope herein.
An embodiment of the present application provides a service data processing method, referring to fig. 1, in this embodiment, the service data processing method includes:
step S10: receiving service data;
step S20: determining target conditions matched with the service data from preset matching rules, and judging whether the target conditions contain state conditions or not;
step S30: if the state condition is contained, determining a target rule response queue mapped with the target condition based on a preset state machine mode, and executing response operation in the target rule response queue;
step S40: and returning an execution result corresponding to the service data.
As an example, the business data processing method is applied to a business data processing system, in particular to an application platform in the business data processing system, which is subordinate to a business data processing device.
As an example, when developing the application platform, implementing the business data processing method in the application platform based on a rule engine, wherein the rule engine is developed by an inference engine, the rule engine is a component embedded in the application platform, implementing the separation of business decisions from application program codes, and writing business decisions using predefined semantic modules; and receiving data input, interpreting the business rule, and making a business decision according to the business rule.
As an example, when a complex service platform is developed, logic codes and service codes of the program are nested and complicated, and meanwhile, the maintenance cost is high and the expansibility is poor. A rules engine (e.g., open source engine Drools) can reduce complex business logic component complexity, reduce maintenance and scalability of applications.
At present, when a rule engine is used for realizing agile research and development of a service scene, the working mode of the conventional rule engine is found to match the received service data with various rules in a rule base so as to obtain a corresponding service decision result. Whereas the sentences defined by the various rules in the rule base are generally "… if …", such rule engines cannot be applied to services with various scenes or state changes, and the service decision result is relatively single.
In order to be able to handle agile research and development services, agile research and development service scenario flows require support of state machine scenarios, however, existing rule engines cannot support state machine scenarios.
The state machine scene is similar to an approval process engine in the function support range, based on state definition and state inversion, a driving core is formed, the service flow based on a state machine mechanism is completed, the state machine engine inevitably comprises an event response engine, however, the event is represented as a state related event, the migration event is initiated by a system or a person, the response is embodied as related response processing and state value change, the state and migration restrict event rules in a simple way, and the action defines the response. The state machine engine typically identifies rule-compliant state values and migration behavior through a state matrix.
Therefore, the application aims to realize a transaction type application platform through the introduction of a rule engine, and the application platform is characterized in that: complex data structure, complex flow control, large amount of data processing and statistics rules, personalized interaction mode and various communication cooperation modes. Then various objects are also faced and the characteristics of the objects: diversity, variability, complexity, relevance, disassemblability, confidentiality, error-prone, normative.
That is, the application provides a rule engine supporting a state machine mode, and meanwhile, the rule engine can support flexible and changeable work objects in the agile research and development business field in daily work. Through the rule engine supporting the state machine mode, service personnel can efficiently realize own service flow with low cost through rule configuration, and the software development period is reduced. Compared with the prior art, the application enables the rule engine, different applications only need to configure rules according to needs, and personalized processing requests are supported by combining the processing units.
As an example, maven (a Java platform-based project management and integration tool) may be used to manage the development and management process of a project in the development of an application platform by Spring (a Java development framework) which abstracts the development and management process of the project into a Project Object Model (POM). The deployment of the rule engine can be completed by introducing the public components (dependent packages) and the rule engine which need to be used through Maven, specifically, maven independently introduces the public components or the rule engine through a POM module, or packages the public components and the rule engine into a Starter for introduction.
As an example, after the deployment of the rule engine is completed, the rule engine is registered into a Spring Bean container (used for managing the Spring Bean) through @ Component (used for implementing the injection of the Bean object) by adopting the Spring Bean (used for storing the logic code of the application platform), and then the loading of the rule engine can be completed.
As an example, after completing the loading of the rule engine, the developer only needs to make some simple rule configuration in the rule engine, so that the development of the application platform can be completed. Therefore, in the process of developing the application platform, a large amount of programming is not required by a developer, the development workload is reduced, and the programming level requirement on the developer is reduced.
As an example, the rule engine provides default condition rules, behavior rules, and the like, and the rule engine interface also provides a condition element interface, a behavior element interface, a context object interface, an intermediate value element interface, and the like, which are not particularly limited. The user can customize the Condition rule through the I Condition Unit interface, customize the behavior rule through the I Action Unit interface, customize the Context Object (Context) through the I Status Engine Context Context Object interface, the Context Object is a data structure similar to Map < String, object > (Map is a mapping table, string is an attribute name, and the Object corresponds to the reference of the Object), and the user can make keys by using character strings or other forms and put any type of data. The user can also customize the intermediate value through the I Middle Unit intermediate value (some rule between two rules) Unit interface.
As an example, the condition rules may include an environmental condition rule and a status condition rule, the status condition rule indicating whether the current business object is in a certain state, and determining a corresponding response operation based on the state in which the current business object is. The environmental condition rule represents a rule of a non-state condition, for example, a corresponding response operation is determined based on a type of a current business object, or a corresponding response operation is determined based on a processing period of the current business object, etc., which is not particularly limited.
As an example, the service data, that is, the service object registered by the user, may be a document or a product, and the like, and is not limited in particular.
Specifically, considering partial complexity and adaptability, a user can upload a custom script through an interface provided by a rule engine interface, the rule engine runs the script, and the script is executed by using the rule engine, so that the registration of the extension content (condition rule, behavior rule and the like) in the custom script of the user is realized.
As an example, as shown in fig. 2, the user-provided custom script types may be a bloom y script, a V8js script, a ruby script, etc., and the corresponding custom script types provided by the user include a bloom y grammar engine, a V8js grammar engine, a ruby grammar engine, etc., which are not limited in particular, but the content of the grammar engine operation is limited to a predefined script package and a predefined context object, so that the business boundary security is ensured.
As an example, the processing objects serving as the condition unit and the behavior unit are added into the rule engine in a registration mode, the rule engine does not directly pay attention to the actual source of the data of the processing objects, and decoupling is realized conveniently.
As an example, in order to facilitate the condition unit and behavior unit manipulation of Object data, the registered Object needs to be formatted, as shown in fig. 3, as a K-V (Key-Value, attribute-field type) Object of Map < String, object > type is necessary. As shown in fig. 4, the formatted data objects aggregate business objects that need to be processed at the condition unit and behavior unit, which have type detection for the data objects of the operation. That is, the business objects (documents, products, etc.) are registered in the rule engine, and the condition objects corresponding to the business objects and the behavior objects (i.e., the data assembly process in fig. 4) are also required to be registered, where the condition objects are state conditions and/or non-state conditions that may be included in the registered current business object, and the behavior objects are possible response operations that may be performed corresponding to the state conditions that may be included in the registered current business object. The rule engine analyzes and executes the rule on the registered business object and the corresponding condition object and behavior object based on the condition rule and behavior rule, and returns the data to the business object after the processing is completed (the rule engine changes the business data of the business object).
Therefore, in the processing of the condition unit and the behavior unit, the corresponding object type needs to be explicitly defined to be normally called, besides the object needs to be registered at the time of running, metadata of description type needs to be provided, and definition is given at the time of initialization. However, the actual data description using a single layer cannot satisfy all scenes, for example, the data object of the scene used by the working object is a complex basic data, multiple layers of description need to be introduced in the condition unit, as shown in fig. 3, for example, K1 represents a title, multiple data sub-attributes of the title are needed, V as a field of the title cannot be represented by a character string, but is described by multiple layers of K11 (ID), K12 (name) and K13 (theme), and fields corresponding to K11, K12 and K13 respectively can be a character string, and if K11, K12 and K13 still need further description, multiple layers of description are needed.
As an example, the rule engine only performs rule processing on business objects, does not do final persistence (binning), and there are two implementations of persistence operations:
one is to complete persistence based on registered response objects after the rule engine completes the current business processing;
one is to add custom behavior units to perform persistence processing in the behavior units;
the first control is completely controlled by the application outside the processing of the rule engine, which is not beneficial to the unified control of the rule engine on the business objects; the second way is to use custom behavior units to complete persistence processing, but a submission will trigger multiple rules, and the final execution sequence of rules is determined according to rules, so that the execution time of custom behavior units is changed, and is easy to be out of control, and the persistence processing is started by incorrect configuration in response to the fact that the processing is not completed, so that the rule engine needs to provide callback processing after business processing is completed.
Specifically, one or more rules are matched in one service request, corresponding predefined operations are executed, execution exception occurs in part of operations, callback needs to be performed on intermediate change data in order to maintain consistency, and because a behavior unit in a rule engine supports callback extension, the callback extension exceeds the control range of the rule engine, the rule engine cannot support a transaction mechanism, but a session mechanism can be provided, and therefore, in order to support callback, the callback extension realizes session management by an application platform.
As an example, the rule engine introduces an initial callback extension (starting a transaction) and a completion callback extension, and an abnormal callback, provides support for the transaction flow, can start the transaction based on a context object in the initial callback for the operation of a common database, finish the transaction in the callback, execute the unified callback operation in the abnormal callback, sequentially execute the callback methods in the behavior units according to the rule execution sequence in the abnormal execution, and finally execute the unified abnormal callback.
As an example, different application platforms have differences in rule execution appeal, even though the same orchestration results are differentiated when actually executed, so the rule engine needs to support isolation, from behavior units and condition units, and the data content needs to remain isolated during actual execution. By introducing a context object into a rule engine, the isolation strategy is divided into two layers by considering that the application ranges of various elements of the rule engine are different: application level isolation and session level isolation.
Specifically, as shown in fig. 5 and fig. 6, the static elements of the application-level isolation rule engine mainly include a behavior unit, a condition unit, a service object definition, a state matrix, and the like, where the general behavior unit and the condition unit belong to a system general capability and are globally valid, but can distinguish between a custom condition unit and a behavior unit of an application platform extension. Session-level isolation mainly isolates session elements of the rule engine execution process, including behavior units and condition units required in the specific business object processing process, ending callbacks, and the like.
That is, as shown in fig. 7, in the initialization stage of the application platform, the following preparation work needs to be completed: and introducing a rule engine component to complete the initialization of the interface, creating a context object, registering a custom unit of each context object, registering a unified ending callback of each context object, registering a state list and a state matrix of each context object, and registering rule configuration of each context object. In the service processing stage of the application platform, an application session needs to be established, and the condition object adaptation and registration to the service session are completed; completing behavior object adaptation and registering to a service session; registering a state object to a business session for a state machine scenario; in the running process, the synchronous state and the rule configuration change; executing service session and setting corresponding working mode.
The present embodiment aims at: based on rule response in the state machine mode, the diversity of business decisions is improved.
The method comprises the following specific steps:
step S10: receiving service data;
as an example, the application platform developed above can support a state machine mode, as shown in fig. 8, which includes two parts, one being a static configuration part: as shown in fig. 9, the data configuration of the state matrix, the description state list and the state inversion conforming to the rule need to be completed in the initialization process of the application platform; completing matching configuration of the state condition rule and the environment condition rule; mapping the rule and the response operation is completed; and defining the behavior operation of the response operation corresponding to the rule. The behavior operation includes: change business data (change workitem model field); calling an external API (Application Program Interface), an application programming interface; the bar is operated by other passes (e.g., mailing, etc.). The response operation is an operation step in the response queue, and the behavior operation is to execute the response operation corresponding to the target response queue. One is a dynamic execution part, a user submits service data change (service request) through a UI interface or an external system, and a rule engine analyzes a rule response queue triggered by the instance service data associated with the current submitting action according to rule configuration and sequentially executes corresponding response processing procedures in the queue. The rule operation result entry is persistent (if not necessary, part of rule response does not relate to the persistent operation) and other non-persistent operations, and the processing of the service data is completed.
Specifically, the flow is dynamically executed, and as shown in fig. 10, a user submits a service data change (service request) through a UI interface or an external system.
As an example, submitting a business data change may be assigning a value to a field transaction date, or changing a transaction state, etc. through a UI interface, which is not limited in particular.
Step S20: determining target conditions matched with the service data from preset matching rules, and judging whether the target conditions contain state conditions or not;
as an example, the preset matching rule is a matching rule of the service data and the target condition.
As one example, the target conditions include a state condition and a non-state condition.
As an example, a state condition is a condition that determines the current state of a business object.
As an example, the non-state condition is to decide the processing priority of the service object or whether a preset threshold is reached, and the like, and is not particularly limited.
As an example, the status condition includes a transaction date or a transaction period, etc., and the non-status condition includes a transaction amount or a transaction amount, etc., without being limited in particular.
Step S30: if the state condition is contained, determining a target rule response queue mapped with the target condition based on a preset state machine mode, and executing response operation in the target rule response queue;
as an example, the preset state machine mode is to make a corresponding response operation according to a state condition and then make a corresponding response operation according to a non-state condition.
As one example, each target condition has a mapping relationship with a target rule response queue.
As one example, the target rule response queue contains a plurality of response operations arranged in a predetermined order.
As an example, if a state condition is included in a target condition matching with the input traffic data, a target rule response queue mapped to the target condition, that is, a rule response queue corresponding to the state condition is determined based on a preset state machine mode.
As an example, if the current state of the business object is to be transacted and the target condition matched with the transaction date includes a state condition before the business data is input and the business data is input, determining that the current state of the business object is changed based on a preset state machine mode and the target rule response queue mapped with the state condition is in transaction. And determining a target rule response queue mapped with the non-state condition according to other non-state conditions in the target conditions.
Step S40: and returning an execution result corresponding to the service data.
As an example, a rule engine in the application platform executes corresponding response operations based on the target rule response queue and returns execution results corresponding to the service data.
As an example, based on the target rule response queue, the current state of the business object is changed into the transaction, the target rule response queue mapped with the non-state condition is executed, and the execution result corresponding to the business data is returned after the execution.
In this embodiment, after the step of returning the execution result corresponding to the service data, the method further includes:
step S50: and if the service data is detected to be changed, a third rule response queue is redetermined and obtained based on the changed service data, and the response operation in the third rule response queue is executed.
As an example, the response operation corresponding to the target rule response queue includes a plurality of steps, if the service data is detected to change in the process of executing the plurality of response operations corresponding to the target rule response queue, returning to the step of determining the target condition matched with the service data from the preset matching rule and judging whether the target condition includes the state condition or not based on the changed service data, re-determining to obtain a third rule response queue, and continuing to execute the response operation in the third rule response queue from the current response operation. That is, the rules engine supports internal secondary triggers of events (event responses will trigger new events again).
In this embodiment, after the step of returning the execution result corresponding to the service data, the method further includes:
step S120: and determining whether to perform persistence processing or not based on the type of the execution result of the service data.
As one example, the persistence operation is a store to database (binning) operation.
As an example, the type of execution result of the document includes a completed document, or a document still in process, etc., without limitation in particular.
As an example, the completed document may need to be stored in a database for it to be filled out, and no persistence operations may be performed for the document still in process.
It is determined whether to perform persistence processing.
In this embodiment, a rule engine supporting a state machine mode introduced by an application platform determines a target rule response queue mapped with the target condition for different service data in different states, and returns an execution result corresponding to the service data, that is, the application can obtain service decisions corresponding to the service data in different states, thereby improving the diversity of the service decisions.
Further, based on the first embodiment of the present application, there is provided another embodiment of the present application, in this embodiment, referring to fig. 11, the step of determining, if a state condition is included, a target rule response queue mapped with the target condition based on a preset state machine mode includes:
step A1: if the verification method comprises a plurality of state conditions, determining whether the plurality of state conditions all complete a verification process based on a preset condition rule based on a preset state machine mode;
as an example, if the input service data matches with a plurality of state conditions, and the plurality of state conditions are included, in order to ensure the correctness of the response, each state condition needs to be checked one by one based on a preset condition rule.
As an example, the preset condition rule may be customized by a user through a rule engine interface.
As an example, if the current state of the business object is to be transacted, the next state is in transaction, and then the next state is transaction completion, and if the state condition of the business data matching is transaction completion condition, based on the preset state condition rule, it is determined that the state to be transacted cannot jump to the transaction completion interface directly, that is, the rationality of the state and the compliance of the state flip need to be detected, so that the target rule response queue may be, without limitation, reminding the user to reenter, making the user unable to input or reminding the user to pay attention to the node, and the like.
As one example, the preset condition rules include a state condition rule and an environmental condition rule.
As an example, if the inputted transaction information includes a transaction date, a transaction period, a transaction quantity, a transaction amount, etc., the transaction date, the transaction period, and the transaction period need to be verified based on the state condition rule, and the transaction date, the transaction period, and the transaction period of the non-state condition need to be verified based on the environmental condition rule.
Step A2: if all the conditions are completed, determining whether the non-state conditions contained in the target conditions completely complete the verification process of the preset condition rule;
as an example, if the verification of the state condition has been completed, it is determined whether the non-state condition included in the target condition has completed the verification process of the preset condition rule.
Step A3: and if the target condition is completely finished, determining a target rule response queue based on the response operation mapped by the target condition.
As one example, if verification of the state condition and the non-state condition has been completed in total, a target rule response queue is determined based on the response operation to which the target condition is mapped.
In this embodiment, the preset condition rule includes a state condition rule, and if a plurality of state conditions are included, based on a preset state machine mode, after determining whether all of the plurality of state conditions have completed the steps of the verification process based on the preset condition rule, the method further includes:
step S60: if not, determining whether the state conditions of the incomplete verification process accord with the state condition rules;
as an example, if the verification of the status condition is not completed in its entirety, the verification of the status condition of the incomplete verification flow is continued.
Step S70: if yes, based on the response operation mapped by the state condition meeting the state condition rule, a first rule response queue is obtained, and the first rule response queue is inserted into the target rule response queue, so that the target rule response queue can be supplemented.
As an example, if the status condition of the incomplete verification process accords with the corresponding status condition rule, a first rule response queue is obtained based on the response operation mapped by the status condition which accords with the status condition rule.
As an example, the first rule response queue is inserted into the above-described target rule response queue to be executed as a target rule response queue as well.
In this embodiment, for the business object whose state needs to be determined, a rule engine supporting both a state machine mode and a normal mode is used to process the business object, so as to improve the diversity of business decisions. And verifying the target conditions matched with the service data one by one based on the target condition rules so as to comprehensively determine a target rule response queue and improve the accuracy of the executed target rule response queue.
Further, based on the first embodiment and the second embodiment in the present application, another embodiment in the present application is provided, in this embodiment, after the step of determining whether the target condition includes a status condition, the method further includes:
step S80: if the state condition is not contained, determining whether the target condition completely completes a verification process based on a preset condition rule based on a preset common mode, wherein the target condition has a plurality of target conditions;
as an example, if the target condition matched with the input service data does not include a state condition, it is indicated that the current service object does not need to consider a change of state, but one-to-one verification is still required to be performed on the non-state condition, so that based on a preset normal mode, it is determined whether the target condition has all completed a verification process based on a preset condition rule, where there are a plurality of target conditions.
As an example, if the number of transactions and the amount of transactions contained in the currently input transaction information are in and out of existence as specified in the environmental condition rules, the output result on the document may be affected.
Step S90: and if the target condition is completely finished, determining a target rule response queue based on the response operation mapped by the target condition.
As one example, if verification of the target condition has been completed entirely, a target rule response queue is determined based on the response operation to which the target condition is mapped.
In this embodiment, the preset condition rule further includes an environmental condition rule, and if the condition rule does not include the state condition, after determining, based on a preset normal mode, whether the target condition has all completed the steps of the verification process based on the preset condition rule, the method further includes:
step S100: if not, determining whether the non-state condition of the incomplete verification process accords with the environmental condition rule;
as an example, if the verification of the target condition is not completed entirely, the verification of the non-state condition for which the verification process is not completed is continued based on the environmental condition rule.
Step S110: and if yes, obtaining a second rule response queue based on the response operation mapped by the non-state condition meeting the environmental condition rule, and inserting the second rule response queue into the target rule response queue.
As an example, if the non-state condition of the incomplete verification process meets the environmental condition rule, a second rule response queue is obtained based on the response operation mapped by the non-state condition meeting the environmental condition rule.
As an example, inserting the second rule response queue into the target rule response queue may supplement the target rule response queue.
In this embodiment, the service processing logic of the rule engine supporting the normal mode is provided for the service object not requiring the determination of the state change, so as to avoid the complicated process in the process of processing the service object not requiring the determination of the state change by only adopting the rule engine supporting the state machine mode. Based on the environmental condition rules, verifying the non-state conditions matched with the service data one by one to comprehensively determine a target rule response queue, and improving the accuracy of the executed target rule response queue.
Referring to fig. 12, fig. 12 is a schematic device configuration diagram of a hardware running environment according to an embodiment of the present application.
As shown in fig. 12, the service data processing apparatus may include: a processor 1001, a memory 1005, and a communication bus 1002. The communication bus 1002 is used to enable connected communication between the processor 1001 and the memory 1005.
Optionally, the service data processing device may further include a user interface, a network interface, a camera, an RF (Radio Frequency) circuit, a sensor, a WiFi module, and the like. The user interface may include a Display, an input sub-module such as a Keyboard (Keyboard), and the optional user interface may also include a standard wired interface, a wireless interface. The network interface may include a standard wired interface, a wireless interface (e.g., WI-FI interface).
It will be appreciated by those skilled in the art that the business data processing apparatus structure shown in fig. 12 is not limiting of the business data processing apparatus, and may include more or fewer components than shown, or may combine certain components, or a different arrangement of components.
As shown in fig. 12, an operating system, a network communication module, and a service data processing program may be included in the memory 1005 as one type of storage medium. An operating system is a program that manages and controls the hardware and software resources of a business data processing device, supporting the operation of business data processing programs and other software and/or programs. The network communication module is used to enable communication between components within the memory 1005 and with other hardware and software in the business data processing system.
In the service data processing apparatus shown in fig. 12, a processor 1001 is configured to execute a service data processing program stored in a memory 1005, and implement the steps of the service data processing method described in any one of the above.
The specific implementation manner of the service data processing device is basically the same as that of each embodiment of the service data processing method, and is not repeated here.
The application also provides an optical module failure prediction device, which comprises:
the data receiving module is used for receiving service data;
the matching module is used for determining target conditions matched with the service data from preset matching rules and judging whether the target conditions contain state conditions or not;
the response module is used for determining a target rule response queue mapped with the target condition based on a preset state machine mode if the state condition is contained, and executing response operation in the target rule response queue;
and the result return module is used for returning an execution result corresponding to the service data.
The specific implementation manner of the service data processing device is basically the same as that of each embodiment of the service data processing method, and is not repeated here.
The present application also provides a storage medium having stored thereon a service data processing program which, when executed by a processor, implements the steps of the service data processing method as described in any one of the above.
The specific implementation manner of the storage medium is basically the same as that of each embodiment of the service data processing method, and is not repeated here.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or system. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or system that comprises the element.
The foregoing embodiment numbers of the present application are merely for describing, and do not represent advantages or disadvantages of the embodiments.
From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) as described above, including several instructions for causing a terminal device (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the method described in the embodiments of the present application.
The foregoing description is only of the preferred embodiments of the present application, and is not intended to limit the scope of the claims, and all equivalent structures or equivalent processes using the descriptions and drawings of the present application, or direct or indirect application in other related technical fields are included in the scope of the claims of the present application.
Claims (10)
1. A service data processing method, characterized in that the service data processing method comprises the following steps:
receiving service data;
determining target conditions matched with the service data from preset matching rules, and judging whether the target conditions contain state conditions or not;
if the state condition is contained, determining a target rule response queue mapped with the target condition based on a preset state machine mode, and executing response operation in the target rule response queue;
and returning an execution result corresponding to the service data.
2. The traffic data processing method according to claim 1, wherein said step of determining a target rule response queue mapped with said target condition based on a preset state machine mode if a state condition is included, comprises:
if the verification method comprises a plurality of state conditions, determining whether the plurality of state conditions all complete a verification process based on a preset condition rule based on a preset state machine mode;
if all the conditions are completed, determining whether the non-state conditions contained in the target conditions completely complete the verification process of the preset condition rule;
and if the target condition is completely finished, determining a target rule response queue based on the response operation mapped by the target condition.
3. The traffic data processing method according to claim 2, wherein after said step of judging whether or not the state condition is included in the target condition, said method further comprises:
if the state condition is not contained, determining whether the target condition completely completes a verification process based on a preset condition rule based on a preset common mode, wherein the target condition has a plurality of target conditions;
and if the target condition is completely finished, determining a target rule response queue based on the response operation mapped by the target condition.
4. The traffic data processing method according to claim 2, wherein the preset condition rule includes a state condition rule, and if a plurality of state conditions are included, based on a preset state machine mode, after determining whether the plurality of state conditions have all completed the steps of the verification process based on the preset condition rule, the method further includes:
if not, determining whether the state conditions of the incomplete verification process accord with the state condition rules;
and if yes, obtaining a first rule response queue based on the response operation mapped by the state condition meeting the state condition rule, and inserting the first rule response queue into the target rule response queue.
5. The traffic data processing method according to claim 3, wherein the preset condition rule further includes an environmental condition rule, and the method further includes, if the state condition is not included, after determining whether the target condition has all completed the step of the verification process based on the preset condition rule based on a preset normal mode:
if not, determining whether the non-state condition of the incomplete verification process accords with the environmental condition rule;
and if yes, obtaining a second rule response queue based on the response operation mapped by the non-state condition meeting the environmental condition rule, and inserting the second rule response queue into the target rule response queue.
6. The service data processing method according to claim 1, wherein after the step of returning the execution result corresponding to the service data, the method further comprises:
and if the service data is detected to be changed, a third rule response queue is redetermined and obtained based on the changed service data, and the response operation in the third rule response queue is executed.
7. The service data processing method according to claim 1, wherein after the step of returning the execution result corresponding to the service data, the method further comprises:
and determining whether to perform persistence processing or not based on the type of the execution result of the service data.
8. A traffic data processing apparatus, the apparatus comprising:
the data receiving module is used for receiving service data;
the matching module is used for determining target conditions matched with the service data from preset matching rules and judging whether the target conditions contain state conditions or not;
the response module is used for determining a target rule response queue mapped with the target condition based on a preset state machine mode if the state condition is contained, and executing response operation in the target rule response queue;
and the result return module is used for returning an execution result corresponding to the service data.
9. A traffic data processing apparatus, the apparatus comprising: memory, a processor and a service data processing program stored on the memory and executable on the processor, the service data processing program being configured to implement the steps of the service data processing method according to any one of claims 1 to 7.
10. A storage medium having stored thereon a service data processing program which, when executed by a processor, implements the steps of the service data processing method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211634619.9A CN116186107A (en) | 2022-12-19 | 2022-12-19 | Service data processing method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211634619.9A CN116186107A (en) | 2022-12-19 | 2022-12-19 | Service data processing method, device, equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116186107A true CN116186107A (en) | 2023-05-30 |
Family
ID=86431795
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211634619.9A Pending CN116186107A (en) | 2022-12-19 | 2022-12-19 | Service data processing method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116186107A (en) |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2006025062A2 (en) * | 2004-09-02 | 2006-03-09 | Logiccon Design Automation Ltd. | Method and system for designing a structural level description of an electronic circuit |
| CN1855931A (en) * | 2005-04-20 | 2006-11-01 | 华为技术有限公司 | Method for processing upload event of media gateway in network of the latter generation |
| US20150160988A1 (en) * | 2012-06-23 | 2015-06-11 | Guilherme Scomparim | Computing device for state transitions of recursive state machines and a computer-implemented method for the definition, design and deployment of domain recursive state machines for computing devices of that type |
| CN105844422A (en) * | 2016-04-01 | 2016-08-10 | 阿里巴巴集团控股有限公司 | Business flow execution method and device |
| CN110580155A (en) * | 2019-07-31 | 2019-12-17 | 苏宁云计算有限公司 | Implementation method and device of state machine engine, computer equipment and storage medium |
| CN111144982A (en) * | 2019-12-20 | 2020-05-12 | 网联清算有限公司 | Order state transition method and device, electronic equipment and storage medium |
| CN113590454A (en) * | 2021-02-03 | 2021-11-02 | 腾讯科技（深圳）有限公司 | Test method, test device, computer equipment and storage medium |
| CN114418319A (en) * | 2021-12-24 | 2022-04-29 | 浙江时空道宇科技有限公司 | Linkage processing method, device, equipment and storage medium |
| CN114490134A (en) * | 2022-02-11 | 2022-05-13 | Tcl通讯科技（成都）有限公司 | Event processing method, system, device, computer equipment and storage medium |
-
2022
- 2022-12-19 CN CN202211634619.9A patent/CN116186107A/en active Pending
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2006025062A2 (en) * | 2004-09-02 | 2006-03-09 | Logiccon Design Automation Ltd. | Method and system for designing a structural level description of an electronic circuit |
| CN1855931A (en) * | 2005-04-20 | 2006-11-01 | 华为技术有限公司 | Method for processing upload event of media gateway in network of the latter generation |
| US20150160988A1 (en) * | 2012-06-23 | 2015-06-11 | Guilherme Scomparim | Computing device for state transitions of recursive state machines and a computer-implemented method for the definition, design and deployment of domain recursive state machines for computing devices of that type |
| CN105844422A (en) * | 2016-04-01 | 2016-08-10 | 阿里巴巴集团控股有限公司 | Business flow execution method and device |
| CN110580155A (en) * | 2019-07-31 | 2019-12-17 | 苏宁云计算有限公司 | Implementation method and device of state machine engine, computer equipment and storage medium |
| CN111144982A (en) * | 2019-12-20 | 2020-05-12 | 网联清算有限公司 | Order state transition method and device, electronic equipment and storage medium |
| CN113590454A (en) * | 2021-02-03 | 2021-11-02 | 腾讯科技（深圳）有限公司 | Test method, test device, computer equipment and storage medium |
| CN114418319A (en) * | 2021-12-24 | 2022-04-29 | 浙江时空道宇科技有限公司 | Linkage processing method, device, equipment and storage medium |
| CN114490134A (en) * | 2022-02-11 | 2022-05-13 | Tcl通讯科技（成都）有限公司 | Event processing method, system, device, computer equipment and storage medium |
Non-Patent Citations (2)
| Title |
|---|
| JEHN-RUEY JIANG等: ""Short Survey on Physical Layer Authentication by Machine-Learning for 5G-based Internet of Things"", 《2020 3RD IEEE INTERNATIONAL CONFERENCE ON KNOWLEDGE INNOVATION AND INVENTION (ICKII)》, 18 January 2021 (2021-01-18), pages 1 - 4 * |
| 袁军: ""大型多人在线角色扮演游戏人工智能的设计及优化"", 《中国优秀硕士学位论文全文数据库信息科技辑》, 15 June 2019 (2019-06-15), pages 140 - 40 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11847167B2 (en) | System and method for generation of chat bot system with integration elements augmenting natural language processing and native business rules | |
| US8108433B2 (en) | Dynamic extension fields for business objects | |
| US7941450B2 (en) | Software, devices and methods facilitating execution of server-side applications at mobile devices | |
| CA2598426C (en) | Facilitating mobile device awareness of the availability of new or updated server-side applications | |
| US8356274B2 (en) | System and methods to create a multi-tenancy software as a service application | |
| CN115485690A (en) | Batch technique for handling unbalanced training data of chat robots | |
| US7920852B2 (en) | Compression of data transmitted between server and mobile device | |
| CN110493067A (en) | A kind of method and device that API gateway service updates | |
| US20110302212A1 (en) | Systems and methods for analyzing operations in a multi-tenant database system environment | |
| US20090300063A1 (en) | Software, devices and methods facilitating execution of server-side applications at mobile devices | |
| US20100057771A1 (en) | Dynamic node extensions and extension fields for business objects | |
| CN110413288A (en) | Using dispositions method, device, server and storage medium | |
| US20080155523A1 (en) | System and method using transformation nodes with enhancement layers | |
| CN108776592B (en) | Page construction method, device, equipment and storage medium | |
| CN111784108A (en) | Modeling method and device for main data management platform | |
| CN116302448B (en) | Task scheduling method and system | |
| US20120179711A1 (en) | System and Method for Accessing a Database Including Data Abstraction Layer and Request Table Processing | |
| CN111522840B (en) | Label configuration method, device, equipment and computer readable storage medium | |
| CN112860308A (en) | Configuration method of interface definition, service processing method, server and storage medium | |
| CN111008015B (en) | Micro front-end application framework based on front-end technology | |
| WO2021093672A1 (en) | Method for embedding external system, workflow system, device and computer readable storage medium | |
| CN116186107A (en) | Service data processing method, device, equipment and storage medium | |
| CN111722881B (en) | Resource expansion method, system and device of container cloud platform | |
| US11810022B2 (en) | Contact center call volume prediction | |
| US11188548B2 (en) | Profile data store automation via bots |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |