Multi-enterprise collaboration method and platform for logistics supply chain based on shared chain

Abstract

This application relates to the field of smart logistics technology and provides a multi-enterprise collaboration method for a logistics supply chain based on a shared chain. The chain management module monitors the task processing progress of each business module on the target shared chain in real time, synchronizes the task processing progress data to the authorized role on the chain, and at the same time, by sending creation instructions, realizes the flow of target business between nodes on the chain, realizes the transparency of chain data, and ensures the smooth progress of business.

Description

Technical Field

[0001] The present application relates to the field of smart logistics technology, and in particular to a multi-enterprise collaboration method, platform and electronic equipment for a logistics supply chain based on a shared chain. 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 existing enterprise business management methods, each enterprise conducts business process control 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 inter-enterprise flowability and the problem of process information opacity, which leads to untimely business flow or even interruption of flow, greatly affecting the stability of cooperative relationships between enterprises. Summary of the Invention

[0003] In order to overcome the above-mentioned technical problems, the present application provides a multi-enterprise collaboration method for a logistics supply chain based on a shared chain, which is applied to a multi-enterprise collaboration platform for a logistics supply chain, wherein the platform includes a chain management module and multiple business modules. The method is executed by the chain management module, including: real-time monitoring of the task creation dynamics of each of the business modules; when it is monitored that the business module completes the first processing task based on the target business creation, determining the target shared chain for processing the target business according to the chain identifier carried in the target business, tracking and obtaining the processing progress data of the first processing task, and sharing the processing progress data in real time to the authorized role on the target shared chain; determining the node type of the node corresponding to the business module on the target shared chain. If the node type is an initial node or an intermediate node, when it is monitored that the processing of the first processing task is completed, sending a task creation instruction to the business module corresponding to the next node to instruct the business module corresponding to the next node to create a second processing task based on the processing result of the first processing task and the target business.

[0004] Based on the above technical solution, dynamic monitoring of each business module is achieved through the chain management module, so that whenever a task is created in a business module, the tracking of the task processing progress data of the business module is started, and the data is shared with the authorized role on the target shared chain, so that the corresponding chain partners can view the processing progress of the target task on the target shared chain in a timely manner. At the same time, when the task on the business module is completed, the chain management module can instruct the business module corresponding to the next node on the target chain to create the corresponding processing task, thereby realizing the automatic flow of the target business between the nodes on the chain, so that the chain management module can update the flow progress of the chain business in a timely manner. When the business module corresponding to the next node creates and completes the processing task, the chain management module will also check the progress data of the task. Tracking and sharing. In this way, as long as any business module corresponding to the target shared chain creates a corresponding processing task based on the target task, the processing progress data will be controllably shared with the authorized role on the chain, thereby realizing data transparency of the business on the chain, so that the authorized role can timely know the processing progress of the target business. At the same time, the chain management module uniformly controls the flow of the target business between nodes, avoiding the problem of untimely flow in cross-enterprise flow. In addition, based on the above solution, by realizing the flow of the target business on the target business chain, not only can users build corresponding shared chains according to business needs to ensure the smooth development of the business, but also users can choose more suitable partners for different business needs, which helps users seek and maintain stable cooperative relationships.

[0005] In one implementation, the method for creating the target sharing chain includes: responding to a target sharing chain creation request initiated by a user, parsing the creation request to obtain sharing chain attribute information and invitee information, wherein the sharing chain attribute information includes role names, relationships between roles, and role permissions; determining invitees based on the invitee information, and sending an on-chain invitation to the invitee; after receiving a confirmation reply to the on-chain invitation, instructing the user to determine the partner corresponding to the role name from the invitees; in response to the confirmation information submitted by the user, constructing the nodes and node relationships on the target sharing chain according to the role names and the relationships between the roles, and configuring the corresponding business modules for the partners according to the role permissions and setting on-chain data viewing permissions.

[0006] Based on the above technical solution, users can create a shared chain to complete the task according to actual business needs. During the creation process, they can freely set the role names, relationships between roles, and role permissions on the chain to build a shared chain that fully meets business needs. At the same time, users can control the degree of transparency of on-chain data through the configuration of role permissions, so that only authorized roles can view the corresponding on-chain data, avoiding data security issues caused by excessive disclosure of data.

[0007] In one implementation, the instructing the user to determine the partner corresponding to the role name includes: when there are multiple invitees with the same role name, generating a capability assessment result for each invitee based on historical cooperation data and invitee qualification analysis for the user's reference and selection; or, providing a bidding interface so that each invitee completes the bidding based on the bidding interface, and outputting the bidding results for the user's reference and selection.

[0008] Based on this, the optimal selection of partners corresponding to the role names can be achieved, helping users to select more suitable partners for the target sharing chain.

