Shared chain creation method of logistics supply chain alliance and business collaboration platform

Abstract

The invention relates to the technical field of logistics management, and provides a shared chain creation method of a logistics supply chain alliance and a business collaboration platform, and the method comprises the steps: responding to a downstream node creation request of a target node application, and determining each event item contained in the target node application; obtaining event groups corresponding to the event items and the event item combinations; outputting the downstream node application for a user to select; determining a target event group from the event groups; configuring a risk control task for the target event group according to a cooperation protocol of the target logistics supply chain alliance; and adding the target event group and the target downstream node application to the target shared chain. On the basis, flexible creation of the shared chain can be realized, and personalized risk control management is realized.

Description

Technical Field

[0001] The present application relates to the field of logistics management technology, and in particular to a shared chain creation method based on a logistics supply chain alliance, a logistics supply chain alliance business collaboration platform, an electronic device and a computer-readable storage medium. Background Art

[0002] With the rapid development of the logistics industry, the division of labor in the industry has gradually become more refined, and the business collaboration between different enterprises in the logistics supply chain has become increasingly close. However, in the traditional business management mode of enterprises, each enterprise controls the business process based on its own methods, such as internal ERP systems or manual management. The process management data involved in cross-enterprise freight business has poor circulation between enterprises, and there is a problem of opaque process information, which leads to untimely business flow or even interruption of flow, which greatly affects the stability of the cooperative relationship between enterprises.

[0003] To address this issue, patent application CN118569756A proposes to implement business data flow management between cooperative enterprises based on a shared chain, solving the sharing and visualization of cooperative business data between authorized enterprises. However, there is still much room for optimization in the flexibility of creating a shared chain. Summary of the invention

[0004] In order to achieve flexible creation of shared chains and meet various business needs of customers, the embodiments of the present application provide a shared chain creation method, a business collaboration platform, an electronic device and a computer storage medium for a logistics supply chain alliance.

[0005] A method for creating a shared chain for a logistics supply chain alliance provided in an embodiment of the present application includes the following steps: in response to a downstream node creation request of a target node application, determining each event item contained in the target node application; wherein the target node application is any node application in a target shared chain, and the target shared chain is any shared chain created by a user based on a target logistics supply chain alliance; obtaining an event group corresponding to each of the event items and event item combinations, wherein the event group includes a downstream node application associated with the corresponding event item or event item combination; outputting the downstream node application for user selection; and selecting the target downstream node application from each of the downstream node applications according to the target downstream node application selected by the user. A target event group is determined from the event group; a risk control task is configured for the target event group according to the cooperation agreement of the target logistics supply chain alliance; the risk control task is used to review the business processing process on the target downstream node application to determine whether the processing process complies with the cooperation agreement, and send an early warning message to the target logistics supply chain alliance if it is determined that it does not comply; the target event group and the target downstream node application are added to the target sharing chain, and the alliance enterprise identity information is configured for the target downstream node application, so that when the target sharing chain is created, the target downstream node application access entrance is created under the account corresponding to the alliance enterprise identity information.

[0006] Based on the above technical solution, the creation of the shared chain is based on the logistics supply chain alliance. In this way, it is possible to create multiple shared chains based on the same logistics supply chain alliance to adapt to different cooperation methods, so that users can choose some companies in the alliance based on actual business needs to complete certain business cooperation. Furthermore, by automatically matching the selectable downstream node applications based on the target node application, users can quickly select the target downstream node application. In addition, by obtaining downstream node applications based on the event item dimension, it can assist in mining the association between platform node applications, thereby providing users with more possibilities for cooperation methods, not limited to traditional existing methods. By configuring risk control tasks for the target event group, not only can the risk review of the cooperative business be realized, but also by separating personalized requirements from general application functions, the application development investment can be reduced, and the unified maintenance of each node application can be facilitated. In this way, the flexible configuration of the shared chain can be achieved.

[0007] In one implementation, the outputting of the downstream node application for user selection includes: based on the business roles of each alliance enterprise in the target logistics supply chain alliance, selecting a downstream node application that is adapted to the business role from each downstream node application in each event group for user selection.

