Service execution method and device, electronic equipment and computer readable storage medium

Abstract

The invention provides a business execution method and device, electronic equipment and a computer readable storage medium, and can be applied to the technical field of intelligent logistics, the technical field of intelligent supply chains and the technical field of big data. Determining M performance businesses to be executed in the process of providing the target service and an execution sequence of the M performance businesses; determining M trigger track nodes associated with the M performance services from the N track nodes; and configuring a standard style for each trigger track node according to a pre-constructed track standard style sheet, generating a performance trigger rule in combination with the execution sequence of the M performance services, and triggering the M performance services to be executed in sequence based on the performance trigger rule.

Description

Technical Field

[0001] The present disclosure relates to the fields of smart logistics technology, smart supply chain technology, and big data technology, and specifically to a business execution method, device, equipment, medium, and program product. Background Art

[0002] With the rapid development of international cross-border logistics business, logistics enterprise service platforms need to provide more complete logistics services to external merchants, such as cross-border order fulfillment monitoring functions, timely and comprehensive tracking of the delivery progress and timeliness of goods in each fulfillment link, and provide personalized merchant trajectory production functions with flexible configuration, real-time effectiveness and support for multi-channel feedback according to the ever-changing trajectory customization needs of different merchants. At the same time, it is also necessary to provide operators with pre-set and timely fulfillment links and logistics trajectory abnormality warning capabilities, so that operators can discover and handle order fulfillment anomalies in advance of customers and reduce related customer complaints.

[0003] In the process of realizing the concept of the present disclosure, the inventors found that the execution methods of logistics services in related technologies have problems such as complex execution logic, low execution efficiency, and high system interface development costs. For example, the fulfillment trajectories of cross-border orders are scattered in various downstream business execution systems, and the issuance and monitoring of each fulfillment task need to be connected to each business execution system one by one, resulting in complex execution logic and low execution efficiency. The node styles, execution logic, etc. of each business execution system are not unified, and there is no strong business association between them. Therefore, when connecting to a new business execution system, the previous trajectory connection logic cannot be reused, and it is necessary to re-plan and develop a new trajectory connection interface between systems, and the customized development cost is high. Summary of the invention

[0004] In view of the above problems, the present disclosure provides a service execution method, apparatus, device, medium and program product.

[0005] In one aspect of the present disclosure, a service execution method is provided, comprising:

[0006] According to the configuration information of the target service, determine the M performance services to be performed in the process of providing the target service and the execution order of the M performance services, wherein the M performance services are executed one by one through the M service execution systems, and the M performance services involve N trajectory nodes, where M and N are positive integers, and N≥M;

[0007] Determine M trigger trajectory nodes associated with M contract performance services from the N trajectory nodes, wherein the M trigger trajectory nodes are used to trigger the M service execution systems to execute their respective corresponding contract performance services one by one;

[0008] According to the pre-built trajectory standard style table, a standard style is configured for each triggered trajectory node, and the fulfillment trigger rule is generated in combination with the execution order of M fulfillment services, wherein the information in the trajectory standard style table includes the standard styles of all trajectory nodes involved in all services;

[0009] Based on the fulfillment triggering rules, M fulfillment businesses are triggered to be executed sequentially.

[0010] According to an embodiment of the present disclosure, the fulfillment trigger rule is used to characterize the standard style and execution order of M trigger trajectory nodes, and triggering the M fulfillment businesses to be executed sequentially based on the fulfillment trigger rule includes:

[0011] After the Lth business execution system is triggered to start executing the Lth fulfillment business, the real-time trajectory feedback information sent by the Lth business execution system is received, wherein the real-time trajectory feedback information includes: the original style of the target trajectory node currently transferred by the Lth business execution system, L is a positive integer, and 1≤L<M;

[0012] Based on a pre-built standard style mapping table, the original style of the target trajectory node is converted into a standard style, wherein the standard style mapping table includes: a mapping relationship between the original style and the standard style of all trajectory nodes involved in the full service;

[0013] When the standard pattern of the target trajectory node matches the standard pattern of the target trigger trajectory node associated with the L+1th fulfillment business, the L+1th business execution system is triggered to start executing the L+1th fulfillment business.

[0014] According to an embodiment of the present disclosure, it also includes:

[0015] When the standard pattern of the target trajectory node does not match the standard pattern of the target trigger trajectory node associated with the L+1th fulfillment business, the L+1th business execution system is suspended from starting to execute the L+1th fulfillment business.

[0016] According to an embodiment of the present disclosure, it also includes:

[0017] According to the historical trajectory feedback information sent by the first L business execution systems, determine the original styles of multiple historical trajectory nodes that have been circulated by the first L business execution systems;

[0018] According to the preset execution order of the N trajectory nodes, multiple historical trajectory nodes marked with the original style are concatenated to form an original trajectory chain;

[0019] Based on a pre-built standard style mapping table, the original styles of multiple historical trajectory nodes contained in the original trajectory chain are converted into standard styles to form a standard trajectory chain for the target service.

[0020] According to an embodiment of the present disclosure, it also includes:

[0021] Obtain the target packaging needs of target customers;

[0022] Querying a target packaging style mapping table corresponding to the target packaging requirement, wherein the target packaging style mapping table includes: a mapping relationship between a standard style of all trajectory nodes involved in the full service and a target packaging style, wherein the target packaging style meets the target packaging requirement;

[0023] Based on the target packaging style mapping table, the standard styles of multiple historical trajectory nodes included in the standard trajectory chain are converted into the target packaging style to form a packaging trajectory chain for the target service.

[0024] According to an embodiment of the present disclosure, the standard style of the full track node includes at least: a standard node name, a standard node code, and a standard display script;

[0025] The target packaging style mapping table is constructed by the following method:

[0026] Analyze the target packaging requirements and determine the target packaging style of all trajectory nodes. The target packaging style at least includes: packaging node name, packaging node code, and packaging display words;

[0027] Bind the standard node name to the packaged node name, bind the standard node code to the packaged node code, and bind the standard display words to the packaged display words.

[0028] According to an embodiment of the present disclosure, the standard style mapping table is constructed by the following method:

[0029] Obtain the original style of all track nodes from the full business system or third-party service provider. The original style includes at least: original node name, original node code, and original display script;

[0030] According to the preset standard node configuration rules, the original node name is bound to the standard node name, the original node code is bound to the standard node code, and the original display words are bound to the standard display words.

[0031] According to an embodiment of the present disclosure, it also includes:

[0032] Determine S warning trajectory nodes that need to be monitored during the execution of the target service from N trajectory nodes, N ≥ S;

[0033] Configure warning rules for S warning trajectory nodes;

[0034] The S warning trajectory nodes are monitored according to the warning rules.

[0035] According to an embodiment of the present disclosure, monitoring S warning trajectory nodes according to the warning rule includes:

[0036] Obtain the first timestamp corresponding to the completion of the reference trajectory node, wherein the reference trajectory node is the previous trajectory node of the warning trajectory node, or the reference trajectory node is the first trajectory node corresponding to the start of the first fulfillment business;

[0037] Obtain a second timestamp corresponding to the target monitoring time period;

[0038] When the time interval between the second timestamp and the first timestamp is greater than a preset time threshold, a warning prompt is issued for the warning trajectory node.

[0039] Another aspect of the present disclosure provides a service execution device, including:

[0040] A first determination module is used to determine, according to the configuration information of the target service, M performance services to be performed in the process of providing the target service and the execution order of the M performance services, wherein the M performance services are executed one by one through the M service execution systems, the M performance services involve N trajectory nodes, M and N are positive integers, and N≥M;

[0041] A second determination module is used to determine M trigger trajectory nodes associated with M contract performance services from the N trajectory nodes, wherein the M trigger trajectory nodes are used to trigger the M service execution systems to execute their respective corresponding contract performance services in a one-to-one correspondence;

[0042] The style configuration module is used to configure the standard style for each triggered trajectory node according to the pre-built trajectory standard style table, and generate the fulfillment trigger rule in combination with the execution order of M fulfillment services, wherein the information in the trajectory standard style table includes the standard styles of all trajectory nodes involved in all services;

[0043] The execution module triggers M fulfillment businesses to be executed sequentially based on the fulfillment trigger rules.

[0044] According to an embodiment of the present disclosure, the fulfillment trigger rule is used to characterize the standard style and execution order of M trigger trajectory nodes, and the execution module includes:

[0045] A feedback receiving unit is used to receive real-time trajectory feedback information sent by the Lth business execution system after triggering the Lth business execution system to start executing the Lth contract performance business, wherein the real-time trajectory feedback information includes: the original style of the target trajectory node currently transferred by the Lth business execution system, L is a positive integer, and 1≤L<M;

[0046] A first conversion unit is configured to convert an original style of a target trajectory node into a standard style based on a pre-built standard style mapping table, wherein the standard style mapping table includes: a mapping relationship between the original style of all trajectory nodes involved in the full service and the standard style;

[0047] The trigger unit is used to trigger the L+1th business execution system to start executing the L+1th fulfillment business when the standard pattern of the target trajectory node matches the standard pattern of the target trigger trajectory node associated with the L+1th fulfillment business.

[0048] According to an embodiment of the present disclosure, the execution module further includes:

[0049] The suspension execution unit is used to suspend the L+1th business execution system from starting to execute the L+1th fulfillment business when the standard pattern of the target trajectory node does not match the standard pattern of the target trigger trajectory node associated with the L+1th fulfillment business.

[0050] According to an embodiment of the present disclosure, the execution module further includes:

[0051] A determination unit, configured to determine, based on the historical trajectory feedback information sent by the first L business execution systems, the original styles of the plurality of historical trajectory nodes that have been circulated by the first L business execution systems;

[0052] A concatenation unit, used for concatenating a plurality of historical trajectory nodes marked with original styles to form an original trajectory chain according to a preset execution order of the N trajectory nodes;