[0009] In one implementation, the method also includes: when monitoring that the business module completes the first processing task based on the target business creation, pre-constructing the processing task on the business module corresponding to the unreached node based on the target business, wherein the unreached node is all nodes on the target sharing chain that are located after the current node; evaluating whether the pre-constructed processing task can be completed smoothly, and if it cannot be completed smoothly, generating a resource emergency scheduling task and sending it to the corresponding partner.

[0010] Based on the above technical solution, the chain management module pre-creates corresponding processing tasks for the target business on the nodes that have not yet arrived on the target shared chain, and evaluates whether these tasks can be completed smoothly, so as to predict whether the target business can be completed smoothly when it actually arrives at the relevant nodes, and generates resource emergency scheduling tasks and sends them to the corresponding partners, so that the corresponding partners can plan resource scheduling in advance to ensure the smooth completion of the target tasks.

[0011] In one implementation, the method also includes: tracking the processing progress of the resource emergency scheduling task, and if it is determined that the resource emergency scheduling task cannot be completed within the preset time, issuing a control instruction to the business module corresponding to the initial node of the target sharing chain to instruct the business module corresponding to the initial node to refuse the user to initiate a new business to the target sharing chain.

[0012] Based on the above technical solution, risk management of the target sharing chain can be achieved to avoid the situation where the target sharing chain cannot guarantee the smooth completion of the current target task and takes on new tasks, thereby causing multiple tasks to fail to be completed smoothly.

[0013] In one implementation, the method for creating the target sharing chain includes: in response to a sharing chain editing request initiated by a user, modifying a designated sharing chain in a sharing chain resource pool to generate the target sharing chain.

[0014] Based on the above technical solution, it is possible to modify the existing shared chain and directly obtain the target shared chain, which can realize the rapid creation of the target shared chain and deepen the cooperation with existing partners, which is conducive to maintaining a stable cooperative relationship.

[0015] In one embodiment, the chain management module is provided with a first communication port and a second communication port. By monitoring the first communication port, the task data reported by each of the business modules is obtained to realize real-time monitoring of the task creation dynamics of each of the business modules, and the task creation instruction is sent to the business module corresponding to the next node through the second communication port, wherein the first communication port is different from the second communication port.

[0016] In one implementation, the service priority of the second communication port is higher than that of the first communication port.

[0017] Based on the above technical solution, different types of data are received through different communication ports. On the one hand, the communication pressure of a single port can be reduced. On the other hand, the chain management module can distinguish different types of data based on the port, and give priority to processing the data received by the second communication port according to the business priority, thereby ensuring the timely flow of target business between nodes.

[0018] Based on the same inventive concept, the present application also provides a logistics supply chain multi-enterprise collaboration platform, which includes a chain management module and multiple business modules, wherein the chain management module is used to implement the above method.

[0019] In addition, 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 implements the above-mentioned method when executed by the processor.

[0020] In summary, this application has at least the following beneficial effects: 1. It achieves transparency of on-chain data, allowing authorized roles to obtain timely and detailed information on on-chain business progress data, facilitating user evaluation of partners' business processing capabilities and facilitating user selection of appropriate partners for subsequent business. 2. It enables the automated flow of on-chain business, eliminating the need to rely on the flow operations of individual partners, ensuring the smooth progress of the target business on the target shared chain.

[0021] 1. By pre-building and evaluating processing tasks, we can know in advance whether there are risks in the subsequent processing of the target business. Then, by notifying the partners in advance, we can schedule service resources to ensure the smooth completion of the target tasks.

[0022] 2. Setting different communication ports for different types of task data not only reduces port communication pressure, but also allows for quick identification of different types of task data based on the communication port, thereby improving the data processing efficiency of the chain management module. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] The accompanying drawings, which constitute part of this application, are used to provide a further understanding of the application.

[0024] The embodiments and their descriptions are used to explain the present application and do not constitute improper limitations on the present application.

[0025] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following describes the technical solutions required in the embodiments.

[0026] The accompanying drawings are used for a brief introduction. Obviously, the accompanying drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other accompanying drawings can be obtained based on these accompanying drawings without paying any creative work.

[0027] Figure 1 A schematic diagram of the functional modules of the logistics supply chain multi-enterprise collaboration platform provided in an embodiment of the present application is shown.

[0028] Figure 2 A schematic diagram of a sharing chain structure provided in an embodiment of the present application is shown.

[0029] Figure 3 A schematic diagram of a shared chain structure in an example of an embodiment of the present application is shown.

[0030] Figure 4 A flow chart of a method for creating a sharing chain provided in an embodiment of the present application is shown.

[0031] Figure 5 A flowchart of a multi-enterprise collaboration method for a logistics supply chain based on a shared chain provided by an embodiment of the present application is shown.