[0008] Based on the above technical solution, it can be ensured that the target downstream node application selected by the user can be implemented based on the logistics supply chain alliance, avoiding the user from selecting the business that cannot be implemented based on the alliance, thereby improving the user experience.

[0009] In one implementation, the method further includes: in response to an approval node creation request, outputting a custom approval form creation interface to receive approval form creation requirements set by a user; wherein the approval node is located between the target node application and the target downstream node application; generating an approval form page code based on the approval form creation requirements, and creating an approval node task in the target sharing chain, so that after the target node application completes business processing, the approval node task is triggered for execution, and the approval node task includes providing an approval form to an approver based on the approval form page code, and triggering the execution of the target downstream node application after approval is passed.

[0010] Based on the above technical solution, users can flexibly create approval nodes and set approval forms as needed according to actual needs, thereby further meeting users' business management needs.

[0011] In one implementation, the method further includes: in response to an order node creation request, outputting an order template for user selection; determining a creation location of the order node based on the order template selected by the user, and creating an order node task in the target shared chain based on the creation location, wherein the order node task includes creating and sending an order to an order recipient based on the order template selected by the user.

[0012] Based on the above technical solution, business management based on standardized orders can be realized, thereby adapting to corresponding user needs and providing users with a variety of business management methods.

[0013] In one implementation, the event group further includes a parameter transfer rule, and the parameter transfer rule includes a method for obtaining input parameters of the target downstream node application based on relevant parameters of the target node application.

[0014] Based on the above technical solution, the acquisition of application input parameters of the target downstream node can be achieved.

[0015] In one implementation, the determining each event item included in the target node application includes: determining the event item corresponding to each business function according to the business functions enabled in the target node application.

[0016] Based on the above technical solution, not only can the business functions in the target node application be enabled on demand, avoiding misoperation and simplifying the operation method, but it also ensures that after the user sets the business function, the event group determined based on each event item is feasible.

[0017] In one implementation, the method for generating the event group includes: determining relevant parameters of each event item in the target node application and input parameters of other node applications; wherein the relevant parameters include input parameters, output parameters, intermediate parameters and extended parameters; determining the other node applications whose input parameters are included in the relevant parameters as downstream node applications corresponding to the target node application; determining the event items and event item combinations including the input parameters of the downstream node applications corresponding to the target node application in the relevant parameters, and generating the corresponding event group.

[0018] Based on the above technical solution, in the process of generating event groups, relevant parameters are selected to mine the association relationship between applications, which can realize in-depth mining of the relationship between platform applications to assist users in exploring more cooperation models and possibilities.

[0019] Based on the same inventive concept, an embodiment of the present application also provides a logistics supply chain alliance business collaboration platform, which realizes the creation of a shared chain based on the above method.

[0020] In addition, an embodiment of the present application also provides an electronic device, which includes a processor, a memory, and a program or instruction stored in the memory and executable on the processor, and the program or instruction implements the above method when executed by the processor.

[0021] The embodiment of the present application further provides a computer-readable storage medium storing a computer program, wherein the computer program implements the above method when executed by a processor. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] The drawings constituting a part of the present application are used to provide further understanding of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute improper limitations on the present application.

[0023] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0024] Figure 1 A schematic diagram of the structure of a logistics supply chain alliance business collaboration platform provided in an embodiment of the present application is shown.

[0025] Figure 2 A flow chart of a method for creating a shared chain for a logistics supply chain alliance provided in an embodiment of the present application is shown.

[0026] Figure 3 A flow chart of a method for generating an event group provided in an embodiment of the present application is shown.

[0027] Figure 4 A flow chart of a method for creating an approval node provided in an embodiment of the present application is shown.

[0028] Figure 5 A flow chart of a method for creating an order node provided in an embodiment of the present application is shown.

[0029] Figure 6 A flow chart of a business collaboration method provided in an embodiment of the present application is shown. DETAILED DESCRIPTION

[0030] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0031] In the description of the embodiments of the present application, unless otherwise specified, "plurality" means two or more, and various digital numbers are only used for the convenience of description and are not used to limit the scope of the embodiments of the present application.