[0053] The second conversion unit is used to convert the original styles of multiple historical trajectory nodes included in the original trajectory chain into a standard style based on a pre-built standard style mapping table to form a standard trajectory chain for the target service.

[0054] According to an embodiment of the present disclosure, the execution module further includes:

[0055] A first acquisition unit is used to acquire target packaging requirements of target customers;

[0056] A query unit, configured to query a target packaging style mapping table corresponding to a target packaging requirement, wherein the target packaging style mapping table includes: a mapping relationship between a standard style of a full set of trajectory nodes involved in a full set of services and a target packaging style, wherein the target packaging style satisfies the target packaging requirement;

[0057] The third conversion unit is used to convert the standard styles of multiple historical track nodes included in the standard track chain into the target packaging style based on the target packaging style mapping table to form a packaging track chain for the target service.

[0058] According to an embodiment of the present disclosure, the standard style of the full track node includes at least: a standard node name, a standard node code, and a standard display script;

[0059] The above device also includes a first construction module, which is used to construct a target packaging style mapping table. The first construction module includes:

[0060] A parsing unit is used to parse the target packaging requirements and determine the target packaging style of the full trajectory node. The target packaging style at least includes: packaging node name, packaging node code, and packaging display words;

[0061] The first binding unit is used to bind the standard node name to the packaged node name, bind the standard node code to the packaged node code, and bind the standard display words to the packaged display words.

[0062] According to an embodiment of the present disclosure, the above-mentioned device further includes a second construction module, which is used to construct a standard style mapping table, and the second construction module includes:

[0063] The second acquisition unit is used to acquire the original style of the full track node from the full business system or a third-party service provider, where the original style at least includes: the original node name, the original node code, and the original display script;

[0064] The second binding unit is used to bind the original node name to the standard node name, bind the original node code to the standard node code, and bind the original display words to the standard display words according to the preset standard node configuration rules.

[0065] According to an embodiment of the present disclosure, the above device further includes:

[0066] A third determination module is used to determine S warning trajectory nodes that need to be monitored during the execution of the target service from the N trajectory nodes, N ≥ S;

[0067] The warning rule configuration module is used to configure warning rules for S warning trajectory nodes;

[0068] The monitoring module is used to monitor the S warning trajectory nodes according to the warning rules.

[0069] According to an embodiment of the present disclosure, the monitoring module includes:

[0070] A third acquisition unit is used to acquire a first timestamp corresponding to when the reference trajectory node is executed, wherein the reference trajectory node is a previous trajectory node of the warning trajectory node, or the reference trajectory node is a first trajectory node corresponding to the start of execution of the first performance business;

[0071] A fourth acquisition unit, configured to acquire a second timestamp corresponding to a target monitoring time period;

[0072] The prompt unit is used to issue a warning prompt for the warning trajectory node when the time interval between the second timestamp and the first timestamp is greater than a preset time threshold.

[0073] Another aspect of the present disclosure provides an electronic device, comprising: one or more processors; and a memory for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors execute the above-mentioned service execution method.

[0074] Another aspect of the present disclosure further provides a computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, causes the processor to execute the above-mentioned service execution method.

[0075] Another aspect of the present disclosure further provides a computer program product, including a computer program, which implements the above-mentioned service execution method when executed by a processor.

[0076] According to the embodiments of the present disclosure, by determining the trigger trajectory nodes associated with each fulfillment business, and configuring a standard style for each trigger trajectory node according to a pre-built trajectory standard style table, and generating a fulfillment trigger rule in combination with the execution order of multiple fulfillment businesses, each fulfillment link can be automatically triggered to execute in sequence, solving the problem of complex execution logic and low execution efficiency in the issuance of each segment of fulfillment tasks in related technologies. The trigger trajectory nodes in the generated fulfillment trigger rules adopt a standard style, so the fulfillment trigger rules are a set of rules using a standard style, which can be used to connect to multiple different business execution systems. Even if the node styles, execution logic, etc. of the multiple business execution systems are not unified, and there is no strong business association relationship between them, the previous trajectory docking logic can be reused when connecting to multiple different business systems or connecting to a new business execution system. By defining and configuring a set of reusable standard nodes for different fulfillment platforms based on the pre-built track standard style sheet, a trigger rule common to multiple business systems is formed, achieving non-intrusive decoupling of order status flow and track processing logic. Different docking platforms can reuse most standard nodes, and there is no need to integrate complex business execution system tracks, thereby saving related business planning and development workload. BRIEF DESCRIPTION OF THE DRAWINGS

[0077] The above contents and other objects, features and advantages of the present disclosure will become more apparent through the following description of the embodiments of the present disclosure with reference to the accompanying drawings, in which:

[0078] Figure 1 The application scenario diagram schematically shows the service execution method, apparatus, device, medium and program product according to the embodiments of the present disclosure;

[0079] Figure 2 A flowchart of a service execution method according to an embodiment of the present disclosure is schematically shown;

[0080] Figure 3 A schematic diagram of a method for triggering the sequential execution of multiple fulfillment services and monitoring the execution process according to an embodiment of the present disclosure is shown;

[0081] Figure 4 The schematic diagram shows the principle diagram of data interaction between various systems in the process of constructing the standard style mapping table and the package style mapping table;

[0082] Figure 5 A schematic diagram of a system principle for generating a track chain during the execution of a contract fulfillment business according to an embodiment of the present disclosure is shown;

[0083] Figure 6 A schematic diagram showing a structural block diagram of a service execution device according to an embodiment of the present disclosure; and

[0084] Figure 7 A block diagram of an electronic device suitable for implementing a service execution method according to an embodiment of the present disclosure is schematically shown. DETAILED DESCRIPTION

[0085] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the present disclosure. In the following detailed description, for ease of explanation, many specific details are set forth to provide a comprehensive understanding of the embodiments of the present disclosure. However, it is apparent that one or more embodiments may also be implemented without these specific details. In addition, in the following description, descriptions of known structures and technologies are omitted to avoid unnecessary confusion of the concepts of the present disclosure.

[0086] The terms used herein are only for describing specific embodiments and are not intended to limit the present disclosure. The terms "comprise", "include", etc. used herein indicate the existence of the features, steps, operations and / or components, but do not exclude the existence or addition of one or more other features, steps, operations or components.

[0087] All terms (including technical and scientific terms) used herein have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein should be interpreted as having a meaning consistent with the context of this specification, and should not be interpreted in an idealized or overly rigid manner.

[0088] When using expressions such as "at least one of A, B, and C, etc.", they should generally be interpreted according to the meaning of the expression commonly understood by those skilled in the art (for example, "a system having at least one of A, B, and C" should include but is not limited to a system having A alone, B alone, C alone, A and B, A and C, B and C, and / or A, B, C, etc.).

[0089] In the embodiments of the present disclosure, the collection, updating, analysis, processing, use, transmission, provision, disclosure, storage, etc. of the data involved (for example, including but not limited to user personal information) are in compliance with the provisions of relevant laws and regulations, are used for legitimate purposes, and do not violate public order and good morals. In particular, necessary measures are taken for user personal information to prevent illegal access to user personal information data and maintain the security of user personal information, network security, and national security.

[0090] In the embodiments of the present disclosure, the user's authorization or consent is obtained before obtaining or collecting the user's personal information.

[0091] An embodiment of the present disclosure provides a service execution method, including:

[0092] According to the configuration information of the target service, determine the M performance businesses to be executed in the process of providing the target service and the execution order of the M performance businesses, wherein the M performance businesses are executed one-to-one through M business execution systems, and the M performance businesses involve N trajectory nodes, M and N are positive integers, N≥M; determine M trigger trajectory nodes associated with the M performance businesses from the N trajectory nodes, wherein the M trigger trajectory nodes are used to trigger the M business execution systems to execute their respective corresponding performance businesses one-to-one; according to the pre-constructed trajectory standard style sheet, configure a standard style for each trigger trajectory node, and generate a performance trigger rule in combination with the execution order of the M performance businesses, wherein the information in the trajectory standard style sheet includes the standard styles of all trajectory nodes involved in the full amount of services; trigger the M performance businesses to execute sequentially based on the performance trigger rule.

[0093] Figure 1 The application scenario diagram of the service execution method, apparatus, device, medium and program product according to the embodiments of the present disclosure is schematically shown.

[0094] like Figure 1As shown, the application scenario 100 according to this embodiment may include a first terminal device 101, a second terminal device 102, a third terminal device 103, a network 104, and a server 105. The network 104 is used to provide a medium for a communication link between the first terminal device 101, the second terminal device 102, the third terminal device 103, and the server 105. The network 104 may include various connection types, such as wired, wireless communication links, or optical fiber cables, etc.

[0095] The user may use at least one of the first terminal device 101, the second terminal device 102, and the third terminal device 103 to interact with the server 105 through the network 104 to receive or send messages, etc. Various communication client applications may be installed on the first terminal device 101, the second terminal device 102, and the third terminal device 103, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc. (only as examples).

[0096] The first terminal device 101, the second terminal device 102, and the third terminal device 103 may be various electronic devices having display screens and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers, desktop computers, and the like.

[0097] The server 105 may be a server that provides various services, such as a background management server (only as an example) that provides support for websites browsed by users using the first terminal device 101, the second terminal device 102, and the third terminal device 103. The background management server may analyze and process the received data such as user requests, and feed back the processing results (such as web pages, information, or data obtained or generated according to user requests) to the terminal device.

[0098] In the application scenario of the embodiment of the present disclosure, an external merchant user can interact with the server 105 through the network 104 via at least one of the first terminal device 101, the second terminal device 102, and the third terminal device 103, and initiate an order request for logistics services to the server 105. In response to the user request, the server 105 can execute the business execution method of the embodiment of the present disclosure, trigger the sequential execution of the fulfillment business involved in the requested service, and return a fulfillment track list to the customer.