[0032] Figure 6 A flowchart of a multi-enterprise collaboration method for a logistics supply chain based on a shared chain is shown in another embodiment of the present application. DETAILED DESCRIPTION

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

[0034] In the description of the embodiments of the present application, unless otherwise specified, "multiple" means two or more, and "first", "second" and various numerical numbers are only distinctions for the convenience of description and are not used to limit the scope of the embodiments of the present application.

[0035] The features, structures, or characteristics of this application may be combined in any suitable manner in one or more embodiments. In the various embodiments of this application, the order of the sequence numbers of the processes does not necessarily indicate the order of execution. The order of execution of the processes should be determined by their functions and inherent logic, and should not constitute any limitation on the implementation of the embodiments of this application.

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

[0037] 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, unless otherwise specified and there is no logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced to each other. The technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships. The implementation methods of this application do not constitute a limitation on the scope of protection of this application.

[0038] In order to solve the above technical problems, the present application embodiment provides a logistics supply chain multi-enterprise collaboration platform, please refer to Figure 1 The logistics supply chain multi-enterprise collaboration platform 10 includes at least a chain management module 101 and multiple business modules 102 (shown as 102a, 102b... in the figure), and each business module 102 is evenly communicated with the chain management module 101.

[0039] Among them, the business module 102 is a general term for functional modules on the platform used to implement specific business management. In specific applications, the business module 102 can be any one of the procurement management module, warehousing management module, transportation management module, and sales management module. The basic functions that can be achieved can refer to the relevant management software in the existing technology. Developers can implement relevant business modules on the platform according to the actual application scope and business needs. This application does not limit this.

[0040] The chain management module 101 can be used to manage the shared chain, including the creation, modification, and deletion of the shared chain, as well as the management and control of the business on the shared chain, including the acquisition and sharing of business processing data and the monitoring of the business processing flow.

[0041] Among them, the shared chain is created by the user according to business needs for a certain business or a certain type of business. Please refer to Figure 2The shared chain 200 includes multiple nodes 201 and 202. Each node is assigned a corresponding role R1 and R2. Each role corresponds to a partner C1 and C2. The role is set by the user according to business needs, such as supplier, carrier, and consignee, which is used to limit the business functions to be implemented by each node on the shared chain. The partner is an entity enterprise, which is used to play the corresponding role and is the object that actually completes the business operations of the corresponding node.

[0042] For example, see Figure 3 , a user creates shared chain 300, dedicated to the delivery of item A. Shared chain 300 may include four nodes: Node 301, Node 302, Node 303, and Node 304, corresponding to the roles of supplier, shipping warehouse, carrier, and receiving warehouse, respectively. The corporate entities playing each role are: shipper, warehousing company, logistics company, and purchasing company. It is worth noting that users can create corresponding shared chains based on different freight needs. This shared chain can be a complete freight chain, that is, covering all nodes from the shipper to the consignee, or a fragmented chain, such as only including the shipping warehouse and carrier.

[0043] The chain management module 101 can configure business modules with corresponding functions for each node on the shared chain 300: sales management module, warehouse management module, transportation management module, and warehouse management module.

[0044] It is worth noting that the business modules corresponding to each node on the chain are independent of each other. Even if two business modules with the same function are configured on the same chain, the two business modules are independent of each other. The data of each business module is stored separately and the assigned login account is also different. Therefore, the number of business modules on the platform 10 will change according to the number of nodes in the shared chain. That is, when a new shared chain is created, the corresponding business module will also be added.

[0045] To optimize the user experience, in another implementation, when the same business entity plays the same role on different shared chains, it can reuse the same business module and use chain identifiers to distinguish and manage the business data. This allows partners to log into only one business module to process tasks on related shared chains, eliminating the need to log into different business modules separately. This improves the user experience and conserves platform service resources.

[0046] Please refer to Figure 4 Based on the above-mentioned logistics supply chain multi-enterprise collaboration platform, the embodiment of this application provides a method for creating a shared chain.

[0047] As shown in the figure, a shared chain creation method is executed by the chain management module and includes the following steps:

[0048] S401 , in response to a sharing link creation request initiated by a user, parsing the creation request to obtain sharing link attribute information and invitee information.

[0049] In one implementation, the user submits a creation request through the chain creation interface provided by the chain management module. The creation request carries relevant data, including shared chain attribute information and invitee information.

[0050] The shared chain attribute information includes the role name, the relationship between roles, and the role permissions. The relationship between roles is used to determine the corresponding node position of each role on the chain. The role permissions include the data viewing permissions corresponding to the role name and the operation permissions of the business module. In this application, the role with data viewing permissions is called the authorized role.

[0051] The invitee information may be a list of designated invitees corresponding to the role, or may be requirements for the invitees.

[0052] S402: Determine the invitee based on the invitee information, and send a chain invitation to the invitee.