[0032] The features, structures or characteristics in this application may be combined in one or more embodiments in any suitable manner. In various embodiments of this application, the size of the sequence number of each process does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0033] Some optional features in the embodiments of the present application may be implemented independently in some scenarios without relying on other features to solve corresponding technical problems and achieve corresponding effects. They may also be combined with other features in some scenarios as needed.

[0034] In this application, unless otherwise specified, the same or similar parts between the various embodiments can refer to each other. In the various embodiments of this application, if there is no special description and logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced to each other, and the technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships. The implementation methods of this application do not constitute a limitation on the scope of protection of this application.

[0035] The embodiments of the present application are described in detail below with reference to the accompanying drawings.

[0036] The shared chain creation method of the logistics supply chain alliance provided in the embodiment of the present application is implemented based on the logistics supply chain alliance business collaboration platform. Please refer to Figure 1 The logistics supply chain alliance business collaboration platform includes an alliance management module 101, a shared chain management module 102 and a business management module 103. The shared chain management module 102 is communicated with the alliance management module 101 and the business management module 103 respectively.

[0037] The alliance management module 101 provides the creation and maintenance functions of the logistics supply chain alliance, so that users can create and manage the logistics supply chain alliance according to their needs. The logistics supply chain alliance is used to establish an alliance relationship between the user enterprise and its partner enterprises. The user enterprise can send an invitation to the partner enterprise so that the partner enterprise can join the corresponding logistics supply chain alliance through the invitation entrance and become an alliance enterprise. The user enterprise can configure business roles for each alliance enterprise to clarify the business that the alliance enterprise can undertake in the logistics supply chain alliance.

[0038] It is worth noting that users can create corresponding logistics supply chain alliances based on their own business management needs. For example, they can create a logistics supply chain alliance for transporting a specific batch of goods, that is, only invite partner companies related to the transportation of this batch of freight. They can also create a logistics supply chain alliance that includes all partner companies, or they can create a logistics supply chain alliance that only includes high-quality partner companies.

[0039] The alliance management module 101 also provides a maintenance function for the logistics supply chain alliance, so that users can adjust the alliance enterprises in the logistics supply chain alliance, including but not limited to adding new alliance enterprises, deleting alliance enterprises, modifying the business roles of alliance enterprises, etc.

[0040] The sharing chain management module 102 is used to provide the creation and maintenance functions of the sharing chain. The user can implement the custom creation of the sharing chain based on the sharing chain management module 102.

[0041] The business management module 103 is used to manage the flow of business requests on the sharing chain when a user initiates a business request based on the sharing chain, so as to achieve collaborative processing of business requests among alliance enterprises.

[0042] Please refer to Figure 2 The shared chain creation method of the logistics supply chain alliance provided in the embodiment of the present application specifically includes the following steps.

[0043] S210 , in response to a downstream node creation request of a target node application, determining each event item included in the target node application.

[0044] Among them, the target node application is any node application in the target sharing chain, and the target sharing chain is any sharing chain created by the user based on the target logistics supply chain alliance.

[0045] The user can complete the creation of a new shared chain and the modification of the old shared chain through the shared chain creation interface provided by the shared chain management module 102. The target shared chain is the shared chain that is currently being created or modified. It is worth noting that the shared chain creation methods provided in the embodiments of the present application are all created based on the logistics supply chain alliance that has been created by the platform, that is, the shared chain is only used to serve a certain logistics supply chain alliance. Therefore, before creating a new shared chain, the user needs to select a logistics supply chain alliance to establish an association between the two. The target logistics supply chain alliance is any logistics supply chain alliance created by the user before creating a new target shared chain.

[0046] When a downstream node needs to be created for a target node application, the user can select the icon of the target node application in the creation interface and click the Create Downstream Node button to initiate a request to create the downstream node.