[0099] It should be noted that the service execution method provided in the embodiment of the present disclosure can generally be executed by the server 105. Accordingly, the service execution device provided in the embodiment of the present disclosure can generally be set in the server 105. The service execution method provided in the embodiment of the present disclosure can also be executed by a server or server cluster that is different from the server 105 and can communicate with the first terminal device 101, the second terminal device 102, the third terminal device 103 and / or the server 105. Accordingly, the service execution device provided in the embodiment of the present disclosure can also be set in a server or server cluster that is different from the server 105 and can communicate with the first terminal device 101, the second terminal device 102, the third terminal device 103 and / or the server 105.

[0100] It should be understood that Figure 1 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to implementation requirements.

[0101] The following will be based on Figure 1 The scene described by Figure 2 to Figure 7 The method of the embodiment of the present disclosure is described in detail.

[0102] Figure 2 The flowchart of the service execution method according to the embodiment of the present disclosure is schematically shown.

[0103] like Figure 2 As shown, the service execution method of this embodiment includes operations S201 to S204.

[0104] In operation S201, according to the configuration information of the target service, M performance services to be performed in the process of providing the target service and the execution order of the M performance services are determined, wherein the M performance services are executed one by one through the M service execution systems, and the M performance services involve N trajectory nodes, where M and N are positive integers, and N≥M;

[0105] In operation S202, M trigger trajectory nodes associated with M contract performance services are determined from the N trajectory nodes, wherein the M trigger trajectory nodes are used to trigger the M service execution systems to execute their respective corresponding contract performance services in a one-to-one correspondence;

[0106] In operation S203, according to the pre-built trajectory standard style table, a standard style is configured for each triggered trajectory node, and a fulfillment trigger rule is generated in combination with the execution order of the M fulfillment services, wherein the information in the trajectory standard style table includes the standard styles of all trajectory nodes involved in all services;

[0107] In operation S204, M fulfillment businesses are triggered to be executed sequentially based on the fulfillment triggering rules.

[0108] Figure 3 The schematic diagram shows the principle diagram of a method for triggering the sequential execution of multiple fulfillment businesses and monitoring the execution process according to an embodiment of the present disclosure.

[0109] The following combination Figure 2 , Figure 3 The above method of triggering the execution of multiple fulfillment businesses is described in detail. Figure 3 The method for node monitoring is described in the subsequent embodiments.

[0110] According to the embodiments of the present disclosure, the above method is applied in the scenario of international logistics cross-border business, such as Figure 3 As shown, the system architecture of the embodiment of the present disclosure may include a client, a comprehensive configuration processing system (including a docking platform and a comprehensive processing platform), a business execution system, a third-party logistics service system ( Figure 3 ), wherein the comprehensive configuration processing system is used to execute the business execution method of the embodiment of the present disclosure.

[0111] External merchant customers initiate an order request for logistics services through the client to purchase logistics services. The target service is a specific logistics service purchased by the customer, which can be one of the multiple logistics services provided by the logistics company.

[0112] The process of providing the target service involves M fulfillment businesses, which are respectively for the M fulfillment links of the target service, such as warehousing fulfillment link, delivery fulfillment link, customs clearance fulfillment link, etc. Among them, each fulfillment link involves one or more track nodes, and M fulfillment businesses involve a total of N track nodes, N ≥ M.

[0113] The business execution system includes multiple systems, which can be used to execute multiple fulfillment businesses involved in logistics services one by one. It is responsible for the acceptance and monitoring of fulfillment orders for each stage of warehousing and distribution business of cross-border orders, and feedback the fulfillment progress to the comprehensive configuration processing system.

[0114] The business execution system can be connected to the third-party logistics service system to instruct the third-party logistics service company to complete the logistics delivery tasks.

[0115] The integrated configuration processing system may further include a docking platform and an integrated processing platform.

[0116] The docking platform is responsible for docking with external customers. It is used to receive order requests initiated by merchant customers, parse the requests and extract key information, complete the issuance and import of merchant orders, and distribute data to various business systems according to different business scenarios, such as collection, warehousing, trunk transportation, cross-border transportation, and import and export customs clearance systems, and integrate and monitor the status of the entire order process.

[0117] The comprehensive processing platform is used to unify the order fulfillment tracks of various business execution systems of international logistics, and provide standardized or customized track management, mapping processing and monitoring capabilities for the entire life cycle of orders for docking platforms or external merchant customers.

[0118] In the application scenario of the embodiment of the present disclosure, when connecting to an external merchant system, first configure the order service product according to the business model required by the customer, generate the corresponding order plan by setting the matching rules of the key fulfillment attributes of the order (such as the country of delivery, estimated weight of the package, etc.), and schedule the corresponding fulfillment business to be executed on different downstream business execution systems.

[0119] As the international logistics fulfillment chain is relatively long, and the business complexity and personalization are also high, from the package collection to the overseas delivery, it is necessary to rely on multiple business execution systems deployed in different countries and regions to continue scheduling and jointly complete the fulfillment. Therefore, the full life cycle trajectory of cross-border orders is also provided by each business execution system. In addition to their own system operation nodes, the business execution systems will also connect to the logistics trajectory nodes returned by the third-party service provider systems, and feed back the collected original logistics trajectories to the comprehensive processing platform for processing in real time. After receiving the feedback of the original trajectory, the platform will perform style conversion processing, etc., and then feed back the processed full-process trajectory node link to the external merchant system or user.

[0120] Furthermore, the integrated processing platform pre-builds a track standard style sheet, and the information in the track standard style sheet includes the standard styles of all track nodes involved in all services. The standard style may include standard number, standard name, standard words, etc. For example, for a certain track node, configure the standard name: Warehousing; standard number: 001; standard words: Warehousing.

[0121] According to an embodiment of the present disclosure, based on Figure 3 In the system architecture shown, the above operations S201 to S204 may be, for example:

[0122] In operation S201, the docking platform receives an order request for a target service initiated by a merchant customer, and determines, based on the configuration information of the target service, the M fulfillment businesses to be executed in the process of providing the target service, the execution order of the M fulfillment businesses, the M business execution systems involved, and the N trajectory nodes involved in the entire process.

[0123] Taking the target service as cross-border parcel service as an example, according to the service configuration information, it is determined that the service involves 4 fulfillment links, which are executed in this order: warehousing fulfillment link, delivery fulfillment link, account collection fulfillment link, and customs clearance fulfillment link; each fulfillment link involves one or more track nodes, such as the warehousing fulfillment link involves multiple track nodes including: start, order placement, sorting, ... warehousing, etc.; the delivery fulfillment link involves multiple track nodes including: collection, transit 1, transit 2, etc. Correspondingly, the above 4 fulfillment links are executed through 4 business execution systems, such as the domestic / overseas warehousing management system is responsible for the warehousing fulfillment link, the third-party service provider system is responsible for the delivery fulfillment link, the account collection system is responsible for the account collection fulfillment link, and the customs clearance system is responsible for the customs clearance fulfillment link.

[0124] In operation S202, the docking platform determines M trigger trajectory nodes associated with M performance services from N trajectory nodes. The trigger trajectory nodes are used to trigger the service execution system to execute the corresponding performance services. The operator can configure the trigger trajectory nodes for each performance service of the target service on the docking platform, that is, configure the timing for the service execution system to execute the performance link.

[0125] In operation S203, the docking platform can obtain the pre-built track standard style table from the integrated processing platform, configure the standard style for each trigger track node, and generate the fulfillment trigger rule in combination with the execution order of the M fulfillment businesses. The fulfillment trigger rule is used to characterize the standard style and execution order of the M trigger track nodes. For example, the business personnel selects the appropriate trigger node as the trigger time and binds it to the order according to the pre-planned fulfillment sequence.

[0126] Taking the cross-border parcel order mentioned above as an example, four business execution systems need to be connected and issued:

[0127] 1) Issue a warehouse entry order to the domestic / overseas warehouse management system to execute the fulfillment business, and select the time to place the warehouse entry order, that is, the trigger trajectory node is the "initial" node;

[0128] 2) Issue a cross-border waybill to the third-party service provider system to perform the fulfillment business and select the time to place the cross-border waybill, that is, the trigger trajectory node is the "package arrives at the warehouse" node;

[0129] 3) Send the receivables bill to the collection system to perform the contract fulfillment business, select the time to place the receivables bill, that is, the trigger trajectory node is the "in-warehouse package weighing" node;

[0130] 4) Send a customs clearance application form to the customs clearance system to execute the fulfillment business, select the time to place the customs clearance application form, that is, trigger the trajectory node to be the "arrival at the destination port" node.

[0131] In operation S204, M fulfillment businesses are triggered to be executed sequentially based on the fulfillment triggering rules.

[0132] In the cross-border logistics scenario of the disclosed embodiment, the execution method of logistics services in the related technology has problems such as complex execution logic, low execution efficiency, and high system interface development cost. For example, when a customer places a cross-border order through the platform, it is necessary to first generate a corresponding fulfillment order plan based on the pre-configured service products, and schedule it according to each section of the plan, and issue fulfillment orders to different downstream business execution systems. There is no strong business correlation between the issuance processes of each fulfillment order. It is simply in accordance with the established order of the fulfillment plan until the fulfillment plan is executed. The cross-border order status is transferred through the order results subsequently fed back by the business execution system. If one of the business execution systems ultimately fails to place an order, or the order is successful but cannot be fulfilled (especially If the downstream system is an asynchronous ordering scenario), all other previously issued fulfillment orders must be canceled through their respective business system operations, which not only affects the overall order fulfillment efficiency, but also greatly increases the operation and maintenance pressure; and because the fulfillment tracks of each segment of cross-border orders are scattered in various downstream business execution systems, the issuance and monitoring of each segment of fulfillment tasks need to be connected to each business execution system one by one, and the execution logic is complex and the execution efficiency is low; the node styles and execution logics of each business execution system are not unified, and there is no strong business association between them. Therefore, when connecting to a new business execution system, the previous track connection logic cannot be reused, and it is necessary to re-plan and develop a new track connection interface between systems, and the customized development cost is high.

