CN116542623A

CN116542623A - Business constraint relation management and control method and business relation management engine

Info

Publication number: CN116542623A
Application number: CN202310444174.6A
Authority: CN
Inventors: 商大磊; 张锦超; 杨钊; 董立华; 佘飞宇; 崔政; 余莎莎; 王朝阳; 刘承亮; 朱韦桥; 潘立海; 王日谭; 郝伟俊; 于立凯; 王婷; 赵毅; 刘新; 任柯苇; 支宇
Original assignee: Institute of Computing Technologies of CARS; Beijing Jingwei Information Technology Co Ltd
Current assignee: Institute of Computing Technologies of CARS; Beijing Jingwei Information Technology Co Ltd
Priority date: 2023-04-21
Filing date: 2023-04-21
Publication date: 2023-08-04

Abstract

The application provides a business constraint relation management and control method and a business relation management engine, wherein the method comprises the following steps: in an environment independent of each service system, acquiring service flow restriction relation control results of a target service initiated by a current request of a target service system according to service flow restriction relation data prestored in a local area, wherein the service flow restriction relation data is edited by an authorized user from a visualization module; if the control result shows that the target service does not have a restriction relation with other services and the current self, a notification message is sent out so that the target service system initiates the target service after the service verification of the target service is passed. The method and the system can effectively realize centralized control of the business constraint relation of a plurality of business systems, and can effectively improve the flexibility, reliability, comprehensiveness and efficiency of the control of the business constraint relation, and further can effectively improve the operation reliability and business processing efficiency of each business system.

Description

Business constraint relation management and control method and business relation management engine

Technical Field

The present disclosure relates to the field of data processing technologies, and in particular, to a business constraint relationship management and control method and a business relationship management engine.

Background

The user of the business system needs to change the existing data content, data state and the like to achieve a certain goal, the change is completed through the fixed execution process of the system, and the whole process from the initiation to the completion is called a business process. The explicit identifier that a certain execution step is reached or completed in the process from initiation to completion of a business process may be referred to as a business state. In a user management system such as vendor management, personnel management and the like, various business processes, such as enterprise residence management, enterprise change management, enterprise protocol management, enterprise business scope management and the like, are designed for a system user (enterprise or individual) according to the requirements of business scenes and relations, and part of business has one sub-process (state) which is realized by submitting forms for many times. Similar to the concurrency scene in the database transaction management, when different business processes are concurrent, because the reading and writing of user basic data and business data are involved, unreasonable constraint control is not provided, and the unreasonable reading, dirty reading and dirty writing of the business data can also occur. Therefore, a certain constraint relationship needs to exist between these business processes.

Currently, in the system design, service data is directly searched in the system through a service interface, and the service state is judged to check whether the in-transit service exists. However, with the increasing of service functions, the constraint mutual exclusion requirement of the system on the service flows is higher and higher, and whether other in-transit services exist is directly searched through the service interface, so that the research difficulty and the application performance are not preferable, the comprehensiveness and the effectiveness of service constraint relation query cannot be ensured, and the efficiency and the setting flexibility of service constraint relation query can be influenced.

Disclosure of Invention

In view of this, embodiments of the present application provide a business constraint relationship management method and a business relationship management engine to obviate or mitigate one or more disadvantages in the prior art.

One aspect of the present application provides a method for controlling a business constraint relationship, including:

in an environment independent of each service system, acquiring service flow restriction relation control results of a target service initiated by a current request of a target service system according to service flow restriction relation data prestored in a local area, wherein the service flow restriction relation data is edited by an authorized user from a visualization module;

if the service flow restriction relation management and control result shows that the target service does not have restriction relation with other services, a corresponding notification message is sent to the target service system based on a preset interface so that the target service system initiates the target service after service verification is passed on the target service.

In some embodiments of the present application, further comprising:

acquiring a service state constraint relation management and control result of a target service system which currently requests service state circulation according to service state constraint relation data prestored in a local, wherein the service state constraint relation data is edited by an authorized user from a visualization module;

If the service state constraint relation management and control result shows that the current self state of the target service and the states of the current and other services of the target service do not have constraint relation, a corresponding notification message is sent to the target service system based on a preset interface so that the target service system carries out state circulation on the target service after the service verification of the target service is passed.

In some embodiments of the present application, further comprising:

if the business process restriction relation management and control result shows that the target business currently has restriction relation with the target business and/or other businesses, acquiring a current business process restriction record of the target business from business process record data prestored in a local place; if the service flow restriction record shows that the target service is currently in an unrestricted state, a corresponding notification message is sent to the target service system based on a preset interface so that the target service system initiates the target service after service verification is carried out on the target service;

and if the service state constraint relation management and control result shows that the state of the target service is present and/or the state between the target service and other services is in constraint relation, acquiring a service state constraint record of the target service present from service state record data prestored in the local, and if the service state constraint record shows that the state of the target service is not present in a constraint state, sending a corresponding notification message to the target service system based on a preset interface so that the target service system carries out state circulation on the target service after the service verification of the target service is passed.

In some embodiments of the present application, further comprising:

if the business process restriction record shows that the target business is currently in a restricted state, a corresponding notification message is sent to the target business system based on a preset interface so that the target business system sends a failure notification message for the initiation of the target business;