[0047] When receiving the downstream node creation request, the shared chain management module 102 determines the event items contained in the target node application. Among them, the event items are the operations required to implement the business functions in the target node application, including but not limited to the addition, modification, deletion, query of business data, and processing of business data. In one example, the event items correspond to function functions or function components. The relationship between the target node application and the business function is one-to-one or one-to-many, and the relationship between the business function and the event item is one-to-one or one-to-many.

[0048] S220, obtaining event groups corresponding to each event item and event item combination.

[0049] Specifically, the event group records all downstream node applications associated with the event items and event item combinations, and records the parameter transfer rules corresponding to each downstream node application. In the embodiment of the present application, the event group is pre-built based on each node application on the platform and recorded in the data table. Therefore, by querying the identification information of each event item, the corresponding event group can be obtained from the data table. In one example, an event group corresponds to an event item or a combination of multiple event items. For example, event item A corresponds to event group 1, and the combination of event items A and B corresponds to event group 2. Please refer to Figure 3 Taking the target node application as an example, the method for generating an event group in the embodiment of the present application includes the following steps.

[0050] S310, determining relevant parameters of the target node application.

[0051] Among them, relevant parameters include input parameters, output parameters, intermediate parameters and extended parameters, among which intermediate parameters are intermediate values ​​generated during the internal processing of the event item; extended parameters are parameters that can be obtained by extending the input parameters, output parameters or intermediate parameters. In one example, the extended processing includes calculation based on preset rules, querying the database based on known parameters, etc.

[0052] The relevant parameters of the target node application include relevant parameters of each event item, and the corresponding relationship between these relevant parameters and the event items can be recorded in a parameter table of the target node application.

[0053] S320, determining input parameters of other node applications.

[0054] Specifically, the platform provides applications that implement various business functions. These applications can be used to create a shared chain and serve as a node in the shared chain. Therefore, they can also be called node applications. Other node applications are all node applications other than the target node application on the platform.

[0055] S330, based on the relevant parameters and input parameters of other node applications, determine the downstream node application from other node applications.

[0056] In one example, the parameter table of the target node application may be queried based on the input parameters of other node applications to determine whether the parameter table includes the input parameters. If so, the node application is determined to be a downstream node application.

[0057] S340, determining event items and event item combinations including downstream node application input parameters in the relevant parameters, and generating corresponding event groups.

[0058] In implementation, the query parameter table contains event items of at least part of the input parameters of the downstream node application, and based on the correspondence between the event items and each input parameter in the query result, the event item or event item combination containing all the input parameters of the downstream node application is determined.

[0059] For example, the input parameters of the downstream node application D include C1, C2 and C3. The parameter table is queried based on these three parameters respectively. If the query result is: the relevant parameters of event item A1 include C1, C2 and C3, the relevant parameters of event item A2 include C1 and C2, and the relevant parameters of event item A3 include C3 and C1, then it can be determined that event item A1 is associated with the downstream node application D, and the event item combinations A2 and A3 are associated with the downstream node application D.

[0060] After obtaining the association relationship between each event item and event item combination in the target application and each downstream node application, a corresponding event group can be generated for each event item and each event item combination to record the association relationship with the downstream node application, as well as parameter passing rules. The parameter passing rules include a method for obtaining the input parameters of the target downstream node application based on the relevant parameters of the target node application. When the input parameters of the downstream node application correspond to intermediate parameters or extended parameters, the parameter passing rules record the corresponding acquisition method of the intermediate parameters or extended parameters.

[0061] S230, outputting each downstream node application associated with each event item and event item combination for user selection.

[0062] Specifically, each event item in the target node application and all downstream node applications associated with the event item combination may be output in a drop-down list for user selection.

[0063] In one example, based on the business roles of each alliance enterprise in the target logistics supply chain alliance, downstream node applications that are compatible with each business role can be selected from all associated downstream node applications for user selection. For example, when the target logistics supply chain alliance includes three alliance enterprises, the user enterprise and the cooperative enterprises E1 and E2, when creating the logistics supply chain alliance, the business role set for enterprise E1 is the carrier, and the business role set for enterprise E2 is the warehouse party and the purchaser. At the same time, according to the business applications ordered by the user enterprise on the platform, including procurement and sales management and warehousing management, it can be determined that the roles of the user enterprise include the owner and the warehouse party. Based on this, procurement and sales management, warehousing management, and transportation management can be selected from all downstream node applications for user selection, so that users can quickly find downstream node applications suitable for the target logistics supply chain alliance.