[0133] According to the embodiments of the present disclosure, by determining the trigger trajectory nodes associated with each fulfillment business, and configuring a standard style for each trigger trajectory node according to a pre-built trajectory standard style table, and generating a fulfillment trigger rule in combination with the execution order of M fulfillment businesses, each fulfillment link can be automatically triggered to execute in sequence, solving the problem of complex execution logic and low execution efficiency in the issuance of each segment of fulfillment tasks in the related technology. The trigger trajectory nodes in the generated fulfillment trigger rules adopt a standard style, so the fulfillment trigger rules are a set of rules using a standard style, which can be used to connect to multiple different business execution systems. Even if the node styles, execution logic, etc. of the multiple business execution systems are not unified, and there is no strong business association relationship between them, the previous trajectory docking logic can be reused when connecting to multiple different business systems or connecting to a new business execution system. By defining and configuring a set of reusable standard nodes for different fulfillment platforms based on the pre-built track standard style sheet, a trigger rule common to multiple business systems is formed, achieving non-intrusive decoupling of order status flow and track processing logic. Different docking platforms can reuse most standard nodes, and there is no need to integrate complex business execution system tracks, thereby saving related business planning and development workload.

[0134] According to an embodiment of the present disclosure, triggering M fulfillment services to be executed sequentially based on the fulfillment triggering rule includes the following operations:

[0135] Operation 11: after triggering the Lth business execution system to start executing the Lth fulfillment business, receiving the real-time trajectory feedback information sent by the Lth business execution system, wherein the real-time trajectory feedback information includes: the original style of the target trajectory node currently transferred by the Lth business execution system, L is a positive integer, and 1≤L<M;

[0136] Operation 12: based on a pre-built standard style mapping table, convert the original style of the target trajectory node into a standard style, wherein the standard style mapping table includes: a mapping relationship between the original style and the standard style of all trajectory nodes involved in the full service;

[0137] Operation 13: When the standard pattern of the target trajectory node matches the standard pattern of the target trigger trajectory node associated with the L+1th fulfillment business, trigger the L+1th business execution system to start executing the L+1th fulfillment business;

[0138] Operation 14: When the standard pattern of the target trajectory node does not match the standard pattern of the target trigger trajectory node associated with the L+1th fulfillment business, suspend the L+1th business execution system from starting to execute the L+1th fulfillment business.

[0139] According to an embodiment of the present disclosure, still taking the cross-border parcel order mentioned above as an example, four business execution systems are required to complete the service business.

[0140] The domestic / overseas warehouse management system completes the warehousing fulfillment link, and the trigger track node is configured as the "initial" node; the third-party service provider system completes the delivery fulfillment link, and the trigger track node is configured as the "package arrives at the warehouse" node; the collection system completes the collection fulfillment link, and the trigger track node is configured as the "package weighing in the warehouse" node; the customs clearance system completes the customs clearance fulfillment link, and the trigger track node is configured as the "arrival at the destination port" node.

[0141] The generated fulfillment trigger rules are used to characterize the standard style and execution order of M trigger trajectory nodes. For example, the fulfillment trigger rules are: "Initial" - Order 1, "Package arrives at the warehouse" - Order 2, "Package weighing in the warehouse" - Order 3, "Arrival at the destination port" - Order 4.

[0142] refer to Figure 3According to the embodiments of the present disclosure, during the execution of the corresponding fulfillment business, the business execution system will feed back the real-time trajectory feedback information to the comprehensive processing platform after each trajectory node is executed. Therefore, in operation 11, after the Lth business execution system is triggered to start executing the Lth fulfillment business, the comprehensive processing platform will receive the real-time trajectory feedback information sent by the Lth business execution system. The real-time trajectory feedback information mainly includes: the original style of the target trajectory node that the current business execution system is currently transferring to, and the original style is the common node display style in the business system.

[0143] Since the track node styles and execution logic of multiple business execution systems are not unified and there is no strong business association between them, there is no unified standard for the styles of track nodes fed back in real time by different business systems. Figure 3 , the original style of the target trajectory node can be converted into a standard style based on a pre-built standard style mapping table.

[0144] In addition to the standard style mapping table pre-built by the comprehensive processing platform, a standard style mapping table is also pre-built to characterize the mapping relationship between the original style and the standard style of all trajectory nodes involved in the full service. For example, for the trajectory node of the logistics package arriving at the warehouse, the original style is: name-"package arrives at the warehouse", number-XB12, which is converted to the standard style according to the standard style mapping table: name-"package arrives at the warehouse", number-002.

[0145] In operation 13, refer to Figure 3 , the standard style of the target trajectory node can be compared with the standard style of the target trigger trajectory node associated with the next stage of fulfillment business. If they match, it means that the current fulfillment business link has been executed and the execution of the next stage of fulfillment business can be triggered.

[0146] For example, still taking the cross-border parcel order mentioned above as an example, when the customer places an order, the docking platform generates a fulfillment plan according to the fulfillment channel configuration and starts execution according to the plan. It identifies that the trigger trajectory node of the first warehousing fulfillment link is configured as the "initial" node, and directly places an order to the downstream domestic / overseas warehousing management system. If the fulfillment warehouse is successfully issued, the docking platform will suspend the order, waiting for the physical package to actually arrive at the warehouse and the domestic / overseas warehousing management system to feedback the status of the package to the warehouse. When the standard style of the trajectory node received by the docking platform is "package arrives at the warehouse", which matches the standard style of the target trigger trajectory node associated with the next fulfillment business, that is, the delivery fulfillment link, the next cross-border waybill is automatically triggered. The subsequent fulfillment trigger process is similar until the fulfillment plan is actually executed and the cross-border order is finally issued. If the docking platform fails to place an order to any business execution system in the ordering process, or the order is successfully placed but the downstream cannot perform the contract normally, for example, the service provider does not follow the normal process through the platform system, but cancels the fulfillment order privately through the service provider system, the docking platform will no longer receive the trigger node of the next fulfillment channel, and the fulfillment order process will be terminated accordingly, which can avoid the execution of subsequent invalid fulfillment links and the problem troubleshooting and operation and maintenance work caused by it.

[0147] According to the embodiments of the present disclosure, a set of reusable standard nodes are configured for different fulfillment businesses through the above method, the original style of the trajectory returned by the downstream is received and converted into a standard style node, and rule matching is performed to drive the order status flow, thereby realizing non-intrusive order status flow and trajectory processing logic decoupling. The standard style node is used as the triggering order timing for each segment of the business, and multiple segments of fulfillment orders are automatically driven to be issued, so as to more effectively follow up the actual logistics progress of the package, and reasonably and orderly connect the order flow process of each business execution system, avoiding the abnormal order of a certain fulfillment channel due to the disconnection of the online and offline order fulfillment progress, or the need to return multiple segments of fulfillment orders at the same time due to the actual inability to fulfill the contract, thereby improving the order fulfillment success rate.

[0148] In addition, a combination of general order message caching and order timing triggering mode can be adopted, so that operation and maintenance can focus more on message correction and order timing triggering, thereby reducing the workload of online operation and maintenance.

[0149] According to an embodiment of the present disclosure, a standard style mapping table and a standard style mapping table are pre-built on the integrated processing platform, and multiple packaging style mapping tables are also pre-built. The multiple packaging style mapping tables are created for different customer packaging requirements.

[0150] Figure 4 The schematic diagram shows the principle diagram of data interaction between various systems in the process of building the standard style mapping table and the packaging style mapping table. Figure 4 The methods for constructing the above two types of mapping tables are described.

[0151] Among them, the standard style mapping table is constructed by the following method:

[0152] First, the original style of all trajectory nodes is obtained from the full business system or a third-party service provider. The original style includes at least: original node name, original node code, and original display words. Then, according to the preset standard node configuration rules, the original node name is bound to the standard node name, the original node code is bound to the standard node code, and the original display words are bound to the standard display words.

[0153] like Figure 4 As shown, first of all, the original style of the full track node needs to be obtained from the full business system or third-party service provider. When the docking platform order placement link is newly docked with the business execution system, or the docked business execution system integrates a new logistics service provider, and the docking platform needs to subsequently monitor the fulfillment order track returned by the newly docked service provider system or business system, the original code, original name, original words, service provider / business system information and system time zone of the track node defined by the new service provider system or business execution system can be provided to the comprehensive processing platform for unified maintenance into the service provider original track node list (the business execution system is also uniformly classified as the service provider system relative to the international comprehensive processing platform), so as to achieve unified closing, identification and monitoring by the comprehensive processing platform, and provide track-related service capabilities to the outside world in a unified manner, and store the original style data of the full track node as the basic data raw material for customized processing.

[0154] On the integrated processing platform, a track standard style sheet is pre-built, which is used to subsequently generate a standard style mapping sheet and a packaging style mapping sheet based on the table.

[0155] Among them, the track standard style table includes the standard styles of all track nodes involved in all services. It is mainly aimed at the needs of external merchants to monitor the progress of order fulfillment directly from the docking platform terminal, or the docking platform needs to trigger the issuance of subsequent fulfillment orders and the flow of order status based on the operation track of the previous fulfillment order. A set of standardized international logistics order full tracks is uniformly defined and configured to facilitate the unified provision of standardized track broadcasting or query services for the fulfillment system of international logistics internal merchants, and support merchant fulfillment systems serving customers in different countries and regions to obtain international multilingual track displays according to needs.

[0156] When configuring the standard style of the full trajectory node, the docking platform that needs to access the trajectory monitoring can provide a list of order trajectory nodes that need to be monitored, and configure the standard style of the full trajectory node on the international integrated processing platform. The standard style may include standard node name, standard node code, standard display script, node type, etc., and mark whether it is an abnormal node or the final node, which is convenient for subsequent fulfillment order progress tracking and abnormal warning. If the integrated processing platform has configured the same type of standard trajectory, it can be reused directly. Most external merchants or business execution systems can basically reuse most standard nodes when docking, and there is no need to repeatedly define the entire trajectory. If there are a few newly added personalized standard nodes, they can be configured additionally.

[0157] like Figure 4 After obtaining the original style of the full trajectory node from the full business system or a third-party service provider, based on the preset standard node configuration rules, for example, based on the standard style of the full trajectory node in the trajectory standard style table, the original node name is bound to the standard node name, the original node code is bound to the standard node code, and the original display language is bound to the standard display language, and a standard style mapping table is generated to characterize the mapping relationship between the original style of the full trajectory node and the standard style.

[0158] According to the embodiments of the present disclosure, although most of the logistics track types defined for cross-border orders in different business scenarios of international logistics are not much different and can be reused, due to the different service provider systems or business execution systems connected to the downstream, the definition system of logistics track nodes is different, and even the definition of track nodes representing the same logistics status is different (such as coding, speech, and order status represented, etc.). If the original track returned by the downstream is directly provided to external customers or merchant fulfillment systems for display without processing, it may cause problems such as overlapping logistics status, inconsistent time zones, or difficult to understand due to different track speech types. In addition, the merchant fulfillment system cannot directly associate the newly added original track nodes with the order status for fulfillment flow, and the fulfillment system needs to continuously increase customized conversion and processing. By configuring the mapping relationship between the original style and the standard style, the comprehensive processing platform can summarize and aggregate the original track styles according to specific rules, and convert them into a set of standard styles that can be applied to most cross-border scenarios, so as to realize the generalization of standard nodes and reduce the docking workload of each fulfillment system. The integrated processing platform supports flexible mapping configuration of the track node style according to the service provider / business execution system dimension, and can set whether the track node uses the service provider's original words or standard words when displaying. Words are used to describe the node function and can be displayed according to the preset language (Chinese, English, Japanese, etc.). For example, for the track node of express delivery entering the warehouse, its standard words are: Warehousing, and the service provider's original words are: Entering warehouse.

[0159] According to the embodiments of the present disclosure, external merchants actively pull or passively push real-time order tracks through the external interface provided by the docking platform. Compared with the standard track nodes defined by the platform, the merchant platform may be more concerned about how to track orders in real time according to a customized track system. In response to such various customized needs, the comprehensive processing platform can support merchant personalized packaging and processing configuration based on the configured standard track nodes.

[0160] There are multiple packaging style mapping tables, which are created for different customer packaging requirements. For example, a target packaging style mapping table is constructed for the target packaging requirements of target customers. The target packaging style mapping table includes: a mapping relationship between the standard style of all track nodes involved in the full service and the target packaging style, wherein the target packaging style meets the target packaging requirements.

[0161] The target packaging style mapping table is constructed by the following method:

[0162] like Figure 4 As shown, first, the target packaging requirements of the target customers are obtained by parsing the user requests, and the target packaging style of the full trajectory nodes is determined. The target packaging style includes at least: packaging node name, packaging node code, and packaging display words; then, based on the standard style of the full trajectory nodes in the trajectory standard style table, the standard style of the node is bound to the target packaging style, that is, the standard node name is bound to the packaging node name, the standard node code is bound to the packaging node code, and the standard display words are bound to the packaging display words.

[0163] For example, when external merchants are connected, they provide the comprehensive processing platform with a list of custom trajectory information that needs to be subscribed and monitored. The comprehensive processing platform first creates a new packaging rule (user packaging requirement) according to the merchant dimension, and then adds a merchant packaging node under the packaging rule. Based on the standard style of all trajectory nodes in the trajectory standard style table, the standard style corresponding to each trajectory node is selected in the trajectory standard style table, and the packaging node code, name, merchant system time zone, and merchant custom packaging scripts in different languages ​​are set. At the same time, the script type can be set to be used when displaying to the user after the user obtains the trajectory. For example, the merchant packaging script, service provider script, or standard script can be selected. Finally, the comprehensive processing platform publishes the packaging style mapping table and provides it to the docking platform.

[0164] According to the embodiments of the present disclosure, a user packaging demand subscription function can be further set. User packaging demands can be pre-stored in the demand subscription system. Business personnel open an ordering account for the customer on the docking platform and can set the docking demand subscription system information. Through the demand subscription system, the full packaging style mapping table configured by the integrated processing platform can be obtained in real time. By pre-selecting the packaging style mapping table and user packaging demands corresponding to the merchant platform and subscribing and binding them to the demand subscription system, the information of the demand subscription system can be reused when other ordering accounts are docked later. At the same time, the track feedback method expected by the external merchant can be set on the docking system master data, such as no feedback / real-time feedback / customer actively pulling the track, etc.

[0165] According to the embodiments of the present disclosure, with the rapid development of international logistics cross-border business, logistics companies need to provide external merchants with more complete cross-border order fulfillment monitoring functions, timely and fully track the delivery progress and timeliness of goods in each fulfillment link, and provide personalized merchant trajectory production functions with flexible configuration, real-time effectiveness and support for multi-channel feedback according to the ever-changing trajectory customization needs of different merchants. At the same time, it is also necessary to provide operators with pre-set and timely fulfillment links and logistics trajectory abnormality warning capabilities, so that operators can discover and handle order fulfillment anomalies in advance of customers and reduce related customer complaints.

[0166] In addition, when certain key trajectory nodes involved in order fulfillment are missing, resulting in logistics suspension, and the platform is unable to predict in advance which are the key nodes and monitor the anomalies in a timely manner, it will cause a series of subsequent problems. For example, when the package weighing operation of the fulfillment warehouse system is missing, the docking platform will be unable to push receivables to the billing system. Only when the operating staff discovers the missing accounting data at the end of the month will they discover it and notify the warehouse to make up the account, thereby affecting the processing time of the order, causing economic losses to the company or causing customer complaints.

[0167] According to the embodiments of the present disclosure, during the process of executing multiple fulfillment businesses in sequence, a current full-process track chain can be generated and pushed to the user. A standard track chain or a packaged track chain can be pushed according to user needs.

[0168] According to an embodiment of the present disclosure, the service execution method of the embodiment of the present disclosure further includes:

[0169] Operation 21: determining original styles of multiple historical trajectory nodes that have been circulated by the first L business execution systems according to the historical trajectory feedback information sent by the first L business execution systems;

[0170] Operation 22, according to the preset execution order of the N trajectory nodes, concatenating multiple historical trajectory nodes marked with the original style to form an original trajectory chain;

[0171] Operation 23: Based on a pre-built standard style mapping table, convert the original styles of multiple historical trajectory nodes included in the original trajectory chain into a standard style to form a standard trajectory chain for the target service.

[0172] Operation 24: Push the standard track chain to the customer.

[0173] According to the embodiments of the present disclosure, the original styles of the third-party logistics tracks are uniformly converted into standard styles for management and generalization, and can be dynamically and effectively implemented in real time. This allows for rapid identification of business node processes and can save track docking R&D costs.

[0174] According to the embodiments of the present disclosure, external merchant customers prefer to monitor the entire life cycle logistics trajectory chain. The processing method in the relevant technology requires the platform to separately formulate a set of trajectory-order status mapping schemes for the trajectory nodes returned by each segment of the business system, and also to design a scheme to connect the document status mapped by the trajectory nodes in series, solve problems such as trajectory node overlap and time zone asynchrony. Even if the trajectory processing logic is similar, the fulfillment systems of various merchants cannot be reused, resulting in a large workload for trajectory mapping of various business lines and product planning.

[0175] In the method of the disclosed embodiment, a pre-constructed standard style mapping table is used as the basis for realizing the non-uniform styles of various system nodes. By concatenating the completed trajectory nodes and converting the styles, standardized and unified processing of the trajectories of different business systems is achieved. The processing logic is simple and the timeliness is high, which solves the problems of complex trajectory mapping processing procedures and high system processing pressure in various business lines and product planning.

[0176] According to the embodiments of the present disclosure, external merchants actively pull or passively push real-time order tracks through the external interface provided by the docking platform. Compared with the standard track nodes defined by the platform, the merchant platform may be more concerned about how to track orders in real time according to a customized track system. In response to such various customized needs, the comprehensive processing platform can support merchant personalized packaging and processing configuration based on the configured standard track nodes.

[0177] Based on this, in the process of returning the track chain to the customer, the above method also includes:

[0178] Operation 25: Obtain target packaging requirements of target customers;

[0179] Operation 26: querying a target packaging style mapping table corresponding to the target packaging requirement, wherein:

[0180] Operation 27: based on the target packaging style mapping table, convert the standard styles of multiple historical track nodes included in the standard track chain into the target packaging style to form a packaging track chain for the target service.

[0181] Operation 28: Push the packaging track chain to the customer.

[0182] Since external merchants have different requirements for order trajectory display, some need to obtain the original trajectory nodes of the fulfillment service provider, some need to display the standard order status nodes uniformly formulated by the docking platform, and some need to convert the service provider's trajectory into a customized trajectory node of the merchant system. Most of the related technologies require customized production of the business execution system or the service provider's original trajectory separately, and lack the ability to provide unified management and dynamic configuration for customized requirements such as unified conversion of multi-language scripts, languages, time zones, and trajectory node subscriptions for specific merchants, which invisibly increases the complexity of R&D and the cost of merchant docking.

[0183] According to the embodiments of the present disclosure, the standard nodes converted from the original trajectory are personalized and reprocessed according to the customer's packaging needs and transmitted back to the upstream, so as to realize the unified management, generalization and dynamic real-time effectiveness of packaging rules, and meet the personalized needs of customers.

[0184] Figure 5 The system principle diagram for generating a track chain during the execution of a fulfillment business according to an embodiment of the present disclosure is schematically shown.

[0185] The following combination Figure 5 The above method is further described in detail.

[0186] like Figure 5 As shown in the figure, when an external customer places a cross-border order through the docking platform, the corresponding order fulfillment plan is first generated according to the service product configuration, and the fulfillment order is issued to the downstream business execution systems in the order of the plan execution. At the same time, the docking system feedback information is obtained through the order account. If the docking system is bound to the merchant's track packaging requirements and return method, the cross-border order code, the user's login language environment and the time zone are sent to the comprehensive processing platform (track platform).

[0187] After receiving the above information, the comprehensive processing platform generates an order trajectory tracking task for subsequent logistics monitoring and abnormal warning, and synchronizes the order fulfillment plan from the docking platform database through the data synchronization tool to obtain the trajectory feedback information of each business execution system, as well as the execution order between each fulfillment link and trajectory nodes.

[0188] The comprehensive processing platform then synchronizes the original style of the trajectory nodes of each segment of the fulfillment order from the corresponding business execution system database in batches based on the fulfillment plan information through the data synchronization tool, determines the preset execution order of the trajectory nodes through the cross-border order coding, and based on the preset execution order of the trajectory nodes, connects multiple historical trajectory nodes marked with the original style in series to form the original trajectory chain warehouse, so as to provide raw materials for the overall monitoring of the subsequent fulfillment process and trajectory mapping processing.

[0189] According to the embodiments of the present disclosure, the trajectory feedback method expected by the merchant customers can be pre-bound, such as no feedback / real-time active feedback / customer active tracking, etc., so as to push the trajectory chain to the customer according to the set feedback method.

[0190] If the customer does not send the track feedback method or the feedback method is no feedback, the original track chain is converted into a standard track chain and placed in the warehouse as the basic data.

[0191] If the feedback method requested by the customer is real-time active feedback, it means that the order packaging track needs to be pushed to the customer system in real time according to customized requirements.

[0192] First, the comprehensive processing platform will batch-match the multiple historical trajectory nodes newly synchronized with the original style to the corresponding standard style. If no match is found, the original state node will be directly broadcast to the merchant through the message queue for self-processing. If a match is found, the trajectory speech will be converted into the standard display speech of the corresponding language according to the language type issued, and the original trajectory information in the message will be replaced with the mapped standard trajectory node information, and then broadcast to the upstream docking platform to continue the fulfillment order process. If the docking platform also issues the trajectory packaging requirements, the standard style trajectory code will continue to match the corresponding packaging style mapping table. If no match is found, the processing flow will be terminated and not broadcast externally; if a match is found, the standard style will be converted into the packaging style to generate a packaging trajectory chain.

[0193] Specifically, the configured display speech type can be obtained. If the standard speech is still used, only other information in the message is replaced. If the merchant's packaged speech needs to be used, the packaged speech in the corresponding language is obtained through the issued language type to replace the original speech. If the time zone of the issued customer is different from the service provider's track time zone, the track operation time will be uniformly converted to the customer's time zone and replace the original time. Finally, the personalized packaged track nodes will be sorted, invalid tracks will be screened out, and broadcast in sequence, connected to the platform consumption and pushed to the external customer system in real time.

[0194] If the feedback method requested by the customer is / customer actively pulls the track, it means that the customer system will subsequently pull the incremental packaging track by regularly calling the docking platform interface.

[0195] When the customer calls the docking platform interface or queries the package track from the platform terminal, the docking platform then calls the packaging track interface of the integrated processing platform to pass in the corresponding order number, the language of the current login environment, the customer code and the packaging rules. The integrated processing platform obtains the original style of the track nodes of each fulfillment link based on the passed-in information and performs standard style conversion. The conversion process is the same as the above operation.

[0196] Query whether there is any incoming customer's trajectory packaging demand. If no incoming trajectory packaging demand is found during the query, no packaging node conversion processing will be performed. Continue with subsequent processing steps such as time zone conversion, filtering out junk data, and node sorting, and return the standard trajectory list to the upstream merchant fulfillment system.

[0197] If you query the customer's trajectory packaging requirements, use the standard style trajectory code to continue to match the corresponding packaging style mapping table to perform personalized trajectory processing. If no match is found, only the time zone conversion is performed and the standard node information is retained; if a match is found, the standard style is converted into the packaging style to generate a packaging trajectory chain.

[0198] Specifically, the speech type configured on the packaging track can be converted (keep the standard speech or use customized merchant track speech), and the track speech can be switched to the corresponding language through the language type passed in through the interface, and then the track time in the service provider's time zone can be converted to the customer's time zone. Finally, the track list after parallel asynchronous processing is summarized and sorted, and the track nodes missing key information are screened out and returned to the customer.

[0199] According to the embodiments of the present disclosure, the above method is used to target the personalized needs of different external merchants for trajectory monitoring and display, and the standard nodes that need to be monitored and customized are set with personalized mapping configurations such as multi-language, merchant packaging language, and cross-time zone conversion from the merchant dimension, and are uniformly packaged as packaging trajectories for release. By subscribing to the rules when configuring the docking system information of the corresponding merchant, and by setting the merchant's desired trajectory feedback method, the comprehensive processing platform will perform personalized reprocessing and return the standard nodes converted from the original trajectory according to the packaging rules and feedback methods issued when the fulfillment platform places an order, so as to achieve unified management, generalization, and dynamic real-time effectiveness of packaging rules. Merchants do not need to dock and develop online when adding personalized trajectory nodes, thereby saving trajectory docking R&D costs.

[0200] According to an embodiment of the present disclosure, during the process of sequentially executing multiple fulfillment services, the nodes may be monitored. Specifically, the service execution method further includes:

[0201] Operation 31: Determine S warning trajectory nodes that need to be monitored during the execution of the target service from the N trajectory nodes, where N ≥ S;

[0202] Operation 32: configure warning rules for S warning trajectory nodes;

[0203] Operation 33: Monitor the S warning trajectory nodes according to the warning rules.

[0204] Specifically, monitoring S warning trajectory nodes according to the warning rules includes:

[0205] Operation 41: obtaining a first timestamp corresponding to when a reference trajectory node is executed, wherein the reference trajectory node is a previous trajectory node of the warning trajectory node, or the reference trajectory node is a first trajectory node corresponding to the start of execution of a first fulfillment business;

[0206] Operation 42: Obtain a second timestamp corresponding to the target monitoring time period;

[0207] Operation 43: When the time interval between the second timestamp and the first timestamp is greater than a preset time threshold, issue a warning prompt for the warning trajectory node.

[0208] like Figure 3 As shown, during the business execution process, the integrated processing platform will generate a trajectory tracking task for the issued order information, and synchronize the order fulfillment plan from the fulfillment platform. Subsequently, the integrated processing platform will also generate an early warning monitoring task.

[0209] Specifically, operators can configure early warning trajectory nodes for the entire process on the docking platform, and determine the early warning trajectory nodes that need to be monitored during the execution of the target service from the full-process trajectory nodes. After the docking platform issues a fulfillment order to the business execution system, it will send the fulfillment order information, order time and monitoring nodes, that is, the list of early warning trajectory nodes, to the comprehensive processing platform. The comprehensive processing platform can set early warning rules in advance for the early warning nodes set for each fulfillment channel of the upstream order service product, including early warning thresholds, that is, the upper limit of the timeout from the order to the feedback of the node, which is set by business personnel based on historical early warning statistics. In addition, you can also set the number of early warning pushes, early warning mailboxes, and related systems for receiving monitoring alarms.

[0210] The comprehensive processing platform configures warning rules for the warning trajectory nodes, generates warning monitoring tasks, and monitors S warning trajectory nodes according to the warning rules.

[0211] Furthermore, two types of monitoring can be performed by setting two different warning rules.

[0212] These two warning rules are generally similar, both of which include: obtaining the first timestamp corresponding to the completion of the reference trajectory node; obtaining the second timestamp corresponding to the target monitoring time period (for example, the time node of the current polling monitoring); and issuing a warning prompt for the warning trajectory node when the time interval between the second timestamp and the first timestamp is greater than the preset time threshold. The only difference is the reference trajectory node. In one way, the reference trajectory node is the previous trajectory node of the warning trajectory node, that is, it is necessary to monitor whether the time interval between the completion time of the previous trajectory node of the warning trajectory node and the target monitoring time period exceeds the limit; in another way, the reference trajectory node is the first trajectory node corresponding to the start of the first fulfillment business, that is, it is necessary to monitor whether the time interval between the start time of the service and the target monitoring time period exceeds the limit.

[0213] For example, if it is necessary to monitor whether the time interval between the service start time and the target monitoring time period exceeds the limit, the preset time threshold for time limit determination in monitoring needs to be calculated during the early warning rule configuration stage.

[0214] Specifically, for S warning trajectory nodes, the interval time threshold between two adjacent warning trajectory nodes is configured in advance based on operation and maintenance experience. For example, when the service starts to execute, that is, the interval time threshold between the first trajectory node and the warning trajectory node 1 corresponding to the start of the first fulfillment business is configured to be 50 minutes, the interval time threshold between the warning trajectory node 1 and the warning trajectory node 2 is configured to be 30 minutes, and the interval time threshold between the warning trajectory node 2 and the warning trajectory node 3 is configured to be 40 minutes... All the interval time thresholds before the current warning trajectory node corresponding to the target monitoring time period (the time node currently performing polling monitoring) are accumulated in sequence to obtain the preset time threshold for time limit judgment in monitoring.

[0215] After the configuration is completed, the first timestamp corresponding to the first trajectory node corresponding to the start of the first fulfillment business is obtained, and the time of issuing the fulfillment order is used as the monitoring starting point. Combined with the second timestamp corresponding to the time node of the current polling monitoring, the execution time of each fulfillment link is accumulated according to the actual execution order of the fulfillment, and the accumulated business execution time is calculated. It is determined whether the accumulated business execution time exceeds the preset time threshold. If the business feedback result corresponding to the current early warning trajectory node is not received after the preset time threshold, it is preliminarily determined that the current early warning trajectory node is abnormal in fulfillment or not connected to the comprehensive processing platform, triggering the reminder setting, notifying relevant personnel by email or sending a monitoring platform alarm to the merchant fulfillment system / business execution system associated with the task to remind timely intervention and investigation.

[0216] For example, when it is necessary to determine whether the time interval between the completion time of the predecessor trajectory node of the current monitoring warning trajectory node and the target monitoring time period exceeds the limit, in the stage of configuring the warning rules, the preset time threshold for time limit judgment is configured, which can be configured according to the historical processing time of the predecessor trajectory node and the current monitoring warning trajectory node.

[0217] After the configuration is completed, the first timestamp corresponding to the completion of the previous trajectory node is obtained, combined with the second timestamp corresponding to the time node currently executing polling monitoring, and the time interval between the second timestamp and the first timestamp is calculated as the current link business execution duration, and whether the current link business execution duration exceeds the preset time threshold is determined. If the preset time threshold is exceeded and the business feedback result corresponding to the current early warning trajectory node is still not received, it is preliminarily determined that the current early warning trajectory node is abnormal in performance or not connected to the comprehensive processing platform, triggering the reminder setting, notifying relevant personnel by email or sending a monitoring platform alarm to the merchant performance system / business execution system associated with the task, reminding timely intervention and investigation.

[0218] In addition, to avoid the problem of order message loss, general order messages will be cached through the file system when the fulfillment plan is executed. Each fulfillment link that triggers an order will download the message from the file system and reorganize and issue it. For abnormal orders that need to be reissued due to fulfillment termination, operation and maintenance personnel do not need to reorganize the message by themselves. They can directly download, modify and upload the message from the file system through tools, and push the order timing node of the fulfillment channel where the abnormality occurs to the message queue that monitors the order timing of the fulfillment platform, so as to automatically complete the subsequent order flow. The mechanism of triggering fulfillment based on order timing can effectively reduce the operation and maintenance workload for abnormal orders.

[0219] According to the embodiments of the present disclosure, a monitoring mechanism is set up to monitor the business execution time, so as to timely grasp the business execution status of each link. If no feedback is received from the downstream business system within the scheduled time, it is preliminarily determined that the current early warning trajectory node is abnormal in performance. Through the early warning setting, relevant personnel are notified to intervene in the investigation, so as to facilitate timely discovery of problems and resolve anomalies in the business execution process.

[0220] Based on the above service execution method, the present disclosure also provides a service execution device. Figure 6 The device is described in detail.

[0221] Figure 6 The structure block diagram of the service execution device according to the embodiment of the present disclosure is schematically shown.

[0222] like Figure 6 As shown, the service execution device 600 of this embodiment includes a first determination module 601 , a second determination module 602 , a style configuration module 603 , and an execution module 604 .

[0223] The first determination module 601 is used to determine, according to the configuration information of the target service, M performance services to be performed in the process of providing the target service and the execution order of the M performance services, wherein the M performance services are executed one by one through the M service execution systems, and the M performance services involve N trajectory nodes, where M and N are positive integers, and N≥M;

[0224] The second determination module 602 is used to determine M trigger trajectory nodes associated with M performance services from the N trajectory nodes, wherein the M trigger trajectory nodes are used to trigger the M service execution systems to execute their corresponding performance services one by one;

[0225] The style configuration module 603 is used to configure a standard style for each triggered trajectory node according to a pre-built trajectory standard style table, and generate a fulfillment trigger rule in combination with the execution order of M fulfillment services, wherein the information in the trajectory standard style table includes the standard styles of all trajectory nodes involved in all services;

[0226] The execution module 604 triggers the sequential execution of M fulfillment businesses based on the fulfillment triggering rules.

[0227] According to an embodiment of the present disclosure, the fulfillment trigger rule is used to characterize the standard style and execution order of M trigger trajectory nodes, and the execution module 604 includes a feedback receiving unit, a first conversion unit, and a trigger unit.

[0228] A feedback receiving unit is used to receive real-time trajectory feedback information sent by the Lth business execution system after triggering the Lth business execution system to start executing the Lth contract performance business, wherein the real-time trajectory feedback information includes: the original style of the target trajectory node currently transferred by the Lth business execution system, L is a positive integer, and 1≤L<M;

[0229] A first conversion unit is configured to convert an original style of a target trajectory node into a standard style based on a pre-built standard style mapping table, wherein the standard style mapping table includes: a mapping relationship between the original style of all trajectory nodes involved in the full service and the standard style;

[0230] The trigger unit is used to trigger the L+1th business execution system to start executing the L+1th fulfillment business when the standard pattern of the target trajectory node matches the standard pattern of the target trigger trajectory node associated with the L+1th fulfillment business.

[0231] According to an embodiment of the present disclosure, the execution module 604 also includes a suspension execution unit, which is used to suspend the L+1th business execution system from starting to execute the L+1th fulfillment business when the standard pattern of the target trajectory node does not match the standard pattern of the target trigger trajectory node associated with the L+1th fulfillment business.

[0232] According to an embodiment of the present disclosure, the execution module 604 further includes a determination unit, a concatenation unit, and a second conversion unit.

[0233] A determination unit, configured to determine, based on the historical trajectory feedback information sent by the first L business execution systems, the original styles of the plurality of historical trajectory nodes that have been circulated by the first L business execution systems;

[0234] A concatenation unit, used for concatenating a plurality of historical trajectory nodes marked with original styles to form an original trajectory chain according to a preset execution order of the N trajectory nodes;

[0235] The second conversion unit is used to convert the original styles of multiple historical trajectory nodes included in the original trajectory chain into a standard style based on a pre-built standard style mapping table to form a standard trajectory chain for the target service.

[0236] According to an embodiment of the present disclosure, the execution module 604 further includes a first acquisition unit, a query unit, and a third conversion unit.

[0237] A first acquisition unit is used to acquire target packaging requirements of target customers;

[0238] A query unit, configured to query a target packaging style mapping table corresponding to a target packaging requirement, wherein the target packaging style mapping table includes: a mapping relationship between a standard style of a full set of trajectory nodes involved in a full set of services and a target packaging style, wherein the target packaging style satisfies the target packaging requirement;

[0239] The third conversion unit is used to convert the standard styles of multiple historical track nodes included in the standard track chain into the target packaging style based on the target packaging style mapping table to form a packaging track chain for the target service.

[0240] According to an embodiment of the present disclosure, the standard style of the full trajectory node includes at least: a standard node name, a standard node code, and a standard presentation language.

[0241] The above device also includes a first construction module, which is used to construct a target packaging style mapping table. The first construction module includes a parsing unit and a first binding unit.

[0242] A parsing unit is used to parse the target packaging requirements and determine the target packaging style of the full trajectory node. The target packaging style at least includes: packaging node name, packaging node code, and packaging display words;

[0243] The first binding unit is used to bind the standard node name to the packaged node name, bind the standard node code to the packaged node code, and bind the standard display words to the packaged display words.

[0244] According to an embodiment of the present disclosure, the above-mentioned device further includes a second construction module for constructing a standard style mapping table, and the second construction module includes a second acquisition unit and a second binding unit.

[0245] The second acquisition unit is used to acquire the original style of the full track node from the full business system or a third-party service provider, where the original style at least includes: the original node name, the original node code, and the original display script;

[0246] The second binding unit is used to bind the original node name to the standard node name, bind the original node code to the standard node code, and bind the original display words to the standard display words according to the preset standard node configuration rules.

[0247] According to an embodiment of the present disclosure, the above-mentioned device also includes a third determination module, an early warning rule configuration module, and a monitoring module.

[0248] A third determination module is used to determine S warning trajectory nodes that need to be monitored during the execution of the target service from the N trajectory nodes, N ≥ S;

[0249] The warning rule configuration module is used to configure warning rules for S warning trajectory nodes;

[0250] The monitoring module is used to monitor the S warning trajectory nodes according to the warning rules.

[0251] According to an embodiment of the present disclosure, the monitoring module includes a third acquisition unit, a fourth acquisition unit, and a prompt unit.

[0252] A third acquisition unit is used to acquire a first timestamp corresponding to when the reference trajectory node is executed, wherein the reference trajectory node is a previous trajectory node of the warning trajectory node, or the reference trajectory node is a first trajectory node corresponding to the start of execution of the first performance business;

[0253] A fourth acquisition unit, used to acquire a second timestamp corresponding to the target monitoring time period;

[0254] The prompt unit is used to issue a warning prompt for the warning trajectory node when the time interval between the second timestamp and the first timestamp is greater than a preset time threshold.

[0255] According to an embodiment of the present disclosure, any multiple modules of the first determination module 601, the second determination module 602, the style configuration module 603, and the execution module 604 can be combined in one module for implementation, or any one of the modules can be split into multiple modules. Alternatively, at least part of the functions of one or more of these modules can be combined with at least part of the functions of other modules and implemented in one module. According to an embodiment of the present disclosure, at least one of the first determination module 601, the second determination module 602, the style configuration module 603, and the execution module 604 can be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on a chip, a system on a substrate, a system on a package, an application specific integrated circuit (ASIC), or can be implemented by hardware or firmware such as any other reasonable way of integrating or packaging the circuit, or implemented in any one of the three implementation methods of software, hardware, and firmware or in an appropriate combination of any of them. Alternatively, at least one of the first determination module 601 , the second determination module 602 , the style configuration module 603 , and the execution module 604 may be at least partially implemented as a computer program module, and when the computer program module is executed, a corresponding function may be executed.

[0256] Figure 7 A block diagram of an electronic device suitable for implementing a service execution method according to an embodiment of the present disclosure is schematically shown.

[0257] like Figure 7 As shown, the electronic device 700 according to an embodiment of the present disclosure includes a processor 701, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 702 or a program loaded from a storage part 708 into a random access memory (RAM) 703. The processor 701 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or a related chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 701 may also include an onboard memory for caching purposes. The processor 701 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

[0258] In RAM 703, various programs and data required for the operation of electronic device 700 are stored. Processor 701, ROM 702 and RAM 703 are connected to each other via bus 704. Processor 701 performs various operations of the method flow according to the embodiment of the present disclosure by executing the program in ROM 702 and / or RAM 703. It should be noted that the program can also be stored in one or more memories other than ROM 702 and RAM 703. Processor 701 can also perform various operations of the method flow according to the embodiment of the present disclosure by executing the program stored in the one or more memories.

[0259] According to an embodiment of the present disclosure, the electronic device 700 may further include an input / output (I / O) interface 705, which is also connected to the bus 704. The electronic device 700 may further include one or more of the following components connected to the input / output (I / O) interface 705: an input portion 706 including a keyboard, a mouse, etc.; an output portion 707 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage portion 708 including a hard disk, etc.; and a communication portion 709 including a network interface card such as a LAN card, a modem, etc. The communication portion 709 performs communication processing via a network such as the Internet. A drive 710 is also connected to the input / output (I / O) interface 705 as needed. A removable medium 711, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 710 as needed, so that a computer program read therefrom is installed into the storage portion 708 as needed.

[0260] The present disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or may exist independently without being assembled into the device / apparatus / system. The above computer-readable storage medium carries one or more programs, and when the above one or more programs are executed, the method according to the embodiment of the present disclosure is implemented.

[0261] According to an embodiment of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, for example, may include but is not limited to: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by or in combination with an instruction execution system, an apparatus or a device. For example, according to an embodiment of the present disclosure, a computer-readable storage medium may include the ROM 702 and / or RAM 703 described above and / or one or more memories other than ROM 702 and RAM 703.

[0262] The embodiment of the present disclosure also includes a computer program product, which includes a computer program, and the computer program contains program code for executing the method shown in the flowchart. When the computer program product is run in a computer system, the program code is used to enable the computer system to implement the service execution method provided by the embodiment of the present disclosure.

[0263] The above functions defined in the system / device of the embodiment of the present disclosure are performed when the computer program is executed by the processor 701. According to the embodiment of the present disclosure, the system, device, module, unit, etc. described above can be implemented by a computer program module.

[0264] In one embodiment, the computer program may rely on tangible storage media such as optical storage devices, magnetic storage devices, etc. In another embodiment, the computer program may also be transmitted and distributed in the form of signals on a network medium, and downloaded and installed through the communication part 709, and / or installed from the removable medium 711. The program code contained in the computer program may be transmitted using any appropriate network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0265] In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 709, and / or installed from the removable medium 711. When the computer program is executed by the processor 701, the above functions defined in the system of the embodiment of the present disclosure are performed. According to the embodiment of the present disclosure, the system, device, means, module, unit, etc. described above can be implemented by a computer program module.

[0266] According to an embodiment of the present disclosure, the program code for executing the computer program provided by the embodiment of the present disclosure can be written in any combination of one or more programming languages. Specifically, these computing programs can be implemented using high-level process and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, Java, C++, python, "C" language or similar programming languages. The program code can be executed entirely on the user computing device, partially on the user device, partially on the remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device can be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computing device (for example, using an Internet service provider to connect through the Internet).

[0267] The flow charts and block diagrams in the accompanying drawings illustrate the possible architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each box in the flow chart or block diagram can represent a module, a program segment, or a part of a code, and the above-mentioned module, program segment, or a part of a code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flow chart, and the combination of the boxes in the block diagram or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0268] It will be appreciated by those skilled in the art that the features described in the various embodiments and / or claims of the present disclosure may be combined and / or combined in a variety of ways, even if such combinations and / or combinations are not explicitly described in the present disclosure. In particular, the features described in the various embodiments and / or claims of the present disclosure may be combined and / or combined in a variety of ways without departing from the spirit and teachings of the present disclosure. All of these combinations and / or combinations fall within the scope of the present disclosure.

[0269] The embodiments of the present disclosure are described above. However, these embodiments are only for the purpose of illustration and are not intended to limit the scope of the present disclosure. Although the embodiments are described above separately, this does not mean that the measures in the various embodiments cannot be used in combination to advantage. The scope of the present disclosure is defined by the attached claims and their equivalents. Without departing from the scope of the present disclosure, those skilled in the art may make various substitutions and modifications, which should all fall within the scope of the present disclosure.

Claims

1. A business execution method, comprising: Determine, according to the configuration information of the target service, M performance services to be performed in the process of providing the target service and the execution order of the M performance services, wherein the M performance services are executed one-to-one by M service execution systems, the M performance services involve N trajectory nodes, and the M and N are positive integers, and N≥M; Determine M trigger trajectory nodes associated with the M contract performance services from the N trajectory nodes, wherein the M trigger trajectory nodes are used to trigger the M service execution systems to execute their respective corresponding contract performance services in a one-to-one correspondence; According to the pre-built trajectory standard style table, a standard style is configured for each of the trigger trajectory nodes, and a performance trigger rule is generated in combination with the execution order of the M performance services, wherein the information in the trajectory standard style table includes the standard styles of all trajectory nodes involved in all services; The M fulfillment businesses are triggered to be executed sequentially based on the fulfillment triggering rules.

2. The method according to claim 1, wherein: The performance triggering rule is used to characterize the standard style and execution order of the M trigger trajectory nodes. Triggering the M performance services to be executed sequentially based on the performance triggering rule includes: After triggering the Lth business execution system to start executing the Lth fulfillment business, receiving real-time trajectory feedback information sent by the Lth business execution system, wherein the real-time trajectory feedback information includes: the original style of the target trajectory node currently transferred by the Lth business execution system, where L is a positive integer and 1≤L<M; Based on a pre-built standard style mapping table, the original style of the target trajectory node is converted into a standard style, wherein the standard style mapping table includes: a mapping relationship between the original style and the standard style of all trajectory nodes involved in the full service; When the standard pattern of the target trajectory node matches the standard pattern of the target trigger trajectory node associated with the L+1th fulfillment business, the L+1th business execution system is triggered to start executing the L+1th fulfillment business.

3. The method according to claim 2, further comprising: When the standard pattern of the target trajectory node does not match the standard pattern of the target trigger trajectory node associated with the L+1th fulfillment business, the L+1th business execution system is suspended from starting to execute the L+1th fulfillment business.

4. The method according to claim 2, further comprising: According to the historical trajectory feedback information sent by the first L business execution systems, determine the original styles of multiple historical trajectory nodes that have been circulated by the first L business execution systems; According to the preset execution order of the N trajectory nodes, a plurality of the historical trajectory nodes marked with the original style are connected in series to form an original trajectory chain; Based on a pre-constructed standard style mapping table, the original styles of the plurality of historical trajectory nodes included in the original trajectory chain are converted into a standard style to form a standard trajectory chain for the target service.

5. The method according to claim 4, further comprising: Obtaining target packaging requirements of the target customers; Querying a target packaging style mapping table corresponding to the target packaging requirement, wherein the target packaging style mapping table includes: a mapping relationship between a standard style of a full amount of trajectory nodes involved in a full amount of services and a target packaging style, wherein the target packaging style satisfies the target packaging requirement; Based on the target packaging style mapping table, the standard styles of the plurality of historical track nodes included in the standard track chain are converted into a target packaging style to form a packaging track chain for the target service.

6. The method according to claim 5, wherein: The standard style of the full track node at least includes: standard node name, standard node code, and standard display words; The target packaging style mapping table is constructed by the following method: Parse the target packaging requirements and determine the target packaging style of the full track node, wherein the target packaging style at least includes: packaging node name, packaging node code, and packaging display words; The standard node name is bound to the packaging node name, the standard node code is bound to the packaging node code, and the standard display words are bound to the packaging display words.

7. The method according to claim 2, wherein: The standard style mapping table is constructed by the following method: Obtaining the original style of the full track node from the full business system or a third-party service provider, wherein the original style includes at least: an original node name, an original node code, and an original display script; According to the preset standard node configuration rules, the original node name is bound to the standard node name, the original node code is bound to the standard node code, and the original display words are bound to the standard display words.

8. The method according to claim 2, further comprising: Determining S warning trajectory nodes that need to be monitored during the execution of the target service from the N trajectory nodes, where N≥S; Configuring warning rules for the S warning trajectory nodes; The S warning trajectory nodes are monitored according to the warning rules.

9. The method according to claim 8, wherein: Monitoring the S warning trajectory nodes according to the warning rule includes: Obtaining a first timestamp corresponding to when the reference trajectory node is executed, wherein the reference trajectory node is a previous trajectory node of the warning trajectory node, or the reference trajectory node is a first trajectory node corresponding to the start of execution of the first fulfillment business; Obtain a second timestamp corresponding to the target monitoring time period; When the time interval between the second timestamp and the first timestamp is greater than a preset time threshold, a warning prompt is issued for the warning trajectory node.

10. A service execution device, comprising: A first determination module is used to determine, according to configuration information of a target service, M performance services to be performed in the process of providing the target service and an execution order of the M performance services, wherein the M performance services are performed one-to-one by M service execution systems, the M performance services involve N trajectory nodes, and the M and N are positive integers, and N≥M; A second determination module is used to determine M trigger trajectory nodes associated with the M contract performance services from the N trajectory nodes, wherein the M trigger trajectory nodes are used to trigger the M service execution systems to execute their respective corresponding contract performance services in a one-to-one correspondence; A style configuration module, configured to configure a standard style for each of the trigger trajectory nodes according to a pre-built trajectory standard style table, and generate a performance trigger rule in combination with the execution order of the M performance services, wherein the information in the trajectory standard style table includes standard styles of all trajectory nodes involved in all services; An execution module triggers the M fulfillment businesses to be executed sequentially based on the fulfillment triggering rules.

11. An electronic device, comprising: one or more processors; a storage device for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors are enabled to execute the method according to any one of claims 1 to 9.

12. A computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, causes the processor to execute the method according to any one of claims 1 to 9.

13. A computer program product, comprising a computer program, wherein when the computer program is executed by a processor, the method according to any one of claims 1 to 9 is implemented.

Images