if the service state restriction record shows that the state of the target service is currently in a restricted state, a corresponding notification message is sent to the target service system based on a preset interface so that the target service system sends a state circulation failure notification message aiming at the target service.

In some embodiments of the present application, further comprising:

judging whether the target service system executes the initiating process aiming at the target service successfully or not, if so, newly adding the service flow and state information aiming at the target service in the service flow record data prestored in the local;

judging whether the state flow process of the target service system aiming at the target service is successfully executed, if so, newly adding service state information aiming at the target service in service state record data prestored in the local.

In some embodiments of the present application, before the obtaining the service flow constraint relationship management result of the target service initiated by the current request of the target service system, the method further includes:

receiving an initiating request of a target service system aiming at a target service currently based on a preset interface;

obtaining a user token occupation record corresponding to the initiation request from the user token occupation record data corresponding to each user unique identifier currently stored in advance according to the user unique identifier corresponding to the initiation request;

if the user token occupation record is empty, newly adding initial user token occupation record data corresponding to the initiation request and used for displaying that the user token corresponding to the initiation request is not occupied currently in the user token occupation record data, and acquiring a unique service identifier of the target service for inquiring service flow restriction relation data;

if the user token occupation record shows that the user token is not occupied currently, acquiring a unique service identifier of the target service for inquiring service flow restriction relation data;

and if the user token occupation record shows that the user token is currently occupied, a corresponding notification message is sent to the target service system based on a preset interface so that the target service system sends out a failure initiation notification message aiming at the target service.

In some embodiments of the present application, before the obtaining the service state constraint relation management result of the target service that the target service system currently requests the service state flow, the method further includes:

receiving a service state circulation request of a target service system aiming at a target service at present based on a preset interface;

obtaining a user token occupation record corresponding to the service state circulation request from user token occupation record data corresponding to each user unique identifier currently stored in advance according to the user unique identifier corresponding to the service state circulation request;

if the user token occupation record is empty, newly adding initial user token occupation record data which corresponds to the service state circulation request and is used for displaying that the user token corresponding to the service state circulation request is not occupied currently in the user token occupation record data, and acquiring the unique identification of the target service and the state to be circulated thereof for inquiring service state restriction relation data;

if the user token occupation record shows that the user token is not occupied currently, acquiring the unique identifier of the target service and the state to be circulated thereof for inquiring service state constraint relation data;

If the user token occupation record shows that the user token is currently occupied, a corresponding notification message is sent to the target service system based on a preset interface so that the target service system sends a service state circulation failure notification message aiming at the target service.

A second aspect of the present application provides a business relationship management engine comprising:

the business process editing and inquiring module is used for acquiring business process constraint relation management and control results of a target business initiated by a current request of a target business system according to pre-stored business process constraint relation data in an environment independent of each business system, wherein the business process constraint relation data is edited by an authorized user from the visualization module;

and the business process control module is used for sending a corresponding notification message to the target business system based on a preset interface so that the target business system initiates the target business after the business verification of the target business is passed if the business process restriction relation control result shows that the target business does not have restriction relation between the current self and the current and other businesses of the target business.

In a third aspect, the present application provides an electronic device, including a memory, a processor, and a computer program stored in the memory and capable of running on the processor, where the processor implements the service constraint relationship management method when executing the computer program.

A fourth aspect of the present application provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the business constraint relationship management method.

According to the business constraint relation management and control method, business process constraint relation management and control results of a target business initiated by a current request of a target business system are obtained according to business process constraint relation data prestored in a local environment independent of each business system, wherein the business process constraint relation data are edited by an authorized user from a visualization module; if the service flow restriction relation management and control result shows that the target service does not have restriction relation between the target service and other services, a corresponding notification message is sent to the target service system based on a preset interface so that the target service system initiates the target service after the service verification of the target service is passed, thereby effectively realizing centralized management and control of service restriction relation of a plurality of service systems, effectively improving flexibility, reliability, comprehensiveness and efficiency of service restriction relation management and control, and further effectively improving operation reliability and service processing efficiency of each service system.

Additional advantages, objects, and features of the application will be set forth in part in the description which follows and in part will become apparent to those having ordinary skill in the art upon examination of the following or may be learned from practice of the application. The objectives and other advantages of the application may be realized and attained by the structure particularly pointed out in the written description and drawings.

It will be appreciated by those skilled in the art that the objects and advantages that can be achieved with the present application are not limited to the above-detailed description, and that the above and other objects that can be achieved with the present application will be more clearly understood from the following detailed description.

Drawings

The accompanying drawings are included to provide a further understanding of the application, and are incorporated in and constitute a part of this application. The components in the figures are not necessarily to scale, emphasis instead being placed upon illustrating the principles of the application. Corresponding parts in the drawings may be exaggerated, i.e. made larger relative to other parts in an exemplary device actually manufactured according to the present application, for convenience in showing and describing some parts of the present application. In the drawings:

fig. 1 is a schematic flow chart of a first flow control of a service flow in a service constraint relation management and control method according to an embodiment of the present application.

Fig. 2 is a schematic flow chart of a first flow of service state constraint control in a service constraint relation control method according to an embodiment of the present application.

Fig. 3 is a second flow chart of the business flow constraint control in the business constraint relation control method in an embodiment of the present application.

Fig. 4 is a schematic diagram of a second flow of service state constraint control in the service constraint relation control method in an embodiment of the present application.