[0064] Optionally, when the number of selected downstream node applications exceeds the display range of the drop-down box, the downstream node applications can be sorted based on the historical sharing chain created by the user. In one example, the downstream node applications can be sorted according to the distance from the target node application in the historical sharing chain, such as placing the downstream node application with the largest number of times after the target node application at the front.

[0065] For example, the display range of the drop-down box is 10, that is, when the number of downstream node applications exceeds 10, the user needs to scroll down to display the remaining downstream node applications. In order for the user to quickly select the downstream node application, the downstream node application is output in descending order according to the number of times the downstream node application is located after the target node application in the historical sharing chain.

[0066] In another example, the downstream node application can be determined based on the business cooperation model on the logistics supply chain, where the business cooperation model on the logistics supply chain can be obtained based on industry research and platform sharing chains. For example, according to industry research, the downstream node applications corresponding to procurement and sales management include transportation management and warehousing management. Based on the statistics of the platform sharing chain, it can be further determined that warehousing management is used more frequently as a downstream node application of procurement and sales management, and warehousing management can be ranked before transportation management. Based on this, a more practical reference can be provided to new users.

[0067] S240: Determine a target event group from each event group according to a target downstream node application selected by a user from each downstream node application.

[0068] Specifically, after determining the target downstream node application, there may be a situation where the target downstream node corresponds to multiple event groups. For example, in the above example, the downstream node application D is associated with event item A1 and event item combinations A2 and A3, so the target event group needs to be selected from the corresponding event group.

[0069] In one example, the event group corresponding to a single event item, that is, the event group corresponding to event item A1, is preferentially selected. If there are multiple event items, the event item with the least number is selected based on the number of intermediate parameters and extended parameters in the parameter passing rule. If there are multiple options, the event item with the largest number of input parameters applied by downstream nodes is preferentially selected. If there are still multiple options, they are randomly selected.

[0070] Based on the above technical solution, giving priority to a single event item can facilitate problem location when an exception occurs in the execution process of the shared chain. Selecting the event item or event item combination with the least intermediate parameters and extended parameters can reduce the amount of computing tasks and save system resources. By making a selection based on the coverage of the input parameters, operation anomalies caused by output parameter anomalies can be avoided as much as possible.

[0071] S250, configuring risk control tasks for the target event group according to the cooperation agreement of the target logistics supply chain alliance.

[0072] Specifically, when creating a target logistics supply chain alliance, the user can configure a cooperation agreement for the target logistics supply chain alliance to regulate the cooperation process, including but not limited to relevant requirements on cargo type, transportation tool type, transportation route, operating personnel, deadline, storage method, etc.

[0073] When the target node application is located at the first node of the shared chain, the behavior specifications related to the target node application and the downstream node application can be determined according to the cooperation agreement to generate the corresponding risk control tasks. When the target node application is not the first node application, the behavior specifications related to the downstream node application can be determined according to the cooperation agreement to generate the corresponding risk control tasks.

[0074] The risk control task is used to review the business processing on the relevant node application to determine whether the processing process complies with the cooperation agreement, and output warning information when it is determined that the business processing process does not meet the requirements, so as to facilitate timely correction. In implementation, the risk control task may include the verification of the type of transportation tool, transportation route, operating personnel, and storage method to determine that these contents are consistent with the agreement content. For example, it can be verified by filling in the relevant information in the application, and confirmed by calling the relevant monitoring video of the transportation vehicle; the risk control task also includes monitoring the business processing period of the node application. For example, when the transportation period exceeds the provisions of the agreement, a warning message is generated and sent to the relevant alliance enterprise.

[0075] In this step, the risk control task is configured in the event group in the form of a task list. Based on this, in the general event group, the risk control task is personalized according to the alliance cooperation agreement, which can flexibly adapt to various risk control requirements of users.