[0053] Specifically, when the invitee information provided for a role meets the corresponding requirements, the chain management module can prioritize obtaining invitees that meet the requirements from the partner resource pool based on the requirements. The partner resource pool is a resource pool constructed by the chain management module based on the partners corresponding to each node on the user's historical shared chain. If the user's partner resource pool does not contain a qualified invitee, the module can further match qualified invitees from the resource pools of other users on the platform, or from companies that have settled on the platform.

[0054] The invitation to join the chain can be sent through SMS, email, platform message, etc.

[0055] S403: After receiving the confirmation reply of the on-chain invitation, instruct the user to determine the partner corresponding to the role name from the invitees.

[0056] Specifically, after receiving the confirmation reply of the on-chain invitation from each invitee or after the invitation period ends, the user can be notified to select the partner corresponding to each role name from the invitees who have confirmed on-chain.

[0057] In actual applications, a role name may correspond to multiple invitees, so users need to make a selection. In response to this situation, in one implementation, the chain management module can generate capability assessment results for each invitee based on historical cooperation data and invitee qualification analysis for user reference and selection. Specifically, the platform requires new invitees to submit relevant qualification certificates for the platform to verify their identities, ensure that the invitees meet relevant policy requirements, and ensure the legality and compliance of the business. Historical cooperation data includes the invitee's business participation in other shared chains, including the number of chains, activity, type and number of businesses undertaken, historical task completion status, cooperation credibility, etc. The chain management module calculates the invitee's score based on the corresponding preset weights and combines the data of these dimensions for user reference. At the same time, when the data of a certain dimension is lower than the preset standard, an early warning is issued.

[0058] In another embodiment, the chain management module may provide a bidding interface, so that each invitee can complete the bidding based on the bidding interface, and output the bidding results for the user's reference and selection.

[0059] It is understood that in the embodiments of this application, the above two methods can be combined to provide selection references. Different evaluation methods can also be used for different roles. The specific settings can be set according to actual application needs, and this application is not limited to this. Based on this, by providing users with selection references, users can be assisted in selecting higher-quality partners to ensure the smooth development of business.

[0060] After receiving the confirmation reply of the invitation to go on the chain, the chain management module can also review the service qualifications of the invitee according to the preset review standards, and synchronize the invitees who pass the review to the cooperation resource pool to expand the cooperation resource pool. The chain management module can also refuse to go on the chain to the invitees who fail the review, or mark them with warnings to remind users of risks.

[0061] Among them, the preset review standards are generated based on the business requirements in the shared chain attribute information and the business requirements of other shared chains created by the user. Business requirements are used to ensure that the invitee has the ability to undertake the corresponding business. In one example, they may specifically include business qualifications, business scope, risk level, credit level, etc. For example, for a warehousing company, business requirements may include storage space, storage conditions and other requirements. In a specific implementation, the preset review standards can also be proposed by the user, and the chain management module gives priority to the preset review standards proposed by the user. S404, in response to the confirmation information submitted by the user, construct the nodes and node relationships on the shared chain according to the role names and the relationships between the roles.

[0062] S405: Configure the corresponding business module for the partner according to the role name and set the on-chain data viewing permission for the partner according to the role permission.

[0063] Referring to the shared chain 300, it can be seen that the business scope performed by each role name on the shared chain is different. Therefore, the partners corresponding to the role name need to configure the corresponding business modules so that each partner can perform the corresponding processing tasks through the business module operations configured for it, such as outbound tasks, inbound tasks, waybill tasks, etc.

[0064] In the implementation, in the default settings of the platform, the role permissions of each node on the shared chain are that they can only view the business data related to the node, and the chain creator can view the business data of the entire chain. Users modify the default settings to expand the scope of the partner's permission to view, such as Figure 3 In the example shown, users can grant full data viewing permissions to both the shipper and the purchasing company, allowing both the supplier and consignee to obtain timely information on the execution and flow of transactions. In some application scenarios, funding parties are also involved. These parties do not participate in actual transaction processing within the shared chain, but require information on transaction status to initiate funding. Therefore, users need to grant full chain data viewing permissions to these parties.

[0065] At this point, the shared chain is built and will be stored in the user's shared chain resource pool.

[0066] In the embodiments of the present application, in addition to creating new shared chains based on creation requests, users can also modify shared chains in the shared chain resource pool to obtain new shared chains. Specifically, the chain management module provides a chain management interface that allows users to manage shared chains in the shared chain resource pool, including deleting and editing shared chains.

[0067] In one example, in response to a user-initiated request to edit a shared chain, the chain management module modifies the shared chain specified in the edit request based on the edited content, generating a new shared chain. Modifications can include deleting some nodes, replacing some nodes, or relocating nodes. The modified shared chain is stored as a new shared chain in the shared chain resource pool. The original shared chain can be retained or deleted from the resource pool based on user instructions.