Fig. 5 is a schematic diagram of a first architecture of a business relationship management engine according to another embodiment of the present application.

Fig. 6 is a schematic diagram of a second architecture of a business relationship management engine according to another embodiment of the present application.

Fig. 7 is a schematic diagram of the overall architecture of the business relationship management engine in the application example of the present application.

Fig. 8 is an exemplary schematic diagram of business process relationship maintenance content in an application example of the present application.

Fig. 9 is a schematic diagram of a business process information collection framework in an application example of the application.

Fig. 10 is a flow chart of business flow constraint control in an application example of the present application.

Fig. 11 is a detailed flow diagram of a flow constraint of service initiation in an application example of the present application.

Fig. 12 is a detailed flow chart of service status constraint in an application example of the present application.

Detailed Description

For the purposes of making the objects, technical solutions and advantages of the present application more apparent, the present application will be described in further detail with reference to the embodiments and the accompanying drawings. The exemplary embodiments of the present application and their descriptions are used herein to explain the present application, but are not intended to be limiting of the present application.

It should be noted here that, in order to avoid obscuring the present application due to unnecessary details, only structures and/or processing steps closely related to the solution according to the present application are shown in the drawings, while other details not greatly related to the present application are omitted.

It should be emphasized that the term "comprises/comprising" when used herein is taken to specify the presence of stated features, elements, steps or components, but does not preclude the presence or addition of one or more other features, elements, steps or components.

It is also noted herein that the term "coupled" may refer to not only a direct connection, but also an indirect connection in which an intermediate is present, unless otherwise specified.

Hereinafter, embodiments of the present application will be described with reference to the drawings. In the drawings, the same reference numerals represent the same or similar components, or the same or similar steps.

In one or more embodiments of the present application, the user token refers to: the method is used for acquiring the authority of the service relation management engine check service by a single user service, and a queuing mechanism is adopted for calling the service relation check service by controlling a plurality of service processes of the single user through a user token in order to avoid dirty reading of service constraint relation data.

The method and the system consider that a general manageable business relation management engine is built outside a business module, and whether the business can be started or not can be identified only through a simple interface and high-efficiency judgment when a business flow is initiated.

For example, management systems such as a national iron store merchant auditing system serving as an admission system of a national iron store mainly provide supplier admission information submission auditing and subsequent information management services, and cover various business processes associated with suppliers, such as a supplier admission process, a supplier newly-added process, a supplier renewing process, a supplier trading process and the like, wherein the business processes are independent of each other, but business data are mutually coupled, and each business line in the system is decoupled through a business process control table, so that each business is mutually restricted, and only one in-transit business of the suppliers is ensured.

The business constraint relation management and control method and the business relation management engine mainly solve the problem of management of constraint relation among different businesses of a single user in a business management system, avoid errors or anomalies of reading and writing of main data of the business of the user in the process of concurrent execution or repeated execution of a plurality of independent business processes of the system, only pay attention to state transfer of the business processes in the process of execution, and can completely give the constraint relation with other business scenes to the business relation management engine for control, thereby greatly improving research and development efficiency and flexibility of the system.

The following examples are provided to illustrate the invention in more detail.

The embodiment of the application provides a service constraint relation management and control method, referring to fig. 1, the service constraint relation management and control method which can be executed by a service relation management engine specifically includes the following contents:

step 100: in an environment independent of each service system, according to the service flow restriction relation data prestored in the local, acquiring a service flow restriction relation control result of a target service initiated by a current request of a target service system, wherein the service flow restriction relation data is edited by an authorized user from a visualization module.

It is understood that the context independent of each business system refers to an independent third party where the business relationship management engine is not located within any business system.

In one or more embodiments of the present application, the service flow constraint relationship data is used to store a correspondence between the content of a service unique identifier of each service, constraint relationship data of each service, and constraint relationship data between each service and other services.

Step 200: if the service flow restriction relation management and control result shows that the target service does not have restriction relation with other services, a corresponding notification message is sent to the target service system based on a preset interface so that the target service system initiates the target service after service verification is passed on the target service.

In one or more embodiments of the present application, for example, a unique identifier (e.g., a service ID) of the target service may be extracted from an initiation request of the target service;

and searching business process constraint relation information corresponding to the target business in a preset business process relation table according to the unique identifier of the target business, wherein the business process constraint relation information comprises the unique identifier of the target business, unique identifiers (such as constraint business identifiers) of other businesses with constraint relation with the target business, exceptional states, corresponding relations between constraint states and recording states, and the recording states comprise two contents of effective or invalid.

As can be seen from the above description, the service constraint relation management and control method provided by the embodiment of the present application can effectively implement centralized management and control of service constraint relations of multiple service systems, and can effectively improve flexibility, reliability, comprehensiveness and efficiency of service constraint relation management and control, so that operational reliability and service processing efficiency of each service system can be effectively improved.

In order to further improve the comprehensiveness and effectiveness of the service constraint relation management and control, in the service constraint relation management and control method provided in the embodiment of the present application, referring to fig. 2, the service constraint relation management and control method further specifically includes the following contents:

step 300: and acquiring a service state constraint relation management and control result of a target service system which currently requests service state circulation according to the service state constraint relation data prestored in the local, wherein the service state constraint relation data is edited by an authorized user from a visualization module.