[0076] S260, adding the target event group and the target downstream node application to the target sharing chain, and configuring the alliance enterprise identity information for the target downstream node application.

[0077] In implementation, the target downstream node is created by adding the target event group and the target downstream node application's corresponding information to the target sharing chain's record, and recording the alliance enterprise identity information corresponding to the target downstream node application.

[0078] Among them, the alliance enterprise identity information corresponding to the target downstream node application can be confirmed and configured according to the user input, or the alliance enterprise identity information corresponding to the target downstream node application can be directly determined according to the business role of the alliance enterprise. For example, if the target downstream node application is warehouse management, if there is only one alliance enterprise in the alliance whose business attribute is a warehouse party, then the alliance enterprise of the target downstream node is directly configured as the warehouse party enterprise. It is understandable that if there are two warehouse parties, options can be provided for the user to select and confirm. In this way, the automatic confirmation of the enterprise identity can be realized, and the user experience can be optimized.

[0079] It can be seen that in the embodiment of the present application, by separating the creation of the logistics supply chain alliance from the shared chain, not only can the flexible creation of the shared chain be achieved, but also corresponding shared chains can be created based on the same logistics supply chain alliance for different cooperation modes and business needs, which is convenient for user companies to manage and maintain cooperation with various alliance companies. At the same time, by automatically providing options during the creation of downstream node applications, the convenience of user operations can be improved. In addition, by establishing associations with downstream node applications based on event items and event groups, it can assist in digging out possible cooperation modes between node applications to adapt to various changes in actual needs.

[0080] When the user completes the creation of the sharing chain, the sharing chain management module 102 sends the sharing chain to the business management module 103. The business management module 103 creates an access entry for the node application under the corresponding account based on each node application in the sharing chain and the corresponding alliance enterprise identity information, such as creating a corresponding node application icon in the alliance application interface. In this way, each alliance enterprise can view the node application icon after logging into the platform, and access the corresponding node application by clicking the icon to perform related tasks. For example, when the target sharing chain is created, a downstream node application access entry can be created under the account corresponding to the alliance enterprise identity information configured for the target downstream node application.

[0081] Furthermore, when creating target node applications and downstream node applications, users can select the business functions enabled by the applications. Specifically, each node application may have multiple business functions, but in the business corresponding to the current shared chain, only some of these functions are needed. In order to simplify operations and prevent misoperation, users can choose to enable some business functions so that other functions are blocked during subsequent operations. For example, only the warehousing management function is enabled for warehousing companies.

[0082] It is understandable that business functions are implemented based on event items, and one business function may involve multiple event items. Accordingly, in the above step of determining the event items included in the target node application, it is necessary to determine the event items corresponding to each business function according to the business functions enabled in the target node application as the event items corresponding to the target node application. In this way, it can be ensured that the determined event groups are all achievable.

[0083] In other embodiments of the present application, approval nodes can also be added to the shared chain to meet different business management requirements. Figure 4 ,The method of creating an approval node includes the following steps.

[0084] S410, in response to the approval node creation request, output a custom approval form creation interface to receive the approval form creation requirements set by the user.

[0085] The position of the approval node can be flexibly set. In one example, the approval node can be located between the target node application and the target downstream node application.

[0086] Users can enter customized approval form creation requirements based on the creation interface and submit them.

[0087] S420, generating approval form page code based on the approval form creation requirement, and creating an approval node task in the target shared chain.

[0088] In one example, the creation of an approval form can be implemented based on low-code page technology.

[0089] Specifically, when a request to create an approval form submitted by a user is received, the approval form page code is generated accordingly, and an approval node task is created in the target shared chain, so that after the target node application completes business processing, the approval node task is triggered for execution. For example, the approval node task may include providing an approval form to the approver based on the approval form page code, and after the approval is passed, triggering the execution of the target downstream node application.

[0090] Based on this, custom approval tasks can be created to meet personalized business processing needs.

[0091] In other embodiments of the present application, the creation of order nodes can also be realized, so that the business processing process can be managed in the form of business orders, thereby meeting the user's business management needs. Figure 5 , the method for creating an order node includes the following steps: S510, in response to an order node creation request, output an order template for user selection.