[0068] In actual applications, after editing a shared chain, the user may wish to migrate existing businesses on the chain directly to the edited shared chain. Based on this, the chain management interface also provides a business migration option. When the user selects business migration, the chain management module can migrate the business on the chain according to this option. In one example, the migration method includes:

[0069] Determine the task processing status on each node of the old chain. For the first node that currently has a processing task, determine the second node with the same role name from the new chain based on the role name corresponding to the first node. When the processing task is completed, send a task creation instruction to the next node of the second node, thus completing the migration of the business from the old chain to the new chain. If there is no node with the same role name in the new chain, then continue to confirm whether there is a node with the same role name as the next node of the first node in the new chain, and so on, until the second node is matched. When the business is about to flow to the old chain node corresponding to the second node, send a task creation instruction to the second node to realize the flow of business to the new chain. In this way, the migration of business is realized, and the smooth development of business is also guaranteed.

[0070] It is worth noting that before deleting a shared chain, the chain management module will first confirm that there is no business being processed on the shared chain to be deleted. Otherwise, it will wait until the business processing is completed before deletion to avoid affecting the business development.

[0071] In order to ensure that the business on the shared chain can flow smoothly and realize the sharing of data on the chain, the embodiment of the present application provides a multi-enterprise collaboration method for the logistics supply chain based on the shared chain, which is executed by the chain management module. Please refer to Figure 5 , the method comprises the following steps:

[0072] S501, real-time monitoring of task creation dynamics of each business module.

[0073] In one implementation, when there is a processing task update, the business module actively sends task data to the first communication port of the chain management module. The chain management module receives the task data sent by each business module in real time by monitoring the first communication port, where the task data includes task type, task status and process data.

[0074] The task type is determined by the business functions implemented by the business module. For example, the business types covered by the warehouse management module may include outbound delivery, inbound delivery, picking, and inventory, while the business types covered by the transportation management module may include transportation planning, scheduling, and tracking. Task status indicates the progress of task processing, including statuses such as created, in progress, and completed. Process data records all data from task creation to completion, including task content, person handling the task, processing time, and processing content. It is understood that task data may also carry the module identifier of the business module to indicate the source of the data.

[0075] It is worth noting that in order to ensure that the chain management module can obtain the real-time dynamics of the tasks processed on the business module in a timely manner, in one implementation, the business module can directly report to the chain management module when new task data is generated; in another implementation, when the number of business modules on the platform is large and the task data is updated quickly, the frequency of the business module reporting data to the chain management module can be controlled by setting the reporting node. For example, only when a new task is created, the status of the key processing node changes, and the task processing is completed, the relevant data in the process will be reported to the chain management module. This ensures that the chain management module can promptly know the key status changes of the processing task, and can reduce the number of communications between modules, thereby alleviating the communication pressure on the platform.

[0076] The chain management module determines whether a new task is created on the business module based on the received task data.

[0077] S502: When it is detected that the service module has completed the first processing task based on the target service, a target shared chain for processing the target service is determined according to a chain identifier specified by the target service.

[0078] The target service may be any service initiated by the user according to actual needs, and the target sharing chain is a service collaborative resource chain selected for the target service from the sharing chain resource pool when the user initiates the target service.

[0079] by Figure 3 Taking the shared chain 300 in as an example, the initiator user is the cargo owner, and the cargo owner specifies that all goods in batch 001 will be delivered through the shared chain 300. Correspondingly, the target business is to send the goods in batch 001 to the purchasing enterprise warehouse, and the target shared chain is the shared chain 300.

[0080] The cargo owner can create a shipping task (first processing task) based on the target business information in the sales management module and enter the chain identifier of the shared chain 300 in the creation request interface to specify that the batch of goods be processed through the shared chain 300. It can be understood that the chain identifier is the identity information used to uniquely mark the shared chain. The sales management module writes the chain identifier into the task data and sends it to the chain management module. When the shipping task processing is completed, the sales management module will send the approved shipping order to the chain management module. Based on this, the chain management module sends a second task creation instruction (outbound task) to the warehouse management module corresponding to the shipping warehouse, and carries the shipping order and cargo batch 001 in the instruction message.

[0081] It is worth noting that the first processing task in the embodiment of the present application does not specifically refer to a certain type of processing task. It is used to refer to any business processing task created on any business module, that is, the processing tasks created on each business module are all first processing tasks.

[0082] S503: Track and obtain the processing progress data of the first processing task, and share the processing progress data with the authorized role on the target sharing chain in real time.

[0083] In one embodiment, the chain management module provides a chain information display interface for users to view the data on the chain. After the user logs in to the platform, he can view the processing progress of the target business on the target shared chain by accessing the chain information display interface. The chain management module will view the content of the permission control interface based on the data of the logged-in user, so that the user can only view the data within the scope of permission. This not only realizes the sharing of on-chain data, but also can flexibly adjust the data visibility range of each logged-in user according to the permission settings, thereby improving data security and avoiding interference of irrelevant data on users.