In one or more embodiments of the present application, the service state constraint relationship data is used to store a correspondence between the content of a service unique identifier of each service, constraint relationship data of each state itself currently, constraint relationship data between each state currently and other states, and so on.

Specifically, the function can maintain flow restriction relation for different services, including service ID, restriction state, exception state, etc.

Restriction state: the effective state representing the constraint service as the constraint condition is ALL by default, and when the constraint service has any non-final state service, the constraint is generated on the initiation service; the non-ALL scene takes the value of the intermediate state (non-final state) of the constraint service, when the constraint service is in the constraint state and the following state nodes, the constraint exists on the initiating service, and the exceptional state in the non-ALL scene is required to be NULL.

Exception status: representing the exceptional state of the constraint service as the constraint condition, defaulting NULL, and restricting the initiating service when the constraint service has any non-final state service; the non-NULL scene takes the value of the intermediate state (non-final state) of the constraint service, when representing the state node before the exception state of the constraint service, the constraint exists on the initiation service, and the constraint state in the non-NULL scene must be ALL.

The flow restriction relation of different services is presented as mutual restriction and pair occurrence, for example, service B has restriction on service A, service A also has restriction on service B, and when maintaining the restriction relation of B to A, the system can automatically add reverse restriction record.

Step 400: if the service state constraint relation management and control result shows that the current self state of the target service and the states of the current and other services of the target service do not have constraint relation, a corresponding notification message is sent to the target service system based on a preset interface so that the target service system carries out state circulation on the target service after the service verification of the target service is passed.

In order to further improve the comprehensiveness and effectiveness of the management and control of the service constraint relation, in the management and control method of the service constraint relation provided by the embodiment of the application, the management and control method of the service constraint relation further specifically comprises the following contents:

referring to fig. 3, step 210, which is performed after step 100: if the business process restriction relation management and control result shows that the target business currently has restriction relation with the target business and/or other businesses, acquiring a current business process restriction record of the target business from business process record data prestored in a local place; if the service flow restriction record shows that the target service is currently in an unrestricted state, a corresponding notification message is sent to the target service system based on a preset interface so that the target service system initiates the target service after service verification is carried out on the target service.

Referring to fig. 4, step 410, which is performed after step 300: and if the service state constraint relation management and control result shows that the state of the target service is present and/or the state between the target service and other services is in constraint relation, acquiring a service state constraint record of the target service present from service state record data prestored in the local, and if the service state constraint record shows that the state of the target service is not present in a constraint state, sending a corresponding notification message to the target service system based on a preset interface so that the target service system carries out state circulation on the target service after the service verification of the target service is passed.

referring to fig. 3, step 220, which is performed after step 100: if the business process restriction record shows that the target business is currently in a restricted state, a corresponding notification message is sent to the target business system based on a preset interface so that the target business system sends a failure notification message for the initiation of the target business.

Referring to fig. 4, step 420, which is performed after step 300: if the service state restriction record shows that the state of the target service is currently in a restricted state, a corresponding notification message is sent to the target service system based on a preset interface so that the target service system sends a state circulation failure notification message aiming at the target service.

In order to further improve the comprehensiveness and effectiveness of the service constraint relation management and control, in the service constraint relation management and control method provided in the embodiment of the present application, referring to fig. 3, after step 200 and step 210 in the service constraint relation management and control method, the following contents are specifically included:

step 230: judging whether the target service system executes the initiating process aiming at the target service successfully or not, if so, newly adding the service flow and state information aiming at the target service in the service flow record data prestored in the local.

Referring to fig. 4, after step 400 and step 410 in the service constraint relation management and control method, the following are specifically included:

step 430: judging whether the state flow process of the target service system aiming at the target service is successfully executed, if so, newly adding service state information aiming at the target service in service state record data prestored in the local.

In order to further improve the comprehensiveness and effectiveness of the service constraint relation management and control, in the service constraint relation management and control method provided in the embodiment of the present application, referring to fig. 3, before step 100 in the service constraint relation management and control method, the following specifically includes:

step 010: and receiving an initiating request of the target service system for the target service currently based on a preset interface.

Step 020: and acquiring the user token occupation record corresponding to the initiation request from the user token occupation record data corresponding to each user unique identifier currently stored in the local pre-storage according to the user unique identifier corresponding to the initiation request.

Step 031: if the user token occupation record is empty, the initial user token occupation record data which corresponds to the initiation request and is used for displaying that the user token corresponding to the initiation request is not occupied currently is newly added in the user token occupation record data, and the unique service identification of the target service is obtained for inquiring service flow restriction relation data.

Step 032: and if the user token occupation record shows that the user token is not occupied currently, acquiring a unique service identifier of the target service for inquiring service flow restriction relation data.

Step 033: and if the user token occupation record shows that the user token is currently occupied, a corresponding notification message is sent to the target service system based on a preset interface so that the target service system sends out a failure initiation notification message aiming at the target service.

In order to further improve the comprehensiveness and effectiveness of the service constraint relation management and control, in the service constraint relation management and control method provided in the embodiment of the present application, referring to fig. 4, before step 300 in the service constraint relation management and control method, the following specifically includes:

step 040: and receiving a service state circulation request of the target service system aiming at the target service at present based on a preset interface.