[0092] The order template is pre-created and generated based on each business function in each node application. Outputting the order template to the user includes outputting the order template corresponding to the node application created in the target sharing chain to the user.

[0093] S520, determining a creation location of an order node according to the order template selected by the user.

[0094] Specifically, the corresponding node application can be determined according to the business function corresponding to the order template, and then the order node is set after the node application.

[0095] S530, creating an order node task in the target shared chain based on the creation position.

[0096] Among them, the order node task includes creating and sending an order to the order undertaker based on the order template selected by the user when the business flow is transferred to the order node.

[0097] Based on the above-mentioned shared chain, the business management module 103 can realize the business flow between alliance enterprises, which can be based on Figure 6 The method shown is implemented, and the business collaboration method provided in the embodiment of the present application includes the following steps: S610, in response to a business processing request issued by a target node application, querying and executing event group tasks.

[0098] Specifically, a user can create a business on the target node application to start a business cooperation or can receive a business processing task and access the target node application to process the business request. The business management module 103 can receive the business processing request and query the target event group to obtain the corresponding parameter processing task and risk control task. Among them, the parameter processing task is determined based on the parameter transmission rule, including obtaining intermediate parameters and extended parameters, which are used to obtain the input parameters of the target downstream node application.

[0099] In one example, after the target sharing chain is created, the business management module 103 creates a management process and a business process when the target sharing chain is used to execute business for the first time, wherein the business process is used to respond to business requests, and the management process is used to read the target transaction group corresponding to the target node application, and generate corresponding pending tasks according to the parameter transfer rules and risk control tasks in the target transaction group, and execute the corresponding pending tasks according to the processing progress of the business request. In this way, by isolating the processing of business requests and the processing of related tasks, the processing of business requests by business processes can be completed in a standard manner, so that the business processes can be uniformly managed and optimized.

[0100] After executing each pending task, the management process records the execution result, and when the execution result shows that there is a risk, the execution step sends a warning message to the alliance enterprises in the target logistics supply chain alliance.

[0101] S620, when the business request is processed, a business processing task for the next node is generated based on the business processing result and sent to the alliance enterprise corresponding to the target downstream node application.

[0102] In an embodiment, when the business request on the target node application is processed, the business will flow to the next node application and need to be processed by the corresponding alliance enterprise. Based on this, a corresponding task processing reminder can be generated and sent to the corresponding alliance enterprise, and when the target downstream node application is accessed, the target downstream node application is called based on the input parameters obtained in the above steps.

[0103] It can be seen that the shared chain created based on the embodiment of the present application can realize the collaborative processing of business within the logistics supply chain alliance, and the business processing and risk review of the business can be separated, which can not only ensure the rapid flow of business processes, but also realize risk identification and reminders based on cooperation agreements. And the acquisition and risk control of input parameters are realized based on the event group method, which makes the creation of shared chains more flexible and reduces the work of system opening.

[0104] In addition, an embodiment of the present application also provides an electronic device, which includes a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements a method as in any one of the implementations in the embodiments of the present application; wherein the processor may adopt a general-purpose central processing unit (CPU), a microprocessor, an application specific integrated circuit (ASIC), a graphics processing unit (GPU), or one or more integrated circuits, for executing relevant programs to implement the method in any one of the implementations in the embodiments of the present application.

[0105] The processor may also be an integrated circuit electronic device with signal processing capability. In the implementation process, each step of the method in any implementation of the embodiments of the present application may be completed by an integrated logic circuit of hardware in the processor or by instructions in software form.

[0106] The above-mentioned processor can also be a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the method disclosed in the embodiments of the present application can be directly embodied as a hardware decoding processor to be executed, or the hardware and software modules in the decoding processor can be combined and executed.

[0107] The software module may be located in a storage medium mature in the art, such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory, and the processor reads the information in the memory, and combines its hardware to complete the functions required to be performed by the units included in the data processing device of the embodiment of the present application, or executes the method in any one of the implementation modes in the embodiment of the present application.