[0084] In another embodiment, the chain management module can realize real-time sharing of processing progress data by sending processing progress data of corresponding authority scope to each authorized role, so that users can view it through corresponding business modules, text messages, emails, platform station messages, etc.

[0085] It is understandable that developers can selectively implement corresponding data sharing methods based on actual product design conditions, and this application is not limited to this.

[0086] S504: Determine the node type of the node corresponding to the business module.

[0087] It is understood that a shared chain includes at least two nodes, which can be divided into initial nodes, intermediate nodes, and terminal nodes according to their locations. In the embodiment of the present application, nodes located between the initial node and the terminal node are referred to as intermediate nodes. In this step, the node type can be determined based on the location of the node corresponding to the business module on the target shared chain. If the node type is an initial node or an intermediate node, step S505a is executed; if the node type is a terminal node, step S505b is executed.

[0088] S505a, when monitoring the completion of the first processing task, sending a task creation instruction to the business module corresponding to the next node to instruct the business module corresponding to the next node to create a second processing task based on the processing result of the first processing task and the target business.

[0089] In this step, when the chain management module obtains the completion of the first processing task, it determines the next node based on the position of the business module on the target shared chain, and then determines the corresponding business module through the mapping relationship between the node and the business module, and sends a task creation instruction to the business module corresponding to the next node through the second communication port.

[0090] In one implementation, the task creation instruction includes the target business information and the processing results of the first processing task. After receiving the task creation instruction, the business module corresponding to the next node can directly parse the target business information and the processing results of the first processing task to create the second task. For example, after receiving the task creation instruction from the chain management module, the warehouse management module corresponding to node 302 creates a shipment task for batch 001 based on the shipping order processed by the sales management module and the target business information. Based on this, the chain management module implements the management and control of business flow between nodes, thereby ensuring the smooth flow of target business on the target shared chain.

[0091] In another implementation, in order to reduce the data transmission pressure between the chain management module and the business module, when the business module completes the first processing task, it actively sends the first task processing result and target business information to the business module corresponding to the next node. In this way, the task creation instruction sent by the chain management module does not need to carry too much data, which reduces the data transmission pressure and improves the transmission efficiency of the creation instruction.

[0092] After receiving the task creation instruction, the business module corresponding to the next node may create a second processing task based on the data obtained from the business module of the previous node.

[0093] In actual application, data transmission between modules may result in packet loss. Based on this, after receiving the task creation instruction sent by the chain management module, if the business module corresponding to the next node finds that it has not yet received data from the previous node, it can actively request the corresponding data from the previous node. If no response is received within the preset time or after repeating the request a preset number of times, it can request the third port of the chain management module to obtain relevant data and mark the communication line as abnormal. After receiving the data acquisition request through the third port, the chain management module obtains data from the corresponding node and responds to the acquisition request based on the acquired data. If the chain management module also does not receive a response, it indicates that the business module has an abnormality. In order to ensure the smooth progress of the tasks on the chain, the chain management module can directly request access to the platform database to obtain relevant data and feedback the abnormal situation to the background administrator to promptly troubleshoot the problem.

[0094] In this way, when data is not received normally, the business module can obtain the data required to create the task by repeatedly requesting the chain management module in turn, reducing the negative impact of abnormal data transmission between modules on business flow.

[0095] It is worth noting that according to the above description, when the business module corresponding to the next node completes the creation of the second processing task, it will send the task data to the chain management module, and the chain management module will continue to execute the above steps to realize the flow control of the target business between each node.

[0096] S505b: Determine whether the target business is completed.

[0097] It can be seen that by executing the above steps, the chain management module can ensure the smooth flow of target business between nodes on the target shared chain. At the same time, it also obtains all on-chain data and shares it synchronously with relevant role users based on role authorization, thereby realizing the visualization of on-chain data, allowing relevant partners to be informed of business processing dynamics in a timely manner, avoiding misunderstandings and conflicts caused by data asynchrony, which is not only conducive to improving the cooperation efficiency of on-chain partners, but also increases mutual trust and helps stabilize cooperative relationships.

[0098] In one embodiment, the first communication port, the second communication port, and the third communication port are different communication ports on the chain management module. By using different communication ports to receive different types of data, not only is the pressure on single-port communication reduced, but different types of data can also be directly distinguished according to the port, thereby improving processing efficiency. Optionally, corresponding service priorities can be configured for different communication ports to ensure timely processing of key tasks. For example, the service priorities of the first communication port, the second communication port, and the third communication port can be set to increase in sequence, that is, the service priorities of the first communication port, the second communication port, and the third communication port are from low to high, thereby ensuring a rapid response to abnormal situations received by the third communication port, timely eliminating problems, and ensuring rapid flow of services between nodes.