Step 050: and acquiring the user token occupation record corresponding to the service state circulation request from the user token occupation record data corresponding to each user unique identifier currently stored in advance according to the user unique identifier corresponding to the service state circulation request.

Step 061: and if the user token occupation record is empty, newly adding initial user token occupation record data which corresponds to the service state circulation request and is used for displaying that the user token corresponding to the service state circulation request is not occupied currently in the user token occupation record data, and acquiring the unique identification of the target service and the state to be circulated thereof for inquiring service state restriction relation data.

Step 062: and if the user token occupation record shows that the user token is not occupied currently, acquiring the unique identification of the target service and the state to be circulated thereof for inquiring service state constraint relation data.

Step 063: if the user token occupation record shows that the user token is currently occupied, a corresponding notification message is sent to the target service system based on a preset interface so that the target service system sends a service state circulation failure notification message aiming at the target service.

From the software aspect, the present application further provides a service relationship management engine for executing all or part of the service constraint relationship management method, referring to fig. 5, where the service relationship management engine specifically includes the following contents:

the business process editing and inquiring module 10 is configured to obtain, in an environment independent of each business system, a business process constraint relationship management and control result of a target business initiated by a current request of a target business system according to business process constraint relationship data prestored in a local area, where the business process constraint relationship data is edited by an authorized user from the visualization module;

And the business process management and control module 20 is configured to send a corresponding notification message to the target business system based on a preset interface if the business process constraint relationship management and control result shows that the target business does not have a constraint relationship between the current business and other business, so that the target business system initiates the target business after the business verification is performed on the target business.

The embodiment of the service relation management engine provided in the present application may be specifically used to execute the process flow of the embodiment of the service constraint relation management method in the above embodiment, and the functions thereof are not described herein again, and may refer to the detailed description of the embodiment of the service constraint relation management method.

The part of the business relation management engine for business constraint relation management can be executed in a server, and in another practical application situation, all operations can be completed in the client device. Specifically, the selection may be made according to the processing capability of the client device, and restrictions of the use scenario of the user. The present application is not limited in this regard. If all operations are completed in the client device, the client device may further include a processor, and a specific process of controlling the service restriction relationship.

The client device may have a communication module (i.e. a communication unit) and may be connected to a remote server in a communication manner, so as to implement data transmission with the server. The server may include a server on the side of the task scheduling center, and in other implementations may include a server of an intermediate platform, such as a server of a third party server platform having a communication link with the task scheduling center server. The server may include a single computer device, a server cluster formed by a plurality of servers, or a server structure of a distributed device.

Any suitable network protocol may be used for communication between the server and the client device, including those not yet developed at the filing date of this application. The network protocols may include, for example, TCP/IP protocol, UDP/IP protocol, HTTP protocol, HTTPS protocol, etc. Of course, the network protocol may also include, for example, RPC protocol (Remote Procedure Call Protocol ), REST protocol (Representational State Transfer, representational state transfer protocol), etc. used above the above-described protocol.

Referring to fig. 6, the business relationship management engine may further include the following:

The service state editing and querying module 30 is configured to obtain a service state constraint relationship management and control result of a target service that is currently requested to be circulated by a target service system according to service state constraint relationship data that is prestored locally, where the service state constraint relationship data is edited by an authorized user from the visualization module;

and the service state management and control module 40 is configured to send a corresponding notification message to the target service system based on a preset interface if the service state constraint relation management and control result indicates that the state of the target service is not in constraint relation with the states of the other services, so that the target service system performs state circulation on the target service after performing service verification on the target service.

As can be seen from the above description, the service relationship management engine provided in the embodiment of the present application can effectively implement centralized management and control of service restriction relationships for multiple service systems, and can effectively improve flexibility, reliability, comprehensiveness and efficiency of service restriction relationship management and control, so as to effectively improve operational reliability and service processing efficiency of each service system.

In order to further explain the scheme, the application also provides a specific application example for realizing the business constraint relation management and control method by using the business relation management engine.

(one) business relationship management engine overall architecture

Referring to fig. 7, in the overall architecture, the business relationship management engine is divided into basic resources, application services, and interface services.

The interface service is a way for the management engine to provide service to the outside, and mainly provides interfaces such as business process collection, business state collection, business process restriction verification, business state verification and the like.

The application service is the realization of the main business and application functions of the management engine, and comprises the functions of business flow management, business constraint relation management, flow information acquisition, state information acquisition, flow constraint control, state constraint control and the like.

The underlying resource is the underlying platform for information collection by the management engine to provide transport, exchange, storage, and computation. The system software and hardware infrastructure comprises facilities such as servers, storage devices and the like and management software (comprising virtualization software, an operating system, a database, middleware and the like) thereof.

(II) application scenario

1. Conditions of application

The business relation management engine is suitable for user management systems such as provider management, personnel management and the like with more parallel businesses, such as a provider access system, a CRM, a personnel system, a comprehensive service platform and the like. The system needs to be provided with a unique identifier of a user, a unique identifier of a service flow and a service serial number, and is realized through lightweight integrated transformation.

1. Applicable scene

The business relation management engine comprises three modules, namely business flow relation maintenance, business flow information acquisition and business flow restriction control.

The business process relation maintenance module maintains the constraint relation among different business processes through the front end interface, wherein the constraint relation comprises process constraint and state constraint, and the constraint of different businesses is mutually and pairwise, for example, after maintaining the constraint relation of business B to business A, the business A automatically generates constraint to business B.

Business process relationship maintenance is illustrated in fig. 8, for example.

The service relation management engine core function comprises two parts, namely information management and service control. The information management is operated through a front-end page, and an operator is usually a system administrator and comprises maintenance of business process information, business state mapping information, business process relations and business state relations; the business control is realized by opening interface butt joint for business service, including business flow restriction control and business state restriction control.

Referring to fig. 9, the business process information acquisition module mainly collects information of initiation, state, end and the like of a certain business process of a single user through an integrated interface.

Referring to fig. 10, business process constraint control includes process constraint and state constraint control. Judging whether other on-road services restricting the service initiation exist or not by checking the service flow relation and the service flow record information; and judging whether other in-transit services restricting the service state circulation exist or not by checking the service state relation and the service flow record information.

(III) data Structure

Depending on the application architecture, the business relationship management engine may contain the following main table structures:

(1) The business process may include fields shown in table 1, and specific examples may be referred to as examples of the contents of the business process information table described in table 6 below.

TABLE 1 fields of the business process information table

Field name	Annotating
		id	Main key id
business_id	Service id (Global unique identifier of service system and management engine)
		business_name	Service name
business_system	System or service to which business belongs
		status	Status (whether or not it is valid)
operator	Operator
		create_time	Creation time
update_time	Update time

(2) The business_status table may include fields as shown in table 2, wherein specific examples of the content corresponding to part of the fields may be referred to as examples of the content of the business state mapping table as shown in table 8.

Table 2-fields of the service state mapping table

/>

(3) The business_relation table may include fields as shown in table 3, wherein specific examples of the content corresponding to some fields may be referred to as examples of the business flow self constraint relation table described in table 7 and examples of the constraint relation table between business flows described in table 9.

TABLE 3 Business Process relation Table

/>

(4) The business state relation table may include fields as shown in table 4, where specific examples of the content corresponding to part of the fields may be referred to as examples of the content of the business state relation table as shown in table 10 below.

TABLE 4 Business State relation Table

(5) The business record table may include fields as shown in table 5, where specific examples of the content corresponding to some of the fields may be referred to as examples of the content of the business record table as shown in table 12 below.

TABLE 5 business process record table

/>

(IV) description of the functionality

(1) Business process information management

When a business system adds a business process, a system administrator or a role designated with high authority maintains a business process information table through a front-end interface, as shown in table 6, and comprises: service name, service ID, service status, etc. The service flow ID is a unique identifier in the service, and the record status identifies whether the corresponding record is valid, and in table 1, it particularly refers to whether the service is currently valid, and when the service is offline, the record status may be changed to invalid.

Meanwhile, the system can generate a relationship record of the restriction of the business process in a business process restriction relationship table shown in table 7 or table 9.

TABLE 7 examples of business process self-restriction relationship tables

/>

The service state mapping relation needs to be maintained, see table 8, and the intermediate states of the service in the service relation management engine service are set from '01' according to the state circulation sequence and are mapped with the states of the service one by one.

Table 8-content examples of service state mapping tables

When the business process is abandoned and deleted, the system checks whether the in-transit business exists in the business process record, can give information prompt according to different business scenes, or sets the in-transit business to be in a termination state, and simultaneously uniformly deletes the constraint process information and the state mapping information related to the abandoned business or sets the in-transit business to be in an invalid state.

(2) Business process relationship management

As shown in table 9, the constraint relationship can be maintained for different services by this function, including service ID, constraint status, exception status, etc.

TABLE 9 restriction relationship Table between business processes

The constraint on E00004 by E00001 in table 9 above is not recorded in reverse because the constraint on E00001 by E00004 belongs to the state constraint, and the flow initiation of the E00001 service is not restricted any more, and the record of reverse constraint exists in the state constraint relationship and will be presented in the next section.

(3) Business state relationship management

As in table 10, by this function, status constraints can be maintained for different services, including service ID, service status, constraint service ID, constraint status, etc.

Service status: the flow representing the initiating service receives the restriction of other services when the flow flows to the appointed state, the value is the non-initial state of the initiating service, no default value exists, and the flow cannot be set as ALL and NULL.

Restriction state: the service flow relation information is the same as the constraint state in the service flow relation information, represents the effective state of constraint service as constraint condition, defaults to ALL, and represents that the constraint service has constraint on initiating service when any non-final service exists; the non-ALL scene takes the value as the middle state (non-final state) of the constraint service, and when the constraint service is in the constraint state and the nodes in the subsequent states, the constraint is present on the initiation service.

Table 10-content examples of business state relationship tables

The constraint relation of E00004 to E00001 corresponds to the constraint relation of E00001 to E00004 in the foregoing, namely when the user has E00004 on-the-way service, the E00001 service cannot flow to the 03 state, and conversely, if E00001 is in the 03 and subsequent state nodes (non-final state), the constraint of flow initiation is generated for the E00004 service. And such constraint relationships can only be generated by maintaining state constraint relationships, and the flow constraint relationships of E00001 and E00004 cannot exist in the business flow relationship table before the relationship record is generated.

The relationship between E00001 and E00005 is a constraint relationship between the states, that is, when any service is in 02 and the following state node (non-final state), another service cannot flow to 02. If the business process relationship table already has process constraint information between E00001 and E00005, the state constraint will fail.

In this particular example, the constraint relationship exists independently because the state constraint of E00006 on E00001 is not a constraint. As can be seen from the above table, when E00006 enters 02 and the subsequent state node (not in the final state), E00001 cannot enter the final state 99, and it can be inferred that the reverse scene, E00001, has no restriction on E00006 unless the business process relation table already has the process restriction information between E00001 and E00006.

(4) Business process record acquisition

As shown in table 11, the real-time collection of the service flow records is realized through an open interface, including service initiation information collection, service state information collection and service termination information collection.

When user service is successfully initiated, the service pushes initiation information to the service flow management engine, and the service state is fixed to be 00; when the business state flows, the business service pushes state change information to the business process management engine, and the business state records the current actual state; when the service is finished (including successful end of service, cancellation of service, etc.), the service pushes termination information to the service flow management engine, and the service state is fixed to 99.

Table 11-examples of contents of business process record tables

(5) Business relationship constraint control

The real-time verification of the business process is realized through the open interface, and comprises verification of whether the business process can be initiated or not and verification of whether the business process can be circulated to a specified state or not.

First, business process constraints

When a user initiates a service flow, the system firstly acquires constraint relation information of the initiated service through a service flow management engine, then acquires a service flow record through the user information and the constraint relation information, judges whether the service can be initiated or not through a series of algorithms of the service flow constraint, and records the service state as shown in table 12; if the constraint record exists, the business process management engine returns the constraint reason.

Considering that the same service or different services are initiated simultaneously, dirty reading or unreal reading of the service flow records may be caused, so that the service flow restriction service and the service state restriction service provided by the service management engine belong to shared resources for a single user or the same group of weaving mechanisms, and the access of the shared resources needs to be controlled. The business relationship management engine adopts two modes of database lock (record lock of user token record table) and distributed lock based on Redis to solve the problem.

The principle of the database lock (record lock of the user token record list) is that before a user initiates a service and acquires constraint relation information, whether the user token record exists in the service flow record list is judged (the service of the token record is identified as a fixed value of AAAAAA, and the user is unique, if the service of the token record does not exist, one token record is inserted or preset through a visual interface), if the occupied state of the record is 0-unused, the occupied state of the record is 1-in-use and sub-transaction submission is carried out, the subsequent flow can be carried out, and after the service is processed by the current node, the occupied state is updated back to 0-unused to release the token; if the recorded occupancy state is '1-in-use', prompting a user and terminating the operation; another way is to directly use the preset exclusive lock of the database when reading the token record, which will no longer set the "occupied state", "creation time", "update time" column values. The principle of controlling access to shared resources using database locks is relatively simple and will be described in terms of database locks in the following business processes for ease of understanding.

Redis-based distributed locks are consistent with the implementation targets of database locks, use user IDs (or organization IDs), or user IDs (or organization IDs) +request services as keys to control concurrency and waiting of threads, avoid high overhead and performance problems of database I/Os compared with database locks, and can be more reliable and less invasive to system services in complex architectures such as multi-service, distributed and the like, but as the scale of system users is continuously enlarged and the architecture is complicated, redis-based distributed locks are continuously upgraded and evolved in face of problems such as timeout, false deletion and the like, and will not be described in detail herein.

TABLE 12 business process record table

As shown in fig. 11, the flow restriction control initiated by the service is a relatively general application scenario, because the specific state of the control service is not involved, and the maintenance of the restriction relationship and the restriction logic are relatively simple.

Secondly, business state restriction

As shown in fig. 12, the service state constraint refers to checking, by the service relationship management engine, whether or not there is a constraint on the service and whether or not the service can be changed to the next state when the service state is circulated. Maintenance and constraint logic of a service state constraint relation are relatively complex, and if a service flow in a normal system has an initiating condition, the circulation of the state is not controlled, so that the service state constraint is not commonly used in actual service; in practical application, when the service state flows, the token (the same token record as the service flow restriction is used) is obtained from the service relation management engine service through the interface, and the state restriction check is started.

Fifth interface design

The business relation management engine opens interfaces for business services, and the interfaces comprise a flow restriction checking interface, a state restriction checking interface and a flow record acquisition interface.

(VI) flow restriction verification

As shown in table 13, the flow restriction checking interface is applied to the service initiation scene, and the token acquisition and the service flow relation checking are realized through the interface.

TABLE 13

(seventh) State constraint verification

As shown in table 13, the state constraint checking interface is applied to a service state circulation scene, and the token and service state relation checking is obtained through the interface.

TABLE 13

(eighth) Process record acquisition

As shown in table 14, the process record collection interface is applied to a service full process scene, including service initiation, service state circulation, service termination, etc., and realizes recording of service process and state information through the interface, and releases the token, without checking a common state circulation scene of a state constraint relationship, without starting a function of releasing the token, and only recording the state information.

TABLE 14

The application example greatly improves the flexibility of optimizing and expanding the service main service and improves the research and development efficiency of the service function through decoupling the service management and the service main service; through the visual management of the business relationship, the cost of system modification and upgrading caused by the change of the business relationship can be greatly reduced.

With the continuous increase of service functions, the restriction and mutual exclusion requirements of the system on service flows are higher and higher, whether other in-transit services exist or not is directly searched through a service interface, and whether the service is difficult to develop or not or the application performance is not preferable, so that it is significant to build a general manageable service relation management engine outside a service module, and whether the service can be started or not can be identified only by simple interface and efficient judgment when the service flows are initiated. And through visual management of the business relationship, the cost of system transformation and upgrading caused by the change of the business relationship can be greatly reduced.

The embodiment of the application further provides an electronic device, which may include a processor, a memory, a receiver, and a transmitter, where the processor is configured to execute the service constraint relation management method mentioned in the foregoing embodiment, and the processor and the memory may be connected by a bus or other manners, for example, through a bus connection. The receiver may be connected to the processor, memory, by wire or wirelessly. The electronic device may receive real-time motion data from a sensor in the wireless multimedia sensor network and receive an original video sequence from the video acquisition device.

The processor may be a central processing unit (Central Processing Unit, CPU). The processor may also be any other general purpose processor, digital signal processor (Digital Signal Processor, DSP), application specific integrated circuit (Application Specific Integrated Circuit, ASIC), field programmable gate array (Field-Programmable Gate Array, FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof.

The memory, as a non-transitory computer readable storage medium, may be used to store a non-transitory software program, a non-transitory computer executable program, and modules, such as program instructions/modules corresponding to the business constraint relationship management method in the embodiments of the present application. The processor executes various functional applications and data processing of the processor by running non-transitory software programs, instructions and modules stored in the memory, that is, the service constraint relation management method in the above method embodiment is implemented.

The memory may include a memory program area and a memory data area, wherein the memory program area may store an operating system, at least one application program required for a function; the storage data area may store data created by the processor, etc. In addition, the memory may include high-speed random access memory, and may also include non-transitory memory, such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid state storage device. In some embodiments, the memory may optionally include memory located remotely from the processor, the remote memory being connectable to the processor through a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The one or more modules are stored in the memory that, when executed by the processor, perform the business constraint relationship management method of the embodiments.

In some embodiments of the present application, the user equipment may include a processor, a memory, and a transceiver unit, where the transceiver unit may include a receiver and a transmitter, and the processor, the memory, the receiver, and the transmitter may be connected by a bus system, the memory storing computer instructions, and the processor executing the computer instructions stored in the memory to control the transceiver unit to transmit and receive signals.

As an implementation manner, the functions of the receiver and the transmitter in the present application may be considered to be implemented by a transceiver circuit or a dedicated chip for transceiver, and the processor may be considered to be implemented by a dedicated processing chip, a processing circuit or a general-purpose chip.

As another implementation manner, a manner of using a general-purpose computer may be considered to implement the server provided in the embodiments of the present application. I.e. program code for implementing the functions of the processor, the receiver and the transmitter are stored in the memory, and the general purpose processor implements the functions of the processor, the receiver and the transmitter by executing the code in the memory.

The embodiments of the present application also provide a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the aforementioned business constraint relationship management method. The computer readable storage medium may be a tangible storage medium such as Random Access Memory (RAM), memory, read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, floppy disks, hard disk, a removable memory disk, a CD-ROM, or any other form of storage medium known in the art.

Those of ordinary skill in the art will appreciate that the various illustrative components, systems, and methods described in connection with the embodiments disclosed herein can be implemented as hardware, software, or a combination of both. The particular implementation is hardware or software dependent on the specific application of the solution and the design constraints. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application. When implemented in hardware, it may be, for example, an electronic circuit, an Application Specific Integrated Circuit (ASIC), suitable firmware, a plug-in, a function card, or the like. When implemented in software, the elements of the present application are the programs or code segments used to perform the required tasks. The program or code segments may be stored in a machine readable medium or transmitted over transmission media or communication links by a data signal carried in a carrier wave.

It should be clear that the present application is not limited to the particular arrangements and processes described above and illustrated in the drawings. For the sake of brevity, a detailed description of known methods is omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method processes of the present application are not limited to the specific steps described and illustrated, and those skilled in the art can make various changes, modifications, and additions, or change the order between steps, after appreciating the spirit of the present application.

The features described and/or illustrated in this application for one embodiment may be used in the same way or in a similar way in one or more other embodiments and/or in combination with or instead of the features of the other embodiments.

The foregoing description is only a preferred embodiment of the present application and is not intended to limit the present application, and various modifications and variations may be made to the embodiment of the present application by those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principles of the present application should be included in the protection scope of the present application.

Claims

1. A business constraint relation management and control method is characterized by comprising the following steps:

2. The traffic constraint relation management and control method according to claim 1, further comprising:

3. The traffic constraint relation management and control method according to claim 2, further comprising:

4. The traffic constraint relationship management method according to claim 3, further comprising:

5. The traffic constraint relation management and control method according to claim 2, further comprising:

6. The method for controlling a service constraint relation according to claim 1, further comprising, before the step of obtaining a service flow constraint relation control result of a target service initiated by a current request of the target service system:

7. The method for controlling service constraint relation according to claim 2, further comprising, before the obtaining the service state constraint relation control result of the target service of the current request service state flow of the target service system:

8. A business relationship management engine, comprising:

9. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the business constraint relationship management method of any of claims 1 to 7 when the computer program is executed by the processor.

10. A computer readable storage medium having stored thereon a computer program, which when executed by a processor implements a business constraint relationship management method according to any one of claims 1 to 7.