CN111435495A - Service processing method, device and equipment - Google Patents
Service processing method, device and equipment Download PDFInfo
- Publication number
- CN111435495A CN111435495A CN201910030671.5A CN201910030671A CN111435495A CN 111435495 A CN111435495 A CN 111435495A CN 201910030671 A CN201910030671 A CN 201910030671A CN 111435495 A CN111435495 A CN 111435495A
- Authority
- CN
- China
- Prior art keywords
- service
- target
- component
- scene
- rule
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- 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 then executing a target component corresponding to the target service according to a 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 requirement, 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, apparatus and device.
Background
With the rapid development of internet technology, more and more enterprises begin to adopt enterprise management software to perform various operations such as business data processing and enterprise management, so as to better improve the business process of the enterprises and improve the core competitiveness of the enterprises.
An Enterprise Resource Planning (ERP) system is a management system commonly used at present, and can help an Enterprise manage supply chains such as purchasing, selling, and inventory. Taking inventory management as an example, the current ERP system generally develops several inventory management business processes with fixed functions to realize different businesses; when the user uses the system, the user can select the corresponding inventory management business process according to the needed business to perform inventory management.
However, the service management scheme with the solidified service flow function cannot meet the differentiated requirements of different users, and is poor in flexibility; when a new service is added, the related service flows need to be combed, and the service flows are secondarily developed, so that the service development speed is influenced.
Disclosure of Invention
In view of this, the present invention provides a method, an apparatus, and a device for processing a service, which are used to improve flexibility of service management and increase a 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 services to be executed according to the service requests, wherein each service scene is pre-configured 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.
As an optional implementation manner in this embodiment of the present invention, after receiving the service request, before executing the target component corresponding to the target service according to the 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 in the embodiment of the present invention, acquiring a target component corresponding to a target service according to a service request includes:
identifying the service identity of the target service according to the service request;
determining a target service template bound by the service identity of the target service according to a binding relationship between the service identity and the service template, wherein the service template comprises a preset component set;
and acquiring the target component according to the target service template.
As an optional implementation manner in the embodiment of the present invention, a service request carries service identity information, and a service identity of a target service is identified according to the service request, including:
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 in 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 a first mapping relation is stored in the service identity tree.
As an optional implementation manner in this 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 relationship among the services.
As an optional implementation manner in the embodiment of the present invention, a service request carries a service flow identifier, a service template includes at least one service flow, the service flow includes a component identifier of a required component, and acquiring 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 identifier;
and acquiring a target component corresponding to the component identifier in the target business process.
As an optional implementation manner in the embodiment of the present invention, the business process further includes an execution sequence of each component, and the executing of the target component according to the component execution rule corresponding to the business scenario includes:
and executing the target components according to the component execution rules corresponding to the business scenes and the execution sequence in the target business process.
As an optional implementation manner in the embodiment of the present invention, the service request carries service scenario information, and the identifying, according to the service request, a service scenario of a target service to be executed 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 in the embodiment of the present invention, the service request carries service operation parameters, and the executing of 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 according to the component execution rule corresponding to the service operation parameter and the service scene.
As an optional implementation manner 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 services to be executed according to the inventory management service request, wherein each service scene is pre-configured 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 to generate 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 the service scenes of the target service to be executed according to the service request, wherein each service scene is pre-configured 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 optional implementation manner of the embodiment of the present invention, the service request is an inventory management service request.
As an optional implementation manner of the embodiment of the present invention, the apparatus further includes: and the acquisition module is used for acquiring the target component corresponding to the target service to be executed according to the service request after the receiving module receives the service request and before the execution module executes 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, 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 bound by the service identity of the target service according to the binding relationship between the service identity and the service template, wherein the service template comprises a pre-configured component set;
and the acquisition unit is used for acquiring the target component according to the target service template.
As an optional implementation manner in 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 a first mapping relation is stored in the service identity tree.
As an optional implementation manner of the embodiment of the present invention, the apparatus further includes:
and 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 identifier;
and acquiring 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 business process further includes an execution sequence of each component, and the execution module is specifically configured to: and executing the target components according to the component execution rules corresponding to the business scenes and the execution sequence in the target business process.
As an optional implementation manner in the embodiment of the present invention, the service request carries service scenario 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 in the embodiment of the present invention, the service request carries service operation parameters, 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 the service scenes of the target service to be executed according to the inventory management service request, wherein each service scene is pre-configured 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 to generate the inventory accounting data.
In a fifth aspect, an embodiment of the present invention provides a service processing device, including: a memory for storing a computer program and a processor; the processor is configured to perform the method of any of the embodiments of the first aspect, the second aspect or 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: client and the service processing device of 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, where the computer program, when executed by a processor, implements the method described in the first aspect, the second aspect, or any implementation manner of the first aspect.
According to the service processing method, the device and the equipment provided by the embodiment of the invention, after the service request is received, the service scene of the target service is identified according to the service request, the target component corresponding to the target service is executed according to the component execution rule corresponding to the service scene, and 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 needs, and the flexibility of service management and the service development speed can be improved.
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 illustrating a process for obtaining a target component according to an embodiment of the present invention;
FIG. 3 is a schematic diagram of a model of a service identity tree according to an embodiment of the present invention;
fig. 4 is a schematic 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 apparatus 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 due to the solidification of a service flow, the embodiment of the invention provides a service processing method, a device and equipment, which are mainly based on the idea of componentization design, logically componentize each service of the service flow, separate a service scene from a specific service flow, identify the service scene of a target service according to the service request after receiving the service request, and then execute the target component corresponding to the target service 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, thereby improving the flexibility of service management and the service development speed.
The method, the apparatus, and the device for processing the service provided in the embodiments of the present invention may be applied to an inventory management system or other service management systems.
Embodiments of the present invention will be described below with reference to the accompanying drawings.
Fig. 1 is a schematic flow diagram of a service processing method according to an embodiment of the present invention, and as shown in fig. 1, the service processing method according to this 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 by a client, and the service processing device may receive the service request.
S101, acquiring a target component corresponding to a target service to be executed according to the received service request.
Specifically, various management services are implemented through various service flows, various service logics in the service flows can be packaged in advance as various components and stored in a component library, and a target component is a component obtained after componentization processing is performed on various service logics required for implementing the target service.
In specific implementation, the service processing device may preset a corresponding relationship between a service and a component, and after receiving a service request, may identify a target service to be executed according to the service request, and then obtain a target component corresponding to the target service according to the corresponding relationship.
The user can also pre-configure the service identity of the service, bind a service template for each service identity, and configure the component 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 receiving the service request, the target component can be obtained by the method shown in fig. 2, so that the user can quickly cope with the change of the service by customizing the service identity and the service template corresponding to the service identity, and the effects of improving the flexibility of service management and the service development speed are achieved. Fig. 2 is a schematic flowchart of a process for acquiring a target component according to an embodiment of the present invention, and as shown in fig. 2, the method may include the following steps:
and 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 parse the service request through the policy engine to identify the service identity of the target service. The service identity is used for indicating specific service, and the service request can carry service identity information. The service identity information may be a service identity identifier; 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 performing routing 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, the service identity information in the service request may be matched with the first service rule in the preset first mapping relationship, and the service identity corresponding to the matched first service rule is determined as the service identity of the target service.
For example, the first service rule corresponding to the service identity of the target service K is: the user identity is K1 (sub rule R1), the commodity is K2 (sub rule R2), and the warehouse is K3 (sub rule R3); the business 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 may be sequentially matched, for example: matching the user identity (namely whether K1 is K1), matching the commodity from the matched first business rule after the matching is successful (namely whether K2 is K2), matching the warehouse from the matched first business rule after the matching is successful (namely whether K3 is K3), wherein the matching of the three sub-rules is successful, namely the business identity of the target business A is identified.
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, that is, when the service identity information in the service request is matched with the first service rule in the first mapping relationship, the service identity information may be matched with the first service rule stored in the pre-established service identity tree.
Specifically, some services may include sub-services, such as: the enterprise A self-service business comprises a sub-business health business, an international direct-service business, an online supermarket business and the like; the first service rule of each sub-service belonging to a certain service is the first service rule containing the service, and when the service identity tree is established, the nodes corresponding to each sub-service of the service are all the sub-nodes of the nodes corresponding to the service. The node (i.e., the parent node) corresponding to the service stores the first service rule of the service, and the child node of the parent node may store the first service rule of the child service or the service rule of the first service rule of the child service except the first service rule of the parent node.
Continuing with the foregoing example as an example, assume that the service K is a sub-service of the service N, the service N is a sub-service of the service M, the first service rule of the service K includes three sub-rules R1, R2, and R3, the first service rule of the service N includes two sub-rules R1 and R2, and the first service rule of the service M includes one sub-rule 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; during storage, the node corresponding to the service M stores the sub-rule R1, the node corresponding to the service N may store the sub-rules R1 and R2, or only store R2, and the node corresponding to the service K may store the sub-rules R1, R2, and R3, or only store R3. In addition, the node corresponding to each service may further store a service identity (specifically, a service identity) of the service or a binding relationship between the service identity and the service template (specifically, a binding relationship between the service identity and the service template).
Fig. 3 is a schematic diagram of a model of a service identity tree according to an embodiment of the present invention, and 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 child nodes, and each child node may also include 0 or at least one child node; the number of child nodes included in each node and the depth of the service identity tree are determined according to the service relationship between the service established by the user and each service, in fig. 3, the root node includes three child nodes (i.e., service a, service B, and service C), the node corresponding to service a includes two child nodes (i.e., child service a1 and child service a2), the node corresponding to service B includes one child node (i.e., child service B1), the node corresponding to service C includes 0 child nodes, and the depth of the tree is 3 for example.
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 the service identity information in the service request meets a first service rule in the node when traversing to a certain node, if not, continuing to traverse the next node according to the width, and finishing traversing when traversing to each node according to the width; if yes, recording the node, checking whether a child node exists in the node, and if not, ending traversal; if the node exists, the traversal operation is continuously executed on each sub-node under the node until the traversal is finished, and the service identity (such as a service identity identifier) stored in the node which is recorded last is output and is taken as the service identity of the target service.
S1012, determining a target service template bound by the service identity of the target service according to the binding relationship between the service identity and the service template configured in advance.
Specifically, a user may pre-configure a binding relationship between a service identity of a service and a service template at a client, where the service template may include at least one service process, for example: warehousing-in flow, warehousing-out flow, occupation cancellation flow, confirmation flow and the like; for each business process, a user can adopt a process template preset by the system, or self-define the process template according to needs, and configure a corresponding component set and an execution sequence of each component.
After the service processing device identifies the service identity of the target service, a service template (i.e., a 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, the binding relationship between the service identity corresponding to the node and the service template is stored in each node except the root node; the binding relationship may also be stored in other locations, and only the service identity is stored in the node 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 a plurality of service identities, so that the service template can be reused.
And S1013, acquiring the target assembly according to the target service template.
Specifically, the business process in the business template may include a component identifier of a required component, and the business processing device may obtain a corresponding target component from the component library according to the component identifier.
As described above, the business process may include at least one business process, and when the target component is obtained, the target business process may be determined according to the business request, and then the corresponding target component is obtained 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 a corresponding target service flow from the target service template according to the service flow identifier, and then obtain 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 is executed after step S100 is executed.
And S102, identifying the service scene of the target service according to the service request.
In the embodiment, the service scene is separated from the concrete service flow and abstracted, so that a user can configure the service scene of the service according to the need of the user, the requirement of rapidly developing the service is met, and meanwhile, the flexibility of service management is improved; in addition, the service flow among different service scenes can be isolated, so that monitoring is facilitated, and operators can be helped to quickly position and correct the malposition.
Specifically, the user configures a service scenario of a service, that is, a service scenario of a service template bound by a service identity of the service. When the service scenes are specifically configured, a user can select a required service scene from service scenes preset by a system, can also customize the service scene, and can also not configure the service scene, wherein the service scene contained in the service is a default service scene; that is, one service template may configure 0 or at least one service scenario. Each service scenario is pre-configured with a corresponding component execution rule, a process of configuring a service scenario by a user is also a process of configuring a component execution rule, and the component execution rule may be to change an execution result and/or an execution policy (e.g., not to execute) of a certain component or certain components.
For example, the default service scenario of the service a is: synchronizing inventory data to the e-commerce platform 1; the user adds a service scene A according to the requirement of service development: the inventory data is synchronized to the e-commerce platform 1 and the e-commerce platform 2. Another example is: the default service scenario of service B is: the stock proportion of the e-commerce platform 1 is 50%, and the stock proportion of the e-commerce platform 2 is 50%; the user adds a service scene B according to the requirement of service development: the stock proportion of the e-commerce platform 1 is 80%, and the stock 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 a corresponding service scene. Similar to the identification of the service identity, when identifying the service scene, the service request may carry service scene information, which may be a service scene identifier, and may also include at least one of user identity, commodity information, warehouse information, transaction type, and other information that may be used to identify the service scene, and correspondingly, the service scene may be represented by a service rule (referred to as a second service rule), and when identifying the service scene, the second service rule may be used to perform route identification of the service scene, so as to improve the identification efficiency of the service scene.
In specific implementation, a second mapping relationship may be preset, where the second mapping relationship includes a corresponding relationship between a service scenario and a second service rule, and when a service request is received, service scenario information in the service request may be matched with the second service rule in the preset second mapping relationship; 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 scene is similar to the identification process of the service identity, and is not described herein again.
It should be noted that, in this embodiment, there is no strict execution timing relationship between steps S102 and S101, and step S102 may be executed after step S101, or before step S101, or simultaneously with 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 scenario is identified, the service processing device may 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 scenario, so that the components may respond differently in different service scenarios.
In this embodiment, the service request may carry service operation parameters, for example: and after the service scene is identified, the target component can be executed according to the component execution rule and the service operation parameter corresponding to the service scene.
In addition, as described above, the business process may include an execution sequence of each component, and when the target component is executed, 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.
In the service processing method provided by this embodiment, after a target component corresponding to a target service to be executed is acquired according to a received service request, a service scene of the target service is identified according to the service request, and finally the target component is executed according to a component execution rule corresponding to the service scene, so that the service scene and a 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 as required, and components in the service flow realize different functions, thereby effectively improving flexibility of service management; and when a user adds a new service, the method can be directly realized by configuring a service scene without carrying out secondary development on a service flow, so that the service development speed can be improved.
Fig. 4 is a flowchart illustrating another service processing method according to an embodiment of the present invention, which is a specific implementation manner for processing an inventory management service. As shown in fig. 4, the method provided by this embodiment may include the following steps:
s201, receiving an inventory management service request.
Specifically, when the business side needs to perform an inventory operation, such as: and warehousing or occupying a warehouse and the like, an inventory management service request can be initiated through a client, and the service processing equipment can receive the service request.
S202, identifying a service scene of the target service to be executed according to the inventory management service request.
Specifically, the service party may pre-configure the service scenario of the inventory management service according to its own requirements, so that the components in the service flow of the inventory management service implement different inventory management policies through different component execution rules, that is, each service scenario has a corresponding component execution rule.
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, then executes the component based on the component execution rule corresponding to the service scene, and realizes the inventory management service according to the corresponding inventory management strategy; for a specific identification process of the service scenario, reference may be made to the related description of step S102, which is not described herein again.
S203, 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.
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 relevant data such as inventory operation lists, idempotent operation records and the like; the service checking component is used for checking whether inventory operation initiated by a service party is operated or not, checking whether a corresponding warehouse indicates the requirement of the service party or not and the like; the business conversion component is used for converting the inventory operation flow initiated by the business party into a corresponding inventory accounting operation object, for example: adding the quantity of C pieces of commodities with the inventory type B of the warehouse A; the inventory accounting component is used for recording inventory operation data of business parties into a database and generating inventory accounting data. Various inventory management services may be combined through these types of components to achieve corresponding functionality.
After the business processing device identifies the business scene, the target component corresponding to the target business can be executed according to the component execution rule corresponding to the business scene, and the inventory accounting data is generated.
In the service processing method provided by this embodiment, after receiving the inventory management service request, the service scenario of the target service to be executed is identified according to the inventory management service request, then the target component corresponding to the target service is executed according to the component execution rule corresponding to the service scenario, so as to generate inventory accounting data, and the service scenario is separated from the service flow and abstracted, so that the service party can configure the service scenario and the component execution rule corresponding to the service scenario as required, so that the components in the service flow implement different inventory management policies, and thus the flexibility of service management can be effectively improved; and when a service party adds a service, the service can be directly realized by configuring a service scene without carrying out secondary development on a service flow, so that the service development speed can be effectively improved.
Based on the same inventive concept, as an implementation of the foregoing method, an embodiment of the present invention provides a service processing apparatus, where the apparatus embodiment corresponds to the foregoing method embodiment, and for convenience of reading, details in the foregoing method embodiment are not repeated in this apparatus embodiment one by one, but it should be clear that the apparatus in this embodiment can correspondingly implement all the contents in the foregoing method embodiment.
Fig. 5 is a schematic structural diagram of a service processing apparatus according to an embodiment of the present invention, and as shown in fig. 5, a service processing apparatus 10 according to this embodiment includes:
a receiving module 100, configured to receive a service request;
the identifying module 120 is configured to identify service scenarios of a target service to be executed according to a service request, where each service scenario is preconfigured with a corresponding component execution rule;
the executing module 130 is configured to execute a target component corresponding to a target service according to a component execution rule corresponding to a service scenario.
Wherein the service request may be an inventory management service request.
As an optional implementation manner of the embodiment of the present invention, the apparatus further includes:
the obtaining module 110 is configured to obtain a target component corresponding to a target service according to a service request after the receiving module 100 receives the service request and 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 optional implementation manner 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, according to a binding relationship between a preconfigured service identity and a service template, a target service template to which the service identity of the target service is bound, where the service template includes a preconfigured component set;
an obtaining unit 113, configured to obtain the target component according to the target service template.
As an optional implementation manner in 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 a first mapping relation is stored in the service identity tree.
As an optional 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 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 identifier;
and acquiring 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 be specifically configured to: and executing the target components according to the component execution rules corresponding to the business scenes and the execution sequence in the target business process.
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 in the embodiment of the present invention, the service request carries service operation parameters, 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 apparatus provided in this embodiment may execute the method embodiments, and the implementation principle and the technical effect are similar, which are not 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 identification 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 apparatus provided in this embodiment may execute the method embodiments, and the implementation principle and the technical effect are similar, which are not 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, and as shown in fig. 7, the service processing device according to the embodiment includes: a memory 310 and a processor 320, the memory 310 being for storing computer programs; the processor 320 is configured to execute the method according to the above-described method embodiment when the computer program is called.
The service processing device provided in this embodiment may execute the method embodiments, and the implementation principle and the technical effect are similar, which are not described herein again.
An embodiment of the present invention further provides a service management system, which includes: client and the service processing device described in the above embodiments.
Embodiments of the present invention further provide a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the method described in the above method embodiments.
As will be appreciated by one skilled in the art, 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 in the medium.
The Processor may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic, discrete hardware components, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). The memory is an example of a computer-readable medium.
Computer readable media include both permanent and non-permanent, removable and non-removable storage media. Storage media may implement information storage by any method or technology, and the information may be computer-readable instructions, data structures, modules of a program, or other data. Examples of computer storage media 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 Discs (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solution of the present invention, and not to limit the same; while the invention has been described in detail and with reference to the foregoing embodiments, it will be understood by those skilled in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present invention.
Claims (16)
1. A method for processing a service, comprising:
receiving a service request;
identifying service scenes of target services to be executed according to the service requests, wherein each service scene is pre-configured 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.
2. The method according to claim 1, wherein after the receiving the service request and before the executing the target component corresponding to the target service according to the component execution rule corresponding to the service scenario, the method further comprises:
and acquiring a target component corresponding to the target service according to the service request.
3. The method according to claim 2, wherein the obtaining the target component corresponding to the target service according to the service request includes:
identifying the service identity of the target service according to the service request;
determining a target service template bound by the service identity of the target service according to a binding relationship between a pre-configured service identity and a service template, wherein the service template comprises a pre-configured component set;
and acquiring the target assembly according to the target service template.
4. The method of claim 3, wherein the service request carries service identity information, and the identifying the service identity of the target service according to the service request comprises:
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 a 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.
5. The method according to claim 4, wherein the matching the service identity information with the first service rule in the preset first mapping relationship comprises:
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.
6. The method of claim 5, wherein before the identifying the service identity of the target service according to the service request, the method further comprises:
and establishing the service identity tree according to the service relationship among the services.
7. The method according to claim 3, 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.
8. The method according to claim 7, 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.
9. The method of claim 1, wherein the service request carries service scenario information, and the identifying a service scenario of a target service to be executed according to the service request comprises:
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 a 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.
10. The method of claim 1, wherein the service request carries service operation parameters, and the executing the target component corresponding to the target service according to the component execution rule corresponding to the service scenario comprises:
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.
11. A method for processing a service, comprising:
receiving an inventory management service request;
identifying service scenes of target services to be executed according to the inventory management service request, wherein each service scene is pre-configured 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 to generate inventory accounting data.
12. A traffic processing apparatus, comprising:
the receiving module is used for receiving the service request;
the identification module is used for identifying the service scenes of the target service to be executed according to the service request, wherein each service scene is pre-configured 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.
13. A traffic processing apparatus, comprising:
the receiving module is used for receiving the inventory management service request;
the identification module is used for identifying the service scenes of the target service to be executed according to the inventory management service request, wherein each service scene is pre-configured with a corresponding component execution rule;
and the generating module is used for executing the target component corresponding to the target business according to the component execution rule corresponding to the business scene to generate the inventory accounting data.
14. A traffic processing device, comprising: a memory for storing a computer program and a processor; the processor is adapted to perform the method of any of claims 1-11 when the computer program is invoked.
15. A traffic management system, comprising: a client and a traffic processing device as claimed in claim 14.
16. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the method according to any one of claims 1-11.
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 true CN111435495A (en) | 2020-07-21 |
| CN111435495B 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) |
Cited By (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 |
| CN113516541A (en) * | 2021-09-14 | 2021-10-19 | 杭州小电科技股份有限公司 | Dynamic configuration method and device for store distribution scene and electronic device |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104639451B (en) * | 2013-11-14 | 2019-03-22 | 中兴通讯股份有限公司 | Data flow shunt 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 |
| CN107038042B (en) * | 2017-02-07 | 2020-08-28 | 阿里巴巴集团控股有限公司 | Service execution method and device |
| CN107506181A (en) * | 2017-07-17 | 2017-12-22 | 阿里巴巴集团控股有限公司 | Business processing, data processing method, device and electronic equipment |
| CN108153551B (en) * | 2017-12-11 | 2021-07-23 | 中国民生银行股份有限公司 | Method and device for displaying business process page |
-
2019
- 2019-01-14 CN CN201910030671.5A patent/CN111435495B/en active Active
Cited By (3)
| 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 |
| CN113516541A (en) * | 2021-09-14 | 2021-10-19 | 杭州小电科技股份有限公司 | Dynamic configuration method and device for store distribution scene and electronic device |
| CN113516541B (en) * | 2021-09-14 | 2022-01-11 | 杭州小电科技股份有限公司 | Dynamic configuration method and device for store distribution scene and electronic device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111435495B (en) | 2023-06-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11711268B2 (en) | Methods and apparatus to execute a workload in an edge environment | |
| US10257289B2 (en) | Capturing configuration items from hybrid-cloud provisioning data | |
| CN109933593B (en) | Asset data recording method, device and equipment | |
| JP2019525333A (en) | Terminal rule engine device and terminal rule operating method | |
| US9424403B2 (en) | Obtaining software asset insight by analyzing collected metrics using analytic services | |
| CN110175201A (en) | Business data processing method, system, device and electronic equipment | |
| CN111435495A (en) | Service processing method, device and equipment | |
| CN106157066A (en) | Mapping relations processing method, system and information processing platform equipment | |
| CN108924185A (en) | Interface creation method and device | |
| CN111142849A (en) | Flow processing method and device, storage medium and processor | |
| CN111008404A (en) | Service call auditing method, equipment and medium based on block chain | |
| CN113923268A (en) | Analysis method, equipment and storage medium for multi-version communication protocol | |
| CN112035156A (en) | E-commerce platform docking device, method, equipment and medium | |
| CN106855821B (en) | Distributed transaction processing method and device | |
| CN111131474A (en) | Method, device and medium for managing user protocol based on block chain | |
| CN110401925A (en) | A kind of generation method and device of communication message | |
| CN114491662B (en) | Block chain-based data asset auditing method, system and equipment | |
| US11647377B2 (en) | Mobile device roaming optimization and operation | |
| CN115063198A (en) | Method, equipment and medium for performing data access on EPR (expressed resource Server) software under SaaS (software as a service) service | |
| CN107135191B (en) | Method and device for checking integrity of distributed service processing | |
| JP6649502B2 (en) | System and method for resolving conflicts in order management of data products | |
| US20180341463A1 (en) | Software object definition and integration | |
| CN112486565A (en) | Containerization-based continuous integration method and equipment | |
| CN113687973B (en) | Control method, equipment and medium for log dynamic output | |
| CN106844056B (en) | Hadoop big data platform multi-tenant job management method and system |
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 |