[0099] To further ensure the smooth development of on-chain business, please refer to Figure 6 , the above collaborative method further includes the following steps:

[0100] S601 : When it is monitored that the service module completes the first processing task based on the target service, a processing task on the service module corresponding to the unreached node is pre-built based on the target service.

[0101] The unreached nodes are all nodes on the target shared chain that are located after the current node. For example, when the chain management module detects that the sales management module on the shared chain 300 has completed the creation of the shipping task, it pre-builds the outbound task on the warehouse management module corresponding to the shipping warehouse, the transportation plan on the transportation management module corresponding to the carrier, and the inbound task on the warehouse management module corresponding to the receiving warehouse.

[0102] S602, evaluating whether the pre-built processing task can be successfully completed. If not, executing step S603a; if so, executing step S603b.

[0103] In one specific implementation, the chain management module can generate service resource requirements based on pre-built processing tasks to indicate the service resources required to complete the target business, such as warehouse storage space, inbound and outbound time, etc., and send the service resource requirements to the corresponding partners, instructing them to confirm whether the service resources are sufficient, and determine the evaluation results based on the feedback from the partners.

[0104] In another implementation, the chain management module may obtain the total available service resources provided by each partner in advance. For example, when the initial node of the target shared chain completes the creation of the first processing task, the total available service resources that can be provided by the partners are obtained from the business modules corresponding to other nodes on the chain. When evaluating the pre-built processing tasks, the current available service resources of each business module are determined based on the total available service resources corresponding to each business module and the service resources occupied by the tasks currently being processed on each business module. The service resources required for the target business are evaluated based on the currently available service resources to obtain the evaluation results.

[0105] S603a: Generate an emergency resource scheduling task, send it to the corresponding partner, and execute step S604.

[0106] S603b, record the evaluation results.

[0107] S604: Track the processing progress of the resource emergency dispatch task and evaluate whether the resource emergency dispatch task can be completed within a preset time.

[0108] Specifically, the chain management module sends the generated resource emergency dispatch task to the corresponding business module, and determines whether it can be completed within the preset time based on the feedback from the partner on the emergency dispatch task in the business module.

[0109] If it is determined that the resource emergency scheduling task cannot be completed within the preset time, step S605a is executed; otherwise, step S605b is executed.

[0110] S605a: Send a control instruction to the service module corresponding to the initial node of the target sharing chain to instruct the service module corresponding to the initial node to reject the user from initiating a new service to the target sharing chain.

[0111] If any node on the target shared chain is determined to be unable to complete resource scheduling, the chain management module controls the corresponding business module of the initial node of the target business chain to refuse to accept new tasks initiated by the user to the target shared chain until the target business is processed on the node that cannot complete resource scheduling or the node reports that resource scheduling is complete. This prevents the smooth progress of new services due to insufficient node resources and ensures that all services on the target shared chain can be completed smoothly.

[0112] S605b: Evaluate the credibility of the partner based on the actual completion status of the task processed on the node.

[0113] In one implementation, if the business module corresponding to a node performs an emergency resource tracking dispatch task and reports dispatch completion, the chain management module can obtain the actual completion status of the corresponding processing task when the target business arrives at the node to determine whether the feedback is true. If the processing task is successfully completed as required, the credibility score of the corresponding partner is increased; otherwise, it is deducted. This also provides a reference for users to manage the shared chain.

[0114] It is worth noting that since the user's business initiation behavior cannot be predicted, the task creation status on each business module is changing in real time. Correspondingly, the business resource reserves that can be used to execute processing tasks are also changing in real time. Optionally, in order to ensure the accuracy of the evaluation, in step S601, the chain management module can pre-build the processing tasks on subsequent nodes when a new task is created on the business module. Therefore, during the process of the target business circulating on the target chain, the service capabilities of the nodes that have not been reached will be continuously evaluated, thereby ensuring the smooth development of the target business.

[0115] For example, when the target business flows to the shipping warehouse, the chain management module will pre-build the transportation plan in the carrier's transportation management module and the warehousing task in the receiving warehouse's warehouse management module, and then evaluate them. This can minimize the possibility of target business being delayed due to resource fluctuations.

[0116] Optionally, when the chain management module determines that the business module that creates a new processing task is an intermediate node, it can determine whether a new processing task is created on the subsequent node after the time point of the latest pre-built processing task of the subsequent node. If so, the processing task corresponding to the target business is pre-built for the node again. If not, it means that the resources on the node have not changed, and there is no need to pre-build it again, which can reduce the processing pressure of the chain management module.

[0117] 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 runnable on the processor, wherein the program or instruction, when executed by the processor, implements a method as in any one of the implementation methods in the embodiments of the present application; wherein the processor can adopt a general central processing unit (CPU), a microprocessor, an application specific integrated circuit (ASIC), a graphics processing unit (GPU) or one or more integrated circuits to execute relevant programs to implement the method in any one of the implementation methods in the embodiments of the present application.

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

[0119] 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 device, a discrete gate or transistor logic device, or a discrete hardware component. The various 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. The steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor.

[0120] The software module can be located in a storage medium well-established in the art, such as a random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or register. The storage medium is located in the memory, and the processor reads the information in the memory and, in conjunction with its hardware, completes the functions required to be performed by the units included in the data processing apparatus of the embodiments of the present application, or executes the method of any implementation method of the embodiments of the present application.

[0121] The above embodiments are detailed descriptions of specific implementations of the present application, but the scope of protection of the present application is not limited to the above embodiments. Any changes and modifications based on the ideas and principles of the present application should be included in the scope of protection of the present application.

Claims

1. A multi-enterprise collaboration method for logistics supply chain based on shared chain, characterized by: Applied to a multi-enterprise collaborative platform for a logistics supply chain, the platform includes a chain management module and multiple business modules. The method is executed by the chain management module and includes: Real-time monitoring of task creation dynamics of each business module; When it is monitored that the business module completes the first processing task based on the target business creation, the target shared chain for processing the target business is determined according to the chain identifier carried in the target business, the processing progress data of the first processing task is tracked and obtained, and the processing progress data is shared in real time with the authorized role on the target shared chain; the shared chain is created by the user according to business needs for a certain item or a certain type of business, and the shared chain includes multiple nodes, each node is assigned a corresponding role, and each role corresponds to a partner, wherein the role is set by the user according to business needs, and is used to limit the business functions to be implemented by each node on the shared chain. The partner is an entity enterprise, which is used to play the corresponding role and is the object that actually completes the business operation of the corresponding node; Determine the node type of the node corresponding to the business module on the target shared chain. If the node type is an initial node or an intermediate node, upon detecting that the first processing task is completed, send a task creation instruction to the business module corresponding to the next node to instruct the business module corresponding to the next node to create a second processing task based on the processing result of the first processing task and the target business; When monitoring that the business module completes the first processing task based on the target business, pre-constructing a processing task on the business module corresponding to the unreached node based on the target business, wherein the unreached node is all nodes on the target shared chain that are located after the current node; Evaluate whether the pre-built processing task can be successfully completed. If it cannot be successfully completed, generate an emergency resource scheduling task and send it to the corresponding partner; Track the processing progress of the resource emergency scheduling task. If it is determined that the resource emergency scheduling task cannot be completed within the preset time, a control instruction is issued to the business module corresponding to the initial node of the target sharing chain to instruct the business module corresponding to the initial node to refuse the user to initiate a new business to the target sharing chain.

2. The method according to claim 1, characterized in that The method for creating the target sharing chain includes: In response to a target sharing chain creation request initiated by a user, parsing the creation request to obtain sharing chain attribute information and invitee information, wherein the sharing chain attribute information includes role names, relationships between roles, and role permissions; Determine an invitee based on the invitee information, and send an on-chain invitation to the invitee; After receiving a confirmation reply of the on-chain invitation, instruct the user to determine the partner corresponding to the role name from the invitees; In response to the confirmation information submitted by the user, the nodes and node relationships on the target shared chain are constructed according to the role names and the relationships between the roles, and the corresponding business modules are configured for the partners according to the role permissions and the on-chain data viewing permissions are set.

3. The method according to claim 2, characterized in that The step of instructing the user to determine the partner corresponding to the role name includes: When there are multiple invitees for the same role name, generate capability assessment results for each invitee based on historical cooperation data and invitee qualification analysis for user reference and selection; or A bidding interface is provided so that each invitee can complete the bidding based on the bidding interface, and the bidding results are output for the user's reference and selection.

4. The method according to claim 1, wherein The method for creating the target sharing chain includes: In response to a sharing chain editing request initiated by a user, a designated sharing chain in a sharing chain resource pool is modified to generate the target sharing chain.

5. The method according to claim 1, wherein The chain management module is provided with a first communication port and a second communication port. By monitoring the first communication port, the task data reported by each business module is obtained to realize real-time monitoring of the task creation dynamics of each business module, and the task creation instruction is sent to the business module corresponding to the next node through the second communication port, wherein the first communication port is different from the second communication port.

6. The method according to claim 5, characterized in that The service priority of the second communication port is higher than that of the first communication port.

7. A multi-enterprise collaborative platform for logistics supply chain, characterized by: The platform includes a chain management module and multiple business modules, wherein the chain management module is used to implement the method according to any one of claims 1 to 6.

8. An electronic device, characterized in that: The electronic device includes 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 6 when executed by the processor.

Images