[0108] Another embodiment of the present application relates to a computer-readable storage medium storing a computer program, which implements the above method when executed by a processor.

[0109] Those skilled in the art can understand that all or part of the steps in the above-mentioned implementation method can be completed by instructing the relevant hardware through a program, and the program is stored in a storage medium, including a number of instructions to enable a device (which can be a single-chip microcomputer, chip, etc.) or a processor to execute all or part of the steps of each implementation method of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program codes.

[0110] The above are all preferred embodiments of the present application, and the protection scope of the present application is not limited thereto. Therefore, any equivalent changes made according to the structure, shape, and principle of the present application should be included in the protection scope of the present application.

Claims

1. A method for creating a shared chain for a logistics supply chain alliance. It is characterized in that The method comprises the steps of: In response to a downstream node creation request of a target node application, determine each event item included in the target node application; wherein the target node application is any node application in a target sharing chain, and the target sharing chain is any sharing chain created by a user based on a target logistics supply chain alliance; Acquire an event group corresponding to each of the event items and event item combinations, wherein the event group includes a downstream node application associated with the corresponding event item or event item combination; Outputting the downstream node application for user selection; Determining a target event group from each of the event groups according to a target downstream node application selected by a user from each of the downstream node applications; Configure a risk control task for the target event group according to the cooperation agreement of the target logistics supply chain alliance; the risk control task is used to review the business processing process on the target downstream node application to determine whether the processing process complies with the cooperation agreement, and send warning information to the target logistics supply chain alliance if it is determined that it does not comply; The target event group and the target downstream node application are added to the target sharing chain, and the alliance enterprise identity information is configured for the target downstream node application, so that when the target sharing chain is created, the target downstream node application access entry is created under the account corresponding to the alliance enterprise identity information.

2. The method according to claim 1, It is characterized in that The outputting the downstream node application for user selection comprises: Based on the business roles of the alliance enterprises in the target logistics supply chain alliance, downstream node applications adapted to the business roles are selected from the downstream node applications in the event groups for selection by the user.

3. The method according to claim 1, It is characterized in that The method further comprises: In response to the approval node creation request, a custom approval form creation interface is output to receive the approval form creation requirements set by the user; wherein the approval node is located between the target node application and the target downstream node application; An approval form page code is generated based on the approval form creation requirement, and an approval node task is created in the target shared chain, so that after the target node application completes business processing, the approval node task is triggered to execute, and the approval node task includes providing an approval form to the approver based on the approval form page code, and triggering the execution of the target downstream node application after the approval is passed.

4. The method according to claim 1, It is characterized in that The method also includes: in response to an order node creation request, outputting an order template for user selection; determining a creation location of the order node based on the order template selected by the user, and creating an order node task in the target shared chain based on the creation location, wherein the order node task includes creating and sending an order to an order recipient based on the order template selected by the user.

5. The method according to claim 1, It is characterized in that The event group also includes parameter transfer rules, and the parameter transfer rules include a method for obtaining input parameters of the target downstream node application based on relevant parameters of the target node application.

6. The method according to claim 1, It is characterized in that The determining of each event item included in the target node application includes: According to the business functions enabled in the target node application, the event items corresponding to the business functions are determined.

7. The method according to claim 1, It is characterized in that The method for generating the event group comprises: Determine the relevant parameters of each event item in the target node application and the input parameters of other node applications; wherein the relevant parameters include input parameters, output parameters, intermediate parameters and extended parameters; Determine the other node application whose input parameter is included in the relevant parameters as a downstream node application corresponding to the target node application; The event items and event item combinations including the input parameters of the downstream node application corresponding to the target node application are determined in the relevant parameters, and the corresponding event group is generated.

8. A logistics supply chain alliance business collaboration platform, It is characterized in that The platform implements the creation of a shared chain based on the method described in any one of claims 1 to 7.

9. An electronic device, It is characterized in that The method comprises a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction implements the method according to any one of claims 1 to 7 when executed by the processor.

10. A computer-readable storage medium storing a computer program, It is characterized in that When the computer program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.

Images