CN111724144A - Bank transaction workflow engine system - Google Patents
Bank transaction workflow engine system Download PDFInfo
- Publication number
- CN111724144A CN111724144A CN202010689534.5A CN202010689534A CN111724144A CN 111724144 A CN111724144 A CN 111724144A CN 202010689534 A CN202010689534 A CN 202010689534A CN 111724144 A CN111724144 A CN 111724144A
- Authority
- CN
- China
- Prior art keywords
- workflow
- flow
- transaction
- nodes
- service
- 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.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/02—Banking, e.g. interest calculation or account maintenance
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Strategic Management (AREA)
- Human Resources & Organizations (AREA)
- General Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Marketing (AREA)
- Entrepreneurship & Innovation (AREA)
- Economics (AREA)
- Physics & Mathematics (AREA)
- Finance (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Technology Law (AREA)
- Data Mining & Analysis (AREA)
- Development Economics (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention discloses a bank transaction workflow engine system. The system comprises a transaction receiving unit, a workflow processor, a workflow node unit, a service realizing unit and a context object unit. The method is realized based on java and configuration files, does not depend on any third-party framework, is simple, light and strong in expandability, the configuration files are mainly used for compiling the service workflow, the flow management, the flow trend and the flow processing of the engine are realized by java, and the editing and acceptance under different scenes of a complex service system are fully met by combining the design of java adapters, factories, responsibility chains and other modes. And strict layering can be performed according to request receiving, workflow processing, basic service implementation and public component implementation, so that clear and clear structure and layering are ensured, and the readability and maintainability of codes are strong. After a transaction request is received, the workflow engine can be started by performing basic processing such as conversion, verification and the like on a request object.
Description
Technical Field
The invention relates to the technical field of bank transaction systems, in particular to a bank transaction workflow engine system.
Background
With the rapid development of the financial industry, online and offline financial scenes are more abundant, the user product experience is continuously improved, the functions of a bank back-end transaction system are gradually increased, the transaction scenes of credit loan, financing and cash withdrawal and the like related to financial services are increased besides the traditional authentication card binding, payment, transfer remittance, revocation and inquiry, and the processing of various service transaction processes becomes very tedious. At present, for most banks, a traditional transaction system combines business logic and processing flow, each business flow needs rigid judgment, the business logic and functional units are coupled deeply, and brand new business logic is generated when the business flow is changed, so that the system complexity is higher and higher along with the business development, the code maintainability is poorer and poorer, great risks and cost investment are brought in development, testing, operation and maintenance, a set of workflow engine for arranging the business flow, separating the business logic and realizing the process is needed, and the workflow engine is flexibly designed for processing various transaction scenes by taking the bank financial business requirements as the leading factor.
Aiming at the management of the process nodes and the connection control of the process, various types of workflow engine frameworks such as a jbpm workflow management system, an SWF distributed scheduling framework and the like exist in the current market, the products are often complex in system and function and much in external dependence, extra learning and use are needed when the products are integrated with an application system, and the products cannot be fully adapted to a bank transaction system, so that the transaction workflow engine under a complex scene in a bank is provided.
Disclosure of Invention
The invention aims to provide a bank transaction workflow engine system aiming at the defects in the prior art.
In order to achieve the above object, the present invention provides a bank transaction workflow engine system, comprising:
the transaction receiving unit is used for receiving a transaction request of a user and converting the transaction request into an internal transaction object through a message;
the workflow processor is used for initializing a flow set flowMap by loading a flow file when the application system is started and storing the flow set flowMap in a memory, receiving the internal transaction object and controlling the service trend according to the type of the internal transaction object and the workflow node of the flow file so as to generate and send a corresponding transaction request for the internal transaction object and enable all nodes in the flow file to execute circularly according to an expected process;
the workflow node unit is used for arranging workflow nodes of the flow files, including start nodes and end nodes, so as to specify the circulation and the trend of the workflow nodes and take charge of the realization of specific service nodes;
the business implementation unit is used for receiving the transaction request, completing specific business implementation according to the transaction request and generating a return result, and the return result is returned to the transaction receiving unit through the workflow node unit and the workflow processor in sequence;
and the context object unit is used for storing variable attributes such as a request object, a return object and a workflow node processing state during workflow operation, and is used as a flow container required by workflow node and service realization connection.
Furthermore, when the internal transaction object does not meet the expected flow trend, the workflow processor is also used for interrupting the workflow, and when the system is abnormal, the workflow processor controls the workflow to jump out for exception handling.
Furthermore, the workflow processor processes the nodes of the flow files through the command of the excel (), the nodes are taken as the nodes of the flow files, the nextnoes variable is specially responsible for the transmission of the flow, the service implementation class of the nodes is Component, the specific service logic is executed, and the workflow processor can be expanded.
Further, if the nextNodes is a single value, it is directly used as the nextNode, and if the nextNodes is a plurality of values, it uses executeStaus to obtain or expand the execution el expression.
Further, the flow file is a combined workflow, and a subFlow is opened through a subFlow variable.
Further, the workflow processor routes in a manner that a specified dimension is combined with a bean configuration.
Furthermore, the process file further comprises a thread pool asynchronous execution service component for processing the service which does not affect the main process, and the workflow nodes of the thread pool asynchronous execution service component are set to be asynchronously executed by the thread pool.
Further, after the transaction is overtime, the system registers a compensation process, simultaneously caches nodes, states and transaction request information of the workflow process, and after the compensation request is sent, the cache information can be obtained, context objects required by the workflow operation are assembled, and a workflow engine is started.
Has the advantages that: the method is realized based on java and configuration files, does not depend on any third-party framework, is simple, light and strong in expandability, the configuration files are mainly used for compiling business workflow, the flow management, the flow trend and the flow processing of an engine are realized by java, and the method and the system fully meet the requirements of arrangement and acceptance under different scenes of a complex business system, particularly financial and transaction systems, by combining the design of java adapters, factories, responsibility chains and other modes. On the design of a framework structure of an application system, strict layering can be performed according to request receiving, workflow processing, basic service implementation and public component implementation, the clear and clear layering of the structure is guaranteed, and the readability and maintainability of codes are high. After a business system receives a transaction request, a workflow engine can be started by generally performing basic processing such as conversion, verification and the like on a request object, and the workflow engine has many advantages in basic development and project construction, and specifically the following steps are performed:
development risks are reduced, developers can clearly design business requirements and achieve the business requirements through design, circulation, states and behaviors of workflows, coupling depths among different businesses are reduced, and business requirement iterative maintenance is convenient and fast.
And development efficiency is improved, developers only pay attention to business realization without paying attention to connection and control of the process, and meanwhile, public components can be directly used, and the business process is easy to design and rearrange, so that the development speed of the developers is higher, and the system maintenance is easier.
The process is managed in a unified mode, the business workflow is managed in a centralized mode through the process files, under the condition that the business process changes frequently, the fact that business implementation codes scatter in all places is not needed to be concerned, and nodes and circulation of the process are maintained easily.
The complexity of the system is reduced, the flow files are written in a light weight mode, the core architecture of the flow engine is simple and easy to understand, flexible expansion can be achieved according to the service implementation requirements, the workflow engine is responsible for running connection of the whole flow, the code structure of a service implementation layer is clearer, reusability is high, and the complexity of the application system is greatly reduced.
Drawings
FIG. 1 is a schematic diagram of the architecture of a bank transaction workflow engine system according to an embodiment of the invention;
FIG. 2 is a schematic workflow diagram of a bank transaction workflow engine system according to an embodiment of the invention;
FIG. 3 is a schematic workflow diagram of a combined workflow of an embodiment of the present invention.
Detailed Description
The present invention will be further illustrated with reference to the accompanying drawings and specific examples, which are carried out on the premise of the technical solution of the present invention, and it should be understood that these examples are only for illustrating the present invention and are not intended to limit the scope of the present invention.
As shown in fig. 1 and 2, an embodiment of the present invention provides a bank transaction workflow engine system, which includes a transaction receiving unit 1, a workflow processor (flowexecutive) 2, a workflow node unit 3, a service implementation unit (Component)4, and a Context unit (Context) 5.
The transaction receiving unit 1 is configured to receive a transaction request of a user, and convert the transaction request into an internal transaction object through a message, where the internal transaction object refers to data in a format set inside a system.
The workflow processor 2 is configured to initialize the flow set flowMap by loading the flow file when the application system is started, and store the flow set flowMap in the memory, and the workflow processor 2 is further configured to receive the internal transaction object, and control the service trend according to the type of the internal transaction object and the workflow node of the flow file, so as to generate and send out a corresponding transaction request for the internal transaction object, and enable all nodes in the flow file to execute circularly according to an expected process. The workflow processor 2 is also used for taking charge of engine start of the workflow.
The workflow node unit 3 is used to arrange workflow nodes of the process file, including start to end nodes, to specify the flow and direction of the workflow nodes, and to implement specific service nodes. Nodes can be added or deleted during service process maintenance, deep coupling in traditional mode service realization is removed, and other service processes are not influenced in function. A workflow content declaration comprises a name attribute and a flow node set, core content is written for the flow node set, and a spring bean declaration can be used in a creating mode, and a flow file can be customized and an xml format is used.
The service implementation unit 4 is configured to receive the transaction request, complete specific service implementation according to the transaction request, and generate a return result, where the return result is returned to the transaction receiving unit 1 through the workflow node unit 3 and the workflow processor 2 in sequence. The service implementation unit 4 is divided into common components and service components according to the service scene of the application system, for example, there are common components such as account verification, wind control processing, rights and interests processing, and also there are single service components for payment and return of goods in the transaction system. The business component is to be distinguished from the basic interface service class in the structural design, the business component plays a role of business implementation in the workflow engine and can depend on the basic layer interface service, the data layer service and the like, the design of the business component needs to consider the universality and the complexity and is not too tedious, otherwise, the workflow is huge.
The context object unit 5 is configured to store variable attributes such as a request object, a return object, and a workflow node processing state during workflow operation, and serve as a flow container required for implementing connection between a workflow node and a service. Specifically, the object can be set as an interface or an abstract class, which is convenient for service expansion and use, such as service scenes of authentication, personal account transfer, revolution account checking, remittance and the like in a bank transaction system, and the service scenes are different service objects respectively. The service implementation class execution method parameter of the workflow node is a Context object, and the object transmits variables and parameters required by each service implementation. In the workflow engine system, Context completes the workflow nodes and the flow containers needed by service realization connection.
When the internal transaction object does not meet the expected condition of the process trend, the workflow processor 2 is also used for interrupting the workflow, and when the system is abnormal, the workflow processor 2 controls the workflow to jump out for abnormal processing.
The workflow processor 2 processes the flow file nodes through the excete () instruction, defaults to execute from the begin node and finish the flow to the end node, and may also specify to start from a certain node, and after the current node finishes executing, if there is a next node, then execute recursively, and complete the circulation of the processing chain. A Node in a workflow architecture belongs to a substep in a workflow engine, is similar to a link in a workshop pipeline, and is responsible for realizing specific service nodes, such as message inspection, account verification, order warehousing, accounting, transaction sending and the like of a transaction system. The Node is used as a Node in the flow file, the nextNodes variable is specially responsible for the transmission of the flow, the service implementation class of the Node is Component, the specific service logic is executed, and the expansion is realized.
If the above nextNodes has one value, it is directly used as nextNode, and if the above nextNodes has multiple values, the execute eL expression is obtained or extended by using execute status. Because the Flow and the Node of the mode are both self-defined and are not restricted by the bean attribute of spring, more modes can be expanded, such as combination workflow, abnormal Node execution and other scenes.
As shown in fig. 3, because there are many business scenarios and many similar parts in different scenarios, a combined workflow concept is added to the design of the workflow, and the flow document in the embodiment of the present invention is a combined workflow and opens the child workflow through a subFlow variable. For example, a payment transaction workflow in the transaction system is split into a workflow a and a workflow b, nodes of the workflow a are public service components such as anti-duplication, account verification, rights and interests and wind control, and nodes of the workflow b are used for processing such as warehousing, sending and accounting of the payment transaction, so that the workflow a can be used by service processes such as correction and return, coding repetition is reduced, and system maintainability is improved. The other mode is a nested mode, that is, the service implementation of a certain node in the workflow can be a sub-workflow mode, such as transaction transmission in a payment workflow, and can be designed as an independent workflow due to differences of downstream channel assembly messages, communication modes, communication processes, result control and the like.
After receiving a service processing request, an application system determines a workflow according to dimensions such as an account, a service type, a channel and the like, for a complex service system, a rule engine is generally adopted to realize workflow routing, the workflow routing can be simply and directly realized by hard coding, and for convenience of maintenance and expansion, a mode of combining specified dimensions with bean configuration can be used for routing.
Usually, workflow designs are processed serially, that is, a subsequent link can be started after one link is completed, but in the field of software development, a back-end application system needs to deal with a performance bottleneck when high concurrent requests exist, so that asynchronous execution of workflow nodes is a common scenario for many business systems. Therefore, the flow file of the embodiment of the present invention further includes a thread pool asynchronous execution service component, where the thread pool asynchronous execution service component is used to process a service that does not affect a main flow, and a workflow node of the thread pool asynchronous execution service component is set to be executed asynchronously by the thread pool. Such as notification of transaction results, big data push.
When the workflow is used, the normal service scenes are all completed by a whole process from a starting node to an ending node, but the normal service scenes need to be started from the middle of the workflow under certain specific scenes, and the requirement can be met after the core architecture of the workflow is known. If the transaction is overtime, the system registers a compensation process, simultaneously caches nodes, states and transaction request information of the workflow process, and after the compensation request is sent, the cached information can be obtained, context objects required by the workflow operation are assembled, and a workflow engine is started, so that the workflow engine is perfectly combined with the flow during the transaction.
The specific implementation mode of the invention is as follows:
1. the process Node realizes the Node type:
2. flow class Flow:
3. flow engine processor flowexecutive:
4. data object class Context of flow stream:
5. service implementation type Component:
6. workflow content case:
the workflow node set is maintained by the map of the spring bean, id is the identification of the workflow, and the circulation of the node is designated at the same time.
② self-defining flow file
The customized workflow compiling method is based on the xml nodes, is more convenient in defining the node set, has stronger expansibility, can support el expressions, but needs to be independently realized in loading and analyzing the contents of the workflow, is suitable for the workflow circulation requirement of a little bit of complexity, and does not depend on any other framework.
The foregoing is only a preferred embodiment of the present invention, and it should be noted that other parts not specifically described are within the prior art or common general knowledge to those of ordinary skill in the art. Without departing from the principle of the invention, several improvements and modifications can be made, and these improvements and modifications should also be construed as the scope of the invention.
Claims (8)
1. A banking transaction workflow engine system comprising:
the transaction receiving unit is used for receiving a transaction request of a user and converting the transaction request into an internal transaction object through a message;
the workflow processor is used for initializing a flow set flowMap by loading a flow file when the application system is started and storing the flow set flowMap in a memory, receiving the internal transaction object and controlling the service trend according to the type of the internal transaction object and the workflow node of the flow file so as to generate and send a corresponding transaction request for the internal transaction object and enable all nodes in the flow file to execute circularly according to an expected process;
the workflow node unit is used for arranging workflow nodes of the flow files, including start nodes and end nodes, so as to specify the circulation and the trend of the workflow nodes and take charge of the realization of specific service nodes;
the business implementation unit is used for receiving the transaction request, completing specific business implementation according to the transaction request and generating a return result, and the return result is returned to the transaction receiving unit through the workflow node unit and the workflow processor in sequence;
and the context object unit is used for storing variable attributes such as a request object, a return object and a workflow node processing state during workflow operation, and is used as a flow container required by workflow node and service realization connection.
2. The system of claim 1, wherein the workflow processor is further configured to interrupt the workflow when the internal transaction object does not meet the expected trend of the process, and when the system is abnormal, the workflow processor controls to jump out the workflow for exception handling.
3. The system of claim 1, wherein the workflow processor processes nodes of the flow document through an explicit () instruction, the flow document takes nodes as nodes, nextNodes variables are specially responsible for the transmission of the flow, the service implementation class of the nodes is Component, and the specific service logic is executed and can be extended.
4. The system of claim 3, wherein if said nextNodes is one value, then directly as nextNodes, if said nextNodes is multiple values, then use executeStatus to obtain or extend the execution el expression.
5. The system of claim 3, wherein the flow document is a combined workflow and opens a sub-workflow through a subFlow variable.
6. The system of claim 1, wherein the workflow processor routes in a manner that a specified dimension is combined with a bean configuration.
7. The system of claim 1, wherein the flow document further comprises a thread pool asynchronous execution business component for processing business that does not affect the main flow, the workflow nodes of the thread pool asynchronous execution business component being configured for thread pool asynchronous execution.
8. The system of claim 1, wherein after the transaction is overtime, the system registers a compensation process, and simultaneously caches the node, state and transaction request information of the workflow process, and after the compensation request is sent, the system can obtain the cached information, assemble the context object required by the workflow operation, and start the workflow engine.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010689534.5A CN111724144B (en) | 2020-07-17 | 2020-07-17 | Bank transaction workflow engine system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010689534.5A CN111724144B (en) | 2020-07-17 | 2020-07-17 | Bank transaction workflow engine system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111724144A true CN111724144A (en) | 2020-09-29 |
| CN111724144B CN111724144B (en) | 2022-06-28 |
Family
ID=72572667
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010689534.5A Active CN111724144B (en) | 2020-07-17 | 2020-07-17 | Bank transaction workflow engine system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111724144B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112866268A (en) * | 2021-01-29 | 2021-05-28 | 中国工商银行股份有限公司 | Message processing method and system |
| CN113504955A (en) * | 2021-07-16 | 2021-10-15 | 航天中认软件测评科技（北京）有限责任公司 | BPMN-based aerospace workflow management system |
| CN114070719A (en) * | 2020-11-03 | 2022-02-18 | 北京市天元网络技术股份有限公司 | Alarm service processing method and system |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103279840A (en) * | 2013-06-08 | 2013-09-04 | 北京首钢自动化信息技术有限公司 | Workflow engine implement method based on dynamic language and event processing mechanism |
| CN108305010A (en) * | 2018-02-10 | 2018-07-20 | 西安精雕软件科技有限公司 | A kind of workflow engine system and its flow propulsion method cross-platform, across application |
| CN109741030A (en) * | 2018-12-28 | 2019-05-10 | 杭州当虹科技股份有限公司 | A kind of simple workflow engine and workflow executing method can customize configuration |
-
2020
- 2020-07-17 CN CN202010689534.5A patent/CN111724144B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103279840A (en) * | 2013-06-08 | 2013-09-04 | 北京首钢自动化信息技术有限公司 | Workflow engine implement method based on dynamic language and event processing mechanism |
| CN108305010A (en) * | 2018-02-10 | 2018-07-20 | 西安精雕软件科技有限公司 | A kind of workflow engine system and its flow propulsion method cross-platform, across application |
| CN109741030A (en) * | 2018-12-28 | 2019-05-10 | 杭州当虹科技股份有限公司 | A kind of simple workflow engine and workflow executing method can customize configuration |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114070719A (en) * | 2020-11-03 | 2022-02-18 | 北京市天元网络技术股份有限公司 | Alarm service processing method and system |
| CN114070719B (en) * | 2020-11-03 | 2024-03-29 | 北京市天元网络技术股份有限公司 | Alarm service processing method and system |
| CN112866268A (en) * | 2021-01-29 | 2021-05-28 | 中国工商银行股份有限公司 | Message processing method and system |
| CN113504955A (en) * | 2021-07-16 | 2021-10-15 | 航天中认软件测评科技（北京）有限责任公司 | BPMN-based aerospace workflow management system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111724144B (en) | 2022-06-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111724144B (en) | Bank transaction workflow engine system | |
| US11941381B2 (en) | Method for compiling from a high-level scripting language to a blockchain native scripting language | |
| US20080065994A1 (en) | Systems and methods for adapting service interface behaviors | |
| MX2008011914A (en) | Abstract execution model for a continuation-based meta-runtime. | |
| CN103425462A (en) | Method and device for workflow data persistence | |
| CN102799962A (en) | Configuration type business flow system and realization method thereof | |
| JP2009532758A (en) | A framework for modeling continuations in a workflow | |
| Cao et al. | Flashot: a snapshot of flash loan attack on DeFi ecosystem | |
| US20080163269A1 (en) | Remote procedure call system, remote procedure call method, program for implementing remote procedure call system | |
| CN104021452A (en) | Method for integrating various service systems at cloud computing server side | |
| CN103019874A (en) | Method and device for realizing exception handling based on data synchronization | |
| Oh et al. | Standards-based semantic integration of manufacturing information: Past, present, and future | |
| CN111984447B (en) | Registration compensation system and method in overtime or abnormal situation of bank transaction | |
| CN107679140B (en) | Document handling method and system | |
| US20150312107A1 (en) | Composition of Services | |
| CN115022312A (en) | Method and device for realizing multiple intelligent contract engines, electronic equipment and storage medium | |
| Dong et al. | A blockchain-based decentralized booking system | |
| Norta et al. | A Public, Blockchain-based distributed smart-contract platform enabling mobile lite wallets using a proof-of-stake consensus algorithm | |
| EP2577497A2 (en) | Method and system for disintegrating an xml document for high degree of parallelism | |
| Xu et al. | A petri net-based method for data validation of web services composition | |
| CN102203756B (en) | Client terminal device, server unit and framing program used in information processing system | |
| Li et al. | Mediator: A component-based modeling language for concurrent and distributed systems | |
| Lukichev et al. | Using UML-based rules for web services modeling | |
| CN111813413B (en) | Method for automatically generating YAML file | |
| CN109741176B (en) | Distributed service scheduling system based on internet financial scene |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |