CN111435495B - Service processing method, device and equipment - Google Patents
Service processing method, device and equipment Download PDFInfo
- Publication number
- CN111435495B CN111435495B CN201910030671.5A CN201910030671A CN111435495B CN 111435495 B CN111435495 B CN 111435495B CN 201910030671 A CN201910030671 A CN 201910030671A CN 111435495 B CN111435495 B CN 111435495B
- Authority
- CN
- China
- Prior art keywords
- service
- target
- component
- identity
- scene
- 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.)
- Active
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
- G06Q10/00—Administration; Management
- G06Q10/08—Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
- G06Q10/087—Inventory or stock management, e.g. order filling, procurement or balancing against orders
-
- 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/12—Accounting
- G06Q40/125—Finance or payroll
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Strategic Management (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Human Resources & Organizations (AREA)
- Economics (AREA)
- General Business, Economics & Management (AREA)
- Physics & Mathematics (AREA)
- Marketing (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Entrepreneurship & Innovation (AREA)
- Development Economics (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- Technology Law (AREA)
- Data Mining & Analysis (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention provides a service processing method, a device and equipment, wherein the method comprises the following steps: after receiving the service request, identifying a service scene of the target service to be executed according to the service request, and executing the target component corresponding to the target service according to the component execution rule corresponding to the service scene. According to the technical scheme provided by the invention, the service scene and the service flow are separated and abstracted, so that a user can configure the service scene and the component execution rule corresponding to the service scene according to the needs, and the flexibility of service management and the service development speed can be improved.
Description
Technical Field
The present invention relates to the field of service management technologies, and in particular, to a service processing method, device, and equipment.
Background
With the rapid development of internet technology, more and more enterprises begin to adopt enterprise management software to perform business data processing, enterprise management and other works, so as to better improve the business process of the enterprises and improve the core competitiveness of the enterprises.
An enterprise resource planning (Enterprise Resource Planning, ERP) system is a relatively common management system that can help enterprises manage supply chains such as purchasing, selling, and stocking. Taking inventory management as an example, the current ERP system generally develops a plurality of inventory management business processes with fixed functions for realizing different businesses; when in use, the user can select the corresponding inventory management business flow to carry out inventory management according to the required business.
However, the business management scheme with the solidified business flow functions cannot meet the differentiated requirements of different users, and has poor flexibility; and when the business is newly added, the related business processes are required to be combed, and secondary development is carried out on the business processes, so that the business development speed is influenced.
Disclosure of Invention
In view of the foregoing, the present invention provides a service processing method, apparatus and device, which are used for improving flexibility of service management and improving service development speed.
In order to achieve the above object, in a first aspect, an embodiment of the present invention provides a service processing method, including:
receiving a service request;
identifying service scenes of target service to be executed according to service requests, wherein each service scene is preconfigured with corresponding component executing rules;
and executing the target component corresponding to the target service according to the component execution rule corresponding to the service scene.
As an optional implementation manner of the embodiment of the present invention, after receiving a service request, before executing a target component corresponding to a target service according to a component execution rule corresponding to the service scenario, the method further includes:
and acquiring a target component corresponding to the target service according to the received service request.
As an optional implementation manner of the embodiment of the present invention, obtaining, according to a service request, a target component corresponding to a target service includes:
identifying the service identity of the target service according to the service request;
determining a target service template for binding the service identity of the target service according to the binding relation between the pre-configured service identity and the service template, wherein the service template comprises a pre-configured assembly set;
and acquiring the target component according to the target service template.
As an optional implementation manner of the embodiment of the present invention, the service request carries service identity information, and the identifying the service identity of the target service according to the service request includes:
matching the service identity information with a first service rule in a preset first mapping relation, wherein the first mapping relation comprises a corresponding relation between the service identity and the first service rule;
and determining the service identity corresponding to the matched first service rule as the service identity of the target service.
As an optional implementation manner of the embodiment of the present invention, matching the service identity information with a first service rule in a preset first mapping relationship includes:
and matching the service identity information with a first service rule stored in a pre-established service identity tree, wherein the service identity tree stores a first mapping relation.
As an optional implementation manner of the embodiment of the present invention, before identifying the service identity of the target service according to the service request, the method further includes:
and establishing a service identity tree according to the service relation among the services.
As an optional implementation manner of the embodiment of the present invention, the service request carries a service flow identifier, the service template includes at least one service flow, the service flow includes component identifiers of required components, and the obtaining a target component according to the target service template includes:
determining a corresponding target business process from the target business template according to the business process identification;
and obtaining a target component corresponding to the component identifier in the target business process.
As an optional implementation manner of the embodiment of the present invention, the service flow further includes an execution sequence of each component, and executing the target component according to the component execution rule corresponding to the service scenario includes:
and executing the target component according to the component execution rule corresponding to the service scene and the execution sequence in the target service flow.
As an optional implementation manner of the embodiment of the present invention, the service request carries service scenario information, and identifies a service scenario of a target service to be executed according to the service request, where the method includes:
Matching the service scene information with a second service rule in a preset second mapping relation, wherein the second mapping relation comprises a corresponding relation between the service scene and the second service rule;
and determining the service scene corresponding to the matched second service rule as the service scene of the target service.
As an optional implementation manner of the embodiment of the present invention, a service request carries a service operation parameter, and executes a target component corresponding to a target service according to a component execution rule corresponding to a service scenario, where the method includes:
and executing the target component according to the component execution rule corresponding to the service operation parameter and the service scene.
As an alternative implementation of the embodiment of the present invention, the service request is an inventory management service request.
In a second aspect, an embodiment of the present invention provides a service processing method, including:
receiving an inventory management service request;
identifying service scenes of target service to be executed according to inventory management service requests, wherein each service scene is preconfigured with corresponding component execution rules;
and executing the target component corresponding to the target service according to the component execution rule corresponding to the service scene, and generating the inventory accounting data.
In a third aspect, an embodiment of the present invention provides a service processing apparatus, including:
the receiving module is used for receiving the service request;
the identification module is used for identifying service scenes of target service to be executed according to the service request, wherein each service scene is preconfigured with a corresponding component execution rule;
and the execution module is used for executing the target component corresponding to the target service according to the component execution rule corresponding to the service scene.
As an alternative implementation of the embodiment of the present invention, the service request is an inventory management service request.
As an alternative implementation manner of the embodiment of the present invention, the apparatus further includes: the acquisition module is used for acquiring the target assembly corresponding to the target service to be executed according to the service request before the execution module executes the target assembly corresponding to the target service according to the assembly execution rule corresponding to the service scene after the receiving module receives the service request.
As an optional implementation manner of the embodiment of the present invention, the obtaining module includes:
the identification unit is used for identifying the service identity of the target service according to the service request;
the determining unit is used for determining a target service template for binding the service identity of the target service according to the binding relation between the pre-configured service identity and the service template, wherein the service template comprises a pre-configured assembly set;
And the acquisition unit is used for acquiring the target component according to the target service template.
As an optional implementation manner of the embodiment of the present invention, the service request carries service identity information, and the identification unit is specifically configured to:
matching the service identity information with a first service rule in a preset first mapping relation, wherein the first mapping relation comprises a corresponding relation between the service identity and the first service rule;
and determining the service identity corresponding to the matched first service rule as the service identity of the target service.
As an optional implementation manner of the embodiment of the present invention, the identification unit is specifically configured to: and matching the service identity information with a first service rule stored in a pre-established service identity tree, wherein the service identity tree stores a first mapping relation.
As an alternative implementation manner of the embodiment of the present invention, the apparatus further includes:
the establishing module is used for establishing a service identity tree according to the service relation among the services before the identifying unit identifies the service identity of the target service according to the service request.
As an optional implementation manner of the embodiment of the present invention, the service request carries a service flow identifier, the service template includes at least one service flow, the service flow includes a component identifier of a required component, and the obtaining unit is specifically configured to:
Determining a corresponding target business process from the target business template according to the business process identification;
and obtaining a target component corresponding to the component identifier in the target business process.
As an optional implementation manner of the embodiment of the present invention, the service flow further includes an execution sequence of each component, and the execution module is specifically configured to: and executing the target component according to the component execution rule corresponding to the service scene and the execution sequence in the target service flow.
As an optional implementation manner of the embodiment of the present invention, the service request carries service scene information, and the identification module is specifically configured to:
matching the service scene information with a second service rule in a preset second mapping relation, wherein the second mapping relation comprises a corresponding relation between the service scene and the second service rule;
and determining the service scene corresponding to the matched second service rule as the service scene of the target service.
As an optional implementation manner of the embodiment of the present invention, the service request carries a service operation parameter, and the execution module is specifically configured to:
and executing the target component according to the component execution rule corresponding to the service operation parameter and the service scene.
In a fourth aspect, an embodiment of the present invention provides a service processing apparatus, including:
The receiving module is used for receiving the inventory management service request;
the identification module is used for identifying service scenes of target services to be executed according to the inventory management service request, wherein each service scene is preconfigured with corresponding component execution rules;
and the generating module is used for executing the target component corresponding to the target service according to the component execution rule corresponding to the service scene and generating the inventory accounting data.
In a fifth aspect, an embodiment of the present invention provides a service processing apparatus, including: a memory and a processor, the memory for storing a computer program; the processor is configured to perform the method of the first aspect, the second aspect or any implementation of the first aspect when the computer program is invoked.
In a sixth aspect, an embodiment of the present invention provides a service management system, including: a client and a service processing device according to the third aspect.
In a seventh aspect, an embodiment of the present invention provides a computer readable storage medium, on which a computer program is stored, which when executed by a processor implements the method according to the first aspect, the second aspect or any implementation of the first aspect.
According to the business processing method, the business processing device and the business processing equipment provided by the embodiment of the invention, after the business request is received, the business scene of the target business is identified according to the business request, and then the target assembly corresponding to the target business is executed according to the assembly execution rule corresponding to the business scene, so that the business scene and the business flow are separated and abstracted, and a user can configure the business scene and the assembly execution rule corresponding to the business scene according to the requirement, thereby improving the flexibility of business management and the business development speed.
Drawings
Fig. 1 is a schematic flow chart of a service processing method according to an embodiment of the present invention;
FIG. 2 is a schematic flow chart of a target component acquisition process according to an embodiment of the present invention;
FIG. 3 is a schematic diagram of a business identity tree according to an embodiment of the present invention;
fig. 4 is a flow chart of another service processing method according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of a service processing device according to an embodiment of the present invention;
fig. 6 is a schematic structural diagram of another service processing apparatus according to an embodiment of the present invention;
fig. 7 is a schematic structural diagram of a service processing device according to an embodiment of the present invention.
Detailed Description
Aiming at the defects of poor flexibility and low service development speed of the current service management scheme caused by solidification of the service flow, the embodiment of the invention provides a service processing method, device and equipment, which are mainly based on the thought of componentization design, each service logic component of the service flow is componentized, a service scene is separated from a specific service flow, after a service request is received, the service scene of a target service is identified according to the service request, and then the target component corresponding to the target service is executed according to the component execution rule corresponding to the service scene, so that a user can configure the service scene and the component execution rule corresponding to the service scene according to the requirement, and the flexibility of service management and the service development speed are improved.
The service processing method, device and equipment provided by the embodiment of the invention can be applied to an inventory management system or other service management systems, and for convenience of explanation, the inventory management system is taken as an example for illustration in the embodiment of the invention.
Embodiments of the present invention are described below with reference to the accompanying drawings.
Fig. 1 is a flow chart of a service processing method provided by an embodiment of the present invention, as shown in fig. 1, the service processing method provided by the embodiment may include the following steps:
s100, receiving a service request.
Specifically, when a user (i.e., a service party) needs to perform a service management operation, a service request may be initiated through a client, and a service processing device may receive the service request.
S101, acquiring a target component corresponding to a target service to be executed according to a received service request.
Specifically, various management services are realized through various service flows, various service logics in the service flows can be pre-packaged into various components and stored in a component library, and a target component is a component obtained by performing componentization processing on various service logics required by realizing the target service.
In specific implementation, the corresponding relation between the service and the components can be preset in the service processing device, after the service request is received, the target service to be executed can be identified according to the service request, and then the target component corresponding to the target service is obtained according to the corresponding relation.
The user can also pre-configure the service identity of the service, bind a service template for each service identity, and configure the assembly set required by the service in the service template; the binding relationship (i.e. the binding relationship between the service identity and the service template) can be stored in the service processing device, and after the service request is received, the target component can be obtained by the method shown in fig. 2, so that the user can rapidly cope with the change of the service by customizing the service identity and the service template corresponding to the service identity, thereby achieving the effect of improving the flexibility of service management and the service development speed. Fig. 2 is a schematic flow chart of obtaining a target component according to an embodiment of the present invention, as shown in fig. 2, the method may include the following steps:
s1011, identifying the service identity of the target service according to the service request.
Specifically, after receiving the service request, the service processing device may analyze the service request through the policy engine, and identify the service identity of the target service. The service identity is used for marking the specific service, and the service request can carry service identity information. The service identity information may be a service identity identifier; and the method can also comprise at least one of user identity, commodity information, warehouse information, transaction type and other information which can be used for identifying the service identity, and correspondingly, the service identity can be represented by a service rule (called a first service rule), and when the service identity is identified, the first service rule can be used for carrying out route identification of the service identity, so that the identification efficiency of the service identity can be improved.
In specific implementation, a first mapping relationship may be preset, where the first mapping relationship includes a correspondence between a service identity and a first service rule; when a service request is received, service identity information in the service request and a first service rule in the preset first mapping relation can be matched, and a service identity corresponding to the matched first service rule is determined as a service identity of a target service.
For example, the first service rule corresponding to the service identity of the target service K is: the identity of the user is K1 (sub-rule R1), the commodity is K2 (sub-rule R2), and the warehouse is K3 (sub-rule R3); the service identity information carries the user identity k1, the commodity information k2 and the warehouse information k3, and when rule matching is performed, three sub-rules can be matched in sequence, for example: firstly matching the user identity (namely whether K1 is K1) and then matching the commodity (namely whether K2 is K2) from the matched first business rule after matching is successful, and then matching the warehouse (namely whether K3 is K3) from the matched first business rule after matching is successful, wherein the business identity of the target business A is identified after three sub-rules are matched successfully.
In order to further improve the identification efficiency of the service identity, in this embodiment, before identifying the service identity of the target service, a service identity tree may be established according to the service relationship between the services, and the first mapping relationship is stored in the service identity tree; in the process of identifying the service identity, when the service rule is matched, namely when the service identity information in the service request is matched with the first service rule in the first mapping relation, the service identity information can be matched with the first service rule stored in the pre-established service identity tree.
Specifically, some services may include some sub-services, such as: the enterprise A self-camping business comprises sub-business health business, international direct camping business, online supermarket business and the like; the first business rule of each sub-business belonging to a certain business is the first business rule containing the business, and when the business identity tree is established, the node corresponding to each sub-business of the business is the sub-node of the node corresponding to the business. The first business rule of the business is stored in the node corresponding to the business (namely, the father node), and the first business rule of the child business or the business rules except the first business rule of the father node in the first business rule of the child business can be stored in the child node of the father node.
Continuing with the foregoing example, assume that service K is a sub-service of service N, service N is a sub-service of service M, a first service rule of service K includes three sub-rules of R1, R2, and R3, a first service rule of service N includes two sub-rules of R1 and R2, and a first service rule of service M includes one sub-rule of R1. The node corresponding to the service K is a child node of the node corresponding to the service N, and the node corresponding to the service N is a child node of the node corresponding to the service M; when in storage, the sub-rule R1 is stored in the node corresponding to the service M, the sub-rules R1 and R2 can be stored in the node corresponding to the service N, or only R2 can be stored, and the sub-rules R1, R2 and R3 can be stored in the node corresponding to the service K, or only R3 can be stored. In addition, the node corresponding to each service may store the service identity (specifically, may be a service identity identifier) of the service or the binding relationship between the service identity and the service template (specifically, may be the binding relationship between the service identity identifier and the service template identifier).
Fig. 3 is a schematic diagram of a service identity tree provided in an embodiment of the present invention, where as shown in fig. 3, a root node is used as an entry for service identity identification, and does not correspond to a specific service, and includes a plurality of sub-nodes, and each sub-node may also include 0 or at least one sub-node; the number of sub-nodes and the depth of the service identity tree contained in each node are determined according to the service established by the user and the service relationship between the services, in fig. 3, the root node contains three sub-nodes (i.e. service a, service B and service C), the node corresponding to service a contains two sub-nodes (i.e. sub-service A1 and sub-service A2), the node corresponding to service B contains one sub-node (i.e. sub-service B1), the node corresponding to service C contains 0 sub-nodes, and the depth of the tree is 3.
When rule matching is performed according to the service identity tree, after the root node is read, the following traversal operation can be performed on each node under the root node: traversing each node according to the width, judging whether service identity information in a service request meets a first service rule in a node when traversing to a certain node, if not, continuing to traverse the next node in the width, and finishing the traversing when traversing each node in the width; if yes, recording the node, checking whether the node has a child node, and if not, ending the traversal; if so, continuing to execute the above traversal operation on each child node under the node until the traversal is finished, and outputting the service identity (such as the service identity identifier) stored in the last recorded node, and taking the service identity as the service identity of the target service.
S1012, according to the binding relation between the pre-configured service identity and the service template, and determining a target service template to which the service identity of the target service is bound.
Specifically, the user may configure a binding relationship between a service identity of the service and a service template in advance at the client, where the service template may include at least one service flow, for example: a warehousing flow, a ex-warehouse flow, an occupation flow, a cancel occupation flow, a confirmation flow and the like; for each business process, a user can adopt a process template preset by the system or customize the process template according to the requirement to configure a corresponding assembly set and the execution sequence of each assembly.
After the service processing device identifies the service identity of the target service, the service template (i.e., the target service template) to which the service identity of the target service is bound can be determined according to the binding relationship.
In specific implementation, as described above, the binding relationship may be stored in a node of the service identity tree, that is, each node except the root node stores the binding relationship between the service identity corresponding to the node and the service template; the binding relationship may also be stored in other locations, with only the service identities being stored in the nodes of the service identity tree.
In this embodiment, the service identity is bound to the service template, and the same service template may be bound by multiple service identities, so that the service template may be reused.
S1013, acquiring a target assembly according to the target service template.
Specifically, the service flow in the service template may include the component identifier of the required component, and the service processing device may obtain the corresponding target component from the component library according to the component identifier.
As described above, the business processes may include at least one business process, and when the target component is acquired, the target business process may be determined according to the business request first, and then the corresponding target component may be acquired according to the component identifier in the target business process.
In specific implementation, the service request may carry a service flow identifier, and the service processing device may determine, according to the service flow identifier, a corresponding target service flow from the target service template, and then acquire a target component corresponding to the component identifier in the target service flow.
When the service processing device stores the target component corresponding to the target service in advance, step S101 may not be executed, that is, step S102 may be executed after step S100 is executed.
S102, identifying a service scene of the target service according to the service request.
In the embodiment, the service scene is separated from a specific service flow and abstracted, so that a user can configure the service scene of the service according to own needs to meet the requirement of rapidly developing the service, and meanwhile, the flexibility of service management is improved; in addition, the business processes among different business scenes can be isolated, so that monitoring is facilitated, and operators can be helped to quickly locate and correct dislocation.
In particular, the user configures a service scenario of a service, i.e. configures a service scenario of a service template of a service identity binding of the service. When the service scene is specifically configured, a user can select a required service scene from service scenes preset by the system, can customize the service scene, and can not configure the service scene, wherein the service scene contained in the service is a default service scene at the moment; i.e. one business template may configure 0 or at least one business scenario. Wherein each business scenario is preconfigured with corresponding component execution rules, and the process of configuring the business scenario by the user is that of configuring the component execution rules, and the component execution rules may be that of changing the execution result and/or the execution policy (e.g., not executing) of a certain component or components.
For example, the default service scenario for service a is: synchronizing the inventory data to the e-commerce platform 1; the user increases a service scene A according to the requirements of service development: the inventory data is synchronized to the e-commerce platform 1 and the e-commerce platform 2. Also for example: the default service scenario for service B is: the inventory proportion of the E-commerce platform 1 is 50%, and the inventory proportion of the E-commerce platform 2 is 50%; the user is required to develop according to the service, adding a service scene B: the inventory proportion of the E-commerce platform 1 is 80%, and the inventory proportion of the E-commerce platform 2 is 20%.
After receiving the service request, the service processing device can analyze the service request through the service engine to identify the corresponding service scene. Similarly to the identification of the service identity, when the service scenario is identified, the service request may carry service scenario information, where the service scenario information may be a service scenario identifier, or may include at least one of user identity, commodity information, warehouse information, transaction type, and other information that may be used to identify the service scenario, and the service scenario may be represented by a service rule (referred to as a second service rule), where when the service scenario is identified, the service scenario may be identified by using the second service rule to perform route identification of the service scenario, so as to improve identification efficiency of the service scenario.
When the service request is received, the service scene information in the service request can be matched with the second service rule in the preset second mapping relation; and determining the service scene corresponding to the matched second service rule as the service scene of the target service. The identification process of the service scenario is similar to the identification process of the service identity, and will not be described here again.
In this embodiment, there is no strict execution timing relationship between the steps S102 and S101, and the step S102 may be executed after the step S101, may be executed before the step S101, may be executed simultaneously with the step S101, and the specific execution sequence is not particularly limited in this embodiment.
S103, executing the target component according to the component execution rule corresponding to the service scene.
Specifically, after the service scene is identified, the service processing device can combine the target components into a flow through the flow engine, and execute the target components according to the component execution rule corresponding to the identified service scene, so that the components can respond differently under different service scenes.
In this embodiment, the service request may carry service operation parameters, for example: and after the business scene is identified, the target component can be executed according to the component execution rule and the business operation parameter corresponding to the business scene.
In addition, as described above, the business process may include an execution sequence of each component, and when executing the target component, the target component is executed according to the component execution rule corresponding to the business scenario and the execution sequence in the target business process.
According to the business processing method provided by the embodiment, after the target component corresponding to the target business to be executed is obtained according to the received business request, the business scene of the target business is identified according to the business request, and finally the target component is executed according to the component execution rule corresponding to the business scene, so that the business scene is separated from the business flow and is abstracted, a user can configure the business scene and the component execution rule corresponding to the business scene according to the needs, and the components in the business flow realize different functions, so that the flexibility of business management can be effectively improved; and the user can directly realize by configuring the service scene without secondary development of the service flow when the service is newly added, so that the service development speed can be improved.
Fig. 4 is a flowchart of another service processing method according to an embodiment of the present invention, where the embodiment is a specific implementation manner of processing an inventory management service. As shown in fig. 4, the method provided in this embodiment may include the following steps:
s201, receiving an inventory management service request.
Specifically, when a business party needs to perform an inventory operation, such as: warehouse entry or library occupation, etc., can initiate inventory management service requests through clients, and service processing equipment can receive the service requests.
S202, identifying a service scene of a target service to be executed according to the inventory management service request.
Specifically, the service party can pre-configure service scenes of the inventory management service according to own requirements, so that components in a service flow of the inventory management service realize different inventory management strategies through different component execution rules, namely each service scene has corresponding component execution rules.
After receiving the inventory management service request, the service party firstly identifies the service scene of the target service according to the inventory management request, and then executes the component based on the component execution rule corresponding to the service scene, thereby realizing the inventory management service according to the corresponding inventory management strategy; the specific identification process of the service scenario may refer to the description related to step S102, which is not repeated here.
S203, executing the target components corresponding to the target service according to the component execution rules corresponding to the service scene, and generating inventory accounting data.
In particular, components for inventory management may include: the system comprises a data preparation component, a business verification component, a business conversion component, an inventory accounting component and other types of components, wherein the data preparation component is used for preparing inventory operation sheets, idempotent operation records and other data; the business verification component is used for verifying whether inventory operation initiated by a business party is already operated, whether a corresponding warehouse indicates the requirement of the business party or not, and the like; the business conversion component is configured to convert an inventory operation procedure initiated by a business party into a corresponding inventory accounting operation object, for example: adding the number of C pieces to the commodity with the stock type B of the warehouse A; the inventory accounting component is used for recording the inventory operation data of the business party into the database and generating the inventory accounting data. Various inventory management services may be combined through these types of components to achieve corresponding functionality.
After the service processing device identifies the service scene, the target component corresponding to the target service can be executed according to the component execution rule corresponding to the service scene, and the inventory accounting data can be generated.
According to the business processing method provided by the embodiment, after the inventory management business request is received, the business scene of the target business to be executed is identified according to the inventory management business request, then the target assembly corresponding to the target business is executed according to the assembly execution rule corresponding to the business scene, the inventory accounting data is generated, the business scene is separated from the business flow and is abstracted, so that a business party can configure the business scene and the assembly execution rule corresponding to the business scene according to the requirement, and the assemblies in the business flow realize different inventory management strategies, so that the flexibility of business management can be effectively improved; and the business party can directly realize by configuring the business scene without secondary development of the business flow when newly adding the business, thereby effectively improving the speed of business development.
Based on the same inventive concept, as an implementation of the above method, the embodiment of the present invention provides a service processing apparatus, where the embodiment of the apparatus corresponds to the embodiment of the foregoing method, and for convenience of reading, the embodiment of the present invention does not describe details of the embodiment of the foregoing method one by one, but it should be clear that the apparatus in the present embodiment can correspondingly implement all the details of the embodiment of the foregoing method.
Fig. 5 is a schematic structural diagram of a service processing device according to an embodiment of the present invention, and as shown in fig. 5, the service processing device 10 provided in this embodiment includes:
a receiving module 100, configured to receive a service request;
an identification module 120 for identifying a service scenario of a target service to be executed according to the service request, each business scene is preconfigured with a corresponding component execution rule;
and the execution module 130 is configured to execute the target component corresponding to the target service according to the component execution rule corresponding to the service scenario.
Wherein the service request may be an inventory management service request.
As an alternative implementation manner of the embodiment of the present invention, the apparatus further includes:
the obtaining module 110 is configured to obtain, after the receiving module 100 receives the service request, the target component corresponding to the target service according to the service request before the executing module 130 executes the target component corresponding to the target service according to the component execution rule corresponding to the service scenario.
As an alternative implementation of the embodiment of the present invention, the obtaining module 110 includes:
an identifying unit 111, configured to identify a service identity of a target service according to the service request;
a determining unit 112, configured to determine a target service template to which the service identity of the target service is bound according to a binding relationship between the pre-configured service identity and the service template, where the service template includes a pre-configured component set;
An obtaining unit 113, configured to obtain the target component according to the target service template.
As an optional implementation manner of the embodiment of the present invention, the service request carries service identity information, and the identifying unit 111 is specifically configured to:
matching the service identity information with a first service rule in a preset first mapping relation, wherein the first mapping relation comprises a corresponding relation between the service identity and the first service rule;
and determining the service identity corresponding to the matched first service rule as the service identity of the target service.
Further, the identifying unit 111 may specifically be configured to: and matching the service identity information with a first service rule stored in a pre-established service identity tree, wherein the service identity tree stores a first mapping relation.
As an alternative implementation manner of the embodiment of the present invention, the apparatus further includes:
the establishing module 140 is configured to establish a service identity tree according to a service relationship between the services before the identifying unit 111 identifies the service identity of the target service according to the service request.
As an optional implementation manner of the embodiment of the present invention, the service request carries a service flow identifier, the service template includes at least one service flow, the service flow includes a component identifier of a required component, and the obtaining unit 113 is specifically configured to:
Determining a corresponding target business process from the target business template according to the business process identification;
and obtaining a target component corresponding to the component identifier in the target business process.
Further, the business process may further include an execution sequence of each component, and the execution module 130 may specifically be configured to: and executing the target component according to the component execution rule corresponding to the service scene and the execution sequence in the target service flow.
As an optional implementation manner of the embodiment of the present invention, the service request carries service scenario information, and the identification module 120 is specifically configured to:
matching the service scene information with a second service rule in a preset second mapping relation, wherein the second mapping relation comprises a corresponding relation between the service scene and the second service rule;
and determining the service scene corresponding to the matched second service rule as the service scene of the target service.
As an optional implementation manner of the embodiment of the present invention, the service request carries a service operation parameter, and the execution module 130 is specifically configured to:
and executing the target component according to the component execution rule corresponding to the service operation parameter and the service scene.
The service processing device provided in this embodiment may execute the above method embodiment, and its implementation principle is similar to that of the technical effect, and will not be described herein again.
Fig. 6 is a schematic structural diagram of another service processing apparatus according to an embodiment of the present invention, and as shown in fig. 6, a service processing apparatus 20 according to this embodiment includes:
a receiving module 210, configured to receive an inventory management service request;
the identifying module 220 is configured to identify service scenarios of a target service to be executed according to the inventory management service request, where each service scenario is preconfigured with a corresponding component execution rule;
the generating module 230 is configured to execute a target component corresponding to a target service according to a component execution rule corresponding to a service scenario, and generate inventory accounting data.
The service processing device provided in this embodiment may execute the above method embodiment, and its implementation principle is similar to that of the technical effect, and will not be described herein again.
Based on the same inventive concept, the embodiment of the invention also provides a service processing device. Fig. 7 is a schematic structural diagram of a service processing device according to an embodiment of the present invention, as shown in fig. 7, where the service processing device provided in this embodiment includes: a memory 310 and a processor 320, the memory 310 for storing a computer program; the processor 320 is configured to perform the method described in the method embodiments above when the computer program is invoked.
The service processing device provided in this embodiment may execute the above method embodiment, and its implementation principle is similar to that of the technical effect, and will not be described herein again.
The embodiment of the invention also provides a service management system, which comprises: the client and the service processing device described in the above embodiment.
The embodiment of the invention also provides a computer readable storage medium, on which a computer program is stored, which when being executed by a processor, implements the method described in the above method embodiment.
It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media having computer-usable program code embodied therein.
The processor may be a central processing unit (Central Processing Unit, CPU), but may also be other general purpose processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), off-the-shelf programmable gate arrays (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, etc., such as Read Only Memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.
Computer readable media include both non-transitory and non-transitory, removable and non-removable storage media. Storage media may embody any method or technology for storage of information, which may be computer readable instructions, data structures, program modules, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Disks (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium which can be used to store information that can be accessed by a computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.
Finally, it should be noted that: the above embodiments are only for illustrating the technical solution of the present invention, and not for limiting the same; although the invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some or all of the technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit of the invention.
Claims (14)
1. A method for processing a service, comprising:
receiving a service request;
identifying the service identity of the target service according to the service request;
determining a target service template for binding the service identity of the target service according to a binding relation between a pre-configured service identity and the service template, wherein the service template comprises a pre-configured assembly set;
acquiring a target component according to the target service template;
identifying service scenes of target service to be executed according to the service request, wherein each service scene is preconfigured with a corresponding component executing rule;
and executing the target component corresponding to the target service according to the component execution rule corresponding to the service scene.
2. The method according to claim 1, wherein the service request carries service identity information, and the identifying the service identity of the target service according to the service request includes:
matching the service identity information with a first service rule in a preset first mapping relation, wherein the first mapping relation comprises a corresponding relation between the service identity and the first service rule;
and determining the service identity corresponding to the matched first service rule as the service identity of the target service.
3. The method of claim 2, wherein the matching the service identity information with the first service rule in the preset first mapping relationship includes:
and matching the service identity information with a first service rule stored in a pre-established service identity tree, wherein the first mapping relation is stored in the service identity tree.
4. A method according to claim 3, characterized in that before said identifying the service identity of the target service from the service request, the method further comprises:
and establishing the service identity tree according to the service relation among the services.
5. The method according to claim 1, wherein the service request carries a service flow identifier, the service template includes at least one service flow, the service flow includes a component identifier of a required component, and the obtaining the target component according to the target service template includes:
determining a corresponding target business process from the target business template according to the business process identifier;
and acquiring a target component corresponding to the component identifier in the target business process.
6. The method according to claim 5, wherein the business process further includes an execution sequence of each component, and the executing the target component according to the component execution rule corresponding to the business scenario includes:
and executing the target component according to the component execution rule corresponding to the service scene and the execution sequence in the target service flow.
7. The method according to claim 1, wherein the service request carries service scenario information, and the identifying the service scenario of the target service to be executed according to the service request includes:
matching the service scene information with a second service rule in a preset second mapping relation, wherein the second mapping relation comprises a corresponding relation between the service scene and the second service rule;
And determining the service scene corresponding to the matched second service rule as the service scene of the target service.
8. The method according to claim 1, wherein the service request carries a service operation parameter, and the executing the target component corresponding to the target service according to the component execution rule corresponding to the service scenario includes:
and executing the target component corresponding to the target service according to the service operation parameter and the component execution rule corresponding to the service scene.
9. A method for processing a service, comprising:
receiving an inventory management service request;
identifying the service identity of the target service according to the service request;
determining a target service template for binding the service identity of the target service according to a binding relation between a pre-configured service identity and the service template, wherein the service template comprises a pre-configured assembly set;
acquiring a target component according to the target service template;
identifying service scenes of target service to be executed according to the inventory management service request, wherein each service scene is preconfigured with a corresponding component execution rule;
and executing the target component corresponding to the target service according to the component execution rule corresponding to the service scene, and generating inventory accounting data.
10. A service processing apparatus, comprising:
the receiving module is used for receiving the service request;
the target component determining module is used for identifying the service identity of the target service according to the service request; determining a target service template for binding the service identity of the target service according to a binding relation between a pre-configured service identity and the service template, wherein the service template comprises a pre-configured assembly set; acquiring the target assembly according to the target service template;
the identification module is used for identifying service scenes of the target service to be executed according to the service request, wherein each service scene is preconfigured with a corresponding component execution rule;
and the execution module is used for executing the target component corresponding to the target service according to the component execution rule corresponding to the service scene.
11. A service processing apparatus, comprising:
the receiving module is used for receiving the inventory management service request;
the target component determining module is used for identifying the service identity of the target service according to the service request; determining a target service template for binding the service identity of the target service according to a binding relation between a pre-configured service identity and the service template, wherein the service template comprises a pre-configured assembly set; acquiring the target assembly according to the target service template;
The identification module is used for identifying service scenes of target services to be executed according to the inventory management service request, wherein each service scene is preconfigured with a corresponding component execution rule;
and the generating module is used for executing the target component corresponding to the target service according to the component execution rule corresponding to the service scene and generating stock accounting data.
12. A service processing apparatus, comprising: a memory and a processor, the memory for storing a computer program; the processor is configured to perform the method of any of claims 1-9 when the computer program is invoked.
13. A service management system, comprising: a client and a service processing device as claimed in claim 12.
14. A computer readable storage medium, on which a computer program is stored, which computer program, when being executed by a processor, implements the method according to any of claims 1-9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910030671.5A CN111435495B (en) | 2019-01-14 | 2019-01-14 | Service processing method, device and equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910030671.5A CN111435495B (en) | 2019-01-14 | 2019-01-14 | Service processing method, device and equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111435495A CN111435495A (en) | 2020-07-21 |
| CN111435495B true CN111435495B (en) | 2023-06-23 |
Family
ID=71580646
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910030671.5A Active CN111435495B (en) | 2019-01-14 | 2019-01-14 | Service processing method, device and equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111435495B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112199413A (en) * | 2020-09-17 | 2021-01-08 | 中国建设银行股份有限公司 | Service request execution method, device, electronic equipment and storage medium |
| CN113516541B (en) * | 2021-09-14 | 2022-01-11 | 杭州小电科技股份有限公司 | Dynamic configuration method and device for store distribution scene and electronic device |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2015070592A1 (en) * | 2013-11-14 | 2015-05-21 | 中兴通讯股份有限公司 | Data flow distribution method and controller |
| CN105844422A (en) * | 2016-04-01 | 2016-08-10 | 阿里巴巴集团控股有限公司 | Business flow execution method and device |
| CN106873957A (en) * | 2016-06-23 | 2017-06-20 | 阿里巴巴集团控股有限公司 | The processing method and equipment of a kind of operation flow |
| CN107038042A (en) * | 2017-02-07 | 2017-08-11 | 阿里巴巴集团控股有限公司 | The method and device that a kind of business is performed |
| CN107506181A (en) * | 2017-07-17 | 2017-12-22 | 阿里巴巴集团控股有限公司 | Business processing, data processing method, device and electronic equipment |
| CN108153551A (en) * | 2017-12-11 | 2018-06-12 | 中国民生银行股份有限公司 | A kind of operation flow page shows method and apparatus |
-
2019
- 2019-01-14 CN CN201910030671.5A patent/CN111435495B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2015070592A1 (en) * | 2013-11-14 | 2015-05-21 | 中兴通讯股份有限公司 | Data flow distribution method and controller |
| CN105844422A (en) * | 2016-04-01 | 2016-08-10 | 阿里巴巴集团控股有限公司 | Business flow execution method and device |
| CN106873957A (en) * | 2016-06-23 | 2017-06-20 | 阿里巴巴集团控股有限公司 | The processing method and equipment of a kind of operation flow |
| CN107038042A (en) * | 2017-02-07 | 2017-08-11 | 阿里巴巴集团控股有限公司 | The method and device that a kind of business is performed |
| CN107506181A (en) * | 2017-07-17 | 2017-12-22 | 阿里巴巴集团控股有限公司 | Business processing, data processing method, device and electronic equipment |
| CN108153551A (en) * | 2017-12-11 | 2018-06-12 | 中国民生银行股份有限公司 | A kind of operation flow page shows method and apparatus |
Non-Patent Citations (1)
| Title |
|---|
| 王家昉;薛洋;冯志勇.分层多agent应用集成框架中的动作组件库设计.计算机应用研究.2009,(10),全文. * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111435495A (en) | 2020-07-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107395353B (en) | block chain consensus method and device | |
| US9690822B2 (en) | System and method for metadata level validation of custom setup objects | |
| CN109933593B (en) | Asset data recording method, device and equipment | |
| JP6215850B2 (en) | Method and apparatus for user recognition and information distribution | |
| CN110909373B (en) | Access control method, equipment, system and storage medium | |
| US20170373939A1 (en) | Data uploading method, apparatus, and system | |
| CN110955715B (en) | Data conversion method and device for ERP system and target platform and electronic device | |
| CN106897342B (en) | Data verification method and equipment | |
| US9766881B2 (en) | Social project management system and marketplace | |
| CN111435495B (en) | Service processing method, device and equipment | |
| CN103152391A (en) | Journal output method and device | |
| CN111124871A (en) | Interface test method and device | |
| CN105187399A (en) | Resource processing method and device | |
| CN111857981A (en) | Data processing method and device | |
| CN112328363B (en) | Cloud hard disk mounting method and device | |
| CN110958278B (en) | API gateway-based data processing method and system and API gateway | |
| CN109389271B (en) | Application performance management method and system | |
| CN116244062A (en) | Data processing method and device, electronic equipment and storage medium | |
| CN111443918A (en) | Channel access method and device for business object installation package | |
| CN115063198A (en) | Method, equipment and medium for performing data access on EPR (expressed resource Server) software under SaaS (software as a service) service | |
| CN112769928B (en) | Information interaction method and device based on service scene | |
| CN114066277A (en) | Business decision method, decision platform, readable medium and electronic device | |
| CN109787945B (en) | Method and device for realizing user component in Android system | |
| CN110704818A (en) | User information modification method and device | |
| CN110287434B (en) | Website processing method and device and storage medium |
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 |